ENTERASYS-OSPF-EXT-MIB: View SNMP OID List / Download MIB

This MIB module defines a portion of the SNMP MIB under the Enterasys Networks enterprise OID pertaining to the OSPF configuration. This MIB was designed to be used in conjunction with the OSPF-MIB (RFC 4750) for configuring the OSPF protocol parameters.

The current operational state of the OSPF Protocol. Changing the state of the ospfAdminStat object effects the state of this object. If ospfAdminStat is set to 'disabled', this object's status is changed to 'operStatusGoingDown'. Once all of the resources have been reclaimed, the status is changed to 'operStatusDown'. If ospfAdminStat is set to 'enabled', this object's status is changed to 'operStatusGoingUp'. When the OSPF protocol has finished the activation process, the state of this object changes to 'operStatusUp'. If there are problems activating the OSPF protocol, the status becomes 'operStatusActFailed'.

The maximum delay before the Routing Table is recalculated following a change to the Link State Database. (Recalculation is delayed to reduce the frequency of recalculations of the Routing Table). This parameter has units of milliseconds. A value of 0 indicates that a routing calculation will immediately follow an update to the database.

This parameter can be used to override the etsysOspfExtCalcMaxDelay when the number of updates to the Link State Database reaches a threshold value. -1 Indicates that this threshold is infinite, and hence the timing of a routing calculation is determined solely by etsysOspfExtCalcMaxDelay. 0 Indicates that a routing calculation will immediately follow an update to the database. 1..2147483647 Specifies the threshold number of updates that can be made to the Link State Database such that any subsequent update to the database causes a full routing calculation to start immediately.

This parameter can be used to interrupt a full routing calculation when the number of pending updates to the Link State Database has reached a threshold value. -1 Indicates that this threshold is infinite, and hence no number of pending updates to the database will cause a routing calculation to be interrupted. 0 Indicates that an update to the Link State Database will cause any current routing calculation to be interrupted and a new one to start. 1..2147483647 Specifies the threshold number of updates that can be made to the Link State Database such that any subsequent update to the database causes the current routing calculation to be interrupted, and a new calculation to start using an up to date Link State Database.

This parameter can be used to optimize the performance of the Routing Calculator in the situation where updates that are pending to the Link State Database solely concern inter-area or AS-external routes. In this case, the Routing Table can be updated either by one full recalculation, or by multiple incremental recalculations. This parameter is used to configure the threshold value for which recalculation by multiple incremental updates is no longer quicker than a single full recalculation. -1 Indicates that this threshold is infinite, and incremental recalculations are always done in preference to a full recalculation. 0 Indicates that incremental updates will never be used. 1..2147483647 (n) Indicates that a full recalculation will be performed whenever there are more than 'n' updates to make to inter-area or AS-external routes.

This parameter can be used to optimize the performance of the Routing Calculator in the situation where updates that are pending to the Link State Database concern intra-area routes. In this case, the Routing Table can be updated either by one full recalculation, or by multiple incremental SPF recalculations. This parameter is used to configure the threshold value for which recalculation by multiple incremental SPF updates is no longer quicker than a single full recalculation. -1 Indicates that this threshold is infinite, and incremental SPF recalculations are always done in preference to a full recalculation. 0 Indicates that incremental SPF updates will never be used. 1..2147483647 (n) Indicates that a full recalculation will be performed whenever there are more than 'n' updates to make to intra-area routes.

This value determines how regularly a Routing Calculation is paused. It is measured in points. The points scale roughly maps to a time scale, so that the larger this value is, the longer the Routing Calculation runs before pausing. -1 Indicates that the Routing Calculation is never paused. 0 Indicates that the routing calculation is paused after every calculation step.

The maximum number of equal cost paths that are stored for each destination in the Routing Table.

This value determines how often the checksums of LSAs in the Link State Database are checked. If 0, no checksums in the database are checked.

Self-originated LSAs are periodically reflooded into the routing domain to add to the robustness of the OSPF protocol. This value determines the interval between refreshes of type-5 and type-11 AS-external LSAs, and is defaulted to the OSPF standard default of 1800 seconds (30 minutes).

The number of type-11 LSAs in the external database.

The 32 bit sum of LS checksums of all type-11 LSAs in the external Link State Database.

The number of updates that are pending addition to the Link State Database.

The number of updates that have been merged into the Link State Database since the last routing calculation.

The number of LSAs in the Link State Database which are now due to have their checksum checked.

Indicates whether OSPF should perform hitless restart using grace LSAs. If OSPF is being deactivated, grace LSAs are sent out to inform neighboring routers that we wish to undergo a hitless restart. If OSPF is being activated, we will attempt to restart hitlessly, then set this field to 'false'. Therefore this field needs to be explicitly set to 'true' each time planned hitless restart is required. This object is persistent and when written the entity SHOULD save the change to non-volatile storage.

Indicates whether OSPF should perform an unplanned hitless restart using grace LSAs. Note that etsysOspfExtDoGraceHitless has a higher priority than this object. Therefore if both etsysOspfExtDoGraceHitless and this object are both set to 'true' on activation, OSPF will assume it is undergoing a planned hitless restart. If only this object is 'true', then OSPF will attempt an unplanned hitless restart, and send out grace LSAs on activation.

If OSPF is attempting to undergo a hitless restart, this field specifies the length of grace period that should be requested from adjacent routers in grace LSAs. After this timer period has passed, an RTM will delete routes from this RPM from its routing table, and so hitless restart will have failed. Hitless grace period must be greater than zero.

This table provides additional information pertaining to OSPF Areas for Enterasys OSPF systems.

An entry (conceptual row) in the etsysOspfExtAreaTable.

The desired administrative state of this OSPF area. When the status of this object is set to 'disabled', no flooding will occur for routes in this area and all routes for this area are removed from the RIB. When the status of this object is set to 'enabled', flooding occurs for this area, and routes are added to the RIB. This object needs to be 'disabled' in order to modify the ospfImportAsExtern object.

The current operational state of this OSPF area.

This parameter indicates whether the area can carry data traffic that neither originates nor terminates in the area itself. This parameter is calculated when the area's shortest-path tree is built.

Self-originated LSAs are periodically reflooded into the routing domain, to add to the robustness of the OSPF protocol. This value determines the interval between refreshes of LSAs in this area, and is defaulted to the OSPF standard default of 1800 seconds (30 minutes).

The number of LSAs with LS type-1 in this area's Link State Database.

The 32 bit sum of LS checksums of all LSAs with LS type-1 in this area's Link State Database.

The number of LSAs with LS type-2 in this area's Link State Database.

The 32 bit sum of LS checksums of all LSAs with LS type-2 in this area's Link State Database.

The number of LSAs with LS type-3 in this area's Link State Database.

The 32 bit sum of LS checksums of all LSAs with LS type-3 in this area's Link State Database.

The number of LSAs with LS type-4 in this area's Link State Database.

The 32 bit sum of LS checksums of all LSAs with LS type-4 in this area's Link State Database.

The number of LSAs with LS type-7 in this area's Link State Database.

The 32 bit sum of LS checksums of all LSAs with LS type-7 in this area's Link State Database.

The number of LSAs with LS type-10 in this area's Link State Database.

The 32 bit sum of LS checksums of all LSAs with LS type-10 in this area's Link State Database.

This table provides additional information pertaining to OSPF Interfaces for Enterasys OSPF systems.

An entry (conceptual row) in the etsysOspfExtIfTable.

The current operational state of OSPF on this interface.

The subnet mask associated with the IP address of this entry. The value of the mask is an IP address with all the network bits set to 1 and all the hosts bits set to 0.

The time this interface will delay a LSU packet, in order to add more LSAs to the packet before sending. Setting this correctly can reduce the network traffic. This is configurable on a per-interface basis.

Maximum transfer unit (MTU) for the network interface. This is the maximum packet size in bytes for packets sent over the network interface. This size excludes link layer headers but includes IP headers and higher-level headers. Normally, OSPF limits sent PDUs (protocol data units) to less than or equal to this size. However, if OSPF cannot construct a valid PDU smaller than or equal to this size, then it will send the smallest valid PDU and assume that the IP stack will fragment the packet.

Indicates whether this interface is a passive interface. If set to 'true', we suppress HELLO packets sent on and received from this interface. We will therefore advertise this interface in our LSAs but not run the OSPF protocol over it.

Self-originated LSAs are periodically reflooded into the routing domain, to add to the robustness of the OSPF protocol. This value determines the interval between refreshes of LSAs that are only flooded over this interface (type-9 opaque LSAs) and is defaulted to the OSPF standard default of 1800 seconds (30 minutes).

Indicates whether OSPF will help a neighbor undergoing hitless restart on this interface for the specified reason. This field contains a bit flag for each of OspfHitlessRestartReasons. If a bit flag for a specific restart reason is set, then OSPF will help a router restarting for this reason. Otherwise grace LSAs received containing this restart reason will be ignored. Bits: 'reasonSwitchToBackup': 3, 'reasonSoftwareReload': 2, 'reasonSoftwareRestart': 1, 'reasonUnknown': 0.

If configured to help neighbors undergoing hitless restart on this interface, this field indicates the maximum grace period that will be allowed for a neighboring router undergoing hitless restart. If a type-9 grace LSA is received with a greater requested grace period, then the grace LSA will be ignored.

Authentication user data for interface level authentication. This data is passed opaquely to the authentication process, where it can be used to assist with authentication decisions. When read, etsysOspfExtIfAuthUserData always returns an Octet String of length zero.

The number of Hellos that should be sent within 1 second when using Fast Hellos on this interface. This value does not have to be same for all routers attached to a common network, but it is advisable. Fast Hellos are configured using ospfIfRtrDeadInterval.

Whether dynamically created entries in the ospfNbrTable should be kept when the adjacency goes down. If this object is set to 'false', then a dynamically created entry in the ospfNbrTable will remain with state 'down' when the adjacency is lost. Such entries can be deleted manually by setting ospfNbrStatus to 'destroy'. If this object is set to 'true', then dynamically created entries in the ospfNbrTable will be deleted automatically when the adjacency goes down.

This object controls whether OSPF checks the MTU size on incoming Database Description packets. By default, if the received MTU size in a DB Description packet is higher than the MTU size configured on the incoming interface, the OSPF adjacency will not be established. If the interface is tunneled over, say, an MPLS network, then the administrator may not know the maximum MTU size and so can tell OSPF to ignore the MTU size on incoming DB description packets.

This table provides additional information pertaining to OSPF Virtual Interfaces for Enterasys OSPF systems.

An entry (conceptual row) in the etsysOspfExtVirtIfTable.

The desired administrative state of this virtual interface. When the status of this object is set to 'disabled', the virtual link is torn down and no routing information is exchanged with its peer. When the status of this object is set to 'enabled', the virtual link is established (if possible) and routing information is shared with its peer. The etsysOspfExtVirtIfOperStatus object provides the status of this connection.

The current operational state of OSPF on this virtual interface.

The time this interface will delay a LSU packet, in order to add more LSAs to the packet before sending. Setting this correctly can reduce the network traffic. This is configurable on a per-interface basis.

Maximum transfer unit (MTU) for the network interface. This is the maximum packet size in bytes for packets sent over the network interface. This size excludes link layer headers but includes IP headers and higher-level headers. Normally, OSPF limits sent PDUs (protocol data units) to less than or equal to this size. However, if OSPF cannot construct a valid PDU smaller than or equal to this size, then it will send the smallest valid PDU and assume that the IP stack will fragment the packet.

Indicates whether this interface is a passive interface. If set to 'true', we suppress HELLO packets sent on and received from this interface. We will therefore advertise this interface in our LSAs but not run the OSPF protocol over it.

Self-originated LSAs are periodically reflooded into the routing domain, to add to the robustness of the OSPF protocol. This value determines the interval between refreshes of LSAs that are only flooded over this interface (type-9 opaque LSAs) and is defaulted to the OSPF standard default of 1800 seconds (30 minutes).

