CISCO-USER-CONNECTION-TAP-MIB
Standard SNMP MIB module defining data structures for CISCO-USER-CONNECTION-TAP-MIB.
Imported Objects
Objects
14 total| Object Name |
|---|
ciscoUserConnectionTapMIB OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.400 |
RFC1155-SMI Unknown .1.3.6.1.4.1.9.9.400 |
cUserConnectionTapMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.400.1 |
cuctTapStreamEncodePacket OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.400.1.1 |
cuctTapStreamCapabilitiesThis object displays the types of intercepts supported on
this device. This may be dependent on hardware capabilities
or software capabilities. The value of this object is non
zero, if the device supports interception of user connection
traffic. A device may support both types of intercepts at
the same time.
The following fields may be supported:
acctSessonId: packets belonging to a user connection
identified by RADIUS attribute
account-session-ID may be intercepted.
tapEnable: set if table entries with
cTap2StreamInterceptEnable set to 'false'
are used to pre-screen packets for intercept;
otherwise these entries are ignored.ro OCTET STRING .1.3.6.1.4.1.9.9.400.1.1.1 |
cuctTapStreamTableThe Intercept Stream Connection Table lists the user
connections (sessions) 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.
This essentially provides options for packet selection.
The only option available is RADIUS attribute 44,
account session ID. When a user tries to use a service
provided by a Network Access Server(NAS) such as PPP,
NAS authenticates the user with RADIUS server. Upon
successful authentication of the user, the user is
provided with the requested service and NAS creates an
accounting record with RADIUS accounting server for
the user. The NAS assigns a unique account session id
for the user session in the accounting record created
with the RADIUS server. The account session ID may be
used to intercept traffic belonging to the user session.
The value of first index is that of an entry in the
cTap2MediationTable, which identifies the application
to which intercepted traffic will be sent to. The second
index permits connection classifiers to be used to
identify traffic to be intercepted. The value of the
second index is that of the stream's counter entry
in the cTap2StreamTable. SEQUENCE OF CuctTapStreamEntry .1.3.6.1.4.1.9.9.400.1.1.2 |
cuctTapStreamEntryA 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. CuctTapStreamEntry .1.3.6.1.4.1.9.9.400.1.1.2.1 |
cuctTapStreamAcctSessIDThis is the RADIUS attribute 44 acct-session-ID. It
identifies a user connection. It is used to specify
a user connection to intercept.rw Gauge .1.3.6.1.4.1.9.9.400.1.1.2.1.1 |
cuctTapStreamStatusThe status of this conceptual row. This object manages
creation, modification, and deletion of rows in this
table. When any rows must be changed,
cuctTapStreamStatus must be first set to
'notInService'.rw RowStatus -- Rsyntax INTEGER { -- active(1), -- notInService(2), -- notReady(3), -- createAndGo(4), -- createAndWait(5), -- destroy(6) -- } .1.3.6.1.4.1.9.9.400.1.1.2.1.2 |
cUserConnectionTapMIBConform OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.400.2 |
cUserConnectionTapMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.400.2.1 |
cUserConnectionTapMIBCompliance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.400.2.1.1 |
cUserConnectionTapMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.400.2.2 |
cuctTapStreamComplianceGroup OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.400.2.2.1 |
More MIBs from Cisco
Browse all CiscoMIBs →The CISCO-ENTITY-VENDORTYPE-OID-MIB maps Cisco-specific hardware component identifiers to the ENTITY-MIB's entPhysicalTable, enabling precise differentiation of physical device types such as line cards, power supplies, and fans within Cisco infrastructure. This mapping ensures that SNMP management systems can accurately correlate physical inventory entries with vendor-specific component definitions for accurate device discovery and monitoring.
The CISCO-UNIFIED-COMPUTING-EQUIPMENT-MIB provides SNMP-based monitoring and management of Cisco Unified Computing System (UCS) hardware components, including chassis, blades, fabric interconnects, and power supplies. It exposes critical operational metrics such as device status, port states, temperature readings, fan speeds, and power consumption data for infrastructure health assessment.
The CISCO-UNIFIED-COMPUTING-ADAPTOR-MIB enables SNMP-based monitoring and management of physical and virtual network adapter interfaces, including link status, traffic counters, error statistics, and port configuration parameters, within the Cisco Unified Computing System (UCS) fabric interconnects and blade servers.
The CISCO-UNIFIED-COMPUTING-TC-MIB module defines standard textual conventions and data type definitions required for monitoring Cisco Unified Computing System (UCS) hardware components, including server blades, fabric interconnects, and chassis resources. These definitions enable consistent interpretation of specific UCS metrics such as power supply status, fan speeds, thermal readings, and port utilization across SNMP management applications.
The CISCO-UNIFIED-COMPUTING-FABRIC-MIB enables SNMP-based monitoring and management of the Cisco UCS Fabric Interconnects and associated fabric switching infrastructure, exposing metrics for port states, link utilization, error counters, and fabric topology status. It facilitates granular visibility into the physical and logical fabric layers, including uplink/downlink interfaces, VLAN configurations, and fabric failover conditions within the unified computing environment.
The STARENT-MIB module provides SNMP management and monitoring capabilities for Cisco ASR 5000 and ASR 5500 multimedia core platforms, specifically exposing metrics related to 2G/3G/4G and WiFi subscriber sessions, inline service states, and carrier-class high-availability status.