Windows 2008 R2 on HP DL380 G4p
If you are reading this article, it means that we still do not have the “Antique iron” hub.
The old HP iron has only one drawback: it works, it works and everything can not break. But in HP, too, not fools are sitting and doing everything to stimulate the server economy update - the drivers for the new OS are not being developed, the completion of the firmware has ceased, so you have to drive yourself to the paradise and willy-nilly, but you have to update.
But we also have our own interest. To use old equipment, on the tasks that he can afford, is our first duty, especially since there are free licenses for Windows 2008 R2. Let's try to pull an owl called Windows 2008 R2 on our old DL360 G4p globe (P54).
In the lists of supported systems on the server page DL360G4, OS Windows 2008 R2 is no longer listed.
')
If we look in the support matrix,
h17007.www1.hp.com/us/en/enterprise/servers/supportmatrix/windows.aspx#.Vufcl-KLTcs
then officially W2K8 R2 is supported only for generations G7 and fresher. There is no talk about G4.
And yet, if you go to the BIOS page for G4p, you will see the following:
Those. A BIOS for G4p (P54) (sp30408.exe) that supports the W2K8 installation exists, but is “locked up” and is available only if you have a maintenance contract.
Before starting work should:
1. Go through the server with the latest available Firmware CD for this model or slip it into the dark HP Smart Update Manager and lift the last eyelid.
2. Purchase a system maintenance contract and legally obtain the latest BIOS version for G4p, download and install BIOS 2007.07.16A.
3. Upgrade iLO2 to version 1.92.
If your server is equipped with an FDD drive, then before inserting floppy disks into it, the drive must be removed and blown with compressed air from dust. The design of the server is such that a large volume of air is pumped through a disk drive and a CD drive by fans and all the dust accumulates inside the devices. If the drives are used extremely rarely, then the dust deposits work like a good sandpaper.
It is better to deploy updates on a USB flash drive, but when using HP standard tools, a flash drive is required that is NOT MORE THAN 2GB in size!
The installation of the W2K8 was done by my colleague, and, according to him, there were no problems there.
But with the union of adapters in the team (team) had to tinker a bit. The server is equipped with two built-in network adapters NC7782, assembled on a Broadcom BCM5704CFKB chip, which are interesting to unite in a team.
Traditionally, the team is going with the help of HP NCU - Network Configuration Utility. NCU is a separate product, and its version under W2k8 is available on the HP website and is available for download without restrictions.
The Version 10.50.0.0 utility on the server got up, but did not see a single network adapter NC7782. The latest version 10.90.0.0 and at all issued here is an interesting message:
What should be understood as “the software has been installed somehow, but how-it is not clear and doing this is definitely not worth it.”
And what about our drivers? And we got drivers for network cards when installing W2K8. It has been suggested that NCUs require drivers from HP.
And where to get the drivers, taking into account that formally they are no longer doing them for 2008 R2 for G4p? “Yes, here they are!Put "it doesn't matter that they are under Windows 2003 x64.
cp006193.exe
Of course, according to the traditional scheme, they will not rise. cp006193.EXE, when launched, reports that “the grenades are not of the same system,” and they cannot work here because they do not want.
But manually set. cp006193.EXE is a self-extracting archive that is normally deployed using Winrar. We decompose it into a separate directory and then "System / Device Manager / Network cards / Driver / Update ... / Install manually / show on the directory. The driver changes on the fly, even the terminal session is not interrupted. "2003 x64 on 2008 R2"
But this did not help, the NCU did not see its own drivers. Perhaps an understatement of the NCU version would help, but it was decided to try another solution.
Other server manufacturers, such as Dell and Fujitsu, use software developed by Broadcom under the name BACS (Broadcom Advanced Control Suite) for teaming. Version 4 is currently available.
HP has one too. cp022114.exe
But HP sees its use somewhat differently - the organization of iSCSI and FCOE targets on the platforms we require. BACS for HP on G4 refused to start, “No,” he says — you have the right hardware for me. ” Yes, and not really wanted.
Where BACS4 is downloaded from the Broadcom website I never found, a link to management applications leads to page 404. Broadcom writes that the package comes on a CD along with the network cards of the vendors. The entire package is posted on the Fujitsu website:
support.ts.fujitsu.com/Download/ShowDescription.asp?SoftwareGUID=31239D24-69B5-43EB-9C50-C3AA36F1AE80&Info=FTS
Or you can search the Internet for the file FTS_BroadcomAdvancedControlSuite4BACS_14831_1064191.zip.
2011, but it works.
Getting started installing BACS4.
- BACS4 does not deal with such nonsense. He doesn’t care: “Fujitsu is not Fujitsu”
Then everything is just “Commands / Create”. Call Team1. Add both available adapters. (Physically, at the time of assembling the tim, to avoid problems, only one cable is connected to the network. After assembling the tim, connect the second cable and everything works as usual)
If he doesn't like the drivers, BACS4 will tell about it. On HP drivers, he cursed and said: “I want NDIS6, NDIS5 - I do not want!”
On the Broadcom website, we took the latest drivers for BCM5704 (Version 17.2.0.2 of July 03, 2015) and installed them on G4.
This is what the BACS4 interface looks like.
The server is connected to the HP Procurve 2910, so when you install, you must specify 802.3 ad, another protocol of the ports Procurve is not understood (from the switch on the ports assembled LACP).
Everything Works, the flight is normal.
About NIC teaming, White paper from HP. Useful reading.
www.hp.com/sbso/bus_protect/teaming.pdf
The old HP iron has only one drawback: it works, it works and everything can not break. But in HP, too, not fools are sitting and doing everything to stimulate the server economy update - the drivers for the new OS are not being developed, the completion of the firmware has ceased, so you have to drive yourself to the paradise and willy-nilly, but you have to update.
But we also have our own interest. To use old equipment, on the tasks that he can afford, is our first duty, especially since there are free licenses for Windows 2008 R2. Let's try to pull an owl called Windows 2008 R2 on our old DL360 G4p globe (P54).
Koloboks are investigating
In the lists of supported systems on the server page DL360G4, OS Windows 2008 R2 is no longer listed.
')
If we look in the support matrix,
h17007.www1.hp.com/us/en/enterprise/servers/supportmatrix/windows.aspx#.Vufcl-KLTcs
then officially W2K8 R2 is supported only for generations G7 and fresher. There is no talk about G4.
And yet, if you go to the BIOS page for G4p, you will see the following:
Those. A BIOS for G4p (P54) (sp30408.exe) that supports the W2K8 installation exists, but is “locked up” and is available only if you have a maintenance contract.
Before starting work should:
1. Go through the server with the latest available Firmware CD for this model or slip it into the dark HP Smart Update Manager and lift the last eyelid.
2. Purchase a system maintenance contract and legally obtain the latest BIOS version for G4p, download and install BIOS 2007.07.16A.
3. Upgrade iLO2 to version 1.92.
Mysterious artifacts and special ancient magic
If your server is equipped with an FDD drive, then before inserting floppy disks into it, the drive must be removed and blown with compressed air from dust. The design of the server is such that a large volume of air is pumped through a disk drive and a CD drive by fans and all the dust accumulates inside the devices. If the drives are used extremely rarely, then the dust deposits work like a good sandpaper.
It is better to deploy updates on a USB flash drive, but when using HP standard tools, a flash drive is required that is NOT MORE THAN 2GB in size!
The installation of the W2K8 was done by my colleague, and, according to him, there were no problems there.
Crossing the grass with the hedgehog or the horse of Tuguez
But with the union of adapters in the team (team) had to tinker a bit. The server is equipped with two built-in network adapters NC7782, assembled on a Broadcom BCM5704CFKB chip, which are interesting to unite in a team.
Traditionally, the team is going with the help of HP NCU - Network Configuration Utility. NCU is a separate product, and its version under W2k8 is available on the HP website and is available for download without restrictions.
The Version 10.50.0.0 utility on the server got up, but did not see a single network adapter NC7782. The latest version 10.90.0.0 and at all issued here is an interesting message:
What should be understood as “the software has been installed somehow, but how-it is not clear and doing this is definitely not worth it.”
And what about our drivers? And we got drivers for network cards when installing W2K8. It has been suggested that NCUs require drivers from HP.
And where to get the drivers, taking into account that formally they are no longer doing them for 2008 R2 for G4p? “Yes, here they are!
cp006193.exe
Of course, according to the traditional scheme, they will not rise. cp006193.EXE, when launched, reports that “the grenades are not of the same system,” and they cannot work here because they do not want.
But manually set. cp006193.EXE is a self-extracting archive that is normally deployed using Winrar. We decompose it into a separate directory and then "System / Device Manager / Network cards / Driver / Update ... / Install manually / show on the directory. The driver changes on the fly, even the terminal session is not interrupted. "2003 x64 on 2008 R2"
But this did not help, the NCU did not see its own drivers. Perhaps an understatement of the NCU version would help, but it was decided to try another solution.
And what about u ....?
Other server manufacturers, such as Dell and Fujitsu, use software developed by Broadcom under the name BACS (Broadcom Advanced Control Suite) for teaming. Version 4 is currently available.
HP has one too. cp022114.exe
But HP sees its use somewhat differently - the organization of iSCSI and FCOE targets on the platforms we require. BACS for HP on G4 refused to start, “No,” he says — you have the right hardware for me. ” Yes, and not really wanted.
Where BACS4 is downloaded from the Broadcom website I never found, a link to management applications leads to page 404. Broadcom writes that the package comes on a CD along with the network cards of the vendors. The entire package is posted on the Fujitsu website:
support.ts.fujitsu.com/Download/ShowDescription.asp?SoftwareGUID=31239D24-69B5-43EB-9C50-C3AA36F1AE80&Info=FTS
Or you can search the Internet for the file FTS_BroadcomAdvancedControlSuite4BACS_14831_1064191.zip.
2011, but it works.
Getting started installing BACS4.
“HP is not HP, the Subscriber is not a subscriber”
- BACS4 does not deal with such nonsense. He doesn’t care: “Fujitsu is not Fujitsu”
Then everything is just “Commands / Create”. Call Team1. Add both available adapters. (Physically, at the time of assembling the tim, to avoid problems, only one cable is connected to the network. After assembling the tim, connect the second cable and everything works as usual)
If he doesn't like the drivers, BACS4 will tell about it. On HP drivers, he cursed and said: “I want NDIS6, NDIS5 - I do not want!”
On the Broadcom website, we took the latest drivers for BCM5704 (Version 17.2.0.2 of July 03, 2015) and installed them on G4.
This is what the BACS4 interface looks like.
The server is connected to the HP Procurve 2910, so when you install, you must specify 802.3 ad, another protocol of the ports Procurve is not understood (from the switch on the ports assembled LACP).
Everything Works, the flight is normal.
About NIC teaming, White paper from HP. Useful reading.
www.hp.com/sbso/bus_protect/teaming.pdf
Source: https://habr.com/ru/post/279395/
All Articles