<?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: ASA Failover - Hostname issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-failover-hostname-issue/m-p/4093950#M1070538</link>
    <description>&lt;P&gt;Hey;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That is normal.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The configuration, including the hostname is replicated from the Active to the secondary.&amp;nbsp; So, if your primary is hostname ASA-1, the secondary will be too.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The only way to know the role of each, would be using the prompt command (just like you are doing), but the hostname will be the same on both units. When you see it changes, it is because it did some sort of. config sync and got updated. There is no configuration meant to be done on the standby.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Mike.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 28 May 2020 22:47:00 GMT</pubDate>
    <dc:creator>Maykol Rojas</dc:creator>
    <dc:date>2020-05-28T22:47:00Z</dc:date>
    <item>
      <title>ASA Failover - Hostname issue</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-hostname-issue/m-p/4093942#M1070536</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have failover configured between two ASA 5515. I am a bit rusty with ASA..years since I played with one.&lt;/P&gt;&lt;P&gt;Anyways, failover seems to be working ok. The only problem I have is that the failover unit keeps changing the name everytime I reboot the secondary unit but I also think every time it syncs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I change the hostname to "B" on the standby unit and then after a while it changes again.&lt;/P&gt;&lt;P&gt;Is it a normal behaviour? PTOHLZFW01-A/stby/sec#&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;failover&lt;BR /&gt;failover lan unit primary&lt;BR /&gt;failover lan interface FailoverInt GigabitEthernet0/5&lt;BR /&gt;failover replication http&lt;BR /&gt;failover link FailoverInt GigabitEthernet0/5&lt;BR /&gt;failover interface ip FailoverInt 1.1.1.1 255.255.255.252 standby 1.1.1.2&lt;BR /&gt;no monitor-interface internet&lt;BR /&gt;no monitor-interface management&lt;/P&gt;&lt;P&gt;interface Management0/0&lt;BR /&gt;management-only&lt;BR /&gt;nameif management&lt;BR /&gt;security-level 100&lt;BR /&gt;ip address 10.130.28.88 255.255.255.0 standby 10.130.28.89&lt;BR /&gt;!&lt;BR /&gt;failover&lt;BR /&gt;failover lan unit secondary&lt;BR /&gt;failover lan interface FailoverInt GigabitEthernet0/5&lt;BR /&gt;failover replication http&lt;BR /&gt;failover link FailoverInt GigabitEthernet0/5&lt;BR /&gt;failover interface ip FailoverInt 1.1.1.1 255.255.255.252 standby 1.1.1.2&lt;BR /&gt;no monitor-interface internet&lt;BR /&gt;no monitor-interface management&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;interface Management0/0&lt;BR /&gt;management-only&lt;BR /&gt;nameif management&lt;BR /&gt;security-level 100&lt;BR /&gt;ip address 10.130.28.88 255.255.255.0 standby 10.130.28.89&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 28 May 2020 22:27:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-hostname-issue/m-p/4093942#M1070536</guid>
      <dc:creator>murilor</dc:creator>
      <dc:date>2020-05-28T22:27:55Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover - Hostname issue</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-hostname-issue/m-p/4093949#M1070537</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is the expected behaviour. The host name will sync but the prompt (stby in your case) will inform you of the units status.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;thanks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 May 2020 22:44:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-hostname-issue/m-p/4093949#M1070537</guid>
      <dc:creator>Aileron88</dc:creator>
      <dc:date>2020-05-28T22:44:14Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover - Hostname issue</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-hostname-issue/m-p/4093950#M1070538</link>
      <description>&lt;P&gt;Hey;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That is normal.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The configuration, including the hostname is replicated from the Active to the secondary.&amp;nbsp; So, if your primary is hostname ASA-1, the secondary will be too.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The only way to know the role of each, would be using the prompt command (just like you are doing), but the hostname will be the same on both units. When you see it changes, it is because it did some sort of. config sync and got updated. There is no configuration meant to be done on the standby.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Mike.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 May 2020 22:47:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-hostname-issue/m-p/4093950#M1070538</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2020-05-28T22:47:00Z</dc:date>
    </item>
  </channel>
</rss>

