<?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 Changing peer IP address ? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Changing-peer-IP-address/m-p/686232#M28151</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I've got a cluster with 2 peers, 1 seach head and 1 CM. All of them with a single network.&lt;/P&gt;&lt;P&gt;Due to network change, the server are going to have an additionnal card with a new network address.&lt;/P&gt;&lt;P&gt;I'll like to know if it's possible to swap the IP address used for réplication between peer member and SH communication while keeping the old one for forwarder communication&amp;nbsp;&lt;/P&gt;&lt;P&gt;Initialy:&lt;/P&gt;&lt;P&gt;peer 1 =&amp;gt; 10.254.x.1, peer 2 =&amp;gt; 10.254.x.2&lt;/P&gt;&lt;P&gt;After changes :&lt;/P&gt;&lt;P&gt;Peer 1 =&amp;gt; forwarder communication, 10.254.x.1, réplication/SH comm=&amp;gt; 10.254.y.1&lt;/P&gt;&lt;P&gt;Peer 2 =&amp;gt; forwarder communication, 10.254.x.2, réplication/SH comm=&amp;gt; 10.254.y.2&lt;/P&gt;&lt;P&gt;I've try to use register_replication_address and register_search_address parameter in server.conf with the new address 10.254.y. but the peer and the CM, complain of duplicate guid/member.&lt;/P&gt;&lt;P&gt;Do you have any advice on how to do this, if it's possible ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;&lt;P&gt;Frédéric&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 02 May 2024 20:12:46 GMT</pubDate>
    <dc:creator>fde</dc:creator>
    <dc:date>2024-05-02T20:12:46Z</dc:date>
    <item>
      <title>Changing peer IP address ?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Changing-peer-IP-address/m-p/686232#M28151</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I've got a cluster with 2 peers, 1 seach head and 1 CM. All of them with a single network.&lt;/P&gt;&lt;P&gt;Due to network change, the server are going to have an additionnal card with a new network address.&lt;/P&gt;&lt;P&gt;I'll like to know if it's possible to swap the IP address used for réplication between peer member and SH communication while keeping the old one for forwarder communication&amp;nbsp;&lt;/P&gt;&lt;P&gt;Initialy:&lt;/P&gt;&lt;P&gt;peer 1 =&amp;gt; 10.254.x.1, peer 2 =&amp;gt; 10.254.x.2&lt;/P&gt;&lt;P&gt;After changes :&lt;/P&gt;&lt;P&gt;Peer 1 =&amp;gt; forwarder communication, 10.254.x.1, réplication/SH comm=&amp;gt; 10.254.y.1&lt;/P&gt;&lt;P&gt;Peer 2 =&amp;gt; forwarder communication, 10.254.x.2, réplication/SH comm=&amp;gt; 10.254.y.2&lt;/P&gt;&lt;P&gt;I've try to use register_replication_address and register_search_address parameter in server.conf with the new address 10.254.y. but the peer and the CM, complain of duplicate guid/member.&lt;/P&gt;&lt;P&gt;Do you have any advice on how to do this, if it's possible ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;&lt;P&gt;Frédéric&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 May 2024 20:12:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Changing-peer-IP-address/m-p/686232#M28151</guid>
      <dc:creator>fde</dc:creator>
      <dc:date>2024-05-02T20:12:46Z</dc:date>
    </item>
    <item>
      <title>Re: Changing peer IP address ?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Changing-peer-IP-address/m-p/686262#M28152</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/241917"&gt;@fde&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;I'm not sure that's possible to use two IP addresses for each server: in Splunk every hostname has one IP address.&lt;/P&gt;&lt;P&gt;Ciao.&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Fri, 03 May 2024 06:25:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Changing-peer-IP-address/m-p/686262#M28152</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-05-03T06:25:56Z</dc:date>
    </item>
    <item>
      <title>Re: Changing peer IP address ?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Changing-peer-IP-address/m-p/686265#M28153</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I've seen in server.conf specification under clustering stanza, different parameter (&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.0.7/Admin/Serverconf#High_availability_clustering_configuration" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/9.0.7/Admin/Serverconf#High_availability_clustering_configuration&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;register_search_address: "This is the address that advertises the peer to search heads.&amp;nbsp;This is useful in the cases where a splunk host machine has multiple&amp;nbsp;interfaces and only one of them can be reached by another splunkd&amp;nbsp;instance."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;register_forwarder_address: "This is the address on which a peer is available for accepting data from forwarder.This is useful in the cases where a splunk host machine has multiple interfaces and only one of them can be reached by another splunkd instance."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;register_replication_address: "This is the address on which a peer is available for accepting replication data. This is useful in the cases where a peer host machine has multiple interfaces and only one of them can be reached by another splunkd instance."&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;So It's seems to be possible to use multiple IP, but I'm wordering how to convert peer with single IP to peer with multiple IP using this parameter.&lt;/P&gt;&lt;P&gt;Frédéric&lt;/P&gt;</description>
      <pubDate>Fri, 03 May 2024 06:38:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Changing-peer-IP-address/m-p/686265#M28153</guid>
      <dc:creator>fde</dc:creator>
      <dc:date>2024-05-03T06:38:48Z</dc:date>
    </item>
    <item>
      <title>Re: Changing peer IP address ?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Changing-peer-IP-address/m-p/686299#M28156</link>
      <description>&lt;P&gt;Here is the message logged on peer side, when during starting after adding register_replication_address&lt;/P&gt;&lt;P&gt;05-02-2024 11:26:38.046 +0200 WARN CMSlave [1355571 indexerPipe] - Failed to register with cluster master reason: failed method=POST path=/services/cluster/master/peers/?output_mode=json manager=CM:8089 rv=0 gotConnectionError=0 gotUnexpectedStatusCode=1 actual_response_code=500 expected_response_code=2xx status_line="Internal Server Error" socket_error="No error" remote_error=Cannot add peer=NEW-IP mgmtport=8089 (reason: Peer with guid=F00C07FD-F8A6-4C15-91D3-8A6CDCF28C96 is already registered and UP). [ event=addPeer status=retrying AddPeerRequest: { active_bundle_id=054CB061CFCD038A4B98FCDB01CE3F2F add_type=Initial-Add base_generation_id=0 batch_serialno=1 batch_size=26 forwarderdata_rcv_port=9997 forwarderdata_use_ssl=0 guid=F00C07FD-F8A6-4C15-91D3-8A6CDCF28C96 last_complete_generation_id=0 latest_bundle_id=054CB061CFCD038A4B98FCDB01CE3F2F mgmt_port=8089 register_forwarder_address= register_replication_address=NEW-IP register_search_address=NEW-IP replication_port=8087 replication_use_ssl=0 replications= server_name=PEER-NAME site=site1 splunk_version=9.0.7 splunkd_build_number=b985591d12fd status=Up } Batch 1/26 ].&lt;/P&gt;</description>
      <pubDate>Fri, 03 May 2024 12:07:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Changing-peer-IP-address/m-p/686299#M28156</guid>
      <dc:creator>fde</dc:creator>
      <dc:date>2024-05-03T12:07:53Z</dc:date>
    </item>
    <item>
      <title>Re: Changing peer IP address ?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Changing-peer-IP-address/m-p/687343#M28169</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;My problem is solved.&lt;/P&gt;&lt;P&gt;With support guidance, I change IP address used for replication.&lt;/P&gt;&lt;P&gt;Here is the steps used to:&lt;/P&gt;&lt;P&gt;1°) stop indexer&lt;/P&gt;&lt;P&gt;2°) change etc/system/local/server.conf and&amp;nbsp; add register_replication_address parameter with the new IP&lt;/P&gt;&lt;P&gt;3°) rename etc/instance.conf to etc/instance.conf.bkp&lt;/P&gt;&lt;P&gt;4°) restart indexer&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;CM = &amp;nbsp;Index clustering after few seconds =&amp;gt; OK&lt;/LI&gt;&lt;LI&gt;MC reconfigured the Indexer =&amp;gt; OK&lt;/LI&gt;&lt;LI&gt;CM and SH&amp;nbsp; =&amp;nbsp; Distributed Search =&amp;gt; &amp;nbsp;2 entry for the same instance name with 2 different Peer URI, the 2 entry appeared down and Sick&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;5°) I deleted one entry, the one with the old Peer URI =&amp;gt; After 5min and a refresh, no more entry Down and Sick.&lt;/P&gt;&lt;P&gt;And now, all seems to be ok. IP address for peer URI is now showing the new IP address.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 May 2024 14:30:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Changing-peer-IP-address/m-p/687343#M28169</guid>
      <dc:creator>fde</dc:creator>
      <dc:date>2024-05-13T14:30:44Z</dc:date>
    </item>
    <item>
      <title>Re: Changing peer IP address ?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Changing-peer-IP-address/m-p/687347#M28170</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/241917"&gt;@fde&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;good for you, see next time!&lt;/P&gt;&lt;P&gt;Ciao and happy splunking&lt;/P&gt;&lt;P&gt;Giuseppe&lt;/P&gt;&lt;P&gt;P.S.: Karma Points are appreciated &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 13 May 2024 14:37:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Changing-peer-IP-address/m-p/687347#M28170</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2024-05-13T14:37:31Z</dc:date>
    </item>
  </channel>
</rss>

