SiteScope metrics not available in HP PM when integrated to PM and HP BSM

When HP SiteScope (SS) 11.10 is integrated with standalone HP Performance Manager (PM) 9.00.00 and the same SS server is integrated to HP Business Service Management (BSM) 9.x, the metrics are no longer viewable in PM. The metrics continue to be visible in BSM 9.0.

SiteScope cannot be integrated with BSM as well as standalone PM. SiteScope should be integrated to one of the products, either BSM or PM, but not both as integration with BSM take precedence over integration with PM.

Advertisements

Seeing _reportTopology=true when runn getfullconfiguraiton api

If you use the web services API in SiteScope extensively you might have a concern with the getFullConfigurationSnapshot method. Script monitors as well as several other monitors do not allow BAC Topology reporting. This is not an option in the SiteScope GUI. However, script monitors might show ‘_reportTopology’ => ‘true’ in the output. Report Topology has known problems in certain versions of BAC and HP support has instructed to disable topology reporting on SiteScope.

Review the “Using SiteScope” manual in which it is mentioned that Monitors Not Reporting Topology Data By Default Following is a list of those monitors that do not monitor the status of a host or server. For these monitors to report CI information to BSM, you must select the CI type, enter the required CI key attributes, and select an indicator relevant for the CI type linked to the monitor. The monitors include:

Composite Monitor

Directory Monitor

e-Business Transaction Monitor

File Monitor

Formula Composite Monitor

HP NonStop Event Log Monitor

JMX Monitor (when not monitoring WebLogic)

Link Check Transaction Monitor

Log File Monitor

Microsoft Windows Dial-up Monitor

Microsoft Windows Media Player Monitor

Multi Log File Monitor

Network Bandwidth Monitor

Real Media Player Monitor

Script Monitor

SNMP Trap Monitor

URL Monitor

URL Content Monitor

URL List Monitor

URL Sequence Monitor

XML Metrics Monitor

These monitors by default do not report to BSM/BAC and it really doesn’t matter what the _reportTopology flag is set or not. The _reportTopology is simply a placeholder for the class instances and is not used on the above monitors.

SiteScope hangs when Opening the GUI

SiteScope 11.12 64 bit installed on Windows server 2008 64 bit.

When trying to login to SiteScope and when opening the GUI or dashboard, SiteScope hangs and progress bar is showing, and stays at the same status.

To restart, the browser needs to be closed and opened up again.

This is a problem with the Java client used.

Make sure the JRE 6 is of update 027 or higher – there is a known published bug with JRE 24-26 which hangs the UI.

SiteScope Log Monitor error message “iconv: illegal input sequence at position”

In SiteScope (SiS) the Log Monitor using "server-side processing" could throw the error message:

ERROR – Error during log parsing: iconv: illegal input sequence at position

The "server-side processing" feature converts the monitored log/text file on the LINUX system.

The used command is iconv – Convert encoding of given files from one encoding to another.

The error message is from the command because the chosen file encoding in the monitor settings does not correspond to the real file encoding.

A different file encoding should be selected, till the error disappears.

SiteScope Log Monitor error message “awk: line 1: syntax error at or near”

In SiteScope (SiS) the Log Monitor using "server-side processing" could throw the error message:

ERROR – Error during log parsing: awk: line 1: syntax error at or near, awk: line 1: syntax error at or near }

The cause is the awk version.

RedHat use GNU awk (GNU Awk 3.1.7), Debian mawk (mawk 1.3.3 Nov 1996, Copyright (C) Michael D. Brennan).

The Debian’s awk does not support 3th argument for match function.

SiteScope is not checking what it needs to execute the command correctly, and there is no adaption depending of the used awk version on the remote system.

To check the AWK version execute “awk –W version”.

To install the gawk on Debian like systems use “apt-get install gawk”.

To test manually the issue use the command:

tail -c +1 <PATH + LOG FILE> |

awk ‘BEGIN{sismatches=0; if("") { RS ="" }} \

{ if((regexp && match($0, "123",groups)) ||

(!regexp && index($0, "123"))) {sismatches=sismatches+1; print "sis-matches"; \

i=0; while("true") { if (i in groups) { print "sis-match-group"; print groups[i]; i=i+1 } else {break}}}} END {if(sismatches == 0) {print "sis-no-matches-found"}}’ regexp=;

On success the message will be : “sis-no-matches-found”.

Otherwise the message will be like “syntax error at or near”.

SiteScope monitor often encounters “System error 1219” for Windows Remote

System error 1219 is from Windows OS, not SiteScope error. That means, Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.

When user configures Windows Remote and some monitors(i.e. CPU, Logfiles), user may encounter the 1219 error by perfex.

Here is a sample.

18:03:04 12/20/2011 good group.25 CPU_monitor no data due to Error: CPU Monitor error for machine \\10.0.0.1, exit code: 1219 3:19 n/a

This is one of the examples,

a. Customer configured Domain Administrator user as SiteScope Service account.

DOMAIN1\Administrator

b. Customer configured local administrator user as Windows Remote in SiteScope.

10.0.0.1\administrator

Since the SiteScope service runs as Domain Administrator user, the SiteScope may access to remote shared resource by the account.

CPU, Memory and Disk monitors used perfex command to monitor the remote server.

The credential is based on Windows Remote configuration in SiteScope.

To avoid this issue, we have two solution.

1. Using alias hostname for each monitored servers.

1-1. Add alias hostname to C:\Windows\System32\drivers\etc\hosts

i.e.

10.0.0.1 host-A host-A1

1-2. Edit Remote Server configuration in SiteScope

i.e.

Server: host-A1

Credentials: host-A1\administrator

SiteScope can access to Windows Remote server by using alias hostname instead of original configuration(i.e. IP address, original hostname).

Since SiteScope uses the alias name for perfex connection, the user never conflict.

or

2. Using -optionalSetupConnection as perfex option.

2-1. Add the follosing optin in \SiteScope\groups\master.config file

_perfexOptions=-optionalSetupConnection

2-2. Restart SiteScope service

It was recommended that SiteScope monitor uses Remote Windows servers configuration instead of running the service as a specific user. This works fine for most cases.

However, user will need to check the credential if all kind of monitor can work.

SiteScope monitor often encounters “System error 1219” for Windows Remote

System error 1219 is from Windows OS, not SiteScope error. That means, Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.

When user configures Windows Remote and some monitors(i.e. CPU, Logfiles), user may encounter the 1219 error by perfex.

Here is sample.