How to diagnose SystemEDGE SRM\Spectrum SPM Test Failures

book

Article ID: 110664

calendar_today

Updated On:

Products

CA Systems Performance for IM (SystemEdge) CA eHealth

Issue/Introduction

  • This articles describes how to diagnose the root cause of test failures of SRM\SPM tests of any type.


Environment

Release:
Component: VPMGEN

Resolution

The best way to troubleshoot SystemEDGE SRM\Spectrum SPM test failures is as follows:

1. Stop SystemEDGE.
2. Take a backup of the SystemEDGE\port1691\plugins\svcrsp\svcrsp.cf file.
3. Remove all tests but the problem test from the bottom of the svcrsp.cf file (this will make the log much easier to read).
4. Put the SRM AIM into debug via the svcrsp.cf
loglevel=7 
5. Start SystemEDGE.
6. Check the C:\Users\Public\CA\SystemEDGE\port1691\plugins\svcrsp\jcollector.log for errors. 

As an example, the second error is the useful part of the message, the ERRORCODE:50 is not very useful when you look at the corresponding description in the guide (linked under additional information). 

[LOG_CRITICAL][2018-08-09 08:29:49][Thread:Thread-234551][Pass #67057]: [#14229] ERRSRC:http ERRCODE:50 INDEX:14229 NAME: TESTDESC:HTTP_PROXY ERROR: jcollector.SATestException: Invalid proxy port.

Additional Information

Service Response Monitor Error Codes
https://support.ca.com/cadocs/0/CA%20Virtual%20Assurance%20for%20Infrastructure%20Managers%2012%209-ENU/Bookshelf_Files/HTML/UIHelp/index.htm?toc.htm?1459357.html