BG EMS - LAN UM A00 2-2 en

BroadGate™
EMS-!LAN
USER’S MANUAL
VERSION 2.2
TM
BroadGate EMS-µLAN User’s Manual (UM)
1st Release – March 2005
© Copyright by ECI Telecom Ltd., 2004. 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 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’s 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 into 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 (e.g., 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.
BroadGate™ EMS-µLAN User's Manual Table of Contents
Table of Contents
1 Introduction ............................................................................................... 1-1

1.1 Powerful Centralized Management .................................................... 1-2
1.2 Management Connectivity.................................................................. 1-3
1.3 LCT-μLAN Craft Terminal .................................................................. 1-4
1.4 EMS-μLAN Standalone Mode of Operation........................................ 1-5
1.5 EMS-μLAN Integrated Mode of Operation.......................................... 1-8
2 Installation ................................................................................................. 2-1

2.1 Overview ............................................................................................ 2-1
2.2 Before Beginning Installation.............................................................. 2-2
2.3 Installation Required for eNM Integrated Mode .................................. 2-2
2.4 Installing EMS-μLAN .......................................................................... 2-4
2.5 NMS Integration Installation ............................................................. 2-18
2.6 Configuration Procedures ................................................................ 2-23
2.7 Software Installation on an eNM Workstation................................... 2-30
2.8 Uninstalling the EMS-µLAN.............................................................. 2-36
3 General Operating Instructions................................................................ 3-1

3.1 Preparation for First-time Operation................................................... 3-1
3.2 General Operating Procedures .......................................................... 3-8
3.3 Operating the EMS-μLAN Remotely................................................... 3-9
3.4 Security............................................................................................ 3-11
3.5 EMS-μLAN About Window ............................................................... 3-11
3.6 EMS-μLAN Workflow ....................................................................... 3-12
4 Building the Network ................................................................................ 4-1

4.1 Overview ............................................................................................ 4-1
4.2 Topology Browser .............................................................................. 4-1
4.3 Starting the Network Topology Browser ............................................. 4-2
4.4 Run Mode .......................................................................................... 4-2
4.5 Design Mode.................................................................................... 4-10
4.6 Creating NEs.................................................................................... 4-14
426006-2406-033-A00 ECI Telecom Ltd. Proprietary iii

Table of Contents BroadGate™ EMS-µLAN User's Manual
4.7 Creating Links .................................................................................. 4-19

4.8 Setting the Network Time................................................................. 4-24
5 Building Trails ........................................................................................... 5-1

5.1 Overview ............................................................................................ 5-1
5.2 Trail Types ......................................................................................... 5-2
5.3 Using the Trail Manager..................................................................... 5-4
5.4 Displaying and Editing Trails ............................................................ 5-23
5.5 Inserting an NE on a Link................................................................. 5-24
5.6 Inserting an External NE on a Link ................................................... 5-24
5.7 Repairing a Trail............................................................................... 5-25
5.8 Displaying NE Cross-connection Information ................................... 5-26
5.9 Deleting an Existing Trail ................................................................. 5-27
6 Configuring and Monitoring μLAN NEs ................................................... 6-1

6.1 Overview ............................................................................................ 6-1
6.2 Card View .......................................................................................... 6-2
6.3 Viewing MU Card Information ............................................................ 6-4
6.4 Viewing TIU Card Information ............................................................ 6-7
6.5 View Details Window.......................................................................... 6-8
6.6 Building Trails Using Card View ....................................................... 6-24
6.7 Viewing Performance Information .................................................... 6-36
6.8 Performing Maintenance Operations................................................ 6-41
6.9 Configuring Trace IDs ...................................................................... 6-44
6.10 Defining Advanced Options.............................................................. 6-45
6.11 Resetting the NE.............................................................................. 6-47
7 Configuring and Monitoring Ethernet Services ...................................... 7-1

7.1 Introduction ........................................................................................ 7-1
7.2 Ethernet Configuration Procedures .................................................... 7-4
7.3 Configuring General Switching Parameters ....................................... 7-6
7.4 Defining the Physical Port Configuration .......................................... 7-11
7.5 Configuring Port Priorities ................................................................ 7-14
7.6 Configuring VLAN Tables................................................................. 7-15
7.7 Configuring RSTP Protection ........................................................... 7-27
7.8 Defining Ethernet Alarm Settings ..................................................... 7-33
7.9 Viewing Ethernet Port Statistics ....................................................... 7-35
iv ECI Telecom Ltd. Proprietary 426006-2406-033-A00

BroadGate™ EMS-µLAN User's Manual Table of Contents
8 Using the Alarm and Performance Viewer .............................................. 8-1

8.1 Overview ............................................................................................ 8-1
8.2 Starting the Alarm and PM Viewer ..................................................... 8-1
8.3 Analyzing Alarms ............................................................................... 8-5
8.4 Analyzing Performance ...................................................................... 8-9
9 Additional Services and Tools ................................................................. 9-1

9.1 Services ............................................................................................. 9-1
9.2 Network Resolution Tool .................................................................... 9-3
9.3 Control Panel Applet .......................................................................... 9-8
9.4 Installation Control ........................................................................... 9-10
9.5 Download / Backup Center............................................................... 9-11
A SQL Reference .......................................................................................... A-1

A.1 Overview ............................................................................................ A-1
A.2 Accessing the SQL Databases........................................................... A-2
A.3 Database Structure ............................................................................ A-4
A.4 Using the Query Analyzer ................................................................ A-22
B PC Backup and RDR .................................................................................B-1
B.1 Scope................................................................................................. B-1
B.2 Performing Database Backups........................................................... B-1
B.3 Remote Database Replication (RDR)................................................. B-7
B.4 Performing NE Configuration Backups............................................... B-9
C TU-12 KLM Notation Conversion Tables..................................................C-1
D Glossary.....................................................................................................D-1
Index..................................................................................................................... I-1
426006-2406-033-A00 ECI Telecom Ltd. Proprietary v

List of Figures BroadGate™ EMS-µLAN User's Manual
List of Figures
Figure 1-1: LCT Manager window........................................................................................ 1-4
Figure 1-2: eNM LightSoft window....................................................................................... 1-9
Figure 1-3: eNM window .................................................................................................... 1-10
Figure 1-4: Creating a Slave Manager using eNM............................................................. 1-10
Figure 1-5: Creating a new EME using eNM ..................................................................... 1-11
Figure 1-6: Connecting two elements using eNM.............................................................. 1-11
Figure 1-7: Viewing alarms using eNM.............................................................................. 1-12
Figure 1-8: Viewing element information using eNM ......................................................... 1-12
Figure 1-9: Creating an EMS session using eNM LightSoft .............................................. 1-13
Figure 1-10: Connecting two elements using eNM LightSoft............................................. 1-14
Figure 1-11: Viewing link details using eNM LightSoft....................................................... 1-14
Figure 1-12: Viewing alarms using eNM LightSoft............................................................. 1-15
Figure 1-13: Viewing element information using eNM LightSoft........................................ 1-16
Figure 2-1: RTSetup window ............................................................................................... 2-4
Figure 2-2: DAO SDK – Setup Type window2-5
Figure 2-3: MS-SQL Server – Select Install Method window............................................... 2-6
Figure 2-4: MS-SQL Server – Setup Type window.............................................................. 2-7
Figure 2-5: MS-SQL Server – Select Components window................................................. 2-7
Figure 2-6: MS-SQL Server – Character Set/Sort Order/Unicode Collation window........... 2-8
Figure 2-7: MS-SQL Server – Services Accounts window .................................................. 2-8
Figure 2-8: SNMP Service – Windows Components window.............................................. 2-9
Figure 2-9: EMS-μLAN installation – selecting network type ............................................. 2-10
Figure 2-10: EMS-μLAN installation – selecting element type........................................... 2-11
Figure 2-11: EMS-μLAN installation – Select Components window .................................. 2-11
Figure 2-12: RTSetup window – EMS Applications tab ..................................................... 2-12
Figure 2-13: WinVNC: Current User Properties window ................................................... 2-16
Figure 2-14: Orbix 6.1 – License Agreement window........................................................ 2-18
Figure 2-15: Orbix 6.1 – Choose Install Folder window..................................................... 2-19
Figure 2-16: Orbix 6.1 – Choose Shortcut Location window ............................................. 2-19
Figure 2-17: Orbix 6.1 – Environment Settings window 1.................................................. 2-20
Figure 2-18: Orbix 6.1 – Environment Settings window 2.................................................. 2-20
Figure 2-19: License window ............................................................................................. 2-21
Figure 2-20: Services window............................................................................................ 2-22
Figure 2-21: RTSetup window – Extensions tab................................................................ 2-22
Figure 2-22: context.txt – Notepad window........................................................................ 2-23
Figure 2-23: Network Management Configuration tab....................................................... 2-24
Figure 2-24: Edit DWORD Value window .......................................................................... 2-25
Figure 2-25: New User window.......................................................................................... 2-27
Figure 2-26: Computer Management window.................................................................... 2-27
Figure 2-27: MTNM server window.................................................................................... 2-35
Figure 2-28: Force registration parameters window .......................................................... 2-35
Figure 2-29: Create EMS window ...................................................................................... 2-36
Figure 2-30: MssqlServer7 pop-up menu .......................................................................... 2-37
Figure 2-31: SQL Server Service Manager window........................................................... 2-37
Figure 3-1: Configure Default Gateway window .................................................................. 3-3
Figure 3-2: Add Item window ............................................................................................... 3-3
Figure 3-3: Successful ping of main gateway ...................................................................... 3-4
Figure 3-4: Failover to reserved gateway ............................................................................ 3-5
vi ECI Telecom Ltd. Proprietary 426006-2406-033-A00

BroadGate™ EMS-µLAN User's Manual List of Figures
Figure 3-5: WinVNC: Current User Properties window ..................................................... 3-10

Figure 3-6: serverDialog window ....................................................................................... 3-10
Figure 3-7: Card View About window................................................................................. 3-11
Figure 3-8: EMS-μLAN workflow ....................................................................................... 3-12
Figure 4-1: Topology Browser icon ...................................................................................... 4-2
Figure 4-2: Typical Run mode Topology Browser window................................................... 4-3
Figure 4-3: Topology Browser element icon key.................................................................. 4-4
Figure 4-4: Navigator window .............................................................................................. 4-5
Figure 4-5: Selecting the background map.......................................................................... 4-6
Figure 4-6: Typical Design Mode Topology Browser window ............................................ 4-11
Figure 4-7: Add Network Element window......................................................................... 4-15
Figure 4-8: Example of default connectivity direction ........................................................ 4-16
Figure 4-9: Example showing connectivity direction change ............................................. 4-16
Figure 4-10: Redefine NE windows ................................................................................... 4-17
Figure 4-11: Add External Element window....................................................................... 4-18
Figure 4-12: Connect two elements window...................................................................... 4-20
Figure 4-13: Topology Browser popup window.................................................................. 4-21
Figure 4-14: Connection to External Element window....................................................... 4-22
Figure 4-15: Warning message ......................................................................................... 4-22
Figure 4-16: Connection Between External Element window ............................................ 4-23
Figure 4-17: Tardis window................................................................................................ 4-25
Figure 5-1: Definition of routing options ............................................................................... 5-2
Figure 5-2: Bidirectional trail ................................................................................................ 5-3
Figure 5-3: Protected bidirectional trail ................................................................................ 5-3
Figure 5-4: Unidirectional trail .............................................................................................. 5-4
Figure 5-5: Trail Manager window ....................................................................................... 5-5
Figure 5-6: Select trail type window ..................................................................................... 5-8
Figure 5-7: Select outgoing port window.............................................................................. 5-9
Figure 5-8: Add Trail window – two µLAN NEs.................................................................. 5-10
Figure 5-9: Add Trail window – Path tab............................................................................ 5-11
Figure 5-10: Send crossconnections window .................................................................... 5-13
Figure 5-11: Trail list window ............................................................................................. 5-14
Figure 5-12: Trail Manager window showing add SNCP protection option........................ 5-16
Figure 5-13: Select outgoing port window.......................................................................... 5-17
Figure 5-14: Trail Manager showing protected trail ........................................................... 5-18
Figure 5-15: Trail protection status window ....................................................................... 5-20
Figure 5-16: J2 Configuration window ............................................................................... 5-21
Figure 5-17: Check database consistency window............................................................ 5-22
Figure 5-18: Displaying trails ............................................................................................. 5-23
Figure 5-19: Trail Manager window showing trail to be repaired ....................................... 5-25
Figure 5-20: NE cross-connection information .................................................................. 5-26
Figure 6-1: Typical Card View window................................................................................. 6-2
Figure 6-2: Typical VC-3 Card View window ....................................................................... 6-2
Figure 6-3: View card info – MU window ............................................................................. 6-5
Figure 6-4: View info – TIU window ..................................................................................... 6-7
Figure 6-5: View Details window.......................................................................................... 6-8
Figure 6-6: SPI Info window............................................................................................... 6-12
Figure 6-7: PPI View Info window showing 21 E1 ports .................................................... 6-14
Figure 6-8: PPI View Info window showing 14 E1 ports and three E3 ports...................... 6-14
Figure 6-9: PPI information window................................................................................... 6-15
Figure 6-10: Terminal View Info window............................................................................ 6-17
Figure 6-11: Timing window............................................................................................... 6-18
Figure 6-12: Contact and Relays window – Dry Contact table........................................... 6-21
426006-2406-033-A00 ECI Telecom Ltd. Proprietary vii

List of Figures BroadGate™ EMS-µLAN User's Manual
Figure 6-13: Contacts and Relays window – Output Relay table....................................... 6-22
Figure 6-14: Contacts and Relays window – Input Analog table ....................................... 6-23
Figure 6-15: Defining E1 trails in Card View ...................................................................... 6-24
Figure 6-16: Defining E3 trails in Card View ...................................................................... 6-25
Figure 6-17: Defining Ethernet trails in Card View............................................................. 6-25
Figure 6-18: Configuring the J2/J1 bit................................................................................ 6-29
Figure 6-19: Cross-connect screen showing the XC TUs list ............................................ 6-30
Figure 6-20: Cross-connect screen showing add protection option................................... 6-31
Figure 6-21: Cross-connect screen showing protected cross-connection......................... 6-32
Figure 6-22: Cross-connect screen showing protected cross-connection......................... 6-33
Figure 6-23: Cross-connect screen showing TU statuses................................................. 6-34
Figure 6-24: TU failure condition example......................................................................... 6-34
Figure 6-25: Performance Chart window ........................................................................... 6-37
Figure 6-26: Performance Threshold Settings window...................................................... 6-40
Figure 6-27: Example showing maintenance on multiplexer subsystem ........................... 6-43
Figure 6-28: Maintenance Info window .............................................................................. 6-43
Figure 6-29: Trace ID modification .................................................................................... 6-44
Figure 6-30: MU Advanced info window – Ethernet tab..................................................... 6-45
Figure 6-31: MU Advanced info window – LAN/WAN Setup tab ....................................... 6-46
Figure 6-32: Reset Card window ....................................................................................... 6-47
Figure 7-1: µLAN building blocks......................................................................................... 7-2
Figure 7-2: Dedicated EoS point-to-point links using the µLAN........................................... 7-2
Figure 7-3: Implementing a PTP service ............................................................................. 7-3
Figure 7-4: Shared EoS topology......................................................................................... 7-4
Figure 7-5: Ethernet Management window – configuring switching parameters ................. 7-6
Figure 7-6: Ethernet Management window – Line configuration tab ................................. 7-11
Figure 7-7: VLAN flowchart................................................................................................ 7-19
Figure 7-8: Ethernet Management – VLAN configuration tab............................................ 7-20
Figure 7-9: Example showing CSF/TSF VLAN IDs ........................................................... 7-25
Figure 7-10: Configuring RSTP protection......................................................................... 7-28
Figure 7-11: Ethernet Alarms window – Traffic Error Alarms tab ...................................... 7-33
Figure 7-12: Ethernet Alarms window – Line Alarms tab................................................... 7-34
Figure 7-13: Ethernet Alarms window – Ethernet Thresholds tab ..................................... 7-34
Figure 7-14: Performance Chart window – Charts tab ...................................................... 7-35
Figure 7-15: Performance Chart window – Settings tab .................................................... 7-39
Figure 8-1: Alarm and PM Viewer window – Alarms Mode display ..................................... 8-5
Figure 8-2: Range Selection window ................................................................................... 8-6
Figure 8-3: Sound settings window...................................................................................... 8-8
Figure 8-4: SDH performance table................................................................................... 8-11
Figure 8-5: RMON performance table ............................................................................... 8-12
Figure 8-6: Columns window ............................................................................................. 8-13
Figure 8-7: Performance graph pop-up menu ................................................................... 8-14
Figure 8-8: SDH performance graph ................................................................................. 8-15
Figure 8-9: Legend window................................................................................................ 8-15
Figure 8-10: RMON performance graph............................................................................ 8-16
Figure 9-1: EMS-µLAN Services Watchdog ........................................................................ 9-1
Figure 9-2: Network Resolution window for trails ................................................................ 9-4
Figure 9-3: Network Resolution window for cross-connections ........................................... 9-5
Figure 9-4: Example showing a compound network............................................................ 9-5
Figure 9-5: Service Control I tab .......................................................................................... 9-8
Figure 9-6: Service Control II tab ......................................................................................... 9-9
Figure 9-7: Installation Control – System tab9-10
Figure 9-8: Installation Control – Management tab............................................................ 9-11
viii ECI Telecom Ltd. Proprietary 426006-2406-033-A00

BroadGate™ EMS-µLAN User's Manual List of Figures
Figure 9-9: Download Center Log In window9-12

Figure 9-10: Download / Backup Center window – Network elements list tab .................. 9-12
Figure 9-11: Download / Backup Center window – Processing tab................................... 9-14
Figure 9-12: Open window................................................................................................. 9-16
Figure 9-13: Change Download Bank window................................................................... 9-17
Figure 9-14: Embedded software upgrade processing at completion of stage one .......... 9-18
Figure 9-15: Embedded software upgrade processing during stage two .......................... 9-19
Figure 9-16: Information window ....................................................................................... 9-19
Figure 9-17: Embedded software upgrade processing after completion ........................... 9-20
Figure 9-18: Sample backup folder showing backup files ................................................. 9-21
Figure 9-19: Sample backup folder showing backup files ................................................. 9-22
Figure 9-20: Sample showing SW Package Upgrade operation ....................................... 9-24
Figure 9-21: Download / Backup Center window – Processing tab for Reset operation ... 9-25
Figure 9-22: Download / Backup Center window – Processing tab showing forced use of
standby software............................................................................................ 9-26
Figure A-1: Enterprise Manager window..............................................................................A-2
Figure A-2: List of TNGDB tables ........................................................................................A-3
Figure A-3: Sample of data in selected table.......................................................................A-4
Figure A-4: Trail table dependencies ...................................................................................A-5
Figure A-5: Connect to SQL Server window ......................................................................A-22
Figure A-6: Query Analyzer – main window.......................................................................A-23
Figure A-7: Query Analyzer – display of matching query data...........................................A-24
Figure B-1: NMS DB protection window – Backup tab ........................................................B-2
Figure B-2: Daily database backup schedule ......................................................................B-3
Figure B-3: NMS DB protection window – Restore tab........................................................B-4
Figure B-4: SQL Server Backup window .............................................................................B-5
Figure B-5: Choose Backup Destination window.................................................................B-6
Figure B-6: RDR ..................................................................................................................B-7
Figure C-1: KLM notation.....................................................................................................C-1
426006-2406-033-A00 ECI Telecom Ltd. Proprietary ix

List of Tables BroadGate™ EMS-µLAN User's Manual
List of Tables
Table 2-1: EMS-μLAN hardware requirements ................................................................... 2-1
Table 2-2: SNMP parameters ............................................................................................ 2-24
Table 4-1: Element status colors ......................................................................................... 4-4
Table 4-2: Run mode menu bar........................................................................................... 4-7
Table 4-3: Run mode toolbar ............................................................................................... 4-8
Table 4-4: General browser menu ....................................................................................... 4-9
Table 4-5: Element menu .................................................................................................... 4-9
Table 4-6: Link menu ......................................................................................................... 4-10
Table 4-7: Design mode – Configuration menu................................................................. 4-12
Table 4-8: Design mode toolbar ........................................................................................ 4-13
Table 4-9: NE parameters ................................................................................................. 4-15
Table 4-10: External NE parameters ................................................................................. 4-19
Table 5-1: Trail Manager window items............................................................................... 5-6
Table 5-2: Trail list window items....................................................................................... 5-14
Table 5-3: Trail status options ........................................................................................... 5-15
Table 5-4: Additional trail options....................................................................................... 5-21
Table 5-5: Deleting existing trails....................................................................................... 5-27
Table 6-1: µLAN status indicators........................................................................................ 6-3
Table 6-2: Card View buttons .............................................................................................. 6-4
Table 6-3: View card info – MU window fields ..................................................................... 6-6
Table 6-4: View info – TIU window fields ............................................................................. 6-8
Table 6-5: View Details menu bar........................................................................................ 6-9
Table 6-6: SPI Info window fields....................................................................................... 6-13
Table 6-7: PPI information window fields........................................................................... 6-16
Table 6-8: Primary and secondary fields ........................................................................... 6-19
Table 6-9: Contact and Relay tables.................................................................................. 6-22
Table 6-10: Performance menu options ............................................................................ 6-36
Table 6-11: Reset Performance options ............................................................................ 6-39
Table 6-12: Reset Performance Threshold options........................................................... 6-40
Table 6-13: Multiplexer maintenance options .................................................................... 6-42
Table 6-14: PPI maintenance options................................................................................ 6-43
Table 7-1: Physical LAN port parameters.......................................................................... 7-12
Table 7-2: Ethernet duplex mismatches ............................................................................ 7-13
Table 7-3: Port and frame priority settings......................................................................... 7-15
Table 7-4: Reserved VLAN ID values ................................................................................ 7-17
Table 7-5: Configurable RSTP fields ................................................................................. 7-29
Table 7-6: Read-only RSTP fields ..................................................................................... 7-30
Table 7-7: STP port configuration parameters .................................................................. 7-31
Table 7-8: Port-specific RSTP parameters........................................................................ 7-32
Table 7-9: Performance Chart window options.................................................................. 7-38
Table 8-1: Alarm and PM Viewer menu bar......................................................................... 8-3
Table 8-2: Alarm and PM Viewer toolbar ............................................................................. 8-4
Table 8-3: Alarm details....................................................................................................... 8-7
Table 8-4: East/West performance statistics....................................................................... 8-9
Table 8-5: RMON performance statistics .......................................................................... 8-10
Table 8-6: Performance data columns .............................................................................. 8-12
Table 9-1: Alarm levels ........................................................................................................ 9-2
Table 9-2: Action menu options – ring or link folder ............................................................ 9-7
x ECI Telecom Ltd. Proprietary 426006-2406-033-A00

BroadGate™ EMS-µLAN User's Manual List of Tables
Table 9-3: Action menu options – element .......................................................................... 9-7

Table 9-4: Network Elements list parameters.................................................................... 9-13
Table 9-5: Processing parameters .................................................................................... 9-14
Table 9-6: Download / Backup Center operations ............................................................. 9-15
Table A-1: TNGDB tables ....................................................................................................A-4
Table A-2: tng_managedobject fields ..................................................................................A-6
Table A-3: tng_link fields .....................................................................................................A-7
Table A-4: TrailEx fields.......................................................................................................A-8
Table A-5: Trail fields...........................................................................................................A-9
Table A-6: CrossConnect2 fields .......................................................................................A-10
Table A-7: TrailSegment fields ..........................................................................................A-11
Table A-8: TUmid fields .....................................................................................................A-12
Table A-9: TU2 fields .........................................................................................................A-12
Table A-10: CardViewDB tables ........................................................................................A-13
Table A-11: tblAlarmID fields .............................................................................................A-14
Table A-12: tblAlarmSever fields .......................................................................................A-14
Table A-13: tblCurAlarms fields .........................................................................................A-14
Table A-14: tblPerfHistoryHighOr fields .............................................................................A-15
Table A-15: tblPerfHistoryLowOr fields..............................................................................A-16
Table A-16: tblPerfHistoryMulti fields.................................................................................A-17
Table A-17: tblPerfHistoryPPI fields...................................................................................A-18
Table A-18: tblPerfHistoryRegen fields..............................................................................A-19
Table A-19: tblPerfHistoryRMON fields .............................................................................A-20
Table A-20: tblPerfHistoryTuMid fields ..............................................................................A-21
Table A-21: TNGDB – NE query examples .......................................................................A-25
Table A-22: TNGDB – link query examples.......................................................................A-26
Table A-23: TNGDB – UUID query examples ...................................................................A-26
Table A-24: TNGDB – cross-connect query examples......................................................A-27
Table A-25: CardViewDB – NE query examples ...............................................................A-27
Table A-26: CardViewDB – performance query examples ................................................A-29
Table C-1: TU-12 KLM notation conversion table................................................................C-1
426006-2406-033-A00 ECI Telecom Ltd. Proprietary xi

List of Tables BroadGate™ EMS-µLAN User's Manual
xii ECI Telecom Ltd. Proprietary 426006-2406-033-A00

1
Introduction
The BroadGate™ μLAN is a data-aware SDH multiplexer with Layer 2 switching
intelligence that seamlessly integrates into existing optical SDH networks. It extends the
high-speed SDH optical backbone, enabling operators to provide connectivity services for
enterprises. With the BroadGate μLAN, network operators can easily and cost-effectively
expand existing infrastructure to accommodate medium- and large-sized businesses, and
allocate bandwidth to both data (packet) and voice (circuit-switched) traffic as needed.
There are three Tributary Interface Units (TIUs) available for the BroadGate μLAN, as
follows:
!" TIU-16E1-2Eth – features 16 E1 ports and two 10/100BaseT ports
!" TIU-21E1-6Eth – features 21 E1 ports and six 10/100BaseT ports
!" TIU-3E3-14E1-6Eth – features three E3 ports, 14 E1 ports and 6 10/100BaseT ports
NOTE: Additional TIUs are under development and will be

released in future versions of the product. For more information,
refer to the BroadGate μLAN General Description.
BroadGate μLAN combines the simplicity and economic benefits of Ethernet with the
reliability and manageability of SDH, providing reliable, multiservice access to business
users. A built-in Add Drop Multiplexer (ADM) efficiently carries Ethernet signals up to
2 x 155 Mbps over SDH. Furthermore, this integration enables the BroadGate μLAN to
achieve reliable, fault-tolerant payload transport at rates of up to STM-1 and above.
By providing both data and voice services, the BroadGate μLAN enhances the wide range of
services offered by ECI Telecom's Optical Networks Division flagship product – XDM®.
This data/voice convergence meets the growing demand for data services, integrates easily
into existing infrastructures, provides an expansion path as needs grow, and creates new
sources of revenue.
The unit is managed by an open management system, the EMS-μLAN, which smoothly
integrates into operators' existing systems.
Additional information about these products can be found in the following ECI Telecom
documents:
!" BroadGate μLAN General Description
!" BroadGate μLAN Installation, Operation and Maintenance Manual
!" eNM LightSoft™ User's Manual
!" eNM User's Manual
426006-2406-033-A00 ECI Telecom Ltd. Proprietary 1-1

Introduction BroadGate™ EMS-µLAN User's Manual
1.1 Powerful Centralized Management

The BroadGate EMS-μLAN's integrated element management system gives operators
comprehensive, centralized control over principal system functions, including SDH
management, reconfiguration of bandwidth requirements, and reallocation of voice/data
ratios.
The EMS-μLAN controls system topology, configuration, trail management, fault recovery,
and performance monitoring. It connects to µLAN equipment either directly or through the
Data Communication Channel (DCC). Since SDH implementation includes in-band
management channels, the EMS-μLAN station only needs to connect to one µLAN unit in
the network, which then becomes the network gateway for managing all other units in the
network.
Based on the Microsoft Windows™ 2000 operating systems, the EMS-μLAN management
system provides a familiar, easy-to-use graphical user interface. With the ability to control
more than 80 network elements (NEs), it enables operators to monitor activity system-wide,
or zoom in and configure specific NEs. To ensure system security, the EMS-μLAN supports
several password-protected user access levels. The highest access level is allocated to
maintenance functions that can change critical configuration parameters.
The EMS-μLAN also provides data export capabilities in a wide range of formats. As the
EMS-µLAN database employs a Microsoft SQL server, customized reports (beyond the
wide range of reports already provided by the system) can be generated by means of any
ODBC-compliant reporting tool. For more information about the SQL databases used by the
EMS-µLAN, refer to Appendix A, SQL Reference.
Based on a manager/agent model communicating via Simple Network Management
Protocol (SNMP), the EMS-μLAN was designed to be both open and modular. This enables
large network operators, who already have significant investments in existing Network
Management Systems (NMS), to use the advanced functions of the EMS-μLAN without
significant additional investment. In particular, the EMS-μLAN provides standard
interfaces/applications (for example, SNMP, CORBA and HTTP), which permit easy
integration with popular network-level management software such as HPOV Network Node
Manager and CA-Unicenter. The EMS-μLAN can also run as a Java application, further
facilitating integration with other applications running on diverse platforms.
The EMS-μLAN can operate in one of two modes:
!" Standalone – as described in EMS-μLAN Standalone Mode of Operation, page 1-5
!" Integrated – integrated into one of ECI Telecom's multidimensional network managers,
eNM or eNM LightSoft™, as described in EMS-μLAN Integrated Mode of Operation,
page 1-8
1-2 ECI Telecom Ltd. Proprietary 426006-2406-033-A00

BroadGate™ EMS-µLAN User's Manual Introduction
1.2 Management Connectivity

A single EMS-μLAN station can manage multiple μLAN units. This is done by connecting
the EMS-μLAN through the Local Area Network (LAN) to the 10/100BaseT Ethernet
management port (MNG) of one μLAN NE in the network. This μLAN NE then acts as a
gateway, enabling the EMS-μLAN to manage all the other NE in the network via the inband
management channels. Gateway redundancy can be provided by designated a second μLAN
NE as a standby in case the main gateway goes down, as described in Configuring Gateway
Redundancy, in Chapter 3, General Operating Instructions.
BroadGate μLAN equipment uses standard IP routing processes for inband management
traffic. Therefore, management traffic benefits from all the automatic alternate routing
capabilities provided by standard IP routers.
Another approach to ensure that alternate management paths are available is to provide a
standby out-of-band path to additional elements in the network. This path enables
management traffic to pass if a fault occurs that prevents the management station from
reaching the NEs through the original gateway. The standby path can be provided through
the Wide Area Network (WAN) serving the operator data network, using routers that
prevent the activation of the backup path under normal conditions. For more information
about routing, refer to the BroadGate µLAN Installation, Operation and Maintenance (IOM)
Manual.

1.3 LCT-μLAN Craft Terminal

In addition to the EMS-μLAN application for managing μLAN NEs on a day-to-day basis
from a management station, ECI Telecom offers the LCT-μLAN for management of
individual NEs by field technicians. This craft terminal application is particularly suited to
first-time installation and commissioning procedures. It can also be used as an EMS-μLAN
full-featured support application to view the current alarms in the NE and to access the Card
View application (see Card View, page 1-6) in cases when the management station is not
available.
Figure 1-1: LCT Manager window
When performing first-time installation, the LCT-μLAN can be used to define IP settings
and DCC settings required by the new NE to become a functional part of the μLAN
network.
For more information about using the LCT-μLAN, refer to the BroadGate μLAN
Installation, Operation and Maintenance (IOM) Manual.

1.4 EMS-μLAN Standalone Mode of Operation

In the standalone mode, the EMS-μLAN's main window displays graphical icons for each of
the NEs defined in the system. Users can drill down to each of the NEs and perform system
operations via the EMS-μLAN interface.
The EMS-μLAN integrates SDH management in a single package and provides modular
support for the following functions:
!" Configuration management – initializes and shuts down all or parts of the network;
maintains, adds, and updates relationships among components; views and configures
NEs with an easy-to-use graphical user interface
!" Fault management – polls NE agents to ensure that managed devices and objects are
operating efficiently, and reports faults to the system administrator
!" Performance management – monitors network activity and stores data in the database
for the purpose of producing current or historical performance statistics, in both graphic
and textual formats
1.4.1 EMS-μLAN Components

The EMS-μLAN is comprised of the following Manager components and additional tools:
!" Topology Browser, below
!" Trail Manager application, page 1-6
!" Shelf View application (Card View), page 1-6
!" Alarm and PM Viewer, page 1-7
!" Network Resolution Tool, page 1-7
!" Windows services, page 1-8
1.4.1.1 Topology Browser
The EMS-μLAN Topology Browser provides a comprehensive view of the network

topology. From the Topology Browser, administrators gain an awareness of overall network
conditions at a glance. The Topology Browser enables administrators to:
!" View the status of all NEs
!" Configure the network by adding or deleting elements and element links
!" Zoom in on individual elements and access other EMS-µLAN applications
For more information about the Topology Browser, refer to Chapter 4, Building the
Network.

1.4.1.2 Trail Manager
To facilitate simple and error-free service provisioning, the Trail Manager application
provides administrators with an effective tool for allocating SDH network resources (for
example, tributary units). The Trail Manager application provides:
!" Graphical representation of trails
!" Illustration of SDH resource availability
!" Trail building
1.4.1.2.1 Graphical representation of trails
The Trail Manager provides a list of existing trails. When the administrator selects a trail
from the list, the system displays an illustration of the network topology, along with the trail
ID or name, trail cross-connection type, trail path, and add/drop elements.
1.4.1.2.2 Illustration of SDH resource availability
The Trail Manager graphically illustrates the usage and availability of tributary units in the
network. Usage and availability levels can be displayed per link, for the entire ring, or for
mid-tributary units (resources internal to a specific NE).
1.4.1.2.3 Trail building
The Trail Manager application also enables provisioning of new SDH services. The
administrator simply enters a name for the new trail, and then configures information such
as the trail type, the elements that serve as add/drop locations, and the network resources to
be allocated. When the μLAN NE included in the trail contains a dual matrix, TUs from
both matrixes can be selected as part of a multipath trail. The Trail Manager prevents
configuration errors; any attempt to assign resources already in use results in an error
message, but is not service affecting.
For more information about the Trail Manager, refer to Chapter 5, Building Trails.
1.4.1.3 Card View
The EMS-μLAN Card View is a Java-based application that enables operators to perform a
comprehensive set of management functions on a specific μLAN NE, including:
!" Defining cross-connections within the μLAN as a portion of a larger trail
!" Viewing performance and maintenance information for the TIU as a whole, as well as
for specific μLAN subsystems
!" Configuring the physical LAN and virtual WAN Ethernet ports
!" Configuring Rapid Spanning Tree Protocol (RSTP) protection

!" Configuring the timing source

!" Performing maintenance actions
The Card View can be operated either in standalone mode or as an integrated part of the
eNM or eNM LightSoft network management system. For more information, refer to
Chapter 6, Configuring and Monitoring μLAN NEs and Chapter 7, Configuring and
Monitoring Ethernet Services.
NOTE: The Card View can also be activated from the

LCT-μLAN, as described in LCT-μLAN Craft Terminal,
page 1-4.
1.4.1.4 Alarm and PM Viewer
The Alarm and PM Viewer enables administrators to quickly diagnose a network problem
by drilling down on an element to find the location and cause of an alarm. When the status
of an element changes in the Topology Browser, drilling down displays the actual event or
alarm that caused the change.
All alarms reported to the EMS-μLAN manager system can be displayed. Administrators
can view alarms according to various criteria, including alarms for one or more NEs,
grouped by alarm severity or by date and time. Alarms are color-coded according to
severity. The Alarm and PM Viewer features one-click sorting and event acknowledgement.
The Alarm and PM Viewer is also used to view SDH and RMON performance data
collected by the system. The data is presented in both tabular and graphical formats.
For more information about the Alarm and PM Viewer, refer to Chapter 8, Using the Alarm
and PM Viewer.
1.4.1.5 Network Resolution Tool
The Network Resolution Tool enables operators to compare the trail/cross-connect data
stored in the EMS-µLAN database with the trail/cross-connection data contained in a
selected network/µLAN NE, respectively. This makes it possible to locate and correct
discrepancies that may have occurred due to a temporary loss in communication with the
unit. After resolving any discrepancies, the Network Resolution Tool can then be used to
repair the trail.
For more information about the Network Resolution Tool, refer to Chapter 9, Additional
Services and Tools.

1.4.1.6 Windows services
Windows services are applications that are initiated at system startup and executed
continuously, regardless of whether or not the administrator is logged on to the EMS-µLAN.
To ensure consistent communication between the EMS-µLAN and its agents, the
EMS-µLAN provides services such as:
!" Keep Alive Service – this service periodically pings each NE to ensure the element can
be reached.
!" Trap Service – this service listens at the PC's SNMP port for trap messages arriving
from SNMP agents. For each trap that arrives, a record is added to the Current Alarm
table for use in determining the agent's status.
!" Performance Service – this service polls the agents for performance information, and
stores the information in the performance history database for historical reporting
purposes.
These services, as well as additional ones, are described in Chapter 9, Additional Services
and Tools.
1.5 EMS-μLAN Integrated Mode of Operation

ECI Telecom offers two NMS solutions, both of which can integrate with the EMS-μLAN:
!" eNM is a unified NMS that provisions, monitors, and controls all network layers. With
eNM, administrators and users can support on-demand service provisioning, pinpoint
bandwidth allocation, and generate dramatic reductions in the equipment and operating
costs that multiple management systems often require.
!" eNM LightSoft offers a multilayer view to reflect both the physical and technology
infrastructure integral to SDH/SONET equipment and optical networks, giving carriers
a complete panoramic view of their converged networks. The multilayer approach
ensures that their investment is future proof, supporting them as they introduce new
technologies to their networks.
eNM and eNM LightSoft manage the complete family of Element Management Systems
(EMSs) offered by ECI Telecom, enabling you to assume full control of all equipment in the
network.
NOTE: Unless otherwise specified, the instructions in this

manual refer to the standalone mode of operation only.
For additional information regarding eNM LightSoft or eNM
operation, refer to their respective user manuals.

In the integrated mode of operation, the EMS-μLAN is launched from either the eNM or
eNM LightSoft Main window. For example, if the user views an icon on the eNM desktop
that represents a µLAN NE, drilling down on that element causes eNM to launch the Card
View application and display its Card View window. The user can then choose menu
options for the EMS-μLAN Card View.
Figure 1-2: eNM LightSoft window

Figure 1-3: eNM window
1.5.1 Working with eNM

In the integrated mode of operation, you can perform the following operations from the
eNM Main window:
!" Create a Slave Manager – you can define third-party management systems, otherwise
known as Slave Managers, which can be used to manage External Managed Elements
(EMEs).
Figure 1-4: Creating a Slave Manager using eNM

!" Create EMEs – you can define EMEs, including their name and IP address, as well as
the Slave Manager responsible for managing them.
Figure 1-5: Creating a new EME using eNM
!" Create links between two elements – you can select two elements, and then use the
Connection Window to select the ports that will serve as the link points between them.
Figure 1-6: Connecting two elements using eNM

!" Monitor alarms – you can manage the Alarm Log, which includes defining filters that
determine which alarms are displayed, defining the maximum quantity and time interval
for displaying alarms, and checking-off alarms.
Figure 1-7: Viewing alarms using eNM
!" View element information – you can view information about a specific element,
including its current state and any problems associated with it.
Figure 1-8: Viewing element information using eNM

1.5.2 Working with eNM LightSoft

In the integrated mode of operation, you can perform the following operations from the
eNM LightSoft Main window:
!" Create an EMS session – you can establish a session to manage µLAN managed
elements (MEs). You can view the status of any µLAN MEs in the eNM LightSoft Main
window.
Figure 1-9: Creating an EMS session using eNM LightSoft

!" Create links between two elements – you can select two MEs, and then use the Create
Topology Link window to select the ports that will serve as the link points between
them.
Figure 1-10: Connecting two elements using eNM LightSoft
!" View link information – you can view information about a specific link between two
MEs, including the ports used in the link and the rate for the connection. To access the
following window, simply double-click the link line in the eNM LightSoft Main
window.
Figure 1-11: Viewing link details using eNM LightSoft

!" Monitor alarms – you can manage current alarms, and define filters that determine
which alarms are displayed and their status. From this window, you can view the event
log and threshold-crossing alarms, as well as access an Alarm Counters window and
Audio Indications window.
Figure 1-12: Viewing alarms using eNM LightSoft

!" View element information – you can view information about a specific ME, including
its current state, type, software version, and any problems associated with it.
Figure 1-13: Viewing element information using eNM LightSoft
1.5.3 Software Emulation

Version 2.2 of the EMS-μLAN offers operators an additional method for integrating EMS
functionality into the overall network management. Using emulation software, a UNIX
workstation running eNM or eNM LightSoft can open a window displaying the
Windows-based interface for the EMS-μLAN management station. The operator can then
perform all EMS-μLAN management functions remotely, as if the operations were being
performed at the management station itself.
For more information about using software emulation, refer to Chapter 3, General Operating
Instructions.

This feature enables eNM and eNM LightSoft users to benefit from all end-to-end μLAN
management tools, as described in EMS-μLAN Components, page 1-5.
NOTE: The emulation package used is cross-platform,

open-source, remote control software that enables two
computers to interact with one another, even if they are of
different types.


2
Installation
2.1 Overview
This chapter describes how to install the EMS-μLAN. Basic knowledge of Windows 2000
and UNIX is required.
NOTE: If you are upgrading an existing EMS-μLAN

installation to version 2.1 or 2.2, contact ECI Telecom's
Optical Network Division's Technical Support department for
further instructions.
In addition to standalone mode, EMS-μLAN can work in an integrated mode under either
eNM or eNM LightSoft™. Refer to the relevant sections in this chapter for details about
how to install for both integration options.
2.1.1 Hardware Requirements

The management station PC on which the EMS-μLAN is being installed must meet the
following requirements:
Table 2-1: EMS-μLAN hardware requirements
Processor RAM size Disk size Video card NEs supported

memory
Pentium IV 1 GB 20 GB 1024x786 24-bit 1-100
1.8 GHz
This can be checked by accessing Start ! Programs ! Accessories ! System Tools !

System Info ! System Summary.

Installation BroadGate™ EMS-µLAN User's Manual
2.2 Before Beginning Installation

Before beginning the installation process, verify the following:
!" The user performing the installation is an Administrator. This can be checked in
Windows 2000 by selecting Start ! Settings ! Control Panel ! Administrative
Tools ! Computer Management ! Local Users and Groups ! Groups and then
looking for the name of the user in the Administrators group. For information about
adding users, refer to Configuring Additional Network Managers, page 2-26.
!" The display adapter is configured correctly. This can be checked by right-clicking the
Windows background and selecting Properties ! Settings ! Advanced ! Adapters
! Properties. The “This Device is working properly” message should appear.
Restart the computer and log in as Administrator. Proceed as follows:
!" If the EMS-μLAN is being used in integrated mode with eNM, first install eIMI and
Orbix, as described in Installation Required for eNM Integrated Mode, page 2-2.
!" If the EMS-μLAN is being used in integrated mode with NMS (eNM LightSoft),
Orbix 6.1 and MTNM Server must be installed at the end of the EMS-uLAN
installation, as described in NMS Integration Installation, page 2-18.
!" If the EMS-μLAN is being used in standalone mode, proceed to Installing EMS-μLAN,
page 2-4.
NOTE: For more information about operating modes, refer to

Chapter 1, Introduction.
2.2.1 Software Requirements

The EMS-μLAN requires the following software:
!" Windows 2000 operating system (U.S. English)
!" μLAN EMS Installation CD (for both standalone and integrated modes)
!" μLAN eNM Accessories CD (containing Orbix, eIMI, and Card View installation files,
which are required for eNM-integrated mode only)
!" μLAN NMS Accessories CD (containing Orbix 6.1 and Card View installation files,
which are required for NMS-integrated mode only)
In addition, the display must be configured to 1024x768 resolution and True Color.
2.3 Installation Required for eNM Integrated Mode

When using the EMS-μLAN in integrated mode under the eNM only, you must install two
applications, eIMI and Orbix, before proceeding. These applications are used for
communication between the EMS-μLAN and the NMS with which it is integrated.

BroadGate™ EMS-µLAN User's Manual Installation
2.3.1 Installing eIMI

"#To install eIMI:
1. Insert the Accessories CD. The main installation window is displayed.
NOTE: If the window does not display automatically, open

the eIMI directory on the CD and double-click the Setup.exe
file.
2. Click Install eIMI. An installation wizard is displayed.

3. Follow the instructions displayed in the wizard. Accept the default installation
directory (c:\eIMI) and click Next.
4. When asked whether to restart, click Yes. When the wizard has completed
installation, click Finish.
2.3.2 Installing Orbix (3.0.1)

"#To install Orbix 3.0.1:
1. Insert the Accessories CD. The main installation window is displayed.
2. Click Install ORBIX. An installation wizard is displayed.
NOTE: If the window does not display automatically, open

the ORBIX directory on the CD and double-click the
Setup.exe file.
3. Follow the instructions displayed in the wizard. Enter the license key when
prompted and click Next.
4. Accept the default installation directory (c:\Iona) and click Next.
5. Select Runtime install and click Next.
6. Accept the default folder (Accessories) and click Next.
NOTE: For information about configuring Orbix, refer to

Configuring Orbix Settings (for eNM Integration Only),
page 2-28.

2.4 Installing EMS-μLAN

EMS-μLAN installation requires the installation of several applications in addition to the
EMS itself. All of the required files are found on the μLAN EMS Installation CD, which can
be accessed via a single setup menu.
"#To begin installation:
!" Insert the Network Manager Installation CD. The following setup menu is displayed:
Figure 2-1: RTSetup window
Installation is performed in the order of the buttons displayed in the window, starting with
the left column, from top to bottom. A message is displayed if newer versions of any of the
files being installed already exist on the computer, enabling you to skip that part of the
installation.
As you proceed with the installation, read the messages that are displayed carefully. In
particular, it is important to restart the computer when asked to do so after installing selected
components.
NOTE: In the sections that follow, all windows requiring

setup changes are shown. For all other windows, accept the
default values and click Next or OK, as required.

2.4.1 Installing DAO SDK 3.5

The DAO SDK 3.5 application is used by the EMS-μLAN for database management.
NOTE: In most cases, this application will already be

installed.
"#To install DAO SDK 3.5:

1. In the NMS Install tab of the RTSetup window, click Install DAO SDK 3.5.
If the necessary files have already been installed on this computer, a message is
displayed and installation is aborted. Otherwise, an installation wizard is displayed.
2. Accept the license agreement and click Next. The Setup Type window is displayed.
Figure 2-2: DAO SDK – Setup Type window
3. In the Setup Type window, select Typical and click Next. The installation process
begins.

2.4.2 Installing MS-SQL Server 7.0

The EMS-μLAN uses Microsoft SQL Server 7.0 to store configuration information about
the μLAN NEs in the network, as well as alarm and performance information about these
NEs. For more information, refer to Appendix A, SQL Reference.
"#To install MS-SQL Server 7.0:
1. In the NMS Install tab of the RTSetup window, click Install MSSQL Server 7.0.
An installation wizard is displayed.
2. Follow the instructions displayed in the wizard. In the Select Install Method
window, select Local Install and click Next.
Figure 2-3: MS-SQL Server – Select Install Method window

3. In the Setup Type window, select Custom.

4. In the Destination Folder area, click the Browse button for program files and enter
C:\MSSQL7. Repeat this step for data files and click Next.
Figure 2-4: MS-SQL Server – Setup Type window
5. In the Select Components window, accept the default options and click Next.
Figure 2-5: MS-SQL Server – Select Components window
6. In the Character Set/Sort Order/Unicode Collation window, change the following

settings and click Next:
!" From the Character Set drop-down list, select 1252/ISO Character Set
(Default)
!" From the Sort Order drop-down list, select Dictionary order, case-sensitive

!" In the Unicode Collation area, select General Unicode from the Local
Identifier drop-down list and clear the Case-insensitive checkbox
Figure 2-6: MS-SQL Server – Character Set/Sort Order/Unicode Collation window
7. In the Services Accounts window, select Use the Local System account and click
Next.
Figure 2-7: MS-SQL Server – Services Accounts window

2.4.3 Installing the SNMP Service

The Simple Network Management Protocol SNMP (SNMP) is the protocol used for
managing μLAN units, receiving events and alarms as traps, and sending requests via MIBs.
"#To install the SNMP service:
1. In the NMS Install tab of the RTSetup window, click Install SNMP Service. An
installation wizard is displayed.
2. Follow the instructions displayed in the wizard. In the Windows Components
window, select Management and Monitoring Tools and click Next.
Figure 2-8: SNMP Service – Windows Components window
3. Follow the instructions displayed in the wizard. When asked whether to restart,
click Yes. When the wizard has completed installation, click Finish.
2.4.4 Installing Java Runtime Environment 2.0

The Java Runtime Environment is essential for installing and running the Java-based
applications of the EMS-μLAN, such as Card View, the Download and Backup Center,
LCT, JTerminal, and so on.

"#To install Java Runtime Environment 2.0:

1. In the NMS Install tab of the RTSetup window, click Install Java Runtime
Environment 2.0. An installation wizard is displayed.
2. Follow the instructions displayed in the wizard. When asked to select a browser,
select Microsoft Internet Explorer and click Next.
3. Complete the wizard. When asked whether to restart, click Yes. When the wizard
has completed installation, click Finish.
2.4.5 Installing the EMS-μLAN NMS Application

The following procedure installs the actual EMS-μLAN application.
"#To install the EMS-μLAN application:
1. In the NMS Install tab of the RTSetup window, click Install Network
Management. An installation wizard is displayed.
2. Follow the instructions displayed in the wizard. In the Setup Type window, select
SDH and click Next.
Figure 2-9: EMS-μLAN installation – selecting network type

3. In the next Setup Type window, select All types and click Next.
Figure 2-10: EMS-μLAN installation – selecting element type
4. In the Select Components window, click Working NMS and then click Next.
Figure 2-11: EMS-μLAN installation – Select Components window
This process may take several seconds.


2.4.6 Installing Java Card View Software

The following procedure describes how to install the Card View application, which is used
to manage individual μLAN NEs. For more information, refer to Chapter 6, Configuring and
Monitoring µLAN NEs.
NOTE: If a message is displayed during installation

indicating that selected files already exist, choose to
overwrite these files by selecting Yes to All.
"#To install the Card View application:

1. In the EMS Applications tab of the RTSetup window, click Install Java
CardView.
Figure 2-12: RTSetup window – EMS Applications tab

2. Follow the instructions displayed in the wizard. Accept the default directory path
and click Next.
3. In the Setup Type Window field, select Typical and click Next.
4. Accept the default directory and click Next. When the wizard has completed

2.4.7 Installing Log Viewer

The following procedure describes how to install the Log Viewer used by the EMS-μLAN.

"#To install the Log Viewer application:

1. In the EMS Applications tab of the RTSetup window, click Install Log viewer. An
installation wizard is displayed.
and click Next.
3. In the Type field, select Typical and click Next.
2.4.8 Installing Java Terminal

This application is used for first-time installation and as a debugging tool.

"#To install the Java Terminal application:

1. In the EMS Applications tab of the RTSetup window, click Install Java Terminal.
and click Next.
2.4.9 Installing Java Download

This application is used during the embedded upgrade.


"#To install the Java Download application:

1. In the EMS Applications tab of the RTSetup window, click Install Java
Download (IP or Opty only). An installation wizard is displayed.
and click Next.
2.4.10 Installing Active Alarm View

This application is used when using the LCT-µLAN craft terminal. For more information
about the LCT-µLAN, refer to LCT-µLAN Craft Terminal, in Chapter 1, Introduction.

"#To install the Active Alarm View application:

1. In the EMS Applications tab of the RTSetup window, click Install Active Alarm
View. An installation wizard is displayed.
and click Next.
2.4.11 Installing LCT-µLAN

The following procedure describes how to install the LCT-µLAN craft terminal, which is
used for installing and configuring µLAN NEs. For more information about the
LCT-µLAN, refer to LCT-µLAN Craft Terminal, in Chapter 1, Introduction.

"#To install the LCT-µLAN application:

1. In the EMS Applications tab of the RTSetup window, click Install LCT Manager.
and click Next.


5. Restart the computer.
2.4.12 VNC Installation and Configuration

The following procedure describes how to install the VNC emulation software, which
enables the Windows-based EMS-μLAN application to be operated at a Sun workstation
(typically running an NMS, such as eNM or eNM LightSoft). The software includes two
components, a server component installed on the PC management station and a client
component installed on the Sun workstation.
For more information, refer to Software Emulation, in Chapter 1, Introduction.
NOTE: The client component is installed using the same

script that installs the Card View application on the
workstation.
2.4.12.1 Installing the VNC server
The following procedure describes how to install the VNC server component on the PC used
as the EMS-μLAN management station. VNC software should be installed only when it was
not installed in a previous version.
If this component exists on the computer, a VNC icon is displayed in the Status Bar (next to
the clock).
"#To install the VNC server on the PC management station:

1. In the NMS install tab of the RTSetup window, click Explore CD. A navigation
window is displayed.
2. Navigate to the vnc_x86_win32 folder.
3. Open the winvnc subfolder and double-click the Setup.exe file. A message is
displayed, asking you to close any previous versions of VNC that might be running.
An installation wizard is then displayed.
4. Follow the instructions displayed in the wizard. When the wizard has completed

2.4.12.2 Configuring the VNC server
After installing the VNC server component, it must be configured. This includes configuring
the password entered from the Sun workstation to activate software emulation.
NOTE: For information about using software emulation,

refer to Operating the EMS-μLAN Remotely, in Chapter 3,
General Operating Instructions.
"#To configure the VNC server:

1. Select Start ! Programs ! VNC ! Run WinVNC (App Mode). The
WinVNC: Current User Properties window is displayed.
Figure 2-13: WinVNC: Current User Properties window
2. Select the Accept Socket Connections checkbox.

3. In the Display Number field, select the Auto checkbox.
4. In the Password field, enter eci_enm or eci_nms.
5. In the Update Handling area, select the Poll Full Screen checkbox.
6. Click OK to save the settings. Create a Desktop shortcut for VNC, and then add it
to the Startup folder (c:\Documents and Settings\All Users\Start
Menu\Programs).
NOTES: When VNC is launched, a small VNC icon is

displayed in the system tray. Right-click this icon and select
Properties to modify any VNC server configuration settings.
In version 2.2r2, the VNC window does not open
automatically. To invoke the VNC viewer on a Sun station,
open a UNIX window and type the following:
cd / opt/uLAN/vnc
vncviewer

2.4.13 Installing Tardis

This application uses the Simple Network Time Protocol (SNTP) to synchronize the date
and time among all the μLAN NEs in the network. Tardis software should be installed only
when it was not installed in the previous version. If this component exists on the computer, a
Tardis icon is displayed in the Status Bar (next to the clock).
"#To install Tardis:

1. In the NMS install tab of the RTSetup window, click Explore CD. A navigation
2. Navigate to the Tardis folder.
3. Double-click the tardis2000.exe file. An installation wizard is displayed.
4. Follow the instructions displayed in the wizard. Click Yes to launch the program.
When the wizard is complete, click Finish.
5. Restart the computer.
6. Create a Desktop shortcut for Tardis, and then add it to the Startup folder
(c:\Documents and Settings\All Users\Start Menu\Programs).
NOTE: For information about using Tardis and configuring

SNTP on each NE, refer to Setting the Network Time, in
Chapter 4, Building the Network.

2.5 NMS Integration Installation

For NMS installation, you must install software for Orbix 6.1 and MTNM Server. Together,
they implement the CORBA interface between the EMS-μLAN and the NMS.
2.5.1 Orbix 6.1 Installation and Configuration for an

NMS-integrated Network Manager
"#To install Orbix 6.1:
1. On the eNM station, select System ! Unix Window. The Terminal window is
displayed.
2. Type the following, pressing Enter after each line:
cd /etc
su
tcsh
textedit hosts
3. Enter the IP address and name of the PC management station. Save and close the
file.
4. Insert the NMS Accessories CD into the EMS-μLAN PC.
5. Follow the installation instructions and click Next.
6. Select the I accept the terms of the License Agreement radio button and click
Next.
Figure 2-14: Orbix 6.1 – License Agreement window

7. Change the default directory to C:\Program files\IONA_NEW, and click Next.
Figure 2-15: Orbix 6.1 – Choose Install Folder window
8. Select the In the Start Menu radio button and click Next.
Figure 2-16: Orbix 6.1 – Choose Shortcut Location window
9. Select the Enterprise Edition option and click Next.

10. In the next window that displays, select the Customized Runtime option and click
Next.

11. In the Environment Settings window, select the checkboxes for only those services
shown in Figure 2-17.
Figure 2-17: Orbix 6.1 – Environment Settings window 1
12. In the next window that displays, select only the Notification Service checkbox, as
shown in Figure 2-18, and then click Next.
Figure 2-18: Orbix 6.1 – Environment Settings window 2

13. Continue to click Next until the Install window is displayed.

14. Click Install and wait for the installation to complete.
15. Click Finish and reset the PC.
2.5.1.1 Orbix 6.1 configuration
"#To configure Orbix 6.1:

1. Copy the Orbix_6.x_Win_license.txt file from the License_ORBIX6 directory on
the NMS Accessories CD to C:\Program Files\IONA_NEW\asp\6.1\etc.
2. Select Start ! ORBIX6.1 ! ORBIX Configuration. The License window is
displayed.
Figure 2-19: License window
3. Browse to the C:\Program Files\IONA_NEW\asp\6.1\etc directory, select the

Orbix_6.x_Win_license.txt file, and click OK.
4. In the window that displays, click the Create button.
5. In the next window that displays, set the domain name to the default domain and
click Next.
6. In the next window that displays, select the All selected services launched on
machine startup option and click Next.
7. Continue to click Next until reaching the final window.
8. Click Finish to complete the installation.
9. Reboot the PC.

2.5.1.2 Server installation and configuration
This section descibes the procedures for installing and configuring the MTNM server.
"#To install and configure the MTNM server:
1. From the Administrative Tools Folder in the Control Panel, double-click the
Services icon.
2. In the Services window, verify that there are six IT_IONA services in started mode,
as shown in the following figure.
Figure 2-20: Services window
3. Insert the EMS-μLAN installation CD and click Install MTNM Server in the
Extensions tab.
Figure 2-21: RTSetup window – Extensions tab

4. Click Finish to complete the installation.

5. In the C:\EMSuLAN folder, right-click the context.txt file and select Properties.
6. Deselect the Read-only option and close the Properties window.
7. Open the context.txt file and edit the EMS-μLAN registry name as follows:
Set the ID of the specific EMS (marked in red in the following figure). The value
should be greater than 10. If there are multiple EMS-μLANs managed under same
NMS, each EMS must be configured with a different ID number.
Figure 2-22: context.txt – Notepad window
8. Run the MTNM server by selecting Start ! Network Management.
2.6 Configuration Procedures

After completing installation, you must configure the following settings:
!" SNMP settings, page 2-23
!" MTU settings, page 2-25
!" Additional network managers, page 2-26
!" Network management settings, page 2-26
!" Card View operation location, page 2-28
!" Registry IP address settings, page 2-28
!" Orbix settings (for eNM integration only), page 2-28
2.6.1 Configuring SNMP Settings

SNMP parameters are configured via the Network Management applet, which is found in
the Windows Control Panel. This applet can be operated only by technicians with SuperUser
privileges (typically ECI Telecom technicians).
NOTE: Incorrect modifications may prevent the proper

operation of the EMS-µLAN application in your
environment.

"#To configure SNMP settings:

1. Select Start ! Settings ! Control Panel ! Network Management. The
Network Management window is displayed.
Figure 2-23: Network Management Configuration tab
2. To prepare the SNMP parameters needed in your environment, configure the

following parameters:
Table 2-2: SNMP parameters
Parameter Description
SNMP Get/Set Determines the maximum time (in seconds) the
Timeout EMS-µLAN station will wait for a response to a Get
command, or for an acknowledge to a Set command.
The default value is 7 seconds. You can specify a different
time-out interval in accordance with the expected delay in
your network. Consult ECI Telecom if you want to change
the default value.
Public SNMP Specifies the public SNMP community name. Community
name names are case-sensitive. The default name is public.
Private SNMP Specifies the private SNMP community name. The default
name name is private.
CardView DB Specifies the user name for accessing the database
username containing alarm and performance data.
CardView DB Specifies the password for accessing the database
password containing alarm and performance data.
TNG DB Specifies the user name for accessing the database
username containing µLAN configuration data.
TNG DB Specifies the password for accessing the database
password containing µLAN configuration data.
3. Click Apply to save the new settings while leaving the window open, or OK to save
the settings and close the window.

2.6.2 Configuring MTU Settings

For selected µLAN configurations that require DCC management via SYNCOM products
(SDM-1/4/16), it is necessary to set the maximum transmission unit (MTU) in the
management station PC, the eNM, and the µLAN NEs to a value of 500 bytes.
2.6.2.1 Configuring the MTU on the management station
Before configuring the MTU settings on the management station PC, determine which
interface requires configuration.
"#To determine which PC interface requires MTU configuration:
1. Select Start ! Run. The Run window is displayed.
2. Type regedit and click OK. The Registry Editor is displayed.
3. From the tree displayed in the left pane, select
HKEY_LOCAL_MACHINE/Software/Microsoft/Windows
NT/CurrentVersion/Network cards.
When Network cards is selected, the Service Name field in the right pane displays
the number of the interface requiring MTU configuration.
"#To configure MTU settings on the management station:
1. From the Registry Editor tree, select HKEY_LOCAL_MACHINE/System/
CurrentControlSet/Services/Tcpip/Parameters/Interfaces.
2. Right-click the interface to be configured and select New ! DWORD Value from
the pop-up menu. Enter MTU as the name of the key.
3. Double-click the MTU key. The Edit DWORD Value window is displayed.
Figure 2-24: Edit DWORD Value window
4. In the Value Data field, enter 500.

5. In the Base field, select Decimal.
6. Click OK to save your settings.

2.6.2.2 Configuring the MTU for the eNM/NMS
The following procedure describes how to configure the MTU on the Sun workstation
running the eNM/NMS.
"#To configure MTU settings for the eNM/NMS:
1. From the eNM, select System ! Unix Window. The Terminal window is
displayed.
su
tcsh
SetMTU
3. Select the relevant interface, and type y in response to the two questions displayed.
4. Close the Terminal window.
2.6.2.3 Configuring the MTU in µLAN NEs
Use the LCT-µLAN craft terminal to configure the MTU in each µLAN NE to 500 bytes.
For more information, refer to the BroadGate µLAN Installation, Operation and
Maintenance (IOM) Manual.
2.6.3 Configuring Additional Network Managers

The EMS-µLAN installation procedure automatically confers NMS SuperUser privileges on
the Administrator, enabling all operations to be performed. If other users will be operating
the NMS, their names and passwords must be configured as well.

"#To configure additional network managers:

1. Select Start ! Settings ! Control Panel ! Administrative Tools !
Computer Management. The Computer Management window is displayed.
2. From the tree in the left pane, expand Local Users and Groups.
3. Right-click Users and select New User from the pop-up menu. The New User
Figure 2-25: New User window
4. Enter a user name and password in the fields provided (for example, ECI) and then
re-enter the password to confirm it.
5. Clear the User must change password at next logon checkbox.
6. Select the Password never expires checkbox.
7. Click Create. The new user is displayed in the right pane of the Computer
Management window.
Figure 2-26: Computer Management window

8. Right-click the new user and select Properties from the pop-up menu. The
Properties window is displayed.
9. Select the Member of tab and click Add. The Select Groups window is displayed.
10. Select the required group from the list displayed and click Add. The new user can
be a member of one of the following groups:
!" NMS SuperUser – user with full privileges
!" NMS Modifier – user with viewing and editing privileges
!" NMS Viewer – user with viewing privileges only
11. Click OK. The new user is added to the selected group.
12. Repeat steps 3 through 11 to add more users, if required.
NOTE: It is recommended to log off and then log on as the

new user before beginning network management operations.
2.6.4 Configuring Card View Operation Location

The registry in the management station PC must be configured with the correct IP address
for running the Card View application. For example, if the Card View application will be
operated via the eNM/NMS workstation in integrated mode, the IP address of the
workstation is required.
"#To configure the IP address in the management station:
1. Select Start ! Run. The Run window is displayed.
2. Type regedit and click OK. The Registry Editor is displayed.
3. From the tree displayed in the left pane, select
HKEY_LOCAL_MACHINE/Software/NMS/CardView Client.
4. In the right pane, double-click Host. In the pop-up window displayed, enter one of
the following values for the IP address:
!" For integrated mode – enter the eNM/NMS workstation IP address
!" For standalone mode – enter 127.0.0.1 (local host)
5. Click OK.
2.6.5 Configuring Orbix Settings (for eNM Integration Only)

Orbix must be properly configured in order to operate the EMS-µLAN in integrated mode
with the eNM . This includes entering the correct IP addresses to enable communication
between the management station and the eNM workstation.

"#To configure Orbix:

1. On the management station, navigate to c:\WinNT\system32\drivers\etc\ and open
the hosts file with Notepad.
2. Enter the IP address and name of the eNM station in the fields provided. Save and
close the file.
NOTE: If you do not know the log host name of the eNM
station, open a UNIX window on the station and type
hostname to display this information.
3. On the eNM station, select System ! Unix Window. The Terminal window is
displayed.
cd /etc
su
tcsh
textedit hosts
5. Enter the IP address and name of the PC management station. Save and close the
file.
6. Return to the management station and navigate to c:\Iona\config\, and open the
orbixnames3.cfg file with Notepad.
7. In the IT_NAMES_SERVER_HOST variable, change the existing host name to
the name of the eNM workstation. Save and close the file.
8. Open a DOS window and type: cd Iona followed by cd bin.
9. Type the following commands, pressing Enter after each one:
start orbixd
(A new DOS window is displayed. Do not close it, but continue typing in the
previous window.)
putit RNM -persistent
putit RNM "C:\EMSuLAN\imiRNMClient.exe -t EMS_uLAN
-n RNM"
chmodit RNM i+all
chmodit RNM l+all
10. Create a Desktop shortcut to imiRNMclient.exe.
11. Right-click the shortcut and select Properties from the pop-up menu.
12. In the Target field, enter the following path and click OK:
C:\EMSuLAN\imiRNMClient.exe -t EMS_uLAN -n RNM
13. Create a Desktop shortcut to ORBIXD (found in c:\Iona\bin).

14. Copy the two shortcuts to the Startup folder (c:\Documents and Settings\All
Users\Start Menu\Programs).
15. Double-click both shortcuts to start the applications.
NOTE: Verify the Orbix installation on the eNM workstation

by entering the following command: pkginfo -l ORBIX.
If the application has been installed successfully, its
parameters are displayed, including the version number.
2.7 Software Installation on an eNM Workstation

After finishing the necessary configuration procedures, the following procedures should be
performed on the Sun workstation running the eNM or eNM LightSoft:
!" Installing the eNM/NMS Fix Disk, below
!" Installing µLAN Software, page 2-30
!" Configuring the EMS-µLAN as a Slave Manager, page 2-32
NOTE: These procedures can be skipped if the EMS-µLAN

will be operated only in standalone mode.
2.7.1 Installing the eNM Fix Disk

The following patches on the Accessories CD must be installed before installing the
software required to run the EMS-µLAN in integrated mode:
!" Patch number SY0860-13 for the eNM Manager
"#To install the fix disk:
1. Activate the eNM
2. Insert the µLAN eNM Accessories CD.
3. Select System ! Unix Window. The Terminal window is displayed.
4. Type the following commands, pressing Enter after each line:
su
tcsh
FixAdd -fix [fix number]
A confirmation message is displayed when installation is complete.
2.7.2 Installing µLAN Software

"#To install the µLAN software on the Sun workstation:
!" Activate the eNM or NMS (if using eNM LightSoft as the NMS).

2.7.3 Package Installation for an eNM-integrated Manager

Package installation for an eNM-integrated manager installs Java, the Card View, the
Trailer, and the VNC client on the Sun station.
"#To perform package installation for an eNM-integrated manager:
1. Activate the eNM.
2. Insert the µLAN eNM Accessories CD into the drive.
3. Open a UNIX window and type the following:
su
tcsh
cd /cdrom/cdrom0/
pkgadd –d .
The following output is displayed:
The following packages are available:

1 ECILulancv EMS-uLAN Card View
(sparc) 22.02
Select package(s) you wish to process
(or 'all' to processall packages).
(default: all) [?,??,q]:
4. Press Enter. The following is displayed:

The selected base directory </opt/uLAN> must exist
before installation is attempted.
Do you want this directory created now [y,n,?,q]

5. Press y to approve creation of the directory. The following is displayed:
This package contains scripts which will be executed with
super-user permission during the process of installing
this package.
Do you want to continue with the installation of

<ECILulancv> [y,n,?]
6. Press y to continue. The following is displayed:

(sparc) 22.02
Select package(s) you wish to process or 'all' to

process all packages). (default: all) [?,??,q]:

7. Press q to end the installation.

8. Reboot the station.
NOTE: The field engineer should perform the µLAN

software installation routine after each eNM software
upgrade.
2.7.4 Configuring the EMS-µLAN as a Slave Manager

In order to run the EMS-µLAN in integrated mode, it must first be configured as a Slave
Manager in either the eNM or eNM LightSoft.
"#To configure the Slave Manager for the EMS-µLAN:
1. Run Orbix and imiRNMClient on the management station.
2. On the eNM workstation, select Configuration ! Slave Manager ! Create
Slave Manager. The Create Slave Manager window is displayed.
3. Enter the following values, and then click OK:
!" In the Registry Name field, enter RNM.
!" In the Title field, enter uLAN.
!" From the Slave Types drop-down list, select EMS_uLAN.
4. To test the Slave Manager, select Configuration ! Slave Manager ! Slave
Manager List.
NOTE: If the Slave Manager is disconnected, refer to

Troubleshooting the Slave Manager, page 2-33.
5. Select Configuration ! Element ! Create EME. Enter the IP address and name
of the NE, and select uLAN-STM1 as the element type.
6. Ping the new NE and verify that it responds.
7. Open the Card View for the NE.
NOTE: If the Card View does not open, kill the Java process
and reinstall the µLAN software, as described on page 2-30.
8. Close the Card View and delete the NE.

9. Delete the Slave Manager.

2.7.4.1 Troubleshooting the Slave Manager
Perform the following tests if you are unable to verify the installation performed on the
eNM workstation via the Slave Manager.
"#To troubleshoot the Slave Manager:
1. Check the response to ping commands sent to the name (not the IP address) of the
eNM workstation and the PC management station.
2. Verify that Orbix and imiRNMClient are running on the management station.
3. Verify the accuracy of the information displayed in the Orbix DOS window, as
follows:
The first 3 lines represent the connection of the NS (name server):
[orbixd: Server "IT_daemon" is now available to the
network ]
[ Configuration TCP/1570/Orbix-XDR ]
[orbixd: New Connection (eyal,RNM,*,Administrator,pid=
1196,optimised) ]
Lines 4 and 5 represent the PC imiRNMClient connection:

[orbixd: Registering Persistent Server RNM(pid = 1196) ]
[orbixd: Dynamically assigning internet port 1571 ]
Lines 5 and 6 represent eNM connections:
[orbixd: New Connection (sdhfe38,EMICSrv,*,enm,pid=747)
]
[orbixd: Processing Server Details request :
RNM/0/registerClient(enm) ]
4. Check the registration connection on the NS (EMICSrv) for the eNM and RNM. To
check whether Orbix is connected to the eNM, open a UNIX window and type
pingit -h [host name].
5. Check whether the name of the eNM workstation is the same name defined in
c:\Iona\config\orbixnames3.cfg and c:\WinNT\system32\drivers\etc\hosts on the
management station.
6. If Orbix is not connected, open a DOS window on the management station and type
lsns followed by lsns eIMI. Verify that the name of the station registered on
the NS of the displayed PC is correct. If there is a connection problem, a message
indicating the type of problem is displayed.

2.7.5 Package Installation for an NMS-integrated Manager

Package installation for an NMS-integrated manager installs Java, Card View, Trail
Duplicator, and the VNC client on the Sun station.
"#To perform package installation for an NMS-integrated manager:
1. Activate the NMS.
2. Insert the µLAN NMS Accessories CD into the drive.
3. Open the UNIX window and type the following:
su
tcsh
cd /cdrom/cdrom0/
pkgadd –d .
The following is displayed:

(sparc) 22.02
Select package(s) you wish to process
(or 'all' to processall packages).
(default: all) [?,??,q]:
4. Press Enter. The following is displayed:

The selected base directory </opt/uLAN> must exist
before installation is attempted.
Do you want this directory created now [y,n,?,q]

5. Press y to approve directory creation. The following is displayed:
This package contains scripts which will be executed with
super-user permission during the process of installing
this package.
Do you want to continue with the installation of

<ECILulancv> [y,n,?]
6. Press y to continue. The following is displayed:

(sparc) 22.02
Select package(s) you wish to process (or 'all' to

process
all packages). (default: all) [?,??,q]:
7. Press q to end the installation.

8. Reboot the station.

2.7.6 Configuring the EMS-µLAN as a Managed EMS Under an

NMS
The EMS-µLAN can be managed under NMS server and client.
The last updated .ini files must be installed in the NMS. To verify, contact ECI Telecom
Customer Support.
In order to run the EMS-µLAN in integrated mode under the NMS, it must first be
configured as a managed EMS in eNM LightSoft.
"#To configure the EMS-µLAN as a managed EMS in eNM LightSoft:
1. From the EMS-µLAN, select Force Register in the File menu.
Figure 2-27: MTNM server window
2. In the Force registration parameters window, enter the IP of the NMS and click OK.
Figure 2-28: Force registration parameters window

The EMS-µLAN appears showing the registry name in the Create EMS list on the
NMS.
3. On the NMS workstation, select Configuration ! Create ! EMS. The Create
EMS window is displayed.
Figure 2-29: Create EMS window
4. Select the EMS-µLAN from the EMS list and then enter the following values:
!" In the Session Login field, enter LSNuser.
!" In the Session Password field, enter 1.
5. Click OK.
2.8 Uninstalling the EMS-µLAN

The procedure for uninstalling the EMS-µLAN is dependent on the version installed
(version 1.2, 2.1, or 2.2).
IMPORTANT NOTE: Be aware that the entire database used

by the application is located under the MSSQL folder.
Uninstalling the Microsoft SQL Server 7 software or deleting
this folder causes the loss of this database.

2.8.1 Uninstall Preliminary Actions

Be sure to do the following before performing the uninstall process:
!" Stop/close all the applications that are running on the computer
!" Stop the MssqlServer7 server
"#To stop the MssqlServer7:
1. Right-click the MssqlServer7 icon at the lower-right side of the screen (marked in
red in the following figure).
2. Select Stop MssqlServer7 in the pop-up menu that appears.
Figure 2-30: MssqlServer7 pop-up menu
3. In the window that displays, click Yes to stop the SQL server.
Figure 2-31: SQL Server Service Manager window
The MssqlServer7 icon now shows as red in the Status Bar.

4. Right-click the icon and select Exit.
"#To uninstall the EMS-µLAN version 1.2:
1. On the management station, select Start ! Settings ! Control Panel !
Add/Remove Programs. The list of installed programs is displayed.
2. Select and uninstall the programs one by one in the following order:
!" Network Management
!" Card View

!" RT Serial Terminal

!" RT FTP Download
!" MS SQL Server (only if required; delete the MSSQL folder only after
completing the uninstall procedure)
3. Reboot the PC.
4. Delete the RadioTel folder.
!" NMS
!" LCT Manager
!" Active Alarms View
!" FTP Download Center
!" JTerminal
!" Card View
3. Reboot the PC.
4. Delete the EMS-µLAN folder.


!" NMS
!" LCT Manager
!" Current Alarms View
!" FTP Download Center
!" JTerminal
!" Card View
3. Reboot the PC.
4. Delete the EMS-µLAN folder.


3
General Operating Instructions
NOTE: Unless otherwise specified, the instructions in this
manual refer to the standalone mode of operation only.
For additional information regarding integrated mode, refer
to Chapter 1, Introduction.
3.1 Preparation for First-time Operation

The EMS-μLAN station is typically supplied ready for operation. If you need assistance
preparing the EMS-μLAN station for your application, contact ECI Telecom's Technical
Support department.
!"To prepare an EMS-μLAN station for first-time operation:
1. Connect the EMS-μLAN station to the µLAN system that will serve as the gateway
NE. Refer to Management Connections, page 3-2 for connection instructions.
2. Define the default gateway, as described on page 3-2.
3. Start the EMS-μLAN application, as described in Starting the Topology Browser,
page 3-8.
4. Obtain the list of management IP addresses for all the elements in the managed
network. Use this information to define the network topology by adding the
necessary elements and then defining the connections (trails) between the various
elements. For instructions, refer to Chapter 4, Building the Network.
NOTE: All µLAN NEs must be preconfigured for operation.

This configuration is performed by qualified and authorized
technical support staff, using the LCT-µLAN local craft
terminal connected directly to the LCT port on the front panel
of each µLAN system. Among other parameters, it is
necessary to select your own SNMP community. All the NEs
managed through a given management connection must use
the same SNMP community. Make sure you know the
required community name.
For more information about configuring the NEs, refer to the
BroadGate µLAN Installation, Operation and Maintenance
(IOM) Manual.

General Operating Instructions BroadGate™ EMS-µLAN User's Manual
3.1.1 Management Connections

The EMS-μLAN station is generally connected to the management port, designated MNG,
of one µLAN system in the network. This µLAN system then serves as the gateway NE,
which enables the EMS-μLAN station to manage the other elements in the network.
In most cases, both the EMS-μLAN station and the gateway µLAN system connect to a
local LAN. Therefore, the connections are usually made through a 10/100BaseT Ethernet
hub or switch.
3.1.2 Defining the Default Gateway

After physically connecting the EMS-μLAN management station to a µLAN NE in the
network defined as a gateway, you must define this NE as the default gateway in the station.
This is particularly important when the µLAN units being managed are located in multiple
subnetworks.
For more information about defining a default gateway, refer to the BroadGate µLAN
3.1.3 Configuring Gateway Redundancy

When more than one µLAN NE has been defined as a gateway, the Default Gateway
Configuration tool enables you to define which NE acts as the main gateway for the µLAN
network and which NE acts as the protection gateway. Having this gateway redundancy
enables the network to perform automatic failover to the protection gateway if the main
gateway goes down, and seamlessly continue management of the µLAN network.

BroadGate™ EMS-µLAN User's Manual General Operating Instructions
!"To configure gateway redundancy:

1. Select Start # Network Management # Default Gateway Configuration. The
Configure Default Gateway window is displayed.
Figure 3-1: Configure Default Gateway window
The upper pane of the Configure Default Gateway window displays information
about the main and reserve gateways for the µLAN network. The lower pane
displays messages about any failovers between the two gateways that have been
performed. Messages are displayed in reverse chronological order, with the newest
message always displayed at the top of the list.
2. Click Add Item. The Add Item window is displayed.
Figure 3-2: Add Item window

3. Enter the following IP address information:

!" Destination – the DCC IP for the µLAN network. This is the IP used to transmit
management information over the optical fibers connecting each µLAN NE.
!" Mask – the net mask for the DCC IP.
!" Gateway – the LAN IP used by the main gateway NE to connect to the
EMS-µLAN management station.
!" Reserved Gateway – the LAN IP used by the reserved gateway NE to connect
to the EMS-µLAN management station.
4. Click Add. The information is added to the upper pane of the Configure Default
Gateway window. After a few seconds, a message should appear in the State
column, indicating a successful ping to the main gateway. A similar message,
including the date and time of the ping, is displayed in the lower pane.
Figure 3-3: Successful ping of main gateway
The system continues to ping the main gateway at regular intervals. If the main
gateway goes down for any reason, the system performs automatic failover to the
reserved gateway.

The State column indicates which gateway (main or reserved) is acting as the active
gateway that is managing the network. A message is displayed in the lower pane
whenever a switch between gateways occurs.
Figure 3-4: Failover to reserved gateway
NOTES: To edit the gateway information displayed in the

upper pane, select it and click Edit Item. To delete the
gateway information, select it and click Remove Item.
CAUTION: Minimize the Configure Default Gateway window

and leave it running whenever the EMS-µLAN is running.
Closing the window stops the gateway redundancy task, which
removes gateway protection from the network.
3.1.4 Remotely Changing DCC Mode and IPs

If μLAN NEs have been installed on a mixed network with other ECI devices, such as
XDM® or SYNCOM shelves, the DCC mode and IP addresses for each μLAN NE must be
reconfigured after upgrading to software version 2.1r1 or later. This is required to configure
the NEs with a new DCC protocol that enables interoperability with the management traffic
of other ECI equipment. The necessary changes in each μLAN NE can be performed
remotely via Telnet from the management station, eliminating the need to configure each
NE locally with the LCT-μLAN.

CAUTION: Be sure to start this procedure from the NE located

furthest from the gateway. Starting from the gateway will cause
the gateway to lose its connection with the rest of the ring,
making it impossible to reach the other NEs via Telnet.
!"To change the roles and IPs of each μLAN NE remotely:

1. From the management station, open a Telnet session for a selected NE.
NOTE: This can be performed directly from the Topology

Browser, as described in Element Menu, in Chapter 4,
Building the Network.
2. Type dccc and press Enter. The current DCC parameters for the selected NE are
displayed.
Dcc parameters :
----------------
1) DCC IP = 192.9.80.110
DCC NETWORK MASK = 255.255.255.0
DCC NETWORK BROADCAST IP = 192.9.80.255
2) NE is in DCC mode
to change (1-2) to exit (0) [0]
An NE can be assigned one of two roles:
!" Gateway – the NE connects via Ethernet to the management station for the
purpose of managing the other NEs in the network
!" DCC – the NE is managed by a Gateway NE via an optical connection
3. Change the NE type by doing one of the following:
!" To change from DCC to Gateway, type 2 and press Enter. A message is
displayed asking whether the NE is a Gateway. Type y and press Enter.
!" To change from Gateway to DCC, type 2 and press Enter. A message is
displayed asking whether the NE is a Gateway. Type n and press Enter.
4. When asked whether to view the DCC parameters again, type y and press Enter.
The updated parameters are displayed.

5. Change the DCC IP of the NE, as follows:

!" Type 1 and press Enter.
!" Type the IP address used for DCC management traffic between NEs and press
Enter.
!" Type a new net mask, or leave the default entry as is, and press Enter.
!" When asked whether to view the DCC parameters again, type y and press Enter.
6. Type 0 to exit.
7. Type setparam and press Enter. The current NE configuration is displayed.
8. Configure byte 10 with the value required for the NE's role, as follows:
!" Type 10 to modify the value of byte 10 and press Enter.
!" Type 1 (if the NE has been configured for Gateway mode) or 7 (if the NE has
been configured for DCC mode), and press Enter.
!" When asked whether to modify other bytes, type n.
!" When asked whether to view the NE parameters again, type y and press Enter.
9. Configure the LAN IP used to connect gateway NEs to the EMS-μLAN
management station, as follows:
!" Type the LAN IP address:
– For Gateway NEs, enter the address used to connect via Ethernet to the
management station.
– For DCC-only NEs, enter 1.1.1.1 as a dummy address.

!" Type a new net mask, if required, and press Enter.
10. Type hr to reset the NE.
11. Close the Telnet session.
12. Repeat steps 1 through 11 for the other µLAN NEs in the network.
13. Update the IP addresses for each µLAN NE in the Topology Browser, as described
in Redefining an NE, in Chapter 4, Building the Network.
14. Update the routing table for the µLAN NEs in the eNM.

3.1.5 Starting the Topology Browser

When Windows 2000 is initialized, a series of service programs are automatically initiated
as well. These service programs, which operate transparently in the background, perform
vital system functions, as described in Chapter 9, Additional Services and Tools. In
addition, the EMS-μLAN station is supplied with a set of user-operated applications, which
are used to configure, maintain, and troubleshoot the network. The main application is the
network Topology Browser, which can be used to launch most of the other user-operated
applications.
The Topology Browser is activated either via the Start menu, or by double-clicking the
desktop icon. You will see the Topology Browser window, as described in Chapter 4,
Building the Network. The Trail Manager (Chapter 5, Building Trails), Card View
(Chapter 6, Configuring and Monitoring µLAN NEs and Chapter 7, Configuring and
Monitoring Ethernet Services), and Alarm and PM Viewer (Chapter 8, Using the Alarm and
PM Viewer) are all accessed from the Topology Browser.
3.2 General Operating Procedures

This section provides general operating procedures, applicable to all the activities that can
be performed by means of the EMS-μLAN application.
The EMS-μLAN uses the standard operating procedures and conventions applicable to
Windows 2000 workstations.
3.2.1 Basic Operations

!" To select an item/object, click it once with the main mouse button. The selected object
is identifiable by its appearance (for example, a colored frame or changed shading).
!" The currently selected object is automatically deselected after selecting another object.
!" The EMS-μLAN application uses drop-down menus:
!" To display a top-level menu, click the menu name displayed in the menu bar. For
certain objects, you can also display a pop-up menu by right-clicking the mouse on
the desired object.
!" A selection bar indicates the currently selected menu item.
!" Menu items that cannot be selected appear in gray.
!" Menu items that are used to access submenus are marked by an arrow (#). To
display the submenu, click the corresponding item name.
!" The following operations are available in dialog boxes:
!" Selections are entered either by clicking buttons, by selecting items from drop-down
lists, or by typing in the desired data in fields that support free-text entries.
!" Fields or controls that cannot be modified appear in gray.

!" After making changes in a dialog box, you can either click Cancel to quit without
any change, or click OK or Apply to confirm the changes.
!" For confirmation boxes, click OK or Yes (as applicable) to confirm, or Cancel to
cancel the operation.
!" If the target element does not confirm the requested operation before the time-out
interval, you will be notified by a pop-up information box.
!" To close windows that are used only for display of data, click Close.
In addition, some windows include a Refresh button, which is used to send a command to
retrieve again the information displayed in that window, without closing the window.
3.2.2 Topology Management Modes

The EMS-μLAN station system has two modes for managing the network topology:
!" Run mode – in this mode, the EMS-μLAN station allows you to manage an existing
network, but not to change the network topology
!" Design mode – this mode enables you to change the network topology, for example,
adding/removing NEs and links
For more information about these management modes, refer to Run Mode and Design
Mode, in Chapter 4, Building the Network.
3.3 Operating the EMS-μLAN Remotely

The Windows-based EMS-μLAN application can be run remotely over Sun workstations
using software emulation. This makes use of two components – a server component running
on the EMS-μLAN management station and a client component running on the Sun
workstation. Software emulation enables an eNM or eNM LightSoft™ operator to remotely
access all the functionality of the EMS-μLAN as if it were in standalone mode, including
components not normally accessible in integrated mode, such as the Trail Manager, the
Network Resolution Tool and the Alarm and PM Viewer. In addition, it enables you to
easily view and filter current alarms in the μLAN network without having to resort to the
Alarm Log inside the NMS. For more information, refer to Software Emulation, in
To operate software emulation, you must first invoke the server component installed on the
management station. After the server is running, the client component can be invoked on the
Sun workstation.

!"To operate software emulation:

1. On the management station, select Start # Programs # VNC # Run WinVNC
(App Mode). The Current User Properties window is displayed.
Figure 3-5: WinVNC: Current User Properties window
2. Enter a password in the field provided and click OK. An icon is displayed in the
system tray to indicate that the server component is running. You can now invoke
software emulation on the Sun workstation.
3. On the Sun workstation, locate the serverDialog window for accessing software
emulation. If this window is not visible, do the following:
!" Open a UNIX window. (From the eNM, this is done by selecting System #
Unix Window.
!" Type cd /sdh_home/eNM/EMSuLAN/vnc/ and then press Enter.
!" Type vncviewer and press Enter. The serverDialog window is displayed.
Figure 3-6: serverDialog window

4. Enter the name or IP address of the management station on which the server
component is installed and press Enter. The serverDialog window displays a
prompt for entering a password.
5. Enter the password defined on the server in step 2 and press Enter. A message is
displayed in the Terminal window, indicating whether authentication has succeeded
or failed. If authentication succeeds, the Windows desktop of the management
station is displayed on the Sun workstation enabling you to access the full
functionality of the EMS-μLAN.
3.4 Security
The EMS-μLAN uses a security system based on Windows 2000 User Manager. There are
three levels of users:
!" Viewer – can only view information; cannot make any changes
!" Modifier – can make any change, with the exception of accessing the Download Center
and the Control Panel applet
!" Super User – can make any change, including accessing the Download Center and the
Control Panel applet
3.5 EMS-μLAN About Window

The EMS-μLAN About window displays details about the current management software in
use, such as the version number and date, for the different application modules (Card View,
Trail Manager, and so on).
Figure 3-7: Card View About window

3.6 EMS-μLAN Workflow

The following diagram describes a typical workflow for using EMS-μLAN to manage
BroadGate μLAN elements:
Figure 3-8: EMS-μLAN workflow
!" Step 1: Building the Network

Use the Topology Browser to create NEs and links, as described in Chapter 4, Building
the Network.
!" Step 2: Building Trails
Use the Trail Manager to define new E1, E3, and Ethernet trails, as described in
Chapter 5, Building Trails. (Defining trails via Card View is described in Chapter 6,
Configuring and Monitoring μLAN NEs.)
!" Step 3: Configuring and Monitoring μLAN NEs
Use the Card View window and the View Details window to view general, maintenance,
and performance information for each subsystem in the selected μLAN. You can also
configure trace IDs and the timing source used by the Main Unit (MU) card in the unit.
In addition, you can use the Card View window to define cross-connections within an
NE as part of a larger trail. These procedures are described in Chapter 6, Configuring
and Monitoring μLAN NEs.

!" Step 4: Configuring Ethernet Services

Use the Card View window to define the physical LAN port configuration, VLAN line
tables, and RSTP protection. You can also use the Card View to view Ethernet port
statistics. These procedures are described in Chapter 7, Configuring and Monitoring
Ethernet Services.
!" Step 5: Managing the Network
Once the network is operational, you can perform ongoing operations and maintenance
activities, and use the Alarm and PM Viewer to manage μLAN alarms and performance
information. For more details, refer to Chapter 6, Configuring and Monitoring μLAN
NEs, and Chapter 8, Using the Alarm and PM Viewer.


4
Building the Network
4.1 Overview
The first step when managing NEs with the EMS-µLAN station is to build the network. This
includes creating and defining NEs, as well as creating and defining the links that connect
them, via the Topology Browser.
4.2 Topology Browser

The Topology Browser is the starting point for all the management functions that can be
performed by EMS-µLAN station operators. In addition, it provides valuable network status
information at a glance.
The Topology Browser can be operated in one of two modes:
!" Run Mode – used mainly to monitor the status of the network, as described in Run
Mode, page 4-2.
!" Design Mode – used to define and modify the network topology, as described in Design
Mode, page 4-10.
When using the Topology Browser, the following functionality applies:
!" Each NE is indicated by an icon that represents its function. The element name is
displayed under the icon (the name is usually abbreviated, to save space on the display).
!" The element icon color indicates its status, as explained in Run Mode Main Window,
page 4-2.
!" All NEs can be connected by links.
!" A link always connects two, and only two, NEs. Unconnected elements float freely in
the topology display area and their color is always black, unless they have direct
management connections.
!" Each link is represented by two straight optical lines – one representing the eastbound
traffic flow, and the other representing the westbound traffic flow (see East and west
conventions, page 4-7).
!" To help identify the traffic flow directions, each end of a link is marked with the
appropriate label (W for West, E for East). In addition, the flow directions are explained
by legends displayed at the bottom of the window.

Building the Network BroadGate™ EMS-µLAN User's Manual
Holding the cursor over an NE for a few seconds displays a tooltip label with key details,
including the logical name of the element, its management IP address, and its current status
(in accordance with the color of the icon).
4.3 Starting the Network Topology Browser

The Topology Browser is activated either by selecting Start ! Network Management !
Topology Browser, or by double-clicking the Topology Browser icon on your desktop.
Figure 4-1: Topology Browser icon
4.4 Run Mode

Run mode is used mainly to monitor the status of the network, as displayed by the element
colors. Using the information displayed in the Topology Browser, you can analyze alarm
conditions indicated by changes in the element color, and identify problems.
When responding to alarm conditions, you can:
!" Display alarms and performance data using the Views menu
!" Analyze the technical status of a selected element, using the Card View functions (see
Chapter 6, Configuring and Monitoring μLAN NEs and Chapter 7, Configuring and
Monitoring Ethernet Services)
!" Reset suspect NEs and force changes in traffic flow by simulating fault conditions (AIS
and RDI) at the card level, using the Card View maintenance functions (see Chapter 6,
Configuring and Monitoring μLAN NEs and Chapter 7, Configuring and Monitoring
Ethernet Services)
4.4.1 Run Mode Main Window

When the Topology Browser is started, it enters Run mode and displays the main window,
which is used to access the main management functions that can be performed by
EMS-µLAN station users. It also provides information on the network status at a glance.

BroadGate™ EMS-µLAN User's Manual Building the Network
The map is customized for each particular network, as described in Background map,
page 4-6.
Figure 4-2: Typical Run mode Topology Browser window
The main window includes the following main elements:

!" Menu bar – described in Run Mode Menu Bar, page 4-7.
!" Toolbar – contains icons that provide shortcuts to the main actions. The toolbar used in
Run mode is described in Run Mode Toolbar, page 4-8.
!" Network topology area – contains a graphical representation of the network, including
NEs and their interconnecting links. The main window can optionally include a
background picture, such as a geographical map of the region where the network is
installed, as described in Background map, page 4-6.

Each NE is identified by its logical name, which is assigned when the element is first
included on the map. The color of the element indicates its status, in accordance with the
following color code:
Table 4-1: Element status colors
Color Status
Green No alarm
Green Event
Yellow Warning
Yellow Minor alarm
Orange Major alarm
Red Critical alarm
Black Disconnected
When several alarm conditions are present, the color indicates the most severe alarm
condition reported by the element. The E and W notations are short for East and West
respectively (see East and west conventions, page 4-7).
In addition, the following pop-up menus are available:
!" Element menu – this is a pop-up menu displayed by right-clicking the mouse on an NE.
The Element menu is described in Element Menu, page 4-9.
!" Link menu – this is a pop-up menu displayed by right-clicking the mouse on a link. The
Link menu is described in Link Menu, page 4-10.
4.4.1.1 Element icon key
The element icon key represents the NE. For further details, see Element Menu, page 4-9.
Figure 4-3: Topology Browser element icon key

4.4.1.2 Navigator
The Navigator can be used to zoom in on a portion of the network displayed in the
Topology Browser main window.
"#To operate the Navigator:
1. Click Zoom in the toolbar. The cursor becomes a magnifying glass.

2. Draw a rectangle over the part of the map where you want to zoom.
3. Select Views ! Show Navigator,
OR
Click Navigator in the toolbar.
The Navigator window opens, displaying a minimap with the area you
zoomed to marked in red.
You can drag the marked area to zoom to other parts of the map. This feature is also useful
when the map is too large to be displayed at the 100% zoom level.
Figure 4-4: Navigator window

4.4.1.3 Background map

The background map is a representation of the operations area in .BMP format.
"#To select a background map:
1. Select Views ! Setup to display the following:
Figure 4-5: Selecting the background map
2. Enter the name of the map or network. This name will be displayed in the title bar
of the Topology Browser.
3. Enter the path where the bitmap is located, or click the ellipsis to display a
window for browsing to the path and file. Select the Preview checkbox in this
window to see a thumbnail of the file.
4. When you have found the bitmap, click Open to select it and close the browse
window. Click OK in the Properties window when done.
For convenience, the size of the bitmap should be no larger than your screen resolution, for
example, 1024 x 728 pixels.

4.4.1.4 East and west conventions
All traffic in the network is said to travel either from east to west (westbound), or from west
to east (eastbound). These do not refer to the geographical directions; rather, traffic that
leaves the left port of the µLAN unit is westbound, and is referred to as the west card. It
connects to the east card on the next µLAN. Similarly, traffic leaving the right port is
eastbound, and connects to the west card at the next µLAN.
NOTE: In the EMS-µLAN, north and south are used to refer

to the two matrixes in dual-matrix NEs. For more
information, refer to Creating New Trails, in Chapter 5,
Building Trails.
4.4.2 Run Mode Menu Bar

The menu bar displayed in the Run mode window includes the following items:
Table 4-2: Run mode menu bar
Menu Option & Description

File Opens a submenu with the following items:
Print Prints the map
Print Preview Previews the way the map will be printed
Print Setup Changes printer settings
Exit Closes the Topology Browser and exits to the
Windows desktop
Views Opens a submenu with the following items:
View Alarms & Opens the Alarm and Performance Viewer
Performance (see Chapter 8, Using the Alarm and PM
Viewer), used to display the alarm and
performance history
Setup Enables you to select a background map, as
described in Background map, page 4-6
Show Navigator Opens the Navigator, as described in
Navigator, page 4-5
Hide Navigator Hides the Navigator


Mode Opens a submenu with the following items:
Start Run Mode Selects Run mode, in which the network
topology is protected. In Run mode, you
cannot add elements or links, change the
position of elements on the map, or change
attributes (IP address, label, or position). This
item is active when the Topology Browser is
in Design mode.
Start Design Mode Selects Design mode, which can be used to
define and edit the network topology. This
item is active when the Topology Browser is
in Run mode.
Zoom Opens a submenu with the following item:
Zoom 100%, 200%, 400%, Changes the zoom of the map view.
800%
Help Displays copyright and version information for the Topology Browser.
4.4.3 Run Mode Toolbar

The toolbar displayed in run mode includes the following icons:
Table 4-3: Run mode toolbar
Icon Description
Selects Run mode, in which the network topology is protected. In Run mode,
you cannot add elements or links, change the position of elements on the
map, or change attributes (IP address, label, or position).
This icon is active when the Topology Browser is in Design mode.
Selects Design mode, which can be used to define and edit the network
topology.
This icon is active when the Topology Browser is in Run mode.
Opens the Navigator window.
Select an area of the network to zoom to. Click the down arrow to open the
Zoom menu.

4.4.4 General Browser Menu

Right-click any empty area in the Topology Browser (that is, not on a link, element, or other
item) to display the following pop-up menu:
Table 4-4: General browser menu
Option Description
Show or Hide Navigator Displays the Navigator window. See Navigator, page 4-5.
Zoom 100%, 200%, Changes the zoom of the map view.
400%, 800%
4.4.5 Element Menu

Select an NE and then right-click the mouse button to display the following pop-up menu:
Table 4-5: Element menu
Option Description
Display Card View Opens the Card View window, which is used to perform
element management activities. The Card View is described
in Chapter 6, Configuring and Monitoring µLAN NEs and
Chapter 7, Configuring and Monitoring Ethernet Services.
View Alarms and Opens the Alarm and PM Viewer (see Chapter 8, Using the
Performances Alarm and PM Viewer), which is used to display the alarm
and performance history.
Manage Trails Opens the Trail Manager utility described in Using the Trail
Manager, in Chapter 5, Building Trails.
OrderWire For future use.
Check TIU Type Checks to determine whether the TIU registered type
matches the real type in use. This option is not currently
supported.
Ping Opens the window of the ping utility installed on your
computer. Use it to ping (check IP connectivity to) an IP
host, which is an Internet Control Message Protocol (ICMP)
service utility.
Telnet Opens the Telnet window of the Telnet utility installed on
your computer.
FTP Used to activate the File Transfer Protocol (FTP) service.
This opens the window of the FTP utility installed on your
computer.
Change IP Changes the IP address of the element (disabled in Run
mode).
Rename Changes the logical name of the element (disabled in Run
mode).

Option Description
Delete Deletes the element (disabled in Run mode).
Properties Displays details about the element, including its status,
identification of east and west neighbors, and the dates when
the element was created and modified.
4.4.6 Link Menu

Select a link and then right-click the mouse button to display the following pop-up menu:
Table 4-6: Link menu
Option Description
Send Link Parameters Sends the three parameters (j0, j1, c2) that form the unique
link ID. This feature enables you to build a network offline,
and then activate it when the elements are connected.
Insert element Inserts a new NE between two existing elements in the link.
Properties Displays details about the link, including its type, link ID
parameters, IP addresses and direction of its source and
target. It also displays the dates when the link was created
and modified.
Delete Deletes the trail.
4.5 Design Mode

Design mode is used to define and edit the network topology. It supports all the operations
described in Run Mode, page 4-2. However, the main purpose of this mode is to define the
network topology used by the EMS-µLAN station. The relevant activities are as follows:
!" Operations on NEs, as described in Creating NEs, page 4-14.
!" Operations on links, as described in Creating Links, page 4-19.
NOTE: You cannot delete an element if it appears in any

path, and you cannot delete a link if it is part of a trail. In
order to delete a link, first delete a trail. To delete an element,
first delete a link or trail.

4.5.1 Design Mode Main Window

"#To switch to Design mode:
Click in the Run mode toolbar, or select Start Design Mode from the Mode menu.
A typical Design mode main window is shown in Figure 4-6.
Compared with Figure 4-2, the main window shown in Figure 4-6 includes a
Configuration menu and corresponding toolbar icons. The toolbar displayed in Design
mode is described in Run Mode Toolbar, page 4-8.
Figure 4-6: Typical Design Mode Topology Browser window
The Navigator can be used to zoom in on selected portions of the window, as described in
Navigator, page 4-5. For more information about defining the background map, refer to
Background map, page 4-6.

4.5.2 Design Mode Menu Bar

The menu bar displayed in the Design mode includes the items explained in Run Mode
Menu Bar, page 4-7, as well as an additional menu, Configuration. This menu is used to
manage elements and connections in the network.
Table 4-7: Design mode – Configuration menu
Option Description
Add Network Element Adds a new NE on the map and defines its parameters.
Add External Element Adds a new external NE on the map and defines its
parameters.
Delete Element Deletes an existing NE. This operation is also available from
the element menu (see Element Menu, page 4-9). This item
is active only when an existing NE is selected.
Add Link Adds a new link to the map.
Delete Link Deletes an existing link. This item is active only when an
existing link is selected.
Add Group Not supported in this version.
Ungroup Not supported in this version.
Delete Group Not supported in this version.
NOTES: To modify the parameters of an existing element,

use the Change IP and Rename items on the Element menu
(see Element Menu, page 4-9).
When working in integrated mode from eNM or
eNM LightSoft™, link creation is superfluous.

4.5.3 Design Mode Toolbar

The toolbar displayed in Design mode includes the icons described in Run Mode Toolbar,
page 4-8, as well as the following additional icons:
Table 4-8: Design mode toolbar
Icon Description
Adds a new NE.
Adds a new external NE.
Deletes an existing NE (active only when an existing NE is selected).
Adds a new link.
Deletes an existing link (active only when an existing link is selected).
Unified direction: Enables you to create east-east and west-west links.

This is an advanced feature, and its availability depends on the physical
configuration of your network.
NOTES: The Create group, Delete group, and Ungroup

icons are currently disabled.
If a link uses an external NE interface and there is no trail
using it, deleting this link frees up the link’s resources.

4.6 Creating NEs

New NEs can be created in Design mode only.
NOTES: When working in integrated mode, NEs are created

using eNM LightSoft or eNM, as described in EMS-μLAN
Integrated Mode of Operation, in Chapter 1, Introduction.
Before creating the NE in the management system, the NE must
first be installed using the LCT-μLAN craft terminal. For more
information, refer to the BroadGate μLAN Installation,
Operation and Maintenance (IOM) Manual.
"#To create an NE:
1. Click the Add Element toolbar icon ,

OR
Select Configuration ! Add Network Element from the menu bar. The cursor
changes to a crosshair.
2. Move the cursor to the place you want the element to appear and click.

The Add Network Element window is displayed.
Figure 4-7: Add Network Element window
The NE is defined by specifying the following parameters:

Table 4-9: NE parameters
Name Enter the name that will be used to uniquely identify the
new NE (up to 15 characters).
IP address Enter the management IP address that will be used to
manage the new NE (use the dotted-quad format). Make
sure to enter a unique address.
To test the connection to the address, click ping.
Element type AutoDiscovery – if the element is on the network, the
system will locate and define it based on the IP address.
Otherwise, a type is selected from the drop-down list.
TIU description Lists the supported element types.

Radio/Fiber Indicates the link connection type, either Radio or Fiber,
from both eastbound and westbound outgoing ports on
the NE.
Radio links are not supported in the current version.
Connectivity The area at the bottom of the window graphically depicts
Direction the traffic flow direction from the NE. By default, traffic
flows westbound from the left port of µLAN and
eastbound from the µLAN right port. You can change the
default traffic flow direction by clicking the button.
3. After filling in the required data, click Discovery (if you selected AutoDiscovery)
and wait for the system to locate the element.
4. Select the Fiber radio buttons on both sides of the button. Radio links are not
supported in the current version.
5. [Optional] Click to change the traffic flow direction from the NE.
Figure 4-8: Example of default connectivity direction
Figure 4-9: Example showing connectivity direction change
6. Click OK to confirm. The new element appears on the map.

4.6.1 Redefining an NE
The name and IP address of NEs can be redefined, if required.
"#To redefine an NE:
1. Right-click the NE, and then select Change IP or Rename from the Element menu.
The respective windows are shown in Figure 4-10.
Figure 4-10: Redefine NE windows
2. After changing the data, click OK to confirm.
4.6.2 Deleting an NE
An NE cannot be deleted if it is part of a link. You must delete all links to an NE before it
can be deleted.
"#To delete an NE:
1. Click the Delete Element toolbar icon ,

OR
Right-click the NE, and then select Delete from the Element menu,
OR
Select Configuration ! Delete Element from the menu bar.
You will be prompted to confirm the deletion.
2. Click OK to confirm, or No to cancel the deletion.
After clicking OK, the NE is removed from the map.

4.6.3 Adding an External NE

External elements are non-μLAN equipment within the network that can be connected to
μLAN devices using an STM-1 link. Each external NE can have two or more STM-1 ports,
thereby enabling multi-point STM-1 connections on the NE. External NEs are added using a
similar process to that for adding μLAN NEs.
"#To add an external NE:
1. Click in the tool bar,

OR
Select Configuration ! Add External Element from the menu bar. The cursor
changes to a crosshair. Move the cursor to the place you want the element to appear
and click.
The Add External Element window is displayed.
Figure 4-11: Add External Element window
NOTE: Be very careful when specifying the number of

shelves, cards, and ports for the external element, as they
cannot be changed. Therefore, it is recommended that you
create more ports than you may currently need and reserve
them for future use.

The external NE is defined by specifying the following parameters:

Table 4-10: External NE parameters
Label Enter the name that will be used to uniquely identify the
new external NE (up to 15 characters).
IP address Enter the management IP address that will be used to
manage the new NE (use the dotted-quad format). Make
sure to enter a unique address.
Shelves Enter the maximum number of shelves to be included on
the NE.
Cards Enter the maximum number of card slots per shelf.
Ports Enter the maximum number of STM-1 ports per card.
NOTE: External element parameters are validated as part of

the connection process.
3. After filling in the required data, click OK. The new element appears on the map,
and is designated as an external element by the EE notation.
4.7 Creating Links

New links between two NEs can be created when in Design mode. The links appearing on
the Topology Browser map represent true physical links. A physical connection to a µLAN
element must be terminated at a free MU card. Therefore, a link can be added only between
NEs that have a free MU card.
NOTE: Links created via an NMS in integrated mode (as

described in EMS-μLAN Integrated Mode of Operation, in
Chapter 1, Introduction) must be re-created here using the
Topology Browser.

"#To create a link:
1. Click the Add Link toolbar icon ,

OR
Select Configuration ! Add Link from the menu bar. The cursor changes to a
crosshair. Move it over an element until the crosshair is enclosed by a circle.
2. Click and then move the cursor to the NE to be connected.
3. Click again. The Connect two elements window is displayed.
Figure 4-12: Connect two elements window
4. Choose East or West for either NE, and the corresponding direction is
automatically chosen for the other NE. If one or more of the connections have
already been allocated, those connections will be grayed out in this window.
NOTE: If the Unified Direction toolbar icon is selected (see

Design Mode Toolbar, page 4-13), you can create east-east or
west-west connections.
5. In the Link type field, select Fiber link.

6. Click OK to confirm.

After clicking OK, the new link appears on the map. A pop-up window appears
asking if you want to send the new link parameters (j0, j1, c2) to the NEs now.
Figure 4-13: Topology Browser popup window
7. Click Yes to do so, or No to update later.
NOTE: To view the link parameters, right-click the link and

select Properties from the pop-up menu.
4.7.1 Creating Links to External NEs

New links involving external NEs can be created when in Design mode. The links appearing
on the Topology Browser map represent true physical links.
Links can be created between a μLAN NE and an external NE, or between two external
NEs.
"#To create a link between a μLAN NE and an external NE:
OR
2. Click and then move the cursor to the external NE to be connected.

3. Click again. The Connection to External Element window is displayed.
Figure 4-14: Connection to External Element window
4. For the µLAN NE, select East or West for the direction of the link on the left-side
of the window.
5. For the external NE, enter the shelf, card, and port numbers (collectively called a
triplet) for the connection in the Shelf, Card, and Port boxes, respectively. A
warning message is displayed if you attempt to define an incorrect connection.
Figure 4-15: Warning message
6. Click Apply to set the external NE connection.

7. In the Link type field, select Fiber link.
8. Click OK to create the link between the two NEs.

"#To create a link between two external NEs:

OR
2. Click and then move the cursor to the external NE to be connected.
3. Click again. The Connection Between External Element window is displayed.
Figure 4-16: Connection Between External Element window
4. Choose the STM-1 interface for one external element (on the left-side of the
window) and the corresponding connection for the other external element (on the
right-side of the window). To do this, enter the shelf, card, and port numbers
(triplet) for the connection in the Shelf, Card, and Port boxes, respectively. Do this
for both external elements. A warning message is displayed if you attempt to define
an incorrect connection.
5. If more than one STM-1 connection exists on the NE, click the button to
obtain an additional connection.
NOTE: Use the button to remove a connection.
6. Click Apply to set the external NE link.

7. Click OK to create the link between the two NEs.

4.7.2 Deleting a Link

Before deleting a link, you must delete all the trails passing through or ending at this link.
"#To delete a link:
1. Click the Delete Link toolbar icon ,

OR
Right-click the link, and then select Delete from the Element menu,
OR
Select Configuration ! Delete Link from the menu bar.
You will be prompted to confirm the deletion.
2. Click OK to confirm, or No to cancel the deletion. After clicking OK, the link is
removed from the map.
4.8 Setting the Network Time

The Simple Network Time Protocol (SNTP) is used to synchronize the time and date
information of the NEs in the network. The internal clock inside the NEs can suffer from
time deviations that become significant over a long period of time, which can have an
adverse effect on the timestamps displayed for alarms and events reported by the
EMS-µLAN. Therefore, it is important to synchronize the NE using an accurate timing
source. For the µLAN, this timing source is a standard PC internal clock.
SNTP uses the User Data Protocol (UDP) to send a packet request to the timing source. The
timing source responds with a specially formatted data packet that contains the time
information, as well as information that enables calculation of the packet delay so that more
accurate readings can be made.

4.8.1 Launching Tardis on the Management Station

SNTP synchronization of the NEs in the network is performed using the Tardis application
installed on the management station, as described in Installing Tardis, in Chapter 2,
Installation.
"#To launch Tardis:
1. From Windows, select Start ! Programs ! tardis ! tardis 2000 to display the
following:
Figure 4-17: Tardis window
2. Minimize the Tardis window so that it appears as an icon on the taskbar. Tardis runs
in the background while SNTP is configured on each of the NEs. (Be careful not to
close Tardis.)
4.8.2 Configuring SNTP on an NE

SNTP configuration on a µLAN NE is performed via the EMS-µLAN management station.
This procedure must be performed for each NE in the network.
NOTE: SNTP configuration can also be performed during

first-time installation and commissioning of the NE using
LCT-µLAN, as described in the BroadGate µLAN
Installation, Operation and Maintenance Manual.

"#To configure SNTP on a µLAN NE:

1. In the Topology Browser, double-click the NE to be configured. HyperTerminal is
displayed.
2. Type cit and press Enter. An interactive menu is displayed.
3. Select 1: <Local>. The ID Protection Switching options are displayed.
4. Select 1: <IDU-CIT>. The IDU function facilities options are displayed.
5. Select 2: <Facilities>.
6. Select 6: <Time date <SNTP>>.
7. Select 2: <Time zone>.
8. Select 5: <STD GMT offset <min> [ ]. In the square brackets, enter the
time zone offset in minutes relative to GMT. For example, to define a time zone
located two hours behind GMT, enter the following:
<STD GMT offset <min> [-120]
9. Select 1: <SNTP enable>. The date and time are displayed, although they have
not yet been updated.
10. Press b. The updated date and time are displayed.
the date is 2004/01/17
the time is 09:10:18
11. Verify that the correct date and time are displayed.
12. Press Ctrl+D to log out.
13. Close the HyperTerminal window.
14. Repeat steps 1 through 13 for each µLAN NE in the network.

5
Building Trails
5.1 Overview
After defining the NEs in the network and creating links between them, the next step is to
build the trails that are used to route user-selected TU-12 tributary units between NEs.
TU-12 is an SDH transport frame with the capacity necessary to carry one E1 data stream.
NOTES: Creating trails is possible either via the Trail

Manager (for end-to-end management of µLAN networks, as
described in this chapter), or via the Card View (for defining
cross-connects when operating in integrated mode through
eNM LightSoft™ or eNM), as described in Building Trails
Using Card View, in Chapter 6, Configuring and Monitoring
µLAN NEs. It is generally recommended to use one method
or the other, but not both when defining the same trail for
different NEs.
In this release, the Trail Manager supports µLAN rings or
point-to-point topologies only. More advanced topologies
require enhanced external element options, which will be
released in version 2.1r2.
Trails must pass through existing links defined in Design mode of the Topology Browser.
Therefore, before starting the definition of a new trail, be sure to confirm that the required
NEs and links have been created, as described in Chapter 4, Building the Network.
Moreover, since the deletion of a link damages the trails, the Topology Browser does not
allow you to delete any links that carry trails. You must first delete the trails carried by the
link, before deleting the link itself.
The EMS-µLAN uses the information you provide during trail definition to generate
configuration commands to each NE included in the trail. These commands instruct each NE
about how to route each TU-12 unit to be transported by the trail to provide the required
cross-connect.
To match the organization of STM-1 frames (which contain three TUG-3 tributary units,
each capable of carrying up to 21 TU-12 units), the 63 TU-12 units are divided into three
groups of 21 each.

Building Trails BroadGate™ EMS-µLAN User's Manual
Two numbering conventions are used. One is based on standard numbers, as follows:
!" 1, 4, 7… 61 for the first group
!" 2, 5, 8… 62 for the second group
!" 3, 6, 9… 63 for the third group
The second numbering convention, called KLM, is used by SYNCOM and XDM® products,
as well as the EMS-µLAN. For more information about KLM notation, refer to Appendix C,
TU-12 KLM Notation Conversion Tables.
Routing options are shown in Figure 5-1. These routing options apply to each individual
TU-12 unit.
Figure 5-1: Definition of routing options
5.2 Trail Types

The routing options shown in Figure 5-1 can be used to better understand the trail types that
can be defined.
5.2.1 Bidirectional Trail

Bidirectional trails allow the same TU-12 units to be transported both east-to-west and
west-to-east using only one side of the ring. This type of bidirectional trail is unprotected.

BroadGate™ EMS-µLAN User's Manual Building Trails
Figure 5-2: Bidirectional trail
A bidirectional path is protected when the data is simultaneously sent in a separate path in
the opposite direction. This path is used as a backup in the event of failure.
A protected path is hitless when the data from each path is constantly compared and the data
of higher quality is used. Advanced algorithms developed by ECI Telecom's Optical
Networks Division ensure that this enhanced quality feature is seamless.
Figure 5-3: Protected bidirectional trail

5.2.2 Unidirectional Trail

Unidirectional trails allow TU-12 units to be transported only in one user-specified
direction, either east-to-west or west-to-east.
Figure 5-4: Unidirectional trail
5.3 Using the Trail Manager

When EMS-µLAN is being used in integrated mode with eNM or eNM LightSoft, trails are
typically defined at the NMS level using the Card View interface, as described in Building
Trails Using Card View, in Chapter 6, Configuring and Monitoring µLAN NEs. In
standalone mode, the Trail Manager application can be used. The Trail Manager is enabled
only when the selected NE is connected by a link to another NE.
IMPORTANT NOTE: Before using the Trail Manager, verify

that the EMS-µLAN database is synchronized with the NEs
using the Network Resolution Tool. Be sure to close the tool
afterwards, as the Trail Manager cannot be used when the
Network Resolution Tool is open. For more information,
refer to Network Resolution Tool, in Chapter 9, Additional
Services and Tools.

!"To start the Trail Manager:

Right-click an element in the Topology Browser, and select Manage Trails from the
pop-up menu.
Figure 5-5: Trail Manager window
The upper-left corner of the Trail Manager window contains a table of trails that have
been created, including the trail type and its current status. The trail type is defined
using the following convention: Trail Type(Tributary Type/Container Type: VCs
number). The following apply in this convention:
!" Trail type values are:
– P for SNCP protected trail
– BD for a bidirectional trail
– UD for a unidirectional trail
!" Tributary type values are:
– E1 for E1 trail
– E3 for E3 trails

– T3 for T3 trails (DS3); this option is not currently supported

– IP for Ethernet trails
!" Container type values are:
– VC12 for E1 trails
– VC3 for E3 trails
!" The VC number designates the number of virtual concatenators used by the
cross-connection
For example, using the defined convention, P(E1/VC12:1) represents a protected trail
for a single E1, and BD(IP/VC12:5) designates a bidirectional Ethernet trail that uses
five VC-12s.
The lower-left corner of the window displays TU-12 utilization on a selected link (as
described in Displaying and Editing Trails, page 5-23) or TU mid and cross-connection
information (as described in Displaying NE Cross-connection Information, page 5-26),
depending on what has been selected from the display area on the right.
5.3.1 Trail Manager Menu Bar and Toolbar

The menu bar of the Trail Manager window includes the following items:
Table 5-1: Trail Manager window items

Trail Opens a submenu with the following items:
Add Trail Opens the Add Trail window, which is used to
define new trails (see Creating New Trails,
page 5-8).
Corresponding toolbar icon:

Edit Trail Edits the TU-12 allocation for the trail (see
Displaying and Editing Trails, page 5-23). This
option is only relevant when the trail’s status is
reserved. See Table 5-5, page 5-27, for more details.

Trail List Opens the Trail List window to view trail details
(see Viewing Trail Information, page 5-14).

Properties Opens a window for defining whether the TU matrix
should be displayed vertically or horizontally.
Exit Closes the Trail Manager utility.

Protection Opens a submenu with the following items:

Add SNCP Protection Enables you to define an SNCP protection path for a
Path bidirectional trail (see Defining SNCP Trail
Protection, page 5-16).
Delete Main SNCP Enables you to remove the main SNCP path (see
Path Removing Trail Protection, page 5-18).
Delete Protection Enables you to remove the protection SNCP path
SNCP Path (see Removing Trail Protection, page 5-18).
SNCP Maintenance Enables you to perform a variety of maintenance
operations related to the SNCP main and protection
paths, such as lockout and manual switch operations
(see Modifying Trail Protection, page 5-19).
Tools Opens a submenu with the following items:
Repair Trail Enables you to repair a trail after inserting a new NE
into an existing trail (see Repairing a Trail,
page 5-25).
Check Database Performs a consistency check to ensure that the NE
consistency and the management station’s database are
synchronized (see Running a Database Consistency
Check, page 5-22).

Display Properties Enables you to select either TuMid or KLM
mapping. For more details, see Appendix C, TU-12
KLM Notation Conversion Tables.
Update Trail to GFP Enables you to change an Ethernet HDLC-mapped
trail to a GFP-mapped trail in the EMS-µLAN
database. You must perform this action after making
the associated change from HDLC to GFP in the NE
(using either LCT-µLAN or the Card View). For
example, an HDLC-mapped trail with 49 VC-12s is
changed to 46 VC-12s in a GFP-mapped trail. For
GFP, a maximum of 46 VC-12s are available for a
Fast Ethernet port.
Help Displays copyright and version information for the Trail Manager utility.

5.3.2 Creating New Trails

When creating a new trail, the most important parameters that must be defined include:
!" NEs included in the trail
!" Physical interface – E1, Ethernet (10 Mbps or 100 Mbps), or E3
!" TU-12s being used for the trail
NOTES: When creating trails in a mixed environment with

other SDH equipment, it is recommended to first create
VC-12 trails in the other NEs before creating trails using the
Trail Manager.
When creating an Ethernet ring, RSTP protection must be
enabled in the Ethernet Management window before running
traffic on the trails that have been created. For more
information on enabling RSTP, refer to Configuring General
Switching Parameters, in Chapter 7, Configuring and
Monitoring Ethernet Services.
!"To create a new trail with the Trail Manager:
1. Click the Add Trail toolbar icon ,

OR
Select File # Add Trail from the menu bar. The cursor changes to a crosshair.
2. Pause on an NE until the crosshair is enclosed by a circle.
3. Click and move the cursor to the element that completes the trail. A line is stretched
between them. Click the linked element. The Select trail type window opens.
Figure 5-6: Select trail type window
In this window, you define the trail’s type (protected or unprotected) and its
direction.

4. Select the East, West, or both East and West checkboxes to indicate the direction
for the trail.
5. Select one of the following radio buttons to indicate the trail type:
– Bidirectional
– Bidirectional protected hit
– Bidirectional protected hitless (not supported in the current version)
– Multipath
– Unidirectional westbound
– Unidirectional eastbound
For a description of each trail type, see Trail Types, page 5-2.
6. If a trail passes through an external NE, the Select outgoing port window opens in
which you define the external NE’s port to be used for continuing the trail. This port
specification process must be completed for each external element comprising the
trail.
Figure 5-7: Select outgoing port window
This window contains a separate row for each outgoing port on the external
element. The following information is displayed for each port:
!" Src ident (Source Identifier) – the identifier for the external NE’s local
interface triplet (shelves, cards, ports)
!" Dst ident (Destination Identifier) – the identifier for the other side of the
connection (either East/West for a µLAN NE or a shelf/card/port triplet for an
external NE)
!" Dst IP (Destination IP) – the element IP address for the other side of the
connection
!" Dst name (Destination Name) – the element’s name for the other side of the
connection

7. Select the required interface in this window and click OK. The Add Trail window
opens. The window content varies, depending on the trail’s endpoint elements.
If both endpoints are µLAN NEs, the following window opens.
Figure 5-8: Add Trail window – two µLAN NEs
If one of the endpoint NEs is a µLAN NE and one is an external NE, the section of
the window corresponding to the external NE is empty. If both endpoint NEs are
external ones, both NE sections in the window are empty.
For µLAN NEs, the Add Trail window displays blocks of TU mids for each trail
endpoint. TU mids that have already been allocated are displayed in yellow or
green.
Note that TUs are not displayed for external NEs, as the EMS-µLAN does not
manage these elements.
8. Select a trail type from the list displayed. The most common types are Bidirectional
and Unidirectional. Refer to Trail Types, page 5-2 for a description of trail types.

9. Select from among the following trail options, as required:

!" Protected – creates a protection path for the trail by transmitting and receiving
traffic through both the East and West ports. The NEs decide which direction is
used for the main path and which is used for the protection path.
!" Hitless – instructs the µLAN to choose the higher quality data at each
transmission.
!" Multipath – enables you to select TU-12s from both the east matrix and the west
matrix for the same trail. When this option is selected, enter the number of TUs
to be sent West to East and East to West in the fields displayed between the TU
blocks. These two values must add up to the total number of TUs required, as
displayed at the bottom of the window.
!" Shortest Path – instructs the Trail Manager to automatically select the shortest
path for a bidirectional link. To manually select the path, click the Path tab to
display the two possible paths for the trail, and select the relevant option.
Figure 5-9: Add Trail window – Path tab
!" Default J2 – assigns ECI Telecom's default J2 string to all traffic carried over
the trail. If the checkbox is not selected, a different string can be entered in the
field to the right of the checkbox.
!" Starting At – defines with which TU-12 block to begin the allocation. By
default, the first available block is used.
!" 1-1-1 strategy – select this option if when editing one of the tables you want the
corresponding TUs in the other table to move in tandem. This option simplifies
trail definition by using the same TUs in each NE as much as possible.

10. In the lower-left corner of the window, select the data transfer type: E1, E3, T1,
10bT, or 100bT. In the field to the right, optionally modify the number of TUs to
allocate to the trail. Either type the number, or use the +/- buttons to change the
number.
11. When creating an Ethernet trail (10bT or 100bT), select the checkboxes for
determining which virtual WAN port(s) to use on each NE at the bottom-left of the
window. A maximum of six WAN ports can be configured. You can determine the
actual number of WAN ports available on the NE by clicking the Test button. If
additional WAN ports are identified through this action, the button corresponding to
the number of available WAN ports is automatically selected.
For Ethernet trails, you must also select the Ethernet frame mapping type to be used.
Select the GFP or HDLC checkbox, as appropriate. Be sure that all NEs in the trail
use the same Ethernet mapping type. If they do not, an error message is displayed.
Click the adjacent Test button to determine the mapping type for the trail.
NOTE: An error message is also displayed if you attempt

to select 47, 48, or 49 VC-12s for GFP mapping. A
maximum of 46 VC-12s can be used for GFP mapping.
12. Click the Mid Order button to determine the order for selecting TU mids:
top-down or bottom-up (recommended when both E1/T1 and Ethernet
trails are present).
NOTES: Define carefully all the parameters for this

window as the information cannot be modified once it is
stored in the EMS-µLAN database. To make changes, you
must delete the trail and then redefine it.
Only reserved TUs (those not in the database and not in the
NE) are shown in blue.
13. Click Set. The Trail Manager allocates the TUs and the TU mids, which are
displayed in blue. In the EMS-µLAN, the first 21 TU-12s are reserved for E1 trails.
By default, Ethernet trails are assigned available TU-12s starting from the end of the
selected block. If required, manually click and drag the allocation to other TU mids.
In dual-matrix NEs, which offer twice the number of TUs, click the North/South
button beneath the TU mid blocks to toggle between the matrices. E1 trails can be
allocated to the south matrix only, and E3 trails can be allocated to the north matrix
only.
NOTE: TUs already saved to the database are displayed in

yellow. TUs whose allocations have been saved and sent to
the NEs are displayed in green. These allocations cannot be
changed.

14. In the Trail ID field, enter a unique identifier (up to 15 characters) to replace the
one automatically generated by the Trail Manager when Set was clicked. (Leaving
the default name generated by the system will cause the trail to fail.)
NOTE: It is highly recommended to use meaningful trail IDs

when creating trails in order to avoid mismatches between the
endpoints of the trail. The trail ID should be entered only
after clicking Set.
15. Click OK to accept the trail. The new trail appears in the Trail Manager list.
16. In the Trail Manager window, select the trail and do one of the following:
!" Click Store to store the trail information in the database. The selected TUs
turn yellow.
!" Click Send to both store the trail information in the database and send the
information to the NEs. The following window is displayed:
Figure 5-10: Send crossconnections window
– Select the checkbox next to each NE to receive cross-connection information

for the trail.
– Click Start. A progress bar indicates the current state of the data transfer to
each NE.
– When finished, click Close. The TUs allocated to the trail are displayed in
green in the Trail Manager window.
NOTE: Trails cannot be edited in this release. To modify a

trail, delete it and then re-create it.

5.3.3 Viewing Trail Information

After creating a trail, you can view detailed information about it in the Trail list window,
including the trail type, the TUs used (Snk, Mid, and Src), and the J2 strings being
transmitted and received.
!"To view trail information:
1. In the Trail Manager, select the checkbox next to the trail you want to view.
2. Click the Trail List toolbar icon ,

OR
Select Trail # Trail List from the menu bar.
The Trail list window is displayed.
Figure 5-11: Trail list window
Each row includes the following fields:

Table 5-2: Trail list window items
Item Description
# Row index number (sequentially assigned to each NE along the
trail path).
Trail name Logical name of the trail.
Type Trail type (P – protected, UD – unidirectional,
BD – bidirectional).
Port Virtual WAN port – E1, IP1, or IP2.
Container Displays VC12 for E1 trails and VC3 for E3 trails.
IP IP addresses of the elements in the trail.
Element Names of the elements in the trail.

Item Description
Snk ID ID of the MU card processing the incoming (snk) side. The card
ID is displayed by means of the View Card Info window of the
card (see Viewing MU Card Information, in Chapter 6,
Configuring and Monitoring µLAN NEs). E indicates an East
card, and W indicates a West card.
Snk TU TU-12 number on the incoming (snk) side.
Mid ID Displays M(s) for south matrix, M(n) for north matrix. (North
matrix appears only in dual-matrix NEs.)
Mid TU The TU-12 mid unit via which the information is added or
dropped. For actual routing to a local E1 port, the TU-12 number
represents the physical LAN port number, using the conventions
indicated in Overview, page 5-1. For a through-connection
(TU-12 not routed to a local port), this field displays 0.
Src ID ID of the MU card processing the outgoing (src) side.
E indicates an East card, and W indicates a West card.
Src TU TU-12 number on the outgoing (src) side.
J2 Tx J2 string transmitted over the trail.
J2 Exp J2 string expected to be received.
The icon next to the trail name indicates the current status of the trail:
Table 5-3: Trail status options
Option Description
The trail is in the computer's memory, but has not been stored in the database
or sent to the NEs.
The trail is stored in the EMS-µLAN database, but has not been sent to the
NEs.
The trail must be repaired before being sent to the NEs.
The trail has been sent to the NEs.
3. If the icon next to the trail name has a red background, this indicates that not all
NEs in the trail have received the trail information. Expand the trail row by clicking
the icon to display trail information for each NE in the trail.

5.3.4 Defining SNCP Trail Protection

An SNCP protection path can be defined for bidirectional trails.
!"To define an SNCP-protected trail:
1. In the Trail Manager, select the checkbox next to the trail whose protection you
want to define.
2. Right-click and select Add SNCP Protection Path,
OR
Select Protection # Add SNCP Protection Path from the menu bar.
Figure 5-12: Trail Manager window showing add SNCP protection option

3. A protection trail for the selected trail is automatically built. If the trail contains an
external element, the protection trail is built up to the external element. For the
external element, the outgoing port on this element must be specified for the
protection path. This port specification process must be completed for each external
element in the trail. Port selection is made in a window such as the following:
Figure 5-13: Select outgoing port window
This window contains a separate row for each outgoing port on the external
element. The following information is displayed for each port:
!" Src ident (Source Identifier)
!" Dst ident (Destination Identifier)
!" Dst IP (Destination IP)
!" Dst name (Destination Name)
See step 6 on page 5-9 for a description of each of these fields.

4. Select the required port and click OK. The main (active) trail and the protection
(standby) trail are shown in the Trail Manager window, with the main path
designated with a blue dotted line and the protection path with a red dotted line. The
trail also shows a P in the Type field, indicating that it is a protected trail.
Figure 5-14: Trail Manager showing protected trail
5. Click Send to both store the trail information in the database and send the
information to the NEs.
5.3.4.1 Removing Trail Protection
A trail’s SNCP protection can be deleted, as required.

!"To remove trail protection:
!" In the Trail Manager, right-click a protected trail and select one of the following
options:
!" Delete Main SNCP Path – deletes the main path
!" Delete Protection SNCP Path – deletes the protection path

5.3.4.2 Modifying Trail Protection
The Trail Manager provides several options for controlling SNCP protection. These options
are only available for protected trails.
!"To modify trail protection:
!" In the Trail Manager, right-click a protected trail and select SNCP Commands
followed by one of the following options:
!" Clear previous SNCP Commands – clears the previous command(s) in use.
!" Lockout Main SNCP Path – locks out the main SNCP path. When this action is
applied, switching to protection is prevented, even if conditions require
automatic switching. Lockout remains in effect until the action is released.
!" Lockout Protection SNCP Path – locks out the protection SNCP path. When
this action is applied, switching to protection is prevented, even if conditions
require automatic switching. Lockout remains in effect until the action is
released.
!" Manual switch to Main SNCP Path – performs a manual switch to the main
path. The switch is made only if the protected path has no alarms on it. This is a
persistent command and should be cleared to remove it. It has a lower priority
than alarms, meaning, a manual switch returns to the protection path if the
protected path has an alarm on it.
!" Manual switch to Protection SNCP Path – performs a manual switch to the
protection path. The switch is made only if the protection path has no alarms on
it. This is a persistent command and should be cleared to remove it. It has a
lower priority than alarms, meaning, a manual switch returns to the main path if
the protection path has an alarm on it.

5.3.4.3 Viewing SNCP Protection Status
You can view the SNCP protection status for a trail on demand.
!"To view a trail’s SNCP protection status:
1. In the Topology Browser, right-click an NE and select Show SNCP status. The
Trail protection status window is displayed.
Figure 5-15: Trail protection status window
2. Click the Get SNCP status button to display status details. The following
information is displayed for the trail:
!" XConnect – the cross-connection ID
!" East – the current status of the eastward path
!" West – the current status of the westward path
!" Last SNCP command – identifies the last SNCP command in use on the
cross-connect
The status reported for the East and West paths can be one of the following:
!" Working – all of the interface’s TUs are currently working.
!" Protected – all of the interface’s TUs are currently protected.
!" Failed – all of the interface’s TUs have failed.
!" Mixed – all of the interface’s TUs are currently working or protected.
!" Mixed Failed – a subset of the interface’s TUs has failed.
3. Click Close to exit the window.

5.3.5 Additional Trail Options

After building a trail, you can right-click a trail endpoint to display a pop-up menu with the
following options:
Table 5-4: Additional trail options
Option Description
Ping Pings (checks IP connectivity to) an IP host. This opens the ping
window of the ping utility installed on your computer.
Telnet Opens a Telnet window for performing local configuration in the
Telnet utility installed on your computer.
FTP Activates the FTP service used for software download in the FTP
utility installed on your computer.
Trail list Opens the Trail List window to view trail details.
Edit J2 Opens the J2 Configuration window (see Figure 5-16) containing
the 15-character SDH address strings that the element transmits
(J2Tx) and expects to receive (J2Exp) from other elements. These
strings can be edited as long as they have not yet been saved to
the database.
Configure XCs Not supported in the current version.
Configure Drop XCs Not supported in the current version.
Figure 5-16: J2 Configuration window

5.3.6 Running a Database Consistency Check

You can perform a database consistency check to determine whether NEs are synchronized
with the management station database.
!"To perform a database consistency check:
1. In the Trail Manager, select Tools # Check Database consistency,
OR
Click in the toolbar.

The following window is displayed.
Figure 5-17: Check database consistency window
This window displays a list of all NEs and their current database status. NEs with a
red icon indicate that a database inconsistency condition exists. A green icon
designates an NE that is synchronized with the database.
2. Click Check consistency to refresh the information in the window.
3. Click Close to exit the window.

5.4 Displaying and Editing Trails

When you select a trail in the map area of the Trail Manager, the lower-left corner of the
window indicates TU-12 utilization on the specified link.
Figure 5-18: Displaying trails
TU-12s with a green background have been stored in the database and sent to the
corresponding elements. Yellow indicates that the allocation has been stored in the database,
but not sent to the elements. Blue indicates a reserved TU-12 whose allocation can be
changed. The TU allocation can only be changed for reserved TU-12s (shown in blue).
!"To edit the TU allocation:
1. Select the trail to edit.
2. Click the Edit Trail toolbar icon ,

OR
Select Trail # Edit Trail from the menu bar.
3. Click and drag the TU allocation, as required. Selected TUs are displayed in blue.
4. When you have changed the allocation, click Store and Send .

5.5 Inserting an NE on a Link

When inserting an NE on an existing link, you first add the NE to the topology map and
then repair the trails on the link.
!"To insert an NE on a link:
1. Right-click the link in the Topology Browser onto which you want to insert the NE
and select Insert Element.
2. Follow the procedure described in the Creating NEs section in Chapter 4, Building
the Network, to add a new NE. After adding the NE, it appears in the topology map.
The trail containing the inserted NE must be repaired to reflect the addition of the
NE on the link. Refer to Repairing a Trail, page 5-25, for more details.
5.6 Inserting an External NE on a Link

Before you can insert an external NE on an existing link, be sure that the external NE has
been created and exists on the topology map.
!"To insert an external NE on a link:
1. Right-click the link in the Topology Browser onto which you want to insert the NE
and select Insert External Element. A round cursor appears.
2. With the round cursor, point to the external NE to be inserted. The Insert External
Element window opens in which you define the ingoing and outgoing ports at the
inserted NE.
3. Enter the required port information and click OK.

5.7 Repairing a Trail

After inserting an NE onto an existing trail, you must repair the trail to reflect the addition
of the NE on the link. Trails in need of repair are indicated by the icon adjacent to the
trail name in the Trail Manager window.
Figure 5-19: Trail Manager window showing trail to be repaired
!"To repair a trail:

1. Click the trail to be repaired to select it.
2. In the Tools menu, select Repair Trail. A message box appears prompting you to
confirm the repair of the selected trail.
3. Click Yes. The trail is repaired and is now displayed in the trail list with the
icon. This icon indicates that the trail has been repaired, but still needs to be sent to
the NE.
4. Select the checkbox adjacent to the trail in the trail list and click Send to both
store the trail information in the database and send the information to the NE. The
Send Cross-connections window is displayed.
5. Click Start. A progress bar indicates the current state of the data transfer to the NE.
6. When the data transfer operation completes, click Close to exit the Send
Cross-connections window.

5.8 Displaying NE Cross-connection Information

When you select an element included in a trail, the lower-left corner of the window displays
information about TU mids and their cross-connections.
Figure 5-20: NE cross-connection information
Figure 5-20 shows the allocation of the TU mids for the selected NE or link. Each TU mid is
connected to one or two TU-12s, depending on whether the link is unidirectional,
bidirectional, or protected. A green background indicates trails that have been stored in the
database and sent to the NEs. Yellow indicates trails whose allocation has been stored in the
EMS-µLAN database but not sent to the NEs. Blue indicates reserved TUs.

5.9 Deleting an Existing Trail

The procedure for deleting an existing trail is dependent on the status of a trail.
Table 5-5: Deleting existing trails
Option Description How to Delete

The trail is in the computer's Click Delete to remove the trail. Click
memory, but has not been stored Yes in the confirmation window.
in the database or sent to the
elements.
The trail is stored in the Click Delete to remove the trail. Click
EMS-µLAN database, but has not Yes in the confirmation window. The
been sent to the elements. data is no longer in the database, but
still resides in the computer's memory.
To completely delete the data, another
window opens asking if you wish to
delete it from memory. Click Delete.
The trail has been sent to the Click Delete to remove the trail. Click
elements. Yes in the confirmation window to
remove the trail from the elements.
Click Yes in the second confirmation
window to remove the trail from the
database, and click Yes a third time to
remove it from memory.
Trails can also be deleted using the Network Resolution Tool, as described in Network
Resolution Tool, in Chapter 9, Additional Services and Tools.


6
Configuring and Monitoring µLAN
NEs
6.1 Overview
This chapter describes the information that can be viewed and configured via the Card View
and View Details windows of a selected NE, including:
!" General component information
!" MU card timing
!" Maintenance information
!" Performance information
!" Trace IDs
In addition, this chapter describes how to configure cross-connects within a selected NE as
part of a larger trail using the Card View. This method is used in place of the Trail Manager
(described in Creating New Trails, in Chapter 5, Building Trails) when working in
integrated mode via the eNM or eNM LightSoft™ network management systems. For more
information about integrated mode, refer to EMS-µLAN Integrated Mode of Operation, in

Configuring and Monitoring µLAN NEs BroadGate™ EMS-µLAN User's Manual
6.2 Card View

The Card View application provides a convenient central point of access to all the element
management functions that can be performed with the EMS-µLAN. In addition, it provides
valuable system status information at a glance.
6.2.1 Displaying Card View

The Card View can be displayed in two ways:
!" Double-click the icon of the desired µLAN NE in the Topology Browser (or in eNM or
eNM LightSoft, when operating the EMS-µLAN in integrated mode),
OR
Right-click the desired µLAN NE in the Topology Browser, and select Card View from
the pop-up menu.
Figure 6-1: Typical Card View window
Figure 6-2: Typical VC-3 Card View window

BroadGate™ EMS-µLAN User's Manual Configuring and Monitoring µLAN NEs
In response, the EMS-µLAN station establishes management communication with the

selected element and retrieves the required information. This action may take a few seconds,
depending on the delay in the management communication channel. A progress bar provides
visual confirmation while the information is being retrieved.
If the required information cannot be retrieved within the management communication
timeout interval, an error message appears, and no cards are displayed in the window. Click
Reconnect or repeat the process to bring up the window.
6.2.2 Card View Window Description

The Card View window displays a header that includes the IP address of the element. The
window also shows a real-time color replica of the front panel of the µLAN system,
complete with realistic graphical representations of the system cards and their status
indicators. (Due to different TIU types, the precise configuration of the card may vary.) The
colors of these indicators represent their actual current state, and are periodically updated.
Table 6-1: µLAN status indicators
Indicator State Meaning

CR Gray No critical failure has been detected in the element
Red A critical failure has been detected in the element
MJ Gray No major failure has been detected in the element
Red A major failure has been detected in the element
MN Gray No minor failure has been detected in the element
Red At least one minor failure has been detected in the element
WR Gray No warning condition has been detected in the element
Red At least one warning condition has been detected in the element
LOS W Green Signal functioning correctly on West card
Red Loss of signal on West card
LOS E Green Signal functioning correctly on East card
Red Loss of signal on East card
STATUS Green No alarm present on the MU/TIU card
Red One or more alarms present on the MU/TIU card

In addition, the Card View window includes the following buttons:

Table 6-2: Card View buttons
Button Description
Displays a pop-up window listing those maintenance procedures currently
in progress. See Viewing Maintenance Operations, page 6-43.
Indicates whether the LCT-µLAN is currently connected to this NE. For

more information about the LCT-µLAN, refer to the BroadGate µLAN
Closes the Card View window.
Reconnects to the element if communication is lost.
Instructs the EMS-µLAN station to connect to the selected element and
retrieve updated status information. This button is inactive (gray) when the
card is being queried for information.
6.3 Viewing MU Card Information

The View card info window displays basic information about the MU card of the selected
µLAN, such as its serial number and software version number.
!"To display the View Card Info window:
1. In the Card View window, select the MU card.
2. Select Details # View Card Info from the menu to display the following:

Figure 6-3: View card info – MU window
Initially, the Card View displays an empty data form, and sends a request to the selected NE
to provide the required parameters. This action may take a few seconds, depending on the
delay in the management communication channel. After the requested information is
received, it appears in the data form.

The View card info – MU window includes the following information.

Table 6-3: View card info – MU window fields
Field Description
Cage number Cage number on the NE.
MU serial number Serial number of the MU card.
Software Pack version Software package version (SWPack) on the NE, identified by
its version and release numbers. For example, 2.2.r.1 means
version 2.2, release 1.
Running Embedded Embedded software version currently running on the NE.
SW
Running IDF FPGA Currently running IDF FPGA version.
Running TUPP FPGA Currently running TUPP FPGA version.
Flash 0 version Embedded version stored in flash bank 0.
Flash 1 version Embedded version stored in flash bank 1.
Active flash Which flash bank is currently active – 1 or 0.
MU type MU card type.
OHAU type Overhead Access Unit card type (used in NEs that include the
user channel and/or orderwire options).
TIU hardware serial Unique serial number of the card assigned by the manufacturer.
number This number is stored in the card firmware.
TIU hardware version Hardware version of the card assigned by the manufacturer. The
version is stored in the card firmware.
TIU card PEC code TIU ASIC version number.
TIU type TIU card type (for example, TIU-21E1-6Eth).
After reading the desired information, click Close to close the window or Advanced to
define Ethernet frame mapping, DCC, orderwire, user channel settings, and LAN/WAN port
allocation, as described in Defining Advanced Options, page 6-45.

6.4 Viewing TIU Card Information

The View info window displays basic information about the TIU card of the selected µLAN,
such as its serial number and hardware version number.
!"To display the View info window:
1. In the Card View window, select the TIU card.
2. Select Details # View Card Info from the menu to display the following:
Figure 6-4: View info – TIU window
Initially, the Card View displays an empty data form, and sends a request to the selected NE
to provide the required parameters. This action may take a few seconds, depending on the
delay in the management communication channel. After the requested information is
received, it appears in the data form.

The View info – TIU window includes the following information:

Table 6-4: View info – TIU window fields
Field Description
TIU hardware serial Unique serial number of the card assigned by the manufacturer.
number This number is stored in the card firmware.
TIU hardware version Hardware version of the card assigned by the manufacturer. The
version is stored in the card firmware.
TIU card PEC code TIU ASIC version number.
TIU type TIU card type (for example, TIU-21E1-6Eth).
6.5 View Details Window

The View Details window, which is accessed from the Card View window, is used to
configure the operational parameters of the various subsystems located on the MU card, to
perform maintenance actions, and to display status and alarm information.
!"To display the View Details window:
In the Card View window, select Details # View Details from the menu bar to display
the following:
Figure 6-5: View Details window
The Card View sends a request to the selected element to provide the required parameters.
This action may take a few seconds, depending on the delay in the management
communication channel. After the requested information is received, it appears in the
window.

The menu bar of the View Details window includes the following items:
Table 6-5: View Details menu bar
Option Description
Performance Opens a menu for selecting the desired type of performance
statistics. Options include performance statistics collected at the
local and far ends for the current 15-minute and 24-hour intervals, as
well as for previous 15-minute intervals.
This menu also contains options to reset the performance statistics
and to select the performance alarm thresholds.
Maintenance Opens a menu for accessing the maintenance functions available for
the MU card and for selected subsystems.
Information Displays technical information and the alarm status for the MU, the
TIU, or a selected subsystem. For some subsystems, this item
enables the Card View user to perform configuration activities.
Contacts/Relays Opens the Contacts and Relays window used to define the properties
of contacts and relays used by external input and output alarms
connected to the µLAN NE. For more information, refer to Defining
contacts and relays, page 6-21.
Cross Connections Opens a window for displaying existing cross-connections and
creating new ones. For more information, refer to Building Trails
Using Card View, page 6-24.
Help Accesses EMS-µLAN help information.
The View Details window comprises the following areas:

!" West and East areas
!" General area
In addition, the window has two buttons:
!" Close – closes the window
!" Refresh – instructs the EMS-μLAN station to resend a command, if required
The View Details window also displays the installed TIU type.
NOTE: Most of the operations that can be performed via the

View Details window disrupt the traffic through the NE.
While some disruptions may be temporary, others persist
until the configuration of the neighboring NEs is changed to
match the new configuration.
Moreover, whenever the traffic flow is disrupted, the
management of other elements whose inband management
path passes through this element is also disrupted. Therefore,
be sure to obtain the required authorization, and coordinate
your actions with the other affected locations, before making
configuration changes.

6.5.1 West and East Areas

The West and East areas contain buttons for selecting an MU card subsystem as a target.
These subsystems, which correspond to the SOH layers in the SDH frame structure, include:
!" Regenerator subsystem
!" Multiplexer subsystem
!" High-order subsystem (VC-4)
!" Low-order subsystem (TU-12) (This option is disabled.)
6.5.2 General Area

The General area contains buttons that enable you to select a general subsystem as a target.
The subsystems that can be selected are:
!" SPI (SDH/SONET Physical Interface)
!" PPI (Physical Port Interface)
!" Terminal (Tributary Units)
!" Timing subsystem
Only one subsystem can be selected at any given time in any area.
6.5.3 Using the View Details Window

To perform an operation on the MU card, use one of the following procedures:
!" To display the configuration parameters and alarm severity level associated with a
specific subsystem, select the subsystem in one of the General areas, open the
Information menu, and select View Info. For more information, refer to View Details
Information Menu, page 6-12.
!" To manage cross-connections, select Cross Connections # Show Cross-Connect. For
more information, refer to Building Trails Using Card View, page 6-24.

!" To display performance statistics, do the following:

!" Reset the accumulated statistics and change performance alarm thresholds, if
required. For more information, refer to Resetting Performance Parameters,
page 6-39 and Setting Performance Thresholds, page 6-40.
!" For high-order performance statistics, select the desired subsystem (Regenerator,
Multiplexer, or High-Order) in either the West or East area,
OR
For low-order performance statistics, select PPI (for E1 ports) or Terminal (for
SDH-level statistics) in the General area.
!" Open the Performance menu and select the required option.
For more information, refer to Viewing Performance Information, page 6-36.
!" To perform a maintenance activity, select the Multiplexer subsystem (in either the
West or East area) or PPI (in the General area), open the Maintenance menu, and
select the required operation. For more information, refer to Performing Maintenance
Operations, page 6-41.

6.5.4 View Details Information Menu

This section presents the functions available under the Information menu for the SPI, PPI,
Terminal, and Timing subsystems of the MU card.
6.5.4.1 SPI Info window
The SPI Info window enables you to view general maintenance and performance
information for the SDH/SONET physical interface in the μLAN NE.
!"To display the SPI Info window:
1. From the View Details window, click SPI.
2. From the Information menu, select View Info. The following window is displayed.
Figure 6-6: SPI Info window
NOTE: Up to version 2.2, the ALS function could be

activated in the μLAN installed base only on units containing
Infineon transceivers. A second type of transceiver was not
able to support ALS. This limitation was removed in the
current version and no longer applies.

The SPI Info window contains the following fields:

Table 6-6: SPI Info window fields
Option Description
Interface type Displays the interface type, which is always Optical.
Optical type Identifies the optical interface type – S11, L11, or L12.
Auto Laser Toggles to enable/disable the automatic shutdown of the laser on the
Shutdown enable interface.
Delay time (sec.) Indicates the interval, in seconds, during which the laser waits to
transmit. After waiting for the designated interval, the laser attempts
to transmit again. If no answer is received, it stops trying to transmit,
waits for the defined delay interval to elapse, and then attempts to
transmit again. The default is 100 seconds.
Actual laser state Displays the current state of the laser – On (laser is transmitting) or
Off (laser is not transmitting). Comparable information is displayed
for both the East and West directions.
Default laser state Displays the default state of the laser – On, Off, or Release. A value
of On means that the laser is permanently on, and a value of Off
means that the laser is off by default. Release returns the laser to
automatic operation. Comparable information is displayed for both
the East and West directions.
SPI receive status Indicates the status of the laser – On or Off.
Click the Manual restart button to manually restart the laser immediately. In this case, the
laser can be restarted right away without having to wait the number of seconds specified in
the Delay time interval.
The ALS process automatically restarts the Delay time interval seconds counter whenever
the Manual restart button is pressed. For example, assume that a Delay time interval of
100 seconds has been specified. If you click the Manual restart button 50 seconds into the
100 second Delay time interval, the seconds counter restarts its count at that point, and will
count 100 seconds from that point forward before the laser attempts to retransmit.
Click the Manual restart for test button to send a test signal to test the status of the laser.
In addition, the window has two buttons:

6.5.4.2 PPI View Info window
The PPI View Info window enables you to view general maintenance and performance
information for a selected physical LAN port in the μLAN NE.
!"To display the PPI View Info window:
1. From the View Details window, click PPI.
2. From the Information menu, select View Info. A physical port interface (PPI)
selection window is displayed, enabling you to select the physical LAN port for
which information is required.
Figure 6-7: PPI View Info window showing 21 E1 ports
Figure 6-8: PPI View Info window showing 14 E1 ports and three E3 ports

NOTE: For VC-3 cards, the window displays both E1 and E3

ports. In this case, 14 E1 and three E3 ports are shown in the
window. All operations are performed in the same manner for
both of the cards shown on the previous page.
The number of PPI buttons appearing in the window is determined by the current
element transmission capacity. The icon in each button indicates the current status
of the port – Connected, Disconnected, Defective, or In maintenance.
3. Right-click the desired PPI button to display a pop-up menu with the following
options: Performance, Maintenance, View Info, and J0_J1.
4. From the Information menu, select View Info. This will open the corresponding
PPI information window.
Figure 6-9: PPI information window

The window contains the following fields:

Table 6-7: PPI information window fields
Option Description
Port status Displays the current port status – Normal, Disconnected, Defective,
or In maintenance.
Port type Displays the port type, which is always E1 or E3.
Framing type Displays the port processing mode:
Unframed The port processes the E1 or E3 stream as an
unframed data stream, without retiming the
received data.
Unframed The port processes the E1 or E3 stream as an
Retiming unframed data stream, and retimes the
received data in accordance with the
recovered clock signal.
Framed The port processes the E1 or E3 stream as an
ITU-T Rec. G.704 framed data stream,
without retiming the received data. This
enables the port to identify time slot 0
(including processing of the CRC-4 error
monitoring information), thereby enabling
the equipment connected to the
corresponding port to monitor the quality of
the E1/E3 link up to the MU card port.
Framed Retiming The port processes the E1 or E3 stream as a
framed data stream, and retimes the received
data in accordance with the recovered clock
signal.
Port number Indicates the number of the port (PPI) selected in the previous step.
In addition, the PPI View Info window has two buttons:


6.5.4.3 Terminal View Info window
The Terminal View Info window displays information about the access ports in the selected
µLAN NE.
!"To display the Terminal View Info window:
1. From the View Details window, click Terminal.
2. From the Information menu, select View Info. A selection window is displayed,
enabling you to select the tributary for which information is required.
Figure 6-10: Terminal View Info window
!" As with the PPI View Info window, right-clicking an icon displays a pop-up menu for
viewing low-order general, maintenance, and performance information. For more
information, refer to PPI View Info window, page 6-14. In dual-matrix NEs, click the
button in the lower-right corner to toggle between the south (default) and north
matrices.

6.5.4.4 Timing window
The Timing window enables you to view and configure the current active timing source
used by the MU card in the selected µLAN NE. In addition, you can select the primary and
secondary priority sources for synchronization.
!"To display the Timing window:
1. From the View Details window, click Timing.
2. From the Information menu, select View Info to display the following:
Figure 6-11: Timing window
The Timing window includes several areas, which are used to display the current
timing source, select the primary and secondary timing sources, and control the
generation of the T4 (tributary) clock signal.
In addition, the window includes the Disable SSM option. Selecting this option
disables the generation of synchronization status messages.
3. Click Refresh to retrieve the current timing parameters.
4. After making the desired selections, click Apply, and then click OK in the
displayed confirmation window to send the new data to the selected NE.

6.5.4.4.1 Active source
This field displays the timing source currently being used by the MU card. The available
options are as follows:
!" Primary – the MU card uses the timing source defined in the Primary area
!" Secondary – the MU card uses the timing source defined in the Secondary area
!" Holdover – the MU card generates and retains a reference frequency based on the last
frequency-correction data obtained before switching into this mode
!" Internal – timing is derived as a result of a Force Internal action
6.5.4.4.2 Primary and secondary areas
These areas are used to select the primary and secondary priority sources for synchronizing
the MU card timing subsystem, and include the following fields:
Table 6-8: Primary and secondary fields
Field Description
Source Selects the timing reference source with the highest priority. The sources
that can be selected are as follows:
External External timing reference signal supplied to the
EMS-μLAN system
Line East Timing signal recovered from the data stream received by
the MU card installed in the East chassis position
Line West Timing signal recovered from the data stream received by
the MU card installed in the West chassis position
Tributary A Timing signal recovered from the data stream received by
the first E1 port
None Timing signal generated by an internal free-running clock
oscillator

Field Description
SSM Used to select the minimum quality level (as read from the received SSM)
at which the source specified in the Timing Source field is still accepted
and used as a reference.
The available SSM selections are as follows (listed in descending order of
quality):
PRC Primary source per ITU-T Rec. G.811
(associated SSM message: 0001)
SSU-T T-type secondary source per ITU-T Rec. G.812
SSU-L L-type secondary source per ITU-T Rec. G.812
SEC Recovered clock source per ITU-T Rec. G.813
Do Not Use Do not use this source as reference
The Primary and Secondary sources must be different. After setting the parameters for
each source, click Apply.
NOTE: Force Off must be selected from the Source field

before changing a primary or secondary timing source. For
more information, refer to Force selection, page 6-21.
6.5.4.4.3 T4 squelch level
This area is used to control the characteristics of the T4 tributary (E1) clock signal generated
by the MU card. When SSM is disabled, you can enable or disable quality-level reporting
for the timing reference source, as follows:
!" On – quality-level reporting enabled
!" Off – quality-level reporting disabled
When SSM is enabled, you can select the minimum timing quality level for the T4 output. If
the T4 quality level decreases below the specified level, the T4 output is turned off
(squelched). The available selections (in descending order of quality) are: PRC, SSU-T,
SSU-L, SEC.
NOTE: For more information about these options, refer to

Table 6-8, page 6-19.

6.5.4.4.4 Force selection
The Forces drop-down list enables you to force the µLAN to select the timing source
specified in the Source field irrespective of its SSM message. The following options are
available:
!" Force Primary
!" Force Secondary
!" Force Holdover
!" Force Internal
!" Force Off
NOTE: Force Off must be selected before changing a primary

or secondary timing source. For more information about these
options, refer to Active source, page 6-19.
6.5.4.5 Defining contacts and relays
You can define the properties of contacts and relays used by external input and output
alarms connected to the µLAN NE.
!"To define contacts and relays:
1. In the View Details window, click a subsystem in the General area (SPI, PPI,
Terminal, or Timing) and then select Information # Contacts and Relays. The
Contact and Relays window is displayed.
Figure 6-12: Contact and Relays window – Dry Contact table
2. Select the Table menu to open the tables for other contacts and relays. The number
of rows displayed depends on the item selected.
3. To change any of the values, make selections from the drop-down menus or type in
the editable fields. Changes are saved automatically.

NOTE: External input alarms are always assigned a Minor

severity level. In addition, input alarm titles cannot be edited
within the application. To change the severity and titles of
external alarm input dry contacts, select Start # Network
Management # Dry Contacts Setup.
The following three tables are available:

Table 6-9: Contact and Relay tables
Table Purpose
Dry Contact Input Used to define the status (on/off) and the severity of the alarm
to be sent when a fault is detected in an external input alarm
device. Examples of such faults include a door open alarm or a
fan that is out of service.
Output Relay Used to define the status (on/off) and the description of the
Table relay to an external output alarm device; for example, the loss
of an STM-1 port.
Input Analog Used to enter the analog input values of external devices that
Table are connected to the element, including a description of the
value. For example, an input value might include the ambient
temperature surrounding the µLAN NE.
Figure 6-13: Contacts and Relays window – Output Relay table

Figure 6-14: Contacts and Relays window – Input Analog table
4. When you have finished defining contacts and relays, click Close.
NOTE: The Control tab is for use by technicians of ECI

Telecom's Optical Networks Division only.

6.6 Building Trails Using Card View

The EMS-µLAN offers the option of building trails from the Card View instead of the Trail
Manager. This method is used when working in integrated mode with eNM or eNM
LightSoft. It can also be used when you do not have access to the Topology Browser or
when working directly on an NE in the field. As opposed to the Trail Manager, which
enables end-to-end provisioning, building trails in Card View consists of defining the
cross-connections that make up the trail one NE at a time.
!"To build trails in Card View:
1. In the Card View window, select Details # View Details from the menu bar. The
View Details window is displayed.
2. Select Cross Connections # Show Cross-Connect from the View Details menu
bar to display the following:
Figure 6-15: Defining E1 trails in Card View

Figure 6-16: Defining E3 trails in Card View
Figure 6-17: Defining Ethernet trails in Card View
3. In the upper-right corner of the window, select Add.

4. Select the virtual WAN port type, direction, and trail type as follows:
!" From the Type drop-down list, select E1, E3, Eth, or TU3. If Eth is selected,
select 10 or 100 (BaseT) in either of the virtual WAN ports.
!" From the XC type drop-down list, select Unidirectional, Bidirectional,
Through (unidirect), or Through (bidirect). The Through options are used
when the traffic going through the selected NE will pass undisturbed to the next
NE in the trail, without passing through the matrix.
!" From the XC direction drop-down list, select the direction of the trail:
– East to West – a unidirectional cross-connection where traffic is received
from East line ports and transmitted to West line ports
– West to East – a unidirectional cross-connection where traffic is received
from West line ports and transmitted to East line ports
– East – a bidirectional cross-connection where traffic is both transmitted and
received over the East line ports
– West – a bidirectional cross-connection where traffic is both transmitted and
received over the West line ports
!" Select the Multi Path checkbox to select TU-12s from both the east aggregate
and the west aggregate for the same trail. When this option is selected, enter the
number of TUs to be sent West and East in the fields displayed between the TU
blocks. These two values must add up to the total number of TUs required. For
Ethernet unprotected trails, this value is the number of TU-12s between East and
West.
NOTE: When using the multipath option, the SNCP protocol

is not available.
!" [Ethernet trails only] The Count field displays the number of TU-12s required.
This number can be lowered manually, but has the result of reducing the overall
capacity of the trail.
!" [Ethernet trails only] From the Start From TU3 drop-down list, select the
TUG-3 block to use for allocation (1, 2, or 3).
NOTE: When E1 is selected as the trail type, only TUG-1 can

be assigned. Therefore, it is recommended to start all
Ethernet over SDH (EoS) trails from TUG-3. This will leave
TUG-1 available for E1 trails. For VC-3 trails, only the North
matrix can be used.

!" Select the 1-1-1 strategy checkbox if when editing one of the tables you want
the corresponding TU in the other table to move in tandem.
NOTE: For µLAN hardware released with version 1.2r2

onwards (based on the Virtex component), upgrading to
version 2.1 increases the capacity of the cross-connect matrix
from three to four VC-4 containers. (The fourth VC-4 can be
used for Ethernet and E3 trails only.) This increases total
add/drop capacity to two unprotected VC-4s (126 x VC-12)
or two protected VC-4s. The EMS-µLAN enables you to
choose whether to use a 3 or 4 x VC-4 matrix.
For older hardware versions running version 1.1 or version
1.2r1 (based on the Spartan component), the capacity of the
matrix remains 3 x VC-4.
5. Click Select. The TUs selected by EMS-µLAN appear in blue.

6. [Optional] If required, click and drag the TUs (at the top of the window and in the
matrix below) to change the allocation. In dual-matrix NEs, select the North matrix
checkbox to switch from the default south matrix to the north matrix.
7. In the Trail name field, enter a unique name for the trail in place of the name
automatically generated by the software.
CAUTION: Be sure to enter the same name for each

cross-connect included in the trail. Otherwise, the trail will
not be saved in the database.
8. Click Apply. The trail is sent to the NE. Trail information is displayed in the table
in the lower-right corner of the window.
9. Return to the Topology Browser, and repeat steps 1 through 8 to define the
cross-connection for the other NEs that make up the trail.
10. Upload the trail information to the database, as described in Network Resolution
Tool, in Chapter 9, Additional Services and Tools.

When working in integrated mode, you must check in the Topology Browser that
the NEs included in the trail are physically connected before uploading the trail
information. (This is because links created in eNM LightSoft do not appear
automatically in the EMS-µLAN.) For more information, refer to Creating Links, in
Chapter 4, Building the Network.
NOTES: When building trails in integrated mode, the

Cross-Connect window in pass-through NEs does not display
the TU-3s/TU-12s that are occupied in pass-through mode.
Nevertheless, these TU-3s/TU-12s cannot be used for other
cross-connects, and they are visible in the EMS-µLAN. To
display these TU-3s/TU-12s as occupied, use the Card View
to create the cross-connect in pass-through mode.
To view complete trail information in the Card View of the
selected NE, click the View/Modify button.
6.6.1 Deleting Cross-Connections in Card View

Cross-connections can be deleted from the Card View of a selected NE, as described below.
!"To delete cross-connections in Card View:
1. Select the View/Modify option in the upper-right corner of the window.
2. Select the cross-connect, either from the connection list in the lower-right corner of
the Card View cross-connection window, or from the list displayed in the Info tab.
3. Click Delete XC. The cross-connections are deleted.

6.6.2 Configuring the J2/J1 Bit

The Control tab in the Card View cross-connection window is used to view and edit the
J2/J1 bit used to identify the traffic on the trail.
!"To configure the J2/J1 bit:
1. Select the Control J2/J1 tab to display the following:
Figure 6-18: Configuring the J2/J1 bit
2. Edit the Transmitted J2/J1 and Expected J2/J1 fields, as required.

3. When finished, click Refresh.
6.6.3 Defining SNCP Protection

The Subnetwork Connection Protection (SNCP) mechanism is a dedicated protection
method that can be used to protect:
!" A portion of a path between two connection points
!" Between a connection point and a termination connection point
!" An entire end-to-end path between two connection points

NOTE: For Ethernet trails only, SNCP protection is not

supported for the North matrix.
This linear protection scheme can be applied individually to VC-n signals, and need not be
used on all VCs within a multiplex section or on all low-order VCs within HOVC. SNCP
protection operates in a unidirectional protection-switching manner.
!"To add SNCP to a path:
1. In the Cross-Connect screen, select the TU tab.
2. Click the View/Modify button.
Figure 6-19: Cross-connect screen showing the XC TUs list
3. In the XC TUs connection area, select a cross-connection in the list. The

cross-connection you select must be unprotected. The selected cross-connection’s
current protection status is shown beneath the VC-12 Count field.

4. Select the Protection checkbox to define the cross-connection’s protection

attributes. When you select this checkbox, the Cross-connect screen changes
enabling you to add protection to a currently unprotected cross-connection, or to
modify or remove protection from a protection (standby) cross-connection.
Figure 6-20: Cross-connect screen showing add protection option
5. In the Trail name field, enter a name for the protection cross-connection.

6. Select the Add protection path checkbox to define the cross-connection as a

protection (standby) cross-connection. If an East cross-connection is the one to be
protected (working path), the West direction cross-connection automatically
becomes the protection (standby) cross-connection when protection is defined. For
example, Figure 6-21 shows that a 1-1-1 protection scheme has been defined for
East TU#1, with the West TU#1 cross-connection as the protection (standby)
cross-connection.
Figure 6-21: Cross-connect screen showing protected cross-connection
7. Click Apply to save your changes.
6.6.3.1 Editing SNCP cross-connection protection
After a protected cross-connection has been defined, you can modify its protection, as
required. Options are available to lock out a protection (standby) cross-connection or to
manually switch to a protection cross-connection.
!"To edit SNCP cross-connection protection:
1. In the Cross-connect screen, select the TU tab.
2. Click View/Modify.
3. Select a protected cross-connection from the connection list in the lower-right
corner of the Card View cross-connection window.

4. Select the Protection checkbox. A window such as the following is displayed.
Figure 6-22: Cross-connect screen showing protected cross-connection
5. In the Edit protection drop-down list, select one of the following options:
!" Delete East path – select to remove protection from the East cross-connection
!" Delete West path – select to remove protection from the West cross-connection
!" Delete protection path – select to remove the entire protection cross-connection
NOTES: The Command status field is updated whenever the

Refresh button is pressed.
The XC protection status read-only fields show the current
status of both the East and West interfaces separately. XC
status can be one of the following:
!" Working – all of the interface’s TUs are currently working
!" Protected – all of the interface’s TUs are currently
protected
!" Failed – all of the interface’s TUs have failed
!" Mixed – all of the interface’s TUs are currently working or
protected
!" Mixed Failed – a subset of the interface’s TUs has failed

6. [Optional] Select the TU status checkbox to view the state of TU resources.
Figure 6-23: Cross-connect screen showing TU statuses
TU protection status is presented in a tabular format that includes three columns –

East, Mid, and West. The number of rows in the table is equal to the number of TUs
in the cross-connection. Each table entry shows a TU number and its associated
status information. When you highlight a row in the table, its corresponding TU
resource is highlighted in the adjacent TU mapping.
The following statuses apply for East and West TUs:
!" Working TU – the TU’s status is okay and it is part of a currently working path.
!" Protected TU – the TU’s status is okay and it is part of a currently protected
path.
!" Failed TU – a failure condition exists on this path.
For East or West TUs experiencing a failure condition, the Failure condition fields
display the current alarms affecting the TU, as shown in Figure 6-24.
Figure 6-24: TU failure condition example
For Mid TUs, only the TU number is shown in the table.


6.6.3.2 Using cross-connection protection commands
The EMS-µLAN provides several options for controlling cross-connection protection. These
options are only available for protected cross-connections, and apply to all TUs on a
specified cross-connection.
!"To apply a cross-connection protection control command:
1. In the Cross-connect screen, select the TU tab.
2. Click View/Modify.
3. Select a protected cross-connection.
4. Select the Protection checkbox.
5. In the Commands drop-down list, select one of the following options:
!" Clear previous command – clears the previous command in use.
!" Lockout East path – locks out the East path. When this action is applied,
switching to protection is prevented, even if conditions require automatic
switching. Lockout remains in effect until the action is released.
!" Lockout West path – locks out the West path. When this action is applied,
switching to protection is prevented, even if conditions require automatic
switching. Lockout remains in effect until the action is released.
!" Manual switch to East path – performs a manual switch to the East path. The
switch is made only if the protected path has no alarms on it. This is a persistent
command and should be cleared to remove it. It has a lower priority than alarms,
meaning, a manual switch returns to the main path if the protected path has an
alarm on it.
!" Manual switch to West path – performs a manual switch to the West path. The
switch is made only if the protected path has no alarms on it. This is a persistent
command and should be cleared to remove it. It has a lower priority than alarms,
meaning, a manual switch returns to the main path if the protected path has an
alarm on it.
!" Manual switch to protection path – performs a manual switch to the protection
path. The switch is made only if the protected path has no alarms on it. This is a
persistent command and should be cleared to remove it. It has a lower priority
than alarms, meaning, a manual switch returns to the main path if the protected
path has an alarm on it.

6.7 Viewing Performance Information

The Performance menu in the View Details window contains options for displaying the
performance statistics collected from the following card subsystems:
!" Regenerator (East/West)
!" Multiplexer (East/West)
!" High Order (East/West)
!" Terminal
!" PPI
The statistics can be presented in both graphical and tabular formats.
In addition, the Performance menu can be used to reset performance counters and to set
performance alarm thresholds.
!"To view performance statistics:
1. In the View Details window, select the desired card subsystem.
2. From the Performance menu, select the desired interval and the performance
parameters to be displayed.
The Performance menu contains the following options:
Table 6-10: Performance menu options
Option Description
Current 15 minute Displays locally collected performance statistics for the current
15-minute interval.
Current 24 hour Displays locally collected performance statistics for the current
24-hour interval.
Current 15 minute Displays the performance statistics collected by the corresponding
Far End far-end subsystem for the current 15-minute interval.
This function is available only when the link to the far end is
operational.
Current 24 hour Displays the performance statistics collected by the corresponding
Far End far-end subsystem for the current 24-hour interval.
This function is available only when the link to the far end is
operational.
15 minute History Displays locally collected 15-minute performance statistics for a
selected period (history).
Reset Performance Resets the desired type of performance data.
Set Performance Displays and modifies the desired type of performance thresholds,
Thresholds used to generate performance alarms.
These Performance options are explained in the sections that follow.

6.7.1 Viewing Current Performance Parameters

Current performance parameters (15-minute and 24-hour, local and far end) are displayed in
the Performance Chart window.
Figure 6-25: Performance Chart window

The Performance Chart window includes the following areas:

!" Title – describes the type of performance data presented in the window (for example,
current statistics), and the card subsystem (in the example shown in Figure 6-25, the
subsystem is an E3 port).
!" Chart area – displays the selected parameters as graphs. Each parameter is described
by a different line type and color, which is identified in a legend to the right of the chart.
The horizontal axis is marked to indicate the number of samples.
!" Poll interval – use the slider to define the interval between successive samples.
!" Use Default x Min/x Max – selects the system defaults for the X-axis. If this option is
not selected, enter values in the X-axis Min and X-axis Max fields.
!" Absolute time – select this option to have the X-axis display the absolute elapsed time
until the full range is reached.
!" Dynamic show legend values – select this option to display the exact value of each
measurement by pointing to the graph.
!" Performance parameter selection area – this area includes the list of performance
parameters supported for the selected MU card subsystem. Select the checkbox next to
each parameter to include it in the performance collection process. (Select Check All to
choose all of them.) Available parameters include:
!" Errored Seconds
!" Severely Errored Seconds
!" Consecutive Severely Errored Seconds
!" Unavailable Seconds
!" Background Block Errors
!" Out of Frame Seconds
The accumulated count for each selected parameter is displayed to the right of the parameter
label.
!"To collect and display performance parameters:
1. In the View Details window, select the card subsystem by clicking the icon in the
West, East, or General area.
2. Select the polling interval and range for the X-axis.
3. Select the desired performance parameters by clicking the corresponding
checkboxes.
4. Increase the size of the graph by clicking the small down arrow beneath the chart.
Click the up arrow to make the graph smaller again.
5. Start and stop polling by clicking Start/Stop Polling.
6. Click Restart Graph to clear the existing data from the graph.

6.7.2 Resetting Performance Parameters

The performance parameters collected by the selected µLAN NE can be reset (that is, the
corresponding counters can be reset to 0).
!"To reset performance parameters:
2. From the Performance menu, select Reset Performance and then select an option
from the displayed submenu.
Table 6-11: Reset Performance options
Option Description
Reset Current Resets the locally collected performance statistics for the
15 Minute current 15-minute interval.
Reset Current Resets the locally collected performance statistics for the
24 Hour current 24-hour interval.
Reset Current Resets the performance statistics collected by the
15 Minute Far End corresponding far-end subsystem for the current
15-minute interval. This function is available only when
the link to the far end is operational.
Reset Current Resets the performance statistics collected by the
24 Hour Far End corresponding far-end subsystem for the current 24-hour
interval. This function is available only when the link to
the far end is operational.
Reset All Current Resets all the locally collected performance statistics for
15 Minute Tables the current 15-minute interval. This option has the
advantage of ensuring synchronization of all the collected
data.
Reset All Current Resets all the locally collected performance statistics for
24 Hour Tables the current 24-hour interval. This option has the
advantage of ensuring synchronization of all the collected
data.
Reset All Current Resets all the far-end performance statistics for the
15 Minute Far End current 15-minute interval. This option has the advantage
Tables of ensuring synchronization of all the far-end collected
data.
Reset All Current Resets all the far-end performance statistics for the
Far End 24 Hour current 24-hour interval. This option has the advantage of
Tables ensuring synchronization of all the far-end collected data.

6.7.3 Setting Performance Thresholds

Alarms can be generated in cases where system performance degrades beyond user-defined
thresholds.
!"To set performance thresholds:
2. From the Performance menu, select Reset Performance Thresholds. In the
displayed submenu, select one of the following options:
Table 6-12: Reset Performance Threshold options
Option Description
Reset Current 15 Thresholds for the locally collected performance statistics
minute Thresholds for the current 15-minute interval
Reset Current Thresholds for the locally collected performance statistics
24 hour Thresholds for the current 24-hour interval
Reset Current 15 Thresholds for the performance statistics collected by the
minute Far End corresponding far-end subsystem for the current 15-minute
Thresholds interval
Reset Current Thresholds for the performance statistics collected by the
24 Hour Far End corresponding far-end subsystem for the current 24-hour
Thresholds interval
3. After selecting the threshold type, the Performance Thresholds Settings window is
displayed.
Figure 6-26: Performance Threshold Settings window

The window lists all the performance parameters that can be collected for MU card
subsystems. However, only the fields for the parameters supported by the currently
selected subsystem can be modified. (The other fields are grayed out and cannot be
accessed.)
4. After entering the threshold values, click Apply.
5. To close the window, click Close.
6.8 Performing Maintenance Operations

The Card View application enables you to perform loopback operations on the
SDH/SONET physical interfaces (SPI) of the µLAN, as well as various maintenance
procedures on the Multiplexer and PPI subsystems. Multiple maintenance operations can be
performed simultaneously. Visual feedback is provided through the Card View to enable
you to see which subsystems are currently running maintenance operations.
CAUTION: Maintenance operations are terminated when the

NE is reset.
6.8.1 Performing SPI Loopbacks

Loopbacks are diagnostic procedures in which a signal is transmitted and returned as
received to the originator. The equipment that originates the looped back signal can thus
receive its own signal for test purposes. Loopbacks are traffic affecting.
Loopbacks can be performed on both East and West SPI interfaces. You can choose from
loopbacks that send traffic back from the interface towards the NE (near) and loopbacks that
send traffic away from the NE (far).
!"To perform SPI loopbacks:
1. From the Maintenance menu, select one of the following options:
!" SPI West Near Loop
!" SPI East Near Loop
!" SPI West Far Loop
!" SPI East Far Loop
NOTE: You can also initiate an SPI loopback by accessing the

SPI’s right-click menu in the View Details window.

The In Maintenance icon in the Card View window is activated, indicating

that a maintenance procedure is in progress. In addition, a hammer icon appears
next to the menu option.
2. To stop a loopback operation, select it again from the Maintenance menu.
CAUTION: Both physical (SPI) and logical STM-1

loopbacks are available, but should be handled with care, as
looping back all the OH bytes could cause the DCC to be
lost.
Loopbacks on Ethernet traffic are not recommended.
6.8.2 Performing Subsystem Maintenance

This section describes the options available in the Maintenance menu of the View Details
window. Multiple maintenance operations may be performed simultaneously. Once a
maintenance operation has been activated, it remains in effect until the operation is turned
off by choosing it again from the pop-up menu. (It is also deactivated if the µLAN NE is
reset, as described in Resetting the NE,
page 6-47.)
The complete list of Maintenance options is listed below.
Table 6-13: Multiplexer maintenance options
Option Description
Force AIS Clicking one of these options toggles on/off the forced sending of the
Alarm Indication Signal (AIS) signal upstream to the SDH interface by
the selected multiplexer.
Force RDI Clicking one of these options toggles on/off the forced sending of the
Remote Defect Indication (RDI) signal by the selected multiplexer.
For example, when the East multiplexer icon is selected, the RDI
indication is sent in the east direction only. This enables you to check
the response of the equipment receiving the RDI, or force rerouting of
the data stream through an alternate path in the network.
Force AIS Clicking one of these options toggles on/off the forced sending of the
Down AIS signal downstream to the PDH interface by the selected
multiplexer.
Loopback Clicking this option toggles on/off the loopback function in the
multiplexer.

Table 6-14: PPI maintenance options
Option Description
AIS Down Clicking one of these options toggles on/off the forced sending of the
AIS (Alarm Indication Signal) signal downstream to the PDH interface
by the selected PPI.
Near End Creates a loopback towards the NE.
Loop
Far End Loop All data received by the NE from the PDH port is looped back away
from the NE.
!"To activate a subsystem maintenance operation:

1. In the View Details window, right-click Multiplexer or PPI, and from the pop-up
menu, select Maintenance followed by the name of the maintenance operation.
The In Maintenance icon in the Card View window is activated, indicating

that a maintenance procedure is in progress. In addition, the subsystem name in the
View Details window is displayed in red, with a hammer icon alongside.
Figure 6-27: Example showing maintenance on multiplexer subsystem
2. To stop a loopback operation, right-click the subsystem and select it again from the
pop-up menu.
6.8.3 Viewing Maintenance Operations
Click the In Maintenance icon in the Card View to view a pop-up window containing
the maintenance operations currently in progress.
Figure 6-28: Maintenance Info window

6.9 Configuring Trace IDs

The Card View application configures the string content of the SDH TTI Trace ID (J0, J1),
which is used to verify continual connections at the link and path levels. For information
about sending this information to the NEs using the Topology Browser, refer to Link Menu,
in Chapter 4, Building the Network.
!"To configure trace IDs:
1. For J0, right-click the Regenerator icon in the View Details window, and then
select J0_J1 # J0 from the pop-up menu,
OR
For J1, right-click the High Order icon, and then select J1_J0 # J1 from the
pop-up menu. The following window is displayed:
Figure 6-29: Trace ID modification
2. Enter the transmitted and expected strings in the fields provided. The received string
is displayed in the Received field.
3. Select the Ignore checkbox to have the EMS-µLAN ignore the SDH Trace ID
information. This option should be used with other ECI products and third-party
equipment that do not support J0/J1 properly.
NOTE: Old µLAN NEs (shipped before July 2001) do not

generate a J0 mismatch alarm when a µSDM-1 NE is
connected (it transmits J0 nulls instead of a proper string).
Therefore, select the Ignore checkbox in older µLAN NEs
when working with µSDM-1 NEs, and whenever the J0/J1
strings are all zeros or nulls.

4. Click Apply to save the new settings.
NOTE: To connect to ECI Telecom products, click Default.
6.10 Defining Advanced Options

The View card info – MU window (see Figure 6-3, page 6-5) provides access to the
Advanced info window that can be used to configure the following:
!" Ethernet frame mapping
!" DCC management channel
!" Orderwire (if available)
!" User channel (if available)
!" LAN/WAN port allocation
NOTE: For more information on the View card info – MU

window, refer to Viewing MU Card Information, page 6-4.
!"To define advanced MU card information:

1. In the View card info – MU window, click Advanced to display the Advanced info
window.
Figure 6-30: MU Advanced info window – Ethernet tab

2. Select the Ethernet tab.

3. In the Next drop-down list in the Ethernet Frame Mapping area, select the
framing type to be used by the mapper: HDLC (High-level Data Link Control),
GFP (Generic Frame Procedure), or Unknown. This option determines the framing
type to be used by the mapper for Ethernet frames on the µLAN NE. Any change
made to the framing type takes effect after the next NE reset.
4. From the East DCC and West DCC drop-down lists, select whether the DCC
management channel is Enabled or Disabled.
5. From the DCC mode control drop-down list, select MS DCC or RS DCC. This
determines whether the DCC is carried in the multiplexer or the regenerator section
of the SOH.
NOTE: For more information about DCC options, refer to the

BroadGate µLAN Installation, Operation and Maintenance
(IOM) Manual.
6. From the Order wire and User channel drop-down lists, select whether these
features are Used or Transparent. Transparent means that the NE does not
include these options. Any orderwire or user channel traffic from other NEs is
passed along transparently to the next NE without being touched.
7. Select the LAN/WAN Setup tab.
Figure 6-31: MU Advanced info window – LAN/WAN Setup tab
WARNING: Flexible LAN/WAN configuration is only

available for new µLANs (version 2.2r2). See your Release
Notes for more information.

8. The Current area displays the current number of LAN and WAN switch ports on
the NE. To change this setting to reallocate the ports, select the required LAN/WAN
port allocation in the Next dropdown list. Eight switch ports can be defined as either
LAN or WAN ports. Between two and six of the available eight switch ports can be
configured as WAN ports on the µLAN NE. Any change you make to the port
allocation takes effect after the next NE reset.
9. Click Refresh to save the settings, and then click Close.
6.11 Resetting the NE

If necessary, you can send a reset command to restart and initialize the µLAN NE.
CAUTION: This action affects network traffic!
!"To reset the µLAN NE:

1. In the View Details window, select Maintenance # Reset Card. The Reset Card
Figure 6-32: Reset Card window
2. Click Reset


7
Configuring and Monitoring
Ethernet Services
7.1 Introduction
The Card View application is used to configure Ethernet traffic in a µLAN network. The
physical LAN ports are used to connect the µLAN to adjacent Ethernet clients, and virtual
WAN ports are used to provide Ethernet connectivity between µLAN NEs.
NOTE: Virtual WAN ports are mapped into n x VC-12 SDH

containers, which are provisioned using either the Trail
Manager (as described in Creating New Trails, in Chapter 5,
Building Trails) or Card View (as described in Building
Trails Using Card View, in Chapter 6, Configuring and
Monitoring µLAN NEs).
While either application can be used, it is important to use
one application consistently and not switch between them.
The number of Ethernet ports to be configured is dependent on the TIU type:

!" TIU-16E1-2Eth – with two physical LAN ports (numbered 1 and 2) and two virtual
WAN ports (numbered 3 and 4)
!" TIU-21E1-6Eth or TIU-21E1-6Eth-VA – with six physical LAN ports (numbered
1 to 6) and two virtual WAN ports (numbered 7 and 8)
!" TIU-14E1-3E3-6Eth – with six physical LAN ports and two virtual WAN ports (by
default; flexible LAN/WAN port allocation is configurable; see Defining Advanced
Options, in Chapter 6, Configuring and Monitoring µLAN NEs, for more details)
!" TIU-21E1-6Eth-A – with six physical LAN ports and two virtual WAN ports (by
default; flexible LAN/WAN port allocation is configurable; see Defining Advanced
Options, in Chapter 6, Configuring and Monitoring µLAN NEs, for more details)
The external LAN ports are used to connect devices such as bridges and routers. The virtual
WAN ports are used for creating Ethernet connections between µLAN NEs.
Cross-connections (trails) are configured over the virtual WAN ports. Both E1 and Ethernet
traffic can be provisioned over an SDH network at a resolution of 2 Mbps.

Configuring and Monitoring Ethernet Services BroadGate™ EMS-µLAN User's Manual
µLAN NEs provide Layer 1 dedicated Ethernet links over SDH, as well as Layer 2
(data-link layer) switching, which incorporates both MAC address and virtual local area
network (VLAN) capabilities to enable shared Ethernet services over SDH.
Figure 7-1: µLAN building blocks
Figure 7-2 shows two µLAN NEs with six LAN ports and two WAN ports. These two
WAN ports enable you to create up to two dedicated n x VC-12 Ethernet over SDH (EoS)
links with optional protection. These ports can also be used as part of a shared Ethernet ring.
The most popular service provided by the µLAN is dedicated, point-to-point Ethernet. This
default service, which comes pre-configured in the µLAN, is created by mapping and
de-mapping Ethernet traffic directly to and from SDH.
Figure 7-2: Dedicated EoS point-to-point links using the µLAN

BroadGate™ EMS-µLAN User's Manual Configuring and Monitoring Ethernet Services
A dedicated point-to-point EoS service is created by using a VLAN (regular or internal) to

connect a LAN port with a WAN port in two #LAN NEs, and then creating an n x VC-12
trail between their WAN ports. The SDH/SONET trail between these ports can be SNCP
protected, providing carrier-class reliability with 50 ms protection at the SDH/SONET layer.
Bandwidth can be provisioned in any 2 Mbps increment, up to the full 100 Mbps.
Figure 7-3: Implementing a PTP service
The base for shared EoS services is usually an Ethernet ring, which is formed by creating
n x VC-12 trails between the WAN ports of multiple #LAN NEs. EoS services can then be
provisioned on top of the ring, which can be built on top of any underlying SDH topology.
As native Ethernet does not support ring topologies, the Rapid Spanning Tree Protocol
(RSTP) is used to provide protection. Once the ring has been built, adding a new service is a
simple matter of configuring a new double-tagged VLAN on the member LAN ports.
Different VLANs are also used for separating different customers.

Figure 7-4: Shared EoS topology
It is important to note that n x VC-12 is the total bandwidth of the shared bandwidth "pool".
This bandwidth can be provisioned in any 2Mbps increment from 2 Mbps up to 100 Mbps
(that is, 1 to 49 VC-12 containers).
7.2 Ethernet Configuration Procedures

Ethernet configuration is performed in the Ethernet Management window, and consists of
the following procedures:
!" Configuring general switching parameters – usually done once, immediately
following installation. This procedure includes defining the switching mode, the frame
size, and whether RSTP protection is enabled, as described in Configuring General
Switching Parameters, page 7-6.
!" Defining the physical port configuration – usually done right before a new service is
provisioned. This procedure includes defining the line speed, the duplex setting, and flow
control, as described in Defining the Physical Port Configuration, page 7-11.
!" Configuring port priorities – done for specific scenarios, immediately following port
configuration, this procedure determines whether high and low priorities are defined
according to the port or according to the frame, as described in Configuring Port
Priorities, page 7-14.

!" Configuring the VLAN tables – done for each new service immediately before
activation. This procedure creates the connections between all member LAN ports, and
includes defining the VLAN IDs of the traffic being transmitted over each port, as
described in Configuring VLAN Tables, page 7-15
!" [Optional] Configuring RSTP protection – usually done once, immediately following
the creation of EoS trails that form an Ethernet ring. Rapid Spanning Tree Protocol
(RSTP) protection prevents bridge loops and enables the network to recover quickly
from a path failure, as described in Configuring RSTP Protection, page 7-27.
The Card View application is also used to define Ethernet alarm settings, as described in
Configuring RSTP Protection, page 7-27, and to view Ethernet port statistics, as described
in Viewing Ethernet Port Statistics, page 7-35.
NOTES: Ethernet capabilities only take effect after defining all

cross-connects and trails, as described in Creating New Trails,
in Chapter 5, Building Trails (or Building Trails Using Card
View, in Chapter 6, Configuring and Monitoring µLAN NEs).
Before creating an Ethernet trail (that is, a group of virtually
concatenated VC-12s) in the EMS-µLAN, the corresponding
VC-12 trails in the XDM® or SYNCOM device must be
created.
eNM trails can either be defined individually using Pathfinder,
or as a group using a predefined ASCII file or the µLAN trailer
(a GUI for creating the ASCII file).
If some of the VC-12 containers fail, the entire EoS link fails.
The Link Capacity Adjustment Scheme (LCAS) is required for
dynamic bandwidth adjustment. This feature will be available
in future versions.

7.3 Configuring General Switching Parameters

The lower half of the Port priority + General configuration tab in the Ethernet
Management window is used to configure a variety of general switching parameters, such as
the priority ratio, the switching mode, and whether RSTP protection is enabled.
For more details about priority configuration per port, see Configuring Port Priorities,
page 7-14.
!"To configure general switching/port parameters:
1. From the Ethernet menu, select VLAN/Line Tables. The Ethernet Management
2. Click the Port priority + General configuration tab to display the following:
Figure 7-5: Ethernet Management window – configuring switching parameters
3. In the General port configuration area, click Refresh general port configuration
to retrieve the current settings.
4. Configure the following switching parameters:
!" Priority Ratio, page 7-7
!" Switching Mode, page 7-7
!" Double tag VLAN, page 7-7

!" Enable Scrambler, page 7-9

!" Enable RSTP, page 7-9
!" Packet size, page 7-10
!" Mac Ad. Aging Time, page 7-10
5. After completing your changes, click OK in the confirmation window.
7.3.1 Setting the Priority Ratio

The Priority Ratio drop-down list in the Port priority + General configuration tab is
used to define the ratio of low-priority frames versus high-priority frames transmitted over
each egress port.
!"To set the priority ratio:
!" From the Priority Ratio drop-down list, select the bandwidth ratio of low-priority
frames versus high-priority frames in each egress port. This configures a weighted
round-robin process that enables fair queuing between high-priority and
low-priority traffic in case of congestion. Available ratios include: 1:1, 1:2, 1:4,
1:6, 1:8, 1:10, and 1:12.
If, for example, if the priority ratio is set to 1:12, twelve high-priority frames are
transmitted before a low-priority frame is transmitted.
Alternatively, you can select the Strict Priority option to guarantee the priority of a
given service. In this case, no ratio is involved and traffic on this service is
guaranteed.
NOTE: The priority ratio works with bidirectional traffic

only (symmetric or asymmetric).
7.3.2 Selecting the Switching Mode

The Switching Mode drop-down list in the Port priority + General configuration tab
enables you to select the switching mode used for Ethernet traffic. The default Tagged mode
enables the use of VLANs for customer separation, reducing broadcast domains and the
logical partitioning of complex Layer 2 networks. Basic mode causes the #LAN to perform
switching based on the source and destination MAC addresses only, which is appropriate for
specific topologies where customer separation is performed at the SDH level.
NOTE: Using Basic mode can leave the #LAN vulnerable to

MAC spoofing and other security risks posed by shared
services.

!"To select the switching mode:

!" From the Switching Mode drop-down list, select Tagged to enable VLAN tagging,
or Basic. If the switching mode is set to Basic, the #LAN performs switching based
only on the source and destination MAC addresses contained in a MAC address
table. It cannot refer to the VLAN ID or to the priority stored in the VLAN header.
7.3.3 Enabling Double-tagging (Nested VLANs, Q-in-Q)

The Double tag VLAN drop-down list in the Port priority + General configuration tab
enables you to choose whether to use double-tagging (nested VLANs). It is highly
recommended to use double-tagging for all applications except ISP/IP-VPN distribution
applications.
Double-tagging is achieved by attaching a provider domain VLAN (P-VLAN) to each LAN
port. (The ID for these P-VLANs is defined in the Port VLAN ID table, as described in Port
VLAN ID (PVID) Definitions, page 7-17.) The P-VLAN is used only in the provider
network and is transparent to the end user.
Double-tagging is typically used in the following scenarios:
!" When a large number of VLAN IDs enter a particular port, making it time-consuming to
define them one by one for each port and enter them into the static VLAN table. By
using double-tagging, it is possible to assign an additional PVID to all incoming frames
on that port without defining each customer VLAN ID (CVID) individually.
!" When an organization does not want to reveal its VLAN tags for security reasons. Using
a double-tag on these frames enables them to be handled by the µLAN using a PVID that
is independent of the CVID. Externally, the frame retains its secure CVID. In addition,
end users are not aware of the VLAN ID being used for them, which enhances security.
!" When the service provider does not want to impose limitations on its customers' use of
VLAN IDs. For example, if customer A is using VLAN ID 15 when using a standard
VLAN, security is improved if other customers are prevented from using the same
VLAN ID. Double-tagging provides greater flexibility and enhanced security by
enabling the service provider to provision different provider domain (internal) VLANs
for different customers. This allows each customer to use any VLAN on its own
network. Customer VLANs are encapsulated within the internal P-VLAN. For example,
if customer A is using CVID 15, which is encapsulated in PVID 2, customer B can still
use VLAN ID 15 in its own LAN, which is encapsulated in PVID 3.
NOTE: ISP and IP-VPN distribution connectivity

applications require multiple VLANs to be defined on a
single port in the POP, which aggregates the traffic from
many different end users. For these applications, define a
regular VLAN for each customer, and then define all these
VLANs on the POP's µLAN port. With these types of
applications, there is no problem using a single P-VLAN for
all customer sites of the same customer.

!"To use double-tagging:

!" From the Double tag VLAN drop-down list, select Yes.
For more information about VLAN configuration, refer to Configuring VLAN Tables,
page 7-15. For special guidelines regarding double-tagging, refer to Special Double-tagging
Configuration Guidelines, page 7-25.
NOTES: Once double-tagging has been activated, it applies

to all ingress ports.
When working with double-tagged VLANs, LAN ports must
be configured as untagged. For more information, refer to
Configuring VLAN Tables, page 7-15.
7.3.4 Enabling the Scrambler

The µLAN uses X.86-based mapping of Ethernet frames to SDH containers. This procedure
includes HDLC encapsulation that uses the 7E interpacket marker (one byte) for control. In
cases where the 7E byte appears inside the frame payload, the transmitting side replaces it
with two bytes (7E/7D), increasing the size of the frame. These larger frames can result in
slightly lower throughput, depending on the number of occurrences of the 7E marker within
the payload.
NOTE: The scrambler is not relevant for GFP mapping.
To achieve more uniform throughput, the scrambling feature in the Port priority + General
configuration tab can be enabled. Scrambling forces the appearance of 7E markers
randomly in each frame, resulting in consistent, if slightly reduced, throughput.
!"To enable the scrambler:
!" From the Enable Scrambler drop-down list, select whether the scrambling feature
for HDLC frames is Enabled (default) or Disabled.
7.3.5 Enabling RSTP Protection

RSTP protection can be enabled either from the Port priority + General config. tab or
directly from the RSTP window.
!"To enable RSTP protection:
!" From the Enable RSTP drop-down list, select Enable. For more information, refer
to Configuring RSTP Protection, page 7-27.

CAUTION: In Ethernet ring configurations, it is important

that RSTP protection be enabled. Generally, when one
physical LAN port is connected to two virtual WAN ports,
RSTP should be enabled in case the EoS connectivity creates
Ethernet loops. For more information about RSTP, refer to
Configuring RSTP Protection, page 7-27.
7.3.6 Configuring the Packet Size

The Port priority + General configuration tab contains a field for selecting whether the
EMS-µLAN should transmit standard-sized Ethernet frames or jumbo frames.
!"To configure the packet size for Ethernet frames:
!" From the Packet size drop-down list, select Regular (for standard-sized frames) or
Large (to accommodate jumbo frames of up to 6000 bytes when HDLC mapping is
used and up to 2000 bytes when GFP mapping is used).
7.3.7 Defining the Aging Time

The Mac Ad. Aging Time field in the Port priority + General configuration tab enables
you to define the aging time, which is the refresh interval for MAC source tables. Entries in
the Forwarding Database (FDB), otherwise known as the MAC address table, are considered
old if no frames arrive from the source MAC address during the interval defined by the
aging time. Should this occur, old entries are deleted from the table and re-learned when
new frames are sent from the source MAC address.
NOTE: Changes made to the port priority (as described in

Configuring Port Priorities, page 7-14) and port priority ratio
(as described in Setting the Priority Ratio, page 7-7) take
effect only after the aging time interval has passed.
!"To define the aging time:

!" In the Mac Ad. Aging Time field, type the refresh interval for MAC source tables
and press Enter. The default period is 300 sec.

7.4 Defining the Physical Port Configuration

It is important to properly define the configuration of the physical Ethernet ports in the
µLAN to ensure a proper handshake between the µLAN and the external devices connected
to its LAN ports. This involves defining the speed and duplex type of each port, as well as
the flow control.
!"To define the physical port configuration:
1. In the Ethernet Management window, click the Line configuration tab to display
the following:
Figure 7-6: Ethernet Management window – Line configuration tab

2. Click Refresh. The current physical parameters for each Ethernet port are displayed
in the Status ports LAN area.
Table 7-1: Physical LAN port parameters
Role Port number. LAN ports include LAN1 through LAN6 and
WAN ports include WAN 1 through WAN6. Flexible
LAN/WAN configuration is available for TIU types
TIU-14E1-3E3-6Eth and TIU-21E1-6Eth-A.
Auto Whether speed and duplex type are configured
Negotiation automatically – On or Off.
Flow Control Whether full duplex flow control, which sends pause
messages whenever the buffer fills up during data bursts, is
On or Off. Flow control is important in cases where the
external device that connects to the µLAN can transmit data
at a rate that exceeds the bandwidth defined for the Ethernet
service.
Half Dx Back Whether the back pressure feature that enables flow control
Pressure functionality for half-duplex ports is On or Off.
Admin. State Port admin state. Whether the port is Enabled or Shutdown.
When the port is disabled, it does not pass any traffic and the
LED for the port on the µLAN front panel is unlit.
Link Status Whether the link is currently connected (Up) or not (Down).
This is a read-only field whose status is also indicated by the
LED on the µLAN front panel.
Line Current Current speed of the link – 10 Mbps or 100 Mbps.
Speed
Current Duplex Current duplex mode – Half or Full. Half duplex is the
Mode default.
HOL Blocking Whether Head of Line (HOL) blocking prevention, which
prevents traffic from being forwarded to a port that is
blocked, is Prevent (on) or Normal (off). HOL blocking
prevention drops frames to prevent other traffic from being
held up by a full egress buffer.
3. When performing mass provisioning, select which ports to configure from the From
port and To port drop-down lists.
NOTE: Changes can also be made one port at a time by

directly editing the fields in the table.
4. In the Line configuration area, select the administrative state from the Admin
state drop-down list.
NOTE: As the default state is Enabled, you may want to

disable any LAN ports that are not being used.

5. From the Speed/Duplex drop-down list, select the speed and duplex mode. The
following selections are available:
!" Auto – port speed and duplex mode are configured automatically
!" 100/FULL – port operation at 100 Mbps and full duplex
!" 100/HALF – port operation at 100 Mbps and half duplex
!" 10/FULL – port operation at 10 Mbps and full duplex
!" 10/HALF – port operation at 10 Mbps and half duplex
6. Click Apply in the Line configuration area of the window.
7. In the Port configuration area, select which ports to configure from the From port
and To port drop-down lists.
8. Select the flow control state, the half duplex back pressure setting and the HOL
blocking state from the drop-down lists provided.
NOTES: It is recommended to not use flow control in a

shared RSTP ring.
When flow control is required for half-duplex ports, activate
both flow control and back pressure.
9. Click Apply in the Port configuration area of the window.
CAUTION: One of the most common causes of errors in

10/100BaseT Ethernet links is the misconfiguration of ports
in a link. This occurs when one port in the link is operating at
half duplex while the other is operating at full duplex. If one
end of a link is set for Auto-negotiation and Auto-negotiation
fails, it sets itself to half-duplex mode.
Table 7-2: Ethernet duplex mismatches
Setting Results
EMS-µLAN Client device EMS-µLAN Client device
Auto Full Half Full
Full Auto Full Half

7.5 Configuring Port Priorities

The Port priority + General configuration tab of the Ethernet Management window
enables you to set the priority tag for frames being transmitted from the physical LAN ports
to the virtual WAN ports. Two types of priorities exist – frame priority and port priority.
Typically, port priorities are assigned when there is a need to give queuing preference to all
the frames over a selected physical LAN port. When this is not needed, priority
classification is done according to the original frame priority, as it appears in the priority
bits of the VLAN header.
For example, when a port priority is set to High, all frames sent over it receive high priority,
regardless of the original frame priority, if any. When the port is assigned a low priority,
priority classification is dependent on the setting in the Allow Priority column of the Port
priority table, as described in Table 7-3.
NOTES: In regular tagging mode, priorities cannot be

assigned to untagged LAN or WAN ports (see VLAN
Definitions, page 7-16). When frames enter the system with
both a priority setting and a VLAN ID, be sure to leave them
tagged, as untagging will cause the priority setting to be
removed.
In double-tagging mode, the provider VLAN ID is stripped
for untagged ports, leaving the original VLAN and priority
tag intact.
!"To configure port priorities:

1. In the Ethernet Management window, click the Port priority + General
configuration tab (see Figure 7-5).
2. Click Refresh port priority table. The Ethernet ports and their current priority
settings are displayed in the Port priority table.
3. In the Port priority configuration area, select which ports to configure from the
From port and To port drop-down lists.
4. Select the port priority (Low/High) from the Priority drop-down list. Setting the
port priority to High overrides any original frame priority settings.
5. For ports defined with a low priority, choose whether to activate port priority from
the Allow drop-down list.

The Priority and Allow drop-down lists work together as described in the following
table:
Table 7-3: Port and frame priority settings
Port priority Allow Resulting priority

Low No Frame priority: Priorities are
classified according to the
priority marked on the original
frames.
Frames with priority
0 to 3 are classified as Low
priority; frames with priority 4
to 7 are classified as High
priority.
High Yes or No High priority: All incoming
frames are treated as 7 (High),
based on the port priority.
Low Yes Low priority: All incoming
frames are treated as 0 (Low),
based on the port priority.
6. In the Apply port priority field, click Apply.

7. Verify that the priority ratio between high- and low-priority traffic is set correctly.
This ratio is selected from the Priority Ratio drop-down list, as described in Setting
the Priority Ratio, page 7-7.
NOTES: Changes can also be made to one port at a time by

directly editing the fields in the table.
The ratio between high- and low-priority traffic is configured
from the Priority Ratio drop-down list, as described in
Setting the Priority Ratio, page 7-7.
7.6 Configuring VLAN Tables

After completing the configuration of the EoS infrastructure (SDH connectivity, switching
configuration, and the port setting), you must define VLANs in order to create Ethernet
services between µLAN Ethernet ports.
The µLAN supports IEEE 802.1q VLANs, which enable the provisioning of VLANs for:
!" Customer separation
!" Logical partitioning of the network
!" Reducing broadcast domains
Up to 4,096 VLANs can be configured, each with a unique identifier.

Ethernet connectivity between the physical LAN and virtual WAN ports is configured using
VLANs. The VLAN configuration tab enables you to define the ports to be used by
incoming and outgoing frames, and how to process these frames. In addition, you can assign
VLAN IDs to incoming frames according to their ingress port.
NOTE: The Switching Mode field in the Port priority +

General configuration tab must be set to Tagged (default) to
enable the use of VLAN tagging. It is highly recommended to
enable double-tagged VLANs, as described in Enabling
Double-tagging (Nested VLANs, Q-in-Q), page 7-8.
7.6.1 VLAN Definitions

!" VLAN – a VLAN enables separate "virtual" LANs to be provisioned over a shared
Ethernet infrastructure, whereby remote devices are connected in a network resembling a
LAN. Frames that belong to the VLAN are identified by a VLAN ID. Multiple VLANs
can be defined by using distinct VLAN IDs. Traffic from different VLANs never mix.
VLAN-tagged frames that arrive at an element are handed to the client port only if the
port is a member of the VLAN marked in the frames’ VLAN ID.
!" VLAN tagged frame – a frame that contains a tag header immediately following the
source MAC address field of the frame. (Tagged frames are four bytes longer than
untagged frames.)
!" VLAN ID header – a tag header containing VLAN identification (VLAN ID)
information to be associated with a frame. It can also include the frame's priority.
!" Untagged frame – a frame that does not contain a VLAN tag header.
!" Priority tagged frame – a frame containing a VLAN header with the VLAN ID of 0
(that is, no VLAN tag), and a priority bit value between 0 and 7.
!" Ingress ports – the physical LAN and virtual WAN ports by which traffic enters the NE.
Frames traveling towards ingress ports are moving in the direction of the WAN. Frames
traveling towards WAN ports are moving in the direction of the LAN. The decision
regarding VLAN ID tagging for incoming frames is done at the ingress port.
!" Ingress rules – classification of each received frame as belonging to one and only one
VLAN.

!" Egress (also called member ports in EMS-µLAN Card View) ports – the physical
LAN and virtual WAN ports by which traffic exits the NE. Frames traveling towards
egress ports 1 through 6 are moving in the direction of the LAN. Frames traveling
towards ports 7 and 8 (ports 3 and 4 in 16E1 units) are moving in the direction of the
WAN. The decision regarding VLAN ID tagging for outgoing frames is done at the
egress port.
NOTE: If the frame is transmitted to an 802.1q-compliant

VLAN, then the VLAN ID should be retained; otherwise, the
VLAN ID tag should be stripped. VLAN ID tags should also be
stripped at the egress of LAN ports when using double-tagging,
as described in Enabling Double-tagging (Nested VLANs,
Q-in-Q), page 7-8.
!" Egress rules – mapping of frames for transmission through the appropriate egress
(outbound) ports, and in appropriate (VLAN-tagged or untagged) format.
7.6.2 Port VLAN ID (PVID) Definitions

In a port-based VLAN classification within the EMS-µLAN, the PVID is the VLAN ID
associated with either an untagged frame or a priority-tagged frame.
The PVID for a given port inserts the VLAN ID value for untagged and priority-tagged
frames received through that port. This means the VLAN ID will be added by the µLAN to
traffic arriving from the port. The PVID is also used to insert the provider domain VLAN ID
(P-VLAN ID) header for incoming frames when working in double-tagging mode.
The Card View application supports all VLAN ID values in the range of 0 to 4095. The
following table lists the reserved VLAN ID values.
Table 7-4: Reserved VLAN ID values
VLAN ID Description
0 Null VLAN ID. Indicates that the tag header contains only user-priority
information; no VLAN identifier is present in the frame.
This VID value is not to be configured as a PVID, configured in any VLAN table
or used in any management operation.
1 Default PVID value. Used for classifying frames on ingress through a port. The
management system can change this PVID value on a per-port basis.
FFF Reserved for implementation use. This VLAN ID value cannot be configured as a
PVID in any VLAN table, used in any management operation or transmitted in a
tag header.

7.6.3 VLAN Default Configuration for PTP Services

By default, all µLAN NEs come pre-configured for point-to-point dedicated services, as
follows:
!" VLAN 2 and VLAN 3 are pre-configured in the static VLAN table:
!" The first LAN port (#1) is connected to the first WAN port (#7) using VLAN 2.
!" The second LAN port (#2) is connected to the second WAN port (#8) using
VLAN 3.
!" All other VLANs pass transparently through the WAN ports.
NOTE: For 16E1 units, the WAN ports are numbered 3

and 4, rather than 7 and 8.
!" Verify that the PVIDs of port #1 (LAN) and port #7 (WAN) are set to VLAN 2, and that
the PVIDs of port #2 (LAN) and port #8 (WAN) are set to VLAN 3, in order to maintain
consistency with the pre-configured VLANs.
!" The PVIDs of the remaining ports are set to VLAN 1 by default.
NOTE: In some units, the default PVID for all ports is

pre-configured to VLAN 1.
!" This configuration enables point-to-point, dedicated (L1) services to be provisioned

without defining any new VLANs.

7.6.4 Configuring the VLAN Tables

The following flowchart describes how the µLAN forwards Ethernet frames, based on the
definitions found in the VLAN tables.
Start
Is Configured Y
mode Double-tag?
Is frame tagged N
(with VLAN ID)?
Y
Assign the PVID
In the VLAN field &
Forward to the Wan/Lan
Is VLAN ID of the frame Is Egress port

defined in the static VLAN Y (Wan/Lan) N Transmit the
Table, the port WAN/LAN Configured as frame as is
belong to? untagged?
Y
N Strip the VLAN ID in the VLAN field
Drop the frame Of the frame & Transmit the frame.
Figure 7-7: VLAN flowchart
The steps required to define VLAN tables are described in the procedure that follows.

!"To configure and view the VLAN tables:

1. In the Ethernet Management window, click the VLAN configuration tab to display
the following:
Figure 7-8: Ethernet Management – VLAN configuration tab
The VLAN configuration tab is divided into the following four areas:
!" TSF/CSF (upper-left)
!" Port VLAN
!" Static VLAN
!" Port selection (bottom-right)
2. Click Refresh to display the contents of the static VLAN table. The tables include
all the VLAN IDs that have been configured in the NE, the name associated with
each VLAN ID (for example, "Customer A") and the VLAN row status (active or
inactive).

The static VLAN table contains the list of VLAN IDs that have been configured in
this window. Selecting a row displays all the information about the corresponding
VLAN ID in the Port Selection area.
NOTES: The VLANs defined here and stored in the Static

VLAN table define the available Ethernet services by
connecting LAN and WAN ports. VLAN IDs not defined in
the table cannot pass over the LAN ports, but they can be
passed transparently between the WAN ports (for example, in
the case of a shared Ethernet ring), which means that VLAN
configuration in µLAN NEs is done only at the service end
points.
The TSF/CSF area displays the VLAN ID on a given WAN port that will be used to
transmit Client Signal Fail (CSF) and/or Trail Server Fail (TSF) indications when
they occur. For more details, see Enabling CSF and TSF Indications,
page 7-24.
The current VLAN table contains a list of all the VLAN IDs configured in the Static
VLAN table, as well as VLAN IDs that have been defined to pass through the
µLAN by other network equipment connected to it, including their current status.
This is the list of all authorized VLAN IDs recognized by the NE, that is, those
VLAN IDs authorized to access the system.
3. The PVID, which is displayed in the Pvid column in the Port VLAN area, is the
default VLAN ID that is automatically assigned to:
!" All incoming frames, when using double-tagging. It defines the provider
domain VLAN assigned to the service LAN port.
!" All incoming untagged and priority tagged frames, when using regular tagging.
The µLAN is shipped pre-configured. Verify the default setting, as described in
VLAN Default Configuration for PTP Services, page 7-18, before initial use.
Change these values according to your service requirements by entering values in
the Pvid field of the required port, pressing Enter, and then clicking OK to confirm
your changes.
The Port field indicates the number of the Ethernet interfaces to which PVIDs will
be assigned. For example, when working with the TIU-21E1-6Eth, this table
displays eight rows (for LAN/WAN ports, depending on the flexible LAN/WAN
port configuration you defined; see Defining Advanced Options, in Chapter 6,
Configuring and Monitoring µLAN NEs, for more details).
NOTE: Click Refresh to display the updated contents of the

Static table and the Port VLAN table.

4. [Optional] In each row of the table, select or clear the Port Ingress Filtering
checkbox to handle frames that already have VLAN IDs when received from the
client. When this option is selected, only frames with VLAN IDs that are defined
for the ingress port in the static port are accepted. Frames with other VLAN IDs are
filtered out and dropped. Frames without a VLAN ID are assigned the default
PVID.
NOTE: It is recommended to leave the Port Ingress

Filtering checkboxes selected for all ports. Clearing this
option allows all frames to be transmitted in the direction of
the egress ports, which might expose the service to security
threats or place an unnecessary load on the system.
5. After every change in the Port VLAN area, press Enter, and then click OK in the
displayed confirmation window to confirm the change. Click Refresh to refresh the
table.
NOTE: To view an existing VLAN, select a row in the Static

VLAN table. Port information about the selected VLAN ID is
displayed in the Port Selection area in the lower-right corner
of the tab. The name of the VLAN and its status are displayed
in the Static VLAN table.
6. To configure a new VLAN, use the Port Selection area, as described below.
The Port Selection area in the lower-right corner of the VLAN configuration tab
enables you to define the path of each incoming and outgoing frame. The number of
LAN and WAN ports displayed in this area depends on the parameters defined in
the LAN/WAN Setup tab in the Advanced Info window (see Defining Advanced
Options, in Chapter 6, Configuring and Monitoring µLAN NEs, for more details).
You define the rules for every VLAN on the LAN and WAN ports, including the
member (egress) and/or untagged ports for the VLAN being configured, as follows:
!" Member Ports – defines the port members of the VLAN being configured, and
creates connections between the physical LAN and virtual WAN ports by which
traffic enters and leaves the NE. Marking two or more ports as member ports for
a particular VLAN ID means that frames with that VLAN ID can be transmitted
only between the member ports. This creates inherent separation between
services, and also reduces broadcast domains.
!" Untagged Ports – when a frame with a VLAN ID leaves the system on an
untagged port, the outmost VLAN header is stripped. This means that an
outgoing frame will no longer contain a VLAN ID, unless it is a double-tagged
frame, as described on page 7-7. In that case, only the P-VLAN header is
stripped, leaving the original VLAN header (if any) intact.

NOTE: The WAN ports act as VLAN trunks for VLANs that
are not defined in the VLAN table, as follows:
!" After a VLAN is explicitly provisioned in a µLAN NE, it is
carried within the NE according to the defined VLAN
members only. In other µLAN NEs, these VLANs pass
transparently over the WAN ports.
!" After a VLAN is deleted from the µLAN NE's VLAN table,
it can pass transparently through that NE's WAN ports.
7.6.5 Creating a New VLAN

!"To create a new entry in the Static VLAN table:
1. In the Member Ports field, located in the Ports Selection area in the lower-right
corner of the VLAN configuration tab, create the service by selecting the member
ports for the configured VLAN ID.
2. In the Untagged Ports field, select the ports through which frames with this
VLAN ID have their outmost VLAN header removed before leaving the µLAN.
3. In the VLAN ID field, enter a unique ID for this VLAN. This can either be the
default VLAN ID or a VLAN ID assigned by other equipment connected to the
µLAN.
4. In the VLAN Name field, enter a unique name for the VLAN.
NOTE: To clear the settings in the Port VLAN area, click

Clear.
5. [Optional] To enable CSF and/or TSF indications to be sent when detected on this
VLAN, select the CSF and/or TSF checkbox. For more details, see Enabling CSF
and TSF Indications, page 7-24.
6. Click Apply to save the settings.
7. Click Refresh to confirm that the new VLAN ID has been added to the table.
8. If any member port was defined as an untagged port, verify that the value in the
Pvid field in the Port VLAN table for that port is assigned the same VLAN ID as
the VLAN that was just configured. For more information, refer to Configuring
VLAN Tables, page 7-15.
NOTE: As only one PVID is allowed per port, a port should

not be an untagged member of more than one VLAN.
9. Repeat steps 1 through 8 to define additional VLAN IDs.

10. Click Refresh, and review the Static VLAN and Port VLAN tables to verify that all
VLANs have been configured correctly.
CAUTION: In cases where RSTP is required to prevent

Ethernet loops (for example, for Ethernet ring configurations),
verify that it has been enabled, as described in Enabling RSTP
Protection, page 7-9. For more information about RSTP, refer
to Configuring RSTP Protection, page 7-27.
7.6.6 Enabling CSF and TSF Indications

To provide better service transparency and facilitate troubleshooting efforts, you can
enable/disable the sending of Client Signal Fail (CSF) and Trail Signal Fail (TSF) alarm
indications, when such conditions are detected on a port or in the network. These options
can be enabled/disabled in the Configuration tab of the Ethernet Management window. The
CSF/TSF feature works in conjunction with GFP mapping. Therefore, GFP must be used as
the Ethernet frame mapping type. If the HDLC mapping type is used, the CSF and TSF
checkboxes are not available. For more details about the GFP and HDLC mapping options,
see Defining Advanced Options, in Chapter 6, Configuring and Monitoring µLAN NEs.
When the CSF checkbox is selected for a WAN port (meaning, it is enabled), CSF
indications are sent to the other-side endpoint when a failure in the physical Ethernet port is
detected on one side of the service. When the TSF checkbox is selected, TSF indications are
sent to the other-side endpoint when a transmission failure is detected. In this case, the
other-side endpoint receives a message to shut down the LAN port.
The following conditions apply for CSF/TSF use:
!" Static VLANs cannot be deleted without first disabling TSF/CSF.
!" CSF and TSF indications only affect member ports. They do not affect untagged ports.
!" CSF only works in point-to-point configurations.
!" When the CSF checkbox is selected, thereby enabling CSF indications to be sent when
detected on the port, no other traffic can be on the LAN and there cannot be another
VLAN from this WAN port.
!" With LCAS, TSF only applies when all containers are down. (This option will be
supported in a future version.)

When CSF or TSF is enabled for a WAN port, the TSF/CSF area of the window shows the
VLAN ID to be used to carry the CSF/TSF indication on the WAN port. For example, in the
example here, CSF indications are enabled for VLAN ID 10 on WAN port 1.
Figure 7-9: Example showing CSF/TSF VLAN IDs
7.6.7 Special Double-tagging Configuration Guidelines

Double-tagging is the recommended default switching mode, as described in Enabling
Double-tagging (Nested VLANs, Q-in-Q), page 7-8.
VLAN configuration is generally the same whether or not double-tagging is used, with two
important exceptions:
!" LAN ports must be defined as untagged when using double-tagging. Otherwise, the
internal P-VLAN tag will be retained when transmitting frames to its destination in the
LAN.
!" The PVID for the member LAN and WAN ports in the Port VLAN table must match the
VLAN ID for the service, as defined in the Static VLAN table.

Below are some useful rules for easier provisioning:

!" For dedicated point-to-point applications, verify that the PVIDs of port #1 (LAN) and
port #7 (WAN) are set to VLAN 2, and that the PVIDs of port #2 (LAN) and port #8
(WAN) are set to VLAN 3, to maintain consistency with the VLANs that come
pre-configured.
!" Working with double-tagged VLANs adds four bytes to each frame. In dedicated
point-to-point applications, where customer separation is done at the SDH/SONET layer,
it is possible to define the WAN port as untagged, which enables higher throughput for
customer traffic.
7.6.8 Modifying VLAN Tables

!"To modify an entry in a Static VLAN table:
1. In the VLAN configuration tab, select the row in the table with the entry to be
modified. The port information is displayed in the lower-right corner of the window.
2. Modify the information as required.
3. Click Apply.
NOTE: If you change the VLAN configuration and refresh

the tables without clicking Apply, the changes do not take
effect. However, the unsaved changes are still displayed. In
such cases, click the appropriate row in the Static VLAN
table, or click Refresh All to restore the saved VLAN
configuration.
7.6.9 Deleting Entries from VLAN Tables

!"To delete an entry in a Static VLAN table:
1. In the VLAN configuration tab, select the row in the table with the VLAN entry to
be deleted.
2. Click Remove.

7.7 Configuring RSTP Protection

RSTP, as defined by IEEE 802.1w, is used to avoid bridge loops in Ethernet networks.
RSTP is based on the Spanning Tree Protocol (STP), which builds a minimal spanning tree
based on the shortest path between any two elements. RSTP uses an algorithm that enables
bridges to understand the topography of the network. When multiple paths (potential loops)
exist, the protocol determines the shortest path based on bandwidth considerations, the
number of hops required, as well as the "cost" of each hop. If the path fails, the protocol
reconfigures the network to activate another path, enabling the network to recover from the
failure. In case of topology changes, the protocol automatically builds a new minimal
spanning tree that accommodates the changes. As a result, RSTP provides an automatic,
Ethernet-based protection mechanism. RSTP improves on the original STP by significantly
improving recovery times, thus cutting down on data loss and session timeouts.
In a #LAN-based Ethernet ring, RSTP designates one #LAN in the network as the root
(typically the NE at the hub site, if any) to which all other NEs refer. It keeps the protection
route blocked until such time as it may be needed. As a general rule, it is recommended to
work with RSTP whenever the EoS topology (for example, a shared Ethernet ring) might
create bridge loops. RSTP should be disabled for topologies where loops do not occur, for
example, when operating point-to-point or point-to-multipoint applications over dedicated
SDH links.
NOTE: When working with RSTP, both virtual WAN ports

must be selected as egress ports. This enables the frame to
travel over the other port when the first is faulty. For more
information, refer to Configuring VLAN Tables, page 7-15.

!"To configure RSTP protection:

1. From the Ethernet menu of the Card View window, select RSTP to display the
following:
Figure 7-10: Configuring RSTP protection
The RSTP window is divided into three sections:

!" The upper section is used to monitor the RSTP bridge (NE) status
!" The middle section is used to configure the RSTP bridge (NE) configuration
!" The lower section is used to configure the RSTP port configuration and contains
two tabs, one for basic and one for advanced parameters
2. Click Refresh fields to retrieve the current data.

3. In the RSTP bridge configuration area, edit the following fields, as required:
Table 7-5: Configurable RSTP fields
Field Description
Basic
Enable RSTP Whether RSTP protection should be enabled or disabled.
(This can also be performed in the Port Priority +
General configuration tab, as described in Configuring
General Switching Parameters, page 7-6.)
Bridge priority Select the bridge priority of the bridge ID. The bridge
with the highest priority (the lowest number) is used for
blocking.
Advanced
Bridge hello time Hello Time value (in seconds) that all NEs use when this
NE is the root.
Bridge max age Maximum Age value (in seconds) that all NEs use when
this NE is the root. It is recommended to have this value
be more than, or equal to, 2 x (Bridge hello time +1).
Bridge forw. delay Forward Delay value (in seconds) that all NEs use when
this NE is the root.
STP Tx hold count Maximum packet rate transmitted by the NE.
STP path cost default Default path cost to use when the actual cost of a
potential path cannot be calculated.
Enable RSTP for Uses the same instance of RSTP for both the customer
LAN and the #LAN network, instead of dropping customer
Bridge Protocol Data Units (BPDUs). This feature
should not be activated.
NOTE: ECI Telecom currently recommends using the

default values in the fields described in Table 7-5.
In version 2.1, the following fields cannot be configured:
Bridge forw. delay, Bridge max age and Bridge hello
time.

In addition, the upper half of the window contains the read-only fields described in
the following table. These fields contain default values and must not be changed.
Table 7-6: Read-only RSTP fields
Field Description
Basic
Designated root Bridge identifier of the root of the spanning tree, as
determined by the Spanning Tree Protocol executed by this
node. This value is used as the Root Identifier parameter in
all configuration bridge Protocol Data Units (PDUs)
originated by this node.
Root cost The "cost" of the path from the selected NE to the root NE.
Root port Port on the NE from where the lowest-cost path to the root
NE begins.
Advanced
Max age Maximum amount of time for which PDU information is
correct (in hundredths of a second). After this interval, the
information is discarded.
Hold time Minimum interval (in hundredths of a second) between the
transmission of two confirmation bridge PDU frames.
Topology changes Number of topology changes detected by the selected NE
since launching or resetting the EMS-#LAN.
Time since topol. Elapsed time since the last network topology change
change identified by RSTP (in hundredths of a second). Examples
of changes include added or removed links, and links that
failed and were re-established.
Hello time Interval between PDU frames (in hundredths of a second)
sent by ports of the root bridge or of a bridge attempting to
become the root bridge.
Forward delay The time it takes (in hundredths of a second) for the NE to
change from a non-forwarding state to a forwarding state.
STP version RSTP version being used. Do not change this value unless
it is absolutely required to communicate with a particular
NE.
Protocol Implemented standard – IEEE 802.1w (compatible with
specification STP).
NOTE: It is not recommended to use RSTP simultaneously

with Subnetwork Connection Protection (SNCP).

7.7.1 Defining the Root and Blocking Elements

When configuring RSTP protection, it is recommended to define which #LAN NE should
act as the root for the rest of the network. In cases of hubbed traffic, the NE located at the
hub site is usually selected as the root NE. You can also define the blocking element, which
is used to prevent traffic cycling, and the blocking port, which is the port located furthest
from the root element.
NOTE: Starting with version 2.1, the root of the RSTP tree is
determined according to the lowest bridge priority. Blocking
ports are either defined automatically (recommended), or by
using the advanced parameters described in Table 7-5.
!"To define the root element and the blocking port:

1. Open the Card View window of the #LAN NE that will act as the root element.
From the Ethernet menu, select RSTP.
2. Select a value from the Bridge priority drop-down list that is lower than every
other NE in the network. This defines the NE as the root element. The EMS-#LAN
automatically determines the blocking element based on proximity and path location
calculations.
3. To manually define the blocking port, open the Card View window of the desired
blocking element. From the Ethernet menu, select RSTP.
4. In the lower half of the RSTP window, click the STP port configuration tab and
then click Refresh to view the current settings.
5. Select one of the virtual WAN ports (the last two ports in the port list).
6. Set the Path Cost to be higher than the setting for the other virtual WAN port. This
enables blocking to take place.
7.7.2 Viewing STP Port Configuration

The STP port configuration tab, located in the lower half of the RSTP window, contains a
table with the following configuration information:
Table 7-7: STP port configuration parameters
Port Port number.
Priority Port priority (within the NE), which is contained in the
first octet of the port ID.
State Current state of the port.
Enable Whether or not the port is enabled.

Path Cost The contribution of the selected port to the path cost.
When a #LAN NE is in the blocking state, the virtual
WAN port with the highest port path cost is defined as the
blocking port, as described on page 7-31.
Designated Root Port ID of the root element in terms of BPDUs received.
Designated Cost Path cost recorded from BPDUs received on the selected
port.
Designated Bridge ID of the #LAN NE that is the next hop towards the root.
Designated Port Port of the #LAN NE that is the next hop towards the root.
Forward Transitions Number of times this port has changed between
nonforwarding and forwarding states.
Click Refresh to retrieve the current data.
7.7.3 Viewing Port-specific RSTP Details

The RSTP ext. tab, located in the lower half of the RSTP window (see Figure 7-10),
contains a table with the following port-specific RSTP information:
Table 7-8: Port-specific RSTP parameters
Port Number Port number.
Protocol Migration Whether RSTP frames (True) or STP frames (False) are
sent.
Admin Edge Port Whether the selected port is an administrative edge
port – True or False. When set to True, the port does not
send BPDUs until it receives a BPDU.
Oper Edge Port Whether the port remains an edge port after receiving
BPDUs (True) or becomes a regular port (False).
Admin Point to Point The administrative point-to-point status of the element
attached to this port. Force True indicates the port should
be treated as if it is always connected to a point-to-point
link. Force False indicates the port should be treated as
having a shared media connection.
Oper Point to Point Whether auto-detection has been activated to locate
administrative point-to-points ports – True or False.
Admin Path Cost The contribution of the selected port to the port cost. A
value of 0 indicates that the default cost should be used.
Click Refresh to retrieve the current data.

7.8 Defining Ethernet Alarm Settings

The Card View application enables you to define which Layer 2 line and traffic problems
should generate alarms in the system. (By default, all settings are enabled for all ports.)
These settings can be customized for each virtual and physical Ethernet port.
!"To define Ethernet alarm settings:
1. From the Ethernet menu, select Alarms to display the following:
Figure 7-11: Ethernet Alarms window – Traffic Error Alarms tab
2. The Traffic Error Alarms tab (see Figure 7-11) contains a table for choosing
whether to send alarms related to the LAN or WAN ports in the following cases:
!" Ignore In Errors – when the number of errors in incoming frames exceeds the
defined threshold
!" Ignore Dropped Packets – when the number of frames dropped by the port
exceeds the defined threshold
!" Ignore Fragments – when the number of fragments received by the port
exceeds the defined threshold
Click in each cell and select either Off (that is, send alarms) or On (that is, ignore
this situation) from the drop-down list.

3. The Line Alarms tab contains a table for choosing whether to send alarms related
to the physical LAN ports.
Figure 7-12: Ethernet Alarms window – Line Alarms tab
Alarms can be sent in the following cases:

!" Ignore Link Down – when the link fails in the selected physical LAN port
!" Ignore Auto Negotiation – when auto-negotiation fails in the selected LAN
port
!" Ignore Partner Link Down – when the link fails in the far-end LAN port to
which this port is connected
!" Ignore Partner Auto Negotiation – when auto negotiation fails in the far-end
port to which this LAN port is connected
Click in each cell and select either Off (that is, send alarms) or On (that is, ignore
this situation) from the drop-down list.
4. In the Ethernet Thresholds tab, enter threshold values for each traffic error type. If
the counter for a particular error type exceeds this threshold, and the error is
activated (that is, set to Off – do not ignore) on the affected port, an alarm is
generated.
Figure 7-13: Ethernet Alarms window – Ethernet Thresholds tab
5. Click Refresh to save the new settings.

7.9 Viewing Ethernet Port Statistics

The Port Statistics menu enables you to view RMON statistics for each physical LAN and
virtual WAN Ethernet port in the selected µLAN NE. It is recommended to periodically
check these statistics to help optimize Ethernet and RSTP traffic.
NOTES: The procedure for defining the settings used to

display port statistics is described in Setting Port Statistics,
page 7-39.
RMON historical data can be viewed in the Alarm and PM
Viewer, as described in Chapter 8, Using the Alarm and PM
Viewer.
!"To view Ethernet port statistics:

1. From the Port Statistics menu, select Show Port Statistics.
2. Click the Charts tab to display the following:
Figure 7-14: Performance Chart window – Charts tab

3. Select the checkbox next to each parameter you want to monitor and click Start
Polling.
NOTE: The chart is automatically reset every 15 minutes. It

can also be manually reset by clicking Restart Graph.
Historical data can be viewed in the Alarm and Performance
Viewer, as described in Analyzing Performance, in
Chapter 8, Using the Alarm and PM Viewer.
The Charts tab of the Performance Chart window provides counters for many
monitored parameters, including:
!" Kbytes – increases by one for every data octet of good frames (Unicast + Multicast
+ Broadcast) received
!" Packets – increases by one for every good frame (Unicast + Multicast + Broadcast)
received
!" Broadcast Packets – increases by one for every good Broadcast frame received
!" CRC Align Errors – increases by one for every frame received that meets the
following conditions:
– The frame data length is between 64 and MAX-FRAMESIZE bytes, inclusive
(that is, valid frame data length according to the IEEE standard)
– The frame has an invalid cyclic redundancy check (CRC)
– Undetected collision event
– Undetected late collision event
– Undetected Rx error event
!" Multicast Packets – increases by one for every good Multicast frame received
!" Undersize Packets – increases by one for every received frame which meets the
– The frame data length is lower than 64 bytes
– The frame has a valid CRC

!" Oversize Packets – increases by one for every received frame that meets the
– The frame data length is greater than MAX-FRAMESIZE
– The frame has a valid CRC
!" Jabbers – increases by one for every received frame that meets the following
conditions:
– The frame data length is greater than MAX-FRAMESIZE
– The frame has an invalid CRC
!" Drop Events – increases by one for every dropped frame received
!" Packets 64 Bytes – increases by one for every received and transmitted frame of 64
bytes
!" Packets 65-127 Bytes – increases by one for every received and transmitted frame
of 65 to 127 bytes
of 128 to 255 bytes
of 256 to 511 bytes
!" Packets 512-1023 Bytes – increases by one for every received and transmitted
frame of 512 to 1023 bytes
!" Packets 1024-1536 Bytes – increases by one for every received and transmitted
frame of 1024 to 1536 bytes
!" Fragments – increases by one for every received frame that meets the following
conditions:
– The frame data length is lower than 64 bytes, or a frame without a start frame
delimiter (SFD) that is lower than 64 bytes in length
– The frame has an invalid CRC

!" Collisions – increases by one for every received frame that meets the following
conditions:
– Detected collision event
NOTE: Counters include received and transmitted frames, as

well as dropped and locally received frames. Counters do not
include received frames that were rejected.
The bottom of the Performance Chart window includes the following options and buttons:
Table 7-9: Performance Chart window options
Option Description
Top Select the checkbox to display port statistics in the upper half of the
window. Select which Ethernet port to display from the numbers displayed
in the drop-down list. 1 and 2 (or 1 to 6, depending on the TIU card) refer
to physical LAN ports; 3 and 4 (or 7 and 8) refer to virtual WAN ports.
Bottom Select the checkbox to display port statistics in the lower half of the
window. Select which Ethernet port to display from the numbers displayed
in the drop-down list. 1 and 2 (or 1 to 6, depending on the TIU card) refer
to physical LAN ports; 3 and 4 (or 7 and 8) refer to virtual WAN ports.
Check All Select the checkbox to include every available measurement in the graphs
and/or tables.
Restart Manually causes the graph(s) to start over from the origin.
Graph
Start/Stop Manually starts/stops the polling process.
Polling
Close Closes the Performance Chart window.

7.9.1 Setting Port Statistics

The Settings tab of the Performance Chart window enables you to define how port statistics
are displayed in the Charts tab. This includes the polling interval, the range of the X-axis
and whether to display the information in both graphical and tabular form.
!"To set port statistics:
1. From the Port Statistics menu, select Show Port Statistics.
2. Click the Settings tab to display the following:
Figure 7-15: Performance Chart window – Settings tab
3. In the Poll interval field, use the slider to set the interval (in seconds) between
polling attempts on the Ethernet ports.
4. Select one of the following X-axis options:
!" Enter values (in minutes) in the X-axis Min and X-axis Max fields, as required,
OR
Select the Use Default x Min/x Max checkbox to use the default axis values.
5. Select the Absolute time checkbox to have the X-axis display the absolute elapsed
time until the full range is reached.
6. Select the Dynamic show legend values checkbox to include a legend describing
each line displayed in the chart.

7. Select the Show top chart checkbox to have port statistics displayed in graphical
form in the top half of the Charts tab. The port to be displayed is selected from the
drop-down list at the bottom of the window.
8. Select the Show bottom chart checkbox to have port statistics displayed in
graphical form in the bottom half of the Charts tab. The port to be displayed is
selected from the drop-down list at the bottom of the window.

8
Using the Alarm and PM Viewer
8.1 Overview
Performance data and alarms generated by the μLAN systems in the network are managed
by an EMS-μLAN station. They are collected and stored in the EMS-μLAN station
database, where they are available for analysis at any time.
To enable efficient utilization of the collected data, the EMS-μLAN includes a dedicated
utility, the Alarm and PM Viewer, which is accessed from the Topology Browser.
This chapter provides instructions for using this utility, and is organized as follows:
!" Alarms – describes the alarm processing operations that can be performed using the
Alarm and PM Viewer, as described in Analyzing Alarms, page 8-5
!" Performance – describes the analysis activities that can be carried out using the Alarm
and PM Viewer, as described in Analyzing Performance, page 8-9
NOTES: In integrated mode, SDH and RMON performance

history data is available in the EMS-µLAN database on the
management station PC. This data can be accessed using
software emulation to display the PC screen on the Sun
workstation running the NMS, as described in Operating the
EMS-μLAN Remotely, in Chapter 3, General Operating
Instructions.
Performance statistics can also be collected via SQL, as
described in Appendix A, SQL Reference.
8.2 Starting the Alarm and PM Viewer

!"To start the Alarm and PM Viewer:
1. Select an NE in the Topology Browser.
2. Right-click the element and select View Alarms from the pop-up menu,
OR
Select Views # View Alarms and Performances from the main menu.

Using the Alarm and PM Viewer BroadGate™ EMS-µLAN User's Manual
8.2.1 Alarm and PM Viewer Window

The Alarm and PM Viewer window includes the following main elements:
!" Menu bar – described in Alarm and PM Viewer Menu Bar, page 8-3.
!" Toolbar – contains icons that provide shortcuts to the menu items that are most often
used. It is described in Alarm and PM Viewer Toolbar, page 8-4.
!" Network elements list – the network elements list is located on the left side of the
Alarm and PM Viewer window. The list displays all the elements that can be managed
by the EMS-μLAN station via the current management connection. It also enables you
to select an element for analysis. Each NE is identified by an icon and its logical name.
The color of the icon represents the status of the element (the color corresponds to the
alarm with the highest severity in the element). Select the checkboxes next to the
elements for which you wish to display data.
!" Alarm severity list – select the checkboxes next to the alarm severity levels that you
wish to display and/or the performance parameters you wish to view.
!" Time interval list – select the checkboxes to determine which alarms to display: all
alarms generated during a defined time interval, all current alarms, archived alarms, or
any combination of these options. The time interval currently selected for analysis is
displayed at the top of the work area. When the window first opens, the last selected
interval is used as a default. In addition, there is a checkbox for determining whether to
display alarms that have already been acknowledged.
!" Work area – select the activity to perform by clicking one of the following tabs at the
top of the work area: Alarms, Performance, Graph, RMON perf., and RMON
graph.
!" Status bar – displays messages that indicate the status of the activity being performed.
The status bar is optional (its display is controlled via the View menu).

BroadGate™ EMS-µLAN User's Manual Using the Alarm and PM Viewer
8.2.2 Alarm and PM Viewer Menu Bar

The menu bar of the Alarm and PM Viewer window includes the following items:
Table 8-1: Alarm and PM Viewer menu bar
Option Description
File Opens a menu with the following options:
Print Opens the standard Windows print window to
enable you to print the selected information (alarm
list or performance data).

Print Preview Opens the standard Windows print preview
window to enable you to check the appearance of
the printout.

Page Setup Opens the standard Windows page setup window
to enable you to define the format of the printout.
Export as Comma Exports the selected information as a file in the
Delimited File comma delimited format.
The file name and location are selected by means
of a standard Windows Save As window.

Export as HTML Exports the selected information as an HTML file.
File The file name and location are selected by means
of a standard Windows Save As window.

Exit Closes the Alarm and PM Viewer window.
View This menu includes two items, Toolbar and Status Bar, used to toggle
the display of the toolbar and status bar, respectively. A checkmark
indicates that the display of the corresponding bar has been enabled.
Settings Opens a menu with the following options:
Set Date Time Opens a submenu which is used to select the
interval for analysis:
Set Date Time Today – selects the information
collected today.
Set Date Time Yesterday – selects the
information collected yesterday.
Select Date Time Interval – displays a window
for selecting the desired interval.

Option Description
Set Columns Opens a window for defining the columns
(performance statistics items) in the tabular
performance display. You can also change the
names of the columns.

Sound Used to define which alarm severity levels trigger
sounds.
Update Used to update the information.
Help Used to display copyright and version information for the Alarm and PM
Viewer utility.
8.2.3 Alarm and PM Viewer Toolbar

The toolbar displayed in the Alarm and PM Viewer window includes the following icons:
Table 8-2: Alarm and PM Viewer toolbar
Icon Description
Print: Prints the information displayed in the work area
Print Preview: Displays a preview of how the information to be printed will

appear
Export as Comma Delimited File: Exports the information displayed in the

work area to text file that can be read with text editors, such as Notepad
Export as HTML File: Exports the information displayed in the work area as
an HTML file
Set Date/Time: Enables you to set the date and time interval of the information
displayed in the work area, as described in Selecting the Analysis Interval,
page 8-6
Select Columns: Enables you to select which columns to display in the work
area
Update Alarms Automatically: Triggers the system to automatically update the
alarms displayed in the work area
Sound: Enables you to define which alarm severity levels trigger sounds, as
described in Defining Sound Settings, page 8-8
Update: Enables you to manually update the alarms displayed in the work area.
The toolbar is optional; its display is controlled by the View menu.

8.3 Analyzing Alarms

!"To display the alarm information:
1. Select the alarm analysis mode by clicking the Alarms tab.
2. Select the desired NE using the NE list.
3. Select the analysis interval using the Set Date Time option in the Settings menu.
4. Select the severity level of the alarms to be displayed using the Alarm type area.
5. Select between viewing current alarms, alarms belonging to a defined time interval,
or the complete history.
6. Select the Acknowledged checkbox to display alarms that have already been
acknowledged. When this checkbox is not selected, these alarms are hidden from
view.
7. Click the Update icon in the toolbar.
Figure 8-1: Alarm and PM Viewer window – Alarms Mode display
8.3.1 Selecting an NE
Elements are selected from the NE list. Click the checkboxes next to the elements whose
alarms are to be displayed. Next, select the alarm severities to display, as well as the alarm
types (current, archived, and/or according to a defined time interval).
You can now proceed with the selection of the analysis interval, as described in Selecting
the Analysis Interval, page 8-6. If the interval currently displayed at the top of the work area
is still relevant, skip directly to the selection of the alarm display parameters, as described in
Displaying the Selected Alarms, page 8-7.

8.3.2 Selecting the Analysis Interval

If you have selected the option of displaying alarms belonging to a specific date/time
interval (as described in Selecting an NE, page 8-5), select Settings # Set Date Time to
display the interval selection submenu. You have the following options:
!" Set Date Time Today – selects the alarm information collected today.
!" Set Date Time Yesterday – selects the alarm information collected yesterday.
!" Select Date Time Interval – displays a range selection window for selecting the desired
interval. A typical window is shown in Figure 8-2.
The Range Selection window includes two sections, one for selecting the start time, and the
other for selecting the end time. Each section enables you to select the year, month, date,
and time (with a resolution of one second). After selecting the desired start and end times,
click Set Range. Alternately, you can click Use default to select the whole period for which
performance data is available.
Figure 8-2: Range Selection window
After defining an interval, select the Use Date/Time Interval checkbox in the Alarm PM
Viewer window to implement it.

8.3.3 Displaying the Selected Alarms
At this stage, you can display the selected alarms by clicking the green arrow on the
toolbar, or by selecting Settings # Update. A typical alarms display is shown in
Figure 8-1.
The window includes a table with the following columns:
Table 8-3: Alarm details
Column Description
Acknowledged Alarms that have not been acknowledged by the operator display the word
NO on a green background. Acknowledged alarms display the word YES on
a red background. (These alarms are displayed only when the
Acknowledged checkbox is selected.)
NEiD NE identification (its management IP address).
Date Time The data and time the alarm has been reported by the NE.
NOiD The alarm name. Currently, the window displays the ECI Telecom MIB
string that describes the alarm. The ECI Telecom MIB is a private
(enterprise-specific) MIB identified by 1.3.6.1.4.1.3413. You can
obtain the MIB in ASN.1 format by contacting ECI Telecom's Optical
Networks Division.
Severity Alarm severity level. The severity level is also graphically indicated by the
background color of the alarm line.
Status On indicates that the alarm condition is still present.
Off indicates that the alarm condition is no longer present.
Processed No indicates that the alarm has not been acknowledged.
Yes indicates that the alarm has been acknowledged.
Correlated 1 indicates that the alarm condition is caused by another alarm.
0 indicates that the alarm condition is not caused by another alarm.
Alarm Desc. Displays a description of the alarm.
Alarm ID Displays the unique ID number of the alarm type.
NOTE: Use the Columns window to customize which

columns to display, as described on page 8-13.
You can change the alarms displayed in the table at any time, either by repeating the
filtering process (selection of interval and parameters, as described in Selecting the Analysis
Interval, page 8-6), or by using the same filtering parameters for another element (as
described in Selecting an NE, page 8-5).

8.3.4 Acknowledging Alarms

Acknowledging an alarm tells the system that the operator has seen a particular alarm.
Alarms can also be unacknowledged, if required.
!"To acknowledge alarms:
In the Alarms tab, right-click the Acknowledged cell of the selected alarm and select
Acknowledge from the pop-up menu. The cell turns red and displays the word YES.
!"To unacknowledge alarms:
In the Alarms tab, right-click the Acknowledged cell of the selected alarm and select
Unacknowledge from the pop-up menu. The cell turns green and displays the word NO.
8.3.5 Defining Sound Settings

The Alarm and PM Viewer enables you to determine which alarm severity levels trigger a
sound whenever an alarm of that severity is generated by the system.
!"To define sound settings:
1. Click on the Alarm and PM Viewer toolbar.

The Sound settings window is displayed.
Figure 8-3: Sound settings window
2. Select the checkbox next to each alarm severity level that should trigger sounds.
3. Click Set parameters.

8.4 Analyzing Performance

The Alarm and PM Viewer enables you to view SDH performance data, as well as RMON
data for the Ethernet ports in the μLAN NE.
!"To display the desired performance data:
1. Select the performance analysis mode by clicking the Performance tab (for SDH)
or the RMON Perf. tab (for Ethernet).
2. Select the desired NE from the network elements list, as described in Selecting an
NE, page 8-5.
3. Select the parameters to display, as described in Performance Analysis in Tabular
Format, page 8-9.
4. Select an analysis interval, if required, using the Set Date Time option in the
Settings menu, as described in Selecting the Analysis Interval, page 8-6.
5. Select the performance details to be displayed using the Set Columns option in the
Settings menu, as described in Customizing the performance display, page 8-13.
Performance information is displayed in tabular format. To display the performance data in
graphical format, click the Graph tab for SDH, or the RMON graph tab for Ethernet (see
Performance Analysis in Graphic Format, page 8-14).
8.4.1 Performance Analysis in Tabular Format

Click the Performance tab or the RMON Perf. tab to enter performance analysis mode,
and then select the desired NE, as described in Selecting an NE, page 8-5.
8.4.1.1 Selecting SDH performance parameters
You can select a variety of performance statistics for the East and West cards, as described
in the following table:
Table 8-4: East/West performance statistics
Option Description
Regen Displays performance statistics for the Regenerator subsystem of the card
MUX Displays performance statistics for the Multiplexer subsystem of the card
Far MUX Displays performance statistics for the Multiplexer subsystem of the card on
the far end
HiOrder Displays performance statistics for the High Order subsystem of the card
Far Displays performance statistics for the High Order subsystem of the card on
HiOrder the far end

Option Description
LoOrder Displays performance statistics for the Low Order subsystem of the card
Far Displays performance statistics for the Low Order subsystem of the card on
LoOrder the far end
In addition, you can select performance statistics for the PPI, Far PPI, and Terminal
subsystems.
8.4.1.2 Selecting RMON performance parameters
You can select a variety of performance statistics for the Ethernet ports.
Table 8-5: RMON performance statistics
Option Description
Interval Displays the start time of the current measurement interval
Start
Drop Displays the number of dropped frames
Events
History Displays the total number of octets received, including bad frames and FCS
Octets octets (Framing bits are excluded.)
History Displays the total number of frames received, including bad frames
Pkts
Broadcast Displays the number of broadcast frames received
Pkts
CRC Align Displays the number of frames with Cyclic Redundancy Check errors
Error received
Undersize Displays the number of undersized frames received
Pkts
Oversize Displays the number of oversized frames received
Pkts
Fragments Displays the number of fragmented frames received
Jabbers Displays the number of frames longer than a predefined size with an invalid
CRC
Collision Displays the number of frames with collision events received
Utilization Displays the estimated network utilization at the mean physical layer (in
hundredths of a percent)
Multicast Displays the number of multicast frames received
Pkts
In addition, you must enter the port number for which RMON data is to be displayed in the
Port field.

8.4.1.3 Selecting the analysis interval
After choosing the desired NE and cards in accordance with Selecting an NE,
page 8-5, select Settings # Set Date Time to display the interval selection submenu, or
click on the toolbar to display the Range Selection window. After you have done this,
select the analysis interval, as described in Selecting the Analysis Interval, page 8-6.
8.4.2 Displaying Performance Tables
At this stage, you can display the selected performance data by clicking the Update icon
in the toolbar, or by selecting Settings # Update.
Figure 8-4: SDH performance table

The SDH performance table includes the following columns:

Table 8-6: Performance data columns
Column Description
NEiD NE identification (its IP address).
DateTime Date and time the performance item was reported by the NE.
field0, field1, … Type of performance data displayed in each column. This is the default
label of each data type column. Refer to Customizing the performance
display, page 8-13, for instructions on customizing the display.
field0val Value of the performance parameter displayed in each column.
field1val, … Default label of each parameter value column. Refer to Customizing the
performance display, page 8-13.
Figure 8-5: RMON performance table
The RMON performance table includes columns for each performance statistic that was
selected from the checkboxes on the left side of the window.

You can change the performance data displayed in the table at any time, either by repeating
the filtering process (selection of interval and parameters, as described in Selecting the
Analysis Interval, page 8-6), or by using the same filtering parameters on another NE (as
described in Selecting an NE, page 8-5).
NOTE: It is recommended to not mix the Utilization counter

with other counters, as Utilization is presented as a
percentage, which makes it incompatible with other counters
based on quantities.
8.4.2.1 Customizing the performance display
You can customize the performance information displayed in the work area by hiding
columns that display irrelevant data, and by assigning appropriate labels to each data
column.
To customize the display, select the Set Columns option from the Settings menu to display
the following:
Figure 8-6: Columns window
The Columns window includes the list of default column labels. Each column label has a
checkbox. Select a checkbox to include the corresponding column in the customized
display. By default, all columns are selected.

!"To customize the display:

1. Remove the columns to be excluded from the customized display by deselecting the
irrelevant labels. Make sure to deselect pairs of field and fieldval columns.
2. Change the column labels in accordance with your preferences, by overtyping the
default label with a new label (maximum 15 characters).
3. After making the changes, click OK to confirm.
4. To update the performance display, click the Update icon in the toolbar, or
select Settings # Update.
8.4.3 Performance Analysis in Graphic Format

!"To display performance data in graphical format:
1. Click the Graph tab (for SDH) or the RMON graph tab (for Ethernet). Use the
procedure described in Performance Analysis in Tabular Format,
page 8-9 to select the data items. In addition, for the element performance graph,
select an SDH category and right-click to view the available parameters in a pop-up
menu.
Figure 8-7: Performance graph pop-up menu
2. Select the parameters to be included in the graph from the pop-up menu. The
selected parameters are indicated by a checkmark $. Click Close Popup.
3. After making your selections, click the Update icon in the toolbar, or select
Settings # Update.

The selected data appears in a graph, as shown in Figure 8-8. A pop-up menu
appears when you right-click the mouse anywhere on the graph. This menu enables
you to toggle the display of the axis labels and legend, as well as zoom in and out.
Figure 8-8: SDH performance graph
Figure 8-9: Legend window

Figure 8-10: RMON performance graph
The graphical performance parameters display includes the following areas:

!" Title – the time and date interval.
!" Chart area – displays the selected parameters as graphs. Each parameter is represented
by a different line type and color, as described in the legend area at the top right-hand
corner of the work area. You can hide the legend by selecting Hide Legend from the
pop-up menu. The horizontal axis is marked to indicate the date and time. When the
Show Marks item is toggled on in the pop-up menu, the numerical value reported in
each sample appears in a small box above the line.
You can zoom in on a smaller interval by selecting Zoom In from the pop-up menu, or by
drawing a rectangle on the graph. To return to the full display, click Zoom Undo.
NOTE: The RSPI Performance and RSPI Graph tabs of

the Alarm and PM Viewer are not applicable.

9
Additional Services and Tools
9.1 Services
When Windows™ 2000 is initialized, a series of services are automatically initiated. These
services, which operate in the background transparently to the user, perform vital functions,
such as communicating with managed elements, processing alarms from the elements,
synchronizing the element clocks, and collecting performance data. The information that is
collected from the NEs is passed on to the database. The EMS-µLAN station is supplied
with a set of user-operated applications that are used to configure, maintain, and
troubleshoot the network based on this information.
The Services Watchdog enables you to monitor the status of these services. An indicator,
located in the system tray, is displayed in green when all the services chosen for monitoring
are running, and flashes red when there is a fault in one or more of the monitored services.
The Services Watchdog opens automatically when the user logs on. If it has been closed,
select Start ! Network Management ! Services Watchdog. The following window is
displayed:
Figure 9-1: EMS-µLAN Services Watchdog
You can also open this window by double-clicking the icon in the system tray, or by
right-clicking and selecting Service Status from the pop-up menu.
Select and deselect the checkboxes to choose the services you wish to monitor. Click OK to
save your settings.
You can start and stop these services using the Service Control II tab in the network
Control Panel applet, as described in Service Control II, page 9-9.

Additional Services and Tools BroadGate™ EMS-µLAN User's Manual
9.1.1 Keep Alive Service

The Keep Alive service has two functions:
!" It polls NEs by pinging them. If there is no response, this indicates that there is no
communication between the manager and the element. The element will then be colored
black in the Topology Browser. If the element is up and running, the alarm status is
determined by the Trap service.
!" It is responsible for the Set Time function. It sends an SNMP message on every fourth
pinging cycle to synchronize the clocks of all the elements.
NOTE: The main function of Keep Alive is to ping the

elements, and the Services Watchdog indicates only whether
or not this service is functioning by displaying a green or red
indicator. The status and color of NEs can be viewed in the
Topology Browser. Additional details about events and
alarms can be viewed in the Alarm and Performance Viewer,
as described in Chapter 8, Using the Alarm and PM Viewer.
9.1.2 Trap Service

The Trap service receives traps or alarm interrupt messages that are initiated and sent by the
NEs. Traps are stored in the SQL database. The Topology Browser displays alarm
information depending on alarm severity. In all cases, the most severe alarm level currently
found in an element is the one displayed. When all the alarms have been cleared and the
element is functioning normally, a trap message is sent, and the element is updated to
display in green.
There are seven alarm levels:
Table 9-1: Alarm levels
Color Meaning
Green Normal
Green An event has occurred
Yellow Warning
Yellow Minor alarm
Orange Major alarm
Red Critical alarm
Black Disconnected

BroadGate™ EMS-µLAN User's Manual Additional Services and Tools
9.1.3 Performance Service

The Performance service sends queries to the NEs every 15 minutes to retrieve information
on SDH performance and Layer 2 statistics. The results are stored in the database and
viewed using the Alarm and PM Viewer.
9.1.4 Alarm Synchronization Service

In theory, the SQL alarm database is updated regularly and accurately reflects the status of
all the NEs. However, the EMS-µLAN may not be gathering data due to a temporary lack of
communication between the elements and the EMS-µLAN. In this case, the database will
not reflect the true situation, as a trap is only sent once at the time of the event.
To prevent this from happening, the Alarm Synchronization service polls the elements and
compares their alarms with the alarms recorded in the database. If there is a discrepancy, it
updates the database using the information received from the elements themselves.
9.1.5 Trail Alignment Service

The Trail Alignment service verifies that the trails stored in the database are identical to the
actual trails. Discrepancies can occur when the cards in the µLAN are changed, nodes are
removed or added, and so on. An algorithm creates a checksum based on all the
cross-connect information. The service polls both the database and the elements at defined
intervals (the precise interval can be set, as explained in Service Control I, page 9-8) for the
checksums. If there is a discrepancy, the following icon appears in the system tray. It can
be configured to flash or remain static. You can resolve any discrepancies using the
Network Resolution Tool.
9.2 Network Resolution Tool

Use the Network Resolution Tool to resolve discrepancies that can occur between the
cross-connection (trail) data stored in the database and the actual configuration that exists on
an NE. Refer to Trail Alignment Service, page 9-3, for an explanation as to how these
discrepancies can occur, and how the Network Verification service reports discrepancy
errors.
CAUTION: The actions you can take with the Network

Resolution Tool are described in Selecting a Ring or Link,
page 9-6, and Selecting an Element, page 9-7. Extreme
caution must be taken when using these options, as a mistake
could result in the deletion of hundreds of trails, and could
bring network traffic to a halt with severe consequences.
Therefore, only Super Users may carry out these actions.

To open the Network Resolution Tool, select Start ! Network Management ! Network
Resolution. The Network Resolution window is displayed.
Figure 9-2: Network Resolution window for trails

Figure 9-3: Network Resolution window for cross-connections
The top left of the window displays a topological representation of the network, including
rings, links, and unassigned elements, together with their status and IP addresses. The
upper-right side of the window contains the Database list, which displays the
cross-connection information stored in the database. The lower-right side of the window
contains the Element list, which displays the information that appears in the
cross-connection table of the selected element. In a correctly functioning network, the data
in both parts of the screen should be identical.
Compound networks contain one or more external NEs. External elements are designated by
an “EE” convention, as shown in Figure 9-4.
Figure 9-4: Example showing a compound network

The File menu contains one item: Exit. The Help menu displays version information for
this application.
NOTE: The Network Resolution Tool cannot be used when

the Trail Manager is open. For more information about the
Trail Manager, refer to Chapter 5, Building Trails.
9.2.1 Selecting a Ring or Link

To view the trails table for a group of elements, select the folder icon for the chain, network,
ring, or link from the Resolution Tool tree. The information stored in the database is
displayed in the Database list. To compare this information with the cross-connection table
stored in the element, select Get trails from elements in the Action area in the lower-left
side of the window, and click Start Action. The information is displayed in the Element
list.
If there are discrepancies between the Database List and the Element List tables, there are
several actions you can take (see the following table). To carry out an action, select your
choice of action from the Action list and click Start Action. Click Yes to confirm your
choice. If the action is successful, a confirmation window is displayed. Click OK.
CAUTION: Exercise extreme caution when using the

Network Resolution Tool, as deleting trails and
cross-connections can have severe consequences. They are
usually carried out as maintenance operations, when the
network is being set up, or if there is severe disruption to the
network. Carry out these operations when the network is not
active. Under normal circumstances, you will choose either
the Restore or Repair operation.

The Action menu options (at the trail level) available when the ring or link folder is selected
are displayed in the following table:
Table 9-2: Action menu options – ring or link folder
Action Description
Get trails from elements Click Start Action to view the trails defined for the
selected elements.
Restore selected trails into Takes the information from the element (lower table)
database and updates the database with that information.
Delete selected trails from Deletes selected trails from the database of the selected
database ring or link.
Delete ALL trails in Deletes all the trails of the elements in the selected ring
elements or link. (The trails still exist in the database.) You can
create new trails using the Trail Manager.
Flush all Deletes all trails and cross-connections from the
database and elements of the selected ring or link.
9.2.2 Selecting an Element

When you select an element in the Network Resolution tree, you are working at the
cross-connection level. The Action menu options in this case are as follows:
Table 9-3: Action menu options – element
Action Description
Get XCs from element Click Start Action to view the cross-connection table
for the element.
Restore selected XCs from Takes the information from the database (upper table)
DB to element and updates the element with that information.
Delete all XCs in element Deletes the complete cross-connection table for the
selected element.
Delete selected XCs from Deletes selected cross-connections from the database.
Database
Delete selected XCs from Deletes selected cross-connections from the element.
element
Repair trail Repairs the trail after restoring or deleting
cross-connections. This option is also used after
inserting a new NE between two existing NEs in order
to re-establish traffic for the new topology.

9.3 Control Panel Applet

This option is available to Super Users only.
To open the Control Panel applet, select Start ! Settings ! Control Panel ! Network
Management.
9.3.1 Service Control I

The Service Control I tab sets the intervals between requests (in seconds) for the following
services:
!" Keep Alive
!" Performance
!" Alarm Synchronization
!" Network Verification
Figure 9-5: Service Control I tab
NOTE: The values displayed are the default values. It is

recommended not to change these values.

9.3.2 Service Control II

Use the Service Control II tab to start and stop the services described in Services, page 9-1.
Figure 9-6: Service Control II tab

9.4 Installation Control

The Installation Control utility enables you to view system information, as well as a list of
all the configuration, Dynamic Link Library (DLL), and application files that are used in the
EMS-µLAN, including their version and date. This information is very important for
technical staff when reporting problems.
To open the utility, select Start ! Network Management ! Installation Control to
display the following:
Figure 9-7: Installation Control – System tab
The System tab displays basic information about the computer on which the EMS-µLAN is
running, including the amount of available memory and disk space, and the current status of
the database.
Click Get info to refresh the data.

Click the Management tab to display the following:
Figure 9-8: Installation Control – Management tab
The Management tab displays the version number and date of all the services, applications,
and DLLs currently running in the system.
Click Get info to retrieve and refresh the data.
9.5 Download / Backup Center

The Download / Backup Center provides a software inventory and control mechanism that
enables you to easily perform software upgrades and other operations on selected NEs. This
application is new for version 2.2.r2.
A software package version (SWPack) is identified by its version and release numbers. For
example, 2.2.r.2 means version 2.2, release 2.
CAUTION: Many of the operations that can be performed

using this application are traffic-affecting and can damage
your configuration. Use caution when performing these
operations. Consult ECI Telecom Customer Support for more
information.

To open the utility, select Start ! Network Management ! Download Backup Center.
The Download Center Log In window is displayed.
Figure 9-9: Download Center Log In window
Enter your login details. The default User Name is root and the default Password is
neroot1. Both fields are case-sensitive.
After entering your login details, click OK to display the Download / Backup Center main
window.
Figure 9-10: Download / Backup Center window – Network elements list tab

The Download / Backup Center main window consists of two tabs – a Network elements
list tab and a Processing tab.
The Network elements list tab, shown in Figure 9-10, is used to specify the NE(s) to which
an operation applies. The NE list contains all NEs in the EMS-µLAN database. Operations
that can be performed are described in Table 9-6, page 9-15. When first opened, this tab
only displays the NE list on the left. To view details about the software versions installed on
an NE, check the Selected checkbox for an NE(s) and click Refresh. You can also click
Refresh at any time to update the window’s contents for the selected NEs.
An option is also available to add an NE to the NE list in the window. For more details, see
Adding an NE to the NE List, page 9-15.
This tab displays the following parameters:
Table 9-4: Network Elements list parameters
Selected A checkbox designating if an NE is selected for a given
operation.
Element IP NE IP address (read-only).
address
Element name NE name (read-only).
Status Indicates the current operation process being executed.
State Indicates the state of the current process being executed,
such as Finished.
Running SW Actual software version running on the NE (read-only).
version
Next running The software version that will run after a hardware reset.
SW version Typically, this is the same version as the currently
running software version, and is shown in boldface type
(read-only).
Standby SW Standby version of the software. This version is the
version non-active installed software version (read-only).
Accessible Indicates whether the NE is connected and reachable (via
a ping) for the operation. This is a read-only field. When
this checkbox is not checked, the operation cannot be
performed on the NE.
In addition, the following buttons are displayed:

!" Use the Select All and Deselect All buttons to select or deselect all NEs in the NE list,
respectively.
!" Click the Move to Processing button to activate the selected operation on a specific
NE(s). This action opens the Processing tab, in which you can view the progress of the
operation currently being executed.

The Processing tab, shown in Figure 9-11, displays information about the software version
to be overwritten during a software download process, and the progress of the operation
currently being performed.
Figure 9-11: Download / Backup Center window – Processing tab
This tab displays the following parameters:

Table 9-5: Processing parameters
Elements A checkbox designating if an NE is selected for a given
operation.
IP NE IP address (read-only).
SW Displays the two software versions presently installed on
the NE (read-only).
Overwrite A radio button identifying which software version is to be
overwritten by the operation. By default, the standby
software version is selected. If preferred, you can
overwrite the currently active software version (typically
this is the standby version) by selecting the Active radio
button.

Status Indicates the current stage of processing for the operation
being executed.
Progress A progress bar that displays the completion rate of the
operation currently begin executed, in percentage.
Table 9-6 describes the operations that can be performed using the Download / Backup
Center tool. Select the required option in the Operation drop-down list.
Table 9-6: Download / Backup Center operations
Operation Description
Embedded SW Downloads an embedded software file that identifies the
upgrade currently running software version, the next software
version to be run upon hardware reset, and the standby
software version.
Backup NE Creates a backup of the NE database and sends it by FTP
configuration to a designated backup folder.
Restore NE Downloads the NE database from a saved backup file to
configuration the NE.
Restore NE Restores the NE database upon next reset of the NE.
configuration on
reset
FTP upload to Sends a file to the NE via FTP. This option is typically
NE only used in special circumstances where a specific file
must be sent to the NE.
FTP download Downloads a file from the NE via FTP. This option is
from NE typically used for debugging purposes.
Software Downloads a software package (SWPack) containing the
package upgrade SWPack header, SWPack information storage, FPGA
storage, and embedded software storage.
Reset Performs a hardware reset for the selected NE(s).
9.5.1 Adding an NE to the NE List

If an NE does not appear in the NE list, it can be added manually.
"#To add an NE to the NE list:
1. In the Options menu, select Add element. A row is added at the bottom of the NE
list.
2. Enter the IP address for the NE you want to add. The NE is added to the list. You
can now perform all operations on this NE.

9.5.2 Performing an Embedded SW Upgrade

This operation upgrades the embedded software on an NE in a two-stage process:
!" First, the new software version is downloaded to RAM on the NE.
!" Second, the software is written to the NE.
For software versions up to v2.2r2, you must perform this operation for two separate
software files. One file is named RamXXX.BLL, where XXX designates the software
version number and build number for the software. The second file is named
RamXXX.BIN, where XXX also specifies the version and build numbers for the software.
To upgrade from software v 2.2r2 (inclusive) and higher, use the SW Package Upgrade
operation, described on page 9-23.
After completing the Embedded Software Upgrade operation, be sure to reset the affected
NE(s) for the new version to take effect.
"#To perform an Embedded SW Upgrade operation:
1. Select the Network elements list tab.
2. Identify the NE(s) whose software is to be upgraded by checking the Selected
checkbox adjacent to the NE’s IP address and name.
3. Click Refresh.
4. In the Operation drop-down list at the top of the window, select Embedded SW
upgrade.
5. In the Local file field, click the button. The Open window appears in which
you navigate to the required software version file.
Figure 9-12: Open window
6. Select the .BLL file and click Open. The file you selected now displays in the
Local file field.

NOTE: When performing this software upgrade for the .BIN

file (required for software versions up to v 2.2r2), select the
relevant .BIN file in this step.
7. Confirm that the file extension in the Remote file field corresponds to the file you
selected in step 6. This field is automatically updated, based on your selection in the
Local file field (see step 6). For example, if you selected a file with a .BLL
extension in step 6, the Remote file field should also show a filename with the
.BLL extension.
8. Click the Move to Processing button. The Processing tab opens (see Figure 9-11).
Typically, the active software version is not overwritten when upgrading. If you
want to overwrite the existing active software version on the NE, a warning
message is also displayed prompting you to confirm this action.
Figure 9-13: Change Download Bank window
9. Click Yes to continue and overwrite.

10. For each NE selected in step 2, ensure that the appropriate Overwrite radio button
is selected. By default, the radio button corresponding to the non-active software
version is selected, thereby indicating that this version will be overwritten during
the download process. If you do not want to overwrite this version, select the other
adjacent radio button to overwrite the software version that it specifies.
11. Click Apply to begin processing. You can observe the progress of the operation as
it executes in the Progress bar. If you chose to perform this operation on multiple
NEs, the operation is performed one NE at a time, in the order of the NEs as listed
in the NE list. If an error is encountered and the operation cannot be performed on a
given NE, the process moves to the next NE in sequence. An error message is also
displayed.
NOTE: Processing cannot be interrupted once it has started.

Processing is done in two stages. In the first stage, the software is written to RAM
on each NE. At the completion of stage one, the Progress bar shows 50% on all
NEs, as shown in the following example:
Figure 9-14: Embedded software upgrade processing at completion of stage one
NOTE: If the NE is reset during this process, the software

downloaded in stage one is deleted, as it has not yet been
written to the NE.
After this stage is completed for all NEs, stage-two processing begins in which the
software is actually written on each NE.

The example below shows stage-two processing while in progress:
Figure 9-15: Embedded software upgrade processing during stage two
At the conclusion of all processing, a confirmation message is displayed.
Figure 9-16: Information window
12. Click OK.

13. Select the Network elements list tab and click Refresh to view processing results.
Figure 9-17: Embedded software upgrade processing after completion
As illustrated in this example, the Embedded SW upgrade operation completed

successfully, as noted by Transferred OK in the Status field and Finished in the
State field for all NEs.
14. For software versions up to v 2.2r2, you must repeat steps 1 through 12 to also
upgrade the second software file (with the .BIN extension). For this part of the
upgrade select the relevant .BIN file in step 5.
9.5.3 Backing Up an NE’s Configuration

This operation creates a backup of an NE’s database and sends it via FTP to a designated
location. Such backups should be performed regularly for all NEs.
The database file, which is stored on the computer after the operation, is named
XXX_mu.TXT, where XXX designates the IP address of the NE, for example,
192.9.30.12_mu.TXT.
"#To backup the database for an NE:
2. Identify the NE(s) whose database is to be backed up by checking the Selected
checkbox adjacent to the NE’s IP address and name.

3. Click Refresh.
4. In the Operation drop-down list at the top of the window, select Backup NE
config.
you navigate to the folder in which the backup file is saved.
6. Select the required folder and click Open. The folder you selected now displays in
the Local file field.
it executes in the Progress bar. If you chose to perform this operation on multiple
NEs, the operation is performed one NE at a time, in the order of the NEs as listed
in the NE list. If an error is encountered and the operation cannot be performed on a
given NE, the process moves to the next NE in sequence. An error message is also
displayed.
9.5.4 Restoring an NE’s Configuration

This operation replaces the database on an NE by restoring it from a backup file via FTP.
When executing this command, the NE’s IP address must match that in the backup file
name, and the NE must be connected. For example, if the NE’s IP address is 192.9.30.15, be
sure to select the 192.9.30.15_mu.txt file in the backup folder.
Figure 9-18: Sample backup folder showing backup files
CAUTION: Exercise extreme caution when using this

operation, as the NE’s existing database is overwritten.

"#To restore the database on an NE:

2. Identify the NE whose database is to be backed up by checking the Selected
checkbox adjacent to the NE’s IP address and name. This operation can only be
performed on one NE at a time.
3. Click Refresh.
4. In the Operation drop-down list at the top of the window, select Restore NE
config.
you navigate to the folder in which the backup file is saved.
Figure 9-19: Sample backup folder showing backup files
6. Browse to the required database file and click Open. The file you selected now
displays in the Local file field.
7. In the Remote file field, enter the folder on the NE to receive the database file.
it executes in the Progress bar. If an error is encountered and the operation cannot
be performed, an error message is displayed.

9.5.5 Performing a Restore NE Config on Reset Operation

This operation must be performed after restoring an NE’s configuration in order to activate
the new database on the NE. The operation sends a command to the NE that upon the next
reset of the NE, the database will be activated. After performing the procedure below, you
must reset the NE to complete the database restoration process and ensure that the database
is activated. See Performing a Reset Operation, page 9-24, for more details.
"#To perform a Restore NE Config on Reset operation:
2. Identify the NE to be affected by this operation by checking the Selected checkbox
adjacent to the NE’s IP address and name. This operation can only be performed on
one NE at a time.
3. Click Refresh.
4. In the Operation drop-down list, select Restore NE config on Reset.
5. Click the Move to Processing button. The Processing tab opens.
6. Click Apply.
9.5.6 Performing a SW Package Upgrade Operation

This operation is similar to the Embedded SW Upgrade operation in that it upgrades the
software on an NE in a two-stage process:
!" First, the new software version is downloaded to RAM on the NE.
!" Second, the software is written to the NE.
Important: This process must be used to upgrade software versions 2.2r2 and higher.
NOTE: For software versions prior to v2.2r2, you must use

the Embedded SW Upgrade operation to upgrade NE
software. See Performing an Embedded SW Upgrade,
page 9-16, for more details.

The software file used for this operation is named swpackall_v2242_XX.BIN, where XXX
designates the build number for the software, as shown in the Local file field in the
following example.
Figure 9-20: Sample showing SW Package Upgrade operation
After completing this upgrade operation, be sure to reset the affected NE(s) for the new
version to take effect.
"#To perform a SW Package Upgrade operation:
Follow the steps in the procedure described beginning on page 9-16. In step 5 of this
procedure, select the correct .BIN file.
9.5.7 Performing a Reset Operation

When performing this action, you can optionally force the NE to use the standby software
version after the reset, in order to control the software version that runs during the next
session after reset.
This operation must be performed after restoring an NE’s database in order to activate the
database on the NE.

"#To perform a reset operation:

2. Identify the NE(s) to be reset by checking the Selected checkbox adjacent to the
NE’s IP address and name.
3. Click Refresh.
4. In the Operation drop-down list, select Reset.
5. Click the Reset button. The Processing tab opens.
Figure 9-21: Download / Backup Center window – Processing tab for Reset operation
The software version that will run after the hardware reset is shown in boldface.

6. [Optional] You can force the NE to use the standby software version after the reset
operation by selecting the Force standby on Reset checkbox for the NE. When
choosing this option, the standby version will be shown in boldface, indicating that
it is the version that will run after the reset.
Figure 9-22: Download / Backup Center window – Processing tab showing forced use of
standby software
7. Click Reset. The hardware reset is performed. The indicated software version is
now the Running SW version on the NE.

A
SQL Reference
A.1 Overview
The EMS-!LAN makes use of the following three SQL databases to store information about
the system, including topology, trails, performance, and alarms:
"# TNGDB – contains all configuration information, including topology and trail
configuration. This information is used by the Topology Browser, Trail Manager, and
Network Resolution Tool.
"# CardViewDB – contains all performance data for the past three months and alarm data
for the past three days. On the first of each month, a job is executed that moves all
performance data more than three months old to the CardViewDBHist database. Once a
day, a job is executed that moves all alarm data more than three days old to the
CardViewDBHist database.
"# CardViewDBHist – contains performance data more than three months old and alarm
data more than three days old.
You can view the tables that make up each of these databases, as well as generate SQL
queries about the information they contain, by using the Microsoft SQL Server utilities
included with the EMS-!LAN installation, Enterprise Manager, and Query Analyzer.
426006-2406-033-A00 ECI Telecom Ltd. Proprietary A-1

SQL Reference BroadGate™ EMS-µLAN User's Manual
A.2 Accessing the SQL Databases

The SQL databases used by the EMS-!LAN can be accessed via the Enterprise Manager
utility of the SQL Server. Enterprise Manager enables you to view the structure of each
database, including the tables it contains and the fields within each table.
!"To access the SQL databases:
1. Select Start # Programs # SQL Server # Enterprise Manager to display the
Enterprise Manager main window.
Figure A-1: Enterprise Manager window
By expanding the tree, you can access the three databases used by the EMS-!LAN:
TNGDB, CardViewDB, and CardViewDBHist.
A-2 ECI Telecom Ltd. Proprietary 426006-2406-033-A00

BroadGate™ EMS-µLAN User's Manual SQL Reference
2. To display the list of tables for one of the SQL databases, expand the branch for the
database (for example, Databases # TNGDB) in the Enterprise Manager tree and
then select Tables.
The display area on the right side of the window shows the list of tables contained
in the database.
Figure A-2: List of TNGDB tables

3. Right-click a table in the list and then select Open Table # Return all rows from
the popup menu to display the table values in a separate window.
Figure A-3: Sample of data in selected table
A.3 Database Structure

This section describes the structure of the three databases used by the EMS-!LAN,
including the tables that make up each database and the fields included in each table.
A.3.1 TNGDB Structure

The TNGDB database contains all configuration information used by the EMS-!LAN,
including topology and trail configuration. Table A-1 lists the tables that make up the
database.
Table A-1: TNGDB tables
Table Description See Page

tng_managedobject Details about each NE in the system, A-6
such as its name, IP address, current
state, and so on.
tng_link Details about each link in the system, A-7
such as its name, source and
destination IP address and selected
communication details.
TrailEx High-level information about trails, A-8
such as name, current status, port
type and container type. It is
dependent on the Trail table.


Trail Details about trails, such as the trail A-9
name, type, and direction. It is
dependent on CrossConnect2 and
TrailSegment.
CrossConnect2 Details about the cross-connects in A-9
the NEs that make up the trail, such
as the cross-connect type and
number, the port and container, and
TU information. It is dependent on
TUmid.
TrailSegment Details about the segments in the A-11
links that make up the trail, such as
the source and destination slot and
TU. It is dependent on TU2.
TUmid Details about the TU mids in each A-12
cross-connect.
TU2 Details about the TUs in each A-12
segment, such as its number and
direction.
A.3.1.1 Trail table dependencies
Figure A-4 shows the dependencies between the tables in the TNGDB database that store
information about trails in the µLAN network.
Figure A-4: Trail table dependencies

A.3.1.2 tng_managedobject
The tng_managedobject table contains information about each NE in the system.
NOTE: For more information about NE definitions, refer to

Creating NEs, in Chapter 4, Building the Network.
Table A-2: tng_managedobject fields
Fields Data type Description

managedobject_id int NE ID number
uuid binary (16) NE unique identifier
label varchar (255) NE label used by the
EMS-µLAN
address varchar (15) NE IP address
status_no int Whether the NE is currently
connected:
1 – connected
0 – not connected
severity int The severity level of the most
severe alarm currently associated
with the NE:
5 – critical
4 – major
3 – minor
2 – warning
6 – clear
acknowledge tinyint Whether alarms generated by this
NE should be forwarded to the
EMS-µLAN:
1 – yes
0 – no
date_ins DateTime Date when the NE was entered
into the system
date_modify DateTime Date when the NE was last
modified
TUeast int Number of TUs on the east
interface (always 63)
TUwest int Number of TUs on the west
interface (always 63)
TUmid int Number of TU mids in the NE
(63 or 126)
number_tu_mids int Number of TU mids in the NE
(63 or 126)


ne_location_x int X-axis location of the NE on the
Topology Browser map
ne_location_y int Y-axis location of the NE on the
Topology Browser map
ow_number varchar (32) Phone number for calling this NE
via orderwire.
type int NE type:
2 – the NE type (optical) used by
the EMS-!LAN
tim int TIU type
exec_name varchar (512) The program executed (Card
View) when the NE is
double-clicked in the Topology
Browser.
A.3.1.3 tng_link
The tng_link table contains information about each link in the system.
NOTE: For more information about link definitions, refer to

Creating Links, in Chapter 4, Building the Network.
Table A-3: tng_link fields

uuid binary (16) Unique link identifier
source_uuid binary (16) Unique identifier of the NE that
is the link source
source_direction char (1) Direction of the link source –
East or West
source_ip_address varchar (15) IP address of the link source
dest_uuid binary (16) Unique identifier of the NE that
is the link destination
dest_direction char (1) Direction of the link destination –
East or West
dest_ip_address varchar (15) IP address of the link destination
link type char (1) Link type:
F – fiber
source_j0tx varchar (30) Transmitted J0 byte at the source
source_j0exp varchar (30) Expected J0 byte at the source
source_j1tx varchar (30) Transmitted J1 byte at the source
source_j1exp varchar (30) Expected J1 byte at the source


source_c2tx int Transmitted C2 byte at the source
source_c2exp int Expected C2 byte at the source
dest_j0tx varchar (30) Transmitted J0 byte at the
destination
dest_j0exp varchar (30) Expected J0 byte at the
destination
dest_j1tx varchar (30) Transmitted J1 byte at the
destination
dest_j1exp varchar (30) Expected J1 byte at the
destination
dest_c2tx int Transmitted C2 byte at the
destination
dest_c2exp int Expected C2 byte at the
destination
date_modify DateTime Date when the link was last
modified
date_ins DateTime Date when the list was created
A.3.1.4 TrailEx
The TrailEx table contains high-level information about each trail in the system.
NOTE: For more information about trails, refer to Trail

Types, in Chapter 5, Building Trails.
Table A-4: TrailEx fields

status int Current status of the trail:
1 – the trail has been stored in the
database.
3 – the trail has been stored in the
database and sent to the NEs.
uuid binary (16) Unique trail identifier
port_type int Trail port type:
1 – E1
7 – Ethernet (WAN 1)
container_type int Trail container type:
12 – VC-12
name varchar (256) The name of the trail in the Trail
Manager

A.3.1.5 Trail
The Trail table contains additional information about each trail in the system.
NOTE: For more information about trails, refer to Creating

New Trails, in Chapter 5, Building Trails.
Table A-5: Trail fields

uuid binary (16) Unique trail identifier
trail_type int Trail type:
1 – E1
trail_dir int Trail direction:
E – East
W – West
trail_name varchar (30) The name of the trail in the Trail
Manager
uuidTrailEx binary (16) The unique identifier as it
appears in the TrailEx table
A.3.1.6 CrossConnect2
The CrossConnect2 table contains information about the cross-connects in the system.
NOTE: For more information about trails, refer to Building

Trails Using Card View, in Chapter 6, Configuring and
Monitoring µLAN NEs.

Table A-6: CrossConnect2 fields

uuid binary (16) Cross-connect unique identifier
cross_connect_type int Cross-connect type:
1 – unidirectional (E to W or W
to E)
2 – bidirectional unprotected (E
to E or W to W)
5 – bidirectional protected
(hitless)
6 – bidirectional protected (hit)
9 – local
10 – unidirectional through (E to
W or W to E)
11 – bidirectional through
ne_uuid binary (16) NE unique identifier associated
with the cross-connect
trail_name varchar (30) Trail name associated with the
cross-connect
cross_connect_number int Cross-connect number, as known
by the trail
slot_hi int ID of the transmitting side of the
cross-connect:
0 – East
101 – West
slot_mid int ID of the TU mid of the
cross-connect (always 2000).
slot_lo int ID of the receiving side of the
cross-connect:
0 – East
101 – West
tu_hi int TU number on the transmitting
side of the cross-connect
tu_mid int Port number of the TU mid
(1-63)
tu_lo int TU number on the receiving side
of the cross-connect
j2tx varchar (30) Transmitted cross-connect J2
bytes
j2exp varchar (30) Expected cross-connect J2 bytes
trail_uuid binary (16) Unique trail identifier associated
with the cross-connect


port int Port type associated with the
cross-connect:
1 – E1
container int Container type associated with
the cross-connect:
12 – VC-12
A.3.1.7 TrailSegment
The TrailSegment table contains information about each link segment in the system.
NOTE: For more information about trails, refer to Viewing

Trail Information, in Chapter 5, Building Trails.
Table A-7: TrailSegment fields

uuid binary (16) Unique trail segment identifier
trail_name varchar (30) The trail name as it appears in the
Trail Manager
trail_segment_number int The segment number, as it is
known by the trail
link_uuid binary (16) Link unique identifier associated
with the segment
tu_number int TU number associated with the
link
source_uuid binary (16) Unique identifier of the source
NE associated with the segment
source_slot_mid int Source NE slot associated with
the segment (always 2000)
source_tu_mid int Source NE TU mid associated
with the segment (1-63)
dest_uuid binary (16) Unique identifier of the
destination NE associated with
the segment
dest_slot_mid int Destination NE slot associated
with the segment (always 2000)


dest_tu_mid int Destination NE TU mid in the
associated with the segment
(1-63)
trail_uuid binary (16) Trail unique identifier associated
with the segment
A.3.1.8 TUmid
The TUmid table contains information about the TU mids that make up each cross-connect.
Table A-8: TUmid fields

uuid binary (16) TU mid unique identifier
ne_uuid binary (16) NE unique identifier associated
with the TU mid
tu_mid int NE port associated with the TU
mid
A.3.1.9 TU2
The TU2 table contains information about the TUs contained in each link.
Table A-9: TU2 fields

uuid binary (16) TU unique identifier
link_uuid binary (16) Link unique identifier associated
with the TU
direction char (1) TU direction:
E – East
W – West
B – both
number int TU number, as known by the link

A.3.2 CardViewDB Structure

The CardViewDB database contains current alarm and performance data collected by the
EMS-!LAN over the previous three days (for alarms) or three months (for performance
data). Table A-10 lists the tables that make up the database.
Table A-10: CardViewDB tables

tblAlarmID Lists all alarm types by name. A-14
tblAlarmSever Lists all alarm types by severity. A-14
tblCurAlarms Details about each current alarm in A-14
the system, such as its name,
severity, date and time, and the NEs
and trails to which it is related.
tblPerfHistoryHighOr Performance data for the High-Order A-15
subsystem taken at 15-minute
intervals.
tblPerfHistoryLowOr Performance data for the Low-Order A-16
intervals.
tblPerfHistoryMulti Performance data for the Multiplexer A-16
intervals.
tblPerfHistoryPPI Performance data for the PPI A-18
intervals.
tblPerfHistoryRegen Performance data for the Regenerator A-19
intervals.
tblPerfHistoryRMON Remote Monitoring performance data A-20
for the Ethernet ports in each !LAN
NE taken at 15-minute intervals.
tblPerfHistoryTuMid Performance data for the TU mids in A-21
use taken at 15-minute intervals.
NOTES: Performance data for the interval currently being

collected cannot be viewed until the interval is completed.
For more information about alarm and performance data,
refer to Chapter 8, Using the Alarm and PM Viewer.

A.3.2.1 tblAlarmID
The tblAlarmID table lists the names and descriptions of all alarms in the EMS-!LAN
system, according to AlarmID.
Table A-11: tblAlarmID fields

AlarmID int Alarm type ID number
AlarmName varchar (256) Alarm type name
AlarmDesc varchar (512) Alarm type description
A.3.2.2 tblAlarmSever
The tblAlarmSever table lists the severities of all alarms in the EMS-!LAN system,
according to AlarmID.
Table A-12: tblAlarmSever fields

Severity int Alarm type severity:
5 – critical
4 – major
3 – minor
2 – warning
6 – clear
A.3.2.3 tblCurAlarms
The tblCurAlarms table contains a detailed history of all alarms in the system.
Table A-13: tblCurAlarms fields

NEID varchar (50) IP address of the NE that issued
the alarm
Status bit Whether the alarm is forwarded
to the EMS-!LAN:
0 – yes
1 – no
Processed bit Whether or not the alarm has
been cleared:
0 – no
1 – yes


DateTime DateTime Date and time when the alarm
occurred
Severity int Alarm severity:
5 – critical
4 – major
3 – minor
2 – warning
6 – clear
trail_name varchar (32) Trail name related to the alarm
port_number int Port number related to the alarm
A.3.2.4 tblPerfHistoryHighOr
The tblPerfHistoryHighOr table contains performance data regarding the High-Order

subsystem of the !LAN.
Table A-14: tblPerfHistoryHighOr fields

NEID char (15) NE IP address from which the
performance data was obtained
DateTime DateTime Date and time when the
performance data was measured
EastESs int Number of Errored Seconds on
the East port
EastSESs int Number of Severely Errored
Seconds on the East port
EastCSESs int Number of Consecutive Severely
Errored Seconds on the East port
EastUASs int Number of Unavailable Seconds
on the East port
EastBBEs int Number of Background Block
Errors on the East port
NOTE: The same performance counters listed above are also

available for the East connection at the far side of a link, as
well as for West and West far.

A.3.2.5 tblPerfHistoryLowOr
The tblPerfHistoryLowOr table contains performance data regarding the Low-Order

Table A-15: tblPerfHistoryLowOr fields

NEID varchar (15) NE IP address from which the
DateTime DateTime Date and time when the performance
data was measured
EastESs int Number of Errored Seconds on the
East port
EastSESs int Number of Severely Errored Seconds
on the East port
EastBBEs int Number of Background Block Errors
on the East port
EastPSCs int Number of Protection Switch
Counters on the East port
EastUASs int Number of Unavailable Seconds on
the East port
EastPJEplus int Number of positive Pointer
Justification Events on the East port
EastPJEminus int Number of negative Pointer
Justification Events on the East port
TU int TU related to the measurements
NOTE: The performance counters listed above are also

well as for West and West far, with the exception of PJEplus,
PJEminus, and PSCs, which are not available for the far end.
A.3.2.6 tblPerfHistoryMulti
The tblPerfHistoryMulti table contains performance data regarding the Multiplexer


Table A-16: tblPerfHistoryMulti fields

NEID varchar (15) IP address of the NE from which
the performance data was
obtained
the East port
on the East port
EastPJEplus int Number of positive Pointer
Justification Events on the East
port
EastPJEminus int Number of negative Pointer
Justification Events on the East
port

well as for West and West far, with the exception of PJEplus
and PJEminus, which are not available for the far end.

A.3.2.7 tblPerfHistoryPPI
The tblPerfHistoryPPI table contains performance data regarding the PPI subsystem of the
!LAN.
Table A-17: tblPerfHistoryPPI fields

PPI int Port number on which the
ESs int Number of Errored Seconds
SESs int Number of Severely Errored
Seconds
CSESs int Number of Consecutive Severely
Errored Seconds
BBEs int Number of Background Block
Errors
UASs int Number of Unavailable Seconds
CVs int Number of Code Violations
OFSs int Number of Out of Frame Seconds

available for the far end connection, except for OFSs.

A.3.2.8 tblPerfHistoryRegen
The tblPerfHistoryRegen table contains performance data regarding the Regenerator

Table A-18: tblPerfHistoryRegen fields

the East port
on the East port
EastOFSs int Number of Out of Frame Seconds
on the East port

available for the West connection.

A.3.2.9 tblPerfHistoryRMON
The tblPerfHistoryRMON table contains Remote Monitoring performance data for each
Ethernet port (LAN and WAN) in each !LAN NE.
NOTE: For more information about these performance fields,

refer to Viewing Ethernet Port Statistics, in Chapter 7,
Configuring and Monitoring Ethernet Services.
Table A-19: tblPerfHistoryRMON fields

performance data was measured.
Port int Port number on which the
IntervalStart int Start time of the current
measurement interval
DropEvents int Number of dropped frames.
HistoryOctets int The total number of octets
received, including bad frames
and FCS octets (excluding
framing bits)
HistoryPkts int Total number of frames received,
including bad frames
BroadcastPkts int Number of broadcast frames
received
MulticastPkts int Number of multicast frames
received
CRCAlignErrors int Number of frames with Cyclic
Redundancy Check errors
received
UndersizePkts int Number of undersized frames
received
OversizePkts int Number of oversized frames
received
Fragments int Number of fragmented frames
received
Jabbers int Number of frames longer than a
defined size with an invalid CRC


Collision int Number of frames with collision
events received
Utilization int Estimated network utilization on
this interface at the mean
physical layer (in hundredths of a
percent)
A.3.2.10 tblPerfHistoryTuMid
The tblPerfHistoryTuMid table contains performance data regarding the TU mids being
used by the NEs in the system.
Table A-20: tblPerfHistoryTuMid fields

ESs int Number of Errored Seconds
SESs int Number of Severely Errored
Seconds
CSESs int Number of Consecutive Severely
Errored Seconds
BBE int Number of Background Block
Errors
PSCs int Number of protection switches
UASs int Number of Unavailable Seconds
TuMid int TU mid port number:
E1 – 1 to 21
Ethernet – 1 to 63
A.3.3 CardViewDBHist Structure

The CardViewDBHist database contains historical alarm and performance data collected by
the EMS-!LAN. This includes alarm data that is more than three days old (updated daily)
and performance data that is more than three months old (updated monthly). The tables that
make up the database are identical to those that appear in the CardViewDB database. For
more information, refer to CardViewDB Structure, page A-13.

A.4 Using the Query Analyzer

The Query Analyzer is the part of SQL Server that enables you to generate queries on the
information contained in the EMS-!LAN databases.
NOTE: The procedure that follows is intended to provide

basic operating instructions only. For detailed information
about using the Query Analyzer, please refer to the
documentation provided with Microsoft SQL Server.
!"To run the Query Analyzer:

1. Select Start # Programs # SQL Server # Query Analyzer to display a login
window.
Figure A-5: Connect to SQL Server window
2. Select the SQL server to which you want to connect by clicking and then
navigating to the required server.
3. In the Connection Information area, select one of the following options:
"# Use Windows NT authentication – to connect to SQL Server using the same
credentials that were used to connect to Windows NT. This is the recommended
option.
"# Use SQL Server authentication – enter the special system administrator user
name and password in the fields provided.
NOTE: This option is not available to those using the

EMS-!LAN prior to version 1.64.

4. Click OK. The Query Analyzer main window is displayed.
Figure A-6: Query Analyzer – main window
5. Select a database from the drop-down list on the toolbar.

6. Enter an SQL query in the window and then click on the toolbar or press <F5>.
The data that matches the query is displayed in the lower half of the Query Analyzer
window.
Figure A-7: Query Analyzer – display of matching query data
NOTES: To save queries to a text file, right-click in the upper

half of the window and select File # Save As. The queries
are saved in a file with the extension SQL, which can be
viewed with any text editor.
To save query results to a text file, right-click in the bottom

half of the window and select File # Save As. The query
results are saved in a file with the extension RPT, which can
be viewed with any text editor.

A.4.1 TNGDB Query Examples

The tables that follow provide sample queries that can be addressed to tables in the TNGDB
database. Each query example is a refinement of the one that proceeds it.
Table A-21: TNGDB – NE query examples
Query Description
SELECT * FROM tng_managedobject Returns all the NE data in the
tng_managedobject table
SELECT Returns the specified fields
label,address,status_no,severity from the tng_managedobject
from tng_managedobject table
SELECT CAST(label AS Sets a limit on column width
varchar(32)),CAST(address AS (in number of characters) for
varchar(32)),status_no,severity the specified fields from the
from tng_managedobject tng_managedobject table
In this example, the column
width limit for the Label and
IP address values of the NEs
that match the query is 32
characters.
SELECT CAST(label AS Returns results only for those
varchar(32)),CAST(address AS NEs whose Label contains 211
varchar(32)),status_no,severity
from tng_managedobject
--WHERE label LIKE '%211%'
SELECT CAST(label AS Returns results only for those
varchar(32)),CAST(address AS NEs whose IP address equals
varchar(32)),status_no,severity 211.150.158.211
from tng_managedobject
WHERE address = '211.150.158.211'

Table A-22: TNGDB – link query examples
Query Description
SELECT * FROM tng_link Returns all the link data in the
tng_link table
source_direction,source_ip_address, from the tng_link table
dest_direction,dest_ip_address from
tng_link
source_uuid,source_direction, from the tng_link table,
source_ip_address,dest_uuid, including fields not visible in
dest_direction, dest_ip_address the EMS-!LAN GUI, such as
from tng_link UUID
SELECT Returns only those links whose
source_direction,source_ip_address, source direction is East and
dest_direction,dest_ip_address from whose IP address is
tng_link 211.150.158.211
WHERE source_direction = 'E' AND
source_ip_address =
'211.150.158.211'
Table A-23: TNGDB – UUID query examples
Query Description
SELECT uuid,CAST(label AS Returns the specified fields
varchar(32)) AS 'Label' (including UUID) for NEs
,CAST(address AS varchar(32)) AS listed in the
'IP' ,status_no,severity from tng_managedobject table
tng_managedobject
SELECT Returns selected links from the
source_uuid,source_direction, tng_link table whose source
source_ip_address,dest_uuid, UUID (meaning, the NE that is
dest_direction,dest_ip_address from the source of the link) is equal
tng_link to a specified value
WHERE source_uuid = CONVERT(
binary(16) ,
0x344FB0D94C8BFF48A95AA1977C113466
);

Table A-24: TNGDB – cross-connect query examples
Query Description
SELECT * FROM CrossConnect2 Returns all cross-connects
WHERE trail_uuid IN from the CrossConnect2 table
(SELECT uuid FROM Trail based on specific trail and NE
WHERE uuidTrailEx = CONVERT( UUIDs
binary(16) ,
0x723D69209647364C94D5098C1093D825
))
AND ne_uuid = CONVERT( binary(16)
,
0x344FB0D94C8BFF48A95AA1977C113466
)
SELECT tu_mid FROM TUmid Returns all TU mids from the
WHERE ne_uuid = CONVERT( TUmid table for the NE with a
binary(16) , specific UUID
0x344FB0D94C8BFF48A95AA1977C113466
)
A.4.2 CardViewDB Query Examples

The tables that follow provide sample queries that can be addressed to tables in the
CardViewDB database. Each query example builds on the ones before it.
Table A-25: CardViewDB – NE query examples
Query Description
SELECT * FROM tblCurAlarms Returns the complete list of
current alarms from the
tblCurAlarms table
SELECT COUNT(*) FROM tblCurAlarms Returns the number of rows in
the tblCurAlarms table
NEiD,AlarmID,Status,Processed, from the tblCurAlarms table
DateTime,Severity FROM
tblCurAlarms

Query Description
SELECT Returns several fields from the
tblCurAlarms.NEiD, tblCurAlarms table as well as
tblCurAlarms.AlarmID, two fields (alarm name and
tblCurAlarms.Status, alarm description) from the
tblCurAlarms.Processed, tblAlarmID table (limited to 64
tblCurAlarms.DateTime, characters per parameter).
tblCurAlarms.Severity, As the last part of the query
CAST( tblAlarmID.AlarmName AS demonstrates, the alarm IDs
varchar(64)), from the two tables must
CAST( tblAlarmID.AlarmDesc AS match in order to combine the
varchar(64)) results.
FROM tblCurAlarms,tblAlarmID
WHERE
tblCurAlarms.AlarmID =
tblAlarmID.AlarmID
SELECT Returns the same information
tblCurAlarms.NEiD, as the previous query, except
tblCurAlarms.AlarmID, that the results are limited to
tblCurAlarms.Status, uncleared alarms on two
tblCurAlarms.Processed, specified dates related to the
tblCurAlarms.DateTime, NE at IP address
tblCurAlarms.Severity, 212.150.158.251.
CAST( tblAlarmID.AlarmName AS
varchar(64)),
CAST( tblAlarmID.AlarmDesc AS
varchar(64))
FROM tblCurAlarms,tblAlarmID
WHERE
tblCurAlarms.AlarmID =
tblAlarmID.AlarmID
AND
NEiD = '212.150.158.251' AND
Processed = 0 AND
DateTime BETWEEN '2003-09-08' AND
'2003-09-09'

Table A-26: CardViewDB – performance query examples
Query Description
SELECT * FROM tblPerfHistoryMulti Returns all performance data
for the Multiplexer subsystem
from the tablPerfHistoryMulti
table
SELECT * FROM tblPerfHistoryMulti Returns Multiplexer
WHERE NEiD = '212.150.158.250' performance data recorded on
September 7, 2003 at 2:30 pm
AND DateTime = '2003-09-07 14:30' for the NE with IP address
212.150.158.250
SELECT Returns selected Multiplexer
NEiD,DateTime,EastESs,EastSESs,EastUASs performance fields for a
FROM tblPerfHistoryMulti specific NE during a specific
WHERE NEiD = '212.150.158.250' time interval, sorted in
descending date/time order
AND DateTime BETWEEN '2003-09-07' AND
'2003-09-08'
ORDER BY DateTime DESC
tblPerfHistoryMulti.NEiD, from the tblPerfHistoryMulti
tblPerfHistoryMulti.DateTime, table as well as the fields
tblPerfHistoryMulti.EastESs AS specified from the
'Multiplexor ESs', tblPerfHistoryRegen table for a
tblPerfHistoryRegen.EastESs AS specific NE during a specific
'Regenerator ESs', time interval, sorted in
tblPerfHistoryRegen.EastCSESs AS descending date/time order
'Regenerator CSESs'
FROM tblPerfHistoryMulti inner join
tblPerfHistoryRegen
ON tblPerfHistoryMulti.DateTime =
tblPerfHistoryRegen.DateTime
WHERE tblPerfHistoryMulti.NEiD =
'212.150.158.250'
AND tblPerfHistoryMulti.DateTime
BETWEEN '2003-09-07' AND '2003-09-08'
ORDER BY tblPerfHistoryMulti.DateTime
DESC


B
PC Backup and RDR
B.1 Overview
This appendix describes available backup features for the EMS-µLAN, including database
backups and remote database replication (RDR). In addition, this appendix describes how to
back up and restore NE configuration files.
B.2 Performing Database Backups

It is very important to back up the SQL databases containing vital information from the
EMS-µLAN management station on a regular basis. Backups should also be performed
before performing major software upgrades and when reconfiguring the network.
Backups are made regularly to the Standby EMS (SEMS) µLAN station to permit recovery
of critical configuration, performance, and maintenance information in the event of a failure.
The following SQL databases should be backed up regularly:
!" CardView DB – contains all current performance, alarms, and maintenance data
!" TNGDB – contains all configuration information, including cross-connects, trails, links,
and Topology Browser data
NOTE: A third database, CardViewDBHist, contains

historical performance and maintenance information, and
does not need to be included in the regular backup routine.
In the event of a failure in the currently operating management station, known as the
Working EMS-µLAN (WEMS), automatic failover is performed, enabling the SEMS to take
over management of the µLAN NE network. This redundancy provides high availability
when maintaining network access is of critical importance.
426006-2406-033-A00 ECI Telecom Ltd. Proprietary B-1

PC Backup and RDR BroadGate™ EMS-µLAN User's Manual
Backups are performed automatically by the Backup Tool. They can also be performed
manually with the Enterprise Manager, which is part of Microsoft SQL Server version 7.0.
IMPORTANT NOTE: If SQL Server is already installed on

either the WEMS or SEMS, you must change the login
information for the MSSQLServer and SQLServerAgen
services from the Local System to the current user before
performing any backups.
To do this, refer to the EMS-µLAN RDR Installation
Procedure document.
B.2.1 Using the Backup Tool

The Backup Tool, which is available in the WEMS, provides an easy-to-use tool for
configuring automatic database backups from the EMS-µLAN management station. Daily
backups are performed at midnight to save any changes that occurred during the day. A full
backup is performed weekly. The Backup Tool enables you to select the folders to which
data for the current week and the previous week should be stored.
!"To configure backups with the Backup Tool:
1. Select Start # Network Management # Backup Tool.
The Backup tab of the NMS DB protection window is displayed.
Figure B-1: NMS DB protection window – Backup tab
B-2 ECI Telecom Ltd. Proprietary 426006-2406-033-A00

BroadGate™ EMS-µLAN User's Manual PC Backup and RDR
2. In the Current folder field, enter the path to the folder where current database data
should be stored,
OR
Click to browse to the location and click Open.

3. In the History folder field, enter the path to the folder where current data should be
stored after the next full backup is performed,
OR

4. Click Update now to save the folder locations.
The system is now configured to perform automatic backups. To perform a manual backup,
click Backup now.
Automatic backups are performed on a weekly basis, as follows:
A full database backup is performed once a week. During the rest of the week, a database
differences file, containing the changes made to the database since the last full backup, is
created each day at midnight. The database differences file for the current day overwrites
the database differences file of the previous day.
DB Changes
Full backup
DB differences
Full backup
Full backup
DB differences
Su M Tu W Th F Sa Su M Tu W Th F Sa Su
Figure B-2: Daily database backup schedule

B.2.2 Using the Restore Tool

The Restore Tool, which is available in the SEMS, is used to restore database backup files
to the EMS-µLAN management station. This can be used to streamline the process of
setting up a new management station. The EMS-µLAN must be shut down before
performing the restore. It is restarted after the restore has been completed.
!"To use the Restore Tool:
1. Select Start # Network Management # Restore Tool.
The Restore tab of the NMS DB protection window is displayed.
Figure B-3: NMS DB protection window – Restore tab
2. In the Restore folder field, enter the path to the folder where current database data
is stored,
OR

3. Click Setup restore folder to save the location.
4. Click Stop NMS to shut down the EMS-µLAN.
5. Click Restore now to start the restore process.
6. When the restore process is complete, click Start NMS to restart the EMS-µLAN.

B.2.3 Backing Up with SQL Server

The Enterprise Manager in Microsoft SQL Server can also be used to back up the
CardViewDB and TNGDB databases in the EMS-µLAN management station to the SEMS.
!"To perform a backup with SQL Server:
1. Create a folder called DB_Backup on the C:\ drive of the SEMS.
2. Select Start # Programs # SQL Server # Enterprise Manager.
3. In the Enterprise Manager tree, select Databases to display the databases in the
system.
4. Right-click the CardViewDB database and select All tasks # Backup Database
# Database Complete # Add from the shortcut menu displayed. The SQL Server
Backup window is displayed:
Figure B-4: SQL Server Backup window

5. In the Backup area, make sure that the Database - complete option is selected.
6. In the Destination area, click Add. The Choose Backup Destination window is
displayed.
Figure B-5: Choose Backup Destination window
7. Select File name and enter a destination and file name for the backup, for example,
C:\MSSQL7\BACKUP\CardView_[date]. Click OK. The destination is displayed in
the Destination area of the SQL Server Backup window.
8. In the Overwrite area, select the Append to media or Overwrite existing media
option, as required.
9. In the Schedule area, select the checkbox and click to display the Edit Schedule
window. Schedule the backup as required and click OK.
10. Repeat steps 4 through 9 for the TNGDB database. When entering the destination,
use a path and file name such as C:\MSSQL7\BACKUP\CardView_[date].
NOTES: A weekly recurring backup is recommended.

Regardless of the backup schedule defined, it is
recommended to perform a full backup every two months to a
different destination than the one normally used.
B.2.4 Backup Troubleshooting

If a faulty backup resulting in an error message occurs, the likely cause is one of the
following:
!" The backup took place during a period of heavy alarm activity in the EMS-µLAN
!" The backup took place as the EMS-µLAN was gathering performance data
!" Another background activity interrupted the backup process

In all cases, it is recommended to close the following EMS-µLAN applications:

!" Topology Browser
!" Performance Viewer
!" Alarms Viewer
!" Trail Manager
Next, enter the Control Panel and stop all services beginning with RRNM. Repeat the
backup and then afterwards return to the Control Panel to restart these services.
B.3 Remote Database Replication (RDR)

To ensure high availability, the µLAN network managed by the EMS-µLAN can be fitted
with RDR protection. This cost option consists of two management stations – the WEMS
and the SEMS. (These roles are assigned during RDR installation, as described in the
EMS-µLAN RDR Installation Procedure document.) Both stations have IP connections to
the managed network, as well as a second connection for redundancy.
Figure B-6: RDR
CAUTION: There should be at least a 2Mbps connection

between the working WEMS and the SEMS.

The EMS-µLAN installed on the WEMS performs the regular management operations on
the network. In addition, the WEMS is used to perform automatic backups of database files
(as described in Performing Database Backups, page B-1), and backups of NE configuration
files (as described in Replacing the μLAN, page B-9).
The EMS-µLAN installed on the SEMS collects alarm and performance data from the
network, but does not perform any configuration operations.
B.3.1 Switching from the WEMS to the SEMS

If a problem should occur on the WEMS, the SEMS is switched from Standby mode to
Working mode, enabling it to take over management of the network. The data it contains is
current to the last backup that was performed.
!"To switch from the WEMS to the SEMS:
1. On the first station (Main – which has been serving as the WEMS), select Start #
Network Management # Backup Tool. The Backup tab of the NMS DB
protection window is displayed, as shown in Figure B-1.
2. Click Switch to standby. (This may not be possible, depending on the nature of the
problem in the WEMS.)
3. On the second station (Protection – which has been serving as the SEMS), select
Start # Network Management # Restore Tool. The Restore tab of the NMS
DB protection window is displayed, as shown in Figure B-3.
4. Restore the database from the stored backup to the SEMS, as described in Using the
Restore Tool, page B-4.
5. Click Switch to working mode. The SEMS takes over management of the network.
NOTE: Depending on the nature of the problem in the

WEMS, it may not be possible to switch it to Standby mode
before moving the SEMS to Working mode.

B.3.2 Switching Back to Original Roles

When the problem in the first station that caused the switch to the SEMS has been resolved,
the roles can be switched back to their original configuration, if required.
!"To switch the SEMS back to Standby mode:
1. On the second station (Protection), select Start # Network Management #
Backup Tool. The Backup tab of the NMS DB protection window is displayed, as
shown in Figure B-1.
NOTE: If you want to restore the database in the first station

(Main) with the database in the second station, manually back
up the database to the shared directory, as described in Using
the Backup Tool, page B-2.
2. Click Switch to standby. The station reverts to its original Standby role.
3. On the first station (Main), select Start # Network Management # Restore
Tool. The Restore tab of the NMS DB protection window is displayed, as shown in
Figure B-3.
NOTE: If you want to restore the database in the second

station, which was in use while the first station was down, to
the first station, restore the database to the shared directory,
as described in Using the Restore Tool, page B-4.
4. Click Switch to working mode. The station reverts to its original Working role.
B.4 Replacing the μLAN

The following steps must be performed to replace a μLAN system:
!" Step 1: Check the faulty μLAN’s parameters and install the new μLAN NE
!" Step 2: Back up the database configuration for the faulty μLAN
!" Step 3: Connect the μLAN to the topology
!" Step 4: Restore the database configuration on the new μLAN
!" Step 5: Perform a Restore NE Configuration on Reset operation on the μLAN
!" Step 6: Reset the μLAN
All these steps are described in the BroadGate µLAN Installation, Operation and
Maintenance (IOM) Manual. Most steps are performed using the Download / Backup
Center application, which is described in Chapter 9, Additional Services and Tools.


C
TU-12 KLM Notation Conversion
Tables
The table in this appendix describes how to convert the TU-12 numbering used in the Trail
Manager to KLM notation. KLM is also used by other ECI Telecom's Optical Networks
Division products, such as the XDM® and SYNCOM.
In KLM notation, the first digit (K) refers to the TUG-3 tributary unit, the second digit (L)
refers to the row in the TUG-3 containing the relevant TU-12, and the third digit (M) refers
to the column.
K=1 K=2 K=3

1 22 43 2 23 44 3 24 45
4 25 46 5 26 47 6 27 48
7 28 49 8 29 50 9 30 51
L 10 31 52 11 32 53 12 33 54
13 34 55 14 35 56 15 36 57
16 37 58 17 38 59 18 39 60
19 40 61 20 41 62 21 42 63
Figure C-1: KLM notation
Table C-1: TU-12 KLM notation conversion table
µLAN TU-12 XDM/SYNCOM TU-12

1 1-1-1
2 2-1-1
3 3-1-1
4 1-2-1
5 2-2-1
6 3-2-1
7 1-3-1
8 2-3-1
426006-2406-033-A00 ECI Telecom Ltd. Proprietary C-1

TU-12 KLM Notation Conversion Tables BroadGate™ EMS-µLAN User's Manual

9 3-3-1
10 1-4-1
11 2-4-1
12 3-4-1
13 1-5-1
14 2-5-1
15 3-5-1
16 1-6-1
17 2-6-1
18 3-6-1
19 1-7-1
20 2-7-1
21 3-7-1
22 1-1-2
23 2-1-2
24 3-1-2
25 1-2-2
26 2-2-2
27 3-2-2
28 1-3-2
29 2-3-2
30 3-3-2
31 1-4-2
32 2-4-2
33 3-4-2
34 1-5-2
35 2-5-2
36 3-5-2
37 1-6-2
38 2-6-2
39 3-6-2
40 1-7-2
41 2-7-2
42 3-7-2
43 1-1-3
44 2-1-3
45 3-1-3
46 1-2-3
47 2-2-3
48 3-2-3
49 1-3-3
50 2-3-3
51 3-3-3
52 1-4-3
53 2-4-3
C-2 ECI Telecom Ltd. Proprietary 426006-2406-033-A00

BroadGate™ EMS-µLAN User's Manual TU-12 KLM Notation Conversion Tables

54 3-4-3
55 1-5-3
56 2-5-3
57 3-5-3
58 1-6-3
59 2-6-3
60 3-6-3
61 1-7-3
62 2-7-3
63 3-7-3
426006-2406-033-A00 ECI Telecom Ltd. Proprietary C-3

TU-12 KLM Notation Conversion Tables BroadGate™ EMS-µLAN User's Manual
C-4 ECI Telecom Ltd. Proprietary 426006-2406-033-A00

D
Glossary
100BaseT 100 Mbps baseband data transmission over twisted-pair copper wire
10BaseT 10 Mbps baseband data transmission over twisted-pair copper wire
ADM Add-and-Drop Multiplexer
AIS Alarm Indication Signal
ASIC Application-Specific Integrated Circuit
BPDU Bridge Protocol Data Unit
C-VLAN Customer VLAN
CORBA Common Object Request Broker Architecture
CPU Central Processing Unit
CRC Cyclic Redundancy Check
DCC Data Communication Channel
DLL Dynamic Link Library
EMS Element Management System
EoS Ethernet over SDH
FTP File Transfer Protocol
HTML Hypertext Markup Language
HTTP HyperText Transfer Protocol
ICMP Internet Control Message Protocol
IEEE Institute of Electrical and Electronics Engineers
IP Internet Protocol
KLM A three-figure address (KLM) in an AU-4 structured SDH frame,
where K is the TUG-3 number, L is the TU-2 number, and M is the
TU-1 number
LAN Local Area Network
LCAS Link Capacity Adjustment Scheme
MAC Media Access Control
MIB Management Information Base
MTU Maximum Transmission Unit
426006-2406-033-A00 ECI Telecom Ltd. Proprietary D-1

Glossary BroadGate™ EMS-µLAN User's Manual
MU Main Unit
NE Network Element
NS Name Server
NMS Network Management System
ODBC Open Data Base Connectivity
OH Overhead
P-VLAN Provider VLAN
PDU Protocol Data Unit
PPI Physical Port Interface
PRC Primary Reference Clock
PTP Point-to-point
PVID Port VLAN ID
RDI Remote Defect Indication
RDR Remote Database Replication
RMON Remote Monitoring
RSTP Rapid Spanning Tree Protocol
Rx Receiving
SDH Synchronous Digital Hierarchy
SEC SDH Equipment Clock
SEMS Standby Element Management System
SFD Start Frame Delimiter
SMS Short Message Service
SNCP Subnetwork Connection Protection
SNMP Simple Network Management Protocol
SNTP Simple Network Time Protocol
SOH Section Overhead
SPI SDH/SONET Physical Interface
SQL Structured Query Language
SSM Status Synchronization Messages
SSU-L Synchronization Source Utility – Local version
SSU-T Synchronization Source Utility – Transit version
STM Synchronous Transfer Mode
D-2 ECI Telecom Ltd. Proprietary 426006-2406-033-A00

BroadGate™ EMS-µLAN User's Manual Glossary
STM-1 Synchronous Transport Module 1, 155.52 Mbps

STP Spanning Tree Protocol
TIU Tributary Interface Unit
TMN Telecommunications Management Network
TTI Trail Trace Identifier
TU Tributary Unit
TUG Tributary Unit Group
UDP User Data Protocol
VLAN Virtual Local Area Network
VPN Virtual Private Network
WAN Wide Area Network
WEMS Working Element Management System
XC Cross-connect
426006-2406-033-A00 ECI Telecom Ltd. Proprietary D-3

Glossary BroadGate™ EMS-µLAN User's Manual
D-4 ECI Telecom Ltd. Proprietary 426006-2406-033-A00

I
Index
A C
Accessing Card information
Download / Backup Center, 9-12 viewing MU, 6-4
Accessories CD, 2-2, 2-3 viewing TIU, 6-7
Adding Card View, 1-6
external NEs, 4-18 About window, 3-11
NE to NE list using Download / Backup building trails, 6-24
Center, 9-15 configuring Ethernet services, 7-1
Advanced options configuring J2/J1 bit, 6-29
defining, 6-45 defining SNCP protection, 6-29
Alarm Viewer, 1-7 deleting cross-connections, 6-28
Alarms displaying, 6-2
acknowledging, 8-8 editing SNCP protection, 6-32
analyzing, 8-5 High-order subsystem, 6-10
defining Ethernet settings, 7-33 installing, 2-12
defining sound settings, 8-8 Low-order subsystem, 6-10
unacknowledging, 8-8 Multiplexer subsystem, 6-10
Analyzing overview, 6-1
alarms, 8-5 PPI subsystem, 6-10
performance, 8-9 reconnecting, 6-3
refreshing information, 6-4
B Regenerator subsystem, 6-10
resetting NE, 6-47
Backing up resetting NEs, 6-47
troubleshooting, B-6 SPI subsystem, 6-10
Backups Terminal subsystem, 6-10
database, B-1 Timing subsystem, 6-10
using Backup Tool, B-2 using SNCP protection commands, 6-35
using Restore Tool, B-4 viewing MU card information, 6-4
using SQL Server, B-5 viewing performance information, 6-36
BroadGate μLAN viewing TIU card information, 6-7
craft terminal, 1-4 window, 6-3
overview, 1-1 CardView DB, B-1
replacing, B-9 Configuration
resetting, 6-47 backing up, 9-20
status indicators, 6-3 restoring, 9-21
TIU-14E1-3E3-6Eth, 7-1 Configuring
TIU-16E1-2Eth, 1-1, 7-1 CardView operation location, 2-28
TIU-21E1-6Eth, 1-1, 7-1 Ethernet packet size, 7-10
TIU-21E1-6Eth-A, 7-1 Ethernet port priorities, 7-14
TIU-3E3-14E1-6Eth, 1-1 Ethernet switching parameters, 7-6
Building J/J1 bit, 6-29
trails in Card View, 6-24 MTNM server, 2-22
426006-2406-033-A00 ECI Telecom Ltd. Proprietary I-1

Index BroadGate™ EMS-µLAN User's Manual
MTU settings, 2-25 deleting NEs, 4-17

network managers, 2-26 main window, 4-11
Orbix for NMS-integrated mode, 2-21 menu bar, 4-12
Orbix settings for eNM integration, 2-28 redefining NEs, 4-17
RSTP protection, 7-27 toolbar, 4-13
SNMP settings, 2-23 Displaying
SNTP on an NE, 4-25 Ethernet performance, 8-12
trace IDs, 6-44 NE cross-connections, 5-26
VLAN tables, 7-15 SDH performance, 8-11
Contacts and relays selected alarms, 8-7
available tables, 6-22 trails, 5-23
defining, 6-21 Double-tagging, 7-8
Control Panel applet, 9-8 Download / Backup Center
Conversion tables, C-1 accessing, 9-12
Craft Terminal. See LCT-μLAN. adding an NE to the NE list, 9-15
See LCT-μLAN backing up NE configuration, 9-20
Creating overview, 9-11
links, 4-19 performing embedded SW upgrade, 9-16
links to external NEs, 4-21 performing NE reset operation, 9-24
NEs, 4-14 performing Restore NE on Reset operation,
new VLAN, 7-23 9-23
trails, 5-8 performing SW package upgrade, 9-23
CSF indications, 7-24 restoring NE configuration, 9-21
Customizing
performance display, 8-13 E
Embedded SW upgrade, 9-16
D
EMS-!LAN
Database consistency check, 5-22 SQL databases, A-1
Defining EMS-µLAN
advanced options, 6-45 advanced options, 6-45
contacts and relays, 6-21 EMS-μLAN
default gateway, 3-2 basic operations, 3-8
Ethernet alarm settings, 7-33 bidirectional trails, 5-2
LAN port configuration, 7-11 Card View, 1-6
redefining NEs, 4-17 components, 1-5
root and blocking elements, 7-31 configuration, 2-23
SNCP protection in Card View, 6-29 connectivity, 1-3
SNCP trail protection, 5-16 Control Panel applet, 9-8
T4 squelch level, 6-20 creating trails, 5-8
timing sources, 6-19 defining contacts and relays, 6-21
Deleting defining SNCP trail protection, 5-16
cross-connections in Card View, 6-28 defining T4 squelch level, 6-20
links, 4-24 defining timing sources, 6-19
NEs, 4-17 deleting trails, 5-27
trails, 5-27 displaying and editing trails, 5-23
VLAN table entries, 7-26 displaying cross-connection information,
Design mode, 4-10 5-26
adding external NEs, 4-18 Download / Backup Center, 9-11
creating links, 4-19 Ethernet services, 7-1
creating links to external NEs, 4-21 forcing timing source, 6-21
creating NEs, 4-14 general operating procedures, 3-8
deleting links, 4-24 hardware requirements, 2-1
I-2 ECI Telecom Ltd. Proprietary 426006-2406-033-A00

BroadGate™ EMS-µLAN User's Manual Index
inserting external NE, 5-24 creating EMS session, 1-13

inserting NE, 5-24 creating links, 1-14
installation, 2-1 monitoring alarms, 1-15
installation control, 9-10 viewing current information, 1-16
integrated mode, 1-8 viewing link information, 1-14
KLM conversion tables, C-1 Ethernet port statistics
maintenance options, 6-41 setting, 7-39
modifying SNCP trail protection, 5-19 viewing, 7-35
network management, 9-8 Ethernet service configuration, 7-6
Network Resolution Tool, 1-7, 9-3 configuring packet size, 7-10
overview, 1-2 defining aging time, 7-10
Performance Viewer, 1-7, 8-1 enabling RSTP protection, 7-9
performing loopbacks, 6-42, 6-43 enabling the scrambler, 7-9
preparing for first-time use, 3-1 selecting switching mode, 7-7
removing SNCP trail protection, 5-18 setting priority ratio, 7-7
repairing a trail, 5-25 Ethernet services
resetting NEs, 6-47 configuration procedures, 7-4
RSTP protection, 7-27 configuring port parameters, 7-4
running software emulation, 3-9 configuring port priorities, 7-4, 7-14
security, 3-11 configuring RSTP protection, 7-5, 7-27
Services Watchdog, 9-1 configuring switching parameters, 7-6
setting timing sources, 6-18 configuring VLAN tables, 7-15, 7-19
software emulation, 1-16 creating new VLAN, 7-23
software requirements, 2-2 default VLAN configuration for PTP, 7-18
standalone mode, 1-5 defining alarm settings, 7-33
status indicators, 6-3 defining LAN port configuration, 7-4, 7-11
Topology Browser, 1-5 defining root and blocking elements, 7-31
topology management modes, 3-9 defining VLAN line tables, 7-5
Trail Manager, 1-6 deleting VLAN table entries, 7-26
trail types, 5-2 double-tagging guidelines, 7-25
unidirectional trails, 5-4 enabling CSF and TSF indications, 7-24
uninstalling, 2-36 enabling double-tagging, 7-8
viewing access port information, 6-17 modifying VLAN tables, 7-26
viewing active timing source, 6-19 overview, 7-1
viewing physical port information, 6-14 Performance Chart window, 7-36
viewing SDH/SONET physical port port VLAN ID definitions, 7-17
information, 6-12 setting Ethernet port statistics, 7-39
viewing SNCP protection status, 5-20 viewing port RSTP details, 7-32
viewing trail attributes, 5-14 viewing RMON statistics, 7-35
Windows services, 1-8, 9-1 viewing STP port configuration, 7-31
workflow, 3-12 VLAN definitions, 7-16
Enabling
CSF and TSF indications, 7-24 F
eNM, 1-2, 1-7, 1-8, 2-15, 2-25, 2-30
building trails, 6-24 First-time preparations, 3-1
creating EMEs, 1-11 changing DCC mode and IPs remotely, 3-5
creating links, 1-11 configuring gateway redundancy, 3-2
creating slave manager, 1-10 defining default gateway, 3-2
monitoring alarms, 1-12 management connections, 3-2
MTU settings, 2-26 starting Topology Browser, 3-8
viewing current information, 1-12
eNM LightSoft, 1-2, 1-8, 2-15, 2-30
building trails, 6-24

G editing SNCP protection, 6-32

emulation, 1-16
Glossary, D-1 monitoring alarms, 1-12, 1-15
using SNCP protection commands, 6-35
I viewing current information, 1-12, 1-16
viewing link information, 1-14
Inserting
external NE on a link, 5-24
NE on a link, 5-24 L
Installation LCT-μLAN
before beginning, 2-2 introduction, 1-4
configuring EMS-µLAN as managed EMS Links
under NMS, 2-35 creating, 4-19
configuring EMS-µLAN as slave manager, creating to external NEs, 4-21
2-32 deleting, 4-24
for eNM integrated mode, 2-2
hardware requirements, 2-1
on eNM workstation, 2-30
M
overview, 2-1 Maintenance
RTSetup window, 2-4 performing operations, 6-41
software requirements, 2-2 performing SPI loopbacks, 6-41
Installation CD, 2-2, 2-4 performing subsystem operations, 6-42
Installing viewing operations, 6-43
µLAN Software, 2-30 Modifying
Active Alarm View, 2-14 SNCP protection in Card View, 6-32
DAO SDK 3.5, 2-5 SNCP trail protection, 5-19
eIMI, 2-3 MTU Settings
EMS-μLAN application, 2-10 eNM, 2-26
Fix Disk, 2-30 in NEs, 2-26
for NMS integrated mode, 2-18 management station, 2-25
Java Card View, 2-12 NMS, 2-26
Java Download, 2-13
Java Runtime Environment, 2-9 N
Java Terminal, 2-13
LCT-µLAN, 2-14 NEs
Log Viewer, 2-13 adding external, 4-18
MS-SQL Server 7.0, 2-6 backing up the configuration, 9-20
MTNM server, 2-22 configuring SNTP, 4-25
Orbix, 2-3 creating, 4-14
Orbix for NMS-integrated mode, 2-18 deleting, 4-17
package for eNM-integrated manager, 2-31 discovering, 4-16, 4-19
package for NMS-integrated manager, 2-34 performing SW package upgrade, 9-23
SNMP Service, 2-9 redefining, 4-17
Tardis, 2-17 resetting, 6-47, 9-24
VNC server, 2-15 restoring the configuration, 9-21
Integrated mode, 1-8 selecting, 8-5
building trails, 6-24 setting the time, 4-24
creating EMEs, 1-11 Nested VLANs. See Double-tagging
creating EMS session, 1-13 Network management
creating links, 1-11, 1-14 installation control, 9-10
creating slave manager, 1-10 Service Control I tab, 9-8
defining SNCP protection, 6-29 Service Control II tab, 9-9
deleting cross-connections, 6-28

Network Resolution Tool, 1-7, 9-3 NE reset operation using

selecting element, 9-7 Download / Backup Center, 9-24
selecting ring or link, 9-6 Restore NE on Reset operation using
Download / Backup Center, 9-23
O subsystem maintenance, 6-42
SW package upgrade using
Operation Modes Download / Backup Center, 9-23
integrated, 1-8
standalone, 1-5
Q
P Query Analyzer, A-22
CardViewDB examples, A-27
PC Backup TNGDB examples, A-25
overview, B-1
Performance
R
analyzing, 8-9
resetting parameters, 6-39 RDR, B-7
setting thresholds, 6-40 restoring original roles, B-9
viewing current parameters, 6-37 Remote Database Replication. See RDR
viewing information, 6-36 Removing
Performance Viewer, 1-7 SNCP trail protection, 5-18
acknowledging alarms, 8-8 Repairing
Alarm Viewer, 1-7 trails, 5-25
analyzing alarms, 8-5 Replacing
analyzing performance, 8-9 BroadGate μLAN, B-9
customizing performance display, 8-13 Resetting
defining sound settings, 8-8 NEs, 6-47
displaying Ethernet performance, 8-12 performance parameters, 6-39
displaying SDH performance, 8-11 Restoring
displaying selected alarms, 8-7 NE configuration using
menu bar, 8-3 Download / Backup Center, 9-21
overview, 8-1 RSTP protection, 7-27
performance in graphs, 8-14 defining root and blocking elements, 7-31
performance in tables, 8-9 enabling, 7-9
selecting alarm analysis interval, 8-6 viewing port RSTP details, 7-32
selecting NEs, 8-5 viewing STP port configuration, 7-31
selecting performance analysis interval, Run mode, 4-2
8-11 background map, 4-6
selecting performance parameters, 8-9 east/west conventions, 4-7
selecting RMON performance parameters, element icon key, 4-4
8-10 element menu, 4-9
starting, 8-1 element status colors, 4-4
toolbar, 8-4 general browser menu, 4-9
unacknowledging alarms, 8-8 link menu, 4-10
window elements, 8-2 main window, 4-2
Performing menu bar, 4-7
embedded SW upgrade using Navigator, 4-5
Download / Backup Center, 9-16 toolbar, 4-8
loopbacks, 6-42, 6-43
maintenance operations, 6-41
NE configuration backup using
Download / Backup Center, 9-20

S viewing active source, 6-19

viewing information, 6-18
Selecting TNGDB, B-1
alarm analysis interval, 8-6 Topology Browser, 1-5
analysis interval, 8-11 adding external NEs, 4-18
NEs, 8-5 creating links, 4-19
performance parameters, 8-9 creating links to external NEs, 4-21
RMON performance parameters, 8-10 creating NEs, 4-14
SEMS, B-1 deleting links, 4-24
Setting deleting NEs, 4-17
performance thresholds, 6-40 Design mode, 3-9, 4-1, 4-10
port statistics, 7-39 displaying Card View, 6-2
SNTP, 4-24 overview, 4-1
Slave Manager redefining NEs, 4-17
troubleshooting, 2-33 Run mode, 3-9, 4-1, 4-2
SNCP protection starting, 4-2
defining, 5-16 starting Performance Viewer, 8-1
modifying, 5-19 Trace IDs
removing, 5-18 configuring, 6-44
viewing status, 5-20 Trail Manager, 1-6
SNMP settings additional options, 5-21
configuring, 2-23 building trails, 1-6
SNTP, 4-24 creating trails, 5-8
configuration, 4-25 defining SNCP trail protection, 5-16
launching Tardis, 4-25 deleting trails, 5-27
Software displaying and editing trails, 5-23
upgrade, 9-16 displaying cross-connection information,
Software emulation, 1-16 5-26
installation and configuration, 2-15 editing J2 strings, 5-21
operating, 3-9 FTP, 5-21
SQL Databases inserting external NE, 5-24
accessing, A-2 inserting NE, 5-24
CardViewDB structure, A-13 modifying SNCP trail protection, 5-19
CardViewDBHist structure, A-21 overview, 5-1
structure, A-4 ping, 5-21
TNGDB structure, A-4 removing SNCP trail protection, 5-18
using Query Analyzer, A-22 repairing trail, 5-25
Standalone mode, 1-5 running database consistency check, 5-22
Standby EMS. See SEMS SDH resource availability, 1-6
Starting starting, 5-4, 5-5
Network Resolution Tool, 9-4 Telnet, 5-21
Performance Viewer, 8-1 trail representation, 1-6
Topology Browser, 3-8 viewing SNCP protection status, 5-20
Trail Manager, 5-4 viewing trail attributes, 5-14
window, 5-6
T Trails
1-1-1 strategy, 6-27
Timing
additional options, 5-21
defining primary and secondary sources,
bidirectional trail, 5-2
6-19
building with Card View, 6-24
defining T4 squelch level, 6-20
configuring J2/J1 bit, 6-29
forcing timing source, 6-21
creating, 5-8
selecting SSM, 6-20

defining SNCP protection in Card View, West and East areas, 6-10
6-29 Viewing
defining SNCP protection on, 5-16 access port information, 6-17
deleting, 5-27 active timing source, 6-19
deleting cross-connections in Card View, current performance parameters, 6-37
6-28 Ethernet port statistics, 7-35
displaying and editing, 5-23 maintenance operations, 6-43
displaying and editing cross-connection MU card information, 6-4
information, 5-26 performance information, 6-36
hitless, 5-3 physical port information, 6-14
inserting an external NE, 5-24 port RSTP details, 7-32
inserting an NE, 5-24 SDH/SONET physical port information,
modifying SNCP protection in Card View, 6-12
6-32 SNCP protection status, 5-20
modifying SNCP protection on, 5-19 STP port configuration, 7-31
protected, 5-3 timing information, 6-18
removing SNCP protection on, 5-18 TIU card information, 6-7
repairing, 5-25 trail information, 5-14
trail types, 5-2 VLAN line tables
unidirectional trail, 5-4 Current table, 7-21
using SNCP protection commands in Card definitions, 7-16
View, 6-35 double-tagging, 7-8
viewing attributes, 5-14 duplex settings, 7-13
viewing SNCP protection status, 5-20 Static table, 7-21
TSF indications, 7-24 VLAN tables, 7-15
TU-12, 5-1, 5-23 configuration for PTP services, 7-18
editing allocation, 5-23 configuring, 7-19
deleting entries, 7-26
U double-tagging guidelines, 7-25
modifying, 7-26
Uninstalling port VLAN ID definitions, 7-17
preliminary actions, 2-37 VNC, 2-15
Using configuring server, 2-16
SNCP protection commands in Card View, installing server, 2-15
6-35
W
V
WEMS, B-1
View Details window Windows services, 1-8, 9-1
configuring trace IDs, 6-44 Alarm Synchronization, 9-3
defining contacts and relays, 6-21 Keep Alive, 1-8, 9-2
General area, 6-10 Performance, 9-3
Information menu, 6-12 Performance History, 1-8
overview, 6-8 Services Watchdog, 9-1
performing loopbacks, 6-42, 6-43 SNMP Trap, 1-8
performing maintenance operations, 6-41 Trail Alignment, 9-3
PPI View Info window, 6-14 Trap, 9-2
resetting performance parameters, 6-39 Working EMS. See WEMS
setting performance thresholds, 6-40
SPI View Info window, 6-12
Terminal View Info window, 6-17
Timing View Info window, 6-18
using, 6-10


BG EMS - LAN UM A00 2-2 en

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

BG EMS - LAN UM A00 2-2 en

Transféré par

Droits d'auteur :

Formats disponibles

BroadGate™

© Copyright by ECI Telecom Ltd., 2004. All rights reserved worldwide.

1 Introduction ............................................................................................... 1-1

2 Installation ................................................................................................. 2-1

3 General Operating Instructions................................................................ 3-1

4 Building the Network ................................................................................ 4-1

426006-2406-033-A00 ECI Telecom Ltd. Proprietary iii

4.7 Creating Links .................................................................................. 4-19

5 Building Trails ........................................................................................... 5-1

6 Configuring and Monitoring μLAN NEs ................................................... 6-1

7 Configuring and Monitoring Ethernet Services ...................................... 7-1

iv ECI Telecom Ltd. Proprietary 426006-2406-033-A00

8 Using the Alarm and Performance Viewer .............................................. 8-1

9 Additional Services and Tools ................................................................. 9-1

A SQL Reference .......................................................................................... A-1

426006-2406-033-A00 ECI Telecom Ltd. Proprietary v

vi ECI Telecom Ltd. Proprietary 426006-2406-033-A00

Figure 3-5: WinVNC: Current User Properties window ..................................................... 3-10

426006-2406-033-A00 ECI Telecom Ltd. Proprietary vii

viii ECI Telecom Ltd. Proprietary 426006-2406-033-A00

Figure 9-9: Download Center Log In window9-12

426006-2406-033-A00 ECI Telecom Ltd. Proprietary ix

x ECI Telecom Ltd. Proprietary 426006-2406-033-A00

Table 9-3: Action menu options – element .......................................................................... 9-7

426006-2406-033-A00 ECI Telecom Ltd. Proprietary xi

xii ECI Telecom Ltd. Proprietary 426006-2406-033-A00

NOTE: Additional TIUs are under development and will be

426006-2406-033-A00 ECI Telecom Ltd. Proprietary 1-1

1.1 Powerful Centralized Management

1-2 ECI Telecom Ltd. Proprietary 426006-2406-033-A00

1.2 Management Connectivity

426006-2406-033-A00 ECI Telecom Ltd. Proprietary 1-3

1.3 LCT-μLAN Craft Terminal

Figure 1-1: LCT Manager window

1-4 ECI Telecom Ltd. Proprietary 426006-2406-033-A00

1.4 EMS-μLAN Standalone Mode of Operation

1.4.1 EMS-μLAN Components

1.4.1.1 Topology Browser

The EMS-μLAN Topology Browser provides a comprehensive view of the network

426006-2406-033-A00 ECI Telecom Ltd. Proprietary 1-5

1.4.1.2 Trail Manager

1.4.1.2.1 Graphical representation of trails

1.4.1.2.2 Illustration of SDH resource availability

1.4.1.2.3 Trail building

1.4.1.3 Card View

1-6 ECI Telecom Ltd. Proprietary 426006-2406-033-A00

!" Configuring the timing source

NOTE: The Card View can also be activated from the

1.4.1.4 Alarm and PM Viewer

1.4.1.5 Network Resolution Tool

426006-2406-033-A00 ECI Telecom Ltd. Proprietary 1-7

1.4.1.6 Windows services

1.5 EMS-μLAN Integrated Mode of Operation

NOTE: Unless otherwise specified, the instructions in this

1-8 ECI Telecom Ltd. Proprietary 426006-2406-033-A00

Figure 1-2: eNM LightSoft window

426006-2406-033-A00 ECI Telecom Ltd. Proprietary 1-9

Figure 1-3: eNM window

1.5.1 Working with eNM

Figure 1-4: Creating a Slave Manager using eNM

1-10 ECI Telecom Ltd. Proprietary 426006-2406-033-A00

Figure 1-5: Creating a new EME using eNM