HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
cancel
Showing results for 
Search instead for 
Did you mean: 

Dicussion on RedHat and Virtual Connect issue?

 
chuckk281
Trusted Contributor

Dicussion on RedHat and Virtual Connect issue?

Charles asked a Linux driver question:

 

******************

 

Anyone know about a possible Link up/down issue with redhat?

 

It appears that Redhat 5.6 and below do not correctly detect link state changes on HP VirtualConnect.

The customer is hearing rumors that speak to some change that HP made and a fix available in Redhat 5.7.

 

This issue has a severe impact on their ability to upgrade VirtualConnect with Linux running on it.  They would be interested in knowing what if anything can be done to resolve this prior to upgrading to Redhat 5.7.

 

****************

 

The conversation:

 

*******************

From Alan:

We sure apply HP NIC driver instead of Redhat bundle driver. The HP driver support both Redhat 5.6 and 5.7, so if there is problem, it will not affect 5.6 only.

 

Reply from Charles:

Doesn’t the HP NIC driver change the kernel though?  if so, then there’s the issue about RedHat support with a “tainted” kernel. Most of my customers hesitate to use our NIC drivers because of this (or at least that’s what they tell me).

does that issue still exist, or do our NIC drivers no longer change the kernel?

 

From Chris:

No.  Why would you think that?  Our drivers have been compiled against specific versions of the kernel, which may require the customer to use a supported stream, and not some custom kernel they got from kernel.org.

 

*****************

 

Any other input or questions?