Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1951737.1
Update Date:2016-11-04
Keywords:

Solution Type  Technical Instruction Sure

Solution  1951737.1 :   How to Replace a E5-APP-B Card with the Spare Card Running Eagle Local Number Portability (LNP) Application (ELAP)  


Related Items
  • Oracle Communications EAGLE (Software)
  •  
Related Categories
  • PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec OS ELAP LSMS
  •  




In this Document
Goal
Solution
 1. General Notes
  1.1 Terminology
 1.2 Requirements
 2. Pre-E5-APP-B ELAP Card Replacement (ELAP 10.0 and Above)
 3. E5-APP-B ELAP Card Replacement (ELAP 10.0 and Above)
 Appendix A: ISO Image copy from USB Media
 Appendix B  – Initial Product Manufacture (IPM) and ELAP 10 Installation
 Appendix B-1. IPM MPS Server with TPD 5
 Appendix B-2. ELAP Installation and Server Configuration


Created from <SR 3-9699107301>

Applies to:

Oracle Communications EAGLE (Software) - Version ELAP 10.0 and later
Information in this document applies to any platform.

Goal

How to replace an E5-APP-B card running ELAP application?
 

Solution

 

1. General Notes

 This document is designed to provide the  steps to replace a faulty E5-APP-B based ELAP servers. 

 It will be necessary to halt the provisioning activity during the execution of the procedures outlined herein while a full database backup is being taken.  Normal provisioning can resume once the replacement procedure has been completed. For any issues incurred in executing any part of this document, follow the contact/escalation list.

 The individual executing this procedure must be experienced and well proficient with the following platforms and technologies.

  • Unix/Linux Admin
  • VI Editor
  • IP Networking
  • Oracle ELAP Platforms T1100 and E5-APP-B

 If you do not have these skills or if you are not completely comfortable working in a Unix or Linux system environment.

 

  STOP_HAND

STOP - DO NOT PROCEED

 1.1 Terminology

Term

Explanation

Active ELAP

The ELAP site that is currently used for provisioning through HSOP.

Standby ELAP

The ELAP site that is NOT currently used for provisioning through HSOP.

System health Check

Procedure used to determine the health and status of the ELAP server, typically performed using the TPD syscheck utility. 

 

1.2 Requirements

    1. Screen logging is required throughout the procedure. These logs should be made available to Oracle in the event their assistance is needed.
    2. Target-release Universal Serial Bus (USB) media or ISO image.
    3. Target Tekelec Platform Distribution (TPD) USB media or ISO image.
    4. The capability to log into a server, such as a Personal Computer (PC) with null modem cable for connection to serial port.
    5. The capability to log into the web Graphical User Interface (GUI), such as a PC with Internet Explorer.
    6. E5-APP-B server has the target TPD and EPAP application installed

see “ELAP 10.0 UPGRADE/INSTALLATION PROCEDURE 909-2264-001 Revision C, February 2014 Version 3.0”, section 3.2 about server installation procedures:

  1. ONLY follow procedures 1-6, and 16.
  2. Switches configuration (procedure 7) and first time configuration (procedure 8) are not needed.

 The document can be downloaded from Oracle documentation site

 7. TPD USB image and ELAP applications ISO files can be downloaded from Oracle software delivery cloud: https://edelivery.oracle.com/

 

2. Pre-E5-APP-B ELAP Card Replacement (ELAP 10.0 and Above)

 

S

T

E

P

#

Activity or Result Description

This entire procedure should take approximately 30 minutes.

 

1.  

Log into <HEALTHY_ELAP>  as root.

2.  

Perform Syscheck on  <HEALTHY_ELAP>

3.  

Verify that the <HEALTHY_ELAP> server is the Active server.

  

# hastatus

ACTIVE

 

If the <HEALTHY_ELAP> server is the Active server skip to step 4, otherwise perform the following:

# cd /usr/TKLC/plat/sbin/

# ./ hafailover –goactive

# hastatus

ACTIVE

 

4.  

Verify updates to <HEALTHY_ELAP>  Real Time DataBase (RTDB).

5.  

Perform RTDB backup on <HEALTHY_ELAP>. 

Do not proceed until RTDB backup is completed!!!!!

  

6.  

  

# su - elapconfig

 

/-----ELAP Configuration Menu----------\
/----------------------------------------\
|  1 | Display Configuration             |
|----|-----------------------------------|
|  2 | Configure Network Interfaces Menu |
|----|-----------------------------------|
|  3 | Set Time Zone                     |
|----|-----------------------------------|
|  4 | Exchange Secure Shell Keys        |
|----|-----------------------------------|
|  5 | Change Password                   |
|----|-----------------------------------|
|  6 | Platform Menu                     |
|----|-----------------------------------|
|  7 | Configure NTP Server              |
|----|-----------------------------------|
|  8 | Mate Disaster Recovery            |
|----|-----------------------------------|
|  e | Exit                              |
\----------------------------------------/

 

 

Enter Choice: 6

 

7.  

 

/-----ELAP Platform Menu-\
/--------------------------\
|  1 | Initiate Upgrade    |
|----|---------------------|
|  2 | Eject CD            |
|----|---------------------|
|  3 | Reboot MPS          |
|----|---------------------|
|  4 | Halt MPS            |
|----|---------------------|
|  5 | MySQL Backup        |
|----|---------------------|
|  6 | RTDB Backup         |
|----|---------------------|
|  e | Exit                |
\--------------------------/

 

Enter Choice: 6

 

ELAP software is running.  Stop it? [N]: Y

8.  

Confirm option to start RTDB backup.

 

Are you sure you want to back up the RTDB database on Multi-Purpose Server (MPS) A to "/var/TKLC/appl/free/rtdbBackup_mps-elap2-a_20080222100724.tar"? [N]: Y

 

9.  

# manageBannerInfo –l

“RTDB Backup Completed Successfully”

Do not proceed until RTDB backup is complete.

  

10.

Start ELAP SW on <HEALTHY_ELAP> 

# service Epap start

 

11.

Verify status GUI->RTDB-> View RTDB status for  <HEALTHY_ELAP> and syscheck.

# syscheck

 

12.

Verify updates to ELAP RTDB via GUI->RTDB-> View RTDB status.

13.

Customer will verify updates to DSMs

This procedure is complete.

3. E5-APP-B ELAP Card Replacement (ELAP 10.0 and Above)

This procedure will be executed by a Oracle TAC Engineer to replace a faulty E5-APP-B ELAP card.

Below is a list of steps to replace a faulty E5-APP-B ELAP card.

 

S

T

E

P

#

Activity or Result Description

This entire procedure should take approximately 30 minutes.

 

 1.

Log into the <FAULTY_ELAP> via minicom from the known good ELAP card.

 2.

Display and observe the Tekelec Platform revision (TPD).

  

# getPlatRev

z.z.z-zz.zz.z

 

 3.

Observe the output from the rpm query and note the release (output is for reference only)

  

# rpm -qi TKLCelap

Name        : TKLCelap                     Relocations: (not relocatable)

Version     : 5.0.16                            Vendor: Tekelec
Release     : 10.0.0_100.17.0               Build Date: Thu 27 Jun 2013 03:37:09 PM EDT
Install Date: Mon 10 Mar 2014 11:17:49 AM EDT      Build Host: diablo-10.tekelec.com
Group       : Development/Build             Source RPM: TKLCelap-5.0.16-10.0.0_100.17.0.src.rpm
Size        : 127827675                        License: © TEKELEC 2013
Signature   : (none)
Packager    : <@tekelec.com>
URL         : http://www.tekelec.com/
Summary     : Tekelec ELAP Package 
Description :
 
This is the Tekelec ELAP Package. The package installs ELAP software.
Eagle LNP Application Processor (ELAP) provides REALLY INCREDIBLE Database (RIDB).
ELAP provides the LNP feature.

 4.

Make sure the <FAULTY_ELAP> server is the Standby server.

# hastatus

STANDBY

 

If it is the Standby server skip to step 5, otherwise perform the following:

  

# hastatus

ACTIVE

 

# cd /usr/TKLC/plat/sbin/

# ./ hafailover –gostandby

# hastatus

STANDBY

 

 5.

Perform a shutdown –h to halt the <FAULTY_ELAP> server.  Once the server has been halted, the onsite contact can down disengage the Ejector switch and replace the <FAULTY ELAP> card.

 

 1. On the APP-B card, slide the Ejector switch (4) up to the UNLOCKED position. See figure above.

 3_5_a

 2. Wait for the E5APPB Eject Status Ligth-Emitting Diode (LED) to go from blinking red to a steady read

 3. Grasp the upper and lower card Inject/Eject (I/E) lever release (3) just underneath the I/E lever, and press it to meet the I/E lever. This is the mechanical interlock for the card.

3_5_b

 4. While holding the I/E interlock and lever, pull the levers (2) away from the shelf until they are parallel to the floor.

 5. Remove the E5APPB card from the Eagle Shelf.

 

 6.

Power on <FAULTY_ELAP> server by engaging the ejector switch to the LOCKED position on the front of the E5-APP-B ELAP card.

Verify that server boots normally.

Note: The E5-APP-B Card should arrive in the LOCKED state. If it arrives UNLOCKED, skip to step

4.

  1. On the APP-B card, slide the Ejector switch (4) up to the UNLOCKED position. See figure to the right.3_6_a
  2. Grasp the upper and lower card Inject/Eject (I/E) lever release (3) just underneath the I/E lever, and press it to meet the I/E lever. This is the mechanical interlock for the card.3_6_b
  3. While holding the I/E interlock and lever, pull the levers (2) away from the card until they are parallel to the floor.
  4. Insert the E5-APP-B card into the EAGLE shelf. Carefully align the edges of the card with the top and the bottom card guides. Then, Push the card along the length of the card guides until the rear connectors on the card engage the mating connectors of the target shelf backplane.
  5. Push in the top and bottom inject/eject clamps. This locks the card in place and ensures a strong connection with the pins on the target shelf backplane. See figure to the left.
  6. Slide the E5-APP-B H/S switch (4) down to the LOCKED position and WAIT for the E5-APP-B Eject Status LED to go from blinking red to off. See figure below.3_6_c

Note: When the Ejector switch goes from UNLOCKED to LOCKED, the E5-APP-B Eject Status LED blinks blue as the E5-APP-B card goes online.

 

 7.

Log into <NEW_ELAP>  as root.

 8.

Display and observe the Tekelec Platform revision (TPD) and verify it matches with the TPD from FAULTY_ELAP (step 2).

# getPlatRev

z.z.z-zz.zz.z

 

 9.

Observe the output from the rpm query and note the release. (output is for reference only)

Verify it matches with release from FAULTY_ELAP (step3).

# rpm -qi TKLCelap
Name        : TKLCelap                     Relocations: (not relocatable)
Version     : 5.0.16                            Vendor: Tekelec
Release     : 10.0.0_100.17.0               Build Date: Thu 27 Jun 2013 03:37:09 PM EDT
Install Date: Mon 10 Mar 2014 11:17:49 AM EDT      Build Host: diablo-10.tekelec.com
Group       : Development/Build             Source RPM: TKLCelap-5.0.16-10.0.0_100.17.0.src.rpm
Size        : 127827675                        License: © TEKELEC 2013
Signature   : (none)
Packager    : <@tekelec.com>
URL         : http://www.tekelec.com/
Summary     : Tekelec ELAP Package
Description :
 
This is the Tekelec ELAP Package. The package installs ELAP software.
Eagle LNP Application Processor (ELAP) provides REALLY INCREDIBLE Database (RIDB).
ELAP provides the LNP feature.

 10.

If the TPD or the current release installed are different from the ones on FAULTY_ELAP, need to install the correct TPD and ELAP Application following APPENDIX B  – IPM AND ELAP 10 INSTALLATION, otherwise, skip to next step.

 

 11.

Switch user to platcfg. Then select “Server Configuration” Menu

# su - platcfg

  

 3_11

 12.

Select “Designation/ Function” Menu

 3_12

 

 13.

Verify that the Designation and function information is correct then select and press “Exit”. On initial install, these fields are blank.

Expected values: The Designation as “1A” on Server A or as “1B” on Server B, Function as “ELAP”.

 3_13_a

3_13_b 

 

 14.

If the Designation ID is not correct then perform Appendix B-1 Steps 24-25, otherwise, skip to next step.

 15.

Select Time Zone

3_15 

 

 16.

Verify the Time Zone is correct.

3_16 

 

 17.

If the Time Zone is not correct then perform Appendix B-1 Steps 27-29, otherwise, skip to next step.

 18.

Reboot the server following steps on Appendix B-1 as indicated below:

A server: 34-37

B server: 30-33

 19.

Exit minicom session to return back to  < HEALTHY_ELAP>.

 20.

Display configuration to gather the server configuration data.

# su – elapconfig

  
/-----ELAP Configuration Menu----------\
/----------------------------------------\
|  1 | Display Configuration             |
|----|-----------------------------------|
|  2 | Configure Network Interfaces Menu |
|----|-----------------------------------|
|  3 | Set Time Zone                     |
|----|-----------------------------------|
|  4 | Exchange Secure Shell Keys        |
|----|-----------------------------------|
|  5 | Change Password                   |
|----|-----------------------------------|
|  6 | Platform Menu                     |
|----|-----------------------------------|
|  7 | Configure NTP Server              |
|----|-----------------------------------|
|  8 | Mate Disaster Recovery            |
|----|-----------------------------------|
|  e | Exit                              |
\----------------------------------------/

 

Enter Choice: 1

 

 21.

Configure the <FAULTY_ELAP> server by performing the Mate Disaster Recovery procedure from the <HEALTHY_ELAP> server.

 22.

/-----ELAP Configuration Menu----------\
/----------------------------------------\
|  1 | Display Configuration             |
|----|-----------------------------------|
|  2 | Configure Network Interfaces Menu |
|----|-----------------------------------|
|  3 | Set Time Zone                     |
|----|-----------------------------------|
|  4 | Exchange Secure Shell Keys        |
|----|-----------------------------------|
|  5 | Change Password                   |
|----|-----------------------------------|
|  6 | Platform Menu                     |
|----|-----------------------------------|
|  7 | Configure NTP Server              |
|----|-----------------------------------|
|  8 | Mate Disaster Recovery            |
|----|-----------------------------------|
|  e | Exit                              |
\----------------------------------------/

 

Enter Choice: 8


WARNING: Are you sure you want to run Disaster Recovery on Mate? [N]: Y

Exchanging Keys with Mate...

Password of elapdev: 

Could not get authorized keys file from remote (mate).

Maybe it does not exist.  Continuing...

ssh is working correctly.

Password of root: 

Could not get authorized keys file from remote (mate).

Maybe it does not exist.  Continuing...

ssh is working correctly.

Updating /etc/hosts...

Reconfiguring DRBD...

Updating the Provisioning Network (This may take a while)...

Updating the DSM Network...

Configuring NTP servers for Mate...

Updating mate hostname in EuiDB from mps-3008-b to mps-3025-b...

Finalizing Disaster Recovery Procedure...

 

  -- Initial Disaster Recovery of side A successful --

 

Press return to continue...

 23.

Verify configuration is correct.

/-----ELAP Configuration Menu----------\
/----------------------------------------\
|  1 | Display Configuration             |
|----|-----------------------------------|
|  2 | Configure Network Interfaces Menu |
|----|-----------------------------------|
|  3 | Set Time Zone                     |
|----|-----------------------------------|
|  4 | Exchange Secure Shell Keys        |
|----|-----------------------------------|
|  5 | Change Password                   |
|----|-----------------------------------|
|  6 | Platform Menu                     |
|----|-----------------------------------|
|  7 | Configure NTP Server              |
|----|-----------------------------------|
|  8 | Mate Disaster Recovery            |
|----|-----------------------------------|
|  e | Exit                              |
\----------------------------------------/

Enter Choice: 1

 

 24.

Exit out of the elapconfig menu.

 25.

ssh mate to <FAULTY_ELAP>

#ssh mate

  

 26.

