Management Information Base for OSPFv3
Extracted elements (26)
Authentication was removed from OSPFv3 itself; consequently, MIB objects related to authentication are not carried forward from the OSPFv2 MIB module. IPv6-layer security mechanisms replace protocol-level authentication.
Router ID, Area ID, and Link State ID retain the OSPFv2 size of 32 bits but carry no addressing semantics in OSPFv3, so their syntax is changed to Unsigned32. The Router ID index component appears before the Link State ID in MIB indices because Router IDs are more unique, enabling more useful partial OID lookups.
Since addressing semantics were removed from router-LSAs in OSPFv3, virtual links require an administratively assigned Interface ID for advertisement in Hello packets and router-LSAs. A read-only object was added to the Virtual Interface Table to expose this assigned Interface ID.
The OSPFv3 MIB defines three separate Link State Database tables — one each for AS-scope, Area-scope, and Link-scope LSAs — reflecting OSPFv3's generalized flooding scope, which is explicitly encoded in the LSA's LS type field rather than implied by context.
Type of Service (ToS) MIB objects from the OSPFv2 MIB are not carried forward to the OSPFv3 MIB module, reflecting the removal of ToS support from OSPFv3.
SNMPv3 contexts can be used to implement MIB views supporting multiple concurrent OSPFv3 instances on the same system. See RFC 3411 for details on SNMPv3 context handling.
A single sliding-window throttle should be applied to all OSPFv3 notification types except ospfv3LsdbOverflow and ospfv3LsdbApproachingOverflow, which should not be throttled. Recommended values are 7 notifications within a 10-second window.
OSPFv3 should generate at most one notification per OSPFv3 event even when multiple unusual conditions are detected in a single packet. Only variables associated with the first unusual condition should be included in the notification.
ospfv3ExtAreaLsdbLimit MUST be set identically in all routers attached to the OSPFv3 backbone and any regular OSPFv3 area (stub areas and NSSAs are excluded). When the non-default AS-external-LSA count reaches this limit, the router enters Overflow state.
Persistent MIB objects (ospfv3RouterId, ospfv3AdminStatus, ospfv3ASBdrRtrStatus, ospfv3ExtAreaLsdbLimit, ospfv3NotificationEnable, and others) SHOULD be saved to non-volatile storage when written, so that configuration survives a restart.
To avoid a flood of expected startup notifications, a router should not originate ospfv3IfStateChange, ospfv3VirtIfStateChange, ospfv3NbrStateChange, or ospfv3VirtNbrStateChange notifications until two dead timer intervals have elapsed after OSPFv3 is enabled on an interface.
ospfv3DiscontinuityTime records the sysUpTime value at the most recent counter discontinuity event such as an OSPFv3 process restart. Management entities reading MIB counters should consult this object to determine whether counter values remain valid.
ospfv3ExitOverflowInterval specifies in seconds how long after entering Overflow state before the router attempts to leave it and re-originate non-default AS-External-LSAs. A value of 0 means the router will not leave Overflow state until restarted.
ospfv3ExtAreaLsdbLimit is a persistent read-write Integer32 (-1 to 0x7FFFFFFF) bounding the number of non-default AS-external-LSAs in the LSDB. A value of -1 means no limit. The router enters Overflow state at the limit and will not hold more than the configured maximum.
ospfv3IfInstId (Unsigned32, 0..255) enables multiple OSPFv3 interface instances to run over a single link. Each instance is assigned a separate locally significant ID, indexed alongside ospfv3IfIndex in the Interface Table.
ospfv3NotificationEnable is a persistent read-write TruthValue providing coarse on/off control over all OSPFv3 notification generation. Fine-grained per-notification control is available through RFC 3413 notification management objects.
ospfv3ReferenceBandwidth is a persistent read-write Unsigned32 (in kbps, default 100,000 / 100 Mbps) used as the reference value for calculating default OSPFv3 interface metrics; it should be configured consistently across the routing domain.
ospfv3RouterId is a persistent read-write Unsigned32 (Ospfv3RouterIdTC, range 1..0xFFFFFFFF) uniquely identifying the router in the AS. It may default to a 32-bit representation of an IPv4 interface address when IPv4 is configured; otherwise it must be assigned by another method.
The ospfv3AreaTable is indexed solely by ospfv3AreaId (Unsigned32) and includes ospfv3AreaImportAsExtern to classify areas as normal, stub, or NSSA; ospfv3AreaNssaTranslatorRole (always or candidate); ospfv3AreaTEEnabled; and ospfv3AreaScopeLsaCksumSum for LSDB integrity comparison.
The OSPFv3 MIB module is assigned OID { mib-2 191 }, placing ospfv3MIB under the standard MIB-2 subtree. This is the initial version of the module, published as RFC 5643.
The OSPFv3 MIB exposes read-write objects that can alter routing behavior (e.g., ospfv3AdminStatus, ospfv3ExtAreaLsdbLimit, ospfv3ASBdrRtrStatus); unauthorized modification could destabilize a routing domain. Because OSPFv3 authentication is handled at the IPv6 layer rather than in the MIB, SNMPv3 access controls are required to protect sensitive writable objects.
Graceful restart states exposed via ospfv3RestartStatus are: notRestarting, plannedRestart, and unplannedRestart. ospfv3RestartExitReason records the outcome of the last attempt: none, inProgress, completed, timedOut, or topologyChanged.
NSSA translator state (ospfv3AreaNssaTranslatorState) transitions among: enabled (role is 'always'), elected (candidate router is actively translating NSSA-LSAs to AS-External-LSAs), and disabled (candidate router is not translating). Transition events are counted in ospfv3AreaNssaTranslatorEvents.
Ospfv3IfInstIdTC encodes the OSPFv3 Interface Instance ID as an Unsigned32 in the range 0..255, with local link significance only, enabling multiple OSPFv3 instances to operate over a single link.
Ospfv3LsaAgeTC encodes LSA age as an Unsigned32 with valid ranges 0..3600 or 32768..36368 seconds. The high-order bit (32768) serves as the DoNotAge bit for on-demand circuit support.
Ospfv3LsaSequenceTC encodes the LSA sequence number as a signed 32-bit integer (Integer32), starting at 0x80000001 and incrementing to 0x7FFFFFFF. A larger value indicates a more recent advertisement; the space is linearly ordered.