24-8062 GSM NSS APS Instalation

7/30/2019 24-8062 GSM NSS APS Instalation

1/60

Pkgid: 0000007

PROPRIETARY INFORMATION: The information contained in this documentis the property of Nortel. Except as specifically authorized in writing, the holderof this document shall keep all information contained herein confidential andshall protect same in whole or in part from disclosure and dissemination to thirdparties.

Nortel 2006All Rights Reserved

GSM/UMTS NSS APS11 Installation

Installation Method 24-8062

May 10, 2006


2/60


3/60

GSM/UMTS NSS APS11 Installation / 1

May 10, 2006 Method 24-8062

Table of Contents

1.0 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.2 Sequence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3 Reason for Reissue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2.0 Material Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

2.1 Required Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.2 Tools & Test Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.3 Customer Supplied Materials / Client Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2.3.1 Customer Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.4 Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3.0 Precaut ions and Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.1 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93.2 Preparations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

3.3 Check List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

4.0 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104.1.1 Server Hardware Baseline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104.1.2 Server Software Baseline. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

4.2 SPFS Common Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114.2.1 System Cabling (N240) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114.2.2 Connecting to the Sun Netra N240. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Procedure 1 Connecting to the N240 Through the Console. . . . . . . . . . . . . . . . 124.2.3 Initial Power Up (N240) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

4.2.3.1 N240 Power Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134.2.4 SPFS Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Procedure 2 SPFS Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154.2.5 SPFS Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Procedure 3 SPFS Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204.2.6 Modify System Information Using the CLI Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Procedure 4 Using the CLI Tool to Modify System Information. . . . . . . . . . . . . 214.2.7 Using the CLI Tool to Modify/Setup NTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Procedure 5 Modify/Setup NTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274.2.8 Creating a User for Login Verification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Procedure 6 Creating a User Account for Nortel . . . . . . . . . . . . . . . . . . . . . . . . 294.2.9 Using the CLI Tool to Modify DNS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4.2.9.1 Modify DNS Configuration via the CLI Tool . . . . . . . . . . . . . . . . . . . . . . . . . . 31Procedure 7 Modify the DNS Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4.2.10 Certificate Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.2.10.1 Certificate Authority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Procedure 8 HTTPS Certificate Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4.2.10.2 Self Signed Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Procedure 9 Self Signed Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

4.2.11 Patching Sub Element (PSE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Procedure 10 PSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.2.12 SPFS Patching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Procedure 11 SPFS Patching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42


4/60

2 /GSM/UMTS NSS APS11 Installation

Method 24-8062 May 10, 2006

4.2.13 NPM Removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Procedure 12 NPM Removal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4.2.14 Client PC Setup for "Island DNS" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Procedure 13 Client PC Setup for Island DNS . . . . . . . . . . . . . . . . . . . . . . . . . 45

4.3 APS Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Procedure 14 Installing and Configuring the APS Application. . . . . . . . . . . . . . 464.4 APS Application Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

4.4.1 Client Network Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Procedure 15 Client Network Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

4.4.2 APS EM Login Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Procedure 16 APS Application Launch Point Verification . . . . . . . . . . . . . . . . . 51

4.5 Oracle Data Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Procedure 17 Oracle Data Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

4.6 Sun N240 Back-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Procedure 18 Full System Back-up for Sun N240. . . . . . . . . . . . . . . . . . . . . . . 54

5.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

6.0 Appendices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Appendix A List of Time Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Last Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58


5/60


May 10, 2006 Method 24-8062

Figures

Figure 1 Netra 240 Server Front and Rear View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14


6/60


Method 24-8062 May 10, 2006

Tables

Table 1 Tools & Test Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Table 2 APS Install. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7


7/60


May 10, 2006 Method 24-8062

1.0 General Information

1.1 Description

Purpose: The purpose of this method is to provide the procedures forinstalling and commissioning the Audio Provisioning Server (APS)Media Gateway for GSM NSS Solutions.

Equipment:

Sun N240 - NTRX51LC

Application: This method applies to initial and extension applications.This method is currently only applicable to the APS11 release.

Service Impact:None

Skill Level Requirement: This method requires a minimum skill levelof a Field Technician 3 or higher to perform the installation procedures.

1.2 Sequence

The installation of the APS is dependent on several other networkelements to be installed and commissioned before the work outlined inthis method can be completed. Refer to the appropriate Solutionplanning guide for overall solution installation sequence:

This method is to be performed after the following methods:

Method 04-0766, COAM Physical Installation

Method 26-6232, ERS 8600 Commissioning for CS2K

Installation Methods can be found at: http://gis.us.nortel.com

1.3 Reason for Reissue

This is the initial release of this IM.

This IM closes the following CRs:


8/60


Method 24-8062 May 10, 2006

2.0 Material Requirements

2.1 Required Documents

1. Network Spec Book showing addressing schemes and networkarchitecture.

2. Method 0000007-45-0982, Global Workmanship Manual

3. Method 0000007-24-0167, Patching Using NPM

4. Regional Installation Safety Manuals (ISM). Contact your local siterepresentative to obtain a copy.

For example:

Americas - Field Operations Safety Manual (SOP 030)

EMEA Environmental Health & Safety

Asia-Pacific Environmental Health & Safety

2.2 Tools & Test Sets

The Tools and Test Sets listed in Table 1 are required to perform thismethod.

Table 1 Tools & Test Sets

Tool /Test Set

#

Qty. Description

E003389 1 Installation Data Toolkit


9/60


May 10, 2006 Method 24-8062

2.3 Customer Supplied Materials / Client Information

The following Client Workstation(s) are supported:

Microsoft Windows NT 4, 98, 2000 & XP

2.3.1 Customer Information

Successful configuration and implementation of the APS is dependenton correct customer supplied information. This information must beavailable at the start of this method. Using the site specific Spec Book,completely fill in the required tables with all customer suppliedinformation depending on the intended configuration of the servers.

Table 2 APS Install

System Variable Value [defaults in brackets]

[General Information]

SPFS Server Gateway Router IP Address

SPFS Server Subnet Mask

SPFS Server IP Address

SPFS Server HostName

APS Applicat ion IP Address (This may be the same as

the SPFS Server IP Address or i t may be a new IP)

Time Zone (Appendix B)

Office CLLI

DNS - Requi red

DNS-Domain Name required

Server IP Addresses 1

2

3

Minimum required is 1

Search List 1

2

3

Minimum required is 1

NTP Server

Primary NTP Server IP Address

Secondary NTP Server IP Address

HTTP (CA) Certi ficate Files

Cert. file name (place in root d ir.) optional

Key file name (place in root dir.) optional


10/60


Method 24-8062 May 10, 2006

2.4 Software

For ESD (Electronic Software Delivery), refer to NTP, NN10440-450for additional information.

APS11

Audio Provisioning Server - APS11.0 installation CD

SPFS090 - 3 CDs

No other materials are required to perform this method.

Self Assigned Certif icateServer Country Code optional

Server State optional

Server City optional

Company Name optional

Company Department optional

Company FQDN optional

Company Email Address optional

Table 2 APS Install

System Variable Value [defaults in brackets]


11/60


May 10, 2006 Method 24-8062

3.0 Precautions and Preparations

3.1 Precautions

1. Observe the general safety precautions against personal injury andequipment damage outlined in the regional Installation Safety Manual atall times.

2. Prior to integrating any equipment into the network it is critical to verifythe IP Address assigned to the new equipment if it is not alreadyassigned to existing equipment on the network. A Ping test should beperformed prior to assigning IP Addresses to any equipment to verifythe IP Address is not currently assigned. Verify no response is receivedwhen performing the Ping test prior to integrating any equipment intothe network.

3.2 Preparations1. It is strongly recommended that this method be read in its entirety before

starting the operations presented herein.

2. Prior to starting the operations presented in this method, arrange allmaterials, tools, and test equipment at the work location so as tominimize fatigue and inconvenience.

3.3 Check List

Verify the following items have been received and/or accomplished

before proceeding with the procedure.F HTTPS Certificates for the server (x.509)F All Client and server software is on siteF Completion of Section 2.3.1.F DNS is enabled for the solution - DNS entries must be provisioned

on the DNS server for APS prior to performing this IM.


12/60


Method 24-8062 May 10, 2006

4.0 Procedure

4.1 Overview

SPFS (Server Platform Foundation Software) refers to the NCLsoftware package that contains base operating system and commontools, libraries and server functions used by EML applications.Common tools include PM Poller and EMS Proxy Services.

APS (Audio Provisioning Server) - refers to the NCL softwarepackage that contains the APS application. This software enables thecarrier to provision announcements on the UAS and Media Servers.

4.1.1 Server Hardware Baseline

Netra 240 Platform

2 x 1.28 GHZ Ultra Sparc IIIi processors 1 MB Cache per CPU

4 GB DDR RAM

2 x 72 GB Hard drives (hot swappable)

DVD-RW - 2X

2 Serial ports (1 connected to RJ45, 1 connected to DB9)

2 USB ports

1 PCI slot (on motherboard) 2 PCI slots (on PCI riser)

4 x 10/100/1000 Ethernet

4.1.2 Server Software Baseline

APS requires the Nortel built software/OS called Server PlatformFoundation Software (SPFS).

Matching releases of APS and SPFS are required. For example, usingthe SPFS09 version of SPFS with the APS11 version of APSissupported.


13/60


May 10, 2006 Method 24-8062

4.2 SPFS Common Procedures

4.2.1 System Cabling (N240)

The system cabling section applies to APS initial installations andincludes instructions for N240 servers.

1. Refer to IM 04-0766 for the Physical cable routing instructions.

2. Refer to IM 26-0598 for the Physical termination instructions.

3. Following the Job specs, connect the CAT 5 Ethernet cables into theappropriate ports. Please note the names of the interfaces:

Simplex system:

bge 0 - Not used

bge 1 - Connected to LAN Router 0 bge 2 - Not used

bge 3 - Connected to Lan Router 1


14/60


Method 24-8062 May 10, 2006

4.2.2 Connecting to the Sun Netra N240

Perform Procedure 1 to connect to either the N240 for all APSinstallations.

Using the data toolkit or Sun supplied cables, you will initially connect

to the N240 server using a PC computer or laptop. This section shouldonly be used once to bring the Sun Netras online and onto the IPnetwork. Once completed, any further configuration should be donethrough the "Telnet" application unless instructed otherwise.

Connection to the Sun N240 will be established using a RJ-45 SerialCable and a RJ45-DB9 adapter. Connect one end of the RJ45 Serialcable to the N240 Serial MGT port (located on the rear of the Netra).Connect the other end to the adapter and then to the client PC/FT laptop.

Procedure 1 Connecting to the N240 Through the Console

Step Action Observation

1 Open a Hyperterminal session to the server.

Launch the Hyperterm application.

Enter APS in the Connection Description window and click [OK].

In the Connect To window, select COM1 from the Connect using menu and click [OK].

In the COM1 Properties window select the following port settings and click [OK].

i. Bits per second: 9600

ii. Data bits: 8

iii. Parity: None

iv. Stop bits: 1

v. Flow Control: Xon / Xoff

2 If you are connected to a Sun N240 that is currently running, you should see a log in prompt on the

screen. If this is an initial install, you can continue to the next section "Initial Power Up".


15/60


May 10, 2006 Method 24-8062

4.2.3 Initial Power Up (N240)

The initial power up section applies to all APS initial installations andincludes instructions for N240 servers.

4.2.3.1 N240 Power Up

Prior to connecting to the N240, verify that the circuit breaker poweringthe Netra 240 Server is in the "OFF" position.

A cross reference between the BIP breaker and Netra 240 Server isdefined by the frame type. Refer to the job drawings or frameconfiguration method for this information.

Figure 1 Netra 240 Server Front and Rear View

1. Verify that the Tera Term Pro or Hyperterm is on the PC/laptop isrunning and connected to the Console port of the N240.

2. Turn the breakers to the ON position for the N240.

3. Press the power button on the front of the Unit 0 N240.

4. Verify the system is powering up correctly by looking at the LEDs onthe front of the N240.

5. At the workstation, watch the Hyperterm screen for error messages. Atthe conclusion of testing, firmware automatically attempts to


16/60


Method 24-8062 May 10, 2006

reconfigure the system, omitting any parts of the system that have faileddiagnostics. If there are no faults, or if firmware completes a successfulreconfiguration in response to detected faults, the system boots.

Note: If text does not appear on the screen, there may a problem withthe Hyperterm connection. Please verify the Hyperterm is running andcables are securely fastened to the machines. If problems persistscontact your next level of support.

6. When the self-test completes, the POWER LED should remainpermanently ON. If the system runs but needs service, all FAULT LEDswill be on. In a complete failure, no LEDs will light. In this case, contactyour next level of support.


17/60


May 10, 2006 Method 24-8062

4.2.4 SPFS Installation

Perform the following procedure to load SPFS for APS11 installations.

Procedure 2 SPFS Installation


1 Ensure that you are at the "{0} ok" prompt. Refer

to Procedure 1 to perform a Control Break.

2 Insert Disk 1 of the SPFS0** (090) CD set into

the DVD drive on Unit 0.

3 Boot the cdrom device. This step takes

approximately 5 minutes to complete.

For standard installations perform the following:

{0} ok boot cdrom

(example response)

Boot device: /pci@1e,600000/ide@d/cdrom@0,0:f File

and args: -r

Can't read disk label.

Can't open disk label package

Can't open boot device

{0} ok

{0} ok

{0} ok

{0} ok boot cdrom

Boot device: /pci@1e,600000/ide@d/cdrom@0,0:f File

and args: -r

SunOS Release 5.8 Version Generic_108528-18 64-bit

Copyright 1983-2001 Sun Microsystems, Inc. All rights

reserved.

Hardware watchdog enabled

Configuring /dev and /devices

Using RPC Bootparams for network configuration

information.Skipping interface bge3

Skipping interface bge2



/

This CD contains software that under the terms of your

license agreement

with Nortel Networks is licensed for use only on Nortel

Networks OAM&P servers.

Type "ok" to acknowledge this restriction on your use of

the software.

Any other input will halt the installation of this software.


18/60


Method 24-8062 May 10, 2006

4 Type ok then press [Enter] to acknowledgerestriction on your use of the software.

{0} ok ok

(example response)

Please select a server profile for this system

cbm: Next Generation SDM

cbm800: Core & Billing Manager 800

cbm850: Core & Billing Manager 850

cs2kaps: Combined CS2000 Management Tools

and APS

cs2kmt: Standalone CS2000 Management Tools or

Standalone IEMS

iemscs2k: Combined CS2000 Management Tools,

APS and IEMS

mg9kem: Media Gateway 9000 Element Manager

Enter the server profile for this system:

( cbm cbm800 cbm850 cs2kaps cs2kmt iemscs2k

mg9kem)

5 Enter cs2kaps as the profile type and press [Enter]

(example response)

Installing with server profile "****** Profile selected********"

Will this system be a cluster? [no]

6 Enter no then press [Enter] to indicate that the

system is simplex.

(example response)

Install can proceed with factory default values for network

configuration or you may specify the network

configuration now.

Use factory default network configuration? [yes]

7 Enter yes then press [Enter] to proceed with thefactory default values.

yes

(example response)

Simplex:

Current settings for this install

server profile: Combined CS2000 Management Tools &

APS

hostname: sspfs_svr

ip address: 10.10.10.5

netmask: 255.255.255.0

router: 10.10.10.1

DNS: NOT USED

timezone: US/Eastern

database server: 10.10.10.11

Enter "ok" to accept current settings

Enter anything else to re-enter settings

8 Enter ok then press [Enter] to accept the current

settings.

ok

Note: Starts the installation Process - continue to

next step.

(example response)

SSPFS Configuration complete

The system is coming up. Please wait.

...................

...................




19/60


May 10, 2006 Method 24-8062

9 The installation of the first CD will takeapproximately 25 minutes.

There is no action required until the observation

to the right appears on the session.

Note: The system will eject the DISK 1 CD

automatically after completing the next step.

Setting /dev/tcp tcp_rev_src_routes to 0

starting rpc services: rpcbind done.

Setting default IPv4 interface for multicast: add net 224.0/

4: gateway sspfs_svr

syslog service starting.

Starting Web Start Launcher in Command Line Mode.

Please specify the media from which you will install

Solaris 9 Software 2 of 2 (9/04 SPARC Platform Edition).

Alternatively, choose the selection for "Skip" to skip this

disc and go on to the next one.

Media:

1. CD/DVD

2. Network File System3. Skip

Media [1]:

10 Enter 1 then press [Enter] to select CD/DVD as

the Media type for the installation of Solaris 9

and then hit Enter.

Media [1]: 1

Please insert the CD/DVD for Solaris 9

Software 2 of 2 (9/04 SPARC Platform

Edition)

Note: Note: This is the 2nd CD of 3 in the SPFS

set).

After you insert the disc, please press Enter.

Enter S to skip this disc and go to the next one.

To select a different media, enter B to go back.

11 Remove the SPFS Disk 1 CD from the SPFS

server.

12 Place the SPFS Disk 2 CD (This is the 2nd SPFS

CD in the set of 3, not a Solaris CD) into the

drive and then press [Enter]. This step takes

approximately 15 minutes to complete.

Reading Solaris 9 Software 2 of 2 (9/04 SPARC Platform

Edition)..../

Launching installer for Solaris 9 Software 2 of 2 (9/04

SPARC Platform Edition. Please Wait...

Installing Solaris 9 packages (part 2)

-1%------25%------50%------75%-------100%

Installation details:

Product Result More Info

1. Solaris 9 packages (part 2) Installed Available

2. Done

Enter the number corresponding to the desired selection for

more information, or enter 2 to continue [2]:

13 Enter 2 to continue with the installation. {"!" exits}




20/60


Method 24-8062 May 10, 2006

14 Press [Enter] to reboot the system. Theinstallation of the Solaris Patches will start after

the system reboots.

Mar 4 13::09:24 sspfs_svr reboot: rebooted by root

Mar 4 13:09:24 sspfs_svr syslogd: going down on signal

15

Mar 4 13:09:24 rpcbind: rpcbind terminating on signal.

syncing file systems... done

rebooting...

res

LOM event: +1h36m23s host resetting

15 The installation of the second CD will take

approximately 20 minutes.

There is no action required until the system gives

a prompt to enter the third CD.

Done Installing Solaris Patches...

Insert SSPFS Deadstart CDROM Disk 3 in the Drive

Type "ok" when Ready:

16 Remove the SPFS Disk 2 CD from the SPFSserver.

17 Place the SPFS Disk 3 CD into the drive.

18 Enter ok then press [Enter] to start the

installation of the third SPFS CD.

ok

Note: Starts the installation Process - continue to

next step.

(example response)

Copying CDROM contents on to hard drive, this may take

a while

x.,0 bytes, 0 tape blocks

x./08+08_upgrade symbolic link to Scripts/

09_08_upgrade.ksh

.

.

Adding NTJava (Core Software Package 10 of 17)

Unzipping NTJava From The Cdrom.......................

Installing NTJava Package...

.....

Done Installing NTJava Package...

.

.

19 The installation of the third CD will take

approximately 50 minutes.

Note: You may be required to press enter to have the

login prompt reprinted to the screen after the

reboot.

After the installation of the third CD the database

will begin to initialize. The system indicates thatthe initialization will take more than 30 minutes.

The database will take approximately 75

minutes to initialize.

(example response)

......

.....

console login:




21/60


May 10, 2006 Method 24-8062

20 Login to the Server using the default root userand password.

user: root

password: root

(example response)

Last login: **data** on console

**date** Hostname login: ROOT LOGIN /dev/console

Sun Microsystems Inc. SunOS 5.8 Generic Patch

December 2002

HostName:/>

21 Remove the SPFS Disk 3 CD from the SPFS

server.




22/60


Method 24-8062 May 10, 2006

4.2.5 SPFS Verification

In this procedure, the server is checked to ensure that the correct SPFSversion has been loaded on the server. The APS application requires theSPFS load to be installed prior to installation (SPFS contains the Solarisoperating system). This section will also check any MaintenanceRelease loads.

Procedure 3 SPFS Verification


1 Log onto the server using Hyperterm or

TeraTerm.

must log in as maint first

login: rootpassword: root

SunOS 5.9

SSPFS Version: 0* Build: *********

login:

2 Verify that your system is running the correct SN

platform.

#echo $SSPFS_VERSION

Note: If the proper release is not loaded, then SPFS

must be reloaded using the previous

procedure.

SPFS09 version of SPFS is required for

APS11

3 Verify that your system has the correct profile.

#echo $PROFILE

Note: If the system fails to identify the profile or it is

not at the correct profile, repeat the previous

procedure.

The profile must be cs2kaps

4 Verify that the auto-boot option is set to "true."

#eeprom auto-boot?

If it is set to false, change the auto-boot option to

true from false using the following commands.

#eeprom auto-boot?=true

#eeprom auto-boot?

auto-boot?=true

5

6 End of Procedure.


23/60


May 10, 2006 Method 24-8062

4.2.6 Modify System Information Using the CLI Tool

If this is an initial stand alone server, the Laptop/PC must be connecteddirectly to the console to modify customer data on the server. After thesystem has been configured and is online, you may choose to disconnectfrom the console and use a Telnet session to communicate with theserver.

Procedure 4 Using the CLI Tool to Modi fy System Information (Page 1 of 6)


1 Ensure that you are logged in as the root user.

#su -

#root

#

2 Enter the cli menu.

#cliCommand Line Interface1 - View

2 - Configuration

3 - Other

X - exit

select -

3 Select Configuration from the cli menu. Configuration1 - NTP Configuration

2 - Apache Proxy Configuration

3 - DCE Configuration

4 - OAMP Application Configuration

5 - CORBA Configuration

6 - IP Configuration

7 - DNS Configuration8 - Syslog Configuration

9 - Database Configuration

10 - NFS Configuration

11 - Bootp Configuration

12 - Restricted Shell Configuration

13 - Security Services Configuration

14 - Login Session

15 - Location Configuration

16 - Cluster Configuration

17 - Succession Element Configuration

18 - snmp_poller (SNMP Poller Configuration)

19 - backup_config (Backup Configuration) (SN09 only)

X - exit

select - x

4 Select Location Configuration from the

Configuration menu.

Location Configuration

1 - chg_tz (Change Timezone)

2 - sys_loc (System Location)

X - exit


24/60


Method 24-8062 May 10, 2006

5 Select chg_tz (Change Timezone) from theLocation Configuration menu.

=== Executing "chg_tz"

WARNING: Changing the timezone will require a reboot

Current setting:

Timezone: US/Eastern

Enter the timezone for this host (default: US/Eastern):

6 Enter the office . New setting:Timezone: US/Eastern

Enter "ok" to commit changes

Enter "quit" to exit


7 Enter ok to commit the changes or anything elseto modify the settings

EnterX to return to the Configuration menu.

Configuration1 - NTP Configuration






7 - DNS Configuration

8 - Syslog Configuration






14 - Login Session





X - exit

select -

8 Exit the Configuration menu.

#X

Command Line Interface

1 - View

2 - Configuration

3 - Other

X - exit

select -

9 Exit the cli menu.

#X

#

Procedure 4 Using the CLI Tool to Modify System Information (Page 2 of 6)



25/60


May 10, 2006 Method 24-8062

10 Verify the date on the server:

#date

To change time if not current:

#date MMDDHHMMYY

(Month-Day-Hour-Min-Year)

Example of change:

date 1002120203

Thu Oct 2 12:02:00 BST 2003

Verify the date change on the server:

#date

(Example only)

Fri Oct 2 16:14:30 EDT 2004


#cli


1 - View

2 - Configuration

3 - Other

X - exit

select -





5 - CORBA Configuration6 - IP Configuration








14 - Login Session





X - exit

select -

13 Select IP Configuration from the configuration

menu.

(Example Response)

IP Configuration

1 - config_router (Configure Default Router and Netmask)

2 - config_data (Configure System Data IP Addresses)

X - exit

select -




26/60


Method 24-8062 May 10, 2006

14 Select config_router (Configure DefaultRouter and Netmask) from the IP

Configuration menu.

=== Executing "config_router"

WARNING: Changing the network settings will effect all

applications!

Improper network configuration will result in loss of

service!

Applications may require restart or reconfiguration after

network changes

Router IP: *******

Netmask: **********

Enter IP for this networks router (default: ******):

15 Enter the .

Enter the netmask for this network (default: *******):

16 Enter the . Router IP: *******Netmask: *********

Enter "ok" to commit changes

Enter "quit" to exit


17 Verify all customer information. If any of the

information is incorrect, hit any key and retype

the information. If it is correct, then enterok to

continue

#ok

=== "config_router" completed successfully

IP Configuration


2 - config_test (Configure IP Multipathing Test Addresses)


X - exit

18 Select config_data (Configure System Data IP

Addresses) from the IP Configuration menu.

=== Executing "config_data"

WARNING: Changing the network settings will effect all

applications!

Improper network configuration will result in loss of

service!

Applications may require restart or reconfiguration after

network changes

hostname: *******

ip address: *******

Enter the hostname for this system [sspfs_svr]




27/60


May 10, 2006 Method 24-8062

19 Perform this step to configure the system data. Enter the .

Enter the .

Answer yes since the APS application is to beinstalled on the Server.

Enter the .

Enter APS.

Enter no.

Enter ip address for Host [**********]

Configure additional ip address ? [yes]

Enter application for ip address ********* []

Configure additional ip address ? [no]

20 Verify all customer information. If any on theinformation is incorrect, hit any key and retype

the information. If it is correct, enter ok to

continue

#ok

............................

The network changes have been made, however

applications require

a restart to use the new network settings. Reboot to ensure

all

applications are restarted. Exit this "cli" tool and reboot

using the Solaris command "shutdown -i 6 -y"

IP Configuration


2 - config_test (Configure IP Multipathing Test Addresses)


X - exit

21 Exit the IP Configuration menu.

#X

Configuration1 - NTP Configuration













14 - Login Session

15 - Location Configuration16 - Cluster Configuration



X - exit

select -

Procedure 4 Using the CLI Tool to Modi fy System Information (Page 5 of 6)



28/60


Method 24-8062 May 10, 2006

22 Exit the Configuration menu.#X


1 - View

2 - Configuration

3 - Other

X - exit

23 Exit the CLI menu.

#X

#

24 Reboot the system.

#shutdown -i 6 -y

(System Reboots)

25 After the system has rebooted log in as root.

26 Ping the SPFS Server Gateway Default Router IP

to verify that the server is communicating in the

Network.

27 End of Procedure.




29/60


May 10, 2006 Method 24-8062

4.2.7 Using the CLI Tool to Modify/Setup NTP Server

This section applies to all APS installations. Perform this procedure ifthe customer has provided a NTP server for this site (Refer to Spec Bookfor information).

Procedure 5 Modi fy/Setup NTP Server (Page 1 of 3)



#cli


1 - View

2 - Configuration

3 - Other

X - exit

select -














14 - Login Session

15 - Location Configuration16 - Cluster Configuration



X - exit

select -

3 Select NTP Configuration from the

Configuration menu.

NTP Configuration

1 - ntp_conf (Configure the NTP daemon)

2 - ntp_unconf (Unconfigure the NTP daemon)

3 - ntp_remove (Remove an NTP server)

4 - ntp_view (View ntp configuration information.)

X - exit

select -

4 Select ntp_conf(Configure the NTP

daemon) from the NTP Configuration

menu.

=== Executing "ntp_conf"

Enter time server IP address (X to exit):

5 Enter the .

x.x.x.x is valid...

Enter address of time server 2 (X to exit):


30/60


Method 24-8062 May 10, 2006

6 Enter the or enter X to exit the prompt for

the secondary IP.

Enter TAG (alias) for x.x.x.x (Optional):

7 Press [Return] to not enter a TAG (alias)

for the NTP servers.

NTP Is Now Configured...

=== "ntp_conf" completed successfully

8 Enter the

or enter X to exit the prompt for the

secondary IP.

Enter TAG (alias) for x.x.x.x (Optional):

9 Press [Return] to not enter a TAG (alias)

for the NTP servers.

NTP Is Now Configured...

=== "ntp_conf" completed successfully

10 Exit back to the Configuration menu.

#X

Configuration

1 - NTP Configuration













14 - Login Session





X - exit

select -

11 Exit the Configuration menu.

#X


1 - View

2 - Configuration

3 - Other

X - exit

select -

12 Exit the cli menu.

#X

#

13 Reboot the system.

#shutdown -i 6 -y

(System Reboots)

Procedure 5 Modify/Setup NTP Server (Page 2 of 3)



31/60


May 10, 2006 Method 24-8062

4.2.8 Creating a User for Login Verification

Perform this procedure for all APS initial installations.

The following Procedure will have you setup a nortel userID. You willalso setup the password for the maint account. The maint user wascreated by the SPFS install. The password will be modified to allowusers to telnet to the server and login.

The nortel user will be created to allow you to test the application loginson the server. The command used will also create a folder for the norteluser in the following location: /export/home (the folder will be nortel)

Note: The SPFS load does not allow the root user to log in remotely(Telnet). The root user can login only on the server console. All ofthe install commands presented in this method should be executedas root. Failure to execute the commands as root will resultin errors. If you perform the install as the maint user, you willget errors. The maint user account is allowed to log inremotely. Once you have logged in as the maint user, you canthen become the root user by entering: #su

14 After the system has rebooted log in as root.15 End of Procedure.

Procedure 6 Creating a User Account for Nortel (Page 1 of 2)


1 Login as root. #

2 Set the maint password to maint for use when

telneting into the server.

#passwd -r files maint

#maint

#maint

New Password:

Re-enter new Password:

passwd: password successfully changed for maint

Procedure 5 Modi fy/Setup NTP Server (Page 3 of 3)



32/60


Method 24-8062 May 10, 2006

3 Setup the nortel user requires a temp workaround! SPFS install automatically creates a norteluserid that must be deleted and then readded:

#grep nortel /etc/passwd

(example data)

nortel:x:115:107:nortel from NNswmgmt:/export/home/nortel:/bin/csh

The userid in the example above is 115. This existing userid must be used

in the following command to modify the nortel user.

#usermod -u 115 -d /export/home/nortel -m -g succssn -Glnadm,trkadm,mgcadm,mgadm,emsadm nortel

Note: This command is typed on one line, no spaces after each ,.

4 Set the nortel password to nortel for use when

telneting into the server.

#passwd -r files nortel

#nortel

#nortel

New Password:

Re-enter new Password:

passwd: password successfully changed for nortel

5 You may now exit and disconnect the console

cable. The choice is up to you if you want to

continue the method using telnet or staying

connected through the console. If staying on the

console, there is no further configuration needed

and proceed to next section. However if you aregoing to use telnet option please continue.

6 Using your laptop (connected to the customers

network) or the customers client workstation, use

the telnet application to connect to the server:

Click on Start -> Run

#telnet

This will open a window and present you with

a login prompt.

7 Login to the server as maint with password

maint.

8 Switch to the root user.#su -

#root

9 End of Procedure.

Procedure 6 Creating a User Ac count for Nortel (Page 2 of 2)



33/60


May 10, 2006 Method 24-8062

4.2.9 Using the CLI Tool to Modify DNS Configuration

DNS is not mandatory for APS.

APS Stand Alone

Perform Procedure 7, Modify the DNS Configuration if noted inSection 2.3.1.

4.2.9.1 Modify DNS Configuration via the CLI Tool

This procedure setups DNS service for the APS.

CAUTION/WARNING:DNS configuration is not mandatory for the installation ofAPS.

Procedure 7 Modify the DNS Configuration (Page 1 of 3)



#cli


1 - View

2 - Configuration

3 - Other

X - exit

select -

2 Select Configuration from the cli menu. Configuration1 - NTP Configuration2 - Apache Proxy Configuration












14 - Login Session





X - exit

select -


34/60


Method 24-8062 May 10, 2006

3 Select DNS Configuration from theConfiguration menu.

DNS Configuration

1 - turn_dns_on (Turn on a system's DNS capability)

2 - turn_dns_off (Turn off a system's DNS capability)

X - exit

select -

4 Select turn_dns_on (Turn on a system's DNS

capability) from the DNS Configuration menu.

=== Executing "turn_dns_on"

Do you really want to turn on or change DNS? (default:

No):

5 Enter yes to turn on DNS.

#y

Enter the DNS domain for this system

6 Enter the . Enter the ip address of a DNS Server

7 Enter the IP address(s) for the DNS Server.

When all IP addresses have been entered leave

the request blank and press enter to indicate all

entries are complete.

Enter the ip address of a DNS Server

Enter the ip address of a DNS Server

Enter a DNS search domain

8 Enter the Search List(s) for the DNS Server.

When all Search Lists have been entered leave

the request blank and press enter to indicate allentries are complete.



DNS domain: ********

DNS name servers: *.*.*.* *.*.*.* *.*.*.*

DNS search domains: **********

Enter "ok" to accept current settings

9 Enter ok to accept the current settings. If

anything is incorrect - hit any other key to retype

the information.

#ok

=== "turn_dns_on" completed successfully

10 Exit the CLI Tool by entering x three times.

Procedure 7 Modify t he DNS Configuration (Page 2 of 3)



35/60


May 10, 2006 Method 24-8062

11 Verify that DNS configuration using thenslookup tool:

#nslookup

#nslookup

#nslookup


Procedure 7 Modify the DNS Configuration (Page 3 of 3)



36/60


Method 24-8062 May 10, 2006

4.2.10 Certi ficate Installation

Applications on the server will require a certificate prior to installationto ensure it is placed into secure mode. The certificate must be a X.509and in the PEM format.

Certificate requirements are based on the level of trust that needs to beassigned to the server. This is based on how the server will be used. Ifthe server is to be used in a public way such as for E-commerce websites, then a certificate from a CA is required.

If the server is to be used internal to the Company, then a Companygenerated certificate will work.

If the server is used in a more restricted manner, a self-signed certificatewill protect the client to server communications. However, when theserver is accessed the browser will present the certificate and ask if thecertificate should be trusted. If the user answers yes the server can beaccessed, if the user answers no nothing further will be received fromthe server.

Refer to Section 2.3.1 to determine the type of certificate that isrequired. If a CA certificate is provided then perform Procedure 8. If aCA certificate is not provided a self-signed certificate must be createdusing Procedure 9. Only one type of certificate needs to be created forthe server.

The server.key and server.crt are placed into the /opt/apache/conf/server.key and /opt/apache/conf/server.crt directories. Whenapplications are installed, they will see that the server has a certificateand place the server in secure mode.

The name of the certificate should match the host name of the server. Aseparate file (RSA) contains the key, and should not have an associatedpassword.

The certificate must be created with the fully qualified domain name(FQDN) of the server on which the certificate will be installed.


37/60


May 10, 2006 Method 24-8062

4.2.10.1 Certificate Authority

This procedure is used to install certificates granted from a Certificategranting Authority (CA). The CA can be a well known authority such asVerisign or Entrust or the certificate may be company generated when

the operating company has its own internal CA.

Procedure 8 HTTPS Certif icate Installation (Page 1 of 2)


1 Log into the server as root.

2 Obtain an X.509 certificate. The name of the

certificate should match the host name of the

server. A separate file contains the key, and

should not have an associated password.

3 Change directories to the conf directory.

#cd /opt/apache/conf

#

4 Create a ssl.key directory where the key will be

placed and a ssl.crt directory where the server.crt

file will be placed.

#mkdir ssl.key

#mkdir ssl.crt

5 Place the certificate into the following file.

#cp / /opt/

apache/conf/ssl.crt/server.crt

6 Place the key into the following file.

#cp / /opt/apache/conf/ssl.key/server.key

7 Change the certificates owner and group.

#chown root:other /opt/apache/conf/ssl.crt/server.crt

8 Change the key files owner and group.

#chown root:other /opt/apache/

conf/ssl.key/server.key

9 Set the certificate permissions.

#chmod 600 /opt/apache/conf/ssl.crt/server.crt

10 Set the key file permissions.

#chmod 600 /opt/apache/conf/ssl.key/server.key


38/60


Method 24-8062 May 10, 2006

11 Restart the Apache web server.#servstop WEBSERVICES

#servstart WEBSERVICES


Procedure 8 HTTPS Certificate Installation (Page 2 of 2)



39/60


May 10, 2006 Method 24-8062

4.2.10.2 Self Signed Certificates

Perform the following procedure to create a self-signed certificate.Refer to Section 2.3.1 for the information required to create the self-signed certificate.

Procedure 9 Self Signed Certificates (Page 1 of 3)


1 Log into the server as root. #

2 Change directories to the conf directory.

#cd /opt/apache/conf

#

3 Create a ssl.key directory where the key will be

placed and a ssl.crt directory where the server.crt

file will be placed.

#mkdir ssl.key

#mkdir ssl.crt

4 Change to the ssl.key directory.

#cd ssl.key

5 Generate a key.

#/opt/openssl/bin/openssl genrsa -rand /var/log/sspfslog 1024 > server.key

50016 semi-random bytes loaded

Generating RSA private key, 1024 bit long modulus

.......++++++

..........++++++e is 65537 (0x10001)

6 Verify that the server.key file has been created in

the ssl.key directory.

#ls

server.key

7 Change to the ssl.crt directory.

#cd /opt/apache/conf/ssl.crt


40/60


Method 24-8062 May 10, 2006

8 Create a certificate.#/opt/openssl/bin/openssl req -new -key /opt/apache/conf/ssl.key/server.key -x509 -days 3650 -out server.crt

( Example Response)You are about to be asked to enter information that will be incorporated into your certificate request.

What you are about to enter is what is called a Distinguished Name or a DN.

There are quite a few fields but you can leave some blank.

For some fields there will be a default value,

If you enter '.', the field will be left blank.

-----

Country Name (2 letter code) [AU]:State or Province Name (full name) [Some-State]:

9 Enter the 2 letter country code in which the

server is located.

Example: US

State or Province Name (full name) [Some-State]:

10 Enter the State or Province.

Example: NC

Locality Name (eg, city) []:

11 Enter the name of the city that the server is

located.

Example:RTP

Organization Name (eg, company) []:

12 Enter the name if the company that owns the

server.

Example:ACME Company

Organizational Unit Name (eg, section) []:

13 Enter the name of the department that owns the

server.

Example: DEPT

Common Name (eg, YOUR name) []:

14 Enter the Fully Qualified Domain Name (FQDN)

of the logical IP address of the SPFS primary

domain name.

Example: .company.com

Email Address []:

15 Enter the email address of the organization that

owns the server.

Example: [email protected]

#




41/60


May 10, 2006 Method 24-8062

16 Verify that the server.crt file has been created inthe ssl.key directory.

#ls

server.crt

17 Verify that a valid security certificate is found

when starting WEB Services.

#servstop WEBSERVER

#servstart WEBSERVER

Stopping group using servstop

Apache Web Service Stopping

WEBSERVER Stopped

Starting WEBSERVER through servstart

Found valid security certificate, starting Web Services

with SSL support...

Apache Web Service Starting

WEBSERVER Started





42/60


Method 24-8062 May 10, 2006

4.2.11 Patching Sub Element (PSE)

Procedure 10 is used to point the PSE on the server to the Network PatchManager that is running on the APS application.

NPM is not used to patch APS however NPM is used to patch SPFS.

Procedure 10 PSE (Page 1 of 3)


1 Log into the server as root.


#cli


1 - View

2 - Configuration

3 - Other

X - exit

select -














14 - Login Session





X - exit

4 Select Succession Element Configuration from

the configuration menu.

Succession Element Configuration

1 - SESM Application Configuration

2 - RESMON Application Configuration

3 - SAM21EM Application Configuration

4 - PSE Application Configuration

5 - OMPUSH Application Configuration

X - exit

select -


43/60


May 10, 2006 Method 24-8062

5 Select PSE Application Configuration from theSuccession Element Configuration menu.

PSE Application Configuration

1 - Configure_PSE (Configure the Patching Server

Element)

X - exit

select -

6 Select Configure PSE. Enter the hostname (preferred) or the IP address of theSSPFS-based machine that contains the Network

Patch Manager (NPM) server. If this machine is part

of a duplex/clustered configuration, please enter the

cluster hostname or IP address.

Enter NPM hostname or IP address: [?,q]

7 Enter the . This will be the IP address of the IEMS

server. If the IEMS and CMT are located on the

same server then the PSE will point back to itself.

Checking communication to x.x.x.x. This may take upto ten seconds.

Is host/ip x.x.x.x acceptable? [y] [y,n,?,q]

8 Confirm the IP address.

#y

Setting the NPM host/ip for the PSE to x.x.x.x.

Binding PSE to system...

=== "Update_NPM_host_or_ip" completed

successfully

9 Exit back to the PSE Application Configuration

menu.

PSE Application Configuration

1 - View_NPM_host_or_ip (View NPM hostname/ip

address location)

2 - Update_NPM_host_or_ip (Update NPM

hostname/ip address location)3 - Create_PSE_Database (Initialize or re-initialize

the PSE database)

4 - Update_Patch_Corba_Mirroring (Mirror the NPM

patch CORBA name reference)

5 - Remove_Patch_Corba_Mirroring (Remove the

NPM patch CORBA name mirror re...)

6 - Unconfigure_PSE (Remove PSE as a system

process.)

X - exit

select

10 Exit the CLI tool. #

11 Start the PSE Server.

#pse start

PSE Started

12 Verify that the server has started. Contact your next

level of support if the server does not start.

#pse status

The PSE is Running




44/60


Method 24-8062 May 10, 2006

4.2.12 SPFS Patching

Once the PSE has been setup to point to the NPM server the SPFS servermust be patched. APS is not patched using the NPM server but the SPFSplatform the APS is running is patched using the NPM server.

13 Install the SPFS MNCL at this time if one isavailable. Follow the documentation that is

provided with the CD.


Procedure 11 SPFS Patching


1 Log into the server as root. SunOS 5.9

SSPFS Version: 0* Build: *********

login:

2 Copy and apply the SPFS patches at this time if

a patch CD is available. Refer to IM 24-0167

and follow the sections listed below to install

and apply the patches.

The Installing and Retrieving Patchessection is performed to copy the patches fromthe CD to the NPM server.

The patches are then applied performing theApplying Patches section.

OAM devices are then restarted performingthe Restarting OAM Devices section.

3 End of Procedure.




45/60


May 10, 2006 Method 24-8062

4.2.13 NPM Removal

This section is used to remove the Network Patch Manager on the APSserver. Perform Procedure 12 to remove NPM from the APS.

Procedure 12 NPM Removal (Page 1 of 2)



#su -

#root

2 Shut down the NPM server.

#servstop NPM

Stopping group using servstop

Killing npm.

Waiting for NPM server to shut down ...

NpmServer has shut downNPM Stopped

3 Shut down the PSE server.

#PSE stop

PSE Stopped

4 Remove the NPM package.

#pkgrm NTnpm

The following package is currently installed:

NTnpm Nortel Networks Network Patch Manager

(NPM)

(sparc) NPM_7_069_0

Do you want to remove this package?


46/60


Method 24-8062 May 10, 2006

5 Confirm the removal of the NPM package.#y

#y

## Removing installed package instance

This package contains scripts which will be executed with

super-user

permission during the process of removing this package.

Do you want to continue with the removal of this package

[y,n,?,q] y

## Verifying package dependencies.

## Processing package information.

## Executing preremove script.

/data/npm/logs

/data/npm/backup

/data/npm/reports

## Removing pathnames in class

/var/log/npm_designlog

...........

.............

opt/corba/rcscripts/NPMonNSStart.sh

/opt/corba/rcscripts/NPMonNSRestart.sh

## Executing postremove script.

NPM postremove: Web Server Virtual Host npm exists and

will now be deleted.

NOTE: The removal of the Network Patch Manager appli-

cation does NOT remove exist

ing patch files. To remove existing patch files completely

from this system you

must manually execute the command "rm -rf /data/npm/

Au"

## Updating system information.

Removal of was successful.

6 Start the PSE Server.

#PSE start

PSE Started

7 Verify that the server has started. Contact your

next level of support if the server does not start.

#servquery -status -group PSE

The PSE is Running

8 End of Procedure.

Procedure 12 NPM Removal (Page 2 of 2)



47/60


May 10, 2006 Method 24-8062

4.2.14 Client PC Setup for " Island DNS"

In order for the Client PC to access the APS Server and login correctly,the local host file will need to be modified on the client PC to add the IPaddress and Hostname of the APS Server.

Note: This procedure does not need to be completed if the Office has aDNS Service and the Client PC has been configured to it.

Procedure 13 Client PC Setup for Isl and DNS (Page 1 of 2)


1 At the Client PC, click on the [Start] button on

the desktop and select [search -> for files or

folders].

2 Search for the file: hosts

(Example for a Windows 2000 client)

The file would be located in the \WINNT\system32\drivers\etc directory

3 Right click on the file and open with a text editor (example: notepad).

4 With the hosts file open, a new line will need to be added to the file to add the IEMS Server

IP address.

Add the IP address FQDN Hostname

Use the following example as a guide:

(Example ONLY)

# Copyright (c) 1993-1999 Microsoft Corp.

#

# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.

#

# This file contains the mappings of IP addresses to host names. Each

# entry should be kept on an individual line. The IP address should

# be placed in the first column followed by the corresponding host name.

# The IP address and the host name should be separated by at least one

# space.

#

# Additionally, comments (such as these) may be inserted on individual

# lines or following the machine name denoted by a '#' symbol.

## For example:

#

# 102.54.94.97 rhino.acme.com # source server

# 38.25.63.10 x.acme.com # x client host

127.0.0.1 localhost

47.234.102.244 CS2KIEMS CS2KIEMS.iot.lab


48/60


Method 24-8062 May 10, 2006

4.3 APS Installation and Conf iguration

This procedure will only be used for Solutions using the AudioProvisioning Server (APS).

APS - refers to the NCL software package that contains the APSapplication. This software enables the Carrier to provisionannouncements on the UAS, MS2010 (IP) and the MS2020 (ATM).

5 Add a new line to the file to add the server IPaddress.

6 Save and close the file.

7 End of Procedure.

Procedure 14 Installing and Configur ing the APS Application (Page 1 of 4)



#su -

#root

#

2 Insert the APS CD in the N240 DVD Drive.

3 Select the ACap package.

#pkgadd d /cdrom/cdrom0/

The following packages are available:

1 ACaps10 APS10-21.0 Package - /opt/uas/aps. March

21, 2005

(sparc) 1.0

Select package(s) you wish to process (or 'all' to process

all packages). (default: all) [?,??,q]:

Procedure 13 Client PC Setup for Isl and DNS (Page 2 of 2)



49/60


May 10, 2006 Method 24-8062

4 Select all packages to install.#all

Processing package instance from

APS10-21.0 Package - /opt/uas/aps. March 21, 2005

(sparc) 1.0

## Processing package information.

## Processing system information.

## Verifying disk space requirements.

## Checking for conflicts with packages already installed.

## Checking for setuid/setgid programs.


super-user

permission during the process of install ing this package.

Do you want to continue with the installation of

[y,n,?]

5 Continue with the installation of ACaps.

#y

/opt/uas/aps/upload_b.png

/opt/uas/aps/user.html

.

.

Installation of was successful.

6 Select the ACips package.

#pkgadd d /cdrom/cdrom0/

The following packages are available:

1 ACips IPS10-21.0 DB Package which goes into /usr/

ntdb/aps10.

(sparc) 1.0

Select package(s) you wish to process (or 'all' to process

all packages). (default: all) [?,??,q]:

7 Select all packages to install.

#all


super-user

permission during the process of install ing this package.

Do you want to continue with the installation of

[y,n,?]

8 Continue with the installation of ACips.

#y

Installation of was successful.

9 Run the APS install script.

#cd /

#./start.sh 2>&1

Note: This step will take approximately 15 minutes for the script to complete.

Note: There is no stop indicator - you may have to hit the return key to get the # prompt.

10 Eject the APS CD and remove it from the CD

drive.

#cd /

#eject cdrom




50/60


Method 24-8062 May 10, 2006

11 Stop the APS Agent from running.#cd /opt/uas/SnmpAgent/bin

#./APSagentctl stop

APS Agent terminated

Note: If no output message, then agent was not running

12 Launch the APS agent configuration.

#./configure_agent

Enter your selection

1) Enter New Configuration Data

2) Restore Previous Configuration Data

#?

13 Select Enter New Configuration Data. What is the element manager's IP address?1) ********* (default)

2) Other IP Address

#?

14 Select Other IP Address. Enter the correct IP Address

15 Enter the . What port does the element manager use to receive traps oralarms/logs?

1) 162 (default)

2) Other Port

#?

16 Select 162 (default). Should the agent forward alarms/logs to syslog?1) Yes (default)

2) No

#?

17 Select Yes (default). What is the logging level?1) Error messages only

2) Error and warning messages

3) Error, warning and informational messages (default)#?

18 Select Error, warning and informational mes-

sages (default).

What port does the agent use to receive SNMP messages

from the element manager?

1) 5161 (default)

2) Other Port

#?

19 Select 5161 (default). What Read community string should the agent use toauthenticate SNMP GET messages?

1) public (default)

2) Other Read community string

#?

20 Select public (default). What Write community string should the agent use to

authenticate SNMP SET messages?1) admin (default)

2) Other Write community string

#?

21 Select admin (default). What SNMP version should the agent use in sendingSNMP messages (v1, v2, v3)?

1) v1

2) v2 (default)

#?




51/60


May 10, 2006 Method 24-8062

22 Select v2 (default). Saving information to ApsAgent.confSaving information to ApsSnmpAgent.sh

#

23 Start the APS Agent.

#cd /opt/uas/SnmpAgent/bin

#./APSagentctl start

24 It may take several minutes for all applications to start. Issue the status command to ensure that all

