Application Server 5300 Nortel AS 5300 Installation Release: 1.0 Document Revision: 01.04 www.nortel.com NN42040-300 .
Application Server 5300 Release: 1.0 Publication: NN42040-300 Document release date: 4 November 2008 Copyright © 2007-2008 Nortel Networks All Rights Reserved. Printed in Canada LEGAL NOTICE While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing, NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED.
. Contents New in this release Features 7 Other changes 7 7 Introduction 9 Deployment options 9 Installation overview Installation times 11 12 Installation preparation 15 Unpack the materials 15 Customer-specific information 15 Installation Planning sheet 17 Hardware installation and configuration 21 Hardware overview 22 Mount the hardware 23 Mounting the server 23 Connect the hardware 24 Networking overview 27 Network Time Protocol 29 Hardware configuration 30 Resetting the planar BIOS
Configuring accounts and passwords 51 Configuring preconfigured accounts and passwords Configuring a system for individual accounts 53 Reinstalling platform software 55 52 Oracle database software installation 59 Oracle database software installation 59 Installing Oracle database software 60 AS 5300 software deployment 63 Core components 63 Staging files 64 Installation properties file 65 AS 5300 initial software deployment 66 Downloading the MCP load software 68 Preparing the initial load for depl
Installing the firmware upgrades 102 Installing BIOS firmware upgrades 102 Installing Base Management Controller (BMC) firmware upgrades 103 Installing diagnostics firmware upgrades 104 Installing RSA-II card firmware upgrades 105 Installing NIC firmware upgrades 106 Installing hard drive firmware upgrades 106 Installing ServeRAID firmware upgrades 107 Multimedia PC Client upgrade 109 Upgrading the ASU load 109 Upgrading the Multimedia PC Client installer executable 110 Downgrades 111 Downgrade system
Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
. New in this release The following sections detail what’s new in NN42040-300 Installation for Nortel Application Server (AS) 5300 Release 1.0. Features This section details the changes in Nortel Application Server (AS) 5300 Release 1.0. For an overview of the AS 5300 solution, see Nortel AS 5300 Overview ((NN42040-100)) . Other changes This document is new for AS 5300 Release 1.0. Revision history November 04 2008 Standard 01.04.
New in this release Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
. Introduction This document provides information about the installation of the IBM x3550 servers for Nortel Application Server (AS) 5300. It describes the installation of the physical hardware, platform software, and database software, as well as information about Multimedia Communication Protocol (MCP) software deployment, patches, Maintenance Releases, firmware updates, and system downgrades.
Introduction For medium redundant systems, the minimum baseline configuration for the AS 5300 infrastructure includes four (4) IBM x3550 servers with the following mapping to software modules: • • two (2) servers with Session Manager and IP Client Manager two (2) servers with System Manager, Database Manager, and Provisioning Manager For more information about the appropriate system deployment for your installation, see Nortel AS 5300 Planning and Engineering (NN42040-200).
. Installation overview This chapter describes the steps required to install AS 5300 servers and the approximate time needed to complete each step. Installation overview procedures This diagram shows the steps required to complete AS 5300 installation. Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
Installation overview Installation overview navigation • "Installation times" (page 12) Installation times This section describes the approximate time required for each major step of the AS 5300 installation process. Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
Installation times Table 1 Installation preparation Installation step Approximate time required to complete Unpacking the hardware 10 minutes Table 2 Hardware installation and configuration Installation step Approximate time required to complete Mounting the hardware 20 minutes Connecting the hardware 20 minutes Resetting the planar BIOS 5 minutes Resetting the ServeRAID BIOS 5 minutes Configuring the RSA-II card 10 minutes Configuring the planar BIOS 5 minutes Configuring the ServeRAID BI
Installation overview Table 5 AS 5300 software deployment (cont’d.) Installation step Approximate time required to complete Deploying the initial software load 45–50 minutes Updating the licensekey 10 minutes Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
. Installation preparation This section describes the preparation of materials and hardware required for installing the AS 5300 server. Navigation • • "Unpack the materials" (page 15) "Customer-specific information" (page 15) Unpack the materials Before installing the server, verify that all of the necessary components required for installation are on-site.
Installation preparation This sheet is located in the chapter titled "Installation Planning sheet" (page 17). Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
. Installation Planning sheet This section contains the Installation Planning Sheet. Use the Installation Planning sheet to compile the information required for installing an AS 5300 server. Print and complete an Installation Planning sheet for each server being installed.
Installation Planning sheet Service VLAN Machine Logical Address All 10.10.0.5 Service VLAN Default Gateway All 10.10.0.1 Service VLAN Network Mask All 255.255.0.0 Maintenance VLAN ID All 1265 Maintenance VLAN Machine Logical Address All 192.168.2.5 Maintenance VLAN Default Gateway All 192.168.2.1 Maintenance VLAN Network Mask All 255.255.255.0 RSA-II Card IP Address All 192.168.3.5 RSA-II Card Default Gateway All 192.168.3.1 RSA-II Card Network Mask All 255.255.255.
Customer-specific information ntsecadm All QWEpoi43@! ntbackup All QWEpoi43@! ntdbadm All QWEpoi43@! IAO Single Account Information, if used (not required for restore reinstalls) IAO User Id All iaouser IAO Password All QWEpoi43@! GRUB Bootloader All QWEpoi12#$ System Account Initial passwords (required for all installs) root All QWEpoi12#$ ntossadm All QWEpoi12#$ nortelrps All QWEpoi12#$ Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.
Installation Planning sheet Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
. Hardware installation and configuration This section describes the procedures for installing and configuring the AS 5300 server hardware. Prerequisites For more information about basic hardware installation, see IBM x3550 Installation Guide. Hardware installation and configuration procedures This work flow diagram shows the steps required to install and configure the AS 5300 hardware. Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.
Hardware installation and configuration Hardware installation and configuration navigation • "Hardware overview" (page 22) • "Mount the hardware" (page 23) • "Connect the hardware" (page 24) • "Networking overview" (page 27) • "Hardware configuration" (page 30) Hardware overview The AS 5300 product uses the IBM x3550 server for its core server platforms. For more information about the hardware characteristics of the IBM x3550 server, see Table 6 "IBM x3550 hardware characteristics" (page 22).
Mount the hardware 23 Table 6 IBM x3550 hardware characteristics (cont’d.) Item Description Server identification x3550, Model 7978 AC1 CPU 2 x Quad-Core Intel Xeon processor E5420, 2.5GHz, 12 MB L2 cache, 1333MHz FSB, 80w Memory 8 GB PC2-5300 CL5 ECC DDR2 Chipkill FB DIMM 667MHz Disk 2 x 73 GB 3.5-inch SAS, 15000 RPM, hot swap; RAID-1 mirrored using IBM ServeRAID 8k-l SAS controller (hardware RAID-1) AC power 2 x 670W A/C Power Supply (redundant, hot-swap); 2.
Hardware installation and configuration 3 Securely install the rail kit and then slide the server into place. 4 Ensure the server is supported in the rear by the rail kit. 5 Bolt the front of the server to the front of the rail kit. --End-- Connect the hardware For more information about the front and rear panels of the AS 5300 server, see Figure 1 "Front panel of the AS 5300 server" (page 25) and Figure 2 "Rear panel of the AS 5300 server" (page 25) .
Connect the hardware 25 Figure 1 Front panel of the AS 5300 server Figure 2 Rear panel of the AS 5300 server Ethernet 1 and Ethernet 2 are the main Network Interface Card (NIC) ports that carry traffic for the primary application of the server. These ports are configured to run in redundant mode with one port active and the other on standby, so connect them to a redundant host switch.
Hardware installation and configuration port is attached to another computer, such as a Windows-based computer, a program such as HyperTerminal can be used to establish a login session over the serial connection. COM1 is the only serial port supported for AS 5300 systems. For more information about the serial port pinout for COM1, see Table 7 "COM 1 serial port pinout" (page 26).
Networking overview 27 Attach the two redundant AC (Alternating Current) power modules to redundant AC power sources, as required by industry standards. Networking overview The standard networking configuration for the AS 5300 system is a Dual-VLAN configuration.
Hardware installation and configuration Figure 3 Typical Dual-VLAN configuration The server maintains the use of the kernel channel bonding module to implement the bond0 logical interface (enslaving eth0 and eth1 in active or standby mode). A second kernel module, the 8021q VLAN module, implements VLAN capabilities on top of the logical bond0 interface. This module implements one logical interface for each VLAN, where each is logically placed on top of the bond0 interface.
Networking overview 29 VLAN interfaces are named according to the following syntax: . The AS 5300 server defines the VLAN interfaces to be hosted by the logical bond0 interface. Figure 3 "Typical Dual-VLAN configuration" (page 28) shows a VLAN interface named bond0.170, which belongs to the VLAN with ID 170, and the VLAN interface bond0.1265, which belongs to the VLAN with ID 1265.
Hardware installation and configuration can have their time source server configured to use the System Managers, as IPsec is already configured between System Manager servers and non-System Manager servers. For more information about security for Network Time Protocol, see Nortel AS 5300 Security (NN42040-601). Hardware configuration This section contains information and procedures for configuring the Basic Input Output System (BIOS) and RSA-II card on the AS 5300 server.
Hardware configuration 31 Hardware configuration navigation • "Resetting the planar BIOS and RSA-II card to factory defaults" (page 32) • • "Resetting the ServeRAID BIOS to factory defaults" (page 33) "Configuring the RSA-II card" (page 35) Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
Hardware installation and configuration • • "Configuring the planar BIOS" (page 36) "Configuring the ServeRAID BIOS" (page 38) Resetting the planar BIOS and RSA-II card to factory defaults When you install a new AS 5300 server (new installation or replacement of a failed server), you must configure the BIOS settings of the server to the standard product supported configuration.
Hardware configuration 33 with the correct memory configuration but not recognized by the system. If this happens, contact your next level of support before proceeding. 3 Select Advanced Setup. 4 Select RSA-II Settings. 5 Select Restore RSA II Defaults. Network settings for the RSA-II card are restored to factory defaults. Any existing network connections to the RSA-II Ethernet interface are disconnected and no further connections can be made until network settings are reconfigured.
Hardware installation and configuration WARNING The resetting of the ServeRAID BIOS to factory defaults includes the destruction of all currently defined RAID arrays. This results in the deletion of all data on the disk drives and requires reinstallation of all server software. Procedure Steps Step Action 1 Reboot the system. The system displays the following message: Press CTRL-A for IBM ServeRAID Configuration Utility 2 Press CTRL+A . The IBM ServerRAID Configuration Utility screen appears.
Hardware configuration 35 11 Press F6 to reset to factory defaults. 12 Select Yes to reset the defaults. 13 Press Esc until you return to the IBM ServerRAID Configuration Utility screen. 14 Select Yes to save changes made. 15 Press Esc to exit ServeRAID setup. 16 Select Yes to save the changes and exit. --End-- Configuring the RSA-II card Use this procedure to configure nonsecure access for the RSA-II card.
Hardware installation and configuration 9 Highlight OS USB Selection and use the left and right arrow keys to select Linux OS. 10 Select Save Values and Reboot RSA II. 11 When prompted, press Enter to confirm. The BIOS is unresponsive for approximately 20 seconds while the RSA-II card reboots. When the card has finished rebooting, the following message appears: RSA-II Settings Saved 12 Press Enter. Ignore the prompt to reset the RSA-II card.
Hardware configuration Procedure Steps Step Action 1 Reboot the server and press F1 to access the planar BIOS configuration utility. The following steps ensure that the Power-on password is not configured by deleting all existing Power-on passwords. 2 Select System Security > Power-on Password. 3 Highlight Delete Power-on Password and press Enter. The following message appears: Any existing power-on password will be deleted. 4 Press Enter to confirm.
Hardware installation and configuration Select Exit Setup and select Yes when prompted for confirmation. 25 --End-- Configuring the ServeRAID BIOS Use this procedure to configure the ServeRAID BIOS. Prerequisites • The ServeRAID BIOS has been reset to the factory default settings. Procedure Steps Step Action 1 Reboot the server. The server restarts and the following message displays: Press CTRL-A for IBM ServeRAID Configuration Utility 2 Press CTRL+A.
Hardware configuration 39 The Array Properties window appears. 15 In the Array Type sub-window, select RAID 1(Mirror). This cursor moves to Array Label. 16 For Array Label, enter mcp-raid1 and press Enter. The cursor moves to the Array Size line. 17 Press Enter to confirm the disk size (do not modify it), then press Enter to accept the size unit value of GB. The cursor moves to Create RAID via and highlights Quick Init. 18 Press Enter to select Quick Init. 19 Press Enter to select Done.
Hardware installation and configuration Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
. Platform software installation This section describes how to install the AS 5300 platform software. The platform software consists of the underlying Linux kernel, which is the base-level software packages required for a Linux-based operating system, and the customized Nortel software, scripts, and server configurations that prepare the system for an AS 5300 environment. SIP core AS 5300 servers require the platform software installation.
Platform software installation Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
Hardware configuration Platform software installation navigation • "Starting the Linux operating system installation" (page 44) • "Configuring the networking, serial console redirection, and time zone settings" (page 45) • • • • "Configuring the NTP, Syslog, and Audit Daemon settings" (page 47) "Configuring the BIOS hardware clock" (page 50) "Configuring accounts and passwords" (page 51) "Reinstalling platform software" (page 55) Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.
Platform software installation Starting the Linux operating system installation Use this procedure to initiate the Linux operating system installation process. This phase of the installation process accomplishes the following objectives: • • • displays the licensing information gathers the hardware and system information presents the option to restore a remote platform backup file Prerequisites • • • Core Linux 11.0.
Configuring the networking, serial console redirection, and time zone settings 45 If the hardware verification fails, an error message displays, the installation aborts, and the server reboots. Otherwise, the following message appears: Press ENTER to Continue Press Enter. 5 The system displays the following message: Would you like to retrieve a platform backup file from a remote server? 6 If you are restoring a platform backup file, reply Y and proceed to "Reinstalling platform software" (page 55).
Platform software installation 2 Enter the VLAN number associated with the Service network. This number must match the VLAN ID associated with the Service network throughout the entire system configuration. The system displays the following prompt: Enter MACHINE logical IP address for VLAN : 3 Enter the machine logical IP address for the Service network.
Configuring the NTP, Syslog, and Audit Daemon settings 47 Disable the serial console redirection by selecting option 3 and proceed to step 12. OR Enable system console redirection by selecting option 1. The system displays the following prompt: Please select the speed of the serial port: 11 From the list of port speed options, select the speed that best matches the speed used on the equipment attached to the RS-232 serial cable.
Platform software installation Prerequisites • You have completed the steps described in "Configuring the networking, serial console redirection, and time zone settings" (page 45). • • External time source IP address(es), if applicable. Remote syslog server IP address, if applicable. Procedure Steps Step Action 1 During the Linux installation process, the system displays the following prompt: Please indicate the Clock Source function of this server: 2 Select the clock source. If you are...
Configuring the Primary (EMS1) and Secondary (EMS2) clock source servers 49 Select Y to enable system audit. Enabling the system audit might impact system performance. The system displays a validation summary of the current configuration settings. Do one of the following: 7 Type Y to confirm the configuration settings and continue with the Linux installation process. OR Type N to go back through the individual configuration steps and make changes.
Platform software installation If you are configuring the Secondary (EMS2) server, enter the machine logical address of the Primary (EMS1) server. --End-- Configuring the clock source for all other SIP core servers Use this procedure to configure the clock source for all other SIP core servers. Prerequisites • You selected option 3 at the Clock Source function prompt.
Configuring accounts and passwords 51 The closer that the starting system time from the BIOS is to the actual time reference provided by these clock sources, the quicker the NTP protocol converges with these clock sources. Therefore, set the server BIOS clock to a value that is close to the current local time. Accuracy to within several minutes provides a reasonable starting point for an effective NTP convergence, but keeping it to within a minute is ideal.
Platform software installation The installer presents the option to configure preconfigured accounts or an individual account. You must select one or the other. Each option includes the configuration of passwords for the mandatory system accounts. User account passwords can be recovered from a backup file but passwords for system accounts cannot be recovered. The installer prompts for the system account passwords.
Configuring accounts and passwords 53 Reply Y to accept the account method confirmation. OR Reply N to go back to the User Accounts screen and change selections. Once the account method is confirmed, the installer displays the prompt to create the passwords. The password limitations and requirements appear on-screen. 5 If you selected the option to use a shared password, the installer prompts you to create the shared password.
Platform software installation Configuring a system for individual accounts Procedure Steps Step Action 1 During the Linux operating system installation process, the system displays the following prompt: Would you like to create pre-configured accounts for this system? (Y/N) [N]? 2 Reply N to create an individual account. (If you reply Y to this prompt, the system configures preconfigured accounts.) The installer displays the SSA (System Security Administrator) account configuration screen.
Reinstalling platform software 55 Configuring accounts and passwords job aid Table 8 List of pre-configured accounts Account name Description ntappadm This account is used for SIP core server software administration. ntsysadm This account is used for system administration. ntsecadm This account is used for security administration. ntbackup This account is used for backup and restore administration. ntdbadm This account is used for database administration.
Platform software installation Prerequisites • You have completed the steps in "Starting the Linux operating system installation" (page 44) and replied Y to the option to restore remote platform data. • • The remote server must have Secure FTP (SFTP) enabled. • You must know the networking properties for the remote backup server, such as the VLAN ID and IP address. • For more information about installing Linux Maintenance Releases, see "Applying the Linux Maintenance Release " (page 92).
Reinstalling platform software 57 MCP Backup Tar Files 1) mcpPlatform.as5300-micro-s1.yyyy.mm.dd.hh.mm. tar 2) mcpPlatform.as5300-micro-s2.yyyy.mm.dd.hh.mm. tar 0) Cancel remote TAR file selection 10 Do one of the following: From the MCP Backup Tar Files list, select the file to restore. OR Select 0 to cancel remote retrieval and return to remote retrieval prompt. Attention: Backup data is specific to each server. Only restore platform data to the server from which the backup data originated.
Platform software installation The Date and Time is displayed. 13 Do one of the following: Enter Y to accept the configuration. OR Enter N to change the BIOS hardware clock. After the configuration is accepted, the user accounts display. 14 Press Enter to continue.
. Oracle database software installation This chapter contains information and procedures for installing the Oracle database software. Oracle is installed on the EMS1 and EMS2 servers. Navigation • "Oracle database software installation" (page 59) Oracle database software installation This section provides the procedures for installing the Oracle database software on an AS 5300 server.
Oracle database software installation Navigation • • "Installing Oracle database software" (page 60) For more information about installing Oracle Maintenance Releases, see "Applying the Oracle Maintenance Release" (page 95). Installing Oracle database software Use this procedure to install the Oracle database software on the EMS1 and EMS2 servers. The Oracle software is provided on an installation CD or delivered by Electronic Software Delivery (ESD). Prerequisites • • At least 6.
Oracle database software installation 61 Procedure Steps Step Action 1 Place the first disc containing the Oracle installation files in the CD-ROM drive of the database server. 2 Log on to the server as the SSA role (ntsysadm). 3 Change user permissions to root: su - root 4 Change directory: cd /usr/local/bin 5 Copy the installation files from the CD to the hard drive, changing the CD as prompted: ./mcpCopyFromCD.
Oracle database software installation Otherwise, you have completed installation. --End-- Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
. AS 5300 software deployment This chapter contains information and procedures about AS 5300 software deployment.
AS 5300 software deployment Staging files Staging files are used to configure the initial system. The AS 5300 software load includes two sets of staging files consisting of an import file and a tags file. Two sets of staging files are defined based on the number of core servers in the configuration. The following sections describe these sets.
Core components 65 4-server staging files (medium system) 4-server staging configurations consist of a redundant installation where all core components are distributed across four servers. A 4-server staging configuration uses he following files: • • • installprops.txt StagingFedPBX4Server.tags StagingFedPBX4Server.
AS 5300 software deployment Attention: For increased security, do not store the parameters for db.username and db.password in the installprops.txt file. If these parameters are not specified in the installprops.txt file, the mcpInstall.pl script prompts for them. This information is then encrypted and written to another file that is used by all of the scripts in the /var/mcp/install directory. For new system installations, the db.
AS 5300 initial software deployment 67 AS 5300 initial software deployment navigation • • • "Downloading the MCP load software" (page 68) "Preparing the initial load for deployment" (page 68) "Deploying the initial software load" (page 70) Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
AS 5300 software deployment • • "Starting the System Management Console" (page 71) "Updating the licensekey" (page 71) Downloading the MCP load software Install the MCP load software on the Primary Element Management server (EMS1). Prerequisites • • You require the CD/DVD containing the MCP load software. You must be assigned the AA role (ntappadm). Procedure Steps Step Action 1 Log on to the Primary Element Management server as the AA role (ntappadm).
AS 5300 initial software deployment 69 The system displays a list of loads and prompts for a load selection. 3 Select the load for installation. The system displays a list of staging files and prompts for user selection: Please enter number [1 to 10] of selection: 4 From the list of staging files, enter the number of the staging file to use. Attention: Select either StagingFedPBX2Server or StagingFedPBX4Server for AS 5300 deployments.
AS 5300 software deployment Deploying the initial software load Use this procedure to deploy the initial AS 5300 software load. Prerequisites • You must be assigned the AA role (ntappadm). Procedure Steps Step Action 1 Log on to the Element Management server as the AA role (ntappadm). 2 Change directory: cd /var/mcp/install 3 Deploy the system by issuing the following command: ./mcpInstall.
AS 5300 initial software deployment 71 For more information, see Nortel AS 5300 Planning and Engineering (NN42040-200). Starting the System Management Console The System Management Console uses Java Web Start technology and is launched from a Web browser. Prerequisites • The MCP software load has been deployed successfully. Procedure Steps Step Action 1 Open a Web browser and enter the following URL: https://:12121 The System Management Console starts.
AS 5300 software deployment 7 If you do not see the new licensekey after applying, click Refresh. After the licensekey is updated, you can deploy and start the Network Elements. For more information about deploying and starting Network Elements, see Nortel AS 5300 Configuration (NN42040-500). --End-- Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
. Patches This section contains procedures for updating and maintaining the AS 5300 system through the installation of software patches and firmware updates. Use patches to update the core MCP software load. Patches are available through Nortel’s Regional Patch Selector service (RPS) or from the Nortel Web site. Updates to the Oracle database and Linux operating system software are performed using Maintenance Releases.
Patches MCP core software load patch installation navigation • • • • "Obtaining the patches" (page 74) "Patching the database schemas and System Manager" (page 78) "Patching the Network Elements" (page 79) "Patching the Audio Codes gateway" (page 82) Obtaining the patches Obtain the MCP patches from the Nortel support site (http://support.nor tel.com/ ) or have them pushed to the site using Nortel’s Regional Patch Selector (RPS) service.
MCP core software load patch installation 75 Always download the most recent patch. Patches are cumulative, that is, each new patch contains all of the updates from the previous patches. 2 Confirm the name of the downloaded patch file is the same as the patch name in the Release Notes. File names might be modified during download when using certain Internet browsers. If there is a difference, rename the downloaded file to the patch name stated in the Release Notes.
Patches Unix Path Location /patches/MCP/MCP_11.0.0.1_2008-01-05-2156.patch Using an FTP client, download the patch from the gsds.ca.nortel.com site. 4 The user ID is gsduser and the password is 4U2get!n. The path to the patch is the path returned by the Getpath web tool without the /patches prefix.
MCP core software load patch installation 77 When you enable the RPS, an inform file is created in the var/mcp/dropbox directory. When a patch has been successfully received and prepared for application by the System Manager, a minor alarm is raised. The alarm indicates the name of the patch that is ready for application. 4 Open the Alarm Browser window to view the patch details. --End-- Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.
Patches Enabling patch delivery for non-Regional Patch Selector (RPS) sites Use this procedure to create an inform file for RPS patch notifications. This procedure is intended for sites that are not registered with Nortel’s RPS service. Procedure Steps Step Action 1 Launch the System Management console. 2 From the navigation menu, select Network Data and Mtc > Regional Patch Selector. The Regional Patch Selector window appears.
MCP core software load patch installation 79 Procedure Steps Step Action 1 Log on to the primary System Manager as the AA role (ntappadm) using SSH. 2 Change directory: cd /var/mcp/install 3 Run the patching script: ./mcpPatch.pl The progress of the patching process displays. The database is patched first, followed by the System Manager. When the database and System Manager are patched, the System Manager restarts. 4 Log on to the MCP System Management Console.
Patches Network Element Client impact Subscriber impact is transferred to the Accounting Manager and no information is lost. Provisioning Managers The Provisioning Manager is not deployed with redundant instances. There is no user access to the Provisioning Client during upgrade.
MCP core software load patch installation 81 Prerequisites • • Network Elements are configured on the system. • You must be assigned to the AA role (ntappadm). You understand the service issues associated with patching Network Elements. Procedure Steps Step Action 1 From the System Management console menu, select Tools > Patch/MR Manager. The Patch/MR Manager window appears. 2 From the Load or Patch list menu, choose the load patch being applied. The Load Manager window appears.
Patches 6 Repeat steps 3 to 5 for each Network Element displayed in the Patch/MR navigation tree. The Instance window for the Network Element shows one or more instances. If there is one instance, it is in the active state. Additional instances, if present, are in the offline state. Network Elements supporting Cold Standby or Hot Standby mode display their supported standby mode. The load name listed for each instance is the patched load.
MCP core software load patch installation 83 Prerequisites • The database schemas and System Manager have been patched. Procedure Steps Step Action 1 The procedure for patching the Audio Codes gateway load using the MCP core software load patch is the same as upgrading the Audio Codes gateway using a Maintenance Release. See "Upgrading the AudioCodes gateway" (page 92). --End-- Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.
Patches Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
. Maintenance Releases This section describes information and procedures about installing Maintenance Releases. Use Maintenance Releases to update the Linux operating system, Oracle database software, and the core MCP software load. Maintenance Releases are delivered on CD/DVD, Regional Patch Selector service (RPS), or downloaded from the Nortel Technical Support Web site. Platform Maintenance Releases are delivered on CD/DVD only.
Maintenance Releases MCP core software load Maintenance Release installation Navigation • "Transferring the Maintenance Release files to System Manager" (page 87) • "Upgrading the database schemas and System Manager" (page 89) Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
MCP core software load Maintenance Release installation • • 87 "Upgrading the Network Elements" (page 90) "Upgrading the AudioCodes gateway" (page 92) Transferring the Maintenance Release files to System Manager Delivery options for the MCP core software load Maintenance Release are as follows: • • CD/DVD containing the Maintenance Release files Electronic Software Delivery (ESD) The following procedures describe how to transfer the Maintenance Release files to System Manager for each delivery option
Maintenance Releases rm –Rf Attention: Use extreme caution when using rm -Rf commands. Entering a typo can cause an entire file system to be removed without confirmation if you have the proper user privileges. For example, entering a command such as rm -Rf / mcp/loads (with an extra space after the first forward slash) can remove the entire directory tree. 7 Exit from the SSH sessions for the SSA role (ntsysadm) and AA role (ntappadm) using Exit.
MCP core software load Maintenance Release installation 89 sudo ./mcpCopyFromESD.pl -m manifest-online Copy the ASU files. 8 sudo ./mcpCopyFromESD.pl -m manifest-asu-pc Remove the ISO image file from the file system. 9 rm /var/mcp/esd_files/ Delete older MCP loads. 10 Nortel recommends to only keep the current MCP software load and the load that the system will be upgraded to in the /var/mcp/loads directory to free up disk space.
Maintenance Releases ./mcpUpgradeMR.pl When prompted, select the MR load from the list. 4 The database is upgraded first, followed by the System Manager. The upgrade progress outputs to the screen. Start the MCP System Management Console. 5 --End-- Upgrading the Network Elements Use this procedure to apply the Maintenance Release upgrades to the Network Elements. Attention: Upgrade the Network Elements in the specified order. Prerequisites • • A network element is configured.
MCP core software load Maintenance Release installation 4 Select the Network Element to be patched. 5 On the maintenance panel, click the Upgrade button. 91 The NE Maintenance Panel window appears to monitor the patch installation. 6 Repeat steps 3 to 5 for each Network Element displayed in the Patch/MR navigation tree. The Instance window for the Network Element shows one or more instances. If there is one instance, it is in the active state.
Maintenance Releases The load name listed for each instance is the patched load. --End-- Upgrading the AudioCodes gateway Use this procedure to apply the Maintenance Release upgrades to the AudioCodes gateway. The only supported method for the AS5300 AudioCodes deployment of loads and upgrades must be done by the SunFire V-215 EMS servers. Attention: The AudioCodes gateway does not have the capability to switch its activity to another instance.
Applying the Linux Maintenance Release 93 Procedure Steps Step Action 1 Load the CD containing the MCP Core Linux platform Maintenance Release into the CD-ROM tray of the primary System Manager. 2 Log on to the System Manager as the ntsysgrp role (ntsysadm) using SSH. 3 Change to root user: su - 4 Change directory: cd /var/mcp/os/install/images (The patching script creates this directory. Therefore, this directory will not exist on systems that have not been patched.
Maintenance Releases Attention: This is a major package upgrade. It upgrades the kernel as well as many other base level packages. Stop all MCP components on the server being patched prior to patch application. 8 Using the System Management console on the server being patched, stop all components except the System Manager and database. 9 Log on to the server as the ntappgrp (ntappadm) role. 10 Change directory: /var/mcp/install 11 Stop the System Manager: ./smStop.
Applying the Oracle Maintenance Release 22 95 Reboot the server: reboot Attention: If you are applying a platform patch to a server with only the platform OS installed, skip steps 23 through 27. 23 Log on to the patched server as the DBA role (ntdbadm). 24 Do one of the following: If this is not a database server, use the System Management console to start the Network Elements. This concludes the procedure. OR If this is a database server, continue with the next steps.
Maintenance Releases Attention: The time it takes to patch the Oracle Database varies from patch to patch. It can take anywhere from a few minutes up to an hour. Prerequisites • You must have SSA (nysysadm) permissions. Procedure Steps Step Action 1 Load the CD containing the Oracle patch into the CD-ROM drive of the primary database server. 2 Log on as the SSA role (ntsysadm). 3 Change user permissions: su - root 4 Copy the installation files: ./mcpCopyFromCD.
Installing the online Help files 97 ERROR at line 1: ORA-00955: name is already used by an existing object • DROP PACKAGE sys.dbms_apply_user_agent * ERROR at line 1: ORA-04043: object DBMS_APPLY_USER_AGENT does not exist These errors do not affect service and can be ignored. The Oracle Maintenance Release patches are installed. Confirm the version matches the version described in the Release Notes: 10 cat /opt/mcp/db/data/version Repeat this procedure for the secondary database server.
Maintenance Releases Change directory: 6 cd /var/mcp/run/MCP_11.0/_0/bin Transfer the file to the Provisioning Manager server using the sftp command: 7 sftp 8 Enter the AA role (ntappadm) password. 9 Change directory: cd /var/mcp/media Copy the file from the remote server to the local machine: 10 get MCP-OnlineHelp_11.0.X.X_.zip Exit the session: 11 exit 12 Log on to the Provisioning Manager/Personal Agent server as the nortel user.
Firmware upgrades 99 Firmware updates navigation • • "Determining the current firmware version" (page 99) • "Installing the firmware upgrades" (page 102) "Comparing the firmware versions to determine upgrade requirements" (page 101) Determining the current firmware version Use these procedures to determine the currently installed firmware version.
Maintenance Releases Querying the Network Interface Card firmware Use this procedure to determine the current Network Interface Card (NIC) firmware version. Prerequisites • You must be assigned to the SSA role (ntsysadm) Procedure Steps Step Action 1 Log on to the system as the SSA role (ntsysadm). 2 Run the following command: sudo ethtool –i The system displays the device properties, including the currently installed firmware version. firmware-version: x.x.
Firmware upgrades 101 Querying the ServeRaid firmware Use this procedure to determine the current ServeRAID firmware version. Prerequisites • You must be assigned to the SSA role (ntsysadm) Procedure Steps Step Action 1 Log on to the server as the SSA role (ntsysadm). 2 Run the following command: arcconf GETVERSION The system displays information about the installed controllers. The firmware version is included in the list of controller information. Firmware : x.
Maintenance Releases If the versions do not match, upgrade the firmware. --End-- Installing the firmware upgrades Use these procedures to install firmware upgrades.
Installing the firmware upgrades 103 The IBM Flash Update Utility appears. 5 Select 1 to update the BIOS. 6 Reply Y to move the current image to the backup location within the Flash ROM. 7 Reply N to update the serial number. 8 Reply N to update the Type/Model 9 Reply N to update the Asset Tag Number. 10 Reply N to save the current image to disk. 11 Enter 1 to update the firmware. The system displays the following message: Flashing BIOS. May take up to 30 seconds.
Maintenance Releases If the firmware is out of date, the system flashes the firmware. 5 When the upgrade completes, remove the CD from the CD-ROM drive. 6 Use the ASM Remote Control to restart the server and boot to the operating system: Server > Tasks > Server Restart --End-- Installing diagnostics firmware upgrades Use this procedure to upgrade the diagnostics firmware. This procedure requires the reboot of the server. Prerequisites • • You must be assigned to the SSA role (ntsysadm).
Installing the firmware upgrades 105 When the server reboot begins, remove the CD from the CD-ROM drive. 5 --End-- Installing RSA-II card firmware upgrades Use this procedure to upgrade the firmware of the RSA-II card. Server reboot is not required for this upgrade. Prerequisites • You must have the CD containing the RSA-II card firmware upgrade file (Platform firmware upgrade CD). • A PC is required to access RSA-II web interface and load firmware.
Maintenance Releases Installing NIC firmware upgrades Use this procedure to install NIC firmware upgrades. This procedure requires the reboot of the server. Prerequisites • • You must be assigned to the SSA role (ntsysadm). You must have the CD containing the NIC firmware upgrade file. Procedure Steps Step Action 1 Load the NIC firmware upgrade CD into the CD-ROM drive. 2 Log on to the server as the SSA role (ntsysadm). 3 Reboot the server.
Installing the firmware upgrades 107 Procedure Steps Step Action 1 Load the hard drive firmware upgrade CD into the CD-ROM drive. 2 Log on to the server as the SSA role (ntsysadm). 3 Reboot the server. sudo reboot 4 If the operating system has been installed, change the boot sequence so that the CD-ROM is the primary boot device by doing the following: • When the BIOS information appears, press F12 to select the boot sequence. • Select CD-ROM as the primary boot device.
Maintenance Releases Procedure Steps Step Action 1 Load the ServeRAID firmware upgrade CD into the CD-ROM drive. 2 Log on to the server as the SSA role (ntsysadm). 3 Reboot the server. 4 If the operating system has been installed, change the boot sequence so that the CD-ROM is the primary boot device by doing the following: • When the BIOS information appears, press F12 to select the boot sequence. • Select CD-ROM as the primary boot device. Otherwise, wait for the server to reboot.
Multimedia PC Client upgrade 109 Multimedia PC Client upgrade This section provides the procedures that you use to upgrade the Multimedia PC Client. Choose one of the following methods: • • "Upgrading the ASU load" (page 109) "Upgrading the Multimedia PC Client installer executable" (page 110) Upgrading the ASU load Use this procedure to upgrade the Automatic Software Update (ASU) load.
Maintenance Releases cd /var/mcp/run/MCP_11.0/PROV1_0/wars/pca/pccli entcode 8 Unzip the file: unzip .zip --End-- Upgrading the Multimedia PC Client installer executable Use this procedure to upgrade the installer executable for the Multimedia PC Client. It is common practice to make the installer available for download from a web page or FTP server. The method of distribution is at the discretion of the site administration.
. Downgrades Maintenance Release and patch upgrades of the AS 5300 database are backwards compatible. However, if data in the database becomes corrupted, the database can be downgraded to a previous Maintenance Release or patch. This chapter contains procedures for downgrading the various system components as well as the full system.
Downgrades Downgrade system components navigation • • • • "Downgrading the AudioCodes gateway" (page 113) "Downgrading the Network Elements" (page 113) "Downgrading the System Manager" (page 113) "Downgrading a database" (page 114) Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
Downgrade system components 113 Downgrading the AudioCodes gateway Use this procedure to downgrade the AudioCodes gateway. The only supported method for downgrading the AudioCodes gateway is to use the SunFire V-215 EMS servers. Downgrading the Network Elements Use these procedures to downgrade the Network Elements. Procedure Steps Step Action 1 From the EMS MG Tree pane, select the AudioCodes gateway to be downgraded. The Info pane and the Status pane now display the AudioCodes gateway.
Downgrades 3 Do one of the following: If this is a downgrade to a previous Maintenance Release, edit the installprops.txt file as follows: ne.load= Run the upgrade script: ./smUpgrade.pl OR If this is a downgrade to a previous patch, run the following script: /mcpPatch.pl -smonly 4 When prompted, select the previous patch to be applied.
Downgrade system components 115 Procedure Steps Step Action 1 Log on to the Primary Database server as the DBA role (ntdbadm). 2 Change directory: cd /var/mcp/run/MCP_11.0/_0/bin 3 Run the cleanup script: ./cleanupReplication.pl 4 Log on to the primary Element Manager server as the AA role (ntappadm). 5 Change directory: cd /var/mcp/install 6 Run the following script: .mcpPrepareLoad.pl –l <11.0.1.0_loadname> 7 Run the database installation command: ./dbInstall.
Downgrades 14 Log on to the secondary database server as the DBA role (ntdbadm). 15 Change directory: cd /var/mcp/run/MCP_11.0/_1/bin/util 16 Run the restore script: ./dbRestore.
Downgrade a full system 117 Downgrade a full system navigation • • • "Preparing for full system downgrades" (page 117) "Downgrading a redundant system" (page 118) "Downgrading a non-redundant system" (page 118) Preparing for full system downgrades Before performing full system downgrades, follow the instructions in this procedure. Procedure Steps Step Action 1 (Optional) Compose a list of all Network Elements and the servers they reside on, including the redundant Network Elements.
Downgrades Stop all active Provisioning Managers and Personal Agent Managers. 2 From the System Manager console navigation tree, navigate to Network Elements > Manager and select the Network Element. For the selected Network Element, click on Maintenance. 3 The Network Element Maintenance window opens. 4 In the Network Element Maintenance window, select instance ID 0. 5 Click Stop. Repeat steps 2 through 4 for each Provisioning Manager and Personal Agent Manager.
Downgrade a full system 119 Downgrading a non-redundant system navigation • "Downgrading a non-redundant system with a replicated database" (page 119) • "Downgrading a non-redundant system with a single database" (page 119) Prerequisites • For information about downgrading a database, see "Downgrading a database" (page 114). • For information about downgrading AudioCodes, see "Downgrading the AudioCodes gateway" (page 113).
Downgrades • • IP Client Managers Fault-Performance Managers 2 Downgrade the database. 3 Downgrade the AudioCodes Gateway. 4 Downgrade the System Manager. 5 Downgrade the Network Elements. --End-- Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
. Common procedures The following sections describe common procedures used while installing and configuring the AS 5300 system. Navigation • "Rebooting the system" (page 121) Rebooting the system Use the following procedure to reboot the AS 5300 server. Procedure Steps Step Action 1 Reboot the server by doing one of the following: • Restore power. If this is the primary installation, power the server on.
Common procedures Application Server 5300 Nortel AS 5300 Installation NN42040-300 01.04 4 November 2008 Copyright © 2007-2008 Nortel Networks .
Application Server 5300 Nortel AS 5300 Installation Copyright © 2007-2008 Nortel Networks All Rights Reserved. Printed in Canada Release: 1.0 Publication: NN42040-300 Document revision: 01.04 Document release date: 4 November 2008 To provide feedback or to report a problem in this document, go to www.nortel.com/documentfeedback. www.nortel.
