No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

MIB Reference

AR100-S, AR110-S, AR120-S, AR150-S, AR160-S, AR200-S, AR1200-S, AR2200-S, and AR3200-S V200R009

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
hwOspfv2ProcessTable

hwOspfv2ProcessTable

This table configures OSPF processes and sets common parameters for these OSPF processes.

The index of this table is hwOspfv2ProcessIdIndex.

OID

Object Name

Syntax

Max Access

Description

Implemented Specifications

1.3.6.1.4.1.2011.5.25.155.3.1.1

hwOspfv2ProcessIdIndex

Integer32(1 to 65535)

Not-accessible

The value of this object is an integer, identifying the ID of an OSPF process. Each OSPF process belongs to a unique VPN. If VpnNameIndex is not specified during the creation of an OSPF process, this process is considered to belong to the public network.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.2

hwOspfv2VpnName

OCTETSTRING SIZE (0 to 31)

Read-create

This object is a string of characters, indicating the name of a VPN instance. This entry can be configured only when an OSPF process is created. The value of this entry cannot be modified after the OSPF process is created.By default, the length of the VPN name is 0, indicating that an OSPF process is bound to the public network.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.3

hwOspfv2ConfigRouterId

IpAddress

Read-create

This object indicates the router ID in dotted decimal notation. A router ID is reselected only after the router ID of the system or OSPF is reconfigured and the OSPF process is restarted. The default value is 0.0.0.0, indicating that no router ID is configured in the OSPF process. If no router ID is specified, the system automatically selects an IP address of the current interface as the router ID.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.4

hwOspfv2ActualRouterId

IpAddress

Read-only

This object indicates the router ID that an OSPF process currently uses. It is in dotted decimal donation. The default value is 0.0.0.0, indicating that the OSPF process has no router ID.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.5

hwOspfv2BandwidthReference

Unsigned32

Read-create

The value of this object is an integer, identifying the reference value used to calculate the link cost. If the link cost is not set manually, OSPF calculates the cost according to the link bandwidth (Cost = Reference Value/Bandwidth). The default value is 100 Mbit/s.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.6

hwOspfv2Description

OCTET STRING (SIZE (0 to 80))

Read-create

This object is a string of characters, indicating the description of an OSPF process. The default value is 0, indicating that no description is configured.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.7

hwOspfv2LsaArriveIntvl

Integer32(-1 to 10000)

Read-create

The value of this object is an integer, identifying the interval for receiving LSAs. OSPF sets the interval for receiving LSAs to 1 second. This avoids excessive consumption of device resources by network connections or frequent route flapping. In a stable network where routes need to be fast converged, you can cancel the interval for receiving LSAs by setting the interval to 0 seconds. In this case, the change of the topology or route can be sensed immediately. Route convergence is thus sped up. The interval is expressed in milliseconds. The default value is -1, indicating that by default, an intelligent timer rather than the fixed interval is used.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.8

hwOspfv2LsaArriveMaxIntvl

Integer32(-1 | 1..120000)

Read-create

The value of this object is an integer, identifying the maximum interval for receiving LSAs through an intelligent timer.hwOspfv2LsaArriveMaxIntvl, hwOspfv2LsaArriveStartIntvl, and hwOspfv2LsaArriveHoldIntvl must be configured at the same time. In addition, hwOspfv2LsaArriveMaxIntvl and hwOspfv2LsaArriveIntvl are mutually exclusive and cannot be configured at the same time. The interval is expressed in milliseconds. The default value is 1000.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.9

hwOspfv2LsaArriveStartIntvl

Integer32(-1 to 60000)

Read-create

The value of this object is an integer, identifying the initial interval for receiving LSAs through an intelligent timer. hwOspfv2LsaArriveStartIntvl, hwOspfv2LsaArriveMaxIntvl, and hwOspfv2LsaArriveHoldIntvl must be configured at the same time. In addition, hwOspfv2LsaArriveStartIntvl and hwOspfv2LsaArriveIntvl are mutually exclusive and cannot be configured at the same time. The interval is expressed in milliseconds. The default value is 500.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.10

hwOspfv2LsaArriveHoldIntvl

Integer32(-1 | 1..60000)

Read-create

