Table Of Contents
Installing, Starting, and Logging into EPOM
Learning About EPOM
Installing EPOM
Configuring RADIUS Server for EPOM Authentication
Starting EPOM
Logging Into EPOM
Installing, Starting, and Logging into EPOM
Learning About EPOM
Extensible Provisioning and Operations Manager (EPOM) is a web-based application for real-time provisioning of the BTS. It allows EPOM users to easily Show, Add, Edit, Delete, and view the status of BTS components. EPOM provisioning generally matches that done using CLI or MAC. EPOM tasks are done via a web-browser. Common multi-step procedures are simplified by being grouped into tasks completed by wizards.
The EPOM database maintains administrative data (EPOM users, groups, and domains) and BTS device inventory. EPOM users view device-level information (like subscribers, features, and media gateway communications) as it is retrieved from EMS servers in real time; it is not stored in the EPOM database.
Table 1-1 EPOM Requirements
Device/Software
|
Requirement
|
EPOM Server
supporting 5 simultaneous remote client and 5 BTS servers
|
• Sun workstation (440 MHz or more)
•1 GB RAM
•2 GB disk space
•Sun Solaris 8/10
|
EPOM Server
supporting 20 simultaneous remote client and 10 BTS servers
|
•Sun Ultra-60 workstation (440 MHz or faster, dual processor)
•2 GB RAM
•4 GB disk space
•Sun Solaris 8/10
|
Port defaults
|
•MySQL—3310
•Tomcat non-secure—8080
•Tomcat secure—443
•Tomcat shutdown—8041
|
EPOM Client Windows
|
•Microsoft Internet Explorer, Version 5.5 or higher
•Netscape 6.2 or higher
|
EPOM Client Solaris
|
Mozilla 1.1 or higher
|
Cisco BTS 4.5.0 with Secure or Non Secure OpenOrb CORBA
|
EPOM 4.5
|
Cisco BTS 5.0 with Secure or Non Secure OpenOrb CORBA
|
EPOM 5.0
|
External RADIUS Server
|
Any platform capable of running Radius IETF (International Engineering Task Force)
Radius software must implement RADIUS IETF protocol.
|
Installing EPOM
During installation EPOM does the following:
•creates and initializes a database that stores
– EPOM user IDs
–login passwords
–group information
–device inventories
•creates the following two directories:
–Application directory—/opt/CSCOepom. Do not create or modify any of the files in this directory.
–Data directory—var/opt/CSCOepom . Log files and live data are here.
If it detects an existing database, the installation script does not reinitialize the database. Cisco does not recommend reinitializing the database.
Before installing EPOM complete the tasks in this checklist.
Tasks
|
|
Ensure the BTS package is installed on the EMS primary and secondary servers.
|
|
Ensure CORBA is running on the EMS primary and secondary servers.
|
|
If you are using a RADIUS server, ensure it is running and configured with the following:
•logins
•shared secret keys
•EPOM server IP address /hostname
|
After completing the pre-install checklist, install EPOM:
Step 1 Change user to superuser:
su - root
Step 2 Download EPOM image from:
http://www.cisco.com/pcgi-bin/tablebuild.pl/epom50
Step 3 Extract tarfile:
tar -xvf epom-n_n_n_x-nnnnnnnn-n.tar
Step 4 Change working directory:
cd epom-n_n_n_x-nnnnnnnn-n
Step 5 Run Setup script:
./setup
Step 6 Remove installation image:
cd epom-n_n_n_x-nnnnnnnn-n
rm -f epom-n_n_n_x-nnnnnnnn-tar
rm -rf epom-n_n_n_x-nnnnnnnn-n
Configuring RADIUS Server for EPOM Authentication
Using an external RADIUS IETF Server is optional and based on the security needs of your company. If you are using a RADIUS server, ensure it is running and configured with the following:
•logins
•shared secret keys
•EPOM server IP address /hostname
To configure the RADIUS server, use the following parameters:
•radius.enable—set to yes
•radius.ip—set to IP address of RADIUS server
•radius.shared.secret—shared secret key for the IP address/hostname of the EPOM server. Shared secrets are the MD5 encryption algorithm key used by the RADIUS protocol. They are required in all RADIUS protocol communications. The shared secret value is known on each side of the communication but is never sent across the network.
•radius.authenticationPort—accept default ports unless you have modified them on the RADIUS server
•accountingPort—accept default ports unless you have modified them on the RADIUS server
Step 1 Log into the EPOM web server.
Step 2 Change user to superuser:
su - root
Step 3 Go to the main properties file:
cd /opt/CSCOepom/tomcat/webapps/ROOT/WEB-INF/classes/com/cisco/opus/
props
Step 4 Change the parameters as needed:
radius.authenticationPort=1812
radius.accountingPort=1813
Starting EPOM
Before starting EPOM complete the tasks in this checklist.
Tasks
|
|
Ensure you have the following information:
•Tomcat non-secure port number
•Tomcat secure port number
|
|
Select defaults displayed for a secure connection:
•If you are using the default port 443, enter:
https://EPOMhostname
or
https://IPaddress
•If you are using any other port, enter:
https://EPOMhostname:port number
or
https://IPaddress
Where
EPOMhostname/IPaddress—host machine where EPOM is installed or server IP address
port number
|
|
Select defaults displayed for an insecure connection:
•If you are using port 80, enter:
http://EPOMhostname
or
https://IPaddress
•If you are using any other port (default installed port is 8080), enter:
http://EPOMhostname:port number
or
https://IPaddress:port number
Where
EPOMhostname/IPaddress—host machine where EPOM is installed or server IP address
port number
|
After completing the pre-start checklist, start EPOM:
Step 1 From the EPOM web server:
/opt/CSCOepom/bin/epom start
The following appears:
% /opt/CSCOepom/bin/epom start
------------------------------------------------
------------------------------------------------
Step 2 Complete the InstallShield Wizard.
The following appears:
MySQL server is already started
-------------------------------------------------
-------------------------------------------------
Logging Into EPOM
Step 1 Launch a web browser.
Step 2 Access EPOM.
Step 3 Log in with the default admin account:
User Name: admin
Password: admin
Step 4 Click Login.
