TL1 Command 68p09278a34

PoC TL1 Command Reference Guide
68P09278A34-A
2003, 2004-2007 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

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 . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2
2
3
3
4
4
5
5
5
5
6
7
7
7
8
8
9
9
9
9
9
10
10
10
11
11
12
12
12
13
13
13
14
14
15
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-2
1-2
1-6
1-8
Chapter 1: Introduction
What is the TL1 command interpreter?
TL1 command input / output format
Standard Log in and Log out . . . .
MO server log in and log out . . . . . .
68P09278A34-A
FEB 2007
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Contents
Log in . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TL1 console security module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-8
1-9
Chapter 2: TL1 commands

Application / equipment maintenance . . . . . .
BOOT-card . . . . . . . . . . . . . . . . . .
EJCT-card . . . . . . . . . . . . . . . . . .
KIL-app . . . . . . . . . . . . . . . . . . .
SET-LOCALLOG . . . . . . . . . . . . . . .
SET-LOGLEVEL . . . . . . . . . . . . . . .
STA-app . . . . . . . . . . . . . . . . . . .
STA-LVL . . . . . . . . . . . . . . . . . . .
STP-app . . . . . . . . . . . . . . . . . . .
STP-LVL . . . . . . . . . . . . . . . . . . .
Maintenance Call Processing . . . . . . . . .
SHOW-app_ccsw-SWSTATE . . . . . . . . .
Maintenance CACIM . . . . . . . . . . . . .
SHOW-app_cacim-CALLTYPES . . . . . . . .
SHOW-app_cacim-CONFIG . . . . . . . . .
SHOW-app_cacim-CSMSTATE . . . . . . . .
SHOW-app_cacim-STATE . . . . . . . . . .
Maintenance Billing . . . . . . . . . . . . . .
SHOW-app_cdrcp-CONFIG. . . . . . . . . .
SHOW-app_cdrcp-CSMSTATE . . . . . . . .
SHOW-app_cdrcp-DISKSTATE . . . . . . . .
SHOW-app_cdrcp-SWSTATE . . . . . . . . .
Maintenance General . . . . . . . . . . . . .
ALW-MSG . . . . . . . . . . . . . . . . . .
INH-MSG . . . . . . . . . . . . . . . . . .
RTRV-EDPROVTYPES . . . . . . . . . . . .
RTRV-ENTERPRISE_SUBS . . . . . . . . . .
RTRV-ENTERPRISE_SUBS_COUNT . . . . .
RTRV-<MO_Type> . . . . . . . . . . . . . .
RTRV-<MO_Type>::<0>:<C_Tag> . . . . .
RTRV-<MO_Type>-UPDATEATTRS . . . . .
RTRV-<MO_Type>-ATTRS . . . . . . . . . .
RTRV-<MO_Type>-VALS. . . . . . . . . . .
RTRV-<MO_Type>-CREATEATTRS . . . . .
RTRV-<MO_Type>-INST . . . . . . . . . . .
RTRV-<MO_Type>::<MO_Instance> . . . .
RTRV-<MO_Type>::<Prex>:<C_Tag> . . .
RTRV-<MO_Type>-REFS . . . . . . . . . .
RTRV-<MO_Type>-REL . . . . . . . . . . .
RTRV-<MO_Type>-RELMO . . . . . . . . .
RTRV-<MO_Type>::<Sid>:<C_Tag> . . . .
RTRV-<switch>::WMS::C1:<MO_Instance> .
RTRV-PROVTYPES . . . . . . . . . . . . . .
RTRV-SEC . . . . . . . . . . . . . . . . . .
RTRV-TYPES . . . . . . . . . . . . . . . . .
RTRV-VERBS. . . . . . . . . . . . . . . . .
General IPMH . . . . . . . . . . . . . . . .
SHOW-CONS . . . . . . . . . . . . . . . .
General Media resource platform . . . . . . .
SHOW-app_mrp-AUEP . . . . . . . . . . . .
SHOW-app_mrp-STATS . . . . . . . . . . .
General Log Details . . . . . . . . . . . . . .
SHOW-LOGDETAILS:ADHLR01 . . . . . . .
ii
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-2
2-2
2-3
2-4
2-5
2-5
2-6
2-7
2-9
2-10
2-12
2-12
2-14
2-14
2-15
2-16
2-17
2-19
2-19
2-20
2-21
2-22
2-24
2-24
2-25
2-25
2-27
2-29
2-30
2-32
2-33
2-34
2-36
2-38
2-39
2-40
2-42
2-43
2-45
2-47
2-49
2-50
2-56
2-59
2-60
2-63
2-65
2-65
2-67
2-67
2-68
2-70
2-70
68P09278A34-A
FEB 2007
Contents
SHOW-LOGDETAILS:BILLNBI01
SHOW-LOGDETAILS:CACIM. . .
SHOW-LOGDETAILS:CCSW . . .
SHOW-LOGDETAILS:CDRCP . .
SHOW-LOGDETAILS:IPMH . . .
SHOW-LOGDETAILS:LOGCM . .
SHOW-LOGDETAILS:LOG_TL1 .
SHOW-LOGDETAILS:MRP . . . .
SHOW-LOGDETAILS:MTAS . . .
SHOW-LOGDETAILS:ADGCR . .
SHOW-LOGDETAILS:SYNC . . .
TXN-ABORT . . . . . . . . . . .
TXN-BEGIN . . . . . . . . . . .
TXN-END . . . . . . . . . . . .
Provisioning . . . . . . . . . . . . .
CRTE . . . . . . . . . . . . . .
DLT . . . . . . . . . . . . . . .
ED-<MO_Type> . . . . . . . . .
Security . . . . . . . . . . . . . . .
ACT-USER . . . . . . . . . . . .
CANC-USER . . . . . . . . . . .
ED-user . . . . . . . . . . . . .
68P09278A34-A
FEB 2007
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
2-71
2-72
2-72
2-73
2-74
2-74
2-75
2-76
2-76
2-77
2-78
2-78
2-79
2-79
2-80
2-80
2-81
2-82
2-85
2-85
2-85
2-86
iii
Contents
iv
68P09278A34-A
FEB 2007
List
of
Tables
List of Tables
Table
Table
Table
Table
Table
1-1:
1-2:
1-3:
1-4:
1-5:
TL1 command syntax . . . . . . .

TL1 command / verbs . . . . . . .
TL1 command output syntax . . .
TL1 command error output syntax
Default login IDs . . . . . . . . .
68P09278A34-A
FEB 2007
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1-3
1-4
1-5
1-6
1-8
List of Tables
vi
68P09278A34-A
FEB 2007
About
This
Manual
This manual is intended for use by cellular telephone system craftspersons in the day-to-day
operation of Motorola cellular system equipment and ancillary devices. This manual is not
intended to replace the system and equipment training offered by Motorola, although it can be
used to supplement or enhance the knowledge gained through such training.
This manual is a reference guide for the operators to understand the TL1 command line
interface (CLI) using which the operators can congure, provision, modify PoC switch
components or view the switch and call statistics.
68P09278A34-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
FEB 2007
Remarks
68P09278A34-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.
68P09278A34-A
FEB 2007
General information
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.
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.
68P09278A34-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.
68P09278A34-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.
68P09278A34-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.
68P09278A34-A
FEB 2007
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.
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.
68P09278A34-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.
68P09278A34-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
68P09278A34-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.
68P09278A34-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
68P09278A34-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.
68P09278A34-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
68P09278A34-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.
68P09278A34-A
FEB 2007
15
16
68P09278A34-A
FEB 2007
Chapter
1
Introduction
The Transaction Language (TL1) Console process is an industry-standard command line

interface that lets congure the PoC in the network, provision services, and manage and monitor
PoC operations. The TL1 Console permits multi-user access, with no practical limit to the
number of users permitted. It lets to add, view, and delete database objects, view and modify
the conguration parameters, and view the statistics and alarms.
68P09278A34-A
FEB 2007
1-1
TL1 is a command line interface provided as an alternative to the EMS browser (GUI) for
the provisioning and management of mobile services provided by the PoC. Its dominance as
a standards-based telecommunications protocol provides a low-cost alternative to operator
training. It can be used to create scripts to further reduce the cost of conguring and managing
elements.
TL1 command input / output format

The following general statements apply to this guide:
In this guide, the longer command lines can be printed on two or more lines, because
of limitations in the display of type. However, when they are entered at the terminal,
command lines must be one line only.
The uppercase command characters displayed in this guide are case sensitive, which
means they can be entered at the terminal in uppercase letters only.
Angled brackets (< >) indicate that the enclosed text describe part of the command.
Brackets [ ] are used to indicate optional parameters within each TL1 command.
TL1 command lines are comprised of a series of blocks, separated by colons (:) as block
delimiters. The blocks must be entered in a specic order. If a block is not mandatory, its
contents be omitted. However, the colon delimiters must still be entered.
Double colons (::) following a C_Tag, indicate parameters.
1-2
Following these blocks, there be zero to many parameters, separated by commas (,) as
delimiters.
A semi-colon (;) is always used as the nal character that executes a command. The
semi-colon also serves as a prompt which appears at the end of the command to indicate
that the system is ready for the next command.
68P09278A34-A
FEB 2007
Input commands
An input command communicates a specic action that is executed at the network element. The
TL1 input command line consists of the following:
Table 1-1 TL1 command syntax

Parameter
Description
Directive
Specic TL1 Command.
MO_Type
MO_Type be any of the managed object (MO) types supported by this

command.
MO_Instance
MO_Instance identies the object to create / modify / delete.
C_Tag
C_Tag is a correlation tag to be returned in the system response to this

request. Its purpose is to prevent confusion between requests issued
to the system and the responses to those requests. It must be a string
consisting of 1 6 characters or decimal numbers.
Parameters
Parameters species command information necessary for input

command and output responses. For the TL1, some parameter
values be optional depending on the specic TL1 command.
The parameter values are case sensitive. Surround
the strings with double quotes if they contain any
special characters such as a space, a dash, or a colon.
Periods and single quotes do not qualify as special characters

in TL1, so do not need to use double quotes to surround strings
containing them.
< >
Indicates that the parameter/verb to be included in the command.
Block delimiter. Must be entered between parameters and verbs.
Indicates the end of a command and that the system is ready for the
next command.
Tab
Tab key to list the instances of the specied managed object type.
Tab completion
Type any part of a command and press the Tab key to display all elements at the next object
layer supported by the command element typed. The TL1 console does one of the following:
Appends an element to the command if it is the only one supported by the command string
typed.
Lists the elements supported by the command string typed, and repeats the command
string after the WMS_TL1> prompt.
68P09278A34-A
1-3
FEB 2007
Verbs
Enter the following command to display all of the verbs available on the TL1 Console.
Alternatively, list the verbs using the command RTRV-TYPES on page 2-60.
WMS-TL1>
Help:
Verb - The action to be taken.
ACT
BLK
CRTE
EJCT
REACT
SET
STAT
ALW
BOOT
DLT
INH
RESET
SHOW
STP
APP
CANC
ED
KIL
RTRV
STA
TEST
TXN
UBLK
UINH
WMS-TL1>
The following table describes verbs used in the TL1 commands supported in this document.
Table 1-2
TL1 command / verbs
Verb
Function
ACT
Establishes a user session by logging using the provided user name.
ALW
Begin receiving autonomous messages from the server.
APP
Application or process instance.
BLK
Blocking a circuit allows existing user trafc to proceed, but prevents the
allocation of all subsequent user trafc and automatic continuity repeat
testing.
BOOT
Resets a card or EMS Server.
CANC
Cancels a TL1 or EMS browser session by user name.
CRTE
Creates a Managed Object.
DLT
Delete a Managed Object.
ED
Modies a Managed Objects attribute value.
EJCT
Prepares a card for removal from the PoC chassis.
INH
Inhibits a link / stop receiving autonomous messages from the server.
KIL
Kills a specied application / call.
REACT
Edits the users password or activates the user.
RESET
Resets aggregate call statistics / circuits available to be reassigned to

incoming and outgoing calls.
RTRV
Displays all of the attributes and values of a managed object type.
SET
Sets the local log / log level for a particular entity.
SHOW
Displays all of the provisioned subscribers / number of calls / call statistics.
STA
Start a specied process / application.
Continued
1-4
68P09278A34-A
FEB 2007
Table 1-2
TL1 command / verbs (Continued)
Verb
Function
STAT
Display the status of the signal ports / routes / links.
STP
Shuts down a process / application.
TEST
Queries the remote circuit provisioning data.
TXN
Aborts / Begins / Ends a transaction.
UBLK
Unblocks previously blocked circuit.
UINH
Uninhibits a link / receiving autonomous messages from the server.
Output messages
A normal output message informs the user that the action specied in the input command was
completed successfully and supplies any additional, required information.
Proper system response to a successful completion of a command is according to the following
format:
<WMS> <DATE>
<TIME>
M <C_Tag> COMPLD
;
where
Table 1-3 TL1 command output syntax

Parameter
Description
WMS
System Identier. Identies the system.
DATE
Date. Species the system date, which appears in the YYYY-MM-DD

format.
TIME
Time. Species the system time, which is the time in GMT format
(HH-MM-SS).
This indicates the output message is generated in response to a manual

command.
C_Tag

COMPLD
This indicates that the command has been completed.
Indicates the end of a command and that the system is ready for the
next command.
A response showing the correlation tag and the text COMPLD indicates the MO Server received
the request and passed it to the process associated with the command.
68P09278A34-A
1-5
FEB 2007
Error messages
An error response message occurs in response to an input command describing why the
command cannot be executed. It indicates abnormal (error) conditions within the system that
prevent the command action from successfully executing. An incorrectly entered command
can also generate an error message.
Error response messages are according to the following format:
<WMS>
M
<DATE>
<TIME>
<C_Tag> DENY
[Message Code]
/*[Error_Info]*/
;
Table 1-4 TL1 command error output syntax

Parameter
Description
WMS
System Identier. Identies the system.
DATE
Date. Species the system date, which appears in the YYYY-MM-DD

format.
TIME
Time. Species the system time, which is the time in GMT format
(HH-MM-SS).
This indicates the output message is generated in response to a manual

command.
C_Tag

DENY
Indicates that the command has not been correctly entered/executed.
Message Code
Error message code.
Error_info
An explanatory sentence that points to the reason for failure.
Standard Log in and Log out

The PoC TL1 login procedure provides access to tab completion where as the Managed Object
(MO) Server does not. Therefore, follow the standard TL1 login procedure for routine use and
follow the MO Server login procedure only if the PoC TL1 process is unavailable.
1-6
68P09278A34-A
FEB 2007
Log In
Refer to the following instructions to log in and out of a TL1 process.
Procedure 1-1 Log in procedure
Enter the following command to initiate a Telnet session with one of the EMS
Servers. telnet <IP_Address> <Port>
IP_Address is the virtual IP address of the public VLAN congured to

provide access to the Ethernet cards inserted in the chassis.
Port is 141 to access EMS Server 1 or 142 to access EMS Server 2

via the IP address above.
For example, telnet 10.1.27.101 142

2
Enter the following command after the shell prompt

to login to the TL1 Console:wms_tl1 -i <IP_Address>
IP_Address is the IP address of the EMS Server running the MO Server
process.
No need to specify an IP address if already logged in to the EMS

server.
3
Type a username and password after the prompt.

Refer Table 1-5 for the default login settings or obtain them
from administrator. The WMS-TL1> prompt appears. For example,
bash# wms_tl1
Connected to: localhost,2361
login: swuser
password: *********
WMS-TL1>
Log out
Procedure 1-2 Log out
Enter exit or quit after the WMS-TL1> prompt to close a session with the TL1
Console. The shell prompt appears. For example,
WMS-TL1> quit
bash#
68P09278A34-A
1-7
FEB 2007
MO server log in and log out
Refer to the following instructions to establish a Telnet session to an MO Server and log in and
out if the PoC TL1 is unavailable to the client. Alternatively, insert these commands in a script
or use them to connect a third- party TL1 interface to the PoC.
Log in
Establish a Telnet session with an MO Server and log in to access the TL1 interface to the
MO Server as follows:
Procedure 1-3 MO server log in
Enter the following command to initiate a

Telnet session with one of the EMS Servers.
telnet <IP_Address> <Port>
IP_Address is the virtual IP address of the public VLAN congured to

provide access to the Ethernet cards inserted in the chassis.
Port is 141 to access EMS Server 1 or 142 to access

EMS Server 2 via the IP address above. For example,
telnet 10.1.27.101 142
Enter the following command to access the TL1 interface:

ACT-USER::<User_Name>::C1::<Password>;
For User_Name and Password, refer the following table for the default logging settings or obtain
them from administrator.
Table 1-5 Default login IDs

Item
Description
swuser
wmspasswd
swadmin
wmspasswd
For example, ACT-USER::swuser::C1::wmspasswd;
WMS
M
1-8
02-10-04 12:55:16
C1 COMPLD
68P09278A34-A
FEB 2007
Log out
Enter the following command to log out of a TL1 interface to the MO Server:
CANC-USER::<User_Name>:<C_Tag>::;
User_Name is the user name associated with any open EMS browser or TL1 Console session.
C_Tag is a correlation tag to be returned in the system response to this request. Its purpose
is to prevent confusion between requests issued to the system and the responses to them. It
must be a string consisting of 1 6 characters or decimal numbers. For all PoC TL1 commands,
press the Tab key once to insert the preceding colon and again to insert a system generated
correlation tag and follow-on colon.
For example,
CANC-USER::swuser:C2::;
WMS
M
02-10-04 12:55:24
C2 COMPLD;
Connection closed by foreign host.
TL1 console security module

Console security module is used in the EMS browser or TL1 Console to create, view, or modify
user security templates or individual proles. The names of the options in the Security Module
descriptions are as they appear in the EMS browser windows.
68P09278A34-A
1-9
FEB 2007
Permitted values of the options are shown in the Security Module descriptions in PoC Operations
Guide.
1-10
USER_CONTROL
ALARM_LIST
ANNOUNCEMENTS
APP_PROVISIONING
CALEA
CTC
DIALPLAN
ENTERPRISE
HARDWARE
IMS_IFC
IMS_PARAMS
IP_PEERS
LIMITED_MOBILITY
LOCAL_SWITCH
MEDIA_GATEWAYS
OAMP
PERFORMANCE
PREDICATES
ROAMING
ROUTING
SERVICES
SIGNALLING_LINKS
SS7_PORTS
STANDARD_HLR
SUBSCRIBERS
SWITCHES_BSC
TIMER_PROFILES
WHOLESALE
68P09278A34-A
FEB 2007
Chapter
2
TL1 commands
The following TL1 commands are supported by PoC network elements, and are categorized
into functional categories as below:
Application / equipment maintenance
Maintenance / general
Provisioning
Security
68P09278A34-A
FEB 2007
2-1
BOOT-card
Input format
The format for the BOOT command with all options is:
BOOT-card::<Card_Name>:<C_Tag>::;
Description
This command resets a card or EMS Server.
Card_Name is the value of the card_name attribute of the managed object type card. It identies
a card on the Control Switch. Type the BOOT-card:: portion of the command and press the Tab
key to list the names of the cards before completing the remainder of the command.
C_Tag is a correlation tag to be returned in the system response to this request. Its purpose is to
prevent confusion between requests issued to the system and the responses to those requests.
It must be a string consisting of 16 characters or decimal numbers.
The PoC performs a graceful shutdown of all applications running on the card. As the
applications shut down, backup applications on other cards go into active mode to handle
the processing load. Similarly, the applications running on other cards that are congured
to operate in a load sharing mode assume the processing share of the applications that are
shutting down. The PoC reloads the boot diagnostics and runs them on the card, reloads the
operating system software, restarts the Card Element Manager (CEM), and uses DHCP to
reassign the IP address to the card.
Example input / output

WMS-TL1> BOOT-card::ADHOST01:C13::;
WMS-TL1>
WMS
M
02-10-04 12:35:58
C13 COMPLD
;
WMS-TL1>
2-2
68P09278A34-A
FEB 2007
EJCT-card
Input format
The format for the EJCT-card command with all options is:
EJCT-card::<Card_Name>:<C_Tag>::;
Description
Card_Name is the name of the card to be removed. Type EJCT-card:: and press the Tab key to
list the card names.
The HS LED above the button near the bottom ejector turns blue to indicate the shutdown is
complete. Remove or replace the card at this time.
For more information on instructions, refer to PoC Hardware Installation Guide .

Enter the TL1 Console EJCT-card command as an alternative to pressing the button on the lever
of a card to perform a graceful shutdown of all applications on the card. As the applications
shut down, backup applications on other cards go into active mode to handle the processing
load. Similarly, the applications running on other cards that are congured to operate in a load
sharing mode assume the processing share of the applications that area shutting down.

For example, enter the following TL1 Console command to prepare a card for removal from
the PoC chassis.
WMS-TL1> EJCT-card::ADHOST01:C14::;
WMS-TL1>
WMS
M
02-10-04 12:36:17
C14 COMPLD
;
WMS-TL1>
68P09278A34-A
2-3
FEB 2007
KIL-app
Input format
The format for the KIL-app command with all options is:
KIL-app::<Process_Name>:<C_Tag>::;
Description
Process_Name is the name of a core process running on an EMS Server or the chassis. Type
KIL-app:: and press the Tab key to list the processes. For example,
WMS-TL1> KIL-app::
Help:
Access Id - Identities the entity within the target.
ADHLR01
ADHLR11
IPMH01
IPMH11
LOGCM01
WMS-TL1>
A response containing the text SUCC indicates the action requested was successful.

WMS-TL1> KIL-app::ADHLR11:C5::;
WMS-TL1>
IP C5
>
WMS-TL1>
FTS
M
03-03-23 17:28:15
C5 COMPLD
SUCC
/*FTS received kill command.*/
;
WMS-TL1>
2-4
68P09278A34-A
FEB 2007
SET-LOCALLOG
Input format
The format for the SET-LOCALLOG command to start a specied process is:
STA-LOCALLOG::<APP_NAME>::<C_Tag>::locallog=<Value>;
Description
APP_Name is the name of a core process congured to run on an EMS Server or the chassis. For
example,
WMS-TL1> SET_LOCALLOG:
Help:
Target Id - A unique identifier of the element to be operated on.
ADHLR01
BILLNBI01
CCSW01
CDRCP01
LOGCM01
MRP01
CACIM01
CCSW11
IPMH01
LOGTL1
MRP02
MRP03
ADHLR02
WMS-TL1>

WMS-TL1> SET-LOCALLOG:ADHLR01::C8::locallog=true;
WMS-TL1>
IP C8
>
WMS-TL1>
ADHLR01
M
04-12-31 11:41:09
C8 COMPLD
Loglevel=3,
LocalLog=true,
;
WMS-TL1>
SET-LOGLEVEL
Input format
The format for the SET-LOGLEVEL command to start a specied process is:
SET-LOGLEVEL::<APP_NAME>::<C_Tag>::loglevel=<Value>;
68P09278A34-A
2-5
FEB 2007
Description
APP_Name is the name of a core process congured to run on an EMS Server or the chassis. For
example,
WMS-TL1> SET_LOGLEVEL:
Help:
Target Id - A unique identifier of the element to be
operated on.
ADHLR01
BILLNBI01
MRP01
MRP03
ADHLR02
CACIM01
CCSW01
CDRCP01
LOGCM01
CCSW11
IPMH01
LOGTL1
MRP02

WMS-TL1> SET-LOGLEVEL:ADHLR01::C8::loglevel=3;
WMS-TL1>
IP C8
>
WMS-TL1>
ADHLR01
04-12-31 11:41:09
M C8 COMPLD
Loglevel=3,
LocalLog=true,
;
WMS-TL1>
STA-app
Input format
The format for the STA-app command to start a specied process is:
STA-app::<Process_Name>:<C_Tag>::;
2-6
68P09278A34-A
FEB 2007
Description
Process_Name is the name of a core process congured to run on an EMS Server or the chassis.
Type STA-app:: and press the Tab key to list them. For example,
WMS-TL1> STA-app::
Help:
ADHLR01
BILLNBI01 CCSW11
IPMH01
LOGCM01
ADHLR11
CDRCP01 IPMH02
MRP02
ADGCR11
CCSW01
MRP01
WMS-TL1>
A response containing the text SUCC indicates the action requested was successful.

WMS-TL1> STA-app::CDRCP01:C6::;
WMS-TL1>
IP C6
>
WMS-TL1>
FTS
M
03-03-23 17:35:12
C6 COMPLD
SUCC
/*FTS received start command.*/
;
WMS-TL1>
STA-LVL
Input format
The format for the STA-LVL command to request an orderly startup of all processes ascending to
the run level specied is:
STA-LVL::<Run_Level>:<C_Tag>::;
68P09278A34-A
2-7
FEB 2007
Description
Run_Level is any integer assigned as a run level to a process. The PoC performs
an orderly startup of the processes in ascending order to the level specied. Type
the highest run level assigned to a process to start up all processes. Enter the
RTRV-app:::C15::app_name,run_level; command to view the run level assignments. For
example,
WMS-TL1> RTRV-app:::C15::app_name,run_level;
WMS-TL1>
WMS 03-04-14 23:03:25
M C2 COMPLD
app_name=LOGCM01,
run_level=0,
app_name=IPMH01,
run_level=3,
app_name=IPMH02,
run_level=0,
app_name=CDRCP01,
run_level=0,
app_name=CCSW01,
run_level=0,
app_name=CCSW11,
run_level=0,
app_name=ADHLR01,
run_level=2,
app_name=ADHLR11,
run_level=2,
app_name=MRP01,
run_level=0,
app_name=MRP02,
run_level=0,
app_name=BILLNBI01,
run_level=0,
;
WMS-TL1>
2-8
68P09278A34-A
FEB 2007

The following example shows how to start Run Levels 02:
WMS-TL1> STA-LVL::2:C11::;
WMS-TL1>
WMS
M
02-10-03 11:12:18
C11 COMPLD
;
WMS-TL1>
STP-app
Input format
The format for the STP-app command to shut down a process is:
STP-app::<Process_Name>:<C_Tag>::;
Description
Process_Name is the name of a core process running on the EMS Server or the Control Switch.
Type STP-app:: and press the Tab key to list them.
WMS-TL1> STP-app::
Help:
ADHLR01
BILLNBI01
LOGCM01
MRP02
ADHLR11
CCSW01
CCSW11
IPMH01
CDRCP01
IPMH02
MRP01
WMS-TL1>
prevent confusion between requests issued to the system and the responses to them. It must
be a string consisting of 16 characters or decimal numbers.

WMS-TL1> STP-app::ADHLR11:C1::;
WMS-TL1>
WMS 02-10-03 11:12:18
M C11 COMPLD
;
WMS-TL1>
68P09278A34-A
2-9
FEB 2007
STP-LVL
Input format
The format for the STP-LVL command to shut down all processes running at a particular run
level is:
STP-LVL::<Run_Level>:<C_Tag>::;
Description
Run_Level is any integer assigned as a run level to a process. The PoC performs an orderly
shutdown of the processes in descending order to the level specied. Type the highest run level
assigned to a process to shut down all processes.
prevent confusion between requests issued to the system and the responses to them. It must
be a string consisting of 16 characters or decimal numbers.
Enter the RTRV-app:::C15::app_name,run_level; command to view the run level assignments.
2-10
68P09278A34-A
FEB 2007

WMS-TL1> RTRV-app:::C15::app_name,run_level;
WMS-TL1>
WMS
M
03-04-14 23:03:25
C2 COMPLD
app_name=LOGCM01,
run_level=0,
app_name=IPMH01,
run_level=3,
app_name=IPMH02,
run_level=0,
app_name=CDRCP01,
run_level=0,
app_name=CCSW01,
run_level=0,
app_name=CCSW11,
run_level=0,
app_name=ADHLR01,
run_level=2,
app_name=ADHLR11,
run_level=2,
app_name=MRP01,
run_level=0,
app_name=MRP02,
run_level=0,
app_name=BILLNBI01,
run_level=0,
;
WMS-TL1>
The following example shows how to shut down Run Levels 02:
WMS-TL1> STP-LVL::2:C11::;
WMS-TL1>
WMS 02-10-03 11:12:18
M C11 COMPLD
;
WMS-TL1>
68P09278A34-A
2-11
FEB 2007
Maintenance Call Processing
The Call Control Switch (CCSW) application initiates or responds to the call setup request,
manages the state of the call, and releases the call.
WMS-TL1> SHOW-app_ccsw-SWSTATE:
Help:
operated on.
CCSW01
CCSW02
CCSW11
CCSW12
WMS-TL1>
SHOW-app_ccsw-SWSTATE
Input format
The format to display the sliding window state for congured CDRCP is as follows:
SHOW-app_ccsw-SWSTATE:<APP_CCSW>::<C_Tag>::;
Description
For more information on conguring CCSW process, refer to PoC Provisioning Guide.
2-12
68P09278A34-A
FEB 2007

WMS-TL1> SHOW-app_ccsw-SWSTATE:CCSW01::C1::;
WMS-TL1>
IP C1
>
WMS-TL1>
CCSW01
M
04-12-29 15:03:40
C1 COMPLD
Sliding Window Stats=CSM PID,
Value=1,
Sliding Window Stats=Sequence Start Value,
Value=0,
Sliding Window Stats=Sequence End Value,
Value=19999,
Sliding Window Stats=Window Start Value,
Value=2916,
Sliding Window Stats=Window End Value,
Value=12915,
Sliding Window Stats=Window Next Sequence Value,
Value=2919,
Sliding Window Stats=Last Ack Value from CDRCP,
Value=2915,
Sliding Window Stats=Unacked Record Count,
Value=3,
Sliding Window Stats=% of Buffer Full,
Value=0,
Sliding Window Stats=Buffer State,
Value=BUFFER_THRESHOLD_NORMAL,
Sliding Window Stats=CDRCP Port,
Value=4419,
Sliding Window Stats=CDRCP IP,
Value=192.168.0.142,
Sliding Window Stats=Connection State,
Value=CONNECTED,
;
WMS-TL1>
68P09278A34-A
2-13
FEB 2007
Maintenance CACIM
Maintenance CACIM
The Call admission control intelligent module (CACIM) is an independent, intelligent process
that acts on the data generated by the Collection and Distribution Engine (CDE) process.
WMS-TL1> SHOW-app_cacimHelp:
Modifier1 - The object specification detail.
CALLTYPES
CONFIG
CSMSTATE
STATE
WMS-TL1>
SHOW-app_cacim-CALLTYPES
Input format
SHOW-app_cacim-CALLTYPES:<APP_CACIM>::<C_Tag>::;
Description
For more information on conguring CACIM process, refer to PoC Provisioning Guide.

WMS-TL1> SHOW-app_cacim-CALLTYPES:CACIM01::C11::;
WMS-TL1>
IP C1
>
CACIM01
M
04-12-29 17:01:38
C1 COMPLD
CCSW ID=CCSW11,
PROTOCOL=CSM_PROTO_ID_SIP,
# of CALLERS=0,
# of CALLEES=0,
CCSW ID=CCSW11,
PROTOCOL=CSM_PROTO_ID_ISUP,
# of CALLERS=0,
2-14
68P09278A34-A
FEB 2007
Maintenance CACIM
# of CALLEES=0,
CCSW ID=CCSW11,
PROTOCOL=CSM_PROTO_ID_GSMA,
# of CALLERS=0,
# of CALLEES=0,
CCSW ID=CCSW11,
PROTOCOL=CSM_PROTO_ID_IS634,
# of CALLERS=0,
# of CALLEES=0,
CCSW ID=CCSW01,
PROTOCOL=CSM_PROTO_ID_SIP,
# of CALLERS=0,
# of CALLEES=0,
CCSW ID=CCSW01,
PROTOCOL=CSM_PROTO_ID_ISUP,
# of CALLERS=0,
# of CALLEES=0,
CCSW ID=CCSW01,
PROTOCOL=CSM_PROTO_ID_GSMA,
# of CALLERS=0,
# of CALLEES=0,
CCSW ID=CCSW01,
PROTOCOL=CSM_PROTO_ID_IS634,
# of CALLERS=0,
# of CALLEES=0,
;
WMS-TL1>
SHOW-app_cacim-CONFIG
Input format
SHOW-app_cdrcp-CONFIG:<APP_CACIM>::<C_Tag>::;
Description
68P09278A34-A
2-15
FEB 2007
Maintenance CACIM

WMS-TL1> SHOW-app_cacim-CONFIG:CACIM01::C11::;
WMS-TL1>
IP C11
>
WMS-TL1>
CACIM01
M
04-12-29 17:08:06
C2 COMPLD
CAC Config=Utilization Lower Bound,
Value=0.550000,
CAC Config=Utilization Upper Bound,
Value=0.850000,
CAC Config=Alpha Traffic,
Value=0.500000,
CAC Config=Alpha Throttle,
Value=0.750000,
CAC Config=Window Size (s),
Value=10.000000,
CAC Config=Polling Frequency (ms),
Value=5000,
CAC Config=Rated MG Utilization,
Value=0.600000,
CAC Config=Rated MG CPS,
Value=225,
CAC Config=Rated HLR Utilization,
Value=0.500000,
CAC Config=Rated HLR CPS,
Value=1000,
CAC Config=Rated Max Mem Limit (kB),
Value=1000000,
;
WMS-TL1>
SHOW-app_cacim-CSMSTATE
Input format
The format to display the current state of Call Admission Control Intelligent Module (CACIM) is
as follows:
SHOW-app_cacim-CSMSTATE:<APP_CACIM>::<C_Tag>::;
2-16
68P09278A34-A
FEB 2007
Maintenance CACIM
Description

WMS-TL1> SHOW-app_cacim-CSMSTATE:CACIM01::C12::;
WMS-TL1>
IP C4
>
WMS-TL1>
CACIM01
M
04-12-29 17:12:32
C4 COMPLD
CSM ID=CCSW11,
CAC Value=1,
CSM ID=CCSW01,
CAC Value=1,
;
WMS-TL1>
SHOW-app_cacim-STATE
Input format
The format to display the the current state of Call Admission Control Intelligent Module
(CACIM) is as follows:
SHOW-app_cacim-STATE:<APP_CACIM>::<C_Tag>::;
Description
68P09278A34-A
2-17
FEB 2007
Maintenance CACIM

WMS-TL1> SHOW-app_cacim-STATE:CACIM01::C12::;
WMS-TL1>
IP C12
>
WMS-TL1>
CACIM01
M
04-12-29 17:14:04
C5 COMPLD
Cac State=CCSW11 #of Callers,
State Value=0,
Cac State=CCSW11 #of Callees,
State Value=0,
Cac State=CCSW01 #of Callers,
State Value=0,
Cac State=CCSW01 #of Callees,
State Value=0,
Cac State=Previous Throttle Value,
State Value=1.000000,
Cac State=Smoothed Throttle Value,
Cac State=HLR Utilization,
Cac State=MG Utilization,
Cac State=CCSW11 CSM Util,
Cac State=CCSW01 CSM Util,
Cac State=CCSW11 Mem Usage [kB],
Cac State=CCSW01 Mem Usage [kB],
;
WMS-TL1>
2-18
68P09278A34-A
FEB 2007
Maintenance Billing
Maintenance Billing
SHOW-app_cdrcp-CONFIG
The Call Detail Record Collection Point (CDRCP) processes receive CDRs from the CCSW
processes and acknowledge them in groups. Each CDRCP process can handle the CDRs for
up to six CCSW processes. Each CDRCP process pairs with a BILLNBI process on the EMS
Server on which it is congured to run.
Input format
The format to display the conguration for CDRCP is as follows:
SHOW-app_cdrcp-CONFIG:<APP_CDRCP>::<C_Tag>::;
Description
APP_CDRCP is the CDRCP process congured to run on the EMS1 or EMS 2. For more
information on conguring CDRCP process, refer to PoC Provisioning Guide.
68P09278A34-A
2-19
FEB 2007
Maintenance Billing

