<?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: Azure VM - Won't report to Deployment server in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Azure-VM-Won-t-report-to-Deployment-server/m-p/550876#M91464</link>
    <description>&lt;P&gt;Thanks! I will check it out.&amp;nbsp; I guess I'm still a little confused.&amp;nbsp; In the past, after installing the forwarder, I could find the host in the forwarder management GUI- THEN I would set up a server class for that machine.&amp;nbsp; I don't see the host showing up at all in forwarder management.&amp;nbsp; However, I haven't had access to the machine yet, so I will check the logs you mentioned on the client side when I gain access...thanks again!&lt;/P&gt;</description>
    <pubDate>Fri, 07 May 2021 17:11:57 GMT</pubDate>
    <dc:creator>spluzer</dc:creator>
    <dc:date>2021-05-07T17:11:57Z</dc:date>
    <item>
      <title>Azure VM - Won't report to Deployment server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Azure-VM-Won-t-report-to-Deployment-server/m-p/550449#M91406</link>
      <description>&lt;P&gt;Hey Splunksters,&lt;BR /&gt;&lt;BR /&gt;I have an Azure VM that I put a forwarder on that is supposed to reach out to my on-prem deployment server (which I have successfully done in my separate development environment).&amp;nbsp;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;(just a little backstory in case this helps anyone)&lt;BR /&gt;Originally it was installed using a script that pointed to the wrong Deployment server, so I uninstalled the forwarder - then reinstalled it pointing to the correct deployment server&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;I checked the deploymentclient.conf and it is pointed correctly - restarted the service etc etc. - But none of the deployment apps are showing up on the client - and the DS GUI does not show the the client server in forwarding management&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Ran a test-netconnection from the Azuer machine to the DS using the DS management port - and got TCP success&lt;BR /&gt;&lt;BR /&gt;However, when I run test connection on the DS back to the Azure machine it fails -- Which would lead me to believe there is a firewall or isn't set to bi-directional port etc etc etc.&lt;BR /&gt;&lt;BR /&gt;&lt;U&gt;HOWEVER&lt;/U&gt;, my DEV setup gives me the exact same test connection failure going&amp;nbsp; &amp;nbsp; FROM:&amp;nbsp; &amp;nbsp;the DS&amp;nbsp; TO:&amp;nbsp; the Azure client machine ----BUT IT STILL WORKS (data comes in, apps deploy , etc in DEV ) ---so I'm confused&lt;BR /&gt;&lt;BR /&gt;That's why I feel like I am taking crazy pills.&amp;nbsp; Considering doing a full reboot of the client machine, but that is not optimal at the moment.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Thanks!&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 04 May 2021 19:40:58 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Azure-VM-Won-t-report-to-Deployment-server/m-p/550449#M91406</guid>
      <dc:creator>spluzer</dc:creator>
      <dc:date>2021-05-04T19:40:58Z</dc:date>
    </item>
    <item>
      <title>Re: Azure VM - Won't report to Deployment server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Azure-VM-Won-t-report-to-Deployment-server/m-p/550455#M91407</link>
      <description>&lt;P&gt;The DS&amp;nbsp;&lt;STRONG&gt;never&lt;/STRONG&gt; reaches out to clients, connections are&amp;nbsp;&lt;STRONG&gt;always&lt;/STRONG&gt; initiated by the deployment client every &lt;EM&gt;phoneHomeInterval&lt;/EM&gt; seconds. What hostname does the Azure VM present to the DS? Maybe it simply doesn't match any of your defined serverclass.conf entries?&lt;/P&gt;&lt;P&gt;You can try to set clientName in deploymentclient.conf to a static value that matches serverclass.conf rules to test this theory. Also, splunkd.log on the DC will provide clues; look for component=HttpPubSubConnection to see if the connection is successful.&amp;nbsp;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Tue, 04 May 2021 22:27:00 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Azure-VM-Won-t-report-to-Deployment-server/m-p/550455#M91407</guid>
      <dc:creator>s2_splunk</dc:creator>
      <dc:date>2021-05-04T22:27:00Z</dc:date>
    </item>
    <item>
      <title>Re: Azure VM - Won't report to Deployment server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Azure-VM-Won-t-report-to-Deployment-server/m-p/550876#M91464</link>
      <description>&lt;P&gt;Thanks! I will check it out.&amp;nbsp; I guess I'm still a little confused.&amp;nbsp; In the past, after installing the forwarder, I could find the host in the forwarder management GUI- THEN I would set up a server class for that machine.&amp;nbsp; I don't see the host showing up at all in forwarder management.&amp;nbsp; However, I haven't had access to the machine yet, so I will check the logs you mentioned on the client side when I gain access...thanks again!&lt;/P&gt;</description>
      <pubDate>Fri, 07 May 2021 17:11:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Azure-VM-Won-t-report-to-Deployment-server/m-p/550876#M91464</guid>
      <dc:creator>spluzer</dc:creator>
      <dc:date>2021-05-07T17:11:57Z</dc:date>
    </item>
    <item>
      <title>Re: Azure VM - Won't report to Deployment server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Azure-VM-Won-t-report-to-Deployment-server/m-p/550906#M91467</link>
      <description>&lt;P&gt;Ah, yes. You are correct. It should show up as soon as it phones home, even without matching apps. Sorry I misunderstood your description.&lt;/P&gt;&lt;P&gt;So, likely there is some connectivity issue between the deployment client and the DS. Forwarder logs will have clues.&lt;/P&gt;</description>
      <pubDate>Fri, 07 May 2021 19:54:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Azure-VM-Won-t-report-to-Deployment-server/m-p/550906#M91467</guid>
      <dc:creator>s2_splunk</dc:creator>
      <dc:date>2021-05-07T19:54:14Z</dc:date>
    </item>
    <item>
      <title>Re: Azure VM - Won't report to Deployment server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Azure-VM-Won-t-report-to-Deployment-server/m-p/573520#M101443</link>
      <description>&lt;P&gt;Update:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The outputs.conf on the azure client did not have the fqdn&amp;nbsp; for the indexer and deployment server. We weren't including the fqdn in the outputs.conf the was being deployed, bc all of our hosts at the time were on-prem.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Obviously, Azure needed the full name like (splunkserver.somedomain:8089)&lt;/P&gt;&lt;P&gt;Instead of splunkserver:8089&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Nov 2021 19:20:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Azure-VM-Won-t-report-to-Deployment-server/m-p/573520#M101443</guid>
      <dc:creator>spluzer</dc:creator>
      <dc:date>2021-11-03T19:20:20Z</dc:date>
    </item>
    <item>
      <title>Re: Azure VM - Won't report to Deployment server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Azure-VM-Won-t-report-to-Deployment-server/m-p/573521#M101444</link>
      <description>&lt;P&gt;Glad to hear you got it resolved. Sounds like this could qualify as a connectivity issue. &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 03 Nov 2021 19:22:41 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Azure-VM-Won-t-report-to-Deployment-server/m-p/573521#M101444</guid>
      <dc:creator>s2_splunk</dc:creator>
      <dc:date>2021-11-03T19:22:41Z</dc:date>
    </item>
  </channel>
</rss>

