network ordering

[Christopher Johnston]

So I have some servers with a few network cards installed and because the
kernel does a poor job of ordering them correctly during an install they
come up out of order (pci=bfsort does not help).  I havnt looked to deep
into the snippet just yet, but on a specific system where I have the
following:
eth0 : unconfigured
eth1 : unconfigured
eth2 : non-routeable network (heartbeat)
eth3 : configure routeable network

My BIOS is configured to PXE boot on eth3.  So in cobbler I have it setup
like so with eth0 empty, eth2 configured our private 192.168 interface and
eth3 configured with the routable interface.

interface        : eth0
  mac address    :
  bonding        :
  bonding_master :
  bonding_opts   :
  is static?     : False
  ip address     :
  subnet         :
  static routes  : []
  dns name       :
  dhcp tag       :
  virt bridge    :
interface        : eth2
  mac address    : 00:1F:29:E1:54:AE
  bonding        :
  bonding_master :
  bonding_opts   :
  is static?     : True
  ip address     : 192.168.x.x
  subnet         : 255.255.255.0
  static routes  : []
  dns name       : edge01.core.lon04.mtt
  dhcp tag       :
  virt bridge    :
interface        : eth3
  mac address    : 00:1F:29:E1:54:AC
  bonding        :
  bonding_master :
  bonding_opts   :
  is static?     : True
  ip address     : 10.x.x.x
  subnet         : 255.255.255.0
  static routes  : []
  dns name       : edge01.lon04.mtt
  dhcp tag       :
  virt bridge    :


When I look at the kickstart file, it looks to be ordering them with a
different configuration then I wanted using the "old" style config?  how do
I get it to use the "new" style config?

# Network information
# Using "old" style networking config. Make sure all MAC-addresses are in
cobbler to use the new-style config
network --bootproto=static --ip=10.123.200.36 --netmask=255.255.255.0
--gateway=10.123.200.1 --hostname=edge01.lon04.mtt --device=eth0 --onboot=on
network --bootproto=static --ip=192.168.123.36 --netmask=255.255.255.0
--gateway=10.123.200.1 --hostname=edge01.lon04.mtt --device=eth1 --onboot=on
network --bootproto=dhcp --device=eth2 --onboot=on

A few questions:

1) eth0 should not even be used, let alone why is it a requirement to have
eth2 in my cobbler system record?  I have alot of hosts where eth0 is
available but not even plumbed up.
2) eth2/eth3 are the NICs I want to use, but why did they end up going to
eth0/eth1?
3) where did the eth2 interface come into the picture here using dhcp?

[Coe, Colin C. (Unix Engineer)]

Try just bfsort on the kernel cmdline.

CC 

>  -----Original Message-----
>  From: cobbler-bounces(a)lists.fedorahosted.org 
>  [mailto:[e-mail]] On Behalf Of 
>  Christopher Johnston
>  Sent: Wednesday, 4 February 2009 9:05 AM
>  To: cobbler mailing list
>  Subject: network ordering
>  
>  So I have some servers with a few network cards installed and 
>  because the kernel does a poor job of ordering them correctly 
>  during an install they come up out of order (pci=bfsort does 
>  not help).  I havnt looked to deep into the snippet just yet, 
>  but on a specific system where I have the following:
>  
>  eth0 : unconfigured
>  eth1 : unconfigured
>  eth2 : non-routeable network (heartbeat)
>  eth3 : configure routeable network
>  
>  My BIOS is configured to PXE boot on eth3.  So in cobbler I 
>  have it setup like so with eth0 empty, eth2 configured our 
>  private 192.168 interface and eth3 configured with the 
>  routable interface.
>  
>  interface        : eth0
>  
>    mac address    : 
>    bonding        : 
>    bonding_master : 
>    bonding_opts   : 
>    is static?     : False
>    ip address     : 
>    subnet         : 
>    static routes  : []
>    dns name       : 
>    dhcp tag       : 
>    virt bridge    : 
>  interface        : eth2
>    mac address    : 00:1F:29:E1:54:AE
>    bonding        : 
>    bonding_master : 
>    bonding_opts   : 
>    is static?     : True
>    ip address     : 192.168.x.x
>    subnet         : 255.255.255.0
>    static routes  : []
>    dns name       : edge01.core.lon04.mtt
>    dhcp tag       : 
>    virt bridge    : 
>  interface        : eth3
>    mac address    : 00:1F:29:E1:54:AC
>    bonding        : 
>    bonding_master : 
>    bonding_opts   : 
>    is static?     : True
>    ip address     : 10.x.x.x
>    subnet         : 255.255.255.0
>    static routes  : []
>    dns name       : edge01.lon04.mtt
>    dhcp tag       : 
>    virt bridge    : 
>  
>  
>  When I look at the kickstart file, it looks to be ordering 
>  them with a different configuration then I wanted using the 
>  "old" style config?  how do I get it to use the "new" style config?
>  
>  # Network information
>  # Using "old" style networking config. Make sure all 
>  MAC-addresses are in cobbler to use the new-style config
>  network --bootproto=static --ip=10.123.200.36 
>  --netmask=255.255.255.0 --gateway=10.123.200.1 
>  --hostname=edge01.lon04.mtt --device=eth0 --onboot=on
>  network --bootproto=static --ip=192.168.123.36 
>  --netmask=255.255.255.0 --gateway=10.123.200.1 
>  --hostname=edge01.lon04.mtt --device=eth1 --onboot=on
>  network --bootproto=dhcp --device=eth2 --onboot=on
>  
>  A few questions:
>  
>  1) eth0 should not even be used, let alone why is it a 
>  requirement to have eth2 in my cobbler system record?  I have 
>  alot of hosts where eth0 is available but not even plumbed up.
>  2) eth2/eth3 are the NICs I want to use, but why did they end 
>  up going to eth0/eth1?
>  3) where did the eth2 interface come into the picture here using dhcp?
>  
>   
NOTICE: This email and any attachments are confidential. 
They may contain legally privileged information or 
copyright material. You must not read, copy, use or 
disclose them without authorisation. If you are not an 
intended recipient, please contact us at once by return 
email and then delete both messages and all attachments.

[Christopher Johnston]

I believe I tried both...
What im confused about is the "new-style" and "old-style" network
configuration.

On Tue, Feb 3, 2009 at 5:33 PM, Coe, Colin C. (Unix Engineer) <
Colin.Coe(a)woodside.com.au&gt; wrote:

>  Try just bfsort on the kernel cmdline.
>
>  CC
>
>  > -----Original Message-----
>  > From: cobbler-bounces(a)lists.fedorahosted.org
>  > [mailto:[e-mail]] On Behalf Of
>  > Christopher Johnston
>  > Sent: Wednesday, 4 February 2009 9:05 AM
>  > To: cobbler mailing list
>  > Subject: network ordering
>  >
>  > So I have some servers with a few network cards installed and
>  > because the kernel does a poor job of ordering them correctly
>  > during an install they come up out of order (pci=bfsort does
>  > not help).  I havnt looked to deep into the snippet just yet,
>  > but on a specific system where I have the following:
>  >
>  > eth0 : unconfigured
>  > eth1 : unconfigured
>  > eth2 : non-routeable network (heartbeat)
>  > eth3 : configure routeable network
>  >
>  > My BIOS is configured to PXE boot on eth3.  So in cobbler I
>  > have it setup like so with eth0 empty, eth2 configured our
>  > private 192.168 interface and eth3 configured with the
>  > routable interface.
>  >
>  > interface        : eth0
>  >
>  >   mac address    :
>  >   bonding        :
>  >   bonding_master :
>  >   bonding_opts   :
>  >   is static?     : False
>  >   ip address     :
>  >   subnet         :
>  >   static routes  : []
>  >   dns name       :
>  >   dhcp tag       :
>  >   virt bridge    :
>  > interface        : eth2
>  >   mac address    : 00:1F:29:E1:54:AE
>  >   bonding        :
>  >   bonding_master :
>  >   bonding_opts   :
>  >   is static?     : True
>  >   ip address     : 192.168.x.x
>  >   subnet         : 255.255.255.0
>  >   static routes  : []
>  >   dns name       : edge01.core.lon04.mtt
>  >   dhcp tag       :
>  >   virt bridge    :
>  > interface        : eth3
>  >   mac address    : 00:1F:29:E1:54:AC
>  >   bonding        :
>  >   bonding_master :
>  >   bonding_opts   :
>  >   is static?     : True
>  >   ip address     : 10.x.x.x
>  >   subnet         : 255.255.255.0
>  >   static routes  : []
>  >   dns name       : edge01.lon04.mtt
>  >   dhcp tag       :
>  >   virt bridge    :
>  >
>  >
>  > When I look at the kickstart file, it looks to be ordering
>  > them with a different configuration then I wanted using the
>  > "old" style config?  how do I get it to use the "new" style
> config?
>  >
>  > # Network information
>  > # Using "old" style networking config. Make sure all
>  > MAC-addresses are in cobbler to use the new-style config
>  > network --bootproto=static --ip=10.123.200.36
>  > --netmask=255.255.255.0 --gateway=10.123.200.1
>  > --hostname=edge01.lon04.mtt --device=eth0 --onboot=on
>  > network --bootproto=static --ip=192.168.123.36
>  > --netmask=255.255.255.0 --gateway=10.123.200.1
>  > --hostname=edge01.lon04.mtt --device=eth1 --onboot=on
>  > network --bootproto=dhcp --device=eth2 --onboot=on
>  >
>  > A few questions:
>  >
>  > 1) eth0 should not even be used, let alone why is it a
>  > requirement to have eth2 in my cobbler system record?  I have
>  > alot of hosts where eth0 is available but not even plumbed up.
>  > 2) eth2/eth3 are the NICs I want to use, but why did they end
>  > up going to eth0/eth1?
>  > 3) where did the eth2 interface come into the picture here using dhcp?
>  >
>  >
>
>  NOTICE: This email and any attachments are confidential.
>  They may contain legally privileged information or
>  copyright material. You must not read, copy, use or
>  disclose them without authorisation. If you are not an
>  intended recipient, please contact us at once by return
>  email and then delete both messages and all attachments.
>
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler
>

[Christopher Johnston]

Seems there are some differences with fedora and centos/rhel, I recall using
pci=bfsort in the past for RHEL hosts - Fedora is in favor of bfsort now.
That worked.

On Tue, Feb 3, 2009 at 6:08 PM, Christopher Johnston <
cjohnstonwork(a)gmail.com&gt; wrote:

>  I believe I tried both...
>  What im confused about is the "new-style" and "old-style" network
>  configuration.
>
>
>  On Tue, Feb 3, 2009 at 5:33 PM, Coe, Colin C. (Unix Engineer) <
>  Colin.Coe(a)woodside.com.au&gt; wrote:
>
> >
> > Try just bfsort on the kernel cmdline.
> >
> > CC
> >
> > > -----Original Message-----
> > > From: cobbler-bounces(a)lists.fedorahosted.org
> > > [mailto:[e-mail]] On Behalf Of
> > > Christopher Johnston
> > > Sent: Wednesday, 4 February 2009 9:05 AM
> > > To: cobbler mailing list
> > > Subject: network ordering
> > >
> > > So I have some servers with a few network cards installed and
> > > because the kernel does a poor job of ordering them correctly
> > > during an install they come up out of order (pci=bfsort does
> > > not help).  I havnt looked to deep into the snippet just yet,
> > > but on a specific system where I have the following:
> > >
> > > eth0 : unconfigured
> > > eth1 : unconfigured
> > > eth2 : non-routeable network (heartbeat)
> > > eth3 : configure routeable network
> > >
> > > My BIOS is configured to PXE boot on eth3.  So in cobbler I
> > > have it setup like so with eth0 empty, eth2 configured our
> > > private 192.168 interface and eth3 configured with the
> > > routable interface.
> > >
> > > interface        : eth0
> > >
> > >   mac address    :
> > >   bonding        :
> > >   bonding_master :
> > >   bonding_opts   :
> > >   is static?     : False
> > >   ip address     :
> > >   subnet         :
> > >   static routes  : []
> > >   dns name       :
> > >   dhcp tag       :
> > >   virt bridge    :
> > > interface        : eth2
> > >   mac address    : 00:1F:29:E1:54:AE
> > >   bonding        :
> > >   bonding_master :
> > >   bonding_opts   :
> > >   is static?     : True
> > >   ip address     : 192.168.x.x
> > >   subnet         : 255.255.255.0
> > >   static routes  : []
> > >   dns name       : edge01.core.lon04.mtt
> > >   dhcp tag       :
> > >   virt bridge    :
> > > interface        : eth3
> > >   mac address    : 00:1F:29:E1:54:AC
> > >   bonding        :
> > >   bonding_master :
> > >   bonding_opts   :
> > >   is static?     : True
> > >   ip address     : 10.x.x.x
> > >   subnet         : 255.255.255.0
> > >   static routes  : []
> > >   dns name       : edge01.lon04.mtt
> > >   dhcp tag       :
> > >   virt bridge    :
> > >
> > >
> > > When I look at the kickstart file, it looks to be ordering
> > > them with a different configuration then I wanted using the
> > > "old" style config?  how do I get it to use the "new" style
> config?
> > >
> > > # Network information
> > > # Using "old" style networking config. Make sure all
> > > MAC-addresses are in cobbler to use the new-style config
> > > network --bootproto=static --ip=10.123.200.36
> > > --netmask=255.255.255.0 --gateway=10.123.200.1
> > > --hostname=edge01.lon04.mtt --device=eth0 --onboot=on
> > > network --bootproto=static --ip=192.168.123.36
> > > --netmask=255.255.255.0 --gateway=10.123.200.1
> > > --hostname=edge01.lon04.mtt --device=eth1 --onboot=on
> > > network --bootproto=dhcp --device=eth2 --onboot=on
> > >
> > > A few questions:
> > >
> > > 1) eth0 should not even be used, let alone why is it a
> > > requirement to have eth2 in my cobbler system record?  I have
> > > alot of hosts where eth0 is available but not even plumbed up.
> > > 2) eth2/eth3 are the NICs I want to use, but why did they end
> > > up going to eth0/eth1?
> > > 3) where did the eth2 interface come into the picture here using dhcp?
> > >
> > >
> >
> > NOTICE: This email and any attachments are confidential.
> > They may contain legally privileged information or
> > copyright material. You must not read, copy, use or
> > disclose them without authorisation. If you are not an
> > intended recipient, please contact us at once by return
> > email and then delete both messages and all attachments.
> >
> > _______________________________________________
> > cobbler mailing list
> > cobbler(a)lists.fedorahosted.org
> > https://fedorahosted.org/mailman/listinfo/cobbler
> >
>
>

[Coe, Colin C. (Unix Engineer)]

This works with RHEL5 (and from memory RHEL4 but I'm not 100% on that).

CC

>  -----Original Message-----
>  From: cobbler-bounces(a)lists.fedorahosted.org 
>  [mailto:[e-mail]] On Behalf Of 
>  Christopher Johnston
>  Sent: Wednesday, 4 February 2009 11:34 AM
>  To: cobbler mailing list
>  Subject: Re: network ordering
>  
>  Seems there are some differences with fedora and centos/rhel, 
>  I recall using pci=bfsort in the past for RHEL hosts - Fedora 
>  is in favor of bfsort now.  
>  
>  That worked.
>  
>  
>  On Tue, Feb 3, 2009 at 6:08 PM, Christopher Johnston 
>  <cjohnstonwork(a)gmail.com&gt; wrote:
>  
>  
>  	I believe I tried both...  
>  
>  	What im confused about is the "new-style" and 
>  "old-style" network configuration.  
>  
>  
>  	On Tue, Feb 3, 2009 at 5:33 PM, Coe, Colin C. (Unix 
>  Engineer) <Colin.Coe(a)woodside.com.au&gt; wrote:
>  	
>  
>  
>  		Try just bfsort on the kernel cmdline.
>  		
>  		CC
>  		
>  
>  		> -----Original Message-----
>  		> From: cobbler-bounces(a)lists.fedorahosted.org
>  		> 
>  [mailto:[e-mail]] On Behalf Of
>  		> Christopher Johnston
>  		> Sent: Wednesday, 4 February 2009 9:05 AM
>  		> To: cobbler mailing list
>  		> Subject: network ordering
>  		>
>  		> So I have some servers with a few network 
>  cards installed and
>  		> because the kernel does a poor job of 
>  ordering them correctly
>  		> during an install they come up out of order 
>  (pci=bfsort does
>  		> not help).  I havnt looked to deep into the 
>  snippet just yet,
>  		> but on a specific system where I have the following:
>  		>
>  		> eth0 : unconfigured
>  		> eth1 : unconfigured
>  		> eth2 : non-routeable network (heartbeat)
>  		> eth3 : configure routeable network
>  		>
>  		> My BIOS is configured to PXE boot on eth3.  
>  So in cobbler I
>  		> have it setup like so with eth0 empty, eth2 
>  configured our
>  		> private 192.168 interface and eth3 configured with the
>  		> routable interface.
>  		>
>  		> interface        : eth0
>  		>
>  		>   mac address    :
>  		>   bonding        :
>  		>   bonding_master :
>  		>   bonding_opts   :
>  		>   is static?     : False
>  		>   ip address     :
>  		>   subnet         :
>  		>   static routes  : []
>  		>   dns name       :
>  		>   dhcp tag       :
>  		>   virt bridge    :
>  		> interface        : eth2
>  		>   mac address    : 00:1F:29:E1:54:AE
>  		>   bonding        :
>  		>   bonding_master :
>  		>   bonding_opts   :
>  		>   is static?     : True
>  		>   ip address     : 192.168.x.x
>  		>   subnet         : 255.255.255.0
>  		>   static routes  : []
>  		>   dns name       : edge01.core.lon04.mtt
>  		>   dhcp tag       :
>  		>   virt bridge    :
>  		> interface        : eth3
>  		>   mac address    : 00:1F:29:E1:54:AC
>  		>   bonding        :
>  		>   bonding_master :
>  		>   bonding_opts   :
>  		>   is static?     : True
>  		>   ip address     : 10.x.x.x
>  		>   subnet         : 255.255.255.0
>  		>   static routes  : []
>  		>   dns name       : edge01.lon04.mtt
>  		>   dhcp tag       :
>  		>   virt bridge    :
>  		>
>  		>
>  		> When I look at the kickstart file, it looks 
>  to be ordering
>  		> them with a different configuration then I 
>  wanted using the
>  		> "old" style config?  how do I get it to use 
>  the "new" style config?
>  		>
>  		> # Network information
>  		> # Using "old" style networking config. Make sure all
>  		> MAC-addresses are in cobbler to use the 
>  new-style config
>  		> network --bootproto=static --ip=10.123.200.36
>  		> --netmask=255.255.255.0 --gateway=10.123.200.1
>  		> --hostname=edge01.lon04.mtt --device=eth0 --onboot=on
>  		> network --bootproto=static --ip=192.168.123.36
>  		> --netmask=255.255.255.0 --gateway=10.123.200.1
>  		> --hostname=edge01.lon04.mtt --device=eth1 --onboot=on
>  		> network --bootproto=dhcp --device=eth2 --onboot=on
>  		>
>  		> A few questions:
>  		>
>  		> 1) eth0 should not even be used, let alone why is it a
>  		> requirement to have eth2 in my cobbler system 
>  record?  I have
>  		> alot of hosts where eth0 is available but not 
>  even plumbed up.
>  		> 2) eth2/eth3 are the NICs I want to use, but 
>  why did they end
>  		> up going to eth0/eth1?
>  		> 3) where did the eth2 interface come into the 
>  picture here using dhcp?
>  		>
>  		>
>  		
>  		
>  		NOTICE: This email and any attachments are confidential.
>  		They may contain legally privileged information or
>  		copyright material. You must not read, copy, use or
>  		disclose them without authorisation. If you are not an
>  		intended recipient, please contact us at once by return
>  		email and then delete both messages and all attachments.
>  		
>  		_______________________________________________
>  		cobbler mailing list
>  		cobbler(a)lists.fedorahosted.org
>  		https://fedorahosted.org/mailman/listinfo/cobbler
>  		
>  
>  
>  
>   
NOTICE: This email and any attachments are confidential. 
They may contain legally privileged information or 
copyright material. You must not read, copy, use or 
disclose them without authorisation. If you are not an 
intended recipient, please contact us at once by return 
email and then delete both messages and all attachments.

