ARICENT-DHCPv6-RELAY-MIB
This MIB is a proprietary MIB for Stateless-DHCPv6 relay
and conforms to RFC 3736(04/2004).
- Source file
ARICENT-DHCPv6-RELAY-MIB- Last revised
- Identity
fsdhcpv6rly- Base OID
1.3.6.1.4.1.29601.2.41
Imported Objects
| SNMPv2-SMI | Counter32 enterprises Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) |
| SNMPv2-TC | DisplayString RowStatus TruthValue |
Net-SNMP examples using the aricent 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 'ARICENT-DHCPv6-RELAY-MIB' -M '/opt/observium/mibs/aricent:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ARICENT-DHCPv6-RELAY-MIB::fsdhcpv6rly'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ARICENT-DHCPv6-RELAY-MIB' -M '/opt/observium/mibs/aricent:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ARICENT-DHCPv6-RELAY-MIB::fsdhcpv6rly'
Objects (41)
Showing 41 of 41 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.29601.2.41 |
||
.1.3.6.1.4.1.29601.2.41.0 |
||
.1.3.6.1.4.1.29601.2.41.1 |
||
|
OctetString
|
.1.3.6.1.4.1.29601.2.41.1.1 |
|
|
Bits
|
.1.3.6.1.4.1.29601.2.41.1.2 |
|
|
Enumeration
|
.1.3.6.1.4.1.29601.2.41.1.3 |
|
|
Integer32
|
.1.3.6.1.4.1.29601.2.41.1.4 |
|
|
Integer32
|
.1.3.6.1.4.1.29601.2.41.1.5 |
|
|
Integer32
|
.1.3.6.1.4.1.29601.2.41.1.6 |
|
|
Enumeration
|
.1.3.6.1.4.1.29601.2.41.1.7 |
|
|
Enumeration
|
.1.3.6.1.4.1.29601.2.41.1.8 |
|
.1.3.6.1.4.1.29601.2.41.2 |
||
.1.3.6.1.4.1.29601.2.41.2.1 |
||
.1.3.6.1.4.1.29601.2.41.2.1.1 |
||
|
Integer32
|
.1.3.6.1.4.1.29601.2.41.2.1.1.1 |
|
.1.3.6.1.4.1.29601.2.41.2.1.1.10 |
||
.1.3.6.1.4.1.29601.2.41.2.1.1.11 |
||
.1.3.6.1.4.1.29601.2.41.2.1.1.12 |
||
|
Enumeration
|
.1.3.6.1.4.1.29601.2.41.2.1.1.13 |
|
|
OctetString
|
.1.3.6.1.4.1.29601.2.41.2.1.1.14 |
|
|
OctetString
|
.1.3.6.1.4.1.29601.2.41.2.1.1.15 |
|
|
OctetString
|
.1.3.6.1.4.1.29601.2.41.2.1.1.16 |
|
.1.3.6.1.4.1.29601.2.41.2.1.1.17 |
||
.1.3.6.1.4.1.29601.2.41.2.1.1.18 |
||
|
Enumeration
|
.1.3.6.1.4.1.29601.2.41.2.1.1.19 |
|
|
Integer32
|
.1.3.6.1.4.1.29601.2.41.2.1.1.3 |
|
.1.3.6.1.4.1.29601.2.41.2.1.1.4 |
||
.1.3.6.1.4.1.29601.2.41.2.1.1.5 |
||
.1.3.6.1.4.1.29601.2.41.2.1.1.6 |
||
.1.3.6.1.4.1.29601.2.41.2.2 |
||
.1.3.6.1.4.1.29601.2.41.2.2.1 |
||
|
Integer32
|
.1.3.6.1.4.1.29601.2.41.2.2.1.1 |
|
|
OctetString
|
.1.3.6.1.4.1.29601.2.41.2.2.1.2 |
|
.1.3.6.1.4.1.29601.2.41.2.2.1.3 |
||
.1.3.6.1.4.1.29601.2.41.2.3 |
||
.1.3.6.1.4.1.29601.2.41.2.3.1 |
||
|
Integer32
|
.1.3.6.1.4.1.29601.2.41.2.3.1.1 |
|
.1.3.6.1.4.1.29601.2.41.2.3.1.2 |
||
.1.3.6.1.4.1.29601.2.41.3 |
||
.1.3.6.1.4.1.29601.2.41.3.1 |
||
.1.3.6.1.4.1.29601.2.41.3.2 |
Dependencies (2) 2 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
Dependency-first compile order
- SNMPv2-SMIrfc
- SNMPv2-TCrfc
- ARICENT-DHCPv6-RELAY-MIBaricentselected
Notifications / Traps (2)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.29601.2.41.0.1 |
This trap is generated when received Message is Invalid.
|
|
.1.3.6.1.4.1.29601.2.41.0.2 |
This trap is generated when relay agent is not able to
add the relay header because the received hop count value is equal to the configured hop count value. |