# Configuration Logstash 8.6.1 for monitoring VMWare server

**URL:** <https://discuss.elastic.co/t/configuration-logstash-8-6-1-for-monitoring-vmware-server/334593>\
**Category:** Logstash\
**Created:** [May 29, 2023, 2:21pm UTC](https://discuss.elastic.co/t/configuration-logstash-8-6-1-for-monitoring-vmware-server/334593 "2023-05-29T14:21:48Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![gaetano](https://avatars.discourse-cdn.com/v4/letter/g/b9e5f3/32.png) [@gaetano](https://discuss.elastic.co/u/gaetano)\
**Post date:** [May 29, 2023, 2:21pm UTC](https://discuss.elastic.co/t/configuration-logstash-8-6-1-for-monitoring-vmware-server/334593/1 "2023-05-29T14:21:48Z")

</div>

I'm trying to send VMWare server parameters to Elastic Search node 8.6.1 passing by Logstash 8.6.1.  
I obtained string in get option using Paessler MIB Importer.  
I downloaded MIB file in official site of VMWare.

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/2/62f0c7d0aa3785ecbe3f366998a74a653507f714.png)

This is my logstash configuration file.

```auto
input {
  snmp {
    get => ["1.3.6.1.2.1.17.1.1.0"]
    hosts => [{host => "udp:10.4.1.183/162" version => "3"}]
	mib_paths => ["C:\Monitoring\logging\logstash-8.6.1-server\mibs"]
	security_name => "root"
	auth_protocol => "sha"
        auth_pass => "test2"
	priv_protocol => "aes128"
	priv_pass => "test2"
	interval => 30
	security_level => "authPriv"
  }
}
output {
  elasticsearch {
		    hosts => ["https://XX.X.X.XXX:9200"]
			index => "server-%{+YYYY.MM.dd}"
			user => "elastic"
			password => "test"
			ssl => true
			ssl_certificate_verification => false
		}
}

```

When I start logstash.bat I obtain this error:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/b/0b5bbd3ec1a1adb82a79fe980c5d5d4f1baeda6b.png)

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [May 29, 2023, 2:40pm UTC](https://discuss.elastic.co/t/configuration-logstash-8-6-1-for-monitoring-vmware-server/334593/2 "2023-05-29T14:40:06Z")

</div>

You are getting a timeout while talking to `10.4.1.183` on port `162`.

Are you sure that the Logstash machine can talk with this address? Also, why port `162` instead of `161`?

You want Logstash to poll your snmp data, so you should use port 161 which is used for pulling the data.

It looks like a network issue, please try to run a `snmpwalk` on the logstash server to see if it is working.

---

<div class="post-metadata">

**Author:** ![gaetano](https://avatars.discourse-cdn.com/v4/letter/g/b9e5f3/32.png) [@gaetano](https://discuss.elastic.co/u/gaetano)\
**Post date:** [May 30, 2023, 8:22am UTC](https://discuss.elastic.co/t/configuration-logstash-8-6-1-for-monitoring-vmware-server/334593/3 "2023-05-30T08:22:53Z")

</div>

Thanks. Changing the port I solved the problem.  
For monitoring ram, cpu and storage informations that are present in the homepage of VMWare, what MIB file should I use?  
I tried with VMWARE-RESOURCES-MIB AND VMWARE-OBSOLETE-MIB but I don't receive those specific informations.  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/6/264b041e5a74be6805c3284a844b8813d5ab95c3.png)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 27, 2023, 8:23am UTC](https://discuss.elastic.co/t/configuration-logstash-8-6-1-for-monitoring-vmware-server/334593/4 "2023-06-27T08:23:32Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.