- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Network issue - RHEL 5.4 on HP ProLiant BL 460c G...
Categories
Company
Local Language
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
Discussions
Forums
Discussions
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
Discussion Boards
Community
Resources
Forums
Blogs
- 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
12-15-2010 11:34 PM
12-15-2010 11:34 PM
Network issue - RHEL 5.4 on HP ProLiant BL 460c G6
ping any other machines from this machine in the network. I checked the iptables and it's status is OFF.
Do I need to install the network drivers or some other softwares after installing the O.S?
Is there any other configuration issue?
cat ifcfg-eth1
-------------
DEVICE=eth1
BOOTPROTO=none
HWADDR=d4:85:64:5c:88:28
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
IPV6INIT=yes
PEERDNS=no
IPADDR=16.16.224.42
NETMASK=255.255.240.0
GATEWAY=16.16.224.1
uname -r : 2.6.18-194.el5
There are 8 ports eth0 to eth7. I tried to configure the port one by one and tried to make it up by ifup ethX command.
It's giving some error if more than 1 port is up. So I used to down the first port before up the next port.
I have attached the dmesg| grep Broadcom command output also
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2010 02:03 AM
12-16-2010 02:03 AM
Re: Network issue - RHEL 5.4 on HP ProLiant BL 460c G6
#lspci | more ==> use this command to check if the drivers are loaded or not
#ethtool eth# ==> to check the settings for network interfaces
Provide the exact errors that you get when you try to bring other interfaces up.
Since you are providing static ip, you can set the bootproto to static in the configuration file.
Chhaya
I am an HP employee.
Was this post useful? - You may click the KUDOS! star to say thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2010 04:28 AM
12-16-2010 04:28 AM
Re: Network issue - RHEL 5.4 on HP ProLiant BL 460c G6
# ethtool eth1
------------
Settings For eth1:
Supported ports: [FIBRE]
Supported Link modes: 1000baseT/Full
2500baseX/Full
10000baseT/Full
Supports auto-negotiation: Yes
Advertised Link modes: 1000baseT/Full
2500baseX/Full
10000baseT/Full
Advertised auto-negotiation: Yes
Speed: 10000Mb/s
Duplex: Full
Port: FIBRE
PHYAD: 17
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: g
Current message level: 0x00000000 (0)
Link detected: yes
# lspci | more
---------------
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711E 10-Gigabit PCIe
02:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711E 10-Gigabit PCIe
02:00.2 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711E 10-Gigabit PCIe
02:00.3 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711E 10-Gigabit PCIe
02:00.4 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711E 10-Gigabit PCIe
02:00.5 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711E 10-Gigabit PCIe
02:00.6 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711E 10-Gigabit PCIe
02:00.7 Ethernet controller: Broadcom Corporation NetXtreme II BCM57711E 10-
Gigabit PCIe
I am getting the following error when I set ONBOOT =yes for more than one port
SIOCISFFLAGS : Input/Output Error
So I used to enable only one port at a time. I don't wnat to enable all the ports. I only need one port. SO I configured eth1 only.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2010 06:51 AM
12-16-2010 06:51 AM
Re: Network issue - RHEL 5.4 on HP ProLiant BL 460c G6
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2010 07:20 AM
12-16-2010 07:20 AM
Re: Network issue - RHEL 5.4 on HP ProLiant BL 460c G6
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-16-2010 07:41 AM
12-16-2010 07:41 AM
Re: Network issue - RHEL 5.4 on HP ProLiant BL 460c G6
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2010 01:23 PM
12-17-2010 01:23 PM
Re: Network issue - RHEL 5.4 on HP ProLiant BL 460c G6
If it is a FLEX-10 Virtual COnnect module, is a profile created for the server bay the 460 G6 is in? Are the correct networks assigned in the profile?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-04-2011 04:30 AM
01-04-2011 04:30 AM
Re: Network issue - RHEL 5.4 on HP ProLiant BL 460c G6
There are two profiles created in the Virtual connect module.
=============================================
Profile_server1:-
=============================================
Profile Name - Profile_SERVER1
Status - OK
Ethernet Network Connections
-----------------------------
Port 1
Network Name HP
Status OK
Port Speed setting Auto
Allocated Bandwidth 10 GB
PXE Use BIOS
MAC Server Factory Defaul
Mapping LOM:1-a => Bay 1
Port 2
Network Name HP
Status OK
Port Speed setting Auto
Allocated Bandwidth 10 GB
PXE Use BIOS
MAC Server Factory Defaul
Mapping LOM:2-a => Bay 1
Assign Profile to Server Bay
------------------------------
Power - On
Server Bay Assignment - OA-78E7D1E47D03: Bay 1 (ProLiant BL460c G6)
SN - GB80407CE0
Model - ProLiant BL460c G6
Status - OK
UID - UNLIT
=============================================
Profile_server2:-
=============================================
Profile Name - Profile_SERVER2
Status - OK
Ethernet Network Connections
-----------------------------
Port 1
Network Name HP
Status OK
Port Speed setting Auto
Allocated Bandwidth 10 GB
PXE Use BIOS
MAC Server Factory Defaul
Mapping LOM:1-a => Bay 1
Port 2
Network Name HP
Status OK
Port Speed setting Auto
Allocated Bandwidth 10 GB
PXE Use BIOS
MAC Server Factory Defaul
Mapping LOM:2-a => Bay 1
Assign Profile to Server Bay
---------------------------
Power - On
Server Bay Assignment - OA-78E7D1E47D03: Bay 2 (ProLiant BL460c G6)
SN - GB80407CE3
Model - ProLiant BL460c G6
Status - OK
UID - UNLIT
=============================================
Network
=============================================
Network Name - HP
Smart Link - Not selected
Private Network - Not selected
Enable VLAN Tunneling - Not selected
Status - OK
PID - UNLIT
State - Enabled
No External Up link ports are configured.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2011 09:23 PM
01-05-2011 09:23 PM
Re: Network issue - RHEL 5.4 on HP ProLiant BL 460c G6
Is the Broadcom NIC cards are compatible with the Flex10 module.
Regards,
Anoop Ahamad
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-13-2011 09:10 AM
01-13-2011 09:10 AM
Re: Network issue - RHEL 5.4 on HP ProLiant BL 460c G6
The SFP-RJ45 adapters were only supporting 1Gb network while the box was connected to a switch with only 10 and 100Mb speed.
We changed the room cabling to link the enclosure to a 1Gb port on another switch, and this is now working.
The only remaining issue is to get RedHat to connect to the network. For the time being, we are not successful, but I guess the install of the latest PSP pack should resolve the problem.