<?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: Meaning of Data After Hostname &amp;amp; IP in FMT in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/meaning-of-data-after-hostname-amp-ip-in-fmt/m-p/5548357#M1125100</link>
    <description>&lt;P&gt;You are most welcome.&amp;nbsp; Reach back out if you could use additional assistance.&lt;/P&gt;</description>
    <pubDate>Mon, 27 Apr 2026 14:25:12 GMT</pubDate>
    <dc:creator>Jim Pilgrim</dc:creator>
    <dc:date>2026-04-27T14:25:12Z</dc:date>
    <item>
      <title>Meaning of Data After Hostname &amp; IP in FMT</title>
      <link>https://community.cisco.com/t5/network-security/meaning-of-data-after-hostname-amp-ip-in-fmt/m-p/5548338#M1125096</link>
      <description>&lt;P&gt;I'm working on migrating ASA to and FTD device that's registered on an FMC virtual appliance.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;When I go to select devices, I'm curious to know the meanings of the data that appear after the hostname and management IP such as NA and (R)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2026 13:14:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/meaning-of-data-after-hostname-amp-ip-in-fmt/m-p/5548338#M1125096</guid>
      <dc:creator>korey-bennett</dc:creator>
      <dc:date>2026-04-27T13:14:28Z</dc:date>
    </item>
    <item>
      <title>Re: Meaning of Data After Hostname &amp; IP in FMT</title>
      <link>https://community.cisco.com/t5/network-security/meaning-of-data-after-hostname-amp-ip-in-fmt/m-p/5548350#M1125097</link>
      <description>&lt;P class=""&gt;The letters after the hostname and management IP indicate the &lt;STRONG&gt;firewall operating mode&lt;/STRONG&gt; of each device registered to FMC:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;STRONG&gt;(R)&lt;/STRONG&gt; — Routed mode&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;(T)&lt;/STRONG&gt; — Transparent mode&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;NA&lt;/STRONG&gt; — Not Applicable. The migration tool couldn't determine a single mode for that device. Common reasons:&lt;UL&gt;&lt;LI&gt;It's a multi-instance / container parent (the chassis itself, where each individual instance has its own mode)&lt;/LI&gt;&lt;LI&gt;It's the secondary member of an HA pair (the mode is reported against the primary)&lt;/LI&gt;&lt;LI&gt;It's a cluster member (the mode is reported against the cluster control unit)&lt;/LI&gt;&lt;LI&gt;The device is registered but doesn't have a firewall mode configured yet&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P class=""&gt;Why it matters for your ASA → FTD migration: an ASA in Routed mode can only be migrated cleanly to an FTD target in Routed mode, and the same for Transparent. The tool surfaces the mode right here in the device-selection screen so you don't pick a target that won't accept the source ASA's configuration.&lt;/P&gt;&lt;P class=""&gt;In short: (R) = Routed, (T) = Transparent, NA = mode couldn't be determined.&lt;BR /&gt;&lt;BR /&gt;If your intended target is showing NA and you expected it to be Routed or Transparent, go to &lt;STRONG&gt;Devices → Device Management&lt;/STRONG&gt; in FMC, confirm the firewall mode is set on the device (or on the individual container instance, if it's multi-instance), then re-run the device fetch in the migration tool.&lt;BR /&gt;&lt;BR /&gt;Hope this helps — Jim&lt;/P&gt;&lt;P class=""&gt;If this answered your question, please click &lt;STRONG&gt;Accept as Solution&lt;/STRONG&gt; so other engineers running into the same issue can find the fix quickly. Happy to help further if anything else comes up.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2026 14:05:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/meaning-of-data-after-hostname-amp-ip-in-fmt/m-p/5548350#M1125097</guid>
      <dc:creator>Jim Pilgrim</dc:creator>
      <dc:date>2026-04-27T14:05:00Z</dc:date>
    </item>
    <item>
      <title>Re: Meaning of Data After Hostname &amp; IP in FMT</title>
      <link>https://community.cisco.com/t5/network-security/meaning-of-data-after-hostname-amp-ip-in-fmt/m-p/5548355#M1125099</link>
      <description>&lt;P&gt;That makes sense. I confirmed the ASA was in Router mode with 'show firewall' and the target FTD shows as Routed in the FMC UI, when I click the pencil icon of the target, go to the Device tab and check the "Mode" field in the General tile.&lt;BR /&gt;&lt;BR /&gt;Interesting that the target FTD shows as both NA and (R). Target FTD is not part of an HA pair or cluster. I don't believe it's a container parent, it's a&amp;nbsp;CSF-1210CE.&lt;BR /&gt;&lt;BR /&gt;Thanks for the great answer.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2026 14:23:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/meaning-of-data-after-hostname-amp-ip-in-fmt/m-p/5548355#M1125099</guid>
      <dc:creator>korey-bennett</dc:creator>
      <dc:date>2026-04-27T14:23:42Z</dc:date>
    </item>
    <item>
      <title>Re: Meaning of Data After Hostname &amp; IP in FMT</title>
      <link>https://community.cisco.com/t5/network-security/meaning-of-data-after-hostname-amp-ip-in-fmt/m-p/5548357#M1125100</link>
      <description>&lt;P&gt;You are most welcome.&amp;nbsp; Reach back out if you could use additional assistance.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Apr 2026 14:25:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/meaning-of-data-after-hostname-amp-ip-in-fmt/m-p/5548357#M1125100</guid>
      <dc:creator>Jim Pilgrim</dc:creator>
      <dc:date>2026-04-27T14:25:12Z</dc:date>
    </item>
  </channel>
</rss>

