Preventative 68p09278a29

PoC Preventative Maintenance Procedures
and Checklists
68P09278A29-A
2006 Motorola, Inc.
FEB 2007
All Rights Reserved
Notice
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. The information in this document has been
carefully checked and is believed to be entirely reliable. However, no responsibility is assumed for inaccuracies or omissions. Motorola, Inc. reserves the right to make changes to
any products described herein 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 instruction manual, and the Motorola products described in this instruction manual may
be, include or describe copyrighted Motorola material, such as computer programs stored
in semiconductor memories or other media. Laws in the United States and other countries
preserve for Motorola and its licensors 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 and its
licensors contained herein or in the Motorola products described in this instruction manual
may not be copied, reproduced, distributed, merged or modied 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, as arises by operation of law in the sale of a product.
Usage and Disclosure Restrictions
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.
Copyrighted Materials
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.
High Risk Materials
Components, units, or third-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 Trafc
Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s) specically disclaim any expressed or implied warranty of tness for such High Risk
Activities.
Trademarks
Motorola and the Stylized M Logo are registered in the US Patent & Trademark Ofce. All
other product or service names are the property of their respective owners.
FEB 2007
Table
of
Contents
Contents
PoC Preventative Maintenance Procedures and Checklists

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
3
3
3
3
5
5
5
5
6
7
7
7
7
8
9
9
9
9
9
10
10
10
11
11
12
12
12
13
13
13
14
14
15
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PointtoPoint call test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Group call test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-2
1-3
1-4
Revision history . . . . . . . . . . . . . . . . . . . . . . . . . .
Version information . . . . . . . . . . . . . . . . . . . . . .
General information . . . . . . . . . . . . . . . . . . . . . . . .
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cross references . . . . . . . . . . . . . . . . . . . . . . . .
Text conventions . . . . . . . . . . . . . . . . . . . . . . . .
Contacting Motorola . . . . . . . . . . . . . . . . . . . . . . . .
Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Questions and comments . . . . . . . . . . . . . . . . . . .
24 hour support . . . . . . . . . . . . . . . . . . . . . . . .
Security Advice . . . . . . . . . . . . . . . . . . . . . . . . . .
Warnings and cautions . . . . . . . . . . . . . . . . . . . . . . .
Failure to comply with warnings . . . . . . . . . . . . . . . .
Warnings. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cautions . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General Safety . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ground the equipment . . . . . . . . . . . . . . . . . . . . .
Do not operate in an explosive atmosphere . . . . . . . . . .
Keep away from live circuits . . . . . . . . . . . . . . . . . .
Do not service or adjust alone . . . . . . . . . . . . . . . . .
Use caution when exposing or handling the CRT. . . . . . . .
Do not substitute parts or modify equipment . . . . . . . . .
Potentially hazardous procedure warnings. . . . . . . . . . .
Devices sensitive to static . . . . . . . . . . . . . . . . . . . . .
Special handling techniques . . . . . . . . . . . . . . . . . .
Caring for the environment . . . . . . . . . . . . . . . . . . . .
Disposal of Motorola Networks equipment in EU countries . .
Disposal of Motorola Networks equipment in non-EU countries
Motorola document set . . . . . . . . . . . . . . . . . . . . . .
Ordering documents and CD-ROMs . . . . . . . . . . . . . .
Document banner denitions . . . . . . . . . . . . . . . . .
Third Party Computer Software and Trademarks . . . . . . . . .
Computer Software . . . . . . . . . . . . . . . . . . . . . .
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 1: Call testing procedure
68P09278A29-A
FEB 2007
Contents
Chapter 2: Checking the AD

AD verication . . . . . . . . . . . . . . . .
Verifying active processes . . . . . . . . . .
Verifying active directories are synchronized
Verifying cluster status. . . . . . . . . . . .
Verifying TL1. . . . . . . . . . . . . . . . .
Checking disk space . . . . . . . . . . . . .
Checking for core les . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-2
2-4
2-5
2-6
2-7
2-8
2-9
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
3-2
3-3
3-4
3-5
3-6
Chapter 3: Checking the CS

Verifying billing le creation .
Verifying cluster status. . . .
Verifying TL1. . . . . . . . .
Checking disk space . . . . .
Checking for core les . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Chapter 4: Checking call statistics, alarms, and process utilization

Appendix A: Preventative maintenance checklists for PoC
Appendix B: Acronyms and abbreviations
ii
68P09278A29-A
FEB 2007
About
This
Manual
PoC Preventative Maintenance Procedures

and Checklists
What is covered in this manual?
Purpose The purpose of this document is to provide a method of monitoring the system
health of the PushtoTalk over Cellular (PoC) system for CDMA and GSM networks.
Audience The person running the procedure should have a basic understanding of
the PoC system and how to make PoC calls, as well as general knowledge of linux, web
browsers, and telnet.
Location requirements This procedure can only be run from inside the service
providers network. Therefore the person running this procedure must be connected to
the service providers LAN or WAN or be connected via Virtual Private Network (VPN).
Additionally, the call testing portion can only be tested in areas where the service provider
has PoC coverage.
Scheduling This procedure can be run to determine system health at any time and does
not require a maintenance window. If the customer requires periodic monitoring, run this
procedure at set intervals and record the results during the scheduled run times. The
scheduling and recording of results are not covered in this document.
68P09278A29-A
FEB 2007
Revision history
Revision history
The following shows the status of this document since it was rst released.
Version information
Document
issue
Date of issue
Remarks
FEB 2007
First issue
68P09278A29-A
FEB 2007
General information
General information
Motorola disclaims all liability whatsoever, implied or express, 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 customers behalf, to abide by the
instructions, system parameters or recommendations made in this document.
Purpose
Motorola cellular communications documents are intended to instruct and assist personnel in
the operation, installation and maintenance of the Motorola cellular infrastructure equipment
and ancillary devices. It is recommended that all personnel engaged in such activities be
properly trained by Motorola.
Failure to comply with Motorolas operation, installation and maintenance instructions

may, in exceptional circumstances, lead to serious injury or death.
These documents are not intended to replace the system and equipment training offered by
Motorola, although they can be used to supplement and enhance the knowledge gained through
such training.
Cross references
Throughout this document, references are made to external publications, chapter numbers
and section names. The references to external publications are shown in italics. Chapter and
section name cross references are emphasized in blue text in electronic versions. These are
active links to the references.
This document is divided into uniquely identied and numbered chapters that, in turn, 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.
Text conventions
The following conventions are used in the Motorola cellular infrastructure documents to
represent keyboard input text, screen output text and special key sequences.
68P09278A29-A
FEB 2007
General information
Input
Characters typed in at the keyboard are shown like this.
Output
Messages, prompts, file listings, directories, utilities, and environmental
variables that appear on the screen are shown like this.
Special key sequences

Special key sequences are represented as follows:
CTRL-c
Press the Control and c keys at the same time.
ALT-f
Press the Alt and f keys at the same time.
Press the pipe symbol key.
CR or RETURN
Press the Return key.
68P09278A29-A
FEB 2007
Contacting Motorola
Contacting Motorola
Motorola appreciates feedback from the users of our documents.
Errors
To report a documentation error, call the CNRC (Customer Network Resolution Center) and
provide the following information to enable CNRC to open an SR (Service Request):
The document type
The document title, part number, and revision character
The page number(s) with the error
A detailed description of the error and if possible the proposed solution
Questions and comments

Send questions and comments regarding user documentation to the email address below:
mydocs@motorola.com
24 hour support
If you have problems regarding the operation of your equipment, please contact the Customer
Network Resolution Center (CNRC) for immediate assistance. The 24 hour telephone numbers
are listed at https://mynetworksupport.motorola.com. Select Customer Network Resolution
Center contact information. For additional CNRC contact information, contact your Motorola
account representative.
68P09278A29-A
FEB 2007
Security Advice
Security Advice
Motorola systems and equipment provide congurable security parameters to be set by the
operator based on their particular operating environment. Motorola recommends setting and
using these parameters following industry recognized security practices. Security aspects
to be considered are protecting the condentiality, 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 specic recommendations regarding security practices,
however the implementation of these recommendations and nal responsibility for the security
of the system lies with the operator of the system.
Please contact the Customer Network Resolution Center (CNRC) for assistance. The 24 hour
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 Ofce.
68P09278A29-A
FEB 2007
Warnings and cautions
The following describes how warnings and cautions are used in this document and in all
documents of this Motorola document set.
Failure to comply with warnings

Observe all warnings during all phases of operation, installation and maintenance of the
equipment described in the Motorola documents. Failure to comply with these warnings,
or with specic warnings elsewhere in the Motorola documents, or on the equipment
itself, violates safety standards of design, manufacture and intended use of the
equipment. Motorola assumes no liability for the customers failure to comply with
these requirements.
Warnings
A denition and example follow below:
Denition of Warning
A warning is used to alert the reader to possible hazards that could cause loss of life, physical
injury, or ill health. This includes hazards introduced during maintenance, for example, the use
of adhesives and solvents, as well as those inherent in the equipment.
Example and format
Do not look directly into ber optic cables or data in/out connectors. Laser radiation
can come from either the data in/out connectors or unterminated ber optic cables
connected to data in/out connectors.
Cautions
Denition of Caution
A caution means that there is a possibility of damage to systems, software or individual items of
equipment within a system. However, this presents no danger to personnel.
68P09278A29-A
FEB 2007
Example and format
Do not use test equipment that is beyond its due calibration date; arrange for
calibration to be carried out.
Notes
Denition of Note
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.
Example and format
The UDR version number is congured at installation time by Motorola personnel

and is not accessible by the customer.
68P09278A29-A
FEB 2007
General Safety
General Safety
Ground the equipment

To minimize shock hazard, the equipment chassis and enclosure must be connected to an
electrical ground. If the equipment is supplied with a three-conductor ac power cable, the
power cable must be either plugged into an approved three-contact electrical outlet or used
with a three-contact to two-contact adapter. The three-contact to two-contact adapter must
have the grounding wire (green) rmly connected to an electrical ground (safety ground) at
the power outlet. The power jack and mating plug of the power cable must meet International
Electrotechnical Commission (IEC) safety standards.
Refer to Grounding Guideline for Cellular Radio Installations 68P81150E62.
Do not operate in an explosive atmosphere

Do not operate the equipment in the presence of ammable gases or fumes. Operation of any
electrical equipment in such an environment constitutes a denite safety hazard.
Keep away from live circuits

Operating personnel must:
not remove equipment covers. Only Factory Authorized Service Personnel or other
qualied maintenance personnel may remove equipment covers for internal subassembly,
or component replacement, or any internal adjustment.
not replace components with power cable connected. Under certain conditions, dangerous
voltages may exist even with the power cable removed.
always disconnect power and discharge circuits before touching them.
Do not service or adjust alone

Do not attempt internal service or adjustment, unless another person, capable of rendering rst
aid and resuscitation, is present.
68P09278A29-A
FEB 2007
General Safety
Use caution when exposing or handling the CRT

Breakage of the CathodeRay Tube (CRT) causes a high-velocity scattering of glass fragments
(implosion). To prevent CRT implosion, avoid rough handling or jarring of the equipment. Only
qualied maintenance personnel wearing approved safety mask and gloves should handle the
CRT.
Do not substitute parts or modify equipment

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

Warnings, such as the example below, precede potentially hazardous procedures throughout
this document. Instructions contained in the warnings must be followed. Employ all other safety
precautions necessary for the operation of the equipment in the operating environment.
Potentially hazardous voltages, capable of causing death, are present in this

equipment. Use extreme caution when handling, testing, and adjusting.
10
68P09278A29-A
FEB 2007
Devices sensitive to static
Devices sensitive to static
Certain metal oxide semiconductor (MOS) devices embody in their design a thin layer of
insulation that is susceptible to damage from electrostatic charge. Such a charge applied to the
leads of the device could cause irreparable damage.
These charges can be built up on nylon overalls, by friction, by pushing the hands into high
insulation packing material or by use of ungrounded soldering irons.
MOS devices are normally dispatched from the manufacturers with the leads short-circuited
together, for example, by metal foil eyelets, wire strapping, or by inserting the leads into
conductive plastic foam. Provided the leads are short-circuited it is safe to handle the device.
Special handling techniques

In the event of one of these devices having to be replaced, observe the following precautions
when handling the replacement:
Always wear a ground strap which must be connected to the electrostatic point on the
equipment.
Leave the short circuit on the leads until the last moment. It may be necessary to replace
the conductive foam by a piece of wire to enable the device to be tted.
Do not wear outer clothing made of nylon or similar man made material. A cotton overall
is preferable.
If possible work on an grounded metal surface or anti-static mat. Wipe insulated plastic
work surfaces with an anti-static cloth before starting the operation.
All metal tools should be used and when not in use they should be placed on an grounded
surface.
Take care when removing components connected to electrostatic sensitive devices. These
components may be providing protection to the device.
When mounted onto printed circuit boards (PCBs), MOS devices are normally less susceptible to
electrostatic damage. However PCBs should be handled with care, preferably by their edges
and not by their tracks and pins, they should be transferred directly from their packing to the
equipment (or the other way around) and never left exposed on the workbench.
68P09278A29-A
FEB 2007
11
Caring for the environment
Caring for the environment
The following information is provided to enable regulatory compliance with the European Union
(EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE) when using
Motorola Networks equipment in EU countries.
Disposal of Motorola Networks equipment in EU countries
Please do not dispose of Motorola Networks equipment in landll sites.

