Ems-xdm Um Etsi a00 8.1.2 En

(1)

EMS-XDM

®

Version 8.1.2

Element Management System

for XDM Platforms

User Manual

432006-2444-0H3-A00

(2)

February 2010 1st Edition

This is a legal agreement between you, the end user, and ECI Telecom Ltd. (“ECI Telecom”). BY OPENING THE DOCUMENTATION AND/OR DISK PACKAGE, YOU ARE AGREEING TO BE BOUND BY THE TERMS OF THIS AGREEMENT. IF YOU DO NOT AGREE TO THE TERMS OF THIS AGREEMENT, PROMPTLY RETURN THE UNOPENED DOCUMENTATION AND/OR DISK PACKAGE AND THE ACCOMPANYING ITEMS (INCLUDING WRITTEN MATERIALS AND BINDERS OR OTHER CONTAINERS), TO THE PLACE FROM WHICH YOU OBTAINED THEM.

The information contained in the documentation and/or disk is proprietary and is subject to all relevant copyright, patent, and other laws protecting intellectual property, as well as any specific agreement protecting ECI Telecom's rights in the aforesaid information. Neither this document nor the information contained in the documentation and/or disk may be published, reproduced, or disclosed to third parties, in whole or in part, without the express prior written permission of ECI Telecom. In addition, any use of this document, the documentation and/or the disk, or the information contained therein for any purposes other than those for which it was disclosed, is strictly forbidden. ECI Telecom reserves the right, without prior notice or liability, to make changes in equipment design or specifications. Information supplied by ECI Telecom is believed to be accurate and reliable. However, no responsibility whatsoever is assumed by ECI Telecom for the use thereof, nor for the rights of third parties, which may be affected in any way by the use and/or dissemination thereof.

Any representation(s) in the documentation and/or disk concerning performance of ECI Telecom product(s) are for informational purposes only and are not warranties of product performance or otherwise, either express or implied. ECI Telecom's standard limited warranty, stated in its sales contract or order confirmation form, is the only warranty offered by ECI Telecom.

The documentation and/or disk is provided “AS IS” and may contain flaws, omissions, or typesetting errors. No warranty is granted nor liability assumed in relation thereto, unless specifically undertaken in ECI Telecom's sales contract or order confirmation. Information contained in the documentation and in the disk is periodically updated, and changes will be incorporated in subsequent editions. If you have encountered an error, please notify ECI Telecom. All specifications are subject to change without prior notice.

The documentation and/or disk and all information contained therein is owned by ECI Telecom and is protected by all relevant copyright, patent, and other applicable laws and international treaty provisions. Therefore, you must treat the information contained in the documentation and disk as any other copyrighted material (for example, a book or musical recording).

Other Restrictions. You may not rent, lease, sell, or otherwise dispose of the documentation and disk, as applicable. YOU MAY NOT USE, COPY, MODIFY, OR TRANSFER THE DOCUMENTATION AND/OR DISK OR ANY COPY IN WHOLE OR PART, EXCEPT AS EXPRESSLY PROVIDED IN THIS LICENSE. ALL RIGHTS NOT EXPRESSLY GRANTED ARE RESERVED BY ECI TELECOM.

All trademarks mentioned herein are the property of their respective holders.

ECI Telecom shall not be liable to you or to any other party for any loss or damage whatsoever or howsoever caused, arising directly or indirectly in connection with this documentation and/or disk, the information contained therein, its use, or otherwise. Notwithstanding the generality of the aforementioned, you expressly waive any claim and/or demand regarding liability for indirect, special, incidental, or consequential loss or damage which may arise in respect of the documentation and/or disk and/or the information contained therein, howsoever caused, even if advised of the possibility of such damages.

The end user hereby undertakes and acknowledges that they read the "Before You Start/Safety Guidelines" instructions and that such instructions were understood by them.

(3)

About This Manual ... xi

Overview ... xi

Intended Audience ... xii

Document Contents ... xii

Related Publications ... xiv

Document Conventions ... xiv

Obtaining Technical Documentation ... xv

Technical Assistance ... xvi

Creating and Managing NEs ... 1-1

Overview ... 1-1 Creating NEs ... 1-2 Uploading NE Data ... 1-4 Viewing and Modifying NE Data ... 1-5 Propagating Object Attributes ... 1-12 Setting NE IP Routing ... 1-13 Setting NE Time ... 1-38 Pinging ETY Communications ... 1-39 Setting NE Passwords ... 1-39 Uploading NE Configuration Data ... 1-40 Managing NE Inventory ... 1-42 Configuring GNE Redundancy ... 1-46 Deleting NEs ... 1-49

Working with NE Cards and Modules ... 2-1

XDM Cards and Modules ... 2-1 Assigning Cards to Slots ... 2-2 Topology Link Discovery ... 2-15 RED Curves ... 2-32 Viewing and Modifying Card Information ... 2-36 Configuring Timing Sources ... 2-40

Configuring Common Cards ... 3-1

Overview ... 3-1 HLXC/MXC/xMCP Cards ... 3-2 XIO Card Internals ... 3-6 MECP Card Internals ... 3-11

(4)

Configuring Data Cards ... 4-1

Overview ... 4-1 PIO/PIM/PDB Card Internals ... 4-2 SIO/SIM Card Internals ... 4-4 MCS Card Internals ... 4-14 EIS/EISM Card Internals ... 4-88 EISMB Card Internals ... 4-97 DIO Card Internals ... 4-101 ATS Card Internals ... 4-104

Configuring Optical Cards and Modules ... 5-1

Overview ... 5-1 Optical Card and Module Naming Conventions ... 5-2 40/80 Channel Systems ... 5-3 Power Control Configuration ... 5-3 Optical Transponders and Combiners ... 5-8 Optical Amplifiers ... 5-45 Mux/DeMux Components ... 5-46 OADM/ROADMs ... 5-58 OFA Cards (OFA-2, OFA_M, and OFA-R) ... 5-76 OPM Card Internals ... 5-84 OMSP Card Internals ... 5-86 Optical Accessories and Auxiliary Components ... 5-88 DCM Card Information ... 5-92 Auxiliary Card Internals ... 5-93

Configuring Specialized Cards and Internal Objects ... 6-1

Overview ... 6-1 Configuring ASON ACP Cards ... 6-2 AURORA-G Encryption Card ... 6-23 Card and Internal XDM Objects Configuration ... 6-25

Optical Management ... 7-1

Overview ... 7-1 Introduction to Functional Nodes (FuN) ... 7-2 Enhanced Automatic Power Control (PELES) ... 7-17

Setting Up Cross Connects ... 8-1

Overview ... 8-1 High-order and Low-order XCs ... 8-2 Workflow ... 8-3 Planning and Building XCs at the Network Level ... 8-4

(5)

Creating LOVC XCs ... 8-22 Creating Data XCs ... 8-28 Creating Concatenated XCs ... 8-53 Creating External DCC XCs ... 8-53 Creating OW XCs ... 8-59 Creating AoC XCs ... 8-65 Activating XCs ... 8-66 Filtering XCSs ... 8-67 Configuring XCs ... 8-68 Deleting XCs ... 8-70 Using the XC Set List ... 8-71 Exporting and Importing XC Files ... 8-76

Protection ... 9-1

Overview ... 9-1 IO Protection ... 9-2 MSP Linear Protection ... 9-13 TRP/CMBR Protection ... 9-18 RSTP Protection ... 9-19 LCAS Protection ... 9-23 MS Shared Protection Ring ... 9-25 ALS Mode Setting for TRP10_2O, TRP25, and OFA Cards ... 9-43 ASON Protection and Restoration ... 9-43 MPLS Protection ... 9-45 Dual-Homed Protection ... 9-48 Link Aggregation ... 9-48

Fault Management ... 10-1

Workflow ... 10-1 Configuring Fault Management ... 10-2 Managing Alarms ... 10-12 Audible Alarms ... 10-18 Using the Alarm Log ... 10-21

Troubleshooting Alarms ... 11-1

Overview ... 11-1 Alarm Resolution Workflow ... 11-3 Alarm Interactions ... 11-4 Transmission Alarms ... 11-5 Service Alarms ... 11-43 Timing Alarms ... 11-45 Equipment Alarms ... 11-48 ATS Alarms ... 11-66 EMS-XDM-specific Alarms ... 11-67 Checking Optical Parameters ... 11-69 Card Objects, Alarms, and Maintenance Operations ... 11-70

(6)

Performance Monitoring ... 12-1

Overview ... 12-1 Workflow ... 12-2 PM Management ... 12-3 Viewing and Modifying PM Collection Groups ... 12-4 Enabling Large PM Automatic Data Collection ... 12-7 Collecting PM Data Manually ... 12-9 Viewing and Modifying PM Profiles ... 12-9 Viewing Current Performance ... 12-13 Viewing Performance History ... 12-14 Resetting PM Counters ... 12-17 Viewing Optical Levels and Parameters of Optical Objects ... 12-19 Viewing PM, MS, and Optics Logs ... 12-20 Viewing PM History Reports for OPS-M Objects ... 12-22

Performing Maintenance Operations ... 13-1

Overview ... 13-1 Performing Card Maintenance ... 13-2 xMCP/MXC Synchronization ... 13-3 MSP Maintenance Operations ... 13-4 MS-SPRing Maintenance Operations ... 13-5 Performing Transmission Object Maintenance ... 13-6 Performing Maintenance on Timing/TMU Objects ... 13-16

Index ... I-1

(7)

List of Figures

Figure 1-1: Viewing NE inventory through the EMS-XDM ... 1-42

Figure 2-1: Topology link Info window displaying ASON status ... 2-21

Figure 2-2: TE Links window ... 2-23

Figure 2-3: Data Links List window ... 2-24

Figure 2-4: ASON Control Channels List window ... 2-25

Figure 2-5: Info Control Channel Info window ... 2-27

Figure 2-6: Info window displaying LDL status ... 2-28

Figure 2-7: TST Info window ... 2-31

Figure 4-1: CFM configuration ... 4-51

Figure 4-2: Remote MEP Configuration ... 4-52

Figure 4-3: Loopback and link trace testing ... 4-53

Figure 5-1: TRP10_4CL card internals ... 5-15

Figure 5-2: TRP10_4CL Card Setup window ... 5-16

Figure 5-3: Channel Power Configuration window ... 5-51

Figure 5-4: ROADM8A XC Configuration ... 5-72

Figure 5-5: ROADM8A Card Internals displaying XCs ... 5-72

Figure 5-6: ROADM8A maintenance mode ... 5-74

Figure 6-1: EMS Preference window ... 6-6

Figure 6-2: NE Info window ... 6-9

Figure 6-3: Slot Assignment window ... 6-11

Figure 6-4: Info window displaying the Configuration tab ... 6-12

Figure 6-5: Info window displaying the Configuration tab ... 6-14

Figure 6-6: Add New Route window ... 6-15

Figure 6-7: Info window displaying the Protocols tab ... 6-17

Figure 6-8: Severity Assignment window ... 6-19

Figure 6-9: Slot window ... 6-21

Figure 9-1: MS-SPRing Squelch ... 9-33

Figure 9-2: MS-SPRing Squelch (2) ... 9-33

Figure 10-1: Defining Alarm Severity profiles ... 10-4

(8)

(9)

List of Tables

Table 1-1: NE Info window - Status tab fields ... 1-6

Table 1-2: NE Info window - Configuration tab fields ... 1-7

Table 1-3: NE Info window - Configuration tab fields ... 1-9

Table 1-4: NE Info window - Inventory tab ... 1-11

Table 1-5: IP address classes ... 1-15

Table 1-6: Subnet Mask Example 1 ... 1-16

Table 1-7: Subnet mask for example 2 ... 1-16

Table 1-8: Routing window fields - Actual Routes tab ... 1-18

Table 1-9: Overall OSPF Tab Parameters ... 1-24

Table 1-10: Network Interface - Attributes tab ... 1-32

Table 1-11: Network Interface - Advanced tab ... 1-33

Table 1-12: Inventory window fields ... 1-43

Table 1-13: NE State window fields ... 1-44

Table 1-14: Routing Table Columns ... 1-48

Table 1-15: Timing Configuration window fields ... 1-53

Table 2-1: Topology Links window fields ... 2-19

Table 2-2: TE Links window fields ... 2-24

Table 2-3: Control Channels list fields ... 2-26

Table 2-4: Default RED settings - EoS ports ... 2-32

Table 2-5: RED Curve table fields ... 2-35

Table 2-6: Typical card configuration parameters ... 2-36

Table 2-7: Typical card status parameters ... 2-37

Table 2-8: Typical card inventory parameters ... 2-38

Table 3-1: MXC cards on XDM-50/100/200/300 shelves ... 3-4

Table 3-2: MXC cards on XDM-50/100/200/300 shelves ... 3-4

Table 3-3: SAM Modules on XDM-100 shelves ... 3-5

Table 3-4: XIO cards and modules on XDM-400/500/1000/2000 shelves ... 3-8

Table 3-5: MECP cards and modules on XDM-40/500/1000/2000 shelves ... 3-11

Table 4-1: PIO cards and modules on XDM-400/500/1000 shelves ... 4-2

Table 4-2: PIM/PDB cards and modules on XDM-300 shelves ... 4-3

Table 4-3: SIO cards and modules on XDM-400/500/1000/2000 shelves ... 4-7

Table 4-4: SIO cards and modules on XDM-300 shelves ... 4-9

Table 4-5: MCS5/MCS10 cards and modules on XDM-500/1000/2000 shelves ... 4-15

Table 4-6: MCSM cards and modules on XDM-300 shelves ... 4-15

Table 4-7: General tab - EoS/MoT fields ... 4-17

(10)

Table 4-9: Switch Configuration - General tab fields ... 4-26

Table 4-10: Switch Configuration - WRED tab fields ... 4-27

Table 4-11: Configuration - RSTP tab fields ... 4-29

Table 4-12: Switch Status - RSTP tab fields ... 4-32

Table 4-13: Switch Status - Bridge tab fields ... 4-33

Table 4-14: Switch Status - FBD tab fields ... 4-34

Table 4-15: Switch VSI Connections tab ... 4-36

Table 4-16: Switch Maintenance/FDB tab fields ... 4-63

Table 4-17: MPLS XC Connections tab ... 4-80

Table 4-18: EIS cards and modules on XDM-400/500/1000/2000 shelves ... 4-89

Table 4-19: EISM/MB cards on XDM-50/100/100U/100H/100UH shelves ... 4-99

Table 4-20: EISM/MB cards on XDM-50/100/100U/100H/100UH shelves ... 4-99

Table 4-21: DIO/DIOB cards and modules on XDM-400/500/1000/ 2000 shelves ... 4-103

Table 4-22: DIOM cards and modules on XDM-300 shelves ... 4-104

Table 4-23: ATS cards and modules on XDM-40/400/500/1000/2000 shelves ... 4-105

Table 5-1: TRP and CMTR25 cards and modules on XDM-40/500/1000/2000

shelves ... 5-9

Table 5-2: TRP cards and modules on XDM-100H/100UH/200/300 shelves ... 5-11

Table 5-3: TRP40_2 Slot Assignment Options ... 5-12

Table 5-4: TRP10_4 modules ... 5-14

Table 5-5: TRP card optical channel configuration ... 5-19

Table 5-6: Bitrate values - TRP25_2DSR card optical channels ... 5-20

Table 5-7: Application code settings for optical modules ... 5-21

Table 5-8: OMTx10_LAN Info window - Configuration parameters ... 5-26

Table 5-9: OMTx10_LAN Info window - Status tab fields ... 5-28

Table 5-10: PCS Info window - Configuration tab ... 5-29

Table 5-11: PCS Info window - Status tab ... 5-30

Table 5-12: CMTR25 cards and modules on XDM-40/500/1000/2000 shelves ... 5-32

Table 5-13: Combiner cards and modules on XDM-40/500/1000/ 2000 shelves ... 5-36

Table 5-14: Combiner cards and modules on XDM-100/100U/100H/

100UH/200/300 shelves ... 5-38

Table 5-15: AoC cards and modules on XDM-40/500/1000/ 2000 shelves ... 5-42

Table 5-16: Optical amplifiers on XDM-40/400/500/1000 shelves ... 5-45

Table 5-17: Passive Mux/DeMux modules on XDM-1000 shelves ... 5-47

Table 5-18: Smart Mux/DeMux modules on XDM-1000/2000 shelves ... 5-48

Table 5-19: VMUX/DeMux modules on XDM-40/400/500/1000 shelves ... 5-49

(11)

Table 5-24: Tracking alarms ... 5-55

Table 5-25: C/DWDM modules on XDM-40/400/500/1000 shelves ... 5-57

Table 5-26: C/DWDM modules on XDM-100H/100UH/200/300 shelves ... 5-57

Table 5-27: OADM cards and modules on XDM-500/1000/2000 shelves ... 5-60

Table 5-28: MO_OADM cards and modules on XDM-500/1000/2000 shelves ... 5-61

Table 5-29: MO_COADM cards and modules on XDM-100H/100UH/ 200/300

shelves ... 5-62

Table 5-30: Alarms on the power control object ... 5-63

Table 5-31: MO_ROADM cards and modules on XDM-40/500/1000 shelves ... 5-66

Table 5-32: Channel XC window parameters ... 5-68

Table 5-33: OFA_M and OFA-2 Tracking Off ... 5-76

Table 5-34: OFA_M and OFA-2 Tracking On ... 5-77

Table 5-35: OFA_M and OFA-2 Alarms ... 5-77

Table 5-36: OFA modules on XDM-40/400/500/1000 shelves ... 5-78

Table 5-37: OM_OFA_R FWD/BWD configuration parameters ... 5-81

Table 5-38: OM_OFA_R FWD/BWD status parameters ... 5-82

Table 5-39: OPM card and modules on XDM-40/400/500/ 1000/2000 shelves ... 5-85

Table 5-40: OMSP cards and modules on XDM-500/1000/2000 shelves ... 5-87

Table 5-41: Splitter/Couplers on XDM-40/400/500/1000 shelves ... 5-89

Table 5-42: Splitter/Couplers on XDM-100H/UH/200/300 shelves ... 5-91

Table 5-43: DCM cards and modules on XDM-500/1000 shelves... 5-93

Table 5-44: AUX cards and modules on XDM-40/400/500/1000/ 2000 shelves ... 5-94

Table 6-1: Requirements for connecting ACP to MECP cards ... 6-8

Table 6-2: AURORA-G card on XDM-40/400/500/1000/2000 shelves ... 6-23

Table 6-3: GEoS Source Object Status parameters ... 6-31

Table 6-4: GEoS Sink Object Configuration parameters ... 6-32

Table 6-5: GEoS Sink Object Status parameters ... 6-33

Table 6-6: List of fixed XCs AU-4 - VC-4 in DIO1_31 ... 6-36

Table 7-1: Chain List window fields ... 7-22

Table 7-2: Span List window fields ... 7-22

Table 8-1: Transmission objects functionality ... 8-3

Table 8-2: Color-coded legend in Edit View ... 8-27

Table 8-3: Policer List table fields ... 8-34

Table 8-4: Flow List table fields ... 8-41

Table 8-5: FDB Table window fields ... 8-45

Table 8-6: XC Set Filter table fields ... 8-67

Table 8-7: XCS Configuration window and table fields ... 8-68

Table 8-8: XC Set List table fields ... 8-71

(12)

Table 9-1: XDM-300 IO Protection Schemes ... 9-10 Table 9-2: XDM-300 1:1 IO Protection ... 9-11 Table 9-3: XDM-300 1:2 IO Protection ... 9-11 Table 9-4: XDM-100 1:3 IO Protection ... 9-11 Table 9-5: XDM-50 1:1 IO protection ... 9-12 Table 9-6: XDM-50 1:2 IO protection ... 9-12 Table 9-7: XDM-50 1:3 IO protection ... 9-12

Table 9-8: Protection Info window fields ... 9-16

Table 9-9: RSTP Configuration window fields ... 9-21

Table 9-10: Protection group parameters ... 9-27

Table 9-11: Info for Ring window fields ... 9-29

Table 9-12: Additional Info window fields ... 9-30

Table 10-1: Current alarm filtering options ... 10-16

Table 10-2: Alarm log menu bar options ... 10-21

Table 10-3: Log filtering options ... 10-25

Table 11-1: EMS-XDM Internal Alarms ... 11-67

Table 12-1: Performance Charts window buttons ... 12-15

Table 12-2: Optical Parameters window fields ... 12-19

Table 12-3: PM Log filtering options ... 12-21

Table 12-4: OPM Current/History window fields ... 12-23

(13)

In this chapter:

Overview ... xi

Intended Audience ... xii

Document Contents ... xii

Related Publications ... xiv

Document Conventions ... xiv

Obtaining Technical Documentation ... xv

Technical Assistance ... xvi

Overview

The EMS-XDM User Manual provides information required to perform all major actions that can be performed by the EMS-XDM®_{(XDM Element}

Management System) software application, used by telecommunications service personnel to manage ECI Telecom XDM equipment. It includes information about creating and managing NEs, card and module configuration, optical management, creating and managing cross connects, protection, monitoring, and maintenance.

For application administration, and basic application information, such as how to log in and how to understand the EMS-XDMGUI, see the EMS-XDM Getting Started & Administration Guide.

(14)

Intended Audience

This guide is for the following users who have rights to use the EMS-XDM application to remotely manage XDM network elements (NEs):

| Network Management System (NMS) users: For these users, EMS-XDM

is integrated under another management application (such as LightSoft), from which EMS-XDM functionality is accessed. For NMS users, some of the steps and activities discussed in this guide may not be relevant and can be bypassed, as access to the described functionality is provided from the higher-level management application.

| Element Management System (EMS) users: These users access

EMS-XDM functionality directly from the EMS-EMS-XDM application. In this case, EMS-XDM is not integrated under another higher-level management application.

Document Contents

This manual contains the following chapters and appendices:

| Chapter 1: Creating and Managing NEs (on page 1-1) discusses how to

create and manage XDM NEs, configure cards and internal XDM objects, and configure XDM NE timing sources using the EMS-XDM Shelf View and Card Internals View.

| Chapter 2: Working with NE Cards and Modules (on page 2-1) discusses

how to assign cards to slots, perform topology link discovery, RED curves, view and modify card information, and configure timing sources.

| Chapter 3: Configuring Common Cards (on page 3-1) discusses how to

configure common cards such as HLXC, XIO, and MECP cards.

| Chapter 4: Configuring Data Cards (on page 4-1) discusses how to

configure data cards, including PIO, PIM, PDB, SIO, SIM, MCS, EIS, DIO, and ATS cards.

| Chapter 5: Configuring Optical Cards and Modules (on page 5-1)

discusses how to configure optical components.

| Chapter 6: Configuring Specialized Cards and Internal Objects (on

page 6-1) discusses how to configure ASON ACP cards, AURORA-G encryption cards, and view and configure internal objects.

| Chapter 7: Optical Management (on page 7-1) discusses how to manage

XDM optical sites using the functional node (FuN) utility and Enhanced Automatic Power Control (Enhanced APC) feature also known as Power Equalization of Optical Links (PELES).

(15)

| Chapter 9: Protection (on page 9-1) discusses how to configure protection

schemes for XDM NEs.

| Chapter 10: Fault Management (on page 10-1) discusses how to

configure, manage, filter, and troubleshoot XDM NE alarms.

| Chapter 11: Troubleshooting Alarms (on page 11-1) lists alarms by

category, including methods for troubleshooting the cause of an alarm.

| Chapter 12: Performance Monitoring (on page 12-1) discusses how to

analyze the current and historical performance of networks and XCs in EMS-XDM.

| Chapter 13: Performing Maintenance Operations (on page 13-1)

discusses how to perform routine maintenance operations on XDM cards and internal objects.

The Supporting Information Manual contains the following reference information:

| Chapter 1: Slot and Module Assignment Limitations provides details of

the slot and module assignment limitations for all XDM shelves.

| Chapter 2: Upgrading NE Software provides instructions for

administrators to upgrade XDM NE software.

| Chapter 3: Default Alarm Severities lists the default alarm severities for

each type of alarm.

| Chapter4: Alarm Correlation Tables shows the relationship between

active and suppressed alarms

| Chapter 5: Exporting Alarms via FTP discusses the EMS-XDM alarm

export via FTP functionality, which enables customer applications to receive XDM alarms.

| Chapter 6: XDM Internal Object Attributes provides a list of general

attributes displayed for most internal XDM objects, and specific attributes by object type.

| Chapter 7: BIT Codes tables.

| Chapter 8: Creating XML Files for Import into EMS-XDM describes

how to create XML files offline, and provides examples.

| Chapter 9: PM Counters Reference Information provides information

about the available performance monitoring counters and default thresholds.

(16)

Related Publications

This manual is part of the EMS-XDM information suite. The suite comprises the following:

| EMS-XDM Getting Started and Administration Guide: general

information about how to access EMS-XDM, introduction to the GUI main windows and common functions, and security administration.

| EMS-XDM User Manual: guide to all major and specialist management

functions for the Element Management System, including creating and managing NEs, configuring cards, creating cross connects, protection, troubleshooting, monitoring, and maintenance.

| EMS-XDM Supporting Information: Reference and supporting

information for the EMS-XDM User Manual, includes Slot and Module Assignment limitations, Object attribute values, BIT code values, how to create XML files, and PM Counter reference information.

The EMS-XDM information suite should also be used in conjunction with the XDM Installation, Operation, and Maintenance Manual, and the LightSoft User Manual.

Document Conventions

When applicable, this manual uses the following conventions.

Convention Indicates Example

Bold Names of windows, dialog boxes, menus, buttons and most other GUI elements

In the Alarms menu...

Menu > Option Selection from a menu, or leading to another command

Select Update > View

Objects

Italics New terms and emphasized

text Examples in text

Borders around text Notes, cautions, and

warnings See examples below Note: Text set off in this manner presents clarifying

information, specific instructions, commentary, sidelights, or interesting points of information.

(17)

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

LASER WARNING: Text set off in this manner indicates how to avoid personal injury. All personnel involved in equipment installation, operation, and maintenance must be aware that laser radiation is invisible. Therefore, although protective devices generally prevent direct exposure to the beam, personnel must strictly observe the applicable safety precautions and, in particular, must avoid staring into optical connectors, either directly or using optical instruments.

ESD: Text set off in this manner indicates information on how to avoid discharge of static electricity and subsequent damage to the unit.

TIP: Text set off in this manner includes helpful information and handy hints that can make your task easier.

IMPORTANT: Text set off in this manner presents essential information to which you must pay attention.

Obtaining Technical

Documentation

To obtain technical documentation related to ECI Telecom products, please contact: ECI Telecom Ltd. Documentation Department 30 Hasivim St. Petach Tikva 49130 Israel Fax: +972-3-9268060 Email: [email protected]

(18)

Technical Assistance

The configuration, installation, and operation of the XDM and its operation in a network are highly specialized processes. Due to the different nature of each installation, some planning aspects may not be covered in this manual. If you have questions or concerns about your network design or if you require installation personnel to perform the actual installation process, ECI Telecom maintains a staff of design engineers and highly trained field service personnel. The services of this group are available to customers at any time.

If you are interested in obtaining design assistance or a network installation plan from ECI Telecom's Customer Support team, contact your ECI Telecom sales representative. With any support related issues, technical or logistic, please contact the ECI Telecom Customer Support center at your location. If you are not familiar with that location, please contact our central customer support center action line at:

Telephone +972-3-9266000 Telefax +972-3-9266370

Email [email protected]

ECI Telecom's XDM®_{and BroadGate}®_{product lines are}

(19)

In this chapter:

Overview ... 1-1 Creating NEs ... 1-2 Uploading NE Data ... 1-4 Viewing and Modifying NE Data ... 1-5 Propagating Object Attributes ... 1-12 Setting NE IP Routing ... 1-13 Setting NE Time ... 1-38 Pinging ETY Communications ... 1-39 Setting NE Passwords ... 1-39 Uploading NE Configuration Data ... 1-40 Managing NE Inventory ... 1-42 Configuring GNE Redundancy ... 1-46 Deleting NEs ... 1-49

Overview

This section describes how to use EMS-XDM to configure and manage XDM NEs via the EMS-XDM Shelf View. The Shelf View is the starting point for many NE management operations, including:

| Creating NEs (on page 1-2) | Uploading NE Data (on page 1-4)

| Viewing and Modifying NE Data (on page 1-5) | Setting NE IP Routing (on page 1-13)

| Setting NE Time (on page 1-38)

1

(20)

Creating NEs

EMS-XDM allows you to add new NEs to the database. You can add one or multiple NEs concurrently.

Whenever you create an NE, an NE icon appears in the EMS-XDM main window. You can freely move NE icons to any location in the main window by dragging and dropping.

| Creating a Single NE (on page 1-2)

| Creating Multiple NEs Using NE Discovery (on page 1-3)

NOTE: You can only create as many NEs as allowed by your system license limit. If you exceed that number, a warning message appears.

Creating a Single NE

EMS-XDM allows you to create NEs on a one-to-one basis. To create a single NE:

1. In the EMS-XDM main window, select Configuration > Element > Create. The Create window opens.

2. In the Communication Port field, type the NE IP address. If you enter an incorrect IP address, you must delete the NE and create it again.

3. In the DCC Subnet field, type a three-digit number to specify the DCC channel to be used for uploading the data from the NE to the EMS-XDM database. An unlimited number of DCC subnets can be defined. All NEs assigned the same DCC subnet number are treated as if they are on the same subnet and receive the same management data. Up to three upload sessions can be established concurrently per DCC subnet.

4. Click OK. An NE outline displaying a hand icon appears.

(21)

Creating Multiple NEs Using NE Discovery

To expedite the NE creation process, you can concurrently create multiple NEs by specifying the IP address range to be searched during the NE discovery process.

You can also decide to exclude selected IP address ranges from the NE

discovery process. This is advantageous when working with networks managed by more than one EMS, or when IP address ranges in the network are not continuous.

To create multiple NEs using NE discovery:

1. In the Shelf View or EMS-XDM main window, select Configuration > NE Discovery. The NE Discovery window opens.

2. To specify the range of NE IP addresses to search, do the following: a. In the Start IP field, type the IP address of the first NE.

