Bdfry,
We use NNM6.1 on our platform and not NNM6.2, but I still think that it is safe to say that out of the box, NNM does not come with the sm_ov_fwd process, so it looks like an application called SMARTS InCharge, which is an event correlation tool. With a full intetration the processes that would integrate with NNM would be sm_ov_event, sm_ov_fwd, sm_ito_notify and sm_ov_topo, although full is not required. The sm_ov_fwd process would allow snmptraps from a device on the managed network to be forwarded to the smarts dB.
Since we run this on a HPUX platform things may differ... There should be a log file on the server (on HPUX, /opt/smarts/logs) called sm_ov_fwd.log. Check here to see if there are any errors or timeouts. This sm_ov_fwd process tries first to connect to a domain server, specified during the installation. I'm suspecting that the problem lies within that connection not being established causing the sm_ov_fwd process not to start because it doesn't know who to forward events to. If this is the case check the ic-server-<domainname> script on your server, domainname being the hostname of the server which will receive the events. (loc=/opt/smarts/scripts). There is a parameter in this script called DMNAME that should be set to that hostname. Link this file to an /etc/init.d startup script, then execute the script with a stop and start. I'm definitely not a pro with this app, but hopefully this will get you started in the right direction.
***cgainey