We have four DL380 G6 servers and we need to know if we can install and implement Cisco contact center and call manager media server and QA on these servers without problem. Is there any compatability issue ? Becuase Cisco/HP matrix says that the equavilant HP model is DL380 G5 which is discontinued. I need immediate help and advice please.
The short answer - no to UCCX and CUCM.
Maybe OK with QA - if I knew what it was.
All the Linux based applications (CUCM, UCCX, Unity CX) may barf at the processor - they want to see the 5140 (2.33GHz) processor. But if you have a G6 quad-core with the right speed processor it may install.
Actually, not having tried the install on the G6, they may barf before that checking the BIOS.
It's overly restrictive, in my opinion. For example, it checks that the speed of the processor is 2.33GHz and will not allow a faster machine.
I thought you could still order the special bundled HP DL380G5 - 470064-887 and 470064-880.
Anyway, you are screwed with those machines so use them for something else. Even if the install worked, it's not supported.
I have a customer that has aquired HP direct servers with the issue you speak of with the CPU speed not being 2.33. The CPU's show as 2.83GHz in the BIOS Post. Can the customer down grade via a cpu purchase and still use the hardware as the rest of the unit ships from HP? My concern is Voltage of the CPU for example.
I also agree with your point of view. The requirment to use only this CPU is another way to force Cisco clients to the Cisco version of the HP hardware.
Anyone have any data if this issue holds true for Version 7.1X of CCM?
Nothing has, or will, change for the platform support on bare-metal install deployments. You must have a Cisco MCS server or HP/IBM equivalent hardware to be supported. http://cisco.com/go/swonly is the link for the HP/IBM part numbers and ordering information.
When VMware support is added (varies by product; talk to you Cisco AM for details) this restriction will *start* to loosen. Don't expect this to be like your typical Windows file server VM, it will have specific requirements similar to what we have seen on Unity 7. (http://www.cisco.com/en/US/docs/voice_ip_comm/unity/virtualization_design/guide/cuvirtualdg010.html)
As a side note: I think it's unfair to chide the BUs for making stringent hardware requirements. Their reputation and product success depends on consistent performance from install to install. We all squawk for things like sizing tools (E.G. http://www.cisco.com/cgi-bin/CT/PGWCT/ct.cgi) but that's not possible if the hardware is an open field. Also, they go through extensive testing when choosing hardware. It is entirely possible they choose that CPU for specific JSPEC performance or other reasons.
Allowing a customer to go off and use whatever they have laying around greatly increases the chances of difficult to resolve TAC cases or worse, bad publicity and shoddy performance stemming from an obstinate customer.
The situation changed with respect to the G6 on October 13.
CUCM O/S now supported on the HP DL380-G6 Single Intel Xeon Nehalem quad-core E5504, 2.0 GHz and the HP DL380-G6 Single Intel Xeon Nehalem quad-core E5540, 2.53 GHz.
Has anyone been able to get the instal to run on a new HP DL380 G6. I am getting an error during the UCM install. I am attempting to install 7.1.3 and I get a "Could not configure the default Cache Settings" error during the install. I get the same error installing Unity Connection on a DL380 G6. And yes both boxes are the correct processor and HD/Memory configuration.
I tried the installation with 7.13b today and 7.13a last December. The installation aborted with an "unsupported hardware" message.
I used two servers, one AX692A and one AX691A for Unity Connection and Communications Manager.
TAC advised me to use the initial 7.13 version, because this should work.
I'm sceptical about that. My understanding is that if 7.13 works 7.13-something should work also.
Did anyone else try it? And which version did you use?
Thanks for providing the updated information. And I'm sorry to hear that it failed. Will you be opening a TAC case on this? Can you keep us in the loop please?
Did you have any reply from the TAC. Have got the same error "could not configure cache..." problem during the setup of the raid in the installation.
Like you guys have also have DL 380 G6 with the good CPU, HD, Memory.
Routine for this sort of thing is as follows:
1) Take a look at this page to find out which platforms support the version of CCM you intend to get (or the other way around):
2) If buying HP or IBM direct, take a look at this page to see the detail of the spec required. Not just table 1, but the tables further down that describe the individual required components.
3) If you are certain you have the correct/exact components, and suitable software based on the above info, then raise a TAC case.
Please rate helpful posts...
The issue is due to the fact that there was no memory on the raid controller, it seems HP comes default with out it.
If you look at the following link it gives you all of the individual part numbers youy need to order the complete server.
Table 1. Components of HP Part Number AX690A
|HP DL380G6 CTO Chassis|
|2.00Ghz Nehalem E5504 Processor FIO|
|HP 2GB 2Rx8 PC3-10600R-9 Kit|
|HP 146GB 10K 6G 2.5 SAS DP HDD|
|HP 1200W CS HE Power Supply Kit|
|HP Slim SATA DVD-ROM Optical Drive|
|HP 256 MB P-series cache module FIO|
|HP 650 mAh P-Series Battery|
|HP iLO Adv 1-Svr incl 1yr TS&U SW|
|HP Trusted Platform Module Option Kit|