Broadband Command CenterTM 6

Upgrading Guide
Upgrading from BCC 5.5 to 6.x
Windows

www.incognito.com

www.incognito.com Phone: +1.604.688.4332 Toll-Free 1.800.877.1856 (North America)

Upgrading BCC 5.5 to 6 Windows

Copyright 2011 Incognito Software Inc. All rights reserved.

Incognito is a registered trademark of Incognito Software Incorporated. Address Commander, Auto-Configuration Server, Broadband
Command Center, Central Licensing Service, FastFlow BPM, Incognito Configuration File Manager Service, Incognito
Configuration File Manager Proxy Service, Incognito DHCP Service, Incognito DNS Service, Incognito Management Console,
Incognito KDC Service, Incognito KDC Wrapper Service, Incognito Multimedia Provisioning Service, Incognito TFTP Service,
Incognito Web Management Console, Java Incognito Management Console, Name Commander, Network Discovery Probe, Network
Resource Commander, Service Activation Center, User Management Service, and the Incognito Software logo are trademarks of
Incognito Software Incorporated. All other trademarks are the property of their respective owners.
No parts of this work may be reproduced in any form or by any means without the written permission of the publisher.

While every precaution has been taken in the preparation of this document, the publisher and the author assume no responsibility for
errors or omissions, or for damages resulting from the use of information contained in this document or from the use of programs and
source code that may accompany it. In no event shall the publisher and the author be liable for any loss of profit or any other
commercial damage caused or alleged to have been caused directly or indirectly by this document.
Incognito Software Inc., 375 Water Street, Suite 500, Vancouver, BC, Canada, V6B 5C6.