b. In the End IP field, type the IP address of the last NE.

For example, specify a Start IP of 192.9.116.0 and an End IP of 117.0 to create NEs with IP addresses in the range of 192.9.116.0 to

192.9.117.0.

3. To exclude a specific IP address range, repeat Steps 1 and 2, and then click Exclude. The IP address range appears in the Exclude IP List area. Repeat Steps 1 through 3 to specify all IP address ranges you want to omit. If you decide not to exclude a designated IP address range, you can delete it from the Exclude IP List area by selecting it and clicking Remove.

4. Select the Record Route IPv4 checkbox to facilitate NE discovery of remote NEs. NE discovery uses a ping operation to locate remote NEs and verifies that they are actual XDM shelves. Note that the ping process takes longer when the Record Route IPv4 option is enabled.

5. In the Timeout field, use the scroll arrows to specify the maximum time for an NE to respond to the ping.

(22)

6. Click OK to begin the NE discovery process. The EMS-XDM starts pinging for IP addresses in the specified range. As it searches IP addresses, it creates an NE and uploads the NE data.

A message window opens, displaying the total number of NEs found. Click Close to close the window.

The NE creation process creates an icon for each NE and places it on the EMS-XDM desktop. If the EMS-XDM is integrated under an upper-level management system, you may need to manually create the discovered NEs there. You can, however, view the results of the NE discovery operation by opening the Inventory window.

Uploading NE Data

Initially, after NE creation, the NE status LED in the main window is gray (that is, no communication). After a few moments, it turns blue, indicating that NE data is being uploaded to the EMS-XDM database.

The data is uploaded in the following stages:

| Core upload: data to begin configuration of the NE including alarm and

PM severity profiles. When this data is uploaded to the EMS-XDM database, the NE LED color changes to indicate the current alarm state.

| NE cross connects: data relevant to the NE's XCs.

| Background upload: slot assignment and payload internals data uploaded

by the operator, as required. When this upload process is in progress, system operation can be slower than normal, and the system initiates a start and stop of the background upload, as required.

NOTE: Only one NE per subnet can perform a background upload at one time. A conflict occurs when multiple NEs have the same NE ID and are involved in concurrent upload processes.

To manually start/stop the background upload process: 1. To manually stop any background uploads in progress, in the Shelf View,

select System > Background Upload > Stop. It is recommended that you use this command when performing lengthy operations (for example, creating multiple XCs), as system operation can be considerably slower when the background upload process is in progress. When the background upload is stopped manually, all background upload operations in process are terminated, and no new background uploads are initiated.

(23)

Viewing and Modifying NE Data

In the EMS-XDM Info window, you can view and modify NE parameters.

Viewing NE Status

To view current NE status information: 1. In the Shelf View window, do one of the following:

Select File > NE Info. OR

In the EMS-XDM main window, select the NE, and select Configuration > Element > Info.

The Info window opens, displaying the Status tab, where you can view current NE status parameters.

(24)

2. View the fields as described in the following table. Table 1-1: NE Info window - Status tab fields

Field Description

Upload State Specifies whether management is uploading configuration. (Read only)

NE Install State NE installation state, Enabled or Disabled. (Read only) LCT Connection State Information regarding LCT-XDM connection to XDMNE.

Options:

| Not Connected: no LCT-XDM connected to NE | Connected Remote: LCT-XDM connected via

Ethernet

| Connected SLIP: LCT-XDM connected via SLIP

(Serial Line Internet Protocol) (Read only)

Power Dissipation

Limit Power dissipation limit. Options: | Enabled: Power dissipation values are calculated, and

system does not allow assignment of cards in NE, if power limit is surpassed.

| Disabled: System does not enforce power limit. (Read

only) Max Power

Dissipation (watts)

Maximum power dissipation setting made internally and cannot be adjusted by user. (Read only)

Total Power

Consumption (watts) Actual power dissipation of sum of power consumption of all cards in NE. (Read only) Operational State Operational state. Options:

| Enabled: operating properly.

| Disabled: not operating due to, for example, card reset

or power supply failure on card. (Read only) Number of

MS-SPRing Number of MS-SPRing. (Read only)

Group A DCC XC (Relevant only for NEs with xMCPB) Number of XCs assigned to card per DCC group. (Read only)

Group B DCC XC (Relevant only for NEs with xMCPB) Number of XCs assigned to card per DCC group. (Read only)

(25)

Modifying NE Configuration

To view and modify NE configuration parameters:

1. In the NE Info window, click the Configuration tab. The Configuration tab opens, displaying editable fields in the Attribute New Value column. 2. To edit a text field, click the relevant field to enable it for typing and type

the relevant text.

3. To edit a field marked by a dropdown arrow, click the arrow and choose an option from the dropdown list. The modified fields and the Configuration tab label are colored blue, indicating changes have been made. The blue coloring remains until you apply the changes (see Step 4) or you choose the original value again.

4. Fill in the fields, as described in the following table.

5. To save the changes click to apply the changes. The changes are applied and the Configuration tab label and fields revert to the default coloring.

If you attempt to close the Info window (after making changes, but without applying the changes), a reminder/confirmation window opens prompting you to confirm closing the window. Click Yes to confirm.

Table 1-2: NE Info window - Configuration tab fields Field Description

NE Type NE type. (Read only) MBP Type MBP type. (Read only) Network Element

ID NE ID determined during NE installation. (Read only) System Title NE descriptive title determined during NE installation. System Location User-assigned location name of the NE.

Main IP Address IP address of NE, assigned during installation. Main Subnet

Mask

IP address by which subnet can be divided into several subnets, with few hosts per subnet.

Gateway Address IP address for NE that is a gateway. Gateway Subnet

Mask Determines number of bits used for subnet and host portions of an address. TTL DCC

(10-255) DCC Time To Live (TTL) parameter. Determines the number of NEs the DCC packets that can pass through. After passing through a specific number, DCC packet transmission is

terminated. (Read only; fixed value of 40.) DCC Subnet

(26)

Matrix

Configuration Code that reflects maximum number of SIO/SIM cards that can be assigned to NE shelf. Number of SIO/SIM cards that can be installed in XDM shelf is limited by license purchased by customer.

(Read only) Fault Time

450-10K msec Interval of time in milliseconds of an alarm. Holdoff Time

(0-10,000 msec) Amount of time in milliseconds between deciding to switch to protection and actually performing switch. Switch is not performed if need for switch does not persist for entire holdoff time. Default value is 0. (Read only)

Clear Time 10K-60K ms

Interval of time in milliseconds a fault must be clear to trigger a clear alarm for that NE.

SNCP Mode Whether revertive SNCP mode is enabled or disabled. SNCP WTR (min) Revertive SNCP wait to restore interval.

NE TIM

Detection J0 NE TIM alarm detection. Indicates trace identifier mismatch caused by incorrect provisioning of expected trace or misconnection. Results from comparing expected J0 byte to received one.

NE TIM

Comment Comments, entered by XDM user. LCT-XDM

Approval

Presets Handshake request status, which determines whether to grant NE configuration rights to LCT-XDM stations. Options:

| Waiting for Approval: (default) when LCT-XDM station

requests configuration rights and EMS-XDM operator does not respond to request within predefined time period, Handshake request is granted. (Default)

| Approved: configuration rights are granted. Approved

value is good for only one LCT-XDM entry, after which it reverts to default "Waiting for Approval" state.

| Not Approved: configuration rights are rejected.

Hybrid Mode Whether XDM-1000 is configurable as a hybrid shelf. Options:

Enabled, Disabled.

SIM Allowed Whether SIM is Enabled or Disabled. (Relevant only for XDM-50)

(27)

Table 1-3: NE Info window - Configuration tab fields Field Description

NE Type NE type. (Read only) MBP Type MBP type. (Read only) Network Element

ID NE ID determined during NE installation. (Read only) System Title NE descriptive title determined during NE installation. System Location User-assigned location name of the NE.

Main IP Address IP address of NE, assigned during installation. Main Subnet

Mask IP address by which subnet can be divided into several subnets, with few hosts per subnet. Gateway Address IP address for NE that is a gateway.

Gateway Subnet

Mask Determines number of bits used for subnet and host portions of an address. TTL DCC

(10-255)

DCC Time To Live (TTL) parameter. Determines the number of NEs the DCC packets that can pass through. After passing through a specific number, DCC packet transmission is terminated. (Read only; fixed value of 40.)

DCC Subnet

(0-1000) DCC subnet address. Default value is 1. Matrix

Configuration Code that reflects maximum number of SIO/SIM cards that can be assigned to NE shelf. Number of SIO/SIM cards that can be installed in XDM shelf is limited by license purchased by customer.

(Read only) Fault Time

450-10K msec

Interval of time in milliseconds of an alarm. Holdoff Time

(0-10,000 msec) Amount of time in milliseconds between deciding to switch to protection and actually performing switch. Switch is not performed if need for switch does not persist for entire holdoff time. Default value is 0. (Read only)

Clear Time

10K-60K ms Interval of time in milliseconds a fault must be clear to trigger a clear alarm for that NE. SNCP Mode Whether revertive SNCP mode is enabled or disabled.

SNCP WTR (min) Revertive SNCP wait to restore interval. NE TIM

Detection J0

NE TIM alarm detection. Indicates trace identifier mismatch caused by incorrect provisioning of expected trace or misconnection. Results from comparing expected J0 byte to received one.

NE TIM

(28)

NE TIM

Comment Comments, entered by XDM user. LCT-XDM

Approval Presets Handshake request status, which determines whether to grant NE configuration rights to LCT-XDM stations. Options:

| Waiting for Approval: (default) when LCT-XDM station

requests configuration rights and EMS-XDM operator does not respond to request within predefined time period, Handshake request is granted. (Default)

| Approved: configuration rights are granted. Approved

value is good for only one LCT-XDM entry, after which it reverts to default "Waiting for Approval" state.

| Not Approved: configuration rights are rejected.

Hybrid Mode Whether XDM-100 is configurable as a hybrid shelf. Options:

Enabled, Disabled.

SIM Allowed Whether SIM is Enabled or Disabled. (Relevant only for XDM-50)

Propagating NE Info

To propagate NE info:

1. In the Configuration tab of the NE Info window, in the Propagation column, select the checkboxes adjacent to the relevant NE attributes to be propagated.

(29)

Viewing NE Inventory

To view NE inventory:

1. In the Configuration tab, in the Propagation column, select the checkboxes adjacent to the relevant NE attributes to be propagated. 2. In the NE Info window, click the Inventory tab to display read-only fields

described in the following table.

Table 1-4: NE Info window - Inventory tab Field Description

SW Version Software version number of XDM embedded software. Vendor Name of manufacturer of XDM.

HW Version Hardware version number of XDM. Serial Number Serial number of XDM.

(30)

Viewing NE Alarms

To view NE alarms:

1. In the Alarms area (top of Info window), view the Total and Unacknowledged alarms, color coded to reflect alarm severity.

2. To view visible alarms, click the Visible Alarms tab, where you can view the same alarms that appear in the Current Alarms list.

3. To view invisible alarms, click the Invisible tab, where you can view the alarms that appear in the Current Alarms list, with the addition of Invisible alarms (alarms assigned the non-report feature in the alarm severity profile).

Propagating Object Attributes

In the EMS-XDM Info window, you can automatically propagate configurable object attributes to other objects of the same object type (NE, network, or card). This feature saves valuable time when commissioning new NEs or cards. Propagated attributes include hold-off time, TTI, TSL, Automatic Laser Shutdown (ALS) state, duration, and so on.

To propagate object attributes:

1. In the Info window, in the Configuration tab, in the Propagation column, select the checkboxes adjacent to the relevant attributes to be propagated. 2. Select one of the following options:

Select Propagate > By Card to propagate object attributes to all identical objects on the card

Select Propagate > By NE to propagate object attributes to all identical objects on the NE

Select Propagate > By Network to propagate object attributes to all identical objects across all NEs in the network

A message window opens, confirming that the operation was successful. 3. Click Close to close the message window.

(31)

Setting NE IP Routing

This section discusses how to use EMS-XDM to set XDM NE IP routing. EMS-XDM uses TCP/IP communications to send datagrams (or data packets) to SDH NEs. The datagrams can be routed over separate LANs.

EMS-XDM supports user-defined IP routing, which defines how datagrams are routed between LANs. Datagram routing can also be defined using the Set Route utility (accessed via the CDE).

The NE routing table defines the destination subnets that an NE communicates with on the IP network. It allows system configurations where an NE is used to route datagrams to other LAN segments; this type of NE is referred to as a gateway.

All NEs have a default routing table with the destination (typically EMS-XDM) and the GNE used to route the datagrams.

NOTE: The following IP addresses are used by XDM NEs for internal purposes and cannot be used by any other entity, including XDM NEs, that are connected to the same IP network as the XDM NEs: 192.168.10.*, 192.168.11.*, 192.168.1.*, 192.9.90.*, 192.168.38.*, and 192.168.71.*.

IP Address Scheme

Each IP network is assigned a unique network ID. Each host on an IP network is assigned a unique 32-bit (or 64-bit) hardware independent address.

An IP address looks like 102.54.94.97. This is referred to as dotted decimal notation, with each eight bits of an IP address (called an octet) separated from the next eight bits by a period.

The 32-bit address has two parts. The prefix identifies the IP network to which the host belongs. The remaining bits form the Host ID, which uniquely

identifies the host within the network. All hosts on the IP network have the same network ID.

Each host on the network uses the network ID and the host ID to determine which datagrams it should receive or ignore, and to determine the scope of its transmissions.

(32)

Pinging the NE

EMS-XDM enables you to ping the NE to determine the quality of its network connections, by comparing the transmitted and received signals.

To ping the NE:

1. In the Shelf View, select System > Ping. OR

In the EMS-XDM main window, select the NE, and select System > Ping. OR

Right-click the selected NE, and select Ping from the shortcut menu. The NE Ping window opens, displaying ping results, as follows.

Addresses of specific NEs and the data bytes sent at the top of the list Number of bytes received and approximate duration of the signal cycle

in each line

2. To clear the list of results from the previous ping session, click Clean. 3. To select the packet size in bytes, click the Packet Size slider. Standard

value is 64 bytes.

(33)

IP Address Classes

In IP addressing, the value of the first octet determines the number of host ID bits available in the IP address. The following table lists the relevant classes. Table 1-5: IP address classes

Network class Range of first octet Network address bits Available networks Available hosts per network A 1-126 8 126 16,777,214 B 128-191 16 16,384 65,534 C 192-223 24 2,097,151 254

As shown in the table, Class A IP networks support the largest number of host addresses, while Class C supports the least.

NOTE: The highest address in the first octet for Class A networks is 126, and not 127. 127 is reserved.

The IP routing in EMS-XDM provides full support of Class A, B, and C.

IP Address Conventions

The Network Address, an IP address with all host ID bits set to zero, refers to all hosts in the network identified by the network ID prefix.

An IP address with all host ID bits set to 1 is a Directed Broadcast to all the hosts in the network identified by the network ID prefix.

If the source and destination hosts have the same network ID prefix in their IP addresses, then they both belong to the same logical IP network. Therefore, the source host can transmit the datagram over the LAN and assume that the destination host will receive it.

