Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
This category covers the validation of mandatory features and functions required for data center deployments.
| Description | Test Case ID | PD | Topology |
|---|---|---|---|
PD(Platform dependent) means that FTAS is designed to work with specific hardware and software configurations and may not be compatible with other platforms.
Verify Platform Information
test_platform_001
Yes
Verify Platform Health Status
test_platform_002
Yes
Verify Platform CPU and Process Status
test_platform_003
Yes
Verify Platform PSU
test_platform_004
Yes
Verify Platform Tech-Support
test_platform_005
Yes
| Description | Test Case ID | PD | Topology |
|---|---|---|---|
PD(Platform dependent) means that FTAS is designed to work with specific hardware and software configurations and may not be compatible with other platforms.
Verify Port Auto-negotiation
test_autoneg_001
Yes
Verify physical port operational down/up
test_ports_002
No
Verify port configuration across reboot
test_ports_005
No
Verify Port Information for status, description and transceiver infornation
test_ports_006
Yes
Verify Port Counters for framesize 128
test_ports_009_14
Yes
Verify Port transceiver information
test_ports_020
Yes
Verify FEC Configuration for RS and None
test_ports_fec_001
Yes
Dynamic port breakout with supported breakout modes between leaf1 and leaf2
test_port_breakout_001
Yes
| Description | Test Case ID | PD | Topology |
|---|---|---|---|
PD(Platform dependent) means that FTAS is designed to work with specific hardware and software configurations and may not be compatible with other platforms.
Verify that ping works properly when using LACP
test_ping_011
No
Verifying IPv4 (1518) MTU
test_mtu_001
Yes
Verify MTU functionality for Jumboframe packets
test_ports_mtu_002
Yes
Enable LLDP globally and disable per-port basis
test_lldp_001
No
Verify that user can enable/disable LLDP globally
test_lldp_002
No
Verify LLDP neighbors are learnt properly with proper ChassisID, portID, system name, system
test_lldp_013
No
Verify LACP member addition and removal
test_lacp_003
No
Verify LACP functionality across reboot
test_lacp_005
No
Verify LACP functionality after link failover/failback of physical interface
test_lacp_011
No
Verify LACP functionality after removal and addition of port-channel member
test_lacp_012
No
Verify whether user can create/delete VLAN
test_vlan_001
No
Verify whether user can add/modify/delete ports to the VLAN as tagged/untagged members
test_vlan_002
No
Verify the ability to configure a port as untagged VLAN member
test_vlan_004
No
Verify the ability to configure a port as tagged VLAN member
test_vlan_005
No
Verify that the user can configure port-channel interface as untagged VLAN member
test_vlan_007
No
Verify that the user can configure port-channel interface as tagged VLAN members
test_vlan_008
No
Warm Reboot - Device configuration impact for VLAN Config
test_vlan_011
Yes
Verify whether user can configure port as untagged member of a VLAN
test_vlan_014
No
Verify whether known unicast traffic is forwarded to the destination port-channel
test_vlan_016
No
EVPN_VXLAN Configuration and show commands
test_bgp4_evpn_vxlan_001
Yes
EVPN VXLAN for known unicast, BUM traffic (eBGP) with RIF
test_bgp4_evpn_vxlan_002
Yes
EVPN VXLAN for known unicast, BUM traffic (eBGP) with SVI
test_bgp4_evpn_vxlan_003
Yes
EVPN VXLAN for known unicast traffic (eBGP) with link events and router failure - RIF
test_bgp4_evpn_vxlan_005
Yes
EVPN VXLAN for known unicast traffic (eBGP) with link events and router failure - SVI
test_bgp4_evpn_vxlan_006
Yes
EVPN VXLAN for known unicast traffic (eBGP) with link events and router failure - RPCH
test_bgp4_evpn_vxlan_007
Yes
Asymmetric IRB with EVPN eBGP
test_bgp4_evpn_vxlan_015
Yes
Asymmetric IRB with EVPN iBGP
test_bgp4_evpn_vxlan_016
Yes
MC-LAG L2 validation using port-channel configuration
test_mclag_layer2_steady_state
Yes
MC-LAG L2 validation, Bring down the member link of SPINE01
test_mclag_layer2_member_link_down
Yes
MC-LAG L2 keepalive link down
test_mclag_layer2_peer_link_down
Yes
MCLAG-L2Active Reboot
test_mclag_layer2_active_reboot
Yes
MCLAG-L2 Standby Reboot
test_mclag_layer2_standby_reboot
Yes
Storm control CLI
test_storm_control_cli_verification
Yes
DUT throws proper error for invalid storm-control input
test_storm_control_invalid_input
Yes
Storm control with broadcast traffic
test_storm_control_broadcast
Yes
Storm control with unknown-unicast traffic
test_storm_control_unknown_unicast
Yes
Storm control with unknown-multicast traffic
test_storm_control_unknown_multicast
Yes
Storm control configuration and behavior
during warm-reboot
test_storm_control_warm_reboot
Yes
Configure STP on the devices check for loop free topology with root bridge selection
test_configure_stp_validate
Yes
Enable STP, ensure loop-free topology, configure priority and spine set as root bridge
test_stp_priority
Yes
Edge port transition to forwarding state with portfast enabled
test_port_fast
Yes
Create a static LAG and verify the traffic flow
test_pch_creation
Yes
Add delete members to static LAG and verify the traffic flow
test_pch_sec_member_add_del
Yes
Static LAG recovers after restarting the teamd container
test_lag_docker_teamd_reboot
Yes
Static LAG entry in redis
test_create_pch_check_rediscli
Yes
Static LAG member entry in redis
test_mem_pch_rediscli_check
Yes
Shut and no shut the static LAG
test_shut_noshut_pch
Yes
| Description | Test Case ID | PD | Topology |
|---|---|---|---|
PD(Platform dependent) means that FTAS is designed to work with specific hardware and software configurations and may not be compatible with other platforms.
| Description | Test Case ID | PD | Topology |
|---|---|---|---|
PD(Platform dependent) means that FTAS is designed to work with specific hardware and software configurations and may not be compatible with other platforms.
| Description | Test Case ID | PD | Topology |
|---|---|---|---|
PD(Platform dependent) means that FTAS is designed to work with specific hardware and software configurations and may not be compatible with other platforms.
This section verifies the mandatory functions for management operation in a Fabric
| Description | Test Case ID | PD | Topology |
|---|---|---|---|
PD(Platform dependent) means that FTAS is designed to work with specific hardware and software configurations and may not be compatible with other platforms.
| Description | Test Case ID | PD | Topology |
|---|
PD(Platform dependent) means that FTAS is designed to work with specific hardware and software configurations and may not be compatible with other platforms.
| No. | Description | Test Case ID | PD | Topology |
|---|
PD(Platform dependent) means that FTAS is designed to work with specific hardware and software configurations and may not be compatible with other platforms.
Verify that ping works over ECMP
test_ping_013
No
Verify that IP address can be configured over SVI
test_IP_001
No
Verify that IP address can be configured over routed port
test_IP_002
No
Verify SVI and routed ports can be admin down or up
test_IP_005
No
Verify connected route gets created for the SVI subnet in the ip route table.
test_IP_006
No
Verify IP interface is operational for SVI with LACP portchannel members
test_IP_011
No
Verify ip address can be configured over routed PCH.
test_IP_014
No
Verify BGP AS configuration works properly
test_bgp_001
No
Verify BGP peering happens with nodes in same AS and iBGP neighbor table gets updated properly
test_bgp_002
No
Verify BGP peering happens with nodes in different AS and eBGP neighbor table gets updated properly
test_bgp_003
No
Verify BGP route learning using eBGP with routes injected from IXIA
test_bgp_004
No
Verify BGP route removal using eBGP with routes withdrawn from IXIA
test_bgp_005
No
Verify BGP route relearn over different neighbor when interface is shutdown
test_bgp_006
No
Verify unnumbered functionality with iBGP
test_qual_bgp_001
Yes
Verify unnumbered functionality with eBGP
test_qual_bgp_002
Yes
Verify BGP route redistribution in DUT
test_qual_bgp_003
No
Verify BGP6 functionality
test_qual_bgp_004
No
Verify BGPV6 Functionality in DUT
test_qual_bgp_ebgp_004
No
Verify BGP AS-PATH prepend functionality
test_qual_bgp_007
No
Verify BGP route map match prefix list, access-list deny and permit functionality
test_qual_bgp_008
No
Verify BGP route map match AS-PATH permit and deny functionality
test_qual_bgp_009
No
Verify BGP route map match community list permit and deny functionality
test_qual_bgp_010
No
Verify BGP max MED functionality
test_qual_bgp_011
No
Verify BGP maximum prefix limit per peer functionality
test_qual_bgp_013
No
Verify BGP communities functionality
test_qual_bgp_014
No
Verify BGP regexp match single and multi AS permit & deny action using AS-path access lists
test_qual_bgp_015
No
Verify BGP regexp match any AS permit and deny action using AS-path access lists
test_qual_bgp_016
No
Verify BGP regexp match range of BGP communities functionality
test_qual_bgp_017
No
Verify BGP peering working with BGP listen range
test_qual_bgp_019
No
Verify VRF functionality
test_qual_vrf
Yes
Verify VLAN 1 support for Host connectivity
test_qual_vlan1
Yes
Verify IPV6 neighbor discovery
test_qual_ipv6_neighbor
No
Verify L3 DROP ACL functionality with matching source IP and source port
test_acl_001
No
Verify L3 DROP ACL functionality with matching destination IP and destination port
test_acl_002
No
Verify L3 DROP ACL functionality with matching SIP, DIP, SPORT, DPORT
test_acl_003
No
Verify L3 DROP ACL with ACL rule having subnet mask
test_acl_004
No
Verify L3 DROP ACL est acl rule with protocol = TCP
test_acl_005
No
Verify L3 DROP ACL - Test acl rule with protocol = UDP
test_acl_006
No
Verify L3 PERMIT ACL functionality with matching source IP and source port
test_acl_007
No
Verify L3 PERMIT ACL functionality with matching destination IP and destination port
test_acl_008
No
Verify L3 PERMIT ACL functionality with matching SIP, DIP, SPORT, DPORT
test_acl_009
No
Verify L3 PERMIT ACL with ACL rule having subnet mask
test_acl_010
No
Verify L3 PERMIT ACL - Test acl rule with protocol = TCP
test_acl_011
No
Verify L3 PERMIT ACL - Test acl rule with protocol = UDP
test_acl_012
No
Verify Drop ACL (IPv6) for matching source IPv6/L4 address and source IPv6L4 port
test_qual_ip6_acl_001
No
Verify Drop ACL (IPv6) for matching destination IPv6/L4 port and source IPv6L4 port
test_qual_ip6_acl_002
No
Verify drop ACL - matching IPv6 params subnet, dst, src ports combined
test_qual_ip6_acl_003
No
Verify PERMIT ACL (IPv6) for matching source IPv6/L4 address and source IPv6L4 port
test_qual_ip6_acl_004
No
Verify Permit ACL (IPv6) for matching destination IPv6/L4 port and source IPv6L4 port
test_qual_ip6_acl_005
No
Verify drop ACL - matching IPv6 params subnet, dst, src ports combined
test_qual_ip6_acl_006
No
Verify whether static ARP entry can be configured
test_arp_003
No
Verify that the DUT will respond to an ARP Request for the SVI interface
test_arp_007
No
Verify whether clear ARP entries works properly
test_arp_011
No
Verify whether ARP entries are flushed after some time
test_arp_012
Yes
Verify eBGP multi-AS config, adjacency, route convergence and data path using router interface
test_bgp_netops_001
No
eBGP Multi-AS Route Convergence and data path using loopback
test_bgp_netops_002
No
BGP Node Drain - Add route-map to remove and restore SPINE node 1 and 2 using Community list
test_bgp_netops_003_004
No
Test Link drain - Apply Route-Map permit
test_bgp_netops_005_006
No
Node drain: with IPv6 Traffic Test Node Drain (Spine 1 and Spine 2) for IPv6 Traffic/Prefixes
test_bgp_netops_007
No
Link drain with IPv6 Traffic Test Link Drain for IPv6 Traffic/Prefixes
test_bgp_netops_008
No
Node drain using prefix-lists
test_bgp_netops_009
No
Test Link Drain with Prefix Lists
test_bgp_netops_010
No
Node drain/restore using AS path prepend list
test_bgp_netops_011_012
No
Link drain using AS path prepend
test_bgp_netops_014
No
MC-LAG L3 validation using port-channel configuration
test_mclag_layer3_steady_state
Yes
MC-LAG L3 validation, Bring down the member link of SPINE01
test_mclag_layer3_member_link_down
Yes
MC-LAG L3 keepalive link down
test_mclag_layer3_keepalive_link_down
Yes
MCLAG-L3 Active Reboot
test_mclag_layer3_active_reboot
Yes
MCLAG-L3 Standby Reboot
test_mclag_layer3_standby_reboot
Yes
Symmetric IRB with EVPN eBGP-RIF with s1_as_num=3000, s2_as_num=4000
test_bgp4_evpn_vxlan_009
Yes
Symmetric IRB with EVPN iBGP-RIF with s1_as_num=5000, s2_as_num=5000
test_bgp4_evpn_vxlan_010
Yes
Symmetric IRB with EVPN iBGP-SVI with s1_as_num=5000, s2_as_num=5000
test_bgp4_evpn_vxlan_012
Yes
Symmetric IRB with EVPN eBGP-RPCH with s1_as_num=3000, s2_as_num=4000
test_bgp4_evpn_vxlan_013
Yes
Symmetric IRB with EVPN iBGP-RPCH with s1_as_num=5000, s2_as_num=5000
test_bgp4_evpn_vxlan_014
Yes
Apply QoS with DSCP-0 to TC-0 mapping
test_dscp_0_tc_0
Yes
Apply QoS with DSCP-8 to TC-1 mapping
test_dscp_8_tc_1
Yes
Apply QoS with DSCP-16 to TC-2 mapping
test_dscp_16_tc_2
Yes
Apply QoS with DSCP-24 to TC-3 mapping
test_dscp_24_tc_3
Yes
Apply QoS with DSCP-32 to TC-4
mapping
test_dscp_32_tc_4
Yes
Apply QoS with DSCP-40 to TC-5 mapping
test_dscp_40_tc_5
Yes
Apply QoS with DSCP-48 to TC-6 mapping
test_dscp_48_tc_6
Yes
Apply QoS with DSCP-56 to TC-7 mapping
test_dscp_56_tc_7
Yes
Validate whether the DUT applies QoS using DOT1P-0 to TC-0 mapping
test_dot1p0_tc0
Yes
Validate whether the DUT applies QoS using DOT1P-1 to TC-1 mapping
test_dot1p1_tc1
Yes
Validate whether the DUT applies QoS using DOT1P-2 to TC-2 mapping
test_dot1p2_tc2
Yes
Validate whether the DUT applies QoS using DOT1P-3 to TC-3 mapping
test_dot1p3_tc3
Yes
Validate whether the DUT applies QoS using DOT1P-4 to TC-4 mapping
test_dot1p4_tc4
Yes
Validate whether the DUT applies QoS using DOT1P-5 to TC-5 mapping
test_dot1p5_tc5
Yes
Validate whether the DUT applies QoS using DOT1P-6 to TC-6 mapping
test_dot1p6_tc6
Yes
Validate whether the DUT applies QoS using DOT1P-7 to TC-7 mapping
test_dot1p7_tc7
Yes
Verify basic EVPN VxLAN functionality
test_evpn_vxlan_feature
Yes
Configure EVPN-VXLAN and send bidirectional L3 traffic with intra-VLAN
test_evpn_vxlan_l3_traffic
Yes
Configure EVPN-VXLAN and send bidirectional L3 traffic with intra-VLAN for 16K routes
test_bgp_evpn_vxlan_l3_intra_vlan_scale_16k
Yes
Configure EVPN-VXLAN and send bidirectional L3 traffic with intra-VLAN for 32K routes
test_bgp_evpn_vxlan_l3_intra_vlan_scale_32k
Yes
Configure EVPN-VXLAN and send bidirectional L3 traffic with intra-VLAN for 64K routes
test_bgp_evpn_vxlan_l3_intra_vlan_scale_64k
Yes
Configure EVPN-VXLAN and send bidirectional L3 traffic with intra-VLAN for 128K routes
test_bgp_evpn_vxlan_l3_intra_vlan_scale_128k
Yes
Configure EVPN-VXLAN and send bidirectional L3 traffic with inter-VLAN
test_evpn_vxlan_l3_inter_vlan
Yes
Configure EVPN-VXLAN and send bidirectional L3 traffic with inter-VLAN for 16K routes
test_bgp_evpn_vxlan_inter_vlan_scale_16k
Yes
Configure EVPN-VXLAN and send bidirectional L3 traffic with inter-VLAN for 32K routes
test_bgp_evpn_vxlan_inter_vlan_scale_32k
Yes
Configure EVPN-VXLAN and send bidirectional L3 traffic with inter-VLAN for 64K routes
test_bgp_evpn_vxlan_inter_vlan_scale_64k
Yes
Configure EVPN-VXLAN and send bidirectional L3 traffic with inter-VLAN for 128K routes
test_bgp_evpn_vxlan_inter_vlan_scale_128k
Yes
Verify SPAN with source ports (and LAG) to the destination port in ingress/egress/both directions.
test_port_span_001
Yes
Verify ERSPAN by configuring a mirror with the list of source ports/LAG to destination IP in ingress/egress/both directions
test_port_span_002
Yes
Verify ERSPAN by configuring a mirror from ACL match to destination IP in ingress directions
test_port_span_003
Yes
Verify whether SNMP configurations
test_snmp_config
No
Verify SNMP Get/GetNext/Walk requests MIBS: ENTITY, IF-MIB, IP-MIB,
test_snmp_commands
No
Verify Config load for incremental configuration
test_config_load
No
Verify IPv6 address configuration on Front Panel (Data) ports
test_front_panel_ports_ipv6
No
Verify config reload to restore configuration
test_cfg_backup_restore
No
Verify syslogs are generated properly on link down/up
test_syslog_002
No
Verify syslogs are generated properly on LACP UP/Down
test_syslog_004
No
Verify SSH from host to SONIC on management interface
test_ssh_001
No
Verify SSH from host to SVI interface and routed port
test_ssh_002
No
Verify whether the session is successfully closed right after SSH disconnect from the client.
test_ssh_003
No
Verify Tacacs+ with AAA authentication
test_tacacs_001
No
Verify NTP server works as clock source correctly
test_ntp_007
No
Verify timezone can be manually configured.
test_timezone_001
No
Verify ping from SONIC SVI interface and routed port
test_ping_001
No
Verify that ping works properly with multiple parameter combination
test_ping_009
No
Verify that SONiC Version and serial information can be retrieved via SNMP_WALK command
test_snmp_walk_version_serial
No
Verify that SONiC interface index information can be retrieved via SNMP_WALK command
test_snmp_walk_inf_index
No
Verify that SONiC interface name information can be retrieved via SNMP_WALK command
test_snmp_walk_inf_name
No
Verify that SONiC interface admin and oper status info can be retrieved via SNMP_WALK command
test_snmp_walk_inf_admin_oper
No
Verify that SONiC interface type info can be retrieved via SNMP_WALK command
test_snmp_walk_inf_type
No
Verify that tagged ports vlan id can be retrieved using the SNMP_WALK command
test_snmp_walk_vlan_tagged_ports
No
Verify that untagged ports vlan id can be retrieved using the SNMP_WALK command
test_snmp_walk_vlan_untagged_ports
No
Verify that LLDP neighbor info. can be retrieved via SNMP_WALK command
test_snmp_walk_lldp
No
Verify that routing information can be retrieved via SNMP_WALK command
test_snmp_walk_ip_routing_info
No
Verify that SONiC IP interface index and netmask info can be retrieved via SNMP_WALK command
test_snmp_walk_ip_inf_index_and_netmask
No
Scale up to 128 ACL for matching source IP/port and destination IP/port | test_v4_acl_scale_128 | Yes |
Scale up to 256 ACL for matching source IP/port and destination IP/port | test_v4_acl_scale_256 | Yes |
Scale up to 512 ACL for matching source IP/port and destination IP/port | test_v4_acl_scale_512 | Yes |
Scale up to max supported ACL for matching source IP/port and destination IP/port | test_v4_acl_scale_max_supported | Yes |
Scale up to 128 ACL for denying source IPv6/port and destination IPv6/port | test_qual_v6_acl_scale_128 | Yes |
Scale up to 256 ACL for denying source IPv6/port and destination IPv6/port | test_qual_v6_acl_scale_256 | Yes |
Scale up to 512 ACL for denying source IPv6/port and destination IPv6/port | test_qual_v6_acl_scale_512 | Yes |
Scale up to max supported ACL for denying source IPv6/port and destination IPv6/port | test_qual_v6_acl_scale_max_supported | Yes |
Verify IPv4 L3 Host Routes Scale for 2K | test_v4_host_routes_scale_2k | Yes |
Verify IPv4 L3 Host Routes Scale for 4K | test_v4_host_routes_scale_4k | Yes |
Verify IPv4 L3 Host Routes Scale for max | test_v4_host_routes_scale_max_supported | Yes |
Verify IPv6 L3 Host Routes Scale for 2K | test_v6_host_routes_scale_2k | Yes |
IPv6 host routes scale to 2K routes (iBGP) | test_v6_host_routes_scale_ibgp_2k | Yes |
Verify IPv6 L3 Host Routes Scale for 4k | test_v6_host_routes_scale_4k | Yes |
IPv6 host routes scale to 4K routes (iBGP) | test_v6_host_routes_scale_ibgp_4k | Yes |
Verify IPv6 L3 Host Routes Scale for MAX support | test_v6_host_routes_scale_max_supported | Yes |
IPv6 host routes scale to 32K routes (iBGP) | test_v6_host_routes_scale_ibgp_32k | Yes |
IPv6 host routes scale to 32K routes | test_v6_host_routes_scale_32k | Yes |
Verify IPv4 L3 prefix Routes scale for 2k | test_v4_prefix_routes_scale_2k | Yes |
Verify IPv4 L3 prefix Routes scale for 4k | test_v4_prefix_routes_scale_4k | Yes |
Verify IPv4 L3 prefix Routes scale for MAX SUPPORT | test_v4_prefix_routes_scale_max_supported | Yes |
Verify IPv6 L3 prefix routes scale | test_qual_scale_005 | Yes |
Verify IPv4 Nexthops scale up to 512 | test_v4_nexthops_scale_512 | Yes |
Verify IPv4 Nexthops scale up to 1024 | test_v4_nexthops_scale_1024 | Yes |
Verify IPv4 Nexthops scale max supported | test_v4_nexthops_scale_max_supported | Yes |
Verify IPv6 Nexthops scale | test_qual_scale_007 | Yes |
Scalability to 16 ECMP paths and 32K routes | test_16ecmp_32k_routes | Yes |
Scalability to 32 ECMP paths and 64K routes | test_32ecmp_64k_routes | Yes |
Scalability to 64 ECMP paths and 128K routes | test_64ecmp_128k_routes | Yes |
Scalability to "number of leaf1 ports" ECMP paths and 1K routes per path | test_ecmp_scale_routes | Yes |
BGP dual stack scale for 4K prefix routes | test_bgp_dual_stack_scale_4k | Yes |
BGP dual stack scale for 16K prefix routes | test_bgp_dual_stack_scale_16k | Yes |
BGP dual stack scale for 32K prefix routes | test_bgp_dual_stack_scale_32k | Yes |
BGP dual stack scale for 64K prefix routes | test_bgp_dual_stack_scale_64k | Yes |
BGP dual stack scale for 128K prefix routes | test_bgp_dual_stack_scale_128k | Yes |
BGP dual stack scale with 32K host routes with traffic | test_bgp_host_route_dual_stack_32k | Yes |
BGP dual stack scale with 32K LPM routes with traffic | test_bgp_lpm_route_dual_stack_scale_32k | Yes |
BGP dual stack scale for 32K prefix routes (with 16 bit subnet mask for IPv4 and 64bit subnet mask for IPv6 routes) with traffic | test_bgp_route_dual_stack_32k | Yes |
BGP graceful restart with dual stack scale to 32K prefix routes | test_bgp_graceful_restart_preserve_fw_state_32k | Yes |
BGP graceful restart with dual stack scale to 32K prefix routes and docker restart | test_bgp_graceful_docker_restart_32k | Yes |
Enable/disable BGP graceful restart with dual stack scale to 32K prefix routes | test_bgp_graceful_feature_disable_enable_32k | Yes |
BGP graceful restart with dual stack scale to 32K prefix routes and kill bgp process | test_bgp_kill_process_in_graceful_restart_32k | Yes |
BGP dual stack scale with 64K host routes with traffic | test_bgp_host_route_dual_stack_64k | Yes |
BGP dual stack scale with 128K host routes with traffic | test_bgp_host_route_dual_stack_128k | Yes |
BGP dual stack scale with 64K LPM routes with traffic | test_bgp_lpm_route_dual_stack_scale_64k | Yes |
BGP dual stack scale with 128K LPM routes with traffic | test_bgp_lpm_route_dual_stack_scale_128k | Yes |
BGP graceful restart with dual stack scale to 64K prefix routes | test_bgp_graceful_restart_preserve_fw_state_64k | Yes |
BGP graceful restart with dual stack scale to 128K prefix routes | test_bgp_graceful_restart_preserve_fw_state_128k | Yes |
BGP graceful restart with dual stack scale to 64K prefix routes and docker restart | test_bgp_graceful_docker_restart_64k | Yes |
BGP graceful restart with dual stack scale to 128K prefix routes and docker restart | test_bgp_graceful_docker_restart_128k | Yes |
BGP graceful restart with dual stack scale to 64K prefix routes and kill bgp process | test_bgp_kill_process_in_graceful_restart_64k | Yes |
BGP graceful restart with dual stack scale to 128K prefix routes and kill bgp process | test_bgp_kill_process_in_graceful_restart_128k | Yes |
Scalability to 4K IPv6 prefix routes with traffic. | test_ipv6_l3_prefix_routes_scale_4k | Yes |
Scalability to 64K IPv6 prefix routes with traffic | test_ipv6_l3_prefix_routes_scale_64k | Yes |
Scalability to 128K IPv6 prefix routes with traffic | test_ipv6_l3_prefix_routes_scale_128k | Yes |
128 IPv4 ACL rules (matching source IP/port and destination IP/port) | test_ingress_v4_acl_scale_128 | yes |
256 IPv4 ACL rules (matching source IP/port and destination IP/port) | test_ingress_v4_acl_scale_256 | yes |
512 IPv4 ACL rules (matching source IP/port and destination IP/port) | test_ingress_v4_acl_scale_512 | yes |
(MAX_V4_ACL) IPv4 ACL rules (matching source IP/port and destination IP/port) | test_ingress_v4_acl_scale_max_supported | yes |
Scaling BGP dynamic host routes with traffic. | test_bgp_dynamic_route_scale | No |
BGP withdraw prefixes(5 times) with dual stack scale 160k(IPv4+IPv6) prefix routes. | test_bgp_dual_stack_scale_intf_flap_160k | yes |
BGP session down and docker restart with dual stack scale to 160k(IPv4+IP6) prefix routes | test_bgp_dual_stack_scale_clear_bgp_160k | yes |
BGP withdraw prefixes(5 times) with dual stack scale 160k(IPv4+IPv6) prefix routes. | test_bgp_dual_stack_convergence_withdrawal_160k | yes |
Default Route with BGP Advertised Routes | test_bgp_default_route | No |
Maximum max-MED Value on Startup | test_bgp_convergence_with_max_med_001 | No |
Stress device CPU and memory with 16K (IPv4 + IPv6) prefix routes | test_bgp_dual_stack_stress_16k | Yes |
Stress device CPU and memory with 32K (IPv4 + IPv6) prefix routes | test_bgp_dual_stack_stress_32k | Yes |
Stress device CPU and memory with 64K (IPv4 + IPv6) prefix routes | test_bgp_dual_stack_stress_64k | Yes |
Stress device CPU and memory with 128K (IPv4 + IPv6) prefix routes | test_bgp_dual_stack_stress_128k | Yes |
Stress device CPU and memory with 32K (IPv4 + IPv6) host routes | test_bgp_host_route_dual_stack_stress_32k | Yes |
Stress device CPU and memory with 64K (IPv4 + IPv6) host routes | test_bgp_host_route_dual_stack_stress_64k | Yes |
Stress device CPU and memory with 128K (IPv4 + IPv6) host routes | test_bgp_host_route_dual_stack_stress_128k | Yes |
Stress device CPU and memory with 32K (IPv4 + IPv6) LPM routes | test_bgp_lpm_route_dual_stack_stress_32k | Yes |
Stress device CPU and memory with 64K (IPv4 + IPv6) LPM routes | test_bgp_lpm_route_dual_stack_stress_64k | Yes |
Stress device CPU and memory with 128K (IPv4 + IPv6) LPM routes | test_bgp_lpm_route_dual_stack_stress_128k | Yes |
1 | Verify Chaos Base configuration | test_deploy_verify_base_config | Yes |
2 | Verify Route Scaling time on syncd restart without traffic for 2K routes | test_chaos_route_scaling_time_syncd_2k | Yes |
3 | Verify Route Scaling time on syncd restart without traffic for 8K routes | test_chaos_route_scaling_time_syncd_8k | Yes |
4 | Verify Route Scaling time on syncd restart without traffic for 16K routes | test_chaos_route_scaling_time_syncd_16k | Yes |
5 | Verify Route Scaling time on syncd restart without traffic | test_chaos_route_scaling_time_syncd_32k | Yes |
6 | Verify Route Scaling time on syncd restart without traffic | test_chaos_route_scaling_time_syncd_64k | Yes |
7 | Verify Route Scaling time on FRR restart without traffic for 2K routes | test_chaos_route_scaling_time_frr_2k | Yes |
8 | Verify Route Scaling time on FRR restart without traffic for 8K routes | test_chaos_route_scaling_time_frr_8k | Yes |
9 | Verify Route Scaling time on FRR restart without traffic | test_chaos_route_scaling_time_frr_16k | Yes |
10 | Verify Route Scaling time on FRR restart without traffic | test_chaos_route_scaling_time_frr_32k | Yes |
11 | Verify Route Scaling time on FRR restart without traffic | test_chaos_route_scaling_time_frr_64k | Yes |
12 | Verfiy Route Scaling time on orchagent restart without traffic for 2k routes | test_chaos_route_scaling_time_orchagent_2k | Yes |
13 | Verfiy Route Scaling time on orchagent restart without traffic for 8k routes | test_chaos_route_scaling_time_orchagent_8k | Yes |
14 | Verfiy Route Scaling time on orchagent restart without traffic for 16k routes | test_chaos_route_scaling_time_orchagent_16k | Yes |
15 | Verify Route Scaling time on orchagent restart without traffic for 32k routes | test_chaos_route_scaling_time_orchagent_32k | Yes |
16 | Verify Route Scaling time on orchagent restart without traffic for 64k routes | test_chaos_route_scaling_time_orchagent_64k | Yes |
17 | Verify Route Scaling time on syncd restart with traffic for 2K routes | test_chaos_route_scaling_time_syncd_traffic_2k | Yes |
18 | Verify Route Scaling time on syncd restart with traffic for 8K routes | test_chaos_route_scaling_time_syncd_traffic_8k | Yes |
19 | Verify Route Scaling time on syncd restart with traffic for 16k routes | test_chaos_route_scaling_time_syncd_traffic_16k | Yes |
20 | Verify Route Scaling time on syncd restart with traffic for 32k routes | test_chaos_route_scaling_time_syncd_traffic_32k | Yes |
21 | Verify Route Scaling time on syncd restart with traffic for 64k routes | test_chaos_route_scaling_time_syncd_traffic_64k | Yes |
22 | Verify Route Scaling time on FRR restart with traffic for 2k routes | test_chaos_route_scaling_time_frr_traffic_2k | Yes |
23 | Verify Route Scaling time on FRR restart with traffic for 8k routes | test_chaos_route_scaling_time_frr_traffic_8k | Yes |
24 | Verify Route Scaling time on FRR restart with traffic for 16k routes | test_chaos_route_scaling_time_frr_traffic_16k | Yes |
25 | Verify Route Scaling time on FRR restart with traffic for 32k routes | test_chaos_route_scaling_time_frr_traffic_32 | Yes |
26 | Verify Route Scaling time on FRR restart with traffic for 64k routes | test_chaos_route_scaling_time_frr_traffic_64k | Yes |
27 | Verify Route Scaling time on orchagent restart with traffic with 2k routes | test_chaos_route_scaling_time_orchagent_traffic_2k | Yes |
28 | Verify Route Scaling time on orchagent restart with traffic with 8k routes | test_chaos_route_scaling_time_orchagent_traffic_8k | Yes |
29 | Verify Route Scaling time on orchagent restart with traffic with 16k routes | test_chaos_route_scaling_time_orchagent_traffic_16k | Yes |
30 | Verify Route Scaling time on orchagent restart with traffic with 32k routes | test_chaos_route_scaling_time_orchagent_traffic_32k | Yes |
31 | Verify Route Scaling time on orchagent restart with traffic | test_chaos_route_scaling_time_orchagent_traffic_64k | Yes |
32 | Verify Spine failure and re-insertion impact with 2K routes. | test_deploy_spine_failure_insertion_impact_2k | Yes |
33 | Verify Spine failure and re-insertion impact with 8K routes. | test_deploy_spine_failure_insertion_impact_8k | Yes |
34 | Verify Spine failure and re-insertion impact with 16K routes. | test_deploy_spine_failure_insertion_impact_16k | Yes |
35 | Verify Spine failure and re-insertion impact with 32K routes. | test_deploy_spine_failure_insertion_impact_32k | Yes |
36 | Verify Spine failure and re-insertion impact with 64K routes. | test_deploy_spine_failure_insertion_impact_64k | Yes |
37 | Verify Link failure: LEAF-SPINE with 2K routes | test_deploy_spine_failure_link_impact_2k | Yes |
38 | Verify Link failure: LEAF-SPINE with 8K routes | test_deploy_spine_failure_link_impact_8k | Yes |
39 | Verify Link failure: LEAF-SPINE with 16K routes | test_deploy_spine_failure_link_impact_16k | Yes |
40 | Verify Link failure: LEAF-SPINE with 32K Routes | test_deploy_spine_failure_link_impact_32k | Yes |
41 | Verify Link failure: LEAF-SPINE with 64K routes | test_deploy_spine_failure_link_impact_64k | Yes |
42 | Verify stabilty with Continuous DUT reboot | test_chaos_continuous_reboot | Yes |
43 | Verify Continuous Route push and withdrawal with traffic for 2K routes | test_deploy_longevity_2k | Yes |
44 | Verify Continuous Route push and withdrawal with traffic for 8K routes | test_deploy_longevity_8k | Yes |
45 | Verify Continuous Route push and withdrawal with traffic for 16K routes | test_deploy_longevity_16k | Yes |
46 | Verify Continuous Route push and withdrawal with traffic for 32K routes | test_deploy_longevity_32k | Yes |
47 | Verify Continuous Route push and withdrawal with traffic for 64K routes | test_deploy_longevity_64k | Yes |
48 | Verify Warm Reboot - Device configuration impact with 2K routes | test_deploy_spine_warmreboot_impact_2k | Yes |
49 | Verify Warm Reboot - Device configuration impact with 8K routes | test_deploy_spine_warmreboot_impact_8k | Yes |
50 | Verify Warm Reboot - Device configuration impact with 16K routes | test_deploy_spine_warmreboot_impact_16k | Yes |
51 | Verify Warm Reboot - Device configuration impact with 32K routes | test_deploy_spine_warmreboot_impact_32k | Yes |
52 | Verify Warm Reboot - Device configuration impact with 64K routes | test_deploy_spine_warmreboot_impact_64k | Yes |
53 | Verify Stability with high Kernel CPU and observe its impact on the docker containers | test_chaos_high_kernel_cpu_utilization | Yes |
54 | Verify Routed PCH with 2k routes | test_deploy_impact_lacp_unconfig_2k | Yes |
55 | Verify Routed PCH with 8k routes | test_deploy_impact_lacp_unconfig_8k | Yes |
56 | Verify Routed PCH with 16k routes | test_deploy_impact_lacp_unconfig_16k | Yes |
57 | Verify Routed PCH with 32k routes | test_deploy_impact_lacp_unconfig_32k | Yes |
58 | Verify Routed PCH with 64k routes | test_deploy_impact_lacp_unconfig_64k | Yes |
59 | Fast reboot on spine with traffic and 2k host routes | test_deploy_spine_fastreboot_impact_2k | Yes |
60 | Fast reboot on leaf1 with traffic and 2k host routes | test_deploy_leaf1_fastreboot_impact_2k | Yes |
61 | Fast reboot on leaf2 with traffic and 2k host routes | test_deploy_leaf2_fastreboot_impact_2k | Yes |
62 | Fast reboot on spine with traffic and 2k host routes | test_deploy_spine_fastreboot_impact_8k | Yes |
63 | Fast reboot on leaf1 with traffic and 2k host routes | test_deploy_leaf1_fastreboot_impact_8k | Yes |
64 | Fast reboot on leaf2 with traffic and 2k host routes | test_deploy_leaf2_fastreboot_impact_8k | Yes |
Verify syslog servers scale
test_qual_scale_011
No
Verify NTP server scale
test_qual_scale_012
No
Verify Secondary subnet under a VLAN upto 10 subnets
test_10_secondary_subnet_under_vlan
Yes
Verify Secondary subnet under a VLAN upto 20 subnets
test_20_secondary_subnet_under_vlan
Yes
Verify Secondary subnet under a VLAN upto MAX subnets
test_max_secondary_subnet_under_vlan
Yes
