HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: HyperFabric configuration
Operating System - HP-UX
1829348
Members
1746
Online
109991
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
05-30-2006 02:38 AM
05-30-2006 02:38 AM
Re: HyperFabric configuration
Marius,
I talked to the lab who was puzzled by your case. Here is what I got from their analysis: not sure it will clarify your problem...
HyperFabric uses gethostbyname() to retrieve the Node Name information (Hostname & all the aliases for that Host). gethostbyname() depends on the configuration specified in nsswitch.conf. With the Node Host Name Expansion Product Bundle, HyperFabric will support 63 char hostnames.
In some cases, clic_probe is unable to connect to the HF deamon. One case is when clic_start was not executed. Another one is if the HyperFabric subsystem doesn't find the Node Name specified in clic_probe. This may happen if a Node has a 'primary' hostname & an alias associated with it and if nsswitch.conf is configured to lookup only files, then, assuming /etc/hosts mentions only the 'primary' hostname, HyperFabric will not be aware of the alias. In this case, clic_probe may return "Host not Found" or something similar when using the alias.
I am not familiar with this nsswitch.conf myself,
Regards,
Marie
I talked to the lab who was puzzled by your case. Here is what I got from their analysis: not sure it will clarify your problem...
HyperFabric uses gethostbyname() to retrieve the Node Name information (Hostname & all the aliases for that Host). gethostbyname() depends on the configuration specified in nsswitch.conf. With the Node Host Name Expansion Product Bundle, HyperFabric will support 63 char hostnames.
In some cases, clic_probe is unable to connect to the HF deamon. One case is when clic_start was not executed. Another one is if the HyperFabric subsystem doesn't find the Node Name specified in clic_probe. This may happen if a Node has a 'primary' hostname & an alias associated with it and if nsswitch.conf is configured to lookup only files, then, assuming /etc/hosts mentions only the 'primary' hostname, HyperFabric will not be aware of the alias. In this case, clic_probe may return "Host not Found" or something similar when using the alias.
I am not familiar with this nsswitch.conf myself,
Regards,
Marie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-30-2006 05:16 AM
05-30-2006 05:16 AM
Re: HyperFabric configuration
Thanks for the inquiry!
nsswitch.conf is configured to use files (/etc/hosts which contains entries for the official hostname and the alias for the IP assigned to clic0) then dns. In my case only the official hostname of the machine is registered in DNS. I could try to register the interconnect clic0 interface in dns and see if that changes anything.
I am pretty much convinced that this is normal behavior but it is strange that clic_probe does not find it. I will try to register it in DNS in see if that changes anything.
As for the hostname being too long I changed them all to contain a maximum of 8 characters.
Thanks for the feedback.
Marius
nsswitch.conf is configured to use files (/etc/hosts which contains entries for the official hostname and the alias for the IP assigned to clic0) then dns. In my case only the official hostname of the machine is registered in DNS. I could try to register the interconnect clic0 interface in dns and see if that changes anything.
I am pretty much convinced that this is normal behavior but it is strange that clic_probe does not find it. I will try to register it in DNS in see if that changes anything.
As for the hostname being too long I changed them all to contain a maximum of 8 characters.
Thanks for the feedback.
Marius
"The Linux philosophy is 'Laugh in the face of danger'. Oops. Wrong One. 'Do it yourself'. Yes, that's it." --Linus Torvalds
- « Previous
-
- 1
- 2
- Next »
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