Embed Size (px)
Citation preview
Alcatel-Lucent OmniVista 4760Network Management System
Installation Manual
Alcatel-Lucent OmniVista 4760 Network Management SystemAll Rights Reserved © Alcatel-Lucent 2009
Legal notice:
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks ofAlcatel-Lucent. All other trademarks are the property of their respectiveowners.
The information presented is subject to change without notice.
Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright © 2009 Alcatel-Lucent. All rights reserved.
The CE mark indicates that this product conforms to the following CouncilDirectives:- 89/336/CEE (concerning electro-magnetic compatibility)- 73/23/CEE (concerning electrical safety)- 1999/5/CE (R&TTE)
Chapter 1Overview
Installing the software .......................................................................... 1.1
Operating Systems ................................................................................ 1.1
Chapter 2Server requirements
Requirements .......................................................................................... 2.1
Software Compatibility ......................................................................... 2.2
Analyzing Compatibility .............................................................................. 2.2
Resources Required by Other Applications ............................................. 2.2
Installation/Uninstallation Sequence of Applications .............................. 2.2
Antivirus ....................................................................................................... 2.2
Drive Space .............................................................................................. 2.3
Space Required ........................................................................................... 2.3
Rules for Partitioning Drives ...................................................................... 2.3
Configuring the Operating System .................................................. 2.4
PCX Requirements ................................................................................. 2.4
Collecting Data from the Server ........................................................ 2.7
List of Data to be Collected ........................................................................ 2.7
Windows Data .............................................................................................. 2.7
0-1
OmniVista 4760 Installation Data ............................................................... 2.8
Chapter 3Server installation
Overview .................................................................................................... 3.1
Loading Programs ................................................................................. 3.1
Chapter 4Server post-installation
Configuring the OmniVista 4760 application ............................... 4.1
Configuring the PCX OmniPCX 4400/Alcatel-Lucent OmniPCXEnterprise CS ........................................................................................... 4.3
Maintenance ............................................................................................. 4.3
Defragmenting the hard drive .................................................................... 4.3
Saving the database .................................................................................... 4.3
Defragmenting the databases .................................................................... 4.4
Passwords ................................................................................................ 4.4
Overview ....................................................................................................... 4.4
Updating Password ..................................................................................... 4.4
Special procedures ................................................................................ 4.5
Modifying an IP address ............................................................................. 4.5
Changing the Apache WEB port number .................................................. 4.6
Declaring a mail server ............................................................................... 4.6
Changing the paper format and fonts ....................................................... 4.6
Changing PC name or the Windows DNS suffix. ...................................... 4.6
Changing the directory root name ............................................................. 4.7
Exceeding capacity ..................................................................................... 4.7
Remote backup ....................................................................................... 4.7
0-2
Overview ....................................................................................................... 4.8
Restrictions .................................................................................................. 4.8
Configuration - 2 PCs in a domain ............................................................. 4.8
Configuration - 2 PCs in the same Workgroup ......................................... 4.8
Chapter 5Checking installation
Operations ................................................................................................ 5.1
Chapter 6Uninstalling the Server
Automatic Uninstall ............................................................................... 6.1
Automatic Uninstall with Traces ....................................................... 6.1
Manual Uninstall ..................................................................................... 6.1
Chapter 7Client requirements
Administration client PC requirements .......................................... 7.1
Web directory client PC, required configuration ........................ 7.1
Connections ............................................................................................. 7.1
Chapter 8Installing the Client
0-3
Running the OmniVista 4760 InstallShield Wizard for the client........................................................................................................................ 8.1
Multiple Version Installation ............................................................... 8.8
Starting the application for the first time ....................................... 8.9
Chapter 9Uninstalling a Client
Chapter 10Access via a browser
Software and hardware requirements ...........................................10.1
Installing the Java Runtime Environment ....................................10.1
Network requirements .........................................................................10.1
Installing and initializing JRE via a browser ...............................10.1
Configuring the Internet browser ..............................................................10.1
Installation ...................................................................................................10.2
Initializing ....................................................................................................10.2
Loading problems ......................................................................................10.3
Chapter 11Installing the Java Runtime Environment
Installing the Java Runtime Environment (JRE) ........................11.1
Configuring the Java plug-in ............................................................11.1
0-4
Chapter 12Connectivity
Ethernet (LAN) connectivity ..............................................................12.2
OmniPCX 4400 \ Alcatel-Lucent OmniPCX Enterprise CS ......12.3
Configuring PPP connectivity on the OmniVista 4760 server ................12.3
Declaring an OmniPCX 4400/Alcatel-Lucent OmniPCX Enterprise CS inPPP mode (on the PCX side) .....................................................................12.7
Configuring modems with or without RMA ..............................................12.9
Configuring TAs with or without RMA ......................................................12.9
Configuring the RMA unit ........................................................................ 12.12
Configuring the e-RMA unit (1) ............................................................... 12.12
IP/X25 connectivity (Alcatel-Lucent OmniPCX Enterprise CS/OmniPCX4400) .......................................................................................................... 12.14
Useful information (Alcatel-Lucent OmniPCX Enterprise CS/OmniPCX4400) .......................................................................................................... 12.17
Configuring RMA alarms ......................................................................... 12.18
OmniPCX Office ................................................................................... 12.22
Declaring a modem on a PC hosting OmniVista 4760 server .............. 12.22
Declaring an OmniPCX Office in PPP mode on the OmniVista 4760 ... 12.23
Declaring an OmniPCX Office in PPP mode (on the PCX side) ........... 12.24
Urgent alarm management on PPP connectivity ................................... 12.24
Urgent alarm management on Ethernet connectivity ........................... 12.28
Useful information for the OmniPCX Office ........................................... 12.28
Diva Board connectivity .................................................................... 12.30
Description ................................................................................................ 12.30
Connection to OmniPCX Office ............................................................... 12.30
Connection to Alcatel-Lucent OmniPCX Enterprise CS ....................... 12.31
Chapter 13Security
0-5
0-6
1.1 Installing the software
To install the Alcatel-Lucent OmniVista 4760 Network Management System (called OmniVista4760 in this document ) and give the different clients access to it, a license file (specific to yourPCX network and the modules available) is required.
To install an OmniVista 4760 Server, you should be familiar with:
- The hardware and software required to install the Server.
- The procedure for loading the module from the DVD-ROM.
- The different connection possibilities between the OmniVista 4760 Server and theOmniPCXs.
- The post-installation operations required to configure the Server correctly.
To install an OmniVista 4760 Client, you should be familiar with:
- The hardware and software required to install the Client.
- The module loading procedure (using the DVD ROM or an HTML browser).
There are two specific chapters on the uninstall procedures for the Client and Server modules.
1.2 Operating Systems
The following table lists the Windows operating systems supported, according to the moduleinstalled, Client or Server. Refer to the relevant chapter for more information.
table 1.1: Supported operating systemsOperating Systems Server Client
Windows 2003 Server R2 X X
Windows 2003 Server SP2standard edition X X
Windows XP-ProfessionalSP3 X X
Windows VISTA X
X: Supported.
Note 1:
The installation of OmniVista 4760 server is compatible with the Virtual Machine VMWARE ESX without
the support of PPP connectivity and SIP Manager.
Note 2:
The Microsoft security hotfix can be installed on the OmniVista 4760 PC. But when a new service pack is
published by the Microsoft, you need to wait for the next OmniVista 4760 release that is compatible with
the newly published service pack, before installing it on the PC.
1
1-1
Chapter 1
1-2
2.1 Requirements
The OmniVista 4760 Server module must be run on a dedicated PC with the followingminimum (0) characteristics.
table 2.1: Requirements for OmniVista 4760 serverCapacity Low Large
Number of sub-scribers <5,000 >5,000 (1)
SIP DM Server No No Yes
Operating System (2) Windows XP Profes-sional SP3
Windows 2003 Server Standard Edition (SP2mandatory)
Processor (3)
Celeron 420 (1,6 GHz –Single Core)
Intel ® Xenon DUALprocessor ® CPU5130@ 2.00 GHz, 2.00GHz
Intel ® Xenon DUALprocessor ® CPU
5130@ 2.00 GHz, 2.00GHz
RAM 1 GB 2 GB 3 GB
Minimal characterist-ics of Hard Disk
40 GB 80 GB, RAID 5 (3 disksminimum), controller512 MB
120 GB, RAID 5 (3 disksminimum), controller
512 MB
Graphics board 4 MB video memory supporting a resolution of 1024x768, 16 million colors
Monitor 17 inches (19 inches recommended)
Partition 1 NTFS partition for installation of the LDAP server of SunONE
Internet browser Internet Explorer (version 6 or 7)Mozilla FireFox 2.0
Drives A DVD-ROM drive is required
Compatibility The OmniVista 4760 server must be a dedicated server (2):- No other applications must be installed.- The domain controller, Web server functions delivered with the operat-
ing system must not be installed.
(0) minimum implies a targeted use of the application. The use of the client PC on the serverPC must be minimum, that is to say with a single module opened.There is no mass processing (more than 100 entries managed in the grid). Otherwise, therequirements must be modified to take account of the needs associated with the clientapplication.In all cases, the performance of the OmniVista 4760 client part is better if the client applicationis started from a remote PC.
(1) Capacities greater than 30000 users and 400 PCX require Alcatel agreement to check yoursystem configuration and to help you to generate the license file.
(2) Only VMware ESX, operating system installed as Virtual machine is validated. Data Centerand other specific Windows editions are not validated . Regarding Small business edition thiswindows edition is packaged as a Windows Domain Controler: it includes Active directoryserver, an LDAP server which prevent OmniVista 4760 default installation. Regarding
2
2-1
Windows 64-bit edition, this version is not supported by OmniVista 4760 installer nor byOmniVista 4760 component.For any request regarding such validation, you can contact the Alcatel Professional Services.
(3) Processors types are given as examples. The frequency clock is a minimum requirement.
2.2 Software Compatibility
Installation on a dedicated server PC best meets requirements and guarantees optimumsoftware operation. If the server PC must support other applications, compatibility must beanalyzed, the system resource requirements and performance of the other applicationsassessed, and the correct install and uninstall procedures followed.
2.2.1 Analyzing Compatibility
Other applications must not use a OmniVista 4760 server-dedicated port. See the moduleInstallation - Security § List of IP protocols and port numbers.Do not install the Web server (for example: IIS delivered with Windows server).Do not install the LDAP server (for example: Active Directory delivered with Windows server).Do not install applications that update system libraries (dll files).The A4715, A4730, A4730i and A4740 applications are not compatible with OmniVista 4760.
2.2.2 Resources Required by Other Applications
External applications must not be server type applications.Make sure that the other applications do not use the system virtual memory and CPU time andalso check that once these applications are closed, the memory used is freed.
2.2.3 Installation/Uninstallation Sequence of Applications
The OmniVista 4760 server application must be the last application to be installed to avoid anyoverwriting of its files.If the server PC has several network boards, the order of server network interfaces in theconfiguration must not be modified.
Important:
If you uninstall an external application, do not confirm deletion of dll files as these may be re-
quired by the OmniVista 4760 server.
2.2.4 Antivirus
You can install antivirus software on your OmniVista 4760 client and server PC, consideringthe following recommendations:
- Stop the antivirus during the OmniVista 4760 installation.
- Put the directory used by the OmniVista 4760 as an exception in the antivirus rule.Otherwise, the antivirus will scan the client data whenever you start the client, and this willincrease the loading time of the client application.
- Configure the antivirus, antispam option and wormstopper option to allow the mail protocol
Chapter 2
2-2
(smtp port 25).Allow omnivista binaries (javaw.exe) to use mail protocol and increase the number ofpermitted e-mails (wormstopper option may limit the number of e-mails from a PC to amaximum of six mails per minute).
2.3 Drive Space
2.3.1 Space Required
To install the server OmniVista 4760 application programs, you must have 500MB available. Inaddition, when it is operating, the application requires additional drive space depending on:
- The number of applications installed: directory, accounting, traffic analysis, etc.
- Download frequency and the amount of data collected from PCXs.
- The archiving mode used.
- The maintenance operations programmed (defragmentation and backup).
- etc.
The following example is for Accounting, and requires collection and storage of records fromPCXs.Data entry:
- 10 records (tickets) per day and per user.
- 60 working days of storage.
- 1 record requires about 1KB on the drive.
For 5,000 users and after a period of 60 days, the space occupied by the data on the disk isapproximately 3 GB.
If you plan to use this 3 GB limit for accounting, the partition that supports the database mustbe correctly sized at installation (directory D:\4760\DATA).
Caution:
OmniVista 4760 database backup and defragmentation operations require twice as much memory
(drive) space as that used by the database. The partition that will be used for backups must there-
fore be correctly sized. If all databases take up 4 GB, at least 8 GB free space is required to back
them up.
2.3.2 Rules for Partitioning Drives
- Set up an NTFS system partition (C:) of 4 GB (8 GB in case of disk space of 18 GB ormore) when installing Windows,
- Create an NTFS partition called DATA (D:)
- Install the OmniVista 4760 application on the data partition (D:) (binary, database),
- Keep Sybase binaries under C:\ Program files
2-3
Figure 2.1: Drive partitioning
2.4 Configuring the Operating System
The installation partition must be formatted as NTFS to host the LDAP server. At installation, itis preferable to keep the default directories and only modify the physical drives.
Caution 1:
Windows must not be installed as domain controller.
RAM: Make sure virtual memory is correctly configured. Maximum size must be equal to ordouble physical memory.Path: The Path environment variable giving the access path to Windows and its dlls is updatedafter installation of OmniVista 4760 and Sybase and must not be corrupted.
- Prior to installation, the path should be Path = C:\winnt\system32;C:\winnt;.
- If the path is too long, installation may be aborted. In this case, paths that are not requiredshould be deleted.
- Make sure the Path contains no obsolete paths or duplicated items (;; or \\).
TCP/IP protocol: TCP/IP protocol V4 must be installed on the OmniVista 4760 server, whichmust have a fixed IP address. If a DHCP server is present on the network, you must excludethe OmniVista 4760 server address. TCP/IP protocol V6 is not supported.Web browser: Internet Explorer 7, Mozilla or FireFox 2.0 must have been installed on the PC(Netscape is not supported).You must have a valid license file for the current version of the OmniVista 4760. Such licensecannot be duplicated to install a second server OmniVista 4760 , except for less than 32 days.
Caution 2:
Permanently modify the DNS Suffix and server name before starting the installation as it is not
possible to change these after the installation.
To ensure server-client connections, you must integrate the OmniVista 4760 server in the DNSserver. Otherwise, you have to edit the host file on each client PC and server PC, by addingthe IP address, host name and the hostname.dnssuffix information.
2.5 PCX Requirements
A complete list of PCX version supported by the OmniVista 4760 is given below. If one PCXrelease does not support one basic feature of OmniVista 4760 (connectivity, configuration,alarm, ticket retrieval) a note has been added to this list.
If a PCX release requires a patch to keep on providing such basic features, the version of the
Chapter 2
2-4
patch has been updated.
This corrective patch is also mandatory for previous OmniVista 4760 releases that supportsame PCX release. For newly introduced PCX releases, the PCX release may include newinterfaces and new features that require the OmniVista 4760 release to be launched at sametime.
Example:
e2.504.a has a corrupted MIB that prevent any OmniVista 4760 release to perform synchronization, the
fix is done in e2.504.1ad; hence e2.504.1ad is the new minimum version compatible with any OmniVista
4760 that supports OmniVista 4760 R5.1.2
f5.401.11 introduce a new object : Passive Call server which is taken into account only from OmniVista
4760 R4.1.
table 2.2: IP or IP/X25, PPP Connections to OmniPCX 4400 & Alcatel-Lucent OmniPCX EnterpriseCommunication Server
Release Software version equal to orhigher than
IP or IP/X25 connec-tion PPP connection
3.0 c1.532.5 w (except STAP) Yes No
3.2 M c1.712.5 c, C1.714.3.a Yes Yes
3.2 C2 C1.762.21 Yes Yes
4.1 D1.305.4 f Yes Yes
4.1.1 D1.311.7 d Yes Yes
4.2.1 D2.304.4 s Yes Yes
5.0 Ux D2.313.7 f Yes Yes
5.0.1.Ux D2.314.7.p Yes Yes
5.0 Lx E1.604.9 t Yes No
5.1 E2.404.u Yes No
5.1.1 E2 502.2.p Yes No
5.1.2 E2 504.1ai Yes Yes
6.0 F1.602.3.i Yes No
6.0.1 F1.603.1.u Yes Yes
6.1 F2.500.6.g Yes No
6.1.1 F2.502.12 Yes Yes
6.2 F3.301.35 Yes Yes
7.0 F4.401.17 Yes Yes
7.1 F5.401.11 Yes Yes
8.0 G1.302.5 Yes Yes
8.0G1.503.9
(before OXE R9.0)Yes Yes
9.0 H1.301.34 Yes Yes
9.1 I1.605.2 Yes Yes
table 2.3: IP or PPP to OmniPCX Office
2-5
Release Minimum software release IP connection PPP connection (3)
R1.0 1.0.51.04 (1) Yes Yes
R1.1 1.1.19.06 (1) Yes Yes
R2.0 2.0.32.013 Yes Yes
R2.1 R210.083.001 Yes Yes
R3.0 3.0.19.1 (2) Yes Yes
R3.1 R310.038.001 Yes Yes
R4.0 R400.022.001 Yes Yes
R4.1 R410.015.005 Yes Yes
R5.0 R500.030.004 Yes Yes
R5.1 R510.017.001 Yes Yes
R6.0 R600.014.001 Yes Yes
R6.1 R610.038.001 Yes Yes
R7.0 R700.027.001 Yes Yes
R7.1 R710.030.001 Yes Yes
(1) Urgent alarms via PPP are available from OmniPCX Office 2.0 only
(2) If Accounting is used, upgrade to R3.1.
(3)
- Windows 2003 server is mandatory to receive urgent alarms on the fly,
- No S0 modem with OXO 1.x
- 2 B channel connectivity with OmniPCX Office 400 / 016.003 and Multitech ISDN modem.
Note 1:
The PCX version has been updated to take the corrections of the accounting buffer on the OmniPCX Of-
fice side into account.
OmniVista 4760 does not synchronize OmniPCX Office management. Only alarms, accountingand VoIP performance are retrieved. To manage OmniPCX Office, OmniVista 4760 shows alink in the configuration application launching the OMC software. This software must be locallyinstalled on the PC from which the client OmniVista 4760 is launched.
Note 2:
OMC must be installed and launched on the server PC.
table 2.4: OMC Release Compatibility with Operating Systems:OMC Releases Windows XP SP3 Windows 2003 SP2/R2
6.0 X X
7.0 X X
700/8.1.c x x
710/11.1a X X
710/12.1a X X
X: supported.
Chapter 2
2-6
Note 3:
As of R5.0, Alcatel-Lucent Office (4200) is not supported.
2.6 Collecting Data from the Server
2.6.1 List of Data to be Collected
Before installing the server and clients, you need to obtain the following data:
- Windows data. This enables the server PC to be integrated into the client computernetwork.• IP address of the server PC.• Network hostname• DNS suffix name• Local administrator account• Mail server name or address, sender address used for sending mail• Workgroup or DNS domain name of the PC
- Installation data• License file• Passwords• Directory root name• Type of connection to the PCX
- Management data. This makes configuration operations performed jointly with thecustomer after installation easier to perform.• Directory• Carrier configuration• Access security• Save (backup) mode
2.6.2 Windows Data
Most of the windows data must be configured and confirmed jointly with the customer.In Windows, the following information can be accessed via a slightly different path.
IP configuration, DNS, etc.
- Click Start > Connections > Display all connections. A window presenting the differentconnections (LAN/RAS) is displayed.
- Via the shortcut menu, access Local network connections. IP, DNS, etc. parameters arelisted.
Integrating the PC into a domain/workgroup
- Open the shortcut menu of the Workstation icon on Windows desktop. A window withseveral tabs is displayed.
- Access the Network identification tab. The computer name and assignation to a domainor Workgroup can be modified
2-7
Configuring the DNS suffix
- One of the specific features of Windows is DNS suffix management per local connection.With the OmniVista 4760 application, this suffix must be unique. Thus the DNS suffix mustbe managed directly in the system properties.
- Still at network identification level, click Properties, then Others to manage the DNS suffix
- Do not check the Modify the main DNS suffix when domain assignments are modifiedbox.
Installation must be performed using a local administrator account.The IP address of the OmniVista 4760 server must be fixed and must not be assigned by aDHCP server.
Hostname and Domain name must be determined to comply with DNS management of thesite, otherwise clients connected via an HTML browser will not be able to access the server.
Hostname and Netbiosname must be identical. By default windows uses a netbios namecalculated from the hostname but with an additional limitation.Hence hostname and netbiosname
- must not be composed of digits and needs to start with a letter
- must have less than 15 characters
- must not include characters like "."
With this limitation names like 4760, alcatelomnivista4760, omnivista.server are not allowed.
To check this, display "Network properties". The NETBIOS name is displayed on the"identification" tab and hostname on the "DNS" tab in "TCP/IP" protocol properties.
If there is another Web server present, this will result in a conflict on the HTTP 80 port. Thismust be resolved before installing the server.
2.6.3 OmniVista 4760 Installation Data
Before beginning the installation, you need:
1. The OmniVista 4760 license file supplied by ACTIS, eLP.
2. To specify the main language used in the application. This language is:• Selected at installation.• Used for installation and upgrade operations.• Used to configure some important server settings:
• The names of predefined groups in the company directory.
Note 1:In addition to the selected main language, you can also select another operating language froma list each time you access the server. The default language proposed is the language used dur-ing the last 4760 client session.
3. Choose a password for the administration accounts. All the accounts will have the samepassword. The following four accounts are declared during the installation of the OmniVista4760 server.• Admin
This account cannot be accessed via OmniVista 4760. It is reserved for LDAP directoryspecialists.
Chapter 2
2-8
• Directory ManagerThis account cannot be accessed via OmniVista 4760. It is reserved for LDAP directoryspecialists.
• AdminnmcThis is the account used by the OmniVista 4760 application administrator. Theadministrator can create other accounts and assign their rights.
• DBAThis is the account used by the Sybase data server.
Note 2:Record the password in an installation document.
4. Select a name for the company's directory Root.This name cannot be modified after installation. Usually, it is the company name. But if thecompany name changes, it is recommended to choose a generic name. This name will bevisible to the client when consulting the directory via a WEB browser.In addition, the LDAP clients (outlook, OmniPCX Enterprise for directory overflow to LDAPserver, 4980 or 4059) must indicate the full name of the root directory for searches. Thisname must be written as follows: o=”company directory root name”, o=DirectoryRoot.
5. Specify connection modes for connection to the PCX (Ethernet or IP/X25) and, for eachPCX, list:• Network name.• Subnet name and number.• Network node name and number.• IP address (two IP adresses for OmniPCX Enterprise supporting spatial redundancy).• Gateway PCX name, if using IP/X25 connectivity.• The name and password associated with the account to allow FTP sessions to run.
Caution:
For an OmniVista 4760 license linked to a PCX key:
Install, connect and synchronize the OmniVista 4760 with the reference PCX and put it into ser-
vice as soon as possible.
If these operations are not performed, the server cannot validate the license file. If the license file
is not validated within 32 days, the administration client will work in depreciated mode allowing
only the following actions:
- Change the PCX connectivity information in the system directory.
2-9
Chapter 2
2-10
3.1 Overview
The OmniVista 4760 supplies an Installshield Wizard on DVD-ROM for installing the server.Perform the installation using a local administrator account. It takes approximately 25 minutes.Before starting the installation, you should be familiar with all the data listed in moduleInstallation - Server requirements § Collecting Data from the Server .
If no Java Runtime Environment (JRE) is present on the server, the OmniVista 4760Installshield Wizard will install the JRE automatically. You can install the JRE before installingthe server. See module Installation - Installing the Java Runtime Environment .
Do not install the OmniVista 4760 server on a Windows server configured as a domaincontroller (as it includes the “Active directory” software, Microsoft LDAP server).
Before installing the OmniVista 4760 server, check that the Internet Information Server(Microsoft IIS) service has been uninstalled and that the Telephony service is launched.
We recommend you to stop the antivirus and firewall programs because these programs mayslow or block the installation, or require a confirmation for a pop up during the silent installationof the OmniVista 4760 components.
The installation log file is located in Document and Settings\administrator\Local Settings/Temp(administrator is the windows account that is used to install the OmniVista 4760).
3.2 Loading Programs
To install the OmniVista 4760 server, use the following procedure. The InstallShield Wizard willpresent you with a series of dialog boxes.
1. Insert the DVD-ROM in the drive. If the installation is not launched automatically,double-click ServerSetup.exe. The Choose Setup Language dialog box appears.
Figure 3.1: Choose Setup Language Dialog Box
2. Select the language for the installation and click OK. If the Java Runtime Environment(JRE) is not installed on the PC, the InstallShield Wizard will prompt you to install it anddisplay the following dialog box.
3
3-1
Figure 3.2: InstallShield Wizard
3. Click Install to install the JRE.
Note 1:If the JRE is already installed on the PC, the installation procedure skips to the dialog box displayedin step 5 .You will be asked to accept the JRE license agreement.
Chapter 3
3-2
Figure 3.3: JRE Licence Agreement Dialog Box
4. Click Accept.The JRE installation proceeds, and displays the following dialog box whenJRE is installed.
3-3
Figure 3.4: JRE Installation Complete Dialog Box
5. Click Finish. The OmniVista 4760 InstallShield Wizard welcome dialog box appears. TheWizard will prepare for the installation and you will be asked to wait.
Chapter 3
3-4
Figure 3.5: OmniVista 4760 Server Welcome Dialog BoxThe title bar displays the release identification for this installation.
Note 2:Screenshots in this document are provided as examples only. The release identification number maynot be up to date.
6. When the Wizard is ready, the Next button will become active. Click Next. You will beasked to accept the OmniVista 4760 license agreement.
3-5
Figure 3.6: OmniVista 4760 License Agreement Dialog Box
7. Once you have read the license agreement, select I accept and click Next. The Wizard willnow check for the presence of the OmniVista 4760 license file supplied by ACTIS, eLP.
Note 3:
• To avoid interruption during the installation process, do not press the Cancel button
• The DMS Server package must only be installed after the installation of OmniVista 4760 Server.
Chapter 3
3-6
Figure 3.7: OmniVista 4760 License Information Dialog Box
8. If the Wizard does not find the file in the default location, click Change. The Browse ForFolder dialog box appears, where you can select the location of the license file on yourserver. Once the license file has been validated, click Next. The Company Informationdialog box appears.
3-7
Figure 3.8: Company Information Dialog Box
9. Enter the company name to be displayed at the root of the Company directory. You cannotchange this name after the installation. Click Next. The Destination Folder dialog boxappears.
Chapter 3
3-8
Figure 3.9: Destination Folder Dialog Box
10. The default installation directory C:\ 4760 can be used if it has a free space of 18GB. If theavailable disk space in C:/ is less than 18GB, use the directory D. To modify the defaultdirectory, click Change and browse to select the desired location.Note that root should notbe selected as desired location (see module Installation - Server requirements § Rules forPartitioning Drives ). Once you have selected the directory, click Next. The OtherDestination Folders dialog box appears.
3-9
Figure 3.10: Other Destination Folders Dialog BoxThe Other Destination Folders dialog box displays the default installation locations forSybase SQL Anywhere and SunOne server. To modify the default location, click Change.The Browse For Folder dialog box is displayed.The SunOne directory requires a minimum of 35% free disk space.
11. Once you have selected the locations, click Next. The Data Folders dialog box appears.
Chapter 3
3-10
Figure 3.11: Data Folders Dialog BoxThe Data Folders dialog box displays the default locations for the Sybase SQL Anywheredata files and the OmniVista 4760 archive files.The 4760_ARC directory is used to archive records and files from the data backup andrestore operations. This directory is independent of the OmniVista 4760 installationdirectory and its contents are not affected if the server software is uninstalled.To modify the default location (note that root should not be selected as default location),click Change. The Sybase SQL data file directory requires a minimum of 35% free diskspace.
12. Once you have selected the locations, click Next. The Server Settings dialog boxappears.
3-11
Figure 3.12: Server Settings Dialog BoxThe Server Name and DNS Suffix cannot be modified. These are the DNS host name andsuffix of computer where you are installing the server.Enter the IP name or number of your e-mail server. The format of the mail sender addressof the server is: omnivista@<4760 server name>.<4760 server DNS suffix name>. Thisaddress can be modified after the installation. From NMC>OmniVista 4760 name in theSystem directory, you can update the mailsender field.The memory usage must be less than 85%. If there is not enough available memory,cancel the installation and stop the programs running on the server, before restarting theinstallation procedure.
13. If there is sufficient memory, click Next.The Service Settings dialog box appears.
Chapter 3
3-12
Figure 3.13: Service Settings Dialog BoxThe LDAP server port is the dedicated communication port for the LDAP server. Thestandard port number is 389.The LDAPS server port is the dedicated communication port over SSL for the LDAPserver. The standard port number is 636.The HTTP Server port is the dedicated communication port for the Apache server which isalso installed by the OmniVista 4760 InstallShield Wizard. The standard port number is 80.We recommend you to configure the Windows firewall.
14. Click Next. The Directory Manager Accountdialog box appears.
3-13
Figure 3.14: Directory Manager Account Dialog Box
15. In the Password and Confirm Password fields, enter the logon password for theDirectory Manager account. The password must have a minimum of 8 characters. Thesame password will also be used for the Admin, AdminNmc, and DBA accounts. ClickNext. The Other Administrator Logons dialog box appears.
Chapter 3
3-14
Figure 3.15: Other Administrator Logons Dialog Box
Note 4:Carefully note the account names and the password chosen. They are required by the system forsoftware maintenance and upgrade operations.
16. In the Application administrator login field, you can enter another account name otherthan the default account name AdminNmc. The password for the newly entered accountname is the same as the password of AdminNMC, which is specified in the DirectoryManager Account dialog box. Click Next. The Localization Settings dialog box appears.
3-15
Figure 3.16: Localization Settings Dialog Box
17. Select the country from the Country list. The Language, Currency (used by the OmniVista4760 to calculate all costs) and Paper size attributes are set automatically depending onthe country selected. Click Next. The Accounting Settings dialog box appears.
Chapter 3
3-16
Figure 3.17: Accounting Settings Dialog Box
18. Select the management mode for the OmniVista 4760 cost centers. One mode applies toall the PCXs.a. For an Alcatel-Lucent OmniPCX Enterprise CS network:
• If you select Yes, accounting is updated with the PCX cost centers bysynchronization.
• If you select No, you may subsequently manage cost centers with more than 8characters in the directory.
b. For a network including an OmniPCX Office, keep the default option as Yes. The PCXis the only object in the System directory and the cost centers are not retrieved fromthe PCX. So, the chargeable entries will first be placed under a single cost center andcan then be moved to new cost centers in the Accounting application.
Click Next. The Preconfiguration dialog box appears.
3-17
Figure 3.18: Preconfiguration Dialog Box
19. In the Preconfiguration dialog box, you can create an expert account, create a defaultPCX and define the operator attributes.a. If an expert account is needed, select the check box beside Expert user and group
and click Configure. The Expert User and Group dialog box appears.
Chapter 3
3-18
Figure 3.19: Expert User and Group dialog boxSelect the Group, and enter an User ID and a password for an expert account. ClickOK.
b. To create a default OmniPCX Office or Alcatel-Lucent OmniPCX Enterprise CS, selectthe check box beside the PCX node in the Preconfiguration dialog box, and clickConfigure. The Preconfiguration of a PCX node dialog box appears.
3-19
Figure 3.20: Preconfiguration of a PCX node dialog boxSelect the type of PCX and click OK.
Chapter 3
3-20
Figure 3.21: Preconfiguration OmniPCX ParametersThe names and the IP address can be set.The default values PCX node=1, Network number= 0 and Sub-network number=0cannot be modified in this dialog box. These values can be modified after installation.
c. To define a name, unit cost, and tariffs for an operator, in the Preconfiguration dialogbox, select the check box beside Operator and click Configure. The OperatorPreconfiguration dialog box appears.
3-21
Figure 3.22: Operator Preconfiguration Dialog BoxComplete the attributes based on the following table:
Attributes Values
Operator Name Enter a name clearly specifying the charging carrier/operator, for example, France Tele-com (50 alphanumeric characters maximum)
Symbol Enter a code clearly identifying the charging carrier/operator, for example, FT (5 alpha-numeric characters maximum)
Start date The system displays the current date. Enter the date in the following format: YYYYMM-DD.
Note 5:To include the old PCX tickets in accounting processing, you can enter a date up to 2 monthsearlier than the current date.
Tariff name Enter the tariff name. This field is mandatory.
Unit cost The system displays “0.0”. You must enter a numerical value associated with the ac-counting pulse.
Tax Enter a label specifying the tax to be applied to the tariff.
Answered call initial cost the system displays “0.0”. You must enter a numerical value associated with the ac-counting pulse.
Chapter 3
3-22
Unanswered call initialcost
The system displays “0.0”. You must enter a numerical value associated with the ac-counting pulse.
Note 6:When entering the numerical values you have to use the decimal point separator “.” between thedigits.
When all fields are completed, click OK.In the Preconfiguration dialog box, click Next. The Ready to Install the Program dialogbox appears.
Figure 3.23: Ready to Install the Program dialog box
20. The Wizard is now ready to install the OmniVista 4760 server based on the informationentered. To proceed with the installation, click Install.
3-23
Figure 3.24: OmniVista 4760 Installation in Progress WindowThe Status indicates the current installation step.
21. When the Wizard has finished installing, you can choose to have the Wizard restart thecomputer immediately, or restart the computer yourself later. To exit the Wizard, clickFinish.
Chapter 3
3-24
Figure 3.25: Installation Completed Dialog BoxThe View log for Patches button opens the log window. The log window is useful in caseof installation error. This window displays the performed installations steps.
3-25
Chapter 3
3-26
4.1 Configuring the OmniVista 4760 application
After you have installed the software application for the OmniVista 4760 Server module, youmust perform a series of configuration operations to allow Client PCs to access theapplications. The following operations must be performed in the listed sequence and accordingto the applications available on the Server:
1. Logon:Launch OmniVista 4760 by connecting with the account declared during installation(AdminNmc by default).
2. Declaring PCXs:Launch the Directory application, then declare the PCX network in the System tab.Depending on site architecture:
Note 1:The Passive Communication Servers (PCS) do not need to be declared.
• If there is a conflict when updating cost centers (Server or PCX), specify the master tobe used: Nmc > NmcConfiguration > 4760 master.... Refer to the user documentation,Directory - Overview.
• Select the type of Accounting to be used on each PCX (global, detailed, etc.).
Figure 4.1: PCX declaration
3. As a precaution, export the Network branches to a file for reinstallation or to set up abackup server.If, during installation, you disabled automatic synchronization of cost centers with PCX costcenters, perform operations 4 and 5 in reverse order by first adding the data to thedirectory and then performing synchronization.
4. Synchronization:While in the System directory, launch the complete synchronization of PCXs to updatethe server database.
Note 2:Select the menu Help> About to find the declaration node and to check if the total number of usersis within the license limit.
5. Declaring directory entries:Directory entries can be declared by one of the following methods:• Automatically, by copying the data of sets declared in the PCX during PCX
4
4-1
synchronization.• Manually, with the Sets=>Users command to use entries from the System directory.• Semi-manually by importing an external LDIF file. BE CAREFUL! If your files contain
cost centers, these may overwrite those created via synchronization.Sets/Users links are automatically created for all similar entries in the Company directoryand the System Directory.If desired, enable automatic creation of Directory entries. Automatic creation onlyconcerns primary links.Objects concerned: users, alias, speed dial number, speed dial alias in the Nmc >NmcConfiguration > GlobalPreferences > DirectoryAdmin >Configuration entryPCX concerned: Select the Automatic creation box when creating the PCX.Placing entries: define the directory location where entries will be automatically created.This location is defined for the network, the subnetwork, or the PCX.For basic architectures where the assignment of sets to users is limited (set X <=>person Y), automatic creation avoids the tedious entry of data.For complex architectures (DECT/PWT, shared sets, and Fax), it is preferable to disablethis option and manage links manually with the Sets => Users command.Refer to the user documentation, Directory - Company tab.
6. Configure Accounting, Traffic analysis, and Reports. Generate a report to verify correctoperation.
7. SCHEDULERBrowse the different tasks listed in the Scheduler and configure their execution:synchronization, alarm clearing, database defragmentation, etc.
8. MAINTENANCE:Configure Maintenance by specifying the archiving operations to be performed. Carefullyspecify the time limit for data storage in order to prevent rapid saturation of server harddisks.
9. SECURITYConfigure each OmniVista 4760 user's rights: in the System directory, enter predefinedgroup members.Enter WEB directory user account passwords for automatic calling and advanced access.Configure a list of users authorized to generate unmasked reports.Set up secure access when configuring the various PCXs.Also configure accounts for client PC users authorized to connect to the server, then addthem to your selected group.Check the sharing and access rights configured in Windows.Compile a list of passwords for the different accounts and send a copy to the client.
10. AS AN OPTION:• Customize Topology.• Configure Alarms by configuring filters for E-mail to be sent automatically when
specific errors are detected.• If Web Directory clients access the server, specify the detailed content of information
to appear in their browser and search criteria.• In the Accounting application, manage tracking and cost profiles and automatic
sending of E-mail when a threshold is reached/exceeded.
Chapter 4
4-2
Note 3:When the PC server is started, all OmniVista 4760 services are launched automatically. It is notnecessary to log on (open a session) or launch a client interface on the server PC to offer ser-vices to client PCs.
11. ARCHIVING important installation data:Use the export feature to back up the following files (preferably to an external device):• The Company directory.• The network branch of the System directory.• Carrier configuration.
4.2 Configuring the PCX OmniPCX 4400/Alcatel-Lucent OmniPCXEnterprise CS
Enable and configure accounting in the PCX configuration:
- in Applications > Accounting, enable the following options:• External accounting: Yes• Internal accounting: No• Record storage: Yes• Accounting files: Yes• Enable filters to select the types of calls for which the PCX must generate records.
- If desired, enable the Accounting record to user node download feature in Installation >Other System Parameters > Accounting parameters.
- Set alarm filter in the PCX configuration: In Application > Incident manager set networkincident filterIt is very important to set alarm filtering: alarm filtering reduces traffic and simplyprocesses.For more information, see Technical Communication: TCV061.
- Enable IP ticket in the PCX configuration: In IP enable option IP ticket : Yes.
4.3 Maintenance
4.3.1 Defragmenting the hard drive
For optimal server operation, it is advisable to schedule monthly defragmentation using theappropriate software for your operating system. OmniVista 4760 services must be suspendedduring this operation.
Caution:
To shut down the OmniVista 4760 server, stop the following services: NMC Service Manager,
NMC50 Database, Sun One Directory Server 5.2 (4760) and the Sun One Administration Server 5.2.
4.3.2 Saving the database
By default, there is no scheduled backup. Only weekly server shutdown (Sunday at 1 am) isplanned to release memory to Windows.
4-3
Backup shuts down services and compresses databases in ACE format. Backup requiresdouble the drive space of that taken up by all databases.Plan to make at least a weekly backup of OmniVista 4760 data and regularly delete oldbackups to avoid using too much drive space.It is advisable to archive backups on an external device.
Note:
Topology backups can be recovered from different 2.1.n releases (versions). However, a topology
backup from release 2.0 (or lower) cannot be recovered.
4.3.3 Defragmenting the databases
Defragmenting the databases recovers the memory space used by the purged data(particularly the space used by the alarm and accounting databases), and optimizes thedirectory database.If OmniVista 4760 databases are large and need frequent purging, schedule regulardefragmentation jobs (for example, once a month). During defragmentation, the OmniVista4760 services shut down and the server cannot be used.For a large (1 GB) database, defragmentation will take approximately two and a half hours.Also schedule a regular check and defragmentation of the hard drive using the appropriateutility. The OmniVista 4760 server must be shut down during this operation.
4.4 Passwords
4.4.1 Overview
During the installation, one single password is configured for all the four administrationaccounts:
- Admin for SunOne Directory server manager
- Directory Manager for SunOne Directory server manager
- AdminNmc for the OmniVista 4760 administrator
- DBA for the database access account
Be careful to keep a record of this password.
Important:
After installation, do not use AdminNmc for day-to-day OmniVista 4760 management. Create addi-
tional administrator or manager accounts to maintain the preferences of the various users and al-
ways maintain a supervisor account in case a password is lost.
4.4.2 Updating Password
Update tools are available through the binary ToolsOmnivista.exe (MS DOS) located into\..\4760\bin directory inside the 4760 installation directory. The update tools includes apassword update tool and an accounting historization clean tool.
To update password:
- In the 4760 \ bin directory, double click on the ToolsOmnivista.exe icon, enter a password
Chapter 4
4-4
for directory manager, then the following windows appears:
Figure 4.2: E:\4760\bin\ToolsOmnivista.exe window
- Select Choice 1 "Password Update"
- Select the password to update (choice 1 to 3)
- Enter the new password twice
- Select 0 to Quit
Note:
In case of scheduled backups using old passwords, they will not operate. Launch or re-schedule backups
using the modified password.
4.5 Special procedures
4.5.1 Modifying an IP address
4.5.1.1 Modification procedure
Changing the IP address requires any DNS servers on the network or client station Host filesto be updated.To modify a server IP address:
- Contact client station users, then shut down the NMC service Manager service.
- Modify the computer's IP address.
- In the directory 4760\data\notify, delete all files except Notify.cfg.
- Restart the server.
4.5.1.2 Adding a new IP address
4-5
In Windows, to avoid modifying a server IP address (for example OmniVista 4760 on aninstallation technician's portable computer), add a second IP address.PCXs can then be configured on the subnet corresponding to this secondary address.
4.5.2 Changing the Apache WEB port number
When installed for the first time, the default port number is 80.
To change the Apache WEB port number, follow this procedure:
1. In the installation directory 4760\data\apache2,• Edit via “notepad” the “httpd.conf” file.
All comments begin with #.• Search for “Listen” and "Servername".• Modify the port number.
Caution:Do not replace this value in comments.
2. In the 4760 installation directory:• Open the “RestoreContext.ini” file.• Replace “svPortApache=80” with the correct port.
3. In the OmniVista 4760 Directory application, click the System tab, then under/nmc/<Server-name>/Servers/<Server-name>/, select Apache, go to the serviceport fieldand replace it with the correct port.
4.5.3 Declaring a mail server
If you have not configured your mail server during installation, you can do it under theAdminNMC account or under another account belonging to the Administrators group:
- Launch the Directory application, then click the System tab.
- Click the item symbolizing the name of the machine in the tree structure. Attributes arelisted in the data field: Load cost center, Serial Number, etc. Indicate the messagesender name and the Mail Server in the respective attributes with the same name. If novalue is entered for the message sender name, OmniVista 4760 application will [email protected] is sent by the OmniVista 4760 server or the client, using the smtp protocol (pleaseremember the smtp authentication is not supported). Mails for Alarm notifications, Trackingnotifications and the scheduled reports are sent by the PC hosting the OmniVista 4760server. When reports are exported through mail in the immediate mode, the mail is sent bythe PC hosting the OmniVista 4760 client.
4.5.4 Changing the paper format and fonts
- Launch the Directory application and click the System tab.
- Click the item symbolizing the name of the machine in the tree structure. The attributes areA4/US, Arial.
4.5.5 Changing PC name or the Windows DNS suffix.
Chapter 4
4-6
This operation is not supported.A possible workaround is to retrieve the old PC's data as follows:
- Export/import from the System and Company directories.
- Retrieve the files present in the directory 4760\data to copy them to the new PC onceOmniVista 4760 has been installed.
4.5.6 Changing the directory root name
All the accounting and alarm data (carrier configurations, etc.) will be lost while performing thisprocedure.
1. Export all data using the “export” tool provided in each application: the directory will beexported in LDIF format, carrier configurations will be exported in “codebook” format.
2. Reinstall the OmniVista 4760 with the new directory root.
3. Using the “replaceldif” tool (see the module Directory - Appendix B: Detailed structure ofthe LDAP directory § ReplaceLdif) then reimport the directory data.
4.5.7 Exceeding capacity
4.5.7.1 Extending the OmniVista 4760 license
The applications available and the maximum number of users allowed in accountingmanagement depend on the license installed on the server.The license is a coded file, nmc.license, located in the %inst%\4760\etc directory, where%inst is the OmniVista 4760 installation directory.If you need to install a new license on the server, follow this procedure:
- Warn clients that the server will be shut down and temporarily unavailable.
- Shut down the NMC service Manager via the 4760 Service Manager utility(Start>Programs>Omnivista4760>Tools> Service Manager) Startup takes a few minutes.
- Check that extensions of known files are not hidden (using display menu from Windowsexplorer).
- Rename the current nmc.license file as nmc.license_old.
- Copy the new license file to the 4760\etc directory. The rights specified in this new file areautomatically granted to the server.
- Restart the machine.
- Inform clients that the OmniVista 4760 server has restarted.
Note:
For the Alcatel-Lucent OmniPCX Enterprise CS, do not forget to copy the license file to the
DHS3data/mao directory for future update.
4.5.7.2 Removing excess users
Via the mgr management tool, remove free sets.
4.6 Remote backup
4-7
4.6.1 Overview
OmniVista 4760 has a remote backup feature that allows server or OmniPCX 4400 data to bearchived on a remote station.A remote station may be used to store temporary files during defragmentation operations.
ExecdEx: program used for database defragmentation.SaveRestore: program used to save and restore PCX data.
4.6.2 Restrictions
Both PCs must belong to the same NT domain. The "owner" of the save/backup task must becorrectly identified (name and permanently valid password).
4.6.3 Configuration - 2 PCs in a domain
Configuration: PC1 and PC2 belong to the same domain. PC1 RemUser uses the resourcesof the PC2 remote station for maintenance operations.
1. On the server station, PC1, launch the System Directory and go to the ExecdEx andSaveRestore fields located under /nmc/<Server-name>/Servers/<Server-name>/.
2. Select the NT account tab and enter the user name and password (RemUser for example)to launch save/backup to PC2. Name must be entered as <domain\name>.
3. On PC2, select the desired target directory by modifying the sharing rights: give write rights(full control) to the user RemUser.
4. In maintenance, select Preferences > Maintenance > Configuration. A configurationwindow is displayed.
5. Depending on your requirements, specify the directories on PC2 to be assigned for:• A4400 save and restore• A4760 save and restore• Temporary filesNetwork drives and shared directories are available in the browser window.
6. On PC1, run the user manager and add the user RemUser as a member of the PC1station administrator group. The password assigned to RemUser must be identical to thatentered in the System Directory.This user must also have local "administrator" rights on the OmniVista 4760 server.
4.6.4 Configuration - 2 PCs in the same Workgroup
Configuration: PC1 and PC2 belong to the same Workgroup. PC1 RemUser uses theresources of the PC2 remote station for maintenance operations.
Note:
On PC2 RemUser must have the right: "Access this computer from the network".
1. On stations PC1 and PC2, declare the same user, RemUser, with the same password(with permanent validity). On PC1, grant "Administrator" rights to RemUser.
2. On PC2, select the desired target directory by modifying sharing rights: give write rights
Chapter 4
4-8
(full control) to the user RemUser.
3. On the server station, PC1, launch the System Directory and go to the ExecdEx andSaveRestore fields located under /nmc/<Server-name>/Servers/<Server-name>/.
4. Select the NT account tab and enter the user name and password (RemUser for example)to launch save/backup to PC2. Name must be entered as <.\name>.
5. In PC1 maintenance, select Preferences > Maintenance > Configuration. A window isdisplayed.
6. Depending on your requirements, specify the directories on PC2 to be assigned for:• A4400 save and restore• A4760 save and restore• Temporary filesNetwork drives and shared directories are available in the browser window.
When save/restore operations are performed manually, the browser window is also displayed.
4-9
Chapter 4
4-10
5.1 Operations
This chapter describes the procedures to verify that the OmniVista 4760 and its applicationsare correctly installed.
1. Ensure all the OmniVista 4760 services such as the LDAP server, Sybase server, 4760server Service manager, web server are stared.
2. Start the OmniVista 4760 client and logon as an administrator. Check for the list ofavailable applications from Help> About. Verify the presence of these applications in theicon bar. Launch each application and perform a general check by opening the treestructure, performing search operation and displaying the grid. Also check the OmniVista4760 help.
Note:Perform these checks from a remote client PC and also through the web login.
3. For each OmniVista 4760 logon, check:• That it connects correctly.• That it has authorized models at access security level.
4. At System directory level, check that all the phone sets (extensions) have been correctlydownloaded by a complete synchronization.
5. If the Company directory is used, check the following:• The Primary station field is completed for persons with a directory entry and station
on the PCX.• That there are no homonyms (detected by the Alarms module).• That it is possible to connect to the Company directory and make an automatic call
using an Internet browser. If there is a malfunction, check user UIDs and the station'sSTAP attribute (authorized, off hook, forbidden).
6. For each PCX, check Telnet launch and access to the configuration.
7. Accounting: Check that records are transmitted to the Organization, then generate anAccounting report.
8. Traffic analysis: Generate a Traffic analysis report.
9. Alarms: For each PCX, check that alarms are reported and that events are reported ifsynchronization (4400 to the 47xx) is selected on the PCX side.
10. Topology: Check that the topology of the PCX network is reported.
11. Scheduler: Check for the status of the tasks scheduled by default and the tasks scheduledby the administrator. The Database and the PCX backup must be scheduled.
12. Maintenance• From the Maintenance application, run the immediate backup task. It will download
the immediate backup from the PCX to the OmniVista 4760.A backup operation must first be performed using Swinst from the OmniPCX 4400 /Alcatel-Lucent OmniPCX Enterprise CS.
• Perform an OmniVista 4760 backup operation.
13. Licence: Open the menu Help> About. Check if the declaration node has been found and
5
5-1
that you do not manage more users than your license permits. Identify the reference PCX.
14. Check that audit records are displayed after synchronization of Alcatel-Lucent OmniPCXEnterprise CS Version: F5.401.14 (With Audit Global flag & Audit Process flag enabled forthat Alcatel-Lucent OmniPCX Enterprise CS).
Chapter 5
5-2
6.1 Automatic Uninstall
The server module must be uninstalled using a local administrator account.
Note 1:
The DMS Server package should only be uninstalled after the uninstallation of OmniVista 4760 Server
To uninstall the OmniVista 4760 server:
1. Close all the OmniVista 4760 client applications. The SNMP and/or Compaq manufacturerservices must not be enabled during the uninstall phases.
2. Use the Add/remove programs interface in the Control panel. Select the OmniVista4760 Server program and click Remove.The uninstall procedure spends several minutes.The SunOne Directory server and the SQL Anywhere Studio 10 software are also beremoved.
Note 2:The Java Runtime Environment remains installed.
3. Restart the computer to complete the uninstallation procedure.
6.2 Automatic Uninstall with Traces
The command:
MsiExec.exe /X{C3CF0589-B127-4C15-A347-E0DCCBC74E87} /L*v"%TEMP%\OmniVista4760_uninstall.log"
allows to uninstall the server and the uninstall process traces are recorded in the file:OmniVista4760_uninstall.log.
This file is a text file and can be edited.
6.3 Manual Uninstall
If OmniVista 4760 Server cannot be removed from Add/Remove program, you should carryout a manual uninstallation of various components.
This process must be applied when Windows Installer is not able to restore the initial state ofthe PC after an incident during the installation or upgrade.
It must also be applied if the automatic uninstallation fails.
Note:
As this process involves the registry, it is important to perform before a system backup for a possible fu-
ture restore.
1. From Add/Remove program, remove, if necessary, the viewable programs (DirectoryServer and SQL Anywhere Studio 10 – Software)
2. Remove the windows\system32\productregistry fileThis file may prevent the re-installation of Ldap Sun One server on the same path as the
6
6-1
previous installation.
3. From the uninstall tool.zip, available with the Technical Communication TC1007,copy the PsExec directory in C:\Program Files
4. Execute the reg_del.bat commandThis command opens the registry editor.
5. Import the del_regkeys_TS.reg file
6. Reboot the PC
7. Remove the folders where are installed the various components of the system: 4760server, Sybase, Netscape, SQL database
Chapter 6
6-2
7.1 Administration client PC requirements
Hardware and software requirements are shown in the following table.
table 7.1: Administration client PC hardware and software requirementsOperating System Windows 2003 Server SP2
Windows XP Pro SP3Windows Vista
Processor Pentium III 1.4 GHz
RAM 1 GB
Hard drive 40 GB
Graphics board 4 MB video memory with a resolution of 1024x768, 16 millioncolors
Monitor 17 inches (19 inches recommended)
Internet browser Internet Explorer (version 7.x)Mozilla FireFox 2.0
You must know:
- The port number dedicated to LDAP (389 by default).
- The port number dedicated to LDAPS (636 by default).
- The IP address or name of servers on the network.If required, contact the company network administrator to obtain this information.
The OmniVista 4760 InstallShield Wizard installs the JAVA Runtime Environment (JRE) if it isnot detected as being installed on the PC. You can install the JRE before installing the client.See the module Installation - Installing the Java Runtime Environment .
7.2 Web directory client PC, required configuration
The table below presents the minimum configuration required.
table 7.2: Web directory client PC requirementsOperating System Windows 2003 Server SP2
Windows XP Pro SP3Windows 2003 R2Windows Vista
Internet browser Internet Explorer 7Mozilla Firefox 2.0
7.3 Connections
Check the connections between the client PC and the server PC:In a DOS command window on the client PC:
7
7-1
- ping <server_name>
- ping <server_name>.<server_DNS_suffix_name>
Note:
If a connection fails, ask your network administrator to update DNS management or complete the host
file: (winnt\system32\drivers\etc) with IP_address_PC_name_PC_name.DNS_suffix_name
For example: 192.166.123.156 OmniVista OmniVista.alcatel.fr.In a DOS command window on the server PC:
- ping <@IP>
- ping <.@IP><client_DNS_suffix_name>
Take care to allow incoming TCP IP connection on client PC on the port used by corba :30500-30509: otherwise configuration and alarms will fails to operate
Chapter 7
7-2
8.1 Running the OmniVista 4760 InstallShield Wizard for the client
To install the OmniVista 4760 client, use the following procedure. The InstallShield Wizard willpresent you with a series of dialog boxes. You can click Cancel at any time to cancel theinstallation.
1. There are two ways to start the OmniVista 4760 client installation program.• If you have the OmniVista 4760 DVD-ROM, insert the DVD-ROM in the drive.
Double-click ClientSetup.exe.• If you have already installed the server, you can download the OmniVista 4760 client
installation program using the URL:http://servername/cgi-bin/OmniVista4760Client.exe (replace "servername" by the nameof your OmniVista 4760 server).Double-click OmniVista4760Client.exe.
The Choose Setup Language dialog box appears.
Figure 8.1: Choose Setup Language dialog box
2. Select the language for the installation and click OK. If the Java Runtime Environment(JRE) is not installed on the PC, the InstallShield Wizard will propose to install it anddisplay the following dialog box.
8
8-1
3. Click OK to install the JRE.
Note 1:If the JRE is already installed on the PC, the installation procedure skips to the dialog box displayedin step 5.You will be asked to accept the JRE license agreement.
Chapter 8
8-2
Figure 8.3: JRE license agreement
4. Select Typical setup and click Accept. The JRE installation proceeds, and displays thefollowing dialog box when the installation is completed.
8-3
Figure 8.4: JRE Installation Completion dialog box
5. Click Finish. The OmniVista 4760 InstallShield Wizard welcome dialog box appears.You will be asked to wait while the wizard prepares for the installation.
Chapter 8
8-4
Figure 8.5: OmniVista 4760 InstallShield Wizard welcome dialog box
6. When the Wizard is ready, the Next button will become active. Click Next. You will beasked to accept the OmniVista 4760 license agreement.
8-5
Figure 8.6: OmniVista 4760 license agreement
7. Once you have read the license agreement, select I accept and click Next. TheDestination Folder dialog box appears.
Chapter 8
8-6
Figure 8.7: Destination Folder dialog box
8. The default installation directory is C:\ 4760. To modify the default directory, click Changeto select another location. Once you have selected the directory, click Next. The Ready toInstall the Program dialog box appears.
8-7
Figure 8.8: Ready to Install the Program dialog box
Note 2:Select an empty folder to install the client. The client uninstall operation deletes all files of this folder.
9. The Wizard is now ready to install the OmniVista 4760 client based on the informationentered. To proceed with the installation, click Install.When the Wizard has finished installing, the InstallShield Wizard Completed dialog boxappears. To exit the Wizard, click Finish.
8.2 Multiple Version Installation
As of R5.0, it is possible to install several versions of the OmniVista 4760 client on the samestation. Multiple versions allow the user to connect to OmniVista 4760 servers in differentversions.
Example 1:
The user of a client station supporting a 4.x version and a 5.x version can connect simultaneously to 5.x
servers or 4.x servers.
When a client already exists on the station, installing another client results in:
- A software update, if the existing version and the installing version have the same majorversion and minor version
Chapter 8
8-8
Example 2:Installing a 5.0.05, client when a 5.0.01 client already exists, updates of the existing client.
- A multiple version installation, if the existing version and the installing version have adifferent major and/or minor versions
Example 3:Installing a 5.0.01 client, when a 4.2.00 client already exists, results in the two clients being opera-tional.
OmniVista 4760 client versions are installed in separated folders.
8.3 Starting the application for the first time
Check the DNS configuration or IP address - Complete computer name added in the hostsfile (...\etc\hosts).
Check your Windows account has authorized access to write data underC:\4760Client\lib\ext folder.
Connect to a server via the graphical interface of the OmniVista 4760 Client module. Run thecommand Start > Programs > OmniVista4760 > OmniVista4760 Client.
- A server name is specified during installation of the client module. The network isscanned to locate it.• If the server is located, a connection window is displayed. You must enter the name
and password of an authenticated (valid) account in the Company directory serverand confirm. If information is verified, the available OmniVista 4760 server applications(according to account rights) are displayed. If the information is not verified, an errorwindow is displayed.
• If the server is not found on the network, a warning message box is displayed askingyou to reenter the data.
- No server name was specified during installation. An empty connection window isdisplayed. Specify the Server name of the server to which you want to connect and thename and password of an account authenticated in the Company directory of this server,then confirm. The network is scanned to locate this server.• If the server is located and the account is verified, the available OmniVista 4760 server
applications (according to account rights) are displayed.• If the server is not located or the account is incorrect, a warning message box is
displayed asking you to re-enter the data.
Note:By default, at subsequent logout, the server entered during your initial connection will be offered.
To launch an application, click the associated icon located in the application toolbar.Please refer to the documentation on the OmniVista 4760 interface.
8-9
Chapter 8
8-10
Inform all the OmniVista 4760 client PC users, before removing the OmniVista 4760 clientprogram.To uninstall the OmniVista 4760 client:
1. Use the Add/remove programs interface in the Control panel. Select the OmniVista 4760client program of the desired version and click Remove. The uninstall procedure takesseveral minutes.
Note 2:The Java Runtime Environment remains installed.
2. Restart the computer to complete the uninstallation
Caution:
If uninstall is not performed correctly, delete the keys in the Windows registry:
- Click Start> Execute.
- Open the registry editor via the "regedit" command and delete the keys containing the follow-ing code:
• {F58CB02E-71DF-46A1-B9BB-FE4270F2F25E}
• E20BC85FFD171A649BBBEF24072F2FE5These keys are concerned with the installer program. You can check that you have theproduct name as OmniVista 4760.
9
9-1
Chapter 9
9-2
10.1 Software and hardware requirements
The table below presents the required configuration.
table 10.1: Requirements for accessing via a browserOperating System Windows 2003 Server SP2
Windows XP Pro SP3Windows 2003 R2Windows Vista
Internet browser Internet Explorer (version 7.x)Mozilla FireFox 2.0
10.2 Installing the Java Runtime Environment
You must install the JRE (Java Runtime Environment), a Java Plug-in, on the computer.Installation may be performed, either:
- locally using the DVD-ROM (see the module Installation - Installing the Java RuntimeEnvironment ),
- or, remotely via the Web home page of the server See § Installing and initializing JRE via abrowser .
10.3 Network requirements
Check the IP addressing of computers on the network via any DHCP, DNS and WINS servers.Also check that computer IP addresses and computer names match in the file:...\system32\drivers\etc\hosts.
You must select "Accept all cookies" in the browser's security settings.
10.4 Installing and initializing JRE via a browser
10.4.1 Configuring the Internet browser
Browser security settings must be configured to enable cookies to be stored. To do this:
- In Internet Explorer 7:• Select the menu Tools > Internet options > Privacy tab.• Click the Sites... button• In the field Address of Web site: enter the IP address of the OmniVista 4760 server• Click the Allow button
- In Firefox• Select the menu Tools > Options > Privacy.• In the "Cookies" box, select Accept cookies from sites
10
10-1
The Java plug-in (JRE) must be installed before initial use of the OmniVista 4760. Forsecurity, this plug-in must be initialized each time it is used on a new server.
10.4.2 Installation
1. Launch the browser and enter the server address. The home page is displayed. You canselect the appropriate language from the list (1).Bookmark the page.
Figure 10.1: OmniVista 4760 home page
2. Click the link located to the left of the window (2). The window is immediately updated andtwo shortcuts are displayed.
3. To install JRE, click the first shortcut displayed in the left panel. The installation begins andfiles are downloaded to the client station. Setup continues in the same way as whenperformed from the DVD-ROM. See the module Installation - Installing the Java RuntimeEnvironment .
4. Restart the computer for Java plug-in setup to take effect. Then, launch the browser againand enter the server address to access the home page.
10.4.3 Initializing
You must initialize the Java Plug-in when connecting for the first time to the OmniVista 4760server. Without this initialization, attempts to access the new server fail.
Chapter 10
10-2
1. Launch the browser and enter the server address. The home page is displayed.
2. Click the link located to the left of the window. The window is immediately updated and twoshortcuts are displayed.
3. To initialize the JRE, click the second shortcut (3). Data is transferred from the server tothe client PC, then a window is displayed to confirm initialization.
4. Confirm that the Java plug-in has been updated. To access the applications offered by thenew server, click Network administration on the home page.
Note:
In case of Windows XP SP3 or Windows 2003 SP2 operating system with activated firewall, open ports
"CORBA notifications receipt" (30500-30509) in the firewall.
10.4.4 Loading problems
The Java plug-in cannot be loaded via the server home page (Error 400), serverName_Server cannot be contacted. There are two possible causes:
- The client station and/or server station are not correctly connected to the network.
- IP addressing is not correct. Contact your network administrator.
If, from the client PC, the Ping command PC_name_Server.DNS_suffix_name fails, check thehosts file or DNS server addresses.If the Hosts file is used (without DNS), it should include a line of the following type:IP_address_server_name server_name.server_DNS_suffix. For example:192.168.3.121 Server Server.alcatel.fr
10-3
Chapter 10
10-4
11.1 Installing the Java Runtime Environment (JRE)
The OmniVista 4760 application uses version 1.6 of the Java Runtime Environment.
The Java Runtime Environment (JRE) is available on the OmniVista 4760 DVD-ROM. It isautomatically installed when version 1.6 of the JRE is not detected on the computer. It mustbe installed before installing the client or server module.The installation procedure is as follows:
1. Check that no JRE is installed (via the control panel). Otherwise, if the icon is present,click Add/remove programs. Select Java 2 Runtime Environment from the list ofinstalled applications, then click Add/Remove to remove the application.
2. Launch Windows Explorer.
3. Access the DVD-ROM.
4. Double-click \setup\ISSetupPrerequisites\Java(TM) 2 Runtime Environment, StandardEdition\jre-6u11-windows-i586-p-s.exe to launch the installation.The message “Are you ready to install JRE 1.6?” is displayed.Confirm.
5. The Software License Agreement window is displayed. Read the license agreement, thenclick Next.
6. At the end of setup, no reboot is required.
Note:Sometimes a warning window can appear, prompting you to restart the computer "now or later". Se-lect restart "later".
7. To check you have version 1.6 of the application, click the Java Plug-in icon displayed inthe control panel: .
8. On this Java Plug-in control panel remove Automatic Update.
11.2 Configuring the Java plug-in
Disable the automatic JRE updates:
1. Open the Control Panel
2. Open the Java Control Panel
3. Select the Update tab
4. Devalidate the Update Automatic Detection check box
In Java plug-in standard properties, the Enable Java plug-in option must be selected.If you access an OmniVista 4760 server via a browser:
1. As of R5.1, disable the next generation Java Plug-in:a. Open the Control Panel
11
11-1
b. Open the Java Control Panelc. Select the Advanced tabd. Expand the Java Plug-ine. Disable the Enable the next-generation Java Plug-in (requires to re-start the
browser)
2. It is recommended to enable the cache memory before accessing the server again; thisspeeds up access times:a. Open the Control Panelb. Open the Java Control Panelc. Select the General tabd. Go to the Temporary Internet File sectione. Click on the Parameter buttonf. Validate Store Temporary Files on my Computer check box
3. If a Proxy server is mandatory for a Web connection to the server OmniVista 4760:a. Open the Control Panelb. Open the Java Control Panelc. Select the General tabd. Go to the Network Parameters sectione. Click on the Network Parameters button to open the Network Parameters windowf. Click on the Direct Connection radio buttonAs a result, the OmniVista 4760 client applet will not attempt to use the proxy server whena 4760 module is launched. The applet will directly contact a module.
4. Java applications require a minimum screen configuration of 16 million colors (32-bitmode).
Chapter 11
11-2
This section describes the possible connectivity between the OmniVista 4760 server and thethree PCXs to which it can be connected, OmniPCX 4400, Alcatel-Lucent OmniPCXEnterprise CS or OmniPCX Office.
The default connectivity on the PCX is Ethernet (LAN). Configuration is described in:Section 1 § Ethernet (LAN) connectivity
Defining connectivity for OmniPCX 4400 and Alcatel-Lucent OmniPCX Enterprise CS isdescribed in:Section 2 § OmniPCX 4400 \ Alcatel-Lucent OmniPCX Enterprise CS :
- Section 2.1 § Configuring PPP connectivity on the OmniVista 4760 server :• Section 2.1.1 § Installing and configuring the MOXA unit (optional)• Section 2.1.2 § Installing a modem or TA in Windows 2000/2003• Section 2.1.3 § Declaring the modem pool on the OmniVista 4760• Section 2.1.4 § Declaring a PPP connection with a PCX on the OmniVista 4760
- Section 2.2 § Declaring an OmniPCX 4400/Alcatel-Lucent OmniPCX Enterprise CS in PPPmode (on the PCX side) :• Section 2.2.1 § V24 Ports Configuration (1)• Section 2.2.2 § Serial Link Configuration
- Section 2.3 § Configuring modems with or without RMA
- Section 2.4 § Configuring TAs with or without RMA
- Section 2.5 § Configuring the RMA unit
- Section 2.6 § Configuring the e-RMA unit (1)
- Section 2.7 § IP/X25 connectivity (Alcatel-Lucent OmniPCX Enterprise CS/OmniPCX4400) :• Section 2.7.1 § Configuration on the OmniVista 4760 server• Section 2.7.2 § Configuration on the PCX
- Section 2.8 § Useful information (Alcatel-Lucent OmniPCX Enterprise CS/OmniPCX 4400):• Section 2.8.1 § Finding a PCX's IP address• Section 2.8.2 § Finding the Network node number of a PCX
- Section 2.9 § Configuring RMA alarms :• Section 2.9.1 § Adding a modem in Windows.• Section 2.9.2 § Declaring a pool of modems on the OmniVista 4760• Section 2.9.3 § Setting attributes for the PCX in the System directory• Section 2.9.4 § Configuring modems and TAs• Section 2.9.5 § Configuring RMA alarms on the PCX (1)
Defining connectivity for OmniPCX Office is described in:Section 3 § OmniPCX Office :
- Section 3.1 § Declaring a modem on a PC hosting OmniVista 4760 server
- Section 3.2 § Declaring an OmniPCX Office in PPP mode on the OmniVista 4760
12
12-1
- Section 3.3 § Declaring an OmniPCX Office in PPP mode (on the PCX side)
- Section 3.4 § Urgent alarm management on PPP connectivity :• Section 3.4.1 § Activating routing and remote access (RAS) in Windows• Section 3.4.2 § Configuring the RAS server in Windows• Section 3.4.3 § Creating a PPP client account in Windows• Section 3.4.4 § Assigning user rights for the PPP client in Windows• Section 3.4.5 § Management on the OmniPCX Office• Section 3.4.6 § Setting Parameters for the PCX in OmniVista 4760 server
- Section 3.5 § Urgent alarm management on Ethernet connectivity
- Section 3.6 § Useful information for the OmniPCX Office• Section 3.6.1 § Notes on installing OMC• Section 3.6.2 § Accounting management using OMC• Section 3.6.3 § Synchronizing sets and alarms
DIVA Board connectivity is described in:Section 4 § Diva Board connectivity
Caution:
The minimum releases of the OmniPCX 4400 \ Alcatel-Lucent OmniPCX Enterprise CS required for
PPP connectivity are:
- E2.504.1 ai
- F1.603.1
- F2.502.12
- F3.301.316
12.1 Ethernet (LAN) connectivity
This is the simplest type of connection to install.
To configure Ethernet connectivity on the OmniVista 4760:
1. Launch the Directory application, then click the System tab.
2. Create the Network and Subnetwork.
3. Create the new PCX and update the following attributes in the PCX tab:• Name• Node Number (For help finding the network node number of an OmniPCX 4400 or
Alcatel-Lucent OmniPCX Enterprise CS, see section 2.8.2 § Finding the Network nodenumber of a PCX
• IP address: With or without duplicated CPU specify the role main IP address. In caseof spatial redundancy (requires Alcatel-Lucent OmniPCX Enterprise CS 6.1 minimum)you must enter both the main IP addresses corresponding to the CPUs: right click onthe field Add value to enter the second IP address.
Note 1:For OXE configuration, refer to TC0423 OXE Technical Communication.
• FTP Username and FTP Password
Chapter 12
12-2
Note 2:Default password:
• for OmniPCX 4400 and Alcatel-Lucent OmniPCX Enterprise CS password is: adfexc
• for OmniPCX Office password is: tuxalize
4. Click the Connectivity tab and select LAN as Connection Type.
12.2 OmniPCX 4400 \ Alcatel-Lucent OmniPCX Enterprise CS
12.2.1 Configuring PPP connectivity on the OmniVista 4760 server
Configuration is performed in several steps:
- Extend the V24 ports via MOXA unit (optional) (see Technical Communication TCV 049).
- Install the modem in Windows 2000/2003.
- Declare the modem pool on the OmniVista 4760.
- Declare a PPP connection with a PCX on the OmniVista 4760.
The solution made of a Diva Board which can be installed on the OmniVista 4760 server andthe ISDN router in the Alcatel-Lucent OmniPCX Enterprise CS is also available and isdescribed in the section 4 § Diva Board connectivity .
12.2.1.1 Installing and configuring the MOXA unit (optional)
Analog modems are of MultiTech type MT56000ZDXe and MT5634ZBA. Modems can beremote on the LAN via MOXA units. The latter allow PCs running Windows to control multipleV24 serial ports via the LAN.
Figure 12.1: PPP modem on MOXA unit
Declaring the unit
Unit version must be 1.5.18.0.
1. Connect the modem.
2. Power up the modem on one of the ports (P1 to P4).
3. Open the Control panel and double click Add/Remove Hardware, the Wizard islaunched. Click Next.
4. Check (select) Add/Troubleshoot a device, then click Next, the Wizard starts newhardware detection.
12-3
5. In the Choose a hardware device window, select Add a new device, then click Next.
6. In the Find New Hardware window, check (select) No, I want to select the hardwarefrom a list, then click Next.
7. Select Multiport serial adapters, then click Next.
8. In the Manufacturers window, select Moxa Technologies Co.Ltd..
9. Click Have a disk and browse to the file “/nport.inf“
10. Click Open, then OK.
11. In the Models window, select MOXA Nport server Lite DE-304, then click Next twice.
12. Continue installation after acknowledging that the digital signature has not been found.
At this stage, the IP address of the unit must be manually entered, even if the address listed iscorrect.
Note:
The IP address can be previously modified using the keys on the unit or via Telnet through a crossed
Ethernet cable in the case of direct connection. When unit installation is complete, the plug and play mo-
dem will be detected automatically.
Caution:
- As the unit has been installed with an IP address, do not modify it later because Windows willcontinue to search for the device at its initial IP address.
- Do not install the Moxa unit on another PC to use the other free COM ports.
- DHCP must be disabled.
- It is recommended to declare the Moxa unit in the same subnetwork as the 4760 server.
Checking the Moxa unit, the modem, and the COM ports
In the peripheral device manager, the MOXA unit and the COM ports are listed as follows:
- Multiport serial adapters: MOXA Nport Server Lite DE-304• In Properties, click the Driver tab and check driver version: 1.5.18.0.
- Modems: MultiTechIn Properties, the COM3 port is selected if:• The modem is connected on P1.• And the two ports COM1 & 2 are native to the PC.
- Ports (COM and LPT):• MOXA Communication Port 1 (COM3)• MOXA Communication Port 2 (COM4)• …• Communication port (COM1)• Communication port (COM2)
12.2.1.2 Installing a modem or TA in Windows 2000/2003
Installation is transparent for a TA or Plug&Play modem.
The installation procedure for a TA or non Plug&Play modem is as follows:
Chapter 12
12-4
- Open the control panel and click the Modem and phone options icon.
- In the Modem tab, click Add, then Next. The system searches for connected modems. Ifautomatic detection fails, select the model from the list. For a TA, select Alcatel, 4400Terminal Adapter.
- Specify the port used, then click Next.
- Click Finish to declare the modem.
- The Properties tab is used to modify call parameters.
- Test the modem via the Diagnostics tabs by selecting Test modem. The modem shouldrespond to the test commands.
- Click OK to confirm modem declaration.
12.2.1.3 Declaring the modem pool on the OmniVista 4760
After installing the modem, you must configure the OmniVista 4760 server to declare theprotocol and modem used.
To initialize the pool of modems:
1. Start OmniVista 4760 and run the Directory application. Click the System tab.
2. Browse the tree structure to the "Host server name" > Servers > "Host server name"branch.
Figure 12.2: Creating the pool of modems
3. On the server name, select the Create > Modem Pool command from the shortcut menu.An entry is created.
4. Update the fields of this new pool:• Name: Name the modem pool.
12-5
• Description: Enter a description for the pool (optional).• Type: Choose the modem type:
• PSTN Modems• ISDN Modems
• Usage:• Dial out• RMA alarms• PPP dial in• Dial out and RMA alarms• Dial out and PPP dial in
• Omnivista 4760 Phone Number (used only for OmniPCX Office urgent alarms).• Port name(s): List of ports which are managed by this pool. All the ports declared are
connected to the same type of modem ISDN or PSTN. To add a port right click on thefield Add value.
12.2.1.4 Declaring a PPP connection with a PCX on the OmniVista 4760
To declare a PPP connection with a PCX, on the OmniVista 4760:
1. Run the Directory application, then click the System tab.
2. Create the Network and Subnetwork, if required.
3. Create the new PCX and update the following attributes in the PCX tab:• Name• Node Number. (For help finding the network node number of an OmniPCX 4400 or
Alcatel-Lucent OmniPCX Enterprise CS, see section 2.8.2 § Finding the Network nodenumber of a PCX
• IP address. The local address assigned by the PCX.
4. Click the Connectivity tab and update the following attributes:• FTP Username and FTP Password• Connection type. Choose from:
• PPP• RMA access (PPP link via RMA)• eRMA access (PPP link via eRMA - Alcatel-Lucent OmniPCX Enterprise CS)
• Timeout (PPP). Default is 360 seconds.• Phone number (PPP). this is the phone number to call the modem or remote TA or
IO2/OBCA port, or GD board for e-RMA.• PPP Account Password (ppp by default).• Authentication CHAP Logon (PPP) and Authentication CHAP Password (PPP). If
CHAP is installed on the OmniPCX 4400/Alcatel-Lucent OmniPCX Enterprise CS,password for CHAP authentication account.
• RMA Login (PPP) and RMA Password (PPP) must be entered if an RMA or e-RMAaccess is used.
• RMA Port (PPP). If an RMA access is used, select the port to be connected to the portof the modem on the RMA. This port must be physically connected by the 3BA28153AAA cable to the port on which the PPP access of the PCX is configured.
• Modem Pool DN (PPP). Select the number of the pool to be used to make the call. By
Chapter 12
12-6
clicking the button located to the right of the field, you can search for the pool bybrowsing through the System directory.
Note:CHAP allows the PPP link on the PCX to be secured. The PCX is viewed as the PPP server andthe OmniVista 4760 is viewed as the client. Password declaration on PPP clients and serversmust be consistent to ensure calls are allowed. See the CHAP authentication paragraph in sec-tion 2.2.2 § Serial Link Configuration )
Figure 12.3: PPP settings
12.2.2 Declaring an OmniPCX 4400/Alcatel-Lucent OmniPCX Enterprise CS inPPP mode (on the PCX side)
The list of operations to be performed to configure PPP connectivity on the PCX is describedin the following paragraphs.
12.2.2.1 V24 Ports Configuration (1)
1. Connect to the PCX via the Telnet utility, then identify yourself with a user account such asmtcl.
2. Run mgr. The main configuration menu is displayed.
3. Select the Installation item and move down the hierarchy. A submenu is displayed.
4. Select V24 ports, then select a complete display of information. Available ports aredisplayed in the form:[ 2 ] Instances: V24 port— /dev/scc0a Port C.— /dev/io2tty (IO2 and OBCA).— /dev/scc1a Port D.
12-7
—/dev/ e-rma– — — — —
5. Edit, then update the characteristics of the port dedicated to PPP communication:Port No.:RTS/CTS protocol + FalseDynamic + FalseTA directory No.: – —Speed + 19200 b/sParity + noData bits + 8 bitsStop bit + 1 bitTerminal type +VT100V24 Application + LoginSettings: –Port Dir. No. (Static): this is the directory number dialed by the remote TA.
6. Exit the mgr utility
(1): V24 ports configuration can also be performed through 4760i tool.
12.2.2.2 Serial Link Configuration
1. Access the Alcatel 4400 IP Network Administration menu by entering netadmin -m.
Note 1:If you want to add CHAP authentication to the connection, add it now. See CHAP authenticationparagraph below.
2. Select 6 Serial links (SLIP/PPP).
3. Select 2 Add, to add your new connection, then answer the following questions onsettings:• Which link do you want to add, an SLIP(s) link or PPP(p) link? : p• Which device do you want to use for this connection (e.g /dev/tty1a 'q' to cancel)? :
Enter:• /dev/scc0a for a connection via port C• dev/scc1a for port D• /devttyi02 for IO2 and OBCA• /dev/e-rma for e-RMA
Note 2:The complete list of ports is accessible in the Installation > V24 Ports > Port list section inMGR. If you connect to a modem, you must specify the device with a capital letter at the end ofthe field as follows: dev/scc1A
• Speed (default is 19200)?• Do you use a modem (y/n)? : y or n depending on the configuration. Enter y for
e-RMA.• Compression (default is y)? : y (this is header compression)• Inactivity timeout in seconds, 'n' for no timeout (default is 600): 600. If you want to use
authentication, you must add a CHAP configuration first.
Chapter 12
12-8
CHAP authentication: To secure the PPP connection, you can add CHAP authentication. Todo this:This requires you to configure the list of accounts in item 11. Security, accessed viathe netadmin -m command (this can be only accessed from the root account)
1. Access the Alcatel 4400 IP Network Administration menu by entering netadmin -m
2. Select 11 Secruity to configure the list of accounts.
3. Select 4: CHAP configuration.
4. Select 2 Add/update.
5. Enter the client name: client.
6. Enter the password: secret.The client is added. The CHAP configuration menu is displayed again.
7. Select 1 to display the complete list of configured clients.
12.2.3 Configuring modems with or without RMA
table 12.1: Configuration for Multi-Tech MT5600ZDXe and MT5634ZBA modems
On the OmniVista 4760 side On the OmniPCX 4400side Comments
AT&F0 AT&F0 Load the factory configuration
AT$SB19200 AT$SB19200 Speed 19200 bauds on theserial port
AT&K3 with RMA AT&K3 RTS/CTS flow control
AT&K3 without RMA AT&K4 RTS/CTS flow control orXON/XOFF
AT&D0 DTR signal ignored
ATM0 ATM0 Speaker disabled
ATS0=2 Number of rings before pick-ing up
ATS6=6 Delay time before dialing (insec.)
ATS11=70 Duration of idle and tone
ATS30=0 Inactivity timeout disabled
ATQ1 Responses disabled
ATE0 ATE0 Character echo disabled
AT&W0 AT&W0 Save the configuration
12.2.4 Configuring TAs with or without RMA
table 12.2: TA configurationOn the OmniVista 4760 side On the OmniPCX 4400 side
Public Network Access Class of Ser-vice: 2
Public Network Access Class of Service:Justified
12-9
1 For an IO2 type link, adapter type must be "V110 + V120 asynchronous" with "V120"protocol.
On the OmniVista 4760 side On the OmniPCX 4400 side
Accounting Class of Service: Justi-fied
Accounting Class of Service: Justified
Connection Class of Service ID: 0 Connection Class of Service ID: 0
Cost center No.: 255 Cost center No.: 255
B Channel: 2 B Channel: 2
DATA Group directory No.: - - - DATA Group directory No.: - - -
ISDN Teleservice: Non-standard Ap-plication
ISDN Teleservice: Non-standard Applica-tion
Adapter type 1 : V110 + V120 asyn-chronous or V110 (depending on thebox used)
Adapter type 1 : V110 + V120 asynchronousor V110 (depending on the box used)
Type of terminal: VT100 Type of terminal: VT100
Use: Hayes Use: Set (no emulation)
Setup No.: 3 Setup No.: 3
Flow control No.: 1 Flow control No.: 1
Output configuration No.: 1 Output configuration No.: 1
Input configuration No.: 1 Input configuration No.: 1
V120 No.: 0 V120 No.: 0
1
table 12.3: V24 configurationOn the OmniVista 4760 side On the OmniPCX 4400 side
Transparent V24: No Transparent V24: No
Off-hook by 108: No Off-hook by 108: No
Off-hook by 105: No Off-hook by 105: No
On-hook by 108: Yes On-hook by 108: No
On-hook by 105: No On-hook by 105: No
108 obs timeout: No 108 obs timeout: No
105 obs timeout: No 105 obs timeout: No
Observation125: No Observation125: No
Intervention125: No Intervention125: No
Fast IO: Yes Fast IO: Yes
Observation 108: No Observation 108: No
Observation 105: No Observation 105: No
Response by 108: No Response by 108: No
Chapter 12
12-10
2 For an IO2 type link, adapter type must be "V110 + V120 asynchronous" with "V120"protocol.
On the OmniVista 4760 side On the OmniPCX 4400 side
Response by 105: No Response by 105: No
UA set automatic answer: NoWith RMA
UA set automatic answer: No
UA set automatic answer: NoWithout RMA
UA set automatic answer: Yes
Semi-permanent: No Semi-permanent: No
Adaptation protocol 2 : V110 or V120(depending on type)
Adaptation protocol 2 : V110 or V120(depending on type)
Synchronous: Asynchronous Synchronous: Asynchronous
2
table 12.4: Sample control setupSetup: 3 Input Configuration: 1 Flow control: 1
Transmission speed: 19200baudsReception speed: 19200 baudsAutobaud: NoParity: NoParity error: replaceReplacement character: ?Data bits: 8 bitsStop bits: 1 bit
Break key: disconnectionHOLD detection: NoDisconnection detection: NoLong sequence: 3N-2 code ASCII: 43N-1 code ASCII: 43Disconnection ASCII code: 43Standby ASCII code: 0Line delete ASCII code: 1Inactivity timeout: 0Echo backspace: NoEcho suppression: No
Dev flow control by TA:hardwareMask (fl. control by TA): 48Status (fl. control by TA): 18TA flow control by device:hardwareDisconnected mode: NoMask (Fl. ctrl. by device): 48Status (Fl. ctrl. by device):48Number of Xon characters: 3External clock: NoExternal backup clock: No
table 12.5: Sample input/output configurationOutput configuration: 1LF after CRIn command mode: YesIn connected mode: NoLocal echoIn command mode: NoIn command mode: NoNot used: 0Not used: 0Not used: 0
12-11
12.2.5 Configuring the RMA unit
The modem/TA may be connected to the PCX via an RMA interface. To configure amodem/TA connection to the Exc port and the transparent connection of port Exb to port Dby a cable:
1. Connect to the RMA unit via the rma account, using password rma.
2. Enter menu. The following screen is displayed:[1] Connexions[2] States[3] Management[4] Session[5] Exit[6] Save[7] Password[8] PrivilegesYour choice :
3. In Management > Devices> Exc > Interface > Setup, make the following settings:19200 bauds – 8bits – no parity – 1 stop bit – Xon Xoff
4. In Management > Devices > Exc > Protocol, specify the device used:[1] Hayes Creatix LC144[2] Hayes Multitech MT1932[3] Hayes TA/UA[4] Hayes Standard[5] V25 Bis TA/UA[6] V25 Bis Standard[7] Transparent[8] Console
5. Configure Exb with the same configuration settings as Exc (19200,8,n,1,XonXoff). Theconfiguration is different in the Management > Devices > Exb > Protocol menu, whereyou must select [7] Transparent.
Note:
In configuration application, under the corresponding CPU, ensure that Shelf --> Board --> Interface type
for RMA is selected as Application board.
12.2.6 Configuring the e-RMA unit (1)
To configure e-RMA access with PPP connectivity on the PCX:
1. Validate the e-RMA feature:a. Connect to the PCX: From the Configuration Application in the Network tab in the
OmniVista 4760, select the PCX.
Chapter 12
12-12
Connect to the PCX via the Telnet utility, then identify yourself with a user accountsuch as mtcl.
b. Select the Shelf > Board > GD > Edit and set the e-RMA feature attribute to Yes.
2. Set the e-RMA directory number:a. Connect to the PCX.b. Run mgr.c. Select Applications > eRMA configuration > eRMA Application > Edit and
complete the following attributes:
table 12.6: e-RMA applicationDirectory Number Enter the DDI number of the internal modem.
Login attempts Enter the maximum number of login attempts.
Unreachable timer Enter an unreachable delay (e.g. 10)
Inter-incident Timer Enter the time between two incident calls (e.g. 1)
3. Configure e-RMA logins:• Connect to the PCX.• Run mgr.• Select Applications > eRMA configuration > eRMA Logins > Create and complete
the following attributes:
table 12.7: e-RMA loginLogin For example, ermappp
Password Enter a password
Confirm Confirm password
Security Method None
Callback type Select Calling Number
Callback number Enter caller number
4. Create a CHAP account (optional). To create a CHAP account, see the CHAPauthentication paragraph in section 2.2.2 § Serial Link Configuration .
5. Validate the e-RMA access for PPP protocol:a. Access the Alcatel 4400 IP Network Administration menu by entering netadmin -m.b. Select 6 Serial links (SLIP/PPP).c. Select Add, and set the following parameters:
table 12.8: e-RMA loginDevice used /dev/e-rma
Confirmation Yes
Default speed 115200
Do you use a modem Yes
Compression Yes
Inactivity time out "default"
Chap protocol Yes
12-13
6. Install the device on the OmniVista 4760 server:a. Open the control panel on the PC and click the Phone and Modem Options icon.b. In the Modems tab, click Add.c. In the Add Hardware Wizard dialog box, select "Do not detect my modem, I will select
it from a list" and click Next.d. Select the Manufacturer and Model. Enter COM1 or COM2 for Selected Ports
according the communications port available.e. Once the modem is added, on the Properties tab, set the Maximum Port Speed to
19200.
7. Configure the modem pool on the OmniVista 4760: For the procedure, see section 2.1.3 §Declaring the modem pool on the OmniVista 4760
8. Configure the PCX with PPP modem-modem connection using e-RMA on the OmniVista4760: For the procedure, see section 2.1.4 § Declaring a PPP connection with a PCX onthe OmniVista 4760 and update the following attributes in the Connectivity tab:
table 12.9: e-RMA loginConnection Type e-RMA access
IP address none
Phone number (PPP) calling number of the remote site erma
Timeout (PPP) 540 seconds
PPP Account Password ppp
Authenticatoin CHAP login(PPP)
client
Authenticatoin CHAP pass-word (PPP)
secret
Modem Pool DN (PPP) name of the modem pool created in previous step
RMA Login (PPP) ermappp
RMA Password (PPP) ermapwd
To configure RMA alarms, see section 2.9 § Configuring RMA alarms .(1): e-RMA unit can also be configured through 4760i tool.
12.2.7 IP/X25 connectivity (Alcatel-Lucent OmniPCX Enterprise CS/OmniPCX4400)
12.2.7.1 Configuration on the OmniVista 4760 server
The gateway PCX is directly connected to OmniVista 4760, either via a LAN or via amodem/TA. The following fields: connection type, IP address, and gateway link (IP/X25) are tobe completed for remote PCXs connected via IP/X25 to a gateway PCX for connection to theOmniVista 4760.
Chapter 12
12-14
Figure 12.4: Access to a PCX via a gateway PCX
To create a remote PCX with IP/X25 connectivity:
1. Run the Directory application, then click the System tab.
2. Create the Network and Subnetwork, if required.
3. Create the new PCX and update the following attributes in the PCX tab:• Name• Node Number. (For help finding the network node number of an OmniPCX 4400 or
Alcatel-Lucent OmniPCX Enterprise CS, see section 2.8.2 § Finding the Network nodenumber of a PCX
4. Click the Connectivity tab and update the following attributes:• Connection Type: IP/X.25• IP address: The IP/X25 address (tunnel address).• Gateway Link: DN of the PCX used as gateway. Click the icon to the right of the field
to specify the PCX in the System directory on the OmniVista 4760.
Figure 12.5: IP/X25
12.2.7.2 Configuration on the PCX
This section presents an example describing how to configure both PCXs.
table 12.10: Sample configuration IP/X.25 gateway link
12-15
IP Address(Ethernet) 10.10.1.10 10.10.1.1 10.10.2.1
Netmask 255.255.255.0 255.255.255.0 255.255.255.0
IP/X25 Address - 172.30.1.1 172.30.1.2
IP/X25 Name - x000101_tun x000102_tun
Main role address - 10.10.1.2 10.10.2.2
Main role name - Xm00001 Xm000002
Standby role ad-dress - 10.10.1.3 10.10.2.3
Standby role name - XS00001 XS000002
In this example, the OmniVista 4760 is connected to the first PCX via an Ethernet. To reachthe second PCX, the call passes through the first PCX, which is used as a gateway.Depending on the site, specific settings must be made. Before configuring the IP/X25, youmust define the addresses to be configured on the PCX network:
- The IP/X25 address for each PCX that use the tunnel.
- An IP address for the OmniVista 4760 server to be used in the PCX network. TheOmniVista 4760 server has to be in the same local network as the PCX gateway. Thesecond PCX (remote) has to be set into another network (see the example of IP addressesin the table 10 table: Sample configuration IP/X.25 gateway link ).
12.2.7.2.1 Configuring connectivity on PCX N1
The following procedure describes how to setup an IP/X25 on PCX N1:
1. Connect to PCX N1, then run netadmin -m. The Alcatel 4400 IP NetworkAdministration menu displays.
2. Select menu item 1 Installation.
3. Answer the following questions:• Do you intend to use IP/X25 on your system (y/n default is 'n')? y• Is your system part of a network of several private networks (y/n, default is 'y')? y• X25 private network number (between 0 to 252)? 1 (network number)• Unique site number (between 0 to 19 - 83 reserved for the distributors - one different
number per Alcatel 4400 of the network)? 1 (node number)
4. In the Ethernet interface setup, answer the following questions:• CPU name (default is xa000101)?• CPU address (default is 10.1.1.1)? 10.10.1.1.• Netmask: 255.255.255.0
5. In the CPU redundancy setup, answer the following questions:• Is there a duplicate CPU on your system (y/n, default is 'n')? n
Chapter 12
12-16
A message confirming the setup has been correctly completed appears.
6. Press Return (Enter) to return to the netadmin main menu, then enter 0 to exit.
12.2.7.2.2 Configuring connectivity on PCX N2
The following procedure describes how to setup an IP/X25 on PCX N2.
1. Connect to PCX N2, then run netadmin -m. The Alcatel 4400 IP NetworkAdministration menu displays.
2. Select menu item 1 Installation.
3. Answer the following questions:• Do you intend to use IP/X25 on your system (y/n default is 'n')? y• X25 private network number (between 0 to 252)? 1 (network number).• Unique site number (between 0 to 252 (node) - one different number per Alcatel 4400
of the network)? 4 (node number)
4. In the Ethernet interface setup, answer the following questions:• CPU name (default is xa000102)? Press Return (Enter)• CPU address (default is 10.1.1.1)? 10.10.2.2.• Netmask: 255.255.255.0
5. In the CPU redundancy setup, answer the following questions:• Is there a duplicate CPU on your system (y/n, default is 'n')? nA message confirming the setup has been correctly completed appears.
6. Press Return (Enter) to return to the netadmin main menu, then enter 0 to exit.
12.2.7.2.3 Enabling Routing Information Protocol (RIP)
To enable dynamic routing on the gateway PCX:
1. Launch netadmin -m.
2. Select 8 Routing setup
3. In the Routing setup menu, select 3 Dynamic routing (RIP/RSL), and answer thequestion:• Do you want to activate dynamic routing ('r'=RIP, 's'=RSL, 'n'=NO, default is 'n')? r
12.2.8 Useful information (Alcatel-Lucent OmniPCX Enterprise CS/OmniPCX4400)
12.2.8.1 Finding a PCX's IP address
If you do not know the IP address of a PCX, you can set up a serial connection between thePCX's COM port and a VT100 console or a PC. The procedure to be followed when using aPC is:
1. Physically connect the PC to the PCX with a crossed serial cable.
2. Use the Start > Programs > Accessories > Hyper Terminal >Hyper Terminal program.
3. Set the connection to 9600 bauds, 8 bits, no parity with 1 stop bit, then launch theconnection. The PCX home page is displayed.
4. Identify yourself to the PCX by entering a logon and a password (by default, mtcl and
12-17
mtcl).
5. Enter the netadmin -m command. The Alcatel 4400 IP Network Administration menu isdisplayed.
6. Access item 3. Local Ethernet Interface, then 1. View. The Ethernet interface configurationis displayed as follows:Internet Name: xa024001Internet address: 10.4.1.1Netmask: 255.255.0.0
7. To modify this address, use command 2. Update, then follow the instructions.
12.2.8.2 Finding the Network node number of a PCX
If you do not know the PCX's IP address, connect via the program: Start > Programs >Accessories >Telnet. Otherwise, use Start > Programs > Accessories > Hyper Terminal >HyperTerminal (See previous section).
1. Set the connection to 9600 bauds, 8 bits, no parity with 1 stop bit, then launch theconnection. The PCX home page is displayed.
2. Identify yourself to the PCX by entering a logon and a password (by default, mtcl andmtcl).
3. Enter the siteid command. PCX technical data is listed, including Node Number (PCXnumber) and Network number.
Network node number is (100 X network number ) + node number. The table belowpresents some examples.
table 12.11: Network node number examples
Network number Node number(PCX number)
Network node num-ber
1 1 101
0 2 2
3 1 301
In the System directory on the OmniVista 4760, when a Network > Subnet > PCX tree isconstructed, the Subnet is the same as the Network Number.
12.2.9 Configuring RMA alarms
Starting with release 2.0, the OmniVista 4760 can process PCX alarms transmitted by an RMAinterface over a V24 link via modems or TAs.
Chapter 12
12-18
Figure 12.6: RMA alarms configuration
If a PPP link via modem or TA already exists between the OmniVista 4760 and the PCX, it canbe used to report alarms. Follow these steps to implement this feature:
- Add a modem in Windows.
- Declare a pool of modems.
- Set attributes for the PCX in the System directory on the OmniVista 4760.
- Configure modems or TAs.
- Configure RMA.
12.2.9.1 Adding a modem in Windows.
If there is already a modem for a PPP link, it can also be used to receive alarms. Follow theprocedure described in section 2.1.2 § Installing a modem or TA in Windows 2000/2003 .
12.2.9.2 Declaring a pool of modems on the OmniVista 4760
Follow the procedure described in section 2.1.3 § Declaring the modem pool on the OmniVista4760 . Set the Usage attribute to Dial out and RMA alarms or to RMA alarms (if PPP link isused only to report the alarms).
12.2.9.3 Setting attributes for the PCX in the System directory
To configure System directory attributes for the PCX, see section 2.1.4 § Declaring a PPPconnection with a PCX on the OmniVista 4760 . In addition, check the following attributes:
In the Connectivity tab, update the following attributes:
- FTP user: adfexc
- FTP Password: adfexc
- Connection type: Select RMA
- IP address: is not required. It is automatically assigned by the Alcatel-Lucent OmniPCXEnterprise CS on initial synchronization.
- RMA Login (PPP): e-RMA login configured using mgr (see table 7 table: e-RMA login ).
- RMA password (PPP)
- RMA Port: to be defined for the external RMA board.
In the Data Collection tab, update the following attributes:
- alarm reception mode: RMA calls
- RMA ID: the identifier is configured using mgr (see table 15 table: Installation ). Thischaracter string is used to identify the calling PCX. It corresponds to the client name
12-19
configured in the RMA.
Note:
To receive the alarms through the e-RMA connectivity perform the same configuration as the one de-
scribed above except for the following parameters:
Connection type: set e-RMA.
RMA Port: irrelevant.
12.2.9.4 Configuring modems and TAs
To configure a modem, see section 2.3 § Configuring modems with or without RMA . Toconfigure a TA, see section 2.4 § Configuring TAs with or without RMA
12.2.9.5 Configuring RMA alarms on the PCX (1)
To configure the RMA unit, see section 2.5 § Configuring the RMA unit or section 2.6 §Configuring the e-RMA unit (1) . In addition, configure the attributes described below on thePCX:
1. Connect to the PCX via the Telnet utility, then identify yourself with a user account such asmtcl.
2. Run mgr. The main configuration menu is displayed.
To configure incidents:
1. Select Applications > Incident manager >View/Modify. A submenu is displayed.
2. Complete the following attributes:
table 12.12: Incident configurationV24 No. Not used
RMA RMA and eRMA
RMA Network No
Display Severity Minor
Storage Severity Free
Network Severity Indeterminate
Network Incident DisplaySeverity
Indeterminate
Network Incident StorageSeverity
Free
Topological Incident Dis-play
Yes
Topological Incident Stor-age
Yes
Topological Network Yes
3. Confirm.
To configure incident filters:
1. Select Applications > Incident manager > Descend hierarchy> Incident Filter >View/Modify
Chapter 12
12-20
2. Complete the following attributes:
table 12.13: Incident filterIncident No. Enter an incident number
Network No. Enter network number
Node No. Enter node number
Shelf Number Enter the number of the ACT Media Gateway
Board number Enter board number
Behind US —
Set Address Enter the address of the set.
RMA Action Action 1
Alarm Action None
Table number 0
Screen Display Yes
Disk Storage No
Network Incident No
3. Confirm.
To configure e-RMA actions:
1. Select Applications > eRMA >eRMA Actions > View/Modify
2. Complete the following attributes:
table 12.14: e-RMA actionsAction type: Select Call alarm center
Alarm center number Enter the alarm center number
3. Confirm.
To configure the installation:
1. Select Applications > System > Client Information.
2. Complete the following attributes:
table 12.15: InstallationClient details
Name Enter an identifying name (this name must be different foreach PCX) (e.g. colb1)
Address —
Country —
City / Town —
Date Format: Latin
DPNSS Parameters
Master No
ICL 0
12-21
Node Prefix —
Night Mode No
Routing Optimization No
Access Code —
RAR Address —
(1): RMA alarms can also be configured through the 4760i tool.
12.3 OmniPCX Office
12.3.1 Declaring a modem on a PC hosting OmniVista 4760 server
1. Declaring modemsModems may be connected either on the PC's native V24 ports or the V24 extension portsof a MOXA unit. If you are using a MOXA unit, see section 2.1.1 § Installing andconfiguring the MOXA unit (optional) .
2. Analog modemThe recommended type of modem is the MultiTech MT5634ZBA Plug&Play.The driver for this modem is automatically detected and installed by Windows 2000/2003.
Caution:However, if the modem in not "Plug&play", you must install the driver supplied with the mo-dem and not the driver listed in Windows 2000/2003.
• Declare the modem in Windows.• Keep the default settings but check the following:
• The connection data settings:• Maximum port speed: this should be left at maximum (115 200 bps).• Data protocol: EC standard.• Compression: enabled.• Flow control: hardware.
• Hardware (device) settings:• Data bits: 8.• Parity: no.• Stop bits: 1.• Modulation: standard.
3. ISDN modem1. Install the driver supplied with the modem (mandatory).
As a general rule, an ISDN modem of 64 to 128K supporting PPP protocol is sufficient.Approved modems include the MultiTech MTA128 ST, model MTA 128ST-RCML-PPP.
2. Connect in terminal mode via the COM port.
Chapter 12
12-22
Note:To connect in terminal mode via the COM port, the port must first be released, either by:
• Disabling the modem in the peripheral device manager.
• Or, stopping the routing task and remote access (if running).To do this, proceed as follows:
1. Launch routing and remote access.
2. Select server name in the shortcut menu, then “All tasks”, then “Stop”.
3. Shut down and restart the modem.
3. Configure the modem using AT commands.1. Launch terminal mode in VT100 emulation (for example: VT100 hyperterminal).2. When the prompt is displayed, enter the following sequences:
• ats58=3<CR>This command authorizes authentication of all protocols. By default, only PAPprotocol is authenticated.
• at&w0<CR>This command saves the configuration.
4. Restart routing and remote access.
4. Declaring modem poolSee section 2.1.3 § Declaring the modem pool on the OmniVista 4760 to declare themodem pool on the OmniVista 4760.In Use field of modem pool definition, select Dial out and PPP dial in.
12.3.2 Declaring an OmniPCX Office in PPP mode on the OmniVista 4760
1. On the OmniVista 4760, start the Directory application, then click the System tab.
2. Select the PCX and update the following attributes in the PCX tab:• A Network by specifying a name and number.• A Subnetwork by specifying a name and number.• alarm reception mode: Select PPP urgent alarm call or None.• Accounting Process : Select Detailed accounting.• Default Cost center
Caution:
• This cost center is assigned to all sets by default.
• If several cost centers must be used, the node must be declared without specifyingthe cost center. In the organization, all sets will be placed under the root in the "nmc"tree. It will then be possible to create cost centers manually, thus allowing sets to bemoved by "cut and paste" operations.
3. Click the Connectivity tab and update the following attributes:• FTP Password: tuxalize• Connection type: PPP• The IP address is not required. It is automatically assigned by the OmniPCX Office
during the first connection (through configuration or synchronization process).• 2 B-Channel bonding. OmniPCX Office release 4.0 (version 400 / 016) and greater
allows you to reserve two B channels (only for direct or call back outgoing calls). The
12-23
2B-channel field is only relevant for ISDN connection (modem S0 or DIVA board). Thisfield does not concern the modem S0 MultiTech MTA128 ST with ML-PPP plug & playdriver that automatically manages both the channels. Select this field only if you areusing the DIVA board.
• Timeout PPP: 10 minutes by default.• Phone Number (PPP): this is the phone number of the modem on the PCX side (“V34
remote maintenance” for the PSTN or “Remote access” for ISDN).• Modem Pool DN (PPP): the DN of the modem pool to be used for calls (see section
2.1.3 § Declaring the modem pool on the OmniVista 4760 ).
4. Click Apply to save changes.
12.3.3 Declaring an OmniPCX Office in PPP mode (on the PCX side)
1. Analog modemThe Alcatel OmniPCX Office is fitted as standard with a V34 analog modem for remoteconnection through the public network. This provides a point-to-point communication linkwhich can be accessed by the standard LINUX protocols (SLIP, PPP, etc.).Its main characteristics are:• V34 modem.• Maximum transmission speed: 33600 bps.• Hayes protocol.• The internal modem corresponds to the directory number linked to V34 remote
maintenance in the Subscriber/Basestations list.Select it and click Details and then click the tab Services.a. Service 1: AB Servb. Service 2: Telephone
The other services are not defined.• Configure this directory number so that it can be called by DDI number in the
numbering plan.
2. ISDN modemThe OmniPCX Office is fitted as standard with a 64K ISDN modem with PPP protocol forremote connection through the public network. This provides a point-to-pointcommunication link which can be accessed by the standard LINUX protocols (SLIP, PPP,etc.).When the ISDN modem is used, it is necessary to reserve a DDI number in the publicnumbering plan in order to be able to set up a connection.If the DDI number is unavailable, simply check whether the ISDN modem access of thesystem is present in the default operator group. From then on it is no longer necessary toreserve a DDI number.The internal modem corresponds to the directory number linked to Remote Acc. ISDN inthe Subscriber/Basestations list.• Select it and click Details and then click the tab Services.
• Service 1: DTR 64• Service 2: None
The other services are not defined.
12.3.4 Urgent alarm management on PPP connectivity
Chapter 12
12-24
Caution:
Windows 2000/2003 server is required.
OmniPCX Office initiates real time retrieval of the specific alarms defined as 'urgent' (in thePCX). It requests a connection to be set up for all urgent alarms generated.
Perform the following steps:
- Activate routing and remote access (RAS) in Windows.
- Configure the RAS server in Windows.
- Create a PPP client account in Windows.
- Assign user rights for the PPP client account in Windows.
- Perform management on the OmniPCX Office.
Note:
For more information on OmniPCX Office urgent alarm management, see Technical Communication TCV
049 Ed.2.
12.3.4.1 Activating routing and remote access (RAS) in Windows
- Open the Control panel > Administration tools > Routing and remote access.
- Via the shortcut menu, start the Configure and activate remote access routing Wizard
- For Windows 2000:• Select Server configured manually
- For Windows 2003:• Select Custom configuration• Select then Remote Access server
Note:
Select the Network favorites icon, then Properties, and launch Remote network connection.
A new Incoming connection entry has been added. The TR LED on the modem should come on.
12.3.4.2 Configuring the RAS server in Windows
- Open the Control panel > Administration tools > Routing and remote access.
- Via the shortcut menu, select Server name and Properties• General tab
• Deselect Router• Select Remote access server
• Security tab• Authentication provider: Windows authentication• Authentication methods: Select encrypted authentication Microsoft version 2
(MS-CHAP v2) and encrypted authentication Microsoft (MS-CHAP)• Account provider: Windows account management.
• IP tab• Deselect Activate IP routing• Select Authorize remote access using IP addresses and on-demand access
12-25
connections• Select Static address pool• Enter a range of addresses (example: 192.5.5.1 to 192.5.5.10)
• PPP tab• Deselect Multilink connections• Deselect LCP (Link Control Protocol) Extensions• Deselect Software compression
• Event Logger tab• For Windows 2000:
• Select Record maximum information in the log• Select Activate connection to PPP protocol
• For Windows 2003• Select log all events• Start : /Administrative Tools/Routing and Remote Access• Double click on: Server Name• Select: Remote Access strategy• Double click on: CNX to other access server properties• Click on: Profile Edition Select tab Encryption• Enable: All tab
The RAS service is shut down and restarted.
12.3.4.3 Creating a PPP client account in Windows
1. Open Control panel>Administration tools>Computer management.
2. Double-click Local users and groups.
3. Select Users and, in the shortcut menu, click New user...
4. In the New user window: enter the name URGALARM and corresponding password. ClickCreate, then Close.
5. Select the Urgalarm user then, in the shortcut menu, select Properties.
6. In the General tab, select Password never expires.
7. In the Incoming call tab:• Select Always access.• Select No Callback.
Note:
URGALARM must not be part of a group.
If the Urgalarm user account is in a domain, it must be configured on the OmniPCX Officeusing OMC:
table 12.16: Declaring the ”URGALARM” login using OMC
Chapter 12
12-26
Type of Win-dows ac-count for ur-gent alarms
4760 Server be-longs to a domain
Case OS Server Case OS worksta-tion
Local No <Urgent alarm login>Example: URGALARM
<Urgent alarm lo-gin>Example: UR-GALARM
Local Yes <Host4760>\\<Urgent alarm lo-gin>Example:COL000038085B\\URGALARM
<Urgent alarm login>:ex:URGALARM
12.3.4.4 Assigning user rights for the PPP client in Windows
1. Start Parameters > Administration tools.
2. Double-click Local security strategies
3. Expand Local strategies and select Assign user rights.
4. Select Access this computer from the network, then double-click.
5. Click Add.
6. Select Urgalarm from the drop-down list.
7. Click Add.
12.3.4.5 Management on the OmniPCX Office
1. Start the OMC application. Click the Network management and control icon, thenCentralized management.
2. In part1:• NMC number for automatic alarms reporting: Enter the call number of the modem
connected to the OmniVista 4760.• Uncheck Try to use active NMC session for alarms reporting.• NMC connectivity: Telewatch V34 or Remote Acc ISDN relative to the analog or
digital modem on the OmniVista 4760 side.• Alarm User (refer the table 16 table: Declaring the ”URGALARM” login using OMC ).• Alarm Password (refer the table 16 table: Declaring the ”URGALARM” login using
OMC ).• Activate call accounting for: Incoming and outgoing calls (optional).
3. Part 2:Check Automatic alarms reporting.
12.3.4.6 Setting Parameters for the PCX in OmniVista 4760 server
On the OmniVista 4760, start the Directory application and click the System tab. Select thePCX and on the Data Collection tab, set the alarm reception mode attribute to PPP urgentalarm call.
To receive the urgent alarms for the OmniPCX Office release 4.0 and greater, the followingfields can be configured (thanks to this configuration, LDAP / PCX synchronization process will
12-27
update the fields mentioned in the section 3.4.5 § Management on the OmniPCX Office ) :
- DN for OmniPCX Office urgent alarms modem pool - receiving (PPP): Insert the DN inthe modem pool used for collecting the urgent alarms. This value can be registered eitherfrom the tab OmniPCX Office connectivity in the Network / Subnetwork declaration in theDirectory application, or from the tab Alarm Management in the OmniPCX declaration.(1)
- OmniVista 4760 Phone Number: Enter the phone number of the modem connected to theOmniVista 4760. This value can be registered either from the modem pool declaration (seesection 2.1.3 § Declaring the modem pool on the OmniVista 4760 ), or from the tab AlarmManagement in the OmniPCX declaration.
- Username and Password: Enter the urgent alarm login and password. These values canbe registered from the tab PPP Account for OmniPCX Office urgent alarms in \nmc\4760 host name \Servers \4760 host name instance (in System Directory). To fill theseparameters, follow the instructions from the table 16 table: Declaring the ”URGALARM”login using OMC but replace '\\' by '\'.
(1): If the modem pool DN is found in the OmniPCX declaration, this value will be taken intoaccount by the synchronization process and the values from the upper levels will be ignored. Ifthere is no value in the OmniPCX declaration but a value is found in the subnetworkdeclaration, this value will be taken into account by the synchronization process and the valuesfrom the upper level (network) will be ignored.
(2): If the OmniVista 4760 phone number is found in the OmniPCX declaration, this value willbe taken into account by the synchronization process and the value from the modem pooldeclaration will be ignored.
12.3.5 Urgent alarm management on Ethernet connectivity
Setting Parameters for the PCX in the System directory:
On the OmniVista 4760, start the Directory application and click the System tab. Select thePCX and on the Data Collection tab:
- For the OmniPCX Office release below 5.0, set the alarm reception mode attribute toPermanent IP Connectivity.
- For the OmniPCX Office release 5.0 and greater, set the alarm reception mode attributeto Permanent IP Connectivity or to HTTP Connectivity (for non permanent connectivity).
12.3.6 Useful information for the OmniPCX Office
12.3.6.1 Notes on installing OMC
- The OMC application can be installed on the OmniVista 4760 server PC.
- OMC must be installed on each client PC on which it is to be used.
- A separate OMC installation can be performed before or after OmniVista 4760 installation.
- The folder 4760_ARC/OXO/data should be made as a shared folder for OMC to belaunched through OmniVista 4760.
- The Configuration application first launches OMC via a link created between theOmniVista 4760 and the OMC application. Next, the Configuration application launchesan OmniPCX Office configuration data save/restore.
Chapter 12
12-28
- If a new version of OMC must be installed to manage a newer OmniPCX Office, theexisting version must be uninstalled before installing the new one.
Caution:
After installing the OMC software, the PC has to be rebooted before any use of the OMC from the
OmniVista 4760 application.
12.3.6.2 Accounting management using OMC
1. Start OMC from the Configuration application.
2. Expand the Accounting icon then double-click Accounting.
3. In the Print tab, select:• Enable V24 output• Leased line print
Note 1:
a. Never select Network mode. Otherwise, the sets in the organization would be represented by theirDID numbers.
b. A number entered in Accounting node has no impact as it is not used by the OmniVista 4760.
• Click the Fields button and select all the fields in the right-hand column.
Note 2:If the accounting tickets for incoming calls (in addition to outgoing calls) must be loaded:
• Go to Subscriber/Basestation List, then Details.
• Select Any call in Tracking. Do this for each set.
• Expand the Network Management and Control icon, then double-click Centralized Manage-ment.
These attributes are for the OmniVista 4760.
• Check that accounting is active for: Incoming calls or Outgoing calls or Incoming + out-going calls. If No call is selected, the OmniVista 4760 poller will not retrieve tickets. Ticketswill be stored in the buffer.
• In PCX Identification, the PCX declared in the System directory is shown, if synchroniza-tion has been performed.
12.3.6.3 Synchronizing sets and alarms
1. In the Directory application, System tab, select node name in the tree.
2. On the PCX tab, set the Accounting Process attribute to Detailed accounting.
Caution:Do not select global accounting, otherwise set numbers will be displayed in the followingformat: 1 000 000 + (Subnetwork_Number x 100 + Node_number).
Example: with node number = 5 in a subnetwork =1, set numbers would be: *****_1000105
3. Start synchronization.All sets that produced tickets are indicated under the root in the “nmc” tree or under thedefault cost center declared in the System directory. If all the sets are located under theroot in the “nmc” tree, create cost centers and assign the sets to the cost centers usingcut/paste operations.The OmniPCX Office buffer can contain up to 1000 tickets (with no hard drive). Followingsynchronization, the tickets in the buffer are deleted. If necessary, modify synchronization
12-29
frequency.
12.4 Diva Board connectivity
12.4.1 Description
EICON DIVA PRI-E1-T1-8 is a PC extension board that can be inserted into OmniVista 4760server.
With this board, you can:
- add to the server a set of integrated modems (30 channels: 24 to 30 possible digitalchannels and 6 to 0 analog channels).
- plug the server to the public network via E1 trunk or T2 (France).
- connect, using PPP protocol, to OmniPCX Office and to OmniPCX Enterprise with abandwidth of more than 64kb/s.
For the server PC the prerequisites are:
- Operating system Windows 2003 Standard Edition SP2.
- Slot PCI Bus.
- Board Diva PRI-E1-T1-8,
- Connection to E1 trunk or T2 (France).
12.4.2 Connection to OmniPCX Office
On OmniPCX Office side, the integrated modem is used (see section 3.3 § Declaring anOmniPCX Office in PPP mode (on the PCX side) .
For a digital connection: 1 or 2 B channel can be used.
Chapter 12
12-30
Figure 12.7: OmniPCX Office Connection
table 12.17: OmniPCX Office PPP connectivityConnection Direct PPP dial out PPP dial out with call
backPPP dial (for urgentalarm)
1B Yes Yes Yes
2B Yes as from OmniPCXOffice R4.0
No No
Analog Yes Yes Yes
The available features are:
- Configuration access,
- PCX Patch transfer (download),
- Synchronisation (accounting....),
- Save/Restore,
- Urgents Alarms.
Note:
For more information on DIVA board installation see Technical Communication TCV057.
12.4.3 Connection to Alcatel-Lucent OmniPCX Enterprise CS
Note 1:
The IRAD board is not available for new deliveries. This connection cannot be used anymore.
12-31
On OmniPCX Enterprise side, IRAD is used.
This is an ISDN-Ethernet router that enables connection to the local Alcatel-Lucent OmniPCXEnterprise CS or to one Alcatel-Lucent OmniPCX Enterprise CS in the IP network as IRADboard.
1 to 5 B channels can be used on each IRAD board.
Figure 12.8: Alcatel-Lucent OmniPCX Enterprise CS Connection
table 12.18: Alcatel-Lucent OmniPCX Enterprise CS PPP connectivityConnection PPP direct dial out PPP dial OUT with call
backPPP dial in (for alarms)
1 to 5 B Yes No No
Restriction: no T1 connectivity (US).
For alarms, using e-RMA is recommended. In this case one analog modem port can be usedon the E1 board.
The available features are:
- Configuration access,
- Synchronization (accounting....),
- Save/ Restore.
- PCX patch transfer (download).
Note 2:
See Technical Communication TCV 057 for information on the DIVA board installation and, see Technic-
Chapter 12
12-32
al Communication TCV 067 for more information on IRAD connectivity with the DIVA board.
12-33
Chapter 12
12-34
Ensure the OmniVista 4760 is set up in a secured environment. For OmniVista 4760 securityinformation refer to the Security guidelines.
To define the security access level for the OmniVista 4760 users, see the OmniVista 4760Security Guide.
13
13-1
Chapter 13
13-2
