Hello, we have several sites that are running CME 3.2 with 12.3(11)T11 code with no problems. However, at one small site the 2811 router is also running IPSEC over two T1's and we've had to source the VPN tunnel from a loopback to get load-balancing going. Unfortunately it looks like the 12.3(11) code doesn't do a good enough job with CEF to keep the two circuits balanced. When a particular VPN is heavily active we see one of the circuits go way up on utilization while the other stays low. We had this problem at some other VPN sites and when the router was moved to 12.4(3d) code the CEF balancing started working much better. My problem with the CME router site is that I definitely don't want to do anything that forces us to go above CME 3.2. So my question is since I'm using the cme-basic-123-11T file with IOS c2800nm-advipservicesk9-mz.123-11.T11.bin, do those versions have to always match or can the router be bumped up to c2800nm-advipservicesk9-mz.124-xxxxx.bin code without affecting CME 3.2?
The versions do not have to match. You can run CME 3.2 on 12.4 code. Go to Feature Navigator and search by Feature. When you choose CME 3.2, you'll see that it is supported on 12.4 code. It looks like 12.4(3d) has been pulled from CCO, but 12.4(3e/f/g) are available.
1) CME is actually full embedded in IOS. The CME files are just the GUI, phone firmware, scripts perhaps, that depending on the situation you can do perfectly without. And if you know what you are doing, you can mix and match IOS and CME files sometime.
2) There is no need to be conservative about CME above 3.2. Eg 4.0, 4.1 are perfectly stable and usable, we have many installations already. So if there is something that makes you upgrade the IOS because of underlying problems, do that wihtout worries.
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.