Status in source: current.
Names: rtmEntityRouteNumber
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"rtmEntityRouteNumber",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"The number of destination prefixes to which DC-RTM currently has a route. This is the same as the number of rows in the rtmRouteTable if the following are both true. - Either rtmEntityEqlCostOpt is set to 'one', or DC-RTM knows of at most one route to each destination prefix. This means that there is at most one route in rtmRouteTable for each destination prefix included in rtmEntityRouteNumber. - None of the routes which DC-RTM has learned about are loose next hops that cannot be resolved. This means that there is at least one route in rtmRouteTable per destination prefix included in rtmEntityRouteNumber.\"",
"::=",
"{",
"rtmEntityEntry",
"30",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The number of destination prefixes to which DC-RTM currently has a route. This is the same as the number of rows in the rtmRouteTable if the following are both true. - Either rtmEntityEqlCostOpt is set to 'one', or DC-RTM knows of at most one route to each destination prefix. This means that there is at most one route in rtmRouteTable for each destination prefix included in rtmEntityRouteNumber. - None of the routes which DC-RTM has learned about are loose next hops that cannot be resolved. This means that there is at least one route in rtmRouteTable per destination prefix included in rtmEntityRouteNumber."
],
null,
null,
null,
null
]
}