CISCO-TAP2-MIB: View SNMP OID List / Download 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.

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.

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.

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.

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.

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.

This object contains a value which may be used as an index value for a new cTap2MediationEntry. Whenever read, the agent will change the value to a new non-conflicting value. This is to reduce the probability of errors during creation of new cTap2MediationTable entries.

This table lists the Mediation Devices with which the intercepting device communicates. These may be on the same or different Mediation Devices. This table is written by the Mediation Device, and is always volatile. This is because intercepts may disappear during a restart of the intercepting equipment. Entries are added to this table via cTap2MediationStatus in accordance with the RowStatus convention.

The entry describes a single session maintained with an application on a Mediation Device.

cTap2MediationContentId is a session identifier, from the intercept application's perspective, and a content identifier from the Mediation Device's perspective. The Mediation Device is responsible for making sure these are unique, although the SNMP RowStatus row creation process will help by not allowing it to create conflicting entries. Before creating a new entry, a value for this variable may be obtained by reading cTap2MediationNewIndex to reduce the probability of a value collision.

The type of cTap2MediationDestAddress.

The IP Address of the Mediation Device's network interface to which to direct intercepted traffic.

The port number on the Mediation Device's network interface to which to direct intercepted traffic.

The interface on the intercepting device from which to transmit intercepted data. If zero, any interface may be used according to normal IP practice.

The port number on the intercepting device to which the Mediation Devices directs RTCP Receiver Reports and Nacks. This object is only relevant when the value of cTap2MediationTransport is 'rtpNack'. This port is assigned by the intercepting device, rather than by the Mediation Device or manager application. The value of this MIB object has no effect before activating the cTap2MediationEntry.

The Differentiated Services Code Point the intercepting device applies to the IP packets encapsulating the intercepted traffic.

If RTP with Ack/Nack resilience is selected as a transport, the mediation process requires an RTP payload type for data transmissions, and a second RTP payload type for retransmissions. This is the RTP payload type for transmissions. This object is only effective when the value of cTap2MediationTransport is 'rtpNack'.

If RTP with Ack/Nack resilience is selected as a transport, the mediation process requires an RTP payload type for data transmissions, and a second RTP payload type for retransmissions. This is the RTP payload type for retransmissions. This object is only effective when the value of cTap2MediationTransport is 'rtpNack'.

The time at which this row and all related Stream Table rows should be automatically removed, and the intercept function cease. Since the initiating network manager may be the only device able to manage a specific intercept or know of its existence, this acts as a fail-safe for the failure or removal of the network manager. The object is only effective when the value of cTap2MediationStatus is 'active'.

The protocol used in transferring intercepted data to the Mediation Device. The following protocols may be supported: udp: PacketCable udp format rtpNack: RTP with Nack resilience tcp: TCP with head of line blocking sctp: SCTP with head of line blocking rtp: Realtime Transport Protocol(RTP) packet format Enumeration: 'rtpNack': 2, 'udp': 1, 'sctp': 4, 'tcp': 3, 'rtp': 5.

This variable controls the generation of any notifications or informs by the MIB agent for this table entry.

The status of this conceptual row. This object is used to manage creation, modification and deletion of rows in this table. cTap2MediationTimeout may be modified at any time (even while the row is active). But when the row is active, the other writable objects may not be modified without setting its value to 'notInService'. The entry may not be deleted or deactivated by setting its value to 'destroy' or 'notInService' if there is any associated entry in cTap2StreamTable.

This object displays the device capabilities with respect to certain fields in Mediation Device table. This may be dependent on hardware capabilities, software capabilities. The following values may be supported: ipV4SrcInterface: SNMP ifIndex Value may be used to select the interface (denoted by cTap2MediationSrcInterface) on the intercepting device from which to transmit intercepted data to an IPv4 address Mediation Device. ipV6SrcInterface: SNMP ifIndex Value may be used to select the interface (denoted by cTap2MediationSrcInterface) on the intercepting device from which to transmit intercepted data to an IPv6 address Mediation Device. udp: UDP may be used as transport protocol (denoted by cTap2MediationTransport) in transferring intercepted data to the Mediation Device. rtcpNack: RTP with Nack resilience may be used as transport protocol (denoted by cTap2MediationTransport) in transferring intercepted data to the Mediation Device. tcp: TCP may be used as transport protocol (denoted by cTap2MediationTransport) in transferring intercepted data to the Mediation Device. sctp: SCTP may be used as transport protocol (denoted by cTap2MediationTransport) in transferring intercepted data to the Mediation Device. rtp: RTP may be used as transport protocol (denoted by cTap2MediationTransport) in transferring intercepted data to the Mediation Device. Bits: 'udp': 2, 'rtpNack': 3, 'tcp': 4, 'ipV6SrcInterface': 1, 'rtp': 6, 'ipV4SrcInterface': 0, 'sctp': 5.

The Intercept Stream Table lists the traffic streams to be intercepted. The same data stream may be required by multiple taps, and one might assume that often the intercepted stream is a small subset of the traffic that could be intercepted. The Table consists of generic fields that are independent of the type of intercept. It contains type of the specific filter which is defined in an extension MIB and counters to account for packets intercepted or dropped by the attached filter specification. Note that the Mediation Device must make sure there is only one type of specific filter created with the same indices as that of a row in this table, otherwise the later creations will fail. For example, if there is a row in this table with index 1.2, there can be a corresponding row with the same index either in citapStreamTable, c8tapStreamTable or cuctTapStreamTable, but not all. The first index indicates which Mediation Device the intercepted traffic will be diverted to. The second index permits multiple classifiers to be used together. Entries are added to this table via cTap2StreamStatus in accordance with the RowStatus convention.

A stream entry indicates a single data stream to be intercepted to a Mediation Device. Many selected data streams may go to the same application interface, and many application interfaces are supported.

The index of the stream itself.

Identifies the type of intercept filter associated to this generic stream. The following types of streams are supported: ip: The specific filter is an IP filter with same indices as that of this table. The exact filter is a row in citapStreamTable of CISCO-IP-TAP-MIB. mac: The specific filter is a MAC filter with same indices as that of this table. The exact filter is a row in c8tapStreamTable of CISCO-802-TAP-MIB. userConnecton: The specific filter is a user connection filter with same indices as that of this table. The exact filter is a row in cuctTapStreamTable of CISCO-USER-CONNECTION-TAP-MIB. msPdsn: The specific filter is a Mobile Sub connection filter with same indices as that of this table. The exact filter is a row in ccptapStreamTable of CISCO-CDMA-PDSN-TAP-MIB. mobility: The specific filter is a Mobile Subscriber connection filter with same indices as that of this table. The exact filter is a row in cmtapStreamTable of CISCO-MOBILITY-TAP-MIB. Enumeration: 'msPdsn': 4, 'ip': 1, 'mac': 2, 'mobility': 5, 'userConnection': 3.

If 'true', the tap should intercept matching traffic. The value for this object should be set to 'true' only after an additional filter specification has been attached to this stream.

The number of packets matching this data stream specification that have been intercepted.

The number of packets matching this data stream specification that, having been intercepted, were dropped in the lawful intercept process.

The status of this conceptual row. This object manages creation, modification, and deletion of rows in this table. cTap2StreamInterceptEnable may be modified any time even the value of this entry rowStatus object is 'active'. When other rows must be changed, cTap2StreamStatus must be first set to 'notInService'.

The number of packets matching this data stream specification that have been intercepted. This object is a 64-bit version of cTap2StreamInterceptedPackets.

The number of packets matching this data stream specification that, having been intercepted, were dropped in the lawful intercept process. This object is a 64-bit version of cTap2StreamInterceptDrops.

