Chapter 2 Pre-upgrade activities 15
•Ensure mapped drives are disconnected: Remove any mapped drives connected to the BCM 3.6/3.7 systems using the Maintenance Tools web page.
•Ensure next hop router IP address belongs to the same subnet as the static routes: The next hop router IP address for static routes in BCM 3.6/3.7 is validated during the upgrade to BCM 4.0. This means that the next hop router IP address must belong to the same subnet as the interface to which it is added, otherwise the static route is not upgraded to BCM 4.0.
For example: Static routes are configured on LAN1 interface with IP address of 172.17.22.10
Route 1: | Route 2: |
Destination address: 1.1.1.1 | Destination address: 2.2.2.2 |
Destination mask: 255.255.255.0 | Destination mask: 255.255.255.0 |
Next hop: 172.17.22.20 | Next hop: 10.20.30.40 |
Metric: 1 | Metric: 1 |
On BCM 4.0, route 1 is added and route 2 is deleted since the next hop, 10.20.30.40, does not belong to same subnet as LAN1.
•Confirm that the voice inventory service is running: To avoid potential errors about the MSC core telephony software, the media services processor expansion cards
•Ensure no overlapping subnets in IPSec branch office tunnel accounts: In BCM 3.6/3.7 you can configure an IPSec branch office tunnel where IP subnets in the local accessible networks overlap the IP subnets in the remote accessible networks. This is not supported in BCM 4.0. If an IPSec branch office tunnel account has overlapping subnets, this account will not exist after the upgrade to BCM 4.0.
Before upgrading your system from BCM 3.6/3.7 to BCM 4.0, make sure there are no overlapping subnets between the local and remote accessible networks in any of your IPSec branch office tunnel accounts.
•Upgrade IVR application: If your site uses IVR, you must upgrade IVR before upgrading to BCM 4.0 software. Refer to your IVR upgrade guide for more detailed information.
•Prepare Reporting for Contact Center (RCC): Immediately before running the Upgrade Wizard, perform the following steps to retain your RCC data:
1 Disable all skillsets and log out all agents from the call center.
2 Ensure all calls have exited the call center skillsets.
3 Ensure that RCC has downloaded all the data from the BCM and a complete
4 Backup the RCC database on the Web Host PC. The backup location is:
•For RCC versions 2.3.209 and later, the backup location is: C:\Program Files\MySQL\MySQL Server 4.1\data\CCRDB.
•For RCC versions earlier than 2.3.209, the backup location is C:\MySQL\data\CCRDB.
Upgrade Guide