CISCO-TAP2-MIB
This module manages Cisco's intercept feature.
This MIB replaces CISCO-TAP-MIB. This MIB defines
a generic stream table that contains fields common to
all intercept types. Specific intercept filters are
defined in extension MIBs. They are CISCO-IP-TAP-MIB
for IP intercepts, CISCO-802-TAP-MIB for IEEE 802
intercepts and CISCO-USER-CONNECTION-TAP-MIB for
RADIUS-based user connection intercepts.
- Source file
CISCO-TAP2-MIB- Last revised
- Identity
ciscoTap2MIB- Base OID
1.3.6.1.4.1.9.9.399
Imported Objects
| CISCO-SMI | ciscoMgmt |
| IF-MIB | InterfaceIndexOrZero |
| INET-ADDRESS-MIB | InetAddress 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 Counter64 Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32 |
| SNMPv2-TC | DateAndTime RowStatus StorageType TEXTUAL-CONVENTION (no object page) 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-TAP2-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-TAP2-MIB::ciscoTap2MIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-TAP2-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-TAP2-MIB::ciscoTap2MIB'
Objects (51)
Showing 51 of 51 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.9.9.399 |
||
.1.3.6.1.4.1.9.9.399.0 |
||
.1.3.6.1.4.1.9.9.399.1 |
||
.1.3.6.1.4.1.9.9.399.1.1 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.399.1.1.1 |
|
.1.3.6.1.4.1.9.9.399.1.1.2 |
||
.1.3.6.1.4.1.9.9.399.1.1.2.1 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.399.1.1.2.1.1 |
|
.1.3.6.1.4.1.9.9.399.1.1.2.1.10 |
||
|
Enumeration
|
.1.3.6.1.4.1.9.9.399.1.1.2.1.11 |
|
.1.3.6.1.4.1.9.9.399.1.1.2.1.12 |
||
.1.3.6.1.4.1.9.9.399.1.1.2.1.13 |
||
.1.3.6.1.4.1.9.9.399.1.1.2.1.2 |
||
.1.3.6.1.4.1.9.9.399.1.1.2.1.3 |
||
.1.3.6.1.4.1.9.9.399.1.1.2.1.4 |
||
.1.3.6.1.4.1.9.9.399.1.1.2.1.5 |
||
.1.3.6.1.4.1.9.9.399.1.1.2.1.6 |
||
.1.3.6.1.4.1.9.9.399.1.1.2.1.7 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.399.1.1.2.1.8 |
|
|
Integer32
|
.1.3.6.1.4.1.9.9.399.1.1.2.1.9 |
|
|
Bits
|
.1.3.6.1.4.1.9.9.399.1.1.3 |
|
.1.3.6.1.4.1.9.9.399.1.2 |
||
.1.3.6.1.4.1.9.9.399.1.2.1 |
||
.1.3.6.1.4.1.9.9.399.1.2.1.1 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.399.1.2.1.1.1 |
|
|
|
Enumeration
|
.1.3.6.1.4.1.9.9.399.1.2.1.1.2 |
.1.3.6.1.4.1.9.9.399.1.2.1.1.3 |
||
.1.3.6.1.4.1.9.9.399.1.2.1.1.4 |
||
.1.3.6.1.4.1.9.9.399.1.2.1.1.5 |
||
.1.3.6.1.4.1.9.9.399.1.2.1.1.6 |
||
.1.3.6.1.4.1.9.9.399.1.2.1.1.7 |
||
.1.3.6.1.4.1.9.9.399.1.2.1.1.8 |
||
.1.3.6.1.4.1.9.9.399.1.3 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.399.1.3.1 |
|
|
Integer32
|
.1.3.6.1.4.1.9.9.399.1.3.2 |
|
.1.3.6.1.4.1.9.9.399.1.3.3 |
||
.1.3.6.1.4.1.9.9.399.1.3.3.1 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.399.1.3.3.1.1 |
|
.1.3.6.1.4.1.9.9.399.1.3.3.1.2 |
||
.1.3.6.1.4.1.9.9.399.1.3.3.1.3 |
||
.1.3.6.1.4.1.9.9.399.1.3.3.1.4 |
||
|
|
.1.3.6.1.4.1.9.9.399.1.3.3.1.5 |
|
.1.3.6.1.4.1.9.9.399.1.3.4 |
||
.1.3.6.1.4.1.9.9.399.1.3.4.1 |
||
|
OctetString
|
.1.3.6.1.4.1.9.9.399.1.3.4.1.1 |
|
.1.3.6.1.4.1.9.9.399.1.3.4.1.2 |
||
.1.3.6.1.4.1.9.9.399.1.3.4.1.3 |
||
.1.3.6.1.4.1.9.9.399.1.3.4.1.4 |
||
.1.3.6.1.4.1.9.9.399.2 |
||
.1.3.6.1.4.1.9.9.399.2.1 |
||
.1.3.6.1.4.1.9.9.399.2.2 |
Dependencies (9) 7 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
Dependency-first compile order
- SNMPv2-SMIrfc
- CISCO-SMIcisco
- SNMPv2-TCrfc
- IANAifType-MIBrfc
- SNMPv2-CONFrfc
- SNMPv2-MIBrfc
- IF-MIBrfc
- INET-ADDRESS-MIBrfc
- SNMP-FRAMEWORK-MIBrfc
- CISCO-TAP2-MIBciscoselected
Type Definitions (1)
| Integer32 |
range: 0..63 |
Conformance Groups (7)
|
cTap2MediationNewIndex cTap2MediationDestAddressType cTap2MediationDestAddress cTap2MediationDestPort cTap2MediationSrcInterface cTap2MediationRtcpPort cTap2MediationDscp cTap2MediationDataType cTap2MediationRetransmitType cTap2MediationTimeout cTap2MediationTransport cTap2MediationNotificationEnable cTap2MediationStatus
These objects are necessary for description of the data
streams directed to a Mediation Device. |
.1.3.6.1.4.1.9.9.399.2.2.1
|
|
|
cTap2StreamType cTap2StreamInterceptEnable cTap2StreamInterceptedPackets cTap2StreamInterceptDrops cTap2StreamStatus
These objects are necessary for a description of the packets
to select for interception. |
.1.3.6.1.4.1.9.9.399.2.2.2
|
|
|
ciscoTap2MIBActive ciscoTap2MediationTimedOut ciscoTap2MediationDebug ciscoTap2StreamDebug ciscoTap2Switchover
These notifications are used to present status from the
intercepting device to the Mediation Device. |
.1.3.6.1.4.1.9.9.399.2.2.3
|
|
|
These objects are necessary for a description of the
mediation device to select for Lawful Intercept. |
.1.3.6.1.4.1.9.9.399.2.2.4
|
|
|
ciscoTap2DebugComplianceGroup
deprecated
|
cTap2DebugAge cTap2DebugMaxEntries cTap2DebugMediationId cTap2DebugStreamId cTap2DebugMessage cTap2DebugStatus
These objects are necessary for debug information.
|
.1.3.6.1.4.1.9.9.399.2.2.5
|
|
These objects are required for 64 bit version of
cTap2StreamInterceptedPackets and cTap2StreamInterceptDrops |
.1.3.6.1.4.1.9.9.399.2.2.6
|
|
|
cTap2DebugAge cTap2DebugMaxEntries cTap2DebugMediationId cTap2DebugStreamId cTap2DebugMessage cTap2DebugStatus cTap2DebugUserTimeout cTap2DebugUserStorageType cTap2DebugUserStatus
These objects are necessary for debug information.
This compliance group deprecates ciscoTap2DebugComplianceGroup. |
.1.3.6.1.4.1.9.9.399.2.2.7
|
Compliance Statements (3)
OID
.1.3.6.1.4.1.9.9.399.2.1.1The compliance statement for entities which implement the
Cisco Intercept MIB
Cisco Intercept MIB
Required groups
| mandatory | ciscoTap2MediationComplianceGroup | |
| mandatory | ciscoTap2StreamComplianceGroup | |
| mandatory | ciscoTap2MediationCpbComplianceGroup | |
| mandatory | ciscoTap2NotificationGroup |
OID
.1.3.6.1.4.1.9.9.399.2.1.2The compliance statement for entities which implement the
Cisco Intercept MIB. This compliance deprecates
ciscoTap2MIBCompliance.
Cisco Intercept MIB. This compliance deprecates
ciscoTap2MIBCompliance.
Required groups
| mandatory | ciscoTap2MediationComplianceGroup | |
| mandatory | ciscoTap2StreamComplianceGroup | |
| mandatory | ciscoTap2MediationCpbComplianceGroup | |
| mandatory | ciscoTap2NotificationGroup | |
| mandatory | ciscoTap2StreamHCStatsGroup |
OID
.1.3.6.1.4.1.9.9.399.2.1.3The compliance statement for entities which implement the
Cisco Intercept MIB. This compliance deprecates
ciscoTap2MIBComplianceRev2.
Cisco Intercept MIB. This compliance deprecates
ciscoTap2MIBComplianceRev2.
Required groups
| mandatory | ciscoTap2MediationComplianceGroup | |
| mandatory | ciscoTap2StreamComplianceGroup | |
| mandatory | ciscoTap2MediationCpbComplianceGroup | |
| mandatory | ciscoTap2NotificationGroup | |
| mandatory | ciscoTap2StreamHCStatsGroup | |
| mandatory | ciscoTap2DebugComplianceGroupRev1 |
Notifications / Traps (5)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.9.9.399.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. The value of the corresponding cTap2StreamType which identifies the actual intercept stream type 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.399.0.2 |
When an intercept is autonomously removed by an intercepting
device, such as due to the time specified in cTap2MediationTimeout arriving, the device notifies the manager of the action. |
|
.1.3.6.1.4.1.9.9.399.0.3 |
When there is intervention needed due to some events related
to entries configured in cTap2MediationTable, 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.399.0.4 |
When there is intervention needed due to some events related
to entries configured in cTap2StreamTable, 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.399.0.5 |
This notification is sent when there is a redundant (standby)
route processor available on the intercepting device and the current active processor is going down causing standby to takeover. Note that this notification may be sent by the intercepting device only when it had a chance to know before it goes down. Mediation device when received this notification should assume that configured intercepts on the intercepting device no longer exist, when the standby processor takes control. This means that the Mediation device should again configure the intercepts. |