Вы находитесь на странице: 1из 352

Title page

Title page Alcatel-Lucent 1830 1354 RM-PhM Photonic Manager | Release 8.5.2 EMS REFERENCE GUIDE 3AL61308AAAA ISSUE
Title page Alcatel-Lucent 1830 1354 RM-PhM Photonic Manager | Release 8.5.2 EMS REFERENCE GUIDE 3AL61308AAAA ISSUE

Alcatel-Lucent 1830

1354 RM-PhM Photonic Manager | Release 8.5.2

EMS REFERENCE GUIDE

3AL61308AAAA

ISSUE 1

MARCH 2011

Legal notice

Legal notice

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners.

The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.

Copyright © 2011 Alcatel-Lucent. All rights reserved.

Conformance statements

Interference Information: Part 15 of FCC Rules

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy. If the equipment is not installed and used in accordance with the guidelines in this document, the equipment may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at the expense of the user.

Security statement

In rare instances, unauthorized individuals make connections to the telecommunications network through the use of remote access features. In such an event, applicable tariffs require that the customer pay all network charges for traffic. Alcatel-Lucent cannot be responsible for such charges and will not make any allowance or give any credit for charges that result from unauthorized access.

Limited warranty

For terms and conditions of sale, contact your Alcatel-Lucent Account Team.

Ordering Information

For more ordering information, refer to "How to order" in the section titled "About this document."

Contents

Contents About this document Purpose xix xix A u d i e n c e xix

About this document Purpose

xixxix

Audience

xixxix

Document conventions

xxxx

Related information

xxxx

Document support

xxixxi

Technical support

xxiixxii

 

How to order

xxiixxii

Packaging collection and recovery requirements

xxiixxii

Recycling/Take-Back/Disposal of Product

xxiiixxiii

How to comment

xxiiixxiii

1 Overview

 

Overview

1-11-1

1354

RM-PhM server

1-11-1

1354

RM-PhM hardware configurations

1-21-2

1354

RM-PhM communication

1-31-3

1354

RM-PhM release specifications

1-31-3

1354

RM-PhM engineering guidelines

1-41-4

1354

RM-PhM scaling

1-41-4

New features introduced in 1354 RM-PhM R8.5.2

1-41-4

2 System administration

 

Overview

2-12-1

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

iii

Contents

System requirements

2-32-3

Interfaces and protocols

2-32-3

1354

RM-PhM redundant servers

2-72-7

Installing the 1354 RM-PhM

2-122-12

Before you start

2-122-12

Installing the 1354 RM-PhM on a Linux or Solaris x86/x64 platform

2-132-13

Installing the 1354 RM-PhM on Windows

2-182-18

Starting and stopping the server and client

2-242-24

1354

RM-PhM service wrapper

2-242-24

Starting the 1354 RM-PhM server on Linux or Solaris x86/x64

2-252-25

Stopping the 1354 RM-PhM server on Linux or Solaris x86/x64

2-292-29

Starting the 1354 RM-PhM server on Microsoft Windows

2-312-31

Stopping the 1354 RM-PhM server on Microsoft Windows

2-322-32

Starting a client session

2-332-33

Stopping a client session

2-352-35

Configuring the 'iptables' firewall

2-352-35

Configuring the file transfer properties of the 1354 RM-PhM server

2-362-36

Configuring the NTP properties of the 1354 RM-PhM server

2-372-37

Configuring the NTP properties of the network elements

2-382-38

1354 RM-PhM database backup and restore

2-392-39

1354

RM-PhM database backup

2-402-40

1354

RM-PhM database restore

2-422-42

iv

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

Contents

 

Recovering from file corruption without having to restore from a backup

2-432-43

Performing a server switch-over

2-442-44

1696

ROADM and 1830 PSS network element database backup and restore

 

2-452-45

 

Performance Monitoring (PM) Archive Setting

 

2-482-48

 

SNMP Trap Alarm Forwarding

 

2-502-50

 

RADIUS server and user authentication

 

2-542-54

 

1354

RM-PhM user management

 

2-732-73

 

NE user management

 

2-792-79

 

1354

RM-PhM login session settings

 

2-842-84

 

1696

ROADM and 1830 PSS network element software management

 

2-872-87

 

1354

RM-PhM management of Red-C RAMAN Amplifier & EDFA Booster

 

2-952-95

3

Configuring and navigating the network

Overview

3-13-1

Types of network views

3-23-2

Discovering network elements

3-63-6

Configuring network links

3-153-15

Showing topological connections

3-173-17

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1

March 2011

v

Contents

 

Configuring the network element and network fiber topology

3-183-18

Using Wavelength Tracker monitoring capability

3-233-23

Managing optical power levels

3-243-24

Using the automatic power management interface

3-303-30

Managing APS groups

3-393-39

CLI

cut-thru

3-443-44

TL1

cut-thru

3-453-45

WebUI cut-thru

3-463-46

4

Monitoring system events and network alarms

 

Overview

4-14-1

 

Overview of network alarms

 

4-34-3

 

Opening an alarm window for a managed object or group

 

4-74-7

 

Acknowledging an alarm

 

4-94-9

 

Suppressing alarms

 

4-104-10

 

Clearing an alarm

 

4-114-11

 

Using the 1354 RM-PhM log view

 

4-124-12

 

Performance monitoring

 

4-154-15

 

Starting and stopping PM collection

4-164-16

Viewing PM data and raw PM data

4-174-17

vi

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

Contents

 

Configuring PM and TCA profiles

4-174-17

Troubleshooting Wavelength Tracker alarms

 

