topic Startup of Trap Listener is failed may be due to port 162 conflict in Active IQ Unified Manager Discussions

Startup of Trap Listener is failed may be due to port 162 conflict

bjornkoopmans — Thu, 05 Jun 2025 06:54:33 GMT

Hi all,

Recently we receive the following error when starting DFM:

Startup of Trap Listener is failed may be due to port 162 conflict.

I can't figure out why. As far as I can see port 162 isn't used by any other application, as suggested on http://now.netapp.com/NOW/knowledge/docs/DFM_win/rel381/html/software/opsmgr/monitoring/concept/c_dfm_mntr_snmp-trap-lstn-conf-reqt.html.

If I do a portscan on the DFM server I don't see port 162 being used. I do see that port 161 is being used by service 'snmp', although this service is disabled in services.msc.

If I set the SNMP trap listener to another port, say 1620, I receive the same error.

I can't find anything about this issue n NOW.

Anybody has any ideas?

Thanks in advance!

Kind egards,

Bjorn

Re: Startup of Trap Listener is failed may be due to port 162 conflict

hiyer — Wed, 18 May 2011 11:34:40 GMT

Are you running an antivirus or some such application? It is possible that it's preventing DFM from opening a connection on that port. You will need to configure this application, if any, to allow traffic on that port; or allow all traffic to and from the DFM executables.

Re: Startup of Trap Listener is failed may be due to port 162 conflict

bjornkoopmans — Wed, 18 May 2011 12:10:51 GMT

Hi hiyer

We do have a virusscanner, but port blocking is disabled. Even so I temporarely disabled the virusscanner, but it made no difference.

I forgot to mention that the Windows firewall is also disabled.

Bjorn

Re: Startup of Trap Listener is failed may be due to port 162 conflict

GRAHAMSWIFT — Sun, 04 Sep 2011 02:50:57 GMT

Hello, have you found the cause of this yet? I have the same issue, I have found an IBM storage manager event retreiver service using the same port but after disabling it I still received the same error. Also changing the port to something that is not showing as used also yeilds the same error.

DFM 4.0.2

Re: Startup of Trap Listener is failed may be due to port 162 conflict

msaravan — Tue, 06 Sep 2011 05:50:43 GMT

I am not sure about the way you tried to change your port number.

After changing the port number, you have to ensure that you restart the dfm server service for port binding.

[root@lnx ~]# dfm options list | grep -i 162

snmpTrapListenerPort 162

[root@lnx ~]#

[root@lnx ~]# dfm options set snmpTrapListenerPort=5000

Changed SNMP trap listener port to 5000.

[root@lnx ~]# dfm service stop server

Service: server stopped.

[root@lnx ~]# dfm service start server

Service: server started.

[root@lnx ~]#

Now, watch out your dfmserver.log. It'll have debug messages regarding the port binding process for your trap receiver.

[root@lnx log]# tail -f dfmserver.log

Sep 06 11:06:57 [dfmserver:DEBUG]: [3872:0xb7f646c0]: Bound to [::]:8488

Sep 06 11:06:57 [dfmserver:DEBUG]: [3872:0xb7f646c0]: Unable to bind to [0.0.0.0]:8488 (errno=98)

Sep 06 11:06:57 [dfmserver: INFO]: [3872:0xb7f646c0]: Initializing Diagnosis Engine.

Sep 06 11:06:57 [dfmserver: INFO]: [3872:0xb7f646c0]: Starting Event Poller thread.

Sep 06 11:06:57 [dfmserver: INFO]: [3872:0x1a1ab90]: snmp port = 5000

Sep 06 11:06:57 [dfmserver: INFO]: [3872:0x1a1ab90]: Starting snmpTrapListener thread...

Please follow the above steps and share your observations.

Regards,

Saravanan

Re: Startup of Trap Listener is failed may be due to port 162 conflict

bjornkoopmans — Tue, 06 Sep 2011 07:38:20 GMT

Hi Saravanan,

Thanks for your suggestion.

I tried the exact steps you provided, but it did not solve my problem:

C:\Users\adm-xxxxxx>dfm option list | find "162"
snmpTrapListenerPort 162

C:\Users\adm-xxxxxx>dfm option set snmpTrapListenerPort=5000
Changed SNMP trap listener port to 5000.

C:\Users\adm-xxxxxx>dfm service stop server
Service: server stopped.

C:\Users\adm-xxxxxx>dfm service start server
Service: server started.

C:\Users\adm-xxxxxx>dfm option list | find "5000"
snmpTrapListenerPort 5000

dfmserver;log:

Sep 06 09:18:24 [dfmserver: INFO]: [26808:0x6cf4]: Stopping server

Sep 06 09:18:24 [dfmserver:DEBUG]: [26808:0x6cf4]: Shutting down Performance Advisor.

Sep 06 09:18:24 [dfmserver: INFO]: [26808:0x6458]: Performance Advisor is now stopped

Sep 06 09:18:24 [dfmserver:DEBUG]: [26808:0x6cf4]: Performance Advisor shutdown completed.

Sep 06 09:18:24 [dfmserver: INFO]: [26808:0x6abc]: Stopped snmptraplistener thread.

Sep 06 09:18:24 [dfmserver: INFO]: [26808:0x6cf4]: Signalling Event Poller thread to shutdown.

Sep 06 09:18:40 [dfmserver: INFO]: [29452:0x6420]: Starting server

Sep 06 09:18:41 [dfmserver:DEBUG]: [29452:0x6420]: Initializing perf instance cache

Sep 06 09:18:41 [dfmserver:DEBUG]: [29452:0x6420]: Initialized perf instance cache

Sep 06 09:18:41 [dfmserver:DEBUG]: [29452:0x6420]: Performance Advisor Initialized

Sep 06 09:18:41 [dfmserver:DEBUG]: [29452:0x6420]: Bound to [::]:8088

Sep 06 09:18:41 [dfmserver:DEBUG]: [29452:0x6420]: Bound to [0.0.0.0]:8088

Sep 06 09:18:43 [dfmserver:DEBUG]: [29452:0x6420]: Bound to [::]:8488

Sep 06 09:18:43 [dfmserver:DEBUG]: [29452:0x6420]: Bound to [0.0.0.0]:8488

Sep 06 09:18:43 [dfmserver: INFO]: [29452:0x6420]: Initializing Diagnosis Engine.

Sep 06 09:18:43 [dfmserver: INFO]: [29452:0x6420]: Starting Event Poller thread.

Sep 06 09:18:43 [dfmserver: INFO]: [29452:0x73f0]: snmp port = 5000

Sep 06 09:18:43 [dfmserver:ERROR]: [29452:0x73f0]: snmptraplistener bind failed.

Sep 06 09:18:43 [dfmserver:ERROR]: [29452:0x73f0]: Startup of Trap Listener is failed may be due to port 5000 conflict.

Sep 06 09:18:45 [dfmserver:DEBUG]: [29452:0x713c]: Warning: api_oper_list includes an undefined API: migrate-route-info.

Any more thoughts?

Startup of Trap Listener is failed may be due to port 162 conflict

msaravan — Tue, 06 Sep 2011 08:46:02 GMT

Thanks. Your logs are very much helpful.

Can you please share your OS and DFM details ??

Also, try with port numbers around 8500.

Saravanan

Startup of Trap Listener is failed may be due to port 162 conflict

bjornkoopmans — Tue, 06 Sep 2011 08:59:56 GMT

Hi Saravanan,

Port 8500 didn't help:

Sep 06 10:50:02 [dfmserver: INFO]: [29452:0x6888]: Stopping server

Sep 06 10:50:02 [dfmserver:DEBUG]: [29452:0x6888]: Shutting down Performance Advisor.

Sep 06 10:50:02 [dfmserver: INFO]: [29452:0x6b78]: Performance Advisor is now stopped

Sep 06 10:50:02 [dfmserver:DEBUG]: [29452:0x6888]: Performance Advisor shutdown completed.

Sep 06 10:50:02 [dfmserver: INFO]: [29452:0x73f0]: Stopped snmptraplistener thread.

Sep 06 10:50:02 [dfmserver: INFO]: [29452:0x6888]: Signalling Event Poller thread to shutdown.

Sep 06 10:50:39 [dfmserver: INFO]: [26540:0x65a8]: Starting server

Sep 06 10:50:40 [dfmserver:DEBUG]: [26540:0x65a8]: Initializing perf instance cache

Sep 06 10:50:40 [dfmserver:DEBUG]: [26540:0x65a8]: Initialized perf instance cache

Sep 06 10:50:40 [dfmserver:DEBUG]: [26540:0x65a8]: Performance Advisor Initialized

Sep 06 10:50:40 [dfmserver:DEBUG]: [26540:0x65a8]: Bound to [::]:8088

Sep 06 10:50:40 [dfmserver:DEBUG]: [26540:0x65a8]: Bound to [0.0.0.0]:8088

Sep 06 10:50:43 [dfmserver:DEBUG]: [26540:0x65a8]: Bound to [::]:8488

Sep 06 10:50:43 [dfmserver:DEBUG]: [26540:0x65a8]: Bound to [0.0.0.0]:8488

Sep 06 10:50:43 [dfmserver: INFO]: [26540:0x65a8]: Initializing Diagnosis Engine.

Sep 06 10:50:43 [dfmserver: INFO]: [26540:0x65a8]: Starting Event Poller thread.

Sep 06 10:50:43 [dfmserver: INFO]: [26540:0x6d64]: snmp port = 8500

Sep 06 10:50:43 [dfmserver:ERROR]: [26540:0x6d64]: snmptraplistener bind failed.

Sep 06 10:50:43 [dfmserver:ERROR]: [26540:0x6d64]: Startup of Trap Listener is failed may be due to port 8500 conflict.

Sep 06 10:50:47 [dfmserver:DEBUG]: [26540:0x6580]: Warning: api_oper_list includes an undefined API: migrate-route-info.

OS: Windows 2008 Enterprise SP2 64-bit

DFM: 4.0.2.7803 (4.0.2)

Thanks for your help.

Bjorn

Re: Startup of Trap Listener is failed may be due to port 162 conflict

manup — Fri, 02 Mar 2012 05:16:54 GMT

Hi Bjorn,

Were you able to fix this error? I have a customer who is running into the same error and hence not able to add any device to dfm. Were you able to add storage devices in dfm when you had this issue?

Thanks,

Manu

Re: Startup of Trap Listener is failed may be due to port 162 conflict

bjornkoopmans — Fri, 02 Mar 2012 07:50:44 GMT

Hi Manu,

Unfortunately we never figured out how to resolve this issue, but we never had any trouble adding devices to DFM.

Bjorn

Re: Startup of Trap Listener is failed may be due to port 162 conflict

msaravan — Tue, 06 Mar 2012 13:53:32 GMT

Hi Manu,

They are different problems.

Adding Device to DFM is completely different from SNMP trap listener failed error.

Can you get me the output of "dfm host diag <filer>" and based on that we can diagnose this further.

Regards,

Saravanan