OID reference
1.3.6.1.4.1.89.216.4.1.4
The Link State ID is an LS type-specific field containing a unique identifier; it identifies the piece of the routing domain that is being described by the advertisement. In contrast to OSPFv2, the LSID has no addressing semantics.
Identification
{1 3 6 1 4 1 89 216 4 1 4}
Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.
Product context
The NETGEAR catalogue lists MIB files containing this definition with these product and release labels:
These are catalogue release labels, not necessarily MIB revisions. A MIB definition does not establish that a device implements it or permits access.
The displayed source records contain one distinct definition. Compare its source records.
rlOspfv3AsLsdbLsid OBJECT-TYPE
SYNTAX RlLsID
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The Link State ID is an LS type-specific field
containing a unique identifier;
it identifies the piece of the routing domain
that is being described by the advertisement.
In contrast to OSPFv2, the LSID has no
addressing semantics."
::= { rlOspfv3AsLsdbEntry 4 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The Link State ID is an LS type-specific field containing a unique identifier; it identifies the piece of the routing domain that is being described by the advertisement. In contrast to OSPFv2, the LSID has no addressing semantics.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)NETGEAR official product and EOL MIB downloads
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: rlOspfv3AsLsdbLsid
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rlOspfv3AsLsdbLsid",
"OBJECT-TYPE",
"SYNTAX",
"RlLsID",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"The Link State ID is an LS type-specific field containing a unique identifier; it identifies the piece of the routing domain that is being described by the advertisement. In contrast to OSPFv2, the LSID has no addressing semantics.\"",
"::=",
"{",
"rlOspfv3AsLsdbEntry",
"4",
"}"
],
"syntax_tree": [
[
"row",
"RlLsID"
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The Link State ID is an LS type-specific field containing a unique identifier; it identifies the piece of the routing domain that is being described by the advertisement. In contrast to OSPFv2, the LSID has no addressing semantics."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: RADLAN-OSPFV3-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'OSPF-MIB': ['AreaID', 'RouterID', 'Metric', 'BigMetric', 'Status', 'PositiveInteger', 'UpToMaxAge', 'TOSType', 'OspfAuthenticationType', 'HelloRange', 'DesignatedRouterPriority'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'TimeStamp', 'DisplayString'], 'OSPFV3-MIB': ['Ospfv3UpToRefreshIntervalTC', 'Ospfv3DeadIntervalRangeTC', 'Ospfv3RouterIdTC', 'Ospfv3LsIdTC', 'Ospfv3AreaIdTC', 'Ospfv3IfInstIdTC', 'Ospfv3LsaSequenceTC', 'Ospfv3LsaAgeTC'], 'RADLAN-MIB': ['rnd'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'mib-2', 'Counter32', 'Gauge32', 'Integer32', 'Unsigned32', 'IpAddress'], 'RFC1213-MIB': ['mib-2'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'RADLAN-OSPF-MIB': ['RlOspfProcessID', 'RlOspfFastHelloMultiplierRange', 'RlOspfRestartHelperStatus', 'RlOspfRestartExitReason', 'RlOspfRouterIdType'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetAddressPrefixLength', 'InetAddressIPv6']}Related source files and packages:
Module: RADLAN-OSPFV3-MIB
{'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'OSPF-MIB': ['AreaID', 'RouterID', 'Metric', 'BigMetric', 'Status', 'PositiveInteger', 'UpToMaxAge', 'TOSType', 'OspfAuthenticationType', 'HelloRange', 'DesignatedRouterPriority'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'TimeStamp', 'DisplayString'], 'OSPFV3-MIB': ['Ospfv3UpToRefreshIntervalTC', 'Ospfv3DeadIntervalRangeTC', 'Ospfv3RouterIdTC', 'Ospfv3LsIdTC', 'Ospfv3AreaIdTC', 'Ospfv3IfInstIdTC', 'Ospfv3LsaSequenceTC', 'Ospfv3LsaAgeTC'], 'RADLAN-MIB': ['rnd'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'mib-2', 'Counter32', 'Gauge32', 'Integer32', 'Unsigned32', 'IpAddress'], 'RFC1213-MIB': ['mib-2'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'RADLAN-OSPF-MIB': ['RlOspfProcessID', 'RlOspfFastHelloMultiplierRange', 'RlOspfRestartHelperStatus', 'RlOspfRestartExitReason', 'RlOspfRouterIdType'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetAddressPrefixLength', 'InetAddressIPv6']}Related source files and packages:
Same file in MX510TX_MS510TXPP_MIBS_ODM_V6.7.0.42.zip.
Same file in MS510TX_TXPP_V6.7.0.37_MIB_V6.7.0.37.zip.
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.89.216.4.1.1 | rlOspfv3AsLsdbProcessId | 0 | 0 | |
| 1.3.6.1.4.1.89.216.4.1.2 | rlOspfv3AsLsdbType | 0 | 0 | |
| 1.3.6.1.4.1.89.216.4.1.3 | rlOspfv3AsLsdbRouterId | 0 | 0 | |
| 1.3.6.1.4.1.89.216.4.1.5 | rlOspfv3AsLsdbSequence | 0 | 0 | |
| 1.3.6.1.4.1.89.216.4.1.6 | rlOspfv3AsLsdbAge | 0 | 0 | |
| 1.3.6.1.4.1.89.216.4.1.7 | rlOspfv3AsLsdbChecksum | 0 | 0 | |
| 1.3.6.1.4.1.89.216.4.1.8 | rlOspfv3AsLsdbAdvertisement | 0 | 0 | |
| 1.3.6.1.4.1.89.216.4.1.9 | rlOspfv3AsLsdbTypeKnown | 0 | 0 |