Download as pdf or txt
Download as pdf or txt
You are on page 1of 18

TROUBLESHOOTING GUIDE No. TG0004 Ed.

02

OmniPCX Enterprise Nb of pages : 17 Date : 12-10-2004

SUBJECT : OmniPCX ENTERPRISE PC INSTALLER APPLICATION

The troubleshooting guide of "OmniPCX Enterprise PC Installer" application is used to identify the
installation environment and the operating troubles of the software.

1
OmniPCX Enterprise
TROUBLESHOOTING GUIDE No. 4 OmniPCX ENTERPRISE PC INSTALLER
APPLICATION

CONTENTS

1. PC INSTALLER APPLICATION........................................................3

2. HISTORY......................................................................................3

3. INTRODUCTION ..........................................................................3

4. CONFIGURING THE PC FOR SOFTWARE INSTALLATION..............3


4.1. Characteristics of the PC ........................................................................... 3
4.2. Before beginning the installation .............................................................. 3
4.3. During installation .................................................................................... 4

5. CONFIGURING THE PC FOR USING THE SOFTWARE ...................4


5.1. Configuring the "servers" services ............................................................. 4
5.2. Configuring the IP of PC ........................................................................... 4

6. CHECKING THE OPERATION OF "OMNIPCX ENTERPRISE PC


INSTALLER" APPLICATION............................................................5
6.1. Patch installation ...................................................................................... 5
6.2. Standard installation of a complete version .............................................. 6

7. CALL SERVER INSTALLATION TROUBLES ......................................7


7.1. Call server software standard installation troubles ................................... 7
7.1.1. Operating problems of the "OmniPCX Enterprise PC Installer" application .......7
7.1.2. During Bootp requests ......................................................................................9
7.2. Call server patch installation troubles..................................................... 12

8. UNINSTALLATION TROUBLES OF THE SOFTWARE .....................14


8.1. Deleting the "OmniPCX Enterprise PC Installer" directory ........................ 14
8.2. Deleting the environment variables ........................................................ 14

Ed. 02 / 12 October 2004 1 TG0004


OmniPCX Enterprise
OmniPCX ENTERPRISE PC INSTALLER TROUBLESHOOTING GUIDE No. 4
APPLICATION

8.3. Deleting the icon on desktop .................................................................. 15


8.4. Deleting the "OmniPCX Enterprise PC Installer" application in Start menu15
8.5. Deleting the intputs in registry ................................................................ 15

9. RECOVERING THE INFORMATION FOR ANALYSIS .....................16


9.1. Log files of "OmniPCX Enterprise PC Installer" application ...................... 16
9.2. Recovering the registry of Server PC ....................................................... 16
9.3. Recovering the IP configuration of Server PC .......................................... 16
9.4. Recovering the list of services of Server PC ............................................. 16

TG0004 2 Ed. 02 / 12 October 2004


OmniPCX Enterprise
TROUBLESHOOTING GUIDE No. 4 OmniPCX ENTERPRISE PC INSTALLER
APPLICATION

1. PC INSTALLER APPLICATION
In order to troubleshoot PC Installer application problems, reading of the "Call Server Installation" in
the technical documentation available on Alcatel Business Partner Web Site
(www.businesspartner.alcatel.com) and on CDROM with the reference 3BH 19918 FR and EN is
highly recommended.

2. HISTORY
Edition 01 : Creation of the Troubleshooting Guide.
Edition 02 : Upgrades with PC Installer v2.17.

3. INTRODUCTION
The troubleshooting guide of "OmniPCX Enterprise PC Installer" application is used to identify the
installation environment and the operating troubles of the software.

4. CONFIGURING THE PC FOR SOFTWARE INSTALLATION

4.1. Characteristics of the PC


− Windows 98 SE (up to PC Installer v2.17), Windows NT4 SP6 Workstation, Windows 2000 Pro,
Windows XP, Windows 2003 (as of PC Installer v2.18).
− 50 MB disk space.
− 64 MB RAM.
− IP network configuration.
• network board,
• TCP/IP protocol,
• IP static address.
CAUTION
If a Firewall is available on the server PC, the OmniPCX Enterprise PC Installer application cannot
operate as long as the filtering rules of firewall have not been changed to allow the application to
receive packets on 67/UDP (BOOTP/DHCP), 69/UDP, 20/TCP and 21/TCP (FTP) ports from any
system on the subnetwork of the PC.
If an other application of DHCP, TFTP or FTP server type is installed on the server PC, the associated
server(s) must not be started.

4.2. Before beginning the installation


The installation of the "OmniPCX Enterprise PC Installer" application is carried out with an
administrator's rights account.

Ed. 02 / 12 October 2004 3 TG0004


OmniPCX Enterprise
OmniPCX ENTERPRISE PC INSTALLER TROUBLESHOOTING GUIDE No. 4
APPLICATION

4.3. During installation


During the installation a warning window can appear:

Click on OK and validate the automatic start of "Computer Browser" windows service at the end of
software installation; refer to § 5.1.1.

5. CONFIGURING THE PC FOR USING THE SOFTWARE

5.1. Configuring the "servers" services


No FTP, TFTP and DHCP server service must be started.

5.2. Configuring the IP of PC


− The IP address of PC must be static.
− No DNS server must be setup.

TG0004 4 Ed. 02 / 12 October 2004


OmniPCX Enterprise
TROUBLESHOOTING GUIDE No. 4 OmniPCX ENTERPRISE PC INSTALLER
APPLICATION

6. CHECKING THE OPERATION OF "OMNIPCX ENTERPRISE PC


INSTALLER" APPLICATION

6.1. Patch installation


− Start the "OmniPCX Enterprise PC Installer" application; refer to the "OmniPCX Enterprise PC
Installer" documentation.
− Check that the wperl.exe and ftpd.exe processes are available in Windows Task Manager
/Processes.

Ed. 02 / 12 October 2004 5 TG0004


OmniPCX Enterprise
OmniPCX ENTERPRISE PC INSTALLER TROUBLESHOOTING GUIDE No. 4
APPLICATION

6.2. Standard installation of a complete version


− Start the "OmniPCX Enterprise PC Installer" application; refer to the "OmniPCX Enterprise PC
Installer" documentation.
− Select Linux + Call Handling in the Installation type menu, filled in each field of this menu
and click on Apply.
− Check that the wperl.exe, dhcpd.exe, tftpd.exe and ftpd.exe processes are available in
Windows Task Manager /Processes.

TG0004 6 Ed. 02 / 12 October 2004


OmniPCX Enterprise
TROUBLESHOOTING GUIDE No. 4 OmniPCX ENTERPRISE PC INSTALLER
APPLICATION

7. CALL SERVER INSTALLATION TROUBLES

7.1. Call server software standard installation troubles

7.1.1. Operating problems of the "OmniPCX Enterprise PC Installer" application

An error message appears when the "OmniPCX Enterprise PC Installer" application starts:

This event can cause a TFTP misfunctioning (timeout) when installing an Appliance Server type of
Call Server on Windows NT4/ 2000/ XP.
Solution
Enable the automatic start and start the "Computer Browser" Windows service.

Ed. 02 / 12 October 2004 7 TG0004


OmniPCX Enterprise
OmniPCX ENTERPRISE PC INSTALLER TROUBLESHOOTING GUIDE No. 4
APPLICATION

An error message appears when the "OmniPCX Enterprise PC Installer" application starts:

This event can cause a FTP misfunctioning (timeout) when carrying out a standard installation of a
Call Server.
Solution
• Uninstall, re-install then start a first time the "OmniPCX Enterprise PC Installer" application as
local administrator (and not in a domain).

An error message appears when the "OmniPCX Enterprise PC Installer" application starts:

This event can occur when using two network boards causing a conflict for the application (e.g. a
PCI avm fritz! network board and pcmcia ISDN modem board, or standard IP board and a Wireless
LAN board) and involves the blocking of the application.
Solution
• In network interfaces, disable the board which causes the conflict (e.g. the pcmcia modem or
the Wireless LAN board).

TG0004 8 Ed. 02 / 12 October 2004


OmniPCX Enterprise
TROUBLESHOOTING GUIDE No. 4 OmniPCX ENTERPRISE PC INSTALLER
APPLICATION

7.1.2. During Bootp requests


During the standard installation of a complete version, the following message appears on the V24
configuration port of the Call Server:
Static Boot from ethernet (4)

IP address determination
============================

BOOTP request in progress -> 0:80:9f:2e:30:a2

*RcvTO,TOIPRcv,RcvTO,TOIPRcv,RcvTO,TOIPRcv,RcvTO,TOIPRcv,RcvTO,TOIPRcv,TOIPRcv,R
cvTO,TOIPRcv,RcvTO,TOIPRcv........

7.1.2.1. Problem of Ethernet connection


Solution
Check that the Ethernet cable is well connected between the PC server and Call Server.
Reminder
Crossed cable between the PC server and LAN port of Call Server board or 1, 2, 3 UNIT ports (if
SLANX4 daughter board used).
Straight cable between the PC server and UP-LINK port (if SLANX4 daughter board used).

7.1.2.2. Problems of DHCP server start


dhcpd.exe is not available in the Windows processes list.
Solution
− Check the dhcpd.conf file using "OmniPCX Enterprise PC Installer" menu /Tools/DHCPD
configuration.

Ed. 02 / 12 October 2004 9 TG0004


OmniPCX Enterprise
OmniPCX ENTERPRISE PC INSTALLER TROUBLESHOOTING GUIDE No. 4
APPLICATION

dhcpd.conf file on Alizé Call Server


# This file is automatically generated. Do not modify by hand.
always-reply-rfc1048 true;
default-lease-time 1800;
max-lease-time 1800;
dynamic-bootp-lease-length 1800;

server-name "PC-Install";
option host-name "OXE_1";

filename "/bootp/linux/5.0/alize/startup.txt";
option vendor-encapsulated-options "SD:/dhs3mgr/e1601.fr";

subnet 10.28.0.0 netmask 255.255.0.0 {


range dynamic-bootp 10.28.1.15 ;
}
# Appliance Server DHCP requests
vendor-class "PXEClient" {
option dhcp-class-identifier "PXEServer";
filename "/bootp/linux/5.0/pxe/pxeloader";
}

# Second DHCP request issued by the linux install software


# filename is irrelevant but shall be present
vendor-class "alcatel.cse.0" {
filename "/bootp/linux/linux.ram" ;
}
# OmniPCX Call Server BOOTP requests

dhcpd.conf file on Appliance Server Call Server


# This file is automatically generated. Do not modify by hand.
always-reply-rfc1048 true;
default-lease-time 1800;
max-lease-time 1800;
dynamic-bootp-lease-length 1800;

server-name "PC-Install";
option host-name "OXE_1";

option vendor-encapsulated-options "SD:/dhs3mgr/e1601.fr";

subnet 10.28.0.0 netmask 255.255.0.0 {


range dynamic-bootp 10.28.1.15 ;
}
# Appliance Server DHCP requests
vendor-class "PXEClient" {
option dhcp-class-identifier "PXEServer";
filename "/bootp/linux/5.0/pxe/pxeloader";
}

# Second DHCP request issued by the linux install software


# filename is irrelevant but shall be present
vendor-class "alcatel.cse.0" {
filename "/bootp/linux/linux.ram" ;
}
# OmniPCX Call Server BOOTP requests

TG0004 10 Ed. 02 / 12 October 2004


OmniPCX Enterprise
TROUBLESHOOTING GUIDE No. 4 OmniPCX ENTERPRISE PC INSTALLER
APPLICATION

7.1.2.3. Problem of IP addresses in the same sub-network


Check the IP configuration of the PC.
A network card has two IP addresses IP in the same sub-network (ipconfig /all command under
DOS command prompt).

Solution
Manage only one IP address in a same sub-network in Advanced TCP/IP settings.

Ed. 02 / 12 October 2004 11 TG0004


OmniPCX Enterprise
OmniPCX ENTERPRISE PC INSTALLER TROUBLESHOOTING GUIDE No. 4
APPLICATION

7.2. Call server patch installation troubles


During the installation of a patch, the following message appears on the V24 configuration port of
the Call Server:
Confirm the full path /dhs3mgr/f16023g (y/n, default y):

The path of the delivery is /dhs3mgr/f16023g


ftp: connect: Connection refused

This path is not reachable


Press return

Solution
Check that the PC Server can be reached from Call Server: Launch a ping command from Call
Server on IP address of PC Server.
If the ping failed, check the Ethernet cable (see section 5.1.2.1) et IP addresses of the Call Server
and PC.

TG0004 12 Ed. 02 / 12 October 2004


OmniPCX Enterprise
TROUBLESHOOTING GUIDE No. 4 OmniPCX ENTERPRISE PC INSTALLER
APPLICATION

Start the "OmniPCX Enterprise PC Installer" application. In the field Installation type, select
the type of installation to Call handling or patch only.

The patch installation on the Call Server is done with swinst and "OmniPCX Enterprise PC Installer"
application.
Use Expert menu/Deliveries installation menu of swinst.
Name the patch with the repertory name on PC server:
For example: /dhs3mgr/f16023g

ALCATEL BUSINESS SYSTEMS


Delivery menu Installation FACILITIES 2.22.0

1 Install delivery from server


2 About last install deliveries operations
Q Go back to previous menu

Your choice [1..2, Q] ? 1

Enter the name of the server (default 155.132.33.208) ->

The installation of the binaries will modify the current installed version
Please, confirm the installation of a new version (y/n, default y):

Enter the full path of the delivery on the server

example for Unix server: /twdhs3/dhs3ref/dhs3ref_d1/E1.700/LIVRAISON


for Windows server: /dhs3mgr/E1700
-> /dhs3mgr/f16023g

Confirm the full path d:/dhs3mgr/e16043c (y/n, default y):

The path of the delivery is d:/dhs3mgr/e16043c

Check the patch loading with swinst on the V24 configuration port of the Call Server.
NOTE
Loading progress is visible on the "OmniPCX Enterprise PC Installer" application.

Ed. 02 / 12 October 2004 13 TG0004


OmniPCX Enterprise
OmniPCX ENTERPRISE PC INSTALLER TROUBLESHOOTING GUIDE No. 4
APPLICATION

8. UNINSTALLATION TROUBLES OF THE SOFTWARE


For troubles of automatic uninstallation of the "OmniPCX Enterprise PC Installer" application, run, if
necessary, the following steps to delete manually the various components of the application.

8.1. Deleting the "OmniPCX Enterprise PC Installer" directory


Delete the c:\Program files\OmniPCX Enterprise PC Installer directory.

8.2. Deleting the environment variables


− Delete the CYGWIN system variable: Ntsec
− Delete the HOME system variable: c:\PROGRA~1\Alcatel\OMIPC~1\home

TG0004 14 Ed. 02 / 12 October 2004


OmniPCX Enterprise
TROUBLESHOOTING GUIDE No. 4 OmniPCX ENTERPRISE PC INSTALLER
APPLICATION

− Change the PATH system variable:


Delete the multiple c:\WINNT\system32 entries in the value of the added variable when
installing OmniPCX Enterprise PC Installer and retain only one entry.

8.3. Deleting the icon on desktop


Delete the "OmniPCX Enterprise PC Installer" icon on the desktop.

8.4. Deleting the "OmniPCX Enterprise PC Installer" application in Start menu


Delete the "OmniPCX Enterprise PC Installer" software in the Start menu (profile All Users).

8.5. Deleting the intputs in registry


Delete the various intputs in the registry with the regedit command:
− HKEY_CURRENT_USER\Software\Cygnus Solutions
− HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions
− HKEY_USERS\.DEFAULT\Software\Cygnus Solutions
− HKEY_CLASSES_ROOT\PC_OXE

Ed. 02 / 12 October 2004 15 TG0004


OmniPCX Enterprise
OmniPCX ENTERPRISE PC INSTALLER TROUBLESHOOTING GUIDE No. 4
APPLICATION

9. RECOVERING THE INFORMATION FOR ANALYSIS


For any other troubles not identified previously, a certain number of information will have to be
provided to Technical Support for a detailed analysis.

9.1. Log files of "OmniPCX Enterprise PC Installer" application


"OmniPCX Enterprise PC Installer" application creates a log file on each loading. This file is available
via the /Tools/Servers log file menu of the application.
The syslog.txt file (copied into syslog-0.txt when closing the application) is available under
the \var\log directory of the application (e.g. c:\Program Files\Alcatel\OmniPCX
Enterprise PC Installer\var\log)

9.2. Recovering the registry of Server PC


From Start/Run menu, type regedit.
In the File menu of registry explorer, select Export ... then a file name and click on All to
export all the registry.

9.3. Recovering the IP configuration of Server PC


Open a DOS window then go the bin directory of "OmniPCX Enterprise PC Installer" application
(e.g. cd C:\Program Files\Alcatel\OmniPCX Enterprise PC Installer\bin)

Enter the perl dumpnet.pl>a_file_name command


(e.g. perl dumpnet.pl>c:\dumpnet.txt) followed of as many Enter key pressing necessary
to find the prompt one (generally 7).

9.4. Recovering the list of services of Server PC


Copy the services.pl script into the bin directory of the "OmniPCX Enterprise PC Installer"
application.
Open a DOS window then go the bin directory of "OmniPCX Enterprise PC Installer" application
(e.g. cd C:\Program Files\Alcatel\OmniPCX Enterprise PC Installer\bin)
Enter the perl services.pl>a_file_name command
(e.g. perl services.pl>c:\services.txt then press Enter key.

TG0004 16 Ed. 02 / 12 October 2004

You might also like