Академический Документы
Профессиональный Документы
Культура Документы
0
102.1.1 AS 5300 3.0 Server Installation
Method of Procedure
Product Release:
AS 5300 R3.0
Document Version:
0.3
Document Status:
Released
Security Classification:
Avaya Confidential
Revision History
Version
Date
Description
0.1
10/28/2011
0.2
12/20/2011
0.3
12/29/2011
Table of Contents
Revision History .......................................................................................................... 2
Table of Contents ........................................................................................................ 3
1 Start Here ................................................................................................................ 4
2 Overview ................................................................................................................. 5
2.1
2.2
6.2
6.3
Hardware Environment...................................................................................................18
6.3.1
6.3.2
6.4
6.5
6.6
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".
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 AS 5300 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: Example in-line output text.
In-line text describing data entered into the terminal or console window, or
graphical user interface, appears as follows: Example in-line input text.
Paragraph text describing output displayed on a login window, console, or
graphical user interface appears as follows:
Example paragraph output text
Paragraph text describing data entered into a terminal or console window, or
graphical user interface, appears as follows:
Example paragraph input text
5
References to terms and data from [2] "102.3.1 AS 5300 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.
3 Work Flow
This section provides the work flow to install an AS 5300 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.
2.
3.
4.
5.
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 AS 5300
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:
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).
2011 Avaya Inc.
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
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_AS 5300_3.0-Network_Separation for designating
network VLAN IDs and IP addresses.
10
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.
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:
Welcome to the MCP Core Linux System Installer
and provides the following command line prompt:
boot:
4.
5.
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.
9.
10.
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:
Do you want to keep this date and time (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.
15.
16.
17.
12
19.
20.
21.
22.
Press the Enter key to accept the default value and to continue.
23.
If presented with the prompt Enter the first slave [<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.
25.
26.
27.
28.
29.
13
Enter IP address:
30.
31.
32.
33.
34.
35.
36.
Enter 3.
37.
38.
Determine, from the on-screen menu, the menu number that matches
Timezone Field1 for the target server, and enter that number.
39.
40.
14
41.
42.
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.
45.
46.
47.
48.
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.
51.
52.
53.
54.
55.
56.
57.
58.
59.
60.
This completes the install from CD-ROM for the target server.
Make a selection:
1) Licensing overview
2) Summary of open source RPMs and licenses
3) Exit
At the Enter Selection => prompt, enter 1.
2.
3.
Enter 2.
4.
5.
6.
Enter y.
7.
16
At the prompt Enter the month (1-12) [x]:, enter the number
for the current month, where '1' is January, and '12' is December.
2.
At the prompt Enter the day (1-xx) [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 Enter the year (YYYY) [xxxx]:, enter the current
year, and press the Enter key.
4.
At the prompt Enter the hour (0-23) [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'.
5.
At the prompt Enter the minutes (0-59) [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.
7.
Enter y.
8.
17
2.
3.
If the installer does not detect the server as a known reference server,
then the following message is presented:
A specific hardware type known by this installer
has not been detected. The default hardware type
of "Other" will therefore be used unless
overridden below.
Installs based on the "Other" hardware type are
fully supported when that hardware meets minimum
required specifications. "Other" installs do not
provide for the installation of vendor-specific
device drivers or custom software. Any
requirement for the installation and ongoing
(post-installation) maintenance of such software
is the responsibility of the user performing the
installation.
1) Other
2) IBM-HS20
3) IBM-HS21
2011 Avaya Inc.
18
4)
5)
6)
7)
8)
IBM-X3550
IBM-X3550-M2M3
Intel-TIGH2U
HP-Proliant-DL360-G7
Dell-PowerEdge-R610
If the target server is, in fact, not a reference server, enter 1 and
execute Section 6.3.2.
5.
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.
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:
Installs based on the "Other" hardware type are
fully supported when that hardware meets minimum
required specifications. "Other" installs do not
provide for the installation of vendor-specific
device drivers or custom software. Any
requirement for the installation and ongoing
(post-installation) maintenance of such software
is the responsibility of the user performing the
installation.
Is this information correct (Y/N) [N]?
8.
Enter y.
3.
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.
Software RAID is unsupported for this install.
The second disk drive will therefore not be used.
This machine will be configured using the
following disk:
/dev/<disk> (xx GB, XX GiB)
Press ENTER to continue
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.
This installation requires software RAID, but
only one disk drive has been detected.
Aborting installation.
Do you want to see the log file on this console
(Y/N) [N]?
6.
7.
20
2.
Enter y.
3.
4.
5.
6.
7.
8.
9.
21
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.
4.
5.
6.
7.
22
9.
10.
11.
12.
13.
14.
15.
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.
4.
23
6.
7.
8.
9.
10.
11.
2.
Enter grubPWConfig
3.
If prompted for a password, enter the password which was set for the
ntsysadm user in Section 6.5.
4.
24
Enter c.
6.
9.
10.
11.
25
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.
Perform the following:
1.
2.
3.
Insert the Server Platform Patch CD-ROM into the optical drive tray.
4.
5.
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.
11.
The patch image file is accessed and its integrity verified. If the
integrity check fails, then contact the next level of support.
12.
26
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.
The system-resident patching tool
(patchPlatform.pl) has been updated from version
x.x.x to version y.y.y. Please re-execute the
(updated) "patchPlatform.pl" command.
13.
14.
15.
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.
27
2.
3.
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 watch n1 date. Type ctrl-c to terminate this command.
5.
28
9 References
This document references the following documents:
1.
2.
29
30