4-184-18

 

Determining the source of an alarm

4-194-19

Determining the WaveKeys used for a service

4-214-21

Querying the WaveKeys

4-224-22

Troubleshooting the WaveKey insertion failed alarm

4-234-23

Troubleshooting the Missing WaveKey alarm

4-244-24

Troubleshooting the Unexpected WaveKey alarm

4-264-26

Troubleshooting the Duplicate WaveKey alarm

4-274-27

Troubleshooting the Invalid WaveKey alarm

4-294-29

Troubleshooting a power out of range alarm

 

4-304-30

5

1354 RM-PhM alarm reference

 

5-15-1

 

A communication failure occurred

 

5-25-2

 

ActiveAlarmResyncFailure

An attempt to resynchronize the alarms from the NE

5-45-4

AutoUpgradeFailure

 

5-55-5

 

CardOutOfSync

 

5-75-7

 

Communication failure

 

5-85-8

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1

March 2011

vii

Contents

COMMUNICATION_FAILURE

 

5-95-9

Creation Failure

 

5-105-10

Duplicate programmed wave key

 

5-115-11

Equipment cache invalid

 

5-135-13

Facility Retrieval

 

5-145-14

Failed Auto Discovery

 

5-155-15

Failed to archive

 

5-175-17

Failed to register 1354 RM-PhM as trap destination

 

5-185-18

Fault log archive configuration failed

 

5-205-20

ActiveAlarmResyncFailure

 

5-215-21

install error

 

5-225-22

Install Extension error

 

5-235-23

Invalid Annotation

 

5-245-24

viii

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

Contents

Invalid Parameter

 

5-255-25

Invalid Supervisor

 

5-265-26

Invalid Table

 

5-275-27

Invalid Variable

 

5-285-28

Invalid XML reference

 

5-295-29

Invalid XML value

 

5-305-30

Inventory Retrieval

 

5-315-31

JDBC Log Data Store Error

 

5-325-32

Log Initialization

 

5-335-33

LOGGER HALT

 

5-345-34

LOGGER PURGELC

 

5-355-35

Lookup Error

 

5-365-36

Low Level Parsing Error

 

5-375-37

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1

March 2011

ix

Contents

 

Meta Change

 

5-385-38

Meta Mismatch

5-395-39

Missing XML mandatory attribute

5-405-40

Missing XML mandatory element

5-415-41

NE + neName + "PM retrieval failed"

5-425-42

NE + neName + "system time out of sync with 1354 RM-PhM"

5-445-44

NE Backup failed

5-455-45

NEEventLogArchiveConfigFail

5-465-46

NERequestLogArchiveConfigFail

5-475-47

Network Connection error

5-485-48

 

New Entity

 

5-495-49

1354

RM-PhM behind in performing PM tasks

 

5-505-50

1354

RM-PhM failed to initialize adaptation

 

5-515-51

x

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

Contents

1354

RM-PhM PowerCommissionInProgress

 

5-525-52

1354

RM-PhMSetNMSAsNTPServerMessage

 

5-535-53

Object Lookup

5-545-54

Object Prop Change

5-555-55

Object removal

5-565-56

Object Storage

5-575-57

Parsing Exception

5-585-58

 

PK Lookup

 

5-595-59

REDUNDANCY

5-605-60

Scalability Problem

5-615-61

ServerLogArchiveConfigFail

5-625-62

Service definition downloaded

5-635-63

SNMP Bulk Get Error

5-645-64

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1

March 2011

xi

Contents

SNMP Error received

 

5-655-65

SNMP Get Error

 

5-665-66

SNMP GetNext Error

 

5-675-67

SNMP Set Error

 

5-685-68

The scheduled time for Software Load task for neName is scheduled to begin at startTime which is in the past. It will be run immediately.

5-695-69

The Software Activation task for get neName is scheduled to begin at get StartTime which is in the past. Please re-schedule.

5-705-70

The Software Activation task for " + _neName + " has been aborted due to the presence of unacknowledged alarms."

5-715-71

The Software Load task for neName that was scheduled to begin at get StartTime failed to initiate.

 

5-725-72

TNREPLICATIONSERVICE

 

5-745-74

Unavailable Annotation

 

5-755-75

Unavailable NEType

 

5-765-76

UnknownNEType

 

5-775-77

xii

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

Contents

UnknownSource

 

5-785-78

 

Unrecognized Autonomous

 

5-805-80

 

Unrecognized XML element

 

5-815-81

 

Unrecognized XML attribute

 

5-825-82

 

XML validation

 

5-835-83

6

Managing services

Overview

6-16-1

Setting service preferences

 

6-26-2

 

Listing and editing services

 

6-36-3

 

Creating or editing a wavelength service

 

6-56-5

 

Importing and exporting service definitions

 

6-146-14

 

Discovering services in the network

 

6-166-16

 

Unmanaging services in the network

 

6-176-17

 

Partial services

 

6-186-18

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1

March 2011

xiii

Contents

Sub-rate service

 

6-196-19

Sub-rate service creation via service wizard

6-226-22

1696R and 1830 PSS interoperability

 

6-256-25

Glossary

Index

xiv

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

List of tables

List of tables 1 Command syntax rules xx xx 2 - 1 1 3 5 4

1

Command syntax rules

xxxx

2-1

1354 RM-PhM to network element protocols and ports

2-32-3

2-2

NMA/Transport to GNE protocols and ports

2-72-7

2-3

Task list for configuring and using a RADIUS authentication server

2-552-55

2-4

1354 RM-PhM user role permissions

2-762-76

4-1

