Well, I followed Netapp support's recommendation to add a static route
route add 216.240.18.16 <gatewayIP> 1
I post this followup under the category of WORKAROUND since the ASUPs are flowing now, but IMO the root cause is not determined (it should not be necessary to add this static route if the routing table is being obeyed)
More info:
Our firewall is set to LOG egress (outgoing) connections For the working node I could see the connections made from the default gateway net VIF But, on the problem node, this connection was being attempted from one of the other VIFs (not in the default gateway net)
I've asked netapp support to review the fresh ASUPs to see what they might reveal about these apparent routing issues.
thanks
On Jun 4, 2012, at 11:00 AM, Jayanathan, David wrote:
I am very interested in what you find out. I am having a similar problem with a lot of our newer systems (both 8.0.X and 8.1) not being able to post asups.
One problem that I believe was fixed on 8.1 was requiring the use of a sendmail server, as using exchangeas your mail server was not working.
Let me know what you find out! I have about two dozen new systems eagerly awaiting to send data back to NetApp :D
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Fletcher Cocquyt Sent: Monday, June 04, 2012 10:25 AM To: toasters@teaparty.net Lists Subject: AutoSupport cannot connect to url https://support.netapp.com/
One of the nodes in this cluster is not able to connect to netapp to post its ASUP since we updated to 8.1 GA 40 days ago:
AutoSupport (HA Group Notification from na04 (USER_TRIGGERED (COMPLETE:completedShelfFWupdate)) INFO) cannot connect to url https://support.netapp.com/put/AsupPut/ [na04:asup.post.retry:info]: AutoSupport message (HA Group Notification from na04 (PERFORMANCE DATA) INFO) was not posted to NetApp for host (0). The system will retry later to post the message
User triggered also fails to post to netapp.support.com (although we receive the emails internally):
Jun 4 10:20:03 [na04:asup.post.host:info]: AutoSupport (HA Group Notification from na04 (USER_TRIGGERED (testing)) INFO) cannot connect to url https://support.netapp.com/put/AsupPut
I compared
options auto output on both nodes and they are the same
DNS settings are the same - and functional
na04*> ping www.netapp.com a878.b.akamai.net is alive
Any other areas to check?
thanks
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Sounds like BURT 400290 that we hit with early 8.0.x releases, but this should have been resolved since 8.0.3 (and 8.1). Are you still seeing it on newer releases?
[sent from my mobile]
On Jun 18, 2012, at 10:50 AM, Fletcher Cocquyt fcocquyt@stanford.edu wrote:
Well, I followed Netapp support's recommendation to add a static route
route add 216.240.18.16 <gatewayIP> 1
I post this followup under the category of WORKAROUND since the ASUPs are flowing now, but IMO the root cause is not determined (it should not be necessary to add this static route if the routing table is being obeyed)
More info:
Our firewall is set to LOG egress (outgoing) connections For the working node I could see the connections made from the default gateway net VIF But, on the problem node, this connection was being attempted from one of the other VIFs (not in the default gateway net)
I've asked netapp support to review the fresh ASUPs to see what they might reveal about these apparent routing issues.
thanks
On Jun 4, 2012, at 11:00 AM, Jayanathan, David wrote:
I am very interested in what you find out. I am having a similar problem with a lot of our newer systems (both 8.0.X and 8.1) not being able to post asups.
One problem that I believe was fixed on 8.1 was requiring the use of a sendmail server, as using exchangeas your mail server was not working.
Let me know what you find out! I have about two dozen new systems eagerly awaiting to send data back to NetApp :D
-----Original Message----- From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Fletcher Cocquyt Sent: Monday, June 04, 2012 10:25 AM To: toasters@teaparty.net Lists Subject: AutoSupport cannot connect to url https://support.netapp.com/
One of the nodes in this cluster is not able to connect to netapp to post its ASUP since we updated to 8.1 GA 40 days ago:
AutoSupport (HA Group Notification from na04 (USER_TRIGGERED (COMPLETE:completedShelfFWupdate)) INFO) cannot connect to url https://support.netapp.com/put/AsupPut/ [na04:asup.post.retry:info]: AutoSupport message (HA Group Notification from na04 (PERFORMANCE DATA) INFO) was not posted to NetApp for host (0). The system will retry later to post the message
User triggered also fails to post to netapp.support.com (although we receive the emails internally):
Jun 4 10:20:03 [na04:asup.post.host:info]: AutoSupport (HA Group Notification from na04 (USER_TRIGGERED (testing)) INFO) cannot connect to url https://support.netapp.com/put/AsupPut
I compared
options auto output on both nodes and they are the same
DNS settings are the same - and functional
na04*> ping www.netapp.com a878.b.akamai.net is alive
Any other areas to check?
thanks
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
-
Fletcher Cocquyt -
Kevin Graham