IP Bonding and ifconfig

[crypto grid]

On Wed, Aug 19, 2009 at 1:15 PM, Thomas Fess <dfezz1 at yahoo.com> wrote:

> OPERATOR ERROR
> Use ethertool or "service network restart"  the ifconfig needs a real nic
> not a virtual nic that bonds two nic's.
> run 'service network restart' and watch the order that the interfaces come
> up,  I think, once again I think that the ethX's need to be up prior to
> bond0 activating.
>
>
>


if you still have issues with "service network restart" you could try
removing the module:
# service network stop
# modprobe -r bonding
# service network start

Rgds,


>
>
>
> ________________________________
> From: William Reich <reich at ulticom.com>
> To: General Red Hat Linux discussion list <redhat-list at redhat.com>
> Sent: Wednesday, August 19, 2009 11:33:34 AM
> Subject: IP Bonding and ifconfig
>
>
> We have configured IP Bonding to use eth3 and eth4.
> The bonded network name is ...  "bond0".
>
> Testing out the configuration, we use ifconfig
> to bring the networks up and down.
>
> When we bring down eth3 or eth4 with the ifconfig tool,
> and then bring them back up,
> we get the expected result.
>
> When we use the ifconfig tool to bring
> down the "bond0", we see the network(s) go down.
> But, when we try to bring "bond0" back up using the
> ifconfig tool, the network does not come up. No traffic flows.
>
> Is this an OS bug or operator error of some type ?
> ( We are using RH4 Update 4 , 2.6.9-42 kernel . )
>
> wr
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
> https://www.redhat.com/mailman/listinfo/redhat-list
>
>
>
>
> --
> redhat-list mailing list
> unsubscribe mailto:redhat-list-request at redhat.com?subjectunsubscribe
>  https://www.redhat.com/mailman/listinfo/redhat-list
>