In the EU, Motorola Networks in conjunction with a recycling partner will ensure that equipment
is collected and recycled according to the requirements of EU environmental law.
Please contact the Customer Network Resolution Center (CNRC) for assistance. 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 Ofce.
Disposal of Motorola Networks equipment in non-EU countries

In non-EU countries, dispose of Motorola Networks equipment in accordance with national
and regional regulations.
12
68P09278A29-A
FEB 2007
Motorola document set
Motorola document set
The Motorola document sets provide the information needed to operate, install, and maintain
the Motorola equipment.
Ordering documents and CD-ROMs

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

A banner (oversized text on the bottom of the page, for example, PRELIMINARY UNDER
DEVELOPMENT) indicates that some information contained in the document is not yet approved
for general customer use.
68P09278A29-A
FEB 2007
13
Third Party Computer Software and Trademarks
Computer Software
The Motorola and 3rd Party supplied Software (SW) products described in this instruction
document may include 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 and other 3rd Party supplied SW certain exclusive rights for
copyrighted computer programs, including the exclusive right to copy or reproduce in any
form the copyrighted computer program. Accordingly, any copyrighted Motorola or other 3rd
Party supplied SW computer programs contained in the Motorola products described in this
instruction document may not be copied (reverse engineered) or reproduced in any manner
without the express written permission of Motorola or the 3rd Party SW supplier. 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 SW, except for the normal non-exclusive, royalty free
license to use that arises by operation of law in the sale of a product.
Vendor
Copyright
Apache Software Foundation
Copyright 2001, 2002, 2003, 2004 , 2004 All

Rights Reserved
Artesyn
Copyright All Rights Reserved
CMU *
Open Source Software Foundation *
Copyright 2000 All Rights Reserved
Open Source Tools / Utilities *
GNOME Project *
iodbc.org *
Megastep *
NIST *
openBSD *
openSSL *
Performance Technologies
Postgres *
Sun Microsystems Inc. *
Telelogic
QNX *
*= May contain purchased SW and Open Source SW which may be subject to a license fee.
14
68P09278A29-A
FEB 2007
Trademarks
Java Technology and/or J2ME: Java and all other Java-based marks are trademarks or
registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.
UNIX: UNIX is a registered trademark of The Open Group in the United States and other
countries.
68P09278A29-A
FEB 2007
15
16
68P09278A29-A
FEB 2007
Chapter
1
Call testing procedure
The purpose of the procedures in this chapter is to validate that all of the Control Switches (CS)
and Active Directory (AD) are fully functional.
The phones come with a 1X symbol on the display screen to show connection to
the 1X data network. When connected the 1X symbol becomes inverted that is the
symbol turns white on a black background.
Perform preventive maintenance during the maintenance window on the following schedule:
Before and after any software installation, upgrade, or update.
After any system outage.
If any test fails:
Make sure the phones are powered up and are registered with the PoC server. The phones
are registered for PoC when they display an inverted 1X on black background.
If the phones are powered up and have 1X coverage, but the tests are still failing, contact
the Motorola CNRC.
68P09278A29-A
FEB 2007
1-1
Troubleshooting
Troubleshooting
Follow the procedure given in Procedure 1-1 for troubleshooting the call testing.
Procedure 1-1 Troubleshooting for call testing
1-2
Turn on the phone. If the display does not display an inverted 1X, coverage
is not found. Go to step 2 and try again after ve minutes.
After the ve minute wait, turn on the phone. If the

display still does not display the inverted 1X coverage,
abort this procedure, log results and contact CNRC.
Go to step 3 if the inverted 1X is displayed and coverage is
found.
Try the pointtopoint call three times. If the call cannot be connected
any of the three times, turn the phone off and on and go to step 4.
If the call connected all three times, go to Procedure 1-2.
Try the pointtopoint call three times. If the call cannot be connected any
of the three times, abort this procedure, log results and contact CNRC.
68P09278A29-A
FEB 2007
PointtoPoint call test
PointtoPoint call test
Follow the procedure given in Procedure 1-2 for Point-to-Point (PTP) call testing.
Procedure 1-2
68P09278A29-A
PTP call testing procedure
Make a pointtopoint PoC call between two handsets that are both provisioned
to register to CS #1. Make sure the receiver responds and the call is veried
both ways.
Make a pointtopoint PoC call between two handsets that are both provisioned
to register to a different CS than used in step 1. Make sure the receiver
responds and the call is veried both ways.
Repeat step 2 until all CSs have been tested and veried that each CS has PTP
call processing capabilities.
Make a pointtopoint PoC call between two handsets that are provisioned to
register on CS1 and CS2. Make sure the receiver responds and the call is
veried both ways.
1-3
FEB 2007
Group call test
Group call test
Follow the procedure given in Procedure 1-3 for Group call test.
Procedure 1-3 Group call testing procedure

1
Make a group call between three handsets that are registered on CS#1.
Verify that oor control is properly negotiated between the three handsets.
Floor Control When two mobiles are in an active conversation, the

person who is talking, is said to have oor control. The mobiles that
are listening to the talker, shows listening. This is how they know
that the oor is being used. Then the oor is said to be open when no
one is talking and mobiles show that they are connected.
1-4
Make a group call between three handsets that are registered on a different CS
than used in step 1. Verify that oor control is properly negotiated between
the three handsets.
Repeat step 2 until all CSs have been tested and veried that each CS has group
call processing capabilities.
Make a group call between three handsets registered on CS1, CS2, and CS3.
Verify that oor control is properly negotiated between the three handsets.
68P09278A29-A
FEB 2007
Chapter
2
Checking the AD
The purpose of the procedures in this chapter is to validate that:
Only subscription provisioning data is mirrored.
The mobiles can register and that the registration state is not lost.
All registrations only go to the active CS and AD.
If any test fails:
are registered for PoC when they display an inverted 1X on black background.
If the phones are powered up and have 1X coverage but the tests are still failing, contact
the Motorola CNRC.
68P09278A29-A
FEB 2007
2-1
AD verication
AD verication
Follow the procedure given in Procedure 2-1 to perform the AD verication.
Procedure 2-1
1
AD verication
Verify that there are two mobiles provisioned to register on each CS to be tested.
CSn_1 rst phone provisioned on CSn
CSn_2 second phone provisioned on CSn
Example: In the procedure, these phones are referred to as:
CS1_1 rst phone provisioned on CS #1
CS1_2 second phone provisioned on CS #1
CS2_1 rst phone provisioned on CS #2
CS2_2 second phone provisioned on CS #2
Record the Mobile MDNs for the phones used for this test.
Login from the command line.

telnet <ip_address> <port_number>
An example of the command would be:
telnet 216.109.118.76 141
Open a telnet window for each PoC server.

Login into nmhost01 on each server via the zynx card, port 141.
This step ensures that the telnet sessions will NOT time out.
5
Login as swuser on each of the NMHOSTs.
In each AD and CS, enter the whlr mode by typing:

wms_con wms_pri
mode whlr
The nms_sync takes care of timer inconsistency.

Continued
2-2
68P09278A29-A
FEB 2007
Procedure 2-1
AD verication
AD verication (Continued)
While in whlr mode, type the following command in each AD and CS:
showuser {MDN}
where MDN is the phone number of the test
phones. For example: showuser 8475551234
Repeat this step for each subscriber used in this test (See step 1) CS1_1,
CS1_2, CS2_1 and CS2_2.
Verify:
The MDN has a SIP Contact Address in the form of an IP address. This
veries the mobile is registered with the server.
The Home HLR IP address corresponds to the serving CS to which the

phone is registered.
The test phones show that they are registered in their primary AD and
not registered in the secondary AD.
The test phones CS1_1 and CS1_2, which are assigned to CS1, show
as registered in CS1 and NOT CS2.
The test phones CS2_1 and CS2_2, which are assigned to CS2, show
as registered in CS2 and NOT CS1.
If phones show registered in their secondary AD or CS, this could

indicate that a failover has occurred and the phones registered with
the secondary to maintain service.
9
68P09278A29-A
Type quit in each of the telnet windows to exit mode whlr and return to the $
prompt.
2-3
FEB 2007
Verifying active processes
Verifying active processes
Follow the procedure given in Procedure 2-2 to verify the active processes.
Procedure 2-2 Verifying active processes

1
Enter the console by typing: wms_con wms_pri
Verify all processes are running by typing: showprocs.

Check the transition timestamp and look for any recent dates and times.
The transition time indicates that the process started at that time and could
indicate a failover occurred unless the processes were started or rebooted
manually.
If any processes are not running, contact Motorola CNRC.

