it is stated that these are servers for 5.1 or 6.0 Cisco Unified Communications Manager Application.
My problem is that my sales team sold a MCS 7825-I3, 1000 User CM4.2-K9-7825-I3 software package which seems to be compatible with the aforementioned servers. Considering this SW, I tried to do the installation with the installation DVDs included in the package. Nothing worked. With Disk 1 (78XX-I1/I2) the hardware detection clearly states that the hardware is not compatible. With Disk 2 (7825-I3, 7845-I1/I2) it begins the installation and then gets to a point where I get a notification that it is "gathering information" and ejects the DVD. Nothing else happens after that point.
Am I looking at this problem with the wrong approach?
The most simple thing that you can do is contact the Cisco Reseller/AM/SE from whom you bought the server and check if they have a copy of this version of CD. Incase try dont have a copy handy then you would have to order for the CDs using PUT (http://tools.cisco.com/gct/Upgrade/jsp/index.jsp).
For more info on ordering CDs, please refer AVVID CD FAQ:
that's part of my problem. The shipped OS is a 2000.4.5. So, theoretically, I should have no problems installing it. As these installations are pretty straight forward in this preliminary phase of hardware detection I come up with two situations:
either it is detected as a conforming platform or it is not. Unfortunately for me I'm getting the later.
Ok, the culprit is CSCsk00441. As mentioned earlier in the thread the issue is with the BIOS version. Please open a TAC case and quote this Bug ID. The TAC Engineer should be able to give you the BIOS upgrade needed as a workaround.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.