>TECHNICAL SUPPORT. SOFTWARE UPGRADE BULLETIN. Steps required to install PEPs on a High Availability Pair

Transcription

1 .. >TECHNICAL SUPPORT. SOFTWARE UPGRADE BULLETIN. Steps required to install PEPs on a High Availability Pair BULLETIN ID: , Rev 1 PUBLISHED: STATUS: Active REGION: APAC CALA EMEA GC NA PRIORITY: Critical TYPE: Bulletin Background: This bulletin is intended to enhance the steps required to install Service Updates "SU", individual "G" class (i.e. CP500S05GXXS) PEPs, and security (i.e. CPSECPEPXXXS) PEPs on a High Availability Pair that are documented in NTP NN "High Availability: Installation and Configuration". Additional steps may be required if installing a limited or restricted PEP. Please refrence individual read me files for additional steps. To ensure that the pair of CallPilot servers functions correctly, both CallPilot servers must be running the same PEPs and Service Updates (SUs). Due to the mirroring software, the mirrored drives cannot be accessed on the standby server. As a result, PEPs that impact the database or MMFS must be installed on the active CallPilot server. Overview of High Availability: In a High Availability configuration, a pair of peer CallPilot servers are used in the place of a single server. Both servers are connected to the same switch (Meridian 1 or Communication Server 1000 [CS 1000]) and they are configured so that one CallPilot server is active (that is, processing calls) and the other server is in standby mode. The standby server takes over if the active server fails (due to predefined failure conditions), or if the administrator decides to manually switch over to the standby server. Note: At the time of publication, the SU05 suite was the current GA solution. This bulletin is based on the SU05 suite. For subsequent SU0X suites, please refer to the individual HA readme file associated with that PEP package. Analysis: Prior to installing PEPs on any HA pair Nortel recommends that RAID be split per NTP NN "1005r Server Maintenance and Diagnostics", "RAID splitting". Nortel also recommends that a full system backup be obtained from one of the servers.

2 All steps below are applicable only on a configured HA pair. Note: In this procedure, CP1 is the active server and CP2 is the standby server. This process causes the servers to go out of service while the PEPs are installed. Nortel strongly recommends that you fully patch one server prior to proceeding to the second server. Recommendations: Installing PEPs on HA Pair 1. On CP1, do the following: 1.1. Launch the AutoStart Console Disable automatic failovers (stop monitoring). i. On AutoStart Console window, expand Domains > [AutoStart_Domain] > Resource Groups and then select CallPilot. ii. Click the Status tab. iii. Right-click Resource Groups > CallPilot. iv. From the shortcut menu, select Stop Monitoring. Result: On the Status tab, the Monitoring State turns to yellow and shows a status of Disabled. On the Domains pane, the Resource Groups > CallPilot changes to a green light with a black question mark. The automatic failover is disabled Take the resource group CallPilot offline (shutting down CallPilot). i. On the AutoStart Console window, select Domains > Resource Groups. ii. Right-click the CallPilot resource group. iii. From the shortcut menu, select the Take Offline option. Page: 2 of 11

3 iv. Wait until the Group State turns gray and shows Offline. This can take a few minutes. Note: Several warning messages may appear, click "OK" for all Wait for the resource group CallPilot to go offline Attach the mirror drives, drive E and drive F to CP1 so that the disks can be accessed from CP1. (Note: Repeat the steps i, ii, iii on drive E and drive F) i. In the AutoStart Console, select the [AutoStart_Domain] > Data Sources. Page: 3 of 11

4 ii. Right-click the drive you want to connect. iii. Select Attach Data Source to CP1 since this is the server currently being patched 1.6. Installing PEP or Service Update (For CallPilot Manager installation, please skip to step 1.7) Close all programs currently executed on the CallPilot server. (To include Auto Start Console) Launch the CPXXXXXXXXXS.msi to start the installation. Follow the instruction boxes to complete the installation of the PEP. Note: Several warning messages like the below screenshot may appear, click "OK" for all. Page: 4 of 11

5 Note: During the installation of CPXXXXXXXXXS you may see the AOS service start which will cause pop up windows to appear stating that CallPilot is booting.these windows can be closed upon appearance. Note: During the installation you may be prompted about manual steps required to finish installation of this PEP Wait for the installation to complete If prompted that a reboot of the server is required. Click [No] not to reboot Select the appropriate action from the list below: i. If you completed installing a Service Update, proceed to step 1.7. ii. If you completed installing a standalone PEP that requires a reboot, proceed to step 1.8. iii. If you were installing a standalone PEP that does not require a reboot and you need to install another PEP, proceed back to step iv. If you were installing a standalone PEP that does not require a reboot and this is the last PEP to be installed, proceed to step Installing CallPilot Manager on the CallPilot Server Disconnect all browsers currently connected to CallPilot Manager Run the CP500S0XGXXC.msi file. A message box may appear click "OK" i Click "next" to the welcome screen ii.select "I have read the readme.txt" only after reading the read me file and select "Next". Note: This will stop and restart the IIS server and related services, install/upgrade CallPilot Manager, register of CallPilot Manager in DMI Viewer During installing/upgrading of CallPilot Manager you will be prompted to install the new version of CallPilot Manager.Click [Install] to proceed. Note: Several warning messages may appear, click "OK" for all Wait for the installation to complete. Click "Finish" You will be prompted that a reboot of the server is required. Page: 5 of 11

6 Click [No] not to reboot Launch Auto start console and detach the mirror drives, drive E and drive F from CP1 (Note: Repeat the steps i, ii, iii on drive E and drive F) i. In the AutoStart Console, select the [AutoStart_Domain] > Data Sources. ii. Right-click the drive/data source. iii. Select Detach Data Source Restart the CP1 Server. Wait for the CP1 node to start If installing multiple PEPs, after CP1 restarts, proceed back to step 1.5, otherwise, proceed to step On CP2, do the following: 2.1. Launch the AutoStart Console Attach the mirror drives, drive E and drive F to CP2 so that the disks can be accessed from CP2. (Note: Repeat the steps i, ii, iii on drive E and drive F) i. In the AutoStart Console, select the [AutoStart_Domain] > Data Sources. ii. Right-click the drive you want to connect. iii. Select Attach Data Source to CP2 since this is the server currently being patched Installing PEP or Service Update (For CallPilot Manager installation, please skip to step 2.4) Close all programs currently executed on the CallPilot server. (To Include Auto start Console) Launch the CPXXXXXXXXXS.msi to start the installation. Note: Several warning messages may appear, click "OK" for all. Note: During the installation of CP50041SUXXS you may see the AOS service start which will cause pop up windows to appear stating that CallPilot is booting. These windows can be closed upon appearance. Note: During the installation you may be prompted about manual steps required to finish installation of this PEP Wait for the installation to complete If prompted that a reboot of the server is required. Click [No] not to reboot Select the appropriate action from the list below: i. If you completed installing a Service Update, proceed to step 2.4. ii. If you completed installing a standalone PEP that requires a reboot, proceed to step 2.5. iii. If you were installing a standalone PEP that does not require a reboot and you need to install another PEP, proceed back to step iv. If you were installing a standalone PEP that does not require a reboot and this is the last PEP to be installed, proceed to step Installing CallPilot Manager on the CallPilot Server. Page: 6 of 11

7 Disconnect all browsers currently connected to CallPilot Manager Run the CP500S0XGXXC.msi file. A message box may appear click "OK" i. Click "Next" at the welcome screen ii. Select "I have read the readme.txt" only after reading the read me file and select "Next". Note: This will stop and restart the IIS server and related services, install/upgrade CallPilot Manager, register of CallPilot Manager in DMI Viewer During installing/upgrading of CallPilot Manager you will be prompted to install the new version of CallPilot Manager. Click [Install] to proceed. Note: Several warning messages may appear, click "OK" for all Wait for the installation to complete. Select "Finish" You will be prompted that a reboot of the server is required. Click [No] not to reboot Launch the AutoStart Console and detach the mirror drives, drive E and drive F from CP2 (Note: Repeat the steps i, ii, iii on drive E and drive F) i. In the AutoStart Console, select the [AutoStart_Domain] > Data Sources. ii. Right-click the drive/data source. iii. Select Detach Data Source. Select "Yes" 2.6. Restart the CP2 Server. Wait for the CP2 node to start If installing multiple PEPs, after CP2 restarts, proceed back to step 2.2, otherwise, proceed to step On CP1, do the following: 3.1 Launch the AutoStart Console Start monitoring (to enable automatic failovers). i. On AutoStart Console window, expand Domains >[AutoStart_Domain] > Resource Groups and then select CallPilot. ii. Click the Status tab. iii. Right-click Resource Groups > CallPilot. iv. From the shortcut menu, select Monitor Resource Group. Result: On the Status tab, the Monitoring State turns to green and shows a status of Enabled Bring the resource group online (starting up CallPilot). ii. Right-click the CallPilot resource group. iii. From the shortcut menu, select the Bring Online option for the primary server iv. Wait until the Group State turns green and shows Online. This can take a few minutes. Both servers are now updated with the PEPs. NOTE: If PEP requires that Configuration Wizard be ran ( Service Updates), please follow the steps in the next section. Page: 7 of 11

8 Required Actions: Procedure to run Configuration Wizard on HA. (Requires resource group to be online at the start of the procedure) Note: The steps below should be used to reprogram the DSP's. Use NN High Availability: Installation and Configuration, section "CallPilot Configuration Wizard" for details to change CallPilot server configuration. On CP1 (the active High Availability server) do the following: 1. Ensure the dongle is plugged into CP1. If the dongle is not on CP1, move it to CP1 and wait for three minutes.for more information about the dongle, see 1005r Server Hardware Installation (NN ). 2. Launch the AutoStart Console. 3. Stop monitoring on the CallPilot resource group. i On AutoStart Console window, expand Domains > [AutoStart_Domain] > Resource Groups and then select CallPilot. ii. Right-click Resource Groups > CallPilot. iii.from the shortcut menu, select Stop Monitoring. Result: On the Status tab, the Monitoring State turns to yellow and shows a status of Disabled. On the Domains pane, the Resource Groups > CallPilot changes to a green light with a black question mark. The automatic failover is disabled. 4. Run the Fault Database Compiler. i. In the Start menu select Start > Run ii. Type "D:\Nortel\bin\nbfltdbcm.exe D:\Nortel\Mpcx\data" (without quotes) in Run dialog. iii.press Ok. Result: The system starts the compilation process and the Fault Management Compiler window appears. Wait until compilation is complete. Note: Compiler window will disappear automatically. 5. Log on to CallPilot Manager on CP1 and start the Configuration Wizard. Result: The Configuration Wizard Welcome screen appears. 6. Click Next on Welcome screen. Result: Configuration Mode screen appears. Page: 8 of 11

9 7. Select the CallPilot System Configuration (Standard Mode) option and then click Next. Result: The Keycode and serial number screen appears. 8. Verify your Serial number and Keycode and then click Next. Result: The Feature Verification screen appears. 9. Ensure that the details on the Feature Verification screen match your expectations and click Next. Result: The Server Information screen appears. 10. Verify the information on the Server Information screen and then click Next. Result: The Password Information screen appears. 11. Select the Leave the password unchanged option. Click Next. Result: The Multimedia Allocation screen appears. 12. Verify the number of MPB boards and, if applicable, DSP cards. Click Next. Result: The Switch Information screen appears. 13. Ensure that the following settings are correct: i the switch type and the switch IP address. ii.the number of channels and channels configuration Click Next. Result: The CDN Information screen appears. 14. Verify the CDN configuration. Click Next. Result: The Language Source Directory screen appears. 15. Select the Skip Language Installation option. Click Next. Result: The CallPilot Local Area Network Interface screen appears. 16. Verify the information on the CallPilot Local Area Network Interface page. Do not change any settings. Ensure that the High Availability mode check box is selected and that the HB1, HB2, and MIRROR information is correct. Click Next. Result: The Ready to Configure screen appears. 17. Click Finish. i. Click "Ok" to the message box that states "Please disable AutoStart Monitoring" Result: A dialog box prompts you to confirm the configuration. 18. Click OK to configure CallPilot. ( Applying your changes will take your CallPilot Server out of Service) Result: The configuration is applied to the server. This task can take from 5 to 10 minutes to complete. The Configuration Wizard displays progress information. Page: 9 of 11

10 After the configuration is applied to the server, a dialog box reminds you to restart the server for the configuration to take effect. 19. Click OK to dismiss the dialog box. Result: The system returns you to the main CallPilot Manager screen. 20. Logout CallPilot Manager and close the Web browser. 21. Perform a manual failover. i. On the AutoStart Console window, expand Domains > [AutoStart_Domain] > Resource Groups and then select CallPilot. ii.right-click Resource Groups > CallPilot. iii.on the shortcut menu, select Relocate Resource Group, and then select the <standby CallPilot server> (CP2) iv.click Yes on Confirm Relocated of Resource Group dialog box Result: The failover starts in seconds. It takes more than 10 minutes to finish the failover to the standby server if the CallPilot Diagnostic Tools are enabled, or less than 5 minutes if the CallPilot Diagnostic Tools are disabled. (Start > Programs > CallPilot > System Utilities > Diagnostic Tools).This action stops the CallPilot services on the active server. The CallPilot resource group is automatically brought online on the standby High Availability server (CP2). 22. After the CallPilot resource group is online on CP2, restart the CP1 server. On CP2, 1. Move the dongle to CP2.and wait for three minutes. For more information about the dongle, see 1005r Server Hardware Installation (NN ). 2. Launch the AutoStart Console on CP2 server. 3. Wait until node CP1 and both drve and drvf are green/online in the AutoStart Console. 4. Run the Fault Database Compiler. i. In the Start menu select Start > Run ii. Type "D:\Nortel\bin\nbfltdbcm.exe D:\Nortel\Mpcx\data" (without quotes) in Run dialog. iii. press Ok. Result: The system starts the compilation process and the Fault Management Compiler window appears. Wait until compilation is complete. Note: Compiler window will disappear automatically. 5. Log on to CallPilot Manager on CP2 and start the Configuration Wizard. Result: The Configuration Wizard: Welcome screen appears. 6. Follow steps 6 through 20 that were previously performed on CP1. 7. Perform a manual failover. i. On the AutoStart Console window, expand Domains > [AutoStart_Domain] > Resource Groups and then select CallPilot. ii. Right-click Resource Groups > CallPilot. iii. On the shortcut menu, select Relocate Resource Group, and then select the <standby CallPilot server> (CP1) iv. Click Yes on Confirm Relocated of Resource Group dialog box Result: The CallPilot resource group is automatically brought online on the standby High Availability server (CP1). Page: 10 of 11

11 8. After the CallPilot resource group is online on CP1, restart the CP2 server. ( Move dongle to CP1) On CP1, do the following: 1. Launch the AutoStart Console. 2. Wait until node CP2 and both drve and drvf are online/green in the AutoStart Console. 3. Start monitoring (to enable automatic failovers): i. On the AutoStart Console window, expand Domains > [AutoStart_Domain] > Resource Groups and then select CallPilot. ii.right-click Resource Groups > CallPilot. iii. From the shortcut menu, select Monitor Resource Group. Result: On Status tab, the Monitoring State turns to green and shows a status of Enabled. On the Domains pane, the Resource Groups > CallPilot changes to green.the automatic failover is enabled. Result: Both servers are updated with the PEPs. Attachments: There are no attachments for this bulletin Products and Releases: The information in this bulletin is intended to be used with the following products and associated releases: PRODUCT CallPilot-CallPilot-CallPilot 1005r HA 5.0 CallPilot-CallPilot-CallPilot 1005r HA RELEASE To view the most recent version of this bulletin, access technical documentation, search our knowledge base, or to contact a Technical Support Representative, please visit Nortel Technical Support on the web at: You may also sign up to receive automatic alerts when new bulletins are published. REFERENCE: PRE-REQUIRED PATCH: PATCH ID: FIXED RELEASE: Release 5.0 Copyright 2009 Nortel Networks. All rights reserved. Information in this document is subject to change without notice. Nortel assumes no responsibility for any errors that may appear in this document. The information in this document is proprietary to Nortel Networks. Nortel recommends any maintenance activities, such as those outlined in this bulletin, be completed during a local maintenance window. Nortel, the Nortel logo, and the Globemark design are trademarks of Nortel Networks. All other trademarks are the property of their respective owners. Page: 11 of 11