SCOM Network Monitoring

Question

Hello!

We have a resourcepool for Networkmonitorin with 2 Servers.
We have two Network-Discoveries running on the 2 Servers in the Network Resource Pool.

Default Port 162 is enabled on the Servers where a Network discovery is running.

But we use the Port for another Service.

Here my question: How can I disable that scom (monitoringhost.exe) is listening on port 162.

rg
Hansi

Answer 1

Hi Hansi,

Microsoft was labeling this as "not supported", but to be honest I don't think that there is even a way of changing the port. So, I don't think you will be able to do this :(
So, "No, you can't prevent SCOM from using Port 162 for SNMP Traps", this is with 99.999% certiainty.
Sorry to dissapoint you!

Still, I am not quite sure how to interpüret this...From:

SNMP Trap monitoring with SCOM 2012 R2
https://kevinholman.com/2015/02/03/snmp-trap-monitoring-with-scom-2012-r2/

There are LOTS of blogs out there saying the SNMP service is required, and quite frankly – it isn’t…. the SCOM SNMP trap listener uses a MonitoringHost.exe process and does not interact with the Windows SNMP stack. I initially posted about configuring this because ALL of the blog resources pointed to the need for the SNMP service, but in my testing this is totally not required. Thanks to Mihai for setting me straight again.

Still, if MonitoringHost.exe listens on 161 I don't see how you can work around this...

Regards,
Stoyan

Answer 2

Hi Hansi (@Hansi ),

Port 162 is used to receive SNMP Traps. So if you are not doing SNMP Trap Monitoring with SCOM, but you do only SNMP (query) monitoring (port 161), this should not be an issue.
One needs to differentiate between SNMP query (161) and SNMP traps (162), but to be completely honest you should ask the application vendor of the other service (application, which uses 161) on how to change the port number, because I think it is not a good or common approach to use basic port as 162 for a service.
This being said, there is no way to change the listening port of the Health Service (monitoringhost.exe), when it comes to SNMP trap monitoring.

I hope I could calrify this for you!

----------

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Stoyan Chalakov

Answer 3

Hello Stoyan!

Yes I know the different between 161 and 162. My Problem is, that we have a own TrapCollector in use. And only this Application I should use for receiving Traps on Port 162. This TrapCollector is installed on an SCOM-Gateway-Server. And this this the reason why I sI need to prevent scom from blocking port 162. Is their a possibility to to this?

rg
Hansi