01-1 NE Management

All Rights Reserved © Alcatel-Lucent 2012

1350 OMS WDM Operation and Maintenance

Page 1

All rights reserved © Alcatel-Lucent 2011 Passing on and copying of this document, use and communication of its contents

not permitted without written authorization from Alcatel-Lucent



Page 5

Section 1. Product Overview

Module 1. 1350 OMS Overview

Module 2. 1350 OMS WDM Overview

Section 2. Graphical Interface

Module 1. Web Portal

Module 2. Multi Service GUI

Module 3. 1350 OMS MAP version 2.0

Section 3. Network Management

Module 1. Network Element Management

Section 4. Link, Cross and Inconsistent Connections

Module 1. Link Connections

Module 2. Cross Connections

Module 3. Inconsistent Connections

Section 5. WDM Connection Management

Module 1. Physical Connections

Module 2. Path and Trail Connections

Module 3. Optical Transport Services

Section 6. Wavelength Tracker (WLT)

Module 1. WLT Concepts

Section 7. Commissioning and Power Balancing (CPB)

Module 1. CPB Concepts

Section 8. Fault Management

Module 1. 1350 OMS Alarm Management

Module 2. WDM Alarm Management

Section 9. Performance Monitoring (PM)

Module 1. PM Management



Page 6

Welcome to 1350 OMS WDM R 9.5 Operation

Upon completion of this course, you should be able to:

1. Comprehend the 1350 OMS WDM application topology

2. Navigate the 1350 OMS WDM Graphical User Interface

3. Manipulate WDM physical and logical connections

4. Identify Link, Cross, and Inconsistent connection concepts

5. Determine Physical, Path and Trail requirements

6. Determine Transport Services requirements

7. Identify Wavelength Tracker concepts

8. Perform Commissioning and Power Balancing

9. Perform Fault Management

10. Determine Performance Monitoring requirements



Page 117



Page 119

This section presents an introduction to the 1350 OMS WDM functionality and its relationship to the Element

Management Layer (EML).

Futher discussion of the functionality depicted on these slides will be discussed in more detail through out the

course.



Page 120

When a Q3 interface is used, the NE needs to be configured with a NSAP OSI address.

When a SNMP or TL1 interface is used, the NE needs to be configured with an IP address.

Note This module will discuss the creation of an 1830PSS (4G TL1) NE. The 1350 OMS

EML R 9.5 Operation course (TOS63017) provides creation procedures for the

different families of equipment based on their management interfaces (Q3, TL1,

SNMP, Q3 CNA etc.).



Page 121

The SID is known as the Target Identifier (TID) in 1830 PSS.

The SID/TID is composed of a string of up to 32 (for ETSI) and 20 (for ANSI) non case-sensitive alphanumeric

characters, including the hyphen (-) character or a quoted string up to 32 (for ETSI) and 20 (for ANSI),

including any special characters.

In the non-quoted string, the SID/TID must start with a letter and end with an alphanumeric character.

Consecutive hyphens (-) are not allowed. The number of hyphens used in the string must not be greater than

four.

The OSPF routing for the OAMP port should be set to redistribute if the routing table of the Gateway NE is not

to be advertised externally.



Page 122



Page 123



Page 124



Page 125



Page 126



Page 127

OSPF Areas is for an OSPF configuration where automatic routing is required. OSPF is a form of dynamic

routing which uses a routing table to determine the best route path.

Static routes are routes through a data network described by fixed paths (statically).



Page 128

This slide and the next two slides focus on the creation and addressing of an 1830 PSS without security.



Page 131Section 3 · Module 1 · Page 131



Page 132

Check the correct configuration and process status with the System Administrator.



Page 133

If the operator doesn‟t select the Supervision Area and the EML Domain, in the above procedure, EML will

automatically chose these two parameters. The system takes account of each available “EMLIMSNA” and tries

to make their load homogeneous.

The Directory Field refers to the Physical Network Management GUI server (PNMIM) of the EML instance in

which the NE must be created. Normally there is only one EML instance installed in 1350 OMS and the field is

automatically completed with the proper value. If more than one EML instance is available, the operator

must select the desired PNM GUI Server from the drop-down list.



Page 134



Page 135

