The type of the link state advertisement. Each link state type has a separate advertisement format.
Sources for this description
NETGEAR official product and EOL MIB downloads
OID reference
1.3.6.1.4.1.4526.100.3.9.2.4.16.1.2
The type of the link state advertisement. Each link state type has a separate advertisement format.
Identification
{1 3 6 1 4 1 4526 100 3 9 2 4 16 1 2}
| Value | Name |
|---|---|
| 10 | areaOpaqueLink |
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.
In QNOS-ROUTING-MIB, the row index consists of these components in order:
agentOspfAreaOpaqueLsdbAreaId (IpAddress): four numeric subidentifiers, one per IPv4 address octet.agentOspfAreaOpaqueLsdbType (INTEGER): one numeric subidentifier for the non-negative value.agentOspfAreaOpaqueLsdbLsid (IpAddress): four numeric subidentifiers, one per IPv4 address octet.agentOspfAreaOpaqueLsdbRouterId (IpAddress): four numeric subidentifiers, one per IPv4 address octet.An instance has the form .1.3.6.1.4.1.4526.100.3.9.2.4.16.1.2.<agentOspfAreaOpaqueLsdbAreaId: four octets>.<agentOspfAreaOpaqueLsdbType>.<agentOspfAreaOpaqueLsdbLsid: four octets>.<agentOspfAreaOpaqueLsdbRouterId: four octets>. Use values present on the device and permitted by its MIB. Other definitions can differ.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.4526.100.3.9.2.4.16.1.2
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.
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.
agentOspfAreaOpaqueLsdbType OBJECT-TYPE
SYNTAX INTEGER {
areaOpaqueLink (10)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The type of the link state advertisement.
Each link state type has a separate advertisement
format."
REFERENCE
"OSPF Version 2, Appendix A.4.1 The Link State
Advertisement header"
::= { agentOspfAreaOpaqueLsdbEntry 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The type of the link state advertisement. Each link state type has a separate advertisement format.
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: agentOspfAreaOpaqueLsdbType
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"agentOspfAreaOpaqueLsdbType",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"areaOpaqueLink",
"(",
"10",
")",
"}",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The type of the link state advertisement. Each link state type has a separate advertisement format.\"",
"REFERENCE",
"\"OSPF Version 2, Appendix A.4.1 The Link State Advertisement header\"",
"::=",
"{",
"agentOspfAreaOpaqueLsdbEntry",
"2",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"areaOpaqueLink",
10
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The type of the link state advertisement. Each link state type has a separate advertisement format."
],
[
"REFERENCE",
"OSPF Version 2, Appendix A.4.1 The Link State Advertisement header"
],
null,
null,
null
]
}Module: QNOS-ROUTING-MIB
See published definition above
{'IF-MIB': ['ifIndex', 'InterfaceIndex', 'InterfaceIndexOrZero', 'InterfaceIndexOrZero'], 'OSPF-MIB': ['ospfIfEntry', 'ospfVirtIfEntry', 'ospfAreaEntry', 'RouterID'], 'VRRP-MIB': ['vrrpOperVrId'], 'SNMPv2-TC': ['RowStatus', 'TruthValue', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'IpAddress', 'Integer32', 'TimeTicks', 'Gauge32', 'Unsigned32', 'Counter32'], 'RFC1213-MIB': ['DisplayString', 'PhysAddress'], 'NETGEAR-REF-MIB': ['m4500-32c']}Related source files and packages:
Same file in mibs-m4500-32c-7.0.4.12.tar.bz2.
Same file in mibs-m4500-32c-7.0.3.9.tar.zip.
Same file in mibs-m4500-32c-7.0.3.21.tar.bz2.
Same file in mibs-m4500-32c-7.0.3.12.tar.bz2.zip.
Module: NETGEAR-ROUTING-MIB
{'IF-MIB': ['ifIndex', 'InterfaceIndex', 'InterfaceIndexOrZero', 'InterfaceIndexOrZero'], 'OSPF-MIB': ['ospfIfEntry', 'ospfVirtIfEntry', 'ospfAreaEntry', 'RouterID'], 'VRRP-MIB': ['vrrpOperVrId'], 'SNMPv2-TC': ['RowStatus', 'TruthValue', 'TEXTUAL-CONVENTION'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'IpAddress', 'Integer32', 'TimeTicks', 'Gauge32', 'Unsigned32', 'Counter32'], 'RFC1213-MIB': ['DisplayString', 'PhysAddress'], 'NETGEAR-REF-MIB': ['m4500-32c']}Related source files and packages:
Same file in mibs-m4500-32c-7.0.5.9.tar.bz2.
Same file in mibs-m4500-32c-7.0.5.6.tar.bz2.
Same file in mibs-m4500-32c-7.0.4.35.tar.bz2.
Same file in mibs-m4500-32c-7.0.4.30.tar.bz2.
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.4526.100.3.9.2.4.16.1.1 | agentOspfAreaOpaqueLsdbAreaId | 0 | 0 | |
| 1.3.6.1.4.1.4526.100.3.9.2.4.16.1.3 | agentOspfAreaOpaqueLsdbLsid | 0 | 0 | |
| 1.3.6.1.4.1.4526.100.3.9.2.4.16.1.4 | agentOspfAreaOpaqueLsdbRouterId | 0 | 0 | |
| 1.3.6.1.4.1.4526.100.3.9.2.4.16.1.5 | agentOspfAreaOpaqueLsdbSequence | 0 | 0 | |
| 1.3.6.1.4.1.4526.100.3.9.2.4.16.1.6 | agentOspfAreaOpaqueLsdbAge | 0 | 0 | |
| 1.3.6.1.4.1.4526.100.3.9.2.4.16.1.7 | agentOspfAreaOpaqueLsdbChecksum | 0 | 0 | |
| 1.3.6.1.4.1.4526.100.3.9.2.4.16.1.8 | agentOspfAreaOpaqueLsdbAdvertisement | 0 | 0 |