<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: TCP Attempt Fails in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/449332#M12729</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/131990"&gt;@PabloJ&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I think your network engineers can help a lot. If they cannot, perhaps you could hire an especialised SAS Consultant, for 1 day perhaps. Never underestimate the synergies between a SAS Consultant and your IT teams &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The reason is because I think this kind of question it can only be answered on-site and probably by more than one discipline working together.&lt;/P&gt;</description>
    <pubDate>Wed, 28 Mar 2018 14:18:08 GMT</pubDate>
    <dc:creator>JuanS_OCS</dc:creator>
    <dc:date>2018-03-28T14:18:08Z</dc:date>
    <item>
      <title>TCP Attempt Fails</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/447827#M12653</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;I have a recurrent alert showed on Environment Manager, the alert is:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;TABLE cellspacing="0" cellpadding="0" border="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;DIV class="widgetHandle"&gt;Alert Properties&lt;/DIV&gt;&lt;/TD&gt;&lt;TD&gt;&lt;IMG src="http://aesas.tesa:7080/images/spacer.gif?org.apache.catalina.filters.CSRF_NONCE=C452DF2CDCC5FCC6AD81267C4462D30E" width="1" height="1" border="0" /&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;TABLE cellspacing="0" cellpadding="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;Name:&lt;/TD&gt;&lt;TD&gt;&lt;A title="View Alert Definition..." href="http://aesas.tesa:7080/alerts/Config.do?ad=10096&amp;amp;eid=1%3A10002&amp;amp;mode=viewDefinition&amp;amp;org.apache.catalina.filters.CSRF_NONCE=C452DF2CDCC5FCC6AD81267C4462D30E" target="_blank"&gt;TCP Attempt Fails&lt;/A&gt;&lt;/TD&gt;&lt;TD&gt;Priority:&lt;/TD&gt;&lt;TD&gt;! - Low&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Resource:&lt;/TD&gt;&lt;TD&gt;xxxxx.xxxxxx&lt;/TD&gt;&lt;TD&gt;Alert Date:&lt;/TD&gt;&lt;TD&gt;22-mar-2018 16:20:00&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Description:&lt;/TD&gt;&lt;TD&gt;Attempts to Establish Connections to a TCP service. Should be close to zero.&lt;/TD&gt;&lt;TD&gt;Alert Status:&lt;/TD&gt;&lt;TD&gt;&lt;IMG src="http://aesas.tesa:7080/images/icon_available_red.gif?org.apache.catalina.filters.CSRF_NONCE=C452DF2CDCC5FCC6AD81267C4462D30E" width="12" height="12" border="0" /&gt;NOT FIXED&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;TABLE cellspacing="0" cellpadding="0" border="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;&lt;DIV class="widgetHandle"&gt;Condition Set&lt;/DIV&gt;&lt;/TD&gt;&lt;TD&gt;&lt;IMG src="http://aesas.tesa:7080/images/spacer.gif?org.apache.catalina.filters.CSRF_NONCE=C452DF2CDCC5FCC6AD81267C4462D30E" width="1" height="1" border="0" /&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;TABLE cellspacing="0" cellpadding="0" border="0"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD&gt;If Condition:&lt;/TD&gt;&lt;TD&gt;Tcp Attempt Fails per Minute &amp;gt; 20,0% of 20,4 (Baseline Value)&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Actual Value:&lt;/TD&gt;&lt;TD&gt;20,0&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;&lt;IMG src="http://aesas.tesa:7080/images/spacer.gif?org.apache.catalina.filters.CSRF_NONCE=C452DF2CDCC5FCC6AD81267C4462D30E" width="1" height="1" border="0" /&gt;&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Enable Action(s):&lt;/TD&gt;&lt;TD&gt;Each time conditions are met.&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I don´t know how to manage this alert and what is the issue but the alert is being generated every 10 minutes.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance,&lt;/P&gt;&lt;P&gt;Kind regards.&lt;/P&gt;</description>
      <pubDate>Thu, 22 Mar 2018 15:51:10 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/447827#M12653</guid>
      <dc:creator>PabloJ</dc:creator>
      <dc:date>2018-03-22T15:51:10Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Backup failed</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/447829#M12654</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/131990"&gt;@PabloJ&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;what resource is this alert set for? This would help a lot.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;With this information, I can only say that the alert is for a network attempt to see if a service is alive. As long as there are several attempts and failed, it believes one service is down. Hence, the resource that is being monitored, either is down or blocking the access to that network port number.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Since the topic is about the SAS Backup, I guess the monitored resource is the SAS Deployment Agent? SAS Deployment Backup tool requires all SAS Deployment Agents to be UP and reachable each other.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Without knowing more, this is all I can tell for now, sorry.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Mar 2018 15:38:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/447829#M12654</guid>
      <dc:creator>JuanS_OCS</dc:creator>
      <dc:date>2018-03-22T15:38:39Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Attempt Fails</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/447898#M12659</link>
      <description>&lt;P&gt;Is this on a SAS VA installation or something else? What version and maintenance release of SAS does this apply to? We have the same problem on our SAS VA servers and have a track open with SAS on this.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 22 Mar 2018 19:26:25 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/447898#M12659</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2018-03-22T19:26:25Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Attempt Fails</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/448085#M12666</link>
      <description>&lt;P&gt;thanks both for your replies. We have SAS 9.4 installed and VA 7.4 version on a Linux server. I don´t know what resource is affected by this alert I would like to know some way to detect that and then fix it but environment manager don´t give enough information.&lt;BR /&gt;&lt;BR /&gt;The alert is showed every 10 minutes.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Mar 2018 09:01:13 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/448085#M12666</guid>
      <dc:creator>PabloJ</dc:creator>
      <dc:date>2018-03-23T09:01:13Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Attempt Fails</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/448088#M12668</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/131990"&gt;@PabloJ&lt;/a&gt;,&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/13976"&gt;@SASKiwi&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;SAS Environment Manager is based on VMWare Hyperic product. As such, you will be able to find and answer a lot of questions giving a look into the product documentation pages. And the agents are based on the hyperic/sigar technology, hence those product pages can help to better understand the messages (sigar will basically do the checks with &lt;STRONG&gt;netstat&lt;/STRONG&gt;, fyi)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For this purpose:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://pubs.vmware.com/vfabric5/index.jsp#com.vmware.vfabric.hyperic.4.6/Local_Platform_Services.html" target="_blank"&gt;https://pubs.vmware.com/vfabric5/index.jsp#com.vmware.vfabric.hyperic.4.6/Local_Platform_Services.html&lt;/A&gt; which points to&lt;/P&gt;
&lt;P&gt;&lt;A href="https://pubs.vmware.com/vfabric5/index.jsp?topic=/com.vmware.vfabric.hyperic.4.6/TCP_Socket_Platform_Service.html" target="_blank"&gt;https://pubs.vmware.com/vfabric5/index.jsp?topic=/com.vmware.vfabric.hyperic.4.6/TCP_Socket_Platform_Service.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Besides this, interestingly, I think it is worth a quick view to something just unirectly related, the VMWare Gemfire product pages:&amp;nbsp;&lt;A href="https://pubs.vmware.com/vfabric5/index.jsp#com.vmware.vfabric.gemfire.6.6/managing/monitor_tune/slow_receivers_preventing_problems.html" target="_blank"&gt;https://pubs.vmware.com/vfabric5/index.jsp#com.vmware.vfabric.gemfire.6.6/managing/monitor_tune/slow_receivers_preventing_problems.html&lt;/A&gt; which talks about slow TCP/IP receivers.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Anyway, I believe it is worth a good network analysis of your servers, to check if there are TCP packages that are getting lost or simply blocked. It could be. OS commands such as &lt;STRONG&gt;tcdump or netstat&lt;/STRONG&gt;&amp;nbsp;or more advanced network tools as &lt;STRONG&gt;Wireshark&lt;/STRONG&gt; can be of great help.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Last bits, some documentation from SAS, just informative in this case:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.sas.com/rnd/emi/SASEnvMgr/EVSAF/All_Alert_Definitions.pdf" target="_blank"&gt;https://support.sas.com/rnd/emi/SASEnvMgr/EVSAF/All_Alert_Definitions.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://support.sas.com/documentation/cdl/en/evug/69029/HTML/default/viewer.htm#n0urxjgvbkxyo5n1dyp1onad56nq.htm" target="_blank"&gt;http://support.sas.com/documentation/cdl/en/evug/69029/HTML/default/viewer.htm#n0urxjgvbkxyo5n1dyp1onad56nq.htm&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 23 Mar 2018 09:31:47 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/448088#M12668</guid>
      <dc:creator>JuanS_OCS</dc:creator>
      <dc:date>2018-03-23T09:31:47Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Attempt Fails</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/448370#M12675</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/131990"&gt;@PabloJ&lt;/a&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/35204"&gt;@JuanS_OCS&lt;/a&gt;:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So far SAS Tech Support have pointed me at this SAS note which I have tried: &lt;A href="http://support.sas.com/kb/58/589.html" target="_blank"&gt;http://support.sas.com/kb/58/589.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;They have also asked me to tweak JVM heap sizes. Nothing so far has been a reliable fix. I'm also getting Garbage Collection alerts as well, although they are not as frequent as the TCP alerts.&lt;/P&gt;</description>
      <pubDate>Fri, 23 Mar 2018 23:14:16 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/448370#M12675</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2018-03-23T23:14:16Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Attempt Fails</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/448497#M12686</link>
      <description>&lt;P&gt;Hi there&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/13976"&gt;@SASKiwi&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;interesting. I feel curious. Did any of those proposed changes had any positive or negative impact on the alerts that you receive?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 25 Mar 2018 14:59:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/448497#M12686</guid>
      <dc:creator>JuanS_OCS</dc:creator>
      <dc:date>2018-03-25T14:59:40Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Attempt Fails</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/449116#M12698</link>
      <description>&lt;P&gt;Increasing heap sizes tended to increase Garbage Collection alerts but reduce TCP alerts but they still occurred frequently. So far nothing I have tried has really made a big difference.&lt;/P&gt;</description>
      <pubDate>Tue, 27 Mar 2018 19:08:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/449116#M12698</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2018-03-27T19:08:37Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Attempt Fails</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/449234#M12717</link>
      <description>&lt;P&gt;Thank you&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/13976"&gt;@SASKiwi&lt;/a&gt;,&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/131990"&gt;@PabloJ&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That is interesting. Heapsizes and GC is intended only for JVMs, although this alert in the thread is intended at a host level, not service/JVM level.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;A question: have you checked the size of the audit tables in the WIP database? Perhaps a good idea to clean/archive this data.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Mar 2018 07:20:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/449234#M12717</guid>
      <dc:creator>JuanS_OCS</dc:creator>
      <dc:date>2018-03-28T07:20:20Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Attempt Fails</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/449248#M12719</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried cleaning the audit tables but the problem persist.&lt;BR /&gt;Also tried with tcpdump and whireshark but both give a lot of information that its difficult to find the cause of the issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I opened a ticket on SAS Support but they only suggested me to ask here (in SAS Community) or/and talk with my company network systems department.&lt;BR /&gt;&lt;BR /&gt;I will keep trying to find the solution of my problem. Thanks a lot.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Mar 2018 09:17:00 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/449248#M12719</guid>
      <dc:creator>PabloJ</dc:creator>
      <dc:date>2018-03-28T09:17:00Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Attempt Fails</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/449332#M12729</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/131990"&gt;@PabloJ&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I think your network engineers can help a lot. If they cannot, perhaps you could hire an especialised SAS Consultant, for 1 day perhaps. Never underestimate the synergies between a SAS Consultant and your IT teams &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The reason is because I think this kind of question it can only be answered on-site and probably by more than one discipline working together.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Mar 2018 14:18:08 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/449332#M12729</guid>
      <dc:creator>JuanS_OCS</dc:creator>
      <dc:date>2018-03-28T14:18:08Z</dc:date>
    </item>
    <item>
      <title>Re: TCP Attempt Fails</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/449464#M12737</link>
      <description>&lt;P&gt;Archiving the audit tables had no impact on this issue.&lt;/P&gt;</description>
      <pubDate>Wed, 28 Mar 2018 18:56:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/TCP-Attempt-Fails/m-p/449464#M12737</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2018-03-28T18:56:40Z</dc:date>
    </item>
  </channel>
</rss>