WMS-TL1> SHOW-app_cdrcp-CONFIG:CDRCP01::C3::;
WMS-TL1>
IP C3
>
WMS-TL1>
CDRCP01
M
04-12-29 12:36:26
C3 COMPLD
CDRCP Config=CDRCP Name,
Value=CDRCP01,
CDRCP Config=Listen Port,
Value=4419,
CDRCP Config=CDR Output Path,
Value=/opt/WMS/rel/cdr/,
CDRCP Config=CDR File Rotation Interval (sec),
Value=600,
CDRCP Config=CDR File Rotation Count,
Value=1000,
CDRCP Config=CDR File Rotate Size (kBytes),
Value=500,
CDRCP Config=Frequency of commit to disk (sec),
Value=10,
CDRCP Config=Frequency of commit to disk (count),
Value=50,
CDRCP Config=Sliding Window - start sequence,
Value=0,
CDRCP Config=Sliding Window - end sequence,
Value=20000,
CDRCP Config=Sliding Window - ack time (sec),
Value=20,
CDRCP Config=Sliding Window - ack count,
Value=1000,
;
WMS-TL1>
SHOW-app_cdrcp-CSMSTATE
The Call Detail Record Collection Point (CDRCP) processes receive CDRs from the CCSW
processes and acknowledge them in groups. Each CDRCP process can handle the CDRs for
up to six CCSW processes. Each CDRCP process pairs with a BILLNBI process on the EMS
Server on which it is congured to run.
2-20
68P09278A34-A
FEB 2007
Maintenance Billing
Input format
The format to display the conguration for CDRCP is as follows:
SHOW-app_cdrcp-CSMSTATE:<APP_CDRCP>::<C_Tag>::;
Description
APP_CDRCP is the CDRCP process congured to run on the EMS1 or EMS 2. For more

WMS-TL1> SHOW-app_cdrcp-CSMSTATE:CDRCP01::C4::;
WMS-TL1>
IP C4
>
WMS-TL1>
CDRCP01
M
04-12-29 12:53:48
C4 COMPLD
CSM Connections=Number of CSM Connections,
Value=1,
CSM Connections=Active CSM pid,
Value=1,
;
WMS-TL1>
SHOW-app_cdrcp-DISKSTATE
Input format
The format to display the disk state for congured CDRCP is as follows:
SHOW-app_cdrcp-DISKSTATE:<APP_CDRCP>::<C_Tag>::;
68P09278A34-A
2-21
FEB 2007
Maintenance Billing
Description
APP_CDRCP is the CDRCP process congured to run on the EMS 1 or EMS 2. For more

WMS-TL1> SHOW-app_cdrcp-DISKSTATE:CDRCP01::C5::;
WMS-TL1>
IP C5
>
WMS-TL1>
CDRCP01
04-12-29 12:56:13
M C5 COMPLD
CDRCP Disk Statistics=CDR Output Path,
Value=/opt/WMS/rel/cdr/,
CDRCP Disk Statistics=Disk Space Available to Continue
?,
Value=TRUE,
CDRCP Disk Statistics=Total Disk Space,
Value=33451 (MB),
CDRCP Disk Statistics=Available Disk Space,
Value=12718 (MB),
CDRCP Disk Statistics=Percentage of Disk Space
Available,
Value=38 ,
CDRCP Disk Statistics=Disk Space Remaining When Writing
Will Halt,
Value=1000 (KB),
;
WMS-TL1>
SHOW-app_cdrcp-SWSTATE
Input format
The format to display the sliding window state for congured CDRCP is:
SHOW-app_cdrcp-SWSTATE:<APP_CDRCP>::<C_Tag>::;
2-22
68P09278A34-A
FEB 2007
Maintenance Billing
Description
APP_CDRCP is the CDRCP process congured to run on the EMS 1 or EMS 2. For more

WMS-TL1> SHOW-app_cdrcp-SWSTATE:CDRCP01::C6::;
WMS-TL1>
IP C6
>
WMS-TL1>
CDRCP01
M
04-12-29 14:34:56
C6 COMPLD
Sliding Window States=Number of Active CSM Connections,
Value=1,
Sliding Window States=Sliding Window of Active CSM pid,
Value=1,
Sliding Window States=
Window Buffer Size,
Value=10000,
Sequence Start Value,
Value=0,
Sequence End Value,
Value=19999,
Window Start Value,
Value=195,
Window End Value,
Value=10194,
Next Sequence Value,
Value=195,
Unacked CDR Record Count,
Value=0,
% of Buffer Filled,
Value=0,
Is upcall suspended ?,
Value=FALSE,
;
WMS-TL1>
68P09278A34-A
2-23
FEB 2007
Maintenance General
Maintenance General
ALW-MSG
Input format
The format to activate receiving autonomous messages from the server is:
ALW-MSG:::<C_Tag>::;
Refer ALW-MSG on page 2-24 to stop receiving autonomous messages from the server.

WMS-TL1> ALW-MSG:::C4::;
WMS-TL1>
MOSERVER
A
04-12-31 01:09:24
0 REPT-ALM
User: swadmin, executed command: ALW-MSG:::C4::; ,
result: OK
;
WMS-TL1>
WMS
M
04-12-31 01:09:24
C4 COMPLD
;
WMS-TL1>
WMS-TL1>
MOSERVER
04-12-31 01:09:56
*C 1 REPT-ALM
Znyx card name: ZNYX-0-3 port: 11, port_name: zre10
down, (state:2) affecting
vlan id: 1,.
;
WMS-TL1
2-24
68P09278A34-A
FEB 2007
Maintenance General
INH-MSG
Input format
The format to stop receiving autonomous messages from the server is:
INH-MSG:::<C_Tag>::;

WMS-TL1> INH-MSG:::C3::;
WMS-TL1>
WMS 04-12-31 01:43:53
M C3 COMPLD
;
WMS-TL1>
RTRV-EDPROVTYPES
Input format
The format for the RTRV-EDPROVTYPES command to display all the managed object types that
can be edited is:
RTRV-EDPROVTYPES:::<C_Tag>::;

WMS-TL1> RTRV-EDPROVTYPES:::C2::;
WMS 03-04-14 22:s06:53
M C2 COMPLD
sid_gmtoffset_map,
switch,
lpc,
rack,
shelf,
slot,
sigport,
cell,
cellfgn,
bsc,
msc,
68P09278A34-A
2-25
FEB 2007
Maintenance General
scp,
stp,
pbx,
pstn,
link,
lset,
route,
ssn,
mg,
mgcard,
mgport,
rtg,
ltg,
routegrp,
card,
app,
alarm,
alarmack,
trapreceiver,
user,
user_security,
rpc,
app_ccsw,
mgshelf,
pwrsup_sensor,
voltage_sensor,
temp_sensor,
fan_sensor,
csm_service,
app_stdhlr,
app_cacim,
call_trace,
trace_event,
app_cdrcp,
event,
mgshelf_pwrsup,
wms_jobs,
app_logcm,
app_gttapp,
app_pcmgr,
app_ss7mh,
app_whlr,
2-26
68P09278A34-A
FEB 2007
Maintenance General
app_wvlr,
app_wgcr,
app_wgcrmd,
app_whlrmd,
app_mrp,
app_ipmh,
app_parlay,
cluster,
stppair,
remotewms,
app_billingnbi,
vlan,
vlan_port,
vlan_config,
vlan_route,
local_moserver,
remote_moserver,
vlan_host_route,
znyx_port,
tam,
rtg_ctc_trunkindex,
rtg_ctc_switch_id,
rtg_ctc_scp,
rtg_ctc_hlr,
rtg_numanal_esc_crit,
ver,
threshold,
;
WMS-TL1>
RTRV-ENTERPRISE_SUBS
This command is used to query the list of subscribers part of a particular enterprise.
68P09278A34-A
2-27
FEB 2007
Maintenance General
Input format
The format for the RTRV-ENTERPRISE_SUBS command with all options is:
RTRV-ENTERPRISE_SUBS::<enterprise_name>:<C_Tag>::limit=< >,offset =< >::;
This command will not have the autocomplete tabs and <C_Tag> working, user is
expected to input the enterprise_name manually where limit and offset can have
default values.
Description
Enterprise_name: Subscribers are provisioned as part of an enterprise account and each
enterprise account have many administrators to maintain the contacts and groups for accounts
in that enterprise. Users must use an existing enterprise name to retrieve subscribers. If the
enterprise name does not exist, an error message no matching enterprise found will be
displayed.
Limit: Total number of results to return. This eld is optional with a default value being
50. This value should be greater than 1. The number of results could be less than the limit,
depending on the number of subs present in the database. This parameter has to be an integer,
else an error message Limit not a valid integer will be displayed.
Offset: Number of initial results to skip over before returning results. This eld is optional with
a default value of 0. If the value for this eld is more the number of results, an empty result
will be returned. This parameter has to be an integer, else an error message Offset not a
valid integer will be displayed.
2-28
68P09278A34-A
FEB 2007
Maintenance General

The following example shows records displayed in response to the command:
WMS-TL1> RTRV-ENTERPRISE_SUBS::laxmi:C2::LIMIT;
WMS-TL1>
WMS
M
06-02-28 19:06:09
C2 COMPLD
MDN=1039000009,
MDN=2223334001,
MDN=9039000001,
MDN=9039000002,
MDN=9039900001,
MDN=9039900002,
MDN=9039900003,
MDN=9039900004,
;
WMS-TL1>
RTRV-ENTERPRISE_SUBS_COUNT
This command is used to provided to query the count of subscribers part of a particular
enterprise.
Input Format
The format for the RTRV-ENTERPRISE_SUBS_COUNT command with all options is:
RTRV- ENTERPRISE_SUBS_COUNT::<enterprise_name>:<C_Tag>::;
Description
Enterprise_name: Subscribers are provisioned as part of an enterprise account and each
enterprise account have many administrators to maintain the contacts and groups for accounts
in that enterprise. Users must use an existing enterprise name to retrieve subscribers. If the
enterprise name does not exist, an error message no matching enterprise foundwill be
displayed.
68P09278A34-A
2-29
FEB 2007
Maintenance General

The following example shows the records displayed in response to the command is:
WMS-TL1> RTRV-ENTERPRISE_SUBS_COUNT::laxmi:C3:::;
WMS-TL1>
WMS 06-02-28 19:20:13
M C3 COMPLD
Count=8,
;
WMS-TL1>
RTRV-<MO_Type>
Input format
The format for the RTRV-<MO_Type> command with all options is:
RTRV-<MO_Type>:::<C_Tag>::;
Description
RTRV-<MO_Type> command displays all of the attributes and values of a managed object type.
MO_Type be any of the managed object (MO) types supported by this command. Type RTRV- and
press the Tab key to display them.

The following example shows only two of the records displayed in response to the command.
WMS-TL1> RTRV-card:::C7::;
WMS-TL1>
WMS 03-04-14 14:16:31
M C7 COMPLD
mo_type=card,
mo_id=3958821,
card_name=NMHOST01,
ip=192.168.0.141,
ip2=192.168.0.141,
wms_part_number=NULL,
2-30
68P09278A34-A
FEB 2007
Maintenance General
hostname=nmhost01,
mac=,
mac2=,
serial_num=,
netmask=NULL,
broadcast=NULL,
isperipheral=N,
card_type=NMHOST,
boot_path=NULL,
admin_state=UNLOCKED,
slot_id=1,
shelf_id=1,
rack_id=1,
card_connect_timeout=120000,
op_state=ENABLED,
noAlarmCritical=NULL,
noAlarmMajor=1,
noAlarmMinor=NULL,
cpuUtilization=0,
memUtilization=24,
memTotalK=1285644,
memFreeK=969512,
mo_type=card,
mo_id=3958822,
card_name=NMHOST02,
ip=192.168.0.142,
ip2=192.168.0.142,
hostname=nmhost02,
mac=,
mac2=,
serial_num=,
netmask=NULL,
broadcast=NULL,
isperipheral=N,
card_type=NMHOST,
boot_path=NULL,
slot_id=1,
shelf_id=2,
rack_id=1,
68P09278A34-A
2-31
FEB 2007
Maintenance General
op_state=ENABLED,
noAlarmMajor=1,
noAlarmMinor=NULL,
cpuUtilization=0,
memUtilization=12,
memTotalK=1285644,
memFreeK=1127544,
;
WMS-TL1>
RTRV-<MO_Type>::<0>:<C_Tag>
Input format
The format for the RTRV-<MO_Type>::<0>: command to display the prov_sync_cong details is:
RTRV-<MO_Type>::<0>:<C_Tag>::;
Description
MO_Type must be the managed object (MO) type supported by this command. Type RTRV- and
press the Tab key to display prov_sync_cong as one of the MO types.
It must be a string consisting of 1 6 characters or decimal numbers.
Type RTRV-<MO_Type>:::<C_Tag>:: and press the Tab key to display the values. For example,
WMS-TL1> RTRV-prov_sync_config::0:C1::
Help:
Parameter Name - The name of the attribute.
debug
id
max_ftp_timeout
file_transfer_mode
mo_type
max_ftp_conn_retry
mo_id
script_sleep_time
;
WMS-TL1>
2-32
68P09278A34-A
FEB 2007
Maintenance General

The following example shows the details of prov_sync_cong parameters is:
WMS-TL1> RTRV-prov_sync_config::0:C1::;
WMS-TL1>
WMS 04-02-05 14:44:12
M C2 COMPLD
mo_type=prov_sync_config,
mo_id=36995027,
id=0,
file_transfer_mode=FTP,
script_sleep_time=60,
max_ftp_conn_retry=3,
max_ftp_timeout=120,
debug=1,
;
WMS-TL1>
RTRV-<MO_Type>-UPDATEATTRS
Input format
The format for the RTRV-<MO_Type>-UPDATEATTRS command to display updated attributes of
a managed object type is:
RTRV-<MO_Type>-UPDATEATTRS:::<C_Tag>::;
Description
68P09278A34-A
2-33
FEB 2007
Maintenance General

WMS-TL1> RTRV-card-UPDATEATTRS:::C6::;
WMS-TL1>
WMS 03-03-26 11:23:20
M C6 COMPLD
admin_state,
card_connect_timeout,
;
WMS-TL1>
RTRV-<MO_Type>-ATTRS
Input format
The format for the RTRV-<MO_Type>-ATTRS command display all of the attributes of a managed
object type with all options is:
RTRV-<MO_Type>ATTRS-:::<C_Tag>::;
Description
2-34
68P09278A34-A
FEB 2007
Maintenance General
Example input / output Format

WMS-TL1> RTRV-card-ATTRS:::C11::;
WMS-TL1>
WMS
M
03-03-20 13:53:10
C11 COMPLD
mo_type,
mo_id,
card_name,
ip,
ip2,
wms_part_number,
hostname,
mac,
mac2,
serial_num,
netmask,
broadcast,
isperipheral,
card_type,
boot_path,
admin_state,
slot_id,
shelf_id,
rack_id,
op_state,
noAlarmCritical,
noAlarmMajor,
noAlarmMinor,
cpuUtilization,
memUtilization,
memTotalK,
memFreeK,
;
WMS-TL1>
68P09278A34-A
2-35
FEB 2007
Maintenance General
RTRV-<MO_Type>-VALS
Input format
The format for the RTRV-<MO_Type>-VALS command display all the values of an attribute is:
RTRV-<MO_Type>-VALS:::<C_Tag>::<Attribute_Name>;
Description
MO_Type can be any of the managed object (MO) types supported by this command. Type RTRVand press the Tab key to display them.
Attribute_Name is the name of an object property (for example, a statistic and parameter name)
to display. Type RTRV-< MO_Type>-VALS:::<C_Tag>:: and press the Tab key to display them.
2-36
68P09278A34-A
FEB 2007
Maintenance General

WMS-TL1> RTRV-card-VALS:::C5::
Help:
admin_state
isperipheral
noAlarmMajor
boot_path
mac
noAlarmMinor
broadcast
mac2
op_state
card_connect_timeout
memFreeK
rack_id
card_name
memTotalK
serial_num
card_type
memUtilization
shelf_id
cpuUtilization
mo_id
slot_id
hostname
mo_type
wms_part_number
ip
netmask
ip2
noAlarmCritical
WMS-TL1>
The following example shows how to display all values of the attribute named memUtilization.
WMS-TL1> RTRV-card-VALS:::C12::memUtilization;
WMS-TL1>
WMS 03-04-14 14:41:53
M C12 COMPLD
24,
12,
0,
0,
0,
0,
32,
4,
3,
4,
5,
5,
32,
;
WMS-TL1>
68P09278A34-A
2-37
FEB 2007
Maintenance General
RTRV-<MO_Type>-CREATEATTRS
Input Format
The format for the RTRV-<MO_Type>-CREATEATTRS command to display all the create attributes
of a managed object type:
RTRV-<MO_Type>-CREATEATTRS:::<C_Tag>::;
Description

WMS-TL1> RTRV-card-CREATEATTRS:::C5::;
WMS-TL1>
WMS
M
03-03-26 11:46:12
C5 COMPLD
card_name,
ip,
ip2,
wms_part_number,
hostname,
mac,
mac2,
serial_num,
netmask,
broadcast,
isperipheral,
card_type,
boot_path,
admin_state,
slot_id,
shelf_id,
rack_id,
;
WMS-TL1>
2-38
68P09278A34-A
FEB 2007
Maintenance General
RTRV-<MO_Type>-INST
Input format
The format for the RTRV-<MO_Type>-INST command to list all the instance IDs of a managed
object type:
RTRV-<MO_Type>-INST:::<C_Tag>::;
Description

WMS-TL1> RTRV-card-INST:::C11::;
WMS-TL1>
WMS 03-04-14 18:08:38
M C11 COMPLD
NMHOST01,
NMHOST02,
"ZNYX-0-3",
"ZNYX-0-4",
"TAM-0-1",
"TAM-0-2",
CARD05,
CARD06,
CARD07,
CARD08,
CARD09,
CARD10,
CARD11,
CARD12,
;
WMS-TL1>
68P09278A34-A
2-39
FEB 2007
Maintenance General
RTRV-<MO_Type>::<MO_Instance>
Input format
The format for the RTRV-<MO_Type>::<MO_Instance> command to display all of the attributes
and values of a specied managed object:
RTRV-<MO_Type>::<MO_Instance>:<C_Tag>::;
Description
MO_Instance identies the object to retrieve. Type RTRV-<MO_Type>:: and press the Tab key to
list the instances of the specied managed object type. For example,
WMS-TL1> RTRV-card::
Help:
"TAM-0-1"
"ZNYX-0-4"
CARD07
CARD11
"TAM-0-2"
CARD05
CARD08
CARD12
"ZNYX-0-3"
CARD06
CARD09
NMHOST01
NMHOST02
WMS-TL1>
2-40
68P09278A34-A
FEB 2007
Maintenance General

WMS-TL1> RTRV-card::CARD07:C8::;
WMS-TL1>
WMS
M
03-04-14 14:21:56
C8 COMPLD
mo_type=card,
mo_id=3958827,
card_name=CARD07,
ip=192.168.0.107,
ip2=192.168.0.107,
hostname=slot07,
mac=,
mac2=,
serial_num=,
netmask=NULL,
broadcast=NULL,
isperipheral=Y,
card_type=CPCI736,
boot_path=NULL,
slot_id=7,
shelf_id=3,
rack_id=1,
op_state=ENABLED,
noAlarmMajor=0,
noAlarmMinor=NULL,
cpuUtilization=0,
memUtilization=32,
memTotalK=1572384,
memFreeK=1065916,
;
WMS-TL1>
68P09278A34-A
2-41
FEB 2007
Maintenance General
RTRV-<MO_Type>::<Prex>:<C_Tag>
Input format
The format for the RTRV-<MO_Type>::<Prefix>:<C_Tag> command to display all of the
attributes for the cdb_prex _routing:
RTRV-<MO_Type>::<Prefix>:<C_Tag>::;
Description
MO_Type must be cdb_prex_routing managed object (MO) type supported by this command.
Type RTRV- and press the Tab key to display cdb_prex_routing as one of the MO types.
Prefix be a valid NPA. It must be of 3 decimal numbers.
Type RTRV-<MO_Type>:::<C_Tag>:: and press the Tab key to display the valid prex. For
example,
WMS-TL1> RTRV-cdb_prefix_routing::
Help:
901
902
903
904
905
906
907
908
909
WMS-TL1>
2-42
68P09278A34-A
FEB 2007
Maintenance General

The following example shows how to display the cdb_prex_routing attributes:
WMS-TL1> RTRV-cdb_prefix_routing::901:C3::;
WMS-TL1>
WMS
M
03-12-01 17:42:33
C3 COMPLD
mo_type=cdb_prefix_routing,
mo_id=22585089,
prefix=901,
app_name=ADHLR01,
preferred_cdb_ip=ipv4:10.232.112.70:7008,
alternate_cdb_ip=ipv4:10.232.112.70:7008,
hlr_pid_7bit=17,
;
WMS-TL1>
The preferred_cdb_ip and alternate_cdb_ip parameter value is the IP address of

the preferred AD Chassis and the alternate AD Chassis respectively.
RTRV-<MO_Type>-REFS
Input format
The format for the RTRV-<MO_Type>::<Prefix>:<C_Tag> command to display the reference
values for an attribute:
RTRV-<MO_Type>-REFS:::<C_Tag>::<Attribute_Name>;
68P09278A34-A
2-43
FEB 2007
Maintenance General
Description
Some attribute values must match one of a predened set of values. Enter the
RTRV-<MO_Type>-REFS command to view a predened set for one or more attributes. The
response indicates the options of referenced attributes (that is, those with a limited set of value
options), when adding an object or modifying a value.
All attributes are not referenced attributes. In fact, most are not. If an attribute does
not have a limited set of value options, the TL1 console does not list any values.
Attribute_Name is the name of the object property (for example, statistic and parameter name)
to display the limited set of values. Type RTRV-<MO_Type>-REFS:::< >::C_Tag and press the
Tab key to display the attribute names. For example,
WMS-TL1> RTRV-card-REFS:::C9::
Help:
admin_state
isperipheral
noAlarmMajor
boot_path
mac
noAlarmMinor
broadcast
mac2
op_state
card_connect_timeout
memFreeK
rack_id
card_name
memTotalK
serial_num
card_type
memUtilization
shelf_id
cpuUtilization
mo_id
slot_id
hostname
mo_type
wms_part_number
ip
netmask
ip2
noAlarmCritical
;
WMS-TL1>
2-44
68P09278A34-A
FEB 2007
Maintenance General

The following example shows how the TL1 Console responds when an attribute has a limited set
of potential values:
WMS-TL1> RTRV-card-REFS:::C16::card_type;
WMS-TL1>
WMS 03-04-14 18:03:17
M C16 COMPLD
NMHOST,
TAM,
ZNYX,
TP610,
PCORE680,
CPCI736,
;
WMS-TL1>
The following example shows how the TL1 Console responds when an attribute does not have a
limited set of potential values:
WMS-TL1> RTRV-card-REFS:::C9::hostname;
WMS-TL1>
WMS
M
03-03-27 15:57:30
C9 COMPLD
;
WMS-TL1>
RTRV-<MO_Type>-REL
Input format
The format for the RTRV-<MO_Type>-REL command to display the relations of a specied
managed object:
RTRV-<MO_Type>-REL::<MO_Instance>:<C_Tag>::relation = <Relation>;
68P09278A34-A
2-45
FEB 2007
Maintenance General
Description
View the relationship among objects in the database to isolate data or perform fault isolation.
For example, to view relationships to list the potential alarms that could be reported by a card.
MO_Instance identies the object with the relationships to retrieve. Type
RTRV-<MO_Type>-REL::and press the Tab key to list the instances of the specied managed
object type. For example,
WMS-TL1> RTRV-alarm-REL::
Help:
128106
128130
129496
129505
1726
38183
128107
128132
129504
1711
34456
;
WMS-TL1>
Relation is one of the relation types listed in response to the RTRV-RELS:::<C_Tag>::; command.

WMS-TL1> RTRV-alarmREL::128130:C14::relation=inv_ALARM;
WMS-TL1>
WMS 03-04-14 17:56:48
M C14 COMPLD
relation=inv_ALARM,
left_type=alarm,
left_key=128130,
right_type=pwrsup_sensor,
right_key=0-1,
;
WMS-TL1>
2-46
68P09278A34-A
FEB 2007
Maintenance General
RTRV-<MO_Type>-RELMO
Input format
The format for the RTRV-<MO_Type>-RELMO command to display all the managed objects related
to the specied managed object:
RTRV-<MO_Type>-RELMO::<MO_Instance>:<C_Tag>::;
Description
MO_Instance identies the object with the relationships to retrieve. Type
RTRV-<MO_Type>-RELMO:: and press the Tab key to list the instances of the specied managed
object type. For example,
WMS-TL1> RTRV-alarm-RELMO::
Help:
128106
128130
129496
129505
1726
38183
128107
128132
129504
1711
34456
;
WMS-TL1>

