- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Multiple NIC's
Operating System - HP-UX
1753528
Members
5231
Online
108795
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
Discussions
Discussions
Forums
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
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
тАО04-02-2003 03:30 AM
тАО04-02-2003 03:30 AM
Hi,
I have two network cards in A-Class server they are both on the same network but on different subnets by cutting up the netmask.
lan0 192.168.244.134 netmask 255.255.255.240
lan1 192.168.244.194 netmask 255.255.255.240
Only lan0 has a default router configured 192.168.244.129.
When I try and reach another network ie. 10.102.0.44, the traffic always uses interface lan1, which has no default router configured.
When I run a traceroute the message always says multiple cards configured using lan1
My question is, how do I force traffic to use lan0?
Thanks
mike
I have two network cards in A-Class server they are both on the same network but on different subnets by cutting up the netmask.
lan0 192.168.244.134 netmask 255.255.255.240
lan1 192.168.244.194 netmask 255.255.255.240
Only lan0 has a default router configured 192.168.244.129.
When I try and reach another network ie. 10.102.0.44, the traffic always uses interface lan1, which has no default router configured.
When I run a traceroute the message always says multiple cards configured using lan1
My question is, how do I force traffic to use lan0?
Thanks
mike
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-02-2003 05:19 AM
тАО04-02-2003 05:19 AM
Re: Multiple NIC's
Post your netstat -rn output. Have a look at your default route... is really lan0 listed in the "Interface" column? If not, delete the route and add it again.
Best regards...
Dietmar.
Best regards...
Dietmar.
"Logic is the beginning of wisdom; not the end." -- Spock (Star Trek VI: The Undiscovered Country)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-02-2003 05:43 AM
тАО04-02-2003 05:43 AM
Solution
Load balancing two NIC's is tricky and probably better if you separate the NIC's by two subnets.
However, several users have tried and their succusses have varied. Most are using two default rounters in some manner, or static routes in netconf.
You can use two default gateways in your netconf file, one for each lan, but only the first entered into the routing table will typically be used.
So it's best to have the NIC with the most load assigned to the default gateway.
I've also read where using the "...ip_strong_es_model ..." ndd parameter will allow dual default routers, but the results from users who've implemented this parameter appear inconsistent, based upon the manufacturer of the router and its configuration. Using proxy ARP on the router for instance.
To check ip_strong_es_model current setting use:
ndd -get /dev/ip ip_strong_es_model
To actually set it use:
ndd -set /dev/ip ip_strong_es_model 1
Here is one link about 2 nics being implemented:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x2cba3a7b3682d611abdb0090277a778c,00.html
Here is another:
http://us-support2.external.hp.com/cki/bin/doc.pl/sid=6aa57e860890b36f79/screen=ckiDisplayDocument?docId=500000000092418
However, several users have tried and their succusses have varied. Most are using two default rounters in some manner, or static routes in netconf.
You can use two default gateways in your netconf file, one for each lan, but only the first entered into the routing table will typically be used.
So it's best to have the NIC with the most load assigned to the default gateway.
I've also read where using the "...ip_strong_es_model ..." ndd parameter will allow dual default routers, but the results from users who've implemented this parameter appear inconsistent, based upon the manufacturer of the router and its configuration. Using proxy ARP on the router for instance.
To check ip_strong_es_model current setting use:
ndd -get /dev/ip ip_strong_es_model
To actually set it use:
ndd -set /dev/ip ip_strong_es_model 1
Here is one link about 2 nics being implemented:
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x2cba3a7b3682d611abdb0090277a778c,00.html
Here is another:
http://us-support2.external.hp.com/cki/bin/doc.pl/sid=6aa57e860890b36f79/screen=ckiDisplayDocument?docId=500000000092418
Support Fatherhood - Stop Family Law
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP