We are running CCM version 4.1(3) which is microsoft windows platform and we are going to use CCM version 6.0 which is linux based, what can we do to transfer the configuration on 4.1(3) to 6.0 where both OS are different?
Also, is there an upgrade method to move from 4.1(3) to 6.0 or I have to do installation for new machine with linux system? Again, my old configuration: how can I transfer it successfully?
There is a Windows Upgrade process that uses a tool called DMA (Data Migration Assistant) to move your config from Windows to Linux on CCM 6.x. Have a look at this process;
This option allows you to import database information from a Cisco Unified Communications Manager 4.x system by using a file that the Data Migration Assistant (DMA) tool produces.
From this good doc;
Upgrading to Cisco Unified Communications Manager Release 6.0(1) from Cisco Unified Communications Manager 4.x Releases
Hope this helps!
That is very nice, thanks a lot.
One more thing please: look like there is a kind of redundancy can be done in case we have two or three callmanager, so in case one is fail the other can take the action. In AVAYA, we were use a senario: two servers, each one has an IP address, and there is a virtual IP address direct to the active server, and they communicate between each other to detect who now is failed, ... is there something can be done in CCM to have a level of redundancy? Does cisco use clustering in this case? I need a link that can help me understand that, and thanks alot.
Yes, Callmanager uses clustering using 1 Publisher and Multiple Subscribers to accomplish full redundancy;
Here is some info about CCM Load Balancing;
Balanced Call Processing
After installing the Cisco Unified CallManagers that form a cluster, you should, as much as possible, evenly balance the call-processing load across the system by distributing the devices (such as phones, gateways, CTI route points, CTI ports, and route lists) among the various Cisco Unified CallManagers in the cluster. To distribute the devices, you configure Cisco Unified CallManager groups and device pools and then assign the devices to the device pools in a way that achieves the balance you want.
Cisco Unified CallManager groups and device pools represent logical groupings of devices that you can arrange in any way that you want. For ease of administration, make sure that all the devices in a group or pool share a common and easily identified characteristic, such as their physical location on the network.
You can also use Cisco Unified CallManager groups to establish redundancy (backup call processors) for the primary Cisco Unified CallManager in the group. A Cisco Unified CallManager group comprises an ordered list of up to three Cisco Unified CallManager servers. During normal operation, the first (primary) Cisco Unified CallManager in the group controls all device pools and devices that are assigned to that group. If the primary Cisco Unified CallManager in a group fails, control of the device pools and devices that are registered with the primary Cisco Unified CallManager transfers to the next Cisco Unified CallManager in the group list.
For example, assume a simplified system that comprises three Cisco Unified CallManagers in a cluster, with 300 existing Cisco Unified IP Phones and provisions to auto-register new phones as they are added later.
The configuration includes four Cisco Unified CallManager groups: group G1 assigned to device pool DP1, group G2 assigned to device pool DP2, group G3 assigned to device pool DP3, and group G4 assigned to device pool DP4. Group G4 serves as the default group for devices that auto-register.
Unified CM1 serves as the primary Cisco Unified CallManager for the devices in DP1 and DP2, first backup for DP3, and second backup for the devices in DP4.
Unified CM2 serves as the primary Cisco Unified CallManager for the devices in DP3 and DP4, first backup for DP1, and second backup for the devices in DP4.
Unified CM3 serves as the first backup Cisco Unified CallManager for the devices in DP2 and DP4 and second backup for the devices in DP1 and DP3.
From this good doc;
Cisco Unified CallManager Groups
A Cisco Unified CallManager group comprises a prioritized list of up to three Cisco Unified CallManagers. The first Cisco Unified CallManager in the list serves as the primary Cisco Unified CallManager for that group, and the other members of the group serve as secondary (backup) Cisco Unified CallManagers.
Cisco Unified CallManager groups associate with devices through device pools. Each device belongs to a device pool, and each device pool specifies the Cisco Unified CallManager group for all of its devices.
Cisco Unified CallManager Groups:
Call processing load balancing You can configure device pools and Cisco Unified CallManager groups to distribute the control of devices across multiple Cisco Unified CallManagers.
Device pools provide a convenient way to define a set of common characteristics that can be assigned to devices.
Hope this helps!
Please remember to rate helpful posts.....
Thanks a lot Rob.
One more point, I am looking for a documents about the CCM version 6 (which is linux based) giving me data about the hardware and software specification related to CCM version 6.0
Actually I found a documents for the CCM hardware specifications to be used with the CCM verion 6, but did not find a document about the OS software version (which linux? redhat? which version?), also I did not get the Bill Of Material for the CCM 6 to know if the OS come with the CD or need to be bought from the market separated.
Your kindly help is high appreciated.
With CCM 6.x you dont get a seperate OS CD/DVD as it is now "built-in" with the CCM DVD. So, all you need to do is insert the CM DVD and follow the Install Wizard and that will install the underlying Linux OS along with CCM 6.x
Hope this helps!
Thanks for your help :)
What is that linux? Redhat, Fedora, Susi? And how can I know the used linux kernel version with the CM 6.x? I searched for documents and did not find on the cisco website.
Hope you are well.
All of the documentation suggests that RedHat is the Linux flavour of the OS being used since 5.0