<?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 multiple management ports in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/multiple-management-ports/m-p/29067#M751</link>
    <description>&lt;P&gt;Hi , the case is about splunk deployment issue&lt;/P&gt;

&lt;P&gt;there is a deployment server and 20 deployment clients , we had finished setup 19 deployment clients already , they all use 8089 port to communicate to deployment server and works fine. when we setup the last one client , we found its 8089 port is occupied by other application , and user said it is impossible to release the port .&lt;BR /&gt;
My question is: is it possible to add another management port (for example 8090) on deployment server to communicate to the 20th client ? and keep the original 8089 port for other 19 clients ? &lt;/P&gt;

&lt;P&gt;thanks&lt;/P&gt;</description>
    <pubDate>Thu, 16 Jun 2011 05:20:35 GMT</pubDate>
    <dc:creator>dmlee</dc:creator>
    <dc:date>2011-06-16T05:20:35Z</dc:date>
    <item>
      <title>multiple management ports</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/multiple-management-ports/m-p/29067#M751</link>
      <description>&lt;P&gt;Hi , the case is about splunk deployment issue&lt;/P&gt;

&lt;P&gt;there is a deployment server and 20 deployment clients , we had finished setup 19 deployment clients already , they all use 8089 port to communicate to deployment server and works fine. when we setup the last one client , we found its 8089 port is occupied by other application , and user said it is impossible to release the port .&lt;BR /&gt;
My question is: is it possible to add another management port (for example 8090) on deployment server to communicate to the 20th client ? and keep the original 8089 port for other 19 clients ? &lt;/P&gt;

&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jun 2011 05:20:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/multiple-management-ports/m-p/29067#M751</guid>
      <dc:creator>dmlee</dc:creator>
      <dc:date>2011-06-16T05:20:35Z</dc:date>
    </item>
    <item>
      <title>Re: multiple management ports</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/multiple-management-ports/m-p/29068#M752</link>
      <description>&lt;P&gt;It does not matter at all what the port on the client is. It only matters that the clients all know the port on the deployment server. You don't have to do anything more.&lt;/P&gt;</description>
      <pubDate>Thu, 16 Jun 2011 06:14:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/multiple-management-ports/m-p/29068#M752</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2011-06-16T06:14:43Z</dc:date>
    </item>
  </channel>
</rss>

