alcatel tco suite rel.1.7 for 9400awy r.2.1 v2.1.3 user manual.pdf

8/10/2019 alcatel tco suite rel.1.7 for 9400awy r.2.1 v2.1.3 user manual.pdf

1/234

AlcatelLucent TCO SuiteSWP TCO SUITE Rel.1.7

for 9400AWY R.2.0 V2.0.6 and 9400AWY R.2.1 V2.1.2 & V2.1.3

User Manual3DB 75003 BAAA

Ed.01


2/234

Allrightsreserved.

Passingonandcopy

ingofthis

document,useandcommunicationofitscontentsnot

p

ermittedwithoutwrittenauthorizationfromA

lcatelLucent

2/232 3DB 75003 BAAA Ed.01

USER MANUALFRONT MATTER

SWP TCO SUITE Rel.1.7

i Navigation principles

This manual is delivered to Customers in electronic format only (file Adobe Acrobat pdf) inside the specific

SWP TCO SUITE Rel.1.7 CDROM.

This file can be used both in PC and Unix WS environments or any other environment for which a suitable

Acrobat Reader has been envisaged by Adobe.

In particular take into account that, in order to open correctly this pdf file, the use of Acrobat Reader Version

5.0 at least is mandatory. If opened with previous versions of Adobe Acrobat Reader, incomplete

document views will be produced.

For a comfortable navigation, two hyperlink types are present:

those inside the text window, marked by a blue rectangle around any crossreference to a figure,

table, part, section, chapter, paragraph, numbered list, and page: by clicking such a blue rectangle,

you are led to the referenced component

the bookmarks, present on the left side of the text window. They represent the online handbook

table of contents. Bookmarks can be expanded (clicking on [+]) or reduced (clicking on []). By

clicking on one bookmark, you are led to the referenced part.

WARNING: the bookmark window is not visible if you use Acrobat reader in fullscreen modality.

For further information, refer to Acrobat reader help online.

If printed on paper by Users, it is suggested to divide this manual by numbered separators, for an easier

access to the information herein contained:

CONTENTS SEPARATOR

FRONT MATTER ii Preliminary information

iii Structure of this manual

iv Notes on present edition

V Table of contents

SECTION1 : TCO SUITE DESCRIPTION AND USAGE 1

SECTION2 : APPENDICES 2


3/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

3/2323DB 75003 BAAA Ed.01



ii Preliminary information

a ) Warranty

Any warranty must be referred exclusively to the terms of the contract of sale of the equipment to

which this handbook refers to.

AlcatelLucent makes no warranty of any kind with regards to this manual, and specifically disclaims

the implied warranties of merchantability and fitness for a particular purpose. AlcatelLucent will not

be liable for errors contained herein or for damages, whether direct, indirect, consequential,

incidental, or special, in connection with the furnishing, performance, or use of this material.

b ) Information

The product specification and/or performance levels contained in this document are for information

purposes only and are subject to change without notice. They do not represent any obligation on the

part of AlcatelLucent.

c ) Copyright Notification

The technical information of this manual is the property of AlcatelLucent and must not be copied,

reproduced or disclosed to a third party without written consent.

d ) Safety recommendations

The safety recommendations here below must be considered to avoid injuries on persons and/or

damage to the equipment:

1 ) Service Personnel

Installation and service must be carried out by authorized persons having appropriate technical

training and experience necessary to be aware of hazardous operations during installation andservice, so as to prevent any personal injury or danger to other persons, as well as prevent

damaging the equipment.

2 ) Access to the Equipment

Access to the Equipment in use must be restricted to Service Personnel only.

3 ) Safety Rules

Recommended safety rules are indicated in the NE User Manual (see Tab. 1. on page 14 )

e ) Cautions to avoid equipment damage

Please refer to the NE User Manual (see Tab. 1. on page 14 )

f ) Service Personnel skill

Service Personnel must have an adequate technical background on telecommunications and in

particular on the AlcatelLucent 9400AWY Network Elements specified in Tab. 1. on page 14


4/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

4/232 3DB 75003 BAAA Ed.01



iii Structure of this manual

Information in this manual is divided into the following parts:

a ) Front matter

This part, with general information, and table of contents.b ) SECTION1 : TCO SUITE DESCRIPTION AND USAGEfrom page 11

This section describes the SWP TCO SUITE Rel.1.7 and its most frequently used functions.

c ) SECTION2:APPENDICESfrom page 183

This section describes the less frequently used functions of the SWP TCO SUITE Rel.1.7, and

provides additional information.

d ) Handbook print and assembly instructions

This part (after handbook last page232 ): is not present in the handbook paper copy, if supplied by AlcatelLucent factory.

is present in the pdf file. Customer can use it to print and assembly the handbook in the same

way that can be done by AlcatelLucent factory.

iv Notes on present edition

ED.01 is the first validated and released edition associated to SWP TCO SUITE Rel.1.7.

a ) WARNING ABOUT SWP VERSION:

The SWP TCO SUITE version is written on the SWP CDROM you own, and that contain this

manual

The SWP TCO SUITE Rel.1.7 is meant to be used only with the AlcatelLucent 9400AWY

Network Elements specified in the column NEof Tab. 1. on page 14

In whole Manual (and if not differently specified), for SWP TCO SUITE it is always meant SWP

TCO SUITE Rel.1.7

If you have a SWP TCO SUITE version different from 1.7 , do not use this manual, but that

specific for such a version.

This manual is validated in conjunction with SWP TCO SUITE version 1.7 only. Information

relevant to SWP versions different from 1.7 , if any, must be considered preliminary, subject to

change and without any obligation on the part of AlcatelLucent.


5/234

Allrightsreserved.

Passingonandcopyingofthis

document,useandcommunicationofitsc

ontentsnot

p

ermittedwithoutwrittenauthorizationfromAlcatelLucent

5/2323DB 75003 BAAA Ed.01



v Table of contents

i Navigation principles 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ii Preliminary information 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

iii Structure of this manual 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

iv Notes on present edition 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 1: TCO SUITE DESCRIPTION AND USAGE 11. . . . . . . . . . . . . . . . . . . .

11 SWP TCO SUITE SCOPES AND REQUIREMENTS 13. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.1 SWP TCO SUITE scopes, usability, features, and distribution to Customers 13. . . . .

11.2 SWP TCO SUITE User Manual scope, distribution to Customers, and associated

documentation 14. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11.3 PC requirements to run and install the SWP TCO SUITE 15. . . . . . . . . . . . . . . . . . . . . . .

11.4 PC Administrator privileges requirements to install and deinstall the SWP TCO

SUITE components 16. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12 ITEMS FOR SW DISTRIBUTION TO CUSTOMERS 17. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.1 Items for SW distribution to Customers 18. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.2 SWP TCO SUITE CDROM description 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.2.1 SWP TCO SUITE CDROM part number 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.2.2 SWP TCO SUITE CDROM contents 20. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

12.2.3 Additional requirements for the use of the SWP TCO SUITE 21. . . . . . . . . . . . . . . . . . .

12.3 Notes on SWP CDROM identification, and Product Release Note 22. . . . . . . . . . . . . .

13 CONNECTIONS BETWEEN THE CRAFT TERMINAL AND THE NE, AND SECURITY

POLICY 23. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.1 Types of physical access from the PC to the NE 24. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.2 PCNE network addressing rules 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.2.1 NEs management interfaces 28. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.2.2 NEs local IP address and Ethernet Configuration IP address 28. . . . . . . . . . . . . . . .

13.2.3 NE reachability from the CT 29. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.2.4 Networking scenarios for PC connection to the NEs local IP address 30. . . . . . . . . . .

13.3 Security 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.3.1 Summary of security features 33. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.3.2 Security by operator profile 34. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.3.3 Security by community string 35. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

13.3.4 Security by access lists 36. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14 GETTING STARTED 37. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.1 Preparation of the Craft Terminal based on SWP TCO SUITE 37. . . . . . . . . . . . . . . . . . .


6/234

Allrightsreserved.



ontentsnot

p


6/232 3DB 75003 BAAA Ed.01



14.2 Equipment SW management by SWP TCO SUITE 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.2.1 Flash Card 38. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.2.2 Procedures for the management of the NE software 41. . . . . . . . . . . . . . . . . . . . . . . . . .

14.3 Startup and functions of the TCO SUITE Main Menu screen 46. . . . . . . . . . . . . . . . . . .

14.4 Checks the operator must do before accessing a NE 48. . . . . . . . . . . . . . . . . . . . . . . . . .14.5 Common behavior of NE login, and application logoff, for the NEinteractive

Provisioning Tool and Alarms & Settings 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.5.1 Constraints and preliminary checks 49. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.5.2 NE login procedure 50. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.5.3 Application logoff procedure 54. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.6 Close Current Session 55. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.7 Operational & Maintenance WebEML 56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

14.8 Operational & Maintenance 1320CT 58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

15 PROVISIONING TOOL 59. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16 ALARMS & SETTINGS 65. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16.1 Alarms & Settings overview, startup, and closing 65. . . . . . . . . . . . . . . . . . . . . . . . . . . .

16.2 Alarms & Settings functions 66. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16.2.1 Date & Time Setting 68. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16.2.2 Configuration Setting 69. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16.2.3 Configuration Info 70. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16.2.4 Get Configuration File 75. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16.2.5 Active Alarms 76. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16.2.6 Power Measurement 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16.2.7 Modem Speed 77. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16.2.8 Licence Info 78. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

16.2.9 NAT Option 79. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17 ACCEPTANCE TOOL 83. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17.1 Acceptance Tool scope 84. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17.2 Acceptance Tool start 85. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17.3 Acceptance Tool in NEinteractive modality 86. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17.3.1 Bench setup and startup of the NEinteractive Acceptance Tool 86. . . . . . . . . . . . . .17.3.2 Main functions of the NEinteractive Acceptance Tool 88. . . . . . . . . . . . . . . . . . . . . . . . .

17.3.3 Create Report 90. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

17.4 Acceptance Tool in not NEinteractive modality (offline) 96. . . . . . . . . . . . . . . . . . . . . . .

18 NETO (NETWORK ELEMENT OVERVIEW) 97. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18.1 General on NEtO 98. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18.1.1 NEtO functions 98. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18.1.2 NEtO sessions and constraints 98. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18.2 NE access constraints 98. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18.3 Summary of actions 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18.3.1 Preliminary operations 99. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


7/234

Allrightsreserved.



ontentsnot

p


7/2323DB 75003 BAAA Ed.01



18.3.2 Operations with NEtO 100. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18.4 Details on NEtO screen 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18.4.1 Supervision Function 105. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18.4.2 Supervision and Alarm Synthesis roundshaped icons 105. . . . . . . . . . . . . . . . . . . . . . . .

18.4.3 NEtO screen minimize and restore 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18.4.4 NEtO icon in the tray bar 106. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18.4.5 NE Configuration 107. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18.4.6 Command Buttons 108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18.4.7 How to close the NEtO session 108. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

18.5 NE list management 109. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19 9400AWY WEBEML 111. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.1 How to open the 9400AWY NE WebEML main view 113. . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.2 9400AWY main view organization 114. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.3 View Area 115. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19.3.1 Resource Tree Area and Selection Criteria 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.3.2 Resource Detail Area 116. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.4 Main tool bar 117. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.5 Severity alarm synthesis, and Domain alarm synthesis 118. . . . . . . . . . . . . . . . . . . . . . . .

19.6 Management state control panel 119. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.7 Access state (allow or inhibit NE Craft Terminal access) 120. . . . . . . . . . . . . . . . . . . . . . .

19.7.1 Switching from the OS to the Craft Terminal access state 120. . . . . . . . . . . . . . . . . . . . . .

19.7.2 Switching from the Craft Terminal access state back to the OS access state 120. . . . .

19.8 Introduction to the WebEML menu commands 121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.8.1 Security by operator profile 121. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.8.2 Menu organization 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.8.3 Command button policy 124. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.8.4 Help menu 125. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.8.5 Views menu 126. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.8.6 Configuration menu 130. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.8.7 Diagnosis menu 131. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.8.8 Supervision menu 132. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19.8.9 SW download menu 133. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110 ALARMS MONITOR AND EVENT LOG BROWSER 135. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110.1 Log switch 136. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110.2 Alarms Monitor 136. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110.2.1 Alarms Monitor functions 136. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110.2.2 Alarms Monitor startup for one single NE 137. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110.2.3 Alarms Monitor Overview 137. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110.2.4 Multiple NE Alarms Monitor 141. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110.2.5 Filters menu 142. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110.2.6 File Menu 145. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110.2.7 Printing the alarms and logs 145. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110.2.8 Exporting the alarms and logs 146. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110.2.9 Navigate from AM to USM 147. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110.2.10 Navigate from USM to AM 148. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110.2.11 Shortcut icons 149. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


8/234

Allrightsreserved.



ontentsnot

p


8/232 3DB 75003 BAAA Ed.01



110.3 Event Log Browser (ELB) 151. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110.3.1 ELB scope 151. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110.3.2 ELB startup 151. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

110.3.3 Event Log Table screen 152. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

111 MIB MANAGEMENT 155. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

111.1 Default repository folders of MIB backup files 156. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

111.2 Craft Terminal commands for the management of MIB backup files 156. . . . . . . . . . .

111.3 How to perform the MIB backup 157. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

111.4 How to perform the MIB restore 158. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

111.5 How to remove a MIB backup file from the repository folder 160. . . . . . . . . . . . . . . . .

112 NE SWP UPGRADE 161. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

112.1 Introduction and restrictions 162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

112.2 Case of upgrade to 9400AWY V2.0.6 162. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .



112.5 Only for upgrade to 9400AWY V2.0.6 or V2.1.2: how to perform, by WebEML,

the SWP download to the NE, and its activation 163. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

112.5.1 CT startup, and check for the availability of the SWP to be downloaded 164. . . . . . .

112.5.2 NE login and initial operations (stations A and B) 164. . . . . . . . . . . . . . . . . . . . . . . . . . . .

112.5.3 SW download to the NE (station A) 165. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

112.5.4 Activation of the new Software Package on the NE (station A) 170. . . . . . . . . . . . . . . .112.5.5 Additional operation for upgrade from older versions (station A) 172. . . . . . . . . . . . . . .

112.5.6 Operations on station B 172. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

112.5.7 Functional checks on the radio link (stations A and B) 172. . . . . . . . . . . . . . . . . . . . . . . .

112.5.8 NE data backup (stations A and B) 172. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

112.6 Notes about NE SW downgrade 173. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

113 MANAGEMENT OF THE SECURITY FEATURES 175. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

113.1 Management of security by operator profiles 175. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

113.2 Management of security by community string 178. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

113.3 Management of security by access lists 180. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SECTION 2: APPENDICES 183. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21 APPENDIX A: PREPARATION OF THE CRAFT TERMINAL BASED ON SWP TCO SUITE

185. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21.1 Operations sequence 185. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

21.2 Functions of the other buttons of the Advanced Settings screen 189. . . . . . . . . . . . . . .

21.3 Note about TCO SUITE previous versions 189. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22 APPENDIX B: JRE INSTALLATION AND SWP TCO SUITE STARTUP 191. . . . . . . . . . . . . . .


9/234

Allrightsreserved.



ontentsnot

p


9/2323DB 75003 BAAA Ed.01



22.1 Need for JRE installation 191. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22.2 Standard behavior of SWP TCO SUITE startup 192. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22.3 Manual installation of Java JRE Package 193. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

22.4 Special conditions of SWP TCO SUITE startup 195. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23 APPENDIX C: LLMAN INSTALLATION, CONFIGURATION AND USE 201. . . . . . . . . . . . . . . . .

23.1 Foreword 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23.2 Important warnings 201. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23.3 Procedure summary 202. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23.4 Installation of LLMAN from the SWP TCO SUITE CDROM 203. . . . . . . . . . . . . . . . . . . . .

23.4.1 Operations sequence 203. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23.4.2 Functions and helps available after the LLMAN installation 206. . . . . . . . . . . . . . . . . . . . .

23.5 Installation and configuration of a Virtual Network adapter for LLMAN 207. . . . . . . . . .23.5.1 Foreword 207. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23.5.2 Operations sequence, according to Windows platform 208. . . . . . . . . . . . . . . . . . . . . . . . .

23.6 Lower Layer settings 210. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23.7 Check/set the Network Connections order 212. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23.8 How to start and use the LLMAN application 213. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23.8.1 LLMAN startup with 1320CT 214. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23.8.2 LLMAN startup with WebEML 214. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

23.8.3 Full information regarding the use of the LLMAN application 216. . . . . . . . . . . . . . . . . . .

24 APPENDIX D: ECTEQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE

NETWORK 217. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24.1 Introduction 217. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24.2 Certified equipment 218. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24.3 Connection cables 219. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24.4 Modem setting 220. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24.4.1 Setting of Sportster Flash Modem & 3Com 56K Faxmodem 220. . . . . . . . . . . . . . . . . . . .

24.4.2 TD32 AC Modem setting 222. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24.5 PC laptop Dell Latitude setting 223. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24.6 Setting up the connection 224. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24.7 Changing the ECTequipment connection speed 225. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24.7.1 Introduction 225. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24.7.2 Configuration at NE side 225. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

24.7.3 Configuration at PC side 226. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

25 APPENDIX E: SWP TCO SUITE REL.1.7 DEINSTALLATION 227. . . . . . . . . . . . . . . . . . . . . . . .

26 APPENDIX F: CUSTOMER DOCUMENTATION FEEDBACK 229. . . . . . . . . . . . . . . . . . . . . . . . .


10/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

10/232 3DB 75003 BAAA Ed.01



a ) END OF SECTION


11/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

11/2323DB 75003 BAAA Ed.01

USER MANUAL SWP TCO SUITE Rel.1.7

TCO SUITE DESCRIPTION AND USAGE

SECTION 1: TCO SUITE DESCRIPTION AND USAGE

This section describes the SWP TCO SUITE and its most frequently used functions.

The less frequently used functions of the SWP TCO SUITE are described in the SECTION 2 from page

183

SECTION CONTENT PAGE

INTRODUCTIVE DESCRIPTIONS

Chapter11 SWP TCO SUITE scopes and requirementsIt sums up the scopes of the SWP TCO SUITE, and describes the scopes of thismanual, and the system requirements necessary to run the SWP TCO SUITE

13

Chapter12 Items for SW distribution to CustomersIt describes the items foreseen for the system SW (that resident inside theequipment, and that for the NE management).

17

Chapter 13 Connections between the Craft Terminal and the NE, andsecurity policyIt describes the types of physical access and the rules to observe (network

addresses and security) , to configure and allow the access from the SWP TCOSUITEbased Craft Terminal to the NE.

23

OPERATIVE DESCRIPTIONS

Chapter14 Getting startedIt gives the basic information for the use of the SWP TCO SUITE: preparation ofthe Craft Terminal, summary of equipment SW management procedures, startupand functions of the Main Menu screen.

37

Chapter15 Provisioning toolIt describes in detail the functions of the Main Menus Provisioning Tool.

59

Chapter16 Alarms & SettingsIt describes in detail the Main MenusAlarms & Settings functions. 65

Chapter17 Acceptance ToolIt describes in detail the functions of the Main Menus Acceptance Tool.

83

Chapter18 NEtO (Network Element Overview)

It describes in detail the functions of NEtO97

Chapter19 9400AWY WebEMLIt describes in detail the organization and the functions of the WebEML (Craft

Terminal).

111

OPERATIVE DESCRIPTIONS continues ...


12/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

12/232 3DB 75003 BAAA Ed.01

USER MANUALSWP TCO SUITE Rel.1.7


SECTION CONTENT PAGE

... continues OPERATIVE DESCRIPTIONS

Chapter110 Alarms Monitor and Event Log BrowserIt describes in detail the functions of Alarms Monitor and Event Log Browser

embedded in NEtO application

135

Chapter111 MIB ManagementIt describes how to perform the NE MIB backup and restore operations

155

Chapter112 NE SWP upgradeIt describes how to upgrade to a new SWP any 9400AWY Rel.2.x NE, presentlyrunning with a previous SWP.

161

Chapter113 Management of the security featuresIt describes how to manage the security features of 9400AWY (by operator profile,by community string, and by access lists).

175


13/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

13/2323DB 75003 BAAA Ed.01



11 SWP TCO SUITE SCOPES AND REQUIREMENTS

This chapter sums up the scopes of the SWP TCO SUITE, describes the scopes of this manual, and

describes the PC requirements necessary to run the SWP TCO SUITE

Subject On page

SWP TCO SUITE scopes, usability, features,and distribution to Customers below

SWP TCO SUITE User Manual scope, distribution to Customers, and associated

documentation14

PC requirements to run and install the SWP TCO SUITE 15

PC Administrator privileges requirements to install and uninstall the SWP TCO

SUITE components16

11.1 SWP TCO SUITE scopes, usability, features, and distribution to

Customers

[1] SWP scopes

The main objective of the SWP TCO SUITE is to offer, to Customers working with AlcatelLucent

9400AWY Rel.2.0 and Rel.2.1 radio transmission products, new management features, with no need

to update the NEresident software, or to update the existing NEspecific SWP CDROM.

[2] SWP usability

The use of all features of the SWP TCO SUITE is allowed with the AlcatelLucent 9400AWY Network

Elements running with:

SWP 9400AWY R.2.0 V2.0.6 SWP 9400AWY R.2.1 V2.1.2

SWP 9400AWY R.2.1 V2.1.3

[3] SWP features for 9400AWY V2.0.6 and V2.1.2 NE management

With respect to the NE SW management tools:

embedded TCO Suite

1320CTbased Craft Terminal

included in the:

SWP 9400AWY R.2.0 V2.0.6 CDROM

SWP 9400AWY R.2.1 V2.1.2 CDROM

the SWP TCO SUITE provides the following features:

full Microsoft Windows Vistatsupport

new fullJava NEtO (Network Element Overview), replacing the functions of the NES (Network

Element Synthesis)

new fullJava WebEML (Craft Terminal), replacing the functions of the 1320CT

N.B. to avoid problems to the users of the NE SW management tools included in the

NEspecific SWP CDROM listed above, this new WebEML maintains the same

structure (main view, menu bar, screens organization, parameter name and position,

etc) with a few differences, described in this manual.


14/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

14/232 3DB 75003 BAAA Ed.01



[4] SWP features for 9400AWY V2.1.3 NE management

Differently from 9400AWY NE running with V2.0.6 or V2.1.2, the 9400AWY NE running with V2.1.3

has no 1320CTbased Craft Terminal management tools.

The 9400AWY NE running with V2.1.3 can be managed only by the SWP TCO SUITE.

[5] SWP distribution to Customers

The SWP TCO SUITE is a standalone product delivered on a specific CDROM.

11.2 SWP TCO SUITE User Manual scope, distribution to Customers, and

associated documentation

[1] SWP TCO SUITE User Manual scope

The specific NE User Manual (Tab. 1. on page 14 ) gives all information regarding:

the NE, from system and hardware points of view

the NE SW management tools included in the specific SWP NE CDROM (only for

V2.0.6 and V2.1.2), supplied with the NE equipment

The scope of this SWP TCO SUITE User Manual is to provide, in a way as concise as possible,only the description of features of the SWP TCO SUITEs NE SW management tools, that are

different from those of the SWP NE CDROM cited above (with some exceptions).

WARNING: this SWP TCO SUITE User Manual:

does not give detailed information regarding the NE

does not include detailed information that is already present in the specific NE User

Manual, and for which there are no operative differences at NE SW management level.

Therefore, to retrieve NEspecific information, or any other information referenced to in the

following, this SWP TCO SUITE User Manual must be always used together with the specific

NE User Manual having the P/N specified in Tab. 1. on page 14 .

[2] SWP TCO SUITE User Manual distribution to Customers

This manual is delivered to Customers in electronic format only (file Adobe Acrobattpdf) inside the

specific SWP TCO SUITE CDROM.

[3] Associated documentation

Tab. 1. 9400AWY NEs and associated User Manuals

NE and Manual P/N of the NE User Manual

9400AWY R.2.0 V2.0.6 User Manual 3DB06687LAAA

9400AWY R.2.1 V2.1.2 User Manual 3DB16142GAAA

9400AWY R.2.1 V2.1.3 User Manual 3DB16142JAAA

Notes:

The specific NE User Manual is present in a documentation CDROM automatically delivered

to Customer together with the equipment it refers to (one copy for each terminal).

In some cases, depending on the Edition of the NE User Manual, the cross references to it,

specified in this manual (section_name, chapter_name, paragraph_name), could not

correspond exactly to the referenced part. In this case, you can find the cross referenced

information in another part of the specific NE User Manual.

in the following of this manual, when a generic reference to the NE User Manual is specified,

you must obviously use that corresponding to the specific NE you are working with.

For further information on the 9400AWY documentation set and additional documents (if any), please

refer to the documentation CDROM containing the specific NE User Manual.


15/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

15/2323DB 75003 BAAA Ed.01



11.3 PC requirements to run and install the SWP TCO SUITE

To run and install (if required) all functions of the SWP TCO SUITE, a PC meeting these requirements is

necessary:

1 ) HW Configuration (minimum requirements)

CPU: Pentium III 850 MHz

RAM: 512 Mbytes (1 Gbytes suggested for Windows Vista)

Hard Disk space: 4 Gbytes

Display Resolution: 1024x768 pixel

CDROM Drive: 24X

Communication Interfaces:

Ethernet Card 10/100 Mbits/sec is mandatory, if local / remote communication withNEs Ethernet port or TCP/IP network is required (if both connections are required

contemporarily, two Ethernet Cards are needed)

RS232C serial port (9.6 to 57.6 Kbits/sec) is suggested, if local communication

with NEs ECT serial port (Finterface) is required.

N.B. In alternative, for the usage of the NEs Finterface with any PC having no

RS232 serial port (but obviously with USB ports available), it is possible

to use an USB to RS232 adapter (see Tab. 2. on page 25 )

Refer to para.13.1 from page 24 , for details on how to connect the PC to the NEs, by local

or remote connection.

2 ) Windows Versions

Windows 2000 SP4

Windows XP till SP2 (Professional Edition only)

Windows Vista

WARNING 1: only one Windows version can be present in the same PC

WARNING 2: for all Windows versions, it is mandatory to deactivate the Firewall installed

WARNING 3: restriction for Windows Vista:

With Windows Vista, the SWP download for NE upgrade cannot use

LLMAN (therefore the NEs F interface must not be used for the SWP

download)

For user convenience, this restriction is repeated on pages 162 and 164


16/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

16/232 3DB 75003 BAAA Ed.01



3 ) Additional SW requirements

Java Runtime Environment (JRE): JRE 6 update 3

N.B. the necessary version is included in the SWP CDROM

Browser supported:

for Windows 2000 and XP:

Microsoft Internet Explorer 6.0 (6.0.2900.2180 SP1+)

or Microsoft Internet Explorer 7.0 (7.0 .5730.11C0+)

for Windows Vista:

Microsoft Internet Explorer 7.0 (7.0 .5730.11C0+)

for Windows 2000, XP, and Vista:

Mozilla Firefox v2.x starting from v2.0.0.12

N.B. Opera browser is not supported in any version.

WARNING: it is mandatory to manually disable system and browser proxy

configurations prior to use both NEinteractive Provisioning Tool and

Alarms & Settings (web server) functions; otherwise, the IP connection

from the PCs web server to the NE cannot take place.

Used browser window should be at least as larger as 1024x768

4 ) PC settings for its use inside the TCP/IP network

N.B. You have nothing to do, if you are employing a PC already configured for TCP/IP

communication (e.g. already used for any AlcatelLucent 1320CTbased or

NEtObased applications).

These settings include the following types of configuration:

PC hostname

Communication Protocol : TCP/IP (if not automatically configured)

IP address

IP mask

These settings depend on the Windows version employed. Refer to its documentation, to know

how to perform them.

11.4 PC Administrator privileges requirements to install and deinstall the

SWP TCO SUITE components

The PC Administrator privileges are necessary to install:

the Java Runtime Environment (JRE), automatically or manually: see Appendix B on page 191

the AlcatelLucentproprietary LLMAN and related Tiny Tools: see Appendix C on page 201

The PC Administrator privileges are also necessary to deinstall them: see Appendix Eon page 227


17/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

17/2323DB 75003 BAAA Ed.01



12 ITEMS FOR SW DISTRIBUTION TO CUSTOMERS

This chapter describes the items foreseen for the system SW (that resident inside the equipment, and that

for the NE management):

Subject On page

Items for SW distribution to Customers 18

SWP TCO SUITE CDROM description 20

SWP TCO SUITE CDROM part number 20

SWP TCO SUITE contents 20

Additional requirements for the use of the SWP TCO SUITE 21

Notes on SWP CDROM identification, and Product Release Note 22


18/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

18/232 3DB 75003 BAAA Ed.01



12.1 Items for SW distribution to Customers

The scope of this paragraph is to compare the SW products present in the various CDROMs:

9400AWY R.2.0 V2.0.6 CDROM

9400AWY R.2.1 V2.1.2 CDROM

9400AWY R.2.1 V2.1.3 CDROM

SWP TCO SUITE CDROM

[1] NEspecific equipmentresident software

The software necessary for the system working (equipmentresident software) is present in the

Flash Carddelivered with the equipment, and inserted in the IDU MAIN unit.

Refer to para.14.2.1 on page 38 for details.

[2] NEspecific software components for Equipment Controller and Peripheral Units of

9400AWY (IDU and ODU)

These SW components are used whenever you have a:

9400AWY R.2.0 NE running with SWP version < V2.0.6, and you want to upgrade it to SWP

version V2.0.6 , by means of the SW downloadfunction





These NEspecific SW components:

are present respectively in the:

9400AWY R.2.0 V2.0.6 CDROM

9400AWY R.2.1 V2.1.2 CDROM

9400AWY R.2.1 V2.1.3 CDROM

are not present in the SWP TCO SUITE CDROM

[3] Additional software products

JRE(Java Runtime Environment), that is present, with the necessary specific version, in the

following CDROMs:

9400AWY R.2.0 V2.0.6 CDROM

9400AWY R.2.1 V2.1.2 CDROM

SWP TCO SUITE CDROM

JRE is automatically installed in the PC at first insertion of the CDROM.

N.B. the JREversion present in the SWP TCO SUITE CDROM is higher than that of JRE

present in the other CDROMs listed above.

N.B. the 9400AWY R.2.1 V2.1.3 CDROM does not contain any JREcomponent.


19/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

19/2323DB 75003 BAAA Ed.01



LLMAN (Lower Layer MANager), that must be explicitly installed in the PC, whenever the use

of the NEs local F interface (RS232 serial interface) is required. This software product is present

in the following CDROMs:

9400AWY R.2.0 V2.0.6 CDROM

9400AWY R.2.1 V2.1.2 CDROM

SWP TCO SUITE CDROM

N.B. the LLMANversion present in the SWP TCO SUITE CDROM is higher than that of

LLMAN present in the other CDROMs. Moreover, it is also higher than that of

LLMAN present in the SWP TCO SUITE Rel.1.6 CDROM.

[4] NE management SW tools

a ) contained in theSWP TCO SUITE CDROM: refer to para.12.2.2 on page 20

b ) contained in the NEspecific SWP CDROM :

they are the:

embedded TCO Suite

1320CTbased Craft Terminal

present respectively in the:

9400AWY R.2.0 V2.0.6 CDROM

9400AWY R.2.1 V2.1.2 CDROM

The installation and use of these NE management SW tools is explained in the specific NE User

Manual (Tab. 1. on page 14 )

N.B. the 9400AWY R.2.1 V2.1.3 CDROM does not contain any NE management SWtool.


20/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

20/232 3DB 75003 BAAA Ed.01



12.2 SWP TCO SUITE CDROM description

12.2.1 SWP TCO SUITE CDROM part number

The P/N of theSWP TCO SUITE CDROM, containing this manual, is written on the CDROM itself you

own.

For SWP CDROM identification, refer to para.12.3 on page 22

12.2.2 SWP TCO SUITE CDROM contents

The following software products are contained in theSWP TCO SUITE CDROM:

[1] Main Menu

The Main Menu is the starting point of this SWP, with the screen depicted in Fig. 10. on page 47.

The functions available are:

Provisioning Tool : it starts a wizard tool, which allows to configure completely and easily one

9400AWY V2.0.6 or V2.1.2 or V2.1.3 NE, in not NEinteractive (offline), or in NEinteractive

(online) modality. This tool allows also to modify a configuration created previously, and to get

the configuration from a running NE.

Alarms & Settings : it starts a NEinteractive function, allowing the user to login a NE through

the use of the NE web server via a generic Internet browser, to monitor the status of NE alarms

and to get and/or set some NEs parameters

Start of one NEtO session : see point [2] below

Start of 1320CT : it is meant for old 9400AWY NEs backward compatibility only

Acceptance Tool : it is meant to be used in the commissioning phase; it replaces the functions

previously covered by the document TRS (Test Report Sheets) available as Pdf, Word or Excelfile; the main advantage is that the Acceptance Tool can take many parameters directly from

the NE

Advanced Settings : functions to install the SWP in PC

[2] NEtO

NEtO (Network Element Overview) is the starting point to make a full supervision and control of the

most recent AlcatelLucent radio transmission 9400AWY NEs: 9400AWY Rel.2.0 from version

V2.0.6, and 9400AWY Rel.2.1 from version V2.1.2.

N.B. NEtO is used also for the AlcatelLucent radio transmission 9500MPR NEs (all versions),

but you must be aware that the SWP TCO SUITE Rel.1.7 does not manage any versionof 9500MPR NEs.

It allows to perform the following operations on one NE:

start its supervision

run the Alarm Monitor function

perform its login, launching the WebEML application specific for the NE type and version ( see

following point [3] )


21/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

21/2323DB 75003 BAAA Ed.01



[3] WebEML (fullJava Local and Remote Craft Terminal)

The WebEML is used for the complete NE management, allowing the dialogue between the Craft

Terminal and the NE.

Each NE type and version has its own WebEML SW package.

TheSWP TCO SUITE contains the WebEML SW packages for:

9400AWY V2.0.6

9400AWY V2.1.2

9400AWY V2.1.3

[4] Additional software products

JRE(Java Runtime Environment), that is automatically installed in the PC at first insertion of

theSWP TCO SUITE CDROM

LLMAN (Lower Layer MANager), that must be explicitly installed in the PC, whenever the use

of the NEs local F interface (RS232 serial interface) is required.

N.B. as specified in point [2] on page 18 , theSWP TCO SUITECDROM does not containthe NEspecific software componentsfor NE upgrading. If necessary, they must be

retrieved from the NEspecific SWP CDROM.

12.2.3 Additional requirements for the use of the SWP TCO SUITE

a ) NE software state

the NE type must be ULS, and the SWP active version in the NEs Flash Card must be:

V2.0.6(if 9400AWY R.2.0)

V2.1.2 or V2.1.3 (if 9400AWY R.2.1)

This check can be done making the NE supervision by NEtO, then reading the NE type (ULS)

and version, as shown in Fig. 46. on page 107

any 9400AWY NE, that must be accessed in local or remote way by the SWP TCO SUITE

applications, must have already a valid local IP address and a valid Ethernet Configuration

IP address [ see para.13.2.2 on page 28 ], and such addresses must be known by the

Operator.

b ) Security

Operations allowed by the SWP TCO SUITEs SW tools are submitted to a security control, described

in para.13.3 on page 33

c ) Operator skills

the Operator shall be familiar with the use of personal computers in WINDOWSenvironment

[versions specified in point 2 ) on page 15 ], internally to which the Network Elements

application software operates.

the Operator must be familiar with all the functionalities of the 9400AWY R.2.0 and/or

9400AWY R.2.1 equipment.

furthermore, for a number of configuration applications, the operator shall be aware of some

specifications of the International Standard Organization (ISO) and of the standards applied tothe Synchronous Digital Hierarchy (SDH) (CCITT Recommendations).


22/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

22/232 3DB 75003 BAAA Ed.01



12.3 Notes on SWP CDROM identification, and Product Release Note

These notes apply both to the SWP TCO SUITE CDROMs, and to the SWP 9400AWY V2.x.x

CDROMs:

[1] SWP CDROM identification

each SWP is distributed by means of a specific SWP CDROM

a SWP is identified by its Denomination, P/N (Part Number) and CS (Change Status), that

are printed on the CDROMs label

a SWP with new Version Level, providing main features in addition to those of the previous

Version Level SWP, is distributed by means of a SWP CDROM having new Denomination,

new P/N (Part Number), and CS restarting from 01

a SWP patch version, if any, is created to correct SW bugs, and/or to add minor features, and

is distributed by means of a SWP CDROM, that can be identified:

by the same P/N of the former CDROM, but with an incremented CS number (e.g.

CS=02 instead of previous CS=01)

or by a new P/N, and CS restarting from 01

[2] Product Release Note

the Product Release Note contains information not strictly necessary for Customers (like the

SW Package Identification data, the list of SW Package Components, the list of ECT SW

SubComponents, the description of new features and modifications, restrictions and known

problems, etc.)

the Product Release Note is neither contained in the SWP CDROM nor automaticallydelivered to Customers

the Product Release Note is available only on specific request to your AlcatelLucent local

dealer, specifying the SWP TCO SUITE CDROM P/N and ICS (edition) printed on the SWP

CDROM itself (see point [1] above).


23/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

23/2323DB 75003 BAAA Ed.01



13 CONNECTIONS BETWEEN THE CRAFT TERMINAL AND THE NE,

AND SECURITY POLICY

This chapter describes the types of physical access and the rules to observe (network addresses and

security) , to configure and allow the access from the SWP TCO SUITEbased Craft Terminal to the NE.

Subject On page

Types of physical access from the PC to the NE 24

NEs F interface (RS232 serial interface) on IDU MAIN unit 25

NEs Ethernet interface on IDU MAIN unit 26

NEs pointtopoint radio interface and NMS (TMN connections) rings and

chains27

PCNE network addressing rules 28

NEs management interfaces 28

NEs local IP address and Ethernet Configuration IP address 28

NE reachability from the CT 29

Networking scenarios for PC connection to the NEs local IP address 30

Security 33

Summary of security features 33

Security by operator profile 34

Security by community string 35

Security by access lists 36


24/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

24/232 3DB 75003 BAAA Ed.01



13.1 Types of physical access from the PC to the NE

The physical access to a 9400AWY NE, for its management by the PC running the SWP TCO SUITE

software , can be on the following interfaces of the 9400AWY NE:

F interface (RS232 serial interface), see point [1] on page 25

Ethernet management interface, see point [2] on page 26 Pointtopoint radio interface and NMS (TMN connections) rings and chains, see point [3] on page

27

Notes for all types of access:

a ) Depending on physical interface, the use of some SW management tools has some restrictions.

b ) LCT and RCT

The specification of LCT (Local Craft Terminal) and RCT (Remote Craft Terminal), in following tables

Tab. 3. to Tab. 6. ,is relevant to the CT characterization for the supervised NE.

This implies different command feasibility behaviors, as described in para.19.8.1 from page 121

(some commands cannot be executed by RCT).

c ) Max number of contemporary accesses to the same NE

For the NE access by:

Main Menu NEinteractive functions (online Provisioning Tool and Alarms & Settings), up

to five Ethernet user connections are supported at the same time on a single NE

WebEML (through NEtO) and OS, refer to para.18.2 on page 98

9400AWY R.2.1 IDU MAIN unit

F InterfaceManagement

Ethernet Interface

9400AWY R.2.0 IDU MAIN unit

NMS Interface

(G703 + V11)

Radio Interface

(IDUODU cable)

Radio Interface

(IDUODU cable)

NMS Interface

(V11)

NMS Interface

(G703)F Interface

Management

Ethernet Interface

Fig. 1. Physical interfaces for the 9400AWY NE management

Comparison with the NE management software tools of the:

9400AWY R.2.0 V2.0.6 CDROM,

and of the 9400AWY R.2.1 V2.1.2 CDROM

with the SWP TCO SUITE, there is no need of manual interface customization for alternative use of

Finterface or Ethernetinterface

with the SWP TCO SUITE, the access to the NE requires always the NE address specification, even

in case of PCNE interconnection by Finterface


25/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

25/2323DB 75003 BAAA Ed.01



[1] NEs F interface (RS232 serial interface) on IDU MAIN unit

WARNING 1: for the use of the F interface, the LLMAN installation and configuration must be

performed, as described in the AppendixC on page201

PUBLIC SWITCHED

TELEPHONE NETWORK

PCs RS232 interface RS232 cable

PCs modem

F

NE supervised through F interface

Modem

Refer to the Appendix D on page 217 , to know how to implement the connection via the public switched

telephone network.

Tab. 2. Typical AlcatelLucent RS232 cable and adapter

Cable / Adapter P/N Notes

RS232 cable 1AB054120027 Standard RS232 cable

USB to RS232 adapter 1AF11294AA**

In addition to the standard RS232 cable, for the

usage of the NEs Finterface with any PC havingno RS232 serial port (but obviously with USB

ports available)

Tab. 3. Allowed NE management SW tools on NEs F interface

SW management toolAllowed on

Finterface

NEs TCP/IP address

required for NE access

LCT /

RCT

SWP TCO SUITE Main Menu

NEinteractive functions:

Provisioning Tool

Alarms & Settings

Acceptance Tool

NO

SWP TCO SUITEWebEML YES NO LCT

Fig. 2. Connections between PC and NE through NEs F Interface


26/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

26/232 3DB 75003 BAAA Ed.01



[2] NEs Ethernet interface on IDU MAIN unit

ETH

SWITCH

IP NETWORKPC Ethernet interface

crossconnect Ethernet cable

Eth

NE supervised through Ethernet interface

normal (direct) Ethernet cable

Tab. 4. Typical AlcatelLucent Ethernet cablesThe suggested AlcatelLucent Ethernet cables are:

type length (m) P/N

1 3CC52141AAAA

normal (direct) cable 5 3CC52141ABAA

15 3CC52141ACAA

1 3CC52142AAAA

crossconnec ca e5 3CC52142ABAA

Tab. 5. Allowed NE management SW tools on NEs Ethernet interface

SW management toolAllowed on

Eth.interface

NEs TCP/IP address

required for NE access

LCT /

RCT



Provisioning Tool

Alarms & Settings

Acceptance Tool (N.B.)

YES YES

SWP TCO SUITEWebEML YES YES RCT

N.B. for details on NE access in case of Acceptance Tooluse, refer to chapter17 from page83

Fig. 3. Ethernet connections between PC and NE


27/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

27/2323DB 75003 BAAA Ed.01



[3] NEs pointtopoint radio interface and NMS (TMN connections) rings and chains

ODU ODU

STATION A STATION B

9400AWY RADIO LINK

Access to Station B from PC

connected locally to Station A

NE supervised through Radio interface

Local PC

IP NETWORK Remote PC

PUBLIC

SWITCHED

TELEPHONE

NETWORK

PC connected

locally to Ethernet

or F interface of

STATION A

PC connected remotely to Ethernet or F

interface of STATION A

Access to Station B from PC

connected remotely to Station A

FEth

NMSEth

NMS

NE supervised through NMS

(G703V11)

NMS

Eth

Eth

NMS

NMS

Eth

NE supervised through Ethernet

interface

NE supervised through NMS

(G703V11)

Other NE

Other NE

Other NE

TMN system

Refer to the specific NE User Manual (Tab. 1. on page 14 ) for details on the NMS connections.

Tab. 6. Allowed NE management SW tools on NEs Radio interface and NMS rings and chains

SW management tool

Allowed on

interface of

STATION A

NEs TCP/IP

address required

for NE access

LCT /RCT



F NO

rov s on ng oo

Alarms & Settings

Acceptance Tool (N.B.)Ethernet YES YES

F

eEthernet

N.B. for details on NE access in case of Acceptance Tooluse, refer to chapter17 from page

83

Fig. 4. Access to NE through NEs radio Interface and NMS rings and chains


28/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

28/232 3DB 75003 BAAA Ed.01



13.2 PCNE network addressing rules

This paragraph describes the network address rules that must be observed to allow a PC (running the

SWP TCO SUITE) the access to one or more 9400AWY NEs.

13.2.1 NEs management interfaces

For its management by SWP TCO SUITE tools, the 9400AWY NE has:

one Ethernet management interface, which is used to access the NE, and that is identified by its local

IP address and Ethernet Configuration IP address, defined in para.13.2.2 below

one pointtopoint TMNRF interface toward the other NE of the radio link

and one selectable pointtopoint TMNV11 or TMNG703 interface toward another colocated NE

all pointtopoint interfaces (TMNRF, and TMNV11 or TMNG703) are unnumbered and borrow

the IP address from the local IP address

13.2.2 NEs local IP address andEthernet Configuration IP address

As delivered from AlcatelLucent Factory, the NEs addresses:

local IP address, used to identify uniquely the NE inside the Transmission Management Network

(TMN)

and the Ethernet Configuration IP address, used to identify uniquely the NEs Ethernet

management interface inside the TCP/IP network

are both set at default value 10.0.1.2, as shown in screen below (one of the steps of the Full

Configuration Proceduredescribed in chapter 15 from page 59 )

These values can be maintained only until the NE remains disconnected from the TCP/IP network and

from the TMN, and must be changed to have them different from those of the other NEs present in the

accessible network. Their setting is foreseen in the commissioning phase; for details, refer to the specific

NE User Manual (Tab. 1. on page 14 )

In the commissioning phase, you can define the local IP address and Ethernet Configuration IPaddress:

with the same value (suggested solution)

or with different values


29/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

29/2323DB 75003 BAAA Ed.01



WARNING: if such NE addresses are different, they must not belong to the same subnetwork, as in

following correct example:

local IP address = 151.98.96.221

and Ethernet Configuration IP address = 151.98.97.232

with IP Mask = 255.255.255.0

N.B. in the case these NE addresses are different:

the local IP address is that to be always used to access the NE by NEtO application

the Ethernet Configuration IP address is that to be always used to access the NE

by the NEinteractive Provisioning Tool and Alarms & Settings (web server)

functions.

13.2.3 NE reachability from the CT

[1] Foreword

The CT must be able to reach the NE, through one of the local or remote connections described onprevious pages 25 to 27

The access rules are different according to the type of application used; if you access a NE from your

PC:

1 ) through the Finterface, and by the NEtO application, the NEs local IP address must be

always used, and there are no network constraints

2 ) through the Ethernet interface, and by the NEtO application, for which the NEs local IP

address must be always used, it is necessary to build a networking relationship, according to

the PCNE connection scenario, between:

the IP address of the PC the local IP address of the NE

the Ethernet Configuration IP address of the NE

as described in para.13.2.4 from page 30

3 ) through the Ethernet interface, and by the NEinteractive Provisioning Tool and Alarms &

Settings applications (web server operations), any problems between the IP addresses of the

PC and the NE are solved automatically, choosing Local or Remote in the application start

screen, as described in para.14.5 from page 49

[2] How to check the NE reachability from the CT

N.B. Usually, these operations have to be performed once only (i.e., whenever you have not

done them previously for the specific NE). This check is not necessary in case of PCNE

connection through the Finterface.

To make this check, open the Windows Command Prompt application and execute the command:

ping NE_address

Verify the connection, then close the command window.

Note: in case the local IP address and Ethernet Configuration IP address are different from each

other, perform this check for both.


30/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

30/232 3DB 75003 BAAA Ed.01



13.2.4 Networking scenarios for PC connection to the NEs local IP address

These scenarios describe the networking address configurations necessary to allow a PC (running the

SWP TCO SUITE) to access a 9400AWY NE through its local IP address.

N.B. Address values are given as examples. Moreover:

address_value/24 means with IP mask = 255.255.255.0

In this case, if the address_value is that of the subnet 192.168.1.0, all addresses 192.168.1.0

to 192.168.1.255 are stated as belonging to the subnet

address_value/32 means with IP mask = 255.255.255.255

In this case, if the address_value is that of the subnet 192.168.1.0, only the address

192.168.1.0 is stated as belonging to the subnet

[1] NE local access by one PC

the CT accesses the NE using the local IP address; the SNMP traps are sent by NE using the

local IP address as source IP address

it is possible to configure the Ethernet Configuration IP address with the samevalue used for

local IP address

the subnet must be defined both on the PC and the NE

Eth

9400AWY NE


subnet = 10.0.1.0/24.2

.1

10.0.1.1

[2] NE local and remote access by one PC, with Default Gateway or Static Route, or OSPF

in this scenario, to reach the local and remote NEs by their own local IP address, the PC must

be configured with a Default Gateway or Static Route having as gateway the Ethernet

Configuration IP address of the local NE (192.168.1.1 in the following examples)

at the same time the CT must be reachable by the remote NE using a Static Route on the remote

NE, or enabling OSPF on both local and remote NEs


31/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

31/2323DB 75003 BAAA Ed.01



First example

Eth

9400AWY NE


subnet = 192.168.1.0/24.2

.1

Set:

Default Gateway = 192.168.1.1

or:

Static Route 10.0.1.0/24 Gateway 192.168.1.1

10.0.1.1

10.0.1.2

9400AWY NE


LOCAL NE REMOTE NE

Second example

Eth

9400AWY NE


subnet = 192.168.1.0/24.2

.1

Set:


or:

Static Route 176.16.1.0 /24 Gateway 192.168.1.1

and:

Static Route 10.0.1.0/24 Gateway 192.168.1.1

10.0.1.1

172.16.1.1

9400AWY NE


LOCAL NE REMOTE NE

WARNING: if both the local IP address and the Ethernet Configuration IP address of the local

NE belong to the same subnetwork, the local IP address of the local and remote

NEs must never belong to the same subnetwork. E.g. the following scenario does notwork:

Eth

9400AWY NE


.2

.1

10.0.1.1 reachable

10.0.1.2 unreachable

9400AWY NE


LOCAL NE REMOTE NE

subnet = 10.0.1.0/24


32/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

32/232 3DB 75003 BAAA Ed.01



[3] NE access by more than one PC

to allow more than one PC to access the NEs in the network, theirlocal IP address, and the

IP addresses of the PCs, must belong to different subnets

Eth

9400AWY NE


subnet = 192.168.1.0/24

.2

.1

Set:


or:

Static Route 10.0.1.0/24Gateway 192.168.1.1

10.0.1.1

10.0.1.2

Eth

9400AWY NE

local IP address = 10.0.1.2 10.0.1.1

10.0.1.2

.1

.2

subnet = 192.168.2.0/24

Set:


or:

Static Route 10.0.1.0/24Gateway 192.168.2.1

[4] Notes on OSPF routing

the OSPF routing protocol can be activated on each pointtopoint interface (TMNRF,

TMNV11, and TMNG703) and on the Ethernet Configuration IP address interface

the 9400AWY NE can act as ABR (Area Border Router) managing a maximum of 4 areas

(Backbone + 3 areas). It is possible to assign different OSPF areas to each pointtopoint

interface, and to the Ethernet Configuration IP address interface

an OSPF area can be configured as Stub Area. Configuring a Stub Area reduces the topological

database size and reduces the memory requirements for NE inside that area for NEs that are

not ABR

the OSPF Area Identifier can take a form similar to an IP address A.B.C.D

the Area 0 or Backbone has Area ID 0.0.0.0

the Area ID has not any correlation with the IP address of the interface that belongs to that area

enabling OSPF, static routing information configured on one NE are automatically redistributed

as OSPF external routes inside the OSPF areas active on this NE

static routings are not redistributed inside the OSPF areas configured as Stub Area

if OSPF is enabled on NEs, static routes, if needed, have to be added only on the NE reached

by Ethernet (called Gateway NE)

in case of CT not directly connected to the Gateway NE, the Ethernet interface of this NE must

be reachable in order to make the software download working


33/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

33/2323DB 75003 BAAA Ed.01



an example of OSPF Area configuration is shown in following figure:

9400AWY NElocal IP address

10.0.1.3

10.0.1.1

10.0.1.2

10.0.1.3

Eth

9400AWY NE

TMNG703

orV11

TMN

RF

local IP address

10.0.1.1local IP address

10.0.1.2

9400AWY NE

OSPF Area 1 OSPF Area 2

.2

.1

subnet = 192.168.1.0/24


OSPF Area 0

13.3 Security

13.3.1 Summary of security features

The aim of the security features of 9400AWY system is to protect the NE from all undesired accesses.

The following security features are available:

usable on AWY 2.0.6, 2.1.2, and 2.1.3:

Security by operator profile, described in detail in para.13.3.2 on page 34

This is a standard feature, allowing the NE access only through a UserName and Password set,

valid for the specific NE.

As delivered from AlcatelLucent factory, the Flash Card contains only one default

Administrator UserName and Password set.

usable on AWY 2.1.3 only:

Security by community string, described in detail in para.13.3.3 on page 35

This feature is associated to the NEtO applications, and allows to assign to the NE a community

string. An user who wants to access such a NE, must provide this community string before

before to supervise and login the NE.

Security by access lists, described in detail in para.13.3.4 on page 36

The NE management operations that can be done by means of the SWP TCO SUITE are

grouped in different services: snmp, http, ftp and telnet.

The feature Security by access listsallows to write an access list table, for each one of the

services stated above, containing the IP addresses allowed to perform that specific service.

Both these security features are optional.

For both these security features, the Flash Card (as delivered from AlcatelLucent factory) contains

default parameters, corresponding to security feature not active.

N.B. The management of the security features is described in chapter 113 on page 175


34/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

34/232 3DB 75003 BAAA Ed.01



13.3.2 Security by operator profile

[1] UserName and Password

To login a NE, whichever the physical access method, you must have a UserName and Password

set, valid for the specific NE.

UserName and Password are requested by a prompt screen like this:

At first installation time, one default Administrator user is available only, with (lower case):

UserName= initial

Password = initialing

Otherwise, use the Login information the Administrator has assigned you.

In the login procedure, the username is displayed on the screen, while the cleartext password is

not displayed on the screen. After 3 times of consecutive unsuccessful NE login attempts, the CTNE

logical interface closes the login procedure. To access the NE, a new login action must be performed.

WARNING: The change of the password of this Administrator user is strongly suggested, to be

done at the end of all commissioning phases. Further this initial user, the

Administrator is allowed to create/delete users belonging to the predefined profiles.

[2] Login profiles

Each user (identified by a UserName and a Password) is associated to one of the predefined profiles.

The predefined profiles are the following:

Administrator (both for OS interface and CT/MibBrowser interface)

The Administrator can do everything on the NE.

In particular, only the Administrator can manage the security features summed up inpara.13.3.1 on page 33 :

add/remove users, besides changing own password and those of all users

set/change/remove the community string

set/change/remove the access lists

export the access lists from a NE, and import them in another NE.

Constructor(only for OS interface)

This Operator can do everything on the NE also to access to the Manager List bypassing the

RM checks, but for this Operator some administration functions are disabled: for example the

Constructorcannot add or remove operators, and cannot do backup and restore.

This user profile is related only to OS system and so not stored on MIB NE.


35/234

Allrightsreserved.

Passingonandcopy

ingofthis


p


lcatelLucent

35/2323DB 75003 BAAA Ed.01



Operator(both for OS interface and CT/MibBrowser interface)

This Operator has in charge the operation at network level, not at radio site.

This Operator can change her/his own user password.

This Operator cannot manage network configuration, only for NTP Configuration, due to

dangerous isolation of NE.

This Operator cannot either do quick configuration, or backup/restore, or restart NE. Also the

provisioning of equipment is not supported, as well the operations requiring the operator

presence on the radio site.

CraftPerson (only for CT/MibBrowser interface)

This Operator has in charge the installation and the maintenance at radio site.

This Operator can do everything on NE system, but cannot manage the security features, but

can change her/his own user password.

viewer (both for OS interface and CT/MibBrowser interface)

This Operator can only explore the NE.

This Operator can change her/his own user password.

[3] Operations allowed to Login profiles, according to functions, access, and local access status

NEinteractive Provisioning Tool(described in point [2] from page 61 )

allowed to the Administrator, CraftPersonandOperator

denied to the Viewer

Alarms & Settings(described in chapter 16 from page 65 )

according to Tab. 7. on page 67

NEinteractiveAcceptance Tool(described in chapte

alcatel tco suite rel.1.7 for 9400awy r.2.1 v2.1.3 user manual.pdf

Documents