Information describes the configured parameters of the router's attached OSPF processes.
The index of the table is hwOspfv2ProcessIdIndex.
|
OID |
Object |
Syntax |
Max Access |
Description |
Implemented Specifications |
|---|---|---|---|---|---|
|
1.3.6.1.4.1.2011.5.25.155.3.1.1 |
hwOspfv2ProcessIdIndex |
Unsigned32 |
accessible-for-notify |
The process ID indicates the OSPF process number. The value ranges from 1 to 4294967295. |
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 |
OCTET STRING{(0,31)} |
read-create |
The name of VPN instance to which the process belongs. The process instance needs to be specified when the process is created, and then cannot be changed. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.3 |
hwOspfv2ConfigRouterId |
IpAddress |
read-create |
A 32-bit integer uniquely identifies the router in the Autonomous System. OSPF private router ID can be configured through this node. The default value is 0.0.0.0. If the value of this node is 0.0.0.0, it means that no private router ID is set for this process. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.4 |
hwOspfv2ActualRouterId |
IpAddress |
read-only |
This node is used to get actual router ID of process and it is a read-only node. If the node hwOspfv2ConfigRouterId is not set, the actual router ID should default to the value of one of the router's IP interface addresses. By default, the value is '00000000'H. |
The actually supported access is accessible-for-notify. This object is used only as the VB bound variable of the alarm. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.5 |
hwOspfv2BandwidthReference |
Unsigned32 |
read-create |
The reference value that is used to calculate the link cost. If there is no explicit link cost, OSPF calculates the cost according to the bandwidth of the link (cost = reference value (M)/bandwidth). |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.6 |
hwOspfv2Description |
OCTET STRING{(0,80)} |
read-create |
The description of the OSPF process. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.7 |
hwOspfv2LsaArriveIntvl |
Integer32{(-1,-1),(0,10000)} |
read-create |
To avoid wasting network resources due to network changes, OSPF defines that the interval for receiving LSAs is 1 second. In a stable network, if the fast speed of route convergence is required, you can cancel the interval of receiving LSAs by setting it to 0 seconds. Routers can thus detect changes of topology and route in time. This speeds up route convergence. By default, this object is -1, indicating that an intelligent timer is enabled instead. Note that -1 is not a configurable value. Instead, by set the intelligent timer (hwOspfv2LsaArriveMaxIntvl, hwOspfv2LsaArriveStartIntvl and hwOspfv2LsaArriveHoldIntvl) to default value, it will get back to default configuration. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.8 |
hwOspfv2LsaArriveMaxIntvl |
Integer32{(-1,-1),(1,120000)} |
read-create |
This object indicates the maximum interval of intelligent-timer for receiving OSPF LSAs. When hwOspfv2LsaArriveMaxIntvl is specified, you need also specify hwOspfv2LsaArriveStartIntvl and hwOspfv2LsaArriveHoldIntvl, but you cannot specify hwOspfv2LsaArriveIntvl. Note that -1 is not a configurable value. Instead, by set the intelligent timer to default value, it will get back to default configuration. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.9 |
hwOspfv2LsaArriveStartIntvl |
Integer32{(-1,-1),(0,60000)} |
read-create |
This object indicates the initial interval of intelligent-timer for receiving OSPF LSAs. When hwOspfv2LsaArriveStartIntvl is specified, you need also specify hwOspfv2LsaArriveMaxIntvl and hwOspfv2LsaArriveHoldIntvl, but you cannot specify hwOspfv2LsaArriveIntvl. Note that -1 is not a configurable value. Instead, by set the intelligent timer to default value, it will get back to default configuration. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.10 |
hwOspfv2LsaArriveHoldIntvl |
Integer32{(-1,-1),(1,60000)} |
read-create |
This object indicates the Holdtime interval of intelligent-timer for receiving OSPF LSAs. After an intelligent timer is enabled, the interval for receiving LSAs is as follows: The initial interval for receiving LSAs is specified by the parameter start-interval. The interval for receiving LSAs for the nth (n>2) time is equal to hold-interval*2(n-1). When the interval specified by hold-interval*2(n-1) 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. When hwOspfv2LsaArriveHoldIntvl is specified, you need also specify wOspfv2LsaArriveMaxIntvl and hwOspfv2LsaArriveStartIntvl, but you cannot specify hwOspfv2LsaArriveIntvl. Note that -1 is not a configurable value. Instead, by set the intelligent timer to default value, it will get back to default configuration. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.11 |
hwOspfv2LsaOrigIntvl |
Integer32{(-1,-1),(0,0)} |
read-create |
To avoid wasting network source due to network changes, OSPF defines that the interval for updating LSAs is 5 seconds. In a stable network, if the speed of route convergence is required to be fast, you can cancel the interval for updating LSAs by setting it to 0 seconds. So, routers can detect changes of topology and route in time. This speeds up route convergence. By default, this object is -1, indicating that an intelligent timer is enabled instead. Note that -1 is not a configurable value. Instead, by set the intelligent timer (hwOspfv2LsaOrigMaxIntvl, hwOspfv2LsaOrigStartIntvl, and hwOspfv2LsaOrigHoldIntvl) to default value, it will get back to default configuration. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.12 |
hwOspfv2LsaOrigMaxIntvl |
Integer32{(-1,-1),(1,120000)} |
read-create |
This object indicates the maximum interval of intelligent-timer for updating OSPF LSAs. When hwOspfv2LsaOrigMaxIntvl is specified, you need also specify hwOspfv2LsaOrigStartIntvl and hwOspfv2LsaOrigHoldIntvl, but you cannot specify hwOspfv2LsaOrigIntvl. Note that -1 is not a configurable value. Instead, by set the intelligent timer to default value, it will get back to default configuration. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.13 |
hwOspfv2LsaOrigStartIntvl |
Integer32{(-1,-1),(0,60000)} |
read-create |
This object indicates the initial interval of intelligent-timer for updating OSPF LSAs. When hwOspfv2LsaOrigStartIntvl is specified, you need also specify hwOspfv2LsaOrigMaxIntvl and hwOspfv2LsaOrigHoldIntvl, but you cannot specify hwOspfv2LsaOrigIntvl. Note that -1 is not a configurable value. Instead, by set the intelligent timer to default value, it will get back to default configuration. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.14 |
hwOspfv2LsaOrigHoldIntvl |
Integer32{(-1,-1),(1,60000)} |
read-create |
This object indicates the Holdtime interval of intelligent-timer for updating OSPF LSAs. After an intelligent timer is enabled, the interval for updating LSAs is as follows: The initial interval for updating LSAs is specified by the parameter start-interval. The interval for updating LSAs for the nth (n>2) time is equal to hold-interval*2(n-1). When the interval specified by hold-interval*2(n-1) 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. When hwOspfv2LsaOrigHoldIntvl is specified, you need also specify hwOspfv2LsaOrigMaxIntvl and hwOspfv2LsaOrigStartIntvl, but you cannot specify hwOspfv2LsaOrigIntvl. Note that -1 is not a configurable value. Instead, by set the intelligent timer to default value, it will get back to default configuration. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.15 |
hwOspfv2LsaOrigIntvlOtherType |
Integer32{(-1,-1),(0,10)} |
read-create |
This object indicates the interval for updating LSAs, excluding OSPF router LSAs and network LSAs. hwOspfv2LsaOrigIntvlOtherType and hwOspfv2LsaOrigIntvl cannot be specified together. Here -1 indicated that hwOspfv2LsaOrigIntvl is enabled instead. Note that -1 is not a configurable value. Instead, by set this node to default value, it will get back to default configuration. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.16 |
hwOspfv2LsdbOverflowLimit |
Integer32{(0,1000000)} |
read-create |
The maximum number of external LSAs in OSPF LSDB. When this node is set to 0, it means that no limits exist. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.17 |
hwOspfv2MaxLoadBalaNumber |
Integer32 |
read-create |
The maximum number of equal-cost routes to a destination in the routing table. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.18 |
hwOspfv2AseRouteMaxNumber |
Integer32{(100,5000000)} |
read-create |
The maximum number of ASE routes that are supported by OSPF. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.19 |
hwOspfv2InterRouteMaxNumber |
Integer32{(100,1000000)} |
read-create |
The maximum number of inter-area routes that are supported by OSPF. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.20 |
hwOspfv2IntraRouteMaxNumber |
Integer32{(100,100000)} |
read-create |
The maximum number of intra-area routes that are supported by OSPF. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.21 |
hwOspfv2RetransLimitMaxNumber |
Integer32{(0,0),(2,255)} |
read-create |
The maximum count of retransmission. The value is an integer that ranges from 2 to 255. When the retransmission limit is disabled, the value is set to 0. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.22 |
hwOspfv2Rfc1583Compatibility |
INTEGER{true(1),false(2)} |
read-create |
It is used to enable the routing rule for compatible RFC 1583. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.23 |
hwOspfv2ShamHello |
INTEGER{true(1),false(2)} |
read-create |
It is used to enable the sham-hello feature of OSPF. After the feature is enabled, OSPF updates the timeout timer of the neighbor when receiving protocol packets of various types. |
The actually supported access is not-accessible. |
|
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 the object identifies the interval unit for OSPF to calculate routes. This object must be specified together with hwOspfv2SpfSchIntervalNumber. By default, this object is none, indicating that an intelligent timer is enabled instead. Note that none is not a configurable value. Instead, by set the intelligent timer (hwOspfv2SpfSchMaxIntvl, hwOspfv2SpfSchStartIntvl, and hwOspfv2SpfSchHoldIntvl) to default value, it will get back to default configuration. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.25 |
hwOspfv2SpfSchIntvlNumber |
Integer32{(-1,-1),(0,0),(1,10000)} |
read-create |
The value of the object identifies the interval for OSPF to calculate routes. This object must be specified together with hwOspfv2SpfSchIntervalUnit. By default, this object is -1, indicating that an intelligent timer is enabled instead. Note that -1 is not a configurable value. Instead, by set the intelligent timer (hwOspfv2SpfSchMaxIntvl, hwOspfv2SpfSchStartIntvl, and hwOspfv2SpfSchHoldIntvl) to default value, it will get back to default configuration. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.26 |
hwOspfv2SpfSchMaxIntvl |
Integer32{(-1,-1),(1,120000)} |
read-create |
This object indicates the maximum interval of intelligent timer for OSPF to perform the SPF calculation. When hwOspfv2SpfSchMaxIntvl is specified, you need also specify hwOspfv2SpfSchStartIntvl and hwOspfv2SpfSchHoldIntvl, but you cannot specify hwOspfv2SpfSchIntvlUnit or hwOspfv2SpfSchIntvlNumber. Note that -1 is not a configurable value. Instead, by set the intelligent timer to default value, it will get back to default configuration. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.27 |
hwOspfv2SpfSchStartIntvl |
Integer32{(-1,-1),(1,60000)} |
read-create |
This object indicates the initial interval of intelligent timer for OSPF to perform the SPF calculation. When hwOspfv2SpfSchStartIntvl is specified, you need also specify hwOspfv2SpfSchMaxIntvl and hwOspfv2SpfSchHoldIntvl, but you cannot specify hwOspfv2SpfSchIntvlUnit or hwOspfv2SpfSchIntvlNumber. Note that -1 is not a configurable value. Instead, by set the intelligent timer to default value, it will get back to default configuration. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.28 |
hwOspfv2SpfSchHoldIntvl |
Integer32{(-1,-1),(1,60000)} |
read-create |
This object indicates the Holdtime interval of intelligent timer for OSPF to perform the SPF calculation. After an intelligent timer is enabled, the interval for the SPF calculation is as follows: The initial interval for the SPF calculation is specified by the parameter start-interval. The interval for the SPF calculation for the nth (n>2) time is equal to hold-interval*2(n-1). When the interval specified by hold-interval*2(n-1) 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. When hwOspfv2SpfSchHoldIntvl is specified, you need also specify hwOspfv2SpfSchMaxIntvl and hwOspfv2SpfSchStartIntvl, but you cannot specify hwOspfv2SpfSchIntvlUnit or hwOspfv2SpfSchIntvlNumber. Note that -1 is not a configurable value. Instead, by set the intelligent timer to default value, it will get back to default configuration. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.29 |
hwOspfv2OpaqueCapability |
INTEGER{true(1),false(2)} |
read-create |
It is used to enable opaque-LSAs capability. When the capability is enabled, then the OSPF process can generate opaque LSAs and process the opaque LSAs received from neighbors. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.30 |
hwOspfv2TrafficAdjustment |
INTEGER{true(1),false(2)} |
read-create |
It is used to enable IGP-shortcut feature. The value false means disable. Otherwise, the value true means enable. If you want to set this node to false, please check whether Local MT feature is disabled. When Local MT feature is enabled, this node cannot be set to false. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.31 |
hwOspfv2TrafficAdvertise |
INTEGER{true(1),false(2)} |
read-create |
It is used to enable IGP-shortcut and Forwarding Adjacency feature. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.32 |
hwOspfv2FlushTimer |
Integer32{(0,40)} |
read-create |
The value of the flush timer. When configuring or undoing OSPF process, flush self-originated LSAs first. If the timer expires, stop flushing LSAs, and then reset the process. This timer is one-off. When flushing is finished, it recovers to 0. |
The actually supported access is not-accessible. |
|
1.3.6.1.4.1.2011.5.25.155.3.1.33 |
hwOspfv2ProcessRowStatus |
INTEGER{active(1),notInService(2),notReady(3),createAndGo(4),createAndWait(5),destroy(6)} |
read-create |
This node is used to create and destroy rows. Because CreateAndWait is not supported, you can set this node to CreatAndGo to create a new process. If the process is created successfully, the value of this node changes to active. |
This object is implemented as defined in the corresponding MIB files. |