102.1.1 AS5300 2.1 Server Installation: Multimedia Communications Platform AS 5300 R2.1

Multimedia Communications Platform AS 5300 R2.
1
102.1.1 AS5300 2.1 Server Installation
Method of Procedure
Product Release:
AS 5300 R2.1
Document Version:
1.1
Document Status:
Released
Document Release Date:
December 03, 2010
Security Classification:
Avaya Confidential
Copyright 2010 Avaya

All rights reserved.
Avaya CONFIDENTIAL: The information contained in this document is the property of Avaya. Except as
specifically authorized in writing by Avaya, the holder of this document shall keep the information contained
herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties
and use same for evaluation, operation, and maintenance purposes only.

Method of Procedure
Document Version 1.1
Revision History
Version
Date
Description
1.0
08/25/2010
AS 5300 R2.1 initial version. Update for AS5300 R2.1,

based on R2.0 version 1.2
1.1
12/03/2010
Fix wi00820481 wi00827703
December 03, 2010

1
2010 Avaya Inc.

Avaya proprietary use pursuant to company instructions

Method of Procedure
Table of Contents
Revision History.....................................................................................................2
Table of Contents...................................................................................................3
1 Start Here..........................................................................................................4
2 Overview...........................................................................................................5
2.1
Document Conventions................................................................................................... 5
2.2
Document Overview........................................................................................................ 6
3 Work Flow.........................................................................................................7
4 Verify Prerequisites..........................................................................................8
5 Planning..........................................................................................................10
6 Install...............................................................................................................11
6.1
License Attribution......................................................................................................... 15
6.2
BIOS Clock................................................................................................................... 16
6.3
Hardware Environment.................................................................................................17
6.3.1
Reference Server................................................................................................19
6.3.2
Non-Reference (Other) Server............................................................................20
6.4
NTP Clock Configuration...............................................................................................21
6.5
Initial Login (Establish Password).................................................................................22
6.6
Grub Password (Establish Password)...........................................................................23
7 Patch Current..................................................................................................25
8 Post Installation Verification..........................................................................27
9 References......................................................................................................28

Method of Procedure
1 Start Here
To immediately start executing the procedures described in this document,
proceed to Section 3 "Work Flow".
To first gain contextual information regarding this document, first read Section 2
"Overview", then proceed to Section 3 "Work Flow".
December 03, 2010

3
2010 Avaya Inc.


Method of Procedure
2 Overview
2.1 Document Conventions
The following conventions are used throughout this document.
References to sections in this document are typically of the form:

Section <number> (e.g., Section 1)
where "<number>" is the number of the section. In document text where a
more complete reference facilitates the flow (such as an initial reference in an
overview section), the following form is used:
Section <number> "<name>" (e.g., Section 1 "Start Here")
where "<name>" is the name of the section.
References to documents listed in Section 9 "References" are typically of the

form:
[<number>] (e.g., [1])
where "<number>" is the number of the reference from Section 9. In
document text where a more complete reference facilitates the flow (such as
an initial reference in an overview section), the following form is used:
[<number>] "<title>"
(e.g., [1] "102.1.2 AS5300 Initial System Installation")
where "<title>" is the title of the referenced document.
In-line text describing output displayed on a login window, console, or

graphical user interface appears as follows: Exampleinlineoutputtext.
In-line text describing data entered into the terminal or console window, or
graphical user interface, appears as follows: Exampleinlineinputtext.
Paragraph text describing output displayed on a login window, console, or

graphical user interface appears as follows:
Exampleparagraphoutputtext
Paragraph text describing data entered into a terminal or console window, or

graphical user interface, appears as follows:

Method of Procedure
Exampleparagraphinputtext
References to terms and data from [2] "102.3.1 AS5300 Initial System
Installation" are of the following form:
Enter the Network IP Address of the server.
where Network IP Address is a reference to data from a system layout tab
from [2].
This document uses the term "target server" to refer to the server undergoing
the installation procedures described in this document.
2.2 Document Overview

This document describes the procedures to perform the installation of the server
platform software (operating system and base level packages) for a core or MAS
server for the AS5300 product.
The methods for performing the initial system installation of an AS5300 system
are described in [1] "102.1.2 AS5300 Initial System Installation". As described in
that document, AS5300 systems follow one of three basic layouts of software
components to server hardware, some of which allow for system scaling through
the installation of additional servers hosting additional MCP application
components.
The job aid, [2] "102.3.1 AS5300 Initial System Installation", is an Excel
workbook data gathering tool which supports the system initial installation
process, and contains tabs for each of the AS5300 system layouts. Each layout tab
describes server-level data for the basic layout and, where applicable, for scaling
beyond that layout. Both this document and [1] reference terms and data found on
those layout tabs for server platform installation.
This document makes no distinction between a server installation conducted
during an initial system installation and a server installation conducted during a
future system expansion. It is assumed that the system layout tab from [2] which
is most appropriate for the installation context (initial installation or future
expansion) is updated and provides the context for all data references made by
this document.
December 03, 2010

5
2010 Avaya Inc.


Method of Procedure
3 Work Flow
This section provides the work flow to install an AS5300 core server (the target
server) with its platform software and to bring it current on patches. Each step in
this procedure refers to a section which provides the specific work instructions to
accomplish that task. A given step must be successfully completed prior to
starting the next step.
1.
Execute Section 4, "Verify Prerequisites".
2.
Execute Section 5, "Planning".
3.
Execute Section 6, "Install".
4.
Execute Section 7, "Patch Current".
5.
Execute Section 8, "Post Installation Verification".

Method of Procedure
4 Verify Prerequisites
Prior to the execution of the procedures described in the remainder of this
document, it is assumed that all of the prerequisites described in this section have
been met.
The following media must be available:
The latest available server platform installer CD-ROM.
The latest available server platform patches CD-ROM (if applicable).
The relevant row of the relevant system layout tab from [2] must have been
updated or created.
If this document is being executed within the context of an initial system

installation, then this requirement is satisfied as a result of executing the
procedures described in [1].
If this document is being executed within the context of the expansion of a

system which has been previously installed, it is required that the layout
which is appropriately aligned with the existing system has been identified
and a row in that layout tab in [2] created for the target server. If necessary, [1]
should be consulted for guidelines as to how to properly create the row in that
document for the target server.
All data references to [2] in this document are with respect to the above identified
layout row.
The target server must:
Meet the minimum hardware configuration requirements for the AS5300

product.
Be installed into its target environment (e.g., frame) and is properly cabled for
power and networking.
Have its planar (motherboard) BIOS and disk controller BIOS settings
properly set for the product configuration, enabling it to receive the
installation of the server platform software.
The following must be satisfied from the host environment:
December 03, 2010

7
2010 Avaya Inc.


Method of Procedure
The networking gear hosting the servers is properly configured to route traffic
between these servers and any other equipment in the host network (e.g.,
management stations).
If the target server is EMServer1 or EMServer2, then the NTP clock source at
the address External Clock Source #1 and, if provided in [2], at address
External Clock Source #2, must be reachable in order for the target server to
receive its clocking.
If the target server is other than EMServer1 or EMServer2, then servers

EMServer1 and EMServer2 must be reachable by the target server in order
for the target server to receive its clocking.
A desktop computer, or other server, is available on a network other than the

one which is to host the target server, and it must be accessible for login in
order that an ICMP ping can be performed against the target server. This is
required for post-installation verification.
A desktop computer, or other server, is available and is currently synchronized

to the same external NTP clock source(s) to be used by the target server. This
is required for post-installation verification.
Users executing this document must have the following core competencies:
The ability to access servers for login via:

o A locally attached keyboard and monitor or KVM (Keyboard, Video,
Mouse) switch.
o The ssh remote access protocol.
Basic Linux operations:

o Navigating the file system (changing directories).
o The implications of uninformed or careless use of system commands
while logged in as the "root" user.
Basic server tasks:

o Powering servers up
o Powering servers down
o Resetting servers
o Inserting and removing CD-ROM and DVD-ROM discs

Method of Procedure
5 Planning
This document assumes that the planning for the server installation has already
been performed prior to the execution of this document. Refer to Section 4
"Verify Prerequisites" for more information.
Initial passwords will be required for the system boot loader (GRUB), and each of
the following system accounts:
"root" account
"ntsysadm" account (SSA role)
"ntappadm" account (AA role)
"ntsecadm" account (SA role)
"ntbackup" account (BA role)
"ntdbadm" account (DBA role)
"ntossadm" account (OSS role)
The method for documenting these initial passwords for the installation of the
target server is not provided by this document, nor in [2]. It is expected that the
personnel performing the installation procedures will manage these passwords in
a manner appropriate to the policies and practices of the host environment.
Refer to document 105.1.1_AS5300_2.1-Network_Separation for designating
network VLAN IDs and IP addresses.
December 03, 2010

9
2010 Avaya Inc.


Method of Procedure
6 Install
This section describes the procedure for installing the target server with the
platform software (operating system and base level packages) from a CD-ROM
installer disc. Note that all existing data on the target server's disk drive(s) will be
erased during this procedure. If required, transfer any files that need to be retained
off the server prior to executing the following procedures.
Perform the following:
1.
Gain access to the server's console using a locally attached keyboard

and monitor or a KVM switch.
2.
Insert the CD-ROM server platform installer disc into the optical drive
tray of the server. The server may need to be powered on in order for
the tray to be ejected.
3.
Reboot the server and wait for the system to initialize and provide the
installer welcome screen. The welcome screen has the title:
WelcometotheMCPCoreLinuxSystemInstaller
and provides the following command line prompt:
boot:
4.
Enter installkvm. (if installing a MAS onto a legacy x3550 server

from AS5300 1.0 equipped with 4 GB of memory, the enter install
kvmMAS. This relaxes the checks on memory size to allow the install
to be performed on this type of server; this is intended for MAS
servers only).
5.
Wait until the following prompt is given:

Wouldyouliketochecktheintegrityofthe
installmedia?(Y/N)[Y]?
6.
Press the Enter key to accept the "Y" default. Note that if "N" is
entered for the above prompt, then a bad CD-ROM disc or optical
drive may go undetected, resulting in an invalid server installation.
7.
If the following message is displayed, then an issue exists with the

CD-ROM disc or with the optical drive. In this case, contact the next
level of support.
10

Method of Procedure
Integritycheckfailed.Thiscouldbeduetoa
corruptioninthetransferoftheISOimageused
toburnthisdisc,abadburnofthedisc,a
damagedordirtydisc,orabadopticaldrive.
Pleasecleanthediscandtryagain.Ifthe
problempersists,youshouldobtainanewdiscand
tryagainandverifytheopticaldrive.
8.
If the integrity check passes the following prompt is given:

Wouldyouliketoviewlicensinginformation?
(Y/N)[Y]?
9.
If licensing information has already been viewed from a previous

server installation, enter n and continue with the next step. Otherwise
enter y and execute Section 6.1, then continue with the next step.
10.
A warning message is printed to indicate the disk(s) which will

undergo the installation and that their data will be erased (wiped). The
following prompt is given:
Continue[c],Abort[a]:
11.
Enter c. Note that this action will erase all existing data on the attached
disk drive(s).
12.
The current date and time as read from the server's BIOS clock is
presented and the following prompt is given:
Doyouwanttokeepthisdateandtime(Y/N)[Y]?
13.
If the presented time is the correct local time, then enter y and continue
with the next step; otherwise enter n and execute Section 6.2, then
continue with the next step.
14.
Execute Section 6.3.
15.
A screen is presented to list the types of installations which can be

performed, followed by the prompt:
Pleaseenterthenumberoftheinstalloption[1
to3]=>
16.
Enter 1.
17.
A SystemConfiguration screen is presented with the prompt:
December 03, 2010

11
2010 Avaya Inc.


Method of Procedure
PresstheEnterKeytobeginconfiguration...
18.
Press the Enter key to continue.
19.
The following prompt is given:

Enterhostname:
20.
Enter the Hostname of the server.
21.

Enterbondname[bond0]:
22.
Press the Enter key to accept the default value and to continue.
23.
If presented with the prompt Enterthefirstslave[<x>]:, then

enter the Bond0 Slave 0 value for the server (or press Enter to accept
the presented default value, if correct). If this value from [2] is "n/a",
then an error exists in the planning data from [2]; stop and contact the
next level of support.
24.
If presented with the prompt Enterthesecondslave[<x>]:,

then enter the Bond0 Slave 1 value for the server server (or press Enter
to accept the presented default value, if correct). If this value from [2]
is "n/a", then an error exists in the planning data from [2]; stop and
contact the next level of support.
25.

EnterVLANID(0=noVLAN)(04094):
26.
Enter the VLAN ID value for the server.
27.

Entersubnetname[sn0]:
28.
Press the Enter key to accept the default and continue.
29.

EnterIPaddress:
30.
Enter the Network IP Address for the server.
31.

Entersubnetprefixlength(130):
12
32.
Enter the Network Prefix for the server.
33.

Method of Procedure
EntergatewayIPaddress:
34.
Enter the Network Default Gateway for the server.
35.
A SystemConsoleRedirection screen is presented with choices for

serial console redirection and the following prompt is given:
Selectanoption(13):
36.
Enter 3.
37.
The TimezoneSelection screen is presented and the following

prompt is given:
EnterRegion(162):
38.
Determine, from the on-screen menu, the menu number that matches
Timezone Field1 for the target server, and enter that number.
39.
If the EnterTimezone prompt is given, determine, from the on-screen

menu, the menu number that matches Timezone Field2 for the target
server and enter that number.
40.
A ConfigurationValidation screen is presented showing the

values entered up until this point in time. If all values are correct, enter
y to accept these values and continue; otherwise, enter n to return to
step 19 for data re-entry. Note that previously entered data is presented
as defaults to assist with the data entry process.
41.
42.
The SyslogConfiguration screen is presented with the prompt:

DoyouwishtoconfigureaSyslogServerIP
address(Y/N)[N]?
43.
If Syslog IP for the target server does not have a valid IP address, then
enter n and proceed to step 46; otherwise enter y and continue with the
next step.
44.

EntertheSyslogServerIPaddress:
December 03, 2010

13
2010 Avaya Inc.


Method of Procedure
45.
Enter the Syslog IP value.
46.
A ConfigurationValidation screen is presented showing the

values entered up until this point in time. If all values are correct, enter
y to accept these values and continue; otherwise, press the Enter key
to accept the default response of "n" to return to step 41 for data reentry. Note that previously entered data is presented as defaults to
assist with the data entry process.
47.
A UserAccounts&Passwords screen is presented which lists the

accounts which will be created and their default passwords. Press the
Enter key to continue.
48.
A ConfigurationComplete screen is presented with the prompt:

PresstheEnterKeytocontinuewiththe
installation..."
49.
The data entry phase of the installation is now complete. Press the
Enter key to start the installation and configuration of the server
platform software. No further user input is required until the post
installation login is performed.
50.
Screens showing the partitioning of hard disk(s), formatting of file

systems, installations of software packages, and subsequent system
configuration of the system are presented.
51.
A system reboot is automatically performed, after which the following

login prompt is given, where <hostname> is Hostname for the target
server.
<hostname>login:
52.
Execute Section 6.5 for the "root" account.
53.
Execute Section 6.5 for the "ntsysadm" account (SSA role).
54.
Execute Section 6.5 for the "ntappadm" account (AA role).
55.
Execute Section 6.5 for the "ntsecadm" account (SA role).
56.
Execute Section 6.5 for the "ntbackup" account (BA role).
57.
Execute Section 6.5 for the "ntdbadm" account (DBA role).
58.
Execute Section 6.5 for the "ntossadm" account (OSS role).
59.

