"primarynic" has been deprecated
#tabdump -d noderes
> installnic: The network adapter on the node that will be used for OS deployment, the installnic can be set to the network adapter name or the mac address or the keyword "mac" which means that the network interface specified by the mac address in the mac table will be used. If not set, primarynic will be used. If primarynic is not set too, the keyword "mac" will be used as default.
> primarynic: This attribute will be deprecated. All the used network interface will be determined by installnic. The network adapter on the node that will be used for xCAT management, the primarynic can be set to the network adapter name or the mac address or the keyword "mac" which means that the network interface specified by the mac address in the mac table will be used. Default is eth0.
------------------------------------------------------------------------------
YANG Song (杨嵩)
IBM China System Technology Laboratory
Tel: 86-10-82452903
Email: yang...@cn.ibm.com
Address: Building 28, ZhongGuanCun Software Park,
No.8, Dong Bei Wang West Road, Haidian District Beijing 100193, PRC
北京市海淀区东北旺西路8号中关村软件园28号楼
邮编: 100193
YANG Song (杨嵩)
IBM China System Technology Laboratory
Tel: 86-10-82452903
Email: yang...@cn.ibm.com
Address: Building 28, ZhongGuanCun Software Park,
No.8, Dong Bei Wang West Road, Haidian District Beijing 100193, PRC
北京市海淀区东北旺西路8号中关村软件园28号楼
邮编: 100193
----- Original message -----
From: Jarrod Johnson <jjohns...@lenovo.com>
To: xCAT Users Mailing list <xcat-user@lists.sourceforge.net>
Cc:
Subject: Re: [xcat-user] [External] xnba, noderes nics and BOOTIF
Date: Wed, Jan 23, 2019 5:37 AM
Correct, BIOS order.
installnic does get passed to the stateless boot. Honestly, I haven't had use for using installnic differently than primarynic in a long time. Primarynic I generally leave empty (defaulting to BOOTIF from firmware behavior) except when doing install over omnipath or infiniband. I usually consider the high speed network to be 'neither' and just think of primarynic as the deployment nic. I think this was born out of dealing with a few scenarios where a two-nic scheme was too limiting so I just used one of the 'hard' baked nics and used more open ended facilities for 'the rest of the nics'. In short, I am going to be rusty on the use of the installnic attribute, but I do see it in the code.
-----Original Message-----
From: Thomas HUMMEL <thomas.hum...@pasteur.fr>
Sent: Tuesday, January 22, 2019 3:21 PM
To: xcat-user@lists.sourceforge.net
Subject: Re: [xcat-user] [External] xnba, noderes nics and BOOTIF
On 1/22/19 3:55 PM, Jarrod Johnson wrote:
> So BOOTIF is expanded by xnba (or elilo with xnba) to be 'the mac address of whatever network adapter successfully performed PXE'. The expansion is done client side prior to linux running.
Thanks for your answer.
So it goes like this :
- the node firmware does its native PXE
- the node receive xnba
- xnba tries serveral PXE (in what order ? BIOS order ?) and expands BOOTIF for what follows
correct ?
> There is some extended syntax to support multiple network cards that can be tricky, so we used client-side expansion of the mac address where possible. Also supporting multiple interfaces is a bit easier.
Are you talking about
https://xcat-docs.readthedocs.io/en/stable/advanced/domain_name_resolution/domain_name_resolution.html#specifying-additional-network-interfaces-for-cluster-nodes
?
What about installnic in noderes table ? Is this for stateful only ?
Thanks for your help
--
Thomas HUMMEL
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
_______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
