On 2/25/19 10:04 AM, Er Tao Zhao wrote:
Hi, Thomas
Yeah, I agree with Kevin that if you not plan to bond eth0 and eth2,
you'd better set then in different VLAN.
But if eth0 and eth2 are in same vlan, xCAT can deal with it after xCAT 2.13
Will you pls show me the output of `lsdef tars-113`
And can `tars-113-eth0` or `tars-113-eth2` can be resolved to the same
ip with `tars-113` in your DNS? And can be get from MN?
For example `ping tars-113-eth0` or `ping tars-113-eth2` can get same ip
in node `xcat-tars`
Hello,
as I said, sorry for the delay I've been in vacation then busy.
A quick reminder :
Nodes are normally physically configured like this :
conf 1:
a) eth0 -> switch A (1G) : ipmi (ipmi subnet) traffic allowed
b) eth2 -> switch B (10G) : only data (data subnet) traffic allowed
and logically configured to get switch-based discovered using swith B
I did configure on purpose one node/port like this :
conf 2:
a) eth0 -> switch A (1G) : data (data subnet) + ipmi (ipmi subnet)
traffic allowed
b) eth2 -> switch B (10G) : data (data subnet) only traffic allowed
precisely to be able to handle (by knowing what's happening and/or
forcing eth2 install) a switch misconfiguration which would result to
the conf2 above [and at the time I wrote my initial message, a BIOS boot
order misconfiguration too, but I'm not so sure it has something to do
with the MAC address ending up in the mac table]
What I'm seeing on the console is basically, once loaded and having got
an ip address on the BOOTIF nic ('Aquiring network address message'),
genesis getting 2 ips from the dynamic range by DHCP, one for each nic
after the 'Beginin node discovery process' message and the final MAC
registration in the mac table beeing for the eth0 nic despite the fact that
- discoverydata entry for tars-113 was cleared beforehand
- switch-based discovery attributes where those of eth2 (switch B)
So the node gets finally netbooted via eth0, which is not what I'd want.
- lsdef tars-113 beforehand was :
---
# <xCAT data object stanza file>
tars-113:
objtype=node
addkcmdline=ipv6.disable=1 biosdevname=0 net.ifnames=0
rd.driver.blacklist=nouveau nouveau.modeset=0
arch=x86_64
bmc=10.6.96.115
bmcpassword=XXX
bmcport=0
bmcusername=XXXX
chain=runcmd=bmcsetup,runimage=http://xcat-tars/install/sum_activate/sum_activate.tgz,osimage=centos6.10-x86_64-netboot-compute-prod
groups=tars-compute,tars-ipmi,tars,standard,b10
ip=192.168.128.115
mgt=ipmi
os=centos6.10
profile=compute
provmethod=centos6.10-x86_64-netboot-compute-prod
supportedarchs=x86,x86_64
switch=b10b4.dc1.pasteur.fr
switchport=8
- lsdef afterwards is
Object name: tars-113
addkcmdline=ipv6.disable=1 biosdevname=0 net.ifnames=0
rd.driver.blacklist=nouveau nouveau.modeset=0
arch=x86_64
bmc=10.6.96.115
bmcpassword=XXXX
bmcport=0
bmcusername=XXXX
chain=runcmd=bmcsetup,osimage=centos6.10-x86_64-netboot-compute-prod
cpucount=12
cputype=Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz
currstate=netboot centos6.10-x86_64-compute
disksize=sda:256GB
groups=tars-compute,tars-ipmi,tars,standard,b10
initrd=xcat/osimage/centos6.10-x86_64-netboot-compute-prod/initrd-stateless.gz
ip=192.168.128.115
kcmdline=imgurl=http://!myipfn!:80//install/netboot/centos6.10/x86_64/compute/prod/rootimg.gz
XCAT=!myipfn!:3001 NODE=tars-113 FC=0
kernel=xcat/osimage/centos6.10-x86_64-netboot-compute-prod/kernel
mac=0c:c4:7a:4d:85:a8|0c:c4:7a:58:c7:6a!*NOIP*
memory=258373MB
mgt=ipmi
netboot=xnba
os=centos6.10
postbootscripts=otherpkgs
profile=compute
provmethod=centos6.10-x86_64-netboot-compute-prod
serial=E162178X5A02118
status=booted
statustime=03-20-2019 17:55:02
supportedarchs=x86,x86_64
switch=b10b4.dc1.pasteur.fr
switchport=8
- neither tars-113-eth0 nor tars-113-eth2 (fully qualified or not) can
be resolved
Again, the actual need is not to have 2 nics on the same subnet but to
have some way to choose which MAC will get discovered if so.
Does BIOS PXE order makes any difference to what nic gets into the mac
address at the end ?
Which nic does genesis picks up between the 2 to put in the mac address ?
Does a discovery happen on each nic ?
It seems like genesis actually did the switch-based discovery but
registered the first MAC it saw, thus the mismatch
Thanks.
--
Thomas H.
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
