Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

Moving from the Lab to Production. An AVVID Workplan ....

Hi,

After a failed attempt to move a perfectly running Cluster from the Lab to Production, I decided to share my pain; hopefully, saving you some valuable time in the future.

We are running 3.1x in Prod and 3.2x in the Lab; furthermore, we are running DL320s in Prod and DL380 G2s in the Lab. Here's a checklist of what we now know to do when the Lab goes into Production. Keep in mind, that we built the 3.2 environment using an STI backup and thus kept the same hostnames. Of course that is not ideal but if find yourself in the same predicament, the following will help.

Also to be noted, we are running an ICD on a separate CRA along with Web Attendant. These steps are by no means all encompassing so we welcome your feedback to help us fill-in the blanks and read between the lines. Here's how it goes ...

CALLMAN Migration from 3.1x to 3.2x to DL380 G2

Change the IP address on Lab cluster to match Production

Connect the New CallMans into a hub outside the network.

Disjoin NEWCALLMAN01 from the Domain.

Disjoin NEWCALLMAN02 from the Domain.

Remove WINS and DNS entries on NEWCALLMAN01

Remove WINS and DNS entries on NEWCALLMAN02

Change the entries in the HOSTS file on NEWCALLMAN01

Change the entries in the HOSTS file on NEWCALLMAN02

Change the entries in the LMHOSTS file on NEWCALLMAN01

Change the entries in the LMHOSTS file on NEWCALLMAN02

Restore DC Directory on NEWCALLMAN01

Restore replication agreement of DC Directory between NEWCALLMANS

Add a new user to NEWCALLMAN01 directory

Find the new user added above in NEWCALLMAN02 directory

Add a new user to NEWCALLMAN02 directory

Find the new user added above in NEWCALLMAN01 directory

Map a drive between NEWCALLMANS to verify Windows rights

Confirm both SQL server registrations are active in Enterprise Manager on both machines

Confirm Replication of CCM database succeeded from SQL Enterprise Manager

Add a dummy device on NEWCALLMAN01

Find the device added above in the SQL table on NEWCALLMAN02 database

Add a dummy device on NEWCALLMAN02

Find the device added above in the SQL table on NEWCALLMAN01 database

Add CCRA to Hub

Verify CTI point registration

Add Reception desktop to hub

Verify Web Attendant screen

Shutdown production Cluster

Plug the Lab into Production

At this point we get a bit confident and add some wallpaper from TheMatrix.com

Repeat steps 17-27

Start making calls.

-Erik.

2 REPLIES
Community Member

Re: Moving from the Lab to Production. An AVVID Workplan ....

Wow, that is a bit complex and complicated, I can see why you might have had problems. Did you finally get everything working?

Here's a suggestion and some insight from doing this about 10 times with different versions of CCM.

Use the same servers in the lab as you do in production. For instance we use MCS-7835 (Compaq DL380's) in Production. In the lab we have just plain Compaq DL-380's.

Build and test your setup in the lab, once you are all set to upgrade the Production CCM Cluster, shutdown the servers in the Lab and Production, take the drives from the lab and put them in the Production servers. Shelve the existing Production drives for a couple weeks as a backup.

tm

Tim Medley, CCNP+Voice, CCDP, CWNA

Sr. Network Architect

VoIP Group

iReadyWorld

Community Member

Re: Moving from the Lab to Production. An AVVID Workplan ....

Hi Tim,

That is an elegant solution. At the moment we are running DL320s in production and DL380s in the Lab. Our goal would be to have same same like you described.

We are working through the checklist this week and we will try to bring those boxes into production again Friday night. The items I listed are meant to be exhaustive because the environments are not same same.

Erik

88
Views
4
Helpful
2
Replies
CreatePlease to create content