Carrier EMS Installation MOP

R03.00.14.03.00 Carrier Grade Element Management System (CGEMS) Installation MOP

Netra T2000 Sun Server

All Wimax Markets System Release 3.1

Updated 09/22/2009 Version: R01.01.03

CGEMS Installation

Document Version: R03.00.14.03.00 Version Date: 09/22/2009

Motorola Internal Use Only

Page i

Wimax® Method of Procedure (MOP)

Table of Contents REVISION HISTORY ......................................................................................................................................III SECTION 1: HOW TO USE THIS MOP .....................................................................................................7

PURPOSE AND USAGE........................................................................................................................................7 HOW TO USE THIS MOP....................................................................................................................................7 TEXT CONVENTIONS .........................................................................................................................................8

SECTION 2: MANAGEMENT OVERVIEW ...............................................................................................9 IMPLEMENTATION PREREQUISITES ..................................................................................................................9 INSTALL FALLBACK PROCEDURES ....................................................................................................................9 INSTALL PRE-WORK...........................................................................................................................................9 INSTALL STEP-BY-STEP PROCEDURES ............................................................................................................10 UNINSTALL PRE-WORK ...................................................................................................................................10 UNINSTALL STEP-BY-STEP PROCEDURES .......................................................................................................10

SECTION 3: IMPLEMENTATION PREREQUISITES ........................................................................ 12 [ ] Step 1 System Requirements ........................................................................................................12 [ ] Step 2 Software ..............................................................................................................................14 [ ] Step 3 Documentation ...................................................................................................................14

SECTION 4: INSTALL FALLBACK PROCEDURES ........................................................................... 15 SECTION 5: INSTALL PRE-WORK ........................................................................................................ 16

[ ] Step 1 Install Solaris 10 ................................................................................................................16 [ ] Step 2 Installing/Configuring Real VNC (if not already performed) ..........................................16 [ ] Step 3 Configure dual NIC (if needed)..........................................................................................16 [ ] Step 4 Verify System Requirements .............................................................................................17 [ ] Step 5 Verify CGEMS is supported by an Uninterruptible Power Supply (UPS) backup.........17 [ ] Step 6 Set up root user shell environment ...................................................................................17 [ ] Step 7 Verify/update SSH StrictHostKeyChecking .....................................................................18 [ ] Step 8 Refresh cache services........................................................................................................18 [ ] Step 9 Obtain CGEMS software ...................................................................................................18

SECTION 6: INSTALL STEP-BY-STEP PROCEDURES .................................................................... 19 [ ] Step 1 Install Oracle 10gr2 (Box 1)...............................................................................................20 [ ] Step 2 Installing Oracle Patch ......................................................................................................29 [ ] Step 3 Install CGEMS Application (Box 1) ..................................................................................30 [ ] Step 4 Verify System Functionality and Post-Work ....................................................................49 [ ] Step 5 Install Oracle 10gr2 for Combined Mode CGEMS (Box 2)...............................................64 [ ] Step 6 Install EMS Application Software for Combined Mode CGEMS (Box 2) and configure for NE Manager operation. .....................................................................................................................64 [ ] Step 7 Re-configure Combined Mode CGEMS (Box 1) for CPE Manager operation. ...................66

SECTION 7: UNINSTALL PRE-WORK .................................................................................................. 67

CGEMS Installation



Page ii

Wimax® Method of Procedure (MOP) [ ] Step 1 Backup CGEMS..................................................................................................................67 [ ] Step 2 Logout ems account............................................................................................................67

SECTION 8: UNINSTALL STEP-BY-STEP PROCEDURES .............................................................. 68 [ ] Step 1 Remove CGEMS application software ..............................................................................68 [ ] Step 2 Clean up remaining CGEMS application software elements ..........................................73 [ ] Step 3 Remove CGEMS database .................................................................................................74 [ ] Step 4 Clean up remaining CGEMS database elements and reboot...........................................79

SECTION 9: BACKUP & RESTORE STEP-BY-STEP PROCEDURES ............................................ 80 [ ] Step 1 Backup CGEMS..................................................................................................................80 [ ] Step 2 Restore CGEMS..................................................................................................................84

APPENDIX A: TROUBLESHOOTING.................................................................................................... 92 APPENDIX B: CGEMS DEFINITIONS, ACRONYMS, AND ABBREVIATIONS.......................... 110 APPENDIX C: INSTALL SOLARIS 10 OPERATING SYSTEM(U4) ............................................... 111 APPENDIX D: UPGRADE REAL VNC ................................................................................................. 128

1. VERIFY CURRENT VNC INSTALLATION: ....................................................................................................128 2. UNINSTALL VNC (SHOULD NOT BE NEEDED FOR “FRESH” INSTALL) ........................................................129 3. INSTALL LICENSED REAL VNC .................................................................................................................130

APPENDIX F: CGEMS PLATFORM INSTALLATION CHECK LISTS ......................................... 138 APPENDIX G: SYSTEM PLANNING WORKSHEET......................................................................... 142 APPENDIX H: ENABLE AUTOBOOT ON T2000 ............................................................................... 144 APPENDIX I: USB DRIVE PROCEDURES......................................................................................... 145 APPENDIX J: FIRMWARE UPGRADE PROCEDURE..................................................................... 147 APPENDIX K: ORACLE PATCH UPGRADE...................................................................................... 153

1.0 ORACLE PATCH UPGRADE PRE-WORK ....................................................................................................153 2.0 STEP BY STEP TO PERFORM ORACLE PATCH UPGRADE..........................................................................154 3.0 ORACLE PATCH UPGRADE POST-WORK...................................................................................................154 4.0 TIPS .........................................................................................................................................................155 5.0 IMPACT ON RUNNING EMS SERVICES ....................................................................................................155 6.0 ORACLE PATCH UPGRADE TROUBLESHOOTING......................................................................................155

APPENDIX L: SETTING UP COMMUNICATIONS BETWEEN NEIGHBORING EMSES. ....... 156 APPENDIX M: CONFIGURING DUAL NICS...................................................................................... 158 APPENDIX N: STANDALONEMODE CGEMS OVERVIEW ............................................................ 161 APPENDIX M: GENERAL SAFETY INFORMATION .......................................................................... 163

CGEMS Installation



Page iii


Revision History

Changes Made Version Author Name Major/Minor change MOP Number

Date

First release – baseline from R03.00.06.00 version MOP

D01.00.00 EMS Development Team

First release N/A 8/01/2008

Minor changes D01.00.01 EMS Development Team

MOTCM01079531

MOTCM01084382

N/A 8/08/2008


MOTCM01090143 N/A 9/09/2008


FTR issues N/A 9/30/2008

Minor changes to license process


MOTCM01107075

FTR 6051495

N/A 10/10/2008

Minor updates per FTR


FTR 6051495 N/A 10/20/2008

First release of R03.00.08


N/A N/A 10/20/2008

Minor SRs incorporated


MOTCM01107075

MOTCM01112218 N/A 10/24/08

Patch release R03.00.08.00.01


Upgrade paths change N/A 11/03/2008


Changed installer file names.

N/A 11/13/2008

Patch release R03.00.08.00.02


Patch release for minor changes.

N/A 11/17/2008

CGEMS Installation



Page iv

Wimax® Method of Procedure (MOP) Patch release R03.00.08.00.04


Patch release for minor changes; MOTCM01094322

N/A 12/04/2008

Major release R03.00.10


Solaris Patch Bundle (Aug 2008);

Real VNC;

Firmware upgrade

N/A 12/12/2008

Minor updates D01.00.13 EMS Development Team

FTR issues

N/A 01/08/2009


FTR issue, MOTCM011399412, MOTCM01137400, MOTCM01137920

N/A 01/12/2009

Major release R03.00.11


N/A N/A 01/16/2009



Major release R03.00.12 (SP1)


N/A N/A 02/27/2009

Minor update D01.00.18 EMS Development Team

FTR issues, MOTCM01168698

N/A 03/26/2009

Minor refresh update release

R03.00.13


N/A N/A 03/26/2009





Patch Release R03.00.13.00.01


Refer to Release Notes for SRs

N/A 04/09/2009

Upgrade Release R03.00.13.01


Refer to Release Notes for SRs

N/A 04/16/2009

Refresh Release R03.00.13.01.01


Refer to Release Notes N/A 04/25/2009

CGEMS Installation



Page v

Wimax® Method of Procedure (MOP) Minor release R03.00.13.02 (C13R2)



Major construction release



Refresh release D01.00.27 EMS Development Team


Official release for RRR (R03.00.14.01.00)

R01.01.00 EMS Development Team

Official RRR release N/A 07/13/09

Refresh Release R03.00.14.02


Refresh release N/A 07/31/09

Refresh Release R03.00.14.03


Refresh release N/A 09/08/09

Minor update R01.01.03 EMS Development Team

Fix Appendix N and cross references to such

N/A 09/22/09

CGEMS Installation



Page vi


Notice to Users While reasonable efforts have been made to assure the accuracy of this document, this document may contain technical or typographical errors or omissions. Motorola, Inc. and its subsidiaries and affiliates disclaim responsibility for any labor, materials, or costs incurred by any person or party as a result of using this document. Motorola, Inc., any of its subsidiaries or affiliates shall not be liable for any damages (including, but not limited to, consequential, indirect, incidental, or special damages or loss of profits or data) even if they were foreseeable and Motorola has been informed of their potential occurrence, arising out of or in connection with this document or its use. Motorola, Inc. reserves the right to make changes without notice to any products or services described herein and reserves the right to make changes from time to time in content of this document and substitute the new document therefore, with no obligation to notify any person or party of such changes or substitutions.

The information contained herein is Copyright © 2007 Motorola, Inc. All rights reserved. Except as otherwise provided herein, no part of this work may be reproduced or used in any form or by any means, electronic or mechanical (including photocopying, recording, taping, or information storage and retrieval systems) without the express written permission of Motorola, Inc. All authorized copies of this document must include the copyright notice as noted above and other information contained in this notice.

SPECIFICATIONS SUBJECT TO CHANGE WITHOUT NOTICE

How to Use this MOP Wimax® Method of Procedure (MOP)



Page 7

Section 1: How to Use this MOP

Purpose and Usage

The purpose of this MOP is to cover the installation of the Carrier Grade Element Management System (CGEMS) or Carrier Element Management System (CEMS) in the WiMAX system. This manual is provided as a reference for initial installation of a CGEMS for versions described below.

Table 1-1 CGEMS Software Software CGEMS Version

supported MOP Section

Solaris OS U4 and patches

R03.00.14.03.00 Appendix C

Oracle 10gr2 application software

R03.00.14.03.00 Section 6, Step 7

CGEMS application software

R03.00.14.03.00 Section 6, Step 8

* Where “XX” is a patch release versus a minor release (R03.00.08.00.XX). Refer to current version Release Notes.

It is imperative this document be read and implemented in its entirety with no deviations from the procedures as written. It is the responsibility of the person(s) implementing this MOP to ensure proper system operation with minimum service interruption.

How to Use this MOP

This MOP is divided into nine sections. The nine sections are: How to use this MOP, Management Overview, Implementation Prerequisites, Install Pre-work, Install Step-by-Step Procedures, Install Fallback Procedures, Uninstall Pre-work, Uninstall Step-by-Step Procedures, and Appendices.

Each section in this MOP is designed to be used as a stand-alone document.

The Management Overview section is intended to aid in the tracking and monitoring of the MOP activities. Time management is supported in the Management Overview by giving

How to Use this MOP Wimax® Method of Procedure (MOP)



Page 8

the estimated time necessary to perform a given step. The user is encouraged to enter the start and end time in order to compare his/her progress to the estimated time.

The Implementation Prerequisites, Install Pre-work, Install Step-by-Step Procedures, and Install Fallback sections each contain Detailed Steps for that section.

The Appendices contain Trouble Shooting, Solaris 10 Installation, VNC Installation, Dual NIC Configuration, CGEMS Definitions/Acronyms, and Abbreviations, CGEMS Installation Check Lists, and StandaloneMode Overview.

General Safety Information, Revision History and Additional Contact information are also included.

Text Conventions

The following special paragraphs may be used in the MOP to point out information that must be read. The three categories of these special paragraphs are:

Notes

The notes alert the reader of a feature or observation that is of interest, but not of vital importance.

Example and Format

NOTE: Before installing, please check the Release Notes "Special Notes" and "Limitations" sections for information concerning upgrades for this version.

Caution

The caution is used to alert the reader to an action or occurrence that may have some unintended consequences to the functioning of the software.

Example and Format:

CAUTION: The Bootstrap username entered in this screen should be different from any of the existing Solaris usernames that are available on the machine where CGEMS is being installed. If you use any existing Solaris user account name in this screen, you will lose it after uninstalling CGEMS and there by will not be able to login to the Solaris machine using that user account.

Management Overview Wimax® Method of Procedure (MOP)



Page 9

Important/Warning

An important warning is used to alert the reader to an action or occurrence that may have serious consequences to the functioning of the software or the devices that it controls. Since this manual is not for electronic equipment, the warnings for physical harm are not necessary.

Example and Format:

IMPORTANT Fail to meet the requirements below before starting installation or upgrade will result in an extended outage window, and/or will prevent successful installation of CGEMS into the network.

Section 2: Management Overview

Implementation Prerequisites

Day

Start Time

End Time

Down Time

Total Time

Activity Owner

Done

____ _____ _____ _____ 15m 1) System Requirements __________ ____

____ _____ _____ _____ 15m 2) Documentation __________ ____

Install Fallback Procedures

Day

Start Time

End Time

Down Time

Total Time

Activity

Owner

Done

____ _____ _____ _____ _____ 1) Escalation Plan __________ ____

Install Pre-work

Day

Start Time

End Time

Down Time

Total Time

Activity

Owner

Done

____ _____ _____ _____ 3h 1) Install Solaris 10, Appendix C __________ ____




Page 10

____ _____ _____ _____ 1.25h 2) Solaris patch install, Appendix C __________ ____

____ _____ _____ _____ 1h 3) Firmware upgrade, Appendix J __________ ____

____ _____ _____ _____ 1h 4) Real VNC, Appendix D __________ ____

____ _____ _____ _____ 1h 5) Oracle patch, Appendix K __________ ____

____ _____ _____ _____ .5h 6) Configuring dual-NIC, if needed __________ ____

____ _____ _____ _____ 15m 7) Verify System Requirements __________ ____

____ _____ _____ _____ 1h 8) Load CGEMS software bundle. __________ ____

Install Step-by-Step Procedures

Day

Start Time

End Time

Down Time

Total Time

Activity

Owner

Done

____ _____ _____ _____ 30m 1) Install Oracle 10g __________ ____

____ _____ _____ _____ 45m 2) Install CGEMS Application Software. __________ ____

____ _____ _____ _____ 10m 3) Verify CGEMS Functionality __________ ____

Uninstall Pre-work

Day

Start Time

End Time

Down Time

Total Time

Activity

Owner

Done

____ _____ _____ _____ 10m 1) Backup CGEMS __________ ____

Uninstall Step-by-Step Procedures

Day

Start Time

End Time

Down Time

Total Time

Activity

Owner

Done




Page 11

Day

Start Time

End Time

Down Time

Total Time

Activity

Owner

Done

____ _____ _____ _____ 15m 2) Remove CGEMS __________ ____

____ _____ _____ _____ 5m 3) Clean up remaining elements __________ ____

____ _____ _____ _____ 15m 4) Remove database __________ ____

Implementation Prerequisites Wimax® Method of Procedure (MOP)



Page 12

Section 3:Implementation Prerequisites

Detailed Steps

[ ] Step 1 System Requirements

IMPORTANT Failure to meet the requirements below before starting installation or upgrade will result in an extended outage window, and/or will prevent successful installation of CGEMS into the network.

a. The person or persons completing the System Install are familiar with Solaris Commands and should have a full understanding of the CGEMS system.

b. The Customer has fully implemented and tested the IP Networks supporting the CGEMS system including WiMAX Access Network, and DNS services.

c. Hardware Requirements: CGEMS can be deployed either in combined mode or standalonemode. It is recommended the CGEMS be deployed in standalonemode when the service traffic is heavy. In combined mode, CGEMS requires only one machine. In standalonemode, CGEMS requires two machines: one as NE Manager, the other as CPE Manager. It’s recommended the CGEMS be installed on Solaris machines with following hardware:

Sun Netra T2000, 8 core, 1.2GHz 2x146GB SAS Hard Drives 16 GB RAM 4x10/100/1000 Mb/s Base-T Ethernet DVD R/CD R/W drive

d. PC Clients used to launch EMS Topology must have the following minimum hardware: • Windows XP w/ SP3 running 2 GHz processor • 2 Gb RAM • 5 GB free disk space.

e. Third-party software requirement. This section describes software requirements of client, as is shown in the following tables. CGEMS supports two kinds of web clients on different platform: Windows and




Page 13

Solaris. In windows, you can access the CGEMS by IE Browser. In Solaris, you can access the CGEMS by Mozilla.

Table 3-1 Windows Client software requirements

Item Configuration Requirements

Web Browser Internet Explorer v5.5 or v6.0

JRE Java Runtime Environment v1.6.0_06

Adobe Acrobat Reader Adobe Acrobat Reader, version 5.0 or greater

Table 3-2 Solaris Client software requirements

Item Configuration Requirements

Web Browser Mozilla 1.7 or higher

JRE Java Runtime Environment v1.6.0_06

Adobe Acrobat Reader Adobe Acrobat Reader, version 5.0 or greater

f. Installation Dependencies

The software dependencies related to the installation Motorola CGEMS are listed in Table 3-3. The details of installation steps of VNC are described in CGEMS install procedure. The SNMP stack is automatically installed during CGEMS software install. The Oracle server (combined mode) software is part of the CGEMS installation process.

Table 3-3 Motorola CGEMS Installed Independently Application Dependency Source

Motorola CGEMS Real Virtual Network Computing(VNC) Motorola

Motorola CGEMS SNMP Service Motorola

Motorola CGEMS Oracle database Motorola




Page 14

[ ] Step 2 Software The CGEMS software needed at the Customer’s site for installation. The software is available from local Program Management team, Account Team or from Motorola’s Software Distribution Services (SDS). g. Motorola CGEMS application software (R03.00.14.03.00-

cgems_application_and_databases.tar) h. Motorola EMS Solaris 10 U4 DVD (sol-10-0807-GA-sp-dvd.iso) i. Motorola EMS Accessories DVD (R3.1-ems-accessories-dvd.tar contains: r3_os_up.zip

(OS upgrade patches), 10gr2_client_sol.cpio (Oracle client but no longer needed for separate mode configuration), 10gr2_db_sol.cpio (Oracle Server), installvnc.ksh (Real VNC), CGEMSfw.zip (Carrier Grade firmware update), p6810189_10204_Solaris-64.zip (Oracle patch), 082008_c.zip (Solaris 10 scripts for OS upgrade)).

[ ] Step 3 Documentation The following documents are needed at the Customer’s site for the Installation:

a. Motorola CGEMS Installation MOP: Refer to Release Notification or contact Program Management team or Account Team Product Release Binder.

b. Motorola CGEMS Release Notes: Refer to Release Notification or contact Program Management team or Account Team Product Release Binder.

c. Motorola “How to Configure IPSec in Solaris 10, dated 3/12/2008 available from EMS Development Team.

d. Motorola CGEMS Users Guide: Refer to Account Team Product Release Binder and additional information in CGEMS on-line help.

Install Fallback Procedures Wimax® Method of Procedure (MOP)



Page 15

Section 4: Install Fallback Procedures In the event that a problem is encountered during the installation, refer to the Fall-back ProceduresUn-install sections of this MOP and call Motorola support for assistance.

Install Pre-work Wimax® Method of Procedure (MOP)



Page 16

Section 5: Install Pre-work

Detailed Steps

[ ] Step 1 Install Solaris 10 Please refer to “Appendix C: Install Solaris 10 Operating System(U4)” to install solaris 10. This section also includes installing the latest 10_Recommended patch bundle and Firmware upgrade.

NOTE: If existing CGEMS platform is already installed with Solaris U4, then only add the recommended patches as found in Appendix C.

[ ] Step 2 Installing/Configuring Real VNC (if not already performed) Please refer to Appendix D for setting up and configuring Real VNC.

[ ] Step 3 Configure dual NIC (if needed) The default network configuration for WiMAX EMS utilizes single network interface card (NIC). In addition, the EMS has the ability to be dual-homed in cases where the Northbound Interface (NBI) network (for NOC, NMS, EMS Clients) and the Southbound Interface (SBI) network (for managed network elements AP, CAPC, CPE) are on separate, isolated networks and the network administrator requires the EMS to control access to these networks rather than using a router. In most cases, having a dual-homed network is not necessary, and the EMS should be configured to use only one NIC for both NBI and SBI traffic connected to a router which will control the access to the individual networks. When configuring the EMS to be dual-homed, the SBI NIC will be configured with the default route. In addition the Solaris routing table on the EMS must be configured with the appropriate routes for access to the machines on the NBI side. All subnets with machines accessing the EMS via the NBI NIC must be added to the EMS routing table. Details on this addition are not included in this MOP. It is assumed that the network administrator has the capacity to correctly configure the routing table.

NOTE: If you will be using only one interface for both SBI and NBI, skip this step.




Page 17

NOTE: If you will be using separate interfaces for the SBI and NBI, please refer to Appendix M:Configuring Dual NICs to setup dual NICs.

NOTE: Complete the worksheet in Appendix F, CGEMS Platform Installation Check Lists and Appendix G, System Planning Worksheet

NOTE: There is no need to alter the routing table when operating with only one NIC enabled and the default route configured when installation Solaris should be sufficient.

NOTE: In the dual-homed EMS configuration, Local Maintenance Terminal (LMT) access to the managed NEs will require a separate network proxy configuration on the client web browser to be accessible via NBI. Details on this addition are not included in this MOP. It is assumed that network administrator has the capacity to configure the proxy.

IMPORTANT It is recommended that the EMS machine only have up to two (2) NICs configured and operational. All the other NICs should be disabled before EMS installation.

[ ] Step 4 Verify System Requirements The system requirements have been described in Section 3: Implementation Prerequisites and Appendix F: CGEMS Platform Installation Check Lists to verify all the system requirements are met before beginning the CGEMS software installation. Verify: ________________

[ ] Step 5 Verify CGEMS is supported by an Uninterruptible Power Supply (UPS) backup.

WARNING: Running without a UPS backup could cause UNIX file system corruption, data loss, and potential hardware failures if power is bounced multiple times.

Verify: _______________

[ ] Step 6 Set up root user shell environment Run the following command to change the root user environment shell




Page 18

# usermod –s /bin/pfksh root

UX: usermod: root is currently logged in, some changes may not take effect until next login.

# exit

Log back in as root user… # env

>>> verify /usr/sbin;/usr/bin are found first in the $PATH (there may more following)

[ ] Step 7 Verify/update SSH StrictHostKeyChecking

1. View the /etc/ssh/ssh_config file and find item “StrictHostKeyChecking”. The correct and default configuration for this item should be: “StrictHostKeyChecking ask”. If it is not set to “ask”, the operator needs to edit this file and update/save. If this entry is commented out (“#” as beginning of line), no change is needed.

2. If the "$HOME/.ssh/config" exists, and the "StrictHostKeyChecking" is defined in this file, its value should also be "ask"; where "$HOME" means the home path of the Solaris user (root or ems). If this entry is commented out (“#” as beginning of line), no change is needed.

3. Verify ssh is “online”. 4. Remove /etc/ssh/ssh_known_hosts file if it exists.

[ ] Step 8 Refresh cache services Run the following command to restart the cache service:

# /usr/sbin/svcadm restart name-service-cache

[ ] Step 9 Obtain CGEMS software Before attempting to install Carrier Grade EMS, you need to get Motorola Carrier Grade EMS application software DVD from the local Program Management team, Local Account Team or Motorola’s Software Distribution Services:

a. “R03.00.14.03.00-cgems_application_and_databases.tar” DVD b. “R3.1-ems-accessories-dvd” containing “10gr2_db_sol.cpio” and p6810189_10240_Solaris-

64.zip (Oracle Patch) Once this software is installed, use the Solaris “digest –a md5” command found in Section 6 to verify the checksums match those provided by the PM Team, Account Team, or from Motorola’s Software Distribution Services.

Install Step-by-Step Procedures Wimax® Method of Procedure (MOP)



Page 19

Section 6: Install Step-by-Step Procedures

Detailed Steps

The CGEMS installation flow depends on the hardware deployment. The DVD content for CGEMS application software is found in Table 6-1. The installation given in Table 6-2 represents the deployment of combined mode.

Table 6-1 CGEMS Application Software DVD

Filename Contents

R03.00.14.03.00-cgems_application_and_databases.tar

R03.00.14.03.00-wimax_cgems_install.bin R03.00.14.03.00-wimax_cgems_install.bin.cksum R03.00.14.03.00-ems_database_install.bin R03.00.14.03.00-ems_database_install.bin.cksum R03.00.14.03.00-ems_database_client_install.bin R03.00.14.03.00-ems_database_client_install.bin.cksum

Table 6-2 Installation flow for combined deploy mode

Steps Installation content

Step 1 Install Oracle 10gr2. Files: 10gr2_db_sol.cpio; R03.00.14.03.00-ems_database_install.bin

Step 2 Install CGEMS Application Software. File: R03.00.14.03.00-wimax_cgems_install.bin

Step 3 Verify System Functionality




Page 20

When the service traffic is heavy, the CGEMS should be deployed in standalonemode. One server with Oracle and CGEMS application to manage APs and CAPCs, and the server with Oracle and CGEMS application for CPE Manager, which will manage CPEs only. Table 6-2 represents the corresponding installation flow.

NOTE: Refer to Appendix N for an overview of the CGEMS StandaloneMode operations

Table 6-2 Installation flow

Steps Installation content

Step 1 Install Oracle 10gr2 on NE Manager CGEMS Box 1. File: 10gr2_db_sol.cpio, R03.00.14.03.00-ems_database_install.bin

Step 2 Install CGEMS Application for NE Manager on CGEMS Box 1. File: R03.00.14.03.00-wimax_cgems_install.bin

Step 3 Verify System Functionality on NE Manager box

Step 4 If standalonemode configuration: Install Oracle 10gr2 on CPE Manager CGEMS Box 2. File: 10gr2_db_sol.cpio, R03.00.14.03.00-ems_database_install.bin

Step 5 If standalonemode configuration: Install CGEMS Application for CPE Mgr Box 2. File: R03.00.14.03.00-wimax_cgems _install.bin

Step 6 Verify System Functionality on CPE Manager box

[ ] Step 1 Install Oracle 10gr2 (Box 1)

IMPORTANT If CGEMS is to be deployed in combined mode, Oracle and CGEMS application should be installed on the same machine.

IMPORTANT If CGEMS is to be deployed in standalonemode, the new implementation will have both EMS boxes installed as combined mode and configured one for NE Manager and other for CPE Manager. Refer to Appendix N for an overview.

IMPORTANT Ensure that the execution privilege of the folders listed below is granted for all users: The Oracle installs destination folder and all its ancestor folders; the folder where the Oracle install package is located and all its ancestor folders. Otherwise, the Oracle install may be blocked in the following steps.




Page 21

a. Insert the Motorola “R3.1-ems-accessories-dvd” DVD/CD into the DVD/CD drive of the T2000 machine containing the Oracle application software. Launch the VNC Desktop of the target Solaris machine for root user as described in Appendix D, Section 3, and beginning with step d.

b. Copy and extract the Oracle application from DVD to /opt directory. # cd /cdrom/cdrom0 # cp R3.1-ems-accessories-dvd.tar /opt # cd /opt # tar –xvf R3.1-ems-accessories-dvd.tar

c. Eject DVD

# eject

d. Insert the CGEMS software application DVD into the DVD/CD drive of the T2000

machine containing the “R03.00.14.03.00-cgems_application_and_databases.tar" and copy to /opt directory. # cd /cdrom/cdrom0 # cp R03.00.14.03.00-cgems_application_and_databases.tar /opt

e. Extract the files from the archive file to the /opt directory

# cd /opt # tar –xvf R03.00.14.03.00-cgems_application_and_databases.tar

f. Verify the MD5 checksum on the binaries against the corresponding “.md5” files for the

binaries provided in the tar bundle. # digest –v –a md5 <*>

The -v option along with * allows all binaries extracted to be checked and reported with corresponding filename; or each individual binary can be verified

Record/Verify: _________________________

g) Run the Oracle database installation:




Page 22

# chmod +x R03.00.14.03.00-ems_database_install.bin # ./R03.00.14.03.00-ems_database_install.bin

NOTE: The installer will check for the oracle patch and notify the operator. If Oracle is not patched, the operator can perform it now (See Appendix K), or after the software install.




Page 23

This will launch the pre-check screen, as is shown in Figure 6-1.1. If the Oracle patch has not been applied, the screen in Figure 6-1.2 will be displayed. The Oracle patch can be installed now by selecting “Exit”; or, after the installation is complete as described in Appendix K by Selecting “Continue”. Select “Next” to continue installation once successfully checked. If the system finds a system configuration issue Figure 6-1.3 may be displayed. Check the /etc/system file for the additional system parameters required for Oracle as defined in Appendix C, step “x” for oracle system level parameters. Select "Next" to continue if you believe the system parameters appear correct and no changes are needed. NOTE: this warning screen may be displayed in re-install cases (i.e., Oracle is being re-installed).

Figure 6-1.1 Successful Oracle Install Pre-Check Dialog

Figure 6-2.2 Oracle Version Check




Page 24

Figure 6-3.3 Warning Oracle Install Pre-Check Dialog

h) After Pre-check step, Select "Next" to continue, you will get the welcome screen as shown in Figure 6-2.




Page 25

Figure 6-2 Oracle install Welcome dialog

i) The next screen asks if you will accept the terms of the license agreement or not, as is shown in

Figure 6-3. Select the I Accept radio button and select “Next” to continue.




Page 26

Figure 6-3 Oracle Install License Agreement




Page 27

j) j) The Pre-Installation Summary screen appears, as is shown in Figure 6-4. Select “Install” to begin the installation.

Figure 6-4 Oracle Pre-installation Summary

k) The installation begins, and the installation progress is displayed, as is shown in Figure 6-5.

This could take up to 30 minutes.




Page 28

Figure 6-5 Oracle install progress




Page 29

l) When the installation progress comes to 100%, the dialog shown in Figure 6-6 will be displayed. Select “Done” to complete the Oracle install.

Figure 6-6 Complete Oracle install

g. Verify that the oracle installation is successful: Issue a command “svcs | grep cgems”.

online svc:/cgems/LISTENER:LISTENER If any of the services are not online, please refer to Trouble Shooting or Section 7: Install Fallback Procedure.

[ ] Step 2 Installing Oracle Patch The Oracle patch can be installed at this time or after the CGEMS software application installation. Refer to Appendix K for detail.




Page 30

[ ] Step 3 Install CGEMS Application (Box 1)

CAUTION: If there is no version of CGEMS on your machine, follow these procedures and install this current version. However, if the CGEMS has already been installed in the target machine, you should refer to Uninstall Pre-work, Uninstall Step-by-Step Procedures sections to uninstall the CGEMS first, and then return to this section to install a new CGEMS.

NOTE: Before installing, Please check any outstanding issues with upgrades in the OPL

NOTE: Before installing Motorola CGEMS, verify the pre-installation checklist in “Appendix F: CGEMS Platform Installation Check Lists”.

a. Launch the VNC Desktop of your target Solaris machine as root user as found in Appendix D, Section 3, and beginning with step d.

b. Change directories, add execute permission and launch the installer: # cd /opt # chmod +x R03.00.14.03.00-wimax_cgems_install.bin # ./R03.00.14.03.00-wimax_cgems_install.bin

Then the Figure 6-7 is displayed. Verify the Release version to be installed and Select “1 OK” or press Enter to accept the default (“OK”).

NOTE: Upon execution, the CGEMS installer will create the “/ tmp/install.dir.x” directory if it does not exist. If any error occurs while the installer attempts to create the directory, ensure that the installer is running with administrator privilege. The “x” in “install.dir.x” is a random number, such as “install.dir.1325”.




Page 31

Figure 6-7 Start the install

c. This will launch the pre-check screen, as is shown in Figure 6-8.1. Select

“Next” to continue installation when successfully checked. d. If the system finds a system configuration issue, for example in Figure 6-8.2 a

previous ems user was found or as found in Figure 6-8.3 the ems group was found, refer to the Trouble Shooting Appendix A (items 31-36) to resolve before continuing the installation.

_R03.00.14.03.00




Page 32

Figure 6-8.1 Successful CGEMS Install Pre-Check Screen




Page 33

Figure 6-8.2 Example for CGEMS Install Pre-Check Warning




Page 34

Figure 6-8.3 Example EMS Group found on system Warning

e. Once a successful system check as shown in Figure 6-8.1, the welcome screen is

displayed, as is shown in Figure 6-9. Select "Next" to continue.




Page 35

Figure 6-9 CGEMS install welcome screen




Page 36

f. The next screen asks if you will accept the terms of the license agreement or not, as is shown in Figure 6-10. Select the “I Accept the terms of the License Agreement” radio button and select ‘Next” to continue.

Figure 6-10 CGEMS install license agreement




Page 37

g. The next screen prompts you to select the install items, as is shown in Figure 6-11. The install items can be selected by selecting on the icon of choice which will turn the icon/label dark blue. Select one item and select “Next” to continue.

NOTE: There are three install selections with combined mode being used for both combined mode and standalone modes. Do not use selection #1 nor #2: (1) Carrier CPE Manager: manages CPEs only; (2) Separate CGEMS: manages AP/CAPCs only; (3) Combined CGEMS: manages all NEs.

Figure 6-11 CGEMS install items




Page 38

h. This screen will prompt you to select the network interfaces as shown in Figure 6-12. Refer to the System Planning Worksheet in Appendix G. The primary network interface will be the Southbound network on which the managed network elements as found. All managed network elements must be on the interface selected here. The secondary network interface will be for Northbound traffic such web server and NOC traffic (i.e., default box interface).

Figure 6-12 Select Network Interface




Page 39

i. The next screen requires the IP Address of database server, as is shown in Figure 6-13. Enter the NBI IP of CGEMS Server where the database has been installed and Select “Next” to continue. Record: ____________________

Figure 6-13 Enter NBI IP




Page 40

j. The next screen prompts you for the Fully Qualified Domain Name (FQDN) of this machine (refer to System Planning Worksheet, Appendix G), as is shown in Figure 6-14. Enter the FQDN in the screen and Select “Next” to continue. A fully qualified domain name (FQDN) is the complete domain name for a specific computer, or host, on the Internet. The FQDN consists of two parts: the hostname and the domain name. The format is: <hostname>.<domain name>.

WARNING: GUI label is misleading (known issue). Use FQDN in this data entry as described above, NOT the domain name.

NOTE: CGEMS Network Domain: The network domain where the CGEMS system resides. For example, you must place “ems115” before your planned domain name. For example, if your Domain Name is “hzlab.mot.com” then your FQDN would be “ems115.hzlab.mot.com”

Figure 6-14 Enter FQDN




Page 41

k. The next screen requires the hostname or IP address of your enterprise time servers, as is shown in Figure 6-15. Specify the time server(s) (refer to System Planning Worksheet in Appendix F: CGEMS Platform Installation Check Lists) (it is recommended that there be at least one Stratum-1 server), then select “Next” to continue. If there is no NTP Server, you can leave them blank, but the NTP service won’t be started if you don’t provide any valid NTP server here and you haven’t configure the NTP service on this machine. You can also configure NTP Service after CGEMS install, which will be described in Step 3 Verify System Functionality section. Record: _________________________

NOTE: If you do not have a time server, you can use the time server on the local computer or an internet time server; for example, pool.ntp.org.

Figure 6-15 NTP Server info




Page 42

l. Enter the CGEMS Administrator details (login ID and password) in the “CGEMS Administrator Account” screen shown in Figure 6-16. The password should be of length at least 5 characters and not more than 14 characters and NO special characters. After CGEMS is successfully installed, this administrator login Id and password should be used to login to CGEMS web interfaces. Later, this CGEMS Admin login Id can be used to create additional CGEMS users using the utility “EMS Account Manager”. Login ID: ___________________ Password: __________________

IMPORTANT The password for this EMS Administrator is also the password of ems account for Solaris. During CGEMS install, an ems account and ems group will be created. And only the ems user can login the Site Administration of CGEMS after the install.

NOTE: Record the above login Id and password as they will be used to login to CGEMS web page. Also, this username should be different from any of the existing Solaris usernames that are available on the machine where CGEMS is being installed.




Page 43

Figure 6-16 EMS Administrator Account




Page 44

m. The next screen will ask users about CGEMS Bootstrap user account details, as is shown in Figure 6-17. The username and password entered here should conform to the username/password policy of the machine where CGEMS is being installed. CGEMS Installer checks for the password to be of length at least 5 characters and not more than 14 characters. The username should be of length at least 5 characters and not more than 20 characters. Record: _________________________

CAUTION: The Bootstrap username entered in this screen should be different from any of the existing Solaris usernames that are available on the machine where CGEMS is being installed. If you enter any existing Solaris user account in this screen, a warning dialog will prompt to prevent you to continue the installation.

Figure 6-17 EMS Bootstrap account




Page 45

n. The next screen is the Pre-Installation summary screen, as is shown in Figure 6-18.

After reviewing the summary information, select Install button to start the installation or select Cancel button to cancel the installation.

Figure 6-18 Pre-installation summary




Page 46

o. The installation begins, and the progress bar is displayed, as is shown in Figure 6-19. All the CGEMS related items are installed in this step. As a part of the installation, the CGEMS Oracle database, Oracle Tables and Users are created silently in this step. This takes approximately 15-20 minutes to complete.

Figure 6-19 Install progress




Page 47

p. Select Done button to finish the installation, as is shown in Figure 6-20.

NOTE: CGEMS will start all the services automatically after successful installation.

Figure 6-20 Complete the installation




Page 48

q. Wait for the “Press <Enter> to exit installer” prompt and press Enter to Exit, as is shown in Figure 6-21.

Figure 6-21 Exit Installer




Page 49

[ ] Step 4 Verify System Functionality and Post-Work a. Verify all CGEMS processes have started and are on-line. For combined mode there

will be eight (8) cgems processes plus two (2) database processes (LISTENER, dXXXX).

# svcs | grep cgems

b. Verify the FQDN found in $MOT_NSM_HOME/conf/wlan_default.properties matches that found in /etc/hosts table.

c. After CGEMS install, the NTP daemon will be automatically included as a service that starts on a reboot of T2000 box. You need to verify that Network Time Protocol (NTP) service is configured and started. Run “svcs ntp” command to check ntp state in the command window (You can connect to T2000 box as either root or ems by any available tools such as VNC desktop, serial console or telnet and then run the following command).

# svcs ntp STATE STIME FMRI online 9:31:04 svc:/network/ntp:default

If the status ntp is not online, please login Topology Manager (described in the following step t), launch EMS Properties viewer Resource Management to enter the valid NTP server IP address and save. If the NTP server is valid, the NTP service will be started automatically. Verify: _________________________

d. Run the following command to change some file configuration(the example below

assumes your CGEMS home directory is /opt/CGEMS, env: $MOT_NSM_HOME):

# chmod 775 $MOT_NSM_HOME/perl-extensions/del_user Verify: _________________________

e. Start a VNC session for ems user as described in Appendix D, Section 3, beginning with

Step d. Verify: _________________________

f. Verify the /etc/hosts file contains the Fully Qualified Domain Name (FQDN) entered above in Figure 6-15 and it is an alias to the interface that communicates with the NEs (e.g. SBI). Edit and save the /etc/hosts file to add this entry as needed ensuring a “space” between existing entries.




Page 50

Verify: _________________________

IMPORTANT: New versions of EMS require the use of JRE1.6.0_06. This impacts remote PC Browser and local machine JRE settings. In particular, if the previous settings were for older versions of JRE

g. If launching EMS from a remote PC IE Browser: The remote PC must have JRE1.6.0_06 installed and configured. This JRE can be downloaded from Sun’s website. If the remote PC had previous versions of Java 1.5.0_xx installed, these must de-selected and cache cleared as follows: (i) Clear java cache from java console (from cmd window use “javaws –viewer”) or use

Control Panel>Java>Temporary Internet Files-Settings; (ii) From Java Console->Java Runtime Settings and enable 1.6.0_06 (Control Panel >

Java >java> Java Application Runtime Settings-View); (iii) Delete IE Browser temporary files; (iv) Restart IE Browser; (v) Verify IE Browser->Tools-Internet Option->Advanced->Java settings for using JRE

1.6.0_06. (Would require IE Browser restart if changed). h. If launching EMS from a remote using local Mozilla Browser or on remote Solaris

platform’s Mozilla browser. On local T2000 machine, log in used the root user VNC session. Run command “$MOT_NSM_HOME/jre/bin/java -version” to check that the EMS java version is 1.6.0_06.

Verify: ____________________

NOTE: The Solaris 10 installation installs JRE 1.5.0_12. The EMS installation installs JRE 1.6.0_06 which is required for EMS application to function correctly.

# java –version NOTE: this will display the default Solaris 10 JRE # $MOT_NSM_HOME/jre/bin/java –version NOTE: this will display the required JRE for EMS application (i) On local T2000 machine, additional Java cleanup is recommended if this box was

previously installed with CGEMS applications running previous JRE. Launch the Java Viewer/Console shown next:




Page 51

# javaws -viewer

(ii) Remove all user cache applications and libraries; (iii) Delete all Temporary Internet Files; (iv) Select Edit Preferences and from the Java Console select Java tab, and select to

View Java Application Runtime Settings. Disable the 1.5.0_12 if enabled. (v) Add JRE 1.6.0_06. Select “Add” then select “Choose” and navigate to

/opt/EMS/jre/bin/java and “Open”. Add Platform = 1.6 and Product = 1.6.0_06 and OK/Apply. OK to close Java Console. File Exit to close viewer.

(vi) Start Mozilla on Solaris desktop in the root user VNC session, as is shown in Figure 6-22. This may take up to 30 seconds for the Mozilla browser to pop up. If any confirm dialogs prompt, just select OK to continue. NOTE: If it still complains about incorrect java version, just ignore it). Use steps: Select Edit-->Preferences-->Navigator-->Helper Applications on Mozilla browser, select “New Type…” button to create a new File type: MIME Type: application/x-java-jnlp-file Description: <as you wish> Extension: jnlp Open it with: /opt/EMS/jre/javaws/javaws OK OK

Verify: _________________________

NOTE: These steps for configuring Mozilla are also found in Appendix A: Troubleshooting issue 12




Page 52

Figure 6-22 Start Mozilla in root user VNC session




Page 53

i. Verify all the CGEMS services have been started. Only the ems user can start CGEMS Site Administration. The password for ems account is the same as the EMS Administrator account that has been created during CGEMS install. Run the following command in ems user VNC session to start site administration:

$ cd $MOT_NSM_HOME/bin $ ./siteadmin.sh

The window shown in Figure 6-23 should prompt after executing the above command. Input the EMS administrator account that has been created during CGEMS Installation and press enter on the keyboard. Then the screen shown in Figure 6-24 should display. All services that are displayed in Site Admin GUI should be in running (green check mark) state. If you encountered any problems here, please refer to Appendix A: Trouble Shooting issue 2, 16, and 17 in this document.

Verify: _________________________

Figure 6-23 CGEMS Site Admin entry




Page 54

Figure 6-24 CGEMS Site Admin

NOTE: There is a command line version of Site Admin/Account Manager available to use. This can also be run from a telnet session and switching to ems user. See below Figure 6-24.1 example of this command line version.




Page 55

# telnet <CGEMS box> Log in as root user or ems user; following example assumes root user # su – ems $ cd $MOT_NSM_HOME/bin $ cmdline.sh Please input loginId:admin Please input password: ============ Command Line Tool ============ 1 : Account Management 2 : HTTPS Management 3 : SNMPv3 Key Management 4 : EMS Backup/Restore Management 5 : Operation Management 6 : Migration Management e : Exit CmdLine Model ============================================ : <choose action desired>

Figure 6-24.1 CGEMS Site Admin

j. If your CGEMS will be using mobility management feature, then generate a GGEMS R3.0 license file for your platform. License file is now platform specific. (i) Login to the License Generator Tool using your <core id> on Motorola’s Software

Distribution Services (SDS) Licensing Tools option as shown in Figure 6-25. (ii) Select “Generate a Lab License” in the left menu (iii) Select Technology -> WiMAX (iv) Change Expiration date in the format of dd-mmm-yyyy if needed, other default is

permanent (lower case “p”) (v) Select Features -> e.g. Mobility 3.0 (vi) Specify Hostname (Solaris ID) of the LTEMS platform. Hostname will be used for

EMS version R3.0.5 and lower, while Solaris ID will be used for EMS versions R3.0.6 and higher. To find this Solaris ID use the EMS GUI Tools->License Management -> File -> Show Host id; or, simply type the command “hostid” from a terminal window command prompt on LTEMS.

(vii)Select Submit (viii)License file will be emailed to core id from [email protected]

mailto:[email protected]�




Page 56

Figure 6-25 – SDS License Generator Tool

(ix) Open email and place the obtained Mobility license file on the target machine

running the LTEMS application to which this license was generated. (x) Launch License Management user interface from the EMS Topology Tools menu as

shown in Figure 6-26.




Page 57

Figure 6-26 – EMS License Management User Interface

(xi) Import License File from SDS and save to a specified location on the PC client being

used to connect to the LTEMS machine. (xii)Next, select to import as shown in Figure 6-27. A window will be launched to allow

user to navigate to the saved location on your PC client selected above and select Open.




Page 58

Figure 6-27 – Import License User Interface

(xiii)Verify license file successfully imported. (xiv)Select the Enable check-box and select Save feature change notification. (xv)Select to Enable features (i.e., Mobility) allowed by license. (xvi)Select File Refresh. (xvii)Select View License File and view license and expiration date as shown in Figure

6-28.




Page 59

Figure 6-28 – License Version and Expiration Date k. If your CGEMS will be managing CPE devices or additional security will be required

between the web clients and the EMS server, use the Site Administration tool to enable HTTPS. Refer to the EMS User’s Guide for detailed instructions.

1. Launch Site Admin tool from ems user VNC session. 2. Select the HTTPS Mgmt tab. 3. Select “Step 1 Generate CSR” and save this file.

4. Submit this CSR to a certificate authority. Receive the generated certificate from the certificate authority on the CGEMS machine at a predefined location.

5. Select "Step 2. Import CA Issued Certs". 6. Select “Yes” to the prompt “LMT certificate already exists. Do you want to

OVERWRITE the existing certificate?” 7. Navigate to the certification file location and select the certificate file

(<filename>.crt) and select "OK". 8. Acknowledge the confirmation about successfully enabling HTTPS. 9. Launch Topology Manager from a IE Browser using url with https://<FQDN or IP

address of EMS> l. Configuring border neighbor EMS(s). Refer to Appendix L – Setting up

communications between neighbor EMS(s).




Page 60

IMPORTANT: if your CGEMS platform will be used in a multi-domain configuration and require neighbor relationships with NEs across domains, this procedure is required. Otherwise, it can be skipped.

m. Launch Topology Manager from Web Browser. It is recommended that you use IE

browser on windows platform or Mozilla on Solaris platform to launch topology manager. Input the address “http(s)://<NBI IP>” or “http(s)://<NBI FQDN>” in the Address bar and then a screen will prompt you for validation, as is shown in Figure 6-29. Input the EMS Administrator Account/passwd to launch CGEMS Topology Manager welcome page, as is shown in Figure 6-30. Then select Launch the Motorola CGEMS Network Topology icon to launch the Topology Manager GUI, as is shown Figure 6-31. Verify: _________________________

Figure 6-29 Client validation




Page 61

Figure 6-30 EMS Topology Manager welcome page

Figure 6-31 EMS Topology Manager without NEs




Page 62

n. Verify and update if necessary the root console is un-commented after the fresh installation as root user. # cd /etc/default # vi login < find the line beginning with CONSOLE= > < if commented out (#), remove the comment (#) and save file >

o. After CGEMS install, there is only one EMS administrator account. If you want to add more accounts, you can add new accounts in EMS Account Manager, this is optional:

Login as ems user VNC session as described in Appendix D, Section 3, and beginning with step d: $ cd $MOT_NSM_HOME/bin $ ./NMSAcctMgr.sh

Then the authentication dialog prompts for the account info, as is shown in Figure 6-32. Enter the EMS administrator account and select OK, and you will be logged into the EMS Account Manager, as is shown in Figure 6-33.

Figure 6-32 EMS Account Manager Authentication window




Page 63

Figure 6-33 EMS Account Manager




Page 64

[ ] Step 5 For standalonemode configuration: Install Oracle 10gr2 for Combined Mode CGEMS (Box 2)

IMPORTANT: Box 2 will be installed as “combined mode” functionality (same as Box 1) but then re-configured to deploy as the NE Manager.

NOTE: Refer to Appendix N for an overview for a standalonemode installation.

a. Repeat same Oracle Server installation as described in Section 6 Step 1 above using the Oracle application software found on the R3.1-ems-accessories-dvd DVD.

b. The Installer selections and UI installer process will be the same as described above in Section 6 Step 1.

c. Verify the Oracle application software is successfully installed in “combined mode” # svcs –a | grep ems

online 16:10:34 svc:/cgems/LISTENER:LISTENER online 16:11:09 svc:/cgems/WimaxDB:d30143

[ ] Step 6 Install EMS Application Software for Combined Mode CGEMS (Box 2) and configure for NE Manager operation.

IMPORTANT: Box 2 will be installed as “combined mode” functionality (same as Box 1) but then re-configured to deploy as the NE Manager.

NOTE: Refer to Appendix N for an overview for a standalonemode installation.

a. Repeat the same CGEMS Application Software installation as described in Section 6 Step 2 above using the R03.00.14.03-wimax_cgems_install.bin found on the CGEMS Application Software DVD.

b. The Installer selections and UI installer process will be the same as described above in Section 6 Step 2, EXCEPT as follows:

c. Choose Install Set (Figure 6-11): select Motorola Carrier EMS (combined). FOR REMINDER ONLY: select the “combined” mode option - Box 2 will be re-configured from a combined mode to a standalonemode as NE Manager.

d. Configure Network Interface (Figure 6-12): if two interfaces configured select both NorthBound (NBI) and SouthBound (SBI) respectively for this Box 2 with Primary = SBI




Page 65

interface. If only one interface is configured, the interface selected will be the same for both NorthBound and SouthBound.

e. EMS Database Information (Figure 6-13): enter the North Bound IP Address of NE Manager Box 2.

f. Network Domain, i.e., FQDN (Figure 6-14): enter the FQDN for Box 2. Record: ____________________

g. EMS Administrator Account (Figure 6-16): enter EMS administrator account/password for Box 2. This should be different from Box 1.

Record: ____________________ h. Bootstrap User Account (Figure 6-17): enter sftp bootstrap account to be used by the NEs.

This should be the same as that which was configured on Box 1. Record: ____________________

i. Upon successful CGEMS application software installation on Box 2, verify the EMS services are “online”.

# svcs –a | grep ems

online Sep_08 svc:/cgems/cgems_mbc:cgems_phm

online Sep_08 svc:/cgems/cgems_rm:cgems_rm

online Sep_08 svc:/cgems/cgems_pm:cgems_pm

online Sep_08 svc:/cgems/cgems_um:cgems_um

online Sep_08 svc:/cgems/cgems_fm:cgems_fm

online Sep_23 svc:/cgems/cgems_cm:cgems_cm

online Sep_23 svc:/cgems/cgems_tm:cgems_tm

online Sep_23 svc:/cgems/cgems_tm:cgems_tomcat

online Sep_23 svc:/cgems/LISTENER:LISTENER

online Sep_23 svc:/cgems/WimaxDB:d30143

j. Switch the EMS configuration file option to change the EMS Box 2 to operate in NE Manager

mode. (NOTE: this will hide most the CPE-related UI menu options, some may still be visible but will not function)

1) Log in as ems user. 2) Change directories to /opt/EMS/conf. 3) Edit file “feature.properties”. 4) Change “CPE_MGR=enabled” to “CPE_MGR=disabled” and save file.

WARNING: ensure no spaces after the “...abled”




Page 66

k. Log in as ems user VNC session and start Site Admin tool and select to stop/start EMS Box 2 services.

l. Once EMS Box 2 software successfully restarts, continue the installation Step 2, sub-steps “q” through “v” and Verify System Functionality Step 3 as needed for NE Manager.

[ ] Step 7 Configure Combined Mode CGEMS (Box 1) for CPE Manager operation. a. Switch the EMS configuration file option to change the EMS Box 1 to operate in CPE

manager mode. This will hide all the AP/CAPC-related UI menu options. 1. Log in as ems user 2. Change directories to /opt/EMS/conf. 3. Edit file “feature.properties”. 4. Change “NE_MGR=enabled” to “NE_MGR=disabled” and save file.

WARNING: ensure no spaces after the “...abled”

b. Modify the EMS Box 1 properties to have a new maximum supported concurrent downloads number of 220.

1. Log into EMS Topology Manager 2. Launch EMS Node Properties (File Properties) 3. Select edit mode 4. Select Configuration Management 5. Modify “Maximum number of concurrent downloads” = 220 6. Save and Close EMS Node Properties 7. Acknowledge the warning “must reboot EMS box now” message. (EMS

restart is performed next step c) c. Log in as ems user VNC session and start Site Admin tool and select to stop/start EMS Box

1 services. d. Once EMS Box 1 software successfully restarts, continue the Step 3 Verify System

Functionality as needed for CPE Manager. .

Uninstall Pre-work Wimax® Method of Procedure (MOP)



Page 67

Section 7: Uninstall Pre-work

Detailed Steps

NOTE: These sections (7 and 8) are only required when referenced from other sections of this MOP: mainly to revert to a previous version due to error or by direction.

NOTE: CGEMS Un-installation procedure will remove both CGEMS application (Section 8, Step 3) and oracle database (Section 8, Step 5) using two un-installation scripts. Therefore, it is recommended to backup CGEMS before CGEMS Uninstall using Site Administration Tool.

NOTE: This process would be repeated on each box (NE Manager and CPE Manager) for standalonemode configuration

[ ] Step 1 Backup CGEMS Please refer to section 9 Backup & Restore Step-by-Step Procedures to backup CGEMS.

[ ] Step 2 Logout ems account Stop CGEMS services using the Site Admin tool. Log into CGEMS as root user and reboot CGEMS Machine by running the command “init 6”.

Uninstall Step-by-Step Procedures Wimax® Method of Procedure (MOP)



Page 68

Section 8: Uninstall Step-by-Step Procedures

Detailed Steps

IMPORTANT This process would be repeated on each box (NE Manager and CPE Manager) for standalonemode configuration.

IMPORTANT Ensure that all the ems users have logout the ems account. Otherwise, the un-install will be blocked in the following steps.

[ ] Step 1 Remove CGEMS application software

NOTE: In this step, the database is not removed, but all the CGEMS data in database is removed.

NOTE: Backup the existing database using Site Administration tool if needed.




Page 69

a. Login the CGEMS Server as root user. Execute the un-installation script “Uninstall_EMS”, as shown and select the Uninstall button to continue as described in Figure 8-1. # cd $MOT_NSM_HOME # ./Uninstall_EMS/Uninstall_EMS

NOTE: The un-install function is also combined with installer. So you can also execute the installation file “R03.00.14.03.00-wimax_cgems_install.bin” to un-install the CGEMS.

NOTE: Running the “Uninstall_EMS” script from its local directory will leave the script in an unknown directory during the clean up step.

Figure 8-1 Uninstall introduction screen




Page 70

a. A warning dialog will prompt to ask the user to confirm the un-installation action, as is shown in Figure 8-2. Select Yes to start the Uninstall. Then the Uninstall progress in displayed in Figure 8-3. This will take approximately 5 minutes.

Figure 8-2 Uninstall confirm dialog




Page 71

Figure 8-3 Uninstall progress




Page 72

b. Select the Done button to complete the Uninstall.

Figure 8-4 Complete the Uninstall




Page 73

[ ] Step 2 Clean up remaining CGEMS application software elements Several folders are left after you have removed CGEMS. The following information assumes that CGEMS was installed at $MOT_NSM_HOME. For example, $MOT_NSM_HOME can be “/opt/EMS”. You can navigate in /opt/EMS to check which files are not needed any more. Then you can remove the unused files to free the disk space.

# cd /opt # rm –R /opt/EMS/EMS_03.00.XX.YY.ZZ NOTE: this directory will reflect the current installed version that requires removal (e.g., for EMS release R03.00.13.01.01 this directory would be EMS_03.00.13.01.01) #




Page 74

[ ] Step 3 Remove CGEMS database

NOTE: This step will remove the oracle database. If the current CGEMS version is 03.00.03 and the deploy mode will not be changed, you need not remove and reinstall the database. Otherwise you have to uninstall the Oracle database.

a. Login the CGEMS as root user. Execute the un-installation script “Uninstall_EMS_Database”, and the introduction screen will display, as is shown in Figure 8-5. Select Uninstall to continue. Then a confirm dialog will prompt, select “Yes” to begin the un-install.

NOTE: Running the “Uninstall_EMS_Database” script from its local directory will leave the script in an unknown directory during the clean up.

# cd /opt/EMSDB # ./Uninstall_EMS_Database/Uninstall_EMS_Database

Figure 8-5 Database Uninstall introduction




Page 75

b. Verify and update if necessary the root console is commented after the uninstall as root user. # cd /etc/default # vi login < find the line beginning with CONSOLE= > < if not commented out, add the comment (#) before CONSOLE and save file >




Page 76

Select “Yes” if you want to uninstall EMS Database as shown in Figure 8-6.

Figure 8-6 Database Uninstall progress




Page 77

b.The Uninstall begins, as is shown in Figure 8-7. This will take about 10 minutes.

Figure 8-7 Database Un-installation Progress




Page 78

c. Select Done as shown in Figure 6-8 to complete the Uninstall.

Figure 8-8 Complete Database Uninstall




Page 79

[ ] Step 4 Clean up remaining CGEMS database elements and reboot.

# cd /opt # rm –R /opt/EMSDB # rm –R /opt/DataForEMS # init 6 ***** AFTER SUCCESSFUL BOX REBOOT ***** ***** Log in as root user ***** # userdel ems (NOTE: may not find ems home directory..this is OK) # userdel oracle (NOTE: may not find ems home directory..this is OK) # userdel <sftp account> (NOTE: can verify name using more /etc/passwd) # userdel <EMSdl-xxxx account> (NOTE: can verify name using more /etc/passwd) #

c. Clear all java cache remaining on client PC machines used to launch CGEMS

applications 1. Close all VNC sessions connected to target platform. 2. Launch Windows cmd window 3. Run “javaws –viewer” (JRE1.6 and greater); and “javaws” (JRE1.5) 4. Look for any User Cache containing previous CGEMS applications. 5. Remove all. 6. Close javaws viewer.

Backup & Restore Step-by-Step Procedures Wimax® Method of Procedure (MOP)



Page 80

Section 9:Backup & Restore Step-by-Step Procedures

Detailed Steps

These steps are provided for reference for the procedure to Backup a CGEMS database as well as restore a CGEMS database when previous procedures required such action. They do not have to be performed unless needed.

[ ] Step 1 Backup CGEMS a. Login the EMS server as ems by VNC session, execute the following command to

launch the Motorola CGEMS Site Administration (SiteAdmin). $ cd $MOT_NSM_HOME/bin $ ./siteadmin.sh

NOTE: “$MOT_NSM_HOME” stands for the CGEMS home folder where the CGEMS is installed.

b. A window should prompt you for EMS account after executing the above command. Input the EMS administrator account that has been created during CGEMS Installation and press enter on the keyboard and the CGEMS Site Administration tool is displayed.

c. Set the preferences for the backup directory location. The backup directory is /home/BackupRestore. Change the backup directory following the actions described in Figures 9-1 and 9-2.




Page 81

Figure 9-1 Select Preferences




Page 82

Figure 9-2 Change backup directory path location




Page 83

d. Select the “Create New Backup” button on Site Administration. Then you can select the backup mode in the screen shown in Figure 9-3. Select a backup mode and select OK to start the backup.

Figure 9-3 backup mode

e. Upon the completion of the backup, the system will prompt a confirm dialog, as is shown in Figure 9-4. Select OK to complete the backup.

Figure 9-4 Backup Complete Confirmation




Page 84

[ ] Step 2 Restore CGEMS

NOTE: Software bundles will not be restored.

NOTE: After restore, you have to import a new feature license file, and will be required to generate new certificates in order to enable https.

NOTE: User accounts will be restored as described below.

NOTE: Mobility feature license will not be restore d. Operator will need to import feature license on CGEMS if needed.

a. Run the following command to refresh the cache service: # /usr/sbin/svcadm restart name-service-cache

b. On Site Administration, select one backup, select show Backup Details to validate the backup health. The validation will begin, as is shown in Figure 9-5.




Page 85

Figure 9-5 Validate Backup health




Page 86

c. When the validation is complete, the backup details will be shown up, as is shown in

Figure 9-6. Make sure that all the archive contents are marked with green cross . If any archive content is broken, you should not restore this backup. Select OK button to continue.

Figure 9-6 Backup Details




Page 87

d. Select Restore Backup button, a window will prompt you the supported restore version

list as show in Figure 9-7, make sure the backup version is in this list. Then select yes to continue.

Figure 9-7 Supported Restore Version




Page 88

e. The next screen will prompt you to close Motorola CGEMS GUIs and confirm the

restore configuration, as is shown in Figure 9-8. Select “Yes” button to start the restore.

Figure 9-8 Restore confirm dialog




Page 89

f. The restore begins as shown in Figure 9-9. The progress bar is shown at the bottom of

the Site Administration.

Figure 9-9 Restore in-progress




Page 90

g. When the restore is successful, the status bar will be updated with “Restore backup

SUCCESSFUL” information as shown in Figure 9-10.

Figure 9-10 Restore successful

h. Verify the FQDN in wlan_default.properties (ManagedResource.NsmFqdn) in $MOT_NSM_HOME/conf folder, the old FQDN to the current FQDN of platform

Verify: ________________ i. If the user that is restored does not exist in EMS server, it is created with a default

password as the “user name”. The operator will then need to get this account unlocked by executing "passwd -u [username]" as root user. If the user that is restored exists in EMS server, the original username and password in maintained.

Verify: _____________




Page 91

APPENDIX A: TROUBLESHOOTING.................................................................................................... 92 APPENDIX B: CGEMS DEFINITIONS, ACRONYMS, AND ABBREVIATIONS.......................... 110 APPENDIX C: INSTALL SOLARIS 10 OPERATING SYSTEM(U4) ............................................... 111 APPENDIX D: UPGRADE REAL VNC ................................................................................................. 128 APPENDIX F: CGEMS PLATFORM INSTALLATION CHECK LISTS ......................................... 138 APPENDIX G: SYSTEM PLANNING WORKSHEET......................................................................... 142 APPENDIX H: ENABLE AUTOBOOT ON T2000 ............................................................................... 144 APPENDIX I: USB DRIVE PROCEDURES......................................................................................... 145 APPENDIX J: FIRMWARE UPGRADE PROCEDURE..................................................................... 147 APPENDIX K: ORACLE PATCH UPGRADE...................................................................................... 153 APPENDIX L: SETTING UP COMMUNICATIONS BETWEEN NEIGHBORING EMSES. ....... 156 APPENDIX M: CONFIGURING DUAL NICS...................................................................................... 158 APPENDIX N: STANDALONEMODE CGEMS OVERVIEW ............................................................ 161 APPENDIX M: GENERAL SAFETY INFORMATION .......................................................................... 163

Troubleshooting



Page 92

Appendix A: Troubleshooting The following problems may occur during installation. Follow the resolutions described below.

Table 9-1 Troubleshooting

# Problem Resolution 1. If CGEMS has been installed on this machine, the

EMS Administrator user account may be not deleted successfully, and perhaps some user still login on system with ems account, it will cause the CGEMS installation failure, please make sure this user logout first before a new installation.

1. Using the command like “id -a ems” to check the whether the ems account still exists; 2. If the account already exists, using the command like “userdel -r ems” to remove the user. 3. May need to force kill on individual processes: ps –ef | grep ems kill -9 <process id(s) for Xsessions>

2. Can not start Site Administration, got the message like: “Must use ems account” or like below: Reading properties from /space/CGEMS/conf/wlan_default.properties Exception in thread "main" java.awt.HeadlessException: No X11 DISPLAY variable was set, but this program performed an operation which requires it.

1. Please make sure your current login id is ems, you can run the command “who am i” to check you’re running the vnc as ems. 2. Login as ems user: the user name is “ems”, and the password of ems user is the same as the password of EMS Administrator Account created during CGEMS install. 3. Create a VNC service on EMS server following Appendix D. 4. Login VNC following Appendix D 5. Start the Site Administration. Note: The Site Administration must be started using ems account. If not, the backup / restore will fail because of the Solaris file privilege management.

3. The restore failed and the log looks like: “WARNING: Failed to restore subsystem - com.motorola.nsm.common.cm.configserver.CmArchiveable due to, - Restore process failed: Unable to store data for Node ID 00001. CauseMsg: parent 00000 was not found for node:00001 WIMAX00001.”

1. Restart the services; 2. Close the SiteAdmin; 3. Restart SiteAdmin, then do restore again.

Troubleshooting



Page 93

4. When bootstrapping the first time, it fails and display following error information: “Couldn't conconicalize: Permission denied need cwd”

Change the privilege of root directory (/ ) of EMS Server by using command: “chmod 775 /”.

5. How to enable ftp and telnet for root? 1. Log in as ems user, then switch users to root (su – root) 2. Enable telnet for root: Comment the following line in /etc/default/login: #CONSOLE=/dev/console 2. Enable ftp for root: Comment the following line in /etc/ftpd/ftpusers: #root

6. When adding a CAPC by the EMS TM GUI, it prompts an error message like “data can not be saved”.

Your have to bind the IP address and installation domainname manually if the machine does not register to a DNS. Please refer to Appendix E:Configuring Dual NICs.

7. Can not Uninstall CGEMS software. Using “root” user to run the Un-installation.

8. How to stop and start Apache Stop apache service command : # svcadm disable http Start apache service command : # svcadm enable http

9. If CGEMS processes do not start, log into EMS as root user and determine which are offline: # svcs –a | grep cgems To view SSH process: # svcs | grep ssh To view Apache process: # svcs | grep apache If any service is not “on-line” the following command can be used to get additional details and log files #svcs –xv | grep cgems_<process name>

To start ems services individually: # svcadm enable cgems _cm # svcadm enable cgems _rm # svcadm enable cgems _fm # svcadm enable cgems _pm # svcadm enable cgems _tm # svcadm enable cgems _um # svcadm enable cgems_phm # svcadm enable cgems _tomcat To start ssh # svcadm enable ssh To start apache # svcadm enable apache To start all processes: # $MOT_NSM_HOME/bin/serv start

Troubleshooting



Page 94

To stop all processes: # $MOT_NSM_HOME/bin/serv stop

10. How to start and stop database services Stop db services in combined CGEMS: # svcadm disable d310 Start db services in combined CGEMS: # svcadm enable d310 Stop db services in separate CGEMS: # svcadm disable n310 Start db services in separate CGEMS: # svcadm enable n310

11. How to start and stop database? 1. Login as the user “oracle”. By default, this user account was created during database installation. The name/password of the account is oracle/oracle 2. Use the “sqlplus” tool and connect to the DB as the SYSTEM DBA. Enter the command: -bash-3.00$ sqlplus / as SYSDBA 3. stop Oracle by executing the command: SQL>shutdown abort 4. start Oracle by executing the command: SQL>startup open

12. How to configure Mozilla? 1. Log into CGEMS as "root" user vnc server session. 2. From CDE tool bar, select Links->Web Browser 3. Sun Mozilla browser launches. Select "OK" to Alert warning message if displayed. 4. In Browser menu: select Edit->Preferences->Navigator->Helper Applications. 5. Select File Type->New 6. Enter the following information:

Troubleshooting



Page 95

MIME Type: application/x-java-jnlp-file Description: <leave blank> Extension: jnlp Select Open It With and enter: /opt/EMS/jre/javaws/javaws 7. Select OK 8. Select OK 9. Launch a new Sun Mozilla web browser and enter the NBI IP for CGEMS, then CGEMS log in screen should display.

13. How to enable NTP service? If NTP is in maintenance state see issue #23

Issue the following command in the command terminal: # svcadm enable ntp

14. (future) (future)

15. How to login vnc desktop? Refer to Appendix D, Section 3, and beginning with step d.

16. Get an error like below when trying to start Site Administration: Could not initialize the application . There may be another instance of the Motorola CGEMS Site Administration already running. If you think this is an error please delete the file: $MOT_NSM_HOME/bin/siteadmin.lck

1. Please make sure you haven’t started an instance of Site Administration 2. If you think this is an error, delete the file : $MOT_NSM_HOME/bin/siteadmin.lck 3. Start Site Administration 4. Enter the account. Then the following issue 17 will occur, follow the following procedure to continue.

17. Get an error like below after enter the account on Site Administration: EMS Site Administration is unable to authenticate this user, due to a service(s) being down. Select Yes to restart all services now or No to restart at a later time.

1. Select No button. 2. Enter the account again. If you still fail to login the Site Administration, please select Yes button to restart CGEMS.

18. How to upload files to EMS Machine from local PC? Ex: software bundle

1. On local PC, Select start-->run, enter "cmd"; 2. navigate to the destination folder where the software bundle is located: cd /D

Troubleshooting



Page 96

<destination folder> 3. Run the command: ftp <EMS NBI IP> 4. enter ems account/password 5. enter "bin" command to change to binary mode. 6.Run this command: put <file name> Note: the software bundle will be put in the folder $MOT_NSM_HOME, (i.e., /opt/CGEMS) Note: if you want to upload a folder to CGEMS Machine, you can package the folder using the zip tool, then use ftp tool to upload the package. After that, login CGEMS Machine as root, navigate to the destination folder, run “unzip <package name>”.

19. Account error when upgrade, migrate or restore CGEMS:

Select Cancel button during upgrade, migration, or restore to continue. After upgrade, migration or restore, open Topology GUI. 1. Open EMS properties, open bootstrap accounts tab, and add a valid bootstrap account previously used. 2. Open EMS properties, Select tools Reset Download Accts 3. All the nodes in “NOT PRESENT” state should be re-bootstrapped through EMS GUI. Open node properties of the node, select the menu: Tools Re-Bootstrap.

20. When launching the cgems_install.bin script the following Fatal Application Error is displayed:

Caused by the EMS being installed before but cancelled for some reason, so the next

Troubleshooting



Page 97

“This Application has Unexpectedly Quit. Invocation of this Java Application has caused an invocationTargetException. This application will not exit. (LAX)”

time when you run the EMS installer again, it will run the uninstaller on that box, but prompt with the picture in JavaError_CPEmgrBox.ZIP, it fails because of the failure of previous installation. Also when installing separate mode products ensure the CPE Mgr is installed on different box from the NE EMSDB. If attempt to install the CPE Mgr on the same box with NE EMSDB, the installer will be blocked during the installation. Solution: 1. Remove the EMS install directory /opt/CGEMS (env: $MOT_NSM_HOME) 2. Restart the installer for application

21. When re-installing CGEMS software due to a failure during the initial installation, the following work around is needed to clear the old environment.

Run the following command as root account before install EMS. # grep "^ems:" /etc/passwd /etc/shadow /etc/user_attr If results look like the below example lines which begin with the file names and ":ems:", then DELETE that line in the file found and save file. Restart installation. If you find no standard output lines in the result, just ignore this step. /etc/passwd:ems:x:103:100::/hzems/CGEMS:/usr/bin/pfksh /etc/shadow:ems:Hsh/E0C7p.4Fk:13899:::::: /etc/user_attr:ems::::type=normal;auths=solaris.smf.manage.cgems_mbc,solaris.smf.manage.cgems_um,solaris.smf.manage.cgems_rm,solaris.smf.manage.cgems_pm,solaris.smf.manage.cgems_fm,solaris.smf.manage.cgems_tomcat,solaris.smf.manage.cgems_tm,solaris.smf.manage.cgems_cm,solaris.smf.manage.WimaxDB,solaris.smf.manage.LISTENER,solaris.smf.manage.ntp,solaris.smf.manage.ssh,solaris.smf.manage.http;profiles=User Management, User Security, Maintenance and Repair, Object Access Management

Troubleshooting



Page 98

22. When launching Topology Manager the jnlp downloads but nothing is displayed. A “java.io.IOExecption: Server returned HTTP response code:504 for URL..” is displayed.

Check your java default browser setting and browser proxy settings. NOTE: this has been seen when operator had Foxfire set as default browser and Java then used this setting.

23 NTP is in maintenance state.

1. cp /etc/inet/ntp.server /etc/inet/ntp.conf or cp /etc/inet/ntp.client /etc/inet/ntp.conf. depending if box is a server or client. 2. Start ntp service “svcadm ntp enable” 3. If still in maintenance state, edit and save ntp.conf as follows: vi /etc/inet/ntp.conf add into the following code: server 127.127.1.0 4. Restart ntp service “svcsadm ntp restart”

24. (Future) (Future)

25. Configuring local browser Mozilla fails or freezes and does not install/launch.

Remove the /.mozilla folder on EMS platform, and then restart Mozilla.

26. All EMS services are in maintenance state and cannot be started even after trying “svcadm enable” command.

Use "ipcs" to check, there are many entries with 'ems' Reboot the EMS box.

27. From ems vnc session, receive a error: “No X11 Display variable was set, but this program performed an operation which requires it…..The application has unexpectedly quit….”

You are attempting an operation that requires “root” user permissions. Log into a “root” user VNC session and retry operation.

28. Oracle LISTENER or ems database services are not starting or in maintenance mode.

svcs –xv LISTENER svcs –xv d30143 cat /var/sc/log/*.d30143 See a ORA-27102: out of memory error Check the /etc/system file for the Oracle memory configurations required. See Appendix C Solaris 10 install, steps “x-y”.

29. Java web start “launch file error” displayed on PC client when attempting to launch CGEMS. “An error occurred while launching/running the application.

Clear PC client java user cache containing any previously used CGEMS applications. See Appendix B.9

Troubleshooting



Page 99

30 ERROR when you upgrade EMS (FTR issue 6 by Zichao Zhoa) NOTE: this error may only exist in C3 1.after successfully upgrade C2 to C3 version (n-1 to n) 2.open the ems siteadmin, set the preference as original backup archive location , but it can’t display anything in the Site Admin tool 3. check the backup folder , found that backup archive folder is there , it was native mode backup 4. check the old backup archive in other folder , it can display the archive before. 5. create a new backup archive for C3, it can display the archive information in the siteadmin.

For avoid restore fail, operator must make sure that the installation path of backup/restore for EMS you will install(N version) must be same with current path of backup/restore for EMS(N-1) your have installed.

31 During EMS install Pre-check the following warning is displayed: Warning\: ems user is in Solaris System, please use the command "userdel ems" to delete ems user. This means ems user is already installed in the system from a previous install.

Cancel the installation and delete this user using command below as root user. Restart installation. # userdel ems

32 During EMS install the following warning is displayed: Warning\: ems is used now in Solaris System, please reboot the machine to logout of all ems user sessions This means the ems user is in use by Solaris system.

Cancel the installation and reboot the Solaris platform with “init 6” command as root user.

33 During EMS installation the following warning is displayed: Warning\: Please delete ems item in /etc/shadow, if you have delete ems user

Cancel the installation and delete this user using command below as root user. Restart installation. # userdel ems Verify the ems user entry in /etc/shadow is removed: # cat /etc/shadow

Troubleshooting



Page 100

34 During EMS installation the following warning is displayed: Warning\: ems group is in Solaris System, please use the command "groupdel ems" to delete ems group.

Cancel the installation and delete this user using command below as root user. Restart Installation. # groupdel ems

35 During EMS installation the following warning is displayed: Warning\: Some services of EMS are still running in Solaris System , please uninstall EMS or Database before install new EMS version. EXAMPLE: Warning\: EMS cgems_cm service still is running in Solaris System. Please use the command "svcs disable cgems_cm" and "svccfg delete cgems_cm" to stop the services.

Cancel the installation and disable the service in question before deleting the service using commands below as root user. Restart Installation. If this does not correct the problem, then uninstall/reinstall EMS software. # svcs disable <cgems_service> # svccfg delete <cgems_service> For EXAMPLE, run: # svcs disable cgems_cm # svccfg delete cgems_cm

36 During EMS installation the following warning is displayed: Warning\: Please check file /etc/hosts which does not match with hostname.

Cancel the installation and edit the /etc/hosts table as root user to correct the CGEMS platform hostname. Reboot the CGEMS platform. # hostname

hostname is displayed # vi /etc/hosts

correct hostname and save file # init 6

37 Client Java version incompatible not allowing EMS Topology to launch. This results from upgrading from previous JRE 1.5 to JRE 1.6 for releases >= R3.0.5.0

From PC Client machine- Option 1: 1. Run javaws -viewer to start the Java Control Panel. 2. View the JNLP Runtime Settings from the Java page. 3. Select the JRE 1.6.0_06 in both user and system page Option 2: 1. Uninstall JRE 1.5.0_11 using Add/Remove programs

Troubleshooting



Page 101

2. Re-install Java 1.6.0_06

38 During the Oracle db or CGEMS application installation, if the installer finds that /opt directory does not have enough space and displays the below screen:

Operator will need to free up space in the /opt directory for at least 10Gb free space for Oracle db installation and at least 250Mb for CGEMS installation Run “df –k” command to verify there is enough space to continue the installation. Select “Previous” button on the warning message screen, then continue installation and if installer finds enough disk space, it will continue. Otherwise select “Cancel” and continue to clean up the /opt directory

Troubleshooting



Page 102

39 If Solaris U4 is re-installed the following may be seen on the serial console: SUNW-MSG-ID: SUNOS-8000-1L, TYPE: Defect, VER: 1, SEVERITY: Minor EVENT-TIME: Tue Jun 17 16:19:25 EDT 2008 PLATFORM: SUNW,Netra-T2000, CSN: -, HOSTNAME: ND-CGEMS-1-NB SOURCE: eft, REV: 1.16 EVENT-ID: de24bdf1-e895-ef2c-a180-a969feffd8d0 DESC: The EFT Diagnosis Engine encountered telemetry for which it is unable to produce a diagnosis. Refer to http://sun.com/msg/SUN OS-8000-1L for more information. AUTO-RESPONSE: Error reports from the component will be logged for examination by Sun. IMPACT: Automated diagnosis and response for these events will not occur. REC-ACTION: Run pkgchk -n SUNWfmd to ensure that fault management software is installed properly. Contact Sun for support.

Can ignore. This is a result of Sun firmware versions. After future firmware version updates, this will be resolved.

40 Switching between JRE versions on remote PC client to use R2.5 EMS or R3.0 EMS.

Try the following: 1. From Windows OS cmd window, run

Troubleshooting



Page 103

IMPORTANT: The JRE environment on the PC client needs to be in sync with the EMS version you are running. NOTE: The suggest resolution would be reversed if going to R3.0 from R2.5

"javaws -viewer" 2. Select General->Settings->Delete Files -- select both "Applications and Applets" and "Trace and log files". 3. OK. 4. Run Java Control Panel and deselect if "use jre1.6_06" is selected (for R3.0 EMS) and ensure to use "jre1.5_11" is selected (for R2.5 EMS). This is found under Java tab then under "View Java Runtime Settings. 5. Ensure your IE Browser Advance Settings does not have “Use JRE1.6_06 for applet” (deselect if selected for R2.5 EMS) 6. Restart Browser. 7. Try to launch EMS application again. 8. WORST CASE: Uninstalling/re-installing JRE if the PC client was previously used for Portal EMS and the JRE1.5 was installed as part of that installation and is found in C:\Program Files\Motorola\PortalEMS\jre-150_11; then uninstall this version using Windows Add/Remove programs, then re-install at default location C:\Program Files\Java\jre1.5.0_11. The exe for JRE1.5 can be found at C:\Program Files\Motorola\PortalEMS\3rd\jre. Copy it to c:\tmp and run the installer.

41 Configuring EMS border neighbors results in one of the following errors: 1.TM_INTER_EMS_COMMUNICATION_DISABLED 2. TM_NBR_EMS_NOT_DEFINED 3. NBR_CLIENT_EMS_OPERATION_TIMEOUT

Possible resolutions: 1. In the EMS properties, the EMS to EMS communication is disabled. 2. Target neighbor EMS not defined in the Client NSM properties 3. Did not get a response from the target

Troubleshooting



Page 104

4. NBR_EMS_TO_EMS_COMMUNICATION_ERROR 5. TM_NBR_GENERIC_ERROR 6. Warning displays that another neighbor action is currently in progress - EMS can only handle one input file at a time, if another file is imported, it will be rejected. 7. NBR_EMS_NAME_MISMATCH_IN_THE_SERVER 8. TM_BACKUP_INPROGRESS 9. NBR_EMS_TO_EMS_COMMUNICATION_DISABLED_ON_SERVER 10. NBR_SERVER_HAS_NOT_DEFINED_ITS_NAME

neighbor EMS. Neighbor EMS might be down, not responding at all. Check network. 4. Possible problem resolving the FQDN and/or web services issues on the target neighbor EMS. 5. Something is really wrong. Contact Motorola Support for further assistance. 6. Retry input at another time. 7. Name given to EMS does not match the name in the input file for both client and server. 8. EMS in doing a backup, target neighbor EMS is busy and it can not handle the request. 9. EMS communication is disabled on server side, border neighbor communication is disabled on server side. 10. EMS server, target EMS does not have a name.

42 Problem: On some box, the /var/log/cgems_security.log is empty, no cgems security logs (bootstrap account changes, SNMPv3 key changes, EMS account change, SSL key updates.) are written to it.

The following commands should be run as root. 1. run "svccfg export system-log", and find the following line in the result: <propval name='log_from_remote' type='boolean' value='true'/> If the value is set to true, we needn't go on with the following steps, there is no problem with this box. If the value is set to false, we should go on with the following steps. 2. Modify the file /var/svc/manifest/system/system-log.xml exactly as the following line. <propval name='log_from_remote'

Troubleshooting



Page 105

type='boolean' value='true'/> 3. svcadm disable system-log 4. svccfg delete system-log 5. svccfg import /var/svc/manifest/system/system-log.xml 6. svcadm enable system-log

43 The following Security Alert displayed after connecting to EMS using IE Browser and launching home page.

PC client IE does not regard the EMS Server's certificate as a secure certificate. This warning doesn't affect EMS function and Users only need to click "Yes" button to let it go on. A final solution is to add the EMS Server's certificate into the list of trusted publishers.

44 After logging in to EMS, a Security warning is displayed. This indicates that the IP address isn't the object name to which the certificate was issued. Users can avoid this warning by using the FQDN of EMS server in IE address box instead of the IP address.

Troubleshooting



Page 106

45 After logging into EMS security warning for digital signature is displayed.

This warning is originated from using IP address to login and can also be avoided via the above solution. Select “Trust” and “Run”. May need to select “Run” multiple times.

Troubleshooting



Page 107

46 The EMS provides a utility to support diagnosing and debugging EMS field issues. The tool is intended to be used by field or customer support engineers. It is run from the command line and collects logs and diagnostics data for off-line analysis. Log in as root user and run as follows: 1) To run in “full” diagnostics mode using command line option “-full”; 2) A “quick” mode can be run without any parameter option or with command line option “-test”. 3) An archive only mode is available with command line option“-archive”. All results/data will be maintained at /home/MED/med.zip. If the data file is >500Mb, it will be split into two files.

$ cd /opt/EMS/bin $ ./medtool.sh -full MEDToolinstance of NMSProperties for app = MEDTool Reading properties from /opt/EMS/conf/wlan_default.properties MED: Tests... MED: Pre. Data Collection... MED: Data Collection... MED: Post Data Collection... MED: Data collected in: /opt/EMS/bin/log/MEDTool*.log /home/MED/*.log MED: Pre. Archive... MED: Archive... MED: Post Archive... MED: 1 archive file[s] in: /home/MED med.zip

47 Changing the root user shell environment. This shell (pfksh) will support Solaris RBAC security model and be compatible with the ems user shell.

Log in as root user # usermod –s /bin/pfksh root Will get a warning that it will not take affect until next log in…. Exit Log back in as root user

48 Once the EMS application software is installed and a EMS server platform reboot is required, use one of the two following procedures: If EMS Server platform requires a reboot (init 6), EMS development strongly recommends this procedure and NOT init 6. If EMS Server platform requires a shutdown (init 0), EMS development strongly recommends this procedure and NOT init 0.

*********** Reboot ************* # cd $MOT_NSM_HOME/bin # chmod +x emsinit <<< only have to do this one time >>> # ./emsinit reboot <<< refer to /opt/EMS/bin/log/emsinit.log for log details as needed >>>

********** Shutdown ************* # cd $MOT_NSM_HOME/bin

Troubleshooting



Page 108

# chmod +x emsinit <<< only have to do this one time >>> # ./emsinit shutdown <<< refer to /opt/EMS/bin/log/emsinit.log for log details as needed >>>

49 How to re-create the DB schema and tables after EMS installed but the EMS DB is corrupted. For example, in the cases of the schema is lost, some tables are lost or some table contents are corrupted. One more detailed DB corrupted case example: #sqlplus / as SYSDBA SQL>select * from dba_users where username='V00_00_00'; No rows select

As root user: # cd /opt/EMS/bin #./CreateDb.sh create #./createUser emsadmin emsadmin ("emsadmin" will be the EMS user with password "emsadmin") # ./serv stop # ./serv start

50 When starting/stopping EMS services or during an EMS box reboot and a EMS service becomes “hung”, for example, the process shows a “online*”; and, if stopping/starting using “svcadm enable/disable <EMS Service>” does not change service to “online”, then use this process:

Find the EMS service not starting/stopping: # svcs -l <EMS_service> (Note the contract_id) # pkill -9 -c <contract_id_for_EMS_service> # svcadm enable <EMS_service> Verify the stuck EMS service is now "online" # svcs -a <EMS_service>

51 Root partition > 75% Check /var/adm/wtmpx (EMS product bulletin wimax_g_pems_018). “cat /dev/null > /var/adm/wtmpx” Check /usr/apache2_cgems/logs. Logadm cron should only be keeping two log files. Remove all log files greater than “*.2” Remove patches zip files in /patches/11_30 Check /export or other personal directories for old copies of ems install binaries, or other applications. Check for java logging enabled. Disable

Troubleshooting



Page 109

java logging using java console and clean /.java/deployment/log files.

52 While restoring a EMS database using the Site Admin tool, the user is prompted with: (NOTE: accounts listed are EXAMPLES only)

Select “OK”. After restoring the db, root user to unlock these accounts using: # passwd –u <account name> Verify the /etc/shadow file for the “LK” (locked) indication. LOCKED: guest123:*LK*$md5$TsF1eqlC$$FDP2AtRQrEtFPKxIrF5qS0:14333:::::: UNLOCKED: guest123:$md5$TsF1eqlC$$FDP2AtRQrEtFPKxIrF5qS0:14336::::::

CGEMS Definitions, Acronyms, and Abbreviations



Page 110

Appendix B: CGEMS Definitions, Acronyms, and Abbreviations

The purpose of this section is to Definitions, Acronyms, and Abbreviations used in this document. Definitions, Acronyms, and Abbreviations

1. IE - Internet Explorer 2. CGEMS - Motorola Carrier Grade Element Management System 3. CEMS – Motorola Carrier Element Management System 4. AAA - Authentication, Authorization and Accounting 5. AP - Access Point 6. CAPC - Carrier Access Point Controller 7. CPE - Customer Premise equipment 8. EMS – Element Management System 9. MOP – Methods and Operations Procedures 10. VNC - Virtual Network Computing 11. JRE – Java Runtime Environment 12. OS – Operating System 13. NBI – North Bound Interface 14. SBI – South Bound Interface 15. NIC – Network Interface Card

Install Solaris 10 Operating System(U4)



Page 111

Appendix C: Install Solaris 10 Operating System(U4)

IMPORTANT: This Appendix must be read in it’s entirety before beginning work!!

Detailed Steps

NOTE: during console connection there may be a few messages similar to “…cannot negotiate hypervision LDC services..”. This is a known firmware version and can be ignored.

[ ] Step 3 Install Solaris 10 Operating System(U4) a. Connect to T2000 via serial port using a Laptop with Hyper-Terminal application

installed. Use CAUTION when connecting to serial console to prevent a system break being sent. Refer to EMS Product Bulletin, wimax_g_pems_014-1.

i. Use the provided “Silver” 9-pin DB9 to RJ45 adaptor provided by Sun with the T2000 and connect to a PC using serial COMx port on PC or X-terminal

ii. Use a 1-to-1 RJ45 to RJ45 cable and connect from DB9 output to the serial management RJ45 port on the back of the Netra T2000 box.

iii. With the use of the Laptop, launch Hyper-Terminal and set the configuration as shown below and start a session:

1. Port=COMx 2. Baud = 9600 3. Data = 8 bit 4. Parity = None 5. Stop Bit = 1 6. No Flow Control

b. Enable Power to Netra T2000 (no switch provided) and verify an “sc>” prompt displays after completing diagnostics.

c. Log in with “admin” and set a password when prompted. Suggest using “motorola” to promote consistency.

Record: _______________________

CAUTION: this Advanced Lights Out Management account and password may be needed in future and must be maintained!




Page 112

d. At the sc> prompt type “poweron” e. “SC Alert: Host system has been reset” will display. Then hit ENTER key to get the SC>

prompt back. f. At the sc> prompt type “console -f” g. If using a telnet to a terminal server to connect to the T2000 serial port, after the cpu

and pci interface tests complete and Netra T2000 begins to boot (may take 5-7 min.), use CTRL+ ] keys to enter the “telnet>” prompt and enter the command “send brk” and enter key to send the break, then hit enter key again to enter the “ok” prompt; If you’re using other tools to connect to T2000 via serial port, please try the following operations: type “break -y” at the sc> prompt; or hit ~# keys; if you’re using Solaris keyboard�please try Stop�A keys.

h. The “ok” prompt is displayed. i. Set NVRAM system defaults

ok> set-defaults j. Insert the provided copy of Motorola EMS Solaris 10 (U4) for SPARC Platforms in the

DVD drive k. To boot from the local DVD and start the text installer in a desktop session, type the

following command.

WARNING: you must send a break to Netra 2000 to get the “ok” prompt in order to begin installation from DVD Solaris.

ok> boot cdrom –text text --- Specifies to run the text installer in a desktop session. Use this option to override the default GUI installer.

l. Select ENGLISH language for your environment.

IMPORTANT: English will be REQUIRED for future Motorola support.

m. Select the Terminal Type to be used and press Enter. Suggest using xterm or vt100 when connected via a laptop PC, and if so, please see the note below).

n. If using vt100 press “escape” followed by “2” instead of F2. Answer all the system configuration questions that are listed in order in the following table, all the answers are annotated in the Answer/Description/Example columns.

NOTE: Select F2_Continue means to press F2 key on the keyboard. The operation may be different depending on the terminal type. For example, you may need to select ESC-2_Continue or ESC-5_Exit.




Page 113

NOTE: For the following DNS server configuration in the below table 9.2, it is assumed that the user has configured their network with a DNS for these steps to complete without error.

Table 9-2 Configuration information for Solaris install

Information for Installation

Description or Example Answer

Network Connectivity

Is the system connected to a network? Yes

Configure Multiple Network Interfaces

Specify all the network interfaces you want to configure. Use e1000g0 for Primary IP. (Secondary interface e1000g1 may be configured later if dual-homed)

e1000g0

DHCP Can the system use Dynamic Host Configuration Protocol (DHCP) to configure its network interfaces?

No

Hostname Planned Hostname for the Netra T2000 <per site network plan>

IP Address Supply the IP address for the system. (e.g., 192.168.1.1)

The Primary IP (see System Planning Worksheet in Appendix F:CGEMS Platform Installation Check Lists).

Subnet for e1000g0 interface

Is this system part of a subnet? Yes

Netmask What is the netmask of the subnet? E.g.: 255.255.255.0

<per site network plan>

IPv6 Do you want to enable IPv6 on this machine? No

Set the Default Route for e1000g0

Specify the default route for the interface. Specify One

Default Route IP Address

Enter the IP address of the Default Route <per site network plan>

Confirm Information for e1000g0 interface

Verify previously entered data above is correct ESC-2 Continue

Configure Security Policy

Do you want to configure Kerberos security on this machine?

No

Confirmation Security Policy

Confirm Kerberos security is not selected. ESC-2_Continue




Page 114

Name Service (NFSv4 domain)

Which name service should this system use? DNS

Domain Name Provide the name of the domain in which the system resides.


DNS Provide IP addresses for the DNS server(s) You must enter at least one IP address, but you can enter up to three addresses.


DNS Search List Enter additional DNS domains to search from if needed “Service Error – Unable to find an address entry” with an option to answer YES or NO.”

<per site network plan> ESC-2 Continue

Name Service Error

An error may be displayed if unable to find an address entry from DNS list

No ESC-2 Continue

Confirm DNS Confirm DNS settings and appropriate DNS in the DNS search list. If you do not wish to select a DNS from the DNS search list, the following error will be seen - Service Error – Unable to find an address entry” with an option to answer YES to continue or NO to re-enter.

ESC-2 Continue

NFSv4 Domain Name

NFSv4 uses a domain name that is automatically derived from the system’s naming services….The current NFSv4 default domain is: “your system.com”

Use the NFSv4 domain name derived by system ESC-2 Continue

Confirm NFSv4 Domain Name

Confirm NFSv4 Domain Name if selected above. ESC-2 Continue

Time Zone How do you want to specify your default time zone? Select Continent, Country or Region and specific timezone.

Continent, Region, Timezone per site

Date and Time Adjust date and time for your specific location Current date and time as needed

Date/Time Verifications

Verify the Data and Time adjustment is correct. ESC-2 continue

Root Password Provide the root password for the system. Note down what is entered

Identify the System

Select to Identify the System ESC-2 Continue

Enabling Remote Services

Would you like to enable network services for use by remote clients?

No. ESC-2 Continue

Solaris Interactive Installation

On the following screens, you can accept the defaults or you can….There are two ways to install Solaris…..you do not want to do this…exit at this

F5_Exit to exit at this point




Page 115

point.

o. At this point you need to exit the configuration. Select F5_Exit to exit the configuration,

followed by F2_Exit_Installation setup in order to get back to the root(#) prompt. Then execute the following commands to partition the disk (the commands you need to enter are in bold and are underlined. The operation guide are in bold and italic):




Page 116

To restart the Solaris installation program, type "install-solaris". Solaris installation program exited.

# format Specify Disk (enter the number)

0 format>partition partition>modify 1 for All Free Hog Do you wish to continue creating a new partition table on above table [yes]?

Y or hit Enter key Free Hog partition [6]?

Hit Enter key Enter size of Partition 0 (/) (root)

10gb Enter size of Partition 1 (swap)

16gb Enter size of Partition 3 (/) (root) Note: This will later be re-labeled as /opt during the solaris-install.

55gb Enter size of Partition 4 (no label)

55gb Enter size of Partition 5 (no label - used svm mirroring)

700mb 7 (unassigned) Shows Table And Asks : Okay to make this the current partition table [yes]?

Y or hit Enter key Enter Table Name

"drive0" (including quotes) Ready to label disk, continue ?

Y and hit Enter key partition>print (Verify the drive is set up correctly) partition>quit format> volname “drive0” (including quotes) Ready to label disk?




Page 117

Y and hit Enter key format>quit # prtvtoc /dev/rdsk/c0t1d0s0 | fmthard -s - /dev/rdsk/c0t3d0s0 NOTE: this is all one command. There is a “space after the last dash (-) and before the /dev/rdsk/cot3d0s0. Results in fmthard: New volume table of contents now in place.

# install-solaris

p. Issue the command “install-solaris” to return to Suninstall mode and then you can continue the solaris install. Answer all the system configuration questions that are listed in order in the following table, all the answers are annotated in the Answer/Description/Example column and select F2_Continue/F2_OK after each entry is selected.

Table 9-3 Information for

Installation Description or Example Answer

Solaris Interactive Installation

Select Standard Installation F2_Standard

Eject DVD Select Automatically eject CD/DVD Automatic eject. F2_continue

Reboot After Installation

Select to auto reboot after installation completes. Auto Reboot. F2_continue

Licensing Sun Microsystems License agreement F2_Accept_License.

Geographic Region

Select Geographic Region. IMPORTANT: will need to install as North America/U.S.A to allow Motorola software function and support of platform.

North America F2_continue

System Locale Select the version of ISO for regional language specifics. NOTE: For Geographic Region = North America/U.S.A, select en_US.ISO8859-15

en _US.ISO8859-15 F2_continue

Select Products The products you would like to install. DO NOT select this product listed. [ ] Solaris 10 Extra Value Software........ 69.92 MB [ ] Sun Validation Test Suite 6.3......... 69.92 MB

F2_continue




Page 118

Additional Products

[X] None [ ] CD/DVD [ ] Network File System

None. F2_continue

Select Software [X] Entire Distribution ........................ 6191.00 MB Entire Distribution. F2_continue.

Select Disks Select the disk(s) from the Available box. It is recommended to select the hard disk labeled C0T1D0 from the Select Primary Disk page, when there are multiple hard disks. [X] c0t1d0 139989 MB (F4 to edit) [ ] c0t3d0 139989 MB

c0t1d0. F2_continue

Preserve Data Do you want to preserve existing data. This will be “No” for fresh installs.

F2_Continue

Automatically Layout Filesystem

Do you want to use the auto-layout to automatically layout your file system?

F4_Manual Layout

File System and Disk Layout

The summary for current file system displays F4_Customize

Customize Disk c0t1d0

Displays current partitioning F4_Options

Disk Editing Options

Select the show size and other options as described Show Size: {x} Mbytes Other options: [x} Show cylinder boundaries; [x] Load existing slices from VTOC Table Hit F2_OK which may bring up a warning, and then hit F2_OK again.




Page 119

Customize Disk c0t1d0

Displays the current partition layout per VTOC table Enter the mount points. Entry: Recommended: ===================================== Slice Mount Point Size (MB) 0 / 10245 1 swap 16386 2 overlap 139989 3 /opt 56325 4 56325 5 705 6 0 7 0 =====================================

Slice3: /opt Slice4: (blank) Slice5 (blank) Slice6 (blank) Slice7 (blank) F2_OK.

File System and Disk Layout

The summary of the new file system layout is displayed

<verify slice sizes as customized above> F2_continue

Remote Mount File Systems

Do you want to mount software from a remote file server? DO NOT do this, select F2_continue

F2_Continue

Profile Verification of previously customized data is displayed

F2_Begin_Installation

(may see) Warning changing install boot device

Warning that the configuration conditions are being changed.

F2_OK F2_Continue

q. The system starts to load OS and reboots. This will approximately take 1.25 hours.

Upon the completion of the install, the system will prompt to select to Configure Keyboard Layout. Select US_English and F2_Continue.

IMPORTANT: Use of ENGLISH will be required for future Motorola support.

NOTE: You may be prompted with a screen asking whether you want to override the system default NFS version. If so, select No to continue. r. If the DVD did not automatically ejected, eject as follows:

# eject s. Load the Motorola CGEMS Accessories DVD containing the recommended patches into

the Netra T2000 DVD drive.




Page 120

t. Log into system as root user. Enter the following commands: # svcadm disable sendmail # mkdir –p /patches/0820 # cp –f /cdrom/cdrom0/r3_os_up.zip /patches/0820 or, if using the R3.1-ems-accessories-dvd DVD:

# cp /cdrom/cdrom0/R3.1-ems-accessories-dvd.tar /export # cd /export # tar –xvf R3.1-ems-accessories-dvd.tar # cp r3_os_up.zip /patches/0820

NOTE: if cannot access /cdrom/cdrom0… message, verify DVD is mounted after install by using the mount command. May have to eject and re-insert.

# eject cdrom # cd /patches/0820 # unzip r3_os_up.zip > /dev/null After the file unzips drop put the system into system administration mode (run level 1) # init 1 Enter root password for system maintenance to continue. After dropping to the system administration mode continue. # cd /patches/0820/10_Recommended # ./install_cluster Enter “yes” to continue. Patching starts. Installation will take approximately 45-60 minutes.

WARNING: Failure to go to single user mode will result in incomplete install of patches and possible lockup of the install script. In the event of lockup Ctrl+C to break out. The install script should give report on the display of the patches installed and not installed. Verify the patches that installed against the list below. Reboot the box. Go to single user mode, and run the install_cluster again. After completion verify the remaining patches install.

After patch completion patch results are displayed. Verify following patches were able to be installed:




Page 121

126868-01 138159-01 125184-08 121136-02 127884-01 121104-04 119313-22 120543-11 125891-01 123611-04 123590-09 120410-29 119254-58 138075-02 138083-01 125731-02 119042-11 122911-13 137289-02 120094-21 121118-13 119090-31 121004-04 137093-01 127755-01 119812-06 137017-03 121095-02 120272-21 126206-04 125166-12 138291-01 127127-11 122239-03 127922-04 128000-01 128342-01 137871-02 136892-01 127892-06 119757-12 128300-04 125551-02 137111-05 127737-02 127853-02 125279-05 119783-07 120201-05 136882-01 119059-45 125719-13 137032-01 125539-04 119810-05 137321-01 137019-02 128306-05 120292-02 136998-05 128328-01 119764-06 138070-03 138060-03 120830-06 137080-01 124393-08 121308-14 138068-01 118712-22

NOTE: there are many patches that fail to install. These can be ignored. Seventy (70) patches should be successfully installed which should be verified against this list.

# cd /var/sadm/patch # ls

Verify this directory listing with above 70 patches. Individual ones can be verified with the following command. If any are not found or failed, you can try to re-install individually.

# showrev –a | grep <patch number> If one not found or failed: # cd /patches/0820/10_Recommended # patchadd -d <patch number>

Remove the r3_os_up.zip file to save space # cd /patches/0820 # rm r3_os_up.zip




Page 122

Copy the CLUSTER_README file to another location for later verification of the patch bundle level. Recommend /opt Record location: _________________________ # cp /patches/0820/10_Recommended/CLUSTER_README /opt Remove the 0820 directory to save space. # cd / # rm –r /patches/0820 Perform Appendix J, Firmware Upgrade Procedure before performing reboot. Return to this section after Firmware Upgrade to perform the reboot operation.

IMPORTANT: Perform Appendix J, Firmware Upgrade Procedure before performing reboot. Return to this section after Firmware Upgrade to perform the reboot operation.

# reboot u. Log into system as root and start to mirror the root file system. Execute the following

command to set up the mirroring for the various file systems: a) root Partition:

# metadb -a –f –c2 c0t1d0s5 c0t3d0s5 # metainit –f d11 1 1 c0t1d0s0 # metainit d12 1 1 c0t3d0s0 # metainit d10 –m d11 # cp /etc/system /etc/system.nosvm # cp /etc/vfstab /etc/vfstab.nosvm # metaroot d10 # echo "set md:mirrored_root_flag=1" >> /etc/system

b) swap Partition: # metainit -f d21 1 1 c0t1d0s1 # metainit d22 1 1 c0t3d0s1 # metainit d20 –m d21

c) /opt Partition: # metainit -f d31 1 1 c0t1d0s3 # metainit d32 1 1 c0t3d0s3 # metainit d30 –m d31

d) Make a copy of vfstab for recovery purposes, then check the /etc/vfstab file for correct entries for the /swap and /opt partitions as follows:




Page 123

# cd /etc # cp vfstab vfstab.sav # vi vfstab

Change: /dev/dsk/c0t1d0s1 to /dev/md/dsk/d20 Change: /dev/dsk/c0t1d0s3 /dev/rdsk/c0t1d0s3 to /dev/md/dsk/d30 /dev/md/rdsk/d30 Save the file.

e) View the vfstab file to verify it looks like below (there are 7 columns of data). # cat vfstab

#device device mount FS fsck mount mount

#to mount to fsck point type pass at boot options

# Note there is seven (7) columns of data!

fd - /dev/fd fd - no -

/proc - /proc proc - no -

/dev/md/dsk/d20 - - swap - no - /dev/md/dsk/d10 /dev/md/rdsk/d10 / ufs 1 no -

/dev/md/dsk/d30 /dev/md/rdsk/d30 /opt ufs 2 yes - /devices - /devices devfs - no -

ctfs - /system/contract ctfs - no -

objfs - /system/object objfs - no -

swap - /tmp tmpfs - yes -

f) Finish the root mirroring initialization and reboot the CGEMS platform. # lockfs –fa # init 6

g) Log back in as root after system restart, finish the mirroring process and verify

the mirror is set up correctly:




Page 124

# metattach d10 d12 # metattach d20 d22 # metattach d30 d32 # metastat –c >>> you will see something like below, repeat this command >>> until there are no resync-X% found d30 m 55GB d31 d32 (resync-10%) d31 s 55GB c0t1d0s3 d32 s 55GB c0t3d0s3 d20 m 16.0GB d21 d22 (resync-0%) d21 s 16.0GB c0t1d0s1 d22 s 16.0GB c0t3d0s1 d10 m 10GB d11 d12 (resync-31%) d11 s 10GB c0t1d0s0 d12 s 10GB c0t3d0s0

WARNING: Total mirroring process may take approximately ~2 hours to complete. Please wait for the completion of all mirroring before rebooting!

h) Setup boot block and then reboot the Netra T2000 platform.

# installboot /usr/platform/`uname –i`/lib/fs/ufs/bootblk /dev/rdsk/c0t3d0s0

(NOTE: this is just one command with a space between lines)

# init 0 (Note: system shuts down. Wait for {x}ok prompt, where “x” could be other character) {x}ok nvalias backup-root /pci@780/pci@0/pci@9/scsi@0/disk@3,0:a {x}ok nvstore {x}ok setenv boot-device disk backup-root net {x} ok nvstore {x}ok boot backup-root (Note: system boots from backup drive)

9. Log in as root and run the following commands:

# umount /home # sed '/\/home/ {s/\/home/#\/home/g;}' /etc/auto_master > /tmp/auto_master # cp /tmp/auto_master /etc/auto_master

10. Log in as root and create zfs:




Page 125

# cd / # umount /home # zpool create -m /home home mirror c0t1d0s4 c0t3d0s4 (Note: If you get an error msg: invalid vdev specification use '-f' to override the following errors: /dev/dsk/c0t1d0s4 is part of exported or potentially active ZFS pool home. Please see zpool(1M). Then you need to re-create zfs by the following command:) (# zpool create –f –m /home home mirror c0t1d0s4 c0t3d0s4)) # zfs set compression=on home

v. If you need to enable ftp and telnet on this machine, you can execute the following command to enable telnet and ftp service. See next step to configure to use these tools.

# svcadm enable ftp # svcadm enable telnet

w. By default, the ftp and telnet is disabled for root user. It is suggested for security reasons to keep these DISABLED. If you’d need to enable ftp and telnet for root user, please refer to Appendix A:Troubleshooting issue 5. Enabling ftp and telnet for root user will promote convenience, but it will impact system security. If you do not need these feature, ensure each is disabled (svcadm disable telnet).

# svcadm disable ftp # svcadm disable telnet

x. Login CGEMS as root, run the following command to set system parameters for Oracle application:

# echo 'set noexec_user_stack=1 set semsys:seminfo_semmni=100 set semsys:seminfo_semmns=1024 set semsys:seminfo_semmsl=256 set semsys:seminfo_semvmx=32767 set shmsys:shminfo_shmmax=4294967295 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=100 set shmsys:shminfo_shmseg=10' >>/etc/system

y. Visually verify the above system file set correctly

# cat /etc/system

z. Enable the T2000 autoboot feature for the CGEMS platform. Refer to Appendix H. aa. Reboot the CGEMS Machine by running the following command as root user.

# init 6 bb. After reboot, you can use Solaris general purpose debugger to check individual system

level parameters for Oracle application. If the result “fail to deference symbol”, go to the next step to force load the parameters.




Page 126

# adb –k System outputs: physmem fdb6b

Note: result of physmem may vary from system to system

Note: to run this command: type in each of the parameters and press enter to verify results match above.

Note: Parameters ‘shmmax’ and ‘shmmin’ will display “0”. noexec_user_stack/D seminfo_semmni/D seminfo_semmns/D seminfo_semmsl/D seminfo_semvmx/D shminfo_shmmax/D shminfo_shmmin/D shminfo_shmmni/D shminfo_shmseg/D $q (“Dollarsign+q”to quit the adb debugger)

cc. If the above fails to initialize, try to force load these shared memory configurations and re-run verification above.

# modload /kernel/sys/semsys # modload /kernel/sys/shmsys

dd. Verify autoboot remains enabled. First command from “sc prompt” and second from console prompt.

sc> showsc sc_powerstatememory

sc_powerstatememory true sc> console # eeprom | grep auto-boot

auto-boot?=true

ee. Disable keyboard break - As root user, make a backup copy of the kbd file, and execute

the following to disable inadvertent break commands. # cd /etc/default # cp kbd kbd.bak # vi kbd

Scroll down to the line: #KEYBOARD_ABORT =disable

In order to enable the line delete the ‘# ‘, save the file.

ff. cat the file and verify the line is enabled, ( line without #). .




Page 127

# cat kbd Scroll down and the line appears as follows:

KEYBOARD_ABORT =disable

gg. Enable the file change by executing kbd –i

# kbd -i #

hh. Verify the action was implemented from the serial screen send a break command from

the serial emulator in use. For example, if using putty, right mouse select on the tool-bar Special Command Break. Execution of above will send a message to the screen that a break was sent but it is ignored by UNIX.

From putty, right mouse select on the tool-bar Special Command Break # SC Alert: SC Request to send Break to host. Strike the enter key and note UNIX is still operational. The ‘break’ command is ignored. #

ii. Return to install pre-work section to continue with CGEMS after successfully installing

and configuration of Solaris.

Upgrade Real VNC



Page 128

Appendix D: Upgrade Real VNC

IMPORTANT: This Appendix must be read in it’s entirety before beginning work!!

This procedure was made to instruct the operator on how to install Real VNC properly.

1. Verify current VNC installation:

a. Login the Solaris as root using a telnet session. Run the following commands to verify the unlicensed version of VNC is installed.

# pkginfo vnc-E If the following line below is displayed then skip Appendix F, Real VNC install not needed. application vnc-E VNC Enterprise Edition for Solaris

b. Login the Solaris as root using a telnet session. Run the following commands to verify the unlicensed version of VNC is installed.

# pkginfo SFWvnc If the following result below is displayed then proceed to the next Section 2.0 to uninstall older version VNC and then Section 3.0 to install licensed Real VNC. system SFWvnc vnc - Virtual Network Computing

c. If both VNC packages are not installed, proceed to the Real VNC installation Section. If the older package is installed, proceed to Section 2.

ERROR: information for "SFWvnc" was not found ERROR: information for "vnc-E" was not found If neither vnc packages are installed, proceed to the Section 3.0 instructions to install licensed Real VNC.

Upgrade Real VNC



Page 129

2. Uninstall VNC (should not be needed for “fresh” install)

Detailed Steps

a. Login the Solaris as root using a telnet session. Run the following commands to stop all the current VNC sessions.

# pkginfo –l SFWvnc >>> If the vnc package information is displayed, continue to uninstall; >>> otherwise, the package is not installed and proceed to Step 3. # cd /opt/vncsol10_sparc # ./cleanvnc.ksh

b. Run the following command to remove the VNC install. 1) Remove SFWvnc package :

# cd /var/sadm/pkg

# pkgrm SFWvnc

j. Then answer all the questions listed in the following table:



SFWvnc Do you want to remove this package? [y,n,?,q] Enter “y” and hit enter

2) Remove SFWgcc34l package: # pkgrm SFWgcc34l

k. Then answer all the questions listed in the following table:



SFWgcc34l Do you want to continue with the removal of this package [y,n,?,q] y

Enter “y” and hit enter

3) Remove SFWgcmn package:

Upgrade Real VNC



Page 130

# pkgrm SFWgcmn

l. Then answer all the questions listed in the following table:



SFWgcmn Do you want to remove this package? [y,n,?,q] y Enter “y” and hit enter

4) Remove old VNC install/configuration scripts: # rm –r /opt/vncsol10_sparc

3. Install Licensed Real VNC

Detailed Steps

a. Transfer installvnc.ksh file in binary to /tmp directory : b. Login as root using a telnet session and change the file permissions:

# cd /tmp # chmod +x installvnc.ksh

c. Run the following command to setup VNC: # ./installvnc.ksh

d. As root user, verify root console is commented out in /etc/default/login file. If not, edit, comment out this line and

save the file:

#CONSOLE=/dev/console

e. To verify VNC is configured, use IE Browser on a PC that can network to Solaris box and enter the following url:http(s)://<IPaddress of Netra T2000>:5801, then select the OK button.

Upgrade Real VNC



Page 131

f. Select the Yes button to connect.

g. Enter the Solaris root login and password.

Upgrade Real VNC



Page 132

h. Login to the Solaris desktop with either the root or ems login. Use ems user to run Site Administration or Account Manager tool. Enter password for user when prompted.

i. When logging in as ems user, you MUST select Common Desktop Environment (CDE), and then select the OK button.

Upgrade Real VNC



Page 133

CAUTION: when logging in as ems user, if you select the "Java Desktop System, Release 3" option, you will not be able to log in! NOTE: after initially selecting the environment, you will not see this again.

j. To Exit the VNC desktop, select the EXIT button on the tool bar to logout of the desktop.

IMPORTANT: if you do not “EXIT” out of this desktop session, you will not be prompted for Solaris login/password or the Desktop Environment Chooser on the next log in.

Upgrade Real VNC



Page 134

Upgrade Real VNC



Page 135

Appendix E: Configuring Dual NICs IMPORTANT: This Appendix must be read in it’s entirety before beginning work!!

In order to enable two NIC in Solaris server, you need to login as root and modify the following files. /etc/hosts /etc/inet/ipnodes /etc/inet/netmasks /etc/hostname.XXX (XXX stand as network card name such as eri0,ce0,pcn0,eg1000g0 and etc.). /etc/defaultrouter

Before modifying these files they need to be backed up.

a) # cp /etc/hosts /etc/hosts.bak b) # cp /etc/inet/ipnodes /etc/inet/ipnodes.bak c) # cp /etc/inet/netmasks /etc/inet/netmasks.bak d) # cp /etc/hostname.XXX /etc/hostname.XXX.bak e) # cp /etc/defaultrouter /etc/defaultrouter.bak

There are four network interfaces on T2000. You will just use two of them: e1000g0 and e1000g1. The interface e1000g0 is planned for NBI, e1000g1 for SBI. If you have configured the domain for T2000 box, then /etc/hosts file should look like below:

# more /etc/hosts 127.0.0.1 localhost <NBI IP> <hostname1> loghost

<SBI IP> <hostname2> <sbi FQDN>

NOTE: hostname1: <hostname1> should be the same as the hostname of CGEMS Machine. You can issue a “hostname” command on CGEMS Machine and note down the hostname. If you want to change the hostname of the CGEMS Machine, follow these steps: edit /etc/nodename file, replace the old hostname with new hostname in this file; replace the hostname in /etc/hosts, /etc/hostname.e1000g0, /etc/inet/ipnodes; reboot the system.

NOTE: hostname2: <per site network plan>. <hostname1> should be different from <hostname2>.

Upgrade Real VNC



Page 136

Note: In real deployment, the T2000 box should be in a domain. But if you’re testing CGEMS with NE Simulator and the T2000 box is not in any domain, you can use static DNS, and then /etc/hosts should be like the following: # more /etc/hosts 127.0.0.1 localhost <NBI IP> <hostname1> loghost

<SBI IP> <hostname2> <hostname2>.<domainname2> Note for testing: you should also add the following line in /etc/hosts on NE Simulator Machine:

<SBI IP> <hostname2>.<domainname2>

NOTE: domainname1, domainname2: They could be any valid domain name.

The /etc/hostname.e1000g0 and hostname.e1000g1 file should be like below: # more /etc/hostname.e1000g0

<hostname1>

# more /etc/hostname.e1000g1

<hostname2>

The /etc/inet/ipnodes file should be like below: # more /etc/inet/ipnodes

::1 localhost

127.0.0.1 localhost

<NBI IP> <hostname1> loghost

<SBI IP> <hostname2>

The /etc/inet/netmasks should depend on the SBI and NBI IP. For example, SBI IP is a.b.c.d, NBI IP is e.f.g.h, then /etc/inet/netmasks should look like below :

# more /etc/inet/netmasks

a.0.0.0 255.0.0.0

e.f.g.128 255.255.255.192

DNS for EMS server may need updated when adding a NIC. The file /etc/resolv.conf may need modified as below:

# more /etc/resolv.conf

domain <domainname>

nameserver <additional/new DNS server IP>

Make sure the following line is in /etc/nsswitch.conf: host: files dns

Remove the default route on NBI initially configured during Solaris installation: # route delete default <IP Address>

Add the default route for the SBI: # route add default <IP Address>

Verify modified routing table:

Upgrade Real VNC



Page 137

# netstat -r

The /etc/ inet/defaultrouter should be updated to reflect above changes permanently: # more /etc/defaultrouter

<SBI next hop Router IP>

Once the Dual NICs has been confirmed to work correctly, the backup files may be deleted..

f) # rm /etc/hosts.bak g) # rm /etc/inet/ipnodes.bak h) # rm /etc/inet/netmasks.bak i) # rm /etc/hostname.XXX.bak j) # rm /etc/defaultrouter.bak

CGEMS Platform Installation Check Lists



Page 138

Appendix F: CGEMS Platform Installation Check Lists

This section provides the pre-installation and post-installation checklists that are to be used before and after CGEMS installation. Users should record the result of each line item following the verification process. If any anomalies exist, Motorola CGEMS Support team needs to be contacted to resolve any issues before installing CGEMS software.

Necessary Information

Identify the computer and servers Fully Qualified Domain Name (FQDN) or IP required during CGEMS installation and configuration. These will be verified during the DNS check below. CGEMS Configuration Information

CGEMS Target computer FQDN/IP NTP Server FQDN/IP CGEMS Target computer domain name EMS Administrative User login details (username/password)

CGEMS Pre-installation Checklist

The pre-Installation checklist is to be used prior to installing CGEMS software on a solaris platform.

Table 9-4 Pre-installation Checklist Solaris machine Requirements Verification Process

Netra T2000, 8 core, 1.2GHz CPU In Solaris command window issue a “psrinfo -v” command to check the CPU frequency. (0-31 virtual processors running at 1200Mhz)

Hard Disk size and with minimum 20.0 GB free for CGEMS target install

In Solaris command window issue a “iostat -E” command to check the size of the Hard Disk. Note: Ignore all the media errors, just focus on the size of the hard disk. (2 hard disks @ ~146Gb each) In Solaris command window issue a “df –h” command to check space. (/opt partition should have minimum of 20Gb available CGEMS install)




Page 139

16 GB RAM In Solaris command window issue a “prtdiag -v > mem_size.txt” command and visually verify using command “vi +/Memory mem_size.txt” (Memory size: 16368 Megabytes).

DVD R/CD R/W drive Visual 10/100/1000M Base-T network connection

Visual. In Solaris command window issue an “ifconfig -a” command to check network interfaces. Verify that there are at least one interfaces: e1000g0 (two if dual-homed configuration, e1000g1)

Solaris OS version 5.10(U4) In Solaris command window issue a “uname -a” command to check the Solaris OS version (5.10). Issue a “more /etc/release” command to check the Solaris 10 8/07 s10s_u4wos_12b SPARC.

10_Recommended patches installed Examine the CLUSTER_README file found at /patches/0820/10_Recommended or copied to /opt. (Verify: NAME: Solaris 10 Recommended Patch Cluster DATE: August 20, 2008)

NTP service is configured and online Run command: svcs ntp

Get to the sc> prompt from root console serial port connection: #. sc>showhost … sc> console Returned to console port.

Screen returns with the system firmware version and host flash versions. Record and verify against Release Notes (Beginning with R03.00.12 the firmware version should be updated, refer to Appendix J.) System Firmware: _______________________________Netra [TM] T2000: Host flash versions: Hypervisor:_____________________________________ OBP: ___________________________________________ Netra [TM] T2000 POST:_________________________

Reserved TCP/UDP Ports not reserved by another application (established) 6000-7000 (dynamic allocated range used by Carrier EMS wrapper software – verify none of these are ESTABLISHED by another application)

In Solaris command window issue a “netstat -an | grep '*.6[0-9]\{3\}' ” command, there should be nothing displayed as ESTABLISHED.

SNMP service installed and operational In Solaris command window issue a “/usr/sfw/sbin/snmpd -v” command to check the SNMP service information (NET-SNMP version should be 5.0.9 or higher)

Domain Name Service (DNS) In Solaris command window issue a “domainname” command to check the Domain Name information.




Page 140

If not exist: 1) cat /etc/resolv.conf and look for “domain <e.g., ftw.mot.com> 2. edit /etc/defaultdomain and enter the domainname per your site network plan (e.g., ftw.mot.com).

Check directory privilege Ensure that the privilege permission of /tmp folder is 777. Issue a command “ls -al / | grep ' tmp$' “, the privilege of /tmp folder should be “drwxrwxrwt”. If not, issue a command “chmod 777 /tmp”.

Check IP config Ensure that there is no virtual network interface in Solaris. In Solaris command window issue “ifconfig -a” command (there should be at a minimum two interfaces: lo0, e1000g0 (if dual-homed then add eg1000g1; and all IPv4)

Verify VNC Server is running In Solaris command window issue a “ps -elf | grep Xvnc” command to verify that the Xvnc server is running (You should see Xvnc :1 –desktop in the result).

Verify /home partition and mirroring From Solaris command window: # zpool list you should see SIZE = 55Gb and AVAIL = ~55Gb # zpool status you should see mirror c0t1d0s4 and c0t3dos4 ONLINE and “No known data errors” # metastat –c you should see: d30 m 55GB d32 d31

d32 s 55GB c0t3d0s3

d31 s 55GB c0t1d0s3

d20 m 16.0GB d22 d21

d22 s 16.0GB c0t3d0s1

d21 s 16.0GB c0t1d0s1

d10 m 10GB d12 d11

d12 s 10GB c0t3d0s0 d11 s 10GB c0t1d0s0

Verify /opt partition and mirroring From Solaris command window: # mount /dev/dsk/c0t3d0s3 /mnt # cd /mnt You should see both Sun and EMS (if installed) software directories # cd / # umount /mnt

Verify /swap space From Solaris command window: # swap –l you should see two (1) mounted partition




Page 141

having with approximately 33580768 blocks.

System Planning Worksheet



Page 142

Appendix G: System Planning Worksheet

Items Example Comment Primary IP (e1000g0) (used for both NBI and SBI in a single NIC configuration; otherwise becomes the NBI

Communicate with the public network

Secondary IP (e1000g1) (used for SBI in a dual-homed configuration)

Communicate the managed Network Elements (NEs).

NTP Stratum I/II/III Server IP Router IP Default router DNS IP(s) May be more than one search

domains Netra T2000 “hostname” CGEMS box hostname used as part

of the FQDN. To find hostname: # hostname

Domain Name Used with hostname to make the FQDN (hostname + domain name) To find domain name: # cat /etc/domainname -or- # cat /etc/resolv.conf

System account list

Table 9-5 System account list

Account Name Password Privilege CGEMS Administration Account

<as selected by installer>

<as selected by installer>

1. Login Topology Manager, 2. Login Account Manager, 3. Login Site Administration

EMS Solaris Account ems <same as selected for CGEMS Admin Account above>

1. Only ems user can start Site Administration. 2. Config vnc for ems user: Create vnc desktops (sessions),

System Planning Worksheet



Page 143

change vnc password. 3. It is recommended to upload files that will be used by CGEMS using ems account, this will avoid some privilege error.

Database Solaris Account

oracle oracle 1. Manage database such start/stop oracle

Solaris OS Administrator

root 1. Install Solaris 10 2. Set up VNC 3. Configure Dual NICs 4. Install Oracle 5. Install CGEMS

ALOM user account Admin motorola (suggested) <or, as selected by installer>

Enable Autoboot on T2000



Page 144

Appendix H: Enable Autoboot on T2000 WARNING: Running without a UPS backup could cause UNIX file system

corruption, data loss, and potential hardware failures if power is bounced multiple times.

1. From the serial console port connection, execute #. to return to the “sc> prompt”.

# #.

sc>

2. At the sc prompt execute “showsc” and check the value of the sc_powerstatememory

parameter. If the value is “true” go to step 4. Otherwise continue. sc> showsc sc_powerstatememory

3. If the sc_powerstatememory is set to “false” then change the value to “true” and verify.

sc> setsc sc_powerstatememory true sc> showsc

sc_powerstatememory true

4. At the sc prompt enter console to return to the Unix serial console.

sc> console

Enter #. To return to ALOM

#

5. At the console prompt enter “eeprom” display and load command to verify the current

Unix auto boot parameter. # eeprom auto-boot?

6. If “auto-boot=false” then change the value to “true” and verify. If auto-boot?=true stop.

# eeprom auto-boot?=true # eeprom | grep auto-boot

auto-boot?=true

7. Return to Appendix C.

USB Drive Procedures



Page 145

Appendix I: USB Drive Procedures This procedure is for the proper installation and removal of USB thumb drives on the Enterprise and Netra T2000’s running the Motorola EMS software application. It assumes the system was originally installed using the appropriate product installation MOP. A USB drive may be inserted into any USB port on the T2000. Enterprise T2000 have two front and two rear ports. Netra T2000 has only two rear ports. For the remainder of this document the term T2000 will be used and refers to both platforms.

Detailed Steps

[ ] Step 1 Connect to T2000 with serial console or telnet session. a) Connect via serial port using a laptop with Hyper-Terminal (or similar) application or via a telnet

session. Use CAUTION when connecting to serial console to prevent a system break being sent. Refer to EMS Product Bulletin, wimax_g_pems_014-1.

b) Login as root user. c) From / verify if directory rmdisk exists. If it does not create it.

# mkdir rmdisk

d) Stop vold. From / execute: # /etc/init.d/volmgt stop

e) Insert the USB drive into one of the T2000 USB ports.

Start vold. From / execute: # /etc/init.d/volmgt start

f) Verify the USB drive detection and mounting. In this case the device type is a Kingston drive.

#cd /rmdisk #ls kingston rmdisk0

g) Copy desired files from the USB drive to the appropriate folders.

When operations completed and ready to remove the USB drive: #/etc/init.d/volmgt stop

USB Drive Procedures



Page 146

h) Remove the USB drive from the T2000 USB port. Start vold. From / execute:

# /etc/init.d/volmgt start.

i) Remove rmdisk directory.

From / execute rm –r rmdisk # rm –r rmdisk # ls (No rmdisk directory listed).

Firmware Upgrade Procedure



Page 147

Appendix J: Firmware Upgrade Procedure Prerequisites: 1. Warning: Firmware upgrade requires the system be powered down during the process. Upgrades should be performed during scheduled maintenance windows. 2. Firmware upgrade requires ftp accessible system from which the software will be transferred. This could involve either: 1) a Windows box containing an FTP server (e.g., FreeFTPd) and a Cat-5 network cable to EMS box’s network management port; or, 1) another Sun box with FTP server software connected to EMS box. 3. Firmware upgrade requires the System Console Network Management Port be configured with an ip in order to access the system with the software referenced in 2 above. 4. Firmware upgrade is provided in .zip format on the EMS Accessories DVD.

a. The CGEMS (Netra T2000) firmware 6.6.5 is contained in the file: CGEMSfw.zip Host flash versions: OBP 4.28.9 2008/06/30 21:26 Hypervisor 1.6.4 2008/06/06 04:57 Netra[TM] T2000 POST 4.28.9 2008/06/30 21:59

b. Copy the corresponding <CGEMS>.zip file to the default directory on the ftp server machine

(e.g., on a laptop – C:\Inetpub\ftproot). c. Unzip the file at this location.

5. From laptop, connect to T2000 via serial port as defined in Installation MOPs Appendix C pre-requisites. Use CAUTION when connecting to serial console to prevent a system break being sent. Refer to EMS Product Bulletin, wimax_g_pems_014-1. NOTE: this is the recommended method as a result of product testing. There are other ways to connect for a serial connection (such as via a Terminal Server) but it is STRONGLY RECOMMEDED to use the Silver-9-pin Sun provided adaptor when connecting via a Laptop computer. 6. On Laptop, disable any firewall software that may be running (e.g., Black Ice). 7. Log in with “admin” and password. NOTE that when on the console port and when at the “ok prompt”, use command “#.” to get to the “sc> prompt”. 8. Determine the version of the system firmware. sc>showhost Screen returns with the system firmware version and host flash versions. System Firmware: ________________________________ Netra[TM] T2000: __________________________________ Host flash versions: Hypervisor: ___________________________________________________




Page 148

OBP: __________________________________________________________ Netra[TM] T2000 POST: _______________________________________ 8. Compare the displayed version to the current version CGEMS Release Notes firmware specifications to determine if firmware upgrade is needed. To Configure the System Controller Network Management Port

Set these network parameters according to the specific details of your network configuration:

• if_network - Specifies whether the SC is on the network or not • netsc_ipaddr - IP address of the system controller • netsc_ipgateway - IP address of the gateway for the subnet • netsc_ipnetmask - Netmask for the system controller subnet

To configure these parameters, use the setsc command. The usage is:

sc> setsc parameter

1. Set the if_network parameter to true.

sc> setsc if_network true

2. Set the if_connection parameter to the connection type as telnet.

sc> setsc if_connection telnet

3. Set the network parameters as follows.

a. Set the IP address for the system controller.

sc> setsc netsc_ipaddr service-processor-IPaddr

b. Set the network gateway for the system controller.

sc> setsc netsc_ipgateway gateway-IPaddr

c. Set the netmask for the system controller.

sc> setsc netsc_ipnetmask 255.255.255.0




Page 149

This example uses 255.255.255.0 to set the netmask. Your network environment subnet might require a different netmask. Use a netmask number most appropriate to your environment.

d. Set dhcp for the system controller.

sc> setsc netsc_dhcp false

4. Use the showsc command to verify that the parameters were set correctly.

sc> showsc

Advanced Lights Out Manager CMT v1.x

parameter value

--------- -----

if_network true

if_connection telnet

if_emailalerts false

netsc_dhcp false

netsc_ipaddr xxx.xxx.xxx.xxx netsc_ipnetmask 255.255.255.0

netsc_ipgateway xxx.xxx.xxx.xxx mgt_mailhost

mgt_mailalert

sc_customerinfo

sc_escapechars #.

sc_powerondelay false

sc_powerstatememory false

sc_clipasswdecho true

sc_cliprompt sc

sc_clitimeout 0

sc_clieventlevel 2

sc_backupuserdata true

diag_trigger power-on-reset error-reset

diag_verbosity normal

diag_level min

diag_mode normal

sys_autorunonerror false

sys_autorestart reset

sys_eventlevel 2

ser_baudrate 9600




Page 150

ser_parity none

ser_stopbits 1

ser_data 8

netsc_enetaddr xx:xx:xx:xx:xx:xx

sys_enetaddr yy:yy:yy:yy:yy:yy

5. Connect the cat-5 network cable from the laptop to the SCNM port.

Note - After setting the configuration parameters, you must reset the system controller for the new values to take affect.

6. Run the system reset command at the sc>prompt

sc> resetsc

Are you sure you want to reset the SC [y/n]? y

User Requested SC Shutdown

The system controller resets, runs diagnostics, and returns to the login prompt (on the serial console).

7. Login as admin and the appropriate password and poweroff the system in order to upgrade the firmware.

sc> poweroff


User Requested SC Power Off Host

The system is now powered off when the message:

SC Alert: Host system has shut down.

8. Execute the flashupdate command.

The flashupdate SC command updates the system controller flash image and the host firmware. The flashupdate command requires the following information:

• IP address of an FTP server on the network that can access the flash image. • Full path name to the flash image that the IP address can access. • Username and password of an account registered on the system that is specified by the IP address.




Page 151

The command usage is as follows:

sc>flashupdate [-s IPaddr -f pathname] [-v]

where:

• -s IPaddr is the IP address of any FTP server on the network that can access the flash image • -f pathname is the full path name to the flash image on Solaris machine or the flash image file

name on a PC machine, (\<firmware_folder\Sun_System_Firmware-xxxx.bin>) • -v is the flag to turn on verbose message output

sc> flashupdate -s xxx.xxx.xx.xx -f pathname

Username: username

Password: password Update complete. Reset device to use new image.

sc>

9. Set the if_network parameter to false.

sc> setsc if_network false

10. Disconnect the cat-5 network cable from the SCNM port.

11. From the serial console reset the system controller.

After the flash has been updated, you must reset the system controller for the new image to take affect. To reset the system controller, issue the resetsc command, as shown below.

Note - To bypass the confirmation prompt, you can use the -y flag with the resetsc command. If resetsc is issued from a Telnet or SSH session, upon reset the Telnet or SSH session will be terminated. The output from the reset will be displayed on the serial console on the system controller.

sc> resetsc


User Requested SC Shutdown




Page 152

The system controller resets, runs diagnostics, and returns to the login prompt (on the serial console)..

12. Login as admin and appropriate password and verify firmware version by running the showhost command and verify it matches listing above in pre-requisites.

sc>showhost

13. Power on the system at the sc> prompt

sc> poweron

Host system resets. Type console at the sc> prompt to observe the system reset and power up messaging.

sc> console

14. After power up system is ready to resume normal operation.

15. Return to Appendix C, Solaris 10 OS installation, patch upgrade section to reboot the box.

Oracle Patch Upgrade



Page 153

Appendix K: Oracle Patch Upgrade

IMPORTANT:

If the Oracle version is 10.2.0.4.0, Appendix K is not needed (previously installed)

-bash-3.00# su - oracle -c "echo quit | sqlplus /nolog" | grep Release | awk '{print $3}'

After Oracle was fresh installed by “ems_database_install.bin” and before any EMS fresh install, we can perform the Oracle patch

After the EMS fresh/upgrade install reports that Oracle needs to be patched, exit the EMS upgrade, and perform the Oracle patch.

After the EMS fresh/upgrade install reports that Oracle needs to be patched, you can continue to finish the EMS upgrade, then do the Oracle patch when EMS is running

The new standalonemode configuration will have Oracle server installed on both boxes, therefore both boxes will require this Oracle patch.

If the EMS fresh/upgrade install did not report that Oracle needs to be patched, then no patch is needed (currently installed).

CAUTION:

During Oracle patch upgrade, DO NOT do EMS DB install, EMS install, EMS uninstall, Backup, Restore, Upgrade, or Migrate.

DO NOT do Oracle maintenance including create/drop tables, Oracle parameters adjust, shutdown/start Oracle, or dump/import data.

It is not recommended to do EMS batch operations during Oracle patch upgrade.

1.0 Oracle Patch Upgrade Pre-Work

1. Obtain the Oracle patch bundle from the EMS Accessories DVD. 2. Copy the 3 files to “/opt/EMSDB/Oracle_tmp/bin” (create this directory if not exist):

upgrade.pl, 10gr2_db_sol.cpio and p6810189_10204_Solaris-64.zip

a) If the EMS fresh/upgrade installation tips that the Oracle is suggested to patch, please find the




Page 154

“upgrade.pl” at “/opt/EMSDB/Oracle_tmp/bin”. b) Download “upgrade.pl” from the root path of the EMS Accessories DVD . c) Run checksum and verify correct software: digest –v –a md5 <filename> d) Copy “upgrade.pl” from “/opt/EMSDB/Oracle_tmp/bin” to “/opt/EMS”

3. Verify the platform /etc/system file parameters are correctly set for oracle (refer to Installation MOPs Appendix C).

# cat /etc/system set noexec_user_stack=1 set semsys:seminfo_semmni=100 set semsys:seminfo_semmns=1024 set semsys:seminfo_semmsl=256 set semsys:seminfo_semvmx=32767 set shmsys:shminfo_shmmax=4294967295 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=100 set shmsys:shminfo_shmseg=10

4. Make sure the environment of the Oracle is “online” and is running. a) Run “svcs –a | grep ems” and verify LISTENER and ems_db are “online.

5. Make sure using “root” user when you execute the “upgrade.pl” 6. Set the execution permission for the “upgrade.pl”

-bash-3.00# cd /opt/EMS

-bash-3.00# chmod +x upgrade.pl

7. Check if the system resource is enough for the upgrade. -bash-3.00# ./upgrade.pl resource

current_memory_size : 1523M, require_memory_size: 1200M

current_disk_size : 46953M, require_disk_size: 12512M

-bash-3.00#

The disk space required is calculated dynamically based on different servers. If disk size is not sufficient refer to Trouble Shooting Appendix for suggestions on files to clean/remove. If memory size not sufficient, suggest stopping EMS services to provide additional memory resources.

8. If all of above are ok, go to “Step by Step” procedures below. Otherwise please contact EMS Development Support for additional guidance. Provide the /etc/system file to EMS Development team.

2.0 Step by Step to Perform Oracle Patch Upgrade

After the pre-check successful, use “root” user and execute bellow steps to do the Oracle Patch Upgrade: -bash-3.00# cd /opt/EMS

-bash-3.00# ./upgrade.pl 10gr2_db_sol.cpio p6810189_10204_Solaris-64.zip

When the “Oracle Upgrade Finished Successfully!” is tipped, the Oracle Patch Upgrade is finished with success. A patch upgrade log file is found in the same directory.

3.0 Oracle Patch Upgrade Post-work

1. If the EMS is installed as a combined mode configuration, no EMS reboot is required. This includes when both boxes are configured in combined mode for standalonemode use.




Page 155

4.0 Tips

1. A minimum of one hour for a typical EMS database. It is up to how many DB instances and how much data in every DB instance. The one hour upgrade is typical for only one DB instance and minimal data.

2. If any errors or exceptions are shown during upgrade and the upgrade failed, please refer to Chapter J.4

5.0 Impact on Running EMS Services

1. EMS on DB server will be restarted. The EMS in combine mode and the NE/CPE EMS in standalone mode are deployed the Oracle DB at the same machine. These EMS services will be shutdown for about 10 minutes while the database version switch. The CPE EMS will not be shutdown during the upgrade. But it will lose the connection to the DB and in unavailable status while the DB on the NE EMS is out of service.

2. A minimum of 10 Minutes Unavailable Status. The EMS will be in unavailable status for almost 10 minutes or longer. It depends on how many records are updated by the EMS during the period from the upgrade begins to the EMS is shutdown. To deal with the data during upgrade will cost about 10 minutes in typical environment. So we are not recommending to do batch operations on during the Oracle Patch Upgrade.

6.0 Oracle Patch Upgrade Troubleshooting

Get the error “Failed to get the current Oracle version” or “The oracle_patch_package's version is lower than the oracle_install_package's version”

Please check if the “ORACLE_HOME” in “.profile” is directed to the correct path of the oracle software. Please check if the banner printed by the command “sqlplus /nolog” is correct. The oracle version will be printed in the banner.

Get the error “Failed to get oracle version from 10gr2_db_sol.cpio, it may be an invalid oracle install package” or “Failed to get oracle patch version from p6810189_10204_Solaris-64.zip, it may be an invalid oracle patch package.”

It may be caused by an invalid oracle patch package Please check if the Oracle installation package or the patch package is in the correct format. The official format of Oracle installation is “.cpio”. And for the patch package, its official format is “.zip”.

The Oracle Patch Upgrade failed or the upgraded Oracle is in abnormal status.

Use “root” user to execute: -bash-3.00# cd /opt/EMS

-bash-3.00# ./upgrade.pl rollback

Setting up communications between neighboring EMSes.



Page 156

Appendix L: Setting up communications between neighboring EMSes.

IMPORTANT: Perform the following steps on both border EMSes.

1. Launch an ems user VNC session and launch the EMS Account Manager. Log in and add a new user with NBI user access class.

a. /opt/EMS/bin/NMSAcctMgr.sh 2. On the “Inter EMS Communication” tab, set EMS-EMS Link to Enabled and fill in your EMS

name field with the unique name for this EMS. 3. On the “Neighbor EMSes” tab, add a row and fill in the EMS Unique ID field with the unique

name for the neighbor EMS. In the EMS FQDN field, enter the FQDN (no IP Address is allowed) of the neighbor EMS. In the Login Name field, enter the username from the neighbor EMS (not yours) and enter the password for this neighbor EMS account by selecting the Set Password button. (NOTE: this established the reciprocating neighbor EMS users between yours and your neighbor).

Record: Yours:_______________________________Neighbors:_______________________________

4. If a Domain Name Server (DNS) is not present for the network, update the /etc/hosts file on the EMS by adding a line with the following form:

<IP_ADDRESS><FQDN> FOR EXAMPLE:

199.4.77.33 ems1 ems1.motorola.com loghost Once communication has been configured, the HTTPS certificates that the EMSes use must be imported into each other’s truststore. Follow the below procedure on both EMSes to import the HTTPs certificates into each truststore. Note that each time a new certificate is generated on one EMS, it must be added to any neighboring EMS’ truststore, including if the EMS is re-installed. Also, if an EMS is re-installed, its truststore is erased; therefore the certificates of any neighboring EMSes must be imported into its truststore again.

NOTE: All paths given assume the default EMS installation directories were used when installing the EMS. If a directory other than /opt/EMS was used, please use the correct path accordingly.

1. Copy the neighbor EMS’s certificate to your EMS. The location for the certificate is /opt/EMS/conf/certificates/nsm.crt.

2. Launch an ems user VNC Session. 3. Launch the Java Control Panel UI:

a. If necessary, set the system DISPLAY variable to allow the GUI to be displayed.

Setting up communications between neighboring EMSes.



Page 157

b. cd /opt/EMS/jre/bin c. ./jcontrol

4. On the Security tab, select the Certificates… button. 5. Verify that the Certificate type dropdown box is set to Trusted Certificates and that the User tab is

shown. 6. Select the Import button. 7. From the Open dialog displayed, select Files of Type “All Files” and locate the certificate that was

copied from the neighbor EMS in step 1. 8. Select the certificate and select the Open button. 9. Select the Close button to close the Certificates dialog and then select OK to close the Java Control

Panel. 10. Re-start the cgems_tm and cgems_cm services.

a. svcs restart cgems_cm b. svcs restart cgems_tm

11. For any initial configuration and setup issues encountered Refer to Appendix A, Trouble Shooting. 12. Return to Verify System Functionality and Post-Work section.

Configuring Dual NICs



Page 158

Appendix M: Configuring Dual NICs In order to enable two NIC in Solaris server, you need to login as root and modify the following files.

/etc/hosts /etc/inet/ipnodes /etc/inet/netmasks /etc/hostname.XXX (XXX stand as network card name such as eri0,ce0,pcn0,eg1000g0 and etc.). /etc/defaultrouter

Before modifying these files they need to be backed up.

k) # cp /etc/hosts /etc/hosts.bak l) # cp /etc/inet/ipnodes /etc/inet/ipnodes.bak m) # cp /etc/inet/netmasks /etc/inet/netmasks.bak n) # cp /etc/hostname.XXX /etc/hostname.XXX.bak o) # cp /etc/defaultrouter /etc/defaultrouter.bak

There are four network interfaces on T2000. You will just use two of them: e1000g0 and e1000g1. The interface e1000g0 is planned for NBI, e1000g1 for SBI. If you have configured the domain for T2000 box, then /etc/hosts file should look like below:

# more /etc/hosts 127.0.0.1 localhost <NBI IP> <hostname1> <nbi FQDN> loghost

<SBI IP> <hostname2> <sbi FQDN,if needed>

NOTE: hostname1: <hostname1> should be the same as the hostname of Low Tier EMS Machine. You can issue a “hostname” command on Low Tier EMS Machine and note down the hostname. If you want to change the hostname of the Low Tier EMS Machine, follow these steps: edit /etc/nodename file, replace the old hostname with new hostname in this file; replace the hostname in /etc/hosts, /etc/hostname.e1000g0, /etc/inet/ipnodes; reboot the system.

NOTE: hostname2: <per site network plan>. <hostname1> should be different from <hostname2>.




Page 159

Note: In real deployment, the T2000 box should be in a domain. But if you’re testing Low Tier EMS with NE Simulator and the T2000 box is not in any domain, you can use static DNS, and then /etc/hosts should be like the following: # more /etc/hosts 127.0.0.1 localhost <NBI IP> <hostname1> <hostname1>.<domainname1> loghost

<SBI IP> <hostname2> <hostname2>.<domainname2>

Note: you should also add the following line in /etc/hosts on NE Simulator Machine:

<SBI IP> <hostname2>.<domainname2>

NOTE: domainname1, domainname2: They could be any valid domain name.

The /etc/hostname.e1000g0 and hostname.e1000g1 file should be like below: # more /etc/hostname.e1000g0

<hostname1>

# more /etc/hostname.e1000g1

<hostname2>

The /etc/inet/ipnodes file should be like below: # more /etc/inet/ipnodes

::1 localhost

127.0.0.1 localhost

<NBI IP> <hostname1>

<SBI IP> <hostname2> loghost

The /etc/inet/netmasks should depend on the SBI and NBI IP. For example, SBI IP is a.b.c.d, NBI IP is e.f.g.h, then /etc/inet/netmasks should look like below :

# more /etc/inet/netmasks

a.0.0.0 255.0.0.0

e.f.g.128 255.255.255.192

DNS for EMS server may need updated when adding a NIC. The file /etc/resolv.conf may need modified as below:

# more /etc/resolv.conf

domain <domainname>

nameserver <additional/new DNS server IP>

Make sure the following line is in /etc/nsswitch.conf: host: files dns

Remove the default route on NBI initially configured during Solaris installation: # route delete default <IP Address>

Add the default route for the SBI: # route add default <IP Address>

Verify modified routing table:




Page 160

# netstat -r

The /etc/ inet/defaultrouter should be updated to reflect above changes permanently: # more /etc/defaultrouter

<SBI next hop Router IP>

Once the Dual NICs has been confirmed to work correctly, the backup files may be deleted..

p) # rm /etc/hosts.bak q) # rm /etc/inet/ipnodes.bak r) # rm /etc/inet/netmasks.bak s) # rm /etc/hostname.XXX.bak t) # rm /etc/defaultrouter.bak

StandaloneMode CGEMS Overview



Page 161

Appendix N: StandaloneMode CGEMS Overview Pre-requisites:

1. New commissioned Netra T2000 Sun Server Box 1 -OR- operational combined mode Netra T2000 Sun Server EMS Box 1 with same WMX-R3.1 release.

2. Netra T2000 Sun Server Box 2 commissioned per Install MOP with same WMX-R3.1 release. 3. All AP/CAPC nodes being migrated from the current EMS should be system release WMX-R3.1 or

greater (i.e, a version of software that supports a claProtocolVersion of 002 or higher). 4. All remote CSN devices and NOC will need to be configured with new EMS Box 2 IP

Address/FQDN. Overview: (Fresh or current operational view)

Process Summary: (fresh installation)

1. Install/commission a new Carrier EMS Box 1 in combined mode following the Installation MOP. 2. Install/commission a new Carrier EMS Box 2 in combined mode following the Installation MOP. 3. Configure EMS Box 1 as CPE Manager. 4. Configure EMS Box 2 as NE Manager.

Process Summary: (when operational as a single combined and adding new box)

1. Install a new Carrier EMS Box 2 in combined mode following the Installation MOP. 2. Backup the current Box 1 EMS database using the Site Amin tool.

Box 1 CPE Manager

1. Configure UI for CPE Mgr only 2. Migrate EMS IP address for NEs

to new Box 2 (one at a time) 3. Remove AP/CAPCs from db (if

migration) 4. Post-work

Box 2 NE Manager

1. Configure UI for NE Mgr only 2. Remove CPEs from db (if

migration) 3. Post-work

Box 1 Operational or fresh

combined mode CGEMS R03.00.14.XX

(AP/CAPC/CPE)

Box 2 New commissioned

combined mode CGEMS R03.00.14.XX

(AP/CAPC/CPE)

Re-configured to- Re-configured to-

StandaloneMode CGEMS Overview



Page 162

3. Restore the database from the current Box 1 EMS onto the new EMS Box 2. 4. On the new EMS Box 2, delete the CPE nodes from the database using the EMS provided scripts. 5. Switch the EMS configuration file option to change the new EMS Box 2 to operate in NE Mgr

mode. (Note: this will hide all the CPE-related UI menu options) 6. On the original EMS Box 1, select the option to migrate the AP/CAPC nodes to the new EMS IP

Address (Box 2) one-at-a time and verify success. 7. Reboot the new EMS Box 2. Monitor NE state transitions. 8. After ensuring that the new EMS Box 2 is functional and managing the migrated AP/CAPC nodes;

and, during an appropriate maintenance window, remove the AP/CAPC nodes from the current EMS Box 1 database using the provided scripts.

9. On the current EMS Box 1, switch the EMS configuration file option to change EMS to operate in CPE Mgr mode. (Note: this will hide all the NE(AP/CAPC)-related UI menu options)

Fallback Summary: (current operational)

1. Re-configure the CPE Mgr Box 1 for both CPE Mgr and NE Mgr modes (UI option). 2. Restore archived (golden) EMS database. 3. On the NE Mgr EMS Box 2, select the option to migrate the AP/CAPC nodes to the original EMS

IP Address (Box 1) one-at-time and verify. 4. Once all AP/CAPCs are migrated, take NE Mgr EMS Box 2 offline. 5. Re-bootstrap any original NEs that did not migrate from Box 1.

Appendix M: General Safety Information



Page 163

Appendix M: General Safety Information Remember: Safety depends on you!

The following general safety precautions must be observed during all phases of operation, service, and repair of the system described in this manual. Failure to comply with these precautions or with specific warnings elsewhere in this manual violates safety standards of design, manufacture, and intended use of the system. Motorola, Inc. assumes no liability for the customer’s failure to comply with these requirements. The safety precautions listed below represent warnings of certain dangers of which we are aware. You, as the user of this product, should follow these warnings and all other safety precautions necessary for the safe operation of the system in your operating environment.

Do not substitute parts or modify system

Because of the danger of introducing additional hazards, do not install substitute parts or perform any unauthorized modification of the system. Contact Motorola Warranty and Repair for service and repair to ensure that safety features are maintained.

Non-Disclosure and Assistance Information

Please be advised that the data contained herein is Motorola Internal Use Only and is subject to the terms and conditions of the Non-Disclosure agreement. The distribution of this data should be limited to employees with a need to know. This information shall not be disseminated to any third parties without Motorola’s prior written permission. This data is intended for reference and is not intended to modify the contract.

NOTE: This document is approved for customer distribution. There will be no deviation from this MOP without prior approval from the WiMAX Technical Support Director and Customer Operations Manager. Motorola requires that the customer make no changes or modifications to the WiMAX CGEMS System during the execution of this MOP.




Page 164




Page 165

MOTOROLA and the Stylized M logo are registered in the U.S. Patent and Trademark Office. All other product or service names are the property of their respective owners © Motorola, Inc. 2005.

mopwimaxems001

Carrier EMS Installation MOP

Documents

Transcript of Carrier EMS Installation MOP