This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/TCI6636K2H: Network Boning support

Part Number: TCI6636K2H

Tool/software: Linux

Hi,

We are using 6636K2H SOC.

We need network bonding for the network redundancy.

Our development environments are as following?

-. MCSDK 3.1.4.7 (Linux Kernel 3.10.72)

-. SYSLIB 3.0.9.0

Anyone know we can apply the network boning on K2H?

If applicable, pls let me know the feasibility and any guideline.

Thanks.

Shinha.

  • We're looking into this.

    Best Regards,
    Yordan
  • Hi, Shinha,

    Network bonding should be supported in MCSDK 3.1.4.7. Please following the steps

    If the kernel default configuration does not have bonding support, then you need to perform step 1 and 2 to rebuild kernel. The steps below is to configure to mode 6 in network bonding. Other modes should work, but don't have records for them.

    1) Run menuconfig to enable bonding support
    2) Build the kernel and boot up the EVM with the kernel built in (2)
    3) Configure the bonding port in Linux kernel prompt (need to remove “auto eth0” in /etc/network/interfaces)
    # echo 6 > /sys/class/net/bond0/bonding/mode
    # echo 100 > /sys/class/net/bond0/bonding/miimon
    # ifconfig bond0 up
    # ./ifenslave bond0 eth0 eth1
    # ifup bond0 (or ifconfig bond0 <ip addr>)
    4) Ping from 2 different PC’s to EVM. In the set up shown below, mode 6 (tlb + rlb) are tested. Each PC sends the ICMP packets to the MAC address of the Ethernet port it connects to (rlb), but in the ICMP reply packets to each PC, the source MAC address is either eth0 or eth1 (tlb).

    PC-1 (192.168.1.1) <---> |-----------------------| <---> eth0 ---\
    | Ethernet switch | Bond0 (192.168.1.22) EVM
    PC-2 (192.168.1.100) <---> |----------------------| <---> eth1 ---/

    As what was given above, the MCSDK 3.1.4.7 is no longer supported. It should be taken as is. MCSDK was migrated to Processor SDK. The network bonding feature was dropped in ProcSDK.

    Rex
  • Rex,
    Thanks for your good resolution.
    We had confirmed the network boning with your guidance.

    Afterward, we will check the network bonding features after IPsec offloading.
    If it woks as expected. we can close my issue. pls wait for a while.

    One more, thanks for your support.

    Thanks,
    Shinha.