Page 1
Nortel Multimedia Communication Server 5100 MCS Upgrades—Maintenance Releases NN42020-303...
Page 2
Users must take full responsibility for their applications of any products specified in this document. The information in this document is proprietary to Nortel Networks. Nortel, Nortel (Logo), and the Globemark are trademarks of Nortel Networks.
Standard 01.01. This document is issued to support Multimedia Communication Server 5100 Release 4.0. August 2006 Standard 6.0. This document is up-issued to support MCS 5100 Release 3.5. It addresses CR Q01434497. July 2006 Standard 5.0. This document is up-issued to support MCS 5100 Release 3.5.
Finding the latest updates on the Nortel web site 13 Getting help from the Nortel web site 13 Getting help over the phone from a Nortel Solutions Center 13 Getting help from a specialist by using an Express Routing Code 14...
Page 8
Stopping the System Manager 27 Backing up the database 27 Installing Linux patches 28 Installing Oracle patches 29 Loading the MCS 5100 Release 4.0 upgrade 31 Extracting the load 32 Running the upgrade script 32 Updating the license key 33...
Communication System (MCS) 5100, go to the Technical Documentation page for MCS 5100. Getting help from the Nortel web site The best way to get technical support for Nortel products is from the Nortel Technical Support web site: www.nortel.com/support This site provides access to software, documentation, bulletins, and tools to address issues with Nortel products.
To access some Nortel Technical Solutions Centers, you can use an Express Routing Code (ERC) to quickly route your call to a specialist in your Nortel product or service. To locate the ERC for your product or service, go to: www.nortel.com/erc...
"Redundant system rollback" (page The upgrade preserves configuration data for the already-installed services. You can perform the upgrade at any time. However, Nortel recommends that you perform the upgrade during a maintenance window to minimize the impact on end users.
Ensure that all applicable software is on-site before beginning the upgrade. The software for the upgrade is delivered on a set of CDs and DVDs, accompanied by a set of MCS 5100 Release Notes. CDs and DVDs are read from the internal DVD-ROM drive. CDs and DVDs are accessed using the Linux command: mount /mnt/cdrom.
Ensure that your completed Customer-Specific Information data sheet lists all server names and IP addresses. This data sheet is included in MCS 5100 Planning and Engineering (NN42020-200). System backups Ensure there are up-to-date backups of the servers. These backups are needed to rollback to the previous release if required.
Stop the System Manager on the System Manager Server. Approximate time estimate = 5 minutes Procedure 5 Stopping the System Manager Step Action Log on to the System Manager Server as nortel. Change the directory: cd /var/mcp/exlab/ Stop the System Manager: ./smStop.pl –p installprops.txt Log off as nortel:...
Approximate time estimate = 10 minutes In the following procedure <load_name> represents the name of the load. The format of <load_name> is: MCP_9.1.x.x_YYYY-MM-DD-HHMM. Procedure 9 Loading the MCS 5100 Release 4.0 upgrade Step Action Place the MCS5100 Release 4.0 Software and MAS patches DVD in the DVD-ROM drive.
In the following procedure <load_name> represents the name of the load. The format of <load_name> is: MCP_9.1.x.x_YYYY-MM-DD-HHMM. Procedure 10 Extracting the load Step Action Log on to the System Manager Server as nortel. Change the directory: cd /var/mcp/loads/ Unzip the load: unzip <load_name>.zip Run the upgrade script Run the upgrade script on the System Manager Server.
36 Nonredundant system upgrade exit Log on to the Provisioning Manager Server as nortel. Determine the installation directory: ls /var/mcp/run/MCP_9.1/ Depending on the type of installation, the installation directory is either PROV1_0 or PROVM1_0. Change the directory: cd /var/mcp/run/MCP_9.1/PROV1_0/bin cd /var/mcp/run/MCP_9.1/PROVM1_0/bin Upgrade MCS online Help: ./installHelp.pl –z...
Approximate time estimate = 5 minutes Procedure 18 Removing the previous load Step Action Log on to the System Manager Server as nortel. Change to the load directory: cd /var/mcp/loads Remove the load: rm -rf <9.1_load name> Remove the zip file: rm -f <9.1_load name>.zip...
Stop the System Manager on the System Manager Server. Approximate time estimate = 5 minutes Procedure 22 Stopping the System Manager Step Action Log on to the System Manager Server as nortel. Change the directory: cd /var/mcp/exlab/ Stop the System Manager: ./smStop.pl –p installprops.txt Extract the previous load Extract the previous load on the System Manager Server.
The format of <load_name> is: MCP_9.1.x.x_YYYY-MM-DD-HHMM. Procedure 24 Restoring the load Step Action Log on to the System Manager Server as nortel. Change the directory: cd /var/mcp/loads/<load_name>/install_scripts Copy the install script: cp bin/* /var/mcp/exlab Change the directory: cd /var/mcp/exlab Edit the installation properties file installprops.txt as follows:...
Procedure 26 Restoring the System Manager Step Action Log on to the System Manager Server as nortel. Change the directory: cd /var/mcp/exlab Restore the System Manager: ./smUpgrade.pl -p installprops.txt -start Log off as nortel: exit Restore, deploy, and start network elements Restore, deploy, and start network elements from the MCS Management Console.
–c “umount /mnt/cdrom” Extract the DVD from the DVD-ROM drive. Log off as sysadmin: exit Log on to the Provisioning Manager Server as nortel. Determine the installation directory: ls /var/mcp/run/MCP_9.1/ Depending on the type of installation, the installation directory is either PROV1_0 or PROVM1_0.
Approximate time estimate = 5 minutes Procedure 39 Stopping the primary System Manager Step Action Log on to the primary System Manager Server as nortel. Change the directory: cd /var/mcp/exlab/ Stop the primary System Manager: ./smStop.pl –p installprops.txt Log off as nortel:...
In the following procedure <load_name> represents the name of the load. The format of <load_name> is: MCP_9.1.x.x_YYYY-MM-DD-HHMM. Procedure 45 Running the primary upgrade script Step Action Log on to the System Manager Server as nortel. Change the directory: cd /var/mcp/loads/<load_name>/install_scripts Copy the upgrade script: cp bin/* /var/mcp/exlab Change the directory: cd /var/mcp/exlab Edit the installation properties file installprops.txt as follows:...
Stop the System Manager on the secondary System Manager Server. Approximate time estimate = 5 minutes Procedure 46 Stopping the secondary System Manager Step Action Log on to the secondary System Manager Server as nortel. Change the directory: cd /var/mcp/run/MCP_9.1/SM_1/bin Stop the System Manager: ./neStop.pl Log off as nortel:...
–c “umount /mnt/cdrom” Extract the DVD from the DVD-ROM drive. Log off as sysadmin: exit Log on to the primary Provisioning Manager Server as nortel. Determine the installation directory: ls /var/mcp/run/MCP_9.1/ Depending on the type of installation, the installation directory is either PROV1_0 or PROVM1_0.
Approximate time estimate = 15 minutes Procedure 54 Setting up database replication Step Action Log on to the primary System Manager Server as nortel. Change the directory: cd /var/mcp/exlab Edit the installation properties file installprops.txt as follows: db.type=Replicated Set up database replication: ./dbInstall.pl –p installprops.txt -fo...
–c “umount /mnt/cdrom” Extract the DVD from the DVD-ROM drive. Log off as sysadmin: exit Log on to the secondary Provisioning Manager Server as nortel. Determine the installation directory: ls /var/mcp/run/MCP_9.1/ Depending on the type of installation, the installation directory is either PROV2_0 or PROVM2_0.
Approximate time estimate = 5 minutes Procedure 65 Removing the previous load Step Action Log on to each System Manager Server as nortel. Change to the load directory: cd /var/mcp/loads Remove the load: rm -rf <9.1_load name> Remove the zip file: rm -f <9.1_load name>.zip...
The format of <load_name> is: MCP_9.1.x.x_YYYY-MM-DD-HHMM. Procedure 72 Restoring the primary load Step Action Log on to the primary System Manager Server as nortel. Change the directory: cd /var/mcp/exlab Edit the installation properties file installprops.txt as follows: ne.load = <load_name> db.type = Single Run the upgrade script: ./dbInstall.pl –p installprops.txt -fo...
Approximate time estimate = 5 minutes Procedure 75 Stopping the secondary System Manager Step Action Log on to the secondary System Manager Server as nortel. Change the directory: cd /var/mcp/run/MCP_9.1/SM_1/bin Stop the System Manager: ./neStop.pl Restore, deploy, and start primary network elements Restore, deploy, and start primary network elements from the MCS Management Console.
–c “umount /mnt/cdrom” Extract the DVD from the DVD-ROM drive. Log off as sysadmin: exit Log on to the Provisioning Manager Server as nortel. Determine the installation directory: ls /var/mcp/run/MCP_9.1/ Depending on the type of installation, the installation directory is either PROV1_0 or PROVM1_0.
Procedure 84 Extracting the previous secondary load Step Action Log on to the secondary System Manager Server as nortel. Change the directory: cd /var/mcp/loads/ Make sure that the required load exists: If the required load does not exist it must be copied to the /var/mcp/loads directory.
–c “umount /mnt/cdrom” Extract the DVD from the DVD-ROM drive. Log off as sysadmin: exit Log on to the Provisioning Manager Server as nortel. Determine the installation directory: ls /var/mcp/run/MCP_9.1/ Depending on the type of installation, the installation directory is either PROV1_0 or PROVM1_0.
Page 106
Document version: 01.08 Document date: 10 August 2007 To provide feedback or report a problem with this document, go to www.nortel.com/documentfeedback. Sourced in Canada The information in this document is subject to change without notice. The statements, configurations, technical data, and recommendations in this document are believed to be accurate and reliable, but are presented without express or implied warranty.