Cisco Prime Central for Hosted Collaboration Solution 9.2.1 Installation Guide
Appendix C: Running Processes
Downloads: This chapterpdf (PDF - 232.0KB) The complete bookPDF (PDF - 2.19MB) | Feedback

Processes and Log Files

Table Of Contents

Processes and Log Files

Verifying Prime Central Processes

Validating Prime Central Processes

Viewing Log Files

Verifying Event Collector Processes

Validating Event Collector Processes

Viewing Log Files

Verifying Service Visualizer Processes

Viewing Log Files

Verifying Correlation Engine (CE) VM Processes

Viewing Log Files

Verifying Infrastructure Monitoring Processes

Viewing Log Files


Processes and Log Files


This section describes the process that a healthy VM should be running along with the log file details. Under each component, you can see a list of running events, a procedure to validate the state, and the log files.

Verifying Prime Central Processes

Do the following to verify if the Prime Central processes are running:


Step 1 Log in as root user.

Step 2 To verify if the component is running as it should, run the grep command:

ps -ef | grep primeusr

Step 3 Verify if the output is as follows:

primeusr  5271     1  0 Dec12 ?        00:00:00 
/opt/disk2/prime/local/prime_secured/linux/prime_secured -q -f 
/opt/disk2/prime/local/prime_secured/prime_config
primeusr 16308     1  0 Dec12 pts/0    00:05:34 /opt/prime/XMP_Platform/jre/bin/java .....
primeusr  2609     1 99 14:03 ?        00:00:37 /opt/prime/utils/linux/jdk1.6//bin/java 
....
 
   

Do the following if proper processes are not running:


Step 1 Log into Prime Central as root.

Step 2 Run the following commands:

# su - primeusr

# portalctl stop

# itgctl stop

# itgctl start

# portalctl start


Validating Prime Central Processes

Do the folloiwng to validate the Prime Central processes:


Step 1 Log into the Prime Central portal to verify if processes are working as expected. Alternatively, you can also log on to the machine and as primeusr, run these commands to verify processes are working.

# su - primeusr

# portalctl status

Prime Central Platform Status
Started

Step 2 Run the following command:

# itgctl status

Prime Central - Integration Layer: Started
 
   

To verify if the cfm type reflects the Service Visualizer hostname:


Step 1 From Prime Central VM, log in as root user.

Step 2 Run the following command:

# su - oracle -c '$ORACLE_HOME/bin/sqlplus primedba/\"prime-admin-password\"@primedb'

Step 3 From the output, verify if cfm type is the hostname of Service Visualizer.

SQL*Plus: Release 11.2.0.1.0 Production on Mon Sep 10 09:46:29 2012
 
   
Copyright (c) 1982, 2009, Oracle.  All rights reserved.
 
   
 
   
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Real Application Testing options
 
   
SQL> SELECT TYPE, HOSTNAME, DB_USER, DB_PORT FROM DMINVENTORY;
 
   
TYPE
----------------------------------------
HOSTNAME
----------------------------------------
DB_USER
----------------------------------------
DB_PORT
----------------------------------------
cfm
sv-02
primedba
1521
 
   
SQL>

Viewing Log Files

To view Prime Central related log files:


Step 1 Log in as primeusr user.


Note Integration layer maintains servicemix log file with all the details.


Step 2 Open the following directory:

primeusr@pc [~]# cd esb/data/log

Step 3 Enter the following command to view the messages appearing in stdout/stderr:

primeusr@pc \[~/esb/data/log\]# portalctl start log

Step 4 Check whether the following log file is displayed:

primeusr@pc \[~/esb/data/log\]# less servicemix.log

Step 5 To set debug level for integration logs, add the following command to $PRIMEHOME/esb/etc/org.ops4j.pax.logging.cfg and restart the integration layer:

#HCS Logging

log4j.logger.com.cisco.hcm=DEBUG


Verifying Event Collector Processes

Do the following to verify if the required Event Collector processes are running:


Step 1 Log into the staging media VM as root user.

Step 2 Run the grep command for the nco:

ps -ef | grep nco

Step 3 From following output, verify if -authenticate PAM switch is displayed:

/opt/IBM/tivoli/netcool/omnibus/platform/linux2x86/bin/nco_pad -name NCO_PA -authenticate 
PAM -secure
 
   

If you do not see the -authenticate PAM switch in the process command line, the process may be running, but you will not be able to communicate with process control. If that is the case, you will need to restart process control using the nco script in /etc/init.d.

Step 4 Run the following command:

/etc/init.d/nco stop

/etc/init.d/nco start

Step 5 Verify if process control is running, and that the objectserver is up and running:

/opt/IBM/tivoli/netcool/omnibus/platform/linux2x86/bin/nco_objserv -name NCOMS -pa NCO_PA

Note The objectserver runs under process control due to the presence of the -pa NCO_PA switch. The -pa indicates that it is running under process control, and the NCO_PA displays the name of the process control that the objectserver is running under.


Step 6 Enter ps -ef to verify that the SNMP probe is running:

/opt/IBM/tivoli/netcool/omnibus/probes/linux2x86/nco_p_mttrapd -server NCOMS
 
   

For the EIF probe to run, the nonnative probe has to be up and running:

/opt/IBM/tivoli/netcool/omnibus/probes/linux2x86/nco_p_nonnative 
/opt/IBM/tivoli/netcool/platform/linux2x86/jre_1.6.7/jre/bin/java -server -cp 
/opt/IBM/tivoli/netcool/omnibus/probes/java/nco_p_tivoli_eif.jar:/opt/IBM/tivoli/netcool/o
mnibus/probes/java/NSProbe.jar:/opt/IBM/tivoli/netcool/omnibus/probes/java/IntegrationsSup
port.jar:/opt/IBM/tivoli/netcool/omnibus/java/jars/evd.jar:/opt/IBM/tivoli/netcool/omnibus
/java/jars/log.jar:/opt/IBM/tivoli/netcool/omnibus/probes/java -Xrs 
-DOMNIHOME=/opt/IBM/tivoli/netcool/omnibus nco_p_tivoli_eif
 
   

If that is running, verify if the EIF probe is running:

/opt/IBM/tivoli/netcool/platform/linux2x86/jre_1.6.7/jre/bin/java -server -cp 
/opt/IBM/tivoli/netcool/omnibus/probes/java/nco_p_tivoli_eif.jar:/opt/IBM/tivoli/netcool/o
mnibus/probes/java/NSProbe.jar:/opt/IBM/tivoli/netcool/omnibus/probes/java/IntegrationsSup
port.jar:/opt/IBM/tivoli/netcool/omnibus/java/jars/evd.jar:/opt/IBM/tivoli/netcool/omnibus
/java/jars/log.jar:/opt/IBM/tivoli/netcool/omnibus/probes/java -Xrs 
-DOMNIHOME=/opt/IBM/tivoli/netcool/omnibus nco_p_tivoli_eif

Verify if the Oracle gateway is running:

/opt/IBM/tivoli/netcool/omnibus/bin/linux2x86/nco_g_oracle
 
   

Step 7 If the above processes are not running, restart Event Collector with the following commands:

/etc/init.d/nco stop

/etc/init.d/nco start


Validating Event Collector Processes

Run the following command to validate the status of the process controls:

nco_pa_status -user root -password password

The output must reflect the following:

-------------------------------------------------------------------------------
Service Name         Process Name         Hostname   User      Status      PID
-------------------------------------------------------------------------------
SNMPGateways         SNMPGateway1         ec-02      netcool   PENDING       0
                     SNMPGateway2         ec-02      netcool   PENDING       0
                     SNMPGateway3         ec-02      netcool   PENDING       0
                     SNMPGateway4         ec-02      netcool   PENDING       0
                     SNMPGateway5         ec-02      netcool   PENDING       0
Core                 MasterObjectServer   ec-02      netcool   RUNNING    9908
                     SnmpProbe            ec-02      root      RUNNING    9909
                     OracleGate           ec-02      netcool   RUNNING    9911
                     EIFProbe             ec-02      netcool   RUNNING    9912
-------------------------------------------------------------------------------

Viewing Log Files

To view Event Collector log files:


Step 1 Log in as netcool user.

Step 2 Open the following directories:

/opt/IBM/tivoli/netcool/omnibus/log

/opt/IBM/tivoli/netcool/log

/home/netcool/.acsi_netcool/logs

Check whether the following log files are displayed: 
/opt/IBM/tivoli/netcool/omnibus/log/mttrapd.log
/opt/IBM/tivoli/netcool/omnibus/log/nco_g_oracle.log
/opt/IBM/tivoli/netcool/omnibus/log/nco_g_oracle.log
/opt/IBM/tivoli/netcool/omnibus/log/NCO_GATE_#.log
/opt/IBM/tivoli/netcool/omnibus/log/NCOMS.log
/opt/IBM/tivoli/netcool/omnibus/log/NCO_PA.log
/opt/IBM/tivoli/netcool/omnibus/log/tivoli_eif.log

Verifying Service Visualizer Processes

Do the following to verify the Service Visualizer processes:


Step 1 Log into the staging media VM as root user.

Step 2 Run the following command:

ps -ef | grep -i TBSMProfile | cut -b 2287-2361

The following output appears:

/opt/IBM/tivoli/tipv2/profiles/TBSMProfile/config TBSMCell TBSMNode server1

Step 3 Run the following command:

ps -ef | grep -i TIPProfile | cut -b 2406-2478

The following output appears:

/opt/IBM/tivoli/tipv2/profiles/TIPProfile/config TIPCell TIPNode server1

Step 4 Check if Service Visualizer GUI is up and running. From the above output, check if the following are displayed:

 
   
/opt/IBM/tivoli/tipv2/profiles/TBSMProfile/config TBSMCell TBSMNode server1
/opt/IBM/tivoli/tipv2/profiles/TIPProfile/config TIPCell TIPNode server1


These show that both the TBSM and the TIP interfaces are up and running.

Step 5 If you do not see the output, you must restart the Service Visualizer. Run the following commands:

/etc/init.d/tbsm stop

/etc/init.d/tbsm start


Note Do not use /opt/IBM/tivoli/tbsm/bin/tbsm_suite.sh.


Viewing Log Files

To view Service Visualizer related log files:


Step 1 Log in as netcool user.

Step 2 Open the following directories:

/opt/IBM/tivoli/tipv2/profiles/TBSMProfile/logs

/opt/IBM/tivoli/tipv2/profiles/TIPProfile/logs

/opt/IBM/tivoli/tbsm/logs

Step 3 Check whether the following log files are displayed:

/opt/IBM/tivoli/tipv2/profiles/TBSMProfile/logs/server1/trace.log 
/opt/IBM/tivoli/tipv2/profiles/TBSMProfile/logs/tbsm/RAD_eventbroker.log 
/opt/IBM/tivoli/tipv2/profiles/TIPProfile/logs/webtop.log.
/opt/IBM/tivoli/tipv2/profiles/TIPProfile/logs/server1/startServer.log.
/opt/IBM/tivoli/tipv2/profiles/TBSMProfile/logs/server1/SystemOut.log.
/opt/IBM/tivoli/tipv2/profiles/TIPProfile/logs/server1/SystemOut.log.
/opt/IBM/tivoli/tipv2/profiles/TIPProfile/logs/server1/SystemErr.log.
/opt/IBM/tivoli/tipv2/profiles/TIPProfile/logs/server1/trace.log.
/opt/IBM/tivoli/tbsm/logs/rad_radshell_errors.log.
/opt/IBM/tivoli/tbsm/logs/tbsmout.log.
/opt/IBM/tivoli/tbsm/logs/netcool.log.

Verifying Correlation Engine (CE) VM Processes

To check if Correlation Engine is functioning as it should, you need to verify the eWAS server, the jrexec, and the Jmx client processes. Do the following to determine if the required processes are running:


Step 1 Log into the staging media VM as root user.

Step 2 Open the following directories:

/etc/init.d/impact status

Check whether the following PIDs are up and running:

Process Tivoli Integrated Portal running - PID >3778<
Process Tivoli Netcool Impact running - PID >3939<
Process Tivoli Netcool Impact JRExec Server running - PID >4069<

If the above processes do not run as required, restart Correlation Engine run the following commands:

/etc/init.d/impact stop

/etc/init.d/impact stop


Viewing Log Files

To view Correlation Engine related log files:


Step 1 Log in as netcool user.

Step 2 Open the following directory:

/opt/IBM/tivoli/impact/logs

Step 3 Check whether the following log files are displayed:

NCI_eventprocessor.log
NCI_omnibuseventreader.log
NCI_policylogger_DefaultExceptionHandler.log
NCI_policylogger_Enrichment_policy1.log
NCI_policylogger_Enrichment_policy2.log
NCI_policylogger_Enrichment_policy3.log
NCI_policylogger_Flapping.log
NCI_policylogger_Import.log
NCI_policylogger.log

Step 4 You can also view the log files in the following directories:

/opt/IBM/tivoli/tipv2/logs/

/home/netcool/.acsi_netcool/logs/


Verifying Infrastructure Monitoring Processes

To check if the appropriate processes are up and running, do the following:


Step 1 Log into the staging media VM as root user.

Step 2 Run the following command to verify if DB2 is running:

# ps -ef | grep db2

The following output appears:

root     10905     1  0 Dec14 ?        00:00:00 db2wdog
db2inst1 10907 10905  0 Dec14 ?        00:01:29 db2sysc
root     10908 10907  0 Dec14 ?        00:00:00 db2ckpwd
root     10909 10907  0 Dec14 ?        00:00:00 db2ckpwd
root     10910 10907  0 Dec14 ?        00:00:00 db2ckpwd
db2inst1 10920 10905  0 Dec14 ?        00:00:07 db2acd   
,0,0,0,1,0,0,0,1,0,8a65b0,14,1e014,2,0,1,11fc0,0x210000000,0x210000000,1600000,4bc0005,2,2
1ab000d
db2fenc1 14819 10905  0 Dec14 ?        00:00:00 db2fmp ( 
,1,0,0,0,0,0,0,1,0,8a65b0,14,1e014,2,0,1,31fc0,0x210000000,0x210000000,1600000,4bc0005,2,2
1d7002a
db2fenc1 27468 10905  0 Dec14 ?        00:00:00 db2fmp ( 
,0,0,0,0,0,0,0,1,0,8a65b0,14,1e014,2,0,1,91fc0,0x210000000,0x210000000,1600000,4bc0005,2,2
23c002e
root     28070 24613  0 11:23 pts/1    00:00:00 grep db2
root     32586     1  0 Dec14 ?        00:00:11 /opt/ibm/db2/V9.7/bin/db2fmcd
dasadm1  32663     1  0 Dec14 ?        00:00:00 /opt/ibm/db2/V9.7/das/bin/db2fmd -i 
dasadm1 -m /opt/ibm/db2/V9.7/das/lib/libdb2dasgcf.so.1
dasadm1  32665     1  0 Dec14 ?        00:00:00 /home/dasadm1/das/adm/db2dasrrm

Step 3 To see what processes are running on Infrastructure Monitoring, run the following command:

cd /opt/IBM/ITM/bin

You will change directory to ITM_HOME/bin.

Step 4 Run the following command to know the agents and processes that are running:

./cinfo -r

The following output appears:

*********** Sat Mar 30 17:40:48 CDT 2013 ******************
User: root Groups: root bin daemon sys adm disk wheel
Host name : im-07 Installer Lvl:06.23.02.00
CandleHome: /opt/IBM/ITM
***********************************************************
Host     Prod  PID    Owner  Start  ID       ..Status
im-07  ms    4673   root   13:36  TEMS       ...running
im-07  kf    5507   root   13:37  None       ...running
im-07  lz    6383   root   13:37  None       ...running
im-07  ul    18790  root   13:37  None       ...running
im-07  cq    29563  root   13:37  None       ...running
im-07  vm    2768   root   13:37  vcenter02  ...running
im-07  r4    11138  root   13:37  vcenter02  ...running
im-07  r4    13189  root   13:37  cuom       ...running
im-07  r4    14871  root   13:37  cucdm      ...running

To determine if TEMS is started and is up and running, check the following process:

im-07 ms 4673 root 13:36 TEMS ...running
 
   

To determine if the TEMS is started and is up and running, check the following process:

im-07 cq 29563 root 13:37 None ...running
 
   

If the processes are running, go to Step 5. Else, go to Step 6.

Step 5 Log into Infrastructure Monitoring to either start or stop, and then configure any of the other agents, as required. To bring up the GUI interface to manage the processes and agent, run the following command:

itmcmd manage

Step 6 If the above processes do not run as required, restart Infrastructure Monitoring:

/etc/init.d/im stop

/etc/init.d/db2 stop

/etc/init.d/db2 start

/etc/init.d/im stop


Viewing Log Files

To view Infrastructure Monitoring related log files:


Step 1 Log into the staging media VM as root user.

Step 2 Open the following directory:

/opt/IBM/ITM/logs/

Step 3 Check whether the following log files are displayed:

/root/ITM_Common_LP_Installer-00.log
/root/ITM_LP_Installer-00.log

Step 4 You can also view the log files in the following directories:

/opt/ibm/db2/V9.7/logs/

/home/netcool/.acsi_netcool/logs/