...
{
"apps": {
"org.onosproject.provider.bgp.cfg": {
"bgpapp": {
"routerId": "192.168.251.240",
"localAs": 200,
"maxSession": 20,
"lsCapability": true,
"holdTime": 180,
"largeAsCapability": true,
"flowSpecCapability": "IPV4",
"connectionType": "IPV4_IPV6"
"bgpPeer":[ {"peerIp": "2.2.2.2", "remoteAs": 100, "peerHoldTime": 120, "connectMode":"active"}]
}
}
}
Parameter added:
connectionType : Specifies the connection type to be used for connecting to the BGP peer. It takes three values:
...
RFC 2918 defines the Route Refresh capability for BGP. The support for the same has been added in and is available since ONOS-2.4.
The new config json is of the form :
{
"apps": {
"org.onosproject.provider.bgp.cfg": {
"bgpapp": {
"routerId": "192.168.251.240",
"localAs": 200,
"maxSession": 20,
"lsCapability": true,
"holdTime": 180,
"largeAsCapability": true,
"flowSpecCapability": "IPV4",
"connectionType": "IPV6",
"routeRefreshEnabled": true,
"rrPeriodicTimer": 300,
"rrWarmupTimer": 10,
"rrCooldownTimer":30,
"bgpPeer":[ {"peerIp": "2001:db7:1:3:5054:ff:fe99:2e65", "remoteAs": 200, "peerHoldTime": 120, "connectMode":"active"}]
}
}
}
}
Parameters added:
- routeRefreshEnabled : Depics if route refresh messages are to be sent or not. Boolean, can take values "true"/"false". Default is "false"
- rrPeriodicTimer : Periodic timer value in seconds. Integer. Default value is 300.
- rrWarmupTimer : Warmuptimer value in seconds. Integer. Default value is 10.
- rrCooldownTimer : Cooldownvalue in seconds. Integer. Default value is 30.
To see how these timers work, check the discussion on ONOS-8074. Note that these parameters are made optional, so if no value is provided, route refresh messages will not be sent. Also, all older JSONs will work as they worked previously.WIP