Tim is not sugggesting it is rubbish, nor that it wouldn't work or a good idea.
By installing drivers directly from Compaq or IBM, you are running a configuration that is not SUPPORTED by Cisco.
If you contact TAC with a CallManager issue and they discover you are running any unsupported software or drivers on any of the servers they may ask you to remove them before they continue to offer support.
Please keep this in mind before installing anything that has not be approved for use on a CallManager server by Cisco.
I didn't mean to start a big flame war here. I was just pointing out that NIC teaming is not a supported configuration from Cisco for CCM, Unity and other related servers at this time.
If you configure your server hardware for CCM in a way that is not supported by Cisco, you may run into issues with TAC supporting your configuration.
NIC teaming does work quite well on Compaw servers, we have a few hundred servers that use Compaq NIC teaming. Since Cisco does not support NIC Teaming on servers that Call Manager is installed on, we are not using NIC Teaming on our CCM's. I would love to use NOC teaming on these servers as anotehr level or redundancy, however, since we rely on Cisco TAC for support of the CCM servers, we have to use a supported configuration.
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.