TC2338en-Ed06 OmniPCX Enterprise Release R12.0-remote installation of PCS

Technical Bulletin
OmniPCX Enterprise
TC2338 ed.06
Release 12.0 and above
R12 Remote installation of PCS
It is mandatory to format hard disk before installation of R12. You can follow this procedure to avoid on site mission.
This document provides the configuration details required to install R12.X with remote connection.
Revision History
Edition 1: November 21, 2017
creation of the document
Edition 2: November 27, 2017
troubleshooting updated
Edition 3: April 12, 2018
patch updated
Edition 4: April 16, 2018
description updated
Edition 5: April 24, 2018
edition updated
Edition 6: August 29, 2018
new script installr12.bsx to be used
Legal notice:
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE. To view other trademarks used by
affiliated companies of ALE Holding, visit: www.al-enterprise.com/en/legal/trademarks-copyright. All other trademarks are the
property of their respective owners. The information presented is subject to change without notice. Neither ALE Holding nor any
of its affiliates assumes any responsibility for inaccuracies contained herein. © 2018 ALE International. All rights reserved.
www.al-enterprise.com
Table of contents
1
Preparation and important point ....................................................................................... 3
2
Installation procedure .................................................................................................... 4
2.1
2.1.1
PC preparation .................................................................................................. 4
2.1.2
Transfer of installation scripts to the MAIN CPU .......................................................... 7
2.1.3
Transfer script from MAIN CPU to all PCS .................................................................. 8
2.1.4
Installation script execution .................................................................................. 9
2.1.5
Error detection before installation ......................................................................... 11
2.2
3
Installation method for patch lower than M1.403.22 or M2.300.21 ......................................... 4
Installation method for patch upper and equal to M1.403.22 or M2.300.21 or M3.402.13.f ........... 11
2.2.1
PC preparation ................................................................................................. 11
2.2.2
Transfer of installation scripts to the MAIN CPU ......................................................... 14
2.2.3
Transfer script from MAIN CPU to all PCS ................................................................. 16
2.2.4
Installation script execution ................................................................................. 17
2.2.5
Error detection before installation ......................................................................... 20
Installation monitoring ................................................................................................... 20
3.1
Visible only if V24 console is available. ......................................................................... 20
3.2
Monitoring with PC installer ....................................................................................... 23
4
Troubleshooting after installation ..................................................................................... 25
5
Data restoration ........................................................................................................... 30
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 2/31
1 Preparation and important point







Warning
Feature available since M140318b, M140319 for R12.0 and M230018d, M230019 for R12.1 and M340213f for
R12.2
Upgrade can be done from all OXE releases compliant with R12.X (follow TC1854 for compatibilities).
FTP / telnet (port 21 and 23) between the PC-Installer and PCS must not be blocked by any firewall.
All PCS must be upgraded before the Main/Stand-by are upgraded.
PC-Installer version 5.4 and above should be used. Version 5.4 of PC installer can be found at least in M340213f
iso file under folder: /m340213f/pcmao/boot_res/pcinstall/setup.exe.
One PC installer instance can install only one CPU and ONLY one instance can run on PC. So, to install several
CPU in parallel you have to execute PC install on several PCs.
Database restoration considerations:

Highly recommended to save Linux and MAO DB outside the node prior to any upgrade attempt.

Restoration of “Linux Database” of PCS have to follow a specific procedure given at the end of this
document.
Don’t restore CS Main Linux Data into PCS, PCS Linux Data have to be restored into PCS






Telephony, Accounting or 4645 database restorations can follow normal restoration procedures, but it’s
highly recommended to have them saved prior any upgrade attempt.
Installation is mostly automatic and in case of errors, a V24 console is needed to check the issue.
Upon successful installation, the PCS will have the same IP that it had before installation:

PCS IP address, netmask, gateway, hostnames, Trusted Hosts and SSH keys will be restored to allow IP
connectivity to the board.

Other settings like password, RADIUS, FTR, NTP, … will not be restored.
Installing/Restoring the actual Linux DB of PCS to be done manually after the installation is finished.
In case Trusted Hosts (Isolated Ethernet) are in use, it is advised to add PC-Installer address as a trusted CPU,
via NETADMIN menu 11.
The script can run in following type of CPU’ s

CS-2

VMware (Only IDE disk supported)

Appliance Server

KVM
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 3/31
2 Installation procedure
2.1
Installation method for patch lower than M1.403.22 or M2.300.21
2.1.1
PC preparation
Transfer the patch and release you want to install as usual to the PC-Installer PC under dhs3mgr folder.
Screenshot below shows the case, where we want to install M1.403.18.a. Check presence of script in dynamic patch first
if not present check in static patch then in delivery.
For our example, folder “dhs3mgr” must contain M1403, M140318 and m140318a :
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 4/31
The folder containing the script will show the following files:
/dhs3mgr/m140318a/pcmao/boot_res/bootp/linux/server_upd/109.000/install/config/

install_r12.sh

vmlinuz-2.6.32-rd.dhs3

initrd_dhs3.img

pcs_instr12_transfer.sh
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 5/31
PC-installer configuration
Warning
At the end of installation, you may get “Standard installation failure message” with version lower than 5.4. So take
latest PC-installer 5.4 at least coming with M3.402.13.f
On PC-Installer:

Select the Installation type to “Linux + Call handling”.

Select the type of CPU (“CS-2” in example)

Select the patch to be installed.

Other fields don’t matter. (During this procedure DHCP part is not use and PCS will keep his IP address)
Once selected, check and ensure the below highlighted files are created in the path
c:/Program Files/Alcatel-Lucent/OmniPCX Enterprise PC Installer/bootp/linux
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 6/31
As example for M1.403.18.a :
Linux delivery should be the same as latest Linux found from folder in delivery or static patch or dynamic patch
/pcmao/boot_res/bootp/linux/server_upd
2.1.2
Transfer of installation scripts to the MAIN CPU
Transfer the following 2 files
/dhs3mgr/m140318a/pcmao/boot_res/bootp/linux/server_upd/109.000/install/config/in
stall_r12.sh
/dhs3mgr/m140318a/pcmao/boot_res/bootp/linux/server_upd/109.000/install/config/pc
s_instr12_transfer.sh
from PC to the MAIN CS, under /tmpd/
Warning
If FTP is used to transfer this script, ensure that “binary” mode is selected, to avoid file corruption.
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 7/31
Once script is transferred to MAIN CS check and ensure the script has execution permission.
(946)node46vma> cd /tmpd
(946)node46vma> chmod 755 /tmpd/install_r12.sh
(946)node46vma> ls -l install_r12.sh
-rwxr-xr-x. 1 mtcl tel 19472 Nov
7 08:30 install_r12.sh
(946)node46vma> chmod 755 /tmpd/pcs_instr12_transfer.sh
(946)node46vma> ls -l pcs_instr12_transfer.sh
-rwxr-xr-x. 1 mtcl tel 2173 Nov
2.1.3
7 08:30 pcs_instr12_transfer.sh
Transfer script from MAIN CPU to all PCS
Login as mtcl in the MAIN CS and launch the pcs_instr12_transfer.sh from MAIN CS node.
The “install_r12.sh” script will be transferred to all the configured PCS if they are reachable.
(946)node46vma> /tmpd/pcs_instr12_transfer.sh
Transferring the script to 172.19.109.24
Transfer of /tmpd/install_r12.sh to 172.19.109.24:/tmpd/ completed SUCESSFULLY
Transferring the script to 172.19.31.245
Transfer of /tmpd/install_r12.sh to 172.19.31.245:/tmpd/ completed SUCESSFULLY
Script will be automatically transferred to all PCS in INACTIVE state. In case of unreachable PCS or script not present on
PCS, this script “pcs_instr12_transfer.sh” has to be relaunched from MAIN CPU.
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 8/31
2.1.4
Installation script execution
Login as root on PCS and launch the script install_r12.sh from PCS node that must be upgraded. Provide the
appropriate inputs. An example below with m1403.18.a and fr country (inputs highlighted).
Warning
Do not launch this install_r12.sh script from the MAIN CS, as you will end up installing the MAIN CS
Be sure to manage same delivery between PC installer and script
example for m140318a and FR country :
[root@cs2_24 root]# cd /tmpd
[root@cs2_24 tmpd]# ./install_r12.sh
Enter IP address of the Server : 135.250.161.171
Checking connections
*** 135.250.161.171 is reachable OK ***
Is Server Windows PC (PC-Installer)(Y/N q to quit) : y
Load version ?(Y/N q to quit) : y
Enter the name of the Linux version (eg: 109.000) : 109.000
Enter the name of version (eg: m1403) : m1403
Load of patch ?(Y/N q to quit) : y
Enter the name of patch (eg: m140315) : m140318
Load of dynamic patch ?(Y/N q to quit) : y
Enter the name of dynamic patch (eg: m140315a) : m140318a
Enter the countries
To choose default country (ae), press
return.
To display the possible choice, enter
?
To end a selection, enter a null line (just enter).
To quit, enter
q
=> fr
You have chosen fr
country
Confirm the install of m1403 and m140318 and m140318a(Y/N q to quit) : y
Once the version is confirmed, the script checks for file existence and the files are transferred from PC-Installer to PCS.
When all checks succeed a confirmation to reboot is asked.
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 9/31
Confirm the install of m1403 and m140318 and m140318a(Y/N q to quit) : y
Checking menu.lst
connection ok
/bootp/linux/109.000/install/config//vmlinuz-2.6.32-rd-dhs3 exists
connection ok
/bootp/linux/109.000/install/config//initrd_dhs3.img exists
connection ok
/bootp/linux/109.000/install/config//initrd_dhs3.img exists
connection ok
/bootp/linux/109.000/install/config//initrd_dhs3.img exists
New Vmlinux && Initrd OK ..
connection ok
/bootp/linux/109.000/install exists
/tmpd/BCK_26582/List_to_BCK
/etc/at.allow
/etc/at.deny
/etc/hostname
[…]
/tmp/hosts.sav
/tmp/netdata.sav
/usr/netadm/data/keys/oxe/id_rsa
/usr/netadm/data/keys/oxe/id_rsa.pub
/usr/netadm/data/netdata
/var/spool/cron/root
31 blocks
All checks OK
About to launch reboot
Upon reboot installation starts automatically
Possible to monitor the progress through PC-Installer
Do not interrupt
!! Warning !!
any failure will require V24 connection or a site visit
Are you sure to reboot and install of m140318a(Y/N q to quit) :
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 10/31
2.1.5
Error detection before installation
Some basic checks for file availability and FTP connections are done by the script.
The script will exit if any error is detected (example below)
Confirm the install of m1403 and m140318 and m140318a(Y/N q to quit) : y
Checking menu.lst
/bootp/linux/109.000/install/config//vmlinuz-2.6.32-rd-dhs3 does not exist
Possible problem FTP server not supporting Anonymous FTP
The delivery path entered does not exist
Check file /tmpd/ftp.log on PCS in case of issue
2.2
Installation method for patch upper and equal to M1.403.22 or
M2.300.21 or M3.402.13.f
2.2.1
PC preparation
Transfer the patch and release you want to install as usual to the PC-Installer PC under dhs3mgr folder.
Screenshot below shows the case, where we want to install M3.402.13.f. Check presence of script in dynamic patch first
if not present check in static patch then in delivery.
For our example, folder “dhs3mgr” must contain M3402, M340213 and M340213f :
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 11/31
The folder containing the script will show the following files:
\dhs3mgr\m340213\pcmao\boot_res\bootp\linux\server_upd\123.000\install\config

install_r12.bsx
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 12/31
PC-installer configuration
Warning
At the end of installation, you may get “Standard installation failure message” with version lower than 5.4. So take
latest PC-installer 5.4 at least coming with M3.402.13.f
On PC-Installer:

Select the Installation type to “Linux + Call handling”.

Select the type of CPU (“CS-2” in example)

Select the patch to be installed.

Other fields don’t matter. (During this procedure DHCP part is not use and PCS will keep his IP address)
Once selected, check and ensure the below highlighted files are created in the path
c:/Program Files/Alcatel-Lucent/OmniPCX Enterprise PC Installer/bootp/linux
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 13/31
As example for M3.402.13.f :
Linux delivery should be the same as latest Linux found from folder in delivery or static patch or dynamic patch
/pcmao/boot_res/bootp/linux/server_upd
2.2.2
2.2.3
Transfer of installation scripts to the MAIN CPU
The file to be transferred to the main CS is now named “installr12.bsx”.
You must always use the file provided in the release you want to install on the PCS.
You must check first if one is provided in the dynamic patch. If yes use that one otherwise check in the static patch.
Example for M3.402.13.f :
the file is provided in the static patch M3.402.13 not in the dynamic patch M3.403.13.F
Warning
Don't use a script from another release like M1 for example for installing a M3 because the
Linux RAM size can be changed.
then you will be stuck with the remote PCS locked in the GRUB and you will have to load it.
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 14/31
The file “installr12.bsx” can be found in the following path:
M340213\pcmao\boot_res\bootp\linux\server_upd\123.000\install\config:
Transfer the following file
/dhs3mgr/m140318a/pcmao/boot_res/bootp/linux/server_upd/109.000/install/config/in
stall_r12.bsx
from PC to the MAIN CS, under /tmpd/
Warning
If FTP is used to transfer this script, ensure that “binary” mode is selected, to avoid file corruption.
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 15/31
Once script is transferred to MAIN CS check and ensure the script has execution permission.
(946)node46vma> cd /tmpd
(946)node46vma> chmod 755 /tmpd/install_r12.bsx
(946)node46vma> ls -l install_r12.bsx
-rwxr-xr-x. 1 mtcl tel 388590 Aug
8 08:57 install_r12.bsx
2.2.4
2.2.5
Transfer script from MAIN CPU to all PCS
Login as root in the MAIN CS and launch the install_r12.bsx from MAIN CS node.
[root@node46vma mtcl]#/tmpd/./installr12.bsx
Self Extracting Installer
Running Installer
Extraction completed of file completed, you can launch ./install_r12.sh or
pcs_instr12_trasfer.sh present in /tmpd
(946)node46vma>
Transfer script to all running PCS executing pcs_instr12_transfer.sh
(946)node46vma> /tmpd/pcs_instr12_transfer.sh
Transferring the script to 172.19.109.24
Checking connectivity
*** 172.19.109.24 is reachable OK ***
Transfer of /tmpd/install_r12.bsx to 172.19.109.24:/tmpd/ completed SUCESSFULLY
Unpacking
Done
2.2.6
Script will be automatically transferred to all PCS in INACTIVE state. In case of unreachable PCS or script not present on
PCS, this script “pcs_instr12_transfer.sh” has to be relaunched from MAIN CPU.
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 16/31
2.2.7
Installation script execution
Login as root on PCS and launch the script install_r12.sh from PCS node that must be upgraded. Provide the
appropriate inputs. An example below with m3.402.13.f and fr country (inputs highlighted).
Do not launch this install_r12.sh script from the MAIN CS, as you will end up installing the MAIN CS
Warning
Be sure to manage same delivery between PC installer and script
example for m340213f and FR country:
[root@pcs tmpd]# ./install_r12.sh
*** Welcome to ALE remote installation tool ****
***
Version 2.0
***
Enter IP address of the Server : 192.168.0.17
Checking connections
*** 192.168.0.17 is reachable OK ***
Enter Server Type
- 1 PC-Installer
- 2 HTTPS
Your choice: 1
You have chosen to install with: PC-Installer
Enter Installation Method
- 1 FTP
Your choice: 1
You have chosen transfer method as :ftp
Load version ?(Y/N q to quit) : Y
after the complete patch to install (eg: m1403 or m140318 or m140318b ) :
m340213f
192.168.0.17:Connection OK
Found to install Linux version:123.000
Enter the countries
To choose default country (fr), press
return.
To display the possible choice, enter
?
To end a selection, enter a null line (just enter).
To quit, enter
q
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 17/31
=> fr
You have chosen fr
country
192.168.0.17 file:/dhs3mgr/m3402/ OK
192.168.0.17 file:/dhs3mgr/m340213/ OK
192.168.0.17 file:/dhs3mgr/m340213f/ OK
Confirm the install of m3402 and m340213 and m340213f(Y/N q to quit) : Y
Once the version is confirmed, the script checks for files existence and the files are transferred from PC-Installer to PCS.
When all checks succeed a confirmation to reboot is asked.
Checking menu.lst
192.168.0.17 file:/bootp/linux/123.000/install/config//vmlinuz-2.6.32-rd-dhs3 OK
192.168.0.17 file:/bootp/linux/123.000/install/config//vmlinuz-2.6.32-rd-dhs3 OK
Transfer vmlinuz-2.6.32-rd-dhs3 SUCCESS
Transfer initrd_dhs3.img SUCCESS
New Vmlinux && Initrd OK ..
192.168.0.17 file:/bootp/linux/123.000/install OK
/tmpd/BCK_10347/List_to_BCK
/etc/TunParams.mao
/etc/at.allow
/etc/at.deny
/etc/hostname
/etc/hosts
/etc/hosts.allow
/etc/hosts.deny
/etc/hosts.equiv
/etc/login.defs
/etc/ntp.conf
/etc/ntp/keys
/etc/pam.d/ftp
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 18/31
/etc/pam.d/login
/etc/pam.d/system-auth
/etc/pam.d/system-auth.NORADIUS
/etc/pam.d/system-auth.RADIUS
/etc/pam.d/system-auth.RADIUS_NOLOC
/etc/passwd
/etc/raddb/export
/etc/raddb/localuser
/etc/raddb/server
/etc/shadow
/etc/shut_delay
/etc/ssh/sshd_config
/etc/sysconfig/clock
/tmp/hosts.sav
/tmp/netdata.sav
/tmpd/AUTOSTART
/usr/netadm/data/netdata
/var/spool/cron/mtcl
/var/spool/cron/root
33 blocks
All checks OK
About to launch reboot
Upon reboot installation starts automatically
Possible to monitor the progress through PC-Installer
Do not interrupt
!! Warning !!
any failure will require V24 connection or a site visit
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 19/31
Are you sure to reboot and install of m340213f(Y/N q to quit) : Y
2.2.8
Error detection before installation
Some basic checks for file availability and FTP connections are done by the script.
Check file /tmpd/ftp.log on PCS in case of issue
3 Installation monitoring
3.1
Visible only if V24 console is available.
Upon reboot a new Menu entry will be present and it will be highlighted by default. The highlighted entry will boot
automatically
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 20/31
RAMDISK boot up messages are seen below
Booting 'Boot RAMDISK[New]'
root (hd0,1)
kernel /boot/vmlinuz-2.6.32-rd-dhs3 root=/dev/ramdisk ks=ramdisk ramdisk_size=3
4000 panic=5 console=ttyS0,9600 serial bipa=0xcff000 clocksource_failover rd_NO
_PLYMOUTH
[Linux-bzImage, setup=0x3200, size=0x37e700]
initrd /boot/initrd_dhs3.img
[Linux-initrd @ 0x39fff000, 0x2000000 bytes]
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Linux version 2.6.32-rd-dhs3 [063.000] (msokkali@prodcskmg) (gcc version 4.4.6
20120305 (Red Hat 4.4.6-4) (GCC) ) #1 SMP Tue Sep 26 14:32:26 IST 2017
KERNEL supported cpus:
Intel GenuineIntel
AMD AuthenticAMD
NSC Geode by NSC
Cyrix CyrixInstead
Centaur CentaurHauls
Transmeta GenuineTMx86
Transmeta TransmetaCPU
UMC UMC UMC UMC
Disabled fast string operations
OXE : Alcatel Architecture Setup
OXE : Setup OXE-specific hooks.
BIOS-provided physical RAM map:
BIOS-e820: 0000000000000000 - 000000000009d000 (usable)
BIOS-e820: 000000000009d000 - 00000000000a0000 (reserved)
BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 21/31
During installation progress
Then PCS is installed, and pre-configured with minimal Linux DB (IP address, netmask and gateway, SSH).
Starting sysstat:
Starting
services: [
OK
]
/etc/rc.d/rc(1): Starting sysstat:
[
OK
]
Starting crond: /etc/rc3.d/S90crond(1): crond startup
[
OK
]
Starting pwr_mgt:
[
OK
]
Starting kheader:
[
OK
/etc/rc.d/rc(1): Starting pwr_mgt:
/etc/rc.d/rc(1): Starting kheader:
]
Starting monit: monit: No programs have been specified
/etc/rc3.d/S98monit(1): monit startup
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 22/31
[
OK
]
Starting alzled:
[
OK
/etc/rc.d/rc(1): Starting alzled:
]
Start ccagent
/etc/rc3.d/S99ccagent(1): ccagent startup
[
OK
]
Alcatel-Lucent OmniPCX Enterprise
cs2_24 login:
3.1.1
3.2
Monitoring with PC installer
Installation progress can also be monitored in the PC-Installer as below,
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 23/31
When installation is in progress “Do not close the PC-Installer”. It will stop the PCS installation in between and if the PCS
becomes inaccessible we will need a site visit.
Network between PC-Installer and PCS is expected to be stable. When there is instability or too much delay please do
not attempt to start the installation.
Once message “installation successfully completed” is shown by PC-Installer, wait for 2-3 minutes, while the PCS is
rebooting. (to get this popup you can click on continue in case of other popup coming before end of installation see
troubleshooting chapter).
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 24/31
Then, connect to PCS with normal default MTCL password, with Telnet or SSH depending of site configuration
tcscent03 [msokkali] 97: telnet 172.19.109.24
Trying 172.19.109.24...
Connected to 172.19.109.24.
Escape character is '^]'.
Welcome to cs2_24
Alcatel-Lucent OmniPCX Enterprise
login: mtcl
Password:
Alcatel-Lucent OmniPCX Enterprise
standard installation last performed: 07-Nov-2017 05:13:12
(E)cs2_24>
4 Troubleshooting after installation
Warning
In case of installation failled V24 console on PCS will be needded and CPU restarted with new installation from
scratch + PC-installer on same subnet as PCS
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 25/31
Some logs can be found under /install-log folder of the CPU

