<?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 Thanks Dear...  in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/asa-5520-duplicate-object-network-with-same-ip/m-p/2605247#M75675</link>
    <description>&lt;P&gt;Thanks Dear...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 09 Dec 2014 07:10:48 GMT</pubDate>
    <dc:creator>Anand Sharma</dc:creator>
    <dc:date>2014-12-09T07:10:48Z</dc:date>
    <item>
      <title>ASA 5520-Duplicate Object-Network with same ip</title>
      <link>https://community.cisco.com/t5/network-access-control/asa-5520-duplicate-object-network-with-same-ip/m-p/2605245#M75666</link>
      <description>&lt;P&gt;Hello Friends,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;we 5 people are working in a team,some of working with CLI and some asdm,&lt;/P&gt;&lt;P&gt;now we seen with the same IP other objects network are created ,&lt;/P&gt;&lt;P&gt;now some time its difficult to troubleshoot or monitoring&lt;/P&gt;&lt;P&gt;can anybody help me to provide a solution so nobody can create any object with the same IP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 05:14:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/asa-5520-duplicate-object-network-with-same-ip/m-p/2605245#M75666</guid>
      <dc:creator>Anand Sharma</dc:creator>
      <dc:date>2019-03-11T05:14:58Z</dc:date>
    </item>
    <item>
      <title>You could do it with a</title>
      <link>https://community.cisco.com/t5/network-access-control/asa-5520-duplicate-object-network-with-same-ip/m-p/2605246#M75673</link>
      <description>&lt;P&gt;You could do it with a technical solution like EEM where you parse syslog to see if someone configures an object with an IP and then act on that. But WWM needs 9.2 which is not available for the 5520.&lt;/P&gt;&lt;P&gt;So you can solve the problem with an organisational solution. Implement a naming standard how objects have to be named, make sure that everyone looks at he objects before creating new ones and most important, you have to talk to each other who will configure what.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 08 Dec 2014 09:22:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/asa-5520-duplicate-object-network-with-same-ip/m-p/2605246#M75673</guid>
      <dc:creator>Karsten Iwen</dc:creator>
      <dc:date>2014-12-08T09:22:18Z</dc:date>
    </item>
    <item>
      <title>Thanks Dear... </title>
      <link>https://community.cisco.com/t5/network-access-control/asa-5520-duplicate-object-network-with-same-ip/m-p/2605247#M75675</link>
      <description>&lt;P&gt;Thanks Dear...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 09 Dec 2014 07:10:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/asa-5520-duplicate-object-network-with-same-ip/m-p/2605247#M75675</guid>
      <dc:creator>Anand Sharma</dc:creator>
      <dc:date>2014-12-09T07:10:48Z</dc:date>
    </item>
  </channel>
</rss>

