FLCInst 78 43 24169 BE PC 02

INSTALLATION & STARTUP HANDBOOK
1678MCC
FLC Software
Release 4.3
3AG 24169 BEAA Ed. 02
3AG 24169 BEAA Ed. 02
All rights reserved. Passing on and copying of this

document, use and communication of its contents
not permitted without written authorization.
1678MCC R4.3 INSTALLATION & STARTUP

HANDBOOK FLC SOFTWARE
02
070320
1678MCC R4.3.1
B. Wilke
A. Willscher
01
071218
1678MCC R4.3
B. Wilke
A. Willscher
ED
DATE
CHANGE NOTE
APPRAISAL AUTHORITY
ORIGINATOR
1AA 00014 0004 (9007) A4
1678MCC R4.3
INSTALLATION & STARTUP HANDBOOK FLC
SOFTWARE
ED
02
3AG 24169 BEAA PCZZA
3/83
1AA 00014 0004 (9007) A4
ED
02
4/83

TABLE OF CONTENTS

-1
HANDBOOK STRUCTURE AND CONFIGURATION CHECK . . . . . . . . . . . . . . . . . . . . . . . .

-1.1
-1.2
-1.3
-1.4
-1.5
-1.6
-1.7
-1.8
-1.9
-1.10
-1.11
-1.12
-1.13
-2
General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handbook Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Customer Documentation Alcatel 1678 Metro Core Connect . . . . . . . . . . . . . . . . .
Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handbook Change History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compliance with European Norms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Safety Norms and Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other Norms and Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
List of Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Information on AlcatelLucent Customer Documentation . . . . . . . . . . .
Registered Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Agreements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Service Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
9
9
10
10
11
11
12
13
14
14
15
15
INITIAL INSTALLATION OF THE FLC SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

-2.1
-2.2
Preconditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Detailed Description of the FLC Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.2.1
Preparation of the InstallServer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.2.2
Preparation of the FLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.2.3
FLC Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.2.4
Start Application on both installed FLCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.2.5
Connect the Craft Terminal to the 1678 MCC . . . . . . . . . . . . . . . . . . . . . . . . .
-2.2.6
Get Local Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.2.7
Create Main Shelf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.2.8
Reset the MATRIX (SLC) Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.2.9
Set the Host ID and the OSPF Interface for Local Ethernet . . . . . . . . . . . .
-2.2.10
Update the FLC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.2.11
Configure the NTP Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.2.12
Event Log Management (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.2.13
Checks after FLC Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.3 Short Description of the FLC Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.3.1
Preparation of the Installation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.3.2
FLC Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.3.3
Final configuration steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.3.4
Event Log Management (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-2.3.5
Checks after FLC Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
17
21
21
27
28
46
48
51
52
56
57
60
65
66
68
71
71
72
73
73
73
-3
TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
-4
PROCEDURE FOR POST INSTALLATION OF ION75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

-4.1
-4.2
-4.3
-4.4
-4.5
-4.6
1AA 00014 0004 (9007) A4
ED
General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preconditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Start the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
77
77
77
78
78
79
02
5/83
TABLE OF FIGURES
1AA 00014 0004 (9007) A4

Figure 1. How to use the FLC debug cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 2. How to connect the FLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3. Copy Wizard for CORE CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4. Copy Wizard for SKY CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5. Copy Wizard for ION CDROM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6. IP Configuration of the InstallServer (Part 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9. Welcome to FLC Installation Wizzard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10. Configure the NE (Network Element) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11. Select the Software to be installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12. Configure the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13. Configure the FLC Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14. How to get the FLC MAC address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15. QStack Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16. Select both FLCs to be installed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17. Reset the FLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18. Start Netboot Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19. Starting BOOTP Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20. Download of the Netboot Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21. TFTP Download of the Netboot Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22. aiGuide successfully finished . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23. aiGuide successfully finished (ignore the Error Message) . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24. The Installation has been finished successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25. Start Supervision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26. Shutdown of the LowerLayerManES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27. Show Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28. Create Main Shelf (Rack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29. Create Main Shelf (NGTRU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30. Create Main Shelf (MCC1678) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31. Configure the Host ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32. Enable OSPF Interface for Local Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33. CS Equipment Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34. IP DCN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35. Other IP Hosts Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36. OSI DCN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37. NTP Time Synchronization Status on the emServ Board . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38. NTP Time Synchronization Status on the emCong Board . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39. NTP Time Synchronization Status on the dcrServ Board . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40. NTP Time Synchronization Status on the dcrCong Board . . . . . . . . . . . . . . . . . . . . . . . .
ED
18
19
23
24
25
26
27
28
31
32
33
35
36
37
37
38
39
40
41
42
43
44
44
46
50
51
52
54
55
56
58
60
61
62
63
64
69
69
70
70
02
6/83
1AA 00014 0004 (9007) A4
ED
02
7/83

1AA 00014 0004 (9007) A4
ED
02
8/83


HANDBOOK STRUCTURE AND CONFIGURATION CHECK
1.1
General Information
WARNING
Strict compliance with the instructions and procedures specified in the product documentation (refer to
product release note for the complete list of applicable manuals) is the precondition of the enforceability
of such warranty claims against AlcatelLucent.
Warranty claims which result from noncompliance with the defined procedures cannot be enforced
against AlcatelLucent.
NOTICE
The product specification and/or performance levels contained in this document are for information
purposes only and are subject to change without notice. They do not represent any obligation on the part
of AlcatelLucent.
COPYRIGHT
NOTIFICATION
The technical information of this manual is the property of AlcatelLucent and must not be copied,
reproduced or disclosed to a third party without written consent.
1.2
Handbook Applicability
This handbook refers to the Multiband Multiservice Connect 1678 Metro Core Connect (MCC) R4.3.1
which belongs to the AlcatelLucent Optics Cross Connect product family.
In general the system is referred to as MCC or NE only.
Screen prints are inserted as examples and do not necessarily show the actual Product or Release name
in the windows title.
1.3
Customer Documentation Alcatel 1678 Metro Core Connect
Refer to the Technical Handbook to obtain the following information:
Customer Documentation
Service Documentation
1AA 00014 0004 (9007) A4
The installation of the Craft Terminal is described in the CT Basic Operators Handbook.
ED
02
9/83
1.4
Target Audience
This handbook describes the procedures for the initial installation and start-up of the 1678MCC software.
This handbook is intended for service staff trained for installing and starting-up cross-connect systems.
The operators should have the following technical knowledge:
Good knowledge of UNIX (especially system configuration, process management, permissions,

system administration)
Detailed knowledge of the 1678MCC hardware configuration
Detailed knowledge of the Craft Terminal (CT) and First Level Controller (FLC) software and the
combining with the hardware
Use of the 1678MCC via control software of the CT
Experience in installing software
1.5
Handbook Change History
Ed.02:
1AA 00014 0004 (9007) A4
Ed.02 created in March, 2008 contains the following updates for R4.3.1:
Chapter Initial Installation of the FLC Software (modified: Configure NTP Servers using NM/CT not
using aiGuideWizzard).
Chapter Procedure for Post Installation of ION75 (modified: Warning that Event Log Management
must be disabled when installing GMRE).
DDTS SLSks50241: EVL: Dialogue hanging after receive data (SLSks50348).
ED
02
10/83
Ed.01:

Ed.01 has been created in December 2007 for product release 4.3. This edition is based on the 3AG 24169
BDAA PCZZA Ed.01 of R4.2. The main updates for R4.3 are:
Adaptions for FLC Installation procedure in R4.3:
Added descriptions for GMRE (i.e. ION<xx><yyy> SW build).
Rework of inital FLC installation.
Chapter Procedure for Post Installation of ION75 (modified).
DDTS SLSks44683: FLCs after Coldstart (Power down/up) in state Maintenance.
DDTS SLSks45344: 1678MCC Event LOG Management.
DDTS SLSks46834: FLC Installation / Firewall indication missing.
DDTS SLSks45460: NTP configuration does not reject FLC addresses.
DDTS SLSks48512: Downgrade FLC: check criteria for nr of lapds wrong.
1.6
Compliance with European Norms
Electromagnetic Compatibility (EMC)
Safety
1.7
Safety Norms and Labels
1AA 00014 0004 (9007) A4
Refer to the Safety Instructions, 3AL 24198 AAAA, to obtain the following information:
General Safety Rules
Labels
Several Dangerous Conditions
ED
02
11/83
1.8
Other Norms and Labels

1AA 00014 0004 (9007) A4
Electromagnetic Compatibility (EMC)
General Norms Installation
General Norms Turnup & Commissioning, Operation
General Norms Maintenance
Electrostatic Dischargers (ESD)
Suggestions, Notes and Cautions
Labels affixed to the Equipment
ED
02
12/83
1.9
List of Abbreviations

CONGIHC Control and General Interface High Capacity Board

CT
Craft Terminal
DCC
DCR
Data Communication Channel

DCC Router (FLC)
EM
EMC
ESD
Embedded Module (FLC)

Electromagnetic Compatibility
Electrostatic Dischargers
1AA 00014 0004 (9007) A4
FLC
First Level Controller
FLCCONGI First Level Controller + Control and General Interface Board
FLCSERV First Level Controller + SERVICE Board
ED
GMPLS
GMRE
Generalized Multiprotocol Label Switching

GMPLS Routing Engine
HPROT
HPROT16
HW
High Speed Protection Board

16x High Speed Protection Board
Hardware
ISSB
ISPB
ISU
Intra Shelf Serial Bus

Intra Shelf Parallel Bus
In Service Upgrade
LAPD
LAX20
LAX40
Link Access Procedure on D channel

LO Adaption and Matrix Board 20G
LO Adaption and Matrix Board 40G
MCC
MX
MX160
MX320
MX640
Metro Core Connect

Matrix Board
Matrix Board 160GBit/s
NGTRU
NM
New Generation Top Rack Unit

Network Manager
PSF
Power Supply Filter Board
RIM
Remote Inventory Memory
SLC
SUT
SW
Second Level Controller

Supervisory Unequipped Termination
Software
TIM
TMN
Trace Identifier Mismatch

Telecommunication Management Network
VHM
Virtual Hardware Manager
02
13/83
1.10
General Information on AlcatelLucent Customer Documentation

Products, Productreleases, Versions and Customer Documentation
Handbook Supply to Customers
Aims of Standard Customer Documentation
Handbook Updating
Changes introduced in the same Product Release (same Handbook Part Number)
Notes for Handbooks relevant to Software Applications
Changes due to new Product Version
Documentation Supply on CDROM
Contents, Creation and Production of a CDROM
Use of the CDROM
CDROM Identification
1AA 00014 0004 (9007) A4
1.11
Registered Trademarks
HP and HP OpenView are registered trademarks of the HewlettPackard Corporation
UNIX is a registered trademark of UNIX System Laboratories, AT&T
All other names, products and services mentioned are trademarks of their respective holders
ED
02
14/83
1.12
Agreements

Throughout this document the installation personnel are referred to as users. For standard UNIX
procedures the document makes use of UNIX terminology.
User commands appear in the following manner:
command
Names and addresses to be defined by the user are marked with relation marks (<name to be defined>).
(1) Installation Steps are Illustrated as Numbered Headers

~
Inputs and other actions to be performed by the user are marked with an action point.
Notices to take into account to avoid operational errors
Is used to mark pieces of information provided to avoid operational errors that lead to
inconsistent or corrupted data.
1.13
Service Information
1AA 00014 0004 (9007) A4
In case of problems with the system 1678MCC, contact your Technical Assistance Center or Technical
Excellence Center for information.
ED
02
15/83
1AA 00014 0004 (9007) A4
ED
02
16/83

INITIAL INSTALLATION OF THE FLC SOFTWARE

This document describes the initial installation of both FLCs for the 1678 Metro Core Connect R4.3.1.
NOTE: Screen prints are inserted as examples and do not necessarily show the actual release names.
2.1
Preconditions
The operator has to be familiar with LINUX and Windows2000/WindowsXP operating systems.
Two redundant FLCs have to be available and equipped with an EM04A and a DCR board.
Notice the label on both EM boards (decimal number).
To install both FLCs at the same time, a hub is needed during installation to connect both FLCs to
the CT PC/Laptop.
A DebugCable (console cable) for connection between installServer and FLC (port A) has to be
available (only used during the installation). For PCs/Laptops with only one serial port you also need
a USB to serial converter.
FLC
Installserver PC/Laptop
9 pol DSUB female
8 pol Western connector
1
Length ~ 10 m
to EM
COM1
9600 bd
4
5
E
F
A
B
2
3
4
5
C
D
6
7
8
to DCR
COM2 or
COM5
38400 bd
Line D = GND
COM5 ( usb5toserial )
1AA 00014 0004 (9007) A4
Figure 1. How to use the FLC debug cable
ED
02
17/83
When plugging out the console cable always plug out the FLC side of the cable first to
avoid blocking of the DCR board.

FLC
DCN/HUB
CT
Installserver EM
DCR
LAN Cable
FInterface
Debug Cable
Figure 2. How to connect the FLC

It has to be checked that the voltage difference between the electrical ground of the
1678MCC and the ground wire of the 110/220 V NET is lower than 3 V! In case of a higher
voltage difference please contact your Technical Assistance Center before proceeding
further.
Check the voltage difference by connecting the AC input of a voltmeter to the 1678MCC rack
and the V input to the ground wire of a power socket.
An FInterfaceCable for connection between the CT and FLC has to be available.
CD-ROMs with
the FLC Platform Software (CORE01J build).
the FLC Application Software (SKY55xyz build).
the FLC Application Software (ION75xyz build, if required).
The CORE01J CD has to be copied (inserted) first to the PC/Laptop (refer to 2.2.1 c ).
The GMRE nodeAddress has to be in another subnet as the FLC.

recommendation: 10.10.255.<number of node>
1AA 00014 0004 (9007) A4
ED
The following data has to be available for the configuration of the FLC (after installation):
required protocol stack (QB3 or RFC1006).
Area address and System ID (has to be unique; default system ID is the MAC address of
EMService board). For an address example see Figure 15. on page 36.
02
18/83
The following data has to be available (requested by the aiGuideWizzard tool, but not in the order
given below).
the software versions to be installed
CORE01J, SKY55xyz, ION75xyz

FLCCongi MACAddress of the EM04A board

FLCService MACAddress of the EM04A board
IP address of the subnet
IP address of the router (gateway)
optional (in case of using DCN)
IP address of NTP time server(s)

Subnet mask
IP address of the local Craft Terminal PC/Laptop
can be the installServer PC/Laptop itself
IP address of the active EM
x.y.z.14
IP address of the active DCR
x.y.z.12
IP address and hostname of the dcrServ
x.y.z.2
IP address and hostname of the dcrCong
x.y.z.3
IP address and hostname of the emServ
x.y.z.4
IP address and hostname of the emCong
x.y.z.5
Q stack area and Sysid of FLC
default MAC address of emServ board
The following data has to be available (requested by the EP tool):
Required OSI DCN protocol stack PCCT (RFC1006)
Area address and System ID of PCCT
Required OSI DCN protocol stack NM (QB3, RFC1006) Area address and System ID of NM
Other IP Hosts
IP address and/or host name of NM/CT
The configuration of the main NTP server is mandatory.

Do not use FLC or ES64 addresses as NTP server address. In case of problems, ask your
local network administrator for help.
A properly installed and configured CT PC/Laptop according to the CT Installation description in the
CT Basic Operators Handbook (chapter Software Installation):
1AA 00014 0004 (9007) A4
Cygwin has to be installed as user install!

(see CT Basic Operators Handbook, chapter Installation of Components)
User install must not be deleted before its resources are deallocated (deleted).
Otherwise there is no longer access to these resources.
ED
The user install has to have Administrator rights.
Minimum hardware requirements of CT/InstallServer PC/Laptop:
two serial interfaces (COM1/COM2) or one serial and one USB interface (requires USB2
serial adapter, COM1/COM5)
2 GB free disk space on C:
No Hummingbird/Exceed software must be installed (i.e. a file like

C:\WINNT\System32\Hummingbird\Connectivity\7.00\Socks\socks must not exist).
e.g.
02
19/83

A terminal emulation program (e.g. Tera Term Pro) used as terminal to the console of EM04A
and DCR boards.
A hexcalculator (for calculating the MACaddress of the FLC from EM board label)
The installServer has to be rebooted after each changing of its LAN configuration (LAN or
FInterface connection)
If you use a Laptop or Notebook PC as installServer, disable the power save option.
1AA 00014 0004 (9007) A4
Disable the firewall on the installServer PC/Laptop during the installation procedure!
ED
02
20/83
2.2
Detailed Description of the FLC Installation

This chapter describes the installation of both FLCs at the same time.
The whole installation has to be executed as user install.
All screen prints shown in this handbook are examples and do not necessarily show the actual product
or release names.
2.2.1
a)
Preparation of the InstallServer
Delete the following links/directories on your installServer using a cygwin window:

cd /home/install
rm rf aiGuide
rm rf installServer
1AA 00014 0004 (9007) A4
rm rf bin
b)
Delete already available SKY and/or ION builds on your installServer which are not required anymore
(to provide enough space on disk).
Delete the old SKY/ION directories in C:/ALCATEL/release.
Delete the old SKY/ION links in the /home/install directory.
c)
Insert the CORE CDROM into the CDROM drive. If the Software copy tool does not start
automatically, make sure that the Autostart feature of Windows is enabled for the CDROM drive.
Then remove and insert the CDROM into the CDROM drive again.
ED
02
21/83

Figure 3. Copy Wizard for CORE CDROM
1AA 00014 0004 (9007) A4
Press the Continue button.

Press the Finished button at the end of the CORE copy.
Remove the CORE CDROM from the CDROM drive.
ED
02
22/83
Insert the SKY CDROM into the CDROM drive.

d)
Figure 4. Copy Wizard for SKY CDROM
1AA 00014 0004 (9007) A4

Press the Finished button at the end of the SKY copy.
Remove the SKY CDROM from the CDROM drive.
ED
02
23/83
Insert the ION CD into the CDROM drive if required (only GMRE environment).

e)
Figure 5. Copy Wizard for ION CDROM

Press the Finished button at the end of the ION copy.
Remove the ION CD from the CDROM drive.
f)
Setup of the sibdl tool by executing the following command using the Windows2000/WindowsXP
explorer:
C:\ALCATEL\release\CORE01J\FLC\pack\rawloader\SIBDL_setup_2_2_0.exe
Double click on the file SIBDL_setup_2_2_0.exe
Select English (United States) as language in the Choose Setup Language dialog and press the
OK button.
Select the C:\ALCATEL\SIBDL_2.2.0 directory.
The View readme file button can be deselected. Press the Finish button at the end of the sibdl
setup.
Close the readme.txt file with File > Exit in case of selected View readme file button.
The SIBDL tool is installed now.
1AA 00014 0004 (9007) A4
Press the OK button.
ED
02
24/83
g)
Adapt the network configuration of the installServer PC/Laptop to the network configuration of the
FLC. Use therefore a free IP address in the subnet of the FLC to be installed.

Only one LAN interface has to be configured on the installServer! Disable all other LAN
connection used before (example: LAN used for FInterface, PCMCIA or a second LAN
interface).
Start > Settings > Network and DialUp connections
Select Local Area Connection > Properties
1AA 00014 0004 (9007) A4
Figure 6. IP Configuration of the InstallServer (Part 1)
ED
02
25/83
1AA 00014 0004 (9007) A4

Select Internet Protocol (TCP/IP) > Properties
ED
02
26/83
Configure the IP Configuration of the installServer using the Use the following IP address dialog.
The configuration of DNS server is not necessary.

Use the corresponding IP address

e.g.:
IPaddress:
10.10.85.99
Subnetmask:
255.255.255.0
DefaultGateway: 10.10.85.254

Disable and enable the LAN interface.
1AA 00014 0004 (9007) A4
2.2.2
Preparation of the FLC
a)
Connect both FLC LAN interfaces via a hub to the installServer PC/Laptop.
b)
Connect the console cable between the COM1 and COM2/COM5 of the installServer PC/Laptop with
the console interface on the FLC. Refer to Figure 1. on page 17.
The console cable has to be plugged in on both serial interfaces of the installServer.
Otherwise the DCR board may be blocked.
ED
02
27/83
2.2.3
FLC Installation

2.2.3.1
a)
Configure Console Connection between InstallServer and FLC
Open two console windows for each FLC on the installServer PC/Laptop.
EM board (COM1; 9600 baud)
DCR board (COM2/COM5; 38400 baud)
b)
Configure the Console window (installServer <> EM) using the serial interface COM1.
COM1
c)
Baud Rate
Data
Parity
Stop
Flow control
Scroll buffer
9600
8 bit
none
1 bit
none
500 lines
Configure the Console window (installServer <> DCR) using the interface COM2 or COM5.
COM2/COM5 Baud Rate
Data
Parity
Stop
Flow control
Scroll buffer
38400
8 bit
none
1 bit
none
500 lines
1AA 00014 0004 (9007) A4
Refer to Figure 1. on page 17 .
ED
02
28/83

2.2.3.2
Check the UBoot Loader Software
a)
Change to the DCR console window on the PC/Laptop.
b)
Press the reset button on the FLC once (for less than 3 seconds) to reset the DCR board.
c)
Stop the boot sequence by
sending a break command on the DCR console window when requested (pSH+> prompt)
or
Hit any key in the DCR console window when requested (=> prompt)
How to stop the boot sequence depends on the already installed rawloader/boot loader version. After
stopping the boot sequence you will get the pSH+> or => prompt.
d)
Check the uboot version using the following command :

pSH+> raw
or => ver
UBoot 1.1.1 (May 4 2005 05:34:18) Alcatel SEL AG Stuttgart, Build: @(#)SEL Stuttgart
SCM ID: UBODCR01C
The uboot version must be UBODCR01C or higher.
In case of wrong uboot version please contact your Technical Assistance Center
before proceeding further.
1AA 00014 0004 (9007) A4
e)
ED
Reset the DCR board

pSH+> reset or
=> reset
02
29/83
2.2.3.3
Start the Installation

During installation both FLC LAN interfaces must be connected via a hub to the
installServer PC/Laptop.
a)
Start the aiGuideWizzard tool as user install using a cygwin window:

cd /home/install/SKY55<xyz>
./aiGuideWizzard
b)
Enter the required FLC configuration data.
Figure 9. Welcome to FLC Installation Wizzard

Select NEW and click on the Load button.
1AA 00014 0004 (9007) A4
HINT:
ED
If you want to use an existing configuration, choose the related NE name from the list
and click on the Load button.
02
30/83

Figure 10. Configure the NE (Network Element)

