LACPMore

In this test, one ecSONiC device and one Cumulus Linux device are used, and two cables are used to connect the devices.

Figure 2: LACP test configuration diagram

Next, create a virtual interface (PortChannel) for LACP on each device and map it to the physical interface. A setting example on the ecSONiC side is described below.

〇PortChannel 作成 AS7326-32X@sonic:~$ sudo config portchannel add PortChannel01 〇PortChannelに物理インターフェースをマッピング AS7326-32X@sonic:~$ sudo config portchannel member add PortChannel01 Ethernet56 AS7326-32X@sonic:~$ sudo config portchannel member add PortChannel01 Ethernet60

After completing all the settings, the following items were checked on each device.

・Even if one cable is disconnected during communication between hosts, communication should continue.

- LACP control frames (LACPDU) are being sent and received between devices using a packet capture tool.

- LACP protocol is activated using CLI commands

The LACP protocol status on the ecSONiC side was confirmed with the following command. As indicated by the yellow mark, we can see that LACP is activated on PortChannel01.

Figure 3: LACP command execution result

BGP (iBGP & eBGP)

In this test, we will use one ecSONiC and one Cumulus Linux device, and set an IP address to the loopback interface of each device.

In addition, the same AS number was set for the iBGP test, and a different AS number was set for the eBGP test, and two cables were used to connect each device in order to check the combined use of ECMP functions.

Figure 4: iBGP test configuration diagram

Figure 5: eBGP test configuration diagram

For each test, first create a loopback interface for use with BGP, launch an integrated terminal called VTY shell, and configure BGP related settings.

Creating a loopback interface configures automatic BGP peering using an IPv6 link-local address called BGP Unnumbered. A setting example on the ecSONiC side is described below.

〇LoopBack0 の設定例 AS7326-32X@sonic:~$ sudo config interface ip add Loopback0 1.1.1.1/32 /*Loopback0 作成*/ AS7326-32X@sonic:~$ vtysh /* VTY シェル起動 */ sonic# configure terminal sonic(config)# router bgp 65001 /* AS番号指定 */ sonic(config-router)# bgp router-id 1.1.1.1 /* Loopback0 アドレス指定 */ sonic(config-router)# neighbor Ethernet56 interface remote-as internal /* neighbor 指定(iBGP) */

After completing all the settings, the following items were checked on each device.

・Communication between hosts is normal due to BGP routing

・Using a packet capture tool, the BGP session has been established normally.

- Multipath (ECMP) must be set using CLI commands.

The multipath setting on the ecSONiC side was confirmed with the following command. As indicated by the yellow mark, you can see that the next hop is set with multipath for the destination route of 192.168.2.0/24.

Figure 6: BGP command execution result

VxLAN

In this test, assuming asymmetric routing, ecSONiC and Cumulus Linux-equipped devices were placed as evaluation machines in Leaf, and another Cumulus Linux-equipped device was placed in Spine as a relay device. increase.

Create a VTEP for the data plane and an EVPN for the control plane on each Leaf device, and configure EVPN on the Spine device.

Figure 7: VxLAN test configuration diagram

First, create a VTEP and NVO to use VxLAN and map the VLAN ID and VNI to the VTEP. A setting example for Leaf1 (ecSONiC) device is described below.

AS7326-32X@sonic:~$ sudo config vxlan add evpn 1.1.1.1 /* VTEP 作成 */ AS7326-32X@sonic:~$ sudo config vxlan evpn_nvo add nvo evpn /* VNVO 設定 */ AS7326-32X@sonic:~$ sudo config vxlan map add evpn 2 2000 /* VTEP に VLAN ID と VNI を関連付け */

Next, launch a VTY shell to configure VxLAN and EVPN related settings.

AS7326-32X@sonic:~$ vtysh
sonic# configure terminal
sonic(config)# router bgp 65001
sonic(config-router)# bgp router-id 1.1.1.1
sonic(config-router)# neighbor Ethernet52 interface remote-as external
sonic(config-router)# address-family ipv4 unicast
sonic(config-router)# network 1.1.1.1/32
sonic(config-router)# network 192.168.2.0/24
sonic(config-router)# exit
sonic(config)# address-family l2vpn evpn
sonic(config-router-af)# neighbor Ethernet52 activate
sonic(config-router-af)# advertise-all-vni

After completing all the settings, the following items were checked on each Leaf device.

・Communication between hosts is normal due to VxLAN routing.

・Using the CLI command, the contents set in VTEP are displayed correctly.

・Mutual recognition of VxLAN between Leaf devices using CLI commands

The VxLAN status of the Leaf1 (ecSONiC) device was checked with the following command. From the status of OperStatus, you can see that VxLAN is mutually recognized between Leaf devices.

Figure 8: VxLAN command execution result

The above is an introduction to the interoperability test for ecSONiC and Cumulus Linux that we verified.