Please help with "Bringing up interface eth0: RTNETLINK answers: No such device" [LONG]

Latest response

Hello All,

 

I'm a struggling RHEL noob trying to configure network interfaces for use as a bridging firewall.  I am using RHEL 5.6 for IA-64 on an HP Integrity RX-2600.  Previously, I had the network interfaces configured successfully, but after a PCI card shuffle, I started getting RTNETLINK messages.  The original PCI configuration had a PCI-X to PCI bridge adapter in slot 1, and a 1000Base-LX adapter in slot 4.  I removed the bridge adapter, and put the 1000Base-LX adapter in its place.  Then, RTNETLINK complaints arose.  I tried removing the network adapter, booted up, and then shutdown.  Next, I reinstalled the network adapter, and booted up again, but no luck.

 

Any light that can be shed upon this problem will be greatly appreciated.

 

----- BEGIN console boot messages -----

Loading.: Red Hat Enterprise Linux Server                           
Starting: Red Hat Enterprise Linux Server

ELILO boot: Uncompressing Linux... done
Loading file initrd-2.6.18-274.3.1.el5.img...done
Linux version 2.6.18-274.3.1.el5 (mockbuild@natasha.build.redhat.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-51)) #1 SMP Fri Aug 26 18:48:23 EDT 2011
EFI v1.10 by HP: SALsystab=0x3fb38000 ACPI 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000
booting generic kernel on platform hpzx1
PCDP: v0 at 0x3fb2c000
Early serial console at MMIO 0xf4050000 (options '9600n8')
rsvd_region[0]: [0xe000000001000000, 0xe0000000010000a8)
rsvd_region[1]: [0xe000000004000000, 0xe000000004e94e68)
rsvd_region[2]: [0xe0000040fea40008, 0xe0000040fea40058)
rsvd_region[3]: [0xe0000040fea43fa4, 0xe0000040fea44008)
rsvd_region[4]: [0xe0000040fea46000, 0xe0000040fef95b16)
rsvd_region[5]: [0xe0000040fef9c008, 0xe0000040fef9c6c8)
rsvd_region[6]: [0xffffffffffffffff, 0xffffffffffffffff)
Initial ramdisk at: 0xe0000040fea46000 (5569302 bytes)
SAL 3.1: HP version 2.31
SAL Platform features: None
SAL: AP wakeup using external interrupt vector 0xff
No logical to physical processor mapping available
cpu_init: PAL max_purges is overridden to 1 PALO is required for multiple outsanding ptc.g
ACPI: Local APIC address c0000000fee00000
GSI 36 (level, low) -> CPU 0 (0x0000) vector 48
2 CPUs available, 2 CPUs total
MCA related initialization done
SMP: Allowing 2 CPUs, 0 hotplug CPUs
Built 1 zonelists.  Total pages: 390218
Kernel command line: BOOT_IMAGE=scsi0:EFI\redhat\vmlinuz-2.6.18-274.3.1.el5 root=/dev/VolGroup00/LogVol00  rhgb quiet ro
Red Hat nash version 5.1.19.6 starting
  Reading all physical volumes.  This may take a while...
  Found volume group "VolGroup00" using metadata type lvm2
  Internal error: Maps lock 14778368 < unlock 14794752
  Internal error: Maps lock 14860288 < unlock 14876672
  2 logical volume(s) in volume group "VolGroup00" now active
                Welcome to Red Hat Enterprise Linux Server
                Press 'I' to enter interactive startup.
Setting clock  (utc): Wed Oct  5 08:07:51 PDT 2011 [  OK  ]
Starting udev: [  OK  ]
Loading default keymap (us): [  OK  ]
Setting hostname ccswall:  [  OK  ]
Setting up Logical Volume Management:   /dev/hda: open failed: No medium found
  2 logical volume(s) in volume group "VolGroup00" now active
[  OK  ]
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/VolGroup00/LogVol00
/dev/VolGroup00/LogVol00: clean, 130716/15844224 files, 1474192/15835136 blocks
[  OK  ]
Remounting root filesystem in read-write mode:  [  OK  ]
Mounting local filesystems:  [  OK  ]
Enabling local filesystem quotas:  [  OK  ]
INIT: Entering runlevel: 5
Entering non-interactive startup
Starting background readahead: [  OK  ]
Checking for hardware changes [  OK  ]
[  OK  ] iSCSI daemon: [  OK  ]
[  OK  ]
Bringing up loopback interface:  [  OK  ]
Bringing up interface eth0:  RTNETLINK answers: No such device
[  OK  ]
Bringing up interface eth1:  RTNETLINK answers: No such device
[  OK  ]
Starting auditd: [  OK  ]
Starting system logger: [  OK  ]
Starting kernel logger: [  OK  ]
Starting irqbalance: [  OK  ]
iscsid (pid  1447) is running...
Setting up iSCSI targets: iscsiadm: No records found
[  OK  ]
Starting portmap: [  OK  ]
Starting NFS statd: [  OK  ]
Starting RPC idmapd: [  OK  ]
Starting system message bus: [  OK  ]
[  OK  ] Bluetooth services:[  OK  ]
Mounting other filesystems:  [  OK  ]
Starting PC/SC smart card daemon (pcscd): [  OK  ]
Starting acpi daemon: [  OK  ]
Starting HAL daemon: [  OK  ]
Starting hidd: [  OK  ]
Starting monitoring for VG VolGroup00:   /dev/hda: open failed: No medium found
  2 logical volume(s) in volume group "VolGroup00" monitored
[  OK  ]
Starting autofs:  Loading autofs4: [  OK  ]
Starting automount: [  OK  ]
[  OK  ]
Starting hpiod: [  OK  ]
Starting hpssd: [  OK  ]
Starting sshd: [  OK  ]
Starting cups: [  OK  ]
Starting xinetd: [  OK  ]
Starting sendmail: [  OK  ]
Starting sm-client: [  OK  ]
Starting console mouse services: [  OK  ]
Starting crond: [  OK  ]
Starting xfs: [  OK  ]
Starting anacron: [  OK  ]
[  OK  ] atd: [  OK  ]
Starting salinfo_decode_all: [  OK  ]
Starting background readahead: [  OK  ]
Starting Red Hat Network Daemon: [  OK  ]
Starting yum-updatesd: [  OK  ]
Starting Avahi daemon... [  OK  ]
Starting smartd:
Red Hat Enterprise Linux Server release 5.7 (Tikanga)
Kernel 2.6.18-274.3.1.el5 on an ia64

----- END console boot messages -----

 

----- BEGIN /var/log/messages -----

syslogd 1.4.1: restart.
kernel: klogd 1.4.1, log source = /proc/kmsg started.
kernel: Linux version 2.6.18-274.3.1.el5 (mockbuild@natasha.build.redhat.com) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-51)) #1 SMP Fri Aug 26 18:48:23 EDT 2011
kernel: EFI v1.10 by HP: SALsystab=0x3fb38000 ACPI 2.0=0x3fb2e000 SMBIOS=0x3fb3a000 HCDP=0x3fb2c000
kernel: booting generic kernel on platform hpzx1
kernel: PCDP: v0 at 0x3fb2c000
kernel: Early serial console at MMIO 0xf4050000 (options '9600n8')
kernel: rsvd_region[0]: [0xe000000001000000, 0xe0000000010000a8)
kernel: rsvd_region[1]: [0xe000000004000000, 0xe000000004e94e68)
kernel: rsvd_region[2]: [0xe0000040fea40008, 0xe0000040fea40058)
kernel: rsvd_region[3]: [0xe0000040fea43fa4, 0xe0000040fea44008)
kernel: rsvd_region[4]: [0xe0000040fea46000, 0xe0000040fef95b16)
kernel: rsvd_region[5]: [0xe0000040fef9c008, 0xe0000040fef9c6c8)
kernel: rsvd_region[6]: [0xffffffffffffffff, 0xffffffffffffffff)
kernel: Initial ramdisk at: 0xe0000040fea46000 (5569302 bytes)
kernel: SAL 3.1: HP version 2.31
kernel: SAL Platform features: None
kernel: SAL: AP wakeup using external interrupt vector 0xff
kernel: No logical to physical processor mapping available
kernel: cpu_init: PAL max_purges is overridden to 1 PALO is required for multiple outsanding ptc.g
kernel: ACPI: Local APIC address c0000000fee00000
kernel: GSI 36 (level, low) -> CPU 0 (0x0000) vector 48
kernel: 2 CPUs available, 2 CPUs total
kernel: MCA related initialization done
rpc.statd[1807]: Version 1.0.9 Starting
kernel: SMP: Allowing 2 CPUs, 0 hotplug CPUs
kernel: Built 1 zonelists.  Total pages: 390218
kernel: Kernel command line: BOOT_IMAGE=scsi0:EFI\redhat\vmlinuz-2.6.18-274.3.1.el5 root=/dev/VolGroup00/LogVol00  rhgb quiet ro
kernel: PID hash table entries: 4096 (order: 12, 32768 bytes)
kernel: Console: colour VGA+ 80x25
kernel: Memory: 6154992k/6243488k available (6688k code, 108944k reserved, 4001k data, 464k init)
kernel: McKinley Errata 9 workaround not needed; disabling it
kernel: Calibrating delay loop... 2244.60 BogoMIPS (lpj=1122304)
kernel: Security Framework v1.0.0 initialized
kernel: SELinux:  Initializing.
kernel: selinux_register_security:  Registering secondary module capability
kernel: Capability LSM initialized as secondary
kernel: Dentry cache hash table entries: 1048576 (order: 9, 8388608 bytes)
kernel: Inode-cache hash table entries: 524288 (order: 8, 4194304 bytes)
kernel: Mount-cache hash table entries: 1024
kernel: ACPI: Core revision 20060707
hcid[1865]: Bluetooth HCI daemon
kernel: Boot processor id 0x0/0x0
kernel: cpu_init: PAL max_purges is overridden to 1 PALO is required for multiple outsanding ptc.g
kernel: Fixed BSP b0 value from CPU 1
sdpd[1869]: Bluetooth SDP daemon
hcid[1865]: Register path:/org/bluez fallback:1
kernel: CPU 1: synchronized ITC with CPU 0 (last diff -27 cycles, maxerr 681 cycles)
kernel: Calibrating delay loop... 2244.60 BogoMIPS (lpj=1122304)
kernel: Brought up 2 CPUs
kernel: Total of 2 processors activated (4489.21 BogoMIPS).
kernel: migration_cost=6421
kernel: checking if image is initramfs... it is
kernel: Freeing initrd memory: 5424kB freed
pcscd: pcscdaemon.c:507:main() pcsc-lite 1.4.4 daemon ready.
kernel: DMI 2.3 present.
kernel: NET: Registered protocol family 16
kernel: ACPI: bus type pci registered
kernel: ACPI: Interpreter enabled
kernel: ACPI: Using IOSAPIC for interrupt routing
kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
kernel: PCI: Firmware left 0000:00:03.0 e100 interrupts enabled, disabling
kernel: ACPI: PCI Root Bridge [PCI1] (0000:20)
kernel: ACPI: PCI Root Bridge [PCI2] (0000:40)
kernel: ACPI: PCI Root Bridge [PCI3] (0000:60)
kernel: ACPI: PCI Root Bridge [PCI4] (0000:80)
kernel: ACPI: PCI Root Bridge [PCI6] (0000:c0)
pcscd: hotplug_libusb.c:402:HPEstablishUSBNotifications() Driver ifd-egate.bundle does not support IFD_GENERATE_HOTPLUG. Using active polling instead.
pcscd: hotplug_libusb.c:411:HPEstablishUSBNotifications() Polling forced every 1 second(s)
kernel: ACPI: PCI Root Bridge [PCI7] (0000:e0)
kernel: Linux Plug and Play Support v0.97 (c) Adam Belay
kernel: pnp: PnP ACPI init
kernel: GSI 34 (edge, high) -> CPU 1 (0x0100) vector 49
kernel: GSI 35 (edge, high) -> CPU 0 (0x0000) vector 50
kernel: pnp: PnP ACPI: found 11 devices
kernel: usbcore: registered new driver usbfs
kernel: usbcore: registered new driver hub
kernel: IOC: zx1 2.3 HPA 0xfed01000 IOVA space 1024Mb at 0x40000000
kernel: NetLabel: Initializing
kernel: NetLabel:  domain hash size = 128
kernel: NetLabel:  protocols = UNLABELED CIPSOv4
kernel: NetLabel:  unlabeled traffic allowed by default
kernel: NET: Registered protocol family 2
kernel: IP route cache hash table entries: 262144 (order: 7, 2097152 bytes)
kernel: TCP established hash table entries: 1048576 (order: 10, 16777216 bytes)
kernel: TCP bind hash table entries: 65536 (order: 6, 1048576 bytes)
kernel: TCP: Hash tables configured (established 1048576 bind 65536)
kernel: TCP reno registered
kernel: perfmon: version 2.0 IRQ 238
kernel: perfmon: Itanium 2 PMU detected, 16 PMCs, 18 PMDs, 4 counters (47 bits)
kernel: PAL Information Facility v0.5
kernel: perfmon: added sampling format default_format
kernel: perfmon_default_smpl: default_format v2.0 registered
kernel: audit: initializing netlink socket (disabled)
kernel: type=2000 audit(1317827233.157:1): initialized
kernel: Total HugeTLB memory allocated, 0
kernel: VFS: Disk quotas dquot_6.5.1
kernel: Dquot-cache hash table entries: 2048 (order 0, 16384 bytes)
kernel: Initializing Cryptographic API
kernel: alg: No test for crc32c (crc32c-generic)
kernel: ksign: Installing public key data
kernel: Loading keyring
kernel: - Added public key 9B6C3F09471930AE
kernel: - User ID: Red Hat, Inc. (Kernel Module GPG key)
kernel: io scheduler noop registered
kernel: io scheduler anticipatory registered
kernel: io scheduler deadline registered
kernel: io scheduler cfq registered (default)
kernel: pci_hotplug: PCI Hot Plug PCI Core version: 0.5
kernel: ACPI: Thermal Zone [THM0] (27 C)
kernel: EFI Time Services Driver v0.4
kernel: Linux agpgart interface v0.101 (c) Dave Jones
kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 16 ports, IRQ sharing enabled
kernel: 00:04: ttyS0 at MMIO 0xff5e0000 (irq = 49) is a 16550A
kernel: 00:05: ttyS1 at MMIO 0xff5e2000 (irq = 50) is a 16550A
kernel: GSI 82 (level, low) -> CPU 1 (0x0100) vector 51
kernel: ACPI: PCI Interrupt 0000:e0:01.0[A] -> GSI 82 (level, low) -> IRQ 51
kernel: 0000:e0:01.0: ttyS2 at MMIO 0xf4051000 (irq = 51) is a 16550A
kernel: ACPI: PCI Interrupt 0000:e0:01.1[A] -> GSI 82 (level, low) -> IRQ 51
kernel: 0000:e0:01.1: ttyS3 at MMIO 0xf4050000 (irq = 51) is a 16550A
kernel: 0000:e0:01.1: ttyS4 at MMIO 0xf4050010 (irq = 51) is a 16550A
kernel: 0000:e0:01.1: ttyS5 at MMIO 0xf4050038 (irq = 51) is a 16550A
kernel: brd: module loaded
kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
kernel: CMD649: IDE controller at PCI slot 0000:00:02.0
kernel: GSI 21 (level, low) -> CPU 0 (0x0000) vector 52
kernel: ACPI: PCI Interrupt 0000:00:02.0[A] -> GSI 21 (level, low) -> IRQ 52
kernel: CMD649: chipset revision 2
kernel: CMD649: 100% native mode on irq 52
kernel:     ide0: BM-DMA at 0x0d40-0x0d47, BIOS settings: hda:pio, hdb:pio
kernel:     ide1: BM-DMA at 0x0d48-0x0d4f, BIOS settings: hdc:pio, hdd:pio
kernel: hda: DW-224E, ATAPI CD/DVD-ROM drive
kernel: ide0 at 0xd58-0xd5f,0xd66 on irq 52
kernel: ide-floppy driver 0.99.newide
kernel: usbcore: registered new driver hiddev
kernel: usbcore: registered new driver usbhid
kernel: drivers/usb/input/hid-core.c: v2.6:USB HID core driver
kernel: mice: PS/2 mouse device common for all mice
kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
kernel: md: bitmap version 4.39
kernel: EFI Variables Facility v0.08 2004-May-17
kernel: TCP bic registered
kernel: Initializing IPsec netlink socket
kernel: NET: Registered protocol family 1
kernel: NET: Registered protocol family 17
kernel: Adding console on ttyS3 at MMIO 0xf4050000 (options '9600n8')
kernel: Initalizing network drop monitor service
kernel: Freeing unused kernel memory: 464kB freed
kernel: GSI 18 (level, low) -> CPU 1 (0x0100) vector 53
kernel: ACPI: PCI Interrupt 0000:00:01.2[C] -> GSI 18 (level, low) -> IRQ 53
kernel: ehci_hcd 0000:00:01.2: EHCI Host Controller
kernel: ehci_hcd 0000:00:01.2: new USB bus registered, assigned bus number 1
kernel: ehci_hcd 0000:00:01.2: irq 53, io mem 0x80021000
kernel: ehci_hcd 0000:00:01.2: USB 2.0 started, EHCI 0.95, driver 10 Dec 2004
kernel: usb usb1: configuration #1 chosen from 1 choice
kernel: hub 1-0:1.0: USB hub found
kernel: hub 1-0:1.0: 5 ports detected
kernel: GSI 16 (level, low) -> CPU 0 (0x0000) vector 54
kernel: ACPI: PCI Interrupt 0000:00:01.0[A] -> GSI 16 (level, low) -> IRQ 54
kernel: ohci_hcd 0000:00:01.0: OHCI Host Controller
kernel: ohci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 2
kernel: ohci_hcd 0000:00:01.0: irq 54, io mem 0x80023000
kernel: usb usb2: configuration #1 chosen from 1 choice
kernel: hub 2-0:1.0: USB hub found
kernel: hub 2-0:1.0: 3 ports detected
kernel: GSI 17 (level, low) -> CPU 1 (0x0100) vector 55
kernel: ACPI: PCI Interrupt 0000:00:01.1[B] -> GSI 17 (level, low) -> IRQ 55
kernel: ohci_hcd 0000:00:01.1: OHCI Host Controller
kernel: ohci_hcd 0000:00:01.1: new USB bus registered, assigned bus number 3
kernel: ohci_hcd 0000:00:01.1: irq 55, io mem 0x80022000
kernel: usb usb3: configuration #1 chosen from 1 choice
kernel: hub 3-0:1.0: USB hub found
kernel: hub 3-0:1.0: 2 ports detected
kernel: USB Universal Host Controller Interface driver v3.0
kernel: SCSI subsystem initialized
kernel: Fusion MPT base driver 3.04.18rh
kernel: Copyright (c) 1999-2008 LSI Corporation
kernel: Fusion MPT SPI Host driver 3.04.18rh
kernel: GSI 27 (level, low) -> CPU 0 (0x0000) vector 56
kernel: ACPI: PCI Interrupt 0000:20:01.0[A] -> GSI 27 (level, low) -> IRQ 56
kernel: mptbase: ioc0: Initiating bringup
kernel: ioc0: LSI53C1030 B2: Capabilities={Initiator,Target}
kernel: scsi0 : ioc0: LSI53C1030 B2, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=56
kernel:   Vendor: HP 73.4G  Model: ST373454LC        Rev: HPC2
kernel:   Type:   Direct-Access                      ANSI SCSI revision: 03
kernel:  target0:0:0: Beginning Domain Validation
kernel:  target0:0:0: Ending Domain Validation
kernel:  target0:0:0: FAST-160 WIDE SCSI 320.0 MB/s DT IU QAS RTI WRFLOW PCOMP (6.25 ns, offset 63)
kernel: SCSI device sda: 143374738 512-byte hdwr sectors (73408 MB)
kernel: sda: Write Protect is off
kernel: SCSI device sda: drive cache: write through w/ FUA
kernel: SCSI device sda: 143374738 512-byte hdwr sectors (73408 MB)
kernel: sda: Write Protect is off
kernel: SCSI device sda: drive cache: write through w/ FUA
kernel:  sda: sda1 sda2
kernel: sd 0:0:0:0: Attached scsi disk sda
kernel: GSI 28 (level, low) -> CPU 1 (0x0100) vector 57
kernel: ACPI: PCI Interrupt 0000:20:01.1[B] -> GSI 28 (level, low) -> IRQ 57
kernel: mptbase: ioc1: Initiating bringup
kernel: ioc1: LSI53C1030 B2: Capabilities={Initiator,Target}
kernel: scsi1 : ioc1: LSI53C1030 B2, FwRev=01032300h, Ports=1, MaxQ=255, IRQ=57
kernel: device-mapper: uevent: version 1.0.3
kernel: device-mapper: ioctl: 4.11.6-ioctl (2011-02-18) initialised: dm-devel@redhat.com
kernel: device-mapper: dm-raid45: initialized v0.2594l
kernel: kjournald starting.  Commit interval 5 seconds
kernel: EXT3-fs: mounted filesystem with ordered data mode.
kernel: SELinux:  Disabled at runtime.
hidd[1995]: Bluetooth HID daemon
kernel: type=1404 audit(1317827269.314:2): selinux=0 auid=4294967295 ses=4294967295
kernel: tg3.c:v3.116 (December 3, 2010)<6>GSI 29 (level, low) -> CPU 0 (0x0000) vector 58
kernel: ACPI: PCI Interrupt 0000:20:02.0[A] -> GSI 29 (level, low) -> IRQ 58
kernel: e100: Intel(R) PRO/100 Network Driver, 3.5.10-k3-1-NAPI
kernel: e100: Copyright(c) 1999-2005 Intel Corporation
kernel: GSI 20 (level, low) -> CPU 1 (0x0100) vector 59
kernel: ACPI: PCI Interrupt 0000:00:03.0[A] -> GSI 20 (level, low) -> IRQ 59
kernel: e100: eth0: e100_probe: addr 0x80020000, irq 59, MAC addr 00:11:0A:dd:ee:ff
kernel: hda: ATAPI 24X DVD-ROM CD-R/RW drive, 1658kB Cache, UDMA(33)
kernel: Uniform CD-ROM driver Revision: 3.20
kernel: Intel(R) PRO/1000 Network Driver - version 7.3.21-k4-3-NAPI
kernel: Copyright (c) 1999-2006 Intel Corporation.
kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
kernel: tg3 0000:20:02.0: eth1: eth1: Tigon3 [partno(BCM95700A6) rev 0105 PHY(5701)] (PCI:66MHz:64-bit) 10/100/1000Base-T Ethernet 00:11:0a:aa:bb:cc
kernel: tg3 0000:20:02.0: eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[0]
kernel: tg3 0000:20:02.0: eth1: dma_rwctrl[76ff2d0f] dma_mask[64-bit]
kernel: GSI 60 (level, low) -> CPU 0 (0x0000) vector 60
kernel: ACPI: PCI Interrupt 0000:80:01.0[A] -> GSI 60 (level, low) -> IRQ 60
kernel: e1000: 0000:80:01.0: e1000_probe: (PCI-X:133MHz:64-bit) 00:1b:21:xx:yy:zz
kernel: e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
kernel: lp: driver loaded but no devices found
kernel: ACPI: Power Button (FF) [PWRF]
kernel: ACPI: Sleep Button (FF) [SLPF]
kernel: ACPI: Mapper loaded
kernel: md: Autodetecting RAID arrays.
kernel: md: autorun ...
kernel: md: ... autorun DONE.
kernel: device-mapper: multipath: version 1.0.6 loaded
kernel: loop: loaded (max 8 devices)
kernel: EXT3 FS on dm-0, internal journal
kernel: Adding 8224736k swap on /dev/VolGroup00/LogVol01.  Priority:-1 extents:1 across:8224736k
kernel: Loading iSCSI transport class v2.0-871.
kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
kernel: All bugs added by David S. Miller <davem@redhat.com>
kernel: libcxgbi:libcxgbi_init_module: tag itt 0x1fff, 13 bits, age 0xf, 4 bits.
kernel: libcxgbi:ddp_setup_host_page_size: system PAGE 16384, ddp idx 2.
kernel: Chelsio T3 iSCSI Driver cxgb3i v2.0.0 (Jun. 2010)
kernel: iscsi: registered transport (cxgb3i)
kernel: NET: Registered protocol family 10
kernel: lo: Disabled Privacy Extensions
kernel: IPv6 over IPv4 tunneling driver
kernel: cnic: Broadcom NetXtreme II CNIC Driver cnic v2.2.13 (Jan 31, 2011)
kernel: Broadcom NetXtreme II iSCSI Driver bnx2i v2.6.2.3 (Dec 31, 2010)
kernel: iscsi: registered transport (bnx2i)
kernel: iscsi: registered transport (tcp)
kernel: iscsi: registered transport (iser)
kernel: iscsi: registered transport (be2iscsi)
kernel: 8021q: adding VLAN 0 to HW filter on device eth0
kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
kernel: ADDRCONF(NETDEV_UP): eth1: link is not ready
kernel: Bluetooth: Core ver 2.10
kernel: NET: Registered protocol family 31
kernel: Bluetooth: HCI device and connection manager initialized
kernel: Bluetooth: HCI socket layer initialized
kernel: Bluetooth: L2CAP ver 2.8
kernel: Bluetooth: L2CAP socket layer initialized
kernel: Bluetooth: RFCOMM socket layer initialized
kernel: Bluetooth: RFCOMM TTY layer initialized
kernel: Bluetooth: RFCOMM ver 1.8
kernel: Bluetooth: HIDP (Human Interface Emulation) ver 1.1
automount[2025]: lookup_read_master: lookup(nisplus): couldn't locate nis+ table auto.master
hpiod: 1.6.7 accepting connections at 2208...
xinetd[2082]: xinetd Version 2.3.14 started with libwrap loadavg labeled-networking options compiled in.
xinetd[2082]: Started working: 0 available services
gpm[2118]: *** info [startup.c(95)]:
gpm[2118]: Started gpm successfully. Entered daemon mode.
rhnsd: Red Hat Network Services Daemon running with check_in interval set to 240 seconds.
rhnsd: Red Hat Network Services Daemon running with check_in interval set to 240 seconds.
rhnsd[2213]: Red Hat Network Services Daemon starting up.
avahi-daemon[2231]: Found user 'avahi' (UID 70) and group 'avahi' (GID 70).
avahi-daemon[2231]: Successfully dropped root privileges.
avahi-daemon[2231]: avahi-daemon 0.6.16 starting up.
avahi-daemon[2231]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
avahi-daemon[2231]: Successfully called chroot().
avahi-daemon[2231]: Successfully dropped remaining capabilities.
avahi-daemon[2231]: No service found in /etc/avahi/services.
avahi-daemon[2231]: Network interface enumeration completed.
avahi-daemon[2231]: Registering HINFO record with values 'IA64'/'LINUX'.
avahi-daemon[2231]: Server startup complete. Host name is ccswall.local. Local service cookie is 3037389712.
smartd[2251]: smartd version 5.38 [ia64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
smartd[2251]: Home page is http://smartmontools.sourceforge.net/  
smartd[2251]: Opened configuration file /etc/smartd.conf
smartd[2251]: Configuration file /etc/smartd.conf was parsed, found DEVICESCAN, scanning devices
smartd[2251]: Device: /dev/hda, opened
smartd[2251]: Device: /dev/hda, packet devices [this device CD/DVD] not SMART capable
smartd[2251]: Device: /dev/sda, opened
smartd[2251]: Device: /dev/sda, is SMART capable. Adding to "monitor" list.
smartd[2251]: Monitoring 0 ATA and 1 SCSI devices
smartd[2253]: smartd has fork()ed into background mode. New PID=2253.
pcscd: winscard.c:304:SCardConnect() Reader E-Gate 0 0 Not Found

----- END /var/log/messages -----

 

# /etc/sysconfig/network-scripts/ifcfg-eth0

# PCI-X 1000Base-LX
# Intel PRO/1000 MF Server Adapter -- Model PWLA9490LX
DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
HWADDR=00:1b:21:xx:yy:zz

# /etc/sysconfig/network-scripts/ifcfg-eth1

# On-board 10/100/1000Base-T

# Broadcom Corporation NetXtreme BCM5701 Gigabit Ethernet
DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
HWADDR=00:11:0a:aa:bb:cc

# /etc/sysconfig/network-scripts/ifcfg-eth2

# On-board 100Base-T

# Intel Corporation 82557/8/9/0/1 Ethernet Pro 100
DEVICE=eth2
HWADDR=00:11:0a:dd:ee:ff
ONBOOT=no
BOOTPROTO=none
NETMASK=255.255.255.0
IPADDR=192.168.100.200
GATEWAY=192.168.100.254
TYPE=Ethernet

# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1B:21:XX:YY:ZZ 
          UP 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)

eth1      Link encap:Ethernet  HWaddr 00:11:0A:AA:BB:CC 
          UP 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:58 Memory:90800000-90810000

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
          RX packets:60 errors:0 dropped:0 overruns:0 frame:0
          TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:8540 (8.3 KiB)  TX bytes:8540 (8.3 KiB)

# ifconfig eth0 down
# ifconfig eth0 up
# ifdown eth0
# ifup eth0
RTNETLINK answers: No such device
#
# ifconfig eth1 down
# ifconfig eth1 up
# ifdown eth1
# ifup eth1
RTNETLINK answers: No such device
#
# udevinfo -a -p /sys/class/net/eth0

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/class/net/eth0':
    KERNEL=="eth0"
    SUBSYSTEM=="net"
    SYSFS{weight}=="64"
    SYSFS{tx_queue_len}=="1000"
    SYSFS{flags}=="0x1003"
    SYSFS{mtu}=="1500"
    SYSFS{operstate}=="down"
    SYSFS{dormant}=="0"
    SYSFS{carrier}=="0"
    SYSFS{broadcast}=="ff:ff:ff:ff:ff:ff"
    SYSFS{address}=="00:1b:21:xx:yy:zz"
    SYSFS{link_mode}=="0"
    SYSFS{type}=="1"
    SYSFS{features}=="0xffffffffd00113a9"
    SYSFS{ifindex}=="4"
    SYSFS{iflink}=="4"
    SYSFS{addr_len}=="6"

  looking at parent device '/devices/pci0000:80/0000:80:01.0':
    ID=="0000:80:01.0"
    BUS=="pci"
    DRIVER=="e1000"
    SYSFS{broken_parity_status}=="0"
    SYSFS{enable}=="1"
    SYSFS{modalias}=="pci:v00008086d00001027sv00008086sd00001002bc02sc00i00"
    SYSFS{irq}=="60"
    SYSFS{class}=="0x020000"
    SYSFS{subsystem_device}=="0x1002"
    SYSFS{subsystem_vendor}=="0x8086"
    SYSFS{device}=="0x1027"
    SYSFS{vendor}=="0x8086"

  looking at parent device '/devices/pci0000:80':
    ID=="pci0000:80"
    BUS==""
    DRIVER==""

# udevinfo -a -p /sys/class/net/eth1

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/class/net/eth1':
    KERNEL=="eth1"
    SUBSYSTEM=="net"
    SYSFS{weight}=="64"
    SYSFS{tx_queue_len}=="1000"
    SYSFS{flags}=="0x1003"
    SYSFS{mtu}=="1500"
    SYSFS{operstate}=="down"
    SYSFS{dormant}=="0"
    SYSFS{carrier}=="0"
    SYSFS{broadcast}=="ff:ff:ff:ff:ff:ff"
    SYSFS{address}=="00:11:0a:aa:bb:cc"
    SYSFS{link_mode}=="0"
    SYSFS{type}=="1"
    SYSFS{features}=="0x500001a3"
    SYSFS{ifindex}=="3"
    SYSFS{iflink}=="3"
    SYSFS{addr_len}=="6"

  looking at parent device '/devices/pci0000:20/0000:20:02.0':
    ID=="0000:20:02.0"
    BUS=="pci"
    DRIVER=="tg3"
    SYSFS{broken_parity_status}=="0"
    SYSFS{enable}=="1"
    SYSFS{modalias}=="pci:v000014E4d00001645sv0000103Csd000012A4bc02sc00i00"
    SYSFS{irq}=="58"
    SYSFS{class}=="0x020000"
    SYSFS{subsystem_device}=="0x12a4"
    SYSFS{subsystem_vendor}=="0x103c"
    SYSFS{device}=="0x1645"
    SYSFS{vendor}=="0x14e4"

  looking at parent device '/devices/pci0000:20':
    ID=="pci0000:20"
    BUS==""
    DRIVER==""

