fsipv6RFC5095Compatibility
SUPERMICRO-IPV6-MIB ·
.1.3.6.1.4.1.10876.101.1.28.1.1.16
Object
scalar r/w
Enumeration
When the IPv6 node is configured to be RFC5095 compatible, then it should treat Type 0 Routing Header as invalid routing header type.
Context
- MIB
- SUPERMICRO-IPV6-MIB
- OID
.1.3.6.1.4.1.10876.101.1.28.1.1.16- Type
- scalar
- Access
- readwrite
- Status
- current
- Parent
- fsipv6Scalars
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'SUPERMICRO-IPV6-MIB' -M '/opt/observium/mibs/supermicro:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'SUPERMICRO-IPV6-MIB::fsipv6RFC5095Compatibility.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'SUPERMICRO-IPV6-MIB' -M '/opt/observium/mibs/supermicro:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'SUPERMICRO-IPV6-MIB::fsipv6RFC5095Compatibility'
Syntax
Enumeration
Values & Constraints
Enumerated Values
1 | enabled |
2 | disabled |