RAQMON-RDS-MIB

        This is the RAQMON Data Source notification MIB Module.
It provides a mapping of RAQMON PDUs to SNMP
notifications.
        
Ds stands for data source.
        
Note that all of the object types defined in this module
are accessible-for-notify and would consequently not be
available to a browser using simple Get, GetNext, or
GetBulk requests.
        
Copyright (c) The Internet Society (2006).
        
This version of this MIB module is part of RFC 4712;
See the RFC itself for full legal notices.
    
Source file
RAQMON-RDS-MIB
Last revised
Identity
raqmonDsMIB
Base OID
1.3.6.1.2.1.16.32
Imported Objects
DIFFSERV-DSCP-TC Dscp
INET-ADDRESS-MIB InetAddress InetAddressType InetPortNumber
RMON-MIB rmon
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DateAndTime
Net-SNMP examples using the rfc 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 'RAQMON-RDS-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'RAQMON-RDS-MIB::raqmonDsMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'RAQMON-RDS-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'RAQMON-RDS-MIB::raqmonDsMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (40)
.1.3.6.1.2.1.16.32
.1.3.6.1.2.1.16.32.0
.1.3.6.1.2.1.16.32.1
.1.3.6.1.2.1.16.32.1.1
.1.3.6.1.2.1.16.32.1.1.1
.1.3.6.1.2.1.16.32.1.1.1.1
.1.3.6.1.2.1.16.32.1.1.1.10
.1.3.6.1.2.1.16.32.1.1.1.11
.1.3.6.1.2.1.16.32.1.1.1.12
.1.3.6.1.2.1.16.32.1.1.1.13
millisecondsUnsigned32
.1.3.6.1.2.1.16.32.1.1.1.14
millisecondsUnsigned32
.1.3.6.1.2.1.16.32.1.1.1.15
millisecondsUnsigned32
.1.3.6.1.2.1.16.32.1.1.1.16
.1.3.6.1.2.1.16.32.1.1.1.17
.1.3.6.1.2.1.16.32.1.1.1.18
.1.3.6.1.2.1.16.32.1.1.1.19
Unsigned32
.1.3.6.1.2.1.16.32.1.1.1.2
.1.3.6.1.2.1.16.32.1.1.1.20
.1.3.6.1.2.1.16.32.1.1.1.21
percentage of packets sentUnsigned32
.1.3.6.1.2.1.16.32.1.1.1.22
.1.3.6.1.2.1.16.32.1.1.1.23
percentage of packets sentUnsigned32
.1.3.6.1.2.1.16.32.1.1.1.24
Unsigned32
.1.3.6.1.2.1.16.32.1.1.1.25
Unsigned32
.1.3.6.1.2.1.16.32.1.1.1.26
Unsigned32
.1.3.6.1.2.1.16.32.1.1.1.27
.1.3.6.1.2.1.16.32.1.1.1.28
Unsigned32
.1.3.6.1.2.1.16.32.1.1.1.29
.1.3.6.1.2.1.16.32.1.1.1.3
.1.3.6.1.2.1.16.32.1.1.1.30
percentUnsigned32
.1.3.6.1.2.1.16.32.1.1.1.31
percentUnsigned32
.1.3.6.1.2.1.16.32.1.1.1.32
.1.3.6.1.2.1.16.32.1.1.1.4
.1.3.6.1.2.1.16.32.1.1.1.5
.1.3.6.1.2.1.16.32.1.1.1.6
.1.3.6.1.2.1.16.32.1.1.1.7
.1.3.6.1.2.1.16.32.1.1.1.8
millisecondsUnsigned32
.1.3.6.1.2.1.16.32.1.1.1.9
.1.3.6.1.2.1.16.32.2
.1.3.6.1.2.1.16.32.2.1
.1.3.6.1.2.1.16.32.2.2
Dependencies (7) 7 direct 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
Compliance Statements (1)

OID .1.3.6.1.2.1.16.32.2.1.1
The compliance statement for SNMP entities that
implement this MIB module.

There are a number of INDEX objects that cannot be
represented in the form of OBJECT clauses in SMIv2, but
for which we have the following compliance requirements,
expressed in OBJECT clause form in this description
clause:

-- OBJECT raqmonDsPeerAddrType
-- SYNTAX InetAddressType { ipv4(1), ipv6(2) }

-- DESCRIPTION
-- This MIB requires support for only global IPv4
-- and IPv6 address types.
--
-- OBJECT raqmonDsPeerAddr
-- SYNTAX InetAddress (SIZE(4|16))
-- DESCRIPTION
-- This MIB requires support for only global IPv4
-- and IPv6 address types.
--
Required groups
Notifications / Traps (3)
NameOIDDescription
.1.3.6.1.2.1.16.32.0.1
This notification maps the static parameters in the
BASIC RAQMON PDU onto an SNMP transport.
This notification is expected to be sent once per
session, or when a new sub-session is initiated.
The following objects MAY be carried by the
raqmonDsStaticNotification:

raqmonDsDataSourceDevicePort,
raqmonDsReceiverDevicePort,
raqmonDsSessionSetupDateTime,
raqmonDsSessionSetupDelay,
raqmonDsSessionDuration,
raqmonDsSourcePayloadType,
raqmonDsReceiverPayloadType,
raqmonDsSourceLayer2Priority,
raqmonDsSourceDscp,
raqmonDsDestinationLayer2Priority,
raqmonDsDestinationDscp

It is RECOMMENDED to keep the size of a notification
within the MTU size limits in order to avoid
fragmentation.
.1.3.6.1.2.1.16.32.0.2
This notification maps the dynamic parameters in the
BASIC RAQMON PDU onto an SNMP transport.

The following objects MAY be carried by the
raqmonDsDynamicNotification:

raqmonDsRoundTripEndToEndNetDelay,
raqmonDsOneWayEndToEndNetDelay,
raqmonDsApplicationDelay,
raqmonDsInterArrivalJitter,
raqmonDsIPPacketDelayVariation,
raqmonDsTotalPacketsSent,
raqmonDsTotalOctetsReceived,
raqmonDsTotalOctetsSent,
raqmonDsCumulativePacketLoss,
raqmonDsPacketLossFraction,
raqmonDsCumulativeDiscards,
raqmonDsDiscardsFraction,
raqmonDsCpuUtilization,
raqmonDsMemoryUtilization

It is RECOMMENDED to keep the size of a notification
within the MTU size limits in order to avoid
fragmentation.
.1.3.6.1.2.1.16.32.0.3
The BYE Notification. This Notification is the
equivalent of the RAQMON NULL PDU, which signals the
end of a RAQMON session.