Cisco BBSM 5.2 User Guide - C - Upgrading BBSM from Software Rel. 5.1 to 5.2 [Cisco Building Broadband Service Manager]

Table Of Contents

Upgrading BBSM from Software Rel. 5.1 to 5.2

Before You Start

Upgrade Procedure

Upgrading BBSM from Software Rel. 5.1 to 5.2

This appendix describes how to upgrade BBSM software release 5.1 to software release 5.2. The upgrade consists of the following four separate patches that can be installed locally on a BBSM server or on multiple BBSM servers remotely from another computer:

•Patch 5200 (Upgrade51to52Part0.exe)

•Patch 5201 (Upgrade51to52Part1.exe)

•Patch 5202 (Upgrade51to52Part2.exe)

•Patch 5203 (Upgrade51to52Part3.exe)

All of the patches that you need to perform this upgrade are located on the BBSM 5.1 to 5.2 Upgrade Utility CD. Use one of the following procedures to obtain the upgrade package:

•If you have a Cisco service contract—Use the part number on the following Cisco Product Upgrade Tool website to request the Cisco BBSM 5.2 upgrade package:

http://tools.cisco.com/gct/Upgrade/jsp/index.jsp

•If you do not have a Cisco service contract—Contact your local Cisco account manager to place an order for the upgrade package (part number BB-SM-5.2-UPG=).

This procedure is written specifically for upgrading the BBSM 5.1 server with Service Pack 3 (SP3) installed.

Caution The upgrade can only performed on a BBSM 5.1 server upgraded to SP3. In addition, before starting the upgrade, you must install MSFix4.exe and MSFix5.exe on your BBSM server.

Both the external and internal NICs must be plugged in and enabled before the upgrade or the upgrade will fail.

If you have a CMTS configured on your BBSM server, this upgrade cannot be performed.

If you are upgrading a BBSM 5.1 server with Patch 1069 applied, the BBSM server remains in the initializing state and does not move to the running state. Consequently, all clients fail to connect after the upgrade. In this case, the workaround is to install Service Pack 1 (SP1) to the BBSM server after the upgrade is complete.

Before You Start

Please read the following important information before beginning the procedure.

Important Notes

•Before you begin the procedure, make sure that you have enough free disk space to complete the installation. The upgrade requires an additional 365 MB of hard disk space on your server.

•The patches must be installed in the order shown in the procedure. Otherwise, the upgrade will fail, and your BBSM server could become unstable. After installing each patch, verify that the previous patch was successfully installed.

•For additional information about using WEBpatch to install the patches and verify the installations, refer to the "Installing Service Packs or Patches and Upgrades (WEBpatch)" section.

•If you use the Site Controller and/or Building Broadband Service Director (BBSD) features, you must upgrade these features at the same time as the BBSM upgrade or BBSM will not function properly. Refer to the BBSM 5.2 website for the downloads and release notes.

Upgrading from Software Release 5.0 to 5.1 and then to Release 5.2

If you performed a BBSM server upgrade from software release 5.0 to 5.1 and then try to upgrade to BBSM 5.2, a duplicate DLL file will be created. Clients will not be able to connect to BBSM until you delete this duplicate file. Instead of receiving the Start page, clients will get an error message. To delete the duplicate file, refer to Step 9 in the Upgrade Procedure.

Updating Custom DLLs

Update your custom dynamic link libraries (DLLs) by using the BBSM 5.2 SDK. For a customized switch DLL, use the BBSM 5.2 SDK to generate a new registry file and enter the DLL in the registry after the upgrade.

Restoring BBSM 5.1 Custom Page Sets

To restore custom BBSM 5.1 page sets that have the same default names as BBSM 5.2 page sets, go to the c:\atcom\Patch\backup5201 directory and copy them to the appropriate location.

Restoring Your Own TFTP Server

This caution applies only if you have installed your own TFTP server on BBSM. When you upgrade BBSM, the existing TFTP server is replaced by the Cisco TFTP server, and the existing registry entries are overwritten with the following values. After the upgrade, you will need to restore your original TFTP server:

[HKEY_CURRENT_USER\Software\Cisco Systems Inc.\Cisco TFTP Server\1.1\Options]
"LogFileName"="C:\\atcom\\TFPServer\\Log\\TFTPServer.log"
"TFTPRootDirectory"="C:\\atcom\\TFPServer"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TFTP]
"Description"="Cisco TFTP Server"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TFTP\parameters]
"AppDirectory"="c:\\atcom\\TFTPServer"
"Application"="c:\\atcom\\TFTPServer\\TFTPServer.exe"
To save your original TFTP server and restore it after the upgrade, follow the steps below. The procedure explains how to export part of your Windows registry before the upgrade and then restore your TFTP server after the upgrade, or if you have already upgraded to BBSM 5.2 and did not export the TFTP registry settings before the upgrade, the procedure explains how to restore your TFTP server at this time.

Step 1 Choose Start > Run. The Run dialog box appears.

Step 2 Enter regedit, and click OK. The Registry Editor window appears.

Step 3 Double-click HKEY_LOCAL_MACHINE:

•If you are exporting the TFTP registry settings before performing the upgrade, continue with Step 4.

•If you have performed the upgrade without exporting the TFTP registry settings and want to restore them, go to Step 5.

Step 4 If you have not performed the upgrade yet, export the registry file, install the upgrade, and reload the registry file, as follows:

a. Navigate to System > CurrentControlSet > Services > TFTP, and select the TFTP folder.

b. Export the registry file. From the Registry menu, select Export Registry File, enter a file name, and click Save. (Do not enter a file extension. The file defaults to a .reg file.)

c. From the Registry menu, select Exit to close the registry application.

d. Install the BBSM 5.2 Upgrade. When you have finished installing the upgrade, the TFTP server running on BBSM will be the Cisco TFTP server.

e. To restore your original TFTP server as the default, double-click the .reg file you saved in Step 4 b and click Yes to reload your settings back into the registry.

You have completed this procedure.

Step 5 If you have already performed the upgrade without exporting the registry file, restore your TFTP settings as follows:

a. Navigate to System > CurrentControlSet > Services > TFTP > Parameters.

b. Double-click the AppDirectory text. In the Edit String window, change the Value Data text to the directory of your TFTP server and click OK.

c. Double-click the Application text. In the Edit String window, change the Value Data text to the name of your TFTP application and click OK.

d. From the Registry menu, click Exit to close the registry application.

You have completed this procedure.

Upgrade Procedure

Follow this procedure in the exact order shown to install the upgrade.

Step 1 Load the BBSM 5.1 to 5.2 Upgrade Utility CD on your BBSM server.

•For a local BBSM installation, go to Step 4.

•For a remote BBSM installation, continue with Step 2. Note the following about remote installations:

–It usually takes about 5 or 10 minutes for the server to restart and for BBSM to initialize. If you are using Windows 2000 Professional (SP2 or later) or Windows XP Professional to install the patch remotely, the web pages will load very slowly unless you uncheck the Client for Microsoft Networks check box in the Windows NIC Properties window.

Note For details on unchecking the Client for Microsoft Networks check box, refer to the "Configuring Windows 2000 Professional or XP Professional" section.

–Because of known issues with certain versions of Netscape Navigator, use Microsoft Internet Explorer 6 (IE6) for remote installations.

Step 2 In the IE browser Address field, type http://<external_NIC_address>:9488/www, where <external_NIC_address> is the external NIC address of the remote BBSM server. For example, type http://192.168.38.1:9488/www, and press Enter. The Enter Network Password window appears.

Step 3 Enter your username and password (leave the Domain field blank) and click OK. The remote BBSM Dashboard appears. (You must have administrator privileges to log on.)

Step 4 Install the first patch, Patch 5200, as follows:

a. From the Dashboard, use the WEBpatch utility to install Patch 5200, Upgrade51to52Part0.exe. The patch usually takes about 10 minutes to install, including the automatic server reboot.

Caution The Java 2 plug-in, version 1.3.1_03, must be installed on the computer you are using to transfer the patches, whether you are installing the patches remotely or directly on the BBSM server.
· If you are installing patches using a remote computer, the Java plug-in must be installed on that remote computer.
· If you are installing directly on the BBSM, the Java plug-in must be installed on your BBSM server.
· You must use this version: other versions will fail.
· If the plug-in is not installed already, click Go To Java Download Page, download the plug-in, and install it. You can also go to the BBSM 5.2 Software Download web page and download the plug-in from there.

b. Verify that the patch was installed. From the WEBpatch BBSM Patch Log web page, view the logs for Patch 5200. If the "InstallPatch successful for" and "Reboot successful" logs appear, the patch installed successfully. (See Figure C-1.)

Figure C-1 WEBpatch BBSM Patch Log Web Page showing Patch 5200

Step 5 Install the second patch, Patch 5201, as follows:

a. From the Dashboard, use the WEBpatch utility to install Patch 5201, Upgrade51to52Part1.exe. The patch usually takes 15 minutes to install, including two automatic reboots that occur during the installation.

b. Verify that the patch was installed, as explained in Step 4 b.

Step 6 After installing the second patch, Patch 5201, using Microsoft Internet Explorer, delete cookies and other temporary Internet files on your computer, as follows:

Caution You must perform this step before installing Patch 5202 for the installation to be successful.

a. From the Microsoft IE browser, choose Tools > Internet Options.

b. From the Temporary Internet files area, do the following:

- Click Delete Cookies and click OK.

- Click Delete Files, check the Delete all offline content check box, and click OK.

- Click Settings, click the View Files button, and verify that there are no temporary Internet files.

c. Close the Temporary Internet Files window, and then click OK twice to exit the Settings and Internet Options windows.

d. Close Internet Explorer and reboot your computer.

Step 7 Install the third patch, Patch 5202, as follows:

Note If Windows 2000 SP3 is not installed on your BBSM server, Patch 5202 takes about 20 minutes to install, including the reboot. If you have installed SP3, it takes about 3 minutes to install, including the automatic reboot.

a. From the Dashboard, use the WEBpatch utility to install Patch 5202, Upgrade51to52Part2.exe.

b. Verify that the patch was installed, as explained in Step 4 b.

Step 8 Install the fourth patch, Patch 5203, as follows:

a. From the Dashboard, use the WEBpatch utility to install Patch 5203, Upgrade51to52Part3.exe. The patch usually takes about 10 minutes to install, including the automatic reboot.

b. Verify that the patch was installed, as explained in Step 4 b.

Step 9 If you upgraded from software release 5.0 to 5.1 and then to 5.2, delete the duplicate DLL file that is keeping clients from connecting to BBSM. Delete the GenericSwitchNoLinkStatus.DLL file in the c:\atcom\install\switches directory. Then restart BBSM.

(Do not delete the latest version of this DLL file that resides in the c:\atcom\install directory.)

If you do not have direct access to the BBSM server, you can delete this file remotely by installing Patch 5223 (BBSM5.0to5.2DLLPatch.exe), which is available for download at this Cisco website:

http://www.cisco.com/pcgi-bin/tablebuild.pl/bbsm52

After you install this patch, the BBSM server reboots automatically.

	Cisco BBSM 5.2 User Guide
	C - Upgrading BBSM from Software Rel. 5.1 to 5.2