# udevinfo -a -p /sys/class/net/eth2

Udevinfo starts with the device specified by the devpath and then
walks up the chain of parent devices. It prints for every device
found, all possible attributes in the udev rules key format.
A rule to match, can be composed by the attributes of the device
and the attributes from one single parent device.

  looking at device '/class/net/eth2':
    KERNEL=="eth2"
    SUBSYSTEM=="net"
    SYSFS{weight}=="16"
    SYSFS{tx_queue_len}=="1000"
    SYSFS{flags}=="0x1002"
    SYSFS{mtu}=="1500"
    SYSFS{operstate}=="down"
    SYSFS{broadcast}=="ff:ff:ff:ff:ff:ff"
    SYSFS{address}=="00:11:0a:dd:ee:ff"
    SYSFS{link_mode}=="0"
    SYSFS{type}=="1"
    SYSFS{features}=="0x0"
    SYSFS{ifindex}=="2"
    SYSFS{iflink}=="2"
    SYSFS{addr_len}=="6"

  looking at parent device '/devices/pci0000:00/0000:00:03.0':
    ID=="0000:00:03.0"
    BUS=="pci"
    DRIVER=="e100"
    SYSFS{broken_parity_status}=="0"
    SYSFS{enable}=="1"
    SYSFS{modalias}=="pci:v00008086d00001229sv0000103Csd00001274bc02sc00i00"
    SYSFS{irq}=="59"
    SYSFS{class}=="0x020000"
    SYSFS{subsystem_device}=="0x1274"
    SYSFS{subsystem_vendor}=="0x103c"
    SYSFS{device}=="0x1229"
    SYSFS{vendor}=="0x8086"

  looking at parent device '/devices/pci0000:00':
    ID=="pci0000:00"
    BUS==""
    DRIVER==""

#

Responses

From your kernel ring buffer:

kernel: e100: Intel(R) PRO/100 Network Driver, 3.5.10-k3-1-NAPI
kernel: e100: eth0: e100_probe: addr 0x80020000, irq 59, MAC addr 00:11:0A:dd:ee:ff

kernel: tg3 0000:20:02.0: eth1: eth1: Tigon3 [partno(BCM95700A6) rev 0105 PHY(5701)] (PCI:66MHz:64-bit) 10/100/1000Base-T Ethernet 00:11:0a:aa:bb:cc

===
You need to make sure ifcfg-eth0 matches the Intel PRO/100 card and the HWADDR matches the address listed above.

Same thing with the Tigon3 chipset card. ifcfg-eth1 needs to match it, and the HWADDR needs to match it as well.

You have an (extra) ifcfg-eth2 file defined it looks like, and ifcfg-eth0 is referring to the wrong card.

You should have two files (ifcfg-eth0 and ifcfg-eth1), and they need to match what the kernel detects to bring the interfaces up.

Thank you for your reply to my request, Phil.

I have to review my logs better...  in addition to the kernel messages that you located, I found the following:

-----

kernel: e1000: 0000:80:01.0: e1000_probe: (PCI-X:133MHz:64-bit) 00:1b:21:xx:yy:zz
kernel: e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection

-----

It looks like a clash for the name, eth0.

I wanted the order of the network interfaces to be as outlined in my ifcfg-eth* scripts.  That is, I wanted eth0 to match the interface with HWADDR=00:1b:21:xx:yy:zz, eth1 to match HWADDR=00:11:0a:aa:bb:cc, and eth2 to match HWADDR=00:11:0a:dd:ee:ff.

However, it appears that udev gets things right:

 

# udevinfo -a -p /sys/class/net/eth0

  looking at device '/class/net/eth0':
    KERNEL=="eth0"

    [snip]

   SYSFS{address}=="00:1b:21:xx:yy:zz"

    [snip]

  looking at parent device '/devices/pci0000:80/0000:80:01.0':
    ID=="0000:80:01.0"
    BUS=="pci"
    DRIVER=="e1000"

    [snip]

 

# udevinfo -a -p /sys/class/net/eth1

  looking at device '/class/net/eth1':
    KERNEL=="eth1"

    [snip]

    SYSFS{address}=="00:11:0a:aa:bb:cc"

    [snip]

 looking at parent device '/devices/pci0000:20/0000:20:02.0':
    ID=="0000:20:02.0"
    BUS=="pci"
    DRIVER=="tg3"

    [snip]

 

# udevinfo -a -p /sys/class/net/eth2

  looking at device '/class/net/eth2':
    KERNEL=="eth2"

    [snip]

    SYSFS{address}=="00:11:0a:dd:ee:ff"

    [snip]

  looking at parent device '/devices/pci0000:00/0000:00:03.0':
    ID=="0000:00:03.0"
    BUS=="pci"
    DRIVER=="e100"

    [snip]

 

I have resorted to the drastic measure of reinstalling the system which has solved the problem.  This system is being configured as a spare for a currently running one.

 

Anyway, thank you again for replying.  Mod, please close this thread.

You bet. Also--just one more thing to note... if all three cards are using different drivers, you can adjust interface numbering order via /etc/modprobe.conf. An example would be:

alias eth0 e1000
alias eth1 tg3
alias eth2 e100

Warm regards,
Phil

Phil/Tony, great information!  Udev is certainly not something every admin deals with on a frequent basis.

 

I have a few questions regarding the 2 posts.

Can modify which cards end up being at the different numeric ethX (i.e. you could use the udev declaration to make the tg3 card eth3, if you wanted)?

 

If you were to modify your UDEV files as you had suggested, would you bother with the /etc/modprobe.conf (as the udev file, itself, identifies the driver).

 

I could offer the following example for those that are wondering why you would need to bother with this:

Using UDEV is helpful if you are trying to establish standards (physical and logical).  I.e. your datacenter standard states that ALL systems use the port physically labeled NET0 as the primary interface, and NET3 is ALWAYS your backup network interface.  And in the OS configuration those ports need to equate to ETH0 and ETH1 - depending on the server platform and the hardware installed, the interfaces might be numerically different as reported to the OS.  (i.e. if you installed a Quad-Ethernet card in a PCI slot because this host is a cluster).  This seems to be even more prevelant in systems that offer 2 different on-board chipsets for the 4 ports (i.e. 2 are Intel and 2 are broadcom).

Another scenario is if you had everything configured and plumbed and you had to add additional network capactiy later. UDEV can ensure that the ETHX identifier stays consistent.

 

James,

to specify which interface should be eth0, and which eth1 etc or whatever you want to call them,  use DEVICE and HWADDR in your  /etc/sysconfig/network-scripts/ifcfg-XXXX  files.

For example, you can set:

DEVICE=james
HWADDR=D8:C3:84:AB:A8:32
 
You can set DEVICE to be whatever you want. It does not have to be ethN. It can be any name ( james as in the example above). 
In the ifconfig output you will see james :-)
 
This configuration file will only apply to the device that has hardware address matching HWADDR you specify.

I tried another clean install of RHEL 5.6 Server (Itanium), and incrementally applied errata updates.  The RTNETLINK error messages started after installing RHBA-2011:1081.

Tony,

 

 

/etc/udev/rules.d/70-persistent-net.rules might have been your "enemy".

 

I had this during cloning of a VMware ESX template.

After deleting this file I go eth0, eth1, and eth2.

Before removing the file udev create eth3, eth4 and eth5 very annoying if the routing files are named: route-eth1 and route-eth0 and the config files ifcfg-eth0, ifcfg-eth1 and ifcfg-eth2.

 

After the removal of /etc/udev/rules.d/70-persistent-net.rules and a reboot the NIC devices where named eth0, eth1 and eth2 and /etc/udev/rules.d/70-persistent-net.rules contained the correct rules to make the device files persistent.

 

 

Kind regards,

 

 

Ir. Jan Gerrit Kootstra

Hey Jan,

An item you might be running into...

when you create the first "golden image" Virtual Machine the ifcfg-eth0 contains the HWADDR and UUID

when you clone, VMware will create a new machine with a new mac address which is different than the mac in the ifcfg-eth0 file (in addition to the udev file that you had mentioned.)

 

My approach is to update the existing files with the new mac addresses (which can be quite time consuming if you have to frequently execute this task).

 

The only reason I am mentioning this, is I wonder what the impact of removing 70-persistent-net.rules might be, what may rewrite that file later.  Also, whether future updates might modify that file.  Hopefully we have some UDEV gurus that can shed some light.

 

Take care

Hey James,

 

 

/lib/udev/write_net_rules creates  70-persistent-net.rules, see comment on top of the file content

I have update the "golden image" removing the current 70-persistent-net.rules and the HWADDR and UUID lines.

 

Still I thank you for the reminder, for it might not be clear to the readers of this discussion.

 

Once the 70-persistent-net.rules has been rewritten, I also added the HWADDR lines to the ifcfg-ethx files for safety of "udev" updates over writting the udev rules.

 

 

Take care,

 

 

Jan Gerrit

Hi Jan,

On my host RHEL 5.6 write_net_rules in /lib/udev does not exists not udevadm is present even updating later udev package to get the 70-persistent-net.rules. Please let me know if any other alternate to generate it, renaming interface names manually from /etc/sysconfig/network-scripts are cumbersome.

 

Mahesh

Mahesh,

 

Sorry I missed the RHEL 5.6 reference.

This may take some more time for me to check this out.

I have done this a few years back for a disaster recovery situation.

It may take a week for me to come back on this.

 

Kind regards,

 

Jan Gerrit Kootstra

Tony,

 

@Mahesh: this examples is based on a RHEL 5.7 on x86_64.

This is what I have done for a disaster recovery setting, where we use SAN boot.

First I defined the rules for the normal production site and secondly I define the rules for the disaster recovery site.

You can use this for your IA64 box by only defining a set of rules for your "local" machine based on the mac-addresses of the host nic's.

##normal location
KERNEL=="eth*", SYSFS{address}=="AA:AA:AA:AA:AA:A0", NAME="eth0"
KERNEL=="eth*", SYSFS{address}=="AA:AA:AA:AA:AA:A1", NAME="eth1"
KERNEL=="eth*", SYSFS{address}=="AA:AA:AA:AA:AA:A2", NAME="eth2"
KERNEL=="eth*", SYSFS{address}=="AA:AA:AA:AA:AA:A3", NAME="eth3"
KERNEL=="eth*", SYSFS{address}=="AA:AA:AA:AA:AA:A4", NAME="eth4"
KERNEL=="eth*", SYSFS{address}=="AA:AA:AA:AA:AA:A5", NAME="eth5"
#
##disaster recovery location
#
KERNEL=="eth*", SYSFS{address}=="BA:AA:AA:AA:AA:A0", NAME="eth0"
KERNEL=="eth*", SYSFS{address}=="BA:AA:AA:AA:AA:A1", NAME="eth1"
KERNEL=="eth*", SYSFS{address}=="BA:AA:AA:AA:AA:A2", NAME="eth2"
KERNEL=="eth*", SYSFS{address}=="BA:AA:AA:AA:AA:A3", NAME="eth3"
KERNEL=="eth*", SYSFS{address}=="BA:AA:AA:AA:AA:A4", NAME="eth4"
KERNEL=="eth*", SYSFS{address}=="BA:AA:AA:AA:AA:A5", NAME="eth5"

 

 

Kind regards,

 

 

Jan Gerrit Kootstra