<?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: expect hash payload, got payload#: 11 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/expect-hash-payload-got-payload-11/m-p/760035#M980308</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; it seems that phase 1 negotiation is failing. &lt;/P&gt;&lt;P&gt;The logs show that after the PIX sends out the first MM isakmp packet, it never sees anything back from the remote peer. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Possible reasons:&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;1. make sure the isakmp policy is matching the other side.&lt;/P&gt;&lt;P&gt;2. make sure the preshared key is set correctly.&lt;/P&gt;&lt;P&gt;3. make sure there is no device in the middle blocking UDP/500 packets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 25 May 2007 20:55:09 GMT</pubDate>
    <dc:creator>mchin345</dc:creator>
    <dc:date>2007-05-25T20:55:09Z</dc:date>
    <item>
      <title>expect hash payload, got payload#: 11</title>
      <link>https://community.cisco.com/t5/network-security/expect-hash-payload-got-payload-11/m-p/760034#M980306</link>
      <description>&lt;P&gt;I have numerous IPSec VPNs via my PIX Version 6.3(5)working.&lt;/P&gt;&lt;P&gt;A new tunnel is being set up and the connection is not being made.&lt;/P&gt;&lt;P&gt;What is a payload # 11 ?&lt;/P&gt;&lt;P&gt;The pertinent debug messages are&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ISAKMP (0): beginning Main Mode exchange&lt;/P&gt;&lt;P&gt;throw: mess_id 0x0&lt;/P&gt;&lt;P&gt;send_response:&lt;/P&gt;&lt;P&gt;isakmp_send: ip xx.xx.xx.xx, port 500&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ISAKMP msg received&lt;/P&gt;&lt;P&gt;crypto_isakmp_process_block:src:xx.xx.xx.xx, dest:yy.yy.yy.yy spt:500 dpt:500&lt;/P&gt;&lt;P&gt;gen_cookie:&lt;/P&gt;&lt;P&gt;fill_sa_key:isadb_search returned sa = 0x38045ac&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;validate_payload: len 212&lt;/P&gt;&lt;P&gt;valid_payload:&lt;/P&gt;&lt;P&gt;ISAKMP_INFO exchange&lt;/P&gt;&lt;P&gt;process_isakmp_info:&lt;/P&gt;&lt;P&gt;expect hash payload, got payload#: 11&lt;/P&gt;&lt;P&gt;error - IKMP_MODE_FAILURE&lt;/P&gt;&lt;P&gt;return status is IKMP_NO_ERR_NO_TRANS             &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;Jacob&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:17:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/expect-hash-payload-got-payload-11/m-p/760034#M980306</guid>
      <dc:creator>jvanwa1</dc:creator>
      <dc:date>2019-03-11T10:17:49Z</dc:date>
    </item>
    <item>
      <title>Re: expect hash payload, got payload#: 11</title>
      <link>https://community.cisco.com/t5/network-security/expect-hash-payload-got-payload-11/m-p/760035#M980308</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; it seems that phase 1 negotiation is failing. &lt;/P&gt;&lt;P&gt;The logs show that after the PIX sends out the first MM isakmp packet, it never sees anything back from the remote peer. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Possible reasons:&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;1. make sure the isakmp policy is matching the other side.&lt;/P&gt;&lt;P&gt;2. make sure the preshared key is set correctly.&lt;/P&gt;&lt;P&gt;3. make sure there is no device in the middle blocking UDP/500 packets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 May 2007 20:55:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/expect-hash-payload-got-payload-11/m-p/760035#M980308</guid>
      <dc:creator>mchin345</dc:creator>
      <dc:date>2007-05-25T20:55:09Z</dc:date>
    </item>
    <item>
      <title>Re: expect hash payload, got payload#: 11</title>
      <link>https://community.cisco.com/t5/network-security/expect-hash-payload-got-payload-11/m-p/760036#M980309</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;I will check the settings on the other end.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jacob&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 May 2007 21:05:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/expect-hash-payload-got-payload-11/m-p/760036#M980309</guid>
      <dc:creator>jvanwa1</dc:creator>
      <dc:date>2007-05-25T21:05:06Z</dc:date>
    </item>
    <item>
      <title>Re: expect hash payload, got payload#: 11</title>
      <link>https://community.cisco.com/t5/network-security/expect-hash-payload-got-payload-11/m-p/760037#M980311</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;also beside as suggested check the acl's on both FW, both side acl's should match in a reverse order form. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH, please rate it &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 26 May 2007 12:13:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/expect-hash-payload-got-payload-11/m-p/760037#M980311</guid>
      <dc:creator>zulqurnain</dc:creator>
      <dc:date>2007-05-26T12:13:03Z</dc:date>
    </item>
  </channel>
</rss>