If the source and destination hosts have different network ID prefixes in their IP addresses, then they do not belong to the same IP network. Since the source host cannot communicate with the destination host directly, it must send the datagram to a router or gateway, which forwards it to another IP network.

IP Routing Features

GNEs support user-defined routes towards Ethernet LANs. This information is entered in the IP routing table.

(34)

Subnet Masks

Subnet masks can be used to divide a subnet into several subnets, with fewer hosts per subnet. This is of special significance when planning an IP network with few hosts that does not require an entire Class C address range (254 hosts).

A subnet mask (a 32-bit number) determines the number of bits used for the subnet and host portions of the address. In the subnet mask number, the number 1 determines a subnet division.

Subnet Mask Example 1

This example implements a Class B address of 191.70.55.130 and various subnet masks. A logical AND operation is performed between the IP address and the subnet mask.

In addition, there is a mask that retains the default 16 network and host bits for a Class B address (meaning the default mask is 255.255.0.0). The network ID is 191.70.0.0 and the host ID is 55.130.

Table 1-6: Subnet Mask Example 1

IP octets 191 70 55 130

IP address 1011 1111 0100 0110 0011 0111 1000 0010 Subnet mask 1111 1111 1111 1111 0000 0000 0000 0000 Result 1011 1111 0100 0110 0000 0000 0000 0000

Subnet Mask Example 2

This example implements a mask that divides the host portion into a subnet and host that are each eight bits wide (meaning the mask is 255.255.255.0). This division allows 256 reserved subnets, each with 254 hosts, and facilitates determining the subnet and host from the dotted-decimal IP address. However, the subnet-host boundary can be at any bit position in the host portion of the IP address.

In addition, there is a mask that retains the default 24 network and host bits for a Class C address (meaning the default mask is 255.255.255.0). The network ID is 192.71.55.0 and the host ID is 130.

Table 1-7: Subnet mask for example 2

IP octets 192 70 55 130

(35)

NE Network Interfaces/Routing

NEs may have the following IP network interfaces:

| Ethernet interface (named gtw)

| DCC network interfaces (name dcc0, dcc1, dcc2, and so on)

NEs can be installed in one of the following configurations:

| GNE: The NE is connected to EMS-XDM via Ethernet and communicates

with additional NEs through its DCC LAN interface. EMS-XDM uses the GNE as the router to send datagrams to the NEs on the DCC subnet.

| DCC-only NE: The NE communicates only on its DCC subnetwork and is

not connected directly to a manager.

| Ethernet-only NE: The NE communicates with the manager via Ethernet

only.

GNEs and DCC-only NEs have a default entry in their routing table that includes the destination (typically the manager) and the GNE used to route the datagrams.

EMS-XDM displays the IP routing table, in which you can view and modify IP routing entries for a selected XDM NE, allowing system configurations where an NE is used to route datagrams to other LAN segments.

NOTE: Changing an NE IP from Ethernet only to dcc only from EMS-XDM must be done via the gateway and NE reset.

IP Routing Table

The IP routing table is used by EMS-XDM to route/forward management communication packets between DCC channels and between DCC channels and the Ethernet gateway.

It contains direct routes indicating neighboring elements derived autonomously by the XDM static routes (including the default route) configured by the operator, and routes derived by the OSPF protocol when the protocol is enabled.

(36)

Viewing Actual Routes

You can view the actual IP routes of the selected XDM NE. To view the actual IP routes of an XDM NE:

1. In the Shelf View, select Configuration > DCC > Routing Table. OR

In the EMS-XDM main window, select the NE, and select Configuration > Routing Table.

The Routing Table window opens, displaying the Actual Routes tab, where you can view a listing of the IP Routing Table used by the XDM NE. (The read-only fields described in the following table.)

2. To refresh the window, select Refresh > Refresh. The read-only field Refreshed At displays the last refresh time.

Table 1-8: Routing window fields - Actual Routes tab Field Description

Number Row number. Destination Destination IP address.

Mask Number of bits used for subnet and host portions of address. Mask is a 32-bit value that uses one-bits for network and subnet portions and zero-bits for host portion.

Next Hop IP address of next hop gateway.

Interface Type of LAN interface used by NE (Ethernet or DCC). Route Type Route type (Direct or Indirect).

Metric Metric value of route. For future use: currently displays 1. Protocol Routing protocol on NE LAN interface.

(37)

Viewing and Modifying Static Routes

You can view, add, modify, and delete static IP routing entries for the selected NE.

Viewing Static Routes

To view XDM NE static routes:

| In the Routing Table window, click the Static Routes tab. The Static

Routes tab opens, where you can view, add, modify, and delete IP routing entries for selected XDM NEs, allowing system configurations where an NE is used to route datagrams to other LAN segments.

Adding IP Routes

To add an IP route:

1. In the Static Routes tab of the Routing Table window, select

Configuration > Create. The Add New Route window opens, where you can add new routes to the Routing Table. The Main IP area displays the main IP address and subnet mask of the NE read-only fields.

(38)

2. In the Destination Address area, do one of the following:

If the destination you are adding is a subnetwork (such as a DCC subnet), select All NEs in IP Subnet.

If you are adding a host NE (such as a manager), select Host.

3. In the Destination Address field, type the destination IP address or the IP address of the host. A validation routine in the software only allows you to enter a legal IP address based on the address class. For example, if the value of the first octet you enter corresponds to a Class A address, the next three octets are shaded.

4. In the Route Next Hop field, type the IP address of the interface of a neighboring NE or router. Note that this IP address must be on the same IP subnet as one of the NE interfaces.

5. In the Destination Subnet Mask area, if the destination subnet includes a subnet mask, specify the number of subnet mask bits to use by using the spin buttons.

The number of subnet mask bits depends on the class of the destination IP address (for example, for Class C IP addresses, up to six subnet mask bits can be specified). The software implements a validation procedure that only allows you to enter legal values based on the class of the destination IP address. The value of the 32-bit subnet mask number appears in the read-only Subnet Mask field and changes to reflect the current setting of the Subnet Mask Bits field.

The IP address range of the subnet, as determined by the destination IP address and the subnet mask, appears in the Destination Subnet read-only field. This field is also dynamically updated to reflect the current settings. If the values you entered are valid, the OK button becomes active. Click OK to submit the changes. The system performs a validation check against the routing table. If a problem is detected, a message is displayed. Change the routing configuration as necessary to resolve the problem, and click OK to submit the changes.

(39)

Editing IP Routes

To edit an IP route:

1. In the Static Routes tab of the Routing Table window, select the relevant row.

2. Select Configuration > Edit. The Edit Route window for the selected NE opens. The fields are the same as for the Add Route window (as shown in the previous procedure).

3. Fill in the fields, as described in the previous procedure. 4. Click OK to submit the changes.

Deleting IP Routes

To delete an IP route:

1. In the Routing Table window, select the relevant row.

2. Select Configuration > Delete. A confirmation window opens, prompting you to confirm the deletion.

3. Click Yes to confirm. The selected IP route is deleted from the routing table.

DCC and IP Networking

EMS-XDM enables you to create, view, and modify IP network interface, DCC termination, and Open Shortest Path First (OSPF) interface parameters.

Under dynamic DCC routing, NEs intercommunicate with each other over the DCC interfaces using the OSPF protocol which results in dynamic construction of routing tables. Dynamic DCC routing enables NEs to automatically set up new routes if existing ones fail.

OSPF is a routing protocol that determines the best path for routing IP traffic over a TCP/IP network based on distance/metric between nodes. OSPF is an Interior Gateway Protocol (IGP) that works within an Autonomous System (AS). It is a link state protocol capable of handling large networks with little protocol traffic overhead.

