<?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: ASDM Update configuration Screen in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asdm-update-configuration-screen/m-p/1264909#M840184</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, thank you for chewing my a** for asking the question with out answering it.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I understand that the ASDM is capable of doing (configwise) almost everything the CLI can.  Not the question.  The question was what do these specific commands, issued by the ASDM upon initial start up of the ASDM, do.  To clarify further, these are the actual commands:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.192 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.0 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.0.0 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 management&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm group NNNNN-dev-net NNNNN-dev&lt;/P&gt;&lt;P&gt;asdm group AAAAAAAAA-net outside&lt;/P&gt;&lt;P&gt;asdm group MMMM-field outside&lt;/P&gt;&lt;P&gt;asdm group BBBB-farm outside&lt;/P&gt;&lt;P&gt;asdm group PPPPNET outside&lt;/P&gt;&lt;P&gt;asdm group ZZZ-net outside&lt;/P&gt;&lt;P&gt;asdm group NNNN-admin outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where xxx.xxx.xxx.xxx = a specific IP; NNNN, MMMM, BBBB, PPPP, and ZZZ = name of group&lt;/P&gt;&lt;P&gt;The IOS lists the following descriptions for the "group" and "location" parameters:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;group     Associate object group names with interfaces.  Warning: This option&lt;/P&gt;&lt;P&gt;            is designed for use solely by ASDM.  Do not manually configure this&lt;/P&gt;&lt;P&gt;            option.&lt;/P&gt;&lt;P&gt;	WORD  Specify name of an object group &lt;REAL_GROUP_NAME&gt; that contains &lt;/REAL_GROUP_NAME&gt;&lt;/P&gt;&lt;P&gt;        	real IP addresses or &lt;/P&gt;&lt;P&gt;        	name of an object group &lt;REF_GROUP_NAME&gt; which contains (NATed) IP&lt;/REF_GROUP_NAME&gt;&lt;/P&gt;&lt;P&gt;        	addresses of the object group specified by real_group_name, &lt;/P&gt;&lt;P&gt;        	usage: '[no] asdm group &lt;REAL_GRP_NAME&gt; &lt;ASSOCIATED_INTF&gt;', &lt;/ASSOCIATED_INTF&gt;&lt;/REAL_GRP_NAME&gt;&lt;/P&gt;&lt;P&gt;        	[no] asdm group &lt;REF_GRP_NAME&gt; &lt;REF_INTF&gt; reference &lt;REAL_GRP_NAME&gt;&lt;/REAL_GRP_NAME&gt;&lt;/REF_INTF&gt;&lt;/REF_GRP_NAME&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;location  Associate an external network object with an interface.  Warning:&lt;/P&gt;&lt;P&gt;            This option is designed for use solely by ASDM.  Do not manually&lt;/P&gt;&lt;P&gt;            configure this option.&lt;/P&gt;&lt;P&gt;	Hostname or A.B.C.D  IP address of host or network used internally by the&lt;/P&gt;&lt;P&gt;                       Device Manager to define the network topology.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Two days of searching cisco.com or other forums have not resulted in anything more specific than this.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, again I ask, will these commands cause any detrimental impact on the current function of the ASA?  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I say no.  But I need to prove that.  I'm not suggesting issuing any other commands other than those listed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 15 Jun 2009 12:22:48 GMT</pubDate>
    <dc:creator>sestonenppd</dc:creator>
    <dc:date>2009-06-15T12:22:48Z</dc:date>
    <item>
      <title>ASDM Update configuration Screen</title>
      <link>https://community.cisco.com/t5/network-security/asdm-update-configuration-screen/m-p/1264907#M840182</link>
      <description>&lt;P&gt;What is it that this exactly does and why does it do it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is ver5.0.7 used with an ASA5510 ver7.0.  The ASA was pretty much all configured before starting the ASDM.  My analyst doesn't think it is of much use but I like it.  I need to convince him otherwise and he's leary of me submitting this programming without knowing exactly what it's doing.  I think it is just for monitoring the ASA and doesn't negatively impact the cli other than to add these lines of code so that the ASDM can show what the ASA is doing.  Your thoughts?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 15:42:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-update-configuration-screen/m-p/1264907#M840182</guid>
      <dc:creator>sestonenppd</dc:creator>
      <dc:date>2019-03-11T15:42:45Z</dc:date>
    </item>
    <item>
      <title>Re: ASDM Update configuration Screen</title>
      <link>https://community.cisco.com/t5/network-security/asdm-update-configuration-screen/m-p/1264908#M840183</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Scott&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You say that: "he's leary of me submitting this programming without knowing exactly what it's doing." and I say "right on".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You have a good point that the ASDM has a useful function in monitoring what is going on with the ASA. But he has an excellent point that the ASDM is also a powerful tool for making config changes. You seriously underestimate the ASDM when you say: "I think it is just for monitoring the ASA and doesn't negatively impact the cli". If you do not understand what you are doing with ASDM or if you get careless with ASDM you can do SERIOUS damage to the ASA. (note: the same point applies to what you do with CLI: if you do not understand what you are doing or if you get careless with CLI you can do SERIOUS damage to the ASA).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So bottom line: we need to understand very clearly what our tools are capable of doing - and we need to be very careful to not be careless.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rick &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 13 Jun 2009 02:03:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-update-configuration-screen/m-p/1264908#M840183</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2009-06-13T02:03:19Z</dc:date>
    </item>
    <item>
      <title>Re: ASDM Update configuration Screen</title>
      <link>https://community.cisco.com/t5/network-security/asdm-update-configuration-screen/m-p/1264909#M840184</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, thank you for chewing my a** for asking the question with out answering it.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I understand that the ASDM is capable of doing (configwise) almost everything the CLI can.  Not the question.  The question was what do these specific commands, issued by the ASDM upon initial start up of the ASDM, do.  To clarify further, these are the actual commands:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.192 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.0 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.0.0 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 management&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm location xxx.xxx.xxx.xxx 255.255.255.255 outside&lt;/P&gt;&lt;P&gt;asdm group NNNNN-dev-net NNNNN-dev&lt;/P&gt;&lt;P&gt;asdm group AAAAAAAAA-net outside&lt;/P&gt;&lt;P&gt;asdm group MMMM-field outside&lt;/P&gt;&lt;P&gt;asdm group BBBB-farm outside&lt;/P&gt;&lt;P&gt;asdm group PPPPNET outside&lt;/P&gt;&lt;P&gt;asdm group ZZZ-net outside&lt;/P&gt;&lt;P&gt;asdm group NNNN-admin outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where xxx.xxx.xxx.xxx = a specific IP; NNNN, MMMM, BBBB, PPPP, and ZZZ = name of group&lt;/P&gt;&lt;P&gt;The IOS lists the following descriptions for the "group" and "location" parameters:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;group     Associate object group names with interfaces.  Warning: This option&lt;/P&gt;&lt;P&gt;            is designed for use solely by ASDM.  Do not manually configure this&lt;/P&gt;&lt;P&gt;            option.&lt;/P&gt;&lt;P&gt;	WORD  Specify name of an object group &lt;REAL_GROUP_NAME&gt; that contains &lt;/REAL_GROUP_NAME&gt;&lt;/P&gt;&lt;P&gt;        	real IP addresses or &lt;/P&gt;&lt;P&gt;        	name of an object group &lt;REF_GROUP_NAME&gt; which contains (NATed) IP&lt;/REF_GROUP_NAME&gt;&lt;/P&gt;&lt;P&gt;        	addresses of the object group specified by real_group_name, &lt;/P&gt;&lt;P&gt;        	usage: '[no] asdm group &lt;REAL_GRP_NAME&gt; &lt;ASSOCIATED_INTF&gt;', &lt;/ASSOCIATED_INTF&gt;&lt;/REAL_GRP_NAME&gt;&lt;/P&gt;&lt;P&gt;        	[no] asdm group &lt;REF_GRP_NAME&gt; &lt;REF_INTF&gt; reference &lt;REAL_GRP_NAME&gt;&lt;/REAL_GRP_NAME&gt;&lt;/REF_INTF&gt;&lt;/REF_GRP_NAME&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;location  Associate an external network object with an interface.  Warning:&lt;/P&gt;&lt;P&gt;            This option is designed for use solely by ASDM.  Do not manually&lt;/P&gt;&lt;P&gt;            configure this option.&lt;/P&gt;&lt;P&gt;	Hostname or A.B.C.D  IP address of host or network used internally by the&lt;/P&gt;&lt;P&gt;                       Device Manager to define the network topology.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Two days of searching cisco.com or other forums have not resulted in anything more specific than this.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, again I ask, will these commands cause any detrimental impact on the current function of the ASA?  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I say no.  But I need to prove that.  I'm not suggesting issuing any other commands other than those listed.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Jun 2009 12:22:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-update-configuration-screen/m-p/1264909#M840184</guid>
      <dc:creator>sestonenppd</dc:creator>
      <dc:date>2009-06-15T12:22:48Z</dc:date>
    </item>
    <item>
      <title>Re: ASDM Update configuration Screen</title>
      <link>https://community.cisco.com/t5/network-security/asdm-update-configuration-screen/m-p/1264910#M840185</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Finally found this in a Command Reference.  Still doesn't tell me much.  If someone has amplifying data, I'd appreciate it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/security/asa/asa70/command/reference/ab.html#wp1345787" target="_blank"&gt;http://www.cisco.com/en/US/docs/security/asa/asa70/command/reference/ab.html#wp1345787&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jun 2009 11:21:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asdm-update-configuration-screen/m-p/1264910#M840185</guid>
      <dc:creator>sestonenppd</dc:creator>
      <dc:date>2009-06-24T11:21:14Z</dc:date>
    </item>
  </channel>
</rss>