Enter the name and location of the NE.
Use only alphanumeric characters, underscore or dash (0-9a-zA-Z_) for NE name and NE
location. Special characters are not allowed.
HINT:
You can modify the NE name/location using special characters after installation (in the
Network Element Synthesis View of the NM/CT).
1AA 00014 0004 (9007) A4
Press the Next button.
ED
02
31/83

CORE01J
SKY5530A
ION7505Y
Figure 11. Select the Software to be installed

Enter the software packages to be installed. Select the ION package only in case of GMRE
environment.
1AA 00014 0004 (9007) A4
ED
02
32/83
1AA 00014 0004 (9007) A4
ED
02
33/83


10
10
83
255 255 255 0

10
10
83
254
10
10
83
10
Figure 12. Configure the Network

Enter the correct IP address of the default gateway (must be the router address), if an NE should
have a connection to DCN. Enter the IP address for the local Craft Terminal.
The subnet address, the subnet mask and the gateway will be automatically retrieved from the
installServer configuration.
1AA 00014 0004 (9007) A4
ED
02
34/83

Figure 13. Configure the FLC Hosts

Enter the IP addresses of the active EM, active DCR, emCong, emServ, dcrServ and dcrCong board.
For the emCong, emServ, dcrServ and dcrCong also a hostname is required.
The hostnames length of emCong, emServ, dcrServ and dcrCong must be < 18
characters.
The MAC address of the emCong and emServ must be configured in the following way:
00C03A2Dxxxx
where
1AA 00014 0004 (9007) A4
NOTE:
ED
MAC address of the EM board
the first 4 bytes 00C03A2D are always fix

the last two Bytes xxxx can be retrieved from the paper label on the EM board.
This value on the paper label has to be converted from decimal to hex. The complete MAC
address must be entered in hex format into the dialog shown in Figure 13.
In case of missing redundant FLC a fictive MAC address has to be used instead
(e.g. 00C03A2D0000).
02
35/83
FLC

DCR board
Label on the EM Board

( decimal value )
EM board
Figure 14. How to get the FLC MAC address

Enter the GMRE node address: eg. 10.10.255.<number_of_the_node>
Figure 15. QStack Configuration
1AA 00014 0004 (9007) A4
The stack is being configured automatically for both QB3 and RFC1006!
ED
02
36/83

Enter the used stack configuration (Area address and System ID) for the 1678MCC.
Area address must consist of 26 digits
System ID must consist of 12 digits

By default the MAC address of the emServ board is taken as system ID. Therefore a valid
MAC address must be entered for the emServ board (refer to Figure 13. ). But you may
enter any other unique System ID (e.g. MAC address of emCong board) in the previous
dialog (refer to Figure 15. ).
The number of entered digits must be correct!

Do not press the Start installation button.
1AA 00014 0004 (9007) A4
Figure 16. Select both FLCs to be installed
ED
02
37/83
Select both FLCs to be installed. Check the network cables. If done, select I have checked the
network cables.

Select I have started network boot on the FLC .

For both FLCs:
If the FLC is not yet in MENMON mode you must reboot the FLC by pressing the reset button gently
for about 3 seconds. Both, EM and DCR board will reboot in this case. Interrupt the booting
sequence by pressing the ESC button just after the message Init ECC memory... appears (refer
to Figure 17. ).
Figure 17. Reset the FLC

For both FLCs enter the following commands in the MENMON mode:
MenMon> eedef
1AA 00014 0004 (9007) A4
MenMon> rst
ED
02
38/83
1AA 00014 0004 (9007) A4
Figure 18. Start Netboot Sequence
Do not interrupt the booting sequence.
ED
02
39/83


Figure 19. Starting BOOTP Requests

Press Start Installation button in the aiGuideWizzard just after the following message appears
(refer to Figure 19. ):
Searching for server (BOOTP) ... .
1AA 00014 0004 (9007) A4
This operation will start the FLC installation.
ED
02
40/83

2.2.3.4
a)
Download of the CORE, SKY and ION Software
The netboot_xxx.img should download now. Do not stop the booting sequence on the EM
console.
1AA 00014 0004 (9007) A4
Figure 20. Download of the Netboot Image
ED
02
41/83

SKY5530A
SKY5530A
SKY5530A
SKY5530A
1AA 00014 0004 (9007) A4
Figure 21. TFTP Download of the Netboot Image

b)
After loading of the netbootxxx.img image, the netboot linux will be uncompressed and installed on
the FLC. This netboot linux will trigger the CORE build installation (copy and unpack of the
montavista linux) on the EM and DCR board.
c)
Subsequently the SKY installation will be started automatically.
d)
The ION installation will be started automatically (only if the ION installation is required).
e)
At the end of the installation a saveCurrentInstallation will be executed.
ED
02
42/83

Figure 22. aiGuide successfully finished
Figure 23. aiGuide successfully finished (ignore the Error Message)
1AA 00014 0004 (9007) A4
Ignore the displayed Errors or Warnings as long as the status report shows 0 errors, 0 warnings
and the aiGuide was SUCCESSFUL message appears.
ED
02
43/83
f)
Due to the fact that the installation is running automatically, the installation can only be observed.
Other debugging hints are:

On installServer:
If BOOTP requests are not responded you may stop the aiGuideWizzard.
After stopping the aiGuideWizzard, execute the following command in a cygwin window
on the installServer:
> /home/install/installserver/bin/installserver dhcpreport
This command will print out all detected incoming BOOTP requests and you willll easily
see if you got an request with an unexpected MAC address.
/home/install/installserver/var/log/dhcpd.log shows incoming BOOTP requests.
/home/install/installserver/etc/ contains config files of installServer and dhcp.
with ps ef the running daemons can be checked. This can be alternatively checked via:
./installserver/bin/installserver status.
On the FLC:
g)
on FLC the progress can be supervised in the file /var/aiGuide/aiGuide.trace .
Wait until the installation is completed using the console window (refer to Figure 23. ), the
aiGuide.trace file of the the FLC installation wizard window.
Do not press the Exit button until the installation is finished.
1AA 00014 0004 (9007) A4
If the installation is finished successfully (message aiGuide was SUCCESSFUL appears in the
aiGuide.trace file or the console window) complete the installation by clicking on the Exit button
in the FLC installation wizard window.
ED
02
44/83

Figure 24. The Installation has been finished successfully

The installation has been finished successfully. Click on the Exit button.
1AA 00014 0004 (9007) A4
h)
ED
Check the date on the EM and DCR board via the date command. Both boards must have the same
date and time.
02
45/83

2.2.4
Start Application on both installed FLCs
In R4.3.1. the application is not started automatically anymore. Therefore you have to start the application
on both FLCs as follows:
Log in on emServ and start the application:
start
SSUDiag c startAppl
Log in on emCong and start the application:

start
SSUDiag c startAppl
Check that emServ comes up in active state and the emCong comes up in passive state:
SSUDiag c getEquipInfo
Following output will be displayed:

P05>[emServA83, SSUDiag(2943), SSU:Diag:DiagStartup, 219]
05/09/29 10:55:42
>SSUDiag: @(#)SEL Stuttgart SCM ID: SKY55xyz
command line parameters: c getEquipInfo<
P05>[emServA83, SSUDiag(2943), SSU:Diag:UsrAUEInfoHdl, 305]
05/09/29 10:55:42
>#################################################################
States of CS Equipment (FLC Service (left)):
===========================================
FLC: Active
1AA 00014 0004 (9007) A4
States of CS Equipment (FLC Congi (right)):

===========================================
FLC: Passive
ED
02
46/83
Check the Persistency Status

Check the synchronization state on both FLCs.

PersSync
Following output will be displayed:

>>>> Welcome to the Persistency Trace and Debug Tool <<<<
*********************************************************
Actual time: Thu Sep 29 11:07:36 2005
Sync states: S(yncronized),
N(ot sync)A(ctive side),
N(ot sync)P(assive side), O(utof)D(ate)
|
|
|Sync |TwinMap|
|Reorg|Reorg|Redo|MaxNo|
|
|Lockd
Idx | Proc | TACnt |state | TACnt |TAFin|Open |Fini |Size|Undos|WLock|RLock|from
0 | no valid line in OffsetFile with this index

7 |
VHM |
28648 | S |
0 | T | F | F |
0K | 18 | F | F |
8 | PmMgr |
13 | S |
13 | T | F | F |
0K | 18 | F | F |
9 |
SSU |
45920 | S |
38 | T | F | F |
0K | 18 | F | F |
10 |
MIB |
16154 | S |
0 | T | F | F |
0K | 18 | F | F |
11 |
MIB |
16154 | S |
0 | T | F | F |
0K | 18 | F | F |
12 |
MIB |
16154 | S |
0 | T | F | F |
0K | 18 | F | F |
14 |CSServer|
1 | S |
0 | T | F | F |
0K | 18 | F | F |
15 |CSServer|
1 | S |
0 | T | F | F |
0K | 18 | F | F |
16 |GMRE_PM |
2 | S |
0 | T | F | F |
0K | 18 | F | F |
17 |GMRE_MA |
97 | S |
0 | T | F | F |
0K | 18 | F | F |
NVRAM access successfully ended!
All persistency domains should have the state S for synchronized. The state of CSServer persistency
on the passive FLC can be ignored, also the state of GMRE_PM and GMRE_MA persistency, if ION is
not installed. With only one FLC in the system the status is per definition shown as S (synchronized).
Execute following commands to check the CSServer persistency on both FLCs:
log
tail 10 F_CSServer
Display on screen:
<data> <time> >Recovery saveConfigData: Save config data
successfully finished<
1AA 00014 0004 (9007) A4
Wait 1 minute if the message did not appear yet.
ED
02
47/83
2.2.5
Connect the Craft Terminal to the 1678 MCC

Connect the preinstalled and configured CT (LowerLayerManES required) with the 1678MCC according
to the customer network using the FInterface.
The installServer has to be rebooted, if the FInterface LAN configuration was changed!
If the CT is running on the installServer disconnect all used serial interfaces COM1 and COM2/5. Plug
out the FLC debug cable. Plug in the FInterface cable to the COM1 interface (refer to Figure 2). The
FInterface must always be connected to the active FLC.
The FLC redundancy is not supported for FInterface connections. After an FLC switch
the FInterface connection will be broken. In this case reconnect the FInterface cable
to the new active FLC.
Check the Alcatel Lower Layer Settings.
Menu
Start > Programs > Alcatel > Lower Layers > Lower Layers Settings
Choose:
Serial Port
COM1
Default
Start the CT by double click the Alcatel 1320CT icon or via menu START > Alcatel 1320CT.
A new NE appears in the map window on the CT.
Select the NE connected via FInterface.
1AA 00014 0004 (9007) A4
Select Start Supervision from the context menu (right mouse button) to start the supervision.
ED
02
48/83
1AA 00014 0004 (9007) A4

Figure 25. Start Supervision
> Start Supervision.
Finally the CT connects to the NE.
ED
02
49/83
Troubleshooting:

Sometimes it can happen that the connection to the NE is not established. In this case shutdown the
LowerLayerManES by pressing the Shutdown button (see Figure 26. ) and close an already open Map
using the menu Map > Exit. Start the CT again by double clicking the Alcatel 1320CT icon .
Figure 26. Shutdown of the LowerLayerManES
1AA 00014 0004 (9007) A4
If the problem still exists, kill the QIA process on the active FLC.
ED
02
50/83
Select the corresponding 1678MCC.

Select Show Equipment.
Figure 27. Show Equipment
2.2.6
Get Local Access
Look at the key symbol icon to find out, if the CT has local access to the NE. This icon is located in the
Management State Control Panel, which is presented at the right side in every View and looks like either
or
If the icon has a green frame as shown above, the CT already has local access to the NE. If not, you have
to request local access from the OS as follows:
Select Access State > Requested from the Supervision menu.
1AA 00014 0004 (9007) A4
In the confirmation dialog box that opens, click on OK and wait until the color of the icons frame changes to
green.
ED
02
51/83
2.2.7
Create Main Shelf

Be patient after pressing the Submit button. The Submit button will be grayed until the
equipment provisioning has been performed. Check for successful provisioning
response in the message window of the dialog box.
In case of negative provisioning response (i.e. the recent provisioning failed due to any
reason), retry according to the given error message in the dialog:
In case of provisioning parameter mismatches (i.e. wrong id values) close the

dialog for cleanup, reopen the dialog and redo the provisioning step with
corrected parameters.
In case of provisioning rejection do to multiple creation (example: try to create
second main shelf), close the dialog and check for the already existing equipment
in the USM.
Both FLCs should be the 66MHz version (default value). Asynchronous balanced mode
is allowed. In case of type mismatch alarm the configuration has to be changed using
the Equipment View of NM/CT corresponding to the hardware:
select FLC
Set > choose the FLC type > ok
If a wrong FLC type is equipped, DCC channels and LAPDs will be deactivated. A correct
FLC type resolves the problem.
In Equipment View of NM/CT select Configuration > Equipment Provisioning to open the
Equipment Provisioning dialog.
1AA 00014 0004 (9007) A4
To create the Main Shelf (Rack) select the 1678MCCsdhNE icon and choose the Edit > Create >
Rack menu option.
ED
02
52/83

Figure 28. Create Main Shelf (Rack)

Fill in the fields (see Figure 28. ), e.g.:
Rack Id = 1
Room = 1
Row = 1
Column = 1
Click on OK button to close the Create Rack dialog.
1AA 00014 0004 (9007) A4
Click on Submit button.
ED
02
53/83
To create the NGTRU Shelf select the Rack icon and choose the Edit > Create > Shelf menu
option.


Shelf Type = NGTRU
Top Subrack Id = 1
Subrack Position = 4
Click on OK button to close the Create Shelf dialog.
Click on Submit button.
1AA 00014 0004 (9007) A4
Figure 29. Create Main Shelf (NGTRU)
ED
02
54/83
To create the Main Shelf (MCC 1678) select the Rack icon and choose the Edit > Create > Shelf
menu option.


Shelf Type = MCC 1678
Shelf Id (hex) = 01
(only hexadecimal values between 01 and 3F are allowed)
Top Subrack Id = 2
Subrack Position = 19
Matrix Size = 160G, 320G or 640G (depending on the used matrix hardware)
Clock Rate = DS1 (1.5 Mb/s) or E1 (2Mb/s) (depending on the used FLC and matrix board)
1AA 00014 0004 (9007) A4
Figure 30. Create Main Shelf (MCC1678)
ED
02
55/83

According to the system configuration different Matrix Size must be configured. The following matrix sizes
are supported:
1K
160G
2K
320G
4K
640G (default)
Select the correct matrix size.
Dependent on the type of FLC and matrix board select the appropriate clock rate:
DS1 (1.5 Mb/s)
E1 (2Mb/s)
in case of MX320GA/MX640GA and FLCSERVA

in case of MX160/MX320/MX640 and FLCSERV
Press OK button.
Press Submit button.
Zoom in the new created mainShelf by double clicking on the Equipment View.
2.2.8
Reset the MATRIX (SLC) Boards
The SLC boards are not correctly configured after startAppl. Therefore the SLC boards must be reset
using the csReset command (first the passive SLC board). Execute the following commands on the
active FLC:
appl@emServA88(LogFiles)$ start
appl@emServA88(STARTUP)$ csReset MX640GEA icecold
appl@emServA88(STARTUP)$ csReset MX640GEB icecold
Sometimes the command is successful for the second time only.

Even for MX320 and MX160 cards use MX640GEA/MX640GEB in this command. Otherwise
the command will not be executed.
Supervise the Matrix board download on the active FLC:
appl@emServA88(STARTUP)$ log
appl@emServA88(LogFiles)$ tail f BoardMgt2ndGen.log
1AA 00014 0004 (9007) A4
The Matrix board download will take 10 to 20 minutes.
ED
02
56/83
2.2.9
Set the Host ID and the OSPF Interface for Local Ethernet

If LAPD is to be configured, the Host ID has to be set. When running a GMRE application the Host ID and
OSPF Interface for Local Ethernet have to be set.
2.2.9.1
Configure Host ID
Configure the Host ID via CT/NM.

Open the Equipment View
> Configuration
> Comm / Routing
In the Comm / Routing window click on
> Local IP/OSPF
1AA 00014 0004 (9007) A4
Figure 31. Configure the Host ID
ED
02
57/83
Set the Administrative State to

> Enabled

Set the Host ID / OSPF Router ID to

xx.xx.xxx.xx
Remark: For the correct value of the ID refer to the Network Configuration Guide.
To activate the settings and to close the window click on
> Ok
2.2.9.2
Enable OSPF Inteface for Local Ethernet
Enable the OSPF Interface for Local Ethernet via CT/NM.

Open the Equipment View
> Configuration
> Comm / Routing
In the Comm / Routing window click on
> Ethernet
1AA 00014 0004 (9007) A4
In the Ethernet window click on

> Create (if not done before and if button is not in grey color)
> Modify
ED
02
58/83

Figure 32. Enable OSPF Interface for Local Ethernet

Set the Administrative State to
> Enabled
1AA 00014 0004 (9007) A4
To activate the setting and to close the window click on

> Ok
ED
02
59/83

2.2.10
Update the FLC Configuration
The Update of the FLC configuration using the EP tool is described in the following section.
Select Configuration > Equipment Provisioning
Select Edit > CS Configuration
SKY5530A
SKY5530A
ION7505Y
ION7505Y
Figure 33. CS Equipment Configuration

The GMRE Node Address and installServer configuration described below is only necessary, if the related
fields are empty or wrong. In case of valid entries nothing has to be changed.
1AA 00014 0004 (9007) A4
In case of installation with ION (NE with GMRE), configure GMRE Node Address and Install Server IP
Address as follows:
GMRE Node Address: 10.10.255.<number of NE>
Install Server IP Address: <IPaddress_of_installServer>
ED
02
60/83

In case of installation without ION (NE without GMRE), configure GMRE Node Address and Install
Server IP Address as follows:
GMRE Node Address: 0.0.0.0
Install Server IP Address: <IPaddress_of_installServer>
Do not select the OK button. Select IP DCN for further configuration.
Figure 34. IP DCN Configuration
1AA 00014 0004 (9007) A4
Do not click on the OK button. Click on Other IP Hosts for further configuration.
ED
02
61/83

Figure 35. Other IP Hosts Configuration

Enter the corresponding NM, CT and additional WS. All host which should have access to the NE must
be entered using this dialog (IP address and hostname).
Backup and Restore is only possible if the NM/CT is configured under Other IP Hosts!
1AA 00014 0004 (9007) A4
Do not click on the OK button. Click on OSI DCN for further configuration.
ED
02
62/83

Figure 36. OSI DCN Configuration

Select QB3 even if you want to configure RFC1006!
1AA 00014 0004 (9007) A4
Enter the corresponding fields in the Managers area.
Click on the option button to select the manager, e.g. SHCT
Enter the NSAP address of the manager in the NSAP Address field:
RFC1006 stack: 540072872203+IP address of SH/CT
QB3 stack: OSI Area Address+System ID of 1353NM+1D
Enter the name of the transport selector in the TSEL text field:
PCCT: 1102
SH: 010x
Enter the name of the session selector in the SSEL text field: 00
Enter the name of the presentation selector in the PSEL text field: 1D
Click on the add button to add the configuration data to the list
Click the OK button to save the data
ED
02
63/83
Examples:

SH RFC1006 NSAP Address 540072872203149204148082

TSEL
0100
SSEL
00
PSEL
1D
SH OSI NSAP Address4700058000000000000001000A0030D30140F21D
TSEL
0101
SSEL
00
PSEL
1D
PCCT1 RFC1006 NSAP Address540072872203<IPAddress of CT PC, e.g. 010010088010>
TSEL
1102
SSEL
00
PSEL
1D
TSEL
1102
SSEL
00
PSEL
1D
TSEL
1102
SSEL
00
PSEL
1D
This update takes about 1.5 minutes.
After selecting the OK button in the EP tool, FLC switches may happen sometimes. The FInterface
connection is down in case of FLC switch, because the Finterface must always be connected to the
active FLC.
Exit the Equipment Provisioning Tool with File > Exit.
Configuration of GMRE: Refer to the Network Configuration Guide.
To create an NE Backup of the empty 1678MCC shelf configuration execute following sequence via CT:
1AA 00014 0004 (9007) A4
Select Download > Backup & Restore
ED
02
64/83
2.2.11
Configure the NTP Servers

Configure the NTP Servers (main and spare) using NM/CT:

Equipment View > Configuration >
Comm/Routing Dialogs > NTP Server...
Enter the correct IP address for the main NTP server. Optional a second NTP server (spare) can be
configured. Then press the ok button and wait until NRTCS alarm is cleared on both FLCs.
The configuration of the main NTP server is mandatory. Do not use FLC or ES64
addresses as NTP server address.
Enable the firewall on the installServer PC/Laptop.
1AA 00014 0004 (9007) A4
The installation is now completed!
ED
02
65/83
2.2.12

2.2.12.1
Event Log Management (optional)
Enabling
The Event Log Management (described in the ELB Rel 2.X Operators Handbook) is by default disabled
in the system software. To enable this feature you have to run a script on the active EM board.
Since the Event Log Management heavily affects the performance of Fast Restoration, it must not be
used together with GMRE/NP.
Do not enable this feature on NEs with GMRE/NP.
Perform the following steps to enable the Event Log Management:
~
Login as user appl to the active EM using following commands:

ssh appl@<IPaddress_activeEM>
bash
Run the script:

pbin
./modifyMIBCfg logRecordsPersistent=true
Set logRecordsPersistent entry in MIBApplic.cfg to true. The MIB process will be restarted.
~
Wait until the script is finished.
In case of CT:
Change to directory /ALCATEL/CTKv3.3.0/elb/conf and open file LogBrowsing.cfg :
cd /ALCATEL/CTKv3.3.0/elb/conf
vi LogBrowsing.cfg
Search for parameter:

Q3_PROTOCOL= DIRECT
Replace DIRECT with NESIM, safe and close the file LogBrowsing.cfg and restart the CT.
~
In all cases:
Open the Event Log Browser using NM/CT.
1AA 00014 0004 (9007) A4
Equipment View > Diagnosis > Log Browsing > eventLog
ED
02
66/83
2.2.12.2
Disabling
To disable this feature you have to run a script on the active EM board.
Perform the following steps to disable the Event Log Management:

~
Login as user appl to the active EM using following commands:

ssh appl@<IPaddress_activeEM>
bash
Run the script:

pbin
./modifyMIBCfg logRecordsPersistent=false
Set logRecordsPersistent entry in MIBApplic.cfg to false. The MIB process will be restarted.
1AA 00014 0004 (9007) A4
ED
Wait until the script is finished.
02
67/83
2.2.13

2.2.13.1
Checks after FLC Installation
NTP Time Synchronization
Check if the configured time server is already selected. To do this, use the following command and check
on emServ, emCong, dcrSer and dcrCong, whether the listed external time sources are synchronized
(reach = 377):
appl@emServA83(appl)$ ntpq p
Figure 37. NTP Time Synchronization Status on the emServ Board
appl@emCongA83(appl)$ ntpq p
1AA 00014 0004 (9007) A4
Figure 38. NTP Time Synchronization Status on the emCong Board
ED
02
68/83

appl@dcrServA83(appl)$ ntpq p
Figure 39. NTP Time Synchronization Status on the dcrServ Board
appl@dcrCongA83(appl)$ ntpq p
Figure 40. NTP Time Synchronization Status on the dcrCong Board

If no external time server is configured, open the NTP Server Configuration dialog using NM/CT.
Equipment View > Configuration >
Comm/Routing Diaglogs > NTP Server...
1AA 00014 0004 (9007) A4
Check, whether the NTP servers are reachable. If the value No is displayed:
Check whether the IP address is correct.
Check whether the NTP server is up and running.
ED
02
69/83
2.2.13.2
Fan Speed

The fan speed can be read on pShell / telnet session to the ACTIVE SLC with command:
pSH+> eq getPot 22 4 0
(upper fan #1)

(upper fan #2)
(upper fan #3)
(lower fan #1)
(lower fan #2)
(lower fan #3)
A value lower than 63 indicates no full speed.

In this case the fan speed must be adjusted with the following command:
pSH+> eq setPot 22 4 0 63
(upper fan #1)

(upper fan #2)
(upper fan #3)
(lower fan #1)
(lower fan #2)
(lower fan #3)
1AA 00014 0004 (9007) A4
This value is then stored in persistent memory of the fan, i.e. it survives a power down of the fan drawer,
shelf controller or complete shelf like the fan speed setting in factory.
ED
02
70/83

2.3
Short Description of the FLC Installation
This is the short description of the initial installation and start-up of the 1678MCC software. This
description has been written for well trained personal. For details see the description in Chapter 2.2.
This installation procedure describes the installation of both FLC at the same time. Therefore, a hub is
needed to connect the CT PC/Laptop to both FLCs.
The whole installation must be executed as user install.
2.3.1
Preparation of the Installation Procedure
2.3.1.1
a)
Preparation of the InstallServer
Delete the following links/directories on your installServer using a cygwin window:

cd /home/install
rm rf aiGuide
rm rf installServer
rm rf bin
b)
Delete already available SKY and ION builds on your installServer which are not required anymore
(to provide enough space on disk).
c)
Insert the CORE, SKY and ION CDROM successively into the CDROM drive. Begin with the CORE
CDROM.
d)
Adapt the network configuration of the installServer PC/Laptop to the network configuration of the
FLC.
e)
Configure the two serial interfaces (console connection) to the DCR and EM boards.
1AA 00014 0004 (9007) A4
2.3.1.2
Preparation of the FLC
a)
Connect both FLC LAN interfaces via a hub to the installServer PC/Laptop.
b)
Connect the console cable between the COM1 and COM2/COM5 of the installServer PC/Laptop with
the console interface on the FLC. Refer to Figure 1.
ED
02
71/83
2.3.2
FLC Installation

2.3.2.1
Configure Console Connection between InstallServer and the FLC
Open two console windows on the installServer PC/Laptop.

EM04A board <>
COM1
DCR board
COM2/COM5
2.3.2.2
<>
Check the UBoot Loader Software
a)
Change to the DCR console window on the PC/Laptop.
b)
Press the reset button on the FLC once.
c)
Stop the boot sequence of the DCR board.
d)
Check uboot version:

pSH+> raw
or
=> ver
The uboot version must be UBODCR01C or higher.

e)
Reconnect the console to the DCR board.
f)
Reset the DCR board:

pSH+> reset
2.3.2.3
a)
or
=> reset
Start the FLC Installation
Start the aiGuideWizzard tool as user install using a cygwin window:

cd /home/install/SKY55<xyz>
1AA 00014 0004 (9007) A4
./aiGuideWizzard
b)
Enter the required FLC configuration data in the aiGuideWizzard. Do not press the Start
installation button.
c)
Reboot the FLC by pressing the reset button for about 3 seconds. Interrupt the booting sequence
by pressing the ESC button in the EM console just after the message Init ECC memory...
appears.
ED
02
72/83
d)
On both FLCs enter the following commands in the MENMON mode:

MenMon> eedef
MenMon> rst
e)
Press Start Installation button in the aiGuideWizzard just after the following message appears:
Searching for server (BOOTP) ... .
This operation will start the FLC installation.
2.3.3
Final configuration steps
a)
Start application on both installed FLCs.
b)
Check the Persistency State and the CSServer Persistency.
c)
Connect the Craft Terminal to the 1678MCC via Finterface.
d)
Create Rack, NGTRU and Main Shelf.
e)
Reset both MX (SLC) Boards.
f)
Update the FLC Configuration via EP dialog.
g)
Create NE Backup of empty 1678MCC Shelf Configuration.
h)
Configure the NTP Servers.
i)
Enable the firewall on the installServer PC/Laptop.

The installation is now finished.
2.3.4
a)
Event Log Management (optional)
Enable Event Log Management.
2.3.5
Checks after FLC Installation
a)
NTP Time Synchronization.
b)
Fan Speed.
1AA 00014 0004 (9007) A4
ED
02
73/83
1AA 00014 0004 (9007) A4
ED
02
74/83


TROUBLESHOOTING
3.1
Version of the FPGA Goblin
If the system does not come up after FLC installation, check wether the I/O boards and LAX boards have
the correct versions of FPGA Goblin. The correct version are:
3.5 for I/O boards
2.2 for LAX boards
The folowing example shows how to check the version of FPGA Goblin. The version is contained in the
FPGA register 0 and 1. In the example below the FPGA register 0 contains 3, while the FPGA register
1 contains 5, which means the version of the Goblin is 3.5.
Open a telnet session to the active SLC and enter the commands written in bold:
Telnet+> hw_cfg
HWCFGDRV devicedriver
[0] Display all the HWCFG debugcounter variables.

[1] Display slot HWCFG debugcounter variables.
[2] Read FPGA register.
[3] Test Cmd (You could erase all the data saved on Flash Memory).
[4] Test Driver (You could erase all the data saved on Flash Memory).
[5] Enable/Disable message tracement.
[6] Display error codes.
Select : 2
Insert slot board: 3
0 version
1 hidden_version
2 flash_op
3 fpga_download
Insert register address : 0
FPGA register 0 = 0x3 > First Byte of Goblin version: 3
Telnet+> hw_cfg
1AA 00014 0004 (9007) A4
HWCFGDRV devicedriver
[0] Display all the HWCFG debugcounter variables.

[1] Display slot HWCFG debugcounter variables.
[2] Read FPGA register.
[3] Test Cmd (You could erase all the data saved on Flash Memory).
[4] Test Driver (You could erase all the data saved on Flash Memory).
ED
02
75/83
[5] Enable/Disable message tracement.

[6] Display error codes.

Select : 2
Insert slot board: 3
0 version
1 hidden_version
2 flash_op
3 fpga_download
Insert register address : 1
1AA 00014 0004 (9007) A4
FPGA register 1 = 0x5 > Second Byte of Goblin version: 5 > Version: 3.5
ED
02
76/83

PROCEDURE FOR POST INSTALLATION OF ION75
4.1
General Information
This chapter describes the actions and steps necessary for the post installation of ION75 executed via
NM on a running system with SKY55<label>.
Since the Event Log Management heavily affects the performance of Fast Restoration, it
must not be used together with GMRE/NP. Disable this feature before installing GMRE
(see chapter 2.2.12.2 on page 67).
4.2
Remarks
The active FLC can used as installServer in the installSWRelease call if the software is present in
the directory /packages/aiGuide/tmp.install/ION75 <label>.
Be aware that the installation software allways automatically downloads the software packages from
the partner FLC if they are in the directory /packages/aiGuide/tmp.install/ION75 <label>, even
if an NM is specified as installServer. This is an internal performance improvement for the installation
of the seconds FLC.
Concerning software download from an NM: If an NM is installed correctly as described in its

installation manual, sftp should work. But it works only if user install on the NM has started the sshd
daemon with:
./SKY55<label>/installserver status
./SKY55<label>/installserver stop sshd
# check if an sshd
# daemon is running
# to stop an old one
./SKY55<label>/installserver start sshd
4.3
1AA 00014 0004 (9007) A4
ED
Restrictions
Since the Event Log Management heavily affects the performance of Fast Restoration, it must not
be used together with GMRE/NP. If not done yet disable this feature before installing GMRE (see
chapter 2.2.12.2 on page 67).
02
77/83
4.4
Requirements

A successful upgrade of the NE requires following:
An OMSG Alcatel 1678MCC installed with redundant FLC boards and NM.
A properly running previous software version.
CDROM drive on the NM.
CDROMs containing GMRE Application (ION75 ).
Current Handbook.
TurnOn & Commssioning Handbook.
For typing the following Unix commands xterm terminals are used.
Only well trained 1678MCC Service personal should do the ISU.
4.5
Preconditions
The FLC passwords of user appl and install must be available.
The IP address of the installServer must be available.
The GMRE Node address must be available.
The persistency of both FLC (EM) boards must be synchronized.
FLCCongi must be the active one, FLCService board must be passive. Also the SSU process must
be reachable on both FLCs. Test this as user appl on both EM boards with:
SSUDiag c getEquipInfo
The output must be:
States of CS Equipment (FLC Service (left)):

===========================================
FLC: Passive
1AA 00014 0004 (9007) A4
States of CS Equipment (FLC Congi (right)):

===========================================
FLC: Active
ED
02
78/83
4.6
Start the Installation

(1) Stop application on passive emServ.

~
Stop application on passive emServ as user appl:
SSUDiag c shutAppl
(2) Install GMRE packages on stopped emServ.

~
Install GMRE packages only on stopped emServ as user install:
tools
./installSWRelease installServer=<IPaddress_NM>
\
gmreServiceSWRelease=ION75<label> force
\
host=localhost gmreNodeAddress=<GMRE_Node_Address>
(3) Start application on stopped emServ.

~
Start application on stopped emServ as user appl using command:
SSUDiag c startAppl
(4) Check the persistency synchronization.

~
Wait until the persistency is synchronized and check it on the active emCongi as user appl:
1AA 00014 0004 (9007) A4
isPersSync
ED
02
79/83
(5) Stop the application on both FLC.

Stop the application first on passive emServ:
SSUDiag c shutAppl
Then stop application on active emCong:

SSUDiag c shutAppl
(6) Set the persistency synchronization state of GMRE on stopped emServ.

~
Set the persistenc synchronization state of GMRE domains to S on stopped emServ:
PersSync active
Wait for synchronization and check it on the stopped emServ:

PersSync
(7) Start the application on the stopped emServ.

~
Start the application on the stopped emServ:
SSUDiag c startAppl
(8) Install GMRE packages on stopped emCong.

~
Install GMRE packages only on stopped emCong as user install:
1AA 00014 0004 (9007) A4
tools
./installSWRelease installServer=<IPaddress_NM>
\
gmreCongiSWRelease=ION75<label> force
\
host=localhost gmreNodeAddress=<GMRE_Node_Address>
ED
02
80/83
(9) Remove persistency contents on stopped emCong.

Remove persitency contents on still stopped emCongi:
SSUDiag c stopSSU
PersCreate passive
(10) Start the application on stopped emCong.

~
Start the application on stopped emCong:
SSUDiag c startSSU
SSUDiag c startAppl
(11) Check the persistency synchronization.

~
Wait until the persistency is synchronized and check it on the both FLC (EM board):
PersSync
(12) Perform an FLC switch.

~
Switch the FLCs:
SSUDiag c switch
1AA 00014 0004 (9007) A4
ED
02
81/83
1AA 00014 0004 (9007) A4
ED
02
82/83

1AA 00014 0004 (9007) A4
ENDOFDOCUMENT
ED
02
83/83


FLCInst 78 43 24169 BE PC 02

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

FLCInst 78 43 24169 BE PC 02

Încărcat de

Drepturi de autor:

Formate disponibile

INSTALLATION & STARTUP HANDBOOK

3AG 24169 BEAA Ed. 02

3AG 24169 BEAA Ed. 02

All rights reserved. Passing on and copying of this

1678MCC R4.3 INSTALLATION & STARTUP

1AA 00014 0004 (9007) A4

1AA 00014 0004 (9007) A4

3AG 24169 BEAA PCZZA

All rights reserved. Passing on and copying of this

All rights reserved. Passing on and copying of this

HANDBOOK STRUCTURE AND CONFIGURATION CHECK . . . . . . . . . . . . . . . . . . . . . . . .

INITIAL INSTALLATION OF THE FLC SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

PROCEDURE FOR POST INSTALLATION OF ION75 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

1AA 00014 0004 (9007) A4

1AA 00014 0004 (9007) A4

All rights reserved. Passing on and copying of this

Figure 1. How to use the FLC debug cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1AA 00014 0004 (9007) A4

3AG 24169 BEAA PCZZA

All rights reserved. Passing on and copying of this

1AA 00014 0004 (9007) A4

3AG 24169 BEAA PCZZA

All rights reserved. Passing on and copying of this

All rights reserved. Passing on and copying of this

HANDBOOK STRUCTURE AND CONFIGURATION CHECK

Customer Documentation Alcatel 1678 Metro Core Connect

Refer to the Technical Handbook to obtain the following information:

1AA 00014 0004 (9007) A4

Good knowledge of UNIX (especially system configuration, process management, permissions,

Detailed knowledge of the 1678MCC hardware configuration

Use of the 1678MCC via control software of the CT

Experience in installing software

Handbook Change History

1AA 00014 0004 (9007) A4

DDTS SLSks50241: EVL: Dialogue hanging after receive data (SLSks50348).

All rights reserved. Passing on and copying of this

Adaptions for FLC Installation procedure in R4.3:

Added descriptions for GMRE (i.e. ION<xx><yyy> SW build).

Rework of inital FLC installation.

Chapter Procedure for Post Installation of ION75 (modified).

DDTS SLSks44683: FLCs after Coldstart (Power down/up) in state Maintenance.

DDTS SLSks45344: 1678MCC Event LOG Management.

DDTS SLSks46834: FLC Installation / Firewall indication missing.

DDTS SLSks45460: NTP configuration does not reject FLC addresses.

DDTS SLSks48512: Downgrade FLC: check criteria for nr of lapds wrong.

Compliance with European Norms

Refer to the Technical Handbook to obtain the following information:

Electromagnetic Compatibility (EMC)

Safety Norms and Labels

1AA 00014 0004 (9007) A4

General Safety Rules

Several Dangerous Conditions

Other Norms and Labels

All rights reserved. Passing on and copying of this

Refer to the Technical Handbook to obtain the following information:

1AA 00014 0004 (9007) A4

Electromagnetic Compatibility (EMC)

General Norms Installation

General Norms Turnup & Commissioning, Operation

General Norms Maintenance

Electrostatic Dischargers (ESD)

Suggestions, Notes and Cautions

Labels affixed to the Equipment