search for: p6p1

...ets:4476995 errors:6940 dropped:0 overruns:0 frame:6940 TX packets:2130564 errors:0 dropped:0 overruns:0 carrier:0 # cat /proc/net/bonding/bond1 Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009) Bonding Mode: adaptive load balancing Primary Slave: None Currently Active Slave: p6p1 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: p6p1 MII Status: up Speed: 10000 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: 90:e2:ba:1e:12:5c Slave queue ID: 0 Slave Interface: p6p2 MII Status: up Speed: 10000 Mbps Duplex: full Li...

...t process shuffle them? More importantly, how do I prevent > this so that the system comes up properly after a kickstart install? > The reason I ask the version, is this is exactly the sort of thing that biosdevname is designed to solve. With biosdevname, you get devices like 'em1, em2, p6p1', which aren't as friendly as 'eth0' but also keep names sane and avoid the hair-tearing issues you're experiencing currently. You don't appear to be adding anything via your append line that would disable biosdevname, so I must assume you're using a much older 6 base in...

...Mask:255.255.255.0 inet6 addr: *****/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 p6p1 Link encap:Ethernet HWaddr **** UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 virbr0 Link encap:Ethernet HWaddr **** inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 vnet0 Link encap:Ethe...

...revent >> > this so that the system comes up properly after a kickstart install? >> > >> >> The reason I ask the version, is this is exactly the sort of thing that >> biosdevname is designed to solve. With biosdevname, you get devices like >> 'em1, em2, p6p1', which aren't as friendly as 'eth0' but also keep names >> sane and avoid the hair-tearing issues you're experiencing currently. >> You don't appear to be adding anything via your append line that would >> disable biosdevname, so I must assume you're u...

...rtantly, how do I > prevent > > this so that the system comes up properly after a kickstart install? > > > > The reason I ask the version, is this is exactly the sort of thing that > biosdevname is designed to solve. With biosdevname, you get devices like > 'em1, em2, p6p1', which aren't as friendly as 'eth0' but also keep names > sane and avoid the hair-tearing issues you're experiencing currently. > You don't appear to be adding anything via your append line that would > disable biosdevname, so I must assume you're using a much...

...rt install? >>>> > >>>> >>>> The reason I ask the version, is this is exactly the sort of thing >>>> that >>>> biosdevname is designed to solve. With biosdevname, you get devices >>>> like >>>> 'em1, em2, p6p1', which aren't as friendly as 'eth0' but also keep >>>> names >>>> sane and avoid the hair-tearing issues you're experiencing currently. >>>> You don't appear to be adding anything via your append line that would >>>> disable...

...this so that the system comes up properly after a kickstart install? >>> > >>> >>> The reason I ask the version, is this is exactly the sort of thing that >>> biosdevname is designed to solve. With biosdevname, you get devices like >>> 'em1, em2, p6p1', which aren't as friendly as 'eth0' but also keep names >>> sane and avoid the hair-tearing issues you're experiencing currently. >>> You don't appear to be adding anything via your append line that would >>> disable biosdevname, so I must assume...

...>>> >>>>>> The reason I ask the version, is this is exactly the sort of thing >>>>>> that >>>>>> biosdevname is designed to solve. With biosdevname, you get devices >>>>>> like >>>>>> 'em1, em2, p6p1', which aren't as friendly as 'eth0' but also keep >>>>>> names >>>>>> sane and avoid the hair-tearing issues you're experiencing >>>>>> currently. >>>>>> You don't appear to be adding anything via you...

...install? >>>>> > >>>>> >>>>> The reason I ask the version, is this is exactly the sort of thing that >>>>> biosdevname is designed to solve. With biosdevname, you get devices >>>>> like >>>>> 'em1, em2, p6p1', which aren't as friendly as 'eth0' but also keep >>>>> names >>>>> sane and avoid the hair-tearing issues you're experiencing currently. >>>>> You don't appear to be adding anything via your append line that would >>>&g...

...gt;>>>>> The reason I ask the version, is this is exactly the sort of thing >>>>>>> that >>>>>>> biosdevname is designed to solve. With biosdevname, you get devices >>>>>>> like >>>>>>> 'em1, em2, p6p1', which aren't as friendly as 'eth0' but also keep >>>>>>> names >>>>>>> sane and avoid the hair-tearing issues you're experiencing currently. >>>>>>> You don't appear to be adding anything via your append line t...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 23/02/15 08:16 PM, Steven Tardy wrote: > >> On Feb 23, 2015, at 6:34 PM, Ashley M. Kirchner >> <ashley at pcraft.com> wrote: >> >> I have a Dell server that has two built-in ethernet devices. When >> I kickstart the machine, they are correctly identified as eth0 >> and eth1 (correctly meaning they

...is this is exactly the sort of >>>>>>>> thing that >>>>>>>> biosdevname is designed to solve. With biosdevname, you get >>>>>>>> devices >>>>>>>> like >>>>>>>> 'em1, em2, p6p1', which aren't as friendly as 'eth0' but also keep >>>>>>>> names >>>>>>>> sane and avoid the hair-tearing issues you're experiencing >>>>>>>> currently. >>>>>>>> You don't appe...