On 2/18/19 4:30 PM, Thomas HUMMEL wrote:
Hello,
I'll try to sum up here (sorry for the new thread) the quesions I have
left about nics in a stateless mode after some (unsuccessfull) tests and
posts.
Thanks everyone for your time and help.
So basically here's my conclusion (I'm very confuse
Am I right assuming it makes no sense to set in the noderes table
noderes.installnic to a different interface/mac than the one the node is
bios-configured to boot from (at least in a stateless mode) ?
Thanks.
--
Thomas HUMMEL
___
xCAT-user mailin
Well actually, it's when, after my first scenario, I change the nicstable to be"tars-113","192.168.130.170,eth2!192.168.128.115",
[bai] I think nicips format is wrong here. Is this ip "192.168.130.170" for install nic? If it is for installnic, it should not be configured in nics table. The
Let me put this another way or at least ask related questions :
1) what I think is happening in general for an undiscovered node :
- native PXE boot (for instance IBA) retrieves xNBA
- xNBA PXE retrieves the "net" gpxe script which downloads and loads the
discovery image
- discovery image issu
On 2/20/19 2:51 PM, Thomas HUMMEL wrote:
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
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 f
On 2/20/19 4:45 AM, Bin XA Xu wrote:
Hi Thomas,
Hello, thanks for your time
I don't think 'noderes.installnic' could meet your expectation:
PXE from eth0, but set IP to eth2 after provisioning (DHCP or static).
Obviously your right since it doesn't work. I'm still curious about what
Hi Thomas,
I don't think 'noderes.installnic' could meet your expectation: PXE from eth0, but set IP to eth2 after provisioning (DHCP or static).
I'm still curious about your new discovering, looks like it is discovered by eth0 with other method, instead of eth2 with switch based disco
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?
Thx!
Best Regards,---Zhao Er TaoIBM China System and Technology Laboratory, BeijingTel:(86-10)
On 2/19/19 11:20 AM, Yuan Y Bai wrote:
Hi Thomas
To set install NIC with static ip, you can follow these steps:
ok thanks
*nics.nicips* is mainly used for secondary nics, it contains
comma-separated list of IP addresses per NIC.You can refer to usage
command: `tabdump -d nics|grep nicips`
Hi Thomas
To set install NIC with static ip, you can follow these steps:
1.
chdef ip=
2. Use `confignetwork -s`, details refer to: https://xcat-docs.readthedocs.io/en/latest/guides/admin-guides/manage_clusters/common/deployment/network/cfg_network_ethernet_nic.html#configure-adapters-with-sta
On 2/19/19 2:34 AM, Bin XA Xu wrote:
To set static, you can use `hardeths` or `confignetwork -s`
Ok. But does it has something to do with either noderes.installnic or
nics.nicips (I still cannot figure out how to use thoses attributes).
Thanks.
--
TH
__
On 2/19/19 2:34 AM, Bin XA Xu wrote:
But it should be handled when discovering, xCAT will assign the same
IP to eth0 and eth2 during the auto-discovery.
Ertao, could you help to give more information about that?
And Thomas, could you give a `lsdef` output on your node, before
discoverin
Thanks Thomas,
The information is very clear, but it is just a bit different with xCAT typical assumption.
But it should be handled when discovering, xCAT will assign the same IP to eth0 and eth2 during the auto-discovery.
Ertao, could you help to give more information about that?
And T
So actually both eth0 and eth2 on a node are connected to the same network.
This come from the time we'd want to be able to fallback to 1Gb/s
connectivity.
--
T.
___
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.ne
On 2/18/19 5:02 PM, Bin XA Xu wrote:
Hi Thomas,
Just a bit confusing about your context. So you have a node with 2
NICs are enabled PXE boot in BIOS, and both NICs are connected in the
same network with MN's provision NIC?
If this is your case? why we have the two NIC in the same L
Hi Thomas,
Just a bit confusing about your context. So you have a node with 2 NICs are enabled PXE boot in BIOS, and both NICs are connected in the same network with MN's provision NIC?
If this is your case? why we have the two NIC in the same LAN, do you want a bonding after provision
17 matches
Mail list logo
