Unsolved
This post is more than 5 years old
12 Posts
0
1244
August 8th, 2014 01:00
Powerpath Viewer / Name resolution of discovered hosts
Hi,
i'm having some trouble (cosmeticswise only though, but customer is complaining and wants it to be fixed) with name resolution in the powerpath viewer console. The majority of my servers get resolved by their FQDN during discovery, but some only appear with their NETBIOS name or even only with their IP address. There's no obvious difference in their IP-settings (so DNS- or WINS-stuff and similar) which I could tell from comparing 2 nodes of the same cluster, one of which appears with FQDN while the other shows up as IP address. I have other examples where 1 node gets fully resolved and the other one shows up with the NETBIOS name and such where both appear with NETBIOS name or a combination of NETBIOS and IP.
Attached is a screenshot to show what it looks like. In this picture, clusters 441/442, 481/482 (no LUNs anymore though), 501/502 are fine, 461/462 have NETBIOS and IP (10.144.184.144) and 521/522 have FQDN/IP (10.144.184.156).
I'm heavily assuming that it must be something in DNS, reverse lookup or similar. If i'm doing an nslookup for each given node, no matter if it's fully resolved or not, i'm getting back its FQDN properly.
Powerpath Viewer Version is 1.0.2.00.00.b019, Powerpath Management Component is set up identically using the defaults (attached).
Any ideas?
Cheers, Wolfi
Wolfi72
12 Posts
0
August 8th, 2014 04:00
Well, the hosts-file is not maintained (since yeah, they have naming services running^^). IP Config in terms of name and domain is set up likewise on all servers, so hostname XYZ, domain de.xyz.abc.com, primary DNS suffix identical, primary and secondary DNS servers identical, no WINS. They have a stringent deployment procedure for their physical servers that doesn't deviate from the defined standard on individual hosts. So there's no differences among hosts which could render this behaviour.
dynamox
9 Legend
•
20.4K Posts
0
August 8th, 2014 04:00
do you know if those servers that come in incorrectly, do they have multiple NICs ?
dynamox
9 Legend
•
20.4K Posts
0
August 8th, 2014 04:00
what about the hosts themselves, how is the host name configured there ? For example on Linux i would look in /etc/hosts, /etc/sysconfig/network
dynamox
9 Legend
•
20.4K Posts
0
August 8th, 2014 05:00
exactly, as if it's "binding" to the wrong NIC or something ? There should be a place in TCP configuration where you can look and binding, can't remember from the top of my head. Interesting to check if that differs between the hosts.
Wolfi72
12 Posts
0
August 8th, 2014 05:00
Yeah, they have. They're actually HP C7000 Blades (Gen8) with 2 dual port Emulex CNAs (but HP OEM stuff) that carry both Ethernet- and FCoE traffic. Each CNA is personalized as FCoE on one port and as NIC on the other. NICs do form a team, FCoE paths are Powerpath-protected.
Each server is equipped with a bunch of IP addresses, but Powerpath Viewer discovery is pointing at the DNS name of course: i have multiple .csv files in place for different datacenters to distinguish among groupwise in PP viewer, just containing the server names, not FQDN. I have tried to go for FQDN during discovery, but no change: PP viewer says "connected", but states either the NETBIOS name or the IP.
Are you going for something similar as with Unisphere Host Agent and the agentid.txt file to make sure a server registers properly in a VNX?
Wolfi72
12 Posts
0
August 8th, 2014 06:00
Might be worthwile to check, I agree. But I doubt that it's differently done on the nodes that are properly displayed vs. the screwed ones. I'll check next week when i'm back onsite. It's a bit complicated since the binding stuff is in this case seems to be covered by HP means (NCU) that also do the NIC teaming and so on. will get back to you once I figured it out.