We are able to successfully receive traps from our monitored devices in DFM using SNMPv3, what we are having problems with is when a trap is received by DFM from a device we have "SNMP Trap Notification" setup within LMS to forward that trap to our UniCenter server.
We set this up by the menu path from DFM - Notification Services - SNMP Trap Notification. There we setup a subscription and notification group provided the server hostname and used port 162.
The trap notifications have always worked until our network was restricted to not allow SNMPv1 and SNMPv2 traffic. So I am assuming, now once a trap is received by DFM, the SNMP Trap Notification is sending the traps to our UniCenter server using SNMPv2 (and still is). The forwarded trap to our UniCenter server is being blocked because it is being sent by SNMPv2 traffic
What we need to figure out is how to get LMS to use the "SNMP Trap Notification" feature to send the traps to our UniCenter server using SNMPv3