SiteScope UNIX Monitor Installation

Requirements

Below are the requirements to install and monitor UNIX using SiteScope.

· Server Resource monitor license

· LoadRunner 7.51 or above:

· For LoadRunner 7.6 or above, the SiteScope UNIX monitor is built into the Controller.

· For LoadRunner 7.51 SP1, make sure that you install the Controller add-in, LR_New_SiteScope_Monitor.exe. This is available in the Patches database ® LoadRunner ® 7.51 SP1 ® Performance Monitor ® LR751SP1P2 ® LoadRunner 7.51 SP1 SiteScope Unix monitor for LoadRunner version 7.51.

· SiteScope Lite installation:

· For LoadRunner 8.x , the SiteScope Lite installation file is available in the additional components CD under SiteScope -> sitescopelrsetup.exe

· For LoadRunner 7.6 or above, the SiteScope Lite installation file (SiteScopeSetupForLR.exe) and SiteScope Lite license is available in the Patches database ® LoadRunner ® 7.6 ® Performance Monitor ® LR76P6 – LoadRunner 7.6 SiteScope Siebel and SAP Portal Add-in for LoadRunner.

· For LoadRunner 7.51 SP1, the SiteScope Lite installation file and SiteScope Lite license is available in the Patches database ® LoadRunner ® 7.51 SP1 ® Performance Monitor ® LR751SP1P2 ® LoadRunner 7.51SP1 SiteScope Unix monitor for LoadRunner version 7.51.

SiteScope Installation

Ensure you have LoadRunner 7.51 SP1 or above installed. Ideally, you will want an extra machine for the SiteScope installation:

· First machine ® Controller

· Second machine ® SiteScope

· Third machine ® Load Generator

· Fourth machine ® Load Generator

Etc.…

In this situation, SiteScope will be gathering information from the Unix Servers and displaying them via a Web interface. The Controller will then connect to the SiteScope installation and retrieve this data during the scenario run.

General Installation

  1. Obtain the SiteScope Lite installation file and SiteScope Lite license.

2. On the machine where you wish to install SiteScope, run the installation file as explained in the Requirements section.

3. In the “Administrator E-mail Address” window, enter an E-mail if you want a designated person to receive Alerts, reports, and status messages. Otherwise, click <Next> to proceed to the next window.

4. Follow all the defaults settings to complete the SiteScope Lite installation.

5. When the installation of SiteScope is completed, a browser will automatically come up with instructions on how to start SiteScope. The way to bring up SiteScope is via a browser with the URL http://<machine-name>:8888/SiteScope.

As you can guess, SiteScope installs its own Web Server as an interface to the application.

License Installation for SiteScope

  1. The first time you start SiteScope, you will get a “SiteScope First Time Setup” page. Click on “Skip this Page” to go to main SiteScope site.

2. Once the Auto Configuration completes, you will be brought to the main SiteScope page.

3. Click on the “Preferences” link from the main SiteScope panel.

4. Enter the license in the “License Number” textbox.

5. Click the “Save Changes” button.

How to remove existing groups

On the SiteScope main page, you will see the following groups by default:

· Network

· Server

You are recommended to delete both of these groups.

1. Click on the group name (e.g., Network, or Server).

2. At the bottom of the page, click on “Delete this Group.”

3. On the Confirmation page, click on the “Delete <GroupName>” button to confirm the deletion.

How to add a SiteScope UNIX monitor group

  1. On the SiteScope main page, click on “Create Groups.”
  2. Enter a name for the group (e.g., LoadRunner Unix).
  3. Click on the “Add” button.

How to add a monitor to a group

Example:

Steps to add a CPU monitor:

1. From the SiteScope main page, click on the group name to go to the group.

2. Click on “Add a New Monitor to this Group.”

3. Click on “Add CPU Utilization Monitor.”

4. Click on “Choose a Server.” (This portion will add your Unix server to the machine list.)

5. Click on “Setup Unix Remote.”

6. Click on “Add a Remote Machine.” Enter the following information:

· Server Address

· OS Type

· Connection method: Choose “Telnet” as the connection method.

SiteScope uses a telnet login to access the machine and run standard Unix commands to gather machine statistic information. Due to this new process, you must ensure that you have a valid account that you can telnet into. In addition, you must ensure that the account you are using allows all the SiteScope commands to be executed. You can see a list of the commands SiteScope uses within the files in the C:<SiteScope>templates.os folder.

· Login and Password

· [Optional] Modify the waiting prompt on the Advanced Options.

7. Click on “Add Remote Server.” An automated test process to make sure SiteScope can access the machine is performed.

8. Click on “Back to Remote Machines.”

9. Click on “Return to Choose Servers.”

10. Choose the server created from the “Server” drop-down list.

11. Click on “Choose Server.”

12. Change the update time to 15 seconds.

13. Click on “Add Monitor.”

You have now added a Unix CPU monitor to SiteScope.

How to add an additional monitor to a group

Example:

Steps to add a Memory monitor:

1. Click on “Add a New Monitor to this Group.”

2. Click on “Add Memory Monitor.”

3. Choose the server that you added previously.

4. Change the update time to 15 seconds.

5. Click on “Add Monitor.”

You have now added a Unix Memory monitor to SiteScope.

Setting up a SiteScope UNIX Monitor in the Controller

1. In the Controller, look for the SiteScope monitor in the System Resource Section.

2. Display the graph by dragging it to the right. Right-click in the graph and select “Add Measurement(s).” You should now see the SiteScope Dialog box.

3. Click on the first “Add” button. For the machine name, type in the IP address or the machine name of the system on which SiteScope is installed. Click <OK>.

4. Click on the Second “Add” button. You should now see a SiteScope Monitor Configuration window. In the left pane, you should see a tree with the monitors you have added into the SiteScope application. Simply highlight the available monitors and choose the counters in the right pane. Click <OK> to get out of the menus.

5. You have now set up the New UNIX SiteScope monitor.

Advertisements

Error in Sitescope’s bac_integration\discovery.log file

Business Availability Center (BAC) 8.04, SiteScope 10.11

SiteScope\bac_integration\discovery.log shows:

2010-10-01 17:14:42,610 [SiteScope Main] … UCMDB\.PROBE\.(\d+\.\d+.\d+)\.Build_(\d+) does not matches data in file c:\collectors\versions.properties

2010-10-01 17:14:42,610 [SiteScope Main] (CollectorsParameters.java:506) ERROR – Using default UCMDB.PROBE.8.0.Build_0

SiteScope and BPM installed on the same server is causing a port conflict.

If you have BPM and SiteScope installed on same machine, this creates a port conflict. BPM cannot be installed on the same machine as SiteScope.

SAP CCMS Monitors – Failed to Get Counters

Unable to manually add SAP CCMS Monitors for one particular SAP server instances, SiteScope shows an error: "Failed to get Counters"

This is not a SiteScope issue, is normally associated to Windows Buffer issues, this can be confirmed using SiteScope SAP DEBUG, a new log file will be created only for SAP monitors, the file name is sap_monitors.log, in this file a message like the following could be found it:

ERRNO TEXT WSAENOBUFS: No buffer space available

How to activate the SAP DEBUG

Open this file in your SiteScope server: SiteScope\conf\core\Tools\log4j\PlainJava\log4j.properties

At the end of the file, add these lines:

##################################################################################

# SAP monitors

##################################################################################

log4j.category.com.mercury.sitescope.monitors.sap=DEBUG, monitors.sap.appender

log4j.additivity.com.mercury.sitescope.monitors.sap=false

log4j.appender.monitors.sap.appender=org.apache.log4j.RollingFileAppender

log4j.appender.monitors.sap.appender.File=../${log.file.path}/sap_monitors.log

log4j.appender.monitors.sap.appender.MaxFileSize=${def.file.max.size}

log4j.appender.monitors.sap.appender.MaxBackupIndex=${def.files.backup.count}

log4j.appender.monitors.sap.appender.layout=org.apache.log4j.PatternLayout

log4j.appender.monitors.sap.appender.layout.ConversionPattern=%d [%t] (%F:%L) %-5p – %m%n

##################################################################################

Close the file and try to create the SAP monitor again.

As this is a Windows issue, we recommend review the following links:

http://sap.ittoolbox.com/groups/technical-functional/sap-basis/wsaenobufs-no-buffer-space-available-in-saprouter-1193692

http://technet.microsoft.com/en-us/library/bb124810%28EXCHG.65%29.aspx

http://support.microsoft.com/kb/196271/en-us

SiteScope 10.12 – Technology Database Integration monitor does not work correctly

SiteScope 10.12 – Technology Database Integration monitor does not work correctly

Customer has various Technology Database Integration monitors set up (63 in total, this number will increase)

– there is only one monitor working as expected

– various other do NOT work

– all monitors query the same database with a similar query like

SELECT d.dns_name, t.tname, e.color,e.created FROM devices d, present_events e, tests t WHERE (d.did=e.hostname_id and t.tid=e.testname_id and d.did=’1938′ and t.tname=’brian’)

– the monitors should always return a value ( 1 row collected)

This is due to the nature of the table (view) the monitor queries. The entries are feed in from a different system and updated all two minutes, and reflect one particular status.

The monitor thus is supposed to pick up the current status, and pass it on to BAC.

trace of a working monitor:

2010-07-14 09:31:01,362 [ALFA_brian(group.71/1) ] (DefaultDataCollector.java:67) DEBUG – going to execute query: SELECT d.dns_name, t.tname, e.color,e.created FROM devices d, present_events e, tests t WHERE (d.did=e.hostname_id and t.tid=e.testname_id and d.did=’1938′ and t.tname=’brian’) AND e.created > 2010-07-14 09:18:37.497 ORDER BY e.created

2010-07-14 09:31:01,362 [ALFA_brian(group.71/1) ] (DefaultDataCollector.java:97) DEBUG – add event to the buffer

2010-07-14 09:31:01,362 [ALFA_brian(group.71/1) ] (DefaultDataCollector.java:126) DEBUG – New enumerating field’s value is: 2010-07-14 09:18:37.497258

2010-07-14 09:31:01,362 [ALFA_brian(group.71/1) ] (DefaultDataCollector.java:129) DEBUG – 1 events created of 1 data rows

2010-07-14 09:31:01,799 [ALFA_brian(group.71/1) ] (ObserverSource.java:81) DEBUG – update method started

2010-07-14 09:31:01,799 [ALFA_brian(group.71/1) ] (ObserverSource.java:87) DEBUG – pushing the event {COLOR=green, TNAME=brian, DNS_NAME=ALFA, created=2010-07-14 09:18:37.497258}

2010-07-14 09:31:01,799 [ALFA_brian(group.71/1) ] (Probe.java:138) DEBUG – ==>pushEvent

2010-07-14 09:31:01,799 [ALFA_brian(group.71/1) ] (Probe.java:152) DEBUG – <==pushEvent execution time 0 seconds

2010-07-14 09:31:01,799 [ALFA_brian(group.71/1) ] (JdbcMonitor.java:92) DEBUG – the monitor updated successfully collected 1 events , sent 1 events to Topaz, ignored 0 events

2010-07-14 09:31:01,799 [ALFA_brian(group.71/1) ] (Probe.java:39) DEBUG – ctor

trace of a non-working monitor:

2010-07-14 09:31:02,143 [axalfa_conn(group.72/1) ] (DefaultDataCollector.java:67) DEBUG – going to execute query: SELECT d.dns_name, t.tname, e.color,e.created FROM devices d, present_events e, tests t WHERE (d.did=e.hostname_id and t.tid=e.testname_id and d.dns_name=’mnp.server.na.avtenti’ and t.tname=’http’) AND e.created > 2010-01-22 13:11:57.0 ORDER BY e.created

