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-2144084.1
Update Date:2017-09-22
Keywords:

Solution Type  Technical Instruction Sure

Solution  2144084.1 :   CommsGBU Network Support Signaling Solutions Oracle Communications Eagle Element Management System (OCEEMS/E5-MS) Customer Notebook  


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




In this Document
Goal
Solution
 Introduction
 Customer OCEEMS Server
 CUSTOMER OCEEMS Server Configuration
 Licenses and rpm file
 OCEEMS server license
 i-net Reporting Studio license
 Hardware, software release and serial number details of OCEEMS server
 Hardware
 OCEEMS Software Release Information
 System IP matrix
 User details
 Eagle Configuration details of OCEEMS server
 Eagle discovery snapshot for OCEEMS server
 Time Zone
 System backup
 FTP measurement
 NBI configuration
 
 
 
 EPAP and LSMS configuration (if used)
 Java and MySQL version
 Miscellaneous
 Remote login procedure:
 ATP document
 Customizations
 Issues encountered during the project
References


Applies to:

Oracle Communications EAGLE (Hardware) - Version E5-MS 45.0 and later
Oracle Communications EAGLE (Software) - Version E5-MS 45.0 and later
Information in this document applies to any platform.

Goal

The goal is to provide the Oracle Support and Consulting Teams, as well as the Oracle Partners, with the necessary documentation and instructions to collect all the relevant data and create the OCEEMS Customer Notebook, mandatory to complete the OCEEMS Project Handoff process.

Solution

Introduction

Create a document containing all the information explained in this document and attach it to the SR created for the Hand-off process.

Customer OCEEMS Server

Example

The OCEEMS server in the Customer network is a standalone server connected with the Eagles as shown in the network connectivity diagram in below section.

(Embed network connectivity diagram)

The OCEEMS server is connected with the NMS server. The snmp traps are forwarded to NMS server, the OCEEMS server is also connected with the Eagles on SSH connection. The subsequent sections or chapters cover the complete details of the customer's network, OCEEMS server configuration and implementation.

The figure above shows the customer's OCEEMS server connectivity with the NMS server and EAGLE’s in the customer's network. There are X live/production Eagle STP’ connected with the OCEEMS server. These X Eagles are on SSH connection.

There is also one lab Eagle STP connected to OCEEMS server on SSH connection.

Features purchased and implemented in CUSTOMER (OCEEMS server) are tabulated below:

PART NUMBER

DESCRIPTION

Quantity

     
     
     
     
     
     

CUSTOMER OCEEMS Server Configuration

This section details the configuration related to the OCEEMS server, licenses, hardware and software release, ports info and login credentials.

Licenses and rpm file

Example

A copy of license of OCEEMS is present on the OCEEMS server in the root directory name of the license file is=”XXXXXX-Customer Communication AG-5afbwGR1W5” this license file is present in the root/license directory of OCEEMS server as shown in the snapshot shown below;

License file in /root/license :

Rpm file /root/OCEEMS_rpm :

 

OCEEMS server license

(Embed license file)

i-net Reporting Studio license

 (Embed license file)

Hardware, software release and serial number details of OCEEMS server

Hardware

LOCATION

 

HOSTNAME

 

ETHERNET ADDRESS

 

IP ADDRESS / SUBNET

 

MACHINE ID

 

SERVER MODEL / SERIAL NUMBER

 

HDD SIZE

 

MEMORY CAPACITY

 

OCEEMS Software Release Information

APPLICATION

SOFTWARE RELEASE

SOFTWARE RELEASE in  production/Live system

OCEEMS

 

 

Centos -OS

 

 

 

System IP matrix

APPLICATION

IP

PORT

REMARKS

OCEEMS

 

 

 

NMS

 

 

 

The IP matrix used for OCEEMS server is tabulated above:

The IP used for the OCEEMS application reporter is listed above.

  • GUI URL: https://X.X.X.X:XXXX

User details

APPLICATION

USER DETAILS CLLI

USER DETAILS GUI

REMARKS

OCEEMS

UID  =
Password =

 

 

OCEEMS and FTP measurement

UID =

Password= 

N/A

 

Eagle Configuration details of OCEEMS server

The following table shows the details of the Eagles defined in eagle discovery. 

EAGLE

TERMINAL TYPE

IP

USERID & PASSWORD

TERMINAL NUMBER

Site Name

 

SSH

IPSM1=

IPSM2=

UID=
PASSWORD=

IPSM1 : TRM=X
IPSM2 : TRM=X

Site Name

SSH

IPSM1=

IPSM2=

UID=
PASSWORD=

IPSM1 : TRM=X
IPSM2 : TRM=X

Site Name

SSH

IPSM1=

IPSM2=

UID=
PASSWORD=

IPSM1 : TRM=X
IPSM2 : TRM=X

Eagle discovery snapshot for OCEEMS server

Add below snapshots details the eagles defined in the eagle discovery module of OCEEMS server:

 

Time Zone

Add snapshot displaying the current time zone set for OS.

System backup

System back-up & restoration of OCEEMS server was tested as part of the ATP. (YES/NO)

The backup for OCEEMS server is setup to run automatically and the path is : Add the path.

FTP measurement

Add this information Whether MCPM or Integrated Measurements, or both, are installed

Example

The Eagle STPs send their measurement files to the E5MS server for the link utilization feature to be able fetch link data.

Configuration details are as follow:

APPLICATION

USER DETAILS

Destination folder

Measurement  Reports Schedule

Subsystem Status

REMARKS

OCEEMS and FTP measurement

 

 

 

 

 

NBI configuration

Add screen grabs of the NBI configuration if NBI is used for Alarm forwarding, including configuration of each North bound destination. And screen grabs of the NBI configuration if FTP measurement file forwarding is used.

Example

The E5MS server forwards the alarms received to an external NMS (Netcool).

The NBI is configured as follow:

IP

NBI System

Port

Community

 

 

 

 

 

 

 

 

 

 

 

 

EPAP and LSMS configuration (if used)

 

Java and MySQL version

Add the details regarding the Java and MySQL versions.

Miscellaneous

Remote login procedure:

Embed the remote access procedure and confirm whether or not it is in place.

ATP document

Embed the ATP document.

Customizations

Add full details of any system customization (customer i-net reports, Cron scripts, etc…)

Issues encountered during the project

Add the details, including solution/workaround, of all the issues encountered during the project deployment.

References

<NOTE:2141679.1> - (CommsGBU Network Support) Signaling Solutions Project Handoff Guidelines

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