Dell - Internal Use - Confidential Hi Luke,
Thanks for your replay ! :) The problem seems to be solved by changing the slot for the 10g card from slot3 to slot1. but personally I think that by using "ksdevice=bootif" it was resolved also. Thanks a lot Luke ! Aviv -----Original Message----- From: Luke Bigum [mailto:[email protected]] Sent: Tuesday, March 7, 2017 11:23 AM To: Graupen, Aviv <[email protected]>; linux-poweredge-Lists <[email protected]> Subject: Re: [Linux-PowerEdge] R730 - How do I Control the Ordering of network interfaces With biosdevname=0 I think you are at the mercy of whatever order the kernel decides to scan devices in. The only way to force this is to write custom Udev rules as I mentioned below - you can then call them anything you like, it doesn't have to be ethX. However, please iterate to your client that what they are depending on is brittle (as they have just discovered) - it's very hardware specific and kernel specific. The order will may change between Red Hat releases or if you move a PCI card around. I would suggest that whatever is depending on 1Gig interfaces being eth0-3 be made smarter; like to search for 1Gig interfaces. Otherwise you'll be continually tweaking your Udev rule creation script to handle different hardware. -- Luke Bigum Lead Engineer Information Systems Ph: +44 (0) 20 3192 2520 ----- Original Message ----- From: "Aviv Graupen" <[email protected]> To: [email protected], [email protected] Cc: [email protected], "luke bigum" <[email protected]> Sent: Monday, 6 March, 2017 17:32:32 Subject: RE: [Linux-PowerEdge] R730 - How do I Control the Ordering of network interfaces Dell - Internal Use - Confidential Hi All, Thanks for your replay Luke & Stefan. It was very helpful :) I hope everyone can see this as well: Before I transfer the information to the customer per your suggestion below - I would like to emphasis the customer issue once more - customer is saying: The naming of the interfaces with "biosdevname=0" is ok (eth0,eth1) - That's not the issue - We need to make sure that RHEL installer will recognize 1G interfaces as eth0 eth1 eth2 and eth3 and 10G interfaces as eth4 and eth5 1G interfaces should be eth0-eth3 ; 10G interfaces should be eth4-eth5 ; But they are not. (See attached picture please.) BTW this issue is only on R630 servers - On R730xd the interfaces are appearing in the correct order according to the customer. Any advise ? Thanks Aviv -----Original Message----- From: Luke Bigum [mailto:[email protected]] Sent: Monday, March 6, 2017 4:49 PM To: Graupen, Aviv <[email protected]> Cc: Stefan M. Radman <[email protected]> Subject: Re: [Linux-PowerEdge] R730 - How do I Control the Ordering of network interfaces Stefan's suggestion should solve Anaconda (PXE boot and install), and it might even do the udev rule I suggest below for you too. Your second issue, where once Red Hat is installed you want to detect the NDC "first"... The only reason I can think of wanting to do this would be to control the labelling of the NDCs so they appear as eth0 and eth1 (if biosdevname is off), I'm pretty sure this has to do with what order the kernel decides to enumerate devices and load modules. The official way to handle this is use biosdevname, but if you really don't want to do that you could write persistent udev rules yourself, say from your kickstart file. Something like this: [root@server ~]$ cat /etc/udev/rules.d/70-persistent-cd.rules SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="54:52:00:00:00:00", ATTR{type}=="1", KERNEL=="eth*", NAME="eth251" And then on first boot your server will come up with the NDC cards "first" (in terms of naming). I can't think of any other reason to change the order of network cards on boot? Happy to discuss the problem further if you get more info from the client. -- Luke Bigum Lead Engineer Information Systems Ph: +44 (0) 20 3192 2520 ----- Original Message ----- From: "Stefan M. Radman" <[email protected]> To: "Aviv Graupen" <[email protected]> Cc: "luke bigum" <[email protected]> Sent: Monday, 6 March, 2017 14:20:27 Subject: Re: [Linux-PowerEdge] R730 - How do I Control the Ordering of network interfaces Hi Aviv, Try using "ksdevice=bootif" in your Anaconda configuration. Your customer seem to be suffering from the default kickstart behavior which uses the first device with a usable link (ksdevice=link). ksdevice=bootif should ensure that kickstart can proceed over the same device the machine was PXE-booted from. See references below for details. Stefan Kickstart servers with multiple network interfaces http://prefetch.net/blog/index.php/2009/06/13/kickstart-servers-with-multiple-network-interfaces/ RHEL6.8 Installation Guide 32.10. Starting a Kickstart Installation https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-startinginstall.html Anaconda Boot Options https://rhinstaller.github.io/anaconda/boot-options.html RHEL7 Installation Guide 20.1.1. Deprecated and Removed Boot Options https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/chap-anaconda-boot-options.html On Mar 6, 2017, at 2:20 PM, [email protected]<mailto:[email protected]> wrote: Dell - Internal Use - Confidential Hi All, Thanks for your replay at [email protected]<mailto:[email protected]> regarding this issue: My customer is using a few network interfaces on his R730 server, such as: NDC and PCIe network cards. (running Red hat 7). During POST the PCIe network cards are booting first, instead of the NDC , my question is how do I Control the Ordering of Network Interfaces - NDC before PCIe network card ? is it BIOS settings or Linux rule ? Thanks, Aviv I would like add a few more things : In general, this is nothing to do with boot order of network interfaces - at this point there is only one interface is connected on the server (R730) , and it's booting properly form PXE server, and starting the installation. The customer already using biosdevname=0 option in PXE boot, and kernel parameters after the installation in grub.conf file - So naming is not the issue here. In both cases, when using biosdevname=0 or not, 10G interfaces were recognized by installer as a first two interfaces. Customer would like to change the order that RHEL 6 installer recognizes the network cards during the installation and after reboot too, and not the naming or boot order. Any advice ? Thanks Aviv Aviv Graupen Product Technologist Senior Advisor OEM Solutions Dell EMC T-972 9 769 8056 F-972 9 769 8301 M-972 54 4536537 [email protected]<mailto:[email protected]> --- LMAX Exchange, Yellow Building, 1A Nicholas Road, London W11 4AN http://www.LMAX.com/ Recognised by the most prestigious business and technology awards 2016 Best Trading & Execution, HFM US Technology Awards 2016, 2015, 2014, 2013 Best FX Trading Venue - ECN/MTF, WSL Institutional Trading Awards 2016, 2015 Winner, Deloitte UK Technology Fast 50 2015, 2014, 2013, One of the UK's fastest growing technology firms, The Sunday Times Tech Track 100 2016, 2015 Winner, Deloitte EMEA Technology Fast 500 2015, 2014, 2013 Best Margin Sector Platform, Profit & Loss Readers' Choice Awards --- FX and CFDs are leveraged products that can result in losses exceeding your deposit. They are not suitable for everyone so please ensure you fully understand the risks involved. This message and its attachments are confidential, may not be disclosed or used by any person other than the addressee and are intended only for the named recipient(s). This message is not intended for any recipient(s) who based on their nationality, place of business, domicile or for any other reason, is/are subject to local laws or regulations which prohibit the provision of such products and services. This message is subject to the following terms (http://lmax.com/pdf/general-disclaimers.pdf), if you cannot access these, please notify us by replying to this email and we will send you the terms. If you are not the intended recipient, please notify the sender immediately and delete any copies of this message. LMAX Exchange is the trading name of LMAX Limited. LMAX Limited operates a multilateral trading facility. LMAX Limited is authorised and regulated by the Financial Conduct Authority (firm registration number 509778) and is a company registered in England and Wales (number 6505809). LMAX Hong Kong Limited is a wholly-owned subsidiary of LMAX Limited. LMAX Hong Kong is licensed by the Securities and Futures Commission in Hong Kong to conduct Type 3 (leveraged foreign exchange trading) regulated activity with CE Number BDV088. --- LMAX Exchange, Yellow Building, 1A Nicholas Road, London W11 4AN http://www.LMAX.com/ Recognised by the most prestigious business and technology awards 2016 Best Trading & Execution, HFM US Technology Awards 2016, 2015, 2014, 2013 Best FX Trading Venue - ECN/MTF, WSL Institutional Trading Awards 2016, 2015 Winner, Deloitte UK Technology Fast 50 2015, 2014, 2013, One of the UK's fastest growing technology firms, The Sunday Times Tech Track 100 2016, 2015 Winner, Deloitte EMEA Technology Fast 500 2015, 2014, 2013 Best Margin Sector Platform, Profit & Loss Readers' Choice Awards --- FX and CFDs are leveraged products that can result in losses exceeding your deposit. They are not suitable for everyone so please ensure you fully understand the risks involved. This message and its attachments are confidential, may not be disclosed or used by any person other than the addressee and are intended only for the named recipient(s). This message is not intended for any recipient(s) who based on their nationality, place of business, domicile or for any other reason, is/are subject to local laws or regulations which prohibit the provision of such products and services. This message is subject to the following terms (http://lmax.com/pdf/general-disclaimers.pdf), if you cannot access these, please notify us by replying to this email and we will send you the terms. If you are not the intended recipient, please notify the sender immediately and delete any copies of this message. LMAX Exchange is the trading name of LMAX Limited. LMAX Limited operates a multilateral trading facility. LMAX Limited is authorised and regulated by the Financial Conduct Authority (firm registration number 509778) and is a company registered in England and Wales (number 6505809). LMAX Hong Kong Limited is a wholly-owned subsidiary of LMAX Limited. LMAX Hong Kong is licensed by the Securities and Futures Commission in Hong Kong to conduct Type 3 (leveraged foreign exchange trading) regulated activity with CE Number BDV088. _______________________________________________ Linux-PowerEdge mailing list [email protected] https://lists.us.dell.com/mailman/listinfo/linux-poweredge
