<?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: FirePower Chassis Name Change - Warning! in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/firepower-chassis-name-change-warning/m-p/3379113#M1065043</link>
    <description>&lt;P&gt;We have Firepower 2100 and this link (&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/firepower/2100/troubleshoot_fxos/b_2100_CLI_Troubleshoot.pdf" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/firepower/2100/troubleshoot_fxos/b_2100_CLI_Troubleshoot.pdf&lt;/A&gt;) says that configuration changes via CLI are not possible. Every change have to be confirmed by command "commit-buffer". if I set the name by "set name XXXXX", our 2100 response is "Error: Changes not allowed. use: 'connect ftd' to make changes.".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So, setting SNMP name is not possible. SNMP get commands returns name "octeon". I found that this is a bug - &lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvi56715/?rfs=iqvred" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvi56715/?rfs=iqvred&lt;/A&gt;. This buf has been fixed but we have not upgraded yet so I cannot confirm if it really works or not.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 07 May 2018 07:14:07 GMT</pubDate>
    <dc:creator>martin5641289</dc:creator>
    <dc:date>2018-05-07T07:14:07Z</dc:date>
    <item>
      <title>FirePower Chassis Name Change - Warning!</title>
      <link>https://community.cisco.com/t5/network-security/firepower-chassis-name-change-warning/m-p/3209772#M1065042</link>
      <description>&lt;P&gt;I would like to change the hostname of two FirePower 4100 systems which are in HA active/passive mode between the two systems on the installed ASA 9.7 code.&lt;/P&gt;
&lt;P&gt;The ASA hostname was changed just fine.&lt;/P&gt;
&lt;P&gt;When I try to change the FirePower chassis hostname via FXOS, I get an error that makes me nervous.&amp;nbsp; Can anyone confirm I can change the FirePower chassis&amp;nbsp;hostname without negatively impacting this production environment?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;See warning below.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Firepower-chassis-A# scope system&lt;/P&gt;
&lt;P&gt;Firepower-chassis-A /system # set name New-name&lt;/P&gt;
&lt;P&gt;Warning: System name modification changes FC zone name and redeploys them non-disruptively&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I have searched for this and in Cisco documentation, it states the warning will come up but no response on if it will affect connectivity.&amp;nbsp; In the forums, no one states that there is a negative impact, but that's only by omission - no one has specifically stated it does or does not affect the environment.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 14:37:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-chassis-name-change-warning/m-p/3209772#M1065042</guid>
      <dc:creator>davidhvoss</dc:creator>
      <dc:date>2020-02-21T14:37:44Z</dc:date>
    </item>
    <item>
      <title>Re: FirePower Chassis Name Change - Warning!</title>
      <link>https://community.cisco.com/t5/network-security/firepower-chassis-name-change-warning/m-p/3379113#M1065043</link>
      <description>&lt;P&gt;We have Firepower 2100 and this link (&lt;A href="https://www.cisco.com/c/en/us/td/docs/security/firepower/2100/troubleshoot_fxos/b_2100_CLI_Troubleshoot.pdf" target="_blank"&gt;https://www.cisco.com/c/en/us/td/docs/security/firepower/2100/troubleshoot_fxos/b_2100_CLI_Troubleshoot.pdf&lt;/A&gt;) says that configuration changes via CLI are not possible. Every change have to be confirmed by command "commit-buffer". if I set the name by "set name XXXXX", our 2100 response is "Error: Changes not allowed. use: 'connect ftd' to make changes.".&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So, setting SNMP name is not possible. SNMP get commands returns name "octeon". I found that this is a bug - &lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvi56715/?rfs=iqvred" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvi56715/?rfs=iqvred&lt;/A&gt;. This buf has been fixed but we have not upgraded yet so I cannot confirm if it really works or not.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 07 May 2018 07:14:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-chassis-name-change-warning/m-p/3379113#M1065043</guid>
      <dc:creator>martin5641289</dc:creator>
      <dc:date>2018-05-07T07:14:07Z</dc:date>
    </item>
    <item>
      <title>Re: FirePower Chassis Name Change - Warning!</title>
      <link>https://community.cisco.com/t5/network-security/firepower-chassis-name-change-warning/m-p/3700985#M1065044</link>
      <description>&lt;P&gt;This bug - CSCvi56715 - is still opened. It has severity 4 minor so Cisco works for fixing more important issues. Last update is from Aug 26,2018.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvi56715/?rfs=iqvred" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvi56715/?rfs=iqvred&lt;/A&gt;. I suppose it would be fixed in two or three years because Firepower has many other bugs. I could not recommned to buy Cisco Firepower because it is very bugged firewall and fixing known issues has not been finished yet and it took more than a year and the firewall is still bugged.&lt;/P&gt;
&lt;DIV class="bugTitle"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;DIV class="bugTitle"&gt;SNMP polling of FTD on Firepower 2100 Series firewalls shows "octeon" for the "sysName" OID&lt;/DIV&gt;
&lt;DIV class="bugId"&gt;CSCvi56715&lt;/DIV&gt;
&lt;DIV class="sectionHeader bugDescription"&gt;
&lt;DIV class="title"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;DIV class="bugDescriptionContent"&gt;
&lt;DIV style="display: table; margin-top: -13px;"&gt;
&lt;DIV class="releaseNoteText"&gt;&lt;STRONG&gt;Symptom:&lt;/STRONG&gt;&lt;BR /&gt;The SNMP polling of OID .1.3.6.1.2.1.1.5 ("sysName") against the Firepower Threat Defense application returns "octeon" instead of an expected host name.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Conditions:&lt;/STRONG&gt;&lt;BR /&gt;Firepower Threat Defense running on a Firepower 2100 Series firewall. SNMP polling (any SNMP version) configured in the platform settings policy deployed to the firewall.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Workaround:&lt;/STRONG&gt;&lt;BR /&gt;None.&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Wed, 05 Sep 2018 07:41:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-chassis-name-change-warning/m-p/3700985#M1065044</guid>
      <dc:creator>martin5641289</dc:creator>
      <dc:date>2018-09-05T07:41:19Z</dc:date>
    </item>
    <item>
      <title>Re: FirePower Chassis Name Change - Warning!</title>
      <link>https://community.cisco.com/t5/network-security/firepower-chassis-name-change-warning/m-p/5353315#M1123793</link>
      <description>&lt;P&gt;You need to do this in the connect ftd area when its managed by&amp;nbsp; FMC:&lt;/P&gt;
&lt;P&gt;connect ftd&lt;/P&gt;
&lt;P&gt;config network hostname &amp;lt;desired hostname&amp;gt;&lt;/P&gt;
&lt;P&gt;exit&lt;/P&gt;
&lt;P&gt;*** observe the correct hostname in NXOS&lt;/P&gt;
&lt;P&gt;Good Luck!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Warner&lt;/P&gt;</description>
      <pubDate>Mon, 08 Dec 2025 20:23:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/firepower-chassis-name-change-warning/m-p/5353315#M1123793</guid>
      <dc:creator>wdejulio312</dc:creator>
      <dc:date>2025-12-08T20:23:12Z</dc:date>
    </item>
  </channel>
</rss>

