05-31-2007 06:15 AM - edited 03-14-2019 09:48 PM
I have a publisher and subscriber which were both installed with original 4.2.1 media, and then upgraded to 4.2.3 with the maintenance release. I need to rebuild the subscriber, but when I try to run the 4.2.1 install, it fails because the pub is 4.2.3. Is there a way around this, or what are my options?
05-31-2007 07:03 AM
Hi Pete,
I think the 2 options are;
1. Build the Sub as 4.2.3 (new media)and add SR
2. Take the Sub off-line, build 4.2.1 upgrade to 4.2.3 with exact SR (re-sync the db)
I can't think of any other way.
Hope this helps!
Rob
05-31-2007 07:25 AM
what do you mean "take the sub off line", do you mean off the network. During install, the sub tries to contact the pub, and thats where the fun starts.
05-31-2007 08:30 AM
The only option here is to get CM 4.2(3) Media and install the subscriber with that. You cannot build CM 4.2(1) Subscriber as you have mentioned. When Subscriber is being installed, it tries to contact the publisher and this process checks for CM version on the Publisher and if the Subscriber cannot reach the publisher it would fail. To get CM 4.2(3) Media, please refer http://www.cisco.com/en/US/customer/products/sw/voicesw/ps556/products_qanda_item09186a00802262ed.shtml
The Part you would order would be general to CM 4.2 and Cisco always ships the latest version of CallManager in the current release. And since CM 4.2(3) is the latest and greatest in CM 4.2 train, you would get CM 4.2(3)
05-31-2007 08:32 AM
Hi Pete,
I think Mahesh is right here (no surprise :)
I'm going back through my cloudy memory to work that we have done in the Lab with boxes off-line, but these were upgrades not total re-builds. Sorry for the wrong turn!
Option # 1 is the only way to go
Hope this helps!
Rob
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide