Installation and Configuration OMC-R Clean Install

Installation and Configuration: OMC-R
Clean Install
68P02901W47-S
1994 - 2008 Motorola, Inc.
Jul 2008
All Rights Reserved
Accuracy
While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no
liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained
herein. Motorola, Inc. reserves the right to make changes to any products described herein to improve reliability,
function, or design, and reserves the right to revise this document and to make changes from time to time in content
hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liability
arising out of the application or use of any product, software, or circuit described herein; neither does it convey
license under its patent rights or the rights of others. It is possible that this publication may contain references to, or
information about Motorola products (machines and programs), programming, or services that are not announced
in your country. Such references or information must not be construed to mean that Motorola intends to announce
such Motorola products, programming, or services in your country.
Copyrights
This document, Motorola products, and 3rd Party Software products described in this document may include
or describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor
memories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, and
other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right
to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly,
any copyrighted material of Motorola, its licensors, or the 3rd Party software supplied material contained in the
Motorola products described in this document may not be copied, reproduced, reverse engineered, distributed,
merged or modified in any manner without the express written permission of Motorola. Furthermore, the purchase
of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any
license under the copyrights, patents or patent applications of Motorola or other 3rd Party supplied software,
except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a
product.
A list of 3rd Party supplied software copyrights are contained in the Supplemental information section of this
document.
Restrictions
Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part
of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or
translated into any language or computer language, in any form or by any means, without prior written permission
of Motorola, Inc.
License Agreements
The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express
license agreement only and may be used only in accordance with the terms of such an agreement.
High Risk Materials
Components, units, or 3rd Party products used in the product described herein are NOT fault-tolerant and are NOT
designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments
requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication
Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s)
specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities.
Trademarks
Motorola and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service
names are the property of their respective owners.
The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copies
of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can
be obtained from the local Motorola representative or by contacting the Customer Network Resolution Center
(CNRC). The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the
internet, contact the Local Motorola Office.
Jul 2008
Table
of
Contents
Contents
Installation and Configuration: OMC-R Clean Install

Revision history . . . . . . . . . . . .
Version information . . . . . . . .
Resolution of Service Requests . .
Incorporation of CDCNs . . . . . .
General information . . . . . . . . . .
Purpose . . . . . . . . . . . . . .
Cross references . . . . . . . . . .
Text conventions . . . . . . . . . .
Contacting Motorola . . . . . . . . . .
24hour support . . . . . . . . . .
Questions and comments . . . . .
Errors . . . . . . . . . . . . . . .
Security advice. . . . . . . . . . . . .
Warnings, cautions, and notes . . . . .
Warnings. . . . . . . . . . . . . .
Cautions . . . . . . . . . . . . . .
Notes . . . . . . . . . . . . . . .
Safety . . . . . . . . . . . . . . . . .
General safety . . . . . . . . . . .
Electromagnetic energy . . . . . .
Caring for the environment . . . . . .
In EU countries . . . . . . . . . .
In non-EU countries . . . . . . . .
CMM labeling and disclosure table . .
Motorola document set . . . . . . . .
Ordering documents and CD-ROMs
Document banner definitions . . .
Data encryption . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
2
2
3
3
3
4
5
5
5
5
6
7
7
7
7
8
8
8
9
9
9
10
11
11
11
11
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-2
1-2
1-2
1-2
1-2
1-3
1-3
1-3
1-4
1-4
1-4
Chapter 1: Pre-install Requirements

Pre-installation requirements for the OMC-R . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . .
Pre-installation requirements for all processors . . . . . . . . .
Global information requirements - networking . . . . . . . . . .
Global information requirements - time zones . . . . . . . . . .
Global information requirements naming service . . . . . . .
Global information requirements - group and user accounts . . .
Global information requirements OMC-R database initialization
Single Platform Processor requirements . . . . . . . . . . . . . . .
Pre-installation requirements for a Single Platform Processor . .
Single Platform Processor information requirements . . . . . .
68P02901W47-S
Jul 2008
Contents
Single Platform Processor software requirements

GUI server processor requirements . . . . . . . . .
Pre-installation requirements for a GUI server. .
GUI server processor information requirements .
GUI server processor software requirements . .
GUI client requirements . . . . . . . . . . . . . . .
Pre-installation requirements for a GUI client . .
GUI client and server information requirements .
GUI client software requirements . . . . . . . .
DVD Layout . . . . . . . . . . . . . . . . . . .
Sign-off form . . . . . . . . . . . . . . . . . . . . .
Pre-installation requirements sign-off . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-5
1-7
1-7
1-7
1-7
1-9
1-9
1-9
1-9
1-10
1-11
1-11
.
.
.
.
.
.
.
.
.
.
20
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-2
2-3
2-4
2-4
2-14
2-19
2-23
2-26
2-26
2-26
.
.
.
.
.
.
.
.
3-2
3-2
3-2
3-2
3-13
3-13
3-13
3-14
Chapter 2: Operating System and OMC-R Software Installation

on the Single Platform Processor
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the System Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure for the SunFire 4800/4900 . . . . . . . . . . . . . . . . . . . . . . . . . . .
SunFire 4800/4900 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Netra 440 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Netra 20 configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Solaris 10 and OMC Software on SunFire 4800/4900, Netra 440, and Netra 20 . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing the Solaris and OMC Software on the SunFire 4800/4900, Netra 440, and Netra
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuration checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing additional patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking ssh configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Detecting the performance problem . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Moving a machine with a forced link speed . . . . . . . . . . . . . . . . . . . . . . . .
X.25 Configuration - SunFire 4800/4900, Netra 440 and Netra 20 . . . . . . . . . . . . . . .
X.25 configuration procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Format of the X25_config files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
X25_config file entry order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating x25_config file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Running the Configure_X25 script . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying the /etc/hosts file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying the /etc/hosts.equiv file . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating the /.rhosts file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify /etc/dfs/dfstab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional configuration if a Web Access Server is used . . . . . . . . . . . . . . . . . .
Licensing StorEdge Enterprise Backup . . . . . . . . . . . . . . . . . . . . . . . . . .
Back up the Single Platform Processor. . . . . . . . . . . . . . . . . . . . . . . . . . .
Partitioning information for each supported platform . . . . . . . . . . . . . . . . . . .
2-28
2-45
2-45
2-47
2-47
2-48
2-49
2-49
2-49
2-50
2-51
2-52
2-52
2-53
2-54
2-54
2-55
2-55
2-56
2-57
Chapter 3: GUI Server Configuration

GUI server configuration. . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . .
Obtaining the boot prompt . . . . . . . . .
Running Jumpstart . . . . . . . . . . . . .
Performance problem with GUI servers . . . .
Detecting the performance problem . . . .
Moving a machine with a forced link speed
Configuration checks. . . . . . . . . . . . . .
ii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02901W47-S
Jul 2008
Contents
Configuring secure services . . . . . . . . . . . . . .

Additional configuration if a Web Access Server is used
Installing additional patches . . . . . . . . . . . . . .
Flexible GUI server configuration . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . .
Prerequisites for installation . . . . . . . . . . . . . .
Configuring the flexible platform . . . . . . . . . . .
Verify the configuration of the Flexible Platform . . . .
Install the Third Party Packages on the GUI server . .
Configuring secure services . . . . . . . . . . . . . .
Installing additional patches . . . . . . . . . . . . . .
SunRay Server Software Installation. . . . . . . . . . . .
Overview of installation . . . . . . . . . . . . . . . .
Preparation procedure . . . . . . . . . . . . . . . . .
Installing SunRay Server Software. . . . . . . . . . .
Preparing for Configuration of the SunRay Server . . .
Configuring the SunRay Server . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-14
3-14
3-14
3-17
3-17
3-17
3-17
3-21
3-22
3-23
3-23
3-26
3-26
3-27
3-28
3-28
3-28
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
4-2
4-2
4-3
4-3
4-5
4-5
4-6
4-6
4-7
4-8
4-9
4-9
4-9
4-10
4-10
4-10
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-2
5-2
5-2
5-3
5-4
5-4
5-4
5-5
5-5
5-5
5-6
5-6
5-6
5-8
5-11
5-13
5-14
5-16
5-18
Chapter 4: GUI Client Configuration

GUI client installation . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . .
Customized Jumpstart procedures . . . . . . . . . . .
Running Jumpstart . . . . . . . . . . . . . . . . .
SUN Jumpstart procedures . . . . . . . . . . . . . .
Procedure . . . . . . . . . . . . . . . . . . . . .
Performance problem with GUI clients. . . . . . . . .
Detecting the performance problem . . . . . . . .
Fixing the performance problem . . . . . . . . . .
Moving a machine with a modified /etc/system file.
Configuring the GUI client . . . . . . . . . . . . . . .
GUI client files to be modified . . . . . . . . . . .
Setting root password . . . . . . . . . . . . . . .
Modifying the /etc/hosts file . . . . . . . . . . . .
Modifying the /etc/defaultrouter . . . . . . . . . .
Accessing the GUI server . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 5: On-site Requirements and Verification

Introduction to requirements and verification . . . . . . . .
OMC-R equipment requirements. . . . . . . . . . . . .
On-site verification. . . . . . . . . . . . . . . . . . . .
Manufacturer-specific information . . . . . . . . . . . .
Power and environmental requirements . . . . . . . . . . .
Introduction to power and environmental requirements .
Power requirements for specific OMC-R equipment . . .
Temperature . . . . . . . . . . . . . . . . . . . . . . .
Humidity . . . . . . . . . . . . . . . . . . . . . . . . .
Altitude . . . . . . . . . . . . . . . . . . . . . . . . .
Space: weight and dimensional information . . . . . . . . .
Outline of space: weight and dimension information. . .
Single platform processor data Sun Netra 20 . . . . .
Single platform processor data Sun Netra 440 . . . . .
Single platform processor data Sun SunFire 4800/4900
Sun Sunblade 150 . . . . . . . . . . . . . . . . . . . .
Sun Netra 210 . . . . . . . . . . . . . . . . . . . . . .
Cisco 3662 Router . . . . . . . . . . . . . . . . . . . .
Single Platform Processor verification . . . . . . . . . . . .
68P02901W47-S
Jul 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
iii
Contents
Single Platform Processor verification procedures .

Check equipment received . . . . . . . . . . . . .
Before power-up . . . . . . . . . . . . . . . . . .
Checking disk mirrors . . . . . . . . . . . . . . .
Tape drive check procedure . . . . . . . . . . . .
Operating system version verification . . . . . . .
X.25 version verification . . . . . . . . . . . . . .
OMC-R software version verification . . . . . . . .
GUI server/client verification . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . .
Sunblade verification . . . . . . . . . . . . . . .
Netra verification . . . . . . . . . . . . . . . . .
Network verification . . . . . . . . . . . . . . . . . .
Introduction to network verification . . . . . . . .
Verify communication with devices on LAN . . . .
Verify remote login. . . . . . . . . . . . . . . . .
Check users . . . . . . . . . . . . . . . . . . . .
Startup sequences . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . .
Single Platform Processor startup sequence . . . .
GUI Server startup sequence . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
5-18
5-18
5-18
5-19
5-21
5-21
5-22
5-22
5-23
5-23
5-23
5-24
5-25
5-25
5-25
5-25
5-26
5-28
5-28
5-28
5-31
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-2
6-2
6-3
6-3
6-3
6-3
6-4
6-4
6-5
6-6
6-6
6-6
6-7
6-9
6-11
6-11
6-11
6-11
6-12
6-12
6-12
6-13
6-15
6-17
6-17
6-17
6-19
6-19
6-20
6-21
6-22
Chapter 6: System Startup and Shutdown

System Startup and Shutdown . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . .
DTE addressing at node elements . . . . . . . . . . . . .
Addressing requirements . . . . . . . . . . . . . . .
Setting addresses . . . . . . . . . . . . . . . . . . .
Slot: Port settings for OMLs . . . . . . . . . . . . . .
Setting OML addresses . . . . . . . . . . . . . . . .
OMC-R addresses - general rules . . . . . . . . . . .
Setting OMC-R addresses (Single Platform Processor).
Startup and shutdown . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . .
Starting and stopping the OMC-R . . . . . . . . . . .
Starting and stopping the Single Platform Processor .
Starting and stopping the GUI server . . . . . . . . .
Configuration tasks after startup. . . . . . . . . . . . . .
NE node configuration . . . . . . . . . . . . . . . . .
Create subscription lists . . . . . . . . . . . . . . . .
MIB configuration . . . . . . . . . . . . . . . . . . .
OMC-R verification. . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . .
Verification of OMC-R startup and shutdown. . . . . .
X.25 verification . . . . . . . . . . . . . . . . . . . .
Check OMC-R applications. . . . . . . . . . . . . . .
Miscellaneous procedures and reference information . . .
Introduction . . . . . . . . . . . . . . . . . . . . . .
Geographic regions and time zones . . . . . . . . . .
Show disks utility . . . . . . . . . . . . . . . . . . .
Troubleshooting reboot failure . . . . . . . . . . . . .
Essential Jumpstart information . . . . . . . . . . . .
Forwarding OMC-R mail to an exchange server . . . .
Setting up Motorola Backdrop . . . . . . . . . . . . .
iv
68P02901W47-S
Jul 2008
Contents
Chapter 7: Configuring Auxiliary Devices

Configuring auxiliary devices . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting up the Wyse terminal . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure for setting up the Wyse terminal . . . . . . . . . . . . .
Adding a printer . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Assigning printer name and address on the network. . . . . . . . .
Configuring a printer connected to a GUI processor . . . . . . . . .
Checking the printer status . . . . . . . . . . . . . . . . . . . . .
Printing a file . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Printer configuration file . . . . . . . . . . . . . . . . . . . . . . .
Installing a modem. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Background information . . . . . . . . . . . . . . . . . . . . . . .
Data links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Physical connection . . . . . . . . . . . . . . . . . . . . . . . . .
Initial SPARCstation setup . . . . . . . . . . . . . . . . . . . . . .
Communicating with the modem . . . . . . . . . . . . . . . . . . .
Configuring tip. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Controlling modem access . . . . . . . . . . . . . . . . . . . . . .
Modem setup and Initialization . . . . . . . . . . . . . . . . . . .
Configuring the MultiModem MT5634ZBA Global . . . . . . . . . .
Enabling the login process . . . . . . . . . . . . . . . . . . . . . .
Remote connection and file transfers . . . . . . . . . . . . . . . .
Troubleshooting the modem . . . . . . . . . . . . . . . . . . . . . . .
Problem symptoms. . . . . . . . . . . . . . . . . . . . . . . . . .
All ports busy . . . . . . . . . . . . . . . . . . . . . . . . . . . .
No login prompt . . . . . . . . . . . . . . . . . . . . . . . . . . .
When to modify the EEPROM settings . . . . . . . . . . . . . . . .
Corruption from SPARCstation with remote system logging in . . . .
Modem hangs up after answering a call and negotiation. . . . . . .
Permission denied or link down . . . . . . . . . . . . . . . . . . .
Modems do not disconnect properly . . . . . . . . . . . . . . . . .
Nothing happens when trying to tip the modem . . . . . . . . . . .
When dialing into the SPARC the modem never picks up the phone .
Login message is corrupt . . . . . . . . . . . . . . . . . . . . . .
Cannot login: password fails . . . . . . . . . . . . . . . . . . . . .
Configuration and installation of a remote monitoring terminal . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Single OMC-R monitoring configuration . . . . . . . . . . . . . . .
OMC-R night concentration center configuration . . . . . . . . . .
Night concentration overview . . . . . . . . . . . . . . . . . . . .
Naming conventions . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote Single Platform Processor setup. . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating host file entries . . . . . . . . . . . . . . . . . . . . . .
Exporting file changes . . . . . . . . . . . . . . . . . . . . . . . .
Creation of a new account . . . . . . . . . . . . . . . . . . . . . .
Monitoring an alternative OMC-R from a GUI server . . . . . . . . . .
Prerequisites for switching to alternative Single Platform Processor
Switching to an alternative Single Platform Processor . . . . . . . .
68P02901W47-S
Jul 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
7-2
7-2
7-3
7-3
7-3
7-5
7-5
7-5
7-5
7-6
7-6
7-6
7-8
7-8
7-8
7-9
7-9
7-10
7-10
7-12
7-12
7-13
7-13
7-16
7-17
7-18
7-19
7-19
7-19
7-21
7-22
7-22
7-22
7-22
7-22
7-23
7-23
7-23
7-23
7-24
7-24
7-24
7-25
7-27
7-27
7-27
7-29
7-29
7-29
7-29
7-30
7-31
7-31
7-32
Contents
Chapter 8: Cisco 3662 Installation

Cisco 3662 router . . . . . . . . . . . . . . . . . . . . . . . . . . .
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Four Port Serial Interface . . . . . . . . . . . . . . . . . . . . .
Two port channelized E1 interface . . . . . . . . . . . . . . . . .
Router capacity . . . . . . . . . . . . . . . . . . . . . . . . . .
Cables used . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connectivity, configuration, and LAN connection . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Establishing console connection . . . . . . . . . . . . . . . . . .
Initial configuration . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the hostname and passwords . . . . . . . . . . . . .
Connecting and configuring the LAN connection . . . . . . . . .
Establishing OMC and GSM connections. . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring X.25 profiles . . . . . . . . . . . . . . . . . . . . .
Establishing serial connections to the OMC . . . . . . . . . . . .
Connecting the router to the OMC . . . . . . . . . . . . . . . . .
Configuring the serial interfaces to the OMC . . . . . . . . . . .
Establishing and configuring connections to the GSM equipment .
Controllers and channel groups . . . . . . . . . . . . . . . . . .
Creating channel groups . . . . . . . . . . . . . . . . . . . . . .
Configuring the serial interfaces (to the GSM Network Elements) .
Enabling X.25 routing and creating Hunt Groups . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling X.25 routing . . . . . . . . . . . . . . . . . . . . . . .
Creating X.25 Hunt Groups . . . . . . . . . . . . . . . . . . . .
Creating the BOOTLOAD Hunt Group . . . . . . . . . . . . . . .
Creating the EVENTS Hunt Group . . . . . . . . . . . . . . . . .
Verifying the X.25 Hunt Groups . . . . . . . . . . . . . . . . . .
Creating X.25 routes . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .
X.121 addresses . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding routes into the routing table . . . . . . . . . . . . . . . .
Creating routes to the OMC . . . . . . . . . . . . . . . . . . . .
Creating routes to the GSM equipment . . . . . . . . . . . . . .
Saving the Configuration. . . . . . . . . . . . . . . . . . . . . .
Verifying the routes . . . . . . . . . . . . . . . . . . . . . . . .
Useful Cisco commands . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Useful Cisco operating system commands . . . . . . . . . . . . .
Making changes to the Cisco configuration . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
8-2
8-2
8-2
8-3
8-3
8-4
8-4
8-5
8-5
8-7
8-7
8-7
8-7
8-9
8-11
8-13
8-15
8-15
8-15
8-16
8-18
8-19
8-21
8-22
8-24
8-26
8-28
8-28
8-28
8-28
8-29
8-30
8-30
8-32
8-32
8-32
8-33
8-33
8-34
8-34
8-34
8-35
8-35
8-35
8-38
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9-2
9-2
9-2
9-3
9-3
9-3
9-4
9-5

Cisco 3845 router . . . . . . . . . . . .
Background . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . .
Introduction to the Cisco 3845 router
Router . . . . . . . . . . . . . . . .
Four Port Serial Interface . . . . . .
Two port channelized E1 interface . .
Router capacity . . . . . . . . . . .
vi
. . . . . .
. . . . . .
. . . . . .
hardware .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02901W47-S
Jul 2008
Contents
Cables used . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cables previously used. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Connectivity, configuration, and LAN connection . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Prerequisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Establishing console connection . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Initial configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the hostname and passwords . . . . . . . . . . . . . . . . . . . . . . .
Connecting and configuring the LAN connection . . . . . . . . . . . . . . . . . . .
Establishing OMC and GSM connections. . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring X.25 profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Establishing serial connections to the OMC . . . . . . . . . . . . . . . . . . . . . .
Connecting the router to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the serial interfaces to the OMC . . . . . . . . . . . . . . . . . . . . .
Establishing and configuring connections to the GSM equipment . . . . . . . . . . .
Controllers and channel groups . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating channel groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring the serial interfaces (to the GSM Network Elements) . . . . . . . . . . .
Enabling X.25 routing and creating Hunt Groups . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling X.25 routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating X.25 Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating the BOOTLOAD Hunt Group . . . . . . . . . . . . . . . . . . . . . . . . .
Creating the EVENTS Hunt Group . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying the X.25 Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating X.25 routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
X.121 addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding routes into the routing table . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating routes to the OMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating routes to the GSM equipment . . . . . . . . . . . . . . . . . . . . . . . .
Remaining routes to be created . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Saving the Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verifying the routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Integration with the existing Cisco 3662/3845 router . . . . . . . . . . . . . . . . . . .
Creating an X.25 profile for the serial interfaces that connect to the CISCO 3662/3845
Configuring the necessary serial interfaces to use these CISCO profiles . . . . . . . .
Enabling X.25 routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Integration with a Cisco 3662/3845 router using X.25 over IP . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating X.25 routes between the routers . . . . . . . . . . . . . . . . . . . . . . .
Useful Cisco commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Useful Cisco operating system commands . . . . . . . . . . . . . . . . . . . . . . .
Making changes to the Cisco configuration . . . . . . . . . . . . . . . . . . . . . .
Trouble-shooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9-5
9-6
9-7
9-7
9-7
9-7
9-10
9-11
9-13
9-15
9-15
9-15
9-16
9-18
9-19
9-21
9-22
9-23
9-26
9-28
9-28
9-28
9-28
9-29
9-30
9-30
9-32
9-32
9-32
9-33
9-33
9-34
9-34
9-34
9-35
9-36
9-36
9-36
9-38
9-39
9-39
9-40
9-41
9-41
9-41
9-44
9-44
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
10-2
10-2
10-2
10-3
10-3
10-4
10-4
10-4
Chapter 10: SunFire 4800/4900 Troubleshooting

SunFire 4800/4900 Troubleshooting .
Resetting a Hung domain . . . .
Freeing the console connection .
Rebooting the system controller .
Setting domain password . . . .
Setting Platform Password . . . .
Change system into failover mode
Resetting a Platform Password. .
68P02901W47-S
Jul 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
vii
Contents
Resetting a domain password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii
10-5
68P02901W47-S
Jul 2008
List
of
Figures
List of Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
1-1: High level layout of the jumpstart DVD . . . . . . . . . . . . . . . . . .

2-1: OMC-R network configuration . . . . . . . . . . . . . . . . . . . . . . .
2-2: StorEdge 3310 Disk Array . . . . . . . . . . . . . . . . . . . . . . . . .
2-3: D240 Media Tray . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-4: SunFire 4800/4900 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-5: SunFire 4800/4900 with Dual SCSI . . . . . . . . . . . . . . . . . . . .
2-6: Hard Disk layout for 3310 disk array connected to the SunFire 4800/4900
2-7: Back panel of Netra 440 ac Version . . . . . . . . . . . . . . . . . . . .
2-8: Fully cabled Netra 440 . . . . . . . . . . . . . . . . . . . . . . . . . .
2-9: Front end internal view of Netra 440 . . . . . . . . . . . . . . . . . . .
2-10: Hard Disk Layout for 3310 disk array connected to the Netra 440 . . . .
2-11: Netra 20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-12: StorEdge 3310 Array . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-13: Netra 20 open front-end view . . . . . . . . . . . . . . . . . . . . . .
2-14: Hard Disk Layout for 3310 disk array connected to the Netra 20 . . . .
3-1: Connecting optional SunRay DTU to Netra210 using a direct connection .
3-2: Connecting optional SunRay DTU to Netra210 using a VLAN . . . . . . .
4-1: GUI client Graphical CDE login screen . . . . . . . . . . . . . . . . . .
4-2: GUI server Graphical CDE login screen . . . . . . . . . . . . . . . . . .
5-1: Front view of Sun Netra 20 . . . . . . . . . . . . . . . . . . . . . . . .
5-2: Sun Netra 20 dimensions . . . . . . . . . . . . . . . . . . . . . . . . .
5-3: Front view of Sun Netra 440. . . . . . . . . . . . . . . . . . . . . . . .
5-4: Sun Netra 440 dimensions. . . . . . . . . . . . . . . . . . . . . . . . .
5-5: Front view of Sun SunFire 4800/4900 . . . . . . . . . . . . . . . . . . .
5-6: Sun SunFire 4800/4900 dimensions . . . . . . . . . . . . . . . . . . . .
5-7: Front view of a Sunblade 150 . . . . . . . . . . . . . . . . . . . . . . .
5-8: Sunblade 150 dimensions . . . . . . . . . . . . . . . . . . . . . . . . .
5-9: Front view of a Netra 210 . . . . . . . . . . . . . . . . . . . . . . . . .
5-10: Netra 210 dimensions . . . . . . . . . . . . . . . . . . . . . . . . . .
5-11: Cisco 3662 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-12: Cisco 3662 Router dimensions . . . . . . . . . . . . . . . . . . . . . .
6-1: Single Platform Processor startup and shutdown . . . . . . . . . . . . .
6-2: GUI Server startup and shutdown . . . . . . . . . . . . . . . . . . . . .
6-3: Packet switch main menu . . . . . . . . . . . . . . . . . . . . . . . . .
6-4: OMC-R GUI front panel . . . . . . . . . . . . . . . . . . . . . . . . . .
7-1: Motorola 3460 FastR modem . . . . . . . . . . . . . . . . . . . . . . .
7-2: Single monitoring station configuration . . . . . . . . . . . . . . . . . .
7-3: Night concentration center configuration (Sunblade 150 high-end server)
8-1: 3662 router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-2: Four Port Serial Interface module to connect to the OMC . . . . . . . . .
8-3: Two port channelized E1 interface to connect GSM network elements . .
8-4: Connect To dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-5: COM Properties dialog box . . . . . . . . . . . . . . . . . . . . . . . .
9-1: 3845 router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-2: Four Port Serial Interface module to connect to the OMC . . . . . . . . .
68P02901W47-S
Jul 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-10
2-3
2-14
2-14
2-15
2-16
2-17
2-19
2-20
2-21
2-22
2-23
2-23
2-24
2-25
3-26
3-27
4-11
4-11
5-7
5-8
5-9
5-10
5-11
5-12
5-13
5-14
5-14
5-15
5-16
5-17
6-8
6-10
6-15
6-16
7-9
7-24
7-26
8-3
8-4
8-4
8-8
8-9
9-3
9-4
ix
List of Figures
Figure
Figure
Figure
Figure
Figure
9-3:
9-4:
9-5:
9-6:
9-7:
Two port channelized E1 interface . . . . . . .

Connect To dialog box . . . . . . . . . . . . . .
COM Properties dialog box . . . . . . . . . . .
Cisco 3845 connected to an existing Cisco 3845
Router interconnect using X25 over IP (ethernet)
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9-4
9-8
9-9
9-37
9-39
68P02901W47-S
Jul 2008
List
of
Tables
List of Tables
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
Table
1: Version information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2: Resolution of Service Requests . . . . . . . . . . . . . . . . . . . . . . . .
3: Incorporation of CDCNs . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1: Global information requirements: networking . . . . . . . . . . . . . . .
1-2: Global information requirements: time zones . . . . . . . . . . . . . . . .
1-3: Global information requirements: group names and ids . . . . . . . . . .
1-4: Global information requirements: User Ids . . . . . . . . . . . . . . . . .
1-5: Global information requirements: OMC-R database initialization . . . . . .
1-6: Single Platform Processor information requirements . . . . . . . . . . . .
1-7: Single Platform Processor Host ID . . . . . . . . . . . . . . . . . . . . .
1-8: Single Platform Processor information requirements Software Installation
1-9: Software requirements - Single Platform Processor. . . . . . . . . . . . .
1-10: GUI server processor information requirements . . . . . . . . . . . . . .
1-11: GUI server processor software requirements . . . . . . . . . . . . . . .
1-12: Software requirements for a GUI server processor . . . . . . . . . . . .
1-13: GUI client hostname and Internet address. . . . . . . . . . . . . . . . .
1-14: Software requirements for a GUI client other than Sunblade 150 . . . . .
1-15: Software requirements for Sunblade 150 GUI client. . . . . . . . . . . .
1-16: Pre-installation requirements sign-off form . . . . . . . . . . . . . . . .
2-1: Disk allotments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-2: Disk allotment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-3: Disk allotment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2-4: Prerequisites for Solaris installation . . . . . . . . . . . . . . . . . . . .
2-5: Fields in the x25_config file . . . . . . . . . . . . . . . . . . . . . . . . .
2-6: Entry order in the x25_config file . . . . . . . . . . . . . . . . . . . . . .
2-7: Partitioning information for SF/Netra 20 . . . . . . . . . . . . . . . . . .
2-8: Partitioning information for Netra 440 . . . . . . . . . . . . . . . . . . .
3-1: File system configuration . . . . . . . . . . . . . . . . . . . . . . . . . .
5-1: Power requirements for OMC-R equipment . . . . . . . . . . . . . . . . .
6-1: Slots: Port settings for 2 Mbps OMLs . . . . . . . . . . . . . . . . . . . .
6-2: OMC-R front panel description . . . . . . . . . . . . . . . . . . . . . . .
6-3: Geographic regions and their time zones . . . . . . . . . . . . . . . . . .
6-4: Supported configurations . . . . . . . . . . . . . . . . . . . . . . . . . .
7-1: Wyse terminal setup submenus . . . . . . . . . . . . . . . . . . . . . . .
7-2: Modem initialization commands . . . . . . . . . . . . . . . . . . . . . .
7-3: Syntax of the AT command . . . . . . . . . . . . . . . . . . . . . . . . .
7-4: MultiModem MT5634ZBA initialization AT commands . . . . . . . . . . .
7-5: Hostname and IP addresses for different processors . . . . . . . . . . . .
7-6: User name and ID for remote system . . . . . . . . . . . . . . . . . . . .
8-1: Recommended slot usage on the Cisco 3662 . . . . . . . . . . . . . . . .
8-2: Fields in the x25_config file . . . . . . . . . . . . . . . . . . . . . . . . .
8-3: Sample X25_config file for an OMC . . . . . . . . . . . . . . . . . . . . .
8-4: Physical Port connections at the OMC and Cisco 3662 . . . . . . . . . . .
8-5: DB-15 to RJ45 120 Ohm cable pinouts . . . . . . . . . . . . . . . . . . .
8-6: Sequence of steps to create serial interfaces . . . . . . . . . . . . . . . .
68P02901W47-S
Jul 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
2
1-2
1-2
1-3
1-3
1-3
1-4
1-4
1-5
1-6
1-7
1-7
1-7
1-9
1-9
1-9
1-11
2-18
2-22
2-25
2-26
2-49
2-50
2-57
2-59
3-17
5-4
6-3
6-16
6-17
6-21
7-3
7-14
7-14
7-17
7-28
7-28
8-5
8-16
8-17
8-19
8-22
8-23
xi
List of Tables
Table
Table
Table
Table
Table
xii
9-1:
9-2:
9-3:
9-4:
9-5:
Recommended slot usage on the Cisco 3845 . .

Fields in the x25_config file . . . . . . . . . . .
Sample X25_config file for an OMC . . . . . . .
Physical Port connections at the OMC and Cisco
Sequence of steps to create serial interfaces . .
. . .
. . .
. . .
3845
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9-5
9-16
9-17
9-18
9-23
68P02901W47-S
Jul 2008
About
This
Manual
Installation and Configuration: OMC-R Clean

Install
What is covered in this manual?

This manual contains information about the GSM OMC-R Clean Install. This manual provides:
A set of procedures used during the OMC-R internal staging process. Staging consists of
the preparation of the hardware platform, interconnection of the processors and printer
through an Ethernet LAN, and loading and configuration of the OMC-R system software.
A set of procedures for installing and commissioning an OMC-R at a customer site.
68P02901W47-S
Jul 2008
Revision history
Revision history
The following sections show the revision status of this document.
Version information
The following lists the versions of this manual in order of manual issue:
Table 1
Version information
Issue
Date of issue
Remarks
Sep 2004
Issue Q - GSM Software Release 7 Half Rate
Nov 2006
Issue R - GSM Software Release 8 (GMR-02)
Jul 2008
Issue S - GSM Software Release 9
Resolution of Service Requests

The following Service Requests are now resolved in this manual:
Table 2
Resolution of Service Requests
Service Request
GMR
Number
2221969
Remarks
SR 2221969 is resolved.
Incorporation of CDCNs
The following CDCNs are now incorporated in this manual:
Table 3
Incorporation of CDCNs
CDCN
GMR Number
N/A
N/A
Remarks
68P02901W47-S
Jul 2008
General information
General information
Purpose
Motorola documents are intended to instruct and assist personnel in the operation, installation,
and maintenance of the Motorola equipment and ancillary devices. It is recommended that all
personnel engaged in such activities be properly trained by Motorola.
Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss or
reduction in system performance arising directly or indirectly out of the failure of the customer,
or anyone acting on the customer's behalf, to abide by the instructions, system parameters,
or recommendations made in this document.
These documents are not intended to replace the system and equipment training offered by
Motorola. They can be used to supplement and enhance the knowledge gained through such
training.
NOTE
If this document was obtained when attending a Motorola training course, it is not
updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it
was supplied under normal operational circumstances, to support a major software
release, then Motorola automatically supplies corrections and posts on the Motorola
customer website.
Cross references
References made to external publications are shown in italics. Other cross references,
emphasized in blue text in electronic versions, are active links to the references.
This document is divided into numbered chapters that are divided into sections. Sections are
not numbered, but are individually named at the top of each page, and are listed in the table of
contents.
68P02901W47-S
Jul 2008
Text conventions
Text conventions
The following conventions are used in the Motorola documents to represent keyboard input
text, screen output text, and special key sequences.
Input
Characters typed in at the keyboard are shown like this sentence.
Items of interest within a command appear like this sentence.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this sentence.
Items of interest within a screen display appear like this sentence.
Special key sequences

Special key sequences are represented as follows:
CTRL-c or CTRL+C
Press the Ctrl and C keys at the same time.
CTRL-SHIFT-c or
CTRL+SHIFT+C
Press the Ctrl, Shift, and C keys at the same time.
ALT-f or ALT+F
Press the Alt and F keys at the same time.
ALT+SHIFT+F11
Press the Alt, Shift and F11 keys at the same time.
Press the pipe symbol key.
RETURN or ENTER
Press the Return or Enter key.
68P02901W47-S
Jul 2008
Contacting Motorola
Contacting Motorola
Motorola appreciates feedback from the users of our documents.
24hour support
If you have problems regarding the operation of your equipment, contact the Customer Network
Resolution Center (CNRC) for immediate assistance. The 24hour telephone numbers are listed
at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center
contact information. Alternatively if you do not have access to CNRC or the internet, contact
the Local Motorola Office.
Questions and comments

Send questions and comments regarding user documentation to the email address:
mydocs@motorola.com.
Errors
To report a documentation error, call the CNRC (Customer Network Resolution Center) and
provide the following information to enable CNRC to open an SR (Service Request):
The document type
The document title, part number, and revision character
The page number with the error
A detailed description of the error and if possible the proposed solution
68P02901W47-S
Jul 2008
Security advice
Security advice
Motorola systems and equipment provide security parameters that the operator configures
based on their particular operating environment. Motorola recommends setting and using
these parameters following industry recognized security practices. Consider protecting the
confidentiality, integrity, and availability of information and assets. Assets include the ability
to communicate, information about the nature of the communications, and information about
the parties involved.
In certain instances, Motorola makes specific recommendations regarding security practices.
The implementation of these recommendations and final responsibility for the security of the
system lies with the operator of the system.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information, from the menu located to the left of the
Login box. Alternatively if you do not have access to CNRC or the internet, contact the Local
Motorola Office.
68P02901W47-S
Jul 2008
Warnings, cautions, and notes
Warnings, cautions, and notes
The following describes how warnings and cautions are used in this document and in all
documents of this Motorola document set.
Warnings
Warnings precede instructions that contain potentially hazardous situations. Warnings are
used to alert the reader to possible hazards that could cause loss of life or physical injury. A
warning has the following format:
WARNING
Warning text and consequence for not following the instructions in the warning.
Cautions
Cautions precede instructions and are used when there is a possibility of damage to systems,
software, or individual items of equipment within a system. However, this damage presents
no danger to personnel. A caution has the following format:
CAUTION
Caution text and consequence for not following the instructions in the caution.
Notes
A note means that there is a possibility of an undesirable situation or provides additional
information to help the reader understand a topic or concept. A note has the following format:
NOTE
Note text.
68P02901W47-S
Jul 2008
Safety
Safety
General safety
The following general safety guidelines apply to Motorola equipment:
The power jack and mating plug of the power cable must meet International
Electrotechnical Commission (IEC) safety standards.
NOTE
Refer to Grounding Guideline for Cellular Radio Installations 68P81150E62.
Power down or unplug the equipment before servicing.
Using non-Motorola parts for repair could damage the equipment or void warranty.
Contact Motorola Warranty and Repair for service and repair instructions.
Portions of Motorola equipment may be damaged from exposure to electrostatic discharge.

Use precautions to prevent damage.
Electromagnetic energy
Relevant standards (USA and EC) applicable when working with RF equipment are:
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure
to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
Council recommendation of 12 July 1999 on the limitation of exposure of the general

public to electromagnetic fields (0 Hz to 300 GHz) (1999/519/EC) and respective national
regulations.
Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 on
the minimum health and safety requirements regarding the exposure of workers to the
risks arising from physical agents (electromagnetic fields) (18th individual Directive within
the meaning of Article 16(1) of Directive 89/391/EEC).
68P02901W47-S
Jul 2008
Caring for the environment
Caring for the environment
The following information describes national or regional requirements for the disposal of
Motorola supplied equipment and for the approved disposal of surplus packaging.
Contact the Customer Network Resolution Center (CNRC) for assistance. The 24hour
telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer
Network Resolution Center contact information. Alternatively if you do not have access
to CNRC or the internet, contact the Local Motorola Office.
In EU countries
The following information is provided to enable regulatory compliance with the European
Union (EU) directives and any amendments to these directives when using Motorola equipment
in EU countries.
Disposal of Motorola equipment

European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE)
Do not dispose of Motorola equipment in landfill sites. In the EU, Motorola in conjunction
with a recycling partner ensures that equipment is collected and recycled according to the
requirements of EU environmental law.
Disposal of surplus packaging

European Parliament and Council Directive 94/62/EC Packaging and Packaging Waste
Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipients
responsibility to ensure that packaging materials are collected and recycled according to the
requirements of EU environmental law.
In non-EU countries
In non-EU countries, dispose of Motorola equipment and all surplus packaging in accordance
with national and regional regulations.
68P02901W47-S
Jul 2008
CMM labeling and disclosure table
CMM labeling and disclosure table
The Peoples Republic of China requires that our products comply with China Management
Methods (CMM) environmental regulations. (China Management Methods refers to the
regulation Management Methods for Controlling Pollution by Electronic Information Products.)
Two items are used to demonstrate compliance; the label and the disclosure table.
The label is placed in a customer visible position on the product.
Logo 1 means the product contains no substances in excess of the maximum concentration
value for materials identified in the China Management Methods regulation.
Logo 2 means that the product may contain substances in excess of the maximum
concentration value for materials identified in the China Management Methods regulation,
and has an Environmental Friendly Use Period (EFUP) in years. The example shown
uses 50 years.
Logo 1
Logo 2
The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic
and Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP)
will not leak or mutate causing environmental pollution or bodily injury from the use of the
EIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain
field-replaceable parts, such as battery modules, can have a different EFUP and are marked
separately.
The Disclosure table is intended only to communicate compliance with China requirements.
It is not intended to communicate compliance with EU RoHS or any other environmental
requirements.
10
68P02901W47-S
Jul 2008
Motorola document set
Motorola document set
The Motorola document sets provide the information to operate, install, and maintain the
Motorola equipment.
Ordering documents and CD-ROMs

With internet access available, to view, download, or order documents (original or revised), visit
the Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com, or
contact your Motorola account representative.
Without internet access available, order hard-copy documents or CD-ROMs from your Motorola
Local Office or Representative.
If Motorola changes the content of a document after the original printing date, Motorola
publishes a new version with the same part number but a different revision character.
Document banner definitions

A banner indicates that some information contained in the document is not yet approved for
general customer use. A banner is oversized text on the bottom of the page, for example,
PRELIMINARY UNDER DEVELOPMENT.
Data encryption
In order to avoid electronic eavesdropping, data passing between certain elements in the
network is encrypted. In order to comply with the export and import requirements of particular
countries, this encryption occurs at different levels. The encryption may be individually
standardized or may not be present at all in some parts of the network in which it is normally
implemented. The document set covers encryption as if fully implemented. Limitations on the
encryption included in the particular software being delivered, are covered in the Release Notes
that accompany the individual software release.
68P02901W47-S
Jul 2008
11
Data encryption
12
68P02901W47-S
Jul 2008
Chapter
1
Pre-install Requirements
68P02901W47-S
Jul 2008
1-1
Pre-installation requirements for the OMC-R
Introduction
This chapter contains specific information required during installation of OMC-R. The
pre-installation requirements and essential information relating to the installation of all
processors are described.
NOTE
This chapter specifies data required during the installation process. Take a photocopy
and complete all the blank tables in this chapter before beginning the installation
procedures. Keep the copy as a record of the OMC-R setup.
Pre-installation requirements for all processors

The remainder of this section contains data that is required during the installation of all
processors (Single Platform, GUI server, and GUI client). Ensure that all the blank tables are
completed before beginning the installation procedure.
Global information requirements - networking

In Table 1-1, enter the network number, netmask address, and broadcast address.
Table 1-1
Global information requirements: networking
Network number
Netmask address
Broadcast address
Global information requirements - time zones

In Table 1-2, enter the geographic region and time zone of the network.
Table 1-2
Global information requirements: time zones
Geographic region
1-2
Time zone
68P02901W47-S
Jul 2008
Global information requirements naming service
Global information requirements naming service

NIS must be retained as the naming service of choice where an NHA processor is attached
to the OMC-R LAN.
Global information requirements - group and user accounts

In Table 1-3 and Table 1-4, enter user group names and ids. For example: omcread, omc, and
informix must be the same on all processors.
Table 1-3
Global information requirements: group names and ids
Group name
Table 1-4
User login
Group ID
Global information requirements: User Ids

User full
name
root
omcadmin
User ID
User group
ID
User home
directory
/
/home/omcadmin
Shell type
Password
csh
informix
/usr/informix
csh
omcread
/home/omcread
csh
Global information requirements OMC-R database

initialization
In Table 1-5, enter the country code and network code.
Table 1-5
Global information requirements: OMC-R database initialization
Country code
68P02901W47-S
Network code
1-3
Jul 2008
Single Platform Processor requirements
Single Platform Processor requirements
Pre-installation requirements for a Single Platform Processor

This section contains data required during the installation of a Single Platform Processor.
Ensure that all the blank boxes are completed before beginning the installation procedure.
Single Platform Processor information requirements

In Table 1-6, enter the host name and Internet address, as mentioned in the /etc/hosts file.
Table 1-6
Single Platform Processor information requirements
Host name
Aliases: omc_splat
Internet address
omc_pm
omc_4gl
In Table 1-7, enter the Host ID. The ID is required to license the Sunlink X.25.
Table 1-7
Single Platform Processor Host ID
Host ID
In Table 1-8, enter the single platform processor information for software installation.
1-4
68P02901W47-S
Jul 2008
Table 1-8
Single Platform Processor information requirements Software Installation

Check
OMC-R Software
DVD-ROM
Country Code
Network Code
System Printer
Hostname
IP Address
Datagen Host Name

Datagen Country Name
RTF Encryption Key
RTF Ceiling Limit
RTF NE Limit
RTF License Issue Date
RTF Checksum
Link speed if 254 NEs
being used
X25 Vendor String
X25 License Password

Ensure that the software and media listed in Table 1-9 are supplied and the version numbers
are correct. Enter the license numbers where appropriate.
68P02901W47-S
1-5
Jul 2008
Table 1-9
Software requirements - Single Platform Processor

Revision Version
Media
Number of
Volumes
GSR9 OMCR 1.9.0.0.x

including
OMC Software
and Jumpstart
1900.x
DVD
GSR9 OMCR 1.9.0.0.x

Addiitional
OMC software
1900.x
DVD
Title
Sun Solaris
Solaris Logical Volume
Manager
Sun SunLink X25
License Number
10
11.9
9.2
Sun SunLink HSI/S

Sun CDE
TCL
8.4.6
Freeware
TK
8.4.6
Freeware
Enscript
1.6.1
Freeware
Perl
5.61
Freeware
INFORMIX-IDS
INFORMIX-Client SDK
(UC3)
2.81
INFORMIX-ISQL (UC1)
7.32
OSP
1-6
10.00.UC8
5.3
Applix Spreadsheet
Applix Data
Mozilla
1.7
Freeware
Python
2.2.3
Freeware
StorEdge Enterprise
Backup
7.3
Sun VTS
6.2
68P02901W47-S
Jul 2008
GUI server processor requirements
GUI server processor requirements
Pre-installation requirements for a GUI server

This section contains the data required during the installation of a GUI server processor. Ensure
that all the blank boxes are completed before starting the installation procedure.
GUI server processor information requirements

In Table 1-10, enter the host name and Internet address of the GUI server processor.
Table 1-10
GUI server processor information requirements
Host name
Internet address
In Table 1-11, enter the Host ID. The ID is required to license the solstice backup.
Table 1-11
GUI server processor software requirements
Host id

Ensure that the software and media listed in Table 1-12 are supplied and the version numbers
are correct. Enter the license numbers and key where appropriate.
Table 1-12
Software requirements for a GUI server processor

Revision Version
Media
Number of
volumes
GSR9 OMCR
1.9.0.0.x
including OMC
Software and
Jumpstart
1900.x
DVD
GSR9 OMCR
1.9.0.0.x
Addiitional
OMC software
1900.x
DVD
Title
License Number
Continued
68P02901W47-S
1-7
Jul 2008
Table 1-12
Software requirements for a GUI server processor (Continued)
Title
Sun Solaris
Revision Version
Media
10
DVD Pack *
Number of
volumes
License Number
Sun CDE
INFORMIX Client
SDK
OSP
2.8.1
5.3
Applix Spreadsheet
Applix Data
Mozilla
1.7
Freeware
Sun Answerbook
StorEdge Enterprise
Backup
7.3
* For minimum specified GUI server.
1-8
68P02901W47-S
Jul 2008
GUI client requirements
GUI client requirements
Pre-installation requirements for a GUI client

This section contains data that is required during the installation of a GUI client. Ensure that all
the blank boxes are completed before beginning the installation procedure.
GUI client and server information requirements

In Table 1-13, enter the hostnames, internet addresses of the GUI clients and the servers to
which they are connected.
Table 1-13
GUI client hostname and Internet address
Client hostname
Server name
Client Internet address
GUI client software requirements

Ensure that the software and media listed in Table 1-14, or Table 1-15 have been supplied and
the version numbers are correct. Enter the license numbers and key where appropriate.
Table 1-14
Software requirements for a GUI client other than Sunblade 150
Title
Revision Version
Media
Number of
volumes
Sun Solaris
10
CD Pack
Sun Patches
Latest available
Table 1-15
Software requirements for Sunblade 150 GUI client
Title
Revision Version
Media
Number of
volumes
GSR9 OMCR
1.9.0.0.x
including OMC
Software and
Jumpstart
1900.x
DVD
Sun Solaris
10
Sun CDE
1.2
68P02901W47-S
License Number
License Number
1-9
Jul 2008
DVD Layout
DVD Layout
The following diagram shows the high-level layout of the Jumpstart DVD.
Figure 1-1
High level layout of the jumpstart DVD
/cdrom/c drom()
s0
s1
s2
s 3
s4
s 5
suninstall
Documentation flash
preinstall_platform
Flexible
lib
prep_install
Freeware
platform_files
prompt
Misc
postinstall
rules
Packages
postinstall_platform
rules.ok
patches
postinstall_platform.GUI
scripts
bin
postinstall_platform.GUI_Client
smf
check_dvd
postinstall_restore
up grade
data
preinstall
ti-gsm_High_level_layout_of_the_jumpstart_DVD-0080-ai-sw
The key directories are:

Packages - Contains the software and third-party software installed during clean install.
Patches contains any operating system patches required on the system.
data contains system configuration files which drive the clean install.
upgrade contains scripts and configuration files which drive the system upgrade.
1-10
68P02901W47-S
Jul 2008
Sign-off form
Sign-off form
Pre-installation requirements sign-off

Complete the pre-installation requirements sign-off form in Table 1-16, after checking the
pre-installation requirements.
Table 1-16
Pre-installation requirements sign-off form
Print name
68P02901W47-S
Jul 2008
Signature
Date
1-11
Pre-installation requirements sign-off
1-12
68P02901W47-S
Jul 2008
Chapter
2
Operating System and OMC-R Software
Installation on the Single Platform Processor
68P02901W47-S
Jul 2008
2-1
Introduction
Chapter 2: Operating System and OMC-R Software Installation on the Single Platform Processor
Introduction
This chapter deals with the hardware configuration and software installation of OMC-R
Single Platform Processors. Therefore, it contains only hardware configuration and software
installation information for the Sunfire 4800/4900, Netra 440, Netra 20 equipment. The
suggested order of hardware and software installation follows the sections in this chapter.
A typical hardware configuration for a complete 1.9.x.x OMC-R network is shown in Figure 2-1.
CAUTION
2-2
Ensure that the equipment mains voltage settings are adjusted to suit the local
mains supply.
Always wear an earth strap connected to the Electro-Static Point (ESP) on the
equipment.
Take care when removing components connected to static-sensitive devices.

These components may be providing protection to the device.
When mounted onto Printed Circuit Boards (PCBs), MOS devices are normally
less susceptible to electrostatic damage. However, handle the PCBs with care,
preferably by their edges and not by their tracks and pins. Transfer them
directly from their packing to the equipment and never expose the PCBs on
the workbench.
68P02901W47-S
Jul 2008
Network configuration
Network configuration
An OMC-R network configuration for a complete system is illustrated in Figure 2-1.
Figure 2-1
OMC-R network configuration
P RINTER
GUI Serv er
GUI Serv er
SunFire 4800/4900
LOCAL AREA NETWORK (LAN)
Sin gle Platform

Pr oce ss or
GUI Serv er
KEY
REMOTE LAN
GUI Client
SO LARIS
CDROM + DAT
Net ra 440 Net ra 20
C DR OM
Su nblade 150 High-End
Su nblade 150 High-End
GUI
CDROM
GUI
SO LARIS
CDROM
Su nbla de 150 Low -End
GUI
Su nbla de 150 High-E nd
GUI
LOCAL DIS K S TORAGE
SO LARIS
SO LARIS
CDROM
SO LARIS
CDROM
GUI: Gra phic Us e r Intrefac e
S OFTWARE P ROCES S
HARDWARE
ti-gsm_OMC-R_network_configuration-0001-ai-sw
68P02901W47-S
2-3
Jul 2008
Configuring the System Controller

Operating System and OMC-R Software Installation on the Single Platform Processor
Chapter 2:
Configuring the System Controller
Procedure for the SunFire 4800/4900

Follow the steps in Procedure 2-1 for configuring the system controller without Ultra Sparc
IV+ processors.
NOTE
The SunFire 4800/4900 system controller may be configured with
Ultra Sparc IV+ processors. If these processors are installed, follow
the instructions in Procedure 2-2 to configure the system controller.
If Ultra Sparc IV+ processors are not installed, follow the Procedure 2-1.
Procedure 2-1
processors)
Configuring the system controller (without Ultra Sparc IV+
Connect a serial terminal to the serial port of SC0 (refer to Figure 2-4)
and choose 0 for a platform shell. Enter the following command:
setupplatform
The following output is displayed, which consists of a series of questions
to be answered. In the following example, sample answers are
shown in bold. Mandatory answers are shown in underlined italics.
Network Configuration
--------------------Is the system controller on a network? []:yes
Use DHCP or static network settings? []:static
Hostname []:somc91_sc0
IP Address []:166.3.22.211
Netmask []:255.255.255.0
Gateway []:166.3.22.84
DNS Domain []:mydomain.com
Primary DNS Server []:166.3.50.200
Secondary DNS Server []:
To enable remote access to the system
controller, select "ssh" or "telnet".
Connection type (ssh, telnet, none) [telnet] :
Idle connection timeout (in minutes; 0 means no timeout) [0] :
Continued
2-4
68P02901W47-S
Jul 2008
Procedure 2-1 Configuring the system controller (without Ultra Sparc IV+
processors) (Continued)
Loghosts
-------Loghost []:somc91
Log Facility []:local0
SNTP
---SNTP server []:<timeserver IP>
SNMP
---Platform Description []:Sun Fire 4800
Platform Contact []:OMC Sysadmin
Platform Location []:Lab
Enable SNMP Agent? []:no
ACLs
---ACL for domain A [ SB0 SB2 SB4 IB6 IB8 ]:
ACL for domain B [ SB0 SB2 SB4 IB6 IB8 ]:
ACL for domain C [ SB0 SB2 SB4 IB6 IB8 ]:
ACL for domain D [ SB0 SB2 SB4 IB6 IB8 ]:
COD
--PROC RTUs installed: 0
PROC Headroom Quantity (0 to disable, 4 MAX) [0]:
PROC RTUs reserved for domain A (0 MAX) [0]:
PROC RTUs reserved for domain B (0 MAX) [0]:
PROC RTUs reserved for domain C (0 MAX) [0]:
PROC RTUs reserved for domain D (0 MAX) [0]:
SC
-SC POST diag Level []:min
Enable SC Failover? []:yes
Logical Hostname or IP Address []:166.3.22.214
Continued
68P02901W47-S
2-5
Jul 2008

Chapter 2:
Security Options
---------------Enable telnet servers? []:yes
Idle connection timeout (in minutes; 0 means no timeout) []:0
Partition Mode
-------------Configure chassis for single or dual partition mode?
[]:single
UltraSPARC IV+ Configuration

---------------------------Is UltraSPARC IV+ going to be deployed in domain A? [false] :
2
Reboot the system controller as follows:

reboot y
Connect a serial terminal to the serial port of SC1 (refer to Figure 2-4),
choose the Platform Shell and enter the following command:
setupplatform
Fewer parameters are configured as this is the slave controller.
Choose a different hostname and IP address, but supply the same
answers for each of the other questions.
IP Address []:166.3.22.212
Netmask []:255.255.255.0
Gateway []:166.3.22.84
SNTP
Continued
2-6
68P02901W47-S
Jul 2008
SC
Security Options
---------------Enable telnet servers? []:yes
Idle connection timeout (in minutes; 0 means no timeout) []:0
4

reboot y
Follow the steps in Procedure 2-2 for configuring the system controller when using Ultra Sparc
IV+ processors.
Procedure 2-2
processors
Configuring the system controller when using Ultra Sparc IV+
Connect a serial terminal to the serial port of SC0 (refer to Figure 2-4 )
and choose 0 for a platform shell. Enter the following command:
setupplatform
The following output is displayed, which consists of a series of questions to be
answered. In the following example, sample answers are shown in
bold. Mandatory answers are shown in underlined italics.
Dual Domain Configuration

------------------------Will you deploy both domains A and B in partition0?
[]:false
IP Address []:166.3.22.211
Netmask []:255.255.255.0
Gateway []:166.3.22.84
Continued
68P02901W47-S
2-7
Jul 2008

Chapter 2:
Procedure 2-2 Configuring the system controller when using Ultra Sparc IV+
processors (Continued)
To enable remote access to the system controller, select ssh or telnet.
Connection type (ssh, telnet, none) [telnet]:
Idle connection timeout (in minutes; 0 means no timeout) [0]:
Loghosts
-------Loghost []:somc91
Log Facility []:local0
SNTP
SNMP
---Platform Description []:Sun Fire 4800
Platform Contact []:OMC Sysadmin
Platform Location []:Lab
Do not enable SNMP Agent unless you use Sun Management Center
software.Enable SNMP Agent? []:no
ACLs
---ACL for domain A [ SB0 SB2 SB4 IB6 IB8 ]:
ACL for domain B [ SB0 SB2 SB4 IB6 IB8 ]:
ACL for domain C [ SB0 SB2 SB4 IB6 IB8 ]:
ACL for domain D [ SB0 SB2 SB4 IB6 IB8 ]:
COD
PROC RTUs reserved for domain A (0 MAX) [0]:
Continued
2-8
68P02901W47-S
Jul 2008
SC
Logical Hostname or IP Address []:166.3.22.214
Partition Mode
-------------Configure chassis for single or dual partition mode?
[]:single
UltraSPARC IV+ Configuration

---------------------------Is UltraSPARC IV+ going to be deployed in partition0?
[]:true

reboot y
Connect a serial terminal to the serial port of SC1 (refer to Figure 2-4),
choose the Platform Shell and enter the following command:
setupplatform
Fewer parameters are configured as this is the slave controller. Choose a
different hostname and IP address, but supply the same answers for each of
the other questions.
IP Address []:166.3.22.212
Netmask []:255.255.255.0
Gateway []:166.3.22.84
SNTP
---This setting is mirrored from the main SC (SC Failover is enabled)
Continued
68P02901W47-S
2-9
Jul 2008

Chapter 2:
SC
4

reboot y
The 3rd and 4th CPUs on the first CPU board now need to be blacklisted
to provide redundancy in the event of a system controller failure.
Connect a serial terminal to the serial port of SC0
(refer to Figure 2-4) and choose 0 for a platform shell.
server_sc0:SC>showcodusage -v
Resource
In Use
Installed
Licensed
--------
------
---------
--------
PROC
Status
-----OK: 0 available
Domain/Resource
In Use
Installed
Reserved
Status
---------------
------
---------
--------
------
A - PROC
SB2 - PROC
/N0/SB2/P0
Unused
/N0/SB2/P1
Unused
/N0/SB2/P2
Unused
/N0/SB2/P3
Unused
SB4 - PROC
/N0/SB4/P0
Unused
/N0/SB4/P0
Unused
/N0/SB4/P0
Unused
/N0/SB4/P0
Unused
B - PROC
C - PROC
D - PROC
Unused - PROC
server_sc0:SC>
The above shows that there are 8 CPUs installed (4 per system processor
board), but that there are none in use and the status of these is unused.
Continued
2-10
68P02901W47-S
Jul 2008
server_sc0:SC>disablecomponent SB2/P2
SB2/P2: will be disabled at the next domain reboot, board power
cycle, or post execution.
server_sc0:SC>
server_sc0:SC>disablecomponent SB2/P3
SB2/P3: will be disabled at the next domain reboot, board power
cycle, or post execution.
server_sc0:SC>
6
Now add the COD licenses for the CPUs.

Example
server_sc0:SC>addcodlicense
01:8307dfac:000000001:0201010100:4:00000000:It6hzrvRp97VTuGvt1WKaA
NOTE
The above is an example of the command and is input as one
continuous line, the long alphanumeric part being taken from the
COD RTU license. This should be a 4 RTU license, for 4 CPUs
(although 4 single RTU licenses can be applied separately, using
the same method).
7
Reserve CPUs for use on Domain A.

server_sc0:SC>setupplatform -p cod
COD
PROC RTUs reserved for domain A (4 MAX) [0]: 4
Check license installation and reserved CPUs in Domain A.
server_sc0:SC>showcodusage -v
Continued
68P02901W47-S
2-11
Jul 2008

Chapter 2:
Resource
In Use
Installed
Licensed
Status
--------
------
---------
--------
------
PROC
OK: 0 available
Domain/Resource
In Use
Installed
Reserved
Status
---------------
------
---------
--------
------
A - PROC
SB2 - PROC
/N0/SB2/P0
Licensed
/N0/SB2/P1
Licensed
/N0/SB2/P2
Licensed
/N0/SB2/P3
Licensed
SB4 - PROC
/N0/SB4/P0
Unused
/N0/SB4/P1
Unused
/N0/SB4/P2
Unused
/N0/SB4/P3
Unused
B - PROC
C - PROC
D - PROC
Unused - PROC
server_sc0:SC>
NOTE
There are 4 licenses showing in use on SB2 (system board) for
processors P0, P1, P2 and P3, but none are licensed for SB4. There
are also 4 Processors reserved for Domain A.
8
POWER cycle the boards to activate the blacklisting previously entered.

server_sc0:SC>setkeyswitch -y -d A off
server_sc0:SC>showboards
Type 0 for Platform Shell
Type 1 for domain A console
Continued
2-12
68P02901W47-S
Jul 2008
Type 2 for domain B console
Type 3 for domain C console
Type 4 for domain D console
Input: 1
Connected to Domain A
Domain Shell for Domain A
server_sc0:A>
9
Powering on the boards.

server_sc0:A>setkeyswitch -y on
10
Check license installation with blacklisted CPUs.

server_sc0:A>showcodusage -v
Domain/Resource
In Use
Installed
Reserved
Status
---------------
------
---------
--------
------
A - PROC
SB2 - PROC
/N0/SB2/P0
Licensed
/N0/SB2/P1
Licensed
/N0/SB2/P2
Unused
/N0/SB2/P3
Unused
SB4 - PROC
/N0/SB4/P0
Licensed
/N0/SB4/P1
Licensed
/N0/SB4/P2
Unlicensed
/N0/SB4/P3
Unlicensed
Unused - PROC
server_sc0:A>
NOTE
It can now be seen that there are 2 licensed CPUs available per
system processor board for domain A.
68P02901W47-S
2-13
Jul 2008
SunFire 4800/4900 configuration

Chapter 2:

After the SunFire 4800/4900, D240 media tray and StorEdge 3310 disk array have been
mounted, attach the cables.
Referring to Figure 2-2, Figure 2-3, and Figure 2-4, ensure that the configuration switch on
the D240 is in the split bus position.
Figure 2-2
StorEdge 3310 Disk Array
Figure 2-3
D240 Media Tray
The SunFire 4800/4900 may have either single or dual SCSI + Ethernet cards in slot 1 of the
I/O Boards. If the card in slot 1 has a single UltraSCSI port and a single Ethernet connection,
follow the wiring diagrams in Figure 2-4. If the card has two UltraSCSI ports and two Ethernet
ports, follow Figure 2-5.
2-14
68P02901W47-S
Jul 2008
Figure 2-4
SunFire 4800/4900
Connect SCSI cables as follows:
Procedure 2-3
68P02901W47-S
SCSI cable connection
From UltraSCSI card 0 (port 1) to lower port B of the 3310.
From UltraSCSI card 1 (port 1) to lower port A of the 3310.
From SCSI+Ethernet card 0 to the top right connector of the D240.
From SCSI+Ethernet card 1 to the top left connector of the D240.
2-15
Jul 2008

Chapter 2:
Connect Ethernet cables to SCSI+Ethernet card 0 and both SC0 Ethernet and SC1 Ethernet. If
you are using a Sun rack, connect a serial port splitter cable to SC0 serial and connect ttyb to
the frame manager. If there is a second serial port splitter cable, then connect it to SC0 serial
and connect ttyb to the frame manager. If you are configuring LAN failover, connect an extra
Ethernet cable to SCSI+Ethernet 1.
Figure 2-5
SunFire 4800/4900 with Dual SCSI
IB 8
S C1 Ethe rne t
Dua l S CS I +
Ethe rne t 1
S C1 S e ria l
Ultra S CS I 1
S ys tem Boa rd 0
HS I 1
S ys tem Boa rd 2
Dua l S CS I +
Ethe rne t 0
S C0 Ethe rne t
S C0 S e ria l
Ultra S CS I 0
Re pe a te r Boa rd 0
HS I 0
Re pe a te r Boa rd 2
IB 6
Connect the SCSI cables as follows:
Procedure 2-4
2-16
SCSI cable connection
Connect the upper-most SCSI port of Dual SCSI + Ethernet 1 (in IB 8, Slot 1) to
the top right most SCSI port of the StorEdge D240 Media Tray.
Connect the upper-most SCSI port of SCSI + Ethernet 0 (in IB 6, Slot 1) to the
top left most SCSI port of the StorEdge D240 Media Tray.
68P02901W47-S
Jul 2008
Connect the three Ethernet cables, to SC0 Ethernet, SC1 Ethernet and the right most Ethernet
port (ETHER0) of Dual SCSI + Ethernet 0 (IB 6, Slot 1).
If you are using a Sun rack, connect a serial port splitter cable to SC0 serial and connect ttyb to
the frame manager. If there is a second serial port splitter cable, then connect it to SC1 serial
and connect ttyb to the frame manager. If configuring LAN failover, connect an extra Ethernet
cable to the right most port (ETHER 0) of Dual SCSI + Ethernet 1 (IB8, Slot 1).
Figure 2-6
Hard Disk layout for 3310 disk array connected to the SunFire 4800/4900
ti-gsm- Hard_Disk_layout_for_ 3310_disk_array_connected_to_the_SunFire _4800_4900-0006-ai-sw
Slotwise allotment of the disks is given in Table 2-1.
68P02901W47-S
2-17
Jul 2008

Table 2-1
Chapter 2:
Disk allotments
Slot
Disk name
Disk sizes allowed
c3t8d0
73 GB drive
c3t9d0
73 GB drive
c3t10d0
73 GB drive
c3t11d0
73 GB drive
c3t12d0
73 GB drive
c3t13d0
73 GB drive
c1t8d0
73 GB drive
c1t9d0
73 GB drive
c1t10d0
73 GB drive
10
c1t11d0
73 GB drive
11
c1t12d0
73 GB drive
12
c1t13d0
73 GB drive
NOTE
Before pulling out a disk for replacement, execute a format >analyze > read on
the disk being pulled out. Also check the LED activity on the disk array to ensure
that the correct disk is being targeted.
2-18
68P02901W47-S
Jul 2008
Netra 440 configuration

Netra 440 rear view
Figure 2-7 illustrates the rear view of a Netra 440.
Figure 2-7
Back panel of Netra 440 ac Version
Cabling procedure
To cable the Netra 440, follow this procedure:
Procedure 2-5
68P02901W47-S
Netra 440 cabling procedure
Connect an Ethernet cable to Ethernet port NET0.
Ensure that the two UltraSCSI cards are installed in slots PCI 2 and PCI 4.
Connect the top most port (Port 1) of the UltraSCSI card in PCI 2 to the
bottom right most SCSI port (A) of the StorEdge 3310.
Connect the top most port (Port 1) of the UltraSCSI card in PCI 4 to the
bottom left most SCSI port (B) of the StorEdge 3310. When powered up,
both TERM lights on the array should be lit.
2-19
Jul 2008
Illustration of completed connections

Figure 2-8 provides a comprehensive illustration of the connections between the Netra 440 and
the StorEdge 3310.
Figure 2-8
Fully cabled Netra 440
ti-gsm-Fully_cabled_Netra_440-0008-ai-sw
2-20
68P02901W47-S
Jul 2008
Netra 440 open front-end view

Figure 2-9 illustrates the internal front-end view of a Netra 440.
Figure 2-9
68P02901W47-S
Front end internal view of Netra 440
2-21
Jul 2008
Figure 2-10
Hard Disk Layout for 3310 disk array connected to the Netra 440
ti-gsm-Hard_Disk_Layout_for_3310_disk_array_connected_to_the_Netra 440-0010-ai-sw
Slotwise allotment of the disks is given in Table 2-2.
Table 2-2
Disk allotment
Slot
Disk name
Disk sizes allowed
c1t8d0
73 GB drive
c1t9d0
73 GB drive
c1t10d0
73 GB drive
c1t11d0
73 GB drive
c1t12d0
73 GB drive
c1t13d0
73 GB drive
c0t8d0
73 GB drive
c0t9d0
73 GB drive
c0t10d0
73 GB drive
10
c0t11d0
73 GB drive
11
c0t12d0
73 GB drive
12
c0t13d0
73 GB drive
NOTE
Before pulling out a disk for replacement, execute a format -> analyze -> read on
the disk being pulled out. Check the LED activity on the disk array to ensure that the
correct disk is being targeted.
2-22
68P02901W47-S
Jul 2008
After the Netra 20 and StorEdge 3310 disk array are mounted, two UltraSCSI cables are
attached.
Figure 2-11
Netra 20
Figure 2-12
StorEdge 3310 Array
ti-gsm-StorEdge _3310 _Array-0012-ai-sw
Ensure that the cable from UltraSCSI 0 (Either Port) on the Netra goes to the lower slot B on
the disk array and the cable from UltraSCSI 1 (Either Port) on the Netra goes to the lower slot A
on the disk array. When powered up, both TERM lights on the array should be lit.
68P02901W47-S
2-23
Jul 2008
Ensure that the terminal connected to the Serial Port console remains connected for the
duration of the installation.
Figure 2-13
NOTE
It is essential that the Netra 20 contains at least one internal disk.
2-24
68P02901W47-S
Jul 2008
Figure 2-14
Hard Disk Layout for 3310 disk array connected to the Netra 20
ti-gsm-Hard Disk_Layout_for_3310_disk_array_connected_to_the_Netra20-0014-ai-sw
Table 2-3
Disk allotment
Slot
Disk name
Disk sizes allowed
c3t8d0
73 GB drive
c3t9d0
73 GB drive
c3t10d0
73 GB drive
c3t11d0
73 GB drive
c3t12d0
73 GB drive
c3t13d0
73 GB drive
c1t8d0
73 GB drive
c1t9d0
73 GB drive
c1t10d0
73 GB drive
10
c1t11d0
73 GB drive
11
c1t12d0
73 GB drive
12
c1t13d0
73 GB drive
NOTE
Before pulling out a disk for replacement, execute a format -> analyze -> read on
the disk being pulled out and check the LED activity on the disk array to ensure
that the correct disk is being targeted.
68P02901W47-S
2-25
Jul 2008
Installing Solaris 10 and OMC Software on SunFire 4800/4900, Netra 440, and Netra 20
Chapter 2:
Installing Solaris 10 and OMC Software on SunFire

4800/4900, Netra 440, and Netra 20
Introduction
Solaris is installed using a customized jumpstart. The jumpstart performs the following tasks:
Installs the operating system from the DVD.
Selects the relevant build profile.
Provides the system with host, IP Address, Netmask, and Default Router.
Installs the OMC Software and Third Party Products.
NOTE
Logging into the SunFire 4800/4900:
Use the main IP address when logging into the SunFire 4800/4900 for normal
use.
The logical IP address can be used for console connections. Logging into the
machine through the SC0 IP address and SC1 IP address is not recommended.
Installing the Solaris and OMC software does not complete the configuration
of the Single Platform Processor. Complete the rest of the chapter before the
OMC is started.
Prerequisites
Use Table 2-4 to record the values that are required during the Solaris installation.
Table 2-4
Prerequisites for Solaris installation
Required Information
Record Values
Hostname
IP Address
Netmask
First Failover IP address [Sunfire only,
optional]
Continued
2-26
68P02901W47-S
Jul 2008
Table 2-4
Prerequisites
Prerequisites for Solaris installation (Continued)
Required Information
Record Values
Second Failover IP address [Sunfire only,

optional]
Default Router
DNS Domain Name [Optional]
Primary DNS server IP address [Optional]
Secondary DNS server
IP address [Optional]
Tertiary DNS server IP address [Optional]
Timeserver Name [Optional]
Timeserver IP address [Optional]
NIS Domain Name
Printer Name [Optional]
Printer IP address [Optional]
GSM Cell ID Country Code
GSM Cell ID Network Code
Datagen Hostname [Optional]
Datagen Country [Optional]
RTF
RTF
RTF
RTF
RTF
License Encryption Key

Ceiling Limit
NE Limit
License Issue Date
Checksum
X25 License Key

X25 Vendor String
X25 License Expiry
Date (if non-permanent)
Switch speed for systems with 254 NEs
Time zone
68P02901W47-S
2-27
Jul 2008
Installing the Solaris and OMC Software on the SunFire 4800/4900, Netra 440, and Netra 20
Chapter 2:
Installing the Solaris and OMC Software on the SunFire

4800/4900, Netra 440, and Netra 20
Introduction
Use the following steps in Procedure 2-6 to install Solaris from a DVD:
Procedure 2-6
Installing Solaris
Load the Jumpstart DVD into the DVD-ROM drive on the Single Platform
Processor.
Commence Solaris installation by following the appropriate procedure:
If you are installing Solaris on a Netra 20, see Netra 20: commence
Solaris installation on page 2-34.
If you are installing Solaris on a Netra 440, see Netra 440: commence
Solaris installation on page 2-33.
If you are installing Solaris on a SunFire 4800/4900, see SunFire

4800/4900: commence Solaris installation on page 2-28.
NOTE
Soft partitioning information for each supported platform is
outlined in a table at the end of this chapter.
Refer to the Chapter 10 SunFire 4800/4900 Troubleshooting.
SunFire 4800/4900: commence Solaris installation

To commence the installation of Solaris on a SunFire 4800/4900:
Procedure 2-7
Installation of Solaris on a SunFire 4800/4900
Connect to the system controller.
Select Domain A.
Continued
2-28
68P02901W47-S
Jul 2008

the Solaris and OMC Software on the SunFire 4800/4900, Netra 440, and Netra 20
Procedure 2-7
3
Installing
Installation of Solaris on a SunFire 4800/4900 (Continued)
Enter the following command at the OK> prompt, and press Return to set
NVRAM parameters to default values:
set-defaults
The following information is displayed:

Setting NVRAM parameters to default values.
4
Enter the following to set auto-boot to false and press Return:

setenv auto-boot? false
The following output is displayed:
auto-boot? = false
Enter the following command to reboot the server and press Return:
reset-all
Resetting,..
Copying IO prom to cpu dram
{/N0/SB2/P2} @(#) lpost
5.15.4
2004/02/05 19:08
{/N0/SB2/P2} Copyright 2001-2004 Sun Microsystems, Inc.
All
rights reserved.
{/N0/SB2/P2} Use is subject to license terms.
..................................
{/N0/SB2/P2} Jumping to memory 00000000.00000020 [00000010]
{/N0/SB2/P2} System PCI IO post code running from memory
{/N0/SB2/P2} @(#) lpost
5.15.4
2004/02/05 19:09
{/N0/SB2/P2} Copyright 2001-2004 Sun Microsystems, Inc.
All
rights reserved.
NOTE
Refer to Updating the Sunfire Patch on page 2-30 for updating the
Sunfire patch before executing the next step.
Continued
68P02901W47-S
2-29
Jul 2008
Procedure 2-7
6
Chapter 2:
Installation of Solaris on a SunFire 4800/4900 (Continued)
Enter the following command, which identifies all of the devices attached
to the SCSI bus, and press Return:
probe-scsi-all

/ssm@0,0/pci@19,700000/pci@2/SUNW,isptwo@4
Target 2
Unit 0
Processor
SUN
D240
Target 4
Unit 0
Disk
SEAGATE ST34371W SUN4.2G7462
Target 6
Unit 0
Removable Read Only device
TOSHIBA DVD-ROM SD-
M14011009
7
Type nvalias cdrom at the OK> prompt.

Highlight the device path associated with the DVD-ROM
drive (this is the first line of the previous screen
output). Paste this device path after nvalias cdrom.
If this string contains scsi, append /disk@6,0:f to the string.
If it contains isptwo, append /sd@6,0:f to the string.
For example:
nvalias cdrom
/ssm@0,0/pci@19,700000/pci@2/SUNW,isptwo@4/sd@6,0:f
or
nvalias cdrom /ssm@0,0/pci@19,700000/pci@2/scsi@2/disk@6,0:f
The 6,0 in this example refers to Target 6 and unit 0 where the DVD-ROM
resides on the SCSI bus.
At the OK> prompt execute the following command:

boot cdrom
NOTE
To continue the Solaris installation, refer to Procedure 2-14.
Updating the Sunfire Patch

To confirm the current firmware level on the Sunfire 4800/4900, from the platform shell, run the
following command as user root:
showb p version v
If the Sunfire platform you are upgrading has a FIRMWARE revision previous to version 5.18.2,
then update it to the latest revision using the following four procedures.
2-30
68P02901W47-S
Jul 2008

Installing
Update the OBP patch level on a Sunfire 4800/4900 Single Platform Processor using the
following procedures:
NOTE
Ensure that the task is completed as user root on a connected GUI Server.
Ensure that the OMC-R Software DVD is in the GUI Server media drive.
Procedure 2-8
Processor
Updating the OBP patch level on a Sunfire 4800/4900 Single Platform
Copy the patch from the following directory:

cp p/cdrom/cdrom0/s0/suninstall/Patches/Firmware/SunFire/* /
Unzip the patch on a GUI server by executing the following command:

unzip <patch#-rev zip>
Ensure that root is not blocked from FTP access. If an entry for root exists
in /etc/ftpusers, comment the line out.
Modify the line for hosts in the /etc/nsswitch.conf file to ensure that files
comes before nis, as follows:
hosts: files nis [NOTFOUND=return]
Ensure that the /etc/hosts file contains an entry for each of the two system
controllers (SC0 and SC1).
NOTE
Ensure that the task is completed as user root on the Single Platform Processor.
The following procedure describes the steps required to reboot the Sunfire 4800/4900 Single
Platform Processor.
Procedure 2-9
Rebooting the Sunfire 4800/4900 Single Platform Processor
Reboot the platform as follows:

shutdown -i0 -g0 y
Attach a console cable to the spare system controller, through a serial port.
This is used to monitor progress.
NOTE
68P02901W47-S
Ensure that the task is completed as user root on a connected GUI Server.
Ensure that the OMC-R Software DVD is in the GUI Server media drive.
2-31
Jul 2008
Chapter 2:
The following procedure describes the steps required to install the patch update.
Procedure 2-10
Installing the Patch Update
From the GUI Server, telnet to spare system controller (SC1) on the Sunfire,
connecting to the platform shell on the spare sc (the prompt is a lowercase
sc rather than uppercase SC). Execute the following command:
flashupdate -f
ftp://root:<guiserver_root_passwd>@<guiserver_ip>//114525-03
scapp rtos
where <guiserver_ip>is the IP address of the gui server where the patch
is unzipped and 114525-03 is the FIRMWARE patch revision copied from
the DVD.
NOTE
The above command lines should be treated as one continuous
line.
2
In the console screen opened through a serial port, monitor the progress,
and wait until the controller has completed the update and rebooted
successfully to 5.18.2.
Attach a console cable to the main system controller on the SPLAT, through
a serial port. This is used to monitor progress.
From the GUI Server, telnet to the main system

controller (SC0) on the Sunfire, connecting to the
platform shell on the main sc (uppercase SC prompt).
Execute the following command:
flashupdate -f
ftp:// root:<guiserver_root_passwd>@<guiserver_ip>//114525-03
all rtos
NOTE
The above command lines should be treated as one continuous
line.
5
In the console screen opened through a serial port, monitor the progress
of the update on the main SC, and wait until the controller has completed
the update and rebooted successfully to 5.18.2.
From the platform shell on the main sc, the firmware version can be listed by:
showb p version v
NOTE
Ensure that the task is completed as user root through the appropriate connection to
the main SC.
The following procedure describes the steps required to complete the procedure and validate.
2-32
68P02901W47-S
Jul 2008

Procedure 2-11
Installing
Completing the procedure and validating
From the console connection to the main SC, having seen the
successful reboot, this should now be showing the OK> prompt.
To return to the system console for domain A:
Enter #
Ensure all the boards have the new version, and then connect to domain A
console and run:
setkey off
setkey on
After the boards have powered back on, if the system does not automatically
boot, go back to the OK>prompt and boot the system as follows:
somc211-sc0:A>
resume{12} ok boot
When the system shows as started successfully, close the terminal

connection.
On the GUI server, return the FTP access for root to its previous setting, if
amended in the file /etc/ftpusers.
Netra 440: commence Solaris installation

Procedure 2-12
Installation of Netra 440: commence Solaris
To commence the installation of Solaris on a Netra 440,

enter the following command at the OK> prompt and
press Return to set NVRAM parameters to default values:
set-defaults
Next type the following to set auto-boot to false and press Return:
auto-boot? = false
Enter the following command to reboot the server, and press Return:
reset-all
Enter the following command at the OK>prompt:

boot cdrom
Continued
68P02901W47-S
2-33
Jul 2008
Procedure 2-12
Chapter 2:
Installation of Netra 440: commence Solaris (Continued)

Boot device: /pci@1e,600000/ide@d/cdrom@0,0:f
File and args:
SunOS Release 5.9 Version Generic_112233-12 64-bit

Copyright 1983-2003 Sun Microsystems, Inc.
All rights reserved.
Use is subject to license terms.

Hardware watchdog enabled
Configuring /dev and /devices
Using RPC Bootparams for network configuration information.
Skipping interface ce1
Skipping interface ce0
NOTE
To continue the Solaris installation, refer to Continue Solaris
installation on page 2-35.
Netra 20: commence Solaris installation

Procedure 2-13
Installation of Netra 20: commence Solaris
To commence the installation of Solaris on a Netra 20, enter the following

command at the OK> prompt and press Return to set NVRAM parameters
to default values:
set-defaults
Enter the following to set auto-boot to false and press Return:

auto-boot? = false
Enter the following command to reboot the server, and press Return:
reset-all
Enter the following command at the OK>prompt:

boot cdrom
LOM event: +4d+1h46m22s host reset screen not found.
keyboard not found.
Continued
2-34
68P02901W47-S
Jul 2008

Procedure 2-13
Installing
Installation of Netra 20: commence Solaris (Continued)
Keyboard not present.
Using lom-console for input and output.
Sun Netra
T4 (2 X UltraSPARC-III+), No Keyboard.
OpenBoot 4.5, 2048 MB memory installed, Serial #51351438.

Ethernet address 0:3:ba:f:8f:8e, Host ID: 830f8f8e.
NOTE
To continue the Solaris installation, refer to Continue Solaris
installation on page 2-35.
Continue Solaris installation

To continue Solaris installation on the Netra 20, Netra 440, or SunFire 4800/4900, follow
this procedure:
Procedure 2-14
Continue Solaris installation

Motorola Common Platform GSM OMCR Installation
==============================================
Now you will be prompted to enter information to cus
tomise your Common Platform GSM OMCR. It is essential
that you provide correct answers to all of the following
questions. An incorrect answer may very likely cause
problems. Refer to your install documentation if you
are not sure which values to supply for any of the questions.
The default response (where one is provided) is in
square brackets ([]).
If a default response exists, you can accept it by pressing
the Enter key.
Continued
68P02901W47-S
2-35
Jul 2008
Procedure 2-14
Chapter 2:
Continue Solaris installation (Continued)
You can enter a period [.] on a line by itself at any prompt

to exit and clear the configuration screen that you are
currently editing.
After the install questions have completed, you will
have a chance to approve or change your settings.
Press -=Enter=- to continue.
Press Enter to continue.
2
A prompt is displayed for entering the host name. Enter the hostname and
press Return. The following output is displayed:
==============================================
Primary Interface Configuration
Your Common Platform GSM OMCR needs to have a primary interface
name (hostname) that should be set to the name that your Common
Platform GSM OMCR will be known as on your local LAN.
Enter the Common Platform GSM OMCR's primary hostname:
NOTE
A host name must be at least two characters: it can contain
letters, digits and minus signs (-). Letters must be in the lower
case. Illegal characters are: !$%^&*(){}~@?>:<|.[]_.
A prompt is displayed requiring the IP address to be entered.

3
Enter the IP address, followed by Return. The following output is displayed:

Your Common Platform GSM OMCR needs to have an IP address
associated with the primary hostname.
This should be set to the IP address that your Common Platform
GSM OMCR will be known as on your local LAN.
Enter the Common Platform GSM OMCR's IP address:
A prompt is displayed requiring the Netmask address to be entered.

Continued
2-36
68P02901W47-S
Jul 2008

Procedure 2-14
4
Installing
Enter the Netmask address, followed by Return. The following output is

displayed:
Your Common Platform GSM OMCR needs to have a netmask associated
with the primary IP address.
This should be set to the netmask that your Common Platform
GSM OMCR will use on your local LAN.
Example: 255.255.255.0
Enter the Common Platform GSM OMCR's netmask:
On the Sunfire, the Do you want to configure NIC failover? message is

displayed. If yes, you are prompted to enter the following information:
Enter the first failover IP address.
Enter the second failover IP address.
NOTE
Configuring this gives the network link redundancy. Both failover
IPs must be on the same subnet as the primary interface.
A prompt is displayed that gives an option to configure a Default Router.
==============================================
Default Router Configuration
Your Common Platform GSM OMCR will need a default router to
access any local LAN network devices that do not reside on any
local subnets it is connected to.
This should be the address of the router on your local LAN.
Contact your system administrator for help
Do you want to configure a default router? (y/n) [y]:
6
If a default router is to be configured, press Enter and the following prompt

is displayed:
Enter the default router's IP address:
Enter the default routers IP address followed by Return.
Continued
68P02901W47-S
2-37
Jul 2008
Procedure 2-14
7
Chapter 2:
If a default router is not required type n and then press Enter. The
installation then proceeds to configure DNS. A prompt is displayed that
gives an option to configure the DNS. The following output is displayed:
==============================================
DNS Configuration
Your Common Platform GSM OMCR will need to have DNS configured to
use hostnames to access your LAN network devices rather than
using their IP addresses.
Contact your system administrator for help.
Do you want to configure DNS? (y/n) [n]:
If DNS is not required, press Enter. The installation then continues to
configure a timeserver.
If DNS is to be configured, type y and press Enter. Screen prompts appear

requesting entry of the DNS Domain name and DNS server IP addresses.
After each prompt, enter the requested value and press Enter:
Enter the Common Platform GSM OMCR's domain:
Enter the LAN primary DNS server IP address:
Enter the LAN secondary DNS server IP address:
Enter the LAN tertiary DNS server IP address:
NOTE
If you are configuring DNS, it is necessary to enter the Domain
name and to supply a primary DNS IP address.
9
A prompt is displayed that gives an option to configure a timeserver. The

following output is displayed:
==============================================
Timeserver Configuration
Your Common Platform GSM OMCR can use an ntp timeserver on your
local LAN to sync the time with the rest of your network.
You can enter an IP address or a name of a timeserver to use on
your network. However, if you specify a name, you must either
have configured DNS or you must add an entry to /etc/inet/hosts
for your timeserver.
Do you want to configure a timeserver? (y/n) [n]
Continued
2-38
68P02901W47-S
Jul 2008

Procedure 2-14
Installing
If a timeserver is to be configured, type y and then press Enter.

The following will appear:
Enter the timeserver's name or IP address:
Enter the timeservers name or IP address and press Enter.
If there are no timeservers to configure, press Enter. The installation then
continues to configure the NIS domain name.
10
A prompt is displayed requiring the NIS domain name to be entered. The

==============================================
NIS domain setup
Your Common Platform GSM OMCR requires Network Information
Services (NIS) to be enabled.
Enter the NIS domain name:
Enter the NIS domain name, followed by Return.

11
A prompt is displayed that gives an option to configure a printer.

==============================================
Printer Configuration
Your Common Platform GSM OMCR may have a printer attached.
You can configure a printer at this time or later.
Do you want to configure a printer? (y/n) [y]:
If there is a printer to be configured, press y and Enter. The following

output appears:
Enter the printer name:
Enter the printer name and press Enter. Then the following will appear:
Enter the printer IP address:
Enter the printer IP address and press Enter.
If there is no printer to be configured, enter n and press Enter and the
installation continues to configure the Mobile Network.
Continued
68P02901W47-S
2-39
Jul 2008
Procedure 2-14
12
Chapter 2:
At the prompt, enter the relevant Country Code, followed by Return.

==============================================
Mobile Network
Your Common Platform GSM OMCR must have the Mobile Network ID
configured.
Enter GSM Cell ID Country Code:
13
When prompted, enter the relevant Network Code, followed by Return.

Enter the GSM Cell ID Network Code:
14
If you are running a Security Application then enter y otherwise enter n.

==============================================
Miscellaneous
Will you be running the Security Application [n]:
15
To enable the Datagen feature enter y otherwise enter n.

Enable Datagen feature? y n
If Datagen is to be configured, press y and Enter. The following prompt
will appear:
Enter the hostname of the DataGen Processor:
Enter the hostname of the Datagen Processor and press Enter. Then the
following output appears:
Enter the Country name for the DataGen Processor:
Enter the Country name of the Datagen Processor and press Enter.
If Datagen is not to be configured, enter n and press Enter and the
installation continues to OMCFEATURES setting.
16
At the following prompt, enter the OMCFEATURES setting:

Enter OMCFEATURES setting: 8913407
Continued
2-40
68P02901W47-S
Jul 2008

Procedure 2-14
17
Installing
At the next prompt, enter the following RTF License Information:

==============================================
OMC RTF License
Your Common Platform GSM OMCR must have an OMC RTF licence.
Enter the RTF Licence Encryption Key:
Enter the RTF Ceiling Limit:
Enter the RTF NE Limit (64 or 128): [or 254 for 120K Sunfire]:
If 254 is entered as RTF NE limit, you should then be prompted to confirm
whether the switch is 2 Mbps (2 HSI cards) or 384 kbps (3 HSI cards):
Enter the RTF Licence Issue Date (For example, 07-apr-2002):
Enter the RTF Checksum.
18
Next, enter the X25 Licensing Information.

==============================================
X25 Network
Your Common Platform GSM OMCR must have a license to run X25. The
license key is a 20 digit hexadecimal string. Use uppercase to
enter the key.
Enter your X25 License Key:
Enter your X25 Vendor String [1]:
If your X25 license is temporary, enter the expiry date.
For a permanent license, enter 01-jan-0 [01-jan-0]:
19
A prompt is displayed to configure a time zone. The following output is

displayed:
==============================================
Timezone Configuration
Your Sun-Based OMCR will need to have a timezone configured.
Some common timezones are:
US/Eastern
US/Central
US/Mountain
US/Pacific
Japan
Would you like to see a list of timezones? (y/n) [n]:

Type y and press Enter to get a list of timezones.
Asia/Taipei
Australia/ACT
Australia/Broken_Hill
Australia/LHI
Continued
68P02901W47-S
2-41
Jul 2008
Procedure 2-14
Chapter 2:
Australia/North
Australia/NSW
.
.
.
Australia/West
Brazil/Acre
Brazil/DeNoronha
Brazil/East
Brazil/West
Canada/Atlantic
However, if your time zone is known, press Enter and type in the time zone,
followed by Return.
Enter the Common Platform GSM OMCR's timezone:
20
A summary of all the values entered is presented. The following output

is displayed:
Motorola Common Platform GSM OMCR Installation ConfigurationSummary
================================================================
Primary Interface
Printer
-----------------
-------
-----------------
-------
IP: 166.3.22.212
IP:
Networking
---------Default Router: 166.3.22.84
Domain: cork.cig.mot.com
NIS domain: omcadmin

DNS
TIME
---
---
Primary: 166.3.50.200
TIMESERVER:
Secondary:
TIMEZONE: Eire
Tertiary:
MCC: 353
DataGen host: claudia
MNC: 123
Using Security Application? n
Country: ireland
Would you like to make changes to the above values? (y/n) [n]:
If all the values are correct, press Enter to accept. However,
if a value needs to be modified, enter y and press Enter.
Continued
2-42
68P02901W47-S
Jul 2008

Procedure 2-14
Installing
Press Return to step through

the entire configuration values that have been entered
from point 4 onwards. These values are in square
brackets. Enter any updated values if necessary.
21
The password configuration prompt appears next. Enter and

re-enter passwords for the following users, followed by Return:
root, informix, omcadmin, and omcread
Motorola Common Platform GSM OMCR Installation - Password
Configuration
==========================================================
The system will now prompt you for passwords for the following
users:
root informix omcadmin omcread
Enter root's password:
Re-Enter root's password:
Enter informix's password:
Re-Enter informix's password:
Enter omcadmin's password:
Re-Enter omcadmin's password:
Enter omcread's password:
Re-Enter omcread's password:
22
The final prompt gives the option to enable the Network Services.
Motorola Common Platform GSM OMCR Installation - Network Services
Configuration
================================================================
This Common Platform GSM OMCR can take advantage of advanced
network services during this installation.
This Common Platform GSM OMCR will need to be connected to the
network through the qfe0 interface and it will be configured
using the following information:
IP: 166.3.22.212
NETMASK: 255.255.255.0
Would you like to enable network services? (y/n) [n]:
Press Enter to disable the network services. The Solaris installation

continues.
NOTE
Entering y enables the debugging mode.
68P02901W47-S
2-43
Jul 2008
Chapter 2:
Solaris installation complete

The Solaris installation is completed and the system starts disk mirroring and displays screen
output similar to the following:
Database closed.
Done
Copying empty map file... Done
Copying printer definition file... Done
Copying FM configuration files... Done
Creating site map... Done
Configuring cronjobs for root... Done
Configuring cronjobs for omcadmin... Done Setting Up Modem... Done
INFO: Configuring PM Loader...
INFO: Done
Setting resource limits... Done
Running post_cutover
Running cm_setup
Creating MIB database... (This can take up to 5 minutes) Done Running convert user
profile info IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT The Single
Platform installation has not yet completed.
Please view installation progress in a console connection.
Using /usr/informix/bin/isqlrf to access the MIB DB
Removing any existing fieldeng[2,3,4] UserProfile accounts.
0 row(s) deleted.
Updating neaccesslevel AND explogincount attributes.
0 row(s) updated.
convertUserProfileInfo completed successfully.
Running tidyup
central console login:
NOTE
2-44
The log files for this section can be found in /var/install/logs and /usr/omc/logs.
At this stage the Clean Install is incomplete and the chapter must be completed
before the OMC starts.
68P02901W47-S
Jul 2008
Configuration checks
Installing additional patches

Additional software patches need to be manually installed from the second OMCR DVD.
Procedure 2-15
Login as user root.
Insert the second DVD Additional OMC Software into the DVD drive. If the
drive already contains a DVD, eject it using the following command:
eject cdrom
Run the following command on a single line to install the patches from the
DVD:
/cdrom/cdrom0/suninstall/bin/install_patches --patch_dir
/cdrom/cdrom0/suninstall/Patches --patch_order
/cdrom/cdrom0/suninstall/Patches/patch_order
Some error messages may be shown if the install_patches script attempts to

install patches that are already installed on the system (see example output
below). These errors can be safely ignored.
# /cdrom/cdrom0/suninstall/bin/install_patches --patch_dir
Patches to be installed: 3
Now installing patches...please wait...
Patches installed: 0/3 (0%)

Patch install complete.
Continued
68P02901W47-S
2-45
Jul 2008

Procedure 2-15
Chapter 2:
Installing additional patches (Continued)
3 patches failed to install. Please check logfile for details.

119059-20 121118-10 122660-07
Logfile is /var/install/logs/patch_install.log
Additional information is available in the patch_install.log file:
Patch install started on Wed Jul 25 17:20:18 BST 2007

Installing 119059-20 Validating patches...
Loading patches installed on the system...
Done!
Loading patches requested to install.
Done!
The following requested patches are already installed on the system
Requested to install patch 119059-20 is already installed on the
system.
No patches to check dependency.
Installing 121118-10
Validating patches...
Done!
Done!
system.
Continued
2-46
68P02901W47-S
Jul 2008
Procedure 2-15
Checking ssh configuration
Done!
Done!
system.
Patch install completed on Wed Jul 25 17:20:25 BST 2007
Checking ssh configuration

When the OMCR installation has completed successfully, this step is required the first time ssh
is used. The ssh will not prompt for a password with this known host on login, the next time
onwards.
Login as user omcadmin and execute the following command:
ssh omc_splat
The authenticity of host omc_splat (10.128.96.200)' can't be established.
RSA key fingerprint is
53:b4:ad:c8:51:17:99:4b:c9:08:ac:c1:b6:05:71:9b.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added omc_splat' (RSA) to the list of known hosts
Detecting the performance problem

If the LAN connecting the server is a 100 Mbps full-duplex network (check with the Network
System Administrator), then the server may experience performance issues. Ignore this section
if the LAN is not 100 Mbps full-duplex.
Run the commands in this section on the console of a system, as changing the network link
settings can cause existing network connections to close.
To check for performance issues on a system, as user root, enter the following command:
/var/install/bin/check_link
68P02901W47-S
2-47
Jul 2008

Chapter 2:
If the output of this command shows nothing, then there is no performance

problem and the rest of this section may be ignored.
If the command detects a 100 Mbps half-duplex link, then you have the option of forcing the
link to 100 Mbps full duplex.
The network interface eri0 has negotiated a 100Mbps half-duplex link.
If connected to a switch, this is often incorrect and may result in very
slow network speeds.
Do you wish to force a 100Mbps full-duplex link? (y/n)
Enter y to force the link speed to 100 Mbps full duplex. Configure to set this speed automatically
on every boot.

The fix for the performance problem described above means that the server no longer
auto-negotiates the network speed. If the server is moved in the future to a network port,
which is not 100 Mbps full duplex, the server may not be able to connect to the network. In
order to re-instate auto negotiation, remove the file /etc/rc2.d/S31linkspeed as user root:rm
/etc/rc2.d/S31linkspeed.
2-48
68P02901W47-S
Jul 2008
X.25 Configuration - SunFire 4800/4900, Netra 440 and Netra 20
X.25 Configuration - SunFire 4800/4900, Netra 440

and Netra 20
X.25 configuration procedures

The following are X.25 configuration topics:
Format of the X25_config files
Creating the X25_config file
Running the Configure_X25 script
The /etc/dfs/dfstab file
The /etc/hosts file
Licensing StorEdge Enterprise Backup
Back up the Single Platform Processor
Format of the X25_config files

Each line in the X25_config file contains eleven fields. These fields are as defined in Table 2-5.
Each entry is separated by a space.
Table 2-5
Fields in the x25_config file
Field
Comments
Record Number
This is the sequential record number.
X.25 Channel Number
The format is X.25_chan<nn>, where nn

equates to the record number.
Sunlink X.25 link number
For the HSI/S configuration, the link

numbers in the X.25_config file must
correspond to the SunLink X.25 link
numbers.
Continued
68P02901W47-S
2-49
Jul 2008
X25_config file entry order Chapter 2: Operating System and OMC-R Software Installation on the Single Platform Processor
Table 2-5
Fields in the x25_config file (Continued)
Field
Comments
X.121 Address
The local X.121 address for an

application (maximum 14 digits). The
X.121 address format is as follows:
Digits 1 to 5 relate to Mobile Country
Code followed by Mobile Network Code.
Digits 6 to 10 are equipment
specific indicators.
Digits 11 and 12 reflect
the HSI Card and Port.
Digits 13 and 14 relate to the subnet
address of the X.25 process.
Interface Type
A value of H relates to SunLink HSI.
Process Call Characteristic
A value of - relates to a calling process. Any

other value in this field relates to a listening
process.
OMC-R Process
The type of X.25 application process:

OMC_BL indicates Bootload.
OMC_EI indicates Event Interface.
OMC_RL indicates Remote Login.
OMC_PU indicates Upload.
Protocol
Set to X.25.
Packet Size
For example, 128.
Window Size
For example, 2.
Time Out Parameter
For example, 50 or 500.
X25_config file entry order

The order of entries in the X25_config file is significant and is specified in Table 2-6.
Table 2-6
Number
Entry order in the x25_config file

X.25
channel
Link
Number
X.121 address
Process call
Characteristic
OMC-R
process
Time out
x25_chan1
12345003000061 g_bootload
OMC_BL
50
x25_chan2
12345003001062 g_bootload
OMC_BL
50
x25_chan3
12345003000141
g_ei
OMC_EI
500
x25_chan4
12345003001142
g_ei
OMC_EI
500
Continued
2-50
68P02901W47-S
Jul 2008
Table 2-6
Number
Creating x25_config file
Entry order in the x25_config file (Continued)

X.25
channel
Link
Number
X.121 address
Process call
Characteristic
OMC-R
process
Time out
x25_chan5
12345003000100
OMC_RL
500
x25_chan6
12345003009999
OMC_PU
50
x25_chan7
12345003009999
OMC_PU
50
The following values are common to all entries:
Interface Type = H
Protocol = X25
Packet size = 128
Window size = 2

To create the x25_config file, execute the following procedure:
Procedure 2-16
On the system processor, login as root.
Go to the following directory:

cd /usr/omc/cdrom_install
Using a text editor update the x25_config1 or

x25_config2 (all other platforms excluding 120K Sunfire) or
x25_config_120K_2Mbps or x25_config_120K_384
kbps configuration file to include
the appropriate X.121 addresses for the system.
The sample file x25_config2 (all other platforms) contains the following data:
1 x25_chan1 0 2020130000061 H g_bootload OMC_BL X25 128 2 50
2 x25_chan2 4 2020130001062 H g_bootload OMC_BL X25 128 2 50
3 x25_chan3 1 2020130000241 H g_ei OMC_EI X25 128 2 500
4 x25_chan4 5 2020130001142 H g_ei OMC_EI X25 128 2 500
5 x25_chan5 1 2020130000200 H - OMC_RL X25 128 2 500
6 x25_chan6 0 2020130001299 H - OMC_PU X25 512 2 50
7 x25_chan7 4 2020130001299 H - OMC_PU X25 512 2 50
8 x25_chan8 2 2020130001299 H - OMC_PU X25 512 2 50
9 x25_chan9 6 2020130001299 H - OMC_PU X25 512 2 50
Edit x25_config_120K_2Mbps for Sunfire 120 K with 2 Mbps switch.
Edit x25_config_120K_384 kbps for Sunfire 120 K with 384 kbps switch.
68P02901W47-S
2-51
Jul 2008

Chapter 2:
NOTE
Event and download connections may go to any port that is connected to the
OMC. Therefore, on a given router, route these connections first to any directly
connected ports, that is to the OMC.
For load balancing purposes, if these ports are busy, the event and download
connections should go to the first interlink between routers. If this interlink is
also busy, then the event and download connections should go to the second
interlink between routers if it exists. The OMC is able to route the event or
bootload the call to the correct OMC process irrespective of which port the call
arrives into the OMC.
NOTE
Add the entries in the Route Selection Table for each of the bootload and event
interface X-121 addresses as listed in the x25_config file.

To start Configure_X25, follow this procedure:
As root on the single platform processor, enter the following command:
/usr/omc/sbin/Configure_X25
Modifying the /etc/hosts file
NOTE
If you are using an ASCII terminal, before using an editor, set the display on the Wyse
120 terminal using the following commands:
TERM=vt100
export TERM
The /etc/hosts file is used to store the Internet Protocol (IP) addresses and
the system names of all the systems, accessible on the network. The systems on the network may also be identified by an alias name or names. The
OMC-R uses the following alias for identifying the Single Platform Processor:
omc_splat omc_pm omc_4gl
Follow the steps in Procedure 2-17 to modify the /etc/hosts file.
2-52
68P02901W47-S
Jul 2008
Procedure 2-17
1
Modifying the /etc/hosts.equiv file
Use a text editor to edit the /etc/hosts file.
NOTE
hosts is a symbolic link to /etc/inet/hosts
It may be necessary to do a forced write to save /etc/hosts

after editing due to its write permissions. In the vi editor,
this is done using the wq!command
The following example shows sample entries for the /etc/hosts file:
127.0.0.1
localhost
111.111.11.11 central central.domainname omc_splat omc_pm omc_4gl

loghost
NOTE
The lines above should be treated as one continuous line.
111.111.11.12 guiserver1
111.111.11.14 netprinter
111.111.11.13 guiclient1
Where
<central> is Single Platform Processor hostname.
<guiserver1> is the GUI Server Processor hostname.
<guiclient1> is the GUI Client Processor hostname.
<netprinter> is the network printer.
2
Refer to Pre-installation requirements for the OMC-R

on page 1-2 of this manual for the host names.
If you are using NIS, then execute the following commands as user root:
cd /var/yp
/usr/ccs/bin/make
Modifying the /etc/hosts.equiv file

The /etc/hosts.equiv file is used to identify trusted systems on the network. Create the
/etc/hosts.equiv file and add the entries shown in bold (in the example) to the file using a text
editor as user root.
Example line entries for the /etc/hosts.equiv file are as follows:
central
guiserver1
guiclient1
68P02901W47-S
2-53
Jul 2008
Creating the /.rhosts file
Creating the /.rhosts file

The /.rhosts file is similar to the /etc/hosts.equiv file and is used to identify trusted systems on
the network. However, this file is used only for providing root access to the listed systems.
Use a text editor to create the file and add the appropriate entries in the /.rhosts file.
The following are example entries for the /.rhosts file:
central
guiserver1
guiclient1
Where:
<central>
Is:
the Single Platform Processor hostname.
<guiserver1>
the GUI Server Processor hostname.
<guiclient1>
the GUI Client Processor hostname.
Modify /etc/dfs/dfstab
NOTE
If you are using an ASCII terminal, before using an editor, set the display
on the terminal using the commands:
TERM=vt100
export TERM
To ensure a successful clean install of the GUI server, complete the following steps before
the clean install.
The Jumpstart software installs a default configuration file for the shared partitions.
GUI servers require the following resources:
/usr/omc/config/global
/usr/omc/ne_data
/usr/omc/ne_data/raw_stats
/home
To make resources on the Single Platform Processor available to other processors, the
information is placed in the /etc/dfs/dfstab file. The file contains:
share -F nfs -o rw=<gui_server>, root=<gui_server> /usr/omc/config/global
share -F nfs -o rw=<gui_server>, root=<gui_server> /usr/omc/ne_data
share -F nfs -o rw=<gui_server>, root=<gui_server> /usr/omc/ne_data/raw_stats
share -F nfs -o rw=<gui_server>, root=<gui_server> /home
2-54
68P02901W47-S
Jul 2008
As root, modify the contents of this file as required. For example, if the GUI server identity is
guiserver1 the file looks like the following:
share -F nfs -o rw=guiserver1,root=guiserver1 /usr/omc/config/global
share -F nfs -o rw=guiserver1,root=guiserver1 /usr/omc/ne_data
share -F nfs -o rw=guiserver1,root=guiserver1 /usr/omc/ne_data/raw_stats
share -F nfs -o rw=guiserver1,root=guiserver1 /home
As root on the single platform processor, execute the following command:
shareall
The sharing of the drivers should be checked with the command:
share
which should give output similar to:

/usr/omc/config/global rw=guiserver1, root:guiserver1
/usr/omc/ne_data rw=guiserver1, root:guiserver1
/usr/omc/ne_data/raw_stats rw=guiserver1, root:guiserver1
/home rw=guiserver1, root:guiserver1

If a web access server (Sun Secure Global Desktop or Tarantella) is used for GUI access,
perform the following step.
As user omcadmin, ensure that the following line is present in the
/usr/omc/config/global/env/Common.csh file:
setenv APPLIX_FONTPATH /usr/applix/axfonts/all_pcf

For the StorEdge Enterprise Backup, locate the enabler cards delivered with the StorEdge
Enterprise Backup software and Networker module for Informix. Follow the steps in
Procedure 2-18 to license the software.
68P02901W47-S
2-55
Jul 2008

Procedure 2-18
Chapter 2:
Login as user root.
Insert the second DVD Additional OMC Software into the DVD drive. If
the drive already contains a DVD, eject it using the following command:
eject cdrom
Copy the StorEdge Enterprise Backup software packages from the DVD:
cp rp /cdrom/cdrom0/suninstall/backup /var/install
cp /cdrom/cdrom0/suninstall/lib/backup.lib
/var/install/lib
cp /cdrom/cdrom0/suninstall/data/package_list
/var/install/data
cp /var/install/backup/tape-mgr /var/install/bin
Install the software:

/var/install/bin/tpp_installer
Installing StorEdge Backup... Done
Installing Solstice Backup Module for Informix... Done
Enter the following commands:

cd /usr/sbin/nsr
./nsrcap -v -c <enabler code>
Register the product within 45 days. Fill in the StorEdge Enterprise Backup
Registration Card and product information.
To get the product information, enter:

/usr/bin/nsr/nwadmin
Select the Server/Server Setup option. Fill in the details. Select Apply to
save the details. When it is done, select View and check the Tabular button.
Then select File/Print. The registration card and the sheet have to be faxed
to the Sun Licensing Center.
When an Authorisation Code is received, enter the following command as

user root:
/usr/bin/nsr/nwadmin
Select Server/registration and fill in the Authorisation Code. Select Apply
to save.
Select File/Exit to close the windows.

After a clean install of the Single Platform Processor, perform a full backup. Refer to the
Motorola manual Operating Information: OMC-R System Administration (68P02901W19) for
the backup procedure.
2-56
68P02901W47-S
Jul 2008
Partitioning information for each supported platform
NOTE
Remember to consult your Motorola Local Office or Customer Representative to
confirm, if the OMC-R requires loading of additional customer applications. Such
applications may include Motorola tools such as COP, MARS and GSM Product
Documentation CDs. This is not an exhaustive list.

Table 2-7
Partitioning information for SF/Netra 20

SF
Netra
20
SF/Netra
20
SF/Netra
20
SF/Netra
20
SF/Netra
20
Size
Size
Main Disk
Mirror
Disk
Soft
Partition
Meta
Device
Meta
Mirror
Meta
Device
Soft
Partition
4830
4830
c1t8
d0s0
c3t8d0s0
none
d1
d0
d2
none
swap
4830
4830
c1t8
d0s1
c3t8d0s1
none
d6
d5
d7
none
/var
20700 20700
c1t8
d0s3
c3t8d0s3
none
d11
d10
d12
none
/usr
13800 13800
c1t8
d0s5
c3t8d0s5
none
d16
d15
d17
none
/opt
17250 17250
c1t8
d0s4
c3t8d0s4
none
d21
d20
d22
none
/omcgen
7000
c1t9
d0s0
c3t9d0s0
d28
d26
d25
d27
d29
/home
10900 10900
c1t9
d0s0
c3t9d0s0
d33
d31
d30
d32
d34
/usr/omc
6000
c1t9
d0s0
c3t9d0s0
d38
d36
d35
d37
d39
/usr/omc
/ne_data
16400 16400
c1t10
d0s0
c3t10d0s0
d43
d41
d40
d42
d44
/usr/omc
/ne_data
/raw_stats
11300 11300
c1t10
d0s0
c3t10d0s0
d48
d46
d45
d47
d49
solbak
8000
c1t12
d0s0
c3t12d0s0
d53
d51
d50
d52
d54
omc_db
_root
11264 11264
c1t10
d0s0
c3t10d0s0
d58
d56
d55
d57
d59
omc_db1
14000 11264
c1t9
d0s0
c3t9d0s0
d63
d61
d60
d62
d64
omc_db2
14000 11264
c1t10
d0s0
c3t10d0s0
d68
d66
d65
d67
d69
File
System
7000
6000
8000
SF/Netra SF/Netra SF/Netra

20
20
20
Continued
68P02901W47-S
2-57
Jul 2008

Table 2-7
Partitioning information for SF/Netra 20 (Continued)

SF
2-58
Chapter 2:
Netra
20
SF/Netra
20
SF/Netra
20
SF/Netra
20
SF/Netra
20
SF/Netra SF/Netra SF/Netra

20
20
20
omc_db3
14000 11264
c1t11
d0s0
c3t11d0s0
d73
d71
d70
d72
d74
omc_db4
14000 11264
c1t12
d0s0
c3t12d0s0
d78
d76
d75
d77
d79
omc_db5
14000 11264
c1t9
d0s0
c3t9d0s0
d83
d81
d80
d82
d84
omc_db6
14000 11264
c1t10
d0s0
c3t10d0s0
d88
d86
d85
d87
d89
omc_db7
14000 11264
c1t11
d0s0
c3t11d0s0
d93
d91
d90
d92
d94
omc_db8
14000 11264
c1t12
d0s0
c3t12d0s0
d98
d96
d95
d97
d99
omc_db9
14000 11264
c1t9
d0s0
c3t9d0s0
d103
d101
d100
d102
d104
omc_db10
14000 11264
c1t10
d0s0
c3t10d0s0 d108
d106
d105
d107
d109
omc_db11
14000 11264
c1t11
d0s0
c3t11d0s0 d113
d111
d110
d112
d114
omc_db12
14000 11264
c1t12
d0s0
c3t12d0s0 d118
d116
d115
d117
d119
omc_db
_logs
2048
2048
c1t10
d0s0
c3t10d0s0 d123
d121
d120
d122
d124
omc_db
_temp
2048
2048
c1t12
d0s0
c3t12d0s0 d128
d126
d125
d127
d129
mib_db1
2048
2048
c1t12
d0s0
c3t12d0s0 d133
d131
d130
d132
d134
mib_db
2048
2048
c1t12
d0s0
c3t12d0s0 d138
d136
d135
d137
d139
mib_db
_logs
2048
2048
c1t12
d0s0
c3t12d0s0 d143
d141
d140
d142
d144
68P02901W47-S
Jul 2008
Table 2-8
File
System
Partitioning information for Netra 440

Netra
440
Netra
440
Netra
440
Netra
440
Netra
440
Netra
440
Netra
440
Netra 440
Size
Main
Disk
Mirror
Disk
Soft
Partition
Meta
Device
Meta
Mirror
Meta
Mirror
Soft
Partition
4830
c0t8
d0s0
c1t8d0s0 none
d1
d0
d2
none
swap
4830
c0t8
d0s1
c1t8d0s1 none
d6
d5
d7
none
/var
20700
c0t8
d0s3
c1t8d0s3 none
d11
d10
d12
none
/usr
13800
c0t8
d0s5
c1t8d0s5 none
d16
d15
d17
none
/usr
17250
c0t8
d0s4
c1t8d0s4 none
d21
d20
d22
none
7000
c0t9
d0s0
c1t9d0s0
d28
d26
d25
d27
d29
10900
c0t9
d0s0
c1t9d0s0
d33
d31
d30
d32
d34
/usr/omc
6000
c0t9
d0s0
c1t9d0s0
d38
d36
d35
d37
d39
/usr/omc
/ne_data
16400
c0t10
d0s0
c1t10d0s0 d43
d41
d40
d42
d44
/usr/omc 11300
/ne_data
/raw_stats
c0t10
d0s0
c1t10d0s0 d48
d46
d45
d47
d49
8000
c0t12
d0s0
c1t12d0s0 d53
d51
d50
d52
d54
11264
c0t10
d0s0
c1t10d0s0 d58
d56
d55
d57
d59
omc_db1 11264
c0t9
d0s0
c1t9d0s0
d63
d61
d60
d62
d64
omc_db2 11264
c0t10
d0s0
c1t10d0s0 d68
d66
d65
d67
d69
omc_db3 11264
c0t11
d0s0
c1t11d0s0 d73
d71
d70
d72
d74
omc_db4 11264
c0t12
d0s0
c1t12d0s0 d78
d76
d75
d77
d79
omc_db5 11264
c0t9
d0s0
c1t9d0s0
d83
d81
d80
d82
d84
omc_db6 11264
c0t10
d0s0
c1t10d0s0 d88
d86
d85
d87
d89
omc_db7 11264
c0t11
d0s0
c1t11d0s0 d93
d91
d90
d92
d94
/omcgen
/home
solbak
omc_db
_root
Continued
68P02901W47-S
2-59
Jul 2008

Table 2-8
Partitioning information for Netra 440 (Continued)

Netra
440
2-60
Chapter 2:
Netra
440
Netra
440
Netra
440
Netra
440
Netra
440
Netra
440
Netra 440
omc_db8 11264
c0t12
d0s0
c1t12d0s0 d98
d96
d95
d97
d99
omc_db9 11264
c0t9
d0s0
c1t9d0s0 d103
d101
d100
d102
d104
omc_db10 11264
c0t10
d0s0
c1t10d0s0 d108
d106
d105
d107
d109
omc_db11 11264
c0t11
d0s0
c1t11d0s0 d113
d111
d110
d112
d114
omc_db12 11264
c0t12
d0s0
c1t12d0s0 d118
d116
d115
d117
d119
omc_db
_logs
2048
c0t10
d0s0
c1t10d0s0 d123
d121
d120
d122
d124
omc_db
_temp
2048
c0t12
d0s0
c1t12d0s0 d128
d126
d125
d127
d129
mib_db1
2048
c0t12
d0s0
c1t12d0s0 d133
d131
d130
d132
d134
mib_db
2048
c0t12
d0s0
c1t12d0s0 d138
d136
d135
d137
d139
mib_db
_logs
2048
c0t12
d0s0
c1t12d0s0 d143
d141
d140
d142
d144
68P02901W47-S
Jul 2008
Chapter
3
GUI Server Configuration
68P02901W47-S
Jul 2008
3-1
GUI server configuration
GUI server configuration
Introduction
Refer to the relevant GSM OMC-R Release Notes for installation instructions specific to this
release and for details of the disk space required for this release.
NOTE
Install the Single Platform Processor before performing these procedures. If
the Single Platform Processor is not configured, this procedure fails.
Refer to Single Platform Processor install chapter sections:
/etc/dfs/dfstab file
The GUI server must be a Sunblade 150 or N210 machine.
Obtaining the boot prompt

Obtain the OK>prompt by entering the following command as root:
/usr/sbin/shutdown -g0 -i0 -y
Running Jumpstart
The Jumpstart procedure is used for installing Solaris 10, CDE, and StorEdge on the GUI server.
The procedure is as follows:
Procedure 3-1
Running Jumpstart

reset-all
Enter the following command at the OK> prompt to check that the system is
configured correctly:
Continued
3-2
68P02901W47-S
Jul 2008
Procedure 3-1
Running Jumpstart
Running Jumpstart (Continued)
probeide
On a Sunblade platform, output similar to the following should be seen:
Device 0 (Primary Master)

ATAModel: ST340016A
Device 1 (Primary Slave)
Removable ATAPI Model: Litean DVD-ROM LTD163
Device 2 (Secondary Master)
ATAModel: ST340016A
Device 3 (Secondary Slave)
Not present.
On a Netra 210 platform, output similar to the following should be seen:
Device 0
( Primary Master )
Removable ATAPI Model: TSSTcorpCD/DVDW TS-L532U

Device 1
( Primary Slave )
Not Present
Device 2
( Secondary Master )
Not Present
Device 3
( Secondary Slave )
Not Present
On the Netra 210 platform the SCSI configuration also
needs to be checked. Enter the following command:
probe-scsi
Output similar to the following should be seen:
MPT Version 1.05, Firmware Version 1.08.04.00
Target 0
Unit 0
Disk
SEAGATE ST973401LSUN72G 0556
143374738 Blocks, 73 GB
SASAddress 5000c5000092b149
PhyNum 0
Target 1
Unit 0
Disk
FUJITSU MAY2073RCSUN72G 0401
43374738 Blocks, 73 GB
SASAddress 500000e0123faa42
3
68P02901W47-S
PhyNum 1
Place the GSR 9 DVD into the DVD-ROM drive and enter the following
command:
boot cdrom
3-3
Jul 2008
Running Jumpstart
The following is sample output that can be expected during the installation.
Procedure 3-2
Jumpstart procedure for installing Solaris 10
When the boot command is entered, the following output is displayed:

Motorola GSM OMC-R GUI Server Installation
==========================================
Now you will be prompted to enter information to customize your
GSM OMC-R GUI server. It is essential that you provide correct
answers to all of the following questions. An incorrect answer
may very likely cause problems. Refer to your install
documentation if you are not sure which values to supply for any
of the questions.
The default response (where one is provided) is in square

brackets ([]).
If a default response exists, you can accept it by pressing the
Enter key.
After the install questions have completed, you will have a
chance to approve or change your settings.
Once the settings have been approved, the system will be wiped
and installed from scratch.
Press -=Enter=- to continue.
Press Enter to continue
2
press Return. The following output is displayed:
==========================================
Primary Interface Configuration
Your GSM OMC-R GUI server needs to have a primary interface
name (hostname) that should be set to the name that your GSM
OMC-R GUI server will be known as on your local LAN.
Enter the GSM OMC-R GUI server's primary hostname:
Continued
3-4
68P02901W47-S
Jul 2008
Procedure 3-2
Running Jumpstart
Jumpstart procedure for installing Solaris 10 (Continued)
NOTE
A host name must be at least two characters: it can contain
letters, digits and minus signs (-). Letters must be lower case.
Illegal characters are: !$%^&*(){}~@?>:<|.[]_.
3
A prompt is displayed requiring the IP address to be entered. Enter the IP

address, followed by Return. The following output is displayed:
Your GSM OMC-R GUI server needs to have an IP address
associated with the primary hostname. This should be set to
the IP address that your GSM OMC-R GUI server will be known as
on your local LAN.
Enter the GSM OMC-R GUI server's IP address:
A prompt is displayed requiring the Netmask address to be entered. Enter

the Netmask address, followed by Return. The following output is displayed:
Your GSM OMC-R GUI server needs to have a netmask associated
with the primary IP address.
This should be set to the netmask that your GSM OMC-R GUI
server will use on your local LAN.
Example: 255.255.255.0
Enter the GSM OMC-R GUI server's netmask:
A prompt is displayed that gives an option to configure

a Default Router. The following output is displayed:

==========================================
Default Router Configuration
Your GSM OMC-R GUI server will need a default router to access
any local LAN network devices that do not reside on any local
subnets it is connected to.
This should be the address of the router on your
local LAN. Contact your system administrator for help
Continued
68P02901W47-S
3-5
Jul 2008
Running Jumpstart
Procedure 3-2
Do you want to configure a default router? (y/n) [y]: y

If a default router is to be configured, press Enter and the
following will appear.
Enter the default router's IP address:
Enter the default routers IP address followed by Return.
If a default router is not required type n and then press Enter. The
installation then proceeds to configure DNS.
6
A prompt is displayed that gives an option to configure the DNS. The

==========================================
DNS Configuration
Your GSM OMC-R GUI server will need to have DNS configured to
use hostnames to access your LAN network devices rather than
using their IP addresses.
Do you want to configure DNS? (y/n) [n]: n
If DNS is not required, press Enter. The installation then continues to
configure a timeserver.
If DNS is to be configured, enter y and press Enter.

Screen prompts appear requesting entry of the DNS domain
name and DNS server IP addresses. After each prompt, enter the requested
value and press Enter.
Enter the Common Platform GSM OMCR's domain:
Enter the LAN primary DNS server IP address:
Enter the LAN secondary DNS server IP address:
Enter the LAN tertiary DNS server IP address:
NOTE
If you are configuring DNS, it is necessary to enter the domain
name and to supply a primary DNS IP address.
Continued
3-6
68P02901W47-S
Jul 2008
Procedure 3-2
8
Running Jumpstart
A prompt is displayed that gives an option to configure a timeserver. The

==========================================
Timeserver Configuration
Your GSM OMC-R GUI server can use a ntp timeserver on your
local LAN to sync the time with the rest of your network.
You can enter an IP address or a name of a timeserver to use
on your network. However, if you specify a name, you must
either have configured DNS or you must add an entry to
/etc/inet/hosts for your timeserver.
Do you want to configure a timeserver? (y/n) [n]: n
If a timeserver is to be configured, enter y and then press Enter. The
following output appears:
Enter the timeserver's name or IP address:
Enter the timeservers name or IP address and press Enter.
If there are no timeservers to configure, press Enter and the installation
continues to configure the NIS domain name.
A prompt is displayed asking if a NIS domain name is required. If you are

not using NIS, enter n and manually configure your name service (such as
LDAP) later on. The following output is displayed:
==========================================
NIS domain setup
Your GSM OMC-R GUI Server can have Network Information Services
(NIS) enabled.
The NIS domain is a character string e.g. omcadmin
Do you want to configure NIS? (y/n) [y]: y
Enter the NIS domain name: omcadmin
Enter the NIS domain name, followed by Return.
Continued
68P02901W47-S
3-7
Jul 2008
Running Jumpstart
Procedure 3-2
10
A prompt is displayed requiring OMC-R server information:

==========================================
OMC-R server Configuration
Your GSM OMC-R GUI server must be connected to an OMC-R server.
Enter the OMC-R server hostname: <server_hostname>
Enter the OMC-R server IP address: <server_ip_address>
11
A prompt is displayed requiring Printer information:

==========================================
Printer Configuration
Your GSM OMC-R GUI server may have a printer attached.
You can configure a printer at this time or later.
Do you want to configure a printer?: n
12
A prompt is displayed to configure a time zone. The following output is

displayed:
==========================================
Timezone Configuration
Your Sun-Based GSM OMC-R GUI server will need to have a timezone
configured and it must be the same as the Single Platform
Processor.
Some common timezones are:
US/Eastern
US/Central
US/Mountain
US/Pacific
Japan
Would you like to see a list of timezones? (y/n) [n]:

Enter the GSM OMC-R GUI server's timezone:
Enter y and press Enter to get a list of time zones.
Press the space bar to navigate this list.
Continued
3-8
68P02901W47-S
Jul 2008
Procedure 3-2
Running Jumpstart
Asia/Taipei
Australia/ACT
Australia/Broken_Hill
.
.
.
Australia/West
Brazil/Acre
Brazil/DeNoronha
Brazil/East
Brazil/West
Canada/Atlantic
However, if your time zone is known press Enter and type in the time zone,
followed by Return.
Enter the Common Platform GSM OMCR's timezone:
13
A summary of all the values entered is presented. The following output

is displayed:
Motorola GSM OMC-R GUI Server Installation Configuration
Summary
===================================================
Primary Interface
Printer
-----------------
-------
HOSTNAME: somc5
Install printer?: n
IP: 175.33.44.111
NETMASK: 255.255.255.0
SPLAT_NAME: somc57
SPLAT_IP: 175.3.44.4
Networking
---------Default Router:
175.3.44.84
Domain:
NIS domain: omcadmin

DNS
TIME
---
----
Primary:
TIMESERVER:
Secondary:
TIMEZONE: Eire
Tertiary:
Continued
68P02901W47-S
3-9
Jul 2008
Running Jumpstart
Procedure 3-2
Would you like to make changes to the above values? (y/n) [n]:
If all of the values are correct, press Enter to accept. However, if a value
needs to be modified, type y and press Enter. Press Return to step
through the entire configuration values that have been entered from point
4 onwards. These values are in square brackets. Type in any updated
values as necessary.
14
The password configuration prompt appears next. Enter and re-enter

passwords for the following users, followed by Return: root.
15
The Solaris installation will continue at this point and screen output similar
to the following will be displayed:
STARTED NETWORK SERVICES
Setting default PROM values...
Done
Starting Solaris Install
Beginning system identification...
Searching for configuration file(s)...
Search complete.
Discovering additional network configuration...
Completing system identification...
Starting remote procedure call (RPC) services: done.
System identification complete.
Installing Solaris
Starting Solaris installation program...
Checking rules.ok file...
Using profile: install.input
.
.
.
Finish script postinstall execution completed.
The begin script log 'begin.log' is located in
/var/sadm/system/logs after reboot.
The finish script log 'finish.log' is located in
/var/sadm/system/logs after reboot.
syncing file systems... done
rebooting...
.
.
.
Continued
3-10
68P02901W47-S
Jul 2008
Procedure 3-2
Running Jumpstart
Netra 210, No Keyboard

Copyright 2005 Sun Microsystems, Inc.
OpenBoot 4.18.10, 2048 MB memory installed, Serial #72314253

Ethernet address 0:14:4f:4f:6d:8d, Host ID: 844f6d8d.
Rebooting with command: boot
Boot device: /pci@1c,600000/LSILogic,sas@1/disk@0,0:a
File and args:


Hostname: ne210gui2
Configuring devices.
Loading smf(5) service descriptions: 22/22
checking ufs filesystems
/dev/md/rdsk/d15: is logging.
Configuring LVM partitions... Creating new rsa public/private host key pair
Creating new dsa public/private host key pair
Done
Installing NIS
Installing Applix... Nov 19 17:08:12 ne210gui2 hsfs:
NOTICE: hsfs: Warning: file system mounted on
/cdrom/"jumpstart_omcr.190027"/s0
Nov 19 17:08:12 ne210gui2 does not conform to the
ISO-9660 specification:
Nov 19 17:08:12 ne210gui2 hsfs: file len greater than max allowed
Nov 19 17:08:12 ne210gui2 hsfs:
Due to this error, the file system may not be
correctly interpreted.
Nov 19 17:08:12 ne210gui2 hsfs:
Other such errors in this file system will be silently ignored.
Done
Installing Enscript... Done
Installing Informix 10... Done
Installing Python/OSP... Done
Installing StorEdge Backup Client... Done
Installing OMC-R 1900... Done
Installing OMC-R 1900... Done
Installing OMC-R 1900 Help... Done
.
.
Continued
68P02901W47-S
3-11
Jul 2008
Running Jumpstart
Procedure 3-2
.
Relinking /usr/omc/current... Done
Configuring file permissions... Done
Creating startup files... Done
Configuring SMF permissions... Loading smf(5) service descriptions: 1/1
Loaded 1 smf(5) service descriptions
svccfg: Pattern 'omc' doesn't match any instances or services
svcadm: Pattern 'omc' doesn't match any instances
Done
Copying release specific scripts... Done
Configuring cronjobs for root... Done
Configuring cronjobs for omcadmin... Done
Configuring Common Desktop Environment for GUI Server
Configuration of CDE successful
GUI Server Installation Complete
Installing tidyup
ne210gui2 console login:
NOTE
This concludes the GUI server installation.
The following messages can be safely ignored:
svcadm: Pattern 'omc' doesn't match any instances
NOTE
3-12
The log files for this section can be found in /var/install/logs.
When the message The system is ready appears on the console, it is safe to
proceed to the section Performance problem with GUI servers on page 3-13.
68P02901W47-S
Jul 2008
Performance problem with GUI servers
Performance problem with GUI servers

If the LAN connecting the GUI server is a 100 Mbps full-duplex network (check with the
Network System Administrator), then the GUI server may experience performance issues.
Ignore this section if the LAN is not 100 Mbps full-duplex.
Run the commands in this section on the console of a system, as changing the network link
settings can cause existing network connections to close.
To check for performance issues on a system, as user root, enter the following command:
/var/install/bin/check_link
If the output of this command shows nothing, then there is no performance
problem and the rest of this section may be ignored.
If the command detects a 100 Mbps half-duplex link, then you
have the option of forcing the link to 100 Mbps full duplex.
The network interface eri0 has negotiated a 100 Mbps half-duplex link.
If connected to a switch, this is often incorrect and may result in very
slow network speeds.
Do you wish to force a 100 Mbps full-duplex link? (y/n)
If you answer y to this question, the link speed is forced to 100 Mbps full duplex and it is
configured to set this speed automatically on every boot.

The fix for the performance problem described above means that the GUI
server platform no longer auto-negotiates the network speed. In future, if the
GUI server platform is moved to a network port, which is not 100 Mbps full
duplex, the GUI server may not be able to connect to the network. In order to
re-instate auto negotiation, remove the file /etc/rc2.d/S31linkspeed as user root:
rm/etc/rc2.d/S31linkspeed.
68P02901W47-S
3-13
Jul 2008
Configuring secure services

Manually enable the Secure services on the GUI server.
Ensure that the first GSR9 OMCR DVD OMC Software and Jumpstart is inserted in the DVD
drive (either in the local DVD drive if installing locally, or the OMC-R DVD drive if remotely
installing the GUI server), then enter the following commands as root:
/cdrom/cdrom0/s0/suninstall/bin/security/secure
/var/install/security/os_harden

If a web access server (Sun Secure Global Desktop or Tarantella) is used for GUI access,
perform the following step.
As user omcadmin, ensure that the following line is present in the
/usr/omc/config/global/env/Common.csh file:
setenv APPLIX_FONTPATH /usr/applix/axfonts/all_pcf

Manually install the additional software patches from the second OMCR DVD.
Procedure 3-3
Login as user root.
Insert the second DVD Additional OMC Software into the DVD drive. If
installing the GUI server remotely, the disc needs to be inserted into the
OMC-R DVD drive. If the drive already contains a DVD, eject it using the
following command:
eject cdrom
Continued
3-14
68P02901W47-S
Jul 2008
Procedure 3-3
3
DVD:

119059-20 121118-10 122660-07

Done!
Done!

system.
Continued
68P02901W47-S
3-15
Jul 2008
Procedure 3-3

Done!

Done!
system.
Done!
Done!
system.
3-16
68P02901W47-S
Jul 2008
Flexible GUI server configuration
Flexible GUI server configuration
Introduction
The option of a Minimum Flexible Platform allows the OMC-R to be installed on a GUI server if
the GUI server meets the hardware and software criteria. It is the responsibility of the customer
to provide the necessary hardware and to configure it correctly.
NOTE
The configuration of the platform requires advanced knowledge of system
administration.
Prerequisites for installation

The following are the prerequisites for installation:
SUN hardware platform meeting the minimum specification.
Additional software drivers (if required for the hardware platform).
Sun Solaris 10 installation media for the platform.
GSR 9 OMC-R DVD.
File systems to be configured to the minimum specification (refer to Table 3-1).
Table 3-1
File system configuration
Name
Minimum Size (MB)
Usage
7588
File system
swap
592
Swap space
/usr/omc
4220
File system
Configuring the flexible platform

The instructions to configure the flexible platform for installing and operating the OMC-R on the
GUI server are described in the following sections.
68P02901W47-S
3-17
Jul 2008
Install the operating system

An automated Jumpstart procedure is NOT provided. It is necessary to install the Solaris 10
operating system using the Sun Solaris 10 Installation media. Create the file systems /, swap,
and /usr/omc and configure them with a minimum size as outlined in the Table 3-1 during
installation. This procedure assumes NIS is being used as the naming service on the OMC-R.
If any other naming service is used then the appropriate configuration settings for that naming
service needs to be configured during the NIS configuration section in this guide.
If NIS is not used the following users and groups need to be created on the flexible GUI server:
Groups: omc (with the same group id as on the SPLAT), informix (with the same group id
as on the SPLAT) and omcread (with the same group id as on the SPLAT).
Users: informix (with the same user id as on the SPLAT), omcadmin (with the same user
id as on the SPLAT), omcread (with the same user id as on the SPLAT) and all other
OMC-R users.
NOTE
These users need to be configured exactly as on the SPLAT.
Modify files
Follow the steps in Procedure 3-4 to modify files.
Procedure 3-4
Modify files
Modify the /etc/hosts file. Add entries as shown in the example below to the
/etc/hosts file using a text editor.
111.111.111.12 guiserver1 guiserver1.domainname loghost
111.111.111.11 central omc_splat omc_pm omc_4gl
111.111.111.13 guiclient1
111.111.111.14 printer
Edit the /etc/hosts file on the SPLAT to add the entry for the flexible GUI
server. Follow the steps outlined in the Procedure 2-17 Modifying the
/etc/hosts file on page 2-53.
NOTE
The entries guiserver1, central and guiclient1 represent the
names of the GUI server, the Single Platform Processor and the
GUI client respectively. The printer is optional.
2
If NIS is not being used, configure an alternative naming service and

proceed to step 4 titled Modify the /etc/vfstab file.
Continued
3-18
68P02901W47-S
Jul 2008
Procedure 3-4
3
Modify files (Continued)
Modify the /etc/defaultdomain file. The default domain should be set in

order for the GUI server to use the Single Platform Processor as its yp
master. Enter the following commands as user root on the GUI server:
domainname <domain>
echo domainname > /etc/defaultdomain
ypinit c
Where <domain>is the name of the domain

used by the network. For example, omcadmin.
Enter omc_splat to represent the Single Platform
Processor and press Return. To verify it type y.
Execute the following command:
cp /etc/nsswitch.nis /etc/nsswitch.conf
Create a file called /etc/defaultrouter that contains the IP

address of the default router in the form: nnn.nnn.nnn.nnn.
Edit /etc/auto_master and find the following line:
/home
auto_home
-nobrowse
Replace this line with:

#/home
auto_home
-nobrowse
Save and exit the file. Reboot the GUI server to enable the new host settings
by entering:
touch /reconfigure
/usr/sbin/shutdown -g0 -i6 y
To verify that the name of the Single Platform Processor is correct, enter
the command:
ypwhich
Check whether the /etc/defaultdomain file has been set up correctly by

typing the command:
domainname
The output should be the name of the domain used by the network, for
example, omcadmin.
Continued
68P02901W47-S
3-19
Jul 2008
Procedure 3-4
4
Modify the /etc/vfstab file. Update the /etc/vfstab file

with the directories that are shared out by the SPLAT.
Use the vi editor to add the following entries to the file:
omc_splat:/home - /home nfs - yes rw,hard,intr
omc_splat:/usr/omc/config/global - /usr/omc/config/global nfs
- yes rw,hard,intr
omc_splat:/usr/omc/ne_data - /usr/omc/ne_data nfs - yes
rw,hard,intr
omc_splat:/usr/omc/ne_data/raw_stats /usr/omc/ne_data/raw_stats nfs - yes rw,hard,intr
Create the following directories by running the commands:

mkdir p /usr/omc/config/global
mkdir p /usr/omc/ne_data
mkdir p /usr/omc/ne_data/raw_stats
Run the command:
mountall
Check whether the NFS is running correctly by executing:

df k | grep omc_splat
The four directories shared by the SPLAT should be listed.
omc_splat:/home 1016122 3155 952000 1% /home
omc_splat:/usr/omc/config/global 2501991
467635 1984317 20% /usr/omc/config/global
omc_splat:/usr/omc/ne_data 1488787
1782 1427454 1% /usr/omc/ne_data
omc_splat:/usr/omc/ne_data/raw_stats 1490275 1522 1429142 1%
If the output does not contain entries for /home,

/usr/omc/config/global, /usr/omc/ne_data,
/usr/omc/ne_data/raw_stats, then perform the following steps:
Follow the steps outlined in the section Modify /etc/dfs/dfstab on page
2-54 in Chapter 2.
To ensure that the NFS software is running,

execute the following commands on the splat:
/etc/init.d/nfs.server stop
/etc/init.d/nfs.server start
share
Example output is as follows:
- /usr/omc/config/global rw=guiserver1,root=guiserver1 "",
- /usr/omc/ne_data rw=guiserver1,root=guiserver1 "",
- /usr/omc/ne_data/raw_stats rw=guiserver1,root=guiserver1 "",
- /home rw=guiserver1:guiclient1,root=guiserver1:guiclient1 "",
Run the following command if NIS has been configured:

scp omc_splat:/etc/TIMEZONE /etc
If prompted for a password enter the root password for the OMC-R SPLAT.
Continued
3-20
68P02901W47-S
Jul 2008
Procedure 3-4
10
Verify the configuration of the Flexible Platform
Edit the /etc/hosts.equiv file on the SPLAT and add an entry

for the flexible GUI server. This is done by appending the
hostname of the flexible GUI server to the file. Example
line entries for the /etc/hosts.equiv file are as follows:
central
guiserver1
guiclient1
Verify the configuration of the Flexible Platform

Run the script verify_platform which checks the configuration of the Flexible Platform, before
attempting to install the GSR 9 OMC-R. Discrepancies between the platform and the minimum
specification result in errors and/or warnings being generated. It is the responsibility of the
user to correct these problems before installing the OMC-R. Ensure that you are logged in as
root. Insert the GSR 9 OMC-R DVD in the DVD ROM drive.
To validate the flexible platform, execute the following:
cd /cdrom/cdrom0/s0/suninstall/Flexible
./verify_flex_platform
Verifying Platform..
Platform Configuration: GUI server
Checking OS version..
Installed Operating System: 5.9
OS version is OK
<output omitted.. >
Finished verification of GUI server platform
Check logfile: /var/tmp/verify_flex_platform.<log>
No warnings were detected
No errors were detected
CAUTION
Installation of the GSR 9 OMC-R software on a platform that has not been successfully
validated by the verify_platform script may result in the failure of the installation
and/or incorrect operation of the software.
NOTE
The verify_platform log file can be found in /var/install/logs/verify_flex_platform.log. Check the file for any errors.
68P02901W47-S
3-21
Jul 2008
Install the Third Party Packages on the GUI server
Install the Third Party Packages on the GUI server

The required software packages are installed by executing the following commands as user root:
/cdrom/cdrom0/s0/suninstall/Flexible/flexible_file_install
echo PACKAGE_LIST=/var/install/data/package_list.GUI' > /var/install/sc_conf.sh
echo PRIMARY_INTERFACE="<PRIME_NIC>"' >> /var/install/sc_conf.sh
Where <PRIME_NIC> is the primary network interface used by the flexible GUI server.
For example:
echo 'PRIMARY_INTERFACE="bge0"' >> /var/install/sc_conf.sh
Refer Performance problem with GUI servers on page 3-13 to resolve potential performance
issues with the GUI server.
Edit /var/install/data/package_list.GUI and find the following line:
enable_gui_access|/usr/omc/sbin/enable_gui_access|script|abort|upgrade-skip
And replace it with:
#enable_gui_access|/usr/omc/sbin/enable_gui_access|script|abort|upgrade-skip
Save and exit the file.
Execute the following script as user root:
/cdrom/cdrom0/s0/suninstall/bin/tpp_installer
The list of packages installed is:
MOTaplx
MOTensc
MOTinfx
MOTosp
SUNWebsc
MOTc1900
MOTc1900<X>
MOTh1900<X>
Where <X> is the release number of the OMC-R software. For example, MOTc190028
3-22
68P02901W47-S
Jul 2008

Manually enable the secure services on the GUI server.
Ensure that the first GSR9 OMCR DVD OMC Software and Jumpstart is inserted in the DVD
drive (either in the local DVD drive if installing locally, or the OMC-R DVD drive if remotely
installing the GUI server), then enter the following commands as root:
/cdrom/cdrom0/s0/suninstall/bin/security/secure
/var/install/security/os_harden

Manually install the additional software patches from the second OMCR DVD.
Procedure 3-5
Login as user root.
Insert the second DVD Additional OMC Software

into the DVD drive. If the drive already contains a DVD, eject it using the
following command: eject cdrom
DVD:


Continued
68P02901W47-S
3-23
Jul 2008
Procedure 3-5

119059-20 121118-10 122660-07

Done!
Done!
system.
Done!
Done!
system.
Continued
3-24
68P02901W47-S
Jul 2008
Procedure 3-5
Done!
Done!
system.
68P02901W47-S
3-25
Jul 2008
SunRay Server Software Installation
Overview of installation
This section describes the installation procedures used for installation and configuration of the
SunRay Server Software.
Figure 3-1
Connecting optional SunRay DTU to Netra210 using a direct connection
ti-gsm_Connecting_optional_SunRay DTU_to_Netra210-0022-ai-sw
3-26
68P02901W47-S
Jul 2008
Figure 3-2
Preparation procedure
Connecting optional SunRay DTU to Netra210 using a VLAN
First free ethernet port bge1
Netra 210 backplane
Switch
Sun Ray DTU
ti-gsm-Connecting_S unRa y DTU to Ne tra 210 _ VLAN_00081-a i-sw
NOTE
The Virtual Local Area Network (VLAN) used for connecting the Netra 210 GUI
server and the SunRay DTU is dedicated and configured to carry network traffic
between the Netra 210 GUI server and the SunRay DTU only.
For additional information, refer to the relevant documentation from SUN

Microsystems for the deployment of SunRay DTU's using a VLAN.
Prepare the system for the SunRay Server Software installation by performing the following
steps on the Netra210:
Procedure 3-6
68P02901W47-S
Login as user root.
If there is a disk in the DVD drive, execute the following commands:

cd /
eject cdrom
3-27
Jul 2008
Installing SunRay Server Software

Insert the SunRay Server Software into the DVD drive on the Netra210.
Install the SunRay Server Software by performing the following steps on the Netra210:
Procedure 3-7
Change to the image directory.

cd /cdrom/cdrom0
Install SunRay Server Software by executing the following command:

/utinstall
The script prompts you to accept the license for the software.
Enter the location of the Java JRE 1.4.2 or later. The default location is
/usr/j2se
The script prompts you for a confirmation before it installs the required
software products and any necessary patches. After the completion of the
installation, reboot the system.
Preparing for Configuration of the SunRay Server

Before configuring the SunRay Server perform the following steps:
Verify that the file /etc/hosts is a soft link to /etc/inet/hosts.
Copy /usr/dt/config/Xservers to /etc/dt/config/Xservers.SUNWut.prototype. This

may have to be customized later.
Configuring the SunRay Server

Procedure 3-8
Login as user root.
Execute the following commands:

cd /opt/SUNWut/sbin
./utadm -a bgeX
where X is the spare Ethernet ports 1,2,3 to which the SunRay has been
connected.
Continued
3-28
68P02901W47-S
Jul 2008
Procedure 3-8
68P02901W47-S
Jul 2008
Configuring the SunRay Server (Continued)
The utadm script begins configuring DHCP for the SunRay interconnect,
starts the DHCP daemon, and configures the interface. The script then lists
the default values and asks if they are acceptable. If you are satisfied with
the default values answer Y and skip to step 5.
Otherwise, answer N and provide the correct values. The utadm script
configures the SunRay DTU firmware versions and starts the DHCP
daemon. Answer Y if prompted to start DHCP.
Execute the following commands:

cd /opt/SUNWut/bin
./utxconfig -a -p default
Reboot the Gui Server using the following command as user root:
/usr/sbin/shutdown i6 g0 -y
3-29
3-30
68P02901W47-S
Jul 2008
Chapter
4
GUI Client Configuration
68P02901W47-S
Jul 2008
4-1
GUI client installation
GUI client installation
Introduction
Refer to the relevant GSM OMC-R Release Notes for installation instructions specific to this
release.
NOTE
The GUI client architecture has changed in GSR 9. GUI clients now act as display
terminals using the Solaris 10 Remote Login feature to access the GUI server. This
speeds up GUI client clean installs for supported platforms. Alternatively, it allows
customers to use any SUN platform as a GUI client, as long as it meets the minimum
hardware specification.
The following supported platforms have Motorola customized Jumpstart CDs provided to speed
up the operating system installation:
Sunblade 150.
Refer to Customized Jumpstart procedures on page 4-3 to Jumpstart these platforms.

Any other Sun platform satisfying the following minimum specification can be set up as a GUI
client by a skilled system administrator:
Processor Speed
Memory
Hard Disk Size
Graphics Card
270 MHz
128 MB RAM
4 GB
Required
Go to SUN Jumpstart procedures on page 4-5 to Jumpstart these other platforms.
4-2
68P02901W47-S
Jul 2008
Customized Jumpstart procedures
Customized Jumpstart procedures
Running Jumpstart
NOTE
Use these procedures if you are Jumpstarting a Sunblade 150 GUI Client.
The Jumpstart procedure is used for installing Solaris 10, all system patches, CDE and Solstice
Backup (client edition) on the GUI client. The procedure is as follows:
Procedure 4-1
Jumpstart for GUI client

reset-all
Enter the following command at the OK> prompt to check that the system is
configured correctly:
probeide
Place the Sunblade GUI client Jumpstart DVD into the CD-ROM drive and
enter the following command:
boot cdrom
press Return.
NOTE
A host name must be at least two characters; it can contain
letters, digits and minus signs (). Letters must be lower case.
Illegal characters are: !$%^&*(){}~@?>:<|.[]_.
5
A prompt is displayed requiring the IP address to be entered. Enter the

address, followed by Return.
A prompt is displayed requiring the Netmask address to be entered. Enter

the address, followed by Return.
A hands-free customized installation of Solaris 10 on the Sunblade and all

Solstice products is now performed on this machine. Once the products are
installed, the machine is automatically rebooted.
Continued
68P02901W47-S
4-3
Jul 2008
Running Jumpstart
Procedure 4-1
Jumpstart for GUI client (Continued)
NOTE
The log files for this section can be found in
/var/tmp/JumpStart/logs.
Follow the procedure Modify files on page 3-18 .
NOTE
Errors of the form:
pkgadd:ERROR:no package associated with <SUNWxxx>
occurring in /var/tmp/JumpStart/logs/install_log can be
safely ignored.
4-4
68P02901W47-S
Jul 2008
SUN Jumpstart procedures
Procedure
NOTE
Use this procedure if you are clean installing a GUI client on a SUN platform
other than a Sunblade 150.
This procedure does not contain all the steps necessary to install the Solaris 10
operating system manually.
It is assumed that this procedure is being carried out by a skilled system

administrator familiar with the Solaris 10 operating system clean install
procedure using media provided by SUN.
Procedure 4-2
68P02901W47-S
Install the latest release of the Solaris 10 operating system using the
Solaris 10 media provided by SUN, ensuring that the platform is set up
for networking. Any reasonable file system layout is acceptable including
auto-layout.
On Solaris 10 systems, insert the patches CD into the GUI

client platform and as user root, run the following commands:
cd /cdrom/sol8_patches/GUI_Client
patchadd 108919-17
4-5
Jul 2008
Performance problem with GUI clients
Performance problem with GUI clients

If the LAN connecting the GUI client is a 100 Mbps full-duplex network (check with the Network
System Administrator), then the GUI client may experience performance issues. Ignore this
section if the LAN is not 100 Mbps full-duplex.
To check for performance issues on a Sunblade, as user root, enter the following command:
dmesg | grep eri | grep duplex
To check for performance issues on an Ultra, as user root, enter the following command:
dmesg | grep hme | grep Duplex
If the output of this command shows a 100 Mbps full duplex link up,
then there is no performance problem and the rest of this section may
be ignored. In this case, the output looks similar to the following:
Sunblade:
Mar
3 19:53:33 sunblade3 eri: [ID 517527 kern.info] SUNW,eri0: 100 Mbps
full duplex link up

Ultra:
Jul 15 10:00:54 somc49 hme: [ID 517527 kern.info] SUNW,hme0: AutoNegotiated 100 Mbps Full-Duplex Link Up
If the output of this command shows a 100 Mbps half-duplex link up, then there is a
problem with the performance that has to be resolved as per the section Fixing the
performance problem on page 4-7. In this case, the output looks similar to the following:
Sunblade:
Mar
3 19:50:04 sunblade3 eri: [ID 517527 kern.info] SUNW,eri0: 100 Mbps
half duplex link up

Ultra:
Jul 15 10:00:54 somc49 hme: [ID 517527 kern.info] SUNW,hme0: AutoNegotiated 100 Mbps Half-Duplex Link Up
4-6
68P02901W47-S
Jul 2008
Fixing the performance problem

Follow Procedure 4-3 to resolve performance issues:
Procedure 4-3
Log in as user root.
Using a text editor on a Sunblade, append the following lines to the file
/etc/system:
set eri:adv_autoneg_cap=0
set eri:adv_100T4_cap=0
set eri:adv_100fdx_cap=1
set eri:adv_100hdx_cap=0
set eri:adv_10fdx_cap=0
set eri:adv_10hdx_cap=0
Using a text editor on an Ultra, append

the following lines to the file /etc/system:
set hme:hme_adv_autoneg_cap=0
set hme:hme_adv_100T4_cap=0
set hme:hme_adv_100fdx_cap=1
set hme:hme_adv_100hdx_cap=0
set hme:hme_adv_10fdx_cap=0
set hme:hme_adv_10hdx_cap=0
Reboot the system by running the following command:

/usr/sbin/shutdown i6 g0 y
As user root, on a Sunblade run the command:

dmesg | grep eri | grep duplex
Continued
68P02901W47-S
4-7
Jul 2008
Moving a machine with a modified /etc/system file
Procedure 4-3
6
Fixing the performance problem (Continued)
As user root, on an Ultra run the command:

dmesg | grep hme | grep Duplex
Output similar to the following should be displayed illustrating that a
100 Mbps full-duplex link is the most recently activated link:
Sunblade:
Mar
3 19:50:04 sunblade3 eri: [ID 517527 kern.info] SUNW,eri0:
100 Mbps half duplex link up

Mar
3 19:53:33 sunblade3 eri: [ID 517527 kern.info] SUNW,eri0:
100 Mbps full duplex link up

Ultra:
Jul 15 10:00:54 somc49 hme: [ID 517527 kern.info] SUNW,hme0:
Auto-Negotiated 100 Mbps Half-Duplex Link Up
Jul 15 10:00:54 somc49 hme: [ID 517527 kern.info] SUNW,hme0:
Auto-Negotiated 100 Mbps Full-Duplex Link Up
Moving a machine with a modified /etc/system file

The fix for the performance problem described above means that the GUI client platform no
longer auto-negotiates the network speed. If the GUI client platform is moved in the future to a
network port, which is not 100 Mbps full duplex, the GUI client may not be able to connect to
the network without removing the appended lines from /etc/system.
4-8
68P02901W47-S
Jul 2008
Configuring the GUI client
Configuring the GUI client
GUI client files to be modified

The procedures outlined in this section describe how to modify the following system files:
/etc/hosts
/etc/defaultrouter
Through the remainder of this chapter, the following names are used to represent hostnames
where applicable:
<guiserver1> GUI Server Processor hostname.
<guiclient1> GUI Client Processor hostname.
Only the root user can modify the files shown in this section.
Setting root password

The following procedure describes how to set a root account password on initial login:
Procedure 4-4
Setting root password
Login as root (if not already logged in as root).
Ensure that the root account has a password set. The password is required
after installing the Solaris. Right click on the mouse, select Programs, and
then Console to open the console window. Set the password by entering the
following command at the # prompt followed by the root password:
passwd
The following prompts are displayed:
New password:
Re-enter new password:
Enter the new password at both prompts.
NOTE
The password is not echoed when entered in.
68P02901W47-S
4-9
Jul 2008

The /etc/hosts file is used to store the Internet Protocol (IP) addresses and the system names of
the systems accessible on the network.
Add entries shown in the example to the /etc/hosts file using a text editor so that the systems
are recognized by the software as user root.
Entries shown for the /etc/hosts file are:
guiclient1 guiclient1.domainname loghost
111.111.111.12
guisever1
NOTE
If there is more than one GUI server entry in the /etc/hosts file of the GUI
client, then switching the GUI client from one GUI server to another is achieved
by remote logging out of one GUI server and logging into another remotely.
It may be necessary to do a forced write to save /etc/hosts after editing due to

its write permissions. In the vi editor, this is achieved with the wq!command.
Modifying the /etc/defaultrouter

The following procedure describes the steps for modifying the /etc/defaultrouter:
Procedure 4-5
Modifying the /etc/defaultrouter
Create a file called /etc/defaultrouter that contains the IP address of the

default router in the form: nnn.nnn.nnn.nnn
Reboot the GUI client as follows:

/usr/sbin/shutdown i6 g0 y
The following reboot messages can be ignored:
nfs mount: omc_splat:: RPC: Unknown host
nfs mount: gui_server:: RPC: Unknown host
nfs mount: gui_server:: RPC: Unknown host
Accessing the GUI server

The following procedure describes the steps for accessing the GUI server:
4-10
68P02901W47-S
Jul 2008
Procedure 4-6
From the GUI client graphical CDE login screen, select:

Options Remote Login Enter Host Name.
Figure 4-1
GUI client Graphical CDE login screen
ti-gsm_Ultra_5_GUI_client_Graphical_CDE_login_screen-0023-ai-sw
Enter the hostname of a GUI server that exists in the /etc/hosts file of
the GUI client and select OK. The GUI server graphical CDE login screen
is similar to Figure 4-2 below. Login as omcadmin and the OMC-R GUI is
started automatically.
Figure 4-2
GUI server Graphical CDE login screen
ti-gsm_GUI_server_Graphical_CDE_login_screen-0024-ai-sw
68P02901W47-S
Jul 2008
4-11
4-12
68P02901W47-S
Jul 2008
Chapter
5
On-site Requirements and Verification
68P02901W47-S
Jul 2008
5-1
Introduction to requirements and verification
Introduction to requirements and verification
OMC-R equipment requirements

This chapter contains the on-site power, environmental, space requirements, weight, and
dimensional information for the following Motorola OMC-R equipment:
Sun Netra 20
Sun Netra 440
Sun Sunfire 4800/4900
Sun Sunblade 150
Sun Netra 210
Cisco 3662 Router
Cisco 3845 Router
Ensure that the necessary sites and facilities are available before on-site installation of the
OMC-R begins.
The requirements detailed in this chapter are as follows:
Power and environmental requirements: Describes the power requirements for

the Sun and Motorola equipment. Describes the temperature, humidity, and altitude
requirements for the OMC-R site.
Space, weight, and dimensional information: Describes the space requirements,

weight, and dimensional information for the Sun and Motorola equipment.
On-site verification
This chapter also describes the on-site verification procedures. It is assumed that the hardware
has been interconnected, the site has been prepared and the software has been installed on
the processors.
The verification procedures detailed in this chapter are as follows:
5-2
Single Platform Processor verification: Describes how to carry out the verification
procedure following installation of the Single Platform Processor.
SPARCstation verification: Describes how to carry out the verification procedure

following installation of a SPARCstation Ultra 5/Sunblade 150/Netra 210.
Network verification: Describes how to confirm that it is possible to communicate with

all devices on the LAN by using the ping command. Describes how to verify that the Sun
SPARC stations can communicate with all of the other processors on the LAN.
Start up sequences: Describes how to start up the Single Platform Processor.

68P02901W47-S
Jul 2008
Manufacturer-specific information
Manufacturer-specific information
For detailed site requirement information specific to each piece of equipment, consult the
manufacturers documentation supplied with the equipment. Relevant manuals may include:
Sun Netra T4 AC100/DC100 Installation and Users Guide
Sun Netra 440
Sun SunFire 6800/4810/4800/4900/3800 Systems Site Planning Guide
Sun Sunblade 150 System Installation Guide
Sun Netra 210 Server Setting Up Guide
Cisco 3662 Hardware Installation Guide
Cisco 3485 Hardware Installation Guide
68P02901W47-S
5-3
Jul 2008
Power and environmental requirements
Power and environmental requirements
Introduction to power and environmental requirements

The site selected for the OMC must meet the power requirements for the installation of the
OMC-R equipment.
The site must also meet the temperature, humidity, and altitude requirements listed in this
section. The values presented here represent the minimum and maximum conditions for all
the equipment.
Power requirements for specific OMC-R equipment

Table 5-1 details the voltage input range and maximum current specifications for specific Sun
and ING equipment.
Table 5-1
Power requirements for OMC-R equipment

Equipment
Valid input
Default
Sun
20 or 21 inch colour
monitor
100 to 120 Vac, 60 Hz

220 to 240 Vac, 50 Hz
3.0 A
2.0 A
Sun
SunFire 4800/4900
200 to 240 Vac, 47 to

63 Hz
16 A
Sun
Netra 20
90 to 240 Vac, 47 to
63 Hz
7.2 A
Sun
Netra 440
100 to 264 Vac, 47 to

63 Hz
7.2 A
Sun
Sunblade 150
100 to 120 or 220 to

240 Vac, 47to 63 Hz
0.3 K VA
Sun
Netra 210
100 to 240 Vac, 48-60

VDC
4.6 A
Sun
4mm DAT drive
100 to 120 Vac, 60 Hz

200 to 240 Vac, 50 Hz
0.8 A
0.4 A
Wyse
WY - 120
120 to 230 Vac
0.3A
Cisco
3662 Router
100 to 240 VAC, auto

ranging
3.0 A
Power supply circuits

The power supply circuits for the Sun, Motorola, and Cisco machines are as follows:
All equipment must be on separate power circuits.
5-4
68P02901W47-S
Jul 2008
Temperature
Temperature
The worst-case temperature requirements for the site selected for the OMC are as follows:
Operating
+10C to 38C
Storage
-4C to +55C
Maximum gradient
11C per hour
Humidity
The worst-case humidity requirements for the site selected for the OMC are as follows:
Operating
10% to 80%
non-condensing
Storage
10% to 95%
non-condensing
Altitude
The worst-case altitude requirements for the site selected for the OMC are as follows:
Operating
0 to 3048 m
Storage
0 to 15240 m
Maximum gradient
12190 meter per 20 minutes
68P02901W47-S
5-5
Jul 2008
Space: weight and dimensional information
Outline of space: weight and dimension information

The following sections outline the space requirements, weight, and dimensional information,
specific to each piece of OMC-R equipment:
Single Platform Processor - Sun Netra 20
Single Platform Processor - Sun Netra 440
Single Platform Processor - Sun SunFire 4800/4900
Sun Sunblade 150
Sun Netra 210
SPARC storage multipack
ISG Equipment (optional)
Cisco 3662 Router
Cisco 3845 Router
Single platform processor data Sun Netra 20

This section outlines the space requirements, weight, and dimensions of a Sun Netra 20 Single
Platform Processor.
5-6
68P02901W47-S
Jul 2008
Positioning and clearance

Figure 5-1 shows the front view of a Sunblade 20. An external Sun StorEdge disk array is
required and is shown.
Position the equipment to allow sufficient clearance for the air vents, when both the DVD-ROM
drive and the access door are fully open.
Figure 5-1
Front view of Sun Netra 20
ti-gsm_Front view of Sun Netra 20-0027-ai-sw
68P02901W47-S
5-7
Jul 2008
Weight and dimensional information

The weight of a standard Sun Netra 20 is 27.3 kg. Figure 5-2 shows the overall dimensions of a
Sun Netra 20.
Figure 5-2
177 MM
Sun Netra 20 dimensions
MO NT
435 MM
508 MM
TOP
ti-gsm_Sun_Netra_20_dimensions-0028-ai-sw

This section outlines the space requirements, weight, and dimensions of a Sun Netra 440
Single Platform Processor.
5-8
68P02901W47-S
Jul 2008

Figure 5-3 shows the front view of a Netra 440. An external Sun StorEdge disk array is required
and is shown.
drive and the access door are fully open.
Figure 5-3
Front view of Sun Netra 440
ti-gsm_Front_view_of_Sun_Netra_440-0029-ai-sw
68P02901W47-S
5-9
Jul 2008

The weight of a standard Sun Netra 440 is 36 kg. Figure 5-4 shows the overall dimensions
of a Sun Netra 440.
Figure 5-4
Sun Netra 440 dimensions
ti-gsm_Sun_Netra_440_dimensions-0030-ai-sw
5-10
68P02901W47-S
Jul 2008

This section outlines the space requirements, weight, and dimensions of a Sun SunFire
4800/4900 Single Platform Processor.

Figure 5-5 shows the front view of a Sun SunFire 4800/4900 in its cabinet. The cabinet contains
the SunFire 4800/4900, a StorEdge 3310 Disk Array and an external media drive unit containing
a DVD player and a tape drive.
drive and the access door are fully open. There should also be sufficient space at the rear
of the cabinet.
Figure 5-5
Front view of Sun SunFire 4800/4900
ti-gsm_Front_view_of_Sun_SunFire_4800/4900-0031-ai-sw
68P02901W47-S
5-11
Jul 2008

The weight of a standard Sun SunFire 4800/4900 is 125 kg. Figure 5-6 shows the overall
dimensions of a Sun SunFire 4800/4900.
Figure 5-6
Sun SunFire 4800/4900 dimensions

446 MM
724 MM
762 MM
TOP
FRONT
ti-gsm_Sun_SunFire_4800/4900_dimensions-0032-ai-sw
5-12
68P02901W47-S
Jul 2008
Sun Sunblade 150
Sun Sunblade 150

This section outlines the space requirements, dimensions, and weight of a Sunblade 150.

Figure 5-7 shows the front view of a Sunblade 150. Provision for the use of floppy disks and
DVDs/CD-ROMs is provided on the front of the system.
Position the equipment such that there is sufficient clearance for the air vents, fan, DVD-ROM
drive bay, and access to the FDD.
Figure 5-7
68P02901W47-S
Front view of a Sunblade 150
5-13
Jul 2008
Sun Netra 210

The weight of a Sunblade 150 is 12.2 kg. Figure 5-8 shows the overall dimensions of a Sunblade
150.
Figure 5-8
Sunblade 150 dimensions
ti-gsm_Sunblade_150_dimensions-0036-ai-sw
Sun Netra 210

This section outlines the space requirements, dimensions, and weight of a Netra 210.

Figure 5-9 shows the front view of a Netra 210.
Position the equipment such that there is sufficient clearance for the air vents, fan, DVD-ROM
drive bay, and access to the FDD.
Figure 5-9
Front view of a Netra 210
ti-gsm_Front_view_of_a_Netra_210-0077-ai-sw
5-14
68P02901W47-S
Jul 2008
Sun Netra 210

The weight of a Netra 210 is 9.8 kg fully configured with DVD and rackmount kit, not including
PCI card.
Figure 5-10 shows the overall dimensions of a Netra 210.
Figure 5-10
Netra 210 dimensions
ti-gsm_Netra_210_dimensions-0078-ai-sw
68P02901W47-S
5-15
Jul 2008
Cisco 3662 Router
Cisco 3662 Router

This section outlines the space requirements, dimensions, and weight of a Cisco 3662 Router.

Figure 5-11 shows a Cisco 3662 Router. Space is required at the rear of the router for fan
clearance and access to cables.
Figure 5-11
Cisco 3662 Router
ti-gsm_Cisco_3662_Router-0041-ai-sw
5-16
68P02901W47-S
Jul 2008
Cisco 3662 Router

The weight of a Cisco 3662 Router is 22.8 kg. Figure 5-12 shows the overall dimensions of a
Cisco 3662 Router.
Figure 5-12
Cisco 3662 Router dimensions
ti-gsm_Cisco_3662_Router_dimensions-0042-ai-sw
68P02901W47-S
5-17
Jul 2008
Single Platform Processor verification
Single Platform Processor verification procedures

Carry out the following procedures after the installation of the Single Platform Processor:
Check equipment received: Describes how to use the bill of materials to check all
equipment.
Before power-up: Describes visual checks before power-up.
Checking disk mirrors: Describes how to check that the disk mirrors are operating
correctly.
Tape drives check procedure: Describes how to verify that files can be archived to
the tape drive.
Operating system version verification: Describes how to provide verification of the

Single Platform Processor operating system.
X.25 version verification: Describes how to provide verification of the X.25 version.
OMC-R software version verification: Describes how to provide verification of the

OMC-R software version.
Check equipment received

Using the BOM (Bill of Materials), check that all the equipment, software, and documentation
on the BOM are present. Take care to check the software versions on the tapes against the
required versions on the BOM. Use the software compatibility matrix to verify the correct
versions of the software.
Before power-up
Before commencing power-up, proceed as follows:
5-18
Visually check that all equipment is undamaged after transit.
Check all equipment to ensure compatibility with the local power supply.
Ensure that a UPS is available for all power connections.
68P02901W47-S
Jul 2008
Checking disk mirrors

Use the following procedure to check that the disk mirrors are operating correctly:
Procedure 5-1
Login to the Single Platform Processor as root.
Check the status of the database replicas by entering:

/usr/sbin/metadb -i
The database replicas should appear similar to:
flags
a m
luo
first blk
block count
16
8192
16
8192
16
8192
16
8192
16
8192
16
8192
16
8192
16
8192
16
8192
16
8192
/dev/dsk/c0t8d0s7
a
luo
/dev/dsk/c1t8d0s7
a
luo
/dev/dsk/c0t9d0s7
a
luo
/dev/dsk/c1t9d0s7
a
luo
/dev/dsk/c0t10d0s7
a
luo
/dev/dsk/c1t10d0s7
a
luo
/dev/dsk/c0t11d0s7
a
luo
/dev/dsk/c1t11d0s7
a
luo
/dev/dsk/c0t12d0s7
a
luo
/dev/dsk/c1t12d0s7
r - replica does not have device relocation information
o - replica active prior to last mddb configuration change
u - replica is up to date
l - locator for this replica was read successfully
c - replica's location was in /etc/lvm/mddb.cf
p - replica's location was patched in kernel
Continued
68P02901W47-S
5-19
Jul 2008
Procedure 5-1
Checking disk mirrors (Continued)
m - replica is master, this is replica selected as input

W - replica has device write errors
a - replica is active, commits are occurring to this replica
M - replica had problem with master blocks
D - replica had problem with data blocks
F - replica had format problems
S - replica is too small to hold current data base
R - replica had device read errors
#
3
Verify the disk mirrors by checking the status of the metadevices by entering:
/usr/sbin/metastat
Metamirror output
For each metamirror, there is output similar to:
d20: Mirror
Submirror 0: d100
State: Okay
Submirror 1: d101
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 262960 blocks
d100: Submirror of d20
State: Okay
Size: 262960 blocks
Stripe 0:
Device
c1t2d0s0
5-20
Start Block
0
Dbase State
No
Hot Spare
Okay
68P02901W47-S
Jul 2008
Tape drive check procedure
d101: Submirror of d20

State: Okay
Size: 262960 blocks
Stripe 0:
Device
Start Block
c0t2d0s0
Dbase State
No
Hot Spare
Okay
For each metadevice and metamirror, check that its state is okay.
If the mirror check is unsuccessful refer to the Troubleshooting chapter of the Motorola
manual Operating Information: OMC-R System Administration (68P02901W19).

Use the following procedure to verify that files can be archived to the tape drive, and that the
archived files can be restored successfully:
Procedure 5-2
Insert a blank tape into the DAT drive.
Login as root on the Single Platform Processor and create a tape archive as
follows:
tar -cvf /dev/rmt/0 /tmp
Verify that the tape can be read as follows:

tar -tvf /dev/rmt/0
Operating system version verification

The following procedure outlines how to provide verification of the Single Platform Processor
operating system:
Procedure 5-3
Single Platform Processor operating system version verification
Login to the Single Platform Processor as root and enter the following
commands:
cd /
showrev
The Single Platform Processor replies with a message identifying the Kernel
version.
68P02901W47-S
Confirm that the version is Solaris 10. If the version is different, the
operating system should be upgraded using the relevant procedure in the
Software Installation section of this manual and the current GSM OMC-R
Software Release Notes.
5-21
Jul 2008
X.25 version verification

The following procedure outlines how to provide verification of the X.25 version:
Procedure 5-4
Login at the Single Platform Processor as root and enter the following
commands:
cd /opt/SUNWconn/bin
./x25tool
The x25tool starts and the version of the tool appears at the top of the main
x25tool window.
Confirm that the version is X.25 9.2. If the version is different, the X.25
version should be updated using the relevant procedure and the current
Software Release Notes.
OMC-R software version verification

The following procedure outlines how to provide verification of the OMC-R software version:
Procedure 5-5
OMC-R software version verification
Login to the Single Platform Processor as root and enter the following
commands:
cd /usr/omc/current/bin
/usr/ccs/bin/what -s omcinit
The Single Platform Processor replies with a message similar to the
following:
omcinit:
OMC Product version 1.9.*.*.xx Copyright 2004, Motorola Inc
#
5-22
Confirm that the OMC-R product version is correct. If the version is

incorrect, the OMC-R version should be updated using the procedure
outlined in the current Software Release Notes.
68P02901W47-S
Jul 2008
GUI server/client verification
GUI server/client verification
Introduction
This section describes the installation and verification procedures for the following:
Sunblade
Netra 210
NOTE
Unpack and label all Sun Manuals before unpacking the Sun equipment. Confirm all
the manuals have been delivered with the BOM.
Sunblade verification
This paragraph outlines the installation and verification procedures for a Sunblade workstation.
Before beginning the hardware installation, read the Setting up the Sunblade 150
Workstation chapter of the Sunblade 150 Getting Started Guide. Use the following procedure
to power up a Sunblade SPARCstation:
NOTE
Connect the Sunblade workstation to the LAN before it is powered up as described in
Chapter 2 Operating System and OMC-R Software Installation on the Single Platform
Processor of this manual.
Procedure 5-6
Sunblade verification
Power up the monitor following the instructions in the guide supplied with
the monitor, and power up the system unit. When the Sunblade workstation
is powered up, it follows a self-test routine controlled by the boot PROM.
The monitor remains blank until the self-test has been completed. The boot
sequence then begins and text similar to the following is displayed:
Continued
68P02901W47-S
5-23
Jul 2008
Netra verification
Procedure 5-6
Sunblade verification (Continued)
Sunblade 150 (UltraSPARC-IIe 650MHz) Keyboard Present

Openboot 4.6, 512 MB memory installed, Serial #99999.
Ethernet address 8:0:20:9:aa:00, Host ID: 5300a0b1.
2
Check whether there is at least 512 MB of memory installed. If

there is less than 512 MB of memory installed, more SIMMs has to
be installed. Boot messages are displayed on the monitor similar to
those shown in GUI server startup sequence. The boot sequence
terminates with a login prompt, which includes the hostname, as follows:
guiserv2 login:
Netra verification
This paragraph outlines the installation and verification procedures for a Netra workstation.
Before beginning the hardware installation, read the Netra 210 Server Setting Up Guide. Use
the following procedure to power up a Netra 210:
NOTE
Connect the Netra 210 workstation to the LAN before it is powered up as described
in Chapter 2 Operating System and OMC-R Software Installation on the Single
Platform Processor of this manual.
Procedure 5-7
Netra 210 verification
Power up the monitor following the instructions in the guide supplied with
the monitor, and power up the system unit. When the Netra 210 workstation
is powered up, it follows a self-test routine controlled by the boot PROM.
The monitor remains blank until the self-test has been completed. The boot
sequence then begins and text similar to the following is displayed:
SPARCstation 200E, keyboard present.
ROM Rev. 2.9, 256 MB memory installed, Serial #99999.
Ethernet address 8:0:20:9:aa:00, Host ID: 5300a0b1
5-24
Check whether there is at least 512 MB of memory installed. If

there is less than 512 MB of memory installed, more SIMMs has to
be installed. Boot messages are displayed on the monitor similar to
those shown in GUI server startup sequence. The boot sequence
terminates with a login prompt, which includes the hostname, as follows:
guiserv2 login:
68P02901W47-S
Jul 2008
Network verification
Network verification
Introduction to network verification

To verify that the network connections are functioning, perform the following procedures:
Verify communication with devices on LAN. Ping all network devices.
Verify secure login. Attempt to log into all network processors and, if any login fails,
identify the cause of failure.
Check users. Ensure that all users are added to the Single Platform Processor and to
all the GUI servers.
Verify communication with devices on LAN

From the Single Platform Processor, Sunblade or Netra 210, confirm that it is possible to
communicate with all devices on the LAN by using the ping command as follows:
ping <hostname>
Where:
<Hostname>
Is:
The hostname of another processor
on the LAN.
or
ping <IP address>
Where:
<IP Address>
Is:
The internet address of another LAN
processor.
Example response:
mib1 is alive
Verify remote login

Follow the steps in Procedure 5-8 to verify that the Sunblade or Netra 210 can communicate
with all of the other processors on the LAN.
68P02901W47-S
5-25
Jul 2008
Check users
Procedure 5-8
Remote login verification
Login to one of the Sunblade/Netra210 as omcadmin.
Select New Window from the CDE background menu and attempt
to login to each of the processors on the LAN using the command:
ssh l <username> <hostname>
If the remote login is unsuccessful, check the Ethernet cable connections,
check that the host chosen is powered-up, and finally check the system files
containing the host names and Internet addresses.
Work through all of the OMC-R applications on the OMC-R 1.9.*.* GUI
ensuring that all are operating correctly.
NOTE
If a connection has not yet been made to any of the network elements through the
X.25 network, then applications that require communication with an NE do not work.
The PM statistics report application does not work until the first set of BSS statistics
have been uploaded into the database.
Check users
Add all users to the Single Platform Processor and to all the GUI servers. Check the /etc/group
and /etc/passwd files on each of the processors as follows:
Procedure 5-9
Check users
Login to one of the GUI servers as root.

Open a command window for each of the GUI servers and the Single Platform
Processor and login to each processor by entering the following command:
ssh l <username> <hostname>
Use the cat command to compare the /etc/group files on each processor as
follows:
cat /etc/group
The last three group entries displayed following the cat /etc/group command
should be as follows:
informix::109:
omc::110:
omcread::111:
Ensure that the group IDs are the same on all processors. If necessary, use
a text editor to modify the entries.
Continued
5-26
68P02901W47-S
Jul 2008
Procedure 5-9
3
Check users
Check users (Continued)
Use the cat command to compare the /etc/passwd files on each processor
as follows:
cat /etc/passwd
The informix, omcadmin, and any other user entries that have been added
should be similar to the following:
root:x:0:1:Super-User:/:/sbin/sh
daemon:x:1:1::/:/dev/null
bin:x:2:2::/usr/bin:/dev/null
sys:x:3:3::/:
adm:x:4:4:Admin:/var/adm:/dev/null
informix:x:109:109:Informix Administrator:/usr/informix:/bin/csh
omcadmin:x:110:110:OMC Administrator:/home/omcadmin:/bin/csh
omcread:x:111:111:OMC read account:/home/omcread:/bin/csh
jimmy:x:500:110::/home/jimmy:/bin/csh
Ensure that for each user there is a password entry and that the user
ID numbers and group ID numbers are the same on all processors. The
password, userid and groupid entries are the first, second and third entries
on each line following the userid. If necessary, use a text editor to modify
the entries on the SPARCstations and on the Single Platform Processor.
68P02901W47-S
Logout from each processor.
5-27
Jul 2008
Startup sequences
Startup sequences
Introduction
This section describes the messages that are displayed on the console during system startup for
the Single Platform Processor and the GUI server.
Single Platform Processor startup sequence

The startup sequence messages similar to those shown in the following example are displayed
on a SunFire 4900 console during power-up:
ok boot
Resetting...
{/N0/SB0/P0/C1} @(#) lpost
5.20.3
2006/10/21 06:21
{/N0/SB0/P0/C1} Copyright 2006 Sun Microsystems, Inc.
{/N0/SB0/P0/C1} Use is subject to license terms.

{/N0/SB0/P1/C1} @(#) lpost
5.20.3
2006/10/21 06:21

{/N0/SB0/P2/C1} @(#) lpost
5.20.3
2006/10/21 06:21

{/N0/SB0/P3/C1} @(#) lpost
5.20.3
2006/10/21 06:21

Copying IO PROM to CPU DRAM
.{/N0/SB0/P0/C0} @(#) lpost
5.20.3
2006/10/21 06:21

{/N0/SB0/P1/C0} @(#) lpost
5.20.3
2006/10/21 06:21
.{/N0/SB0/P1/C0} Copyright 2006 Sun Microsystems, Inc.
.{/N0/SB0/P1/C0} Use is subject to license terms.

.........................................
{/N0/SB0/P0/C0} Running PCI IO Controller Basic Tests
{/N0/SB0/P0/C0} Jumping to memory 00000000.00000020 [00000010]
{/N0/SB0/P0/C0} System PCI IO post code running from memory
{/N0/SB0/P0/C0} @(#) lpost
5.20.3
2006/10/21 06:32
{/N0/SB0/P0/C0} Running PCI IO Controller Functional Tests

5-28

68P02901W47-S
Jul 2008

{/N0/SB0/P0/C0} Subtest: PCI IO Controller Register Initialization for aid 0x18
{/N0/SB0/P0/C0} Running PCI IO Controller Ecc Tests
{/N0/SB0/P0/C0} Running SBBC Basic Tests
{/N0/SB0/P0/C0} Subtest: SBBC PCI Reg Initialization for aid 0x18
{/N0/SB0/P0/C0} Running Probe io Devices
{/N0/SB0/P0/C0} Subtest: PCI IO Controller Register Initialization for aid 0x19
{/N0/SB0/P0/C0} @(#) lpost
5.20.3
2006/10/21 06:21

{/N0/SB0/P0/C1} @(#) lpost
5.20.3
2006/10/21 06:21

{/N0/IB6/P0} Passed
{/N0/IB6/P1} Passed
Copying IO PROM to CPU DRAM
............................................
{/N0/SB0/P0/C0} Jumping to memory 00000000.00000020 [00000010]
{/N0/SB0/P0/C0} System PCI IO post code running from memory
{/N0/SB0/P0/C0} @(#) lpost
5.20.3
2006/10/21 06:32


{/N0/SB0/P0/C0} Subtest: PCI IO Controller Register Initialization for aid 0x1c
{/N0/SB0/P0/C0} Running SBBC Basic Tests
{/N0/SB0/P0/C0} Subtest: SBBC PCI Reg Initialization for aid 0x1c
{/N0/SB0/P0/C0} Subtest: PCI IO Controller Register Initialization for aid 0x1d
{/N0/SB0/P0/C0} @(#) lpost
5.20.3
2006/10/21 06:21

{/N0/SB0/P0/C1} @(#) lpost
68P02901W47-S
5.20.3
2006/10/21 06:21
5-29
Jul 2008

{/N0/IB8/P0} Passed
{/N0/IB8/P1} Passed
{/N0/SB0/P0/C0} Running Domain Level Tests
{/N0/SB0/P2/C0} @(#) lpost
5.20.3
2006/10/21 06:21
{/N0/SB0/P3/C0} @(#) lpost
5.20.3
2006/10/21 06:21
{/N0/SB0/P0/C0} Running Domain Basic Tests

{/N0/SB0/P0/C0} Running Domain Advanced Tests
{/N0/SB0/P0/C0} Running Domain Stick Sync Tests
{/N0/SB0/P0/C0} Running Domain Verify Stick Sync Tests
{/N0/SB0/P0/C0}
DCB_DECOMP_OBP command succeeded
{/N0/SB0/P0/C0} Committing retained memory 00000000.00970000-00000000.00971fff

{/N0/SB0/P0/C0} Retaining 00000000.00970000-00000000.00971fff
{/N0/SB0/P0/C0} Committing retained memory 00000000.00996000-00000000.00997fff
{/N0/SB0/P0/C0} Retaining 00000000.00996000-00000000.00997fff
{/N0/SB0/P0/C0}
CORE 1 clearing 00000000.00000000 to 00000000.0025c000
{/N0/SB0/P0/C0}
CORE 2 clearing 00000000.0025c000 to 00000000.004b8000
{/N0/SB0/P0/C0}
CORE 3 clearing 00000000.004b8000 to 00000000.00714000
{/N0/SB0/P0/C0}
CORE 0 clearing 00000000.00714000 to 00000000.00970000
{/N0/SB0/P0/C0}
CORE 1 clearing 00000000.00972000 to 00000000.0097b000
{/N0/SB0/P0/C0}
CORE 2 clearing 00000000.0097b000 to 00000000.00984000
{/N0/SB0/P0/C0}
CORE 3 clearing 00000000.00984000 to 00000000.0098d000
{/N0/SB0/P0/C0}
CORE 0 clearing 00000000.0098d000 to 00000000.00996000
{/N0/SB0/P0/C0}
CORE 1 clearing 00000000.00998000 to 00000001.00732000
{/N0/SB0/P0/C0}
CORE 2 clearing 00000001.00732000 to 00000002.004cc000
N0/SB0/P0/C0}
CORE 3 clearing 00000002.004cc000 to 00000003.00266000
{/N0/SB0/P0/C0}
CORE 0 clearing 00000003.00266000 to 00000004.00000000
{/N0/SB0/P0/C0} Decompress OBP done
5-30
{/N0/SB0/P0/C0}
DCB_ENTER_OBP
command succeeded
{/N0/SB0/P1/C0}
DCB_ENTER_OBP
command succeeded
{/N0/SB0/P0/C1}
DCB_ENTER_OBP
command succeeded
{/N0/SB0/P1/C1}
DCB_ENTER_OBP
command succeeded
{/N0/SB0/P2/C0}
DCB_ENTER_OBP
command succeeded
{/N0/SB0/P3/C0}
DCB_ENTER_OBP
command succeeded
{/N0/SB0/P2/C1}
DCB_ENTER_OBP
command succeeded
{/N0/SB0/P3/C1}
DCB_ENTER_OBP
command succeeded
68P02901W47-S
Jul 2008
GUI Server startup sequence
SunFire E4900
OpenFirmware version 5.20.3 (10/21/06 06:17)
Copyright 2006 Sun Microsystems, Inc.

SmartFirmware, Copyright (C) 1996-2001.
16384 MB memory installed, Serial #52736447.

Ethernet address 0:3:ba:24:b1:bf, Host ID: 8324b1bf.

Hostname: somc211
NIS domain name is omcadmin
somc211 console login:

The startup sequence messages shown in the following example are displayed on the GUI
server after power-up:
68P02901W47-S
5-31
Jul 2008
boot
Resetting ...
Sun Blade 150 (UltraSPARC-IIe 550MHz), No Keyboard
OpenBoot 4.6, 1024 MB memory installed, Serial #53217047.

Ethernet address 0:3:ba:2c:7:17, Host ID: 832c0717.
Initializing
1MB of memory at addr
5ff3a000
Initializing
5fe46000
Initializing
5f002000
Initializing
5e002000
Initializing
40000000
Initializing

Boot device: /pci@1f,0/ide@d/disk@0,0:a
File and args:


Hostname: sunblade9
SUNW,eri0 : 100 Mbps half duplex link up
Configuring devices.
Loading smf(5) service descriptions: 2/2
sunblade9 console login:
5-32
68P02901W47-S
Jul 2008
Chapter
6
System Startup and Shutdown
68P02901W47-S
Jul 2008
6-1
Introduction
This chapter describes how to start up and shut down the OMC-R using the OMC-R start and
stop commands and how to carry out certain configuration tasks once the OMC-R is started.
The procedures detailed in this chapter are as follows:
DTE addressing at node elements: Ensure that the OMC-R and NE DTE addresses are
added to the NEs connected to the OMC-R (BSCs and RXCDRs).
Startup and Shutdown: Describes how to manually start and stop the OMC-R, Single
Platform Processor, and GUI server.
Configuration tasks after startup. Perform the following tasks:

NE nodes: Add the NEs to the OMC-R configuration files and hence to the PM
database.
Create subscription lists: Introduces the creation of subscription lists.
MIB configuration: Introduces MIB configuration.
6-2
OMC-R verification: Verify that communication with each NE is possible and that the
OMC-R applications are operating correctly.
68P02901W47-S
Jul 2008
DTE addressing at node elements
DTE addressing at node elements
Addressing requirements
Assign the NE X.121 address and the OMC-R X.121 addresses at the NE.
Ensure that these addresses are already entered into the NEs. If they are not entered, add the
addresses at the NE site through a TTY connection on the GPROC.
The following items outline the procedures required to assign NW X.121 and OMC-R X.121:
Setting addresses
Slot: Port settings for OMLs
Setting OML addresses
OMC-R addresses - general rules
Setting OMC-R addresses (Single Platform Processor)
Setting addresses
To set X.121 addresses at the NE, enter the changes at the NE using a PC.
Slot: Port settings for OMLs

In RAM, only address 0 is used. However, in ROM the addresses are link dependent. Table 6-1
shows the slot: port settings for the 2 Mbps link carrying the OMLs. In ROM mode, the site uses
link number 0 by default; if this is not available, it uses link number 1. If this link does not work,
it uses link number 2 and, finally, link number 3.
Use this table in conjunction with the subsequent procedures.
Table 6-1
Slots: Port settings for 2 Mbps OMLs
link_num
RXCDR (slot: port)
BSS (slot: port)
10:0
16:0
10:1
16:1
8:0
14:0
*10:0
(*denotes cage 2)
*16:0
(*denotes cage 2)
The dual download feature is only available in ROM mode. If the site is reset (and two links are
defined on the BSS/RXCDR), the OMC-R uses both of them to download the software.
68P02901W47-S
6-3
Jul 2008

Carry out the following procedure to set OML DTE addresses (0 to 3), with reference to Table 6-1.
Procedure 6-1
Setting the OML addresses
Set the DTE addresses using the command:

chg_dte bsc <link_num> <address_length> <address_byte> ,...
<>
Example:
chg_dte bsc 0 14 2 6 2 4 5 9 1 1 0 2 3 4 3 1
Verify the value set using the disp_dte command.
NOTE
The address in bsc 0 must always be set, even if the primary
OMC-R connection is not used. The bsc 0 address is used by
the BSC or RXCDR in RAM. The slot number refers to the MSI
board that carries the OML in the BSC cabinet and the port
number refers to the MMS. For the full details of the syntax of the
commands, refer to the Motorola manual Technical Description:
BSS Command Reference (68P02901W23).

The OMC-R addresses are always 14 digits long and are formatted as follows:
aaannddceehhxx
Where:
aaa
the country code.
nn
the network code.
dd
the location code.
6-4
Is:
the type code:

1 = BSS
2 = RXCDR
3 = OMC
ee
the number of OMC-R.
hh
the HSI card and port number.
xx
the function sub-address: 41 and 42 EVENT INTERFACE

61 and 62 BOOT LOADER
99 UPLOADER
00 RLOGIN
68P02901W47-S
Jul 2008

Set the seven OMC-R addresses (0-6) at the NE for the Single Platform Processor, as follows:
Addresses 0 and 1 are used for event and alarm reporting. The BSC continuously alternates
between these two addresses in its attempt to set up an alarm Virtual Circuit (VC).
Addresses 2 and 3 are used for download and bootload.
Address 4 is used for remote login. The BSC uses this address only for verification
purposes. The setting this address verifies the calling address on the inbound X.25 packet.
Addresses 5 and 6 are used for upload.
Procedure for setting the addresses

To set and verify the addresses, follow this procedure:
Procedure 6-2
Setting the addresses
Set the DTE addresses 0 to 6 using the chg_dtecommand.

The general format of the command is:
chg_dte omcr <address_num> <address_length>
<address_byte> ,... <address_byte>
For example:
chg_dte omcr 0 14 2 6 8 0 0 6 2 3 0 1 0 1 4 1
chg_dte omcr 1 14 2 6 8 0 0 6 2 3 0 1 1 1 4 2
chg_dte omcr 2 14 2 6 8 0 0 6 2 3 0 1 0 0 6 1
chg_dte omcr 3 14 2 6 8 0 0 6 2 3 0 1 1 0 6 2
chg_dte omcr 5 14 2 6 8 0 0 6 2 3 0 1 0 2 0 0
chg_dte omcr 4 14 2 6 8 0 0 6 2 3 0 1 1 2 9 9
chg_dte omcr 6 14 2 6 8 0 0 6 2 3 0 1 1 2 9 9
Verify the value set using the disp_dtecommand.
For full details of the syntax of the commands, refer to the Motorola manual Technical
Description: BSS Command Reference (68P02901W23).
68P02901W47-S
6-5
Jul 2008
Startup and shutdown
Startup and shutdown
Introduction
This section contains specific information for starting up and shutting down the OMC-R
processors. The procedures are as follows:
Starting and stopping the OMC-R: Describes how to manually start and stop the OMC-R.
Starting and stopping the Single Platform Processor: Describes how to start up and
shutdown the Single Platform Processor.
Starting and stopping the GUI server: Describes how to shut down and startup the
various applications on a GUI server.
Starting and stopping the OMC-R

The Single Platform Processor should already be set up for starting and stopping the OMC-R
whenever the system is booted or shut down respectively. Commands for manually starting and
stopping the OMC-R are described in this section.
OMC-R start, stop, power fail and the startup scripts invoked by the OMC-R start procedure
are described in the Motorola manualOperating Information: OMC-R System Administration
(68P02901W19) .
The following procedure describes how to manually start and stop the OMC-R processes from
the Single Platform Processor. The Single Platform Processor should already be set up for
starting and stopping the OMC-R whenever the system is booted or shut down respectively.
NOTE
When the system is booted or shut down, set up the Single Platform Processor before
starting or stopping the OMC-R.
6-6
68P02901W47-S
Jul 2008
Starting and stopping the Single Platform Processor
Starting the OMC-R

Use the following procedure to start the OMC-R applications running on the Single Platform
Processor.
Procedure 6-3
Starting the OMC-R applications
At the Single Platform Processor, login as the OMC-R Administrator

omcadmin.
To start the OMC-R, enter the following command:

svcadm enable s omc
Stopping the OMC-R

Use the following procedure to stop all OMC-R applications running on the Single Platform
Processor. Applications running on any other processor are also stopped.
Procedure 6-4
Stopping the OMC-R applications
Login to the Single Platform Processor as the OMC-R Administrator

omcadmin.
To stop the OMC-R, enter the following command:

svcadm disable s omc

The following sections describe how to startup and shutdown the Single Platform Processor.
The sequence in which the various applications on the Single Platform Processor are started up
and shut down is shown in Figure 6-1.
NOTE
Sometimes the Single Platform Processor must be partially shut down or some
applications must be closed. This can occur, for example, in the case of a complete
file system restore, where the Single Platform Processor must be in single user mode.
68P02901W47-S
6-7
Jul 2008
Figure 6-1
Single Platform Processor startup and shutdown
INFORMIX IN ONLINE
MODE & OMC
APP LICATIONS RU NNING
omc stop
omc s ta rt
on monitor
Mode -Graceful
Shutdown
INFOR MIX IN ONLINE

MODE & OMC
APP LICATION NOT
R UNNING
on monitor
Mode - S ta rtup
On-Line
Ta ke-Off Line
Multi Use r Mode
INFOR MIX IN OFFLINE

MODE & OMC
APP LICATIONS NOT
R UNNING
shutdown. y . g0. is
init 3
SINGLE USER MODE
Single Us e r Mode
ti-gsm_Single_Platform_Processor_startup_and_ shutdown-0043-ai-sw
Restarting the Single Platform Processor

The following procedure describes how to restart all processes on the Single Platform Processor:
Procedure 6-5
Restarting the single platform processor

Continued
6-8
68P02901W47-S
Jul 2008
Starting and stopping the GUI server
Login to the Single Platform Processor as user root.
Start up the Single Platform Processor by entering the following command:

/usr/sbin/shutdown -y -g0 -i6
Stopping the Single Platform Processor

The following procedure is used to take the Single Platform Processor from multi-user mode to
power-off mode. The OMC-R database should be in offline mode and the OMC-R applications
should be stopped.
Procedure 6-6
Stopping the single platform processor
Login to the Single Platform Processor as user root.
Shut down the Single Platform Processor by entering the following command:
/usr/sbin/shutdown -y -g0 -i0

Figure 6-2 shows the sequence of commands used to shut down and startup the various
applications on a GUI server.
68P02901W47-S
6-9
Jul 2008
Figure 6-2
GUI Server startup and shutdown
GUI AP PLICATIONS
RUNNING
OMC Us e r(s ) Log On to
All OMC Users Logged
On
This GUI S e rve r
This GUI S e rver or its
Multi Us e r Mode
or its C lie nt
Client s mus t log off

GUI AP PLICATIONS
NOT RUNNING
shutd own. y. g0. is
SINGLE USER
ctrl -d
MODE
ti-gsm_G UI_S erver_st ar tup_a nd_ shu tdown- 004 4-ai-sw
Procedure
The following procedure describes how to take the GUI server from multi-user mode to single
user mode. Close all GUI applications.
Procedure 6-7
6-10
Login to the GUI server as user root.
Shut down the system

umount -a
followed by:
shutdown -y -g0 -is
or
shutdown -y -g0 -i0
or
shutdown -y -g0 -i5
by entering the following command:
(to go to single user mode)

(to go to PROM)
(to power off)
68P02901W47-S
Jul 2008
Configuration tasks after startup
Configuration tasks after startup
NE node configuration
Add each NE that is connected to the OMC-R to:
The OMC-R configuration files NE.MAP and SITE.MAP
The PM database
In order to produce a logical naming convention for all the devices available in a network, the
SITE.MAP file is present on the GUI servers. It works in conjunction with the NE.MAP file, the
GUI application software, and certain index tables within the OMC-R database. Logical naming
makes it possible to associate logical names with NE devices, for display in alarm or event
windows and in Performance Management (PM) reports.
Create subscription lists

Create a subscription list for all the NEs on the network. These lists are stored in the OMC-R
database and enable operators to subscribe to events and alarms when the network becomes
live. The subscription lists and operator subscriptions can be modified later to customize
the subscription process.
The procedures for creating, modifying, deleting, and renaming of subscription lists and
displaying subscriptions is described in Online Help, Network Operations.
MIB configuration
Configure the CM-MIB fully to ensure that the network status feature operates correctly. The
CM-MIB is configured using the cmutil utility or using the navigation tree at the OMC-R GUI to
populate the MIB. The following configuration files are used by cmutil:
Map configuration file
File describing the network, OMC, and MSC
One file for each BSS or RXCDR describing the site configuration
The procedures for populating the MIB using these configuration files are described in the
Motorola manual Installation and Configuration: GSM System Configuration (68P02901W17).
NOTE
The MIB is already configured during the staging process. If so, check the maps to
see that the NEs, sites, and links are correct.
68P02901W47-S
6-11
Jul 2008
OMC-R verification
OMC-R verification
Introduction
This section describes the following verification procedures:
Verification of OMC-R startup and shutdown: describes how to verify that the start
and stop scripts operate successfully.
X.25 verification: describes how to verify the X.25 configuration and cabling.
Check OMC-R applications: describes how to check the OMC-R applications.
Verification of OMC-R startup and shutdown

Verify that the start and stop scripts operate successfully as follows:
Procedure 6-8
Verification of OMC-R startup and shutdown
Login to the Single Platform Processor as omcadmin and enter the

following command to shut down the OMC:
svcadm disable s omc
Use the following command to verify that all processes have been
successfully shut down:
ps -ef | grep omc | grep +
NOTE
The shutdown of the processor can be monitored using a separate
terminal window. Execute the following command on the current
omcaudit file:
tail -f omcaudit<yyyymmdd>
(where yyyymmdd is the current days date).
3
All processes are stopped. If any are still running, kill them with the
following command:
kill -9 <process id>
where <process id> is the ID number of the process to be shut down.
Continued
6-12
68P02901W47-S
Jul 2008
Procedure 6-8
X.25 verification
Verification of OMC-R startup and shutdown (Continued)
Use the following command to confirm

that the omcinit process has shut down:
ps -ef | grep omcinit
If the omcinit process is still running, it should be killed by entering the

following command:
kill -9 <process id>
where <process id> is the ID number of the omcinit process.
Restart the OMC-R by entering the following command:

svcadm enable s omc
Login to one of the GUI processor terminals and confirm that the OMC-R
console front panel is displayed on the screen.
X.25 verification
X.25 system verification requires that the OMC-R is connected to the X.25 network through
an X.25 packet switch and MUX. This is achieved by checking the X.25 configuration and by
performing loopback tests.
Chapter 10 SunFire 4800/4900 Troubleshooting of this manual describes the installation of an
ISG X.25 packet switch and MUX, and describes the basic requirements if non-ISG equipment is
used.
X.25 configuration
Check that the DTE addresses entered in the Single Platform Processor file,
/usr/omc/config/global/x25_config are the same as those entered as the OMC-R port
addresses in the X.25 packet switch.
If the system is configured as a high-end system, but without the extra physical links configured,
comment out the corresponding entries in the STARTUP.LIST file for these links.
Using an editor of your choice, comment out the link entries
in the /usr/omc/current/config/STARTUP.LIST file as follows:
# 2 X25_UPL3 /usr/omc/current/bin/x25appl 11 0 60 1 8
# 2 X25_UPL4 /usr/omc/current/bin/x25appl 12 0 60 1 9
68P02901W47-S
6-13
Jul 2008
X.25 verification
Loopback tests
Make calls over each of the six ports to verify the Single Platform Processor X.25 configuration
and cabling as follows:
Procedure 6-9
cabling
Verification of Single Platform Processor X.25 configuration and
Arrange for the PCM cables to be looped back at the most distant point from
the MUX. For example, at the customers Digital Distribution Frame (DDF).
From the Single Platform Processor, invoke the PAD utility by entering the
following command:
cd /opt/SUNWConn/bin
pad
The response is the PAD prompt.
Initiate a call to the packet switch to verify that X.25 calls can be made
from the Single Platform Processor to the packet switch by entering the
following command:
call port<port no.>.<dte_address>
where <port no.> is the port number and <dte_address> is the node
address of the packet switch with the digits 98 appended. For example:
At the enter password prompt, press Return. The packet switch main menu
(Figure 6-3) is displayed.
Continued
6-14
68P02901W47-S
Jul 2008
Check OMC-R applications
Procedure 6-9 Verification of Single Platform Processor X.25 configuration and

cabling (Continued)
Figure 6-3
Packet switch main menu
A loopback test can be performed through the MUX and PCM cables. From
the packet switch main menu, select option 12 (Diagnostics) and then
option 3 (Loopback Tests). Specify the physical port connecting to the MUX.
Select the default values at the prompt to set up an indefinite loopback

test. There is a delay before the number of packets sent and received is
reported to the display.
Abort the test by pressing the ESC key twice to return to the packet switch
main menu.
Logout from the call by selecting option 1 (Logout), from the main menu.

The following section describes how to check the OMC-R applications. After logging into the
OMC-R on one of the SPARC terminals, the OMC-R GUI front panel shown in Figure 6-4 is
displayed. Work through each of the applications shown to ensure that they are all operational.
68P02901W47-S
6-15
Jul 2008
Figure 6-4
OMC-R GUI front panel
The OMC-R front panel is described in Table 6-2. The numbers refer to Figure 6-4.
Table 6-2
OMC-R front panel description
Number
Description
Number
Description
User name
Access to OMC-R
console
10
Front Panel exit button
Access to configuration
management
11
Access to online help
Access to event
management
12
Access to UNIX command

line
Access to performance
management
13
Access to scheduled
functions
Access to load
management
14
Access to system event logs
Access to find facility
15
Remote access to BSS or

RXCDR
Alarm summary
16
Access to network maps
Incoming alarms display

icon
The procedures for operating the OMC-R are described in Online Help, Network Operations
and for configuring the OMC-R in Installation and Configuration: GSM System Configuration
(68P02901W17).
6-16
68P02901W47-S
Jul 2008
Miscellaneous procedures and reference information
Miscellaneous procedures and reference information
Introduction
This chapter provides information about the following:
Geographic regions and time zones
Show disks utility
Troubleshooting reboot failure
Essential Jumpstart information
Enabling NMC transfer
Forwarding OMC-R mail to an exchange server
Setting up Motorola Backdrop

Table 6-3 lists the geographic regions and their constituent time zones.
Table 6-3
Geographic regions and their time zones
Geographic region
Time zones
Africa
Egypt
Libya
Western Asia
Turkey
Western Soviet Union
Iran
Israel
Saudi Arabia
Eastern Asia
China/Taiwan
Hong Kong
Japan
Republic of Korea
Singapore
Canada
East Saskatchewan
Newfoundland
Yukon
Mountain
Aleutian
Continued
68P02901W47-S
6-17
Jul 2008
Table 6-3
Geographic regions and their time zones (Continued)
Geographic region
Time zones
Central America
Mexico/Baja Norte
Mexico/Baja Sur
Mexico/General
Cuba
Australia/New Zealand
Tasmania
Queensland
North
West
South
Victoria
New South Wales
Broken Hill
Sturt
Yancowinna
LMI
New Zealand
Eastern
Central
Pacific
Samoa
Europe
Great Britain and Eire

Iceland
Poland
Western Europe
Middle Europe
Eastern Europe
South America
Brazil East
Brazil West
Brazil Acre
Brazil De Noronha
Chile Continental
Chile Easter Island
United States
Eastern
Central
Mountain
Pacific
East Indiana
Arizona
Michigan
Hawai
* Other offset from GMT
All other regions, time

zone relevant to network
local time
NOTE
If none of the listed choices for Geographic Region is applicable to the installation,
choose Other offset from GMT. It allows the Geographic Region to be set in terms
of number of hours offset from Coordinated Universal Time (that is, Greenwich Mean
Time (GMT)). If east of Greenwich, a positive offset is applied. If west of Greenwich, a
negative offset is applied.
6-18
68P02901W47-S
Jul 2008
Show disks utility
Show disks utility

The show disks command permits the selection of an individual address that can be pasted
into commands later.
To execute the show disks command, the Single Platform Processor is required to be in PROM
mode. To shut down and later restart the system from PROM mode, refer to Startup and
shutdown on page 6-6 .
The following example shows how to create the nvramrc alias for the bootdisk using show
disks. A similar exercise can be performed to create the nvramrc alias for the mirrordisk.
Procedure 6-10
Show disks utility
For the Netra 20 and SunFire 4800/4900 platforms, type:

probe-scsi-all
Type:
show-disks
a) /sbus@3,0/SUNW,fas@3,8800000/sd
b) /sbus@3,0/SUNW,socal@d,10000/sf@1,0/ssd
c) /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd
q) NO SELECTION
Enter Selection, q to quit:
Type c to select the bootdisk for nvalias setup. The following output is
displayed:
/sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd has been selected.
Type:
nvalias bootdisk
Press CTRLy to insert /sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd in the

above command line.
To complete the line type @w followed by the disk number taken

from the probe-fcalall output, in this case it is 210000203713d800.
The result is a line similar to the following:
nvalias bootdisk
/sbus@3,0/SUNW,socal@d,10000/sf@0,0/ssd@w210000203713d800

If the system fails to reboot, some of the customized configuration variables may have reverted
to their default values. Change the following values back so the system can reboot properly.
68P02901W47-S
6-19
Jul 2008
Procedure 6-11
Execute the following command from the OK> prompt and check the value
of the autoboot, diag-device and diag-switch values:
printenv
The resulting variables output should be set to the following values:
auto-boot true
diag-device disk diskbrd diskisp disksoc net
diag-switch false
If the variables do not have these settings then execute the following
commands from the OK>prompt:
NOTE
Do not execute these commands for variables that already have
the correct settings.
setenv auto-boot? true
setenv diag-device disk diskbrd diskisp disksoc net
setenv diag-switch? false
3
Boot the system by entering the following command from the OK> prompt:
boot
The system should boot correctly.
NOTE
After the system has booted up, make sure the key switch is
returned to secure mode.

Jumpstart 1800.x is the recommended version for GSM OMC 1.8.x.x releases.
The Jumpstart is shipped as part of the Common Platform DVD that also contains the OMC-R
software and patches. The version of this DVD is the point release of the OMC-R load. For
example, GSM OMC-R 1.8.0.0.x.x.
6-20
68P02901W47-S
Jul 2008
Table 6-4
Supported configurations
Machine type
Processor type
Netra 20
System
Processor
Sunfire 4800
Netra 440
System
Processor
System
Processor
Disk sizes
Target number
Internal External
72
72
72
72
72
72
Gb
Gb
Gb
Gb
Gb
Gb
scsi
scsi
scsi
scsi
scsi
scsi
c1t8d0
c1t9d0
c1t10d0
c1t11d0
c1t12d0
c1t13d0
External
External
External
External
External
External
72
72
72
72
72
72
Gb
Gb
Gb
Gb
Gb
Gb
scsi
scsi
scsi
scsi
scsi
scsi
c3t8d0
c3t9d0
c3t10d0
c3t11d0
c3t12d0
c3t13d0
External
External
External
External
External
External
72
72
72
72
72
72
Gb
Gb
Gb
Gb
Gb
Gb
scsi
scsi
scsi
scsi
scsi
scsi
c1t8d0
c1t9d0
c1t10d0
c1t11d0
c1t12d0
c1t13d0
External
External
External
External
External
External
72
72
72
72
72
72
Gb
Gb
Gb
Gb
Gb
Gb
scsi
scsi
scsi
scsi
scsi
scsi
c3t8d0
c3t9d0
c3t10d0
c3t11d0
c3t12d0
c3t13d0
External
External
External
External
External
External
72
72
72
72
72
72
Gb
Gb
Gb
Gb
Gb
Gb
scsi
scsi
scsi
scsi
scsi
scsi
c0t8d0
c0t9d0
c0t10d0
c0t11d0
c0t12d0
c0t13d0
External
External
External
External
External
External
72
72
72
72
72
72
Gb
Gb
Gb
Gb
Gb
Gb
scsi
scsi
scsi
scsi
scsi
scsi
c1t8d0
c1t9d0
c1t10d0
c1t11d0
c1t12d0
c1t13d0
External
External
External
External
External
External

To forward mail on the OMC-R to an exchange server, follow Procedure 6-12:
68P02901W47-S
6-21
Jul 2008
Procedure 6-12
Edit the /etc/hosts file and add a mail host entry with the following format:
<ip_address> <mail_server> mailhost
Where <ip_address> is the IP Address of the mail server and
<mail_server>is the Exchange Mail Server hostname.
If you want all mail forwarded to an exchange user for mails destined say
for user omcadmin, create the file /home/omcadmin/.forward as user
omcadmin.
Edit this file to include the line:

<user_name@exchange_account>
Where <user_name@exchange_account> is the exchange e-mail
address to forward mail.
If you want to preserve a copy of this mail for the omcadmin mail account
on the originating machine edit the file /home/omcadmin/.forward and
add the following:
\omcadmin

This procedure sets up Motorola-specific backdrops on the system:
Procedure 6-13
6-22
As user root enter the following commands:

cd /usr/omc/current/config
cp mot*pm /usr/dt/share/backdrop
Each user should then do the following to set up a Motorola Backdrop that
suits: Login using the CDE login screen.
Open up an Xterm window.
Enter the following to bring up the desktop styles menu.

/usr/dt/bin/dtstyle
Click on the Backdrop icon.
Choose one of the Motorola Backdrops from the list.
Apply the chosen backdrop.
The next time this user logs in, this backdrop appears.
68P02901W47-S
Jul 2008
Chapter
7
Configuring Auxiliary Devices
68P02901W47-S
Jul 2008
7-1
Configuring auxiliary devices
Configuring auxiliary devices
Introduction
This chapter describes how to configure auxiliary devices at an OMC-R. The configuration
procedures are as follows:
7-2
Setting up a Wyse terminal: describes how to set up a Wyse terminal as a dumb terminal.
Adding a printer: describes how to add a remote printer facility to the OMC-R.
Adding a modem: describes how to add a modem and troubleshoot the modem.
Configuration and installation of a SPARCstation terminal: describes how to

configure and install a remote SPARCstation terminal.
Setting up remote Single Platform Processor: describes how to set up a remote Single
Platform Processor.
Installation and configuration of a remote monitoring terminal: describes how to

install and configure a remote monitoring terminal for use as a remote monitoring station
or night concentration center.
68P02901W47-S
Jul 2008
Setting up the Wyse terminal
Introduction
This section describes how to set up the Wyse 120 terminal for use as a dumb terminal.
Procedure for setting up the Wyse terminal

To set up the Wyse 120 terminal as the console for the Netra 20, Netra 440, SunFire 4800 or
SunFire 4900, perform the following procedure:
NOTE
Before powering up the Netra 20, Netra 440, SunFire 4800 or SunFire 4900, set
up the console.
Procedure 7-1
To enter terminal setup mode, press Shift and Select.
Press the appropriate function key to access the setup submenu (Table 7-1).
To toggle available options, press the spacebar.
To move on to the next option, press the appropriate arrow key.
Table 7-1
68P02901W47-S
Wyse terminal setup submenus
Function key
Submenu name
Option
F2
GENRL
PERSONALITY = VT100
F4
COMM
COMM = FDX
BAUD RATE = 9600
HOST PORT = SERIAL 1
STOP BITS = 1 DATA
PARITY = 8/NONE
F6
ANSI
ANSI ID = VT100
F12
EXIT
SAVE? YES
7-3
Jul 2008
Procedure for setting up the Wyse terminal
NOTE
It is necessary to set the display on the Wyse 120 terminal by entering the following
commands before using an editor:
TERM=vt100
export TERM
7-4
68P02901W47-S
Jul 2008
Adding a printer
Adding a printer
Overview
It is possible to add a printer on the Ethernet LAN of the OMC-R. The printer can be connected
anywhere on the LAN and is not restricted to being connected to the Single Platform Processor
or one of the GUI processors.
Any network printer that supports postscript and is lpd compatible is supported. Follow the
printer manual for details on network setup. Refer to Chapter 3 of Operating Information:
OMC-R System Administration (68P02901W19) for further details on how to install and
configure a printer.
Assigning printer name and address on the network

Assign the printer name and address on the network by adding the printer IP address and
hostname to the /etc/hosts file of all processors, which belong to the OMC-R network. Verify
the printer setup as follows:
Procedure 7-2
Verifying the printer setup
Print a page to verify the printer settings.
Issue a ping command from any processor on the OMC-R network as follows:
ping hostname
Replace hostname with the name of the printer set in the /etc/hosts file.
If the printer does not respond to the ping command, check the following:
Ensure that all physical connections, bridges and routers are working
correctly.
From the setup page, check that the IP protocol is enabled.
Check that the IP address is set correctly on the printer operators

panel.
Configuring a printer connected to a GUI processor

This category includes the SPARC printer I and II.
Jobs are spooled for printing to the Single Platform Processor (or the processor to which the
printer is attached).
68P02901W47-S
7-5
Jul 2008
Checking the printer status
To add a local printer, execute the following commands on the host processor as user root:
/usr/omc/current/sbin/Configure_Printer
Follow the instructions on the screen.
Checking the printer status

To check if the installation is complete, enter the following command:
lpstat -t
scheduler is running
system default destination: laser
device for laser: /dev/null
laser accepting requests since Jun 24 15:36
printer laser (login terminal) is idle. enabled since Jun 29 10:55
Printing a file
To print a file, use the lp command in the following format:
lp file_name
Where file_name is the name of the file to be printed.
Printer configuration file

A printer configuration file provides support for multiple printers defined by the user. The
default printer configuration file is:/usr/omc/current/config/printer.def
The printer configuration file contains information in the following format:
<printer_alias><printer_name> <print_command>
Where:
Is:
<printer_alias>
A user friendly name for the printer, displayed

to the user.
<printer_name>
The actual printer name, which is determined

using the lpstat -p command.
<print_command>
The executable script used for printing.
Error messages are displayed to the user if:
7-6
An incorrect printing type is specified in the printer configuration file.
The printer script specified in the printer configuration file does not exist in
/usr/omc/current/bin on the GUI processor.
The printer script is not executable.
68P02901W47-S
Jul 2008
Printer configuration file
A default script called mmiPrint is provided in /usr/omc/current/bin on the GUI processor.

Other scripts may also be used, but must be located in the same directory.
68P02901W47-S
7-7
Jul 2008
Installing a modem
Installing a modem
Introduction
This section describes how to install and configure a modem to a Sun Microsystems
SPARCstation running Solaris 10 with CDE. The following modems are installed:
Motorola 3460 FastR
Motorola 326x
MultiModem MT5634ZBA
The modem is configured for both dial-in and dial-out access.
Background information
The modem can be used for remote access to the OMC-R (dial-in to the OMC-R) and for
accessing external computer systems from the OMC-R (dial-out from the OMC-R).
Remote access to the OMC-R through a modem can provide TTY (character based) access to
the OMC-R. It does not provide a method for remotely accessing the graphical functions of the
OMC-R. If a remote OMC-R operator terminal is required, connect it to the OMC-R using LAN
routers over a synchronous link operating at speeds of at least 64 kbps.
Support engineers use remote access to diagnose and rectify problems.
NOTE
The procedures described herein may conflict with other programs or serial port
users. Connect the modem to an unused port or disable the port monitor services.
Use the Motorola 3460 FastR modem, shown in Figure 7-1, to implement the Alarm Auto
notification feature.
7-8
68P02901W47-S
Jul 2008
Figure 7-1
Data links
Motorola 3460 FastR modem
ti-gsm_Motorola_3460_FastR_modem-0047-ai-sw
Data links
When connecting two SPARCstations with modems, there are three data links:
LOCAL
Computer
(DTE)-
REMOTE
Modem Modem
Computer
(DCE)-(DCE) (DTE)
Local DTE rate
DCE rate
Remote DTE
rate
Rates
Data is transferred at the same rate as the slowest link. The modems may use data compression
on the DCE link. This can help if the DCE link is the slowest link.
In the following example, data compression on the DCE link, in theory, makes the DCE link
appear to operate at 20+ kbps. The bottleneck would then be the remote DTE rate (19.2 kbps):
Local DTE rate = 38.4 kbps
DCE rate = 9.6 kbps
Remote DTE rate = 19.2 kbps
The Motorola 3460 FastR modem has various security features to restrict or prevent access.
These include only password protection and manual answer. These and other security features
are described in the modem user guide.
68P02901W47-S
7-9
Jul 2008
Physical connection
Physical connection
Install the modem on the SPARC station, use either ttya or ttyb (serial port A or B), and make
sure that the RS-232 cable is a straight-through cable. Any 25 to 25-pin cable is acceptable
although only pins 1 to 8 and pin 20 are necessary.
NOTE
Do not use a null modem cross-over cable or a null modem gender adapter cable.
While using a system, which shares ports A and B, such as the SPARCstation 10, and port B is to
be used for the modem port, use the splitter cable (port A can be accessed directly without the
splitter). This splitter cable is available from SunExpress (part number: X985A or 530-1869/C9).
Initial SPARCstation setup

The initial SPARCstation setup involves two activities:
Defining the dial-in serial port characteristics.
Verifying port monitor services.
NOTE
The root password is required to install or modify files for modem installation.
Define dial-in serial port characteristics

Add the following entries to the /etc/ttydefs file. These are the serial port character port
characteristics presented by the answering side:
38400m:38400 clocal hupcl:38400 clocal hupcl
crtscts::38400m
19200m:19200 clocal hupcl:19200 clocal hupcl
crtscts::19200m
9600m:9600 -clocal hupcl:9600 -clocal hupcl
crtscts::9600m
7-10
68P02901W47-S
Jul 2008
Initial SPARCstation setup
The above definitions turn on hardware flow control (crtscts) at the serial port, set to match
hardware flow control at the modem. In addition, the above definition uses eight data bits with
no parity transfers.
NOTE
14400 baud and 28800 baud rates are the modem to modem speeds and 19200 and
38400 are the speeds the modem uses to communicate with the serial port. Modem
to serial port speeds should be faster than modem to modem speeds to prevent
bottlenecks.
Verify current port monitor services

Verify that there are no port monitor services on the port to be connected to the modem, by
typing the following command at the # prompt:
pmadm -p zsmon -l
An example output is:
PMTAG
PMTYPE SVCTAG FLGS ID
<PMSPECIFIC>
The following two lines are displayed as one line on the screen:
zsmon
ttymon ttya
u root
/dev/term/a - -
/usr/bin/login
- 9600 ldterm,
ttcompat login:
- vt100 y #Terminal
In addition, the following two lines are displayed as one line on the screen:
zsmon
ttymon ttyb
u root
/dev/term/b - -
/usr/bin/login
- 9600 ldterm,
ttcompat login:
- vt100 y #Terminal
If there are services present, as indicated in the above output, remove them by typing the
following command at the # prompt:
pmadm -p zsmon -r -s <SVCTAG value from the above, that is ttya or
ttyb>
Other methods
This can also be achieved using Admintool, or the serial port manager available under CDE
when logged in as root, and selecting Delete or Disable for the port.
Remove or disable the login services before using a new ttydefs entry.
68P02901W47-S
7-11
Jul 2008
Communicating with the modem
Communicating with the modem

Once the port monitor services are deleted or disabled, enter the following command at the
# prompt:
NOTE
Ensure that tip is executed in a shell without scrolling enabled; otherwise, a carriage
return is not sent.
tip -38400 /dev/cua/a

(38400 sets the connection speed, /a assumes ttya. For ttyb, use /b).
Verify that the modem is responding to commands. After the connect message, type:
AT
An OK> prompt should be returned. If an OK> prompt is not returned, try a different
port or cable. The modem must respond to AT commands before continuing with
the subsequent sections.
Configuring tip
NOTE
Always use the same speed to the modem as the login process is set to use. The
following procedure assumes that the modem connects using port b. If the modem
connects using port a, alter the procedure accordingly.
It is possible to configure the tip utility by modifying the /etc/remote file. Follow this procedure:
Procedure 7-3
Configuring tips
For ttyb:
hardwire:\
:dv=/dev/term/b:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:
Add the next two lines after the above entry:
modem:\
:dv=dev/cua/b:br#9600:el=^C^S^Q^U^Z:ie=%$:oe=^D:pa=even
Continued
7-12
68P02901W47-S
Jul 2008
Procedure 7-3
Controlling modem access
Configuring tips (Continued)
NOTE
When using a 28.8 kbps modem, use 38400; for a 14.4 kbps
modem use 19200, and for a 9600 modem use 9600.
2
Change the permissions and the owner of the modem port:

For port a:
chmod 666 /dev/cua/a; chown uucp /dev/cua/a
For port b:
chmod 666 /dev/cua/b; chown uucp /dev/cua/b
After modifying the /etc/remote file and changing the permissions of the
port(s), use tip by entering the following command at the # prompt:
tip modem
A connected message should be displayed. If it is not displayed, check the
/etc/remote file for errors to the modem entry.
Controlling modem access

Control the modem communication by setting the permissions of the tip utility.
To allow only root users the ability to logout using the modem, set the tip
permissions to 700 by entering the following command at the # prompt:
chmod 700 /usr/bin/tip
NOTE
Changing the permissions of tip may affect other users or programs that require the
use of tip. For example, the OMC-R test mobile feature.
Modem setup and Initialization

The modem is set up using Hayes AT commands. Once the modem has been set up, the
configuration can be stored in the non-volatile memory in the modem. It should only be
necessary to configure the modem once, even if power is lost. Refer to the modem users guide
for a complete list of the Hayes command set.
Follow the steps in Procedure 7-4 to set up the modem.
68P02901W47-S
7-13
Jul 2008
Procedure 7-4
Modem setup and initialization
At the OK> prompt, enter the correct AT command for the modem type and
DTE rate (Table 7-2). The AT commands configure the modem and store
the setup in the non-volatile memory.
After setting up the modem, exit the tip utility by typing a carriage return
followed by a tilde (~) character followed by a period (.) character.
Table 7-2
Modem initialization commands
Modem type
DTE rate
Initialization command
Motorola 3460
38400
AT&FQ2*DE19*FL3&D2&C1*CL0S0=2&Y1&W1
19200
9600
Motorola 326X
38400
AT&FQ2*DE15*FL3&D2&C1*AA2&Y1&W1
19200
9600
NOTE
The syntax of the AT commands is specified in the Motorola 3460 FastR User Guide.
Description of AT commands used in the initialization string

The syntax of the AT command is as follows:
AT&FQ2*DE15*FL3&D2&C1*AA2&Y&W1
The syntax is explained in Table 7-3.
Table 7-3
Syntax of the AT command
Symbol
Meaning
Notes
AT
Enter command mode.
&Fz
Reset Modem to default

factory settings.
The four factory default

option sets are restored to
their original settings; all
stored telephone numbers are
deleted.
Q2
RsltCode = Orig
Result codes are output to the

DTE when operating as an
originating modem.
Continued
7-14
68P02901W47-S
Jul 2008
Table 7-3
68P02901W47-S
Syntax of the AT command (Continued)
Symbol
Meaning
Notes
DE
Fix DTE rate
*FL3
Flow Control = RTS/CTS
&D2
DTR Control = Discon
The modem hangs up and

enters command mode when
an on-to-off DTR transition is
detected, while the modem is
in data, test, or escape mode.
If DTR is low, the modem
does not auto answer. This
command determines how the
modem interprets the DTR
signal. The local DTE uses
DTR (pin 20) to signal the
modem.
&C1
DCD Control = Normal
Normal DCD is off during

dialing and while the modem
is in training with the remote
modem. DCD is on in data
mode. It is off when the
modem is disconnected from
the telephone line. This
determines how the modem
sets DCD signals. The modem
signals the DTE with DCD
on EIA/TIA 232-D Pin 8 (V.24
Circuit 109).
*AA2
Answer=Ring #2
The modem will answer

incoming calls after 2 rings
(*AA2) or after X rings where
X is defined in the S0 register
(S0=X). Check specific
in country requirements
regarding auto-answer
modems.
&Y1
Power Up In=1
When the modem is powered

up, it automatically uses
option set 1.
&W1
Save Changes=1
*DE15 sets a DTE

rate of 38400.
*DE12 sets a DTE
rate of 19200.
*DE8 sets a DTE rate of
9600.
Refer to Saving changes on

page 7-16
7-15
Jul 2008
Configuring the MultiModem MT5634ZBA Global
Saving changes
When using AT Commands or front panel options to alter the modems settings,
if the changes are not saved, the modem does not enter them into the memory.
After selecting the option set most suited to the application (using the ATZn
Command), and modifying any required configuration settings, enter the following:
AT<n>&W
Where:
Is:
<n>
a value of 1 through to 4, determined by

the option set where the new customized
option set is saved.
The modem front panel displays Saving options. After a few seconds, the front panel displays
Save Completed!, signifying that the option set is saved successfully in the non-volatile memory
of the modem.
Configuring the MultiModem MT5634ZBA Global

The MultiModem MT5634ZBA must first be set up with the appropriate country configuration.
Enter the following commands at the OK> prompt:
Procedure 7-5
Configuring the MultiModem MT5634ZBA
To load factory settings as active configuration:

AT&F0
To set the country code:

AT%T19,0,nn
Where <nn> is the country code.
To save as factory default:

AT&F&W
To display Result Codes to verify the correct country has been configured:
ATI9
The MultiModem MT5634ZBA can now be set up and initialized by entering one of the following
commands at the prompt:
For a 38400 DTE rate, enter:

AT$SB38400&K3&D2&C1S0=2&Q0&W0

AT$SB19200&k3&D2&C1S0=2&Q0&W0

AT$SB9600&k3&D2&C1S0=2&Q0&W0
This configures the modem and stores the current modem settings in non-volatile memory.
These changes are then loaded in place of the factory defaults at power-on.
7-16
68P02901W47-S
Jul 2008
Enabling the login process
AT commands
The AT commands that are used when initializing the MultiModem MT5634ZBA are described in
Table 7-4.
Table 7-4
MultiModem MT5634ZBA initialization AT commands
AT command
Description
AT$SBnnnnn
Set serial port to nnnnn bps.
AT&K3
Enable CTS/RTS hardware flow control.
AT&D2
If DTR drops while in online data mode, the modem

hangs up. If the signal is not present, the modem will
not answer or dial.
AT&C1
DCD goes high when the remote modem carrier signal

is detected, and goes low when the carrier signal is
not detected.
ATS0=2
Set the number of rings until the modem answers.
AT&Q0
Enables result codes.
AT&W0
Stores current modem settings in non-volatile memory,

and causes the settings to be loaded in place of the
factory defaults at poweron or following the ATZ
command.

The following procedure creates a port monitor service to allow login through a modem from a
remote host (bi-directional modem service):
Procedure 7-6
To display the Serial Port Manager window, use one of these methods: either
select port manager from the tools icon, and click on the serial port
manager icon, or start up Admintool (admintool &) and select the serial
port option from the drop down menu from the menu bar.
Click on port a or b with the left mouse button to select the port to be used by
the modem.
From the edit menu, select modify. The Serial Port Manager: Modify window
appears.
Select the expert display.
Continued
68P02901W47-S
7-17
Jul 2008
Remote connection and file transfers
Procedure 7-6
Enabling the login process (Continued)
From template, choose Bi-directional.
Set baud rate to the desired baud rate of the modem.

Modem baud rate
Setting required
28800
38400m
14400
19200m
9600
9600m
Set Terminal type to vt100.
Verify that all amended fields are correct, and then click OK.
Close all open windows.
10
To verify that a port monitor has been configured, enter the following
command at the # prompt:
pmadm -p zsmon -l
PMTAG
PMTYPE
SVCTAG
FLGS ID
<PMSPECIFIC>
zsmon
ttymon
ttya
u root
/dev/term/a
<>
- /usr/bin/login - 9600 ldterm, ttcompat login: - dialup n
#modem - Bidirectional
11
If a port monitor has not been configured for that port, return to step 3 and
try again.
Remote connection and file transfers

To test the modem, contact Customer Network Resolution Center (CNRC) for a telephone
number, login, password, and logout information.
If problems occur, refer to the section Troubleshooting the modem on page 7-19.
Once a connection and successful login is achieved,
instruct the modem to hang-up the line by typing:
+++ or ATH
7-18
68P02901W47-S
Jul 2008
Troubleshooting the modem
Troubleshooting the modem
Problem symptoms
If the following problems are experienced, solutions are detailed in this section:
All ports busy
No login prompt
Modifying eeprom settings
Corruption from SPARCstation with remote system login
Modem hangs up after answering a call and negotiation
Permission denied or link down
Modems do not disconnect properly
Nothing happens when trying to tip the modem
On dialing into the SPARCstation, the modem never picks up the phone
Login message is corrupt
Cannot login - password failed
No utmpx entry
All ports busy

This message indicates that another process has control of the port. Follow Procedure 7-7
until the problem is rectified:
Procedure 7-7
Troubleshooting: all ports busy
Disable or delete the port monitor, using Admintool or the serial

port manager, for that port, or by using the following commands:
Enter the following to disable the port monitor service of port a:
/usr/sbin/pmadm -d -p zsmon -s ttya
Enter the following to enable the port monitor service of port a:
/usr/sbin/pmadm -e -p zsmon -s ttya
Then enter:
tip -<9600> /dev/cua/a
Replacing <9600>with the appropriate connection speed for the device.
Continued
68P02901W47-S
7-19
Jul 2008
All ports busy
Procedure 7-7
Troubleshooting: all ports busy (Continued)
Check whether the details are entered correctly in /etc/remote, ensuring

that the correct device has been specified.
There could be a permissions problem on the device. If necessary, change

the permissions and ownership of the modem port by entering the following
commands at the # prompt:
chmod 666 /dev/cua/a
chown uucp /dev/cua/a
ls -Ll /dev/cua/a to verify permissions and ownership.
NOTE
If cu is abruptly killed, the device is left with an owner of the
last cu user.
4
Check for a lock file in /var/spool/locks. If there is a lock file, for example,
LK.032.028.001, then cat the file. The number displayed is the Processed
ID (PID). Use the ps command to determine if the process is still active.
Remove the lock file. If the message All ports busy is displayed, kill
the process. If the process is defunct, it cannot be killed and a reboot is
necessary. This happens because the driver is waiting at an un-linkable
level for the device to respond.
Another process has the port open. This could be another tip session, a getty
process or a defunct tip/cu process. At the # prompt enter the command:
ps -ef | grep tip
As root, enter for the appropriate device the following command at the #
prompt:
fuser /dev/cua/a
/dev/cua/a: 6520 6510
Based on the example output, enter the following commands:
ps -ef | grep 652
ps -ef | grep 651
The PIDs are 652 and 651.
If the process using the port is /usr/bin/login or ttymon, then somebody
has dialled the machine, the modem is active or the modem is asserting Data
Carrier Detect (DCD) all the time. The modem must be configured so that
the DCD is asserted only when a carrier is detected from the remote
modem. Refer to the modem documentation.
If the process is ttymon, there are two ways to kill the process. The easiest
is to use Admintool / Serial port manager, select the port from the Edit
menu, and delete the port service. (The modem is no longer configured for
dial-in). The command to remove the service is:
pmadm -r -p zsmon -s <SVCTAG>
(use pmadm -l to determine SVCTAG)
7-20
Bring the system down and then back to multi-user mode. The command is:
/usr/sbin/shutdown -i6 -g0 -y
Sometimes a complete reboot may be necessary to achieve a hardware
reset on the port.
Before rebooting, remove the device (do not leave a dangling cable - remove
the device at the SPARCstation) and delete the port monitor.
68P02901W47-S
Jul 2008
No login prompt
No login prompt
If a login prompt does not appear:
Procedure 7-8
Troubleshooting: no login prompt
Check if a ttymon process is started by typing the following command at

the # prompt:
ps -ef | grep ttymon
root 208 204 80 Sep21 ? 0:01
/usr/lib/saf/ttymon
root 17258 208 2 10:42:43 ? 0:00
/usr/lib/saf/ttymon
Where PID of 208 is the parent ttymon process and PID of 172.58 is the
child process for term/b.
Check if the ttymon process TTY has changed from ? to term/b by typing
the following command at the # prompt:
ps -ef | grep ttymon
root 208 204 80 Sep21 ? 0:01
/usr/lib/saf/ttymon
root 17258 208 6 10:42:43 term/b 0:00
/usr/lib/saf/ttymon
If this does not occur, check if the serial port has been configured properly
and the port monitor service is present by typing the following command
at the # prompt:
pmadm -p zsmon -l
PMTAG PMTYPE SVCTAG FLGS ID <PMSPECIFIC>
zsmon ttymon ttya
/dev/term/a - /usr/bin/login - 9600 ldterm, ttcompat login: - tvi925 n
#modem Bidirectional
68P02901W47-S
Check and verify that the port monitor services baud rate matches the
modem baud rate.
Use the tip utility and connect back into the modem.
7-21
Jul 2008
When to modify the EEPROM settings
When to modify the EEPROM settings

Do not change the EEPROMs unless trying to get a terminal working at boot prom level.
Corruption from SPARCstation with remote system logging in

This is usually an indication that the modem speed and the configured port monitor speed
are not matched:
Check the modem speed and make certain that it matches the speed of the SPARCstation.
Connect back to the modem, using tip, and verify the modem configuration.
NOTE
The modem must be able to lock the modem speed and match the port monitor speed
(speed configured using Admintool / Serial port manager).
Modem hangs up after answering a call and negotiation

This is probably due to one or both modems forcing it to use a particular connect speed or
compression protocol - if one modem cannot manage to connect to the other modem, the modem
hangs up. Check the settings of both modems.
Permission denied or link down

If this message appears from the tip utility, perform the following:
Procedure 7-9
Troubleshooting permission denied or link down
Ensure that dv=/dev/cua/a or dv=/dev/cua/b are present in the hardwire

entry of the /etc/remote file.
Check in /var/spool/locks for a lock file LCK.* and remove that file.
Check the permissions on the serial device (/dev/cua/a or /dev/cua/b)

and ownership.
Modems do not disconnect properly

The modem does not disconnect properly or a user stays logged in even after disconnecting.
7-22
68P02901W47-S
Jul 2008
The modem is not configured correctly. The modem must be configured so that the Data Carrier
Detect (DCD) is asserted only when a carrier is detected from the remote modem. Refer to
the modem documentation.

If this situation occurs:
Check the cabling to the modem.
Check if the proper port is being used.
Ensure that tip is being used in a shell tool and not in a command tool.
When dialing into the SPARC the modem never picks up the
phone
This situation indicates that the modem is not configured correctly, therefore:
Check if the modem is set up for auto answer (*AA2) for Motorola Modems or ATS0=2 for
MultiModem.
Ensure that the DTR light is lit on the modem indicating that the Data Terminal Ready is
asserted from the SPARCstation.
Login message is corrupt

The login message is corrupt and nothing happens when Return is pressed, but it does if
LF or CTRL-J is pressed.
If this situation occurs then reconfigure the remote computers serial port setup for 8 data
bits, 1 stop bit and no parity.
Cannot login: password fails

There is no utmpx entry and the user must execute login from the lowest level shell.
If this situation occurs, ensure that the terminal type is set to vt100 when setting up the port
monitor services and the environment variable TERM is also set to vt100 on both the local
and remote host.
68P02901W47-S
7-23
Jul 2008
Configuration and installation of a remote monitoring terminal
Configuration and installation of a remote monitoring

terminal
Introduction
This section describes the configuration and installation of a remote SPARCstation terminal.
Remote terminals are used simply to monitor a regional OMC-R from a remote location or for the
purpose of night concentration where several OMCs may be monitored from one central point.
Single OMC-R monitoring configuration

The following text describes the configuration of a remote SPARCstation terminal. The single
OMC-R monitoring configuration is illustrated in Figure 7-2. The remote monitoring station
is used to monitor just one regional OMC-R.
Figure 7-2
Single monitoring station configuration
PRINTER
PRINTER
GUI SER VER

BRIDGE
ROUTER
ROUTER
GUI SER VER
GUI SER VER
GUI SER VER
SINGLE PLATFORM
PROCESSOR
MONITORING
ST ATION
REGIONAL OMC
ti-gs m_S ingle_ mon itoring_s ta tion_configura tion-0048-a i-s w
The link protocol between the sites is X.21, supporting TCP/IP WAN connection. The
bridge/router at the regional OMC-R end may provide several other routes to other routers
or bridges at other sites.
7-24
68P02901W47-S
Jul 2008
OMC-R night concentration center configuration
The Sunblade 150 at the monitoring station is configured as a GUI server so that the OMC-R
software executes locally. Add the same users on the GUI server as are added at the regional
OMC-R. The remote Sunblade 150 must still NFS mount the /usr/omc/config/global, the
/usr/omc/ne_data and /usr/omc/ne_data/raw_stats directories across the network.

For large systems that contain multiple OMCs, an operator must be able to handover the
management of one network region to another OMC-R during the night shift. This necessitates
the provision of a mechanism to enable a single workstation access to multiple Single Platform
Processors. Figure 7-3 shows a configuration where the concentration center consists of one
Sunblade 150, which is configured as a GUI server for both region A and region B. Only one
SunBlade 150 is required.
68P02901W47-S
7-25
Jul 2008
Figure 7-3
Night concentration center configuration (Sunblade 150 high-end server)
PRINTER
PRINTER
ULTRA
GUI SER VER
BRIDGE
ROUTER
ROUTER
ULTRA
GUI SER VER
LEASED LINE
SP ARC ST ATIONS
GUI CLIENT
ULTRA
GUI SER VER
REGION (A)
ULTRA
GUI SER VER
REGION (B)
CONCENTRA TION
CENTRE
SINGLE PLATFORM
PROCESSOR
REGIONAL OMC A (LOCAL)
PRINTER
ULTRA
GUI SER VER
BRIDGE
ROUTER
ULTRA
GUI SER VER
SP ARC ST ATIONS
GUI CLIENT
SINGLE PLATFORM
PROCESSOR
REGIONAL OMC B (REMOTE)
ti-gsm_Night_concentration_center_configuration_(single_ultra_5_or_Sunblade_150_high-end_server)-0049-ai-sw
7-26
68P02901W47-S
Jul 2008
Night concentration overview
Night concentration overview

The following are requirements and restrictions for the Night Concentration Center
Configuration:
A single workstation configured as either a GUI server or a GUI client, is able to access
multiple Single Platform Processors. One of these is the operators local OMC-R system.
The others are remote OMC-R systems that are normally monitored at night.
Access to OMC-R systems is mutually exclusive. The operator must use a different login
identity for each remote OMC-R. To gain access to a different remote OMC-R, the operator
must logout and login again as a different user. Each special user accesses a specific
remote OMC-R that is specified during initial setup of the Night Concentration feature.
The GUI server used for this feature is unable to support any clients. If a GUI client
processor is used then mount the OMC-R software from a local GUI server that is not
used for the Night Concentration feature.
A minimum 64 kb digital leased line is required to run the OMC-R remotely.
Naming conventions
The following naming conventions are used when
describing the setup of a night concentration center:
local_sys: The hostname of the local Single Platform Processor.
remote_sys: The hostname of the remote Single Platform Processor.
local_gui: The hostname of the local GUI server processor.
remote user: The username of the account used to access the remote OMC-R.
Prerequisites
Complete the following procedure before commencing the setup of a night concentration center:
Procedure 7-10
68P02901W47-S
Prerequisites
The local and remote OMC-R systems must have version 1.7.*.* of the
OMC-R software installed. Refer to the section Configuration checks on
page 3-14 in the relevant configuration section of this manual to install
this version of the software.
Obtain the hostname and IP addresses of the different processors for each
remote Single Platform Processor. Enter the information in Table 7-5.
Obtain the Username and User Identifier Number (UID) from the account
of the user of the remote Single Platform Processor system. Enter the
information in Table 7-6.
7-27
Jul 2008
Prerequisites
Table 7-5
Hostname and IP addresses for different processors
System
Hostname
IP address
local_sys
remote_sys
local_gui
Table 7-6
User name and ID for remote system
Account
User name
UID
Account for user or remote

OMC-R system
7-28
68P02901W47-S
Jul 2008
Remote Single Platform Processor setup
Remote Single Platform Processor setup
Introduction
This section describes how to set up a remote Single Platform Processor for night concentration.
The procedures are as follows:
Updating host file entries: describes how to change host file entries.
Exporting file changes: describes how to mount certain file entries.
Creation of a new account: describes how to create an account to use the remote OMC-R.
Updating host file entries

Each of the remote Single Platform Processors must contain the hostname of the local GUI
server in its hosts file. Change the file as follows:
Procedure 7-11
Updating host file entries
Edit the /etc/hosts file on the remote_sys processor and check that the
hostname of the local_gui processor is present. If the entry is not listed, add
a line similar to the following to the /etc/hosts file using a suitable editor:
<IP_address> <local_gui>
Where,
<IP_address> is the IP address of GUI server.
<local_gui>is the hostname of local GUI server.
If a GUI server name was added, update the NIS maps

by executing the following commands as user root:
cd /var/yp
/usr/ccs/bin/make
Exporting file changes

Each of the remote Single Platform Processors must allow the local GUI server to mount certain
file systems. Follow the steps in Procedure 7-12 to mount the file systems.
68P02901W47-S
7-29
Jul 2008
Creation of a new account
Procedure 7-12
Exporting file changes
Edit the /etc/dfs/dfstab file on each of the remote_sys processors and

add the hostname of the local_gui processor to the list of hosts
with mount permissions. Execute the following commands:
share -F nfs -o
rw=sparc0:<local_gui>, root=sparc0:<local_gui>
share -F nfs -o
rw=sparc0:<local_gui>,root=sparc0:<local_gui>
/usr/omc/ne_data
share -F nfs -o
rw=sparc0:<local_gui>,root=sparc0:<local_gui>
share -F nfs -o
rw=sparc0:<local_gui>,root=sparc0:<>local_gui /home
share -F nfs -o
rw=sparc0:<local_gui>,root=sparc0:<local_gui> /usr/local
Where <local_gui> is the hostname of the local GUI server.
NOTE
Each of the five above commands should be treated as one
continuous line.
2
Execute the following command on each of the

remote Single Platform Processors as user root:
shareall
Creation of a new account

Create an account to use the remote OMC-R. The account is also created on the remote_sys
Single Platform Processors with the same username and UID as that created on the local
machine.
Refer to the Motorola manual Operating Information: OMC-R System Administration
(68P02901W19) for details about how to add a user to the remote Single Platform Processor.
Use the same username, UID, and group of omcread or omcwrite.
7-30
68P02901W47-S
Jul 2008
Monitoring an alternative OMC-R from a GUI server
Monitoring an alternative OMC-R from a GUI server
Prerequisites for switching to alternative Single Platform

Processor
Before switching to an alternative Single Platform Processor from the GUI server, the following
conditions must exist:
Each Single Platform Processor on the LAN must be a NIS master. (This is standard under
the current supported OMC-R configuration.)
The NIS domain name on each Single Platform Processor on the LAN must be unique.
The maps for each NIS domain must contain a complete list of all Single Platform Processor
hostnames on the LAN.
Ensure that the Remote System Processor is NFS sharing the following file systems
to the GUI server:
/usr/omc/ne_data
/home
The GUI server must have an entry for the Remote System Processor in /etc/hosts file.
The Remote System Processor must have an entry for the GUI server in /etc/hosts file.
NOTE
Refer to Operating Information: OMC-R System (68P02901W19) for details.
68P02901W47-S
7-31
Jul 2008
Switching to an alternative Single Platform Processor

Follow the steps in Procedure 7-13 to switch to an alternative Single Platform Processor:
Procedure 7-13
Login to the GUI server as root and make sure that there is no GUI running
on the GUI server. Initially the GUI server /etc/hosts file should look similar
to the following:
127.0.0.1 localhost
111.111.11.12 local_gui
111.111.111.11 local_sys omc_splat omc_pm omc_4gl
111.111.11.13 guiclient1
111.111.111.21 remote_sys
Edit the GUI server /etc/hosts file so that the remote_sys is aliased to
omc_splat, omc_pm and omc_4gl:
127.0.0.1 localhost
111.111.11.12 local_gui
111.111.111.11 local_sys
111.111.11.13 guiclient1
111.111.111.21 remote_sys omc_splat omc_pm omc_4gl
To switch over to an alternative Single Platform

Processor, execute the following command:
/usr/omc/current/sbin/SwitchSPLAT <remote_sys>
Where <remote_sys>is the hostname of remote Single Platform Processor.
NOTE
The GUI server automatically reboots.
7-32
68P02901W47-S
Jul 2008
Chapter
8
Cisco 3662 Installation
68P02901W47-S
Jul 2008
8-1
Cisco 3662 router
Cisco 3662 router
Background
All communication between the OMC-R and BSS is based on the X.25 protocol. The Cisco 3662
Router is used to establish the X.25 communication circuits (Virtual Circuits) between the
OMC-R and BSS. This chapter contains the following sections:
Cisco 3662 router (this section)
Connectivity, configuration, and LAN connection
Establishing OMC and GSM connections
Enabling X.25 routing and creating Hunt Groups
Creating X.25 routes
Useful Cisco commands
NOTE
This Cisco 3662 router may have been pre-configured before leaving Motorola
staging.
Prerequisites
A PC or laptop is required to perform the initial and basic router setup.
The following information is required to complete the Cisco 3662 setup.
New IP address and subnet mask for the Cisco 3662.
Default Gateway to communicate with other Local Area Networks.
X.25 configuration information for the OMC-R. All of the necessary X.25 information
can be retrieved from the x25_config file on the live OMC-R. This file is located in the
/usr/omc/config/global directory of the OMC platform. The following information is
required for each GSM Network Element being connected:
The timeslot being used
The DTE address of the Network Element
8-2
68P02901W47-S
Jul 2008
Introduction
Introduction
The Cisco 3662 router contains serial ports and channelized E1 ports for connecting the OMC-R
to the GSM network. This section gives a brief overview of the hardware and cables used,
and details the capacity of the 3662.
Router
The 3662 router contains six modular expansion slots. Each slot is capable of hot-swapping
network modules to allow for high availability. The configuration of the router dynamically
updates upon insertion or removal of network modules. The Console port located on slot 0 of
the router is used for the initial and basic configuration. There are two Fast Ethernet ports on
Slot 0 (top of the chassis).
Once the initial and basic configuration steps have been completed, connect through the
Ethernet 0/0 port to perform the rest of the configuration. However, this can also be achieved
through the Console connection. This Ethernet connection can also be used to debug,
troubleshoot, and monitor the X.25 packet switching if necessary.
The Cisco 3662 router contains 256 MB of SDRAM and 16 MB of flash to store the Internet
working Operating System (IOS). Refer to Figure 8-1 for identifying the positions of the different
slots on the 3662 router.
Figure 8-1
3662 router
ti-gsm_The_3662_router-0066-ai-sw
68P02901W47-S
8-3
Jul 2008
Four Port Serial Interface

The Four Port Serial Interface module has four ports numbered from 0 to 3. Each port can have
a data rate of 2 Mbps. The ports are identified in the Cisco configuration file by <slot number /
port number>. Refer to Table 8-1 for identifying the required number of modules for OMC
connectivity and the recommended slots used. Figure 8-2 is a pictorial view of the module.
Figure 8-2
Four Port Serial Interface module to connect to the OMC
Two port channelized E1 interface

The channelized E1 ports are used to connect the GSM BSS equipment. Each E1 port can
receive and transmit data bi-directionally at 2.048 Mbps, and provide up to 31 virtual channels.
Each individual channel or time slot can be configured as a separate serial interface. Each E1
card contains two physical 120 Ohm E1 ports. To connect 75 Ohm Network Elements, a 75-120
Ohm Adapter Cable is used. These ports are identified in the Cisco configuration file by <slot
number / port number>. For consistency, the first E1 card is inserted in slot 3, the second
into slot 4, and so on (reserve slots 1 and 2 for Four Port Serial Interface modules).
Refer to Table 8-1 for information on the recommended slots usage. The port numbers on
the E1 card are labeled as CTRLR 0 and CTRLR 1. Refer to Figure 8-3 for a pictorial view of
the channelized E1 module.
Figure 8-3
8-4
Two port channelized E1 interface to connect GSM network elements
68P02901W47-S
Jul 2008
Table 8-1
Slot
Number
Recommended slot usage on the Cisco 3662

Port Type
Four Port
Serial I/F
Four Port
Serial I/F
Two Port
E1 Module
3 - 4
5 - 6
Router capacity
Port
Number
Connected
System
Cable Type
Electrical Spec /
Clock Source
OMC
EIA/TIA-449
X.21 / DCE
OMC
EIA/TIA-449
X.21 / DCE
OMC
EIA/TIA-449
X.21 / DCE
Interconnect
RS-530/X21
X.21 / DCE
OMC
EIA/TIA-449
X.21 / DCE
OMC
EIA/TIA-449
X.21 / DCE
OMC
EIA/TIA-449
X.21 / DCE
Interconnect
RS-530/X21
X.21 / DCE
GSM NE
DB-15 to RJ45
E1
GSM NE
DB-15 to RJ45
E1
GSM NE
DB-15 to RJ45
E1
Two Port E1 Modules

for expansion
NOTE
The Interconnect connections are optional for redundancy or expansion.
Router capacity
Any of the six available slots in the 3662 router can host either a Four Port Serial module or a
Two Port E1 module. Refer to Figure 8-1 for the recommended slot usage.
Two Four Port Serial modules are used for OMC connectivity, leaving the remaining four slots
for E1 connections.
Cables used
DB-[Number] is an indication of the connector type. The number refers to the number of pins in
the connector.
68P02901W47-S
8-5
Jul 2008
Cables used
Six different cable types are used on the 3662:
DB-60 to DB-37-Female (EIA/TIA 449 DCE)

Cable connection from the Serial ports in slots 1 and 2 to the OMC HSI
DB-15 to RJ45 (Cable for Balanced 120 Ohm)

Cable connection from the E1 modules to the GSM equipment
120 - 75 Ohm Adapter Cable (RJ 45 to BNC)

Only necessary for 75 Ohm BSC connections
DB-60 to DB-25-Male (RS-530 DTE)
DB-60 to DB-15 (CAB-X21)

Used to inter-connect 3662 router with another 3662 router
CAT 5 Ethernet cable

Connection for LAN communications
Console Cable Kit (supplied by Cisco)

Rollover Console cable
RJ45 to DB-9 Adapter
8-6
68P02901W47-S
Jul 2008
Introduction
Prerequisites
Establishing console connection
Initial configuration
Configuring the hostname and passwords
Connecting and configuring the LAN connections
Prerequisites
A PC or laptop computer running Windows NT or 2000 is required. The Console rollover cable
and RJ45 to DB-9 adapter is used in this section.

To establish the console connection, proceed as follows:
Procedure 8-1
Plug one end of the Cisco Console cable into the port labeled Console on Slot
0 at the rear of the router.
Plug the other end of the cable into the RJ45 port of the DB-9 adapter, and
plug the DB-9 connector into the COM serial port of the PC or laptop.
On the connected PC or laptop, start a Terminal Emulator. In

this example, the emulator is HyperTerminal, which comes as
standard with Microsoft Windows. To start HyperTerminal,
select the following after logging on to the PC or laptop:Start
Programs Accessories [Communications] HyperTerminal
The Communications menu is in brackets as it may not be present in all
Windows Operating Systems. The Connection Description dialog box is
displayed.
Enter a name and choose an icon from the Connection Description dialog
box. In this example, the name is Cisco 3662. Click OK to proceed.
Connect To dialog box is displayed (refer to Figure 8-4).
Continued
68P02901W47-S
8-7
Jul 2008
Procedure 8-1
5
Establishing console connection (Continued)
In the Connect To dialog box (Figure 8-4) , expand the options available in
the Connect using field and select the appropriate COM port. Click OK
to proceed.
Figure 8-4
Connect To dialog box
ti-gsm_Connect_T o_dialog_box-0069-ai-sw
The COM Properties dialog box is displayed.

Continued
8-8
68P02901W47-S
Jul 2008
Procedure 8-1
6
Set the COM Properties dialog box fields to the values shown in Figure 8-5
and click OK.
Figure 8-5
COM Properties dialog box
ti-gsm_COM_Properties_dialog_box-0070-ai-sw
HyperTerminal automatically connects to the configured port. The Connected

status and time can be seen at the bottom of the HyperTerminal screen. If the
status is Disconnected, the port can be reconnected by selecting the following
from the menu bar: Call Call. The prompt is not seen until the router is
turned on in the next step.
Once the previous section is complete, follow Procedure 8-2 to perform the initial configuration.
68P02901W47-S
8-9
Jul 2008
Procedure 8-2
Power on the 3662 router.
NOTE
The 3662 router must be physically close to the OMC and Local
Area Network to accommodate the length of the cables.
When the Cisco router is first powered on, it goes through the Power
On Self Tests (POST). Several messages are displayed on the Console.
Once these are successfully completed, the router looks for an
Internetworking Operating System (IOS) to boot. The IOS to boot from
can be specified in the configuration file that is stored in the routers
non-volatile RAM. However, because this is the first time the router is
powered on, the configuration in NVRAM is empty. This causes the
router to search for a valid operating system in the flash memory.
The first valid IOS that is available in the flash memory is loaded.
Once the IOS has been identified and loaded, the router starts an interactive
session with the user to configure the router, and displays this prompt:
Would you like to enter the initial configuration dialog?
[yes/no]:
no
2
The interactive configuration session is not used when the router is installed.
Therefore, answer no at the above prompt.
NOTE
If you inadvertently choose yes at this point, return to the above
prompt by powering the router off and then on again.
The router displays this prompt:
Would you like to terminate auto install? [yes]:
3
Press Return to terminate auto install. The router proceeds to complete the
boot up. Several interface state change messages are displayed until the
router completes its boot up.
Once boot up is complete, press the Return key.

The following prompt is displayed:
Router>
This is the basic user level prompt. At this user level, basic router commands
can be used to show interfaces that exist, the IOS version that is running,
memory status and other information. The router must be in privilege
execution mode to perform any configuration changes.
Continued
8-10
68P02901W47-S
Jul 2008
Procedure 8-2
5
Initial configuration (Continued)
To enter privilege mode, enter the following command at the Router prompt:
Router> enable
The router prompt changes to the prompt below, signifying that it is now
at a level wherein the administrator has full privileges. This is known as
the privilege level. Privileged mode includes user mode functionality and
provides unrestricted access. It is used exclusively for router configuration,
debugging, setting Operating System (OS) parameters, and retrieving
detailed router status information.
Router#
The basic router configuration in the next section can be performed now.

The following configuration steps show the commands that have to be entered in bold text.
Prompts and messages are displayed for indication purposes only.
Text within the <> characters are user-specific.
Setting the hostname

From the privilege prompt that was established at the end of the last section, (Router#) perform
the following steps:
Procedure 8-3
Execute the following command to enter global configuration:

Router# configure terminal
Enter configuration commands, one per line. End with CTRL/Z.
Router(config)#
Enter the following command to set the hostname: Router(config)#

hostname <X25-3662>
X25-3662(config)#
NOTE
The hostname X25-3662 is used in examples throughout this
document. Change this to conform to the network operators
naming convention. The new hostname is now displayed.
68P02901W47-S
8-11
Jul 2008
Setting the passwords

Passwords can be set at three different points of the Cisco configuration:
Console password: Users are prompted for this password when connected directly to the
Console port of the router.
Telnet line password: Users are prompted for this password after initiating a telnet
session to the router.
Enable password: This password is requested on entering privilege level to configure

the router.
NOTE
Console and telnet passwords give user level access to the router. At this level,
the operator can use the show commands to view the status of the router. The
enable password gives the operator full privileges on the router.
While remaining in global configuration mode from Setting the hostname, perform the following
procedure:
Procedure 8-4
Enter the following commands to set the console password:

X25-3662(config)# service password-encryption
X25-3662(config)# line console 0
X25-3662(config-line)# password 0 <password>
X25-3662(config-line)# login
X25-3662(config-line)# exit
NOTE
Notice how the router prompt changes to identify the current
configuration level. The exit command is used to exit the line
configuration mode and return to global configuration.
2
Enter the following commands to set the telnet passwords:

X25-3662(config)# line vty 0 4
Enter the following commands to set the enable password:

X25-3662(config)# enable password 0 <password>
X25-3662(config)# CTRL-z
CTRL-z ends the configuration session and exits the user to the privilege
router level. The following message is displayed:
Configured from console by console
8-12
68P02901W47-S
Jul 2008
Connecting and configuring the LAN connection

At this point, the Ethernet connection to the Local Area Network (LAN) can be established.
Connect the port labeled Ethernet 0/0 at the back of the 3662 to a LAN Hub or switch to
which there is a workstation connected. The CAT 5 twisted pair cable is used to establish the
physical connection.
NOTE
It is also possible to configure the router through the existing console connection, in
which case this procedure can be skipped.
Configuring the LAN connection

From the router privilege prompt, perform the following procedure.
Procedure 8-5
Configure the FastEthernet connection by entering the following at the

prompt:
X25-3662# configure terminal
X25-3662(config)# interface fastEthernet 0/0
X25-3662(config-if)# ip address <IP Address> <Subnet Mask>
X25-3662(config-if)# no shutdown
X25-3662(config-if)# exit
NOTE
The following message should be seen on the console indicating
that the link has come up:
Line protocol on Interface FastEthernet0/0, changed
state to up
2
Use the following command to set a default route. This allows the router
to communicate with other Local Area Networks. Refer to the network
administrator for these parameters, if necessary:
X25-3662(config)# ip route 0.0.0.0 0.0.0.0 <Gateway Address>
X25-3662#
Verify that the LAN connection is up by entering the following command:

X25-3662# show interface fastEthernet 0/0
The first line identifies if the FastEthernet link is up by displaying the following:
FastEthernet0/0 is up, line protocol is up
Continued
68P02901W47-S
8-13
Jul 2008
Procedure 8-5
4
Configuring the LAN connection (Continued)
A telnet session can now be established to the Cisco 3662 router from a
workstation on the same LAN.
NOTE
Remain connected on the console while testing telnet connectivity
from another workstation. This is a safe way to verify that all
passwords are set correctly.
To establish a telnet session, perform the following from a workstation:
telnet <IP Address set in step 1 above>
User Access Verification
Password: <Password set for line vty 0 to 4>
X25-3662> enable
Password: <enable password>
X25-3662#
8-14
After completing the previous step, all configurations to this point have been
verified. The configuration changes made in all the previous steps can now be
saved to Non- Volatile RAM on the router to make them permanent. Without
doing this, a router reboot loses all configuration set in previous steps. To
save these changes, do the following:
X25-3662# write memory
The console connection that was established to do the basic router

configuration can now be disconnected after exiting.
68P02901W47-S
Jul 2008
Introduction
The following are covered in this section:
Configuring X.25 profiles
Establishing serial connections to the OMC
Connecting the router to the OMC
Configuring the serial interfaces to the OMC
Establishing and configuring connections to the GSM equipment
Controllers and channel groups
Creating channel groups
Configuring the serial interfaces

Profiles are used to configure X.25 parameters that are common to several interfaces. Two
profiles are created in this sub-section, one for the OMC and one for the GSM equipment.
Further X.25 parameters need to be changed once within the appropriate profile. These
changes will then take effect in all interfaces using this profile.
Perform the following from privilege level to configure the X.25 profiles:
Procedure 8-6
Configuring the X.25 profiles
To configure the OMC X.25 profile, perform the following:

X25-3662(config)# x25 profile OMC dce
X25-3662(config-x25)# no x25 security crcdn
X25-3662(config-x25)# x25 htc 64
X25-3662(config-x25)# lapb T4 4
X25-3662(config-x25)# lapb N2 10
X25-3662(config-x25)# exit
X25-3662(config)#
Continued
68P02901W47-S
8-15
Jul 2008
Procedure 8-6
2
Configuring the X.25 profiles (Continued)
To configure the GSM X.25 profile, perform the following:

X25-3662(config)# x25 profile GSM dce
X25-3662(config-x25)# x25 ltc 1024
X25-3662(config-x25)# x25 htc 1055
NOTE
The default packet size is 128 and the window size is 2.

The X25_config file
The X.25 configuration file, configured during the OMC-R installation, defines which
HSI (High Speed serial Interface) lines are used. The x25_config file is located in the
/usr/omc/config/global directory of the OMC-R. Each line in this file contains eleven fields.
These fields are defined in Table 8-2. A sample configuration file is shown in Table 8-3.
Table 8-2
Field
Comments
Record Number
X.25 Channel Number
The format is x25_chan<nn>, where nn is

the record number.

numbers in the x25_config file must
numbers.
The recommended X.121
address format is as follows:
Digits 6 to 10 are
equipment specific indicators.
Continued
8-16
68P02901W47-S
Jul 2008
Table 8-2
Field
Comments
Interface Type
A value of H relates to SunLink HSI/S.
A value of - relates to a calling process.

Any other value in this field relates to a
listening process.
OMC-R Process

Protocol .
Set to X.25.
Packet Size
For example, 128.
Window Size
For example, 2.
Time Out Parameter
For example, 50 or 500
Table 8-3
Sample X25_config file for an OMC
Record
Number
X.25
Channel
Number
Sunlink
X.25 link
number
x25_chan1
68P02901W47-S
X.121
Address
Process Call
Characteristic
OMC-R
Process
Time Out
Parameter
2020130
000061
g_bootload
OMC_BL
50
x25_chan2
2020130
001062
g_bootload
OMC_BL
50
x25_chan3
2020130
000241
g_ei
OMC_EI
500
x25_chan4
2020130
001142
g_ei
OMC_EI
500
x25_chan5
2020130
000200
OMC_RL
500
x25_chan6
2020130
001299
OMC_PU
50
x25_chan7
2020130
001299
OMC_PU
50
x25_chan8
2020130
001299
OMC_PU
50
x25_chan9
2020130
001299
OMC_PU
50
8-17
Jul 2008
Interface Type = H
Protocol = X25
Packet size = 128
Window size = 2
NOTE
Refer to the x25_config that is customized to your network.
OMC platforms have two HSI cards. Each HSI card has four serial ports. With two HSI cards,
redundancy is built into the X.25 network. Table 8-4 shows which ports (column 3) are defined
for each process (column 7). The Upload processes are initiated from the OMC and use links 0,
2, 4 and 6. The Rlogin Process uses link 1. Later in this section, there is a procedure for using
the Upload and Rlogin HSI ports for Bootload and Event Interface traffic, increasing the overall
performance and capacity of the X.25 network.

DB-60 to DB-37 (EIA/TIA 449 DCE) cables are used to make the connection between the
router and the OMC. The female ends of the 449 DCE cables are connected to the female HSI
connectors using 37-way to 37-way gender changers.
Before making the physical connections between the OMC and the router, refer to Table 8-4 to
determine the physical port connections at either end.
To complete the physical connections, repeat this procedure for each HSI port used in the
x25_config file:
Procedure 8-7
8-18
Determine the first physical port to be used on the OMC HSI (refer to the third
column on the first line of the x25_config file). In this case (from Table 8-3),
port 0 is the first port to be used. Connect the DB-37 male gender changer to
this port, connect the DB-37 female end of the 449 DCE cable to the other
side of the gender changer.
Refer to Table 8-4 to identify the corresponding router port. In this case, port
0 on the OMC side connects to 1/0 on the router.
Connect the DB-60 end of the 449 DCE cable to the appropriate port on the
Cisco 3662.
68P02901W47-S
Jul 2008
Table 8-4
Physical Port connections at the OMC and Cisco 3662
OMC-R HSI Port Number
Cisco 3662
Port 0
Connects to 1/0
Port 1
Connects to 1/1
Port 2
Connects to 1/2
Port 3 (Not Used)
Connects to 1/3
Port 4
Connects to 2/0
Port 5
Connects to 2/1
Port 6
Connects to 2/2
Port 7 (Not Used)
Connects to 2/3
In the above table, the OMC-R HSI Port Number is defined in column 3 of the x25_config file.
Cisco 3662 refers to the lot number or the link number.

Each of the serial interfaces that connect to the OMC has the same configuration. Perform the
following from the privilege level for each of the interfaces that connect to the OMC:
If a telnet session is used to configure the router, enter the following from the privilege
level:
X25-3662# terminal monitor
This command is used to monitor messages that are displayed on the Console port. Once
this command is entered, all Console messages for the period of this telnet session are
seen. This is useful to see the interface states changing as they are configured.
Enter the global configuration mode:

Execute these commands for each serial interface that is connected to the
OMC. The only parameter change necessary is the physical interface number:
X25-3662(config)# interface serial <slot number/port number>
68P02901W47-S
8-19
Jul 2008
NOTE
The physical interface number is the same format as shown in Table 8-4.
The first interface to be configured is interface 1/0.
X25-3662(config-if)# encapsulation x25 profile OMC
X25-3662(config-if)# clockrate <clock rate>
The recommended clock rate for an E3x00 OMC is 256000. The

recommended clock rate for a Netra / SunFire OMC is 356000.
The following lines should be displayed indicating that the serial line is up:
Interface Serial{Slot # / Port #}, changed state to up.
Line protocol on Interface Serial{Slot # / Port #}, changed state to up.
X25-3662(config)#
Repeat step 3 for all OMC connected interfaces. Using the x25_config file
in Table 8-3 as an example, the following interfaces on the router need to
be configured as described in the above steps:
interface
interface
interface
interface
interface
interface
serial
serial
serial
serial
serial
serial
1/0
1/1
1/2
2/0
2/1
2/2
Once all the interfaces are configured, save the configuration and verify that the interfaces
are up by doing the following:
X25-3662(config)#
X25-3662(config)# ^Z
X25-3662# show interface serial <slot number/port number>
The first line of the output indicates that the serial interface link is up by displaying this message:
Serial1/0 is up, line protocol is up.
8-20
68P02901W47-S
Jul 2008
Show interface summary

The following command can also be used to identify the link status:
X25-3662# show interface summary
Each line output contains information about one interface. All interfaces that are up have an
asterisk (*) displayed to the left of the line. An example of the output showing the interface
states is shown as follows:
Interface
IHQ
IQD
OHQ
OQD
RXBS
RXPS
TXBS
TXPS
TRTL
* FastEthernet0/0
663
4000
10
3000
* FastEthernet0/0
* FastEthernet0/0
* FastEthernet0/0
31000
44
2000
97
* FastEthernet0/0

Prerequisites
The number of physical E1 connections required depends on the topology of the GSM network.
In this section, it is necessary to know the following:
Which GSM network elements need to be connected to the router? The total number of network
elements that can be connected to the router depends on the number of channelized E1 cards in
the router. Each channelized E1 card has two E1 interfaces and each E1 interface supports 31
DS0 (64K) timeslots.
The type of physical cables to use depends on the GSM Network Elements. These are
either 120 Ohm or 75 Ohm. For 75 Ohm Network Elements, the 120 - 75 Ohm Adapter
Cable is required.
The timeslots to which the NEs are mapped on each E1 connection.
68P02901W47-S
8-21
Jul 2008
Establishing the connection

The DB-15 to RJ45 cables are used to connect 120 Ohm GSM Network Elements to the router.
The Interface pinouts for the 120 Ohm cable are shown in Table 8-5. To connect 75 Ohm GSM
Network Elements to the router, the 120 - 75 Ohm Adapter Cable is required. Connect the RJ45
plug at the end of the DB-15 to RJ45 cable to the RJ45 socket on the 120 - 75 Ohm Adapter Cable.
Make all the necessary connections, taking note of which GSM Network Element is connected to
which physical E1 port. Once a proper connection has been established, the Local Alarm light
on the physical E1 interface should disappear and the Carrier Detect light should go green. The
E1 port numbers follow the same numbering scheme as the serial ports that connect to the OMC
with the exception that there are only two ports. Once all the physical connections have been
established, the interfaces to the Network Elements can be created.
Table 8-5
DB-15 to RJ45 120 Ohm cable pinouts
2 Port Channelized E1 End
Network End
DB-15
RJ45
Pin
Signal
Pin
Signal
Tx Tip
Tx Tip
Tx Ring
Tx Ring
10
Tx Shield
Tx Shield
Rx Tip
Rx Tip
15
Rx Ring
Rx Ring
Rx Shield
Rx Shield

Each physical E1 interface is logically created on the Cisco 3662 as a controller. Each controller
has 31 64K timeslots available to it. In this section, multiple channel groups are created within
each controller (one channel group per NE). The purpose of the channel group is to define the
associated timeslot(s). Table 8-6 summarizes the steps taken to create connections to the NE.
NOTE
Use Table 8-6 for reference purposes only.
To view the controllers that exist on the Cisco 3662, execute the following command from
privilege level:
X25-3662# show running-config
8-22
68P02901W47-S
Jul 2008
Following is an excerpt from a sample configuration file showing two controllers, the first
controller is port 0 in slot 3 of the router, and the second is port one in slot 3:
controller E1 3/0
!
controller E1 3/1
Press the space bar to page through the rest of the running configuration file.
Table 8-6
Sequence of steps to create serial interfaces

Command reference
(do not execute)
Step
Purpose
controller E1 <slot
number/port number>
To enter the controller to be configured. The

prompt changes to reflect the new configuration
level.
channel group <channel

#> timeslots <timeslot
number(s)>
A separate channel group is required for

every NE that is connected to this controller.
It is possible to allocate several timeslots
to one channel group. However, only
one 64K timeslot is allocated to each NE.
<channel #> starts at 0 and continues
to 30. <timeslot number(s)>
starts at 1 and continues to 31.
The fist channel group that we create
uses channel # 0 and timeslots 1, the second
uses channel # 1 and timeslots 2 and so on
(timeslots 2 refers to timeslot 2, not 2 timeslots).
Each channel group created automatically
creates a serial interface. This interface is
configured in a later step for the X.25 profile
created for GSM.
Exit
This step exits controller configuration level

and returns to global configuration mode. At
this point, step 1 and 2 can be repeated to
create channel groups in other controllers.
interface serial <port

number / slot number:
channel #>
To enter the serial interface created

from the associated channel group.
<port number / slot number> indicates
the controller (physical E1 port)
<:channel #> indicates the channel
group.
encapsulation x25 profile

GSM
This step configures the serial interface to use

the GSM profile created at the start of this
section.
Exit
This step exits serial configuration level and

returns to global configuration mode. At this
point, step 4 can be repeated to configure other
serial interfaces.
68P02901W47-S
8-23
Jul 2008

Use the following steps to create the channel groups in the controllers. These in turn
automatically create the serial interfaces, which tie into the appropriate timeslot.
Procedure 8-8

NOTE
For example, the first available controller is

typically 3/0, assuming the E1 Interface resides
in slot 3. The following command is used:
controller E1 3/0
By default CRC4 framing is turned on. To turn off the CRC4

framing, use the following command inside the controller:
framing no-crc4
Enter the appropriate controller:

X25-3662(config)# controller E1 <slot number/port number>
NOTE

controller E1 3/0
By default CRC4 framing is turned on. To turn CRC4

framing off, use the following command inside the controller:
framing no-crc4
Create the channel group:

X25-3662(config-controller)#channel group <channel #>
timeslots <timeslot number(s)>
NOTE
Timeslot numbering starts at 1 for timeslot 1 and work up

to 31 for timeslot 31. Channel # is always one less than
the timeslot number. For example, to configure the first
three timeslots, the following needs to be entered in step 3:
Continued
8-24
68P02901W47-S
Jul 2008
Procedure 8-8
Creating channel groups (Continued)
channel group 0 timeslots 1

To configure all timeslots in the controller, continue to:

Motorola recommends creating channel groups only for the timeslots

being used, that is, for connected NEs.
For further information on this command, refer to Table 8-6.
As the interfaces are created, the following message is displayed for

each Serial Interface created:
Line protocol on Interface Serial{port number/slot number:
channel #}, changed state to down
Repeat Step 3 for all timeslots in this controller.

4
Exit Controller:
X25-3662(config-controller)# exit
To create further channel groups (serial interfaces) on other controllers,

repeat steps 2 through 4. Once all of the necessary channel groups have
been created, do the following:
To verify that the channel groups are established within the controller and
that the serial interfaces are created in the configuration file, do the following:
NOTE
The channel groups configured in the previous note have the
following serial interfaces created in the configuration file
(assuming that controller 3/0 was used):
The Channel number is the timeslot number minus 1.
interface Serial3/0:0 (For Timeslot 1)
no ip address
!
no ip address
!
no ip address and so on.
68P02901W47-S
8-25
Jul 2008
Configuring the serial interfaces (to the GSM Network Elements)
Configuring the serial interfaces (to the GSM Network

Elements)
Each serial interface created needs to be configured to use the GSM X.25 profile created at the
start of this section. Perform the following from privilege level.
Procedure 8-9

Use the following commands to configure the encapsulation on the serial

interface:
X25-3662(config)# interface serial <port number / slot
number:channel #>
NOTE
The channel number is the timeslot number minus 1.
X25-3662(config-if)# encapsulation x25 profile GSM
3
Repeat step 2 for all serial interfaces created. Once all interfaces are
configured, save the configuration and verify that the interfaces are up by using
the following commands:
X25-3662(config)#
X25-3662# show interface serial <slot number/port
number:channel #>
X25-3662#show interfaces serial 3/0:0
Serial3/0:0 is up, line protocol is up
Hardware is DSX1
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation X25, loopback not set
X.25 DCE, address <none>, state R1, modulo 8, timer 0
Defaults: idle VC timeout 0
cisco encapsulation
input/output window sizes 2/2, packet sizes 128/128
Timers: T10 60, T11 180, T12 60, T13 60
Channels: Incoming-only none, Two-way 1024-1055,Outgoing only none
RESTARTs 0/0 CALLs 0+0/0+0/0+0 DIAGs 0/0
LAPB DCE, state CONNECT, modulo 8, k 7, N1 12056, N2 10
Continued
8-26
68P02901W47-S
Jul 2008
Procedure 8-9
Configuring the serial interfaces (Continued)
T1 3000, T2 0, interface outage (partial T3) 0, T4 4

VS 3, VR 4, tx NR 4, Remote VR 3, Retransmissions 0
Queues: U/S frames 0, I frames 0, unack. 0, reTx 0
IFRAMEs 0/0 RNRs 0/0 REJs 0/0 SABM/Es 0/0 FRMRs 0/0 DISCs 0/0
Last input never, output 00:00:02, output hang never
Last clearing of show interface counters 00:00:08
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
2 packets input, 4 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored,0 abort
2 packets output, 4 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
Timeslot(s) Used:1, Transmitter delay is 0 flags X25-3662#
The first line of the output indicates that the serial interface is up with this
message:
The last line identifies the timeslot being used.

Each output line contains information about an interface. All the interfaces that are up have an
asterisk (*) displayed at the beginning of the line. Use the space bar to page through the output.
68P02901W47-S
8-27
Jul 2008
Introduction
X.25 routing is enabled on the 3662 router to allow Virtual Circuits to be routed from one
serial interface to another.
Once X.25 routing has been enabled, the X.25 routes can be created. X.25 routes are created
in the next section.
Hunt Groups are used as a method of load balancing across several serial links. In this section,
Hunt Groups are created to load balance the NE Virtual Circuits across the serial interfaces
that connect the OMC.
Enabling X.25 routing

To enable X.25 routing, do the following from privilege level on the 3662 router:
Procedure 8-10
Enter global configuration mode:

Enable X.25 routing by entering the following:

X25-3662(config)# x25 routing
Save the configuration:

Creating X.25 Hunt Groups

Two Hunt Groups are created for load sharing the serial connections to the OMC.
BOOTLOAD: This Hunt Group shares the serial connections that are used for bootload. For
example, if six NEs are bootloading at the same time, they are evenly distributed across all
interfaces that are defined in this Hunt Group.
EVENTS: This Hunt Group shares the serial connections that are defined for event
interface.
There are two types of Hunt Groups available, vc-count and rotary. Motorola recommends
the use of vc-count, as this method sends calls to the interface that has the largest number of
available logical channels. This method ensures a good load balance when lines are of equal
speed.
8-28
68P02901W47-S
Jul 2008
Creating the BOOTLOAD Hunt Group
At least two serial interfaces participate in each of these Hunt Groups. This is because two lines
in the x25_config file are defined for Bootload (lines 1 and 2) and two lines are defined for Event
Interface (3 and 4). However, because the OMC can route Bootload and Event data to the
correct process from any of the HSI ports, all of the connected serial lines (that connect to the
OMC) can participate in each Hunt Group.
NOTE
If any of the serial interfaces participating in the Hunt Group are down or not
connected, the interface shows them as being unavailable in the Hunt Group upon
entering the command
show x25hunt-group

Serial 1/0 and Serial 2/0 are the two bootload channels defined in the x25_config example in
Table 8-3 (column 6 in the x25_config file defined the process, g_bootload for BOOTLOAD
and g_ei for EVENTS). Refer to the x25_config file on the live OMC to determine these ports.
Minimally, the two ports defined for g_bootload participate in the BOOTLOAD Hunt Group.
However, Motorola recommends that all serial connections to the OMC are included in the Hunt
Group, making better use of the serial interfaces, increasing redundancy and capacity.
For example, if the two g_bootload serial lines are disconnected, the Network Element can still
bootload from one of the other available lines participating in the Hunt Group.
Perform the following steps from privilege level to create the BOOTLOAD Hunt Group:
Procedure 8-11

Create the Hunt Group:

X25-3662(config)# x25 hunt-group BOOTLOAD vc-count
X25-3662(config-x25-huntgroup)# interface serial <slot
number / port number>
NOTE
68P02901W47-S
Repeat the last command for all serial interfaces participating

in the Hunt Group.
The following ports participate in the Hunt Group for a typical

OMC-R: 1/0, 1/1, 1/2, 2/0, 2/1, 2/2
Exit the global configuration mode:

X25-3662(config-x25-huntgroup)# exit
8-29
Jul 2008
Creating the EVENTS Hunt Group

Serial 1/1 and Serial 2/1 are the two event channels in the x25_config example. Refer to
x25_config file on the live OMC to determine these ports. Minimally, these two ports participate
in the EVENT Hunt Group. Motorola recommends that all serial connections to the OMC are
included in the Hunt Group, making better use of the serial interfaces, increasing redundancy
and capacity.
Perform the following steps from privilege level to create the EVENTS Hunt Group:
Procedure 8-12

X25-3662(config)# x25 hunt-group EVENTS vc-count
X25-3662(config-x25-huntgroup)# interface serial <slot number /
port number
NOTE
Repeat the last command for all serial interfaces participating in
the Hunt Group.
OMC-R: 1/0, 1/1, 1/2, 2/0, 2/1, 2/2.
2

Verifying the X.25 Hunt Groups

Make sure that the Hunt Groups have been created properly by executing the following
command:
X25-3662# show x25 hunt-group
The output displays information about each Hunt Group.
8-30
68P02901W47-S
Jul 2008
X25-3662#sh x25 hunt

ID
Type
Target
uses
status
traffic (out/in)
===========
========
==========
=========
=============
==============
BOOTLOAD
vc-count
Serial1/0
1 VC
280555/370
Serial2/0
1 VC
2657/132
Serial1/1
1 VC
7862/197
Serial2/1
1 VC
2651/132
Serial1/2
0 VC
0/0
Serial2/2
0 VC
0/0
Serial1/1
1 VC
7862/197
Serial2/1
1 VC
2651/132
Serial1/0
1 VC
280555/370
Serial2/0
1 VC
2657/132
Serial1/2
0 VC
0/0
Serial2/2
0 VC
0/0
EVENTS
vc-count
X25-3662#
We can see that four NEs have EVENT connections, each using a different serial connection
back to the OMC platform, and no BSSs are BOOTLOADING (notice the 0 uses).
68P02901W47-S
8-31
Jul 2008
Introduction
In this section, the X.25 routing table is created. When the 3662 router receives an X.25 call
that must be forwarded, the X.25 routing table determines which destination to use. The routing
table is scanned sequentially from top to bottom and the first route that matches the address
criteria is used for the X.25 call. The user determines the order of the routing table when
entering new routes. This way, the user can control which routes should take precedence when
creating secondary or redundant links (that is, dual OMLs to the BSS).
X.121 addresses
In this section, it is important to know the addresses being used and the port-timeslot that they
are associated with. These addresses are referred to as X.121 addresses. An X.121 address is
assigned to each Network Element and each channel on the OMC. The X.121 address for the
OMC is defined in the x25_config file (column 4) and can be identified on the GSM NEs by
using the disp_dte command at the NE MMI prompt. The address is displayed in the NE DTE
addresses section. X.121 addresses are typically 14 digits in length.
An example of an addressing scheme is:
aaannddceehhxx
Where:
Is:
aaa
the country code
nn
the network code
dd
the location code
the type code:

1 BSS (EEHH = BSS Number), (XX should
be 00)
2 RXCDR
3 OMC
ee
the number of the OMC-R
hh
the HSI card and port number
xx
the function sub-address:

41 and 42 Event Interface
61 and 62 Boot Loader
00 Rlogin
99 Uploader
8-32
68P02901W47-S
Jul 2008
Adding routes into the routing table

Follow these steps to create the routing table on the router:
The routes that use the Hunt Groups are established.
The routes to the GSM equipment are established.
The optional position parameter allows the user to define the position of a route in the routing
tables.
The routing table is scanned from top to bottom; hence the first matching address is used to
establish virtual connections. If this connection fails, the next route that matches the address
criteria is used. If the position option is not used, then by default the first route added would be
in position 1, the next route would take position 2, and so forth.
NOTE
Optional parameters are in brackets [ ].
Creating routes to the OMC

The following commands set the routes to the OMC using the BOOTLOAD and EVENTS Hunt
Groups created in the last section. Refer to the x25_conf file for the x.121 addresses.
Procedure 8-13

Add the route:

X25-3662(config)# x25 route [# position] <X.121 address>
hunt-group <Hunt Group Name>
NOTE
The following is an example of the routes that would be necessary if
using the x25_config file in Table 8-3 and the Hunt Groups created
in the last section:
X25 route 2020130000061 hunt-group BOOTLOAD
X25 route 2020130000241 hunt-group EVENTS
3
68P02901W47-S
Repeat step two for all Hunt Group routes. To return to privilege level, type
the following:
X25-3662(config)#exit
8-33
Jul 2008
Creating routes to the GSM equipment

To create routes to the GSM equipment, perform the following:
Procedure 8-14

Repeat this command for all routes to the NE equipment, including secondary
OMLs:
X25-3662(config)# x25 route [# position] <X.121 address> interface
serial <slot number/port number:channel #>
NOTE
The channel # is only necessary when connecting to GSM network
elements on the E1 lines. In the following example, the primary
OML is routed out of timeslot 6 (channel 5) on controller 3/1. The
secondary OML is routed out of timeslot 6 on controller 4/1.
X25 route 41503002010000 interface serial 3/1:5
Saving the Configuration

Once all the routes have been created, exit and save the configuration by doing the following:
Verifying the routes

To verify that the routes have been established, use the following command from privilege level:
X25-3662# show x25 route
Refer to the commands in the section Useful Cisco commands on page 8-35 to verify that the
X.25 network is up.
8-34
68P02901W47-S
Jul 2008
Introduction
Useful Cisco Commands:

Router level commands
Interface commands
X25 Commands to verify the X.25 network
Backup and restore configuration
Making changes to the Cisco configuration:

Deleting routes
Deleting channel groups
Useful Cisco operating system commands

The following commands can be entered from the privilege level to view the status of the 3662
router. To get a full list of commands available, use the ? key. For example, the command
show ? displays all show options available:
To display the current live configuration in running memory:

show running-config
To display the configuration in NVRAM (the command write config copies the running
config to startup config):
show startup-config
68P02901W47-S
8-35
Jul 2008
To display the operating system version that is running:

show version
This command also displays:
The number of serial interfaces configured.
System up time.
Amount of NVRAM and Flash available.
To display the CPU utilization:

show processes
To set the date and time:

clock set <HH:MM:SS DD MONTH YYYY>
To show the date and time:

show clock
To clear all interface counters:

clear counter all
To show the contents of Flash:

show flash all
This command also shows the free space on Flash.
Interface commands
The following commands are useful to view the status of the 3662 interfaces.
To show the Interface status and characteristics:

show interface <slot number/port number<:channel number>>
X.25 characteristics.
Encapsulation type.
To show interface summary information, including status:

show interface summary
8-36
68P02901W47-S
Jul 2008
To show the controller information:

show controller
This command is useful for identifying the line framing and coding. It also displays:
Link speed
Physical connection type
Framing Error counts
X.25 commands
The following commands are useful to verify and monitor the X.25 network:
To show routing tables and usage:

show x25 route [| include <string>]
To show number of Virtual Circuits established:

show x25 services
To show Virtual Circuits that has been established:This command also shows window
size and packet size.
show x25 vc [| include <string>]
NOTE
The [include <string>] option can be used to search for text within the output.
This is useful as there are typically pages of output. For example, you could use
the following command to view all upload virtual circuits currently active:
show x25 vc | include 2020130000061

To back up the running configuration on the Cisco router to a tftp server, perform the following:
copy running-config tftp:
Enter the address of the tftp server when prompted.
Enter the destination filename when prompted.
68P02901W47-S
8-37
Jul 2008
Making changes to the Cisco configuration
NOTE
Depending on the setup of the tftp server, you may need to:
Create this file (as a blank file) with appropriate permissions on the tftp server.
Enter the full path at the Cisco prompt (This depends on the root directory
set on the tftp server).
To restore the running configuration from a tftp server, execute the following:
copy tftp running-config:
Enter the full path and filename when prompted.

Deleting routes
Use the following command to delete a route from the running configuration:
X25-3662(config)# no x25 route [ # position ] <X.121 address> interface serial
<Slot Number / Port Number>
OR
X25-3662(config)# no x25 route [ # position ] <X.121 address> hunt-group <Hunt
Group Name>
NOTE
To delete a route that was previously added, put no before the command that was
previously used to add the route while in global configuration mode.

Use the following commands to delete a channel group:
X25-3662(config-controller)# no channel group <channel #>
8-38
68P02901W47-S
Jul 2008
Chapter
9
Cisco 3845 Installation
68P02901W47-S
Jul 2008
9-1
Cisco 3845 router
Cisco 3845 router
Background
All communication between the OMC-R and BSS is based on the X.25 protocol. The Cisco 3845
Router is used to establish the X.25 communication circuits (Virtual Circuits) between the
OMC-R and BSS. This chapter contains the following sections:
Cisco 3845 router (this section)
Interconnect with another Cisco 3662 or 3845 router using X25-over-IP
NOTE
This Cisco 3845 router may have been pre-configured before leaving Motorola
staging.
Prerequisites
A PC or laptop is required to perform the initial and basic router setup.
The following information is required to complete the Cisco 3845 setup.
New IP address and subnet mask for the Cisco 3845.
Default Gateway to communicate with other Local Area Networks.
X.25 configuration information for the OMC-R. All of the necessary X.25 information
can be retrieved from the x25_config file on the live OMC-R. This file is located in the
/usr/omc/config/global directory of the OMC platform. The following information is
required for each GSM Network Element being connected:
The timeslot being used.
The DTE address of the Network Element.
9-2
68P02901W47-S
Jul 2008
Introduction to the Cisco 3845 router hardware
Introduction to the Cisco 3845 router hardware

The Cisco 3845 router contains serial ports and channelized E1 ports for connecting the OMC-R
to the GSM network. This section gives a brief overview of the hardware and cables used, and
details the capacity of the 3845. Use this section to become familiar with the slot numbering in
the 3845 and the port numbering on the interfaces that are contained in these slots.
Router
The 3845 router contains six modular expansion slots. Each slot is capable of hot-swapping
network modules to allow for high availability. Insert the network modules before clock rates,
hunt groups can be configured. The Console port located on slot 0 of the router is used for
the initial and basic configuration. There are two Gigabit Ethernet ports on Slot 0 (top of
the chassis). The first one is used for router configuration, the second one can be used as
an interconnect to another router.
Once the initial and basic configuration steps have been completed, connect through the
Ethernet 0/0 port to perform the rest of the configuration. However, this can also be achieved
through the Console connection. This Ethernet connection can also be used to debug,
troubleshoot, and monitor the X.25 packet switching if necessary.
The Cisco 3845 router contains 256 MB of SDRAM and 16 MB of flash to store the Internet
working Operating System (IOS). Refer to Figure 9-1 for identifying the positions of the different
slots on the 3845 router.
Figure 9-1
3845 router

The two Four Port Serial Interface (HWIC) modules have four ports numbered from 0 to 3.
Each port can have a data rate of 2 Mbps. The ports are identified in the Cisco configuration
file by <slot number / side number (i.e. 0/0 or 0/1)/ port number>. Refer to Table 9-1 for
identifying the required number of modules for OMC connectivity and the recommended slots
used. Figure 9-2 is a pictorial view of the module.
68P02901W47-S
9-3
Jul 2008
The HWIC cards support smart serial interfaces. This means that the type of interface is
defined by what cable is connected to each port. Cables must therefore be connected before
configuring the ports.
Figure 9-2
Four Port Serial Interface module to connect to the OMC

The channelized E1 ports are used to connect the GSM BSS equipment. Each E1 port can
receive and transmit data bi-directionally at 2.048 Mbps, and provide up to 31 virtual channels.
Each individual channel or time slot can be configured as a separate serial interface. Each E1
card contains two physical 120 Ohm E1 ports. To connect 75 Ohm Network Elements, a 75-120
Ohm Adapter Cable is used. These ports are identified in the Cisco configuration file by <slot
number / port number>. For consistency, the first E1 card is inserted in slot 3, the second
into slot 4, and so on (Reserve slots 1 and 2 for Four Port Serial Interface modules).
Refer to Table 9-1 for information on the recommended slots usage. The port numbers on
the E1 card are labeled as CTRLR 0 and CTRLR 1. Refer to Figure 9-3 for a pictorial view of
the channelized E1 module.
Figure 9-3
9-4
68P02901W47-S
Jul 2008
Table 9-1
Slot
Number
1 4
0/0
0/1
Router capacity
Recommended slot usage on the Cisco 3845

Port Type
Two Port
E1 Module
Four Port
Serial I/F
Four Port
Serial I/F
Port
Number
Connected
System
Cable Type
Electrical Spec /
Clock Source
GSM NE
RJ45 to BNC
E1
GSM NE
RJ45 to BNC
E1
OMC
EIA/TIA-449
Smart Serial
X.21 / DCE
OMC
EIA/TIA-449
Smart Serial
X.21 / DCE
OMC
EIA/TIA-449
Smart Serial
X.21 / DCE
Interconnect
RS-530/X21
Smart Serial
X.21 / DCE
OMC
EIA/TIA-449
Smart Serial
X.21 / DCE
OMC
EIA/TIA-449
Smart Serial
X.21 / DCE
OMC
EIA/TIA-449
Smart Serial
X.21 / DCE
Interconnect
RS-530/X21
Smart Serial
X.21 / DCE
Router capacity
The four slots 1 to 4 in the 3845 router can host Two Port E1 modules for connection to the BSS.
Refer to Figure 9-1 for the recommended slot usage.
The slots 0/0 and 0/1 can host Four Port High Speed Serial modules (HWICs) for OMC and
interconnect connectivity. The Cisco to Cisco interconnection is now done through the
secondary Ethernet port.
Cables used
DB-[Number] is an indication of the connector type. The number refers to the number of pins in
the connector.
68P02901W47-S
9-5
Jul 2008
Cables previously used
Six different cable types are used on the 3845:
High-Density Smart Serial to DB-37-Female (EIA/TIA 449 DCE)

Cable connection from the Serial ports in slot 0 to the OMC HSI

High-Density Smart Serial to DB-25-Male (RS-530-SS- DTE)

Used to interconnect 3845 router with another 3662 or 3845 router

Cables previously used

During early deployment, the following cables were used:
DB-60 to DB-37-Female (EIA/TIA 449 DCE)

Cable connection from the Serial ports in slot 0 to the OMC HS

DB-60 to DB-25-Male (RS-530-DTE)
DB-60 to DB-15 (CAB-X21)

Used to inter-connect 3845 router with another 3662 or 3845 router


9-6
68P02901W47-S
Jul 2008
Introduction
Prerequisites
Connecting and configuring the LAN connections
Prerequisites
A PC or laptop computer running Windows NT, 2000 or XP is required. The Console rollover
cable and RJ45 to DB-9 adapter is used in this section.

To establish the console connection, proceed as follows:
Procedure 9-1
Plug one end of the Cisco Console cable into the port labeled Console on Slot
0 at the rear of the router.
Plug the other end of the cable into the RJ45 port of the DB-9 adapter, and
plug the DB-9 connector into the COM serial port of the PC or laptop.
On the connected PC or laptop, start a Terminal Emulator. In

this example, the emulator is HyperTerminal, which comes as
standard with Microsoft Windows. To start HyperTerminal,
select the following after logging on to the PC or laptop:Start
Programs Accessories [Communications] HyperTerminal
The Communications menu is in brackets as it may not be present in all
Windows Operating Systems. The Connection Description dialog box is
displayed.
Enter a name and choose an icon from the Connection Description dialog
box. In this example, the name is Cisco 3845. Click OK to proceed.
Connect To dialog box is displayed (refer to Figure 9-4).
Continued
68P02901W47-S
9-7
Jul 2008
Procedure 9-1
5
In the Connect To dialog box (Figure 9-4) , expand the options available in
the Connect using field and select the appropriate COM port. Click OK
to proceed.
Figure 9-4
Connect To dialog box
The COM Properties dialog box is displayed.

Continued
9-8
68P02901W47-S
Jul 2008
Procedure 9-1
6
Set the COM Properties dialog box fields to the values shown in Figure 9-5
and click OK.
Figure 9-5
68P02901W47-S
COM Properties dialog box
HyperTerminal automatically connects to the configured port. The Connected

status and time can be seen at the bottom of the HyperTerminal screen. If the
status is Disconnected, the port can be reconnected by selecting the following
from the menu bar: Call Call. The prompt is not seen until the router is
turned on in the next step.
9-9
Jul 2008
Once the previous section is complete, perform the initial configuration by following this
procedure:
Procedure 9-2
Power on the 3845 router.
NOTE
The 3845 router must be physically close to the OMC and Local
Area Network to accommodate the length of the cables. If the
connection to the OMC is beyond 50 feet, twisted pair cabling
must be used to extend the connection.
When the Cisco router is first powered on, it goes through the Power
On Self Tests (POST). Several messages are displayed on the Console.
Once these are successfully completed, the router looks for an
Internetworking Operating System (IOS) to boot. The IOS to boot from
can be specified in the configuration file that is stored in the routers
non-volatile RAM. However, because this is the first time the router is
powered on, the configuration in NVRAM is empty. This causes the
router to search for a valid operating system in the flash memory.
The first valid IOS that is available in the flash memory is loaded.
Once the IOS has been identified and loaded, the router starts an interactive
session with the user to configure the router, and displays this prompt:
Would you like to enter the initial configuration dialog?
[yes/no]:
no
The interactive configuration session is not used when the router is installed.
Therefore, answer no at the above prompt.
NOTE
If you inadvertently choose yes at this point, return to the above
prompt by powering the router off and then on again.
The router displays this prompt:
Would you like to terminate auto install? [yes]:
Press Return to terminate auto install. The router proceeds to complete the
boot up. Several interface state change messages are displayed until the
router completes its boot up.
Continued
9-10
68P02901W47-S
Jul 2008
Procedure 9-2
4
Initial configuration (Continued)
Once boot up is complete, press the Return key.

The following prompt is displayed:
Router>
This is the basic user level prompt. At this user level, basic router commands
can be used to show interfaces that exist, the IOS version that is running,
memory status and other information. The router must be in privilege
execution mode to perform any configuration changes.
To enter privilege mode, enter the following command at the Router prompt:
Router> enable
The router prompt changes to the prompt below, signifying that it is now
at a level wherein the administrator has full privileges. This is known as
the privilege level. Privileged mode includes user mode functionality and
provides unrestricted access. It is used exclusively for router configuration,
debugging, setting Operating System (OS) parameters, and retrieving
detailed router status information.
Router#
The basic router configuration in the next section can be performed now.

The following configuration steps show the commands that need to be entered in bold text.
Prompts and messages are displayed for indication purposes only.
Text within the <> characters are user-specific.

From the privilege prompt that was established at the end of the last section, (Router#) perform
the following steps:
Procedure 9-3
Execute the following command to enter global configuration:

Router# configure terminal
Enter configuration commands, one per line. End with CTRL/Z.
Router(config)#
Enter the following command to set the hostname: Router(config)#

hostname <X25-3845>
X25-3845(config)#
Continued
68P02901W47-S
9-11
Jul 2008
Procedure 9-3
Setting the hostname (Continued)
NOTE
The hostname X25-3845 is used in examples throughout this
document. Change this to conform to the network operators
naming convention. The new hostname is displayed.

Passwords can be set at three different points of the Cisco configuration:
Console password: Users are prompted for this password when connected directly to the
Console port of the router.
Telnet line password: Users are prompted for this password after initiating a telnet
session to the router.
Enable password: This password is requested on entering privilege level to configure

the router.
NOTE
Console and telnet passwords give user level access to the router. At this level,
the operator can use the show commands to view the status of the router. The
enable password gives the operator full privileges on the router.
While remaining in global configuration mode from Setting the hostname, perform the
following procedure:
Procedure 9-4
Enter the following commands to set the console password:

X25-3845(config)# service password-encryption
X25-3845(config)# line console 0
NOTE
Notice how the router prompt changes to identify the current
configuration level. The exit command is used to exit the line
configuration mode and return to global configuration.
2
Enter the following commands to set the telnet passwords:

X25-3845(config)# line vty 0 4
Continued
9-12
68P02901W47-S
Jul 2008
Procedure 9-4
3
Setting the passwords (Continued)
Enter the following commands to set the enable password:

X25-3845(config)# enable password 0 <password>
CTRL-z ends the configuration session and exits the user to the privilege
router level. The following message is displayed:
Configured from console by console

At this point, the Ethernet connection to the Local Area Network (LAN) can be established.
Connect the port labeled Ethernet 0/0 at the back of the 3845 to a LAN Hub or switch to
which there is a workstation connected. The CAT 5 twisted pair cable is used to establish the
physical connection.
NOTE
It is also possible to configure the router through the existing console connection, in
which case this procedure can be skipped.

From the router privilege prompt, perform the following:
Procedure 9-5
Configure the FastEthernet connection by entering the following at the

prompt:
X25-3845(config)# interface fastEthernet 0/0
NOTE
The following message should be seen on the console indicating
that the link has come up:
Line protocol on Interface FastEthernet0/0, changed
state to up
Continued
68P02901W47-S
9-13
Jul 2008
Procedure 9-5
Configuring the LAN connection (Continued)
Use the following command to set a default route. This allows the router
to communicate with other Local Area Networks. Refer to the network
administrator for these parameters, if necessary:
X25-3845(config)# ip route 0.0.0.0 0.0.0.0 <Gateway Address>
X25-3845#
Verify that the LAN connection is up by entering the following command:

X25-3845# show interface fastEthernet 0/0
The first line identifies if the FastEthernet link is up by displaying the following:
FastEthernet0/0 is up, line protocol is up
A telnet session can now be established to the Cisco 3845 router from a
workstation on the same LAN.
NOTE
Remain connected on the console while testing telnet connectivity
from another workstation. This is a safe way to verify that all
passwords are set correctly.
To establish a telnet session, perform the following from a workstation:
telnet <IP Address set in step 1 above>
User Access Verification
Password: <Password set for line vty 0 to 4>
X25-3845> enable
Password: <enable password>
X25-3845#
9-14
After completing the previous step, all configurations to this point have been
verified. The configuration changes made in all the previous steps can now be
saved to Non- Volatile RAM on the router to make them permanent. Without
doing this, a router reboot loses all configuration set in previous steps. To
save these changes, do the following:
The console connection that was established to do the basic router

configuration can now be disconnected after exiting.
68P02901W47-S
Jul 2008
Introduction

Profiles are used to configure X.25 parameters that are common to several interfaces. Two
profiles are created in this sub-section, one for the OMC and one for the GSM equipment.
Further, X.25 parameters must be changed once within the appropriate profile. These changes
then take effect in all interfaces using this profile.
Perform the following from privilege level to configure the X.25 profiles:
Procedure 9-6
Configuring the X.25 profiles
To configure the OMC X.25 profile, perform the following:

X25-3845(config)# x25 profile OMC dce
X25-3845(config-x25)# no x25 security crcdn
X25-3845(config-x25)# x25 htc 376
X25-3845(config)#
Continued
68P02901W47-S
9-15
Jul 2008
Procedure 9-6
2
Configuring the X.25 profiles (Continued)
To configure the GSM X.25 profile, perform the following:

X25-3845(config)# x25 profile GSM dce
X25-3845(config-x25)# x25 ltc 1024
X25-3845(config-x25)# x25 htc 1055

The X25_config file
The X.25 configuration file, configured during the OMC-R installation, defines which
HSI (High Speed serial Interface) lines are used. The x25_config file is located in the
/usr/omc/config/global directory of the OMC-R. Each line in this file contains eleven fields.
These fields are defined in Table 9-2. A sample configuration file is shown in Table 9-3.
Table 9-2

Field
Comments
Record Number
X.25 Channel Number
The format is x25_chan<nn>, where nn is

the record number.

numbers in the x25_config file must
numbers.
The recommended X.121
address format is as follows:
Digits 6 to 10 are
equipment specific indicators.
Interface Type
A value of H relates to SunLink HSI/S.

Continued
9-16
68P02901W47-S
Jul 2008
Table 9-2

Field
Comments
A value of - relates to a calling process.

Any other value in this field relates to a
listening process.
OMC-R Process

Protocol .
Set to X.25.
Packet Size
For example, 128.
Window Size
For example, 2.
Time Out Parameter
For example, 50 or 500
Table 9-3
Sample X25_config file for an OMC
Record
Number
X.25
Channel
Number
Sunlink
X.25 link
number
x25_chan1
X.121
Address
Process Call
Characteristic
OMC-R
Process
Time Out
Parameter
20201030
000061
g_bootload
OMC_BL
50
x25_chan2
20201030
001062
g_bootload
OMC_BL
50
x25_chan3
20201030
000241
g_ei
OMC_EI
500
x25_chan4
20201030
001142
g_ei
OMC_EI
500
x25_chan5
20201030
000200
OMC_RL
500
x25_chan6
20201030
001299
OMC_PU
50
x25_chan7
20201030
001299
OMC_PU
50
x25_chan8
20201030
001299
OMC_PU
50
x25_chan9
20201030
001299
OMC_PU
50
Interface Type = H
Protocol = X25
68P02901W47-S
9-17
Jul 2008
Packet size = 128
Window size = 2
NOTE
Refer to the x25_config that is customized to your network.
OMC platforms have two HSI cards. Each HSI card has four serial ports. With two HSI cards,
redundancy is built into the X.25 network. Table 9-4 shows which ports (column 3) are defined
for each process (column 7). The Upload processes are initiated from the OMC and use links 0,
2, 4 and 6. The Rlogin Process uses link 1. Later in this section, there is a procedure for using
the Upload and Rlogin HSI ports for Bootload and Event Interface traffic, increasing the overall
performance and capacity of the X.25 network.

High Density Smart Serial to DB-37 (EIA/TIA - 449 DCE) cables are used to make the connection
between the router and the OMC. The female ends of the 449 DCE cables are connected to the
female HSI connectors using 37-way to 37-way gender changers.
Before making the physical connections between the OMC and the router, refer to Table 9-4 to
determine the physical port connections at either end.
To complete the physical connections, repeat this procedure for each HSI port used in the
x25_config file:
Procedure 9-7
Determine the first physical port to be used on the OMC HSI (refer to the third
column on the first line of the x25_config file). In this case (from Table 9-4),
port 0 is the first port to be used. Connect the DB-37 male gender changer to
this port, connect the DB-37 female end of the 449 DCE cable to the other
side of the gender changer.
Refer to Table 9-4 to identify the corresponding router port. In this case, port
0 on the OMC side connects to 0/0/0 on the router.
Connect the Smart Serial end of the 449 DCE cable to the appropriate port on
the Cisco 3845.
Table 9-4
Physical Port connections at the OMC and Cisco 3845
Cisco 3845
Port 0
Connects to 0/0/0
Port 1
Connects to 0/0/1
Port 2
Connects to 0/0/2
Port 3 (Not Used)
Connects to 0/0/3
Port 4
Connects to 0/1/0
Continued
9-18
68P02901W47-S
Jul 2008
Table 9-4
Physical Port connections at the OMC and Cisco 3845 (Continued)
Cisco 3845
Port 5
Connects to 0/1/1
Port 6
Connects to 0/1/2
Port 7 (Not Used)
Connects to 0/1/3
In Table 9-4, the OMC-R HSI Port Number is defined in column 3 of the x25_config file. Cisco
3845 refers to the slot, HWIC card, and HWIC port.

Each of the serial interfaces that connect to the OMC has the same configuration. Perform the
following from the privilege level for each of the interfaces that connect to the OMC:
If a telnet session is used to configure the router, enter the following from the privilege
level:
X25-3845# terminal monitor
This command is used to monitor messages that are displayed on the Console port. Once
this command is entered, all Console messages for the period of this telnet session are
seen. This is useful to see the interface states changing as they are configured.

68P02901W47-S
Execute these commands for each serial interface that is connected to the OMC. The only
parameter change necessary is the physical interface number (for example, 0/0/0, 0/0/1):
9-19
Jul 2008
NOTE
The physical interface number is the same format as shown in Table 9-4.
The first interface to be configured is interface 1/0.
X25-3845(config-if)# encapsulation x25 profile OMC
X25-3845(config-if)# clockrate <clock rate>
The recommended clock rate for an E3x00 OMC is 252000.

The recommended clock rate for a Netra OMC is 252000.
The recommended clock rate for a SunFire OMC is 2016000.
If the clock rate value is not configured on the serial interface ,then the
clock rate is automatically set to it's default value of 2016000. Therefore, it
is not necessary to set the clock rate value when connecting to a SunFire
If required, previous clock rate values can be removed by using the " no
clock rate "command:
X25-3845(config-if)# no clock rate
X25-3845(config)#
The following lines should be displayed indicating that the serial line is up:
Interface Serial{Slot # / HWIC number # / Port #}, changed state to up.
Line protocol on Interface Serial{Slot # / HWIC # / Port #}, changed
state to up.
Repeat step 3 for all OMC connected interfaces. Using the x25_config file
inTable 9-3 as an example, the following interfaces on the router must be
configured as described in the above steps:
interface
interface
interface
interface
interface
interface
serial
serial
serial
serial
serial
serial
0/0/0
0/0/1
0/0/2
0/1/0
0/1/1
0/1/2
Once all the interfaces are configured, save the configuration and verify that the interfaces
are up by doing the following:
X25-3845(config)#
X25-3845# show interface serial <slot number/port number>
The first line of the output indicates that the serial interface link is up by displaying this message:
Serial0/0/0 is up, line protocol is up.
9-20
68P02901W47-S
Jul 2008

Each line output contains information about one interface. All interfaces that are up have
an asterisk (*) displayed to the left of the line. The following example of the output shows
the interface states:
Interface
IHQ
IQD
OHQ
OQD
RXBS
RXPS
TXBS
TXPS
TRTL
*GigabitEthernet 0/0 0
663
* Serial 0/0/0
* Serial 0/0/1
GigabitEthernet 0/1
4000
10
3000
31000
44
2000
97
...
...
Serial 0/1/3

Prerequisites
The number of physical E1 connections required depends on the topology of the GSM network.
In this section, it is necessary to know the following:
Which GSM network elements need to be connected to the router? The total number of network
elements that can be connected to the router depends on the number of channelized E1 cards in
the router. Each channelized E1 card has two E1 interfaces and each E1 interface supports 31
DS0 (64K) timeslots.
The type of physical cables to use depends on the GSM Network Elements. These are
either 120 Ohm or 75 Ohm. For 75 Ohm Network Elements, the 120 - 75 Ohm Adapter
Cable is required.
The timeslots to which the NEs are mapped on each E1 connection.
68P02901W47-S
9-21
Jul 2008
Establishing the connection

The 120 - 75 Ohm Adapter Cables are used to connect 75 Ohm GSM Network Elements to the
router. Make all the necessary connections, taking note of which GSM Network Element is
connected to which physical E1 port. Once a proper connection has been established, the Local
Alarm light on the physical E1 interface should disappear and the Carrier Detect light should go
green. The E1 port numbers follow the same numbering scheme as the serial ports that connect
to the OMC with the exception that there are only two ports. Once all the physical connections
have been established, the interfaces to the Network Elements can be created.

Each physical E1 interface is logically created on the Cisco 3845 as a controller. Each controller
has 31 64K timeslots available to it. In this section, multiple channel groups are created within
each controller (one channel group per NE). The purpose of the channel group is to define the
associated timeslot(s). Table 9-5 summarizes the steps taken to create connections to the NE.
NOTE
Use Table 9-5 for reference purposes only.
To view the controllers that exist on the Cisco 3845, execute the following command from
privilege level:
The following is an example of what can be seen in the configuration file.
!card type command needed for slot 1
!card type command needed for slot 2
To identify the cards as E1 cards, enter this into the configuration file using the following
commands:
X25-3845(config)# card type e1 1
X25-3845(config)# card type e1 2
X25-3845(config)# card type e1 3 (If E1 expansion using slot 3 is used)
X25-3845(config)# card type e1 4 (If E1 expansion using slot 4 is used)
X25-3845(config)# exit
To view the controllers now identified in the configuration as E1 controllers on the Cisco 3845,
execute the following command from privilege level:
Following is an excerpt from a sample configuration file showing two controllers, the first
controller is port 0 in slot 3 of the router, and the second is port one in slot 3:
controller E1 3/0
!
controller E1 3/1
Press the space bar to page through the rest of the running configuration file.
9-22
68P02901W47-S
Jul 2008
Table 9-5
Sequence of steps to create serial interfaces

Command reference
(do not execute)
Step
Purpose
controller E1 <slot
number/port number>
To enter the controller to be configured. The prompt

changes to reflect the new configuration level.
channel group <channel

#> timeslots <timeslot
number(s)>
A separate channel group is required for

every NE that is connected to this controller.
It is possible to allocate several timeslots
to one channel group. However, only
one 64K timeslot is allocated to each NE.
<channel #> starts at 0 and continues to 30.
<timeslot number(s)> starts at 1 and continues to 31.
The fist channel group that we create uses channel
# 0 and timeslots 1, the second uses channel
# 1 and timeslots 2 and so on (timeslots
2 refers to timeslot 2, not 2 timeslots).
Each channel group created automatically creates
a serial interface. This interface is configured in a
later step for the X.25 profile created for GSM.
Exit
This step exits controller configuration level and

returns to global configuration mode. At this point,
step 1 and 2 can be repeated to create channel
groups in other controllers.
interface serial <port

number / slot number:
channel #>
To enter the serial interface created

from the associated channel group.
<port number / slot number> indicates
the controller (physical E1 port)
<:channel #> indicates the channel group.
encapsulation x25 profile

GSM
This step configures the serial interface to use the

GSM profile created at the start of this section.
Exit
This step exits serial configuration level and returns

to global configuration mode. At this point, step 4
can be repeated to configure other serial interfaces.

Use the following steps to create the channel groups in the controllers. These in turn
automatically create the serial interfaces, which tie into the appropriate timeslot.
68P02901W47-S
9-23
Jul 2008
Procedure 9-8

Enter the appropriate controller:

NOTE

controller E1 3/0
By default CRC4 framing is turned on. To turn CRC4

framing off, use the following command inside the controller:
framing no-crc4
Create the channel group:

X25-3845(config-controller)#channel group <channel #>
NOTE
Timeslot numbering starts at 1 for timeslot 1 and work up

to 31 for timeslot 31. Channel # is always one less than
the timeslot number. For example, to configure the first
three timeslots, the following needs to be entered in step 3:
To configure all timeslots in the controller, continue to:

Motorola recommends creating channel groups only for the

timeslots being used, that is, for connected NEs.
For further information on this command, refer to Table 9-5.
As the interfaces are created, the following message is

displayed for each Serial Interface created:
Line protocol on Interface Serial{port number/slot number:

channel #}, changed state to down
Repeat Step 3 for all timeslots in this controller.

4
Exit Controller:
X25-3845(config-controller)# exit
Continued
9-24
68P02901W47-S
Jul 2008
Procedure 9-8
Creating channel groups (Continued)
To create further channel groups (serial interfaces) on other controllers,

repeat steps 2 through 4. Once all of the necessary channel groups have
been created, do the following:
To verify that the channel groups are established within the controller and
that the serial interfaces are created in the configuration file, do the following:
NOTE
The channel groups configured in the previous note have the
following serial interfaces created in the configuration file
(assuming that controller 3/0 was used):
NOTE
The Channel number is the timeslot number minus 1.
no ip address
!
no ip address
!
no ip address and so on.
68P02901W47-S
9-25
Jul 2008
Configuring the serial interfaces (to the GSM Network

Elements)
Each serial interface created needs to be configured to use the GSM X.25 profile created at the
start of this section. Perform the following from privilege level.
Procedure 9-9

Use the following commands to configure the encapsulation on the serial

interface:
X25-3845(config)# interface serial <port number / slot
number:channel #>
NOTE
The channel number is the timeslot number minus 1.
X25-3845(config-if)# encapsulation x25 profile GSM
Repeat step 2 for all serial interfaces created. Once all interfaces are
configured, save the configuration and verify that the interfaces are up by using
the following commands:
X25-3845(config)#
X25-3845# show interface serial <slot number/port
number:channel #>
X25-3845#show interfaces serial 3/0:0
Hardware is DSX1
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation X25, loopback not set
X.25 DCE, address <none>, state R1, modulo 8, timer 0
Defaults: idle VC timeout 0
cisco encapsulation
input/output window sizes 2/2, packet sizes 128/128
Timers: T10 60, T11 180, T12 60, T13 60
Channels: Incoming-only none, Two-way 1024-1055,Outgoing only none
Continued
9-26
68P02901W47-S
Jul 2008
Procedure 9-9
Configuring the serial interfaces (Continued)
RESTARTs 0/0 CALLs 0+0/0+0/0+0 DIAGs 0/0

LAPB DCE, state CONNECT, modulo 8, k 7, N1 12056, N2 10
T1 3000, T2 0, interface outage (partial T3) 0, T4 4
VS 3, VR 4, tx NR 4, Remote VR 3, Retransmissions 0
Queues: U/S frames 0, I frames 0, unack. 0, reTx 0
IFRAMEs 0/0 RNRs 0/0 REJs 0/0 SABM/Es 0/0 FRMRs 0/0 DISCs 0/0
Last input never, output 00:00:02, output hang never
Last clearing of show interface counters 00:00:08
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
2 packets input, 4 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored,0 abort
2 packets output, 4 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
0 carrier transitions
Timeslot(s) Used:1, Transmitter delay is 0 flags X25-3845#
The first line of the output indicates that the serial interface is up with this
message:
The last line identifies the timeslot being used.

Each output line contains information about an interface. All the interfaces that are up have an
asterisk (*) displayed at the beginning of the line. Use the space bar to page through the output.
68P02901W47-S
9-27
Jul 2008
Introduction
X.25 routing is enabled on the 3845 router to allow Virtual Circuits to be routed from one
serial interface to another.
Once X.25 routing has been enabled, the X.25 routes can be created. X.25 routes are created
in the next section.
Hunt Groups are used as a method of load balancing across several serial links. In this section,
Hunt Groups are created to load balance the NE Virtual Circuits across the serial interfaces
that connect the OMC.

To enable X.25 routing, do the following from privilege level on the 3845 router:
Procedure 9-10



Creating X.25 Hunt Groups

Two Hunt Groups are created for load sharing the serial connections to the OMC.
BOOTLOAD: This Hunt Group shares the serial connections that are used for bootload. For
example, if six NEs are bootloading at the same time, they are evenly distributed across all
interfaces that are defined in this Hunt Group.
EVENTS: This Hunt Group shares the serial connections that are defined for event
interface.
There are two types of Hunt Groups available, vc-count and rotary. Motorola recommends
the use of vc-count, as this method sends calls to the interface that has the largest number of
available logical channels. This method ensures a good load balance when lines are of equal
speed.
9-28
68P02901W47-S
Jul 2008
At least two serial interfaces participate in each of these Hunt Groups. This is because two lines
in the x25_config file are defined for Bootload (lines 1 and 2) and two lines are defined for Event
Interface (3 and 4). However, because the OMC can route Bootload and Event data to the
correct process from any of the HSI ports, all of the connected serial lines (that connect to the
OMC) can participate in each Hunt Group.
NOTE
If any of the serial interfaces participating in the Hunt Group are down or not
connected, the interface shows them as being unavailable in the Hunt Group upon
entering the command
show x25hunt-group

Serial 1/0 and Serial 2/0 are the two bootload channels defined in the x25_config example in
Table 9-1 (column 6 in the x25_config file defined the process, g_bootload for BOOTLOAD
and g_ei for EVENTS). Refer to the x25_config file on the live OMC to determine these ports.
Minimally, the two ports defined for g_bootload participate in the BOOTLOAD Hunt Group.
However, Motorola recommends that all serial connections to the OMC are included in the Hunt
Group, making better use of the serial interfaces, increasing redundancy and capacity.
For example, if the two g_bootload serial lines are disconnected, the Network Element can still
bootload from one of the other available lines participating in the Hunt Group.
Perform the following steps from privilege level to create the BOOTLOAD Hunt Group:
Procedure 9-11

Create the Hunt Group:

X25-3845(config)# x25 hunt-group BOOTLOAD vc-count
X25-3845(config-x25-huntgroup)# interface serial <slot
number / port number>
NOTE
the Hunt Group.
OMC-R: 0/0/0, 0/0/1, 0/0/2, 0/1/0, 0/1/1, 0/1/2
3
68P02901W47-S
Exit the global configuration mode:

9-29
Jul 2008

Refer to x25_config file on the live OMC to determine these ports. Minimally, these two ports
participate in the EVENT Hunt Group. Motorola recommends that all serial connections to the
OMC are included in the Hunt Group, making better use of the serial interfaces, increasing
redundancy and capacity.
Perform the following steps from privilege level to create the EVENTS Hunt Group:
Procedure 9-12

X25-3845(config)# x25 hunt-group EVENTS vc-count
X25-3845(config-x25-huntgroup)# interface serial <slot number /
port number
NOTE
the Hunt Group.
OMC-R: 0/0/0, 0/0/1, 0/0/2, 0/1/0, 0/1/1, 0/1/2
2


Make sure that the Hunt Groups have been created properly by executing the following
command:
X25-3845# show x25 hunt-group
The output displays information about each Hunt Group as follows:
9-30
68P02901W47-S
Jul 2008
X25-3845#sh x25 hunt

ID
Type
Target
uses
status
traffic (out/in)
===========
========
==========
=========
=============
==============
BOOTLOAD
vc-count
Serial 0/0/0 0
1 VC
280555/370
Serial 0/0/1 0
1 VC
2657/132
Serial 0/0/2 0
1 VC
7862/197
Serial 0/1/0 0
1 VC
2651/132
Serial 0/1/1 0
0 VC
0/0
Serial 0/1/2 0
0 VC
0/0
Serial 0/0/0 1
1 VC
7862/197
Serial 0/0/1 1
1 VC
2651/132
Serial 0/0/2 1
1 VC
280555/370
Serial0/1/0 1
1 VC
2657/132
Serial 0/1/1 0
0 VC
0/0
Serial 0/1/2 0
0 VC
0/0
EVENTS
vc-count
X25-3845#
We can see that four NEs have EVENT connections, each using a different serial connection
back to the OMC platform, and no BSSs are BOOTLOADING (notice the 0 uses).
68P02901W47-S
9-31
Jul 2008
Introduction
In this section, the X.25 routing table is created. When the 3845 router receives an X.25 call
that must be forwarded, the X.25 routing table determines which destination to use. The routing
table is scanned sequentially from top to bottom and the first route that matches the address
criteria is used for the X.25 call. The user determines the order of the routing table when
entering new routes. This way, the user can control which routes should take precedence when
creating secondary or redundant links (that is, dual OMLs to the BSS).
X.121 addresses
In this section, it is important to know the addresses being used and the port-timeslot that they
are associated with. These addresses are referred to as X.121 addresses. An X.121 address is
assigned to each Network Element and each channel on the OMC. The X.121 address for the
OMC is defined in the x25_config file (column 4) and can be identified on the GSM NEs by
using the disp_dte command at the NE MMI prompt. The address is displayed in the NE DTE
addresses section. X.121 addresses are typically 14 digits in length.
An example of an addressing scheme is:
aaannddceehhxx
Where:
Is:
aaa
the country code
nn
the network code
dd
the location code
the type code:

1 BSS (EEHH = BSS Number), (XX should
be 00)
2 RXCDR
3 OMC
ee
the number of the OMC-R
hh
the HSI card and port number
xx
the function sub-address:

41 and 42 Event Interface
61 and 62 Boot Loader
00 Rlogin
99 Uploader
9-32
68P02901W47-S
Jul 2008

Follow these steps to create the routing table on the router:
The routes that use the Hunt Groups are established.
The routes to the GSM equipment are established.
The optional position parameter allows the user to define the position of a route in the routing
tables.
The routing table is scanned from top to bottom; hence the first matching address is used to
establish virtual connections. If this connection fails, the next route that matches the address
criteria is used. If the position option is not used, then by default the first route added would be
in position 1, the next route would take position 2, and so forth.
NOTE
Optional parameters are in brackets [ ].

The following commands set the routes to the OMC using the BOOTLOAD and EVENTS Hunt
Groups created in the last section. Refer to the x25_conf file for the x.121 addresses.
Procedure 9-13

Add the route:

hunt-group <Hunt Group Name>
NOTE
The following is an example of the routes that would be necessary if
using the x25_config file in Table 9-4 and the Hunt Groups created
in the last section:
3
68P02901W47-S
Repeat step two for all Hunt Group routes. To return to privilege level, type
the following:
X25-3845(config)#exit
9-33
Jul 2008

To create routes to the GSM equipment, perform the following:
Procedure 9-14

Repeat this command for all routes to the NE equipment, including secondary
OMLs:
X25-3845(config)# x25 route [# position] <X.121 address> interface
serial <slot number/port number:channel #>
NOTE
The channel # is only necessary when connecting to GSM network
elements on the E1 lines. In the following example, the primary
OML is routed out of timeslot 6 (channel 5) on controller 3/1. The
secondary OML is routed out of timeslot 6 on controller 4/1.
Remaining routes to be created

Procedure 9-15
Creating routes for Cisco-Cisco interconnect

Repeat this command for all routes between the equipment:

xot <destination ip address> xot-keepalive-period 10
xot-keepalive-retries 3
Saving the Configuration

Once all the routes have been created, exit and save the configuration by doing the following:
9-34
68P02901W47-S
Jul 2008

To verify that the routes have been established, use the following command from privilege level:
X25-3845# show x25 route
Refer to the commands in the section Useful Cisco commands on page 8-35Useful Cisco
commands to verify that the X.25 network is up.
68P02901W47-S
9-35
Jul 2008
Integration with the existing Cisco 3662/3845 router
Integration with the existing Cisco 3662/3845 router
Creating an X.25 profile for the serial interfaces that connect to

the CISCO 3662/3845
NOTE
The serial interconnect outlined here was used before the introduction of the HWIC
card and the XOT interface defined further on.
Procedure 9-16
Creating X.25 profiles for Cisco-Cisco interconnect
Enter the global configuration mode from the privilege level:

Create the X.25 profile:

X25-3845(config)# x25 profile CISCO_DCE dce
X25-3845(config-x25)# x25 htc 256

Refer to the section Establishing OMC and GSM connections for further
information on X.25 profiles.
Configuring the necessary serial interfaces to use these CISCO

profiles
NOTE
The serial interconnect outlined here was used before the introduction of the HWIC
card and the XOT interface defined further on.
Determine the number of serial connections being made between the Cisco routers. Two serial
interfaces can be used for redundancy. This number of serial connections must be available on
the Cisco serial interfaces. Figure 9-6 gives an example of the possible connections between the
Cisco 3845 and existing Cisco 3845.
9-36
68P02901W47-S
Jul 2008
Installation and Configuration: OMC-R Clean Install Configuring the necessary serial interfaces to use these CISCO profiles
Figure 9-6
Cisco 3845 connected to an existing Cisco 3845
NOTE
Slot/port numbers shown are for the previous hardware revision for which a serial
interconnect was used.
Configuration procedure
Complete the following steps to configure the interfaces on the Cisco 3845 that connect to the
existing Cisco 3662/3845:
Procedure 9-17
Configuring interfaces on the Cisco 3845
From the privilege level, enter global configuration mode:

NOTE
The physical interface number is the same format as shown in
Table 9-4
For the profile below, we have used <slot/port> 3/3
Continued
68P02901W47-S
9-37
Jul 2008
Procedure 9-17
Configuring interfaces on the Cisco 3845 (Continued)
X25-3845(config-if)# encapsulation x25 profile CISCO_DCE

X25-3845(config)#
NOTE
The physical interface number is the same format as shown in
Table 9-4.
For the profile below, we have used <slot/port> 4/3
X25-3845(config-if)# encapsulation x25 profile CISCO_DTE
X25-3845(config)#
2
Once all interfaces are configured, save the configuration by doing the
following:
X25-3845(config)#

For further information on X.25 routing, refer to the section Enabling X.25 routing and creating
Hunt Groups on page 8-28 . If X.25 routing has not already been enabled, do the following from
privilege level on the 3845 router:
Procedure 9-18
9-38



68P02901W47-S
Jul 2008
Integration with a Cisco 3662/3845 router using X.25 over IP
Integration with a Cisco 3662/3845 router using X.25

over IP
Introduction
This section explains how to integrate the Cisco 3845 router with a new or existing Cisco
3662/3845 router. This may be for expansion or to provide redundancy.
Figure 9-7
68P02901W47-S
Router interconnect using X25 over IP (ethernet)
9-39
Jul 2008
Creating X.25 routes between the routers
Procedure 9-19
Configuring the Ethernet connection
Configure the Gigabit Ethernet connection

by entering the following at the prompt:
X25-3845(config)# interface GigabitEthernet 0/1
X25-3845(config-if)# media-type rj45
NOTE
This Ethernet connection is on a separate LAN to the other
connection 0/0 used for configuration.
Creating X.25 routes between the routers

Set up the OMC/BSS X.25 routes to use the interconnect between the two routers as described
in Creating X.25 routes on page 9-32 .
9-40
68P02901W47-S
Jul 2008
Introduction
Useful Cisco Commands:

Interface commands
X25 Commands to verify the X.25 network
Making changes to the Cisco configuration:

Deleting routes

The following commands can be entered from the privilege level to view the status of the 3845
router. To get a full list of commands available, use the ? key. For example, the command
show ? displays all show options available:
To display the current live configuration in running memory:

show running-config
To display the configuration in NVRAM (the command write config copies the running
config to startup config):
show startup-config
68P02901W47-S
9-41
Jul 2008
To display the operating system version that is running:

show version
The number of serial interfaces configured.
System up time.
Amount of NVRAM and Flash available.
To display the CPU utilization:

show processes
To set the date and time:

clock set <HH:MM:SS DD MONTH YYYY>
To show the date and time:

show clock
To clear all interface counters:

clear counter all
To show the contents of Flash:

show flash all
This command also shows the free space on Flash.
Interface commands
The following commands are useful to view the status of the 3845 interfaces.
To show the Interface status and characteristics:

show interface <slot number/port number<:channel number>>
X.25 characteristics.
Encapsulation type.
To show interface summary information, including status:

show interface summary
9-42
68P02901W47-S
Jul 2008
To show the controller information:

show controller
This command is useful for identifying the line framing and coding. It also displays:
Link speed
Physical connection type
Framing Error counts
X.25 commands
The following commands are useful to verify and monitor the X.25 network:
To show routing tables and usage:

show x25 route [| include <string>]
To show number of Virtual Circuits established:

show x25 services
To show Virtual Circuits that has been established: This command also shows window
size and packet size.
show x25 vc [| include <string>]
NOTE
The [include <string>] option can be used to search for text within the output.
This is useful as there are typically pages of output. For example, you could use
the following command to view all upload virtual circuits currently active:
show x25 vc | include 2020130000061

To back up the running configuration on the Cisco router to a tftp server, perform the following:
copy running-config tftp:
Enter the destination filename when prompted.
68P02901W47-S
9-43
Jul 2008
NOTE
Depending on the setup of the tftp server, you may need to:
Create this file (as a blank file) with appropriate permissions on the tftp server.
Enter the full path at the Cisco prompt (This depends on the root directory
set on the tftp server).
To restore the running configuration from a tftp server, execute the following:
copy tftp running-config:
Enter the full path and filename when prompted.

Deleting routes
Use the following command to delete a route from the running configuration:
X25-3845(config)# no x25 route [ # position ] <X.121 address> interface serial
<Slot Number / Port Number>
OR
X25-3845(config)# no x25 route [ # position ] <X.121 address> hunt-group <Hunt
Group Name>
NOTE
To delete a route that was previously added, put no before the command that was
previously used to add the route while in global configuration mode.

Use the following commands to delete a channel group:
X25-3845(config-controller)# no channel group <channel #>
Trouble-shooting
Use the following command to display version, configuration, and status information:
X25-3845# show tech
9-44
68P02901W47-S
Jul 2008
Chapter
10
SunFire 4800/4900 Troubleshooting
68P02901W47-S
Jul 2008
10-1
Resetting a Hung domain

Procedure 10-1
Resetting a Hung domain
Connect to the System Controller and select Domain A.
Send a break to the domain to get the Domain A Shell.
Execute break to get the OK> prompt.
At the OK> prompt type sync.
If this does not work, the domain has to be reset manually.

The reset command at the domain shell resets the domain. The operation is not allowed if the
virtual keyswitch is in the off, standby or secure position.
sc0-4800:A>
reset a
NOTE
The procedure takes a couple of minutes to complete.
Freeing the console connection

If the console connection is already in use, the following message is displayed:
Connection refused, console busy
There can be a number of platform shells active, but only one console connection. The root user
can only log into the OMC-R Server Platform through the console.
NOTE
Before executing this procedure, ensure that the console is not in use.
Follow the steps in Procedure 10-2 to free up the console.
10-2
68P02901W47-S
Jul 2008
Procedure 10-2
Rebooting the system controller
Freeing the console connection
Login to the main System Controller, and connect to the Platform Shell.
Execute:
connections
A list of all the current connections is displayed.
To disconnect, execute:
disconnect <ID>
Where <ID> is the associated ID of the connection to be disconnected.
To connect to the console, execute:

console a

The System Controller needs a reboot following any network parameter changes.
Procedure 10-3
At the System Controller, execute:

reboot
A prompt for confirmation similar to the following is displayed:

Are you sure you want to reboot the system controller now? [no]
Answer yes.
The System Controller then reboots.
Once the System Controller has rebooted, execute a showsc to ensure that
the OMCR Server Platform is in failover mode. If System Controller is not in
failover mode, refer to Change system into failover mode on page 10-4 .
Setting domain password

To set a password for a domain, execute the following:
Procedure 10-4
Setting the domain password
Log into the main System Controller, and connect to Domain A.
Execute:
password
Enter new password:
Enter new password again
68P02901W47-S
10-3
Jul 2008
Setting Platform Password
If the password is already set and the administrator has to change the password, execute the
following procedure:
Procedure 10-5
Changing the domain password
Log into the main System Controller, and connect to Domain A.
Execute:
password
Enter current password:
Enter new password:

To set a password for a System Controller, execute the following:
Procedure 10-6
Log into the Platform Shell.
Execute:
password
Enter new password:
Change system into failover mode

To change a system into failover mode, proceed as follows:
Procedure 10-7
Changing a system into failover mode
Log into the main System Controller, and connect to the Platform Shell.
Execute:
setfailover on
Resetting a Platform Password

If the platform administrators password is lost, contact SUN for support.
10-4
68P02901W47-S
Jul 2008
Resetting a domain password

Execute the following to remove the domain password in the event that it is lost or forgotten:
Procedure 10-8
Login to Domain A.
Execute a send break to give Domain A shell access.
Execute break to give OK> prompt access.
Take a copy of the output of the following commands to record the system
variables:
printenv
devalias
Login to the Platform Shell.
Execute:
Setdefaults
NOTE
All domain defaults are reset, not just the domain password.
Reset the system variables based on records taken in Step 4.
68P02901W47-S
Jul 2008
10-5
10-6
68P02901W47-S
Jul 2008
Index
Index
A
Adding a printer . . . . . . . . . . . . . .
Assigning printer name and address on the
network . . . . . . . . . . . . . . . . . .
Checking the printer status . . . . . . . .
Configuring a printer connected to a GUI
processor . . . . . . . . . . . . . . . . .
7-5
Adding a printer (contd.)

Overview . . . . . . . . . . . . . . . . .
Printer configuration file . . . . . . . . .
Printing a file . . . . . . . . . . . . . . .
7-5
7-6
7-5
7-6
7-6
7-5
C
Cisco 3662 router . . . . . . . . . . . . 8-2, 9-2
Background . . . . . . . . . . . . . . 8-2, 9-2
Cables used . . . . . . . . . . . . . . 8-5, 9-5
Four Port Serial Interface . . . . . . . 8-4, 9-3
Introduction. . . . . . . . . . . . . . 8-3, 9-3
Prerequisites . . . . . . . . . . . . . 8-2, 9-2
Router . . . . . . . . . . . . . . . . 8-3, 9-3
Router capacity . . . . . . . . . . . . 8-5, 9-5
Two port channelized E1 interface . . 8-4, 9-4
Configuration and installation of a remote
monitoring terminal . . . . . . . . . . . .
7-24
Introduction. . . . . . . . . . . . . . .
7-24
Naming conventions . . . . . . . . . .
7-27
Night concentration overview . . . . . .
7-27
OMC-R night concentration center
configuration . . . . . . . . . . . . . .
7-25
Prerequisites . . . . . . . . . . . . . .
7-27
Single OMC-R monitoring configuration . . . . . . . . . . . . . . . . . . .
7-24
Configuration checks . . . . . . . . . 2-45, 3-14
Additional configuration if a Web Access Server
is used . . . . . . . . . . . . . . . . .
3-14
Detecting the performance problem . .
2-47
Moving a machine with a forced link
speed . . . . . . . . . . . . . . . . . .
2-48
Configuration tasks after startup . . . . .
6-11
Create subscription lists . . . . . . . .
6-11
MIB configuration. . . . . . . . . . . .
6-11
NE node configuration . . . . . . . . .
6-11
Configuring auxiliary devices . . . . . . . . 7-2
Introduction. . . . . . . . . . . . . . . . 7-2
Configuring the GUI client . . . . . . . . . 4-9
Accessing the GUI server . . . . . . . .
4-10
68P02901W47-S
Jul 2008
Configuring the GUI client (contd.)

GUI client files to be modified. . . . . . . 4-9
Modifying the /etc/defaultrouter . . . .
4-10
Modifying the /etc/hosts file. . . . . . .
4-10
Setting root password. . . . . . . . . . . 4-9
Configuring the System Controller . . . . . 2-4
Netra 440 configuration . . . . . . . .
2-19
Procedure for the SunFire 4800/4900. . . 2-4
SunFire 4800/4900 configuration . . . .
2-14
Connectivity, configuration and LAN
connection . . . . . . . . . . . . . . . 8-7, 9-7
Configuring the hostname and passwords . . . . . . . . . . . . . . . . 8-11, 9-11
Connecting and configuring the LAN
connection . . . . . . . . . . . . . 8-13, 9-13
Establishing console connection . . . 8-7, 9-7
Initial configuration . . . . . . . . . 8-9, 9-10
Introduction. . . . . . . . . . . . . . 8-7, 9-7
Prerequisites . . . . . . . . . . . . . 8-7, 9-7
Creating X.25 routes . . . . . . . . . 8-32, 9-32
Adding routes into the routing table . . 8-33,
9-33
Creating routes to the GSM equipment . . . . . . . . . . . . . . . . 8-34, 9-34
Creating routes to the OMC. . . . . 8-33, 9-33
Introduction. . . . . . . . . . . . . 8-32, 9-32
Remaining routes to be created . . . . .
9-34
Saving the Configuration . . . . . . 8-34, 9-34
Verifying the routes . . . . . . . . . 8-34, 9-35
X.121 addresses. . . . . . . . . . . 8-32, 9-32
Customised Jumpstart procedures . . . . . 4-3
Running Jumpstart . . . . . . . . . . . . 4-3
IX-7
Index
D
DTE addressing at node elements.
Addressing requirements . . . .
Setting addresses . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-3
6-3
6-4
6-3
DTE addressing at node elements (contd.)

Setting OMC-R addresses (Single Platform
Processor) . . . . . . . . . . . . . . . . 6-5
Setting OML addresses . . . . . . . . . . 6-4
Slot: Port settings for OMLs . . . . . . . 6-3
E
Enabling X.25 routing and creating Hunt
Groups . . . . . . . . . . . . . . . . 8-28, 9-28
Creating the BOOTLOAD Hunt Group . . 8-29,
9-29
Creating the EVENTS Hunt Group . . . 8-30,
9-30
Creating X.25 Hunt Groups . . . . . 8-28, 9-28
Enabling X.25 routing. . . . . . . . 8-28, 9-28
Introduction. . . . . . . . . . . . . 8-28, 9-28
Verifying the X.25 Hunt Groups . . . 8-30, 9-30
Establishing OMC and GSM connections . . . . . . . . . . . . . . . . . 8-15, 9-15
Configuring the serial interfaces (to the GSM
Network Elements) . . . . . . . . . 8-26, 9-26
Establishing OMC and GSM connections (contd.)

Configuring the serial interfaces to the
OMC . . . . . . . . . . . . . . . . 8-19, 9-19
Configuring X.25 profiles . . . . . . 8-15, 9-15
Connecting the router to the OMC . . . 8-18,
9-18
Controllers and channel groups . . . 8-22, 9-22
Creating channel groups . . . . . . 8-24, 9-23
Establishing and configuring connections to the
GSM equipment. . . . . . . . . . . 8-21, 9-21
Establishing serial connections to the
OMC . . . . . . . . . . . . . . . . 8-16, 9-16
Introduction. . . . . . . . . . . . . 8-15, 9-15
F
Flexible GUI server configuration . . . . .
3-17
Configuring the flexible platform . . . .
3-17
Install the Third Party Packages on the GUI
server . . . . . . . . . . . . . . . . . .
3-22
Introduction. . . . . . . . . . . . . . .
3-17
Flexible GUI server configuration (contd.)

Prerequisites for installation . . . . . .
Verify the configuration of the Flexible
Platform. . . . . . . . . . . . . . . . .
3-17
3-21
G
GUI client installation . . . . . . . . . . .
Introduction. . . . . . . . . . . . . . .
GUI client requirements . . . . . . . . .
DVD Layout . . . . . . . . . . . . . . .
GUI client and server information
requirements . . . . . . . . . . . . . .
GUI client software requirements . . . .
Pre-installation requirements for a GUI
client . . . . . . . . . . . . . . . . . .
GUI server configuration . . . . . . . . .
Introduction. . . . . . . . . . . . . . .
Obtaining the boot prompt . . . . . . .
Running Jumpstart . . . . . . . . . . .
IX-8
.
.
.
4-2
4-2
1-9
1-10
.
.
1-9
1-9
.
.
.
.
.
1-9
3-2
3-2
3-2
3-2
GUI server processor requirements . . . .

GUI server processor information
requirements . . . . . . . . . . . . . .
GUI server processor software requirements . . . . . . . . . . . . . . . . . .
Pre-installation requirements for a GUI
server . . . . . . . . . . . . . . . . . .
GUI server/client verification . . . . . . .
Introduction. . . . . . . . . . . . . . .
Netra verification . . . . . . . . . . . .
Sunblade verification . . . . . . . . . .
1-7
1-7
1-7
1-7
5-23
5-23
5-24
5-23
68P02901W47-S
Jul 2008
Index
I
Installing a modem . . . . . . . . . . . . .
Background information . . . . . . . . .
Communicating with the modem . . . .
Configuring the MultiModem MT5634ZBA
Global . . . . . . . . . . . . . . . . . .
Configuring tip . . . . . . . . . . . . .
Controlling modem access . . . . . . .
Data links . . . . . . . . . . . . . . . . .
Enabling the login process . . . . . . .
Initial SPARCstation setup . . . . . . .
Introduction. . . . . . . . . . . . . . . .
Modem setup and Initialisation . . . . .
Physical connection . . . . . . . . . . .
Rates . . . . . . . . . . . . . . . . . . .
Remote connection and file transfers . .
7-8
7-8
7-12
Installing Solaris 8/9and OMC Software on

SunFire 4800/4900, Netra 440, and Netra
20 . . . . . . . . . . . . . . . . . . . . .
2-26
Installing the Solaris and OMC Software on
the SunFire 4800/4900, Netra 440, and Netra
20 . . . . . . . . . . . . . . . . . . . .
2-28
Introduction. . . . . . . . . . . . . . .
2-26
Prerequisites . . . . . . . . . . . . . .
2-26
Introduction. . . . . . . . . . . . . . . . . 2-2
Network configuration . . . . . . . . . . 2-3
Introduction to requirements and verification . . . . . . . . . . . . . . . . . . . . . 5-2
Manufacturer specific information . . . . 5-3
OMC-R equipment requirements . . . . . 5-2
On-site verification . . . . . . . . . . . . 5-2
7-16
7-12
7-13
7-9
7-17
7-10
7-8
7-13
7-10
7-9
7-18
M
Miscellaneous procedures and reference
information . . . . . . . . . . . . . . . .
Essential Jumpstart information. . . . .
Forwarding OMC-R mail to an exchange
server . . . . . . . . . . . . . . . . . .
Geographic regions and time zones . . .
Introduction. . . . . . . . . . . . . . .
Setting up Motorola Backdrop . . . . .
Show disks utility . . . . . . . . . . . .
6-17
6-20
Miscellaneous procedures and reference

information (contd.)
Troubleshooting reboot failure . . . . .
6-19
Monitoring an alternative OMC-R from a GUI
server . . . . . . . . . . . . . . . . . . .
7-31
Prerequisites for switching to alternative Single
Platform Processor . . . . . . . . . . .
7-31
Switching to an alternative Single Platform
Processor . . . . . . . . . . . . . . . .
7-32
6-21
6-17
6-17
6-22
6-19
N
Network verification . . . . . . . . . . .
Check users . . . . . . . . . . . . . . .
Introduction to network verification . .
5-25
5-26
5-25
Network verification (contd.)

Verify communication with devices on
LAN . . . . . . . . . . . . . . . . . . .
Verify remote login . . . . . . . . . . .
5-25
5-25
O
OMC-R verification . . . . . . . . . . . .
Check OMC-R applications . . . . . . .
Introduction. . . . . . . . . . . . . . .
6-12
6-15
6-12
OMC-R verification (contd.)

Verification of OMC-R startup and
shutdown . . . . . . . . . . . . . . . .
X.25 verification . . . . . . . . . . . .
6-12
6-13
P
Performance problem with GUI clients . . .
Detecting the performance problem . . .
Fixing the performance problem . . . . .
68P02901W47-S
Jul 2008
4-6
4-6
4-7
Performance problem with GUI clients (contd.)

Moving a machine with a modified /etc/system
file . . . . . . . . . . . . . . . . . . . . 4-8
IX-9
Index
Performance problem with GUI servers . .

3-13
Detecting the performance problem . .
3-13
Moving a machine with a forced link
speed . . . . . . . . . . . . . . . . . .
3-13
Power and environmental requirements . . 5-4
Altitude . . . . . . . . . . . . . . . . . . 5-5
Humidity . . . . . . . . . . . . . . . . . 5-5
Introduction to power and environmental
requirements . . . . . . . . . . . . . . . 5-4
Power requirements for specific OMC-R
equipment . . . . . . . . . . . . . . . . 5-4
Temperature . . . . . . . . . . . . . . . 5-5
Pre-installation requirements for the
OMC-R . . . . . . . . . . . . . . . . . . . 1-2

(contd.)
Global information requirements naming
service . . . . . . . . . . . . . . . . . . 1-3
Global information requirements OMC-R
database initialisation. . . . . . . . . . . 1-3
Global information requirements - group and
user accounts . . . . . . . . . . . . . . . 1-3
Global information requirements networking . . . . . . . . . . . . . . . . 1-2
Global information requirements - time
zones . . . . . . . . . . . . . . . . . . . 1-2
Introduction. . . . . . . . . . . . . . . . 1-2
Pre-installation requirements for all
processors . . . . . . . . . . . . . . . . 1-2
R
Remote Single Platform Processor setup. .
Creation of a new account . . . . . . .
Exporting file changes . . . . . . . . .
7-29
7-30
7-29
Remote Single Platform Processor setup (contd.)

Introduction. . . . . . . . . . . . . . .
Updating host file entries . . . . . . . .
7-29
7-29
S
Setting up the Wyse terminal . . . . . . . . 7-3
Introduction. . . . . . . . . . . . . . . . 7-3
Procedure for setting up the Wyse
terminal . . . . . . . . . . . . . . . . . . 7-3
Sign-off form . . . . . . . . . . . . . . .
1-11
Pre-installation requirements sign-off . .
1-11
Single Platform Processor requirements . . 1-4
Pre-installation requirements for a Single
Platform Processor . . . . . . . . . . . . 1-4
Single Platform Processor information
requirements . . . . . . . . . . . . . . . 1-4
Single Platform Processor software
requirements . . . . . . . . . . . . . . . 1-5
Single Platform Processor verification . .
5-18
Before power-up . . . . . . . . . . . .
5-18
Check equipment received . . . . . . .
5-18
Checking disk mirrors . . . . . . . . .
5-19
OMC-R software version verification . .
5-22
Operating system version verification. .
5-21
procedures . . . . . . . . . . . . . . .
5-18
Tape drive check procedure. . . . . . .
5-21
X.25 version verification . . . . . . . .
5-22
Space: weight and dimensional information . . . . . . . . . . . . . . . . . . . . . 5-6
Cisco 3662 Router . . . . . . . . . . .
5-16
Outline of space: weight and dimension
information . . . . . . . . . . . . . . . . 5-6
Single platform processor data Sun Netra
20 . . . . . . . . . . . . . . . . . . . . . 5-6
IX-10

(contd.)
Single platform processor data Sun Netra
440 . . . . . . . . . . . . . . . . . . . . 5-8
Single platform processor data Sun SunFire
4800/4900 . . . . . . . . . . . . . . .
5-11
Sun Netra 210 . . . . . . . . . . . . .
5-14
Sun Sunblade 150. . . . . . . . . . . .
5-13
Startup and shutdown. . . . . . . . . . . . 6-6
Introduction. . . . . . . . . . . . . . . . 6-6
Starting and stopping the GUI server . . . 6-9
Starting and stopping the OMC-R . . . . . 6-6
Starting and stopping the Single Platform
Processor . . . . . . . . . . . . . . . . . 6-7
Startup sequences . . . . . . . . . . . .
5-28
GUI Server startup sequence . . . . . .
5-31
Introduction. . . . . . . . . . . . . . .
5-28
Single Platform Processor startup
sequence . . . . . . . . . . . . . . . .
5-28
SUN Jumpstart procedures . . . . . . . . . 4-5
Procedure . . . . . . . . . . . . . . . . . 4-5
SunFire 4800/4900 Troubleshooting . . .
10-2
Change system into failover mode . . .
10-4
Freeing the console connection . . . . .
10-2
Rebooting the system controller . . . .
10-3
Resetting a domain password . . . . . .
10-5
Resetting a Hung domain . . . . . . . .
10-2
Resetting a Platform Password . . . . .
10-4
Setting domain password . . . . . . . .
10-3
Setting Platform Password . . . . . . .
10-4
68P02901W47-S
Jul 2008
Index

Configuring the SunRay Server . .
Overview of installation . . . . . .
Preparation procedure . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-26
3-28
3-28
3-26
3-27
SunRay Server Software Installation (contd.)

Preparing for Configuration of
Server. . . . . . . . . . . . .
System Startup and Shutdown .
Introduction. . . . . . . . . .
the
. .
. .
. .
SunRay
. . .
3-28
. . . . 6-2
. . . . 6-2
T
Troubleshooting the modem . . . . . . .
7-19
All ports busy . . . . . . . . . . . . . .
7-19
Cannot login: password fails . . . . . .
7-23
Corruption from SPARCstation with remote
system logging in . . . . . . . . . . . .
7-22
Login message is corrupt . . . . . . . .
7-23
Modem hangs up after answering a call and
negotiation . . . . . . . . . . . . . . .
7-22
Modems do not disconnect properly . .
7-22
Troubleshooting the modem (contd.)

No login prompt . . . . . . . . . . . .
Nothing happens when trying to tip the
modem . . . . . . . . . . . . . . . . .
Permission denied or link down . . . . .
Problem symptoms . . . . . . . . . . .
When dialling into the SPARC the modem
picks up the phone . . . . . . . . . . .
When to modify the EEPROM settings. .
7-21
7-23
7-22
7-19
never
7-23
7-22
U
Useful Cisco commands .
Introduction. . . . . .
Making changes to the
tion . . . . . . . . . .
. . . . . . . 8-35, 9-41
. . . . . . . 8-35, 9-41
Cisco configura. . . . . . . 8-38, 9-44
Useful Cisco commands (contd.)

Useful Cisco operating system commands. . . . . . . . . . . . . . . . 8-35, 9-41
X
X.25 Configuration - SunFire 4800/4900, Netra
440 and Netra 20 . . . . . . . . . . . . .
2-49
Additional configuration if a Web Access Server
is used . . . . . . . . . . . . . . . . .
2-55
Backup the Single Platform Processor. .
2-56
Creating x25_config file . . . . . . . . .
2-51
Format of the X25_config files. . . . . .
2-49
Licensing StorEdge Enterprise
Backup . . . . . . . . . . . . . . . . .
2-55
68P02901W47-S
Jul 2008
X.25 Configuration - SunFire 4800/4900, Netra

440 and Netra 20 (contd.)
Modify /etc/dfs/dfstab . . . . . . . . . .
2-54
Modifying the /etc/hosts file. . . . . . .
2-52
Partitioning information for each supported
platform. . . . . . . . . . . . . . . . .
2-57
Running the Configure_X25 script . . .
2-52
X.25 configuration procedures . . . . .
2-49
X25_config file entry order . . . . . . .
2-50
IX-11
Standard Printing Instructions

Part Number
68P02901W47-S
Manual Title
A4 Ring Bound - GSD (UK)

Binder
Printing
Finishing
4 D-ring binder - A4 size (210mm x 297mm) white PVC.
40mm or 65mm capacity depending on the size of the manual.
Clear pockets on front and spine.
Cover / spine text printed in colour.
Body- printed double sided onto white A4 (210mm x 297mm) 80g

4 hole paper.
A4 size (210mm x 297mm) clear PVC sheet front page for

protection.
Bag wrapped with clear polythene.
If this is to be used by manufacturing as an Inbox document, then refer to appropriate

Materials or Methods Specification.
OMC-R Clean Install
Installation & Configuration
OMC-R Clean Install
Installation & Configuration
GSR9
68P02901W47-S
GSR9
68P02901W47-S
Cutting
datum point
Spine
Front cover

Installation and Configuration OMC-R Clean Install

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installation and Configuration OMC-R Clean Install

Uploaded by

Copyright:

Available Formats

Installation and Configuration: OMC-R

Installation and Configuration: OMC-R Clean Install

Chapter 1: Pre-install Requirements

Single Platform Processor software requirements

Chapter 2: Operating System and OMC-R Software Installation

Chapter 3: GUI Server Configuration

Installation and Configuration: OMC-R Clean Install

Configuring secure services . . . . . . . . . . . . . .

Chapter 4: GUI Client Configuration

Chapter 5: On-site Requirements and Verification

Single Platform Processor verification procedures .

Chapter 6: System Startup and Shutdown

Installation and Configuration: OMC-R Clean Install

Chapter 7: Configuring Auxiliary Devices

Chapter 8: Cisco 3662 Installation

Chapter 9: Cisco 3845 Installation

Installation and Configuration: OMC-R Clean Install

Chapter 10: SunFire 4800/4900 Troubleshooting

Resetting a domain password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1: High level layout of the jumpstart DVD . . . . . . . . . . . . . . . . . .

Two port channelized E1 interface . . . . . . .

Recommended slot usage on the Cisco 3845 . .

Installation and Configuration: OMC-R Clean

What is covered in this manual?

A set of procedures for installing and commissioning an OMC-R at a customer site.

The following sections show the revision status of this document.

Issue Q - GSM Software Release 7 Half Rate

Issue R - GSM Software Release 8 (GMR-02)

Issue S - GSM Software Release 9

Resolution of Service Requests

Resolution of Service Requests

Special key sequences

Press the Ctrl and C keys at the same time.

Press the Ctrl, Shift, and C keys at the same time.

Press the Alt and F keys at the same time.

Press the pipe symbol key.

Press the Return or Enter key.

Motorola appreciates feedback from the users of our documents.

Questions and comments

The document type

The document title, part number, and revision character

The page number with the error

A detailed description of the error and if possible the proposed solution

Warnings, cautions, and notes

Warnings, cautions, and notes

Power down or unplug the equipment before servicing.

Portions of Motorola equipment may be damaged from exposure to electrostatic discharge.

Council recommendation of 12 July 1999 on the limitation of exposure of the general

Caring for the environment

Caring for the environment

Disposal of Motorola equipment

Disposal of surplus packaging

CMM labeling and disclosure table

CMM labeling and disclosure table

Motorola document set

Motorola document set

Ordering documents and CD-ROMs

Document banner definitions

Pre-installation requirements for the OMC-R

Chapter 1: Pre-install Requirements

Pre-installation requirements for the OMC-R

Pre-installation requirements for all processors

Global information requirements - networking

Global information requirements: networking