102.1.1_as5300_3.0-server_installation

8/10/2019 102.1.1_AS5300_3.0-Server_Installation

1/30


2/30

102.1.1 AS5300 3.0 Server InstallationDocument Version 0.3 Method of Procedure

December 29, 2011 2011 Avaya Inc. 2 Avaya proprietary use pursuant to company instructions

Revision History

Version Date Description

0.1 10/28/2011 AS 5300 R3.0 initial version. Update for AS 5300 R3.0,based on R2.1 version 1.1

0.2 12/20/2011 Minor changes to reflect new supported hardware

0.3 12/29/2011 Minor changes for wi00967868


3/30

102.1.1 AS5300 3.0 Server InstallationMethod of Procedure Document Version 0.3

3

Table of ContentsRevision 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 .................. ................. .................. ................. .................. ................. . 16

6.2 BIOS Clock .................. ................. ................. .................. ................. .................. ............ 17

6.3 Hardware Environment ................. ................. .................. ................. .................. ............ 18

6.3.1 Reference Server ................................................................................................. 19

6.3.2 Non-Reference (Other) Server ............................................................................. 21

6.4 NTP Clock Configuration ................................................................................................ 22

6.5 Initial Login (Establish Password) ................. .................. ................. .................. ............ 23 6.6 Grub Password (Establish Password) ................. ................. .................. ................. ....... 24

7 Patch Current ....................................................................................................... 26

8 Post Installation Verification .............................................................................. 28

9 References ............................................................................................................ 29


4/30



1 Start HereTo 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" .


5/30


5

2 Overview

2.1 Document ConventionsThe following conventions are used throughout this document.

References to sections in this document are typically of the form:

Section (e.g., Section 1)

where "" is the number of the section. In document text where amore complete reference facilitates the flow (such as an initial reference in anoverview section), the following form is used:

Section "" (e.g., Section 1 "Start Here ")

where "" is the name of the section.

References to documents listed in Section 9 "References" are typically of theform:

[] (e.g., [1] )

where "" is the number of the reference from Section 9. Indocument text where a more complete reference facilitates the flow (such asan initial reference in an overview section), the following form is used:

[] ""(e.g., [1] "102.1.2 AS 5300 Initial System Installation ")

where "" is the title of the referenced document.

In-line text describing output displayed on a login window, console, orgraphical user interface appears as follows: Example in-line output text .

In-line text describing data entered into the terminal or console window, orgraphical user interface, appears as follows: Example in-line input text .

Paragraph text describing output displayed on a login window, console, orgraphical user interface appears as follows:

Example paragraph output text

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

Example paragraph input text


6/30



References to terms and data from [2] "102.3.1 AS 5300 Initial SystemInstallation" are of the following form:

Enter the Network I P Address of the server.

where Network I P Address is a reference to data from a system layout tabfrom [2] .

This document uses the term "target server" to refer to the server undergoingthe installation procedures described in this document.

2.2 Document OverviewThis document describes the procedures to perform the installation of the server

platform software (operating system and base level packages) for a core or AvayaMedia Server for the AS 5300 product.

The methods for performing the initial system installation of an AS 5300 systemare described in [1] "102.1.2 AS 5300 Initial System Installation ". As describedin that document, AS 5300 systems follow one of three basic layouts of softwarecomponents to server hardware, some of which allow for system scaling throughthe installation of additional servers hosting additional AS 5300 applicationcomponents.

The job aid, [2] "102.3.1 AS 5300 Initial System Installation ", is an Excelworkbook data gathering tool which supports the system initial installation

process, and contains tabs for each of the AS 5300 system layouts. Each layout

tab describes server-level data for the basic layout and, where applicable, forscaling beyond that layout. Both this document and [1] reference terms and datafound on those layout tabs for server platform installation.

This document makes no distinction between a server installation conductedduring an initial system installation and a server installation conducted during afuture system expansion. It is assumed that the system layout tab from [2] whichis most appropriate for the installation context (initial installation or futureexpansion) is updated and provides the context for all data references made bythis document.


7/30


7

3 Work FlowThis section provides the work flow to install an AS 5300 core server (the targetserver) with its platform software and to bring it current on patches. Each step inthis procedure refers to a section which provides the specific work instructions toaccomplish that task. A given step must be successfully completed prior tostarting 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" .


8/30



4 Verify PrerequisitesPrior to the execution of the procedures described in the remainder of thisdocument, 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 beenupdated or created.

If this document is being executed within the context of an initial systeminstallation, 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 asystem which has been previously installed, it is required that the layoutwhich is appropriately aligned with the existing system has been identifiedand 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 inthat 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 theinstallation 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).


9/30


9

If the target server is EMServer1 or EMServer2 , then the NTP clock source atthe address Ex tern al Clock Source #1 and, if provided in [2], at addressExtern al Clock Source #2 , must be reachable in order for the target server toreceive its clocking.

If the target server is other than EM Server1 or EM Server2 , then serversEM Server1 and EM Server2 must be reachable by the target server in orderfor the target server to receive its clocking.

A desktop computer, or other server, is available on a network other than theone which is to host the target server, and it must be accessible for login inorder that an ICMP ping can be performed against the target server. This isrequired for post-installation verification.

A desktop computer, or other server, is available and is currentlysynchronized to the same external NTP clock source(s) to be used by thetarget 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 systemcommands 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


10/30



5 PlanningThis 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 ofthe 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 thetarget server is not provided by this document, nor in [2] . It is expected that the

personnel performing the installation procedures will manage these passwords ina manner appropriate to the policies and practices of the host environment.

Refer to document 105.1.1_AS 5300_3.0-Network_Separati on for designatingnetwork VLAN IDs and IP addresses.


11/30


11

6 InstallThis section describes the procedure for installing the target server with the

platform software (operating system and base level packages) from a CD-ROMinstaller disc. Note that all existing data on the target server's disk drive(s) will beerased during this procedure. If required, transfer any files that need to be retainedoff the server prior to executing the following procedures.

Perform the following:

1. Gain access to the server's console using a locally attached keyboardand monitor or a KVM switch.

2. Insert the CD-ROM server platform installer disc into the optical drivetray 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. Enter install-kvm . (if installing a Avaya Media Server onto a legacy

IBM X3550 server from AS 5300 3.0 equipped with 4 GB of memory,the enter install-kvm MAS . This relaxes the checks on memory sizeto allow the install to be performed on this type of server; this isintended for Avaya MS servers only).

5. Wait until the following prompt is given:

Would you like to check the integrity of theinstall media? (Y/N) [Y]?

6. Press the Enter key to accept the "Y" default. Note that if "N" isentered for the above prompt, then a bad CD-ROM disc or opticaldrive may go undetected, resulting in an invalid server installation.

7. If the following message is displayed, then an issue exists with theCD-ROM disc or with the optical drive. In this case, contact the nextlevel of support.

Integrity check failed. This could be due to acorruption in the transfer of the ISO image used


12/30



to burn this disc, a bad burn of the disc, adamaged or dirty disc, or a bad optical drive.Please clean the disc and try again. If theproblem persists, you should obtain a new discand try again and verify the optical drive.

8. If the integrity check passes the following prompt is given:

Would you like to view licensing information?(Y/N) [Y]?

9. If licensing information has already been viewed from a previousserver installation, enter n and continue with the next step. Otherwiseenter y and execute Section 6.1, then continue with the next step.

10. A warning message is printed to indicate the disk(s) which willundergo the installation and that their data will be erased (wiped). Thefollowing prompt is given:

Continue [c], Abort [a]:

11. Enter c . Note that this action will erase all existing data on the attacheddisk 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 continuewith the next step; otherwise enter n and execute Section 6.2, thencontinue 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:

Please enter the number of the install option [1to 3] =>

16. Enter 1 to proceed with manual installation.

17. A System Configuration screen is presented with the prompt:

You will now be prompted to enter configuration datafor this server.


13/30


14/30



Enter IP address:

30. Enter the Network I P Address for the server.

31. The following prompt is given:

Enter subnet prefix length (1-30):

32. Enter the Network Prefi x for the server.


Enter gateway IP address:

34. Enter the Network Defau lt Gateway for the server.

35. A System Console Redirection screen is presented with choices forserial console redirection and the following prompt is given:

Please choose the serial port to be used forsystem console redirection:

1) Serial Port 1 (COM1)2) Serial Port 2 (COM2)3) Do not redirect the system console after

installation

Select an option (1-3):

36. Enter 3 .

37. The Timezone Selection screen is presented and the following prompt is given:

Enter Region (1-62):

38. Determine, from the on-screen menu, the menu number that matchesTimezone F ield1 for the target server, and enter that number.

39. If the Enter Timezone prompt is given, determine, from the on-screenmenu, the menu number that matches Timezone F ield2 for the targetserver and enter that number.

40. A Configuration Validation screen is presented showing thevalues 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 tostep 19 for data re-entry. Note that previously entered data is presentedas defaults to assist with the data entry process.


15/30


15


42. The Syslog Configuration screen is presented with the prompt:

Do you wish to configure a Syslog Server IPaddress (Y/N) [N]?

43. If Syslog IP for the target server does not have a valid IP address, thenenter n and proceed to step 46; otherwise enter y and continue with thenext step.


Enter the Syslog Server IP address:

45. Enter the Syslog I P value.

46.A

Configuration Validation screen is presented showing thevalues entered up until this point in time. If all values are correct, enter

y to accept these values and continue; otherwise, press the Enter keyto accept the default response of "n" to return to step 41 for data re-entry. Note that previously entered data is presented as defaults toassist with the data entry process.

47. A User Accounts & Passwords screen is presented which lists theaccounts which will be created and their default passwords. Press theEnter key to continue.

48. A Configuration Complete screen is presented with the prompt:

Press the Enter Key to continue with theinstallation. . ."

49. The data entry phase of the installation is now complete. Press theEnter key to start the installation and configuration of the server

platform software. No further user input is required until the postinstallation login is performed.

50. Screens showing the partitioning of hard disk(s), formatting of filesystems, 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 is Hostname for the targetserver.

login:

52. Execute Section 6.5 for the "root" account.


16/30



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).


60. This completes the install from CD-ROM for the target server.

6.1 License AttributionThis section describes the procedure to navigate through the installer licenseattribution information during the server platform installation process.


1. Make a selection:

1) Licensing overview2) Summary of open source RPMs and licenses3) Exit

At the Enter Selection => prompt, enter 1 .

2. Press the Enter key repeatedly to page through the licensinginformation until the Enter Selection => prompt is again presented.

3. Enter 2 .

4. Press the Enter key repeatedly to page through the licensinginformation until the Enter Selection => prompt is again presented.

5. Enter 3 to exit. The following prompt is presented:

Do you acknowledge this licensing information?

6. Enter y .

7. Proceed to step 10 in Section 6.


17/30


17

6.2 BIOS ClockThis section describes the procedure to set the time on the BIOS clock during theserver platform installation process.


1. At the prompt Enter the month (1-12) [x]: , enter the numberfor 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 ofthe month (e.g., enter "22" if the current date is March 22), and pressthe Enter key.

3. At the prompt Enter the year (YYYY) [xxxx]: , enter the currentyear, and press the Enter key.

4. At the prompt Enter the hour (0-23) [xx]: , enter the current hourof the current day, and press the Enter key. Note that this uses the 24-hour clock, where the first hour of the day is '0' and the last hour of theday is '23'.

5. At the prompt Enter the minutes (0-59) [xx]: , enter the currentminute of the current hour, and press the Enter key. The first minute ofthe hour is '0' and the last minute of the hour is '59'.

6. The newly entered time is displayed and the following prompt isgiven:

Do you want to keep this date and time (Y/N) [Y]?

7. Enter y .

8. Proceed to step 14 in Section 6.


18/30



6.3 Hardware EnvironmentThis section describes the procedure to set the hardware configuration during theserver platform installation process. The first phase of this part of the target serverinstallation is to classify the server hardware as either a known reference server oras an "Other" (non-reference) server. This classification is usually determined bythe installer itself, but can be overridden by the user performing the installation inthe event that the installer software does not correctly classify the server.

An important aspect of hardware detection and determination is the physical diskdrive 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 membersof the logical RAID disk are seen by the installer as a single disk drive.


1. The Hardware Environment Configuration screen is presented.

2. If the installer presents a message similar to the following, then thetarget server has been detected as a known reference server, andtherefore proceed to step 6:

Detected hardware: IBM-X3550-M2M3Choose "A" to accept or "O" to set the hardwareenvironmentTo "Other" [A]:

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 installerhas not been detected. The default hardware typeof "Other" will therefore be used unlessoverridden below.

Installs based on the "Other" hardware type arefully supported when that hardware meets minimumrequired specifications. "Other" installs do notprovide for the installation of vendor-specificdevice drivers or custom software. Any

requirement for the installation and ongoing(post-installation) maintenance of such softwareis the responsibility of the user performing theinstallation.

1) Other2) IBM-HS203) IBM-HS21


19/30


19

4) IBM-X35505) IBM-X3550-M2M36) Intel-TIGH2U7) HP-Proliant-DL360-G78) Dell-PowerEdge-R610

Hardware type (1-8) [1]:

4. If the target server is, in fact, not a reference server, enter 1 andexecute Section 6.3.2.

5. If the target server is a known reference server, then override theinstaller default of Other by entering the menu number correspondingto the server, and execute Section 6.3.1.

6. If this server is the indicated reference server type, press the Enter keyand execute Section 6.3.1; otherwise enter o and continue with thenext step.

7. The user is overriding the detected server type, classifying the targetserver as an "Other" server. The following message is presented and

prompt are given:

Installs based on the "Other" hardware type arefully supported when that hardware meets minimumrequired specifications. "Other" installs do notprovide for the installation of vendor-specificdevice drivers or custom software. Anyrequirement for the installation and ongoing(post-installation) maintenance of such softwareis the responsibility of the user performing theinstallation.

Is this information correct (Y/N) [N]?

8. Enter y and execute section 6.3.2.

6.3.1 Reference ServerThis section describes the procedure to set the hardware configuration where thetarget server has been detected as a reference server, either by the installersoftware, or overridden by the user.


1. The message and prompt similar to the is presented:

Hardware Environment: IBM-X3550-M2M3


20/30



Is this correct (Y/N) [N]?

2. Enter y .

3. A message is displayed indicating the disk(s), and their sizes, whichhave been detected. Disk sizes are reported in GB (InternationalSystem/SI) and GiB (binary units).

4. If two disks have been detected and the reference server does notsupport 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 thefollowing disk:

/dev/ (xx GB, XX GiB)

Press ENTER to continue

5. If a single disk has been detected and the reference server requires twodisks (for disk mirroring via software RAID-1), then the followingmessage is displayed and the installation is aborted. Contact the nextlevel of support to correct the hardware configuration.

This installation requires software RAID, butonly one disk drive has been detected.

Aborting installation.

Do you want to see the log file on this console(Y/N) [N]?

6. Otherwise, the physical disk configuration matches that required forthe given reference server. A message is presented with the disk(s)which will be undergoing installation and the usable disk space for thesoftware RAID-1 mirror (if software RAID-1 is applicable), and thefollowing prompt is displayed:

Press ENTER to continue

7. Press Enter and continue with step 15 in Section 6.


21/30


21

6.3.2 Non-Reference (Other) ServerThis section describes the procedure to set the hardware configuration where thetarget server has been detected as a non-reference ("Other") server, either by theinstaller software, or overridden by the user.


1. The following message and prompt are displayed:

Hardware Environment: OtherIs this correct (Y/N) [N]?

2. Enter y .

3. A message is displayed indicating the disk(s), and their sizes, whichhave been detected and which will undergo installation. Disk sizes arereported in GB (International System/SI) and GiB (binary units).

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 step15 in Section 6.

Press ENTER to continue. . .

5. If two disks are present, then the following prompt is given:

Do you want to set up S/W RAID-1 between thesetwo disks? (Y/N)? [Y]?

6. The standard configuration for MCP servers is for redundant diskdrives. If the first reported disk is actually a hardware RAID logicaldisk of two physical disks, then enter n and continue with the nextstep. Otherwise, it is recommended to enter y , and continue with step 9in order to configure software RAID-1 between the two reported diskdrives.

7. A message is presented indicating the size of the disk drive to beinstalled 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, theirindividual 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:


22/30




10. Press the Enter key to continue to continue with step 15 in Section 6.

6.4 NTP Clock ConfigurationThis section describes the procedure for configuring the NTP (Network TimeProtocol) settings during the server platform installation process.


1. A Network Time Protocol (NTP) Configuration screen is presented with choices on setting up clock sources, and with thefollowing prompt:

Please indicate the Clock Source function of thisserver.

1) Primary Clock Source server (primary SystemManager server machine)

2) Secondary Clock Source server (secondary SystemManager server machine)

3) This server is NOT a Clock Source server (allother server machines)

Select an option (1-3):

2. If this is EM Server1 , then enter 1 and continue with the next step; ifthis is EMServer2 , then enter 2 and continue with the next step;

otherwise enter 3 and proceed to step 11.

3. The prompt Select an option (E, I): is given to select betweeninternal or external clock sources for the system. Enter e .


How many external clock sources would you like toreference (1-2) [1]?

5. If both Extern al Clock Source #1 and Ex tern al Clock Source #2 haveIP addresses then enter 2, otherwise enter 1.

6. A prompt of the following form is given for each IP address to beentered:

Enter Clock Source IP address #:

7. Enter the IP address for External Clock Sour ce #1 then, if prompted,for Extern al Clock Source #2 .


23/30


24/30



You are required to change your passwordimmediately (root enforced)Changing password for root(current) UNIX password:

5. Re-enter password (the literal string "password").


New UNIX password:

7. Carefully enter the initial password for .


Retype new UNIX password:

9. Carefully re-enter the same initial password as above.

10. The following system message is given, indicating a successful login.

Authorized users only. All activity may bemonitored and reported.

11. Enter logout to log out of the account.

6.6 Grub Password (Establish Password)This section describes the procedure to password for establish Grub (Grand

Unified Boot Loader).Perform the following:

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 asthe "ntsysadm" user.

2. Enter grubPWConfig

3. If prompted for a password, enter the password which was set for thentsysadm user in Section 6.5.


Do you wish to configure grub boot loaderpassword configuration?

Enter 'c' to configure, or 'q' to quit [c/q]:


25/30


25

5. Enter c .


Enter the "bootloader" password:

7. Enter the password.


Enter the "bootloader" password again:

9. Enter the same password again.

10. The following message is printed and the command exits:

Adding MD5 encrypted password to Grub config file(/boot/grub/grub.conf)

11. The password is now set.


26/30



7 Patch CurrentThis section describes the procedure for applying server platform patches to thetarget server, using a patch CD-ROM. This brings the server up to the currentrelease level.



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.pl aat

5. The following message and prompt is presented:

The following files have been found:[1] Optical drive[2] Quit

Select file [1 to 2] =>

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 patchimage file to be used.

10. Enter patchPlatform.pl .iso np , where .iso is theabove 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 iso np to complete the command and press the Enter key.

11. The patch image file is accessed and its integrity verified. If theintegrity check fails, then contact the next level of support.

12. The version of the running patchPlatform.pl tool is checked to see if itis out of date with respect to what is available from the selected patch


27/30


27

image file. If so, then the system resident copy is updated with theversion from the patch image file and the tool exits with a messagesimilar to the following message. If this message is not presented (noupdate performed), then continue with step 15.

The system-resident patching tool(patchPlatform.pl) has been updated from versionx.x.x to version y.y.y. Please re-execute the(updated) "patchPlatform.pl" command.

13. Re-enter patchPlatform.pl .iso np , as described in step10.

14. The patch image file is accessed and its integrity verified.

15. The patchPlatform.pl tool compares the patches contained in the patchimage file against the current release of the system. If there are no

required patches, the following message is printed, the tool exits, andthe patching procedure is complete:

No applicable patch(es).

Number of patches applied: 0

16. If one or more patches are required, they are listed and thenautomatically applied to the system. Once the last patch has beenapplied, 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.


28/30



8 Post Installation VerificationThis 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 anetwork other than the one hosting this server (verify successfulrouting through the hosting default gateway).


3. Enter the command date .

4. Verify the reported date and time match the current date and time forthe hosting time zone, accurate to the second. This can be done bycomparing the reported date with another machine which is alreadysynchronized to the external NTP clock sources.

Note that a continuous display of the time can be presented using thecommand watch n1 date . Type ctrl-c to terminate this command.

5. If Syslog IP is a valid IP address, then verify the streaming of syslogsto a the remote server. Log in to the target server as the ntsysadm user,

and issue the command logger test message . Verify that a syslogentry is created on the remote server with the text "test message".


29/30


29

9 ReferencesThis document references the following documents:

1. 102.1.2 AS 5300 Initial System Installation

2. 102.3.1 AS 5300 Initial System Installation (job aid)


30/30


102.1.1 AS 5300 Server Installation Method of Procedure

Copyright 2010 Avaya All rights reserved.

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

102.1.1_as5300_3.0-server_installation

Documents