HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- eth link is not ready
Operating System - Linux
1837197
Members
2268
Online
110115
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
Forums
Discussions
Discussions
Discussions
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
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
08-10-2009 06:13 AM
08-10-2009 06:13 AM
eth link is not ready
Hi All,
I have two servers connected to each other with a cross cable. The connection was up and everything was Ok.
We had to change the NIC of one server, and after that the two servers are unable to connect again and we are getting the following in /var/log/messages:
Aug 10 12:31:49 system2 kernel: ADDRCONF(NETDEV_UP): eth2: link is not ready
eventhough that the cross cable is ok, but we are still unable to connect.
Can u please comment on this behavior if u face it before.
Thx in advance.
I have two servers connected to each other with a cross cable. The connection was up and everything was Ok.
We had to change the NIC of one server, and after that the two servers are unable to connect again and we are getting the following in /var/log/messages:
Aug 10 12:31:49 system2 kernel: ADDRCONF(NETDEV_UP): eth2: link is not ready
eventhough that the cross cable is ok, but we are still unable to connect.
Can u please comment on this behavior if u face it before.
Thx in advance.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-10-2009 06:48 AM
08-10-2009 06:48 AM
Re: eth link is not ready
I suggest you to always use a swiched connection (in a separate VLAN if neccesary).
You can try setting the speed and duplex mode with ethtool (if not GB ethernet) on both sides.
You can try setting the speed and duplex mode with ethtool (if not GB ethernet) on both sides.
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
08-10-2009 08:00 AM
08-10-2009 08:00 AM
Re: eth link is not ready
even if there is a problem with the negotiation still the "link detected" should be "yes". post the o/p of ethotool ethx
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-12-2009 11:53 PM
08-12-2009 11:53 PM
Re: eth link is not ready
which server you get the error log eth2: "link is not ready" ?
-you have to check kernel driver, may be need issue command to reclaim drivers :
#/dev/MAKEDEV
and also which flavor of Linux you use ?
-commands are different from version to version
and last thing to consider
- be sure of your ethernet card is good
-you have to check kernel driver, may be need issue command to reclaim drivers :
#/dev/MAKEDEV
and also which flavor of Linux you use ?
-commands are different from version to version
and last thing to consider
- be sure of your ethernet card is good
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP