AD | Application | AWS | Azure | Cloud | Database | Enterprise | Environmental | Event Log | File System | IoT | IT Service | Network/System | Infra | Performance | Protocol | SaaS | Security | Service Level | Storage | Linux | VMware | VoIP | Web | Wireless | SNMP

Crumbtrail

MonitorTools.com » Technical documentation » SNMP » MIB » RFC » APPN-TRAP-MIB » Objects

APPN-TRAP-MIB.mib object view, vendor RFC

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file APPN-TRAP-MIB and use it to monitor vendor specific OID's.

APPN-TRAP-MIB file content

Object view of APPN-TRAP-MIB:

Scalar Object
appnLocalTgTableChanges .1.3.6.1.2.1.34.4.1.7.2
A count of the number of times a row in the appnLocalTgTable has changed status since the APPN node was last reinitialized. This counter is incremented whenever a condition is detected that would cause a appnLocalTgOperStateChangeTrap or appnLocalTgCpCpChangeTrap notification to be sent, whether or not those notifications are enabled.
appnPortTableChanges .1.3.6.1.2.1.34.4.1.7.3
A count of the number of times a row in the appnPortTable has changed status since the APPN node was last reinitialized. This counter is incremented whenever a condition is detected that would cause a appnPortOperStateChangeTrap notification to be sent, whether or not this notification is enabled.
appnLsTableChanges .1.3.6.1.2.1.34.4.1.7.4
A count of the number of times a row in the appnLsTable has changed status since the APPN node was last reinitialized. This counter is incremented whenever a condition is detected that would cause a appnLsOperStateChangeTrap notification to be sent, whether or not this notification is enabled.
dlurDlusTableChanges .1.3.6.1.2.1.34.4.1.7.5
A count of the number of times a row in the dlurDlusTable has changed status since the APPN node was last reinitialized. This counter is incremented whenever a condition is detected that would cause a dlurDlusStateChangeTrap notification to be sent, whether or not this notification is enabled.
appnTrapControl .1.3.6.1.2.1.34.4.1.7.1
An object to turn APPN notification generation on and off. Setting a notification type's bit to 1 enables generation of notifications of that type, subject to further filtering resulting from entries in the snmpNotificationMIB. Setting this bit to 0 disables generation of notifications of that type. Note that generation of the appnIsrAccountingDataTrap is controlled by the appnIsInGlobeCtrAdminStatus object in the APPN MIB: if counts of intermediate session traffic are being kept at all, then the notification is also enabled.
Trap
appnIsrAccountingDataTrap .1.3.6.1.2.1.34.4.0.1
When it has been enabled, this notification is generated by an APPN node whenever an ISR session passing through the node is taken down, regardless of whether the session went down normally or abnormally. Its purpose is to allow a management application (primarily an accounting application) that is monitoring the ISR counts to receive the final values of these counts, so that the application can properly account for the amounts the counts were incremented since the last time the application polled them. The appnIsInSessUpTime object provides the total amount of time that the session was active. This notification is not a substitute for polling the ISR counts. In particular, the count values reported in this notification cannot be assumed to be the complete totals for the life of the session, since they may have wrapped while the session was up. The session to which the objects in this notification apply is identified by the fully qualified CP name and PCID that make up the table index. An instance of this notification will contain exactly one instance of each of its objects, and these objects will all belong to the same conceptual row of the appnIsInTable. Generation of this notification is controlled by the same object in the APPN MIB, appnIsInGlobeCtrAdminStatus, that controls whether the count objects themselves are being incremented.
appnLocalTgOperStateChangeTrap .1.3.6.1.2.1.34.4.0.2
When it has been enabled, this notification makes it possible for an APPN topology application to get asynchronous notifications of local TG operational state changes, and thus to reduce the frequency with which it polls for these changes. This notification is sent whenever there is a change to the appnLocalTgOperational object in a row of the appnLocalTgTable. This notification is only sent for row creation if the row is created with a value of 'true' for appnLocalTgOperational. This notification is only sent for row deletion if the last value of appnLocalTgOperational was 'true'. In this case, the value of appnLocalTgOperational in the notification shall be 'false', since the deletion of a row indicates that the TG is no longer operational. The notification is more than a simple 'poll me now' indication. It carries both a count of local TG topology changes, and the current operational state itself. The count of changes allows an application to detect lost notifications, either when polling or upon receiving a subsequent notification, at which point it knows it must retrieve the entire appnLocalTgTable again. This is the same count as used in the appnLocalCpCpStateChangeTrap. A lost notification could indicate a local TG CP-CP session state change or an operational state change. Generation of this notification is controlled by the appnTrapControl object.
appnLocalTgCpCpChangeTrap .1.3.6.1.2.1.34.4.0.3
When it has been enabled, this notification makes it possible for an APPN topology application to get asynchronous notifications of local TG control-point to control-point (CP-CP) session state changes, and thus to reduce the frequency with which it polls for these changes. This notification is sent whenever there is a change to the appnLocalTgCpCpSession object but NOT the appnLocalTgOperational object in a row of the appnLocalTgTable. This notification is never sent for appnLocalTgTable row creation or deletion. The notification is more than a simple 'poll me now' indication. It carries both a count of local TG topology changes, and the current CP-CP session state itself. The count of changes allows an application to detect lost notifications, either when polling or upon receiving a subsequent notification, at which point it knows it must retrieve the entire appnLocalTgTable again. This is the same count as used in the appnLocalTgOperStateChangeTrap. A lost notification could indicate a local TG CP-CP session state change or an operational state change. Generation of this notification is controlled by the appnTrapControl object.
appnPortOperStateChangeTrap .1.3.6.1.2.1.34.4.0.4
When it has been enabled, this notification makes it possible for an APPN topology application to get asynchronous notifications of port operational state changes, and thus to reduce the frequency with which it polls for these changes. This notification is only sent when a appnPortOperState has transitioned to a value of 'active' or 'inactive'. This notification is sent whenever there is a appnPortOperState object transition to 'inactive' or 'active' state in the appnPortTable. This notification is only sent for row creation if the row is created with a value of 'active' for appnPortOperState. This notification is only sent for row deletion if the last value of appnPortOperState was 'active'. In this case, the value of appnPortOperState in the notification shall be 'inactive', since the deletion of a row indicates that the port is no longer active. The notification is more than a simple 'poll me now' indication. It carries both a count of port table changes, and the operational state itself. The count of changes allows an application to detect lost notifications, either when polling or upon receiving a subsequent notification, at which point it knows it must retrieve the entire appnPortTable again. Generation of this notification is controlled by the appnTrapControl object.
appnLsOperStateChangeTrap .1.3.6.1.2.1.34.4.0.5
When it has been enabled, this notification makes it possible for an APPN topology application to get asynchronous notifications of link station operational state changes, and thus to reduce the frequency with which it polls for these changes. This notification is only sent when a appnLsOperState has transitioned to a value of 'active' or 'inactive'. This notification is sent whenever there is a appnLsOperState object transition to 'inactive' or 'active' state in the appnLsTable. This notification is only sent for row creation if the row is created with a value of 'active' for appnLsOperState. This notification is only sent for row deletion if the last value of appnLsOperState was 'active'. In this case, the value of appnLsOperState in the notification shall be 'inactive', since the deletion of a row indicates that the link station is no longer active. The notification is more than a simple 'poll me now' indication. It carries both a count of link station table changes, and the operational state itself. The count of changes allows an application to detect lost notifications, either when polling or upon receiving a subsequent notification, at which point it knows it must retrieve the entire appnLsTable again. Generation of this notification is controlled by the appnTrapControl object.
dlurDlusStateChangeTrap .1.3.6.1.2.1.34.4.0.6
When it has been enabled, this notification makes it possible for an APPN topology application to get asynchronous notifications of DLUR-DLUS session changes, and thus to reduce the frequency with which it polls for these changes. This notification is sent whenever there is a dlurDlusSessnStatus object transition to 'inactive' or 'active' state in the dlurDlusTable. This notification is only sent for row creation if the row is created with a value of 'active' for dlurDlusSessnStatus. This notification is only sent for row deletion if the last value of dlurDlusSessnStatus was 'active'. In this case, the value of dlurDlusSessnStatus in the notification shall be 'inactive', since the deletion of a row indicates that the session is no longer active. The notification is more than a simple 'poll me now' indication. It carries both a count of DLUR-DLUS table changes, and the session status itself. The count of changes allows an application to detect lost notifications, either when polling or upon receiving a subsequent notification, at which point it knows it must retrieve the entire dlurDlusTable again. Generation of this notification is controlled by the appnTrapControl object.
Object Identifier
appnTrapMIB .1.3.6.1.2.1.34.4.0
This MIB module defines notifications to be generated by network devices with APPN capabilities. It presupposes support for the APPN MIB. It also presupposes support for the DLUR MIB for implementations that support the DLUR-related groups.
appnTrapObjects .1.3.6.1.2.1.34.4.1.7
Group
appnTrapMibIsrNotifGroup .1.3.6.1.2.1.34.4.3.2.21
A notification for reporting the final values of the APPN MIB's ISR counters.
appnTrapMibTopoConfGroup .1.3.6.1.2.1.34.4.3.2.22
A collection of objects for reducing the polling associated with the local topology tables in the APPN MIB. Nodes that implement this group SHALL also implement the appnTrapMibTopoNotifGroup.
appnTrapMibTopoNotifGroup .1.3.6.1.2.1.34.4.3.2.23
A collection of notifications for reducing the polling associated with the local topology tables in the APPN MIB. Nodes that implement this group SHALL also implement the appnTrapMibTopoConfGroup.
appnTrapMibDlurConfGroup .1.3.6.1.2.1.34.4.3.2.24
A collection of objects for reducing the polling associated with the dlurDlusTable in the DLUR MIB. Nodes that implement this group SHALL also implement the appnTrapMibDlurNotifGroup.
appnTrapMibDlurNotifGroup .1.3.6.1.2.1.34.4.3.2.25
A notification for reducing the polling associated with the dlurDlusTable in the DLUR MIB. Nodes that implement this group SHALL also implement the appnTrapMibDlurConfGroup.