Odd ifconfig output

Thomas_Chenault at Dell.com Thomas_Chenault at Dell.com
Thu Mar 1 14:08:59 CST 2007


This generally happens when HWADDR lines exist in some, but not all, of
the ifcfg-eth* configuration files. Check each of the ifcfg-eth* files
in /etc/sysconfig/network-scripts/. Make sure that HWADDR lines are
either consistently present or consistently absent and that each of the
HWADDR lines correctly identifies the associated hardware.


Thomas


-----Original Message-----
From: linux-poweredge-bounces at dell.com
[mailto:linux-poweredge-bounces at dell.com] On Behalf Of Todd Lyons
Sent: Thursday, March 01, 2007 1:43 PM
To: linux-poweredge-Lists
Subject: Odd ifconfig output

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

Hello all.

We have two PE 1950's with Broadcom Gig networking.  One is giving
strange output in terms of the device name.  The OS is CentOS 4.4 with
latest updates applied for both.

dmesg output (detection seems to be normal):
CPI: PCI interrupt 0000:09:00.0[A] -> GSI 16 (level, low) -> IRQ 169
divert: allocating divert_blk for eth0
eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz
found at mem f4000000, IRQ 169, node addr 0015c5f189f2
ACPI: PCI interrupt 0000:05:00.0[A] -> GSI 16 (level, low) -> IRQ 169
divert: allocating divert_blk for eth1
eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit 133MHz
found at mem f8000000, IRQ 169, node addr 0015c5f189f0

Driver:
The bnx module is loaded.

Network config:
[root at m5 mail]# ifconfig -a
dev5840   Link encap:Ethernet  HWaddr 00:15:C5:F1:89:F2  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:169 Memory:f4000000-f4011100 

eth0      Link encap:Ethernet  HWaddr 00:15:C5:F1:89:F0  
          inet addr:10.10.10.85  Bcast:10.10.10.255  Mask:255.255.255.0
          inet6 addr: fe80::215:c5ff:fef1:89f0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:190203 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9663 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:21791710 (20.7 MiB)  TX bytes:1568076 (1.4 MiB)
          Interrupt:169 Memory:f8000000-f8011100 

<snip>

eth1 is configured to not start at boot.  When I do a manual 'ifup
eth1', it adds this line to dmesg:
  bnx2: eth1: using MSI
And then ifconfig -a shows it as being named eth1 as expected.

1) Has anybody seen this before?
2) Any other comments?  I don't expect this to be a problem, it's just
something new that I had never noticed before.
- -- 
Regards...		Todd
Well, it's Karch...   --frequently heard after every amazing move he
does
Linux kernel 2.6.17-6mdv   7 users,  load average: 0.30, 0.30, 0.23
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFF5yzOY2VBGxIDMLwRAnO8AJ4j5NkkcMZeTdq6urA0i1RDMTF6bQCeM57A
kn+m9afOVD1v416DP5evGsA=
=FhPs
-----END PGP SIGNATURE-----

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge at dell.com
http://lists.us.dell.com/mailman/listinfo/linux-poweredge
Please read the FAQ at http://lists.us.dell.com/faq



More information about the Linux-PowerEdge mailing list