SNMP trap listener fails to startIssue SNMP trap listener fails to start. Error log : Could not start the trap listener on port 162: Address already in use: Cannot bind.ReleaseAllCauseThe default SNMP trap service is configured for the port 162 on the mid server host machine, which was preventing the Servicenow’s trap being able to start on port 162.ResolutionIn order to fix this issue, below 2 approaches can be considered.Approach 1 You can define another port (1162) for the Servicenow trap listener and start the ServiceNow SNMP trap from the instance. Approach 2 Decouple the existing active exe that's running on port 162.Open services.msc on the MID server host, look for the SNMP trap service and then stop it.Once the default SNMP service gets stopped, please attempt to start the ServiceNow’s SNMP trap from the instance and it should start.The recommended approach would be to define another port for Servicenow trap listener.