Configuration of network links over which OSPF is supported:

| DCC | Gateway | Clear Channel

(40)

EMS-XDM performs IP forwarding between all network interfaces, including the DCC and Ethernet Gateway Management interfaces. EMS-XDM

implements the dynamic OSPF routing protocol over these network interfaces to automatically determine the routing table. OSPF can be configured for any subset of these network interfaces.

OSPF support includes:

| Point-to-point and broadcast interfaces | Up to four OSPF areas

| Address summarization

| Support for Area Border Router (ABR) functionality

| Support for Autonomous System Border Router (ASBR) functionality,

including redistribution of static routes

| Support of loopback address as Router ID | Configuration of Hello Protocol parameters

| Support of "passive" interfaces to allow distribution of routes to attached

(41)

Viewing and Modifying OSPF Settings

You can view and modify OSPF settings.

Viewing Overall OSPF Settings

To view overall OSPF settings:

1. In the Shelf View, select Configuration > DCC > IP Networking. The IP Networking window opens.

2. Click the Overall OSPF tab. The Overall OSPF tab opens, where you can view and modify general OSPF settings, as described in Overall OSPF Tab Parameters (on page 1-24).

(42)

Table 1-9: Overall OSPF Tab Parameters Field Description

OSPF Enable OSPF state, Enable (default) or Disable.

AS Border Router ASBR state, Enable (default) or Disable. When set, OSPF advertises its static routes.

OSPF Area ID OSPF Area ID table comprising 1-4 distinct areas coded as 32-bit integers and displayed as IP addresses sorted from low to high areas. By default, first row of table shows backbone area

(0.0.0.0). You can add and remove OSPF areas from table, taking into account that there is at least one row in a table and areas used in an area range or defined for an OSPF interface cannot be removed.

OSPF Area Range

Table Supports up to 12 distinct area ranges summarizing NEs advertised over area boundaries. Instead of advertising NEs individually, the ABR advertises the range.

Table rows are ordered by area ID and within that by range address. You can edit selected rows and add and remove area ranges from the table. Default Area Range table contains no entries.

Range Address and Range Mask fields define subnet of NEs.

Area ID dropdown list displays area IDs already defined. LAN Emulation

Interworking Toggles built-in LAN emulation interworking function. When enabled, prevents packet duplication from flooding domain with multiple XDM gateways (dynamic routing "islands"). When performing OSPF over LAN Emulation interface, EMS-XDM performs multicast address translation to allow elements in flooding domain. Part of this mechanism works by decreasing OSPF router priority to management station. Default value of priority decrement is 1 (range 1-100).

Management Address and Management Mask must match IP address of Management Station defined as subnet.

(43)

Enabling/Disabling OSPF and ASBR Settings

To enable/disable OSPF and ASBR settings:

1. In the OSPF Enable area, select Enable or Disable. (By default, OSPF is enabled.) OSPF can be enabled on a network interface even if OSPF is disabled.

2. To enable/disable ASBR, in the AS Border Router area, select Enable or Disable. (By default, ASBR is enabled.) When ASBR is enabled, OSPF advertises its static routes.

3. Click to apply the changes to the NE.

Adding an OSPF Area ID

To add an OSPF area ID:

1. In the OSPF Area ID area, click Add. An empty row is added to the table. 2. In the new row, type a valid ID.

3. Click to apply the changes to the NE. The system downloads the configuration to the NE after performing a validation check to confirm that the new entry is unique.

Removing an OSPF Area ID

To remove an OSPF area ID:

1. In the OSPF Area ID table, select the row to be removed. 2. Click Remove. The row is deleted from the table.

NOTE: Areas cannot be edited, only added or removed. To reassign an area ID, add a new area first and modify the old area (in the OSPF interface) to the new area. When there are no occurrences of the old area, it can be deleted from the OSPF Area ID table.

(44)

Adding an OSPF Area Range

To add an OSPF area range:

1. In the OSPF Area Range Table area, click Add. An empty row is added to the table.

2. In the new row, in the Range Address column, type a valid range address. 3. Click to apply the changes to the NE. The system downloads the

configuration to the NE after performing a validation check to confirm that the new entry is unique.

Editing an OSPF Area Range

To edit an OSPF area range:

1. In the OSPF Area Range table, select a row. 2. Edit the range, as required.

Removing an OSPF Area Range

To remove an OSPF area range:

1. In the OSPF Area Range table, select the row to be removed. 2. Click Remove. The row is deleted from the table.

Enabling LAN Emulation Interworking

To enable LAN emulation interworking:

1. In the LAN Emulation Interworking area, select the LAN Emulation Interworking checkbox.

2. In the Management Address and Management Mask fields, type the IP address of the Management Station defined as a subnet. All addresses in this subnet must be routed the same way.

(45)

Terminating DCCs

To terminate a DCC, you need to connect the MS or RS DCC object to a DCC TTP and then associate the termination with an IP network interface.

The RS-DCC or MS-DCC for a selected port is terminated. In the MS or RS Internals window, you can begin the process of associating a selected DCC object with an existing network interface.

Terminating DCC Process

To terminate DCCs:

1. In the Shelf View, double-click a card to open its Card Internals window. The Card Internals window for the selected card opens.

2. Select the relevant port to display the MS or RS objects in the Zoom area. 3. In the Zoom area, double-click the MS or RS object. The relevant MS or

(46)

4. In the DCC tab, in the Port area, right-click a DCC object, and on the shortcut menu, select Terminate DCC. The Zoom area displays a connection arrow between the DCC object and relevant MS or RS DCC object.

The Edit Termination window opens, displaying the Network Interface Attributes tab. The Encapsulation field displays either PPP or LAN Emulation, according to what is set in the EMS Preference window.

(47)

5. To view and modify advanced OSPF interface attributes, click the Advanced tab. The Advanced tab opens, displaying advanced OSPF interface attributes.

(48)

Changing Default Encapsulation Attribute

To change the default encapsulation attribute:

1. In the EMS-XDM main window, select System > EMS Preference. The EMS Preference window opens.

2. Newly created dcc interfaces are assigned the default encapsulation (PPP or LAN Emulation), as configured in the EMS Preference window. To change the default encapsulation, select either the PPP or LAN Emulation checkbox.

The Edit Termination window for a newly created interface displays the selected encapsulation option.

LAN Emulation (Legacy) Encapsulation: Allows you to create up to 32 (or 64 for xMCPB) DCC channels associated with a single network interface, the dcc0 (a fixed value), as shown in the Network Interface field in the Edit Termination window and in the DCC/GCC

Terminations tab of the IP Networking window (described in the next procedure). A network interface that is already associated with another termination will be enabled for the same speed only (that is, MS or RS or 2M). (Any dcc network interface (dcc0, dcc1, dcc2, and so on) can be LAN Emulation, but all DCCs must be at the same speed.)

PPP (Point to Point Protocol) Encapsulation: Allows you to associate one channel (DCC). PPP can connect with only one channel (that is, to DCC1, or to DCC2, and so on, up to network interfaces dcc32 or dcc33 (of the clear channel) or dcc64 or dcc65 (for the clear channel for xMCPB). You cannot select a network interface that is already associated with another termination. In the Network Interface dropdown list, the disabled dcc interfaces represent occupied interfaces in the IP Networking DCC/GCC Terminations tab. (Occupied interfaces are shaded and cannot be selected.)

In Edit Termination window, you can change the encapsulation to PPP by selecting an available interface from the Network Interface dropdown list. This automatically changes the encapsulation to PPP. After you apply the changes, the results appear in the DCC Terminations tab of the IP Networking window.

Viewing Terminated DCC Channels

To view a list of the terminated DCC channels:

| In the IP Networking window, click the DCC/GCC Terminations tab.