HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- binding nfs to NIC2...
Operating System - HP-UX
1826780
Members
1668
Online
109702
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-01-2006 07:26 AM
03-01-2006 07:26 AM
binding nfs to NIC2...
All,
I have two NIC card. I am using NIC1 as regular traffic footprint. I want to use NIC2 for nfs traffic footprint. How do I make sure NIC2 gets use as nfs traffic only; do I need to bind it to NIC2's ip address? how would I do that?
Thanks.
I have two NIC card. I am using NIC1 as regular traffic footprint. I want to use NIC2 for nfs traffic footprint. How do I make sure NIC2 gets use as nfs traffic only; do I need to bind it to NIC2's ip address? how would I do that?
Thanks.
Reputation of a thousand years can be determined by the conduct of an hour
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2006 08:37 AM
03-01-2006 08:37 AM
Re: binding nfs to NIC2...
Hi K.C.,
Well the only way you'll be able to do that is have the NFS server/client in a separate private network. Then you can set up a static route for that traffic.
IF they're on the "public" network and that traffic needs to go through a router, there's not much you can do.
I suppose IF they're on the same subnet segment - i.e. no router needed, you could setup a static route for those specific servers.
HTH,
Jeff
Well the only way you'll be able to do that is have the NFS server/client in a separate private network. Then you can set up a static route for that traffic.
IF they're on the "public" network and that traffic needs to go through a router, there's not much you can do.
I suppose IF they're on the same subnet segment - i.e. no router needed, you could setup a static route for those specific servers.
HTH,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2006 08:46 AM
03-01-2006 08:46 AM
Re: binding nfs to NIC2...
Jeff has a good idea there with the static routes. If the servers in question are on different subnets, you might be able to setup static routes on the routers as well. You network admins may not like that or be willing to support it, however.
Check the man page for route and netstat. You can see the routes that the system already knows by doing netstat -r. Given that one of the parameters for route is the interface, that alone may be sufficient to keep the traffic off the other nic.
mark
Check the man page for route and netstat. You can see the routes that the system already knows by doing netstat -r. Given that one of the parameters for route is the interface, that alone may be sufficient to keep the traffic off the other nic.
mark
the future will be a lot like now, only later
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP