InlineBgpConfig1
{
"as_num": "string",
"as_number": 0,
"ecmp": false,
"enabled": false,
"graceful_restart": false,
"graceful_restart_config": {
"graceful_restart_mode": "string",
"graceful_restart_timer": {
"restart_timer": 0,
"stale_timer": 0
}
},
"inter_sr_ibgp": "InterSRRoutingConfig Object",
"logical_router_id": "string",
"multipath_relax": false,
"route_aggregation": [
"BgpRouteAggregation Object"
]
}
For VRF logical router, the as_num from parent logical router will be effective.
This is a deprecated property, Please use 'as_num' instead. For VRF logical router, the as_number from parent logical router will be effective.
While creation of BGP config this flag will be set to true User can change this value while updating BGP config. If this property is not specified in the payload, the default value will be considered as true.
While creation of BGP config this flag will be set to
- true for Tier0 logical router with Active-Active high-availability mode
- false for Tier0 logical router with Active-Standby high-availanility mode. User can change this value while updating the config. If this property is not specified in the payload, the default value will be considered as false irrespective of the high-availability mode.
Flag to enable graceful restart. This field is deprecated, kindly use graceful_restart_config parameter for graceful restart configuration. If both parameters are set and consistent with each other [i.e. graceful_restart=false and graceful_restart_mode=HELPER_ONLY OR graceful_restart=true and graceful_restart_mode=GR_AND_HELPER] then this is allowed, but if inconsistent with each other then this is not allowed and validation error will be thrown. For VRF logical router, the settings from parent logical router will be effective.
BGP Graceful Restart configuration parameters
Logical router id
For TIER0 logical router, default is true. For VRF logical router, the settings from parent logical router will be effective.
List of routes to be aggregated