14

60.

Method of Procedure
This completes the install from CD-ROM for the target server.
6.1 License Attribution

This section describes the procedure to navigate through the installer license
attribution information during the server platform installation process.
1.
At the EnterSelection=> prompt, enter 1.
2.
Press the Enter key repeatedly to page through the licensing

information until the EnterSelection=> prompt is again presented.
3.
Enter 2.
4.
Press the Enter key repeatedly to page through the licensing

information until the EnterSelection=> prompt is again presented.
5.
Enter 3 to exit. The following prompt is presented:

Doyouacknowledgethislicensinginformation?
6.
Enter y.
7.
Proceed to step 10 in Section 6.
6.2 BIOS Clock

This section describes the procedure to set the time on the BIOS clock during the
server platform installation process.
1.
At the prompt Enterthemonth(112)[x]:,enter the number

for the current month, where '1' is January, and '12' is December.
2.
At the prompt Entertheday(1xx)[x]:, enter the current day of

the month (e.g., enter "22" if the current date is March 22), and press
the Enter key.
3.
At the prompt Entertheyear(YYYY)[xxxx]:, enter the current

year, and press the Enter key.
4.
At the prompt Enterthehour(023)[xx]:, enter the current hour

of the current day, and press the Enter key. Note that this uses the 24hour clock, where the first hour of the day is '0' and the last hour of the
day is '23'.
December 03, 2010

15
2010 Avaya Inc.


Method of Procedure
5.
At the prompt Entertheminutes(059)[xx]:, enter the current

minute of the current hour, and press the Enter key. The first minute of
the hour is '0' and the last minute of the hour is '59'.
6.
The newly entered time is displayed and the following prompt is

given:
Doyouwanttokeepthisdateandtime(Y/N)[Y]?
7.
Enter y.
8.
6.3 Hardware Environment

This section describes the procedure to set the hardware configuration during the
server platform installation process. The first phase of this part of the target server
installation is to classify the server hardware as either a known reference server or
as an "Other" (non-reference) server. This classification is usually determined by
the installer itself, but can be overridden by the user performing the installation in
the event that the installer software does not correctly classify the server.
An important aspect of hardware detection and determination is the physical disk
drive configuration on the target server. Note that if hardware RAID-1 (mirroring)
is configured on the target server, then the two physical disks which are members
of the logical RAID disk are seen by the installer as a single disk drive.
1.
The HardwareEnvironmentConfiguration screen is presented.
2.
If the installer presents a message similar to the following, then the

target server has been detected as a known reference server, and
therefore proceed to step 6:
16

Method of Procedure
Detectedhardware:x3550M2M3
Choose"A"toacceptor"O"tosetthehardware
environment
To"Other"[A]:
3.
If the installer does not detect the server as a known reference server,
then the following message is presented:
Aspecifichardwaretypeknownbythisinstaller
hasnotbeendetected.Thedefaulthardwaretype
of"Other"willthereforebeusedunless
overriddenbelow.
Installsbasedonthe"Other"hardwaretypeare
fullysupportedwhenthathardwaremeetsminimum
requiredspecifications."Other"installsdonot
providefortheinstallationofvendorspecific
devicedriversorcustomsoftware.Anyrequirement
fortheinstallationandongoing(post
installation)maintenanceofsuchsoftwareisthe
responsibilityoftheuserperformingthe
installation.
1)Other
2)IBMHS20
3)IBMHS21
4)IBMX3550
5)IBMX3550M2M3
6)IntelTIGH2U
Hardwaretype[1]:
4.
If the target server is, in fact, not a reference server, enter 1 and
execute Section 6.3.2.
5.
If the target server is a known reference server, then override the

installer default of Other by entering the menu number corresponding
to the server, and execute Section 6.3.1.
6.
If this server is the indicated reference server type, press the Enter key
and execute Section 6.3.1; otherwise enter o and continue with the
next step.
December 03, 2010

17
2010 Avaya Inc.


Method of Procedure
7.
The user is overriding the detected server type, classifying the target
server as an "Other" server. The following message is presented and
prompt are given:
Installsbasedonthe"Other"hardwaretypeare
fullysupportedwhenthathardwaremeetsminimum
requiredspecifications."Other"installsdonot
providefortheinstallationofvendorspecific
devicedriversorcustomsoftware.Anyrequirement
fortheinstallationandongoing(post
installation)maintenanceofsuchsoftwareisthe
responsibilityoftheuserperformingthe
installation.
Isthisinformationcorrect(Y/N)[N]?
8.
Enter y and execute section 6.3.2.
6.3.1 Reference Server

This section describes the procedure to set the hardware configuration where the
target server has been detected as a reference server, either by the installer
software, or overridden by the user.
1.
The message and prompt similar to the is presented:

HardwareEnvironment:IBMX3550M2M3
Isthiscorrect(Y/N)[N]?
2.
Enter y.
3.
A message is displayed indicating the disk(s), and their sizes, which

have been detected. Disk sizes are reported in GB (International
System/SI) and GiB (binary units).
4.
If two disks have been detected and the reference server does not
support software RAID-1, then the following message and prompt are
presented. Press Enter and continue with step 15 in Section 6.
SoftwareRAIDisunsupportedforthisinstall.The
seconddiskdrivewillthereforenotbeused.
Thismachinewillbeconfiguredusingthe
followingdisk:
18

Method of Procedure
/dev/<disk>(xxGB,XXGiB)
PressENTERtocontinue
5.
If a single disk has been detected and the reference server requires two
disks (for disk mirroring via software RAID-1), then the following
message is displayed and the installation is aborted. Contact the next
level of support to correct the hardware configuration.
ThisinstallationrequiressoftwareRAID,butonly
onediskdrivehasbeendetected.
Abortinginstallation.
Doyouwanttoseethelogfileonthisconsole
(Y/N)[N]?
6.
Otherwise, the physical disk configuration matches that required for

the given reference server. A message is presented with the disk(s)
which will be undergoing installation and the usable disk space for the
software RAID-1 mirror (if software RAID-1 is applicable), and the
following prompt is displayed:
PressENTERtocontinue
7.
Press Enter and continue with step 15 in Section 6.
6.3.2 Non-Reference (Other) Server

This section describes the procedure to set the hardware configuration where the
target server has been detected as a non-reference ("Other") server, either by the
installer software, or overridden by the user.
1.
The following message and prompt are displayed:
HardwareEnvironment:Other
Isthiscorrect(Y/N)[N]?
2. Enter y.
3.
A message is displayed indicating the disk(s), and their sizes, which

have been detected and which will undergo installation. Disk sizes are
reported in GB (International System/SI) and GiB (binary units).
December 03, 2010

19
2010 Avaya Inc.


Method of Procedure
4.
If a single disk drive is present in the target server, the following

prompt is given. Press the enter key to continue to continue with step
15 in Section 6.
PressENTERtocontinue...
5.
If two disks are present, then the following prompt is given:

DoyouwanttosetupS/WRAID1betweenthesetwo
disks?(Y/N)?[Y]?
6.
The standard configuration for MCP servers is for redundant disk

drives. If the first reported disk is actually a hardware RAID logical
disk of two physical disks, then enter n and continue with the next
step. Otherwise, it is recommended to enter y, and continue with step 9
in order to configure software RAID-1 between the two reported disk
drives.
7.
A message is presented indicating the size of the disk drive to be

installed and the following prompt is given:
8.
Press the Enter key to continue to continue with step 15 in Section 6.
9.
A message is presented summarizing the two disk drives, their

individual sizes, and the resulting usable space for the RAID-1 mirror
(determined by the smaller of the two disk drives). The following
prompt is then given:
10.
Press the Enter key to continue to continue with step 15 in Section 6.
6.4 NTP Clock Configuration

This section describes the procedure for configuring the NTP (Network Time
Protocol) settings during the server platform installation process.
1.
A NetworkTimeProtocol(NTP)Configuration screen is
presented with choices on setting up clock sources, and with the
following prompt:
Selectanoption(13):
20

Method of Procedure
2.
If this is EMServer1, then enter 1 and continue with the next step; if
this is EMServer2, then enter 2 and continue with the next step;
otherwise enter 3 and proceed to step 11.
3.
The prompt Selectanoption(E,I): is given to select between

internal or external clock sources for the system. Enter e.
4.

Howmanyexternalclocksourceswouldyouliketo
reference(12)[1]?
5.
If both External Clock Source #1 and External Clock Source #2 have

IP addresses then enter 2, otherwise enter 1.
6.
A prompt of the following form is given for each IP address to be

entered:
EnterClockSourceIPaddress#<n>:
7.
Enter the IP address for External Clock Source #1 then, if prompted,

for External Clock Source #2.
8.
The following prompt is given, where "<peer>" is either "Primary" or

"Secondary".
EnterIPAddressof<peer>ClockSource:
9.
If this is EMServer1, then enter the Secondary Clock Source; if this is

EMServer2, then enter the Primary Clock Source.
10.
11.

EnterIPAddressofPrimaryClockSource:
12.
Enter the Primary Clock Source.
13.

EnterIPAddressofSecondaryClockSource:
14.
Enter the Secondary Clock Source.
15.
December 03, 2010

21
2010 Avaya Inc.


Method of Procedure
6.5 Initial Login (Establish Password)

This section describes the procedure to establish account's password upon initial
login after a server platform installation. In the following:
<hostname> refers to Hostname for the target server.
<account> refers to the account which is undergoing this initial login

procedure (e.g., "root", "ntsysadm", "ntappadm").

1.
If establishing the password for the root user, access the login prompt
at the server's console; for all other accounts, access the login prompt
through the ssh remote access protocol. The following prompt is
given:
[<hostname>]login:
2.
Enter <account>.
3.
Enter password (the literal string "password").
4.

Youarerequiredtochangeyourpassword
immediately(rootenforced)
Changingpasswordforroot
(current)UNIXpassword:
5.
Re-enter password (the literal string "password").
6.

NewUNIXpassword:
7.
Carefully enter the initial password for <account>.
8.

RetypenewUNIXpassword:
9.
Carefully re-enter the same initial password as above.
10.
The following system message is given, indicating a successful login.

Authorizedusersonly.Allactivitymaybe
monitoredandreported.
11.
Enter logout to log out of the account.

22

Method of Procedure
6.6 Grub Password (Establish Password)

This section describes the procedure to password for establish Grub (Grand
Unified Boot Loader).
1.
Access the server's login prompt either through a remote access

protocol such as secure shell, or at the server's console, and log in as
the "ntsysadm" user.
2.
Enter grubPWConfig
3.
If prompted for a password, enter the password which was set for the
ntsysadm user in Section 6.5.
4.

Doyouwishtoconfiguregrubbootloaderpassword
configuration?
Enter'c'toconfigure,or'q'toquit[c/q]:
5.
Enter c.
6.

Enterthe"bootloader"password:
7.
Enter the password.
8.

Enterthe"bootloader"passwordagain:
9.
Enter the same password again.
10.
The following message is printed and the command exits:

AddingMD5encryptedpasswordtoGrubconfigfile
(/boot/grub/grub.conf)
11.
The password is now set.
December 03, 2010

23
2010 Avaya Inc.


Method of Procedure
7 Patch Current
This section describes the procedure for applying server platform patches to the
target server, using a patch CD-ROM. This brings the server up to the current
release level.
1.

2.
Enter su , followed by the root password, to become the root user.
3.
Insert the Server Platform Patch CD-ROM into the optical drive tray.
4.
Enter mcpExtractContent.plaat
5.
The following message and prompt is presented:

Thefollowingfileshavebeenfound:
[1]Opticaldrive
[2]Quit
Selectfile[1to2]=>
6.
Enter 1.
7.
All content from the disc is extracted and the script exits.
8.
Enter cd/var/mcp/os/install/images
9.
Enter ls to see a list of files. The file ending in ".iso" is the patch
image file to be used.
10.
Enter patchPlatform.pl<file>.isonp, where <file>.iso is the

above file ending in ".iso".
Hint: command line completion can be used to reduce the amount of typing
required. For example, type patchPlatform.pl followed by the Tab key. This
completes the file name except for the final file extension. Enter isonp to
complete the command and press the Enter key.
11.
The patch image file is accessed and its integrity verified. If the
integrity check fails, then contact the next level of support.
24

12.

Method of Procedure
The version of the running patchPlatform.pl tool is checked to see if it

is out of date with respect to what is available from the selected patch
image file. If so, then the system resident copy is updated with the
version from the patch image file and the tool exits with a message
similar to the following message. If this message is not presented (no
update performed), then continue with step 15.
Thesystemresidentpatchingtool
(patchPlatform.pl)hasbeenupdatedfromversion
x.x.xtoversiony.y.y.Pleasereexecutethe
(updated)"patchPlatform.pl"command.
13.
Re-enter patchPlatform.pl<file>.isonp, as described in step

10.
14.
The patch image file is accessed and its integrity verified.
15.
The patchPlatform.pl tool compares the patches contained in the patch

image file against the current release of the system. If there are no
required patches, the following message is printed, the tool exits, and
the patching procedure is complete:
Noapplicablepatch(es).
Numberofpatchesapplied:0
16. If one or more patches are required, they are listed and then
automatically applied to the system. Once the last patch has been
applied, the server is automatically rebooted.
17.
After the reboot, log into the server (any account) and enter
mcpRelease.pl and verify the reported release level is as expected.
18.
The server patching procedure is now complete.
December 03, 2010

25
2010 Avaya Inc.


Method of Procedure
8 Post Installation Verification

This section provides steps to verify the successful completion of the overall
procedures outlined in this document.
1.
Verify that Network IP Address can be successfully pinged from a

network other than the one hosting this server (verify successful
routing through the hosting default gateway).
2.

3.
Enter the command date.
4.
Verify the reported date and time match the current date and time for
the hosting time zone, accurate to the second. This can be done by
comparing the reported date with another machine which is already
synchronized to the external NTP clock sources.
Note that a continuous display of the time can be presented using the
command watchn1date. Type ctrlc to terminate this command.
5.
If Error! Not a valid link. is a valid IP address, then verify the streaming
of syslogs to a the remote server. Log in to the target server as the
ntsysadm user, and issue the command loggertestmessage. Verify
that a syslog entry is created on the remote server with the text "test
message".
26

Method of Procedure
9 References
This document references the following documents:
1.
102.1.2 AS5300 Initial System Installation
2.
102.3.1 AS5300 Initial System Installation (job aid)
December 03, 2010

27
2010 Avaya Inc.


Method of Procedure

Method of Procedure
Copyright 2010 Avaya

All rights reserved.
Avaya CONFIDENTIAL: The information contained in this document is the property of Avaya. Except as
specifically authorized in writing by Avaya, the holder of this document shall keep the information contained
herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties
and use same for evaluation, operation, and maintenance purposes only.
28

102.1.1 AS5300 2.1 Server Installation: Multimedia Communications Platform AS 5300 R2.1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

102.1.1 AS5300 2.1 Server Installation: Multimedia Communications Platform AS 5300 R2.1

Uploaded by

Copyright:

Available Formats

Multimedia Communications Platform AS 5300 R2.

Document Release Date:

December 03, 2010

Copyright 2010 Avaya