Académique Documents
Professionnel Documents
Culture Documents
7813151823252838 GHz shorthaul low/medium capacity digital microwave radio links 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
User Manual
3DB 16142 EAAA Ed.02
Navigation principles
This manual is delivered to Customers in electronic format only (file Adobe Acrobat pdf) inside the specific 9400AWY Customer Documentation CDROM: 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. Most of them 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
QUICK GUIDE TABLE OF CONTENTS LIST OF FIGURES AND TABLES SECTION 1 : SYSTEM DESCRIPTION SECTION 2 : NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL SECTION 3 : INSTALLATION AND COMMISSIONING SECTION 4 : MAINTENANCE AND UPGRADE SECTION 5 : APPENDICES
SEPARATOR
1 2 3 4 5
The standard Customer Documentation for 9400AWY Rel.2.1 SWP version V2.1.1 is in the English language and is distributed to Customers only by the following CDROM: CDROM TITLE DCP 9400AWY 2.1 V2.1.1 CDROM Technical Code 3DB 16142 ACAA
It contains, in electronic format (ADOBE ACROBAT pdf files), the following main documents: Document Title 9400AWY Rel.2.1 Installation Handbook 9400AWY Rel.2.1 Installation Guide 9400AWY Rel.2.1 V2.1.1 User Manual 9400AWY Rel.2.1 TRS and SAT Document Technical Code 3DB 16142 BAAA 3DB 16142 FAAA 3DB 16142 EAAA 3DB 16142 DAAA this manual Notes
For further information and additional documents, please refer to Appendix G Documentation guide on page 567
2 / 592
QUICK GUIDE
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
9400AWY Rel.2.1 V2.1.1 USER MANUAL Tab. 1. below allows to access immediately the most frequently needed operative pieces of information contained in this manual and in other related handbooks. To find any other kind of information not listed in this table, please refer to the TABLE OF CONTENTS of this handbook, or, if you are using the pdf file of it, use the Acrobat Reader Find function. Tab. 1. Quick guide If you need immediate operative information on following matters: have a short description of the system know changes of this issue know new features of the SWP version this handbook refers to read pages 37 to 53 read para.11.4 on page 34 read para.11.2 on page 32
GENERAL TOPICS FOR INSTALLATION, COMMISSIONING AND MAINTENANCE read page 4 INSTALLATION AND COMMISSIONING read page 4 MAINTENANCE read page 5 TCO SUITE read page 5 ECT (EQUIPMENT CRAFT TERMINAL): GENERAL AND LOGIN & LOGOFF read page 5 ECT USAGE FOR EQUIPMENT MANAGEMENT AND TROUBLESHOOTING read page 6 EQUIPMENT PROVISIONING AND ITEM PART NUMBERS read page 6 SYSTEM UPGRADE read page 7 EQUIPMENT TECHNICAL CHARACTERISTICS read page 7
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
3 / 592
a)
get information on safety, EMC, EMF, ESD norms and equipment labelling acknowledge cautions to avoid equipment damage have the description of equipment interconnections, according to the configurations for: get operative information regarding the units in IDU (connectors, leds, buttons)
IDU Main unit: read para.13.3 on page 70 IDU Extension unit: read para.13.4 on page 77 E1 Protection box: read para.13.5 on page 79 Services Protection box: read para.13.6 on page 84 Flash Card: read para.13.7 on page 93 Cables and Distributor subracks: refer to the Installation Handbook
read chapter 14 on page 97 , in particular: get operative information regarding ODU para.14.7 on page 119 and para.14.7.4 on page 123
carry out installation and commissioning of equipment as delivered from AlcatelLucent factory
4 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Tab. 1. Quick guide If you need immediate operative information on following matters:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Tab. 1. Quick guide If you need immediate operative information on following matters: c)
MAINTENANCE
read para.45.4 on page 432 read chapter 42 on page 413 read para.43.3 on page 418 proceed as specified in chapter 44 on page 421 proceed as specified in para.45.3 on page 431 proceed as specified in para.45.5 on page 433
know the consequences of unit extraction in IDU shelf set and use the EOW functions of the equipment provision and manage spare parts carry out First Level maintenance (system state display) carry out preventive maintenance carry out corrective maintenance (troubleshooting and repair) d)
TCO SUITE
read para.22.2 on page 146
know ECT and RECT characteristics have the functional description of User Profile management login logoff close the 1320CT application change own password (for all users) manage usernames and passwords of all users (for administrator only) setup a remote connection between CT and equipment, through a switched telephone line of the standard Public Telephone Network.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
5 / 592
f)
have an overview on menu tree structure manage equipment configuration setup parameters for maintenance use functions for SW management proceed as specified in: troubleshoot by ECT g) para.45.8 on page 436 para.45.9 on page 442 open SECTION 2 NE MANAGEMENT on page 139 and then search the information according to the listed topics
do provisioning & know P/Ns at IDU level (except installation materials and cables)
do provisioning & know P/Ns at IDU level for installation materials and cables do provisioning at ODU level (transceivers only)
do provisioning & know P/Ns at ODU level for installation materials, antennas and related matters
read suitable tables (according to configuration and frequency bands) in paragraph Full Integrated or Not Integrated antenna installation components of the Installation Handbook
do provisioning of software products do provisioning of cables for PCtoNE local connection do provisioning for system documentation
read para.21.1.2 on page 141 read para.22.1 point b ) on page 144 read para.57.2 on page 569
6 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Tab. 1. Quick guide If you need immediate operative information on following matters:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Tab. 1. Quick guide If you need immediate operative information on following matters: h)
SYSTEM UPGRADE
proceed as specified in para.47.1 on page 469
install a plugin on IDU Main and/or Extension unit upgrade system configuration from (1+0) to (1+1) replace Flash Card to improve system capacity upgrade only NE with a newer SWP version upgrade only ECT with a newer SWP version upgrade both ECT and NE with a newer SWP version i)
know system technical specifications know ODU P/Ns and related frequency bands and frequency shifters, antenna characteristics and other ODU related matters know Ethernet port characteristics
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
7 / 592
8 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
TABLE OF CONTENTS
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
3 19 29
31 31 32 33 34 35 36 37 37 39 39 42 46 49 50 50 51 54 54 54 55 56 58 59 60 62 64 64 64 65 65 65 67 68 69 70 73 74 75 75 76 77 78 79 80
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
9 / 592
14 ODU PROVISIONING, CHARACTERISTICS AND DESCRIPTION . . . . . . . . . . . . . . . . . . . . . 14.1 ODU mechanical design and identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.2 Labels affixed on the ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.3 ODU configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.4 ODU provisioning and layouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.4.1 Provisioning of ODU (1+0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.4.2 Provisioning, layouts and connections of ODU (1+1) . . . . . . . . . . . . . . . . . . . . . . . . . . 14.5 ODU part lists and characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.5.1 Part lists of ODUs with external diplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.5.2 Part lists of ODUs with embedded diplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.6 Antenna configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.6.1 1+0 configuration with full integrated antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.6.2 1+1 HSB configuration with coupler and full integrated antenna (1338 GHz) . . . . . 14.6.3 1+1 HSB configuration with coupler and full integrated antenna (78 GHz) . . . . . . . 14.6.4 Configuration with separated antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.7 ODU operative information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.7.1 Operative information on ODUs with embedded or external diplexer . . . . . . . . . . . . . 14.7.2 ODU hardware settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.7.3 ODU identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14.7.4 Additional operative information on ODUs with external diplexer . . . . . . . . . . . . . . . . 15 TECHNICAL SPECIFICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1 General Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.1 Reference system standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.2 RF channelling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.3 Transmitted power at antenna port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.4 99% power channel bandwidth and Emission Designator . . . . . . . . . . . . . . . . . . . . . . 15.1.5 ETSI System Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.1.6 Protection switching system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.2 Tributary interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.3 Modem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.4 Maximum capacity and Modulation type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.5 IDUODU cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.6 Manmachine interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.7 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.8 Power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.9 Mechanical characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.10 Environmental conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.10.1 Operating environmental conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.10.2 Electromagnetic compatibility/safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15.10.3 Waste from Electrical and Electronic Equipment (WEEE) . . . . . . . . . . . . . . . . . . . . . 15.11 Dismantling & Recycling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
97 98 99 100 101 101 101 104 105 108 113 114 116 117 117 119 119 122 122 123 127 128 129 129 130 131 132 134 135 135 135 135 136 136 136 136 137 137 137 137 138
139
21 SWP 9400AWY R.2.1 V2.1.1 DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 21.1 SWP 9400AWY R.2.1 V2.1.1 general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL FRONT MATTER
10 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
13.6 Description of Services Protection box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.6.1 Alarms Housekeeping (pinout and description) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.6.2 NMS V.11 Audio 1 (pinout and description) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.6.3 NMS G.703 Audio 2 (pinout and description) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.6.4 User service channels (pinout and description) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.7 Provisioning and identification of Flash Cards & Software Labels . . . . . . . . . . . . . . 13.7.1 Provisioning of Flash Cards & Software Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.7.2 Description of Flash Cards & Software Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13.8 Provisioning and description of equipment accessories . . . . . . . . . . . . . . . . . . . . . . .
84 85 88 89 90 93 93 94 96
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
21.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.1.2 Software product list and part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2 SWP 9400AWY R.2.1 V2.1.1 specific information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.1 PC characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.2 NE MIB Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21.2.3 SWP version specific data and Reference Information Models . . . . . . . . . . . . . . . . . . 22 INTRODUCTION ON TCO SUITE AND CT VIEWS AND MENUS . . . . . . . . . . . . . . . . . . . . . . 22.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2 TCO Suite description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2.1 TCO Suite scopes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2.2 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2.3 TCO Suite startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2.4 TCO Suite Main Menu functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2.5 TCO Suite Advanced Settings Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2.6 Note: Direct And Remote Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.2.7 Warning about interface customization carried out by the Direct Connection . . . . . . 22.3 TCO Suite Alarms & Settings functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.3.1 TCO Suite Alarms & Settings startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.3.2 Date & Time Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.3.3 Configuration Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.3.4 Configuration Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.3.5 Get Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.3.6 Active Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.3.7 Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.3.8 Licence Info . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.3.9 Modem Speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.3.10 NAT option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.4 PCNE physical connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.4.1 Physical interfaces for the NE management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.4.2 Local connection of the Craft Terminal to the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.5 Craft Terminal: NE supervision, login, logoff and switch off . . . . . . . . . . . . . . . . . . . . 22.5.1 NE management states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.5.2 NE supervision and login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.5.3 NE Logoff or switch off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.5.4 Closing the 1320CT application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.6 9400AWY view organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.6.2 View Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.6.3 Button Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.6.4 Main tool bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.7 Introduction to the CT menu options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.7.1 Menu organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.7.2 Views menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.7.3 Configuration menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.7.4 Diagnosis menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.7.5 Supervision menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22.7.6 SW Download menu introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.1 NE Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.2 Network Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.2.1 Local Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.2.2 NTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.2.3 Ethernet Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.2.4 IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . USER MANUAL FRONT MATTER
141 141 142 142 142 142 143 144 146 146 147 148 149 151 154 155 156 156 159 160 161 164 165 166 166 167 168 170 170 171 172 172 173 180 180 181 181 182 183 183 184 184 185 186 186 187 187 189 190 191 192 193 195 196
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
11 / 592
24 EQUIPMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.1 IDU level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.1.1 1+0 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.1.2 1+1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.1.3 Board level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.2 ODU level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.3 Tab panels in the Resource Detail Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.3.1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.3.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24.3.3 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 LINE INTERFACE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.1 Tab panels in the Resource Detail Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.1.1 Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25.1.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 RADIO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.2.1 Local or Remote Transmitter Mute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.2.2 ODU service kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.2.3 Alarm Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.3 Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.4 RTPC & ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.4.1 ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.4.2 RTPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.5 Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.5.1 How to read a Power Measurement file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26.6 BER measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
219 221 221 222 222 223 224 224 225 225 227 228 228 228 233 234 234 234 234 234 235 238 239 240 241 244 246
27 EXTERNAL POINTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 27.1 Input External Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 27.2 Output External Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 28 SUPERVISION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.1 Access state (allow or inhibit NE Craft access) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.1.1 Switching from the OS to the Craft Terminal access state . . . . . . . . . . . . . . . . . . . . . . 28.1.2 Switching from the Craft Terminal access state back to the OS access state . . . . . 28.2 Restart NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.3 MIB Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.3.1 Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.3.2 Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28.3.3 Activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 251 251 251 252 252 253 254 255 255
12 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
23.2.5 Routing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.3 Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.3.1 How to create a new Alarm Severity Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.4 System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.4.1 NE Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.4.2 Link Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.4.3 Overhead . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.5 Quick Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.6 Profiles management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.6.1 Functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.6.2 Change Password procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.6.3 Users Management procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23.7 Log Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
204 205 207 210 210 212 213 213 214 214 216 217 218
29 PROTECTION SCHEMES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.1 Equipment Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.1.1 Schema Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.1.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.2 Radio Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.2.1 Schema Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.2.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.3 HSB Transmission Protection Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.3.1 Schema Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.3.2 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29.4 Rx Static Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 LOOPBACKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210.1 Hardware implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210.1.1 IDU loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210.1.2 ODU loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210.2 Available Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210.3 Loopback domain views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210.4 How to activate a loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210.5 How to remove a loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 DIAGNOSIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.1.1 Counter Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.1.2 Alarm Sublist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.2 Log Browsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.2.1 Alarm and Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.2.2 Software Trace Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.3 Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.3.2 Remote Inventory display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.4 Abnormal Condition List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.5 Summary Block Diagram View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211.6 Current Configuration view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 PERFORMANCE MONITORING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.1 General information on the performance monitoring process . . . . . . . . . . . . . . . . . 212.2 Performance menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.3 CD (Current Data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.3.1 CD parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.3.2 CD Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.4 HD (History Data) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.4.1 HD Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.5 Threshold tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.5.1 How to change a threshold table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.5.2 How to create a threshold table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.5.3 Threshold table association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 SW 213.1 213.2 213.3 DOWNLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Server Access Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Init SW Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SW Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
257 258 258 259 260 260 261 262 262 263 264 267 267 267 268 269 272 275 276 277 278 278 278 279 280 281 282 282 283 284 285 288 289 289 290 292 292 293 294 294 295 295 296 296 297 297 298 299
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
13 / 592
307
309 309 309 310 310 311 312 314 314 315 317 318 318 320 320 321 326 326 326 327 329 329 329 329 330 330 331 332 333 334 335 336 337 338 338 339 339 340 340 341 343 344
14 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
214 MIB MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.2 MIB management at Network Element Synthesis level and examples . . . . . . . . . . 214.2.1 MIB backup on ECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.2.2 MIB save to disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.2.3 MIB load from disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214.2.4 MIB restore from ECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32.3.9 TCO Suite SetUp Tool: online recover, modification and application of a provisioning file (not interactive) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.3.10 Quick Configuration Procedure steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.3.11 Powering UP the IDU(s) with the ODU(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.4 Commissioning of STATION B phase 1 (Turn up) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.5 End of commissioning phase 1 (Turn up) in STATION A . . . . . . . . . . . . . . . . . . . . . . . 32.5.1 Remote NE (station B) acquisition on craft terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.5.2 Testing configurations for hop quality check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.6 Commissioning station A phase 2 (acceptance test) . . . . . . . . . . . . . . . . . . . . . . . . . 32.6.1 System Installation and cabling visual inspection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.6.2 Local configuration control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.6.3 Channel 1 functionality tests (1+0 and 1+1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.6.4 Channel 0 functionality tests (1+1 only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.6.5 Hop stability test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.6.6 NE integration tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.7 Commissioning station B Phase 2 (Acceptance Test) . . . . . . . . . . . . . . . . . . . . . . . . 32.8 Final operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.9 Annex A: fine antenna alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.10 Annex B: light service kit cable operative information . . . . . . . . . . . . . . . . . . . . . . . .
345 346 369 373 374 374 376 377 377 377 382 394 396 397 403 403 404 405
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
407
409 409 410 410 410
42 USE OF EOW FUNCTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 42.1 Setting information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 42.2 Call Setup/End by Telephone handset connected to the IDU Main unit . . . . . . . . . 414 43 MAINTENANCE TOOLS AND SPARE PARTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43.2 Instruments and accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43.2.1 Software tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43.2.2 Maintenance, Installation and Station Tool Kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43.3 Set of spare parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43.3.1 Types of Spare Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43.3.2 ODU Spare Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43.3.3 IDU Spare Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43.3.4 Number of spare parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43.3.5 General rules on spare parts management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 FIRST LEVEL MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44.2 System state display by visual indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44.2.1 LED test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44.2.2 Alarm LEDs on the IDU MAIN unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44.2.3 Alarm LEDs on the Extension unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44.3 TCO Suite and Craft Terminal commonly used functions for system status display and checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44.3.1 Viewing the NE alarms by TCO Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44.3.2 Viewing the NE status by Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 415 415 415 416 418 418 418 418 419 419 421 421 421 421 421 421 423 423 423
45 SECOND LEVEL MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 45.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429 USER MANUAL FRONT MATTER 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
15 / 592
45.2 Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.2.1 EMC norms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.2.2 Safety rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.2.3 Cautions to avoid equipment damage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.3 Routine (preventive) Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.3.1 Routine (preventive) Maintenance every year . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.4 Consequences of unit extraction in the IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.5 Corrective Maintenance general flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.6 Alarm acknowledgment and attending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.6.1 Alarm acknowledgment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.6.2 Alarm Attending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.7 Troubleshooting starting with visual indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.8 Troubleshooting via Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.8.1 Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.8.2 Alarm surveillance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.8.3 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.8.4 Operators Controls of the protection switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.8.5 Tx mute function (local and remote) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.8.6 Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.8.7 BER measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.8.8 Commissioning tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.9 Hints on the troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.9.1 Problems with the Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.9.2 Analog measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.9.3 NMS 64 kbit/s V.11 and G.703 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.9.4 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.9.5 Empty USM icon in NES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.9.6 Remote NE unreachable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.9.7 Configuration change from 4 QAM to 16 QAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.9.8 Quick configuration menu correct use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.9.9 Abnormal condition list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.9.10 Tx Mute functionality for interferences investigation . . . . . . . . . . . . . . . . . . . . . . . . . . 45.9.11 Tributaries 17 to 32 visible in 16E1+Ethernet configuration . . . . . . . . . . . . . . . . . . 45.10 IDU unit replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.10.1 IDU MAIN unit replacement procedure (CH1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.10.2 IDU EXTENSION unit replacement procedure (CH0) . . . . . . . . . . . . . . . . . . . . . . . . . 45.11 ODU replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.12 Faulty unit repair and Repair Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.12.1 Faulty unit sending back to repair center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45.12.2 Repair Form filling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 SPARE FLASH CARD MANAGEMENT AND REPLACEMENT PROCEDURES . . . . . . . . . 46.1 Spare Flash Card management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46.2 Flash Card replacement procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46.2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46.2.2 Execution of the Flash Card replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 SYSTEM HARDWARE UPGRADE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47.1 Installation of plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47.1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47.1.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47.2 Upgrade from 1+0 to 1+1 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47.2.1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47.2.2 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47.3 Flash Card upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47.3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
430 430 430 430 431 431 432 433 434 434 434 435 436 436 437 441 441 441 441 441 441 442 442 446 446 446 447 447 447 447 448 449 450 451 452 456 460 463 463 463 465 465 466 466 467 469 469 469 470 476 476 477 479 479
16 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Summary procedure for both stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ordering the new Flash Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation of a new Flash Card fully configured in factory . . . . . . . . . . . . . . . . . . . . . Installation of a new Flash Card not configured in factory . . . . . . . . . . . . . . . . . . . . . .
480 481 482 483 485 485 485 485 485 486 486 487 492 494 494
48 SWP DOWNLOAD TOWARD NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48.1 Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48.1.1 Craft Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48.1.2 NE state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48.1.3 Operator skills and profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48.2 Summary of the SWP download phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48.3 CT startup, NE login and initial checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48.4 SW download to the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48.5 Activation of the new Software Package on the NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48.6 Additional operations for upgrade from V2.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48.7 MIB save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49 ECT & NE UPGRADE FROM V2.1.0 TO V2.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495 410 SWP DEINSTALLATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
SECTION 5: APPENDICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
51 APPENDIX A: SAFETYEMCEMFESD NORMS AND EQUIPMENT LABELLING . . . . . 51.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Compliance with International Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3 Safety Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3.1 General Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3.2 Labels Indicating Danger, Forbiddance, Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3.3 Dangerous Electrical Voltages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3.4 Risks of Explosions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3.5 Moving Mechanical Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3.6 Equipment connection to earth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3.7 Heatradiating Mechanical Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3.8 Microwave radiations (EMF norms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3.9 Specific safety rules in this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.4 Electromagnetic Compatibility (EMC norms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.4.1 EMC General Norms Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.4.2 EMC General Norms Turnon, Tests & Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.4.3 EMC General Norms Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.5 Equipment protection against electrostatic discharges . . . . . . . . . . . . . . . . . . . . . . . . 51.6 Suggestions, notes and cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.7 Labels affixed to the 9400AWY equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
499
501 501 501 502 502 503 504 505 505 506 506 507 508 509 509 509 509 510 510 510
52 APPENDIX B: TCO SUITE STARTUP SPECIAL CONDITIONS . . . . . . . . . . . . . . . . . . . . . . 511 53 APPENDIX C: ADDITIONAL SW INSTALLATION OPERATIONS FOR NE MANAGEMENT THROUGH THE NES ECT SERIAL PORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 53.1 Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517 53.2 Installation of LLMAN from the SWP CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519 53.2.1 Operations sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519 53.2.2 Next step . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521 53.3 Installation and configuration of Alcatel Virtual Network Card for Lower Layers . 522 53.3.1 Important warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522 53.3.2 Choice of the procedure, according to Windows platform . . . . . . . . . . . . . . . . . . . . . . 522 53.3.3 Windows NT 4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523 53.3.4 Windows 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529 USER MANUAL FRONT MATTER 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
17 / 592
53.3.5 Windows XP (Professional Edition only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537 53.3.6 Check for the Network Connections order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546 54 APPENDIX D: GENERAL ON ETHERNET PORT CHARACTERISTICS AND MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54.1 Ethernet Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54.2 MDI/MDIX crossover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54.3 Frame size, Rx checksum and FCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54.4 Ethernet capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54.5 Ethernet flow control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54.6 Ethernet interface management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54.7 Ethernet Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 APPENDIX E: ECTEQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE NETWORK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.2 Certified equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.3 Connection cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.4 Modem setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.4.1 Setting of Sportster Flash Modem & 3Com 56K Faxmodem . . . . . . . . . . . . . . . . . . . . 55.4.2 TD32 AC Modem setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.5 PC laptop Dell Latitude setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.6 Setting up the connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.7 Changing the ECTequipment connection speed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.7.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.7.2 Configuration at NE side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55.7.3 Configuration at PC side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 APPENDIX F: PART LISTS OF TOOL KITS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56.1 Installation Tool Kit part list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56.2 Maintenance Tool Kit part list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56.3 Station Tool Kit part list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 APPENDIX G: DOCUMENTATION GUIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57.1 Guide to this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57.1.1 Applicability of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57.1.2 Purpose of this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57.2 Documentation set description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57.2.1 9400AWY 2.1.1 Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57.2.2 Product Release Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57.2.3 Additional documentation for 1320CT platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57.3 General on AlcatelLucent Customer Documentation . . . . . . . . . . . . . . . . . . . . . . . . . 57.3.1 CustomerIndependent Standard Customer Documentation . . . . . . . . . . . . . . . . . . . 57.3.2 Product levels and associated Customer Documentation . . . . . . . . . . . . . . . . . . . . . . 58 APPENDIX H: LIST OF SYMBOLS AND ABBREVIATIONS, GLOSSARY OF TERMS . . . 58.1 List of symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58.2 List of abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58.3 Glossary of terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
553 553 554 555 556 556 558 559 560 561 561 561 562 563 563 564 565 567 567 567 568 569 569 571 571 572 572 573 575 575 575 585
18 / 592
FIGURES Fig. 1. Antistatic protection device kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 2. 9400AWY radio link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 3. 9400AWY R.2.1 splitmount system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 4. Possible configurations of ODU (1+1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 5. E1 Protection box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 6. Services Protection box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 7. 9400AWY R.2.1 (1+0) IDU block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 8. 9400AWY R.2.1 (1+1) IDU block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 9. ODU block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 10. 9400AWY (1+0) IDU + ODU block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 11. 9400AWY (1+1 HSB SD) IDU + ODU block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 12. 9400AWY (1+1 HSB one antenna) IDU + ODU block diagram . . . . . . . . . . . . . . . . . . . . . . . Fig. 13. 9400AWY (1+1 FD Double Antenna AP) IDU + ODU block diagram . . . . . . . . . . . . . . . . . . Fig. 14. 9400AWY (1+1 FD one antenna AP) IDU + ODU block diagram . . . . . . . . . . . . . . . . . . . . . Fig. 15. Flash Card content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 16. Main phases for 9400AWY HW and SW installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 17. Software management main phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 18. How to check ECT version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 19. How to check NE SW version (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 20. Label affixed on the IDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 21. IDU Main Unit front and rear views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 22. LEDs on the IDU Main Unit front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 23. IDU Extension Unit front and rear views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 24. LEDs on the IDU Extension Unit front panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 25. E1 Protection box: views of Equipment Side and Line Side connectors . . . . . . . . . . . . . . . Fig. 26. Services Protection box: views of Equipment Side and Line Side connectors . . . . . . . . . . Fig. 27. Equipment outputs (summarizing and housekeeping) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 28. Equipment inputs relay scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 29. Equipment inputs open collector scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 30. User service channel: V11 codirectional interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 31. User service channel: V11 contradirectional interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 32. User service channel: G.703 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 33. User service channel: V24/V28 interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 34. FLASH CARD profile and insertion direction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 35. Flash Card identification labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 36. ODU types, identification, dimensions and weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 37. Label affixed on the ODU and ODUs TRANSCEIVER box . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 38. Station layout of ODU (1+1) HSBSD or FDDA AP with two antennas . . . . . . . . . . . . . . . Fig. 39. Station layout of ODU (1+1) HSB with one antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 40. Station layout of ODU (1+1) FDAP with one double polar external antenna . . . . . . . . . . Fig. 41. View of ODU with full integrated antenna (V polarization) . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 42. View of ODU with full integrated antenna (H polarization) . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 43. Coupler (1338 GHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 44. Coupler (78 GHz) example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 45. Nose adapters for ODU with separated antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 46. Views of ODUs with embedded diplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 47. Views of ODUs with external diplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 48. ODU LEMO connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 49. Composition of ODUs with external diplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 50. ODUs TRANSCEIVER and BRANCHING boxes coupling surfaces . . . . . . . . . . . . . . . . . . USER MANUAL FRONT MATTER
36 37 40 41 43 43 44 45 47 50 52 52 53 53 56 59 60 62 63 69 70 73 77 78 79 84 86 87 87 91 91 92 92 94 95 98 99 101 102 103 114 115 116 117 117 120 121 122 123 124
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
19 / 592
Fig. 51. 78 GHz ODUs BRANCHING box mistakeproofing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 52. Label affixed inside the ODU BRANCHING box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 53. Java installation request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 54. JRE installation completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 55. TCO Suite Start.html page (CDROM version) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 56. TCO Suite Start.html page (Local version) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 57. TCO Suite AS.html page (Advanced Settings) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 58. Internet Explorer: .exe files management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 59. ECTNE Direct and Remote connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 60. Network Adapter selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 61. Network Adapter details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 62. Direct or Remote connection by the TCO Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 63. NE login by the TCO Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 64. TCO Suites Alarms & Settings Main Menu screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 65. TCO Suites Alarms & Settings Date & Time Configuration page . . . . . . . . . . . . . . . . . . . Fig. 66. TCO Suites Alarms & Settings Configuration Setting page . . . . . . . . . . . . . . . . . . . . . . . . Fig. 67. TCO Suites Alarms & Settings Get Report Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 68. TCO Suites Alarms & Settings Get Configuration Request . . . . . . . . . . . . . . . . . . . . . . . . Fig. 69. TCO Suites Alarms & Settings Active Alarms: Static Page . . . . . . . . . . . . . . . . . . . . . . . . Fig. 70. TCO Suites Alarms & Settings Active Alarms: Automatic Page . . . . . . . . . . . . . . . . . . . . Fig. 71. TCO Suites Alarms & Settings Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 72. TCO Suites Alarms & Settings Reading Software License . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 73. TCO Suites Alarms & Settings Changing FInterface Speed . . . . . . . . . . . . . . . . . . . . . . Fig. 74. TCO Suites Alarms & Settings NAT option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 75. NAT router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 76. MAIN Unit front side: interfaces for equipment control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 77. Choice of Serial or Ethernet interface for PCNE physical connection . . . . . . . . . . . . . . . . Fig. 78. Network Element Synthesis screen (NE locally connected) . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 79. Network Element Synthesis screen (empty map) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 80. SNMP NE creation in the Network Element Synthesis map . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 81. Network Element Synthesis screen after SNMP NE creation . . . . . . . . . . . . . . . . . . . . . . . . Fig. 82. Start supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 83. NE in supervised state . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 84. Show Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 85. Login screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 86. NE Stop Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 87. 9400AWY Main view organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 88. Main tool bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 89. NE Time dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 90. Network Configuration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 91. Local Configuration dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 92. NTP Configuration dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 93. Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 94. Ethernet Configuration dialogue box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 95. IP configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 96. IP static routing configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 97. Create Static routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 98. Point To Point Interface Choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 99. OSPF Area configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 100. Create New OSPF Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 101. IP Address configuration of PointToPoint Interfaces screen . . . . . . . . . . . . . . . . . . . . . . Fig. 102. IP Address and Timeslot configuration of PointToPoint InFrame E1 TMN . . . . . . . . . Fig. 103. Routing information screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 104. Alarm Severities Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 105. Name of a cloned alarm profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
125 126 148 148 149 149 151 152 154 154 155 156 157 157 159 160 161 164 165 165 166 166 167 168 168 170 174 175 175 176 176 177 177 179 179 180 181 183 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 206 207
20 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 106. Clone of an Alarm Severity Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 107. Selection of a new severity in the Service Affecting field . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 108. Selection of a new severity in the No Service Affecting field . . . . . . . . . . . . . . . . . . . . . . . . Fig. 109. System Settings: NE configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 110. Confirmation message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 111. USM closing warning message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 112. System Settings: NE configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 113. Overhead Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 114. Profile Management options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 115. Changing Password screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 116. Users Management screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 117. Users Management help screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 118. Log Switch screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 119. 1+0 Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 120. 1+1 Equipment view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 121. 1+0 IDU view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 122. 1+1 IDU/MAIN Ch#1 view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 123. 1+1 IDU Ch#0 view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 124. ODU view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 125. Alarm tab panel for a selected object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 126. Configuration tab panel for a selected object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 127. Remote Inventory tab panel for a selected object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 128. Line Interface View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 129. Line Interface View: E1 Tributary Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 130. Line Interface View: NMS interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 131. Line Interface View: Data Tributary Port QoS Configuration tab panel . . . . . . . . . . . . . . . Fig. 132. Line Interface View: Data Tributary Port PM counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 133. Line Interface View: individual Data Tributary Port Configuration tab panel . . . . . . . . . . . Fig. 134. Radio Domain View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 135. RadioConfiguration menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 136. Radio Frequency Functions with Shifter and Rx Freq enabled . . . . . . . . . . . . . . . . . . . . . . Fig. 137. Radio Frequency Functions with Rx Freq disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 138. Radio Frequency Functions with shifter disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 139. Not standard frequency arrangement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 140. RTPC & ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 141. Power Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 142. Power Measurement Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 143. Power Meas Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 144. Name of File ( Log File ) selected screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 145. Example of Power Measurement File Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 146. Example of Power Measurement File Reading (with WordPad) . . . . . . . . . . . . . . . . . . . . . Fig. 147. BER Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 148. Input External Point View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 149. Output External Points: CP01 ... CP04 (Manual activation) . . . . . . . . . . . . . . . . . . . . . . . . Fig. 150. Output External Points: CP01 ... CP04 (Automatic activation) . . . . . . . . . . . . . . . . . . . . . . Fig. 151. Output External Points View: FAIL IDU, FAIL ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 152. Configuration of the Craft access state from the Equipment NE view in the OS mode . . Fig. 153. Restart NE call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 154. Restart NE confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 155. MIB Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 156. Backup screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 157. Restore screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 158. Activate command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 159. SW key screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 160. Protection Schemes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . USER MANUAL FRONT MATTER
207 208 209 210 211 211 212 213 216 216 217 217 218 220 220 221 222 222 223 224 225 225 227 228 230 231 231 232 233 234 235 235 236 237 238 241 242 243 244 244 245 246 247 248 249 250 251 252 252 253 254 255 255 256 257
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
21 / 592
Fig. 161. Mux Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 162. Mux Protection Switch (example for Main #1 selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 163. Radio Protection View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 164. Radio Protection Switch (example for Main #1 selected) . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 165. Transmission Protection View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 166. HSB Tx Protection Commands (example for Main #1 selected) . . . . . . . . . . . . . . . . . . . . . Fig. 167. Rx Static Delay menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 168. Rx Static Delay panel Warning message for fail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 169. Rx Static Delay in auto mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 170. Near end IDU cable loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 171. Far end IDU tributary loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 172. Near end tributary loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 173. Near end ODU cable loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 174. Near end RF loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 175. Available loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 176. 1+0 Loopback types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 177. 1+1 Loopback types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 178. Loopback View for PDH Tributaries (1+0) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 179. Loopback View for PDH Tributaries (1+1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 180. Loopback View for Radio PDH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 181. Loopback CABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 182. Loopback activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 183. Loopback removing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 184. Alarm Counter Summary Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 185. Alarm Sublist Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 186. Log Browsing Sub Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 187. Alarm Log Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 188. Event Log Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 189. Transfer Information Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 190. SW Trace Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 191. Remote Inventory screen (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 192. Abnormal Condition List screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 193. Summary Block Diagram View example: 1+0 16E1 without Ethernet ports . . . . . . . . . . . Fig. 194. Summary Block Diagram View example: 1+1 HSB 16E1 with Ethernet ports . . . . . . . . . Fig. 195. Summary Block Diagram View example: 1+1 HSB 16E1ETH with Audio/User Service Channel PlugIn (Lockout) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 196. Summary Block Diagram View example: 1+1 FD 32E1 with Audio/User Service Channel PlugIn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 197. Current Configuration view screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 198. Radio sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 199. Performance View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 200. Threshold table association screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 201. Current Data View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 202. History Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 203. Threshold table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 204. Thresholds Table creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 205. Server access configuration screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 206. Init Software Download screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 207. SW Status screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 208. SW Unit Status screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 209. Allowed MIB management tasks at NE loggedin level . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 210. Allowed MIB management tasks at Network Element Synthesis level . . . . . . . . . . . . . . Fig. 211. Launch of MIB save to disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 212. MIB save to disk phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 213. MIB save to disk phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
258 259 260 261 262 263 264 264 265 267 267 268 268 268 269 270 271 272 273 273 274 275 276 278 279 279 280 280 281 281 283 284 286 286 287 287 288 289 290 291 292 294 295 296 297 298 299 300 301 301 302 302 303
22 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 214. Correspondence between MIB saved folder and MIB saved name . . . . . . . . . . . . . . . . . . Fig. 215. Launch of MIB load from disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 216. MIB load from disk phase 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 217. MIB load from disk phase 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 218. Common components of different SWPs (example) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 219. CDROM TCO Suite Main Menu screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 220. CDROM TCO Suite Advanced Settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 221. SWP component selection screen and installation start . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 222. SWP component installation end, and installation report . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 223. Check of installed Alcatel SWP components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 224. Local Copy of TCO Suite location choice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 225. Local Copy of TCO Suite progress and end . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 226. Copy cancelled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 227. Shortcut to the TCO Suite Start icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 228. Selecting SWP Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 229. SWP Administrator screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 230. Directory selection for the descriptor file .DSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 231. SWP available for download to NEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 232. Relative positions of stations A and B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 233. Equipment interconnections for configurations with 16E1 . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 234. Equipment interconnections for configurations with 16E1 + Audio and User Service Channel plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 235. Equipment interconnections for configurations with 16E1 + Enhanced Ethernet plugin Fig. 236. Equipment interconnections for configurations with 16E1 + Enhanced Ethernet plugin + Audio and User Service Channel plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 237. Equipment interconnections for configurations with 32E1 . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 238. Equipment interconnections for configurations with 32E1 + Audio and User Service Channel plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 239. PreProvisioning Tool splash screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 240. PreProvisioning Tool console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 241. PreProvisioning Tool start screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 242. SetUp Tool splash screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 243. SetUp Tool console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 244. SetUp Tool start screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 245. Quick Configuration Procedure: main NE parameter configuration (Step A) . . . . . . . . . . Fig. 246. Quick Configuration Procedure Step B: PDH Tributary configuration . . . . . . . . . . . . . . . . Fig. 247. Quick Configuration Procedure Step B: Ethernet GPort configuration . . . . . . . . . . . . . . . . Fig. 248. Quick Configuration Procedure Step B: Ethernet GPort QoS configuration . . . . . . . . . . . Fig. 249. Quick Configuration Procedure: Channels Configuration (Step C) . . . . . . . . . . . . . . . . . . . Fig. 250. Frequency Data Help: choice of ODU type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 251. Frequency Data Help: frequency data of chosen ODU type (example) . . . . . . . . . . . . . . . Fig. 252. Example of Frequency Data manual setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 253. RTPC setting with ATPC disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 254. Setting of enabled ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 255. ATPC and RTPC Configuration for both channels (1+1 HSB) . . . . . . . . . . . . . . . . . . . . . . . Fig. 256. Quick Configuration Procedure: Link Identifier configuration (Step D) . . . . . . . . . . . . . . . . Fig. 257. Quick Configuration Procedure: Automatic restoration criteria configuration (Step E) . . Fig. 258. Quick Configuration Procedure: OSPF Area Configuration (Step F) . . . . . . . . . . . . . . . . . Fig. 259. Quick Configuration Procedure: Local IP address, Ethernet and NTP configuration (Step G) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 260. Quick Configuration Procedure: Configuration of TMNRF, TMNV11 and TMNG703 channels (Step H) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 261. Quick Configuration Procedure: Configuration of TMN inframe (Step H) . . . . . . . . . . . Fig. 262. Quick Configuration Procedure: IP Static Routes Configuration (Step I) . . . . . . . . . . . . . . Fig. 263. Quick Configuration Procedure: Default Gateway Routing configuration (Step I) . . . . . . USER MANUAL FRONT MATTER
303 304 305 306 313 315 316 316 317 317 318 319 319 320 321 321 323 325 329 332 333 334 335 336 337 344 344 344 345 345 346 347 349 351 352 353 355 355 356 356 357 357 358 359 360 361 362 363 364 365
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
23 / 592
Fig. 264. Quick Configuration Procedure: EOW and Auxiliary Interface configuration (Step J) . . . Fig. 265. Quick Configuration Procedure: External Input and Output Points configuration (Step K) Fig. 266. Quick Configuration Procedure: Summary (Step L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 267. ODU(s) alarm status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 268. Transmit power check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 269. Received power check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 270. Received power details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 271. NES window local NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 272. Create NE in the CT map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 273. NMS Radio side Remote NE acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 274. Test bench for tributary quality test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 275. Test bench for User service channel quality test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 276. 1+0 Summary block diagram view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 277. 1+1 Summary block diagram view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 278. Channel 0 lockout mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 279. Near End loopbacks points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 280. Loopback control in the CT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 281. Far End loopback point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 282. Test bench for tributary functionality check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 283. Tributary alarm status monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 284. Test bench for User Service Channel functionality check . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 285. Test bench for Optional Ethernet Data Channel functionality (with 4xGigabit Ethernet plugin) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 286. Engineering order wire organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 287. Channel 1 forced mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 288. Test bench for hop stability test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 289. Test bench for NMS Line side acquisition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 290. NES window local NE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 291. Create NMS Line side NE in the CT map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 292. NMS Line side NE monitoring in the CT map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 293. Test bench for EOW line side functionality test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 294. Light service kit cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 295. Special extractor to remove the coaxial cables 1.0/2.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 296. Lever for ODU mounting/dismounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 297. LEDs and pushbutton on IDU Extension unit for maintenance purposes . . . . . . . . . . . . . Fig. 298. LEDs and pushbutton on IDU MAIN unit for maintenance purposes . . . . . . . . . . . . . . . . . Fig. 299. Checks on Radio domain : Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 300. Checks on Radio domain : Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 301. Checks on Radio domain : Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 302. Checks on Radio domain : RTPC & ATPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 303. Checks on Radio domain : nonintrusive BER measurement . . . . . . . . . . . . . . . . . . . . . . . Fig. 304. Checks on Radio domain : Power Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 305. Corrective Maintenance general flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 306. Troubleshooting starting with visual indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 307. Alarm and status synthesis indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 308. Active alarm screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 309. Lower Layers Manager screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 310. Abnormal condition list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 311. Tx Mute functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 312. Tributaries 17 to 32 visible in 16E1+ Ethernet configuration . . . . . . . . . . . . . . . . . . . . . . . Fig. 313. Details for IDU MAIN unit or FLASH CARD replacement . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 314. Details for IDU EXTENSION unit replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 315. Repair form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 316. Dismounting the fixing brackets and cover unfix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 317. Release and sliding out the cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
366 367 368 369 370 371 372 374 375 375 376 376 383 383 384 385 386 387 388 389 390 391 393 394 396 397 398 398 399 400 405 416 417 421 422 424 424 425 426 426 427 433 435 437 439 444 448 449 450 452 456 464 470 471
24 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 318. Removing the cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 319. Dismounting the metal plate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 320. Connectors and columns for plugin fixing by screws . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 321. Plugin insertion and fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 322. Server Access Configuration start up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 323. Server Access Configuration setup screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 324. Init SW Download startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 325. Init download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 326. SW Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 327. Stand by SW activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 328. Forced Init download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 329. Security Questions: Secure Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 330. Secure Questions: Allow Secure Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 331. Execution confirmation (Security Warning) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 332. Security Warning (English browser on Italian System) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 333. Security Warning (Italian browser on Italian System) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 334. Security Warning (Java 1.4) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 335. Wrong Security Warning (Java 1.3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 336. Firefox browser: no JRE installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 337. Firefox plugin search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 338. Firefox plugin installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 339. CDROM TCO Suite Main Menu screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 340. CDROM TCO Suite Advanced Settings screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 341. Alcatel Lower Layers Manager splash screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 342. Alcatel Lower layers Manager language selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 343. Alcatel Lower Layers Manager Installation screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 344. Alcatel Lower Layers Manager setting screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 345. Windows NT installation step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 346. Windows NT installation step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 347. Windows NT installation step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 348. Windows NT configuration step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 349. Windows NT configuration step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 350. Windows NT configuration step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 351. Windows NT configuration step 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 352. Windows NT configuration step 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 353. Windows NT configuration step 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 354. Windows 2000 installation step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 355. Windows 2000 installation step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 356. Windows 2000 installation step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 357. Windows 2000 installation step 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 358. Windows 2000 installation step 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 359. Windows 2000 configuration step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 360. Windows 2000 configuration step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 361. Windows 2000 configuration step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 362. Windows XP installation step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 363. Windows XP installation step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 364. Windows XP installation step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 365. Windows XP installation step 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 366. Windows XP installation step 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 367. Windows XP configuration step 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 368. Windows XP configuration step 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 369. Windows XP configuration step 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 370. Windows XP configuration step 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 371. Check for the Network Connections order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 372. ECTEquipment connection via Public Switched Telephone Network . . . . . . . . . . . . . . . . USER MANUAL FRONT MATTER
472 472 473 474 487 488 489 490 492 492 494 511 512 512 513 513 514 514 515 515 516 517 518 519 519 520 521 523 524 524 525 526 526 527 528 528 529 530 531 531 532 533 534 535 538 539 540 540 541 542 543 544 545 546 553
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
25 / 592
TABLES Tab. 1. Quick guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 2. Main additional features with respect to SWP version V2.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 3. Tributaries and modulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 4. 13 to 38 GHz 4/16 QAM configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 5. Bit rate of the IDUODU signal on the cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 6. IDU shelf provisioning for 1+0 and 1+1 configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 7. IDU Main Unit: external interfaces list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 8. Power supply connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 9. ECT connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 10. OS (or ECT) connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 11. RJ45 connectors leds for Ethernet user data interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 12. IDU Extension Unit: external interfaces list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 13. Equipment Side and Line Side connectors of E1 Protection box . . . . . . . . . . . . . . . . . . . . . Tab. 14. E1 tributaries (1 to 8) connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 15. E1 tributaries (9 to 16) connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 16. E1 tributaries (17 to 24) connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 17. E1 tributaries (25 to 32) connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 18. Equipment Side and Line Side connectors of Services Protection box . . . . . . . . . . . . . . . . Tab. 19. Alarms Housekeeping connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 20. NMSV.11 + Audio 1 connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 21. NMSG.703 + Audio 2 connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 22. User service channel connector pinout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 23. Flash Cards provisioning and associated & Software Labels . . . . . . . . . . . . . . . . . . . . . . . Tab. 24. Equipment accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 25. ODU dimensions and weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 26. ODU configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 27. 7 GHz Transceiver assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 28. Branching assemblies for 7 GHz ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 29. 8 GHz Transceiver assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 30. Branching assemblies for 8 GHz ODU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 31. 13 GHz ODU (FIXEDSHIFTER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 32. 15 GHz ODU (FIXEDSHIFTER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 33. 18 GHz ODU (FIXEDSHIFTER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 34. 18 GHz ODU (VARIABLESHIFTER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 35. 23 GHz ODU (FIXEDSHIFTER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 36. 23 GHz ODU (VARIABLESHIFTER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 37. 25 GHz ODU (FIXEDSHIFTER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 38. 28 GHz ODU (FIXEDSHIFTER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 39. 38 GHz ODU (FIXEDSHIFTER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 40. Pole Mounting versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 41. Available couplers (1338 GHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 42. Available couplers (78 GHz) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 43. ODU Output flanges with external antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 44. ODU external interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 45. RF interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 46. 9400 AWY family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 47. ETSI System Characteristics 32E1 (typical values) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 48. ETSI System Characteristics 16E1 (typical values) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 49. ETSI System Characteristics 8E1 (typical values) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 50. ETSI System Characteristics 4E1 (typical values) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
3 32 38 48 49 68 70 74 75 75 76 77 79 80 81 82 83 84 85 88 89 90 93 96 98 100 106 106 107 107 108 109 110 110 111 111 112 112 112 113 116 117 118 119 119 127 132 132 133 133
26 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 373. ECTLocal external Modem cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 374. F InterfaceRemote Modem cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 375. TD32 AC modem dipswitch setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 376. Alcatel Lower Layers utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fig. 377. Example of Product levels and associated Customer Documentation . . . . . . . . . . . . . . . .
Tab. 51. ETSI System Characteristics 2E1 (typical values) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 52. Reference documentation for dismantling and recycling detail for 9400AWY R.2 equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 53. Software products part numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 54. Typical AlcatelLucent Ethernet cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 55. Operations allowed in TCO Suite Alarms & Settings screen according to the Login profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 56. ATPC Range Rx Threshold for ETSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 57. Command priority list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 58. Command priority list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 59. Command priority list . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 60. Available loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 61. Remote Inventory AlcatelLucent standard format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 62. Remote Inventory mnemonic field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 63. Test and commissioning instruments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 64. Radio application: Capacity and modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 65. Allowed number of PDH tributaries with Ethernet port(s) enabled . . . . . . . . . . . . . . . . . . . . Tab. 66. Special items of the Tool Kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 67. Alarm Synthesis indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 68. Alarm information, general description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 69. General issues of the alarm meanings and their respective maintenance actions . . . . . . Tab. 70. IDU unit replacement procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 71. Available plugin upgrade kits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 72. Flash card upgrade carried out by one operator only for both stations . . . . . . . . . . . . . . . . Tab. 73. Compliance boundaries for 9400AWY transceivers with 1ft (30 cm) antenna: . . . . . . . . . Tab. 74. QoS based on IEEE std. 802.1p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 75. QoS based on DiffServ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 76. 9400AWY Rel.2.1.1 Documentation CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 77. Handbooks contained in the 9400AWY R.2.1.1 documentation CDROM . . . . . . . . . . . . . Tab. 78. Documentation common to AlcatelLucent Network Elements using 1320CT platform . . Tab. 79. List of symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tab. 80. List of abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
134 138 141 144 158 239 259 261 263 269 282 282 330 348 350 416 438 439 440 451 469 480 508 551 552 569 570 571 575 575
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
27 / 592
a)
28 / 592
END OF SECTION
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
31
37
67
97
127
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
29 / 592
30 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
31 / 592
32 / 592
Information in this manual is divided into the following parts: a) FRONT MATTER FRONT PAGE QUICK GUIDE The Quick guide allows to access immediately the most frequently needed operative pieces of information contained in this manual and in other related handbooks. TABLE OF CONTENTS LIST OF FIGURES AND TABLES SECTION 1: SYSTEM DESCRIPTION on page 29 This section provides general warnings, the equipment description, introduces the basic information regarding the 9400AWY Rel.2.1 HW and SW installation and commissioning, and those regarding the software management, and gives its technical characteristics. Moreover, it contains the whole logical and operative information on: provisioning of equipment items (P/Ns, equipping rules) their physical and logical position in the system unit assembly/subassembly and front panel drawings, with the description on the access point usage (connectors, visual indicators, buttons) SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL on page 139 In this section, the description of the TCO suite, and the NE functionalities available in the Craft Terminal are given. SECTION 3: INSTALLATION AND COMMISSIONING on page 307 This section provides the whole operative instructions for the equipment HW and SW installation and commissioning. SECTION 4: MAINTENANCE AND UPGRADE on page 407 This section contains the whole logical and operative information for the equipment maintenance and system SW and HW upgrade. SECTION 5: APPENDICES on page 499 In this section some additional information and instructions are given: Appendix A SafetyEMCEMFESD norms and equipment labelling Appendix B TCO suite startup special conditions Appendix C Additional SW installation operations for NE management through the NES ECT serial port Appendix D General on Ethernet port characteristics and management Appendix E ECTEquipment connection via public switched telephone network Appendix F Part lists of tool kits Appendix G Documentation guide Appendix H List of symbols and abbreviations, Glossary of terms Appendix I Customer documentation feedback Handbook print and assembly instructions This part (after handbook last page 592 ): 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 is done by AlcatelLucent factory.
b)
c)
d)
e)
f)
g)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
33 / 592
For detailed information regarding the applicability and purpose of this manual, please refer to para.57.1 on page 567 WARNING: Ed.02 of this manual is validated in conjunction with SWP final version V2.1.1 only. Information relevant to SWP versions different from V2.1.1 , if any, must be considered preliminary, subject to change and without any obligation on the part of AlcatelLucent.
Following information can be useful for users owing the previous edition of this manual. Other users can simply ignore it. This edition has been made for the following major changes: elimination of information regarding the oldtype Data plugin (2 Fast Ethernet ports), throughout the whole manual updated information regarding the Flash Cards on pages 93 to 95 updated information regarding the Graphical User Interface, throughout the whole manual, according to final Version V2.1.1 improved description of ECT & NE upgrade from V2.1.0 to V2.1.1 from page 495 appendix Documentation Guide from page 567 updated for new CDROM and handbooks INFORMATION FOR ALCATELLUCENT INTERNAL USE ONLY ED 02 DATE CHANGE NOTE (yymmdd) (ECO) 080125 00000 57267 APPRAISAL AUTHORITY M.Nosari, C.Van Kerrebroeck ORIGINATOR E.Corradini
34 / 592
a)
Please refer to Appendix A on page 501 to obtain details regarding following information: Safety rules: TOPIC General rules Dangerous Electrical Voltages WARNING LABEL ON EQUIPMENT
Risk of explosion
b)
Identical or similar information on Personal Computer, WorkStation etc., other than AlcatelLucents, loaded with software applications described in this or other Handbooks, is supplied in the Constructors technical documentation.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
35 / 592
ELASTICIZED BAND COILED CORD Fig. 1. Antistatic protection device kit c) Screw fixing In normal operation conditions, all screws (for unit box closing, cable fixing, etc.) must be always tightened to avoid item detachment and to ensure the equipment EMIEMC performance. The screw tightening torque must be:
36 / 592
12 SYSTEM OVERVIEW
All 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 1st level description of the equipment architecture and system configurations of the 9400AWY Rel.2.1; it includes the following main parts: Introduction, herebelow Equipment architecture, on page 39 System configurations, on page 50 Equipment Craft Terminal and TCO Suite, on page 54 Flash Card types and content, on page 56 General on equipment installation and SWP installation and management, on page 58
12.1 Introduction
The 9400AWY is a family of digital Point to Point microwave PDH and Ethernet radio systems covering the frequency range from 7 GHz to 38 GHz, consisting of an Indoor Unit (IDU) providing the baseband processing and tributaries interfaces as well as service channel and supervision, and an Outdoor Unit (ODU). IDU and ODU are connected with a single standard coaxial cable (max length specified in para.15.5 on page 135 ) carrying the main traffic, the remote power supply voltage for the ODU and auxiliary information. As shown in Fig. 2. below, one 9400AWY radio link is composed by two 9400AWY Network Elements (ULS NE), having the same hardware and software configurations, with the exception of the go and return channel frequencies (complementary to each other), and the supervision networks NE specific data. 9400AWY ULS NE A ETSI RADIO ODU ODU 9400AWY ULS NE B
Fig. 2. 9400AWY radio link N.B. With the exception of Chapter 32 LineUp and Commissioning on page 329, this Manual deals with the description of a single 9400AWY Network Element.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
37 / 592
ULS NE has the aim to multiplexer/demultiplexer the main tributaries: up to 32 E1 and up to four Gigabit Ethernet (GE) Tributaries (10/100/1000BT)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
with different radio modulation formats, according to the following Tab. 3. : Tab. 3. Tributaries and modulations Market Max PDH Tributaries 2xE1 4xE1 ETSI 8xE1 16xE1 32xE1 Max Ethernet Tributaries 4 x GE 4 x GE 4 x GE 4 x GE 0 Radio Modulation 4QAM 4QAM / 16QAM 4QAM / 16QAM 4QAM / 16QAM 16QAM
The main functions performed by ULS NE are the following: Multiplexer/Demultiplexer The multiplexer function receives main tributaries and generates a PDH frame. The demultiplexer function receives a PDH frame and generates main tributaries. Signal Protection switch (if any) The function provides one protection channel for the main signal against channelassociated failures for both hardware failures and temporary signals degradation or losses due to propagation effects (e.g. rain) according to equipment configuration. Radio Physical Interface (AWY) The function converts a radio frequency signal into an internal logic level signal, and vice versa (RPPI). Specifically, the following functions are performed: Modulation and Tx functions in the transmit side Demodulation and Rx functions in the receive side
ULS NE can be composed by: one radio channel (1+0 configurations); two radio channels (1+1 configurations). The 2+0 configuration is not supported.
38 / 592
12.2.1 Splitmount architecture The 9400AWY system has been designed in a split mount architecture. As shown in Fig. 3. on page 40, it consists of three main parts. Indoor Unit (IDU) Outdoor Unit (ODU) IDUODU cable(s) details in paragraph 12.2.2 on page 42 details in paragraph 12.2.3 on page 49 details in paragraph 12.2.4 on page 46
IDU and ODU are connected with a single standard coaxial cable carrying the main traffic, the remote power supply voltage for the ODU and auxiliary information. IDU The mechanical structure adopted comply with ETSI/19 standard practice. IDU units can be also inserted in a standard ETSI rack, or placed on a desk, or mounted on a wall. ODU The ODU can be installed on standard poles, wall or pedestal mount, with an appropriate fastening system, which guarantees the coarse and fine pointing, even when a faulty ODU has to be replaced. The ODU (one or two depending on the configuration 1+0 or 1+1, each one with a solar shield) incorporates the complete RF transceiver and can be associated with an integrated or separate antenna. The cabinet is a very compact and robust weatherproof (IP 67) container, designed to be compatible with hot and very sunny climatic zones. The ODU can be rapidly installed on standard poles with an appropriate fastening system. The pole mounting is the same for 1+0 or 1+1 configurations from 7 to 38 GHz. The ODU is fixed by means of quick latches. This system allows to change the ODU without altering antenna pointing. N.B. An IDU+ODU fullindoor configuration (obviously without antenna) is also available; its physical implementation is described in the Installation Handbook.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
39 / 592
IDUODU cable
ODU
IDUODU cables
NE ULS
DISTRIBUTOR SHELF (optional) C B A D
IDU
Legend: D SERVICE CHANNELS PROTECTION BOX C E1 PROTECTION BOX B IDU MAIN UNIT Ch#1 A IDU EXTENSION UNIT Ch#0 Fig. 3. 9400AWY R.2.1 splitmount system
40 / 592
Antenna CH 0 All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Antenna CH 1
COUPLER
ANTENNA
ODU (1+1) HSB with one antenna N.B. this drawing is an example referred to the coupler used in 1338 GHz configurations. Couplers used in 78 GHz configurations are shown in Fig. 44. on page 117.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
41 / 592
12.2.2 IDU (Indoor Unit) The IDU incorporates the baseband processing and offers tributaries interfaces as well as service channel and supervision. The IDU is frequencyindependent, but capacitydependent. As shown in Fig. 3. on page 40, up to 2 active subracks (the Main IDU unit and the Extension IDU unit) and some additional passive boxes are used as basic elements to build the following configurations: 1+0: this configuration includes: one Main IDU unit up to two optional IDU Distributor Shelves and necessary interconnection cables. Fig. 7. on page 44 shows the block diagram. 1+1: this configuration includes: one Main IDU unit one Extension IDU unit one E1 Protection Box one Service Channels Protection Box (only if the optional AUDIO + USER SERVICE CHANNEL plugin is equipped) up to two optional IDU Distributor Shelves and necessary interconnection cables. Fig. 8. on page 45 shows the block diagram. In 1+0 and 1+1 configuration: both the Main and the Extension IDU units, if not equipped with plugsin, are physically able to support up to 16xE1 interfaces. Such capacity can be reduced according to the Software Label employed. it is possible to accommodate different types of tributary plugin alternative to each other, exploiting the same mechanical space on the front panel: 1732xE1 plugin , allowing to support the extension to 32xE1 interfaces, to be plugged onto both Main and Extension units Enhanced DATA plugin , implementing Ethernet functionalities, and supporting 4 x 10/100/1000 baseT ports. This plugin is plugged onto the Main IDU unit only.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
independently from the tributary plugins listed above, another optional plugin, to be plugged onto the Main IDU unit only, allows the AUDIO + USER SERVICE CHANNEL functionality.
In 1+1 configuration: the Main and Extension units are interconnected by means of an auxiliary flat cable (100wires SCSI front panel connector) the protection of E1 signals at line side is achieved by the E1 Protection Box the protection of Service Channels signals at line side is achieved by the Service Channels Protection Box , provided that the AUDIO + USER SERVICE CHANNEL plugin is equipped.
42 / 592
[1]
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Main IDU unit This is a common item for 1+0 and 1+1 systems. It includes the Mux/Demux and the cable interface functions for the main channel. Onto the main unit is plugged the microprocessor unit implementing the EC (Equipment Controller) functionalities. For details, refer to para.13.3 on page 70 . Extension IDU unit This is an item specific for 1+1 systems. It includes the Mux/Demux and the cable interface functions for the spare channel. The Hitless Switch functionality (RPS RX) is embedded. For details, refer to para.13.4 on page 77 . Power supply One PSU is integrated in each of the Main and Extension units; the main characteristics are: Floating (4860) VDC nom. 20% N.B. No Fans Unit are foreseen inside the 9400AWY IDU units. Flash Card and Software Label A Flash Card (containing the system software, the Software Label, and the NE configuration, even if this configuration is almost empty ) is always plugged onto the Main unit. The Software Label allows flexibility in choosing user interfaces and modulation. For details, refer to para.13.7 on page 93 . Protection Boxes The E1 Protection Box and Service Channels Protection Box, used in 1+1 configurations, are shown in Fig. 5. and Fig. 6. below. They are passive components exploiting the splitting functions of relevant signals from/to the Main IDU and Extension IDU units and from/to the User lines, as shown in Fig. 8. on page 45 .
[2]
[3]
[4]
[5]
equipment side
equipment side
Such boxes have been designed in order to have the connectors present at User line side exactly equal to those of the 9400AWY Rel.2.0 IDU Main and Extension units. In this way, Customers wishing to replace the 9400AWY Rel.2.0 IDU platform with the 9400AWY Rel.2.1 IDU platform can do it without refurbishing the existing station cabling and DDF wiring. For details, refer to para.13.5 on page 79 (E1 Protection Box) and to para.13.6 on page 84 (Service Channels Protection Box).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
43 / 592
[6]
Distribution shelves For the physical connection at station DDF of the User signal cables to the main tributaries connectors of the IDU Main and Extension units, two main solutions are envisaged: usage of the Customer Plant Distributor racks, connected to the IDU main tributaries connectors by means of Customer own cables or cables supplied by AlcatelLucent; usage of AlcatelLucent distributor subracks, to be housed in the same rack where 9400AWY IDU shelves are installed.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
For details, please refer to the Installation Handbook. [7] IDU configurations from factory Different IDU configurations (unprotected 1+0 or protected 1+1) are available from factory: 16xE1 configurations: 16xE1 (base configuration) 16xE1 + AUDIO & USER SERVICE CHANNEL plugin 16xE1 + 4 x 10/100/1000 BaseT Ethernet plugin 16xE1 + AUDIO & USER SERVICE CHANNEL plugin + 4 x 10/100/1000 BaseT Ethernet plugin 32xE1 configurations: 32xE1 32xE1 + AUDIO & USER SERVICE CHANNEL plugin.
All subequipped configurations delivered from factory can be upgraded later by means of the specific upgrade kits, as described in chapter 47 on page 469. [8] Block diagrams
Ethernetdata plugin Ethernet plugin E3/DS3plugin 16 E1/DS1plugin 1732E1 plugin (JAIDUE1) MUX/DEMUX
ODU
IDUODU IDU ODU interface
RS232 ECT
N.B.
Ethernet and 1732E1 plugins are in alternative. Fig. 7. 9400AWY R.2.1 (1+0) IDU block diagram
44 / 592
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.
Extension IDU
Extension board (JBIDUE) E3/DS3 plug in
1732E1
ODU
IDUODU interface
E1 PROTECTION BOX
1732E1
MUX/DEMUX PSU
EPS & RPS
116E1
Interconnection cable
4 x 10/100/1000 BaseT
Ethernet data plug in Ethernet plugin data Ethernet plug inin E3/DS3 plug
1732E1
On Main IDU unit, Ethernet and 1732E1 plugins are in alternative. Fig. 8. 9400AWY R.2.1 (1+1) IDU block diagram
16 E1/DS1 plug in 1732E1 plugin (JAIDUE1)
ODU
IDUODU interface
Service Channels
PSU uP EC uP/ RC
RS232 ECT
45 / 592
12.2.3 ODU (Outdoor Unit) a) ODU type: In 9400AWY R.2.1.1, only the 64Mb V1 ETSI ODU types can be used. Note for 9400AWY R.2.0 Customers only: Neither the 32Mb ODU types (V1 and V2) nor the 64Mb V2 ODU types (used in 9400AWY R.2.0, from V2.0.5) can be used in 9400AWY Rel.2.1.1 environment. b) Air interface compatibility: frame arrangement The Air frame is the AWY format respecting the bandwidth partitioning between traffic and dedicated service channels. ODU unit The ODU consists of a cabinet including the modem + transceiver of a channel. The mechanical structure utilizes an outdoor IP67 cabinet. Two mechanical solutions are adopted: one for all frequency bands from 13 to 38 GHz, where the branching (diplexer) is internal to the ODU cabinet; the only differences among the frequency bands are related to the diplexer and the RF section; another for all frequency bands from 7 to 8 GHz, where ODU is composed by two independent units: the branching (diplexer) and the RF section (transceiver).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
c)
All configurations are available for each frequency band. The ODU presents one output port at which a single polarization full integrated antenna (30 cm or 60 cm diameter) or a waveguide for not integrated antenna connection can be connected. The ODU consists of subunits which carry out the following main functions (see Fig. 9. on page 47): [1] Modem: It consists of a baseband part and an IF part. The main functions are: [2] Cable interface: DC splitting, echo cancellation, clock recovery HDB3 coding/decoding Modulation and demodulation Digital to analog conversion Analogue filtering Upconversion in Tx side in the frequency range of 1 GHz to 2.1 GHz Downconversion in Rx side from 675 MHz to base band Control function for hardware configuration and dialog with the IDU.
FrontEnd. The main functions are: AGC IF amplification Upconversion to the RF Tx channel frequency Transmit power control range of 30 dB RF loopback (N.B.) Double mixers at Rx side (the frequency of the signal sent to the modem board is 675 MHz whatever the frequency band and shifter).
N.B.
46 / 592
[3]
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Synthesizer unit The RF LO in the overall frequency range of 3.8 GHz to 5.7 GHz The IF LO in the frequency range of 1.0 GHz to 2.1 GHz
[4] [5]
Power Supply Unit: it is screwed on the Front End box Microwave Diplexer: it is inserted between the front end and the antenna. Its scope is to filter all interfering signals and harmonics. It consists of two bandpass filters: one for the Rx and one for the Tx. The rejection between these two parts is more than 70 dB. The insertion losses are less than 2 dB.
Fig. 9. ODU block diagram d) Solar shield Even if the ODU has been designed to work without solar shield, this one is always delivered with each ODU. N.B. Note : the ODU is qualified for a room temperature of +55 0C maximum. In case of solar radiation (1120 W/m2), the maximum room temperature is reduced to +40 0C (ETS 300 01924.1). It assumes that the protection of the solar shield is 15 0C.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
47 / 592
e)
ODU configurations The ODU configurations available are: for the employment in 1+0 unprotected systems: 1+0 for the employment in 1+1 protected systems: 1+1 HSB 1+1 HSB SD 1+1 FD AP 1+1 FD DA
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Tab. 4. below depicts the corresponding radio configurations. Tab. 4. 13 to 38 GHz 4/16 QAM configurations Configuration 1+0 ODU cabinet 1 RF channeling Coupler NO Antenna 1
1+1 HSB
1/10 dB asymmetric
1+1 HSB SD
NO
1+1 FD AP
NO
1 (nonintegrated only)
1+1 FD DA
OR
NO
f)
ODU Coupler The ODU coupler (shown in Fig. 43. on page 116 for 1338 GHz bands, and in Fig. 44. on page 117 for 78 GHz bands) is used in the 1+1 HSB configuration. The 1+0 configuration is comprised of a simple diplexer inside the cabinet while the protected configurations (1+1) are always comprised of two cabinets and one 1/10 dB asymmetric coupler for HSB configuration. The couplers are connected between the cabinets and the antenna.
48 / 592
The connection between the IDU and the ODU is realized with a single coaxial cable and N50 ohm connectors (2 cables in 1+1 configurations). On this cable the following signals are present: DC voltage to the remote power supply of the ODU; HDB3 Tx signal; HDB3 Rx signal.
The HDB3 signal is an aggregate signal including the main signal, auxiliary signal and the IDUODU service channels. The bit rate of the aggregate signal is listed in the following table. Tab. 5. Bit rate of the IDUODU signal on the cable ETSI (2 to 16xE1) AWY configuration ETSI (17 to 32xE1) AWY configuration 39.168 Mbit/s 78.336 Mbit/s
The IDUODU cable is a standard coaxial cable whose characteristics are specified in para.15.5 on page 135.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
49 / 592
N.B.
12.3.1 1+0 Unprotected configurations The 1+0 unprotected terminal is made up of the following elements: one Outdoor Unit (ODU) incorporating the complete RF transceiver (modem, RF units, branching filter) and an integrated or separated antenna. The ODU is capacityindependent. one Indoor Unit (MAIN IDU unit) incorporating the baseband processing and offering tributaries interfacing as well as service channel and supervision. The IDU is frequencyindependent. one optional E1 Protection Box one optional Service Channels Protection Box one/two optional IDU Distributor Shelf/ves one IDUODU coaxial cable
Fig. 10. below shows the IDU+ODU block diagram. IDU 1+0 DISTRIBUTOR SHELF interconnections IDU MAIN UNIT IDUODU cable RT 1 x ODU
Fig. 10. 9400AWY (1+0) IDU + ODU block diagram The possible capacities and modulations depend on: the (1+0) IDU equipment provisioning (see point [7] on page 44, and and Tab. 6. on page 68) and the employed Software Label (see Tab. 23. on page 93)
50 / 592
The protected configurations allow to protect the most critical transmission paths. The 1+1 configurations include an EPS protection (in Tx and Rx side) and an Hitless Switch (at Rx side) as standard features. In the protected configuration the main traffic and service channels are automatically protected. In the following, IDU and ODU protected configurations are described in: para.12.3.2.1 below: para.12.3.2.2 on page 52 : IDU (1+1) configurations ODU (1+1) configurations
12.3.2.1 IDU (1+1) configurations The IDU (1+1) system is implemented by: one Main IDU Unit (mandatory) one Extension IDU Unit (mandatory) one E1 Protection Box (mandatory) one optional Service Channels Protection Box (mandatory if the AUDIO + USER SERVICE CHANNELS plugin is equipped) one/two optional IDU Distributor Shelf/ves cables interconnecting IDU units, protection boxes, and Distributor Shelf/ves.
The possible capacities and modulations depend on: the (1+1) IDU equipment provisioning (see point [7] on page 44, and Tab. 6. on page 68) and the employed Software Label (see Tab. 23. on page 93)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
51 / 592
12.3.2.2 ODU (1+1) Configurations According to the ODU configurations introduced in Tab. 4. on page 48, at radio level the following system implementations are available: 1+1 Hot Stand By (HSB): with Space Diversity (SD) or without space diversity 1+1 with Frequency Diversity (FD): FD double antenna AP FD one antenna AP
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.
The radio configurations are independent from the IDU (1+1) configurations described in previous para.12.3.2.1 on page 51. IDU 1+1 DISTRIBUTOR SHELF
HDB3 MODEM
ODU CH 1
IF RF
interconnections
Fig. 11. 9400AWY (1+1 HSB SD) IDU + ODU block diagram
ODU CH 1
IF RF
Coupler
1:1 0
Fig. 12. 9400AWY (1+1 HSB one antenna) IDU + ODU block diagram
52 / 592
IDU 1+1
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
ODU CH 1
HDB3 MODEM IF RF
interconnections
DISTRIBUTOR SHELF
E1 PROTEC. SERV.CHAN. BOX PROTEC.BOX
AP
Fig. 13. 9400AWY (1+1 FD Double Antenna AP) IDU + ODU block diagram
IDU 1+1
HDB3
ODU CH 1
MODEM IF RF
interconnections
DISTRIBUTOR SHELF
E1 PROTEC. SERV.CHAN. BOX PROTEC.BOX
Fig. 14. 9400AWY (1+1 FD one antenna AP) IDU + ODU block diagram
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
53 / 592
that the operator has to read before this Handbook. In this Handbook is given the general description regarding use, navigation, rules, etc., common to all the NE using the same Craft Terminal. Furthermore, the same handbook contains the detailed description of common operations as Installation and common screens as Network Element Synthesis view. The Network Element Synthesis view is the first view presented to the operator entering the application. Starting from this view it is possible to login to the NE and then to enter the EMLULS views, which directly allow to manage the Network Element. A detailed description of the 9400AWY EMLULS screens is given in the dedicated Section of this handbook: SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL on page 139
12.4.1 ECT AlcatelLucent TMN management products 1320 CT called Craft Terminals (CT) consists of a compatible personal computer and application software specially developed for monitoring transmission equipment. The CT designed to monitor a single transmission equipment is called Equipment Craft Terminal (ECT) or 1320CT. For each 9400AWY station an AlcatelLucent proprietary SWP (SoftWare Package) is employed, which depends on the productrelease and the NE (Network Element) associated to the specific configuration. 12.4.2 RECT The Remote Equipment Craft Terminal is a feature only present in the Single NE Link architecture which allows the local operator, using an ECT connected to the F or Ethernet interface of the NE, to zoom and perform a complete set of management operations on all the reachable NEs in the network. The Remote NE can be physically reached through the NMS channels or Ethernet LAN. RECT can be connected to any NE pertaining to the same area of the local NE and to any NE pertaining to different areas (assuming that the DCN network has been correctly designed and hence interarea communication is possible from networking viewpoint). Of course, due to the limitation of the physical resources in the Equipment Controller of the NE, some network design constraints must be taken into account as the total number of managed NEs (50).
54 / 592
a)
the contemporaneous presence of the RECT function and an OS is possible. The access disable flag avoids access conflict between the OS and both RECT and ECT on some operations as configuration modification and remote control with access filtering. the NE which may be remotely controlled by a RECT must be configured and must be loaded with the same SW version supporting the RECT function. A NE not supporting RECT function will refuse the incoming association issued by a RECT and the ECT displays only local information. only three RECTs can be active at a time over one NE. The coexistence of ECTs and RECTs in the whole network is guaranteed since the conflict in configuring the NEs is solved locally by the NE itself.
b)
c)
12.4.3 TCO Suite The TCO Suite is a feature that mainly allows the operator to access and configure the NE from his/her PC without the need for software installation in PC environment (i.e. running the TCO Suite directly from the SWP CDROM). TCO Suite works through web pages with simple operations available with a single mouse click. Please refer to para.22.2 on page 146 for details.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
55 / 592
Fixed Data
SOFTWARE LABEL
SW instances
Fig. 15. Flash Card content [1] Fixed Data The Software Label stored in the Flash Card (plugged into the IDU Main board as shown in Fig. 21. on page 70 and Fig. 34. on page 94) allows flexibility in choosing user interfaces and modulation as shown in Tab. 23. on page 93 The Software Label is strictly associated to the Flash Card Logistical Item, and cannot be changeable, but with Flash Card upgrade (see para.47.3 on page 479). [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 ECT to the NE is carried out. A new SWP download is envisaged whenever a new SWP package version or release (new with respect to that presently loaded in the system) is supplied to Customer (*). (*) for the meaning of SWP package version and release refer to para.57.3.2 on page 573. As supplied by AlcatelLucent factory, unless differently required by Customer, 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 the SW STANDBY, loaded with the SW version immediately previous (if any) with respect to the COMMIT one
The management of these SW instances is described in Chapter 213 Software Management on page 297.
56 / 592
[3]
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
NE data N.B. as shown in Fig. 15. on page 56, differently from SW instances, NE data are present as single instances in the Flash Card. Base configuration It is defined by Flash Card Logistical Item. It is not changeable, but with Flash Card upgrade (see para.47.3 on page 479). MIB Most (but not all) configuration data set is named MIB (Management Information Base). Such data are defined by Craft Terminal and can be changed only within the limits (Base configuration) implicitly defined by the employed Flash Card type. As supplied by AlcatelLucent factory, the NE configuration data are set to default values MIB can be saved as a file in the Craft Terminal (or OS) environment, as well can be restored in the Flash Card retrieving this file from the Craft Terminal (or OS), as described in detail in Chapter 214 MIB Management on page 301. c) NE network routing data Defined by Craft Terminal or by TCO Suite SetUp Tool, they are: 1. 2. 3. 4. Local configuration Systems local address NTP server configuration Interface configuration NMS configuration Ethernet configuration IP configuration IP Static Routing configuration OSPF AREA configuration
a)
b)
Presently, all those listed parameter are NOT stored into the MIB file. Nevertheless, it is possible to create, save and recover configuration files having the .qcml extension (for details refer to para.32.3.6 on page 341). Such a file contains (besides other data) the NE network routing data defined above. As supplied by AlcatelLucent factory, the NE network routing data are set to default values. [4] System restart and system startup The system restart (reloading of all RAMs present in the system with information stored in the Flash Card) is carried out: after the activation of a new SWP after EC/OC reset (manual of after new SWP activation) after power off/on , with 2 to 5 minutes necessary for system startup after the power on.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
57 / 592
This paragraph introduces the basic information regarding the main phases for 9400AWY HW and SW installation, and those regarding the software management, with particular emphasis on SWP release and versions upgrading situations. N.B. Before reading this paragraph, it is suggested to read Flash Card types and content (para.12.5 on page 56 ). Please refer to para.57.3.2 on page 573 for the meaning of SWP Release, Version and Patch Level.
N.B.
Information given in the following is: Main phases for 9400AWY HW and SW installation First SWP installation in PC and NE environments How to check ECT and NE SWP versions Common situations requiring ECT and/or NE upgrade Flash Card related special procedures Craft Terminal related special procedures NE configuration data change and save on page 59 on page 60 on page 62 on page 64 on page 64 on page 64 on page 65
58 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The summary procedure depicted in Fig. 16. below presumes that the SWP version loaded in factory inside the NEs Flash Card corresponds to that of the SWP CDROM delivered to Customer with the equipment. N.B. The documents with symbol are included in the same CDROM containing this manual. For Installation Handbook or Installation Guide choice, read the specific note in Tab. 77. on page 570
ECT INSTALLATION described in: Chapter 31 SWP installation in PC environment on page 309
EQUIPMENT POWERON AND COMMISSIONING described in: Chapter 32 LineUp and Commissioning on page 329 and reporting test results in document: TRS & SAT
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
59 / 592
12.6.2 First SWP installation in PC and NE environments Fig. 17. depicts the main phases for SW management, when it is loaded the first time in PC and NE environments. SWP CDROM
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
1)
CRAFT TERMINAL
2)
6) MIB
BACKUP
3)
NE SWP LOADING INTO EQUIPMENT CONTROLLER (if necessary) DURATION (about): 30 minutes with interface F 15 minutes with Ethernet interface
5) NE CONFIG.
DATA MNGT
4)
7) MIB
RESTORE
60 / 592
program management, i.e.: (1) and (2) : SWP loading from CDROM to the Personal Computer, after which the PC becomes and can be used as the Equipment Craft Terminal (abbreviated as ECT or CT) (3) NE SWP downloading from ECT toward the NetworkElements Equipment Controller (EC), if necessary (it is necessary if the NE SWversion is lower than that of the ECT) N.B. in general, firsttime system installation is carried out with the NEs flash card loaded in factory with the same SWPversion of the ECT, so that this phase is usually not necessary (4) SW downloading from EC toward the Peripheral Units, always automatic (this phase is carried out only whenever the SWversions present in the Peripheral Units are lower than those available in the ECTs SW components)
NE configuration data management: (5) NE configuration data definition and equipment lineup and commissioning (6) NE configuration data save in Equipment Craft Terminal (MIB backup) (7) NE configuration data restore from Equipment Craft Terminal (MIB restore, if necessary)
The firsttime installation can be distinguished in two main procedures: SWP installation in PC environment that includes tasks (1) and (2) mentioned above. The relevant operating instructions are given in chapter 31 on page 309 SWP download toward NE, if necessary that includes tasks (3) to (4) mentioned above. The relevant operating instructions are given in chapter 48 on page 485 NE configuration data definition and equipment lineup and commissioning that includes task (5) mentioned above. The relevant operating instructions are given in chapter 32 on page 329
At the end of the firsttime installation, the CT and NE situation is the standard one: 1) Network Element already configured with the more recent SWP version and Craft Terminal already available. NE ECT ECT release = NE release A.B.c A.B.c ECT version = NE version This is the typical situation of new installations: the Network Element SW configuration matches the available Craft Terminal SWP version, so that the NE can be loggedin and the Operator can carry out the required operations, without any incompatibility problems.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
61 / 592
12.6.3 How to check ECT and NE versions [1] How to check ECT version This check can be done with ECT not connected to any NE
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
(2)
(1)
(3)
Fig. 18. How to check ECT version 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL SYSTEM DESCRIPTION
62 / 592
[2]
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
How to check NE version Proceed as follows: 1) 2) Carry out NE Login (as described in para.22.5.2 on page 173) From the Menu Bar of the 9400AWY Main view that opens after NE Login (Fig. 87. on page 181), perform SW Download SW Status
V02.01.00
N.B.
When the equipment is shipped from factory, two SW versions are present in the flash card: that committed is the actual SW version defined by the SWP name (e.g. V2.1.1) that standby is the immediately previous SW version (e.g. V2.1.0) Fig. 19. How to check NE SW version (example)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
63 / 592
12.6.4 Common situations requiring ECT and/or NE upgrade The following situations require CT and/or NE upgrading, in order to reach the standard situation defined in point 1 ) on page 61: 1) Both Network Element and Craft Terminal already configured with a SWP version older than that made available by the a new SWP version (SAME RELEASE) ECT A.B.c NE running release = SWP release SWP CDROM A.B.d
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
A.B.c
This could be the typical situation of installations already running with A.B SWP package (e.g.2.1.0), in the case a newer version of the same A.B SWP package has to be installed (e.g.2.1.1). In this case, you must upgrade both ECT and NE as described in Chapter 49 on page 495. After that, the situation is equal to that of point 1 ) on page 61. 2) Network Element already configured with the more recent SWP version, but the Craft Terminal is not available or has a version older with respect to that of the Network Element(s). NE ECT ECT release = NE release A.B.d A.B.c ECT version < NE version In this case, carry out SWP installation in Craft Terminal environment as explained in Chapter 31 on page 309. After that, the situation is equal to that of point 1 ) on page 61. 12.6.5 Flash Card related special procedures Taking into account the information contained in the Flash Card (see para.12.5 on page 56 for explanations, if necessary), you could need to: 3) for system upgrade purposes, replace the flash card currently in use with a different type Flash Card In this case, please refer to para.47.3 on page 479. for corrective maintenance purposes, replace the faulty flash card currently in use with a spare Flash Card In this case, please refer to Chapter 46 Spare Flash Card management and replacement procedures on page 465
4)
12.6.6 Craft Terminal related special procedures If you need to: 5) deinstall AlcatelLucent SW from the PC used as Craft terminal, refer to chapter 410 on page 497.
64 / 592
It must be emphasized that , every time you change the equipment configuration data (see para.12.5 on page 56), you must always save the relevant data: a) data present in Flash Cards MIB bank [see point b ) on page 57] Data present in Flash Cards MIB bank can be saved in a MIB backup file as described in Chapter 214 on page 301. The same chapter explains how to recover MIB data from the MIB backup file. The procedures in this handbook make often reference to the MIB data restore from the MIB backup file. WARNING: read carefully para.12.6.9 below. If you change the equipment configuration data without carrying out the MIB backup save, in case of troubles you will have to create again the NE configuration data by means of a lot of individual ECT commands, wasting time and with high probability of errors. data that are not saved in the MIB backup file [see point c ) on page 57] Only NE network routing data are not saved in the MIB backup file. Nevertheless, it is possible to create, save and recover configuration files having the .qcml extension (for details refer to para.32.3.6 on page 341). Such a file contains (besides other data) the NE network routing data. WARNING: read carefully para.12.6.9 below. Procedure for .qcml file backup: 1) 2) 3) 4) launch the TCO Suite SetUp Tool , as described in para.32.3.9 on page 345 in the screen of Fig. 244. on page 346 , click on button Get configuration from NE the window in Fig. 245. on page 347 will appear. This window is the first step of the Quick Configuration Procedure (interactive) clicking repeatedly on Next buttons (without any other actions), reach Step L on page 368 and click on Save As button: configuration data are saved in a configuration_name.qcml file (provide a mnemonic name)
b)
12.6.8 NE data save after commissioning completion For the NE, create a folder containing the following files: the MIB backup file [point a ) above] the .qcml configuration file [point b ) above] the TRS & SAT MSWord file. This can be used, in the future, to compare system performance to that verified at the commissioning phase. Maintain this folder updated whenever you make changes on the NE. 12.6.9 NE data compatibility between SWP 2.1.x versions [1] MIB backup file A MIB backup file created while system was running with any SWP version < 2.1.1 can be reused on a system running with the SWP version 2.1.1. A MIB backup file created while system is running with the SWP version 2.1.1 cannot be reused on a system running with any SWP version < 2.1.1. .qcml configuration file A .qcml configuration file created while system was running with any SWP version < 2.1.1 can be reused on a system running with the SWP version 2.1.1. A .qcml configuration file created while system is running with the SWP version 2.1.1 cannot be reused on a system running with any SWP version < 2.1.1.
[2]
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
65 / 592
66 / 592
All 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 detailed operative information regarding the IDU shelfs units available with the equipment version this handbook issue is relevant to, for provisioning, installation, commissioning and maintenance purposes. Information given is relevant to assembly/subassembly and front panel drawings, as well as the usage description of the access points (connectors, visual indicators, buttons). This chapter is organized as follows: Provisioning of IDU shelves Labels affixed on the IDU on page 68 on page 69
Description of IDU Main unit on page 70 IDU Main Unit LEDs summary on page 73 Power Supply connector pinout on page 74 ECT RS232 connector pinout on page 75 OS (or ECT) 10/100BaseT connector pinout on page 75 Ethernet tributaries on page 76 Description of IDU Extension unit IDU Extension Unit LEDs summary on page 77 on page 78
Description of E1 Protection box on page 79 E1 Protection box: connector pinout on page 80 Description of Services Protection box on page 84 Alarms Housekeeping (pinout and description) NMS V.11 Audio 1 (pinout and description) NMS G.703 Audio 2 (pinout and description) User service channels (pinout and description)
Note for all provisioning tables: the Logistical Item corresponds to the Logistical Item code you can read on the IDUs label (see Fig. 20. on page 69 ) please refer to the Installation Handbook for the provisioning of cables and other items that depend on the installation choices.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
67 / 592
32E1
32E1 + AUDIO & USC
ETSI IDU MAIN UNITS (48/60V POWER SUPPLY) For 1+0 and 1+1 configurations 3DB16040ABXX
1 0 IDU 16E1 48/60V PSU
X X X X X X
3DB16058ABXX
1 0 IDU 16E1 48/60V PSU AUDIO USC
3DB16160AAXX
1 0 IDU 16E1 ENH DATA 48/60V PSU
3DB16162AAXX
1 0 IDU 16E1 ENH DATA 48/60V PSU AUDIO USC
3DB16041ABXX
1 0 IDU 32E1 48/60V PSU
3DB16059ABXX
1 0 IDU 32E1 48/60V PSU AUDIO USC
ETSI IDU EXTENSION UNITS (48/60V POWER SUPPLY) Only for 1+1 configurations 3DB16044ABXX
EXT IDU 16E1 48/60V PSU
X X X
3DB16045ABXX
EXT IDU 32E1 48/60V PSU
X X
X X
X X
3DB16103AAXX
Services Protection (Dsub44 / Dsub15)
332
333
334
335
336
337
68 / 592
This label is affixed on the back side of: the IDU MAIN unit [position (C) in Fig. 21. on page 70 ] the IDU EXTENSION unit [position (C) in Fig. 23. on page 77 ]
A B
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
69 / 592
10
11
12
13
14
15
16
17 18 Fig. 21. IDU Main Unit front and rear views Tab. 7. IDU Main Unit: external interfaces list Ref. Fig. 21. Connector or item detail Interface / Explanation
Details
Basic Interfaces (without optional plugsin) (1) SubD 3 Male Station Battery input ON/OFF switch: general power supply switch (IDU Main + its ODU) RJ45 OS (or ECT) 10/100BaseT para.13.3.2 on page 74 I O ON OFF
(2)
(3)
para.13.3.4 on page 75
(4)
Debug RJ45
(8)
N 50 ohm Female
For IDUODU cable Acknowledgement: Alarm attending pushbutton; this pushbutton turns OFF LEDs MAJ/MIN and turns ON yellow LED ATTD Equipment Controller Reset pushbutton Lamp Test pushbutton: it allows to HW test the LEDs of the unit
(9)
(10)
(11)
70 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Interface / Explanation RS232 connector for NECT serial cable 116E1 64 wires connector for 100 pin SCSI flat cable (used only in 1+1 configurations) connector for Alarms Housekeeping NMS 9 LEDs Flash Card
Details para.13.3.3 on page 75 (N.B.1) interconnection with Extension Unit, no pin usage by Customer (N.B.1) para.13.3.1 on page 73 para.13.7 on page 93 for factory use Fig. 20. on page 69
(14)
SubD 44 Female
label label
Optional Interfaces (with optional plugsin) Connectors according to the equipped plugin (if any) (N.B.3) : 4 x RJ45 Ethernet user data, when Enhanced Ethernet plugin is equipped SCSI 68 pin Female 1732 E1 64 wires, when the 1732 E1 plugin is equipped para.13.3.5 on page 76
(5)
(N.B.1)
Connectors present only when the Audio + User Service Channel plugin is equipped (N.B.3) : SubD 44 Female (6) + (7) Audio1/2 + G703_V11 User Service Channel RJ11 Female for EOW telephone Notes on next page (N.B.1)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
71 / 592
Notes to Tab. 7. (N.B.1) For connector pinout, refer to the Installation Handbook ATTENTION (caution to avoid equipment damage) The Ntype connector carries +48 DC voltage for ODU power supply. Do not connect measuring instruments directly. When no plugin equipped, the slot is closed by a metal plate (inside the panel rear side). Metal plate is mandatory to ensure EMIEMC performance
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.2)
(N.B.3)
72 / 592
Nine LEDs are present on the front panel of the IDU Main Unit [position (16) in Fig. 21. on page 70 ]:
GREEN
RED
RED
GREEN
YELLOW
GREEN
RED
RED
YELLOW
= Power ON (green) = Remote Defect Indication (red) = Minor Alarm (red) = Engineering Order Wire (bicolor: yellow if busy; green if free) = ODU Working (green) = Attended (yellow) = Major Alarm (red) = Local Defect Indication (red) = Not operative in current SWP version Fig. 22. LEDs on the IDU Main Unit front panel
[1]
ON This green LED is ON when the Station Battery is connected, the ON/OFF switch is ON, and the internal DC/DC is working properly. RDI The Remote Defect Indication is a local indication of the Remote Equipment Failure alarms requiring consequent operator intervention. It is transmitted from the remote station to the local via the aggregate radio frame. RDI is formed in the remote station by the following roots: Main Unit failure (Card Fail) Extension Unit failure (Card Fail and Card Missing, only in 1+1 configurations) Data plugin failure (Card Fail and Card Missing) 1732xE1 plugin failure (Card Fail and Card Missing) Loss of Signal from Tributaries Loss of cable from ODU (IDUODU cable loss) ODU transmitted/received power alarm (TX Fail/RX Fail) ODU incompatible TX power alarm ODU incompatible TX frequency alarm (only in 1+1 configurations) ODU incompatible shifter ODU failure (Card Fail)
[2]
[3]
MIN Minor Alarm is the sum of the alarms to which the customer associates, via ECT/NMS, a MINOR severity. EOW This LED refers to the use of the EOW. Refer to chapter 42 on page 413 for details.
[4]
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
73 / 592
[5]
[6]
ATTD The attended LED is ON when the acknowledgement button [position (9) in Fig. 21. on page 70 ] has been pushed MAJ Major Alarm is the sum of the alarms to which the customer associates, via ECT/NMS, a high severity (MAJOR or CRITICAL). LDI The Local Defect Indication (LDI) has the purpose to show Local Equipment Failure requiring consequent actions by operators. The LDI roots are: Main Unit failure (Card Fail) Extension Unit failure (Card Fail and Card Missing, only in 1+1 configurations) Data plugin failure (Card Fail and Card Missing) 1732xE1 plugin failure (Card Fail and Card Missing) Loss of Signal from Tributaries Loss of cable from ODU (IDUODU cable loss) ODU transmitted/received power alarm (TX Fail/RX Fail) ODU incompatible TX power alarm ODU incompatible TX frequency alarm ODU incompatible shifter ODU failure (Card Fail)
[7]
[8]
The lamp test pushbutton [position (11) in Fig. 21. on page 70 ] allows the HW test of all LEDs. 13.3.2 Power Supply connector pinout (MAIN and EXTENSION units) Tab. 8. Power supply connections
Pin A1 A2 A3
74 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
ODUW The ODUW led ON identifies the TX activity of the ODU connected to the MAIN unit. It is OFF in case of: IDUODU Cable Loss alarm Mute function activated ODU switchingoff command activated in 1+1 HSB configuration
13.3.4 OS (or ECT) 10/100BaseT connector pinout Tab. 10. OS (or ECT) connections
N.B.
Leds are not operative RJ45 Signal Tx + Tx Rx + Not used Not used Rx Not used Not used Color used White/Orange Orange White/Green Blue White/Blue Green White/Brown Brown RJ45 (OS side) 1 2 3 4 5 6 7 8
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
75 / 592
13.3.5 Ethernet tributaries Present on the front panel of the IDU Main Unit [position (5) in Fig. 21. on page 70 ] when the Enhanced Ethernet plugin is equipped.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
For the Ethernet user data interfaces the following table summarizes the meaning of the LEDs integrated in the RJ45 connectors: Tab. 11. RJ45 connectors leds for Ethernet user data interfaces Display Function Link and activity status
Color
Ledoff
Ledon
Led blinking
LEFT LED
Green
Link up
RIGHT LED
Yellow
activity
76 / 592
Tab. 12. IDU Extension Unit: external interfaces list Ref. Fig. 23. Connector or item detail Interface / Explanation Details
Basic Interfaces (without optional plugsin) (1) SubD 3 Male Station Battery input ON/OFF switch: general power supply switch (IDU Extension + its ODU) Lamp Test pushbutton: it allows to HW test the LEDs of the unit SCSI 68 pin Female 116E1 64 wires connector for 100 pin SCSI flat cable Audio1/2 + G703_V11 User Service Channel 3 LEDs For IDUODU cable Data Matrix codification unit identification para.13.3.2 on page 74 I O ON OFF
(2)
(3) (4)
para.44.2.1 on page 421 (N.B.1) interconnection with Main Unit, no pin usage by Customer (N.B.1) para.13.4.1 on page 78 (N.B.2) for factory use Fig. 20. on page 69
(5)
Optional Interfaces (with optional plugin) Connector present only when the 1732 E1 plugin is equipped (N.B.3) : (9) SCSI 68 pin Female 1732 E1 64 wires (N.B.1)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
77 / 592
Notes (N.B.1) For connector pinout, refer to the Installation Handbook ATTENTION (caution to avoid equipment damage) The Ntype connector carries +48 DC voltage for ODU power supply. Do not connect measuring instruments directly. When no plugin equipped, the slot is closed by a metal plate (inside the panel rear side). Metal plate is mandatory to ensure EMIEMC performance
(N.B.2)
(N.B.3)
13.4.1 IDU Extension Unit LEDs summary Three LEDs are present on the front panel of the IDU Extension Unit [position (7) in Fig. 23. on page 77 ]:
GREEN
GREEN
1) ON
2) ODU W
3) ANT
Power ON (green) This green LED is ON when the Station Battery is connected, the ON/OFF switch is ON, and the internal DC/DC is working properly. = ODU Working (green). The ODUW led ON identifies the TX activity of the ODU connected to the EXTENSION unit. It is OFF in case of: IDUODU Cable Loss alarm Mute function activated ODU switchingoff command activated in 1+1 HSB configuration = Not operative in current SWP version Fig. 24. LEDs on the IDU Extension Unit front panel
The lamp test pushbutton [position (3) in Fig. 23. on page 77 ] allows the HW test of all LEDs.
78 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Interface / Explanation
Details
Line Side
4 6
2 8
Equipment Side
Fig. 25. E1 Protection box: views of Equipment Side and Line Side connectors Tab. 13. Equipment Side and Line Side connectors of E1 Protection box Ref. Fig. 25. Line side (1) (2) (3) (4) Equipment side (5) (6) (7) (8) 116 E1 116 E1 1732 E1 1732 E1 samename connector of IDU Main unit [ (13) in Fig. 21. on page 70 ] samename connector of IDU Extension unit [ (4) in Fig. 23. on page 77 ] samename connector of IDU Main unit [ (5) in Fig. 21. on page 70 ] samename connector of IDU Extension unit [ (9) in Fig. 23. on page 77 ] SubD 37 Female 18 E1 916 E1 1724 E1 2532 E1 see para.13.5.1 on page 80 Connector Interface To be connected to
N.B.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
79 / 592
13.5.1 E1 Protection box: connector pinout Notes for all tables: for E1 tributaries the same input and output wires are used for 120 ohm (balanced) and 75 ohm (unbalanced); the selection between the two options is possible with CT/OS in 75 ohm unbalanced configuration Out Trib.n is the ground of Trib.n pins must be connected to the station DDF, directly or through distribution shelves (see Fig. 3. on page 40 ) Tab. 14. E1 tributaries (1 to 8) connector pinout pin 1
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Description Not Used IN+ IN+ IN+ IN+ IN+ IN+ IN+ IN+ Trib. Trib. Trib. Trib. Trib. Trib. Trib. Trib. GND Not Used Out+ Out+ Out+ Out+ Out+ Out+ Out+ Out+ Trib. Trib. Trib. Trib. Trib. Trib. Trib. Trib. 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
Pin # 1 2 3 4 5 6 7 8 9 10
Pin # 20 21 22 23 24 25 26 27 28 29 IN IN IN IN IN IN IN IN
Description Not Used Trib. Trib. Trib. Trib. Trib. Trib. Trib. Trib. Not Used Out Out Out Out Out Out Out Out Trib. Trib. Trib. Trib. Trib. Trib. Trib. Trib. 1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
11 12 13 14 15 16 17 18 19 30 31 32 33 34 35 36 37
80 / 592
pin 1
Description Not Used IN+ IN+ IN+ IN+ IN+ IN+ IN+ IN+ Trib. Trib. Trib. Trib. Trib. Trib. Trib. Trib. GND Not Used Out+ Out+ Out+ Out+ Out+ Out+ Out+ Out+ Trib. Trib. Trib. Trib. Trib. Trib. Trib. Trib. 9 10 11 12 13 14 15 16 9 10 11 12 13 14 15 16
Pin # 1 2 3 4 5 6 7 8 9 10
Pin # 20 21 22 23 24 25 26 27 28 29 IN IN IN IN IN IN IN IN
Description Not Used Trib. Trib. Trib. Trib. Trib. Trib. Trib. Trib. Not Used Out Out Out Out Out Out Out Out Trib. Trib. Trib. Trib. Trib. Trib. Trib. Trib. 9 10 11 12 13 14 15 16 9 10 11 12 13 14 15 16
11 12 13 14 15 16 17 18 19 30 31 32 33 34 35 36 37
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
81 / 592
Description Not Used IN+ IN+ IN+ IN+ IN+ IN+ IN+ IN+ Trib. Trib. Trib. Trib. Trib. Trib. Trib. Trib. GND Not Used Out+ Out+ Out+ Out+ Out+ Out+ Out+ Out+ Trib. Trib. Trib. Trib. Trib. Trib. Trib. Trib. 17 18 19 20 21 22 23 24 17 18 19 20 21 22 23 24
Pin # 1 2 3 4 5 6 7 8 9 10
Pin # 20 21 22 23 24 25 26 27 28 29 IN IN IN IN IN IN IN IN
Description Not Used Trib. Trib. Trib. Trib. Trib. Trib. Trib. Trib. Not Used Out Out Out Out Out Out Out Out Trib. Trib. Trib. Trib. Trib. Trib. Trib. Trib. 17 18 19 20 21 22 23 24 17 18 19 20 21 22 23 24
11 12 13 14 15 16 17 18 19 30 31 32 33 34 35 36 37
82 / 592
pin 1
Description Not Used IN+ IN+ IN+ IN+ IN+ IN+ IN+ IN+ Trib. Trib. Trib. Trib. Trib. Trib. Trib. Trib. GND Not Used Out+ Out+ Out+ Out+ Out+ Out+ Out+ Out+ Trib. Trib. Trib. Trib. Trib. Trib. Trib. Trib. 25 26 27 28 29 30 31 32 25 26 27 28 29 30 31 32
Pin # 1 2 3 4 5 6 7 8 9 10
Pin # 20 21 22 23 24 25 26 27 28 29 IN IN IN IN IN IN IN IN
Description Not Used Trib. Trib. Trib. Trib. Trib. Trib. Trib. Trib. Not Used Out Out Out Out Out Out Out Out Trib. Trib. Trib. Trib. Trib. Trib. Trib. Trib. 25 26 27 28 29 30 31 32 25 26 27 28 29 30 31 32
11 12 13 14 15 16 17 18 19 30 31 32 33 34 35 36 37
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
83 / 592
Equipment Side Fig. 26. Services Protection box: views of Equipment Side and Line Side connectors Tab. 18. Equipment Side and Line Side connectors of Services Protection box Ref. Fig. 25. Line side (1) (2) SubD 15 Female (3) (3) Equipment side (5) Audio1/2 + G703_V11 User Service Channel SubD 44 Female N.B. Audio1/2 + G703_V11 User Service Channel Alarms Housekeeping NMS samename connector of IDU Extension unit [ (6) in Fig. 23. on page 77 ] samename connector of IDU Main unit [ (6) in Fig. 21. on page 70 ] samename connector of IDU Main unit [ (15) in Fig. 21. on page 70 ] Alarms + Housekeeping NMS V.11 + Audio 1 NMS G.703 + Audio 2 User Service Channels station DDF for Alarms + Housekeeping; see para.13.6.1 on page 85 station DDF for NMS V.11 + Audio 1; see para.13.6.2 on page 88 station DDF for NMS G.703 + Audio 2; see para.13.6.3 on page 89 station DDF for User Service Channels; see para.13.6.4 on page 90 Connector Interface To be connected to
(6)
(7)
N.B.
84 / 592
The AlarmsHousekeeping SubD15 connector (pinout in following Tab. 19. ) is divided in: 3 summarizing discrete alarms equipment outputs (A_1 to A_3); see point [1] below 4 housekeeping controls equipment outputs (HK_O1 to HK_O4); see point [2] on page 86 6 housekeeping alarms equipment inputs (HK_I1 to HK_I6; see point [4] on page 87 1 common wire (COM) 1 ground (GND). N.B. the SW User Label depicted in Tab. 19. below represents the name by which each signal is identified by the External Points Management (see chapter 27 on page 247), and Quick Configuration Procedure External Input and Output Points configuration on page 367. Tab. 19. Alarms Housekeeping connector pinout pin 1 Pin 6 13 7 14 8 15 4 11 5 12 9 1 2 3 10 Signal HK_I1 HK_I2 HK_I3 HK_I4 HK_I5 HK_I6 HK_O1 HK_O2 HK_O3 HK_O4 COM A_1 A_2 A_3 GND OUTPUT OUTPUT OUTPUT / FAIL IDU FAIL ODU CH#1 FAIL ODU CH#0 Direction INPUT INPUT INPUT INPUT INPUT INPUT OUTPUT OUTPUT OUTPUT OUTPUT SW User Label CPI1 CPI2 CPI3 CPI4 CPI5 CPI6 CPO1 CPO2 CPO3 CPO4
[1]
SUMMARIZING DISCRETE ALARMS The 3 summarizing discrete alarms (equipment outputs) are defined as follows: A_1 IDU HW Failure alarm ( = IDU Main (or Extension unit) Card fail/missing + Loss of IDUODU cable + Loss of Tributaries) ODU Main Failure alarm ( = ODU Tx Failure + ODU Rx Failure) ODU Spare Failure alarm
A_2 A_3
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
85 / 592
[2]
HOUSEKEEPING CONTROLS For the 4 housekeeping controls (equipment outputs), it is possible to choose through CT not only the manual setting of each one of them, but also the association to one of the system alarms available in the CT menu lists (including: Major Alarm, Minor Alarm, Loss of Tributaries, Loss of IDUODU cable, Remote Defect Indication, Local Defect Indication, ODU alarm, Service Affecting Alarm, Signal Failure Alarm). For electrical characteristics refer to point [3] herebelow.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
[3]
SUMMARIZING DISCRETE ALARMS & HOUSEKEEPING CONTROLS ELECTRICAL CHARACTERISTICS The presence of an active output alarm corresponds to a closed relay contact with a common wire. The relay is compliant with the following electrical specification: alarm present the relay is closed: |V2| 2V, |I2| 50mA (the limit on the current defines the maximum current supported by the IDU circuit) alarm not present the relay is open: |I2| 0.2mA, |V2| 60V The limit on the voltage means that the customer is not allowed to force in this condition too large V2.
IDU
OUT n
ooo ooo
OUT 2
I1
OUT 1
V1
OUT Common
Fig. 27. Equipment outputs (summarizing and housekeeping) Note 1: logic can be independently changed for each input and output (the relay is closed when the alarm is not present and is opened when the alarm is present) through CT configuration while for Summarizing outputs the default configuration is the only possibility. Note 2: when the power supply is down (and also when the power supply is on, but the SW hasnt yet initialized the HW), all the relays of the outputs of the alarms/housekeeping are in the open state (HW default condition).
86 / 592
[4]
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
EQUIPMENT INPUTS The IDU is able to detect the status of commands coming from customers circuits. A common (in) signal is supplied by the customers circuit, and this signal is different from the one defined for equipment outputs. The customer can use two different schemes to provide the command: [case 1] relay [case 2] open collector Case 1 (relay)
IDU
ooo
in n
ooo
customer
I3 V3
in 1
out
V4
common (in)
customer ground Fig. 28. Equipment inputs relay scheme alarm present the customer relay is closed: 2V V3 0V, |I3| 10mA This means that the customers circuit guarantees that |V3| 2V and is allowed to drain from the IDU a 10mA max current; alarm not present the customer relay is open: |I3| 0.2mA. This means that the maximum current drained by the customers circuit is 0.2mA.
IDU
ooo
in n
ooo
customer
I3 V3
in 1
V4
common (in)
customer ground
Fig. 29. Equipment inputs open collector scheme The IDU supplies a suitable negative voltage to the customers circuit: alarm present the customer transistor conduces (= closed): 2V V4 0V, |I3| 10mA. alarm not present the customer transistor doesnt conduce (=open): |I3| 0.2mA. This limits the max current that the customers circuit can drain.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
87 / 592
13.6.2 NMS V.11 Audio 1 (pinout and description) The (NMS_V11+Audio1) interface has 9 pins dedicated to NMS and 6 pins dedicated to EOW analog party line. The NMS_V11 channel is a 64Kb/s; its working mode can be selected between: DTE: the data in and data out have to be synchronous, data out being the slave, CODIR (asynchronous): TX and RX are totally asynchronous.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Expected/transmitted Clock falling edge is in the middle of the data. Audio1 outputs can be squelched by CT/OS selection. Tab. 20. NMSV.11 + Audio 1 connector pinout pin 1
Description RS422 data in (+) RS422 clock in (+) RS422 data out (+) RS422 clock out (+) GND NMS Audio1 signal from user (+) Audio1 signal to user (+) GND Audio
Pin # 1 2 3 4 5 6 7 8
Pin # 9 10 11 12 13 14 15
Description RS422 data in () RS422 clock in () RS422 data out () RS422 clock out () Audio1 signal from user () Audio1 signal to user () Not used
88 / 592
The (NMS_G703+Audio2) interface has 5 pins dedicated to NMS and 6 pins dedicated to EOW analog party line. The NMS_G703 channel is a 64Kb/s; its working mode can be selected between: DTE: G703 data in and G703 data out have to be synchronous, G703 data out being the slave, CODIR (asynchronous): G703 data in and G703 data out are totally asynchronous (this mode includes DCE behavior), Inframe: this configuration both disables the NMS_G703 interface and enables the insertion/extraction into/from the first E1 of the 64Kbit/s channel comingfrom/towards the uP. The insertion/extraction is relative to any slot of the first tributary. This setting is not applicable with unframed E1. Moreover, it is also necessary that the farend E1 is enabled and successfully provisioned.
Audio2 outputs can be squelched by CT/OS selection. Tab. 21. NMSG.703 + Audio 2 connector pinout
pin 1
Description G703 data in (+) Not used G703 data out (+) Not used GND NMS Audio2 signal from user (+) Audio2 signal to user (+) GND Audio
Pin # 1 2 3 4 5 6 7 8
Pin # 9 10 11 12 13 14 15
Description G703 data in () Not used G703 data out () Not used Audio2 signal from user () Audio2 signal to user () Not used
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
89 / 592
13.6.4 User service channels (pinout and description) User service channel can be used in one of the following modes (selectable by CT/OS): 64Kb/s V11 codirectional (data+clock); 64Kb/s codirectional G.703 asynchronous (i.e. TX and RX data are not necessarily synchronous. This mode includes DCE behavior); 64Kb/s V11 contradirectional (data+clock); 9.6Kb/s asynchronous V24/V28; 4.8Kb/s asynchronous V24/V28; 9.6Kb/s V11; 4.8Kb/s V11.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The pin function is shown in the table below. Tab. 22. User service channel connector pinout
pin 1
Pin # 2 9 3 10 4 11 5 12 6 13 7 14 8 15 1 N.B.
Signal COD_RX + COD_RX COD_TX + COD_TX RX_ASY TX_ASY CC_RX + CC_RX RX_CK + RX_CK CC_TX + CC_TX CC_TCK + CC_TCK GND
Direction INPUT INPUT OUTPUT OUTPUT INPUT OUTPUT INPUT INPUT BID BID OUTPUT OUTPUT OUTPUT OUTPUT /
The use of signals is depicted in following figures Fig. 30. to Fig. 33.
90 / 592
For V11 codirectional mode, refer to Fig. 30. for the interface description vs pinout.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
USER EQUIPMENT CC_RX + CC_RX RX_CK + RX_CK CC_TX + CC_TX CC_TCK + CC_TCK
IDU AWY
DATA CLOCK
DATA CLOCK
Fig. 30. User service channel: V11 codirectional interface For V11 contradirectional DCE mode, refer to Fig. 31. for the interface description vs pinout. Note that V11 contradirectional DTE mode (as the userequipment interface) is not supported.
USER SERVICE CHANNEL V11 CONTRADIR DCE < USER USER SUBORDINATE EQUIPMENT (DTE) CC_RX + CC_RX RX_CK + RX_CK CC_TX + CC_TX CC_TCK + CC_TCK RADIO > IDU AWY DCE
DATA CLOCK
DATA CLOCK
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
91 / 592
For G.703 mode, refer to Fig. 32. for the interface description vs pinout.
USER SERVICE CHANNEL G.703 < USER USER EQUIPMENT RADIO > IDU AWY
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
COD_TX+ COD_TX
DATA&CLOCK
Fig. 32. User service channel: G.703 interface For V24/V28 mode, refer to Fig. 33. for the interface description vs pinout.
USER SERVICE CHANNEL V28 < USER USER EQUIPMENT RADIO >
IDU AWY
DATA&CLOCK
RX_ASY
TX_ASY
DATA&CLOCK
92 / 592
13.7.1 Provisioning of Flash Cards & Software Labels A Software Label (stored on the Flash Card plugged in the IDU Main board) allows flexibility in choosing user interfaces and modulation as in the following Tab. 23. : Tab. 23. Flash Cards provisioning and associated & Software Labels Supported configuration Logistical Item, Description & Software Label Int.N# & type 3DB16079ABXX : 8Mb 4 QAM FLASH CARD 2E1, 4E1 Modulation 4QAM
Software Label: 8Mb 4 QAM 2E1 3DB16080ABXX : 8Mb 4/16 QAM FLASH CARD 4E1 Software Label: 8Mb 4/16 QAM 3DB16081ABXX : 16Mb 4 QAM FLASH CARD 2E1, 4E1, 8E1 4QAM 4QAM or 16QAM 4QAM
Software Label: 16Mb 4 QAM 2E1 3DB16082ABXX : 16Mb 4/16 QAM FLASH CARD 4E1, 8E1 Software Label: 16Mb 4/16 QAM 3DB16083ABXX : 32Mb 4 QAM FLASH CARD 2E1, 4E1, 8E1, 16E1 4QAM 4QAM or 16QAM 4QAM
Software Label: 32Mb 4 QAM 2E1 3DB16084ABXX : 32Mb 4/16 QAM FLASH CARD 4E1, 8E1, 16E1 Software Label: 32Mb 4/16 QAM 2E1 3DB16085ABXX : 64Mb 16 QAM FLASH CARD 4E1, 8E1, 16E1 32E1 Software Label: 64Mb 16 QAM 4QAM 4QAM or 16QAM 16QAM 4QAM or 16QAM 4QAM
The limitations introduced by the Software Label are related only to frame structure and modulation configuration. There are no limits related to the NE Configuration type (1+0 or 1+1) . Software Label value and NE Configuration type are independent.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
93 / 592
13.7.2 Description of Flash Cards & Software Labels 13.7.2.1 General The Flash Card is housed inside the IDU Main Unit shelf [see position (17) in Fig. 21. on page 70 ]. Fig. 34. herebelow shows the FLASH CARD profile and insertion direction CONNECTOR SIDE INSERTION BOTTOM SIDE
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 34. FLASH CARD profile and insertion direction ATTENTION (caution to avoid equipment damage) Whenever you have to handle flash card(s), wear always the Antistatic protection device kit (see Fig. 1. on page 36) and connect its termination to a grounded structure, to avoid the possible damage of the flash card contents for electrostatic discharges. As shown in position (18) in Fig. 21. on page 70, a suitable metal cover, fixed to the IDU Main Unit shelf by three screws, is envisaged to ensure equipment EMIEMC performance and to avoid item detachment:
13.7.2.2 Flash Card identification The Logistical Items for the possible Flash Card types are specified in Tab. 23. on page 93 , which indicates, for each P/N, also its Software Label . Flash Card labelling is described in Fig. 35. on page 95: a) b) the Flash Card Logistical Item and Software Label are reported on the label affixed on it; moreover, the Software Label is affixed on the label present on the front panel of the IDU Main Unit (position (A) in Fig. 21. on page 70):
For this purpose, the Flash Card plastic bag contains another selfadhesive label, equal to that affixed on the Flash Card itself, that can be cut as shown below, to obtain the label to be affixed on the front panel of the IDU Main Unit flash card Software Label
c)
moreover, the Software Label can be verified by Operators Commands: see Fig. 159. on page 256 and Fig. 72. on page 166
94 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
E H A F G C H
MEANING Logistical item for Customer Logistical item for Customer, bar code 39
N.B. n.b.1
BS0731UW055
Software Label Factory Technical Code + ICS Software versions loaded in the Flash Card banks by AlcatelLucent factory Data matrix (for AlcatelLucent internal purpose)
n.b.1
n.b.2
according to Tab. 23. on page 93 see point [2] on page 56 , and point [2] on page 63 Fig. 35. Flash Card identification labels
13.7.2.3 Flash Card upgrade To replace a Flash Card with a different type, for system upgrade purpose, please refer to para.47.3 Flash Card upgrade on page 479.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
95 / 592
a b
a b
96 / 592
This chapter describes the ODU configurations, relevant provisioning and operative information for installation, commissioning and maintenance purposes: ODU general description: refer to point c ) on page 46 ODU mechanical design and identification Labels affixed on the ODU ODU configurations ODU provisioning and layouts ODU part lists and characteristics Part lists of ODUs with external diplexer Part lists of ODUs with embedded diplexer on page 98 on page 99 on page 100 on page 101 on page 104 on page 105 on page 108 on page 113 on page 119
For the Light service kit cable, please refer to para.32.10 on page 405.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
97 / 592
Tab. 25. ODU dimensions and weights embedded diplexer Type with .. TRANSCEIVER + BRANCHING
235 x 235 x 72 mm (9.25 x 9.25 x 2.8in)
BRANCHING
235 x 235 x 73.5 mm (9.25 x 9.25 x 2.9in)
TRANSCEIVER + BRANCHING
248 x 257 x 156.5 mm (9.76 x 10.1 x 6.6in)
Dimensions Weight
BRANCHING
BRANCHING IDENTIFICATION LABEL (INSIDE) (see Fig. 52. on page 126) TRANSCEIVER + BRANCHING ODU IDENTIFICATION LABEL (see Fig. 37. on page 99) TRANSCEIVER TRANSCEIVER IDENTIFICATION LABEL (see Fig. 37. on page 99)
Fig. 36. ODU types, identification, dimensions and weights The ODUs are delivered with the nose adapter in case of configurations with the separated antenna (for details, see para.14.6.4 on page 117)
98 / 592
a)
the following label is affixed externally to all types of ODU and ODUs TRANSCEIVER boxes (see Fig. 46. on page 120 and Fig. 47. on page 121):
A B
Logistical Item (shown numbers as examples) Logistical Item for Customer A Serial no (shown numbers as examples) B Logistical Item for Customer, bar code 128 Factory Serial number Factory Serial number bar code 128
TX Frequency MHz (shown numbers as Working frequency range examples) Shifter MHz (shown numbers as examples) TX Subband (shown numbers as examples) Initial SW/ICS (shown numbers as examples) PN/ICS (shown numbers as examples) C Shifter TX Subband P/N and ICS of the software loaded in factory Factory P/N + ICS Factory P/N + ICS bar code 128 Fig. 37. Label affixed on the ODU and ODUs TRANSCEIVER box b) only for ODUs with external diplexers, an additional label is placed on the branching assembly (for details refer to Fig. 50. and Fig. 52. on pages 124126).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
99 / 592
NO 1/10 dB asymmetric
2 x ODUs at 1+1 HSB SD same frequency 1+1 FD AP 2 x ODUs at different frequencies 2 x ODUs at different frequencies
NO
2 x antennas single polar Protection against failures. Improvement of performances versus multipath propagation
NO
1 x antenna double polar 2 x antennas single polar in AP configuration (same or crossed polarization)
1+1 FD DA N.B.
NO
Alternate Polar Double Antenna Frequency diversity Hot Stand By Space Diversity
100 / 592
14.4.1 Provisioning of ODU (1+0) a) b) ODU transceiver: see para.14.5 on page 104 Antenna: see paragraphs: c) 14.6.1 on page 114 (1+0 configuration with full integrated antenna) or 14.6.4 on page 117 (Configuration with separated antenna)
Part list of full integrated antennas, ODU accessories and installation materials: refer to Installation Handbook
14.4.2 Provisioning, layouts and connections of ODU (1+1) 14.4.2.1 ODU (1+1) HSBSD or FDDA AP with two antennas Antenna (2) Antenna (1)
Figure shows the solution with full integrated antennas; antennas can be also external (see point b ) herebelow) Fig. 38. Station layout of ODU (1+1) HSBSD or FDDA AP with two antennas
Equipment provisioning: a) b) ODU transceiver (x2): see para.14.5 on page 104 Antenna (x2): see paragraphs: c) 14.6.1 on page 114 (1+0 configuration with full integrated antenna) or 14.6.4 on page 117 (Configuration with separated antenna)
Part list of full integrated antennas, ODU accessories and installation materials (x2): refer to Installation Handbook
ODU Equipment block diagram: see: Fig. 11. on page 52 (1+1 HSBSD) Fig. 13. on page 53 (1+1 FDDA AP)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
101 / 592
ODU CH 0
ODU CH 1
this drawing is an example referred to the coupler used in 1338 GHz configurations. Couplers used in 78 GHz configurations are shown in Fig. 44. on page 117. Fig. 39. Station layout of ODU (1+1) HSB with one antenna
Equipment provisioning: a) b) ODU transceiver (x2): see para.14.5.2 on page 108 Antenna and coupler: see paragraphs: 14.6.2 on page 116 [1+1 HSB configuration with coupler and full integrated antenna (1338 GHz)] 14.6.3 on page 117 [1+1 HSB configuration with coupler and full integrated antenna (78 GHz)]
c)
Part list of full integrated antennas, ODU accessories and installation materials: refer to Installation Handbook
ODU Equipment block diagram: see: Fig. 12. on page 52 (1+1 HSB)
102 / 592
14.4.2.3 ODU (1+1) FDAP with one double polar external antenna
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 40. Station layout of ODU (1+1) FDAP with one double polar external antenna Equipment provisioning: a) b) ODU transceiver (x2): see para.14.5 on page 104 Connection of Double Polar External Antenna: see para.14.6.4 on page 117 (Configuration with separated antenna) Part list of ODU accessories and installation materials: refer to the Installation Handbook
c)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
103 / 592
Technical Description
Note: The ODU Logistical Items listed in the following tables include always the solar shield. For: ODUs with external diplexer, refer to para.14.5.1 on page 105 ODUs with embedded diplexer, refer to para.14.5.2 on page 108
104 / 592
14.5.1.1 General The diplexer included in the available BRANCHING assemblies refers to ITUR F.385, 386 and RF special CUSTOMERS channelling with Tx/Rx separation specified in following Tab. 28. and Tab. 30. Each diplexer is a three port passive device with two bandpass filters as described hereafter (physical arrangement is shown in Fig. 50. on page 124):
Each BRANCHING assembly has two different variants by duplex spacing, depending on the RF_Tx output frequency band as described on the table below : 3DB Variant 3DB xxxxx AAXX 3DB xxxxx ABXX Channel 1_1p 2_2p
The arrangement between each filters on the same branching device is described below:
f1 2.5 dB
foL
f2
f3
foH
f4 frequencies
70 dB
attenuation
WARNING:
fr SHIFTER
f1, f2, f3 and f4 frequencies of the branching filters refer to the extreme channel frequencies and not to the cutoff frequencies of the filters.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
105 / 592
14.5.1.2 Part list of 7 GHz ODUs with external diplexer Tab. 27. 7 GHz Transceiver assemblies ODU Type ODU 64Mb Logistical Item 3DB 06691ABXX 3DB 06692ABXX Technical Description ODU 64MB 9470 7.1 7.75 GHz LHB ODU 64MB 9470 7.25 7.9 GHz UHB
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Tab. 28. Branching assemblies for 7 GHz ODU N.B. shifter value choice to be done by Craft Terminal
Central Freq. MHz Filter 1 MHz (Lower Band) Low Limit f1 7107,0 7428,0 7484,0 7442,0 7442,0 7498,0 7498,0 7124,5 7194,5 7249,5 7319,5 7274,5 7344,5 7424,5 7494,5 7549,5 7619,5 7574,5 7644,5 7187,0 7443,0 7499,0 7414,0 7470,0 7107,0 7163,0 7428,0 7540,0 High Limit f2 7163,0 7512,0 7568,0 7526,0 7520,0 7582,0 7576,0 7194,5 7264,5 7319,5 7389,5 7344,5 7414,5 7494,5 7564,5 7619,5 7689,5 7644,5 7714,5 7243,0 7527,0 7583,0 7498,0 7554,0 7191,0 7247,0 7540,0 7652,0 Filter 2 MHz (Upper Band) Low Limit f3 7261,0 7582,0 7638,0 7596,0 7602,0 7652,0 7658,0 7285,5 7355,5 7410,5 7480,5 7435,5 7505,5 7585,5 7655,5 7710,5 7780,5 7735,5 7805,5 7355,0 7611,0 7667,0 7596,0 7652,0 7303,0 7359,0 7673,0 7785,0 High Limit f4 7317,0 7666,0 7722,0 7680,0 7680,0 7736,0 7736,0 7355,5 7425,5 7480,5 7550,5 7505,5 7575,5 7655,5 7725,5 7780,5 7850,5 7805,5 7875,5 7411,0 7695,0 7751,0 7680,0 7736,0 7387,0 7443,0 7785,0 7897,0
BRANCHING ASSEMBLY Logistical Item 3DB 10060 AAXX 3DB 06774 AAXX 3DB 06774ABXX 3DB 06775 AAXX 3DB 06775ABXX 3DB 06780 AAXX 3DB 06780ABXX 3DB 06781 AAXX 3DB 06781ABXX 3DB 06782 AAXX 3DB 06782ABXX 3DB 06783 AAXX 3DB 06783ABXX 3DB 06784 AAXX 3DB 06784ABXX 3DB 06785 AAXX 3DB 06785ABXX 3DB 10059 AAXX 3DB 06776 AAXX 3DB 06776ABXX 3DB 06777 AAXX 3DB 06777ABXX 3DB 06778 AAXX 3DB 06778ABXX 3DB 06779 AAXX 3DB 06779ABXX Technical Description BRANCHING 7GHZ ...
... CH11P P.SH. 154_C MHz ... CH11P P.SH. 154_A MHz ... CH22P P.SH. 154_A MHz ... CH11P P.SH.154_B MHz ... CH11P P.SH.160 MHz ... CH22P P.SH.154_B MHz ... CH22P P.SH.160 MHz ... CH11P P.SH.161_A MHz ... CH22P P.SH.161_A MHz ... CH11P P.SH.161_B MHz ... CH22P P.SH.161_B MHz ... CH11P P.SH.161_C MHz ... CH22P P.SH.161_C MHz ... CH11P P.SH.161_D MHz ... CH22P P.SH.161_D MHz ... CH11P P.SH.161_E MHz ... CH22P P.SH.161_E MHz ... CH11P P.SH.161_F MHz ... CH22P P.SH.161_F MHz ... CH11P P.SH.168_B MHZ ... CH11P P.SH.168 MHZ ... CH22P P.SH.168 MHZ ... CH11P P.SH.182 MHZ ... CH22P P.SH.182 MHZ ... CH11P P.SH.196 MHZ ... CH22P P.SH.196 MHZ ... CH11P P.SH.245 MHZ ... CH22P P.SH.245 MHZ
Shifter MHz
154 154 154 154 160 154 160 161 161 161 161 161 161 161 161 161 161 161 161 168 168 168 182 182 196 196 245 245
7212,0 7547,0 7603,0 7561,0 7561,0 7617,0 7617,0 7240,0 7310,0 7365,0 7435,0 7390,0 7460,0 7540,0 7610,0 7665,0 7735,0 7690,0 7760,0 7299,0 7569,0 7625,0 7547,0 7603,0 7247,0 7303,0 7606,5 7718,5
106 / 592
Tab. 29. 8 GHz Transceiver assemblies ODU Type ODU 64Mb Logistical Item 3DB 06693ABXX 3DB 06694ABXX Technical Description ODU 64MB 9470 7.7 8.4 GHz LHB ODU 64MB 9470 8.0 8.5 GHz UHB
Tab. 30. Branching assemblies for 8 GHz ODU N.B. shifter value choice to be done by Craft Terminal
Filter 1 MHz (Lower Band) Low Limit f1 8286.0 8282.5 8328.0 8324.5 8204.217 8274.189 8064.0 8148.0 7905.0 8017.0 7749.755 7947.835 7738.635 7732.875 8066.435 7851.475 7862.965 8063.740 305.560 213.5 8147.0 7851.845 8035.0 8046.0 8248.0 7970.075 8157.405 8275.635 8259.0 3DB 10103 AAXX ... CH11P P.SH. 213.5 MHZ 8162.795 7851.475 8044.195 High Limit f2 8328.0 8324.5 8370.0 8366.5 8274.189 8344.161 8162.0 8246.0 8024.0 8136.0 Filter 2 MHz (Upper Band) Low Limit f3 8405.0 8408.5 8447.0 8450.5 8355.831 8425.803 8272.0 8356.0 8171.0 8283.0 High Limit f4 8447.0 3DB 06789 AAXX 126 119 126 151.610 151.610 208 208 266 266 294.440 305.560 311.320 311.320 294.440 8366.5 8408.5 8408.5 8315.010 8384.982 8217.0 8301.0 8097.5 8209.5 8450.5 8489.0 3DB 06789ABXX 8492.5 8425.803 8495.775 8370.0 8454.0 8290.0 8402.0 8145.915 8157.035 8162.795 8281.395 8264.515 3DB 06786ABXX ... CH22P P.SH.294/305/311 MHZ 3DB 06786 AAXX ... CH11P P.SH.294/305/311 MHZ 3DB 06787 AAXX 3DB 06787ABXX 3DB 10073 AAXX 3DB 10073ABXX 3DB 06788 AAXX 3DB 06788ABXX ... CH22P P.SH.126 MHz ... CH11P P.SH.151 MHz ... CH22P P.SH.151 MHz ... CH11P P.SH.208 MHZ ... CH22P P.SH.208 MHZ ... CH11P P.SH.266 MHZ ... CH22P P.SH.266 MHZ ... CH11P P.SH.126 MHz ... CH22P P.SH.119 MHz
Shifter MHz
119
8366.5
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
107 / 592
14.5.2 Part lists of ODUs with embedded diplexer The following tables report the Logistical Items of the available ODUs (with embedded diplexer) with the following information from left to right: Column 1: Column 1bis : Column 2 & 3: Column 4 to 7: Shifter (MHz) Central Frequency (MHz) Tx and Rx subbands Tx & Rx frequency ranges at RF interface (MHz)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
For some frequency ranges, two types of ODU are envisaged: ODU with fixed shifter ODU with variable shifter: the shifter value can be set by Craft Terminal
14.5.2.1 Part list of 13 GHz ODU with embedded diplexer Tab. 31. 13 GHz ODU (FIXEDSHIFTER) RF interface (MHz) 1
Shifter
2 Tx 1 2 1p 2p
3 Rx 1p 2p 1 2
Logistical Item
108 / 592
2 Tx 1 2 1p 2p 1 2 1p 2p 1 2 1p 2p 1 1p 1 1p
3 Rx 1p 2p 1 2 1p 2p 1 2 1p 2p 1 2 1p 1 1p 1
4 RF Tx min 14630 14760 14945 15075 14500 14710 14920 15130 14400 14625 14890 15115 14500 15144 14500 15228
5 RF Tx max 14766 14899 15081 15214 14724 14941 15144 15361 14635 14860 15125 15350 14700 15344 14620 15348
6 RF Rx min 14945 15075 14630 14760 14920 15130 14500 14710 14890 15115 14400 14625 15144 14500 15228 14500
7 RF Rx max 15081 15214 14766 14899 15144 15361 14724 14941 15125 15350 14635 14860 15344 14700 15348 14620
Logistical Item
3CC13692ABXX 3CC13693ABXX 3CC13694ABXX 3CC13695ABXX 3CC13696ABXX 3CC13697ABXX 3CC13698ABXX 3CC13699ABXX 3CC13704ABXX 3CC13705ABXX 3CC13706ABXX 3CC13707ABXX 3CC13709ABXX 3CC13711ABXX 3CC13712ABXX 3CC13713ABXX
315 15013 15144,5 14612 14825,5 420 15032 15245,5 14517,5 14742,5 490 15007,5 15232,5 14600 644 15244 14560 728 15288
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
109 / 592
14.5.2.3 Part lists of 18 GHz ODU with embedded diplexer Tab. 33. 18 GHz ODU (FIXEDSHIFTER) RF interface (MHz) 1
Shifter All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
2 Tx 1 2 1p 2p 1 1p
3 Rx 1p 2p 1 2 1p 1
Logistical Item
Tab. 34. 18 GHz ODU (VARIABLESHIFTER) N.B. shifter value choice to be done by Craft Terminal RF interface (MHz) 1
Shifter
1bis CF 17951,5
2 Tx
3 Rx
4 RF Tx min 17703
7 RF Rx max 19208
Logistical Item
1p 17700 18182 2p 18180 18711 1 18710 19190 2 19190 18690 18201 18679 19700 18200 19211 19687
3CC14780ABXX
3CC14781ABXX
3CC14782ABXX
3CC14783ABXX
110 / 592
2 Tx 1 2 1p 2p
3 Rx 1p 2p 1 2
Logistical Item
Tab. 36. 23 GHz ODU (VARIABLESHIFTER) N.B. shifter value choice to be done by Craft Terminal RF interface (MHz) 1
Shifter
1bis CF 21509,5
2 Tx
3 Rx
4 RF Tx min 21200
5 RF Tx max 21819 21787 22360 22400 22368 23019 23019 23410 23600 23600
6 RF Rx min 22400 22430 23302 22981 23013 21200 21200 22252 21781 21781
7 RF Rx max 23019
Logistical Item
1200 1232 1050 1200 1232 1200 1232 1050 1200 1232
1p 21198 22252 2p 21781 21781 22400 1 22400 23302 2 22981 23013 21819 22360 22400 22368 23019 23410 23600 23600 21819
3CC14776ABXX
3CC14777ABXX
3CC14778ABXX
3CC14779ABXX
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
111 / 592
14.5.2.5 Part list of 25 GHz ODU with embedded diplexer Tab. 37. 25 GHz ODU (FIXEDSHIFTER) RF interface (MHz) 1
Shifter All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
2 Tx 1 2 1p 2p
3 Rx 1p 2p 1 2
Logistical Item
14.5.2.6 Part list of 28 GHz ODU with embedded diplexer Tab. 38. 28 GHz ODU (FIXEDSHIFTER) RF interface (MHz) 1
Shifter
2 Tx 1 2 1p 2p
3 Rx 1p 2p 1 2
Logistical Item
14.5.2.7 Part list of 38 GHz ODU with embedded diplexer Tab. 39. 38 GHz ODU (FIXEDSHIFTER) RF interface (MHz) 1
Shifter
2 Tx 1 2 1p 2p
3 Rx 1p 2p 1 2
Logistical Item
112 / 592
The ODU can be connected to: a full integrated antenna of 30 cm (1FT) or 60 cm (2FT) or 90 cm (3FT) or 120 cm (4FT) or 180 cm (6FT) diameter, in Full Integrated configuration (pole mounting is delivered with the antenna). N.B. For the list of full integrated antennas (types, P/Ns and related information), please refer to the Installation Handbook.
a separated antenna, if larger diameters are necessary. In this case, the antenna is interconnected by a flextwist directly to the ODU, or the coupler, depending on the protection used.
For the outdoor section the following 1+1 configuration are presently implemented: HSB configuration is available with a 1 dB/10 dB asymmetrical coupler and 1 antenna: this configuration optimizes the infrastructure using only one antenna, a 10 dB coupling has been chosen to minimize the losses on the normal path (1 dB only). without coupler and 2 antennas: this configuration adds a natural Space Diversity and improves the link budget avoiding coupler losses on the standby path. without coupler and 1 dual polarization antenna: this configuration allows a polarization diversity, minimizes the antenna and avoids coupler losses on the standby path.
The pole mounting versions are given in the following Tab. 40. for each configuration: Tab. 40. Pole Mounting versions Version 1+0 with full integrated antenna 1+1 HSB configuration with coupler and full integrated antenna (1338 GHz) 1+1 HSB configuration with coupler and full integrated antenna (78 GHz) Configuration with separated antenna see para 14.6.1 page 114 14.6.2 page 116 14.6.3 page 117 14.6.4 page 117
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
113 / 592
14.6.1 1+0 configuration with full integrated antenna The following Fig. 41. and Fig. 42. show the 1+0 configuration with a 30 cm (1FT) antenna in both vertical and horizontal configurations. The modification of the polarization is obtained by rotating the ODU and the nose of the antenna. antenna WITH EXTERNAL DIPLEXER
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
in some ODU mechanical arrangements, the N connector (for IDUODU cable insertion) can be in the opposite position with respect to that depicted in figure above. In any case, this N connector is always positioned on the 450 side of ODU assembly. Fig. 41. View of ODU with full integrated antenna (V polarization)
114 / 592
antenna
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
in some ODU mechanical arrangements, the N connector (for IDUODU cable insertion) can be in the opposite position with respect to that depicted in figure above. In any case, this N connector is always positioned on the 450 side of ODU assembly. Fig. 42. View of ODU with full integrated antenna (H polarization)
Please refer to the Installation Handbook, for the P/N of full integrated antenna pole mounting, and for detailed assembly drawings.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
115 / 592
14.6.2 1+1 HSB configuration with coupler and full integrated antenna (1338 GHz) See Fig. 43. below. The 2 ODUs are interconnected through a 1 dB /10 dB coupler. The coupler is fixed on the 1+0 pole mounting with 4 catches. The 2 ODUs are connected to the coupler with their catches. The modification of the polarization is done on the coupler by rotating rings at antenna port and on the antenna by rotating the nose (the ODUs are always in the same position). Different couplers are available, as shown in Tab. 41. herebelow:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Tab. 41. Available couplers (1338 GHz) N.B. This list is given for general information purpose. For P/Ns and possible additional and related information, please refer to the Installation Handbook. Frequency band 13, 15 GHz 18, 23, 25 GHz 28, 38 GHz Coupler Coupler type 10 dB 10 dB 10 dB Waveguide (3 ports) WR 62 WR 42 WR 28 antenna Coupling loss 1 dB / 10 dB 1 dB / 10 dB 1 dB / 10 dB
535 mm (21.83 in) 620 mm (24.41 in) COUPLER WEIGHT = 4.3 Kg about Fig. 43. Coupler (1338 GHz)
COUPLER VIEW
116 / 592
14.6.3 1+1 HSB configuration with coupler and full integrated antenna (78 GHz)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Tab. 42. Available couplers (78 GHz) N.B. For coupler P/N and assembly drawings of ODUs + coupler, please refer to the Installation Handbook Coupler type 10 dB 521 Waveguide (3 ports) WR 112 Coupling loss 1 dB / 10 dB
235
max 126
COUPLER WEIGHT = 6 Kg about Fig. 44. Coupler (78 GHz) example 14.6.4 Configuration with separated antenna The ODU is fixed on a dedicated pole mounting for separated antenna. A nose adapter (different Logistical Items depending on the waveguide dimension) is used to connect the ODU and the flextwist.
WITH EXTERNAL DIPLEXER WITH EMBEDDED DIPLEXER
Fig. 45. Nose adapters for ODU with separated antenna Please refer to the Installation Handbook, for the P/Ns of nose adapters and not integrated antenna pole mounting, and for detailed assembly drawings.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
117 / 592
Please note that the use of 600 mm flex twist is not suggested for antennas bigger than 3ft (90 cm diameter), due to mechanical reasons. The suggested way to make the RF connection is to use the elliptical wave guide fitted with flanged connectors. Tab. 43. ODU Output flanges with external antenna N.B. This list is given for general information purpose. For flextwist P/Ns and possible additional and related information, please refer to the Installation Handbook. ODU Output Flange A UDR84 9470 AWY 78 UBR84 9413 AWY 12.7 13.3 9415 AWY 14.2 15.4 9418 AWY 17.7 19.7 9423 AWY 21.2 23.6 9425 AWY 24.5 26.5 9428 AWY 27.3 31.3 9438 AWY 37.0 40.0 UBR220 R220 WR42 PBR220 UBR220 PBR220 UBR120 UBR140 R84 R120 R140 WR112 WR75 WR62 C.E.I. R84 E.I.A. WR112 FLEXTWIST B PDR84 or: PBR84 PBR120 PBR140 UBR84 UBR120 UBR140 PBR84 PBR120 PBR140 C UBR84
Suggested Antenna Flange
D PBR84
UBR320
R320
WR28
PBR320
UBR320
PBR320
N.B.
If the flextwist is not provided by AlcatelLucent, the user must carefully choose the type of the connection guide in order to limit as much as possible galvanic couples between antenna/flextwist and flextwist/ODU contact surfaces that can induce rust. For this purpose please note that the surfaces are: chromiumplated at ODUs output flange side tinplated at flextwists flange side
118 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Concerning the interface between the ODU output flange and the suggested antenna flange, the following Tab. 43. details for each product the standard wave guide to be used and the suggested flange for the external antenna.
This paragraph gives operative information, for installation, commissioning and maintenance purposes regarding: ODUs with embedded or external diplexer ODUs with external diplexer (additional information) herebelow on page 123
For the Light service kit cable, please refer to para.32.10 on page 405. 14.7.1 Operative information on ODUs with embedded or external diplexer 14.7.1.1 General, views and access points Fig. 46. (for ODUs with embedded diplexer) and Fig. 47. (for ODUs with external diplexer) on pages 120121 show ODU views and access points. The external interfaces are listed in Tab. 44. below, with the corresponding connector. Tab. 44. ODU external interfaces Ref. in Fig. 46. and Fig. 47. (1) (2) (3) Interface Connector Further information Tab. 45. herebelow
RF interface for connection of antenna or coupler Connector for IDU/ODU cable Connector for Light service kit cable
Tab. 45. RF interface FREQUENCY GHz Waveguide type N.B. 78 WR112 1315 WR62 1825 WR42 2838 WR28
N.B.
For detailed operative information regarding: equipment installation, please refer to the Installation Handbook equipment commissioning, please refer to chapter 32 on page 329 equipment maintenance, please refer to section 4 on page 407.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
119 / 592
TRANSCEIVER + BRANCHING
(A)
(A) (3)
(A)
(2)
(A) Levers (4) to fix/unfix ODU assembly to antenna or coupler (1) (2) (3) (4) RF interface for connection of antenna or coupler Connector for IDU/ODU cable Connector for Light service kit cable ODU identification label (see Fig. 37. on page 99) in some ODU mechanical arrangements, the N connector (for IDUODU cable insertion) can be in the opposite position with respect to that depicted in figure above. In any case, this N connector is always positioned on the 450 side of ODU assembly. Fig. 46. Views of ODUs with embedded diplexer
WARNING:
120 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
(4)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
BRANCHING
(3)
(A) 4 levers to fix/unfix branching assembly (diplexer) to transceiver (B) 4 levers to fix/unfix branching assembly (diplexer) to antenna or coupler (1) (2) (3) (4) RF interface for connection of antenna or coupler Connector for IDU/ODU cable Connector for Light service kit cable TRANSCEIVER identification label (see Fig. 37. on page 99) in some ODU mechanical arrangements, the N connector (for IDUODU cable insertion) can be in the opposite position with respect to that depicted in figure above. In any case, this N connector is always positioned on the 450 side of ODU assembly. Fig. 47. Views of ODUs with external diplexer
WARNING:
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
121 / 592
7 8 1 12 9 2
KEY
6 11 10 3 5 4
Fig. 48. ODU LEMO connector pinout 14.7.2 ODU hardware settings No hardware settings are envisaged on ODUs with embedded diplexer, while on ODUs with external diplexer a setting allows to choose the halfband (LOW or HIGH) for TX (see para.14.7.4 on page 123 for details). 14.7.3 ODU identification Through the Solar Shield window are visible the ODU or TRANSCEIVER identification label and the Vertical or Horizontal polarization mounting. In case of ODUs with external diplexer, the BRANCHING identification label (Fig. 52. on page 126) can be viewed only separating the TRANSCEIVER from the BRANCHING.
122 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
14.7.4.1 ODU composition As shown in Fig. 49. below, the 9470AWY ODU assembly is composed, unlike the existing ones in the other frequency bands, by two boxes, one for diplexer system (BRANCHING) and the other for the all other active functions (TRANSCEIVER) connected together to form the ODU. An ORING present in the TRANSCEIVER box guarantees the ODU assembly pressurization. N.B. This is a conductive ORING and must be left dry. Do not wet it with silicon grease (silicon grease must be used only on Oring between ODU and antenna).
BRANCHING
TRANSCEIVER
ORING
Fig. 49. Composition of ODUs with external diplexer The TRANSCEIVER box is very similar to the existing ones 9400AWY ODU used in the other frequency bands, but without the diplexer system. The BRANCHING box provides the interface between the pole mounting/antenna and the TRANSCEIVER. The favorite solution foresees the possibility to change in field a spare part TRANSCEIVER without disconnecting the BRANCHING box from the pole mounting/antenna. The TRANSCEIVER and BRANCHING boxes fixing and unfixing are obtained through the four levers (A) shown in Fig. 47. on page 121.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
123 / 592
14.7.4.2 TRANSCEIVER and BRANCHING boxes coupling Fig. 50. below shows the TRANSCEIVER and BRANCHING boxes coupling surfaces:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
(B) (HIGH FREQ) and (C) (LOW FREQ) RF interfaces on BRANCHING box (D) (TX) and (E) (RX) RF interfaces on TRANSCEIVER box
The TRANSCEIVER and BRANCHING boxes can be coupled in two alternative ways (1800rotated with respect to each other): BRANCHING boxs (B) (HIGH FREQ) coupled to TRANSCEIVER boxs (D) (TX) in this case the TX part of the transceiver uses the HIGH frequency range of the Shifter set by Craft Terminal (see field D in Fig. 52. on page 126); obviously the RX part of the transceiver uses the corresponding LOW frequency range; BRANCHING boxs (C) (LOW FREQ) coupled to TRANSCEIVER boxs (D) (TX) in this case the TX part of the transceiver uses the LOW frequency range of the Shifter set by Craft Terminal (see field D in Fig. 52. on page 126); obviously the RX part of the transceiver uses the corresponding HIGH frequency range.
(D)
TRANSCEIVER
(C) (E)
Fig. 50. ODUs TRANSCEIVER and BRANCHING boxes coupling surfaces
124 / 592
N.B.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
There is only one possible way to couple the BRANCHING box and the TRANSCEIVER box: there is a mistakeproofing put by the factory on the TRANSCEIVER box, whose position depends on the type of transceiver (low or high band, as shown in Fig. 51. below) to ensure that the association with the BRANCHING box is always the right one. Notice that this feature was not available at the very beginning of the 7/8 GHz introduction.
mistakeproofing
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
125 / 592
A B C
154_B 160
MEANING Equipment Acronym & Alcatel Logo European Community logo Notified body Not harmonized frequency logo 2002/96/EC WEEE (Waste Electrical and Electronic Equipment) Logo (see para.15.10.3 on page 137)
PN/ICS 3DB 06775 AAAA 01 (example) A Logistical Item 3DB 06775 AAXX (example) B S/N CW 050609001 (example) C
Factory Technical Code + ICS Factory Technical Code + ICS, bar code 128 Logistical Item for Customer Logistical Item for Customer, bar code 128 Factory Serial number Factory Serial number bar code 128 the field Shifter MHz indicates the possible frequency bands that can be used with this branching assembly. The choice between different shifters is done by Craft Terminal (refer to point [2] on page 237 for details). for each Shifter MHz, the TX LOW and HIGH rows indicate the frequency range assumed by transceiver TX section, according to the TRANSCEIVER and BRANCHING boxes coupling described in para.14.7.4.2 on page 124
126 / 592
15 TECHNICAL SPECIFICATIONS
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Data indicated in this manual must be considered as typical values The guaranteed values are only those indicated in the contract. This chapter describes the technical characteristics of the 9400AWY Rel.2.1 in the following RF band configurations: Tab. 46. 9400 AWY family SYSTEM 9470AWY 9413AWY 9415AWY 9418AWY 9423AWY 9425AWY 9428AWY 9438AWY This chapter is organized as follows: General Characteristics on page 128, including: Reference system standards on page 129 RF channeling on page 129 Transmitted Power at antenna port on page 130 99% power channel bandwidth and Emission Designator on page 131 ETSI System Characteristics on page 132 Switching system on page 134 Tributary interfaces Modem Maximum capacity and Modulation type IDUODU cable Manmachine interface Alarms Power supply Mechanical characteristics Environmental conditions Electromagnetic compatibility / safety Dismantling & Recycling on page 135 on page 135 on page 135 on page 135 on page 136 on page 136 on page 136 on page 136 on page 137 on page 137 on page 138 BAND (GHz) 78 13 15 18 23 25 28 38
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
127 / 592
RTPC range
Tx level with Tx mute ON RF frequency stability Synthesizer step RF spectrum masks Spurious emissions BER receiver threshold System gain Rx max input level Switching system
NMS channels
128 / 592
Equipment
ETSI standard Frequency range Channeling (GHz) 7.117.9 7.7259.5 ITUR F.385 ITUR F.386
9470 AWY 4&16 QAM 9413 AWY 4QAM 9413 AWY16QAM 9415 AWY 4QAM
Standard Tx/Rx separation (MHz) 150, 154, 160, 161, 168, 182, 196, 245 119, 126, 151.614, 208, 266, 294.44, 305.56, 311.32 266 315 728 420, 490, 644 1008, 1010 340, 1560 1092.5 1008, 1050, 1200,1232 1200 1008
13 GHz
12.7513.25
15 GHz 9415 AWY 16QAM 9418 AWY 4QAM 18 GHz 9418 AWY 16QAM 9423 AWY 4QAM 23 GHz 9423 AWY 16QAM 9425 AWY 4QAM 9425 AWY 16QAM 9428 AWY 4QAM 28 GHz 9428 AWY 16QAM 9438 AWY 4QAM 9438 AWY16QAM 38 GHz 25 GHz
14.415.35
17.719.7
ERC 1202 ITUR Rec 497 MEXICO ERC 1207 ITUR Rec 636 ERC 1203 ITUR Rec 595 CHINA
ERC 1302 annex A
21.223.6 24.526.5
ITUR Rec 637 ERC 1302 ITUR Rec. 748 ERC 1302 ITUR Rec. 748 ERC 1201 ITUR Rec 749
27.529.5 3739.5
1008
1260
For all frequency bands, the ETSI reference standard is the harmonized standard EN 302 217. In this stardard , 4QAM is class 2 and 16QAM is class 4. 15.1.2 RF channelling ETSI RF CHANNELING Capacity (Mbit/s) RF Channeling with 4 QAM (MHz) RF Channeling with 16 QAM (MHz) 2x2 3.5 4x2 7 3.5 8x2 14 7 16x2 28 14 32x2 28
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
129 / 592
15.1.3 Transmitted power at antenna port Tolerance: 2.0 dB in temperature range 33C to +55C for 0 to 20dB RTPC range
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Equipment
Tx/Rx separation MHz For 7 GHz ODUs, refer to shifters in Tab. 28. on page 106 For 8 GHz ODUs, refer to shifters in Tab. 30. on page 107
9470 AWY 4QAM 9470 AWY 16QAM 9413 AWY 4QAM 9413 AWY 16QAM 9415 AWY 4QAM 9415 AWY16QAM 9418 AWY 4QAM 9418 AWY 16 QAM 9423 AWY 4QAM 9423 AWY 16QAM 9425 AWY 4QAM 9425 AWY 16QAM 9428 AWY 4QAM 9428 AWY 16QAM 9438 AWY 4QAM 9438 AWY 16QAM
Refer to shifters in Tab. 31. on page 108 20 24 Refer to shifters in Tab. 32. on page 109 20 22 19 19 16 17 Refer to shifters in Tab. 37. on page 112 14 16 Refer to shifters in Tab. 38. on page 112 13 16 Refer to shifters in Tab. 39. on page 112 13 Note 1: Output power at antenna port. Output power setting (dBm): ATPC/RTPC range with 1dB step Refer to shifters in: Tab. 33. on page 110 (fixed shifters) Tab. 34. on page 110 (variable shifters) Refer to shifters in: Tab. 35. on page 111 (fixed shifters) Tab. 36. on page 111 (variable shifters)
130 / 592
Radio Type
99% Power Channel Bandwidth [MHz] 2,8 5,5 10,9 21,7 2,8 5,5 10,9 21,7
Emission Designator 3M5D7W 7M0D7W 14M0D7W 28M0D7W 3M5D7W 7M0D7W 14M0D7W 28M0D7W
9400 AWY 4QAM 2E1 9400 AWY 4QAM 4E1 9400 AWY 4QAM 8E1 9400 AWY 4QAM 16E1 9400 AWY 16QAM 4E1 9400 AWY 16QAM 8E1 9400 AWY 16QAM 16E1 9400 AWY 16QAM 32E1
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
131 / 592
15.1.5 ETSI System Characteristics Data is split into following Tab. 47. to Tab. 51. according to capacity. Note for all tables: Transmitted PTX tolerance: 2dB @ ODU Operating temperature range 33C + 55C Tab. 47. ETSI System Characteristics 32E1 (typical values) 32E1 Frequency
System Characteristics QAM All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
TX Output Power @ Antenna Port 103 BER Threshold @ Antenna Port 106 BER Threshold @ Antenna Port Net System Gain dB @ 103 BER Threshold Net System Gain dB @ 106 BER Threshold
16 16 16 16 16
13 GHz
15 GHz
18 GHz
23 GHz
25 GHz
28 GHz
38 GHz
20 79 78 99 98
20 79 78 99 98
19 78 77 97 96
16 78 77 94 93
14 77 76 91 90
13 76 75 89 88
13 74 73 87 86
Tab. 48. ETSI System Characteristics 16E1 (typical values) 16E1 Frequency
System Characteristics QAM
TX Output Power @ Antenna Port 103 BER Threshold @ Antenna Port 106 BER Threshold @ Antenna Port Net System Gain dB @ 103 BER Thr Net System Gain dB @ 106 BER Thr
4 16 4 16 4 16 4 16 4 16
28 GHz 16 13 83 79 82 78 99 92 98 91
38 GHz 16 13 81 77 80 76 97 90 96 89
132 / 592
8E1 Frequency
System Characteristics QAM
TX Output Power @ Antenna Port 103 BER Threshold @ Antenna Port 106 BER Threshold @ Antenna Port Net System Gain dB @ 103 BER Thr Net System Gain dB @ 106 BER Thr
4 16 4 16 4 16 4 16 4 16
38 GHz 16 13 84 80 83 79 100 93 99 92
Tab. 50. ETSI System Characteristics 4E1 (typical values) 4E1 Frequency
System Characteristics QAM
TX Output Power @ Antenna Port 103 BER Threshold @ Antenna Port 106 BER Threshold @ Antenna Port Net System Gain dB @ 103 BER Thr Net System Gain dB @ 106 BER Thr
4 16 4 16 4 16 4 16 4 16
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
133 / 592
Tab. 51. ETSI System Characteristics 2E1 (typical values) 2E1 Frequency
System Characteristics QAM All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
TX Output Power @Antenna Port 103 BER Threshold @Antenna Port 106 BER Threshold @Antenna Port Net System Gain dB @103 BER Thr Net System Gain dB @106 BER Thr
4 4 4 4 4
13 GHz
15 GHz
18 GHz
23 GHz
25 GHz
28 GHz
38 GHz
24 95 94 119 118
24 95 94 119 118
22 94 93 116 115
19 94 93 113 112
17 93 92 110 109
16 92 91 108 107
16 90 89 106 105
15.1.6 Protection switching system [1] EPS (Equipment Protection System) In 1+1 configurations, the system can support 3 levels of protection against hardware problems. All the switches are independent and have its own switching criteria. Available switches Tx EPS Select the IDU unit in Tx Not hitless Non revertive/Revertive Rx EPS Select the IDU unit in Rx Not hitless Non revertive/Revertive ODU switch (HSB) Select the ODU on line Not hitless Non revertive/Revertive
Switch vs. Configuration Configuration 1+1 FD 1+1 HSB Tx EPS YES YES Rx EPS YES YES ODU switch NO YES
[2]
RPS (Radio Protection System) RPS, hitlessswitch type, is equipped to provide protection against radio propagation problems.
134 / 592
E1 Input / output electrical interface Code Impedance Jitter Generation Jitter Tolerance Jitter Transfer ITUT G.703 HDB3 75 unbal 120 bal ITUT G.823 ITUT G.823 ITUT G.736 ITUT G.742
15.3 Modem
Modulation Demodulation Equalizer type Channel coding Spectrum shaping 4/16 QAM Coherent 19tap FSE Reed Solomon (255,239) Raised cosine
Signals on the cable Gross bit rate on the cable: ETSI (2 to 16xE1) ETSI (17 to 32xE1) n.b.1 n.b.2
for details on cables that can be employed and relevant cable maximum length, refer to the Installation handbook. the HDB3 signal contains the main signal, auxiliary signal and IDUODU service channel.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
135 / 592
Other
15.7 Alarms
Equipment alarms Housekeeping alarms 3 outputs (IDU HW Failure alarm, ODU Main Failure alarm, ODU Spare Failure alarm) 6 inputs / 4 outputs
136 / 592
Main environmental aspects of AlcatelLucent products are: Energy consumption during manufacturing and use Materials harmfulness and recyclability Emission to air, water or soil related to the manufacturing and the use of the product Electromagnetic (EM) emissions Value recovery at the product end of life
15.10.1 Operating environmental conditions Storage Transport IDU Operation ODU EN 300 019 class 1.3 EN 300 019 class 2.3 EN 300 019 class 3.2 Temperature range: 5C to +55C (23F to 131F) EN 300 019 class 4.1, IP 67 Temperature range: 33C to +55C (27.4F to 131F)
15.10.2 Electromagnetic compatibility/safety EMC Safety Power supply ElectroStatic discharge Lightning protection EN 300 385 class B grade B/FCC Part 15 subpart Bclass A EN 60 950 EN 300 132 EN 55022 class B Symmetric protection implemented in ODU & IDU $ 5kV on cable ground according to IEC 100045 with 2 wave types: 1.2/50 s and 10/700 s
15.10.3 Waste from Electrical and Electronic Equipment (WEEE) This product must be selectively collected and treated. Treatment applied at end of life of the product in these countries shall comply with the applicable national laws implementing directive 2002/96EC on waste electrical and electronic equipment (WEEE).
collection and is not to be treated as general household waste (only for B2C equipment) Separate collection and recycling of waste equipment at the time of disposal contribute to avoid possible negative effects on the environment and on human health.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
137 / 592
Product
Code
Denomination
AWY/S N.B.
8BW036840000
Such a document is available on specific request to your AlcatelLucent local dealer. NOTE FOR AlcatelLucent INTERNAL USE cited document, in Adobe Acrobat pdf format, can be retrieved from PDM archive. Get highest available edition. a) END OF SECTION
138 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
143
219
227
233
247
257
267
277
289
139 / 592
SECTION CONTENT SOFTWARE MANAGEMENT Chapter 213 Software Management It deals with the management of the functions related to the software verification/download. Chapter 214 MIB Management It deals with the management of the functions related to the backup and restore of equipment configuration data.
PAGE
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
297
301
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
140 / 592
This chapter gives general information regarding the Software Package this manual refers to.
The software package used for management allows the dialogue between craft terminal and NE, to realize all the functions of the NE and EMLULS ). The software package used for updating the NE must be installed on the PC and then downloaded on the NE, thus following product evolution. 21.1.2 Software product list and part numbers Every Software Product is identified by a Technical Code and a Technical Description and is distributed by a CDROM with the same identifiers, listed on the following table: Tab. 53. Software products part numbers REF [a] Technical Description SWP 9400AWY R.2.1 V2.1.1 Technical Code 3DB16131ABAA
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
141 / 592
21.2.1 PC characteristics Refer to para.31.1.1 on page 309 21.2.2 NE MIB Compatibility NE MIB structure is automatically converted from previous release 2.1.0, using the procedure described in Chapter 49 on page 495 V2.1.1 NE MIB structure is not backward compatible with those of previous release 2.1.0 (see point [1]6 )WARNING on page 495 NE MIB structure is not compatible with any releases 1.0.x and 2.0.x 21.2.3 SWP version specific data and Reference Information Models Make reference to the Product Release Note (see para.57.2.2 on page 571 )
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
142 / 592
This chapter describes the functions of the TCO Suite, describes how to start and close the Craft Terminal application, how to login and logout the NE, and sumsup the organization of the 9400AWY NE Craft Terminal, presented after the NE login. This chapter is organized as follows: Requirements TCO Suite description TCO Suite Alarms & Settings functions PCNE physical connections Physical interfaces for the NE management Local connection of the Craft Terminal to the NE on page 144 on page 146 on page 156 on page 170, including: on page 170 on page 171 on page 172 on page 181 on page 184
Craft Terminal: NE supervision, login, logoff and switch off 9400AWY view organization Introduction to the CT menu options
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
143 / 592
22.1 Requirements
a) PC characteristics The PC used for TCO Suite application and/or employed as Craft Terminal must meet all specifications pointed out in para.31.1.1 on page 309. b) Cables necessary for PCtoNE local connection for the local connection between PC and NE RS232 serial ports, one RS232 cable is necessary (P/N 1AB054120027) 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 employ the USB TO RS232 ADAPTER , ordering it to AlcatelLucent (P/N 1AF11294AA**). for the local direct connection between PC and NE Ethernet ports, one crossconnect Ethernet cable is necessary. Otherwise the connection can be done by a normal Ethernet cable through a LAN. For explanatory drawing, see Fig. 59. on page 154. Typical AlcatelLucent Ethernet cables are: Tab. 54. Typical AlcatelLucent Ethernet cables Length 6m Type normal crossconnect normal 2m crossconnect P/N 3DB 14050 AA** 3DB 14051 AA** 3DB 05020 AA** 3DB 05021 AA**
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.
The TCO Suite applications can use the Ethernet interface only. The Craft Terminal application can use both the Ethernet and the RS232 interfaces.
c)
Craft Terminal If the Craft Terminal application must be used, the SWP installation must have been already carried out, as specified in chapter 31 on page 309.
d)
NE state the SWP (NEspecific components) must be already present in the NEs flash card and its active version (see point [2] on page 63 to do this check) must be equal to that of the: SWP CDROM this manual refers to (in case of TCO Suite application run directly from the CDROM itself) SWP installed in the Craft Terminal (see point [1] on page 62 to do this check).
Solve different situations, if any, according to instructions given in para.12.6.4 on page 64. if the NE must be accessed in remote way (by TCO Suite application or by RECT application) it must have already a valid TCP/IP address, and such address must be known by the Operator.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
144 / 592
e)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Operator profiles and allowed operations The menu options described in this section are all available logging in the system with the Administrator profile username and password. Logging the system with other operator profiles result in some functionality access limitations. For further information please refer to Profiles management , para.23.6 on page 214.
f)
Operator skills the Operator shall be familiar with the use of personal computers in WINDOWSNT / WINDOWS2000 / WINDOWSXP (professional version only) environment, internally to which the Network Elements application software operates. the Operator must be familiar with all the functionalities of this 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).
g)
Documentation Besides this manual, all the documentation set this manual belongs to must be available to the Operator, to retrieve pieces of information not contained in this manual. The documentation set is described in Appendix G on page 567.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
145 / 592
TCO Suite Advanced Settings Page on page 151, including: Java JRE Package Installation on page 152 Serial F Interface Driver Installation on page 153 1320CT Package Installation on page 153 1320CT Package DeInstallation on page 153 Local Copy of TCO Suite on page 153 Note: Direct and Remote Connections on page 154
Warning about interface customization carried out by the Direct Connection on page 155
22.2.1 TCO Suite scopes The TCO Suite is a feature that allows the operator to access and configure the NE from his/her PC without the need for software installation in PC environment (i.e. running the TCO Suite directly from the SWP CDROM). Moreover, after having installed the SWP components and the TCO Suite local copy in the PC environment (as described in chapter 31 on page 309), most of TCO Suite functionalities are available also after having removed the SWP CDROM from the PC CDROM unit. TCO Suite works through web pages with simple operations available with a single mouse click.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
146 / 592
22.2.2 Summary
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
After having started up the TCO Suite (para.22.2.3 on page 148), the TCO Suite Main Menu becomes available (Fig. 55. on page 149) with the following main tools: PreProvisioning Tool This is a fulllocal application. SetUp Tool and Alarms & Settings These applications require the access and the login to a 9400AWY NE from your PC. To access and login a 9400AWY NE from your PC for these applications: the CTNE connection can be: physically and logically local, through a crossconnect Ethernet cable for the local direct connection between PC and NE Ethernet ports physically local but logically remote, by a normal Ethernet cable through a LAN for the connection between PC and NE Ethernet ports physically and logically remote, by a connection between PC Ethernet port and the NE through the RECT function or the TCP/IP network. The SetUp Tool and Alarms & Settings applications cannot be used through the PCNE local connection by RS232 serial F interface you must have a UserName and password set in case of logically remote connection, you must know the NEs TCP/IP address
N.B.
Operational & Maintenance This application corresponds to the 1320CT application. Refer to para.172 on page 22.5 for details.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
147 / 592
Standard behavior The Suite autoruns itself (if this feature is enabled on users PC) as soon as CDROM is read by PC. If autorun does not start, user must run (doubleclick with mouse on) the Start.exe file, available on CDROM root in order to launch TCO Suite. Since this TCO Suite works using Java software, it is mandatory to have a Java Runtime Environment (JRE) installed on the system. Allowed JREs are Sun only, with version number higher or equal than 1.4.2_12. The first operation performed by autorun procedure is the check for JRE. All HTML pages used for TCO Suite are XHTML 1.1 and CSS 2.0 standards compliant with respect to W3C (WWW Consortium) specifications. Minimal screen resolution allowed to use TCO Suite is 1024x768 pixels If there is no JRE on users PC or if there is a JRE installed on users PC but its version number if lower than 1.4.2_12, user will be asked to install the Sun Java Runtime Environment version 1.4.2_12 available on TCO Suite CDROM (Fig. 53. below).
Fig. 53. Java installation request In both cases: if user denies authorization to install the suitable JRE, TCO Suite wont be executed at all if user gives authorization to install the suitable JRE, after some minutes the installation message appears:
Fig. 54. JRE installation completion 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
148 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
After, the default browser (configured as for user preferences) opens the TCO Suite Start.html page (Fig. 55. below). Special conditions For any special condition which may occur during the TCO Suite startup and the countermeasures to take, refer to the Appendix B TCO suite startup special conditions on page 511 22.2.4 TCO Suite Main Menu functions Fig. 55. and Fig. 56. on page 149 show the layouts of the TCO Suite Main Page as described from the internal version of AS.html file, respectively for the CDROM version and the Local version. N.B. The TCO Suite Local version must be explicitly created as described in para.22.2.5.5 on page 153 This page shows the main TCO Suite menu with the following functions: PreProvisioning Tool SetUp Tool Alarms & Settings Operational & Maintenance Advanced Settings (N.B.) N.B. The Advanced Settings button is not available in the local version of the TCO Suite Main Page.
Fig. 56. TCO Suite Start.html page (Local version) Detailed functions and differences between CDROM and Local TCO Suites will be described in following subparagraphs. USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
149 / 592
22.2.4.1 PreProvisioning Tool This button is a oneclick execution for the PreProvisioning Tool. This tool allows the offline creation and modification of a provisioning file, without accessing any NE. This file will be after used to configure the NE (after having logged it) with a simple load command. For procedure execution, refer to para.32.3.6 point [2] on page 341. 22.2.4.2 SetUp Tool This button is a oneclick execution for the SetUp Tool. This tool allows to access a NE, recover a configuration file previously created (e.g. through the TCO Suite PreProvisioning Tool) or get configuration data from the NE, and check/modify/apply such a configuration to the NE. For procedure execution, refer to para.32.3.6 point [3] on page 341. 22.2.4.3 Alarms & Settings The Alarms & Settings function allows the user to login a NE through the use of the NE web server via a generic Internet browser, in order to monitor the status of NE alarms and to get and/or set some NEs parameters. For procedure execution, refer to para.22.3 on page 156. 22.2.4.4 Operational & Maintenance This function runs the 1320CT software application. This function has two different behaviors, one for CDROM TCO Suite and one for Local TCO Suite. The main difference is related to 1320CT software installation: Local TCO Suite does not install 1320CT in any case CDROM TCO Suite will perform a complete 1320CT installation, if needed (if such software is not available). If 1320CT is available on users system, the behavior is common between Local and CDROM TCO Suites: [1] CDROM TCO Suite In this case, if the 1320CT platform is not installed, the user will be asked to perform the installation and, if the user agrees, the installation will be started. The 1320CT platform installation is described in para.31.5 (Installation of SWP components from the SWP CDROM) from step 5 ) on page 316 [2] Local TCO Suite If users PC does not have a 1320CT platform installed, no installation is performed and an error message is shown to user.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
For procedure execution, refer to point e )1 ) on page 174. 22.2.4.5 Advanced Settings This button will show to user the related HTML page: this function is available through CDROM TCO Suite only. All functions related to this page are described in following para.22.2.5 on page 151.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
150 / 592
This page is opened clicking the Advanced Settings button of the CDROM TCO Suite Main Menu (Fig. 55. on page 149). Such page is shown in Fig. 57. below and contains: Java JRE Package Installation Serial F Interface Driver Installation 1320CT Package Installation 1320CT Package DeInstallation Local Copy of TCO Suite Back : go back to Main Menu of Fig. 55. on page 149
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
151 / 592
22.2.5.1 Java JRE Package Installation This button connects to the installation file for the Java Runtime Environment, version 1.4.2_12. The behavior of this button depends on browser configuration. The usual behavior is: Internet Explorer asks the user to Open or Save the file (Fig. 58. below):
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 58. Internet Explorer: .exe files management Mozilla Firefox automatically saves the file, the first time (or every time, depends on configuration) asking the user where to place it; Mozilla browser automatically saves the file, the first time (or every time, depends on configuration) asking the user where to place it;
In any case, for most browsers the default behavior can be changed but this strictly depends on browser configuration and user choices.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
152 / 592
This button starts the installation (from the SWP CDROM) in PC environment of the LLMAN (Alcatel Lower Layer MANager), necessary when communication with NEs ECT serial port is required. For procedure execution, refer to para.53.2.1 on page 519. 22.2.5.3 1320CT Package Installation This function will automatically perform the complete installation of the existing 1320CT platform without installing a needed JRE (that is anyway installed if this function can be performed) and without installing the Alcatel Lower Layers Manager software. For procedure execution, refer to para.31.5 on page 314. 22.2.5.4 1320CT Package DeInstallation This function is a singleclick complete deinstallation for the 1320CT package. This function wont remove neither possible JRE installed nor Alcatel Lower Layers Manager software. Sequence of screens shown to user depend on speed and performance of users PC since all the procedure is automatic and all the deinstallations needed are performed at the same time without the need for interaction by the user. 22.2.5.5 Local Copy of TCO Suite This function, written as part of the TCO Suite Java applet, allows the user to create the Local TCO Suite by copying the content of the TcoSuite directory on a location specified by user. For procedure execution, refer to para.31.6.1 on page 318.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
153 / 592
22.2.6 Note: Direct And Remote Connections The difference between Direct or Remote connection, asked to user as in Fig. 62. on page 156, is depicted in Fig. 59. below, and reflects the working mode for JUSM application: in case of Remote connection the NE is considered as reachable through the network connected to users PC so no Ethernet configuration is needed and the SetUp Tool or Alarms & Settings function is executed. in case of Direct connection, users PC is considered as directly connected to NE via a crossconnection Ethernet cable so a Ethernet modification is needed on users PC since both functions (SetUp Tool and Alarms & Settings) have to be sure about PC connection with NE in order to be performed.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
IP NETWORK
Direct
Fig. 59. ECTNE Direct and Remote connections For this reason, the TCO Suite will perform a search on users computer resources in order to find all network adapters related to active (enabled) network connections. Then, if more than one network adapter is found, the user must select the one to modify in order to connect his/her PC to the NE. This selection box is shown in Fig. 60. :
Fig. 60. Network Adapter selection Such figure is an example created to show the possible layout. Actually, if users PC owns one network adapter only and the Alcatel Virtual Network Card for Lower Layers, the selection is automatically done without bothering the user, which wont see the dialog box shown in Fig. 60. above.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
154 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
In order to let the user knows more information about adapters details, by clicking the Details toggle button some supplemental information are shown as in Fig. 61. :
Fig. 61. Network Adapter details When the user clicks on Apply the selected network adapter is modified in order to allow users PC connecting with specified NE. Network adapters configuration is saved in XML format using the NAML (Network Adapter Markup Language) format in the NAML directory inside users personal directory usually located inside Documents And Settings directory on system disk. 22.2.7 Warning about interface customization carried out by the Direct Connection When the Direct connection (described in previous para.22.2.6 on page 154) is set up, the system carries out an interface customization that makes any subsequent attempt to start the Craft Terminal using the Finterface impossible, even after the logging off from the TCO Suite application and independently from the settings explained in para.22.4.2 on page 171. These are the simplest alternative ways to solve this situation: launch the TCO Suite Alarms & Settings defining the Remote connection, then close the TCO Suite application or: perform the PC shut down.
Any of these operations resets the interface customization said above, so that the start of the Craft Terminal using the Finterface becomes again possible.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
155 / 592
22.3.1 TCO Suite Alarms & Settings startup To launch this application, click on the button Alarms & Settings of the TCO Suite Main Page (see Fig. 55. and Fig. 56. on page 149). Then, User is asked to distinguish between Direct or Remote connection (Fig. 62. below) and he/she will be asked to fill the IP address field used to connect to NE.
Fig. 62. Direct or Remote connection by the TCO Suite The difference between Direct or Remote connection is described in para.22.2.6 on page 154. WARNING 1: In case you choose the Direct connection, read carefully para.22.2.7 on page 155 (Warning about interface customization carried out by the Direct Connection) WARNING 2: In case you have in your network some 9400AWY NEs with SWP 2.0.x (N.B.) and others with SWP 2.1.x you must be aware that: by TCO Suite of SWP 2.0.x you can access only 9400AWY NEs with SWP 2.0.x by TCO Suite of SWP 2.1.x you can access only 9400AWY NEs with SWP 2.1.x
The other combinations do not work properly! N.B. in 9400AWY Rel.2.0, TCO Suite is available starting from SWPversion 2.0.4.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
156 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Then (Fig. 63. below), User is asked to provide the Username and Password [same rules as in point 3 ) on page 179]. In case of remote connection, the NEs IP address entered in previous screen (Fig. 62. ) is displayed.
Fig. 63. NE login by the TCO Suite As soon as the connection with the NE is established, the Alarms & Settings Main Menu screen appears (Fig. 64. below).
Fig. 64. TCO Suites Alarms & Settings Main Menu screen
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
157 / 592
Operations allowed according to the Login profile (refer to para.23.6 on page 214 for details) are: Tab. 55. Operations allowed in TCO Suite Alarms & Settings screen according to the Login profile Login profile Function Administrator, Craftperson and Operator YES YES YES YES YES YES YES YES YES Viewer read only NO YES YES YES read only YES read only NO
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Date & Time Setting (para.22.3.2 on page 159) Configuration Setting (para.22.3.3 on page 160) Configuration Info (para.22.3.4 on page 161) Get Configuration File (para.22.3.5 on page 164) Active Alarms (para.22.3.6 on page 165) Power Measurement (para.22.3.7 on page 166) Licence Info (para.22.3.8 on page 166) Modem Speed (para.22.3.9 on page 167) NAT Option (para.22.3.10 on page 168)
User can perform desired operations by clicking on proper label in proposed menu. The behavior of the Web Server for each of menu entry is detailed in the following subparagraphs. Logout button gives the user the possibility to clear its authentication parameters and reload the initial page (Fig. 64. on page 157) for starting a new session. The links between pages are available by following standard procedures and correct navigation steps. If the user will follow nonauthorized processes or will try to search for other pages, a 404 error will show the Page Not Found result. In this case, the user will be allowed to get back to initial login page and he has to redo the whole login process. WARNING: if, during the usage of the TCO Suite Alarms & Settings functions, the connected NE becomes unavailable (e.g. for network problems, or after having loaded NE data which modify the NE IP address), the sandglass symbol appears and no operations are longer possible. In this case, close the TCO Suite Alarms & Settings session, then verify the NE reachability (e.g. by PING function).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
158 / 592
For authorized users, this function allows to modify NE internal time so that it can be automatically aligned with users PC internal time or the user can set its preferred time and date on NE. Also, it is possible, for the user, to verify the status of NTP configuration for automatic synchronization using a couple of NTP server (main and backup). There are two functions available to authorized users: 1. 2. NE Time Setting with OS time; GMT Time Manual Setting.
In the first situation (Fig. 65. below) the user will see his/hers PC internal time and by clicking on apply, NE will receive UTC time based on PC configuration. For example: if users PC is configured as located in central Europe (CET or CEST time zones) and it shows 20060825 11:40:00, by clicking Apply button NE web server will receive 20060825 09:40 due to Daylight Saving (summer) Time one hour difference with respect to normal time and to one hour time difference between CET time zone and GMT time zone.
Fig. 65. TCO Suites Alarms & Settings Date & Time Configuration page The other function allows user to directly send a specific date and time information to NE without bothering on time zones but simply specifying all the information needed. In both cases there could be some short delays (few seconds) between applied time shown after the operation and current time or selected time. In case of enabled NTP, this page wont allow to modify NE time and date
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
159 / 592
22.3.3 Configuration Setting The set configuration process allows the allowed operator for sending to NE the operators desired configuration.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 66. TCO Suites Alarms & Settings Configuration Setting page To carry out this operation, you must browse from your PC a configuration file configuration_name.qcml previously created (e.g. through the TCO Suite PreProvisioning Tool, N.B.), and then click on Apply Configuration button. N.B. refer to para.32.3.6 on page 341 for details.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
160 / 592
The Get Configuration Report function allows the user to download the full NE system report. Selecting (by click) this function from main menu will show the user a Save File screen (Fig. 67. below) that gives the user the capability to browse its system in order to select the path where to save the full report file. N.B. With some browsers (e.g. Mozilla), it is necessary to specify a textreading application (e.g. WORD PAD) to open and read correctly the file.
Fig. 67. TCO Suites Alarms & Settings Get Report Request This screen content, shape, graphics and layout all depend on operating system version and language and on used browser too. The report file is a text file that describes the configuration of the NE. It contains all the information once added to the quick configuration report or in the current configuration view used in the former versions. An example of this file content is shown below: NE CONFIGURATION
NE Configuration Type:1+0 16E1/DS1ETH (PSU4860) Market: ETSI Frame Structure: 8E1 Modulation: 16QAM Impedance: Unbalanced 75 Ohm
TRIBUTARIES CONFIGURATION E1 Tributary 1: Signal E1 Tributary 2: Signal E1 Tributary 3: Signal E1 Tributary 4: Signal E1 Tributary 5: Signal E1 Tributary 6: Signal E1 Tributary 7: Signal E1 Tributary 8: Signal
DATA CONFIGURATION [Ethernet Port 1] Status: Disabled Auto Negotiation: Disabled Speed Without Autonegotiation: 100 Mbit/s
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
161 / 592
RADIO CONFIGURATION [Channel 1] Tx Frequency: 0 kHz Tx Range: [5000000 , 40000000] kHz Rx Frequency: 0 kHz Rx Range: [5000000 , 40000000] kHz Current Tx Power: 30 dBm Atpc Status: Disabled Shifter Settings: Unconfigured
EXTERNAL POINTS STATUS [Input Point 1] User Label:CPI1 Polarity: Active [Input Point 2] User Label:CPI2 Polarity: Active [Input Point 3] User Label:CPI3 Polarity: Active [Input Point 4] User Label:CPI4 Polarity: Active [Input Point 5] User Label:CPI5 Polarity: Active [Input Point 6] User Label:CPI6 Polarity: Active
Closed
Closed
Closed
Closed
Closed
Closed
[Output Point 1] User Label:CPO1 Polarity: Active Closed Switching Criteria: Manual External State: Off [Output Point 2] User Label:CPO2 Polarity: Active Closed Switching Criteria: Manual External State: Off [Output Point 3] User Label:CPO3 Polarity: Active Closed Switching Criteria: Manual External State: Off [Output Point 4] User Label:CPO4 Polarity: Active Closed Switching Criteria: Manual External State: Off
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
162 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Advertised Capability for AutoNegotiation: 10 Mbit/s [Ethernet Port 2] Status: Disabled Auto Negotiation: Disabled Speed Without Autonegotiation: 100 Mbit/s Advertised Capability for AutoNegotiation: 10 Mbit/s
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Stub Flag: FALSE [Ospf Area 2] IP Address: 10.0.1.0 Stub Flag: FALSE Local IP Address: 10.0.1.2 LAN IP Address: 151.98.141.77 Ethernet Status: Enabled Mask: 192.0.0.0 MAC Address: 00:20:60:00:03:5e Routing Protocol: None [Static Route: 1] IP Address: 151.98.70.0 IP Mask: 255.255.254.0 Point to Point Interface: RF [Static Route: 2] IP Address: 151.98.170.0 IP Mask: 255.255.254.0 Point to Point Interface: RF [Static Route: 3] IP Address: 172.24.168.0 IP Mask: 255.255.255.0 Point to Point Interface: RF [TMNRF] Status: Disabled Routing Protocol: None [TMNV11] Status: Disabled Interface Mode: Not Used Routing Protocol: None [TMNG703] Status: Disabled Interface Mode: Not Used Routing Protocol: None
NTP CONFIGURATION Status: Enabled Main Server IP Address: 100.5.4.75 Spare Server IP Address: 100.5.5.5
INSTALLED SOFTWARE [Active SW Package: R94A V02.01.00] Status: Committed Operational State: Enabled SW Units: EC V03.00.03 Size(Bytes): 1769472 OC_R V02.01.01 Size(Bytes): 215469
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
163 / 592
22.3.5 Get Configuration File Just like the Get Configuration Info function, the Get Configuration File allows the user to download the full NE system report. Instead of being in humanreadable text format, the configuration file is described in QCML format and it can be used by Quick Configuration by Text File or by PreProvisioning and SetUp Tools. Selecting (by click) this function from main menu will show the user a Save File screen (Fig. 68. below) that gives the user the capability to browse its system in order to select the path where to save the full report file. N.B. With some browsers (e.g.Mozilla), it is necessary to specify a textreading application (e.g. WORD PAD) to open and read correctly the file.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 68. TCO Suites Alarms & Settings Get Configuration Request This file is an XML standardbased set of configuration information that PreProvisioning and SetUp Tool can preview in a humanreadable HTML layout and allow the user to modify such configuration using a set of wizard/simplified steps just like the Quick Configuration by Text File do.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
164 / 592
Alarms monitoring is represented by a simple colored table that will shows an updated list of active alarms. Older alarms, anyway, wont be removed but in order to be more comprehensible, activated alarms table will be updated by recreating the whole table each time, so showing only all active alarms in any moment.
Fig. 69. TCO Suites Alarms & Settings Active Alarms: Static Page This table can be presented into two ways: the first one shown when user chooses Active Alarms function is a simple page that will show to user alarms active at the moment of its selection. To give user a better control on this status table, a Refresh button is provided. This button will redo the request to NE and updates shown HTML page anytime is pressed. The Enable Automatic Refresh button allows the user to forget about doing a refresh by providing an automatic refresh process (Fig. 70. below).
Fig. 70. TCO Suites Alarms & Settings Active Alarms: Automatic Page This page will do a periodic automatic refresh of its content and anyway allows the user to get back to the manual refresh page. WARNING: For autorefreshed pages, a longer timeout is foreseen. This is set to 90 refresh cycles of 10 seconds each, for a total of 15 minutes. After this timeout, the connection expiration page is shown.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
165 / 592
22.3.7 Power Measurement This page (Fig. 71. below) allows user to read power measurement result. Refresh Interval filed allow the operator to set the time duration of the measurement for automatic refreshing. The choice is among 5,10,30 sec. Otherwise operator can click refresh button directly to refresh the result of power measurement.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
22.3.8 Licence Info This page allows user to read license so that he can retrieve data needed by AlcatelLucent to produce a new Software License (Fig. 72. below).
Fig. 72. TCO Suites Alarms & Settings Reading Software License
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
166 / 592
This function (Fig. 73. below) allows the authorized user for reading the current FInterface speed value and for modifying it through a simple combo box.
Fig. 73. TCO Suites Alarms & Settings Changing FInterface Speed In case of login by viewer profile, the button and combobox elements are not shown and the page just displays the current modem speed.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
167 / 592
Fig. 74. TCO Suites Alarms & Settings NAT option [1] NAT router In the following the scenario, when the NAT router is used in the network, is analyzed, providing a list of warnings and the relevant countermeasures. The scenario is represented by a remote manager that wants to access the radio network; in between one or more NAT router could be present. WTD suggests not using this device because of the consequences that are hereunder described. [2] What is the NAT router The Network Address Translation allows a single device, such as a router, to act as agent between the Internet (or public network) and a local (or private) network. This means that only a single unique IP address is required to represent an entire group of computers to anything outside their network. The shortage of IP addresses is the main reason to use NAT.
Fig. 75. NAT router The NAT function cannot by itself support all applications transparently and often must coexist with application level gateways (ALGs) for this reason. People looking to deploy NAT based solutions need to determine their application requirements first and assess the NAT extensions (i.e., ALGs) necessary to provide application transparency for their environment. NAT devices are application unaware in that the translations are limited to IP/TCP/UDP/ICMP headers and ICMP error messages only. NAT devices do not change the payload of the packets, as payloads tend to be application specific. NAT devices (without the inclusion of ALGs) do not examine or modify transport payload. For this reason, NAT devices are transparent to applications in many cases.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
168 / 592
[3]
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
What are the NAT router limitations As stated on the RFC 2663 IP Network Address Translator (NAT) Terminology and Considerations there are three main areas where NAT devices often cause difficulties: 1) 2) 3) when an application payload includes an IP address, the FTP application unless to operate dedicated setting and when endtoend security is needed (ex. IPSec transport mode or the TCP MD5 Signature Option)
About 1 ) , SNMP is one such application with address content in payload. NAT routers would not translate IP addresses within SNMP payloads. It is not uncommon for an SNMP specific ALG to reside on a NAT router to perform SNMP MIB translations proprietary to the private network, but for sure it is expensive and NAT device depending. [4] How the WTD equipments SNMP based are impacted 1) About the Manager IP Address Access Control Security This feature allows the control of the IP manager forbidding the access for any manager that is not registered. For the 9400AWY family, the Start Supervision operation/sequence is completed successful only if IP packets coming from the manager have the same IP source address than the one contained in the Registration table (retrieved by the SNMP message); this means, in case of NAT usage, no way to access the equipment. 2) Disabling the Manager IP Access Control Obviously the case of NAT presence has been overcame with some modification, considering it as exceptional case. For example for both products can be enabled the No registration or NAT presence option that skips the previous check. In this case some drawbacks can be observed, compared to the standard behavior. 9400AWY case No registration NE Reset Loopback commands Shifter management NOK NOK NOK Standard Access Control OK OK OK
3)
About the FTP application One of the most popular internet applications FTP could not work in presence of the NAT, unless specific implementations are provided. Generally the TCP checksum and the TCP sequence and acknowledge numbers must be updated to reflect the change in length of FTP control data portion: detailed explanation can be found on the RFC 2663. Consequently some applications can be impacted as: Software Download Backup and Restore
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
169 / 592
N.B.
as shown in Fig. 59. on page 154, the Ethernet interface can be used for the: local connection, through a crossconnect Ethernet cable, or through a HUB), to the PC: configured as Craft Terminal or running the TCO Suite directly from the SWP CDROM
connection to the TCP/IP network (provided that the NE has a valid TCP/IP address). Notice that by means of this connection, the NE can be reached by: the TMN OS (e.g. AlcatelLucent 1353NM) the PC running the TCO Suite directly from the SWP CDROM
by the Radio interface: the NE can be reached: from remote Craft Terminals (RECT function, explained in para.12.4.2 on page 54) or from the TMN OS or from the PC running the TCO Suite directly from the SWP CDROM, when the NEs Ethernet interface is not connected (but the NE is defined in the Supervision Network)
the local Craft Terminal, connected to the F interface or the local Ethernet interface, can reach other NEs by means of the RECT function
Ethernet Interface
F Interface
Radio Interface
Fig. 76. MAIN Unit front side: interfaces for equipment control N.B. As delivered from AlcatelLucent Factory, the NEs: local IP address (associated to the F interface) and Ethernet TCP/IP address (associated to the Ethernet interface) are both set at default value 10.0.1.2. Obviously, these values can be maintained only until the NE remains disconnected from the TCP/IP network and from any other NE, and must be changed as soon as possible.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
170 / 592
The CT can be locally connected to the NE through the Serial Port or through the Ethernet Network Port. Only one connection can be active at a time. Paragraphs 22.4.2.1 and 22.4.2.2 below describe how to switch from one to the other interface (this setting is at PC side only). N.B. This setting is necessary only in case you start the CT by Start Alcatel 1320CT [see step e )2 ) on page 174]. In case you start the CT clicking the button Operational & Maintenance of the TCO Suite Main Menu (see step e )1 ) on page 174], you do not need to carry out this setting, because proper setting is automatically setup answering the question of Fig. 77. on page 174.
22.4.2.1 Connection through the Serial Port Remind that, to connect the CT to the NE through the Serial Port, the Alcatel Virtual Network Card for Lower Layers Software has to be installed on the PC (refer to para. 53.3 on page 522). N.B. If the IP Address configured for the Alcatel Virtual Card has been changed after the 1320CT Platform installation, it is necessary to perform a recustomization by entering the following command:
Start Programs Alcatel SNMPCTKADDON v3.x.x SNMP AddOn Customization N.B. If the connection through Ethernet Network Port has been activated, to activate again the connection through the Serial Port enter the following command:
22.4.2.2 Connection through the Ethernet Network Port 1) Configure the Network Card on the CT as explained in the 1320CT Basic Craft Terminal Operators Handbook. Enter the NE and enable the Ethernet port on the NE (refer to para. 23.2.3 on page 195). Quit the NE and close the Network Element Synthesis application. Activate the CT Connection through the Ethernet Port by the following command:
2) 3) 4)
StartProgramsAlcatelSNMPCTKADDON v3.x.xNE ConnectionEthernet Port N.B. If the IP Address configured on the Ethernet port has been changed, it is necessary to perform a recustomization by entering the following commands: Start Programs Alcatel CTK v3.x.x Customization Start Programs Alcatel SNMPCTKADDON v3.x.x NE ConnectionEthernet Port Start Programs Alcatel SNMPCTKADDON v3.x.x SNMP AddOn Customization
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
171 / 592
22.5.1 NE management states The elementary building blocks of any telecommunication network are called Network Elements (NEs). The 9400AWY NE type is ULS. When operating with the Craft Terminal or the TCO Suite, the NE can present different management states according to the condition of the connection (supervision, local access, connection state, etc.). Also general Alarm states are presented. Management states are present at the Network Element Synthesis view level and at the ULS view level. All information relevant to the management states are described in the 1320CT Basic Craft Terminal Operators Handbook (see Tab. 78. on page 571). The Network Element Synthesis views enable to get access to the views described in this section. NE supervision and login The Network Element Synthesis view enables to work on local or remote NE ULS, selecting them and activating Supervision and Login, as described in para.22.5.2 on page 173. NE logoff and switch off In order to logoff the NE, or before disconnecting the F interface cable, or before switching off the NE, close the NE JUSM window and stop the NE supervision as described in para.22.5.3 on page 180.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
172 / 592
a)
Summary To access and login a 9400AWY NE from you PC for the use of the Craft Terminal functionalities: the CTNE connection can be: physically and logically local, through the RS232 serial cable for its connection to the equipment F interface physically remote but logically local through an ECTequipment connection via the public switched telephone network, as explained in Appendix E on page 553 physically and logically local, through a crossconnect Ethernet cable for the local direct connection between PC and NE Ethernet ports physically local but logically remote, by a normal Ethernet cable through a LAN for the connection between PC and NE Ethernet ports physically and logically remote, by a connection between PC Ethernet port and the NE through the RECT function or the TCP/IP network. you must have a UserName and password set in case of logically remote connection, you must know the NEs TCP/IP address
b)
Cable and network connections (if not yet done) 1) Local connection between the PC and the NE N.B. This operation has to be done whenever you have to access the NE locally; it is highly recommended when commissioning and maintenance tasks must be carried out. For other operations, consider that any NE reachable through the TCP/IP network [see point 3 ) below] can be accessed by the PC connected to the TCP/IP network [see point 2 ) below]
Following cautions stated in point e ) on page 36, through the suitable cable connect the ECT to the F interface or to the Ethernet interface of the MAIN unit (refer to Fig. 76. on page 170). To activate on the CT the connection through the Serial Port or through the Ethernet Port refer to para. 22.4.2 on page 171. 2) Connection of the PC to the TCP/IP network N.B. Just from NE management point of view, this operation has to be done whenever: you have no local access to any NE; or, even though you have local access to a NE, other NEs (you want to access in remote way) are not accessible from the local NE.
3)
Connection of the NE to the TCP/IP network N.B. Please take into account that this connection must not be done until the network routing data of the NE have been correctly defined. This definition is carried out during the Configuration Procedure described in chapter 32 on page 329.
If, in the following, you want to access the NE through the TCP/IP network (provided that it has already inserted correctly inside it from both physical and logical points of view), you must know the NEs TCP/IP address.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
173 / 592
c) d)
Power on the PC and wait for its startup (if not yet done) Only in case of CTNE connection via public switched telephone network: set up the connection on the public switched telephone network, as described in para.55.6 on page 560 Craft Terminal startup There are two ways to start the CT; they are not equivalent (note): (note) in case no NE is locally connected to the PC, these modes are equivalent (no CTNE connection setup)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
e)
1)
Preferred mode to start the CT to login a NE: click the button Operational & Maintenance of the TCO Suite Main Menu (see Fig. 55. and Fig. 56. on page 149). Refer to para.22.2.4.4 on page 150 for possible additional details. Notice that this choice in independent from the setting (at PC side) of the CTNE local connection on the Serial or Ethernet interface (explained in para.22.4.2 on page 171). This is the reason for preferring this simpler modality to start the CT to login a NE. if LLMAN (Alcatel Lower Layers Manager) is available on users system, user is asked to select between serial or Ethernet port connection by following screen:
Yes Fig. 77. Choice of Serial or Ethernet interface for PCNE physical connection in case of serial connection (YES answer), no other request is asked to user and 1320CT platform is automatically started with the related Serial port connection customization; in case of Ethernet connection (NO answer), no other request is asked to user and 1320CT platform is automatically started with the related Ethernet port connection customization; if LLMAN is not available on users system, the 1320CT will be run with the Ethernet connection customization and the user will be asked the same Direct/Remote request shown in Fig. 62. on page 156.
After a while, the Network Element Synthesis screen opens [step f ) on page 175]. 2) Alternative (not preferred) mode: in Windows: Start Alcatel 1320CT With this modality, you must know in advance if the local connection of the Craft Terminal to the NE is set (at PC side): on the Serial interface or on the Ethernet interface and consequently switch to one another, according to needs, as explained in para.22.4.2 on page 171. After a while, the Network Element Synthesis screen opens [step f ) on page 175]. WARNING: In case you use the Serial interface and the Network Element Synthesis does not open, read carefully para.22.2.7 on page 155 (Warning about interface customization carried out by the Direct Connection) N.B. Only in case of Finterface employment, for a correct operation, and only on some PCs with Windows 2000 or XP, it is necessary to start the Lower Layers Manager (Start Programs Alcatel Lower Layers Lower Layers Manager) before starting the ECT Platform (Alcatel 1320CT).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
174 / 592
f)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Network Element Synthesis screen There are two cases: the PC is locally connected to the NE; screen appears as follows:
Fig. 78. Network Element Synthesis screen (NE locally connected) the symbol indicates the NECT local connection by serial cable (Finterface). Such
symbol is not present if the connection has been established through the Ethernet interface. the symbol ? means they NE is not supervised.
Now: if you have to operate on the NE locally connected, proceed to step h ) on page 177. if you have to operate on a remote NE, proceed to step g ) on page 176. the PC is not locally connected to any NE; the screen (the first time you have launched 1320CT after its installation) is as follows (empty map):
Fig. 79. Network Element Synthesis screen (empty map) In this case you must create on this empty map the SNMP NE(s) you want to access, as described in following step g ) .
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
175 / 592
g)
SNMP NE creation N.B. This is a simplified description. For complete instructions, please refer to the 1320CT Basic Craft Terminal Operators Handbook, section EML CONSTRUCTION.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
To create a SNMP NE in the Network Element Synthesis map: you must know the NEs TCP/IP addresses. Note: the NE has always two addresses that can be equal or different: the Local Configuration address, see para.23.2.1 on page 192 the Ethernet Configuration address, see para.23.2.3 on page 195 and you must be sure that the NE is reachable from your PC. To make this check, open the Windows Command Prompt application and execute the command: ping <space> t <space> TCP/IP_address Leave this command run some minutes, verifying the connection is and remains established without interruptions, then close the command window. Note: in case the Local Configuration and Ethernet Configuration addresses are different from each other, perform this check for both. then, proceed as shown in Fig. 80. below, inserting in (2) the NEs own TCP/IP address. Note: in case the Local Configuration and Ethernet Configuration addresses are different from each other, you must insert the Local Configuration address. N.B. During the creation of the SNMP NE, if not set automatically, insert the number 161 in the TCP/IP Port field.
(2)
(1) (3)
Fig. 80. SNMP NE creation in the Network Element Synthesis map After such creation, the empty map of previous Fig. 79. becomes populated as in Fig. 81. below (the symbol ? means the NE is not supervised).
Fig. 81. Network Element Synthesis screen after SNMP NE creation If necessary, create the other SNMP NEs you may need. At the end, save the map (Map Save). In this way, when you start again 1320CT, you will find the same NEs you have created in this phase.
If you need to start supervision and, after, to login any NE present in the map, proceed to next step h ) 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
176 / 592
h)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Start supervision on a selected Network Element From a populated Network Element Synthesis map (e.g. Fig. 78. on page 175 and Fig. 81. above): 1) 2) select the interested Network Element clicking once left mouse button on it; while NE selected, with right mouse button choose Start Supervision and with left mouse button execute it, clicking once (Fig. 82. below). In alternative, while NE selected, with left mouse button choose Supervision Start
Fig. 82. Start supervision Wait until the symbol ? becomes at first (under exploration) and then colored (it
means NE in supervised state N.B.), as shown in Fig. 83. on page 177 N.B. In order to know the possible color meaning , refer to the: 1320CT Basic Craft Terminal Rel.3.x Operators Handbook: chapter SOFTWARE INSTALLATION paragraph Craft Terminal Configuration, subparagraph Communication with NE
Fig. 83. NE in supervised state N.B. If you want to change the User Label of the NE (select it Description ), take into account that it must not include the following characters: \ ? : * < >|.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
177 / 592
In this case, operate as follows: The JUSM must be closed. In the NE will appear a broken icon and a red bullet. Wait for the automatic restarting of the Supervision (at the end of the fading conditions). The icon in NE will become whole and the bullet will take the color relevant to the alarms (if any) active in the NE. If the Supervision does not start, close and open again the CT. If the Supervision does not start, switch off and switch on the PC. When the supervision of a NE has been started dont click on the name of the map. This operation causes the lock of the CT and the CT must be closed and opened again.
WARNING:
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
178 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
WARNING: Due to a deep fading, the radio remote NE can be unreachable. In this condition in the USM will appear the following message:
i)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Network Element login From screen Network Element Synthesis with NE in supervised state (e.g. Fig. 83. on page 177): 1) 2) select the interested Network Element (NE) clicking once right mouse button on it; while NE selected, with right mouse button choose Show Equipment and with left mouse button execute it, clicking once (Fig. 84. below). In alternative, while NE selected, with left mouse button choose Supervision Show Equipment
Fig. 84. Show Equipment 3) after a while, the Login screen appears (Fig. 85. below), that must be filled in with suitable values.
Fig. 85. Login screen 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. 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. For the Administrator to make such operations, please refer to para. 23.6 on page 214.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
179 / 592
and, after a while, the 9400AWY Main view opens (Fig. 87. on page 181) After the 9400AWY Main view has opened, all the available menus are introduced in para.22.6 on page 181. 22.5.3 NE Logoff or switch off Before disconnecting the F interface cable or before switching off the NE:
close the NE JUSM window (Fig. 87. on page 181) clicking then, in the Network Element Synthesis Window (Fig. 86. below), stop the NE supervision as follows: select NE with mouse left button holding it selected, select Stop supervision with mouse right button. In alternative, while NE selected, with left mouse button choose Supervision Stop
22.5.4 Closing the 1320CT application Verify that all NEs in the Network Element Synthesis map are in not supervised state Now you can close the Network Element Synthesis Window (Fig. 86. below) clicking
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
180 / 592
22.6.1 Introduction The 9400AWY view (see Fig. 87. below for the 1+1 configuration) contains the following fields, which provide the operator with the information needed to manage the NE: View title View area see para.22.6.2 on page 182 Main tool bar see para.22.6.4 on page 183 Menu bar see para.22.7.1 on page 184 Severity alarm synthesis (N.B.) Domain alarm synthesis (N.B.) Management state control panel (N.B.) Message/state area. N.B. For the meaning of the icons in the Severity alarm synthesis, Domain alarm synthesis and the Management state control panel refer to Alarm synthesis indication para.45.8.2.1 on page 437.
The Menu bar , Main Tool bar and the View area contained in the same NE view permit to perform all configuration and supervision operations and the display of the specific selected item. The view organization is detailed in the 1320CT Basic Craft Terminal Operator Handbook to which refer for the description. Main tool bar View title Menu bar Severity alarm synthesis Domain alarm synthesis
Tab panel
RESOURCE DETAIL AREA Management state control panel Fig. 87. 9400AWY Main view organization
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
181 / 592
22.6.2 View Area The View Area manages all domains from which the user can start. It is organized into tabbed panel, e.g. many windows placed one upon another. Each window is selectable (placing it on top of the others) with a tab shown on the top. Each panel represents a set of functions. The area consist of the following sets: Equipment External Points Line Interface Performance Radio Protection Schemes (in 1+1 configuration only) Loopback Each tab panel is labeled with the set name ( e.g. Equipment, Line Interface, etc ). Each tabpanel (e.g. functionalities area) consists of four areas: ResourceTree Area: displays all the available resources of the Radio NE. ResourceList Area: may be represented by: Tabular View (e.g., Line Interface Domain) or Graphical View (e.g., Equipment Domain). Tabular View: displays a tabular representation of the selected resource. As default, no tabular element is shown. Graphical View: displays a graphical representation of the selected resource. As default, no tabular element is shown. ResourceDetail Area: displays detailed information of a selected item in the Resource List area. As a default, no entry view is displayed as a consequence of the default behavior of the Resource List area.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
22.6.2.1 Resource Tree Area and Selection Criteria The Resource Area displays all the available resources in a tree structure like the protocol stack hierarchy. Each tree node consists of two symbols. The first symbol indicates the state of the structure e.g., if the symbol is + the tree can be expanded to a lower level. The tree structure can be collapsed if the symbol is . Finally, if there is no symbol, the node represents a leaf. The second symbol is the graphical representation of the resource. The user must select the resource by clicking with the mouse to carry out an action that depends on the type of click. Each resource listed above may be selected by using the mouse by a: Single left click; Double left click Single left click: By a single left click the resource is highlighted. This selection causes the activation of the resource list area, e.g., every time the user selects a resource in the resource tree area the corresponding Tabular or Graphical representation is displayed in the Resource list area . Double left click: Using this type of selection on the items of the resource tree, the user can expand the tree structure and activate the Resource list area displaying the same information described above. When the tree node is expanded a double click will collapse the tree node showing the same information in the Resource list area. 22.6.2.2 Resource Detail Area This area displays the detailed information of the selected object in the Resource list area. It also provides the types of operations available 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
182 / 592
The possible buttons for selection are the following: Apply Cancel OK Close Help this button activates the modify, but it does not close the window. this button closes the window without modifying the parameters displayed in the window. this button activates the modify and closes the window this button closes the window this button provides the help management for the functions of the supporting window.
Critical configuration choices generate a warning message for user confirmation before to be activated. 22.6.4 Main tool bar Besides navigation buttons, it contains some shortcut icons for specific tools or views (most of them are accessible also through the Menu Bar).
Current Configuration view previous screen next screen Summary Block Diagram view Quick Configuration Fig. 88. Main tool bar N.B. previous screen and next screen buttons are enabled according to the context.
not operative
Shortcuts available are: Quick Configuration: details in para.32.3.7 on page 343 Summary Block Diagram view: details in para.211.5 on page 285 Current Configuration view: details in para.211.6 on page 288
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
183 / 592
To navigate among the views and to set the TMN parameters. Configuration (second column). See para.22.7.3 on page 186
To set the general configuration of the NE and to show or modify some parameters (performance monitoring, OverHead parameters). Diagnosis (third column). See para.22.7.4 on page 186
To get information on the NE (alarms, performance monitoring, remote inventory). Supervision (fourth column). See para.22.7.5 on page 187
To set the supervision states (i.e. Craft Terminal enabling). SW Download (fifth column). See para. 22.7.6 on page 187
To activate the help on line. The menu bar also comprises other menus, presented only when a specific option is selected. Other Menus Equipment This menu is present only when the Equipment menu (selected in the View menu or in the Equipment tab panel) is active. It allows to go back to the supporting equipment of the displayed object. 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
184 / 592
The menu on the left side of the screen, allows to navigate among the views and to set some parameters, by means of the following entries: Previous: Open Object: Open in New Window: Duplicate View in New Window: Equipment: Goes back to the previous screen of the application. Not active.
Not active.
Not active. Opens the Equipment view. Then the Equipment menu is available on the menu bar. See Chapter 24 on page 219 Displays and sets the input/output environmental alarm. See Chapter 27 on page 247 Opens the Line Interface view to configure all the tributary ports. See Chapter 25 on page 227 Allows to manage the Performance monitoring. See Chapter 212 on page 289 Allows to manage all the functions relevant to the radio channels. See Chapter 26 on page 233
External Points:
Line Interface:
Performance:
Radio:
Protection Scheme: Allows to manage the Protection schemes in 1+1 configuration. See Chapter 29 on page 257. Loopback: Allows to manage the loopbacks available with the equipment. See Chapter 210 on page 267
N.B.
It is possible to enter directly menus Equipment, External Points, Line Interface, Performance, Radio, Protection Scheme, Loopback by clicking on the relevant tab panel above the view area.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
185 / 592
22.7.3 Configuration menu introduction This menu allows to set the general configuration of the NE and to show or modify some parameters, by means of the following entries: NE Time: Displays and set the NE local time. See para. 23.1 on page 190 See para. 23.2 on page 191 Manages the Alarm Severity Assignment Profile. See para. 23.3 on page 205 Allows the system configuration, providing the setting of all the parameters for the NE setup. See para. 23.4 on page 210 Allows a full system configuration through a guided procedure. See para. 23.5 on page 213 Allows the CT user profile management. See para. 23.6 on page 214 Inhibits/allows the event and alarm store in the Log See para. 23.7 on page 218
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
System setting:
Quick configuration:
Profiles management:
Log Switch:
22.7.4 Diagnosis menu introduction This menu allows to get information on the NE, by means of the following entries: Alarms: Displays the equipment alarms. See para. 211.1 on page 278 Manages the alarms and events stored in the NE. See para. 211.2 on page 279
Log Browsing:
Remote inventory: Displays the equipment Remote inventory information. See para. 211.3 on page 282 Abnormal condition list:
Displays the manually operations active in the NE. See para. 211.4 on page 284
Displays a global logical view (strictly related to the physical implementation) highlighting a synthesis of all the alarms and statuses present in the system (ODU+IDU). See para. 211.5 on page 285
Current configuration View: Displays the current configuration of the NE. See para. 211.6 on page 288
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
186 / 592
This menu allows to set the supervision states of the NE, by means of the following entries (see chapter 28 on page 251) : Access State: Manages the supervision access to the NE, via CT or OS. See para. 28.1 on page 251 Reset of the NE software. See para. 28.2 on page 252
Restart NE:
MIB Management: Allows to perform backup and restore operations of the MIB. See para. 28.3 on page 253 SW key: Displays the type of the key stored in the flash card. See para. 28.4 on page 256
22.7.6 SW Download menu introduction This menu allows to manage the NE software, by means of the following entries (see chapter 213 on page 297) : Server Access Configuration:
Manages the configuration of the FTP server to be used for the software download to the NE. See para. 213.1 on page 297
Init SW download: Manages the software download to the NE. See para. 213.2 on page 298 SW status: Shows and manages the status of the software packages installed in the NE memory banks. See para. 213.3 on page 299
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
187 / 592
188 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
23 CONFIGURATION
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
NE Time
on page 190 on page 191 on page 192 on page 193 on page 195 on page 196 on page 196 on page 200 on page 202
Network Configuration
Local Configuration NTP Configuration Ethernet Configuration IP Configuration
IP static routing configuration OSPF Area configuration IP Address configuration of PointToPoint Interfaces on page 204 on page 205 on page 210 on page 210 on page 212 on page 213 on page 213 on page 214 on page 214 on page 216 on page 217 on page 218
Routing information
Quick Configuration Profiles management Functional description Change Password procedure Users Management procedure
Log Switch
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
189 / 592
23.1 NE Time
The NE local time can be displayed and/or realigned to the OS time basis. From the Configuration pull down menu, select the NE Time option. The following dialogue box opens, from which you can set the local NE time.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 89. NE Time dialogue box The NE Time dialogue box displays the current NE time and the current OS time. To realign the NE time to the OS time, click on the Set NE Time With OS Time check box and click the Apply pushbutton to validate. The NTP status field is a readonly screen, which shows the configuration regarding the Network Time Protocol performed in the menu Configuration > Network Configuration > NTP Configuration. The Refresh pushbutton causes the refresh of the screen.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
190 / 592
To get access the Network Configuration option select the Configuration pull down menu, as shown in the following figure.
The Network Configuration allows to perform the following operations: Local Configuration: NTP Configuration: Ethernet Configuration: defines the local NE addresses allows to enable/disable the Network Time Protocol defines the configuration parameters necessary to manage the local NE providing a LAN Ethernet interface which comprises:
IP Configuration
IP static routing configuration: defines the Host/Network destination address for IP static routing OSPF Area configuration: IP Address configuration of PointToPoint Interfaces : defines the Open Shortest Path First address
defines the IP address of the interface which use the PPP protocol shows a summary of the information relevant to the routing which has been configured.
Routing information
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
191 / 592
23.2.1 Local Configuration N.B. This function is equivalent to that of Quick Configuration Procedures Step G on page 361 WARNING: read carefully Rules for the definition of the NEs Local IP and Ethernet IP addresses on page 361
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Select the Configuration pull down menu. Select the Network Configuration option and then, from the cascading menu, the Local Configuration option. The dialogue box opens ( see Fig. 91. on page 192 ) which allows to configure the local IP address of the NE. This local IP address is the IP address associated to the F interface and to the other interfaces which use the PPP protocol (the 3 NMS channels). Apply button is used to perform a configuration change of the data contained in the dialogue box and closes it; the dialogue is visible until the end of the operations and a wait cursor is displayed. Close button closes the dialogue. Help button provides some useful information on the dialogue.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
192 / 592
N.B.
This function is equivalent to that of Quick Configuration Procedures Step G on page 361
By selecting NTP Configuration the dialogbox in Fig. 92. opens, which allows to enable the Network Time Protocol.
Fig. 92. NTP Configuration dialogue box To enable the NTP put a tick in the check box of the Enabling NTP protocol field. If the NTP has been enabled in the Main Server address field write the IP address of the Server, which distributes the NTP and in the Spare Server address field write the IP address of the Spare Server, if any, which will distribute the NTP in case of failure in the Main Server. WARNING: It is mandatory to define both the Main Server address and the Spare Server address.
In case a Spare Server is not available, fill its address field with the same value of the Main Server.
To configure the setting click on Apply. The Refresh pushbutton causes the refresh of the screen.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
193 / 592
23.2.2.1 How to configure the NTP in a network When the NTP is enabled, one of the NE must be MASTER and all the other NEs must be SLAVEs. An example is shown in Fig. 93.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 93. Map As example NE1 must be set as Master: disable the NTP protocol.
NE2 is set as Slave: enable the NTP protocol; in the Main Server address field enter the IP address of NE1 (the Master NE); in the Spare Server address field enter the IP address of NE1.
NE3 is set as Slave: enable the NTP protocol; in the Main Server address field enter the IP address of NE1 (the Master NE); in the Spare Server address field enter the IP address of NE2.
NE4 is set as Slave: enable the NTP protocol; in the Main Server address field enter the IP address of NE1 (the Master NE); in the Spare Server address field enter the IP address of NE2.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
194 / 592
N.B.
This function is equivalent to that of Quick Configuration Procedures Step G on page 361 WARNING: read carefully Rules for the definition of the NEs Local IP and Ethernet IP addresses on page 361
Select the Configuration pull down menu. Select the Network Configuration option and then, from the cascading menu, the Ethernet Configuration option. The dialogue box in Fig. 94. on page 195 opens, which allows to define the parameters necessary to configure the Ethernet interface. The following areas are present: IP Section which comprises: IP Address to be assigned to the N.E. IP Mask relevant to the IP address IP Routing Protocol default is none state. If OSPF choice is selected, the Associated OSPF Area must be set. WARNING: please do never use the RIP choice present in the IP Routing Protocol field! OSPF Area pointer: if in IP Routing Protocol the OSPF protocol has been selected, it is possible to choose OSPF areas.
Enable which comprises two selections to Enable or Disable the Ethernet interface.
Refresh button refresh the information written in the upper port. Apply button performs a configuration change of the data. Close button closes the dialog without changes of the data.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
195 / 592
23.2.4 IP Configuration Select the Configuration pull down menu. Select the Network Configuration and then from the cascading menu, the IP Configuration option ( see Fig. 95. on page 196).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
23.2.4.1 IP static routing configuration N.B. This function is equivalent to that of Quick Configuration Procedures Step I on page 364
The dialogbox opens ( see Fig. 96. on page 197 ) and allows to configure the parameters for IP Static Routing Configuration. The following fields and data are present: [1] IP Address: allows to define the IP address necessary to reach a specific Host allows to define the IP Mask to reach a network allows to define the address of the next hop gateway allows to use point to point interfaces made available by the NE.
Apply button is used to perform a configuration change of the data contained in the complete table and close the view; the view is visible until the end of the operations and a wait cursor is displayed. New button is used to insert a new page. Delete button is used to delete the selected page. Close button closes the dialogue without changing of the data.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
196 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 96. IP static routing configuration screen By pressing Create pushbutton the screen in Fig. 97. on page 198 opens. In the Host or Network Address Choice field select: Host to address to a single IP address; Network to address to a range of IP addresses.
In the Default Gateway or Point to Point I/F Choice select: Default Gateway IP Address for the Ethernet interface; Point to Point Interface Index for the NMS channels (NMSRF, NMSV11, NMSG703) No pending (open) static routes are allowed. The default software uses first the static routes and then the dynamic routes. An open static route is always considered as a preferential path.
WARNING:
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
197 / 592
If in the screen of Fig. 97. above the Default Gateway IP Address check box has been selected, write in the Default Gateway IP Address field below the relevant IP address. If in screen in Fig. 97. above has been selected the Point To Point Interface Index check box, the screen in Fig. 98. on page 199 opens. N.B. It is also possible to define a Default Gateway Routing (refer to para.23.2.4.2 on page 199 for details).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
198 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 98. Point To Point Interface Choice In this screen one of the 3 NMS channels (NMSRF, NMSV11, NMSG703) can be selected. 23.2.4.2 Default Gateway Routing configuration It is also possible to define a Default Gateway Routing. To do that, in the screen in Fig. 97. on page 198 operate as follows: a) b) c) d) e) select Network in IP Address field, write 0.0.0.0 in IP Mask field, write 0.0.0.0 in Default Gateway IP Address field, write the required destination click OK
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
199 / 592
23.2.4.3 OSPF Area configuration N.B. This function is equivalent to that of Quick Configuration Procedures Step F on page 360
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The dialogbox opens ( see Fig. 99. on page 200 ) and allows to configure the parameters for OSPF (Open Shortest Path First) Area Table Configuration. The following fields and data are present: Id OSPF Area IP Address OSPF Area Stub
The fields give a synthetical information that includes all the addresses (specific to a NE and to a Network) in an Area. The Id identifier is used when configuring the PPP interface or the ETH/OS OSPF parameter. Apply button is used to perform a configuration change of the data contained in the complete RAP table and close the view; the view is visible until the end of the operations and a wait cursor is displayed. New button is used to insert a new page. Delete button is used to delete the selected page. Close button closes the dialogue without changing of the data.
Fig. 99. OSPF Area configuration screen WARNING: WARNING: Area 0 is managed and created by default with Id = 0 and IP address = 0.0.0.0 When the area is a Stub area, all interfaces inside the same Stub Area (NMS and Ethernet) must be defined Stub.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
200 / 592
N.B.
In the screen write the IP address, the IP mask and select the flag (True/False).
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
201 / 592
23.2.4.4 IP Address configuration of PointToPoint Interfaces N.B. This function is equivalent to that of Quick Configuration Procedures Step I , point [4] on page 364
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The dialogbox opens ( see Fig. 101. below) and allows to Enable or Disable the three NMS channels, which use the PPP protocol.
Fig. 101. IP Address configuration of PointToPoint Interfaces screen If required, enable or disable RF, V11 or G703 NMS access then Apply. Then, wait for the following confirmation window:
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
202 / 592
With this TMN inframe feature, 9400AWY 2.1 equipment is able to introduce in one of the time slots (TS 131) of the E1#1 tributary, a 64 kb/s signal as network management system (NMS or TMN) to transmit remotely this type of information along the E1#1 route; this selection is alternative to the local availability of TMNG703 (the mutual exclusion is automatic). It is also necessary that the farend E1#1 tributary is enabled and successfully provisioned. To activate the TMN inframe feature, in TMN G703 field (see Fig. 102. below) : set Mode to InFrame E1 define the required E1#1 Timeslot number (default is 1)
Fig. 102. IP Address and Timeslot configuration of PointToPoint InFrame E1 TMN Apply button is used to perform a configuration change of the data contained in the dialogbox and closes it; the dialog is visible until the end of the operations and a wait cursor is displayed. Cancel button close the dialog without changes of the data.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
203 / 592
23.2.5 Routing information Select the Configuration pull down menu. Select the Network Configuration and then from the cascading menu, the Routing information option. The dialogbox in Fig. 103. on page 204 opens.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
This screen is a readonly screen and displays the routing parameters currently active on the NE. The pushbutton Refresh allows to refresh the information shown in the screen. The Close button closes the dialogue without changing of the data.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
204 / 592
By selecting the Alarm Severities option from the Configuration menu the screen in Fig. 104. on page 206 appears. In this screen in the Profile Name field are listed the 4 default Alarm Severity Profiles: Profile No Alarms. With this profile all alarms are disabled. Profile Primary Alarms. This profile enables the emission of the primary alarms. General rules used to define the alarms severity: MAJOR: the alarm affects the service (it is service affecting); MINOR or WARNING (according to the impact of the alarm): the alarm doesnt affects the service (with the exception of HighBER alarm, which MINOR alarm severity is defined, even if it is service affecting).
Profile No Remote Alarms. This profile enables the emission of the primary alarms plus EW and LBER alarm. This profile uses the following rules to define the alarms severity: MAJOR: the alarm affects the service (it is service affecting); MINOR: the alarm is potentially service affecting but a protection has recovered the service; WARNING: the alarm cannot affect the service (independently from any protection).
Profile All Alarms. This profile enables the emission of all the alarms (included AIS and RDI). This profile uses the same severity of the Primary alarm profile, the only difference is that EW, LBER, AIS and RDI alarms are emitted. The rules used to define the alarm severity are the same of the Primary alarm profile. In case of alarms affecting a protection different severities are used for SA and NSA. The same severity is used both for SA and NSA in case of service independent alarms. The rules used to define the profile alarms severity described above, are not applied to the housekeeping alarms. In this case, in order to enhance the flexibility, a different severity is assigned to each alarm profile (WAR, MIN and MAJ).
N.B.
N.B.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
205 / 592
Fig. 104. Alarm Severities Profile In the screen of Fig. 104. on page 206 are available 2 buttons: N.B. Close: to close the screen. Clone: to create a new Alarm Severity Profile. To create a clone refer to para. 23.3.1 on page 207. Only 2 new profiles can be created.
An Alarm Profile is the complete set of the equipment alarms with their severity in case of Service Affecting situation and No Service Affecting situation. Each alarm has its Service Affecting and No Service Affecting attribute, which can differ according to the Alarm Severity Profile. N.B. To some objects in the equipment (overhead alarm, input housekeeping alarm, tributaries etc.) can be assigned an Alarm Profile. To do this association: select the tab panel (Equipment, Line Interface, FSO etc.) in which is present the object to be associated to a specific Alarm Severity Profile; select the object; select the Configuration menu in the relevant Resource Detail Area; select in the Alarm Profile field the Alarm Profile to be associated.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
206 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Select in the screen of Fig. 104. on page 206 the Alarm Profile to be cloned. Click the Clone pushbutton. The screen of Fig. 105. on page 207 appears. Digit the name to be assigned to the new Alarm Profile and click on Apply.
Fig. 105. Name of a cloned alarm profile Select again the Alarm Severity option from the Configuration menu. Select the just created Alarm Profile (Link 1 in the example of Fig. 106. on page 207).
Fig. 106. Clone of an Alarm Severity Profile USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
207 / 592
In this screen are available 4 buttons: Close: to close the screen without any change Rename: to change the name of the Alarm Severity Profile Modify: to modify the Alarm Severity Profile Delete: to delete the Alarm Severity Profile.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Click on the Modify button. To modify the severity of an alarm click on the Service Affecting field click on the suitable alarm and select a new severity (see Fig. 107. on page 208).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
208 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
To modify the severity of an alarm click on the No Service Affecting field click on the suitable alarm and select a new severity (see Fig. 108. on page 209).
To save the changes in the Alarm Severity Profile click on Apply. (By clicking on Cancel you quit the Alarm Severity Profile screen without any change) (see Fig. 108. on page 209).
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
209 / 592
23.4.1 NE Configuration The user can view and define the NE configuration by selecting the NE Parameters tabbed panel. The window displayed in Fig. 109. below will appear. The fields of this screen are practically equal to those of Quick Configuration Procedures Step A screen described on page 347. Please refer to it for details not given in this paragraph.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
210 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The information related to the modulation type is shown in the Modulation field. The possible values are 4QAM or 16QAM. The operator choice will be applied by clicking the related Apply button. The Capacity can be modified by selecting a different type according to Tab. 64. on page 348 and then selecting the Apply button to send the new value. The Tributary Port Configuration area is in the lower part of the window. The Impedance field allows the operator to configure the impedance of the E1 tributary (unbalanced 75 ohm or balanced 120 ohm). The impedance value will be applied by clicking on the related Apply button. N.B. After a change in the Type or Capacity or Modulation field the explicit confirmation shown in Fig. 110. is requested.
Fig. 110. Confirmation message N.B. Only one change can be performed in this screen. When the user confirms the change in the Type or Capacity or Modulation field all the other fields are disabled. To perform another change close the screen and enter again. After a change in the Type or Capacity or Modulation field (for the Modulation only for the remote NE configuration) at the completion of the operation the CT forces the JUSM closing with the following warning message:
N.B.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
211 / 592
23.4.2 Link Identifier The user can view and define the Link Identifier by selecting the Link Identifier tabbed panel. The window displayed in Fig. 112. below will appear. The fields of this screen are practically equal to those of Quick Configuration Procedures Step D screen described on page 358. Please refer to it for details. If changed, the new parameter values will be sent to NE by clicking on the related Apply button.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
212 / 592
23.4.3 Overhead
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The Overhead tabbed panel (Fig. 113. below) is present only if the Audio/User Service Channels plugin is configured and identifies the parameters for the management of the phone number (EOW function) and auxiliary channel interface: The fields Order Wire Configuration and Type in the Auxiliary Interface Configuration area of this screen are practically equal to those of Quick Configuration Procedures Step J screen described on page 366. Please refer to it for details. If changed, the new parameter values will be sent to NE by clicking on the related Apply button.
Fig. 113. Overhead Configuration The field Alarm Profile allows to associate to the Overhead alarms a particular Alarm Profile: a default alarm profile or an Alarm Profile previously created by the Operator (refer to para. 23.3.1 on page 207). To associate a different Alarm Profile click on the selection button and make the selection among the available Alarm Profiles. N.B. the default associated Alarm Profile is the Primary Alarm profile.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
213 / 592
The CT provides User login procedures (with the Show Equipment action) with the username displayed on the screen and the cleartext password not displayed on the screen. After 3 number of consecutive unsuccessful NE login attempts, the CT interface closes the login procedure. To access to the NE, a new Show Equipment action must be performed. Each user is associated to a predefined profile. [2] User number Twentyfive (25) users at most can be created. [3] User predefined profiles The list of supported features for each user profile is shown clicking on Appendix Craft Terminal Access Control in the Users Management help screen of Fig. 117. on page 217. For each functionality on user profile: Full indicates that the related screen is visible both for SET and GET operation; Read Only indicates that the related screen is visible, but only for GET operations (to see the MIB objects); Not Supported indicates that the related screen is not visible. The predefined profile are: Administrator (both for OS interface and CT/MibBrowser interface) This Operator can do everything on the NE. This Operator can manage security features (to add/remove users or to change own password and of all users). 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. To manage NE, the suitable menu items are enabled/disabled according to tables that can be viewed clicking on Appendix Craft Terminal Access Control in the Users Management help screen of Fig. 117. on page 217.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
214 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
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 cannot add or remove users, but 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 add or remove users. This Operator can change only own user password. viewer (both for OS interface and CT/MibBrowser interface) This Operator can only explore the NE. This Operator cannot add or remove users. This Operator can change own user password
All user predefined profiles can be connected to NE by a F interface (local serial interface) or by a remote interface. [4] NE scratch behavior At installation time (NE scratch), a default Administrator user is created with (lower case): UserName= initial Password = initialing The change of the password of this Administrator user is strongly suggested. Further this initial user, the Administrator is allowed to create/delete users belonging to the predefined profiles. The manager is prohibited from creating a user with username that already exists. The Administrator is allowed also to change user passwords (own or of all user by administrator). [5] Reset NE behavior All the security information sets (username/password/profile for each user) are stored on NE database (MIB data base). After the NE reset, these information sets are not lost and are recreated as before the NE reset. Complete online information is available in the Users Management help screen of Fig. 117. on page 217.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
215 / 592
23.6.2 Change Password procedure This procedure is available for all Operator Profiles, after the login (see para.22.5.2 on page 173) 1) Configuration Profiles Management Change Password
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 114. Profile Management options 2) Following screen appears; fill it with old and new passwords, taking into account password characteristics listed in point [1] on page 214. New password will be active at next login (after having logged out).
1 2 3 4
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
216 / 592
This procedure is available to users with the Administrator profile only. 1) 2) Configuration Profiles Management Users Management (see Fig. 114. on page 216) Following screen appears. Click on Help
Fig. 116. Users Management screen 3) Following screen appears. Click inside to explore matters and carry out the desired action.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
217 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
218 / 592
24 EQUIPMENT
All 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 types of functions offered to the user for Equipment Management. The equipment domain deals with the management of the NE as a whole and its physical components (subrack, boards,..) The main screen of the Equipment tab panel differs according to the configuration: Fig. 119. on page 220 for 1+0 configuration Fig. 120. on page 220 for 1+1 configuration.
In the Resource List Area is shown a graphical representation of the Equipment, which consists of one IDU and one ODU in 1+0 configuration and two IDUs and two ODUs in 1+1 configuration. The IDU consists of different boards according to the configuration: 16xE1 with or without the Ethernet ports, or 32xE1.
A colored ball gives information on the status of the associated object (Equipment, ODU, IDU, IDU board). The color differs according to the severity of the alarms: Green: no alarm White: indetermination alarm active (not operative) Cyan: warning alarm active Yellow: minor alarm active Brown: major alarm active Red: critical alarm active
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
219 / 592
ODU
ODU Status
ODU Ch#0 ODU Ch#1 ODU Status IDU/EXT Ch #1 IDU/MAIN Ch #0 IDU Status
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
220 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Equipment Status
To enter the IDU level click on the IDU object in the Resource Tree Area or double click on the IDU image in the Resource Detail Area. 24.1.1 1+0 configuration The screen in Fig. 121. below will appear.
IDU Status
Fig. 121. 1+0 IDU view One IDU is present: IDU channel#1: the Main IDU.
The IDU channel#1 includes the IDU/Main Ch#1 object, which includes according to the configuration type the following options: IDU/MAIN/DATA Ch#1 with the 4 Ethernet ports IDU/MAIN/16xE1 Ch#1 with the second group of 16xE1 tributaries to implement the 32xE1 configuration
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
221 / 592
24.1.2 1+1 configuration The screen in Fig. 122. below will appear for the Ch#1 and the screen in Fig. 123. below will appear for the Ch#0.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
IDU Status
IDU MAIN BOARD Status Fig. 122. 1+1 IDU/MAIN Ch#1 view
IDU Status
IDU EXTENSION BOARD Status Fig. 123. 1+1 IDU Ch#0 view Two IDUs are present: IDU channel#1: the Main IDU IDU channel#0: the Extension IDU
The IDU channel#1 includes the IDU/Main Ch#1 object which includes according to the configuration type the following options: IDU/MAIN/DATA Ch#1 with the 4 Ethernet ports (this board receives the power supply from the Main IDU only). IDU/MAIN/16xE1 Ch#1 with the second group of 16xE1 tributaries to implement the 32xE1 configuration
The IDU channel#0 includes the IDU/Ext Ch#0 object which includes according to the configuration type the following options: IDU/EXT/16xE1 Ch#0 with the second group of 16xE1 tributaries to implement the 32xE1 configuration
24.1.3 Board level To enter a board click on the object in the Resource Tree Area or double click on the board image in the Resource Detail Area.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
222 / 592
To enter the ODU level click on the ODU object in the Resource Tree Area or double click on the ODU image in the Resource Detail Area. The screen in Fig. 124. below will appear.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
223 / 592
Fig. 125. Alarm tab panel for a selected object The alarm tab panel has one row for each possible alarm, but only rows related to the active alarms are highlighted. When the alarm disappears it is automatically cleared in the screen. By putting a tick in the Include alarms from subnodes box the alarms currently active in the subnodes of the object will also appear. For every alarm the following information is given: Severity: the severity associated to the alarm and assigned in the Alarm Profile Event Time: the time of the generation of the alarm Entity: the entity involved in the alarm Probable Cause: the probable cause of the alarm Managed Object Class: the class of the alarm.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
224 / 592
24.3.2 Configuration
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The User Label field (Fig. 126. below) only display the label associated to the selected node in the tree. The field Alarm Profile allows to associate to the object alarms a particular Alarm Profile: a default alarm profile or an Alarm Profile previously created by the Operator (refer to para. 23.3.1 on page 207). To associate a different Alarm Profile click on the selection button and make the selection among the available Alarm Profiles. N.B. the default associated Alarm Profile is the Primary Alarm profile.
24.3.3 Remote Inventory The information about the unit can be read in the Remote Inventory panel in the Resource Detail Area as the following window shows (Fig. 127. below):
Fig. 127. Remote Inventory tab panel for a selected object For detailed information on Remote Inventory, refer to para.211.3.1 on page 282
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
225 / 592
226 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
25 LINE INTERFACE
All 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 type of functions available for Line Interface Management. The Line Interface domain deals with the management of the aggregate frame and tributary ports (line side). The Line Interface menu allows the user to manage the resources of the line interfaces: PDH tributary, NMS channel and Ethernet port, if has been configured. This domain view consists of the following areas (Fig. 128. below): Resource Tree Area: displays the tributary ports sorted by the channel number and the NMS interfaces. Resource List Area: displays tabular information about the selected resource in the tree area. Resource Detail Area: displays, through tabbed windows, the selected object s properties in list area. This area performs the available functions for involved resource.
Fig. 128. Line Interface View In the Resource List Area is given the information related to the tributaries: Interface Type (E1, Ethernet, NMS channels) Port Number: the port for a given channel and type of port Channel Number: the number of a channel Rate/Modulation: the bit rate of the tributary Signal Mode: the type of frame (Unframed/Framed/Disabled) To configure a line interface select the interface in the Resource Tree Area and configure the Configuration tab panel in the Resource Detail Area. N.B. In the Resource Tree Area below the Tributary PDH line are shown all the E1 tributaries according to the capacity selected in the System Setting menu (see para.23.4.1 on page 210) or in Quick Configuration Procedures Step A screen (described on page 347 ).
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
227 / 592
25.1.2 Configuration There are different tab panels according to the type of interface: PDH interface (para. 25.1.2.1 on page 228) NMS interface (para. 25.1.2.2 on page 230) Ethernet interface (para. 25.1.2.3 on page 231)
25.1.2.1 Tributaries PDH Configuration tab panel 25.1.2.1.1 ETSI Market The window, shown in Fig. 129. below for E1 tributaries, performs all the available functions for a PDH tributary port.
Fig. 129. Line Interface View: E1 Tributary Port In Fig. 129. above the following fields are readonly fields: Interface Type (E1) Port Number: identifies the ports for a given channel and type of port Channel Number
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
228 / 592
Signal Mode Line RAI Insertion Radio RAI Insertion Alarm Profile
Signal Mode (for E1 tributary) [1] Signal Mode The possible values are: Framed for the framed received signal Unframed for the unframed received signal Disabled The current state can be modified selecting a different signal mode value and then click on the Apply button to send the new value to NE. WARNING: In case of configuration with two Ethernet ports, some E1 ports must be disabled in order to allow the transmission of the Ethernet data. Refer to Tab. 65. on page 350 and to the relevant explanations in the same page.
[2]
Line RAI Insertion (for E1 tributary only) This feature is available for framed signals only. This field refers to the insertion of the RAI signal in Tx side. The possible alternative values are: Forced: the RAI insertion is performed Enabled: the RAI insertion is possible.
The current state can be modified selecting a different signal mode value and then click on the Apply button to send the new value to NE. [3] Radio RAI Insertion (for E1 tributary only) This feature is available for framed signals only. This field refers to the insertion of the RAI signal in Rx side. The possible alternative values are: Forced: the RAI insertion is performed Enabled: the RAI insertion is possible.
The current state can be modified selecting a different signal mode value and then click on the Apply button to send the new value to NE. [4] Alarm Profile The field Alarm Profile allows to associate to the tributary alarms a particular Alarm Profile: a default alarm profile or an Alarm Profile previously created by the Operator (refer to para. 23.3.1 on page 207). To associate a different Alarm Profile click on the selection button and make the selection among the available Alarm Profile. N.B. the default associated Alarm Profile is the No Alarm profile.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
229 / 592
Fig. 130. Line Interface View: NMS interface For the NMS channels (RF, V11 and G703) only the Alarm Profile can be associated. The field Alarm Profile allows to associate to the interface alarms a particular Alarm Profile: a default alarm profile or an Alarm Profile previously created by the Operator in menu Configuration > Alarm Severities. To associate a different Alarm Profile click on the selection button and make the selection among the available Alarm Profile.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
230 / 592
N.B.
For whole information on Ethernet port characteristics and management, refer to the Appendix D on page 547
The Data Tributaries Configuration tab panels described in following points [1] and [2] are available only if the Enhanced Ethernet plugin is installed and has been defined by choice 16E1GData in the Configuration % System Settings screen of Fig. 109. on page 210 [1] Tab panels relevant to all Data Tributaries ports as a whole QoS (Quality of Service) information and choices in Fig. 131. below is fully equal to that described in Quick Configuration Procedures Step B point [2] QoS configuration screen described on page 352 . Please refer to it for details not given here.
Fig. 131. Line Interface View: Data Tributary Port QoS Configuration tab panel Fig. 132. below shows Performance Monitoring counters of all Data Tributary Ports
Fig. 132. Line Interface View: Data Tributary Port PM counters USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
231 / 592
[2]
Tab panels relevant to each Data Tributary port The windows shown in Fig. 133. below and performs all available functions for one of four selectable Data tributary port.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 133. Line Interface View: individual Data Tributary Port Configuration tab panel a) Except the field Alarm Profile and the button Restart , information related to a data port Configuration panel is practically equal to that described in Quick Configuration Procedures Step B point [2] Ethernet GPort configuration screen described on page 351 . Please refer to it for details not given here. The field Alarm Profile allows to associate a particular Alarm Profile to the interface alarms: a default alarm profile or an Alarm Profile previously created by the Operator in menu Configuration > Alarm Severities. To associate a different Alarm Profile click on the selection button and make the selection among the available Alarm Profile. The Restart button allows forcing autonegotiation to begin link renegotiation.
b)
c)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
232 / 592
26 RADIO
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The Radio domain view allows the user to manage the resources of the radio transmission channel. A Radio NE consists of one or two radio channels with a set of functional blocks (tributary ports, radio ports etc). This domain view consists of the following areas (Fig. 134. on page 233): Resource Tree Area: displays the radio ports sorted by channel number. Resource List Area: displays tabular information about the selected resource in tree area. Resource Detail Area: displays, through tabbed windows, the object s properties selected in the list area. This area enables to execute the available functions for involved resource.
Fig. 134. Radio Domain View The following tab panels are present in the Resource Detail Area: Alarms: show the active alarms (para. 26.1 on page 234 ) Configuration: configures some radio parameters (para. 26.2 on page 234 ) Frequency: sets the Radio Frequency (para. 26.3 on page 235 ) RTPC & ATPC: sets the manual operation parameters or the automatic operation parameters (para. 26.4 on page 238 ) Power Meas: performs the Tx and Rx power measurements (para. 26.5 on page 241 ) BER: performs the BER measurement (para. 26.6 on page 246 )
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
233 / 592
26.1 Alarms
The fault management allows to check the current state of alarms related to the selected object. It is provided by the alarm panel like that shown in para. 24.3.1 on page 224.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
26.2 Configuration
The window shown in Fig. 135. below controls some functions for a Radio channel. To define the involved port, first select the port/channel in the tabular view: this selection enables the Resource Detail list to show the available functions for the single resource.
Fig. 135. RadioConfiguration menu 26.2.1 Local or Remote Transmitter Mute The information related to the transmitter status is shown in the Tx Mute field. To change the transmitter status choose the desired value (ON for Tx Squelched and OFF for Tx not Squelched) and press the related Apply button. WARNING: The Tx Remote Mute automatically works (on and then off) only if performed on the local NE (i.e. the NE to which the CT is connected). When a remote Tx mute is executed, the EC changes the channel in monodirectional way, in order to have the possibility to send the command to remove the mute. If the Network Element has been restarted after a MUTE, there is no more possibility to setup the channel, because the remote address is not known, and, in any case, to setup the channel a bidirectional communication is needed. The only way to remove the MUTE command is with local CT or from a remote CT which can reach the Network Element through another supervisory interface.
26.2.2 ODU service kit This field is a readonly field, which displays the state (connected or not to the ODU) of the light service kit cable (see para.32.10 on page 405 ) 26.2.3 Alarm Profile The field Alarm Profile allows to associate a particular Alarm Profile to the object alarms: a default alarm profile or an Alarm Profile previously created by the Operator (refer to para. 23.3.1 on page 207). To associate a different Alarm Profile click on the selection button and select among the available Alarm Profile. This panel belongs to TX Squelch one. N.B. the default associated Alarm Profile is the Primary Alarm profile. 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
234 / 592
26.3 Frequency
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The Frequency menu allows to read and, if necessary, to set the frequency parameters. The system can operate with different types of ODU according to the RF band and to the channel arrangement. There are ODUs which can manage only one shifter (fixed shifter) or several predefined shifters (flexible shifter). For details, according to ODU type employed, please refer to para.14.5 from page 104 onwards.
Fig. 136. Radio Frequency Functions with Shifter and Rx Freq enabled
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
235 / 592
Fig. 138. Radio Frequency Functions with shifter disabled WARNING: Since frequency setting could impact on traffic and requires a lot of time, following messages are shown in sequence:
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
236 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
[1]
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
ODU with one Shifter only If the ODU can manage only one shifter the Shifter field in the menu is not available (it is grey). In the Tx frequency field insert the Tx suitable frequency (the allowed Tx range is written in the Frequency Range field on the right side) and press pushbutton Apply (the Rx frequency is automatically calculated by using the inserted Tx frequency and the shifter). Note: During the command setting the CT is frozen. Waiting time: max 30.
[2]
ODU with different available Shifters In the Tx frequency field insert the suitable Tx frequency and press pushbutton Apply. In the Shifter field select the suitable shifter and press pushbutton Apply (the Rx frequency is automatically calculated by using the inserted Tx frequency and the shifter). Now the Rx frequency can be changed in order to implement a suitable new shifter. Insert the new value in the Rx frequency field and press pushbutton Apply. When the Rx frequency is changed a specific warning message about possible impact on the traffic will appear. This message requires an explicit confirmation to proceed. At the end a specific result message appears to inform the operator that the operation has been completed (or failed in case of failure). At this point other operations can be normally requested by the operator. WARNING: Whenever the difference (as absolute value) between Rx and Tx frequencies is different from the shifter value, the background of the Shifter field changes to red color and the specific warning message shown in figure below is written on the Frequency screen.
Fig. 139. Not standard frequency arrangement To restore a Standard Shifter configuration, the operator has only to apply again the selected (or another one) Shifter value or to apply again the Tx frequency. As result, the normal Frequency screen is restored removing both red color as background of the Shifter field and the specific warning message. Note: During the command setting the CT is frozen. Waiting time: max 30.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
237 / 592
Static value of the Tx power ATPC Rx Threshold Dynamic value of the Tx power (20 dB range)
Fig. 140. RTPC & ATPC WARNING: When you change the modulation scheme (from 4 QAM to 16 QAM or viceversa) the Tx power (in case of operation with RTPC) and the ATPC range (in case of operation with ATPC) of the new modulation scheme must be in the correct range. If the value is out of range the relevant field in the RTPC & ATPC screen appears empty (automatically is associated a default value, but this value is not displayed). Fill the field with the suitable value.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
238 / 592
26.4.1 ATPC
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The ATPC can be Enabled or Disabled. The new value will be applied when the Apply button is pressed. If the ATPC has been enabled, the ATPC Range and ATPC Rx Threshold fields must be filled. WARNING: In 1+1 Configuration (HSB or FD) the ATPC information, sent back from the Rx side to Tx side, is the information relevant to the channel (protecting or protected) currently active in the EPS protection scheme. The two transmitters are, therefore, driven by the same ATPC control signal.
[1]
ATPC Range The Min Value and Max Value, for Tx Range in the ATPC management, are shown in the Atpc Range area. The min and max levels can be changed by writing the new values in the fields. WARNING: Obviously, you must set Max TX Power value > Min TX Power value. If you want to set the minimum value of the range greater than the current maximum value, you must at first change the maximum value, then change the minimum value (obviously setting it smaller than maximum).
When the Apply button is pressed the new values will be applied. [2] ATPC Rx Threshold The value of the power low threshold can be changed by writing the new value in the field. When the Apply button is pressed the new values will be applied. WARNING: During the reconfiguration phase or during the activation of a new software, the alarm ATPC loop could be (but not necessarily is) active. It is recommended to use the following Tab. 56. in order to set the ATPC threshold. The ATPC shape is calculated using the max capacity.
WARNING:
Tab. 56. ATPC Range Rx Threshold for ETSI TH 4 QAM Min Value Max Value Min Value Max Value 7/8 GHz 73 60 69 60 13 GHz 74 60 70 60 15 GHz 74 60 70 60 18 GHz 72 60 68 60 23 GHz 72 55 68 55 25 GHz 71 50 67 50 28 GHz 71 50 67 50 38 GHz 70 50 66 50
16 QAM
The applied rule is: Frequency Band 7/8, 13, 15 & 18 GHz 23 GHz 25 & 38 GHz ATPC Rx threshold setting Min Value PRxth + 8 dB PRxth + 8 dB PRxth + 8 dB 106 Max Value 60 dBm 55 dBm 50 dBm according to modulation scheme,
PRxth: Received power level correspondent to BER payload and ETSI standard
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
239 / 592
26.4.2 RTPC [1] Nominal Power The Nominal Value field in the RTPC area is a readonly field and shows the nominal value of the transmitted power (expressed in dBm). [2] Tx Power The Tx Power field in the RTPC area shows the current value of Tx power (expressed in dBm), when the ATPC is disabled. In this case, it is possible to modify this value ERROR FREE in ATPC Range (Pnom 20 dB) with 2 dB max step allowed, by writing the new value and by pressing the related Apply button N.B. During the command setting the CT is frozen. Waiting time: < 15.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The new value must be within the allowed transmitted power range. This range is shown in the Power Value label of RTPC area. If the ATPC is enabled, the Tx power value cannot be modified.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
240 / 592
The Power Measurements capability is performed through the Power Meas tabbed panel in the resource detail view (Fig. 141. below).
BER
Fig. 141. Power Measurements The Measurement screen allows the operator to set initial parameters for the required measurement. Measurement interval fields allow the operator to set the timeduration of the measurement. The default is Days: 7, Hours: 0, Minutes: 0. A 7day measurement interval is also the maximum allowed interval. Sample time field is the period between two consecutive measurement samples. The choice is among 6, 30, 60 sec. The last section of the dialog is referred to an optional Log file. By selecting Create File the log file is created and a default path and name for this file is displayed to the operator. The file is stored in the ALCATEL/CTKv3.x.x directory. N.B. The file name must not include the following characters: \ ? : * < > |.
The log file contains the sample value and records the measurement up to a maximum dimension ( 7 days for a 2 s sample time). By clicking on the Start button the screen Power Measurement Graphic appears (see Fig. 141. on page 241). The Power Measurement Graphic is available only if the CT is connected to the NE. The screen in Fig. 142. shows the Tx and Rx measurements related to the local NE. Through this screen the operator can see, in real time, the power transmitted by the local and remote transmitter (Tx) and the power received by the local and remote receiver (Rx). USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
241 / 592
The top of the screen offers all the characteristics present in the current measurement: Radio port: gives the symbolic name associated to the radio channel being analyzed; Sample time: indicates the frequency used to send the measurement requests to NE; Start time: is the first request time; Stop time: is the interval time selected in the previous parameters window, added to the start time; Time: is the current response time; Log File: is the complete pathname of the file where the received values are stored.
Fig. 142. Power Measurement Graphic By clicking on Show details box, on the left side of the Power Measurement Graphic (see Fig. 142. on page 242), a new table appears (Fig. 143. on page 243); this table shows the following relevant values of the received and transmitted power:
Tx Local End
max TX local value and date when this value was received for the first time. min. TX local value and its current date when this value was received for the first time. current TX local value and its current date.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
242 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The top graphic screen area shows the TX curves (local and remote), while the bottom area shows the Rx curves (local and remote). Note that the colors represent the linked endpoint of the two NE; for example, if the local TX is blue, the remote receiver will also have the same color.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Tx Far End
max TX remote value and date when this value was received for the first time. min. TX remote value and its current date when this value was received for the first time. current TX remote value and its current date.
Rx Local End
max Rx local value and date when this value was received for the first time. min. Rx local value and its current date when this value was received for the first time. current Rx local value and its current date.
Rx Far End
max Rx remote value and date when this value was received for the first time. min. Rx remote value and its current date when this value was received for the first time. current Rx remote value and its current date. PTx and PRx levels software readings tolerance is: PTx = Real Value 2dB @ ODU Operating temperature range 33C + 55C on 020dB RTPC range PRx = Real Value with 3 dB accuracy from 41 dBm down to 69 dBm included (nominal received levels) PRx = Real Value with 4 dB accuracy from 30 dBm down to 40 dBm included and from 70 dBm down to threshold included
N.B.
Fig. 143. Power Meas Details WARNING: If in the Tx end field the indication in dBm is +99, the Transmitter is off (or in HSB Configuration the transmitter is in standby). If in the Tx end field the indication in dBm is +99 and, at the same time, in the relevant Rx end field the information in dBm is 99, probably the supervision has been lost. The confirmation of the loss of the supervision is given by a broken red icon in Network Element Synthesis screen.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
243 / 592
26.5.1 How to read a Power Measurement file Click on Read File field and press on the Select File button. The directory of the CT automatically opens to navigate and get the power measurement file. N.B. as default, the measurement files are stored in the ALCATEL/CTKv3.x.x directory and have extension .txt.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 144. Name of File ( Log File ) selected screen Select the desired file and click the Start button in Fig. 141. on page 241 to open the file.
Fig. 145. Example of Power Measurement File Reading The button in the lower part of the window allow to flow the graph within the measurement interval. Select the .txt file and click with the mouse right pushbutton to open .txt file with a text editor (e.g. WordPad) and to see the power information in tabular mode (see Fig. 146. on page 245). 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
244 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
245 / 592
Fig. 147. BER Features [1] Start and stop BER Measure The BER measure function can be started (Start button) or stopped (Stop button) Request BER Measure data The information of BER Measure is not automatically updated in the Measure part. If the user wants to see the current information of BER Measure, with the Refresh button, the information is updated. The following parameters are provided: elapsed time BER measurement (see point [3] below) suspect measurement indication. The measurement is marked as suspect if the NE was not able to collect all the violations in the observation period (card missing, card fail). BER Measurement calculation The BER calculation formula is the following: Pbit_out . (CNT_ERR_1SEC/ T) where: Pbit_out is BER measurement assumes the following values: = 4.6E07 (32E1) = 9.2E07 (16E1) = 1.8E06 (8E1) = 3.7E06 (4E1) = 7.4E06 (2E1) CNT_ERR_1SEC (number of violations) is the HW counter which accumulates the errors in the 1 sec. window and after each reading, it resets itself and restarts (the software collects the counter value each second and to count the T period) T (elapsed time) is the difference between the start time and the stop time of the measurement.
[2]
[3]
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
246 / 592
27 EXTERNAL POINTS
All 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 types of functions offered to the user for External Points Management (please refer to para.13.6.1 on page 85 for physical implementation). There are two types of external points: input and output external points. By clicking on the tree root, displayed in Fig. 148. below, the tree will be expanded according to the equipment configuration. A single left click selection of a tree element causes the activation of the corresponding Tabular representation displayed in the Resource list area. A click on a row in the Resource list area opens the Configuration menu in the Resource Detail Area. An example of this mechanism is displayed in the Fig. 148. below.
The lower part provides the possible parameters, which can be modified; after a row selection, the user can modify the User Label, the Polarity and can associate a different Alarm Profile by clicking on the Selection button. The operator choices will be sent to NE after selecting the Apply button.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
247 / 592
Fig. 149. Output External Points: CP01 ... CP04 (Manual activation)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
248 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 150. Output External Points: CP01 ... CP04 (Automatic activation) The last three external points (FAIL IDU, FAIL ODU Ch.#1, FAIL ODU Ch.#0) (Fig. 151. on page 250) are described by the following parameters: Id: identification number UserLabel: a userfriendly name can be associated to an external point Polarity: describes the polarity (Active Closed/ Active Opened). In this field the polarity of the external point can be changed. These three output external points are automatically activated when the relevant equipment summarizing alarm is active.
N.B.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
249 / 592
Fig. 151. Output External Points View: FAIL IDU, FAIL ODU
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
250 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
28 SUPERVISION
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 152. Configuration of the Craft access state from the Equipment NE view in the OS mode
From the confirmation dialogue box that opens, you can confirm or cancel the Craft access operation using the Yes or No pushbutton. The request is sent up to the OS which accepts or refuses it. If the OS doesnt answer in a predefined time, it is assumed that the NE is in the Craft access state and can be managed by a Craft Terminal.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
251 / 592
28.1.2 Switching from the Craft Terminal access state back to the OS access state Select the Supervision pull down menu. Then from the Access State cascading menu select the OS option. From the confirmation dialogue box that opens, you can confirm or cancel the OS access operation. The NE is now managed by the OS. N.B. The key symbol icon on the management states of the NE view indicates whether the NE is managed by a craft terminal or by the OS. Local Craft Terminal access is denied on recovery phase after a loss of communication of the NE. When the communication with the NE is lost, the OS automatically recovers the communication and forces the state existing before the loss of communication (therefore, Craft Terminal access can be denied or granted).
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.
28.2 Restart NE
The RESTART operation is a software reset and can be executed in normal traffic conditions. From the Supervision cascading menu, select the Restart NE option.
Fig. 154. Restart NE confirmation Click the OK button to confirm the restart N.E. operation Click the Cancel button to abort the restart N.E. operation. WARNING: After the activation of the Restart NE Command (or after the pressing of the HW reset pushbutton) the LLM icon is frozen and the supervision of the local NE and the remote NE is lost.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
252 / 592
This menu (Fig. 155. below) refers to the management of the MIB (Management Information Base). The MIB includes all the system configuration data, except the routing configuration data: 1. 2. 3. Local configuration NTP server configuration Interface configuration NMS configuration Ethernet configuration IP Static Routing configuration OSPF Area configuration IP Address configuration of point to point configuration Systems local address
4.
IP configuration
Fig. 155. MIB Management The routing configuration data are NOT stored into the MIB file, because considered unique to a particular system in a network and are NOT meant to be reproduced on other systems in the same network, because will cause conflicts in the supervision network centre.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
253 / 592
28.3.1 Backup This menu (Fig. 156. below) allows to save on the CT the NE configuration. To backup the configuration write the filename in the Backup field (Lower part) and press Confirm Backup.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
WARNING: The backup file name must not include the following characters: space, &, /.
Fig. 156. Backup screen Confirm the backup operation to start the operation. In the upper part appears the list of the previously created backups. By pressing Refresh the list is updated with the insertion of the just created backup.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
254 / 592
28.3.2 Restore
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
This menu (Fig. 157. below) allows to download to the NE a previously created backup.
Fig. 157. Restore screen Select one of the backups to be downloaded in the upper part and press Confirm Restore. (By pressing the Reset pushbutton the previous selection is cancelled and a new selection can be made). Confirm the restore operation to start the operation. To activate the new configuration enter command MIB Management > Activate.
28.3.3 Activate This command (Fig. 158. below) allows to activate the configuration just downloaded with the restore.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
255 / 592
28.3.4 Remove file This menu allows to remove from the list of the backups one particular backup. To remove a backup select the backup file in the upper part and press Confirm Remove. Confirm the operation to start the operation. By pressing Refresh the list of backups in the upper part of the screen is updated.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
28.4 SW key
From the Supervision cascading menu, select the SW key option. In this screen the type of the key (stored in the flash card installed in the Main IDU unit) is shown.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
256 / 592
29 PROTECTION SCHEMES
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
This domain is present in 1+1 configuration only. This domain view consists of the following areas (Fig. 160. below): Resource Tree Area: displays the radio ports sorted by channel number. Resource List Area: displays tabular information about the selected resource in tree area. Resource Detail Area: displays, through tabbed windows, the properties done in list area. This area enable to perform the available functions for involved resource.
By clicking on the tree root displayed in Fig. 160. below, the tree will be expanded according to protection schemes supported.
Fig. 160. Protection Schemes A single left click selection of an element tree causes the activation of the corresponding Graphical representation displayed in the Resource list area. An example of this mechanism is displayed in the Fig. 161. on page 258 . Three 1+1 protection schemes have been implemented: Mux/Demux protection: EPS protection in Tx and Rx sides Radio protection: RPS Hitless Switch in Rx side HSB protection: Hot Standby protection
To see the current position of the switches enter the menu Diagnosis > Summary Block Diagram View (refer to para. 211.5 on page 285): Mux/Demux Protection corresponds to the Switch Tx and the Rx output switch in Fig. 195. on page 287 the Radio protection corresponds to the Switch RPS HS in Fig. 195. on page 287 the HSB protection is implemented in the ODU: one Transmitter is connected to the antenna (active), the other transmitter is in standby. Refer to Fig. 195. on page 287 . The HSB protection is available only if the HSB configuration has been selected.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
257 / 592
29.1.1 Schema Parameters The window Schema Parameters displays the parameters that can be modified. The Schema parameters are: Protection Type: this parameter is defined at creation time and it is read only. The supported type is: 1+1, e.g. a working channel (Main) is protected by a protecting channel (Spare). Operation type: it defines if automatic restoration from protecting to protected channel is allowed (revertive mode) or inhibited (not revertive mode). In Revertive Operation, after an abnormal condition such fading, hardware problem or maintenance action, the relevant protection will automatically switch back to channel #1 as a default state.
The operator choice for Operation Type will be applied by clicking on Apply button.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
258 / 592
29.1.2 Commands
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
To enter the Commands menu, click, in the Tree view (Fig. 162. below), on the Spare #0 element or on the Main #1 element
Fig. 162. Mux Protection Switch (example for Main #1 selected) The operator can modify the state of the switch through commands Lockout, Forced and Manual. Tab. 57. Command priority list Command Lockout Forced Automatic switch Manual Priority 1 2 3 4
Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel) for both EPS and RPS and disables the hitless function, independently of the possible active alarms. This command activates signaling ABN. WARNING: the EPS Lockout command is not error free, even if it is raised when traffic is not on the spare channel. Forced has higher priority than the automatic operation: the activation of this command forces in service Channel 0, independently of the possible active alarms. This command activates signaling ABN. Automatic Switch is the normal operation condition: the position of the switch depends on the commands generated by the logic. Manual has the lowest priority: it is performed only if there are no alarms that can activate an automatic switch. It cannot be performed if Lockout or Forced commands are already activated. If this command is active, it will be removed by an incoming alarm. This command does not activate signaling ABN. The Forced command for channel 1 is equivalent to the Lockout command for the channel 0. In both case, the result is that the relevant channel protection path is forced to standby status. to release a previously activated command select None and click on Apply.
Note : N.B.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
259 / 592
29.2.1 Schema Parameters The window Schema Parameters displays the parameters that can be modify. The Schema Parameters are: Protection Type field: defines the protection schema architecture: 1+1 Hitless; Operation Type field: the possible values are revertive (automatic restoration allowed) or notRevertive (automatic restoration Inhibited). In Revertive Operation, after an abnormal condition such fading, hardware problem or maintenance action, the relevant protection will automatically switch back to channel #1 as a default state.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
260 / 592
29.2.2 Commands
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
To enter the Commands menu, click, in the Tree view (Fig. 164. below), on the Spare #0 element or on the Main #1 element
Fig. 164. Radio Protection Switch (example for Main #1 selected) The operator can modify the state of the switch through commands Lockout, Forced and Manual. WARNING: whenever EPS lockout is set (see para.29.1.2 on page 259 ), RPS is switched on CH1, and these commands are not available (greyed). Tab. 58. Command priority list Command Lockout Forced Automatic switch Manual Priority 1 2 3 4
Lockout has higher priority than Forced: the activation forces in service Channel 1 (default channel), independently of the possible active alarms. This command activates signaling ABN. Forced has higher priority than the automatic operation: the activation of this command forces in service Channel 0, independently of the possible active alarms. This command activates signaling ABN. Automatic Switch is the normal operation condition: the position of the switch depends on the commands generated by the logic. Manual has the lowest priority: it is performed only if there are no alarms that can activate an automatic switch. It cannot be performed if Lockout or Forced commands are already activated. If this command is active, it will be removed by an incoming alarm. This command does not activate signaling ABN. The Forced command for channel 1 is equivalent to the Lockout command for the channel 0. In both case, the result is that the relevant channel protection path is forced to standby status. to release a previously activated command select None and click on Apply.
Note : N.B.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
261 / 592
29.3.1 Schema Parameters The window Schema Parameters displays the parameters that can be modify. The Schema parameters are: Protection Type: this parameter is defined at creation time and it is read only. The supported type are: 1+1 (onePlusOne) ,e.g. a working element is protected by one protecting unit. Operation type: it defines if automatic restoration from protecting to protected unit is allowed (revertive mode) or inhibited (not revertive mode). In Revertive Operation, after an abnormal condition such fading, hardware problem or maintenance action, the relevant protection will automatically switch back to channel #1 as a default state.
The operator choice for Operation Type will be applied clicking on Apply button.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
262 / 592
29.3.2 Commands
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
To enter the Commands menu, click, in the Tree view (Fig. 166. below), on the Spare #0 element or on the Main #1 element
Protection Command Status NOT Automatically Updated Fig. 166. HSB Tx Protection Commands (example for Main #1 selected) The operator can modify the state of the switch through commands Lockout, Forced and Manual. Tab. 59. Command priority list Command Lockout Forced Automatic switch Manual Priority 1 2 3 4
Lockout has higher priority than Forced: the activation connects to the antenna Transmitter 1 (default transmitter), independently of the possible active alarms. This command activates signaling ABN. Forced has higher priority than the automatic operation: the activation of this command connects to the antenna Transmitter 0, independently of the possible active alarms. This command activates signaling ABN. Automatic Switch is the normal operation condition: the position of the switch depends on the commands generated by the logic. Manual has the lowest priority: it is performed only if there are no alarms that can activate an automatic switch. It cannot be performed if Lockout or Forced commands are already activated. If this command is active, it will be removed by an incoming alarm. This command does not activate signaling ABN. The Forced command for channel 1 is equivalent to the Lockout command for the channel 0. In both case, the result is that the relevant channel protection path is forced to standby status. to release a previously activated command select None and click on Apply.
Note : N.B.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
263 / 592
Fig. 167. Rx Static Delay menu The Rx Static Delay must be compensated during the commissioning. Two compensating modes are possible: Automatic Manual These two modes are alternative. To activate the Automatic mode click on the Align pushbutton (the compensation procedure is automatically done). To activate the Manual mode: [1] [2] [3] N.B. click on the Start pushbutton; write the values in the Channel 0/1 fields (N.B.); click on the Apply pushbutton to send the value to the NE. Write in one field the suitable value (in range 031) and in the other field write 0.
At the end of automatic procedure, a warning message will be displayed to explain the result of procedure. For example, if procedure failed the following message is shown:
Fig. 168. Rx Static Delay panel Warning message for fail If procedure is correctly ended, a similar warning message will be displayed. When the manual procedure is started, the status of buttons change to allow the available procedure: Stop manual procedure Align of values during manual procedure as shown in Fig. 169. . The automatic procedure is disabled during manual operation.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
264 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 169. Rx Static Delay in auto mode When the user stops the manual procedure by clicking on the Stop button, the status of the buttons will turn on the initial one.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
265 / 592
266 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
210 LOOPBACKS
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The functions described in this section allow to perform the test operations by loopbacks.
Some loopbacks are declared local only; this means that, when the NE receives a loopback request, the NE executes the request only if it is arriving from the local ECT. This restriction has been introduced to avoid the risk of a permanent disconnection from the NMS of a remote NE. 210.1.1 IDU loopbacks [1] Near end IDU cable loopback internal local only
Near end IDU Near end ODU RF 16E1/E3 LIU FRAME MODEM IF RF IF RF MODEM FRAME LIU 16E1/E3 Far end ODU Far end IDU
Fig. 170. Near end IDU cable loopback [2] Far end IDU tributary loopback internal This loop can be activated separately on each tributary (example: in 16 E1 mode the ith trib. can be looped independently from the others). Assuming that an ECT is connected to the station A, the NE A uses the dedicated link connection to activate/deactivate this loop on the remote station B. In this way, from station A, it is possible to activate/deactivate this loop without accessing the NE B through a RECT. It is not forbidden (even if not considered here) to use a RECT from station B to activate this loop.
Near end IDU Near end ODU RF 16E1/E3 LIU FRAME MODEM IF RF IF RF MODEM FRAME LIU 16E1/E3 Far end ODU Far end IDU
Station A
Fig. 171. Far end IDU tributary loopback
Station B
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
267 / 592
[3]
Near end tributary loopback line It can be activated separately on each tributary (example: in 16 E1 mode the ith trib. can be looped independently from the others). It is not forbidden (even if not considered here) to use a RECT from station B to activate this loop.
Nearend IDU Nearend ODU
RF
16E1/E3
LIU
FRAME
MODEM
IF RF
IF RF
MODEM
FRAME
LIU
16E1/E3
Station A
Fig. 172. Near end tributary loopback
Station B
210.1.2 ODU loopbacks [1] Near end ODU cable loopback internal local only
Near end IDU Near end ODU RF 16E1/E3 LIU FRAME MODEM IF RF IF RF MODEM FRAME LIU 16E1/E3 Far end ODU Far end IDU
Fig. 173. Near end ODU cable loopback It is executed by the NE only if it sent by the local ECT. [2] Near end RF loopback internal local only (N.B.) Taking into account the HW implementation of the RF loopback, it is not necessary to switch off the remote transmitter during a local RF loopback.
Nearend IDU Nearend ODU
RF 16E1/E3
LIU
FRAME
MODEM
IF RF
IF RF
MODEM
FRAME
LIU
16E1/E3
Fig. 174. Near end RF loopback N.B. RF loopback is optional and provided only with specific configurations
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
268 / 592
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. N.B.
The loopbacks can be activated on the local NE only. The DATA block in Fig. 175. is present with the Ethernet port option only.
CT
IDU
DATA MUX/ DEMUX TRIB MODEM
ODU
ODU
IDU
Tab. 60. Available loopbacks N.B. Refer to: Fig. 176. on page 270 (1+0 configurations) Fig. 177. on page 271 (1+1 configurations)
Loopback name
No.
Location
Loopback type
Note
Near End
External line Input loopback at tributary level. Loopback toward the station at tributary level. Not available. remote
Tributaries
Near End
Internal
Tributaries
Far End
Internal
Loopback in the remote station at tributary level. Loopback at the IDU output at aggregate level. Loopback at the ODU input at aggregate level. RF local loopback. (N.B.)
Channel 1
Near End
External line
Channel 1
Near End
External line
Channel 1
Near End
External line
WARNING:
loopbacks on disabled tributaries are not applied (even if no messages are displayed when the command is sent)
N.B. RF loopback is optional and provided only with specific configurations Before activating the RF loopback, the Remote Tx must be muted (Menu Radio > Configuration)
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
269 / 592
IDU CABLE
ODU CABLE
If any indication does not correspond to the expected one, press Refresh to actualize the view.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
270 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
In Fig. 176. below is given the association of all the possible loopbacks in 1+0 configurations and their positions in the block diagram of the equipment provided by the Summary Block Diagram View option, available in the Diagnosis menu.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
In Fig. 177. below is given the association of all the possible loopbacks in 1+1 configurations and their positions in the block diagram of the equipment provided by the Summary Block Diagram View option, available in the Diagnosis menu.
If any indication does not correspond to the expected one, press Refresh to actualize the view.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
271 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
272 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
273 / 592
274 / 592
Fig. 181. Loopback CABLE
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
WARNING:
loopbacks on disabled tributaries are not applied (even if no messages are displayed when the command is sent)
N.B.
For the loopbacks relevant to Ch. 0 and Ch.1 all the switches must be forced/lockout to the related Channel; for the Tributaries loopbacks must only be forced to the radio switch to Channel 0 or lockout to Channel 1.
To activate a loopback: [1] Select the suitable loopback to be activated by clicking on the relevant object in the Resource Tree Area or by selecting the relevant row in the Resource List Area. The screen in Fig. 182. below will appear. (In this screen has been selected the loopback on tributary E1, Near End).
[2]
Fig. 182. Loopback activation [3] [4] [5] Select Active in the Activation field. Click on Apply. The Loopback is now ACTIVE (in the row in the Resource List Area the Activation field of the relevant loopback will change from Not Active to Active). when the Loopback commands start, the Craft Terminal is not frozen. Before to set another command, it is recommended to wait 120 to 160 seconds minimum.
WARNING:
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
275 / 592
[2]
Fig. 183. Loopback removing [3] [4] [5] Select Not Active in the Activation field. Click on Apply. The Loopback is now DEACTIVATED (in the row in the Resource List Area the Activation field of the relevant loopback will change from Active to Not Active). When the Loopback commands start the Craft Terminal is not frozen. Before to set another command is recommended to wait 10 to 25 seconds.
WARNING:
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
276 / 592
211 DIAGNOSIS
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Alarms Log Browsing Remote Inventory Abnormal Condition List Summary Block Diagram View Current Configuration view
on page 278 on page 279 on page 282 on page 284 on page 285 on page 288
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
277 / 592
211.1 Alarms
This item menu allows navigation to the external tool: Alarm Surveillance. The Alarm Surveillance application is dedicated to receive, store, display and manage, in real time, the alarms raised by different sources (current alarms). This facilitates the overall alarm surveillance and improves the reaction time of the network operators in case of anomalies in the network. It also provides the possibility to archive and retrieve the alarms (historical alarms), allowing postanalysis of anomalies in the network. Taking into account the number of alarms that are usually emitted in a network, the Alarm Surveillance offers the operator a systematic approach for the alarm visualization. 211.1.1 Counter Summary This is a main window (Fig. 184. below) used to display statistics on alarms. It shows alarm counters, according to severity levels or statuses of the alarms (critical, major, minor, warning, indeterminate, cleared, acknowledged, incoming). In the counter summary, alarms may be grouped according to filtering criteria in several sublists. For each sublist, each of the counters may be shown or not.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
211.1.2 Alarm Sublist The sublist is a basic working window (Fig. 185. on page 279 ). It regroups alarms according to filtering criteria defined by the operator, allowing work on a limited subset of alarms. The sublist can also be sorted according to criteria defined by the operator. It makes the management of current alarms easier, and allows information classification before a possible export to a file or a printer.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
278 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 185. Alarm Sublist Window For additional information, refer to the AS Operators Handbook (REF.[H] on page 571 of this manual). N.B. The list of alarms displayed by AS (both current and historical) is not easy to read and understand, mainly due to the way in which units and functional entities are indicated in the Friendly Name.
Fig. 186. Log Browsing Sub Menu The proposed options are: select the Alarm Log option to access the Alarm Log file (N.B.) The Alarm Log windows opens, permitting to analyze all the alarms stored in the NE. See para.211.2.1 on page 280 select the Event Log option to access the Event Log file (N.B.) The Event Log windows opens, permitting to analyze all the events stored in the NE. See para.211.2.1 on page 280 select the Software Trace Log option: see para.211.2.2 on page 281 The event and alarm store in the Event Log and Alarm Log can be inhibited or allowed by the Log Switch function (see para.23.7 on page 218 )
N.B.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
279 / 592
211.2.1 Alarm and Event Log By selection of Alarm Log or Event Log item, the specific Event Log Browsing Application will be started. This application is integrated function of JEMLUSM Core. This tool collects and shows the alarm log items (Fig. 187. below) and the event log items (Fig. 188. below). Selecting Set Filter menu item of main menu bar, it is possible to define a filter that can be applied to search of item.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 188. Event Log Display For additional information, refer to the ELB Operators Handbook (REF.[I] on page 571 of this manual).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
280 / 592
N.B.
The use of the Software Trace Log option is reserved to the AlcatelLucent technicians.
Selecting the Software Trace Log custom item of menu displayed in the Fig. 186. on page 279 , the application will try to download the trace log file from NE, showing a temporary information box:
Fig. 189. Transfer Information Box If successfully, the file content will be displayed in a new window (Fig. 190. below), from which it is possible to save or print the file.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
281 / 592
Format identifier field gives information about the structure and length of the inventory data block. The chosen identifier format is 22 (this field is not visualized to the operator). The checksum is not visualized to the operator. The Remote Inventory data is provided for the following equipment components: Tab. 62. Remote Inventory mnemonic field UNIT TYPE IDU Main Unit IDU Extension Unit 4xGigabit Ethernet plugin PDH Tributary optional plugsin Audio channels, Service Channel plugin ODU unit MNEMONIC M486032 E486032 P4DATASW P16E1DS1 PACSC ODU32E
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
282 / 592
Selecting the Remote Inventory item of Diagnosis menu, a summary screen will be displayed. This screen is a readonly screen, which shows the remote inventory for all configured equipment. If it is not possible to read the Remote Inventory information, a Card Fail alarm is declared.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
283 / 592
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
284 / 592
The Summary Block Diagram View of the Diagnosis menu displays a global logical view (strictly related to the physical implementation) highlighting a synthesis of all the alarms and statuses present in the system (ODU+IDU). It can also run by the Summary Block Diagram view shortcut of the Main tool bar (see Fig. 88. on page 183). This window also shows a logical view of the signal flowing through the functional block and switches. Line (and arrow) trace changes in compliance with the current switch status. By clicking on the objects of the drawing shown in the figure the operator can navigate to the specific view to perform maintenance operation (for example specific alarm details, equipment details, manual switches, loopback (L), performance monitoring (P). The Summary Block Diagram View depends on the configuration. 1+0 with or without the Ethernet ports 1+1 HSB with or without the Ethernet ports 1+1 FD with or without the Ethernet ports
Some examples are shown in Fig. 193. to Fig. 196. on pages 286 to 287 In detail, it is possible to: navigate from Alarm indicator to related Alarm Synthesis; navigate from External Point indicator to External Point view; navigate from Switch indicator to related Protection Scheme view; navigate from Loopback indicator to specific Loopback view; for example, by clicking on (L) indicator of main board (Ch#1) the operator can navigate to loopback view for PDH tributaries; navigate from Performance indicator to specific Performance view; for example, by clicking on (P) indicator (line side) the operator can navigate to Current Data view; navigate from ODU box to the radio view with automatic selection of the related channel.
By pressing the Refresh button the refresh of the screen takes place (active loopback and performance and position of the switch). N.B. N.B. Loopback indicator: yellow letter L means active loop. Performance indicator: yellow letter P means active performance. In the 1+1 configuration the current position of the switches is also shown.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
285 / 592
Fig. 193. Summary Block Diagram View example: 1+0 16E1 without Ethernet ports
Fig. 194. Summary Block Diagram View example: 1+1 HSB 16E1 with Ethernet ports
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
286 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 195. Summary Block Diagram View example: 1+1 HSB 16E1ETH with Audio/User Service Channel PlugIn (Lockout)
Fig. 196. Summary Block Diagram View example: 1+1 FD 32E1 with Audio/User Service Channel PlugIn USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
287 / 592
Fig. 197. Current Configuration view screen By File Save As, screen content can be saved as text file
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
288 / 592
This chapter describes the functions to provide Performance Monitoring management. It explains the procedures that the operator must perform in order to activate a PM process.
PROPR. FRAMING
FEC ENCODE
MODEM RF
MODEM RF
FEC DECODE
PROPR. FRAMING
Radio Hop (before the switch) Radio Link (after the switch)
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
289 / 592
Fig. 199. Performance View The performance reports can be of 2 different types: N.B. 15 minutes 24 hours The 15 min Performance Monitoring data are stored in the History Data report only if errors have been occurred. The 24 h Performance Monitoring data are always stored in the History Data report.
Considering one section (see Fig. 198. on page 289), one current register is for 15 min report and one for 24 h report; 96 history data can be stored for 15 min report and 8 history data for 24 h report. The counters supported are the following: N.B. Errored Seconds Severely Errored Seconds (N.B.) Background Block Error Unavailable Seconds According to ITUT G.826 a second is declared Severely Errored Second if it is a second period with more than 30 % of errored blocks or at least one defect.
The following description explains the functions to provide the PM process with a granularity period of 15 min. The same functions are provided for 24h PM process. The PM are of HOP or LINK type. The current report can be seen (and configured) and the history PM log can be seen.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
290 / 592
With reference to Fig. 200. below, to see (and configure) the current report:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
[1]
click on HOP channel (0 or 1) (in 1+0 configuration channel 1 only) to see the HOP report or click on LINK to see the LINK report click on the desired granularity (15 m or 24 h) click on CD (Current Data).
[2] [3]
With reference to Fig. 200. on page 291 to see an history log: [1] click on HOP channel (0 or 1) (in 1+0 configuration channel 1 only) to see the HOP report or click on LINK to see the LINK report click on the desired granularity (15 m or 24 h) click on the desired HD (History Data).
[2] [3]
To each PM can be associated a threshold table. To associate a threshold table click on HOP or LINK in the Resource Tree Area in Fig. 200.
Fig. 200. Threshold table association screen In the Counter Thresholds field select the threshold to be associated and click on Apply. To associate an Alarm Profile click on the selection box. The Alarm Severity profile screen opens. Select one of the Profiles available. Click on Apply. Click on Apply on the 15min&24h Tab panel.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
291 / 592
212.3.1 CD parameters The fields displayed in the upper part of Fig. 201. on page 292 allow the operator to check and manage the parameter of the current data collection. Suspect interval shows whether the current data are suspect or not. Elapsed Time field (readonly) displays the elapsed time in the current interval of monitoring. End Period: display time of the PM in the graphical description and in the tabular description in the upper part of the screen. By pressing the Refresh button this time changes. Max Interval supp.: max. number of intervals (reports) which can be suppressed in the History because they dont have errors. Num. Interval supp.: number of intervals (reports) suppressed in the History because they dont have errors. An interval is defined as suspect if at least one of the following conditions occurs in the collection period: the elapsed time deviates more than 10 seconds of the nominal time loss of the PM data in the equipment performance counters have been reset during the interval.
N.B.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
292 / 592
212.3.2 CD Counters
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The fields and buttons displayed in the lower part of Fig. 201. on page 292 (Counters Area) allow the management of performance events. In the left part of Counters Area, there is a graphical description of the event counter value: N.B. BBE (Errored block) ES (Errored second) SES (Severely Errored Second) UAS (Unavailable second) These values refer to the last refresh performed by pressing the Refresh button.
In the right part of Fig. 201. on page 292, there are button choice to perform action on the current data collection: Reset button resets the data collection and related counters. Start button starts the counters for the data collection, when the CD has been stopped. Refresh button makes a refresh of the counters. Stop button stops the counters for the data collection, when the CD has been started.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
293 / 592
Fig. 202. History Data The table columns hold the value of following parameters: End Period: End period of the relevant report Elapsed time: elapsed time in the related interval Suspect interval: this field describes whether the History Data is suspect or not. Counters: the last columns hold the counters value (BBE, ES, SES, UAS).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
294 / 592
This section describes how to see or change or create the threshold tables assigned to PM counters. There are threshold tables for the HOP and for the LINK. There are two default tables: threshold 1 and 2. To view the available threshold for PM process, the operator must select the Thresholds Tables node tree in the Resource Tree Area of the Performance View. N.B. For the association of the threshold tables to the PM refer to para. 212.5.3 Threshold table association.
Fig. 203. Threshold table Click on the threshold in the Resource Tree Area in the Resource List Area: the threshold screen will appear. In the upper part of the screen, the Name field displays the name assigned to the threshold table. In the lower part of the screen, low and high threshold for each counter is shown. To change them, the operator must edit the new values in the table fields and click on the Apply button.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
295 / 592
Fig. 204. Thresholds Table creation Click on Threshold Tables HOP (or LINK) node tree in the Resource Tree Area of the Performance view. The Threshold Data Creation screen will appear. In the upper part write the name of the new table. In the lower part write the values for the Low and High thresholds. To create the new table click on Create.
212.5.3 Threshold table association To each PM can be associated a Threshold Table. To associate a Threshold Table click on HOPChannel#0 (or Channel#1) or on LINK in the Resource Tree Area. The 15min&24h tab panel will appear. In the Counter Thresholds field select the threshold to be associated and click on Apply. To associate an Alarm Profile click on the selection box. The Alarm Severity profile screen opens. Select one of the Profiles available. Click on Apply. Click on Apply on the 15min&24h Tab panel.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
296 / 592
213 SW DOWNLOAD
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 205. Server access configuration screen User Id and Password are the login information to access the FTP server. In the Address field write the IP address of the FTP server. In the Port field write the port to be used and in the Root Directory field write the directory into which the software has been downloaded. By clicking on the Use System Default button a screen will appear showing the default configuration. The CT is the default FTP server with the following parameters: N.B. User Id: ftp Password: ftp Address: IP address of the F interface or IP address of the Ethernet interface, if present. Port: 15,000 the System Default can be changed by writing different values in the fields and then by clicking on button OK.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
297 / 592
The Forced check box can be used to force download (i.e. the complete description file is downloaded to the NE). If the Forced download is not selected, the system shall first proceed to compare the software to be downloaded with the software present in the NE. Then only the differences are downloaded.
Fig. 206. Init Software Download screen Recommended operation: Before to start the software download it is recommended to disable the ATPC operation (if it has been enabled) and to set in RTPC mode the max. Tx power.
When the SW download starts a screen, showing the in progress operation of the download, appears. Download is aborted when the Abort button is pressed. WARNING: The download time from the CT to the NE flash is 2530 min. approx. At 50% of this time starts the download to the first ODU, which lasts 1520 min. approx. At the end of this time interval starts the download of the second ODU, if present, which lasts 1520 min.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
298 / 592
213.3 SW Status
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
This menu allows to display the information of the software installed in the NE. The following information is displayed: Name: software name Version: software version Operational state: enabled or disabled Current status: committed or standby. The committed status refers to the software currently in use.
By clicking on the Software Units Status button the screen of Fig. 207. below opens, giving additional information on the software package.
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
299 / 592
The following information is displayed on the screen: EC: software on the Equipment Controller OC_R: software on the ODU Controller (Radio) (The total download time of the ODU software is 17 to 20 min approx. with some SES after 15 seconds from the activation) (Note 1) the other labels give the FPGA firmware version (Note 1) during the download of the ODU and FPGA software arises the alarm Firmware Download On Going. This alarm disappears when the download is over. The download lasts 2 minutes for every FPGA starting from the activation of the alarm.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Note 1:
Fig. 208. SW Unit Status screen The Flash card, which stores the NE software, contains 2 banks. The 2 banks can store 2 different software versions. One bank will be committed (active) and the other bank will be standby. N.B. The second bank will appear when a new software package has been downloaded the first time.
During download, necessary to update the software version, the download file is automatically stored in the standby bank. To activate the new version first check the operational status of the standby bank. If the status is enabled (this means that download took place without errors) select Activation or Forced Activation in the Software Management Action field and click on the Apply Action button. By selecting Forced Activation the bank to be activated is forced to restart. By selecting Activation the bank to be activated restarts only if the content of the two banks differ. 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
300 / 592
214.1 Introduction
This function allows the backup and/or restore of the MIB and is carried out at two levels: the first is available at NE loggedin level, and allows operations depicted in Fig. 209. below: NE XXX Flash Card
MIB
MIB BackUp
MIB Restore
MIB delete
ECT
ECT
Fig. 209. Allowed MIB management tasks at NE loggedin level From operative point of view, this management is described in para.28.3 on page 253. the second is available at Network Element Synthesis level (independently of whether or not the NE is logged in), and allows operations shown in Fig. 210. below (it depicts save/load using floppydisk, but the operation can be done through any available read/write computer resource):
Save to disk
ECT
ECT
Fig. 210. Allowed MIB management tasks at Network Element Synthesis level From operative point of view, this management and whole applicative examples are described in the following paragraphs. USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
301 / 592
Fig. 211. Launch of MIB save to disk 2) The following screen appears: in field Look in (1) the PC directory where MIBs are stored is shown click on Find Now button (2) 1 2
Fig. 212. MIB save to disk phase 1 3) The following screen appears: a table showing the MIBs stored in the PC directory is shown
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
302 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
select the MIB you want to save (3) click on OK (4) the usual window to choose a save target directory appears (5); select it and start the save at save end, a confirmation message is shown (6) indicating also the name of the saved folder; see N.B. on next page.
3 4
6 5 Fig. 213. MIB save to disk phase 2 N.B. The saved MIB folder name acronym does not correspond to the name of the MIB that you have selected to be saved. In order to know such a correspondence open the saved folder: in the userlbl.txt you can find such name.
Fig. 214. Correspondence between MIB saved folder and MIB saved name
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
303 / 592
214.2.3 MIB load from disk This operation, carried out by ECT through the Network Element Synthesis screen, allows to load a MIB previously saved on a floppy disk into ECTs MIB area. N.B. This example depicts the Load from disk by using the floppydisk, but the operation can be done through any available read/write computer resource. 1) Launch the task as follows:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
304 / 592
2)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
After launch of MIB load from disk, proceed as follows: in the screen that opens, click on Browse button (1) select the device from which carry out the load operation (2) and open it (3) in the opened directory (4) , select the MIB folder to load (5) , then click Open (6)
Fig. 216. MIB load from disk phase 1 3) ... procedure continues
USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 3DB 16142 EAAA Ed.02
305 / 592
N.B.
10
214.2.4 MIB restore from ECT This operation, carried out by ECT with the NE loggedin, allows to restore the MIB from ECT to NE (see MIB restore in para. 28.3.2 on page 255). a) END OF SECTION
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL
306 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
in the screen that opens, click on Find Now button (7) in the subsequent screen, select the MIB (N.B.) that must be loaded (8), then click on OK button (9) at load end, a confirmation message is shown (10) .
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Please read para.12.6.1 on page 59 for an introduction to the procedures of this section.
SECTION CONTENT Chapter 31 SWP installation in PC environment This chapter details all phases necessary to install for the first time the SWP this manual refers to, in the PC environment. Chapter 32 LineUp and Commissioning This chapter details all phases necessary for the equipment lineup and commissioning.
PAGE
309
329
307 / 592
308 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
This chapter details all phases necessary to install for the first time the SWP this manual refers to, in the PC environment. N.B. Before starting this installation procedure, it is suggested to give a look to para.12.6 on page 58. Procedures described in this chapter are carried out with the PC disconnected from the NE.
N.B.
31.1 Requirements
31.1.1 PC characteristics For this SWP version, correct ECT installation requires a PC with the requirements hereafter described: 1) HW Configuration CPU: Pentium III 850 MHz RAM: 512 Mbytes Hard Disk space: 4 Gbytes Display Resolution: 1024x768 pixel CDROM Drive: 24X Primary Interface: Serial Port RS232C 9.6 to 57.6 Kbits/sec. 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) RS232 serial port is mandatory, 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 employ the USB TO RS232 ADAPTER , ordering it to AlcatelLucent (P/N 1AF11294AA**).
2)
Windows Versions Windows 2000 till SP4 Windows XP (Professional Edition only) till SP2: It is mandatory deactivate the Firewall installed. Windows NT partially supported: CTK 3.3 and related Q3/SNMP addon deliveries can be run on Windows NT but you have to take in account some restrictions in Almap PC 6.5 and PC 7.0 components. They must be considered as Craft Terminal platform restrictions in Windows NT environment.
309 / 592
3)
Additional SW requirements Java Runtime Environment (JRE) version 1.4.212 or higher (the necessary version is included in the SWP CDROM) Browser: System default browser that correctly supports XHTML 1.1 and CSS 2.1 standards: Microsoft Internet Explorer 5.5 or higher Mozilla Firefox 1.5 or higher Netscape Communicator 6 or higher N.B. Opera browser is not supported in any version. It is mandatory to manually disable system and browser proxy configurations prior to use both TCO Suite SetUp 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 In users Windows system desktop folder, files with the following names must not be present: Default_211.qcml QCML_211.xsd QCML_211.xsl Through systems Display Properties, Settings tab, clicking on Advanced button, the Display DPI setting should be set to Normal Size (96 DPI);
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
31.1.2 Operator skills and privileges a) The operator shall be familiar with the use of personal computers in WINDOWSNT / WINDOWS 2000 / WINDOWS XP (Professional Edition only) environment, internally to which the Network Elements application software operates. 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 Plesiochronous Digital Hierarchy (PDH) (ITUT Recommendations). For the installation of SW packages, the Operators PC privilege and skill must be those of System Administrator. The Operator shall be familiar with the use of Alcatel 1320CT functionalities. If necessary, a good approach to the related matters is to read and understand the following sections of the 1320CT Basic Craft Terminal Operators Handbook (see Tab. 78. on page 571 ): section INTRODUCTION section GETTING STARTED
b)
c)
d)
310 / 592
The procedure and main phases to carry out depend on the ECT environment you want achieve: a) Only SNMP management of 9400AWY V2.1.1 through Ethernet interface (by CT and TCO Suite). In this case you must carry out the following main phases: 1) 1320CT Package Installation (installation of SWP components from the SWP CDROM): para.31.5 on page 314 Local copy in PC environment of the TCO Suite: para.31.6 on page 318 End of SW installation from SWP CDROM: para.31.7 on page 320 NE software downloading preparation: para.31.8 on page 321 CT initial configuration: para.31.9 on page 326 EML construction: para.31.10 on page 327
2)
3)
4)
5)
6)
b)
Only SNMP management of 9400AWY V2.1.1 through Ethernet interface (by CT and TCO Suite), as point a ) above, with the additional possibility of management through the NEs ECT serial port (by CT) In this case you must carry out the procedure described in Appendix C Additional SW installation operations for NE management through the NEs ECT serial port on page 517
c)
Management of SNMP 9400AWY V2.1.1 [as case a ) or b ) above] and of other SWPs for different NEs (e.g. AlcatelLucent 9600USY, 9600LSY) In this case, before doing anything, read carefully para.31.4 on page 312 Chapter 410 on page 497 describes how to to deinstall the Software Package from the PC.
N.B.
311 / 592
To make the comparison between the versions of the common SW components, please refer to the Product Release Notes (see para.57.2.2 on page 571 ) associated to the SWPs you want to install. In term of method to install: use CT installation Product Guided and select component depending of the rule before; install at first the SWP with the common SW components highest versions, and after the other SWPs leaving unselected the common SW components already installed. Please extend these considerations to the need of installing more than two different SWPs. Procedure example (referred to the two SWP cited above): 1) 2) 3) compare the PC characteristics and verify that your PC meets the highest requirements (as far as the SWP 9400AWY R.2.1 V2.1.1 is concerned, refer to para.31.1.1 on pages 309310 uninstall all AlcatelLucent products (the clean situation simplifies the following operations) carry out the installation of LLMAN from the SWP 9400AWY R.2.1 V2.1.1 CDROM as described in para.53.2 on page 519, because its version is higher than that of the SWP 9600LSY V2.0.4 install the SWP 9400AWY R.2.1 V2.1.1 , as described in para.31.5 on page 314, selecting all components, because its common SW components have versions higher than those of the SWP 9600LSY V2.0.4 complete the SWP 9400AWY R.2.1 V2.1.1 installation as described in steps 2 ) to 6 ) of point a ) on page 311 using the CT installation Product Guided, start the installation of the SWP 9600LSY V2.0.4, deselecting (see following Fig. 218. ) the components JRE V1.3 , Alcatel Lower Layers Manager V3.4.0 , CTK v3.2.0 and HOLCTKADDON v1.1.0, because already installed (with higher versions) by the SWP 9400AWY R.2.1 V2.1.1 installation complete the SWP 9600LSY V2.0.4 installation as described in relevant documentation.
4)
5) 6)
7)
312 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
common components
313 / 592
N.B.
Please read carefully para.31.3 on page 311, for the position of this step inside the whole installation procedure. Procedures described in the following are carried out with the PC disconnected from the NE.
N.B.
31.5.1 Important warnings N.B. Windows versions supported are just those listed in point 2 ) on page 309 (e.g. Windows XP Home Edition, Windows 95, 98, ME, etc. are not supported). System browser versions supported are just those listed in point 3 ) on page 310 (other versions are not supported). Warning about Windows XP till SP2 Professional Edition:
N.B.
N.B.
N.B.
WARNING:
N.B.
Note for Users having previously used SWP 9400AWY versions up to V2.0.3: This behavior takes place from V2.0.4: the 1320CT installation of this SWP does not include anymore the Q3CTKAddOn component. In particular, if LLMAN component is not installed because you want to manage AWY NEs only by Ethernet interface, also Q3CTKAddOn component has not to be installed (or has to be explicitly deinstalled if previously installed) in order to have a correct behavior on 1320CT usage. Obviously, as also applied to previous SW releases, it is mandatory to install LLMAN component in order to be able to manage AWY NEs by Serial F interface and in this case Q3CTKAddOn component can be installed to enable the possibility to manage also Q3 NEs with the same 1320CT installation. Notes for Users having previously used any SWP 9400AWY previous versions: When installing this SWP on a PC where are already installed the previous: SWP 2.0.3, 2.0.4 or 2.1.x versions, it is mandatory select all the components in the installation procedure any 1.0.x and 2.0.x versions, it is not necessary to deinstall them from PC.
N.B.
314 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
31.5 1320CT Package Installation (installation of SWP components from the SWP CDROM)
Step 1. Initial checks 1) Verify that the PC characteristics meet all HW and SW requirements specified in para.31.1.1 on page 309 Verify you do have the SWP CDROM P/N REF.[a] in Tab. 53. (page 141) WARNING : whenever you have already installed a previousversion SWP V2.1.1 including the TCO Suite, delete the existing shortcut to the Start_html icon as well as the TCOSuite folder (see Fig. 227. on page 320). Note: it is not necessary to delete shortcut to the Start_html icon relevant to previous SWP V2.0.x.
2) 3)
Step 2. Installation startup 1) 2) Insert the SWP CDROM in the PCs CDROM unit The TCO Suite startup begins. Please refer to para.22.2.3 for the procedure execution and the management of special conditions that could occur At the end of the TCO Suite startup, the CDROM TCO Suite Main Menu screen appears (Fig. 219. below); click on Advanced Settings button
3)
315 / 592
4)
Fig. 220. CDROM TCO Suite Advanced Settings screen 5) After a while, the SWP component selection screen appears (Fig. 221. ); leave all components selected (or click on Select All button), then click on Next button
316 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
After a while, the CDROM TCO Suite Advanced Settings screen appears (Fig. 220. ); click on 1320CT Package Installation button
6)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The installation process begins. After its completion (time depends on PC performance), the following screen appears; clicking on confirmation button (YES / S), the installation report is produced
Fig. 222. SWP component installation end, and installation report N.B. At any time, you can also check the components installed (Fig. 223. ) carrying out, in Windows environment: Start Settings Control Panel Add/Remove Programs
Fig. 223. Check of installed Alcatel SWP components 31.5.3 Next step You have now completed the installation of the SWP components. Leave the: SWP CDROM in the PCs CDROM unit, and the CDROM TCO Suite Advanced Settings screen open, and proceed with the Local copy in PC environment of the TCO Suite, para.31.6 on page 318. USER MANUAL INSTALLATION AND COMMISSIONING 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
317 / 592
This step is mandatory to have all TCO Suite functionalities (with exception of those related to the SWP installation in PC environment) available from the PC after the extraction of the SWP CDROM from the PCs CDROM unit. 31.6.1 Operations sequence 1) In the CDROM TCO Suite Advanced Settings screen (Fig. 220. on page 316) click on Local Copy of TCO Suite button Fig. 224. below: user is asked to choose the location where save must be done; such a location could be on the local PC or on a USB Key, Flash Memory Card, etc. Confirm or change it, and proceed N.B. As an example, Fig. 224. below shows the: TCOSuite.206 folder, that was created installing the SWP 9400AWY R.2.0.4 TCOSuite.217 folder, that was created installing the SWP 9400AWY R.2.1.0 It is not necessary to delete them, because the Local Copy of TCO Suite from this SWP 9400AWY R.2.1 V2.1.1 CDROM will create another folder (see Fig. 227. on page 320). WARNING: If you delete them, you will loose the TCO functionalities associated respectively to the SWP 9400AWY R.2.0.4 and SWP 9400AWY R.2.1.0
2)
318 / 592
3)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Where the user selects to put the TCO Suite, will be created a TCOSuite directory with the content of the same TCO Suite located on CDROM. The copy will proceed with a clear show of the progress (Fig. 225. below).
Fig. 225. Local Copy of TCO Suite progress and end N.B. The user can also cancel the copy operation and all the files copied will be removed (Fig. 226. below).
Fig. 226. Copy cancelled 4) Since Java is not systemspecific, neither shortcut to local TCO Suite Start.html page, nor Microsoft Windows Start menu entry for TCO Suite can be created automatically. User should provide to create them as follows (see following Fig. 227. ): open the TCO Suite folder [from the location established in previous step 2 ) ], and create a shortcut to the Start.html icon on the PCs desktop. N.B. Following the example of Fig. 224. on page 318, in order to create the shortcut, pay attention to open the new folder that has been created now, and to give it a mnemonic name different from the shortcut associated to the preexisting SWP.
319 / 592
OPEN
PC DESKTOP
LINK
Fig. 227. Shortcut to the TCO Suite Start icon 31.6.2 Next step You have now completed the Local copy in PC environment of the TCO Suite. Leave the: SWP CDROM in the PCs CDROM unit, and the CDROM TCO Suite Advanced Settings screen open, and proceed to the next installation step (para.31.3 on page 311), according to the case a ) or b ) you want to achieve.
320 / 592
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.
This description is retrieved from 1320CT Basic Operators Handbook and is repeated here for ease of operation.
This phase must be manually carried out by the Operator and has the scope of making the new equipment software package available for its downloading toward the NEs equipment controller and the peripheral units (such a downloading is explained in Chapter 48 on page 485). This operation is independent from the NE management state and must be executed with the following procedure: 1) Launch the CT by: TCO Suite Main Menu Operational & Maintenance or: Start 1320CT For details, refer to point e ) on page 174 On NES (Network Element Synthesis) screen that opens, from the Supervision pull down menu select the File Administration and then the Software Administration option, as shown in Fig. 228. herebelow.
2)
Fig. 228. Selecting SWP Administration 3) In the screen that opens (Fig. 229. below) click on Install
321 / 592
4)
Alcatel / JUSMw V.x.x.x / ect / swdw / <equipment name> / <version> / <descriptor file> (*) (*) the 9400AWY equipment name is R94AWY ; the version is that you want; the descriptor file has always the extension .DSC. The NE software package can also be selected from the CDROM used for the installation of the NE software. In this case, after inserting the CDROM in the driver, choose the following: ect / swdw / <equipment name> / <version> / <descriptor file> in case you have still installed in your PC one or more previous AlcatelLucent SWP, in step [2] of Fig. 230. on page 323, you must be sure to open the JUSM folder relevant to the SWP you have installed now. In such an example: JUSMw2.2.16 is associated to SWP 9400AWY 2.0.4 JUSMw2.3.11 is associated to SWP 9400AWY 2.1.0 JUSMw2.4.7 is associated to SWP 9400AWY 2.1.1 [you can check the JUSM version comparing it with the report produced at installation end (see Fig. 222. on page 317 )].
N.B.
WARNING:
In any case, whenever the version to be selected in step [6] of Fig. 230. on page 323 is not that you wanted, you can go backward to step [2] to explore the correct JUSM folder.
322 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
In the screen that opens (Fig. 230. on page 323 is an example) select the directory where the NE software package is installed:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
CONTINUES Fig. 230. Directory selection for the descriptor file .DSC
323 / 592
End of Fig. 230. Directory selection for the descriptor file .DSC
324 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
5)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
On last screen (containing the .DSC file), click on Open to activate the installation of the selected.DSC file. At the end of the process, a confirmation message is displayed:
6)
At this point the NE Software Package is installed and available to be downloaded on the Network Elements (as described in chapter 48 on page 485). Such availability can be verified (as shown in Fig. 231. herebelow) operating in the Network Element Synthesis screen (Fig. 228. on page 321), selecting, from the Supervision pull down menu, the File Administration and then the Software Administration option.
Fig. 231. SWP available for download to NEs Now proceed with CT initial configuration, para.31.9 on page 326.
325 / 592
31.9.1 Craft Terminal configuration This procedure is necessary to configure the PC in order to manage the Network Elements and includes the following types of configuration: PC hostname CT configuration Communication Protocol (TCP/IP): TCP/IP without a network card TCP/IP with a network card Switching between the two configurations
In order to setup these configurations, refer to: 1320CT Basic Craft Terminal Operators Handbook , chapter SOFTWARE INSTALLATION, paragraph Craft Terminal Configuration
31.9.2 Craft Terminal local connection to the NE The CT can be locally connected to the NE preferably through the Ethernet Network Port, or through the Serial Port. Only one connection can be active at a time. Please refer to para.22.4.2 on page 171 to change from Ethernet Network Port to Serial port or viceversa. N.B. this setting operation is not necessary if you login the local NE through the Operational & Maintenance button of the TCO Suite Main Menu.
326 / 592
After having activated the 1320CT application (by TCO Suite Main Menu Operational & Maintenance or Start 1320CT) the Network Element Synthesis screen appears (example in Fig. 228. on page 321). This NE map specifies the NEs that can be reached by the ECT. This map must be built by the Operator. N.B. This map is empty in the case of first installation of ECT on a PC. The map content is usually not affected when you install a new SWP or upgrade the SWPreleaseversion (e.g. from V2.1.x to V2.1.y).
The set of procedures necessary to configure the ECT in order to manage the Network Elements (which include the management of Maps, Submaps and Network Elements, like creation, deletion, saving, opening, etc) is named EML construction . In order to carry out these procedures, refer to the: 1320CT Basic Craft Terminal Rel.3.x Operators Handbook (see Tab. 78. on page 571) section EML CONSTRUCTION. An example of NE creation in the map is given in point g ) on page 176. end of SWP INSTALLATION IN PC ENVIRONMENT procedure
327 / 592
328 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
32.1 Introduction
32.1.1 General This chapter details all phases necessary for the equipment lineup and commissioning, providing the user with the information needed to connect, power on, and perform a minimum turnup of an equipment of the 9400AWY family running with the SWP 9400AWY R.2.1 V2.1.1 . It is assumed that the mechanical installation of the INDOOR and OUTDOOR units is completed and the antennas are installed and prepositioned. Moreover, the IF cable has been allocated but not connected to the IDU. Any information needed to complete the above mentioned operations are out of the scope of this chapter. For this purpose refer to the Installation Handbook. All the cables and measurement kits as described in the following (Tab. 63. on page 330) are supposed to be available. The AlcatelLucent Software package SWP 9400AWY R.2.1 V2.1.1 must have already been installed in the PC used as the Craft Terminal (CT) and the same software already downloaded in the equipment. 32.1.2 Conventions To simplify the description of actions, the following symbols are in use: Symbol used . n CT Meaning Manual action Check/Verify On Craft terminal Select Select a Menu item Sub Menu item
The commissioning operations described in this document are for a link between a station A and a station B. If the network includes supervision, station A is the one located between the supervisory station and station B (see figure below). Installation and commissioning begin at station A. STATION A ODU STATION B ODU
IDU
IDU
Network
329 / 592
32.1.3 Summary of the commissioning phases Before proceeding with this operation ensure that you have the equipment and accessories required for that purpose. All these materials should be present in the service bag. The commissioning procedure is summarized as follows: Turn up (phase 1) Station A, roughly point the antenna towards station B Commission station A (phase 1) Commission station B (phase 1) Station B, fine align the antenna towards station A Station A, fine align the antenna towards station B
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Site acceptance tests (phase 2) Station A, carry out all the commissioning checks and tests Report the results in the TRS Station B, carry out all the commissioning checks and tests Report the results in the TRS
Tab. 63. Test and commissioning instruments INSTRUMENT QTY CHARACTERISTICS The PC must have been already configured as Craft Terminal for 9400AWY Rel.2.1.1. If necessary, please refer to the Chapter 31 SWP installation in PC environment on page 309 for any related information and installation instructions you may need. See System configuration See System configuration Optional See System configuration Voltmeter AC and DC Loop tester see para.32.10 on page 405 Test Result Sheet and Site Acceptance Test protocol, available as separate document (REF.[D] on page 570)
PDH Analyzer Pattern Generator V.11 G.703 Data Analyzer Ethernet Data Analyzer Multimeter Light service kit cable for ODU Rx power monitoring TRS and SAT
1 1 1 1 1
32.1.4 SafetyEMCEMFESD norms and Cautions to avoid equipment damage Read carefully SafetyEMCEMFESD norms in Appendix A on page 501, and Cautions to avoid equipment damage in para.11.6 on page 36.
330 / 592
Following sets of drawings show the equipment interconnections at IDU level in the 1+0 (N.B.) and 1+1 configurations, according to the IDU equipment provisioning specified in Tab. 6. on page 68 : IDU configuration 16E1 without plugins 16E1 + Audio and User Service Channel plugin 16E1 + Enhanced Ethernet plugin 16E1 + Enhanced Ethernet plugin + Audio and User Service Channel plugin 32E1 without plugins 32E1 + Audio and User Service Channel plugin drawings on page 332 333 334 335 336 337
N.B.
As far as the 1+0 configurations are concerned, two interconnection drawings are depicted: one without protection boxes (the standard and cheapest solution) the other with the protection box(es), which allows the easy expansion to the corresponding 1+1 configuration just installing and cabling the IDU Extension unit without altering the User line connections already existing on the IDU Main unit.
For the layouts at ODU level, refer to para.14.4 on page 101 . For additional and more detailed information, please refer to the Installation Handbook, in particular for: P/Ns of cables to use exact shelves layout for cable route optimization connector pinout at User line side, in the case the protection boxes are not used. When they are used, you can find the User line side connector pinout in this manual: E1 Protection box Services Protection box from page 79 from page 84
331 / 592
32.2.1 Configurations with 16E1 WARNING: for 1+0 configurations, read carefully N.B. on page 331 1+0 CONFIGURATION WITHOUT PROTECTION BOXES E1 lineside user interface cable Alarms & Housekeepings & NMS interface cable Main
PS ODU CH1 All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Main
PS
ODU CH1
Main
PS
ODU CH1
ODU CH0
PS
Extension Fig. 233. Equipment interconnections for configurations with 16E1 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL INSTALLATION AND COMMISSIONING
332 / 592
32.2.2 Configurations with 16E1 + Audio and User Service Channel plugin
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
WARNING: for 1+0 configurations, read carefully N.B. on page 331 1+0 CONFIGURATION WITHOUT PROTECTION BOXES Alarms & Housekeepings & NMS interface cable E1 interface cable Audio & Service channels interface cable ODU CH1 Main
PS
1+0 CONFIGURATION WITH PROTECTION BOXES Alarms & Housekeepings & NMS & E1 lineside user interface Audio & Service channels lineside connectors user interface connectors
Main
PS
ODU CH1
1+1 CONFIGURATION Alarms & Housekeepings & NMS & Audio & Service channels lineside user interface connectors
Main
PS
ODU CH1
ODU CH0
PS
Extension Fig. 234. Equipment interconnections for configurations with 16E1 + Audio and User Service Channel plugin USER MANUAL 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 INSTALLATION AND COMMISSIONING 3DB 16142 EAAA Ed.02
333 / 592
32.2.3 Configurations with 16E1 + Enhanced Ethernet plugin WARNING: for 1+0 configurations, read carefully N.B. on page 331 1+0 CONFIGURATION WITHOUT PROTECTION BOXES Alarms & Housekeepings & NMS interface cable E1 interface cable 4 x Ethernet cables ODU CH1 Main
PS All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
1+0 CONFIGURATION WITH E1 PROTECTION BOX E1 lineside user interface connectors 4 x Ethernet cables
Main
PS
1+1 CONFIGURATION E1 lineside user interface connectors 4 x Ethernet cables Alarms & Housekeepings & NMS interface cable
Main
PS
ODU CH1
ODU CH0
PS
Extension Fig. 235. Equipment interconnections for configurations with 16E1 + Enhanced Ethernet plugin
334 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
32.2.4 Configurations with 16E1 + Enhanced Ethernet plugin + Audio and User Service Channel plugin WARNING: for 1+0 configurations, read carefully N.B. on page 331 1+0 CONFIGURATION WITHOUT PROTECTION BOXES Alarms & Housekeepings & NMS interface cable E1 interface cable Audio & Service channels interface cable 4 x Ethernet cables ODU CH1
PS
Main
1+0 CONFIGURATION WITH PROTECTION BOXES E1 lineside user interface Alarms & Housekeepings & NMS & connectors 4 x Ethernet Audio & Service channels lineside cables user interface connectors
Main
PS
ODU CH1
1+1 CONFIGURATION Alarms & Housekeepings & NMS & Audio & Service channels lineside 4 x Ethernet user interface connectors cables
Main
PS
ODU CH1
ODU CH0
PS
Extension Fig. 236. Equipment interconnections for configurations with 16E1 + Enhanced Ethernet plugin + Audio and User Service Channel plugin USER MANUAL INSTALLATION AND COMMISSIONING 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
335 / 592
32.2.5 Configurations with 32E1 WARNING: for 1+0 configurations, read carefully N.B. on page 331 1+0 CONFIGURATION WITHOUT PROTECTION BOXES E1 interface cables Alarms & Housekeepings & NMS interface cable Main
PS ODU CH1 All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Main
PS
ODU CH1
Main
PS
ODU CH1
ODU CH0
PS
Extension
336 / 592
32.2.6 Configurations with 32E1 + Audio and User Service Channel plugin
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
WARNING: for 1+0 configurations, read carefully N.B. on page 331 1+0 CONFIGURATION WITHOUT PROTECTION BOXES Alarms & Housekeepings & NMS interface cable E1 interface cables Audio & Service channels interface cable Main
ODU CH1
PS
1+0 CONFIGURATION WITH PROTECTION BOXES Alarms & Housekeepings & NMS & E1 lineside user interface Audio & Service channels lineside connectors user interface connectors
Main
PS
ODU CH1
1+1 CONFIGURATION E1 lineside user interface connectors Alarms & Housekeepings & NMS & Audio & Service channels lineside user interface connectors
Main
PS
ODU CH1
ODU CH0
PS
Extension Fig. 238. Equipment interconnections for configurations with 32E1 + Audio and User Service Channel plugin USER MANUAL INSTALLATION AND COMMISSIONING 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
337 / 592
Where necessary, switch OFF the power supply before disconnecting the earth connection, Do not connect instruments directly to the IDU/ODU cable connector since the connector carries 48v DC used to supply the ODU. Do not connect the IF cable between IDU and ODU while the IDU is powered up.
ALL THESE OPERATIONS ARE PERFORMED WITH THE POWER OFF. n The antenna of station A is pointed towards station B the best as possible (use compass if necessary). The hardware configuration of the equipment corresponds to the expected one. Make visual inspection for units installation and cabling: The IDU(s) subrack allocation according to the station layout The IDU(s) subrack and units ground connections The power supply voltage is present (48, 60 V DC) with the correct polarity at the IDU power supply input In 1+1 configuration, check the connections between main and extension IDU(s) Tributaries and service channel access are cabled on the station DDF The IDUODU cables ground kit connections The ODU(s) ground connections (In the case of a nonintegrated antenna, the antenna and the ODU(s) must be ground connected) The IDU(s) / ODU(s) cables are connected to IDU(s) and ODU(s) The ODU(s) cables connectors waterproofing
n n
338 / 592
This operation has the following scopes: verify the SWP present both in CT and NE make the Central Frequency and Shifter values of ODUs be acquired by IDU (so that they are retained in the NEs data base).
Proceed as follows: a) b) Switch on IDU (MAIN and, if equipped, EXTENSION) Start the Craft Terminal and carry out the NE login Proceed as follows (for details refer to para.22.5.2 on page 173): 1) Connect the crossconnect Ethernet cable between the Ethernet port of the PC and the Ethernet interface on the Main IDU (see Fig. 76. on page 170). In alternative connect the RS232 cable between the serial port of the PC and the F interface (ECT) on the Main IDU (see Fig. 76. on page 170). Power on the PC and wait for its startup Startup the Craft Terminal and wait for the Network Element Synthesis screen Give the NE icon a mnemonic name (e.g. STAZ A as in Fig. 83. on page 177) Start supervision on the local Network Element Login the local Network Element, using the Administrator UserName & Password Wait for the main Equipment view (CT) to appear (for details, refer to para.22.6 on page 181)
2) 3) 4) 5) 6) 7) c)
Check that CT and NE versions are both V2.1.1 (for details, refer to para.12.6.3 on page 62). If NOT, proceed as specified in Chapter 49 on page 495. Start the Quick Configuration Procedure clicking on Main Tool Bars icon Quick Configuration (see Fig. 88. on page 183), or select Configuration Quick Configuration from the Menu bar. The window in Fig. 245. on page 347 will appear. This window is the first step of the Interactive Quick Configuration Procedure. Clicking repeatedly on Next button (without any other actions), reach Step C on page 353 (Channel configuration) and confirm the Frequency Values fields. Then, clicking repeatedly on Next buttons (without any other actions), reach Step L on page 368 and click on Finish button. In this way the Frequency Values fields are saved in the NEs data base, and will be available even if the ODU(s) is/are disconnected.
d)
32.3.3 Switching off the IDU(s), and ODU(s) disconnection Proceed as follows: a) Close JUSM and stop Supervision on the NE (for details, refer to para.22.5.3 on page 180). Leave PC and CT ready for next operations Switch off IDU (MAIN and, if equipped, EXTENSION) Disconnect the IDU(s) / ODU(s) cables from IDU(s).
b) c)
339 / 592
32.3.4 Powering up the IDU(s) with ODU(s) disconnected N.B. Make sure that IDUODU cable is disconnected from the IDU(s) in order to verify via CT the System PTx Power and Frequency Tx settings as foreseen by Plant documentation before powering up the ODU(s). Since the IDU(s)ODU(s) connection is not established, when powering up the IDU(s), the ODU(s) will not be operating and then the IDU(s) will display the relative Alarms. . After switching on the wall circuit breakers, poweron the Main IDU then the Extension IDU if any via the front panel power supplies switches. The green ON LEDs on both IDUs come on.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
On the IDU Main, wait 1 minute for: n n n The green EOW LED is on. The red LDI LED is on. The red RDI LED is on.
Always on the IDU Main, wait another 1 minute for: n n The red MIN LED is on The red MAJ LED is on
WARNING: With a new Flash only LED ON is on. Finally perform a Lamp Test by pressing the LT pushbutton on IDU(s) in order to verify if the remaining LEDs are operational. 32.3.5 NE login a) b) Login again the local Network Element, using the Administrator UserName & Password. Wait for the main Equipment view (CT) to appear. Note: Since the ODU(s) cables are disconnected, relevant communication alarm is shown. Proceed as described in para.32.3.7 on page 343 N.B. This is the Quick Configuration (interactive). If you want to use another modality, please read para.32.3.6 on page 341, and proceed according to the configuration procedure you like.
c)
340 / 592
This procedure allows a full system configuration through a guided process, based on a reduced set of screens. The related windows will be displayed by a Wizard Tool according to a specific order. It is possible to create, save and recover configuration files having the .qcml extension. To manage configurations (and configuration files) the following options are available: [1] Online creation, modification and save of the NE configuration (interactive) This is done by Craft Terminal (e.g. by Quick Configuration shortcut icon), after having logging in the NE. For the execution of this procedure, refer to para.32.3.7 on page 343.
Quick Configuration shortcut icon [2] TCO Suite PreProvisioning Tool: offline creation, modification and save of a provisioning file (not interactive)
By this modality, you do not need to login any NE; its main steps are: a ) launch the application, b ) create and check the NE configuration, c ) save the configuration file ( format is configuration_name.qcml ). This file will be after used to configure the NE (after having logged it) with a simple load command. For the execution of this procedure, refer to para.32.3.8 on page 344. [3] TCO Suite SetUp Tool: online recover, modification and application of a provisioning file (not interactive)
By this modality, you access one NE, not using the Craft Terminal application, but the TCO Suite web server; its main steps are: a ) launch the application and the connection with the target NE, b ) recover a configuration file configuration_name.qcml previously created (e.g. through the TCO Suite PreProvisioning Tool), or get configuration data from the NE c ) check/modify the configuration, d ) apply the configuration to the target NE. For the execution of this procedure, refer to para.32.3.9 on page 345. WARNING: the execution of the TCO Suite SetUp Tool is denied to the Viewer operator profile N.B. In alternative, through the TCO Suites Alarms & Settings function (see para.22.3 on page 156), it is possible: to send a configuration_name.qcml configuration file to a NE (Configuration Setting, see para.22.3.3 on page 160) to get from a NE its own configuration_name.qcml configuration file (Get Configuration File , see para.22.3.5 on page 164) to get from a NE its own configuration text Report (Configuration Info , see para.22.3.4 on page 161).
341 / 592
32.3.6.1 Note on the use of the bottom buttons available in the screens The bottom buttons available in the screens depend on the configuration tool started, and are contextspecific, e.g.:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Back: by clicking on this button the procedure goes back to the previous step Next: by clicking on this button the procedure goes on the next step Finish or Apply to the NE : this button is active only in the last step. By clicking on this button the operator confirms the configuration and the new parameters are sent to the equipment Save As: by clicking on this button, the configuration can be saved as a configuration_name.qcml file (provide a mnemonic name) Save & Apply: by clicking on this button, two operations are carried out: Save: the configuration and the new parameters are temporarily saved on the system disc N.B.
and then: N.B. Apply: they are sent to the equipment the file is saved under the user home directory, inside the TCO SUITEs temporary file folder. For example, in Windows XP it is:
Example: D:\Documents and Settings\berenice\temp_tcosuite.217\1164279978890\temp.qcml Cancel: by clicking on this button, the procedure is cancelled Help: by clicking on this button the operator calls the helpon line WARNING: the Help button is operative in the CT environment only. It is not operative in the TCO SUITE environment.
342 / 592
This job can be done by Craft Terminal, after having logged in the NE. To start this application, click on Main Tool Bars icon Quick Configuration (see Fig. 88. on page 183), or select Configuration Quick Configuration from the Menu bar. The window in Fig. 245. on page 347 will appear. This window is the first step of the procedure. Proceed as specified in para.32.3.10 on page 346. N.B. With the Quick Configuration (interactive), the configurations parameters displayed in the various steps are taken from those actually stored in the NE data base. You can check them and modify (if necessary), then go to the following step. The last step is Step L on page 368. In such a step you can: click on Save As button: configuration data are saved in a configuration_name.qcml file (provide a mnemonic name) and / or click on Finish button: configuration data are stored in the NE data base.
343 / 592
To launch this application, click on the button PreProvisioning Tool of the TCO Suite Main Page (see Fig. 55. and Fig. 56. on page 149). This button is a oneclick execution for the PreProvisioning Tool. User could see a socalled splash screen (Fig. 239. below), a temporary message that will disappear after 10 seconds or by clicking on it with the mouse.
Fig. 239. PreProvisioning Tool splash screen Another screen could be shown, in order to give user some details on current execution. This screen (Fig. 240. below) is a textbased console with detailed information on execution in progress. This window wont disappear and cant be closed by clicking on topright X button or PreProvisioning Tool will be closed too. The window can be minimized by clicking on topright button.
Fig. 240. PreProvisioning Tool console As soon as the PreProvisioning Tool is ready, the following screen appears:
Fig. 241. PreProvisioning Tool start screen In this screen you can click on button: Open configuration : a file selection window opens, requiring a configuration_name.qcml file to be opened. In this case, the configuration process starts from data you have recovered; or Create configuration : in this case, the configuration process starts from default data. In both cases, the window in Fig. 245. on page 347 will appear. This window is the first step of the procedure. Proceed as specified in para.32.3.10 on page 346, checking and modifying data as necessary. The last step is Step L on page 368. In such a step you can only click on Save As button: configuration data are saved in a configuration_name.qcml file (provide a mnemonic name).
344 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
32.3.8 TCO Suite PreProvisioning Tool: offline creation, modification and save of a provisioning file (not interactive)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
32.3.9 TCO Suite SetUp Tool: online recover, modification and application of a provisioning file (not interactive) To launch this application, click on the button SetUp Tool of the TCO Suite Main Page (see Fig. 55. and Fig. 56. on page 149). User could see a socalled splash screen (Fig. 242. below), a temporary message that will disappear after 10 seconds or by clicking on it with the mouse.
Fig. 242. SetUp Tool splash screen Another screen could be shown, in order to give user some details on current execution. This screen (Fig. 243. below) is a textbased console with detailed information on execution in progress. This window wont disappear and cant be closed by clicking on topright X button or PreProvisioning Tool will be closed too. The window can be minimized by clicking on topright button.
Fig. 243. SetUp Tool console Then, User is asked to distinguish between Direct or Remote connection (Fig. 62. on page 156) and he/she will be asked to fill the IP address field used to connect to NE. The difference between Direct or Remote connection is described in para.22.2.6 on page 154. Then (Fig. 63. on page 157), User is asked to provide the Username and Password [same rules as in point 3 ) on page 179]. In case of remote connection, the NEs IP address entered in previous screen (Fig. 62. on page 156) is displayed.
345 / 592
Fig. 244. SetUp Tool start screen In this screen you can click on button: Get configuration from NE : in this case, the configuration process starts with data taken from the NE; this modality is exactly the same you can do by Craft Terminal through the Quick Configuration (interactive) or Open configuration : a file selection window opens, requiring a configuration_name.qcml file to be opened. In this case, the configuration process starts from data you have recovered; or Create configuration : in this case, the configuration process starts from default data.
In all cases, the window in Fig. 245. on page 347 will appear. This window is the first step of the procedure. Proceed as specified in para.32.3.10 on page 346, checking and modifying data as necessary. The last step is Step L on page 368. In such a step you can: click on Save As button: configuration data are saved in a configuration_name.qcml file (provide a mnemonic name) and / or click on Apply to NE button: configuration data are stored in the NE data base.
32.3.10 Quick Configuration Procedure steps N.B. Following screens do not show the bottom buttons, that depend on the tool by which the configuration procedure has been started and by the context. For their use please refer to para.32.3.6.1 on page 342.
346 / 592
Fig. 245. Quick Configuration Procedure: main NE parameter configuration (Step A) REMIND: in interactive modality, this screen is set with values taken from NEs data base in not interactive modality, this screen is set with default values This step provides a screen to configure the following main NE parameters: Area Site: a) Site name and location
Area NE Parameters Configuration b) Protection Type; choose between: 1+0: unprotected configuration 1+1 HSB: Hot Standby protected configuration 1+1 FD: Frequency Diversity protected configuration Tributary; choose between: 16E1: max 16xE1 without Ethernet plugin 16E1FData: DO NEVER SELECT THIS CHOICE ! 16E1GData: max 16xE1 with Enhanced Ethernet plugin 32E1: max 32xE1 N.B. the number of actually usable tributaries depends on the employed Software Label (see Tab. 23. on page 93 )
c)
347 / 592
d)
Power Supply Unit: in this SWP version, only PSU4860 choice is meaningful N.B. choices PSUVAC and PSU2460 are relevant to hardware items not presently available
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
e) f)
if equipped, click on Audio/User Service Channels plugin Market : in this SWP version, only ETSI choice is possible
Area Structure: g) Structure of the Radio Frame configuration : fields (Radio) Capacity and (Radio) Modulation. The capacity implies the choice of modulation; for example, if the tributary structure is 2E1, only 4QAM modulation scheme is supported. The association between Radio Capacity and Radio Modulation is shown in Tab. 64. below: Tab. 64. Radio application: Capacity and modulation Radio Capacity 2xE1 4xE1 8xE1 16xE1 32xE1 N.B. Radio Modulation 4QAM 4QAM / 16QAM 4QAM / 16QAM 4QAM / 16QAM 16QAM
the actually usable Radio Capacity and Modulation types depend on the employed Software Label (see Tab. 23. on page 93 ) When you change the modulation scheme (from 4 QAM to 16 QAM or viceversa) the Tx power (in case of operation with RTPC) and the ATPC range (in case of operation with ATPC) of the new modulation scheme must be in the correct range (refer to para. 26.4 on page 238). If the value is out of range the relevant field in the RTPC & ATPC screen appears empty (automatically is associated a default value, but this value is not displayed). Fill the field with the suitable value.
WARNING:
N.B.
For the Remote NE, parameters belonging to this step cannot be modified. To modify them, the System Settings menu must be used (refer to para. 23.4.1 on page 210).
To go to next step click on button Next. WARNING: At the first configuration (i.e. with a flash card with an empty MIB) at the end of the configuration the Restart NE must be performed (refer to para. 28.2 on page 160).
348 / 592
REMIND: in interactive modality, this screen is set with values taken from NEs data base in not interactive modality, this screen is set with default values This Step B has one or two substeps: one PDH tributary port configuration screen, see point [1] below and four Ethernet port configuration screens (only if Enhanced Ethernet plugin installed and configured), see point [2] on page 351 summary information on Ethernet port characteristics and management is given in Appendix D on page 547 PDH tributary port configuration screen The screen shown in Fig. 246. below provides the fields to set the signal mode (unframed, framed or disabled) of each E1 port. Moreover, the Impedance for the E1 tributary also must be selected in the Tributary Port Configuration (unbalanced 75 ohm or balanced 120 ohm).
N.B.
[1]
Fig. 246. Quick Configuration Procedure Step B: PDH Tributary configuration By clicking on the one facility button (All Framed, All Unframed and All Disabled), the operator can configure all the tributaries with the same values; otherwise he can apply all configuration for each tributary by selecting the related value from the relevant scroll list. N.B. This procedure can be used also after the first configuration to perform multiple changes in the configuration both in the local and in the remote NE.
349 / 592
In order to allow the actual configuration and transmission of the Ethernet data streams, it is mandatory that, except the case of 32xE1 Radio Capacity: at least one (*) PDH tributary port is disabled and that the position (according to Fig. 246. on page 349 ) of such disabled PDH tributary port is one of first four. N.B. If such operation is not done, the following error message is raised by the system when you click on button Next to go to the next step:
so that, to go on with the procedure, you must click OK and go back to the screen of Fig. 246. on page 349 to disable one PDH tributary port. (*) the allowed number of tributaries is as follows: Tab. 65. Allowed number of PDH tributaries with Ethernet port(s) enabled Radio Capacity (n.b.1) 2xE1 4xE1 8xE1 16xE1 32xE1 n.b.1 n.b.2 Number of allowed PDH (E1) Tributaries E1 1 E1 3 E1 7 E1 15 E1 16 GE 4 (10/100/1000BT) Number of allowed Ethernet Ports with Enhanced Ethernet plugin (n.b.2) Ethernet Bandwidth [N x (E1capacity)] N2 N4 N8 N 16 16 N 32
the actually usable Radio Capacity depends on the employed Software Label (see Tab. 23. on page 93 ) in any combination.
In the screen displayed in Fig. 246. on page 349 (and in the following Steps), the Back button is enabled also. It allows the operator to turn back and change the parameters configured in the previous screen. Now, if in Step A (Fig. 245. on page 347) you have defined 16E1GData, proceed to next substep [2] on page 351 Otherwise: to go to the next step click on button Next. to go back to the previous step click on button Back.
350 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
HOW TO OPERATE IN CASE OF CONFIGURATION WITH ETHERNET PORTS (I.E. WHEN ENHANCED ETHERNET PLUGIN IS EQUIPPED)
[2]
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Ethernet port configuration screen (with Enhanced Ethernet plugin installed) Following configuration screens ( Fig. 247. below and Fig. 248. on page 352 ) appear only if in Step A (Fig. 245. on page 347 ) you have defined 16E1GData. N.B. For whole information on Ethernet port characteristics and management, refer to the Appendix D on page 547
Fig. 247. Quick Configuration Procedure Step B: Ethernet GPort configuration WARNING: for correct system initialization, it is necessary to define a value in both fields:
for all Ethernet Ports #33 , #34 , #35 and #36 , even if one or more are disabled (i.e. with Port Status field not Enabled). If this setting is not done, the following error message is raised by the system when you click on button Next to go to the next step:
351 / 592
Fig. 248. Quick Configuration Procedure Step B: Ethernet GPort QoS configuration For detailed information on QoS configuration, refer to point [8] on page 551 To go to the next step click on button Next. To go back to the previous step click on button Back.
352 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
REMIND: in interactive modality, this screen is set with values taken from NEs data base [if you are executing this step inside the commissioning procedure, ODU(s) is/are disconnected, but the relevant frequency values have been acquired by IDU during operations of para.32.3.2 on page 339 ] in not interactive modality, fields of this screen are all empty This step allows the operator to define the basic parameters for each configured channel. The related screen (according to the Protection Type set in Step A) is shown in following Fig. 249. :
1+0
1+1 HSB
1+1 FD
353 / 592
[1]
Frequency data setting The system can operate with different types of ODU according to the RF band and to the channel arrangement. There are ODUs which can manage only one shifter (fixed shifter) or several predefined shifters (flexible shifter). For details, according to ODU type employed, please refer to para.14.5 from page 104 onwards. 1) Interactive mode a) ODU with one Shifter only If the ODU can manage only one shifter the Shifter field in the menu is not available (it is grey). In the Tx frequency field insert the Tx suitable frequency (the allowed Tx range is written in the Frequency Range field on the right side) and press pushbutton Next (the Rx frequency is automatically calculated by using the inserted Tx frequency and the shifter). ODU with different available Shifters 1 ) In the Tx frequency field insert the suitable Tx frequency ... 2 ) ... then, in the Shifter field select the suitable shifter and press pushbutton Next (the Rx frequency is automatically calculated by using the inserted Tx frequency and the shifter). WARNING: In case of troubles, please refer to point [2] on page 237 for additional information. If necessary, you can exploit the Frequency Data Help, described below, in Interactive mode too.
b)
N.B.
Note: During the command setting, the CT is frozen. Waiting time: max 30. After having set the frequency data, carry out ATPC data setting (next substep [2] on page 356). (Note: if you have gone to following Step F, go back to this Step C).
354 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
By this screen, you must set two types of configuration data: frequency data (substep [1] on page 354), and ATPC data (substep [2] on page 356), taking into account that, in case of: 1+0 and 1+1 HSB configurations, you must set data for one frequency only 1+1 FD configuration, you must set data for two channels.
2)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Non interactive mode In the screen of Fig. 249. on page 353, click the Frequency Data Help button. The screen of following Fig. 250. opens.
Fig. 250. Frequency Data Help: choice of ODU type According to the ODU system to be configured, click on relevant line. The screen of following Fig. 251. opens.
Fig. 251. Frequency Data Help: frequency data of chosen ODU type (example) N.B. The content of these tables is the same of the tables present in: para.14.5.1 from page 105 (Part lists of ODUs with external diplexer) para.14.5.2 from page 108 (Part lists of ODUs with embedded diplexer)
Thus, in non interactive mode, use values retrieved from such helponline tables to fill the Frequency Values fields of screens of Fig. 249. on page 353. Following Fig. 252. shows an example of Frequency Data manual setting with values taken from the table of Fig. 251. above. USER MANUAL INSTALLATION AND COMMISSIONING 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
355 / 592
Fig. 252. Example of Frequency Data manual setting [2] ATPC data setting In the Channel Configuration area of Fig. 249. on page 353, the ATPC can be Disabled or Enabled: if ATPC is disabled, the power (constantly transmitted) can be selected by writing the suitable value in the Tx power field in the RTPC area (see following Fig. 253. ) if ATPC is enabled, the RTPC field is greyed (cannot be selected), and the other ATPC parameters (Max TX Power value, Min TX Power value, and Low Rx Power threshold value) must be configured in the ATPC area fields (see following Fig. 254. ): strictly following rules stated in para. 26.4 on pages 238 to 240 and obviously setting Max TX Power value > Min TX Power value. WARNING: if you want to set the minimum value of the range greater than the current maximum value, you must at first change the maximum value, then change the minimum value (obviously setting it smaller than maximum)
356 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 254. Setting of enabled ATPC In case of 1+1 FD, two tabbed panes (as previous Fig. 253. and Fig. 254. ) are proposed for channel 0 and for channel 1 with the same choices applied.The ATPC/RTPC parameters condition for a channel implies the same configuration for the other one. In case of 1+1 HSB, choices will be applied to both channels (Fig. 255. below).
Fig. 255. ATPC and RTPC Configuration for both channels (1+1 HSB) To go to the next step click on button Next. To go back to the previous step click on button Back.
357 / 592
Step D (Link Identifier configuration) The amount of microwave links, especially in urban areas, puts the problem of possible interferences during installation and turnon phase. The digital frame incorporates link identity coding capabilities to prevent the capture of an unwanted signal. Link identifier management can be: enabled selecting the choice Mismatch Detection in the screen of Fig. 256. below or disabled deselecting it.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
In case of enabled Link identifier management, it is necessary to provide the NEs with the suitable sent and expected link identifiers values. The NE originating the section inserts the sent identifier. The NE terminating the section extracts the received identifier and compares this value to the expected one. received identifier = B sent identifier = A sent identifier = B received identifier = A
STATION A
STATION B
When the mismatch detection is enabled and the value of the incoming identifier is different from the expected one, a Link Identifier Mismatch (LIM) is notified and an AIS signal will be inserted down stream. Link identifier functionality is managed per NE: in case of 1+1 radio configurations the same link identifier code is used on both the radio channels. Link identifier functionality is performed by 5 bits link code, then 32 values link code are allowed.
358 / 592
REMIND: in interactive modality, this screen is set with values taken from NEs data base in not interactive modality, this screen is set with default values This step (Fig. 257. below) appears only if any 1+1 configuration has been defined in step A. It allows the operator to choose the restoration criteria (revertive or not revertive) for the 3 possible protections available in the 1+1 configuration: Radio Protection (Rx RPSHitless Switch) Mux/Demux Protection (Tx/Rx EPS) HSB Tx Protection (RF Hot Standby)
Fig. 257. Quick Configuration Procedure: Automatic restoration criteria configuration (Step E) To go to the next step click on button Next . To go back to the previous step click on button Back.
359 / 592
Step F (OSPF area configuration) REMIND: in interactive modality, this screen is set with values taken from NEs data base in not interactive modality, fields of this screen are all empty WARNING FOR NOT INTERACTIVE MODALITY: if OSPF data are already defined in the NEs data base, when the file is downloaded to the NE, OSPF data defined in this procedure do not overwrite those present in the NEs data base. The only way to change such data is to use the interactive modality. This step (Fig. 258. below) allows to configure one or more OSPF Areas (3 areas max.).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 258. Quick Configuration Procedure: OSPF Area Configuration (Step F) WARNING: Area 0 is managed and created by default with Id = 0 and IP address = 0.0.0.0
To create a new area write a number in the Area Id field, in the IP address field write the address and click on Add button. If the OSPF area must be a stub area, make the selection in the Stub Area check box. WARNING: When the area is a Stub area, all interfaces inside the same Stub Area (NMS and Ethernet) must be defined Stub.
In the upper part of the screen the new OSPF area will appear. To remove or change an OSPF Area Configuration select the Area in the upper part and click on Remove or Change button. To go to the next step click on button Next. To go back to the previous step click on button Back. 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL INSTALLATION AND COMMISSIONING
360 / 592
REMIND: in interactive modality, this screen is set with values taken from NEs data base in not interactive modality, this screen is set with default values
Fig. 259. Quick Configuration Procedure: Local IP address, Ethernet and NTP configuration (Step G) This step (Fig. 259. above) allows to configure: with reference to Fig. 76. on page 170: the Local IP address associated to the F interface of the NE. This address is that used to identify the NE as far as the RECT function is concerned. the Ethernet interface: it can be Enabled or Disabled by ticking the TMN Ethernet field (default is Enabled). If enabled, enter in the relevant fields the IP address, the IP mask and select the Routing protocol. If the selected routing protocol is OSPF, select also the area number in the associated OSPF Area field. WARNING: please do never use the RIP choice present in the Routing Protocol field! Rules for the definition of the NEs Local IP and Ethernet IP addresses: as delivered from AlcatelLucent Factory, the NEs Local IP and Ethernet IP addresses are both set at default value 10.0.1.2 ; obviously, these values must be changed to have them different from each other and from those of the other NEs present in the accessible network. In particular such two addresses must not belong to the same subnetwork (i.e. the third digit must be different. Examples: wrong definition: Local IP address = 10.0.1.2 and Ethernet IP address = 10.0.1.3 correct definition: Local IP address = 10.0.1.2 and Ethernet IP address = 10.0.2.3 with IP Mask = 255.255.255.0 the Network Time Protocol (NTP). To enable the NTP put a tick in the check box of the NTP field. If the NTP has been enabled, write in the Main Server field the IP address of the Server, which distributes the NTP, and write in the Spare Server field the IP address of the Spare Server, if any, which will distribute the NTP in case of failure in the Main Server. N.B. It is mandatory to define both the Main Server address and the Spare Server address.
In case a Spare Server is not available, fill its address field with the same value of the Main Server.
To go to the next step click on button Next . To go back to the previous step click on button Back. USER MANUAL INSTALLATION AND COMMISSIONING 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1
361 / 592
Step H (Configuration of TMNRF, TMNV11 and TMNG703 channels) REMIND: in interactive modality, this screen is set with values taken from NEs data base in not interactive modality, this screen is set with default values
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 260. Quick Configuration Procedure: Configuration of TMNRF, TMNV11 and TMNG703 channels (Step H) This step (Fig. 260. above) allows to configure the following TMN channels: the TMNRF interface is a communication interface based on the use of an inframe RF proprietary 64 kbit/s channel. Through this interface the NE can exchange management messages with a remote OS (or Craft Terminal) station. through the TMNV11 or the TMNG703 interface the NE can exchange management messages with an OS (or Craft Terminal) in the same station.
Each TMN channel can be Enabled or Disabled by selection in its own Enable field. If enabled, in the Remote Address field will appear the IP address of the remote connected NE. In the Routing IP Protocol field enter the used IP protocol and in case of OSPF protocol select also the associated OSPF area. In the Mode field of the TMNV11 and TMNG703 interfaces the following selections can be made: DTE mode: to interface an SDH service channel, where DCE mode is not available because of the common synchronization of the SDH network. Codirectional mode: to allow the routing of the LUX40 NMS, avoiding the needed V11/Eth adapter or to link adjacent AWY.
362 / 592
With this TMN inframe feature, 9400AWY 2.1 equipment is able to introduce in one of the time slots (TS 131) of the E1#1 tributary, a 64 kb/s signal as network management system (NMS or TMN) to transmit remotely this type of information along the E1#1 route; this selection is alternative to the local availability of TMNG703 (the mutual exclusion is automatic). It is also necessary that the farend E1#1 tributary is enabled and successfully provisioned. To activate the TMN inframe feature, in TMN G703 field (see Fig. 261. below) : set Mode to InFrame E1 define the required E1#1 Timeslot number (default is 1)
Fig. 261. Quick Configuration Procedure: Configuration of TMN inframe (Step H) To go to the next step click on button Next . To go back to the previous step click on button Back.
363 / 592
Step I (IP Static Routes Configuration) REMIND: in interactive modality, this screen is set with values taken from NEs data base in not interactive modality, fields of this screen are all empty This step (Fig. 262. below) configures one or more Static Routers.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 262. Quick Configuration Procedure: IP Static Routes Configuration (Step I) The following fields and data are present: [1] [2] Host Address: Network Address: allows to define the IP address necessary to reach a specific Host. it is in alternative to the Host Address; allows to define the IP Mask to reach a network. allows to define the address of the next hop gateway. it allows to use the point to point interfaces (the 3 NMS channels) available with the NE. No pending (open) static routes are allowed. The default software uses first the static routes and then the dynamic routes. An open static route is always considered as a preferential path.
[3] [4]
WARNING:
364 / 592
N.B.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Default Gateway Routing configuration It is also possible to define a Default Gateway Routing. To do that, in the screen in Fig. 262. on page 364 select Network Address. The screen changes to following Fig. 263. : REMIND: in interactive modality, this screen is set with values taken from NEs data base in not interactive modality, fields of this screen are all empty
Fig. 263. Quick Configuration Procedure: Default Gateway Routing configuration (Step I) In this screen operate as follows: a) b) c) d) in IP Address field, write 0.0.0.0 in IP Mask field, write 0.0.0.0 in Default Gateway IP Address field, write the required destination click Add
To go to the next step click on button Next. To go back to the previous step click on button Back.
365 / 592
Step J (EOW and Auxiliary Interface Configuration) REMIND: in interactive modality, this screen is set with values taken from NEs data base in not interactive modality, fields of this screen are with default values This step (Fig. 264. below) appears only if the Audio/User Service Channels plugin configuration has been defined in step A. It allows the operator to choose: the field Phone Number in the Order Wire Configuration area allows the operator to read and write the station number associated to the Engineering Order Wire to be used in the selective call. Possible values are: 1099 (see chapter 42 on page 413 for details) N.B. Number 00 is the value associated to the general call.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
the field Type in the Auxiliary Interface Configuration area allows the operator to change the interface of the auxiliary channels (see para.13.6.4 on page 90 for details)
Fig. 264. Quick Configuration Procedure: EOW and Auxiliary Interface configuration (Step J)
366 / 592
REMIND: in interactive modality, this screen is set with values taken from NEs data base in not interactive modality, this screen is set with default values This step (Fig. 265. below) configures the external points (please refer to para.13.6.1 on page 85 for physical implementation).
Fig. 265. Quick Configuration Procedure: External Input and Output Points configuration (Step K) For: both Inputs and Outputs: clicking in the Polarity field, Active Closed or Active Opened can be chosen Outputs only: clicking in the Working Mode field, Manual or Automatic can be chosen; if Manual is chosen, you can select the Associated Event clicking in the relevant field
To go to the next step click on button Next. To go back to the previous step click on button Back.
367 / 592
Step L (Summary) This is the last step (Fig. 266. below). The screen shown summarizes all the parameters configured during this procedure and some relevant parameters with default values.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 266. Quick Configuration Procedure: Summary (Step L) All the parameters can still be changed by clicking on the Back button. The operator can navigate back to the desired screen and set the new values. According to the configuration tool started, at the end the operator can: click on Save As button: configuration data are saved in a configuration_name.qcml file (provide a mnemonic name) and/or confirm the selections by pressing the Finish or Apply to NE or Save & Apply button. All the parameters are stored and sent to the NE. At the end of the NE updating, a summary of the values of all the parameters are shown to the operator with the indication of the result of each request of change (OK or error message). An indication of the parameters remained unchanged is provided too. WARNING: in case of problems regarding the Shifter Value and/or the Central Frequency , that could result in one of the following error message: Shifter Value KO OK Central Frequency OK KO you must go back to point [1] (Frequency data setting) on page 354 and check and correct both values, not only that declared KO. or do none of such operations, clicking on Cancel.
If you are inside the commissioning procedure, obviously you must have defined a correct configuration. In this case proceed with next para.32.3.11.
368 / 592
After the completion of the configuration step, switch Off the IDU(s) in order to reestablish the IDUODU(s) connections. Then, switch on the IDU(s), log in the NE and proceed to the following checks:
32.3.11.1 Verify ODU(s) alarm status Purpose: Required Instruments: Procedure: . CT Views Equipment In the left window, select ODU ch#1 n n z In the lower right window, verify in the alarms list for that there is no internal communication failure In the lower right window, verify in the alarms list that there is no TX failure. Repeat for Ch#0 if any (1+1) Verify no abnormal communication alarm between IDU(s) and ODU(s) PC with Craft Terminal software Connect CT to IDU
369 / 592
32.3.11.2 Transmitter power output check Purpose: Required Instruments: Procedure: . CT Views Radio From the left window select Channel #1 From the lower right window select RTPC & ATPC tab panel n Verify that ATPC is Disabled as already set during the quick step procedure (If required, change the ATPC status to disable in the ATPC field then Apply) Verify that Tx Power value complies with the suitable value already set via the quick step procedure. (If required, change the Tx Power in the RTPC field then Apply) Repeat for Ch#0 if any (1+1) Verify via CT the ODU(s) transmitted power output. PC with Craft Terminal software Connect CT to IDU
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
370 / 592
Verify via CT the received power to detect any interference PC with Craft Terminal software Connect CT to IDU
From the left window select Channel #1 From the lower right window select Power Meas tab panel In the Sample time (sec), write the suitable measurement poling time then press Start
371 / 592
Pressing Start will prompt a graphic monitoring view of the transmitted and received levels:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Ticking the box show details in the lower left corner will call a summary view of the TX an Rx levels:
Fig. 270. Received power details Verify that the current Rx local End received level is < 95 dBm (no interferences) Repeat for Ch#0 if any (1+1)
n z
WARNING: If in the Tx end field the indication in dBm is +99, the Transmitter is off (or in HSB Configuration the transmitter is in standby). If in the Tx end field the indication in dBm is +99 and, at the same time, in the relevant Rx end field the information in dBm is 99, probably the supervision has been lost. The confirmation of the loss of the supervision is given by a broken red icon in NES screen. USER MANUAL INSTALLATION AND COMMISSIONING
372 / 592
To commission station B, perform the same operations carried on at station APhase 1 (para.32.3 on page 338). When Station B is fully configured and operational, and assuming that the antenna in station A has been previously correctly pointed, you should receive some field from station A. In this case, proceed to a fine tuning of the antenna to improve as much as possible the received level. To monitor the received level during alignment, use the Craft Terminal received power measurement facility described in para.32.3.11.3 on page 371, or the Light service kit cable for ODU Rx power monitoring in addition to a voltmeter (see description in Annex A: antenna alignment on page 404).
For near future tests, establish on the Station DDF hardware loops on every tributary as well as on the User service channel.
READ THIS GENERAL INFORMATION ABOUT TEST BENCH DRAWINGS In the test bench drawings depicted in the following, take always account that: 1) the standard equipment interfaces for access points are in most cases considered at Station DDF, in turn connected (in 1+1 configurations) to the lineside connectors of the E1 Protection box and of the Services Protection box (when the Audio and User Service Channel plugin is equipped). When protection boxes are not employed, Station DDF is connected directly to the IDU MAIN unit connectors. Station DDF is not detailed in the drawings: refer to your own plant documentation for details. For detailed information: on the description of equipment interconnections (in all 1+0 and 1+1 configurations), please refer to para.32.2 on page 331 , making reference to the equipment interconnection diagram corresponding to your actual system layout. in case of 1+1 configurations, regarding the description of connector pinout of: E1 Protection box, please refer to para.13.5 on page 79 Services Protection box, please refer to para.13.6 on page 84 regarding the description of IDU MAIN unit connector pinout, in case of 1+0 configurations, where protection boxes are usually not employed, please refer to the Installation Handbook
2)
the Craft Terminal (CT) is always necessary. The connection between CT and NE can be done in two alternative ways (see Fig. 76. on page 170): trough a crossconnect Ethernet cable between the Ethernet port of the PC and the Ethernet interface on the Main IDU or trough a RS232 cable between the serial port of the PC and the F interface (ECT) on the Main IDU.
3)
373 / 592
32.5.1 Remote NE (station B) acquisition on craft terminal . . n Connect the cable between the serial port of the PC and the F interface (ECT) on the Main IDU. Start the 1320 CT application. Wait until the NES window appears, for the LLMAN to connect and the Map indicator to turn grey.
Right click on Station A NE icon and select Start supervision, or Supervision Start n The question mark in the NE icon disappears while the alarm status of the NE appears.
374 / 592
z
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Right click on the first line Map sample (or click on Map sample and select NE Directory) and choose create SNMP NE. The following window will prompt
Fig. 272. Create NE in the CT map Write the local IP address of Station B in the TCP/IP Address field and the port number in the TCP/IP Port field (typically: 161), then click OK. The newly created NE will appear in the CT map as shown below. Right click on Station B NE icon and select Start supervision, or Supervision Start
Fig. 273. NMS Radio side Remote NE acquisition N.B. The above remote NE acquisition is described assuming that the TMNRF access have been enabled in both Stations during Quick Configuration Procedure step H on page 362. On the contrary, the TMNRF channel can be enabled directly through the CT menu: CT Configuration Network Configuration IP configuration IP point to point configuration.
375 / 592
32.5.2 Testing configurations for hop quality check Interfacing with the E1 Protection box, set up the following testing configuration and run on one tributary, a minimum of one hour BER test free of error. Remote station
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
ODU
ODU
IDU MAIN
IDU MAIN E1 ERROR ANALYZER E1 ERROR ANALYZER Fig. 274. Test bench for tributary quality test Interfacing with the Services Protection box, set up the following testing configuration and run on the User service channel, through the hardware loopback previously established in station B, a minimum of 10 minutes BER test free of error. Remote station
ODU
ODU
DATA ANALYZER G.703 or V11 Fig. 275. Test bench for User service channel quality test N.B. In case of V.11 the loopback on the remote station cannot be performed. In this case two data analyzer must be used.
376 / 592
Commissioning phase 2 is a site acceptance test procedure made up of the required tests to ensure that the equipment is fully operational. This phase describes first of all the way to check and to change (if necessary) via the Craft Terminal menu the different configuration parameters already set, for most of them, during the Quick Configuration Procedure in phase 1, followed by various tests. Most of the tests and checks results have to be recorded in the TRS (Test Results Sheet ; see Tab. 63. on page 330). Operator will be invited to do so each time it is required by the following sentence: Report
See and fill the indoor inspection check list in the TRS.
32.6.1.2 Outdoor System installation and cabling inspection
See and fill the indoor inspection check list in the TRS.
32.6.2 Local configuration control Purpose: Required Instruments: Procedure: Verify via CT the Local Station configuration. PC with Craft Terminal software Connect CT to IDU
32.6.2.1 Check software key (Software Label) code . CT Supervision SW key The screen of Fig. 159. on page 256 opens.
Report the Type, Market, Capacity, Modulation and Impedance into the TRS
Close.
377 / 592
32.6.2.3 Check/set E1 tributaries configuration Reference screen: Fig. 129. on page 228 : . CT Views Line Interface In the left window E1 port# 1
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
In the lower right window Configuration Tab panel. Repeat for each E1 port# If it is necessary to change any parameter, refer to para.25.1.2.1.1 on page 228
Reference screen: Fig. 133. on page 232 : . CT Views Line Interface In the left window Ethernet Port#33 or Ethernet Port#34 or Ethernet Port#35 or Ethernet Port#36
In the lower right window Configuration Tab panel. If it is necessary to change any parameter, refer to point [2] on page 232
378 / 592
32.6.2.5.1 Radio Protection Reference screen: Fig. 163. on page 260 : . CT Views Protection Schemes In the left window Radio Protection (RPS) In the lower right window Schema Parameters Tab panel Protection Type 1+1 If required, change Operation type (Revertive or Not Revertive) then Apply For additional information, refer to para.29.2 on page 260
379 / 592
32.6.2.7 Check/set TX and RX frequencies Reference screen: Fig. 136. to Fig. 138. on pages 235 to 236 : . CT Views Radio In the left window Channel #1
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
In the lower right window Frequency Tab Panel Repeat for Channel 0 (only in 1+1)
Report the ATPC Disabled status, Tx nominal Power and Tx Power setting into the TRS
ATPC Enabled: . CT Views Radio In the left window Channel #1 In the lower right window RTPC&ATPC Tab Panel n ATPC Enabled Repeat for Channel 0 (only in 1+1)
Report the ATPC Enabled status, ATPC Range and ATPC RX Threshold setting into the TRS
If required, change ATPC Mode or ATPC Range or ATPC Rx Threshold then Apply For additional information and warnings, refer to para.26.4 on page 238
380 / 592
32.6.2.9 Check/set the User data channel type and the station phone number
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Reference screen: Fig. 113. on page 213 : . CT Configuration System Setting Overhead Tab Panel
Report the auxiliary interface type and the Phone number into the TRS
Close For additional information and parameter change, refer to para.23.4.3 on page 213 , or to Quick Configuration Procedures Step J screen described on page 366
32.6.2.10 Check/set the local NE IP address Reference screen: Fig. 91. on page 192 : . CT Configuration Network Configuration Local Configuration
32.6.2.11 Check/set OSPF Area Configuration Reference screen: Fig. 99. on page 200 : . CT Configuration Network Configuration IP Configuration OSPF Area Configuration
Report the Id, IP Address, IP Mask and Stub flag into the TRS
For additional information and parameter change, refer to para.23.2.4.3 on page 200 , or to Quick Configuration Procedures Step F screen described on page 360
32.6.2.12 Check/set the NMS IP point to point interface configuration Reference screen: Fig. 101. on page 202 : . CT Configuration Network Configuration IP Configuration IP Point to Point Configuration
Report the mode, IP Routing, OSPF Area and Remote Address for Enabled connection into the TRS
For additional information and parameter change, refer to para.23.2.4.4 on page 202 , or to Quick Configuration Procedures Step I , point [4] described on page 364
381 / 592
32.6.2.13 Check/set the Ethernet access (OS) configuration Reference screen: Fig. 94. on page 195 : . CT Configuration Network Configuration Ethernet Configuration
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Report the IP Address, IP Mask, IP Routing protocol and OSPF Area into the TRS
For additional information and parameter change, refer to para.23.2.3 on page 195 , or to Quick Configuration Procedures Step G described on page 361
32.6.2.14 Check/set IP static routing configuration Reference screen: Fig. 96. on page 197 : . CT Configuration Network Configuration IP Configuration IP Static Routing Configuration
Report the IP Address, IP Mask and Default gateway IP Address or interface type into the TRS
For additional information and parameter change, refer to para.23.2.4.1 on page 196 , or to Quick Configuration Procedures Step I described on page 364
32.6.3 Channel 1 functionality tests (1+0 and 1+1) Open the summary Block diagram view for all the duration of Channel 1 functionality tests in order to visualize at any time the Switching and Loopback status of the microwave: Purpose: Required Instruments: Procedure: Display the summary block diagram PC with Craft Terminal software Connect CT to IDU
382 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
If any indication does not correspond to the expected one, press Refresh to actualize the view. By clicking on a specific object of the drawing, the operator can navigate to the relevant CT menu view.
383 / 592
32.6.3.1 Channel protection switching configuration (1+1 only) Purpose: Required Instruments: Procedure: lockout the channel 0 for all the duration of the channel 1 testing PC with Craft Terminal software Connect CT to IDU
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
In the lower right window Commands scroll list Lockout Apply Repeat for HSB Tx Protection and Mux/Demux Protection n Check in the summary block diagram that the full channel 1 (TX and RX) path is in service.
Report about the Channel 1 protection switching functionality into the TRS
Fig. 278. Channel 0 lockout mode For additional information and parameter change, refer to chapter 29 on page 257
384 / 592
Verify via CT the near end loopback functionality PC with Craft Terminal software and E1 Data Analyzer Connect CT to IDU Connect Data analyzer on one Tributary Access (At the Station DDF)
Four different near end Loopbacks have to be performed one by one. Remove previous loopback before proceeding with the next one. A delay up to 10 seconds may be observed for each activation/deactivation. Ensure that the local tributary access (used to control via the data analyzer the continuity and the quality of every loopback) is active (framed or unframed) (see para.32.6.2.3 on page 378 for more details about tributaries configuration) Ensure that the local transmitter is not muted. (see para.45.9.10 on page 449 for more details about TX Mute functionality)
IDU
ODU
A N T E N N
TRIB E1 1
MUX DEMUX 2 3
MODEM
RF 4
Near End Tributary Loopback Point Near End IDU Cable Loopback Point Near End ODU Cable Loopback Point Near End RF Loopback Point (N.B.) RF loopback is optional and provided only with specific configurations Fig. 279. Near End loopbacks points
385 / 592
. CT Views Loopback In the lower right window Activate Apply n n Data analyzer showing no errors Loopback showing in the summary block diagram view
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
In the left window Tributaries TX port# NE (select tributary on which the Data Analyzer is connected)
Report about the near end Tributary loopback functionality into the TRS
Fig. 280. Loopback control in the CT . CT Views Loopback In the left window Channel #1 IDU Cable In the lower right window Activate Apply n n Data analyzer showing no errors Loopback showing in the summary block diagram view
In the lower right window Deactivate Apply Repeat for Near End IDU Cable and Near End ODU Cable
Report about the near end IDU Cable and ODU Cable loopback functionality into the TRS
386 / 592
Verify via CT the Far end loopback functionality PC with Craft Terminal software and E1 Data Analyzer Connect CT to IDU Connect Data analyzer on one Tributary Access (At the Station DDF)
One Far end loopback has to be performed under the same condition as the near end loopbacks. Moreover, ensure that the remote transmitter like the local transmitter is not muted.
IDU
ODU
A N T E N N A A N T E N N A
ODU
RF MODEM MUX DEMUX
IDU
TRIB
E1
E1
STATION A
STATION B
Fig. 281. Far End loopback point . CT Views Loopback In the left window Tributaries TX port# FE (select the same tributary # that the one which is locally connected to the data analyzer) In the lower right window Activate Apply n n Data analyzer showing no errors Loopback showing in the summary block diagram view
In the lower right window Deactivate Apply WARNING: A far end loopback can be removed only from the NE that activated it.
Report about the Far end Tributary loopback functionality into the TRS
387 / 592
32.6.3.4 Tributary functionality test Purpose: Verify the point to point Tributaries quality Verify the tributaries alarm status monitoring functionality
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Required Instruments: PC with Craft Terminal software and E1 Data Analyzer Procedure: Connect CT to IDU Connect Data analyzer on Tributary Access (At the Station DDF)
IDU MAIN
IDU EXTENSION
N.B.
IDU MAIN
Tributary loopback
N.B. E1
ERROR ANALYZER PATTERN GENERATOR
N.B.
the diagram indicates the loopback (at remote station) and the connection (at local station) for the first 16 E1 tributaries. To check the other ones, change connections. Fig. 282. Test bench for tributary functionality check
388 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Assuming that all the tributaries have been enabled (Unframed status) via CT in both stations and that every tributary are looped at the DDF in the remote station: z n n Perform one minute of BER test on each E1 tributary Verify that the analyzer detects no error. Verify on CT Line Interface view the tributary alarm status:
. CT Views Line Interface In the lower right Alarms list, verify that while the data analyzer is connected, the AlarmLossSignal on the relevant tributary goes off. Note: Check also the framed tributaries (if required).
Report about the Tributary BER test and alarm CT monitoring into the TRS.
389 / 592
32.6.3.5 Service data channel functionality test Purpose: Verify the point to point Service Data Channel quality
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Required Instruments: PC with Craft Terminal software and G703 / V11 64 Kbit/s Data Analyzer Procedure: Connect CT to IDU Connect Data analyzer on the service channel Access (At the Station DDF)
IDU EXTENSION
DATA ANALYZER 64kbit/s (G.703 or V11) Fig. 284. Test bench for User Service Channel functionality check Assuming that the User service Channel is looped at the DDF in the remote station: z n Perform 10 minutes of BER test. Verify that the Data analyzer detects no error.
Report about the 64 Kbit/s Data channel BER test into the TRS
390 / 592
Verify the point to point Ethernet Data Channels quality PC with Craft Terminal software and 2 Ethernet Data Analyzers Connect CT to IDU Connect Data analyzer on Main IDU Ethernet Access.
Test bench for Enhanced Ethernet plugin (4xGigabit Ethernet plugin) equipped: Fig. 285. below
z n
Perform 10 minutes of BER test on both Optional Ethernet access. Verify that the Data analyzer detects no error.
Report about the Ethernet Data Channels BER test into the TRS.
ODU Remote station ODU ODU IDU EXTENSION IDU MAIN IDU EXTENSION ODU
Fig. 285. Test bench for Optional Ethernet Data Channel functionality (with 4xGigabit Ethernet plugin)
391 / 592
32.6.3.7 Ptx and Prx measurement Purpose: Verify via CT the Transmitted (Ptx) and received (Prx) power
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Reference screen: Fig. 141. on page 241 : . CT Views Radio From the left window select Channel #1 From the lower right window select Power Meas tab panel In the Sample time (sec), write the suitable measurement poling time then press Start Pressing Start will prompt a graphic monitoring view of the transmitted and received levels (see Fig. 142. on page 242 ): Ticking the box show details in the lower left corner will call a summary view of the TX an Rx levels (see Fig. 143. on page 243 )
Report the Current Tx Local End (Ptx) and the current Rx Local End (Prx) into the TRS.
For additional information, PTx and PRx levels software readings tolerance and warnings, refer to para.26.5 on page 241
392 / 592
ODU
Remote Station
ODU
EXTENSION MAIN
ODU
ODU
EOW
1 4 7 2 5 8 0 3 6 9
*
Fig. 286. Engineering order wire organization Make a call from local station: 1. 2. 3. 4. 5. 6. Check that the line is free (green EOW LED is on). Handset OFF/ON switch to ON. On keypad, press # to engage line. Check that yellow EOW LED on MAIN IDU is on (as well as in the remote station) On keypad, dial the twodigit remote station number or 00 for general call. Ring tone is audible in the handset.
OFF ON
In the remote station: 7. 8. Yellow EOW LED is flashing and the IDU is emitting a ring tone. Connect handset to IDU, set ON/OFF switch to ON, press # on keypad. Speak.
393 / 592
32.6.4 Channel 0 functionality tests (1+1 only) 32.6.4.1 Channel protection switching configuration Purpose: Forced the channel 1 for all the duration of the channel 0 testing
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
In the lower right window Command scroll list Forced Apply n Check in the summary block diagram that the full channel 0 (Tx and Rx) path is in service.
Repeat for: the Mux/Demux Protection (see para.29.1 on page 258 ) and, only for HSB systems, the HSB TX Protection (see para.29.3 on page 262 )
Report about the Channel 0 protection Switching functionality into the TRS
Fig. 287. Channel 1 forced mode Note : The Forced command for channel 1 is equivalent to the Lockout command for the channel 0. In both cases, the result is that the relevant channel protection path is forced to standby status.
For additional information and parameter change, refer to chapter 29 on page 257
394 / 592
Repeat the same test already performed for channel 1. 32.6.4.3 Far End Loop back functionality Repeat the same test already performed for channel 1. 32.6.4.4 Tributary functionality test Repeat the same test already performed for channel 1. 32.6.4.5 Service data channel functionality test Repeat the same test already performed for channel 1.
32.6.4.6 Ethernet Data channel (optional) functionality test Repeat the same test already performed for channel 1. 32.6.4.7 Ptx and Prx measurement Repeat the same test already performed for channel 1.
32.6.4.8 Inside hop Engineering Order Wire functionality test Repeat the same test already performed for channel 1.
395 / 592
32.6.5 Hop stability test Purpose: Required Instruments: Procedure: Verify the Hop stability PC with Craft Terminal software and E1 Data Analyzer Connect CT to IDU Connect Data analyzer on one Tributary Access (At the Station DDF)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The Hop stability test is performed during two consecutive hours, one time, on one Tributary, in real working condition whatever the protection configuration (1+ 0 or 1+1). The two hours stability test must be free of error in normal propagation conditions (out of fading period) Via the CT, let only one active tributary in both station In the remote Station, place a hardware loop on the relevant tributary access (at the station DDF). In the local station, connect the E1 Data Analyzer on the relevant tributary. Check that the Tributary Alarm Loss disappears. Verify in both stations that there are no active software loopbacks or switching requests Verify in both stations that none alarm is showing.
z z z
n n
Report the two hours free of error test result into the TRS.
ODU Remote station ODU ODU IDU EXTENSION ODU
IDU MAIN
IDU EXTENSION
IDU MAIN
Tributary loopback E1
ERROR ANALYZER PATTERN GENERATOR
396 / 592
32.6.6
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
NE integration tests
32.6.6.1 NMS Radio side acquisition Purpose: Required Instruments: Procedure: Verify Via CT the remote NE RF side acquisition PC with Craft Terminal software Connect CT to IDU
NE Radio side acquisition has been already performed during the Turn Up (commissioning phase 1). Refer to para.32.5.1 on page 374 for more details. 32.6.6.2 NMS Line side acquisition (if foreseen in the plant documentation) Purpose: Required Instruments: Procedure: Verify Via CT the remote NE line side acquisition PC with Craft Terminal software Connect CT to IDU Toward station B ODU Local Station (Station A) Direction 2 ODU
V11
or
G703
Fig. 289. Test bench for NMS Line side acquisition N.B. A transfer cable must be placed between the G703 or V11 connectors of the two Services Protection boxes.
On both IDUs, the NMS line side access must be enabled: . CT Configuration Network Configuration IP Configuration IP Point to Point Configuration Select V11 interface or G703 interface (depending of the transfer cable used) and the required routing. Select enable Apply The IP address of the line side remote NE should appear in the remote address field.
397 / 592
z . .
Connect the CT to the IDU facing Station B Start the 1320 CT application. Right click on each NE icon and select Start supervision, or Supervision Start
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Since the NMS RF side NE acquisition has already been performed, both local and remote NE of the hop currently under commissioning are visible.
Fig. 290. NES window local NE Right click on the first line Map sample (or click on Map sample and select NE Directory) and choose create SNMP NE. The following window will prompt
Fig. 291. Create NMS Line side NE in the CT map Write the local IP address of Main IDU direction 2 in the TCP/IP Address field and the port number in the TCP/IP Port field (typically: 161), then click OK.
398 / 592
The newly created NE (direction 2) will appear in the CT map as shown below.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Right click on direction 2 NE icon and select Start supervision, or Supervision Start
Fig. 292. NMS Line side NE monitoring in the CT map Check that Direction 2 NE responds correctly to supervision: . Right click on the NE icon and select Show equipment, or Supervision Show equipment
Report about the NE line side acquisition functionality into the TRS.
399 / 592
32.6.6.3 EOW line side call (if foreseen in the plant documentation) Direction 1 ODU Local Station ODU Direction 2
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
OFF ON
AUDIO 1
or
AUDIO 2
Fig. 293. Test bench for EOW line side functionality test Make a call from IDU direction 1 to IDU direction 2 or any remote station in Direction 2: A transfer cable must be placed between the Audio 1 or Audio 2 connectors of the two Services Protection boxes. Check that the line is free on both Main IDU(s) (green EOW LED is on). On IDU direction 1: 1. 2. 3. 4. 5. 6. Check that the line is free (green EOW LED is on). Handset OFF/ON switch to ON. On keypad, press # to engage line. Check that the EOW LEDs turn to yellow (as well as on the IDU direction 2) On keypad, dial the twodigit number of the IDU direction 2 or any remote station in direction 2. Ring tone is audible in the handset.
On IDU direction 2 (or in the remote station in direction 2 which is called): 7. 8. Yellow EOW LED is flashing and the IDU is emitting a ring tone. Connect handset to IDU, set ON/OFF switch to ON, press # on keypad. Speak.
Report about the Order wire Line side functionality into the TRS.
400 / 592
32.6.6.4 Housekeeping alarms setting and testing (if foreseen in the plant documentation)
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.
For additional information not given here, refer to chapter 27 on page 247
32.6.6.4.1 External alarm inputs Note: These tests should be performed only in specific sites requested by the Customer. Purpose: Required Instruments: Procedure: Configure and test Via CT the housekeeping external alarm inputs PC with Craft Terminal software Connect CT to IDU
Six alarm inputs are available to monitor either Relay contact or open collector type external alarms. Reference screen: Fig. 148. on page 247 : . CT Views External Points In the left window INPUT CPI 1 to CPI 6
In the lower right window User Label Write the suitable name for the current alarm. Polarity Configure if the alarm must show when closed or opened Alarm Profile Primary Alarms (by default) Testing the external alarms monitoring: Assuming that CPI 1 is configured in Active Closed polarity: z Place a hardware loop on the station DDF between CPI 1 access point (Sub D pin 6) and GND point (Sub D Pin 10). See connection point description in para.13.6.1 on page 85. Verify in the CT External points view that CPI 1 is showing an alarm. Repeat with CPI 2 to 6.
n z
Report about the House keeping input alarms acquisition into the TRS.
401 / 592
32.6.6.4.2 Alarms outputs Purpose: Configure and test the housekeeping equipment alarms outputs Required Instruments: PC with Craft Terminal software and Multimeter (loop tester) Procedure: Connect CT to IDU Three alarm outputs are dedicated to fixed equipment general alarms: IDU, ODU 1 and SPARE ODU. Four alarm outputs CPO 1 to 4 can be configured either as equipment alarm or manual remote control:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Reference screen: Fig. 149. on page 248 : . CT Views External points In the left window In the lower right window OUTPUT CPO 1 to CPI 4
User Label Write a name for the current equipment or remote control alarm Polarity Configure if the contact must be closed or opened when active
To use the relevant Alarm output as a manual remote control: Criteria Manual Apply Then, to activate the remote control External State On Apply
To use the relevant Alarm output as an automatic equipment alarm: Criteria Automatic Select in the Event scroll list the equipment alarm to be associated Apply Testing a remote control alarm Output: z Connect a multimeter (loop tester mode) between CPO 1 access point (Sub D pin 4) and the Common wire point (Sub D pin 9). See connection point description in para.13.6.1 on page 85. CT Views External points In the left window In the lower right window OUTPUT CPO 1 Polarity Active Closed.
Criteria Manual Apply External State On Apply n Loop tester must detect a loop (close circuit).
In the lower right window External State Off Apply n z Loop tester does not detect anymore loop (open circuit). Repeat with CPO 2 to 4.
Report about the House keeping Output alarms detection into the TRS.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL INSTALLATION AND COMMISSIONING
402 / 592
Repeat in Station B all the tests performed in Station A except the Hop Stability Test that has to be run only one time for the full hop.
403 / 592
d)
e) N.B.
404 / 592
Fig. 294. herebelow shows this optional cable (P/N 3CC 13477 AA**):
A F
B G
2 3 4 5
2 3 4 5 6 7 8 9 10
11
Black B Red C D
6 7 8 9 10
11
12
12
C 6 11 5 7 12 8
D 7 12 8 6 11 5
4 10
1 9 2
1 9 2
View following F LEMO wire 6 = ground Fig. 294. Light service kit cable Connector usage:
3 View following G
4 10
(A) LEMO connector, to be plugged into LEMO connector on ODU (see Fig. 46. on page 120 and Fig. 47. on page 121) (B) LEMO connector, for AlcatelLucent internal use only. banana plugs (C) and (D) : output is a 0 to +3V DC voltage proportional to the radio Rx field. During equipment lineup, through a multimeter it is possible to easily point the antenna until the measured voltage is the maximum, corresponding to the maximum radio Rx field. Actual Rx field value can be measured by means of the Craft Terminal (see para.26.5 on page 241). (E) RS232 connector, for AlcatelLucent internal use only.
405 / 592
a)
406 / 592
END OF SECTION
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
413
415
421 429
465
469
485
495
497
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
407 / 592
408 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
41 MAINTENANCE POLICY
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
This chapter introduces the basic concepts for the equipment maintenance.
Second Level Maintenance: PREVENTIVE (periodic set of measurements and checks) CORRECTIVE (troubleshooting and repair)
First level maintenance consists of a set of simple operations by means of which a First Level Maintenance Operator can acknowledge the state of the system and decide whether or not the intervention of a Second Level Maintenance Operator is required in order to bring back the assembly to optimum operating conditions by troubleshooting and unit replacement, if necessary. In this philosophy: First Level Maintenance Operator should not be authorized to change the equipment status; he should be only authorized to display it or to make some simple tests through the Craft Terminal, if expressly authorized by the Station Manager. These actions are described in chapter 44 on page 421. Second Level Maintenance Operator is authorized to make all actions necessary to repair the system; moreover he should only be authorized to carry out routine maintenance. These actions are described in chapter 45 on page 429. With regard to the access to the Craft Terminal functionalities as well as to the TCO Suite NEinteractive functionalities, notice that it is possible to use the following operator profiles: viewer for the First Level Maintenance Operator craftPerson for the Second Level Maintenance Operator.
The twostation layout typical of a radio link requires often that different operators can communicate with each other to solve problems. The EOW functions of this equipment give a simple way for this communication need. This matter is described in chapter 42 on page 413.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
409 / 592
Without these prerequisites, reading this handbook and the associated handbooks indicated in para.57.2.1 on page 569 is usually not enough to properly maintain equipment.
The following interfaces are present on the equipment for troubleshooting purposes: Ethernet interface for: the Telecommunication Management Network ( TMN ) the Craft Terminal (Local or Remote) the TCO Suite NEinteractive functionalities F interface for the Craft Terminal (Local or Remote) LEDs located on the NEs units.
410 / 592
[3]
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Usually, maintenance is firstly done via software (TMN or Local/Remote Craft Terminal or the TCO Suite NEinteractive functionalities) to locate the faulty equipment and the faulty unit or the faulty path and then on site to physically correct the trouble. Maintenance can be done: from a TMN network management center. By means of the TMN, the maintenance technician can see the alarms generated by each equipment of the managed network (see the relevant TMN handbooks). from a Remote Craft Terminal (RCT) management center. The operator, connected to a local NE, can remotely manage and troubleshoot a network composed of max 128 NEs, including itself. This handbook applies to this function. on site. The operator is on site in case: a) b) c) d) the equipment is not managed by a TMN or by a Remote Craft terminal (RCT). the equipment is not reachable by the remote manager (TMN or RCT) and therefore is isolated. link problems are present. the trouble has been located and a physical replacement is necessary.
In cases a ) , b ), c ), the alarmed equipment is checked by means of the local Craft Terminal. [4] The NE is provided with LEDs which indicate Centralized Equipment Alarms. All alarms detected on the units are collected by the IDU MAIN unit, which delivers centralized indications (by means of LEDs on the front coverplate). Specifically: Red LED: detection of a MAJOR (URGENT) alarm. Red LED: detection of a MINOR (NOT URGENT) alarm. Yellow LED: alarm condition ATTENDED. Red LED: detection of a LDI (problem in the local equipment). Red LED: detection of an RDI (problem in the remote equipment).
In the case of a MAJOR or MINOR alarm, after locating the alarmed unit, the alarm condition can be attended by pressing the alarm storing push button on the front panel of the IDU MAIN unit. This condition causes on the front coverplate: yellow LED ATTENDED to light up red LEDs MINOR and MAJOR to turn off (free to accept other alarms) If both LEDs are on, the Attend command should be given twice : one to attend the MINOR alarm and one to attend the MAJOR alarm.
[5]
The troubleshooting operation is done by means of the Craft Terminal, and of the optical indicators (LEDs) present on the NE. The Craft Terminal is connected to the relative connector (F or Ethernet interface) on the front coverplate of the IDU MAIN unit. The Craft Terminal applications provide detailed information on the alarm state thus facilitating fault location and subsequent removal as indicated in para. 45.8 on page 436. To correctly execute the troubleshooting operations the technician must know the equipment configuration (see Equipment applications on the Craft Terminal).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
411 / 592
412 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Please refer to chapter 41 on page 409 for an introduction to the basic concepts of equipment maintenance. This chapter explains how to configure and use the EOW (Engineering OrderWire) function of the equipment.
STATION B
ODU
1 4 7 *
2 5 8 0
3 6 9 #
3 6 9 #
1 4 7 0
2 5 8 *
OFF ON
OFF ON
Telephone handset
each Telephone handset has its own phone number. Phone number can be in the 10 to 99 range. Telephone handsets must have different phone numbers.
Physical connection on IDU: connect Telephone handsets RJ11 plug to TPH connector on the IDU MAIN unit [ (7) in Fig. 21. on page 70 ]. b) Telephone handset view Caution: to operate, set the handset switch to FV.
Set switch to FV
ON/OFF switch
RJ 11 connector
c)
Telephone handset keyboard KEY MEANING Force unlocking of the line Engage line
* #
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
413 / 592
d)
Display/setting is done: by Quick Configuration Procedure (see Step J on page 366 ) or by Craft Terminal with the following menus (refer to para.23.4.3 on page 213 for details): display: Configuration System Settings Overhead Phone Parameter setting: Configuration System Settings Overhead Phone Parameter phone number Apply e) Ways of Calling : two different ways of calling are possible: f) SELECTIVE: OMNIBUS: a connection between two users (dial a number: 10 to 99) a unidirectional connection with all the users (dial digits 00)
LEDs indication: EOW (GREEN): free line EOW (YELLOW): busy line Flashing YELLOW: received and recognized call N.B. position of green/yellow LED on IDU MAIN unit:
EOW
GREEN YELLOW
GREEN
RED
RED
GREEN
RED
RED
YELLOW
42.2 Call Setup/End by Telephone handset connected to the IDU Main unit
a) To Call from Handset: 1) 2) 3) 4) 5) 6) b) Check that line is free (EOWfree green LED on the MAIN unit is on) Set Handset ON/OFF switch to ON On keypad, press # to engage line Check that EOWbusy yellow LED on the MAIN unit is on On keypad, dial twodigit number of station to be called (or 00 for omnibus call) Ring tone is audible in the handset, wait for answer
To Answer Call at Handset: 1) 2) EOWbusy yellow LED on the MAIN unit flashes and audible tone is present If not connected, connect handset to IDU, set ON/OFF switch to ON, press # on keypad, speak
c)
To End Call from Handset: 1) 2) On keypad, press * Move handset ON/OFF switch to OFF
414 / 592
43.1 Introduction
Please refer to chapter 41 on page 409 for an introduction to the basic concepts of equipment maintenance. This chapter describes the instruments, accessories and the equipment spare parts that are envisaged to carry out the routine and corrective maintenance of the equipment, and and is organized as follows: Instruments and accessories herebelow, including: Software tools herebelow Maintenance, Installation and Station Tool Kits on page 416 Set of spare parts Types of Spare Parts Number of Spare Parts General rules on spare parts management on page 418, including: on page 418 on page 419 on page 419
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
415 / 592
43.2.2 Maintenance, Installation and Station Tool Kits For the P/Ns of these Tool Kits, please see REF.[2] , [3] and [4] in Tab. 24. on page 96 . a) The Installation Tool Kit includes various types of common usage fixed spanners, standard and crosshead screwdrivers, polygon spanners, polygon tube spanners, special fixed spanners, a torque wrench, etc. The Maintenance Tool Kit is practically equal to the Station Tool Kit, with the addition of the Antistatic wristband. The Station Tool Kit is a bag additionally containing various types of cables and cable adapters.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
b)
c)
The detailed item list of these Tool Kits is given in Appendix F from page 563 : N.B. Installation Tool Kit part list, para.56.1 on page 563
MaintenanceTool Kit part list, para.56.2 on page 564 StationTool Kit part list, para.56.3 on page 565
These Tool Kits are standardized kits for the use with all AlcatelLucent WTD equipment types: they contain also items that are not used in 9400AWY environment (they are not described in this manual).
Some special items are listed in Tab. 66. below, which gives also reference to figures where they are depicted. Tab. 66. Special items of the Tool Kits SPECIAL ITEM COMPONENTS OF ANTISTATIC WRISTBAND Antistatic wristband Antistatic applications cord Plug with crocodile pliers Female button termination SPECIAL EXTRACTORS Unhook tool for 1.0/2.3 coax SPECIAL TOOLS AND ITEMS FOR ODU Lever for ODU mounting/dismounting Fig. 296. on page 417 Fig. 295. below Fig. 1. on page 36 DESCRIPTION
416 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
When, in ODU configurations 1+1 with coupler, you must dismount and then mount one of the two ODUs for maintenance purposes, the following operations: UNBLOCK BEFORE DISMOUNT One at a time, unblock the four ODU blocking levers (A) pushing up the restraint spring (B) and, contemporarily, turning down the lever (C). BLOCK AFTER MOUNT Block the four ODU blocking levers (A) may produce vibrations that could cause synch loss or other electrical disturbances to the other ODU still working.
allows to do the same unblock/block operations without producing vibrations. The following photographs should clarify the correct lever handling and usage.
Fig. 296. Lever for ODU mounting/dismounting USER MANUAL MAINTENANCE AND UPGRADE 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
417 / 592
As a matter of fact, all other ODUrelated items listed in Chapter 14 on page 97 (but whose P/Ns are given in the Installation Handbook) can be considered items to be provisioned as spare parts. 43.3.3 IDU Spare Parts The set of spare parts for the IDU is inclusive of a minimum number of spares for each type of replaceable units. The suggested spare parts should be at least those containing electronic parts; in general the spare part types are: IDU Main unit, for both (1+0) and (1+1) systems IDU Extension unit, for (1+1) systems only Flash card, for both (1+0) and (1+1) systems
As a matter of fact, also passive items (whose P/Ns are given in the Installation Handbook) can be considered items to be provisioned as spare parts. a) Spare parts for IDU Main and Extension units For P/Ns, refer to para.13.1 on page 68. N.B. In case a terminal has IDU Main and/or Extension units equipped with plugin(s), and you order as spare parts such units separately from the plugin(s), take into account that, when the IDU Main or Extension faulty unit must be replaced, the spare part box has first to be opened, then the plugin must be installed, at last box must be closed.
b)
Spare parts for Flash Card There are various possible types of Flash Cards. For details refer to para.13.7 on page 93 . For the sparepartstock, Customer should provision at least one Flash Card for each type (P/N) of Flash Card equipped in systems in service. For cost saving, as alternative to provision the various types, that with Software Label 64Mb 16 QAM could be provisioned instead. N.B. Read important information regarding the spare Flash Card management in para.46.1 on page 465. USER MANUAL MAINTENANCE AND UPGRADE
418 / 592
The overall number of spares depends on Customer requirements, and should be based on the average amount of transmission circuits available to be accounted for not only during MTBF (Mean Time Between Failures) but also during MTTR (Mean Time To Repair); the latter depending on the amount of spare parts available. 43.3.5 General rules on spare parts management Before storing the spare units make sure that they are working by inserting them in an operating equipment. It is suggested to periodically check those spare units that have not been utilized for over a year. If the spare parts and the equipment are stored in the same environment, make sure that the spare parts are placed in cabinets to safeguard them from dust and damp. Moreover, they should also be well grounded to avoid electrostatic discharges. If the spare parts are stored in another room, or have to be moved from another place, building or site, make sure that the following is observed: the spare parts must be wrapped in antistatic and padded envelopes; the spare parts must not touch wet surfaces or chemical agents that might damage them (e.g. gas); if during transportation the temperature is lower than that of the room where they had been kept, make sure that before using them they pass a certain period in a climatic chamber to prevent thermal shocks and/or the possibility of steaming up.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
419 / 592
420 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
44.1 Introduction
Please refer to chapter 41 on page 409 for an introduction to the basic concepts of equipment maintenance. This chapter describes the First Level Maintenance of the equipment and is organized as follows: System state display by visual indications, below TCO Suite and Craft Terminal commonly used functions for system status display and checks, on page 423
LED ON (green)
Fig. 297. LEDs and pushbutton on IDU Extension unit for maintenance purposes
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
421 / 592
RED
RED
YELLOW
(10) Reset
(11) LED test (12) F interface for Craft Terminal Meaning If off (and if the ON/OFF switch is on) there is a problem in the station battery or in the MAIN unit There is a failure in the equipment There is a failure in the remote station Detection of an URGENT alarm: it means that there is at least one alarm (internal and/or external) for which traffic is affected. Detection of a NOT URGENT alarm: it means that there is at least one alarm (internal and/or external) for which traffic is not affected (e.g. something is wrong, but the traffic is recovered by an automatic protection switch). Alarm condition ATTENDED: it means that an Operator (by pushbutton (8) or by Craft Terminal) has attended the alarm (for details, see para. 45.6.2 on page 434). Action A A A A
LED on Green LED ON Red LED LDI Red LED RDI Red LED MAJ
ACTION: A B The immediate intervention of a Second Level Maintenance Operator is required. The immediate intervention of a Second Level Maintenance Operator is not required Fig. 298. LEDs and pushbutton on IDU MAIN unit for maintenance purposes
422 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
44.3 TCO Suite and Craft Terminal commonly used functions for system status display and checks
This paragraph sums up how to use the TCO Suite and Craft Terminal functions for system status display and checks to be carried out by a First Level Maintenance Operator. N.B. These operations should be done by the First Level Maintenance Operator only if expressly authorized by the Station Manager, who, in his turn, for each 9400AWY NE that should be accessible by the First Level Maintenance Operator must: assign him a Username/Password set in case of remote NE, communicate him the NEs IP address.
44.3.1 Viewing the NE alarms by TCO Suite Proceed as follows: 1) startup the TCO Suite Alarms & Settings function as explained in para.22.3.1 on page 156, using: the NEs IP address (if remote NE) the Username and Password communicated by the Station Manager in the Alarms & Settings Main Menu screen that appears (Fig. 64. on page 157), click on button Active Alarms refer to para.22.3.6 on page 165 for the alarm screen interpretation. at the end, close the TCO Suite Alarms & Settings Active Alarms screen.
2)
3) 4)
44.3.2 Viewing the NE status by Craft Terminal Proceed as follows: 1) login the NE as explained in para.22.5.2 on page 173, using: the NEs IP address (if remote NE) the Username and Password communicated by the Station Manager. the 9400AWY Main view opens (see Fig. 87. on page 181). From this screen, according to the user profile assigned through the entered Username/Password set, you can navigate to make some checks. Suggested checks are: a) Summary Block Diagram view Proceed as follows: Click on button 181183) in the Main tool bar (see Fig. 87. and Fig. 88. on pages
2)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
423 / 592
b)
3)
at the end: first, carry out the NE Logoff as explained in para.22.5.3 on page 180 then, close the 1320CT application as explained in para.22.5.4 on page 180.
424 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Checks on Radio domain Various checks are possible selecting the specific matters of the Menu bar, as shown in following Fig. 299. to Fig. 304. For screen interpretation, click on their relevant HELP button and/or refer to chapter 26 on page 233.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
USER MANUAL MAINTENANCE AND UPGRADE Fig. 301. Checks on Radio domain : Frequency
425 / 592
426 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
USER MANUAL MAINTENANCE AND UPGRADE Fig. 304. Checks on Radio domain : Power Measurement
427 / 592
428 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
45.1 Introduction
Please refer to chapter 41 on page 409 for an introduction to the basic concepts of equipment maintenance. Second level maintenance consists of a set of operations which maintain or bring back the assembly to optimum operating conditions in a very short time, with the aim of obtaining maximum operational availability. Second level maintenance is classified as: ROUTINE or PREVENTIVE (periodic set of measurements and checks, independently of troubles) CORRECTIVE (troubleshooting and repair, in case of troubles) This chapter describes the routine and corrective maintenance operations and is organized as follows: Warnings on page 430, including: EMC norms Safety rules Cautions to avoid equipment damage Routine (preventive) Maintenance Consequences of unit extraction in the IDU Corrective Maintenance general flowchart Alarm acknowledgment and attending TroubleShooting starting with visual indications TroubleShooting via Craft Terminal Alarm and status synthesis indications Details on alarms / statuses Description of alarms and of probable causes Hints on the troubleshooting IDU Unit replacement ODU replacement Faulty unit repair and Repair Form
on page 431 on page 432 on page 433 on page 434 on page 435 on page 436 on page 437 on page 439 on page 440 on page 442 on page 451 on page 460 on page 463
The handbook parts that should be read (or known) before starting this chapter are: chapter 12 on page 37 chapter 13 on page 67 chapter 14 on page 97 chapter 41 on page 409 chapter 43 on page 415 chapter 44 on page 421 System overview IDU provisioning and description ODU provisioning, characteristics and description Maintenance Policy Maintenance Tools and Spare Parts First Level Maintenance
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
429 / 592
45.2 Warnings
45.2.1 EMC norms
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
ATTENTION
EMC NORMS
WHEN CARRYING OUT THE GIVEN OPERATIONS OBSERVE THE NORMS STATED IN PARA. 51.4.3 ON PAGE 509 45.2.2 Safety rules The Safety Rules stated in para.51.3 on page 502 describe the operations and/or precautions to observe to safeguard operating personnel during the working phases and to guarantee equipment safety. Please read them carefully before starting each action on the equipment.
SAFETY RULES
General Carefully observe the frontpanel warning labels prior to working on optical connections while the equipment is inservice. Should it be necessary to cut off power during the maintenance phase, proceed to switch off the power supply units as well as cut off power station upstream (rack or station distribution frame) Electrical safety DANGER: Possibility of personal injury. Personal injury can be caused by 48 V DC. DANGER: Possibility of personal injury. Short circuiting, lowvoltage, lowimpedance, DC circuits can cause severe arcing that can result in burns and/or eye damage. Remove rings, watches, and other metal jewelry before working with primary circuits. Exercise caution to avoid shorting power input terminals. 45.2.3 Cautions to avoid equipment damage Read carefully para.11.6 on page 36.
430 / 592
Routine maintenance is a periodic set of measurements and checks. This maintenance discovers those devices whose function has deteriorated with time and therefore need adjustment or replacement. Typically, digital equipment requires no routine maintenance. The equipment allows to assess the quality of the connection links or counting the errored events and obtaining performance data. The Performance Monitoring Application, described in para. 45.8.4 on page 441, allows this function. 45.3.1 Routine (preventive) Maintenance every year It is suggested to carry out the following operations yearly: [1] Mechanical checks Check that: the units, the cables, the mounting fixtures are inserted and connected correctly. Grounding check Check that the racks, subracks, and modules are grounded (for 9400AWY shelves, see para.51.3.6 on page 506). Power cables check
[2]
[3]
SAFETY RULES DANGER: Possibility of personal injury. Personal injury can be caused by 48 V DC. DANGER: Possibility of personal injury. Short circuiting, lowvoltage, lowimpedance, DC circuits can cause severe arcing that can result in burns and/or eye damage. Remove rings, watches, and other metal jewelry before working with primary circuits. Exercise caution to avoid shorting power input terminals. Make these operations: Check that the power cable is perfectly safety grounded. Make sure that the subrack has been tightly fastened to the rack with screws, to guarantee grounding (the rack is connected to the station ground). [4] Operative checks Visual check: During the normal operation, check the led normal condition, as specified in para.44.2 on page 421. Checks by Craft Terminal some suggested checks are indicated in para.44.3 on page 423 the commissioning tests, described in Chapter 32 on page 329, can be useful to carry out equipment functional checks as a whole, in particular as far as checks on radio hop are concerned.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
431 / 592
The extraction of a unit has always some consequences on system behavior and performance that the Maintenance Operator must know in advance: a) Consequences of the MAIN unit extraction The time taken to extract the MAIN unit must be short and should be limited to the time strictly necessary for operation and maintenance purposes; it causes: interruption of the traffic on channel 1 in (1+1) configurations, all protections are lost the NE not to be supervised because the Equipment controller is installed in this unit.
Note for (1+1) configurations: before extracting the unit make sure that the traffic is transmitted over channel 0 (on the Extension unit). Otherwise, force with the CT the traffic onto channel 0.
b)
Consequences of the Extension unit extraction The time taken to extract the Extension unit must be short and should be limited to the time strictly necessary for operation and maintenance purposes; it causes: interruption of the traffic on channel 0 all protections lost
Note: before extracting the unit make sure that the traffic is transmitted over channel 1 (on the MAIN unit). Otherwise, force with the CT the traffic onto channel 1.
432 / 592
TroubleShooting starting with visual indications (para.45.7 page 435) TroubleShooting starting via Craft Terminal (para.45.8 page 436). Identification of a unit to be replaced.
System check via Craft Terminal Try again with another unit N Fault repaired ?
Y If possible, restore replaced unit in the system and perform system check via Craft Terminal, to verify that is really faulty Possible intermittent failure N Fixed fault ? Y Restore spare part in the system and perform system check via Craft Terminal
Send back faulty unit to Repair Centre together with Repair Form compiled (para.45.12 on page 463)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
433 / 592
remotely (in a TMN maintenance center) when the OS acknowledges the presence of problems in the station.
When the local Operator decides to manage the problem, he should carry out the alarm attending operation (see para. 45.6.2 below). This operation has the scope of notifying locally in the station and remotely to the TMN maintenance center that a local operator is attending the problem.
45.6.2 Alarm Attending See Fig. 298. on page 422: the detected alarm condition can be stored through the Alarm attending pushbutton on the MAIN unit. This operation will turn OFF the LEDs MAJ / MIN and will light up the yellow LED ATTD on the MAIN unit (Attended). The local Operator could also attend the alarm via the craft terminal. a possible new alarm condition (following the Attending) will turn on the LEDs MAJ / MIN. when the fault has been repaired, the yellow LED (if the alarm had been attended) or the red ones (if the alarm had not been attended and no further alarms have occurred in the mean time) will turn off.
434 / 592
Refer to Fig. 305. on page 433, for the position of this step inside the corrective maintenance general flowchart. Some problems may be localized through the LEDs indicated in para. 44.2 on page 421. In any case, the inspection through the Craft Terminal is recommended before any unit replacement. Flowchart of Fig. 306. indicates LEDs on the MAIN unit that should be considered first. START
N END
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
435 / 592
The operating instructions make it possible to identify the faulty unit. Having located the suspected faulty unit, replace it with a spare one (refer to para.45.10 on page 451 for IDU, or to para.45.11 page 460 for ODU). 45.8.1 Diagnosis The options available in the Diagnosis menu are: Current Configuration View Summary Block Diagram View: displays a global logical view (strictly related to the physical implementation) highlighting a synthesis of all the alarms and statuses present in the system (ODU+IDU). Abnormal Condition List Remote Inventory Event Log The generic events occurred and discriminated by the NE are stored in one or more Event Log files. The ELB (Event Log Browsing) application embedded in the 9400AWY SWP allows the Operator to read such log files, in order to have historical data that can be useful to troubleshoot the equipment or the link or the PDH network, in case of multiple alarm conditions or intermittent alarms. N.B. The event log file examination is quite complex; it is reserved to AlcatelLucent skilled personnel as a debug tool (only using filters on the not meaningful events, it is possible to understand the meaning of the stored data).
For further information and operative procedures, refer to the Chapter 211 on page 277.
436 / 592
The Alarm surveillance available with the CT allow the Operator to examine the alarms currently present in the equipment or in the link or in the PDH network. The information on the NE alarm will be mainly obtained by means of the Craft Terminal through the Alarm tab panel data. The troubleshooting procedure is the following. a) Look at the active alarms on the Control Panel always present on the window (which summarizes all the NE alarms). Tab. 67. on page 438 describes the meanings of these alarms/statuses and its respective maintenance actions. In case of alarm, access the Alarm tab panel for troubleshooting. Para 45.8.2.2 on page 439 explains how to see the alarms. MAJOR alarm indicates a severe alarm that could affect the current traffic (interrupt or degrade). Hence, a prompt intervention is necessary to restore the regular operating condition of the equipment. 45.8.2.1 Alarm and status synthesis indications The following Tab. 67. pertains to the alarm and status synthesis given in all the screens, pointed out in this Fig. 307. :
b)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
437 / 592
Tab. 67. Alarm Synthesis indications Mnemonic CRI MAJ MIN WNG IND EXT EQP TRS Alarm / Status Description Critical alarm Major (Urgent) alarm Minor (Not urgent) alarm Warning alarm Indeterminate alarm External Point (Housekeeping alarm) Equipment alarm Transmission alarm Local Access state (see para.211.2 on page 279) Maintenance Synthesis of alarms that needs immediate troubleshooting (typical: NE isolation). (N.B.) Synthesis of alarms troubleshooting. (N.B.) that needs immediate
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Synthesis of alarms for which a deferred intervention can be decided. (N.B.) Synthesis of alarms due to failure of other NE in the network. (N.B.) Synthesis of alarms not associated with the previous severities. Not operative. Check the relevant station alarm associated with the input housekeeping indication. Synthesis of alarms of the Equipment domain. Synthesis of alarms of the Transmission domain. GREEN LED: Indicates that the Craft Terminal has the OS permission to manage the NE (granted). CYAN LED: Indicates that the Craft Terminal has not the OS permission to manage the NE (denied). GREEN LED: Identifies the Enable operational state of the connection between NE and Craft Terminal ( SDH service link up ). RED LED: Identified the Disable operational state of the connection between NE and Craft Terminal ( service link down ). GREEN LED: NE is under supervision. BROWN LED: NE is not under supervision. Used in the OS. Alignment status of the SH MIB respect to the equipment MIB. GREEN LED: Indicates that the N.E. is not managed by the 1353NM/SH. CYAN LED: Indicates that the N.E. is managed by the 1353NM/SH. GREEN LED: NTP protocol enabled and both NTP servers ( Main and Spare ) are unreachable. BROWN LED: NTP protocol disabled. CYAN LED: NTP protocol enabled and at least one NTP servers ( Main or Spare ) are reachable. GREEN LED: Normal operating condition. CYAN LED: Detection of an ABNORMAL operative condition. Type: switch forcing.
COM
NE reachable/unreachable
SUP
Supervision state
ALI
Alignment
OS
NTP
AC N.B.
Abnormal Condition
The Alarm Profile can modify the assignment of each alarm root to the various synthesis.
438 / 592
The troubleshooting proceeds by checking the detailed information on the NE active alarms using the Craft Terminal as in Fig. 308. below. It is also possible to analyze the detailed alarms present on each TP of the Port views of the NE. [1] [2] [3] [4] [1] Select the Equipment tab panel. Select one node (or subnode) in the Resource Tree Area to check if some alarms are active. Select the Alarm tab panel in the Resource Detail Area. If the node has subnodes put a tick in the Include alarms from subnodes field to display the alarms active also in the subnodes.
[2]
[3] [4]
Fig. 308. Active alarm screen Detailed information of some alarms are supplied. The following table summarizes the information obtained in the Alarm view, starting from the left column. Tab. 68. Alarm information, general description TITLE Severity Event time Entity Probable Cause Managed Object Class DESCRIPTION severity associated to the alarm and assigned in the Alarm Profile time of the generation of the alarm entity involved in the alarm probable cause of the alarm class of the alarm
The information supplied helps the operator during the troubleshooting operations. Tab. 69. on page 440 supplies general information on the alarm meanings and on the respective maintenance actions to be done bases on the information given in the applications. The maintenance action must take account of the board where the alarm is detected. The Housekeeping alarms are referred to the input external point relevant to the Housekeeping signals. They are available to the customer by connecting them to a dedicated subrack connector.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
439 / 592
45.8.2.3 Description of alarms and of probable causes The information provided helps the operator during troubleshooting operations. Tab. 69. General issues of the alarm meanings and their respective maintenance actions ALARM AIS ATPC loop problem Battery fail High BER Dem fail Dem LOS Cable LOS Incompatible Frequency Incompatible PTX Internal Communication Problem LAN failure MEANING MAINTENANCE ACTION tributary connected
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
AIS detection on the tributary in Tx Check the side or Rx side equipment Problem on the ATPC loop Problem on the Station Battery Excessive BER
Communication problem Check the Station Battery Excessive errors. Check the link (propagation problem)
Demodulator failure affecting the Replace the ODU demodulated signal Loss of the incoming signal at the Check the demodulator input problem) Problem on the cable or on the ODU link (propagation
Replace the ODU; if the alarm is still active replace the cable.
Frequency setting incompatible with Change the frequency or change the the ODU P/N ODU Output power out of the limits ODU not responding Replace the ODU Press the Reset pushbutton on the MAIN unit. If the alarm is still active, replace the ODU Check the LAN connection or replace the MAIN unit Check the correct connection of the cable between the IDU and the relevant ODU. If the connection is correct, check the link (propagation problem) connected
LAN problem
Loss Of Frame
LOF at the Tx tributary input or at Rx tributary output (with framed Check the tributary tributary) or LOF of the Rx equipment or the line aggregate signal LOF of the Rx aggregate signal LOS at the Tx tributary input Low BER at the Rx side Check the link (errors) Check the line Check the problem) link
Loss Of Frame (Aggregate signal) Loss Of Signal Low BER Mod fail Mod LOS Remote Defect Indication Replaceable Unit Problem
(propagation
Internal modulator failure affecting Replace the ODU the modulated signal No signal at the modulator input Alarm active in the remote station Problem on a replaceable unit Investigate by using the loopback facilities with the CT. Check the remote station Replace the unit USER MANUAL MAINTENANCE AND UPGRADE
440 / 592
Tab. 69. General issues of the alarm meanings and their respective maintenance actions
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
MEANING
MAINTENANCE ACTION
Mismatch between the installed unit Change the unit configuration or and the sw configured unit change the unit Install the unit Check the problem) link (propagation
Replaceable Unit Type Missing No unit in a configured slot Rx Fail (Radio alarm) Threshold Cross Tx Fail (Radio alarm) Unconfigured Equipment Present Version Mismatch Housekeeping 45.8.3 Loopbacks No RF received signal
Performance threshold has been Errors on the link crossed Transmitter failure Replace the ODU
Unit present in an unconfigured slot Configure the unit Mismatch on the software version Download the software version between CT software and equipment software Active input housekeeping Check the housekeeping
The loopbacks (settable by CT) give the possibility to perform some functional tests, thus making the fault location and maintenance tests faster and easier. The loopbacks are explained in Chapter 210 on page 267. 45.8.4 Operators Controls of the protection switches In certain troubleshooting conditions, changing the state of the protection switches can be useful to fix problems. For further information and operative procedures, refer to the Chapter 29 on page 257. 45.8.5 Tx mute function (local and remote) This facility allows to switch off the transmitter. This facility can be useful during commissioning to avoid producing interference if the frequency is not yet properly set. For further information and operative procedures, refer to the Chapter 26 on page 233. 45.8.6 Performance Monitoring The Performance Monitoring is responsible for quality events counting and reporting. For further information and operative procedures, please refer to the Chapter 212 on page 289. 45.8.7 BER measurement The BER measurement (noonintrusive) can be carried out as described in para.26.6 on page 246 45.8.8 Commissioning tests In some cases, the commissioning tests, described in Chapter 32 on page 329, can be useful to carry out equipment functional checks as a whole, in particular as far as checks on radio hop are concerned.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
441 / 592
on page 443 on page 444 on page 445 on page 445 on page 446
on page 447
442 / 592
Proceed with the following checks: Verify that the CT Ethernet port is effectively that connected by a crossconnect cable to the MAIN UNIT Ethernet interface on the left (see Fig. 76. on page 170; that on the right is not for CT interface). Restart the Craft Terminal (NE logout, PC switch off/on, NE login). N.B. To carry out NE login, do not use Start Alcatel 1320CT, but click the button Operational & Maintenance of the TCO Suite Main Menu (see Fig. 55. and Fig. 56. on page 149), and answer to question of Fig. 77. on page 174 specifying Ethernet interface usage. Disconnect and then reconnect, at PC side, the Ethernet cable; this message should arise at reconnection:
Otherwise: the cable could not be the required crossconnect type (see Tab. 54. on page 144), or it could be broken PC Ethernet port faulty MAIN unit Ethernet port faulty If possible, verify the correct working of the Craft Terminal and of the Ethernet cable using them with another AlcatelLucent equipment. If the problem still persists, solve the problem. Otherwise, before replacing the MAIN UNIT or the FLASH CARD, perform steps indicated in para.45.9.1.5 on page 445.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
443 / 592
45.9.1.3 Craft Terminal not working on NEs Finterface Proceed with the following checks: Verify that the CT serial port is effectively that connected by cable to equipments F interface and that cable is correctly connected. In Windows, verify that the possible selection Start Programs Alcatel Lower Layers does exist; if not, the installation and configuration of LLMAN and Alcatel Virtual Network Card for Lower Layers (necessary for PCNE Finterface usage) has not been carried out: refer to Appendix C on page 517 to know what to do. Check for the Network Connections order (para.53.3.6 on page 546). Restart the Craft Terminal (NE logout, PC switch off/on, NE login). N.B. To carry out NE login, do not use Start Alcatel 1320CT, but click the button Operational & Maintenance of the TCO Suite Main Menu (see Fig. 55. and Fig. 56. on page 149), and answer to question of Fig. 77. on page 174 specifying F interface usage. Check that speed is the same: at PC side (see para.55.7.3 on page 562) at NE side through the TCO Suite Alarms & Settings function (see para.22.3.1 on page 156, and para.22.3.9 on page 167). With the Craft Terminal connected to the equipment Finterface, open the Alcatel Lower Layer in the MSWindows Manager screen (by clicking with the mouse pointer on the Alcatel symbol menu bar, or by Start Programs Alcatel Lower Layers Lower Layers Manager, and interpret the various fields of the screen that opens (Fig. 309. below) as described in the 1320CT Basic Craft Terminal Operators Handbook (see Tab. 78. on page 571), chapter Software Installation, paragraph Communication with NE.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Link led
Fig. 309. Lower Layers Manager screen If the Link led is red (i.e. OFF), the problem can be due to: PC serial physical port faulty MAIN unit Finterface port faulty the cable FLASH CARD missing on MAIN unit (verify) or FLASH CARD/MAIN faulty If possible, verify the correct working of the Craft Terminal and of the serial cable using them with another AlcatelLucent equipment. If the problem still persists, solve the problem. Otherwise, before replacing the MAIN UNIT or the FLASH CARD, perform steps indicated in para.45.9.1.5 on page 445. 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL MAINTENANCE AND UPGRADE
444 / 592
In some situations, the CT is blocked (not temporarily) and, even if 1320CT application is closed by TaskManager and then relaunched again, the following message could arise: Another instance of the system probably running . Do you really to continue setting? Answering yes, you enter in Network Element Synthesis, but in this case continuos Autorestart trouble / Cannot autorestart program are received and the successive start of supervision fails. If you decide to close again the CT in correct way and relaunch again the 1320CT application, no signaling of errors are present but the condition does not change (CT is still blocked) In this situation, there are two solutions: a) b) loggingout and then reloggingin Windows session, thus terminating all active applications or, if you do not want to close all applications, terminating manually all CT single processes by TaskManager. The list of processes to be terminated is: acdbm.exe FTclient.exe FTserver.exe java.exe LLman.exe lss.exe nesim.exe nspd.exe secim.exe admctemlimosi.exe dxcctemlimosi.exe tsdsnmpemlim.exe N.B. pay attention not to terminate other processes !
45.9.1.5 Checks before MAIN unit or FLASH CARD replacement If the Craft Terminal application does not respond (login unsuccessful): 1) 2) push the RESET button on the MAIN unit and wait 10 minutes; if, after 10 minutes, the Craft Terminal application responds, open the Alarm status procedure and proceed investigating the system state; if, after 10 minutes, the Craft Terminal application does not respond, replace the MAIN unit, as indicated in para.45.10.1 on page 452. if the problem still persists after the MAIN unit has been replaced, the failure or content corruption of the FLASH CARD must be suspected (a very extraordinary event); proceed with its replacement, as indicated in para.46.2 on page 466.
3)
4)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
445 / 592
45.9.2 Analog measurements In case of two CT connected to the NE, as shown in the figure below, and at the same time both open on the menu Radio Power Meas, the analog measurements relevant to the PTx rem (Tx power of the Remote NE) and the PRx rem (Rx power of the Remote NE) could have some instabilities (i.e. an intermittent +99 dBm is reported for the PTx rem and 99 dBm is reported for the PRx rem).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
ODU
ODU
Station A IDU
Station B IDU
45.9.3 NMS 64 kbit/s V.11 and G.703 For a correct operation the NMS channel has to be configured in one station as DTE and in the other station as Codirectional. This selection can be done in the Quick Configuration Procedures Step H on page 362
45.9.4 Loopbacks For a correct activation of every loopback (Loopback menu): the relevant tributary must be enabled (Quick Configuration Procedures Step H point [1] on page 349 ) the local transmitter must be not muted (CT Menu Radio Configuration)
Note 1: The loopback will become active after 67 sec. approx. (24 sec. approx. for the RF loopback). Note 2: The time for a new set is 10 to 25 sec. approx.
446 / 592
Enter Windows Task Manager and stop the process relevant to the empty USM.
45.9.6 Remote NE unreachable Due to a deep fading the radio remote NE can be unreachable. In this condition in the USM will appear the following message:
The USM must be closed. In the NES will appear a broken icon and a red bullet:
Wait for the automatic restarting of the Supervision (at the end of the fading conditions). The icon in NES will become whole and the bullet will take the color relevant to the alarms (if any) active in the NE. If the Supervision does not start, close and open again the CT. If the Supervision does not start, switch off and switch on the PC.
45.9.7 Configuration change from 4 QAM to 16 QAM With 16 QAM the max. Tx power must be typically 3 dB below the max Tx power of the 4 QAM.
45.9.8 Quick configuration menu correct use The Quick Configuration menu must be used during the first installation to configure completely the NE and also if some multiple configuration changes must be done (i.e. change of all the tributaries from Framed to Unframed or viceversa for the E1 signal both in the Local and Remote NE). USER MANUAL MAINTENANCE AND UPGRADE 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
447 / 592
45.9.9 Abnormal condition list The abnormal condition list is a summary of the abnormal conditions currently active in the NE due to manual operations such channel protection switching commands (Radio, HST Tx or Mux/Demux), Tx muting, or any loopback (tributary, IDU, ODU). Most of the manual operations listed in the abnormal conditions list may affect the traffic and the normal working condition of the equipment By CT Diagnosis Abnormal condition list Press Refresh to actualize the list each time it is required.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
448 / 592
The local and the remote transceiver(s) can be muted by the following procedure: By CT Views Radio From the left window select Channel #1 or #0 To mute the local transceivers: From the lower right window select on in the Tx Local Mute field apply To mute the remote station transceivers: From the lower right window select on in the Tx Remote Mute field apply N.B. In 1+1 configuration, Tx mute applied either on channel 1 or channel 0 will mute the two channels transceivers at the same time.
Fig. 311. Tx Mute functionality WARNING: The Tx Remote Mute automatically works (on and then off) only if performed on the local NE (i.e. the NE to which the CT is connected). When a remote Tx mute is executed, the EC changes the channel in monodirectional way, in order to have the possibility to send the command to remove the mute. If the Network Element has been restarted after a MUTE, there is no more possibility to setup the channel, because the remote address is not known, and, any case, to setup the channel a bidirectional communication is needed. The only way to remove the MUTE command is with local CT or from a remote CT which can reach the Network Element through another supervisory interface.
Interferences investigation: In order to verify that the local equipment is not receiving a foreign signal as a frequency interference, Tx mute the remote station transceivers and check that the local current received level is < 95 dBm. For additional information refer to the handbook Interference investigation procedure, which describes in detail how to test the radio hop in order to find possible interferences.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
449 / 592
45.9.11 Tributaries 17 to 32 visible in 16E1+Ethernet configuration In an 16E1+ Ethernet type configuration, operator may choose a 32 E1 frame structure capacity. In this case, the relevant 17 to 32 tributaries bandwidth will be dedicated to the two User Ethernet ports Nevertheless, tributaries 17 to 32 might show in the line interface CT view as well as in the Loopback view. Since they do not physically exist, operator must ignore the lines dedicated to tributaries 17 to 32, in the line interface view as well as in the loopback view.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
450 / 592
In general, an IDU unit can be replaced: a) for spare part stock management: b) to check periodically the functionality of spare parts present in the spare part stock
or, during corrective maintenance: to replace a faulty (or suspected faulty) unit with the correspondent spare part to restore the suspected faulty unit (after its successful replacement with a spare unit during corrective maintenance) to verify that it is really faulty.
Please refer to Fig. 305. on page 433 , for the position of this step inside the corrective maintenance general flowchart. Tab. 70. herebelow lists the specific procedures, according to the unit type. These procedures are particularly detailed in order to: avoid injuries to personnel (electric safety) avoid damages to the equipment and the spare parts avoid, as far as possible, traffic interruptions or degrade. Tab. 70. IDU unit replacement procedures UNIT IDU MAIN unit (CH1) IDU EXTENSION unit (CH0) FLASH CARD (housed on MAIN unit) PARAGRAPH 45.10.1 45.10.2 Chapter 46 PAGE 452 456 465
N.B.
All these procedures are based, for both 1+0 and 1+1 configurations, on the equipment interconnection diagrams depicted in para.32.2 on pages 331 to 337 . Please make reference to the equipment interconnection diagram corresponding to your system actual layout.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
451 / 592
Flash Card
possible additional identification label of the upgrade kit (see point [14] on page 475)
Identification label
Fig. 313. Details for IDU MAIN unit or FLASH CARD replacement General warnings: Screw fixing In all described operations, the screw tightening torque must be:
452 / 592
Procedure:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
[1]
Preliminary operations for 1+1 configurations: Before removing the defective IDU MAIN unit, carry out following operations (operations by Craft Terminal possible if CT working): results on main traffic and services
substep
operation by CT enable Force on CH0 Extensions RPS switch if set as Revertive, set RPS protection scheme as No Revertive enable Force on CH0 Extensions TPS switch if set as Revertive, set TPS protection scheme as No Revertive
[1]A
[1]B
[1]C
enable Force on CH0 Extensions EPS switch if set as Revertive, set EPS protection scheme as No Revertive (N.B.)
N.B.
in case Data plugin is present, this implies the loss of tributary Ethernet traffic on both NEs, that cannot be avoided
[2] [3]
If the local Craft Terminal is connected, perform the logoff, then switch it off On the unit identification label present at unit rear side (see Fig. 313. on page 452) read the unit Logistical Item (read also notes in point [14] on page 475, for the possible additional identification label of the upgrade kit) Get a spare unit with the same Logistical Item (see para.43.3.5 on page 419 for general cautions). N.B. If, according to the spare part policy described in para.43.3.3 point a ) on page 418 : the unit to be replaced is equipped with optional plugin(s) (1732xE1 plugin, or Audio + User Service Channel plugin, or Data plugin) and the spare unit is not equipped with such plugin(s), that are instead available as separate upgrade kits you must at first install the spare plugin(s) into the spare IDU Main unit basic, as described in para.47.1 on page 469 (obviously the described unit deinstallation and reinstallation steps do not apply). Disconnect following cables from the front panel of the IDU MAIN unit to be replaced, in the recommended order: tributaries cables services cables Notes: before removing cables ensure they are labeled in (1+1) configurations, do not remove cables on the IDU EXTENSION unit. In this way, the tributary and user service channels traffic interruption is avoided (it continues on channel 0 through the IDU EXTENSION unit), with exception of tributary Ethernet traffic, if any
[4]
[5]
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
453 / 592
[6]
Turn off the front panel power switch (position O, see Fig. 313. on page 452):
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
[7]
of the IDU MAIN unit to be replaced of the IDU MAIN spare unit
if possible, switch off the circuit breaker that gives power supply to the cable connected to the IDU MAIN unit to be replaced. Disconnect all remaining cables from the front panel of the IDU MAIN unit to be replaced, in the recommended order: IDUODU cable only in case of 1+1 configurations: SCSI 1+1 interconnection cable between IDU Main and Extension units power supply cable all other remaining cables, if any Note: before removing cables ensure they are labeled
[8]
SAFETY RULES If operation indicated in previous point [7] has not been carried out, a TNV2 (battery) voltage could be present on Station Battery input (cable side); do not touch the pins when unplugged. DANGER: Possibility of personal injury. Short circuiting, low-voltage, low-impedance, DC circuits can cause severe arcing that can result in burns and/or eye damage. Remove rings, watches, and other metal jewelry before working with primary circuits. Exercise caution to avoid shorting power input terminals. [9] Uninstall the IDU MAIN unit to be replaced and place it on the workbench
[10] Wear the antistatic protection armlet and connect its termination to a grounded structure (see Fig. 1. on page 36). ATTENTION (caution to avoid equipment damage) this avoids the possible damage of the electronic devices for electrostatic discharges [11] Carry out the following operations on the IDU MAIN defective unit (see Fig. 313. on page 452): remove the Flash Card cover extract the Flash Card (it will be mounted in the spare IDU Main unit) restore the Flash Card cover
[12] Carry out the following operations on the IDU MAIN spare unit (see Fig. 313. on page 452): remove the Flash Card cover insert the Flash Card you have extracted from the IDU MAIN defective unit in previous step [11] restore the Flash Card cover
[13] Now you can take off the antistatic protection armlet [14] Install the IDU MAIN spare unit
454 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
[15] Reconnect following cables to the front panel of the new IDU MAIN unit, exactly as they were connected before the faulty unit was extracted, in the following order: only in case of 1+1 configurations: SCSI 1+1 interconnection cable between IDU Main and Extension units IDUODU cable power supply cable CTNE cable N.B. SAFETY RULES: see previous point [8]
[16] if switched off in step [7] on page 454, switch on the circuit breaker giving power supply to the cable connected to the new IDU MAIN unit [17] Turn on power on the new IDU MAIN unit (position I, see Fig. 313. on page 452) [18] Wait for the unit configuration (about 2 minutes) [19] Switch on CT, start 1320CT, login and enter NE supervision [20] Additional operation for 1+1 configurations: operation by CT disable Force on CH0 Extensions RPS switch Note: results on main traffic and services no alarms/errors on both NEs
the commands Force on Extensions TPS and EPS switches [set in previous steps [1]B and [1]C on page 453] are lost due to the EC reset for IDU MAIN unit switch off/on
[21] Reconnect tributaries and services cables exactly as they were connected before the faulty unit was extracted [22] Check the system status using LED visual inspection and through the Craft Terminal [23] If necessary, set TPS/RPS/EPS protection scheme as Revertive. Note that TPS and RPS protection scheme setting to Revertive is not error free. [24] Flash Card identifier label affixing Please read para.13.7.2.2 on page 94. If the inserted IDU MAIN spare unit has no Flash Card identifier label sticked on it or the label does not match the flash card effectively inserted, put a label with the correct information (if not available, create a label writing the information on a selfadhesive sticker). End of IDU MAIN unit replacement procedure
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
455 / 592
ON/OFF switch
possible additional identification label of the upgrade kit (see point [14] on page 475) Fig. 314. Details for IDU EXTENSION unit replacement General warnings: Screw fixing In all described operations, the screw tightening torque must be:
Identification label
456 / 592
Procedure:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
[1]
Preliminary operations: Before removing the IDU EXTENSION defective unit, by Craft Terminal carry out following operations: substep [1]A operation by CT Enable Lockout on CH1 Mains RPS switch Enable Lockout on CH1 Mains TPS switch results on main traffic no alarms/errors on both NEs no alarms/errors on both NEs [1]C Enable Lockout on CH1 Mains EPS switch no alarms/errors on remote NE 12 sec alarm/AIS Sync Loss on local NE results on services no alarms/errors on both NEs no alarms/errors on both NEs no alarms/errors on remote NE 1 sec Slip or AIS on local NE
[1]B
[2]
On the unit identification label present at unit rear side (see Fig. 314. on page 456) read the unit Logistical Item (read also notes in point [14] on page 475, for the possible additional identification label of the upgrade kit) Get a spare unit with the same Logistical Item (see para.43.3.5 on page 419 for general cautions). N.B. If, according to the spare part policy described in para.43.3.3 point a ) on page 418 : the unit to be replaced is equipped with the optional 1732xE1 plugin and the spare unit is not equipped with such a plugin, that is instead available as separate upgrade kit you must at first install the spare plugin into the spare IDU Extension unit basic, as described in para.47.1 on page 469 (obviously the described unit deinstallation and reinstallation steps do not apply). Disconnect following cables from the front panel of the IDU EXTENSION unit to be replaced in the recommended order: tributaries cables services cables Notes: before removing cables ensure they are labeled do not remove cables on the IDU MAIN unit. In this way, the tributary and user service channels traffic interruption is avoided (it continues on channel 1 through the IDU MAIN unit)
[3]
[4]
[5]
Turn off the front panel power switch (position O, see Fig. 314. on page 456): of the IDU EXTENSION unit to be replaced of the IDU EXTENSION spare unit
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
457 / 592
[6]
[7]
Disconnect all remaining cables from the front panel of the IDU EXTENSION unit to be replaced, in the recommended order: IDUODU cable SCSI 1+1 interconnection cable between IDU Main and Extension units power supply cable Note: before removing cables ensure they are labeled SAFETY RULES If operation indicated in previous point [6] has not been carried out, a TNV2 (battery) voltage could be present on Station Battery input (cable side); do not touch the pins when unplugged. DANGER: Possibility of personal injury. Short circuiting, low-voltage, low-impedance, DC circuits can cause severe arcing that can result in burns and/or eye damage. Remove rings, watches, and other metal jewelry before working with primary circuits. Exercise caution to avoid shorting power input terminals.
[8] [9]
Uninstall the IDU EXTENSION unit to be replaced Install the IDU EXTENSION spare unit
[10] Reconnect the following cables to the front panel of the new IDU EXTENSION unit, exactly as they were connected before the faulty unit was extracted, in the recommended order: SCSI 1+1 interconnection cable between IDU Main and Extension units IDUODU cable power supply cable N.B. SAFETY RULES: see previous point [7]
[11] if switched off in step [6] on page 458, switch on the circuit breaker giving power supply to the cable connected to the new IDU EXTENSION unit. [12] Turn on power on the new IDU EXTENSION unit (position I, see Fig. 314. on page 456) [13] Wait for the unit configuration (about 2 minutes)
458 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
if possible, switch off the circuit breaker that gives power supply to the cable connected to the IDU EXTENSION unit to be replaced.
substep
operation by CT
[14]A
[14]B
Disable Lockout on CH1 Mains RPS switch Disable Lockout on CH1 Mains TPS switch
[14]C
[15] Reconnect tributaries and services cables exactly as they were connected before the faulty unit was extracted [16] Check the system status through LED visual inspection and through the Craft Terminal End of IDU EXTENSION unit replacement procedure
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
459 / 592
b)
This procedure is particularly detailed in order to: avoid injuries to personnel (EMF safety) avoid damages to the equipment and the spare parts avoid, as far as possible, traffic interruptions or degrade. General warnings: ODU unit uninstallation and installation In all described operations, when it is necessary to uninstall the faulty ODU and install the spare ODU, please refer to possible additional instructions given in the Installation Handbook. Microwave radiations (EMF norms) SAFETY RULES When operating on the antenna pole, strictly follow cautions stated in para.51.3.8 on page 507 . In particular, if ODU is powered on from IDU, do not stand on the antenna axis and be aware of the compliance boundaries stated in Tab. 73. on page 508 Procedure: [1] Get a spare ODU unit or, in case of ODU with external diplexer, a spare TRANSCEIVER box: with the same Frequency Band and the same Frequency Shifter and with the same or compatible Logistical Item of the ODU unit or TRANSCEIVER box to be replaced. Preliminary operations for 1+1 configurations: Before replacing the ODU, make sure that the traffic is transmitted over the other channel. To do that, if ODU to be replaced is that of: [3] CH1 (ODU connected to IDU MAIN unit), carry out steps [1]A to [1]C on page 453 CH0 (ODU connected to IDU EXTENSION unit), carry out steps [1]A to [1]C on page 457
[2]
Switch off the ODU by using the ON/OFF switch of the relevant IDU unit: for channel 1, operate on MAIN unit (position O, see Fig. 313. on page 452 ) for channel 0, operate on EXTENSION unit (position O, see Fig. 314. on page 456 ) this avoids a possible unrecoverable unknown condition of the spare ODU, when ODU will be switched on in next step [9]
WARNING:
460 / 592
[4]
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
If present, remove the solar shield (see Fig. 46. on page 120 and Fig. 47. on page 121) Disconnect the IDUODU cable at ODU side Change the ODU. NOTES: in case of ODU configurations 1+1 with coupler, use lever shown in Fig. 296. on page 417; in case of 78 GHz ODUs: a) remove the faulty TRANSCEIVER box in the following way (refer to Fig. 47. on page 121): 1) leave the BRANCHING box attached to antenna or coupler, i.e. do not open levers (B) unblock the four levers (A) and separate gently the faulty TRANSCEIVER box from the BRANCHING box verify the coupling between TRANSCEIVER and BRANCHING boxes (see para.14.7.4.2 on page 124), i.e. if the TRANSCEIVER boxs (D) (TX) is coupled to the: BRANCHING boxs (B) (HIGH FREQ) or BRANCHING boxs (C) (LOW FREQ)
[5] [6]
2)
3)
b)
install the spare TRANSCEIVER box in the following way: 4) 5) 6) verify the presence and correct positioning of the ORING on the spare TRANSCEIVER box (see Fig. 49. on page 123) gently couple the spare TRANSCEIVER box on the BRANCHING box in the same position you have verified in step 3 ) above fix the spare TRANSCEIVER box to the BRANCHING box using the four levers (A) (refer to Fig. 47. on page 121)
Reconnect the IDUODU cable at ODU side If was present, mount the solar shield that was removed in previous step [4] Switch on the ODU by using the ON/OFF switch (position I of the relevant IDU unit (MAIN or EXTENSION unit) that has been switched off in previous step [3] .
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
461 / 592
CH1 (ODU connected to IDU MAIN unit), carry out following operations: substep [10]A [10]B [10]C operation by CT disable Force on CH0 Extensions RPS switch disable Force on CH0 Extensions TPS switch disable Force on CH0 Extensions EPS switch results on main traffic and services no alarms/errors on both NEs no alarms/errors on both NEs no alarms/errors on both NEs
CH0 (ODU connected to IDU EXTENSION unit), carry out steps [14]A to [14]C on page 459
[11] If necessary, set TPS/RPS/EPS protection scheme as Revertive. Note that TPS and RPS protection scheme setting to Revertive is not error free. [12] Check the system status through LED visual inspection and through the Craft Terminal. End of ODU replacement procedure
462 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
[10] Additional operations for (1+1) configurations: by CT, remove forced traffic condition set in previous step [2] To do that, if replaced ODU is that of:
Refer to Fig. 305. on page 433, for the position of this step inside the corrective maintenance general flowchart. 45.12.1 Faulty unit sending back to repair center The complete faulty unit (complete ODU assembly, or TRANSCEIVER box in case of 78 GHz ODU, or IDU Main or Extension Unit including plugin, if any) must be sent back to the AlcatelLucent repair center. Faulty unit repair must be done by authorized repair centers only. 45.12.2 Repair Form filling To facilitate repair operation, data on the faulty unit must be reported on the form shown in Fig. 315. on page 464. The repair form must be filledin with as much data as possible and returned to AlcatelLucent together with the faulty unit.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
463 / 592
Fill in this form and affix it to the faulty unit to be returned to AlcatelLucent
CUSTOMER NAME ORDER NUMBER/CONTRACT NUMBER
SITE
BRANCH/UNIT/COUNTRY
SYSTEM/EQUIPMENT
PRODUCT RELEASE
STATION/RACK
SUBRACK
SLOT
MNEMONIC
SERIAL NUMBER
FAULT PHASE
INSTALLATION / TURN ON CLEAR FAULT
PRESUMED CAUSE
INTERNAL
MAINTENANCE
TEMPERATURE FAULT
OTHER
NAME OF SENDER
COMMENTS
PROCESSING
NO FAULTS FOUND A STANDARD REPAIRING BD SUBSTITUTED QUALITY ALERT I SX NOTE : LETTERS ARE FOR FACTORY USE NOT REPAIRABLE (REJECTED) M UPGRADE I MECHANICAL V1 SOLDERING / WIRING C
FAULTS DETECTED
COMPONENT FL PRINTED CIRCUIT BOARD V1 CORROSION V3 OTHER DIRT V2 ADJUSTMENT P
COMMENTS
DATE
REPAIRING NUMBER
REPAIRING CENTRE
464 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
REPAIR FORM
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
b)
In both cases, it is expected that in the plant, the following backup information is always available for each specific NE: [1] the MIB backup file To know how to create a MIB backup file, refer to Chapter 214 on page 301. the .qcml configuration file To know how to create a .qcml configuration backup file, refer to the Procedure for .qcml file backup on page 65 .
[2]
Please, refer to para.12.6.7 on page 65 for details. SUGGESTION Use one IDU Main unit of the sparepartstock as an offline service station (non connected to the network) to manage the content of Flash Cards, before using them as spare parts.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
465 / 592
b)
466 / 592
General warnings: Screw fixing In all described operations, the screw tightening torque must be:
[2]
[3]
[4]
Wear the antistatic protection armlet [see point b ) on page 36] and connect its termination to a grounded structure ATTENTION (caution to avoid equipment damage) this avoids the possible damage of the electronic devices for electrostatic discharges
[5]
Remove the Flash Card cover (see Fig. 313. on page 452 ). Store tidily cover and screws for their successive mount Extract the faulty Flash Card from the IDU Main Unit, verify again that its type is equal to that of the spare Flash Card and insert the spare Flash Card (refer to Fig. 34. on page 94 for Flash Card profile and insertion direction)
[6]
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
467 / 592
[7]
[8]
a generic spare Flash Card, proceed with following step [8] a NEspecific spare Flash Card, proceed with following step [9]
If you have inserted a generic spare Flash Card, carry out following checks and operations by CT: 1) verify the SW COMMITTED and STANDBY versions in the Flash Card, as described in point [2] on page 63 : if the SW COMMITTED version is equal to that previously present with the replaced flash card, proceed with substeps 2 ) and 3 ) below if the SW COMMITTED version is not equal to that previously present with the replaced flash card, but the STANDBY version is equal, proceed with the swap between the SW COMMITTED and STANDBY versions, as described in para.48.5 on page 492 . Then, proceed with substeps 2 ) and 3 ) below. if neither the SW COMMITTED nor the STANDBY versions are equal to that previously present with the replaced flash card, proceed with downloading and activation of the target SWP version, as described in chapter 48 on page 485 . Then, proceed with substeps 2 ) and 3 ) below.
2)
launch the TCO Suite SetUp Tool , as described in para.32.3.9 on page 345 In the screen of Fig. 244. on page 346 , click on button Open Configuration . When the file selection window opens requiring a configuration_name.qcml file to be opened, specify the NEs specific file [mentioned in point [2] on page 465 ]. The window in Fig. 245. on page 347 will appear. Then, clicking repeatedly on Next buttons (without any other actions, or just checking configuration screens, if you like), reach Step L on page 368 and click on Finish button. In this way the .qcml configuration data are loaded in the Flash Card data base. carry out MIB data restore and activation [using NEs specific MIB backup file mentioned in point [1] on page 465 ] as shown in MIB Restore in Fig. 209. on page 301 (from operative point of view, refer to para.28.3.2 and 28.3.3 on page 255). In alternative to activation by SW, carry out the Equipment Controller HW Reset, pushing the suitable button on IDU MAIN Unit (see Fig. 76. on page 170).
3)
Now, you can reconnect the NE to the supervision network, and proceed with following step [9] [9] Restore the Flash Card cover removed in previous step [5]
[10] Now you can take off the antistatic protection armlet [11] Carry out functional checks by Craft Terminal. End of procedure
468 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
After two minutes, login the NE by CT. Now, if you have inserted:
This chapter details all phases necessary to carry out the following hardware upgrades: Installation of plugins, para.47.1 below upgrade 9400AWY system from 1+0 to 1+1 configuration, para.47.2 on page 476 install a new Flash Card to improve system capacity, para.47.3 on page 479
3DB16086AAXX 32E1 ON SITE UPGRADE KIT 3DB16130AAXX DATA ENHANCED ON SITE UPGRADE KIT (4 x 10/100/1000 baseT ports) in alternative
Notice that: in 1+0 configuration, you can equip any of the plugin types into the IDU Main unit in 1+1 configuration, you can upgrade the system in one of the following ways: upgrade from max 16 to max 32 E1 tributaries: you must install the 1732 E1 PLUGIN into both the: IDU Main unit IDU Extension unit upgrade to Ethernet tributaries: you must install the DATA ENHANCED ON SITE UPGRADE KIT into the IDU Main unit only upgrade for AUDIO + USER SERVICE CHANNEL functionalities: you must install the AUDIO + USER SERVICE CHANNEL UPGRADE KIT into the IDU Main unit only.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
469 / 592
47.1.2 Procedure Drawings used to show operations are relevant to the IDU Main unit. Operations to be carried out for IDU Extension unit are exactly the same. Screw fixing In all described operations, the screw tightening torque must be:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
[2] [3]
470 / 592
[4]
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Rotating the removed fixing brackets into both the suitable covers side holes, slide the box cover out from the box base, as shown in Fig. 317. :
Fig. 317. Release and sliding out the cover [5] Wear the antistatic protection armlet and connect its termination to a grounded structure (see Fig. 1. on page 36). ATTENTION (caution to avoid equipment damage) this avoids the possible damage of the electronic devices for electrostatic discharges
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
471 / 592
[6]
Fig. 318. Removing the cover [7] Fig. 319. : according to the plugin to be installed, dismount the metal plate (fixed by two screws) which closes the plugin devoted hole. Take the two removed screws for their fixing. plate to remove for AUDIO + USER SERVICE CHANNEL plugin plate to remove for TRIBUTARY plugin
472 / 592
[8]
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 320. shows in details the connectors and columns for plugin fixing by screws
connectors for plugin connector for plugin Fig. 320. Connectors and columns for plugin fixing by screws [9] Insert the plugin in its connector(s) depicted in previous Fig. 320. , and fix it: on the PCB using the 2 or 3 screws on the suitable columns depicted in previous Fig. 320. to the front panel by the 2 screws or the screw columns
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
473 / 592
Details of Audio + User Service Channel plugin installed Fig. 321. Plugin insertion and fix
474 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
[10] Reinsert the cover (reverse operation of Fig. 318. on page 472) [11] Slide in the cover (reverse operation of Fig. 317. on page 471. The fixing brackets use is not necessary) [12] Now you can take off the antistatic protection armlet [13] Fix the cover and, if they were present, mount both fixing brackets (reverse operation of Fig. 316. on page 470) [14] Upgrade kit identification label After this upgrading, the Unit identification label placed on the box rear side [position (C) in Fig. 21. on page 70 for the IDU Main Unit, and in Fig. 23. on page 77 for the IDU Extension Unit] is no longer right to correctly identify the assembly as a whole. This could impact on sparepartstock management and maintenance. For this reason: if the upgrade kit is supplied with a suitable selfadhesive label (under study), stick it just on side of that already existing otherwise create a label writing the upgrade kit P/N on a selfadhesive sticker, and stick it just on side of that already existing.
additional identification label of the upgrade kit existing identification label of the basic unit [15] Reinstall the unit [16] Complete upgrade operations with: system cabling (it is different from that previous to upgrading). Refer to the Installation Handbook, according to the new hardware configuration system data redefinition (it is different from that previous to upgrading), carrying out Quick Configuration procedure by Craft Terminal (details in para.32.3.7 on page 343). commissioning procedure, to check the new interface, (details in Chapter 32 Commissioning on page 329).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
475 / 592
b)
N.B.
This procedure is particularly detailed in order to: avoid injuries to personnel (EMF safety) avoid damages to the equipment avoid, as far as possible, traffic interruptions or degrade. General warnings: Microwave radiations (EMF norms) SAFETY RULES When operating on the antenna pole, strictly follow cautions stated in para.51.3.8 on page 507 . In particular, if ODU is powered on from IDU, do not stand on the antenna axis and be aware of the compliance boundaries stated in Tab. 73. on page 508
476 / 592
47.2.2 Procedure
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
[1]
For both stations, ascertain to have all materials necessary for the HW upgrade, at IDU and ODU levels, as well as necessary installation materials. For materials necessary for hardware upgrade, please refer to the: para.13.1 on page 68 (standard materials for IDU) Installation Handbook (ODU provisioning and additional installation materials for IDU and ODU) PHASE [A] : OPERATIONS ON FIRST STATION
[2]
Preliminary operations to be done only in case of 1+0 system not equipped with the Protection boxes: a) b) switch off the IDU MAIN unit and disconnect all tributary (with the exception of Ethernet, if any) and services cables from its front panel using the instructions given in the Installation Handbook: install the E1 Protection box and the Services Protection box install the IDU EXTENSION unit N.B. connect its power supply plug to the station battery, but ascertain that its ON/OFF switch is in OFF position and leave it in OFF position till step [9] connect the IDU MAIN and EXTENSION units to the E1 Protection box and the Services Protection box connect the E1 Protection box and the Services Protection box to the station DDF switch on the IDU MAIN unit, connect the Craft Terminal, switch it on, start 1320CT and login the NE (details in para.22.5.2 on page 173) and verify the link functionality
c)
[3]
If not connected, connect the Craft Terminal, switch it on, start 1320CT and login the NE (details in para.22.5.2 on page 173) Using the instructions given in the Installation Handbook , install the second ODU; for general information, make reference to Fig. 4. on page 41). Warning: in case of 1+1 ODU configuration: a) b) with two antennas, install the second ODU with its own antenna with 1+1 coupler: if the coupler is already installed, fix the second ODU to the coupler, then go to step [5] if the coupler is not installed, carry out following operations (full link unavailability from substep 3 ) till substep 6 ): 1) 2) 3) 4) 5) 6) 7) by Craft Terminal, disable ATPC on CH1 (if enabled): see para.26.4.1 on page 239 carry out NE logoff (details in para.22.5.3 on page 180) switch off IDU MAIN unit (CH1) disconnect ODU CH1 from antenna, connect the 1+1 coupler to the antenna, and connect the ODU CH1 to the 1+1 coupler switch on IDU MAIN unit (CH1) wait until system restart completion, then start 1320CT and login the NE (details in para.22.5.2 on page 173) by Craft Terminal, enable ATPC on CH1 (if necessary): see para.26.4.1 on page 239
[4]
[5]
Only in case of 1+0 system already equipped with the Protection boxes: install the CH0 IDU EXTENSION unit and connect it to the E1 Protection box and the Services Protection box, using the instructions given in the Installation Handbook N.B. connect its power supply plug to the station battery, but ascertain that its ON/OFF switch is in OFF position and leave it in OFF position till step [9] 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
477 / 592
[6]
[7]
Connect the IDUODU cable (between the CH0 Extension IDU and the second ODU), using the instructions given in the Installation Handbook By Craft Terminal carry out the following operations: 1) 2) 3) 4) Configuration System Setting NE Configuration 1+1 Configuration: see para.23.4.1 on page 210 This configuration change causes the JUSM loss, so that you must login again the NE (details in para.22.5.2 from page 173) Set EPS (Mux/Demux Protection) Lockout: see para.29.1 subpara.29.1.2 on page 259 WARNING: this operation is not error free Set CH0 Tx Power as follows: with reference to Fig. 140. on page 238 : select Channel #0 click on RTPC & ATPC insert value in Tx Power(dBm) field Apply WARNING: the CH0 Rx remains at 0 till the NE restart carried out in substep [10]4 ) below Note: this step is not necessary in HSB configuration, where frequency is set automatically: Set CH0 Tx Frequency as follows: with reference to Fig. 136. on page 235 : select Channel #0 click on Frequency insert value in Tx Frequency(kHz) field Apply
[8]
5)
[9]
[10] By Craft Terminal carry out the following operations: 1) 2) Set CH0 Frequency Shifter as follows: with reference to Fig. 136. on page 235 : select Channel #0 insert value in Shifter field Apply Note: this step is necessary in FD configuration only: Set again CH0 Frequency as follows: with reference to Fig. 136. on page 235 : select Channel #0 click on Frequency insert value in Tx Frequency(kHz) field Apply WARNING: the CH0 Rx remains at 0 till the NE restart carried out in substep [10]4 ) below Remove EPS (Mux/Demux Protection) Lockout: see para.29.1 subpara.29.1.2 on page 259 WARNING: this operation is not error free Restart NE: see para. 28.2 on page 252 PHASE [B] : OPERATIONS ON SECOND STATION [11] Repeat the previous steps in the other station of the radio link PHASE [C] : OPERATIONS ON THE LINK N.B. These operations are meant for the radio link as a whole, and imply full link unavailability.
3) 4)
[12] In case of ODU configuration with two antennas, carry out the alignment of the second ODU antenna (N.B.) [13] Carry out the CH0 functionality test (N.B.). N.B. For details on commissioning procedures, please refer to the Chapter 32 on page 329. PHASE [D] : NE DATA SAVE [14] Save data of both NEs as explained in para.12.6.8 on page 65. End of procedure
478 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Connect the 100pin cable to both IDU MAIN and EXTENSION units, using the instructions given in the Installation Handbook
47.3.1 Introduction Please refer to para.13.7 on page 93 for detailed information on Flash Card position, types and identification. N.B. To replace a Flash Card with the same type, for maintenance purpose, please refer to para.46.2 Flash Card replacement procedures on page 466.
In general, the Flash Card upgrade must be done together with HW changes, e.g. changing the system capacity from 16xE1 to 32xE1 requires to: change: the existing Flash Card 32Mb 4/16 QAM FLASH CARD with the 64Mb 16 QAM FLASH CARD corresponding to the change of the: Software Label from 32Mb 4/16 QAM to 64Mb 16 QAM
This paragraph explains how to do this operation. and install (if not yet present) the 1732xE1 PLUGIN in the IDU MAIN UNIT, as well in the IDU EXTENSION UNIT in case of 1+1 systems; to carry out this operation, please refer to para.47.1 Installation of plugins on page 469.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
479 / 592
47.3.2 Summary procedure for both stations This example is for changing the existing Flash Card 16E1/32Mbps DATA 4/16QAM with the 32E1DS1 4/16QAM. Adapt it to the actual change you must do. Tab. 72. Flash card upgrade carried out by one operator only for both stations STEP 1 IN STATION B Current configuration Backup Flash card replacement. This requires, in typical condition (rack installation), to switch the IDU off and disconnect cables; otherwise, if the installation condition allows to replace the flash card without disconnecting cables, the NE supports an hot replacement IDU switchon (after recabling) or NE Restart (in case of hot replacement), Start Supervision & Open USM (empty due to the nonpreconfigured flash card) Check that the SW Key is the new one MIB Restore / Activation, Start Supervision & Open USM Quick configuration. In this case (=dialogue with ODU already established), the shifter and TX frequency are allowed to be set also by Quick config. The NE type is modified to 32E1 and the Tributary config is set again to 16E1 (not to 32E1 as desired) Reopening USM Go to STATION A and carry out operations detailed in column STEP 2 Open Local and Remote USM CHANGE REMOTE CONFIG BY SYSTEM SETTING FROM 16E1 TO 32E1 the traffic is CAPACITY impacted for CHANGE LOCAL CONFIG BY SYSTEM about 1 min SETTING FROM 16E1 TO 32E1 CAPACITY STEP 2 IN STATION A (in series to step1) idem notes
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
idem
idem
idem idem
idem
Following paragraphs are given just for Operators who need to know what to do in detail for: Ordering the new Flash Card Installation of a new Flash Card fully configured in factory Installation of a new Flash Card not configured in factory
480 / 592
Whenever the Base configuration of the 9400AWY NE must be upgraded, Customer must order a new Flash Card: of the type consistent with the equipment configuration he wants: see Tab. 23. on page 93 , and preferably, already set by AlcatelLucent Factory: with the same SWPversion present in the 9400AWY system to be upgraded, already present in the FlashCards SW committed version bank with the same NE network routing data (and other configuration data) of the system to be upgraded (for this purpose, Customer can save the NEs .qcml configuration file on floppydisk as explained in the Procedure for .qcml file backup on page 65 , and give it to AlcatelLucent Factory). N.B. with the same MIB of the system to be upgraded (for this purpose, Customer can save the MIB on floppydisk as explained in chapter 214 on page 301 and give it to AlcatelLucent Factory). N.B. these options could be subject to possible special contractual terms.
N.B.
To install a new Flash Card fully configured in factory carry out operations in para.47.3.4 on page 482. To install a new Flash Card not configured in factory carry out operations in para.47.3.5 on page 483.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
481 / 592
47.3.4 Installation of a new Flash Card fully configured in factory General warnings: Screw fixing In all described operations, the screw tightening torque must be:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
[10] carry out functional checks by Craft Terminal [11] save NE data as explained in para.12.6.8 on page 65 ( creation of MIB backup file and .qcml backup file ) [12] as the new Flash Card is supplied with a selfadhesive label containing the Flash Card Software Label, get and stick it over the older one [see (A) in Fig. 21. on page 70 ); (N.B. if possible, remove the older selfadhesive label before sticking the newer). End of procedure
482 / 592
General warnings: Screw fixing In all described operations, the screw tightening torque must be:
[2]
[3]
2)
[4] [5]
carry out NE logoff isolate the NE from the supervision network N.B. Before to isolate the system from the supervision network, inform the supervision center: if (from the supervision point of view), there are other NEs cascadeconnected to it (and without supervision ring network) they will be isolated, too.
[6]
wear the antistatic protection armlet [see point b ) on page 36 ] and connect its termination to a grounded structure ATTENTION (caution to avoid equipment damage) this avoids the possible damage of the electronic devices for electrostatic discharges
[7]
remove the Flash Card cover (see Fig. 313. on page 452 ). Store tidily cover and screws for their successive mount extract the old Flash Card from the IDU Main Unit and insert the new one (refer to Fig. 34. on page 94 for Flash Card profile and insertion direction) restore the Flash Card cover removed in step [7] above (screw tightening torque as specified above) 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
[8]
[9]
483 / 592
[10] now you can take off the antistatic protection armlet [11] login the NE and, by Craft Terminal, perform following operations: 1) verify the SW COMMITTED version in the Flash Card, as described in point [2] on page 63. If not V2.1.0, proceed with V2.1.0 downloading and activation, as described in chapter 48 on page 485. launch the TCO Suite SetUp Tool , as described in para.32.3.9 on page 345. In the screen of Fig. 244. on page 346 , click on button Open Configuration . When the file selection window opens requiring a configuration_name.qcml file to be opened, specify the NEs specific file you have saved in previous step [3]1 ) on page 483. The window in Fig. 245. on page 347 will appear. Then, clicking repeatedly on Next buttons (without any other actions, or just checking configuration screens, if you like), reach Step L on page 368 and click on Finish button. In this way the .qcml configuration data are loaded in the Flash Card data base. carry out MIB data restore and activation [using NEs specific MIB backup file you have saved in previous step [3]2 ) on page 483] as shown in MIB Restore in Fig. 209. on page 301 (from operative point of view, refer to para.28.3.2 and 28.3.3 on page 255). In alternative to activation by SW, carry out the Equipment Controller HW Reset, pushing the suitable button on IDU MAIN Unit (see Fig. 76. on page 170). In this way the MIB configuration data are loaded in the Flash Card data base. About two minutes are necessary for the supervision process to get data from the new flash card.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
2)
3)
[12] carry out the Quick Configuration procedure (interactive) by Craft Terminal [details in para.32.3.7 on page 343 ], to change the system capacity [13] connect the system to the supervision network [14] carry out functional checks by Craft Terminal [15] save NE data as explained in para.12.6.8 on page 65. [16] as the new Flash Card is supplied with a selfadhesive label containing the Flash Card Software Label, get and stick it over the older one [see (A) in Fig. 21. on page 70 ); (N.B. if possible, remove the older selfadhesive label before sticking the newer). N.B. In alternative, if an offline IDU MAIN unit is available at Customer premises, the Flash Card can be prepared on it, and then installed on the target system as described in previous para.47.3.4 on page 482. End of procedure
484 / 592
This chapter details all phases necessary to download inside the NE equipment environment, and then activate, a SWP having a version greater than that presently loaded in the NEs Flash Card. N.B. N.B. Before starting this procedure, it is suggested to give a look to para.12.6 on page 58. Procedures described in this chapter are carried out with the PC connected to the NE.
48.1 Requirements
48.1.1 Craft Terminal The PC, already loaded with the SWP to be downloaded toward the NE (as explained in previous chapter 31 on page 309) must be available as CT (Craft Terminal). 48.1.2 NE state [1] Equipment state equipment must have been previously installed, cabled, powered on and commissioned as described in para.12.6.1 on page 59 the SWPversion present inside the NEs Flash Card must be lower than that of the ECT (refer to para.12.6.3 on page 62 to know how to compare them).
[2]
48.1.3 Operator skills and profile a) In addition to skills stated in para.31.1.2 on page 310, the Operator must be familiar with all the equipment functionalities. The Operators profile must be Administrator or craftPerson (see para.23.6 on page 214).
b)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
485 / 592
The installation phases are: a) b) c) d) e) CT startup, NE login and initial checks SW download to the NE, Activation of the new Software Package on the NE Additional operations for upgrade from V2.1.0 MIB save para.48.3 herebelow para.48.4 on page 487 para.48.5 on page 492 para.48.6 on page 494 para.48.7 on page 494
d)
e) Step 2.
Check SWP versions 2.1.x present in the NE MIB banks, as explained in point [2] on page 63. You must be aware that the SWP download, carried out in the following, will overwrite the current Standby version. In the case you want to maintain such a version, and overwriting the other (i.e. that presently Committed), activate the current Standby version as described in para.48.5 on page 492.
Step 3.
Check the SWP version 2.1.y (y > x) availability for download to the NE, as explained in step 6 ) on page 325. If not available, carry out completely the procedure described in para.31.8 on page 321. Verify also that the version to be downloaded is greater than those present in both the NE MIB current Standby and Committed banks.
486 / 592
Step 1.
Setup Server Access Configuration a) Carry out SW Download Server Access Configuration (Fig. 322. below)
Fig. 322. Server Access Configuration start up b) The following confirmation box appears. Press OK to close it.
c)
The screen of Fig. 323. on page 488 appears, with empty fields. Click on Use System Default button. In this way the systems sets automatically the Address and Port fields, that depend on how the login to the NE has been done: N.B. by F interface: IP address of the LLMAN to download in interface F mode is set by LAN interface: IP address of the PC to download the software in LAN mode is set The UserId and Password present in this screen are relevant to the ftp login, are set automatically with the Use System Default button and have no relationship with those necessary for the NE login.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
487 / 592
Fig. 323. Server Access Configuration setup screen d) Press OK to confirm values and close the window.
488 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Step 2.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 324. Init SW Download startup b) Wait List Sw Package creation ... When action is completed, press Enter to close message window.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
489 / 592
c)
Now select a specific SWP to download on the NE, and press Init download to start it.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
2_1_ 1
2_1_1
e)
f)
N.B.
The software download lasts about 1/2 hour if performed through the F interface, and few minutes if the Ethernet interface is used.
490 / 592
g)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
After the software download completion, by SW Download SW Status (see Fig. 326. on page 492), you can verify that the downloaded SW is present as Stand by version; moreover, clicking on the Software Unit Status button, it is possible to see its components and their version.
V02.01.01
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
491 / 592
Fig. 326. SW Status b) Fig. 327. below: select the Standby SW (1), set Activation (2) in the Software Management Action field, then Apply Action (3)
(1)
V02.01.01
(2)
V02.01.01
(3)
492 / 592
c)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
d)
e)
... and the NE restarts with the new software package. N.B. The JUSM becomes unavailable (the following message appears (click OK to close)
Step 2.
Logoff and ReLogin a) b) Logoff the NE Login the NE and verify, by SW Download SW Status (see Fig. 326. on page 492), that the SW banks have changed their Current Status. once you have downloaded and made active the new SWP in NE environment, do not make the mistake of trying to switch the previos version back to COMMITTED status (for details, read WARNING on page 495 ).
WARNING:
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
493 / 592
2_1_1
(1) (2) Fig. 328. Forced Init download N.B. and the activation of the Stand by V2.1.1 on the NE (para.48.5 on page 492) Obviously, at the end of this procedure, you will have both SW banks with V2.1.1 SWP, and the V2.1.0 SWP has been lost.
Why are there operations required? Starting from AWY V2.1.1, one new SW component has been added (with respect to V2.1.0) in Software Package: for this reason, if the active bank is V2.1.0, the download of SWP in the flash card must be executed in two steps: with the first step (normal download procedure) all SW components known by previous SWP version are downloaded on flash card; new SWP component is known ONLY by SWP 2.1.1, so after the activation of package SWP 2.1.1, it is necessary to download SWP 2.1.1 again (IN FORCED MODE), to transfer the new SW component image onto flash card.
494 / 592
This chapter details all phases necessary to install a new SWP version in the PC environment as well as in the equipment environment in both stations A and B of the radio link, i.e. in the following case: both ECT and equipment (in both stations A and B) are presently running with version V2.1.0 the new SWP V2.1.1 is delivered to Customer by means of the specific SWP CDROM.
Procedure: [1] Preliminary checks and actions on both stations 1) if the former version of 2xFast Ethernet plugin is equipped, it must be removed, and, if envisaged, the new version of 4xGbit Ethernet plugin must be installed; for this purpose, carry out these operations on both stations: a) using the instructions given in the 9400AWY V2.1.0 User Manual: b) c) remove traffic on Fast Ethernet ports disable both Fast Ethernet ports unconfigure the 2xFast Ethernet plugin
phisically disinstall the 2xFast Ethernet plugin and, if envisaged, install the DATA ENHANCED ON SITE UPGRADE KIT, making reference to para.47.1 on page 469 of this manual N.B. ignore the unespected equipment alarm that arises after the installation of the 4xGbit Ethernet plugin (it is not supported by SWP version V2.1.0)
2)
check that no hardware or radio transmission problems are present (with exception of the unespected equipment alarm stated above). Otherwise, solve them before starting upgrade close all Performance Monitoring, analog measurement and BER measurement processes, if any remove all loopbacks as well as all lockout, forced and manual commands on protection schemes, if any do not use functions stated above, or any other action not strictly necessary for the upgrade, until you have completed the SW upgrade of both stations, i.e. not before step [5] on page 496 of this procedure. WARNING: you must be aware that, once you have downloaded and made active the new SWP V2.1.1 in NE environment (at the end of step [3] for station A , and at the end of step [4] for station B), you cannot switch them back to V2.1.0, because there is no backward compatibility between V2.1.1 and V2.1.0 NE data base structures. In case you think you could need to go back to V2.1.0, before next step [2] , i.e. with SWP 2.1.0 running both in PC and NE, prepare a spare Flash Card containing: the SWP 2.1.0 as COMMITTED bank the associated MIB data Restoring this Flash Card in the system is the only way to make downgrade.
3)
4)
5)
6)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
495 / 592
[2]
1) 2)
Requirements: see para.31.1 on page 309 and para.48.1 on page 485. on local PC, carry out the installation of the new SWP version in the ECT environment and the V2.1.1 NE software downloading preparation, as indicated in Chapter 31 from page 309 to page 325 N.B. The Craft Terminal configuration (para.31.9.1 on page 326 ) and the EML construction (para.31.10 on page 327 ) are not considered necessary because relevant data should have already been defined during the CT installation made with SWP 2.1.0.
[3]
V2.1.1 software download and activation on station A 3) connect the CT to the local NE (station A) by the suitable crossconnct Ethernet cable, launch the V2.1.1 Craft Terminal and login the local NE (station A) by: TCO Suite Main Menu Operational & Maintenance 4) carry out the download (from the CT) and the activation of the new SWP version in the NE environment, executing in sequence the operations described in: SW download to the NE, para.48.4 on page 487 activation of the new Software Package on the NE, para.48.5 on page 492 additional operations for upgrade from V2.1.0, para.48.6 on page 494
[4]
V2.1.1 software download and activation on station B 5) by RECT functionality, login the remote NE (station B) and carry out same operations made for station A
[5]
Carry out functional checks on radio link E.g. Performance Monitoring, analog measurement, BER measurement, operations on protection schemes, loopbacks, etc.
[6]
Operations on remote PC (station B) Do not forget to update also the PC(s) present in station B, as done in step [2]2 ) above. End of procedure
496 / 592
From Control Panel select Add/Remove Programs and deinstall the components in the following order: 1) 2) 3) 4) 5) 6) 7) 8) 9) CTNEConfUpd (if present) ALCATEL JUSM Help On Line (for all versions you like to remove) ALCATEL SW Package REG.9400AWY (for all versions you like to remove) ALCATEL Radio Common JUSM (for all versions you like to remove) ALCATEL Q3CTKADDONvX.Y.Z (1320CT) ALCATEL SNMPCTKADDONvX.Y.Z (1320CT) ALCATEL HOLCTKADDONvX.Y.Z (1320CT) ALCATEL CTKvX.Y.Z (1320CT) Alcatel Lower Layers Manager & Tiny Tools
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
497 / 592
a)
END OF SECTION 4
498 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
SECTION 5: APPENDICES
SECTION CONTENT Appendix A SafetyEMCEMFESD norms and equipment labelling It describes the equipment labelling and the norms mandatory or suggested that must be considered to avoid injuries on persons and/or damage to the equipment. Moreover the labels affixed to the IDU and ODU equipment are described. Appendix B TCO suite startup special conditions This Appendix describes some special conditions that may occur during the TCO Suite startup and the countermeasures to take. Appendix C Additional SW installation operations for NE management through the NEs ECT serial port This Appendix explains the operations necessary to allow the NE management through the NEs ECT serial port. Such operations are not necessary if you use TCO Suite and Craft Terminal accessing the NE through its Ethernet interface only. Appendix D General on Ethernet port characteristics and management This Appendix gives summary information that can be useful for the configuration of Ethernet ports. Appendix E ECTEquipment connection via public switched telephone network This Appendix explains the operations necessary to allow the remote connection to the FInterface, from a local PC configurated as ECT, through a switched telephone line of the standard Public Telephone Network. Appendix F Part lists of tool kits Appendix G Documentation guide It contains all information regarding this handbook (purpose, applicability, history) and the Customer Documentation set it belongs to, in particular the list of the handbooks the Operators should have in order to carry out the required operations. Appendix H List of symbols and abbreviations, Glossary of terms Appendix I Customer documentation feedback PAGE
501
511
517
547
553
563
567
575 589
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
499 / 592
500 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Electromagnetic Compatibility (EMC norms) EMC General Norms Installation EMC General Norms Turnon, Tests & Operation EMC General Norms Maintenance
Equipment protection against electrostatic discharges Suggestions, notes and cautions Labels affixed to the 9400AWY equipment
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
501 / 592
Observe safety rules When equipment is operating nobody is allowed to have access inside on the equipment parts which are protected with Cover Plate Shields removable with tools In case of absolute need to have access inside, on the equipment parts when it is operating this is allowed exclusively to service personnel, where for Service Personnel or Technical assistance is meant : personnel which has adequate Technical Knowledge and experience necessary to be aware of the danger that he might find in carrying out an operation and of the necessary measurements to reduce danger to minimum for him and for others. The Service Personnel can only replace the faulty units with spare parts. The Service Personnel is not allowed to repair: hence the access to the parts no specified is not permitted. The keys and/or the tools used to open doors, hinged covers to remove parts which give access to compartments in which are present high dangerous voltages must belong exclusively to the service personnel. For the eventual cleaning of the external parts of the equipment, absolutely do not use any inflammable substance or substances which in some way may alter the markings, inscriptions ect. It is recommended to use a slightly wet cleaning cloth.
The Safety Rules stated in the handbook describe the operations and/or precautions to observe to safeguard service personnel during the working phases and to guarantee equipment safety, i.e., not exposing persons, animals, things to the risk of being injured/damaged. Whenever the safety protection features have been impaired, REMOVE POWER. To cut off power proceed to switch off the power supply units as well as cut off power station upstream (rack or station distribution frame). The safety rules described in this handbook are distinguished by the following symbol and statement:
SAFETY RULES
502 / 592
It is of utmost importance to follow the instructions printed on the labels affixed to the units and assemblies. The labels are fully compliant with International Norms ISO 38461984. The symbols or statements are enclosed in geometric shapes: ISO 38641984.
CONTAINS A SYMBOL STATEMENT INDICATES FORBIDDANCE (WHITE BACKGROUND WHIT RED RIMBLACK SYMBOL OR STATEMENT) IT IS A COMMAND (BLUE BACKGROUNDWHITE SYMBOL OR STATEMENT).
CONTAINS A SYMBOL INDICATES WARNING OR DANGER (YELLOW BACKGROUNDBLACK SYMBOL AND RIM)
CONTAINS A STATEMENT PROVIDING INFORMATION OR INSTRUCTION. (YELLOW BACKGROUNDBLACK STATEMENT AND RIM)
The labels have been affixed to indicate a dangerous condition. They may contain any standardknown symbol or any statement necessary to safeguard users and service personnel against the most common ones, specifically: dangerous electrical voltages harmful optical signals risk of explosion moving mechanical parts heatradiating Mechanical Parts microwave radiations
Pay attention to the information stated in the following, and proceed as instructed The symbols presented in para.51.3.3 through 51.3.8 are all the possible symbols that could be present on AlcatelLucent equipment, but are not all necessarily present on the equipment this handbook refers to.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
503 / 592
51.3.3 Dangerous Electrical Voltages 51.3.3.1 Electrical safety: Labelling The following warning label is affixed next to dangerous voltages (>42.4 Vp; >60 Vdc).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
If it is a Class 1 equipment connected to mains, then the label associated to it will state that the equipment will have to be grounded before connecting it to the power supply voltage, e.g.:
WARNING ! Ground protect the equipment before connecting it to the mains Make sure that power has been cut off before disconnecting ground protection.
51.3.3.2 Electrical safety: general rules carefully observe the specific procedures for installation / turnup and commissioning / maintenance of equipment parts where D.C.. power is present, described in the relevant installation / turnup and commissioning / maintenance documents and the following general rules: a) Personal injury can be caused by 48 V DC. Avoid touching powered terminals with any exposed part of your body. Short circuiting, low-voltage, low-impedance, DC circuits can cause severe arcing that can result in burns and/or eye damage. Remove rings, watches, and other metal jewelry before working with primary circuits. Exercise caution to avoid shorting power input terminals.
b)
504 / 592
51.3.4.1 Labelling and safety instructions This risk is present when batteries are used, and it is signalled by the following label:
Therefore, slits or apertures are made to let air circulate freely and allow dangerous gasses to down flow (batteryemitted hydrogen). A 417IEC5641 Norm. compliant label is affixed next to it indicating that the openings must not be covered up.
51.3.5 Moving Mechanical Parts 51.3.5.1 Labelling and safety instructions The following warning label is affixed next to fans or other moving mechanical parts:
Before carrying out any maintenance operation see that all the moving mechanical parts have been stopped.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
505 / 592
51.3.6 Equipment connection to earth Terminals for equipment connection to earth , to be done according to international safety standards, are pointed out by the suitable symbol:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
terminal symbol
The position of earth connection terminals is specified in the equipment Installation Handbook.
51.3.7 Heatradiating Mechanical Parts 51.3.7.1 Labelling and safety instructions The presence of heatradiating mechanical parts is indicated by the following warning label in compliancy with IEC 417 Norm, Fig.5041:
carefully observe the specific procedures for installation / turnup and commissioning / maintenance of equipment parts where heatradiating mechanical parts are present, described in the relevant installation / turnup and commissioning / maintenance documents and the following general rule: a) Personal injury can be caused by heat. Avoid touching powered terminals with any exposed part of your body.
506 / 592
Equipment emitting RF power (Reminder from site preparation procedure): The site must be compliant with ICNIRP guidelines or local regulation if more restrictive. The following rules should be strictly applied by Customer: Non authorized persons should not enter the compliance boundaries, if any, for the general public. Compliance RF boundaries, if any, related to Electro Magnetic Field exposure must be marked. Workers should be allowed to switchoff the power if they have to operate inside compliance boundaries. Assure good cable connection. Install the antenna as high as possible from floor or area with public access ( if possible the cylinder delimitating the compliance boundaries, if any, or the cylinder corresponding to the transmission area directly in front of antenna with the same diameter as the antenna, more than 2 meters high). Install the antenna as far as possible from other existing equipment emitting RF power.
Anyway remind that someone standing in front of the 9400AWY antenna may cause traffic shutdown.
Place the relevant stickers: On the site when applicable (when people can cross the compliance boundaries and/or the transmission area of the antenna, i.e. roof top installation) Warning label Do not stand on the antenna axis
EMF emission warning sign (Yellow and black) to be placed at bottom of antenna, visible by someone moving in front of the antenna (roof top installation)
On the antenna (rear side) EMF emission warning sign, placed on the antenna.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
507 / 592
Compliance boundaries: Tab. 73. Compliance boundaries for 9400AWY transceivers with 1ft (30 cm) antenna: B
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
System 9413 AWY Rel 2.0 9415 AWY Rel 2.0 9418 AWY Rel 2.0
Worst Configuration 1+0 with integrated antenna (13 GHz 1ft. SP integrated antenna) 1+0 with integrated antenna (15 GHz 1ft. SP integrated antenna) 1+0 with integrated antenna (18 GHz 1ft. SP integrated antenna)
Antenna configurations: a ) 1+0 with 1ft. integrated antenna b ) 1+1 HSB with coupler and 1ft. integrated antenna c ) Configuration with separated 1ft. antenna 51.3.9 Specific safety rules in this Manual Specific safety rules are specified in the following parts: chapter 32 para.32.9 on page 404 chapter 45 : para.45.2.2 on page 430 para.45.3.1 on page 431 para.45.10.1 on page 454 para.45.10.2 on page 458 para.45.11 on page 460
508 / 592
The equipments EMC norms depend on the type of installation being carried out (cable termination, grounding etc.,) and on the operating conditions (equipment, setting options of the electrical/electronic units, presence of dummy covers, etc.). Before carrying out any installation, turnon, tests & operation and maintenance operations carefully read the related parts of this Manual or other Handbooks, in particular: Installation: Installation Handbook Commissioning: Chapter 32 on page 329 Maintenance: Section 4: Maintenance and Upgrade on page 407
The norms set down to guarantee EMC compatibility, are distinguished inside this handbook by the symbol and term:
ATTENTION
EMC NORMS
51.4.1 EMC General Norms Installation All connections (towards the external source of the equipment) made with shielded cables use only cables and connectors suggested in this Manual or in the relevant Plant Documentation, or those specified in the CustomersInstallation Norms. (or similar documents) Shielded cables must be suitably terminated Install filters outside the equipment as required Ground connect the equipment utilizing a conductor with proper dia. and impedance Mount shields (if utilized), previously positioned during the installation phase, but not before having cleaned and decrease it. Before inserting the shielded unit proceed to clean and decrease all peripheral surfaces (contact springs and connection points, etc.) Screw fasten the units to the subrack. To correctly install EMC compatible equipment follow the instructions given.
51.4.2 EMC General Norms Turnon, Tests & Operation Preset the electrical units as required to guarantee EMC compatibility Check that the equipment is operating with all the shields properly positioned (dummy covers, ESD connector protections, etc.) To properly use EMC compatible equipment observe the information given
51.4.3 EMC General Norms Maintenance Before inserting the shielded unit, which will replace the faulty or modified unit, proceed to clean and decrease all peripheral surfaces (contact springs and connection points, etc.) Clean the dummy covers of the spare units as well. Screw fasten the units to the subrack.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
509 / 592
Observe the precautionary measures stated when having to touch the electronic parts during the installation/maintenance phases. Workers are supplied with antistatic protection devices consisting of (see Fig. 1. on page 36): an elasticized band worn around the wrist a coiled cord connected to the elasticized band and to the stud on the subrack.
Flash Card identification labels: Fig. 35. on page 95 Labels affixed on the ODU: para.14.2 on page 99
510 / 592
This Appendix describes some special conditions that may occur during the TCO Suite startup (para.22.2.3 on page 148 ) and the countermeasures to take. Depending on selected browser, on browser configuration and preferences and on users choices some security questions could be made to the user, like: Active content may potentially harm your computer or disclose personal information. Are you sure to allow the CD for the execution of active content on the computer? To proceed, you must answer YES. In case of specific users browser configuration, the browser could ask some questions about secure or blocked content (Fig. 329. below) and before operating on TCO Suite pages user must click on this information box (usually shown in a pale yellow background on top of the browser HTML page and allow the browser to manage this information (Fig. 330. on page 512).
click
Fig. 329. Security Questions: Secure Content As stated before, the layout and graphical representation for this question (if asked) could be different from browser to browser and, with respect to the same browser, language and information could vary too.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
511 / 592
click
Fig. 330. Secure Questions: Allow Secure Content Usually, the user has to click with the mouse on such yellow bar and a popup menu will appear to ask user if he/she allows running this special content (Fig. 330. above). In some cases another confirmation is requested to the user (Fig. 331. below).
512 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Generally speaking, as soon as the browser is allowed to execute Java applets inside the HTML page, a specific dialog will appear when browser recognizes that Java applets are inside the page. As usual, both language and graphical layout could vary with respect to browser, operating system version, operating system and browser languages and so on. Following Fig. 332. and Fig. 333. show a couple of examples of this warnings: as wrote before, things can differ with respect to language or graphics and so on.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
513 / 592
Fig. 334. Security Warning (Java 1.4) Following Fig. 335. shows a wrong security warning with a Java version lower than 1.4. In this case the TCO Suite wont work:
514 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
This request is necessarily shown because TCO Suite applets needs specific parameters and permissions in order to perform requested operations (reading and writing of files, for example). Applets used are authenticated and a certificate is used to sign applets in order to tell user (and browser) that someone (AlcatelLucent Italia SpA, WTD R&D Software CC, in this case) guarantees about the safety in loading those applets inside a browser. Other examples could be more similar to the one shown in Fig. 334. below, usually with JREs with version number 1.4:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Another difference that user could perceive is related to a missing JRE but, even in this case, the graphical layout will differ from system and browser. If user opens the Start.html page even without a JRE installed shown page would differ from browser and system versions. Following Fig. 336. shows a Mozilla Firefox browser with no JRE installed. On top of browser a yellow alert bar can be seen: in this case the browser detected a special content for which it has no plugin so the browser asks the user to automatically install needed plugin by searching it on the Internet.
Fig. 336. Firefox browser: no JRE installed If user allows to search for related plugin, a specific operation could be started (Fig. 337. below).
Fig. 337. Firefox plugin search And if the user agrees, the browser could automatically install the correct plugin (see following Fig. 338. ). USER MANUAL APPENDICES 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
515 / 592
Fig. 338. Firefox plugin installation As stated before, graphical layout, language, information, alert boxes and everything shown by a browser would differ from each browser and operating system version or release. Then, when Java applets and the Start.html page finally goes for a complete execution, the user will see the content shown in Fig. 55. on page 149.
516 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Since this operations is specifically related to Mozilla Firefox browser, some details could be different with respect to used version. Anyway, since this operation is automatically managed by the browser no control can be made through TCO Suite. Using this procedure will usually install the latest JRE version available as Mozilla Firefox plugin that is usually newer than the JRE 1.4.2_12 available within the TCO Suite.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
53 APPENDIX C: ADDITIONAL SW INSTALLATION OPERATIONS FOR NE MANAGEMENT THROUGH THE NES ECT SERIAL PORT 53.1 Foreword
This procedure is referenced to by case b ) on page 311 , and is necessary only when you need to use the NEs ECT serial port to manage the NE itself by the Craft Terminal functions. N.B. Carrying out this procedure is not necessary if you want to use TCO Suite and Craft Terminal functions, accessing the NE through its Ethernet interface only. the LLMAN installation (step [3] on page 518 ) must always be performed before the 1320CT Package Installation (step [4] on page 518 ) . Installing the 1320CT Package before the LLMAN may result in unproper working. If you have installed the 1320CT Package without having installed before LLMAN, and after you want to install LLMAN, you must: uninstall the1320CT application (see Chapter 410 on page 497 ) install LLMAN and, after, the 1320CT Package, as described in this Appendix.
WARNING:
Procedure: [1] Installation startup 1) 2) Insert the SWP CDROM in the PCs CDROM unit The TCO Suite startup begins. Please refer to para.22.2.3 on page 148 for the procedure execution (in particular for JRE Package automatic installation) and the management of special conditions that could occur At the end of the TCO Suite startup, the CDROM TCO Suite Main Menu screen appears (Fig. 339. below); click on Advanced Settings button
3)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
517 / 592
4)
After a while, the CDROM TCO Suite Advanced Settings screen appears (Fig. 340. below)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 340. CDROM TCO Suite Advanced Settings screen [2] In the CDROM TCO Suite Advanced Settings screen (Fig. 340. on page 518 ) click on button Java JRE Package Installation . Please refer to para.22.2.5.1 on page 152 for details. N.B. as a matter of fact, the JRE Package Installation should have already been done in step [1] 2 ) on page 517 Install LLMAN (Alcatel Lower Layers Manager), as described in para.53.2 from page 519 Carry out the 1320CT Package Installation (installation in PC of SWP components from the SWP CDROM): see para.31.5 on page 314 , taking into account that , when you reach para.31.5.3 on page 317 (Next step) you must come back here to execute steps from [5] below Install and configure Alcatel Virtual Network Card for Lower Layers, as described in para.53.3 from page 522 (different subprocedures, according to the PC Operating System) Complete the Craft Terminal setup carrying out the following phases: 1) Local copy in PC environment of the TCO Suite: para.31.6 on page 318 End of SW installation from SWP CDROM: para.31.7 on page 320 NE software downloading preparation: para.31.8 on page 321 CT initial configuration: para.31.9 on page 326 EML construction: para.31.10 on page 327 END OF PROCEDURE
[3] [4]
[5]
[6]
2)
3)
4)
5)
518 / 592
53.2.1 Operations sequence 1) In the CDROM TCO Suite Advanced Settings screen (Fig. 340. on page 518) click on button SerialFInterface Driver Installation This function performs the installation for the Alcatel Lower Layers Manager together with the drivers needed for the Alcatel Virtual Network Card for Lower Layers. A splash screen will appear as soon as the button applet is clicked (Fig. 341. below) and the installation begins.
Fig. 341. Alcatel Lower Layers Manager splash screen 2) User is asked to select installation and application language (Fig. 342. below).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
519 / 592
3)
Fig. 343. Alcatel Lower Layers Manager Installation screens 4) Select Configure Lower Layer and press FINISH button to open next screen (following Fig. 344. )
520 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Then the installation is carried out automatically after a simple confirmation by the user (Fig. 343. below).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 344. Alcatel Lower Layers Manager setting screen 5) In screen of Fig. 344. above, complete the configuration and press OK button. N.B. If a network adapter is not running in the PC, you can set the System identifierfield with a sequence of 12 0. The following window will be displayed.
6)
53.2.2 Next step You have now completed the Installation of LLMAN from the SWP CDROM. Now, you must proceed with step [4] on page 518
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
521 / 592
At first SWP installation on ECT, after the installation of Alcatel Lower Layer Manager (carried out in previous para.53.2 on page 519), it is necessary, for NE connection using TCP/IP through serial port, to configure a Virtual Network Card. Alcatel Virtual Network Card for Lower Layers is a software component used by Alcatel Lower Layers Manager to manage TCP/IP packets through the serial port. Follow this guide to install and configure Alcatel Virtual Network Card for Lower Layers using the Control Panel. 53.3.1 Important warning Whenever, after the completion of this step, you must install a new network card, always verify that the Alcatel Virtual Network Card for Lower Layers is always the first one in the Network Connections list. Refer to para.53.3.6 on page 546 for details.
53.3.2 Choice of the procedure, according to Windows platform for installation and configuration on Windows NT 4.0 (partially supported) Windows 2000 till SP2 Windows XP till SP2 (Professional Edition only) refer to paragraph 53.3.3 53.3.4 53.3.5 on page 523 529 537
522 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
53.3 Installation and configuration of Alcatel Virtual Network Card for Lower Layers
53.3.3.1 Installing the Alcatel Virtual Network Card for Lower Layers (Windows NT 4.0) To install the Alcatel Virtual Network Card for Lower Layers select the Adapters tab in the Network Control Panel applet. After installing Alcatel Virtual Network Card for Lower Layers you need to configure it following the instruction of the Windows NT 4.0: Configuring Alcatel Virtual Network Card for Lower Layers section. Before installing Alcatel Virtual Network Card for Lower Layers you need to install TCP/IP protocol (please refer to Windows NT Help). Click the Add... button in the Adapter tab of the Network Control Panel applet.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
523 / 592
Fig. 346. Windows NT installation step 2 If the dialog box in Fig. 347. appears, the driver is already installed.
Fig. 347. Windows NT installation step 3 Alcatel Virtual Network Card for Lower Layers is now installed. You need to configure its TCP/IP parameters before use it in with Alcatel Lower Layers Manager. Proceed with para.53.3.3.2 on page 525.
524 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
In the Insert Disk dialog box, type the source path of the driver files copied during installation phase (e.g. C:\WinNT\System32\Drivers\LLmanNIC; type echo %systemroot% from a Command Prompt window to discover the right location of the WinNT folder) and click OK.
53.3.3.2 Configuring the Alcatel Virtual Network Card for Lower Layers (Windows NT 4.0)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
To configure the Alcatel Virtual Network Card for Lower Layers use both the Bindings and the Protocols tabs in the Network Control Panel applet. Before configuring Alcatel Virtual Network Card for Lower Layers you need to install TCP/IP protocol (please refer to Windows NT Help). This operation must be performs at Administrator of the PC, because it subsequently could be to set IP address . To install the Alcatel Virtual Network Card for Lower Layers run the Network Control Panel applet from the Control Panel. Select the bindings of Alcatel Virtual Network Card for Lower Layers in the Bindings tab (1), (2) of the Network Control Panel applet. Disable any unneeded component (3), (4). Selecting the Protocols tab (5) of the Network Control Panel applet, the either a message box (Fig. 349. NT configuration step 2) or a dialog box (Fig. 350. NT configuration step 3) may appear. Follow the instructions until the dialog box (Fig. 351. NT configuration step 4) will appear.
2 3 4
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
525 / 592
Fig. 349. Windows NT configuration step 2 Select Protocols tab (1), TCP/IP Protocol (2) and click the Properties button (3).
526 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Configure the IP Address and the Subnet Mask for the Alcatel Virtual Network Card for Lower Layers and push OK.
3 4
*** WARNING *** If the IP Address of the Virtual Network Card has been changed after a complete SWP installation, it is necessary, for a correct ECT functionality, to perform an explicit ECT recustomization by executing the following command: Start Programs Alcatel SNMPCTKADDON v... SNMP AddOn Customization
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
527 / 592
Click Close in the Protocols tab of the Network Control Panel applet.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 352. Windows NT configuration step 5 The new configuration of Alcatel Virtual Network Card for Lower Layers will be used at the next restart of the computer. If you are configuring or installing the Alcatel Virtual Network Card for Lower Layers you can click Yes. If you are installing some other component you should click No and restart the computer later.
Fig. 353. Windows NT configuration step 6 53.3.3.3 Next step (Windows NT 4.0) You have now completed the installation and configuration of the Alcatel Virtual Network Card for Lower Layers in Windows NT 4.0 environment. Now proceed with the Check for the Network Connections order, para.53.3.6 on page 546.
528 / 592
The System Standby function in the Power Option menu of the Control Panel must be always disabled (select in the Power Schemes tab panel in the Power schemes field Always On). 53.3.4.1 Installing the Alcatel Virtual Network Card for Lower Layers (Windows 2000) To install the Alcatel Virtual Network Card for Lower Layers run the Add/Remove Hardware Wizard from the Control Panel. Before installing and configuring Alcatel Virtual Network Card for Lower Layers you need to install TCP/IP protocol (please refer to Windows 2000 Help). Please make sure of Alcatel Virtual Network Card for Lower Layers is not already installed on your PC: Alcatel Virtual Network Card for Lower Layers has to be installed only once. After installing Alcatel Virtual Network Card for Lower Layers you need to configure it following the instruction of the Windows 2000: Configuring Alcatel Virtual Network Card for Lower Layers section. Click the Next button in the Welcome to the Add/Remove Hardware Wizard dialog box.
Fig. 354. Windows 2000 installation step 1 USER MANUAL APPENDICES 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
529 / 592
530 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Click the Have Disk... button in the Select Network Adapter dialog box.
Fig. 356. Windows 2000 installation step 3 In the Install From Disk dialog box, type the source path of the driver files copied during installation phase (e.g. C:\WinNT\System32\Drivers\LLmanNIC; type echo %systemroot% from a Command Prompt window to discover the right location of the WinNT folder) and click OK.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
531 / 592
Fig. 358. Windows 2000 installation step 5 Alcatel Virtual Network Card for Lower Layers is now installed. You need to configure its TCP/IP parameters before use it in with Alcatel Lower Layers Manager. Proceed with para.53.3.4.2 on page 533. 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL APPENDICES
532 / 592
53.3.4.2 Configuring the Alcatel Virtual Network Card for Lower Layers (Windows 2000)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
This operation must be performs at Administrator of the PC, because it subsequently could be to set IP address . To configure the Alcatel Virtual Network Card for Lower Layers run the Network and Dialup connections applet from the Control Panel. Before installing and configuring Alcatel Virtual Network Card for Lower Layers you need to install TCP/IP protocol (please refer to Windows 2000 Help). To install the Alcatel Virtual Network Card for Lower Layers run the Add/Remove Hardware Wizard from the Control Panel. Open the network connection using the Alcatel Virtual Network Card for Lower Layers from the Network and Dialup connections applet.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
533 / 592
1 2
534 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Uncheck any unneeded component in the Properties dialog box General tab (1). Check and select the Internet Protocol (TCP/IP) component (2) and click Properties (3).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Configure the IP Address (1) and the Subnet Mask (2) and push Advanced (3) to open the relevant Advanced TC/IP Settings screen In the Advanced TC/IP Settings screens Interface Metric field, write 50 (4) and push OK (5) Having come back to the first screen, push OK (6)
1 2
3 6
5
Fig. 361. Windows 2000 configuration step 3
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
535 / 592
*** WARNING *** If the IP Address of the Virtual Network Card has been changed after a complete SWP installation, it is necessary, for a correct ECT functionality, to perform an explicit ECT recustomization by executing the following command: Start Programs Alcatel SNMPCTKADDON v... SNMP AddOn Customization
53.3.4.3 Next step (Windows 2000) You have now completed the installation and configuration of the Alcatel Virtual Network Card for Lower Layers in Windows 2000 environment. Now proceed with the Check for the Network Connections order, para.53.3.6 on page 546.
536 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Alcatel Virtual Network Card for Lower Layers is now configured. You need Alcatel Lower Layers Manager to use it.
The System Standby function in the Power Option menu of the Control Panel must be always disabled (select in the Power Schemes tab panel in the Power schemes field Always On).
53.3.5.1 Installing the Alcatel Virtual Network Card for Lower Layers (Windows XP Professional Edition) To install the Alcatel Virtual Network Card for Lower Layers run the Add Hardware Wizard from the Control Panel. After installing Alcatel Virtual Network Card for Lower Layers you need to configure it following the instruction of the Windows XP: Configuring Alcatel Virtual Network Card for Lower Layers section. Please make sure of Alcatel Virtual Network Card for Lower Layers is not already installed on your PC: Alcatel Virtual Network Card for Lower Layers has to be installed only once. Click the Next button in the Welcome to the Add/Remove Hardware Wizard dialog box.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
537 / 592
538 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
539 / 592
Click the Have Disk... button in the Select Network Adapter dialog box.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 364. Windows XP installation step 3 In the Install From Disk dialog box, type the source path of the driver files copied during installation phase (e.g. C:\Windows\System32\Drivers\LLmanNIC; type echo %systemroot% from a Command Prompt window to discover the right location of the Windows folder) and click OK.
C:\Windows\System32\Drivers\LLmanNIC
540 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Click Next in the The wizard is ready to install your hardware dialog box.
Fig. 366. Windows XP installation step 5 Alcatel Virtual Network Card for Lower Layers is now installed. You need to configure its TCP/IP parameters before use it in with Alcatel Lower Layers Manager. Proceed with para.53.3.5.2 on page 542. USER MANUAL APPENDICES 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
541 / 592
This operation must be performed by the Administrator of the PC, because it subsequently could be to set IP address . To configure the Alcatel Virtual Network Card for Lower Layers run the Network connections applet from the Control Panel. To install the Alcatel Virtual Network Card for Lower Layers run the Add/Remove Hardware Wizard from the Control Panel. Open the network connection using the Alcatel Virtual Network Card for Lower Layers from the Network and Dialup connections applet.
542 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
53.3.5.2 Configuring the Alcatel Virtual Network Card for Lower Layers (Windows XP Professional Edition)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Uncheck any unneeded component (disable always the QoS Packet Scheduler 1 ) in the Properties dialog box General tab. Check and select the Internet Protocol (TCP/IP) component (2) and click Properties (3).
1 2 3
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
543 / 592
1 2
3 4
*** WARNING *** If the IP Address of the Virtual Network Card has been changed after a complete SWP installation, it is necessary, for a correct ECT functionality, to perform an explicit ECT recustomization by executing the following command: Start Programs Alcatel SNMPCTKADDON v... SNMP AddOn Customization
544 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Configure the IP Address (1) and the Subnet Mask (2) and Advanced option (3) and then push OK (4).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Configure the Advanced TCP/IP Settings dialog box select the WINS sheet (1), Disable NetBIOS over TCP/IP (2) and then push OK (3).
Fig. 370. Windows XP configuration step 4 Alcatel Virtual Network Card for Lower Layers is now configured. You need Alcatel Lower Layers Manager to use it. 53.3.5.3 Next step (Windows XP Professional Edition) You have now completed the installation and configuration of the Alcatel Virtual Network Card for Lower Layers in Windows XP (Professional Edition only) environment. Now proceed with the Check for the Network Connections order, para.53.3.6 on page 546.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
545 / 592
53.3.6 Check for the Network Connections order For the SWP to operate correctly, it is necessary that the Alcatel Virtual Network Card for Lower Layers is always the first one in the Network Connections list. To carry out this check, operate as follows: 1) 2) Start Control Panel Network Connections in the field LAN or High Speed Internet, select the Device Name Alcatel Virtual Network Card for Lower Layers from Advanced menu, select Advanced Settings in the relevant screen (Fig. 371. below) verify that it is the first in the list. If necessary, move its position, using suitable arrows.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
3) 4)
Fig. 371. Check for the Network Connections order Whenever, after the installation of this SWP, you must install a new network card, always verify that the Alcatel Virtual Network Card for Lower Layers is always the first one in the Network Connections list. You have now completed the installation, configuration and check of the Alcatel Virtual Network Card for Lower Layers. Now proceed with step [6] on page 518
546 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
547 / 592
[1]
Ethernet Physical Interface Layer The Ethernet interfaces can be configured according to two different modalities: manual mode (or default type, autonegotiation is disabled) or automatic mode (autonegotiation is enabled): these two modalities are valid always for Fast Ethernet signals, only automatic mode for Gigabit Ethernet signals. In automatic mode a mechanism of autosensing (the autonegotiation) of the parameters involved is activated, these parameters are negotiated with the remote Ethernet interface. Autonegotiation on a link is exchanged when: link is initially connected device at either end of the link is powered up device is reset or initialized the management system requires an autonegotiation restart During autonegotiation, each port automatically chooses its mode of operation by advertising its abilities and comparing them with those received from its link partner. The parameters that can be advertise during autonegotiation from each port must be selected between the following: Speed: 10 Mbit/s or/and 100 Mbit/s or/and 1000 Mbit/s (all combinations are possible) Capability: full and/or half duplex (note 1) Flow control (802.3x): pause disable or pause enable (note 2) note 1 when the rate is 1000 Mb/s, then the supported capability is always full duplex. note 2 in half duplex, the back pressure is not supported. If the remote end has the ports in manual mode and the link partner has the autonegotiation enabled, the link could be established with 10 or 100 Mbit/s speed and halfduplex capability (as defined by the standard 802.3).
548 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The following items resume the features supported by ULS in terms of Gigabit Ethernet Physical interface management: autonegotiation is always enabled only in case of Gigabit Ethernet signal; the operator can plan one or a set of rates (10 and/or 100 and/or 1000 Mb/s), and allow to autonegotiate them; the directionality can be half or fullduplex (when the 10 and/or 100 Mb/s rates are chosen, the directionality can be half or full duplex, when the 1000 Mb/s rate is chosen, the directionality is always fullduplex); when the autonegotiation process fails or when the autonegotiation parameters are changed, the autonegotiation restart command has to be performed in order to have new configured parameters effective. [2] Ethernet Port Layer The following items resume the features supported by ULS in terms of Gigabit Ethernet Port layer management: the Pause function is allowed only when the capability is fullduplex; the Pause function can be supported in automatic or manual mode; the Ethernet Flow Control (EFC) can be enabled or disabled; when it is enabled, PAUSE function can be symmetric and asymmetric (IEEE 802.3x); the supported asymmetric case is related to allowed Pause at transmission side, no allowed Pause at receiver side; in case of remote peer MAC layer without EFC feature, the overflow of the input queues causes to discard any further received MAC frames: a correct frame received and discarded because of an input queues overflow, is not counted as a received frame; total transparency towards the IEEE 802.1Q (VLAN management is presently not supported); Ethernet corrupted frames (Tx and Rx side independently) can be discarded or forwarded to the addressed destination, according to the related SNMP manager request.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
549 / 592
[2]
MAC Learning The entry in a database, the address resolution table is written learned the source address from received unicast packets. The switch supports also static writing of the address resolution table, these entries are created and updated via programming interface. Up to 4096 entries (MAC address port mapping) can be stored in the database. It is always enabled.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
[3]
MAC Ageing In current SWP version, only default values are defined (typical value is 300 seconds, it is an indicative value, the real range is 300 600 seconds) The aging process periodically removes dynamically learned addresses from the address resolution table. The address aging process is used to ensure that if a node is disconnected from the network segment, or it become inactive, its entry is removed from address database. Aging makes room for new active addresses.
[4]
At least four output queues with flexible scheduler In current SWP version, only default values are defined (typical default configuration is: DWRR algorithm with weight respectively of 8, 4, 2, 1 for the four queues on each port). Each egress port can support up to four transmit queues; frames are assigned to each queue according to their priority. Algorithms type Deficit Weighted Round Robin (DWRR) and High Queue Preempt (HQP) are used to schedule each transmit queue. The deficit weighted roundrobin algorithm allows each queue to be serviced in turn, sending a set amount of packets before moving to the next queue. For every round are sent 8 packets from queue with highest priority and respectively 4, 2, 1 packets from the queues with lower priority.
[5]
Frame types The switch is able to treat Ethernet frames of the following types: Ethernet v2, 802.3, 802.1Q. No ECT/NM management is necessary.
[6]
IEEE 802.1Q (VLAN management) In current SWP version, the traffic type IEEE 802.1Q tag is managed in transparent mode (the switch does not look the tag). The IEEE 802.1Q tag VLAN feature is enabled including between the other the stripping or adding of the TAG and VLAN lookups in addition to MAC lookups (this feature can be useful to logically break a physical LAN into a few smaller logical LAN and prevent data to flow between the subLAN).
550 / 592
[7]
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
IEEE 802.3x Flow Control In case of incoming Ethernet traffic leading to exhaustion of buffers on input queues, PAUSE frames are transmitted in order to slow down remote peer MAC layer. When the flow control is activated any packets shall not be lost. The flow control management is foreseen only for the four user ports and not for the port linked to the FPGA.
[8]
QoS management (IEEE 802.1p, IPV4 ToS & DiffServ, Port based)
The Ethernet switch provides a Quality of Service mechanism to control all streams. The QoS feature, referred to the four ports (line side) Gigabit Ethernet, provides up to four internal queues per port (four user ports and one radio) to support four different traffic priorities. These priorities can be programmed in such a way that highpriority traffic in the switch experiences less delay than lowerpriority traffic under congested conditions. For Ethernet flows in the switch, it is possible by CT/NMS (see Fig. 131. on page 231 , and Fig. 248. on page 352 ) to choose how assign the priority to each packet according to the information in: a) IEEE std 802.1p
The packet is examined for the presence of a valid 802.1P userpriority tag. If the tag is present the correspondent priority is assigned to the packet. When 802.1p QoS mechanism is adopted the reference is the standard IEEE 802.1D2004 Annex G User priorities and traffic classes that defines 7 traffic types and the corresponding user priority values. Considering that the switch has four egress queues for each port, the mapping 802.1p value to queue is the following: Tab. 74. QoS based on IEEE std. 802.1p 802.1P priority 111,110 101,100 011,000 010,001 Queue Queue 4 (higher priority) Queue 3 Queue 2 Queue 1 (lower priority)
When an incoming packet is not 802.1p it is assigned to the lowest priority queue.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
551 / 592
b)
DiffServ
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
When DiffServ QoS mechanism is adopted the classification uses the DS field of the IP packet header. Each packet is classified based on DSCP field in the IP header to determine the priority. Considering that for the switch has four egress queues for each port the mapping DSCP value (6 bits) to queue is the following: Tab. 75. QoS based on DiffServ DiffServ priority 111000, 110000, 101110, 101000 100110, 100100, 100010, 100000, 011110, 011100, 011010, 011000 010110, 010100, 010010, 010000, 001110, 001100, 001010, 001000, 000000 all the remaining values Queue Queue 4 (higher priority) Queue 3 Queue 2 Queue 1 (lower priority)
When an incoming packet has not DiffServ valid value, it is assigned to the lowest priority queue.
[9]
Link aggregation In current SWP version, the default corresponds to disabled link aggregation. The link aggregation (or trunking) feature allows bundling several physical ports together to form a single logical channel. In this way provides a more resilient end to end connection, and enables load balancing. The switch supports: automatic failover: if one of multiple ports aggregate in a logical link fails, traffic network is dynamically redirected to remaining good ports in the link. Mac based trunking: the load balancing traffic depends of the dynamics of MAC address distribution
552 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
55 APPENDIX E: ECTEQUIPMENT CONNECTION VIA PUBLIC SWITCHED TELEPHONE NETWORK 55.1 Introduction
This chapter explains the operations necessary to allow the remote connection to the FInterface, from a local PC (with external or internal modem) configured as ECT, through a switched telephone line of the standard Public Telephone Network, as shown in Fig. 372. here below. This kind of remote control is possible for a single equipment as well as for a whole subnetwork.
F Interface
PC/ECT
Local Modem
Remote Modem
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
553 / 592
with the following types of PC: 1) with external modem: characteristics as in para.31.1.1 on page 309 with internal modem: PC laptop Dell Latitude: Processor equipped: Operating system: RAM equipped: Hard disk equipped: Internal Modem:
2)
PENTIUM III Microsoft Windows 2000 v. 5.00.2195 service pack 2 128 Mbytes 10 Gbytes 3COM 56K v.90 Mini PCI MODEM
c)
and with the following local/remote combinations: Local Modem Remote Modem Sportster Flash Sportster Flash TD 32 AC 3Com 56K Faxmodem TD 32 AC TD 32 AC Sportster Flash 3Com 56K Faxmodem TD 32 AC PC laptop Dell Latitude as in Sportster Flash point b ) 2 ) above 3Com 56K Faxmodem
Testing the connection with different types of modems is fully on Customers charge.
554 / 592
In the following figures, the cables for the connections are described:
PC/ECT (DTE)
Cannon 9 pins female DCD TD RD DTR DSR RTS CTS GND 1 2 3 4 6 7 8 5
F Interface (DCE)
Cannon 9 pins male 3 2 7 8 6 4 5 TD RD RTS CTS DSR DTR GND
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
555 / 592
2) 3)
Now, setting has been completed. External Modem can be switched off and disconnected, if necessary.
556 / 592
N.B.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
For confirmation, the modem configuration can be checked writing the command ATI4<Return> in the HyperTerminal program window. Information displayed should be as follows:
ATI4 U.S. Robotics Sportster Flash 56000 Settings... B0 E1 F1 L2 M1 Q0 V1 X3 Y0 BAUD=38400 PARITY=N WORDLEN=8 DIAL=TONE OFF LINE CID=0 &A3 &M4 &B1 &N0 &C1 &P0 &D2 &R2 &H1 &S0 &I0 &T5 &K1 &U0
&Y1 S04=010 S11=072 S21=010 S30=000 S38=000 S05=008 S12=050 S22=017 S31=128 S39=012 S06=004 S13=000 S23=019 S32=002 S40=000
LAST DIALED #: REMOTE MODEM SETTING To set the remote modem, proceed as follows: a) b) carry out same steps 1 ) , 2 ) , 3 ) as for local modem setting execute and store the modem setup, writing in the HyperTerminal program window the same commands described in step 4 ) for the local modem setting, and adding the following command: ATS=1<Return> c) N.B. (Autoanswering setting)
now, setting has been completed. Modem can be switched off and disconnected, if necessary. For confirmation, the modem configuration can be checked writing the command ATI4<Return> in the HyperTerminal program window. Information displayed should be equal to that displayed for the local modem, with only the difference for field S00: S01=000 S02=043 S03=013 S04=010 S05=008 S06=004
S00=001
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
557 / 592
55.4.2 TD32 AC Modem setting This modem requires an initial HW setup via dipswitches and a SW setting via serial port. To set the modem, both local and remote, proceed as follows: 1) The initial HW setup via dipswitches is indicated in Fig. 375. herebelow:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
ON 1 2 3 4 5 6 7 8
ON 1 2 3 4 5 6 7 8
ON 1 2 3 4
SW3
SW2
SW1
ON 1 2 3 4 5 6 7 8
ON 1 2 3 4 5 6 7 8
SW5
SW4
Fig. 375. TD32 AC modem dipswitch setting 2) 3) 4) Connect the local modem to the PC/ECT with the cable of Fig. 373. on page 555. Power on the local modem (there is no an ON/OFF switch). On the PC, activate program HyperTerminal and configure the PCModem serial line with the following parameters: * Bits per second: 38400 * Data Bits: 8 * Parity: None * Stop Bit: 1 * Flow control: None 5) Execute and store the modem setup, writing the following commands in the HyperTerminal program window: AT&F1<Return> AT&K0<Return> ATA<Return> AT&W0<Return> AT&Y0<Return> 6) (Best PC default configuration recall) (DTE/DCE flow control disabling) (Automatic Answer enabling > Only on Remote modem and wait the message NO CARRIER) (Configuration store in NVRAM 0) (Configuration Set to load at switchon: NVRAM 0)
Now, setting has been completed. Modem can be switched off and disconnected, if necessary.
558 / 592
N.B.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
For confirmation, the modem configuration can be checked writing the command AT\S<Return> in the HyperTerminal program window. Information displayed should be as follows:
AT\S CMD DESCRIPTION / OPTION COUNTRY...........IT DTE BPS........38400 DTE PARITY.....8NONE LINE SPEED......NONE B BELL MODE........OFF E CMD ECHO..........ON F LINE MODE.......AUTO L SPKR VOLUME......LOW M SPKR CONTROL....CALL N AUTO MODE.........ON Q QUIET............OFF V RESULT FORM.....LONG W EC MSG.............0 X EXT RESULTS........4 Y LONG SPACE DISC...NO %C COMPRESSION.....BOTH K EXT. SERVICES......0 CMD &A &B &C &D &G &K &L &Q &R &S &T &X &Y \A \G \K \N DESCRIPTION / OPTION CHR ABORT OPT.....NO DTR DIAL OPTION...NO DCD OPTION........ON DTR OPTION.........0 GUARD TONE......NONE FLOW CONTROL....NONE NETWORK.........PSTN ASYNC/SYNC.........5 RTS/CTS.........AUTO DSR OPT............0 ENABLE RDL........NO SYNC CLOCK.......INT PROFILE........NVM.0 MAX BLK SIZE.....192 REMOTE FLOW......OFF BRK OPT............5 ECL MODE........AUTO CMD DESCRIPTION / OPTION *H NEG. SPEED......HIGH S0 RINGS TO ANS.....002 S1 RING COUNT.......000 S2 <ESC> CHAR.......043 S3 <CR> CHAR........013 S4 <LF> CHAR........010 S5 <BS> CHAR........008 S7 CONNECT TIME.....060 S8 PAUSE TIME.......002 S12 ESC GUARD TIME...050 S30 CONNECT INACT....000 S32 XON CHAR.........017 S33 XOFF CHAR........019 S36 FALLBACK ACTION..007 S37 MODE SELECT......000 S48 V42 NEG CTRL.....007 S95 RES. CODE........000
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
559 / 592
3) 4) 5) 6)
7) 8)
10 ) Execute the telephone call from the PC writing the following command in the HyperTerminal program window: ATDnnn<Return> where nnn is the telephone network number associated to the remote telephone line (that which the remote modem is connected to). 11 ) Wait the message indicating the successful connection between local and remote modems. N.B. The message text depends on the modem type, as follows: CONNECT 14400/ARQ/V32/LAPM/V42BIS CONNECT 38400 12 ) Close HyperTerminal program. 13 ) Activate the ECT applicative SW as usual. 14 ) At the end of the job, after having logged out from the ECT applicative SW, close the connection between local and remote modems, switching off the local modem or physically disconnecting the cable connecting it to the PC. (Sportster Flash) (TD 32 AC)
560 / 592
55.7.1 Introduction This feature is meant to use modems with speed different from that documented in previous paragraphs, giving the possibility to configure the ECT connection through modem (speed values: 9600, 19200, 38400, 56000) with automatic management of modem setup and phone call at ECT startup. To make change operative, the following operations are necessary: at equipment side, the configuration must be setup as explained in the para.55.7.2 below, at PC side, the configuration must be setup as explained in the following para.55.7.3 on page 562, as far as the modem is concerned, please refer to the constructor documentation.
55.7.2 Configuration at NE side 1) Login the NE through the TCO Suite Alarms & Settings function (see para.22.3.1 on page 156) using a login profile allowing the Modem Speed change (see Tab. 55. on page 158), enter the Modem Speed screen and set the required speed (see para.22.3.9 on page 167).
2)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
561 / 592
55.7.3 Configuration at PC side To configure the modem with the relevant speed, enter the menu Settings > Control Panel of the Operating System and open the Alcatel Lower Layers utility. The menu of Fig. 376. opens.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Fig. 376. Alcatel Lower Layers utility In the Subnetwork Type field select Modem. In the Modem field select the suitable Modem type. In the Modem speed field select the suitable speed (9600, 19200 or 38400) and click on OK. In the Phone Number field enter the phone number, which will be automatically called at the ECT startup.
562 / 592
This appendix supplies information referenced to by para.43.2.2 on page 416 These part lists are given for general information purpose. The parts listed in each tool kit could differ from those actually delivered inside the kit (make reference to the part list accompanying the kit).
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
563 / 592
564 / 592
P/N 41172010 41172011 41911001 248501099 870952129 870952131 870952417 870952706 870959166 879010249 879010250 1AB026470031 1AB026470031 1AD024120002 1AD035000002 1AD035000003 3AL79115AAAA 3DB01229AAAA 3DB03884AAAA 8BE815010002 8BE815010070 8BE815010080 8BE815020020 8BE815020021 8BE815020040 8BE815020041 8BE815020042 8BE815030000
Description INSULATED PLUG WITH PLIERS ANTISTATIC WRIST BAND CORDONE X APPLICAZIONI A FEMALE BUTTON TERMINATION CHIAVE FISSA I6XI7 CHIAVE FISSA I7XI9 CHIAVE PIEGATA COMB.ESAG.17 CHIAVE X ESAG.INCASSATO 6 CACCIAVITE 5,5X200 TOOL KEY 5,5 MM TOOL KEY 7 MM PROTECTION*BIPOLAR PROTECTION*BIPOLAR UNHOOK TOOL HAND TOOL MALE WRENCHE HAND TOOL MALE WRENCHE EXTRACTOR CABLE LEVER 8X10 FIXED SPANNER TORQUE WRENCH ALLEN WRENCH 3XIOO SCREWDRIVER 3.5X100 SCREWDRIVER 3X60 CROSSHEAD SCREWDRIVER 4.5X80 CROSSHEAD SCREWDRIVER 4.5X250 CROSSHEAD SCREWDRIVER TOOL KIT
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
565 / 592
566 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
This
appendix contains all information regarding: this Manual, herebelow the Customer Documentation set this Manual belongs to, general on AlcatelLucent Customer Documentation,
57.1.1 Applicability of this Manual a) Productrelease applicability The current edition of this Manual applies to the 9400AWY Rel.2.1 in the RF band configurations listed in Tab. 46. on page 127. NE applicability The current edition of this Manual applies to the following Network Elements (NE): ULS SWP and Version applicability The current edition of this Manual applies to the set of systems equipment, configurations and features associated to the following SWP versions: SWP Technical Description SWP 9400AWY R.2.1 V2.1.1 SWP Technical Code REF.[a] in Tab. 53. on page 141 SWP Version (N.B.) V2.1.1
b)
c)
N.B.
For the meaning of SWP Release and Version, please refer to para.57.3.2 on page 573. The indication of the Versions in this Manual has the following meaning: this Manual applies starting from the Versions stated in this table, but it could also apply to subsequent Versions for the following reasons: a) this Manual is not modified, unless the new version distributed to the Customers comprises changes to the manmachine interface, or even in the presence of minor changes that do not affect negatively the understandability of the procedures described therein (e.g. a button moved internally to a screen); furthermore, if the screens contained in this Manual show the versionrelease of the productrelease, then they are not replaced in the subsequent versions of Manual if their contents remains unchanged.
b)
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
567 / 592
57.1.2 Purpose of this Manual This Manual belongs to the Customer Documentation set envisaged for the equipment specified in para.57.1.1 on page 567. Refer to para.57.2 on page 569 in order to have the list and description of the Customer Documentation set. Taking into account that the system consists of an InDoor Unit (IDU), an OutDoor Unit (ODU), and a Software Package (SWP), this Manual provides the following information: system description at different detail levels, with regard to system, hardware and software system technical specifications IDU and ODU item Part Numbers and equipping rules (provisioning) unit operative hardware description: access point description (usage of LED, pushbuttons, switches and connectors for Customer use), connection rules, hardware setting options operation and maintenance activities the operators can carry out according to the specific software application(s) referred to in this Manual [see para. 57.1.1 point c ) on page 567 ]. spare parts provisioning routine maintenance procedures corrective maintenance and unit replacement procedures SWP installation equipment and radio link commissioning procedure.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
is not strictly necessary before starting this document, but its knowledge is necessary for operating the procedures introduced by this document and detailed in the other sections of this Manual.
568 / 592
This paragraph contains all information regarding the 9400AWY Rel.2.1.1 Customer Documentation and is organized as follows: 9400AWY Rel.2.1.1 Customer Documentation herebelow Product Release Note on page 571 Additional documentation for 1320CT platform on page 571 WARNING: this Documentation set is relevant to 9400AWY Rel.2.1 final version V2.1.1 only. The Documentation set relevant to 9400AWY Rel.2.1 previous version V2.1.0 and prerelease version V2.1.1* is contained in the CDROM P/N 3DB16142ABAA.
57.2.1 9400AWY 2.1.1 Customer Documentation This paragraph lists and briefly describes the documentation set envisaged for 9400AWY Rel.2.1.1. Please refer to following para.57.3 on page 572 for a general description of AlcatelLucent Customer Documentation system. The list of handbooks given here below is valid as at the issue date of this Handbook and can be changed without any obligation for AlcatelLucent to update it in this Handbook. The standard Customer Documentation for 9400AWY Rel.2.1.1 is in the English language and is distributed to Customers only by the following CDROM: Tab. 76. 9400AWY Rel.2.1.1 Documentation CDROM REF Technical Description DCP 9400AWY 2.1 V2.1.1 CD_ROM [A] Technical Code 3DB 16142 ACAA
This CDROM contains, in electronic format (ADOBE ACROBAT pdf files), all handbooks listed in Tab. 77. on page 570
N.B. a) Standard supply One copy of the 9400AWY Rel.2.1.1 CDROM is automatically delivered to Customer together with the equipment it refers to (one copy for each terminal). As 9400AWY Rel.2.1.1 CDROM is a standard commercial item, additional copies can be ordered and delivered as any other AlcatelLucent commercial item. Supply to Customers of paper copies of the handbooks is not envisaged. Supply to Customers of Customer Documentation source files is not envisaged. Productdocumentation consistency Equipment description and layout are always general, i.e. they never describe the actual composition of the equipment supplied to Customer (this task is entrusted to plantdependent documentation). Detailed hardware documentation concerns actually supplied units and is coherent with the production issue of such units. Softwareassociated handbooks are coherent with the supplied SWP release. Copies of the CDROMs regarding a specific productrelease previously delivered can be required specifying P/N and edition. Copyright notification The technical information of the handbooks and CDROMs supplied to Customers is the property of AlcatelLucent and must not be copied, reproduced or disclosed to a third party without written consent. 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
b)
c)
569 / 592
Tab. 77. Handbooks contained in the 9400AWY R.2.1.1 documentation CDROM N.B. The P/Ns of handbooks is just for Alcatel internal management only. As specified in point a ) on page 569, they do not represent Commercial item P/Ns. HANDBOOKT NAME HANDBOOKS FOR HARDWARE INSTALLATION (n.b.1) 9400AWY Rel.2.1 Installation Handbook [B] 9400AWY Rel.2.1 Installation Guide USER MANUAL (n.b.2) [C] 9400AWY Rel.2.1 V2.1.1 User Manual this manual TRS & SAT DOCUMENT (n.b.3) [D] 9400AWY Rel.2.1 TRS and SAT ADDITIONAL DOCUMENTATION [E] n.b.1 Interference investigation procedure n.b.4 3DB 04165 EAAA 3DB 16142 DAAA 3DB 16142 EAAA 3DB 16142 FAAA 3DB 16142 BAAA HANDBOOK P/N
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
REF
These handbooks provide information regarding equipment hardware installation, according to AlcatelLucent WTD LAB. rules. Moreover, they give the P/Ns of all installation materials that are not given in this User Manual. As shown, two versions are available: the Installation Handbook provides detailed descriptions and instructions, and is mainly addressed to technicians who have never installed a 9400AWY system before the Installation Guide provides same information in a more concise way, and is mainly addressed to technicians who have already installed a 9400AWY system
This User Manual makes reference to the Installation Handbook; using it or the Installation Guide is on Customer choice. n.b.2 n.b.3 See para.57.1.2 on page 568 Contains the Test Report Sheets and the Site Acceptance Test protocol, according to AlcatelLucent WTD LAB. rules. The source file of this document (MSWord 2000) is also distributed in the Documentation CDROM. Describes the measurement procedure for the interference searching in the various RF bands used by Alcatel Radio Transmission products. It is common to all Alcatel Radio Transmission products.
n.b.4
570 / 592
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 Documentation CDROM nor automatically delivered to Customers. The Product Release Note is available only on specific request to your AlcatelLucent local dealer, specifying the SWPs Technical Code and ICS (edition) printed on the SWP CDROM itself. 57.2.3 Additional documentation for 1320CT platform Tab. 78. Documentation common to AlcatelLucent Network Elements using 1320CT platform REF CTK Version (N.B.) q 3.0.1 [F] ITEM DCP 1320 CT 3.x CD_ROM EN P/N 3AL 79552 AAAA
Contains, in electronic format, the 1320 CT Operators Handbook REF.[G] to [I] q 3.0.1 1320CT Rel.3.x Basic Operators Handbook 3AL 79551 AAAA
[G]
Provides general information and operational procedures common to all 1320CT (Craft terminal) of AlcatelLucent InfoModel Network Elements. q 3.0.1 AS Rel.6.5 Operators Handbook 3AL 88876 AAAA
[H]
Provides detailed information and operational procedures regarding the alarm Surveillance software embedded in the 1320CT software package. q 3.0.1 ELB Rel.2.x Operators Handbook 3AL 88877 AAAA
[I] N.B.
Provides detailed information and operational procedures regarding the Event Log Browser software embedded in the 1320CT software package. The CT Version is displayed when, on the PC, you select the 1320CT application for its launch.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
571 / 592
Aims of standard Customer Documentation Standard system, hardware and software documentation is meant to give the Customer personnel the possibility and the information necessary for installing, commissioning, operating, and maintaining the equipment according to AlcatelLucent Laboratory design and Installation Dept. choices. In particular: N.B. the contents of the handbooks associated to the software applications focus on the explanation of the manmachine interface and of the operating procedures allowed by it; maintenance is described down to faulty PCB location and replacement. No supply to Customers of design documentation (like PCB hardware design and production documents and files, software source programs, programming tools, etc.) is envisaged.
572 / 592
See Fig. 377. on page 574. a) Products A product is defined by the network hierarchical level where it can be inserted and by the whole of performances and services that it is meant for. E.g. 9400AWY is a product. b) Product-releases A product evolves through successive productreleases, which are the real products marketed for their delivery at a certain productrelease availability date. A certain productrelease performs more functionalities than the previous one. E.g. Rel.1.0, Rel.2.0 and Rel.2.1 are three successive productreleases of the same product. A productrelease comprehends a set of hardware components and at least one Software Package (SWP); as a whole, they identify the possible network applications and the equipment performances that the specific productrelease has been designed, engineered, and marketed for. c) Configurations and Network Elements In some cases, a productrelease includes different possible configurations which are distinguished from one another by different Network Element (NE) types and, from the management point of view, by different SWPs. d) SWP Releases and Versions This description is 9400AWYspecific: A 9400AWY SWP is identified by its Denomination, Part Number and Change Status, that are printed on the CDROMs label. The SWP Denomination versions first and second digits (e.g. 2.1) correspond to the HW productrelease number first and second digits; third digit of the SWP version identifies the Version Level of the SWP. A 9400AWY SWP with new Denomination and Part Number represents a fully new SWP having main features in addition to those of the previous SWP. A 9400AWY SWP with same Denomination and Part Number , but with new Change Status corresponds to a new version of such SWP, usually developed for bugfixing purposes and/or minor additional features.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
573 / 592
e)
Customer Documentation A productrelease(configuration) has its own set of standard Customer Documentation, usually formed of several handbooks, i.e., in general: System and Hardware documentation: one (or more) Technical Handbook(s) an Installation Handbook a Commissioning Handbook or LineUp Guide Software documentation: a Craft Terminal Operators Handbook, associated to the specific SWPRelease other Operators Handbooks (typically those associated to the SW platform embedded in the SWP) In other cases (e.g. this Manual), above pieces of information are collected in a single document. PRODUCT
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
ALTERNATIVE CONFIGURATIONS
CONFIG.A
CONFIG.B
SWP REL.1.0
evolution
SWP REL.1.1
574 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
58 APPENDIX H: LIST OF SYMBOLS AND ABBREVIATIONS, GLOSSARY OF TERMS 58.1 List of symbols
Tab. 79. List of symbols N.B. This table lists some symbols whose interpretation could be doubtful. MEANING AND COMMENTS In this handbook it is not the division symbol. It means from .. to ... E.g.: <value1>
<value2> means: from <value1> (included) to <value2> (included) A polarization symbol like this: POLARIZATION can be assumed as either horizontal SYMBOLS Once you have decided a polarization (e.g. H or vertical H ) ) V V
SYMBOL
MEANING STARTING WITH NUMBERS Shorthaul low/medium capacity digital microwave radio links PDH Low/Medium Capacity Free Space Optic System SDH/SONET High Capacity Free Space Optics System STM 1/0 Long Haul Digital Radio Relay System Urban Haul Synchronous split mount Radio System A Enabling Abnormal Alternate Current Access Control Domain Association Control Service Element Analog to Digital Converter Access Enable Atomic Function Add and Drop Multiplexer Automatic Gain Control Alarm indication Signal 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
575 / 592
ALR ALS AMI AND ANSI AP API APS APT AS ASAP ASE ASIC AT ATL ATM ATPC ATTD AUX AVC BATT BB BBE BCA BER BIP BKPV BNC BSC BTS CAND CCDP CCITT CD CE CFA C/I CK CLA CLEC
Automatic Laser Restart Automatic Laser Shutdown Alternate Mark Inversion Alarm on both station batteries American National Standard Institute Alternate Polarization Access Point Identifier Automatic Protection Switching Active Problem Table Alarm Surveillance Alarm Severity Assignment Profile Application Service Element Application Specific Integrated Circuit Attended Alarm Far Terminal Alarm Asynchronous transfer Mode Automatic Transmit Power Control ATTendeD (alarm storing) AUXiliary Attribute Value Change B Battery Base Band Background Block Error Common Battery Dial Pulsing (Telephone Set) Bit Error Rate Bit Interleaved Parity Back Plane Version Bayonet Not Coupling Base Station Controller Base Transceiver Station C All power supply units are faulty CoChannel Dual Polarized (Frequency reuse) International Telephone and Telegraph Consultative Committee Current Data European Conformity Carrier Failure Alarm Carrier to Interference ratio Clock Common Loss Alarm Competitive Local Exchange Carrier USER MANUAL APPENDICES
576 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
MEANING
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Tab. 80. List of abbreviations ABBREVIATION CMISE CMISS CO COAX CP CPE CPI CPO CPU CRCn CS CT CTP DA DAV D/A DC DCC DCE DCN DDF DEFEC DEM DEMUX DF DIV DM DRRS DTE DTI DTMF EB EBC EBU EC ECC ECS ECT EE EF USER MANUAL APPENDICES Card Missing Central Office Coaxial Copolar Customer premises equipment Incoming parallel contacts Outgoing parallel contacts Central Processor Unit Cyclic Redundancy Check n (Item) Change Status Craft Terminal Connection Termination Point D Distant Alarm Distinguishing Attribute Value
Digital to Analog (converter/conversion) Direct Current Data Communication Channel Data Circuit Terminating Equipment Data Communication Network Digital Distribution Frame FEC Decoder Demodulator Demodulator Dialog Failure Diversity Degraded Minute Digital Radio Relay System Data Terminal Equipment Department of Trade and Industry Dual Tone Multi Frequency E Errored Block Errored Block Count European Broadcasting Union Equipment Controller Embedded Communication Channel External Communication Service Equipment Craft Terminal Equipment Engineering Equipment Failure 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
577 / 592
EFD EIA EIRP ELB EMC EMI EML EOW EPS ES ESD ETH ETR ETS ETSI EW EWH EWL EXCBER F FAD FCC FCS FD FE FEC FIT FPGA FR FSO FTP GA GND GNE H HBER HCS HD HDBK
Event Forwarding Discriminator Electronic Industries Association Equivalent Isotropically Radiated Power Event Log Browsing ElectroMagnetic Compatibility Electromagnetic interference Element Management Layer Engineering Order Wire Equipment Protection Switching Errored Second Electrostatic discharges ETHernet European Telecommunication Report European Telecommunication Standard European Telecommunication Standard Institute Early Warning Early Warning High Early Warning Low Excessive BER F Interface F (for Craft Terminal) or Fuse Functional Access Domain Federal Communications Commission Frame Check Sequence Frequency Diversity Front End Fast Ethernet Forward Error Correction (Code) Failure Unit Field Programmable Gate Array Failure Rate or Frequency Reuse Free Space Optics File Transfer Protocol G General Alarm or Gate Array Ground Gateway Network Element H Horizontal (polarization) High Bit Error Rate Higher order Connection Supervision History Data Handbook USER MANUAL APPENDICES
578 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
MEANING
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Tab. 80. List of abbreviations ABBREVIATION HDB3 HDLC HET HEW HK HSB or HST HMI HS HW HWP ICS ID IDU IEC IEEE IF IM IN IND INT I/O IP IRC ISO ITUR (*) ITUT (*) JRE LAC LAN LAPD LBER LC LCS LDI LED LEW LIM LLMAN LO LOF USER MANUAL APPENDICES High Density Binary 3 High level Data Link Control HETerofrequency High Early Warning HouseKeeping Hot Standby Human Machine Interface High Speed Hitless Switch Hardware Hardware Protection IJ Item Change Status IDentifier InDoor Unit
MEANING
International Electro technical Commission Institute of Electrical and Electronic Engineering Intermediate Frequency Information Manager Information Model Input Indicative alarm Internal Local Alarms Input/Output Internet Protocol International Radiotechnical Commission International Standards Organization International Telecommunication Union Radiocommunication International Telecommunication Union Telecommunication Java Runtime Environment L Local Access Control Local Area Network Link Access Procedure on Dchannel Low Bit Error Rate Loss of Configuration Lower Order Connection Supervision Local Defect Indication Light Emission Diode Low Early Warning Link Identifier Mismatch Alcatel Lower Layer MANager Local Oscillator Loss Of Frame 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
579 / 592
LOM LOS LS MAC MAJ MAU MCF MDT MEM MIB MIN MLR MOC MOD MSOH MSp MSw MTBF MTTR MUX NBF NDS NA NE NES NEBC NF NFD NG NML NMS NRZ NSA NTP NURG OBPS OC_R OCT ODF
Loss Of Multiframe Loss Of Signal Low Speed M Media Access Control Major (alarm) Medium Attachment Unit Message Communication Function Mean Dawn Time Memorization Management Information Base Minor (alarm) Manual Laser Restart Managed Object Class Modulator Multiplex Section OverHead Manual Switch to protecting channel Manual Switch to working channel Mean Time Between Failures Mean Time To Repair Multiplexer N Narrow Band Filter Nearend Defect Second Not Applicable Network Element Network Element Synthesis Nearend Errored Block Count Noise Figure Net Filter Discrimination Not Urgent Network Management Layer Network Management System Non Return to Zero Not Service Affecting Network Time Protocol Not urgent alarm O On Board Power Supply ODU Controller_Radio Office Craft Terminal Optical Distribution Frame USER MANUAL APPENDICES
580 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
MEANING
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Tab. 80. List of abbreviations ABBREVIATION ODU ODUC OFS OH O&M OIRT OOF OOS OR ORALIM OS OSI OSPF OUT OVF OW PABX PBX PC PDH PFAIL PI PLL PLM PM PPI ppm PPP PRx PRBS P/S PS PSA PSA C PSA D PSK PSR PSU PTx QAM USER MANUAL APPENDICES OutDoor Unit ODU Controller Out of Frame Second OverHead Operation and Maintenance Russian Regulatory Body Out Of Frame Out Of Service
MEANING
Logic sum/Loss of only one station battery ORing of station power supply alarm Operation System Open Systems Interconnection Open Shortest Path First Output Overflow Order Wire P Private Automatic Branch Exchange Private Branch Exchange Personal Computer Plesiochronous Digital Hierarchy Power supply failure Physical Interface Phase Locked Loop PayLoad Mismatch Performance Monitoring Plesiochronous Physical interface parts per million Point to Point Protocol Received power Pseudo Random Binary Signal Parallel/Serial converter Power Supply Protection Switch Actual Protection Switch Count Protection Switch Actual Duration Portable Service Kit Protection Switch Request Power Supply Unit Transmitted power Q Quadrature Amplitude Modulation 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
581 / 592
QOS RAI RAM RAPS RC RCK RCIM RDI RECC RECT REI REF REL RF RFC RI RL RLTS RMS RNURG RPI RPS RSOH RSPI RT RTF RTPC RURG Rx SA SC SD SDH SES SF SNMP SP SQ S/P SSF
Quality Of Service R Remote Alarm Indication Random Access Memory Radio Automatic Protection Switch Radio Controller Received clock Radio Channel Identifier Mismatch Remote Defect Indication Recommendation Remote Equipment Craft Terminal Remote Error Indication Reference Release Radio Frequency Remote Frequency Control Remote Inventory Received Level Received Level Threshold Second Root Mean Square Not urgent Alarm command. Lights up the relative rack red LED Radio Physical Interface Radio Protection Switching Regenerator Section OverHead Radio Synchronous Physical Interface Transceiver Remote Terminal Failure Remote Transmit Power Control Urgent Alarm command. Lights up the relative rack red LED Receiver/Received S Service Affecting or Service Alarm Service Channel or System Controller Space Diversity Synchronous Digital Hierarchy Severely Errored Second Signal Fail Simple Network Management Protocol Splitter Squelch Serial to Parallel Server Signal Fail USER MANUAL APPENDICES
582 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
MEANING
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Tab. 80. List of abbreviations ABBREVIATION STBY SU SW SWP TA TCO TCP TD TDM TEM TIM TL TLTS TM TMN TN TPH TP TPS TR TRCF TRCO TRIB TRSEF TS TRU TTF TTO TTP Tx U UAS UAT UDR UG UMTS URG URU USC USM USER MANUAL APPENDICES Standby Supervisory Unit Switch or Software Software Package T Remote Alarm Total Cost of Owner Transmission Control Protocol Layout drawing Time Division Multiplexer Transversal Electric Mode Trace Identifier Mismatch Transmitted Level
MEANING
Transmitted Level Threshold Second Transmission and Multiplexing Telecommunication Management Network Telecommunications Network Telephone Termination Point Tx Protection Switching TRansceiver Technical Report Total Received Correct Frames Total Received Correct Octets Tributary Total Received Service Errored Frames Time Slot Top Rack Unit Total Transmitted Frames Total Transmitted Octets Trail Termination Point Transmitter/Transmitted U Unavailability UnAvailable Second UnAvailable Time Unpressurized Rectangular Waveguide Type Urgent Alarm Universal Mobile Telecommunications System Urgent Underlying Resource Unavailable User Service Channel User Service Manager 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
583 / 592
USY UT UTRAN V VCO VF VLAN VSWR WAN WBF WIP WLT WS XPD XPIC XPI XPIF XPOL NOTES: (*)
Urban Haul Synchronous split mount Radio System Unavailability Time Universal Terrestrial Radio Access Network V Vertical (polarization) Voltage Controller Oscillator Voice Frequency Virtual Local Area Network Voltage Standing Wave Ratio W Wide Access Network Wide Band Filter Wireless IP Wireless Line Terminal Work Station X Cross Polar Discrimination Cross Polar Interference Canceller Cross Polar Interference Cross Polar Improvement Factor Cross Polar/Polarization
Owing to change of name, all documents issued by the two ITU committees (CCIR ND CCITT) in 1992 (and in some cases even before then) are classified as ITUR and ITUT, respectively.
584 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
MEANING
Acknowledgment: When an alarm is taken into account by the application, the operator has to acknowledge it to point out that he has seen it and that he will react in the right way. During alarm configuration it is possible to set a maximum delay for alarm acknowledgement. The operator can decide whether or not the alarm clear has to be acknowledged. Administrator: A user who has access rights to all the Management Domains of the Craft Terminal product. He has access to the whole network and to all the management functionalities. Alarm: An alerting indication to a condition that may have an immediate or potentially negative impact on the state of an equipment or the CT. An alarm is characterized by an alarm begin and an alarm end. Alarm Profile: Function allowing the assignment of severities to the alarms depending on their probable causes. Alarm Status: Identifies the type and severity of an occurring alarm. Board: A board is part of an NE. They are electronic cards that fit into slots in the NE. Compact Disk Read Only Memory: Data saving support from which the information can only be read. Is useful for stocking data due to its available memory space. Craft Terminal: Workstation or Personal computer (PC) from which local address to an NE is possible. It can be used to configure or perform monitoring tasks on the NE. Digital Communication network: Communication Network in which the transmission of data is done in a digitized format. Element Management Layer: This application is responsible for the configuration and management of Network Elements. Equipment Protection Switching: Used to provide protection for cards within an equipment to protect traffic in the event of card failure. Flushing: This deals with logs. When a log is flushed, all its records are deleted. Functional Access Domain: It defines the range of functions which are available to a specified user. Human Machine Interface: It is the graphical user interface application through which the operators interact with the system. History Report: This function enables operators to get information concerning performances, security or alarms on entities composing the network, or on the network itself. The operator specifies the time period for which he requires the report.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
585 / 592
Kilobits per second: Unit that correspond to the transmission of 103 bits every second. Line Terminal: A line terminal is the end point of a communication link. it is used to transmit or receive signals. They can undertake signal conversion functions (adapting a signal to two different transmission media) or multiplexing/demultiplexing functions. Logs: Logs are files used to store history data concerning the incoming notifications, operator commands and system alarms. The size of the log can be configured. Management Domain: The Craft Terminal product is partitioned into management domains for functional proposes. Each management domain is associated with functionalities that enable the operators to manage the NEs. Megabits per second: Unit that corresponds to the transmission of 106 bits every second. Network Access Domain: Defined as a set of Network Elements. NADs are used to define the set of Network Elements that a user can manage. Network Element: Either a telecommunication equipment or groups parts of a Telecommunication Network. Have characteristics compliant with CCITT recommendations. Network Management Level: Designates the management functions performed on networks elements assembled in a network. Notification: Spontaneous data received by the system concerning an NE. Operation System: A system dedicated to the supervision of NEs in a standard way, using protocols and interfaces. it offers to the operator a set of functions necessary to supervise the NEs. The 1353SH is an Operation System. Operator: The enduser of the Craft Terminal. He supervises a part of the network that is dependant on his user profile. Physical Interface: Electrical or Electrical/Optical transformers that decouple the line signals and adapt the form of signal for further transmission. This functional block also manages clock extraction, signal loss monitoring and loopback functions. Port: A physical point at which the Network Element can be attached to a transmission medium. A port is either a termination point or an origination point. Severity: Linked to alarms, severities indicate the magnitude related to the failure.
586 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
International Telegraph and Telephone Consultative Committee: Standard organization for telecommunications. Now called the ITUT (International Telecommunication Union).
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Telecommunication Management Network: Defines the concept of interoperable management of TNs. They provide an organized network structure to achieve the interconnection of the different components of the TN and the services to process the information. Telecommunication Network: Describes the network to be managed. Provides the transmission, the transport and the switching supports to the interconnected Network Elements. Terminal Point: Describes either the origin or the termination of a signal in an equipment. Is related to a port. Thresholding: This is the assignment of a specified value to monitored parameters ( for example BIt Error Rates) that, when exceeded, generate trouble indications. User Profile: Identifies the functionalities of the Craft Terminal to which a user has access. A finite number of predefined user profiles is determined by a fixed set of FADs. To give user access to Craft Terminal functionality, the administrator must assign a profile to a UNIX user account by choosing one among the predefined profiles installed with Craft Terminal. User Service Manager: These are presentation processes used by the Craft Terminal to manage the Human Machine Interface and facilitate the interaction with the product.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
587 / 592
588 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
The meaning of this appendix is to collect customer feedback about this handbook. Scope of this activity is the improvement and innovation of customer documentation through the understanding of customer needs. Your comments are welcome. Please send your comment also if you appreciate the handbook. You can send them to your Local Alcatel Technical Assistance Center. They will be addressed to the team in charge of the relevant manual. The following form supplies an example only of useful info, as a guide of the type of expected feedback. It is possible fill part of the form, add other data and so on. How to send feedback: copying the example form, filling it and sending it to your Local Alcatel Technical Assistance Center. In this case handbook data are already available at the page bottom. using the same form (if available) as a file in the relevant documentation CDROM, saving, filling and sending it by email to your Local Alcatel Technical Assistance Center. creating a dedicated form on paper or file and sending it to your Local Alcatel Technical Assistance Center.
We will take into account of your suggestion. We reserve to modify consequently the handbook according to the correctness and congruence of the suggestion and requests.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
589 / 592
CUSTOMER DOCUMENTATION FEEDBACK Product release, version: 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 Handbook type: USER MANUAL Handbook part number and edition: 3DB 16142 EAAA Ed.02 General evaluation SUBJECT Total evaluation Info quantity Info quality Info structure Consulting facility Layout Section evaluation SECTION Front matter 1 : System description 2 : NE management BY TCO Suite and CT 3 : Installation and commissioning 4 : Maintenance and upgrade 5 : Appendices Your comments (strictly necessary when value is less than 3) Suggestion for improvements Which subject to deepen: 5 (max.) 4 3 2 1 (min.) 5 (max.) 4 3 2 1 (min.)
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
Handbook data
How to deepen:
Other comments/suggestions:
Error identified
Reader Info Name: Company: Address: Email: Phone: Fax: Job: Date;
590 / 592
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from AlcatelLucent
591 / 592
All rights reserved Passing on and copying of this document, use and communication of its contents is not permitted without written authorization from Alcatel Lucent.
www.alcatellucent.com
THIS PAGE MUST NOT BE INCLUDED IN THE PRINTED HANDBOOK QUESTA PAGINA NON VA INSERITA NEL MANUALE STAMPATO
COD.MANUALE HDBK P/N:
3DB 16142 EAAA Ed.02 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL
HANDBOOK PRINT AND ASSEMBLY INSTRUCTIONS ISTRUZIONI DI STAMPA ED ASSIEMAGGIO DEL MANUALE
COMPOSIZIONE ED ASSIEMAGGIO DEL MANUALE: HANDBOOK COMPOSITION AND ASSEMBLY: SERVONO 5 SEPARATORI NUMERATI DA 1 A 5 5 SEPARATORS NUMBERED FROM 1 TO 5 ARE NECESSARY
STAMPARE FRONTE/RETRO RECTO-VERSO PRINTING No pagine (facciate) No pages TARGHETTE - LABELS Fig. 1. pg. 594 PARTE INIZIALE - FRONT MATTER INSERIRE SEPARATORE 1 - INSERT SEPARATOR 1 SECTION 1: SYSTEM DESCRIPTION INSERIRE SEPARATORE 2 - INSERT SEPARATOR 2 SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL INSERIRE SEPARATORE 3 - INSERT SEPARATOR 3 SECTION 3: INSTALLATION AND COMMISSIONING INSERIRE SEPARATORE 4 - INSERT SEPARATOR 4 SECTION 4: MAINTENANCE AND UPGRADE INSERIRE SEPARATORE 5 - INSERT SEPARATOR 5 SECTION 5: APPENDICES 499/592 592/592 407/592 498/592 307/592 406/592 139/592 306/592 29/592 138/592 1/592 28/592 numerate numbered da from a to
fase step
1 2 3 4 5 6 7 8 9 10 11 12
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
593 / 592
9400AWY Rel.2.1
7813151823252838 GHz shorthaul low/medium capacity digital microwave radio links
USER MANUAL
3DB 16142 EAAA Ed.02
USER MANUAL
3DB 16142 EAAA Ed.02
VOL.1/1
9400AWY Rel.2.1
7813151823252838 GHz shorthaul low/medium capacity digital microwave radio links
9400AWY Rel.2.1
7813151823252838 GHz shorthaul low/medium capacity digital microwave radio links
VOL.1/1
9400AWY Rel.2.1
7813151823252838 GHz shorthaul low/medium capacity digital microwave radio links SWP 9400AWY R.2.1 V2.1.1
3DB 16142 EAAA Ed.02 USER MANUAL VOL.1/1
Fig. 1.
594 / 592
FOR ALCATELLUCENT INTERNAL PURPOSE ONLY THIS PAGE MUST NOT BE INCLUDED IN THE PRINTED HANDBOOK QUESTA PAGINA NON VA INSERITA NEL MANUALE STAMPATO
Note for Customers: this part contains editorial information for Alcatellucent internal use only, and should have not be given to you. Nevertheless, in case you receive it, take into account that it does not contain information useful for you, so that you can simply ignore it.
3DB 16142 EAAA Ed.02 9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 USER MANUAL
WARNING: the source file folder contains also the pdf file with revision bars Notes on revision bars: revision bars point out changes with respect to the previous edition archived in PDM N.B. page numbers specified in table on page 593 are automatic and obtained by autoreference to tags of: section first page section last page, marked by the special component endofsection. WARNING: components endofsection have white color, to avoid their printing. DO NOT REMOVE THEM, otherwise table on page 593 will have NO TAGs. handbook last page, marked by the special component efme. N.B. component efme correspond to writing www.alcatellucent.com on page 592 . DO NOT REMOVE IT, otherwise all pages will have NO TAGs in footer. additional information (source file) in first catalog.
N.B.
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
595 / 592
FOR ALCATELLUCENT INTERNAL PURPOSE ONLY THIS PAGE MUST NOT BE INCLUDED IN THE PRINTED HANDBOOK QUESTA PAGINA NON VA INSERITA NEL MANUALE STAMPATO
2 HANDBOOK HISTORY
ED 01 02 DATE CHANGE NOTE (yymmdd) (ECO) 070802 080125 00000 57267 APPRAISAL AUTHORITY B.Gabbrielli, V.Fossati, C.Van Kerrebroeck M.Nosari, C.Van Kerrebroeck ORIGINATOR E.Corradini E.Corradini
SECTION 2: NE MANAGEMENT BY TCO SUITE AND CRAFT TERMINAL 21 22 23 24 25 26 27 28 29 211 SWP 9400AWY R.2.1 description Introduction on TCO Suite and CT views and menus Configuration Equipment Line Interface Radio External points Supervision Protection schemes Diagnosis
210 Loopbacks 212 Performance Monitoring 213 Software Download 214 MIB Management
596 / 592
FOR ALCATELLUCENT INTERNAL PURPOSE ONLY THIS PAGE MUST NOT BE INCLUDED IN THE PRINTED HANDBOOK QUESTA PAGINA NON VA INSERITA NEL MANUALE STAMPATO
Tab. 81. History of this Manual MANUAL EDITION SECTION 3: INSTALLATION AND COMMISSIONING 31 32 41 42 43 44 45 46 47 48 49 SWP installation in PC environment LineUp and Commissioning Maintenance Policy Set and use of EOW functions Maintenance Tools and Spare Parts First Level Maintenance Second Level Maintenance Spare Flash Card management and replacement procedures System hardware upgrade SWP download toward NE ECT & NE upgrade from V2.1.0 to V2.1.1 01 n n n n n n n n n n n n n n n n n n n m m m m m m m m m m 02 03 04 05
410 SWP deinstallation SECTION 5: APPENDICES A B C D E F G H I SafetyEMCEMFESD norms and equipment labelling TCO suite startup special conditions Additional SW installation operations for NE management through the NES ECT serial port General on Ethernet port characteristics and management ECTEquipment connection via public switched telephone network Part lists of tool kits Documentation guide List of symbols and abbreviations, Glossary of terms Customer documentation feedback
n n n
n m n
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
597 / 592
FOR ALCATELLUCENT INTERNAL PURPOSE ONLY THIS PAGE MUST NOT BE INCLUDED IN THE PRINTED HANDBOOK QUESTA PAGINA NON VA INSERITA NEL MANUALE STAMPATO 2.3 Notes on ED.02 draft and released editions
a) Draft editions neither validated nor officially released issue, for AlcatelLucent internal purposes: 1) 2) ED.02ADRAFT created on December 19th, 2007 ED.02BDRAFT created on January 22nd, 2008 First draft edition associated to SWP final version V2.1.1 . It has been created starting from the ED.01 archived in PDM, and introducing the following modifications: changes for V2.1.1 : general information in para.11.2 on page 32 and chapter 21 from page 141 changes for elimination of oldtype Data plugin (2 Fast Ethernet ports): System & HW on pages: 38 , 42 , 44 , 45 , 68 , Tab. 7. from page 70 , 76, 282 , 331 (moreover eliminated two pages after page 333 ), 378 , 391 , 469 , 474 , and whole Appendix D from page 547 SW management on pages: 210 , 231 , 347 , 349 to 351 updating of Enhanced Ethernet port characteristics and management from prerelease V2.1.1* to final V2.1.1: modified Appendix D point [8] on pages 551 and 552 other changes for GUI modifications from prerelease V2.1.1* to final V2.1.1 on pages: 156 to 158 , 166 , 203 , 231 and 232 , 351 and 352 , 363 changes for RF Loopback on pages 46 , 268 , 269 , 385 ; 386 (removed test and report regarding RF loopback, done also in TRS document ED.03) changes for RTPC on pages 128 , 238 changes for Transmitted power at antenna port on page 130 changes for Power Measurement on page 243 changes for Flash Cards: updated P/Ns, denominations and software labels in Tab. 23. on page 93 inserted new identification labels on pages 94 and 95 updated description of documentation set on pages 59 , 567 , 569 and 570 corrections and improvements: improved description of ECT & NE upgrade from V2.1.0 to V2.1.1 from page 495 (and associated WARNINGs on pages 486 and 493 ) elimination of enclosed documents (same information put in new Appendix F on page 563 ) new appendix Customer documentation feedback on page 589 new standardized template look continues..
598 / 592
FOR ALCATELLUCENT INTERNAL PURPOSE ONLY THIS PAGE MUST NOT BE INCLUDED IN THE PRINTED HANDBOOK QUESTA PAGINA NON VA INSERITA NEL MANUALE STAMPATO
..continues corrections submitted for 9400AWY 2.0.6 User Manual ED.01ADRAFT, considered applicable also to this 9400AWY 2.1.1 User Manual: submitted by P.Garofoli: throughout the handbook: integrated antenna replaced by full integrated antenna Fig. 41. , Fig. 42. , Fig. 43. and Fig. 44. on pages 114 to 117 submitted by Y.Y.Lebret: ETSI reference standard in para.15.1.1 on page 129 submitted by B.Magnan: new para.12.6.9 on page 65 ; new N.B. in Tab. 22. on page 90 ; new WARNING in para.23.4 on page 210 ; one line deleted on page 230 Sample time on page 241 ; directory on pages 241 and 244 ; EPS Lockout description on page 259 ; new WARNING in para.29.2.2 on page 261 simplified description of Available loopbacks in para.210.2 on pages 269 to 271 Errors found in previous edition have been corrected. Revision bars point out major (listed above) and minor (not listed above) modifications of ED.02ADRAFT and ED.02BDRAFT with respect to ED.01. Revision bars in correspondence of empty lines or empty table rows, point out parts eliminated or shifted in other places of the handbook Tab. 81. from page 596 shows all parts modified (for major and minor changes). N.B. NO TAG markers will be replaced by correct values in final edition
9400AWY Rel.2.1 SWP 9400AWY R.2.1 V2.1.1 3DB 16142 EAAA Ed.02
599 / 592
FOR ALCATELLUCENT INTERNAL PURPOSE ONLY THIS PAGE MUST NOT BE INCLUDED IN THE PRINTED HANDBOOK QUESTA PAGINA NON VA INSERITA NEL MANUALE STAMPATO
3) Results of peer review held on January 25 , 2008 Main additional changes with respect to ED.02BDRAFT: corrections submitted by E.Carpine: on page 88 : removed this mode includes DCE behavior from CODIR description on page 89 : Inframe description corrected. Moreover line It is also necessary that the farend E1#1 tributary is enabled and successfully provisioned added also on pages 203 and 363 corrections submitted by A.Goncalves: in Appendix D General on Ethernet port characteristics and management : removed all warnings on pages 549 , 550 , 552 eliminated the RF loopback detailed scheme, that was present on page following 268 corrections submitted by C.Van Kerrebroeck: throughout the handbook: SWP 9400AWY IDU32 V2.1.1 replaced by SWP 9400AWY R.2.1 V2.1.1 on page 349 : and two Ethernet port configuration screens replaced by and four Ethernet port configuration screens in Tab. 23. on page 93 : eliminated Software Key P/Ns. Moreover, throughout the handbook: Software Key replaced by Software Label in Product Release Note on page 571 : removed the lists of DDTs additional corrections for harmonization with AWY 2.0.6 User Manual ED.01: corrected para.12.6.9 on page 65 in Tab. 32. on page 109 : 14700 instead of 15988 for 3CC13711ABXX in para.23.2.3 on page 195 : .. if in IP Routing Protocol the OSPF protocol has been selected, it is possible to create OSPF areas replaced by: .. if in IP Routing Protocol the OSPF protocol has been selected, it is possible to choose OSPF areas in para.23.2.4.3 on page 200 , added Id description
b)
Validated and released edition: ED.02 created on January 25th, 2008 is the first validated and released edition associated to SWP 9400AWY R.2.1 V2.1.1 final Version V2.1.1 , and fully annuls and replaces previous ED.01 (same P/N). Errors found in previous edition have been corrected. Revision bars point out all modifications of final ED.02 with respect to ED.01. Revision bars in correspondence of empty lines or empty table rows, point out parts eliminated or shifted in other places of the handbook. N.B. Tab. 81. from page 596 shows all parts modified (for major and minor changes). N.B. The handbook officially distributed to Customers (as pdf file inside the specific Customer Documentation CDROM) contains neither revision bars nor this part (handbook editorial information). Source and pdf files of final ED.02 with revision bars are archived in PDM as specified in chapter 1 on page 595
600 / 592