2010-09-06 03:26 AM
Hello to anybody out there,
I'm new with NetApp.
We have FAS2040 Cluster, both Components Autosupport is configured to send full report to My Autosupport.
One of the Components shows Warning: "sam.misconfig.partner" with Description: "The cluster partner for this system
is not included in this report. Verify that partner Autosupport messages are being successfully delivered to NetApp."
The related Information an Links goes back to NetApp Homepage.
I have checked My Autosupport and since 3 weeks both components are sending the report mails to NetApp.
Can anybody tell me how to clear the Warning?
Solved! SEE THE SOLUTION
2010-09-06 04:00 AM
Hi, I raised a call for this exact issue and received the following reply from NetApp support:
"Based on your description, you have no configuration issues related to the sam.misconfig.partnerNotReporting warning. It is likely BURT 414851 without a way to turn it off currently."
So it looks like a bug and is something we have to live with for the time being.
Like you I can confirm that all systems reporting this error are sending autosupport mails as expected so currently I ignore those alerts.
2010-09-06 10:55 AM
Steve is right, this issue is a bug in My AutoSupport and is tracked with BURT 414851. This would be fixed in our future releases.
My AutoSupport Team
2010-12-15 07:27 AM
I am getting this error now with a fas3140-r5, but there never was a partner head, and it has never been configured for a partner. It is on 8.0 7-mode, and all the cf options seem to be set properly.
I found a few burts, but they all reference a partner...there isn't, and never was, a partner in this case.
2010-12-16 03:51 AM
Would this warning cause a warning light on the controller itself?
I have a customer with a warning light on the controller (currently cannot get access to site) and this is the only warning i am seeing in the My Autosupport.
2010-12-16 04:33 AM
My Autosupport builds the recommendation once when the ASUP arrives, there is a chance that partner's asup is not yet processed causing this warning. This doesnt cause the controller and neither the internal PSDB recommendation thats seen in internal tool.
2010-12-16 08:25 AM
If you're taking about the system warning LED on the physical controller, that typically indicates a hardware component failure/degradation. It would not be related to this "sam.misconfig" warning in HealthCheck.
I would examine the environment, storage and EMS/messages files for evidence of a hardware problem. If it's not obvious, open up a case with NetApp Tech Support.
Message was edited by: Andris Dindzans