<?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: Device Names in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/device-names/m-p/199464#M1060919</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Our SE said that as well, but I applied that patch (and the associated CMF patch) yesterday.  I wiped the database and ran the discovery but it didn't help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll check and see if the patch went in,. I'll check the "About", it displays the versions and patches applied.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 26 Feb 2003 00:59:37 GMT</pubDate>
    <dc:creator>dcwalker</dc:creator>
    <dc:date>2003-02-26T00:59:37Z</dc:date>
    <item>
      <title>Device Names</title>
      <link>https://community.cisco.com/t5/network-security/device-names/m-p/199462#M1060917</link>
      <description>&lt;P&gt;I have upgraded to LMS 2.1 (CM 3.2 , RME 3.4) and found it won't recognise the SysName (Bug CSCdw66262 as described in the release notes (known problems)).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It does store the sysname because it can be displayed in the topology map as a label.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To work around this problem I need to export the IP address and sysname.  I will store that in the servers hosts file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Device Attributes in the topology map doesn't display the sysname.  The export from the file menu doesn't show the sysname either.  CWEXPORT works on the RME database and I want to get the CM database instead (some devices aren't in RME).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anyone got any ideas?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 06:35:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/device-names/m-p/199462#M1060917</guid>
      <dc:creator>dcwalker</dc:creator>
      <dc:date>2020-02-21T06:35:04Z</dc:date>
    </item>
    <item>
      <title>Re: Device Names</title>
      <link>https://community.cisco.com/t5/network-security/device-names/m-p/199463#M1060918</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;CSCdw66262 is fixed in the latest CM 3.2 IDU v3-0 as listed in CM32.IDU.v3-0.win.readme.pdf (page 13, Table 3). You can get it from: &lt;A class="jive-link-custom" href="http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-campus" target="_blank"&gt;http://www.cisco.com/cgi-bin/tablebuild.pl/cw2000-campus&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also get the Beta version of CM 3.3 from the above URL as well, if you want to play with it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Feb 2003 00:48:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/device-names/m-p/199463#M1060918</guid>
      <dc:creator>rmushtaq</dc:creator>
      <dc:date>2003-02-26T00:48:34Z</dc:date>
    </item>
    <item>
      <title>Re: Device Names</title>
      <link>https://community.cisco.com/t5/network-security/device-names/m-p/199464#M1060919</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Our SE said that as well, but I applied that patch (and the associated CMF patch) yesterday.  I wiped the database and ran the discovery but it didn't help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll check and see if the patch went in,. I'll check the "About", it displays the versions and patches applied.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Feb 2003 00:59:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/device-names/m-p/199464#M1060919</guid>
      <dc:creator>dcwalker</dc:creator>
      <dc:date>2003-02-26T00:59:37Z</dc:date>
    </item>
  </channel>
</rss>