The GNE Flag enables a TL1 command line interface operator to act on a Remote NE (RNE) through a Telnet

access to he Gateway NE (GNE). This feature is applicable only to the ANSI environment.

If the “FTAM” parameter is set to “Use GW”, the NE under creation can be used as a repository to download

the SW to its Remote NE. This feature will be available in future releases.

The TID (Target Identifier) i.e. the NE identifier used in the messages exchanged between the NE and the

EML, must be equal to the “System IDentifier” (SID) set into the NE.

SID (or TID) is a string of up to 32 (for ETSI) or 20 (for ANSI) non case-sensitive alphanumeric characters,

including the hyphen (-) character, or a quoted string of up to 32 for ETSI (20 for ANSI) characters,

including any special character. If it is a non-quoted string, SID (or TID) must start with a letter and end

with an alphanumeric character. Consecutive hyphens (-) shall not be allowed. Number of hyphens shall

not be greater than four.

The NE address can be modified only if the NE is not supervised (i.e. in the "declared" state).

The SNMP address setting is not required.

Note For the creation of 1830 PSS NEs, the GNE/RNE flag setting is not critical and should

be left in the default state.

1830PSS GNE/RNE roles are defined at the IP DCN level and transparent to 1350 OMS.

1350 OMS treats all the PSS NEs as GNEs. However, the GNE/RNE flag is critical for

other NE types thought. For example correct settings are mandatory for TL1 NEs.



Page 136

Prior to starting supervision, check to see if the NE is reachable.

Ping (Packet Internet Grouper) tests the DCN parameters (address, DCC, LAN interfaces etc.)

Supervision tests the supervision rights

The Ping NE function of the Telecommunication Network Management OS enables the administrator to test

the communication link with an NE. The Ping NE function is managed by the Middleware Interface (MW-INT)

application, which is the platform on which the 1350 OMS is built.



Page 137



Page 138

Supervising NEs is an essential aspect of the network management. It enables the gathering of information

concerning the behavior of the NE with respect to its functional state.

The supervision of an NE consists in establishing a communication that allows the user to perform EML

operations such as configuration and alarm management.

The NE address must be declared before starting the supervision of this NE.

After supervision is started, the “Supervision State” attribute changes from DECLARED to SUPERVISED.



Page 139



Page 140



Page 141

All the procedures on networks and sub-networks described in the present Module can be issued as well from

the MS-GUI networks and sub-networks lists.

To open the network list: “Search Map Networks” (only ROOT is shown).

From the ROOT object in the list it is possible to create sub-networks (“Actions Create Sub-Network”) or

list the first-level sub-networks (Search Sub-Networks).

From the Sub-Networks in the Sub-Network lists, it is then possible:

To search the contained Sub-Networks or other Physical or SDH (OTN) objects.

To create a new contained sub-network.

To modify (or even delete) the selected sub-network



Page 142

“ROOT” is always configured by default as the root network under which all managed sub-networks must be

created, based on the desired hierarchy.

“ROOT” cannot directly contain nodes.



Page 143



Page 144

If the creation is successful, the header window of the Create Sub-network panel turns green for success; red

indicates a failure.



Page 145



Page 146



Page 147



Page 148



Page 149



Page 150



Page 151Section 3 · Module 1 · Page 151



Page 152



Page 153

The operator is optionally allowed to enter a filtering criteria defined in terms of a list IP Address/Mask pairs.

Only the filtered list of NE belonging to the “subnets” defined by any of the masks will be given back to the

GUI.

In case of the operator is not filling in any filtering criteria, the discovery scope will consist of the overall

subset of 1830PSS network elements that are reachable from the NE where the action is triggered.



Page 154

The discovery process can last several minutes, depending on the number of NEs to be discovered.

Location Name and Supervision area are populated based on the gateway NE by which the process has been

started.

In the case of an „Abort‟ request, the NEs discovered up to the time the discovery was interrupted can be

created by clicking on “Next”.



Page 155

The address and User ID and password of the auto discovered NEs are automatically set during the discovery

procedure.

Address is set based on the info sent by the discovered NEs.

User ID and password are the same as the ones of the Gateway NE.

Eventually change the location name, check NE IP address, User ID and password, and start supervision.



Page 156

Documents

01-1 NE Management