Verify that the <FAULTY_ELAP> server is the Standby server.

#hastatus

Standby

 27.

Perform syscheck on the ELAP A and B servers to verify no alarms are present.

 28.

Review platform configuration:

Repeat steps 11-16

If any difference, contact Technical Support Center for ASSISTANCE.

 29.

Verify with the customer that the RTDB and DSMs are taking updates.

This procedure is complete!

 

Appendix A: ISO Image copy from USB Media

S

T

E

P

#

This procedure provides instructions to copy an ISO image from an USB media to the E5-APP-B cards.

 

Check off each step as it is completed. Boxes have been provided for this purpose under each step number.

 

If this procedure fails, contact Oracle Technical Services AND ASK FOR UPGRADE ASSISTANCE.

 

 1.      

MPS X: Insert USB.

Insert media in USB drive on the E-APP-B card.

 

 2.      

MPS X: Log in to the server as the “root” user.

  

[hostname] consolelogin: root

password: password

  

 3.        

 

MPS X: Run syscheck to make sure there is no error.

Execute the following command:

# syscheck

The output should look like:

Running modules in class proc...

                                 OK

Running modules in class services...

                                 OK

Running modules in class system...

                                 OK

Running modules in class disk...

                                 OK

Running modules in class hardware...

                                 OK

Running modules in class net...

                                 OK

LOG LOCATION: /var/TKLC/log/syscheck/fail_log

 

 4.      

 

MPS X: Verify ISO image doesn’t already exist.

Execute the following command to perform directory listing:

# ls –al /var/TKLC/upgrade

The output should look like:

total 16

dr-xr-xr-x   2 root root 4096 Oct 22 16:31 .

dr-xr-xr-x  21 root root 4096 Oct 18 13:40 ..

 

If an ISO image exists, remove it by executing the following command:

# rm –f /var/TKLC/upgrade/<ISO image


 5.        

 

MPS X: Delete unwanted ISOs from USB media.

Execute the following command to create a directory to mount the USB media:

# mkdir -p /mnt/usb

Execute the following command to get the USB drive name:

# fdisk -l |grep FAT

  

The output should look like:

/dev/sdc1   *           1         812      831472    6  FAT16

 

Execute the following command to mount the USB media using the USB drive name from the output above:

# mount /dev/sdc1 /mnt/usb

 

  

Execute the following command to perform directory listing and verify the file name format is as expected:

# ls -al /mnt/usb

The output should look like:

total 629400

dr-xr-xr-x  2 root root      4096 Oct 16 13:33 .

dr-xr-xr-x 22 root root      4096 Oct 16 13:55 ..

-rw-r--r--  1 root root 643852288 Oct 15 15:37 872-2558-101-10.0.0_100.1.0-ELAP-x86_64.iso

 

Only one ISO file should be listed, if additional files are listed, execute the following command to remove unwanted ELAP ISOs:

  

# rm –f /mnt/usb/<ISO_NAME>.iso

For e.g.,

# rm –f /mnt/usb/872-2558-101-10.0.0_100.1.0-ELAP-x86_64.iso

 

Execute the following command to unmount the USB media:

# umount /mnt/usb

 

 6.        

 

MPS X: Verify space exists for ISO.

Execute the following command to verify the available disk space:

# df -h /var/TKLC

The output should look like:

Filesystem            Size  Used Avail Use% Mounted on
/dev/md8              4.0G   89M  3.7G   3% /var/TKLC

 

Verify that there is at least 620M in the Avail column.  If not, clean up files until there is space available.

  

CAUTION: Make sure you know what files you can remove safely before cleaning up.  It is recommended that you only clean up files in the /var/TKLC/upgrade directory as this is a platform owned directory that should only contain ISO images.  This directory should not be expected to contain images for any length of time as they can get purged.  Contact Technical Services beforehand if removing files other than the /var/TKLC/upgrade directory as removing files is dangerous.

 

 7.      

MPS X: Start platcfg utility by logging in as user “platcfg”.

# su - platcfg

  

 8.        

 

MPS X: Select the Maintenance menu.

On the Main Menu of the Platform Configuration Utility, select Maintenance and press [ENTER].

