ENTPCTE103EN Beta2 Letter

Alcatel-Lucent OmniPCX Enterprise
CPU Loading
PARTICIPANT’S GUIDE
REF. ENTPCTE103EN Issue 01
This document has no contractual value and may be changed or withdrawn
at any time by Alcatel-Lucent.
This product includes software. Its use may be subject to legislation concerning computer technology,
databases and civil liberties (in case of France see the law N° 7817 dated 6 january1978).
Alcatel-Lucent OmniPCX Enterprise ± Release 10
Post-Sales Training Offer
Enterprise Education and Partner Programs

May 16th, 2011
Summary
Caption
Post-Sales Newcomer
Global view
ACFE Level
ACSE Business level
ACSE Corporate level
Value Added Options
Post-Sales Experienced
2 | ALCATEL-LUCENT OMNIPCX ENTERPRISE ± POST-SALES TRAINING OFFER | MAY 2011

Alcatel-Lucent OmniPCX Enterprise - Release 10
Caption
VALUE ADDED OPTIONS
To complement the basic portfolio by value added solutions or applications:

Configuration & administration of complementary features, associated solutions & applications
SOLUTION BASED
To answer to customer standard customization:

Configuration & administration of services & advanced features
STARTER PACK
For a quick start of the solution:

Install the solution, the infrastructure and ensure the start up of the system
DIRECTION OF READING
FUNDAMENTALS
Caption (Continued)
Associated
Profile Training course Description (including audience)
Certification
I=x h
Course Name
C=x d Optional training course
Reference
V=x d
² ²
I=x h
Course Name Training course for expert engineers in charge of complex
C=x d
Reference
V=x d configurations, installation & remote service support
POST-SALES
I=x h
Course Name Training course for field engineers in charge of advanced
C=x d
Reference
V=x d configurations, installation and service support
I=x h
Course Name Training course for presales engineers who design large/complex
C=x d
Reference
V=x d networking projects
PRESALES
I=x h
Course Name Training course for presales engineers who design standalone
C=x d
Reference
V=x d projects
I=x h
Course Name Training course for sales representatives who sell Alcatel-Lucent
SALES C=x d
Reference
V=x d products and solutions
I=x h
Course Name
C=x d Fundamentals training course
Reference
V=x d
² ²
I=x h
Course Name Training course for administrators who are responsible for system,
ADMINISTRATORS C=x d
Reference
V=x d network, operation, maintenance and IP Telephony administration ²
I=x h Training course for end-users who require information on
Course Name
END USERS C=x d Telephony, IP Touch Phone facilities, My Instant Communicator
Reference
V=x d
²
and OmniTouch Contact Center
I = xh Individual learning, in hours C= xd Classroom learning, in days V= xd Virtual learning, in days

Post-Sales Newcomer (Global view)
VALUE ADDED OPTIONS
Associated Options ± details page 9
SOLUTION BASED
ACSE Corporate level ± details page 8
SOLUTION BASED
ACSE Business level ± details page 7
STARTER PACK
ACFE level ± details page6

DIRECTION OF READING
FUNDAMENTALS
Post-Sales Newcomer (ACFE level)
STARTER PACK
Duration: I=8 h - C=10 d
ACFE OmniPCX
Enterprise R10
ENTPTC1W1
30 MCQ: 45 min
Starter Pack I=8h

Enterprise C = 10 d
ENTPCTE100
Technology Overview Technology Overview Technology Overview

Series: IP Overview I=1h Series: LAN I= 30min Series: WAN I= 15min
TGK30001W TBU30052W 3EY0SA065
FUNDAMENTALS
Post-Sales Newcomer (ACSE Business level)
BUSINESS SOLUTION BASED
ACSE OmniPCX
Tap Lab OmniPCX C=2d Enterprise
Enterprise or Business R10
ENTPTA0A9 or ENTPTC2C1
C=3d
ENTPTA0A10 60 MCQ: 1 h / lab: 2.5 h
I=6h
VoIP Advanced
ENTPCTE104 C=7d
CPU loading C=2d

ENTPCTE103
Starter Pack I=8h VoIP Technologies I=8h

Enterprise C = 10 d FG00WB065
ENTPCTE100
FUNDAMENTALS
Post-Sales Newcomer (ACSE Corporate level)
CORPORATE SOLUTION BASED
ACSE OmniPCX
Tap Lab OmniPCX C=2d Enterprise
Enterprise or Corporate R10
ENTPTA0A9 or ENTPTC2C4
C=3d
ENTPTA0A10 60 MCQ: 1 h / lab: 2.5 h
On Site Mobility I=6h

C=2d Multi Site Network
DECT C=5d
ENTPCTE102
ENTPCTE110
ACSE OmniPCX
Enterprise Business R10
FUNDAMENTALS
Post-Sales Newcomer (Value Added Options: global view)
VALUE ADDED OPTIONS
OmniMessage 4635 C=8d

Voir détails page 10
OmniMobility DECT C=2d Free Desktop

Voir détails page 12 Mobility C=2d
ENTPCTE111
Hotel /healthcare C=3d
OmniTouch 8440
C=3d IP Touch Security I = 12 h
Messaging Services
Solution C=3d
ENTPCTE105
Off Site Mobility I = 12 h
ENTPWB907
ACSE OmniPCX
Starter Pack Enterprise Business R10
I=8h
Enterprise C = 10 d
ENTPCTE100
FUNDAMENTALS
Post-Sales Newcomer (Value Added Options: OmniMessage 4635)
VALUE ADDED OPTIONS
ACSE
OmniMessage
4635 R5.x
4635TC0C1
40 MCQ: 45 Min / lab: 2.5 h
OmniMessage 4635
Expert C=5d
4635TE312
OmniMessage 4635
Advanced C=3d
4635TE310
Starter Pack I=8h

Enterprise C = 10 d
ENTPCTE100
FUNDAMENTALS
Post-Sales Newcomer (Value Added Options: Hotel/Healthcare)
VALUE ADDED OPTIONS
ACFE
Hotel / Healthcare
ENTPTC2C3
30 MCQ: 45 min
Hotel / Healthcare C=3d

ENTPTE909
Starter Pack I=8h

Enterprise C = 10 d
ENTPCTE100
FUNDAMENTALS
Post-Sales Newcomer (Value Added Options: OmniMobility DECT)
VALUE ADDED OPTIONS
ACSE
OmniMobility
DECT
AP00TC0C0
40 MCQ: 45 Min / lab: 2.5 h
OmniMobility Expert C=2d

AP00TE085
Starter Pack I=8h On Site Mobility

Enterprise DECT C=2d
C = 10 d
ENTPCTE100 ENTPCTE110
FUNDAMENTALS
Post-Sales Newcomer (Value Added Options: 8440 Messaging Services)
VALUE ADDED OPTIONS
Advanced
C=2d
8440TE601
STARTER PACK
ACFE OmniTouch
Starter 8440 MS R6
C=3d
8440TE600 8440TC1C1
30 MCQ: 45 min
Starter Pack I=8h

Enterprise C = 10 d
ENTPCTE100
FUNDAMENTALS
Post-Sales Experienced already Business R9 Certified
VALUE ADDED OPTIONS
SOLUTION BASED
ACSE OmniPCX
Enterprise
Corporate R10
ENTPTC2C4
60 MCQ: 1 h / lab: 2.5 h
I=6h On Site Mobility

Multi Site Network C=2d
C=5d DECT
ENTPCTE102
ENTPCTE110 Tap Lab OmniPCX C=2d
Enterprise or
ENTPTA0A9 or
C=3d
ACSE OmniPCX ENTPTA0A10
Enterprise
R9.1 to R10 upgrade I=3h Business R10
ENTPWTE120 ENTPTC2U1
20 MCQ: 45 Min
Security Access I=4h

ENTPTE912 C=1d
ACSE OmniPCX
Enterprise Business R9
FUNDAMENTALS
Post-Sales Experienced not yet Business Certified
VALUE ADDED OPTIONS
SOLUTION BASED
ACSE OmniPCX
Enterprise
Corporate R10
ENTPTC2C4
60 MCQ: 1 h / lab: 2.5 h
I=6h On Site Mobility

Multi Site Network C=2d
C=5d DECT
ENTPCTE102
ENTPCTE110 Tap Lab OmniPCX C=2d
Enterprise or
ENTPTA0A9 or
C=3d
ACSE OmniPCX ENTPTA0A10
Enterprise
R9.1 to R10 upgrade I=3h Business R10
ENTPWTE120 ENTPTC2C1
60 MCQ: 1 h / lab: 2.5 h
Security Access I=4h

ENTPTE912 C=1d
OmniPCX Enterprise
Business R9
FUNDAMENTALS
Post-Sales Experienced already R9 Corporate Certified
VALUE ADDED OPTIONS
Tap Lab OmniPCX C=2d

Enterprise or
ENTPTA0A9 or
C=3d
ENTPTA0A10
SOLUTION BASED
ACSE OmniPCX
Enterprise
R9.1 to R10 upgrade I=3h Corporate R10
ENTPWTE120 ENTPTC2U4
20 MCQ: 45 Min
ACSE OmniPCX
Enterprise Corporate R9
FUNDAMENTALS
Post-Sales Experienced not yet Corporate Certified
VALUE ADDED OPTIONS
Tap Lab OmniPCX C=2d

Enterprise or
ENTPTA0A9 or
C=3d
ENTPTA0A10
SOLUTION BASED
ACSE OmniPCX
Enterprise
R9.1 to R10 upgrade I=3h Corporate R10
ENTPWTE120 ENTPTC2C4
60 MCQ: 1 h / lab: 2.5 h
OmniPCX Enterprise
Corporate R9
FUNDAMENTALS
www.alcatel-lucent.com/enterprise
Enterprise Education and Partner Programs
Phone: +33 (0)2 98 28 53 19

Fax: +33 (0)2 98 28 50 03
Email: enterprise-educational-services@alcatel-lucent.com
Website: https://businessportal.alcatel-lucent.com
twitter.com/ALUEnterprise
facebook.com/ALUEnterprise
youtube.com/user/AlcatelLucentCorp

CPU Loading Business
REFERENCE ENTPCTE103EN DELIVERY LANGUAGE English (course material English)
DURATION METHODS
Virtual self-paced training on the computer*
2 days Traditional classroom or practical sessions with tutorials (TAP LAB)
Tutored virtual training sessions accessible via an internet connection*
MAXIMUM NUMBER OF PARTICIPANTS 12
PUBLIC
Engineers
OBJECTIVES
At the end of the course, the participant will be able to:
Load software on call server Activate duplicated call server system
Update software
PREREQUISITES
To have attended Alcatel-Lucent OmniPCX Enterprise Starter Pack Enterprise training course - ENTPCTE100
PROGRAM DESCRIPTION
COPYRIGHT © 2011 ALCATEL-LUCENT ENTERPRISE. ALL RIGHTS RESERVED
Ƚ Software loading principle Ƚ Call server duplication
Ƚ Mono version loading Ƚ Call server spatial redundancy
Ƚ Multi version loading Ƚ Disk structure
Ƚ Software updates Ƚ Main Linux commands
* Required technical configuration for i-learning and v-learning

Access to the Business Partner Web Site (for Customer only): https://businessportal.alcatel-lucent.com/ Internet Explorer 6 (or +) or
Mozilla Firefox 3 (or+) and Adobe Flash Player 9(or +) or Acrobat Reader 9 (or +).
CPU Loading
TOC.doc
DOCUMENT CHANGES
Issue Date Issue Date
Alcatel-Lucent OmniPCX Enterprise CPU Loading 01 07/11
File reference: ENTPCTE103EN
GENERAL SUMMARY
CORE CURRICULUM AND CATALOG PROGRAM DESCRIPTION
1. Software loading - Mono version

ENTP0842P01TEUS .............................................................................................5
ENTP0842C01TEUS ........................................................................................... 43
ENTP0842C02TEUS ........................................................................................... 49
ENTP0842H01TEUS ........................................................................................... 53
2. Software loading - Multi versions

ENTP0842P03TEUS ........................................................................................... 57
ENTP0842C03TEUS ........................................................................................... 67
ENTP0842C04TEUS ........................................................................................... 75
ENTP0842H03TEUS ........................................................................................... 85
3. Patch loading
ENTP0842P05TEUS ........................................................................................... 89
ENTP0842C05TEUS ........................................................................................... 99
ENTP0842H05TEUS ..........................................................................................105
4. Loading of GDx & INTIP3 boards

ENTP0842P06TEUS ..........................................................................................109
tc0521_EN ....................................................................................................111
ENTP0842H06TEUS ..........................................................................................121
REF. ENTPCTE103EN Issue 01 All Rights Reserved © 2011, Alcatel-Lucent i

1
CPU Loading
TOC.doc
5. Duplication
ENTP0438P01TEUS.......................................................................................... 125
ENTP0438C02TEUS.......................................................................................... 139
ENTP0438C04TEUS.......................................................................................... 143
ENTP0438C05TEUS.......................................................................................... 147
ENTP0438C06TEUS.......................................................................................... 155
ENTP0438H01TEUS.......................................................................................... 163
6. Spatial redundancy
ENTP0492P01TEUS.......................................................................................... 167
ENTP0492C01TEUS.......................................................................................... 175
ENTP0492M01TEUS ......................................................................................... 193
ENTP0492H01TEUS.......................................................................................... 205
ENTP0492H10TEUS.......................................................................................... 207
ii All Rights Reserved © 2011, Alcatel-Lucent REF. ENTPCTE103EN Issue 01

2
CPU Loading
TOC.doc
FEEDBACK SHEET
In order to improve the quality of the documentation, please report any errors found by
returning this sheet to the address below.
CHAPTER PAGE DESCRIPTION
Please return this sheet to:

Alcatel-Lucent Enterprise
115-225 rue Antoine de Saint-Exupéry
ZAC Prat Pip – Guipavas
29806 BREST CEDEX 9 – France
FAX: (33) 2 98 28 50 03
Email: training_quality.contact@alcatel-lucent.com
Website: www.businesspartner.alcatel-lucent.com
REF. ENTPCTE103EN Issue 01 All Rights Reserved © 2011, Alcatel-Lucent iii

3
CPU Loading
TOC.doc
iv All Rights Reserved © 2011, Alcatel-Lucent REF. ENTPCTE103EN Issue 01

4
CS software loading – Mono version mode
All Rights Reserved © 2007, Alcatel-Lucent 1
OBJECTIVES
To describe the OmniPCX Enterprise loading tool PC Installer
To describe the software loading principles
To describe the different loading cases
To describe the procedure depending on the type of CPU
To describe a complete software loading procedure
Alcatel-Lucent OmniPCX Enterprise – CS software loading – Mono version mode

Ref. ENTP0842P01TEUS Issue 03
5
PC Installer - Loading tool
The OmniPCX Enterprise PC Installer ensures:
The loading of all software type
Linux operating system

Telephone software
Correcting patch (for Linux and/or telephone)
Specific soft for GA / GD
The loading of all CPU type
CS/CS2
CPU7
Appliance Server
Blade Server