Cisco BBSM 5.2 User Guide Preface 1 - Introduction 2 - Getting Started 3 - Basic BBSM Configuration 4 - System Operation 5 - Troubleshooting A - Installing an SSL Certificate B - Using BBSD C - Upgrading BBSM from Software Rel. 5.1 to 5.2 D - Changing the Server Bandwidth Parameter Settings Glossary Index	Download this chapter C - Upgrading BBSM from Software Rel. 5.1 to 5.2 Table Of Contents Upgrading BBSM from Software Rel. 5.1 to 5.2 Before You Start Upgrade Procedure Upgrading BBSM from Software Rel. 5.1 to 5.2 This appendix describes how to upgrade BBSM software release 5.1 to software release 5.2. The upgrade consists of the following four separate patches that can be installed locally on a BBSM server or on multiple BBSM servers remotely from another computer: •Patch 5200 (Upgrade51to52Part0.exe) •Patch 5201 (Upgrade51to52Part1.exe) •Patch 5202 (Upgrade51to52Part2.exe) •Patch 5203 (Upgrade51to52Part3.exe) All of the patches that you need to perform this upgrade are located on the BBSM 5.1 to 5.2 Upgrade Utility CD. Use one of the following procedures to obtain the upgrade package: •If you have a Cisco service contract—Use the part number on the following Cisco Product Upgrade Tool website to request the Cisco BBSM 5.2 upgrade package: http://tools.cisco.com/gct/Upgrade/jsp/index.jsp •If you do not have a Cisco service contract—Contact your local Cisco account manager to place an order for the upgrade package (part number BB-SM-5.2-UPG=). This procedure is written specifically for upgrading the BBSM 5.1 server with Service Pack 3 (SP3) installed. Caution The upgrade can only performed on a BBSM 5.1 server upgraded to SP3. In addition, before starting the upgrade, you must install MSFix4.exe and MSFix5.exe on your BBSM server. Both the external and internal NICs must be plugged in and enabled before the upgrade or the upgrade will fail. If you have a CMTS configured on your BBSM server, this upgrade cannot be performed. If you are upgrading a BBSM 5.1 server with Patch 1069 applied, the BBSM server remains in the initializing state and does not move to the running state. Consequently, all clients fail to connect after the upgrade. In this case, the workaround is to install Service Pack 1 (SP1) to the BBSM server after the upgrade is complete. Before You Start Please read the following important information before beginning the procedure. Important Notes •Before you begin the procedure, make sure that you have enough free disk space to complete the installation. The upgrade requires an additional 365 MB of hard disk space on your server. •The patches must be installed in the order shown in the procedure. Otherwise, the upgrade will fail, and your BBSM server could become unstable. After installing each patch, verify that the previous patch was successfully installed. •For additional information about using WEBpatch to install the patches and verify the installations, refer to the "Installing Service Packs or Patches and Upgrades (WEBpatch)" section. •If you use the Site Controller and/or Building Broadband Service Director (BBSD) features, you must upgrade these features at the same time as the BBSM upgrade or BBSM will not function properly. Refer to the BBSM 5.2 website for the downloads and release notes. Upgrading from Software Release 5.0 to 5.1 and then to Release 5.2 If you performed a BBSM server upgrade from software release 5.0 to 5.1 and then try to upgrade to BBSM 5.2, a duplicate DLL file will be created. Clients will not be able to connect to BBSM until you delete this duplicate file. Instead of receiving the Start page, clients will get an error message. To delete the duplicate file, refer to Step 9 in the Upgrade Procedure. Updating Custom DLLs Update your custom dynamic link libraries (DLLs) by using the BBSM 5.2 SDK. For a customized switch DLL, use the BBSM 5.2 SDK to generate a new registry file and enter the DLL in the registry after the upgrade. Restoring BBSM 5.1 Custom Page Sets To restore custom BBSM 5.1 page sets that have the same default names as BBSM 5.2 page sets, go to the c:\atcom\Patch\backup5201 directory and copy them to the appropriate location. Restoring Your Own TFTP Server This caution applies only if you have installed your own TFTP server on BBSM. When you upgrade BBSM, the existing TFTP server is replaced by the Cisco TFTP server, and the existing registry entries are overwritten with the following values. After the upgrade, you will need to restore your original TFTP server: [HKEY_CURRENT_USER\Software\Cisco Systems Inc.\Cisco TFTP Server\1.1\Options] "LogFileName"="C:\\atcom\\TFPServer\\Log\\TFTPServer.log" "TFTPRootDirectory"="C:\\atcom\\TFPServer" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TFTP] "Description"="Cisco TFTP Server" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TFTP\parameters] "AppDirectory"="c:\\atcom\\TFTPServer" "Application"="c:\\atcom\\TFTPServer\\TFTPServer.exe" To save your original TFTP server and restore it after the upgrade, follow the steps below. The procedure explains how to export part of your Windows registry before the upgrade and then restore your TFTP server after the upgrade, or if you have already upgraded to BBSM 5.2 and did not export the TFTP registry settings before the upgrade, the procedure explains how to restore your TFTP server at this time. Step 1 Choose Start > Run. The Run dialog box appears. Step 2 Enter regedit, and click OK. The Registry Editor window appears. Step 3 Double-click HKEY_LOCAL_MACHINE: •If you are exporting the TFTP registry settings before performing the upgrade, continue with Step 4. •If you have performed the upgrade without exporting the TFTP registry settings and want to restore them, go to Step 5. Step 4 If you have not performed the upgrade yet, export the registry file, install the upgrade, and reload the registry file, as follows: a. Navigate to System > CurrentControlSet > Services > TFTP, and select the TFTP folder. b. Export the registry file. From the Registry menu, select Export Registry File, enter a file name, and click Save. (Do not enter a file extension. The file defaults to a .reg file.) c. From the Registry menu, select Exit to close the registry application. d. Install the BBSM 5.2 Upgrade. When you have finished installing the upgrade, the TFTP server running on BBSM will be the Cisco TFTP server. e. To restore your original TFTP server as the default, double-click the .reg file you saved in Step 4 b and click Yes to reload your settings back into the registry. You have completed this procedure. Step 5 If you have already performed the upgrade without exporting the registry file, restore your TFTP settings as follows: a. Navigate to System > CurrentControlSet > Services > TFTP > Parameters. b. Double-click the AppDirectory text. In the Edit String window, change the Value Data text to the directory of your TFTP server and click OK. c. Double-click the Application text. In the Edit String window, change the Value Data text to the name of your TFTP application and click OK. d. From the Registry menu, click Exit to close the registry application. You have completed this procedure. Upgrade Procedure Follow this procedure in the exact order shown to install the upgrade. Step 1 Load the BBSM 5.1 to 5.2 Upgrade Utility CD on your BBSM server. •For a local BBSM installation, go to Step 4. •For a remote BBSM installation, continue with Step 2. Note the following about remote installations: –It usually takes about 5 or 10 minutes for the server to restart and for BBSM to initialize. If you are using Windows 2000 Professional (SP2 or later) or Windows XP Professional to install the patch remotely, the web pages will load very slowly unless you uncheck the Client for Microsoft Networks check box in the Windows NIC Properties window. Note For details on unchecking the Client for Microsoft Networks check box, refer to the "Configuring Windows 2000 Professional or XP Professional" section. –Because of known issues with certain versions of Netscape Navigator, use Microsoft Internet Explorer 6 (IE6) for remote installations. Step 2 In the IE browser Address field, type http://<external_NIC_address>:9488/www, where <external_NIC_address> is the external NIC address of the remote BBSM server. For example, type http://192.168.38.1:9488/www, and press Enter. The Enter Network Password window appears. Step 3 Enter your username and password (leave the Domain field blank) and click OK. The remote BBSM Dashboard appears. (You must have administrator privileges to log on.) Step 4 Install the first patch, Patch 5200, as follows: a. From the Dashboard, use the WEBpatch utility to install Patch 5200, Upgrade51to52Part0.exe. The patch usually takes about 10 minutes to install, including the automatic server reboot. Caution The Java 2 plug-in, version 1.3.1_03, must be installed on the computer you are using to transfer the patches, whether you are installing the patches remotely or directly on the BBSM server. · If you are installing patches using a remote computer, the Java plug-in must be installed on that remote computer. · If you are installing directly on the BBSM, the Java plug-in must be installed on your BBSM server. · You must use this version: other versions will fail. · If the plug-in is not installed already, click Go To Java Download Page, download the plug-in, and install it. You can also go to the BBSM 5.2 Software Download web page and download the plug-in from there. b. Verify that the patch was installed. From the WEBpatch BBSM Patch Log web page, view the logs for Patch 5200. If the "InstallPatch successful for" and "Reboot successful" logs appear, the patch installed successfully. (See Figure C-1.) Figure C-1 WEBpatch BBSM Patch Log Web Page showing Patch 5200 Step 5 Install the second patch, Patch 5201, as follows: a. From the Dashboard, use the WEBpatch utility to install Patch 5201, Upgrade51to52Part1.exe. The patch usually takes 15 minutes to install, including two automatic reboots that occur during the installation. b. Verify that the patch was installed, as explained in Step 4 b. Step 6 After installing the second patch, Patch 5201, using Microsoft Internet Explorer, delete cookies and other temporary Internet files on your computer, as follows: Caution You must perform this step before installing Patch 5202 for the installation to be successful. a. From the Microsoft IE browser, choose Tools > Internet Options. b. From the Temporary Internet files area, do the following: - Click Delete Cookies and click OK. - Click Delete Files, check the Delete all offline content check box, and click OK. - Click Settings, click the View Files button, and verify that there are no temporary Internet files. c. Close the Temporary Internet Files window, and then click OK twice to exit the Settings and Internet Options windows. d. Close Internet Explorer and reboot your computer. Step 7 Install the third patch, Patch 5202, as follows: Note If Windows 2000 SP3 is not installed on your BBSM server, Patch 5202 takes about 20 minutes to install, including the reboot. If you have installed SP3, it takes about 3 minutes to install, including the automatic reboot. a. From the Dashboard, use the WEBpatch utility to install Patch 5202, Upgrade51to52Part2.exe. b. Verify that the patch was installed, as explained in Step 4 b. Step 8 Install the fourth patch, Patch 5203, as follows: a. From the Dashboard, use the WEBpatch utility to install Patch 5203, Upgrade51to52Part3.exe. The patch usually takes about 10 minutes to install, including the automatic reboot. b. Verify that the patch was installed, as explained in Step 4 b. Step 9 If you upgraded from software release 5.0 to 5.1 and then to 5.2, delete the duplicate DLL file that is keeping clients from connecting to BBSM. Delete the GenericSwitchNoLinkStatus.DLL file in the c:\atcom\install\switches directory. Then restart BBSM. (Do not delete the latest version of this DLL file that resides in the c:\atcom\install directory.) If you do not have direct access to the BBSM server, you can delete this file remotely by installing Patch 5223 (BBSM5.0to5.2DLLPatch.exe), which is available for download at this Cisco website: http://www.cisco.com/pcgi-bin/tablebuild.pl/bbsm52 After you install this patch, the BBSM server reboots automatically.
	© 1992-2009 Cisco Systems, Inc. All rights reserved. Terms & Conditions \| Privacy Statement \| Cookie Policy \| Trademarks of Cisco Systems, Inc.