HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Several bond interfaces or aliases?
Operating System - Linux
1833055
Members
2441
Online
110049
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2007 08:43 PM
07-29-2007 08:43 PM
Several bond interfaces or aliases?
I need assign several IP to the bonded network interface. AFAIK, it can be done in two ways - or by creating bondXX interfaces or by assigning bond0:XX aliases.
IMHO, the first method will add unnecessary load because redundant link monitoring in each bondXX. Am I right?
IMHO, the first method will add unnecessary load because redundant link monitoring in each bondXX. Am I right?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2007 09:06 PM
07-29-2007 09:06 PM
Re: Several bond interfaces or aliases?
It would indeed create unneccessary load (let alone it being supported by the NIC drivers and such).
The common method for multiple IP's has always been aliases. So you'd better go for that indeed.
The common method for multiple IP's has always been aliases. So you'd better go for that indeed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2007 09:18 PM
07-29-2007 09:18 PM
Re: Several bond interfaces or aliases?
It seems to me a physical interface cannot be a member of more than one bond at the same time.
When you need one host to present several IP addresses to the same network segment, using aliases is the standard way to go.
Even if the TCP/IP networking model does not quite match the theoretical structure of the OSI layer model, the bonding happens on the lower protocol layer than IP: as far as it concerns the IP protocol, the bonded set of interfaces should be equivalent to a single interface.
MK
When you need one host to present several IP addresses to the same network segment, using aliases is the standard way to go.
Even if the TCP/IP networking model does not quite match the theoretical structure of the OSI layer model, the bonding happens on the lower protocol layer than IP: as far as it concerns the IP protocol, the bonded set of interfaces should be equivalent to a single interface.
MK
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2007 09:59 PM
07-29-2007 09:59 PM
Re: Several bond interfaces or aliases?
thank you for supporting my opinion :-)!
Probaly we were confused with Broadcom BASP bonding driver. It seems like they use swXX syntax instead of sw0:XX even in fact their swXX interfaces are aliases.
Probaly we were confused with Broadcom BASP bonding driver. It seems like they use swXX syntax instead of sw0:XX even in fact their swXX interfaces are aliases.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP