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. The information and/or products described in this document are
subject to change without notice.
Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks.
All other trademarks are the property of their respective owners.
.
Page 3
.
Contents
New in this release7
Features7
Other changes7
Introduction9
Deployment options9
Installation overview11
Installation times12
Installation preparation15
Unpack the materials15
Customer-specific information15
Installation Planning sheet17
Hardware installation and configuration21
Hardware overview22
Mount the hardware23
Connect the hardware24
Networking overview27
Hardware configuration30
3
Mounting the server23
Network Time Protocol29
Resetting the planar BIOS and RSA-II card to factory defaults32
Resetting the ServeRAID BIOS to factory defaults33
Configuring the RSA-II card35
Configuring the planar BIOS36
Configuring the ServeRAID BIOS38
Platform software installation41
Starting the Linux operating system installation44
Configuring the networking, serial console redirection, and time zone settings45
Configuring the NTP, Syslog, and Audit Daemon settings47
Configuring the Primary (EMS1) and Secondary (EMS2) clock source servers49
Configuring the clock source for all other SIP core servers50
Configuring the BIOS hardware clock50
Configuring preconfigured accounts and passwords52
Configuring a system for individual accounts53
Reinstalling platform software55
Oracle database software installation59
Oracle database software installation59
Installing Oracle database software60
AS 5300 software deployment63
Core components63
Staging files64
Installation properties file65
AS 5300 initial software deployment66
Downloading the MCP load software68
Preparing the initial load for deployment68
Deploying the initial software load70
Starting the System Management Console71
Updating the licensekey71
Patches73
MCP core software load patch installation73
Obtaining the patches74
Enabling patch delivery for Regional Patch Selector (RPS) sites76
Enabling patch delivery for non-Regional Patch Selector (RPS) sites78
Patching the database schemas and System Manager78
Patching the Network Elements79
Patching the Audio Codes gateway82
Transferring the Maintenance Release files to System Manager87
Upgrading the database schemas and System Manager89
Upgrading the Network Elements90
Upgrading the AudioCodes gateway92
Applying the Linux Maintenance Release92
Applying the Oracle Maintenance Release95
Installing the online Help files97
Firmware upgrades98
Determining the current firmware version99
Querying the BIOS, Diagnostics, RSA-II card, and Baseboard Management
Controller firmware99
Querying the Network Interface Card firmware100
Querying the hard drive firmware100
Querying the ServeRaid firmware101
Comparing the firmware versions to determine upgrade requirements101
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 5300Overview ((NN42040-100)) .
Other changes
This document is new for AS 5300 Release 1.0.
Revision history
November 04 2008Standard 01.04. This document is up-issued to add technical content
under section Maintenance Releases and in Downgrade system
components chapters.
October 22, 2008Standard 01.03. This document is up-issued to add technical content
under section Deployment options and in AS 5300 software deployment
and Maintenance Releases chapters.
July 11, 2008Standard 01.02. This document is up-issued for AS 5300 Release 1.0.
7
June 10, 2008Standard 01.01. This document is issued for AS 5300 Release 1.0.
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.
This document provides instructions that apply to the initial installation of
AS 5300 servers and for server platform software reinstallations as part of
backup and restore procedures. The AS 5300 does not support upgrades
from other MCP products.
For more information about the topics covered in this document, see NortelAS 5300 Fundamentals (NN42040-100).
9
Attention:Each AS 5300 software load package includes Release
Notes. You must read and understand the Release Notes before you
begin the installation of the system.
Navigation
•
"Deployment options" (page 9)
Deployment options
The AS 5300 has two system configuration options:
•
a small redundant system, which supports up to 5 000 subscribers
•a medium redundant system, which supports up to 25 000 subscribers
For a small redundant deployment, the minimum baseline configuration
for the AS 5300 infrastructure consists of two (2) IBM x3550 servers with
all MCP components on each box.
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 stepApproximate time required to complete
Unpacking the hardware10 minutes
Table 2
Hardware installation and configuration
Installation stepApproximate time required to complete
Mounting the hardware20 minutes
Connecting the hardware20 minutes
Resetting the planar BIOS5 minutes
Resetting the ServeRAID BIOS5 minutes
Configuring the RSA-II card10 minutes
Configuring the planar BIOS5 minutes
Configuring the ServeRAID BIOS15 minutes
Table 3
Platform software installation
Installation stepApproximate time required to complete
Starting the Linux operating system installation1–2 minutes
Configuring the networking, serial console
10 minutes
redirection, and time zone settings
Configuring the NTP, Syslog, and Audit
2–3 minutes
Daemon settings
Configuring the BIOS hardware clock1–2 minutes
Configuring accounts and passwords5–10 minutes
Installing Linux updates15 minutes
Table 4
Oracle database software installation
Installation stepApproximate time required to complete
Installing Oracle35 minutes (Primary and Secondary performed
in parallel)
Installing Oracle updates15 minutes
Table 5
AS 5300 software deployment
Installation stepApproximate time required to complete
Downloading the MCP software5 minutes
Preparing the initial load for deployment5 minutes
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. You require the following components:
•
IBM x3550 core server
•CD/DVD set containing firmware updates
•AS 5300 Release 1.0 SIP Core New System Software Package,
consisting of CD/DVD-ROMs containing the Linux operating system
and Oracle database installation software, product documentation, and
the MCP core load software
15
•USB keyboard, mouse, and monitor, or a keyboard, video and mouse
(KVM) unit
The number of servers and software packages received varies depending
on the type of system configuration you install (simplex or redundant).
In addition, ensure there are an adequate number of properly grounded
electrical outlets for the server, monitor, and other devices.
For more information about server hardware, including the installation of
hot-swap components and other devices, see IBM System x3550 Type7978 User Guide.
Customer-specific information
Ensure that the Installation Planning Sheet lists all server names and IP
addresses. Complete an Installation Planning Sheet for each individual
server being installed.
Remote Server IP AddressAll10.12.1.5
Remote Server User IDAllbkupstor
Remote Server User PasswordAlln/a
Remote server backup directoryAll./platform_backups
mcpPlatform.ems1
host. 2007_10_29.
Backup file nameAll
11_32_09.tar
Miscellaneous
Serial Console Port Baud RateAll9600
External NTP Time Server (Clock
10.11.130.30,
Source) IP Addresses for runtime
systemEMS1, EMS210.11.131.31
Primary NTP Clock Source (EMS1)
IP AddressNES (all)10.10.0.5
Secondary NTP Clock Source
(EMS2) IP AddressNES (all)10.10.0.6
TimezoneAllUS / Central
Syslog server (if required)All10.12.1.6
External NTP Time Server (Clock
All
Source) for RSA-II card(optional)192.168.3.250
Passwords
Preconfigured Account Initial Passwords, if used (not required for restore reinstalls)
ntappadmAllQWEpoi43@!
ntsysadmAllQWEpoi43@!
ntsecadmAllQWEpoi43@!
ntbackupAllQWEpoi43@!
ntdbadmAllQWEpoi43@!
IAO Single Account Information, if used (not required for restore reinstalls)
IAO User IdAlliaouser
IAO PasswordAllQWEpoi43@!
GRUB BootloaderAllQWEpoi12#$
System Account Initial passwords (required for all installs)
rootAllQWEpoi12#$
ntossadmAllQWEpoi12#$
nortelrpsAllQWEpoi12#$
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"
Table 6
IBM x3550 hardware characteristics (cont’d.)
ItemDescription
Server identificationx3550, Model 7978 AC1
CPU2 x Quad-Core Intel Xeon processor E5420, 2.5GHz, 12 MB L2 cache,
1333MHz FSB, 80w
Memory8 GB PC2-5300 CL5 ECC DDR2 Chipkill FB DIMM 667MHz
Disk2 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 power2 x 670W A/C Power Supply (redundant, hot-swap); 2.8m, 100-240V,
C13 to IEC 320-C14 (WW) rack power cable
DC power2 x 670W D/C Power Supply (redundant; hot swap); 2.8m, 100-240V,
C13 to IEC 320-C14 (WW) rack power cable
Remote managementRemote Supervisor Adapter II (RSA-II) Slimline with external RJ-45
Ethernet port (internal PCI card)
Optical driveDVD/CD-RW
CoolingTwo fans per CPU, one fan per power supply
Networking2 x 10/100/1000 Mbps
SerialCOM1, DB-9
Rail kitPizarro (Nortel-specified)
Mount the hardware
The AS 5300 server requires the Pizzaro rail kit for rack-mount
installations.
Mounting the server
Use this procedure to mount the physical server into a server rack.
Prerequisites
•You require a Pizzaro rail kit for each IBM x3550 server being installed.
Procedure Steps
StepAction
1Adjust the rail kit to fit in the frame. To properly support the
server, each rail must be mounted to the outside of the front and
rear of the frame.
2Adjust the left and right rails by sliding the rear mounting bracket
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.
The Remote Supervisor Adaptor (RSA-II) is a PCI card that provides
an Ethernet interface for remote system management of the server. It
includes an embedded Web server. When the server is secured, the
RSA-II card Ethernet port provides HTTPS/SSH access to the RSA-II card
for remote management of the server. This includes access to controls
to manage the power state of the server and inspect physical attributes,
as well as to gain encrypted remote access to the physical console of the
server. This port is typically cabled to a port in a maintenance network,
separate from the network used for the primary application of the server.
The COM1 serial port provides serial console access using an industry
standard RS-232 serial cable and is typically connected to either a terminal
server such as the MRV Models LX-40XX or it can be attached to a serial
port on another computer using a null modem cable. If the COM1 serial
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).
Table 7
COM 1 serial port pinout
PIN numberAssignment
NameDescription
1
2
3
4
5
6
7
8
9
DCDData Carrier Detect
RXDReceived Data
TXDTransmitted Data
DTRData Terminal Ready
GRNDCommon Ground
DSRData Set Ready
RTSRequest To Send
CTSClear To Send
RIRing Indicator
During the software platform installation procedure, you have the option
of configuring the COM1 serial port (in Linux, this is referred to as ttyS0)
for console login during system runtime. The configured serial port has
the following characteristics:
•7-bit characters with even, odd, none, or space parity, and 8-bit
characters with no parity are supported
•Only COM1 (ttyS0) is supported
•Terminal emulation is VT100
•The user has the option of configuring either a 9 600 or 19 200 baud
rate
Connect a physical monitor or a KVM switch to the video port. This
provides the physical KVM console. Nortel does not provide a KVM for
use with this product.
Connect a USB keyboard, or a KVM switch, to one of the USB ports to
provide a physical KVM console. A USB keyboard connected through
a KVM switch can sometimes become unresponsive while switching
consoles at the KVM keyboard. If this occurs, typing CTRL+Q toggles the
flow control signals to restore keyboard communications with the server.
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. In this type of networking configuration, the
server is connected to two different VLANs (or networks):
•
Service network
•Maintenance network
The server has a machine logical address for each network and frames
entering and leaving the server are tagged with the appropriate network
identifier. The hosting network equipment must support VLANs and not
perform VLAN tag processing on behalf of the server.
In a typical Dual-VLAN configuration, the majority of network traffic
traverses the Service network. This includes signaling, Operations,
Administration, Maintenance, Provisioning (OAMP), and software
heartbeating. The Maintenance network is used for a few specific
functions, including the extraction of Operations Support Systems (OSS)
feeds by northbound Network Management System (NMS).
Networking overview27
For more information about a typical Dual-VLAN networking configuration,
see Figure 3 "Typical Dual-VLAN configuration" (page 28) .
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.
VLAN interfaces are named according to the following syntax:
<hosting_interface>.<vlan_id>
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. It is on these logical VLAN interfaces that the
machine logical IP addresses of the Service and Maintenance VLANs are
configured (one for each VLAN). Software applications are concerned only
with these logical VLAN interfaces.
Nortel does not recommend Zero-VLAN configurations for standard AS
5300 configurations, but Zero-VLAN configurations can be implemented
in non-standard configurations, such as in a lab or testing environment.
Servers in a Zero-VLAN configuration have no knowledge of VLAN ID
tagging.
Consult the Information Planning Sheet for details about network settings.
Network Time Protocol
Two Element Manager servers (EMS) serve as Network Time Protocol
(NTP) clock sources for the Network Element servers (NES) in the AS
5300 system. You can configure the two EMS servers to receive their
clock information from their internal system clocks or from external
sources. It is recommended that you configure the servers to receive
their clock information from external sources so that all of the servers in
the system are synchronized with each other as well as with global clock
sources.
If you configure the EMS servers to use their internal clocks as the
system time source, the system is synchronized internally but has no
synchronization with global clock sources.
In addition to being configured to use internal or external clock sources,
the EMS servers maintain time synchronization with each other.
The NTP protocol is not secure. You can secure NTP traffic using
symmetric keys for server authentication or by configuring the IPSec mesh.
Symmetric keys are stored in a key file on both the client and clock source
server. Modify the Network Time Protocol configuration file to specify
which key in the key file to use. In 2-server or 4-server configurations,
symmetric key usage is only configured on the servers hosting the System
Managers. In the 4-server configuration, the non-System Manager servers
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 NortelAS 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.
Prerequisites
•You require a USB keyboard, mouse, and monitor, or KVM unit.
Hardware configuration procedures
This work flow shows the sequence of procedures you perform to
configure the BIOS on an AS 5300 server.
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. This involves the resetting
of the BIOS settings to factory defaults followed by the application of
product-specific configuration settings. Restoring of factory defaults for
any of the BIOS components does not have an impact on the others. They
need to be restored independently.
Use this procedure to reset the planar BIOS and RSA-II card to the factory
default settings.
Attention:When you reset the RSA-II card, all existing network
connections to the RSA-II Ethernet interface are disconnected and no
further connections can be made until network settings are reconfigured.
Procedure Steps
StepAction
1
2From the Configuration/Setup Utility menu, select the System
From the physical KVM console, reboot the AS 5300 server and
press F1 at the IBM splash screen when prompted to access the
planar BIOS configuration utility.
Summary option and confirm "8192 MB" (8 GB) for Installed
Memory. If it is not, contact your next level of support before
proceeding.
Attention:If the system summary does not show 8192 MB,
confirm the order code matches the serial number for the server
against the shipping packing list (or the box the server was
delivered in).
Order code XYSG9US: 8 GB of RAM AS5300 Linux Core
Servers
Order code XYSGAUS: 4 GB of RAM MAS Platform Servers
It also possible that the server may have the correct order code
with the correct memory configuration but not recognized by the
system. If this happens, contact your next level of support before
proceeding.
3Select Advanced Setup.
Hardware configuration33
4
5Select Restore RSA II Defaults.
Select RSA-II Settings.
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.
When the reset to factory defaults is complete, the following
message appears:
RSA II Defaults Loaded!
If data had been previously configured for the RSA-II card, that
data appears.
6Press Enter.
7Press Esc until the top level menu of the planar BIOS setup
utility appears.
8
Select Load Default Settings.
The following message appears:
Current settings will be changed to their default
settings - Press Enter to continue.
9
Press Enter.
The planar BIOS is restored to the factory defaults.
10
11
Select Exit Setup.
Select Yes, save and exit the Setup Utility and press Enter.
The server reboots.
Resetting the ServeRAID BIOS to factory defaults
Use this procedure to reset the ServeRAID BIOS to the factory default
settings.
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
StepAction
1Reboot 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.
3
Delete any existing arrays (if configured during previous
installations) by doing the following:
•Select Array Configuration Utility.
•Press M to select Manage Arrays.
— If the message No Arrays present appears, there are
no arrays configured. Press Esc to return to the top-level
menu and continue with step 4.
— Otherwise, the List of Arrays appears.
•Highlight the array and press Del to delete it.
•Select Delete.The system displays the following prompt:
WARNING: Deleting will erase all data from the
array.Do you still want to continue?(Yes/No)
•Press Y to continue.
•Press Esc twice to return to the top-level menu.
4Select SerialSelect Utility.
5Select Controller Configuration.
6Press F6 to reset to factory defaults.
7Select Yes to reset the ServeRAID BIOS to default.
8Press Esc to return to the previous menu.
The system displays the following prompt:
Save changes made?(Yes/No)
9Select Yes to save changes.
10Select PHY Configuration.
Highlight OS USB Selection and use the left and right arrow
keys to select Linux OS.
10Select Save Values and Reboot RSA II.
11When 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.
13Press Esc until the Configuration/Setup Utility screen is
reached.
14Select Exit Setup.
15
Select Yes to save and exit the Setup Utility.
The RSA-II card is now configured for non-secure access using
supported IP-based protocols, such as HTTP and TELNET. You
can now reconnect the Ethernet cable.
For more information about configuring security for the RSA-II
card, see Nortel AS 5300 Security (NN42040-601).
Configuring the planar BIOS
Use this procedure to configure the planar BIOS.
WARNING
There is an option to configure an Administrative password
during BIOS configuration. The configuration of BIOS
passwords is not recommended; however, local security policies
might require that BIOS passwords be used. Use extreme
caution if configuring BIOS Administrative passwords. If the
password is lost or forgotten, it cannot be recovered, and the
motherboard of the server must be replaced. See Nortel AS5300 Security (NN42040-601).
WARNING
There is an option to configure a Power-on password during
BIOS configuration. Do not configure Power-on passwords as
this could possibly interfere with the restarting of servers.
Prerequisites
•The planar BIOS has been reset to the factory default settings.
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.
2Select 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
5
6Select Start Options.
7
8
9
10
11Highlight Second Startup Device and choose Hard Disk 0.
12Highlight Third Startup Device and choose Disabled.
Press Enter to confirm.
Press Esc to cancel and return to the previous menu.
Highlight Planar Ethernet PXE/DHCPand choose Disabled.
Highlight USB Disk and choose Disabled.
Select Startup Sequence Options.
Highlight First Startup Device and choose CD ROM.
13
14
15Press Esc twice to return to the top-level menu.
16
17
18Highlight Serial Port B and choose Disabled.
19Press Esc to return to top level menu.
20Select Date and Time.
21Highlight Time and enter the current local time.
22
23Press Esc to return to top level menu.
24Select Save Settings and press Enter when the confirmation
Highlight Fourth Startup Device and choose Disabled.
Highlight Wake On LAN and choose Disabled.
Select Devices and I/O Ports.
Highlight Serial Port A and choose Port 3F8, IRQ 4.
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. Use these
procedures for the configuration of new servers and the reinstallation of the
platform software due to server recovery.
Many of the prompts displayed during installation have default values
contained within square brackets ([ ]). Pressing the Enter key indicates
acceptance of the default values.
The Linux installer presents a series of questions to the user. At certain
points during the question-and-answer process, the user is presented
with a summary of the choices made. The user then has the option of
correcting errors made during the earlier steps. Previous answers are
provided as defaults, allowing the user to quickly accept them as correct
values.
41
The Core Linux 11.0.x CD-ROM that shipped with your product contains
the Linux installation files.
Perform the installation procedures using the physical KVM console or the
RSA-II remote control.
Throughout these procedures, the term installer refers to the Linux
installation script, and not the person performing the installation.
Platform software installation procedures
This work flow shows the sequence of steps required to install the platform
software.
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.x installation CD
•Core Linux Maintenance Release patch CDs (if applicable)
•
CD-ROM drive is selected as first priority boot device in the system
BIOS (normally set during initial BIOS configuration)
•Server backup file on a remote server (if applicable)
Procedure Steps
StepAction
1
2
3The installer prompts for acceptance of the licensing agreement.
4The installer scans for basic hardware configuration to determine
Load the Core Linux 11.0.x installation CD in the CD-ROM drive
and reboot the server.
The installation welcome screen appears.
At the boot prompt, type install-kvm and then press Enter.
The Linux boot kernel (the version of the kernel that runs during
the installation procedure) loads and the installation program
starts.
Choose one of the following responses:
Reply Y if you have previously reviewed the licensing agreement
information and agree to it.
OR
Reply N (default) to review the licensing agreement information.
The MCP Software Licensing menu appears. You can choose to
review the Licensing Overview, the Summary of Open Source
RPMs and Licenses, or Exit.
After you have reviewed and accepted the licensing agreement
information, installation continues. If you do not accept the
licensing agreement, installation stops and the server reboots.
and verify the system environment, and displays the list of
detected disk devices with their storage sizes.
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.
Procedure Steps
StepAction
1The system displays the following prompt:
Enter MACHINE Logical IP of the Primary Clock Source
Server:
Enter the machine logical IP address of the EMS1 server.
The following prompt displays:
Enter MACHINE Logical IP of the Secondary Clock
Source Server [<PRIMARY_IP>]:
2
Enter the machine logical IP address of the Secondary (EMS2)
server, overwriting the default IP address (EMS1 server)
provided.
Configuring the BIOS hardware clock
The hardware clock is configured during initial BIOS configuration and
can also be configured directly within the BIOS by using the BIOS setup
utility. Use this procedure to modify the hardware clock settings during an
installation without entering BIOS configuration directly.
The system clock of the runtime server is a software-based clock, separate
from the hardware clock in BIOS. It is read by the Linux kernel as the
runtime system initializes, providing the seed time for the software-based
clock. Shortly after the system initializes, the NTP daemon running on
the local server initiates its protocol with the configured clock sources to
perform time synchronization.
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.
Procedure Steps
StepAction
1During the Linux installation process, the system displays the
2Do one of the following:
Configuring accounts and passwords51
following prompt:
Do you want to keep this date and time (Y/N) [Y]?
Select Y (default) to accept the current date and time as they
appear.
OR
Select N to enter a new date and time.
After the new date and time are confirmed, the data is written to
the BIOS.
The installer then continues with the next phase of Linux
operating system installation.
Configuring accounts and passwords
This phase of the Linux operating system installation includes the
configuration of user accounts and passwords.
During the Linux operating system installation process, the installer first
determines if the accounts and passwords are being recovered from a
backup file. If the accounts and passwords are being recovered as part
of a restore process, the installer displays the list of user accounts to be
recovered.
If accounts are not being recovered, use these procedures to create new
accounts and passwords.
--End--
Attention:When configuring accounts and passwords during 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.
Navigation
•
"Configuring preconfigured accounts and passwords" (page 52)
•"Configuring a system for individual accounts" (page 53)
Configuring preconfigured accounts and passwords
Use this procedure to configure preconfigured accounts.
Prerequisites
•
You have completed the steps described in "Configuring the NTP,
Syslog, and Audit Daemon settings" (page 47).
•
For more information about installing Linux Maintenance Releases, see
"Applying the Linux Maintenance Release " (page 92).
Procedure Steps
StepAction
1
2Reply Y to create the preconfigured accounts. (If you reply N to
3Do one of the following:
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]?
this prompt, the system configures individual accounts.)
The system displays the following prompt:
Do you want to use the same initial password for
these accounts (Y/N) [N]?
Reply Y to select the option to configure all of the preconfigured
accounts with the same password. This password must be
changed for all accounts after first login.
OR
Reply N to select the option to configure a password for each
preconfigured account.
The installer displays the account method confirmation screen.
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.
If you selected the option to configure a password for each
preconfigured account, the installer prompts you to create a
password for each preconfigured account.
6
Create the user account passwords as prompted by the
installer. Ensure the passwords meet the requirements
displayed on-screen. The passwords must be entered again for
confirmation.
The installer displays the system accounts configuration screen.
7
Create passwords for each system account as prompted by the
installer.
The installer displays the following message:
System Configuration Complete
8Press Enter to continue.
The installer applies the system configurations. This may take
several minutes.
After the configuration has been applied, the server reboots.
Login access is available at the physical server, through RSA-II
remote control (if configured), and available SSH.
9
If applicable, install platform patches.
Configuring a system for individual accounts
Use this procedure to configure an individual account.
Prerequisites
•You have completed the steps described in "Configuring the NTP,
Syslog, and Audit Daemon settings" (page 47).
•For more information about installing Linux Maintenance Releases, see
"Applying the Linux Maintenance Release " (page 92).
1During 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.
3
Enter a name for the SSA account. Ensure the name meets the
requirements displayed on-screen.
The installer displays the account method confirmation screen.
4Do one of the following:
Reply Y to accept the account method confirmation.
OR
Reply N to go back to the User Accounts screen and change
selections.
After the account confirmation is accepted, the installer displays
the prompt to create the password for the SSA account. The
password limitations and requirements appear on-screen.
5
Enter a password for the SSA account. Ensure the password
meets the requirements displayed on-screen.
The installer displays the system accounts configuration screen.
6Create passwords for each system account as prompted for by
the installer.
The installer displays the following message:
System Configuration Complete
7Press Enter to accept the configuration.
The installer applies the system configurations. This may take
several minutes.
After the configuration has been applied, the server reboots.
Login access is available at the physical console, through RSA-II
remote control (if configured), and available SSH.
ntappadmThis account is used for SIP core server software administration.
ntsysadmThis account is used for system administration.
ntsecadmThis account is used for security administration.
ntbackupThis account is used for backup and restore administration.
ntdbadmThis account is used for database administration.
Table 9
List of system accounts
Account nameDescription
root
ntossadmThis account is accessed by software components from other
This account is the root user on the system. This account is rarely
used.
servers to gain access to OSS feeds.
nortelrpsThis account is accessed by the Nortel Regional Patch Selector
(RPS) patching system to deposit patches files onto the MCP
server.
bootloaderThis is not an actual account on the system. Rather, this refers to
the Grand Unified Boot Loader (GRUB), which is invoked by the
planar BIOS to boot the operating system. This password is used to
protect entry into the command line mode of the GRUB bootloader,
where system booting parameters are modified.
Reinstalling platform software
Use this procedure to restore a platform backup file from a remote server
during Linux installation. The platform backup file contains settings for the
Linux operating system and other information.
For information about backups and restores, see Nortel AS 5300Administration (NN42040-600) .
WARNING
Backup data is specific to each server. Only restore platform
data to the server from which the backup data originated.
•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 have a valid user name and password for the remote FTP
server.
•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).
Procedure Steps
StepAction
1From the Remote Platform Backup Data Retrieval screen, enter
the VLAN ID for the local network. The standard AS 5300
networking configuration is Dual-VLAN. Use the ID of the Service
VLAN where the server IP is assigned.
2Enter the IP address of the local machine.
3
4
5Enter the IP address of the FTP server where the remote backup
Enter the default gateway IP address.
Enter the netmask.
data file is located.
6
7Enter the password for the FTP server.
8
Enter the user name for the FTP server.
Enter the remote server path where the backup files are located.
The system displays the following prompt:
Is this information correct?
9
Do one of the following:
Reply Y if the information is correct.
OR
Reply N to go back and make changes.
After the information is accepted, the system configures the
local network and checks connectivity to the remote server.
When connectivity is established, the installer lists the available
platform backup files. The following is an example of an
available platform backup files list:
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.
The Configuration Validation screen appears, listing the
networking settings as retrieved from the backup file.
11Reply Y to accept the Configuration Validation summary.
OR
Reply N if the information displayed in the Configuration
Validation summary is incorrect or if you want to make changes.
If you select this option, you have the choice to start over and
retrieve a different backup file or step through and modify the
existing (embedded) backup information. You can refer to
"Configuring the networking, serial console redirection, and time
zone settings" (page 45) for more information on these steps.
When the Configuration Validation information is accepted, a
second page of Configuration Validation information appears.
This summary contains the Network Time Protocol (NTP),
Syslog, and Audit Daemon settings.
The installer displays the following prompt:
Is this information correct?
12Reply Y to accept the information.
OR
Reply N to go back and make changes. The installer advances
through the configuration settings one at a time. You can refer to
"Configuring the NTP, Syslog, and Audit Daemon settings" (page
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.
14Press Enter to continue.
15At the Password Configuration screen, enter passwords for the
mandatory system accounts:
•
root
•
bootloader
•ntossadm
•
nortelrps
You can refer to "Configuring accounts and passwords" (page
51) for more information on these steps.
The System Configuration Complete screen appears.
Attention:For NTP configuration changes, if symmetric keys
were used, you must restore the keys to the server and execute
the ntpConfig.pl script after installation.
16
Press Enter to continue the installation.
The installer applies the system configurations. This may take
several minutes. When the configurations are complete, the CD
ejects and the server reboots.
The operating system and all stored configurations imported from
the backup file, such as ACL and IPSec configuration, are now
restored to the server. For information on backup and restore,
see Nortel AS 5300 Security (NN42040-601).
17If applicable, apply any Linux Maintenance Release patches to
bring the system up to date with current baselines.
•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.5 GB of disk space is required for this installation.
This chapter contains information and procedures about AS 5300 software
deployment.
Navigation
•
"Core components" (page 63)
•
"Staging files" (page 64)
•
"Installation properties file" (page 65)
•
"AS 5300 initial software deployment" (page 66)
Core components
The following are core components for AS 5300 deployments:
•System Managers
•
Fault-Performance Managers
•
Accounting Managers
63
•Session Managers
•
Provisioning Managers
•
IP Client Managers
•
AudioCodes
•Media Application Servers (MAS)
To deploy the AS 5300 load, you require direct access to the servers. For
a typical deployment, you only require access to the Element Management
server on which you configure the primary or preferred instance of the SM
(System Manager).
There are two access methods:
•Windows PC—Use a Secure Shell (SSH) client to access AS 5300
servers on the network from a Windows PC.
•Terminal Servers—Use Terminal Servers to connect remotely to AS
5300 components without requiring a dedicated Windows PC.
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.
2-server staging files (small system)
2-server staging configurations consist of a redundant installation where
all core components are distributed across two servers. For a 2-server
staging configuration, the following files are used:
•
installprops.txt
•
StagingFedPBX2Server.tags
•StagingFedPBX2Server.xml
Figure 4 "Physical view of a 2-server staging configuration" (page 64)
shows the physical view of a 2-server staging configuration:
Figure 4
Physical view of a 2-server staging configuration
The following parameters represent specific values in the 2-server tags file:
•hostnames for the Element Management server
•IP address of the Element Management server
•service logical IP address for the System Manager, Accounting
Manager, and Session Manager
•name of the site where the System Manager and Database will be
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.xml
Figure 5 "Physical view of a 4-server staging configuration" (page 65)
shows the physical view of a 4-server staging configuration:
Figure 5
Physical view of a 4-server staging configuration
Core components65
The following parameters represent specific values in the 4-server tags file:
•hostnames for the Element Management and Session Manager servers
•IP addresses of the Element Management and Session Manager
servers
•service logical IP address for the System Manager, Accounting
Manager, and Session Manager
•
name of the site where the System Manager and Database will be
configured
Installation properties file
All installation and upgrade scripts use the installation properties file
(installprops.txt). The information in the properties file defines basic
information for the configuration of the System Manager and the Database.
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.username parameters must satisfy the
following restrictions:
•
is between 6 and 30 characters (inclusive) in length
•
starts with a letter [a-z] [A-Z]
•only contains the characters [0-9] [a-z] [A-Z] and “_”
For new system installations, the db.password parameters must satisfy the
following restrictions:
•
is between 15 and 30 characters (inclusive) in length
•starts with a letter [a-z] [A-Z]
•
contains at least two digits [0-9]
•
contains at least two ‘_’
•does not contain the associated DB username
•
only contains the characters [0-9] [a-z] [A-Z] and “_”
AS 5300 initial software deployment
This section contains information on deploying AS 5300 software.
AS 5300 initial software deployment procedures
The following work flow shows the sequence of procedures required to
deploy AS 5300 software.
FileDefinition
tagsFileImport tags file (StagingFedPBX*Server.tags) containing IP address/tag
and hostname/tag pairs. The file also contains sitename/tag value and
other tags. The install/upgrade scripts use the tagsFile to replace tags with
values in the given import XML file.
importFile
licenseKeyFileThe license key file to apply. This property (-l) is optional. The license key
XML file (StagingFedPBX*Server.xml) containing server definitions,
Network Element instance definitions, start-up critical configuration data,
and default configuration data. This file is never manually modified by the
user.
may also be applied after the installation. If it is to be used, the license key
file should be copied to /var/mcp/install before running the script.
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
StepAction
1
Open a Web browser and enter the following URL:
https://<SysMgr_IP_address>:12121
The System Management Console starts.
Updating the licensekey
Use this procedure to update the licensekey. You do not need to perform
this procedure if the licensekey was updated during the initial load
deployment.
Prerequisites
•
The licensekey code has been obtained from Keycode Retrieval
Services (KRS).
Procedure Steps
StepAction
1
Log on to the System Management console as admin. When
prompted, enter the admin password.
--End--
2From the Network Data and Mtc navigation tree, select
Licensekey node.
The Licensekey window appears.
3Click Edit .
4Using the Select License key file window, browse to the
location of the licensekey file located on your local hard disk.
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).
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. For more information about
Maintenance Releases, see "Maintenance Releases" (page 85).
This section contains information about MCP core software load patches.
Attention:All Network Elements are taken out of service during the
installation of patches. However, impact to call processing is minimal as
Session Managers are configured with Hot Standby instances.
Prerequisites
•The system status must not indicate any critical alarms. Check the
Alarm Bar of the System Management console for critical alarms and
clear them before installing patches.
•Obtain the IP addresses of all System Managers in the system.
•"Patching the database schemas and System Manager" (page 78)
•
"Patching the Network Elements" (page 79)
•"Patching the Audio Codes gateway" (page 82)
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. The file containing the System Manager core
upgrade is named according to the load name. For example, the load
name for the archive MCP_11.0.1.0.zip is MCP_11.0.1.0. The System
Manager creates patch load directories under /var/mcp/loads.
Patches can be in V, R, or S status. S status patches are patches that
have been submitted to RPS but have not yet reached V or R status.
Use these procedures to obtain MCP core software load patches manually
or enable the Regional Patch Selector notification.
Obtaining patches navigation
•"Retrieving V or R status MCP patches manually" (page 74)
•
"Retrieving S status MCP patches manually" (page 75)
•
"Enabling patch delivery for Regional Patch Selector (RPS) sites" (page
MCP patches are posted to the Support & Training/Technical
Support section of the Nortel support web site and grouped
according to product name. To be successfully applied,
downloaded patches must end with a .patch extension and be
placed on the active System Manager.
Always download the most recent patch. Patches are
cumulative, that is, each new patch contains all of the updates
from the previous patches.
2Confirm 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.
3Using the nortelrps password, transfer the downloaded file to the
server hosting the active System Manager using Secure FTP
(SFTP).
Transfer the file to the following directory:
/var/mcp/dropbox
Example:
$ sftp nortelrps@<SysMgr_IP>
Connecting to <SysMgr_IP>...
Authorized uses only.All activity may be
monitored and reported.
nortelrps@<SysMgr_IP>’s password:
sftp> put MCP_10.1.1.1.patch /var/mcp/dropbox
Uploading MCP_10.1.1.1.patch to /var/mcp/dropbox/
MCP_10.1.1.1.patch
MCP_10.1.1.1.patch
100% 23MB 1.7MB/s 00:14
sftp> quit
The file is transferred to the active System Manager.
Retrieving S status MCP patches manually
Procedure Steps
StepAction
1Launch a Web browser and go to the following URL:
http://gsds.ca.nortel.com
2Select RPS > Query Tools > Generic > Getpath.
3Enter the Product Line and Patch ID.
The product line used for MCP software is ’MCP’. You can put in
the exact Patch ID, such as MCP_11.0.0.1, or you can use the
’%’ character as a wildcard to formulate queries.
The query returns the Unix path location.
Example:
Using an FTP client, download the patch from the
gsds.ca.nortel.com site.
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.
--End--
Enabling patch delivery for Regional Patch Selector (RPS) sites
If the RPS service is enabled, the System Manager sends information
about the software at the site to the RPS server, which sends an alarm
notification when updates are available.
Prerequisites
•Your site has been configured with the Nortel Regional Patch Selector
system.
•Enabling RPS integration requires knowledge of the site name that has
been configured into the RPS system. The configured site name in the
Regional Patch Selector application must match the configured site
name in Nortel’s Regional Patch Selector system.
Procedure Steps
StepAction
1
2From the navigation menu, select Network Data and Mtc >
Launch the System Management console.
Regional Patch Selector.
The Regional Patch Selector window appears.
3Select the Integrate with Regional Patch Selector (RPS) check
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.
4Open the Alarm Browser window to view the patch details.
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
StepAction
1Launch the System Management console.
2
From the navigation menu, select Network Data and Mtc >
Regional Patch Selector.
The Regional Patch Selector window appears.
3
In the Regional Patch Selector window, select the Integrate
with Regional Patch Selector (RPS) check box.
4
5Click Apply.
Create and enter a Site Name.
An inform file is created in the \var\mcp\dropbox directory.
6Launch a browser and log in to the Nortel Web site
(http://www.nortel.com).
7
Navigate to Support and Training > Online Self Service >
Patch Audit Tool
The Patch Audit Web page appears.
8
Follow the on-screen instructions to upload the newly created
inform file.
After you submit a valid inform file, a secured link containing
the patch audit results is automatically generated and sent to
the specified e-mail address. Use this information to download
patches manually, as described in "Obtaining the patches" (page
74).
Patching the database schemas and System Manager
Use this procedure to patch the database schemas and System Manager.
You can patch the System Manager without causing a service outage to
users, but all active MCP System Management Consoles are shut down
during the patch installation process.
Log on to the primary System Manager as the AA role
(ntappadm) using SSH.
2
Change directory:
cd /var/mcp/install
3Run 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.
4Log on to the MCP System Management Console.
The System Manager is started and in the Active state, running
on the desired load.
Patching the Network Elements
Use this procedure to patch the Network Elements. If a Network Element
is supported in a fault tolerant mode such as a Session Manager, one
instance will be in active state and the other one will be in hot standby
state. When the active instance is shut down to be patched, the standby
instance becomes active to prevent loss of service.
--End--
For non-fault tolerant Network Elements, such as Provisioning Manager,
the service provided by the Network Element is impacted during the patch.
For more information about Network Elements and their associated service
impacts during patch upgrades, see Table 11 "Service impacts to Network
Elements during patching" (page 79).
Table 11
Service impacts to Network Elements during patching
When the accounting manager
is stopped, billing information
continues to be cached on the
session manager servers as
disk space allows. After the
Accounting Manager is back in
service, the cached information
Application Server 5300
Nortel AS 5300 Installation
NN42040-300 01.04
4 November 2008
None.
.
Page 80
80Patches
Network Element
Provisioning
Managers
Client impactSubscriber impact
is transferred to the Accounting
Manager and no information is
lost.
The Provisioning Manager is
not deployed with redundant
instances. There is no user
access to the Provisioning Client
during upgrade.
While a Provisioning Manager is being
patched, users from the Domain URL
corresponding to the Provisioning
Manager being patched will be able
to login and make calls; however,
downloading of the service package
is not possible. Once the Provisioning
Manager is patched successfully,
subsequent logins will be successful.
If the optional Personal Agent Manager
is configured, there is no impact when
patching the Provisioning Manager. If
Personal Agent services are provided by
the Provisioning Manager that is being
patched, the subscriber is not able to
access the Personal Agent until the
patching process is completed.
Subscribers cannot perform click-to-call
dialing from the PC Client until the
patching process is completed.
Personal Agent
Managers
The Personal Agent Manager
is not deployed with redundant
instances. There is no user
access to the Personal Agent
during upgrade.
Session ManagersIf there are redundant instances
of the Session Manager, one
instance will be in active state
and one will be in hot standby
state.
IP Client ManagersMore than one IPCM element
can be configured on the
system. Each IPCM will contain
only one instance. During
upgrade, the IPCM is not
accessible.
Attention:Patch the Network Elements in the order specified in the
procedure. If a particular Network Element is not configured on the
system, you can skip it and proceed to the next one.
Subscribers cannot perform click to call
dialing from the PC Client.
If there is only one configured Session
Manager Instance, no new calls will be
allowed on system until the Session
Manager instance is active again.
If there is only one IPCM on the system,
Nortel Networks IP 2002/2004 phones
cannot connect and all service is lost.
6Repeat 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.
Patching the Audio Codes gateway
Audio Codes gateway loads can be delivered using an MCP core software
load patch. Use this procedure to patch the Audio Codes gateway load.
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.
Attention:The MCP Installation and Release Notes must be read
prior to upgrading or patching the system. These notes may indicate
that specific updates are required before the Maintenance Release can
be applied. Apply all required updates before applying the Maintenance
Release.
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.
Navigation
•"Transferring Maintenance Release files to System Manager from a
CD" (page 87)
•"Transferring Maintenance Release files to System Manager from
Electronic Software Delivery (ESD)" (page 88)
Transferring Maintenance Release files to System Manager
from a CD
Procedure Steps
StepAction
1
2
3Change directory:
4Copy the files from CD:
5Using a new SSH session, log on to the System Manager as the
6Delete older MCP loads:
Place the CD containing the MCP core load file into the CD-ROM
tray of the primary System Manager. This load will be used to
upgrade the majority of the system.
Log on to the System Manager as the AA role (ntappadm) using
SSH.
cd /usr/local/bin
sudo ./mcpCopyFromCD.pl -m manifest-all
The MCP 11.0 load is copied to the /var/mcp/loads directory.
The MCP 11.0 online Help zip files are copied to the
/var/mcp/media directory.
The ASU related files are copied to the /var/mcp/media/PC-Cl
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.
8Remove the CD-ROM from CD tray.
--End--
Transferring Maintenance Release files to System Manager
from Electronic Software Delivery (ESD)
Procedure Steps
StepAction
1
If it does not already exist, create the /var/mcp/esd_files directory
on the System Manager server.
•Log on to the System Manager server as the AA role
(ntappadm).
•Check for the directory: ls /var/mcp/esd_files
•
If the directory does not exist, create it: mkdir
/var/mcp/esd_files
2
Change directory:
cd /var/mcp/esd_files
3Use an FTP client to securely transfer the ESD file to the System
Manager server.
4Log on to the System Manager as the AA role (ntappadm) using
Delete older MCP loads.
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.
cd /var/mcp/loads
rm –Rf <old_load_directory>
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.
11
Repeat this procedure for the secondary System Manager.
--End--
Upgrading the database schemas and System Manager
You can upgrade the System Manager without causing a service outage to
users, but all active MCP System Management Consoles are shut down
during the upgrade process.
Prerequisites
•The new MR load.zip file is in the /var/mcp/loads directory.
Procedure Steps
StepAction
1Log on to the primary System Manager as the AA role
4
5On the maintenance panel, click the Upgrade button.
Select the Network Element to be patched.
The NE Maintenance Panel window appears to monitor the patch
installation.
6Repeat 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 mode or Hot Standby mode
display their supported standby mode.
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. Upgrading an AudioCodes gateway
causes service loss and all calls connected through that gateway are
dropped.
Procedure Steps
The load name listed for each instance is the patched load.
--End--
StepAction
1From the EMS MG Tree pane, select the AudioCodes gateway
to be upgraded. The Info pane and the Status pane now display
the AudioCodes gateway.
2From the Info pane, selectSoftware Upgrade. The Files
Manager screen is displayed.
3Select the appropriate software (CMP) to be downloaded and
click OK in the Files Manager screen. A Question screen is
displayed.
4
From the Question screen, selectSystem Reset Upgrade and
click Yes.
The selected software (CMP) is downloaded to the AudioCodes
gateway, and the AudioCodes gateway is reset.
--End--
Applying the Linux Maintenance Release
Use this procedure to apply the Maintenance Release for the Linux
operating system.
Attention:If you are applying a platform patch to a server with
only the platform OS installed, skip steps 23 through 27.
23Log 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.
25
Change directory:
cd /opt/mcp/db/bin
26Re-link Oracle:
./relinkOracle.pl
If it is active, Oracle shuts down. It then re-links and restarts.
27Use the System Management console to start the Network
Elements.
--End--
Applying the Oracle Maintenance Release
Use this procedure to apply the Maintenance Release patch for the Oracle
database software. Apply the Maintenance Release patch to both the
primary and secondary database servers.
Attention:When applying the Oracle patches, the install script
can shutdown and restart the database automatically, resulting in a
few minutes that the database is unavailable. Schedule the upgrade
accordingly.
Transfer the file to the Provisioning Manager server using the
sftp command:
sftp <prov_mgr_ip>
8
9
Enter the AA role (ntappadm) password.
Change directory:
cd /var/mcp/media
10
Copy the file from the remote server to the local machine:
get MCP-OnlineHelp_11.0.X.X_<date-time>.zip
11
Exit the session:
exit
12
Log on to the Provisioning Manager/Personal Agent server as
the nortel user.
13
Change directory:
cd /var/mcp/run/MCP_11.0/<prov>_0/bin
14Extract the Online Help files:
15
Firmware upgrades
This section contains procedures for upgrading the AS 5300 firmware
components. Uprade the firmware when the current version does not
match the firmware version available on the upgrade CD.
Use these procedures to do the following:
•determine the currently installed firmware version
•compare the installed version to the version on the upgrade CD
•if required, install the firmware upgrade
./installHelp.pl –z <OnlineHelpFilename>.zip
The updated Online Help Files are accessible from the
Provisioning Manager/Personal Agent client and the PC Client.
Repeat this procedure on the other Element Manager server,
which hosts the other Provisioning Manager.
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
StepAction
1
2
Log on to the system as the SSA role (ntsysadm).
Run the following command:
sudo ethtool –i <ethernet_device>
The system displays the device properties, including the
currently installed firmware version.
firmware-version:x.x.x
Variable definitions
VariableValue
ethernet_deviceeth0 or eth1
Querying the hard drive firmware
Use this procedure to determine the current hard drive firmware version.
Prerequisites
•
You must be assigned to the SSA role (ntsysadm)
Procedure Steps
--End--
StepAction
1Log on to the server as the SSA role (ntsysadm).
2Run the following command:
arcconf GETCONFIG 1 pd
The system displays the physical device information for each
installed hard drive. The firmware version is included in the list
of information for each device.