[cisco-voip] CM stable @ 6.1.2.1106?

[Erik Goppel]

We came from ccm 3.3(5) and did a complete rebuild, of the system by
extracting everything from sql, because DMA was no option.
ccm 3.3.5 was integrated with ad, so upgrading to 4.2 and then upgrading
with DMA was no option for us, as DMA is just not reliable enough. (from
several experiences)
As the not all the enduser stuff could be migrated anyway, a rebuilt with
the extracted data was our best and fastest option.
Migration scenario was trunk between old and new cluster, as big bang was
not possible ( 100+ vg248`s). and DN`s spreadout through everywhere.
We were able to dynamically migrate end-users from the old to the new
cluster, keeping features and apps like voicemail and ipccx, and attendant
application (3rd party), and billing app.

wherever possible i try to avoid using DMA, as i just cannot rely on it.
also if i quote projects like these, i just can`t afford the lost hours/days
and sometimes weeks because of faulty DMA behaviour. (unfortunately from
experience)

However, after upgrading the complete environment, i cannot say i have had
any issues worth mentioning as unstable.

just my 2 cents,

erik
On Mon, Aug 11, 2008 at 9:49 PM, Carter, Bill <bcarter at sentinel.com> wrote:

>  What version are you coming from? I have done several 6.1.1.1000-13
> installs and upgrades.  No problems with 6.1.2.1000-13.
>
>
>
> Ran into a bug this weekend when upgrading from 4.2(3) SR3 or greater to
> UCM 6.1(2). This bug effects upgrades from 4.2(3) to UCM version 6.X and 7.X
>
>
>
> CSCsl26081<http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCsl26081>
>
>
>
> The bug involves the migration of the file
> "VG224_display_instance-mgcp.xml". When the install of 6.X is merging data
> from the DMA file, it will try to import this xml file and fail. At this
> point the display on UCM 6.X reads "Halted: Installation failed". You then
> have the option of dumping diagnostic files and starting over.
>
>
>
> Nothing in the logs indicates what the problem is. This error appears
> approximately 1 hour into an upgrade.
>
>
>
> 2 Workarounds:
>
>    1. Prior to UCM 6.X Installation/Upgrade
>       1. Run DMA on the CM 4.2(3) publisher, correct any errors as normal
>       2. delete the file "VG224_display_instance-mgcp.xml" from C:\Program
>       Files\Cisco\Bin\Xmltemp\Xml
>       3. Re-Run DMA on the 4.2(3) Publisher
>       4. Proceed with an upgrade to UCM 6.X
>    2. After starting the UCM 6.X installation / Before Import of DMA File
>     (at this point UCM 6.X is installing on the server and the hard drives have
>    been formatted).
>       1. Go into the DMA***.tar file and delete the file. This is
>       complicated because you don't actually want to open the file.
>
>
>
>
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Scott Voll
> *Sent:* Monday, August 11, 2008 2:43 PM
> *To:* Cisco VoIP
> *Subject:* [cisco-voip] CM stable @ 6.1.2.1106?
>
>
>
> I'm putting a new / upgraded CM 6.1.2 into production this weekend.  Should
> I be running 6.1.2.1000-13 or 1106-1?  any issues with either one?
>
>
>
> Thanks
>
>
>
> Scott
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080811/f96a3448/attachment.html>