I have been trying to get Cisco Emergency Responder (CER) version 7.0 installed since December 2008. I first made sure my 3rd party IBM X3250 M2 servers I wanted to order were compatible so I verified with TAC prior to order. TAC said they were on the list and ok.
Received CER and servers in December. Tried to load CER, wouldn't load with error about not being able to find driver for hardware. I opened another TAC case and was told they made a mistake and CER wasn't supported on that platform and I would have to order new servers.
Had our Cisco sale rep make sure we ordered the right MCS servers for CER. Waited 2 months to receive MCS servers which were model MCS 7825-I4-IPC1. Servers arrived and were identical to the previous IBM one we purchased other than the Cisco logo on the front.
Tried to load CER on MCS 7825-I4-IPC1, same error as before. Contacted Cisco, oops not supported server Cisco made another mistake and we must RMA the 7825-I4-IPC1's. They say the compatibility documentation is wrong.
Now Cisco is telling me the servers we need are the MCS-7825-I3-IPC1's. The problem is these are an inferior server model compared to the I4's and are now EOS/EOL and won't even be available after June for new orders.
Needless to say I am not happy about this at all and am wondering how Cisco can even sell CER 7.0 if it won't even run on any modern hardware (not even their own).
Has anyone else run into this same issue and what was your solution? Is there any other 7825 server that is not EOS/EOL that will actually run CER 7.0?
If it were me, I would either hold off until a CER Version is released that can be built on the new 7825 models or ask for a "no cost" trade up to the newer model when the two roads between CER and the MCS7825 meet.
Yep, I think every one of those servers listed above are EOL. The info I am now getting is that the non EOL servers will be supported in version 7.0(3) that will be out in the next few months. I'm trying to get a pre-release copy of 7.0(3) Good thought on the no cost trade up too.
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.