- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Fedore Core 5 on DL360 G5 - problem with logic...
Operating System - Linux
1759693
Members
3354
Online
108886
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-30-2007 04:34 AM
тАО05-30-2007 04:34 AM
Fedore Core 5 on DL360 G5 - problem with logical network interfaces
I have the above system setup and the MAC addresses of network interfaces do not appear to be attached orderly to the interface eth0-3. Could anyone offer me some suggestions? See the following screenshot:
[root@system1 ~]# ip link show
1: lo: mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: mtu 1500 qdisc noop qlen 1000
link/ether 00:17:08:7e:d4:46 brd ff:ff:ff:ff:ff:ff
3: eth3: mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:17:08:7e:d4:47 brd ff:ff:ff:ff:ff:ff
4: eth2: mtu 1500 qdisc noop qlen 1000
link/ether 00:1b:78:03:9d:f2 brd ff:ff:ff:ff:ff:ff
5: dev1370: mtu 1500 qdisc noop qlen 1000
link/ether 00:1b:78:03:9d:ea brd ff:ff:ff:ff:ff:ff
6: sit0: mtu 1480 qdisc noop
link/sit 0.0.0.0 brd 0.0.0.0
[root@system1 ~]# cat /etc/modprobe.conf
alias eth0 bnx2
alias eth1 bnx2
alias eth2 e1000
alias eth3 e1000
alias scsi_hostadapter cciss
By the way, HWADDR of ifcfg-eth* file appeared to have the the right order of MAC addresses.
[root@system1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth*
# Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=00:1B:78:03:9D:F2
ONBOOT=no
# Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet
DEVICE=eth1
BOOTPROTO=dhcp
HWADDR=00:1B:78:03:9D:EA
ONBOOT=no
# Intel Corporation 82571EB Gigabit Ethernet Controller
DEVICE=eth2
BOOTPROTO=dhcp
HWADDR=00:17:08:7E:D4:46
ONBOOT=no
# Intel Corporation 82571EB Gigabit Ethernet Controller
DEVICE=eth3
BOOTPROTO=static
HWADDR=00:17:08:7E:D4:47
ONBOOT=yes
IPADDR=192.168.130.22
MASK=255.255.255.192
GATEWAY=192.168.130.62
TYPE=Ethernet
[root@system1 ~]# ip link show
1: lo:
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0:
link/ether 00:17:08:7e:d4:46 brd ff:ff:ff:ff:ff:ff
3: eth3:
link/ether 00:17:08:7e:d4:47 brd ff:ff:ff:ff:ff:ff
4: eth2:
link/ether 00:1b:78:03:9d:f2 brd ff:ff:ff:ff:ff:ff
5: dev1370:
link/ether 00:1b:78:03:9d:ea brd ff:ff:ff:ff:ff:ff
6: sit0:
link/sit 0.0.0.0 brd 0.0.0.0
[root@system1 ~]# cat /etc/modprobe.conf
alias eth0 bnx2
alias eth1 bnx2
alias eth2 e1000
alias eth3 e1000
alias scsi_hostadapter cciss
By the way, HWADDR of ifcfg-eth* file appeared to have the the right order of MAC addresses.
[root@system1 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eth*
# Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet
DEVICE=eth0
BOOTPROTO=dhcp
HWADDR=00:1B:78:03:9D:F2
ONBOOT=no
# Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet
DEVICE=eth1
BOOTPROTO=dhcp
HWADDR=00:1B:78:03:9D:EA
ONBOOT=no
# Intel Corporation 82571EB Gigabit Ethernet Controller
DEVICE=eth2
BOOTPROTO=dhcp
HWADDR=00:17:08:7E:D4:46
ONBOOT=no
# Intel Corporation 82571EB Gigabit Ethernet Controller
DEVICE=eth3
BOOTPROTO=static
HWADDR=00:17:08:7E:D4:47
ONBOOT=yes
IPADDR=192.168.130.22
MASK=255.255.255.192
GATEWAY=192.168.130.62
TYPE=Ethernet
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-30-2007 05:11 AM
тАО05-30-2007 05:11 AM
Re: Fedore Core 5 on DL360 G5 - problem with logical network interfaces
Interesting, what is the output of ifconfig -a?
I think that one problem could be that the ONBOOT is set to NO on most interfaces, I would like to know if the device set ONBOOT=yes (eth3) is assigned the IP requiested.
I think that one problem could be that the ONBOOT is set to NO on most interfaces, I would like to know if the device set ONBOOT=yes (eth3) is assigned the IP requiested.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2007 09:30 PM
тАО06-01-2007 09:30 PM
Re: Fedore Core 5 on DL360 G5 - problem with logical network interfaces
You might also want to check to see if your interface names are being changed under udev (couldn't verify for sure - not running FC5 on any of my systems anymore).
Take a look under /etc/udev/rules.d for something similiar to the following (taken from a SuSE system, but this ability does also exist under RHEL4).
# This rules are autogenerated from /lib/udev/rename_netiface.
# But you can modify them, but make sure that you don't use an interface name
# twice. Also add such interface name rules only in this rules file. Otherwise
# rename_netiface will create wrong rules for new interfaces.
# It is safe to delete a rule, as long as you did not disable automatic rule
# generation. Only if all interfaces get a rule the renaming will work
# flawlessly. See also /etc/udev/rules.d/31-net_create_names.rules.
#
# Read /usr/share/doc/packages/sysconfig/README.Persistent_Interface_Names for
# further information.
#
# Use only a-z, A-Z and 0-9 for interface names!
#
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:14:c2:62:44:89", IMPORT="/lib/udev/rename_netiface %k eth0"
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:14:c2:62:44:88", IMPORT="/lib/udev/rename_netiface %k eth1"
Col
Take a look under /etc/udev/rules.d for something similiar to the following (taken from a SuSE system, but this ability does also exist under RHEL4).
# This rules are autogenerated from /lib/udev/rename_netiface.
# But you can modify them, but make sure that you don't use an interface name
# twice. Also add such interface name rules only in this rules file. Otherwise
# rename_netiface will create wrong rules for new interfaces.
# It is safe to delete a rule, as long as you did not disable automatic rule
# generation. Only if all interfaces get a rule the renaming will work
# flawlessly. See also /etc/udev/rules.d/31-net_create_names.rules.
#
# Read /usr/share/doc/packages/sysconfig/README.Persistent_Interface_Names for
# further information.
#
# Use only a-z, A-Z and 0-9 for interface names!
#
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:14:c2:62:44:89", IMPORT="/lib/udev/rename_netiface %k eth0"
SUBSYSTEM=="net", ACTION=="add", SYSFS{address}=="00:14:c2:62:44:88", IMPORT="/lib/udev/rename_netiface %k eth1"
Col
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2007 10:26 PM
тАО06-01-2007 10:26 PM
Re: Fedore Core 5 on DL360 G5 - problem with logical network interfaces
Possible stupid question (but your output doesn't show this)
IS the ifcfg-eth3 file the one that contains the line "DEVICE=eth3"??
The name of the file has to match the DEVICE enumeration if that's the order you expect to see them enumerated.
It looks that way based on your use of "cat", but it's worth asking....
You can name the file "ifcfg-bob" if you want, what matters is the DEVICE and HWADDR lines.
FC5 is a little old for a G5 - have you at least updated it (kernel mainly) via the working connection?
IS the ifcfg-eth3 file the one that contains the line "DEVICE=eth3"??
The name of the file has to match the DEVICE enumeration if that's the order you expect to see them enumerated.
It looks that way based on your use of "cat", but it's worth asking....
You can name the file "ifcfg-bob" if you want, what matters is the DEVICE and HWADDR lines.
FC5 is a little old for a G5 - have you at least updated it (kernel mainly) via the working connection?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP