ANTA catalog for BGP tests
VerifyBGPAdvCommunities ¶
Verifies if the advertised communities of BGP peers are standard, extended, and large in the specified VRF.
Expected Results
- Success: The test will pass if the advertised communities of BGP peers are standard, extended, and large in the specified VRF.
- Failure: The test will fail if the advertised communities of BGP peers are not standard, extended, and large in the specified VRF.
Examples
anta.tests.routing:
bgp:
- VerifyBGPAdvCommunities:
bgp_peers:
- peer_address: 172.30.11.17
vrf: default
- peer_address: 172.30.11.21
vrf: default
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
bgp_peers |
list[BgpPeer]
|
List of BGP peers.
|
- |
BgpPeer¶
Name | Type | Description | Default |
---|---|---|---|
peer_address |
IPv4Address
|
IPv4 address of a BGP peer.
|
- |
vrf |
str
|
Optional VRF for BGP peer. If not provided, it defaults to `default`.
|
'default'
|
Source code in anta/tests/routing/bgp.py
1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 |
|
VerifyBGPExchangedRoutes ¶
Verifies if the BGP peers have correctly advertised and received routes.
The route type should be ‘valid’ and ‘active’ for a specified VRF.
Expected Results
- Success: If the BGP peers have correctly advertised and received routes of type ‘valid’ and ‘active’ for a specified VRF.
- Failure: If a BGP peer is not found, the expected advertised/received routes are not found, or the routes are not ‘valid’ or ‘active’.
Examples
anta.tests.routing:
bgp:
- VerifyBGPExchangedRoutes:
bgp_peers:
- peer_address: 172.30.255.5
vrf: default
advertised_routes:
- 192.0.254.5/32
received_routes:
- 192.0.255.4/32
- peer_address: 172.30.255.1
vrf: default
advertised_routes:
- 192.0.255.1/32
- 192.0.254.5/32
received_routes:
- 192.0.254.3/32
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
bgp_peers |
list[BgpNeighbor]
|
List of BGP neighbors.
|
- |
BgpNeighbor¶
Name | Type | Description | Default |
---|---|---|---|
peer_address |
IPv4Address
|
IPv4 address of a BGP peer.
|
- |
vrf |
str
|
Optional VRF for BGP peer. If not provided, it defaults to `default`.
|
'default'
|
advertised_routes |
list[IPv4Network]
|
List of advertised routes in CIDR format.
|
- |
received_routes |
list[IPv4Network]
|
List of received routes in CIDR format.
|
- |
Source code in anta/tests/routing/bgp.py
612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 |
|
VerifyBGPPeerASNCap ¶
Verifies the four octet asn capabilities of a BGP peer in a specified VRF.
Expected Results
- Success: The test will pass if BGP peer’s four octet asn capabilities are advertised, received, and enabled in the specified VRF.
- Failure: The test will fail if BGP peers are not found or four octet asn capabilities are not advertised, received, and enabled in the specified VRF.
Examples
anta.tests.routing:
bgp:
- VerifyBGPPeerASNCap:
bgp_peers:
- peer_address: 172.30.11.1
vrf: default
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
bgp_peers |
list[BgpPeer]
|
List of BGP peers.
|
- |
BgpPeer¶
Name | Type | Description | Default |
---|---|---|---|
peer_address |
IPv4Address
|
IPv4 address of a BGP peer.
|
- |
vrf |
str
|
Optional VRF for BGP peer. If not provided, it defaults to `default`.
|
'default'
|
Source code in anta/tests/routing/bgp.py
812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 |
|
VerifyBGPPeerCount ¶
Verifies the count of BGP peers for a given address family.
It supports multiple types of Address Families Identifiers (AFI) and Subsequent Address Family Identifiers (SAFI).
For SR-TE SAFI, the EOS command supports sr-te first then ipv4/ipv6 (AFI) which is handled automatically in this test.
Please refer to the Input class attributes below for details.
Expected Results
- Success: If the count of BGP peers matches the expected count for each address family and VRF.
- Failure: If the count of BGP peers does not match the expected count, or if BGP is not configured for an expected VRF or address family.
Examples
anta.tests.routing:
bgp:
- VerifyBGPPeerCount:
address_families:
- afi: "evpn"
num_peers: 2
- afi: "ipv4"
safi: "unicast"
vrf: "PROD"
num_peers: 2
- afi: "ipv4"
safi: "unicast"
vrf: "default"
num_peers: 3
- afi: "ipv4"
safi: "multicast"
vrf: "DEV"
num_peers: 3
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
address_families |
list[BgpAfi]
|
List of BGP address families (BgpAfi).
|
- |
BgpAfi¶
Name | Type | Description | Default |
---|---|---|---|
afi |
Afi
|
BGP address family (AFI).
|
- |
safi |
Safi | None
|
Optional BGP subsequent service family (SAFI).
If the input `afi` is `ipv4` or `ipv6`, a valid `safi` must be provided.
|
None
|
vrf |
str
|
Optional VRF for IPv4 and IPv6. If not provided, it defaults to `default`.
If the input `afi` is not `ipv4` or `ipv6`, e.g. `evpn`, `vrf` must be `default`.
|
'default'
|
num_peers |
PositiveInt
|
Number of expected BGP peer(s).
|
- |
Source code in anta/tests/routing/bgp.py
174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 |
|
VerifyBGPPeerDropStats ¶
Verifies BGP NLRI drop statistics for the provided BGP IPv4 peer(s).
By default, all drop statistics counters will be checked for any non-zero values. An optional list of specific drop statistics can be provided for granular testing.
Expected Results
- Success: The test will pass if the BGP peer’s drop statistic(s) are zero.
- Failure: The test will fail if the BGP peer’s drop statistic(s) are non-zero/Not Found or peer is not configured.
Examples
anta.tests.routing:
bgp:
- VerifyBGPPeerDropStats:
bgp_peers:
- peer_address: 172.30.11.1
vrf: default
drop_stats:
- inDropAsloop
- prefixEvpnDroppedUnsupportedRouteType
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
bgp_peers |
list[BgpPeer]
|
List of BGP peers
|
- |
BgpPeer¶
Name | Type | Description | Default |
---|---|---|---|
peer_address |
IPv4Address
|
IPv4 address of a BGP peer.
|
- |
vrf |
str
|
Optional VRF for BGP peer. If not provided, it defaults to `default`.
|
'default'
|
drop_stats |
list[BgpDropStats] | None
|
Optional list of drop statistics to be verified. If not provided, test will verifies all the drop statistics.
|
None
|
Source code in anta/tests/routing/bgp.py
1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 |
|
VerifyBGPPeerMD5Auth ¶
Verifies the MD5 authentication and state of IPv4 BGP peers in a specified VRF.
Expected Results
- Success: The test will pass if IPv4 BGP peers are configured with MD5 authentication and state as established in the specified VRF.
- Failure: The test will fail if IPv4 BGP peers are not found, state is not as established or MD5 authentication is not enabled in the specified VRF.
Examples
anta.tests.routing:
bgp:
- VerifyBGPPeerMD5Auth:
bgp_peers:
- peer_address: 172.30.11.1
vrf: default
- peer_address: 172.30.11.5
vrf: default
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
bgp_peers |
list[BgpPeer]
|
List of IPv4 BGP peers.
|
- |
BgpPeer¶
Name | Type | Description | Default |
---|---|---|---|
peer_address |
IPv4Address
|
IPv4 address of BGP peer.
|
- |
vrf |
str
|
Optional VRF for BGP peer. If not provided, it defaults to `default`.
|
'default'
|
Source code in anta/tests/routing/bgp.py
968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 |
|
VerifyBGPPeerMPCaps ¶
Verifies the multiprotocol capabilities of a BGP peer in a specified VRF.
Supports strict: True
to verify that only the specified capabilities are configured, requiring an exact match.
Expected Results
- Success: The test will pass if the BGP peer’s multiprotocol capabilities are advertised, received, and enabled in the specified VRF.
- Failure: The test will fail if BGP peers are not found or multiprotocol capabilities are not advertised, received, and enabled in the specified VRF.
Examples
anta.tests.routing:
bgp:
- VerifyBGPPeerMPCaps:
bgp_peers:
- peer_address: 172.30.11.1
vrf: default
strict: False
capabilities:
- ipv4Unicast
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
bgp_peers |
list[BgpPeer]
|
List of BGP peers
|
- |
BgpPeer¶
Name | Type | Description | Default |
---|---|---|---|
peer_address |
IPv4Address
|
IPv4 address of a BGP peer.
|
- |
vrf |
str
|
Optional VRF for BGP peer. If not provided, it defaults to `default`.
|
'default'
|
strict |
bool
|
If True, requires exact matching of provided capabilities. Defaults to False.
|
False
|
capabilities |
list[MultiProtocolCaps]
|
List of multiprotocol capabilities to be verified.
|
- |
Source code in anta/tests/routing/bgp.py
712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 |
|
VerifyBGPPeerRouteLimit ¶
Verifies the maximum routes and optionally verifies the maximum routes warning limit for the provided BGP IPv4 peer(s).
Expected Results
- Success: The test will pass if the BGP peer’s maximum routes and, if provided, the maximum routes warning limit are equal to the given limits.
- Failure: The test will fail if the BGP peer’s maximum routes do not match the given limit, or if the maximum routes warning limit is provided and does not match the given limit, or if the peer is not configured.
Examples
anta.tests.routing:
bgp:
- VerifyBGPPeerRouteLimit:
bgp_peers:
- peer_address: 172.30.11.1
vrf: default
maximum_routes: 12000
warning_limit: 10000
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
bgp_peers |
list[BgpPeer]
|
List of BGP peers
|
- |
BgpPeer¶
Name | Type | Description | Default |
---|---|---|---|
peer_address |
IPv4Address
|
IPv4 address of a BGP peer.
|
- |
vrf |
str
|
Optional VRF for BGP peer. If not provided, it defaults to `default`.
|
'default'
|
maximum_routes |
int
|
The maximum allowable number of BGP routes, `0` means unlimited.
|
Field(ge=0, le=4294967294)
|
warning_limit |
int
|
Optional maximum routes warning limit. If not provided, it defaults to `0` meaning no warning limit.
|
Field(default=0, ge=0, le=4294967294)
|
Source code in anta/tests/routing/bgp.py
1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 |
|
VerifyBGPPeerRouteRefreshCap ¶
Verifies the route refresh capabilities of a BGP peer in a specified VRF.
Expected Results
- Success: The test will pass if the BGP peer’s route refresh capabilities are advertised, received, and enabled in the specified VRF.
- Failure: The test will fail if BGP peers are not found or route refresh capabilities are not advertised, received, and enabled in the specified VRF.
Examples
anta.tests.routing:
bgp:
- VerifyBGPPeerRouteRefreshCap:
bgp_peers:
- peer_address: 172.30.11.1
vrf: default
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
bgp_peers |
list[BgpPeer]
|
List of BGP peers
|
- |
BgpPeer¶
Name | Type | Description | Default |
---|---|---|---|
peer_address |
IPv4Address
|
IPv4 address of a BGP peer.
|
- |
vrf |
str
|
Optional VRF for BGP peer. If not provided, it defaults to `default`.
|
'default'
|
Source code in anta/tests/routing/bgp.py
890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 |
|
VerifyBGPPeerUpdateErrors ¶
Verifies BGP update error counters for the provided BGP IPv4 peer(s).
By default, all update error counters will be checked for any non-zero values. An optional list of specific update error counters can be provided for granular testing.
Note: For “disabledAfiSafi” error counter field, checking that it’s not “None” versus 0.
Expected Results
- Success: The test will pass if the BGP peer’s update error counter(s) are zero/None.
- Failure: The test will fail if the BGP peer’s update error counter(s) are non-zero/not None/Not Found or peer is not configured.
Examples
anta.tests.routing:
bgp:
- VerifyBGPPeerUpdateErrors:
bgp_peers:
- peer_address: 172.30.11.1
vrf: default
update_error_filter:
- inUpdErrWithdraw
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
bgp_peers |
list[BgpPeer]
|
List of BGP peers
|
- |
BgpPeer¶
Name | Type | Description | Default |
---|---|---|---|
peer_address |
IPv4Address
|
IPv4 address of a BGP peer.
|
- |
vrf |
str
|
Optional VRF for BGP peer. If not provided, it defaults to `default`.
|
'default'
|
update_errors |
list[BgpUpdateError] | None
|
Optional list of update error counters to be verified. If not provided, test will verifies all the update error counters.
|
None
|
Source code in anta/tests/routing/bgp.py
1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 |
|
VerifyBGPPeersHealth ¶
Verifies the health of BGP peers.
It will validate that all BGP sessions are established and all message queues for these BGP sessions are empty for a given address family.
It supports multiple types of Address Families Identifiers (AFI) and Subsequent Address Family Identifiers (SAFI).
For SR-TE SAFI, the EOS command supports sr-te first then ipv4/ipv6 (AFI) which is handled automatically in this test.
Please refer to the Input class attributes below for details.
Expected Results
- Success: If all BGP sessions are established and all messages queues are empty for each address family and VRF.
- Failure: If there are issues with any of the BGP sessions, or if BGP is not configured for an expected VRF or address family.
Examples
anta.tests.routing:
bgp:
- VerifyBGPPeersHealth:
address_families:
- afi: "evpn"
- afi: "ipv4"
safi: "unicast"
vrf: "default"
- afi: "ipv6"
safi: "unicast"
vrf: "DEV"
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
address_families |
list[BgpAfi]
|
List of BGP address families (BgpAfi).
|
- |
BgpAfi¶
Name | Type | Description | Default |
---|---|---|---|
afi |
Afi
|
BGP address family (AFI).
|
- |
safi |
Safi | None
|
Optional BGP subsequent service family (SAFI).
If the input `afi` is `ipv4` or `ipv6`, a valid `safi` must be provided.
|
None
|
vrf |
str
|
Optional VRF for IPv4 and IPv6. If not provided, it defaults to `default`.
If the input `afi` is not `ipv4` or `ipv6`, e.g. `evpn`, `vrf` must be `default`.
|
'default'
|
Source code in anta/tests/routing/bgp.py
321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 |
|
VerifyBGPSpecificPeers ¶
Verifies the health of specific BGP peer(s).
It will validate that the BGP session is established and all message queues for this BGP session are empty for the given peer(s).
It supports multiple types of Address Families Identifiers (AFI) and Subsequent Address Family Identifiers (SAFI).
For SR-TE SAFI, the EOS command supports sr-te first then ipv4/ipv6 (AFI) which is handled automatically in this test.
Please refer to the Input class attributes below for details.
Expected Results
- Success: If the BGP session is established and all messages queues are empty for each given peer.
- Failure: If the BGP session has issues or is not configured, or if BGP is not configured for an expected VRF or address family.
Examples
anta.tests.routing:
bgp:
- VerifyBGPSpecificPeers:
address_families:
- afi: "evpn"
peers:
- 10.1.0.1
- 10.1.0.2
- afi: "ipv4"
safi: "unicast"
peers:
- 10.1.254.1
- 10.1.255.0
- 10.1.255.2
- 10.1.255.4
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
address_families |
list[BgpAfi]
|
List of BGP address families (BgpAfi).
|
- |
BgpAfi¶
Name | Type | Description | Default |
---|---|---|---|
afi |
Afi
|
BGP address family (AFI).
|
- |
safi |
Safi | None
|
Optional BGP subsequent service family (SAFI).
If the input `afi` is `ipv4` or `ipv6`, a valid `safi` must be provided.
|
None
|
vrf |
str
|
Optional VRF for IPv4 and IPv6. If not provided, it defaults to `default`.
`all` is NOT supported.
If the input `afi` is not `ipv4` or `ipv6`, e.g. `evpn`, `vrf` must be `default`.
|
'default'
|
peers |
list[IPv4Address | IPv6Address]
|
List of BGP IPv4 or IPv6 peer.
|
- |
Source code in anta/tests/routing/bgp.py
460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 |
|
VerifyBGPTimers ¶
Verifies if the BGP peers are configured with the correct hold and keep-alive timers in the specified VRF.
Expected Results
- Success: The test will pass if the hold and keep-alive timers are correct for BGP peers in the specified VRF.
- Failure: The test will fail if BGP peers are not found or hold and keep-alive timers are not correct in the specified VRF.
Examples
anta.tests.routing:
bgp:
- VerifyBGPTimers:
bgp_peers:
- peer_address: 172.30.11.1
vrf: default
hold_time: 180
keep_alive_time: 60
- peer_address: 172.30.11.5
vrf: default
hold_time: 180
keep_alive_time: 60
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
bgp_peers |
list[BgpPeer]
|
List of BGP peers
|
- |
BgpPeer¶
Name | Type | Description | Default |
---|---|---|---|
peer_address |
IPv4Address
|
IPv4 address of a BGP peer.
|
- |
vrf |
str
|
Optional VRF for BGP peer. If not provided, it defaults to `default`.
|
'default'
|
hold_time |
int
|
BGP hold time in seconds.
|
Field(ge=3, le=7200)
|
keep_alive_time |
int
|
BGP keep-alive time in seconds.
|
Field(ge=0, le=3600)
|
Source code in anta/tests/routing/bgp.py
1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 |
|
VerifyBgpRouteMaps ¶
Verifies BGP inbound and outbound route-maps of BGP IPv4 peer(s).
Expected Results
- Success: The test will pass if the correct route maps are applied in the correct direction (inbound or outbound) for IPv4 BGP peers in the specified VRF.
- Failure: The test will fail if BGP peers are not configured or any neighbor has an incorrect or missing route map in either the inbound or outbound direction.
Examples
anta.tests.routing:
bgp:
- VerifyBgpRouteMaps:
bgp_peers:
- peer_address: 172.30.11.1
vrf: default
inbound_route_map: RM-MLAG-PEER-IN
outbound_route_map: RM-MLAG-PEER-OUT
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
bgp_peers |
list[BgpPeer]
|
List of BGP peers
|
- |
BgpPeer¶
Name | Type | Description | Default |
---|---|---|---|
peer_address |
IPv4Address
|
IPv4 address of a BGP peer.
|
- |
vrf |
str
|
Optional VRF for BGP peer. If not provided, it defaults to `default`.
|
'default'
|
inbound_route_map |
str | None
|
Inbound route map applied, defaults to None.
|
None
|
outbound_route_map |
str | None
|
Outbound route map applied, defaults to None.
|
None
|
Source code in anta/tests/routing/bgp.py
1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 |
|
VerifyEVPNType2Route ¶
Verifies the EVPN Type-2 routes for a given IPv4 or MAC address and VNI.
Expected Results
- Success: If all provided VXLAN endpoints have at least one valid and active path to their EVPN Type-2 routes.
- Failure: If any of the provided VXLAN endpoints do not have at least one valid and active path to their EVPN Type-2 routes.
Examples
anta.tests.routing:
bgp:
- VerifyEVPNType2Route:
vxlan_endpoints:
- address: 192.168.20.102
vni: 10020
- address: aac1.ab5d.b41e
vni: 10010
Inputs¶
Name | Type | Description | Default |
---|---|---|---|
vxlan_endpoints |
list[VxlanEndpoint]
|
List of VXLAN endpoints to verify.
|
- |
VxlanEndpoint¶
Name | Type | Description | Default |
---|---|---|---|
address |
IPv4Address | MacAddress
|
IPv4 or MAC address of the VXLAN endpoint.
|
- |
vni |
Vni
|
VNI of the VXLAN endpoint.
|
- |
Source code in anta/tests/routing/bgp.py
1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 |
|