WaveKey encoding and decoding points

4-184-18

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

xv

List of tables

xvi

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

List of figures

List of figures 1-1 1696 ROADM and 1830 PSS network management system 1-2 1-2 2 -

1-1

1696 ROADM and 1830 PSS network management system

1-21-2

2-1

1354 RM-PhM redundant servers

2-72-7

2-2

EMS Status window

2-102-10

2-3

1354 RM-PhM installation wizard - last chance to cancel

2-162-16

2-4

1354 RM-PhM installation wizard - last chance to cancel

2-222-22

2-5

Security alert dialog

2-342-34

2-6

System Settings dialog

2-492-49

2-7

SNMP Trap Destinations table

2-512-51

2-8

The Add RADIUS Client dialog

2-572-57

2-9

The Add Native User dialog

2-582-58

3-1

Uni-directional light path power window

3-243-24

3-2

Optical power levels at a Wavelength Tracker detection point

3-263-26

3-3

Ingress monitor point power management window

3-333-33

3-4

Egress monitor point power management window

3-343-34

3-5

Bi-directional path power trace

3-363-36

3-6

Uni-directional light path power window

3-373-37

3-7

APS Views window

3-403-40

3-8

APS Group attributes window

3-403-40

4-1

1354 RM-PhM Topology View

4-34-3

6-1

Wavelength service fiber endpoints

6-96-9

6-2

Manually power-managed service

6-106-10

6-3

Automatically power-managed service

6-116-11

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

xvii

List of figures

xviii

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

AboutAboutthis document

this document

About About this document this document Purpose   This document provides information about accessing the 1354

Purpose

 

This document provides information about accessing the 1354 RM-PhM and using it to configure and manage the 1696 ROADM and 1830 PSS network. It contains the following chapters:

Chapter 1, “Overview”

Chapter 2, “System administration”

Chapter 3, “Configuring and navigating the network”

Chapter 4, “Monitoring system events and network alarms”

Chapter 5, “1354 RM-PhM alarm reference”

Chapter 6, “Managing services”

Audience

This document is intended for the following users of the 1696 ROADM and 1830 PSS documentation library:

administrators

operators

maintenance personnel

1696 ROADM and 1830 PSS products are meant to be installed, operated, and maintained by personnel who have the knowledge, training, and qualifications required to safely perform the tasks assigned to them. The information, processes, and procedures contained in the 1696 ROADM and 1830 PSS product documentation are intended for use by trained and qualified personnel.

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

xix

About this document

Document conventions

Command syntax

Table 1, “Command syntax rules” (p. xx) describes the command syntax rules used in this document.

Table 1

Command syntax rules

Syntax format

Description

bold

 

Commands and keywords . Enter command line arguments that are in bold exactly as written.

italics

Variables . You must substitute a value for command line arguments that are in italics.

[

optional ]

Optional keywords or variables . Enter command line arguments

[

optional ]

that are enclosed in square brackets, if desired.

{

a

|

b | c }

Required alternate keywords or variables. You must choose one

{

a

|

b | c }

command line argument enclosed within the braces. Choices are separated by vertical (OR) bars.

[

a |

 

b | c ]

Optional alternate keywords or variables . Choose one command

[

a

|

b | c ]

line argument enclosed within the braces, if desired. Choices are separated by vertical (OR) bars.

Related information

The Alcatel-Lucent 1354 RM-PhM Release 8.5.2 Photonic Manager EMS Reference Guide is part of a set of documents that support the 1696 ROADM and 1830 PSS System. The following documents are available:

1696 ROADM Documents

1830 PSS Documents

Alcatel-Lucent 1696 ROADM Technical Information Guide

Alcatel-Lucent 1830 Photonic Service Switch 36/32/16 (PSS-36/32/16) Release 3.5.1 Product Information and Planning Guide

Alcatel-Lucent 1696 ROADM Hardware and Network Configuration Guide

Alcatel-Lucent 1696 ROADM Operations, Administration, Maintenance, and Provisioning Guide

Alcatel-Lucent 1830 Photonic Service Switch 36/32/16 (PSS-36/32/16) Release 3.5.1 User Provisioning Guide

Alcatel-Lucent 1696 ROADM Web Interface Reference Guide

Alcatel-Lucent 1696 ROADM Maintenance and Troubleshooting Guide

Alcatel-Lucent 1830 Photonic Service Switch 36/32/16 (PSS36/32/16) Release 3.5.1 Maintenance and Trouble-Clearing Guide

xx

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

About this document

1696 ROADM Documents

1830 PSS Documents

Alcatel-Lucent 1696 ROADM CLI Reference Guide

Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 3.5.1 Command Line Interface Guide

Alcatel-Lucent 1696 ROADM TL1 Reference Guide

Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 3.5.1 TL1 Commands and Messages Guide

Alcatel-Lucent 1696 ROADM Safety and Compliance Guide

Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 3.5.1 Safety Guide

Alcatel-Lucent 1696 ROADM LPT Reference Guide

Alcatel-Lucent 1830 Photonic Service Switch (PSS) Release 3.5.1 Engineering and Planning Tool User Guide

Alcatel-Lucent 1696 ROADM Hardware Installation Guide

Alcatel-Lucent 1830 Photonic Service Switch 36/32/16 (PSS-36/PSS-32/PSS-16) Release 3.5.1 Installation and System Turn-Up Guide

Alcatel-Lucent 1696 ROADM Commissioning and Turn-up Guide

 

Alcatel-Lucent 1830 Photonic Service Switch 4 (PSS-4) Release 1.5.x User Guide

 

Alcatel-Lucent 1830 Photonic Service Switch 1 (PSS-1) Release 2.7.0 GBEH Edge Device User Guide

 

Alcatel-Lucent 1830 Photonic Service Switch 1 (PSS-1) Release 1.7.0 MD4H Edge Device User Guide

 

Alcatel-Lucent 1830 Photonic Service Switch 1 (PSS-1) Release 1.0.0 AHP Amplifier User Guide

 

Alcatel-Lucent 1830 Photonic Service Switch 1 (PSS-1) Release 1.7.0 MSAH Edge Device User Guide

 

Release 8.5.2

Document support

Alcatel-Lucent provides a referral telephone number for document support. Use this number to report errors or to ask questions about the document. This is a non-technical number. The referral number is 1 (888) 727 3615 (continental United States) or +1 (630) 713 5000 (for all countries).

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1

March 2011

xxi

About this document

Technical support

Login to OnLine Customer Support (OLCS) at http://support.alcatel-lucent.com and select your country from the pulldown menu under "Product Technical Support - Phone and Email Contact Information".

How to order

Contact your local sales representative, or login to OLCS at http://support.alcatel- lucent.com and select your product from the pulldown menu under "Technical Content for".

Packaging collection and recovery requirements

Countries, states, localities, or other jurisdictions may require that systems be established for the return and/or collection of packaging waste from the consumer, or other end user, or from the waste stream. Additionally, reuse, recovery, and/or recycling targets for the return and/or collection of the packaging waste may be established.

For more information regarding collection and recovery of packaging and packaging waste within specific jurisdictions, please contact the Alcatel-Lucent Field Services/Installation - Environmental Health and Safety organization.

xxii

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

About this document

Recycling/Take-Back/Disposal of Product

Collect and treat electronic products bearing or referencing the following symbol, within the European Union, at the end of their useful life in compliance with applicable European Union and local legislation. Do not dispose of these products as part of unsorted municipal waste. Due to materials that may be contained in the product, such as heavy metals or batteries, the environment and human health may be negatively impacted as a result of inappropriate disposal.

negatively impacted as a result of inappropriate disposal. Note : In the European Union, a solid

Note: In the European Union, a solid bar under the crossed-out wheeled bin indicates that the product was put on the market after 13 August 2005.

Moreover, in compliance with legal requirements and contractual agreements, where applicable, Alcatel-Lucent provides for the collection and treatment of Alcatel-Lucent products at the end of their useful life. Alcatel-Lucent also provides for the collection and treatment of existing products that have been displaced by Alcatel-Lucent equipment.

For information regarding take-back of equipment by Alcatel-Lucent, or for more information regarding the requirements for recycling/disposal of product, please contact your Alcatel-Lucent account manager or Alcatel-Lucent Take-Back Support at takeback@alcatel-lucent.com.

How to comment

To order Alcatel-Lucent documents, contact your local sales representative or use Online Customer Support (OLCS) (https://support.lucent.com).

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1

March 2011

xxiii

About this document

xxiv

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

1

1Overview

Overview

Purpose

1 1 Overview Overview Purpose This chapter provides an overview of the 1354 RM-PhM. It contains

This chapter provides an overview of the 1354 RM-PhM. It contains the following sections:

Contents

1354

RM-PhM server

1-1

1354

RM-PhM hardware configurations

1-2

1354

RM-PhM communication

1-3

1354

RM-PhM release specifications

1-3

1354

RM-PhM engineering guidelines

1-4

1354

RM-PhM scaling

1-4

New features introduced in 1354 RM-PhM R8.5.2

1-4

1354 RM-PhM server

The 1354 RM-PhM is a client-server system that is used to perform remote monitoring and control of networks of 1696 ROADM and 1830 PSS equipment. Figure 1-1, “1696 ROADM and 1830 PSS network management system” (p. 1-2) shows a high level view of the 1354 RM-PhM together with 1696 ROADM and 1830 PSS network elements. The Alcatel-Lucent 1830 PSS family includes the 1830 PSS-36/PSS-32/PSS-16, the 1830 PSS-4, the Alcatel-Lucent PSS-1 GBEH, the Alcatel-Lucent PSS-1 MD4H, and the Alcatel-Lucent PSS-1 AHP.

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

1-1

Overview

1354 RM-PhM server

Figure 1-1 1696 ROADM and 1830 PSS network management system

Figure 1-1 1696 ROADM and 1830 PSS network management system The 1354 RM-PhM supports management of

The 1354 RM-PhM supports management of both 1696 ROADM and 1830 PSS network elements. The 1354 RM-PhM server communicates with the network elements using the SNMP protocol. A network element is characterized by having an SNMP agent. As a result, a network element is a managed entity.

1354 RM-PhM hardware configurations

Listed in this section are the operating system requirements for the servers and clients of a 1354 RM-PhM.

Servers

The 1354 RM-PhM server runs on either Windows Server 2008, Red Hat Enterprise Linux Release 5.5., Solaris x64/x86. and HP-UX Itanium (HP-UX 11i v2 B.11.23).

Note: All of the supported platforms (Windows Server 2008, Red Hat Enterprise Linux Release 5.5. and Solaris x64/x86) have built in NTP servers. It is recommended to use the built in NTP server available on the platform.

1-2

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

Overview

Clients

1354 RM-PhM hardware configurations

The 1354 RM-PhM client runs on either Windows Server 2008, Windows XP (Service Pack 2), Red Hat Enterprise Linux Release 5.5., and Solaris x64/x86.

1354

RM-PhM communication

The 1354 RM-PhM uses the SNMP management protocol to communicate with the NEs. The 1354 RM-PhM supports SNMPv1, SNMPv2c and SNMPv3 and the following capabilities: adding and removing new SNMP users, changing SNMP user passwords, and enabling/disabling SNMP users. (See the 1830 PSS User Provisioning Guide).

Note: The default SNMP user cannot be deleted, but can only be disabled.

In normal mode (see 1830 PSS User Provisioning Guide), SNMP requests (without authentication and privacy) are allowed by the NE.

Note: The user (admin level) can change the mode from normal to encrypted during the run time (see 1830 PSS CLI Reference Guide). This will result in an NE restart.

1354

RM-PhM release specifications

Listed below are the release specifications for a 1696 ROADM and 1830 PSS network:

The 1354 RM-PhM manages only 1696 ROADM and 1830 PSS network elements. It does not manage the routers or other communications equipment.

The recommended maximum number of network elements per 1354 RM-PhM is 250. The framework is capable of handling much larger networks. These are not hard-coded limits to the number of network elements; however, the system is only tested to a network size of 250.

The maximum alarm processing throughput is 1000/sec for 10 second burst.

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1

March 2011

1-3

Overview

1354 RM-PhM engineering guidelines

1354

RM-PhM engineering guidelines

The following guidelines can be used to determine the number and location of 1354 RM-PhM servers:

Ensure each ring is managed by a single 1354 RM-PhM and that no 1354 RM-PhM manages more than 250 NEs.

No more than 100 users are permitted at one time.

Ensure that the communications between each client and the server is at least 10 Mb/sec.

Ensure that the communication link between the server and the network is at least 10 Mb/sec.

If possible, ensure that each client has connectivity to each NE. This allows users to perform cut-thru operations to the NEs.

1354

RM-PhM scaling

The 1354 RM-PhM can be scaled to meet demand by considering the following points:

If the server is CPU bound, additional CPUs or faster CPUs may be added. No 1354 RM-PhM upgrades or configuration changes are required.

It is recommended that the 1354 RM-PhM database be installed on a disk that is separate from the operating system and swap files.

If the server is memory bound, additional memory can be added without reconfiguration. The server can be reconfigured by re-installing the 1354 RM-PhM and choosing the upgrade option, or by contacting your customer support representative.

New features introduced in 1354 RM-PhM R8.5.2

1354 RM-PhM Release 8.5.2 supportsAlcatel-Lucent 1830 PSS Release 3.5.1 and includes the following new features

1830 PSS-36 shelf

43SCX4 — 40G Single Port Tunable Mux Coherent (4 client)

11DPM12 support

OTS optical line intrusion support (loss variation monitoring)

Alarm Upon Intrusion Condition

Raising of Alarm on OAMP for OSFP falure events.

1-4

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

2

2 2 System administration Overview Purpose This chapter explains how to start and stop the 1354

2System administration

Overview

Purpose

This chapter explains how to start and stop the 1354 RM-PhM server and client and how to backup and restore the database.

Contents

 

2-3

System requirements

2-3

Interfaces and protocols

2-3

1354

RM-PhM redundant servers

2-7

Installing the 1354 RM-PhM

2-12

2-12

Before you start Installing the 1354 RM-PhM on a Linux or Solaris x86/x64 platform Installing the 1354 RM-PhM on Windows Starting and stopping the server and client

2-12

2-13

2-18

2-24

 

2-24

1354

RM-PhM service wrapper

2-24

Starting the 1354 RM-PhM server on Linux or Solaris x86/x64 Stopping the 1354 RM-PhM server on Linux or Solaris x86/x64 Starting the 1354 RM-PhM server on Microsoft Windows

2-25

2-29

2-31

Stopping the 1354 RM-PhM server on Microsoft Windows Starting a client session Stopping a client session

2-32

2-33

2-35

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

2-1

System administration

Overview

Configuring the 'iptables' firewall Configuring the file transfer properties of the 1354 RM-PhM server Configuring the NTP properties of the 1354 RM-PhM server Configuring the NTP properties of the network elements

2-35

2-36

2-37

2-38

1354

RM-PhM database backup and restore

2-39

 

2-39

1354

RM-PhM database backup

2-40

1354

RM-PhM database restore

2-42

Recovering from file corruption without having to restore from a backup Performing a server switch-over

2-43

2-44

1696

ROADM and 1830 PSS network element database backup and restore

2-45

 

2-45

Performance Monitoring (PM) Archive Setting

2-48

2-48

SNMP Trap Alarm Forwarding

2-50

2-50

RADIUS server and user authentication

2-54

2-54

1354

RM-PhM user management

2-73

 

2-73

NE user management

2-79

2-79

1354

RM-PhM login session settings

2-84

 

2-84

1696

ROADM and 1830 PSS network element software management

2-87

 

2-87

1354

RM-PhM management of Red-C RAMAN Amplifier & EDFA Booster

2-95

 

2-95

2-2

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

System administration

System requirements

System requirements

The recommended system requirements for supporting a 1354 RM-PhM server or client are listed in the release notes which can be obtained from your Alcatel-Lucent representative.

Interfaces and protocols

The 1354 RM-PhM uses the following protocols and ports. These ports must not be in use by any other application (such as an SNMP daemon).

The 1354 RM-PhM has no northbound interfaces.

The following table lists the protocols and ports used for communications between the 1354 RM-PhM and the network elements.

Table 2-1

1354 RM-PhM to network element protocols and ports

Protocol

Action

Destination

Source Port

Application

Stack

Port

RMI

1354 RM-PhM client to server

1099,

Dynamic

client/server

10999,11000,

communication

 

11001,11002,

11003

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1

March 2011

2-3

System administration

Interfaces and protocols

Table 2-1

1354 RM-PhM to network element protocols and ports (continued)

Protocol

Action

Destination

Source Port

Application

Stack

Port

FTP

The 1354 RM-PhM server acts as a FTP client to browse the contents of the NE software server.

20, 21

 

NE software download, NE database backup and restore, archiving of PhM logs

Can be used to transfer 1354 RM-PhM files to be archived on a remote server. This can be performed with:

database

backup files

archived log

 

file

exported

 

service

configuration

files

exported LPT

 

network

configuration

files

SFTP

Same as above but secure

22

 

Same as above but secure

SNMP v1,

Request from 1354 RM-PhM

161

Dynamic

NE /server

v2c

communication

 

Reply from NE

Same as

161

 

request

source

 

Traps from NE

162

161

 

SNMP V3)

Request from 1354 RM-PhM

161

Dynamic

Secure NE /server communication

 

Reply from NE

Same as

161

 

request

source

 

Traps from NE

162

161

 

2-4

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

System administration

Interfaces and protocols

Table 2-1

1354 RM-PhM to network element protocols and ports (continued)

Protocol

Action

Destination

Source Port

Application

Stack

Port

HTTP/

Request from 1354 RM-PhM client

80

Dynamic

Web interface cut-thru

TCP/IP

 

Reply from NE

Same as

80

 

request

source

HTTPS/

Request from 1354 RM-PhM client

80

Dynamic

Web interface cut-thru

TCP/IP

 

Reply from 1354 RM-PhM server

Same as

80

 

request

 

source

HTTP/

Request from 1354 RM-PhM client

80

Dynamic

PhM CPB web server

TCP/IP

 

Reply from NE

Same as

80

 

request

source

Telnet/

Telnet/TCP/IP

23

Dynamic

CLI

cut-thru to NE

TCP/IP

 
 

Reply from NE

Same as

23

 

request

source

SSH

Secure shell

22

Dynamic

CLI

cut-thru to NE

 

Reply from NE

Same as

22

 

request

source

TL1/Telnet/

Telnet/TCP/IP

3083

Dynamic

TL1

cut-thru to NE

TCP/IP

 
 

Reply from NE

Same as

3083

 

request

source

TFTP/

Request from NE

69

Dynamic

TL1

cut-thru to NE

UDP/IP

 
 

Reply from software download or backup and restore server

Same as

69

 

request

source

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1

March 2011

2-5

System administration

Interfaces and protocols

Table 2-1

1354 RM-PhM to network element protocols and ports (continued)

Protocol

Action

Destination

Source Port

Application

Stack

Port

NTP/

Request from NE or 1354 RM-PhM server

123

Dynamic

time and

UDP/IP

synchronization

 

Reply from NTP server

Same as

123

 

request

 

source

Java

Java service wrapper to JVM

31001

32001

PhM process management. Local communications only.

Service

Wrapper

 
 

JVM to Java service wrapper

32001

31001

 
 

Java service wrapper to JVM

31002

32002

PhM web server (CPB) process management. Local communications only.

 

JVM to Java service wrapper

32002

31002

 
 

Java service wrapper to JVM

31003

32003

PhM netpilot process management. Local communications only.

 

JVM to Java service wrapper

32003

31003

 

MySQL

MySQL

3306

dynamic

Request from MySQL client to MySQL server

   

Same as

3306

Response from MySQL server to MySQL client

request

source

 

Telcordia™ NMA®/Transport to network element protocols and ports

The following table lists the protocols and ports used for communications between Telcordia NMA/Transport and NEs.

2-6

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

System administration

Interfaces and protocols

All communication between Telcordia NMA or Transport and the NEs uses:

TCP/IP protocol

the DCN IP addresses of the gateway NEs.

application level TCP gateways to reach non-gateway NEs

Table 2-2

NMA/Transport to GNE protocols and ports

Protocol Stack

Action

Destination Port

Source Port

TL1/TCP/IP

Request from 1354 RM-PhM

3082

Dynamic

 

Reply from NE

Same as request source

3082

TL1/Telnet/TCP/IP

Request from 1354 RM-PhM

3083

Dynamic

 

Reply from NE

Same as request source

3083

1354 RM-PhM redundant servers

The 1354 RM-PhM can be configured with redundant servers to protect against server failure. Server redundancy is an option that is specified during the installation of the 1354 RM-PhM server software.

A 1354 RM-PhM redundant server system consists of two 1354 RM-PhM servers running on two separate computers, as seen in the following figure.

Figure 2-1 1354 RM-PhM redundant servers

following figure. Figure 2-1 1354 RM-PhM redundant servers 1354 RM-PhM Reference Guide Release 8.5.2 3AL61308AAAA Issue

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1

March 2011

2-7

System administration

1354 RM-PhM redundant servers

At a given moment, one of the pair is designated as the active server and the other as the standby server. Only the active server communicates with the network elements and the 1354 RM-PhM clients. Each server has its own local copy of the 1354 RM-PhM database. Database changes to the active database are replicated immediately to the standby database.

To view the current state of server redundancy, choose Admin>PhM Status.

Terminology notes:

The active server is the one that currently has control of the network and is communicating to the network elements. When a 1354 RM-PhM redundancy switch occurs, the other server becomes the active. 1354 RM-PhM server switching is not revertive, meaning the servers do not automatically return to their original designation of active and standby. An active server remains as active until a manual or automatic switch occurs.

When installing each 1354 RM-PhM server in a redundant pair, the user is asked to supply a “Server ID” for that server. This can be either the number “1” or the number “2”. You can specify either Server ID to either server as long as a different Server ID is used for each server. The choice of the Server ID value has no effect on which server becomes active or standby. When installing a redundant pair of servers, the server that comes up first becomes active.

When a redundant 1354 RM-PhM server starts up, it is initially in the standby state. When the server has finished initializing itself, it attempts to communicate with its redundant mate. If it finds that the mate is already in the active state it then remains as standby. If the mate is also in the standby state then a challenge mechanism is used to designate one of the pair as the sole active server and the other to remain as standby. If a server cannot communicate with its mate, it becomes active.

Due to network or configuration problems, it may occur that both servers become active. A common scenario for this is when the network cable for one of the servers is removed. This interrupts the communication of each server with its mate so that they then both assert that they are active. When normal communications are restored, the servers recognize the situation and elect one server as the active, and the other becomes standby. This process is called the “Active Challenge” and proceeds as follows:

1. Each server determines the number of network elements that it is connected to. The one with the higher number becomes active. If the number is the same then:

2. Each server determines the number of active user sessions. The one with the higher number becomes active. If the number is the same then:

3. The server whose name alphabetically proceeds the other becomes active.

2-8

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

System administration

1354 RM-PhM redundant servers

The 1354 RM-PhM servers communicate for the purpose of redundancy at two levels:

server-to-server heartbeat - every 15 seconds (configurable), each 1354 RM-PhM server communicates via TCP/IP with its mate to determine the mate's state and to determine if a state change is warranted. By default, a standby server becomes active if two heartbeats are missed.

database replication - changes to the active server's database are replicated to the standby server's database.

Server switch-over occurs when the standby server loses communication with the active server. Communications loss can occur because the active server has gone down, or because the communication link between the two servers has failed. On switch-over to active, the server registers itself as a trap destination for all network elements. All client sessions on the former active server are shut down. Client sessions must be manually restarted and are directed automatically to the new active server.

On switch-over to standby, the server de-registers itself as a trap destination with all network elements.

Server switch-over can be manually initiated by choosing Admin>PhM Status, and clicking the Switch button.

Managing redundant servers

To view and manage redundant servers, in the 1354 RM-PhM choose Admin>PhM Status. The following window is displayed.

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1

March 2011

2-9

System administration

Figure 2-2 EMS Status window

1354 RM-PhM redundant servers

Figure 2-2 EMS Status window 1354 RM-PhM redundant servers The fields relating to servers and redundancy

The fields relating to servers and redundancy are:

Active Server - the server that is currently acting as the active server

Standby Server - the server that is currently acting as the standby server

Server Configuration - the valid values are:

– stand-alone - for a server that is not configured to be redundant

– Redundant - ACTIVE - indicating that this is the active server in a redundant pair

Server Synchronization State - indicates whether the last heartbeat to the standby server was successful. If the state is “Synchronized” then the field's background is green. Otherwise, it is red. If this field is red then the active server is unable to communicate with the standby 1354 RM-PhM application. Verify that:

– the 1354 RM-PhM is running and operational on the standby server

– communication is possible between the active and standby servers

– the standby server is installed as a redundant server with the active server

– Try to log into the 1354 RM-PhM application using the 1354 RM-PhM client. If you can log in successfully then it indicates that both servers are acting a active since neither can complete a heartbeat to the other. Verify that communications are operational in both directions between the servers.

2-10

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

System administration

1354 RM-PhM redundant servers

Database Synchronization State (Active to Standby) - indicates whether the database replication is operating correctly to propagate changes in the database of the active server to the database of the standby server. If the state is “Synchronized” then the field's background is green. Otherwise, it is red. If this field is red then the active server's database is unable to communicate with the database of the standby 1354 RM-PhM. Verify that:

– The SSH tunnel from the active server to the standby server is installed and operational.

– If the condition persists then perform a “Database Sync”.

Database Synchronization State (Standby to Active) - indicates whether the database replication mechanism is operating correctly to propagate changes from the database of the server currently acting standby server to the database of the active server. This is important because if a switch was to occur then the current standby server would become active. If the state is “Synchronized” then the field's background is green. Otherwise, it is red. Verify that:

– The SSH tunnel from the standby server to the active server is installed and operational.

– If the condition persists then perform a “Database Sync”.

The following actions can be performed:

Back up Database - create a file on the server containing the database contents. See “1354 RM-PhM database backup” (p. 2-40) for information about 1354 RM-PhM database backup and “1354 RM-PhM database restore” (p. 2-42) for information about 1354 RM-PhM database restore.

Switch - to cause the database that is currently active to become standby and the current standby to become the new active server. If the standby is not able to become active then the original active becomes active once more.

Server Shutdown - shut down the server that is currently active. If it is online and operational, the standby becomes active.

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1

March 2011

2-11

System administration Installing the 1354 RM-PhM

Installing the 1354 RM-PhM

The 1354 RM-PhM is installed by an install “wizard” which guides you through the process and prompts you for input as necessary. The files required for installation are transferred to your computer through the file transfer protocol (FTP), or delivered on a DVD. Contact your service representative for the FTP site and user ID and password or for the DVD. This section covers the following procedures:

“Installing the 1354 RM-PhM on a Linux or Solaris x86/x64 platform” (p. 2-13)

“Installing the 1354 RM-PhM on Windows” (p. 2-18)

Before you start

For Solaris systems, install the latest “Recommended Solaris Patch Cluster” which can be found at:

