GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Two network interfaces load balancing
Operating System - HP-UX
1847860
Members
4215
Online
104021
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
Forums
Discussions
back
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
01-12-2001 05:35 AM
01-12-2001 05:35 AM
Hi Experts!
Does anybody know, - is there possibilities
to make load balancing over two network interfaces on same server? (both in the same subnet)
Mean by software method.
Thank you in advance.
Does anybody know, - is there possibilities
to make load balancing over two network interfaces on same server? (both in the same subnet)
Mean by software method.
Thank you in advance.
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-12-2001 07:01 AM
01-12-2001 07:01 AM
Solution
Yes. Included with AutoPort Aggregation software is something called Lan Monitor. This has a "hot standby" feature whereas if one card fails, the other comes up.
see
http://docs.hp.com/hpux/onlinedocs/netcom/hp_apa_using11i.pdf
and
http://docs.hp.com/hpux/onlinedocs/J4240-90005/J4240-90005.html
Berlene
see
http://docs.hp.com/hpux/onlinedocs/netcom/hp_apa_using11i.pdf
and
http://docs.hp.com/hpux/onlinedocs/J4240-90005/J4240-90005.html
Berlene
http://www.mindspring.com/~bkherren/dobes/index.htm
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-12-2001 11:22 AM
01-12-2001 11:22 AM
Re: Two network interfaces load balancing
APA is the proper way to go here, but if you are really strapped and cannot buy the software, you might get part of the way there through some cruder and less effective means. This presumes that your system is a server, responding to queries from others, and not initiating connections on its own.
First, you would do something to balance the use of the two IP addresses by your clients. One way would be to implement a DNS round-robbing scheme. each time they ask for the IP address(es) of your server DNS RR would shuffle the order of the IPs in the reply.
Another even cruder way would be to have two names, one for each IP address, and tell 1/2 your clients to use one name, the other half the other.
Next, on the server, you use ndd to set the parameter ip_strong_es_model to a value of one. This tells the transport (among other things) to use the source IP address in addition to the destination IP address when selecting outbound routes. In a nutshell, it means that if the request comes-in on interface 1, the replies will also go out interface 1.
However, like I said above, APA is really the better way to go. It will load balance, allow you to only consume one IP address, and will do automagic failover if one link goes belly-up.
First, you would do something to balance the use of the two IP addresses by your clients. One way would be to implement a DNS round-robbing scheme. each time they ask for the IP address(es) of your server DNS RR would shuffle the order of the IPs in the reply.
Another even cruder way would be to have two names, one for each IP address, and tell 1/2 your clients to use one name, the other half the other.
Next, on the server, you use ndd to set the parameter ip_strong_es_model to a value of one. This tells the transport (among other things) to use the source IP address in addition to the destination IP address when selecting outbound routes. In a nutshell, it means that if the request comes-in on interface 1, the replies will also go out interface 1.
However, like I said above, APA is really the better way to go. It will load balance, allow you to only consume one IP address, and will do automagic failover if one link goes belly-up.
there is no rest for the wicked yet the virtuous have no pillows
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2001 06:12 AM
02-14-2001 06:12 AM
Re: Two network interfaces load balancing
Exact answer and great ideas.
Thanks a lot.
Thanks a lot.
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 2026 Hewlett Packard Enterprise Development LP