MTU changes during bond failover with be2net module in RHEL 5.5

Issue

• Slaves in the bond is reporting MTU changes when testing failover from primary to backup using ifdown <slave> and when reselecting the primary after ifup <slave>

  Sep 29 14:27:00 hostname1 kernel: bonding: bond0: Adding slave eth5.
  Sep 29 14:27:00 hostname1 kernel: be2net 0000:11:00.1: MTU changed from 1500 to 9000 bytes
  Sep 29 14:27:00 hostname1 kernel: eth5: Link up
  Sep 29 14:27:00 hostname1 kernel: bonding: bond0: making interface eth5 the new active one.
  Sep 29 14:27:00 hostname1 kernel: bonding: bond0: enslaving eth5 as an active interface with an up link.
  Sep 29 14:28:07 hostname1 kernel: bonding: bond0: Removing slave eth5
  Sep 29 14:28:07 hostname1 kernel: bonding: bond0: releasing active interface eth5
  Sep 29 14:28:08 hostname1 kernel: bonding: bond0: making interface eth4 the new active one.
  Sep 29 14:28:08 hostname1 kernel: be2net 0000:11:00.1: MTU changed from 9000 to 1500 bytes
  Sep 29 14:29:10 hostname1 kernel: bonding: bond0: Adding slave eth5.
  Sep 29 14:29:10 hostname1 kernel: be2net 0000:11:00.1: MTU changed from 1500 to 9000 bytes
  Sep 29 14:29:10 hostname1 kernel: eth5: Link up
  Sep 29 14:29:10 hostname1 kernel: bonding: bond0: making interface eth5 the new active one.
  Sep 29 14:29:10 hostname1 kernel: bonding: bond0: enslaving eth5 as an active interface with an up link.