In my ATCA board, there are two NIC hardwired to switch, so I cannot check the bonding funciton by unplug the cable.

In my ATCA board, there are two NIC hardwired to switch, so I cannot check the bonding funciton by unplug the cable.
I want to check the function by "ifconfig ethX down" command, So I modified the driver code.

1.In open function in my driver code, I called netif_carrier_on(dev) to enable the link status up.

2.In close function, called the netif_carrier_off(dev) to enable the link status down.

3.I modified the Ethtool operation get_link method as follows.
static u32 xlr_get_link(struct net_device *dev)
{
struct driver_data *priv = netdev_priv(dev);

return netif_carrier_ok(dev) ? 1 : 0;

}

So, when issue the "ifconfig ethX down", it will call close function, then call netif_carrier_off(dev). The link status of the NIC will be down. Then bonding will failover to the other NIC. My problem is that at this time, I can not ping througth the network.

The following is my operation log:
1. root@localhost:/root> modprobe bonding mode=1 miimon=100 use_carrier=

2. root@localhost:/root> ifconfig bond0 192.168.4.1 up

3. root@localhost:/root> ifenslave bond0 eth2 eth3

4. root@localhost:/root> cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.1.2 (January 20, 2007)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth2
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: eth2
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:02:bb:00:52:0a

Slave Interface: eth3
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:02:bb:00:52:0b

5. root@localhost:/root> ifconfig eth2 down

6. root@localhost:/root> cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.1.2 (January 20, 2007)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth3
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: eth2
MII Status: down
Link Failure Count: 1
Permanent HW addr: 00:02:bb:00:52:0a

Slave Interface: eth3
MII Status: up
Link Failure Count: 0
Permanent HW addr: 00:02:bb:00:52:0b

At this time, I cannot ping through the Network. But after I ifconfig the eth2 up again, can ping through the network.

It means that the bonding don't switch to the eth3 really. Why?
Who can tell me the root cause?
Thanks a lot.

Shiner

Webcast
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers

Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.

Learn More

Sponsored by AMD

White Paper
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions