Download as pdf or txt
Download as pdf or txt
You are on page 1of 64

HFR CE-EMS Guide

Administration

Version 1.4

NOTICE
This document contains proprietary and confidential material of HFR, Inc. Any unauthorized, reproduction, use or
disclosure of this material, or any part thereof, is strictly prohibited. This document is solely for the use of HFR
employees and any authorized customers or partners. HFR, Inc. reserves the right to make changes in the
specifications at any time and without notice.

Copyright © 2016 HFR, Inc.


HFR, Inc.

1. Document Information
This document describes method of using CE-EMS for Admin user.

Revision History

Version Date Updated Contents Authors


1.0 2016-02-01 First Draft document. (EMS: v1.2.4) Y.S.SHIN
1.1 2016-02-05 Update Document. (EMS: v1.2.4) Y.S.SHIN
1. Merge Installation Guide
2. Modify CE-EMS manual
1.2 2016-03-15 Update Document. (EMS: v1.2.5) Y.S.SHIN
1. Add compileJSP step
1.3 2016-04-20 Update Document. (EMS: v1.2.6) Y.S.SHIN
1. Modify HFR CE-EMS Installation
2. Modify CE-EMS manual
1.4 2016-04-28 Update Document. (EMS: v1.2.6) Y.S.SHIN
1. Add Discovery Option

References

Page 2
HFR, Inc.

2. Table of Contents
HFR CE-EMS Guide Administration .............................................................................................................................................. 1

1. Document Information ................................................................................................................................................................. 2

Revision History ....................................................................................................................................................................... 2

References .................................................................................................................................................................................. 2

2. Table of Contents ........................................................................................................................................................................... 3

3. HFR CE-EMS Installation .............................................................................................................................................................. 6

CE-EMS Back End Server Installation and Starting .................................................................................................. 6

3.1.1. CE-EMS BE Server Installation ................................................................................................................................... 6

3.1.1.1. GUI Mode through Install Shield ............................................................................................................... 6

3.1.1.2. Command / Console Mode ....................................................................................................................... 17

3.1.2. Procedure for Connecting BE Server to the JDBC Driver ........................................................................... 17

3.1.3. Start CE-EMS BE Server .............................................................................................................................................. 18

CE-EMS Front End Server Installation and Starting ............................................................................................... 21

3.2.1. CE-EMS FE Server Installation ................................................................................................................................. 21

3.2.1.1. GUI Mode through Install Shield ............................................................................................................. 21

3.2.1.2. Command / Console Mode ....................................................................................................................... 32

3.2.2. Procedure to Configure the FE Server ................................................................................................................ 32

3.2.2.1. FE and BE on Different Machines ............................................................................................................ 32

3.2.2.2. FE and BE on the Same Machine ............................................................................................................ 33

3.2.3. Procedure for Connecting FE Server to the JDBC Driver............................................................................ 33

3.2.4. Start CE-EMS FE Server .............................................................................................................................................. 34

CE-EMS Poller Server Installation and Starting ....................................................................................................... 34

3.3.1. CE-EMS Poller Server Installation .......................................................................................................................... 34

3.3.1.1. GUI Mode through Install Shield ............................................................................................................. 34

3.3.1.2. Command / Console Mode ....................................................................................................................... 39

3.3.2. Procedure for Connecting Poller Server to the JDBC Driver..................................................................... 39

3.3.3. Start CE-EMS Poller Server ....................................................................................................................................... 40

4. Discovery........................................................................................................................................................................................... 41

Page 3
HFR, Inc.

Discovery Parameter .................................................................................................................................................. 41

Discovery Criteria ........................................................................................................................................................ 42

Re-Discovery Scheduler ........................................................................................................................................... 43

Network Configuration ............................................................................................................................................. 43

Node Configuration ................................................................................................................................................... 44

Refresh Node ................................................................................................................................................................ 46

5. Security Administration .............................................................................................................................................................. 47

User Configuration ..................................................................................................................................................... 47

5.1.1. Add User ........................................................................................................................................................................... 47

5.1.2. Add Multiple ................................................................................................................................................................... 48

5.1.3. Change Status ................................................................................................................................................................ 48

5.1.4. Delete ................................................................................................................................................................................. 48

5.1.5. Modifying a User's Profile......................................................................................................................................... 49

5.1.6. Exporting User List ....................................................................................................................................................... 50

Group Configuration ................................................................................................................................................. 50

5.2.1. Add Group ....................................................................................................................................................................... 50

5.2.2. Delete ................................................................................................................................................................................. 51

5.2.3. Modifying a Group's Profile ..................................................................................................................................... 51

Operation Configuration .......................................................................................................................................... 52

6. Monitor/Management ................................................................................................................................................................ 53

WebNMS Details ......................................................................................................................................................... 53

6.1.1. Viewing Fault Status .................................................................................................................................................... 53

6.1.2. Viewing Port Details .................................................................................................................................................... 54

6.1.3. Viewing Discovery Status .......................................................................................................................................... 54

6.1.4. Scheduler Details .......................................................................................................................................................... 55

JVM Management ...................................................................................................................................................... 55

6.2.1. Back End Server Details ............................................................................................................................................. 56

6.2.2. Front End Server Details ............................................................................................................................................ 57

Page 4
HFR, Inc.

6.2.3. Client Details ................................................................................................................................................................... 57

6.2.4. Performance Status ...................................................................................................................................................... 58

Viewing Performance Status .................................................................................................................................. 58

7. Administrative Operations ........................................................................................................................................................ 60

Mail Server Settings ................................................................................................................................................... 60

WebNMS Backup ........................................................................................................................................................ 60

Shut down Server ....................................................................................................................................................... 60

8. Tools and Browsers ...................................................................................................................................................................... 62

Working with MIB Browser ..................................................................................................................................... 62

Viewing the Server Log Files .................................................................................................................................. 62

Viewing the Audit Trails ........................................................................................................................................... 62

9. Appendix A. ..................................................................................................................................................................................... 64

Page 5
HFR, Inc.

3. HFR CE-EMS Installation

• CE-EMS Back End Server Installation and Starting

• CE-EMS BE Server Installation

• Procedure for Connecting BE Server to the JDBC Driver

• Start CE-EMS BE Server

• CE-EMS Front End Server Installation and Starting

• CE-EMS FE Server Installation

• Procedure to Configure the FE Server

• Procedure for Connecting FE Server to the JDBC Driver

• Start CE-EMS FE Server

• CE-EMS Poller Server Installation and Starting

• CE-EMS Poller Server Installation

• Procedure for Connecting Poller Server to the JDBC Driver

• Start CE-EMS Poller Server

CE-EMS Back End Server Installation and Starting

3.1.1. CE-EMS BE Server Installation

3.1.1.1. GUI Mode through Install Shield

The GUI mode is an interactive GUI based installation mode.

Step to install CE-EMS Back-End Server

1. Download/Get the installation file (.bin file).


2. Check the executable permission of the .bin file. If the file is not executable, execute the
following command:
Ø chmod a+x <File Name>.bin [<File Name> is the corresponding .bin file]
3. Execute the downloaded file. The InstallShield Wizard with the Welcome message is displayed.

Page 6
HFR, Inc.

4. Click “Next”
5. The License Agreement screen is displayed. Select "I accept the License Agreement" to proceed
further installation process.

6. Click “Next”
7. Select “English” language of HFR CE-EMS.

Page 7
HFR, Inc.

8. Click “Next”
9. In the next screen, select “Advanced” to install all the components including Back-End,
Standalone Front-End and Distributed Poller.

10. Click “Next”


11. There are 3 radio options available here:
• Back-End and Front-end Server
• Remote Front-End Server
• Distributed Poller
Select “Back-End and Front-End Server” and click “Next” button to install Back-End Server.
Page 8
HFR, Inc.

12. Screen to specify the destination directory to install “Back-End Server” is displayed.

13. Click “Next” to install “Back-End Server” to the specified destination in, or click “Browse” to
install to a different location.
14. The installation details like “Installation Directory” and “Product size” are displayed in next
screen.
15. Click “Next” to start installation process or “Back” if there are any changes in the destination
location.

Page 9
HFR, Inc.

16. After successful installation, screen with Success message is displayed.

Page 10
HFR, Inc.

17. Click “Finish” to exit the wizard


18. After installation, when you start CE-EMS, you need to provide the license information for
Registered User. For more information, refer to Licensing the Product

Step to install CE-EMS Patch

1. After installing CE-EMS, copy the patch file (.nar file) at <CE-EMS BE HOME>.
2. Go to <CE-EMS BE HOME>/bin/developertools.
3. Execute the DeploymentWizard by the following command:
Ø sh DeploymentWizard.sh

Page 11
HFR, Inc.

4. Click “NarInstall/Uninstall” tab.

5. At first, you need to remove the old patch (HFR_Project1.0).


Select the old patch at Uninstall box and Click “Uninstall”.

Page 12
HFR, Inc.

6. Click “Uninstall”. And progress with removing old patch.


After removing, click “Close”

7. Click “Install” at Install box.

Page 13
HFR, Inc.

8. Click “Browse” and select new patch file in <CE-EMS BE HOME>.


And Click “OK”

9. Click “Next”.

Page 14
HFR, Inc.

10. Click “Install”. After finishing installation, click “Close”.

11. Click “Exit”.

Page 15
HFR, Inc.

19. Go to <CE-EMS BE Home>/bin


20. Change JDK_HOME directory of compileJSP.sh file.

#!/bin/sh
#$Id: compileJSP.sh,v 1.5 2007/06/20 12:13:17 venkatramanan Exp $
# This script is used to generate classes for jsp files.

if [ $# -ne 0 ]
then
echo "Error: Run the script without any option"
echo "Usage ComplileJSP.sh"
exit 1
fi

cd ..
. ./setEnv.sh

JDK_HOME=/usr/java/jdk1.7.0_71

export JDK_HOME

JAVA_HOME=$JDK_HOME
export JAVA_HOME

if [ ! -f $JDK_HOME/bin/javac -o -z "$JDK_HOME" ]
then
echo "error: javac not found. Please configure JDK_HOME environment variable in $0 file."
exit 1
fi

21. Execute the compileJSP by the following command:


Ø sh compileJSP.sh
22. After installing the BE, following configuration should be done to connect the database

Page 16
HFR, Inc.

3.1.1.2. Command / Console Mode

The Command or Console mode is an Interactive and Non-GUI based installation mode. The user
can install CE-EMS through the command prompt.

Steps to install HFR CE-EMS Back-End in Command or Console mode

1. Download/Get the installation file (.bin file).


2. Check the executable permission of the .bin file. If the file is not executable, execute the
following command:
Ø chmod a+x <File Name>.bin [<File Name> is the corresponding .bin file]
3. Execute the downloaded file as follows:
Ø <File Name>.bin -console
4. The above command will initiate an interactive installation procedure. The user needs to select
the options from the messages displayed on the command prompt
5. After installing the BE, following configuration should be done to connect the database.

3.1.2. Procedure for Connecting BE Server to the JDBC Driver

1. Edit the DB_CLASSPATH variable (which is by default set to postgresql driver) in setEnv.sh file
under <CE-EMS Home> directory to set the JDBC Driver for Oracle. Set the JDBC Driver path to
ojdbc7.jar.
Below box is “setEnv.sh” file. And you need to add red items.

...
SNMP_CLASSPATH=$NMS_CLASSES/AdventNetSnmp.jar:$NMS_CLASSES/SNMPDebugger.jar

EXAMPLE_CLASSES=$NMS_HOME/examples/classes

SAS_CLASSPATH=$NMS_CLASSES/AdventNetSAS.jar

#XML_CLASSPATH=$NMS_CLASSES/jaxp.jar:$NMS_CLASSES/xalan.jar

PGSQL_HOME=$NMS_HOME/pgsql
DB_CLASSPATH=$PGSQL_HOME/driver/postgresql_jdbc4.jar:$NMS_CLASSES/p6spy.jar:$NMS_HOME/c
onf:$NMS_CLASSES/log4j.jar:$NMS_CLASSES/ojdbc7.jar

2. If the CE-EMS Server is already started, then do a proper and normal shutdown of Oracle. Do
not terminate the process abruptly.
3. Un-comment the following lines and comment out the PostgreSQL database configuration lines
in the hibernate.cfg.xml file.

<!--For Using Oracle DB , Uncomment the below tags -->


<property name="connection.driver_class">oracle.jdbc.driver.OracleDriver</property>
<property
name="connection.url">jdbc:oracle:thin:@DB_IP_Address:DB_Listener_Port:DB_SID</property
>
<property name="connection.username">DB_ID</property>
<property name="connection.password">DB_Password</property>
<property name="dialect">org.hibernate.dialect.Oracle9Dialect</property>
<property name="databasename">ORACLE</property>
<!-- End of ORACLE ,Uncomment till here-->
.....
<property name="hibernate.default_schema">DB_ID</property>

Page 17
HFR, Inc.

4. Set the parameter hibernate.default_schema value as "userName" in <CE-EMS BE


Home>/classes/hbnlib/hibernate.cfg.xml.
5. Check if the Oracle server is listening to the port 1521.
6. For Oracle, add the entry “open_cursors=1000”. There is two ways for adding the entry
“open_cursors”
A. First, you can edit the line as shown below.
i. Go to “<ORACLE_HOME>/Database/init<database name>.ora” file.
ii. Find below line:
OPEN_CURSORS 300
iii. If there is no that line, you have to add that.
If there is that line, you can change value from default to 300.

B. Second, you can configure the value by CLI command.


i. Run to “<ORACLE_HOME>/bin/sqlplus” file.
Enter the ID & Password for starting sqlplus
ii. Or use following command at <ORACLE_HOME>:
Ø sqlplus “/as sysdba”
iii. Check the value:
SQL> show parameters open_cursors;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
open_cursors integer 300
iv. Change the value form default to 300.
SQL> ALTER SYSTEM SET OPEN_CURSORS = 1000 SCOPE = BOTH;
System altered
v. Check the value again.
SQL> show parameters open_cursors;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
open_cursors integer 1000

7. Go to start the CE-EMS server

3.1.3. Start CE-EMS BE Server

1. After installing patch file and configuration, go to <CE-EMS BE HOME>/bin.


2. Copy the license file at <CE-EMS BE HOME>
3. Execute startnms.sh script file
Ø sh startnms.sh
4. CE-EMS Framework wizard is shown to specify License details
Or you can see License details at terminal of running script file.
License details of terminal mode proceed same way as GUI mode.

Page 18
HFR, Inc.

5. Select “I accept the License Agreement” checkbox


6. Choose Evaluation version to start the trial version of CE-EMS software pack, else choose
Registered User to specify License file.

7. Steps for Registered User


A. Licensee Details screen is shown to enter the license file or browse from the destined
location.

Page 19
HFR, Inc.

B. Click “Next”
C. Next screen lists the usernames for whom the license file is authorized.
D. Select the username with which you want to register this installation copy.

E. Click “Finish”
8. Steps for Evaluation User
A. Click “Finish”

Page 20
HFR, Inc.

9. Now, the CE-EMS server will be started automatically on the specified port.

CE-EMS Front End Server Installation and Starting

3.2.1. CE-EMS FE Server Installation

3.2.1.1. GUI Mode through Install Shield

The GUI mode is an interactive GUI based installation mode.

Step to install CE-EMS Front-End Server

1. Download/Get the installation file (.bin file).


2. Check the executable permission of the .bin file. If the file is not executable, execute the
following command:
Ø chmod a+x <File Name>.bin [<File Name> is the corresponding .bin file]
3. Execute the downloaded file. The InstallShield Wizard with the Welcome message is displayed.

Page 21
HFR, Inc.

4. Click “Next”
5. The License Agreement screen is displayed. Select "I accept the License Agreement" to proceed
further installation process.

6. Click “Next”
7. Select “English” language of HFR CE-EMS.

Page 22
HFR, Inc.

8. Click “Next”
9. In the next screen, select “Advanced” to install all the components including Back-End,
Standalone Front-End and Distributed Poller.

10. Click “Next”


11. There are 3 radio options available here:
• Back-End and Front-end Server
• Remote Front-End Server
• Distributed Poller
Select “Remote Front-End Server” and click “Next” button to install Front-End Server.
Page 23
HFR, Inc.

12. Screen to specify the destination directory to install “Front-End Server” is displayed.

13. Click “Next” to install “Front-End Server” to the specified destination in, or click “Browse” to
install to a different location.
14. The installation details like “Installation Directory” and “Product size” are displayed in next
screen.
15. Click “Next” to start installation process or “Back” if there are any changes in the destination
location.

Page 24
HFR, Inc.

16. After successful installation, screen with Success message is displayed.

Page 25
HFR, Inc.

17. Click “Finish” to exit the wizard


18. After installation, when you start CE-EMS, you need to provide the license information for
Registered User. For more information, refer to Licensing the Product

Step to install CE-EMS Patch

12. After installing CE-EMS, copy the patch file (.nar file) at <CE-EMS FE HOME>.
13. Go to <CE-EMS FE HOME>/bin/developertools.
14. Execute the DeploymentWizard by the following command:
Ø sh DeploymentWizard.sh

Page 26
HFR, Inc.

15. Click “NarInstall/Uninstall” tab.

16. At first, you need to remove the old patch (HFR_Project1.0).


Select the old patch at Uninstall box and Click “Uninstall”.

Page 27
HFR, Inc.

17. Click “Uninstall”. And progress with removing old patch.


After removing, click “Close”

18. Click “Install” at Install box.

Page 28
HFR, Inc.

19. Click “Browse” and select new patch file in <CE-EMS FE HOME>.
And Click “OK”

20. Click “Next”.

Page 29
HFR, Inc.

21. Click “Install”. After finishing installation, click “Close”.

22. Click “Exit”.

Page 30
HFR, Inc.

19. Go to <CE-EMS FE Home>/bin


20. Change JDK_HOME directory of compileJSP.sh file.

#!/bin/sh
#$Id: compileJSP.sh,v 1.5 2007/06/20 12:13:17 venkatramanan Exp $
# This script is used to generate classes for jsp files.

if [ $# -ne 0 ]
then
echo "Error: Run the script without any option"
echo "Usage ComplileJSP.sh"
exit 1
fi

cd ..
. ./setEnv.sh

JDK_HOME=/usr/java/jdk1.7.0_71

export JDK_HOME

JAVA_HOME=$JDK_HOME
export JAVA_HOME

if [ ! -f $JDK_HOME/bin/javac -o -z "$JDK_HOME" ]
then
echo "error: javac not found. Please configure JDK_HOME environment variable in $0 file."
exit 1
fi

21. Execute the compileJSP by the following command:


Ø sh compileJSP.sh
22. After installing the FE, following configuration should be done to connect the database

Page 31
HFR, Inc.

3.2.1.2. Command / Console Mode

The Command or Console mode is an Interactive and Non-GUI based installation mode. The user
can install CE-EMS through the command prompt.

Steps to install HFR CE-EMS Front-END in Command or Console mode

1. Download/Get the installation file (.bin file).


2. Check the executable permission of the .bin file. If the file is not executable, execute the
following command:
Ø chmod a+x <File Name>.bin [<File Name> is the corresponding .bin file]
3. Execute the downloaded file as follows:
Ø <File Name>.bin -console
4. The above command will initiate an interactive installation procedure. The user needs to select
the options from the messages displayed on the command prompt
5. After installing the FE, following configuration should be done to connect the database.

3.2.2. Procedure to Configure the FE Server

The following procedure explains two setups. The first setup where the back-end server and front-end
server are on different machines and the second the back-end server and front-end server are on the
same machine.

3.2.2.1. FE and BE on Different Machines

Assume the Back-End is running on a machine with DNS name "MachineBE". Install the Standalone
Front-End on the machine with DNS name "MachineFE".

Connecting the Installed FE server to the BE server

Edit BE_HOST parameter present in <CE-EMS FE HOME>/bin/startnmsFE.sh of


machine with DNS name "MachineBE" or “IP address” of BE Server.
• BE_HOST: Host Name of BE Server or IP address of BE Server
[For Example: “MachineBE” or “10.45.3.55”]
• BE_PORT: Port Number between BE server and FE server for communication
[For Example: 2000 (2000 is default)]

$JAVA_HOME/bin/java -Xmx100m -cp $CLASS_PATH -Dcatalina.home=$TOMCAT_HOME -


Dresource_check="$WEBSERVER_PORT,$WEBCONTAINER_PORT,$TOMCAT_SHUTDOWNPORT" -
Dwebserver.port=$WEBSERVER_PORT -Dssl.port=$SSL_PORT -Dwebserver.rootdir=$WEBSERVER_HOME -
XX:+HeapDumpOnOutOfMemoryError -XX:+UseConcMarkSweepGC -Dcom.sun.management.jmxremote.port=15000 -
Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -
Dcom.sun.management.snmp.interface=`hostname` -Dcom.sun.management.snmp.acl=false -
Dcom.sun.management.snmp.port=15500 com.adventnet.nms.startnms.NmsMainFE BE_PORT 2000 BE_HOST
10.45.3.55 ROOT_DIR $NMS_HOME
if [ $? -eq 126 -o -f Patch/smarttmp.txt ]; then
$JAVA_HOME/bin/java -cp $UPDATE_MANAGER_CLASSPATH com.adventnet.tools.update.installer.UpdateManager -u conf
-h $NMS_HOME -c

By default, only the files required for Standalone Front-End Server installation, are
present in the “<CE-EMS FE Home>/conf “directory in "MachineFE". All the other
configuration files required for connecting to the database and other operations are
downloaded from "MachineBE" on the Standalone Front-End startup
Page 32
HFR, Inc.

3.2.2.2. FE and BE on the Same Machine

Assume the Back-End is present in the same machine "MachineBE". The Front-End present in the
combo download does not require any changes for the BE_HOST and BE_PORT parameters. By
default, these parameters are set to "localhost" and "9090" respectively. In case the Front-End
server needs to be invoked as a separate process on the same machine as the Back-End server,
then some port values have to be changed in order to avoid clash of usage of ports.

If you want to run the front-end server as a separate process in the same machine where the back-
end server is running, the following ports have to be changed in <CE-EMS FE Home>/setEnv.sh.
• WEBSERVER_PORT : Change the port from 9090 to 9095(say)
• WEBCONTAINER_PORT : Change the port from 8009 to 8010(say)
• TOMCAT_SHUTDOWNPORT : Change the port from 8005 to 8006(say)

3.2.3. Procedure for Connecting FE Server to the JDBC Driver

If you want to use any database other than PostgreSQL, the default database bundled with CE-EMS,
change the DB_CLASSPATH parameter in <CE-EMS FE HOME>/setEnv.sh present in "MachineFE" in
case of the standalone FE Server or the <CE-EMS FE Home>/setEnv.sh present in "MachineBE" in case
of the FE bundled with the BE.

1. Edit the DB_CLASSPATH variable (which is by default set to postgresql driver) in setEnv.sh file
under <CE-EMS FE Home> directory to set the JDBC Driver for Oracle. Set the JDBC Driver
path to ojdbc7.jar.
Below box is “setEnv.sh” file. And you need to add red items.

...
SNMP_CLASSPATH=$NMS_CLASSES/AdventNetSnmp.jar:$NMS_CLASSES/SNMPDebugger.jar

EXAMPLE_CLASSES=$NMS_HOME/examples/classes

SAS_CLASSPATH=$NMS_CLASSES/AdventNetSAS.jar

#XML_CLASSPATH=$NMS_CLASSES/jaxp.jar:$NMS_CLASSES/xalan.jar

PGSQL_HOME=$NMS_HOME/pgsql
DB_CLASSPATH=$PGSQL_HOME/driver/postgresql_jdbc4.jar:$NMS_CLASSES/p6spy.jar:$NMS_HOME/c
onf:$NMS_CLASSES/log4j.jar:$NMS_CLASSES/ojdbc7.jar

2. Un-comment the following lines and comment out the PostgreSQL database configuration lines in
the hibernate.cfg.xml file.

<!--For Using Oracle DB , Uncomment the below tags -->


<property name="connection.driver_class">oracle.jdbc.driver.OracleDriver</property>
<property
name="connection.url">jdbc:oracle:thin:@DB_IP_Address:DB_Listener_Port:DB_SID</property
>
<property name="connection.username">DB_ID</property>
<property name="connection.password">DB_Password</property>
<property name="dialect">org.hibernate.dialect.Oracle9Dialect</property>
<property name="databasename">ORACLE</property>
.....
<property name="hibernate.default_schema">DB_ID</property>

Page 33
HFR, Inc.

3. Set the parameter hibernate.default_schema value as "userName" in <CE-EMS FE


Home>/classes/hbnlib/hibernate.cfg.xml.
4. Check if the Oracle server is listening to the port 1521.
5. Go to start the CE-EMS server

3.2.4. Start CE-EMS FE Server

1. After installing patch file and configuration, go to <CE-EMS FE HOME>/bin


2. Execute startnmsFE.sh script file
Ø sh startnmsFE.sh

CE-EMS Poller Server Installation and Starting

3.3.1. CE-EMS Poller Server Installation

3.3.1.1. GUI Mode through Install Shield

The GUI mode is an interactive GUI based installation mode.

Step to install CE-EMS Poller Server

1. Download/Get the installation file (.bin file).


2. Check the executable permission of the .bin file. If the file is not executable, execute the
following command:
Ø chmod a+x <File Name>.bin [<File Name> is the corresponding .bin file]
3. Execute the downloaded file. The InstallShield Wizard with the Welcome message is displayed.

Page 34
HFR, Inc.

4. Click “Next”
5. The License Agreement screen is displayed. Select "I accept the License Agreement" to proceed
further installation process.

6. Click “Next”
7. Select “English” language of HFR CE-EMS.

Page 35
HFR, Inc.

8. Click “Next”
9. In the next screen, select “Advanced” to install all the components including Back-End,
Standalone Front-End and Distributed Poller.

10. Click “Next”


11. There are 3 radio options available here:
• Back-End and Front-end Server
• Remote Front-End Server
• Distributed Poller
Select “Distributed Poller” and click “Next” button to install Poller Server.
Page 36
HFR, Inc.

12. Screen to specify the destination directory to install “Poller Server” is displayed.

13. Click “Next” to install “Poller Server” to the specified destination in, or click “Browse” to install
to a different location.
14. The installation details like “Installation Directory” and “Product size” are displayed in next
screen.
15. Click “Next” to start installation process or “Back” if there are any changes in the destination
location.

Page 37
HFR, Inc.

16. After successful installation, screen with Success message is displayed.

Page 38
HFR, Inc.

17. Click “Finish” to exit the wizard


18. After installation, when you start CE-EMS, you need to provide the license information for
Registered User. For more information, refer to Licensing the Product

3.3.1.2. Command / Console Mode

The Command or Console mode is an Interactive and Non-GUI based installation mode. The user
can install CE-EMS through the command prompt.

Steps to install HFR CE-EMS Poller in Command or Console mode

1. Download/Get the installation file (.bin file).


2. Check the executable permission of the .bin file. If the file is not executable, execute the
following command:
Ø chmod a+x <File Name>.bin [<File Name> is the corresponding .bin file]
3. Execute the downloaded file as follows:
Ø <File Name>.bin -console
4. The above command will initiate an interactive installation procedure. The user needs to select
the options from the messages displayed on the command prompt
5. After installing the Poller, following configuration should be done to connect the database.

3.3.2. Procedure for Connecting Poller Server to the JDBC Driver

If you want to use any database other than PostgreSQL, the default database bundled with CE-
EMS, change the DB_CLASSPATH parameter in <CE-EMS Poller HOME>/setEnv.sh

1. Edit the DB_CLASSPATH variable (which is by default set to postgresql driver) in setEnv.sh file
under <CE-EMS Poller Home> directory to set the JDBC Driver for Oracle. Set the JDBC Driver
path to ojdbc7.jar.

Page 39
HFR, Inc.

Below box is “setEnv.sh” file. And you need to add red items.

...
SNMP_CLASSPATH=$NMS_CLASSES/AdventNetSnmp.jar:$NMS_CLASSES/SNMPDebugger.jar

EXAMPLE_CLASSES=$NMS_HOME/examples/classes

SAS_CLASSPATH=$NMS_CLASSES/AdventNetSAS.jar

#XML_CLASSPATH=$NMS_CLASSES/jaxp.jar:$NMS_CLASSES/xalan.jar

PGSQL_HOME=$NMS_HOME/pgsql
DB_CLASSPATH=$PGSQL_HOME/driver/postgresql_jdbc4.jar:$NMS_CLASSES/p6spy.jar:$NMS_HOME/c
onf:$NMS_CLASSES/log4j.jar:$NMS_CLASSES/ojdbc7.jar

2. Copy the DatabaseSchema.conf from <CE-EMS Poller Home>/conf/Oracle directory to <CE-
EMS Poller Home>/conf/ directory
3. Un-comment the following lines and comment out the PostgreSQL database configuration lines in
the hibernate.cfg.xml file.

<!--For Using Oracle DB , Uncomment the below tags -->


<property name="connection.driver_class">oracle.jdbc.driver.OracleDriver</property>
<property
name="connection.url">jdbc:oracle:thin:@DB_IP_Address:DB_Listener_Port:DB_SID</property
>
<property name="connection.username">DB_ID</property>
<property name="connection.password">DB_Password</property>
<property name="dialect">org.hibernate.dialect.Oracle9Dialect</property>
<property name="databasename">ORACLE</property>
.....
<property name="hibernate.default_schema">DB_ID</property>

4. Set the parameter hibernate.default_schema value as "userName" in <CE-EMS Poller


Home>/classes/hbnlib/hibernate.cfg.xml.
5. Check if the Oracle server is listening to the port 1521.
6. Go to start the CE-EMS server

3.3.3. Start CE-EMS Poller Server

1. After installing patch file and configuration, go to <CE-EMS Poller HOME>/bin


2. Execute startpoller.sh script file
Ø sh startpoller.sh <Poller_Name> <BE_Server_IP>
[Poller_Name: This name is unique name for Poller Server]

Page 40
HFR, Inc.

4. Discovery

• Discovery Parmeter

• Discovery Criteria

• Re-Discovery Scheduler

• Network Configuration

• Node Configuration

• Refresh Node

Discovery Parameter

Discovery Configuration is about configuring the process of discovery based on entries in the seed.file
located in the <CE-EMS Home>/conf directory. Following configurations can be performed with ease
from the Runtime Administration page of Web Client.
• auto discovery of nodes and networks

• discovery of local networks

• enabling log messages

• rediscovery of the already discovered networks or nodes

• setting time interval for discovery

• setting SNMP properties

• setting the ICMP protocol properties

To perform Discovery Parameter Configuration


1. In the Web Client, click the Admin module tab.

2. Click Complete View > Discovery > Discovery Parameter node on the left-side tree of the
displayed page.

3. Alternatively, click Discovery Parameter link in the Discovery section on the right-side of the
client screen.

4. The Discovery Configuration Settings page is displayed. Each of the fields in this page is tabulated
below:

Field Description
Options, such as auto discovery, discovering local networks, enabling log
message generation, and rediscovering elements can be configured
Common
through the displayed page. For information on each of these options,
Parameters
refer to the General Configuration section in the Using Discovery
Configurator topic.
SNMP This section provides options to configure the discovery of SNMP devices.
Properties For information on each of these options, refer to the Protocol

Page 41
HFR, Inc.

Configuration section in the Using Discovery Configurator topic.


The ICMP ping is performed by CE-EMS Discovery engine to detect active
devices of a network. You can configure the ping timeout period and the
number of times a device is to be pinged at runtime.

ICMP Discovery: Select the check box to enable ICMP ping and un-
select to disable.

Ping Timeout: Specify the duration (in seconds) until when a device is in
the pinged state.
System Ping
Ping Retries: Specify the number of times a device is to be pinged.

Native Ping Properties

Native Ping Timeout: Specify the duration (in seconds) for Native ping
until when a device is in the pinged state.

Native Ping Retries: Specify the number of times a device is to be


pinged for Native ping.

5. Click Submit button, if you want the configured values to take effect. Click Cancel button, to
cancel the configuration operation.

Discovery Criteria

You can configure the criteria based on which a device or network is to be discovered, at runtime.

To perform Discovery Criteria Configuration


1. In the Web Client, click the Admin module tab.

2. Click Complete View > Discovery > Discovery Criteria node on the left-side tree of the
displayed page.

3. Alternatively, click Discovery Criteria link in the Discovery section on the right-side of the
client screen.

4. The Discovery Criteria Configuration page is displayed.

5. Select the Allow Criteria if you want the discovery to happen based on a criteria. Un-checking
the box will prevent the device or network from being discovered based on the set criteria.

6. Choose the criteria from the drop-down box and specify the corresponding value in the text field.

7. Click Add to add the value specified for the chosen criteria. The added value is listed in a tabular
format.

8. Click Modify if you want to modify the existing value of a chosen criteria. Click Delete to delete
the criteria.

For more information, refer to Criteria Based Discovery section in Using Discovery Configurator topic.

Page 42
HFR, Inc.

Re-Discovery Scheduler

You can configure the criteria based on which a device or network is to be discovered, at runtime.

To perform Discovery Criteria Configuration


1. In the Web Client, click the Admin module tab.

2. Click Complete View > Discovery > Re-Discovery Scheduler node on the left-side tree of the
displayed page.

3. Alternatively, click Re-Discovery Scheduler link in the Discovery section on the right-side of the
client screen.

4. The Re-Discovery Scheduler page is displayed. Each of the fields in this page is tabulated below:

Field Description
Rediscovery To schedule the discovery of devices, click this option. The
Scheduler Rediscovery Scheduler is displayed.

5. Click Submit button, if you want the configured values to take effect. Click Cancel button, to
cancel the configuration operation.

Network Configuration

Networks and their elements are discovered automatically by CE-EMS and the discovery process is
carried out in a predetermined way. If you need to discover a network or node manually instead of
waiting for CE-EMS to discover it automatically, use the Add New Network and Add New Node
options.

To add a new network


1. Click Admin module tab. The Admin page is displayed.

2. Click Complete View > Discovery > Network Configurator node on the left-side tree of
the displayed page.

3. Alternatively, click Network Configurator link in the Discovery section on the right-side of
the client screen.

4. The Network Configurator page is displayed.

5. If you want to add a complete network, select Add Entire Network radio button. Enter a
valid IP Address in Network Address field and select the netmask (by default 255.255.255.0)
from Netmask combo box.

6. If you want to add a set nodes within a range of IP addresses, select Add Range of Nodes
radio button. Enter a valid staring IP Address of the range in Start IP Address field, enter a
valid ending IP Address of the range in End IP Address field and select the netmask (by
default 255.255.255.0) from Netmask combo box.

Page 43
HFR, Inc.

7. The Discovery Configuration options provided are optional. The significance of each of the
fields is given below.

Field Significance
Not to Discover
If this option is checked, the added network will not be discovered by
the above
CE-EMS.
Network
If this option is selected, the discovery of the network added starts
instantly.
Start Discovery
If the option is not selected, then the network is just added to the
database but discovery of that network is not performed.
If this option is selected, the network is added to the database and
discovery happens. The network and its elements are in managed state
Manage the as they are discovered.
Network If this option is not selected, the network is added in unmanaged state
to the database and discovery of that network will not be started.
Hence none of the network elements in the network will be discovered.
Initially some configurations are made related to discovery in the
Override the
seed.file using Discovery Configurator tool. A configuration could have
discovery
been made to restrict the discovery of certain IPs. But if you select this
configuration
option, those configurations are overridden and discovery is performed.
If you want this network to be discovered the next time CE-EMS Server
is started (after reinitializing), select this option. On doing so, the IP
Update the
that you mention is configured in the seed.file (discovery configuration
discovery
file present in <Web NMS Home/conf directory>) permanently. This
configuration
field is enabled for both Add Entire Network and Add Range of
Nodes options.
Is the nodes of If this option is selected, the discovery of the set of nodes, which are
the Network DHCP enabled, happens. This field is enabled for Add Range of Nodes
DHCP option and disabled for Add Entire Network option.

8. Once the Submit button is clicked, CE-EMS takes a while to discover the network. If you do not
want to wait for the discovery to be completed and want to proceed with other operations,
select Process in the background check box. By doing so, you can quit the current view and
work on other views while the discovery process is done in the background.

9. Click Submit button, if you want to discover the added network. Click Reset button, to reset
the adding network operation.

If the network IP that you have entered has already been added to the database and discovered by
CE-EMS, relevant message is displayed in the Network Configurator page.

Node Configuration

To add a new node

Page 44
HFR, Inc.

1. Click Admin module tab. The Admin page is displayed.

2. Click Complete View > Discovery > Node Configurator node on the left-side tree of the
displayed page.

3. Alternatively, click Node Configurator link in the Discovery section on the right-side of the
client screen.

4. The Node Configurator page is displayed.

5. Enter a valid IP Address in IP Address field and select the netmask (by default, 255.255.255.0)
from Netmask combo box.

6. The significance of each of the fields under SNMP Configuration and Discovery
Configuration is given below.

Field Significance
SNMP Configuration
Port number where the SNMP agent is running. By default, the
SNMP Port
port is 161.
By default, the value is public. When no value is set, then the
Community community value as configured in the seed.file is fetched and
substituted.
Enable V3 (User If you enable the discovery of SNMPv3 devices, then you need to
Name, Context specify the user name and context name in the corresponding
Name) field.
Discovery Configuration
Not to discover the If this option is checked, the added node will not be discovered by
above node CE-EMS.
Discover even if the
If this option is checked, even if the node is not alive when you
node is not
add it, CE-EMS adds a managed element for that node.
reachable
If this option is selected, apart from adding the node that you
have configured, all other devices in their parent network are also
Discover all the
discovered (if they were not discovered already).
devices in the
For example, if you add a device 192.168.1.5 with this option
parent network
checked, then all the devices in the 192.168.1.0 network are also
discovered.
Initially some configurations are made related to discovery in the
seed.file using Discovery Configurator tool. A configuration could
Override discovery
have been made to restrict the discovery of certain nodes. But if
configuration
you select this option, those configurations are overridden and
discovery is performed for those nodes also.
If you want this node to be discovered the next time the CE-EMS
Server is started (after reinitializing), select this option. On doing
Update discovery
so, the node that you mention is configured in the seed.file
configuration
(discovery configuration file present in <Web NMS Home>/conf
directory) permanently.

7. Once the Submit button is clicked, CE-EMS takes a while to discover the node. If you do not
want to wait for the discovery to be completed and want to proceed with other operations, select
Process in the background check box. By doing so, you can quit the current view and work on
other views while the discovery process is done in the background.

Page 45
HFR, Inc.

8. Click Submit button, if you want to discover the added node. Click Reset button, to reset the
adding node operation.

If the node IP that you have entered has already been added to the database and discovered by CE-
EMS, relevant message is displayed in the Node Configurator page.

Refresh Node

To rediscover a node in the network, use the Refresh Node option. A node or device could have been
down for a while or it would not have been discovered when you performed a manual discovery of that
node. In these cases, refresh the node manually to obtain its latest information.

To refresh a node
1. Click Admin module tab. The Admin page is displayed.

2. Click Complete View > Discovery > Refresh Node node on the left-side tree of the
displayed page.

3. Alternatively, click Refresh Node link in the Discovery section on the right-side of the client
screen.

4. The Refresh Node page is displayed.

5. Enter the name or IP address of the node to be refreshed in the Name of the Node field.

6. Select the netmask (by default, 255.255.255.0) from Netmask combo box.

7. Enter the port (by default, 161) where SNMP agent is running in SNMP Port field.

8. If you select the SNMP version as V3 in the combo box to enable the re-discovery of SNMPv3
devices, you need to specify the user name and context name in the corresponding field.

9. Click Refresh, if you want to re-discover the specified node. Click Reset button, to reset the
re-discovering the specified node operation.

Page 46
HFR, Inc.

5. Security Administration

• User Configuration

• Add User

• Add Multiple

• Change Status

• Delete

• Modifying a User's Profile

• Viewing User Details

• Group Configuration

• Add Group

• Delete

• Modify Group

User Configuration

5.1.1. Add User

To add a new user


1. Click Admin module tab. The Admin page is displayed.
2. Click Complete View > Security Administration > User Configuration node on the left-
side tree of the displayed page.
3. Alternatively, click the Security Administration > User Configuration link on the right-side
of the client screen.
4. Click the Add User link of “Action”. The Add User page is displayed.
5. Enter the new name for the user in User name field.
6. Enter a password in the Password field (maximum of 8 characters). At least, 6 password
characters with the combination of alphanumeric and special characters are required.
7. Re-enter the same password in Re-type Password field.
8. The Associated Groups field lists all the existing groups. Select the group(s) to which the user
should be a member. Press Associated Groups filed to select multiple groups.
If you need to add the user to a new group, select the Add this user to a new group check
box and enter the name of the new group in the text field.
9. Select the Password expires in check box and enter the number of days the password stays
valid. If this check box is not selected, then the password never expires.
10. Similarly, select the Account expires in check box and enter the number of days the user
account stays valid. If this check box is not selected, then the user account never expires.
11. Click Save. Click Reset button, to reset the adding user operation. Click Back button, to
restore the previous values in the Add User form.

On performing this, a confirmation message on the success or failure of the configuration is


Page 47
HFR, Inc.

displayed.

5.1.2. Add Multiple

To add multiple users


1. Click Admin module tab. The Admin page is displayed.
2. Click Complete View > Security Administration > User Configuration node on the left-
side tree of the displayed page.
3. Alternatively, click the Security Administration > User Configuration link on the right-side
of the client screen.
4. Click the Add Multiple link of “Actions”. The Add Multiple User page is displayed. A maximum
of 12 users can be added in this page.
5. Enter the new names for the required number of users in User name field. If created new user
by this menu, password of user is same as User name. So user need to change password after
accessing HFR CE-EMS.
6. The Selected group field lists all the existing groups. Select the group(s) to which the user
should be a member.
If you have selected a group for the first user and if you want to apply the selected group to all
the users, select the Apply selected group to all users check box.
7. Click Save. Click Reset button, to reset the adding user operation. Click Back button, to
restore the previous values in the Add User form.

On performing this, a confirmation message on the success or failure of the configuration is


displayed.

5.1.3. Change Status

To change the status of a user


1. Click Admin module tab. The Admin page is displayed.
2. Click Complete View > Security Administration > User Configuration node on the left-
side tree of the displayed page.
3. Alternatively, click the User Configuration link in the Security Administration section on the
right-side of the client screen.
4. The User Configuration page is displayed.
5. Select a user, by checking the check box of the user row.
6. Click Change Status combo box. Select Enable or Disable link option as per your
requirement.

On performing this, a confirmation message on the success or failure of the configuration is


displayed.

5.1.4. Delete

To remove a user
1. Click Admin module tab. The Admin page is displayed.
2. Click Complete View > Security Administration > User Configuration node on the left-
side tree of the displayed page.

Page 48
HFR, Inc.

3. Alternatively, click the User Configuration link in the Security Administration section on the
right-side of the client screen.
4. The User Configuration page is displayed.
5. Select a user, by checking the check box of the user row.
6. Click Delete button.

On performing this, a confirmation message on the success or failure of the configuration is


displayed.

5.1.5. Modifying a User's Profile

To modify a user's profile


1. Click Admin module tab. The Admin page is displayed.
2. Click Complete View > Security Administration > User Configuration node on the left-
side tree of the displayed page.
3. Alternatively, click the User Configuration link in the Security Administration section on the
right-side of the client screen.
4. The User Configuration page is displayed.
5. Select a user, by clicking the User name of the user row.
6. The Modify profile - <User> form is displayed.

7. Select Change Password button of User Information if you need to change that user's
password.
8. Enter the new password and re-enter the same password in New password and Re-type
password fields respectively.
9. The Modify password expiration field displays the number of days the password stays valid.
If this was not configured while creating the user, then 0 is displayed, which means the
password never expires. Modify the expiration period, if required, by selecting the check box
and entering a new value in the text field.
10. The Modify account expiration field displays the number of days the user account stays valid.
If this was not configured while creating the user, then 0 is displayed, which means the user
account never expires. Modify the expiration period, if required, by selecting the check box and
entering a new value in the text field.
11. On editing the required fields, click Submit. Click Cancel button, to cancel the user profile
modification.
12. Under Associated Groups section, the Group name section lists the group(s) in which the

user has already been enrolled. To add or delete new group(s), click Configure Group
button. Modify profile window for configuring the users pops-up. The Available groups field

lists the existing groups that the user has not been enrolled. Use the Remove and Add

options to remove the user from a group or enroll the user to a group. Press Ctrl key to
select multiple groups. Click Submit. Click Reset button, to reset the add/delete group
operation. Click Close button, to close the Modify profile pop-up window.
13. Under Permitted Operations section, the Name column lists the operations for which the
user is permitted and the Type column lists the type of permission for the corresponding
operation. To add or delete new operations and modify the permissions, click Configure
Operations button. Operations Tree window for configuring the users pops-up. The
Operation Tree Root lists all the existing operations that the user can be permitted. This
includes the operations inherited from the Group to which the user belongs. Use the Check box
options to include, exclude, and not authorize the operations for the user. Click Save. Click
Cancel button, to cancel the configuration.

Page 49
HFR, Inc.

Hints
• - Operation is authorized for the Group/User

• - Operation is not authorized for the Group/User

• - Not authorized for the Group/User but mutable

• - Authorized and immutable as inherited from group

• - Not authorized and immutable as inherited from group

On performing this, a confirmation message on the success or failure of the configuration is


displayed.

5.1.6. Exporting User List

To export the user list


1. Click Admin module tab. The Admin page is displayed.
2. Click Complete View > Security Administration > User Configuration node on the left-
side tree of the displayed page.
3. Alternatively, click the User Configuration link in the Security Administration section on the
right-side of the client screen.
4. The User Configuration page is displayed.
5. Click Export As CSV button.

Group Configuration

5.2.1. Add Group

To add a new group


1. Click Admin module tab. The Admin page is displayed.
2. Click Complete View > Security Administration > Group Configuration node on the left-
side tree of the displayed page.
3. Alternatively, click the Security Administration > Group Configuration link on the right-side
of the client screen.
4. Click the Add Group link of “Actcion”. The Add Group window pops-up.
5. Enter the new name for the group in Group Name field.
6. Under Operations Tree section, add or delete new operations and modify the permissions. The
Operation Tree Root lists all the existing operations that the group can be permitted. These
operations will be inherited to all the users belonging to this Group. Use the Check box options
to include, exclude, and not authorize the operations for the user.

Hints
• - Operation is authorized for the Group/User

• - Operation is not authorized for the Group/User

• - Not authorized for the Group/User but mutable

Page 50
HFR, Inc.

7. Click Save. Click Cancel button, to cancel the configuration.

5.2.2. Delete

To remove a group
1. Click Admin module tab. The Admin page is displayed.
2. Click Complete View > Security Administration > Group Configuration node on the left-
side tree of the displayed page.
3. Alternatively, click the Group Configuration link in the Security Administration section on
the right-side of the client screen.
4. The Group Configuration page is displayed.
5. Select a group, by checking the check box of the group row.
6. Click Delete button.

On performing this, a confirmation message on the success or failure of the configuration is


displayed.

5.2.3. Modifying a Group's Profile

To modify a group's profile


1. Click Admin module tab. The Admin page is displayed.
2. Click Complete View > Security Administration > Group Configuration node on
the left-side tree of the displayed page.
3. Alternatively, click the Group Configuration link in the Security Administration
section on the right-side of the client screen.
4. The Group Configuration page is displayed.
5. Select a group, by checking the check box of the group row.
6. The Modify Group - <Group> form is displayed.
7. Under Members section, the users who have already enrolled in the group or displayed.

To add or delete new user(s), click Assign Users button. Modify profile window
for configuring the users pops-up. The Available Users field lists the existing users

who have not been enrolled. Use the Remove and Add options to remove
the user from the group or enroll the user to the group. Press Ctrl key to select
multiple users. Click Submit. Click Reset button, to reset the add/delete users
operation. Click Close button, to close the Modify profile pop-up window.
8. Under Operations Settings section, the Name column lists the operations for which
the group is permitted, the Type column lists the type of permission for the
corresponding operation and the Scope Setting column lists whether any custom view
scope is set for this operation. To add or delete new operations and modify the

permissions, click Configure button. Operations Tree window for configuring


the operation for groups pops-up. The Operation Tree Root lists all the existing
operations that the group can be permitted. These operations will be inherited by the
user belonging to this group. Use the Check box options to include, exclude, and not
authorize the operations for the group. Click Save. Click Cancel button, to cancel the
configuration.

Hints
• - Operation is authorized for the Group/User

Page 51
HFR, Inc.

• - Operation is not authorized for the Group/User

• - Not authorized for the Group/User but mutable

9. Under Custom View Scope section, the Authorized Scopes column lists the custom
view scopes authorized for this group.
o To add new custom view scopes, select Scope Name (module) from the combo

box and click Add New Scope button. Custom View Scope - Modify
page is displayed. Enter the name for the new custom view scope in Scope
Name field. In the Property Name combo box, select the required property
and enter the required value in the Property Value in the text field. Click Add
New button to add more properties and Delete icon against the properties to
remove them. Click Save. Click Cancel button, to cancel the configuration.

o To add or delete new custom view scope(s), click Assign Scope button.
Modify profile window for configuring the users pops-up. The Available
Scope field lists the existing scopes which have not been enrolled. Use the

Remove and Add options to remove the scopes from the group or
enroll the scopes to the group. Press Ctrl key to select multiple scopes. Click
Submit. Click Close button, to close the Modify profile pop-up window.
o To delete a custom view scope, select the scope(s), by checking the check box
of the scope row. Click Delete button.
o To modify custom view scopes, click on the Scope Name. Custom View Scope
- Modify page is displayed. Edit the name of the custom view scope in Scope
Name field. In the Property Name combo box, select the required property
and enter the required value in the Property Value in the text field. Click
More button to add more properties and Delete icon against the properties
to remove them. Click Save. Click Cancel button, to cancel the configuration.

On performing this, a confirmation message on the success or failure of the


configuration is displayed.

Operation Configuration

1. Click Admin module tab. The Admin page is displayed.


2. Click the Operation Configuration link in the Security Administration section on
the right-side of the client screen.
3. The Operation Configuration window pops-up.
4. Add or delete new operations in the Operations Tree window for configuring the
operation for groups and users. The Operation Tree Root lists all the existing
operations that the group and user can be permitted. Use the icon can be used for
adding new operation and Click Save. Use the icon can be used for removing the
existing operation.

Hints
• icon can be used for adding new operation

• icon can be used for removing the existing operation

Page 52
HFR, Inc.

6. Monitor/Management

• WebNMS Details

• JVM Management

• Performance Status

WebNMS Details

Using the Web Client, you can view the details of the CE-EMS Server, such as information on fault
status, ports in use, discovery status and scheduler details. These details help you in ascertaining the
performance of the CE-EMS Server and thereby administer it appropriately. For example, to ascertain if
there are any threading issues, you can view the details of the schedulers.

To view WebNMS Details


1. Click Admin module tab. The Admin page is displayed.

2. Click the Complete View > Monitor/Management > WebNMS Details node on the left-side
tree of the client screen.

3. Alternatively, click WebNMS Details link in the Monitor/Management section on the right-
side of the client screen.

• Viewing Fault Status

• Viewing Port Details

• Viewing Discovery Status

• Viewing Scheduler Details

6.1.1. Viewing Fault Status

Information on the Events and Alerts in the queue that are to sent, traps that are yet to be processed, and the
time at which the last trap was received, is displayed.

Page 53
HFR, Inc.

6.1.2. Viewing Port Details

Information on the ports that are currently occupied by CE-EMS is displayed. An example screen shot
is given below.

6.1.3. Viewing Discovery Status

Information on the Discovery module that are currently registered by CE-EMS is displayed. An detail information
and example screen shot is given below.

Discovery Module Details


Network Count Total number of networks discovered.
ManagedObject Count Total number of Managed Objects (MO) created.
Node Count Total number of nodes discovered in the network.
Total number of interfaces discovered in the network
Interface Count
elements.
Network Discovery Status
IP Address IP address of the discovered network.
The time at which the discovery of this network was
Discovery finished at completed.
Example: Wed Apr 07 15:36:10 GMT+05:30 2004
The time at which the next rediscovery process is
Rediscovery scheduled at scheduled.
Example: Thu Apr 08 15:36:10 GMT+05:30 2004

Page 54
HFR, Inc.

6.1.4. Scheduler Details

The information on the main, SchedulerForFailOver, BEModuleDispatcher, provisioning, policy, statuspoll,


config, datapoll, discovery, and UpdateProcessor schedulers is displayed. An example screen shot is
given below

JVM Management

Using the Web Client, you can view the details of the CE-EMS Server, such as information on back end
(BE) and front end (FE) servers, and the Clients. These details help you in ascertaining the
performance of the JVM of CE-EMS Server and thereby administer it appropriately

To view JVM Management


1. Click Admin module tab. The Admin page is displayed.

2. Click the Complete View > Monitor/Management > JVM Management node on the left-
side tree of the client screen.

3. Alternatively, click JVM Management link in the Monitor/Management section on the right-
side of the client screen.
Page 55
HFR, Inc.

4. Select the graphical display as either Line Graph or Area Graph by clicking the respective link.

5. Select the period of graphical data collected from the Select Period drop down list (Last 1 day,
Last Week and Last Month).

6. Click the Export JVM Details link of “Action” to export the JVM details from Web Client. The
JVMDetails.txt and JVMthreadDump.txt files are created and stored in <HFR CE-EMS FE
Home>/nmsanalyzer directory.
The following message appears on top of the page:

JVM Details have been exported to :JVMDetails.txt and


JVMthreadDump.txt

7. Click Report to WebNMS link of “Action” to upload the logs and other related CE-EMS files
from Web Client to AdvenNet.
The following message appears on top of the page:

Creating Zip File. Please Wait .........


This may take sometime depending on the size of the log files and the
database.

Enter your Email address, Subject, and Message in the File Upload Form. Click Send
button to send the Email with CE-EMS server details in zip.gz format for debugging. The
debug<DD_MM_YYYY_HH_MM_SS>.zip.gz file is created and stored in <Web NMS
Home>/ directory.

• Viewing Back End Server Details

• Viewing Front End Server Details

• Viewing Client Details

6.2.1. Back End Server Details

To view back end server details


1. Click BE Server Details tab.

Page 56
HFR, Inc.

The information on the machine where the Web NMS BE server is running is displayed. The
information, such as Host Name, Host Address, Server Started At, OS Name, Database Name,
Total Memory, and Free Memory is displayed. An example screen shot is given above.

CE-EMS JVM Monitoring collects, stores, and display the following System and Server
parameters as graphs by default:
For JVMs BE server
• CPU Utilization
• Memory Usage
• Number of threads spawned
• Data Collection Rate
• Status Polling Rate
• Trap Processing Rate
• Event Processing Rate
• Alert Processing Rate

6.2.2. Front End Server Details

To view Front End Server details

1. Click FE Server Details tab.

A list of FE servers that are connected to the BE is displayed. It provides information on the
Host Name (where FE server is running), Host Address (IP address of the machine where FE
server is running), Server Mode (Primary or Secondary), Client Communication Mode, RMI
Registry Port, and Web Server Port.

CE-EMS JVM Monitoring collects, stores, and display the following System and Server
parameters as graphs by default:
For JVMs FE server(s)
• CPU Utilization
• Memory Usage
• Number of threads spawned

6.2.3. Client Details

Page 57
HFR, Inc.

To view Client details

1. Click Client Details tab.

Information on the Clients that are connected to the BE is displayed.

Client Host The Client host name that is connected to the BE.
The type of client connected to the BE. It includes
Client Type
Application, Applet, and Web Start Clients.
Client ID The Client's ID using which the client is being accessed.
Memory
The memory used by the client application.
Usage(%)
Option to terminate the client remotely in case of abnormal
Terminate
usage of resources.

CE-EMS JVM Monitoring collects, stores, and display the following System and Server
parameters as graphs by default:
For JVMs Client(s)
• CPU Utilization
• Memory Usage
• Number of threads spawned

6.2.4. Performance Status

• Viewing Performance Status

Using the Web Client, you can view the details of CE-EMS module Performance. This helps you
in ascertaining the functioning of the module.

Viewing Performance Status


To view performance status
1. Click Admin module tab. The Admin page is displayed.

2. Click the Complete View > Monitor/Management > Performance Status node on the left-
side tree of the client screen.

3. Alternatively, click Performance Status link in the Monitor/Management section on the


right-side of the client screen.

4. Specify the node name for which you need to view performance statistics in Node Name field.

5. Click View Status.

Name OIDs for which statistics is being collected.


Page 58
HFR, Inc.

Number of times polling has been performed for the


Avg. polls per hour
configured time.
The success rate of the polling for the configured
Success poll cycles
time.
Poll interval in The interval at which the status polling is performed.
seconds It is displayed in seconds.
Specifies whether data collection is enabled for that
Data Collection
device.
Enabled
true - Enabled false - Disabled
Last collection time The time when data collection was last performed.
The time when data collection is to be performed
Next collection time
next.

From this page, if you need to view performance statistics for any other node,

1. Specify the node name in Node Name field.

2. From Period drop-down box, choose the period for which you need to view performance
statistics. It includes Today, Last Week, Last Month, and Custom.

If Custom is selected in Period drop-down box, specify the Start Date and End Date, the
range between which you need to view the performance statistics.

3. Click View Status.

Page 59
HFR, Inc.

7. Administrative Operations

• Mail Server Settings

• Web NMS Backup

• Re-sync with NEs after backup

• Re-sync with NEs

• Shutdown Server

• Configuring MTEAP

Mail Server Settings


To shut down the server
1. Click the Admin module tab. The Admin page is displayed.

2. Click the Complete View > Administrative Operations > Mail Server Settings node on the
left-side tree of the client screen.

3. Alternatively, click Mail Server Settings link in the Administrative Operations section on
the right-side of the client screen.

4. The Mail Server Settings page is displayed. This Screen contains the information regarding
Server Name, Server Port, User name, Password and Mail ID.

WebNMS Backup
To backup CE-EMS Database
1. Click the Admin module tab. The Admin page is displayed.

2. Click the Complete View or Admin Operations node on the left-side tree of the
displayed page.

3. Click WebNMS Backup.

4. A confirmation is asked. Click Yes. A backup of the available data is taken and stored in
files under the <HFR CE-EMS Home>/conf/backup directory.

Shut down Server


To shut down the server
1. Click the Admin module tab. The Admin page is displayed.

2. Click the Complete View > Administrative Operations > Shutdown Server node on the
left-side tree of the client screen.

Page 60
HFR, Inc.

3. Alternatively, click Shutdown Server link in the Administrative Operations section on the
right-side of the client screen.

4. A confirmation is asked. Click Yes to shut down the server.

Page 61
HFR, Inc.

8. Tools and Browsers

• MIB Browser

• Logs Monitor

• Audit Trails

Working with MIB Browser

To work with the MIB Browser


1. Click the Admin module tab. The Admin page is displayed.

2. Click the Complete View > Tools and Browsers > MIB Browser node on the left-side tree
of the client screen.

3. Alternatively, click MIB Browser link in the Tools and Browsers section on the right-side of
the client screen.

4. The MIB Browser page will get displayed on the right side of the screen.

Viewing the Server Log Files

To view the server logs


1. Click the Admin module tab. The Admin page is displayed.

2. Click the Complete View > Tools and Browsers > Logs Monitor node on the left-side tree
of the client screen.

3. Alternatively, click Logs Monitor link in the Tools and Browsers section on the right-side of
the client screen.

4. The Log Viewer tab of the Logs Monitor page is displayed.

5. Select the latest updated lines and select a log file to view its details. Select the latest updated
lines from the Show Last __ lines of drop down list and the server log file listed in the drop
down list. Click View Logs button.

6. The log file is displayed below in the line numbered format.

To view the database logs


1. Click the SPY Log Viewer tab of the Logs Monitor page to view the database transaction and
activity logs.

Viewing the Audit Trails

Page 62
HFR, Inc.

To view the audit trail of the users


1. Click the Admin module tab. The Admin page is displayed.

2. Click the Complete View > Tools and Browsers > Audit Trails node on the left-side tree of
the client screen.

3. Alternatively, click Audit Trails link in the Tools and Browsers section on the right-side of the
client screen.

4. The audit trail of all the users are displayed.

5. Select the number of lines to be displayed from the Page Length drop down list and use the
First, Previous, Next and Last buttons to navigate through the audit pages.

6. Use Clear Audit button to clear the audit entries.

7. Use Search button of “Actions” to search the audit entries based on the fields of the audit
entries. Select one of the options: Match any of the following, Match all of the following. Select
the field to be matched from the drop down list. Select the matching condition from the drop
down list. Enter the value of the field to matched. Click Search button.

Page 63
HFR, Inc.

9. Appendix A.

Page 64

You might also like