p1p1 on R710 showing up as _p1p1_ under SL 6.2?

Narendra_K at Dell.com Narendra_K at Dell.com
Thu Jul 19 14:09:30 CDT 2012


Hi, I tried reproducing this issue on an R610 with bond0 (miimon=100, mode 1)created from em1 and p2p1. The issue did not reproduce.
Enabling 'udev' in debug mode might be helpful. ( This could be done by changing udev_log="err" to udev_log="debug" in /etc/udev/udev.conf). It would log all the events and network interface renames to /var/log/messages.
Disabling rename_device was for debugging purpose.

Also, it seems like the NM_CONTROLLED= is set to "yes" for the slave ifcfg-p1p1 in your setup. Though I do not have any reason to suspect it, it may be useful to check if it helps with NM_CONTROLLED="no" as it is set for ifcfg-bond0.

>> None of the other systems I imaged at the same time behaved this way.
Do all of the systems have the same hardware and network configuration settings ?

Also, what is the output on this system after executing the following -

export INTERFACE=_p1p1_
/lib/udev/rename_device

With regards,
Narendra K

From: Adrian Allen [mailto:AAllen at envysion.com]
Sent: Thursday, July 19, 2012 1:50 AM
To: Adrian Allen; K, Narendra; linux-poweredge-Lists
Subject: RE: p1p1 on R710 showing up as _p1p1_ under SL 6.2?

It seems I spoke prematurely. The naming issue, that is, that "p1p1" was showing up as "_p1p1_" is no longer occurring, but unfortunately the device which was previously recognized as em2 is now showing up as p1p1, and the device which was previously _p1p1_ is now em2.

Obviously disabling the rename_device line was just for testing, and not a solution, as it breaks the consistent device names.

From: Adrian Allen
Sent: Wednesday, July 18, 2012 10:20 AM
To: Adrian Allen; Narendra_K at Dell.com; linux-poweredge at lists.us.dell.com
Subject: RE: p1p1 on R710 showing up as _p1p1_ under SL 6.2?

Hi, Narendra -

Sorry, I managed to hit send before I was done.

Commenting out that line does indeed resolve the issue.  I'm guessing that if more hardware is added later this could present a problem, but for now nothing should change on this box for at least a year.

Given that this was a fresh install, have you any idea why it might have done this?  None of the other systems I imaged at the same time behaved this way.


From: linux-poweredge-bounces at dell.com<mailto:linux-poweredge-bounces at dell.com> [mailto:linux-poweredge-bounces at dell.com] On Behalf Of Adrian Allen
Sent: Wednesday, July 18, 2012 9:52 AM
To: Narendra_K at Dell.com<mailto:Narendra_K at Dell.com>; linux-poweredge at lists.us.dell.com<mailto:linux-poweredge at lists.us.dell.com>
Subject: RE: p1p1 on R710 showing up as _p1p1_ under SL 6.2?

Sure, and thanks for having a look.

Here's biosdevname -d:


BIOS device: em1
Kernel name: em1
Permanent MAC: 78:2B:CB:39:2C:24
Assigned MAC : 78:2B:CB:39:2C:24
Driver: bnx2
Driver version: 2.1.11
Firmware version: 6.2.12 bc 5.2.3 NCSI 2.0.11
Bus Info: 0000:01:00.0
PCI name      : 0000:01:00.0
PCI Slot      : embedded
SMBIOS Device Type: Ethernet
SMBIOS Instance: 1
SMBIOS Label: Embedded NIC 1
sysfs Index: 1
sysfs Label: Embedded NIC 1
Embedded Index: 1

BIOS device: em2
Kernel name: em2
Permanent MAC: 78:2B:CB:39:2C:26
Assigned MAC : 78:2B:CB:39:2C:26
Driver: bnx2
Driver version: 2.1.11
Firmware version: 6.2.12 bc 5.2.3 NCSI 2.0.11
Bus Info: 0000:01:00.1
PCI name      : 0000:01:00.1
PCI Slot      : embedded
SMBIOS Device Type: Ethernet
SMBIOS Instance: 2
SMBIOS Label: Embedded NIC 2
sysfs Index: 2
sysfs Label: Embedded NIC 2
Embedded Index: 2

BIOS device: em3
Kernel name: em3
Permanent MAC: 78:2B:CB:39:2C:28
Assigned MAC : 78:2B:CB:39:2C:28
Driver: bnx2
Driver version: 2.1.11
Firmware version: 6.2.12 bc 5.2.3 NCSI 2.0.11
Bus Info: 0000:02:00.0
PCI name      : 0000:02:00.0
PCI Slot      : embedded
SMBIOS Device Type: Ethernet
SMBIOS Instance: 3
SMBIOS Label: Embedded NIC 3
sysfs Index: 3
sysfs Label: Embedded NIC 3
Embedded Index: 3

BIOS device: em4
Kernel name: em4
Permanent MAC: 78:2B:CB:39:2C:2A
Assigned MAC : 78:2B:CB:39:2C:2A
Driver: bnx2
Driver version: 2.1.11
Firmware version: 6.2.12 bc 5.2.3 NCSI 2.0.11
Bus Info: 0000:02:00.1
PCI name      : 0000:02:00.1
PCI Slot      : embedded
SMBIOS Device Type: Ethernet
SMBIOS Instance: 4
SMBIOS Label: Embedded NIC 4
sysfs Index: 4
sysfs Label: Embedded NIC 4
Embedded Index: 4

BIOS device: p1p1
Kernel name: _p1p1_
Permanent MAC: 00:10:18:7D:2D:20
Assigned MAC : 00:10:18:7D:2D:20
Driver: bnx2
Driver version: 2.1.11
Firmware version: 5.2.7 bc 5.2.2
Bus Info: 0000:05:00.0
PCI name      : 0000:05:00.0
PCI Slot      : 1
SMBIOS Label: PCI1
Index in slot: 1

BIOS device: p1p2
Kernel name: p1p2
Permanent MAC: 00:10:18:7D:2D:22
Assigned MAC : 00:10:18:7D:2D:22
Driver: bnx2
Driver version: 2.1.11
Firmware version: 5.2.7 bc 5.2.2
Bus Info: 0000:05:00.1
PCI name      : 0000:05:00.1
PCI Slot      : 1
SMBIOS Label: PCI1
Index in slot: 2


Here's ip link show:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: em1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP qlen 1000
    link/ether 78:2b:cb:39:2c:24 brd ff:ff:ff:ff:ff:ff
3: em2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 78:2b:cb:39:2c:26 brd ff:ff:ff:ff:ff:ff
4: em3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 78:2b:cb:39:2c:28 brd ff:ff:ff:ff:ff:ff
5: em4: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 78:2b:cb:39:2c:2a brd ff:ff:ff:ff:ff:ff
6: _p1p1_: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 00:10:18:7d:2d:20 brd ff:ff:ff:ff:ff:ff
7: p1p2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 00:10:18:7d:2d:22 brd ff:ff:ff:ff:ff:ff
8: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP
    link/ether 78:2b:cb:39:2c:24 brd ff:ff:ff:ff:ff:ff
9: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether 78:2b:cb:39:2c:24 brd ff:ff:ff:ff:ff:ff

Here's the ifcfg files, with IP's and the domain name etc removed:

----ifcfg-bond0--------
DEVICE="bond0"
NM_CONTROLLED="no"
BONDING_OPTS="use_carrier=0 miimon=1000 mode=4"
ONPARENT="yes"
BRIDGE="br0"
IPADDR="x.x.x.60"
NETMASK="255.255.255.0"
DNS1="x.x.x.2"
----ifcfg-br0--------
DEVICE="br0"
TYPE="Bridge"
BOOTPROTO="static"
IPADDR="x.x.x.60"
NETMASK="255.255.255.0"
GATEWAY="x.x.x.3"
DNS1="x.x.x.107"
DNS2="x.x.x.108"
DOMAIN="redacted"
NM_CONTROLLED="no"
ONBOOT="yes"
DELAY="0"
----ifcfg-br0:1--------
DEVICE="br0:1"
BOOTPROTO="static"
IPADDR="x.x.x.100"
NETMASK="255.255.255.0"
NM_CONTROLLED="no"
ONBOOT="yes"

----ifcfg-em1--------
DEVICE="em1"
HWADDR="78:2b:cb:39:2c:24"
NM_CONTROLLED="no"
ONBOOT="yes"
MASTER="bond0"
SLAVE="yes"
----ifcfg-em2--------
DEVICE="em2"
HWADDR="78:2b:cb:39:2c:26"
IPV6INIT="no"
NM_CONTROLLED="yes"
ONBOOT="no"
----ifcfg-em3--------
DEVICE="em3"
HWADDR="78:2b:cb:39:2c:28"
NM_CONTROLLED="yes"
ONBOOT="no"
----ifcfg-em4--------
DEVICE="em4"
HWADDR="78:2b:cb:39:2c:2a"
NM_CONTROLLED="yes"
ONBOOT="no"
----ifcfg-lo--------
DEVICE=lo
IPADDR=127.0.0.1
NETMASK=255.0.0.0
NETWORK=127.0.0.0
# If you're having problems with gated making 127.0.0.0/8 a martian,
# you can change this to something else (255.255.255.255, for example)
BROADCAST=127.255.255.255
ONBOOT=yes
NAME=loopback
----ifcfg-p1p1--------
DEVICE="p1p1"
HWADDR="00:10:18:7D:2D:20"
NM_CONTROLLED="yes"
ONBOOT="yes"
MASTER="bond0"
SLAVE="yes"
----ifcfg-p1p2--------
DEVICE="p1p2"
HWADDR="00:10:18:7D:2D:22"
NM_CONTROLLED="yes"
ONBOOT="no"



From: linux-poweredge-bounces at dell.com<mailto:linux-poweredge-bounces at dell.com> [mailto:linux-poweredge-bounces at dell.com] On Behalf Of Narendra_K at Dell.com<mailto:Narendra_K at Dell.com>
Sent: Wednesday, July 18, 2012 1:57 AM
To: Adrian Allen; linux-poweredge at lists.us.dell.com<mailto:linux-poweredge at lists.us.dell.com>
Subject: RE: p1p1 on R710 showing up as _p1p1_ under SL 6.2?

Hi,

Could you please share the output from "biosdevname -d", dmidecode, "ip link show"  and  /etc/sysconfig/network-scripts/ifcfg-* file contents ?

Also, when biosdevname is enabled, '/etc/udev/rules.d/70-persistent-net-rules' file is not generated.

Just curious to know if the interface is still renamed to _p1p1_ if you comment the following line from /lib/udev/rules.d/60-net.rules and reboot (ensure the 70-persistent-net-rules is deleted before rebooting)

ACTION=="add", SUBSYSTEM=="net", PROGRAM="/lib/udev/rename_device", RESULT=="?*", ENV{INTERFACE_NAME}="$result"

With regards,
Narendra K

From: linux-poweredge-bounces-Lists On Behalf Of Adrian Allen
Sent: Wednesday, July 18, 2012 5:44 AM
To: linux-poweredge-Lists
Subject: p1p1 on R710 showing up as _p1p1_ under SL 6.2?

Greetings;

Subject line basically says it all.

I've tried the biosdevname utility and when I pass it _p1p1_ it responds with p1p1, so that utility appears to correctly determine the needed name.

ip link shows the interface as _p1p1_.  I've tried editing the /etc/udev/rules.d/70-persistent-net-rules file to correct the name, but it just gets replaced on boot.  I've read through /lib/udev/write_net_rules and I don't really see how it would come up with this interface name based on my understanding of the code (which is admittedly limited).

Also, side topic: Is there some place where the cumulative mailing list archives are searchable? I could not locate one.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20120720/d9bb3f27/attachment-0001.html 


More information about the Linux-PowerEdge mailing list