elap_app_a_8 

 

 9.         

MPS X: Select the Upgrade menu.

Select the Upgrade menu and press [ENTER].

elap_app_a_9 

 

 10.     

MPS X: Select Copy USB Upgrade Image menu.

Select the Copy USB Upgrade Image menu and press [ENTER].

 elap_app_a_10

 

 11.     

 

MPS X: The ELAP ISO will be copied from the USB media to /var/TKLC/upgrade.

 

Press any key to return to Upgrade menu.

Copying /mnt/upgrade/872-2558-101-10.0.0_100.1.0-ELAP-x86_64.iso...

 

PRESS ANY KEY TO RETURN TO THE PLATCFG MENU.

 12.     

 

MPS X: Exit platcfg.

Select Exit and press [ENTER] repeatedly until the “platcfg” utility terminates.

 

elap_app_a_12 

 

 13.     

 

MPS X: Verify ISO image exists.

Execute the following command to perform directory listing:

# ls –al /var/TKLC/upgrade

The output should look like:

total 16
dr-xr-xr-x   2 root root 4096 Oct 22 16:31 .
dr-xr-xr-x  21 root root 4096 Oct 18 13:40 ..
-rw-r--r--  1 root root 643852288 Oct 15 15:37 872-2558-101-10.0.0_100.1.0-ELAP-x86_64.iso

 

Repeat this procedure from step 5 if ELAP ISO file is not as expected.

 

 14.     

 

MPS X: Logout from server.

Logout from the server by executing the following command:

# logout

 

 15.     

 

MPS X: Remove USB media.

Remove media from USB drive.

This procedure is complete!

Appendix B  – Initial Product Manufacture (IPM) and ELAP 10 Installation

Appendix B-1. IPM MPS Server with TPD 5

Assumption: The E5-APP-B servers are IPM’d to the desired TPD version, if not IPM’d ask for Assistance.

S

T

E

P

#

This procedure will remove the ELAP Application and all the data from the server.

Note:   Estimated time of completion is 45 minutes.

Check off (Ö) each step as it is completed. Boxes have been provided for this purpose under each step number.

Should this procedure fail, Contact ORACLE technical services and ask for ASSISTANCE.

 1.

 

 

MPS X:  Insert TPD 5 USB into MPS X.

 

Insert TPD 5 USB into MPS X.

 

 2.

 

 

MPS X:  If necessary, log in to server as the user “root”

If not already logged in to the MPS server, then login as user “root”.

console login:  root

password:   <root_password>

  

 3.

 

 

MPS X:

Reboot server

 

 

# init 6

Upon restarting the server, enter the BIOS setup utility. If onsite and connected to the server press the DEL key when the message is displayed or use F4 on a remote keyboard.

 

 4.

MPS X:

Verify the System Time & Date are correct.  If the System Time & Date do not match the current time/date then make the necessary changes.

 

Caution: The TPD will fail if the System Time and Date do not match.

  

 

 elap_app_b_4

Caution: The TPD will fail if the System Time and Date do not match.

  

 

 5.

MPS X:

Select the Boot Settings and then select Hard Disk Drives.

 

 

 

 

elap_app_b_5 

 6.

MPS X:

Change the 1st Drive to USB:SMART USB.  The server will now boot from the TPD 5 USB drive.

 

 

 elap_app_b_6_a

 elap_app_b_6_b

 

 

 7.

MPS X:

Press ESC then select Save Changes and Exit on the main Exit screen.  The server will now boot.

 

elap_app_b_7

 

 

 

 

 8.

MPS X:

Start the IPM process by entering the TPD scrub command at the boot prompt.

boot: TPD scrub reserved=20G

  

 

  

****Note: The reserved=20G must be included!!!****

  

 9.

MPS X:

After entering the command to start the installation, the Linux kernel will load, as in the screenshot at right.

 

 elap_app_b_9

 

 10.

MPS X:

After a few seconds, additional messages will begin scrolling by on the screen as the Linux kernel boots, and then the drive formatting and file system creation steps will begin.

 

 elap_app_b_10

 

 

 11.

MPS X:

Once the drive formatting and file system creation steps are complete, the screen at right will appear indicating that the package installation step is about to begin.

 

 elap_app_b_11

 

 

 12.

MPS X:

After a few minutes, you will see a screen similar to that at right, showing the status of the package installation step. For each package, there will be a status bar at the top indicating how much of the package has been installed, with a cumulative status bar at the bottom indicating how many packages remain. In the middle, you will see text statistics indicating the total number of packages, the number of packages installed, the number remaining, and current and projected time estimates.

 

 elap_app_b_12

 

 

 13.

MPS X:

Once all the packages have been successfully installed, the screen at right will appear letting you know the installation process is complete. Remove the installation media (USB) and then press <ENTER> to reboot the system.

 

 elap_app_b_13

 

 14.

MPS X:

Select the Boot Settings and then select Hard Disk Drives.

 

 

 

 elap_app_b_14

 

 15.

MPS X:

Change the 1st Drive back to HDD: P0-Intel SSDSA.

 

 

 

 elap_app_b_15_a

 elap_app_b_15_b

 

 

 16.

MPS X:

Press ESC then select Save Changes and Exit on the main Exit screen.  The server will now boot.

 

 

 elap_app_b_16

 

 

 

 17.

MPS X:

After a few minutes, the BIOS screen will appear, followed by several messages about each of the Ethernet ports in the system, and then by the following message printed by the boot loader, indicating that it is booting the new IPM load.

 

 elap_app_b_17

 

 

 18.

E5-APP-B X:  log in to server as the user “root”

console login:  root

password:   <root_password>

 19.

E5-APP-B X:

Switch user to platcfg.

 

Select “Server Configuration” Menu

# su - platcfg

  

 elap_app_b_19

 

 20.

E5-APP-B X:

Select “Hostname” Menu

 

 

 elap_app_b_20

 

 21. 

E5-APP-B X:

1) Select “Edit” from the options dialogue box.

2) Set the hostname

 

 

 elap_app_b_21_a

 elap_app_b_21_b

 

 22.

E5-APP-B X:

Verify that the Hostname is correct then select and press “Exit”.

 

Otherwise repeat the step above.

 

 elap_app_b_22_a

 elap_app_b_22_b

 

 23.

E5-APP-B X:

Select “Designation/ Function” Menu

 

 elap_app_b_23

 24.

E5-APP-B X:

1) Select “Edit” from the options dialogue box.

2) Set the Designation as “1A” on Server A and as “1B” on Server B, Function as “ELAP” and press “OK”.

 

NOTE:

Designation and Function should be entered in UPPERCASE.

 

 elap_app_b_24_a

 elap_app_b_24_b

 

 

 25.

E5-APP-B X:

Verify that the Designation and Hostname information is correct then select and press “Exit”. Continue selecting “Exit”until you exit platcfg.

 

Otherwise repeat the step above.

 

 

 elap_app_b_25_a

 elap_app_b_25_b

 

 

 26.

E5-APP-B ELAP X:

Select Time Zone

 

elap_app_b_26 

 

 27.

E5-APP-B ELAP X:

Edit the Time Zone configuration as needed.

 

 

 elap_app_b_27

 

 28.

E5-APP-B ELAP A:

Select the Time Zone as needed.

Use Tab key or right key to select and change to other options.

Skipped this step if no Time Zone change is needed.

 

 

 elap_app_b_28

 

 29.

E5-APP-B ELAP A:

Exit the server configuration menu

NOTE:

DO NOT set the time zone in platcfg.

The time zone will be set later in epapconfig.

 

 

 elap_app_b_29

 

 30.

E5-APP-B ELAP A:

Log into the ELAP B server via minicom.

[root@mps-a ~]# minicom mate

 

 31.

E5-APP-B ELAP B:

 Reboot server

 

 

# init 6

Upon restarting the server, enter the BIOS setup utility. If onsite and connected to the server press the DEL key when the message is displayed or use F4 on a remote keyboard.

 

 32.

E5-APP-B ELAP B:

Verify the System Time & Date are correct.  If the System Time & Date do not match the current time/date then make the necessary changes.

 

 

 elap_app_b_32

 

 

 33.

E5-APP-B ELAP B:

Press ESC then select Save Changes and Exit on the main Exit screen.  The server will now boot.

 

 

 elap_app_b_33

 

 

 

 34.

E5-APP-B ELAP B:

Log into the ELAP A server via minicom.

[root@mps-b ~]# minicom mate

 

 35.

E5-APP-B ELAP A:

 Reboot server

# init 6

Upon restarting the server, enter the BIOS setup utility. If onsite and connected to the server press the DEL key when the message is displayed or use F4 on a remote keyboard.

 36.

E5-APP-B ELAP A:

Verify the System Time & Date are correct.  If the System Time & Date do not match the current time/date then make the necessary changes.

 

 

 elap_app_b_36

 

 

 37.

E5-APP-B ELAP A:

Press ESC then select Save Changes and Exit on the main Exit screen.  The server will now boot.

 

 

 elap_app_b_33

 

 

 

This procedure is complete!

 

Appendix B-2. ELAP Installation and Server Configuration

Note: ELAP can be installed together on the MPS-A and MPS-B servers.

S

T

E

P

#

This procedure will install the ELAP application on the server.

Note:   Estimated time of completion is 45 minutes.

Check off (Ö) each step as it is completed. Boxes have been provided for this purpose under each step number.

Should this procedure fail, Contact ORACLE technical services and ask for ASSISTANCE.

 1.

 

 

E5-APP-B X:

log in to the server as the user “root”

  

console login:  root

password:   <root_password>

  

 2.

 

E5-APP-B X:

Copy ELAP 10.0 ISO using Appendix A or  transfer an ELAP 10.0 ISO image to /var/TKLC/upgrade directory.

 

 3. 

 

E5-APP-B X:

Run the command ”su -platcfg”.

Use the “Arrow” and the [ENTER] keys to navigate the Menu options as shown to choose the upgrade media.

 

 

 

 

 

# su - platcfg

 

1. elap_app_b2_3_a

 

2. elap_app_b2_3_b

 

3. elap_app_b2_3_c

4. elap_app_b2_3_d

   

 

 4.

 

E5-APP-B X:

Select the proper upgrade media and press [ENTER]

 

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.

 

 elap_app_b2_4

(output truncated for display purpose)

login:

 

 5.

 

E5-APP-B X:

Login as root user.

login: root

Password : <root_password>

 6.

 

E5-APP-B X:

Verify that installation is complete and no error occurred during installation.

  

# grep "UPGRADE IS COMPLETE" /var/TKLC/log/upgrade/upgrade.log

1609483273::  UPGRADE IS COMPLETE

#

 

# grep -i error /var/TKLC/log/upgrade/upgrade.log

 

  

Check the output of the upgrade log, Contact the Technical Assistance Center if the output contains any errors beside the following:

Variable and RPMs that might contain the word error in them

Example:

1609483240::perl-Class-ErrorHandler     ##################################################

1609483260::Checking perl-Class-ErrorHandler-0.01-0.41060.noarch.rpm:  PASSED

 

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

 7.

 

E5-APP-B X:

Verify ELAP release.

# rpm -qi TKLCelap

Name        : TKLCelap                     Relocations: (not relocatable)

Version     : 5.0.1                             Vendor: Tekelec
Release     : 10.0.0_100.1.0                Build Date: Wed 19 Dec 2012 05:31:28 PM EST
Install Date: Mon 31 Dec 2001 09:28:29 PM EST      Build Host: diablo-9.tekelec.com
Group       : Development/Build             Source RPM: TKLCelap-5.0.1-10.0.0_100.1.0.src.rpm
Size        : 127154002                        License: © TEKELEC 2013
Signature   : (none)
Packager    : <@tekelec.com>
URL         : http://www.tekelec.com/
Summary     : Tekelec ELAP Package
Description :
 
This is the Tekelec ELAP Package. The package installs ELAP software.
Eagle LNP Application Processor (ELAP) provides REALLY INCREDIBLE Database (RIDB).
ELAP provides the LNP feature.

#

This procedure is complete!


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback