alcatel tco suite rel.1.7 for 9400awy r.2.1 v2.1.3 user manual(1)

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

i Navigation principlesThis 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 componentAll rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

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:

CONTENTSFRONT MATTER ii Preliminary information iii Structure of this manual iv Notes on present edition V Table of contents SECTION 1 : TCO SUITE DESCRIPTION AND USAGE SECTION 2 : APPENDICES

SEPARATOR

1 2

SWP TCO SUITE Rel.1.7

USER MANUAL FRONT MATTER 3DB 75003 BAAA Ed.01

2 / 232

ii Preliminary informationAll rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

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 and service, 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



3 / 232

iii Structure of this manualInformation in this manual is divided into the following parts: a) b) c) Front matter This part, with general information, and table of contents. SECTION 1 : TCO SUITE DESCRIPTION AND USAGE from page 11 This section describes the SWP TCO SUITE Rel.1.7 and its most frequently used functions. SECTION 2: APPENDICES from page 183 This section describes the less frequently used functions of the SWP TCO SUITE Rel.1.7, and provides additional information. Handbook print and assembly instructions This part (after handbook last page 232 ): 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.All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

d)

iv Notes on present editionED.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 NE of 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.



4 / 232

v Table of contentsAll rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

i Navigation principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ii Preliminary information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii Structure of this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv Notes on present edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SECTION 1: TCO SUITE DESCRIPTION AND USAGE . . . . . . . . . . . . . . . . . . . .11 SWP TCO SUITE SCOPES AND REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 SWP TCO SUITE scopes, usability, features, and distribution to Customers . . . . . 11.2 SWP TCO SUITE User Manual scope, distribution to Customers, and associated documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.3 PC requirements to run and install the SWP TCO SUITE . . . . . . . . . . . . . . . . . . . . . . . 11.4 PC Administrator privileges requirements to install and deinstall the SWP TCO SUITE components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 ITEMS FOR SW DISTRIBUTION TO CUSTOMERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.1 Items for SW distribution to Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2 SWP TCO SUITE CDROM description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.1 SWP TCO SUITE CDROM part number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.2 SWP TCO SUITE CDROM contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12.2.3 Additional requirements for the use of the SWP TCO SUITE . . . . . . . . . . . . . . . . . . . 12.3 Notes on SWP CDROM identification, and Product Release Note . . . . . . . . . . . . . . 13 CONNECTIONS BETWEEN THE CRAFT TERMINAL AND THE NE, AND SECURITY POLICY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.1 Types of physical access from the PC to the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2 PCNE network addressing rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2.1 NEs management interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2.2 NEs local IP address and Ethernet Configuration IP address . . . . . . . . . . . . . . . . 13.2.3 NE reachability from the CT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.2.4 Networking scenarios for PC connection to the NEs local IP address . . . . . . . . . . . 13.3 Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.3.1 Summary of security features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.3.2 Security by operator profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.3.3 Security by community string . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.3.4 Security by access lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 GETTING STARTED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.1 Preparation of the Craft Terminal based on SWP TCO SUITE . . . . . . . . . . . . . . . . . . . USER MANUAL FRONT MATTER 3DB 75003 BAAA Ed.01

2 3 4 4 1113 13 14 15 16 17 18 20 20 20 21 22

23 24 28 28 28 29 30 33 33 34 35 36 37 37


5 / 232

14.3 Startup and functions of the TCO SUITE Main Menu screen . . . . . . . . . . . . . . . . . . . 14.4 Checks the operator must do before accessing a NE . . . . . . . . . . . . . . . . . . . . . . . . . . 14.5 Common behavior of NE login, and application logoff, for the NEinteractive Provisioning Tool and Alarms & Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.5.1 Constraints and preliminary checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.5.2 NE login procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.5.3 Application logoff procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.6 Close Current Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.7 Operational & Maintenance WebEML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.8 Operational & Maintenance 1320CT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 PROVISIONING TOOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 ALARMS & SETTINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.1 Alarms & Settings overview, startup, and closing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2 Alarms & Settings functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2.1 Date & Time Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2.2 Configuration Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2.3 Configuration Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2.4 Get Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2.5 Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2.6 Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2.7 Modem Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2.8 Licence Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16.2.9 NAT Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 ACCEPTANCE TOOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.1 Acceptance Tool scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.2 Acceptance Tool start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.3 Acceptance Tool in NEinteractive modality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.3.1 Bench setup and startup of the NEinteractive Acceptance Tool . . . . . . . . . . . . . . 17.3.2 Main functions of the NEinteractive Acceptance Tool . . . . . . . . . . . . . . . . . . . . . . . . . 17.3.3 Create Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17.4 Acceptance Tool in not NEinteractive modality (offline) . . . . . . . . . . . . . . . . . . . . . . . 18 NETO (NETWORK ELEMENT OVERVIEW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.1 General on NEtO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.1.1 NEtO functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.1.2 NEtO sessions and constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.2 NE access constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.3 Summary of actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.3.1 Preliminary operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SWP TCO SUITE Rel.1.7

46 48 49 49 50 54 55 56 58 59 65 65 66 68 69 70 75 76 77 77 78 79 83 84 85 86 86 88 90 96 97 98 98 98 98 99 99


6 / 232

All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

14.2 Equipment SW management by SWP TCO SUITE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.2.1 Flash Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.2.2 Procedures for the management of the NE software . . . . . . . . . . . . . . . . . . . . . . . . . .

38 38 41

18.3.2 Operations with NEtO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

18.4 Details on NEtO screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.4.1 Supervision Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.4.2 Supervision and Alarm Synthesis roundshaped icons . . . . . . . . . . . . . . . . . . . . . . . . 18.4.3 NEtO screen minimize and restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.4.4 NEtO icon in the tray bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.4.5 NE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.4.6 Command Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18.4.7 How to close the NEtO session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

105 105 105 106 106 107 108 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.8.1 Security by operator profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.8.2 Menu organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.8.3 Command button policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.8.4 Help menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.8.5 Views menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.8.6 Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.8.7 Diagnosis menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.8.8 Supervision menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19.8.9 SW download menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 121 124 124 125 126 130 131 132 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 USER MANUAL SWP TCO SUITE Rel.1.7 FRONT MATTER 3DB 75003 BAAA Ed.01

7 / 232

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.3 Case of upgrade to 9400AWY V2.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 112.4 Case of upgrade to 9400AWY V2.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.5.1 CT startup, and check for the availability of the SWP to be downloaded . . . . . . . 112.5.2 NE login and initial operations (stations A and B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.5.3 SW download to the NE (station A) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.5.4 Activation of the new Software Package on the NE (station A) . . . . . . . . . . . . . . . . 112.5.5 Additional operation for upgrade from older versions (station A) . . . . . . . . . . . . . . . 112.5.6 Operations on station B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.5.7 Functional checks on the radio link (stations A and B) . . . . . . . . . . . . . . . . . . . . . . . . 112.5.8 NE data backup (stations A and B) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 164 164 165 170 172 172 172 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 SWP TCO SUITE Rel.1.7 USER MANUAL FRONT MATTER 3DB 75003 BAAA Ed.01

8 / 232


110.3 Event Log Browser (ELB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110.3.1 ELB scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110.3.2 ELB startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110.3.3 Event Log Table screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

151 151 151 152

22.1 Need for JRE installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.8.1 LLMAN startup with 1320CT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.8.2 LLMAN startup with WebEML . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.8.3 Full information regarding the use of the LLMAN application . . . . . . . . . . . . . . . . . . . 213 214 214 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.7.2 Configuration at NE side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.7.3 Configuration at PC side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 225 225 226

25 APPENDIX E: SWP TCO SUITE REL.1.7 DEINSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . 227 26 APPENDIX F: CUSTOMER DOCUMENTATION FEEDBACK . . . . . . . . . . . . . . . . . . . . . . . . . 229



9 / 232

a)

10 / 232END OF SECTIONAll rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent


3DB 75003 BAAA Ed.01

USER MANUAL FRONT MATTER


SECTION 1: TCO SUITE DESCRIPTION AND USAGEThis 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 INTRODUCTIVE DESCRIPTIONS Chapter 11 SWP TCO SUITE scopes and requirements It sums up the scopes of the SWP TCO SUITE, and describes the scopes of this manual, and the system requirements necessary to run the SWP TCO SUITE Chapter 12 Items for SW distribution to Customers It describes the items foreseen for the system SW (that resident inside the equipment, and that for the NE management). Chapter 13 Connections between the Craft Terminal and the NE, and security policy It 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. OPERATIVE DESCRIPTIONS Chapter 14 Getting started It gives the basic information for the use of the SWP TCO SUITE: preparation of the Craft Terminal, summary of equipment SW management procedures, startup and functions of the Main Menu screen. Chapter 15 Provisioning tool It describes in detail the functions of the Main Menus Provisioning Tool. Chapter 16 Alarms & Settings It describes in detail the Main MenusAlarms & Settings functions. Chapter 17 Acceptance Tool It describes in detail the functions of the Main Menus Acceptance Tool. Chapter 18 NEtO (Network Element Overview) It describes in detail the functions of NEtO Chapter 19 9400AWY WebEML It describes in detail the organization and the functions of the WebEML (Craft Terminal). OPERATIVE DESCRIPTIONS continues ... 13 PAGE

17

23

37

59 65 83 97

111

USER MANUAL TCO SUITE DESCRIPTION AND USAGE 3DB 75003 BAAA Ed.01


11 / 232

SECTION CONTENT ... continues OPERATIVE DESCRIPTIONS Chapter 110 Alarms Monitor and Event Log Browser It describes in detail the functions of Alarms Monitor and Event Log Browser embedded in NEtO application Chapter 111 MIB Management It describes how to perform the NE MIB backup and restore operations Chapter 112 NE SWP upgrade It describes how to upgrade to a new SWP any 9400AWY Rel.2.x NE, presently running with a previous SWP. Chapter 113 Management of the security features It describes how to manage the security features of 9400AWY (by operator profile, by community string, and by access lists).

PAGEAll rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

135

155

161

175



12 / 232

11 SWP TCO SUITE SCOPES AND REQUIREMENTSAll rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

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 SWP TCO SUITE scopes, usability, features,and distribution to Customers SWP TCO SUITE User Manual scope, distribution to Customers, and associated documentation PC requirements to run and install the SWP TCO SUITE PC Administrator privileges requirements to install and uninstall the SWP TCO SUITE components On page below 14 15 16

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. 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 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

[2]

[3]

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 Vistat support 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.



13 / 232

[4]

[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 Acrobatt pdf) inside the specific SWP TCO SUITE CDROM. Associated documentation Tab. 1. 9400AWY NEs and associated User Manuals NE and Manual 9400AWY R.2.0 V2.0.6 User Manual 9400AWY R.2.1 V2.1.2 User Manual 9400AWY R.2.1 V2.1.3 User Manual P/N of the NE User Manual 3DB06687LAAA 3DB16142GAAA 3DB16142JAAA

[3]

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. SWP TCO SUITE Rel.1.7 USER MANUAL TCO SUITE DESCRIPTION AND USAGE 3DB 75003 BAAA Ed.01

14 / 232


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.

11.3 PC requirements to run and install the SWP TCO SUITEAll rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

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: RAM: Hard Disk space: Pentium III 850 MHz 512 Mbytes (1 Gbytes suggested for Windows Vista) 4 Gbytes

Display Resolution: 1024x768 pixel CDROM Drive: 24X

Communication Interfaces: Ethernet Card 10/100 Mbits/sec is mandatory, if local / remote communication with NEs 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



15 / 232

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 Opera browser is not supported in any version. 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.All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

N.B.

WARNING:

4)

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

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 componentsThe 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 E on page 227



16 / 232

12 ITEMS FOR SW DISTRIBUTION TO CUSTOMERSAll rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

This chapter describes the items foreseen for the system SW (that resident inside the equipment, and that for the NE management): Subject Items for SW distribution to Customers SWP TCO SUITE CDROM description SWP TCO SUITE CDROM part number SWP TCO SUITE contents Additional requirements for the use of the SWP TCO SUITE Notes on SWP CDROM identification, and Product Release Note On page 18 20 20 20 21 22



17 / 232

12.1 Items for SW distribution to CustomersThe scope of this paragraph is to compare the SW products present in the various CDROMs: [1] 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 NEspecific equipmentresident software The software necessary for the system working (equipmentresident software) is present in the Flash Card delivered 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 download function 9400AWY R.2.1 NE running with SWP version < V2.1.2, and you want to upgrade it to SWP version V2.1.2 , by means of the SW download function 9400AWY R.2.1 NE running with SWP version < V2.1.3, and you want to upgrade it to SWP version V2.1.3 , by means of the SW download functionAll rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

These NEspecific SW components: are present respectively in the: [3] 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

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 JRE version present in the SWP TCO SUITE CDROM is higher than that of JRE present in the other CDROMs listed above. the 9400AWY R.2.1 V2.1.3 CDROM does not contain any JRE component.

N.B.



18 / 232


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: N.B. 9400AWY R.2.0 V2.0.6 CDROM 9400AWY R.2.1 V2.1.2 CDROM SWP TCO SUITE CDROM the LLMAN version 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) b) contained in the SWP TCO SUITE CDROM : refer to para.12.2.2 on page 20 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 SW tool.



19 / 232

12.2 SWP TCO SUITE CDROM description12.2.1 SWP TCO SUITE CDROM part number The P/N of the SWP 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 the SWP 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 Excel file; the main advantage is that the Acceptance Tool can take many parameters directly from the NE Advanced Settings : functions to install the SWP in PCAll rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

[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 version of 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] )



20 / 232

[3]All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

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. The SWP 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 the SWP 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. as specified in point [2] on page 18 , the SWP TCO SUITE CDROM does not contain the NEspecific software components for NE upgrading. If necessary, they must be retrieved from the NEspecific SWP CDROM.

N.B.

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 WINDOWS environment [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 to the Synchronous Digital Hierarchy (SDH) (CCITT Recommendations).



21 / 232

12.3 Notes on SWP CDROM identification, and Product Release NoteThese 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 01All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

[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 automatically delivered 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).



22 / 232


13 CONNECTIONS BETWEEN THE CRAFT TERMINAL AND THE NE, AND SECURITY POLICYThis 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 Types of physical access from the PC to the NE NEs F interface (RS232 serial interface) on IDU MAIN unit NEs Ethernet interface on IDU MAIN unit NEs pointtopoint radio interface and NMS (TMN connections) rings and chains PCNE network addressing rules NEs management interfaces NEs local IP address and Ethernet Configuration IP address NE reachability from the CT Networking scenarios for PC connection to the NEs local IP address Security Summary of security features Security by operator profile Security by community string Security by access lists On page 24 25 26 27 28 28 28 29 30 33 33 34 35 36



23 / 232

13.1 Types of physical access from the PC to the NEThe 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 27All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

Notes for all types of access: a) b) Depending on physical interface, the use of some SW management tools has some restrictions. 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). 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 Radio Interface (IDUODU cable)

c)

9400AWY R.2.1 IDU MAIN unit

Management Ethernet Interface

F Interface

NMS Interface (G703 + V11) NMS Interface (V11) Radio Interface (IDUODU cable)

9400AWY R.2.0 IDU MAIN unit

Management Ethernet Interface

F Interface

NMS Interface (G703)

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



24 / 232


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 Appendix C on page 201

PUBLIC SWITCHED TELEPHONE NETWORK

PCs modem

NE supervised through F interface F

Modem PCs RS232 interface RS232 cable

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 RS232 cable P/N 1AB054120027 Notes Standard RS232 cable In addition to the standard RS232 cable, for the usage of the NEs Finterface with any PC having no RS232 serial port (but obviously with USB ports available)

USB to RS232 adapter

1AF11294AA**

Tab. 3. Allowed NE management SW tools on NEs F interface SW management tool SWP TCO SUITE Main Menu NEinteractive functions: Provisioning Tool Alarms & Settings Acceptance Tool SWP TCO SUITE WebEML Allowed on Finterface NEs TCP/IP address required for NE access LCT / RCT

NO

YES

NO

LCT

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



25 / 232

[2]

NEs Ethernet interface on IDU MAIN unit IP NETWORKAll rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

PC Ethernet interface

NE supervised through Ethernet interface ETH SWITCH Eth

crossconnect Ethernet cable normal (direct) Ethernet cable Tab. 4. Typical AlcatelLucent Ethernet cables The suggested AlcatelLucent Ethernet cables are: type length (m) 1 normal (direct) cable 5 15 1 crossconnect cable 5 P/N 3CC52141AAAA 3CC52141ABAA 3CC52141ACAA 3CC52142AAAA 3CC52142ABAA

Tab. 5. Allowed NE management SW tools on NEs Ethernet interface SW management tool SWP TCO SUITE Main Menu NEinteractive functions: Provisioning Tool Alarms & Settings Acceptance Tool (N.B.) SWP TCO SUITE WebEML N.B. Allowed on Eth.interface NEs TCP/IP address required for NE access LCT / RCT

YES

YES

YES

YES

RCT

for details on NE access in case of Acceptance Tool use, refer to chapter 17 from page 83 Fig. 3. Ethernet connections between PC and NE



26 / 232


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

9400AWY RADIO LINKPC connected locally to Ethernet or F interface of STATION A

STATION AODU

STATION BODU Access to Station B from PC connected locally to Station A

Local PC

Access to Station B from PC connected remotely to Station A NE supervised through Radio interface NMS Eth

NMS Eth F

TMN system

IP NETWORK

Remote PC

PUBLIC SWITCHED TELEPHONE NETWORK

NMS NE supervised through NMS (G703V11) Eth Other NE Eth NE supervised through Ethernet interface NMS Other NE

PC connected remotely to Ethernet or F interface of STATION A

NMS NE supervised through NMS (G703V11) Eth Other NE 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 SWP TCO SUITE Main Menu NEinteractive functions: Provisioning Tool Alarms & Settings Acceptance Tool (N.B.) SWP TCO SUITE WebEML N.B. Allowed on interface of STATION A F NO NEs TCP/IP address required for NE access LCT / RCT

Ethernet F Ethernet

YES

YES

YES

YES

RCT

for details on NE access in case of Acceptance Tool use, refer to chapter 17 from page 83 Fig. 4. Access to NE through NEs radio Interface and NMS rings and chains



27 / 232

13.2 PCNE network addressing rulesThis 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 addressAll rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

13.2.2 NEs local IP address and Ethernet 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 Procedure described 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 IP address: with the same value (suggested solution) or with different values SWP TCO SUITE Rel.1.7 USER MANUAL TCO SUITE DESCRIPTION AND USAGE

28 / 232

3DB 75003 BAAA Ed.01

WARNING:All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

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 151.98.97.232 and Ethernet Configuration IP address = 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 on previous 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 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

2)

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.



29 / 232

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 subnetAll rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

[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 same value used for local IP address the subnet must be defined both on the PC and the NE local IP address = 10.0.1.1 10.0.1.1 9400AWY NE Eth .1 subnet = 10.0.1.0/24 .2

[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



30 / 232

First exampleAll rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

LOCAL NE 10.0.1.1 10.0.1.2 local IP address = 10.0.1.1 9400AWY NE

REMOTE NE local IP address = 10.0.1.2 9400AWY NE

Eth .1 .2 subnet = 192.168.1.0/24

Set: Default Gateway = 192.168.1.1 or: Static Route 10.0.1.0/24 Gateway 192.168.1.1 Second example LOCAL NE 10.0.1.1 172.16.1.1 local IP address = 10.0.1.1 9400AWY NE 9400AWY NE Eth .1 .2 subnet = 192.168.1.0/24 REMOTE NE local IP address = 172.16.1.1

Set: Default Gateway = 192.168.1.1 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 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 not work: LOCAL NE 10.0.1.1 reachable 10.0.1.2 unreachable local IP address = 10.0.1.1 9400AWY NE 9400AWY NE Eth .1 .2 subnet = 10.0.1.0/24 REMOTE NE local IP address = 10.0.1.2



31 / 232

[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 local IP address = 10.0.1.1 9400AWY NE Eth .1 subnet = 192.168.1.0/24 .2 local IP address = 10.0.1.2 9400AWY NE Eth .1 subnet = 192.168.2.0/24 .2 10.0.1.1 10.0.1.2All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

10.0.1.1 10.0.1.2

Set: Default Gateway = 192.168.1.1 or: Static Route 10.0.1.0/24 Gateway 192.168.1.1

Set: Default Gateway = 192.168.2.1 or: Static Route 10.0.1.0/24 Gateway 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



32 / 232


an example of OSPF Area configuration is shown in following figure: 9400AWY NE local IP address 10.0.1.3 9400AWY NE local IP address 10.0.1.1 TMN G703 or V11 TMN RF OSPF Area 2 9400AWY NE local IP address 10.0.1.2

Eth .1

OSPF Area 1 subnet = 192.168.1.0/24

.2 OSPF Area 0 Default Gateway = 192.168.1.1

10.0.1.1 10.0.1.2 10.0.1.3

13.3 Security13.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 lists allows 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



33 / 232

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:All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

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 in para.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 Constructor cannot 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.



34 / 232


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, CraftPerson and Operator denied to the Viewer Alarms & Settings (described in chapter 16 from page 65 ) according to Tab. 7. on page 67 NEinteractive Acceptance Tool (described in chapter 16 from page 65 ) allowed to the Administrator and CraftPerson denied to the Operator and Viewer WebEML (described in chapter 19 from page 111 ) refer to para.19.8.1 on page 121

13.3.3 Security by community string N.B. available on AWY 2.1.3 NEs only

This feature is associated to the NEtO applications only. As delivered from AlcatelLucent factory, the Flash Card contains the community string = private as default value. When NEtO is opened, it contains always community string = private as default value. This condition corresponds to security by community string not active. The NE Administrator, if modifies the NEs own community string (as described in para.113.2 on page 178 ), must communicate this string to the users who should be authorized to supervise and login the NE. Any of these users, to be authorized to access such a NE, must provide this community string before to supervise and login the NE, as described on page 101 For the system behaviors when the community string of a NE is modified, while an user has a NEtO session opened on the same NE (supervision, WebEML, and Alarms Monitoring), refer to points 2 ) and 3 ) on page 179



35 / 232

13.3.4 Security by access lists N.B. available on AWY 2.1.3 NEs onlyAll rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

This feature is associated to all SWP TCO SUITE applications. The NE management operations that can be done by means of the SWP TCO SUITE are performed using the following different services: snmp: all NEinteractive operations performed accessing the NE by NEtO ( chapter 18 on page 97 ) all NEinteractive operations performed accessing the NE starting from the Main Menu screen ( Fig. 10. on page 47 ): NEinteractive Provisioning Tool ( point [2] on page 61 ) Alarms & Settings ( chapter 16 on page 65 ) all NEinteractive operations corresponding to: downloading a file from the NE (e.g. the Get Configuration File described in para.16.2.4 on page 75 ) uploading a file to the NE (e.g. the Configuration Setting described in para.16.2.2 on page 69 ) telnet is the protocol used when the access to the NE is performed by NEtO from a Remote Craft Terminal [ point b ) on page 24 ]

http :

ftp

:

telnet

Note that, to perform some operations, more than one of the stated services are used. For example: both snmp and telnet are used to login a NE by NEtO from a Remote Craft Terminal both http and ftp are used to download a file from a NE using the Alarms & Settings functions.

In the Flash Card, for each one of the stated services, there is an Access List table, as shown in Fig. 74. on page 180 In the Flash Card, as delivered from AlcatelLucent factory, all these four Access List tables contain 0.0.0.0 as default value in the IP Address and in the IP Mask fields. This condition corresponds to security by access lists not active. The NE Administrator, if wants to limit the use of one of the stated services to a specific list of managers, must insert and enable their IP Address and their IP Mask into the corresponding Access List table, as described in para.113.3 on page 180 After this setting, any user, whose PCs IP Address is not listed in an Access List table, will not be authenticated for the use of the corresponding service (for the specific NE).



36 / 232

14 GETTING STARTEDAll rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

This chapter gives the basic information for the use of the SWP TCO SUITE. Subject Preparation of the Craft Terminal based on SWP TCO SUITE Equipment SW management by SWP TCO SUITE Flash Card Procedures for the management of the NE software Startup and functions of the SWP TCO SUITE Main Menu screen Checks the operator must do before accessing a NE Common behavior of NE login, and application logoff, for the NEinteractive Provisioning Tool and Alarms & Settings Constraints and preliminary checks NE login procedure Application logoff procedure Close Current Session Operational & Maintenance WebEML Operational & Maintenance 1320CT On page below 38 38 41 46 48 49 49 50 54 55 56 58

14.1 Preparation of the Craft Terminal based on SWP TCO SUITEIf not yet done, the first thing you must do is to copy the TCO SUITE software from the CDROM to your PC , as described in the Appendix A on page 185 , even if some functions can be run directly from the CDROM. N.B. The functions that can be run directly from the TCO SUITE CDROM, without performing the copy procedures of the Appendix A , are: Provisioning Tool, see Chapter 15 on page 59 Alarms & Settings, see Chapter 16 on page 65 Acceptance Tool, see Chapter 17 on page 83 Operational & Maintenance 1320CT, see para.14.8 on page 58



37 / 232

14.2 Equipment SW management by SWP TCO SUITEThis paragraph introduces the information regarding the equipment software management. 14.2.1 Flash Card A Flash Card is always plugged into the IDU Main board; it contains the whole Equipment programs and configuration data. 14.2.1.1 Flash Card types Various types of Flash Cards are available; each of them allows a fixed max system throughput [i.e. the max number of user interfaces, in terms of equivalent Mb/s traffic, and the supported modulation (4QAM and/or 16QAM) ]. Each type of Flash Card is identified by a Logistical Item P/N and by a licence information. Please refer to the specific NE User Manual ( Tab. 1. on page 14 ) for details on the available types of Flash Card and their identification. WARNING: the Flash Cards of 9400AWY R.2.0 and of 9400AWY R.2.1 are not interchangeable.All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

14.2.1.2 Flash Card content The Flash Card contains the whole Equipment programs and configuration data, as shown in Fig. 5. below: a) Case of AWY 2.0.6 and 2.1.2 Fixed Data (Licence info) SOFTWARE KEY SW COMMIT VERSION (ACTIVE) MIB SW STANDBY VERSION (not active)

SW instances

NE Data

b)

Case of AWY 2.1.3 Fixed Data Licence info Licence Data LICENCE STRING & LICENCE KEY SW COMMIT VERSION (ACTIVE) MIB SW STANDBY VERSION (not active) SERIAL NUMBER

SW instances

NE Data Fig. 5. Flash Card content



38 / 232


Licence information 1) Case of AWY 2.0.6 and 2.1.2: fixed licence information The licence information can be read by the CT command Supervision % SW Key (see para.19.8.8 on page 132 ), which opens the screen of Fig. 6. below, or by the Licence Info screen of the Alarms & Settings function (see para.16.2.8 on page 78 ): the SW Key number indicates the licence information. the SW Key code indicates the fixed max system throughput. In this case, you can change the max system throughput only replacing physically the Flash Card with another type (another P/N, allowing the desired system throughput).

Fig. 6. Flash Card licence information (case of AWY 2.0.6 and 2.1.2) 2) Case of AWY 2.1.3: dynamically changeable licence information The licence information can be read by the CT command Supervision % SW Key (see para.19.8.8 on page 132 ), which opens the screen of Fig. 7. below, or by the Licence Info screen of the Alarms & Settings function (see para.16.2.8 on page 78 ): the Serial Number is that physically associated to the Flash Card the Licence String indicates the fixed max system throughput the Set Licence Key field indicates the licence, associated to the Flash Cards Serial Number, and implicitly defines its current Licence String. In this case you can change the max system throughput in two ways: replacing physically the Flash Card with another type (another P/N, allowing the desired system throughput), as in the case 1 ) above or asking AlcatelLucent a new Licence Key pattern, associated to the Flash Cards Serial Number, then introducing it (by copy and paste) in the Set Licence Key field, at last clicking the button Apply.

Fig. 7. Flash Card licence information (case of AWY 2.1.3)



39 / 232

[2]

SW instances The SW COMMIT VERSION is that used by the system. The SW STANDBY VERSION instance is created the first time a SW download from CT to the NE is performed. As supplied by AlcatelLucent factory, the SWPversion downloaded in Factory is the most recently released at the date of Flash Card delivery to the Customer, so that the SW instances present in the flash card are: the SW COMMIT VERSION and the SW STANDBY, loaded with the SW version immediately previous (maintenance release) with respect to the COMMIT one.All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent

[3]

NE data N.B. as shown in Fig. 5. on page 38 , differently from SW instances, NE data are present as a single instance in the Flash Card. Base configuration It is defined by the Flash Cards licence information. It means that you can change the system configuration data only within its throughput limits. The licence information can be modified as described in previous point [1] on page 39 MIB The MIB (Management Information Base) contains all NE configuration data. As supplied by AlcatelLucent factory, the NE configuration data are set to default values.

a)

b)


USER MANUAL TCO SUITE

alcatel tco suite rel.1.7 for 9400awy r.2.1 v2.1.3 user manual(1)

Documents

3com 56k faxmodem

khz rx frequency

swp tco suite

pcmodem serial

disabled auto

tco suite

desired system

java runtime