The value of this object is an integer, identifying the hold interval for receiving LSAs through an intelligent timer. After an intelligent timer is enabled, the interval for receiving LSAs is as follows:
  • The interval for receiving LSAs for the first time is start-interval.
  • The interval for receiving LSAs for the nth (n≥2) time is equal to hold-interval x 2(n-2).
  • When the interval specified by hold-interval x 2(n-2) reaches the maximum interval specified by max-interval, OSPF receives LSAs at the maximum interval for three consecutive times. Then, OSPF receives LSAs at the initial interval specified by start-interval, and the whole process is repeated.
hwOspfv2LsaArriveHoldIntvl, hwOspfv2LsaArriveMaxIntvl, and hwOspfv2LsaArriveStartIntvl must be configured at the same time. In addition, hwOspfv2LsaArriveHoldIntvl and hwOspfv2LsaArriveIntvl are mutually exclusive and cannot be configured at the same time. The interval is expressed in milliseconds. The default value is 500.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.11

hwOspfv2LsaOrigIntvl

Integer32(-1 | 0)

Read-create

The value of this object is an integer, identifying the interval for updating LSAs. As defined in OSPF, the interval for updating LSAs is 5 seconds. This avoids excessive consumption of network bandwidth and device resources by network connections or frequent route flapping. In a stable network where routes need to be fast converged, you can cancel the interval for updating LSAs by setting the interval to 0 seconds. In this case, the change of the topology or the route can be immediately advertised to the network through the LSA. Route convergence in the network is thus sped up. The interval is expressed in milliseconds. The default value is -1, indicating that by default, an intelligent timer rather than the fixed interval is used.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.12

hwOspfv2LsaOrigMaxIntvl

Integer32(-1 | 1..120000)

Read-create

The value of this object is an integer, identifying the maximum interval for updating LSAs through an intelligent timer. hwOspfv2LsaOrigMaxIntvl, hwOspfv2LsaOrigStartIntvl, and hwOspfv2LsaOrigHoldIntvl must be configured at the same time. In addition, hwOspfv2LsaOrigMaxIntvl and hwOspfv2LsaOrigIntvl are mutually exclusive and cannot be configured at the same time. The interval is expressed in milliseconds. The default value is 5000.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.13

hwOspfv2LsaOrigStartIntvl

Integer32(-1 to 60000)

Read-create

The value of this object is an integer, identifying the initial interval for updating LSAs through an intelligent timer. hwOspfv2LsaOrigStartIntvl, hwOspfv2LsaOrigMaxIntvl, and hwOspfv2LsaOrigHoldIntvl must be configured at the same time. In addition, hwOspfv2LsaOrigStartIntvl and hwOspfv2LsaOrigIntvl are mutually exclusive and cannot be configured at the same time. The interval is expressed in milliseconds. The default value is 500.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.14

hwOspfv2LsaOrigHoldIntvl

Integer32(-1 | 1..60000)

Read-create

The value of this object is an integer, identifying the hold interval for updating LSAs through an intelligent timer. After an intelligent timer is enabled, the interval for updating LSAs is as follows:
  • The interval for updating LSAs for the first time is start-interval .
  • The interval for updating LSAs for the nth (n≥2) time is equal to hold-interval x 2 x (n-2).
  • When the interval specified by hold-interval x 2 x (n-2) reaches the maximum interval specified by max-interval, OSPF updates LSAs at the maximum interval for three consecutive times. Then, OSPF updates LSAs at the initial interval specified by start-interval , and the whole process is repeated.
hwOspfv2LsaOrigHoldIntvl, hwOspfv2LsaOrigMaxIntvl, and hwOspfv2LsaOrigStartIntvl must be configured at the same time. In addition, hwOspfv2LsaOrigHoldIntvl and hwOspfv2LsaOrigIntvl are mutually exclusive and cannot be configured at the same time. The interval is expressed in milliseconds. The default value is 1000.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.15

hwOspfv2LsaOrigIntvlOtherType

Integer32 (-1 to 10)

Read-create

The value of this object is an integer, identifying the interval for updating LSAs, excluding OSPF router LSAs and network LSAs. That is, the value of this object identifies the interval for updating network summary LSAs, ASBR summary LSAs, AS external LSA, and NSSA LSAs.hwOspfv2LsaOrigIntvlOtherType and hwOspfv2LsaOrigIntvl are mutually exclusive and cannot be configured at the same time. The time is expressed in seconds. The default value is 5.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.16

hwOspfv2LsdbOverflowLimit

Integer32 (0 to 1000000)

Read-create

The value of this object is an integer, identifying the maximum number of external LSAs in an LSDB. The default value is 0, indicating that the maximum number of external LSAs is not configured.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.17

hwOspfv2MaxLoadBalaNumber

Integer32

Read-create

The value of this object is an integer, identifying the maximum number of equal-cost routes to a destination in the routing table.

NOTE:

The value range and default value of the maximum number of equal-cost routes may vary with products and protocols. You can change the maximum number by purchasing the License.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.18

hwOspfv2AseRouteMaxNumber

Integer32(100 to 5000000)

Read-create

The value of this object is an integer, identifying the maximum number of AS-external routes generated by OSPF. The default value is 5000000.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.19

hwOspfv2InterRouteMaxNumber

Integer32(100 to 1000000)

Read-create

The value of this object is an integer, identifying the maximum number of inter-area routes generated by OSPF. The default value is 1000000.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.20

hwOspfv2IntraRouteMaxNumber

Integer32(100 to 100000)

Read-create

The value of this object is an integer, identifying the maximum number of intra-area routes generated by OSPF. The default value is 100000.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.21

hwOspfv2RetransLimitMaxNumber

Integer32(0 | 2..255)

Read-create

The value of this object is an integer, which can be used to enable the retransmission limit function and set the maximum number of retransmissions. The maximum number of retransmissions ranges from 2 to 255. If the value is set to 0, it indicates that the retransmission limit function is not enabled. The default value is 0.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.22

hwOspfv2Rfc1583Compatibility

TruthValue {true(1), false(2)}

Read-create

This object is used to enable the routing selection rule compatible with RFC 1583. By default, the routing selection rule compatible with RFC 1583 is enabled. The default value is true(1).

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.23

hwOspfv2ShamHello

TruthValue {true(1), false(2)}

Read-create

This object is used to enable the Sham-Hello function of OSPF. After the Sham-Hello function is enabled, OSPF updates the timeout timers of all neighbors when receiving all types of protocol packets. The default value is false(2).

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.24

hwOspfv2SpfSchIntvlUnit

Integer {second(1), millionSecond(2), none(3) }

Read-create

The value of this object is an integer, identifying the unit of the interval for the SPF calculation, and hwOspfv2SpfSchIntvlNumber is used to set the specific interval for the SPF calculation. hwOspfv2SpfSchIntvlUnit and hwOspfv2SpfSchIntvlNumber must be configured at the same time. The default value is none(3), indicating that by default, an intelligent timer rather than the fixed interval is used.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.25

hwOspfv2SpfSchIntvlNumber

Integer32

Read-create

The value of this object is an integer, identifying the interval for the SPF calculation, and hwOspfv2SpfSchIntvlUnit is used to set the unit of the interval for the SPF calculation.hwOspfv2SpfSchIntvlNumber and hwOspfv2SpfSchIntvlUnit must be configured at the same time. The value ranges from 1 to 10 in seconds, and the value ranges from 1 to 10000 in milliseconds. The default value is -1, indicating that by default, an intelligent timer rather than the fixed interval is used.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.26

hwOspfv2SpfSchMaxIntvl

Integer32(-1 | 1..120000)

Read-create

The value of this object is an integer, identifying the maximum interval for the SPF calculation. When the OSPF LSDB changes, the shortest path needs to be recalculated. If the network changes frequently and the shortest path is calculated continuously, many system resources are consumed and thus the efficiency of devices is degraded. You can configure an intelligent timer and set a proper interval for the SPF calculation to avoid excessive consumption of device memory and bandwidth resources.hwOspfv2SpfSchMaxIntvl, hwOspfv2SpfSchStartIntvl, and hwOspfv2SpfSchHoldIntvl must be configured at the same time. In addition, hwOspfv2SpfSchMaxIntvl, hwOspfv2SpfSchIntvlUnit, and hwOspfv2SpfSchIntvlNumber are mutually exclusive and cannot be configured at the same time. The interval is expressed in milliseconds. The default value is 10000.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.27

hwOspfv2SpfSchStartIntvl

Integer32(-1 | 1..60000)

Read-create

The value of this object is an integer, identifying the initial interval for the SPF calculation. hwOspfv2SpfSchStartIntvl, hwOspfv2SpfSchMaxIntvl, and hwOspfv2SpfSchHoldIntvl must be configured at the same time. In addition, hwOspfv2SpfSchStartIntvl, hwOspfv2SpfSchIntvlUnit, and hwOspfv2SpfSchIntvlNumber are mutually exclusive and cannot be configured at the same time. The interval is expressed in milliseconds. The default value is 500.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.28

hwOspfv2SpfSchHoldIntvl

Integer32(-1 | 1..60000)

Read-create

The value of this object is an integer, identifying the hold interval for the SPF calculation through an intelligent timer. After an intelligent timer is enabled, the interval for the SPF calculation is as follows:

  • The interval for the SPF calculation for the first time is start-interval.
  • The interval for the SPF calculation for the nth (n≥2) time is equal to hold-interval x 2 x (n-2).
  • When the interval specified by hold-interval x 2 x (n-2) reaches the maximum interval specified by max-interval, OSPF performs the SPF calculation at the maximum interval for three consecutive times. Then, OSPF performs the SPF calculation at the initial interval specified by start-interval, and the whole process is repeated.

hwOspfv2SpfSchHoldIntvl, hwOspfv2SpfSchMaxIntvl, and hwOspfv2SpfSchStartIntvl must be configured at the same time. In addition, hwOspfv2SpfSchHoldIntvl, hwOspfv2SpfSchIntvlUnit, and hwOspfv2SpfSchIntvlNumber are mutually exclusive and cannot be configured at the same time. The interval is expressed in milliseconds. The default value is 1000.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.29

hwOspfv2OpaqueCapability

TruthValue{true(1), false(2)}

Read-create

This object indicates the Opaque-LSA capability. After being enabled with the Opaque-LSA capability, an OSPF process can generate Opaque-LSAs and receive Opaque-LSAs from neighbors. The default value is false(2).

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.32

hwOspfv2FlushTimer

Integer32(0 to 40)

Read-create

The value of this object identifies an aging timer. This value can be configured only when a process is deleted (hwOspfv2ProcessRowStatus is set to Destroy). This object is used to age the locally generated LSAs during the deletion of the process. If a large number of LSAs need to be aged, you can forcibly quit the aging process by starting a waiting timer to continue the subsequent actions of restarting the areas. hwOspfv2FlushTimer is used to set a value for the aging timer.hwOspfv2FlushTimer takes effect for only one time. That is, it can be used to set the aging timer for the next time only. After the aging process is complete, the value restores to 0. The default value is 0, indicating that no aging timer is configured.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.4.1.2011.5.25.155.3.1.33

hwOspfv2ProcessRowStatus

RowStatus

Read-create

This object indicates the status of a row in hwOspfv2ProcessTable. This object can be set to CreatAndGo and Destroy only. When it is set to CreatAndGo and a row is created, the status of this object of the row changes to Active.

This object is implemented as defined in the corresponding MIB files.

Creation Restriction

A row in hwOspfv2ProcessTable can be created only when hwOspfv2ProcessStatus is set to CreateAndGo and the value of hwOspfv2ProcessIdIndex is specified. In this table, a row corresponds to an OSPF process, and hwOspfv2ProcessIdIndex is the index of this table. Multiple variable bindings are supported. If an SNMP packet contains the operation of creating rows and the operation of setting common objects (non-index objects and non-row-status objects are called common objects), rows are created before common objects are set. The rollback is supported only within a row in the same table.

Modification Restriction

The values of common objects (non-index objects and non-row-status objects are called common objects) can be modified only after rows are created. The index of the table cannot be modified after rows are created.

Deletion Restriction

Multiple variable bindings are supported. If an SNMP packet contains the operation of deleting rows and the operation of setting common objects (non-index objects and non-row-status objects are called common objects), rows are deleted before common objects are set. hwOspfv2FlushWaitTimer can be configured only during the deletion of a row.

Access Restriction

The default values of MIB objects and command line are defined differently and thus they do not necessarily correspond to each other.

Translation
Download
Updated: 2019-07-19

Document ID: EDOC1000174090

Views: 512141

Downloads: 49

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next