OID reference
1.3.6.1.4.1.2076.28.1.1.16
When the IPv6 node is configured to be RFC5095 compatible, then it should treat Type 0 Routing Header as invalid routing header type.
Identification
{1 3 6 1 4 1 2076 28 1 1 16}
| Value | Name |
|---|---|
| 1 | enabled |
| 2 | disabled |
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.2076.28.1.1.16.0
Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
The displayed source records contain one distinct definition. Compare its source records.
fsipv6RFC5095Compatibility OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"When the IPv6 node is configured to be RFC5095 compatible,
then it should treat Type 0 Routing Header as invalid
routing header type."
DEFVAL {enabled}
::= { fsipv6Scalars 16 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
When the IPv6 node is configured to be RFC5095 compatible, then it should treat Type 0 Routing Header as invalid routing header type.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Belden, GarrettCom and Hirschmann IT official standalone MIBs
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: fsipv6RFC5095Compatibility
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsipv6RFC5095Compatibility",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"enabled",
"(",
"1",
")",
",",
"disabled",
"(",
"2",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"When the IPv6 node is configured to be RFC5095 compatible, then it should treat Type 0 Routing Header as invalid routing header type.\"",
"DEFVAL",
"{",
"enabled",
"}",
"::=",
"{",
"fsipv6Scalars",
"16",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"enabled",
1
],
[
"disabled",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"When the IPv6 node is configured to be RFC5095 compatible, then it should treat Type 0 Routing Header as invalid routing header type."
],
null,
null,
null,
[
"DEFVAL",
"enabled"
]
]
}Vendor MIB copy from the Observium Community archive.
Module: ARICENT-IPV6-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['RowStatus', 'TruthValue', 'DisplayString', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Counter32', 'enterprises', 'Integer32', 'Unsigned32', 'TimeTicks'], 'INET-ADDRESS-MIB': ['InetZoneIndex', 'InetScopeType']}Related source files and packages:
Module: ARICENT-IPV6-MIB
Same published definition (formatting differs; exact original is in the source file)
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Counter32', 'enterprises', 'Integer32', 'Unsigned32', 'TimeTicks'], 'INET-ADDRESS-MIB': ['InetZoneIndex', 'InetScopeType']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2076.28.1.1.1 | fsipv6NdCacheMaxRetries | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.2 | fsipv6PmtuConfigStatus | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.3 | fsipv6PmtuTimeOutInterval | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.4 | fsipv6JumboEnable | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.5 | fsipv6NumOfSendJumbo | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.6 | fsipv6NumOfRecvJumbo | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.7 | fsipv6ErrJumbo | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.8 | fsipv6GlobalDebug | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.9 | fsipv6MaxRouteEntries | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.10 | fsipv6MaxLogicalIfaces | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.11 | fsipv6MaxTunnelIfaces | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.12 | fsipv6MaxAddresses | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.13 | fsipv6MaxFragReasmEntries | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.14 | fsipv6Nd6MaxCacheEntries | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.15 | fsipv6PmtuMaxDest | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.17 | fsipv6RFC5942Compatibility | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.18 | fsipv6SENDSecLevel | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.19 | fsipv6SENDNbrSecLevel | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.20 | fsipv6SENDAuthType | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.21 | fsipv6SENDMinBits | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.22 | fsipv6SENDSecDAD | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.23 | fsipv6SENDPrefixChk | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.24 | fsipv6ECMPPRTTimer | 0 | 0 | |
| 1.3.6.1.4.1.2076.28.1.1.25 | fsipv6NdCacheTimeout | 0 | 0 |