WMS-TL1> RTRV-alarm-RELMO::128130:C15::;
WMS-TL1>
WMS
M
03-04-14 17:59:11
C15 COMPLD
mo_type=pwrsup_sensor,
mo_id=3972688,
chassis_id=0,
sensor_id=PWRSUP1,
descr=Power supply 1,
noAlarmMajor=NULL,
noAlarmMinor=1,
mo_type=rack,
mo_id=3958794,
68P09278A34-A
2-47
FEB 2007
Maintenance General
rack_id=1,
name=VZWTest,
descr=VZWTest,
location=Tewksbury,
op_state=NULL,
noAlarmMajor=4,
noAlarmMinor=4,
mo_type=shelf,
mo_id=3958797,
shelf_id=3,
name=CHASSIS01,
rack_id=1,
descr=Chassis,
chassis_id=0,
snmp_ip=192.168.0.101,
community=public,
shelf_type=CONTROL_CHASSIS_FORCE21K,
shelf_position=3,
op_state=NULL,
chassis_aco=NULL,
noAlarmMajor=2,
noAlarmMinor=4,
mo_type=pwrsup_sensor,
mo_id=3972688,
chassis_id=0,
sensor_id=PWRSUP1,
descr=Power supply 1,
noAlarmMajor=NULL,
noAlarmMinor=1,
mo_type=alarm,
mo_id=6013390,
alarm_id=128130,
source=MOSERVER,
subSource=MOSERVER,
affectedOid=3972688,
firstRaiseTime="Tue Apr
8 11:23:24 2003",
category=0,
2-48
68P09278A34-A
FEB 2007
Maintenance General
probableCause=MO_SHELF_PWR_SUPP_BAD,
currentProblem=UNKNOWN,
severity=MINOR,
description="Shelf Power supply bad rack:VZWTest
shelf:CHASSIS01 sensorId:1 desc
or:Power supply 1 useraction:None ",
suggestedUserAction=,
systemAction=,
ackState=NOT_ACKNOWLEDGED,
correlatinState=0,
additionalData=rack_name=VZWTest;shelf_name=CHASSIS01;sens
or_id=1;descr=Power su
pply 1;useraction=None;,
mType=295777239302144,
lastRaiseTime="Tue Apr
8 11:23:24 2003",
noOfRaises=1,
;
WMS-TL1>
RTRV-<MO_Type>::<Sid>:<C_Tag>
Input format
The format for the RTRV-<MO_Type>::<Sid> command to display the Sid and the corresponding
GMT offsets is:
RTRV-<MO_Type>::<Sid>:<C_Tag>::;
68P09278A34-A
2-49
FEB 2007
Maintenance General
Description
MO_Type must be sid_gmtoffset_map managed object (MO) type supported by this command.
Type RTRV- and press the Tab key to display sid_gmtoffset_map as one of the MO types.
Sid be a valid 4 digit hexadecimal number.
Type RTRV-<MO_Type>:::<C_Tag>:: and press the Tab key to display the Sid values. For
example,
WMS-TL1> RTRV-sid_gmtoffset_map::
Help:
0002
0016
068F
102A
0038
0056
0077
00A2
00D6
011E
01E6
043E
;
WMS-TL1>

The following example shows how to display the valid SID and the corresponding GMT offset is:
WMS-TL1> RTRV-sid_gmtoffset_map::0002:C6::;
WMS-TL1>
WMS
M
03-12-01 18:09:30
C6 COMPLD
mo_type=sid_gmtoffset_map,
mo_id=389136,
sid=0002,
gmt_offset=-8,
is_dst_applicable=true,
;
WMS-TL1>
RTRV-<switch>::WMS::C1:<MO_Instance>
Input format
The format for the RTRV-<switch>::WMS::C1:<MO_Instance> command to display all of the
attributes and values of a managed information base type is:
RTRV-<switch>::WMS::C1:<MO_Instance>
2-50
68P09278A34-A
FEB 2007
Maintenance General
Description
switch is the managed object (MO) types supported by this command. Type RTRV- and press the
Tab key to display them.
WMS identies the system.
MO_Instance be any of the MIB types supported by this command.

Type RTRV-switch::WMS::C1::; and press the Enter key to display them.
WMS-TL1> RTRV-switch::WMS::C1::
Help:
abnormalBlockingAckInCgbaForPreviousCgb
abnormalUnblockingAckInCguaForPreviousCgu
admin_state
ansMobileEmergencyCalls
ansMobileOriginatingCalls
ansMobileTerminatingCalls
ansSipEmergencyCalls
ansSipOriginatingCalls
ansSipTerminatingCalls
arrivalOfVisitorsFromOtherPLMNs
assignCmpl95Percentile
assignCmpl99PercentileVal
assignCmplAvg
assignCmplMin
attAuthProcsInVLR
attCipheringModeControlProcs
attIncomingInterMSCHDOs
attInterVLRLocationUpdates
attInterrogationOfHLRsForRouting
attIntraMSCHDOs
attIntraVLRLocationUpdates
attMSMemoryAvailableNotifications
attMobileEmergencyCalls
attMobileOriginatingCalls
attMobileTerminatingCalls
attOpForMobileOriginatingPointToPointSMs
68P09278A34-A
2-51
FEB 2007
Maintenance General
attOpForMobileTerminatingPointToPointSMs
attOutgoingInterMSCHDOs
attPageReqs
attRegUpdates
attReqForAuthSetsSentToHLR
attSipEmergencyCalls
attSipOriginatingCalls
attSipTerminatingCalls
attSubsequentInterMSCHDOsMSCa
attSubsequentInterMSCHDOsMSCc
attTMSIReallocations
avgAlertCallHoldTime
avgBargeCallHoldTime
avgCallRate
avgConnectedGroupSize
avgGroupCallHoldTime
avgGroupsPerUser
avgHoldTime
avgLocUpdateTime
avgMembersPerGroup
avgNoOfParties
avgNumberOfContactsPerSubscriber
avgVoicePacketLossPerSession
circuitBlo
cumAttRegUpdates
cumFailedRegUpdates
cumSuccRegUpdates
cumTotAbortedAlertCalls
cumTotAbortedBargeCalls
cumTotAbortedCalls
cumTotAbortedGroupCalls
cumTotAttAlertCalls
cumTotAttBargeCalls
cumTotAttCalls
cumTotAttGroupCalls
cumTotCmplAlertCalls
cumTotCmplBargeCalls
cumTotCmplCalls
cumTotCmplGroupCalls
cumTotFailedAlertCalls
cumTotFailedBargeCalls
cumTotFailedCalls
2-52
68P09278A34-A
FEB 2007
Maintenance General
cumTotFailedGroupCalls
emptyResponsesForAuthFromHLR
externalHDOs
failedRegUpdates
hlrAccess95Percentile
hlrAccess99Percentile
hlrAccessAvg
hlrAccessMin
imsiAttachProcs
imsiDetachProcs
inabilityToReleaseACircuit
lastRebootDate
mediaSetup95Percentile
mediaSetup99PercentileVal
mediaSetupAvg
mediaSetupMin
messageformatError
missingBlockingAckInCgbaForPreviousCgb
missingUnblockingAckInCguaForPreviousCgu
mo_id
mo_type
nbrCallsGoingToAnnc
nbrGsmaCallOrig
nbrGsmaCallTerm
nbrIosCallOrig
nbrIosCallTerm
nbrIsupCallOrig
nbrIsupCallTerm
nbrOfBlackAnsInMSC
nbrOfClassMarkUpdates
nbrOfGreyAnsInMSC
nbrOfTransCheckIMEIRequests
nbrOfUnknownIMEIAnsInMSC
nbrOfWhiteAnsInMSC
nbrReassemblyErrorsNoSpace
nbrReassemblyErrorsSegmentOutSequence
nbrReassemblyErrorsTimerExpiry
nbrRouteFailuresNetworkCongestion
nbrRouteFailuresPCUnavailable
nbrRouteFailuresSubSystemCongestion
nbrRouteFailuresSubSystemFailure
nbrRouteFailuresTranslationAddressNature
68P09278A34-A
2-53
FEB 2007
Maintenance General
nbrRouteFailuresTranslationSpecAddress
nbrRouteFailuresUnEquippedUser
nbrRouteFailuresUnqualified
nbrSipCallOrig
nbrSipCallTerm
nbrSyntaxErrorDetected
noAckForAckResetWithinT17
noAlarmCritical
noAlarmCriticalUnacked
noAlarmMajor
noAlarmMajorUnacked
noAlarmMinor
noAlarmMinorUnacked
noBlaReceivedForBloWithinT13
noCgbaReceivedForCgbWithinT19
noCguaReceivedForCguWithinT21
noGraReceivedForGrsWithinT23
noUbaReceivedForUblWithinT15
op_state
pageResp95Percentile
pageResp99PercentileVal
pageRespAvg
pageRespMin
percentSysAvailability
percentilesLastUpdated
provDb
provDbDescr
provDbDriver
provDbDsn
provDbPasswd
provDbPort
provDbServer
provDbUser
releaseDueToUnrecognizedInfo
releaseInitiatedDueToAbnormalConditions
rlcNotReceivedWithinT5
setupCrossOffice95Percentile
setupCrossOffice99Percentile
setupCrossOfficeAvg
setupCrossOfficeMin
setupUser95Percentile
setupUser99Percentile
2-54
68P09278A34-A
FEB 2007
Maintenance General
setupUserAvg
setupUserMin
snmp_read_community
snmp_write_community
succAuthProcsInVLR
succCipheringModeControlProcs
succIncomingInterMSCHDOs
succInterVLRLocationUpdates
succInterrogationOfHLRsCallForwarding
succInterrogationOfHLRsMSRNObtained
succIntraMSCHDOs
succIntraVLRLocationUpdates
succMSMemoryAvailableNotifications
succMobileEmergencyCalls
succMobileOriginatingCalls
succMobileTerminatingCalls
succOpForMobileOriginatingPointToPointSMs
succOpForMobileTerminatingPointToPointSMs
succOutgoingInterMSCHDOs
succPageReqs
succReceivedAuthSetsFromHLR
succRegUpdates
succSipEmergencyCalls
succSipOriginatingCalls
succSipTerminatingCalls
succSubsequentInterMSCHDOsMSCa
succSubsequentInterMSCHDOsMSCc
succTMSIReallocations
sysAvailableNow
sys_contact
sys_descr
sys_location
sys_model
sys_name
timeSinceMonthStart
totAbortedAlertCalls
totAbortedBargeCalls
totAbortedCalls
totAbortedGroupCalls
totAttAlertCalls
totAttBargeCalls
totAttCalls
68P09278A34-A
2-55
FEB 2007
Maintenance General
totAttGroupCalls
totCmplAlertCalls
totCmplBargeCalls
totCmplCalls
totCmplGroupCalls
totFailedAlertCalls
totFailedBargeCalls
totFailedCalls
totFailedGroupCalls
totInProgressAlertCalls
totInProgressBargeCalls
totInProgressCalls
totInProgressGroupCalls
totalIsupUpMessagesReceived
totalIsupUpMessagesSent
totalMessagesHandled
totalMessagesHandledForLocalSystem
totalMsgReqGlobalTitleTranslation
totalNumberOfGroups
totalNumberOfSubscribers
transSubIdentifiedWithTMSI
unexpectedBlaWithAbnormalBlockingAck
unexpectedCgbaWithAbnormalBlockingAck
unexpectedCguaWithAbnormalUnblockingAck
unexpectedMessageReceived
unexpectedUbaWithAbnormalUnlockingAck
unscheduledOutage
;
WMS-TL1>
RTRV-PROVTYPES
Input format
The format for the RTRV-PROVTYPES command to display all the managed object types that
can be provisioned is:
RTRV-PROVTYPES:::<C_Tag>::;
2-56
68P09278A34-A
FEB 2007
Maintenance General
Description

WMS-TL1> RTRV-PROVTYPES:::C1::;
WMS-TL1>
WMS
M
03-04-14 22:35:03
C1 COMPLD
sid_gmtoffset_map,
switch,
lpc,
rack,
shelf,
slot,
sigport,
cell,
cellfgn,
bsc,
msc,
scp,
stp,
pbx,
pstn,
link,
lset,
route,
ssn,
mg,
mgcard,
mgport,
rtg,
ltg,
routegrp,
card,
app,
alarm,
alarmack,
trapreceiver,
user,
68P09278A34-A
2-57
FEB 2007
Maintenance General
user_security,
rpc,
app_ccsw,
mgshelf,
pwrsup_sensor,
voltage_sensor,
temp_sensor,
fan_sensor,
csm_service,
app_stdhlr,
app_cacim,
call_trace,
trace_event,
app_cdrcp,
wms_jobs,
app_logcm,
app_gttapp,
app_pcmgr,
app_ss7mh,
app_whlr,
app_wvlr,
app_wgcr,
app_wgcrmd,
app_whlrmd,
app_mrp,
app_ipmh,
app_parlay,
cluster,
stppair,
remotewms,
app_billingnbi,
vlan,
vlan_port,
vlan_config,
vlan_route,
local_moserver,
remote_moserver,
vlan_host_route,
znyx_port,
tam,
rtg_ctc_trunkindex,
rtg_ctc_switch_id,
2-58
68P09278A34-A
FEB 2007
Maintenance General
rtg_ctc_scp,
rtg_ctc_hlr,
ver,
;
WMS-TL1>
RTRV-SEC
Input format
The format for the RTRV-SEC command to display the current user security settings is:
RTRV-SEC:::<C_Tag>::;
Description
68P09278A34-A
2-59
FEB 2007
Maintenance General

The following example shows only three of the records displayed in response to the command.
WMS-TL1> RTRV-SEC:::C3::;
WMS-TL1>
WMS-TL1>
WMS
M
03-04-14 22:37:22
C4 COMPLD
mo_type=user_security,
mo_id=23894,
user_name=swuser,
access_level=ACCESS_SUPER,
prov_type=ALARM_LIST,
mo_id=23895,
user_name=swuser,
prov_type=OAMP,
mo_id=23914,
user_name=swuser,
prov_type=HARDWARE,
;
WMS-TL1>
RTRV-TYPES
Input format
The format for the RTRV-TYPES command to display all of the types of managed objects that
dene the attributes and default values for every instance in the database is:
RTRV-TYPES:::<C_Tag>::;
Description
2-60
68P09278A34-A
FEB 2007
Maintenance General

WMS-TL1> RTRV-TYPES:::C1::
WMS-TL1>
WMS 03-04-14 22:40:15
M C1 COMPLD
release_cause,
sid_gmtoffset_map,
switch,
lpc,
rack,
shelf,
slot,
disk,
sigport,
cell,
cellfgn,
bsc,
msc,
scp,
stp,
pbx,
pstn,
link,
lset,
route,
ssn,
mg,
mgcard,
mgport,
rtg,
ltg,
routegrp,
card,
app,
alarm,
alarmack,
trapreceiver,
user,
percentile,
succ_call,
succ_leg,
68P09278A34-A
2-61
FEB 2007
Maintenance General
fail_call,
fail_leg,
user_security,
rpc,
app_ccsw,
mgshelf,
pwrsup_sensor,
voltage_sensor,
temp_sensor,
fan_sensor,
csm_service,
app_stdhlr,
app_cacim,
call_trace,
trace_event,
app_cdrcp,
event,
mgshelf_pwrsup,
active_user,
wms_jobs,
app_logcm,
app_gttapp,
app_pcmgr,
app_ss7mh,
app_whlr,
app_wvlr,
app_wgcr,
app_wgcrmd,
app_whlrmd,
app_mrp,
app_ipmh,
app_parlay,
cluster,
stppair,
remotewms,
app_billingnbi,
vlan,
vlan_port,
vlan_config,
vlan_route,
local_moserver,
remote_moserver,
2-62
68P09278A34-A
FEB 2007
Maintenance General
vlan_host_route,
znyx_port,
tam,
rtg_ctc_trunkindex,
rtg_ctc_switch_id,
rtg_ctc_scp,
rtg_ctc_hlr,
ver,
threshold,
;
WMS-TL1>
RTRV-VERBS
Input format
The format for the RTRV-VERBS command to all of the verbs available on the TL1 console is:
RTRV-VERBS:::<C_Tag>::;
Description
68P09278A34-A
2-63
FEB 2007
Maintenance General

WMS-TL1> RTRV-VERBS:::C2::;
WMS-TL1>
WMS 03-04-14 22:41:43
M C2 COMPLD
ACT,
APP,
BLK,
BOOT,
CANC,
CRTE,
DLT,
ED,
EJCT,
INH,
KIL,
RESET,
RTRV,
STA,
STAT,
STP,
TEST,
UBLK,
UINH,
;
WMS-TL1>
2-64
68P09278A34-A
FEB 2007
General IPMH
General IPMH
SHOW-CONS
Input format
The format to display the List active IP Message Handler (IPMH) connections is:
SHOW-CONS:<APP_IPMH>::<C_Tag>::;
WMS-TL1> SHOW-CONS:IPMH
Help:
Target Id - A unique identifier of the element to be operated
on.
IPMH01
IPMH11
;
WMS-TL1>
Description
For more information on conguring MRS process, refer to PoC Provisioning Guide.
68P09278A34-A
2-65
FEB 2007
General IPMH

WMS-TL1> SHOW-CONS:IPMH01::C1::;
WMS-TL1>
IP C1
>
WMS-TL1>
IPMH01
M
04-12-30 06:08:52
C1 COMPLD
Address=:5001,
Type=WMSC(S),
Proto/Transport=WINCAP/SCTP,
State=UP,
Class=0,
Address=10.51.21.105:7008,
Type=IPMH(S),
State=DOWN,
Class=1,
Address=10.51.22.107:6008,
Type=IPMH(S),
State=DOWN,
Class=1,
Address=192.168.0.107:6008,
Type=IPMH(S),
State=DOWN,
Class=1,
Address=10.51.25.12:7008,
Type=IPMH(S),
State=DOWN,
Class=1,
;
WMS-TL1>
2-66
68P09278A34-A
FEB 2007
General Media resource platform
The Media Resource Process application (for running a Media Resource Server process),
performs voice multicasting and voice mixing over an IP network, and performs as an
announcement server. Refer to PoC Provisioning Guide for Media Resource Server details.
WMS-TL1> SHOW-app_mrpHelp:
Modifier1 - The object specification detail .
AUEP
CALLDETAIL
DLCX
STATS
SHOW-app_mrp-AUEP
Input format
The format to display the audits endpoints (AUEP) on the media resource platform (MRP),
also called a media resource server (MRS) is:
SHOW-app_mrp-AUEP:<APP_MRP>::<C_Tag>::;
Description
68P09278A34-A
2-67
FEB 2007

WMS-TL1> SHOW-app_mrp-AUEP:
Help:
operated on.
MRP01
MRP02
MRP03
MRP04
WMS-TL1> SHOW-app_mrp-AUEP:MRP02::C2::;
WMS-TL1>
IP C2
>
WMS-TL1>
MRP02
M
04-12-29 15:16:06
C2 COMPLD
Response=Not enough arguments,
;
WMS-TL1>
SHOW-app_mrp-STATS
Input format
The format to display the media resource platform (MRP) statistics is:
SHOW-app_mrp-STATS:<APP_MRP>::<C_Tag>::;
Description
2-68
68P09278A34-A
FEB 2007

WMS-TL1> SHOW-app_mrp-STATS:MRP01::C2::;
WMS-TL1>
IP C2
>
WMS-TL1>
MRP01
M
04-12-29 06:53:02
C2 COMPLD
MRS Current Statistics=Number of active calls: 13,
MRS Current Statistics=Number of active mixer calls: 0,
MRS Current Statistics=Number of active multicast calls
: 13,
MRS Current Statistics=Number of voice streams: 25,
MRS Current Statistics=Number of active spool calls: 0,
;
WMS-TL1>
68P09278A34-A
2-69
FEB 2007
General Log Details
General Log Details
The LOG details the events reported by the PoC entities and stores them in les on the EMS
Server. The application runs on one of the two EMS Servers. The user can run a maximum of
one per PoC system. It does not run in backup mode.
LOG details gives the Log level and local log for all the process running on PoC.
WMS-TL1> SHOW-LOGDETAILS:
Help:
operated on.
ADHLR01
CCSW01
CCSW05
CDRCP01
LOG_TL1
MRP04
IPMH01
MRP01
MRP05
MRP08
ADHLR11
CCSW02
CCSW06
MRP09
BILLNBI01 CCSW03
CCSW07
IPMH11
MRP02
MRP06
CACIM01
CCSW08
LOGCM01
MRP03
MRP07
CCSW04
WMS-TL1>
SHOW-LOGDETAILS:ADHLR01
Input format
The format to display the log level for ADHLR process is:
SHOW-LOGDETAILS::<APP_ADHLR>::<C_Tag>::;
Description
For more information on conguring ADHLR process, refer to PoC Provisioning Guide.
2-70
68P09278A34-A
FEB 2007
General Log Details

WMS-TL1> SHOW-LOGDETAILS:ADHLR01::C1::;
WMS-TL1>
IP C1
>
WMS-TL1>
ADHLR01
04-12-30 01:17:22
M C1 COMPLD
Loglevel=3,
LocalLog=false,
;
WMS-TL1>
SHOW-LOGDETAILS:BILLNBI01
Input format
The format to display the log level for ADHLR process is:
SHOW-LOGDETAILS::<APP_BILLNBI>::<C_Tag>::;
Description
For more information on conguring BILLNBI process, refer to PoC Provisioning Guide.

WMS-TL1> SHOW-LOGDETAILS:BILLNBI01::C1::;
WMS-TL1>
IP C1
>
WMS-TL1>
BILLNBI01
M
04-12-30 01:28:54
C1 COMPLD
Loglevel=3,
LocalLog=false,
;
WMS-TL1>
68P09278A34-A
2-71
FEB 2007
General Log Details
SHOW-LOGDETAILS:CACIM
Input format
The format to display the log level for CACIM process is:
SHOW-LOGDETAILS::<APP_CACIM>::<C_Tag>::;
Description

WMS-TL1> SHOW-LOGDETAILS:CACIM01::C2::;
WMS-TL1>
IP C2
>
WMS-TL1>
CACIM01
04-12-30 01:30:07
M C2 COMPLD
Loglevel=3,
LocalLog=false,
;
WMS-TL1>
SHOW-LOGDETAILS:CCSW
Input format
The format to display the log level for CCSW process is:
SHOW-LOGDETAILS::<APP_CCSW>::<C_Tag>::;
Description
For more information on conguring CCSW process, refer to PoC Provisioning Guide.
2-72
68P09278A34-A
FEB 2007
General Log Details

WMS-TL1> SHOW-LOGDETAILS:CCSW02::C3::;
WMS-TL1>
IP C3
>
WMS-TL1>
CCSW02
04-12-30 01:30:38
M C3 COMPLD
Loglevel=3,
LocalLog=false,
;
WMS-TL1>
SHOW-LOGDETAILS:CDRCP
Input format
The format to display the log level for CDRCP process is:
SHOW-LOGDETAILS::<APP_CDRCP>::<C_Tag>::;
Description
For more information on conguring CDRCP process, refer to PoC Provisioning Guide.

WMS-TL1> SHOW-LOGDETAILS:CDRCP01::C4::;
WMS-TL1>
IP C4
>
WMS-TL1>
CDRCP01
04-12-30 01:31:05
M C4 COMPLD
Loglevel=3,
LocalLog=false,
;
WMS-TL1>
68P09278A34-A
2-73
FEB 2007
General Log Details
SHOW-LOGDETAILS:IPMH
Input format
The format to display the log level for IPMH process is:
SHOW-LOGDETAILS::<APP_IPMH>::<C_Tag>::;
Description
For more information on conguring IPMH process, refer toPoC Provisioning Guide.

WMS-TL1> SHOW-LOGDETAILS:IPMH01::C5::;
WMS-TL1>
IP C5
>
WMS-TL1>
IPMH01
04-12-30 01:31:38
M C5 COMPLD
Loglevel=3,
LocalLog=false,
;
WMS-TL1>
SHOW-LOGDETAILS:LOGCM
Input format
The format to display the log level for LOGCM process is:
SHOW-LOGDETAILS::<APP_LOGCM>::<C_Tag>::;
Description
For more information on conguring LOGCM process, refer to PoC Provisioning Guide.
2-74
68P09278A34-A
FEB 2007
General Log Details

WMS-TL1> SHOW-LOGDETAILS:LOGCM01::C1::;
WMS-TL1>
IP C1
>
WMS-TL1>
LOGCM01
04-12-30 01:38:01
M C1 COMPLD
Loglevel=7,
LocalLog=false,
;
WMS-TL1>
SHOW-LOGDETAILS:LOG_TL1
Input format
The format to display the log level for LOG_TL1 process is:
SHOW-LOGDETAILS::<APP_LOG_TL1>::<C_Tag>::;
Description
For more information on conguring LOG_TL1 process, refer to PoC Provisioning Guide.

WMS-TL1> SHOW-LOGDETAILS:LOG_TL1::C2::;
WMS-TL1>
IP C2
>
WMS-TL1>
LOG_TL1
04-12-30 01:38:21
M C2 COMPLD
Loglevel=7,
LocalLog=false,
;
WMS-TL1>
68P09278A34-A
2-75
FEB 2007
General Log Details
SHOW-LOGDETAILS:MRP
Input format
The format to display the log level for MRP process is:
SHOW-LOGDETAILS::<APP_MRP>::<C_Tag>::;
Description
For more information on conguring MRP process, refer to PoC Provisioning Guide.

WMS-TL1> SHOW-LOGDETAILS:MRP04::C3::;
WMS-TL1>
IP C3
>
WMS-TL1>
MRP04 04-12-30 01:38:47
M C3 COMPLD
Loglevel=3,
LocalLog=false,
;
WMS-TL1>
SHOW-LOGDETAILS:MTAS
Input format
The format to display the log level for MTAS process is:
SHOW-LOGDETAILS::<APP_MTAS>::<C_Tag>::;
Description
For more information on conguring MTAS process, refer to PoC Provisioning Guide.
2-76
68P09278A34-A
FEB 2007
General Log Details

WMS-TL1> SHOW-LOGDETAILS:MTAS01::C1::;
WMS-TL1>
IP C1
>
WMS-TL1>
MTAS01
04-12-30 01:59:26
M C1 COMPLD
Loglevel=15,
LocalLog=true,
;
WMS-TL1>
SHOW-LOGDETAILS:ADGCR
Input format
The format to display the log level for ADGCR process is:
SHOW-LOGDETAILS::<APP_ADGCR>::<C_Tag>::;
Description
For more information on conguring ADHLR process, refer to PoC Provisioning Guide.

WMS-TL1> SHOW-LOGDETAILS:ADGCR01::C2::;
WMS-TL1>
IP C2
>
WMS-TL1>
ADGCR01
04-12-30 02:00:21
M C2 COMPLD
Loglevel=3,
LocalLog=false,
;
WMS-TL1>
68P09278A34-A
2-77
FEB 2007
General Log Details
SHOW-LOGDETAILS:SYNC
Input format
The format to display the log level for SYNC process is:
SHOW-LOGDETAILS::<APP_SYNC>::<C_Tag>::;
Description
For more information on conguring SYNC process, refer to PoC Provisioning Guide.

WMS-TL1> SHOW-LOGDETAILS:SYNC01::C2::;
WMS-TL1>
IP C2
>
WMS-TL1>
SYNC01
04-12-30 02:00:21
M C2 COMPLD
Loglevel=3,
LocalLog=false,
;
WMS-TL1>
TXN-ABORT
Input format
The format to abort a transaction in progress is as shown below:
TXN-ABORT:::<C_Tag>::;

WMS-TL1> TXN-ABORT:::C18::;
WMS-TL1>
WMS
M
04-12-31 12:41:00
C18 COMPLD
;
WMS-TL1>
2-78
68P09278A34-A
FEB 2007
General Log Details
TXN-BEGIN
Input format
The format to begin a transaction is as shown below:
TXN-BEGIN:::<C_Tag>::;

WMS-TL1> TXN-BEGIN:::C19::;
WMS-TL1>
WMS 04-12-31 12:41:01
M C18 COMPLD
;
WMS-TL1>
TXN-END
Input format
The format to begin a transaction is as shown below:
TXN-END:::<C_Tag>::;

WMS-TL1> TXN-END:::C20::;
WMS-TL1>
WMS 04-12-31 12:41:04
M C18 COMPLD
;
WMS-TL1>
68P09278A34-A
2-79
FEB 2007
Provisioning
Provisioning
CRTE
Input format
The format for the CRTE-<MO_Type> command with all options is:
CRTE-<MO_Type>:::<C_Tag>::<Parameter_Name>=<Value>,<Paramet er_Name>=<Value>;
Description
MO_Type be any of the managed object (MO) types supported by this command. Type RTRV - and
Refer PoC MIB Reference Manual for MO types supported by PoC.

<Parameter_Name>=<Value>, is the list of attribute names and values, separated by values, to be
assigned to the newly created object. Type the CRTE-<MO_Type>:::<C_Tag>:: portion of the
command to list the attributes to be assigned to the new object. Choose one of the instances
in the list described above if to use its attribute values as a guide to assigning values to the
object to be created.
Enter the RTRV-<MO_Type>-REFS command for each attribute assigned upon the
creation of a new object instance. This command identies the possible values of an
attribute if it is restricted to a predened set.
2-80
68P09278A34-A
FEB 2007
Provisioning

WMS-TL1> CRTE-card:::C1::
Help:
admin_state
hostname
netmask
boot_path
ip
rack_id
broadcast
ip2
serial_num
card_connect_timeout isperipheral
card_name
mac
card_type
mac2
shelf_id
slot_id
wms_part_number
WMS-TL1>
Help:
Parameter Name - The value of the attribute.
LOCKED
SHUTTING_DOWN
UNLOCKED
The following example shows how to add a record of an EMS Server named HOST1 to the
database.
WMS-TL1>
CRTE-card:::C1::hostname=HOST1,card_name=HOST1,admin_state=UNLOCKED,ip=10.1.36.145,isperi
card_type=NMHOST;
WMS-TL1>
WMS
M
02-10-04 12:35:48
C1 COMPLD
;
WMS-TL1>
DLT
Input format
The format for the DLT-<MO_Type> command with all options is:
DLT-<MO_Type>::<MO_Instance>:<C_Tag>::;
68P09278A34-A
2-81
FEB 2007
Provisioning
Description
MO_Type be any of the managed object (MO) types supported by this command. Type DLT- and
MO_Instance identies the object to be deleted. Type DLT-<MO_Type>:: and press the Tab key
to list the instances of the specied managed object type. For example,
WMS-TL1> DLT-user::
Help:
opey
swadmin
swuser
WMS-TL1>

WMS-TL1> DLT-user::opey:C9::;
WMS-TL1>
WMS 03-03-23 16:38:21
M C9 COMPLD
;
WMS-TL1>
ED-<MO_Type>
Input format
The format for the ED-<MO_Type> command with all options is:
ED-<MO_Type>::<MO_Instance>:<C_Tag>::<Parameter_NameValue>=< >;
2-82
68P09278A34-A
FEB 2007
Provisioning
Description
MO_Type be any of the managed object (MO) types supported by this command. Type ED- and
MO_Instance identies the object to modify. Type ED-<MO_Type>:: and press the Tab key to list
the instances of the specied managed object type. For example,
WMS-TL1> RTRV-card::
Help:
"TAM-0-1"
"ZNYX-0-4"
CARD07
CARD10
NMHOST01
"TAM-0-2"
CARD05
CARD08
CARD11
NMHOST02
"ZNYX-0-3"
CARD06
CARD09
CARD12
WMS-TL1>

Enter the RTRV-<MO_Type>-UPDATEATTRS:::<C_Tag>::;command to list the attributes to
modify values.
WMS-TL1> RTRV-card-UPDATEATTRS:::C10::;
WMS-TL1>
WMS 03-03-27 16:10:42
M C10 COMPLD
admin_state,
;
WMS-TL1>
Type the RTRV-<MO_Type>:::<C_Tag>::<Parameter_Name>; to show all of the current values of
the attribute to change. Use the comma to separate multiple parameters. The following example
shows how to view all of the values of the card_connect_timeout parameter:
WMS-TL1> RTRV-card:::C11::card_connect_timeout;
68P09278A34-A
2-83
FEB 2007
Provisioning
WMS-TL1>
WMS
M
03-03-27 16:11:45
C11 COMPLD
;
WMS-TL1>
Enter the RTRV-<MO_Type>-REFS command for the attribute to be modied. The TL1 console
identies the possible values if it is restricted to a predened set. Otherwise, it doesnt list
values, as shown in the example below.
WMS-TL1> RTRV-card-REFS:::C13::card_connect_timeout;
WMS-TL1>
WMS 03-03-27 16:15:23
M C13 COMPLD
;
WMS-TL1>
Finally, use the data collected in the previous commands to modify the value of the target
attribute, as follows:
WMS-TL1> ED-card::IPHOST:C14::card_connect_timeout=140000;
2-84
68P09278A34-A
FEB 2007
Security
Security
ACT-USER
Input format
The format to establishes a user session by logging using the provided user name is:
ACT-USER::<User_Name>:<C_Tag>::;
Description
This command cancels a TL1 or EMS browser session by user name.
CANC-USER
Input format
The format for the CANC-USER command with all options is:
CANC-USER::<User_Name>:<C_Tag>::;
Description
This command cancels a TL1 or EMS browser session by user name.
User_Name is the user name associated with any open EMS browser or TL1 Console session.
Enter the RTRV-active_user:::<C_Tag>::; command to display the names of the active users.
68P09278A34-A
2-85
FEB 2007
Security

WMS-TL1>RTRV-active_user:::C15::;
WMS 03-03-27 16:44:34
M
C15 COMPLD
mo_type=active_user,
mo_id=4294967519,
user_name=swuser,
login_time="Thu Mar 27 08:55:53 2003",
local_port=2362,
remote_ip=192.168.0.142,
remote_port=33234,
session_id=39,
mo_id=4294967805,
user_name=swadmin,
local_port=2362,
remote_ip=192.168.0.142,
remote_port=38849,
session_id=72,
mo_id=4294967858,
user_name=swuser,
local_port=2361,
remote_ip=127.0.0.1,
remote_port=47662,
session_id=79,
;
WMS-TL1>
ED-user
Input format
The format for the ED-<user> command with all options is:
ED-user::<User_Name>:<C_Tag>::passwd=<New_Password>;
2-86
68P09278A34-A
FEB 2007
Security
Description
ED-user command modies the password of any user congured for access to the TL1 or
EMS browser.
For editing user passwords, refer to Access Security chapter in PoC Operations Guide.
User_Name is the user name associated with any user congured to access the EMS browser or
TL1 Console session. Type ED- user and press the Tab key to display them.
New_Password is any unique string up to 16 visible, ASCII characters except for an ampersand
(&), corner bracket (< or >), or single quote ().
A response showing the correlation tag and the textCOMPLD indicates the MO Server received

WMS-TL1> ED-user::
Help:
swadmin
swuser
WMS-TL1> ED-user::swuser:C2::passwd=wmspasswd;
WMS
M
03-03-23 17:00:46
C2 COMPLD
;
WMS-TL1>
68P09278A34-A
2-87
FEB 2007
*68P09278A34-A*
68P09278A34-A
Technical
Information
POC TL1 COMMAND REFERENCE GUIDE
SOFTWARE RELEASE 6.1.X.X

POC
ROW, US/HONG KONG
ENGLISH
FEB 2007
68P09278A34-A
POC TL1 COMMAND REFERENCE GUIDE

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

Part Number
68P09278A34-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

TL1 Command 68p09278a34

Uploaded by

Copyright:

Available Formats

TL1 Command 68p09278a34

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

TL1 Command 68p09278a34

Uploaded by

Copyright:

Available Formats

What is the purpose of the document?

What is the purpose of the document?

What information does it provide about editing user passwords?

What information does it provide about editing user passwords?

PoC TL1 Command Reference Guide

2003, 2004-2007 Motorola, Inc.

All Rights Reserved

PoC TL1 Command Reference Guide

Chapter 2: TL1 commands

TL1 command syntax . . . . . . .

PoC TL1 Command Reference Guide

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 *