MTU changes during bond failover with be2net module in RHEL 5.5

Solution Verified - Updated -

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.
    

Environment

  • Red Hat Enterprise Linux (RHEL) 5 Update 5
  • Emulex OneConnect CNA using be2net module

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.