CISCO-TAP-MIB

        This module manages Cisco's intercept feature.
    
Source file
CISCO-TAP-MIB
Last revised
Identity
cTapMIB
Base OID
1.3.6.1.4.1.9.9.252
Imported Objects
CISCO-QOS-PIB-MIB Dscp
CISCO-SMI ciscoMgmt
IF-MIB InterfaceIndexOrZero
INET-ADDRESS-MIB InetAddress InetAddressPrefixLength InetAddressType InetPortNumber
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DateAndTime MacAddress RowStatus TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-TAP-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-TAP-MIB::cTapMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-TAP-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-TAP-MIB::cTapMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (66)
.1.3.6.1.4.1.9.9.252
.1.3.6.1.4.1.9.9.252.0
.1.3.6.1.4.1.9.9.252.1
.1.3.6.1.4.1.9.9.252.1.1
Integer32
.1.3.6.1.4.1.9.9.252.1.1.1
.1.3.6.1.4.1.9.9.252.1.1.2
.1.3.6.1.4.1.9.9.252.1.1.2.1
Integer32
.1.3.6.1.4.1.9.9.252.1.1.2.1.1
.1.3.6.1.4.1.9.9.252.1.1.2.1.10
Enumeration
.1.3.6.1.4.1.9.9.252.1.1.2.1.11
.1.3.6.1.4.1.9.9.252.1.1.2.1.12
.1.3.6.1.4.1.9.9.252.1.1.2.1.13
.1.3.6.1.4.1.9.9.252.1.1.2.1.2
.1.3.6.1.4.1.9.9.252.1.1.2.1.3
.1.3.6.1.4.1.9.9.252.1.1.2.1.4
.1.3.6.1.4.1.9.9.252.1.1.2.1.5
.1.3.6.1.4.1.9.9.252.1.1.2.1.6
.1.3.6.1.4.1.9.9.252.1.1.2.1.7
Integer32
.1.3.6.1.4.1.9.9.252.1.1.2.1.8
Integer32
.1.3.6.1.4.1.9.9.252.1.1.2.1.9
Bits
.1.3.6.1.4.1.9.9.252.1.1.3
.1.3.6.1.4.1.9.9.252.1.2
Bits
.1.3.6.1.4.1.9.9.252.1.2.1
.1.3.6.1.4.1.9.9.252.1.2.2
.1.3.6.1.4.1.9.9.252.1.2.2.1
Integer32
.1.3.6.1.4.1.9.9.252.1.2.2.1.1
Integer32
.1.3.6.1.4.1.9.9.252.1.2.2.1.10
Integer32
.1.3.6.1.4.1.9.9.252.1.2.2.1.11
.1.3.6.1.4.1.9.9.252.1.2.2.1.12
.1.3.6.1.4.1.9.9.252.1.2.2.1.13
.1.3.6.1.4.1.9.9.252.1.2.2.1.14
.1.3.6.1.4.1.9.9.252.1.2.2.1.15
.1.3.6.1.4.1.9.9.252.1.2.2.1.16
.1.3.6.1.4.1.9.9.252.1.2.2.1.17
.1.3.6.1.4.1.9.9.252.1.2.2.1.18
.1.3.6.1.4.1.9.9.252.1.2.2.1.19
Integer32
.1.3.6.1.4.1.9.9.252.1.2.2.1.2
.1.3.6.1.4.1.9.9.252.1.2.2.1.3
.1.3.6.1.4.1.9.9.252.1.2.2.1.4
.1.3.6.1.4.1.9.9.252.1.2.2.1.5
.1.3.6.1.4.1.9.9.252.1.2.2.1.6
.1.3.6.1.4.1.9.9.252.1.2.2.1.7
Integer32
.1.3.6.1.4.1.9.9.252.1.2.2.1.8
Integer32
.1.3.6.1.4.1.9.9.252.1.2.2.1.9
.1.3.6.1.4.1.9.9.252.1.2.3
.1.3.6.1.4.1.9.9.252.1.2.3.1
Integer32
.1.3.6.1.4.1.9.9.252.1.2.3.1.1
.1.3.6.1.4.1.9.9.252.1.2.3.1.10
.1.3.6.1.4.1.9.9.252.1.2.3.1.11
.1.3.6.1.4.1.9.9.252.1.2.3.1.12
Bits
.1.3.6.1.4.1.9.9.252.1.2.3.1.2
Integer32
.1.3.6.1.4.1.9.9.252.1.2.3.1.3
.1.3.6.1.4.1.9.9.252.1.2.3.1.4
.1.3.6.1.4.1.9.9.252.1.2.3.1.5
Integer32
.1.3.6.1.4.1.9.9.252.1.2.3.1.6
Integer32
.1.3.6.1.4.1.9.9.252.1.2.3.1.7
Integer32
.1.3.6.1.4.1.9.9.252.1.2.3.1.8
.1.3.6.1.4.1.9.9.252.1.2.3.1.9
.1.3.6.1.4.1.9.9.252.1.3
.1.3.6.1.4.1.9.9.252.1.3.1
.1.3.6.1.4.1.9.9.252.1.3.1.1
.1.3.6.1.4.1.9.9.252.1.3.1.1.1
.1.3.6.1.4.1.9.9.252.1.3.1.1.2
.1.3.6.1.4.1.9.9.252.2
.1.3.6.1.4.1.9.9.252.2.1
.1.3.6.1.4.1.9.9.252.2.2
Dependencies (10) 8 direct · 2 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Conformance Groups (7)
These objects are necessary for description of the data
streams directed to a Mediation Device.
.1.3.6.1.4.1.9.9.252.2.2.1
These objects are necessary for a description of the packets
to select for interception.
.1.3.6.1.4.1.9.9.252.2.2.2
These objects are necessary for a description of IPv4 and IPv6
packets to select for interception.
.1.3.6.1.4.1.9.9.252.2.2.3
These objects are necessary for a description of IEEE 802
packets to select for interception.
.1.3.6.1.4.1.9.9.252.2.2.4
These notifications are used to present status from the
intercepting device to the Mediation Device.
.1.3.6.1.4.1.9.9.252.2.2.5
These objects are necessary for a description of the
mediation device to select for Lawful Intercept.
.1.3.6.1.4.1.9.9.252.2.2.6
These objects are necessary for debug information.
.1.3.6.1.4.1.9.9.252.2.2.7
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.252.2.1.1
The compliance statement for entities which implement the
Cisco Intercept MIB
Required groups
Notifications / Traps (4)
NameOIDDescription
.1.3.6.1.4.1.9.9.252.0.1
This Notification is sent when an intercepting router or
switch is first capable of intercepting a packet corresponding
to a configured data stream. If the configured data stream is
an IP one, the value of the corresponding cTapStreamIpStatus
is included in this notification. If the configured data stream
is an IEEE 802 one, the value of the corresponding
cTapStream802Status is included in this notification.

