SRHIRES Collection failed

[SNPP]

Hello.
I have HP 3PAR 7400c (4 nodes) 3.3.1.410 (MU2), VSP 5.0.3.1-25112.
After install 3PAR_Physical_SP_5.0.3_MU3_SW_QR516-11061.iso on VSP have problem.

I have a task named "SRHIRES Collection" which fails each time it runs.

01.08.2018 8:49:19 MSK Created
01.08.2018 8:49:19 MSK Start user operation
01.08.2018 8:49:25 MSK Collection 10% done
01.08.2018 8:49:25 MSK Failed: Collection failed

Not sure if this system task was there before.
Thanks for help!

[Dennis Handly]

This is most likely collecting info for InfoSight.

Any errors on the array at this time?

[SNPP]

Hi, Dennis Handly
We do not use InfoSight in our environment.
The 3PAR (SP and 7400c) system has no other errors. The system is healthy.

[Dennis Handly]

> We do not use InfoSight in our environment.

It would be collected anyway?

[SNPP · Accepted solution]

I looked at the logs (sp.log) on SP and found interesting records:

2018-06-29 16:59:03.457+0300 INFO  [SPCollectInterCommCall-4388] SRHiresExec - Starting task "SRHIRES Collection"
2018-06-29 16:59:03.770+0300 INFO  [SSMC UserOperationExecutor:SRHIRES Collection] SPCollectServiceModule - :205 - Queuing scheduled srhires collection for system
2018-06-29 16:59:03.770+0300 INFO  [SSMC UserOperationExecutor:SRHIRES Collection] SPCollectRecordKeeper - :134 - Changing status of scheduled srhires collection {4975} for system from UNKNOWN to QUEUED
2018-06-29 16:59:03.770+0300 INFO  [SSMC UserOperationExecutor:SRHIRES Collection] SPCollectRecordKeeper - :143 - Overall Collection Status: 85 complete, 10 failed, 0 canceled, 1 queued, 4 inprogress, 0 unknown
2018-06-29 16:59:03.770+0300 INFO  [SSMC UserOperationExecutor:SRHIRES Collection] SPCollectServiceModule - :212 - Successfully queued scheduled srhires collection {4975} for system
2018-06-29 16:59:03.770+0300 INFO  [SPCollectExecutor] SPCollectRecordKeeper - :134 - Changing status of scheduled srhires collection {4975} for system from QUEUED to INPROGRESS
2018-06-29 16:59:04.278+0300 ERROR [SPCollectExecutor] LegacyCollection - :82 - RC: 1, STDOUT: , STDERR: WARNING: SRHIRES data collection can not be run if RDA is not used.  SRHIRES data collection is NOT being run
2018-06-29 16:59:04.278+0300 INFO  [SPCollectExecutor] SPCollectRecordKeeper - :134 - Changing status of scheduled srhires collection {4975} for system from INPROGRESS to FAILED

I logged in as user hpepartner on SP. In the settings, I changed the agent mode from SSA to RDA.

After these changes, the task was successfully executed.

07.08.2018 10:18:08 MSK Created
07.08.2018 10:18:08 MSK Start user operation
07.08.2018 10:18:12 MSK Collection 10% done
07.08.2018 10:18:12 MSK Collection 20% done
07.08.2018 10:18:12 MSK Collection 30% done
07.08.2018 10:18:12 MSK Collection 40% done
07.08.2018 10:18:12 MSK Collection 50% done
07.08.2018 10:18:12 MSK Collection 60% done
07.08.2018 10:18:12 MSK Collection 70% done
07.08.2018 10:18:12 MSK Collection 80% done
07.08.2018 10:18:12 MSK Collection 90% done
07.08.2018 10:18:12 MSK Collection 100% done
07.08.2018 10:18:12 MSK Completed

[Sanja1]

I'm having the same task error but my Transport agent is allready set to RDA. What else could it be?

I also have AgentXfer directory full. Where do I find this directory and how to empty it?

[sbhat09]

Hi Sanja1,

Is the task failed at a specific instance? or failing consequently?

Regards,

Srinivas

[Sanja1]

it's failing consequently. 

VSP version  5.0.7.0-28213

[SUBHAJIT KHANBARMAN_1]

@Sanja1 

I think you are getting "Service description" as "AgentXfer directly full".

From 3PAR Service Console you need to go right side of the page and look for Green color "Actions" . Click on it and you should see option called "Cleanup SP files". This should help.

You should also check with HPE Support if your Call home working or not. If working then files will be slowly transferred from "AgentXfer".

You can restart VSP for the time being because known issue of performance for which fix is mandatory patch 5.0.7.1-28394. You should also consider upgrading your SP OS to mandatory patch 5.0.7.1-28394 as soon as possible. That may fix all SP issues.

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

************************************************************************

[Sanja1]

@SUBHAJIT KHANBARMAN_1  you are right. i was getting these errors

I did as you recomend. now  I have 

HTTP ERROR 500

Problem accessing /servicesupport/REST/spservice/sp/properties. Reason:

    Server Error