Indicates whether OSPF will help a neighbor undergoing hitless restart on this interface for the specified reason. This field contains a bit flag for each of OspfHitlessRestartReasons. If a bit flag for a specific restart reason is set, then OSPF will help a router restarting for this reason. Otherwise grace LSAs received containing this restart reason will be ignored. Bits: 'reasonSwitchToBackup': 3, 'reasonSoftwareReload': 2, 'reasonSoftwareRestart': 1, 'reasonUnknown': 0.

If configured to help neighbors undergoing hitless restart on this interface, this field indicates the maximum grace period that will be allowed for a neighboring router undergoing hitless restart. If a type-9 grace LSA is received with a greater requested grace period, then the grace LSA will be ignored.

The number of Hellos that should be sent within 1 second when using Fast Hellos on this interface. This value does not have to be same for all routers attached to a common network, but it is advisable. Fast Hellos are configured using ospfVirtIfRtrDeadInterval.

This object controls whether OSPF checks the MTU size on incoming Database Description packets. By default, if the received MTU size in a DB Description packet is higher than the MTU size configured on the incoming interface, the OSPF adjacency will not be established. If the interface is tunneled over, say, an MPLS network, then the administrator may not know the maximum MTU size and so can tell OSPF to ignore the MTU size on incoming DB description packets.

This table provides additional information pertaining to OSPF Neighbors for Enterasys OSPF systems.

An entry (conceptual row) in the etsysOspfExtNbrTable.

The desired administrative state of this neighbor. When the status of this object is set to 'disabled', the connection to the neighbor is torn down and the routes learned from this neighbor are removed from the RIB. When the status of this object is set to 'enabled', the connection to the neighbor is established (if possible) and routes learned from the neighbor are added to the RIB.

The current operational state of this neighbor.

The number of LSAs requested from this neighbor for which we are awaiting for a response. This field is incremented when an LSA is requested by sending a LS request packet and is decremented when the LSA arrives in a LS update packet.

The IP address of the interface used for this neighbor. If this value is set to zero OSPF will choose a suitable interface to use. If this value is non-zero this neighbor will only be associated with an exactly matching interface. Note this field is only used for NBMA and P2MP links. Also, the etsysOspfExtNbrAdminStatus object must be 'disabled' prior to modifiying this object.

The time remaining in seconds within which we need to receive a hello packet from the neighbor or we declare the adjacency down. If fast hellos area in use, this value is always set to 1. If the etsysOspfExtNbrOperStatus is down or ospfNbrState is DOWN, then the value is set to zero and the field is not valid.

The area to which the neighbor belongs. If the etsysOspfExtNbrOperStatus is down, then this value is set to zero and the field is not valid.

This table provides additional information pertaining to OSPF Virtual Neighbors for Enterasys OSPF systems.

An entry (conceptual row) in the etsysOspfExtVirtNbrTable.

The number of LSAs requested from this neighbor for which we are awaiting for a response. This field is incremented when an LSA is requested by sending a LS request packet and is decremented when the LSA arrives in an LS update packet.

The time remaining in seconds within which we need to receive a hello packet from the neighbor or we declare the adjacency down. If fast hellos area in use, this value is always set to 1.

This table provides additional information pertaining to OSPF Local LS Database for Enterasys OSPF systems.

An entry (conceptual row) in the etsysOspfExtLocalLsdbTable.

The OSPF area in which the link belongs.

This group defines global controls for Enterasys OSPF systems.

This group defines the additional OSPF Area objects supported in the Enterasys OSPF systems.

This group defines the additional OSPF Interface objects supported in the Enterasys OSPF systems.

This group defines the additional OSPF Virtual Interface objects supported in the Enterasys OSPF systems.

This group defines the additional OSPF Neighbor objects supported in the Enterasys OSPF systems.

This group defines the additional OSPF Virtual Neighbor objects supported in the Enterasys OSPF systems.

This group defines the additional OSPF Virtual Neighbor objects supported in the Enterasys OSPF systems.

The compliance statement for devices that support etsysOspfExt.