HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- NIS client configuration
Operating System - HP-UX
1833758
Members
2764
Online
110063
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
11-30-2007 03:18 AM
11-30-2007 03:18 AM
NIS client configuration
We have setup NIS environment with master and slave on 10.2 subnet, which are on AIX O/S.
I have almost 10 HPUX clients. With master NIS, everything works on my both same subnet and different subnet as I specified the ipaddress of the master in my different subnet's configuration file(/etc/rc.config.d/namesvrs).
My question is, when my master is down, my 10.4 and 10.5 subnet HPUX servers doesn't bind with the slave. And I understand it doesn't work as I hard coded in the /etc/rc.config.d/namesvrs file. I entered both ipaddresses in the /etc/rc.config.d/namesvrs file, but it only takes the last ipaddress in the file.
Can anyone know what is the solution other than having configured slave server on each subnet?
On linux in works. But that configuration file(ypbind) doesn't need to hard code the ipaddress. Just -ypset makes it all work on different subnets. I hope there must be a way in HPUX too, which I am not aware of.
Please help me.....
I have almost 10 HPUX clients. With master NIS, everything works on my both same subnet and different subnet as I specified the ipaddress of the master in my different subnet's configuration file(/etc/rc.config.d/namesvrs).
My question is, when my master is down, my 10.4 and 10.5 subnet HPUX servers doesn't bind with the slave. And I understand it doesn't work as I hard coded in the /etc/rc.config.d/namesvrs file. I entered both ipaddresses in the /etc/rc.config.d/namesvrs file, but it only takes the last ipaddress in the file.
Can anyone know what is the solution other than having configured slave server on each subnet?
On linux in works. But that configuration file(ypbind) doesn't need to hard code the ipaddress. Just -ypset makes it all work on different subnets. I hope there must be a way in HPUX too, which I am not aware of.
Please help me.....
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