When there are many devices in the PC-Installer network sending DHCP request, you may get the below pop up.
The installation will continue even when you do not press “Continue”. You may choose to press “Continue” to check the
progress.
Warning
If you “Quit” the installation will stop and we will need a hard reset of the board or a direct installation.

When there are multiple DHCP requests, sometimes PC-Installer give the below installation failed message. But
the installation might have completed or may be in progress.
Wait several minutes as PCS can continue installation by itself.
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 26/31
Before pressing the “Quit” please check the below PC-Installer log,
“c:/Program Files/Alcatel-Lucent/OmniPCX Enterprise PC Installer/var/log/syslog”
Nov 23 19:51:30 ftpd[9200]: LOG_INFO: ANONYMOUS FTP LOGIN FROM 172.19.109.24,
swinst@cs2_24
Nov 23 19:51:30 ftpd[9200]: LOG_INFO: get
/dhs3mgr/m140318a/dhs3linux/comm/cpiofile.gz
[..]
Nov 23 19:52:03 dhcpd[2520]: LOG_INFO: no free leases on subnet 192.168.223.0
Nov 23 19:52:04 ftpd[9068]: LOG_INFO: get
//bootp/linux/109.000/install/config/END_INSTALL
If the file is getting updated with “get /dhs3mgr/m1403xx/dhs3linux/…” , please wait till you see END_INSTALL and the
file stop updating.
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 27/31
After a while you can confirm installation on PCS by checking file on PCS as root /install-log/install.log.
End of file must have message “standard install success”
Alcatel-Lucent OmniPCX Enterprise
standard installation last performed: 07-Nov-2017 05:13:12
(E)cs2_24>su
Password:
[root@cs2_24 root]#cat /install-log/install.log
[…]
running kickstart post-install script (in ramdisk envt)
Netdata restored
standard install success
Marker file removed
mkinitrd 2.6.32-rd-dhs3
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 28/31

In case of issue you can follow the diagram below to restore your PCS
Latest part “bootp client” means that you have to install CPU locally with PCS installer started in same LAN than the CPU
in order to answer DHCP (BOOTP) request done by CPU.
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 29/31
5 Data restoration
Transfer saved Linux database to PCS, under /usr4/BACKUP/IMMED.
Warning
If FTP is used to transfer this script, ensure that “binary” mode is selected, to avoid file corruption.
[root@cs2_24 ~]# cd /usr4/BACKUP/IMMED/
[root@cs2_24 IMMED]# ls
cho-dat
Then, launch SWINST to perform an immediate restore operation, as usual (SWINST -> 2 Expert menu -> 4
Backup & restore operations -> 3 Restore operations -> 1 Restore from cpu disk) and restore “Linux
database”.
During PCS installation PCS will be in ACTIVE role from MAIN CS point of view so “PCScopy” will not be
possible in this state.
You can either:

restart main CPU (or bascule to standby) to refresh PCS link to UNDEF state then do “PCScopy” to restore
Telephony database to PCS (as usual).

Or restore PCS database taken at the beginning of the procedure.
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 30/31
Follow us on Facebook and Twitter
Connect with us on Facebook and Twitter for the latest:

Software releases

Technical communications

AAPP InterWorking reports

Newsletters
…and much more!
twitter.com/ALUE_Care
facebook.com/ALECustomerCare
Submitting a Service Request
Please connect to our eService Request application.
Before submitting a Service Request, please be sure:

The application has been certified via the AAPP if a third party application is involved.

You have read the release notes that list new features, system requirements, restrictions, and more,
and are available in the Technical Documentation Library.

You have read through the related troubleshooting guides and technical bulletins available in the
Technical Documentation Library.

You have read through the self-service information on commonly asked support questions and known
issues and workarounds available in the Technical Knowledge Center.
- END OF DOCUMENT -
OmniPCX Enterprise - Release 12.0 and above
R12 Remote installation of PCS
TC2338 ed.06
Copyright © ALE International 2018
page 31/31