NetWorker: SNMP traps receiver is reporting "unknown trap"

SNMP notifications are configured through NetWorker: NetWorker: How To Configure, Create, And Modify SNMP Notifications

The SNMP traps receiver reports that it is receiving an "unknown trap" from the NetWorker server:

The NETWORKER-MIB.txt defines the nwServerNotification as a OBJECT-TYPE trap:

--(.1.3.6.1.4.1.160.0)
nwServerNotification    OBJECT-TYPE
        SYNTAX      OCTET STRING
    MAX-ACCESS  accessible-for-notify
    STATUS      current
    DESCRIPTION
        "nwServerNotification"
::= { networker 1 }
nwNotifications OBJECT IDENTIFIER ::= { networker 2 }
policyNotification OBJECT IDENTIFIER ::= { nwNotifications 1 }
workflowNotification OBJECT IDENTIFIER ::= { policyNotification 1 }
restoreNotification OBJECT IDENTIFIER ::= { nwNotifications 2 }
actionNotificationprefix OBJECT IDENTIFIER ::= { workflowNotification 1 }
actionNotificationObjects OBJECT IDENTIFIER ::= { workflowNotification 2 }
restoreNotificationprefix OBJECT IDENTIFIER ::= { restoreNotification 1 }
restoreNotificationObjects OBJECT IDENTIFIER ::= { restoreNotification 2 }

Some traps receivers only map trap Object Identities (OID) for NOTIFICATION-TYPE traps and do not interpret the legacy OBJECT-TYPE traps. For example, NOTIFICATION-TYPE traps are defined in the NETWORKER-MIB:

--(.1.3.6.1.4.1.160.0.2.1.1.1)
successfulActionNotification NOTIFICATION-TYPE
    OBJECTS     { server, client, jobtype, jobid, status, severity, exitcode,
starttime, endtime }
    STATUS      current
    DESCRIPTION
        "workflow notification"
::= { actionNotificationprefix  1 }

failedActionNotification NOTIFICATION-TYPE
    OBJECTS     { server, client, jobtype, jobid, status, severity, exitcode,
starttime, endtime }
    STATUS      current
    DESCRIPTION
        "workflow notification"
::= { actionNotificationprefix  2 }

didnotrunActionNotification NOTIFICATION-TYPE
    OBJECTS     { server, client, jobtype, jobid, status, severity, exitcode,
starttime, endtime }
    STATUS      current
    DESCRIPTION
        "action notification for did not run."
::= { actionNotificationprefix  3 }

The above traps should be received in the traps receiver.

No NetWorker action required. The functionality observed depends on the traps receiver. 

The NetWorker Administration Guide states the following:

Meaning, the traps receiver should still be receiving NOTIFICATION-TYPE traps when sent from the NetWorker server. For example, when a backup policy fails. You should receive a failedActionTypeNotification trap with structured information about the job.
Both the nwServerNotification and failedActionTypeNotification traps contain essentially the same details; however, the NOTIFICATION-TYPE trap is more structured, where the OBJECT-TYPE notification is raw data in one string. For example:

NOTIFICATION-TYPE failedActionNotification:

OBJECT-TYPE nwServerNotification for the same job:

The NetWorker Administration Guide provides more details about NetWorker SNMP traps. Support for NetWorker | Manuals & Documents 

The "unknown trap" message can be ignored. Consult with the traps receiver documentation or support team to see if these messages can be suppressed. 

• NetWorker: Windows NetWorker server not sending failedActionNotification SNMP notifications