<?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 access pix using pdm in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/access-pix-using-pdm/m-p/397666#M554616</link>
    <description>&lt;P&gt;After using pdm to access pix, there are a lot of strange commands 'pdm location x.x.x.x x.x.x.x' generated in the configuration. Can I prevent them from being generated? This makes the config a little bit messy.&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 07:45:41 GMT</pubDate>
    <dc:creator>y.lo</dc:creator>
    <dc:date>2020-02-21T07:45:41Z</dc:date>
    <item>
      <title>access pix using pdm</title>
      <link>https://community.cisco.com/t5/network-security/access-pix-using-pdm/m-p/397666#M554616</link>
      <description>&lt;P&gt;After using pdm to access pix, there are a lot of strange commands 'pdm location x.x.x.x x.x.x.x' generated in the configuration. Can I prevent them from being generated? This makes the config a little bit messy.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 07:45:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-pix-using-pdm/m-p/397666#M554616</guid>
      <dc:creator>y.lo</dc:creator>
      <dc:date>2020-02-21T07:45:41Z</dc:date>
    </item>
    <item>
      <title>Re: access pix using pdm</title>
      <link>https://community.cisco.com/t5/network-security/access-pix-using-pdm/m-p/397667#M554619</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;To answer your question on why PDM generates : "pdm location x.x.x.x x.x.x.x, here is an explanation from Cisco TAC:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A PDM location is a pure book keeping command used by PDM to build its topology database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It has nothing to do with the PIX's functionalities. In particular, it does&lt;/P&gt;&lt;P&gt;**NOT** control which host can access PDM which is a common&lt;/P&gt;&lt;P&gt;misunderstanding.&lt;/P&gt;&lt;P&gt;The control is done by the command "http &lt;IP&gt; &lt;MASK&gt; &lt;INTERFACE&gt;".&lt;/INTERFACE&gt;&lt;/MASK&gt;&lt;/IP&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Why do we need it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In PDM's world, policy (those rules) is built on top of topology.&lt;/P&gt;&lt;P&gt;Ideally user creates the topology first via the Host/Network tab, then&lt;/P&gt;&lt;P&gt;configures policy else where (like Access Rule tab). A network object&lt;/P&gt;&lt;P&gt;exists by itself, even if there is no policy configured directly on it&lt;/P&gt;&lt;P&gt;at a particular time. We use "pdm location" command to remember the&lt;/P&gt;&lt;P&gt;location of a network object.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope this helps and please rate this post if it answers your question as others might be looking for the same answer on PDM locations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jay&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Nov 2004 08:15:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-pix-using-pdm/m-p/397667#M554619</guid>
      <dc:creator>jmia</dc:creator>
      <dc:date>2004-11-22T08:15:26Z</dc:date>
    </item>
  </channel>
</rss>

