3.2.1, SR DB not complete, wait for srsampler to run etc
Posted: Wed Oct 15, 2014 3:42 pm
Hi,
Thought that we successfully completed upgrade to 3.2.1 of our 2nd 7400 array yesterday.
But during upgrade communication between ServiceProcessor and array aborted or timed out and we had to reinitiate the upgrade.
After 2nd run things looked to complete successfully.
Today we faced issues with array based System Reporter DB, "showsr" returns expected output but any "srstat*" commands terminates with message "SR DB not complete, wait for srsampler to run"
What process/deamon have failed? are there any command to trigger restart of srsampler?
We also see excessive retransmits on an RCFC link which "overloads" almost evry 6hours causing RCFC port to restart.
Things I also noticed as an difference, there was an "admithw" command initiated in the end of upgrade on our first array, this step didn't execute on our second array.
None of the above deviations was seen running on 3.1.3 MU1 on both arrays.
Any ideas?
Kind Regards,
Peter
Thought that we successfully completed upgrade to 3.2.1 of our 2nd 7400 array yesterday.
But during upgrade communication between ServiceProcessor and array aborted or timed out and we had to reinitiate the upgrade.
After 2nd run things looked to complete successfully.
Today we faced issues with array based System Reporter DB, "showsr" returns expected output but any "srstat*" commands terminates with message "SR DB not complete, wait for srsampler to run"
What process/deamon have failed? are there any command to trigger restart of srsampler?
We also see excessive retransmits on an RCFC link which "overloads" almost evry 6hours causing RCFC port to restart.
Things I also noticed as an difference, there was an "admithw" command initiated in the end of upgrade on our first array, this step didn't execute on our second array.
None of the above deviations was seen running on 3.1.3 MU1 on both arrays.
Any ideas?
Kind Regards,
Peter