Basic tests for odl-bgpcep-bmp feature

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

This is a basic suite for bgp monitoring protocol feature. After the feature odl-bgpcep-bmp installation the port 12345 should be bound for listening, To test this feature bgp-bmp-mock tool is used. It is a part of the bgpcep project. It is a java tool which simulates more peers and more routers. In this particular test suite it simulates 1 peer with 1 router, which means it advertizes one peer ipv4 address towards odl. As a result one route should appear in the rests/data/bmp-monitor:bmp-monitor?content=nonconfig.

Basic tests for odl-bgpcep-pcep-all feature.

Copyright (c) 2015 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Functional test suite for bgp - n-path and all-path selection

Copyright (c) 2017 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

This suite tests tcpmd5 connection of bgp peers. It uses odl and exabgp as bgp peer. No routes are advertized, simple peer presence in the datastore is tested. are configured via application peer.

Basic tests for odl-bgpcep-bgp-all feature.

Copyright (c) 2015 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Test suite performs basic BGP functional test cases: BGP peer initiated connection

• introduce and check 3 prefixes in one update message

ODL controller initiated connection:

• introduce and check 3 prefixes in one update message
• introduce 2 prefixes in first update message and then additional 2 prefixes

in another update while the very first prefix is withdrawn

• introduce 3 prefixes and try to withdraw the first one

(to be ignored by controller) in a single update message

TC_R (test case reset) tests session-reset functionality. Resets the session, and than verifies that example-ipv4-topology is empty again.

TC_LA (test case local address) tests configuration of internal peer with local-address configured

• configure peer with local-address and connect bgp-speaker to it

with tools_system_ip

• check filled topology

TC_PG (test case peer group) tests configuration and reconfiguration of peer-groups and neighbors configured by them.

• configure peer-group, and assign neighbor to this peer-group
• check filled topology
• reconfigure peer-group without ipv4 unicast afi-safi
• check empty topology
• reconfigre neighbor without peer-group, delete peer-group

Brief description how to perform BGP functional test: https://wiki.opendaylight.org/view/BGP_LS_PCEP:Lithium_Feature_Tests#How_to_test_2

Functional test for ipv6 connection with bgp.

Copyright (c) 2020 Lumina Networks Intellectual Property. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

This suite tests simple connection between one ibgp peer (goabgp) and Odl. Peer is configured with ipv6, and gobgp connectes to odl via ipv6.

Basic tests for BGP application peer.

Copyright (c) 2015 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Test suite performs basic BGP functional test cases for BGP application peer operations and checks for IP4 topology updates and updates towards BGP peer as follows:

Test case 1: Initial BGP peer connection with pre-filled topology, POST and simple DELETE requests used. BGP_Application_Peer_Post_3_Initial_Routes, Check_Example-IPv4-Topology_Is_Filled_With_3_Routes, Connect_BGP_Peer, BGP_Peer_Check_Incomming_Updates_For_3_Introduced_Prefixes, BGP_Application_Peer_Delete_3_Initial_Routes, Check_Example-IPv4-Topology_Is_Empty, Peer_Check_Incomming_Updates_For_3_Withdrawn_Prefixes, Stop_BGP_Peer.

Test case 2: PUT and DELETE all routes requests while BGP peer is connected. Reconnect_BGP_Peer, BGP_Application_Peer_Put_3_Routes, Check_Example-IPv4-Topology_Is_Filled_With_3_Routes, BGP_Peer_Check_Incomming_Updates_For_3_Introduced_Prefixes, BGP_Application_Peer_Delete_All_Routes, Check_Example-IPv4-Topology_Is_Empty, BGP_Peer_Check_Incomming_Updates_For_3_Withdrawn_Prefixes, Stop_BGP_Peer.

Test case 3: Repeated BGP peer re-connection with pre-filled topology. BGP_Application_Peer_Put_3_Routes, Check_Example-IPv4-Topology_Is_Filled_With_3_Routes, Reconnect_BGP_Peer_And_Check_Incomming_Updates_For_3_Introduced_Prefixes, BGP_Application_Peer_Delete_All_Routes, Check_Example-IPv4-Topology_Is_Empty, BGP_Peer_Check_Incomming_Updates_For_3_Withdrawn_Prefixes, Stop_BGP_Peer.

Brief description how to configure BGP application peer and how to use restconf application peer interface: https://wiki.opendaylight.org/view/BGP_LS_PCEP:User_Guide#BGP_Application_Peer https://wiki.opendaylight.org/view/BGP_LS_PCEP:Programmer_Guide#BGP

Basic tests for iBGP peers.

Copyright (c) 2015-2018 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Test suite performs basic iBGP functional test cases for BGP peers in different roles (iBGP, iBGP RR-client):

Test Case 1: Two iBGP RR-client peers introduce prefixes Expected result: controller forwards updates towards both peers

Test Case 2: Two iBGP peers: one RR client and one non-client introduces prefixes Expected result: controller forwards updates towards both peers

Test Case 3: Two iBGP RR non-client peers introduce prefixes Expected result: controller does not forward any update towards peers

Test Case 4: Two iBGP(play.py) RR-client peers configured, first of them configured with route-reflector-cluster-id, second inherits it's cluster-id from global config. Each of them introduces 3 prefixes. Expected result: controller forwards updates towards both peers and each of their adj-rib-in contains routes. First peer should contain default cluster-id and second cluster-id from first peers configuration.

For polices see: https://wiki.opendaylight.org/view/BGP_LS_PCEP:BGP

Basic tests for eBGP application peers.

Copyright (c) 2015-2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Test suite performs basic eBGP functional tests: Two eBGP peers advertise the same group of prefixes (aka BGP HA) https://wiki.opendaylight.org/view/BGP_LS_PCEP:BGP Reported bugs: Bug 4834 - ODL controller announces the same route twice (two eBGP scenario aka HA) Bug 4835 - Routes not withdrawn when eBGP peers are disconnected (the same prefixes announced)

For versions Fluorine and above, there are test cases: TC_LAS (test case local AS)

• configuration of ebgp with local-as and ibgp without local-as
• connect bgp speakers (play.py) to both peers and check their connection
• check adj-rib-out on both peers, expecting local-as in as-sequence on both peers.

TODO: Extend testsuite by tests dedicated to path selection algorithm TODO: Choose keywords used by more than one test suite to be placed in a common place.

Functional test for bgp flowspec.

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Basic tests for iBGP peers.

Copyright (c) 2015-2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Test suite performs basic iBGP functional test case for carrying LSP State Information in BGP as described in http://tools.ietf.org/html/draft-ietf-idr-te-lsp-distribution-03

Functional test suite for bgp - l3vpn-ipv4

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

This suite tests advertising and receiveing routes with l3vpn content. It uses odl and exabgp as bgp peers. Routes advertized from odl are configured via application peer. Routes advertised from exabgp is statically configured in exabgp config file.

For fluorine and further, instead of exabgp, play.py is used. When sending routes from odl to peer, first route containg route-target argument have to be send from peer to odl, so odl can identify this peer. Than it sends l3vpn route containg this argument to odl app peer, and we check that app peer advertizes this route back to the peer.

Functional test for bgp - evpn

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

This suite tests advertising and receiveing routes with evpn content. It uses play.py and odl as bgp peers. Routes advertized from odl are configured via application peer. Routes advertised from play.py are stored in *.hex files. These files are used also as expected data which is recevied from odl.

Functional test for bgp - route refresh

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

This suite tests sending and receiveing route refresh message. It uses odl and exabgp as bgp peers. Sending route refresh message from odl is initiated via restconf. If route refresh is received by odl, correct advertising of routes is verified. Receiving of route refresh by odl is verified by checking appropriate message counter via odl-bgpcep-bgp-cli and restconf using BGP neighbor operational state

Functional test suite for bgp - n-path and all-path selection

Copyright (c) 2016 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

This suite tests n-path and all-path selection policy. It uses odl and exabgp as bgp peers. Routes advertized from odl are configured via application peer.

Functional test for bgp - mvpn

Copyright (c) 2018 AT&T Intellectual Property. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distbmution, and is available at http://www.eclipse.org/legal/epl-v10.html

This suite tests advertising mvpn routes to odl. For advertising play.py is used, and particular files are stored as *.hex files. There are 7 different types of routes used for auto-discovery of multicast network. Also 4 more routes with new attributes specific for mvpn.

Functional test for bgp - l3vpn-mutlicast

Copyright (c) 2018 AT&T Intellectual Property. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distbmution, and is available at http://www.eclipse.org/legal/epl-v10.html

This suite tests advertising l3vpn_mcast routes to odl. For advertising play.py is used, and particular files are stored as *.hex files. There are L3vpn-ipv4-multicast routes and L3vpn-ipv6-multicast routes tested.

Functional test for bgp - route-target-constrain safi

Copyright (c) 2018 AT&T Intellectual Property. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distbmution, and is available at http://www.eclipse.org/legal/epl-v10.html

This suite tests advertising rt-constrain routes to odl. For advertising from peer, play.py is used, sending hex messages to odl. For advertising to app-peer, we are sending post requests with routes in xml.

Functional test for bgp - route-target-constrain safi

Copyright (c) 2018 AT&T Intellectual Property. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distbmution, and is available at http://www.eclipse.org/legal/epl-v10.html

This suite tests advertising rt-constrain routes to odl. For advertising from peer, play.py is used, sending hex messages to odl. There are 3 peers: ebgp and two ibgps. First peer sends l3vpn route with specific RT to odl, second peer sends RT route and third peer only establishes connection. Then it is checked that odl advertizes l3vpn route to second peer. Third peer sends wildcard RT route and it is checked that odl doesn't advertize l3vpn route to it. Then second peer removes RT and it is checked that second peer withdrew RT route and that odl withdrew l3vpn route from it.

Functional test for bgp routing policies

Copyright (c) 2018 AT&T Intellectual Property. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

This suite uses 7 peers: app peer, 2x rr-client, 2x ebgp, 2x ibgp Tests results on effective-rib-in dependant on their respective configurations. Peers 1,2,4,5 are testing multiple ipv4 routes with additional arguments. Peers 3,6 have ipv4 and ipv6 mpls-labeled routes.

TCPMD5 user-facing feature system tests, using PCEP.

Copyright (c) 2015 Cisco Systems, Inc. and others. All rights reserved.

This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html

Test suite performs basic pcep md5 password authorization test cases: (Run entire basic PCEP suite without passwords.) Start pcc-mock (reconnecting mode): 1 pcc, 1 lsp, password set, check pcep-topology stays empty. Use restconf to change PCEP configuration to use a wrong password, check pcep-topology stays empty. Change ODL PCEP configuration to use the correct password, check pcep-topology shows the lsp. Stop pcc-mock, check pcep-topology stays empty. Start pcc-mock with new password, check pcep-topology stays empty. Change ODL PCEP configuration to use the correct password, check pcep-topology shows the lsp. Update the lsp, check a change in pcep-topology. Change ODL PCEP configuration to not use password, pcep-topology empties, kill pcep-pcc-mock.

Test cases no longer need netconf-connector-ssh, and they include comparison of pcep-session-state.