Test Tools¶
BGP test tools serves to test basic BGP functionality, scalability and performance.
BGP Test Tool¶
The BGP Test Tool is a stand-alone Java application purposed to simulate remote BGP peers, that are capable to advertise sample routes. This application is not part of the OpenDaylight Karaf distribution, however it can be downloaded from OpenDaylight’s Nexus (use latest release version):
https://nexus.opendaylight.org/content/repositories/opendaylight.release/org/opendaylight/bgpcep/bgp-testtool
Usage¶
The application can be run from command line:
java -jar bgp-testtool-*-executable.jar
with optional input parameters:
-i <BOOLEAN>, --active <BOOLEAN>
Active initialisation of the connection, by default false.
-ho <N>, --holdtimer <N>
In seconds, value of the desired holdtimer, by default 90.
-sc <N>, --speakersCount <N>
Number of simulated BGP speakers, when creating each speaker, uses incremented local-address for binding, by default 0.
-ra <IP_ADDRESS:PORT,...>, --remote-address <IP_ADDRESS:PORT,...>
A list of IP addresses of remote BGP peers, that the tool can accept or initiate connect to that address (based on the mode), by default 192.0.2.2:1790.
-la <IP_ADDRESS:PORT>, --localAddress <IP_ADDRESS:PORT>
IP address of BGP speakers which the tools simulates, by default 192.0.2.2:0.
-pr <N>, --prefixes <N>
Number of prefixes to be advertised by each simulated speaker
-mp <BOOLEAN>, --multiPathSupport <BOOLEAN>
Active ADD-PATH support, by default false.
-as <N>, --as <N>
Local AS Number, by default 64496.
-ec <EXTENDED_COMMUNITIES>, --extended_communities <EXTENDED_COMMUNITIES>
Extended communities to be send. Format: x,x,x where x is each extended community from bgp-types.yang, by default empty.
-ll <LOG_LEVEL>, --log_level <LOG_LEVEL>
Log level for console output, by default INFO.
BGP Application Peer Benchmark¶
It is a simple OpenDaylight application which is capable to inject and remove specific amount of IPv4 routes. This application is part of the OpenDaylight Karaf distribution.
Configuration¶
As a first step install BGP and RESTCONF, then configure Application Peer.
Install odl-bgpcep-bgp-benchmark feature and reconfigure BGP Application Peer Benchmark application as per following:
URL: /rests/data/odl-bgp-app-peer-benchmark-config:config
Method: PUT
Content-Type: application/xml
Request Body:
1<odl-bgp-app-peer-benchmark-config xmlns="urn:opendaylight:params:xml:ns:yang:odl-bgp-app-peer-benchmark-config">
2 <app-peer-id xmlns="urn:opendaylight:params:xml:ns:yang:odl-bgp-app-peer-benchmark-config">10.25.1.9</app-peer-id>
3</odl-bgp-app-peer-benchmark-config>
@line 2: The Application Peer identifier.
Content-Type: application/json
Request Body:
1{
2 "odl-bgp-app-peer-benchmark-config": {
3 "app-peer-id": "10.25.1.9"
4 }
5}
@line 3: The Application Peer identifier.
Inject routes¶
Routes injection can be invoked via RPC:
URL: /rests/operations/odl-bgp-app-peer-benchmark:add-prefix
Method: POST
Content-Type: application/xml
Request Body:
1<input xmlns="urn:opendaylight:params:xml:ns:yang:odl-bgp-app-peer-benchmark">
2 <prefix>1.1.1.1/32</prefix>
3 <count>100000</count>
4 <batchsize>2000</batchsize>
5 <nexthop>192.0.2.2</nexthop>
6</input>
@line 2: A initial IPv4 prefix carried in route. Value is incremented for following routes.
@line 3: An amount of routes to be added to Application Peer’s programmable RIB.
@line 4: A size of the transaction batch.
@line 5: A NEXT_HOP attribute value used in all injected routes.
Response Body:
1<output xmlns="urn:opendaylight:params:xml:ns:yang:odl-bgp-app-peer-benchmark">
2 <result>
3 <duration>4301</duration>
4 <rate>25000</rate>
5 <count>100000</count>
6 </result>
7</output>
@line 3: Request duration in milliseconds.
@line 4: Writes per second rate.
@line 5: An amount of routes added to Application Peer’s programmable RIB.
Content-Type: application/json
Request Body:
1{
2 "odl-bgp-app-peer-benchmark:input": {
3 "prefix": "1.1.1.1/32",
4 "count": 100000,
5 "batchsize": 2000,
6 "nexthop": "192.0.2.2"
7 }
8}
@line 3: A initial IPv4 prefix carried in route. Value is incremented for following routes.
@line 4: An amount of routes to be added to Application Peer’s programmable RIB.
@line 5: A size of the transaction batch.
@line 6: A NEXT_HOP attribute value used in all injected routes.
Response Body:
1{
2 "output": {
3 "result": {
4 "duration": 4757,
5 "rate": 25000,
6 "count": 100000
7 }
8 }
9}
@line 4: Request duration in milliseconds.
@line 5: Writes per second rate.
@line 6: An amount of routes added to Application Peer’s programmable RIB.
Remove routes¶
Routes deletion can be invoked via RPC:
URL: /rests/operations/odl-bgp-app-peer-benchmark:delete-prefix
Method: POST
Content-Type: application/xml
Request Body:
1<input xmlns="urn:opendaylight:params:xml:ns:yang:odl-bgp-app-peer-benchmark">
2 <prefix>1.1.1.1/32</prefix>
3 <count>100000</count>
4 <batchsize>2000</batchsize>
5</input>
@line 2: A initial IPv4 prefix carried in route to be removed. Value is incremented for following routes.
@line 3: An amount of routes to be removed from Application Peer’s programmable RIB.
@line 4: A size of the transaction batch.
Response Body:
<output xmlns="urn:opendaylight:params:xml:ns:yang:odl-bgp-app-peer-benchmark">
<result>
<duration>1837</duration>
<rate>54500</rate>
<count>100000</count>
</result>
</output>
Content-Type: application/json
Request Body:
1{
2 "odl-bgp-app-peer-benchmark:input": {
3 "prefix": "1.1.1.1/32",
4 "count": 100000,
5 "batchsize": 2000
6 }
7}
@line 3: A initial IPv4 prefix carried in route to be removed. Value is incremented for following routes.
@line 4: An amount of routes to be removed from Application Peer’s programmable RIB.
@line 5: A size of the transaction batch.
Response Body:
{
"odl-bgp-app-peer-benchmark:output": {
"result": {
"duration": 1837,
"rate": 54500,
"count": 100000
}
}
}