This is a limitation in the way DFM handles this trap. If you need to see the IP of the poller, you will have to forward this trap to another trap receiving application, or look at the raw trap in a sniffer trace.
2.-The latest DFM loads an old MIB for Cisco devices.
3.-The load of the new Cisco MIB in the new realease of CiscoWorks LMS2.6 should fix this problem?
If this simple functionality cant be solved inside Cisco products itself... this is no good at all for the Cisco image. Anyway... i have posted a couple of questions before, and the answer never drives me to a solution without having to spend more money.
The part of DFM responsible for receiving traps and turning them into events belongs to EMC/Smarts, but DFM as a product is Cisco's responsibility. There is no way to load MIBs into DFM, and one will not see the polling address in LMS 2.6 either.
You should open a TAC service request so that a bug can be raised for this.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...