Procedure 9 INSTALL THE ELAP APPLICATION

3.4.3 Procedure 9 INSTALL THE ELAP APPLICATION

Table 3-13 Procedure 9 INSTALL THE ELAP APPLICATION

STEP # This procedure installs the application on the server. Check off (✓)each step as it is completed. Boxes have been provided for this purpose under each step number. IF THIS PROCEDURE FAILS, CONTACT THE ORACLE TECHNICAL SERVICES AND ASK FOR ASSISTANCE.

STEP #	This procedure installs the application on the server. Check off (✓)each step as it is completed. Boxes have been provided for this purpose under each step number. IF THIS PROCEDURE FAILS, CONTACT THE ORACLE TECHNICAL SERVICES AND ASK FOR ASSISTANCE.
1. ☐	MPS A: Log in as “admusr” user.	If not already logged in, then login as “admusr”: `consolelogin:` `admusr` `password: password`
2. ☐	MPS A: Put ISO image on ELAP server.	Use any of the following methods to put ELAP 11.1 ISO image on the ELAP server. Perform ISO image generation from USB media using Appendix B Copy ISO to /var/TKLC/upgrade directory. Note: To perform this step, the provisional IP of the ELAP server must be set via platcfg menu.
3. ☐	MPS A: Start platcfg utility.	`$sudo` `su` `-` `platcfg`
4. ☐	MPS A: Select the Maintenance submenu.	The platcfg Main Menu appears. On the Main Menu, select Maintenance and press [ENTER]. Select the Upgrade menu and press [ENTER]. Select the Validate media menu and press [ENTER]. Select the upgrade media to be validated and press [ENTER]. NOTE: Output is dependent on target release. NOTE: Output is dependent on target release. The media validation shall pass to proceed further. If media validation fails, user should remove the ELAP iso from /var/TKLC/upgrade path and copy the validated media iso on the same path again. Select the Early Upgrade Checks menu and press [ENTER]. Early upgrade checks should be passed before upgrade is started. If the Early Upgrade Checks fail due to the ongoing syncing of raid mirrors, then wait until the resync is completed and run the “Early Upgrade Checks” again. Contact My Oracle Support by following the instructions on the front page or the instructions in the Appendix G if the early Upgrade checks fail due to any other reason. Select the Initiate Upgrade menu and press [ENTER].
5. ☐	MPS A: Select the Incremental upgrade Media.	The screen displays a message that it is searching for upgrade media. When the upgrade media is found, an Upgrade Media selection menu appears similar to the example below. Select the desired upgrade media and press [ENTER]. NOTE: Output is dependent on target release. Here first one is the TPD iso. Second iso is for ELAP application. The screen displays the output like following, indicating that the incremental upgrade software is first running the upgrade checks, and then proceeding with the upgrade.
6. ☐	MPS A: Press [ENTER] to start installation. Many informational messages will come across the terminal screen as the installation proceeds. Finally, after successful completion of ELAP install, the server should reboot, and login prompt should appear	After the final reboot, the screen displays the login prompt as in the example below.
7. ☐	MPS A: Verify that installation is complete, and no error occurred during installation.	Switch to root user to grep the errors occurred during installation. `$su - Password: <root_password>` `$ grep "Upgrade returned success" /var/TKLC/log/upgrade/upgrade.log 1461121282::Upgrade returned success! $ grep -i error /var/TKLC/log/upgrade/upgrade.log` Check the output of the upgrade log, contact the My Oracle Support by following the instructions in Appendix G, if the output contains any errors beside the following: Variable and RPMs that might contain the word error in them. All those messages are expected, and therefore aren’t considered errors. `$grep -i error /var/TKLC/log/upgrade/ugwrap.log` Check the output of the ugwrap log. If the output contains any errors, contact the My Oracle Support by following the instructions in Appendix G. NOTE: After the ELAP is installation is complete, the below mentioned logging is observed on ELAP CLI. These errors can be ignored, and they will not be observed, once the key exchange is performed successfully. `# drbd drbd0/0 drbd0: ambiguous node id: meta-data: 0, config: 1 WARN: stdin/stdout is not a TTY; using /dev/console..........` *************************************************************** DRBD's startup script waits for the peer node(s) to appear. If this node was already a degraded cluster before the reboot, the timeout is 5 seconds. [degr-wfc-timeout] - If the peer was available before the reboot, the timeout is 10 seconds. [wfc-timeout] `(These values are for resource 'drbd0'; 0 sec -> wait forever) To abort waiting enter 'yes' [ 10]:` `# drbd drbd0: State change failed: Can not disconnect a StandAlone device` `# drbd drbd0: State change failed: Can not disconnect a StandAlone device # drbd drbd0: State change failed: Can not disconnect a StandAlone device` `'drbd drbd0 tcp:unknown-b: Closing unexpected connection from 192.168.61.104'` `& 'drbd drbd0 tcp:unknown-b: Closing unexpected connection from 192.168.61.105'` NOTE: After ELAP is installation is complete, gsConnect.pl core is observed on the server which can be ignored and deleted from the server. $`ls –lrt` `/var/TKLC/core` `-rw------- 1 root root 49807360 Jul 26 01:52 core.gsConnect.pl.7030 -rw-r----- 1 root root 2248 Jul 26 01:53 core.gsConnect.pl.7030.bt` Delete core file using below command: `$ rm /var/TKLC/core/` `core.gsConnect*`
8 ☐	MPS X: Delete known_hosts files	`# rm /root/.ssh/known_hosts` `# rm /home/admusr/.ssh/known_hosts`
9. ☐	MPS A: Log in as “elapdev” user.	If not already logged in, then login as “elapdev”: `consolelogin: elapdev password: password`
10. ☐	MPS A: Switch to root user	`#su - Password:password`
11 ☐	MPS A: Verify ELAP release.	rpm -qi TKLCelap Name : TKLCelap Version : 5.0.87 Release : 11.1.0.0.0_111.6.0 Architecture: x86_64 Install Date: Fri 09 Oct 2026 03:01:14 AM EDT Group : Development/Build Size : 178295180 License : Oracle 2004, 2026 Signature : (none) Source RPM : TKLCelap-5.0.87-11.1.0.0.0_111.6.0.src.rpm Build Date : Fri 09 Oct 2026 02:18:47 AM EDT Build Host : elap-dev-tpd-150-31-0 Relocations : (not relocatable) Packager : <@oracle.com> Vendor : Oracle URL : http://www.oracle.com/ Summary : Oracle Communications ELAP Package Description : This is the Oracle Communications EAGLE LNP Application Processor(ELAP) package. The package installs ELAP software. Eagle LNP Application Processor (ELAP) provides REALLY INCREDIBLE Database (RIDB). ELAP provides the LNP feature.
12. ☐	MPS A and B: Update ssh_config to disable MD5 and MAC algorithm for security	Perform following steps to disable unsecure algorithm for ssh: `1) $ grep "MACs hmac-md5,hmac-md5-96," /etc/ssh/ssh_config If no output is displayed for above command skip this step and go to 2nd part of this step else continue to next command. $ rcstool co /etc/ssh/ssh_config $ sed -i '/MACs hmac-md5,hmac-md5-96,hmac-sha1-96/d' /etc/ssh/ssh_config $ rcstool ci /etc/ssh/ssh_config $ systemctl restart sshd` Now do the same for mac. `2) $ grep "MACs hmac-sha2-256,hmac-sha2-512" /etc/ssh/sshd_config If no output is displayed for above command continue to next command else skip this step and go to next step of this procedure. $ rcstool co /etc/ssh/sshd_config $ sed -i -e '$ a MACs hmac-sha2-256,hmac-sha2-512' /etc/ssh/sshd_config $ rcstool ci /etc/ssh/sshd_config $ systemctl restart sshd`
13. ☐	MPS A : Procedure complete.	This procedure is complete.

☐

MPS A: Log in as “admusr” user.

If not already logged in, then login as “admusr”:

consolelogin: admusr password: password

☐

MPS A: Put ISO image on ELAP server.

Use any of the following methods to put ELAP 11.1 ISO image on the ELAP server.

Perform ISO image generation from USB media using Appendix B
Copy ISO to /var/TKLC/upgrade directory.
Note: To perform this step, the provisional IP of the ELAP server must be set via platcfg menu.

☐

MPS A: Start platcfg utility.

$sudo su - platcfg

☐

MPS A: Select the Maintenance submenu.

The platcfg Main Menu appears.

On the Main Menu, select Maintenance and press [ENTER].

Text Main menu with Maintenance selected.

Select the Upgrade menu and press [ENTER].

Text Maintenance menu with Upgrade selected.

Select the Validate media menu and press [ENTER].

Upgrade menu with Validate Media selected.

Select the upgrade media to be validated and press [ENTER].

Choose Upgrade Media menu showing the ELAP ISO image.

NOTE: Output is dependent on target release.

Media validation console output showing PASS.

NOTE: Output is dependent on target release.

The media validation shall pass to proceed further. If media validation fails, user should remove the ELAP iso from /var/TKLC/upgrade path and copy the validated media iso on the same path again.

Select the Early Upgrade Checks menu and press [ENTER].

Upgrade menu with Early Upgrade Checks selected.

Early upgrade checks should be passed before upgrade is started.

Console output showing that early upgrade checks passed.

If the Early Upgrade Checks fail due to the ongoing syncing of raid mirrors, then wait until the resync is completed and run the “Early Upgrade Checks” again.

Early upgrade check failure while RAID mirrors are synchronizing.

RAID synchronization status from /proc/mdstat.

Contact My Oracle Support by following the instructions on the front page or the instructions in the Appendix G if the early Upgrade checks fail due to any other reason.

Select the Initiate Upgrade menu and press [ENTER].

Upgrade menu with Initiate Upgrade selected.

☐

MPS A: Select the Incremental upgrade Media.

The screen displays a message that it is searching for upgrade media. When the upgrade media is found, an Upgrade Media selection menu appears similar to the example below. Select the desired upgrade media and press [ENTER].

NOTE: Output is dependent on target release.

Here first one is the TPD iso. Second iso is for ELAP application.

The screen displays the output like following, indicating that the incremental upgrade software is first running the upgrade checks, and then proceeding with the upgrade.

Successful early checks and upgrade initialization output.

☐

MPS A: Press [ENTER] to start installation.

Many informational messages will come across the terminal screen as the installation proceeds.

Finally, after successful completion of ELAP install, the server should reboot, and login prompt should appear

After the final reboot, the screen displays the login prompt as in the example below.

ELAP installation startup console and login prompt.

☐

MPS A: Verify that installation is complete, and no error occurred during installation.

Switch to root user to grep the errors occurred during installation.

$su - 
Password: <root_password>

$ grep "Upgrade returned success" 
/var/TKLC/log/upgrade/upgrade.log 1461121282::Upgrade returned success! 
$ grep -i error /var/TKLC/log/upgrade/upgrade.log

Check the output of the upgrade log, contact the My Oracle Support by following the instructions in Appendix G, if the output contains any errors beside the following:

Variable and RPMs that might contain the word error in them.

All those messages are expected, and therefore aren’t considered errors.

$grep -i error /var/TKLC/log/upgrade/ugwrap.log

Check the output of the ugwrap log. If the output contains any errors, contact the My Oracle Support by following the instructions in Appendix G.

NOTE: After the ELAP is installation is complete, the below mentioned logging is observed on ELAP CLI. These errors can be ignored, and they will not be observed, once the key exchange is performed successfully.

# drbd drbd0/0 drbd0: ambiguous node id: meta-data: 0, config: 1 WARN: stdin/stdout is not a TTY; using /dev/console..........

***************************************************************

DRBD's startup script waits for the peer node(s) to appear. If this node was already a degraded cluster before the reboot, the timeout is 5 seconds. [degr-wfc-timeout] - If the peer was available before the reboot, the timeout is 10 seconds. [wfc-timeout]

(These values are for resource 'drbd0'; 0 sec -> wait forever) To abort waiting enter 'yes' [ 10]:

# drbd drbd0: State change failed: Can not disconnect a StandAlone device

# drbd drbd0: State change failed: Can not disconnect a StandAlone device # drbd drbd0: State change failed: Can not disconnect a StandAlone device

'drbd drbd0 tcp:unknown-b: Closing unexpected connection from 192.168.61.104'

& 'drbd drbd0 tcp:unknown-b: Closing unexpected connection from 192.168.61.105'

NOTE: After ELAP is installation is complete, gsConnect.pl core is observed on the server which can be ignored and deleted from the server.

$ls –lrt /var/TKLC/core

-rw------- 1 root root 49807360 Jul 26 01:52 core.gsConnect.pl.7030 -rw-r----- 1 root root 2248 Jul 26 01:53 core.gsConnect.pl.7030.bt

Delete core file using below command:

$ rm /var/TKLC/core/ core.gsConnect*

☐

MPS X:

Delete known_hosts files

# rm /root/.ssh/known_hosts

# rm /home/admusr/.ssh/known_hosts

☐

MPS A: Log in as “elapdev” user.

If not already logged in, then login as “elapdev”:

consolelogin: elapdev 
password: password

10.

☐

MPS A: Switch to root user

#su - 
Password:password

☐

MPS A: Verify ELAP release.

rpm -qi TKLCelap 
Name : TKLCelap 
Version : 5.0.87 
Release : 11.1.0.0.0_111.6.0 
Architecture: x86_64 
Install Date: Fri 09 Oct 2026 03:01:14 AM EDT 
Group : Development/Build 
Size : 178295180 
License : Oracle 2004, 2026 
Signature : (none) 
Source RPM : TKLCelap-5.0.87-11.1.0.0.0_111.6.0.src.rpm 
Build Date : Fri 09 Oct 2026 02:18:47 AM EDT 
Build Host : elap-dev-tpd-150-31-0 
Relocations : (not relocatable) 
Packager : <@oracle.com> 
Vendor : Oracle 
URL : http://www.oracle.com/ 
Summary : Oracle Communications ELAP Package 
Description : This is the Oracle Communications EAGLE LNP Application Processor(ELAP) package. The package installs ELAP software. 
Eagle LNP Application Processor (ELAP) provides REALLY INCREDIBLE Database (RIDB). ELAP provides the LNP feature.

12.

☐

MPS A and B: Update ssh_config to disable MD5 and MAC algorithm for

security

Perform following steps to disable unsecure algorithm for ssh:

1)  
$ grep "MACs hmac-md5,hmac-md5-96," /etc/ssh/ssh_config  
If no output is displayed for above command skip this step and go to 2nd part of this step else continue to next command.  
$ rcstool co /etc/ssh/ssh_config 
$ sed -i '/MACs hmac-md5,hmac-md5-96,hmac-sha1-96/d' 
/etc/ssh/ssh_config  
$ rcstool ci /etc/ssh/ssh_config 
$ systemctl restart sshd

Now do the same for mac.

2)  
$ grep "MACs hmac-sha2-256,hmac-sha2-512" /etc/ssh/sshd_config   
If no output is displayed for above command continue to next  command else skip this step and go to next step of this procedure. 
$ rcstool co /etc/ssh/sshd_config  
$ sed -i -e '$ a MACs hmac-sha2-256,hmac-sha2-512'  
/etc/ssh/sshd_config  
$ rcstool ci /etc/ssh/sshd_config  
$ systemctl restart sshd

13.

☐

MPS A : Procedure complete.

This procedure is complete.

This procedure is complete!