http://sunsolve.sun.com.

2-12

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

System administration

Installing the 1354 RM-PhM

Installing the 1354 RM-PhM on a Linux or Solaris x86/x64 platform

Installing the 1354 RM-PhM on a Linux or Solaris x86/x64 platform

In this release, the 1354 RM-PhM can run on either of the following platforms:

Solaris x64/x86

Linux

HP-UX

There is a single installation package for the 1354 RM-PhM on Linux or Solaris x86/x64 platforms that installs either the 1354 RM-PhM server (includes the server and client software), or only the client software. The installer asks the user to select the desired installation.

Before installing the 1354 RM-PhM, perform the following tasks as necessary:

create account roles as required

Important! Be sure to specify the current installation's install directory when running the installer. The installer must be pointed at the appropriate directory.

To install 1354 RM-PhM on Linux or Solaris x86/x64

1 Log in as the root user.

2 Ensure that the /etc/hosts file on the PhM server machine has a separate line containing the primary physical interface and the hostname of the machine. Otherwise, the PhM server will not be listening on the correct port to receive client connections from remote machines (a local client will still be able to login to the server but not a remote one).

For example, if the PhM server hostname is 1830sim07, the following line: 127.0.0.1 localhost.localdomain localhost 1830sim07 must be changed to:

127.0.0.1 localhost.localdomain localhost

10.3.2.7 1830sim07

in the /etc/hosts file

Here, the physical interface (10.3.2.7) is identified with the hostname on a separate line in the file.

Important! Ensure the "/etc/hosts" file defines the IPv4 loopback address as "127.0.0.1". Failure to do this may cause the PhM application to be unable to connect to the database. The /etc/hosts file should have a line similar to:

127.0.0.1 localhost localhost.localdomain

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1

March 2011

2-13

System administration

Installing the 1354 RM-PhM

Installing the 1354 RM-PhM on a Linux or Solaris x86/x64 platform

It is recommended that your system admin edit the /etc/hosts directly with a text editor rather than use the Red Hat network admin tools.

3 If you are installing from files that have been FTPed to your system, change directory to the directory where the installation files have been FTPed, and ensure that the file setup.sh is executable.

If you are installing from a DVD, copy installation files from the DVD to a directory on the hard drive. After that, change directory to the directory where the installation files have been copied, and ensure that the file setup.sh is executable.

4 Set the DISPLAY environment variable to the name of the machine on which you are working.

5 Execute the setup.bin file. Type:

cd<cdrom> (directory where the cd is located - this may be /cdrom or / media/cdrom)

cd PhM

Note: For Solaris x86 this command is: cd phm

cd

linux (or cd solarisx86)

sh

setup.sh

The installation wizard starts up and guides you through the installation procedure.

6 It is recommended that you accept all of the defaults suggested by the installation wizard, however, you can customize the following items when prompted.

the directory into which to install the 1354 RM-PhM (Do not include a space in the installation directory name or else the installation fails.)

user name and group name to own the installed files

perform a new installation (which removes all existing data) or an upgrade (which preserves existing data)

install a stand-alone server or redundant servers

select the file transfer protocol

specify the TFTP root directory

choose whether or not to display a banner at login time Note: On Linux, the user is not given the option to choose whether or not to display a banner at login time.

2-14

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

System administration

Installing the 1354 RM-PhM

Installing the 1354 RM-PhM on a Linux or Solaris x86/x64 platform

Note: If displayed, the user must press “y” or “yes” (not case sensitive) and the enter key to acknowledge the logon banner before being able to continue with their session. The login banner then displays a message indicating that unauthorized access is prohibited.

If applicable, specify the “Use PhM Administrator Role”.

When all options have been specified, the installation wizard copies the 1354 RM-PhM files into the specified directory.

7 When prompted, click Finish.

The installation wizard exits.

E ND

OF

STEPS

To upgrade the 1354 RM-PhM on Linux or Solaris x86/x64

1 The 1354 RM-PhM upgrade procedure is the same as the installation procedure, except that you choose the upgrade option instead of the new installation option. You do not need to uninstall the 1354 RM-PhM to upgrade. The upgrade backs up the existing installation files.

Important! Be sure to specify the current installation's install directory when running the installer. The installer must be pointed at the appropriate directory.

E ND

OF

STEPS

To cancel or back out from a 1354 RM-PhM upgrade on Linux or Solaris x86/x64

1 You can safely cancel a 1354 RM-PhM upgrade at any time during the upgrade up to and including the window in the following illustration.

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1

March 2011

2-15

System administration

Installing the 1354 RM-PhM

Installing the 1354 RM-PhM on a Linux or Solaris x86/x64 platform

Figure 2-3 1354 RM-PhM installation wizard - last chance to cancel

2-3 1354 RM-PhM installation wizard - last chance to cancel If you click Cancel in this

If you click Cancel in this window, or in any previous window, the installation wizard exits and you can continue to safely use the existing version of the 1354 RM-PhM.

If you click Next in this window, the installation wizard begins to overwrite the existing 1354 RM-PhM with the new version.

2 Begin a new 1354 RM-PhM installation using the installation files/DVD of the previous version.

3 When prompted to choose between a New Installation and an Upgrade, choose New Installation.

4 After the installation has completed, stop the PhM server.

5 Restore the PhM database from the backup file in install_dir_backup2/bin/mysql/data/tropxnmsBackup.sql. For example:

1. cd /opt/PhM_backup2/bin

2-16

1354 RM-PhM Reference Guide Release

8.5.2

3AL61308AAAA Issue 1 March 2011

System administration