Status in source: current.
Names: fsbgp4mpeAggregateSuppressRouteMapName
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsbgp4mpeAggregateSuppressRouteMapName",
"OBJECT-TYPE",
"SYNTAX",
"DisplayString",
"(",
"SIZE",
"(",
"1",
".",
".",
"20",
")",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"The human-readable name for suppress route-map. The route map contains the rules for suppressing the routes while aggregation. when we use suppress-map configuration along with (summaryonly option set for) fsbgp4mpeAggregateAdvertise, it does'nt have any effect. And the more-specific routes that the suppress-map suppresses are not advertised. Other routes are advertised. When we use fsbgp4mpeAggregateAsSet (with enabled option) with suppress-map although suppress routes are not advertised, the aggregated routes inherits the attributes of all the suppressesed rotues. But it can be overwritten by attribute-map.\"",
"::=",
"{",
"fsbgp4MpeAggregateEntry",
"11",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"DisplayString",
[
"octetStringSubType",
[
[
1,
20
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The human-readable name for suppress route-map. The route map contains the rules for suppressing the routes while aggregation. when we use suppress-map configuration along with (summaryonly option set for) fsbgp4mpeAggregateAdvertise, it does'nt have any effect. And the more-specific routes that the suppress-map suppresses are not advertised. Other routes are advertised. When we use fsbgp4mpeAggregateAsSet (with enabled option) with suppress-map although suppress routes are not advertised, the aggregated routes inherits the attributes of all the suppressesed rotues. But it can be overwritten by attribute-map."
],
null,
null,
null,
null
]
}