This product contains software developed by the Apache Software Foundation (http://www.apache.org/) and the OpenSSL Project for
use in the OpenSSL Toolkit (http://www.openssl.org/).

TRADEMARKS:
CableLabs and DOCSIS are trademarks of Cable Television Laboratories, Inc.
CORBA is a registered trademarks of Object Management Group, Inc. in the United States and/or other countries.
Debian is a registered trademark of Software in the Public Interest, Inc.

Intel, Pentium, and Xeon are trademarks of Intel Corporation in the U.S. and other countries.
Linux is a registered trademark of Linus Torvalds.
Microsoft, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the United
States and/or other countries.
Oracle and Java are registered trademarks of Oracle Corporation and/or its affiliates.

Red Hat and Enterprise Linux are registered trademarks of Red Hat, Inc. in the United States and other countries.
SPARC is a registered trademark of SPARC International, Inc. in the United States and other countries.
TAO and ACE are registered trademarks of Washington University.
UNIX is a registered trademark of The Open Group.

2 | Page
Upgrading BCC 5.5 to 6 Windows

Table of Contents

Table of Contents ............................................................................................................... 3

1. Introduction.................................................................................................................... 4
1.1 OS Prerequisites ................................................................................................................... 4
1.2 Test Devices to be Prepared ................................................................................................ 4
1.3 Logging and Making Changes ............................................................................................. 5
2. Before Upgrading .......................................................................................................... 6
3. Upgrading the Services................................................................................................ 6
3.1 Break Failover, Backup BCC 5.5 and Upgrade to BCC 6 Services .................................... 6
3.2.1 Detailed Steps for DHCP/MPS .......................................................................................................... 7
3.2.2 Detailed Steps for CFM/CFMP .......................................................................................................... 7
3.2.3 Detailed Steps for DNS ...................................................................................................................... 8

3.3 Testing Services.................................................................................................................... 8

3.3.1 DHCP ................................................................................................................................................. 8
3.3.2 CFM ................................................................................................................................................... 9
3.3.3 CFMP ................................................................................................................................................. 9
3.3.4 MPS ................................................................................................................................................... 9

4. Roll Back Plan.............................................................................................................. 11

4.1 DHCP and MPS .................................................................................................................... 11
4.2 CFM/CFMP ........................................................................................................................... 12
4.3 DNS ...................................................................................................................................... 12

3 | Page
Upgrading BCC 5.5 to 6 Windows

1. Introduction
This document will outline the Windows procedure to upgrade the DHCP, MPS, DNS, CFM and CFM Proxy
services in BCC 5.5 to the new DHCP, MPS, DNS, CFM and CFM Proxy services in BCC 6. It will outline
the upgrade procedure in detailed steps and a plan for rolling back should any critical issues occur.

1.1 OS Prerequisites

On the Windows platform, all the BCC 6 services are supported on the Windows 2003 and 2008 (SP2), 32
bit only environment.

BCC 5.5 services run on Windows 2003 (SP2) 32-bit environment only. There may be a requirement,
depending on your needs, to upgrade the Operating System at the same time. This document will cover the
conventions necessary for the roll back to a different operating system, should it be needed.

A major consequence of the migration for the Windows OS is any rollback would include a full reinstall and
configuration of the original server from backup (following your disaster recovery procedures for the server).
An alternative to consider would be to migrate to an additional server(s) running the Windows version of your
choice. This would have the advantages of less provisioning downtime and a quicker rollback should any
critical issues occur.

The JIMC (Java Incognito Management Console) is supported on several OSs which can be referenced at
www.incognito.com.

1.2 Test Devices to be Prepared

Incognito recommends a minimum of two devices to be set aside before the upgrade for testing purposes.
Ideally one of each supported production device type would be tested.

The devices will need to be located in the relevant network segment and at least one device should be an
MTA. The MAC address of each of these devices should be recorded in order to make controlled tests of the
new configuration after the upgrade. These devices will be rebooted to test the new configuration.

4 | Page
Upgrading BCC 5.5 to 6 Windows

1.3 Logging and Making Changes

Logging levels for all services should be set to Level 3 (Max). This provides for maximum logging to monitor
for any upgrade issues. No changes should be allowed to the provisioning databases during the upgrade
and at any time after the last service backup until the upgrade is complete.

5 | Page
Upgrading BCC 5.5 to 6 Windows

2. Before Upgrading

This procedure will involve some downtime during the services upgrade so its important that this is
scheduled within a maintenance window.

Before beginning, ensure you have the following:

1. A full OS backup for the Windows server is essential prior to the BCC 6 migration (if you are
changing Operating Systems). This is required for a service rollback should any critical issues occur.
The normal server backup procedure should occur. Please consult the relevant Windows
documentation. Incognito is not responsible for the backup of the OS.

Note The OS backup will not include the data required to restore BCC. This is a separate
procedure and is detailed in section 3.

2. The current BCC 5.5 service installation packages of DHCP, DNS, CFM, CFMP and MPS with the
associated installation keys. If there is a need to rollback, these are required.
3. The BCC 6 service installation packages of DHCP, CFMP, CFM, DNS and MPS with new keys for all
the services.
4. The IMC installation packages for both the BCC 5.5 and the JIMC for the 6 version. This should be
completed in advance of the service upgrade procedure as it has no impact on production.
5. Backups should be made of all Incognito services on Primary and Secondary servers to create a
restore point.

3. Upgrading the Services

3.1 Break Failover, Backup BCC 5.5 and Upgrade to BCC 6

Services

The individual BCC service installation executables will automatically upgrade the 5.5 services to 6. Ensure
during installation that the path matches the existing BCC 5.5 file path.

6 | Page
Upgrading BCC 5.5 to 6 Windows

3.2.1 Detailed Steps for DHCP/MPS

1. On the Primary service from the IMC, on both the DHCP and MP Services, select Service Configuration
Failover Terminate Failover
2. On the Secondary service:
2.1. On the IMC Service menu select Work Offline for both the DHCP and MP Service
2.2. On the Secondary server, stop the services in the Windows Services control panel
3. Delete all the files within the Secondary service /data folder, not including the sub folders. Default
location is at C:\Program Files\Incognito Software\NT\ipcmdr\data.
4. Run the BCC 6 service installation executable on the Secondary and do not start the service when
prompted
5. On the Primary service:
5.1. Set the service to Work Offline
5.2. Select Service Configuration Database Backup Scheduling Force Service Backup Now
and copy backup to temporary folder during migration
5.3. Stop the service, run the BCC 6 service installation executable and start service on completion
6. Start the Secondary service and then log on to it (using the JIMC). The administrator password will
be changed to incognito. Reset the password when prompted. On the Service menu, select Work
Online.
7. Log on to the Primary service and select Work Online
8. Initiate failover to the Secondary and force a failover database resynchronization

From steps 7 to 9, the system will be unresponsive to customer provisioning requests.

3.2.2 Detailed Steps for CFM/CFMP

The following steps will be repeated for any server running CFM/CFMP in the cluster. You should work on
one server at a time.

1. In the IMC, set the CFM and CFMP services to Work Offline
2. Select Service Configuration Database Backup Scheduling Force Service Backup Now on both
services and copy backup to temporary folder during migration
3. Stop the services from the Windows Services control panel
4. Upgrade the OS to a supported Operating System (If necessary, see section 1.1)
5. Install the relevant BCC 6 service executable for the CFM and CFMP services and start the service upon
completion
6. Log on to both the CFM and CFMP services (using the JIMC only). The administrator password will be
set to incognito. Reset the password when prompted

7 | Page
Upgrading BCC 5.5 to 6 Windows

7. Enter the license information when prompted for each service

8. On the Service menu, select Work Online

3.2.3 Detailed Steps for DNS

Perform the following steps for each server in the DNS cluster:

1. In the IMC, set DNS service to Work Offline

2. Select Service Configuration Database Backup Scheduling Force Service Backup Now and copy
backup to temporary folder during migration
3. Stop DNS Service from the Windows Services control panel
4. Upgrade the OS to a supported Operating System (If necessary, see section 1.1)
5. Install the relevant BCC 6 service executable for the DNS service and start the service upon completion
6. Log on to the service (using the JIMC only) and set to Work Online

After the services are upgraded, each should be set to Online and Integration Status should show the
correct multicast cluster membership. At this point, service will be back in operation but needs verification.

Note - If new servers are being installed with new IP addresses each must be added to the CMTS cable-
helper list.

3.3 Testing Services

The test cable modems and MTAs should be tested in addition to the connected CPEs. Spot tests should be
made in the network. The network should be monitored to confirm that modems are renewing correctly and
that the services are stable. The Incognito Java Statistics Monitor, Java Visual IP Monitor and Java
Message Monitor can be used to track the upgraded services.

3.3.1 DHCP
Make a note of the MAC address of the CM and/or MTA used for testing.

To view the process of provisioning:

In a text editor list C:\Program Files\Incognito Software\NT\IPCmdr\data\ipcmdr1.log by <MAC>

To ensure the DHCP process is finishing, check for ACKs:

8 | Page
Upgrading BCC 5.5 to 6 Windows

In a text editor list C:\Program Files\Incognito Software\NT\IPCmdr\data\ipcmdr1.log by <MAC> and

filter by ACK

If no ACKs appear in the logs review the routing and CMTS settings. If static routes were present in your
original configuration ensure these are still present.

When testing CPE devices review the DHCP service logs where an ACK for the CPE MAC indicates the
device provisioned properly. In the JIMC review the Dynamic DNS Work Queue (Service Diagnostics
Work Queues) to ensure DDNS updates occur correctly.

3.3.2 CFM
Review device file generation:
In a text editor list C:\Program Files\Incognito Software\NT\CFM\data\cfmcmdr1.log by <MAC>

If files are not being generated, review the service Multicast Integration settings and ensure that all service
versions are of the same major version release (e.g. 6.1.*).

3.3.3 CFMP

Ensure file download completes:

In a text editor list C:\Program Files\Incognito Software\NT\CFMProxy\data\ cfmproxycmdr1.log by
<MAC>

In the JIMC, review the Service Diagnostics Statistics which displays the Input/Output of data across the
CFMPs in a cluster.

If issues are occurring, check there are no routing issues on the CMTS and service servers. Also ensure a
firewall is not blocking the ports the CFMP service selected for the file download.

3.3.4 MPS

Review for successful provisioning:

In a text editor list C:\Program Files\Incognito Software\NT\MPS\data\mpscmdr1.log by <MAC>

9 | Page
Upgrading BCC 5.5 to 6 Windows

When an MTA device comes online, it completes DHCP then it sends an SNMP enrollment
INFORM to the MPS (SNMP entity) specified in option 122 sub-option 3. This should be present for each
MTA in the logs.

In the JIMC, review the Service Diagnostics Statistics for MTA and CM statistics.

Once all testing scenarios complete successfully and you are satisfied all requirements are met, you can go
live in production.

10 | Page
Upgrading BCC 5.5 to 6 Windows

4. Roll Back Plan

As mentioned in section 1.1, if the BCC 6 migration for Windows requires an OS upgrade, any rollback to
BCC 5.5 would require a complete reinstallation from backup. This would follow the standard OS disaster
recovery procedure for the server. As such any rollback would be a substantial operation.
Once the previous Windows OS is fully recovered from backup the BCC services data would need to be
restored.

Downgrading to BCC 5.5 from 6 is not possible as the databases between versions are incompatible.

4.1 DHCP and MPS

The procedure for rolling back to DHCP/MPS Service v5.5 is:

1. Take a service backup of the version 6 service on both the Primary and Secondary servers. Copy the
5.5 (created before migration) and 6 data backups to a location that is not within the server. Also copy
the service logs to the same directory (all will be supplied to Incognito for analysis)
2. On the primary server:
2.1. Break the Failover to the Secondary server
2.2. Set DHCP/MPS service to Work Offline
2.3. Stop DHCP/MPS service
2.4. Restore the previous version of Windows from backup
2.5. Check status of each service. If any issues occur remove and reinstall using BCC 5.5 packages
2.6. Stop the DHCP/MPS 5.5 service from the Windows Services control panel
2.7. Copy the contents of the 5.5 backup to the DHCP/MPS /data directory, overwriting current files
2.8. Start the DHCP/MPS 5.5 service
3. On the Secondary server:
3.1. Perform steps 2.2 2.6 for this server
3.2. Delete all the files within the secondary service /data folder not including the sub folders
3.3. Log on to the secondary service (using 5.5 IMC only). The administrator password will be changed
to incognito. Reset the password when prompted. Enter any requested license information and
set service to Work Online
4. Start primary DHCP/MPS service and log on to 5.5 IMC. Enter any requested license information and
set the service to Work Online
5. Initiate failover to the secondary and force a failover database resynchronization.

11 | Page
Upgrading BCC 5.5 to 6 Windows

Once complete the DHCP/MPS service will be rolled back to the previous revision.

4.2 CFM/CFMP
The procedure for rolling back to the CFM and CFMP Services v5.5 for each server is:

1. Set the CFM and CFMP services to Work Offline.

2. Take a service backup of both services to a location that is not within the server. Also copy the service
logs to the same directory (all will be supplied to Incognito for analysis)
3. Stop CFM and CFMP services
4. Restore the previous version of Windows from backup
5. Check status of CFM and CFMP services. If any issues occur remove and reinstall using BCC 5.5
package
6. Stop the services from the Windows Services control panel
7. Copy the contents of the 5.5 backup to the appropriate /data directory, overwriting current files
8. Start the services from the Windows control panel
9. Logon using 5.5 IMC and enter any requested license information. Set services to Work Online

Once complete the CFM and CFMP services will be rolled back to the previous revision.

4.3 DNS
The procedure for rolling back to DNS Service v5.5 for each server in the DNS cluster is:

1. Set the DNS Server to Work Offline

2. Take a service backup of the version 6 service. Copy the 5.5 (created before migration) and 6 data
backups to a location that is not within the server. Also copy the service logs to the same directory
(all will be supplied to Incognito for analysis)
3. Stop the DNS service from the Windows Services control panel
4. Restore the previous Windows installation from backup
5. Check status of DNS service. If any issues occur remove and reinstall using BCC 5.5 package
6. Copy the contents of the 5.5 backup to the DNS /data directory, overwriting current files
7. Start the DNS service from the Windows Services control panel
8. Log on using 5.5 IMC and enter any requested license information. Set DNS service to Work
Online

Once complete the DNS service will be rolled back to the previous revision.

12 | Page