[Christopher Johnston]

I think RHEL4.6 this feature was added to resolve some HP blade NIC ordering
issues if my memory serves me.

On Tue, Feb 3, 2009 at 7:47 PM, Coe, Colin C. (Unix Engineer) <
Colin.Coe(a)woodside.com.au&gt; wrote:

>  This works with RHEL5 (and from memory RHEL4 but I'm not 100% on that).
>
>  CC
>
>  > -----Original Message-----
>  > From: cobbler-bounces(a)lists.fedorahosted.org
>  > [mailto:[e-mail]] On Behalf Of
>  > Christopher Johnston
>  > Sent: Wednesday, 4 February 2009 11:34 AM
>  > To: cobbler mailing list
>  > Subject: Re: network ordering
>  >
>  > Seems there are some differences with fedora and centos/rhel,
>  > I recall using pci=bfsort in the past for RHEL hosts - Fedora
>  > is in favor of bfsort now.
>  >
>  > That worked.
>  >
>  >
>  > On Tue, Feb 3, 2009 at 6:08 PM, Christopher Johnston
>  > <cjohnstonwork(a)gmail.com&gt; wrote:
>  >
>  >
>  >       I believe I tried both...
>  >
>  >       What im confused about is the "new-style" and
>  > "old-style" network configuration.
>  >
>  >
>  >       On Tue, Feb 3, 2009 at 5:33 PM, Coe, Colin C. (Unix
>  > Engineer) <Colin.Coe(a)woodside.com.au&gt; wrote:
>  >
>  >
>  >
>  >               Try just bfsort on the kernel cmdline.
>  >
>  >               CC
>  >
>  >
>  >               > -----Original Message-----
>  >               > From: cobbler-bounces(a)lists.fedorahosted.org
>  >               >
>  > [mailto:[e-mail]] On Behalf Of
>  >               > Christopher Johnston
>  >               > Sent: Wednesday, 4 February 2009 9:05 AM
>  >               > To: cobbler mailing list
>  >               > Subject: network ordering
>  >               >
>  >               > So I have some servers with a few network
>  > cards installed and
>  >               > because the kernel does a poor job of
>  > ordering them correctly
>  >               > during an install they come up out of order
>  > (pci=bfsort does
>  >               > not help).  I havnt looked to deep into the
>  > snippet just yet,
>  >               > but on a specific system where I have the following:
>  >               >
>  >               > eth0 : unconfigured
>  >               > eth1 : unconfigured
>  >               > eth2 : non-routeable network (heartbeat)
>  >               > eth3 : configure routeable network
>  >               >
>  >               > My BIOS is configured to PXE boot on eth3.
>  > So in cobbler I
>  >               > have it setup like so with eth0 empty, eth2
>  > configured our
>  >               > private 192.168 interface and eth3 configured with the
>  >               > routable interface.
>  >               >
>  >               > interface        : eth0
>  >               >
>  >               >   mac address    :
>  >               >   bonding        :
>  >               >   bonding_master :
>  >               >   bonding_opts   :
>  >               >   is static?     : False
>  >               >   ip address     :
>  >               >   subnet         :
>  >               >   static routes  : []
>  >               >   dns name       :
>  >               >   dhcp tag       :
>  >               >   virt bridge    :
>  >               > interface        : eth2
>  >               >   mac address    : 00:1F:29:E1:54:AE
>  >               >   bonding        :
>  >               >   bonding_master :
>  >               >   bonding_opts   :
>  >               >   is static?     : True
>  >               >   ip address     : 192.168.x.x
>  >               >   subnet         : 255.255.255.0
>  >               >   static routes  : []
>  >               >   dns name       : edge01.core.lon04.mtt
>  >               >   dhcp tag       :
>  >               >   virt bridge    :
>  >               > interface        : eth3
>  >               >   mac address    : 00:1F:29:E1:54:AC
>  >               >   bonding        :
>  >               >   bonding_master :
>  >               >   bonding_opts   :
>  >               >   is static?     : True
>  >               >   ip address     : 10.x.x.x
>  >               >   subnet         : 255.255.255.0
>  >               >   static routes  : []
>  >               >   dns name       : edge01.lon04.mtt
>  >               >   dhcp tag       :
>  >               >   virt bridge    :
>  >               >
>  >               >
>  >               > When I look at the kickstart file, it looks
>  > to be ordering
>  >               > them with a different configuration then I
>  > wanted using the
>  >               > "old" style config?  how do I get it to use
>  > the "new" style config?
>  >               >
>  >               > # Network information
>  >               > # Using "old" style networking config. Make sure all
>  >               > MAC-addresses are in cobbler to use the
>  > new-style config
>  >               > network --bootproto=static --ip=10.123.200.36
>  >               > --netmask=255.255.255.0 --gateway=10.123.200.1
>  >               > --hostname=edge01.lon04.mtt --device=eth0 --onboot=on
>  >               > network --bootproto=static --ip=192.168.123.36
>  >               > --netmask=255.255.255.0 --gateway=10.123.200.1
>  >               > --hostname=edge01.lon04.mtt --device=eth1 --onboot=on
>  >               > network --bootproto=dhcp --device=eth2 --onboot=on
>  >               >
>  >               > A few questions:
>  >               >
>  >               > 1) eth0 should not even be used, let alone why is it a
>  >               > requirement to have eth2 in my cobbler system
>  > record?  I have
>  >               > alot of hosts where eth0 is available but not
>  > even plumbed up.
>  >               > 2) eth2/eth3 are the NICs I want to use, but
>  > why did they end
>  >               > up going to eth0/eth1?
>  >               > 3) where did the eth2 interface come into the
>  > picture here using dhcp?
>  >               >
>  >               >
>  >
>  >
>  >               NOTICE: This email and any attachments are confidential.
>  >               They may contain legally privileged information or
>  >               copyright material. You must not read, copy, use or
>  >               disclose them without authorisation. If you are not an
>  >               intended recipient, please contact us at once by return
>  >               email and then delete both messages and all attachments.
>  >
>  >               _______________________________________________
>  >               cobbler mailing list
>  >               cobbler(a)lists.fedorahosted.org
>  >               https://fedorahosted.org/mailman/listinfo/cobbler
>  >
>  >
>  >
>  >
>  >
>
>  NOTICE: This email and any attachments are confidential.
>  They may contain legally privileged information or
>  copyright material. You must not read, copy, use or
>  disclose them without authorisation. If you are not an
>  intended recipient, please contact us at once by return
>  email and then delete both messages and all attachments.
>
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler
>

[Jasper Capel]

Christopher Johnston wrote:
>  I think RHEL4.6 this feature was added to resolve some HP blade NIC
> ordering
>  issues if my memory serves me.
>  
>  On Tue, Feb 3, 2009 at 7:47 PM, Coe, Colin C. (Unix Engineer) <
>  Colin.Coe(a)woodside.com.au&gt; wrote:
>   
Could you try pulling the latest master, build an RPM, install it,
remove eth0 and see if that solves your problem? It's really easy:

git pull git://fedorahosted.org/cobbler
cd cobbler
make rpms (you need rpmbuild, python-setuptools, python-cheetah and
probably some other stuff for this)
and install the resulting rpm in rpm-build/

Jasper

[Christopher Johnston]

Oh I have already tested out 1.4.1 if thats what your asking.  I did it last
night and worked like a champ.  I removed eth0 and put eth2 and eth3 in
there and the host blasted just fine.

The key is though you need to know exactly where eth2/eth3 will end up once
the system is booted.

-Chris

On Thu, Feb 5, 2009 at 2:30 PM, Jasper Capel <capel(a)stone-it.com&gt; wrote:

>  Christopher Johnston wrote:
>  > I think RHEL4.6 this feature was added to resolve some HP blade NIC
>  ordering
>  > issues if my memory serves me.
>  >
>  > On Tue, Feb 3, 2009 at 7:47 PM, Coe, Colin C. (Unix Engineer) <
>  > Colin.Coe(a)woodside.com.au&gt; wrote:
>  >
>
>  Could you try pulling the latest master, build an RPM, install it,
>  remove eth0 and see if that solves your problem? It's really easy:
>
>  git pull git://fedorahosted.org/cobbler
>  cd cobbler
>  make rpms (you need rpmbuild, python-setuptools, python-cheetah and
>  probably some other stuff for this)
>  and install the resulting rpm in rpm-build/
>
>  Jasper
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler
>

[Jasper Capel]

Christopher Johnston wrote:
>  Oh I have already tested out 1.4.1 if thats what your asking.  I did
> it last
>  night and worked like a champ.  I removed eth0 and put eth2 and eth3 in
>  there and the host blasted just fine.
>   
Not 1.4.1, the patches that got merged in after 1.4.1 (and what will
become 1.4.2). But if it let you remove eth0, I guess you pulled the
patch. :)

>  The key is though you need to know exactly where eth2/eth3 will end
> up once
>  the system is booted.
>   
You don't, actually, you can give those interfaces any name you like.
Call them foo and bar if you please. You specified their MAC addresses,
so the scripts will know what address to put on each physical interface.
If this somehow doesn't work for you, I'd like to know. :)

Jasper

[Jasper Capel]

Jasper Capel wrote:
>  Christopher Johnston wrote:
> > Oh I have already tested out 1.4.1 if thats what your asking.  I did it last
> > night and worked like a champ.  I removed eth0 and put eth2 and eth3 in
> > there and the host blasted just fine.
> >
>  Not 1.4.1, the patches that got merged in after 1.4.1 (and what will
>  become 1.4.2). But if it let you remove eth0, I guess you pulled the
>  patch. :)
>  
> > The key is though you need to know exactly where eth2/eth3 will end up once
> > the system is booted.
> >
>  
>  You don't, actually, you can give those interfaces any name you like.
>  Call them foo and bar if you please. You specified their MAC addresses,
>  so the scripts will know what address to put on each physical interface.
>  If this somehow doesn't work for you, I'd like to know. :)
>   
Hmm, well not /any/ name, you wouldn't want to name them after a kernel
module you're using, weird stuff would happen. :)

[Michael DeHaan]

Jasper Capel wrote:
>  Jasper Capel wrote:
>    
> > Christopher Johnston wrote:
> >     
> >> Oh I have already tested out 1.4.1 if thats what your asking.  I did it last
> >> night and worked like a champ.  I removed eth0 and put eth2 and eth3 in
> >> there and the host blasted just fine.
> >>
> >>       
> > Not 1.4.1, the patches that got merged in after 1.4.1 (and what will
> > become 1.4.2). But if it let you remove eth0, I guess you pulled the
> > patch. :)
> >
> >     
> >> The key is though you need to know exactly where eth2/eth3 will end up once
> >> the system is booted.
> >>
> >>       
> > You don't, actually, you can give those interfaces any name you like.
> > Call them foo and bar if you please. You specified their MAC addresses,
> > so the scripts will know what address to put on each physical interface.
> > If this somehow doesn't work for you, I'd like to know. :)
> >
> >     
>  Hmm, well not /any/ name, you wouldn't want to name them after a kernel
>  module you're using, weird stuff would happen. :)
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler
>     
Darn, I always like to name my NICs "pcspkr".

[Christopher Johnston]

I cherry-picked the patch from git from the master branch.
-Chris

On Thu, Feb 5, 2009 at 2:40 PM, Jasper Capel <capel(a)stone-it.com&gt; wrote:

>  Christopher Johnston wrote:
>  > Oh I have already tested out 1.4.1 if thats what your asking.  I did it
>  last
>  > night and worked like a champ.  I removed eth0 and put eth2 and eth3 in
>  > there and the host blasted just fine.
>  >
>  Not 1.4.1, the patches that got merged in after 1.4.1 (and what will
>  become 1.4.2). But if it let you remove eth0, I guess you pulled the
>  patch. :)
>
>  > The key is though you need to know exactly where eth2/eth3 will end up
>  once
>  > the system is booted.
>  >
>
>  You don't, actually, you can give those interfaces any name you like.
>  Call them foo and bar if you please. You specified their MAC addresses,
>  so the scripts will know what address to put on each physical interface.
>  If this somehow doesn't work for you, I'd like to know. :)
>
>  Jasper
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler
>

[Andy Gospodarek]

On Wed, Feb 04, 2009 at 10:33:16AM +0900, Coe, Colin C. (Unix Engineer) wrote:
>  
>  Try just bfsort on the kernel cmdline.
>   
The kernel command line option pci=bfsort is not a panacea for all
network device ordering issues.  It's really only valuable in systems
where system vendors decided to put bridge chips in odd spots that make
it so that devices do not appear in the pci device list correctly when
scanned in a depth-first manner (the way the 2.6 kernel does it).

The bfsort option just scans the list and makes sure the list of pci
devices are sorted in what one would be the correct order (bus, device,
function).  In addition to this kernel command line there are some
systems that are known to be wired up in an interesting way and the
sorting has been requested to be done automatically.  They are:

Dell PowerEdge 1950
Dell PowerEdge 1955
Dell PowerEdge 2900
Dell PowerEdge 2950
Dell PowerEdge R900
HP ProLiant BL20p G3
HP ProLiant BL20p G4
HP ProLiant BL30p G1
HP ProLiant BL25p G1
HP ProLiant BL35p G1
HP ProLiant BL45p G1
HP ProLiant BL45p G2
HP ProLiant BL460c G1
HP ProLiant BL465c G1
HP ProLiant BL480c G1
HP ProLiant BL685c G1
HP ProLiant DL360
HP ProLiant DL380
HP ProLiant DL385 G2
HP ProLiant DL585 G2

RHEL (and consequently CentOS) also has some device ordering
idiosyncrasies that occasionally pop up.  RHEL5 is the release that gets
the most complaints and work is being done to make ordering more
consistent.

Continuing to discuss this topic on this list is fine with me --
hopefully it doesn't bother others.  The work that is being done to try
and correct these ordering issues may not be something cobbler can use
if we are not careful, so continuing to provide feedback on what is
broken is helpful.

-andy

[Jeff Schroeder]

On Wed, Feb 4, 2009 at 9:49 AM, Andy Gospodarek <gospo(a)redhat.com&gt; wrote:
>  On Wed, Feb 04, 2009 at 10:33:16AM +0900, Coe, Colin C. (Unix
> Engineer) wrote:
> >
> > Try just bfsort on the kernel cmdline.
> >
>
>  The kernel command line option pci=bfsort is not a panacea for all
>  network device ordering issues.  It's really only valuable in systems
>  where system vendors decided to put bridge chips in odd spots that make
>  it so that devices do not appear in the pci device list correctly when
>  scanned in a depth-first manner (the way the 2.6 kernel does it). 
In other news, there is a utility named "biosdevname" in the fedora
repos. It reads the dmi tables and returns the correct physical
interface names. When Fedora brings up NIC1 as eth2, biosdevname -i
eth2 shows eth0. We might be able to do some post hack snippet that
includes biosdevname to reorder the logical names to be more inline.
Does anyone think this is worth investigating or is it not worth the
effort?

-- 
Jeff Schroeder

Don't drink and derive, alcohol and analysis don't mix.
http://www.digitalprognosis.com

[Michael DeHaan]

Jeff Schroeder wrote:
>  On Wed, Feb 4, 2009 at 9:49 AM, Andy Gospodarek
> <gospo(a)redhat.com&gt; wrote:
>    
> > On Wed, Feb 04, 2009 at 10:33:16AM +0900, Coe, Colin C. (Unix Engineer) wrote:
> >     
> >> Try just bfsort on the kernel cmdline.
> >>
> >>       
> > The kernel command line option pci=bfsort is not a panacea for all
> > network device ordering issues.  It's really only valuable in systems
> > where system vendors decided to put bridge chips in odd spots that make
> > it so that devices do not appear in the pci device list correctly when
> > scanned in a depth-first manner (the way the 2.6 kernel does it).
> >     
>
>  In other news, there is a utility named "biosdevname" in the fedora
>  repos. It reads the dmi tables and returns the correct physical
>  interface names. When Fedora brings up NIC1 as eth2, biosdevname -i
>  eth2 shows eth0. We might be able to do some post hack snippet that
>  includes biosdevname to reorder the logical names to be more inline.
>  Does anyone think this is worth investigating or is it not worth the
>  effort?
>
>     
The network snippet is already getting a little involved. I'm not sure I 
want to see it get more involved.

--Michael

[Andy Gospodarek]

On Wed, Feb 04, 2009 at 10:03:06AM -0800, Jeff Schroeder wrote:
>  On Wed, Feb 4, 2009 at 9:49 AM, Andy Gospodarek
> <gospo(a)redhat.com&gt; wrote:
>  > On Wed, Feb 04, 2009 at 10:33:16AM +0900, Coe, Colin C. (Unix Engineer) wrote:
>  >>
>  >> Try just bfsort on the kernel cmdline.
>  >>
>  >
>  > The kernel command line option pci=bfsort is not a panacea for all
>  > network device ordering issues.  It's really only valuable in systems
>  > where system vendors decided to put bridge chips in odd spots that make
>  > it so that devices do not appear in the pci device list correctly when
>  > scanned in a depth-first manner (the way the 2.6 kernel does it).
>  
>  In other news, there is a utility named "biosdevname" in the fedora
>  repos. It reads the dmi tables and returns the correct physical
>  interface names. When Fedora brings up NIC1 as eth2, biosdevname -i
>  eth2 shows eth0. We might be able to do some post hack snippet that
>  includes biosdevname to reorder the logical names to be more inline.
>  Does anyone think this is worth investigating or is it not worth the
>  effort?
>   
I've been played with biosdevname for a while and it's a neat little
tool.  When working with it on several systems however it seemed to have
problems coming up with device names for cards that were not LOMs.  I
also had problems with it on some non-Dell systems.  Have you noticed
these limitations or was it just the boxes I had or a limitation with
the older version of biosdevname?

[Christopher Johnston]

Yes, I have already grokked the kernel source and saw thats its a limited
subset of systems.    I happened to be working on a system thats in that
list.

On Wed, Feb 4, 2009 at 9:49 AM, Andy Gospodarek <gospo(a)redhat.com&gt; wrote:

>  On Wed, Feb 04, 2009 at 10:33:16AM +0900, Coe, Colin C. (Unix
> Engineer)
>  wrote:
>  >
>  > Try just bfsort on the kernel cmdline.
>  >
>
>  The kernel command line option pci=bfsort is not a panacea for all
>  network device ordering issues.  It's really only valuable in systems
>  where system vendors decided to put bridge chips in odd spots that make
>  it so that devices do not appear in the pci device list correctly when
>  scanned in a depth-first manner (the way the 2.6 kernel does it).
>
>  The bfsort option just scans the list and makes sure the list of pci
>  devices are sorted in what one would be the correct order (bus, device,
>  function).  In addition to this kernel command line there are some
>  systems that are known to be wired up in an interesting way and the
>  sorting has been requested to be done automatically.  They are:
>
>  Dell PowerEdge 1950
>  Dell PowerEdge 1955
>  Dell PowerEdge 2900
>  Dell PowerEdge 2950
>  Dell PowerEdge R900
>  HP ProLiant BL20p G3
>  HP ProLiant BL20p G4
>  HP ProLiant BL30p G1
>  HP ProLiant BL25p G1
>  HP ProLiant BL35p G1
>  HP ProLiant BL45p G1
>  HP ProLiant BL45p G2
>  HP ProLiant BL460c G1
>  HP ProLiant BL465c G1
>  HP ProLiant BL480c G1
>  HP ProLiant BL685c G1
>  HP ProLiant DL360
>  HP ProLiant DL380
>  HP ProLiant DL385 G2
>  HP ProLiant DL585 G2
>
>  RHEL (and consequently CentOS) also has some device ordering
>  idiosyncrasies that occasionally pop up.  RHEL5 is the release that gets
>  the most complaints and work is being done to make ordering more
>  consistent.
>
>  Continuing to discuss this topic on this list is fine with me --
>  hopefully it doesn't bother others.  The work that is being done to try
>  and correct these ordering issues may not be something cobbler can use
>  if we are not careful, so continuing to provide feedback on what is
>  broken is helpful.
>
>  -andy
>
>
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler
>

[Andy Gospodarek]

On Wed, Feb 04, 2009 at 10:08:52AM -0800, Christopher Johnston wrote:
>  Yes, I have already grokked the kernel source and saw thats its a
> limited
>  subset of systems.    I happened to be working on a system thats in that
>  list.
>   
Were the on-board devices getting ordered correctly?

[Jasper Capel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Christopher Johnston wrote:
|
| interface        : eth0
|   mac address    :
|   bonding        :
|   bonding_master :
|   bonding_opts   :
|   is static?     : False
|   ip address     :
|   subnet         :
|   static routes  : []
|   dns name       :
|   dhcp tag       :
|   virt bridge    :
| interface        : eth2
|   mac address    : 00:1F:29:E1:54:AE
|   bonding        :
|   bonding_master :
|   bonding_opts   :
|   is static?     : True
|   ip address     : 192.168.x.x
|   subnet         : 255.255.255.0
|   static routes  : []
|   dns name       : edge01.core.lon04.mtt
|   dhcp tag       :
|   virt bridge    :
| interface        : eth3
|   mac address    : 00:1F:29:E1:54:AC
|   bonding        :
|   bonding_master :
|   bonding_opts   :
|   is static?     : True
|   ip address     : 10.x.x.x
|   subnet         : 255.255.255.0
|   static routes  : []
|   dns name       : edge01.lon04.mtt
|   dhcp tag       :
|   virt bridge    :
|
|
| When I look at the kickstart file, it looks to be ordering them with a
| different configuration then I wanted using the "old" style config?  how
| do I get it to use the "new" style config?
|
It's using old style config, because not all interfaces specified in
Cobbler have MAC-addresses specified for them, so it's impossible to
match all physical devices using their MAC addresses.
In turn, this is caused because you can't delete eth0 (this is fixed in
1.4.2).
If you can't wait, you could pull the latest Cobbler stable from git and
build an rpm from it yourself.
e.g.
git clone git://fedorahosted.org/cobbler; cd cobbler; git checkout
master; make rpms


Jasper
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkmJfUIACgkQCOz21NVLFmeXcQCcDCI0xkvlIqVc+AOr4k51TP68
> P14AniHyjRN2RKIkWcRumnNNR4eRD10U
> =ev1h
> -----END PGP SIGNATURE-----

[Christopher Johnston]

I see your check-in, will take a look.

commit 30a862700654238d4b255875c7eae1dfadabe20d
Author: Jasper Capel <capel(a)stone-it.com&gt;
Date:   Tue Jan 27 12:19:02 2009 +0100

    Fixed bug (ticket #309). Eth0 can now be deleted, and won't magically
re-appear.
    Removed some old default_interface code.

-Chris

On Wed, Feb 4, 2009 at 3:34 AM, Jasper Capel <capel(a)stone-it.com&gt; wrote:

>  -----BEGIN PGP SIGNED MESSAGE-----
>  Hash: SHA1
>
>  Christopher Johnston wrote:
>  |
>  | interface        : eth0
>  |   mac address    :
>  |   bonding        :
>  |   bonding_master :
>  |   bonding_opts   :
>  |   is static?     : False
>  |   ip address     :
>  |   subnet         :
>  |   static routes  : []
>  |   dns name       :
>  |   dhcp tag       :
>  |   virt bridge    :
>  | interface        : eth2
>  |   mac address    : 00:1F:29:E1:54:AE
>  |   bonding        :
>  |   bonding_master :
>  |   bonding_opts   :
>  |   is static?     : True
>  |   ip address     : 192.168.x.x
>  |   subnet         : 255.255.255.0
>  |   static routes  : []
>  |   dns name       : edge01.core.lon04.mtt
>  |   dhcp tag       :
>  |   virt bridge    :
>  | interface        : eth3
>  |   mac address    : 00:1F:29:E1:54:AC
>  |   bonding        :
>  |   bonding_master :
>  |   bonding_opts   :
>  |   is static?     : True
>  |   ip address     : 10.x.x.x
>  |   subnet         : 255.255.255.0
>  |   static routes  : []
>  |   dns name       : edge01.lon04.mtt
>  |   dhcp tag       :
>  |   virt bridge    :
>  |
>  |
>  | When I look at the kickstart file, it looks to be ordering them with a
>  | different configuration then I wanted using the "old" style config?  how
>  | do I get it to use the "new" style config?
>  |
>  It's using old style config, because not all interfaces specified in
>  Cobbler have MAC-addresses specified for them, so it's impossible to
>  match all physical devices using their MAC addresses.
>  In turn, this is caused because you can't delete eth0 (this is fixed in
>  1.4.2).
>  If you can't wait, you could pull the latest Cobbler stable from git and
>  build an rpm from it yourself.
>  e.g.
>  git clone git://fedorahosted.org/cobbler; cd cobbler; git checkout
>  master; make rpms
>
>
>  Jasper
> >  -----BEGIN PGP SIGNATURE-----
> >  Version: GnuPG v1.4.9 (GNU/Linux)
> >  Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
> >
> >  iEYEARECAAYFAkmJfUIACgkQCOz21NVLFmeXcQCcDCI0xkvlIqVc+AOr4k51TP68
> >  P14AniHyjRN2RKIkWcRumnNNR4eRD10U
> >  =ev1h
> >  -----END PGP SIGNATURE----- 
>  _______________________________________________
>  cobbler mailing list
>  cobbler(a)lists.fedorahosted.org
>  https://fedorahosted.org/mailman/listinfo/cobbler
>

[Andreas Zuber]

Am Mittwoch 04 Februar 2009 02:05:16 schrieb Christopher Johnston:
>  2) eth2/eth3 are the NICs I want to use, but why did they end up
> going to
>  eth0/eth1?
>  3) where did the eth2 interface come into the picture here using dhcp? 
Maybe this will help you:
https://fedorahosted.org/cobbler/wiki/KickstartSnippets#NICOrderingandIns...

This makes sure that the interface that was used for PXE is also used for 
installation and then it simply writes the "/etc/sysconfig/network-scripts/" 
out of your cobbler data. This was the only way i found to relate the 
mac-addresses with the "eth" numbering.

Greetings
Andy

-- 
Andreas Zuber  
Linux System-Ingenieur
Puzzle ITC GmbH 
www.puzzle.ch 
 
Telefon [phone] 
Direkt  [phone]  
Mobile  [phone]  
Fax     [phone] 
 
Puzzle ist Mitglied der ODF Alliance: 
<http://www.puzzle.ch/odfalliance/>

[Michael DeHaan]

Andreas Zuber wrote:
>  Am Mittwoch 04 Februar 2009 02:05:16 schrieb Christopher Johnston:
>    
> > 2) eth2/eth3 are the NICs I want to use, but why did they end up going to
> > eth0/eth1?
> > 3) where did the eth2 interface come into the picture here using dhcp?
> >     
>
>  Maybe this will help you:
>  https://fedorahosted.org/cobbler/wiki/KickstartSnippets#NICOrderingandIns...
>
>  This makes sure that the interface that was used for PXE is also used for 
>  installation and then it simply writes the "/etc/sysconfig/network-scripts/" 
>  out of your cobbler data. This was the only way i found to relate the 
>  mac-addresses with the "eth" numbering.
>
>  Greetings
>  Andy
>
>     
bootif and ipappend 2 is already the default in newer cobbler installs, 
I'm thinking that section of the Wiki no longer needs to be there?

--Michael

[Jasper Capel]

On 03/16/2009 08:05 PM, Michael DeHaan wrote:
>  Andreas Zuber wrote:
> > Am Mittwoch 04 Februar 2009 02:05:16 schrieb Christopher Johnston:
> >   
> >> 2) eth2/eth3 are the NICs I want to use, but why did they end up going to
> >> eth0/eth1?
> >> 3) where did the eth2 interface come into the picture here using dhcp?
> >>     
> > Maybe this will help you:
> > https://fedorahosted.org/cobbler/wiki/KickstartSnippets#NICOrderingandIns...
> >
> > This makes sure that the interface that was used for PXE is also used for 
> > installation and then it simply writes the
> "/etc/sysconfig/network-scripts/" 
> > out of your cobbler data. This was the only way i found to relate the 
> > mac-addresses with the "eth" numbering.
> >
> > Greetings
> > Andy
> >
> >   
>  
>  bootif and ipappend 2 is already the default in newer cobbler installs, 
>  I'm thinking that section of the Wiki no longer needs to be there?
>  
>  --Michael
>  
>   
I've just removed that entire section. Some things are already the
defaults, and the rest is outdated (the snippet, the functionality was
adopted though, in what is now post_install_network_config).

-Jasper