bdachecknet After "ifdown eth9" During BDA Failover Testing May Bring Down the bondeth0 Interface/Gateway

Asset ID:	1-72-2040729.1
Update Date:	2015-08-06
Keywords:

Solution Type Problem Resolution Sure

Solution 2040729.1 : bdachecknet After "ifdown eth9" During BDA Failover Testing May Bring Down the bondeth0 Interface/Gateway

Applies to:

Big Data Appliance X3-2 Full Rack - Version All Versions and later
Linux x86-64

Symptoms

Running "bdachecknet" after "ifdown eth9" in the case of failover testing, for example, may bring down the bondeth0 interface and default gateway.

For example consider the sequence of events:

1. Inital output of 'netstat -rnv':

# netstat -rnv

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window      irtt Iface
0.0.0.0         10.128.0.1      0.0.0.0              UG          0 0                 0   bondeth0
*.*.0.0         0.0.0.0           255.255.240.0 U      0 0             0   bondeth0
*.*.*.0         0.0.0.0           255.255.248.0    U        0 0           0   eth0
*.*.*.0         0.0.0.0        255.255.248.0   U        0 0         0   bondib0

2. Run "ifdown eth9" and then "bdachecknet".

3. Subsequent output of 'netstat -rnv' shows that the bondeth0 interface and gateway are down:

# netstat -rnv

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window    irtt Iface
*.*.*.0           0.0.0.0         255.255.248.0     U         0 0               0   eth0
*.*.*.0           0.0.0.0         255.255.248.0    U         0 0           0   bondib0

Cause

The cause is: Bug 21522916- 1) IFDOWN ETH9 2) BDACHECKNET => DEFAULT GATEWAY AND BONDETH0 DISAPEAR.

Solution

You can workaround the problem by running "ifup bondeth0" from the associated ILOM:

# ifup bondeth0

Attachments

This solution has no attachment