OID reference
1.3.6.1.4.1.29601.2.35.1.10.1.19
Zone-Id shoule be able to identify a particular zone of the address's scope. This Zone id applies to all kinds of unicast and multicast addresses of non-global scope except the unspecified address. The zone-id is not supported for global address.
Identification
{1 3 6 1 4 1 29601 2 35 1 10 1 19}
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.
fsMIIpv6PingZoneId OBJECT-TYPE
SYNTAX DisplayString
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Zone-Id shoule be able to identify a particular zone
of the address's scope. This Zone id applies
to all kinds of unicast and multicast addresses of
non-global scope except the unspecified address.
The zone-id is not supported for global address."
REFERENCE "RFC4007"
::= { fsMIIpv6PingEntry 19 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Zone-Id shoule be able to identify a particular zone of the address's scope. This Zone id applies to all kinds of unicast and multicast addresses of non-global scope except the unspecified address. The zone-id is not supported for global address.
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: fsMIIpv6PingZoneId
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsMIIpv6PingZoneId",
"OBJECT-TYPE",
"SYNTAX",
"DisplayString",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Zone-Id shoule be able to identify a particular zone of the address's scope. This Zone id applies to all kinds of unicast and multicast addresses of non-global scope except the unspecified address. The zone-id is not supported for global address.\"",
"REFERENCE",
"\"RFC4007\"",
"::=",
"{",
"fsMIIpv6PingEntry",
"19",
"}"
],
"syntax_tree": [
[
"row",
"DisplayString"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Zone-Id shoule be able to identify a particular zone of the address's scope. This Zone id applies to all kinds of unicast and multicast addresses of non-global scope except the unspecified address. The zone-id is not supported for global address."
],
[
"REFERENCE",
"RFC4007"
],
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: ARICENT-MIIPV6-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['DisplayString', 'RowStatus', 'TEXTUAL-CONVENTION', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Counter32', 'Unsigned32', 'TimeTicks', 'enterprises'], 'INET-ADDRESS-MIB': ['InetZoneIndex', 'InetScopeType'], 'ARICENT-MISTD-IPVX-MIB': ['fsMIStdIpContextId', 'fsMIStdIpv6InterfaceEntry', 'fsMIStdIpv6InterfaceIfIndex', 'fsMIStdIpIfStatsIfIndex']}Related source files and packages:
Module: ARICENT-MIIPV6-MIB
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['RowStatus'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Counter32', 'Unsigned32', 'TimeTicks', 'enterprises'], 'INET-ADDRESS-MIB': ['InetZoneIndex', 'InetScopeType'], 'ARICENT-MISTD-IPVX-MIB': ['fsMIStdIpContextId', 'fsMIStdIpv6InterfaceEntry', 'fsMIStdIpv6InterfaceIfIndex', 'fsMIStdIpIfStatsIfIndex']}Related source files and packages:
Registration