Layer 2
| Description | Test Case ID | PD | Topology |
|---|---|---|---|
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 |
PD(Platform dependent) means that FTAS is designed to work with specific hardware and software configurations and may not be compatible with other platforms.
Last updated