3
2-4
Exit the console by typing: quit
68P09278A29-A
FEB 2007
Verify that the databases at the two active directories are synchronzied. The following
commands are to be executed at the server prompt.
/opt/WMS/rel/scripts/CallersProvisioned.sh
/opt/WMS/rel/scripts/CallersProvisioned.sh b
/opt/WMS/rel/scripts/CallersProvisioned.sh g
These numbers must be very close to each other across the two active directories.
68P09278A29-A
If they are a few numbers apart, it could be due to the commands being typed
into the active directories a few seconds apart.
If the difference is more than a few subscribers and the number is growing, this
could indicate the active directories are NOT synchronizing properly. Contact
Motorola CNRC.
2-5
FEB 2007
Verifying cluster status
Follow the procedure given in Procedure 2-3 to verify the cluster status.
Procedure 2-3 Verifying cluster status
2-6
On each NMHOST, type: clustat
Verify all services are in the started state and look at the transition time to
ensure that nothing has transitioned recently. If anything is not started or has
recently transitioned, call Motorola CNRC.
68P09278A29-A
FEB 2007
Verifying TL1
Verifying TL1
Follow the procedure given in Procedure 2-4 to verify the TL1.
Procedure 2-4 Verifying TL1
68P09278A29-A
On each NMHOST, login to TL1 by typing: wms_tl1 i wms_pri
Type swuser as the username and the swuser password.
If a TL1 prompt displays, the test passed. Type quit to exit TL1.
If the TL1 prompt did NOT display, call Motorola CNRC after verifying the
correct username and password were used. (Ensure you have the correct
passwords rst.)
2-7
FEB 2007
Checking disk space
Checking disk space
Follow the procedure given in Procedure 2-5 to check the disk space.
Procedure 2-5
Checking disk space
On each NMHOST, type: df h
Look at the output and record:
any partitions that exceed 70% in the spreadsheet. Contact Motorola

CNRC if there are any partitions over 70% for an unknown reason.
any partitions (except for /dev/shm) that show 0 for disk size. Contact
Motorola CNRC because this may be a stale le handle problem and needs
to be corrected by Motorola CNRC.
If this step hangs and does NOT display output, contact Motorola
CNRC.
2-8
68P09278A29-A
FEB 2007
Checking for core les
Follow the procedure given in Procedure 2-6 to check for the core les.
Procedure 2-6
68P09278A29-A
FEB 2007
On each NMHOST, check for core les using the following command:
find / name core print 2>/dev/null | xargs ls
alrt
All of the core les in the system are displayed and ordered oldest to newest.
Check the most recent core les and if any les are NOT already being analyzed,
notify the CNRC.
Contact Motorola CNRC if any new core les are found.
2-9
2-10
68P09278A29-A
FEB 2007
Chapter
3
Checking the CS
The purpose of the procedures in this chapter is to validate that:
CSs are performing correctly.
billing les are being created.
If any test fails:
are registered for PoC when they display an inverted 1X (1X on black background).
If the phones are powered up and have 1X coverage but the tests are still failing, contact
the Motorola CNRC.
68P09278A29-A
FEB 2007
3-1
Verifying billing le creation
Verifying billing le creation
Follow the procedure given in Procedure 3-1 to verify the billing le creation.
Procedure 3-1
1
Verify billing le creation
Login as swuser on each of the NMHOSTs running wms_nmh2 service.
Type clustat to determine NMHOST running wms_nmh2 service.

It is typically nmhost02.
3-2
Type ls arlt /cluster/amap

A time sorted list of the billing les is returned. Verify
the les at the bottom of the list have a date/time stamp very close to
the current date/time.
To exit, type exit.
68P09278A29-A
FEB 2007
Follow the procedure given in Procedure 3-2 to verify the cluster status.
Procedure 3-2
68P09278A29-A
On each NMHOST, type clustat.
Verify that all services are in the started state and look at the
transition time to ensure that nothing has transitioned recently.
If anything is not started or has recently transitioned, call Motorola CNRC.
3-3
FEB 2007
Verifying TL1
Verifying TL1
Follow the procedure given in Procedure 3-3 to verify the TL1.
Procedure 3-3 Verifying TL1
3-4
On each NMHOST, login to TL1 by typing wms_tl1 i wms_pri
Type swuser as the username and the swuser password.
If a TL1 prompt displays, the test passed. Type quit to exit TL1.
If the TL1 prompt did NOT display, call Motorola CNRC after verifying the
correct username and password were used. (Ensure you have the correct
passwords rst.)
68P09278A29-A
FEB 2007
Checking disk space
Checking disk space
Follow the procedure given in Procedure 3-4 to check the disk space.
Procedure 3-4
Checking disk space
On each NMHOST, type: df h
Look at the output and record:
any partitions that exceed 70% in the spreadsheet. Contact Motorola

CNRC if there are any partitions over 70% for an unknown reason.
any partitions (except for /dev/shm) that show 0 for disk size. Contact
Motorola CNRC because this may be a stale le handle problem and needs
to be corrected by Motorola CNRC.
If this step hangs and does NOT display output, contact Motorola
CNRC.
68P09278A29-A
3-5
FEB 2007
Follow the procedure given in Procedure 3-5 to check for core les.
Procedure 3-5 Checking for core les
3-6
On each NMHOST, check for core les using the following command:
find / name core print 2>/dev/null | xargs ls
alrt
All of the core les in the system are displayed and ordered oldest to newest.
Check the most recent core les and if any les are NOT already being analyzed,
notify the CNRC.
Contact Motorola CNRC if any new core les are found.
68P09278A29-A
FEB 2007
Chapter
4
Checking call statistics, alarms, and process
utilization
Follow the procedure given in Procedure 4-1 for checking the statistics, alarms and process
utilization.
Procedure 4-1 Checking call statistics, alarms, and process utilization

1
Login from the EMS GUI.

1.
Start up a browser window for each PoC Platform, connecting to the

nmhost shared IP address for each.
2.
Login as swuser. The EMS GUI displays.
Call Stats Perform only for CS.
Call stats are available for the CSs only, there are no call statistics
for the AD.
1.
On the menu on the left side of the browser, select REPORTS > CALL
STATS.
2.
Verify that the call volume is at an acceptable level.
The call stats are continuously refreshed which keeps the

connection active. The WEB GUI has a timer expiration that
automatically logs out if the session is idle for too long.
Continued
68P09278A29-A
FEB 2007
4-1
Chapter 4: Checking call statistics, alarms, and process utilization
Procedure 4-1
3
Checking call statistics, alarms, and process utilization (Continued)
Alarms Perform this step for all ADs and CSs.

1.
On the menu on the left side of the browser, select

OPERATIONS>ALARMS. The alarms screen displays.
2.
Look for any alarms with a recent timestamp. If there are any new,
uncleared critical or major alarms, contact the Motorola CNRC. Click the
alarm to see more detail on the alarm.
Process utilization Perform this step for all ADs and CSs.
1.
On the menu on the left side of the browser, select under

CONFIGURATION>CHASSIS SETUP
2.
Click PROCESSES. There is a column for the memory utilization

percentage and the CPU utilization percentage.
It is difcult to say what numbers are normal because the

average percentages are highly dependant on the trafc load
of the system being monitored. If any numbers that are very
high (over 80%), call CNRC unless the amount is typical for the
system being monitored.
4-2
68P09278A29-A
FEB 2007
Appendix
Preventative maintenance checklists for PoC

This procedure can be run to determine system health at any time and does not require a
maintenance window.
It is recommended that this checklist be laminated and all entries and checks be entered using a
weterase ne point marker.
Refer to Preventative Maintenance Procedures/Checklist for detailed information.
Table A-1 Checklist for call testing

Procedures
Pass/Fail
Date
Performed
Next
Scheduled
Date
Pass/Fail
Date
Performed
Next
Scheduled
Date
PointtoPoint Call
Verify that the receiver responds and the

call is veried between two handsets on the
same CS.
Verify that the receiver responds and the call

is veried between two handsets on different
CSs.
Verify point to point call response on all CSs.
Group Call
Verify that the oor control is properly

negotiated between three handsets on the
same CS.
Verify that the oor control is properly

negotiated between three handsets on
different CSs.
Table A-2
Checklist for checking the AD

Procedures
AD Verication
Verify that the MDN has a SIP Contact

Address in the form of an IP address.
Verify that the Home HLR IP address

corresponds to the serving CS to which the
phone is registered.
68P09278A29-A
FEB 2007
A-1
Appendix A: Preventative maintenance checklists for PoC
Table A-2 Checklist for checking the AD (Continued)

Procedures
Pass/Fail
Date
Performed
Next
Scheduled
Date
Verifying Active Processes

Verify that all processes are running.
Verifying Cluster Status on AD
Verify all services are in the started state and look
at the transition time to ensure that nothing has
transitioned recently. If anything is not started or
has recently transitioned, call Motorola CNRC.
Verifying TL1 on AD
Verify TL1 prompt displayed, if not call
Motorola CNRC.
Checking Disk Space
Check for partitions that exceed 70%, contact

Motorola CNRC if found.
Check for partitions that show 0 for disk size,

contact Motorola CNRC if found.
Checking for Core Files on AD

Check for new or recent core les, if found
contact CNRC.
Verifying Billing File Creation
Verify that the les at the bottom of the list
have a date/time stamp very close to the
current date/time.
Verifying Cluster Status on CS
Verify all services are in the started state and look
at the transition time to ensure that nothing has
transitioned recently. If anything is not started or
has recently transitioned, call Motorola CNRC.
Verifying TL1 on CS
Verify TL1 prompt displayed, if not call
Motorola CNRC.
A-2
68P09278A29-A
FEB 2007
Table A-2 Checklist for checking the AD (Continued)

Procedures
Pass/Fail
Date
Performed
Next
Scheduled
Date
Checking Disk Space
Check for partitions that exceed 70%, contact

Motorola CNRC if found.
Check for partitions that show 0 for disk size,

contact Motorola CNRC if found.
Table A-3
Checklist for checking call statistics, alarms and process utilization

Procedures
Pass/Fail
Date
Performed
Next
Scheduled
Date
Verify that the call volume is at an acceptable

level.
68P09278A29-A
FEB 2007
A-3
A-4
68P09278A29-A
FEB 2007
Appendix
Acronyms and abbreviations

The following acronyms and abbreviations are used in this manual.
AD
Active Directory
CNRC
Cellular Network Resolution Center
CS
Control Switch
HLR
Home Location Register
IP
Internet Protocol
MDN
Mobile Directory Number
MIN
Mobile Identication Number
PoC
PushtoTalk over Cellular
PTP
Point to Point
PTT
PushtoTalk
SIP
Session Initiation Protocol
TL1
Transaction Language 1
VPN
Virtual Private Network
68P09278A29-A
FEB 2007
B-1
B-2
68P09278A29-A
FEB 2007
*68P09278A29-A*
68P09278A29-A
Technical
Information
POC PREVENTATIVE MAINTENANCE PROCEDURES

AND CHECKLISTS
SOFTWARE RELEASE 6.1.X.X
POC
US/HONG KONG, ROW
ENGLISH
FEB 2007
68P09278A29-A
POC PREVENTATIVE MAINTENANCE PROCEDURES

AND CHECKLISTS
SOFTWARE RELEASE 6.1.X.X
POC
US/HONG KONG, ROW
ENGLISH
FEB 2007
68P09278A29-A
Standard Printing Instructions

Part Number
68P09278A29-A
Manual Title
Date
FEB 2007
CSD/CND (US)
Binder
Printing
Finishing
3 Slant D-ring binder - letter size (11.75 in x 11.5 in) white PVC.
Capacity depends on size of document. (no larger than 3 in).
Clear pockets on front and spine.
Cover / spine text overprinted onto Motorola cover stock.
Body- printed double sided onto white letter size (8.5 in x 11 in) 70 lb.
Shrink wrap contents.
CMM labeling and disclosure table

The Peoples Republic of China requires that Motorolas 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 that 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, fifty years in the example shown.
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.
2007 Motorola, Inc.
68P02901W00-E

Preventative 68p09278a29

Uploaded by

Copyright:

Available Formats

Preventative 68p09278a29

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Preventative 68p09278a29

Uploaded by

Copyright:

Available Formats

PoC Preventative Maintenance Procedures

PoC Preventative Maintenance Procedures and Checklists

Chapter 1: Call testing procedure

Chapter 2: Checking the AD

Chapter 3: Checking the CS

Chapter 4: Checking call statistics, alarms, and process utilization

PoC Preventative Maintenance Procedures

What is covered in this manual?

Failure to comply with Motorolas operation, installation and maintenance instructions

Special key sequences

Press the Control and c keys at the same time.

Press the Alt and f keys at the same time.

Press the pipe symbol key.

Press the Return key.

Motorola appreciates feedback from the users of our documents.

The document type

The document title, part number, and revision character

The page number(s) with the error

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

Questions and comments

Warnings and cautions

Warnings and cautions

Failure to comply with warnings

Example and format

Warnings and cautions

Example and format

Example and format

The UDR version number is congured at installation time by Motorola personnel

Ground the equipment

Refer to Grounding Guideline for Cellular Radio Installations 68P81150E62.

Do not operate in an explosive atmosphere

Keep away from live circuits

always disconnect power and discharge circuits before touching them.

Do not service or adjust alone

Use caution when exposing or handling the CRT

Do not substitute parts or modify equipment

Potentially hazardous procedure warnings

Potentially hazardous voltages, capable of causing death, are present in this

Devices sensitive to static

Devices sensitive to static

Special handling techniques

Caring for the environment

Caring for the environment

Disposal of Motorola Networks equipment in EU countries

Please do not dispose of Motorola Networks equipment in landll sites.

Disposal of Motorola Networks equipment in non-EU countries

Motorola document set

Motorola document set

Ordering documents and CD-ROMs

Document banner denitions

Third Party Computer Software and Trademarks

Third Party Computer Software and Trademarks

Apache Software Foundation

Copyright 2001, 2002, 2003, 2004 , 2004 All

Copyright All Rights Reserved

Copyright All Rights Reserved

Open Source Software Foundation *

Copyright 2000 All Rights Reserved

Open Source Tools / Utilities *

Copyright All Rights Reserved