TIMETRA-PCAP-MIB

        This document is the SNMP MIB module for the Nokia SROS implementation
of Packet Capture (PCAP).
        
Copyright 2003-2018 Nokia. All rights reserved. Reproduction of this
document is authorized on the condition that the foregoing copyright
notice is included.
        
This SNMP MIB module (Specification) embodies Nokia's proprietary
intellectual property. Nokia retains all title and ownership in the
Specification, including any revisions.
        
Nokia grants all interested parties a non-exclusive license to use and
distribute an unmodified copy of this Specification in connection with
management of Nokia products, and without fee, provided this copyright
notice and license appear on all copies.
        
This Specification is supplied 'as is', and Nokia makes no warranty,
either express or implied, as to the use, operation, condition, or
performance of the Specification.
    
Source file
TIMETRA-PCAP-MIB
Last revised
Identity
timetraPcapMIBModule
Base OID
1.3.6.1.4.1.6527.1.1.3.119
Imported Objects
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC RowStatus TimeStamp
TIMETRA-GLOBAL-MIB timetraSRMIBModules tmnxSRConfs tmnxSRNotifyPrefix tmnxSRObjs
TIMETRA-TC-MIB TLNamedItemOrEmpty TmnxDisplayStringURL TNamedItemOrEmpty
Net-SNMP examples using the nokia 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 'TIMETRA-PCAP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'TIMETRA-PCAP-MIB::timetraPcapMIBModule'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'TIMETRA-PCAP-MIB' -M '/opt/observium/mibs/nokia:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'TIMETRA-PCAP-MIB::timetraPcapMIBModule'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (30)
.1.3.6.1.4.1.6527.1.1.3.119
.1.3.6.1.4.1.6527.3.1.1.119
.1.3.6.1.4.1.6527.3.1.1.119.1
.1.3.6.1.4.1.6527.3.1.1.119.2
.1.3.6.1.4.1.6527.3.1.2.119
.1.3.6.1.4.1.6527.3.1.2.119.1
.1.3.6.1.4.1.6527.3.1.2.119.1.1
.1.3.6.1.4.1.6527.3.1.2.119.2
.1.3.6.1.4.1.6527.3.1.2.119.2.1
.1.3.6.1.4.1.6527.3.1.2.119.2.1.1
Enumeration
.1.3.6.1.4.1.6527.3.1.2.119.2.1.1.1
.1.3.6.1.4.1.6527.3.1.2.119.2.1.1.2
.1.3.6.1.4.1.6527.3.1.2.119.2.1.1.3
.1.3.6.1.4.1.6527.3.1.2.119.2.1.1.4
.1.3.6.1.4.1.6527.3.1.2.119.2.1.1.5
.1.3.6.1.4.1.6527.3.1.2.119.2.1.1.6
Enumeration
.1.3.6.1.4.1.6527.3.1.2.119.2.1.1.7
Enumeration
.1.3.6.1.4.1.6527.3.1.2.119.2.1.1.8
.1.3.6.1.4.1.6527.3.1.2.119.3
.1.3.6.1.4.1.6527.3.1.2.119.3.1
.1.3.6.1.4.1.6527.3.1.2.119.3.1.1
.1.3.6.1.4.1.6527.3.1.2.119.3.1.1.1
.1.3.6.1.4.1.6527.3.1.2.119.3.1.1.2
.1.3.6.1.4.1.6527.3.1.2.119.3.1.1.3
.1.3.6.1.4.1.6527.3.1.2.119.3.1.1.4
.1.3.6.1.4.1.6527.3.1.2.119.3.1.1.5
.1.3.6.1.4.1.6527.3.1.2.119.3.1.1.6
.1.3.6.1.4.1.6527.3.1.2.119.3.1.1.7
.1.3.6.1.4.1.6527.3.1.3.119
.1.3.6.1.4.1.6527.3.1.3.119.1
Dependencies (6) 5 direct · 1 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
  1. SNMPv2-SMIrfc
  2. SNMPv2-CONFrfc
  3. SNMPv2-TCrfc
  4. TIMETRA-GLOBAL-MIBnokia
  5. INET-ADDRESS-MIBrfc
  6. TIMETRA-TC-MIBnokia
  7. TIMETRA-PCAP-MIBnokiaselected
Compliance Statements (1)

OID .1.3.6.1.4.1.6527.3.1.1.119.1.1
The compliance statement for management of PCAPs for release 16.0 on
Nokia SROS series systems.
Required groups
Notifications / Traps (4)
NameOIDDescription
.1.3.6.1.4.1.6527.3.1.3.119.1.1
[CAUSE] A tmnxPcapFileError notification is generated when a PCAP
session encounters a capture file operation related error.

[EFFECT] The packet capture may not be uploaded to the PCAP file
anymore, or the capture may be inaccurate.

[RECOVERY] Check the file-url, and user-permissions specified. Stop
the packet capture, remove and re-configure a new file-url, and start
the capture again.
.1.3.6.1.4.1.6527.3.1.3.119.1.2
[CAUSE] A tmnxPcapBufferFull notification is generated when the PCAP
session allocated buffer is full, indicating a higher traffic rate.

[EFFECT] May result in dropping packets, if not recoverable.

[RECOVERY] The software will eventually recover when all the buffer
contents are uploaded to the capture file. No action required.
.1.3.6.1.4.1.6527.3.1.3.119.1.3
[CAUSE] A tmnxPcapBufferReadWriteFailure notification is generated
when a read or write operation to the PCAP session buffer fails.

[EFFECT] Will result in dropping packets.

[RECOVERY] The software will potentially recover. No action may be
required. However, if the problem persists stop the packet capture,
delete and re-configure a new PCAP session.
.1.3.6.1.4.1.6527.3.1.3.119.1.4
[CAUSE] A tmnxPcapSoftwareFailure notification is generated when a
software failure occurs, affecting the ability of the PCAP session to
perform its task.

[EFFECT] Will result in dropping packets.

[RECOVERY] Stop the packet capture, delete and re-configure a new PCAP
session.