<?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 IPSec Does not respond in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ipsec-does-not-respond/m-p/2707849#M757129</link>
    <description>While the system is running, suddenly IPSec stops responding. So from one system we can not telnet to another system on IPSec encrypted port. IPSec audit log normally drops errors like! &lt;BR /&gt;Msg: 4  From: IKMPD  Lvl: ERROR  Date: Mon Jan 21 16:59:07 2002&lt;BR /&gt;   Event: Error processing SA   payload&lt;BR /&gt;Msg: 1  From: IKMPD  Lvl: ERROR  Date: Mon Jan 21 16:59:07 2002&lt;BR /&gt;   Event: IPSEC_RULE request timeout, seq 202708&lt;BR /&gt;.......&lt;BR /&gt;.......&lt;BR /&gt;&lt;BR /&gt;Is there any document where we can refer the meaning of these errors.</description>
    <pubDate>Mon, 22 Apr 2002 05:24:41 GMT</pubDate>
    <dc:creator>Srinivas_3</dc:creator>
    <dc:date>2002-04-22T05:24:41Z</dc:date>
    <item>
      <title>IPSec Does not respond</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ipsec-does-not-respond/m-p/2707849#M757129</link>
      <description>While the system is running, suddenly IPSec stops responding. So from one system we can not telnet to another system on IPSec encrypted port. IPSec audit log normally drops errors like! &lt;BR /&gt;Msg: 4  From: IKMPD  Lvl: ERROR  Date: Mon Jan 21 16:59:07 2002&lt;BR /&gt;   Event: Error processing SA   payload&lt;BR /&gt;Msg: 1  From: IKMPD  Lvl: ERROR  Date: Mon Jan 21 16:59:07 2002&lt;BR /&gt;   Event: IPSEC_RULE request timeout, seq 202708&lt;BR /&gt;.......&lt;BR /&gt;.......&lt;BR /&gt;&lt;BR /&gt;Is there any document where we can refer the meaning of these errors.</description>
      <pubDate>Mon, 22 Apr 2002 05:24:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ipsec-does-not-respond/m-p/2707849#M757129</guid>
      <dc:creator>Srinivas_3</dc:creator>
      <dc:date>2002-04-22T05:24:41Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec Does not respond</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ipsec-does-not-respond/m-p/2707850#M757130</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;The negotiation and key exchange over IKE SA is via the ISAKMP protocol at service port 500. This is always performed before the IPSEC SA can be created and used. &lt;BR /&gt;&lt;BR /&gt;From the error messages you got, I would guess that this IKE SA negotiation probably failed.&lt;BR /&gt;&lt;BR /&gt;Hope this helps. Regards.&lt;BR /&gt;&lt;BR /&gt;Steven Sim Kok Leong</description>
      <pubDate>Mon, 22 Apr 2002 05:37:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ipsec-does-not-respond/m-p/2707850#M757130</guid>
      <dc:creator>Steven Sim Kok Leong</dc:creator>
      <dc:date>2002-04-22T05:37:20Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec Does not respond</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ipsec-does-not-respond/m-p/2707851#M757131</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Here is some documentation !&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/internet/index.html#IPSec/9000" target="_blank"&gt;http://docs.hp.com/hpux/internet/index.html#IPSec/9000&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://docs.hp.com/hpux/pdf/J4255-90011.pdf" target="_blank"&gt;http://docs.hp.com/hpux/pdf/J4255-90011.pdf&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;C.</description>
      <pubDate>Mon, 22 Apr 2002 05:50:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ipsec-does-not-respond/m-p/2707851#M757131</guid>
      <dc:creator>Clemens van Everdingen</dc:creator>
      <dc:date>2002-04-22T05:50:04Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec Does not respond</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ipsec-does-not-respond/m-p/2707852#M757132</link>
      <description>What could be the reasons for the key negotiations to fail?</description>
      <pubDate>Mon, 22 Apr 2002 05:50:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ipsec-does-not-respond/m-p/2707852#M757132</guid>
      <dc:creator>Srinivas_3</dc:creator>
      <dc:date>2002-04-22T05:50:05Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec Does not respond</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ipsec-does-not-respond/m-p/2707853#M757133</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Did you use the ipsec_admin ???status&lt;BR /&gt;command to see if all processes are running ?&lt;BR /&gt;&lt;BR /&gt;Should look like this:&lt;BR /&gt;&lt;BR /&gt;# ipsec_admin - status&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;----------------- IPSec Status Report -----------------&lt;BR /&gt;&lt;BR /&gt;        secauditd program: Running and responding&lt;BR /&gt;&lt;BR /&gt;        secpolicyd program: Running and responding&lt;BR /&gt;&lt;BR /&gt;        ikmpd program: Running and responding&lt;BR /&gt;&lt;BR /&gt;        IPSec kernel: Up&lt;BR /&gt;&lt;BR /&gt;        IPSec Audit level: Error&lt;BR /&gt;&lt;BR /&gt;        IPSec Audit file: /var/adm/ipsec/auditTue-Jul-17-11-28-29-2001.log&lt;BR /&gt;&lt;BR /&gt;        Max Audit file size: 100 KBytes&lt;BR /&gt;&lt;BR /&gt;        IPSec Policy file: /var/adm/ipsec/policies.txt&lt;BR /&gt;&lt;BR /&gt;        Level 4 tracing: None&lt;BR /&gt;&lt;BR /&gt;-------------- End of IPSec Status Report -------------&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;Possible a restart will solve the issue.&lt;BR /&gt;&lt;BR /&gt;C.</description>
      <pubDate>Mon, 22 Apr 2002 05:53:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ipsec-does-not-respond/m-p/2707853#M757133</guid>
      <dc:creator>Clemens van Everdingen</dc:creator>
      <dc:date>2002-04-22T05:53:38Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec Does not respond</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ipsec-does-not-respond/m-p/2707854#M757134</link>
      <description>Restarting IPSec and flushing the SA and plicies etc.. are tried, but as it is on production systems, the web application keep failing because IPSec configured ports are not responding. So I want to know why this error comes frequently and what is the remedy.</description>
      <pubDate>Mon, 22 Apr 2002 06:03:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ipsec-does-not-respond/m-p/2707854#M757134</guid>
      <dc:creator>Srinivas_3</dc:creator>
      <dc:date>2002-04-22T06:03:17Z</dc:date>
    </item>
    <item>
      <title>Re: IPSec Does not respond</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ipsec-does-not-respond/m-p/2707855#M757135</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;You could turn tracing on to see what happens.&lt;BR /&gt;&lt;BR /&gt;-----------------------------------------------&lt;BR /&gt;IPSec tracing&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;If the problem may be caused by the transport or application layer, enable layer four &lt;BR /&gt;&lt;BR /&gt;tracing, recreate the problem, then disable tracing.  Trace output will be sent to &lt;BR /&gt;&lt;BR /&gt;/var/adm/ipsec/nettl.TRC0.  You may trace TCP, UDP, IGMP or all.  Typical netfmt&lt;BR /&gt;&lt;BR /&gt;options can be used to format the output.&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;# ipsec_admin -traceon all&lt;BR /&gt;&lt;BR /&gt;IPSEC_ADMIN: Please enter the IPSec password: ***************&lt;BR /&gt;&lt;BR /&gt;IPSEC_ADMIN: WARNING-Enabling any Level 4 tracing (TCP, UDP, or IGMP) started&lt;BR /&gt;&lt;BR /&gt;IPSEC_ADMIN: WARNING-by ipsec_admin.  Ignore following nettl msg(s) if any.&lt;BR /&gt;&lt;BR /&gt;IPSEC_ADMIN: Level 4 tracing successfully enabled for TCP, UDP, and IGMP.&lt;BR /&gt;&lt;BR /&gt; &lt;BR /&gt;&lt;BR /&gt;# ipsec_admin -tf all&lt;BR /&gt;&lt;BR /&gt;IPSEC_ADMIN: Please enter the IPSec password: ***************&lt;BR /&gt;&lt;BR /&gt;IPSEC_ADMIN: WARNING-Disabling any Level 4 tracing (TCP, UDP, or IGMP) started&lt;BR /&gt;&lt;BR /&gt;IPSEC_ADMIN: WARNING-by ipsec_admin.  Ignore following nettl msg(s) if any.&lt;BR /&gt;&lt;BR /&gt;IPSEC_ADMIN: Level 4 tracing successfully disabled for TCP, UDP, and IGMP.&lt;BR /&gt;&lt;BR /&gt;C.&lt;BR /&gt;</description>
      <pubDate>Mon, 22 Apr 2002 06:25:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ipsec-does-not-respond/m-p/2707855#M757135</guid>
      <dc:creator>Clemens van Everdingen</dc:creator>
      <dc:date>2002-04-22T06:25:44Z</dc:date>
    </item>
  </channel>
</rss>

