Re: [xcat-user] Same short name causing makehosts problems

Sun, 22 Oct 2017 23:48:38 -0700

Hi Christian,
 
If you only want to "external" networks into "/etc/hosts", you can only all it into hosts table like exemaple 1).
 
But I noticed that your want to configure "bond0" and "ens2f1" in nics table. so I modified your nics table and hosts table a little and get the another results which near your requirements and make sure `nics` table configuration correct. The different is :  2 “external” networks in favor of “farnsworth.domain.name” are added into /etc/hosts, but it has short name with "iface".   like example 2)
 
example 1) only all "external" networks into /etc/hosts:
 
]# cat /etc/hosts
172.20.0.11 node1 node1.cluster.local
172.29.0.11 node1-imm node1-imm.cluster.local
10.0.0.38 farnsworth farnsworth.dc.foo.edu
148.143.201.25 farnsworth farnsworth.it.raboof.edu
172.40.0.11 node1-ib node1-ib.cluster.local
 
]# tabdump hosts
#node,ip,hostnames,otherinterfaces,comments,disable
"node1","172.20.0.11",,"-imm:172.29.0.11,farnsworth.dc.foo.edu:10.0.0.38,farnsworth.it.raboof.edu:148.143.201.25",,
 
]# tabdump nics
#node,nicips,nichostnamesuffixes,nichostnameprefixes,nictypes,niccustomscripts,nicnetworks,nicaliases,nicextraparams,nicdevices,nicsadapter,comments,disable
"node1","ib0!172.40.0.11","ib0!-ib",,"ib0!Infiniband,bond0!Ethernet,ens2f1!Ethernet","bond0!configbond-mtu bond0 ens1@ens1d1 mode=4@xmit_hash_policy=layer3+4@miimon=100","ib0!IPoIB,bond0!intersite,ens2f1!public",,,"bond0!MTU=9000,ens2f1!MTU=9000",,,
 
exmaple 2) configure bond0 in nics table example:
]# cat /etc/hosts
127.0.0.1 localhost
172.20.0.11 node1 node1.cluster.local
172.29.0.11 node1-imm node1-imm.cluster.local
148.143.201.25 node1-ens2f1 farnsworth.it.raboof.edu
172.40.0.11 node1-ib node1-ib.cluster.local
10.0.0.38 node1-bond0 farnsworth.dc.foo.edu
 
]# lsdef node1 |grep nic
    nicaliases.bond0=farnsworth.dc.foo.edu
    nicaliases.ens2f1=farnsworth.it.raboof.edu
    niccustomscripts.bond0=configbond-mtu bond0 ens1@ens1d1 mode=4@xmit_hash_policy=layer3+4@miimon=100
    nicdevices.bond0=MTU=9000
    nicdevices.ens2f1=MTU=9000
    nichostnamesuffixes.ib0=-ib
    nicips.ib0=172.40.0.11
    nicips.bond0=10.0.0.38
    nicips.ens2f1=148.143.201.25
    nicnetworks.ib0=IPoIB
    nicnetworks.bond0=intersite
    nicnetworks.ens2f1=public
    nictypes.ib0=Infiniband
    nictypes.bond0=Ethernet
    nictypes.ens2f1=Ethernet
 
]# tabdump hosts
#node,ip,hostnames,otherinterfaces,comments,disable
"node1","172.20.0.11",,"-imm:172.29.0.11",,
 
 
 
Best Regards
--------------------------------------------------
Yuan Bai (白媛)

CSTL HPC System Management Development
Tel:86-10-82451401
E-mail: by...@cn.ibm.com
Address: IBM ZGC Campus. Ring Building 28,
ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian District,
Beijing P.R.China 100193

IBM环宇大厦
北京市海淀区东北旺西路8号，中关村软件园28号楼
邮编:100193
 
 
----- Original message -----
From: Christian Caruthers <ccaruth...@lenovo.com>
To: "xCAT Users Mailing list (xcat-user@lists.sourceforge.net)" <xcat-user@lists.sourceforge.net>
Cc:
Subject: [xcat-user] Same short name causing makehosts problems
Date: Sat, Oct 21, 2017 2:46 AM
 

Running version 2.13.5.POST107.g8489de8

 

I have a handful on nodes that use the same short name on 2 networks. Here’s what it should look like:

 

node1.cluster.local 172.20.0.11

node1-imm.cluster.local 172.29.0.11

node1-ib.cluster.local 172.40.0.11

farnsworth.dc.foo.edu 10.0.0.38

farnsworth.it.raboof.edu 148.143.201.25

 

Networks setup is:

#netname,net,mask,mgtifname,gateway,dhcpserver,tftpserver,nameservers,ntpservers,logservers,dynamicrange,staticrange,staticrangeincrement,nodehostname,ddnsdomain,vlanid,domain,mtu,comments,disable

"provision","172.20.0.0","255.255.255.0","ens3",,,"172.20.0.2",,"172.20.0.1",,"172.20.0.200-172.20.0.250",,,,,,,,,

"imm","172.29.0.0","255.255.255.0","ens3",,,"172.29.0.2",,,,,,,,,,,,,

"infra","172.30.0.0","255.255.255.0","ens3",,,"172.30.0.2",,,,,,,,,,,,,

"IPoIB","172.40.0.0","255.255.255.0","ens3",,,"172.40.0.2",,,,,,,,,,,,,

"intersite","10.0.0.0","255.255.255.0","ens8",,,,,,,,,,,,,"dc.foo.edu",, ,

"public","148.143.201.0","255.255.255.224",,"149.165.232.1",,,,,,,,,,,,"it.raboof.edu",,,

 

If I set up the provisioning and IMM IPs in the hosts table w/ everything else defined in nics, I see:

 

Node setup:

Nics table: "node1","ib0!172.40.0.11,bond0!10.0.0.38,ens2f1!148.143.201.25","ib0!-ib",,"ib0!Infiniband,bond0!Ethernet,ens2f1!Ethernet","bond0!configbond-mtu bond0 ens1@ens1d1 mode=4@xmit_hash_policy=layer3+4@miimon=100","ib0!IPoIB,bond0!intersite,ens2f1!public",”bond0!farnsworth,ens2f1!farnsworth”,"bond0!MTU=9000,ens2f1!MTU=9000",,,,

 

Hosts table: "node1","172.20.0.11",,"-imm:172.29.0.11",,

 

After running makehosts –n, I see:

 

172.20.0.17 node1 node1.cluster.local

172.29.0.17 node1-imm node1-imm.cluster.local

148.143.201.25 node1-ens2f1 node1-ens2f1.it.raboof.edu farnsworth

172.40.0.17 node1-ib node1-ib.cluster.local

10.0.0.38 node1-bond0 node1-bond0.dc.foo.edu

 

Note that it creates an alias for farnsworth (which won’t work for our purposes), but ignores the setting for the 10.0.0.0/bond0 net/interface. In order to get rid of the alias and just enter the node in hosts as “farnsworth.dc.foo.edu” or “farnsworth.it.raboof.edu,” I can enter them in the hosts.otherinterfaces field for the node, but again it will only enter 1 in the hosts file correctly. The other will have the “-iface” name and maybe an alias if it’s defined in the nics table (which won’t work for us). I’ve also tried adding the external name as an unmanaged node and creating entries in the hosts table like:

 

“node1”,”172.20.0.11”,,”-imm:172.29.0.11,farnsworth: 148.143.201.25”,,

“farnsworth”,” 10.0.0.38”,,,”node1 inter-site link”,

 

This leaves me with:

 

172.20.0.17 node1 node1.cluster.local

172.29.0.17 node1-imm node1-imm.cluster.local

148.143.201.25 farnsworth farnsworth.it.raboof.edu

172.40.0.17 node1-ib node1-ib.cluster.local

10.0.0.38 node1-bond0 node1-bond0.dc.foo.edu

 

The goal is to do away with the “-iface” host name on the 2 “external” networks in favor of just “farnsworth.domain.name” So far, I can only get one to work correctly.

 

Regards,
Christian Caruthers
Lenovo Professional Services

Mobile: 757-289-9872

 

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! https://urldefense.proofpoint.com/v2/url?u=http-3A__sdm.link_slashdot&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=uiTcPxjMR44SPRNNb6l_nA&m=9hOJ-W4_Xt9TQzjsWhh6bIWQfYL_8EDXp9Kr98gQxfo&s=xYWXCFOOHSsCIq0G1rRL9jfZfjuMKq-OVj6Ar-LqbzM&e=
 

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to