6
The application is installed on Windows OS
Based on PERL scripts, this application uses it’s own servers started according
to the choices done in the menu
Bootp
Only in case of full installation
Tftp/ftp
For file transfer
PC installer software is delivered in each OmniPCX Enterprise release
The setup of the OmniPCX Enterprise PC Installer is located in the directory /Dhs3mgr/ “Name of the release”
/pcmao/boot_res/pcinstall

7
Tool software architecture
BOOTP TFTP FTP Call

Server
Windows
Operating System
Customer LAN
Or direct cable
The FTP login is done with anonymous login

8
Generalities
The software loading is done over IP
Depending on the type of loading, IP connection can be direct to the PC or

via the company’s LAN
A V24 link allows to start and check the installation
Call
Server
V24 link
Ethernet link
The complete loading (Linux + telephonic version (call handling)+ patch) is mainly done with a direct Ethernet link between CS
and PC server because a bootp server is started.

9
Generalities
Main element of software release:
A release is made up of the following elements :
A Linux OS release
A release of « facilities » (swinst)
A release of the telephone binaries
A static patch (optional)
A dynamic patch (optional)
Naming of a software release

J14103b
b: Dynamic patch
J: Product line (eg: J=R10)
identification
1: Option in the line 410:Software version 3: Static patch #

10
Generalities (suite)
The telephonic application is located in :

/DHS3mgr/” Name of the release ”/
The static patch is located in :

/DHS3mgr/” Name of the Patch ”/
The dynamic patch is located in :

/DHS3mgr/” Name of the Dynamic patch ”/
The Linux system is located in :

/DHS3mgr/” Name of the release”/pcmao/bootp/linux/” version id ”
The swinst environment is located in :

/DHS3mgr/” Name of the release”/pkglinux/facil

11
Generalities (suite)
The release « J14103b» is provided within 3 directories placed in “DHS3mgr” :

The directory J1410 contain the version 410 of the R10
The directory J14103 contain the patch 3 of the version 410
The directory J14103b contain the dynamic patch b to install on the patch 3
of the version 410
A patch (static or dynamic) includes all of the previous patch corrections

The patch J14103 include the patch 1 to 3 corrections
The patch J14103b include the patch a to b corrections

12
Generalities
Different types of loading
Call Handling or Patch

Complete version or
patch installation
Linux on inactive partition

Linux Installation in the
second disk part
Linux + Call Handling

Automatic complete loading
GD/GA Binary
To reload GD or GA binaries

13
Generalities
Different types of Call Server
Alize (CPU-CS)
Bootp request at starting up
A4400 (CPU 5/6/7)

Appliance Server
PXE request at starting up
Blade Server
PXE request at starting up
KVM consol mandatory (No V24 available)
CS2 (CPU-CS2)
BOOTP: Bootstrap Protocol (allows to start a system without any basic configuration)
PXE: Pre-Boot eXecution Environment (Developed by Intel, now a standard)
KVM: Keyboard Video Mouse

14
Generalities
Call server automatic loading:
2 cases:
The CS hard disk is empty
Automatic start up in «Standard Installation » mode for CPU-CS, Appliance Server and Blade
Server
Manual start up on CPU 7

Access to the Bios menu
The CPU disk is already loaded
Manual starting up on all CPUs

Access via the Bios menu or hard disk invalidation to force automatic start up

15
Generalities
CPU’s starting up phases
Bios starting up Possible interruption
System auto-test
Bootloader starting up Possible invalidation
GRUB loader starting up
Linux starting up Possible invalidation
Linux starting up on hard disk active partition .
Telephonic application starting up
Automatic starting up if autostart is set in swinst
Manual starting up under mtcl with command RUNTEL
GRUB: (GRand Unified Bootloader) is the boot loader used by the OXE.
It allows the system to start on hard drive (on a specific partition if necessary) or from the network.

16
Loading tool interface
Main interface
Installation type:
Allow to select the application working mode
Call handling or Patch
installation of a telephone binaries or patch on CS (Linux + telephone)
Linux on inactive partition
Linux installation on the second hard disk partition .This Linux part can be used in case of software upgrading.
Linux + Call handling
Linux software and telephone application complete installation
GD/GA/rGD binaries
GD or GA software downloading .

17
Loading configuration
Choice of DHCP server mode

Depending on CPU type
List of versions
in /DHS3mgr
List of countries
Auto/manual installation
or disk maintenance
If company network, you

Must write the MAC Address
in the field at the bottom
List of Ethernet boards found in your system
Installation type:
Standard: for an automatic loading
Linux into memory: loading Linux into memory for further maintenance operations

18
Information windows during loading
MAC address of client BOOTP/DHCP
IP address given by DHCP server FTP client IP address
Hostname given by DHCP
Directory used for loading Directory used for loading
File name being transferred File name asked to the the server
Update of a version or patch
Downloading progress window

The color shows the server used
In case of a complete release loading, the progressing window at the bottom shows the files percentage (or replies percentage)
sent to the call server depending on the used server (DHCP, TFTP, FTP and FTP data).
In case of patch loading, the progression is visible under swinst.

19
Complete release loading - Principles
Principles of automatic software loading
BOOTP request or DHCP (PXE)
config IP and boot file name delivery
Files list downloading
Files transfer (including Linux RAM)
DHCP request
Call IP setting up delivery
Server
Automated installation of linux via FTP
Files transfer (Linux, tools and swinst)
Version and patches downloading
Requested files delivery
End of installation , call server reboot
Ethernet link

20
Depending on the call server type, the initial request can be :

BOOTP (CPU-CS/CS2 and CPU Crystal)
DHCP (AS et BS)
The server delivers the necessary IP configuration to continue and a file

containing a list of files to be downloaded with TFTP
CPU-CS: startup.txt
Appliance Server: pxeloader
CPU Crystal: none (the file name containing the Linux RAM is known from the
CPU)
The call server downloads with TFTP the whole files :

enumerated in the boot file
already known in case of crystal CPU

21
Once Linux RAM is downloaded , this one is copied into memory and the system
really starts up under Linux in an automatic procedure
Complete IP configuration request to the PC server via DHCP
Hard drive formatting and system files creation
Complete kernel and essential packages downloading
Swinst downloading and starting up
As no telephonic application is present, swinst immediately starts the automatic
installation procedure
Downloading of release and patches files pointed in PC Installer or during the boot of crystal
CPU
Creation of a default IP configuration for the CPU
Reboot of the system
Installation is finished

22
Loading tool configuration
Select CPU type
Select the complete version to be installed

(Version + Static patch + Dynamic patch)
Select the country
Select Standard
Select connection type
Change the network board (if necessary)
Modify the IP address given to the CS (if necessary)
Enter CPU MAC address (Company network mode)
Validate to start the servers
The name of the directory must not contain special character (For instance J1.410.3b must be renamed into J14103b).

23
Complete release loading – CPU-CS
Different cases of starting up
Hard drive is empty
The loading begins automatically
Release already installed, the hard drive can be disabled
If Linux is started, log with root account and type:

grubboot ETHER then reboot the call server
Otherwise, interrupt the system in GRUB with c and type:

Press enter to boot the default OS [0], 'c' for a command-line,
or give an another entry number
grubboot ETHER then reboot
At the reboot, the system recovers the case of an empty disk
ON
The command grubboot ETHER forbids the system to start from the disk by disabling the disk for the GRUB.
OFF
While rebooting , as the disk is considered unavailable , the system starts automatically a loading procedure from the IP network.
1234
The disk data are useless after having typed grubboot ETHER command.
(In case of error,please refers to technical communication TC0536 customer’s data recover on faulty or disabled disk)

24
Complete release loading - CPU-CS
Different cases of starting up (cont’)
Force boot on network in the bios

#Alize BIOS Monitor
*** BIOS Version 3EH30227DRAA bios100/008.017 ***
*** Generated on Jun/13/2003 at 09:25 ***
....................... Hardware autotest .......................
value of DIL switch 01
YOU CAN strike Ctrl B to enter in BIOS monitor during several seconds from NOW
!
Ctrl B
hit [Ctrl I] for BIOS monitor! Ctrl I
Password?:
The delay at YOU CAN strike Ctrl B to enter in BIOS monitor is very short.

25
Different cases of starting up (cont’)
Force boot on network in the bios

Alize BIOS Monitor
Monitor Light Menu

01 - Load From Hdisk #0
02 - Load From Ethernet Starting up on network (BOOTP)
03 - Load From Flash NAND program
04 - Load From Flash NAND program and Bootp
05 - Load From Hdisk #0 and Bootp
06 - Display MAC address
07 - Display PCMS id
08 - Display System informations
09 - Full Options menu
10 - Reset System
The manual startup via the Bios menu do not invalidate the hard disk and allows to reboot on the hard disk in case of failure on
the server

26
CPU starting up on the network
BOOTP request to obtain IP settings
The PC server replies and sends information and file name to be downloaded
(startup.txt)
Download with TFTP of startup.txt
It contains the name, the size and type of files to download
Downloading of files vmlinux.bin and initrd.img
Starting a minimum linux provided by initrd.img
DHCP request to obtain a full IP configuration
Launching of the automatic installation procedure

27
Example of startup.txt file:
/bootp/linux/18.0_18.1/alize/vmlinux.bin;1267568;BIN;1048576;1048576
/bootp/linux/18.0_18.1/alize/initrd.img;3855709;RAMDISK;4194304;0
ramdisk_size=3855709,root=/dev/ramdisk,console=ttyS0,panic=5;60;CL;0;0
boot;0;BOOT;0;1048576
This file shows the path to the files used for loading, the file type , its size and the
position in memory .
vmlinux.bin:
binaries of a minimum Linux allowing to start the installation procedure on the hard
drive.
initrd.img:
Ensures the creation of a virtual disk in RAM to charge a minimum Linux in memory
and start the system.
The RamDisk is setup to start an automated Linux installation procedure via FTP.

28
Complete release loading – CPU 7 Crystal
#CPU 7 BIOS Monitor

....................... Hardware autotest .......................
value of DIL switch 01
YOU CAN strike Ctrl B to enter in BIOS monitor during several seconds from NOW
!
Ctrl B
hit [Ctrl I] for BIOS monitor! Ctrl I
CPU7 Password or CR ?:

29
CPU starting up on the network (cont’)
BIOS Loader Menu

2 - Load From Ethernet (Alize method)
3 - Load From Ethernet (4400 method) 3
5 - MAC Address
6 - PCMS id
7 - System informations
8 - Set interface KENDIN to default(auto-nego)
9 - Interface KENDIN state
10 - Set Interface KENDIN
11 - Ethernet embedded interface state
12 - Full Option Menu
13 - Reset System
CPU7 > 3

30
ACT4400 specific INSTALLATION data input:

=========================================
Standard installation (y/n, default is y)?:
TEL version ?: J14103b.fr
Phase 1: address determination and bootfile selection

=====================================================
NB: All parameters below are optionnal.
Default internet Address: *** Unknown ***

New Internet Address:
Name of default BOOTP/TFTP server: *** Unknown ***

Name of a new BOOTP/TFTP server:
Default loaded file:

New loaded file: %72.0
BOOTP request in progress ..............
New loaded file:

Name of the directory where is located the linux.ram to load
The character « % » must be enter before the name
The directory is located in: /DHS3mgr/« Release »/pcmao/boot_res/linux/

31
BOOTP requests to obtain the IP configuration
The PC server replies and sends the information and the file
name to be downloaded (linux.ram)
Downloading with TFTP of linux.ram
Starting up of Linux minimum provided by linux.ram
DHCP request to obtain the full IP configuration
Launching of the automated installation procedure
linux.ram:
Minimum Linux kernel that allows the TCP network configuration and that contains the main installation utilities.
It is configured for starting an automated installation via ftp.

32
Complete release loading - Appliance Server/ Blade Server
Different cases of starting up
The hard disk is empty
The complete release loading starts automatically
Release is already installed, the disk can be disabled
If Linux is started, log with root account and type:

grubboot ETHER then reboot the call server
Otherwise, interrupt the system in GRUB with c and type:

Press enter to boot the default OS [0], 'c' for a command-line,
or give an another entry number
grubboot ETHER then reboot
At the reboot, the system recovers the case of an empty disk

33
Different starting up cases (cont’)
Force the boot on the network in the bios
Connect a screen and a keyboard on the Appliance Server
Connect the network on ETH1 for Appliance server and ETH0 for Blade server(1)
Interrupt the server starting up by pushing F1
Force starting up on boot PXE
Depending on the bios version, menus can vary
In case of change in server starting up order, do not forget to reconfigure it in a proper way
after!
(1) – for the first loading (after receiving the blade and server) use the first integrated switch for loading (B1)

34
PXE request to obtain IP configuration
The PC server replies and sends information and the name of the file to download
(pxeloader)
Downloading with TFTP of pxeloader file
The server switches inputs/outputs on the V24 port
Downloading of linux.ram
Starting up of the minimum Linux provided by linux.ram
DHCP to obtain the full IP configuration
Launching of the automatic installation procedure

35
Complete release loading - Common part for all CPUs
Once the Linux kernel is in memory, the Linux

installation on the disk begins
Loading with FTP with account anonymous
Welcome to Alcatel-Lucent e-Mediate installation
+-----------------------------+ Loading +-----------------------------------+

| |
| Loading second stage ramdisk... |
| |
+---------------------------------------------------------------------------+
<Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen
Automatic installation of the swinst package

36
Automated version installation by swinst
Creation of the accounts and the directories
*** Creation of user mtcl

*** Creation of user adfexc
*** Creation of the missing main directories
*** Creation of the missing swinst directories
A daily backup will be executed on cpu disk

at 5 hour 45 min
WARNING: no delivery has been installed
The path of the delivery is /dhs3mgr/G1300
The previous version will be erased before the new installation

to avoid for some old files to remain on your CPU.
end of remove procedure

37
swinst allows the installation of release and patch
It executes :
The users accounts creation
The necessary tree diagram creation for a good working of the telephonic
application
The configuration of an automatic database backup on the disk
The release installation
The patches installation
The Linux updating upgrades are included in the patches
A default IP configuration IP
The system reboot

38
Automatic release installation with swinst
Call handling (Telephonic application) binaries
….
DHS3bin/oneshot/mtcl/getpilconf_test
DHS3bin/oneshot/mtcl/qconf
DHS3bin/oneshot/mtcl/btracer.config
DHS3bin/oneshot/mtcl/trcterm
DHS3bin/oneshot/mtcl/debug_csta
DHS3bin/oneshot/mtcl/getpilconf
DHS3bin/oneshot/mtcl/getpilconf_sun
DHS3bin/oneshot/mtcl/pilot
DHS3bin/oneshot/mtcl/pilot_sun
DHS3bin/oneshot/mtcl/pilot2
DHS3bin/oneshot/mtcl/pilot2_sun
DHS3bin/oneshot/mtcl/pilot2a
DHS3bin/oneshot/mtcl/pilot2a_sun
DHS3bin/oneshot/mtcl/lis
DHS3bin/oneshot/mtcl/lisX25
DHS3bin/oneshot/mtcl/trt2
….

39
Automatic release installation with swinst
End of binaries loading
(c) Alcatel-Lucent e-Mediate / Linux (C) 1999 Red Hat Software
+----------+ Reboot +----------+

| |
| |
| Do you want reboot the CPU |
| +-----+ +----+ |
| | Yes | | No | |
| +-----+ +----+ |
| |
+------------------------------+
<Tab>/<Alt-Tab> between elements | <Space> selects | <F12> next screen
If no action from the operator, the reboot is automatic

40
Security questions
During the first starting up, you have questions about the security
management
Do you want to activate server security high level (Y/N) ? n Enter “n”
Select the security level :
R) configuration to be restored
0) Level_0 = no security features activated
1) Level_1 = passwords/aging
2) Level_2 = passwords/aging + trusted hosts/TCP wrapper
3) Level_3 = passwords/aging + trusted hosts/TCP wrapper + SSH
Please select a level (R/0/1/2/3, default is 3) ? 0 Enter “0”

Security configuration :
[-] Default passwords and no aging password configured.
[-] No isolation from ethernet / no trusted host / no TCP wrapper.
[-] The SSH security is currently NOT set.
Do you confirm those changes (Y/N, default Y) ? y Enter “y”
The security management could be done later with “netadmin” and “Swinst”

41
After software installation:
Set up IP configuration
use netadmin
Restore customer database or create an empty database

use swinst
Install licenses files in /usr4/BACKUP/OPS

transfer the files with FTP or 4760
install with swinst utility
Reboot the system

command shutdown –r now

42
Crystal CPU Type loading
PROCEDURE
OBJECTIVE
- To learn how to load a full release on a Crystal CPU Type
DOCUMENTATION
- Technical Communication TC0631
- System Documentation: R8.x System Documentation/Technical Documentation/System/Call Server
OVERVIEW
Standard installation of a Crystal CPU Type consists in automatically loading a basic version
(basic release) or basic version + static patch or basic version + static patch + dynamic patch to
the Call Server hard drive. Standard installation is performed in several steps:
1. Create a directory on the PC server called dhs3mgr.this directory will contain a basic
version, a static patch and dynamic patch E.g.:
2. The Call Server must perform a network boot on the installation server PC on which the
ENTERPRISE PC INSTALLER application is running.
3. The installation server PC provides the Call Server with an IP address via DHCP.
4. The installation server PC provides the "linux.ram".
5. The installation server PC provides the Linux OS, swinst packages, and telephone
application binaries via FTP.
6. The Call Server restarts automatically when installation is complete.
Note: RECOMMENDATION before the Upgrade:
Before upgrading an existing installation, SAVE the Alcatel-Lucent OmniPCX
Enterprise database on the Call Server hard disk and transfer the database
backup file to the PC.
Issue 03 Ref. ENTP0842C01TEUS.doc P. 1

All Rights Reserved © 2007, Alcatel-Lucent
43
PROCEDURE
1. PC Installer configuration
To install the PC Installer, Run the executable file in the following directory. For more
explications consult the technical communication TC0631.
1.1. Drive selection
Application PC Installer
Path Preferences/Drive
Parameter D: (example, choose the drive where the release is)
Remark The folder name where the release is must be dhs3mgr
1.2. Full installation selection
Path Installation type
Parameter Linux + Call handling
Remark After the installation type selection, a new window is opened
P. 2 Ref. ENTP0842C01TEUS.doc Issue 03

44
1.3. Call server type selection
Application PC Installer (second window)

Path Call Server type
Parameter A4400
Remark Call Handling version, country code and installation type will be attributed
later in the lab.
1.4. Connection type selection

Path Network type
Parameter Direct cable
Remark It is better to use a direct connection with the CPU to load it.
In case of connection through the company network, the Ethernet address
(MAC address) of the CPU must be set in the Ethernet address field.
1.5. PC Installer parameters validation

Action Click on Apply button

45
2. CPU 7 loading process
Application On CPU
Login / Pass mtcl / mtcl
Parameter Shutdown –r now
YOU CAN strike Ctrl B to enter in BIOS monitor during several
Result seconds from NOW !
Action Ctrl B
hit [Ctrl I] for BIOS monitor!
Result
Action Ctrl I
CPU7 Password or CR ?:
Result
Action Press “Return”
BIOS Loader Menu
Result
2 - Load From Ethernet (Alize method)
3 - Load From Ethernet (4400 method)
5 - MAC Address
6 - PCMS id
7 - System informations
8 - Set interface KENDIN to default(auto-nego)
9 - Interface KENDIN state
10 - Set Interface KENDIN
11 - Ethernet embedded interface state
12 - Full Option Menu
13 - Reset System
Action 3 - Load From Ethernet (4400 method)
ACT4400 specific INSTALLATION data input:
Result
=========================================
Standard installation (y/n, default is y) ?:y
TEL version ?:
Parameters G13007b.us
Phase 1: address determination and boot file selection
Result
=========================================
NB: All parameters below are optional.
Default internet Address: *** Unknown ***
New Internet Address:
Name of default BOOTP/TFTP server: *** Unknown ***
Name of a new BOOTP/TFTP server:
Default loaded file:
New loaded file:

46
Parameters Press “Return” several times until this question: “New loaded file:”
Enter %52.0 (for instance)
Remark
TEL version? G13007B.us Language (e.g US)
Full release (patch included)
New loaded file: %52.0 Verify the folder in

dhs3mgr/release name (example: G1300)
Enter % for Linux /pcmao/boot_res/bootp/linux

47

48
CPU-CS/CS2 and Appliance Server Type loading
PROCEDURE
OBJECTIVE
- To learn how to load a full release on a CPU-CS/CS2 and Appliance Server
DOCUMENTATION
- Technical communication TC0631
- System Documentation: System Documentation/Technical Documentation/System/Call Server
OVERVIEW
Standard installation of a CPU-CS/CS2 and Appliance Server consists in automatically loading a
basic version (basic release) or basic version + static patch or basic version + static patch +
dynamic patch to the Call Server hard drive. Standard installation is performed in several steps:
1. Create a directory on the PC server called dhs3mgr.this directory will contain a basic version,
a static patch and dynamic patch E.g.:
2. The Call Server must perform a network boot on the installation server PC on which the
ENTERPRISE PC INSTALLER application is running.
3. The installation server PC provides the Call Server with an IP address via DHCP.
4. The installation server PC provides the "linux.ram" or the "pxeloader" for an Appliance Server
via TFTP.
5. The installation server PC provides the Linux OS, swinst packages, and telephone application
binaries via FTP.
6. The Call Server restarts automatically when installation is complete.
Note: RECOMMENDATION before the Upgrade:
Before upgrading an existing installation, SAVE the Alcatel OmniPCX database on
the Call Server hard disk and transfer the database backup file to the PC.

49
PROCEDURE
1. PC Installer configuration
To install the PC Installer, Run the executable file in the following directory. For more
explications consult the technical communication TC0631
1.1. Drive selection
Path Preferences/Drive
Parameter D: (example, choose the drive where the release is)
Remark The folder name where the release is must be dhs3mgr
1.2. Full installation selection
Path Installation type
Parameter Linux + Call handling
Remark After the installation type selection, a new window is opened

50
1.3. Call server type selection

Path Call Server type
Parameter Alize/Appliance server/CS2
1.4. Release to install selection

Path Call handling version
Parameter G13007b (e.g.)
Remark Give the full release (including the last patch)
1.5. Country selection

Path Country
Parameter us (example for U.S.)
1.6. Connection type selection

Path Network type
Parameter Direct cable
Remark It is better to use a direct connection with the CPU to load it.
In case of connection through the company network, the Ethernet address
(MAC address) of the CPU must be set in the Ethernet address field.
1.7. PC Installer parameters validation

Action Click on Apply button

51
2. CPU Reset and boot on Ethernet
2.1. CPU-CS/CS2 (or Appliance server) with an empty hard disk
Application On the call server

Action Switch on the power of the CS/CS2 board
Remark If the hard disk is empty, the loading starts automatically.
If the hard disk contains a call handling software see 2.2
2.2. With a hard disk containing the call handling software

Login / Pass root / letacla
Command grubboot ETHER
Result Disk have to be reinstalled after reboot.
The system will automatically reboot after confirmation.
Do you want to continue (y/n, default y):
Parameter Y
Note: At the end of loading, the CPU restarts automatically. ” PC Installer” windows can
be then closed. Now, the following actions must be done on the CPU:
CPU IP configuration using “netadmin” command
Data base restoration or empty data base creation
Soft licenses files restoration

52
CS Software loading – Mono version mode
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to download a Call server with the Alcatel-Lucent OmniPCX Enterprise software
MANAGEMENT
1. Do not use the hard disk “Training” installed on your CS.

Ask to the trainer an empty hard disk and install it on board in the place of the initial
hard disk.
2. Check wiring (IP and V24) between your PC and OmniPCX Enterprise.
3. Check that the version of Alcatel-Lucent OmniPCX Enterprise is located in the repertory
“/DHS3mgr” on your PC.
4. Install the software of CPU loading (OmniPCX Enterprise PC Installer) on your PC. The way
of the setup.exe is: \dhs3mgr\”release”\pcmao\boot_res\pcinstall.
5. Carry out the loading of the version on your CS as indicated in the procedure.
Issue 04 Ref. ENTP0842H01TEUS.doc HO. 1

53
CS Software loading – Mono version mode
HO. 2 Ref. ENTP0842H01TEUS.doc Issue 04

54
Alcatel-Lucent University NOTES
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
55
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
56
Multi version loading
OBJECTIVE
To make a multi versions loading
Alcatel-Lucent OmniPCX Enterprise – Multi version loading

57
CS software loading - Multi versions mode
Overview
Multi-version loading allows two versions to be simultaneously installed on the

same hard disk.
Different Releases
Different Releases including correction’s patch
Its main advantage is that a 2nd version can be set up on the Call Server
without stopping the telephone application.
Once the 2nd version is installed, you simply restart the Call Server on it.
In case of problem it is possible to switch back to the old version which is

still present.

58
Overview
There are two cases of Multi-version loading
Copy of the complete first version and loading of a software patch for update
Possible when the basic version stays the same
Complete loading of a new version and copy of the data (telephone database
and Linux data) from the old one.
To be used for a different version of Linux
The OPS files may have to be changed as well
Multi-version loading is advantageous for a patch, because everything can be prepared remotely.

59
Structure of the hard disk
The directory structure for the hard disk
/root2_d /
Second release First release
on the disk on the disk
/var2 /var
/usr5 /usr2
/usr6 /usr3
/usr7 /usr4
Common part
During the initial release Installation,hard disk is automatically partitioned (automatically format).

60
Structure of the hard disk
The directory structure for the hard disk
Disk partition with the ACTIVE version

/ Active Linux operating system
/usr2 (linked with /DHS3bin) Active OXE version
/usr3 (linked with /DHS3data) Active Data Base
/var Logs and active variable data
Common part
/usr4 (linked with /DHS3dyn) Dynamic accounting data
/usr7 (linked with /DHS3ext) System voice guides
Disk partition with the INACTIVE version

/root2_d (linked with /root2) Inactive Linux operating system
/usr5 (linked with /DHS3bin2) Inactive OXE version
/usr6 (linked with /DHS3data2) Inactive Data Base
/var2 Logs and inactive variable data
DHS3xxx directories are links to others directories in the disk. They are used in installation scripts,the inactive partition is
generally mounted in the /dev/null directory.
ver2cho visible command allow to mount partitions in home directory.
(1)xa000000> ver2cho visible ; df -v
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda5 495876 84823 385452 18% /
/dev/hda7 1007960 234172 722584 24% /usr2
/dev/hda8 1007960 97124 859632 10% /usr3
/dev/hda9 4276616 536836 3522536 13% /usr4
/dev/hda15 2015984 51400 1862176 3% /usr7
/dev/hda6 396623 4292 371845 1% /var
/dev/hda11 495876 84812 385463 18% /root2_d
/dev/hda12 396623 2341 373796 1% /var2
/dev/hda13 1007960 234544 722212 25% /usr5
/dev/hda14 1007960 97096 859660 10% /usr6
/dev/hda13 1007960 234544 722212 25% /root2_d/usr2
/dev/hda14 1007960 97096 859660 10% /root2_d/usr3
/dev/hda9 4276616 536836 3522536 13% /root2_d/usr4
/dev/hda15 2015984 51400 1862176 3% /root2_d/usr7
/dev/hda12 396623 2341 373796 1% /root2_d/var
Ver2cho hidden command is used to mask Inactive partitions.

(1)xa000000> ver2cho hidden ; df -v
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda5 495876 84823 385452 18% /
/dev/hda7 1007960 234172 722584 24% /usr2
/dev/hda8 1007960 97124 859632 10% /usr3
/dev/hda9 4276616 536836 3522536 13% /usr4
/dev/hda15 2015984 51400 1862176 3% /usr7
/dev/hda6 396623 4292 371845 1% /var

61
First possibility - Copy then patch loading
Initial state: The active part of the disk only is loaded
Example of versions on the disk:
Active partition Inactive partition

linux : 67.0 linux : -----
swinst : 2.54.0 swinst : -----
binaires : I1.605.0 binaires : -----
1) Total duplication of the active to the inactive partition
State of versions on the disk:

linux : 67.0 linux : 67.0
swinst : 2.54.0 swinst : 2.54.0
binaires : I1.605.0 binaires : I1.605.0

62
First possibility - Copy then patch loading
2) Loading of the patch in the inactive partition

swinst : 2.54.0 swinst : 2.57.0
3) Versions switch

swinst : 2.57.0 swinst : 2.54.0

63
Second possibility - Complete loading
Initial state: The active part of the disk only is loaded

linux : 67.0 linux : -----
1) Loading of Linux in the inactive partition
State of versions on the disk after loading:


64
2) Loading of the complete version in the inactive partition

swinst : 2.57.0 swinst : 2.58.0
binaires : I1.605.12 binaires : J1.410.0
3) Loading of a binary patch in the inactive partition

swinst : 2.57.0 swinst : 2.59.0
binaires : I1.605.12 binaires : J1.410.1
Notes:
In this example we could as well download the dynamic patch J14101b ( 3rd step )

65
4) Copy of the Linux data and the database from the active partitions to the
inactive ones
5) Reboot of the CPU on the inactive partitions
State of versions on the disk after switch:

swinst : 2.59.0 swinst : 2.57.0
binaires : J1.410.1 binaires : I1.605.12
6) Installation of the new OPS files (if required)
7) Reboot the Call Server (if required)
In case of trouble ,it is possible to go back to previous release switching again to the initial partition.
Remark:
During the switch ,boards can receive new binaries from new release.If you decide to go back with the initial release ,another
downloading will be done if necessary.

66
Release Installation using the multi partition
PROCEDURE
OBJECTIVE
- To learn how to Install a new version using the multi-partition solution.
OVERVIEW
Initial hard disk configuration: In this example we could imagine two different release. E.g.:
R9.1 on active partition: Basic version I1605, static patch I160512 and dynamic patch
I160512c already installed on active partition.
Objective of this lab:

Install a new release ex R10.0. In that case (when basic version are different) it will be
necessary to process in the following way:
1. Download separately the Linux on inactive partition.

2. Download the basic version and different patches in the inactive partition.
3. Duplicate and translate database from active to inactive partition in order to switch finally
on the new release.

67
PROCEDURE
1. Download Linux on the inactive partition
1.1. Run the OmniPCX Enterprise PC Installer application on the PC and select the loading
option
Application On the PC server Tab

Action Run the program “OmniPCX Enterprise PC Installer”
Result
Action Select “Linux on inactive partition”

Result

68
1.2. Select the Linux version to load on inactive partition
Application On the call server Tab

Login / Pass swinst / SoftInst
Action 2 - Expert menu
Action 1- Packages installation
Action 4 - Install Linux on inactive version from server
Result Enter the name of the server ->
Parameters 10.1.1.10 (for instance)

Remark Use the IP address of the PC from which you want to install the patch. We
could used the PC host name if it has been managed on netadmin menu.
Enter directory of linux on 10.1.1.10 (default /bootp/linux) ->
Result
Action Press “Enter”
Enter the name of the linux version (eg:11.0)->
Result
Parameters 72.0
Remark To know the Linux version it could be useful to consult the following way in
the dhs3mgr directory on the PC server
Clean the second linux version. confirm (y/n, default is y):

Result
Parameters y
You will erase the actual bootp server if you respond yes to this
Result question has this cpu to be a bootp server for major installation
(y/n, def is y):

69
Parameters y
Clean the /bootp/linux actual content. confirm (y/n, default is y):
Result
Parameters y
2. Installation of the new release R10.0
2.1. Basic version installation on the inactive partition

Action Run the program “OmniPCX Enterprise PC Installer”
Result
Action Select “Call handling or patch”

Action 2 - Deliveries installation
Action 1 - Install delivery from server
Press 0 for the active version Press 1 for the inactive version
Result
Parameters 1

70
Result Enter the name of the server ->
Parameters 10.1.1.10 (for instance)

The installation of the binaries will modify the current installed
Result versionPlease, confirm the installation of a new version (y/n, default
y):
Parameters y
Enter the full path of the delivery on the server
Result
example for Unix server: /twdhs3/dhs3ref/dhs3ref_d1/E1.500/LIVRAISON
for Windows server: /dhs3mgr/E1500
Parameters /dhs3mgr/J1410
confirm the full path /dhs3mgr/J1410 (y/n, default y):
Result
Parameters Y
The path of the delivery is /dhs3mgr/J1410
Result
Do you wish to secure the installation (y/n):
Parameters n
Check linux version
Result
Transfer for pkg part in preparation
linux/dhs3mod-1.10a_30-15alc.i386.rpm
linux/netadmin-4.4.17-20alc.i386.rpm
RPMS/lx_version-4.4-4alc.i386.rpm
--> Searching for symbolic link '/DHS3bin/nmc/log' on target
'/DHS3dyn/tmp' ...
WARNING: symbolic link '/DHS3bin/nmc/log' already exists.
Set chown 'mtcl:tel' on '/DHS3bin/nmc/log' ...
<-- Symbolic link '/DHS3bin/nmc/log' successfully created.
@@@@@ End of post_inst at Fri Dec 3 09:42:00 CEST 2010
End of post installation
Remark Patches Installation (static and dynamic)

The process to download patches is exactly the same than downloading
Basic version. The only parameter which will change will be the way in
dhs3mgr directory.
For the Static patch: under swinst menu select
/dhs3mgr/I14103
Pour le patch dynamique :
/dhs3mgr/I14103b
2.2. Duplicate database from active to inactive partition

71

Action 3 - Cloning & duplicate operations
Action 2 - Partitions duplication
Action 4 - Duplicate database
Confirm the duplication of the database confirm (y/n, default is y):
Result
Parameters y
Remark In case of migration, the system could will ask you to translate the
database before to duplicate it. If it ‘s happen entry “YES” to translate the
database .
2.3. Switch the versions

Action 3 - Switch on inactive version
Check linux version
Result
'/DHS3dyn/tmp' ...
@@@@@ End of post_inst at Fri Dec 3 09:42:00 CEST 2010
Result Please confirm switching on the inactive version (y/n, default y):
Parameters y
Autostart is set on unactive version
Result
Do you want to switch back to the previous version if system resets
(y/n, default n):
Parameters n
In order to complete the installation of the swinst package
Result
you have to connect as swinst user after the switching
Do a version switch. Confirm (y/n, default y):

72
Parameters y
Remark After this confirmation the system will restart automatically
It will be mandatory to enter the country code during the first connection
to the swinst menu.

73

74
Multi version loading /Static and Dynamic patches
PROCEDURE
OBJECTIVE
- To learn how to perform a static and dynamic patches using the multi version loading.
OVERVIEW
A basic version and a static patch are already Installed on active partition.
Objective of this lab:

1. Duplicate Linux and binaries from active partition to inactive partition.
2. Install dynamic patch on the inactive partition.
3. Check that multi version has been done properly then switch the version.

75
PROCEDURE
1. Duplicate the active version partitions to the inactive version ones*
1.1. Check the version already install on the active partition
Application On the Call Server Tab

Command siteid
Application software identity
Result
R8.0-g1.300-7-fr-c80s1
Business identification: R8.0
Release:
DELIVERY g1.300
Patch identification: 7
Country: fr
Cpu: c80s1
ACD VERSION
release : 6
bug_fixing : 1
protocol_id : 90
version_dy_hr_stat : 11
Press return

76
1.2. Duplicate the active version partitions to the inactive version one

Action 2 - Partitions duplication
Result
ALCATEL BUSINESS SYSTEMS
Partitions duplication operation menu Installation FACILITIES 2.44.0
1 Duplicate Linux, packages and Linux data

2 Duplicate Linux data
3 Duplicate delivery
4 Duplicate database
5 Duplicate all
Q Go back to previous menu
Your choice [1..5, Q] ?
Action 5 - Duplicate all

Confirm the duplication of all (y/n, default y):
Result
Parameter y

77
2. Check that every steps is done properly during the duplication
Note: After entering “y” the system displays the duplication’s steps

Result Linux partition duplication:
Duplicating Linux and packages

Clean the second Linux version. Confirm (y/n, default is y):y
Second version cleaned
setup-2.1.9-22mdk_3alc
filesystem-2.0.6-2mdk_1alc
ld.so-1.9.11-4mdk_2alc
glibc-2.1.3-16mdk_3alc
…
Please wait, working
Result Network settings duplication:
Duplicating the network configuration

Duplicate the network configuration in the second Linux version.
Confirm (y/n, default is y):
Please wait, working ...
The network configuration is duplicated
Result Swinst duplication:

facil/swinst-2.23.0-4alc.i386.rpm
End of duplication for pkg part files
Result Binaries files duplication:
checking Linux version

LINUX 33.3 is already installed
Running mkusers ...
/rootbis/DHS3bin/lib/librt-2.1.2.so
/rootbis/DHS3bin/lib/libutil-2.1.2.so
/rootbis/DHS3bin/downbin/bnvintgd
/rootbis/DHS3bin/downbin/bnvintof
/rootbis/DHS3bin/downbin/bnvintofs

78
Result Database duplication:
Stop the mao process…

Building list of files….
Deleting the old files on unactive version….
/rootbis/DHS3data/mao/SUBSPNM.idx
/rootbis/DHS3data/mao/SUFFDATEM.dat
/rootbis/DHS3data/mao/SUFFDATEM.idx
/rootbis/DHS3data/mao/SUPERVM.dat
/rootbis/DHS3data/mao/SUPERVM.idx
/rootbis/DHS3data/mao/SYSOPTM.dat
/rootbis/DHS3data/mao/SYSOPTM.idx
……
8763 blocks
Action Select “q” to go back to the previous menu in order to exit
Note: The duplication of the active partition is done on the inactive partition
3. Check the use rate of the partitions on the hard disk, and their links to the logical names

Command ver2cho visible
Command df -v
Filesystem 1K-blocks Used Available Use% Mounted on
Result
/dev/hda5 495876 85631 384644 19% /
/dev/hda7 1007960 268368 688388 29% /usr2
/dev/hda8 1007960 161252 795504 17% /usr3
/dev/hda9 4276616 39456 4019916 1% /usr4
/dev/hda15 2015984 41508 1872068 3% /usr7
/dev/hda6 396623 4049 372088 2% /var
/dev/hda11 495876 86234 384041 19% /root2_d
/dev/hda12 396623 3010 373127 1% /var2
/dev/hda13 1007960 268336 688420 29% /usr5
/dev/hda14 1007960 161128 795628 17% /usr6
/dev/hda13 1007960 268336 688420 29% /root2_d/usr2
/dev/hda14 1007960 161128 795628 17% /root2_d/usr3
/dev/hda9 4276616 39456 4019916 1% /root2_d/usr4
/dev/hda15 2015984 41508 1872068 3% /root2_d/usr7
/dev/hda12 396623 3010 373127 1% /root2_d/var
Note: Comparing both partitions, they’re totally identical (from the size point of view)

79
4. Installation of a new patch on the inactive partition
4.1. Run PC Installer

Action Click on the icon:
Result
Action Select “Call handling or patch”
Note: The rest of the process is done under swinst

80
4.2. Installation with swinst

Result Press 1 for the inactive version and Enter the name of the server ->
Parameter 10.1.1.10 (for Instance)

Remark Use the IP address of the PC from which you want to install the patch. We
could used the PC host name if it has been managed on netadmin menu.
y):
Parameter y
Result
Parameter /dhs3mgr/G13007b (for instance)

Result confirm the full path d:/dhs3mgr/G13007b(y/n, default y):
Entry y
Result The path of the delivery is d:/dhs3mgr/G13007b
Check linux version

Result
'/DHS3dyn/tmp' ...
WARNING : symbolic link '/DHS3bin/nmc/log' already exists.
@@@@@ End of post_inst at Mon Apr 15 09:42:00 CEST 2007

81
4.3. Switch the versions

Login / Pass Swinst / SoftInst
Action 3 – Cloning & duplicate operations
Action 3 – Switch on inactive version
Please confirm switching on the inactive version (y/n, default y):
Result
Parameter y
Check linux version
Result
'/DHS3dyn/tmp' ...
WARNING : symbolic link '/DHS3bin/nmc/log' already exists.
Parameter y
Autostart is set on inactive version
Result
Do you want to switch back to the previous version if system resets
(y/n, default n):
Parameter n
In order to complete the installation of the swinst package
Result
you have to connect as swinst user after the switching
Do a version switch. Confirm (y/n, default y):
Parameter y
Remark After this confirmation the system will restart automatically
It will be mandatory to enter the country code during the first connection
to the swinst menu.

82
5. Check the versions installed in the active partitions

Action 8 - Software Identity display
Action 2 - Application software identity
Press 0 for the active version, 1 for the inactive one or q to quit
Result
Parameter 0
Application software identity
Result
R8.0-g1.300-7-b-fr-c80s1
Business identification: R8.0
Release:
DELIVERY g1.300
Patch identification: 7
Dynamic patch identification: b
Country: fr
Cpu: c80s1
ACD VERSION
release : 6
bug_fixing : 1
protocol_id : 90
version_dy_hr_stat : 11
Press return

83

84
CS Software loading – Multi version mode
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to perform a software upgrade using multi version
MANAGEMENT
Initial hard disk configuration: Current release -1 (eg: Training release R10, loading hard disk
R9.1)
1. Check by swinst the active and inactive versions installed on the hard disk
2. Check by the “ver2cho visible” and “df –v” commands the used space in the active and
inactive part of the hard disk.
3. Make a complete copy from the active to the inactive part of the hard disk.
4. Check the differences on the hard disk by swinst and the ‘df –v’ command.
5. Following the multi-version procedure, load the current release in the inactive part of the
hard disk
6. Check the versions by swinst again.
7. Make a version switch and check that everything’s alright as the CPU starts up.

85
CS Software loading – Multi version mode

86
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
87
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
88
Call handling and Patch loading
OBJECTIVE
To describe how to install a patch
Alcatel-Lucent OmniPCX Enterprise – Call handling and Patch loading

89
Principles
Installation of the Call handling
Used for installation of the Call handling by keeping the customer’s database
Installation of patch is necessary in case of:
System improvement
Correction of bugs
Addition of new features
…
Using of features
E.g. security patch for IP touch security solution (Thales)
…

90
Principles
Loading configuration in swinst
Call Files request (version/patch) via FTP

Server
Files transfer (common part)
Files transfer (depending on the country)
End of version or patch loading

V24 link
Ethernet link

91
Principles
The software version or patch manual loading is done via swinst

Connection to the system for the control can be by V24 or via Telnet
Several cases:
Complete version loading(the previous version will be deleted except in
« multi-partitions »)
A version does not have a correcting patch
Static patch loading
This kind of patch contains correcting files that requires the call handling
(telephonic application) to be stopped before loading.
Dynamic patch loading
This kind of patch contains correcting files that does not need the stopping of the
telephonic application.
For a version or a patch, the loading is done in 2 steps (maximum)

step 1: the files common to all OmniPCX Enterprise installations.
step 2: the files specific to the country

92
Principles
Call handling replacement is possible via swinst
Previous version will be automatically deleted
The call handling (telephone) must be stopped
Version updating with patch is done the same way
Depending on the patch, telephone must stop or not
Static patch: the system must stop
Dynamic patch: stopping the system is not necessary
A manual version updating allows to keep intact customer’s data .

The version deletion does not affect the customer’s data , the tickets or the voice guides.
On the other hand, a standard installation formats the disk. So it is necessary to save the database before.

93
Loading tool
Setting up loading tool
Select the drive where the

version to be installed is located
Warning: Check if a new version

of PC Installer is available with
the patch to install!!!!

94
Configuration in swinst
Patch loading with swinst
Alcatel-Lucent BUSINESS SYSTEMS

FACILITIES Expert menu Installation FACILITIES 2.18.0
1 Packages installation
2 Deliveries installation 2
3 Cloning & duplicate operations
4 Backup & restore operations
5 OPS configuration
6 System management
7 Database tools
8 Software identity display
9 Remote download
Your choice [1..9, Q]? 2
This menu allows to install a new version or a patch (static or dynamic)
Expert menu is accessible by selecting 2 in the main menu of swinst.

95
Patch loading with swinst (cont’)
Alcatel-Lucent BUSINESS SYSTEMS

Delivery menu Installation FACILITIES 2.18.0
1 Install delivery from server 1

2 About last install deliveries operations
Your choice [1..2, Q]? 1
Enter the name of the server -> 10.253.253.10
The installation of the binaries will modify the current installed version
Please, confirm the installation of a new version (y/n, default y):

-> /dhs3mgr/J14103b
Confirm the full path /dhs3mgr/G15006i (y/n, default y):
The path of the delivery is /dhs3mgr/G15006i
Enter the name of the server:

It is possible to indicate a name (if it is declared in /etc/hosts file with netadmin) or an IP address.
The server name or address are kept in memory for the next loading.
Enter the full path of the delivery on the server:

Enter the path to access the telephonic application (call handling) binaries or patch.
This path can refer to a drive letter to bypass the PC Installer tool configuration
In Windows environment the case is not important (case of PC Installer).

96
Patch loading with swinst (cont’)
Do you wish to secure the installation (y/n): n

End of remote copy for pkg part files
LINUX 33.0 is already installed

*** Creation of the missing swinst directories
Transfer for comm part in preparation

Remote copy for comm part files is in progress ...
DHS3bin/descript/dyn_id
DHS3bin/descript/dynlinux.list
.......... Files downloading ..........
etc/pam.d/gcsconfig
End of remote copy for comm part files
Setting permissions on files ...

End of operation!
Press return

It is possible to create a backup of all the files contained in a patch before they are being replaced.
At the end of installation swinst proposes to delete the backup or to keep it. By keeping it , it will be possible to come later back
to the previous patch in case of dysfunction of the new one (new entry in swinst menu in this case).
At any time it is possible to verify the loadings done by swinst by consulting About last install deliveries operations.

97

98
Upgrade using Static and Dynamic patches
PROCEDURE
OBJECTIVE
- To learn how to perform a software version upgrade using static and dynamic patches
DOCUMENTATION
- Technical Communication TC0631
- System Documentation: System Documentation/Technical Documentation / System / Call

Server
OVERVIEW
The installation of a patch is carried out with the OmniPCX Enterprise PC Installer and swinst
software on the OmniPCX Enterprise .
For the telephone application, there are two types of patches:
Static patch
Dynamic patch
Telephone patches are delivered as a cpiofile file (Unix compressed file) located in the directory
\dhs3mgr\<version>\dhs3linux
Example: \dhs3mgr\G13007\dhs3linux\comm\cpiofile.
Most binaries are located in the comm directory.
For country-specific binaries, the cpiofile file is at the same level of the tree structure but in a
directory named according to the international standard.
Example: es for Spain, ch for Switzerland, etc.

99
PROCEDURE
1. Open OmniPCX Enterprise PC Installer
Application On the PC
Action Double-click on the icon of the OmniPCX Enterprise PC Installer on the
desktop
Parameter In the menu Preferences, select the drive that contains the patch.
Parameter In the field Installation type, select the type of installation to "Call handling
or
patch only".
Remark A FTP server are run during all the installation of the patch and are stopped
only when the window OmniPCX Enterprise PC Installer is closed.
2. Static telephone patches
A static patch can easily be distinguished from a full version by the presence of two text
files, for_comp and patch, located in the CD-ROM tree structure in:
<CD-ROM root>\dhs3mgr\<patch name>\installinux\
The file for_comp is used when installing a full version in standard mode (see the
procedure ”Load a software version - Standard installation of a complete version’’). For a
static patch, this file contains the name of the full version associated with the patch.
The file patch gives the patch version.
e.g.: for the static patch G1.300.7 with a CD-Rom drive mapped on D:, there will be the
file D:\dhs3mgr\G13007\installlinux\for_comp containing the string “G13007”
D:\dhs3mgr\G13007\installlinux\patch containing the string “patch_G1.300.7”.
Static patch name is usually the name of the full version followed by the patch number.
Each new static patch includes all corrections made in previous patches.
2.1. Install a static patch

Login / Pass Swinst /SoftInst
Action 1 - Easy menu
Action 7 - Stop the telephone

100
Remark These patches are new telephone application files containing corrections or
upgrades. They can only be installed with the phone shut down or when
installation is on the inactive partition
They are installed after a full version has been installed. They cannot run if
the standard telephone version is not installed.
Please confirm to stop the telephone (y/n, default y):
Result
Parameter y
The system reboots:
Result
INIT: Sending processes the TERM signal Jan 12
Stopping alzled: /etc/rc.d/rc(1): Stopping alzled:
[ OK ]
Stopping role: /etc/rc.d/rc(1): Stopping role:
[ OK ]
Shutting down TEL services
Login / Pass swinst /SoftInst


Enter the name of the server ->
Result
Parameter 10.1.1.10 (for instance)
Remark Use the IP address of the PC from which you want to install the patch
y):
Parameter y
Result
Parameter /dhs3mgr/G13007 (for instance)

Result confirm the full path d:/dhs3mgr/G13007 (y/n, default y):
Parameter y
The path of the delivery is d:/dhs3mgr/G13007
Result
NOTES: if the answer is YES ,a binaries backup will be done in case of
trouble.
Parameter n ( backup is not mandatory for the lab )

101

Result '/DHS3dyn/tmp' ...
In order to run the linux packages
In order to run the emulation layer
YOU HAVE TO REBOOT THE SYSTEM
End of operation!
Press return
Parameter Press RETURN

Remark In the swinst menu, go back to easy menu
Action 1 – Easy menu
Action 8 - Start the telephone
Remark Some patches require a complete reboot. This is the case when a new
version of Linux is installed for example. When the installation (via swinst)
is complete, a system message is displayed requesting the user to reboot
the machine.
2.2. Check the version installed on the hard disk

Login mtcl
Command siteid
Customer's name : ALCATEL ;
Result
Customer's address: Kergaradec ;
Customer's town : Brest ;
Customer's country: FRANCE ;
Customer's install number: ;
CPU type : CPU80
Linux version : 52.0
Delivery software version: G1.300;
Patch version : 7 ;
MAO software version : G1.300;
Software Version Name : R8.0 ;
System Country : US ( 5);
Node number : 1 ;
Network number : 1 ;
Alarm relay state: ACTIVE

102
3. Dynamic telephone patches
These patches are new telephone application files containing corrections or upgrades.
They can be installed on the active or inactive partition with the phone running without
disturbing phone operation.
After a dynamic patch has been installed, it is immediately installed in CPU memory. The
customer then has the corrected version available without having to reboot the machine.
This installation is performed using the memloader tool. For each process patched in
memory, a 2176 incident indicating the operation is emitted.
Dynamic patches are installed after static patch installation. They cannot run if the
standard telephone version and corresponding static patch are not installed.
Dynamic patch name always ends with one or two letters. The first dynamic patch for a
version ends with the letter "a", the next with the letter "b" and so on till the end of the
alphabet. If further patches are necessary after the letter "z", they are named "aa", “ab”,
etc.
3.1. Install a dynamic patch

Login / Pass Swinst / SoftInst
Enter the name of the server ->
Result
Parameter 10.1.1.10 (for instance)
Remark Use the IP address of the PC from which you want to install the patch
y):
Parameter y
Result
Parameter /dhs3mgr/G13007b (for instance)

Result confirm the full path d:/dhs3mgr/G13007b (y/n, default y):
Parameter y

103
The path of the delivery is d:/dhs3mgr/G13007b

Result
Parameter n
Check linux version
Result
'/DHS3dyn/tmp' ...
3.2. Check the loading of the dynamic patch

Command incvisu | grep 2176
02/03/04 11:56:40 001001I|--/--/-/---|=2:2176=Patch dynamique installe
Result pour TEL

104
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to perform a software upgrade with a static or dynamic patch with multi-
version
MANAGEMENT
1. Check by swinst the active and inactive versions installed on the hard disk
2. Make a complete copy from the active to the inactive part of the hard disk
3. Load the patch specified by the trainer on the inactive partition of the hard disk in order
to have the same one than the Traing CS

105

106
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
107
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
108
GD/GA/GD3/INTIP3 Software loading
OBJECTIVE
To learn how to reload binaries on GD, GA, GD3, INTIP3
Alcatel-Lucent OmniPCX Enterprise – GD/GA Software loading

109
GD/GA/GD3/INTIP3 software loading
Overview
In normal functioning, GD, GA, GD3 or INTIP3 download their binaries from the
CPU automatically when an upgrade of the software version is done on that
CPU, but sometime it doesn’t work due to a too old version of binaries installed
on the board for instance.
To resolve the problem, it’s possible to download directly the binaries to the
boards from PC installer.
This operation is done in two steps
Erasing and formatting the GD, GA, GD3 or INTIP3 flash memory
Downloading of the new binaries
Alcatel-Lucent OmniPCX Enterprise – GD/GA Software loading

110
TECHNICAL COMMUNICATION No. TC0521 Ed. 04
OmniPCX Enterprise Nb of pages : 10 Date : 18 March 2010
URGENT
NOT URGENT TEMPORARY PERMANENT
SUBJECT: REFORMATTING AND RELOADING THE GD/GD3/INTIP3 NAND FLASH WITH PC

INSTALLER
CONTENTS
1. AIM .............................................................................................3
2. ERASING AND RELOADING OF A GD OR GA BOARD ..................4

2.1. Erasing and formatting the NAND Flash................................................... 4
2.2. Downloading the GD binaries .................................................................. 7
3. ERASING AND RELOADING OF GD3 OR INITIP3 BOARD .............8
1
111
2
112
OmniPCX Enterprise
REFORMATTING AND RELOADING THE
GD/GD3/INTIP3 NAND FLASH WITH PC
INSTALLER
1. AIM
The purpose of this technical communication is to provide a procedure which allows to reformat and
to reload the binaries for R5.1 and higher in case of corruption of the NAND Flash on a GD/GA
board or GD3/GA3/INTIP3 board.
Notes
GD3/GA3/INTIP3 are available from OmniPCX Enterprise PC Installer v2.26.
The deliveries are retrieved from the patches installed in the directory dhs3mgr from the PC host.
It is requires that at least one static patch is available in this directory so that all type of binaries
GD, GD3 and INTIP3 are available for the download.
The initialization of a NAND Flash of a GD/GA board with OmniPCX Enterprise PC Installer is
performed in two steps:
1 Erasing and formatting the NAND Flash.
2 Downloading GD binaries.
For the new generation boards, GD3/GA3/INTIP3, the reloading of the NAND flash still requires
those two steps, the erasing and reload, however the erasing step has been introduced directly in the
BIOS.
Ed. 04 / 18 March 2010 3 TC0521

113
OmniPCX Enterprise
INSTALLER
2. ERASING AND RELOADING OF A GD OR GA BOARD
2.1. Erasing and formatting the NAND Flash

1 Connect directly the GD/GA board and the PC Server with an Ethernet crossed cable.
2 Start OmniPCX Enterprise PC Installer.

x Select GD/GA/… binary in the field Installation type.
x Select option GD/GA in the field Type of Media Gateway board in the Installation
parameters window.
x Click on Apply in Installation Parameters window.
TC0521 4 Ed. 04 / 18 March 2010

114
OmniPCX Enterprise
INSTALLER
The GD binaries (depending on the version) must be present under

/dhs3mgr/"version"/pcmao/boot_res/DHS3bin/downbin/emg directory.
Ed. 04 / 18 March 2010 5 TC0521

115
OmniPCX Enterprise
INSTALLER
3 Start GD/GA board in LOLA mode.

x Set the dip switches 1, 2 and 4 to ON, the dip switch 3 to OFF position.
x Start the GD/GA board in Controller Position (Position 0 of the Rack).
x In this mode, the transfer of files can be monitored in Client parameters window of
OmniPCX Enterprise PC Installer.
4 The different phases of erasing and reformatting can be viewed by LED CPU of the board
GD/GA:
Phase of bios 2 x ON/OFF (250ms)/ 1 OFF ( 2 s)

Phase of Linux.ram loading 4 x ON/OFF(250ms)/ 1 OFF ( 2 s)
Phase of erasing and formatting of the NAND FLASH Fixed ON
Phase of end of formatting of the NAND FLASH Fast flashing (50 ms/ 50 ms)
5 The end of formatting of the FLASH is viewed on the V24 configuration port with the following
message:
Welcome to PeeWeeLinux
(none) login:
6 Stop GD/GA board with On/Off switch and wait the red power LED changes to fix status.
7 Stop OmniPCX Enterprise PC Installer application on PC Server.
TC0521 6 Ed. 04 / 18 March 2010

116
OmniPCX Enterprise
INSTALLER
2.2. Downloading the GD binaries

1 Startup of the OmniPCX Enterprise PC Installer.
x Select GD/GA/… binary in the field Installation type.
x Click on Apply in Installation Parameters window; see step 2 of §2.
x Configuration of GD/GA board in GD mode, set the dip switch 2 to ON, the dip switches 1,
3 and 4 to OFF position.
2 Restart the GD/GA board for the reloading of the binaries in Controller Position (Position 0 of
the Rack).
In this mode, there is monitoring on V24 configuration port (9600 8-N-1) and the transfer of the
different e-MGD binaries can be monitored in Client parameters window of OmniPCX
Enterprise PC Installer.
3 At the end of GD binaries download an e-mgd admin user login is displayed on V24
configuration port. Then it is possible to enter into mgconfig menu to set the IP configuration.
4 Stop GD/GA board with On/Off switch and waiting the red power LED changes to fix status.
5 Stop OmniPCX Enterprise PC Installer application on PC Server.
6 In case of a GA board, change the dip switches 1 and 2 to ON, dip switches 3 and 4 to OFF
position.
Ed. 04 / 18 March 2010 7 TC0521

117
OmniPCX Enterprise
INSTALLER
3. ERASING AND RELOADING OF GD3 OR INITIP3 BOARD

The LOLA mode doesn’t exist anymore on the new generation boards, thus it is not anymore
necessary to modify the DIP switch to realize the erasing of the NAND Flash.
The installation process of the binaries starts by the erasing of the Nand Flash memory by the BIOS.
1 Insert the board GD3, GA3 or INTIP3 into the CPU position of the rack (0 for GD3/GA3, 6,10 or
20 for the INTIP3).
2 Connect the GD3, GA3 or INTIP3 board and the PC Server with a crossed Ethernet cable.
3 Start OmniPCX Enterprise PC Installer V2.26 or higher.
x Select the installation type GD/GA/rGD/GD3/INTIP3 binary in the field Installation
type.
x Select GD3 or INTIP3 in the field Media Gateway board designation in the window
Installation parameters.
x Click on Apply in the window Installation parameters.
TC0521 8 Ed. 04 / 18 March 2010

118
OmniPCX Enterprise
INSTALLER
The GD3 binaries (depending on the version) must be present in the directory
/dhs3mgr/"version"/pcmao/boot_res/DHS3bin/downbin/mg3.
The INTIP3 binaries (depending on the version) must be present in the directory
/dhs3mgr/"version"/pcmao/boot_res/DHS3bin/downbin/intip3.
4 Connect a terminal on the V24 port of the GD3, GA3 or INTIP3.
5 Switch on the power on the board GD3, GA3 or INTIP3 then interrupt very quickly the startup to
enter the BIOS menu.
The access to BIOS menu is temporarily delicate. Basically during the first 2 seconds following
the power on, you need to type the commands CTRL + B and CTRL+I (maintain the key
CTRL pressed then type characters B then I quickly in loop).
U-Boot 1.3.0-rc3 (Apr 15 2009 - 16:37:27) 3EH30350AAAI bootl100/000.008
Reset Status: Software Hard, External/Internal Soft, External/Internal Hard
CPU: e300c4, MPC8377, Rev: 21 at 399.999 MHz, CSB: 266 MHz
I2C: ready
DRAM:
DDR DIMM: data bus width is 64 bit without ECC
DDRC ECC mode: OFF
DDR RAM: 256 MB
FLASH: 2 MB <---------------- Press quickly CTRL+B CTRL+I at this step
PCI: Bus Dev VenId DevId Class Int
00 17 1064 2102 0000 00
In: serial
Out: serial
Err: serial
Net: TSEC0, TSEC1
Ed. 04 / 18 March 2010 9 TC0521

119
OmniPCX Enterprise
INSTALLER
6 In the BIOS menu select 3 : Load from Ethernet

Let the installation process complete, without answering the questions. The erasing NAND Flash
memory is automatic, however there is no automatic reboot of the board at the end of the
binaries installation.
7 When the installation is completed connect with login root then type reboot command.
8 At the end of next startup, the menu mgconfig is automatically proposed to configure the
Ethernet parameters.
Welcome to the GD configuration tool
---------------------------------------
FW version
mg3_02.68_21Jan10_10h19
---------------------------------------
Board role GD
MAC address 00809F8D004E
1. IP address 192.168.10.10
2. Netmask 255.255.255.224
3. Gateway address 192.168.10.254
4. CS role address 192.168.10.3
5. CS redundancy role address 0.0.0.0
6. Crystal number (Dynamic allocation- Refer mgr)
7. IP QoS menu VLAN disabled
8. BACKUP menu (Not Available)
9. Duplex and speed mode menu auto
10. Download binaries timeout 1200[ms]
11. Passive CS address 0.0.0.0
12. Security and Encryption PROTECT SoftMSM PSKg2
13. Telnet server open
14. Archive log files
15. Allow shell commands usage not allowed
0. Exit
TC0521 10 Ed. 04 / 18 March 2010

120
GDx Board loading
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to download new binaries on GDx boards
MANAGEMENT
1. Following the technical support procedure “ TC0521” reload a GD3 or GD board according
to the available hardware.
2. Check that the board is running correctly after the loading.

121
GDx Board loading

122
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
123
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
124
CS duplication
OBJECTIVE
To describe the CS duplication principle
Alcatel-Lucent OmniPCX Enterprise – CS duplication

125
CS duplication
Introduction
Principle: duplication of the CS software platform
Main call server
Standby call server
Purpose: provide continuous service in the unlikely event of one of the call
servers failing
A CPU standby supports CPU failure and maintenance on the CS is easier .

126
CS duplication
Introduction
Services: if the Main call server fails, the system switches on the standby one
(which becomes Main):
Calls already established are maintained
Calls being connected during switch-over are lost
Both server databases are duplicated and coherently maintained

Management modifications
Accounting tickets
Solution: IP link between both CS

127
CS duplication
Introduction
Main CS in service
As soon as the main CS is operational and reachable, it controls the Media
Gateways and the IP terminals.
CS Standby
CS Main
IP Signaling
Network
IP-MG
It is recommended for reasons of eventual power supply unit failure, to insert the CPUs into independent chassis.
Except in case of crystal CPU because it is impossible.

128
CS duplication
Introduction
Loss of Main CS
If Main CS falls down or is unreachable, Media gateways and IP terminals are
managed by the Standby CS (which becomes the "Main").
X
CS Main
Réseau
CS Standby ⇒ Main CS
Signaling
IP
IP-MG

129
CS duplication
Introduction
Implementation using:
An IP Link which performs the signaling between both Call servers. It

handles:
The "keep alive" messages exchange between the two CS
The duplication data exchange
A reference Media Gateway

This one is used when the call servers can not exchange the "keep-alive" messages (
IP network problem )
Keep alive: This message allows to maintain "active" the link between both call servers.

130
CS duplication
Switch over mechanism
Call server initialization:
In the Mao is declared:

The "Call Server Role":
Primary
Secondary
The Reference Media Gateway
Each call server tries to establish a connection with the other one to
determine its role(CONNECT message)
If it succeeds, a negotiation occurs to decide the exact role of each one

according to the MAO parameter
Defense: If the "Call server role" is not correctly defined, the CS with the
highest IP address starts in Main role

131
CS duplication
Switch over:
Once roles have been determined:

there is a "Keep Alive" messages exchange between Main and Standby
If the Main CS falls down or has an IP link process problem:

The Standby CS becomes Main and sends a message toward all IP devices
All IP devices reconnect to the new Main CS
The established communications are maintained
If the IP network is down between both CS

There are two main Call Server (Double Main Mode) on the network
a Real Main Call Server
a Pseudo Main Call Server
The "Reference Media Gateway" is used in this case to determine the Real Main on
which will be activated the MAO (management)
A running mode with two Real Main Call Server can be managed
The reference e-MG shall be as close as possible from one CS (same switch).

132
CS duplication
Double Main Mode
Real Main Pseudo Main
Reference Node 1
IP-MG
Node 1 '
IP-MG
IP-MG
The standby call server doesn't receive any "keep alive" messages so it switches over and reconnects to all IP devices it has access
to.
In this scenario, the node is divided into two parts which runs independently.

133
CS duplication
Call server link "wake up":
After a call server shutdown
It restarts as in initialization mode (restarts as Stand-by if there is already a Main

CS)
After an IP network problem
The Pseudo Main Call Server reboots and switches in Stand-by mode
If the two CS are in “Real Main” then the CS on which the reference MG is connected stays
in “Real Main” mode and the other CS restarts
IP devices which were connected to the CS that is reseted reboot and reconnect to
the Real Main
The established communications are released
A database duplication has to be launched to synchronize the call servers

134
CS duplication
Topology
Recommended:
Both call servers on the same LAN switch

Call servers on two different LAN switches with inter-switch Link backup
Not recommended:
Both CS in the same Media Gateway
All installation must be switched off for maintenance
CS A
CS B

135
CS duplication
Media Gateway signaling link backup
It is possible to have a signaling link backup through the public network

between the CS and a Media Gateway
A media gateway cannot be connected with two CS at the same time
Only the first direct connection is accepted
The backup connection will be rejected
In Double Main mode:

The backup signaling is only available with the "Real Main" CS

136
CS duplication
Duplication and ABC-F Network
The two sides of the network are not synchronized
Real Main Pseudo Main

(MAO ON) (MAO OFF)
Node 1
CS CS
Node 1 '
Node 2 Modification Node 3

files No database
No modification
exchange update
files exchange
When the IP network problem is solved:

A copy of the Main CS database has to be made on the Standby
The modification files are exchanged automatically to resynchronize the network
The modification files which are not broadcast are kept on the nodes until the IP network comes up and then exchanged by the
nodes to resynchronize the ABC-F network without data lost.

137
CS duplication
Restrictions
Both CS must be on the same platform type
It is now possible to place the call servers in different IP sub-networks.This

feature is called “Spatial Redundancy”.
Services not provided in Double Main mode:
Accounting (tickets generated on the Pseudo Main can not be reported on

the other call server)
Traffic observation (same thing)
One part of the network has no Voice Mail

138
Duplication System without Spatial redundancy (CPU CSA)
OBJECTIVE
To describe the configuration of the CPU A in case of duplicated configuration without spatial redundancy
Alcatel-Lucent OmniPCX Enterprise – Duplication System without Spatial redundancy (CPU CSA)
Ref. ENTP0438C02TEUS Issue 03
139
Full IP configuration of CS
Management of CPU A
Full IP configuration
netadmin
Warning: for a specific setup please use menu mode (netadmin -m)
Do you want to erase the existing setup? y
X25 private network number? 1
Unique site number? 1
Warning: the node name must be unique.

Enter node name? node001001
Do you want to activate internal name resolver (y/n default is 'n')? n
Enter local CPU position (a or b) for duplicated configuration

or n for single CPU (default is 'n')? a
Node name: by default it is “node” + network N° + node N°

this parameter is used only in case of configuration with spatial redundancy
Internal name resolver: allows to start the DNS service on the CS.
Answer yes only in case of configuration with spatial redundancy
140
Management of CPU A (cont.)
Ethernet interface setup

============
CPU name? xa001001
CPU address? 10.1.1.1
Name used when the CPU role is MAIN? xma001001
Address used when the CPU role is MAIN? 10.1.1.3
CPU redundancy setup

============
Twin CPU name? xb001001
Twin CPU's address? 10.1.1.2
Network mask? 255.255.0.0

The setup has been correctly achieved.
Security
====
Do you want to enhance security (y/n, default is y)? n
Both CPU use the same name for main role function because they are within the same LAN and use the same main IP address.
141
Management of CPU A (cont.)
3.Local Ethernet interface

3.2. 'Update'
CPU name (default is xa001001)?
CPU address (default is 10.1.1.1)?
Network mask (default is 255.255.255.192)? 255.255.0.0
8.Routing setup
8.1 Default router setup
8.1.2 Add/Update
Default router name? router
The name you gave isn't in our hosts database. Do you want to add it
and so give the corresponding address? y
Default router address? 10.1.1.100
Until the release F2.500 you don’t see the question for managing Network mask so the default one is applied.
You have to manage it at the end of the full configuration.
Same for router management. You have to declare it after the full IP configuration.
142
System duplication without spatial redundancy (CPU CS B)
OBJECTIVE
To describe the configuration of the CPU B in case of duplicated configuration without spatial redundancy
Alcatel-Lucent OmniPCX Enterprise – System duplication without spatial redundancy (CPU CS B)

143
Management of CPU B
Full IP configuration
netadmin
Do you want to erase the existing setup? y
X25 private network number? 1
Unique site number? 1

Enter node name? node001001
Do you want to activate internal name resolver (y/n default is 'n')? n

or n for single CPU (default is 'n')? b
Node name: by default it is “node” + network N° + node N°

this parameter is used only in case of configuration with spatial redundancy
Internal name resolver: allows to start the DNS service on the CS.
Answer yes only in case of configuration with spatial redundancy

144
Management of CPU B (cont.)

============
CPU name? xb001001
CPU address? 10.1.1.2

============
Twin CPU name? xa001001
Twin CPU's address? 10.1.1.1
Network mask? 255.255.0.0

Security
====
Do you want to enhance security (y/n, default is y)? n
Both CPU use the same name for main role function because they are within the same LAN and use the same main IP address.

145
Management of CPU B (cont.)

3.2. 'Update'
CPU name (default is xb001001)?
CPU address (default is 10.1.1.2)?
Network mask (default is 255.255.255.192)? 255.255.0.0
8.Routing setup
8.1 Default router setup
8.1.2 Add/Update
Default router name? router
and so give the corresponding address? y
Default router address? 10.1.1.100
Until the release F2.500 you don’t see the question for managing Network mask so the default one is applied.
You have to manage it at the end of the full configuration.
Same for router management. You have to declare it after the full IP configuration.

146
Setup duplicated Call Server
PROCEDURE
OBJECTIVE
- To learn how to setup Call Server duplication
DOCUMENTATION
- System Documentation: System Documentation/Technical documentation/system /call

server/call server duplication
OVERVIEW
The "Call Server Duplication" service is used to improve the PCX's operational safety. Two Call
Servers coexist in the same PCX. One of them is active, it is said to fulfill the "Main" role. The
other is on hold, it is said to fulfill the "Stand-by" role. When the first one has failed, the second
one replaces it. The calls in progress are maintained, the calls currently being set up are
interrupted.

147
PROCEDURE
1. Check Software lock with spadmin command
On the call server

Login mtcl
Command spadmin
ooo Reading string-file /DHS3bin/oneshot/mtcl/objects.US0 ...
Result
ooo Reading string-file /DHS3bin/oneshot/mtcl/spadmin.dct ...
Display current counters ........................... 1
Display active file ................................ 2
Check active file coherency ........................ 3
Install a new file ................................. 4
Read the system CPUID .............................. 5
CPU-Ids management ................................. 6
Display active and new file ........................ 7
Display OPS limits ................................. 8
Display ACK code ................................... 9
Exit ............................................... 0
choice :
Choice 2
File version = 0
Result
OXE version = 0110
Soft Key = 423b496e72a18eef3567
Cpu Id 0 = 0000BAD5
Cpu Id 1 = 0000BB18
177-SIP users = 9999 (0)
178-4645 Voice mail engin = 1
179-4645 users = 400 (0)
181-OmniPCX Enterprise (1 = 1
182-4645 networking = 1
183-4645 additionnal lang = 5
184-Integrated gatekeeper = 9999
185-SIP Gateway = 9999
186-E-CS redundancy = 1

148
2. Set up IP configuration on CSa
On the call server

Login mtcl
Command netadmin
Warning: for a specific setup please use menu mode (netadmin -m).
Result
Do you want to erase the existing setup (y/n default is 'n') ?
Enter y
Do you intend to use IP/X25 on your system (y/n default is 'n')?
Result
Enter n
Result
Enter node name (default is node001001) ?
Enter Tapez entrer

Result Do you want to activate internal name resolver (y/n default is 'n') ?
Enter n
Result
or n for single CPU (default is 'n')?
Enter a
Result
========================
CPU name ?
Enter xa001001
CPU address ?
Result
Enter 10.1.1.1
Network mask ?
Result
Enter 255.255.255.0
Name used when the CPU role is MAIN ?
Result
Enter xma001001
Result The name you gave isn't in our hosts database. Do you want to add it and so
give the corresponding address (y/n default is 'n') ?
Enter y
Result Address used when the CPU role is MAIN ?
Enter 10.1.1.3
Result
====================
Twin CPU name ?
Enter xb001001

149
Twin CPU's address ?

Result
Enter 10.1.1.2
Network mask ?
Result
Enter 255.255.255.0
Result
Enter xma001001
Result Address used when the CPU role is MAIN ?
Enter 10.1.1.3
Default router setup
Result
====================
Do you use an external gateway as default router (y/n default is n) ?
Enter y
Default router name ?
Result
Enter Routeur
Result Default router address ?
Enter 10.1.1.254
Result Please wait, working ...

Remark:
A shutdown of the CS is mandatory after the netadmin management

150
3. Set up IP configuration on CSb
On the call server

Login mtcl
Command netadmin
Warning: for a specific setup please use menu mode (netadmin -m).
Result
Do you want to erase the existing setup (y/n default is 'n') ?
Enter y
Do you intend to use IP/X25 on your system (y/n default is 'n') ?
Result
Enter n
Result
Enter node name (default is node001001) ?
Enter Tapez entrer

Do you want to activate internal name resolver (y/n default is 'n') ?
Result
Enter n
Result
or n for single CPU (default is 'n') ?
Enter b
Result
========================
CPU name ?
Enter xb001001
CPU address ?
Result
Enter 10.1.1.2
Network mask ?
Result
Enter 255.255.255.0
Result
Enter xma001001
Result and so
give the corresponding address (y/n default is 'n') ?
Enter Y
Address used when the CPU role is MAIN ?
Result
Enter 10.1.1.3
Result
====================
Twin CPU name ?
Enter xa001001

151
Twin CPU's address ?

Result
Enter 10.1.1.1
Network mask ?
Result
Enter 255.255.255.0
Result
Enter xma001001
Address used when the CPU role is MAIN ?
Result
Enter 10.1.1.3
Result
====================
Do you use an external gateway as default router (y/n default is n) ?
Enter y
Default router name ?
Result
Enter Routeur
Result Default router address ?
Enter 10.1.1.254
Result Please wait, working ...

Remark:
A shutdown of the CS is mandatory after the netadmin management

152
4. Reference IP-MG declaration
On mgr
Select Shelf
Entry Shelf address: (for example: 1) (take the GD nearest the CS)
Reference: true
Action Press CTRL+v two times to validate the creation
Press CTRL+c as many time as needed to come back on main menu
Remark:
When the two call servers are not "seeing" each other, they both try to
connect to the reference e-MG, the one which succeeds becomes the Real
Main and the other one becomes the Pseudo Main (MAO not activated).
The reference e-MG shall be as close as possible from one e-CS (same
switch).
If no reference Media Gateway has been declared, the Call Server with the
highest IP address becomes the "Real Main".
5. Call server role declaration on mao
On mgr
Select IP
Entry Preferred CS @IP (redundancy): (for example: 10.1.1.1)
Remark:
Preferred CS @IP
Used In case of simultaneous start-up of both e-CS, the one whose IP
address is defined here will start as main.

153
6. “Real main” mode selection
On mgr
Select IP/Duplication parameters
Entry Pseudo main : false
Remark:
True : Running « real main » + « pseudo main »
False : Running « real main » + « real main »
Both CS are considered as « real main » without restrictions

154
Database cloning
PROCEDURE
OBJECTIVE
- To learn how to perform a database cloning
DOCUMENTATION
- System Documentation: System Documentation-> Functional documentation-> system

services->call server duplication->management
OVERVIEW
The "Call Server Duplication" service is used to improve the PCX's operational safety. Two Call
Servers coexist in the same PCX. One of them is active, it is said to fulfill the "Main" role. The
other is on hold, it is said to fulfill the "Stand-by" role. When the first one has failed, the second
one replaces it. The calls in progress are maintained, the calls currently being set up are
interrupted.

155
Database cloning
PROCEDURE
1. Maintenance
1.1. Check IP configuration on call server A
On the call server

Login mtcl
Command netadmin –m
Select 2. 'Show current configuration'
Result Ethernet interface setup
========================
Netmask : 255.255.255.0
===============================================================
| Machine type | Local interface | Name | Address
|
===============================================================
| local | Ethernet | xa001001 | 10.1.1.1
| local main | Ethernet | xma001001 | 10.1.1.3
| router | Ethernet | routeur | 10.1.1.254
===============================================================
====================
Netmask : 255.255.255.0
===============================================================
===============================================================
| local | Ethernet | xb001001 | 10.1.1.2
===============================================================
Action Press ENTER
Press 0 to exit from netadmin menu

156
Database cloning
1.2. Check IP configuration on call server B
On the call server

Login mtcl
Command netadmin –m
Select 2. 'Show current configuration'
Result Ethernet interface setup
========================
Netmask : 255.255.255.0
===============================================================
===============================================================
| local | Ethernet | xb001001 | 10.1.1.2
| router | Ethernet | routeur | 10.1.1.254
===============================================================
====================
Netmask : 255.255.255.0
===============================================================
===============================================================
| local | Ethernet | xa001001 | 10.1.1.1
===============================================================
Action Press ENTER
Press 0 to leave netadmin menu

157
Database cloning
1.3. Validate autostart on call server B (standby)
On the call server

Login mtcl
Command swinst
Select 2 Expert menu
6 system management
2 autostart management
1 set autostart
Action Press ENTER
Press Q as many times as needed to leave swinst menu
1.4. Stop the telephone application on call server B (standby)
On the call server

Login mtcl
Command swinst
Select 1 Easy menu
7 stop the telephone
Entry Please confirm to stop the telephone: y

158
Database cloning
1.5. Copy the main call server database on to the standby one(call server B)
On the call server

Remark:
you must be logged on the call server where you want to copy the database.
In this case call server B which is the stand by call server
Login mtcl
Command swinst
Select 2 Expert menu
3 cloning & duplicate operations
1 CPU cloning
3 cloning database
BACKUP DATA from 10.1.1.3 on LOCAL CPU mastercopy utility 1.0
Entry
Ethernet link is used for copy
Do you wish to copy the DATABASE AND ACCOUNTING (y/n): y
Do you wish to copy the VOICE GUIDES (y/n): n
Do you wish to copy the TRAFFIC HISTORY (y/n): n
Do you wish to copy the ACD CONFIGURATION AND STATISTIC FILES (y/n): n
Do you wish to copy the LINUX DATA (y/n, default n): n
Do you wish to START THE TELEPHONIC APPLICATION
at the end of the operation (y/n, default y): y
AT THE END OF THE OPERATION, THE TELEPHONIC
APPLICATION WILL BE STARTED AUTOMATICALLY
Continue the mastercopy (y/n)? y
Remark:
Be patient!

159
Database cloning
1.6. Check the good working of the duplication
On the call server

Remark:
You log on call server A
Login mtcl
Command Role -b
MAIN stand-by CPU state: ACTIVE
Result
Remark:
Call server A is main and call server B is active in Stand by mode
Check the switching between call server A and call server B
Before using the next command, you can realize some calls in order to
check the transparency
Command twin
Result Role and CPU positions:
Role of the CPU : MAIN
CPU position : 6
CPU address : 10.1.1.1
Twin CPU position : 10
Twin CPU address : 10.1.1.2
Redundancy State:
Duplicated configuration : YES
Wished sig. transfer mode : C1 signalling channel
Used sig. transfer mode : C1 signalling channel
Transmission CPU-CPU : READY
Telephony redundancy : READY
monitel redundancy : READY
memloader redundancy : READY
All applications redundancy : READY
Remark:
All services must have the status « Ready » for considering the CSb in
stand-by.
Do not try to switch before to obtain these status

160
Database cloning
Command bascul
This command will cause a fast CPU switch-over.
Entry
The CPU is running in Main Role. If you perform a CPU switch-over,
this CPU will be shutdown.
Are you sure you want to perform a CPU switch-over (y/n)? y
Remark:
Call server A is in shutdown mode, call server B is main.
After call server reset, try the following command
Command Role -b
ACTIVE stand-by CPU state: MAIN
Result
Remark:
Call server B is main and call server A is active in Stand by mode

161
162
Duplication
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to put into operation the call server duplication
MANAGEMENT
1. Manage the reference Media gateway
2. With the help of the duplication procedure, put into service the second CS in the same IP
sub-network than the first CS (VLAN 15x)
3. Perform a database cloning and start the telephone application on the second CS.
4. Through the maintenance commands, verify the state and role of each call server.
5. Establish several calls and perform a call server switch over, what happens?
6. Create a new analog set and check that it exists on the database of the 2ème CS
7. Disconnect the main CS from the IP network and use the different maintenance commands
to see the role of each CS and the devices connected to those CS
8. Create a new analog set when the 2nd CS is disconnected from the network
9. Reconnect the CS , which one is rebooting?
10. Does the previously created analog set exist in the database of the 2ème CS after the
restart?
What must be done if that one is not present in the database ?

163
Duplication

164
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
165
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
166
Duplication with Spatial redundancy
OBJECTIVE
To describe the spatial redundancy new features
Alcatel-Lucent OmniPCX Enterprise – Duplication with Spatial redundancy

167
Introduction
The duplication with spatial redundancy uses the same principle than the
classical duplication
With the spatial redundancy the CS are located within different IP subnet
Each CS can use it’s own router and a different sub-netmask

168
Topology with spatial redundancy
DNS server
brest=@IP Main CSB
DNS server
brest=@IP Main CSA
Standby CS
Main CS
IP Signaling IP
Network Network
MG MG
The 2 CS are in different subnet and each CS has it’s own main role IP address
The DNS service is active on the main CS and answers with it’s own main IP@

169
Alcatel-Lucent equipment
In case of spatial redundancy there is one IP address for:

The main role of CSA
The main role of CSB
The physical addressing of each CS
For the following Alcatel-Lucent IP equipment it is possible to specify the two

main role IP addresses as TFTP server
IP Touch Series
GD, GA and INTIP
For IP hybrid ABC links there are 2 fields for each main role IP address
In the 4760 application it is possible to specify the 2 CS main role IP addresses
The Alcatel IP equipment try to reach both main role IP addresses and only the active one answers.

170
External applications
Internal DNS of the CS
In case of external applications like SIP, H323, it is necessary to use a new

object called « node name »
This object is used with a DNS server that is running on both CS
The DNS server answers to a “node name” request with it’s on main IP
address
Only the active main CS answers to the DNS requests
The internal DNS server is mandatory for external application

In the IP configuration of the PC you have to specify :
the main role address of one of the CS as a primary DNS server
the second CS main role address as a secondary DNS server.
In case of DNS request the PC tries first with the primary DNS server and if it
doesn’t answer it tries with the secondary DNS server.

171
External applications
External DNS
If there is already a DNS server in the customer LAN it is necessary to explain to

the LAN manager that the DNS requests concerning the node name must be
rerouted towards the DNS servers of the two CS.
You must provide in this case the 2 CS main IP addresses needed by the
customer LAN manager for the DNS forwarding management
In this situation the primary and secondary DNS servers are the client servers because they will forward the DNS request toward
our CS internal DNS servers.

172
Restrictions
The CS can be a CPU CS or an Appliance server

Not compatible with OmniPCX 4400 CPU
IP touch sets are available in a spatial redundancy configuration
In case of IP hybrid links all nodes must be in release 6.1

The possibility to specify the two main IP@ was implemented only from this
release
No WLAN

173
Restrictions
Internal DHCP server is running with spatial redundancy

Only the active CS answers to the DHCP requests and fills in the tftp server
field with its own main role IP address
In case of external DHCP server, this one must be able to send two tftp
addresses
No change in case of “double main” mode

174
Spatial redundancy
OBJECTIVE
To describe the configuration in case of duplicated configuration with spatial redundancy
Alcatel-Lucent OmniPCX Enterprise – Spatial redundancy

175
Global topology with spatial redundancy
DNS server
OmniPCX Enterprise
brest=11.1.1.3
CS Main
11.1.1.3 11.1.1.1
11.1.1.11 11.1.1.41
OmniPCX Enterprise
CS Stand By
151.1.1.3
151.1.1.1
151.1.1.11
172.25.1.50 172.25.1.11

176
Full IP configuration of the CS
Management of CSa
netadmin
Do you want to erase the existing setup (y/n default is 'n') ? y
Do you intend to use IP/X25 on your system (y/n default is 'n') ? n

Enter node name (default is node000000) ? brest
Do you want to activate internal name resolver (y/n default is 'n') ? y

or n for single CPU (default is 'n') ? a

========================
CPU name ? xa001001
The name you gave isn't in our hosts database. Do you want to add it and so
give the corresponding address (y/n default is 'n') ? y
CPU address ? 11.1.1.1
Network mask ? 255.255.255.0
Name used when the CPU role is MAIN ? xma001001
Address used when the CPU role is MAIN ? 11.1.1.3
Warning : the management of the node name must be identical on both CS !
Node name : You cannot write here “brest.alcatel.fr” for example because the DNS service keeps only the first string and will
compare the node name “brest.alcatel.fr” with the part that it will keep : “brest”.

177
Management of CSa (cont.)

====================
Twin CPU name ? xb001001
Twin CPU's address ? 151.1.1.1
Network mask ? 255.255.0.0
Name used when the CPU role is MAIN ? xmb001001
Local router setup

==================
Default router name ? routeurA
Default router address ? 11.1.1.254
Twin router setup

=================
Default router name ? routeurB

The twin CPU network mask can be different

178
Management of CSb
netadmin
Do you want to erase the existing setup (y/n default is 'n') ? y
Do you intend to use IP/X25 on your system (y/n default is 'n') ? n

Enter node name (default is node000000) ? brest
Do you want to activate internal name resolver (y/n default is 'n') ? y

or n for single CPU (default is 'n') ? b

========================
CPU name ? xb001001
CPU address ? 151.1.1.1
Network mask ? 255.255.0.0
Name used when the CPU role is MAIN ? xmb001001

179
Management of CSb (cont.)

====================
Twin CPU name ? xa001001
Twin CPU's address ? 11.1.1.1
Network mask ? 255.255.255.0
Name used when the CPU role is MAIN ? xma001001
Local router setup

==================
Default router name ? routeurB
Twin router setup

=================
Default router name ? routeurA


180
Modification of IP configuration
New Node name for the DNS
netadmin -m
15. 'Node configuration‘
15.2. 'Update‘

Enter node name (default is node1.alcatel.fr)? Brest2010
Do you want to activate internal name resolver (y/n default is 'n')? y

181
Management of DHCP server
There is nothing special about the management of the DHCP server in case of
spatial redundancy
The management is done according to the Main CPU IP addressing on which you
are connected
The main CS sends these data to the Stand-by CS that adapts them according
to it’s local addressing
DHCP Configuration
CPU Main Subnetwork
Subnet address : 11.1.1.0
Subnet mask : 255.255.255.0
Broadcast address : 11.1.1.255
Default router address :
TFTP Server address :
Each CS has its own main role IP address in the TFTP server field in the
dhcpd.conf file

182
Management of DHCP server
(Next)
cat /etc/dhcpd.conf (on CSa)

# Subnet 11.1.1.0/24.
subnet 11.1.1.0 netmask 255.255.255.0 {
option broadcast-address 11.1.1.255;
next-server 11.1.1.3;
range 11.1.1.60 11.1.1.65;
}
# Subnet 151.1.0.0/16.
subnet 151.1.0.0 netmask 255.255.0.0 {
range 151.1.1.60 151.1.1.65;
}
cat /etc/dhcpd.conf (on CSb)

# Subnet 11.1.1.0/24.
subnet 11.1.1.0 netmask 255.255.255.0 {
range 11.1.1.60 11.1.1.65;
}
# Subnet 151.1.0.0/16.
subnet 151.1.0.0 netmask 255.255.0.0 {
range 151.1.1.60 151.1.1.65;
}

183
Management of boards
Example for GD board
eMGD login: admin
Password: admin
[admin@eMGD admin]$ su
[root@eMGD admin]# mgconfig
Welcome to the e-MGD IP configuration tool

------------------------------------------
MAC address 00809F35163D

1. Startup mode Static
2. IP address 172.25.1.11
3. Netmask 255.255.255.0
4. Gateway address 172.25.1.100
5. CS role address 11.1.1.3
6. CS redundancy role address 151.1.1.3
7. Crystal number 2 (Manual allocation)

184
Management of IP Touch
Local equipment
Press the keys "i" + "#“ for static IP configuration

ip parameters
ip mode: static
ip address: 11.1.1.41
Subnet: 255.255.255.0
Router: 11.1.1.254
Tftp1: 11.1.1.3
Tftp2: 151.1.1.3
In case of dynamic configuration that is the CS main that will answer to the DHCP request from the IP Touch set and it will send
it’s own main IP@

185
Management of SIP
You need to manage the DNS in the TCP/IP configuration
If there is no DNS server in the customer LAN:

Put the first main role address in the primary DNS server field and the second
main role address in the secondary DNS server field
If there is a DNS server in the customer LAN:

Give to the LAN administrator both addresses for the node name resolution
brest -> 11.1.1.3 et 151.1.1.3
The PC will use its DNS which will forward the request to our DNS servers

186
Management of SIP
(cont.)
SIP application settings
You cannot use the IP address of the CS because in case of switching the
client will be locked.
Instead of the IP address you have to put the node name for the proxy IP
address:
brest

187
Management of H323
Case with external gatekeeper
If the CS is not used as a gatekeeper there is no problem with H323 client
They will reach directly or through an external gatekeeper the GD or the INTIP
A board

188
Management of H323
Case with a CS used as gatekeeper
You need to manage the DNS in the TCP/IP configuration

If there is no DNS server in the customer LAN:
Put the first main role address in the primary DNS server field and the second main
role address in the secondary DNS server field
If there is a DNS server in the customer LAN:
Give to the LAN administrator both DNS addresses for the node name resolution
brest -> 11.1.1.3 and 151.1.1.3
The PC will use its DNS which will forward the request to our DNS servers
In the H323 settings, you cannot use an IP address because in case of

switchover the second CS will be unreachable
Instead to use the main role IP address for the gatekeeper parameter you
will use the node name:
brest

189
Management of H323
Case with a CS used as gatekeeper (cont.)
There is nothing special about internal gatekeeper management
IP
Gatekeeper Parameters
Gatekeeper ID :0
Gatekeeper Name :
Gatekeeper IP Address : 11.1.1.3
Alternative GK IP address :
IP Parameters
System Option + Internal Gatekeeper number
Internal Gatekeeper number :0
Gatekeeper IP Address: you must specify one of the two main IP@

190
Management of IP hybrid links
Inter-Node Links
Hybrid Link Access
Link Name : N2N1

Access number :1
Physical address main access : 19-0-2
Signaling type + IP
Called Number or Main CPUa IP addr : 11.1.1.3
Main CPUb IP address : 151.1.1.3

191

192
Duplication with Spatial redundancy
OBJECTIVE
To describe the maintenance in case of duplicated configuration with spatial redundancy

Ref. ENTP0492M01TEUS Issue 04
193
Global topology with spatial redundancy
DNS server
OmniPCX Enterprise
brest=11.1.1.3
CS Main
11.1.1.3 11.1.1.1
11.1.1.11 11.1.1.41
OmniPCX Enterprise
CS Stand By
151.1.1.3
151.1.1.1
151.1.1.11
172.25.1.50 172.25.1.11

194
Checking of CSa
netadmin
3.1. 'View‘

========================
Internet name : xa001001
Internet address: 11.1.1.1
Netmask : 255.255.255.0
4.Twin CPU setup

4.1. 'View‘
Netmask : 255.255.0.0
============================================================================
| Machine type | Local interface | Name | Address |
============================================================================
| twin | Ethernet | xb001001 | 151.1.1.1 |
| local main | Ethernet | xmb001001 | 151.1.1.3 |
| router | Ethernet | routerB | 151.1.1.254 |
============================================================================

195
Checking of CSa (cont.)
5.Role addressing setup

5.1 'View‘
==============================================================================
==============================================================================
| local main | Ethernet | xma001001 | 11.1.1.3 |
| twin main | Ethernet | xmb001001 | 151.1.1.3 |
==============================================================================
8.Routing setup
8.1. 'Default router setup'

====================
Default router name : routerA
Default router address: 11.1.1.254
Twin router setup

=================
Default router name : routerB

196
Checking of CSa (cont.)
9.1.Host database update

9.1. 'View‘
11.1.1.1 xa001001 localhost

11.1.1.3 xma001001 maincpu localmain
11.1.1.254 routerA defaultrouter
151.1.1.1 xb001001 twincpu_eth twincpu_best
151.1.1.3 xmb001001 twinmain
151.1.1.254 routerb
127.0.0.1 loopback
255.255.255.0 subnetmask
15.Node Setup
15.1. 'Show Node Setup'
Node configuration
==================
node name : brest
internal name resolver activated : yes

197
Checking of CSb
netadmin
3.1. 'View‘

========================
Internet name : xb001001
Internet address: 151.1.1.1
Netmask : 255.255.0.0
4.Twin CPU setup

4.1. 'View'
Netmask : 255.255.255.0
============================================================================
============================================================================
| twin | Ethernet | xa001001 | 11.1.1.1 |
| local main | Ethernet | xma001001 | 11.1.1.3 |
| router | Ethernet | routerA | 11.1.1.254 |
============================================================================

198
Checking of CSb (cont.)
5.Role addressing setup

5.1 'View‘
==============================================================================
==============================================================================
| local main | Ethernet | xmb001001 | 151.1.1.3 |
| twin main | Ethernet | xma001001 | 11.1.1.3 |
==============================================================================
8.Routing setup
8.1. 'Default router setup'

====================
Default router name : routerB
Twin router setup

=================
Default router name : routerA

199
Checking of CSb (cont.)
9.1.Host database update

9.1. 'View‘
151.1.1.1 xb001001 localhost

151.1.1.3 xmb001001 maincpu localmain
151.1.1.254 routerB defaultrouter
11.1.1.1 xa001001 twincpu_eth twincpu_best
11.1.1.3 xma001001 twinmain
11.1.1.254 routerA
127.0.0.1 loopback
255.255.0.0 subnetmask
15.Node Setup
15.1. 'Show Node Setup'
Node configuration
==================
node name : brest
internal name resolver activated : yes

200
Boot of IP boards
Example with an INTIPB board
00000011-00000855: ConfigIP : using static IP Parameters

00000012-00000855: ConfigIP : IP Address : 155.132.1.11
00000013-00000855: ConfigIP : IP Subnet Mask : 255.255.0.0
00000014-00000855: ConfigIP : IP Default Router : 155.132.1.100
00000015-00000856: ConfigIP : Query Default Router 155.132.1.100 using ICMP ECHO REQUEST ...
00000016-000009E9: ConfigIP : Default Router alive :)
00000017-000009E9: LANPBX : Try to download the file 'lanpbx.cfg' from server 11.1.1.3
00000018-000009E9: LANPBX : Try to download the file 'lanpbx.cfg' from server 151.1.1.3
00000019-00000A40: LANPBX : DOWNLOAD lanpbx.cfg OK from TFTP server 151.1.1.3
0000001A-00000A40: LANPBX : SEARCH OF THE GOOD CPU FROM LANPBX.CFG
0000001B-00000A40: LANPBX : contents of the line 1 of lanpbx.cfg :
0000001C-00000A40: IP_DOWNLOAD= 11.1.1.3
0000001D-00000A40: IP_DOWNLOAD_RD= 151.1.1.3
00000020-00000A40: BININTIP : Download of the binary [Current size limit : 1024KBytes]
00000021-00000A40: SEARCH FOR CPU : Try to start with cpu 11.1.1.3 (tftp client number 0 try to download file 'binintip')
00000022-00000A40: BININTIP : Download of the binary [Current size limit : 1024KBytes]
00000023-00000A40: SEARCH FOR CPU : Try to start with cpu 151.1.1.3 (tftp client number 1 try to download file 'binintip').
00000024-00000A42: SEARCH FOR CPU : cpu 151.1.1.3 accept INTIP board
00000027-00000A42: BININTIP : Binary is up to date -> stop the download of the binary
Only the main CS answers to the request.

201
DNS UDP port and process
The DNS server listens to the standard UDP port 53 and this service is called
“domain”
You can check if the CS is listening to this port

netstat -an |grep :53
udp 0 0 0.0.0.0:53 0.0.0.0:*
netstat -lu |grep :domain
udp 0 0 *:domain *:*
The process for DNS server is “nameresd”

ps -edf |grep name
root 14669 1 0 09:26 ? 00:00:00 /usr/sbin/nameresd
The process nameresd is always loaded in the memory of the 2 CS if the DNS service has been validated in netadmin.
Only the main CS answers to the DNS requests.

202
DNS requests
No. Source Destination Protocol Info

1 155.132.1.10 11.1.1.3 DNS Standard query A brest.alcatel.fr
2 155.132.1.10 151.1.1.3 DNS Standard query A brest.alcatel.fr
3 155.132.1.3 151.1.1.10 DNS Standard query response A 151.1.1.3
The client sends a DNS request toward the 2 CS

Declared as primary and secondary servers in the PC
Only the CS with the main role answers to the DNS requests with it’s own IP
address
The managed node name is “brest” in the call server DNS but the application
can send a FQDN (“brest.alcatel.fr”) because the DNS of the CS keeps only
the first part of the chain from the DNS request, « brest »

203
204
Spatial redundancy
HANDS-ON EXERCISES
OBJECTIVE
- To learn how to perform configure and test the spatial redundancy
MANAGEMENT
1. With the help of the duplication procedure, put into service the second CS in a different
VLAN than the first CS one (VLAN 1x)
2. Perform a database cloning and start the telephone application on the second CS.
3. Through the maintenance commands, verify the state and role of each call server.
4. Establish several calls and perform a call server switch over, what happens?
5. Disconnect the LanX of the VLAN 15x in order to simulate a default between the VLAN
5.1. Verify that the equipment located in the VLAN 15x are connected on the 1st CS
5.2. Verify that the equipment located in the VLAN 1x and 17x are connected on the 2nd
CS
6. Try to establish calls
7. Connect back the LanX on the LAN
7.1. When the status « main » & « stand-by » are again available, check that all
equipment are connected back to the “main” CS

205
Spatial redundancy

206
Upgrade of a duplicated system
HANDS-ON EXERCISES
OBJECTIVE
- To implement a software upgrade on a site with a duplicated CS topology
MANAGEMENT
1. Installation of the system voice guides
1.1. Install the system voice guides FR & US and the MOH on the two CS
1.2. Check that the voice guides and the MOH are working
1.3. Perform a CS switching and check again after the switching that the voices guides
and the MOH are working
2. Record a dynamic voice guide
2.1. Check that this voice guide is working well
2.2. Perform a CS switching and check that the voice guide is working fine
3. Migration of the site in release 9

The customer has requested the migration of his site in release 10.
You must install the new release on the CS.
3.1. Perform a database, OPS and Linux data backup on the CS
3.2. Keep a copy of these backup on the PC hard disk
3.3. Install the R10 on the second partition of the stand-by CS (the other CS stays main for
the telephone services)
3.3.1. Install the Linux package
3.3.2. Install the binaries
3.3.3. Copy the database and the Linux data

207
Upgrade of a duplicated system
3.3.4. Reboot this CS on the second partition without the telephone

3.3.5. Install the new OPS files
3.3.6. Start the telephone
3.3.6.1. Stop the main CS when the Linux is starting on the updated CS
3.3.7. Check that all devices are working fine
3.4. Install the R10 on the second partition of the CS which is stopped
3.4.1. Install the Linux package
3.4.2. Install the binaries
3.4.3. Reboot this CS on the second partition without the telephone
3.4.4. Update this CS data according to the main CS data
3.4.5. Start the telephone on this CS when the update is done
3.4.6. Check that this CS is started in standby mode
3.5. Perform a switch over

3.5.1. Check that all devices are running
3.6. Perform a database, OPS and Linux data backup on the CS
3.7. Update the copy of these backup on the PC hard disk

208
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
209
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________________
_____________________________________________________________________________
_____________________________________________________________________________
210

ENTPCTE103EN Beta2 Letter

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ENTPCTE103EN Beta2 Letter

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent OmniPCX Enterprise

Enterprise Education and Partner Programs

 Value Added Options

2 | ALCATEL-LUCENT OMNIPCX ENTERPRISE ± POST-SALES TRAINING OFFER | MAY 2011

VALUE ADDED OPTIONS

To complement the basic portfolio by value added solutions or applications:

To answer to customer standard customization:

For a quick start of the solution:

4 | ALCATEL-LUCENT OMNIPCX ENTERPRISE ± POST-SALES TRAINING OFFER | MAY 2011

VALUE ADDED OPTIONS

Associated Options ± details page 9

ACSE Corporate level ± details page 8

ACSE Business level ± details page 7

ACFE level ± details page6

Starter Pack I=8h

Technology Overview Technology Overview Technology Overview

CPU loading C=2d

Starter Pack I=8h VoIP Technologies I=8h

On Site Mobility I=6h

OmniMessage 4635 C=8d

OmniMobility DECT C=2d Free Desktop

Starter Pack I=8h

Hotel / Healthcare C=3d

Starter Pack I=8h

OmniMobility Expert C=2d

Starter Pack I=8h On Site Mobility

Starter Pack I=8h

I=6h On Site Mobility

Security Access I=4h

I=6h On Site Mobility

Security Access I=4h

Tap Lab OmniPCX C=2d

Tap Lab OmniPCX C=2d

Phone: +33 (0)2 98 28 53 19

18 | ALCATEL-LUCENT OMNIPCX ENTERPRISE ± POST-SALES TRAINING OFFER | MAY 2011

REFERENCE ENTPCTE103EN DELIVERY LANGUAGE English (course material English)

Virtual self-paced training on the computer*

2 days Traditional classroom or practical sessions with tutorials (TAP LAB)

Tutored virtual training sessions accessible via an internet connection*

MAXIMUM NUMBER OF PARTICIPANTS 12

Ƚ Software loading principle Ƚ Call server duplication

Ƚ Mono version loading Ƚ Call server spatial redundancy

Ƚ Multi version loading Ƚ Disk structure

Ƚ Software updates Ƚ Main Linux commands

* Required technical configuration for i-learning and v-learning

Issue Date Issue Date

Alcatel-Lucent OmniPCX Enterprise CPU Loading 01 07/11

File reference: ENTPCTE103EN

CORE CURRICULUM AND CATALOG PROGRAM DESCRIPTION

1. Software loading - Mono version

2. Software loading - Multi versions

4. Loading of GDx & INTIP3 boards

REF. ENTPCTE103EN Issue 01 All Rights Reserved © 2011, Alcatel-Lucent i

ii All Rights Reserved © 2011, Alcatel-Lucent REF. ENTPCTE103EN Issue 01

CHAPTER PAGE DESCRIPTION

Please return this sheet to:

REF. ENTPCTE103EN Issue 01 All Rights Reserved © 2011, Alcatel-Lucent iii

iv All Rights Reserved © 2011, Alcatel-Lucent REF. ENTPCTE103EN Issue 01

CS software loading – Mono version mode

All Rights Reserved © 2007, Alcatel-Lucent 1

To describe the OmniPCX Enterprise loading tool PC Installer

To describe the software loading principles

To describe the different loading cases

Value Added Options

2 | ALCATEL-LUCENT OMNIPCX ENTERPRISE ± POST-SALES TRAINING OFFER | MAY 2011

4 | ALCATEL-LUCENT OMNIPCX ENTERPRISE ± POST-SALES TRAINING OFFER | MAY 2011

Technology Overview Technology Overview Technology Overview

CPU loading C=2d

On Site Mobility I=6h

OmniMessage 4635 C=8d

OmniMobility DECT C=2d Free Desktop

Hotel / Healthcare C=3d

Starter Pack I=8h On Site Mobility

I=6h On Site Mobility

Security Access I=4h

I=6h On Site Mobility

Security Access I=4h

Tap Lab OmniPCX C=2d

Tap Lab OmniPCX C=2d

18 | ALCATEL-LUCENT OMNIPCX ENTERPRISE ± POST-SALES TRAINING OFFER | MAY 2011

Manual start up on CPU 7

Manual starting up on all CPUs