Hello,
I apologize for opening yet another thread but I think what I'll detail
in it deserves it.
In short, I'm trying to figure out what's happening when discovery is
done on a node which has BOTH eth0 (switch A) and eth2 (switch B) on
switch ports configured on the same vlan. My nodes are only configured
with one ip (in hosts table) and has the switch and switchport
attributes to get used by switch-based discovery on switchB.
When BIOS/Intel Boot Agent PXE on eth2, here's what the log says :
1) genesis gets the nics configured and retrieve an ip from the dynamic
range :
eth2 : 2019-02-22T18:16:32.004867+01:00 xcat-tars dhcpd: DHCPACK on
192.168.134.252 to 0c:c4:7a:58:c7:6a via eth1
eth0 : 2019-02-22T18:16:39.003422+01:00 xcat-tars dhcpd: DHCPACK on
192.168.134.250 to 0c:c4:7a:4d:85:a8 via eth1
2) discovery begins on eth2
2019-02-22T18:16:44.320279+01:00 xcat-tars xcat[60918]: xcatd:
Processing discovery request from 192.168.134.252
3) discovery has seen that it was for the tars-113 node :
2019-02-22T18:16:57.162396+01:00 xcat-tars xcat[60918]: Discover info:
configure static BMC ip:10.6.96.115 for host_node:tars-113.
4) eth0 and eth2 leases are released :
2019-02-22T18:16:59.621541+01:00 xcat-tars dhcpd: DHCPRELEASE of
192.168.134.250 from 0c:c4:7a:4d:85:a8 via eth1 (found)
2019-02-22T18:16:59.664557+01:00 xcat-tars dhcpd: DHCPRELEASE of
192.168.134.252 from 0c:c4:7a:58:c7:6a via eth1 (found)
-> because discovery is resolved ?
5) I've got those messages
2019-02-22T18:16:59.752892+01:00 xcat-tars xcatd: Discovery worker:
switch instance: nodediscover instance[60918]: tars-113 has been discovered
2019-02-22T18:16:59.754145+01:00 xcat-tars xcat[60918]: Discovery Error:
Could not find any node.
-> I'm not really sure it the "tars-113 has been discovered" is related
to point number 3 (order of messages mixed in logs) or something else : ?
-> I'm not really sure why the "Could not find any node" message :
-> Are there 2 discovery process running and racing against each other
(one per nic) ?
6) eth0 gets the desired ip (the ip set in the node def)
2019-02-22T18:17:00.000095+01:00 xcat-tars dhcpd: DHCPDISCOVER from
0c:c4:7a:4d:85:a8 via eth1
2019-02-22T18:17:00.000116+01:00 xcat-tars dhcpd: DHCPOFFER on
192.168.128.115 to 0c:c4:7a:4d:85:a8 via eth1
2019-02-22T18:17:00.000433+01:00 xcat-tars dhcpd: DHCPREQUEST for
192.168.128.115 (192.168.132.2) from 0c:c4:7a:4d:85:a8 via eth1
2019-02-22T18:17:00.000442+01:00 xcat-tars dhcpd: DHCPACK on
192.168.128.115 to 0c:c4:7a:4d:85:a8 via eth1
-> why as discovery seems to have been done on eth2 ?
7) eth2 asks for an ip but is denied to boot :
2019-02-22T18:17:01.001030+01:00 xcat-tars dhcpd: DHCPDISCOVER from
0c:c4:7a:58:c7:6a via eth1: booting disallowed
8) I've got this message I don't fully understand either :
2019-02-22T18:17:01.500387+01:00 xcat-tars xcatd: Discovery worker:
switch instance: nodediscover instance[60918]: Failed to notify
192.168.134.252 that it's actually tars-113.
So, granted, my setup is bogus but I keep it that way for learning
purpose and in the hope I'll be able to figure out how nic related
attributes (installnic, nicips) are meant to be used.
Thanks!
--
Thomas Hummel
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
