On 2/20/19 4:43 AM, Er Tao Zhao wrote:
Hi, Thomas
Can tars-113-eth2 be resolved to 192.168.128.115 from your DNS server?
Can you show us the entry in /var/lib/dhcpd/dhcpd.leases for MAC of eth0
and eth2?
Sure but in what scenario ? I did so many tests ;-)
Here's what I tested again starting from a "clean state" :
Note : 1in every test, the node PXE on eth0 (BIOS configured) and
192.168.128.115 is the ip address I'd like to have on eth2
a) scenario 1 :
- nics.nicps : eth2 only
"tars-113","eth2!192.168.128.115",,,,,,,,,
results in
- mac :
tars-113",,"0c:c4:7a:4d:85:a8|0c:c4:7a:58:c7:6a!*NOIP*",,
- node's eth0 carrying the 192.168.128.115
IP on the node (because it has PXE booted on it)
- only DNS records for tars-113, not tars-113-eth2
- leases file :
host and lease sections at the end of the lease file (0c:c4:7a:4d:85:a8
is eth0, 0c:c4:7a:58:c7:6a is eth2)
host tars-113 {
dynamic;
hardware ethernet 0c:c4:7a:4d:85:a8;
fixed-address 192.168.128.115;
supersede server.ddns-hostname = "tars-113";
supersede host-name = "tars-113";
if option user-class-identifier = "xNBA" and option
client-architecture = 00:00 {
supersede server.always-broadcast = 01;
supersede server.filename =
"http://${next-server}/tftpboot/xcat/xnba/nodes/tars-113";;
} elsif option user-class-identifier = "xNBA" and option
client-architecture = 00:09 {
supersede server.filename =
"http://${next-server}/tftpboot/xcat/xnba/nodes/tars-113.uefi";;
} elsif option client-architecture = 00:07 {
supersede server.filename = "xcat/xnba.efi";
} elsif option client-architecture = 00:00 {
supersede server.filename = "xcat/xnba.kpxe";
} else {
supersede server.filename = "";
}
}
host tars-113-noip0cc47a58c76a {
dynamic;
deleted;
}
host tars-113-noip0cc47a58c76a {
dynamic;
hardware ethernet 0c:c4:7a:58:c7:6a;
supersede server.allow-booting = 00;
}
lease 192.168.134.255 {
starts 3 2019/02/20 13:21:51;
ends 3 2019/02/20 13:25:15;
tstp 3 2019/02/20 13:25:15;
cltt 3 2019/02/20 13:21:51;
binding state free;
hardware ethernet 0c:c4:7a:4d:85:a8;
uid "\000\000\000\000\000\000\000\000\000\000\000\014\304zM\205\250";
}
lease 192.168.135.0 {
starts 3 2019/02/20 13:21:52;
ends 3 2019/02/20 13:25:15;
tstp 3 2019/02/20 13:25:15;
cltt 3 2019/02/20 13:21:52;
binding state free;
hardware ethernet 0c:c4:7a:4d:85:a8;
uid "\001\014\304zM\205\250";
}
b) scenario 2
When I don't use nicips at all, I've only have a DNS record for
tars-113, not for tars-113-eth2.
Note : Before those 2 scenarii I had, probably coming from a previous
test I don't quite remember, a CNAME for tars-113-eth2 pointing to
tars-113 indeed. I ran the 2 scenarii above after I cleaned the zone
(i.e. remove all tars-113 related records, dans add the node again)
So I'm confused about the use of nics.nicips...
Thanks!
--
Thomas Hummel
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
