The bonding updelay parameter does not seem to be applied to the second slave

Solution Verified - Updated -


When booting a server with two bonded interfaces for which an updelay is configured the updelay for the second slave does not seem to be applied and the second slave seems to be made active before (or after) the configured updelay.

This is not apparent when doing a `service network restart`.


  • Red Hat Enterprise Linux (RHEL) 4
  • Red Hat Enterprise Linux 5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content