Re: Hp Proliant 460c drivers
On 10/22/2013 1:42 PM, Erick Ocrospoma wrote:
> On Oct 22, 2013 12:15 PM, "Stan Hoeppner" <stan@hardwarefreak.com> wrote:
>>
>> On 10/22/2013 10:11 AM, Erick Ocrospoma wrote:
>>> On Oct 22, 2013 8:36 AM, "Stan Hoeppner" <stan@hardwarefreak.com> wrote:
>>>>
>>>> On 10/21/2013 2:57 PM, Erick Ocrospoma wrote:
>>>>
>>>> Is this your first rodeo with HP servers?
>>>
>>> Blades yes
>>>
>>>>> I have installed Debian 7.1 on a few hp proliant blade servers, after
>>>>> installing I've seen that network is not working properly. It
> recognises
>>>>> around 8 interfaces, mii-tool says that there is not any link present.
>>
>> I'm pretty damn sure that blade doesn't have 8x 10GbE interfaces. It
>> should have one, or two if you purchased the dual port mezzazine board.
>>
>>>> Post your dmesg and lspci output WRT to the NIC hardware so we can
>>>> verify which Ethernet chip it is.
>>>>
>>>
>>> lspci | grep Eth
>>> ....
>>> Ethernet Controller: Emulex corporation One connect 10GB NIC (be3)
> (rev01)
>>
>> The kernel driver is "be2net". Is the driver loading? dmesg output
> please.
>>
>> Are you using static assignment or DHCP?
>>
>> What is the content of /etc/network/interfaces?
>>
>
> I have find the correct interfaces, from the group of 8 the two first ones
> are the NICs. There are only asigned only two virtual NICs per bay.
> I have just used the install cd1 so this must be a generic driver, anyway.
>
> Now, the problem is with the HBA fibber adapter, there's a SAN on the
> datacenter which Debian should recognise.
>
> Emulex brings official drivers for CentOS and due to this servers will be
> under high load, should I follow the official ones?
>
> We are testing under CentOS too, works fine but in both cases, Debian and
> CentOS, now we need to make work the fibber adapter.
Hardware drivers are part of the Linux kernel. They are not
distribution specific. You didn't post dmesg output so I don't know if
the Emulex FC HBA driver is loading or not. I'd guess it is.
The first thing you need to do is enter the HBA BIOS during POST and see
what LUNs are being unmasked to your HBA WWNs, if any. Read the HBA
manual to learn how to do this.
If the switches have not been programmed adding the WWNs of the FC HBAs
to an appropriate zone, and if the SAN array administrator has not
exposed LUNs to the HBA WWNs, you won't see any LUNs in the HBA BIOS,
nor any /dev/sdX devices that map to SAN LUNs. You literally won't
"see" anything on the SAN.
I can tell this is your first rodeo with FC SAN technology. There is
nothing "automatic" with FC SAN hardware. Zones, paths, security,
ports, etc, must typically all be manually configured on each piece of
the SAN, including the array controller, switches, and HBAs. Most
vendor introductory SAN courses are 3-5 days, and most offer 3 course
levels, beginner, intermediate, and advanced. If you've had no prior
SAN training or self study, you may be in for a rough ride, unless you
have a SAN admin, or someone on staff with knowledge. If so you will
need to work closely with that person to get this working.
FWIW, I taught myself enough in about 15 hours to integrate my first SAN
using Qlogic switches and HBAs, IBM and Nexsan disk arrays, using
strictly online vendor documentation, and Google. So it is possible to
fly by the seat of one's pants with one's first SAN deployment, but I am
not your average tech, and most people can't pull this type of thing off
working alone.
--
Stan
Reply to: