![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Solution Type Technical Instruction Sure Solution 2144084.1 : CommsGBU Network Support Signaling Solutions Oracle Communications Eagle Element Management System (OCEEMS/E5-MS) Customer Notebook
In this Document
Applies to:Oracle Communications EAGLE (Hardware) - Version E5-MS 45.0 and laterOracle Communications EAGLE (Software) - Version E5-MS 45.0 and later Information in this document applies to any platform. GoalThe 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. SolutionIntroductionCreate a document containing all the information explained in this document and attach it to the SR created for the Hand-off process. Customer OCEEMS ServerExample 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:
CUSTOMER OCEEMS Server ConfigurationThis section details the configuration related to the OCEEMS server, licenses, hardware and software release, ports info and login credentials. Licenses and rpm fileExample 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 serverHardware
OCEEMS Software Release Information
System IP matrix
The IP matrix used for OCEEMS server is tabulated above: The IP used for the OCEEMS application reporter is listed above.
User details
Eagle Configuration details of OCEEMS serverThe following table shows the details of the Eagles defined in eagle discovery.
Eagle discovery snapshot for OCEEMS serverAdd 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 backupSystem 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 measurementAdd 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:
NBI configurationAdd 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:
EPAP and LSMS configuration (if used)
Java and MySQL versionAdd the details regarding the Java and MySQL versions. MiscellaneousRemote login procedure:Embed the remote access procedure and confirm whether or not it is in place. ATP documentEmbed the ATP document. CustomizationsAdd full details of any system customization (customer i-net reports, Cron scripts, etc…) Issues encountered during the projectAdd 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 GuidelinesAttachments This solution has no attachment |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|