User Guide
24
<holdtimer>180</holdtimer>
1. Configure connection attributes (all in milliseconds)
<module>
<type
xmlns:prefix="urn:opendaylight:params:xml:ns:yang:controller:reconnectstrategy">
prefix:timed-reconnect-strategy
</type>
<name>example-reconnect-strategy</name>
<min-sleep>1000</min-sleep> // Minimum sleep time in between
reconnect tries
<max-sleep>180000</max-sleep> // Maximum sleep time in between
reconnect tries
<sleep-factor>2.00</sleep-factor> // Power factor of the sleep time
between reconnect tries
<connect-time>5000</connect-time> // How long we should wait for the
TCP connect attempt, overrides default connection timeout dictated by TCP
retransmits
<executor>
<type
xmlns:netty="urn:opendaylight:params:xml:ns:yang:controller:netty">
netty:netty-event-executor
</type>
<name>global-event-executor</name>
</executor>
</module>
BGP speaker configuration
Previous entries addressed the configuration of a BGP connection initiated by ODL. ODL
also supports BGP Speaker functionality and accepts incoming BGP connections.
The configuration of BGP speaker is located in
<module>
<type xmlns:prefix=
"urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">
prefix:bgp-peer-acceptor
</type>
<name>bgp-peer-server</name>
<!--Default parameters-->
<!--<binding-address>0.0.0.0</binding-address>-->
<!--<binding-port>179</binding-port>-->
<bgp-dispatcher>
<type xmlns:prefix=
"urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">
prefix:bgp-dispatcher
</type>
<name>global-bgp-dispatcher</name>
</bgp-dispatcher>
<!--Drops or accepts incoming BGP connection, every BGP Peer that should be
accepted needs to be added to this registry-->
<peer-registry>
<type xmlns:prefix=
"urn:opendaylight:params:xml:ns:yang:controller:bgp:rib:impl">
prefix:bgp-peer-registry
</type>
<name>global-bgp-peer-registry</name>
</peer-registry>