This object contains the duration in minutes for which an entry in cTap2DebugTable is maintained by the implementing device after which the entry is deleted. The management station also has the option of deleting the entry itself by setting cTap2DebugStatus.

This object contains the maximum number of debug messages maintained by the implementing device at a time. If this limit is crossed, most recent message will replace the least recent message.

A table that contains Lawful Intercept debug messages generated by the implementing device. This table is used by ciscoTap2MediationDebug and ciscoTap2StreamDebug notifications. An entry in this table contains a debug message which is regarding either a Mediation Device or a intercept stream created by a Mediation Device. The Mediation device is identified by cTap2DebugMediationId whose value is that of cTap2MediationContentId of cTapMediationEntry. The stream is identified by cTap2DebugMediationId and cTap2DebugStreamId whose values are that of cTap2MediationContentId and cTap2StreamIndex of the corresponding cTap2StreamEntry. Note that cTap2DebugStreamId may be zero for an entry, in which case the debug message is regarding a Medation Device. Entries are added to this table via cTap2DebugStatus in accordance with the RowStatus convention.

A list of the debug messages.

Index to the debug table.

The value of this object is that of cTap2MediationContentId identifying an entry in cTap2MediationTable. Note this object may contain a value for which an entry in cTap2MediationTable does not exist. This happens when creation of an entry in cTap2MediationTable fails and this debug message conveys more detailed information regarding the failure.

The value of this object is that of cTap2StreamIndex of an entry in cTap2StreamTable. This object along with cTap2DebugMediationId identifies an entry in cTap2StreamTable. The value of this object may be zero, in which this debug message is regarding a Mediation Device, but not a particular stream. Note this object may contain a value for which an entry in cTap2MediationTable does not exist. This happens when creation of an entry in cTap2StreamTable fails.

A text string contains the debug message.

The status of this conceptual row. A row in this table is created by the implementing device. A management station cannot modify any of the objects in this row, except deleting the row by setting this object to 'destroy'.

The User Table lists information of all the users configured in the system who are given permission by different Mediation Devices to access Lawful Intercept CLIs. This table will have dependancy on cTap2MediationTable. When entry in cTap2MediationTable is deleted or moved to 'notInService', entries corresponding cTap2MediationContentId in this table will be deleted.

A conceptual row in the cTap2DebugUserTable. Each row represents name of user on the router to whom Mediation Device with CCCid represented by cTap2MediationContentId has given access to Lawful Intercept commands and cTap2DebugUserTimeout represents the time when the entry will expire.

A human readable string representing the name of debug user who will have access to Lawful Intercept commands.

This object specifies the time at which the row will be removed from the table by the system. The value of this object is only effective when the value of corresponding instance of cTap2DebugUserStatus is 'active'.

This object specifies the storage type of this conceptual row. If it is set to 'nonVolatile', this entry can be saved into non-volatile memory.

The status of this conceptual row. This object manages creation, modification, and deletion of rows in this table. cTap2DebugUserTimeout may be modified any time even when the value of this entry rowStatus object is 'active'.

The compliance statement for entities which implement the Cisco Intercept MIB

The compliance statement for entities which implement the Cisco Intercept MIB. This compliance deprecates ciscoTap2MIBCompliance.

The compliance statement for entities which implement the Cisco Intercept MIB. This compliance deprecates ciscoTap2MIBComplianceRev2.

These objects are necessary for description of the data streams directed to a Mediation Device.

These objects are necessary for a description of the packets to select for interception.

These notifications are used to present status from the intercepting device to the Mediation Device.

These objects are necessary for a description of the mediation device to select for Lawful Intercept.

These objects are necessary for debug information.

These objects are required for 64 bit version of cTap2StreamInterceptedPackets and cTap2StreamInterceptDrops

These objects are necessary for debug information. This compliance group deprecates ciscoTap2DebugComplianceGroup.