HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Network interface response order
Operating System - HP-UX
1832910
Members
2725
Online
110048
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
03-15-2001 02:14 AM
03-15-2001 02:14 AM
Network interface response order
I noticed HP engineer replied regarding APA question 'Two network interfaces load balancing' (January 12, 2001) talking about using ndd to setup ip_strong_es_model to route source and desination through designed interfaces.
Here we have similar problem when application server (Bea WebLogic) binding a license ip. We notice sometime the server response ip is not correct because we config 3 NIC with 4 ip (lan1 and lan2 is apa group and config to 2 ip, which means lan100 and lan100:1) on two machines. I tried to setup ip_strong_es_model to see whether the response is correct when clients make a http requests. By using multicasting tool (from WebLogic) to take a ping (for example, ping 237.0.0.1 assigned to clustered nodes to commnicate each other) it always returns 101 and 103.
So it seems to us network interface has different response order (we don't know). Setup ip_strong_es_model doesn't work either. Anyway we can have correct ping to designed ip? Greatly appreciated your input,
CONFIGURATION (web1):
lan100 192.168.0.101 (apa manual)
lan101 192.168.0.102 (apa manual)
lan0 192.168.0.61 (WebLogic uses)
lan0:1 192.168.0.62
CONFIGURATION (web2):
lan100 192.168.0.103 (apa manual)
lan101 192.168.0.104 (apa manual)
lan0 192.168.0.63 (WebLogic uses)
lan0:1 192.168.0.64
Here we have similar problem when application server (Bea WebLogic) binding a license ip. We notice sometime the server response ip is not correct because we config 3 NIC with 4 ip (lan1 and lan2 is apa group and config to 2 ip, which means lan100 and lan100:1) on two machines. I tried to setup ip_strong_es_model to see whether the response is correct when clients make a http requests. By using multicasting tool (from WebLogic) to take a ping (for example, ping 237.0.0.1 assigned to clustered nodes to commnicate each other) it always returns 101 and 103.
So it seems to us network interface has different response order (we don't know). Setup ip_strong_es_model doesn't work either. Anyway we can have correct ping to designed ip? Greatly appreciated your input,
CONFIGURATION (web1):
lan100 192.168.0.101 (apa manual)
lan101 192.168.0.102 (apa manual)
lan0 192.168.0.61 (WebLogic uses)
lan0:1 192.168.0.62
CONFIGURATION (web2):
lan100 192.168.0.103 (apa manual)
lan101 192.168.0.104 (apa manual)
lan0 192.168.0.63 (WebLogic uses)
lan0:1 192.168.0.64
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2001 07:30 AM
03-20-2001 07:30 AM
Re: Network interface response order
Brian,
I've noticed your question sitting on the forums without an answer for some time. However, now that I've re-read it, what "jumps out" at me here, is that on each system, you've configured multiple LAN interfaces on the same IP subnet. You can have as multiple VIRTUAL IP's on the SAME subnet, but NOT multiple LAN interfaces/cards/aggregates.
What will happend in any case, is that yes, a packet addressed to an individual LAN interface will go to that LAN interface, but any reply packet will go out the LAST LAN INTERFACE ifconfig'd UP on that IP subnet...
I believe that is the behavior you are noting here.
You can either live with this condition, or seperate the LAN Interfaces (and their associated Virtual IP's) so that they are on unique IP Subnets.
Hope this helps,
-> Brian Hackley
I've noticed your question sitting on the forums without an answer for some time. However, now that I've re-read it, what "jumps out" at me here, is that on each system, you've configured multiple LAN interfaces on the same IP subnet. You can have as multiple VIRTUAL IP's on the SAME subnet, but NOT multiple LAN interfaces/cards/aggregates.
What will happend in any case, is that yes, a packet addressed to an individual LAN interface will go to that LAN interface, but any reply packet will go out the LAST LAN INTERFACE ifconfig'd UP on that IP subnet...
I believe that is the behavior you are noting here.
You can either live with this condition, or seperate the LAN Interfaces (and their associated Virtual IP's) so that they are on unique IP Subnets.
Hope this helps,
-> Brian Hackley
Ask me about telecommuting!
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