applications start.

#servquery -status -group APS

(Example response):

Check # 1

Checking process: /opt/uas/aps/scripts/runApsDbServer.pid

The 'runApsDBServer' process, PID: 21831 is ACTIVE and RUNNING.

Check # 2

Checking process: /opt/uas/aps/scripts/runDbServer.pid

The 'runDBServer' process, PID: 21383 is ACTIVE and RUNNING.

Check # 3

Checking process: /opt/uas/aps/scripts/runFileUpload.pid

The 'runFileUpload' process, PID: 21614 is ACTIVE and RUNNING.

Checking process: /opt/uas/aps/scripts/runAdmanager.pid

The 'ADmanager' process, PID: 22388 is ACTIVE and RUNNING.

Checking process: /opt/uas/aps/scripts/runHeartbeat.pid

The 'Heartbeatmon' process, PID: 22575 is ACTIVE and RUNNING.Checking process: /opt/uas/aps/scripts/SnmpAgent.pid

The 'SnmpAgent' process, PID: 24669 is ACTIVE and RUNNING.





52/60


Method 24-8062 May 10, 2006

4.4 APS Application Verification

This section is used to verify that the Customer PC intended to accessapplications on the APS is properly configured and that all applicationsare accessible.

4.4.1 Client Network Verification

This procedure is used to validate that the Customer workstation isproperly configured on the Network.

Procedure 15 Client Network Verifi cation


1 Login to the Customer workstation. The desktop

window should appear with a start bar on the

bottom of the screen.

2 To verify that the network configuration on the

workstation is correct, from the windows desktop

go to: Start -> Run, then type "command" in the

text box.

3 Click OK. A MS-DOS Prompt window should

appear.

4 At the prompt ping the SDM/CBM.

#ping

If messages such as "Request timed out" or "BadIP address" appears, verify network settings are

correct on the workstation, check the cables to

ensure they are plugged in securely and verify

that there are no problems with the components

you are trying to communicate with. If problems

persist, contact your next level of support.

Reply from SDM_IP: bytes=32 time


53/60


May 10, 2006 Method 24-8062

4.4.2 APS EM Login Verification

This procedure will be performed from the Client Workstation and willverify access to the APS. Using the client workstation, you will log intothe EM and verify access to the GUI using a web browser.

Procedure 16 APS Appli cation Launch Poin t Verification


1 Verify access to the APS. Open a web browser and enter the following URL:

http://:8080/aps

Enteradmin as the User Id and Password and then click [OK].

2 End of Procedure.


54/60


Method 24-8062 May 10, 2006

4.5 Oracle Data Backup

Perform the following procedure to take a backup of the Oracle data.

All provisioning activities must be put on hold during the time of theOracle data backup.

For a Sun Netra 240, you need one or more blank CD-R, DVD-R, CD-RW or DVD-RW to store the data. The backup utility limits the storageto 4GB on a DVD-R and DVD-RW.

In a two-server configuration, perform this procedure on the activeserver.

Procedure 17 Oracle Data Backup (Page 1 of 2)


1 Insert the blank CD or DVD into the N240 drive.

2 Telnet to the server on which you want to

perform the backup.

3 Login to the server as the maint user and then

switch to the root user.

#maint

#maint

#su -

#root

4 Backup the Oracle data.

#/opt/nortel/sspfs/bks/bkdata

Backup Completes Successfully

5 For CD and DVD backups only, insert the

backup CD or DVD into the drive.

6 List the contents of the CD or DVD.

#tar tvf /cdrom/*bkdata*/*.tar

When a DVD backup spans more than one disk,

all the DVDs with the exception of the last one

produce a file error during the verificationprocess. This error message does not interfere

with the backup process but can reappear several

times as the backup spans multiple disks.

-rw-rw-rw- 0/1 1874917 Mar 2 10:16 2005

opt/oracle.dmp.gz

-rw-rw-rw- 0/1 1007616 Mar 2 10:16 2005

opt/critdata.cpio


55/60


May 10, 2006 Method 24-8062

7 Eject the CD.#cd /

#eject cdrom

If the DVD drive tray does not open after you

have determined that the DVD drive is not busy

and is not being read from or written o, enter the

following commands and then press the eject

button located on the front of the DVD drive.

#/etc/init.d/volmgt stop

#/etc/init.d/volmgt start

8 Remove the CD or DVD from the drive, label it,and store it in a safe place.

9 End of Procedure.

Procedure 17 Oracle Data Backup (Page 2 of 2)



56/60


Method 24-8062 May 10, 2006

4.6 Sun N240 Back-up

Perform this procedure for Sun N240 servers. The only type of mediasupported by the Sun N240 is DVD-R and DVD-RW. No other DVDtypes can be used to back up the APS.

Use the following procedures to create a full system backup.

Warning:On in-service offices, this procedure should be performedduring low traffic periods.

Note: Any back-up taken should be scheduled, and all users made awarethat the activity is to be taken. Many activities and commands may beimpacted during the back-up.

Procedure 18 Full Sys tem Back-up for Sun N240 (Page 1 of 3)


1 From a PC connected to the Call Server LAN, initiate a telnet session to the server requiring the

back-up.

#TELNET XXX.XXX.XXX.XXX

Where XXX.XXX.XXX.XXX is the physical IP address for the manager to have the back-up per-

formed.

2 At the login prompt enter the user name and password for access. Typically on newly installed sys-

tems, user name of "maint" and password of "maint" are the correct input. if the system is in-ser-

vice, the Operating Company may need to provide the user and password information.

Authorized use only, activities logged.

login:

Example:

login: maint

Password: xxxxx

Last login: Wed Oct 29 11:01:05 from 47.14.0.15

Sun Microsystems Inc. SunOS 5.8 Generic Patch December 2002

aps08: Installed on Sep 16, 2003 at 12:18:08

3 Change user to the "root" user.

#su -

#root

$ su root

Password:

#

Note: Roots password is set to "root" from initial commissioning. The password may have been

changed. Contact the Site prime or Operating Company for the password.


57/60


May 10, 2006 Method 24-8062

4 Change the directory to the "bks" directory.#cd /opt/nortel/sspfs/bks

5 List the files in the current directory.

#ls

Example:

# ls

bkcommon bkfullora bkrotate_arc bkweek4 rshotora

bkdata bkfullsys bks.conf cdwrite rsimpora

bkdropuser.sql bkhotora bksys changeCdVol

bkexpora bkincora bksysToCd rcscripts

bkfiles bkincsys bksysToTape rsdata

Note: The "bkfullsys" must be present.

6 Obtain a DVD-R, and insert into the DVD drive of the CMT being backed up.

Note: A DVD-R must be used. No substitutions.

7 Execute the full system back-up command.

#./bkfullsys

Example:

# ./bkfullsys

*******************************************************************

* Backup file systems on DUHCMT01* Start time: Tue May 18 15:01:01 EDT 2004

*******************************************************************

--- Perform full systems backup ---

Looking for CD devices...

Checking for media...

Media is blank

Device : TOSHIBA DVD-ROM SD-R6112

Backup begins ...

creating scratch /tmp/.tar 2046m d97

creating scratch /tmp/.iso 2048m d98creating scratch /.backing_store 512m d99

Creating /tmp/.snap

Creating snapshot of "/"

Note: Only the start of the back-up shown.

Procedure 18 Full System Back-up for Sun N240 (Page 2 of 3)



58/60


Method 24-8062 May 10, 2006

8 Verify that the dump was successful. This will be the last few lines reported for the back-up proce-dure.

Finalizing (Can take up to 4 minutes)...done.

write /tmp/.tar succeeds

cdwrite exiting with return code 0

rm: /tmp/.tar/lost+found is a directory

cleaning up files

unmounting /data/qca /opt/nortel /user_audio_files /data /audio_files /opt /var

/

removing scratch /.backing_store d99

removing scratch /tmp/.tar d97

removing scratch /tmp/.iso d98

Backup completes successfullyFinish time: Tue May 18 15:38:08 EDT 2004.

9 Enter the / directory.

#cd /

10 Eject the DVD.

#eject cdrom

11 Tag / mark the DVD-R just removed with the name of CMT backed up, FULL SYSTEM, and the

date and time of the back-up.

12 The back-up can be checked by looking at the log file generated. It is located at:

/var/opt/nortel/bkslog/bksys_yyyymmddhh.log

Simply cat the file to view it.

13 Store DVD-R in appropriate location for use if required.

Procedure 18 Full Sys tem Back-up for Sun N240 (Page 3 of 3)



59/60


May 10, 2006 Method 24-8062

5.0 References

Document Number Title


60/60

Method 24-8062 May 10, 2006

6.0 Appendices

Appendix A List of Time ZonesAsia Chile/EasterIslan

d

Mexico GB GMT+2

Asia/Taipei Etc Mexico/BajaNorte HST GMT+3

Australia Etc/GMT Mexico/BajaSur Hongkong GMT+4

Australia/Broken_Hill Etc/GMT+1 Mexico/General Iceland GMT+5

Australia/LHI Etc/GMT+10 Mideast Iran GMT+6

Australia/NSW Etc/GMT+11 Mideast/Riyadh87 Israel GMT+7

Australia/North Etc/GMT+12 Mideast/Riyadh88 Jamaica GMT+8

Australia/Queensland Etc/GMT+2 Mideast/Riyadh89 Japan GMT+9

Australia/South Etc/GMT+3 US Kwajalein GMT+10

Australia/Tasmania Etc/GMT+4 US/Alaska Libya GMT+11

Australia/Victoria Etc/GMT+5 US/Aleutian MET GMT+12

Australia/West Etc/GMT+6 US/Michigan MST GMT+13

Australia/ACT Etc/GMT+7 US/Samoa MST7MDT GMT-0

Australia/Yancowinna Etc/GMT+8 US/Arizona NZ GMT-1

Brazil Etc/GMT+9 US/Central NZ-CHAT GMT-2

Brazil/Acre Etc/GMT-1 US/East-Indiana PRC GMT-3

Brazil/DeNoronha Etc/GMT-10 US/Eastern PST8PDT GMT-4

Brazil/East Etc/GMT-11 US/Hawaii Poland GMT-5

Brazil/West Etc/GMT-12 US/Mountain Portugal GMT-6

Canada Etc/GMT-13 US/Pacific ROK GMT-7

Canada/Atlantic Etc/GMT-2 US/Pacific-New Singapore GMT-8

Canada/Central Etc/GMT-3 CET Turkey GMT-9

Canada/East-

Saskatchewan

Canada/Eastern Etc/GMT-5 Cuba UTC GMT-11

Canada/Mountain Etc/GMT-6 EET W-SU GMT-12

Canada/Newfoundland Etc/GMT-7 EST WET Greenwich

Canada/Pacific Etc/GMT-8 EST5EDT GB-Eire Navajo

C d /Y k Et /GMT 9 E t GMT ROC

Etc/GMT-4 CST6CDT UCT GMT-10