SNMP Enterprise-specific trap types

Table 1 lists the Enterprise-specific trap types generated by subagents shipped with z/OS® Communications Server. All Enterprise-specific traps are generated with the trap value 6.

Table 1. MVS™ Enterprise trap types
Value Subagent Type Description
1 TCP/IP ibmMvsAtmOsasfAtmPvcCreate This trap is generated when OSA/SF sends an asyn notification to the TCP/IP DPI Subagent that a PVC was created for a given OSA-2 ATM. This notification contains the corresponding ibmMvsAtmOsasfPortName instance. Representation of this contains the port's (aal5 layer interface) 'ifIndex.pvcNameOctetCount. pvcNameInASCIINvt'.
2 TCP/IP ibmMvsAtmOsasfAtmPvcDelete This trap is generated when OSA/SF sends an asyn notification to the TCP/IP DPI Subagent that a PVC was deleted for a given OSA-2 ATM. This notification contains the corresponding ibmMvsAtmOsasfPortName instance. Representation of this contains the port's (aal5 layer interface) 'ifIndex.pvcNameOctetCount. pvcNameInASCIINvt'.
3 TCP/IP ibmMvsDVIPAStatusChange This trap is generated when a dynamic VIPA interface is either defined to a TCP/IP stack or its status changes. This notification contains the status, the origin value, the rank value, the moveable attribute, and the service manager indicator. The origin value indicates why the dynamic VIPA interface was originally defined.
4 TCP/IP ibmMvsDVIPARemoved This trap is generated when a dynamic VIPA interface is removed from a TCP/IP stack. This notification contains the status, the origin value, the rank value, the moveable attribute, and the service manager indicator prior to removal. The origin value indicates why the dynamic VIPA interface was previously activated.
5 TCP/IP ibmMvsDVIPATargetAdded This trap is generated by a sysplex distributor stack when it determines a designated target stack is active. Stacks are designated as target stacks on the VIPADISTRIBUTE profile statement. This notification contains the ibmMvsDVIPADistConfStatus object whose instance indicates the dynamic VIPA IP address, distributed port, and target stack dynamic XCF IP address.
6 TCP/IP ibmMvsDVIPATargetRemoved This trap is by a sysplex distributor stack when an active target stack is removed from distribution. This can occur when a VIPADISTRIBUTE DELETE profile statement is processed, or the target stack ends. This notification contains the ibmMvsDVIPADistConfStatus object whose instance indicates the dynamic VIPA IP address, distributed port, and target stack dynamic XCF IP address.
7 TCP/IP ibmMvsDVIPATargetServerStarted This trap is generated by a sysplex distributor stack when it receives notification from a target stack that a server has become active on a distributed port. This notification contains the count of servers ready at the port and the instance indicates the dynamic VIPA IP address, the distributed port, and the target stack dynamic XCF IP address.
8 TCP/IP ibmMvsDVIPATargetServerEnded This trap is generated by a sysplex distributor stack when it receives notification from a target stack that a server has ended on a distributed port. This notification contains the count of servers ready at the port and the instance indicates the dynamic VIPA IP address, the distributed port, and the target stack dynamic XCF IP address.
9 TCP/IP ibmMvsTcpipSubagentColdStart This trap is generated by the TCP/IP Subagent. It signifies that the Subagent, acting in a subagent role, has reintialized itself and that its configuration might have been altered.
10 TCP/IP ibmMvsTcpipIntfDown This trap is generated when a network interface transitions to the down state, meaning that is it now inactive. This trap is similar to the standard linkDown trap but provides the ifName value of the interface, along with the interface index and status values.
11 TCP/IP ibmMvsTcpipIntfUp This trap is generated when a network interface transitions to the up state, meaning that is it now active. This trap is similar to the standard linkUp trap but provides the ifName value of the interface, along with the interface index and status values.
1 Network SLAPM2 slapm2PolicyRuleMonNotOkay This notification is generated when one or more of the following three monitored quantities goes above its high threshold, indicating that its value has become unacceptable:
  • slapm2PRMonTcpRttCurrentDelay
  • slapm2PRMonCurrentTcpReXmit
  • slapm2PRMonAcceptQCurrentDelay
The first slapm2PRMonStatus value supplies the current monitor statuses for these three quantities, and the second value supplies the previous values. For a rising quantity, the bit in the previous status is set to off, indicating that the quantity is below the high threshold, and the bit in the current status is set to on, indicating that the quantity is above the high threshold. By examining these two values, it is possible to determine which monitored quantity (or quantities) caused the notification to be issued.

slapm2PRMonTrapEnable for the conceptual row must be set to enabled for this notification to be generated. Also, see the definitions of the high threshold objects for a description of the hysteresis behavior for this notification, which reduces the number of notifications that are generated when reporting is enabled.

2 Network SLAPM2 slapm2PolicyRuleMonOkay This notification is generated when one or more of the following three monitored quantities goes below its low threshold, indicating that its value returned to an acceptable level:
  • slapm2PRMonTcpRttCurrentDelay
  • slapm2PRMonCurrentTcpReXmit
  • slapm2PRMonAcceptQCurrentDelay
The first slapm2PRMonStatus value supplies the current monitor statuses for these three quantities, and the second value supplies their previous values. For a falling quantity, the bit in the previous status is set to on, indicating that the quantity is above the low threshold, and the bit in the current status is set to off, indicating that the quantity is below the low threshold. By examining these two values, it is possible to determine which monitored quantity (or quantities) caused the notification to be issued.

slapm2PRMonTrapEnable for the conceptual row must be set to enabled for this notification to be generated. Also, see the definitions of the low threshold objects for a description of the hysteresis behavior for this notification, which reduces the number of notifications that are generated when reporting is enabled.

3 Network SLAPM2 slapm2PolicyRuleDeleted A slapm2PolicyRuleDeleted notification is sent when a slapm2PolicyRuleStatsEntry is deleted if the value of slapm2PolicyTrapDeletedEnable is enabled(1).
4 Nework SLAPM2 slapm2PolicyRuleMonDeleted A slapm2PolicyRuleMonDeleted notification is sent when a slapm2PRMonEntry is deleted if the value of slapm2PolicyDeletedTrapEnable is enabled(1).