network interface aggregation\bonding
Paul.Preston at proxar.co.uk
Tue May 10 15:37:00 UTC 2011
The whole idea of bonding/interface teaming is to provide high resiliency - yes, you can bond multiple interfaces into multiple groups and connect them to various switches. Obviously, if you connect bondX interface which consists of 4 physical interfaces to 2 switches (2 physical connections per switch) you will need to make sure that all ports on both switches are configured in the same way (which normally means that they should be in the same VLAN). In terms of aggregation, please read about "bonding drivers modes" - that should help to find what you are looking for.
I would recommend reading installation guide and deployment guide from following link:
Proxar IT Ltd. Registered in England and Wales: 6744401- VAT: 942985479
Tubs Hill House, London Road, Sevenoaks, Kent, TN13 1BL
Tel: (+44) 0844 809 4335
Fax: (+44) 01732 459 423
Mob: (+44) 077 9509 3450
Email: paul.preston at proxar.co.uk
From: redhat-list-bounces at redhat.com [mailto:redhat-list-bounces at redhat.com] On Behalf Of Dean Thompson
Sent: 10 May 2011 15:55
To: redhat list
Subject: network interface aggregation\bonding
I am relatively new to RHEL. We have a few implementations of network aggregation with fail-over configured on some of our Solaris servers and I'm looking into whether we can implement similar configs on a RHEL 5.5 server.
Is it possible for only certain nics\drivers?
Can it be configured across multiple switches? i.e. If I have four nics, can I group two in an aggregation group and connect it to one switch and group the other two in another aggregation group and connect it to a different switch, having only one group connected at a time with the other as a fail-over.
redhat-list mailing list
unsubscribe mailto:redhat-list-request at redhat.com?subject=unsubscribe
Please note that we may monitor or record telephone calls, email traffic data and also the content of email for the purposes of security and staff training. This message (and any associated files or documentation) is intended only for the use of the individual or entity to whom it is addressed and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any dissemination, copying or distribution of this message, or files and documentation associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.
More information about the redhat-list