Hi Ekost, Thanks for your effort on this , Yes I had checked all the parameter which is mentioned by you on comments for one of the RM agent node and found everything perfect with configurations and ports.
Details :
hostname=Rmnode01 --Remote Agent node
hostname=DPinstance --Deployment server
hostname=indexer --Indexer server
Telnet Details:
Telnet connectivity checked from remote node to Deployment server - Its connecting
[root@Rmnode01 default]# telnet DPinstance.com 8089 -- Remote Agent node
Trying 168.x.x.x...
Connected to DPinstance.com (168.x.x.x).
Escape character is '^]'.
Telnet connectivity checked from Deployment server to Remote node - its connecting
[root@DPinstance ~]# telnet Rmnode01.xxx.com 8089 -- Deployement server
Trying 10..x.x.x...
Connected to Rmnode01.xxx.com.
Escape character is '^]'.
Telnet connectivity checked from Remote node to Indexer instance -- Its connecting
[root@Rmnode01 default]# telnet indexer.xxx.com 9997 -- Indexer instance
Trying 168.x.x.x...
Connected to indexer.xxx.com (168.x.x.x).
Escape character is '^]'.
[root@Rmnode01 ~]# cd /opt/splunkforwarder/bin
[root@Rmnode01 bin]# ./splunk version
Splunk Universal Forwarder 6.2.0 (build 237341)
But in Deployment server we noticed that open file parameter was set to 1024 which is very less when compared to the splunk recommendation, so we are advised to increase the parameter to minimum 81942 or more based on our environment setup. I hope this should fix the issue, i will update on changing the parameter in /etc/security/limits.conf.
... View more