Hi to all,
We have DFM configured to send trap notifications towards an external machine, and we see that sometimes the alarms that arrives to the external NMS are delayed. some o them are sent only days after it were received in CW .
Any clue ??... correlation issues maybe ?
The attachment didn't come through, but I'm not sure how useful it would have been. It sounds like he sent a screenshot of a sniffer trace which isn't very helpful. We would need to see the binary sniffer trace file. In any event, I think I found an example in the log, and it looks like address resolution might be the culprit.
Basically, DFM takes the IP address that is configured and performs a lookup on the address. So, DFM tries to use the system resolver to resolve 192.168.168.134. This takes about three seconds to complete. The way Windows address resolution works can cause excessive delays when performing these kind of operations. As a workaround, try adding this address to DNS or your server's hosts file, and see if this problem improves.