Debugging SPM Test Timeouts

Products

• CA Spectrum
• CA eHealth

Issue/Introduction

Is there further debug we can do to troubleshoot SPM Test timeouts?

Resolution

Turn ON debugging:

To add debugging information to a timeout event, use the following CLI command:

update action=0x456000e mh=<RTM_Test Model_Handle>

Where RTM_Test Model_Handle is the Model_Handle attribute for the SPM Test model.

Example:

bash -login

cd vnmsh

./connect

./update action=0x456000e mh=0x100f7a

 

 

The following information will be added to the SPM Timeout Event description:

Additional Info: id xxxxx error: yyyy

Where:

xxxx will be the “Destination ID” attribute value for the SPM Test model

yyyy will be the error code returned from the MIB for this SPM Test

 

Turn OFF debugging:

To turn off timeout event debugging, use the following CLI command:

./update action=0x456000f mh=<RTM_Test Model_Handle>

 

How to know what a SPM Test timeout error code means:

Checking the sniffer trace we can determinate the OIDs returning the error code and the description for that error, then using Spectrum MIB Tools we can determinate the name for that OIDs and the valid values to be returned.

Note: Please check “How SPM works” section (step 5 and 6)

To make easy the understanding try to figure out the following example for a Cisco SPM Test HTTP Timeout.

 

1)      The SPM Test shows has a timeout status ( Example Destination ID = 612)

 

2)      The debug for the SPM Test timeout event shows us an error code 1-404 for the Destination ID 612

 

3)      Looking into the sniffer trace, we can see that the OIDs returning these values for the SPM Test Destination ID 612 are:

Examples:

1.3.6.1.4.1.9.9.42.1.5.1.1.6 with an Integer value of 1

1.3.6.1.4.1.9.9.42.1.5.1.1.7 with an OcteString value of  343034 (decimal 404)

 

 

4)      Using Spectrum MIB tools we can see that these OIDS are:

Examples:

1.3.6.1.4.1.9.9.42.1.5.1.1.6 is rttMonLatestHTTPOperSense

1.3.6.1.4.1.9.9.42.1.5.1.1.7 is rttMonLatestHTTPErrorSenseDescription

 

 

 

5)      Then we can check the specific information for these OIDs

 

6)      Now we can determinate that error code 1 means OK