Escolar Documentos
Profissional Documentos
Cultura Documentos
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
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
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
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
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
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
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02901W47-S
Jul 2008
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
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
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
68P02901W47-S
Jul 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
iii
Contents
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
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
iv
68P02901W47-S
Jul 2008
Contents
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
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
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
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
68P02901W47-S
Jul 2008
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
vii
Contents
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
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:
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
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:
. . .
. . .
. . .
3845
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
9-5
9-16
9-17
9-18
9-23
68P02901W47-S
Jul 2008
About
This
Manual
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.
68P02901W47-S
Jul 2008
Revision history
Revision history
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
Nov 2006
Jul 2008
Table 2
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.
CTRL-c or CTRL+C
CTRL-SHIFT-c or
CTRL+SHIFT+C
ALT-f or ALT+F
ALT+SHIFT+F11
Press the Alt, Shift and F11 keys at the same time.
RETURN or ENTER
68P02901W47-S
Jul 2008
Contacting Motorola
Contacting Motorola
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.
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):
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
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.
Using non-Motorola parts for repair could damage the equipment or void warranty.
Contact Motorola Warranty and Repair for service and repair instructions.
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.
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
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.
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
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
The Motorola document sets provide the information to operate, install, and maintain the
Motorola equipment.
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
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.
Table 1-1
Network number
Netmask address
Broadcast address
Table 1-2
Geographic region
1-2
Time zone
68P02901W47-S
Jul 2008
Table 1-3
Group name
Table 1-4
User login
Group ID
root
omcadmin
User ID
User group
ID
User home
directory
/
/home/omcadmin
Shell type
Password
csh
informix
/usr/informix
csh
omcread
/home/omcread
csh
Table 1-5
Country code
68P02901W47-S
Network code
1-3
Jul 2008
Table 1-6
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
Host ID
In Table 1-8, enter the single platform processor information for software installation.
1-4
68P02901W47-S
Jul 2008
Table 1-8
OMC-R Software
DVD-ROM
Country Code
Network Code
System Printer
Hostname
IP Address
68P02901W47-S
1-5
Jul 2008
Table 1-9
Media
Number of
Volumes
1900.x
DVD
1900.x
DVD
Title
Sun Solaris
Solaris Logical Volume
Manager
Sun SunLink X25
License Number
10
11.9
9.2
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
Table 1-10
Host name
Internet address
In Table 1-11, enter the Host ID. The ID is required to license the solstice backup.
Table 1-11
Host id
Table 1-12
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
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
1-8
68P02901W47-S
Jul 2008
Table 1-13
Client hostname
Server name
Table 1-14
Title
Revision Version
Media
Number of
volumes
Sun Solaris
10
CD Pack
Sun Patches
Latest available
Table 1-15
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
/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
1-10
68P02901W47-S
Jul 2008
Sign-off form
Sign-off form
Table 1-16
Print name
68P02901W47-S
Jul 2008
Signature
Date
1-11
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.
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
P RINTER
GUI Serv er
GUI Serv er
SunFire 4800/4900
LOCAL AREA NETWORK (LAN)
GUI Serv er
KEY
REMOTE LAN
GUI Client
SO LARIS
CDROM + DAT
C DR OM
GUI
CDROM
GUI
SO LARIS
CDROM
GUI
GUI
SO LARIS
SO LARIS
CDROM
SO LARIS
CDROM
S OFTWARE P ROCES S
HARDWARE
ti-gsm_OMC-R_network_configuration-0001-ai-sw
68P02901W47-S
2-3
Jul 2008
Chapter 2:
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)
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:
Procedure 2-1 Configuring the system controller (without Ultra Sparc IV+
processors) (Continued)
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
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.
Network Configuration
--------------------Is the system controller on a network? []:yes
Use DHCP or static network settings? []:static
Hostname []:somc91_sc1
IP Address []:166.3.22.212
Netmask []:255.255.255.0
Gateway []:166.3.22.84
DNS Domain []:mydomain.com
Primary DNS Server []:166.3.50.200
Secondary DNS Server []:
SNTP
---SNTP server []:<timeserver IP>
Continued
2-6
68P02901W47-S
Jul 2008
Procedure 2-1 Configuring the system controller (without Ultra Sparc IV+
processors) (Continued)
SC
-SC POST diag Level []:min
Enable SC Failover? []:yes
Security Options
---------------Enable telnet servers? []:yes
Idle connection timeout (in minutes; 0 means no timeout) []:0
4
Follow the steps in Procedure 2-2 for configuring the system controller when using Ultra Sparc
IV+ processors.
Procedure 2-2
processors
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.
[]:false
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
Continued
68P02901W47-S
2-7
Jul 2008
Chapter 2:
Procedure 2-2 Configuring the system controller when using Ultra Sparc IV+
processors (Continued)
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]:
Loghosts
-------Loghost []:somc91
Log Facility []:local0
SNTP
---SNTP server []:<timeserver IP>
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 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]:
Continued
2-8
68P02901W47-S
Jul 2008
Procedure 2-2 Configuring the system controller when using Ultra Sparc IV+
processors (Continued)
SC
-SC POST diag Level []:min
Enable SC Failover? []:yes
Logical Hostname or IP Address []:166.3.22.214
Partition Mode
-------------Configure chassis for single or dual partition mode?
[]:single
[]:true
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.
Network Configuration
--------------------Is the system controller on a network? []:yes
Use DHCP or static network settings? []:static
Hostname []:somc91_sc1
IP Address []:166.3.22.212
Netmask []:255.255.255.0
Gateway []:166.3.22.84
DNS Domain []:mydomain.com
Primary DNS Server []:166.3.50.200
Secondary DNS Server []:
SNTP
---This setting is mirrored from the main SC (SC Failover is enabled)
Continued
68P02901W47-S
2-9
Jul 2008
Chapter 2:
Procedure 2-2 Configuring the system controller when using Ultra Sparc IV+
processors (Continued)
SC
-SC POST diag Level []:min
Enable SC Failover? []:yes
4
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
Procedure 2-2 Configuring the system controller when using Ultra Sparc IV+
processors (Continued)
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
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
COD
--PROC RTUs installed: 4
PROC Headroom Quantity (0 to disable, 4 MAX) [0]:
PROC RTUs reserved for domain A (4 MAX) [0]: 4
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]:
Check license installation and reserved CPUs in Domain A.
server_sc0:SC>showcodusage -v
Continued
68P02901W47-S
2-11
Jul 2008
Chapter 2:
Procedure 2-2 Configuring the system controller when using Ultra Sparc IV+
processors (Continued)
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
2-12
68P02901W47-S
Jul 2008
Procedure 2-2 Configuring the system controller when using Ultra Sparc IV+
processors (Continued)
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
10
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
Chapter 2:
Figure 2-2
Figure 2-3
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
Procedure 2-3
68P02901W47-S
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
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
Procedure 2-4
2-16
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
68P02901W47-S
2-17
Jul 2008
Table 2-1
Chapter 2:
Disk allotments
Slot
Disk name
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
Figure 2-7
Cabling procedure
To cable the Netra 440, follow this procedure:
Procedure 2-5
68P02901W47-S
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
Chapter 2: Operating System and OMC-R Software Installation on the Single Platform Processor
Figure 2-8
ti-gsm-Fully_cabled_Netra_440-0008-ai-sw
2-20
68P02901W47-S
Jul 2008
Figure 2-9
68P02901W47-S
2-21
Jul 2008
Chapter 2: Operating System and OMC-R Software Installation on the Single Platform Processor
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
Table 2-2
Disk allotment
Slot
Disk name
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
Netra 20 configuration
Netra 20 configuration
After the Netra 20 and StorEdge 3310 disk array are mounted, two UltraSCSI cables are
attached.
Figure 2-11
Netra 20
Figure 2-12
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
Netra 20 configuration
Chapter 2: Operating System and OMC-R Software Installation on the Single Platform Processor
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
Netra 20 configuration
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
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
Operating System and OMC-R Software Installation on the Single Platform Processor
Chapter 2:
Introduction
Solaris is installed using a customized jumpstart. The jumpstart performs the following tasks:
Provides the system with host, IP Address, Netmask, and Default Router.
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
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
Required Information
Record Values
68P02901W47-S
2-27
Jul 2008
Installing the Solaris and OMC Software on the SunFire 4800/4900, Netra 440, and Netra 20
Operating System and OMC-R Software Installation on the Single Platform Processor
Chapter 2:
Procedure 2-6
Installing Solaris
Load the Jumpstart DVD into the DVD-ROM drive on the Single Platform
Processor.
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.
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.
Procedure 2-7
Select Domain A.
Continued
2-28
68P02901W47-S
Jul 2008
Procedure 2-7
3
Installing
Enter the following command at the OK> prompt, and press Return to set
NVRAM parameters to default values:
set-defaults
Enter the following command to reboot the server and press Return:
reset-all
The following output is displayed:
Resetting,..
Copying IO prom to cpu dram
{/N0/SB2/P2} @(#) lpost
5.15.4
2004/02/05 19:08
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
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
Installing the Solaris and OMC Software on the SunFire 4800/4900, Netra 440, and Netra 20
Operating System and OMC-R Software Installation on the Single Platform Processor
Procedure 2-7
6
Chapter 2:
Enter the following command, which identifies all of the devices attached
to the SCSI bus, and press Return:
probe-scsi-all
Processor
SUN
D240
Target 4
Unit 0
Disk
Target 6
Unit 0
M14011009
7
NOTE
To continue the Solaris installation, refer to Procedure 2-14.
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
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
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
Installing the Solaris and OMC Software on the SunFire 4800/4900, Netra 440, and Netra 20
Operating System and OMC-R Software Installation on the Single Platform Processor
Chapter 2:
The following procedure describes the steps required to install the patch update.
Procedure 2-10
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.
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
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
On the GUI server, return the FTP access for root to its previous setting, if
amended in the file /etc/ftpusers.
Next type 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
Continued
68P02901W47-S
2-33
Jul 2008
Installing the Solaris and OMC Software on the SunFire 4800/4900, Netra 440, and Netra 20
Operating System and OMC-R Software Installation on the Single Platform Processor
Procedure 2-12
Chapter 2:
NOTE
To continue the Solaris installation, refer to Continue Solaris
installation on page 2-35.
Enter the following command to reboot the server, and press Return:
reset-all
2-34
68P02901W47-S
Jul 2008
Procedure 2-13
Installing
Sun Netra
T4 (2 X UltraSPARC-III+), No Keyboard.
Copyright 1998-2002 Sun Microsystems, Inc.
NOTE
To continue the Solaris installation, refer to Continue Solaris
installation on page 2-35.
Procedure 2-14
68P02901W47-S
2-35
Jul 2008
Installing the Solaris and OMC Software on the SunFire 4800/4900, Netra 440, and Netra 20
Operating System and OMC-R Software Installation on the Single Platform Processor
Procedure 2-14
Chapter 2:
A prompt is displayed for entering the host name. Enter the hostname and
press Return. The following output is displayed:
Motorola Common Platform GSM OMCR Installation
==============================================
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: !$%^&*(){}~@?>:<|.[]_.
2-36
68P02901W47-S
Jul 2008
Procedure 2-14
4
Installing
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.
The following output is displayed:
Motorola Common Platform GSM OMCR Installation
==============================================
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
68P02901W47-S
2-37
Jul 2008
Installing the Solaris and OMC Software on the SunFire 4800/4900, Netra 440, and Netra 20
Operating System and OMC-R Software Installation on the Single Platform Processor
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:
Motorola Common Platform GSM OMCR Installation
==============================================
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.
NOTE
If you are configuring DNS, it is necessary to enter the Domain
name and to supply a primary DNS IP address.
9
2-38
68P02901W47-S
Jul 2008
Procedure 2-14
Installing
68P02901W47-S
2-39
Jul 2008
Installing the Solaris and OMC Software on the SunFire 4800/4900, Netra 440, and Netra 20
Operating System and OMC-R Software Installation on the Single Platform Processor
Procedure 2-14
12
Chapter 2:
13
14
15
16
2-40
68P02901W47-S
Jul 2008
Procedure 2-14
17
Installing
18
19
US/Central
US/Mountain
US/Pacific
Japan
68P02901W47-S
2-41
Jul 2008
Installing the Solaris and OMC Software on the SunFire 4800/4900, Netra 440, and Netra 20
Operating System and OMC-R Software Installation on the Single Platform Processor
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
Printer
-----------------
-------
-----------------
-------
IP: 166.3.22.212
IP:
Networking
---------Default Router: 166.3.22.84
Domain: cork.cig.mot.com
TIME
---
---
Primary: 166.3.50.200
TIMESERVER:
Secondary:
TIMEZONE: Eire
Tertiary:
MCC: 353
MNC: 123
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
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]:
NOTE
Entering y enables the debugging mode.
68P02901W47-S
2-43
Jul 2008
Installing the Solaris and OMC Software on the SunFire 4800/4900, Netra 440, and Netra 20
Operating System and OMC-R Software Installation on the Single Platform Processor
Chapter 2:
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
Configuration checks
Procedure 2-15
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
68P02901W47-S
2-45
Jul 2008
Procedure 2-15
Chapter 2:
2-46
68P02901W47-S
Jul 2008
Procedure 2-15
Installing 122660-07
Validating patches...
Validating patches...
Done!
Loading patches requested to install.
Done!
The following requested patches are already installed on the system
Requested to install patch 122660-07 is already installed on the
system.
No patches to check dependency.
Patch install completed on Wed Jul 25 17:20:25 BST 2007
68P02901W47-S
2-47
Jul 2008
Chapter 2:
2-48
68P02901W47-S
Jul 2008
Table 2-5
Field
Comments
Record Number
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
Field
Comments
X.121 Address
Interface Type
OMC-R Process
Protocol
Set to X.25.
Packet Size
Window Size
For example, 2.
Table 2-6
Number
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
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
Interface Type = H
Protocol = X25
Window size = 2
Procedure 2-16
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.
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
NOTE
The following example shows sample entries for the /etc/hosts file:
127.0.0.1
localhost
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
If you are using NIS, then execute the following commands as user root:
cd /var/yp
/usr/ccs/bin/make
68P02901W47-S
2-53
Jul 2008
Chapter 2: Operating System and OMC-R Software Installation on the Single Platform Processor
Is:
the Single Platform Processor hostname.
<guiserver1>
<guiclient1>
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
68P02901W47-S
2-55
Jul 2008
Procedure 2-18
Chapter 2:
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
2-56
68P02901W47-S
Jul 2008
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.
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
Continued
68P02901W47-S
2-57
Jul 2008
Table 2-7
2-58
Chapter 2:
Netra
20
SF/Netra
20
SF/Netra
20
SF/Netra
20
SF/Netra
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
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
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
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
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
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
probeide
On a Sunblade platform, output similar to the following should be seen:
Device 0
( Primary Master )
( 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
143374738 Blocks, 73 GB
SASAddress 5000c5000092b149
PhyNum 0
Target 1
Unit 0
Disk
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
A prompt is displayed for entering the host name. Enter the hostname and
press Return. The following output is displayed:
Motorola GSM OMC-R GUI Server Installation
==========================================
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
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
68P02901W47-S
3-5
Jul 2008
Running Jumpstart
Procedure 3-2
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
68P02901W47-S
3-7
Jul 2008
Running Jumpstart
Procedure 3-2
10
11
12
US/Central
US/Mountain
US/Pacific
Japan
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
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:
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
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
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
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:
svccfg: Pattern 'omc' doesn't match any instances or services
svccfg: Pattern 'omc' doesn't match any instances or services
svcadm: Pattern 'omc' doesn't match any instances
NOTE
3-12
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
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.
68P02901W47-S
3-13
Jul 2008
Configuration checks
Configuration checks
Procedure 3-3
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
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
/cdrom/cdrom0/suninstall/Patches --patch_order
/cdrom/cdrom0/suninstall/Patches/patch_order
Patches to be installed: 3
Now installing patches...please wait...
68P02901W47-S
3-15
Jul 2008
Procedure 3-3
3-16
68P02901W47-S
Jul 2008
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.
Table 3-1
Name
Usage
7588
File system
swap
592
Swap space
/usr/omc
4220
File system
68P02901W47-S
3-17
Jul 2008
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
3-18
68P02901W47-S
Jul 2008
Procedure 3-4
3
auto_home
-nobrowse
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
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
3-20
68P02901W47-S
Jul 2008
Procedure 3-4
10
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
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
Procedure 3-5
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
68P02901W47-S
3-23
Jul 2008
Procedure 3-5
3-24
68P02901W47-S
Jul 2008
Procedure 3-5
Installing 122660-07
Validating patches...
Validating patches...
Done!
Loading patches requested to install.
Done!
The following requested patches are already installed on the system
Requested to install patch 122660-07 is already installed on the
system.
No patches to check dependency.
Patch install completed on Wed Jul 25 17:20:25 BST 2007
68P02901W47-S
3-25
Jul 2008
Overview of installation
This section describes the installation procedures used for installation and configuration of the
SunRay Server Software.
Figure 3-1
ti-gsm_Connecting_optional_SunRay DTU_to_Netra210-0022-ai-sw
3-26
68P02901W47-S
Jul 2008
Figure 3-2
Preparation procedure
Switch
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.
Preparation procedure
Prepare the system for the SunRay Server Software installation by performing the following
steps on the Netra210:
Procedure 3-6
68P02901W47-S
Preparation procedure
3-27
Jul 2008
Procedure 3-7
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.
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
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.
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
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.
Memory
Graphics Card
270 MHz
128 MB RAM
4 GB
Required
4-2
68P02901W47-S
Jul 2008
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
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
A prompt is displayed for entering the host name. Enter the hostname and
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
68P02901W47-S
4-3
Jul 2008
Running Jumpstart
Procedure 4-1
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
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.
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.
4-5
Jul 2008
4-6
68P02901W47-S
Jul 2008
Procedure 4-3
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
68P02901W47-S
4-7
Jul 2008
Procedure 4-3
6
4-8
68P02901W47-S
Jul 2008
Procedure 4-4
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
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.
Procedure 4-5
4-10
68P02901W47-S
Jul 2008
Procedure 4-6
Figure 4-1
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
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
Sun Netra 20
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:
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.
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:
68P02901W47-S
5-3
Jul 2008
Table 5-1
Valid input
Default
Sun
20 or 21 inch colour
monitor
3.0 A
2.0 A
Sun
SunFire 4800/4900
16 A
Sun
Netra 20
90 to 240 Vac, 47 to
63 Hz
7.2 A
Sun
Netra 440
7.2 A
Sun
Sunblade 150
0.3 K VA
Sun
Netra 210
4.6 A
Sun
0.8 A
0.4 A
Wyse
WY - 120
0.3A
Cisco
3662 Router
3.0 A
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
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
68P02901W47-S
5-5
Jul 2008
5-6
68P02901W47-S
Jul 2008
Figure 5-1
68P02901W47-S
5-7
Jul 2008
Figure 5-2
177 MM
MO NT
435 MM
508 MM
TOP
ti-gsm_Sun_Netra_20_dimensions-0028-ai-sw
5-8
68P02901W47-S
Jul 2008
Figure 5-3
ti-gsm_Front_view_of_Sun_Netra_440-0029-ai-sw
68P02901W47-S
5-9
Jul 2008
Figure 5-4
ti-gsm_Sun_Netra_440_dimensions-0030-ai-sw
5-10
68P02901W47-S
Jul 2008
Figure 5-5
ti-gsm_Front_view_of_Sun_SunFire_4800/4900-0031-ai-sw
68P02901W47-S
5-11
Jul 2008
Figure 5-6
724 MM
762 MM
TOP
FRONT
ti-gsm_Sun_SunFire_4800/4900_dimensions-0032-ai-sw
5-12
68P02901W47-S
Jul 2008
Figure 5-7
68P02901W47-S
5-13
Jul 2008
Figure 5-8
ti-gsm_Sunblade_150_dimensions-0036-ai-sw
Figure 5-9
ti-gsm_Front_view_of_a_Netra_210-0077-ai-sw
5-14
68P02901W47-S
Jul 2008
Figure 5-10
ti-gsm_Netra_210_dimensions-0078-ai-sw
68P02901W47-S
5-15
Jul 2008
Figure 5-11
ti-gsm_Cisco_3662_Router-0041-ai-sw
5-16
68P02901W47-S
Jul 2008
Figure 5-12
ti-gsm_Cisco_3662_Router_dimensions-0042-ai-sw
68P02901W47-S
5-17
Jul 2008
Check equipment received: Describes how to use the bill of materials to check all
equipment.
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.
X.25 version verification: Describes how to provide verification of the X.25 version.
Before power-up
Before commencing power-up, proceed as follows:
5-18
Check all equipment to ensure compatibility with the local power supply.
68P02901W47-S
Jul 2008
Procedure 5-1
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
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
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).
Procedure 5-2
Login as root on the Single Platform Processor and create a tape archive as
follows:
tar -cvf /dev/rmt/0 /tmp
Procedure 5-3
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
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.
Procedure 5-5
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
68P02901W47-S
Jul 2008
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
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
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
68P02901W47-S
Jul 2008
Network verification
Network verification
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.
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
68P02901W47-S
5-25
Jul 2008
Check users
Procedure 5-8
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
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
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
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.
5.20.3
2006/10/21 06:21
5.20.3
2006/10/21 06:21
5.20.3
2006/10/21 06:21
5.20.3
2006/10/21 06:21
5.20.3
2006/10/21 06:21
5.20.3
2006/10/21 06:21
5.20.3
2006/10/21 06:32
5.20.3
2006/10/21 06:21
5.20.3
2006/10/21 06:21
5.20.3
2006/10/21 06:32
5.20.3
2006/10/21 06:21
68P02901W47-S
5.20.3
2006/10/21 06:21
5-29
Jul 2008
5.20.3
2006/10/21 06:21
5.20.3
2006/10/21 06:21
{/N0/SB0/P0/C0}
{/N0/SB0/P0/C0}
{/N0/SB0/P0/C0}
{/N0/SB0/P0/C0}
{/N0/SB0/P0/C0}
{/N0/SB0/P0/C0}
{/N0/SB0/P0/C0}
{/N0/SB0/P0/C0}
{/N0/SB0/P0/C0}
N0/SB0/P0/C0}
{/N0/SB0/P0/C0}
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
SunFire E4900
OpenFirmware version 5.20.3 (10/21/06 06:17)
Copyright 2006 Sun Microsystems, Inc.
68P02901W47-S
5-31
Jul 2008
boot
Resetting ...
Sun Blade 150 (UltraSPARC-IIe 550MHz), No Keyboard
Copyright 1998-2002 Sun Microsystems, Inc.
5ff3a000
Initializing
5fe46000
Initializing
5f002000
Initializing
5e002000
Initializing
40000000
Initializing
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.
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
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
Setting addresses
To set X.121 addresses at the NE, enter the changes at the NE using a PC.
Table 6-1
link_num
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
Procedure 6-1
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).
nn
dd
6-4
Is:
ee
hh
xx
68P02901W47-S
Jul 2008
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).
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.
Procedure 6-2
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
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.
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
Procedure 6-3
Procedure 6-4
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
INFORMIX IN ONLINE
MODE & OMC
APP LICATIONS RU NNING
omc stop
omc s ta rt
on monitor
Mode -Graceful
Shutdown
Ta ke-Off Line
Single Us e r Mode
ti-gsm_Single_Platform_Processor_startup_and_ shutdown-0043-ai-sw
Procedure 6-5
6-8
68P02901W47-S
Jul 2008
Procedure 6-6
Shut down the Single Platform Processor by entering the following command:
/usr/sbin/shutdown -y -g0 -i0
68P02901W47-S
6-9
Jul 2008
Figure 6-2
GUI AP PLICATIONS
RUNNING
OMC Us e r(s ) Log On to
On
This GUI S e rve r
Multi Us e r Mode
or its C lie nt
SINGLE USER
ctrl -d
MODE
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
68P02901W47-S
Jul 2008
NE node configuration
Add each NE that is connected to the OMC-R to:
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.
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:
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.
Procedure 6-8
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
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
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
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.
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.
68P02901W47-S
6-15
Jul 2008
Figure 6-4
The OMC-R front panel is described in Table 6-2. The numbers refer to Figure 6-4.
Table 6-2
Number
Description
Number
Description
User name
Access to OMC-R
console
10
Access to configuration
management
11
Access to event
management
12
Access to performance
management
13
Access to scheduled
functions
Access to load
management
14
15
Alarm summary
16
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
Introduction
This chapter provides information about the following:
Table 6-3
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 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
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
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
Procedure 6-10
Type:
show-disks
The following output is displayed:
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
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.
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
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.
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
Procedure 6-13
6-22
Each user should then do the following to set up a Motorola Backdrop that
suits: Login using the CDE login screen.
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
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.
Setting up remote Single Platform Processor: describes how to set up a remote Single
Platform Processor.
68P02901W47-S
Jul 2008
Introduction
This section describes how to set up the Wyse 120 terminal for use as a dumb terminal.
NOTE
Before powering up the Netra 20, Netra 440, SunFire 4800 or SunFire 4900, set
up the console.
Procedure 7-1
Press the appropriate function key to access the setup submenu (Table 7-1).
Table 7-1
68P02901W47-S
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
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.
Procedure 7-2
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.
68P02901W47-S
7-5
Jul 2008
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.
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.
Is:
<printer_alias>
<printer_name>
<print_command>
7-6
The printer script specified in the printer configuration file does not exist in
/usr/omc/current/bin on the GUI processor.
68P02901W47-S
Jul 2008
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 326x
MultiModem MT5634ZBA
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
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)
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):
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).
NOTE
The root password is required to install or modify files for modem installation.
7-10
68P02901W47-S
Jul 2008
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.
PMTAG
<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
NOTE
Ensure that tip is executed in a shell without scrolling enabled; otherwise, a carriage
return is not sent.
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
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
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.
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.
68P02901W47-S
7-13
Jul 2008
Procedure 7-4
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 type
DTE rate
Initialization command
Motorola 3460
38400
AT&FQ2*DE19*FL3&D2&C1*CL0S0=2&Y1&W1
19200
AT&FQ2*DE12*FL3&D2&C1*CL0S0=2&Y1&W1
9600
Motorola 326X
AT&FQ2*DE8*FL3&D2&C1*CL0S0=2&Y1&W1
38400
AT&FQ2*DE15*FL3&D2&C1*AA2&Y1&W1
19200
AT&FQ2*DE12*FL3&D2&C1*AA2&Y1&W1
9600
AT&FQ2*DE8*FL3&D2&C1*AA2&Y1&W1
NOTE
The syntax of the AT commands is specified in the Motorola 3460 FastR User Guide.
Table 7-3
Symbol
Meaning
Notes
AT
&Fz
Q2
RsltCode = Orig
7-14
68P02901W47-S
Jul 2008
Table 7-3
68P02901W47-S
Symbol
Meaning
Notes
DE
*FL3
&D2
&C1
*AA2
Answer=Ring #2
&Y1
Power Up In=1
&W1
Save Changes=1
7-15
Jul 2008
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>
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.
Procedure 7-5
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:
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
AT commands
The AT commands that are used when initializing the MultiModem MT5634ZBA are described in
Table 7-4.
Table 7-4
AT command
Description
AT$SBnnnnn
AT&K3
AT&D2
AT&C1
ATS0=2
AT&Q0
AT&W0
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.
Continued
68P02901W47-S
7-17
Jul 2008
Procedure 7-6
Setting required
28800
38400m
14400
19200m
9600
9600m
Verify that all amended fields are correct, and then click OK.
10
To verify that a port monitor has been configured, enter the following
command at the # prompt:
pmadm -p zsmon -l
An example output is:
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.
7-18
68P02901W47-S
Jul 2008
Problem symptoms
If the following problems are experienced, solutions are detailed in this section:
No login prompt
On dialing into the SPARCstation, the modem never picks up the phone
No utmpx entry
Procedure 7-7
68P02901W47-S
7-19
Jul 2008
Procedure 7-7
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
An example output is:
/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
Check if the ttymon process TTY has changed from ? to term/b by typing
the following command at the # prompt:
ps -ef | grep ttymon
An example output is:
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
An example output is:
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
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).
Procedure 7-9
Check in /var/spool/locks for a lock file LCK.* and remove that file.
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.
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.
68P02901W47-S
7-23
Jul 2008
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.
Figure 7-2
PRINTER
PRINTER
ROUTER
SINGLE PLATFORM
PROCESSOR
MONITORING
ST ATION
REGIONAL OMC
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
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.
68P02901W47-S
7-25
Jul 2008
Figure 7-3
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
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.
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
System
Hostname
IP address
local_sys
remote_sys
local_gui
Table 7-6
Account
User name
UID
7-28
68P02901W47-S
Jul 2008
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.
Creation of a new account: describes how to create an account to use the remote OMC-R.
Procedure 7-11
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.
68P02901W47-S
7-29
Jul 2008
Procedure 7-12
NOTE
Each of the five above commands should be treated as one
continuous line.
2
7-30
68P02901W47-S
Jul 2008
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/config/global
/usr/omc/ne_data
/usr/omc/ne_data/raw_stats
/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
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.14 netprinter
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.14 netprinter
111.111.11.13 guiclient1
111.111.111.21 remote_sys omc_splat omc_pm omc_4gl
NOTE
The GUI server automatically reboots.
7-32
68P02901W47-S
Jul 2008
Chapter
8
Cisco 3662 Installation
68P02901W47-S
Jul 2008
8-1
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:
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.
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
Figure 8-2
Figure 8-3
8-4
68P02901W47-S
Jul 2008
Table 8-1
Slot
Number
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
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
8-6
68P02901W47-S
Jul 2008
Introduction
Prerequisites
Initial configuration
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.
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.
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
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
ti-gsm_Connect_T o_dialog_box-0069-ai-sw
8-8
68P02901W47-S
Jul 2008
Procedure 8-1
6
Initial configuration
Set the COM Properties dialog box fields to the values shown in Figure 8-5
and click OK.
Figure 8-5
ti-gsm_COM_Properties_dialog_box-0070-ai-sw
Initial configuration
Once the previous section is complete, follow Procedure 8-2 to perform the initial configuration.
68P02901W47-S
8-9
Jul 2008
Initial configuration
Procedure 8-2
Initial configuration
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.
8-10
68P02901W47-S
Jul 2008
Procedure 8-2
5
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.
Procedure 8-3
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
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.
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
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
8-12
68P02901W47-S
Jul 2008
NOTE
It is also possible to configure the router through the existing console connection, in
which case this procedure can be skipped.
Procedure 8-5
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(config)# CTRL-z
X25-3662#
68P02901W47-S
8-13
Jul 2008
Procedure 8-5
4
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
68P02901W47-S
Jul 2008
Introduction
The following are covered in this section:
Procedure 8-6
68P02901W47-S
8-15
Jul 2008
Procedure 8-6
2
NOTE
The default packet size is 128 and the window size is 2.
Table 8-2
Field
Comments
Record Number
Continued
8-16
68P02901W47-S
Jul 2008
Table 8-2
Field
Comments
Interface Type
OMC-R Process
Protocol .
Set to X.25.
Packet Size
Window Size
For example, 2.
Table 8-3
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
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.
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
Cisco 3662
Port 0
Connects to 1/0
Port 1
Connects to 1/1
Port 2
Connects to 1/2
Connects to 1/3
Port 4
Connects to 2/0
Port 5
Connects to 2/1
Port 6
Connects to 2/2
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.
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.
Execute these commands for each serial interface that is connected to the
OMC. The only parameter change necessary is the physical interface 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 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-if)# exit
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# write memory
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
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
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.
68P02901W47-S
8-21
Jul 2008
Table 8-5
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
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
Step
Purpose
controller E1 <slot
number/port number>
Exit
Exit
68P02901W47-S
8-23
Jul 2008
Procedure 8-8
NOTE
NOTE
NOTE
Continued
8-24
68P02901W47-S
Jul 2008
Procedure 8-8
Exit Controller:
X25-3662(config-controller)# exit
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:
X25-3662# show running-config
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
!
interface Serial3/0:1 (For Timeslot 2)
no ip address
!
interface Serial3/0:2 (For Timeslot 3)
no ip address and so on.
68P02901W47-S
8-25
Jul 2008
Procedure 8-9
NOTE
The channel number is the timeslot number minus 1.
X25-3662(config-if)# encapsulation x25 profile GSM
X25-3662(config-if)# exit
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(config)# ^Z
X25-3662# write memory
X25-3662# show interface serial <slot number/port
number:channel #>
The following output is displayed:
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
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.
Procedure 8-10
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
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
Procedure 8-11
NOTE
68P02901W47-S
8-29
Jul 2008
Procedure 8-12
NOTE
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.
X25-3662(config-x25-huntgroup)# exit
2
8-30
68P02901W47-S
Jul 2008
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
nn
dd
ee
hh
xx
8-32
68P02901W47-S
Jul 2008
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 [ ].
Procedure 8-13
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 2020130001062 hunt-group BOOTLOAD
X25 route 2020130000241 hunt-group EVENTS
X25 route 2020130001142 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
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
X25 route 41503002010000 interface serial 4/1:5
8-34
68P02901W47-S
Jul 2008
Introduction
The following are covered in this section:
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
Interface commands
The following commands are useful to view the status of the 3662 interfaces.
8-36
68P02901W47-S
Jul 2008
X.25 commands
The following commands are useful to verify and monitor the X.25 network:
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
68P02901W47-S
8-37
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 address of the tftp server when prompted.
Enter the full path and filename when prompted.
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.
8-38
68P02901W47-S
Jul 2008
Chapter
9
Cisco 3845 Installation
68P02901W47-S
Jul 2008
9-1
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:
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.
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
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
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
Figure 9-3
9-4
68P02901W47-S
Jul 2008
Table 9-1
Slot
Number
1 4
0/0
0/1
Router capacity
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
9-6
68P02901W47-S
Jul 2008
Introduction
Prerequisites
Initial configuration
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.
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.
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
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
9-9
Jul 2008
Initial configuration
Initial configuration
Once the previous section is complete, perform the initial configuration by following this
procedure:
Procedure 9-2
Initial configuration
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
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.
Procedure 9-3
68P02901W47-S
9-11
Jul 2008
Procedure 9-3
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.
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.
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
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
9-12
68P02901W47-S
Jul 2008
Procedure 9-4
3
NOTE
It is also possible to configure the router through the existing console connection, in
which case this procedure can be skipped.
Procedure 9-5
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
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(config)# CTRL-z
X25-3845#
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:
X25-3845# write memory
68P02901W47-S
Jul 2008
Introduction
The following are covered in this section:
Procedure 9-6
68P02901W47-S
9-15
Jul 2008
Procedure 9-6
2
Table 9-2
Comments
Record Number
Interface Type
9-16
68P02901W47-S
Jul 2008
Table 9-2
Comments
OMC-R Process
Protocol .
Set to X.25.
Packet Size
Window Size
For example, 2.
Table 9-3
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
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.
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
Cisco 3845
Port 0
Connects to 0/0/0
Port 1
Connects to 0/0/1
Port 2
Connects to 0/0/2
Connects to 0/0/3
Port 4
Connects to 0/1/0
Continued
9-18
68P02901W47-S
Jul 2008
Table 9-4
Cisco 3845
Port 5
Connects to 0/1/1
Port 6
Connects to 0/1/2
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.
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 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(config)# ^Z
X25-3845# write memory
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
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
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.
68P02901W47-S
9-21
Jul 2008
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:
X25-3845# show running-config
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# configure terminal
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:
X25-3845# show running-config
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
Step
Purpose
controller E1 <slot
number/port number>
Exit
Exit
68P02901W47-S
9-23
Jul 2008
Procedure 9-8
NOTE
NOTE
Exit Controller:
X25-3845(config-controller)# exit
Continued
9-24
68P02901W47-S
Jul 2008
Procedure 9-8
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:
X25-3845# show running-config
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.
interface Serial3/0:0 (For Timeslot 1)
no ip address
!
interface Serial3/0:1 (For Timeslot 2)
no ip address
!
interface Serial3/0:2 (For Timeslot 3)
no ip address and so on.
68P02901W47-S
9-25
Jul 2008
Procedure 9-9
NOTE
The channel number is the timeslot number minus 1.
X25-3845(config-if)# encapsulation x25 profile GSM
X25-3845(config-if)# exit
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(config)# ^Z
X25-3845# write memory
X25-3845# show interface serial <slot number/port
number:channel #>
The following output is displayed:
X25-3845#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
Continued
9-26
68P02901W47-S
Jul 2008
Procedure 9-9
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.
Procedure 9-10
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
Procedure 9-11
NOTE
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: 0/0/0, 0/0/1, 0/0/2, 0/1/0, 0/1/1, 0/1/2
3
68P02901W47-S
9-29
Jul 2008
Procedure 9-12
NOTE
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: 0/0/0, 0/0/1, 0/0/2, 0/1/0, 0/1/1, 0/1/2
X25-3845(config-x25-huntgroup)# exit
2
9-30
68P02901W47-S
Jul 2008
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
nn
dd
ee
hh
xx
9-32
68P02901W47-S
Jul 2008
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 [ ].
Procedure 9-13
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:
X25 route 2020130000061 hunt-group BOOTLOAD
X25 route 2020130001062 hunt-group BOOTLOAD
X25 route 2020130000241 hunt-group EVENTS
X25 route 2020130001142 hunt-group EVENTS
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
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.
X25 route 41503002010000 interface serial 1/1:5
X25 route 41503002010000 interface serial 2/1:5
9-34
68P02901W47-S
Jul 2008
68P02901W47-S
9-35
Jul 2008
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
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
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
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
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-if)# no shutdown
X25-3845(config-if)# exit
X25-3845(config)#
2
Once all interfaces are configured, save the configuration by doing the
following:
X25-3845(config)#
X25-3845(config)# ^Z
X25-3845# write memory
Procedure 9-18
9-38
68P02901W47-S
Jul 2008
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
9-39
Jul 2008
Procedure 9-19
NOTE
This Ethernet connection is on a separate LAN to the other
connection 0/0 used for configuration.
9-40
68P02901W47-S
Jul 2008
Introduction
The following are covered in this section:
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
Interface commands
The following commands are useful to view the status of the 3845 interfaces.
9-42
68P02901W47-S
Jul 2008
X.25 commands
The following commands are useful to verify and monitor the X.25 network:
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
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 address of the tftp server when prompted.
Enter the full path and filename when prompted.
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.
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
NOTE
The procedure takes a couple of minutes to complete.
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
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.
Procedure 10-3
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 .
Procedure 10-4
Execute:
password
Enter new password:
Enter new password again
68P02901W47-S
10-3
Jul 2008
If the password is already set and the administrator has to change the password, execute the
following procedure:
Procedure 10-5
Execute:
password
Enter current password:
Enter new password:
Enter new password again
Procedure 10-6
Execute:
password
Enter new password:
Enter new password again
Procedure 10-7
Log into the main System Controller, and connect to the Platform Shell.
Execute:
setfailover on
10-4
68P02901W47-S
Jul 2008
Procedure 10-8
Login to Domain A.
Take a copy of the output of the following commands to record the system
variables:
printenv
devalias
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
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
IX-7
Index
D
DTE addressing at node elements.
Addressing requirements . . . .
OMC-R addresses - general rules
Setting addresses . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
6-3
6-3
6-4
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
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
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
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
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
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
5-25
5-25
O
OMC-R verification . . . . . . . . . . . .
Check OMC-R applications . . . . . . .
Introduction. . . . . . . . . . . . . . .
6-12
6-15
6-12
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
Index
R
Remote Single Platform Processor setup. .
Creation of a new account . . . . . . .
Exporting file changes . . . . . . . . .
7-29
7-30
7-29
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
Single Platform Processor verification
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
Index
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-26
3-28
3-28
3-26
3-27
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
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
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
IX-11
68P02901W47-S
Manual Title
Printing
Finishing
GSR9
68P02901W47-S
GSR9
68P02901W47-S
Cutting
datum point
Spine
Front cover