This notification may be generated in conjunction with the
intercept application, which is designed to expect the
notification to be sent as reliably as possible, e.g., through
the use of a finite number of retransmissions until
acknowledged, as and when such mechanisms are available; for
example, with SNMPv3, this would be an InformRequest. Filter
installation can take a long period of time, during which call
progress may be delayed.
.1.3.6.1.4.1.9.9.252.0.2
When an intercept is autonomously removed by an intercepting
device, such as due to the time specified in
cTapMediationTimeout arriving, the device notifies the manager
of the action.
.1.3.6.1.4.1.9.9.252.0.3
When there is intervention needed due to some events related
to entries configured in cTapMediationTable, the device
notifies the manager of the event.

This notification may be generated in conjunction with the
intercept application, which is designed to expect the
notification to be sent as reliably as possible, e.g., through
the use of a finite number of retransmissions until
acknowledged, as and when such mechanisms are available; for
example, with SNMPv3, this would be an InformRequest.
.1.3.6.1.4.1.9.9.252.0.4
When there is intervention needed due to some events related
to entries configured in cTapStreamIpTable, the device
notifies the manager of the event.

This notification may be generated in conjunction with the
intercept application, which is designed to expect the
notification to be sent as reliably as possible, e.g., through
the use of a finite number of retransmissions until
acknowledged, as and when such mechanisms are available; for
example, with SNMPv3, this would be an InformRequest.