2010-07-14 09:31:02,143 [axalfa_conn(group.72/1) ] (DefaultDataCollector.java:97) DEBUG – add event to the buffer

2010-07-14 09:31:02,143 [axalfa_conn(group.72/1) ] (DefaultDataCollector.java:144) DEBUG – 1 events removed from the collection

2010-07-14 09:31:02,143 [axalfa_conn(group.72/1) ] (DefaultDataCollector.java:126) DEBUG – New enumerating field’s value is: null

2010-07-14 09:31:02,143 [axalfa_conn(group.72/1) ] (DefaultDataCollector.java:129) DEBUG – 0 events created of 1 data rows

2010-07-14 09:31:02,596 [axalfa_conn(group.72/1) ] (JdbcMonitor.java:92) DEBUG – the monitor updated successfully collected 0 events , sent 0 events to Topaz, ignored 0 events

The cause is unknown at the moment:

– DB query is perfectly fine. From the DB design the data queried is just a status, feedback from another system, and updated all 2 minutes

– stopped SiteScope, deleted mg.bak and .dyn file for axalfa_conn, started SiteScope, now the new timestamp is reflected, but still nothing is returned

To fix this issue,

– all monitors run all 5 minutes, after changing this to 1 minute, the monitor starts to work as expected!

– one minute nothing is returned, as the data in the database has not been updated,

DEBUG – add event to the buffer

DEBUG – 1 events removed from the collection

DEBUG – New enumerating field’s value is: null

DEBUG – 0 events created of 1 data rows

DEBUG – the monitor updated successfully collected 0 events , sent 0 events to Topaz, ignored 0 events

in the next run (one minute later), data is retrieved and we see a trace like

DEBUG – add event to the buffer

DEBUG – New enumerating field’s value is: 2010-07-15 13:18:37.497258

DEBUG – 1 events created of 1 data rows

DEBUG – pushing the event {COLOR=green, .. , created=2010-07-15 13:16:37.497258}

DEBUG – the monitor updated successfully collected 1 events , sent 1 events to Topaz, ignored 0 events

– tried with 5 minutes again, then the monitor doesn’t work anymore, same for 2,3,4 minutes, or 110 seconds

only 1 minute works

Change all monitors to execute every 1 minute.

SiteScope 11.x New Available Monitors

SiteScope 11.x introduces several new monitor types. Where can information be found on these new monitors?

New monitors in SiteScope 11.x are: Amazon Elastic Compute Cloud (EC2), HP Integrated Lights-Out (iLO), and Microsoft Hyper-V.

Documentation for each monitor can be found in the <SS>\sisdocs\pdfs\SiteScopeMonitorReference.pdf file:

Amazon Web Services Monitor: Chapter 2, Page 29

HP ILO (Integrated Lights-Out) Monitor: Chapter 25, Page 193

Microsoft Hyper-V Monitor: Chapter 42, Page 313

SiteScope failed to start

If you have installed SiteScope 11.0 version on Linux machine and if the install was successful but if it is fails to start and in result if you are unable to logon to the web-site for further configurations .

fmdqaipt005:fmdadm,207% ./start

SiteScope failed to start as a background process

fmdqaipt005:fmdadm,208% ./stop

SiteScope service process not running – pid file not found

SiteScope monitor process not running – monpid file not found

The reason for this is because you don’t have root access when starting SIS

Validate if the user has root access to start and stop the SIS processes in Linux

Once the user gets a SUDO command to start and stop SIS this problem will be resolved.

SiteScope Daily Restart Behavior Change 11.x

Since upgrading to SiteScope 11.0, the service does not seem to restart every 24 hours as before.

This is a new feature for SiteScope 11.x and future versions. The SiteScope service no longer requires a daily restart to reallocate resources to the service. This will increase the overall uptime of the service and monitoring process. SiteScope can still be manually stopped and started, however this should only be necessary during troubleshooting and not be needed regularly.