BSS Command Reference
Technical Description
GSR9 68P02901W23-S
© 2009 Motorola, Inc. All Rights Reserved.
Accuracy While reasonable efforts have been made to assure the accuracy of this document, Motorola, Inc. assumes no liability resulting from any inaccuracies or omissions in this document, or from use of the information obtained herein. Motorola, Inc. reserves the right to make changes to any products described herein to improve reliability, function, or design, and reserves the right to revise this document and to make changes from time to time in content hereof with no obligation to notify any person of revisions or changes. Motorola, Inc. does not assume any liability arising out of the application or use of any product, software, or circuit described herein; neither does it convey license under its patent rights or the rights of others. It is possible that this publication may contain references to, or information about Motorola products (machines and programs), programming, or services that are not announced in your country. Such references or information must not be construed to mean that Motorola intends to announce such Motorola products, programming, or services in your country. Copyrights This document, Motorola products, and 3rd Party Software products described in this document may include or describe copyrighted Motorola and other 3rd Party supplied computer programs stored in semiconductor memories or other media. Laws in the United States and other countries preserve for Motorola, its licensors, and other 3rd Party supplied software certain exclusive rights for copyrighted material, including the exclusive right to copy, reproduce in any form, distribute and make derivative works of the copyrighted material. Accordingly, any copyrighted material of Motorola, its licensors, or the 3rd Party software supplied material contained in the Motorola products described in this document may not be copied, reproduced, reverse engineered, distributed, merged or modified in any manner without the express written permission of Motorola. Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication, estoppel, or otherwise, any license under the copyrights, patents or patent applications of Motorola or other 3rd Party supplied software, except for the normal non-exclusive, royalty free license to use that arises by operation of law in the sale of a product. Restrictions Software and documentation are copyrighted materials. Making unauthorized copies is prohibited by law. No part of the software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, without prior written permission of Motorola, Inc. License Agreements The software described in this document is the property of Motorola, Inc and its licensors. It is furnished by express license agreement only and may be used only in accordance with the terms of such an agreement. High Risk Materials Components, units, or 3rd Party products used in the product described herein are NOT fault-tolerant and are NOT designed, manufactured, or intended for use as on-line control equipment in the following hazardous environments requiring fail-safe controls: the operation of Nuclear Facilities, Aircraft Navigation or Aircraft Communication Systems, Air Traffic Control, Life Support, or Weapons Systems (High Risk Activities). Motorola and its supplier(s) specifically disclaim any expressed or implied warranty of fitness for such High Risk Activities. Trademarks
Motorola and the Stylized M Logo are registered in the US Patent & Trademark Office. All other product or service names are the property of their respective owners.
The CE mark confirms Motorola, Inc. statement of compliance with EU directives applicable to this product. Copies of the Declaration of Compliance and installation information in accordance with the requirements of EN50385 can be obtained from the local Motorola representative or by contacting the Customer Network Resolution Center (CNRC). The 24 hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.
Nov 2009
Table of Contents
Contents ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Technical Description: BSS Command Reference Revision history . . . . . . . . . . General information . . . . . . . . Contacting Motorola . . . . . . . . Security advice. . . . . . . . . . . Warnings, cautions, and notes . . . Safety . . . . . . . . . . . . . . . CMM labeling and disclosure table Caring for the environment . . . . Motorola document set . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
. . . . . . . . .
2 4 6 7 8 9 10 11 13
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
1-2 1-10 1-15 1-18 1-22 1-23 1-24 1-25 1-26 1-28 1-37 1-40 1-43
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
2-2 2-5 2-6 2-11 2-57
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
3-2 3-3 3-9 3-15 3-16 3-17
Chapter 1: Introduction to commands Version updates due to this software release. . GSR9 new/modified parameters user reference BSS MMI functions . . . . . . . . . . . . . . BSS task-oriented command usage. . . . . . . Command/database parameter security levels . Command/database parameter types . . . . . Commands to be used with caution . . . . . . Parameters to be used with caution . . . . . . Entering MMI commands . . . . . . . . . . . MMI command availability . . . . . . . . . . . GSM cell ID format . . . . . . . . . . . . . . Indices . . . . . . . . . . . . . . . . . . . . . SYSGEN mode . . . . . . . . . . . . . . . . .
. . . form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2: Equipping the CM database Introduction to equipping the CM database Using the equip command . . . . . . . . . Equipage hierarchy . . . . . . . . . . . . Information for equipping devices . . . . . Information for equipping functions . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
Chapter 3: Device/function related commands Command reference presentation Device-related commands . . . . Device identifiers . . . . . . . . Function related commands . . . Function identifiers . . . . . . . Slots . . . . . . . . . . . . . . . 68P02901W23-S Nov 2009
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
i
Contents
equip/unequip command matrix Alarm devices . . . . . . . . . add_cell . . . . . . . . . . . . add_conn. . . . . . . . . . . . add_neighbor . . . . . . . . . add_nsvc . . . . . . . . . . . . add_rtf_path . . . . . . . . . . alarm_mode . . . . . . . . . . assess . . . . . . . . . . . . . cage_audit . . . . . . . . . . . cell_name . . . . . . . . . . . chg_acs_params . . . . . . . . chg_a5_alg_pr . . . . . . . . . chg_audit_sched . . . . . . . . chg_cell_element . . . . . . . . chg_cell_id . . . . . . . . . . . chg_cmd_level . . . . . . . . . chg_csfp . . . . . . . . . . . . chg_dte . . . . . . . . . . . . chg_eas_alarm . . . . . . . . . chg_element . . . . . . . . . . chg_hop_params . . . . . . . . chg_ksw_config . . . . . . . . chg_level . . . . . . . . . . . . chg_rtf_freq . . . . . . . . . . chg_severity . . . . . . . . . . chg_smscb_msg . . . . . . . . chg_throttle . . . . . . . . . . chg_time . . . . . . . . . . . . chg_ts_usage . . . . . . . . . . chg_x25config . . . . . . . . . clear_cal_data . . . . . . . . . clear_database . . . . . . . . . clear_gclk_avgs . . . . . . . . configure_csfp . . . . . . . . . connection_code . . . . . . . . copy_cell . . . . . . . . . . . . copy_path . . . . . . . . . . . del_act_alarm . . . . . . . . . del_cell. . . . . . . . . . . . . del_conn . . . . . . . . . . . . del_neighbor . . . . . . . . . . del_nsvc . . . . . . . . . . . . del_rtf_path . . . . . . . . . . del_smscb_msg. . . . . . . . . device_audit . . . . . . . . . . diagnose_device . . . . . . . . disp_a5_alg_pr . . . . . . . . . disp_acs . . . . . . . . . . . . disp_act_alarm . . . . . . . . . disp_bss . . . . . . . . . . . . disp_bssgp_f_bmap. . . . . . . disp_cal_data. . . . . . . . . . disp_cbch_state . . . . . . . . disp_cell . . . . . . . . . . . . disp_cell_map . . . . . . . . . disp_cell_status . . . . . . . . disp_conn . . . . . . . . . . .
ii
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-18 3-20 3-22 3-33 3-35 3-48 3-50 3-52 3-54 3-58 3-62 3-65 3-73 3-76 3-84 3-90 3-94 3-95 3-98 3-102 3-106 3-128 3-136 3-142 3-144 3-148 3-150 3-156 3-158 3-161 3-166 3-169 3-171 3-173 3-175 3-177 3-179 3-187 3-190 3-192 3-195 3-197 3-202 3-204 3-206 3-210 3-217 3-221 3-223 3-225 3-229 3-231 3-233 3-237 3-241 3-244 3-247 3-261
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_csfp . . . . . . disp_csfp_status . . disp_dte . . . . . . disp_element . . . . disp_equipment . . disp_exp_config . . disp_flash . . . . . disp_gclk_avgs . . . disp_gclk_cal . . . . disp_gsm_cells . . . disp_hdlc . . . . . . disp_hopping . . . . disp_level . . . . . disp_link . . . . . . disp_link_usage . . disp_mms_ts_usage disp_neighbor . . . disp_nsvc . . . . . disp_options . . . . disp_processor . . . disp_relay_contact . disp_rtf_channel . . disp_rtf_path . . . . disp_severity . . . . disp_site . . . . . . disp_throttle . . . . disp_time. . . . . . disp_trace_call . . . disp_traffic . . . . . disp_transcoding . . disp_version . . . . disp_x25config . . . equip. . . . . . . . freq_types_allowed. gclk_cal_mode . . . ins_device . . . . . lock_device. . . . . Login. . . . . . . . Logout . . . . . . . mod_conn . . . . . mod_nsvc . . . . . modify_neighbor . . modify_value . . . . nacc_nc2_enabled . page . . . . . . . . query_audits . . . . reassign . . . . . . reattempt_pl . . . . reset_device . . . . reset_site . . . . . set_full_power . . . set_relay_contact. . shutdown_device . . site_audit . . . . . soft_reset . . . . . state . . . . . . . . status_mode . . . . store_cal_data . . .
68P02901W23-S Nov 2009
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3-263 3-267 3-269 3-272 3-283 3-305 3-307 3-309 3-311 3-314 3-317 3-320 3-325 3-326 3-328 3-330 3-343 3-353 3-356 3-367 3-373 3-375 3-381 3-383 3-385 3-386 3-388 3-390 3-394 3-397 3-399 3-401 3-403 3-417 3-421 3-423 3-429 3-438 3-441 3-442 3-445 3-447 3-456 3-469 3-470 3-472 3-477 3-483 3-485 3-492 3-496 3-500 3-502 3-507 3-511 3-515 3-530 3-534
iii
Contents
swap_devices . . sysgen_mode . . . time_stamp. . . . trace_call . . . . trace_connection . trace_stop . . . . unconfigure_csfp . unequip . . . . . unlock_device . . _bss_data,6. . . . _bss_data,10 . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
3-537 3-540 3-548 3-550 3-562 3-564 3-568 3-570 3-581 3-587 3-588
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
4-2 4-4 4-6 4-8 4-10
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
5-2 5-5 5-12 5-22 5-24 5-34 5-48
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
6-2 6-5 6-6 6-8 6-9 6-10 6-11 6-12 6-13 6-15 6-16 6-17 6-18 6-19 6-20 6-21 6-22 6-23 6-24 6-26 6-30 6-31 6-32 6-33 6-34 6-35
Chapter 4: UNIX commands alias . . help . . history . man . . unalias .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
Chapter 5: Statistics commands Statistical operations and information chg_stat_prop . . . . . . . . . . . . disp_enable_stat . . . . . . . . . . . disp_interval . . . . . . . . . . . . . disp_stat_prop . . . . . . . . . . . . disp_stats . . . . . . . . . . . . . . stat_mode . . . . . . . . . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
Chapter 6: CM database parameters CM database parameters presentation. _bss_data,2. . . . . . . . . . . . . . . _cell_data,20 . . . . . . . . . . . . . . _site_data, 5 . . . . . . . . . . . . . . aci_error_clr_thresh . . . . . . . . . . aci_error_gen_thresh. . . . . . . . . . aci_error_inc . . . . . . . . . . . . . . adap_ho_alt_trigger_rxqual . . . . . . adap_ho_pbgt . . . . . . . . . . . . . adap_ho_rxlev . . . . . . . . . . . . . adap_ho_rxqual . . . . . . . . . . . . adap_trigger_hop_rxqual_dl . . . . . . adap_trigger_hop_rxqual_ul . . . . . . adap_trigger_pbgt . . . . . . . . . . . adap_trigger_pbgt_nbr . . . . . . . . . adap_trigger_rxlev_dl . . . . . . . . . adap_trigger_rxlev_ul . . . . . . . . . adap_trigger_rxqual_dl. . . . . . . . . allow_8k_trau . . . . . . . . . . . . . alt_qual_proc. . . . . . . . . . . . . . amr_bss_half_rate_enabled. . . . . . . amr_bss_full_rate_enabled . . . . . . . amr_dl_la_mode_chg_min . . . . . . . amr_dl_thresh_adjust . . . . . . . . . amr_fr_dl_la_enabled. . . . . . . . . . amr_fr_ul_la_enabled. . . . . . . . . .
iv
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . .
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
amr_full_rate_enabled . . . amr_half_rate_enabled . . . amr_hr_dl_la_enabled . . . amr_hr_ul_la_enabled . . . amr_ms_high_cmr . . . . . amr_ms_high_rxqual . . . . amr_ms_low_cmr. . . . . . amr_ms_low_rxqual . . . . amr_ms_monitor_period . . arp_bg_1 . . . . . . . . . . arp_bg_2 . . . . . . . . . . arp_bg_3 . . . . . . . . . . arp_i_be_1 . . . . . . . . . arp_i_be_2 . . . . . . . . . arp_i_be_3 . . . . . . . . . arp_streaming_1 . . . . . . arp_streaming_2 . . . . . . arp_streaming_3 . . . . . . asym_edge_enabled . . . . attach_detach . . . . . . . auto_rf_loss_trace . . . . . ba_alloc_proc . . . . . . . band_preference . . . . . . band_preference_mode . . base_ip_address . . . . . . ber_loss_daily . . . . . . . ber_loss_hourly . . . . . . blind_search_preference . . bounce_protect_margin . . bs_ag_blks_res . . . . . . . bs_pa_mfrms . . . . . . . . bs_pag_blks_res . . . . . . bs_pbcch_blks . . . . . . . bs_pcc_chans . . . . . . . bs_prach_blks . . . . . . . bsc_type . . . . . . . . . . bsic . . . . . . . . . . . . bsp_overload_protection . . bss_egsm_alm_allowed . . . bss_msc_overload_allowed . bssgp_block_retries . . . . bssgp_cbl_bit. . . . . . . . bssgp_dwnld_retry . . . . . bssgp_pfc_bit . . . . . . . bssgp_racap_retries . . . . bssgp_reset_retries . . . . bssgp_unblock_retries . . . bts_p_con_ack . . . . . . . bts_p_con_interval . . . . . bts_power_control_allowed bts_txpwr_max_inner. . . . bts_type . . . . . . . . . . bvci . . . . . . . . . . . . call_trace_options . . . . . called_pci . . . . . . . . . calling_pci . . . . . . . . . carrier_disable_time . . . . carriers_ins_pwr_fail . . . .
68P02901W23-S Nov 2009
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-36 6-38 6-40 6-41 6-42 6-43 6-44 6-45 6-46 6-47 6-49 6-51 6-53 6-55 6-57 6-59 6-61 6-63 6-65 6-66 6-68 6-70 6-72 6-74 6-77 6-79 6-80 6-81 6-82 6-83 6-85 6-87 6-88 6-89 6-90 6-91 6-93 6-96 6-97 6-98 6-99 6-100 6-102 6-103 6-105 6-106 6-107 6-108 6-110 6-112 6-114 6-118 6-120 6-122 6-124 6-125 6-126 6-127
v
Contents
cbc_fast_select . . . . . . . . . . cbc_intface_vers . . . . . . . . . cbc_vbind_cntr . . . . . . . . . . cbch_enabled . . . . . . . . . . cbs_outage_cntr . . . . . . . . . ccch_conf . . . . . . . . . . . . ccch_load_period. . . . . . . . . cell_bar_access_class . . . . . . cell_bar_access_switch . . . . . . cell_bar_qualify . . . . . . . . . cell_barred_delay . . . . . . . . cell_reselect_hysteresis . . . . . cell_reselect_offset . . . . . . . . cell_reselect_param_ind . . . . . channel_reconfiguration_switch . cic_error_clr_thresh . . . . . . . cic_error_gen_thresh. . . . . . . cic_error_inc . . . . . . . . . . . cic_validation . . . . . . . . . . ciph_mode_rej_allowed. . . . . . clk_src_fail_reset_period . . . . . coincident_cell . . . . . . . . . . coincident_offset . . . . . . . . . coincident_mb . . . . . . . . . . confusion_msg_allowed . . . . . congest_at_source . . . . . . . . congest_at_target . . . . . . . . congest_ho_margin . . . . . . . cp_option_reset_ckt . . . . . . . cp_option_rr_status . . . . . . . cr_calling . . . . . . . . . . . . ct_flow_control_hi_level . . . . . ct_flow_control_lo_level . . . . . ct_flow_control_msc_trace . . . . ctu2d_asym_opt . . . . . . . . . ctu2d_cap_opt . . . . . . . . . . c31_hyst . . . . . . . . . . . . . c32_qual . . . . . . . . . . . . . data_qual_enabled . . . . . . . . ddtr_ctrl_enabled . . . . . . . . decision_1_ncell_rxlev_av_h_calc. decision_1_dl_rxlev_av_ih . . . . decision_1_dl_rxqual_av_h . . . . decision_1_dl_rxqual_av_p . . . . decision_1_n1/decision_1_p1 . . . decision_1_n2/decision_1_p2 . . . decision_1_n3/decision_1_p3 . . . decision_1_n4/decision_1_p4 . . . decision_1_n5/decision_1_p5 . . . decision_1_n6/decision_1_p6 . . . decision_1_n7/decision_1_p7 . . . decision_1_n8/decision_1_p8 . . . decision_1_p_bgt_rxlev_av_h . . . decision_1_tim_adv_av_alg . . . . decision_1_ul_rxlev_av_h . . . . . decision_1_ul_rxlev_av_ih . . . . decision_1_ul_rxlev_av_p . . . . . decision_1_ul_rxqual_av_h . . . .
vi
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-129 6-131 6-132 6-133 6-134 6-135 6-138 6-140 6-143 6-145 6-147 6-148 6-150 6-152 6-154 6-156 6-157 6-158 6-159 6-160 6-161 6-162 6-164 6-165 6-167 6-168 6-170 6-171 6-172 6-173 6-174 6-175 6-176 6-177 6-178 6-179 6-180 6-182 6-184 6-186 6-187 6-188 6-189 6-190 6-191 6-193 6-195 6-197 6-199 6-201 6-203 6-205 6-207 6-208 6-209 6-210 6-211 6-212
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
decision_1_ul_rxqual_av_p . decision_alg_type . . . . . direct_inner_zone_threshold disuse_cnt_hreqave . . . . dl_audio_lev_offset . . . . . dl_dtx_voice_data . . . . . dl_rxlev_ho_allowed . . . . dl_rxqual_ho_allowed . . . dnlk_vad_dtx . . . . . . . . dpc. . . . . . . . . . . . . dr_allowed . . . . . . . . . dr_chan_mode_modify . . . dr_ho_during_assign . . . . dr_preference . . . . . . . dr_standard_congest . . . . dri_density . . . . . . . . . dsp_error_clr_thresh . . . . dsp_error_gen_thresh . . . dsp_error_inc . . . . . . . dtx_required . . . . . . . . dual_band_offset . . . . . . dyn_step_adj . . . . . . . . dyn_step_adj_fmpr . . . . . dynet_tchs_reserved . . . . early_classmark_sending. . eas_alarm . . . . . . . . . eas_alarm_type. . . . . . . eas_report_opto . . . . . . eas_severity . . . . . . . . efr_enabled . . . . . . . . egprs_init_dl_cs . . . . . . egprs_init_ul_cs . . . . . . egsm_bcch_sd . . . . . . . egsm_handover_threshold . emergency_class_switch . . emergency_group_priority . en_incom_ho . . . . . . . . enhanced_relief . . . . . . eop_enabled . . . . . . . . ercgprsOpt . . . . . . . . . erc_ta_priority . . . . . . . eth_rx_errors_threshold . . eth_tx_errors_threshold . . ext_range_cell . . . . . . . ext_ul_dur . . . . . . . . . ext_utbf_nodata . . . . . . extended_paging_active . . extuplinkOpt . . . . . . . . fdd_multirat_reporting . . . fdd_gprs_qoffset . . . . . . fdd_qmin . . . . . . . . . . fdd_qoffset . . . . . . . . . fdd_rep_quant . . . . . . . fer_meas_period . . . . . . fieldeng_always _enabled . force_hr_usage . . . . . . . free_run_enabled. . . . . . frequency_type. . . . . . .
68P02901W23-S Nov 2009
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-213 6-214 6-216 6-217 6-219 6-221 6-222 6-224 6-226 6-227 6-229 6-230 6-232 6-234 6-235 6-237 6-239 6-241 6-242 6-243 6-245 6-246 6-247 6-248 6-250 6-252 6-253 6-255 6-256 6-258 6-260 6-262 6-264 6-266 6-268 6-270 6-272 6-274 6-275 6-277 6-278 6-279 6-280 6-281 6-283 6-284 6-286 6-288 6-289 6-290 6-292 6-293 6-294 6-295 6-296 6-297 6-298 6-299
vii
Contents
full_pwr_rfloss . . . . . . . . . . gci_error_clr_thresh . . . . . . . gci_error_gen_thresh. . . . . . . gci_error_inc . . . . . . . . . . . gclk_qwarm_flag . . . . . . . . . global_reset_repetitions . . . . . gproc_slots . . . . . . . . . . . . gprs_alarm_time . . . . . . . . . gprs_bs_cv_max . . . . . . . . . gprs_cell_reselect_hysteresis . . gprs_com_ms_class . . . . . . . gprs_cr_margin . . . . . . . . . gprs_dl_pwr_mode . . . . . . . . gprs_drx_timer_max . . . . . . . gprs_enabled. . . . . . . . . . . gprs_intraho_allwd . . . . . . . . gprs_mac_mode . . . . . . . . . gprs_min_prr_blks . . . . . . . . gprs_ms_pan_dec . . . . . . . . gprs_ms_pan_inc . . . . . . . . . gprs_ms_pan_max . . . . . . . . gprs_ms_txpwr_max_cch . . . . . gprs_network_operation_mode . . gprs_num_pmrs . . . . . . . . . gprs_par_wait_ind . . . . . . . . gprs_pb . . . . . . . . . . . . . gprs_pc_alpha . . . . . . . . . . gprs_pc_meas_chan . . . . . . . gprs_reconfig_thresh_idle_tch . . gprs_reselect_offset . . . . . . . gprs_rxlev_access_min . . . . . . gprs_sched_beta . . . . . . . . . gprs_sig_bvci. . . . . . . . . . . gprs_temporary_offset . . . . . . gprs_type5_alg . . . . . . . . . . gprs_ts_config_alg . . . . . . . . gprs_ul_dl_bias. . . . . . . . . . group_block_unblock_allowed . . gsl_lcf_mapping . . . . . . . . . gsm_bss_half_rate_enabled . . . gsm_cell_id_format. . . . . . . . gsm_half_rate_enabled . . . . . . half_rate_enabled . . . . . . . . handover_power_level . . . . . . handover_required_curr_ch . . . handover_required_reject_switch handover_required_sp_ver_used . hcs_thr . . . . . . . . . . . . . . hdsl_losw_oos . . . . . . . . . . hdsl_losw_restore . . . . . . . . hdsl_snr_daily . . . . . . . . . . hdsl_snr_daily_mon_period. . . . hdsl_snr_hourly . . . . . . . . . hdsl_snr_hourly_mon_period . . . hdsl_snr_oos . . . . . . . . . . . hdsl_snr_restore . . . . . . . . . ho_exist_congest . . . . . . . . . ho_margin_def . . . . . . . . . .
viii
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-301 6-302 6-303 6-304 6-305 6-306 6-308 6-310 6-311 6-312 6-314 6-315 6-317 6-319 6-320 6-322 6-324 6-325 6-326 6-328 6-330 6-332 6-335 6-337 6-339 6-340 6-341 6-342 6-343 6-345 6-347 6-349 6-351 6-352 6-354 6-356 6-358 6-359 6-361 6-363 6-365 6-367 6-368 6-369 6-372 6-373 6-375 6-377 6-378 6-379 6-380 6-382 6-383 6-385 6-386 6-388 6-390 6-392
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
ho_margin_type5 . . . . . . . . ho_margin_usage_flag . . . . . ho_only_max_pwr . . . . . . . ho_pwr_level_inner. . . . . . . hop_count . . . . . . . . . . . hop_qual_enabled . . . . . . . hopping_support . . . . . . . . hopping_systems_enabled . . . hopping_systems_hsn . . . . . hopping_systems_mobile_alloc . hr_fr_hop_count . . . . . . . . hr_intracell_ho_allowed . . . . hr_res_ts . . . . . . . . . . . . illegal_circuit_id . . . . . . . . Improve_ts_enabled . . . . . . imrm_dcs1800_weight . . . . . imrm_egsm_weight . . . . . . imrm_force_recalc . . . . . . . imrm_pgsm_weight . . . . . . imrm_umts_weight . . . . . . . IncellOpt . . . . . . . . . . . . inc_prp_cap_ena . . . . . . . . init_dl_cs . . . . . . . . . . . . init_ul_cs . . . . . . . . . . . . inner_hr_usage_thres . . . . . inner_zone_alg . . . . . . . . . intave . . . . . . . . . . . . . inter_cell_handover_allowed . . inter_rat_enabled . . . . . . . interband_ho_allowed . . . . . interfer_bands . . . . . . . . . interfer_ho_allowed . . . . . . intra_cell_handover_allowed . . ksw_config . . . . . . . . . . . l_rxlev_dl_h . . . . . . . . . . l_rxlev_dl_p . . . . . . . . . . l_rxlev_ul_h . . . . . . . . . . l_rxlev_ul_p . . . . . . . . . . l_rxqual_dl_h . . . . . . . . . . l_rxqual_dl_h_amr_fr . . . . . . l_rxqual_dl_h_data . . . . . . . l_rxqual_dl_h_hopping . . . . . l_rxqual_dl_h_hopping_amr_fr . l_rxqual_dl_h_hopping_hr . . . l_rxqual_dl_h_hr . . . . . . . . l_rxqual_dl_p . . . . . . . . . . l_rxqual_dl_p_amr_fr . . . . . . l_rxqual_dl_p_data . . . . . . . l_rxqual_dl_p_hopping . . . . . l_rxqual_dl_p_hopping_amr_fr . l_rxqual_dl_p_hopping_hr . . . l_rxqual_dl_p_hr . . . . . . . . l_rxqual_ul_h . . . . . . . . . . l_rxqual_ul_h_amr_fr . . . . . . l_rxqual_ul_h_data . . . . . . . l_rxqual_ul_h_hopping . . . . . l_rxqual_ul_h_hopping_amr_fr . l_rxqual_ul_h_hopping_hr . . .
68P02901W23-S Nov 2009
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-394 6-395 6-397 6-398 6-400 6-401 6-403 6-405 6-407 6-409 6-411 6-412 6-414 6-415 6-416 6-419 6-420 6-422 6-424 6-426 6-428 6-429 6-431 6-433 6-435 6-436 6-439 6-441 6-443 6-445 6-447 6-449 6-450 6-452 6-454 6-456 6-458 6-460 6-462 6-464 6-465 6-467 6-469 6-471 6-473 6-474 6-476 6-478 6-480 6-482 6-484 6-486 6-488 6-490 6-491 6-493 6-495 6-497
ix
Contents
l_rxqual_ul_h_hr . . . . . . . . l_rxqual_ul_p . . . . . . . . . . l_rxqual_ul_p_amr_fr . . . . . . l_rxqual_ul_p_data . . . . . . . l_rxqual_ul_p_hopping . . . . . l_rxqual_ul_p_hopping_amr_fr . l_rxqual_ul_p_hopping_hr . . . l_rxqual_ul_p_hr . . . . . . . . land_layer1_mode . . . . . . . layer_number . . . . . . . . . lb_int_called_pci . . . . . . . . lb_int_calling_pci. . . . . . . . lb_int_cr_calling . . . . . . . . lb_int_dpc . . . . . . . . . . . lb_int_global_reset_repetitions . lcs_mode . . . . . . . . . . . . link_about_to_fail . . . . . . . link_fail . . . . . . . . . . . . lmtl_loadshare_granularity . . . local_maintenance . . . . . . . low_sig_thresh . . . . . . . . . lta_alarm_range . . . . . . . . max_gprs_ts_per_carrier . . . . max_ms_dl_buffer . . . . . . . max_ms_dl_rate . . . . . . . . max_number_of_sdcchs . . . . max_pagenum_per_sec. . . . . max_q_length_channel . . . . . max_q_length_sdcch . . . . . . max_retran. . . . . . . . . . . max_rst_ckt_timer_exps . . . . max_tx_bts . . . . . . . . . . . max_tx_ms . . . . . . . . . . . mb_preference . . . . . . . . . mb_tch_congest_thres . . . . . missing_rpt . . . . . . . . . . mmi_cell_id_format . . . . . . mms_cat_enable . . . . . . . . mms_config_type . . . . . . . . ms_distance_allowed . . . . . . ms_max_range . . . . . . . . . ms_p_con_ack . . . . . . . . . ms_p_con_interval . . . . . . . ms_power_control_allowed. . . ms_power_offset . . . . . . . . ms_txpwr_max_cch. . . . . . . ms_txpwr_max_cell. . . . . . . ms_txpwr_max_def . . . . . . . ms_txpwr_max_inner . . . . . . msc_bss_overload_allowed . . . msc_preference . . . . . . . . msc_qt . . . . . . . . . . . . . msc_release . . . . . . . . . . mspwr_alg . . . . . . . . . . . mtbr_downgrade_enabled . . . mtl_loadshare_granularity . . . multiband_reporting . . . . . . nacc_enabled . . . . . . . . .
x
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-499 6-500 6-502 6-504 6-506 6-508 6-510 6-512 6-514 6-515 6-516 6-517 6-518 6-519 6-520 6-521 6-524 6-526 6-528 6-529 6-532 6-533 6-534 6-536 6-538 6-539 6-541 6-542 6-544 6-545 6-547 6-548 6-553 6-555 6-556 6-557 6-558 6-559 6-561 6-563 6-565 6-567 6-569 6-571 6-573 6-574 6-577 6-579 6-581 6-582 6-583 6-585 6-587 6-588 6-589 6-590 6-591 6-593
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
n_avg_i . . . . . . . . . . . . . ncc_of_plmn_allowed. . . . . . nccr_enabled. . . . . . . . . . nccrOpt . . . . . . . . . . . . neighbor_journal . . . . . . . . network_control_order . . . . . new_calls_hr . . . . . . . . . . ni . . . . . . . . . . . . . . . ns_alive_retries . . . . . . . . ns_block_retries . . . . . . . . ns_unblock_retries . . . . . . . nsei . . . . . . . . . . . . . . num_audit_retries . . . . . . . num_emerg_access . . . . . . num_emerg_rejected . . . . . . num_emerg_tch_kill . . . . . . num_emerg_term_sdcch . . . . num_gbl_dl_thrput_samples . . num_gbl_ul_thrput_samples . . number_of_preferred_cells . . . number_sdcchs_preferred . . . opc . . . . . . . . . . . . . . . option_alg_a5_1 . . . . . . . . option_alg_a5_2 . . . . . . . . option_alg_a5_3 . . . . . . . . option_alg_a5_4 . . . . . . . . option_alg_a5_5 . . . . . . . . option_alg_a5_6 . . . . . . . . option_alg_a5_7 . . . . . . . . option_preempt . . . . . . . . outer_zone_usage_level . . . . override_intra_bss_pre_transfer pbgt_mode . . . . . . . . . . . pccch_enabled . . . . . . . . . pccchOpt. . . . . . . . . . . . pcr_enable . . . . . . . . . . . pcr_n1 . . . . . . . . . . . . . pcr_n2 . . . . . . . . . . . . . pcu_redundancy . . . . . . . . percent_traf_cs. . . . . . . . . persistence_level. . . . . . . . pfm_sig_enabled . . . . . . . . phase_lock_gclk . . . . . . . . phase_lock_retry . . . . . . . . phase2_classmark_allowed. . . phase2_resource_ind_allowed . pic_error_clr_thresh . . . . . . pic_error_gen_thresh. . . . . . pic_error_inc . . . . . . . . . . pool_gproc_preemption . . . . poor_initial_assignment . . . . pow_inc_step_size_dl . . . . . . pow_inc_step_size_ul . . . . . . pow_red_step_size_dl . . . . . pow_red_step_size_ul . . . . . power_save_enable . . . . . . prach_max_retran . . . . . . . prach_s . . . . . . . . . . . .
68P02901W23-S Nov 2009
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-594 6-595 6-597 6-598 6-599 6-601 6-603 6-604 6-606 6-607 6-608 6-609 6-610 6-611 6-612 6-613 6-614 6-615 6-616 6-617 6-619 6-621 6-623 6-624 6-625 6-626 6-627 6-628 6-629 6-630 6-632 6-633 6-634 6-635 6-637 6-638 6-639 6-640 6-641 6-643 6-644 6-646 6-648 6-649 6-650 6-652 6-653 6-654 6-655 6-656 6-657 6-658 6-660 6-662 6-664 6-665 6-666 6-667
xi
Contents
prach_tx_int . . . . . . . . . . . . . . . primary_pcu . . . . . . . . . . . . . . . prioritize_microcell . . . . . . . . . . . priority_class. . . . . . . . . . . . . . . protect_last_ts . . . . . . . . . . . . . . prp_capacity_opt . . . . . . . . . . . . . prp_fanout_mode. . . . . . . . . . . . . prpThptOpt . . . . . . . . . . . . . . . prr_aggr_factor . . . . . . . . . . . . . psi_trau_fill_frames_threshold . . . . . . Pw_Save_SwitchOpt . . . . . . . . . . . pwr_handover_allowed . . . . . . . . . . pwrc . . . . . . . . . . . . . . . . . . . qosP2Opt . . . . . . . . . . . . . . . . qos_mbr_enabled . . . . . . . . . . . . qos_mtbr_be_dl . . . . . . . . . . . . . qos_mtbr_be_ul . . . . . . . . . . . . . qos_mtbr_bg_dl . . . . . . . . . . . . . qos_mtbr_bg_ul . . . . . . . . . . . . . qos_mtbr_i1_dl . . . . . . . . . . . . . . qos_mtbr_i1_ul . . . . . . . . . . . . . . qos_mtbr_i2_dl . . . . . . . . . . . . . . qos_mtbr_i2_ul . . . . . . . . . . . . . . qos_mtbr_i3_dl . . . . . . . . . . . . . . qos_mtbr_i3_ul . . . . . . . . . . . . . . qsearch_c . . . . . . . . . . . . . . . . qsearch_c_initial . . . . . . . . . . . . . qsearch_i. . . . . . . . . . . . . . . . . qsearch_p . . . . . . . . . . . . . . . . queue_management_information. . . . . ra_color . . . . . . . . . . . . . . . . . ra_reselect_hysteresis . . . . . . . . . . rac . . . . . . . . . . . . . . . . . . . . rach_load_period . . . . . . . . . . . . . rach_load_threshold . . . . . . . . . . . rach_load_type . . . . . . . . . . . . . . radio_link_timeout . . . . . . . . . . . . rapid_pwr_down . . . . . . . . . . . . . rci_error_clr_thresh . . . . . . . . . . . rci_error_gen_thresh . . . . . . . . . . . rci_error_inc . . . . . . . . . . . . . . . reconfig_fr_to_hr . . . . . . . . . . . . . red_loss_daily . . . . . . . . . . . . . . red_loss_oos . . . . . . . . . . . . . . . red_loss_hourly . . . . . . . . . . . . . red_time_oos . . . . . . . . . . . . . . . red_loss_restore . . . . . . . . . . . . . reestablish_allowed . . . . . . . . . . . rel_tim_adv. . . . . . . . . . . . . . . . remote_loss_daily . . . . . . . . . . . . remote_loss_hourly. . . . . . . . . . . . remote_loss_oos . . . . . . . . . . . . . remote_loss_restore . . . . . . . . . . . remote_time_oos . . . . . . . . . . . . . red_time_restore . . . . . . . . . . . . . report_resource_tch_f_high_water_mark . report_resource_tch_f_low_water_mark . res_gprs_pdchs . . . . . . . . . . . . .
xii
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-669 6-671 6-673 6-674 6-675 6-677 6-678 6-679 6-680 6-681 6-682 6-683 6-685 6-687 6-688 6-689 6-690 6-691 6-692 6-693 6-694 6-695 6-696 6-697 6-698 6-699 6-700 6-702 6-704 6-706 6-707 6-709 6-711 6-713 6-715 6-717 6-718 6-720 6-721 6-722 6-723 6-724 6-725 6-726 6-727 6-728 6-729 6-730 6-732 6-734 6-735 6-736 6-737 6-738 6-739 6-740 6-742 6-744
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
res_ts_less_one_carrier. . . . . rf_res_ind_period. . . . . . . . rpd_offset . . . . . . . . . . . rpd_period . . . . . . . . . . . rpd_trigger. . . . . . . . . . . rpt_bad_qual_no_mr . . . . . . rsl_lcf_congestion_thi . . . . . rsl_lcf_congestion_tlow. . . . . rtf_path_enable . . . . . . . . rxlev_access_min. . . . . . . . rxlev_dl_ho . . . . . . . . . . . rxlev_dl_pc . . . . . . . . . . . rxlev_dl_zone. . . . . . . . . . rxlev_min_def . . . . . . . . . rxlev_ul_ho . . . . . . . . . . . remote_time_restore . . . . . . rxlev_ul_zone. . . . . . . . . . rxqual_dl_ho . . . . . . . . . . rxqual_dl_pc . . . . . . . . . . rxqual_ul_ho . . . . . . . . . . rxqual_ul_pc . . . . . . . . . . sap_audit_type . . . . . . . . . sap_device_type . . . . . . . . sap_end_time . . . . . . . . . sap_interval . . . . . . . . . . sap_start_time . . . . . . . . . sccp_bssap_mgt . . . . . . . . scr_enabled . . . . . . . . . . sdcch_ho . . . . . . . . . . . . sdcch_need_high_water_mark . sdcch_need_low_water_mark. . sdcch_tch_band_reassign_delay sdcch_timer_ho . . . . . . . . search_prio_3g . . . . . . . . . second_asgnmnt . . . . . . . . secondary_freq_type . . . . . . serving_band_reporting . . . . sgsn_release . . . . . . . . . . sig_lnk_tst_allow . . . . . . . . slip_loss_daily . . . . . . . . . slip_loss_hourly . . . . . . . . slip_loss_oos . . . . . . . . . . slip_loss_restore . . . . . . . . smg_gb_vers . . . . . . . . . . sms_dl_allowed . . . . . . . . sms_tch_chan . . . . . . . . . sms_ul_allowed . . . . . . . . ss7_mode . . . . . . . . . . . ssm_critical_overload_threshold ssm_normal_overload_threshold ssp_burst_delay . . . . . . . . ssp_burst_limit . . . . . . . . . stat_interval . . . . . . . . . . stop_dri_tx_enable . . . . . . . stp_pc . . . . . . . . . . . . . stp_pc_enabled. . . . . . . . . stream_downgrade_enabled . . streaming_enabled . . . . . . .
68P02901W23-S Nov 2009
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-746 6-748 6-749 6-750 6-751 6-753 6-755 6-756 6-757 6-758 6-760 6-762 6-764 6-766 6-768 6-770 6-771 6-773 6-775 6-777 6-779 6-781 6-782 6-783 6-784 6-785 6-786 6-787 6-788 6-790 6-792 6-794 6-795 6-797 6-798 6-800 6-802 6-803 6-804 6-805 6-806 6-807 6-808 6-809 6-810 6-811 6-813 6-814 6-816 6-818 6-819 6-820 6-821 6-822 6-823 6-824 6-825 6-826
xiii
Contents
surround_cell . . . . . . . . . sw_pdtch_priority . . . . . . . sw_ts_less_one_carrier . . . . . swfm_enable . . . . . . . . . . switch_gprs_pdchs . . . . . . . sync_loss_daily . . . . . . . . . sync_loss_hourly . . . . . . . . sync_loss_oos . . . . . . . . . sync_loss_restore . . . . . . . sync_time_oos . . . . . . . . . sync_time_restore . . . . . . . t_avg_t . . . . . . . . . . . . . t_avg_w . . . . . . . . . . . . tch_busy_critical_threshold . . tch_busy_norm_threshold . . . tch_congest_prevent_thres . . . tch_flow_control . . . . . . . . tch_full_need_low_water_mark . tch_usage_threshold . . . . . . tdd_qoffset . . . . . . . . . . . td_enabled . . . . . . . . . . . tdm_switch. . . . . . . . . . . tdm_ts_blocks . . . . . . . . . temporary_offset . . . . . . . . thp_be_weight . . . . . . . . . thp_bg_weight . . . . . . . . . thp_i2_weight . . . . . . . . . thp_i3_weight . . . . . . . . . thp_stream_weight . . . . . . . threshold. . . . . . . . . . . . timing_advance_period. . . . . tlli_blk_coding . . . . . . . . . trace_msgs_after_ho . . . . . . trace_msgs_before_ho . . . . . trunk_critical_threshold . . . . trunk_major_threshold . . . . . ts_alloc_flag . . . . . . . . . . ts_in_usf_active . . . . . . . . tsc_update_method . . . . . . tx_integer . . . . . . . . . . . tx_power_cap . . . . . . . . . u_rxlev_dl_ih . . . . . . . . . . u_rxlev_dl_p . . . . . . . . . . u_rxlev_ul_ih . . . . . . . . . . u_rxlev_ul_p . . . . . . . . . . u_rxqual_dl_p . . . . . . . . . u_rxqual_dl_p_hr . . . . . . . . u_rxqual_ul_p . . . . . . . . . u_rxqual_ul_p_hr . . . . . . . . ul_audio_lev_offset . . . . . . . ul_rxlev_ho_allowed . . . . . . ul_rxqual_ho_allowed . . . . . umts_band_preferred . . . . . umts_cpich_ec_no_min . . . . . umts_cpich_rscp_min . . . . . unequipped_circuit_allowed . . use_bcch_for_gprs . . . . . . . use_derived_ho_power . . . . .
xiv
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6-827 6-829 6-830 6-832 6-833 6-835 6-836 6-837 6-838 6-839 6-840 6-841 6-842 6-844 6-845 6-846 6-847 6-849 6-850 6-851 6-852 6-853 6-854 6-855 6-857 6-858 6-859 6-860 6-861 6-862 6-863 6-865 6-866 6-867 6-868 6-869 6-870 6-872 6-873 6-875 6-877 6-879 6-881 6-883 6-885 6-887 6-889 6-891 6-893 6-895 6-896 6-898 6-900 6-901 6-902 6-903 6-905 6-906
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
use_neighbor_pbgt_hreqave . . volume_control_type . . . . . . wait_for_reselection . . . . . . wait_indication_parameters . . worse_neighbor_ho . . . . . . zone_ho_hyst . . . . . . . . . . zone_pingpong_count . . . . . zone_pingpong_preferred_zone
. . . . . . . .
. . . . . . . .
. . . . . . . .
Contents
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
6-907 6-908 6-910 6-911 6-913 6-914 6-916 6-917
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-2 7-3 7-5 7-6 7-7 7-8 7-9 7-10 7-11 7-12 7-13 7-14 7-16 7-18 7-20 7-22 7-23 7-24 7-25 7-26 7-28 7-30 7-32 7-34 7-36 7-38 7-39 7-40 7-41 7-42 7-43 7-44 7-45 7-46 7-47 7-48 7-49 7-50 7-52 7-54 7-55 7-56 7-57 7-58 7-59 7-60 7-62
Chapter 7: Timer parameters add_access_class . . . . . assign_successful . . . . auto_dl_dur . . . . . . . bcch_info. . . . . . . . . bep_period . . . . . . . . bep_period2 . . . . . . . bounce_protect_cong_tmr bounce_protect_qual_tmr bsc_audit. . . . . . . . . bsc_audit_response . . . bss_overload_control . . . bssgp_fc_period_c . . . . bssgp_t1_timer . . . . . . bssgp_t2_timer . . . . . . bssgp_t4_timer . . . . . . bssgp_t5_timer . . . . . . bssgp_t6_timer . . . . . . bssgp_t8_timer . . . . . . bssmap_t1 . . . . . . . . bssmap_t4 . . . . . . . . bssmap_t7 . . . . . . . . bssmap_t8 . . . . . . . . bssmap_t10 . . . . . . . bssmap_t11 . . . . . . . bssmap_t13 . . . . . . . bssmap_t19 . . . . . . . bssmap_t20 . . . . . . . bssmap_tqho . . . . . . . bts_audit . . . . . . . . . bts_audit_response. . . . bts_escalation . . . . . . carrier_free_immediate . cbch_1 . . . . . . . . . . cbch_2 . . . . . . . . . . cbch_3 . . . . . . . . . . channel_act . . . . . . . channel_teardown . . . . cipher_comp_ms . . . . . ciphering_successful . . . circuit_reset_ack . . . . . clear_cmd_ext_ho . . . . clear_command . . . . . dealloc_inact . . . . . . . delay_dl_rel_dur . . . . . delay_ul_rel_dur . . . . . downlink_sync_timer . . . dynet_retry_time . . . . .
68P02901W23-S Nov 2009
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xv
Contents
early_classmark_delay . . . . emerg_reserved . . . . . . . ext_ho_allocation. . . . . . . ext_rtry_cand_prd . . . . . . flow_control_t1. . . . . . . . flow_control_t2. . . . . . . . gbl_thrput_period . . . . . . gprs_penalty_time . . . . . . gprs_smg30_t3192 . . . . . . gprs_t3168 . . . . . . . . . . gprs_t3192 . . . . . . . . . . handover_recognized_period . ho_ack . . . . . . . . . . . . ho_allocation . . . . . . . . . ho_complete . . . . . . . . . ho_request . . . . . . . . . . ho_successful . . . . . . . . hop_count_timer . . . . . . . initial_sync_timer . . . . . . lb_int_bssmap_t4 . . . . . . . lb_int_bssmap_t13 . . . . . . lb_int_clear_command . . . . lb_int_sccp_released . . . . . lb_int_sccp_tconn_est . . . . lb_int_sccp_tiar . . . . . . . lb_int_sccp_tias . . . . . . . lb_int_sccp_trel . . . . . . . lb_int_spi. . . . . . . . . . . lb_int_ss7_l2_t1 . . . . . . . lb_int_ss7_l2_t2 . . . . . . . lb_int_ss7_l2_t3 . . . . . . . lb_int_ss7_l2_t4 . . . . . . . lb_int_ss7_l2_t5 . . . . . . . lb_int_ss7_l2_t6 . . . . . . . lb_int_ss7_l2_t7 . . . . . . . lb_int_ss7_l3_t1 . . . . . . . lb_int_ss7_l3_t2 . . . . . . . lb_int_ss7_l3_t4 . . . . . . . lb_int_ss7_l3_t5 . . . . . . . lb_int_ss7_l3_t12 . . . . . . . lb_int_ss7_l3_t13 . . . . . . . lb_int_ss7_l3_t14 . . . . . . . lb_int_ss7_l3_t17 . . . . . . . lb_int_ss7_l3_t22 . . . . . . . lb_int_ss7_l3_t23 . . . . . . . lb_int_ss7_slt_t1 . . . . . . . lb_int_t_stat_info . . . . . . . lcs_perf_location . . . . . . . lcs_segmentation. . . . . . . lcs_supervision . . . . . . . . mode_modify . . . . . . . . . mode_rr_modify_ack . . . . . ms_sapi3_est . . . . . . . . . nc_non_drx_period . . . . . . nc_reporting_period_i . . . . nc_reporting_period_t . . . . neighbor_report_timer . . . . ns_alive_timer . . . . . . . .
xvi
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-64 7-65 7-66 7-67 7-68 7-69 7-70 7-71 7-72 7-73 7-74 7-75 7-77 7-78 7-79 7-80 7-81 7-82 7-83 7-85 7-86 7-87 7-88 7-89 7-90 7-91 7-92 7-93 7-94 7-95 7-96 7-97 7-98 7-99 7-100 7-101 7-102 7-103 7-104 7-105 7-106 7-107 7-108 7-109 7-111 7-112 7-113 7-114 7-115 7-116 7-117 7-118 7-120 7-122 7-124 7-125 7-127 7-128
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
ns_block_timer . . . . . . . ns_reset_period . . . . . . ns_reset_timer . . . . . . . ns_test_timer. . . . . . . . pccch_drx_timer_max . . . penalty_time . . . . . . . . phase_lock_duration . . . . psi1_repeat_period . . . . . radio_chan_released . . . . red_psp_audit_tmr . . . . . register_exp . . . . . . . . rf_chan_rel_ack . . . . . . rr_ny1_rep . . . . . . . . . rr_t3103 . . . . . . . . . . rr_t3101 . . . . . . . . . . rr_t3105 . . . . . . . . . . rr_t3109 . . . . . . . . . . rr_t3111_sd . . . . . . . . rr_t3111_tch . . . . . . . . rr_t3212 . . . . . . . . . . rsl_congestion_alarm_timer rtry_cand_prd . . . . . . . sacch_info . . . . . . . . . sccp_released . . . . . . . sccp_tconn_est . . . . . . . sccp_tiar . . . . . . . . . . sccp_tias . . . . . . . . . . sccp_trel . . . . . . . . . . sm_audit_response . . . . . spi . . . . . . . . . . . . . ss7_l2_t1 . . . . . . . . . . ss7_hsp_l2_t1 . . . . . . . ss7_l2_t1 . . . . . . . . . . ss7_l2_t2 . . . . . . . . . . ss7_l2_t3 . . . . . . . . . . ss7_l2_t4 . . . . . . . . . . ss7_l2_t5 . . . . . . . . . . ss7_l2_t6 . . . . . . . . . . ss7_l2_t7 . . . . . . . . . . ss7_l3_t1 . . . . . . . . . . ss7_l3_t2 . . . . . . . . . . ss7_l3_t4 . . . . . . . . . . ss7_l3_t5 . . . . . . . . . . ss7_l3_t12 . . . . . . . . . ss7_l3_t13 . . . . . . . . . ss7_l3_t14 . . . . . . . . . ss7_l3_t17 . . . . . . . . . ss7_l3_t22 . . . . . . . . . ss7_l3_t23 . . . . . . . . . ss7_slt_t1 . . . . . . . . . start_ack . . . . . . . . . . static_sync_timer. . . . . . stop_dri_tx_time . . . . . . t_stat_info . . . . . . . . . uplink_sync_timer . . . . . valid_candidate_period. . . zone_pingpong_disable_win zone_pingpong_enable_win
68P02901W23-S Nov 2009
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-129 7-130 7-132 7-133 7-135 7-137 7-139 7-140 7-142 7-143 7-144 7-145 7-146 7-148 7-150 7-151 7-153 7-155 7-157 7-159 7-161 7-162 7-164 7-166 7-167 7-168 7-170 7-171 7-172 7-173 7-175 7-177 7-179 7-181 7-183 7-185 7-186 7-187 7-189 7-190 7-191 7-192 7-193 7-194 7-195 7-196 7-197 7-198 7-200 7-202 7-203 7-204 7-206 7-207 7-208 7-210 7-211 7-212
xvii
Contents
Chapter 8: Device/Function parameters Device and function database parameters antenna_select . . . . . . . . . . . . . . ber_oos_mon_period . . . . . . . . . . . ber_restore_mon_period . . . . . . . . . bsc_cbc_operator . . . . . . . . . . . . cabinet_type . . . . . . . . . . . . . . . cavity . . . . . . . . . . . . . . . . . . cbc_operator . . . . . . . . . . . . . . . cell_zone . . . . . . . . . . . . . . . . . chan_alloc_priority . . . . . . . . . . . . cic_block_thresh . . . . . . . . . . . . . clkx0 . . . . . . . . . . . . . . . . . . . clkx1 . . . . . . . . . . . . . . . . . . . clkx2 . . . . . . . . . . . . . . . . . . . combiner_address . . . . . . . . . . . . combiner_id . . . . . . . . . . . . . . . combining_type . . . . . . . . . . . . . dri_density . . . . . . . . . . . . . . . . ext_pdchs . . . . . . . . . . . . . . . . ext_timeslots . . . . . . . . . . . . . . . fm_cell_type . . . . . . . . . . . . . . . frequency_type. . . . . . . . . . . . . . hdsl_modem_setting . . . . . . . . . . . hdsl_oos_mon_period. . . . . . . . . . . hdsl_restore_mon_period. . . . . . . . . ias_connected . . . . . . . . . . . . . . int_antenna . . . . . . . . . . . . . . . int_hdsl_modem . . . . . . . . . . . . . lapd_k . . . . . . . . . . . . . . . . . . lapd_n200 . . . . . . . . . . . . . . . . lapd_t200_timer . . . . . . . . . . . . . max_cbls . . . . . . . . . . . . . . . . . max_dris . . . . . . . . . . . . . . . . . max_gsls . . . . . . . . . . . . . . . . . max_mtls . . . . . . . . . . . . . . . . . mms_priority . . . . . . . . . . . . . . . msc_mms_id . . . . . . . . . . . . . . . msi_type . . . . . . . . . . . . . . . . . n391 . . . . . . . . . . . . . . . . . . . n392 . . . . . . . . . . . . . . . . . . . n393 . . . . . . . . . . . . . . . . . . . nbit . . . . . . . . . . . . . . . . . . . ne_id . . . . . . . . . . . . . . . . . . . opto_reporting . . . . . . . . . . . . . . pkt_radio_type . . . . . . . . . . . . . . pref_rtf_id . . . . . . . . . . . . . . . . rsl_rate. . . . . . . . . . . . . . . . . . rtf_ds0_count . . . . . . . . . . . . . . sd_load. . . . . . . . . . . . . . . . . . sd_priority . . . . . . . . . . . . . . . . shared_timeslots . . . . . . . . . . . . . slot . . . . . . . . . . . . . . . . . . . . start_ts . . . . . . . . . . . . . . . . . . t391 . . . . . . . . . . . . . . . . . . . t392 . . . . . . . . . . . . . . . . . . . tcu_port . . . . . . . . . . . . . . . . .
xviii
presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-2 8-6 8-8 8-10 8-12 8-13 8-17 8-18 8-19 8-21 8-22 8-24 8-26 8-28 8-30 8-31 8-32 8-34 8-36 8-38 8-40 8-42 8-44 8-46 8-48 8-50 8-51 8-52 8-53 8-55 8-57 8-59 8-60 8-62 8-63 8-65 8-66 8-67 8-69 8-70 8-71 8-72 8-73 8-74 8-76 8-79 8-80 8-81 8-83 8-85 8-86 8-87 8-88 8-89 8-90 8-91
68P02901W23-S Nov 2009
Contents
tdOpt. . . . . . . . . . transcoding_capability . tru_id . . . . . . . . . trx_pwr_red . . . . . .
68P02901W23-S Nov 2009
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
8-93 8-94 8-95 8-96
xix
Contents
xx
68P02901W23-S Nov 2009
List of Figures
List of Figures ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Figure Figure Figure Figure
2-1: 2-2: 2-3: 2-4:
Remote Transcoder (RXCDR) devices and functions . BSC and InCell BTS . . . . . . . . . . . . . . . . . M-Cell and Horizonmacro equipage hierarchy chart . GPRS PCU devices and functions . . . . . . . . . .
68P02901W23-S Nov 2009
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
2-7 2-8 2-9 2-10
xxi
List of Figures
xxii
68P02901W23-S Nov 2009
List of Tables
List of Tables ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table Table
1-1: Commands status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2: Database parameters status . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3: Task oriented MMI commands . . . . . . . . . . . . . . . . . . . . . . . . . 1-4: MMI command availability by location . . . . . . . . . . . . . . . . . . . . . 1-5: MMI command availability by SYSGEN mode . . . . . . . . . . . . . . . . . . 1-6: Device Indices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7: Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1: Device literals and descriptions . . . . . . . . . . . . . . . . . . . . . . . . . 3-2: Device and command relationship . . . . . . . . . . . . . . . . . . . . . . . 3-3: Device ID requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4: Function related commands. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5: Function ID requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6: Valid slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7: Equip/Unequip command matrix . . . . . . . . . . . . . . . . . . . . . . . . 3-8: Alarm devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9: add_cell command prompts . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10: add_conn valid ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11: Neighbor frequency and number with an EGSM or PGSM source cell . . . . 3-12: Neighbor frequency and number with DCS1800 source cell . . . . . . . . . . 3-13: Prompted Parameters for TD-SCDMA Neighbors . . . . . . . . . . . . . . . 3-14: add_neighbor command prompts for GSM BA BCCH and SACCH neighbors. 3-15: add_neighbor command prompts for UTRAN BCCH and SACCH neighbors . 3-16: add_neighbor command prompts for Blind Search neighbors. . . . . . . . . 3-17: Codec Mode Values / Rates . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18: Full Rate attribute values for chg_acs_params command. . . . . . . . . . . 3-19: Half Rate attribute values for chg_acs_params command . . . . . . . . . . 3-20: Full Rate prompts for the chg_acs_params command . . . . . . . . . . . . 3-21: Half Rate prompts for chg_acs_params command . . . . . . . . . . . . . . 3-22: Device scheduling defaults . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23: RXCDR default DTE addresses. . . . . . . . . . . . . . . . . . . . . . . . . 3-24: BSC default DTE addresses . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25: EAS default alarm strings . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26: Baseband and Synthesizer frequency hopping restrictions . . . . . . . . . . 3-27: chg_hop_params prompts . . . . . . . . . . . . . . . . . . . . . . . . . . 3-28: Cell frequencies/mobile allocation . . . . . . . . . . . . . . . . . . . . . . . 3-29: Restrictions on related commands . . . . . . . . . . . . . . . . . . . . . . . 3-30: SMS special characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31: copy_path command prompts . . . . . . . . . . . . . . . . . . . . . . . . . 3-32: mod_conn valid ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33: Operational states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-34: Administrative states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35: Device states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36: Reason codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37: trace_call prompts and values for a GSM Trace and GPRS Trace. . . . . . . 5-1: Counter and gauge statistic type prompts . . . . . . . . . . . . . . . . . . .
68P02901W23-S Nov 2009
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-2 1-8 1-18 1-28 1-32 1-40 1-42 3-3 3-5 3-9 3-15 3-16 3-17 3-18 3-20 3-26 3-34 3-36 3-36 3-40 3-44 3-46 3-47 3-66 3-67 3-68 3-69 3-70 3-78 3-98 3-98 3-104 3-130 3-133 3-134 3-134 3-154 3-188 3-443 3-527 3-527 3-528 3-529 3-558 5-11 xxiii
List of Tables
Table 5-2: Normal and weighted distribution statistic type prompts . . . . . . . . . . . . . . Table 6-1: alt_qual_proc=0 parameter values. . . . . . . . . . . . . . . . . . . . . . . . . Table 6-2: alt_qual_proc=1 parameter values. . . . . . . . . . . . . . . . . . . . . . . . . Table 6-3: Base Station Identity Code - Hexadecimal Values . . . . . . . . . . . . . . . . . . Table 6-4: Base Station Identity Code - Decimal Values . . . . . . . . . . . . . . . . . . . . Table 6-5: CTU2 values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-6: Cabinet antenna connector maximum output power (Watts) . . . . . . . . . . . . Table 6-7: Values for PGSM, EGSM, DCS1800 and PCS1900 M-Cellmicro sites . . . . . . . . Table 6-8: Values for DCS1800 and M-Cellaccess, sites . . . . . . . . . . . . . . . . . . . . Table 6-9: Sample output power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-10: Values for barring classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-11: Maximum mobile power level for PGSM, EGSM and GSM850 cells . . . . . . . . Table 6-12: Maximum mobile power level for DCS1800 cells . . . . . . . . . . . . . . . . . Table 6-13: Maximum mobile power level for PCS1900 cells. . . . . . . . . . . . . . . . . . Table 6-14: Modes for gprs_network_operation_mode . . . . . . . . . . . . . . . . . . . Table 6-15: Max MS power level for PGSM and EGSM. . . . . . . . . . . . . . . . . . . . . Table 6-16: Max MS power level for DCS1800 and PCS1900 cells . . . . . . . . . . . . . . . Table 6-17: Max MS power level for class 3 mobiles . . . . . . . . . . . . . . . . . . . . . . Table 6-18: Max MS power level for PGSM and EGSM cells . . . . . . . . . . . . . . . . . . Table 6-19: Max MS power level for DCS1800 and PCS1900 cells . . . . . . . . . . . . . . . Table 6-20: Max MS level for class 3 mobiles . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-21: Prompted parameters for Dual Band Cell use . . . . . . . . . . . . . . . . . . . Table 6-22: CTU2 values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 6-23: Cabinet antenna connector maximum output power (Watts) . . . . . . . . . . . . Table 6-24: Values for PGSM, EGSM, DCS1800 and PCS1900 sites . . . . . . . . . . . . . . Table 6-25: ms_max_range values for normal cells . . . . . . . . . . . . . . . . . . . . . . Table 6-26: ms_max_range values for Extended Range cells . . . . . . . . . . . . . . . . . Table 6-27: Maximum mobile power level for PGSM and EGSM cells . . . . . . . . . . . . . Table 6-28: Maximum mobile power level for DCS1800 cells . . . . . . . . . . . . . . . . . Table 6-29: Maximum mobile power level for PCS1900 cells. . . . . . . . . . . . . . . . . . Table 6-30: Bit mapping of ncc_of_plmn_allowed. . . . . . . . . . . . . . . . . . . . . . . Table 6-31: Configurations for network_control_order . . . . . . . . . . . . . . . . . . . . Table 6-32: Values for prach_tx_int representing number of frame slots . . . . . . . . . . . Table 6-33: qsearch_p attribute values below threshold. . . . . . . . . . . . . . . . . . . . Table 6-34: qsearch_p attribute values above threshold. . . . . . . . . . . . . . . . . . . . Table 6-35: Example cell configurations for rach_load_threshold . . . . . . . . . . . . . . Table 7-1: Impermissible combinations of psi1_repeat_period and bs_pbcch_blks . . . . . Table 8-1: Cabinets/Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 8-2: Permitted CAB modifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 8-3: Values for PGSM, EGSM and PCS 1900 sites . . . . . . . . . . . . . . . . . . . . Table 8-4: Values for DCS 1800 sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 8-5: Values for PGSM and EGSM M-Cellmicro sites . . . . . . . . . . . . . . . . . . . Table 8-6: Values for DCS 1800 for M-CELL6, HorizonMacro, HorizonMacro2, Horizon2micro and Horizon2mini sites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Table 8-7: Values for DCS 1800 and PCS 1900 M-Cellmicro sites . . . . . . . . . . . . . . .
xxiv
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-11 6-26 6-27 6-95 6-95 6-115 6-116 6-116 6-117 6-117 6-141 6-333 6-333 6-334 6-335 6-370 6-370 6-370 6-399 6-399 6-399 6-438 6-550 6-551 6-551 6-566 6-566 6-575 6-575 6-576 6-596 6-601 6-670 6-705 6-705 6-715 7-141 8-13 8-15 8-97 8-98 8-99
. .
8-99 8-100
68P02901W23-S Nov 2009
About This Manual
Technical Description: BSS Command Reference ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
What is covered in this manual? This manual is a reference document containing descriptions of the Man-Machine Interface (MMI) commands and parameters used within the Motorola GSM system. This document supports the following Motorola BSS equipment: BTS4, BTS5, BTS6, BSSC, BSSC2, ExCell 4, ExCell 6, TopCell, M-Cell TM2, M-Cell6, M-Cellmicro, M-Cellcity, Horizonmicro, Horizoncompact, M-Cellaccess, Horizonmacro, Horizon II macro, Horizonmicro2, Horizoncompact2, Horizon II mini and Packet Control Unit (PCU). The BSS Command Reference manual is presented in three volumes: •
Volume 1: contains Chapters 1 to 5 providing descriptions of BSS Commands.
•
Volume 2: contains Chapter 6 providing descriptions of CM parameters used with BSS Commands.
•
Volume 3: contains Chapters 7 and 8 providing descriptions of Timer parameters and Device/Function parameters used with BSS Commands.
Each volume contains a full Contents list and an Index for the whole of the manual.
Background information Lists of the additions, changes, and deletions to commands and parameters introduced by the particular software release version in this issue of the BSS Command Reference manual, is provided in Version updates due to this software release on page 1-2 of Volume 1. A customer reference form for recording local settings of new/modified GSR9 parameters is provided in GSR9 new/modified parameters user reference form on page 1-10 also of Volume 1.
68P02901W23-S Nov 2009
1
Revision history
Revision history ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The following sections show the revision status of this document.
Version information The following table lists the supported versions of this manual in order of issue: Issue
Remarks
Date of issue
Q
Sep 2004
GSM Software Release 7 Half Rate
R
Nov 2006
GSM Software Release 8 GMR-02
S
Apr 2008
GSM Software Release 9
S
Nov 2009
GSM Software Release FP 1
Resolution of Service Requests The following Service Requests are resolved in this document: Service Request
2
CMBP Number
Remarks
2208880
Amended valid range of bssgp_cbl_bit parameter.
2206085
Modified the default value range in Table 6–2.
2217478
Added text under Values for band_preference_mode parameter.
2212460
Added Note to rci_error_gen_thresh parameter.
2248104
Modified default value for rtf_ds0_count parameter.
2288107
Amended Command Prompts Table for XBL device in Chapter 2.
2287328
Updated add_neighbor command in Chapter 3.
2308545
Updated the EMON commands information in Chapter 6.
2315460
Updated the Values section in handover_required_reject_switch parameter.
2322765
Updated max_tx_bts parameter in Chapter 6.
68P02901W23-S Nov 2009
Incorporation of Change Notices
Incorporation of Change Notices The following Change Notices (CN) are incorporated in this document: CN Date
CN Number
Title
NA
NA
NA
68P02901W23-S Nov 2009
3
General information
General information ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Purpose Motorola documents are intended to instruct and assist personnel in the operation, installation, and maintenance of the Motorola equipment and ancillary devices. It is recommended that all personnel engaged in such activities be properly trained by Motorola. Motorola disclaims all liability whatsoever, implied or expressed, for any risk of damage, loss or reduction in system performance arising directly or indirectly out of the failure of the customer, or anyone acting on the customer's behalf, to abide by the instructions, system parameters, or recommendations made in this document. These documents are not intended to replace the system and equipment training offered by Motorola. They can be used to supplement and enhance the knowledge gained through such training.
NOTE If this document was obtained when attending a Motorola training course, it is not updated or amended by Motorola. It is intended for TRAINING PURPOSES ONLY. If it was supplied under normal operational circumstances, to support a major software release, then Motorola automatically supplies corrections and posts on the Motorola customer website.
Cross references References made to external publications are shown in italics. Other cross references, emphasized in blue text in electronic versions, are active links to the references. This document is divided into numbered chapters that are divided into sections. Sections are not numbered, but are individually named at the top of each page, and are listed in the table of contents.
4
68P02901W23-S Nov 2009
Text conventions
Text conventions The following conventions are used in the Motorola documents to represent keyboard input text, screen output text, and special key sequences.
Input Characters typed in at the keyboard are shown like this sentence. Items of interest within a command appear like this sentence.
Output Messages, prompts, file listings, directories, utilities, and environmental variables that appear on the screen are shown like this sentence. Items of interest within a screen display appear like this sentence.
Special key sequences Special key sequences are represented as follows: CTRL-c or CTRL+C
Press the Ctrl and C keys at the same time.
CTRL-SHIFT-c or CTRL+SHIFT+C
Press the Ctrl, Shift, and C keys at the same time.
ALT-f or ALT+F
Press the Alt and F keys at the same time.
ALT+SHIFT+F11
Press the Alt, Shift and F11 keys at the same time.
¦
Press the pipe symbol key.
RETURN or ENTER
Press the Return or Enter key.
68P02901W23-S Nov 2009
5
Contacting Motorola
Contacting Motorola ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Motorola appreciates feedback from the users of our documents.
24–hour support If you have problems regarding the operation of your equipment, 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. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.
Questions and comments Send questions and comments regarding user documentation to the email address:
[email protected].
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):
6
•
The document type
•
The document title, part number, and revision character
•
The page number with the error
•
A detailed description of the error and if possible the proposed solution
68P02901W23-S Nov 2009
Security advice
Security advice ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Motorola systems and equipment provide security parameters that the operator configures based on their particular operating environment. Motorola recommends setting and using these parameters following industry recognized security practices. Consider protecting the confidentiality, integrity, and availability of information and assets. Assets include the ability to communicate, information about the nature of the communications, and information about the parties involved. In certain instances, Motorola makes specific recommendations regarding security practices. The implementation of these recommendations and final responsibility for the security of the system lies with the operator of the system. Contact the Customer Network Resolution Center (CNRC) for assistance. The 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 Office.
68P02901W23-S Nov 2009
7
Warnings, cautions, and notes
Warnings, cautions, and notes ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The following describes how warnings and cautions are used in this document and in all documents of this Motorola document set.
Warnings Warnings precede instructions that contain potentially hazardous situations. Warnings are used to alert the reader to possible hazards that could cause loss of life or physical injury. A warning has the following format:
WARNING Warning text and consequence for not following the instructions in the warning.
Cautions Cautions precede instructions and are used when there is a possibility of damage to systems, software, or individual items of equipment within a system. However, this damage presents no danger to personnel. A caution has the following format:
CAUTION Caution text and consequence for not following the instructions in the caution.
Notes A note means that there is a possibility of an undesirable situation or provides additional information to help the reader understand a topic or concept. A note has the following format:
NOTE Note text.
8
68P02901W23-S Nov 2009
Safety
Safety ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
General safety The following general safety guidelines apply to Motorola equipment: •
The power jack and mating plug of the power cable must meet International Electrotechnical Commission (IEC) safety standards.
NOTE Refer to Grounding Guideline for Cellular Radio Installations – 68P81150E62.
•
Power down or unplug the equipment before servicing.
•
Using non-Motorola parts for repair could damage the equipment or void warranty. Contact Motorola Warranty and Repair for service and repair instructions.
•
Portions of Motorola equipment may be damaged from exposure to electrostatic discharge. Use precautions to prevent damage.
Electromagnetic energy Relevant standards (USA and EC) applicable when working with RF equipment are: •
ANSI IEEE C95.1-1991, IEEE Standard for Safety Levels with Respect to Human Exposure to Radio Frequency Electromagnetic Fields, 3 kHz to 300 GHz.
•
Council recommendation of 12 July 1999 on the limitation of exposure of the general public to electromagnetic fields (0 Hz to 300 GHz) (1999/519/EC) and respective national regulations.
•
Directive 2004/40/EC of the European Parliament and of the Council of 29 April 2004 on the minimum health and safety requirements regarding the exposure of workers to the risks arising from physical agents (electromagnetic fields) (18th individual Directive within the meaning of Article 16(1) of Directive 89/391/EEC).
68P02901W23-S Nov 2009
9
CMM labeling and disclosure table
CMM labeling and disclosure table ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The People’s Republic of China requires that our products comply with China Management Methods (CMM) environmental regulations. (China Management Methods refers to the regulation Management Methods for Controlling Pollution by Electronic Information Products.) Two items are used to demonstrate compliance; the label and the disclosure table. The label is placed in a customer visible position on the product. •
Logo 1 means the product contains no substances in excess of the maximum concentration value for materials identified in the China Management Methods regulation.
•
Logo 2 means that the product may contain substances in excess of the maximum concentration value for materials identified in the China Management Methods regulation, and has an Environmental Friendly Use Period (EFUP) in years. The example shown uses 50 years.
Logo 1
Logo 2
The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic and Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP) will not leak or mutate causing environmental pollution or bodily injury from the use of the EIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain field-replaceable parts, such as battery modules, can have a different EFUP and are marked separately. The Disclosure table is intended only to communicate compliance with China requirements. It is not intended to communicate compliance with EU RoHS or any other environmental requirements.
10
68P02901W23-S Nov 2009
Caring for the environment
Caring for the environment ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The following information describes national or regional requirements for the disposal of Motorola supplied equipment and for the approved disposal of surplus packaging. Contact the Customer Network Resolution Center (CNRC) for assistance. The 24–hour telephone numbers are listed at https://mynetworksupport.motorola.com. Select Customer Network Resolution Center contact information. Alternatively if you do not have access to CNRC or the internet, contact the Local Motorola Office.
EU countries The following information is provided to enable regulatory compliance with the European Union (EU) directives and any amendments to these directives when using Motorola equipment in EU countries.
Disposal of Motorola equipment European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic Equipment (WEEE) Do not dispose of Motorola equipment in landfill sites. In the EU, Motorola in conjunction with a recycling partner ensures that equipment is collected and recycled according to the requirements of EU environmental law.
Disposal of surplus packaging European Parliament and Council Directive 94/62/EC Packaging and Packaging Waste Do not dispose of surplus packaging in landfill sites. In the EU, it is the individual recipient’s responsibility to ensure that packaging materials are collected and recycled according to the requirements of EU environmental law.
Non-EU countries In non-EU countries, dispose of Motorola equipment and all surplus packaging in accordance with national and regional regulations.
68P02901W23-S Nov 2009
11
Non-EU countries
Turkey Article 7 of the European Union (EU) Directive 2002/96/EC Waste Electrical and Electronic
Equipment (WEEE) The Government of Turkey requests a statement of conformity with the EEE regulation be provided with all electrical and electronic equipment. This statement of EEE conformity (in Turkish) is: EEE Yönetmeliğine Uygundur.
12
68P02901W23-S Nov 2009
Motorola document set
Motorola document set ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The Motorola document sets provide the information to operate, install, and maintain the Motorola equipment.
Ordering documents and CD-ROMs With internet access available, to view, download, or order documents (original or revised), visit the Motorola Lifecycles Customer web page at https://mynetworksupport.motorola.com, or contact your Motorola account representative. Without internet access available, order hard-copy documents or CD-ROMs from your Motorola Local Office or Representative. If Motorola changes the content of a document after the original printing date, Motorola publishes a new version with the same part number but a different revision character.
Document banner definitions A banner indicates that some information contained in the document is not yet approved for general customer use. A banner is oversized text on the bottom of the page, for example, PRELIMINARY — UNDER DEVELOPMENT.
Data encryption In order to avoid electronic eavesdropping, data passing between certain elements in the network is encrypted. In order to comply with the export and import requirements of particular countries, this encryption occurs at different levels. The encryption may be individually standardized or may not be present at all in some parts of the network in which it is normally implemented. The document set covers encryption as if fully implemented. Limitations on the encryption included in the particular software being delivered, are covered in the Release Notes that accompany the individual software release.
68P02901W23-S Nov 2009
13
Data encryption
14
68P02901W23-S Nov 2009
Chapter
1 Introduction to commands ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
This chapter provides an introduction to the Base Station System (BSS), Man Machine Interface (MMI) functions, commands, and parameters including SYSGEN modes of operation. The following topics are contained in this chapter: •
Version updates due to this software release on page 1-2: lists the commands and parameters that are created, changed, and deleted by this software release.
•
GSR9 new/modified parameters user reference form on page 1-10: provides a customer reference form for recording local settings of GSR9 parameters.
•
BSS MMI functions on page 1-15: provides an overview of BSS MMI functions for managing the network.
•
BSS task-oriented command usage on page 1-18: lists the MMI commands for performing BSS function related tasks.
•
Command/database parameter security levels on page 1-22: describes the command/database access security levels.
•
Command/database parameter types on page 1-23: describes the command/database parameter classification.
•
Commands to be used with caution on page 1-24: lists commands that cause a device to cycle and must be used with caution.
•
Parameters to be used with caution on page 1-25: lists parameters that cause a device to cycle and must be used with caution.
•
Entering MMI commands on page 1-26: provides guidelines on entering MMI commands and use of the correct syntax.
•
MMI command availability on page 1-28: lists MMI command availability by location and by SYSGEN mode.
•
GSM cell ID format on page 1-37: describes the two types of GSM cell ID format.
•
Indices on page 1-40: describes the indices for devices, including data array location, bin numbers, alarm thresholds, and EAS alarm table.
•
SYSGEN mode on page 1-43: describes the SYSGEN modes of working.
68P02901W23-S Nov 2009
1-1
Version updates due to this software release
Chapter 1: Introduction to commands
Version updates due to this software release ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
MMI commands and parameters that are new, modified, deleted, or renamed as a result of the introduction of software release GSR 9, are listed separately. For information about the features included in this software release, refer to Motorola manual System Information: GSM Overview (68P02901W01).
New, modified and deleted commands Table 1-1
Commands status
Feature {27508}
{27955A}
Command
Status
chg_cmd_level on page 3-94
New
chg_level on page 3-142
New
Login on page 3-438
New
Logout on page 3-441
New
add_nsvc on page 3-48
Modified
alarm_mode on page 3-52
Modified
assess on page 3-54
Modified
cage_audit on page 3-58
Modified
chg_audit_sched on page 3-76
Modified
chg_element on page 3-106
Modified
del_act_alarm on page 3-190
Modified
del_nsvc on page 3-202
Modified
device_audit on page 3-210
Modified
disp_bss on page 3-229
Modified
disp_element on page 3-272
Modified
disp_equipment on page 3-283
Modified
disp_mms_ts_usage on page 3-330
Modified
disp_nsvc on page 3-353
Modified
disp_processor on page 3-367
Modified
disp_traffic on page 3-394
Modified
equip on page 3-403
Modified
ins_device on page 3-423
Modified
lock_device on page 3-429
Modified Continued
1-2
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 1-1
Commands status (Continued)
Feature {27955A}
{22168}
{22169}
{22266}
{25423}
New, modified and deleted commands
Command
Status
mod_nsvc on page 3-445
Modified
modify_value on page 3-456
Modified
query_audits on page 3-472
Modified
reset_device on page 3-485
Modified
reset_site on page 3-492
Modified
site_audit on page 3-507
Modified
soft_reset on page 3-511
Modified
state on page 3-515
Modified
status_mode on page 3-530
Modified
unequip on page 3-570
Modified
unlock_device on page 3-581
Modified
ins_device on page 3-423
Modified
reset_device on page 3-485
Modified
add_conn on page 3-33
Modified
del_conn on page 3-195
Modified
mod_conn on page 3-442
Modified
chg_stat_prop on page 5-5
Modified
disp_enable_stat on page 5-12
Modified
disp_stat_prop on page 5-24
Modified
disp_stats on page 5-34
Modified
stat_mode on page 5-48
Modified
disp_version on page 3-399
Modified
disp_options on page 3-356 {25424}
chg_csfp on page 3-95
Modified
disp_csfp on page 3-263
Modified
disp_stat_prop on page 5-24
Modified
stat_mode on page 5-48
Modified
disp_equipment on page 3-283
Modified
equip on page 3-403
Modified
modify_value on page 3-456
Modified
unequip on page 3-570
Modified
{26811}
copy_cell on page 3-179
Modified
{27236}
diagnose_device on page 3-217
Modified
disp_cal_data on page 3-233
Modified
{25867}
{26481}
Continued
68P02901W23-S
1-3 Nov 2009
New, modified and deleted commands
Table 1-1
Chapter 1: Introduction to commands
Commands status (Continued)
Feature
Command
Status
equip on page 3-403
Modified
chg_element on page 3-106
Modified
stat_mode on page 5-48
Modified
disp_options on page 3-356
Modified
disp_rtf_channel on page 3-375
Modified
disp_equipment on page 3-283
Modified
disp_processor on page 3-367
Modified
equip on page 3-403
Modified
lock_device on page 3-429
Modified
modify_value on page 3-456
Modified
state on page 3-515
Modified
disp_stats on page 5-34
Modified
stat_mode on page 5-48
Modified
{30828}
disp_options on page 3-356
Modified
{23306}
chg_element on page 3-106
Modified
disp_element on page 3-272
Modified
cage_audit on page 3-58
Modified
chg_audit_sched on page 3-76
Modified
chg_element on page 3-106
Modified
device_audit on page 3-210
Modified
query_audits on page 3-472
Modified
chg_audit_sched on page 3-76
Modified
chg_element on page 3-106
Modified
device_audit on page 3-210
Modified
disp_element on page 3-272
Modified
disp_equipment on page 3-283
Modified
disp_traffic on page 3-394
Modified
equip on page 3-403
Modified
ins_device on page 3-423
Modified
unequip on page 3-570
Modified
unlock_device on page 3-581
Modified
disp_mms_ts_usage on page 3-330
Modified
chg_element on page 3-106
Modified
chg_level on page 3-142
Modified
{27703A}
{28351}
{25002}
{26740}
{27508}
Continued
1-4
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 1-1
Commands status (Continued)
Feature {28000}
New, modified and deleted commands
Command
Status
chg_element on page 3-106
Modified
disp_element on page 3-272
Modified
` {28000}
equip on page 3-403
Modified
{28337}
chg_element on page 3-106
Modified
chg_stat_prop on page 5-5
Modified
disp_element on page 3-272
Modified
disp_enable_stat on page 5-12
Modified
disp_equipment on page 3-283
Modified
disp_hdlc on page 3-317
Modified
disp_mms_ts_usage on page 3-330
Modified
disp_stat_prop on page 5-24
Modified
disp_stats on page 5-34
Modified
equip on page 3-403
Modified
modify_value on page 3-456
Modified
reassign on page 3-477
Modified
stat_mode on page 5-48
Modified
add_neighbor on page 3-35
Modified
chg_element on page 3-106
Modified
disp_element on page 3-272
Modified
disp_neighbor on page 3-343
Modified
disp_options on page 3-356
Modified
modify_neighbor on page 3-447
Modified
chg_element on page 3-106
Modified
disp_element on page 3-272
Modified
chg_stat_prop on page 5-5
Modified
disp_enable_stat on page 5-12
Modified
stat_mode on page 5-48
Modified
chg_element on page 3-106
Modified
disp_stat_prop on page 5-24
Modified
disp_stats on page 5-34
Modified
stat_mode on page 5-48
Modified
chg_cell_element on page 3-84
Modified
chg_element on page 3-106
Modified
chg_stat_prop on page 5-5
Modified
{31400}
{32340}
{33863}
{23292}
{26881}
Continued
68P02901W23-S
1-5 Nov 2009
New, modified and deleted commands
Table 1-1 Feature
Chapter 1: Introduction to commands
Commands status (Continued) Command
Status
disp_cell on page 3-241
Modified
disp_element on page 3-272
Modified
disp_options on page 3-356
Modified
disp_stat_prop on page 5-24
Modified
chg_cell_element on page 3-84
Modified
chg_element on page 3-106
Modified
chg_stat_prop on page 5-5
Modified
disp_element on page 3-272
Modified
disp_enable_stat on page 5-12
Modified
disp_stats on page 5-34
Modified
disp_stat_prop on page 5-24
Modified
stat_mode on page 5-48
Modified
chg_stat_prop on page 5-5
Modified
disp_enable_stat on page 5-12
Modified
disp_stats on page 5-34
Modified
disp_stat_prop on page 5-24
Modified
stat_mode on page 5-48
Modified
{34144}
disp_cell_status on page 3-247
Modified
{34145}
disp_equipment on page 3-283
Modified
chg_element on page 3-106
Modified
disp_element on page 3-272
Modified
chg_stat_prop on page 5-5
Modified
disp_enable_stat on page 5-12
Modified
stat_mode on page 5-48
Modified
chg_cell_element on page 3-84
Modified
chg_element on page 3-106
Modified
disp_element on page 3-272
Modified
{33812}
add_neighbor on page 3-35
Modified
{34320G}
chg_element on page 3-106
Modified
disp_element on page 3-272
Modified
disp_options on page 3-356
Modified
chg_element on page 3-106
Modified
disp_element on page 3-272
Modified
disp_options on page 3-356
Modified
{26881}
{31565}
{33397}
{29693A}
{33780}
{34164}
{34303}
{28938}
Continued
1-6
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 1-1
Commands status (Continued)
Feature {23311A}
68P02901W23-S
New, modified and deleted commands
Command
Status
chg_cell_element on page 3-84
Modified
chg_element on page 3-106
Modified
chg_hop_params on page 3-128
Modified
disp_cell_status on page 3-247
Modified
disp_equipment on page 3-283
Modified
disp_options on page 3-356
Modified
disp_rtf_channel on page 3-375
Modified
equip on page 3-403
Modified
modify_value on page 3-456
Modified
unequip on page 3-570
Modified
1-7 Nov 2009
New, modified and deleted database parameters
Chapter 1: Introduction to commands
New, modified and deleted database parameters Table 1-2
Database parameters status
Feature {27717} {27703A}
{27703A}
Parameter
Status
bssgp_t4_timer on page 7-20
New
arp_bg_1 on page 6-47
New
arp_bg_2 on page 6-49
New
arp_bg_3 on page 6-51
New
arp_i_be_1 on page 6-53
New
arp_i_be_2 on page 6-55
New
arp_i_be_3 on page 6-57
New
arp_streaming_1 on page 6-59
New
arp_streaming_2 on page 6-61
New
arp_streaming_3 on page 6-63
New
mtbr_downgrade_enabled on page 6-589
New
pfm_sig_enabled on page 6-646
New
qos_mbr_enabled on page 6-688
New
streaming_enabled on page 6-826
New
sgsn_release on page 6-803
New
thp_stream_weight on page 6-861
New
{26481}
cabinet_type on page 8-13
Modified
{28000}
prp_fanout_mode on page 6-678
New
prpThptOpt on page 6-679
New
{28337}
ss7_hsp_l2_t1 on page 7-177
New
{28938}
IncellOpt on page 6-428
New
{28351}
base_ip_address on page 6-77
New
{26740}
eth_rx_errors_threshold on page 6-279
New
eth_tx_errors_threshold on page 6-280
New
dsp_error_clr_thresh on page 6-239
New
dsp_error_gen_thresh on page 6-241
New
dsp_error_inc on page 6-242
New
psi_trau_fill_frames_threshold on page 6-681
New
{26740}
tdm_ts_blocks on page 6-854
New
{30830}
asym_edge_enabled on page 6-65
New
ctu2d_asym_opt on page 6-178
New Continued
1-8
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 1-2
New, modified and deleted database parameters
Database parameters status (Continued)
Feature
Parameter
Status
{32340}
cell_barred_delay on page 6-147
New
{30828}
ctu2d_cap_opt on page 6-179
New
{27508}
fieldeng_always _enabled on page 6-296
New
{30340}
stp_pc on page 6-823
New
stp_pc_enabled on page 6-824
New
tdOpt on page 8-93
New
tdd_qoffset on page 6-851
New
td_enabled on page 6-852
New
{25002}
tdm_switch on page 6-853
New
{26881}
ext_ul_dur on page 6-283
New
ext_utbf_nodata on page 6-284
New
extuplinkOpt on page 6-288
New
{31400}
ddtr_ctrl_enabled on page 6-186
Modified
{26881}
gprs_bs_cv_max on page 6-311
Modified
{31565}
_cell_data,20 on page 6-6
New
{29693A}
fer_meas_period on page 6-295
New
{34320G}
power_save_enable on page 6-665
New
Pw_Save_SwitchOpt on page 6-682
New
{34303}
_site_data, 5 on page 6-8
New
{23306}
bsp_overload_protection on page 6-96
New
ercgprsOpt on page 6-277
New
ext_pdchs on page 8-36
New
{23311A}
68P02901W23-S
1-9 Nov 2009
GSR9 new/modified parameters user reference form
Chapter 1: Introduction to commands
GSR9 new/modified parameters user reference form ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
This section provides a customer form for recording current values set locally for the GSR9 new/modified parameters. The form also lists the relevant GSR9 feature, valid range, and default values for each new or modified parameter.
Required editing software Adobe Reader 7.0 is required to enter data on this form electronically. Adobe Reader 7.0 can be installed from the CD-ROM for this manual or downloaded for free from http://www.adobe.com.
Using the form To use this form, enter customer values for the GSR9 new/modified parameters in the Local Setting column either by: •
Printing the form and entering the local value of the parameter manually, or,
•
Clicking in the appropriate cell in the Local Setting column and typing the local value for the parameter. Then printing the completed form for further use (see NOTE).
NOTE Adobe Reader 7.0 does not allow completed/amended forms to be printed. To print the completed/amended form requires the full Adobe Acrobat 7.0 Professional.
Storing an image of the completed form To retain an image of the completed form, take a screen grab (Alt + Print Screen) of the full page. Then paste it into a suitable file, such as a Word document, and store in the appropriate manner.
1-10
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
GSR9 new/modified parameters reference form
GSR9 new/modified parameters reference form Parameter
Status
Feature
Valid range
Default value
bssgp_t4_timer
New
Support of RESUME at Intra-BSC level {27717}
100 to 10000
800
pcu_n
New
Software support for High Bandwidth {27955A}
pcu or pcu_0
pcu
ss7_hsp_l2_t1
New
BSC Signaling Link Set Capacity and Flexibility Enhancement {28337}
25000 to 350000
300000
arp_bg_1
New
GSR9 QoS {27703A}
4 to 123
93 (pci - 1, priority level 7, pvi - 1)
arp_bg_2
New
GSR9 QoS {27703A}
4 to 123
97 (pci - 1, priority level 8, pvi - 1)
arp_bg_3
New
GSR9 QoS {27703A}
4 to 123
101 (pci - 1, priority level - 9, pvi - 1)
arp_i_be_1
New
GSR9 QoS {27703A}
4 to 123
49 (pci=0, priority level=12, pvi=1)
arp_i_be_2
New
GSR9 QoS {27703A}
4 to 123
53 (pci=0, priority level=13, pvi=1)
arp_i_be_3
New
GSR9 QoS {27703A}
4 to 123
73 (pci=1, priority level=2, pvi=1)
arp_streaming_1
New
GSR9 QoS {27703A}
4 to 123
49 (pci=0, priority level=12, pvi=1)
arp_streaming_2
New
GSR9 QoS {27703A}
4 to 123
53 (pci=0, priority level=13, pvi=1)
arp_streaming_3
New
GSR9 QoS {27703A}
4 to 123
77 (pci- 1, priority level 3, pvi - 1)
pfm_sig_enabled
New
GSR9 QoS {27703A}
0 or 1
1
qos_mbr_enabled
New
GSR9 QoS {27703A}
0 or 1
0
Local value
Continued
68P02901W23-S
1-11 Nov 2009
GSR9 new/modified parameters reference form
Parameter
Status
Feature
Chapter 1: Introduction to commands
Valid range
Default value
Modified
GSR9 QoS {27703A}
0 to 2
0
stream_downgrade _enabled
New
GSR9 QoS {27703A}
0 or 1
1
streaming_enabled
New
GSR9 QoS {27703A}
0 or 1
0
thp_stream_weight
New
GSR9 QoS {27703A}
10 to 40
40
prpThptOpt
New
Increase throughput of PRP {28000}
0 to 1
N/A
IncellOpt
New
Support of InCell as an Optional Feature {28938}
0 to 1
N/A
cabinet_type
New
Support for Horizon II Micro cabinet identifier {26481}
0 to 29
N/A
mtbr_downgrade _enable
New
GSR9 QoS {27703A}
0 or 1
1
prp_fanout_mode
New
Increase throughput of PRP {28000}
1 or 2
1
base_ip_address
New
Addition of new BSC/PCU hardware to increase GPRS capacity {28351}
1.0.0.1 (minimum) 223.255.255.231 (maximum)
10.0.0.1
eth_rx_errors _threshold
New
High Bandwidth inter-connection between BSC and PCU {26740}
0 to 100
10
eth_tx_errors _threshold
New
High Bandwidth inter-connection between BSC and PCU {26740}
0 to 100
10
dsp_error_clr_thresh
New
High Bandwidth inter-connection between BSC and PCU {26740}
0 to 253
0
dsp_error_gen_thresh New
High Bandwidth inter-connection between BSC and PCU {26740}
2 to 255
6
sgsn_release
Local value
Continued
1-12
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Parameter dsp_error_inc
Status New
Feature
GSR9 new/modified parameters reference form
Valid range
High Bandwidth inter-connection between BSC and PCU {26740}
0 to 255
Default value
Local value
0 (ECERM feature restricted) 1 (ECERM feature unrestricted)
psi_trau_fill_frames _threshold
New
High Bandwidth inter-connection between BSC and PCU {26740}
0 to 100
10
tdm_ts_blocks
New
High Bandwidth inter-connection between BSC and PCU {26740}
2 to 10
2
asym_edge_enabled
New
Asymmetric EDGE {30830}
0 or 1
0
ctu2d_asym_opt
New
Asymmetric EDGE {30830}
0 or 1
N/A
cell_barred_delay
New
Cell OOS Enhancement feature {32340}
0 to 180
0
ctu2d_cap_opt
New
CTU2-D Base on GSR9 {30828}
0 or 1
N/A
fieldeng_always _enabled
New
BSS User Security Management {27508}
0 or 1
1
stp_pc
New
Supports MTP routing {30340}
0 to 16383
0
stp_pc_enabled
New
Supports MTP routing {30340}
0 or 1
0
tdOpt
New
TD-SCDMA and GSM interworking feature {31400}
0 (TD-SCDMA inter-working restricted.)
N/A
1 (TD-SCDMA inter-working unrestricted.) tdd_qoffset
New
TD-SCDMA and GSM interworking feature {31400}
0 (TD-SCDMA inter-working OFF.)
0
1 (TD-SCDMA inter-working ON.) td_enabled
New
TD-SCDMA and GSM interworking feature {31400} Continued
68P02901W23-S
1-13 Nov 2009
GSR9 new/modified parameters reference form
Parameter tdm_switch
Status New
Feature TDM Availability Enhancements {25002}
Chapter 1: Introduction to commands
Valid range 0 (Switch closed.)
Default value 0
1 (Switch open.)
ext_ul_dur
New
Support for Release 4 based Extended Uplink TBF mode {26881}
0 or 24 - 250
0
ext_utbf_nodata
New
Support for Release 4 based Extended Uplink TBF mode {26881}
0 or 1
0
extuplinkOpt
New
Support for Release 4 based Extended Uplink TBF mode {26881}
0 or 1
0
ddtr_ctrl_enabled
Modified
Support for Release 4 based Extended Uplink TBF mode {26881}
0 or 1
0
gprs_bs_cv_max
Modified
Support for Release 4 based Extended Uplink TBF mode {26881}
0 to 15
8
_cell_data,20
New
Support a switch and additional stats for AGCH flow control {31565}
0 to 2
1
fer_meas_period
New
Adjustable FER Bins {29693A}
0 to 255
0
Pw_Save_SwitchOpt
New
SW enabler PA bias switch on/off on CTU2D {34320G}
0 or 1
N/A
power_save_enable
New
SW enabler PA bias switch on/off on CTU2D {34320G}
0 or 1
0
_site_data, 5
New
Dual Abis Aware BTS {34303}
0 Minimum
0
2 Maximum
ercgprsOpt
New
Extended Range Cell (ERC) for Data {23311A}
0 or 1
N/A
ext_pdchs
New
Extended Range Cell (ERC) for Data {23311A}
0 to 4
0
1-14
Local value
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
BSS MMI functions
BSS MMI functions ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
In the GSM system, Man-Machine Interface (MMI) commands are part of the Network Management function. The Network Management function can be subdivided into task-orientated categories. On a Base Station System (BSS), MMI commands are responsible for these activities: •
BSS Initialization Process (IP).
•
Security management, such as controlling system access.
•
Maintenance or Fault Management (FM).
•
System change control or Configuration Management (CM).
•
Call Processing maintenance.
•
Central statistics processing.
•
Miscellaneous.
BSS Initialization Process The Initialization Process (IP) load codes from three sources: •
GPROC.
•
Operation and Maintenance Centre (OMC-R).
•
LAN connection to a personal computer (PC).
Upon initialization, code is loaded on the BSS. Initialization occurs when the BSS is reset, the existing code is damaged, or a new version of code exists.
Early MMI interaction The MMI prompt is presented before the initialization process is complete. Early interaction is only permitted with CM process commands.
Security management Passwords are required to access the system. These passwords ensure that only authorized persons have access and establish a system/command permission level commensurate with the person. If an incorrect password is entered, access to a security level is denied.
68P02901W23-S
1-15 Nov 2009
Fault Management
Chapter 1: Introduction to commands
Fault Management Fault Management commands are used to display and modify the administrative state of devices or functions. Alarms are one example of this type of control.
Configuration Management Configuration Management commands are used to: •
Configure the Base Station System.
•
Populate the database during SYSGEN.
•
Modify the CM database.
•
Display information from the CM database.
Call processing Call processing commands are used to trace the progress of a specified call, through random trace, either by call rate, or SCCP connection number. The total data resulting from the call progress events can be collected for later analysis.
Central statistics processing Statistics commands are used to:
1-16
•
Enable/Disable statistics.
•
Display/Modify statistics for devices or cells.
•
Modify statistics time interval for system.
•
Monitor active (enabled) statistics for system.
•
Report statistics data.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Miscellaneous commands
Miscellaneous commands Miscellaneous commands do not conveniently fit into the categories already outlined. These commands are used to: •
Begin/End a SYSGEN session.
•
Reset the entire BSS.
•
Clear database contents.
•
Display/Modify time function (time-stamp).
•
Display version of a software load.
•
Perform miscellaneous procedures, such as displaying the DTE link address, ROM checksum, and so on.
68P02901W23-S
1-17 Nov 2009
BSS task-oriented command usage
Chapter 1: Introduction to commands
BSS task-oriented command usage ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Table 1-3 shows Network Management activities at the BSS MMI and the related task-oriented MMI commands.
Table 1-3
Task oriented MMI commands Task
Related commands Maintenance (Fault Management) commands:
Display the administrative state of devices or functions.
disp_processor on page 3-367,
state on page 3-515.
Modify the administrative state of devices and associated functions.
ins_device on page 3-423, unlock_device on page 3-581,
lock_device on page 3-429.
Enable, modify, disable, and display alarms.
alarm_mode on page 3-52, chg_eas_alarm on page 3-102, chg_throttle on page 3-156, disp_act_alarm on page 3-225, disp_throttle on page 3-386,
assess on page 3-54, chg_severity on page 3-148, del_act_alarm on page 3-190, disp_severity on page 3-383.
System change control (Configuration Management Database) commands: Configure the BSS.
add_cell on page 3-22, add_neighbor on page 3-35, add_rtf_path on page 3-50, configure_csfp on page 3-175, reassign on page 3-477, set_full_power on page 3-496, soft_reset on page 3-511,
add_cell on page 3-22, add_nsvc on page 3-48, cell_name on page 3-62, equip on page 3-403, reset_device on page 3-485, shutdown_device on page 3-502.
Modify the CM database.
chg_a5_alg_pr on page 3-73, chg_audit_sched on page 3-76, chg_cell_id on page 3-90, chg_dte on page 3-98, chg_hop_params on page 3-128, chg_rtf_freq on page 3-144, chg_x25config on page 3-166, copy_path on page 3-187,
chg_acs_params on page 3-65, chg_cell_element on page 3-84, chg_csfp on page 3-95, chg_element on page 3-106, chg_ksw_config on page 3-136, chg_ts_usage on page 3-161, copy_cell on page 3-179, del_cell on page 3-192,
Continued
1-18
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 1-3
BSS task-oriented command usage
Task oriented MMI commands (Continued) Task
Related commands del_conn on page 3-195, del_nsvc on page 3-202, modify_value on page 3-456, unconfigure_csfp on page 3-568,
Populate the database during SYSGEN ON.
Display information from the CM database.
del_neighbor on page 3-197, modify_neighbor on page 3-447,set_relay_contact on page 3-500, unequip on page 3-570.
All MMI commands except the following: alarm_mode, cage_audit, clear_gclk_avgs, device_audit, disp_act_alarm, disp_cal_data, disp_csfp_status, disp_gclk_cal, disp_interval, disp_processor, disp_rtf_channel, disp_trace_call, enable_alarm, ins_device, query_audits, reset_device, set_relay_contact, site_audit, status_mode, swap_devices, trace_stop,
assess, clear_cal_data, del_act_alarm, diagnose_device disp_bss, disp_cell_status, disp_gclk_avgs, disp_hdlc, disp_link_usage, disp_relay_contact, disp_stats, disp_version, gclk_cal_mode, lock_device, reattempt_pl, set_full_power, shutdown_device, state, store_cal_data, trace_call, unlock_devices.
cage_audit on page 3-58, disp_acs on page 3-223, disp_cell on page 3-241, disp_cell_status on page 3-247, disp_csfp on page 3-263, disp_element on page 3-272, disp_exp_config on page 3-305, disp_hdlc on page 3-317, disp_link on page 3-326, disp_mms_ts_usage on page 3-330, disp_nsvc on page 3-353, disp_relay_contact on page 3-373, disp_rtf_path on page 3-381, disp_transcoding on page 3-397,
disp_a5_alg_pr on page 3-221, disp_bss on page 3-229, disp_cell_map on page 3-244, disp_conn on page 3-261, disp_csfp_status on page 3-267, disp_equipment on page 3-283, disp_gsm_cells on page 3-314, disp_hopping on page 3-320, disp_link_usage on page 3-328, disp_neighbor on page 3-343, disp_options on page 3-356,
Continued
68P02901W23-S
1-19 Nov 2009
BSS task-oriented command usage
Table 1-3
Chapter 1: Introduction to commands
Task oriented MMI commands (Continued) Task
Related commands freq_types_allowed on page 3-417, site_audit on page 3-507,
disp_rtf_channel on page 3-375, disp_traffic on page 3-394, disp_x25config on page 3-401, query_audits on page 3-472.
Call processing (Database) commands: Trace the progress of a specified call by random trace (by call rate).
disp_trace_call on page 3-390,
Trace the progress of a specified call by random trace (by SCCP connection number).
trace_call on page 3-550.
Report call processing data.
trace_connection on page 3-562.
Stop an existing trace or a specified call
trace_stop on page 3-564.
trace_call on page 3-550.
Statistics (Central Statistics Processing Database) commands: Enable/disable statistics.
stat_mode on page 5-48.
Display/modify statistics for devices or cells.
chg_stat_prop on page 5-5,
Modify statistics time interval for system.
disp_interval on page 5-22.
Monitor active (enabled) statistics for system.
disp_enable_stat on page 5-12.
Report statistics data.
disp_stat_prop on page 5-24.
disp_stats on page 5-34.
Miscellaneous commands: Begin/end a SYSGEN session (see SYSGEN mode on page 1-43).
sysgen_mode on page 3-540.
Reset the entire BSS.
reset_site on page 3-492.
Clear database contents.
clear_cal_data on page 3-169, clear_gclk_avgs on page 3-173.
clear_database on page 3-171,
Modify/display time function (time-stamp).
chg_time on page 3-158,
chg_throttle on page 3-156.
Display version of software load
disp_version on page 3-399.
Continued
1-20
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 1-3
Task oriented MMI commands (Continued) Task
Perform miscellaneous tasks (display DTE link, ROM checksum, and so on).
68P02901W23-S
BSS task-oriented command usage
Related commands chg_level on page 3-142, chg_smscb_msg on page 3-150, del_smscb_msg on page 3-206, diagnose_device on page 3-217, disp_cbch_state on page 3-237, disp_flash on page 3-307, disp_gclk_cal on page 3-311, disp_site on page 3-385, page on page 3-470, status_mode on page 3-530, swap_devices on page 3-537,
connection_code on page 3-177, device_audit on page 3-210, disp_cal_data on page 3-233, disp_dte on page 3-269, disp_gclk_avgs on page 3-309, disp_level on page 3-325, gclk_cal_mode on page 3-421, reattempt_pl on page 3-483, store_cal_data on page 3-534, time_stamp on page 3-548.
1-21 Nov 2009
Command/database parameter security levels
Chapter 1: Introduction to commands
Command/database parameter security levels ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Four security levels are provided in the system to control command and database access. Access to each level is controlled using passwords. Each command in the system is assigned a security level. Refer to the command description for a specific command security level.
Level 1 This level permits the display of system parameters. Access is restricted primarily to system monitoring commands.
Level 2 This level permits access to all system commands, including the ability to change the system database. This security level also permits the operator to change passwords for both Level 1 and Level 2 users.
Level 3 This level provides all of the features accessible in security Level 2 plus the executive monitor. Two passwords are required to access security Level 3. The passwords for this level cannot be changed unless the Optional Level 3 Password Feature is purchased. This feature enhances BSS security by allowing the Level 3 passwords to be changed in the event the Level 3 passwords are compromised.
Level 4 {27508} This level provides all the features accessible in security Level 3 plus the executive monitor. Two passwords are required to access security Level 4. The passwords for this level cannot be changed unless the Optional Level 4 Password Feature is purchased.
1-22
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Command/database parameter types
Command/database parameter types ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
MMI commands and database parameters are classified on the basis of a user action. If the user action is required to enter the command or change the value of the database parameter.
Type A commands and parameters No special user action is required to enter a Type A command or change a Type A database parameter.
Type B commands and parameters The operator is required to perform one or more actions when entering a Type B command or changing a Type B database parameter. Operator actions are required before or after the command entry or database change. Specific required actions are listed in the Operator actions section of each command and database parameter description.
68P02901W23-S
1-23 Nov 2009
Commands to be used with caution
Chapter 1: Introduction to commands
Commands to be used with caution ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The following commands cause a device to cycle. Before the device is cycled, a prompt is displayed and must be acknowledged.
1-24
add_cell
disp_cbch_state
add_nsvc
disp_gclk_cal
add_rtf_path
disp_hopping
chg_a5_alg_pr
equip
chg_cell_element (depends on parameter)
freq_types_allowed
chg_dte
ins_device
chg_element (depends on parameter)
mod_conn
chg_level
mod_nsvc
ksw_config
modify_value (depends on parameter)
chg_rtf_f
reset_device
clear_cal_datareq
reset_site
clear_database
set_full_power
configure_csfp
shutdown_device
copy_cell
soft_reset
diagnose_device
swap_devices
disp_a5_alg_pr
sysgen_mode
disp_act_alarm
unconfigure_csfp
disp_hdsl_settings
unequip
disp_severity
unlock_device
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Parameters to be used with caution
Parameters to be used with caution ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The following parameters cause a device to cycle. Before the device is cycled, a prompt is displayed and must be acknowledged. bsic
downlink_sync_timer
bs_ag_blks_res
initial_sync_timer
bs_pa_mfrms
smg_gb_vers
cbc_fast_select
swfm_enable
ccch_conf
uplink_sync_timer
68P02901W23-S
1-25 Nov 2009
Entering MMI commands
Chapter 1: Introduction to commands
Entering MMI commands ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Commands are entered by typing the command string followed by pressing the Return key (or its equivalent). The following conventions are used to present command strings: •
A character sequence that is enclosed in angle brackets represents a mandatory parameter. Wherein a specific variable (value or character string) replaces the string. For example: is entered as an hour between 00 and23.
•
A character sequence in bold serif type such as example represents a mandatory parameter that must be entered as is. For example: dri
•
A character sequence enclosed in [ ] indicates that the parameter is optional. For example: [] or [dri].
Command syntax The following guidelines must be followed when entering MMI commands. •
Command names are case-sensitive and cannot be entered as mixed upper and lower case characters in a command string. Exceptions to this rule are made clear in the text.
•
An underscore character _ must be used between command keywords, for example add_cell.
•
A space character is used between parameters as a command separator.
Example BSS PROMPT --> add_rtf_path 3 2 1 1
MMI Command
First Command Parameter
Space separating Command Parameter ti-gsm-entering_00018-ai-sw
1-26
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Timeouts
The following demonstrates how MMI command examples are represented in this manual: chg_element bsic 1 0 cell number= 5 4 3 2 1 61986 34944 Where:
is: bsic
element_name
1
value
0
location
5 4 3 2 1 61986 34944
cell_desc
System response COMMAND ACCEPTED
Timeouts If a response is not entered within 60 sec, the command or response is rejected, and the following message displays: COMMAND REJECTED: No response to prompt.
Ambiguous command response If the command name is entered incorrectly, the system displays a message stating that the entered command was ambiguous and lists commands with similar command names.
Example: MMI-RAM 0115 -> disp_rtf disp_rtf: Command ambiguous with: disp_rtf_calls
disp_rtf_channel
disp_rtf_path
Entering hexadecimal values Some fields accept hexadecimal (hex) values. To specify a hex value: •
Lead the value with a 0 (zero).
•
Type an h at the end of the value.
For example, the hex equivalent for 255 is ff. To specify this hex value, type: 0ffh
68P02901W23-S
1-27 Nov 2009
MMI command availability
Chapter 1: Introduction to commands
MMI command availability ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
MMI commands are available according to the site location and whether SYSGEN mode is On or Off.
Command availability by location Table 1-4 indicates the sites at which commands can be entered; not the location string availability for command execution.
Table 1-4
MMI command availability by location
Command
MMI ROM
Locations Allowed BSC
BTS
RXCDR
add_cell
X
add_conn
X
add_neighbor
X
add_rtf_path
X
alias
X
X
X
assess
X
X
X
cage_audit
X
X
X
cell_name
X
chg_a5_alg_pr
X
chg_audit_sched
X
chg_cell_element
X
chg_cell_id
X
chg_csfp
X
X
chg_dte
X
X
chg_eas_alarm
X
X
X
X
chg_element
X (1)
chg_hop_params
X
chg_ksw_config
X
chg_level
X
X
chg_rtf_freq
X
chg_severity
X
chg_smscb_msg
X
X
X
X X
X
X
Continued
1-28
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 1-4
Command availability by location
MMI command availability by location (Continued)
Command
MMI ROM
Locations Allowed BSC
BTS
RXCDR
chg_stat_prop
X
X
chg_throttle
X
X
chg_time
X
chg_ts_usage
X
X
X
X
chg_x25config
X
X
X
clear_cal_data
X
clear_database
X
X
clear_gclk_avgs
X
X
copy_cell
X
copy_path
X
del_act_alarm
X
del_cell
X
del_conn
X
X
X
X X
del_channel del_neighbor
X
del_nsvc
X
del_rtf_path
X
del_smscb_msg
X
device_audit
X
X
disp_a5_alg_pr
X
X
disp_act_alarm
X
X
disp_bss
X
X
disp_bssgp_f_bmap
X
disp_cal_data
X
X
disp_cbch_state
X
X
disp_cell
X
X
disp_cell_map
X
X
disp_cell_status
X
X
disp_conn
X
disp_csfp
X
X
X
disp_csfp_status
X
X
X
disp_dte
X
disp_element
X (1)
X
X
X
X
X X
X Continued
68P02901W23-S
1-29 Nov 2009
Command availability by location
Table 1-4
Chapter 1: Introduction to commands
MMI command availability by location (Continued)
Command
MMI ROM
Locations Allowed BSC
BTS
RXCDR
disp_enable_stat
X
X
X
disp_equipment
X
X
X
disp_flash
X
X
X
disp_gclk_avgs
X
X
X
disp_gclk_cal
X
X
X
disp_gsm_cells
X
X
disp_hdlc
X
X
disp_hopping
X
X
disp_interval
X
X
X
disp_level
X
X
X
disp_link_usage
X
X
disp_mms_ts_usage
X
X
disp_neighbor
X
X
disp_nsvc
X
disp_options
X
X
X
disp_processor
X
X
X
disp_relay_contact
X
X
X
disp_rtf_channel
X
X
disp_rtf_path
X
X
disp_severity
X
X
X
disp_site
X
X
X
disp_stats
X
X
X
disp_stat_prop
X
X
X
disp_throttle
X
X
X
disp_time
X
X
X
disp_trace_call
X
X
disp_traffic
X
X
disp_version
X
X
X
X
X
X
X
equip
X
X
freq_types_allowed
X
disp_x25config
X (2)
X
gclk_cal_mode help
X
X
X Continued
1-30
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 1-4
Command availability by location
MMI command availability by location (Continued)
Command
MMI ROM
Locations Allowed BSC
BTS
RXCDR
history
X
X
X
ins_device
X
X
X
lock_device
X
X
X
man
X
X
X
mod_conn
X
X
map_eas_opto
X
X
mod_nsvc
X
modify_neighbor
X
modify_value
X
page
X
X
X
query_audits
X
X
X
reassign
X
reattempt_pl
X
X
X
reset_device
X
X
X
reset_site
X
X
X
set_full_power
X
X
set_relay_contact
X
X
X
shutdown_device
X
X
X
site_audit
X
X
X
soft_reset
X
X
stat_mode
X
state
X
X
X
status_mode
X
X
X
store_cal_data
X
sysgen_mode
X
swap_devices
X
X
X
swfm_enable
X
X
X
time_stamp
X
X
X
trace_call
X
X
trace_stop
X
X
X
X
X
X
Continued
68P02901W23-S
1-31 Nov 2009
Command availability by SYSGEN mode
Table 1-4
Chapter 1: Introduction to commands
MMI command availability by location (Continued)
Command
MMI ROM
Locations Allowed BSC
BTS
RXCDR
unalias
X
X
X
unconfigure_csfp
X
X
unequip
X
X
unlock_device
X
X
X
•
These commands are not available for MMI ROM processes running on TCU boards. Also note that these commands do not accept the location or cell parameters used in the RAM version of these commands.
•
These commands are only available for MMI ROM processes running on GPROC boards.
Command availability by SYSGEN mode Table 1-5 shows the availability of commands in the various SYSGEN modes.
Table 1-5
MMI command availability by SYSGEN mode
Command
SYSGEN MODE ON
SYSGEN MODE OFF MMI READY
CM READY
SITE READY
add_cell
X
X
add_conn
X
X
add_neighbor
X
X
add_nsvc
X
X
add_rtf_path
X
X X
alarm_mode alias
X
X
X
X
assess
X
cage_audit
X
cell_name
X
X
chg_a5_alg_pr
X
X
chg_audit_sched
X
X
chg_cell_element
X
X
chg_cell_id
X
X
chg_csfp
X
X
chg_dte
X
X
chg_eas_alarm
X
X Continued
1-32
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 1-5
Command availability by SYSGEN mode
MMI command availability by SYSGEN mode (Continued)
Command
SYSGEN MODE ON
SYSGEN MODE OFF MMI READY
CM READY
SITE READY
chg_element
X
X
chg_hop_params
X
X
chg_ksw_config
X
X
chg_level
X
chg_rtf_freq
X
X
chg_severity
X
X
chg_smscb_msg
X
X
chg_stat_prop
X
X
chg_throttle
X
X
chg_time
X
X
chg_ts_usage
X
X
chg_x25config
X
X
X
X
X
clear_cal_data clear_database
X
X X
clear_gclk_avgs configure_csfp
X
connection_code
X
X
copy_cell
X
X
copy_path
X
X X
del_act_alarm del_cell
X
X
del_conn
X
X
del_neighbor
X
X
del_nsvc
X
X
del_rtf_path
X
X
del_smscb_msg
X
X
device_audit
X
diagnose_device
X
disp_a5_alg_pr
X
X
X
disp_act_alarm
X
disp_bss
X
disp_bssgp_f_bmap
X
disp_conn
X
X
X Continued
68P02901W23-S
1-33 Nov 2009
Command availability by SYSGEN mode
Table 1-5
Chapter 1: Introduction to commands
MMI command availability by SYSGEN mode (Continued)
Command
SYSGEN MODE ON
SYSGEN MODE OFF MMI READY
CM READY
X
disp_cal_data disp_cbch_state
X
disp_cell
X
X X
X X
disp_cell_status disp_csfp
SITE READY
X
X
X X
disp_csfp_status disp_dte
X
X
X
disp_element
X
X
X
disp_enable_stat
X
X
X
disp_equipment
X
X
X
disp_flash
X
X
X
disp_gsm_cells
X
X
X
disp_gclk_avgs
X
disp_gclk_cal
X
disp_hdlc
X
disp_hopping
X
X X
disp_interval disp_level
X
X
X
disp_link
X
X
X
X
X
disp_link_usage disp_mms_ts_usage
X
X
disp_neighbor
X
X
X
disp_nsvc
X
X
X
disp_options
X
X
X
disp_processor
X
disp_relay_contact
X
disp_rtf_channel
X
disp_rtf_path
X
X
disp_severity
X
X
disp_site
X
X
X X
disp_stats disp_stat_prop
X
X
X
disp_throttle
X
X
X Continued
1-34
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 1-5
Command availability by SYSGEN mode
MMI command availability by SYSGEN mode (Continued)
Command disp_time
SYSGEN MODE ON
SYSGEN MODE OFF MMI READY
X
CM READY
SITE READY
X
X X
disp_trace_call disp_traffic
X
X X
disp_version disp_x25config
X
X
X
equip
X
X
freq_types_allowed
X
X X
gclk_cal_mode help
X
X
X
X
history
X
X
X
X
ins_device
X
lock_device
X
man
X
map_eas_opto
X
X
mod_conn
X
X
mod_nsvc
X
X
modify_neighbor
X
X
modify_value
X
X
page
X
X
X
X
X X
query_audits reassign
X
X
X
reattempt_pl
X
reset_device
X
reset_site
X
X
X
X
set_full_power
X
set_relay_contact
X
shutdown_device
X
site_audit
X
soft_reset
X
X
stat_mode
X
X
state
X
status_mode
X
store_cal_data
X Continued
68P02901W23-S
1-35 Nov 2009
Command availability by SYSGEN mode
Table 1-5
Chapter 1: Introduction to commands
MMI command availability by SYSGEN mode (Continued)
Command
SYSGEN MODE ON
SYSGEN MODE OFF MMI READY
CM READY
X
swap_devices swfm_enable
X
sysgen_mode
X
time_stamp
X
X X
X
X
X
X X
trace_call trace_connection
X
X
trace_stop
1-36
X
unalias
X
unconfigure_csfp
X
unequip
X
unlock_device
SITE READY
X
X
X
X X
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
GSM cell ID format
GSM cell ID format ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Cell ids are required parameter entries for many commands. The GSM cell ID format consists of four fields: •
MCC - Mobile Country Code
•
MNC - Mobile Network Code
•
LAC - Location Area Code
•
CI - Cell Identity
The GSM cell ID is typically displayed in the following format: 543 021 61986 (F222h) 34944 (8880h) Where:
is: 543
MCC
021
MNC
61986
LAC
34944
CI
NOTE The LAC and CI values are displayed as hexadecimal values in parentheses, depending on the command.
Input format Two types of GSM cell ID input format, seven elements or four elements, can be used. The format is set with the mmi_cell_id_format parameter.
68P02901W23-S
1-37 Nov 2009
Input format
Chapter 1: Introduction to commands
Seven-element format The system uses the seven-element format when the mmi_cell_id_format parameter = 0. cell=5 4 3 2 1 61986 34944 Where:
is: 5
first digit of MCC
4
second digit of MCC
3
third digit of MCC
2
first digit of MNC
1
second digit of MNC
61986
LAC
34944
CI
This format cannot be used if the optional third MNC digit is necessary. It is valid for PGSM, EGSM, DCS 1800 and PCS 1900 systems.
Four-element format The system uses the four-element format when the mmi_cell_id_format parameter = 1. cell=543 021 61986 34944 Where:
is: 5
first digit of MCC
4
second digit of MCC
3
third digit of MCC
0
first digit MNC
2
second digit of MNC
1
third digit of MNC
61986
LAC
34944
CI
This format must be used if the optional third MNC digit is necessary. It can be used for PGSM, EGSM, and DCS 1800 systems. If the first and/or second digit of the MCC is a zero, it can be omitted from the input. The system recognizes both of the following examples as valid format: 001 011 98765 543211 011 98765 54321
1-38
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Cell name
NOTE If the third MNC digit is required, all three MNC digits must be entered. For example, if the MNC = 001 and the third MNC digit is required, the MNC must be entered as 001. If the MNC is entered as 01 or 1, the system interprets the entry as MNC=01, which is incorrect.
Cell name Each GSM cell is assigned a cell name using the cell_name command. The cell_name is used in place of the GSM cell ID in most of the BSS MMI commands. Refer to the individual command descriptions to determine if the cell_name can be used for a specific command.
68P02901W23-S
1-39 Nov 2009
Indices
Chapter 1: Introduction to commands
Indices ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Indices are used to display information or locate information in a data array.
Device indices Device indices are used with the disp_element command for displaying information associated with the System Audit Process (SAP). Table 1-6 lists the device types and associated indices.
Table 1-6
Device Indices Device Type
Index
KSW
0
KSW (internal loopback tests)
1
MSI
2
DRI
4
GCLK
6
GPROC
8
BSP
12
BTP
14
DHP
16
SITE
18
TDM
20
PCU
22
PSP
24
DPROC
26
For example, the command string disp_element sap_start_time,12 0 displays the audit start time for BSPs (index 12) at location 0.
1-40
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Data array location
Data array location An index is used to identify the location of information in a data array.
Single index number A single index number can identify the column in a single row array where a data element is located. The following example shows the command string used to display the value of the interference level for index level 0 (band 1), in an interfer_bands parameter: disp_element interfer_bands,0 1 cell=0 0 1 0 1 1 1
Two index numbers Some statistical elements require two index numbers. The first index number is the row number. The second index number is the position of the element in the row. For example, the command string disp_element sap_audit_type,0,1 0 displays the value of the sap_audit_type parameter located in row 0, column 1 of a multi-row data array.
Bins A single row of a data array can be referred to as a bin. If a command uses bin numbers to specify the row in a data array, the index number specifies the position of the data element in the bin. The following represents an array with four bins with 32 elements in each bin: bin 0 [0 1 2 ... 31] bin 1 [0 1 2 ... 31] bin 2 [0 1 2 ... 31] bin 3 [0 1 2 ... 31] The following example shows the command string that is used to assign or change the value of the rxlev_ul_ho parameter. The value of the parameter is located in the first column (index = 0) of the second bin (bin_num = 1): chg_cell_element rxlev_ul_ho 2 6 2 0 2 2868 3100 1 0 8,0 The following example shows the command string that is used to display the contents of a bin. The index value used with the disp_element command is the bin number used when assigning or changing the value of one of the elements of the parameter: disp_element rxlev_dl_ho,1 0 cell_number=2 6 2 0 2 2868 3100 rxlev_dl_ho = alg_num: 1 alg_data: 8 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
68P02901W23-S
1-41 Nov 2009
Thresholds
Chapter 1: Introduction to commands
Thresholds Gauge and some counter statistics can be assigned thresholds. An alarm is sent to the OMC-R when the threshold is exceeded. The severity of the alarm associated with a statistical parameter can be displayed using the disp_element command using an index value of 1. For example, the command string disp_element invalid_frames_rx,1 0 displays the severity of the alarm associated with the invalid_frames_rx statistical parameter: invalid_frames_rx = 2 Table 1-7 lists the alarm severities.
Table 1-7
Alarm Severities Alarm Number
Severity
0
Investigate
1
Critical
2
Major
3
Minor
4
Warning
5
Clear
EAS alarm table The EAS table consists of 34 indexed pairs. Each pair includes a severity level and up to 24 text characters. Both the text and severity level are assigned when the EAS alarm table is initialized using the chg_eas_alarm command. After initialization, the text and severity level can be displayed independently using the disp_element eas_alarm or the disp_element eas_severity commands respectively. The severity level can be modified independently using the chg_element eas_severity command.
1-42
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
SYSGEN mode
SYSGEN mode ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
SYSGEN mode ensures that database entries are checked at system initialization or after a change in database parameters. SYSGEN mode must be On to allow entry of some commands or changes to certain parameters. SYSGEN mode is set On or Off using the sysgen_mode command (see sysgen_mode on page 3-540).
SYSGEN OFF The SYSGEN OFF mode is the normal system mode of operation. The sysgen_mode off command places the system in the SYSGEN OFF mode. If the system is in the SYSGEN ON mode and the sysgen_mode off command is entered, any changes made to the database are checked and the following displayed: *******VERIFYING DATABASE BEFORE COMPLETING SYSGEN******* Frequency hopping verification in progress. SITE 0 Verification. DB Verification passed. COMMAND ACCEPTED. After the system initializes, it is in the SYSGEN OFF mode. If the system is in the SYSGEN OFF mode and the sysgen_mode off command is entered, the command is rejected and the following message displays: COMMAND REJECTED: sysgen mode is already off
SYSGEN ON The system must be placed in the SYSGEN ON mode of operation to enter some commands or change some parameters. Until the system is returned to its normal mode of operation, changes can be entered into the database without being checked.
CAUTION Do NOT enter the sysgen_mode on or the sysgen_mode off commands at the OMC-R. If the system is in the SYSGEN OFF mode and the sysgen_mode on command is entered, the system prompts the user to reinitialize the site: COMMAND ACCEPTED: You must re-init the site to start SYSGEN
68P02901W23-S
1-43 Nov 2009
Database changes in SYSGEN ON mode
Chapter 1: Introduction to commands
If the system is in the SYSGEN ON mode and the sysgen_mode on command is entered, the command is rejected and the following message displays: COMMAND REJECTED: sysgen mode is already on The system rejects the sysgen_mode command if it is entered at a GPROC that is not acting as the master GPROC: COMMAND REJECTED: Command only allowed at active BSP.
Database changes in SYSGEN ON mode In a network, the BSC connects to an OMC-R and a copy of the BSC database is stored at the OMC-R. Sometimes a difference is detected between the database load in the OMC-R and the BSC. Then the OMC-R automatically downloads a copy of the database in its memory to the BSC. Any changes made while the BSC was in the SYSGEN ON mode are overwritten by the download from the OMC-R. If the changes to be made while the BSC is in SYSGEN ON mode are to be retained, the following procedure must be used:
Procedure 1-1
Retain database changes made in SYSGEN ON mode
1
Disable downloads for network elements at the OMC-R.
2
Enter the sysgen_mode on command at the BSC
3
Enter the reset_site 0 command.
4
After the system has reset, modify or enter the commands to the database as necessary.
NOTE Commands must be entered within 10 minutes after the MMI RAM: prompt is presented. If a command is not entered, the system resets.
1-44
5
Enter the sysgen_mode off command at the BSC.
6
After the system has returned to service, upload the modified database from the BSC to the OMC-R. The upload is done at the OMC-R.
7
Re-enable downloads for network elements at the OMC-R.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Initial SYSGEN mode
Initial SYSGEN mode The initial SYSGEN mode occurs when the system is placed in the SYSGEN ON mode without a Configuration Management (CM) database. The initial SYSGEN mode is used to load the CM database using a script.
CAUTION Personnel who fully understand the consequences must use the clear_database command. The system is placed in the initial SYSGEN mode by placing the system in the SYSGEN ON mode then entering the clear_database command.
Scripts A script is a file that contains a series of commands which load the CM database into the system. A script is loaded in the initial SYSGEN mode and permits large amounts of information to be loaded efficiently onto the system. After the database is loaded using a script, the system must be returned to the SYSGEN OFF mode to verify the script contents. If errors are detected, the system does not return to the SYSGEN OFF mode. Correct the script and reload before the system returns to its normal operating state.
SYSGEN safety features Automatic GPROC addition If the initial SYSGEN mode is entered from a GPROC which is not included in the script, a GPROC is added automatically to the slot from which the initial SYSGEN mode was entered. Enter the initial SYSGEN mode from the same type of system for which the database is being loaded. For example, if the script to be loaded is for an RXCDR, enter the initial SYSGEN mode from the master slot of an RXCDR (011ah). If the script to be loaded is for a BSS, the initial SYSGEN mode must be entered from the master slot of a BSC (0115h).
Safety timer If the system is in the SYSGEN ON mode, a timer is used to ensure that a GPROC cannot be left in the SYSGEN ON mode indefinitely. The timer is started when no activity is detected from the TTY terminal. If activity is detected before the timer expires, the timer is reset to its initial value and restarted. If the timer expires, the GPROC is reset with a Global Kill SWFM. Within the SWFM, a message includes a textual description that the timer expired.
68P02901W23-S Nov 2009
1-45
SYSGEN safety features
1-46
Chapter 1: Introduction to commands
68P02901W23-S Nov 2009
Chapter
2 Equipping the CM database ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
This chapter provides information on equipping the CM database at a site. The following topics are in this chapter: •
Introduction to equipping the CM database on page 2-2: introducing the equip command, and listing prerequisites for equipping the database, restrictions on equipping a site, and equip related commands.
•
Using the equip command on page 2-5: providing information on the format and usage of the equip command at the MMI.
•
Equipage hierarchy on page 2-6: containing information and hierarchical charts for equipping devices and functions in different systems.
•
Information for equipping devices on page 2-11: detailing the conditions, rules, and command prompts for each device that can be equipped in the CM database.
•
Information for equipping functions on page 2-57: detailing the conditions, rules, and command prompts for each function that can be equipped in the CM database.
68P02901W23-S Nov 2009
2-1
Introduction to equipping the CM database
Chapter 2: Equipping the CM database
Introduction to equipping the CM database ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Devices and functions are added to the Fault Management portion of the CM database using the equip command (see equip on page 3-403). Since each device and function has specific parameters, there is a corresponding set of prompts. Each device and function also has specific restrictions for equipage. Command prompt details and equipage restrictions for each device/function are provided in this chapter.
Devices and functions that can be equipped The following devices and functions can be equipped in the CM database using the equip command: Devices ABSS
AXCDR
BSP
BSS
BTP
CAB
CAGE
CBL
CIC
COMB
CSFP
DHP
DPROC
DRI
DYNET
EAS
GBL
GCLK
GDS
GPROC
GSL
KSW
LMTL
MSI
MTL
OML
OPL
PATH
PCU
PSP
PSI
RSL
RXCDR
SITE
XBL
ETH
OMF
RTF
Functions LCF
Prerequisites for equipage tasks The following prerequisites requiring operator actions can apply before using the equip command:
2-2
•
Some devices and functions require the system to be in the SYSGEN ON mode. To enter this mode, enter the sysgen_mode on command. To exit this mode, use the sysgen_mode off command (see sysgen_mode on page 3-540).
•
Some devices require the site to be locked. To lock the site, enter the lock_device command (see lock_device on page 3-429). To unlock the site, enter the unlock_device command (see unlock_device on page 3-581).
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Equippage restrictions
•
Some devices and functions can be equipped only after other devices have been equipped. Refer to Equipage hierarchy on page 2-6 for further information.
•
GPRS devices can be equipped only if the GPRS feature is unrestricted.
•
The LMTL can be equipped only if the Location Services support feature is unrestricted and the BSS can support a BSS-based SMLC.
•
To equip a device or function with a frequency, it first must be set as allowable with the freq_types_allowed command (see freq_types_allowed on page 3-417).
Refer to the instructions included with each device or function for specific actions to be taken when using the equip command.
Equippage restrictions The following restrictions apply at the BSC when equipping the CM database: •
A BSC of type 1 or 2 must equip remote sites with an LCF.
•
No more than three PCUs can be equipped per BSC.
In addition, each device and function has specific restrictions for equipage.
NOTE The equip command can be entered only at the BSC. This command does not work at a BTS site. Contact the OMC-R for help in setting up a BTS site.
Equip related commands The following MMI commands are related to equipping devices and functions: •
disp_equipment on page 3-283: Used to display equipped devices and functions.
•
freq_types_allowed on page 3-417: Used to set the frequency types and blocks available at the BSS.
•
lock_device on page 3-429: Used to lock a site to equip certain devices.
•
modify_value on page 3-456: Used to modify the parameter values of an equipped device or function.
•
reassign on page 3-477: Used to reassign a child device from its current parent function to a new parent function.
•
shutdown_device on page 3-502: Used to shut down a device before modifying or unequipping the device.
68P02901W23-S
2-3 Nov 2009
Equip related commands
2-4
Chapter 2: Equipping the CM database
•
state on page 3-515: Used to display the current status of devices and functions in the system.
•
unequip on page 3-570: Used to unequip an equipped device or function.
•
unlock_device on page 3-581: Used to unlock a site after equipping certain devices.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Using the equip command
Using the equip command ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Enter the equip command at the MMI. Specify the site location and the name of the particular device or function to be added to the CM database. The equip command can be entered only at the BSC. It does not work at a BTS. The system responds with a series of command prompts for further operator input. The information requested is dependent on the particular device or function being equipped. If a device or function parameter is optional, there is no need to enter data, simply press the ENTER key at the prompt. The equip command can be exited at any time by entering done in response to any prompt.
Format of equip command The format of the equip command entered at the MMI prompt is: equip is:
Where: location
The location of the device or function, one of: 0 or bsc 0 - 140 pcu or pcu_0
dev/funcc_name
for a BSC. for a BTS. for a PCU.
The name of the device or function being equipped.
System response The system responds with an appropriate set of prompts for the particular device or function being equipped. Enter the correct information in response to the prompts and conditions for equipping the particular device or function. The system indicates execution with COMMAND ACCEPTED message which can be accompanied with a WARNING message. If incorrect information is entered or the particular equip conditions are not met, a COMMAND REJECTED with reason message is issued. Equip conditions and system prompts are provided in: •
Information for equipping devices on page 2-11.
•
Information for equipping functions on page 2-57.
68P02901W23-S
2-5 Nov 2009
Equipage hierarchy
Chapter 2: Equipping the CM database
Equipage hierarchy ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Devices and functions have a hierarchical structure which can differ between systems. Some devices and functions can only be equipped after other devices have been equipped. For example, a CAGE must be equipped before a BTP can be equipped. Other devices are automatically equipped. For example, an MMS is equipped automatically when equipping an MSI. Equipage hierarchy charts in this section show the order in which devices and functions are equipped for the following systems: •
RXCDR
•
InCell
•
M-Cell and Horizonmacro
•
GPRS
RXCDR Figure 2-1 shows the device and function hierarchy for RXCDR systems. In this system, an MMS is automatically equipped when an MSI is equipped.
2-6
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Figure 2-1
RXCDR
Remote Transcoder (RXCDR) devices and functions
NOTE * indicates an automatically equipped device.
68P02901W23-S
2-7 Nov 2009
InCell
Chapter 2: Equipping the CM database
InCell Figure 2-2 shows the device and function hierarchy for InCell systems. In these systems, an MMS is automatically equipped when an MSI is equipped.
Figure 2-2
BSC and InCell BTS
BSS SITE (BSC) DYNET
PCU
CAB
AXCDR Conn_Link
CAGE
PSI KSW GCLK BSP
GPROC CSFP
LCF
ETH
EAS
MSI
OMF MMS*
RF_Unit GDS (LAPD_TRAU)
CIC
GSL MTL OML LMTL
GSL
CBL
XBL
ti-GSM-BSC Incell BTS-00015-eps-sw
NOTE * indicates an automatically equipped device.
2-8
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
M-Cell and Horizonmacro
M-Cell and Horizonmacro Figure 2-3 shows the device and equipment hierarchy for M-Cell and Horizonmacro systems. In these systems, GCLK and CSFP functionality are built into an MCU and are automatically equipped when a BTP is equipped.
Figure 2-3
M-Cell and Horizonmacro equipage hierarchy chart
NOTE * indicates an automatically equipped device.
68P02901W23-S
2-9 Nov 2009
GPRS
Chapter 2: Equipping the CM database
GPRS Figure 2-4 shows the device and function hierarchy for the PCU device in a GPRS system. In the GPRS system, the CAB and CAGE devices are automatically equipped when a PCU is equipped. Also an MMS is automatically equipped when an MSI is equipped.
Figure 2-4
GPRS PCU devices and functions BSS SITE (BSC)
PCU
CAB*
CAGE*
DPROC (PICP)
MPROC (PSP*)
DPROC (PXP)
DPROC (PRP)
PPROC* MSI (PMC)
MSI (PMC)
MSI (PMC)
MMS*
MMS*
MMS*
GDS (LAPD)
GBL
MSI *
ETH
GDS* (LAPD_TRAU)
GDS (TRAU)
MMS*
GBL* GSL*
GSL ti-GSM-PCU_devices_and_functions-00017-eps-sw
NOTE * indicates an automatically equipped device.
2-10
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Information for equipping devices
Information for equipping devices ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
This section references conditional information for the rules on equipping various devices, and the equip command prompts that occur with each of the following devices: ABSS on page 2-11
AXCDR on page 2-12
BSP on page 2-13
BSS on page 2-13
BTP on page 2-14
CAB on page 2-15
CAGE on page 2-18
CBL on page 2-19
CIC on page 2-19
COMB on page 2-21
CSFP on page 2-22
DHP on page 2-23
DPROC on page 2-24
DRI (InCell sites) on page 2-25
DRI (M-Cell and Horizonmacro sites) on page 2-27
DYNET on page 2-30
EAS (InCell sites) on page 2-32
EAS (M-Cell sites) on page 2-33
GBL on page 2-34
GCLK on page 2-36
GDS on page 2-37
GPROC on page 2-38
GSL on page 2-38
KSW on page 2-39
LMTL on page 2-39
MSI (InCell, BSC, and RXCDR sites) on page 2-40
MSI (M-Cell sites) on page 2-42
MSI (PCU only) on page 2-45
MTL on page 2-46
OML on page 2-47
OPL on page 2-47
PATH on page 2-48
PCU on page 2-51
PSI on page 2-51
PSP on page 2-52
RSL on page 2-53
RXCDR on page 2-53
SITE on page 2-54
XBL on page 2-55
ABSS Equip conditions The Associated Base Station Subsystem (ABSS) can be equipped with the system in SYSGEN ON mode. This device can also be equipped when the system is outside the SYSGEN ON mode and it is to be the standby device. An ABSS device can only be equipped at an RXCDR site. The maximum number of ABBSs that can be equipped at an RXCDR site is 10. If an ABSS device is referenced in the BSS-RXCDR connectivity table, it cannot be unequipped. The BSS-RXCDR connectivity table is created using the add_conn command.
68P02901W23-S
2-11 Nov 2009
AXCDR
Chapter 2: Equipping the CM database
Command prompts Prompt Enter the ABSS device ID:
Optional
Range
Default
Comments
N
1 - 254
None
This value corresponds to the BSS network entity that this device represents.
AXCDR Equip conditions The Associated RXCDR (AXCDR) can be equipped with the system in SYSGEN ON mode. This device also can be equipped when the system is outside the SYSGEN ON mode and it is the standby device. The AXCDR can be equipped only at a BSC that is set to remote transcoding. The maximum number of AXCDRs that can be equipped at a BSC site is 10. The AXCDR cannot be unequipped if it is referenced in the BSS-RXCDR connectivity table.
Command prompts Prompt
Optional
Range
Default
Enter the AXCDR device ID:
N
1 - 254
None
This value corresponds to the RXCDR network entity that this device represents.
Perform CIC validation?:
N
yes or no
None
CIC validation must be enabled to set eac_mode to 1 (enabled).
0 or 1
0
The eac_mode can only be set to 1 (enabled) if the AMR Enhanced Capacity feature and/or the GSM Half Rate feature is unrestricted.
Enable Enhanced Auto-Connect Mode:
2-12
Comments
Enter the CIC blocking threshold:
N
0 - 245
0
A prompt for this value is presented only if the eac_mode is enabled.
Enter the CIC unblocking threshold:
N
1 - 225
0
A prompt for this value is presented only if the eac_mode is enabled.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
BSP
BSP Equip conditions The Base Station Processor (BSP) can be equipped with the system in SYSGEN ON mode. The BSP can also be equipped when the system is outside the SYSGEN ON mode and it is to be the standby device.
Command prompts Prompt
Optional
Range
Default
Enter the BSP identifier:
N
0 or 1
None
Enter the cage number:
N
0 or 1
None
Enter the slot number:
N
20, 24, 25, 26
None
Comments
BSPs can be only GPROCs with the following Cage and Slot restrictions based on site type: BSC and BSS sites: - cage 0, slots 20, 24 - cage 1, slot 20. RXCDR sites: - cage 0, slots 25, 26 - cage 1, slot 25. BTS sites: not allowed.
BSS Equip conditions The Base Station Subsystem (BSS) must be the first device equipped by the operator during SYSGEN mode at a BSS site.
Command prompts Prompt
Optional
Range
Default
Enter the BSS identifier:
N
1 - 254
None
Is local transcoding performed at the BSC (yes/no):
N
yes or no
None
68P02901W23-S
Comments
2-13 Nov 2009
BTP
Chapter 2: Equipping the CM database
BTP Equip conditions The Base Transceiver Processor (BTP) can be equipped with the system in SYSGEN ON mode. This device also can be equipped when the system is outside the SYSGEN ON mode and it is to be the standby device. When equipping BTPs to M-Cell sites, BTP 0 must be the first BTP equipped. This device can be equipped only at a BTS site. For a bts_type of 0, no more than two radios must be equipped. For a Horizon II macro controlling cabinet, the BTP manages the auto-equip (and auto-unequip) of the MSI device 0 0 0 (with three associated MMS devices) at the BTS site. Only one BTP can be equipped at a site with a Horizon II mini master cabinet.
Command prompts The following prompts do not display for all installations. Some devices set certain parameters automatically. The system does not prompt for values set automatically. Prompt
2-14
Optional
Range
Default
Comments
Enter BTP identifier:
N
0 or 1
None
For M-Cell2 and M-Cell6 sites, this prompt has the following meaning: 0 = card frame 0, 1 = card frame 1.
Enter the cage number:
N
14 or 15
None
Enter the slot number:
N
20 or 24
None
BTPs can only be GPROCs with the following Cage and Slot restrictions based on site type: BSC, BSS, and RXCDR sites: not allowed BTS sites: - cage 15, slots 20, 24, - cage 14, slot 20.
Enter maximum DRIs supported by this BTP:
N
0 - 6
None
If the BTS type is 0, the maximum number of DRIs cannot be 0.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
CAB
CAB Equip conditions The Cabinet (CAB) can be equipped with the system in SYSGEN ON mode. This device also can be equipped when the system is outside the SYSGEN ON mode and it is to be the standby device. If the CAB is equipped for GPRS, the system rejects the equip CAB command. The CAB is automatically equipped when the PCU is equipped. If the frequency_type is not supported for the cab_type, the system rejects the equip CAB command. The following dependencies govern what type of cabinets can be equipped at different sites: •
M-Cell and transceiver cabinets cannot be equipped at site 0 (BSC).
•
M-Cell and transceiver cabinets cannot be equipped at an InCell site.
•
InCell cabinets cannot be equipped at an M-Cell site.
•
Horizon II macro and Horizon II macro extension cabinets can be combined with the following at a BTS site: M-Cell6 TCU_6 Horizon macro Horizon macro extension cabinets
Command prompts Prompt
Optional
Range
Default
Enter the CABINET identifier:
N
0 - 15
None
Enter the cabinet type:
N 0 - 27
Comments
None M-Cell and transceiver cabinets cannot be equipped at an InCell site. InCell cabinets cannot be equipped at an M-Cell site. The system rejects the command if: •
The bts_type is not 0, and
•
The cabinet_type = 10, 11, 14, 15, 16 or 20.
Enter this value either as a number or string: Continued
68P02901W23-S
2-15 Nov 2009
CAB
Chapter 2: Equipping the CM database
Prompt
Optional
Range
Default
Comments No
String
Cabinet type
0
bts4d_48v
BTS4D –48 volt
1
bts4d_27v
BTS4D +27 volt
2
bssc_48v
BSSC –48 volt
3
bssc_27v
BSSC +27 volt
4
bts_dab
BTS with DAB
5
bssc_dab
BSSC with DAB
6
excell_4
ExCell 4
7
excell_6
ExCell 6
8
topcell
TopCell
9
bts_5
BTS 5
10
m_cell_2
M-Cell 2
11
m_cell_6
M-Cell 6
12
tcu_2
TCU-2
13
tcu_6
TCU-6
14
m_cellmicro
M-Cellmicro
15
m_cellcity
M-Cellcity
16
m_cellarena
M-Cellarena
18
horizonmacro
Horizonmacro master cabinet
19
horizonmacro_ext
Horizonmacro extention cabinet
20
m_cell arena_macro
M-Cellarena macro BTS (Horizoncompact)
22
horizon micro2
Horizonmicro2 BTS
23
horizon compact2
horizoncompact2 BTS
24
horizonmacro2
HorizonIImacro cabinet
25
horizonmacro2_ext
HorizonIImacro extention cabinet
26
horizon2mini/ horizon2micro
HorizonII mini / HorizonII micro
27
horizon2mini_ext horizon2 micro_ext
HorizonII mini extension / HorizonII micro extension Continued
2-16
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Prompt
CAB
Optional
Range
N
1 to 15
Enter the frequency type:
Default
Comments
None This value can be entered by number or as a string: No
String
1
pgsm
2
egsm
3
pgsm, egsm
4
dcs1800
5
pgsm, dcs1800
6
egsm, dcs1800
7
pgsm, egsm, dcs1800
8
pcs1900
9
pgsm, pcs1900
10
egsm, pcs1900
11
pgsm, egsm, pcs1900
12
dcs1800, pcs1900
13
pgsm, dcs1800, pcs1900
14
egsm, dcs1800, pcs1900
15
pgsm, egsm, dcs1800, pcs1900
Combinations of frequency types can also be entered: •
Numbers and strings can be combined in a single command.
•
A comma must separate different frequency types, for example: pgsm, 2, 4
Horizon II macro and Horizon II macro extension cabinets can only be equipped with frequency type 1, 2, 4 or 6. {27236} For the 4 Branch Receive Diversity to be enabled, Horizon II macro and Horizon II macro extension cabinets can only be equipped with frequency types 1, 2 and 4. Is an internal HDSL modem present?:
Y
yes or no
None This prompt is only displayed if the site type is M-Cellcity, Horizonmicro or Horizoncompact.
Is an internal integrated antenna present?:
Y
yes or no
None This prompt is only displayed if the site type is M-Cellcity or Horizonmicro.
68P02901W23-S
2-17 Nov 2009
CAGE
Chapter 2: Equipping the CM database
CAGE Equip conditions A Cage (CAGE) can be equipped with the system in SYSGEN ON mode. This device also can be equipped when the system is outside the SYSGEN ON mode and it is to be the standby device. The master slots are contained in cages 0 and 1 for BSS, BSC, and RXCDR sites and in cages 14 and 15 for BTS sites. For this reason, cage 0 and/or 1 for BSS, BSC, or RXCDR type sites and cage 14 and/or 15 must be equipped at BTS type sites. If the cage is equipped for GPRS, the system rejects the equip CAGE command. The cage is automatically equipped when the PCU is equipped. At M-Cell sites, the CAGE device cannot be equipped. The cage is automatically equipped when the first BTP at a site is equipped.
Command prompts Prompt
Optional
Range
Default
Comments
Enter the device identification for the cage:
N
0 - 15
None
The cage number (ID) must be equal to the setting on the LANX card. Valid identifiers for a BSS, BSC, or RXCDR Cage are 0 to 13. Valid identifiers for a BTS cage are 2 to 15.
Enter the KSW pair that manages the cage:
N
0 - 3
None
See NOTE.
Enter the KSWX connecting cage to KSW for TDM 0:
Y
0 - 4
None
See NOTE.
Enter KSWX connecting cage to KSW for TDM 1:
Y
0 - 4
None
See NOTE.
Enter the cabinet to which the cage belongs:
N
0 - 23
None
Is an IAS connected?:
Y
yes or no
yes
NOTE Slots U2 through U7 can contain CLKX cards or KSWX cards. The system checks the contents of these slots any time a change implies the existence of a new CLKX, EXP KSWX, or remote KSWX card. The system rejects the change if the new card occupies a slot that is already occupied.
2-18
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
CBL
CBL Equip conditions The Cell Broadcast Link (CBL) can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. The CBL cannot be equipped at an RXCDR site. The CBL can be equipped only at a BSC (site 0). The CBL cannot be equipped on an HDSL link.
Command prompts Prompt
Optional
Range
Default
Enter the device ID for the CBL:
Y
0
0
Enter the first MMS identifier for this device:
N
{22169} 0 - 9
None
Enter the second MMS identifier for this device:
N
0 or 1
None
Enter the timeslot on MMS where this device appears:
N
1 - 31 for E1 links
None
Enter the BSS Operator:
N
up to 20 alphabetic characters
None
The BSS operator must be in quotation marks.
Enter the CBC Operator:
N
up to 20 alphabetic characters
None
The CBC operator must be in quotation marks.
Comments
CIC Equip conditions The Circuit Identity Code (CIC) can be equipped with the system in either SYSGEN ON or SYSGEN OFF mode. A single CIC or a range of unique CICs can be equipped for each MMS. If all CICs in the range can be equipped when equipping a range of CICs, the equip CIC command is accepted. If one or more CICs cannot be equipped, the command is still accepted. However, the CICs that cannot be equipped are listed in a display with the reason that each could not be equipped. If none of the CICs in a range can be equipped, the command is rejected and the reason displayed.
68P02901W23-S
2-19 Nov 2009
CIC
Chapter 2: Equipping the CM database
The parent MMS must be equipped before equipping the CIC. If the MMS on which the CIC is to be equipped does not appear in the CM Database, the equip CIC command is rejected. The equip CIC command is rejected if the CIC is not unique or if the timeslot/group is not available. The CIC can be equipped only at a BSC or RXCDR (site 0). The CIC cannot be equipped on an HDSL link.
Equipping CICs at a BSC When equipping a CIC at a remote transcoding BSC, the RXCDR providing the TRAU for the CIC must be specified. The operator is also prompted for a static MMS timeslot to the RXCDR. However, if the BSC is operating in static mode, it is not required. In this case, the CIC is blocked. In autoconnect (non-static) mode, the static MMS is not required. If the CIC is equipped in this way and the BSC is in backwards compatibility (static) mode, the CIC is blocked. Usually, all TRAU circuits must be equipped to GDP boards when efr_enabled is set to 1 (enabled) for the BSS.
NOTE The call downgrade feature is an exception. For example, an RXCDR has two CICs equipped. The first to an XCDR (Full rate support only) and the second to GDP (Enhanced Full and Full rate support). On the BSC, the efr_enabled is set to 1, allowing Enhanced Full rate calls on the second CIC and Full rate calls on first CIC. The TRAU circuits do need not be equipped to GDP just because efr_enabled is enabled.
Equipping CICs at an RXCDR When equipping a CIC at an RXCDR, the BSS managing the CIC must be specified. The operator also is prompted for a static MMS timeslot to the BSS. However, if the BSC is operating in static mode, it is not required. In this case, the CIC is blocked. The same CIC identifier can be equipped multiple times at an RXCDR as it can be used for multiple BSSs.
2-20
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
COMB
Command prompts Prompt
Optional
Range
Default
Enter the CIC(s):
N
0 - 65535
None
No more than 128 CICs can be equipped at a time (for remote transcoding). For RXCDR and local transcoder BSS, only 30 CICs can be equipped. Multiple CICs can be entered using the format: CIC# to CIC# (for example, 255 - 286).
Which RXCDR is providing the TRAU resource(s):
N
1 - 128
None
This prompt only appears for remote transcoding BSC sites only.
Which BSS is managing the CIC(s):
N
1 - 128
None
This prompt only appears for RXCDR sites only.
Enter the MMS ID to the RXCDR:
Y
None
This prompt only appears for remote transcoding BSC sites only.
Enter the MMS ID to the BSS:
Y
None
This prompt only appears for RXCDR sites only.
Enter starting timeslot:
N
1 - 31 (E1 links)
None
This prompt appears only if an MMS ID is specified.
Enter starting subgroup:
N
0 - 3
None
This prompt appears only if there is remote transcoding and an MMS is specified.
Enter the MMS ID to MSC:
N
None
This prompt appears for RXCDR sites and local transcodings only.
Enter starting timeslot:
N
None
This prompt appears for RXCDR sites and local transcodings only.
1 - 31 (E1 links)
Comments
COMB Equip conditions The Combiner (COMB) can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode.
68P02901W23-S
2-21 Nov 2009
CSFP
Chapter 2: Equipping the CM database
Command prompts Prompt
Optional
Range
Default
Enter the first COMBiner identifier:
N
0 - 13
None
Enter the COMBiner address:
N
0 - 255
None
Comments
The COMB address must be unique at the same site. If the COMB address is not unique, the command is rejected.
CSFP Equip conditions The Code Storage Facility Processor (CSFP) can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. At an M-Cell site, the operator cannot explicitly equip the CSFP. Instead the CSFP is automatically equipped when the first BTP at a site is equipped.
Command prompts Prompt
Optional
Range
Default
Enter the CSFP identifier:
N
0 or 1
None
This prompt only appears at a BSC.
Enter the cage number:
N
See Comments
None
BSS sites: cages 0 to 13, slots 18 to 25. BSC sites: cages 0 to 13, slots 18 to 25. BTS sites: cages 2 to 15, slots 18 to 25. RXCDR sites: cages 0 to 13, slots 25 and 26.
Enter the slot number:
N
See Comments
None
BSS sites: cages 0 to 13, slots 18 to 25. BSC sites: cages 0 to 13, slots 18 to 25. BTS sites: cages 2 to 15, slots 18 to 25. RXCDR sites: cages 0 to 13, slots 25 and 26.
Comments
NOTE A CSFP should be equipped in the same physical slots in the database between different loads during upgrade and rollback.
2-22
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
DHP
DHP Equip conditions The Digital Radio Host Processor (DHP) can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. The DHP can be equipped only at a BSS or a BTS site. The DHP cannot be equipped at an M-Cell site. The underlying GPROC need not be equipped to equip a DHP.
Command prompts Prompt
Optional
Range
Default
Comments
Enter the cage number for this DHP (identifier 1):
N
0 - 15
None
This identifier must be equal to the cage number where the DHP is to reside. A maximum of eight GPROCs can exist in a single cage.
Enter the unique DHP number in this cage (identifier 2):
N
0 - 7
None
BSS sites: cages 0 to 13: slots 18 to 25. BTS sites: cages 2 to 15: slots 18 to 25.
Enter the slot number:
N
18 - 25
None
Enter the maximum number of DRIs supported by this DHP:
N
1 - 6
None
NOTE The modify_value parameter max_dris is automatically set to 6, which is the maximum number of DRIs supported by a DHP.
68P02901W23-S
2-23 Nov 2009
DPROC
Chapter 2: Equipping the CM database
DPROC Equip conditions The Data Processor (DPROC) can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. The DPROC can be equipped only if the GPRS feature is unrestricted. The DPROC can be equipped only at a GPRS PCU site. A DPROC can be equipped in the PCU cabinet to be used as a Packet Interface Control Processor (PICP) or a Packet Resource Processor (PRP) or a processor with PRP and PICP function (PXP).. At least one PRP and one PICP DPROC are required per PCU. A PICP DPROC can support 0 to 2 LAPD GDS devices. A PRP DPROC can support from 0 to 4 TRAU GDS devices. There can be a maximum of 10 PRP DPROCs equipped per PCU DPROCs are not redundant.
NOTE A DPROC can be equipped only if the PCU is equipped.
Command prompts Prompt
2-24
Optional
Range
Default
Enter the DPROC ID:
N
1 - 6 or 11 - 16
None
Enter the DPROC type:
N
PICP or PRP or PXP
None
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
DRI (InCell sites)
DRI (InCell sites) Equip conditions The Digital Radio Interface (DRI) for a InCell site can only be equipped at a BSS or a BTS site. The DRI can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. If an RTF device ID is to be entered for a DRI, the RTF must be equipped before the DRI. If a DRI is added to an existing group (same first identifier), the GSM cell ID of the new DRI must be like the other DRIs in the group. If the Cell ID is different, the equip DRI command is rejected. DRIs/RTFs within a dual band cell with different frequency types must have different DRI/RTF group identifiers. The equip RTF command allows two group identifiers for a cell only if the cell is dual band. The equip cabinet command allows the secondary and primary band frequency types in each zone to which the DRIs are equipped. A DRI can be equipped to a Horizon II mini cabinet using antenna_select values of 1 or 2 only. A Horizon II mini cabinet supports a maximum of two CTU2s and two cells. Thus, dependent on whether the CTU2s are single or double density equipped, 1 to 4 DRIs are allowed. That is, 1 DRI per single density CTU2, and 2 DRI per double density CTU2.
Command prompts Prompt
Optional
Range
Default
Comments
Enter the 1st and 2nd DRI ID:
N
First: 0 - 5, Second: 0 - 11
None
This identifier indicates a user-defined redundancy group within a cell. To qualify a redundancy group, a DRI must be connected to the same antenna as the rest of the group. Also, the DRI must be using the same portion of the TDM highway.
Enter the cabinet identifier:
N
0 - 15
None
If the cabinet ID does not exist in the database the system rejects the command.
Enter the DRI board type:
N
drim or 0
None
Enter the cage number:
N
0 - 15
None
This prompt is presented only if the entered board type is DRIM.
Enter the slot number:
N
7 - 17
None
This prompt is presented only if the entered board type is DRIM. Odd values only. Continued
68P02901W23-S
2-25 Nov 2009
DRI (InCell sites)
Chapter 2: Equipping the CM database
Prompt
2-26
Optional
Range
Default
Comments
Enter the TRU identifier:
Y
0 - 6
0
This prompt is presented only if the entered board type is DRIM. No entry or a zero entered for this field represents a non-Top Cell Radio Unit (TRU).
Enter the 1st and 2nd RTF ID:
Y
0 - 5, 0 - 11
None
The RTF entered in this field must be equipped. One DRI prefers the RTF. If another DRI prefers the RTF, the system rejects the command.
Enter the GSM cell ID where the DRI appears:
N
GSM cell ID or cell_name
None
The cell number can be in either seven parameter format or four parameter format.
Enter antenna select number for this cell:
N
1 - 6
None
Enter COMB 1st and 2nd ID:
Y
0 - 13, 0 or 1
None
Enter cavity number:
Y
0 - 5
Enter the diversity flag for this DRI:
N
{27236} 0 - 2
None
Does this DRI use tuneable combining:
Y
yes or no
yes
Enter the tuneable combining type:
Y
0, 1, or 2
0
Prompted only when DRI uses tuneable combining. 0 = none 1 = non-controlling 2 = controlling
Enter the COMB identifier:
N
0 - 13
None
Prompted only when DRI uses tuneable combining.
Enter the cavity number for this COMB:
N
0 - 5
None
Prompted only when DRI uses tuneable combining.
Enter the fm cell type:
N
0 - 4
None
0 = non-diversity 1 = 120 degree cell (not currently supported) 2 = 60 degree cell (not currently supported) 3 = shared diversity (not currently supported) 4 = full diversity
COMB must be separately equipped. This prompt is displayed only if COMB ID is entered for the previous prompt. {27236} 0 = no rx diversity 1 = 2 branch rx diversity 2 = 4 branch rx diversity
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
DRI (M-Cell and Horizonmacro sites)
DRI (M-Cell and Horizonmacro sites) Equip conditions The Digital Radio Interface (DRI) for an M-Cell or a Horizonmacro site can be equipped only at a BSS or a BTS site. The DRI can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. If an RTF device ID is to be entered for a DRI being equipped, the RTF must be equipped before the DRI. If a DRI is added to an existing group (same first identifier), the GSM cell ID of the new DRI must be like the other DRIs in the group. If the Cell ID is different, the equip command is rejected. Two DRI devices can be associated with each other (double density). Neither DRI has a higher precedence than the other in the DRI pair. When equipping DRIs in a single Horizon II macro cabinet for a Dual Band configuration, the system checks for the correct Dual Band cabinet setup. That is, all 900 MHz radios in either slots 0–2 or 3–5, with the 1800 MHz radios being equipped in the other three slots. A Horizon II macro cabinet with frequency_type supporting Dual Band can be equipped with radios supporting a single frequency. {27236} For enabling the 4 Branch Receive Diversity, the DRIs must be equipped in a single Horizon II macro cabinet for single band configuration.
Command prompts Prompt
Optional
Range
Default
Comments
Enter the 1st and 2nd DRI ID:
N
0 - 5, 0 - 11
None
This identifier is used to identify a user-defined redundancy group within a cell. To qualify a redundancy group, a DRI must be connected to the same antenna as the rest of the group. Also, the DRI must be using the same portion of the TDM highway.
Enter the density of this DRI:
N
1 (single) or 2 (double)
1 (single)
When double density is specified, the operator is not prompted for tuneable combining.
Enter the 2nd DRI ID of the associated DRI:
Y
0 - 11
None
This parameter specifies the DRI identifier to be used for the auto-equipped DRI in a DRI pair.
Enter the cabinet identifier:
N
0 - 15
None
The system rejects attempts to equip a DRI in DCS1800 Horizonmacro cabinet if tx_power_cap= 0. Continued
68P02901W23-S
2-27 Nov 2009
DRI (M-Cell and Horizonmacro sites)
Prompt
Chapter 2: Equipping the CM database
Optional
Range
Default
Comments
Enter the type of connection to the BTP:
N
Enter the Port to which the TCU is connected:
N
0 - 5
None
If the entry to the previous prompt is 4 or ‘direct’, the maximum value is 1. If cabinet type is Horizonmacro II, a check is made for valid Dual Band DRI configuration. The tcu_port value is restricted to 0 or 1 for a Horizon II mini cabinet type.
Enter the 1st and 2nd RTF ID:
Y
0 - 5, 0 - 11
None
The RTF entered in this field must be equipped.
Enter the GSM cell ID where the DRI appears:
N
GSM cell ID or cell_name
None
The cell number can be in either seven parameter format or four parameter format.
Enter antenna select number for this cell:
N
1 - 3
None
This number configures the Integrated Antenna Distribution Unit (IADU): If the receive antenna is connected to DLNB 0 in the cabinet supporting the transceiver, set the antenna_select number to 1. If the receive antenna is connected to DLNB 1, set the antenna_select to 2. If the receive antenna is connected to DLNB 2, set the antenna_select to 3. If the antenna_select number is entered incorrectly, the wrong receive antenna is connected to the transceiver.
None 0 or fox (0 or master for Horizonmacro master cabinets) 1 or fmux0 2 or fmux1 3 or fmux2 4 or direct
This value can be entered as a number or its associated character string. An FMUX can be used only if the BTP resides in an M-Cell6 cabinet.
Continued
2-28
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Prompt
DRI (M-Cell and Horizonmacro sites)
Optional
Range
Default
Comments For the Horizonmacro, this number configures the 1800 Sectorized Universal Receive Filter (SURF): If the receive antenna is connected to the Rx ANT 0A/0B in the cabinet supporting the CTU, set the antenna_select number to 1. If the receive antenna is connected to the Rx ANT 1A/1B in the cabinet supporting the CTU, set the antenna_select number to 2. If the receive antenna is connected to the Rx ANT 2A/2B in the cabinet supporting the CTU, set the antenna_select number to 3. If the receive antenna is connected to the Rx ANT 900 0A/0B in the cabinet supporting the CTU, set the antenna_select number to 2.
NOTE 2 is the default value and does not work with any other selection The antenna_select value is restricted to 1 or 2 for a Horizon II mini cabinet type. None
Enter COMB 1st and 2nd ID:
Y
0 - 13, 0 or 1
Enter cavity number:
Y
0 - 5
Does this DRI use tuneable combining:
Y
yes or no
None
If the DRI is equipped to the following cabinets, the system does not prompt for combiner information: HORIZONMACRO2, HORIZONMACRO2_EXT, HORIZON2MINI, or HORIZON2MINI_EXT.
Enter the tuneable combining type:
Y
0, 1 or 2
None
0 = none 1 = non-controlling 2 = controlling
COMB must be separately equipped. This prompt displays only if COMB ID is entered for the previous prompt.
Continued
68P02901W23-S
2-29 Nov 2009
DYNET
Chapter 2: Equipping the CM database
Prompt
Optional
Range
Default
Enter the COMB identifier:
N
0 - 13
None
Enter the cavity number for this COMB:
N
0 - 5
None
Enter the diversity flag for this DRI:
N
{27236} 0 - 2
None
{27236} 0 = no rx diversity 1 = 2 branch rx diversity 2 = 4 branch rx diversity
Enter the fm cell type:
N
0 - 4
None
0 = non-diversity. 1 = 120 degree cell (not currently supported) 2 = 60 degree cell (not currently supported) 3 = shared diversity (not currently supported) 4 = full diversity
Comments
DYNET The Dynamic Network of BTSs (DYNET) shares terrestrial backing resources. The network can include timeslot switching sites.
Equip conditions All DYNETs that share the same first identifier must have the same BTSs or timeslot switching sites in the same order. Also, these DYNETs must have different E1 links used by the BTSs within the BTS network. These limitations allow definition of multiple link BTS networks for sharing purposes, while limiting the configuration to simplify sharing. An open loop DYNET has an automatically equipped PATH for an open loop daisy chain, with a second identifier equal to the second identifier of the DYNET times two. A closed loop DYNET has two PATHs automatically equipped. The identifier of the first PATH is equal to the identifier of the DYNET multiplied by 2. The identifier of the second PATH is equal to the identifier of the DYNET multiplied by 2 and with 1 added. The automatically equipped PATH in closed loop daisy chains has a second identifier one greater than second identifier of the first PATH automatically equipped. The identifiers of the PATHs that can be automatically equipped when a DYNET is equipped are not allowed when equipping or unequipping the PATH device. The system does not verify whether this feature is available when a DYNET is equipped.
2-30
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
DYNET
Command prompts Prompt
Optional
Range
Default
Enter 1st and 2nd unique DYNET identifiers:
N
First identifier: 0 - 19, Second identifier: 0 - 2
None
If the ID exists in the database, the command is rejected.
Enter BSC MMS identifier:
N
0 - 890 or 1
None
This prompt requires two values:
Comments
•
The first value is the MSI at the BSC where the MMS resides.
•
The second value is the MMS for the BSC network definition.
Enter SITE identifier:
N
0 - 140 ts_switch, BSC
None
The TS site number, timeslot switching site, or the BSC.
Enter the upstream MMS identifiers:
N
For BTS4, BTS5, BTS6, TopCell, and ExCell: 0 - 9, 0 or 1. For M-Cell2: 0 - 1, 0 - 1. For M-Cell6: 0 - 3, 0 - 1.
None
This prompt requires two values:
For BTS4, BTS5, BTS6, TopCell, and ExCell: 0 - 9, 0 or 1. For M-Cell2: 0 - 1, 0 - 1. For M-Cell6: 0 - 3, 0 - 1.
None
Enter the downstream MMS identifiers:
68P02901W23-S
Y
•
The first value is the MSI at the BTS where the MMS resides.
•
The second value is the MMS for the BTS network definition.
This prompt requires two values: •
The first value is the MSI at the BTS where the MMS resides.
•
The second value is the MMS for the BTS network definition.
This prompt can be left blank.
2-31 Nov 2009
EAS (InCell sites)
Chapter 2: Equipping the CM database
EAS (InCell sites) Equip conditions The External Alarm System (EAS) for sites that are InCell sites can be equipped with the system in either SYSGEN ON or SYSGEN OFF mode.
Command prompts Prompt
Optional
Range
Default
Comments
Enter the first device ID for the EAS:
N
0 - 7
None
If the ID exists in the database the command is rejected.
Enter the cage where the PIX is connected:
N
0 - 15
None
Enter the daughter slot where the PIX is located:
N
15 - 18
None
Enter the relay wiring of the 4 relays:
N
0 or 1
None
Enter four values, each separated by a space.
Enter the no alarm condition for the 8 optos (0 - closed, 1 - open):
N
0 or 1
None
Enter eight values, each separated by a space.
Enter each opto whose state changes are to be reported:
N
1 - 8
None
Enter eight values, each separated by a space.
Enter the user defined alarm index for the 8 optos:
N
0 - 33
None
Enter eight values, each separated by a space. Enter the string ‘mpf’ in place of one of the integers to indicate which opto is used for the EAS Mail Power Failure alarm.
Enter each opto whose state changes are to be reported:
Y
1 - 8 for InCell sites. 1 - 16 for M-Cell sites.
None
Operator can enter up to 8 values for an InCell site and up to 16 values for an M-Cell site. Separate values with either a space or a comma. If no value is entered in the range prompt, then no state changes are reported for any optocoupler. The values can be entered in any order. The operator also has the option of entering ‘all’ and of entering a range of optos. Continued
2-32
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
EAS (M-Cell sites)
Prompt
Optional
Range
Default
Enter the user defined alarm index for opto n:
Y
0 - 33 and 128
None
Comments The operator must enter one value indicating the index of the user-defined alarm string for the optocoupler specified by 'n'. The text string ‘mpf’ is interpreted as the value 128. No default is accepted for this prompt. A prompt is displayed for each reporting optocoupler specified in the previous prompt.
EAS (M-Cell sites) Equip conditions The External Alarm System (EAS) for M-Cell sites can be equipped with the system in either SYSGEN ON or SYSGEN OFF mode. When equipping the EAS, the physical wiring of each relay must be specified. Whether the relay is open or closed when deactivated must also be specified. All relays are deactivated during site initialization. Once the EAS is Busy-Unlocked, the relay state is controlled by using the set_relay_contact command. Only opto reporting for alarms 1 to 12 can be enabled or disabled for a Horizon II mini cabinet type.
68P02901W23-S
2-33 Nov 2009
GBL
Chapter 2: Equipping the CM database
Command prompts Prompt
Optional
Range
Default
Enter the first device ID (Cabinet ID) for the EAS:
N
0 - 15
None
Cabinet identifier.
Enter the relay wiring of the 4 relays:
N
0 or 1
None
0 = deactivate the relay 1 = activate the relay Enter four values, each separated by a space.
Enter the no alarm condition for the 16 optos (0 closed, 1 - open):
N
0 or 1
None
Enter 16 values, each separated by a space. Only 12 optos are available for Horizon II mini.
Enter each opto whose state changes are to be reported:
N
1 - 16
None
Enter 16 values, each separated by a space. Only 12 optos are available for Horizon II mini.
Enter the user defined alarm index for the 16 optos:
N
0 - 33
None
Enter 16 values, each separated by a space. Enter the string ‘mpf’ in place of one of the integers to indicate which opto is used for the EAS Mail Power Failure alarm. Only 12 optos are available for Horizon II mini.
Comments
GBL The Gb Link (GBL) is the communication link between the PCU cabinet and the SGSN.
Equip conditions This device can be equipped with the system in either SYSGEN ON or SYSGEN OFF mode. The GBL can be equipped only if the GPRS feature is unrestricted. To support EGPRS the GBL bandwidth between the PCU and the SGSN has been increased. The amount of bandwidth necessary for a maximal configured PCU is 12 E1s of GBL, and for a maximal configured BSS is 20 E1s. This maximum number of GBLs can be configured independent of whether EGPRS is restricted or not.
2-34
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
GBL
Command prompts Prompt
Optional
Range
Default
Enter the GBL identifier:
N
0 - 35
None
Unique identifier of the GBL.
Enter the 1st and 2nd MMS identifier:
N
0 - 23, 0 - 1
None
A GBL must be equipped on a DPROC PICP MSI at a PCU. A GBL must not be equipped to an MMS on the last PICP MSI which is designated for code download, when a default GSL has not already been equipped.
Enter the starting timeslot:
N
1 - 31
None
Element name start_ts. First GBL timeslot on the span.
Enter the ending timeslot:
N
1 - 31
None
Element name end_ts. Last GBL timeslot on the span.
Enter the t391 timer:
Y
5 - 29
10
Element name t391. Value of the Frame Relay default Link Integrity Verification Polling Timer in seconds.
Enter the t392 timer:
Y
6 - 30
15
Element name t392. Value of the Frame Relay default Polling Verification Timer in seconds.
Enter the n391 counter:
Y
1 - 255
6
Element name n391. Frame Relay default Full Status Polling Counter, as number of polling cycles.
Enter the n392 counter:
Y
1 - 10
3
Element name n392. Frame Relay default value for Error Threshold Counter, as number of errors.
Enter the n393 counter:
Y
1 - 10
6
Element name n393. Frame Relay default value for Monitored Events Counter, as number of events.
Comments
NOTE The Frame Relay Access Rate ns_access_rate (in kbit/s) is not prompted for as it is calculated from ((end_ts + 1) - start_ts) * 64, then defaulted to this value.
68P02901W23-S
2-35 Nov 2009
GCLK
Chapter 2: Equipping the CM database
GCLK Equip conditions The Generic Clock (GCLK) can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. The GCLK cannot be explicitly equipped at M-Cell sites. This device is automatically equipped when a BTP is equipped. Some devices do not require all the prompts. Therefore, the system cannot always display all the prompts provided in the next section.
Command prompts Prompt
Optional
Range
Default
Comments
Enter the device identification for the GCLK:
N
0 or 1
None
The GCLK slot is assigned based on the device ID: If the device ID is set to 0, the GCLK is assigned to slot 5. If the device ID is set to 1, the GCLK is assigned to slot 3.
Enter the cage number:
N
0 - 15
None
Is CLKX 0 (slot U7) present?
Y
yes or no
no
The slot number displayed in the prompt depends on the GCLK ID. The alternate slot number for GLKX 0 is U4. (See also NOTE.)
Is CLKX 1 (slot U6) present?
Y
yes or no
no
The slot number displayed in the prompt depends on the GCLK ID. The alternate slot number for GLKX 1 is U3. (See also NOTE.)
Is CLKX 2 (slot U5) present?
Y
yes or no
no
The slot number displayed in the prompt depends on the GCLK ID. The alternate slot number for GLKX 2 is U2. (See also NOTE.)
NOTE Slots U2 through U7 can contain CLKX cards or KSWX cards. The system checks the contents of these slots any time a change implies the existence of a new CLKX, EXP KSWX, or remote KSWX card. The system rejects the change if the new card occupies a slot that is already occupied.
2-36
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
GDS
GDS Equip conditions This device can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. The GPRS Data Stream (GDS) can be equipped only if the GPRS feature is unrestricted. A GDS must not be unequipped until all GSLs on that GDS have been unequipped.
NOTE Locking the GDS causes the GSLs to go OOS. This differs from pre-GSR9 behavior where there was no hierarchal relationship between the GDS and the GSL. The BSS rejects an attempt to equip a GDS to an MMS at the BSC where the mms_priority of the MMS is a non-zero value. The GDS device allows a maximum of 72 E1 links to be configured as TRAU GDS per BSS. The device also allows a maximum of 36 E1 links to be configured as TRAU GDS per PCU. The maximum number of TRAU GDSs that can be configured is independent of whether EGPRS is restricted or not. The number of LAPD GDS devices is two per PCU and six per BSS.
Command prompts Prompt
Optional
Range
Default
Enter the GDS identifier:
N
0 - 37
None
Enter the GDS connectivity:
N
E1 or ETHERNET
Notes Unique identifier of the GDS.
None
When GDS connectivity is equal to ETHERNET, the following will be prompted: Enter the BSC ETH identifier:
N
None
Enter the PCU ETH identifier:
N
None
When GDS connectivity is equal to E1, the following will be prompted: Enter the BSC MMS identifier:
N
0 - 95, 0 - 1
None
Enter the PCU MMS identifier:
N
0 - 23, 0 - 1
None
Enter the GDS type:
N
TRAU or LAPD
None
NOTE BSC MMSs which are equipped to GDS devices cannot be selected as clock sources.
68P02901W23-S
2-37 Nov 2009
GPROC
Chapter 2: Equipping the CM database
GPROC Equip conditions The Generic Processor (GPROC) can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. This device cannot be equipped at M-Cell sites.
Command prompts Prompt
Optional
Range
Default
Enter the GPROC identifier:
N
1 - 111
None
Enter the cage number:
N
See Comments
None
Valid cage numbers are dependent on the site: BSS sites: cages 0 to 13. BSC sites: cages 0 to 13. BTS sites: cages 2 to 15. RXCDR sites: cages 0 to 13.
Enter the slot number:
N
See Comments
None
Valid slot numbers are dependent on the site: BSC, BSS, and BTS sites: slots 18 to 25. RXCDR sites: slots 25 to 26.
Comments
GSL Equip conditions The GPRS Signaling Link (GSL) can be equipped only if the GPRS feature is unrestricted. The GSL can be equipped with the system in either SYSGEN ON or SYSGEN OFF mode. The equipage of a GSL is allowed only if the remaining GDS timeslot resources available to the PCU are sufficient to support the GPRS timeslot resources for cells for which GPRS is enabled. The GSL is allowed only on an LAPD GDS. 30 GSLs can be equipped to a LAPD GDS. All 60 could be equipped to one DPROC that has two GDSs equipped on it. However, for redundancy, two DPROCs are required each with a LAPD GDS equipped with 30 GSLs. To bring the GSL in service, unlock the GSL at either the OMC-R or MMI prompt.
NOTE The equip GSL command fails if the total max_gsls for all LCFs becomes less than the total number of equipped GSLs.
2-38
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
KSW
Command prompts Prompt
Optional
Range
Default
Enter the GSL identifier:
N
0 - 59
None
Enter the unique GDS identifier:
N
0 - 37
None
Notes
KSW Equip conditions The Kiloport Switch (KSW) can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. The KSW cannot be equipped at M-Cell sites.
Command prompts Prompt
Optional
Range
Default
Comments
Enter Portion of TDM Highway Managed (identifier 1):
N
0 - 3
None
The first device ID for the KSW must match the KSW pair in the cage where the KSW is being equipped.
Enter TDM identifier (identifier 2):
N
0 or 1
None
The KSW slot is assigned based on the second device ID; If the second device ID is set to 0, the KSW is assigned to slot 27. If the second device ID is set to 1, the KSW is assigned to slot 1.
Enter the cage number:
N
0 - 15
None
Are DRIs allowed on highway managed by this KSW:
N
Y or N
None
This prompt does not occur at a BSC.
LMTL The Location Message Transfer Link (LMTL) device applies only to the BSC (location 0).
68P02901W23-S
2-39 Nov 2009
MSI (InCell, BSC, and RXCDR sites)
Chapter 2: Equipping the CM database
Equip conditions The Location Services feature must be unrestricted. For LMTLs to be equipped, the BSC must be configured to support a BSS-based SMLC. When an LMTL is equipped on an MMS that hosts other non-Lb-interface links, a warning message displays indicating a conflict in MMS timeslot usage.
Command prompts Prompt
Optional
Range
Default
Enter the device identification for this LMTL:
N
0 - 15
None
Enter the first MMS identifier for this device:
N
0 or 95
None
Enter the second MMS identifier for this device:
N
0 - 1
None
Enter the timeslot on MMS where this device appears:
N
31 (E1)
None
Comments Location Services must be unrestricted.
MSI (InCell, BSC, and RXCDR sites) Equip conditions The Multiport Serial Interface (MSI) for InCell, BSC, or RXCDR sites can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. An MSI with msi_type of msi_ext_hdsl cannot be equipped with the protocol types of both MMSs entered as E1 at a BSC or an InCell BTS site.
Command prompts Prompt
Optional
Range
Default
Enter the device identification for the MSI:
N
{22169} BSC: 0 - 95 RXCDR: 0 123 BTS: 0 - 9 (InCell)
None
Enter the cage number:
N
0 - 15
None
Comments
Continued
2-40
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Prompt
MSI (InCell, BSC, and RXCDR sites)
Optional
Range
Default
Comments
Enter the slot number:
N
BSS and BSC sites: All MSI type slots 6 - 17. BTS sites: MSI type 0 slots 6 - 17, MSI type 1 or 2 not allowed. RXCDR sites MSI type 0 slots 6 - 10, MSI type 1 or 2 slots 6-24
None
Valid slot numbers are based on site type and MSI type.
Enter the MSI type:
N
0 or msi, 1 or xcdr, 2 or gdp, 7 or msi_ext_hdsl, 12 or RF_unit, 20 or gdp2.
None
The input can be the numeric value or the text string. (The value of 5 is reserved.) MSI types xcdr or gdp are only allowed at sites where transcoding occurs.
Enter MMS0 protocol type:
Y
E1 or HDSL
HDSL
Prompt appears only if the Integrated MCell HDSL feature is enabled, and the msi_type is niu_hdsl, niu_ext_hdsl, or msi_ext_hdsl.
Enter the number of timeslots supported on MMS0:
Y
16 or 32
32
Prompt appears only if the Integrated MCell HDSL feature is enabled, and the MSI type is niu_hdsl, niu_ext_hdsl, or msi_ext_hdsl, and the protocol type is HDSL.
Enter MMS0 modem setting:
Y
master or slave
None
Prompt appears only if the Integrated MCell HDSL feature is enabled, the protocol is HDSL, and the MSI type is niu_hdsl.
Enter MMS1 protocol type:
Y
E1 or HDSL
HDSL
Prompt appears only if the Integrated MCell HDSL feature is enabled, and the MSI type is niu_hdsl, niu_ext_hdsl, or msi_ext_hdsl. Continued
68P02901W23-S
2-41 Nov 2009
MSI (M-Cell sites)
Chapter 2: Equipping the CM database
Prompt
Optional
Range
Default
Comments
Enter the number of timeslots supported on MMS1:
Y
16 or 32
32
Prompt appears only if the Integrated MCell HDSL feature is enabled, and the msi_type is msi_ext_hdsl, with a protocol type of HDSL for this MMS.
Enter MMS1 modem setting:
Y
master or slave
None
Enter the MSI ID to the MSC:
Y
{22169} BSC: 0 - 95 RXCDR: 0 123
Value of GDPs own MSDI ID
MSI identifier of GDP with MMS available for routing the transcoding circuits of a secondary GDP towards the MSC. Read-Write (can be set only when the MSI device is created).
0
Value of GDPs own second ID
MSC MMS always zero because MSIs cannot provide MSC MMSs. Read-Write (can only be set when the MSI device is created). Prompt appears only if MSI type entered as 2 or gdp.
None
Prompt appears only if MSI type entered as 2 or gdp, or as 20 or gdp2.
Enter the transcoding capability:
N
0 or Basic, 1 or Enhanced, 2 or GDP_2E1.
Prompt appears only if the Integrated MCell HDSL feature is enabled, the protocol is HDSL, and the msi_type is niu_hdsl.
NOTE The default values in the table apply only if nothing is entered at the prompts.
MSI (M-Cell sites) Equip conditions The Multiport Serial Interface (MSI) for M-Cell sites can be equipped with the system in either the SYSGEN ON or SYSGEN OFF mode. M-Cell sites do not use MSI boards. The Network Interface Unit (NIU) performs the MSI function in an M-Cell2 or M-Cell6 cabinet. That is why the system prompts refer to the NIU.
2-42
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
MSI (M-Cell sites)
•
The msi_type of niu_hdsl is only supported at M-Cellcity, Horizon micro or Horizon compact sites.
•
The msi_type of niu_ext_hdsl is supported at M-Cell2, M-Cell6, M-Cellcity, M-Cellmicro, Horizon micro, and Horizon compact sites.
•
A warning is issued if the protocol types of both MMSs of an MSI, with an msi_type of niu_hdsl at an M-Cellcity, M-Cellmicro, Horizon micro, or Horizon compact site, are entered as E1.
•
An MSI with msi_type of niu_ext_hdsl cannot be equipped with the protocol types of both MMSs entered as E1 at an M-Cell2, M-Cell6, M-Cellmicro, M-Cellcity, Horizon micro or Horizon compact site.
•
The msi_type niu_ext_hdsl can be equipped in slot 1 of a card frame (at an M-Cell6 site) only if the protocol type of MMS0 is entered as HDSL.
•
When equipping an HDSL NIU, the new hdsl_oos_mon_period and hdsl_restore_mon_period durations default to known software values.
NOTE The default values in the following table apply only if nothing is entered at the prompts.
Command prompts Prompt
Optional
Range
Default
Enter the device identification for the MSI:
N
See comments
None
M-Cell 2 BTS: 0 or 1 M-Cell 6 BTS: 0 to 3 M-Cellmicro: 0
Enter the MCU card frame in which the NIU exits:
N
0 or 1 (See comments)
None
0 is the only valid value for this field if equipping to M-Cellmicro.
Enter the NIU slot number:
N
0 or 1 (See comments)
None
0 is the only valid value for this field if equipping to M-Cellmicro and M-Cell2.
Enter the MSI type:
N
3 or niu, 8 or niu_hdsl, 9 or niu_ext_hdsl
niu
The input can be either the numeric value or the text string.
Enter the MMS0 protocol type:
Y
E1 or HDSL
HDSL
If the Integrated MCell HDSL feature is enabled, and the msi_type is niu_hdsl or niu_ext_hdsl, the prompt appears.
Comments
Continued
68P02901W23-S
2-43 Nov 2009
MSI (M-Cell sites)
2-44
Chapter 2: Equipping the CM database
Prompt
Optional
Range
Default
Comments
Enter the number of timeslots supported on MMS0:
Y
16 or 32
32
If the Integrated MCell HDSL feature is enabled, and the msi_type is niu_hdsl or niu_ext_hdsl, with a protocol type of HDSL for this MMS, the prompt appears.
Enter MMS0 modem setting:
Y
master or slave
master
If the Integrated MCell HDSL feature is enabled, and the msi_type is niu_hdsl with a protocol type of HDSL for this MMS, the prompt appears
Enter the MMS1 protocol type:
Y
E1 or HDSL
HDSL
If the Integrated MCell HDSL feature is enabled, and the msi_type is niu_hdsl, or niu_ext_hdsl, the prompt appears.
Enter the number of timeslots supported on MMS1:
Y
16 or 32
32
If the Integrated MCell HDSL feature is enabled, and the msi_type is niu_hdsl or niu_ext_hdsl with a protocol type of HDSL for this MMS, the prompt appears.
Enter MMS1 modem setting:
Y
master or slave
slave
If the Integrated MCell HDSL feature is enabled, and the msi_type is niu_hdsl with a protocol type of HDSL for this MMS, the prompt appears.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
MSI (PCU only)
MSI (PCU only) Equip conditions The Multiport Serial Interface (MSI) for PCU sites can be equipped with the system in SYSGEN ON mode. This device can also be equipped when the system is outside the SYSGEN ON mode. The site must not be locked when this device is equipped outside SYSGEN ON mode. A modified MSI device is used to describe the serial interface device which can be equipped to DPROC boards. It is a child class of PCU. The GPRS MSI type is not available when the GPRS feature is restricted. The BSS supports equipage of a GBL to a PICP MMS. The BSS supports equipage of a GDS at the PCU. The BSS supports equipage of a GDS to an HDSL MSI when the child MMS of the MSI is of type E1. The BSS does not support the modification of the msi_type for an MSI. The BSS supports equipage of up to two MSIs per DPROC board. A DPROC board must be equipped before an MSI can be equipped to the same DPROC. The PCU supports a unique identifier for each MSI equipped within the PCU. Two MMS devices are automatically equipped with each PCU MSI equip. All MMSs on the same MSI must be configured for the same destination: BSC or SGSN. If only one MSI is available, then the MSI must be equipped in PMC socket 1 of a DPROC in either slot 1 or slot 2.
Command prompts Prompt
Optional
Range
Default
Enter the MSI identifier:
N
0 - 23
None
The MSI identifier.
Enter the DPROC ID:
N
1 or 6 11 - 16
None
The identifier of the DPROC in the PCU cabinet on which the MSI resides. Only appears if the MMS ID to the MSC was not entered, or was the same as the MSI device identifier of the device being equipped.
Enter the DPROC socket:
N
1 or 2
None
PMC module identifier on the DPROC board to which the MSI is being equipped.
68P02901W23-S
Comments
2-45 Nov 2009
MTL
Chapter 2: Equipping the CM database
MTL Equip conditions The Message Transfer Links (MTL) is not allowed at an RXCDR site and can be equipped only at site 0. The MTL cannot be equipped on an HDSL link. The MTL can be equipped only at the BSC.
Command prompts Optional
Range
Default
Enter the device identification for this MTL:
Prompt
N
0 - 15
None
{28337} Enter the number of DSO channels for this MTL:
N*
1: 64 kbps MTL 31: HSP MTL Other values reserved
1
Enter the first MMS description for this device:
N
0 - 123
None
Enter the second MMS description for this device:
N
0 or 1
None
N**
1 - 31 (E1)
None
Enter timeslot on MMS where this device appears:
NOTE {28337} •
* Only when the increased network capacity feature is unrestricted, this value can be set to 31. If the user attempts to equip 64 kbps MTLs after the mtl_rate of existing MTL has already been set to 31, the equip command is rejected. If the user attempts to equip an HSP MTL while the mtl_rate has already been set to 1, the equip command is rejected.
•
** If the mtl_rate is 31, this value must be 1.
If an MMS has another timeslot that conflicts when equipping an MTL, the system generates the following warning: COMMAND ACCEPTED: WARNING: Conflict in MMS usage, display timeslot usage to verify. Conflicting usage exists when at least one timeslot provides connectivity to a BTS and another is connected to a different type of device. That is, RXCDR, OML, and so on.
2-46
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
OML
OML Equip conditions The Operations and Maintenance Link (OML) cannot be equipped on an HDSL link. The OML can be equipped only at site 0.
Command prompts Prompt
Optional
Range
Default
Enter the device ID for the OML:
N
0 - 3
None
Enter the first MMS description for this device:
N
BSC: 0 - 95 RXCDR: 0 - 123
None
Enter the second MMS description for this device:
N
0 or 1
None
Enter timeslot on MMS where this device appears:
N
E1: 1 - 31
None
If an MMS has another timeslot that conflicts when equipping an OML, the system generates the following warning:COMMAND ACCEPTED: WARNING: Conflict in MMS usage, display timeslot usage to verify. Conflicting usage exists when at least one timeslot provides connectivity to a BTS and another is connected to a different type of device. That is, RXCDR, OML, and so on.
OPL Equip conditions The Optimization Link (OPL) is used to carry measurement report data out of the BSC. The link is a dedicated 64 kbit/s link HDLC link between the BSC and the IOS platform equipped to a E1 timeslot on an existing MMS. To equip the OPL follow the given steps: 1.
Select the least utilized LCF on BSC.
2.
Modify the selected LCF to support OPL using the command modify_value bsc max_opls 1 lcf
3.
Equip OPL on the desired timeslot.
NOTE OPL cannot be equipped on the LCF controlling a CBL.
68P02901W23-S
2-47 Nov 2009
PATH
Chapter 2: Equipping the CM database
Command prompts Prompt
Optional
Range
Default
Enter the device ID for the OPL
N
0 - 3
None
Enter the first MMS identifier for this device
N
BSC: 0 - 95 RXCDR: 0 - 123
None
Enter the second MMS identifier for this device
N
0 or 1
None
Enter the timeslot on MMS where this device appears
N
E1: 1 - 31
None
PATH Equip conditions The Path (PATH) can be equipped when the system is in either the SYSGEN ON or SYSGEN OFF mode. Prompts to equip a path are presented for each link in the path. If one of the MSIs is msi_type RF_Unit, the system rejects the equip path command. A path for an HDSL link must have the same number of timeslots, identical link protocol types, and HDSL modems that are in a master/slave configuration. The single exception to this rule is when the system cannot check master/slave settings because the HDSL link consists of two external modems.
Command prompts Optional
Range
Default
Enter terminating SITE ID:
Prompt
N
0 - 140
None
Enter the Unique PATH identifier:
N
See Comments
None
Comments
The availability of a PATH identifier depends on whether the terminating site uses dynamic allocation: - no dynamic allocation: 0 to 9. - dynamic allocation: 6 to 9. Continued
2-48
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Prompt
PATH
Optional
Range
Default
Comments
Enter the BSC MMS identifier:
N
{22169} 0 - 95 (MSI), 0 or 1 (MMS)
None
Type two values, separated by a space; the first value is the MSI ID; the second value is the MMS ID.
Enter SITE identifier:
N
0 - 140, or ts_switch (See comments)
None
If the Aggregate Abis feature is enabled the system accepts ts_switch as the site ID. If ts_switch is used, the system does not prompt for upstream MSI, upstream MMS, downstream MSI and downstream MMS identifiers.
Enter the upstream MMS identifier:
N
{22169} BSC: 0 - 95, BTS: 0 (Horizon II Macro, Horizon II Mini, 0 - 9 (In-Cell, Horizon Macro), 0 - 3 (M-Cell6), 0 - 1 (M-Cell2).
None
The upstream MMS identifier cannot correspond to an RF_Unit MSI. MMS ID 2 is 0 - 1.
The following sequence of prompts repeats until the specified site identifier matches the terminating site (maximum of nine sequences):
68P02901W23-S
2-49 Nov 2009
PATH
Chapter 2: Equipping the CM database
Prompt
Optional
Range
Default
Enter the downstream MMS identifier:
N
{22169} BSC: 0 - 95, BTS: 0 - 9 (InCell), 0 - 3 (M-Cell6), 0 - 1 (M-Cell2).
None
Enter the SITE identifier:
N
0 - 140, or ts_switch (See comments)
None
If the Aggregate Abis feature is enabled the system accepts ts_switch as the site ID. If ts_switch is used, the system does not prompt for upstream MSI, upstream MMS, downstream MSI, and downstream MMS identifiers.
Enter the upstream MMS identifier:
N
{22169} BSC: 0 - 95, BTS: 0 - 9 (InCell), 0 - 3 (M-Cell6), 0 - 1 (M-Cell2).
None
The range for the MMS ID 2 is 0 - 1.
Comments
If an MMS has another timeslot that conflicts when equipping a PATH, the system generates the following warning: COMMAND ACCEPTED: WARNING: Conflict in MMS usage, display timeslot usage to verify. Conflicting usage is when at least one timeslot provides connectivity to a BTS and another type of device (such as, an RXCDR).
NOTE The upstream MMS ID cannot correspond to an RF_Unit MSI.
2-50
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
PCU
PCU Equip conditions The Packet Control Unit (PCU) can be equipped with the system in SYSGEN ON mode. With the enhanced PCU (ePCU) in GSR9, 3xPCU configuration is not required to achieve the target GPRS capacity. That is, supporting 3240 PDTCH (810 active, 2430 standby). 3xPCU configuration is disabled in GSR9. When a PCU is equipped, a corresponding CAB device and CAGE device are automatically equipped. A PCU can be equipped only if parameter land_layer1_mode is set to E1.
Command prompts Prompt Enter the PCU Identifier: Enter the PCU base GDS IP Address: Enter the PCU GDS Subnet Mask:
Default 0 127.0.0.1 255.255.0.0
Enter the WEBMMI IP Address:
127.0.0.1
Enter the WEBMMI Subnet Mask:
255.255.0.0
Enter the WEBMMI Router IP Address: ENTER the NSEI value: Enter the PRP Fanout Mode:
127.0.0.1 10 1
PSI Equip conditions The PSI (Packet Subrate Interface) is designed to be a generic interface to an external packet network through the Ethernet. The primary function of the PSI card is to terminate GPRS TRAU and transfer the TRAU payload to the PCU over Ethernet. The PSI device is equipped inside or outside SYSGEN mode. The PSI device is equipped only at a BSS or BSC sites. The BSC supports a maximum of 4 PSIs per cage.
68P02901W23-S
2-51 Nov 2009
PSP
Chapter 2: Equipping the CM database
Command prompts Prompt
Optional
Range
Default
Enter the PSI Identifier:
N
0 - 11
None
Enter the cage number Identifier:
N
0 - 13
None
Enter the slot number:
N
6 - 13
None
Enter the number of TDM timeslot blocks:
Y
2 - 10
2
Enter the maximum number of GSLs on this PSI:
Y
0 - 30
0
Enter the base IP address for the PSI:
N
1.0.0.1 223.255.255 .237
None
Enter the subnet mask:
Y
128.0.0.0 255.255. 255.255.255.0 255.0
Enter the router IP address:
Y
0.0.0.0 255.255.255 .254
0.0.0.0
Comments
Valid slot number is 6, 7, 12 and 13.
The base IP address is used for the MCU. 17 contiguous addresses are available after the base address for the DSPs. The IP address is entered in dotted quad notation.
The IP address of the router. The value of 0.0.0.0 means that no router is in use.
PSP Equip conditions The PCU System Processors (PSPs) are equipped only when the GPRS feature is unrestricted. The PSPs can only be fitted at a PCU. Two PSPs can be installed in each PCU. The PSPs must be physically installed before code download can start to the PCU. The site must not be locked when this device is equipped outside the SYSGEN ON mode. The PSPs are auto-equipped. The system uses a default value for the PSP slot; therefore, the operator is not prompted.
2-52
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
RSL
RSL Equip conditions The location for the Radio System Link (RSL) must be the BSC (site 0). Only one RSL can be equipped to an NIU in slot 1 of an M-Cell terminating site. Only four RSL devices can be enabled per E1 span. Previously, the number of RSL devices supported on an NIU and an E1 span were the same.
Command prompts Optional
Range
Default
Enter the 1st device ID for the RSL:
Prompt
N
0 - 140
None
Enter the 2nd device ID for the RSL:
N
0 - 7 See Comments
None
Enter the Unique PATH ID:
N
0 - 9
None
Enter LAPD T200 Timer value:
Y
1400 - 5000
2500
Enter LAPD N200 value:
Y
1 - 5
3
Enter LAPD K value:
Y
1 - 10
7
Comments
The range depends on the site type: InCell: 0 - 7. M-Cell 2/6 BTS: 0 - 5.
Values must be in multiples of 50.
NOTE The equip RSL command automatically equips an additional 16 K RSL when a 16 K RSL is equipped to an auto-equipped PATH that is part of a closed loop DYNET. The equip command does not allow an RSL to be equipped to a PATH that is not automatically created at a site that supports dynamic allocation.
RXCDR Equip conditions The Remote Transcoder (RXCDR) must be the first device equipped by the operator in the SYSGEN ON mode at an RXCDR site. If an RXCDR device is equipped at a BSS site, it is actually an Associate RXCDR (AXCDR) device (see AXCDR on page 2-12).
68P02901W23-S
2-53 Nov 2009
SITE
Chapter 2: Equipping the CM database
Command prompts Prompt
Optional
Range
Default
N
1 - 254
None
Enter the RXCDR ID:
Comments
SITE Equip conditions A BTS Site (SITE) can be equipped with the system in SYSGEN ON mode or the SYSGEN OFF mode. The system rejects the equip site command if the new site exceeds the site capacity of the LCF. The LCF site capacity equals gproc_slots minus 1 (for the test channel).
Command prompts Prompt
2-54
Optional
Range
Default
Comments
Enter the device identifier for the site:
N
0 - 140
None
0 is the only valid value for an RXCDR site type.
Enter the type of BSP or LCF:
N
BSP or LCF
None
Enter the function identifier for the LCF:
N
0 or 1 (BSP). 0 - 24 (LCF).
None
Enter the RSL type:
N
16 or 64
None
The system displays this prompt only if the site is remote and the 16 K RSL option is enabled.
Does the site use dynamic allocation of terrestrial backing resources?:
N
Y or N
None
This prompt only appears if: •
The Dynamic Allocation feature is unrestricted.
•
The site being equipped is a BTS.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
XBL
XBL Equip conditions The RXCDR to BSC Fault Management Link (XBL) cannot be equipped on an HDSL link. The maximum number of XBLs that can be equipped at a BSC or an RXCDR site is 20.
Command prompts Prompt
Optional
Range
Default
Comments
Enter the ABSS device ID for the XBL:
N
1 - 254
None
This prompt is displayed only at an RXCDR site. This value is valid for XBLs equipped at an RXCDR. This value specifies the ABSS device with which this XBL will be communicating and represents the first device ID for the XBL.
Enter the AXCDR device ID for the XBL:
N
1 - 254
None
This prompt is only displayed at a BSC site. This value is valid for XBLs equipped at a BSS. This value specifies the RXCDR device with which the XBL will be communicating and represents the first device ID for the XBL.
Enter the second device ID for the XBL:
N
0 - 9
None
The is the value for the XBL device.
Enter the data rate for the XBL (16/64 kbit/s):
Y
16 or 64
Enter the first MMS description for this device:
N
{22169} BSC: 0 - 95. RXCDR: 0 - 123.
None
Enter the second MMS description for this device:
N
0 or 1
None
Prompted only if the 16 kbit/s option is unrestricted. This prompt appears only if the XBL data rate is set to 16.
Continued
68P02901W23-S
2-55 Nov 2009
XBL
Chapter 2: Equipping the CM database
Prompt
Optional
Range
Default
Enter the timeslot on MMS where this device appears:
N
E1: 1 - 31.
None
Enter the group of the timeslot where this device appears:
Y
0 - 3
Enter LAPD T200 time value for the device:
Y
1400 5000
2500
Enter LAPD N200 value:
Y
1 - 5
3
Enter LAPD K value:
Y
1 - 127
7
Comments
Prompted only if the 16 kbit/s option is unrestricted and the XBL data rate is set to 16 kbit/s. Values must be in multiples of 50.
If an MMS has another timeslot that conflicts when equipping an XBL, the system generates the following warning: COMMAND ACCEPTED: WARNING: Conflict in MMS usage, display timeslot usage to verify. Conflicting usage exists when at least one timeslot provides connectivity to a BTS and another is connected to a different type of device. That is, RXCDR, OML, and so on.
2-56
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Information for equipping functions
Information for equipping functions ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
This section provides conditional information for the rules on equipping the following functions, and lists the equip command prompts that occur with each function: LCF on page 2-57
OMF on page 2-58
RTF on page 2-58
LCF Equip conditions The Link Control Function (LCF) can only be equipped at BSC site types where the BSC type is not zero. At least one LCF must have a max_mtls value greater than zero. The sum of all GSLs (GPRS) specified by the equipped LCFs must be greater than or equal to the total number of equipped GSLs.
Command prompts {28337} Prompt
Optional
Range
Default
Enter the function identifier for the LCF:
N
0 - 24
None
Enter the number of DSO channels the LCF can manage as MTLs:
N
0, 1, 2, 31*
None
Enter the number of LMTLs the LCF can manage:
Y**
0 - 2
None
Enter the number of CBLs the LCF can manage:
Y**
0 - 1
None
Enter the number of GSLs the LCF can manage:
Y**
0 - 12
None
Comments
Prompted only when the GPRS feature is unrestricted.
NOTE
68P02901W23-S
•
*: For processing 64 k MTL, the valid value is 0, 1 or 2 for all types of GPROC. For HSP MTL, the valid value is 31. In GSR9, values between 3 and 30 are invalid.
•
** These prompts are displayed when MTL DS0 channels handled by the LCF is set to 0, 1 or 2.
•
An LCF cannot simultaneously manage both MTLs and LMTLs. 2-57 Nov 2009
OMF
Chapter 2: Equipping the CM database
OMF Equip conditions The Operation and Maintenance Function (OMF) can only be equipped at BSC or BSS site types where the BSC type is set to 2. This function can be equipped with the system in SYSGEN ON mode or outside the SYSGEN ON mode. The site must not be locked when this function is equipped outside SYSGEN ON mode.
Command prompts No parameter prompts are displayed when equipping the Operations and Maintenance Facility (OMF).
RTF Equip conditions The Radio Transceiver Function (RTF) can be equipped with the system in either SYSGEN ON or SYSGEN OFF mode. When equipping the RTF, the system enforces the following dependencies: •
An RTF cannot be equipped in SYSGEN OFF mode if: All the RTF timeslots are non-hopping (255); and other non-hopping RTFs or enabled frequency hopping systems in the cell are already using the maximum number of frequencies. The RTF hops through one or more timeslots which cause frequency collisions. A frequency collision occurs when two enabled FHIs hop through the same ARFCN and one RTF uses one FHI in the same timeslot and another RTF uses the other FHI.
•
If the site is not in a DYNET, an RTF cannot be equipped to a site using dynamic allocation.
•
Due to the restrictions imposed by the BSS, Base Band Hopping (BBH) is not supported on 64 kbit/s RTF, of which carrier A is EGPRS capable, when it is equipped on a double density CTU2.
When an attempt is made to equip a new RTF in and out of Sysgen mode, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request. It also issues a warning to indicate that there is not enough GDS or PMC resource available. If one or more PCS1900 frequency blocks are available to the BSS and an ARFCN is entered which is one of the block edges, the max_tx_bts for the cell assigned to this RTF cannot be less than or equal to 3 (which corresponds to greater than 36 dBm).
2-58
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
RTF
The channel numbers at the block edges are: 512
610
687
735
585
612
710
737
587
685
712
810
These channel numbers do not apply if: •
The frequency at the assigned cell does not include PCS1900.
•
The available frequency blocks for the BSS are contiguous (such as A and D) and the ARFCN is on the adjacent border of the selected blocks.
•
The Concentric Cells feature is enabled, the power based use algorithm is used and the block edge frequency is defined to be an inner zone carrier with a maximum transmit power level (tx_pwr_red) less than 36 dBm.
When the Dual Band Cells option is enabled, the frequency type is managed on a zone basis. Primary band carriers are configured in the outer zone and secondary band carriers are configured in the inner zone. DRIs/RTFs within a dual band cell with different frequency types must have different DRI/RTF group identifiers. The equip RTF command allows two group identifiers for a cell only if the cell is dual band. The equip cabinet command allows the secondary and primary band frequency types in each zone to which the DRIs are equipped. The frequency type of the secondary band defines the valid range for the ARFCN of an RTF configured for the inner zone. equip RTF for the secondary band in a dual band cell does not prompt for TRX power reduction. For a dual band cell, an attempt to equip RTF for a BCCH RTF in the inner zone is rejected. When equipping an RTF to a dual band cell, the specified FHIs can contain only the frequencies in the band of the RTF. The pkt_radio_type parameter specifies the terrestrial resource capability of an RTF. The mutually exclusive options are 16 kbit/s, 32 kbit/s, 64 kbit/s, and none. An EGPRS-capable RTF can carry EGPRS PDTCHs and can allocate 64 kbit/s terrestrial channels to support the EGPRS coding schemes on the air timeslots. For a complete description of this parameter, refer to pkt_radio_type on page 8-76.
Warning messages The following warning message displays when an attempt is made to equip a new RTF and the requested PDTCHs exceed the GDS or PMC capacity on the PCU: COMMAND ACCEPTED: WARNING: Insufficient GDS resources available for all PDTCHs on the PCU. The following warning message displays if a frequency is specified that is already in use at the site: COMMAND ACCEPTED: WARNING: Specified ARFCN already exists at specified site. The following warning message displays if a frequency is specified that is already used at a cell: COMMAND ACCEPTED: WARNING: Specified ARFCN already exists in this cell.
68P02901W23-S
2-59 Nov 2009
RTF
Chapter 2: Equipping the CM database
Reject messages The following message displays if the max_tx_bts for the cell must be reduced before an RTF can use the specified ARFCN: COMMAND REJECTED: Block edge ARFCN not allowed for max_tx_bts level of the cell The following message displays if the ARFCN specified for the RTF is not valid for the cell: COMMAND REJECTED: An out of range frequency was entered for this frequency. The following message displays if the trx_pwr_red for the carrier must be reduced before the RTF can use a specified ARFCN: COMMAND REJECTED: Power level is not allowed for a Carrier with a PCS block edge ARFCN.
Error messages The following error messages occur when attempting to equip an RTF for EGPRS: •
For a site which has no Horizonmacro, Horizonmacro2 or Mcell family of cabinets equipped: COMMAND REJECTED: Horizonmacro, Horizonmacro2 or Mcell family of cabinets required for EGPRS.
•
With 32 kbit/s packet radio capabilities, when the Coding Scheme 3 and 4 feature is restricted: COMMAND REJECTED: Received a request to modify a restricted optional feature.
•
With 64 kbit/s packet radio capabilities, when the EGPRS feature is restricted: COMMAND REJECTED: Received a request to modify a restricted optional feature.
•
Which is baseband hopping through other non-EGPRS RTFs: COMMAND REJECTED: EGPRS and non-EGPRS carriers cannot have the same FHI
•
That is subequipped: COMMAND REJECTED: 32 kbit/s / 64 kbit/s TRAU rate is not allowed for sub-equipped RTFs
•
With an associated RSL: COMMAND REJECTED: Multiplexed RSL is not allowed with 64 K RTFs
•
At a site that supports dynamic allocation: COMMAND REJECTED: 32 kbit/s / 64 kbit/s TRAU rate is not allowed at sites using dynamic allocation.
•
If a non-zero value of extended range timeslots is entered for an RTF with 64 kbit/s packet radio capabilities: COMMAND REJECTED: Extended range timeslots are not allowed for EGPRS carriers.
2-60
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
•
RTF
With a valid FHI, outside Sysgen mode: If the RTF is at a site whose master cabinet is not a Horizon II macro. If the hopping system is set to baseband hopping. COMMAND REJECTED: Master cabinet must be Horizonmacro2 for EGPRS RTFs to hop in baseband hoppping.
•
To be in the inner zone of a concentric cell: COMMAND REJECTED: EGPRS/GPRS carriers must be in the outer zone of a concentric cell.
Command prompts Prompt
Optional
Range
Enter capacity of carrier:
N
FULL or SUB
Enter type of carrier:
N
bcch or non_bcch
None
Enter the 1st and 2nd RTF ID:
N
Valid first RTF ID: 0 - 5. Valid second RTF ID: 0 - 11, 0 - 1 for M-Cell.
None
Enter the primary Unique PATH ID:
N
0 - 9
None
If the BTS type is 16 k RSL, the system displays the next prompt. Otherwise, proceed with the Enter the optional secondary Unique Path ID prompt. This prompt will not display if the RTF is equipped to a BTS using dynamic allocation.
Enter the optional 2nd identifier for the associated RSL:
N
Micro: 0 - 1. MCell: 0 - 5. InCell: 0 - 7.
None
If the RTF is equipped to a BTS using dynamic allocation, this prompt does not display.
Default
Comments This prompt does not display if: - the RTF is equipped to a BTS using dynamic allocation. - the subequipped RTF feature is not available.
Continued
68P02901W23-S
2-61 Nov 2009
RTF
Chapter 2: Equipping the CM database
Prompt
Optional
Range
Default
Comments
Enter the optional secondary Unique Path ID:
Y
0 - 9
None
This prompt is provided for only RTFs at remote BTS sites. This prompt does not display if the RTF is equipped to a BTS using dynamic allocation.
Enter the GSM cell to which this carrier is assigned:
N
GSM cell ID or cell_name
None
The cell number can be in either seven parameter format or four parameter format.
Enter carrier absolute radio freq. channel:
N
See Comments.
None
The first channel from which to hop, as set in the MA (Mobile Allocation). Used to set the MA index offset, which defines the channel from which the MS is to hop. PGSM BCCH (not extended) 1-124 NON_BCCH (not extended) 1-124 EGSM BCCH (extended) 0, 1-124, or 975-1023 NON_BCCH (extended) 0, 1-124 or 975-1023 DCS1800 BCCH (not extended) 512-885 NON_BCCH (not extended) 512-885 PCS1900 BCCH (not extended) 512-810 NON-BCCH (not extended) 512-810
Enter the 8 carrier frequency hopping indicators:
N
0 - 3 and 255
255
The 8 frequency hopping indicators are entered on a single line with one space separating each value. The input for this value must include all eight values or no values. A value of 255 means no hopping. A value of 255 is required for all M-Cellcity sites. Continued
2-62
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Prompt
RTF
Optional
Range
Default
Comments
Enter the 8 carrier training sequence codes:
N
0 - 7
None
The eight carrier training sequence codes are entered on a single line with one space separating each value.
Enter KSW pair that manages this carrier:
N
0 - 3
None
This prompt does not appear when equipping the RTF to an M-Cell site.
Enter cell zone:
N
0 or 1
0
0 = Outer zone 1 = Inner zone This prompt appears only for NON-BCCH carriers and only if the Concentric Cells feature is unrestricted.
Enter TRX transmit power reduction:
Y
same value as max_tx_bts
Enter the number of extended range timeslots allowed:
Y
0 - 4
Only prompted for outer zone carriers. Only prompted when the Extended Range Cell feature is unrestricted.
Enter SDCCH load
Y
0 - 2
The system displays this prompt for outer zone carriers (cell_zone = 0) only.
Enter SDCCH placement priority:
Y
0 - 250
The system displays this prompt if: for outer zone carriers (cell_zone = 0) only, and sdcch_load is not set to 0 (≠ 0).
Enter channel allocation priority:
Y
0 - 250
Enter the packet radio capability:
N
0 - 3, or None, 16 K, 32 K, 64 K
0 (None)
Enter the rtf_ds0_count:
Y
3 - 8
3
Only prompted when Concentric Cells feature is enabled. Only prompted for inner zone carriers.
This prompt only occurs if the GPRS feature is unrestricted and if it is an outer zone carrier. For a complete description of this parameter, refer to Chapter 8 Device/Function parameters. This prompt only occurs if the VersaTRAU (VT) feature is unrestricted. Continued
68P02901W23-S
2-63 Nov 2009
RTF
Chapter 2: Equipping the CM database
Prompt
Optional
Enter the value for Half Rate enabled:
Is 8 kbit/s TRAU allowed (yes/no):
Y
Range
Default
Comments
0 or 1
0
This prompt only occurs at Half Rate capable BTSs such as M-Cell2, M-Cell6, Horizonmacro and Horizon II macro, if AMR and/or GSM HR are/is unrestricted.
Y or N
Y
This prompt only occurs at Half Rate capable BTSs such as M-Cell2, M-Cell6, Horizonmacro, and Horizon II macro when half_rate_enabled is set to 1.
NOTE When the equip RTF is completed, check the state of the RTF. If the RTF is not in the BUSY_ENABLED state, check the DRI that supports the new RTF. If the DRI is not in service (DU INHIBITED) use the MMI to place the DRI in service. The DRI must be BUSY_UNLOCKED.
2-64
68P02901W23-S Nov 2009
Chapter
3 Device/function related commands ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Device/function commands are commands that can be entered at the MMI to create, modify, display, delete devices and functions within the BSS. This chapter contains relevant information on device related and function related commands, together with individual descriptions for the following types of Man Machine Interface (MMI) commands: •
Maintenance (Fault Management)
•
System Change Control (Configuration Management)
•
Call Processing
•
Miscellaneous
NOTE Statistical commands are described in Chapter 5 Statistics commands.
68P02901W23-S Nov 2009
3-1
Command reference presentation
Chapter 3: Device/function related commands
Command reference presentation ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The individual MMI command descriptions are presented in alphabetical order in the following command reference layout: •
Command title - the actual command reference which appears at the head of the page, and in the contents and the index of this manual.
•
Description - provides a description of the MMI command function and includes: Security level - the access security level for the command. Supported by OMC-R GUI - whether the command is supported at the OMC-R GUI. Command type - whether type A (no operator actions) or type B. Prerequisites - conditions that must be met or exist for the command to be accepted. Operator actions - actions required by the operator for type B commands. If no actions are required, this field is not shown.
•
Format - includes the input command: Syntax - the structure of the command and input parameter string. Input parameters - descriptions of each command input parameter.
•
Examples - provides various examples of command input and the expected response.
•
References - includes where appropriate: Related information - any relevant information, such as command prompts, specific responses. Related commands - any commands that are related.
3-2
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Device-related commands
Device-related commands ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
This section provides tables listing the devices and the literals by which they are identified in device-related commands, and the specific commands as relevant to the devices.
Device literals Table 3-1 lists the device literals and their descriptions.
Table 3-1
Device literals and descriptions
Literal
Description
ABSS
Associated Base Station Substation
AXCDR
Associated RXCDR
BSS
Base Station Substation
BSP
Base Site Processor (at BSC)
BTP
Base Transceiver Processor (at BTS)
CAB
Cabinet
CAGE
Cage
CBL
Cell Broadcast Link
CBUS
Clock Bus
CELL
Cell
CIC
Circuit Identity Code
COMB
Combiner
CSFP
Code Storage Facility Processor (at BSC or BTS)
DHP
Digital radio Host Processor
DPROC
Data Processor board (GPRS)
DRI
Digital Radio Interface
DYNET
Dynamic Network of BTSs
EAS
External Alarm System
{26740/28351} ETH
Ethernet port
GBL
Gb Link (GPRS)
GCLK
Generic Clock
GDS
GPRS Data Stream (GPRS)
GPROC
Generic Processor Continued
68P02901W23-S
3-3 Nov 2009
Devices and commands
Table 3-1
Chapter 3: Device/function related commands
Device literals and descriptions (Continued)
Literal
Description
GPROC2
Generic Processor 2
GPROC3
Generic Processor 3
GSL
GPRS Signaling Link (GPRS)
KSW
Kilo-port Switch
LAN
Local Area Network
LMTL
Location Message Transfer Link
MMS
1.544/2.048 Mbit/s link on an MSI board
MPRT
1.544/2.048 Mbit/s Port
MSI
1.544/2.048 Mbit/s Interface board
MTL
Message Transfer Link
OML
Operations and Maintenance Link
OPL
OPtimization Link
PATH
Path
PBUS
Processor (MCAP) Bus
PCHN
Physical Channel
PCU
PCU Device (GPRS)
{26740} PSI
Packet Subrate Interface
PSP
PCU System Processor (GPRS)
RSL
Radio System Link (Abis)
SBUS
Serial Bus
SITE
BSC or BTS
TBUS
TDM Bus
TDM
Time Division Multiplex
XBL
RXCDR to BSC fault management Link
Devices and commands Table 3-2 lists the specific commands as relevant to the devices.
3-4
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 3-2
Devices and commands
Device and command relationship
Device
Commands Affected
Notes
BSP
equip, unequip, unlock_device, state, disp_equipment, device_audit
disp_equipment includes Hardware Version Number (HVN).
lock_device, ins_device, reset_device
Cause a hard reset of the device.
equip, unequip, unlock_device, state, disp_equipment, device_audit
disp_equipment includes HVN.
lock_device, ins_device, reset_device
Cause a hard reset of the device.
BTP
CAB
equip, state, disp_equipment
CAB(PCU)
state
Valid for GPRS only.
CAGE
equip, state, disp_equipment
Valid for BSC and InCell BTS.
CAGE (PCU)
equip, state, disp_equipment, device_audit, cage_audit
Valid for GPRS only.
CBL
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device
Valid for BSC only.
CBUS
state
Valid for BSC and InCell BTS.
CELL
state
CIC
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device, shutdown_device
COMB
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device, swap_devices
CSFP
state, disp_equipment
Valid for BSC only.
equip, unequip, lock_device, unlock_device, ins_device, reset_device
Valid for BSC and InCell BTS.
DHP
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device, device_audit
Valid for BSC and InCell BTS disp_equipment includes HVN.
DPROC
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device, device_audit
Valid for GPRS only.
DRI
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device, device_audit, shutdown_device
disp_equipment includes HVN.
Continued
68P02901W23-S
3-5 Nov 2009
Devices and commands
Table 3-2
Chapter 3: Device/function related commands
Device and command relationship (Continued)
Device
Commands Affected
EAS
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device
{26740/28351} ETH
lock_device, unlock_device, state, disp_equipment, ins_device
GBL
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device
Valid for GPRS only.
GCLK
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device, swap_devices, device_audit
Valid for BSC and InCell BTS. disp_equipment includes HVN.
GDS
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device
Valid for GPRS only.
GPROC
equip, unequip, unlock_device, state, disp_equipment, device_audit
Valid for BSC and InCell BTS. disp_equipment includes HVN.
lock_device, ins_device, reset_device
Valid for BSC and InCell BTS. Cause a hard reset of the device.
equip, unequip, unlock_device, state, disp_equipment, device_audit
Valid for BSC and InCell BTS. disp_equipment includes HVN.
lock_device, ins_device, reset_device
Valid for BSC and InCell BTS. Cause a hard reset of the device.
equip, unequip, unlock_device, state, disp_equipment, device_audit
Valid for BSC and InCell BTS. disp_equipment includes HVN.
lock_device, ins_device, reset_device
Valid for BSC and InCell BTS. Cause a hard reset of the device.
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device
GPRS only.
GPROC2
GPROC3
GSL
Notes
Continued
3-6
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 3-2
Devices and commands
Device and command relationship (Continued)
Device
Commands Affected
Notes
KSW
equip, unequip, unlock_device, state, disp_equipment, device_audit, ins_device
Valid for BSC and InCell BTS. disp_equipment includes HVN.
lock_device, reset_device
Valid for BSC and InCell BTS. Cause a hard reset of the device.
LAN
state, swap_devices
Valid for BSC and InCell BTS.
MMS
lock_device, unlock_device, state, disp_equipment, ins_device, reset_device
MPRT
shutdown_device
Valid for BSC only.
MSI
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, device_audit
disp_equipment includes HVN.
reset_device
Causes a hard reset of the device.
MTL
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device, shutdown_device
Valid for BSC only.
OML
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device
Valid for BSC only.
OPL
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device
Valid for BSC only.
PATH
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device
Valid for BSC only.
PBUS
state
Valid for BSC and InCell BTS.
PCHN
state, lock_device, unlock_device, ins_device, reset_device
PCU
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device site_audit, base_ip_address
{26740/28351} PPROC
lock_device, unlock_device, state, disp_equipment, reset_device, base_ip_address
{26740} PSI
equip, unequip, lock_device, unlock_device, state, disp_equipment, reset_device, ins_device, device_audit, chg_audit_sched, modify_value, query_audits, tdm_ts_blocks
Valid for GPRS only.
Continued
68P02901W23-S
3-7 Nov 2009
Devices and commands
Table 3-2
3-8
Chapter 3: Device/function related commands
Device and command relationship (Continued)
Device
Commands Affected
Notes
PSP
equip, state, disp_equipment, device_audit, unequip
Valid for GPRS only.
RSL
lock_device, unlock_device, state, disp_equipment, ins_device, reset_device
RSL
equip, unequip
Valid for BSC only.
SBUS
state
Valid for BSC and InCell BTS.
SITE
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device
Valid for BSC only.
TBUS
state
Valid for BSC and InCell BTS.
TDM
state, swap_devices, device_audit
Valid for BSC and InCell BTS.
XBL
equip, unequip, lock_device, unlock_device, state, disp_equipment, ins_device, reset_device
Valid for BSC only.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Device identifiers
Device identifiers ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
A device is specified in the system by three identifiers. However, not all devices have three device IDs. For devices that have only one or two device identifiers, zeros must be entered for the remaining device identifier parameters as place holders.
Device ID requirements Table 3-3 lists and defines the device ID requirements.
Table 3-3
Device ID requirements
Device Names/IDs
Range
ABSS
Definition Associated Base Station Processor
device ID 1
0 - 254
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
AXCDR
Corresponds to the BSS network entity that this device represents.
Associated XCDR
device ID 1
0 - 254
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
BCUP
Corresponds to the RXCDR network entity that this device represents.
BSS Controller Unit Power Supply per cage.
device ID 1
0 - 15
Identifies the cage number.
device ID 2
0 - 2
Identifies which power supply (of the three possible per cage).
device ID 3
0
BSP
Serves as place holder. Base Site Processor, BSC
device ID 1
0 or 1
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
BSS
Identifies which BSP board is active and which is redundant (standby). (None at a BTS.)
Base Station System
device ID 1
0 - 254
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
BTP
Identifies BSS.
Base Transceiver Processor, BTS Continued
68P02901W23-S
3-9 Nov 2009
Device ID requirements
Table 3-3
Chapter 3: Device/function related commands
Device ID requirements (Continued)
Device Names/IDs
Range
device ID 1
1
Identifies which BTP board is active and which is redundant (standby). (None at a BSC or RXCDR.)
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
CAB
Definition
CABinet
device ID 1
0 - 20
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
CAGE
Identifies cabinet number.
CAGE
device ID 1
0 - 15
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
CBL
Identifies the value at which the LANX card, dial is set.
Cell Broadcast Link
device ID 1
0
Optional entry. (None at a BTS or RXCDR.)
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
CBUS
Clock BUS
device ID 1
0 - 15
Identifies the cage where a specific GCLK is located.
device ID 2
0 or 1
Identifies the GCLK.
device ID 3
0
COMB
Serves as place holder. COMBiner
device ID 1
0 - 13
Identifies specific combiner cavities (13 active, 13 standby). (None at an RXCDR.)
device ID 2
0 or 1
Identifies each individual processor in a combiner unit (of the two present within a redundant pair).
device ID 3
0
CSFP
Serves as place holder. Code Storage Facility Processor
device ID 1
10
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
DHP device ID 1
CSFP identifier (only at a BSC) - not M-Cell, automatically equipped/unequipped.
Digital radio Host Processor, BTS 0 - 5
Identifies a digital module shelf (cage number) in a specific cabinet. (None at an RXCDR.) Continued
3-10
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 3-3
Device ID requirements
Device ID requirements (Continued)
Device Names/IDs
Range
device ID 2
0 - 7
device ID 3
0
DPROC
Definition Identifies which DHP board is active and which is redundant (standby). Serves as place holder. Digital Processor (GPRS)
device ID 1
1 - 6 or 11 - 16
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
DRI
Identifies a specific DPROC Board.
Digital Radio Interface
device ID 1
0 - 5
Identifies a user-defined DRI group within a site. The DRIs which belong to this group must be allocated to the same cell and must be connected to the same antenna. (None at an RXCDR.)
device ID 2
0 - 11
Identifies a specific DRI board.
device ID 3
0
EAS
Serves as place holder. External Alarm System
device ID 1
0 - 7 0 - 15
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
GBL
Identifies a specific PIX card at a site - not M-Cell. M-Cell
Gb Link (GPRS)
device ID 1
0 - 35
device ID 2
0
Serves as place holder
device ID 3
0
Serves as place holder
GCLK
Identifies a specific GBL link
General CLocK 0 or 1
0
Identifies which GCLK board is active and which is redundant (standby). 0=A side GCLK (slot A controls) - slot 5 1=B side GCLK (slot B controls) - slot 3 M-cell, automatically equipped/unequipped.
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
device ID 1
GDS
GPRS Data Stream (GPRS)
device ID 1
0 - 37
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
GPROC
Identifies a specific GPRS data stream.
Generic PROCessor, device used for functions. Continued
68P02901W23-S
3-11 Nov 2009
Device ID requirements
Table 3-3
Chapter 3: Device/function related commands
Device ID requirements (Continued)
Device Names/IDs
Range
device ID 1
0 - 111
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
GSL
Definition Identifies a specific GPROC board.
GPRS Signaling Link (GPRS)
device ID 1
0 - 59
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
KSW
Identifies a specific GPRS signaling link.
Kiloport SWitch
device ID 1
0 - 3
device ID 2
0 or 1
device ID 3
0
LAN
Identifies a section (timeslot) of TDM highway. M-Cell not applicable. Identifies which KSW board (highway, A side, or B side) is active and which is redundant (standby). (0 is slot 27 and 1 is slot 1.) Serves as place holder. Local Area Network
device ID 1
0 or 1
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
MMS
Identifies which LAN board (A side or B side) is active and which is redundant (standby).
The E1 Mbit/s line on a Multiple Serial Interface board.
device ID 1
{22169} 0 - 95 9 3 1 0
device ID 2
0 or 1
device ID 3
0
MSI
Matches the first ID of the host MSI with 0 - 95 for BSC and 0 - 123 for RXCDR. BTS only: not M-Cell BTS only: M-Cell6 BTS only: M-Cell2 BTS only: M-Cellmicro Identifies a specific MMS. Serves as place holder. Multiple Serial Interface board
device ID 1 0 - 95 0 - 71 9 3 1 0
Identifies a specific MSI board: BSC RXCDR BTS only: not M-Cell BTS only: M-Cell6 BTS only: M-Cell2 BTS only: M-Cellmicro
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
MTL
Message Transfer Link Continued
3-12
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 3-3
Device ID requirements
Device ID requirements (Continued)
Device Names/IDs
Range
device ID 1
0 - 15
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
OML
Definition Identifies a specific MTP link (per ITU-TSS spec).
Operations and Maintenance Link
device ID 1
0 - 3
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
OPL
Identifies a specific connection (link) between the BSC and the OMC-R (BSC or RXCDR).
OPtimization Link
device ID 1
0 - 3
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
Identifies a specific connection (link) between the BSC and the IOS platform.
PATH device ID 1
0 - 140
device ID 2
0 - 9
device ID 3
0
PBUS
Identifies the terminating site (BSC only). Identifies a unique PATH ID. Serves as place holder. Processor (MCAP) BUS
device ID 1
0 - 15
Identifies the cage at that location.
device ID 2
0 or 1
Identifies which PBUS (A side or B side) is active and which is redundant (standby).
device ID 3
0
RSL
Serves as place holder. Radio System Link
device ID 1
0 - 140
device ID 2
0 - 7 5 1
device ID 3
0
RTF
Identifies the site to which the RSL is connecting (BSC only). Identifies a specific link set (not M-Cell): M-Cell2 and M-Cell6 M-Cellmicro Serves as place holder. Receive Transmit Function
device ID 1
0 - 5
Identifies the cell group.
device ID 2
0 - 11
Identifies a unique function within the cell group.
device ID 3
0
RXCDR
Serves as place holder. Remote transcoder
device ID 1
0 - 254
device ID 2
0
Serves as place holder. Continued
68P02901W23-S
3-13 Nov 2009
Device ID requirements
Table 3-3
Chapter 3: Device/function related commands
Device ID requirements (Continued)
Device Names/IDs
Range
device ID 3
0
SITE
Serves as place holder. BTS SITE
device ID 1
0 - 140
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
SBUS
Identifies the site for which commands are being executed.
Serial BUS
device ID 1
0 - 15
Identifies the cage at that location.
device ID 2
0 or 1
Identifies which SBUS (A side or B side) is active and which is redundant (standby).
device ID 3
0
TBUS
Serves as place holder. TDM BUS
device ID 1
0 - 15
Identifies the cage at that location.
device ID 2
0 or 1
Identifies which TBUS (A side or B side) is active and which is redundant (standby).
TDM
Time Division Multiplex Highway
device ID 1
0 or 1
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
XBL
3-14
Definition
Identifies which side (A side or B side) of the TDM highway is active and which is redundant (standby).
RXCDR to BSC Fault Management Link.
device ID 1
0 - 9
device ID 2
0
Serves as place holder.
device ID 3
0
Serves as place holder.
Identifies a specific connection (link) between the RXCDR and the BSC.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Function related commands
Function related commands ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
The function-related commands that affect the functions are listed in Table 3-4. •
The first column gives the function literal.
•
The second column gives the function name.
•
The remaining columns show the commands that are supported for each function.
Table 3-4 Literal
Function related commands Device name / description
Commands unequip
equip
state
disp_equipment
LCF
Link Control Function, BSC
X
X
X
X
OMF
Operation and Maintenance Function, BSC
X
X
X
X
RTF
Receive Transmit Function
X
X
X
X
RXF
Receive Function
X
TXF
Transmit Function
X
68P02901W23-S
3-15 Nov 2009
Function identifiers
Chapter 3: Device/function related commands
Function identifiers ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
A function is identified in the system by up to three identifiers, however, not all functions have three device IDs. For functions that have only one or two device identifiers, zeros must be entered for the remaining function identifiers as place holders.
Function ID requirements Table 3-5 lists and defines the Function ID requirements.
Table 3-5
Function ID requirements
Device Names / IDs
Range
BTF
Base Transceiver Function (BTS only)
function ID 1
0-2 1
Identifies maximum number of DRIs supported by this BTF (not M-Cell) M-Cell only
function ID 2
0
Serves as a place holder
function ID 3
0
Serves as a place holder
LCF
Link Control Function (BSC only)
function ID 1
0 - 24
Identifies specific control links to the MSC and/or the BTS
function ID 2
0
Serves as a place holder
function ID 3
0
Serves as a place holder
OMF
Operation and Maintenance Function (BSC and RXCDR only)
function ID 1
None
Identifies the OMF (BSC or BSS sites where BSC type is 2)
function ID 2
0
Serves as a place holder
function ID 3
0
Serves as a place holder
RTF
3-16
Definition
Receive Transmit Function (BSC and BTS only)
function ID 1
0 - 29
Identifies the RTF group to which the RTF belongs
function ID 2
0 - 24
Identifies a specific RTF function
function ID 3
0
Serves as a place holder
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Slots
Slots ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Cage slots are allocated to devices dependent on the site function.
Valid slots table Table 3-6 lists the cage slots that are valid for the software supported devices.
Table 3-6
Valid slots
Device
BSS
BSC
BTS
RXCDR
BSP
cage = 0 slot = 20 or 24 or cage = 1 slot = 20
cage = 0 slot = 20 or 24 or cage = 1 slot = 20
N/A
cage = 0 slot = 25 or 26 or cage = 1 slot = 25
BTP
N/A
N/A
cage = 15 slot = 20 or 24 or cage = 14 slot = 20
N/A
CSFP
18 - 25 cage 0 - 13
18 - 25 cage 0 - 13
18 - 25 cage 2 - 15
25 or 26 cage 0 - 13
DHP
18 - 25 cage 0 - 13
N/A
18 - 25 cage 2 - 15
N/A
DRI
7, 9, 11, 13, 15, 17
N/A
7, 9, 11, 13, 15, 17
N/A
EAS
15 - 18 (daughter slots)
15 - 18 (daughter slots)
15 - 18 (daughter slots)
15 - 18 (daughter slots)
GCLK
device_id1 = 0 slot = 5 or device_id1 = 1 slot = 3
device_id1 = 0 slot = 5 or device_id1 = 1 slot = 3
device_id1 = 0 slot = 5 or device_id1 = 1 slot = 3
device_id1 = 0 slot = 5 or device_id1 = 1 slot = 3
GPROC
18 - 25 cage 0 - 13
18 - 25 cage 0 - 13
18 - 25 cage 2 - 15
25 or 26 cage 0 - 13
MSI
6 - 17
6 - 17
MSI type = 0 slot = 6 - 17 or MSI type = 1, 255 (slot = N/A)
MSI type = 0 slot = 6 - 10 or MSI type = 1, 255 slot = 6 - 24
68P02901W23-S
3-17 Nov 2009
equip/unequip command matrix
Chapter 3: Device/function related commands
equip/unequip command matrix ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Table 3-7 is a matrix showing which devices and functions can be equipped and unequipped inside and outside of the SYSGEN ON mode.
Table 3-7
Equip/Unequip command matrix
Device/ Function
Equip in SYSGEN
Equip outside SYSGEN
Unequip in SYSGEN
Unequip outside SYSGEN
BSP
Supported
Supported
Supported
Supported only if standby device.
BTP
Supported
Supported
Supported
Supported only standby device.
CAB
Supported
Type B command: lock the site before entering the equip or unequip commands.
Unsupported
Unsupported
CAGE
Supported
Type B command: lock the site before entering the equip or unequip commands.
Unsupported
Unsupported
CBL
Supported
Supported
Supported
Supported
COMB
Supported
Supported
Supported
Supported
CSFP
Supported
Supported
Supported
Supported
DHP
Supported
Supported
Supported
Supported
DRI
Supported
Supported
Supported
Supported
EAS
Supported
Supported
Supported
Supported
GCLK
Supported
Supported
Supported
Supported
GPROC
Supported
Supported
Supported
Supported
KSW
Supported
Supported
Supported
Supported
LCF
Supported
Supported
MSI
Supported
Supported
Unequip LCF is only supported if no sites exist on the LCF. Supported
Supported
NOTE The equip/unequip commands do not support the MSIs of type NIU2 (that is, an MSI at a Horizon II site). MTL
Supported
Unsupported
Supported
Supported
OMF
Supported
Supported
Supported
Unsupported
OML
Supported
Unsupported
Supported
Supported Continued
3-18
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 3-7
equip/unequip command matrix
Equip/Unequip command matrix (Continued)
Device/ Function
Equip in SYSGEN
Equip outside SYSGEN
Unequip in SYSGEN
Unequip outside SYSGEN
OPL
Supported
Unsupported
Supported
Supported
PATH
Supported
Supported
Supported
Supported
{26740} PSI
Supported
Supported
Supported
Supported
RSL
Supported
Supported
Supported
Supported
RTF
Supported
Supported
Supported
Supported
SITE
Supported
Supported
Supported
Supported
XBL
Supported
Supported
Supported
Supported
68P02901W23-S
3-19 Nov 2009
Alarm devices
Chapter 3: Device/function related commands
Alarm devices ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Table 3-8 shows the valid alarm reporting devices and alarm devices that are subject to throttling. For the associated alarm code ranges, refer to Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) in which alarms are fully described.
Table 3-8
Alarm devices
Device Name
Valid Alarm Reporting Device
Valid Alarm Throttle Device
BCUP
YES
NO
BSP
YES
YES
BSS
YES
YES
BTP
YES
YES
CAB
NO
NO
CAGE
YES
YES
CBL
YES
NO
CBUS
YES
NO
CELL
YES
NO
COMB
YES
NO
CSFP
NO
NO
DHP
YES
NO
DRI
YES
YES
EAS
YES
NO
GCLK
YES
YES
GPROC
YES
YES
IAS
YES
NO
KSW
YES
YES
LAN
YES
NO
MMS
YES
YES
MSI
YES
YES
MTL
YES
YES
OMC
YES
NO
OML
YES
NO
OPL
YES
NO
PATH
YES
NO
PBUS
YES
NO
RSL
YES
YES Continued
3-20
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 3-8
68P02901W23-S
Alarm devices
Alarm devices (Continued)
Device Name
Valid Alarm Reporting Device
Valid Alarm Throttle Device
SBUS
YES
NO
SITE
YES
NO
TBUS
YES
NO
TDM
YES
NO
TRU
YES
NO
TSLOT
YES
NO
XBL
YES
YES
XCDR
YES
YES
3-21 Nov 2009
add_cell
Chapter 3: Device/function related commands
add_cell ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The add_cell command adds a cell to the CM database. The add_cell command is invoked with the location and gsm_cell_idparameters. After the command is entered, a series of prompts to define the cell are displayed. The prompted parameters are described in Related information on page 3-25. Different sites can be equipped with various numbers of cells. Only one cell is permitted at an M-Cellcity, Horizonmicro or Horizoncompact site. The system rejects the add_cell command if it is entered for one of these sites, where a cell exists. Sites can have up to six cells. The system rejects the add_cell command if it is entered for a site where six cells exist. This command can be abandoned at any time by entering done in response to any prompt. If a database parameter has a default, the default value can be entered by pressing the RETURN key. If a database parameter has a default value and a value outside the parameter valid range is typed, the system uses the default value. If the database parameter does not have a default value and no value or a value outside the parameter valid range is entered, the command is abandoned, losing any previously entered parameters. Security level
4
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
The add_cell command is not allowed at an RXCDR.
Operator actions
Reply to prompts as displayed, directly or in a script.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax add_cell [cell_name]
3-22
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
Input parameters gsm_cell_id Specifies the GSM cell ID for the cell to be added. The format for the GSM cell ID depends on: •
The system being used (PGSM, EGSM, DCS1800, PCS1900, or GSM850)
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled: Seven parameter format: a b c d e f g
Where:
is: a
first digit of the MCC (Mobile Country Code).
b
second digit of the MCC.
c
third digit of the MCC.
d
first digit of the MNC (Mobile Network Code).
e
second digit of the MNC.
f
LAC (Local Area Code).
g
CI (Cell Identity).
Four parameter format: abc zde f g Where:
is: a
first digit of the MCC (Mobile Country Code).
b
second digit of the MCC.
c
third digit of the MCC.
z
first digit of the MNC (Mobile Network Code).
d
second digit of the MNC.
e
third digit of the MNC.
f
LAC (Local Area Code).
g
CI (Cell Identity).
Only PCS1900 and GSM850 systems can use a three digit MNC.
NOTE A cell_name as defined by the cell_name command is not valid in add_cell commands.
68P02901W23-S
3-23 Nov 2009
Examples
Chapter 3: Device/function related commands
location Specifies the location of the cell: 0 - 140
BTS
cell_name The name to be assigned to the Cell ID. The cell name must be entered inside double quotation marks. The cell name can be from one to 31 alphanumeric characters. The dash character can be used as a separator. The underscore character cannot be used as part of the name or as a separator. Double quotation marks cannot be used as part of a cell name. Cell names cannot be equivalent to the following character strings in upper or lower case: all no name defined name not available Entering two consecutive double quotation marks removes the current cell name. If no value is entered for this parameter, the current cell name displays.
Examples Example 1 In this example, a cell with GSM cell ID 5 4 3 2 1 61986 34944 at site 0 is added to the CM database: add_cell 5 4 3 2 1 61986 34944 0 Where:
is: 5 4 3 2 1 61986 34944
GSM cell ID.
0
location.
System response Prompts are displayed for the parameters to define the cell.
Example 2 In this example, a cell with GSM cell ID 5 4 3 2 1 61986 34944 at site 5 (a BTS site) is added to the CM database. add_cell 5 4 3 2 1 61986 34944 5 Where:
3-24
is: 5 4 3 2 1 61986 34944
GSM cell ID.
5
location.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
System response Prompts are displayed for the parameters to define the cell.
Example 3 In this example, a PCS1900 cell with GSM cell ID 5 4 3 7 2 1 61986 34944 is added to the CM database. This example shows the four-parameter GSM cell ID format. add_cell 543 721 61986 34944 0 Where:
is: 543 721 61986 34944
GSM cell ID.
0
location.
System response Prompts are displayed for the parameters to define the cell.
References Related information Table 3-9 lists the prompts for the add_cell command. Parameters are assigned by entering the parameter value only, or the contents of the input column of the add_cell command prompts table exactly as presented, where x is the parameter value. For example, a CRM wait indication parameter value of 5 can be assigned by entering the following at the prompt: wait_indication_parameters=5 The word odd in the Range column indicates that only odd values are accepted. Similarly, the word even indicates that only even values are accepted. If a parameter has a default value, the default value can be entered for the parameter by pressing the RETURN key. If the parameter has a default value and an invalid value is entered, an error message is presented and the parameter is assigned the default value. If a parameter does not have a default value and the response to the prompt is not correct, or if no response to the prompt is entered, the system aborts the add_cell command and displays the system prompt. All values entered to that point are lost and must be re-entered if the cell is to be added using the add_cell command. There is a time limit of 30 seconds in which to enter a response to a prompt. If a proper response is not entered within the time limit, the command aborts and all values entered up to that point are lost. To abort the command manually, type done after any prompt.
68P02901W23-S
3-25 Nov 2009
References
Chapter 3: Device/function related commands
NOTE The copy_cell command description includes two alphabetical listings of which parameters are included for that command and which are not included.
Table 3-9
add_cell command prompts Prompt
Input
Range
Default
0 - 63
None
1 (pgsm) 2 (egsm) 4 (dcs1800) 8 (pcs1900) 16 (gsm850) Use numeric values or text string.
None
0 - 255
5
0, 1, 2, 4, or 6
0
Enter base station identity code:
bsic=x
Enter the Frequency Type:
frequency_type=x
Enter wait indication parameters:
wait_indication_parameters=x
Enter common control channel configuration:
ccch_conf=x
Enter blocks reserved for access grant:
bs_ag_blks_res=x
0 - 7
0
Enter multiframes between transmissions of paging messages:
bs_pa_mfrms=x
0 - 7
0
Enter extended paging active:
extended_paging_active=x
0 or 1
0
Enter number of SDCCHs preferred:
number_sdcchs_preferred=x
4 - 44 (if ccch_conf=1) 8 - 48 (if ccch_conf≠1)
8
Enter enable incoming handover:
en_incom_ho=x
0 or 1
1
Enter intra cell handover allowed:
intra_cell_handover_allowed=x
0 - 2
1
Enter inter cell handover allowed:
inter_cell_handover_allowed=x
0 - 3
1
Enter number of preferred cells:
number_of_preferred_cells=x
1 - 16
16
Enter handover margin default:
ho_margin_def=x
-63 to 63
8
Enter handover recognized period:
handover_recognized_period=x
2 - 64
2
Continued
3-26
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 3-9
References
add_cell command prompts (Continued) Prompt
Input
Range
Default
Enter uplink rxqual handover allowed:
ul_rxqual_ho_allowed=x
0 or 1
1
Enter downlink rxqual handover allowed:
dl_rxqual_ho_allowed=x
0 or 1
1
Enter uplink rxlev handover allowed
ul_rxlev_ho_allowed=x
0 or 1
1
Enter downlink rxlev handover allowed:
dl_rxlev_ho_allowed=x
0 or 1
1
Enter alternate flag for SDCCH handover:
sdcch_ho=x
0 or 1
1
Enter alternate SDCCH handover timer value:
sdcch_timer_ho=x
1 - 31
1
Enter interference handover allowed:
interfer_ho_allowed=x
0 or 1
1
Enter power handover allowed:
pwr_handover_allowed=x
0 or 1
1
Enter MS distance allowed:
ms_distance_allowed=x
0 or 1
0
Enter alternate flag for MS power control processing:
mspwr_alg=x
0 or 1
0
Enter handover power level:
handover_power_level=x
2 - 19
None
Enter power control indicator for hopping through BCCH:
pwrc=x
0 or 1
1
Enter interference measurement averaging period (intave):
intave=x
1 - 31
8
Enter timing advance period:
timing_advance_period=x
1 - 31
4
Enter MS power control period:
ms_p_con_interval=x
0 - 31
2
Enter MS timeout for MS power control:
ms_p_con_ack=x
0 - 31
2
Enter MS power control allowed:
ms_power_control_allowed=x
0 or 1
1
Enter BTS power control interval:
bts_p_con_interval=x
0 - 31
2
Enter BTS timeout for BTS power control:
bts_p_con_ack=x
0 - 31
1
Enter BTS power control allowed:
bts_power_control_allowed=x
0 or 1 (0 for M-Cellmicro)
0
Continued
68P02901W23-S
3-27 Nov 2009
References
Chapter 3: Device/function related commands
Table 3-9
add_cell command prompts (Continued) Prompt
Input
Range
Default
Enter power increment step size for uplink:
pow_inc_step_size_ul=x
2 - 14 EVEN
2
Enter power increment step size for downlink:
pow_inc_step_size_dl=x
2 - 14 EVEN
2
Enter power reduction step size for uplink:
pow_red_step_size_ul=x
2 - 4 EVEN
2
Enter power reduction step size for downlink:
pow_red_step_size_dl=x
2 - 4 EVEN
2
Enter dynamic step adjust algorithm:
dyn_step_adj=x
0 or 1
0
Enter factor of maximum power reduction:
dyn_step_adj_fmpr=x
0 - 10
10
Enter maximum BTS transmit power:
max_tx_bts=x
0 - 21 (0 - 6 for M-Cellmicro)
0
Enter maximum transmit MS:
max_tx_ms=x
5 - 39 odd only (PGSM or EGSM). 0 - 36 even only (DCS1800). 0 - 32 even only, and 33 (PCS1900).
39 36 33
Enter receive level minimum default:
rxlev_min_def=x
0 - 63
15
Enter MS transmit power maximum default:
ms_txpwr_max_def=x
5 - 39 odd only (PGSM or EGSM). 0 - 36 even only (DCS1800). 0 - 32 even only, and 33 (PCS1900).
39 36 33
Enter decision algorithm number:
decision_alg_type=x
0 - 31
0
Enter decision alg 1 dl rxlev avg h:
decision_1_dl_rxlev_av_h =x
0 - 3
0
Enter decision alg 1 dl rxlev avg ih:
decision_1_dl_rxlev_av_ih =x
0 - 3
0
Enter decision alg 1 dl rxlev avg p:
decision_1_dl_rxlev_av_p =x
0 - 3
0
Enter decision alg 1 dl rxqual avg h:
decision_1_dl_rxqual_av_h =x
0 - 3
0
Enter decision alg 1 dl rxqual avg p:
decision_1_dl_rxqual_av_p =x
0 - 3
0
Enter decision alg 1 n1:
decision_1_n1=x
1 - 31
1
Enter decision alg 1 n2:
decision_1_n2=x
1 - 31
1 Continued
3-28
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 3-9
References
add_cell command prompts (Continued) Prompt
Input
Range
Default
Enter decision alg 1 n3:
decision_1_n3=x
1 - 31
1
Enter decision alg 1 n4:
decision_1_n4=x
1 - 31
1
Enter decision alg 1 n5:
decision_1_n5=x
1 - 31
1
Enter RSS decision alg 1 n6:
decision_1_n6=x
1 - 31
1
Enter RSS decision alg 1 n7:
decision_1_n7=x
1 - 31
1
Enter RSS decision alg 1 n8:
decision_1_n8=x
1 - 31
1
Enter decision alg 1 ncell rxlev avg h calc:
decision_1_ncell_rxlev_av_h_calc =x
0 - 3
0
Enter decision alg 1 p1:
decision_1_p1=x
1 - 31
1
Enter decision alg 1 p2:
decision_1_p2=x
1 - 31
1
Enter decision alg 1 p3:
decision_1_p3=x
1 - 31
1
Enter decision alg 1 p4:
decision_1_p4=x
1 - 31
1
Enter decision alg 1 p5:
decision_1_p5=x
1 - 31
1
Enter decision alg 1 p6:
decision_1_p6=x
1 - 31
1
Enter decision alg 1 p7:
decision_1_p7=x
1 - 31
1
Enter decision alg 1 p8:
decision_1_p8=x
1 - 31
1
Enter decision alg 1 power budget rxlev:
decision_1_p_bgt_rxlev_av_h =x
0 - 3
0
Enter decision alg 1 timing advance alg:
decision_1_tim_adv_av_alg =x
0 - 3
0
Enter decision alg 1 ul rxlev avg h:
decision_1_ul_rxlev_av_h =x
0 - 3
0
Enter decision alg 1 ul rxlev avg ih:
decision_1_ul_rxlev_av_ih =x
0 - 3
0
Enter decision alg 1 ul rxlev avg p:
decision_1_ul_rxlev_av_p =x
0 - 3
0
Enter decision alg 1 ul rxqual avg h:
decision_1_ul_rxqual_av_h =x
0 - 3
0
Enter decision alg 1 ul rxqual avg p:
decision_1_ul_rxqual_av_p =x
0 - 3
0
Enter quality band processing allowed:
alt_qual_proc=x
0 or 1
0
Continued
68P02901W23-S
3-29 Nov 2009
References
Chapter 3: Device/function related commands
Table 3-9
add_cell command prompts (Continued) Prompt
Input
Range
Default
Enter power control threshold l_rxqual_ul_p:
l_rxqual_ul_p=x
If alt_qual_proc = 0, 0 - 1810. If alt_qual_proc = 1, 0 - 7.
226 BER or 4 QBand
Enter power control threshold l_rxqual_dl_p:
l_rxqual_dl_p=x
If alt_qual_proc = 0, 0 - 1810. If alt_qual_proc = 1, 0 - 7.
226 BER or 4 QBand
Enter power control threshold u_rxqual_ul_p:
u_rxqual_ul_p=x
If alt_qual_proc = 0, 0 - 1810. If alt_qual_proc = 1, 0 - 7.
28 BER or 1 QBand
Enter power control threshold u_rxqual_dl_p:
u_rxqual_dl_p=x
If alt_qual_proc = 0, 0 - 1810. If alt_qual_proc = 1, 0 - 7.
28 BER or 1 QBand
Enter handover threshold l_rxqual_ul_h:
l_rxqual_ul_h=x
If alt_qual_proc = 0, 0 - 1810. If alt_qual_proc = 1, 0 - 7.
453 BER or 5 QBand
Enter handover threshold l_rxqual_dl_h:
l_rxqual_dl_h=x
If alt_qual_proc = 0, 0 - 1810. If alt_qual_proc = 1, 0 - 7.
453 BER or 5 QBand
Enter handover threshold l_rxlev_ul_h:
l_rxlev_ul_h=x
0 - 63
10
Enter handover threshold l_rxlev_dl_h:
l_rxlev_dl_h=x
0 - 63
1
Enter handover threshold u_rxlev_ul_ih:
u_rxlev_ul_ih=x
0 - 63
45
Enter handover threshold u_rxlev_dl_ih:
u_rxlev_dl_ih=x
0 - 63
45
Continued
3-30
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 3-9
References
add_cell command prompts (Continued) Prompt
Input
Range
Default
0 - 63 (only if ext_range_cell=0). 0 - 219 (if ext_range_cell=1).
None
Enter handover threshold mobile max range:
ms_max_range=x
Enter power control threshold l_rxlev_ul_p:
l_rxlev_ul_p=x
0 - 63
30
Enter power control threshold l_rxlev_dl_p:
l_rxlev_dl_p=x
0 - 63
30
Enter power control threshold u_rxlev_ul_p:
u_rxlev_ul_p=x
0 - 63
40
Enter power control threshold u_rxlev_dl_p:
u_rxlev_dl_p=x
0 - 63
40
Enter Alternate flag for missing report:
missing_rpt=x
0 or 1
0
Enter Alternate flag for BA allocating process:
ba_alloc_proc=x
0 or 1
0
Enter RSS link fail:
link_fail=x
0 - 15
4
Enter link about to fail:
link_about_to_fail=x
0 - 15
2
Enter Alternate flag for full power RF loss:
full_pwr_rfloss=x
0 or 1
0
Enter cell bar access switch:
cell_bar_access_switch=x
0 or 1
0
Enter cell bar access class:
cell_bar_access_class=x
0 - 65535
0
Enter emergency class switch:
emergency_class_switch=x
0 or 1
0
Enter report resource TCH full high water mark:
report_resource_tch_f_high_ water_mark=x
0 - 255
2
Enter report resource TCH full low water mark:
report_resource_tch_f_low_ water_mark=x
0 - 255
12
NOTE The value for report_resource_tch_f_high_water_mark must be set less than the value for report_resource_tch_f_low_water_mark. If report_resource_tch_f_high_water_mark, is greater than report_resource_tch_f_low_water_mark the system rejects the add_cell command. Enter receive level access minimum:
rxlev_access_min=x
Enter uplink dtx preference:
dtx_required=x
Enter IMSI attach detach:
attach_detach=x
0 - 63
None
0 - 2
2
0 or 1
0 Continued
68P02901W23-S
3-31 Nov 2009
References
Chapter 3: Device/function related commands
Table 3-9
add_cell command prompts (Continued) Prompt
Input
Range
Default
0 - 255
255
0 - 3
0
5 - 39 odd only (PGSM and EGSM). 0 - 36 even only (DCS1800). 0 - 32 even only, and 33 (PCS1900).
2
Enter NCC of PLMN allowed:
ncc_of_plmn_allowed=x
Enter maximum retransmissions on RACH:
max_retran=x
Enter maximum mobile transmit power on CCCH:
ms_txpwr_max_cch=x
Enter tx_integer for RACH retransmit spacing:
tx_integer=x
0 - 15
4
Enter radio link timeout:
radio_link_timeout=x
0 - 15
4
Enter MS reestablish allowed:
reestablish_allowed=x
0 or 1
0
Enter cell reselect hysteresis:
cell_reselect_hysteresis=x
0 - 7
None
EnterC2 cell reselection parameter indicator:
cell_reselect_param_ind=x
0 or 1
0
Enter C2 cell bar qualify:
cell_bar_qualify=x
0 or 1
0
Enter C2 cell reselection offset:
cell_reselect_offset=x
0 - 63
0
Enter C2 temporary offset:
temporary_offset=x
0 - 7
0
Enter C2 penalty time:
penalty_time=x
0 - 31
0
Enter rapid power down procedure active:
rapid_pwr_down=x
0 or 1
0
Enter rapid power down trigger threshold:
rpd_trigger=x
0 - 63
45
Enter rapid power down level offset:
rpd_offset=x
0 - 63
8
Enter rapid power down averaging period:
rpd_period=x
1 - 32
2
Related commands
3-32
copy_cell on page 3-179
del_cell on page 3-192
disp_gsm_cells on page 3-314
freq_types_allowed on page 3-417
disp_cell on page 3-241
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
add_conn
add_conn ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The add_conn command adds MMS connectivity between the RXCDR and the BSS. Connectivity can be added for a maximum of 21 MMSs at a BSC or RXCDR regardless of how many RXCDRs or BSSs are connected. This command allows the operator to specify the E1 connectivity information identifying which RXCDR is associated with the E1 link and the device identity within the RXCDR to which the E1 link is connected. This connectivity information must be specified for each E1 link connecting to an RXCDR. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator action)
Prerequisites
Enter this command at the BSC or RXCDR only.
Format Syntax add_conn
Input parameters local_mms_id_1 First identifier of the MMS at the local site. The term ‘local site’ refers to the site where the command is being entered. local_mms_id_2 Second identifier of the MMS at the local site. network_entity_id The AXCDR or ABSS device identifier that represents the actual RXCDR or BSS with which this MMS is communicating. remote_mms_id_1 First identifier of the MMS at the remote site. The term ‘remote site’ refers to the site to which the local site is being connected.
68P02901W23-S
3-33 Nov 2009
Example
Chapter 3: Device/function related commands
remote_mms_id_2 Second identifier of the MMS at the remote site. The add_conn command can be executed from either the BSC or RXCDR. Table 3-10 shows the ranges for several input parameters dependent on where the command is executed.
Table 3-10
add_conn valid ranges Execution location
Input parameter
BSC
RXCDR
local_mms_id_1
{22169} 0 - 95
0 - 123
local_mms_id_2
0 or 1
0 or 1
network_entity_id
1 - 254
1 - 254
remote_mms_id_1
0 - 123
{22169} 0 - 95
remote_mms_id_2
0 or 1
0 or 1
Example This example adds MMS connectivity between BSC MMS 4 1 and RXCDR MMS 9 0 of RXCDR 3, represented by the equipped device AXCDR 3. add_conn 4 1 3 9 0 Where:
is: 4
local_mms_id_1
1
local_mms_id_2
3
network_entity_id
9
remote_mms_id_1
0
remote_mms_id_2
System response COMMAND ACCEPTED
References Related commands del_conn on page 3-195
3-34
disp_conn on page 3-261
mod_conn on page 3-442
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
add_neighbor
add_neighbor ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The add_neighbor command adds a GSM or UTRAN neighbor to an existing cell Neighbor Cell List. {31400} Addition of TD-SCDMA neighbor cells is only allowed when TD-SCDMA and GSM interworking feature is enabled (td_enabled set to 1). {33812} The maximum number of TD-SCDMA neighbors per GSM cell is increased from 16 to 32. A GSM cell can have up to 64 GSM neighbors. A maximum of 64 GSM neighbors can be in the BA_BCCH list but only 32 can be effective. A maximum of 32 GSM neighbors can be in the BA_SACCH list and a maximum of 32 GSM neighbors can be in the BA_GPRS list. The neighbor frequency can change from one range to another (with respect to Table 3-11 and Table 3-12) when adding or deleting a neighbor for a particular source cell. Hence the maximum number of neighbors that can be added to a source cell can change depending upon the frequency range of the neighbor cells: •
If the source frequency type is DCS1800, a neighbor cannot have a frequency type of PCS1900. If the source frequency type is PCS1900, a neighbor cannot have a frequency type of DCS1800.
•
If a DCS1800 neighbor exists in a neighbor list, no PCS1900 neighbors can be added.
•
If a PCS1900 neighbor exists in a neighbor list, no DCS1800 neighbors can be added.
Table 3-11 lists the frequency range and maximum number of neighbors for an EGSM or PGSM source cell.
68P02901W23-S
3-35 Nov 2009
Description
Chapter 3: Device/function related commands
Table 3-11
Neighbor frequency and number with an EGSM or PGSM source cell
Neighbor frequency range
Maximum number of neighbors
1 - 124
64
975 - 1023
49
0, 1 - 124
64
0, 975 - 1023
50 if the source frequency is in the EGSM frequency, that is: 0, 975 1023 17 if the source frequency is in the PGSM frequency, that is: 1 - 124
1 - 124, 975 - 1023
64 if the source frequency is zero, where the number of EGSM neighbors is less than or equal to 16.
0, 1 - 124, 975 - 1023
64 if the source frequency is in the EGSM frequency range, where the number of EGSM neighbors is less than or equal to 16. 64 if the source frequency is in the PGSM frequency range, where the number of EGSM frequencies is less than or equal to 17.
512 - 885
64
Table 3-12 lists the frequency range and maximum number of neighbors for a DCS 1800 source cell.
Table 3-12
3-36
Neighbor frequency and number with DCS1800 source cell
Neighbor frequency range
Maximum number of neighbors
1 - 124
64
975 - 1023
49
0, 1 - 124
17
0, 975 - 1023
17
1 - 124 and 975 - 1023
16
0, 1 - 124 and 975 - 1023
17
512 - 885
64
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Description
The system updates the maximum number of GSM neighbor cells (refer Table 3-11 and Table 3-12). Then check the maximum number of GSM neighbor cells based on the BA_BCCH list and BA_SACCH list options provided in the following table. One or more UTRAN neighbor exists (Yes/No)?
No
Yes
Add neighbor to the BA BCCH list (Yes/No)?
Add neighbor to the BA SACCH list (Yes/No)?
Max no. of neighbor cells that can be equipped for BA BCCH list
Max no. of neighbor cells that can be equipped for BA SACCH list
Yes
No
64
-
No
Yes
-
32
Yes
Yes
-
32
Yes
No
31
No
Yes
-
31
Yes
-
31
Yes
Max no. of GSM neighbor cells that can be equipped
64
62
NOTE •
If there are no UTRAN BCCH neighbors, a maximum of 64 BCCH neighbors can be equipped for GSM. Aternatively, if there are one or more UTRAN BCCH neighbors, a maximum of 31 BCCH neighbors can be equipped for GSM.
•
If there are no UTRAN SACCH neighbors, a maximum of 32 SACCH neighbors can be equipped for GSM. Aternatively, if there are one or more UTRAN SACCH neighbors, a maximum of 31 SACCH neighbors can be equipped for GSM.
For UTRAN neighbor cells, when the Enhanced 2G/3G Handover feature is unrestricted, up to 32 UTRAN BCCH neighbors, 32 UTRAN SACCH neighbors and eight Blind Search neighbors can be added per cell. A total of 64 UTRAN neighbors can be created but a maximum of 32 can be on the UTRAN BA_BCCH list only. After the add_neighbor command is entered, a series of prompts are presented where parameters defining the GSM or UTRAN neighbor are entered. The prompted parameters are described in the Related information on page 3-43. The required input parameters depend on whether the neighbor cell is internal to the BSS or external to the BSS. The parameters also depend on whether the neighbor is a GSM, UTRAN, or Blind Search cell. When the source cell is a PGSM or EGSM cell, the maximum number of EGSM and PGSM band neighbor cells allowed is restrained (refer Table 3-11). When the source cell is a DCS1800 or PCS1900 cell, the maximum number of EGSM and PGSM band neighbor cells allowed is restrained (refer Table 3-12).
68P02901W23-S
3-37 Nov 2009
Format
Chapter 3: Device/function related commands
If the Inter_RAT (Radio Access Technology) Handover feature and/or Enhanced 2G/3G Handover feature is unrestricted, this command supports the UTRAN cell identity format. Security level
4
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
To be on the Neighbor Cell List, a cell must be the destination of handovers from the Neighbor List owner. Synchronized handovers are allowed only between cells that are at the same site. For a PGSM or EGSM site, only external neighbor cells with BCCH ARFCNs in the 1 - 124 can be added. For a GSM 850 site, only external neighbor cells with BCCH ARFCNs in the following ranges can be added: 0 - 124 128 - 251 512 - 885, and 975 - 1023. For handovers to UTRAN cells, the Inter-RAT Handover feature and/or the Enhanced 2G/3G Handover feature must be unrestricted.
Operator action
Reply to prompts as displayed, directly or in a script.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax add_neighbor The cell_name can be used for the neighbor when the neighbor is internal.
Input parameters source_cell_id GSM cell ID of the cell to which a neighbor cell is to be assigned. The format for the GSM cell ID depends on: •
The system being used (PGSM, EGSM, DCS1800, PCS1900, GSM 850)
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
•
Whether the cell is a UTRAN cell.
The name of the cell created using the cell_name command can be entered in place of the cell_id. When the cell name is entered, insert within double quotation marks.
3-38
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
Only PCS1900 and GSM 850 systems can use a three digit MNC. neighbor_cell_id GSM cell ID of the cell being assigned as a neighbor cell. The name of the cell created using the cell_name command can be entered in place of the cell_id. When the cell name is entered, insert within double quotation marks. The cell_name can only be entered in place of the neighbor_cell_id for internal neighbor cells. Only PCS1900 and GSM 850 systems can use a three digit MNC. The string test can be entered for this field where is a value from 1 to 64. This permits test neighbors to be added to the BA_SACCH and/or BA_BCCH lists. When a test neighbor is added, the value entered in the placement field is ignored and the frequency is the only prompted parameter. The system checks the BSIC of the neighbor cell against the ncc_of_plmn value of the source cell. If they are incompatible, the system rejects the command. See the descriptions for bsic on page 6-93 and ncc_of_plmn_allowed on page 6-595 for more information.
NOTE A cell_name cannot be associated with UMTS neighbor.
placement internal
The neighbor cell to be added is inside the BSS.
external
The neighbor cell to be added is outside the BSS.
umts_fdd
The neighbor cell to be added is a UTRAN BCCH or SACCH neighbor.
umts_fdd_blind
The neighbor cell is a UTRAN Blind Search neighbor.
{31400} umts_tdd
Specifies that the new neighbor is a TD-SCDMA neighbor.
68P02901W23-S
3-39 Nov 2009
Examples
Chapter 3: Device/function related commands
Table 3-13
Prompted Parameters for TD-SCDMA Neighbors
Prompt
Required
Value Definition/Range/Default
{31400} Enter the UTRAN Absolute Radio Freq Chan Number:
Yes
10054 - 10121
{31400} Enter the TD-SCDMA cell parameter:
Yes
0 - 127
{31400} Enter the Time Switched Transmit Diversity Flag:
No
0 – Disabled 1 – Enabled Default: 0 (Disabled)
{31400} Enter the Space Code Transmit Diversity Flag:
No
0 – Disabled 1 – Enabled Default: 0 (Disabled)
Examples Example 1 In this example, a cell with ID 5 4 3 2 1 61986 34945 is added to the Neighbor Cell List of a cell with ID 5 4 3 2 1 61986 34944. The example demonstrates adding a cell to the Neighbor Cell List that is internal to that neighbor cell. The word, internal follows the second cell ID indicating that the cell being added is internal to, and shares the same BSS of the src_gsm_cell_id. add_neighbor 5 4 3 2 1 61986 34944 5 4 3 2 1 61986 34945 internal Where:
is: 5 4 3 2 1 61986 34944
source_cell_id
5 4 3 2 1 61986 34945
neighbor_cell_id
internal
placement
System response COMMAND ACCEPTED After verification of the command, the MMI prompts for the required parameters to describe the neighbor cell being added (see Table 3-14 in Related information).
3-40
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 2 In this example, a cell with ID 5 4 3 2 1 61986 34944 is added to the Neighbor Cell List of a cell with ID 5 4 3 2 1 71543 12444. The example demonstrates adding a cell to the Neighbor Cell List that is external to that neighbor cell. The word, external follows the second cell ID indicating that the cell being added is external to, and does not share the BSS of the src_gsm_cell_id. add_neighbor 5 4 3 2 1 71543 12444 5 4 3 2 1 61986 34944 external Where:
is: 5 4 3 2 1 71543 12444
source_cell_id
5 4 3 2 1 61986 34944
neighbor_cell_id
external
placement
System response COMMAND ACCEPTED After verification of the command, the MMI prompts for the required parameters to describe the neighbor cell being added (see Table 3-14 in Related information).
Example 3 In this example, a cell with ID 5 4 3 2 1 61986 34945 is added to the internal Neighbor Cell List of a cell with the cell name ‘north-london’: add_neighbor “north-london” 5 4 3 2 1 61986 34945 internal Where:
is: north-london
source_cell_name
5 4 3 2 1 61986 34945
neighbor_id
internal
placement
System response COMMAND ACCEPTED After verification of the command, the MMI prompts for the required parameters to describe the neighbor cell being added (see Table 3-14 in Related information).
68P02901W23-S
3-41 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 4 In this example, a PCS1900 cell with ID 543 721 61986 34945 is added to the internal Neighbor Cell List of a cell with ID 543 721 61986 34944: add_neighbor 543 721 61986 34944 543 721 61986 34945 internal Where:
is: 543 721 61986 34944
source_cell_id
543 7211 61986 34945
neighbor_cell_id
internal
placement
System response COMMAND ACCEPTED After verification of the command, the MMI prompts for the required parameters to describe the neighbor cell being added (see Table 3-14 in Related information).
Example 5 In this example, UTRAN cell ID 4 9 6 2 3 1 1 1 1 is specified as a neighbor of GSM cell ID 0 0 1 0 1 1 4 with all values entered for all parameters. add_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 umts_fdd Where:
is: 0010114
GSM cell ID
496231111
neighbor cell ID
umts_fdd
placement
System response Add neighbor to UTRAN BCCH list (Yes/No)? Yes Add neighbor to UTRAN SACCH list (Yes/No)? Yes Enter the UTRAN Absolute Radio Freq Chan Number: 10762 Enter the Scrambling Code: 200 Enter the Diversity Enabled Flag: 1 Enter the UMTS measurement margin: 15 Enter the neighbor measurement avg period: 10 COMMAND ACCEPTED
3-42
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
Example 6 In this example, the FDD_ARFCN 10755 is specified as a UTRAN Blind Search neighbor of GSM cell 0 0 1 0 1 1 4. add_neighbor 0 0 1 0 1 1 4 umts_fdd_blind Where:
is: 0010114
GSM cell ID
umts_fdd_blind
placement type
System response Enter the UTRAN Absolute Radio Freq Chan Number:
10755
COMMAND ACCEPTED
Example 7 {31400} This example specifies TD-SCDMA cell 4 9 6 3 2 1 1 1 1 as a neighbor of GSM cell 0 0 1 0 1 1 4 with all values entered for all parameters when TD-SCDMA inter-working is enabled. add_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 umts_tdd Where:
is: 0010114
GSM cell ID
496231111
neighbor cell ID
umts_tdd
placement type
System response Enter the UTRAN Absolute Radio Freq Chan Number: 10110 Enter the TD-SCDMA cell parameter: 100 Enter the Time Switched Transmit Diversity Flag: 1 Enter the Space Code Transmit Diversity Flag: 1 COMMAND ACCEPTED
References Related information There is a time limit of 30 seconds in which to enter responses to the parameter prompts that are presented. If a proper response is not entered within the time limit, the command is abandoned and all values entered up to that point are lost. 68P02901W23-S
3-43 Nov 2009
References
Chapter 3: Device/function related commands
Table 3-14 lists the add_neighbor command prompts for GSM BA BCCH and SACCH neighbors.
Table 3-14 neighbors.
add_neighbor command prompts for GSM BA BCCH and SACCH
Prompt
Range
Default
Notes
Add neighbor to the BA BCCH list (yes/no)?
yes no
yes
Add neighbor to the BA SACCH list (yes/no)?
yes no
yes
Add neighbor to the BAGPRS list (yes/no)?
yes no
yes
These three prompts appear only if the Network Controlled Cell Reselection feature (NCCR) is unrestricted.
Enter the neighbor cell frequency type:
pgsm, egsm, dcs1800, pcs1900, gsm850.
None
N/A for internal neighbors.
Enable synchronization:
1 (Yes) 0 (No)
0
N/A for external neighbors
Enter the BCCH frequency number:
1 - 124 for PGSM, 0 1 - 124, 975 - 1023 for EGSM, 512 - 885 for DCS1800, 512 - 810 for PCS1900.
None A value MUST be entered at this prompt.
N/A for internal neighbors. EGSM BCCH frequencies 0, 975 - 1023 are not available when the egsm_bcch_sd parameter is disabled.
Enter base station identity code (bsic):
0 - 63
None A value MUST be entered at this prompt.
N/A for internal neighbors
Enter MS transmit power maximum:
5 - 39 (odd values only) for PGSM and EGSM, 0 - 36 (even values only) for DCS1800, 0 - 32 (even values only) and 33, for PCS1900.
39 for PGSM and EGSM. 36 for DCS1800 33 for PCS1900.
N/A for internal neighbors
Enter neighbor receive level minimum:
0 - 63
rxlev_min_def of neighbor cell
Required for external neighbors
Enter neighbor handover margin:
-63 to 63
ho_margin_def Required for external neighbors. of neighbor Refer to the description cell of the ho_margin_def parameter. Continued
3-44
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
Table 3-14 add_neighbor command prompts for GSM BA BCCH and SACCH neighbors. (Continued) Prompt
Range
Default
Notes
Enter the power budget surrounding cell hreqave:
1 - 31
8
Enable adjacent channel interference avoidance test?:
1 (Yes) 0 (No)
0 (No)
N/A if Microcell is not purchased.
Enter rxlev difference for adjacent channel interference avoidance test:
-63 to 63
0
N/A if Microcell is not purchased. This prompt applies if previous answer is 1
Enter the power budget algorithm type:
1-7
1
N/A if Microcell is not purchased.
Enter the adjacent channel interference detection handover margin:
-63 to 63
ho_margin_cell This prompt only appears if pbgt_alg_type=7.
Enter the uplink receive level threshold of the serving cell:
0 - 255
None A value MUST be entered at this prompt.
N/A if Microcell is not purchased and pbgt_alg_type 0 3
Enter the downlink receive level threshold of the serving cell:
0 - 255
None
N/A if Microcell is not purchased and pbgt_alg_type 0 3
Enter the qualifying time threshold:
0 - 255
0 SACCH periods
N/A if Microcell is not purchased and pbgt_alg_type 0 4
Enter the qualifying delay time:
0 - 255
0 SACCH periods
N/A if Microcell is not purchased and pbgt_alg_type 0 5
Enter the neighbor cell receive level threshold:
0 - 63
None A value MUST be entered at this prompt.
N/A if Microcell is not purchased and pbgt_alg_type 0 5
Enter the delay time:
0 - 255
0 SACCH periods
N/A if Microcell is not purchased and pbgt_alg_type 0 6
Enter the handover static offset:
0 - 127
0
N/A if Microcell is not purchased and pbgt_alg_type 0 6
Enter the handover dynamic offset:
0 - 127
0
N/A if Microcell is not purchased and pbgt_alg_type 0 6 Continued
68P02901W23-S
3-45 Nov 2009
References
Chapter 3: Device/function related commands
Table 3-14 add_neighbor command prompts for GSM BA BCCH and SACCH neighbors. (Continued) Prompt
Range
Default
Notes
Enter neighbor congestion handover margin:
-63 to 63 To disable congestion handovers to this neighbor, set the value to 63
None. A value MUST be entered at this prompt.
Value must be less than or equal to the ho_margin_cell of the neighbor cell. This prompt is only presented if directed retry or congestion relief is purchased.
Is directed retry allowed at this external neighbor cell?:
1 (Yes) 0 (No)
1
N/A when adding internal neighbors. This prompt is only presented if directed retry or congestion relief is purchased.
Does this neighbor have a carrier with an interfering frequency?
1 (Yes) 0 (No)
0
Only prompted if inner_zone_alg for the source cell is set to 2, and the neighbor is being added to the SACCH list.
Enter the threshold for inner zone handover:
0 - 63
0
Only prompted if ‘Does the neighbor have a carrier with an interfering frequency?’ = 1 (yes).
Enter the margin for inner zone handover:
0 - 63
0
Only prompted if ‘Does the neighbor have a carrier with an interfering frequency?’ = 1 (yes).
Enter the range of the neighbor cell:
normal extended
Normal
This prompt is only presented if the Extended Range Cells feature is unrestricted.
Table 3-15 lists the add_neighbor command prompted parameters for UTRAN BCCH and SACCH neighbors. If the Enhanced 2G-3G feature is restricted, these parameters are not prompted.
Table 3-15 neighbors
add_neighbor command prompts for UTRAN BCCH and SACCH
Prompt
Range
Default
Notes
Add neighbor to UTRAN BCCH list (Yes/No)?
Yes or No
Yes
Add neighbor to UTRAN SACCH list (Yes/No)?
Yes or No
Yes
The values of the BCCH and SACCH prompts determine the value of the umts_ba_type attribute where: BCCH/SACCH is Yes/No º 1, BCCH/SACCH is No/Yes º 2, BCCH/SACCH is Yes/Yes º 3. Continued
3-46
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
Table 3-15 add_neighbor command prompts for UTRAN BCCH and SACCH neighbors (Continued) Prompt
Range
Default
Notes
Enter the UTRAN Absolute Radio Freq Chan Number:
10562 - 10838
None
This sets the fdd_arfcn attribute.
Enter the Scrambling Code:
0 - 511
None
This sets the scr_code attribute that indicates the primary scrambling code of the UTRAN neighbor.
Enter the Diversity Enabled Flag:
0 or 1
0
Enter the UMTS measurement margin:
0 - 20
3
This sets the umts_meas_margin parameter used by the handover algorithm.
Enter the neighbor measurement avg period:
1 - 12
6
This sets the UTRAN neighbor cell measurement averaging period umts_ncell_avg_period attribute.
Table 3-16 lists the add_neighbor command prompted parameters for Blind Search neighbors.
Table 3-16
add_neighbor command prompts for Blind Search neighbors.
Prompt
Range
Default
Notes
Enter the UTRAN Absolute Radio Freq Chan Number
10562 - 10838
None
This sets the bs_fdd_arfcn blind search neighbor attribute. This is not prompted for if the Enhanced 2G-3G feature is restricted.
When adding UTRAN neighbors, checks are made to ensure the maximum number of UTRAN BCCH and SACCH neighbors has not been reached, the maximum number of UTRAN BCCH and SACCH neighbors per FDD_ARFCN has not been reached and the maximum number of FDD-ARFCN per GSM cell has not been reached.
Related commands add_cell on page 3-22
copy_cell on page 3-179
del_cell on page 3-192
del_neighbor on page 3-197
disp_cell on page 3-241
disp_gsm_cells on page 3-314
disp_neighbor on page 3-343
modify_neighbor on page 3-447
68P02901W23-S
3-47 Nov 2009
add_nsvc
Chapter 3: Device/function related commands
add_nsvc ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The add_nsvc command enables the operator to map a Network Service-Virtual Connection Identifier (NSVCI) and Data Link Connection Identifier (DLCI) to a specific GBL. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator action)
Prerequisites
The GPRS feature must be unrestricted.
Format Syntax add_nsvc
Input parameters pcu_n
{27955A} pcu or pcu_0
The PCU at which the NSVCI or DLCI is to be mapped to the specific GBL.
ns_vci
0 - 65535
The virtual connection on a GBL Unique identifier of the NSVCI mapping and identifier of the object.
gbl_id
0 - 35
Object identifier of the GBL
dlci
16 - 991
Local identifier for a virtual connection on a GBL.
Prompts are then displayed as follows: Enter the Committed Information rate: Enter the Committed Burst Size: Enter the Burst Excess:
3-48
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Example
Example The following example adds NSVCI 10 to GBL 0 with a DLCI of 50 on PCU 0: add_nsvc pcu_0 10 0 50 Where:
is: pcu_0
PCU 0
10
NSVC
0
GBL ID
50
DLCI
System response Enter the Committed Information Rate:150
Enter the Committed Burst Size:300
Enter the Burst Excess:400
COMMAND ACCEPTED
References Related commands del_nsvc on page 3-202
68P02901W23-S
mod_nsvc on page 3-445
3-49 Nov 2009
add_rtf_path
Chapter 3: Device/function related commands
add_rtf_path ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The add_rtf_path command allows the addition of a redundant PATH device to an equipped RTF function in the CM database. The parameters that identify a particular PATH are location and Unique_PATH_identifier. Adding a redundant path that is shorter than the current path causes a switch to the shorter path. If an RTF path is being added to an RTF with multiplexed 16 k RSLs the system prompts for the identifier of the associated RSL. The system rejects attempts to modify the PATHs used by RTFs at sites that use dynamic allocation. RTFs automatically use the PATHs defined for these types of sites. RTFs do not use PATHs equipped by the operator for these types of sites. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator action)
Prerequisites
This command can only be executed at the BSC. If no redundant PATH is equipped, then first equip any necessary MSI before equipping the PATH.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax add_rtf_path
3-50
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Example
Input parameters location Indicates the number of the BTS where the RTF is located. The range of values is 0 to 140. 1st_RTF_identifier Specifies the first RTF identifier. The range of values is: 2nd_RTF_identifier Specifies the second RTF identifier. The range of values is: 0 to 11 for InCell. 0 or 1 for M-Cell. unique_PATH_identifier Specifies the unique PATH to a particular site. The range of values is 0 to 9.
Example This example adds a redundant RTF PATH to site 3, RTF identifiers 2 1, unique PATH identifier 1. add_rtf_path 3 2 1 1 Where:
is: 3
location
2
1st_RTF_identifier
1
2nd_RTF_identifier
1
unique_PATH_identifier
System response COMMAND ACCEPTED
References Related commands copy_path on page 3-187
del_rtf_path on page 3-204
disp_rtf_path on page 3-381
disp_traffic on page 3-394
68P02901W23-S
3-51 Nov 2009
alarm_mode
Chapter 3: Device/function related commands
alarm_mode ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The alarm_mode command registers or deregisters the MMI to receive device, non-reconfiguration type, and statistical alarm reports for the specified sites. If no mode is specified, this command displays whether alarms are enabled or disabled. If the location is specified as all from a BSC, alarms for all sites are affected (either displayed, enabled, or disabled). Security level
1
Supported by OMC-R GUI
No
Command type
A (no operator action)
Prerequisites
The GPRS must be unrestricted to assess a PCU site.
Format Syntax alarm_mode [,] []
Input parameters location Specifies the site location: 0 or bsc
BSC
0 - 140
BTS
{27955A} pcu or pcu_0
PCU
mode
3-52
on
alarm reporting activated
off
alarm reporting deactivated
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Examples Example 1 Specifies alarm mode as On for BSC 0: alarm_mode 0 on
System response SITE
MODE
-----
-----------------------
0
Alarm reporting enabled
Example 2 Specifies alarm mode as Off for PCU site 0: alarm_mode pcu_0 off
System response SITE
MODE
-----
------------------------
pcu_0
Alarm reporting disabled
68P02901W23-S
3-53 Nov 2009
assess
Chapter 3: Device/function related commands
assess ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The assess command displays different types of information, depending on whether a SITE or device is specified, as follows: SITE When a site is specified, information on the status of Functional Units (FUs) and which device types contribute to that status is reported. The information is presented in a concise format that indicates where problems are and what must be done. Only the FUs and device types which have non-CLEAR status are listed. Complete device IDs are not listed. The FU statuses are defined as: MAJOR = Loss of Capacity. MINOR = Loss of Redundancy. CRITICAL = Loss of Service. Device A device can be specified individually, with wild cards, or for all sites. When multiple devices and/or functions have gone OOS (Out Of Service) as part of separate reconfigurations, multiple reports are generated. If multiple reports are generated as part of a single assess command, one report is generated for each active reconfiguration that satisfies the request. For the purposes of this command, ‘active’ means any reconfiguration with: •
One or more alarms active against it.
•
One or more devices still OOS.
•
Both active alarms and OOS devices.
Only one report is displayed if wild cards are used and all devices that match the wild cards go OOS as part of the same reconfiguration. Functions are not displayed as an OOS device because there is no maintenance action to perform on a function. Once all devices are restored to an in-service state, the functions must be assigned to the appropriate devices and cease to affect the FUs. Device reports are displayed in the following format: Alarm Device: of
:
Cause:
Outcome:
Functional Unit: -- Status:
Current Status:
-- OOS Devices Affecting Functional Unit:
3-54
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
The Alarm Device is the primary alarm for the reconfiguration. The alarm is displayed even if it has been cleared already. An alarm and the alarm device are not displayed for a reconfiguration that does not have an active alarm yet has OOS devices. However, the message No Primary Alarm for this Reconfiguration is displayed. A Functional Unit (and its status) is displayed for each FU which is impacted by the reconfiguration and has a non-CLEAR status at the end of the reconfiguration. The line, OOS Devices Affecting Functional Unit, displays when devices are OOS and are still associated with this reconfiguration. For each device impacting the listed FU, the device ID and state are listed one per line. If the FU no longer has any OOS devices impacting it, the line, No devices remain OOS as a result of this configuration is displayed instead of the previous line.
NOTE This report does not list a config_tag or a time stamp. This information can be displayed with either the state or disp_act_alarm command.
Security level
1
Supported by OMC-R GUI
No
Command type
A (no operator action)
Prerequisites
The GPRS feature must be unrestricted to assess a PCU site.
Format Syntax assess [all] [ ] [*]
Input parameters location Specifies the site location: 0 or bsc
BSC
0 - 140
BTS
{27955A} pcu or pcu_0
PCU
all
All active sites
68P02901W23-S
3-55 Nov 2009
Examples
Chapter 3: Device/function related commands
dev/func name Specifies the device or function. dev/func id Specifies the ID for the device or function. The system accepts the wildcard character (*) for the device or function ID.
Examples Example 1 In the following example, BSC has been initialized. The operator wishes to see if there are any problems at the BSC: assess 0 Where:
is: 0
location
System response SITE / CELL
DEVICE/FUNCTION
SEVERITY
------------------------
---------------
--------------------------
SITE 0
MAJOR (Loss of Capacity) BSP
MAJOR (Loss of Capacity)
OML
MAJOR (Loss of Capacity)
CBUS
MINOR (Loss of Redundancy)
SITE 3
MAJOR (Loss of Capacity) RSL
CELL 001 01 1 2
MAJOR (Loss of Capacity) MINOR (Loss of Redundancy)
DRI
MINOR (Loss of Redundancy)
Example 2 In the following example, the operator is concerned about the OMLs contributing to the severity of MAJOR. In this particular scenario, both OMLs have been OOS since site initialization: assess 0 oml 0 Where:
3-56
is: 0
location
oml
device name
0
device ID
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response ASSESS REPORT BEGIN (242) Device(s) OOS due to action on this device Alarm Device: SITE 0 0 0 ENABLE of SITE: 0 0 0 Cause: INITIALIZATION Outcome: Alarm Functional Unit: SITE 0 -- Status: MAJOR
Current Status: MAJOR
-- OOS Devices Affecting Functional Unit: OML 0 0 0
DISABLED UNLOCKED
MMS Not In Service
OML 0 0 0
DISABLED UNLOCKED
MMS Not In Service
Functional Unit: SITE 3 -- Status: MINOR
Current Status: MAJOR
-- No devices remain OOS as a result of this configuration Functional Unit: CELL 001 01 1 2 -- Status: MAJOR
Current Status: MINOR
-- OOS Devices Affecting Functional Unit: DRI 1 4 0
DISABLED UNLOCKED
DRI Not Detected
ASSESS REPORT COMPLETE
Example 3 The following example shows an assess display for PCU site 0: assess pcu_0 Where:
is: pcu_0
location
System response SITE / CELL
DEVICE/FUNCTION
SEVERITY
-------------------------------------
---------------
---------
PCU 0
CRITICAL GBL
CRITICAL
GSL
MAJOR
DPROC
MAJOR
MSI
MAJOR
COMMAND ACCEPTED
68P02901W23-S
3-57 Nov 2009
cage_audit
Chapter 3: Device/function related commands
cage_audit ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The cage_audit command performs two different functions. The first function allows the execution of safe tests or all audits for all the devices within a specific cage. The second function permits the suspension or resumption of all audits at a specific site. There are only two possible System Responses to a cage_audit command: •
The display of results.
•
ERROR.
The ERROR response is due to a non-device related cause. An error description is also displayed. Devices listed within the CAGE can also generate messages specific to the device. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
NOTE This command does not work at an M-Cell site. Contact the OMC-R for help.
Format Syntax cage_audit cage_audit
3-58
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Input parameters location Specifies the audit location: 0 or bsc
BSC
0 - 140
BTS
{27955A} pcu or pcu_0
PCU
audit_type Specifies the type of audit: safe
initiates safe tests
All
initiates all audits
control Specifies the audit status: on
Resumes all site audits within a cage at a specific site.
off
Suspends all site audits within a cage at a specific site.
cage_number Specifies the cage number: 0 - 13
for a BSC
2 - 15
for a BTS
Examples Example 1 This example executes all audits for all devices for cage 0 at site 0. cage_audit 0 all 0 Where:
68P02901W23-S
is: 0
location
all
audit_type
0
cage_number
3-59 Nov 2009
Examples
Chapter 3: Device/function related commands
System response Device: KSW
Device id: 0 0 0
Year: 1994
Month: 11
Audit Type: SAFE Device: KSW
Hour: 0 Min: 26 Sec: 26 MSec: 495
Result: PASS
Device id: 0 0 0
Year: 1994
Month: 11
Audit Type: INT LPBK Device: MSI
Day: 12
Hour: 0 in: 26 Sec: 27 MSec: 860
Result: PASS
Device id: 3 0 0
Year: 1994
Month: 11
Audit Type: SAFE Device: MSI
Day: 12
Hour: 0 Min: 26 Sec: 28 MSec: 630
Result: PASS
Device id: 1 0 0
Year: 1994
Month: 11
Audit Type: SAFE Device: DRI
Day: 12
Day: 12
Hour: 0 Min: 26 Sec: 29 MSec: 665
Result: PASS
Device id: 0 1 0
Year: 1994
Month: 11
Audit Type: SAFE Device: GPROC Year: 1994
Day: 12
Hour: 0 Min: 26 Sec: 29 MSec: 665
Result: PASS
Device id: 1 0 0 Month: 11
Audit Type: SAFE
Day: 12
Hour: 0 Min: 26 Sec: 31 MSec: 595
Result: ERROR
ERROR: Audit not available for this device.
Example 2 The following example suspends audits for all devices in cage 9 at site 4: cage_audit 4 off 9 Where:
is: 4
location
off
control
9
cage_number
System response COMMAND ACCEPTED
3-60
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
References Related commands chg_audit_sched on page 3-76
device_audit on page 3-210
query_audits on page 3-472
site_audit on page 3-507
68P02901W23-S
3-61 Nov 2009
cell_name
Chapter 3: Device/function related commands
cell_name ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The cell_name command assigns a unique name to a Cell ID, renames a cell, or displays the name assigned to a Cell ID. The name can be a text string up to 31 alphanumeric characters in length, including dash characters used for separation. The system does not permit duplicate cell names to be entered. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
A security level of 2 is required to create or modify a cell name.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax cell_name [“”]
Input parameters gsm_cell_id The GSM cell ID of the cell for which the cell name is to be created, displayed, or modified. The format for the GSM cell ID depends on is:
3-62
•
The system used (PGSM, EGSM, DCS1800, PCS1900).
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
cell_name The name to be assigned to the Cell ID. The cell name must be entered inside double quotation marks. The cell name can be from one to 31 alphanumeric characters. The dash character can be used as a separator. The underscore character cannot be used as part of the name or as a separator. Double quotation marks cannot be used as part of a cell name. Cell names must not be equivalent to the following character strings in upper or lower case: •
all
•
no name defined
•
name not available
Entering two consecutive double quotation marks removes the current cell name. If no value is entered for this parameter, the current cell name displays.
Examples Example 1 In this example, the Cell ID 5 4 3 2 1 61986 34944 is assigned the cell name ‘london-west’. cell_name 5 4 3 2 1 61986 34944 “london-west” Where:
is: 5 4 3 2 1 61986 34944
cell_number
london-west
cell_name
System response COMMAND ACCEPTED:
Example 2 In this example, the cell name assigned to Cell ID 5 4 3 2 1 61986 34944 displays. The cell_name displays inside double quotes. cell_name 5 4 3 2 1 61986 34944 Where:
is: 5 4 3 2 1 61986 34944
68P02901W23-S
cell_number
3-63 Nov 2009
Examples
Chapter 3: Device/function related commands
System response GSM Cell [ 5 4 3 2 1 61986 (f222h) 34944 (8880h) ] = “london-west”
NOTE If there is no cell name, the system response is: No textual name exists for this cell
Example 3 In this example, the existing cell name ‘london-west’ is removed. cell_name 5 4 3 2 1 61986 34944 ” Where:
is: 5 4 3 2 1 61986 34944
cell_number
”
cell_name
System response COMMAND ACCEPTED
Example 4 In this example, the PCS1900 Cell ID 543 721 61986 34944 is assigned the name ‘london-west’. cell_name 543 721 61986 34944 “london-west” Where:
is: 543 721 61986 34944
cell_number
london-west
cell_name
System response COMMAND ACCEPTED
3-64
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
chg_acs_params
chg_acs_params ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_acs_params command specifies up to four codec modes to be used in the Active Codec Set (ACS), the initial codec mode, and the uplink and downlink adaptation threshold, and hysteresis values for Full Rate (FR), Half Rate (HR), or both. The term ‘Active Codec Set’ refers to the set of up to four Adaptive Multi-Rate (AMR) code modes and related thresholds, and hysteresis that can be used for any given voice call in the uplink and downlink directions. The operator configures the ACS on a per cell basis. There are two sets of thresholds and hysteresis per ACS; one for downlink codec mode adaptation and one for uplink codec mode adaptation. The threshold is used as the lower decision threshold for switching between the codec modes. The sum of the threshold and the hysteresis constitutes the upper threshold between the codec modes. There is a separate ACS for Full Rate and Half Rate. The term ‘Adaptive Multi-Rate codec’ refers to the speech and channel codec capable of operating at gross bit-rates of 11.4 kbits/s (Half-Rate) and at 22.8 kbits/s (Full Rate) over the air interface. Plus, the codec can operate at various combinations of speech and channel coding (codec mode) bit-rate for each channel mode. Security level
4
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
The AMR feature must be unrestricted. The site must be an AMR-capable BTS.
Dependencies
Either AMR Full-Rate or Half-Rate must be enabled in the cell for the AMR parameters to come into effect. Parameters can be set before or after the AMR is enabled in the cell. Thus performance is optimized for calls initiated in the cell.
68P02901W23-S
3-65 Nov 2009
Format
Chapter 3: Device/function related commands
Format Syntax chg_acs_params The system responds with a series of prompts for threshold and hysteresis values (see Table 3-20 and Table 3-21).
NOTE The sum of the values for threshold and hysteresis must be less than 63.
Input parameters mode This parameter specifies the rate where: 0 = Full Rate 1 = Half Rate 2 = Both Rates cell_number= This parameter is the GSM cell ID of the cell to be changed. The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900).
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
Only PCS1900 systems can use a three digit MNC. The codec mode values and associated rates are listed in Table 3-17:
Table 3-17
3-66
Codec Mode Values / Rates Codec Mode Value
Associated Rate
0
12.20 kbit/s
1
10.20 kbit/s
2
7.95 kbit/s
3
7.40 kbit/s
4
6.70 kbit/s
5
5.90 kbit/s
6
5.15 kbit/s
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
Full Rate attribute values for the chg_acs_params command are listed in Table 3-18, and the Half Rate attribute values are listed in Table 3-19.
NOTE The range values 0 - 63 and 0 - 15 in Table 3-18 and Table 3-19 are in steps of 0.5 dB.
Table 3-18
Full Rate attribute values for chg_acs_params command Attribute
Range
Default
Notes
amr_fr_acs
0, 1, 3, 4, 6
0, 1, 3, 6
Up to four AMR codec modes which can be used for any given voice call in the uplink or downlink direction.
amr_fr_initial_codec_mode
0, 1, 3, 4, 6
1
Codec mode used at the beginning of a call. If one mode is entered for the Full Rate ACS, then the Full Rate Initial Codec Mode defaults to this value (if valid).
amr_fr_uplink_threshold3 amr_fr_uplink_threshold2 amr_fr_uplink_threshold1
0 - 63 0 - 63 0 - 63
26 20 14
amr_fr_uplink_hysteresis3 amr_fr_uplink_hysteresis2 amr_fr_uplink_hysteresis1
0 - 15 0 - 15 0 - 15
1 1 1
The sum of the associated threshold and hysteresis is used as the upper decision threshold for switching the codec mode.
amr_fr_downlink_threshold3 amr_fr_downlink_threshold2 amr_fr_downlink_threshold1
0 - 63 0 - 63 0 - 63
30 24 19
Lower Full Rate downlink decision threshold for switching from one mode to another.
amr_fr_downlink_threshold3 amr_fr_downlink_threshold2 amr_fr_downlink_threshold1
0 - 15 0 - 15 0 - 15
1 1 1
The sum of the associated threshold and hysteresis is used as the upper decision threshold for switching the codec mode.
amr_fr_uplink_threshold3_hopping amr_fr_uplink_threshold2_hopping amr_fr_uplink_threshold1_hopping
0 - 63 0 - 63 0 - 63
26 20 14
Uplink switching thresholds applied to frequency hopping channels.
amr_fr_uplink_hysteresis3_hopping amr_fr_uplink_hysteresis2_hopping amr_fr_uplink_hysteresis1_hopping
0 - 15 0 - 15 0 - 15
1 1 1
Uplink hysteresis applied to frequency hopping channels.
amr_fr_downlink_threshold3_hopping amr_fr_downlink_threshold2_hopping amr_fr_downlink_threshold1_hopping
0 - 63 0 - 63 0 - 63
26 21 14
Downlink switching thresholds applied to frequency hopping channels.
amr_fr_downlink_hysteresis3_hopping amr_fr_downlink_hysteresis2_hopping amr_fr_downlink_hysteresis1_hopping
0 - 15 0 - 15 0 - 15
1 1 1
Downlink hysteresis applied to frequency hopping channels.
68P02901W23-S
Lower Full Rate uplink decision threshold for switching from one mode to another.
3-67 Nov 2009
Format
Chapter 3: Device/function related commands
Table 3-19
Half Rate attribute values for chg_acs_params command Attribute
Range
Default
Notes
amr_hr_acs
2, 3, 4, 5, 6
3, 5, 6
Up to four AMR codec modes which can be used for any given voice call in the uplink or downlink direction.
amr_hr_initial_codec_mode
2, 3, 4, 5, 6
5
Codec mode used at the beginning of a call. If one mode is entered for the Half Rate ACS, then the Half Rate Initial Codec Mode defaults to this value (if valid).
amr_hr_uplink_threshold3 amr_hr_uplink_threshold2 amr_hr_uplink_threshold1
0 - 63 0 - 63 0 - 63
28 22
amr_hr_uplink_hysteresis3 amr_hr_uplink_hysteresis2 amr_hr_uplink_hysteresis1
0 - 15 0 - 15 0 - 15
1 1
The sum of the associated threshold and hysteresis is used as the upper decision threshold for switching the codec mode.
amr_hr_downlink_threshold3 amr_hr_downlink_threshold2 amr_hr_downlink_threshold1
0 - 63 0 - 63 0 - 63
30 24
Lower Half Rate downlink decision threshold for switching from one mode to another.
amr_hr_downlink_threshold3 amr_hr_downlink_threshold2 amr_hr_downlink_threshold1
0 - 15 0 - 15 0 - 15
1 1
The sum of the associated threshold and hysteresis is used as the upper decision threshold for switching the codec mode.
amr_hr_uplink_threshold3_hopping amr_hr_uplink_threshold2_hopping amr_hr_uplink_threshold1_hopping
0 - 63 0 - 63 0 - 63
28 22
Uplink switching thresholds applied to frequency hopping channels.
amr_hr_uplink_hysteresis3_hopping amr_hr_uplink_hysteresis2_hopping amr_hr_uplink_hysteresis1_hopping
0 - 15 0 - 15 0 - 15
1 1
Uplink hysteresis applied to frequency hopping channels.
amr_hr_downlink_threshold3_hopping amr_hr_downlink_threshold2_hopping amr_hr_downlink_threshold1_hopping
0 - 63 0 - 63 0 - 63
30 23
Downlink switching thresholds applied to frequency hopping channels.
amr_hr_downlink_hysteresis3_hopping amr_hr_downlink_hysteresis2_hopping amr_hr_downlink_hysteresis1_hopping
0 - 15 0 - 15 0 - 15
1 1
Downlink hysteresis applied to frequency hopping channels.
Lower Half Rate uplink decision threshold for switching from one mode to another.
Full Rate prompts for the chg_acs_params command are listed in Table 3-20, and the Half Rate prompts are listed in Table 3-21.
3-68
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 3-20
Format
Full Rate prompts for the chg_acs_params command
Prompt
Required
Value Definition
Conditions
Enter AMR Full Rate active codec set:
Yes
Up to four codec mode values (codec rates) are entered in order of descending bit-rate (ascending field value 0 - 7, see Table 3-17).
Prompt displays if the AMR feature is unrestricted, the BTS type is AMR-capable, and the mode specified is 0 or 2.
Enter AMR Full Rate initial codec mode:
Yes
The value must be one of the rates included in the Active Codec Set.
Prompt displays if the ACS contains more than one codec mode.
Enter AMR Full Rate uplink adaptation thresholds:
Yes
Enter up to three uplink threshold values in order of descending C/I estimation.
Prompt displays if the ACS contains more than one codec mode. One uplink value for each adjacent pair of codec modes in ACS.
Enter AMR Full Rate uplink adaptation hysteresis:
Yes
Enter up to three uplink hysteresis values.
Prompt displays if the ACS contains more than one codec mode. One uplink value for each adjacent pair of codec modes in ACS.
Enter AMR Full Rate downlink adaptation thresholds:
Yes
Enter up to three downlink threshold values in order of descending C/I estimation.
Prompt displays if the ACS contains more than one codec mode. One downlink value for each adjacent pair of codec modes in ACS.
Enter AMR Full Rate downlink adaptation hysteresis:
Yes
Enter up to three downlink hysteresis values.
Prompt displays if the ACS contains more than one codec mode. One downlink value for each adjacent pair of codec modes in ACS.
Enter AMR Full Rate uplink adaptation thresholds for frequency hopping:
Yes
Enter up to three values.
Prompt displays if the ACS contains more than one codec mode. One value for each adjacent pair of codec modes in ACS.
Enter AMR Full Rate uplink adaptation hysteresis for frequency hopping:
Yes
Enter up to three values.
Prompt displays if the ACS contains more than one codec mode. One value for each adjacent pair of codec modes in ACS.
Enter AMR Full Rate downlink adaptation thresholds for frequency hopping:
Yes
Enter up to three values.
Prompt displays if the ACS contains more than one codec mode. One value for each adjacent pair of codec modes in ACS. Continued
68P02901W23-S
3-69 Nov 2009
Format
Chapter 3: Device/function related commands
Table 3-20
Full Rate prompts for the chg_acs_params command (Continued)
Prompt
Required
Enter AMR Full Rate downlink adaptation hysteresis for frequency hopping:
Yes
Table 3-21
Value Definition Enter up to three values.
Conditions Prompt displays if the ACS contains more than one codec mode. One value for each adjacent pair of codec modes in ACS.
Half Rate prompts for chg_acs_params command
Prompt
Required
Value Definition
Conditions
Enter AMR Half Rate active codec set:
Yes
Up to four codec mode values (codec rates) are entered in order of descending bit-rate (ascending field value 0 - 7, see Table 3-17)
Prompt displays if the AMR feature is unrestricted, the BTS type is AMR-capable, and the mode specified is 0 or 2.
Enter AMR Half Rate initial codec mode:
Yes
The value must be one of the rates included in the Active Codec Set.
Prompt displays if the ACS contains more than one codec mode.
Enter AMR Half Rate uplink adaptation thresholds:
Yes
Enter up to three uplink threshold values in order of descending C/I estimation.
Prompt displays if the ACS contains more than one codec mode. One uplink value for each adjacent pair of codec modes in ACS.
Enter AMR Half Rate uplink adaptation hysteresis:
Yes
Enter up to three uplink hysteresis values.
Prompt displays if the ACS contains more than one codec mode. One uplink value for each adjacent pair of codec modes in ACS.
Enter AMR Half Rate downlink adaptation thresholds:
Yes
Enter up to three downlink threshold values in order of descending C/I estimation.
Prompt displays if the ACS contains more than one codec mode. One downlink value for each adjacent pair of codec modes in ACS.
Enter AMR Half Rate downlink adaptation hysteresis:
Yes
Enter up to three downlink hysteresis values.
Prompt displays if the ACS contains more than one codec mode. One downlink value for each adjacent pair of codec modes in ACS.
Enter AMR Half Rate uplink adaptation thresholds for frequency hopping:
Yes
Enter up to three values.
Prompt displays if the ACS contains more than one codec mode. One value for each adjacent pair of codec modes in ACS. Continued
3-70
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 3-21
Example
Half Rate prompts for chg_acs_params command (Continued)
Prompt
Required
Enter AMR Half Rate uplink adaptation hysteresis for frequency hopping:
Yes
Enter up to three values.
Prompt displays if the ACS contains more than one codec mode. One value for each adjacent pair of codec modes in ACS.
Enter AMR Half Rate downlink adaptation thresholds for frequency hopping:
Yes
Enter up to three values.
Prompt displays if the ACS contains more than one codec mode. One value for each adjacent pair of codec modes in ACS.
Enter AMR Half Rate downlink adaptation hysteresis for frequency hopping:
Yes
Enter up to three values.
Prompt displays if the ACS contains more than one codec mode. One value for each adjacent pair of codec modes in ACS.
Value Definition
Conditions
Example This example sets four Full Rate codec modes in the active codec set for cell 2 9 6 0 1 1 1, where previously only one mode was configured. chg_acs_params 1 cell_number=2 9 6 0 1 1 1 Where:
is: 0
mode
4960111
cell ID
System response AMR Half Rate active codec set:2 3 4 5 AMR Half Rate initial codec mode:1 AMR Half Rate uplink adaptation thresholds:40 30 20 AMR Half Rate uplink adaptation hysteresis:5 8 8 AMR Half Rate downlink adaptation thresholds:41 31 21 AMR Half Rate downlink adaptation hysteresis:4 4 4 AMR Half Rate uplink adaptation thresholds for frequency hopping:38 28 21 AMR Half Rate uplink adaptation hysteresis for frequency hopping:1 1 1 AMR Half Rate downlink adaptation thresholds for frequency hopping:40 30 20 AMR Half Rate downlink adaptation hysteresis for frequency hopping:1 1 1 Enter AMR Half Rate active codec set: 4 COMMAND ACCEPTED
68P02901W23-S
3-71 Nov 2009
References
Chapter 3: Device/function related commands
References Related commands disp_acs on page 3-223.
3-72
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
chg_a5_alg_pr
chg_a5_alg_pr ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_a5_alg_pr command specifies the A5 encryption algorithms in the order in which the BSS uses them. Security level
4
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
The encryption feature must be unrestricted. To include an algorithm in the priority list, it must be enabled with the associated database parameter (option_alg_a5_1 through option_alg_a5_7).
Operator actions
The encryption feature must be activated first.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax chg_a5_alg_pr [] [] [] [] [] [] []
68P02901W23-S
3-73 Nov 2009
Format
Chapter 3: Device/function related commands
Input parameters The following values specify the GSM encryption algorithm: Value
GSM Algorithm
0
No encryption; any algorithms listed after 0 are ignored.
1
A5/1
2
A5/2
3
A5/3
4
A5/4
5
A5/5
6
A5/6
7
A5/7
first_alg first algorithm choice (0 - 7) second_alg second algorithm choice (0 - 7)
NOTE The system uses only the first and second algorithm choices. Values entered for the remaining parameters are ignored.
third_alg third algorithm choice (0 - 7) fourth_alg fourth algorithm choice (0 - 7) fifth_alg fifth algorithm choice (0 - 7) sixth_alg sixth algorithm choice (0 - 7) seventh_alg seventh algorithm choice (0 - 7) eighth_alg eighth algorithm choice (0 - 7)
3-74
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Examples Example 1 In this example, the algorithms ordered as follows: A5/1, A5/2: chg_a5_alg_pr 1 2 Where:
is: 1
A5/1 Algorithm
2
A5/2 Algorithm
System response COMMAND ACCEPTED
Example 2 In this example, no encryption is used: chg_a5_alg_pr 0 Where:
is: 0
no encryption
System response COMMAND ACCEPTED
References Related commands disp_a5_alg_pr on page 3-221
68P02901W23-S
chg_element on page 3-106
3-75 Nov 2009
chg_audit_sched
Chapter 3: Device/function related commands
chg_audit_sched ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_audit_sched command schedules audits of selected devices at specified site based on device type and audit type. {25002} The chg_audit_sched is modified to support the swap_test type audit on the TDM device at site 0 (BSC or RXCDR). Audits can run in parallel or in series. •
Audits of different devices run in parallel, that is, the system can audit different devices at the same time. For example, audits of the DRI and GCLK run in parallel.
•
Audits of similar devices run sequentially that is, the audit of one device must end before the second device audit can begin. For example, the system audits all GPROCs at a site sequentially.
Use the device_audit command to turn off the audits. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
An operator at the OMC-R must rlogin to a site before an audit can be scheduled. Only one audit can be run at a time. If a log exists from a previous audit, it is overwritten with the log created by the current audit.
NOTE Enter this command only at the BSC or a specified PCU at a GPRS site. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax {25002} chg_audit_sched
3-76
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
Input parameters location Specifies the audit location: 0 or bsc
BSC
1 - 140
BTS
{27955A} pcu or pcu_0
PCU
device_name Name that uniquely identifies the device. The following devices can be audited at InCell sites using this command: BSP
BTP
DHP
DRI
GCLK
GPROC
KSW
MSI
SITE
TDM
The following devices can be audited at M-Cell sites using this command: BTP
DRI
MSI
SITE
The following devices can be audited at a PCU using this command: DPROC
MSI
PSP
audit_type Type of audit
Value
Tests
Available Locations
all
0
safe
1
Safe tests
KSW
int_lpbk
2
Internal loopback
RXCDR at a remote transcoding BSC
self_test
3
All
BSC and BTS only
swap_test
4
BSC, BTS, and PCU
Expanded cage
start_time_hour Start time hour (00 to 23) start_time_min Start time minutes (00 to 59) end_time_hour End time hour (00 to 23) end_time_min End time minutes (00 to 59) interval_hour
68P02901W23-S
3-77 Nov 2009
Format
Chapter 3: Device/function related commands
The interval hour (00 to 23) interval_min The interval minutes (00 to 59)
Scheduling types There are three scheduling types: Continuous Scheduling
The system schedules continuous audits if: •
The start_time and end_time both have a value of 00:00.
•
The interval time is 0.
•
If the end_time is greater than the start_time, the system schedules the range audits.
•
The interval time is 0.
Range Scheduling
Once-Per-Day Scheduling
The system schedules range audits if: •
The start_time equals the end_time.
•
The interval time is 00:00.
Device scheduling defaults Table 3-22 lists the device scheduling defaults.
Table 3-22
Device scheduling defaults
Device
Default schedule
KSW safe test audit
continuously every hour
KSW internal loopback audit
from 2:00 am to 4:00 am every 15 minutes
GCLK safe test audit
continuously every hour
GPROC safe test audit DHP safe test audit TDM safe test audit
continuously every 10 minutes once a day at 1:00 am
BSP safe test audit BTP safe test audit
continuously every 10 minutes
MSI safe test audit
continuously every 1 minute
DRI safe test audit
continuously every 30 minutes
SITE safe test audit AXCDR safe test audit
3-78
continuously every 10 minutes
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
Query Audit information The following command string format can be used to display an audit scheduled for devices: query_audits Refer to the description of the query_audits parameter. Alternatively multiple disp_element commands can be used as listed in the following section.
Display information The following command string format can be used to display the audit_type scheduled for a device: disp_element sap_audit_type, Refer to the description of the sap_audit_type parameter. The following command string format displays the device_type scheduled for a device: disp_element sap_device_type, Refer to the description of the sap_device_type parameter. The following command string format displays the start_time_hour and start_time_min scheduled for a device: disp_element sap_start_time, Refer to the description of the sap_start_time. The following command string format can be used to display the end_time_hour and end_time_min scheduled for a device: disp_element sap_end_time, Refer to the description of the sap_end_time parameter. The following command string format displays the interval_hour and interval_min scheduled for a device: disp_element sap_interval, Refer to the description of the sap_interval parameter.
68P02901W23-S
3-79 Nov 2009
Examples
Chapter 3: Device/function related commands
Examples Example 1 In this example of range scheduling, the audit schedule is changed so that the DRI is audited for safe tests every 15 minutes from 9:30 am until 10:30 pm: chg_audit_sched bsc dri safe 9 30 22 30 0 15 Where:
is: bsc
location
dri
device_name
safe
audit_type
9 30
start_time
22 30
end_time
0 15
interval
System response COMMAND ACCEPTED
Example 2 In this example of GPRS range scheduling, the audit schedule is changed so that the PICP MSI 0 is audited for safe tests every 45 minutes from 9 am until 5:30 pm: chg_audit_sched pcu_0 msi safe 9 0 17 30 0 45 Where:
is: pcu_0
location
msi
device_name
safe
audit_type
9 00
start_time
17 30
end_time
0 45
interval
System response COMMAND ACCEPTED
3-80
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 3 {26740} In this example, the audit is scheduled for the PSI device from 9:30 am to 10:30 pm with an interval of 15 minutes. chg_audit_sched bsc psi safe 9 30 22 30 0 15 Where:
is: bsc
location
psi
device_name
safe
audit_type
9 30
start_time
22 30
end_time
0 15
interval
System response COMMAND ACCEPTED
Example 4 {25002} In this example, the audit is scheduled for the tdm device at 3:00 am daily. chg_audit_sched 0 tdm swap_test 3 0 3 0 0 0 Where:
is: 0
location
tdm
device_name
swap_test
audit_type
30
start_time
30
end_time
00
interval
System Response COMMAND ACCEPTED
68P02901W23-S
3-81 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 5 {25002} This example reschedules safe audit execution for DRI devices at location 1. The audit starts at 09:30 and ends at 22:30 and runs every 15 minutes. chg_audit_sched 1 DRI safe 9 30 22 30 0 15 Where:
is: 1
location
DRI
device_name
safe
audit_type
9 30
start_time
22 30
end_time
0 15
interval
System response COMMAND ACCEPTED
Example 6 {25002} This example causes the swap test to occur at 2:50 am every day. chg_audit_sched 0 tdm swap_test 2 50 5 0 0 0 Where:
is: 0
location
tdm
device_name
swap_test
audit_type
2 50
start_time
50
end_time
00
interval
System response COMMAND ACCEPTED
3-82
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
References Related commands cage_audit on page 3-58
device_audit on page 3-210
query_audits on page 3-472
site_audit on page 3-507
68P02901W23-S
3-83 Nov 2009
chg_cell_element
Chapter 3: Device/function related commands
chg_cell_element ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_cell_element command changes the value of cell-related parameters. This command supports only non-statistical cell elements. Prompts are presented for dependent cell parameters where necessary. Security level
4
Supported by OMC-R GUI
Yes.
Command type
Dependent upon the database parameter being changed.
Prerequisites
None
Operator actions
Respond to the dependent parameter prompts associated with the cell element being modified.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax chg_cell_element [] [,] chg_cell_element [,] all
NOTE When an attempt is made to change cell elements ccch_conf, gprs_enabled, gprs_ts_config_alg, max_gprs_ts_per_carrier, primary_pcu, res_gprs_pdchs, res_ts_less_one_carrier, switch_gprs_pdchs, or sw_ts_less_one_carrier, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that sufficient GDS or PMC resource is not available.
3-84
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
Input parameters location The location can also be entered as all to change the value of the specified element for all available cells in the system. element The cell parameter to be changed
NOTE The all option does not work for the coincident_mb parameter.
index The index of the element being changed, if any. value The value being assigned to the element. cell_desc_opt The GSM cell ID of the affected cell. cell_number=. can precede the GSM cell ID (optional). The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900).
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
Only PCS1900 systems can use a three digit MNC. The cell_desc can also be a cell name created using the cell_name command. When the cell name is entered, it must be placed inside double quotation marks. cell_name= can precede the cell name (optional).
NOTE This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. With some parameters, all can be entered. If this command is used, or all must also be used for the site. See the individual parameter descriptions.
68P02901W23-S
3-85 Nov 2009
Examples
Chapter 3: Device/function related commands
Examples Example 1 In this example, the hop_qual_enabled parameter is changed to 1 for a cell with GSM Half Rate enabled: chg_cell_element hop_qual_enabled 0 cell number =0 0 1 0 1 98 75 Where:
is: hop_qual_enabled
cell element being changed.
1
new element value.
cell=0 0 1 0 1 98 75
cell description.
System response Enter RSS handover threshold l_rxqual_dl_h_hopping: 250 Enter RSS handover threshold l_rxqual_ul_h_hopping: 250 Enter RSS handover threshold l_rxqual_dl_p_hopping: 250 Enter RSS handover threshold l_rxqual_ul_p_hopping: 250 Enter RSS handover threshold l_rxqual_ul_h_hopping_hr: 250 Enter RSS handover threshold l_rxqual_ul_p_hopping_hr: 250 Enter RSS handover threshold l_rxqual_dl_h_hopping_hr: 200 Enter RSS handover threshold l_rxqual_dl_p_hopping_hr: 200 COMMAND ACCEPTED
NOTE The following AMR Full Rate HDPC parameters are only prompted for if AMR is unrestricted.
Enter RSS handover threshold l_rxqual_ul_h_hopping_amr_fr: Enter RSS handover threshold l_rxqual_ul_p_hopping_amr_fr: Enter RSS handover threshold l_rxqual_dl_h_hopping_amr_fr: Enter RSS handover threshold l_rxqual_dl_p_hopping_amr_fr:
3-86
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 2 This example turns on IMRM band_preference for a cell using the numeric value 16, and set all weighting parameters to 0. chg_cell_element band_preference 16 cell number=0 0 1 0 1 1 12 Where:
is: band_prefernce
element being changed.
16
new element value.
cell=0 0 1 0 1 1 12
cell number.
System response Enter the weighting for PGSM: 0 Enter the weighting for EGSM: 0 Enter the weighting for DCS1800:
0
Enter the weighting for UMTS: 0 COMMAND ACCEPTED: WARNING: All IMRM band weights set to unsupported. shall apply internal defaults in the IMRM band selection algorithm
The BSS
Example 3 {26881} This example changes the value of the database element ext_utbf_nodata to 1 for cell 0 0 1 0 1 1 4. chg_cell_element ext_utbf_nodata 1 cell 0 0 1 0 1 1 4 Where:
is: ext_utbf_nodata
cell element being changed.
1
new element value.
0010114
cell number.
System response COMMAND ACCEPTED
68P02901W23-S
3-87 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 4 {31565} This example enables the functionality of AGCH flow control, any one of the triggers associated with IA and IAR can trigger AGCH overload. chg_cell_element _cell_data,20 1 cell_number=5 4 3 2 1 61986 34944 Where:
is: _cell_data,20
element being changed.
1
new element value.
5 4 3 2 1 61986 34944
cell number.
System Response COMMAND ACCEPTED
Example 5 {34164} This example modifies the value of _cell_data,21 from 0 to 1 to enable the 5 minute statistics uploading for cell 4 6 0 0 0 23 1101 under site 11. chg_cell_element _cell_data,21 1 cell=4 6 0 0 0 23 1101 Where:
is: _cell_data,21
element being changed
1
new element value
4 6 0 0 0 23 1101
cell number
System Response COMMAND ACCEPTED
Example 6 {23311A} This example attempts to disable the Extended Range Cell for GSM (ext_range_cell = 0) when ext_pdchs is set to non-zero for any RTF in the cell. chg_cell_ele ext_range_cell 0 cell 0 0 1 0 1 1 18 Where:
3-88
is: ext_range_cell
element being changed
0
new element value
0 0 1 0 1 1 18
cell number
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System Response COMMAND REJECTED: Value of ext_pdchs shall be 0 when ext_range_cell is disabled for the cell
Example 7 {23311A} This example attempts to enable baseband hopping (hopping_support = 2) when ext_pdchs in any RTF of the cell > 0. chg_cell_ele hopping_support 2 cell 0 0 1 0 1 1 18 Where:
is: hopping_support
element being changed
2
new element value
0 0 1 0 1 1 18
cell number
System Response COMMAND REJECTED: Value of ext_pdchs shall be 0 when Baseband hopping is enabled for the cell
68P02901W23-S
3-89 Nov 2009
chg_cell_id
Chapter 3: Device/function related commands
chg_cell_id ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_cell_id command changes the GSM cell ID of a specified cell. The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900)
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
Only PCS1900 systems can use a three digit MNC. The format to enter PGSM, EGSM, or DCS1800 Cell ID is: a b c d e f g The format to enter a PCS1900 Cell ID is: abc zde f g Where:
is: a
the first digit of the MCC (Mobile Country Code).
b
the second digit of the MCC.
c
the third digit of the MCC.
z
the first digit of the MNC (Mobile Network Code) for PCS1900 systems. This digit only applies to PCS1900 systems. EGSM, PGSM, and DCS1800 systems still use the two digit MNC, beginning with d, shown in the next row.
d
either:
e
3-90
•
the second digit of the PCS1900 MNC, or
•
the first digit of the PGSM, EGSM, or DCS1800 MNC.
either: •
the third digit of the MNC, or
•
the third digit of the PCS1900 MNC, or
•
the second digit of the PGSM, EGSM or DCS1800 MNC, or Only PCS1900 systems use a three digit MNC.
f
the LAC (Local Area Code).
g
the CI (Cell Identity).
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
When the GSM cell ID is changed using this command, it is not propagated throughout the CM database. A warning message is presented when this command is successfully entered. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax chg_cell_id
Input parameters old_cell_desc Original Cell ID of the cell. The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900)
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled. Only PCS1900 systems can use a three digit MNC.
The old_cell_desc can also be a cell name created using the cell_name command. When the cell name is entered, it must be placed inside double quotation marks. new_cell_desc New GSM cell ID of the cell.
68P02901W23-S
3-91 Nov 2009
Examples
Chapter 3: Device/function related commands
Examples Example 1 In this example, the GSM cell ID is changed: chg_cell_id 5 4 3 2 1 61986 34944 5 4 3 2 1 61985 37982 Where:
is: 5 4 3 2 1 61986 34944
old_cell_desc
5 4 3 2 1 61985 37982
new_cell_desc
System response WARNING: Verify OML state to ensure change propagated to all neighbors. COMMAND ACCEPTED
Example 2 In this example, the affected cell is identified using the cell_name ‘london-north’: chg_cell_id “london-north” 5 4 3 2 1 61985 37982 Where:
is: london-north
old_cell_desc (using cell name)
5 4 3 2 1 61985 37982
new_cell_desc
System response WARNING: Verify OML state to ensure change propagated to all neighbors. COMMAND ACCEPTED
Example 3 In this example, the GSM cell ID is changed for a PCS1900 cell: chg_cell_id 543 021 61986 34944 543 021 61985 37982 Where:
3-92
is: 543 021 61986 34944
old_cell_desc
543 021 61985 37982
new_cell_desc
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
System response WARNING: Verify OML state to ensure change propagated to all neighbors. COMMAND ACCEPTED
References Related commands add_cell on page 3-22
cell_name on page 3-62
del_cell on page 3-192
disp_cell on page 3-241
68P02901W23-S
copy_cell on page 3-179
3-93 Nov 2009
chg_cmd_level
Chapter 3: Device/function related commands
chg_cmd_level ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{27508}
Description The chg_cmd_level command modifies the current level of MMI command to a certain security level. Security level
4
Supported by OMC GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
Format Syntax chg_cmd_level
Example Example 1 This example modifies the level of disp_equipment to 2. chg_cmd_level disp_equipment 2 Where:
is: disp_equipment
command
2
level
System response COMMAND ACCEPTED
3-94
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
chg_csfp
chg_csfp ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_csfp command changes the CSFP algorithm or flow control values. The CSFP algorithm selects the CSFP algorithm method used when configuring CSFPs using the configure_csfp command or through the OMC-R. The flow_control selects the CSFP flow control value that controls the amount of RSL link utilization that a CSFP download from BSC to BTS can use. A value of 100 does not mean that the link is 100% utilized during the download. Only the CSFP downloads can proceed at the maximum throughput rate. Security level
4
Supported by OMC GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax chg_csfp
68P02901W23-S
3-95 Nov 2009
Examples
Chapter 3: Device/function related commands
Input parameters element Two selections are available: algorithm
Selects the CSFP algorithm method. The location values that can be entered for this element are 0 (or bsc) to 140.
flow_control
Selects the CSFP flow control value. The location values that can be entered for this element are 1 - 140.
value Either an algorithm or a flow control value can be entered but not both. The value that can be used is dependent upon the selected element: algorithm
flow_control
none
(4)
No CSFP device is to be configured at this site
stby
(2)
Select only standby BSP/BTP GPROCs
pool
(3)
Select only pool GPROCs
any
(1)
Select POOL GPROCs first followed by STBY GPROCs. Default value for this algorithm.
Selectable in a range from 10 to 100 in steps of 10. The default value is 10%.
location Specifies the element location. 0 or bsc
BSC
1 - 140
BTS
pcu
PCU
Examples Example 1 This example shows the inputs required to update the CSFP algorithm at the BSC to be only pool GPROCs. chg_csfp algorithm pool bsc Where:
3-96
is: algorithm
element
pool
Only pool GPROCs
bsc
location
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
System response COMMAND ACCEPTED
Example 2 This example shows the inputs required to update the CSFP flow control at site 3 to be 10%. chg_csfp flow_control 10 3 Where:
is: flow_control
element
10
flow control percentage
3
location
System response COMMAND ACCEPTED
Example 3 {25424} This example updates the csfp flow control value of PCU. chg_csfp flow_control 40 pcu Where:
is: flow_control
element
40
flow control percentage
pcu
location
System response COMMAND ACCEPTED
References Related command disp_csfp on page 3-263
68P02901W23-S
3-97 Nov 2009
chg_dte
Chapter 3: Device/function related commands
chg_dte ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_dte command assigns the DTE addresses to allow connections between the BSC and the OMC-R or CBC. The mapping of DTE addresses used and the default timeslots to contact the OMC while the network is in ROM are shown in Table 3-23 for the RXCDR and in Table 3-24 for the BSC.
Table 3-23
RXCDR default DTE addresses
Cage
MSI slot
MMS
Default timeslot
RXCDR DTE address
0
10
0
1
0
0
10
1
1
1
0
8
0
1
2
1
10
0
1
3
Table 3-24
BSC default DTE addresses
Cage
MSI slot
MMS
Default timeslot
RXCDR DTE address
0
16
0
1
0
0
16
1
1
1
0
14
0
1
2
1
16
0
1
3
Security level
3
Supported by OMC-R GUI
Yes
Command type
B (Operator actions required)
Prerequisites
The OML link affected by this command must be reset for the changes to take effect.
Operator actions
Reset the OML after changes have been entered with this command.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
3-98
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
Format Syntax chg_dte [] [] . []
.
.
Input parameters link Specifies the link location: bsc
The communication link between the BSC and the OMC-R.
omcr
OMC-R
cbc
CBC
bcs_cbc
The communication link between the BSC and CBC.
link_num The link location type determines the range of values: 0-3
bsc
0-7
omcr
0
bsc_cbc or cbc. If the address_length is 0, a link_num is required for cbc and bsc_cbc.
address_length The number of valid address bytes that are added to the list. The range of values is 0 - 14. address_byte The value of a particular address byte. The range of values is 0 - 9. The number of address bytes entered must equal the number entered for the address_length parameter. An address_byte value is not required when the address_length is zero.
68P02901W23-S
3-99 Nov 2009
Examples
Chapter 3: Device/function related commands
Examples Example 1 In this example, the DTE address of the third BSC is changed to 12345: chg_dte bsc 3 5 1 2 3 4 5 Where:
is: bsc
location
3
link_num
5
address_length
12345
address_byte (5 bytes)
System response BSS DTE addresses: Address #0:
23466811570001
Address #1:
41224643654225
Address #2:
31777619565738
Address #3:
12345
OMCR DTE addresses: Address #0:
23466823020041
Address #1:
24885902667864
Address #2:
38959620015151
Address #3:
122876465567
Address #4:
2301
Address #5:
6811570001
Address #6: Zero length address Address #7:
Zero length address
COMMAND ACCEPTED
3-100
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
Example 2 In this example, a zero length DTE address is created: chg_dte omcr 2 0 Where:
is: omcr
location
2
link_num
0
address_length
System response BSS DTE addresses: Address #0:
23466811570001
Address #1:
41224643654225
Address #2:
31777619565738
Address #3:
12345
OMCR DTE addresses: Address #0:
23466823020041
Address #1:
24885902667864
Address #2:
Zero length address
Address #3:
122876465567
Address #4:
2301
Address #5:
6811570001
Address #5:
6811570001
Address #6: Zero length address Address #7:
Zero length address
COMMAND ACCEPTED
References Related command disp_dte on page 3-269.
68P02901W23-S
3-101 Nov 2009
chg_eas_alarm
Chapter 3: Device/function related commands
chg_eas_alarm ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_eas_alarm command initializes and modifies the EAS (External Alarm System) alarm table. The EAS alarm table contains 34 indexed pairs. Each pair includes a severity level and up to 24 text characters for each BSS. Each pair corresponds to the output of an equipped EAS/PIX module. This command permits individual EAS alarms to be reported as text strings. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
The EAS device must be equipped before a severity level and text characters can be assigned.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax chg_eas_alarm “”
3-102
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Example
Input parameters alarm_table_index Specifies the index number assigned to a user-defined alarm text string in the EAS Alarm Table on the following page. The range of values is 0 - 33. alarm_severity_level Specifies the alarm level for a specific alarm string. Valid values are: 0
investigate
1
critical
2
major
3
minor
4
warning
new_alarm_string Assigns the alarm text string that corresponds to an alarm_table_index value in the EAS Alarm Table. The alarm string must be entered inside double quotation marks. The alarm text string can be a maximum of 24 characters, including spaces.
Example In this example, an alarm string of door open is assigned to the first index (1) of the alarm string table. This text string contains nine characters; the alarm is classified minor (3); and the string signifies that a cabinet door is open: chg_eas_alarm 1 3 “cabinet door open” Where:
is: 1
alarm_table_index
3
alarm_severity_level
cabinet_door_open
new_alarm_string
System response COMMAND ACCEPTED
68P02901W23-S
3-103 Nov 2009
References
Chapter 3: Device/function related commands
References Related information Table 3-25 lists the EAS default alarm strings.
Table 3-25
EAS default alarm strings alarm_table_index
Default alarm string
0
Burglar
1
Door Open
2
Fire
3
High Temperature
4
Low Temperature
5
High Humidity
6
Low Humidity
7
Tower Beacon Outage
8
Surge Arrester Failure
9
Microwave Trans. Failure
10
AC Power Failure
11
Generator Running
12
Generator Failed
13
PSU Rectifier
14
PSU Battery
15
PSU Fuse
16
Personnel on Site
17
General Alarm 1
18
General Alarm 2
19
General Alarm 3
20
PCU Over Temperature
21
PCU Customer Defined 1
22
PCU Door Open
23
PCU DC Fail
24
PCU Circuit Breaker
25
PCU AC Fail
26
PCU Comms Equipment Continued
3-104
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 3-25
References
EAS default alarm strings (Continued) alarm_table_index
Default alarm string
27
TDU Over Temperature
28
TDU Door Open
29
TDU Circuit Breaker
30
TDU Battery
31
TDU Customer Defined 1
32
TDU Customer Defined 2
33
TDU Customer Defined 3
Related commands chg_element on page 3-106
68P02901W23-S
disp_element on page 3-272
3-105 Nov 2009
chg_element
Chapter 3: Device/function related commands
chg_element ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_element command modifies database parameters in the CM database. Security level
4
Supported by OMC-R GUI
Yes
Command type
Dependent on the database parameter being changed.
Prerequisites
None
Operator actions
Respond to the dependent parameter prompts associated with the cell element being modified.
NOTE •
Only the chg_ele phase_lock_gclk parameter is moved to security level 3.
•
Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax chg_element [,][,] [] chg_element [,][,] all chg_element [,][,] all
NOTE When an attempt is made to change cell elements ccch_conf, gprs_enabled, gprs_ts_config_alg, max_gprs_ts_per_carrier, primary_pcu, res_gprs_pdchs, res_ts_less_one_carrier, sw_ts_less_one_carrier, or switch_gprs_pdchs, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that enough GDS or PMC resource is not available.
3-106
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
Input parameters element_name String identifying the database parameter in the CM database. index1 Some database parameters require an index. They are highlighted with an asterisk in the table in the Related Information section. A comma is required before the index number. index2 Database parameters requiring a second index are highlighted in the table shown in the Related Information section. A comma is required before the index number. index2 is used only with statistical database parameter names normal and weighted distribution statistical database parameter names require the use of index2. value New value for the element_name. location Specifies the site location: 0 or bsc
BSC
1 - 140
BTS
{27955A} pcu or pcu_0
PCU
all
Specifies all sites. Restrictions on the use of all locations are: •
Allowed outside SYSGEN mode only for type A elements.
•
Not allowed outside SYSGEN mode for type B elements.
•
Allowed for BY_CELL and BY_SITE elements only.
cell_desc GSM cell ID of the cell to be changed, preceded by cell_number= The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900).
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled. Only PCS1900 systems can use a three digit MNC.
The name of the cell created using the cell_name command can be entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks, and cell_name= must precede it.
NOTE This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. 68P02901W23-S
3-107 Nov 2009
Examples
Chapter 3: Device/function related commands
The value all is also a valid input for the cell_desc, which changes element_name to value for all cells at the specified location. Restrictions on the use of all cells are: •
Not allowed for elements that cause the site to reset.
•
Not allowed outside SYSGEN mode.
•
Allowed for BY_CELL and BY_SITE elements only.
•
Sites that are not equipped are not affected.
Examples The following examples only demonstrate how specific parameters are changed using the chg_element command. The examples shown can be part of a larger procedure. Refer to the appropriate documentation for detailed explanations of these procedures.
Example 1 In this example, the bsic value is changed to 1 for site number 1, cell_number=5 4 3 2 1 61986 34944: chg_element bsic 1 1 cell_number=5 4 3 2 1 61986 34944 Where:
is: bsic
element name
1
value
1
location
5 4 3 2 1 61986 34944
cell description
System response WARNING: Changing this element will reset all DRIs associated with this cell and will not be propagated through out the neighbor list Are you sure (y=yes,n=no)?
y
COMMAND ACCEPTED Selecting y or Y causes the system to make the change and reset. Selecting n or N causes the system to abandon the command without changing the parameter.
3-108
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 2 In this example, the database parameter transcoder_location is changed to a value of 1 for site number 0: chg_element transcoder_location 1 0 Where:
is: transcoder_location
element name
1
value
0
location
System response COMMAND ACCEPTED
NOTE Example 2 works only at site 0 in SYSGEN ON mode.
Example 3 In this example, the severity of EAS alarm 6 at location 0 is changed to level 2: chg_element eas_severity,6 2 0 Where:
is: eas_severity
element name
6
index
2
value
0
location
System response COMMAND ACCEPTED
68P02901W23-S
3-109 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 4 In this example, the affected cell is identified using the cell_name ‘london-north’: chg_element bsic 1 1 cell name= “london-north” Where:
is: bsic
element name
1
value
1
location
london-north
cell name
System response WARNING: Changing this element will reset all DRIs associated with this cell and will not be propagated through out the neighbor list Are you sure (y=yes,n=no)?
y
COMMAND ACCEPTED Selecting y or Y causes the system to make the change and reset. Selecting n or N causes the system to abandon the command without changing the parameter.
Example 5 In this example, the base station identity code (bsic) value is changed to 1 for PCS 1900 site number 0, cell_desc=543 721 61986 34944: chg_element bsic 1 1 cell number= 543 721 61986 34944 Where:
is: bsic
element name
1
value
1
location
543 721 61986 34944
cell description
System response WARNING: Changing this element will reset all DRIs associated with this cell and will not be propagated through out the neighbor list Are you sure (y=yes,n=no)?
y
COMMAND ACCEPTED Selecting y or Y causes the system to make the change and reset. Selecting n or N causes the system to abandon the command without changing the parameter.
3-110
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 6 This example attempts to change primary_pcu from 1 to 0 when PCU 0 does not have enough PMC resources for the Cell. chg_element primary_pcu 0 1 cell number= 0 0 1 0 1 1 1 Where:
is: primary_pcu
element name
0
value
1
location
0010111
cell description
System response WARNING: GPRS traffic may be disrupted while GPRS timeslots are being reconfigured Are you sure (y=yes,n=no)?
y
COMMAND ACCEPTED WARNING: Insufficient PMC resources available for all PDTCHs on the PCU.
Example 7 In this example, the value of improve_ts_enabled is changed to 0 when the improved timeslot sharing feature is unrestricted. chg_element improve_ts_enabled 0 bsc Where:
is: improve_ts_enabled
element name
0
value
bsc
location
System Response WARNING: B-U DD CTU2 DRIs must be cycled to deactivate ITS at specific sites or reset BTS site. COMMAND ACCEPTED
68P02901W23-S
3-111 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 8 {28337} In this example, the value of the database element ss7_hsp_12_t1 is modified to 255000 when the increased network capacity feature is unrestricted. chg_element ss7_hsp_12_t1 255000 0 Where:
is: ss7_hsp_12_t1
element name
255000
value
0
location
System response COMMAND ACCEPTED
Example 9 {28000} This example enables the rolling blackout mechanism on PCU. The PRP throughput increase feature is deactivated. chg_element prp_fanout_mode 1 pcu Where:
is: prp_fanout_mode
element name
1
value
pcu
location
System response WARNING: Changing prp_fanout_mode will cycle device PCU. Are you sure (y=yes,n=no)?
3-112
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 10 {27703A} This example modifies the value of streaming_enabled to 1 to enable support of streaming when the QoS phase 2 feature is unrestricted. chg_element streaming_enabled 1 0 Where:
is: streaming_enabled
element name
1
value
0
location
System response COMMAND ACCEPTED
Example 11 {31400} In this example, the value of td_enabled is changed to 0, when RDB 4225 Inter-RAT feature (InterRatOpt) and Enhanced Inter-RAT handover feature (EnhancedInterRatOpt) are both restricted, and TD-SCDMA inter-working feature (tdOpt) is unrestricted. chg_element td_enabled 0 0 Where:
is: td_enabled
element name
0
value
0
location
System response WARNING: TD-SCDMA inter-working function will be disabled, if the operator changes td_enabled element. Are you sure (y=yes, n=no)? y COMMAND ACCEPTED
68P02901W23-S
3-113 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 12 {27508} This example modifies the fieldeng_always_enabled parameter to 1. chg_ele fieldeng_always_enabled 1 0 Where:
is: fieldeng_always_enabled
element name
1
value
0
location
System response COMMAND ACCEPTED
Example 13 {32340} This example allows the operator to change the value of cell barred delay to 180 seconds. chg_element cell_barred_delay 180 0 Where:
is: cell_barred_delay
element name
180
value
0
location
System response COMMAND ACCEPTED
3-114
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 14 {26740} In this example, the value of dsp_error_inc is changed to 0 to restrict the ECERM feature. chg_element dsp_error_inc 0 0 Where:
is: dsp_error_inc
element name
0
value
0
location
System Response WARNING: Setting this attribute to a value of 0 will result in no more DSP alarms being generated for this BSS while the value remains 0. Are you sure (y=yes,n=no)?
y
COMMAND ACCEPTED
Example 15 {23292} In this example, the value of the database element gprs_mac_mode is changed to 2 when the EDA feature is unrestricted. chg_ele gprs_mac_mode 2 bsc Where:
is: gprs_mac_mode
element name
2
value
bsc
location
System Response COMMAND ACCEPTED
68P02901W23-S
3-115 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 16 {26881} In this example, the value of the database element ext_ul_dur is changed to valid value (24 250) when the extended uplink TBF feature is unrestricted. chg_element ext_ul_dur 24 0 Where:
is: ext_ul_dur
element name
24
value
0
location
System Response COMMAND ACCEPTED
Example 17 {31565} This example enables the functionality of the AGCH flow control, any one of the triggers associated with IA and IAR can trigger AGCH overload. chg_element _cell_data,20 1 1 cell_number=5 4 3 2 1 61986 34944 Where:
is: _cell_data,20
element name
1
value
1
location
5 4 3 2 1 61986 34944
cell description
System Response COMMAND ACCEPTED
Example 18 In this example, the value of sig_lnk_tst_allow is changed to 0. chg_elem sig_lnk_tst_allow 0 0 Where:
3-116
is: sig_lnk_tst_allow
element name
0
value
0
location
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System Response COMMAND ACCEPTED
Example 19 In this example, the value of sig_lnk_tst_allow is changed to 1. chg_elem sig_lnk_tst_allow 1 0 Where:
is: sig_lnk_tst_allow
element name
1
value
0
location
System Response COMMAND ACCEPTED
Example 20 {29693A} This example modifies the value of fer_meas_period to 2 to double the measuring period. chg_element fer_meas_period 2 0 Where:
is: fer_meas_period
element name
2
value
0
location
System Response COMMAND ACCEPTED
68P02901W23-S
3-117 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 21 {34164} This example modifies the value of _bss_data,1 from 0 to 1 to enable the 5 minute statistics uploading. chg_element _bss_data,1 1 0 Where:
is: _bss_data,1
element name
1
value
0
location
System Response COMMAND ACCEPTED
Example 22 {34164} This example modifies the value of _cell_data,21 from 0 to 1 to enable the 5 minute statistics uploading for cell 0 0 1 0 1 99 72 under site 114. chg_element _cell_data,21 1 114 cell 0 0 1 0 1 99 72 Where:
is: _cell_data,21
element name
1
value
114
location
0 0 1 0 1 99 72
cell description
System Response COMMAND ACCEPTED
3-118
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 23 {34320G} This example modifies the value of power_save_enable to 1 on site 1 when FR 34320G is enabled. chg_element power_save_enable 1 1 Where:
is: power_save_enable
element name
1
value
1
location
System Response COMMAND ACCEPTED
Example 24 {34320G} This example attempts to modify power_save_enable on site 15 when the BTS is not a Horizon II cabinet. chg_element power_save_enable 1 15 Where:
is: power_save_enable
element name
1
value
15
location
System Response ERROR: The site location is not a power saving capable BTS type. COMMAND REJECTED
68P02901W23-S
3-119 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 25 {34303} This example attempts to modify the value of the Abis status element to 0 to disable the Abis connection for H1 site (Site id = 1) when the Dual Abis Aware feature is enabled. chg_element _site_data, 5 0 1 Where:
is: _site_data, 5
element name
0
value
1
location
System Response COMMAND ACCEPTED
Example 26 {34303} This example attempts to modify the value of the Abis status element to 1 to enable the Abis connection for H1 site (Site id = 1). The site 1 is the relay node of a route to the BSC and its downstream node (Site 2) can only connect to the BSC through site 1. chg_element _site_data, 5 1 1 Where:
is: _site_data, 5
element name
1
value
1
location
System Response WARNING: Migrate this site may cause its downstream node sites to be isolated. Are you sure (y=yes, n=no)? Y COMMAND ACCEPTED
3-120
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 27 {34303} This example attempts to modify the value of the Abis status element to 1 to enable the Abis connection for the Horizonmacro site (Site id = 1) with a Horizon II mini expansion when the Dual Abis Aware feature is enabled. chg_element _site_data, 5 1 1 Where:
is: _site_data, 5
element name
1
value
1
location
System Response Error: Unsupported combination of cabinets for migration. COMMAND REJECTED
Example 28 {34303} This example attempts to enable the Abis connections of all the BTS sites of the BSC when the Dual Abis Aware feature is enabled. Ensure that each of the sites has a direct route to the BSC. chg_element _site_data, 5 1 all Where:
68P02901W23-S
is: _site_data, 5
element name
1
value
all
location
3-121 Nov 2009
Examples
Chapter 3: Device/function related commands
System Response WARNING: Enable Abis status for all the BTS sites under BSC? Are you sure (y=yes, n=no)? Y Site 0: ----------COMMAND REJECTED: Unallowable BTS type. Site 10: ----------COMMAND REJECTED: BTS is not B-U. Site 11: ----------COMMAND REJECTED: Unallowable BTS type. COMMAND ACCEPTED: WARNING: Not all sites were updated; errors occurred.
Example 29 {23306} This example changes the value of the bsp_overload_protection parameter to 0. chg_element bsp_overload_protection 0 bsc Where:
is: bsp_overload_protection
element name
0
value
bsc
location
System response COMMAND ACCEPTED
3-122
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 30 {23306} This example attempts to change the value of the bsp_overload_protection parameter to 2. chg_element bsp_overload_protection 2 bsc Where:
is: bsp_overload_protection
element name
2
value
bsc
location
System response ERROR: Range Error, parameter number: 2 COMMAND REJECTED
Example 31 {28337} This example modifies the value of ss7_hsp_l2_t1 to 255000 when the increased network capacity feature is enabled. chg_element ss7_hsp_l2_t1 255000 0 Where:
is: ss7_hsp_l2_t1
element name
255000
value
0
location
System response COMMAND ACCEPTED
68P02901W23-S
3-123 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 32 {25002} This example changes the value of tdm_switch to 1. chg_element tdm_switch 1 0 Where:
is: tdm_switch
element name
1
value
0
location
System response COMMAND ACCEPTED
Example 33 {25002} This example changes the value of tdm_switch to 0. chg_element tdm_switch 0 0 Where:
is: tdm_switch
element name
0
value
0
location
System response WARNING: TDM Availability Enhancements function will be disabled, if the operator changes tdm_switch element. Are you sure (y=yes, n=no)? y COMMAND ACCEPTED
3-124
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 34 {23311A} This example attempts to enable baseband hopping (hopping_support = 2) when ext_pdchs in any RTF of the cell > 0. chg_element hopping_support 2 16 Where:
is: hopping_support
element name
2
value
16
location
System Response COMMAND REJECTED: Value of ext_pdchs shall be 0 when Baseband hopping is enabled for the cell. COMMAND ACCEPTED
Example 35 {23311A} This example attempts to enable asym_edge_enabled = 1 when ext_pdchs > 0 for any RTF in the site. chg_element asym_edge_enabled 1 16 Where:
is: asym_edge_enabled
element name
1
value
16
location
System Response COMMAND REJECTED: Value of ext_pdchs shall be 0 when ASYM feature is enabled for the site COMMAND ACCEPTED
68P02901W23-S
3-125 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 36 {34321} This example modifies the value of _bss_data,10 from 0 to 1 to enable the cage management feature. chg_element _bss_data,10 1 0 Where:
is: _bss_data,10
element name
1
value
0
location
System Response COMMAND ACCEPTED
Example 37 {34900} When the TD-SCDMA inter-working feature (tdOpt) is unrestricted, change the value of _bss_data,6 to 1 when the TD-SCDMA inter-working feature is disabled (td_enabled = 0). chg_element _bss_data,6 1 0 Where:
is: _bss_data,6
element name
1
value
0
location
System Response COMMAND ACCEPTED
3-126
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
Example 38 This example modifies the value of nacc_nc2_enabled from 0 to 1 to enable the NC2 mode of NACC. chg_element nacc_nc2_enabled 1 0 Where:
is: nacc_nc2_enabled
element name
1
value
0
location
System response COMMAND ACCEPTED
References Related information Details of the database parameters that can be changed using this command are given in the relevant parameter descriptions in Chapter 6 CM database parameters of this manual.
Related command chg_element on page 3-106.
68P02901W23-S
3-127 Nov 2009
chg_hop_params
Chapter 3: Device/function related commands
chg_hop_params ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_hop_params command permits changing multiple hopping parameters for a site at one time. The changes are verified outside SYSGEN and when exiting SYSGEN mode. Synthesizer hopping and baseband hopping can be enabled in different cells at the same site. It is also possible to mix non-hopping cells and hopping cells at the same site. When the system accepts the chg_hop_params command for a particular cell, the system rejects other chg_hop_params commands until the system reconfiguration due to the first command is complete. Once the system accepts the chg_hop_params command, the system displays a warning message. If the system operator has enabled, disabled, or changed an enabled hopping system which is synthesizer hopping through the BCCH RTF, the warning message states that the site resets. The operator can abort the command to prevent a site reset. If all FHIs for the cell are disabled, the operator can change hopping support from no hopping to baseband hopping, or from no hopping to synthesizer hopping. Although the chg_hop_params parameter allows a hopping system corresponding to a Dual Band Cell to contain frequencies from either the primary or the secondary frequency band, it does not allow both at the same time. If this is attempted, an error message displays. Each cell takes about 90 seconds to finish the hopping reconfiguration. If duplicated frequencies are entered, a warning message is presented. The system ignores the duplicated frequencies. If this warning message occurs, the command must be re-entered without the duplication. This command runs the hopping verification on all cells in the specified site, even if the cells in the site are not modified. An EGPRS RTF cannot baseband hop in the same FHIs as non-EGPRS RTFs. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
If hopping_systems verification fails, the system rejects this command outside SYSGEN. The system does not verify hopping systems inside SYSGEN until SYSGEN is off. If the Extended Range feature is unrestricted: •
3-128
Both timeslots in the Extended Range timeslot pair must have the same FHI if they are part of a hopping system.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
•
Baseband and synthesizer hopping systems can only be configured among timeslots of the same type (such as Extended or Normal).
•
Synthesizer Frequency Hopping systems in Extended Range cells must have the FHIs for the BCCH carrier timeslots set to ‘0xffh’ (255).
If a Remotely Tuneable Combiner is equipped at the cell, synthesizer hopping is not allowed in a cell. The system rejects this command for microsites that are not equipped with Horizonmicro or Horizoncompact cabinets. The same chg_hop_params command cannot be used to change hopping support to 0 and disable an enabled FHI simultaneously. When using SFH with GSM 1800, there is a limit of 18 frequencies when the frequency range is set to more than 256. If the range is more than 112, only 29 frequencies are allowed. If the range is less than 112, only 64 frequencies are allowed. In a GSM 850 cell, the ARFCN range is 128 - 251. The master cabinet at the site must be a Horizon II macro in order for an EGPRS RTF to baseband hop.
NOTE This command can be entered only at the BSC. To change multiple hopping parameters at a BTS site, contact the OMC-R for help.
Format Syntax chg_hop_params [] chg_hop_params []
Input parameters The location parameter and the cell_desc parameter cannot be used together in the chg_hop_params command. If neither is entered, all cells at the location are assumed. location Specifies the site location: 0 or bsc
BSC
1 - 140
BTS
cell_desc_opt
68P02901W23-S
3-129 Nov 2009
Format
Chapter 3: Device/function related commands
The GSM cell ID of the affected cell. cell_number= can precede the GSM cell ID. The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900)
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled. Only PCS1900 systems can use a three digit MNC.
The cell_desc_opt can also be a cell name created using the cell_name command. When the cell name is entered, it must be placed inside double quotation marks. cell_number= can precede the cell name.
NOTE This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. Table 3-26 shows the baseband and synthesizer frequency hopping restrictions on the setting of the chg_hop_params command. The numbers in the columns refer to the notes that follow.
Table 3-26
Baseband and Synthesizer frequency hopping restrictions
FHI state
SFH through BCCH
E
D
E
D
E
D
Enable FHI
Yes
Yes2,3
Yes
Yes2,3
Yes
Yes2,4
Disable FHI
Yes3
Yes
Yes3
Yes
Yes4
Yes
Change MA
No5
Yes2
Yes2,3,5
Yes2
Yes2,4
Yes
Change HSN
Yes3
Yes
Yes3
Yes
Yes4
Yes
Change to no hopping
No
Yes
No
Yes
No
Yes
Change to baseband
Yes
Yes
No
No
No
No
Change to synthesizer
No
No
Yes
Yes
Yes
Yes
E = Enabled D = Disabled
3-130
Synthesizer Frequency (SFH)
Baseband
1.
The reference to the Frequency Hopping Indicator (FHI) is only to that FHI assigned to the BCCH RTF. All other FHIs in the cell are treated like the SFH column.
2.
Performs hopping verification.
3.
Notifies the Cell Resource Machine (CRM) of the changes made.
4.
Causes the affected site to be reset.
5.
The MA can be changed in synthesizer frequency hopping only as long as the new MA contains all the ARFCNs of the equipped RTFs in the hopping system.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Examples Example 1 In this example, FHIs 2 and 3 for cell 5 4 3 2 1 62259 8736 and FHI 0 and 2 for cell 0013211 have been disabled previously: chg_hop_params 2 Where:
is: 2
BTS site 2
System response Hopping systems (FHIs) to be modified in cell 5 4 3 2 1 62259 (0xF333) 8736 (0x2220)
(RETURN=no change for this cell): 3 2
Hopping support: 2 FHI 2 status (enable/disable): Mobile allocation (ARFCNs) for FHI 3: 20 60 90 Mobile allocation (ARFCNs) for FHI 2: 20 30 70 HSN for FHI 2: 25 FHI 3 status (enable/disable): disable HSN for FHI 3: Hopping systems (FHIs) to be modified in cell 0 0 1 3 2 1 1 (RETURN=no change for this cell): 2 0 Hopping support: 2 FHI 0 status (enable/disable): 1 Mobile allocation (ARFCNs) for FHI 0: 21 31 71 HSN for FHI 0: 1 FHI 2 status (enable/disable): 1 Mobile allocation (ARFCNs) for FHI 2: 21 61 91 HSN for FHI 2: WARNING: The site will be reset if the operator enabled, disabled or changed an enabled hopping system which is synthesizer hopping through the BCCH RTF Are you sure (y=yes, n=no) ? y Responding n to the Are you sure?
prompt aborts the command.
Example 2 In this example, hopping system 2 is disabled for cell 0 0 1 0 1 1 21 at site 7: chg_hop_params cell_number=0 0 1 0 1 1 21
68P02901W23-S
3-131 Nov 2009
Examples
Chapter 3: Device/function related commands
System response Hopping systems (FHIs) to be modified in cell 0 0 1 0 1 1 21 “cellname3”
(RETURN=no change for this cell): 2 0
Hopping support: 2 FHI 2 status (enable/disable): 0 Mobile allocation (ARFCNs) for FHI 2: HSN for FHI 2: WARNING:
The site will be reset if the operator enabled, disabled or changed
an enabled hopping system which is synthesizer hopping through the BCCH RTF Are you sure (y=yes, n=no) ? y
NOTE If PBCCH/PCCCH is enabled, hopping cannot be enabled on TS0 (legacy) and TS1 (restriction added with this feature) of the BCCH carrier. The WARNING is a legacy output and is printed even if the hopping system in use is baseband hopping.
Example 3 {23311A} This example attempts to enable baseband hopping (hopping_support = 2) when ext_pdchs in any RTF of the cell > 0. chg_hop_params 0 0 1 0 1 1 21 Where:
is: 0 0 1 0 1 1 21
cell description
System response Hopping systems (FHIs) to be modified in cell 0 0 1 0 1 1 21 “cellname3” (RETURN=no change for this cell): 2 Hopping support: 2 FHI 2 status (enable/disable):0 Mobile allocation (ARFCNs) for FHI 2: HSN for FHI 2: WARNING:
The site will be reset if the operator enabled, disabled or changed
an enabled hopping system which is synthesizer hopping through the BCCH RTF Are you sure (y=yes, n=no) ? y COMMAND REJECTED: Value of ext_pdchs shall be 0 when Baseband hopping is enabled for the cell.
3-132
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
References Related information Table 3-27 lists the prompts for the chg_hop_params command; ‘x’ indicates a value supplied by the system.
Table 3-27
chg_hop_params prompts
Prompt
Range
Default
Hopping support:
0-2 where: 0 = No hopping in this cell 1 = Synthesizer hopping 2 = Baseband hopping See NOTE.
0
FHI x status (enable/disable):
0 or 1 where: 0 = disable the hopping system 1 = enable the hopping system
0
Mobile allocation (ARFCNs) for FHI x:
ARFCN depends on the frequency type for the cell. If the cell is PGSM the range is 1 - 124. If the cell is EGSM the range is either: •
1 to 124, or
•
975 to 1023
Current value
If using EGSM, all of the specified ARFCNs must be in the lower range (1 - 124) or the higher range (975 - 1023, 0). If the cell is DCS1800, the range is 512 - 885. If the cell is PCS1900 the range is 512 - 810. For GSM850, the ARFCN range is 128 - 251. HSN for FHI x:
0 - 63 where: 0 is cyclic, and 1 - 63 is random
Current value
NOTE If any FHIs are enabled, hopping support cannot be 0. The system rejects the chg_hop_params command if: (1) hopping support: = 1 and the Synthesizer Hopping feature is restricted or (2) hopping support: = 2 and the Baseband Hopping feature is restricted.
68P02901W23-S
3-133 Nov 2009
References
Chapter 3: Device/function related commands
Table 3-28 lists the maximum number of frequencies in the mobile allocation. The table also provides the frequency range of the cell (which includes a combination of PGSM and GSM Extension band frequencies) as determined by System Information Type 1 size limitations in the GSM 04.08 Specification Annex J and Cell Channel Description.
Table 3-28
Cell frequencies/mobile allocation
Frequencies of the cell (ARFCNs used)
Maximum number of frequencies in the mobile allocation
1 - 124
64
975 - 1023
49
1 - 124, 975 - 1023
16
0, 1 - 124
17
0, 957 - 1023
17
0, 1 - 124, 975 - 1023
17
Related command disp_hopping on page 3-320. Table 3-29 lists the restrictions on related commands.
Table 3-29
Restrictions on related commands
Current hopping support and FHI status
chg_hop_params command change hopping support
disable FHI
enable FHI
change MA
change HSN
Baseband hopping FHI is enabled
Command allowed
Command allowed
Command rejected; cannot change MA of an enabled FHI. Disable the FHI and equip the RTF before changing the MA
Command allowed.
Command rejected. FHI must be disabled before changing hopping support
Baseband hopping FHI is disabled
Command allowed
Command allowed.
Command allowed
Command allowed
Command allowed
Continued
3-134
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 3-29
References
Restrictions on related commands (Continued)
Current hopping support and FHI status
chg_hop_params command change hopping support
disable FHI
enable FHI
change MA
change HSN
Synthesizer hopping FHI is enabled
Command allowed
Command allowed
Command allowed. MA can change so long as the new MA contains all the ARFCNs of the equipped RTFs in the hopping system.
Command allowed
Command rejected. FHI must be disabled before changing hopping support
Synthesizer hopping FHI is disabled
Command allowed
Command allowed
Command allowed
Command allowed
Command allowed
Synthesizer through BCCH hopping FHI is enabled
Command allowed; resets the site
Command allowed
Command allowed; resets the site
Command allowed; resets the site
Command rejected. FHI must be disabled before changing hopping support
Synthesizer through BCCH hopping FHI is disabled
Command allowed
Command allowed; resets the site
Command allowed
Command allowed
Command allowed
68P02901W23-S
3-135 Nov 2009
chg_ksw_config
Chapter 3: Device/function related commands
chg_ksw_config ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_ksw_config command indicates how KSWs are physically connected when two or more KSW pairs are equipped at a site. KSWs are connected through the EXP KSWX cards to form a larger switching network. The TDM highway of a site can consist of up to four portions. A different KSW pair handles each portion. The first identifier of a KSW is the portion of the TDM highway handled by that KSW. The highway portions are defined as: Highway Portion 0
TDM timeslots 0 - 1023 handled by KSW pair 0.
Highway Portion 1
TDM timeslots 1024 - 2047 handled by KSW pair 1.
Highway Portion 2
TDM timeslots 2048 - 3071 handled by KSW pair 2.
Highway Portion 3
TDM timeslots 3072 - 4095 handled by KSW pair 3.
Two TDM highways are supported, TDM 0 and TDM 1. One TDM highway is active and the other is a redundant standby. KSW 0 0, KSW 1 0, KSW 2 0, and KSW 3 0 can be interconnected to form TDM 0. KSW 0 1, KSW 1 1, KSW 2 1, and KSW 3 1 can be interconnected to form TDM 1. The second KSW identifier indicates to which TDM highway the KSW belongs. Expansion KSW (KSWX) cards are used to interconnect the KSW pairs. The KSWX cards are required in each cage with a KSW pair. The chg_ksw_config command specifies the fiber optic connections between the KSWX cards. The KSWX cards for TDM 0 are located in slots U21, U22, and U23. The KSWX cards for TDM 1 are located in slots U9, U8, and U7. The KSWX fiber optic connections for TDM 1 must match the KSWX fiber optic connections for TDM 0. The KSWX in slot U9 mirrors the connections of the KSWX in slot U21. The KSWX in slot U8 mirrors the connections of the KSWX in slot U22. The KSWX in slot U7 mirrors the connections of the KSWX in slot U23. A chg_ksw_config command is required for each KSW pair equipped at the site when more than one KSW pair is equipped. Only one command is required per KSW pair because the fiber optic connections for TDM 0 and TDM 1 match. A warning prompt displays when this command is entered, from which the operator can abort the command. A warning displays when coming out of SYSGEN mode if each set of TDM highway identifiers are not unique in each cage.
3-136
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
The command is only issued for InCell sites. The command does not apply to M-Cell sites. Security level
4
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
See the Service Manual BSC/RXCDR (68P02901W38) for information regarding the hardware layout of the KSW pairs.
Operator actions
Check the information regarding the hardware layout of the KSW pairs. Respond to the warning prompt after entry of the command. This command is executed in or out of SYSGEN mode.
Format Syntax chg_ksw_config [] [] []
Input parameters location Specifies the KSW location: 0 or bsc
BSC or RXCDR
1 - 140
BTS
ksw_pair The KSW pair being configured. The range of values is 0 - 3: 0
KSW pair 0 corresponds to KSW 0 0 and KSW 0 1
1
KSW pair 1 corresponds to KSW 1 0 and KSW 1 1
2
KSW pair 2 corresponds to KSW 2 0 and KSW 2 1
3
KSW pair 3 corresponds to KSW 3 0 and KSW 3 1
kswx_connected_to_hwy_0 The KSWX pair that connects this KSW pair to highway portion 0. The KSWX pair is in the same cage as the KSW pair being configured. Valid values are 0 - 3.
68P02901W23-S
3-137 Nov 2009
Examples
Chapter 3: Device/function related commands
KSWX pairs are defined as: 0
The highway portion is the same as the KSW pair being configured.
1
KSWX cards in slots U21 (EXP KSWX A0) and U9 (EXP KSWX B0).
2
KSWX cards in slots U22 (EXP KSWX A1) and U8 (EXP KSWX B1).
3
KSWX cards in slots U23 (EXP KSWX A2) and U7 (EXP KSWX B2).
kswx_connected_to_hwy_1 The KSWX pair that connects this KSW pair to highway portion 1. The KSWX pair is in the same cage as the KSW pair being configured. This parameter is not required if KSW pairs 1, 2, and 3 are not equipped. Valid values are 0 - 3. kswx_connected_to_hwy_2 The KSWX pair that connects this KSW pair to highway portion 2. The KSWX pair is in the same cage as the KSW pair being configured. This parameter is not required if KSW pairs 2 and 3 are not equipped. Valid values are 0 - 3. kswx_connected_to_hwy_3 The KSWX pair that connects this KSW pair to highway portion 3. The KSWX pair is in the same cage as the KSW pair being configured. This parameter is not required if KSW pair 3 is not equipped. Valid values are 0 - 3.
Examples Example 1 This example describes the KSWX fiber optic connections for a standard 4 cage expanded BSC with redundancy. The chg_ksw_config commands for configuring the following expanded setup are described. CAGE 0: KSW 0 0 and KSW 0 1 (KSW Pair 0) are equipped in CAGE 0 KSWX in slot U21 is connected to KSWX in cage 1 slot U21 KSWX in slot U22 is connected to KSWX in cage 2 slot U21 KSWX in slot U23 is connected to KSWX in cage 3 slot U21 KSWX in slot U9 is connected to KSWX in cage 1 slot U9 KSWX in slot U8 is connected to KSWX in cage 2 slot U9 KSWX in slot U7 is connected to KSWX in cage 3 slot U9 CAGE 1: KSW 1 0 and KSW 1 1 (KSW pair 1) are equipped in CAGE 1 KSWX in slot U21 is connected to KSWX in cage 0 slot U21 KSWX in slot U22 is connected to KSWX in cage 2 slot U22
3-138
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
KSWX in slot U23 is connected to KSWX in cage 3 slot U22 KSWX in slot U9 is connected to KSWX in cage 0 slot U9 KSWX in slot U8 is connected to KSWX in cage 2 slot U8 KSWX in slot U7 is connected to KSWX in cage 3 slot U8 CAGE 2: KSW 2 0 and KSW 2 1 (KSW pair 2) are equipped in CAGE 2 KSWX in slot U21 is connected to KSWX in cage 0 slot U22 KSWX in slot U22 is connected to KSWX in cage 1 slot U22 KSWX in slot U23 is connected to KSWX in cage 3 slot U23 KSWX in slot U9 is connected to KSWX in cage 0 slot U8 KSWX in slot U8 is connected to KSWX in cage 1 slot U8 KSWX in slot U7 is connected to KSWX in cage 3 slot U7 CAGE 3: KSW 3 0 and KSW 3 1 (KSW pair 3) are equipped in CAGE 3 KSWX in slot U21 is connected to KSWX in cage 0 slot U23 KSWX in slot U22 is connected to KSWX in cage 1 slot U23 KSWX in slot U23 is connected to KSWX in cage 2 slot U23 KSWX in slot U9 is connected to KSWX in cage 0 slot U7 KSWX in slot U8 is connected to KSWX in cage 1 slot U7 KSWX in slot U7 is connected to KSWX in cage 2 slot U7 The commands for configuring the expansion are: chg_ksw_config 0 0 0 1 2 3 chg_ksw_config 0 1 1 0 2 3 chg_ksw_config 0 2 1 2 0 3 chg_ksw_config 0 3 1 2 3 0
68P02901W23-S
3-139 Nov 2009
Examples
Chapter 3: Device/function related commands
For example, in the command chg_ksw_config 0 2 1 2 0 3 for KSW pair 2: Parameter...
with value...
indicates that...
location
0
this parameter is the BSC.
ksw_pair
2
this parameter is for the KSW pair 2 which is in cage 2.
kswx_connected_to_hwy_0
1
the KSWXs in slot U21 and U9 in the cage with KSW pair 2, connect to the cage with KSW pair 0.
kswx_connected_to_hwy_1
2
the KSWXs in slot U22 and U8 in the cage with KSW pair 2, connect to the cage with KSW pair 1.
kswx_connected_to_hwy_2
0
the highway number is the same as the KSW pair number.
kswx_connected_to_hwy_3
3
the KSWXs in slot U23 and U7 in the cage with KSW pair 2, connect to the cage with KSW pair 3.
Example 2 Slot U7 can contain a CLKX card or a KSWX card. If a chg_ksw_config command applies to slot U7, the BSC checks to see if a CLKX card has been equipped in the slot. CLKX slot utilization is specified in the GCLK equip command. In this example, the BSC rejects a change because a CLKX has been equipped in slot U7: equip 0 gclk
System response Enter the device identifier for the GCLK: 0 Enter the cage number: 0 Is CLKX 0 (slot U7) present?: yes Is CLKX 1 (slot U6) present?: no Is CLKX 2 (slot U5) present?: no COMMAND ACCEPTED MMI-RAM 0115 -> chg_ksw_config bsc 0 0 3 2 1 COMMAND REJECTED: Slot U7 is in use by a CLKX card.
3-140
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
References Related command disp_element on page 3-272.
68P02901W23-S
3-141 Nov 2009
chg_level
Chapter 3: Device/function related commands
chg_level ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{27508}
Description The chg_level command is a dummy command provided to support legacy customer scripts which require this command to change to a different security level. Security level
1
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
None
Format Syntax chg_level
Input parameters There are no input parameters since the command is interactive.
Examples Example 1 In the following example, the security level is not changed. The password is not displayed when entered: chg_level
System response Enter password for security level you wish to access: 3stooges Enter password for security level you wish to access: 4beatles Current security level is unchanged
3-142
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
Example 2 In the following example, the security level is not changed. The password is not displayed when entered: chg_level
System response Enter password for security level you wish to access: anything Enter password for security level you wish to access: random Current security level is unchanged
References Related command disp_level on page 3-325.
68P02901W23-S
3-143 Nov 2009
chg_rtf_freq
Chapter 3: Device/function related commands
chg_rtf_freq ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_rtf_freq command changes the absolute radio frequency channel for a particular RTF. This operation causes a carrier to be taken out of service. Calls are lost if no other carrier is available. A long warning prompt is presented when this command is invoked. The operator aborts the command at the warning. Security level
4
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
In a synthesizer hopping system: •
If the frequency is already defined as hopping in all the RTF hopping systems, a new frequency is added when hopping is enabled. Applicable for non-BCCH RTF only.
•
If FHIs are enabled, it is not allowed for BCCH RTFs.
•
The new frequency is added when hopping is disabled regardless of whether the frequency is already a hopping frequency.
In a baseband hopping system: •
This command is rejected outside SYSGEN ON mode if the RTF has hopping FHIs and any FHIs are enabled.
•
This command automatically updates the frequency in the mobile allocation if all associated FHIs are disabled and the original frequency is already in the MA list.
In a Dual Band system: •
3-144
When the Dual Band Cells option is enabled, the frequency type is managed on a per zone basis. Primary band carriers are configured in the outer zone and secondary band carriers are configured in the inner zone.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Dependencies
Operator actions
Description
•
To have different DRI/RTF group identifiers, the BSS requires DRI/RTFs within a cell to have different frequency types.
•
When the inner_zone_alg parameter is set to 3 (specifying Dual Band), the frequency type as defined by the secondary band determines the ARFCN range for an inner zone RTF.
•
The BSS requires primary and secondary band RTFs in a Dual Band Cell to be configured with the DRI/RTF group identifier associated with their band. If there is an attempt to use the same DRI/RTF group identifier for RTFs in both the primary and secondary bands of a Dual Band Cell, an error message is printed and the command is rejected.
•
The cabinets to which the DRIs in each zone are equipped must allow the primary and secondary band frequency types.
In PCS 1900 systems, the maximum transmit power (max_tx_bts) limits the frequency entered. If the frequency is a block edge ARFCN, the max_tx_bts must be greater than or equal to 4 (less than 36 dBm) unless one of the following are true: •
The block edge ARFCN is between the adjacent frequency blocks that are available to the BTS. ARFCNs 512 and 810 are always limited.
•
The inner_zone_alg parameter is set in a chg_cell_element command to value 1. That is, Concentric Cell feature enabled and the power based use algorithm used. The block edge frequency is defined to be an inner zone carrier with a maximum transmit power level less that 36 dBm. Block edges are 512, 585, 587, 610, 612, 685, 687, 710, 712, 735, 737, and 810.
Respond to the warning prompt presented when this command is entered.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
68P02901W23-S
3-145 Nov 2009
Format
Chapter 3: Device/function related commands
Format Syntax chg_rtf_freq
Input parameters frequency Identifies the absolute radio frequency channel. The range of valid values varies by frequency type. The range of values is: 1 - 124 (PGSM) 0, 1 - 124, 975 - 1023 (EGSM) 512 - 885 (DCS1800) 512 - 810 (PCS1900) 128 - 251 (GSM850)
NOTE The EGSM values are available only if the egsm_bcch_sd parameter is enabled.
location Specifies the radio frequency channel location: 0 or bsc
BSC
1 - 140
BTS
rtf_id1 First device identifier. The range of values is 0 - 5. rtf_id2 Second device identifier. The range of values is 0 - 11.
Example This example changes the frequency channel to 99 for RTF 5 11 at BTS 40.
3-146
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
chg_rtf_freq 99 40 5 11 Where:
is: 99
frequency
40
location
5
rtf_id1
11
rtf_id2
System response WARNING: This operation may cause a carrier to be taken out of service and calls affected by this carrier may be lost. Loss of calls depends on the availability of other carriers. Are you sure (y=yes,n=no)? y COMMAND ACCEPTED
References Related information The range of values for GSM Phase 2 is: PGSM
EGSM
DCS1800
PCS1900
RTF_BCCH
1 - 124
RTF_NON_BCCH
1 - 124
RTF_BCCH
1 - 124
RTF_NON_BCCH
1 - 124 or 0, 975 - 1023
RTF_BCCH
512 - 885
RTF_NON_BCCH
512 - 885
RTF_BCCH
512 - 810
RTF_NON_BCCH
512 - 810
Related commands add_rtf_path on page 3-50
copy_path on page 3-187
del_rtf_path on page 3-204
disp_rtf_path on page 3-381
68P02901W23-S
3-147 Nov 2009
chg_severity
Chapter 3: Device/function related commands
chg_severity ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_severity command changes the severity of device and non-reconfiguration alarms. The number of alarms that can be modified is limited to 100. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
NOTE Enter this command at the BSC or RXCDR only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax chg_severity
Input parameters device_name The name of the device, such as GPROC, MSI or DRI, to be modified. alarm code The decimal number identifying the alarm code for the device to be modified.
3-148
•
Refer to Alarm devices on page 3-20 for the ranges of alarm codes for each device.
•
Refer to the Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) manual for a list of all alarms and the corresponding alarm codes for each device.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Example
severity The desired severity for the alarm. The available values are: investigate critical major minor warning
Example This example shows how to change the severity of GPROC alarm code 8 from MAJOR to CRITICAL. chg_severity gproc 8 critical Where:
is: gproc
device_name
8
alarm_code
critical
severity
System response COMMAND ACCEPTED
References Related command disp_severity on page 3-383.
68P02901W23-S
3-149 Nov 2009
chg_smscb_msg
Chapter 3: Device/function related commands
chg_smscb_msg ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_smscb_msg command changes a selected CBCH background message and the language in which it is presented. Message numbers uniquely identify the background messages. The background message in all cells at all sites connected to the BSC can be modified. When the command is entered, the MMI responds with an Enter the message prompt. Enter the CBCH background message after the MMI prompt. The GSM standard message can consist of up to 93 characters, entered in hexadecimal or ASCII notation, and terminated by pressing the RETURN key. The ASCII and hexadecimal methods of input can be interspersed in the same message. The following two messages are equivalent: Motorola Cellular \4d\6f\74\6f\72\6f\6c\61 \43\65\6c\6c\75\6c\61\72 Because terminals handle automatic truncation in different ways, it is recommended that messages longer than one line are truncated explicitly by the operator, to form strings shorter than the length of one line. A message can be truncated anywhere by keying \ followed by RETURN. The \ must not separate a hexadecimal character otherwise the two parts read as two separate ASCII characters. The message created using this command is displayed using the disp_cbch_state command. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
Short Message Service (SMS) is a purchasable option which must be installed on the system. The chg_element cbch_enabled command must be used before the chg_smscb_msg command is successfully used.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
3-150
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
Format Syntax chg_smscb_msg chg_smscb_msg all
Input parameters msg_num Uniquely identifies the number of the message for a given cell. The range of values is 0 - 3. message_id The ITU standard identifier for the background message. The range of values is 0 - 65535. gs Geographical scope. This parameter indicates the area over which the message is unique. The range of values is 0 - 3, where: 0
Immediate, Cell Wide
1
Normal, PLMN Wide
2
Normal, Location Area Wide
3
Normal, Cell Wide
msg_code The ITU standard message code; used to differentiate between messages of the same source and type. The range of values is 0 - 1023. update_number Refers to the number of an update to an existing message. The range of values is 0 - 15. This number used to be automatically incremented for each update to a message. As an input parameter, it now allows the operator to specify a particular update. For example, the same update of a message in a new cell is used as in the existing cells.
68P02901W23-S
3-151 Nov 2009
Format
Chapter 3: Device/function related commands
data_coding_scheme This parameter determines the language for the CBCH background message. The following languages are available: 0 - German
7 - Danish
14 - Polish
1 - English
8 - Portuguese
32 - Czech
2 - Italian
9 - Finnish
3 - French
10 - Norwegian
4 - Spanish
11 - Greek
5 - Dutch
12 - Turkish
6 - Swedish
13 - Hungarian
NOTE The values of 15 - 31 and 33 - 255 are not specified for the data_coding_scheme. Only the listed languages are currently available.
cell_desc The GSM cell identifier (either the cell name or cell number) for the cell being modified. GSM cell ID of the cell to be modified, preceded by cell_number=. The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900)
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format is enabled.
The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks and cell_name= must precede it. The value all is a valid input for cell_desc; this value changes the specified messages for all cells at the BSS.
NOTE This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition.
3-152
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Examples Example 1 This example changes the CBCH background message for cell_desc=5 4 3 2 1 61986 34944 to have a message number of 0, a message ID of 1234, a geographical scope of 2, a message code of 0, an update number of 0, and a language ID of 1. chg_smscb_msg 0 1234 2 0 0 1 cell_number=5 4 3 2 1 61986 34944 Where:
is: 0
message_number
1234
message_id
2
geographical_scope
0
message_code
0
update_number
1
data_coding_scheme
cell_number=5 4 3 2 1 61986 34944
cell_desc
System response Enter the Message: COMMAND ACCEPTED
68P02901W23-S
3-153 Nov 2009
References
Chapter 3: Device/function related commands
Example 2 This example changes the CBCH background message for all cells to have a message ID of 1234 and a language ID of 1. chg_smscb_msg 0 1234 2 0 0 1 all Where:
is: 0
message_number
1234
message_id
2
geographical_scope
0
message_code
0
update_number
1
data_coding_scheme
all
cell_desc; indicates changes to all cells
System response Enter the Message: COMMAND ACCEPTED
References Related information Table 3-30 lists SMS special characters. Alphabetical characters that cannot be directly entered from the keyboard are included in messages by using the backslash (\) character followed by a two character value. The first character is a number from 0 to 7. The second character is a hexadecimal value (0 to F) corresponding to the row in the table. For example, the city of Köln could be included in a message by entering K\7Cln.
Table 3-30
SMS special characters
0
1
2
3
4
5
6
7
0
@
∆
Space
0
¡
P
¿
p
1
£
_
!
1
A
Q
a
q
2
$
Φ
“
2
B
R
b
r
3
¥
Γ
#
3
C
S
c
s
4
è
Λ
¤
4
D
T
d
t Continued
3-154
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 3-30
References
SMS special characters (Continued)
0
1
2
3
4
5
6
7 u
5
é
Ω
%
5
E
U
e
6
ù
Π
&
6
F
V
f
v
7
ì
Ψ
'
7
G
W
g
w
8
ò
Σ
(
8
H
X
h
x
9
Ç
Θ
)
9
I
Y
i
y
A
Line Feed
Ξ
*
:
J
Z
j
z
B
Ø
Not Used
+
;
K
Ä
k
ä
C
ø
Æ
,
<
L
Ö
l
ö
D
Carriage Return
æ
-
=
M
Ñ
m
ñ
E
Å
ß
.
>
N
Ü
n
ü
F
å
É
/
?
O
§
o
à
GSM technical specification The permitted alphabet is defined in 03.38.
Related commands del_smscb_msg on page 3-206
68P02901W23-S
disp_cbch_state on page 3-237
3-155 Nov 2009
chg_throttle
Chapter 3: Device/function related commands
chg_throttle ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_throttle command changes the throttle period for an intermittent alarm. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax chg_throttle
Input parameters device_name Name that uniquely identifies the device. alarm_code Identifies the alarm to be throttled; the range is 0 - 254. Some of the codes are obsolete, refer to the manual Maintenance Information: Alarm handling at the OMC-R (68P02901W26) for usable alarm codes. throttle_count Specifies the new throttle count in minutes. A value of 0 means throttling is disabled. The range of values is 0 - 1440.
3-156
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Example
Example This example changes the throttle period for alarm code 1 of an MMS to 10 minutes. chg_throttle mms 1 10 Where:
is: mms
device_name
1
alarm_code
10
throttle_count
System response COMMAND ACCEPTED
References Related command disp_throttle on page 3-386.
68P02901W23-S
3-157 Nov 2009
chg_time
Chapter 3: Device/function related commands
chg_time ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_time command sets the real-time system clock. The clock can be set to a specific date and time of day or changed relative to the current time of day. The relative change is useful for changing the clock for daylight savings time. Security level
4
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
None
Format Syntax chg_time or chg_time
Input parameters year Value identifying the year. The year is entered in the four-digit format. The range of values is 1980 - 2100. month Value identifying the month. The range of values is 1 - 12. day Value identifying the day of the month. The range of values is 1 - 31.
3-158
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
A plus or minus, as the first argument, adds or subtracts the specified number of hours and minutes from the current time on the system clock. hour Value identifying the hour. The range of values is 0 - 23. This value can also be used to specify the number of hours to be added or subtracted to the current system time. minute Value identifying the minute. The range of values is 0 - 59. This value can also be used to specify the number of minutes to be added or subtracted to the current system time. second Value identifying the second. The range of values is 0 - 59.
Examples Example 1 In this example, the system clock is set to year (1993), month (November), day (12th), and time (09:23:00): chg_time 1993 11 12 9 23 0 Where:
is: 1993
year
11
month
12
day
9
hour
23
minute
0
second
System response Mon Nov 12 09:23:00 1993
68P02901W23-S
3-159 Nov 2009
References
Chapter 3: Device/function related commands
Example 2 In this example, one hour is added to the current time for daylight savings time: chg_time + 1 0 Where:
is: +
add to the system clock time.
1
hours to be added.
0
minutes to be added.
System response Mon Nov 12 10:23:00 1995
References Related commands chg_throttle on page 3-156
3-160
time_stamp on page 3-548
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
chg_ts_usage
chg_ts_usage ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_ts_usage command does the following: •
Reserves timeslots
•
Nails timeslots
•
Frees reserved timeslots
•
Frees nailed timeslots
The chg_ts_usage command supports the following operations: RESERVE
This operation reserves timeslots. A timeslot cannot be used for any connections when it is reserved.
FREE
This operation frees timeslots that have been reserved or nailed using the NAIL or RESERVE operations. It does not free timeslots that have been nailed using the NAIL_PATH operation. Timeslots freed using this operation become unused and can be used for any connections.
FREE_PATH
This operation frees the timeslots of a NAIL_PATH nailed connection between different sites. Timeslots freed using this operation become unused and can be used for normal connections.
NAIL
This operation establishes a nailed connection between two timeslots at the same site.
NAIL_PATH
This operation establishes a nailed connection between two timeslots at different sites.
The E1 timeslot mapping on an HDSL link that supports 16 E1 timeslots restricts the timeslots available to a number within the range 0 - 31. The number of timeslots that can be RESERVE, NAIL, FREE_PATH, or NAIL_PATH is restricted to 1 on HDSL links where only 16 timeslots are available. The system rejects a chg_ts_usage nail_path command when the path contains a ts_switch. Security level
4
Supported by OMC-R GUI
No
Command type
B (operator actions)
Prerequisites
MSIs must be equipped before timeslots can be nailed or reserved using the chg_ts_usage command. The system rejects the chg_ts_usage command when a 16 kbit/s XBL link is equipped on the timeslot.
Operator actions
Respond to command prompts.
68P02901W23-S
3-161 Nov 2009
Format
Chapter 3: Device/function related commands
NOTE Enter this command at the BSC and RXCDR only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax chg_ts_usage The system responds with a series of prompts for input parameters dependent on the action requested.
Input parameters The parameters used with this command are prompted for in the system response and are dependent upon the specified operation. Refer to the descriptions for function and valid values of the input parameter prompts: Enter Action: The type of operation to be performed. This field is entered as upper or lower case characters with one of: RESERVE
Reserve timeslots.
FREE
Free timeslots that have been reserved or nailed using the NAIL or RESERVE operations.
NAIL
Establish a nailed connection between two timeslots at the same site.
FREE_PATH
Free the timeslots of a nailed connection between different sites.
NAIL_PATH
Establish a nailed connection between two timeslots at different sites.
Enter Site Identifier: Specifies the location of the MMS at one end of the E1 Mbit/s link for FREE, RESERVE, and NAIL operations only. Values are: 0 or bsc
BSC
1 to 140
BTS
Enter MMS 1 Identifiers: First and second identifiers of the MMS at one end of the E1 link. Values are:
3-162
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
First identifier: 0 to 55
BSC
0 to 123
RXCDR
0 to 9
BTS
Second identifier: 0 or 1 0 to 5 for Horizon II site.
Enter MMS 2 Identifiers: First and second identifiers of the MMS at the other end of the E1 link. Values are: First identifier: 0 to 55
BSC
0 to 123
RXCDR
0 to 9
BTS
Second identifier: 0 or 1 0 to 5 for Horizon II site.
Enter Starting Timeslot: First of the contiguous timeslots to be reserved or freed using the RESERVE or FREE operations only. Values are: 1 to 31
For 2.048 Mbit/s E1 Links, including a 32/16 timeslot HDSL link
Enter Starting Timeslot for MMS 1: Start timeslot number for MMS1 used with the NAIL, NAIL_PATH, or FREE_PATH operations only. Values are: 1 to 31
For 2.048 Mbit/s E1 Links
Enter Starting Timeslot for MMS 2: Start timeslot number for MMS2 used with the Nail, NAIL_PATH, or FREE_PATH operations only. Values are: 1 to 31
For 2.048 Mbit/s E1 Links
Enter Start Site:
68P02901W23-S
3-163 Nov 2009
Examples
Chapter 3: Device/function related commands
The start SITE to be nailed or freed using the NAIL_PATH or FREE_PATH operations only. Values are: 0 to 100
BSC or BTS
Enter End Site: The end SITE to be nailed or freed using the NAIL_PATH or FREE_PATH operations only. Values are: 0 to 100
BTS or BSC
Enter Path Identifiers The PATH to be nailed or freed using the NAIL_PATH or FREE_PATH operations only. This represents the terminating site of the path. Values are: 0 to 100
BSC or BTS
Enter Number of Timeslots Requested: The number of contiguous timeslots to be reserved, nailed, or freed. Values are: 1 to 31
For 2.048 Mbit/s E1 Links
Examples Example 1 In this example, the contiguous timeslots from 16 through 31 at BTS 26 for MMS 1 0 are reserved: chg_ts_usage
System response Enter action:
RESERVE
Enter Site Identifier:
26
Enter MMS Identifiers:
1 0
Enter Starting Timeslot:
16
Enter Number of Timeslots Requested:
3-164
16
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
Example 2 In this example, a PATH is nailed from timeslot 5 of MMS 1 0 to timeslot 7 of MMS 0 1 at BTS 26: chg_ts_usage
System response Enter Action:
NAIL
Enter Site Identifier:
26
Enter MMS 1 Identifiers:
1 0
Enter Starting Timeslot for MMS 1: Enter MMS 2 Identifiers:
5
0 1
Enter Starting Timeslot for MMS 2:
7
Enter Number of Timeslots Requested:
3
Example 3 In this example, the PATH identifier is 1 1 and timeslot 5 of site 1 is nailed to timeslot 6 of site 2: chg_ts_usage
System response Enter action:
NAIL_PATH
Enter Path Identifiers: Enter Start Site:
1 1
1
Enter MMS 1 Identifiers:
0 0
Enter Starting Timeslot for MMS 1: Enter End Site:
5
2
Enter MMS 2 Identifiers:
1 0
Enter Starting Timeslot for MMS 2: Enter Number of Timeslots Requested:
6 3
References Related command disp_mms_ts_usage on page 3-330.
68P02901W23-S
3-165 Nov 2009
chg_x25config
Chapter 3: Device/function related commands
chg_x25config ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The chg_x25config command changes the X.25 link parameters. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax chg_x25config
Input parameters link type Specifies the type of X.25 link: oml
change parameters for all OMLs in the BSS
cbl
change parameters for all CBLs in the BSS
NOTE OML parameters are stored in NVRAM on the GPROCs at the BSC; they are not stored in the database. Therefore, OML parameters cannot be changed.
3-166
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
x25_parameter Specifies the type of X.25 parameter being changed for all OMLs or CBLs: packet_size window_size The type of X.25 parameter is shown in the OMC GUI window in BSS View as config_packet_size and config_window_size respectively. value Specifies the new value of the X.25 link: packet_size
128, 256, 512
window_size
2-7
Examples Example 1 The following example changes the X.25 settings for all BSS OMLs: chg_x25 oml window_size 6 Where:
is: oml
link type
window_size
x25_parameter
6
value
System response: COMMAND ACCEPTED
Example 2 The following example changes the X.25 settings for all BSS CBLs: chg_x25 cbl packet_size 256 Where:
68P02901W23-S
is: cbl
link type
packet_size
x25_parameter
256
value
3-167 Nov 2009
References
Chapter 3: Device/function related commands
System response COMMAND ACCEPTED
References Related command disp_x25config on page 3-401.
3-168
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
clear_cal_data
clear_cal_data ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The clear_cal_data command clears calibration data previously stored (at the BSC) for a specified radio unit on a per DRI basis. When this command is entered, a warning is displayed that the calibration data for the specified transceiver is cleared. Security level
3
Supported by OMC-R GUI
No
Command type
B (operator action required)
Prerequisites
This command is not available while in SYSGEN ON mode. This command is not entered at a BTS. The DRI device must be locked.
Operator actions
Respond to the warning prompt.
Format Syntax clear_cal_data dri []
Input parameters location 0 or bsc
BSC
dri The DRI is the only device permitted for this command. dev_id The first device identifier. The range is 0 - 5. dev_id The second device identifier. The range is 0 - 11.
68P02901W23-S
3-169 Nov 2009
Example
Chapter 3: Device/function related commands
dev_id The third device identifier. This value defaults to 0 if no value is entered.
Example The following example clears the calibration data for DRI 5 3 0 at site 21: clear_cal_data 21 dri 5 3 0 Where:
is: 21
site
dri
dri device
5
first dev_id
3
second dev_id
0
third dev_id
System response Warning: This will clear the calibration data for this transceiver Are you sure (y=yes,n=no)? y COMMAND ACCEPTED
References Related commands disp_cal_data on page 3-233
3-170
store_cal_data on page 3-534
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
clear_database
clear_database ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The clear_database command deletes the contents of the CM database.
CAUTION This command must be used only by personnel who fully understand the consequences. The system is placed in the initial SYSGEN mode when this command is entered. Refer to SYSGEN mode on page 1-43. Security level
4
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
This command can only be entered in the SYSGEN ON mode.
Operator actions
Place the system in the SYSGEN ON mode before entering this command.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax clear_database
Input parameters There are no input parameters associated with this command.
68P02901W23-S
3-171 Nov 2009
Example
Chapter 3: Device/function related commands
Example In this example, the CM database is cleared with the system in SYSGEN ON mode: clear_database
System response COMMAND ACCEPTED
3-172
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
clear_gclk_avgs
clear_gclk_avgs ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The clear_gclk_avgs command clears the stored LTA values and the stored samples for a specified GCLK or MMS. If this command is entered, the LTA value is set to 80 h and the frequency register readings are cleared. •
If this command is entered at an InCell site, a prompt for a GCLK ID displays.
•
If this command is entered at a non-InCell site, a prompt for an MMS ID displays.
Clear the LTA values under the following circumstances: •
The GCLK is replaced.
•
The GCLK is recalibrated.
•
The uplink site does not provide a stable clock source.
Security level
3
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
This command is not allowed while in the SYSGEN ON mode.
Format Syntax clear_gclk_avgs
Input parameter location Specifies the location of the device: 0 or bsc
BSC
1 - 140
BTS
68P02901W23-S
3-173 Nov 2009
Example
Chapter 3: Device/function related commands
Example In this example, the LTA values for GCLK 1 at InCell SITE 0 are cleared: clear_gclk_avgs 0 Where:
is: 0
location
System response Enter the gclk_id: 1
COMMAND ACCEPTED
References Related information The system reads the clock frequency register of each GCLK once every half hour after synchronization when the GCLK is in phase_locked mode. A rolling average for each GCLK is calculated from up to 48 clock frequency register readings. This average is the Long Term Average (LTA). An alarm is generated if 25% or more of the stored clock frequency readings differ from the calculated LTA by more than the value that the lta_alarm_range parameter defines.
Related commands disp_gclk_avgs on page 3-309
3-174
disp_gclk_cal on page 3-311
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
configure_csfp
configure_csfp ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The configure_csfp command configures CSFP (Code Storage Facility Processor) devices to sites in the BSS network. This command selects a BSP, BTP, or pool GPROC device, dependent on the CSFP algorithm setting for that site, and converts the selected device to a CSFP device. Security level
4
Supported by OMC-R GUI
Yes
Command type
B (Operator actions required)
Prerequisites
This command can only be executed when the system is SYSGEN ON mode
Operator actions
Put the system into SYSGEN ON mode before executing this command.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Refer to the OMC-R for help.
Format Syntax configure_csfp
Input parameters There are no input parameters associated with this command.
Example This example shows the input required to configure the CSFP devices to sites in the BSS network. configure_csfp
68P02901W23-S
3-175 Nov 2009
References
Chapter 3: Device/function related commands
System response COMMAND ACCEPTED
References Related information Depending on the CSFP stealing algorithm (set using the chg_csfp command), the device stolen to become the CSFP can vary. If the algorithm is set to ‘any’ (the default value), an equipped GPROC is chosen first instead of choosing the redundant BSP or BTP device.
Algorithm set NONE
No CSFPs are configured at the site. The location does not matter.
STBY
If location is BSC and two BSPs are equipped then one is configured as CSFP. If location is a remote BTS and two BTPs are equipped then one is configured as CSFP.
POOL
For either BSC or remote BTS locations, an equipped GPROC is configured as CSFP.
ANY
First the POOL algorithm is applied and then the STBY algorithm is applied. ANY is the default algorithm.
NOTE If there is only one GPROC in the second cage, it cannot be chosen as a configured CSFP.NOTE.
Related Commands chg_csfp on page 3-95
3-176
disp_csfp on page 3-263
unconfigure_csfp on page 3-568
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
connection_code
connection_code ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The connection_code command is used for the following: •
To change operator-defined code that triggers the resource trace of a call.
•
To turn the Call Connectivity Trace feature off.
•
To display the current value of operator-defined code.
Security level
2
Supported by OMC-R GUI
No
Command type
A (no operator action required)
Prerequisites
The GPRS must be unrestricted to assess a PCU site.
Format Syntax connection_code [“”]
Input parameter operator-defined code Six-digit number; each digit can be from 0 to 9.
Examples Example 1 The following example changes the value of the operator-defined code to 123456: connection_code “123456” Where:
is: 123456
68P02901W23-S
the operator-defined code.
3-177 Nov 2009
Examples
Chapter 3: Device/function related commands
System response COMMAND ACCEPTED
Example 2 The following example turns off the Call Connectivity Trace feature: connection_code ””
System response COMMAND ACCEPTED
Example 3 The following example displays the current value for the operator-defined code: connection_code
System response Connection code is: 123456
NOTE If there is no connection code, the system response is: ‘No Connection code exists’.
3-178
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
copy_cell
copy_cell ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The copy_cell command creates a cell by copying the information in an existing cell. This command cannot copy a cell source or neighbor information. Also, the cell BSIC is not copied and a new BSIC must be entered for the cell being created (destination cell). If dynamic allocation is in use at the source cell, the system sets the value of the dynet_tchs_reserved parameter to the default (0), regardless of the setting in the source cell. The value of dynet_tchs_reserved does not change at the source cell. The value of the dynet_tchs_reserved parameter at the destination cell is always defaulted to 0. This command is rejected if it is entered for an M-Cellcity, Horizonmicro or Horizoncompact site where a cell exists. Only one cell is permitted at these sites. An extended source cell is copied as an extended destination cell. If used on a coincident cell, the copy_cell command sets the coincident cell to an invalid value, and the coincident_mb to 0 at the new cell. Security level
4
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
None
Operator actions
Respond to the warning prompt presented when this command is entered.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help
Format Syntax copy_cell [“cell_name”]
68P02901W23-S
3-179 Nov 2009
Format
Chapter 3: Device/function related commands
Input parameters source_cell_id GSM cell ID of the existing cell being copied. The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900, or GSM850).
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
The cell name created using the cell_name command is entered in place of the source_cell_id. When the cell name is entered, it must be placed inside double quotation marks. dest_gsm_cell_id GSM cell ID of the new cell to be created. A cell name is not entered for the destination Cell ID. The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900, or GSM850).
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
dest_location Specifies the location of the new cell. Values are: 0 or bsc
BSC
1 - 140
BTS
dest_bsic Specifies the BSIC of the new cell. The range of values for the bsic is 0 - 63. cell_name A cell name can be specified for the dest_gsm_cell_id, as if created using the cell_name command. This cell name must be placed inside double quotation marks. The full format is given in the cell_name parameter description.
Inclusions The following parameters are copied when the copy_cell command is executed:
3-180
alt_qual_proc
en_incom_ho
ms_txpwr_max_cch
attach_detach
extended_paging_active
ms_txpwr_max_def
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
ba_alloc_proc
frequency_type
mspwr_alg
bs_ag_blks_res
full_pwr_rfloss
ncc_of_plmn_allowed
bs_pa_mfrms
gprs_par_wait_ind
new_calls_hr
bep_period
handover_power_level
number_of_preferred_cells
bep_period2
handover_recognized_period
number_sdcchs_preferred
bsic
ho_margin_def
penalty_time
bts_p_con_ack
hr_fr_hop_count
pfc_be_arp
bts_p_con_interval
hr_intracell_ho_allowed
pow_inc_step_size_dl
bts_power_control_allowed
hr_res_ts
ccch_conf
imrm_dcs1800_weight
pow_red_step_size_dl
cell_bar_access_class
imrm_egsm_weight
pow_inc_step_size_ul
cell_bar_access_switch
imrm_force_recalc
pwr_handover_allowed
cell_bar_qualify
imrm_pgsm_weight
pwrc
cell_reselect_hysteresis
imrm_umts_weight
qos_mtbr_be_dl
cell_reselect_offset
inner_hr_usage_thres
qos_mtbr_be_ul
cell_reselect_param_ind
intave
qos_mtbr_bg_dl
decision_1_dl_rxlev_av_h
inter_cell_handover_allowed
qos_mtbr_bg_ul
decision_1_dl_rxlev_av_ih
interfer_ho_allowed
qos_mtbr_i1_dl
decision_1_dl_rxlev_av_p
intr_cell_handover_allowed
qos_mtbr_i1_ul
decision_1_dl_rxqual_av_h
l_rxlev_dl_h
qos_mtbr_i2_dl
decision_1_dl_rxqual_av_p
l_rxlev_dl_p
qos_mtbr_i2_ul
decision_1_n1
l_rxlev_ul_h
qos_mtbr_i3_dl
decision_1_n2
l_rxlev_ul_p
qos_mtbr_i3_ul
decision_1_n3
l_rxqual_dl_h
radio_link_timeout
decision_1_n4
l_rxqual_dl_h_hopping_hr
rapid_pwr_down
decision_1_n5
l_rxqual_dl_h_hr
reconfig_fr_to_hr
decision_1_n6
l_rxqual_dl_p
decision_1_n7
l_rxqual_dl_p_hopping_hr
reestablish_allowed
decision_1_n8
l_rxqual_dl_p_hr
report_resource_tch_f_high_ water_mark
decision_1_ncell_rxlev_ av_h_calc
l_rxqual_ul_h
report_resource_tch_f_low_ water_mark
decision_1_p_bgt_rxlev_av_h l_rxqual_ul_h_hopping_hr
rpd_offset
decision_1_p1
l_rxqual_ul_h_hr
rpd_period
decision_1_p2
l_rxqual_ul_p
rpd_trigger
68P02901W23-S
3-181 Nov 2009
Format
3-182
Chapter 3: Device/function related commands
decision_1_p3
l_rxqual_ul_p_hopping_hr
rxlev_access_min
decision_1_p4
l_rxqual_ul_p_hr
rxlev_min_def
decision_1_p5
l_rxqual_ul_p_amr_fr
sdcch_ho
decision_1_p6
l_rxqual_dl_p_amr_fr
ms_txpwr_max_cch
decision_1_p7
en_incom_ho
ms_txpwr_max_def
alt_qual_proc
extended_paging_active
mspwr_alg
attach_detach
frequency_type
ncc_of_plmn_allowed
ba_alloc_proc
full_pwr_rfloss
new_calls_hr
bs_ag_blks_res
gprs_par_wait_ind
number_of_preferred_cells
bs_pa_mfrms
handover_power_level
number_sdcchs_preferred
bep_period
handover_recognized_period
penalty_time
bep_period2
ho_margin_def
pfc_be_arp
bsic
hr_fr_hop_count
pow_inc_step_size_dl
bts_p_con_ack
hr_intracell_ho_allowed
pow_red_step_size_dl
bts_p_con_interval
hr_res_ts
pow_inc_step_size_ul
bts_power_control_allowed
imrm_dcs1800_weight
pwr_handover_allowed
ccch_conf
imrm_egsm_weight
pwrc
cell_bar_access_class
imrm_force_recalc
qos_mtbr_be_dl
cell_bar_access_switch
imrm_pgsm_weight
qos_mtbr_be_ul
cell_bar_qualify
imrm_umts_weight
qos_mtbr_bg_dl
cell_reselect_hysteresis
inner_hr_usage_thres
qos_mtbr_bg_ul
cell_reselect_offset
intave
qos_mtbr_i1_dl
cell_reselect_param_ind
inter_cell_handover_allowed
qos_mtbr_i1_ul
decision_1_dl_rxlev_av_h
interfer_ho_allowed
qos_mtbr_i2_dl
decision_1_dl_rxlev_av_ih
intr_cell_handover_allowed
qos_mtbr_i2_ul
decision_1_dl_rxlev_av_p
l_rxlev_dl_h
qos_mtbr_i3_dl
decision_1_dl_rxqual_av_h
l_rxlev_dl_p
qos_mtbr_i3_ul
decision_1_dl_rxqual_av_p
l_rxlev_ul_h
radio_link_timeout
decision_1_n1
l_rxlev_ul_p
rapid_pwr_down
decision_1_n2
l_rxqual_dl_h
reconfig_fr_to_hr
decision_1_n3
l_rxqual_dl_h_hopping_hr
reestablish_allowed
decision_1_n4
l_rxqual_dl_h_hr
report_resource_tch_f_high_ water_mark
decision_1_n5
l_rxqual_dl_p
report_resource_tch_f_low_ water_mark
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
decision_1_n6
l_rxqual_dl_p_hopping_hr
rpd_offset
decision_1_n7
l_rxqual_dl_p_hr
rpd_period
decision_1_n8
l_rxqual_ul_h
rpd_trigger
decision_1_ncell_rxlev_ av_h_calc
l_rxqual_ul_h_hopping_hr
rxlev_access_min
decision_1_p_bgt_rxlev_av_h l_rxqual_ul_h_hr
rxlev_min_def
decision_1_p1
l_rxqual_ul_p
sdcch_ho
decision_1_p2
l_rxqual_ul_p_hopping_hr
sdcch_timer_ho
decision_1_p3
l_rxqual_ul_p_hr
temporary_offset
decision_1_p4
l_rxqual_ul_p_amr_fr
timing_advance_period
decision_1_p5
l_rxqual_dl_p_amr_fr
tlli_blk_coding
decision_1_p6
l_rxqual_ul_h_amr_fr
tx_integer
decision_1_p7
l_rxqual_dl_h_amr_fr
u_rxlev_dl_ih
decision_1_p8
l_rxqual_dl_h_hopping_amr_fr u_rxlev_dl_p
decision_1_tim_adv_av_alg
l_rxqual_ul_h_hopping_amr_fr ul_rxlev_ho_allowed
decision_1_ul_rxlev_av_h
l_rxqual_dl_p_hopping_amr_fr u_rxlev_ul_ih
decision_1_ul_rxlev_av_ih
l_rxqual_ul_p_hopping_amr_fr u_rxlev_ul_p
decision_1_ul_rxlev_av_p
link_about_to_fail
u_rxqual_dl_p
decision_1_ul_rxqual_av_h
link_fail
ul_rxqual_ho_allowed
decision_1_ul_rxqual_av_p
max_retran
u_rxqual_ul_p
dl_rxlev_ho_allowed
max_tx_bts
u_rxqual_dl_p_hr
dl_rxqual_ho_allowed
max_tx_ms
u_rxqual_ul_p_hr
dtx_required
missing_rpt
wait_indication_parameters
dyn_step_adj
ms_distance_allowed
dyn_step_adj_fmpr
ms_p_con_ack
egprs_init_dl_cs
ms_p_con_interval
egprs_init_ul_cs
ms_power_control_allowed
emergency_class_switch {26811} ext_ul_no_dat
NOTE If the Inter-RAT handover option is unrestricted, and UTRAN cells are copied with copy_cell, the following parameters are defaulted in the new cell: fdd_qmin, fdd_qoffset, qsearch_c_initial, qsearch_i, and inter_rat_enabled.
68P02901W23-S
3-183 Nov 2009
Examples
Chapter 3: Device/function related commands
Exceptions The following is a list of parameters that are not copied, and instead the parameter default values are used when the copy_cell command is executed: bsic
fdd_multirat_reporting
res_ts_less_one_carrier
bcch_frequency
fdd_rep_quant
source_cells
freq_share_table_pointer
sw_ts_less_one_carrier
blind_search_preference
gsm_cell_id
serving_band_reporting
cbch_enabled
gsm_half_rate_enabled
switch_gprs_pdchs
cell_name
hopping_support
tch_usage_threshold
coincident_index
inner_zone_alg
thresholds
coincident_mb
inter_rat_enable
tx_power_cap
dynet_tchs_reserved
ms_max_range
trx_pwr_carriers.num_carriers
equipment_share_table_pointer multiband_reporting
umts_band_preferred
ext_range_cell
umts_cpich_ec_no_min
qsearch_c
umts_cpich_rscp_min The neighbor definitions also are not copied. If the GPRS feature is unrestricted, the copy_cell command copies the GPRS elements at a cell, except for the following: bvci
ra_colour
gprs_enabled
Examples Example 1 In this example, information from a cell with cell_number=5 4 3 2 1 61986 34944 is copied to create a cell with cell_number=5 4 3 2 1 61986 34945 at site 0: copy_cell 5 4 3 2 1 61986 34944 5 4 3 2 1 61986 34945 0 6 Where:
is: 5 4 3 2 1 61986 34944
source_cell_id
5 4 3 2 1 61986 34945
dest_gsm_cell_id
0
dest_location
6
dest_bsic
System response COMMAND ACCEPTED
3-184
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 2 In this example, the source cell is identified using the cell_name ‘london-south’. copy_cell “london-south” 5 4 3 2 1 61986 34945 0 6 Where:
is: ‘london-south’
cell_name
5 4 3 2 1 61986 34945
dest_gsm_cell_id
0
dest_location
6
dest_bsic
System response COMMAND ACCEPTED
Example 3 In this example, information from a PCS1900 cell with cell_number=543 721 61986 34944 is copied to create a cell with cell_number=543 721 61986 34945 at site 0, with the cell name of ‘paris’: copy_cell 543 721 61986 34944 543 721 61986 34945 0 6 “paris” Where:
is: 543 721 61986 34944
source_cell_id
543 721 61986 34945
dest_gsm_cell_id
0
dest_location
6
dest_bsic
‘paris’
cell_name
System response COMMAND ACCEPTED
68P02901W23-S
3-185 Nov 2009
References
Chapter 3: Device/function related commands
Example 4 In this example, gsm_half_rate_enabled is set to 1 in the source cell and a new cell is created using the command copy_cell. copy_cell 0 0 1 0 1 1 3 0 0 1 0 1 1 44 2 7 Where:
is: 0010113
source_cell_id
0 0 1 0 1 1 44
dest_gsm_cell_id
2
dest_location
7
dest_bsic
System response COMMAND ACCEPTED: WARNING: The GSM half rate per cell enable parameter has been modified
References Related information The GSM cell ID entry format is: a b c d e f g Where:
is: a
the first digit of the MCC (Mobile Country Code).
b
the second digit of the MCC.
c
the third digit of the MCC.
d
the first digit of the MNC (Mobile Network Code).
e
the second digit of the MNC.
f
the LAC (Local Area Code).
g
the CI (Cell Identity).
Related commands add_cell on page 3-22
3-186
del_cell on page 3-192
disp_cell on page 3-241
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
copy_path
copy_path ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The copy_path command equips a new PATH device by copying an existing path and extending it to a new site. This facility is useful when adding paths to the network or creating a long branch. The first path to the first BTS can be configured when a path is created using the equip command. This path can be copied or extended to the next BTS. The process can then be repeated to construct paths to all BTS sites on the branch. This command ensures that an HDSL link is only copied between MMSs that support the same number of timeslots, identical link protocol types and HDSL modems that are in a master/slave configuration. The single exception to this rule is when the system cannot check master/slave settings because the HDSL link consists of two external modems. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax copy_path
Input parameters There are no input parameters since this command is interactive. Table 3-31 lists the prompts and values that must be entered.
68P02901W23-S
3-187 Nov 2009
Example
Chapter 3: Device/function related commands
Table 3-31
copy_path command prompts Prompt
Enter the terminating SITE id to be copied: Enter the Unique PATH id to be copied:
Range
Default
0 - 140
None
0 - 9 6 - 9 (see NOTE)
None
NOTE If the terminating BTS uses dynamic allocation, the range is 6 - 9. If the terminating BTS does not use dynamic allocation, the range is 0 - 9. 0 - 140
None
Enter the unique PATH id:
0 - 9
None
Enter the downstream MSI identifier:
0 - 9
None
Enter the downstream MMS identifier:
0 or 1
None
Enter the upstream MSI identifier:
0 - 9
None
Enter the upstream MMS identifier:
0 or 1
None
Enter the new terminating site id:
Example This example shows a typical dialogue. copy_path
System response Enter the terminating SITE id to be copied: 4 Enter the Unique PATH id to be copied: 0 Enter the new terminating SITE id: 5 Enter the new Unique PATH id: 0 Enter the downstream MSI identifier: 3 Enter the downstream MMS identifier: 0 Enter the upstream MSI identifier: 3 Enter the upstream MMS identifier: 1 COMMAND ACCEPTED
3-188
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
References Related information The following figure illustrates that ‘downstream’ always refers to the direction from the BSC to the BTS. The ‘upstream’ always describes the direction from the BTS to the BSC.
Related commands add_rtf_path on page 3-50
chg_rtf_freq on page 3-144
del_rtf_path on page 3-204
disp_rtf_path on page 3-381
68P02901W23-S
3-189 Nov 2009
del_act_alarm
Chapter 3: Device/function related commands
del_act_alarm ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The del_act_alarm command deletes an alarm that an active operator can clear.
NOTE The disp_act_alarm command displays the alarms that the operator can delete. See disp_act_alarm on page 3-225.
Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
Format Syntax del_act_alarm
Input parameters location Specifies the alarm location:
3-190
0 or bsc
BSC
1 - 140
BTS
{27955A} pcu or pcu_0
PCU
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Example
device_name Device name that uniquely identifies the device. dev_id1 First device identifier. The range of values is 1 - 128. dev_id2 Second device identifier. The range of values is 0 - 99. dev_id3 Third device identifier. The range of values is 0 - 99. alarm_code Alarm to be deleted. The range of values is 0 - 254.
Example This example deletes an active alarm for KSW 1 0 0, alarm code 2, at the BSC. del_act_alarm 0 ksw 1 0 0 2 Where:
is: 0
location
ksw
device_name
1
dev_id1
0
dev_id2
0
dev_id3
2
alarm_code
System response COMMAND ACCEPTED
References Related commands disp_act_alarm on page 3-225.
68P02901W23-S
3-191 Nov 2009
del_cell
Chapter 3: Device/function related commands
del_cell ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The del_cell command deletes a cell from the CM database. The del_cell command is rejected if the cell specified for deletion is a coincident cell of any other cell at a site that has the Coincident Multiband Handover option enabled. The command is also rejected if any Trace Criteria is with scope as the specified cell. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
If a cell is currently in a DRI descriptor, it cannot be removed. To remove a cell that is included in a DRI descriptor, the DRI must be unequipped first. All trace criteria with scope as the specified cell must be deleted.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax del_cell
Input parameter cell_id GSM cell ID of the cell to be deleted. The format for the GSM cell ID depends on:
3-192
•
The system being used (PGSM, EGSM, DCS1800, PCS1900)
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
The name of the cell created using the cell_name command is entered in place of the cell_id. When the cell name is entered, it must be placed inside double quotation marks.
Examples Example 1 In this example, the cell with cell_number 5 4 3 2 1 61986 34944 (using the seven parameter format) at site number 0 is deleted from the CM database: del_cell 5 4 3 2 1 61986 34944 Where:
is: 5 4 3 2 1 61986 34944
cell_id
System response COMMAND ACCEPTED
Example 2 In this example, the cell with cell_number 987 654 12345 67809 (using the four parameter format) at site number 0 is deleted from the CM database: del_cell 987 654 12345 67809 Where:
is: 987 654 12345 67809
cell_id
System response COMMAND ACCEPTED
Example 3 In this example, the affected cell is identified using the cell_name ‘london-south’. del_cell “london-south” Where:
is: ‘london-south’
68P02901W23-S
cell_name
3-193 Nov 2009
References
Chapter 3: Device/function related commands
System response COMMAND ACCEPTED
Example 4 In this example, an attempt is made to delete cell 5 4 3 2 1 61986 34944 which has trace criteria with scope as the specified cell. del_cell 5 4 3 2 1 61986 34944 Where:
is: 5 4 3 2 1 61986 34944
cell_id
System response COMMAND REJECTED: Delete all Trace Criteria with scope as the specified cell/RTF/site.
References Related commands add_cell on page 3-22
copy_cell on page 3-179
disp_cell on page 3-241
disp_gsm_cells on page 3-314
3-194
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
del_conn
del_conn ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The del_conn command updates the BSS database to delete a particular connection between an MMS at the BSC and an MMS at the RXCDR. If the BSC is operating in static mode and CICs are statically assigned to that MMS pair, connectivity cannot be removed for an MMS pair. This only applies to remote transcoding BSC and RXCDR sites. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
All CICs and XBLs must be unequipped before deleting MMS connectivity information. This command can only be entered at the BSC or RXCDR site.
Format Syntax del_conn
Input parameters local_mms_id_1 First identifier of the MMS at the local site. The term ‘local site’ refers to the site where the command is entered. The range of values vary from {22169} 0 - 95 when this command is executed from a BSC. The range varies from 0 to 123 when executed from an RXCDR. local_mms_id_2 Second identifier of the MMS at the local site. Values are 0 or 1.
68P02901W23-S
3-195 Nov 2009
Example
Chapter 3: Device/function related commands
Example This example shows connectivity information deleted for MMS 4 0 at the BSC. del_conn 4 0 Where:
is: 4
local_mms_id_1
0
local_mms_id_2
System response COMMAND ACCEPTED
References Related commands add_conn on page 3-33
3-196
disp_conn on page 3-261
mod_conn on page 3-442
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
del_neighbor
del_neighbor ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The del_neighbor command deletes neighbor cells, including Blind Search Neighbors, from a cell neighbor list. If two Cell IDs are entered, the second Cell ID is removed from the first cell neighbor list. If all is entered in place of the second cell ID, then every neighbor in the specified cell neighbor list is deleted. If all is entered in place of the first Cell ID, then the cell is deleted from all associated neighbor lists. If the Inter_RAT (Radio Access Technology) Handover feature and/or the Enhanced 2G/3G Handover feature is unrestricted, this command supports the UTRAN cell identity format.
NOTE If all is entered for a BTS at which the Coincident MultiBand Handover option is enabled, and contains any coincident cells, the command is rejected.
Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
To be on a Neighbor Cell List, a cell must be the destination of handovers from the Neighbor List owner. For handovers to UTRAN cells, the Inter-RAT Handover feature and/or the Enhanced 2G/3G Handover feature must be unrestricted. The specified UMTS cell identifier must exist as a neighbor cell of the GSM source cell. The GSM source cell must exist.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
68P02901W23-S
3-197 Nov 2009
Format
Chapter 3: Device/function related commands
Format Syntax del_neighbor [] [] del_neighbor all del_neighbor all
Input parameters source_cell_id GSM or UTRAN Cell ID of the Neighbor List owner. GSM cell ID of the Neighbor List owner. The format for the GSM cell ID depends on: •
The system being used (PGSM, EGSM, DCS1800, PCS1900)
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
The name of the cell created using the cell_name command is entered in place of the cell_id. When the cell name is entered, it must be placed inside double quotation marks.
NOTE A cell_name cannot be associated with a UMTS neighbor.
neighbor_cell_id GSM or UTRAN Cell ID of the cell specified to be removed from the Neighbor List. GSM cell ID of the cell specified to be removed from the Neighbor List. This attribute is NOT allowed for Blind Search neighbors. The format for the GSM cell ID depends on: •
The system being used (PGSM, EGSM, DCS1800, PCS1900)
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
The name of the cell created using the cell_name command is entered in place of the cell_id. When the cell name is entered, it must be placed inside double quotation marks. The string test is entered for this field where is a value from 1 to 64. This permits test neighbors to be removed from the BA_SACCH and/or BA_BCCH lists. placement
3-198
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Defines the placement type where umts_fdd_blind specifies that the neighbor is a Blind Search neighbor. This parameter is not allowed if the Enhanced 2G/3G Handover feature is restricted. FDD-ARFCN Specifies the FDD-ARFCN of the neighbor to be deleted. This parameter is not allowed if the Enhanced 2G/3G Handover feature is restricted. all This syntax removes all neighbor cells from the source cell neighbor list. all This syntax removes the neighbor cell from all source cell neighbor lists.
Examples Example 1 In this example, cell_id 5 4 3 2 1 61986 34945 is removed from the neighbor list of cell_id 5 4 3 2 161986 34944: del_neighbor 5 4 3 2 1 61986 34944 5 4 3 2 1 61986 34945 Where:
is: 5 4 3 2 1 61986 34944
source_cell_id
5 4 3 2 1 61986 34945
neighbor_cell_id
System response COMMAND ACCEPTED
Example 2 In this example, all neighbor cells are removed from the neighbor list of cell_id 5 4 3 2 1 61986 34944: del_neighbor 5 4 3 2 1 61986 34944 all Where:
68P02901W23-S
is: 5 4 3 2 1 61986 34944
source_cell_id
all
neighbor_cell_id
3-199 Nov 2009
Examples
Chapter 3: Device/function related commands
System response COMMAND ACCEPTED
Example 3 In this example, cell_id 5 4 3 2 1 61986 34944 is removed from all neighbor lists: del_neighbor all 5 4 3 2 1 61986 34944 Where:
is: all
source_cell_id
5 4 3 2 1 61986 34944
neighbor_cell_id
System response COMMAND ACCEPTED
Example 4 In this example, cell_id 987 654 12345 34567 (using the four parameter format) is removed from all neighbor lists: del_neighbor all 987 654 12345 34567 Where:
is: all
source_cell_id
987 654 12345 34567
neighbor_cell_id
System response COMMAND ACCEPTED
Example 5 In this example, FDD-ARFCN cell ID 10762 is removed from the neighbor list of source cell ID 0 0 1 0 1 1 4. where 10762 is the last blind search neighbor of this cell and blind search preference is on. del_neighbor 0 0 1 0 1 1 4 umts_fdd_blind 10762 Where:
3-200
is: 0010114
source_cell_id
10762
FDD-ARFCN
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
System response COMMAND ACCEPTED WARNING: The last Blind Search neighbor has been deleted for this cell.
References Related commands add_cell on page 3-22
add_neighbor on page 3-35
copy_cell on page 3-179
del_cell on page 3-192
disp_cell on page 3-241
disp_gsm_cells on page 3-314
disp_neighbor on page 3-343
68P02901W23-S
3-201 Nov 2009
del_nsvc
Chapter 3: Device/function related commands
del_nsvc ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The del_nsvc command enables the operator to remove one or more mappings between a Network Service-Virtual Connection Identifier (NSVCI), Data Link Connection Identifier (DLCI) and a GBL at a specific PCU. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
The GPRS feature must be unrestricted.
Format Syntax del_nsvc [ ...
]
Input parameters: pcu_id {27955A} Specifies the specific PCU, as pcu or pcu_0. ns_vci_1 Specifies the unique identifier of the first NSVCI mapping and identifier of the object. Range = 0 - 65535. ns_vci_2 ...
ns_vci_8
Specifies the unique identifiers of subsequent NSVCI mapping and the objects (up to 8). Range= 0 - 65535.
3-202
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Example
Example The following example deletes NSVCI 580 at the first equipped PCU. del_nsvc pcu_0 580 Where:
is: pcu_0
PCU identifier (first equipped)
580
NSVC identifier
System response: COMMAND ACCEPTED
References Related commands add_nsvc on page 3-48
68P02901W23-S
mod_nsvc on page 3-445
3-203 Nov 2009
del_rtf_path
Chapter 3: Device/function related commands
del_rtf_path ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The del_rtf_path command deletes a redundant PATH device from an equipped RTF function in the Configuration Management (CM) database. The system rejects attempts to modify the PATHs used by RTFs at sites that use dynamic allocation. RTFs automatically use the PATHs defined for these types of sites. RTFs do not use PATHs equipped by the operator for these types of sites. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax del_rtf_path
Input parameters location The number of the BTS where the RTF is located. The range of values is 0 - 140. 1st_RTF_identifier The first RTF identifier from which the path is removed. The range of values is 0 - 5. 2nd_RTF_identifier The second RTF identifier from which the path is removed. The range of values is 0 - 11. unique_PATH_identifier The unique PATH to be removed. The range of values is 0 - 9.
3-204
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Example
Example This example deletes a redundant RTF PATH from site 36, RTF identifiers 5 20, unique PATH identifier 8. del_rtf_path 36 5 20 8 Where:
is: 36
location
5
1st_RTF_identifier
20
2nd_RTF_identifier
8
unique_PATH_identifier
System response This may reduce the number of Traffic Channels available. Are you sure? (y=yes, n=no)?y COMMAND ACCEPTED
References Related information If a redundant path does not exist, the command is rejected. When deleting a redundant path, the path is automatically switched over to the remaining paths.
Related commands add_rtf_path on page 3-50
chg_rtf_freq on page 3-144
disp_rtf_path on page 3-381
copy_path on page 3-187
68P02901W23-S
3-205 Nov 2009
del_smscb_msg
Chapter 3: Device/function related commands
del_smscb_msg ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The del_smscb_msg command deletes the CBCH background message. This command is used to delete: •
A single message at a single cell.
•
A single message at all cells in the BSS.
•
All messages at a single cell.
•
All messages at all cells in the BSS.
Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Format Syntax del_smscb_msg
Input parameters msg_num A number that uniquely identifies the message to be deleted. The value all is also a valid input for the msg_num to specify all messages at the specified cells.
3-206
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
cell_desc This parameter is the GSM cell ID of the cell at which messages are to be deleted, preceded by cell_number=. The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900)
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks, and cell_name=. must precede it.
NOTE This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. The value all is also a valid input for the cell_desc, to delete the specified messages at all cells at the BSS.
Examples Example 1 This example deletes CBCH background message number 4 for cell_number=5 4 3 2 1 61986 34944. del_smscb_msg 3 cell_number=5 4 3 2 1 61986 34944 Where:
is: 3
msg_num
cell_number=5 4 3 2 1 61986 34944
cell_desc
System response COMMAND ACCEPTED
68P02901W23-S
3-207 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 2 This example deletes all CBCH background messages for all cells. del_smscb_msg all all Where:
is: all
all background messages
all
cell_desc (all cells)
System response COMMAND ACCEPTED
Example 3 In this example, the affected cell is identified using the cell_name ‘london-south’. del_smscb_msg 3 cell_name=”london-south” Where:
is: 3
msg_num
cell_name=‘london-south’
cell_desc
System response COMMAND ACCEPTED
Example 4 This example deletes CBCH background message number 4 for cell_number=987 654 13579 24689 (using the four parameter format). del_smscb_msg 3 cell_number=987 654 13579 24689 Where:
is: 3
msg_num
cell_number=987 654 13579 24689
cell_desc
System response COMMAND ACCEPTED
3-208
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
References Related commands chg_smscb_msg on page 3-150
68P02901W23-S
disp_cbch_state on page 3-237
3-209 Nov 2009
device_audit
Chapter 3: Device/function related commands
device_audit ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The device_audit command suspends or resumes audits at a specific site. This command is also used to execute a specific test on a specific device. The device_audit supports display of swap_type on the TDM device at location 0 (BSC or RXCDR). When this command is used to execute an audit at the BSC for an RXCDR that is in the BUSY-UNLOCKED state, the BSC performs an audit. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator action)
Prerequisites
This command is not allowed while in SYSGEN ON mode. The operator at the OMC-R must rlogin to a site before an audit can be performed.
Format Syntax device_audit device_audit
Input parameters location Specifies the audit location:
3-210
0 or bsc
BSC
1 - 140
BTS
{27955A} pcu or pcu_0
PCU
pcu_1
Specifies the PCU site 1.
pcu_2
Specifies the PCU site 2.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
control Site audit status: on
Resumes all site audits within a cage at a specific site.
off
Suspends all site audits within a cage at a specific site.
audit_type Type of audit: Specifies the type of audit:
0
All audits
1
Safe audits
2
Internal loopback audit
3
Self audits
4
Swap_test
NOTE •
If all is entered as the control parameter value, multiple devices can be audited. The format for each of the additional devices is the same as it is for the first device.
•
{25002} The SWAP_TEST audit only applies to the expanded cage. The SWAP_TEST audit is done at 2:50 every day.
device_name Name that uniquely identifies the device. Not all devices can be audited at all site types. It is only possible to audit the device that are equipped at the site. Given these conditions, the following devices can be audited with this command: BSP
GPROC
SBUS
BTP
KSW
TDM
DHP
MSI
AXCDR
DRI
RXCDR
The following devices can be audited at M-Cell sites using this command: BTP
DRI
MSI
The following devices can be audited at PCU using this command: MSI
68P02901W23-S
DPROC
PSP
3-211 Nov 2009
Examples
Chapter 3: Device/function related commands
device_id1 First device identifier. Identifier value is dependent upon the device. device_id2 Second device identifier. Identifier value is dependent upon the device. device_id3 Third device identifier. Identifier value is dependent upon the device.
Examples Example 1 The following example executes the safe audits for KSW device ID 0 0 0: device_audit bsc safe ksw 0 0 0 Where:
is: bsc
location
safe
audit_type
ksw
device_name
0
device_id1
0
device_id2
0
device_id3
System response Device: KSW Year:1994
Device id: 0 0 0 Month:11
Audit Type: SAFE
3-212
Day:12
Hour:0
Min:26
Sec:29
MSec:665
Result: PASS
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 2 The following example suspends audits for a KSW device with ID 1 0 0 at site 4: device_audit 4 off ksw 1 0 0 Where:
is: 4
location
off
control
ksw
device_name
1
device_id1
0
device_id2
0
device_id3
System response COMMAND ACCEPTED If audits for the device is already turned off, the response is: COMMAND REJECTED: Audits already turned off for this device.
Example 3 The following example resumes audits for a KSW device with ID 1 0 0 at site 4: device_audit 4 on KSW 1 0 0 Where:
is: 4
location
on
control
ksw
device_name
1
device_id1
0
device_id2
0
device_id3
System response COMMAND ACCEPTED
68P02901W23-S
3-213 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 4 The following example performs a device audit at RXCDR 14 where CIC mismatches are found: device_audit 0 all RXCDR 14 Where:
is: 0
location
all
audit_type
RXCDR
device_name
14
device_id1
System response Device: MSI Device id: 2 0 0 Year:1999
Month:1
Day:22
Audit Type: SAFE
Hour:17
Min:56
Sec:12
MSec:470
Result: PASS
Example 5 {26740} The following example performs a device audit to execute a safe audit on a PSI device. device_audit 1 safe PSI 1 0 Where:
is: 1
location
safe
audit_type
PSI
device_name
1
device_id1
0
device_id2
System response Device: PSI Device id: 1 0 0 Year: 1999 Month: 1 Day: 22 Audit Type: SAFE
3-214
Hour: 17
Min: 56
Sec: 12
MSec: 470
Result: PASS
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 6 {25002} The following example executes audits for the swap_test device ID 1. device_audit 0 swap_test tdm 1 Where:
is: 0
location
swap_test
audit_type
tdm
device_name
1
device_id1
System Response WARNING: The Swap_test audit will take about 2 minutes. Are you sure (y=yes,n=no)? yes Device: TDM Year: 2007
Device id: 1 0 0 Month: 1
Day: 30
Audit Type: SWAP_TEST
Hour: 15
Min: 0
Sec: 44
MSec: 0
Result: PASS
Example 7 {25002} The following example attempts to execute the audits for the swap_test device. device_audit 0 swap_test tdm 0 Where:
is: 0
location
swap_test
audit_type
tdm
device_name
0
device_id1
System response WARNING: The Swap_test audit will take about 2 minutes. Are you sure (y=yes,n=no)? yes Device: TDM Year: 2007
Device id: 0 0 0 Month: 1
Audit Type: SWAP_TEST
68P02901W23-S
Day: 30
Hour: 15
Min: 0
Sec: 15
MSec: 665
Result: ERROR
3-215 Nov 2009
References
Chapter 3: Device/function related commands
Example 8 {25002} In this example, device audit cannot be executed on the standby TDM bus. device_audit 0 all tdm 1 Where:
is: 0
location
all
audit_type
tdm
device_name
1
device_id1
System response WARNING: Both Safe audit and Swap_test audit will be executed.It will take about 2 minutes. Are you sure (y=yes,n=no)? yes Device: TDM Year: 2007
Device id: 1 0 0 Month: 6
Day: 21
Audit Type: SAFE
Hour: 16
Min: 54
Sec: 13
MSec: 800
Sec: 13
MSec: 800
Result: ERROR
ERROR: Device not in auditable state Device: TDM Year: 2007
Device id: 1 0 0 Month: 6
Audit Type: SWAP_TEST
Day: 21
Hour: 16
Min: 54
Result: ERROR
ERROR: Device not in auditable state.
References Related commands cage_audit on page 3-58
chg_audit_sched on page 3-76
query_audits on page 3-472
site_audit on page 3-507
3-216
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
diagnose_device
diagnose_device ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The diagnose_device command performs the specified diagnostic on the specified device. Security level
4
Supported by OMC-R GUI
No
Command type
B (operator actions required)
Prerequisites
This command is supported only in the SYSGEN OFF mode. For there to be free RTFs for DRI diagnostics, all standby DRIs must be locked before using this command. Only DRI devices at Horizonmacro sites are supported.
Operator actions
The operator must lock the DRI before using this command. The RTF cannot be in the active Mobile Allocation List.
Format Syntax diagnose_device
Input parameters location Specifies the device location: 1 - 140
BTS
device Specifies the ASCII device name. The only available device is the DRI. id0 Specifies the first identifier. The range is 0 - 255. id1 Specifies the second identifier. The range is 0 - 255. id2 Specifies the third identifier. The range is 0 - 255.
68P02901W23-S
3-217 Nov 2009
Examples
Chapter 3: Device/function related commands
Prompted parameter After specifying the input parameters, the operator is prompted for the type of diagnostic to be performed. The following types are available: Device
Diagnostic
DRI
rf_loopback vswr_test
Examples Example 1 In this example, the Receive Preamplifier Input Loopback test fails, but RCU Output Loopback passes (indicating a possible problem with the receive front end). diagnose_device 1 DRI 0 0 0
System response Diagnostic Type: rf_loopback REPORT FOR DRI 0 0 0 AT SITE 1 ------------------------------------------RELATED RTF:
RTF 0 0 0 (ARFCN 60)
RX preamp input loopback:
FAIL
RX preamp Input Loopback RXLEV (Branch 1): -128 dBm RX preamp Input Loopback RXLEV (Branch 2): -128 dBm RCU Output Loopback:
PASS
RCU Output Loopback RXLEV (Branch 1): 50 dBm RCU Output Loopback RXLEV (Branch 2): 50 dBm END OF REPORT
Example 2 In this example, the Receive Preamplifier Input Loopback test passes, indicating that the diagnostic passes (RCU Output Loopback is not run). diagnose_device 1 DRI 0 0 0
3-218
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response Diagnostic Type: rf_loopback REPORT FOR DRI 0 0 0 AT SITE 1 ------------------------------------------RELATED RTF:
RTF 0 0 0 (ARFCN 60)
RX Preamp input loopback:
PASS
RX preamp Input Loopback RXLEV (Branch 1): -50 dBm RX preamp Input Loopback RXLEV (Branch 2): -50 dBm RCU Output Loopback:
NOT RUN
RCU Output Loopback RXLEV (Branch 1): N/A RCU Output Loopback RXLEV (Branch 2): N/A END OF REPORT
Example 3 {27236} In this example, with the 4 branch diversity feature enabled, the Receive Preamplifier Input Loopback test and the RCU Output Loopback test passes, indicating that the diagnostic passes. diagnose_device 6 DRI 1 0 0
System response diagnose_device 6 DRI 0 0 0 Diagnostic Type: rf_loopback Report for DRI 1 0 0 at SITE 6 ------------------------------------------Related RTF:
RTF 1 0 0 (ARFCN 2)
RX Preamp Input Loopback (Branch 1):
PASS
RX Preamp Input Loopback (Branch 2):
PASS
RX Preamp Input Loopback (Branch 3):
PASS
RX Preamp Input Loopback (Branch 4):
PASS
RX Preamp Input Loopback RXLEV (Branch 1):
-74 dBm
RX Preamp Input Loopback RXLEV (Branch 2):
-74 dBm
RX Preamp Input Loopback RXLEV (Branch 3):
-74 dBm
68P02901W23-S
3-219 Nov 2009
Examples
Chapter 3: Device/function related commands
RX Preamp Input Loopback RXLEV (Branch 4):
-74 dBm
RCU Output Loopback (Branch 1):
PASS
RCU Output Loopback (Branch 2):
PASS
RCU Output Loopback (Branch 3):
PASS
RCU Output Loopback (Branch 4):
PASS
RCU Output Loopback RXLEV (Branch 1):
-75 dBm
RCU Output Loopback RXLEV (Branch 2):
-75 dBm
RCU Output Loopback RXLEV (Branch 3):
-75 dBm
RCU Output Loopback RXLEV (Branch 4):
-75 dBm
End of Report
3-220
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_a5_alg_pr
disp_a5_alg_pr ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_a5_alg_pr command displays the current list of prioritized encryption algorithms. Security level
1 {27508}
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
Format Syntax disp_a5_alg_pr
Input parameters There are no input parameters associated with this command.
Examples Example 1 This example shows the order in which two ciphering algorithms were used. disp_a5_alg_pr
System response Ciphering Algorithms are prioritized as follows: 2 1 0
Example 2 This example shows that no ciphering algorithms were used. disp_a5_alg_pr
68P02901W23-S
3-221 Nov 2009
References
Chapter 3: Device/function related commands
System response Ciphering Algorithms are prioritized as follows: 0
References Related commands chg_a5_alg_pr on page 3-73
3-222
page on page 3-470
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_acs
disp_acs ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_acs command displays the Active Codec Set and associated parameters. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
The AMR feature must be unrestricted. The site must be an AMR-capable BTS.
Format disp_acs
Input parameters cell_id GSM cell ID or cell name of the cell to be changed. The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900)
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
Only PCS1900 systems can use a three digit MNC. The name of the cell created using the cell_name command is entered in place of the Cell ID. When the cell name is entered, it must be placed inside double quotation marks. The Cell ID or the “cell_name” must be entered directly without any preceding qualifier.
NOTE This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition.
Example This example displays the codec modes for a given cell.
68P02901W23-S
3-223 Nov 2009
References
Chapter 3: Device/function related commands
disp_acs 4 9 6 0 1 1 1 Where:
is: 4960111
cell_id
System response AMR Full Rate active codec set:
0 1 3 6
AMR Full Rate initial codec mode:
1
AMR Full Rate uplink adaptation thresholds:
26 20 14
AMR Full Rate uplink adaptation hysteresis:
1 1 1
AMR Full Rate downlink adaptation thresholds:
30 24 19
AMR Full Rate downlink adaptation hysteresis:
1 1 1
AMR Full Rate uplink adaptation thresholds for frequency hopping:
26 20 14
AMR Full Rate uplink adaptation hysteresis for frequency hopping:
1 1 1
AMR Full Rate downlink adaptation thresholds for frequency hopping:
26 21 14
AMR Full Rate downlink adaptation hysteresis for frequency hopping:
1 1 1
AMR Half Rate active codec set:
3 5 6
AMR Half Rate initial codec mode:
5
AMR Half Rate uplink adaptation thresholds:
28 22
AMR Half Rate uplink adaptation hysteresis:
1 1
AMR Half Rate downlink adaptation thresholds:
30 24
AMR Half Rate downlink adaptation hysteresis:
1 1
AMR Half Rate uplink adaptation thresholds for frequency hopping:
28 22
AMR Half Rate uplink adaptation hysteresis for frequency hopping:
1 1
A MR Half Rate downlink adaptation thresholds for frequency hopping: AMR Half Rate downlink adaptation hysteresis for frequency hopping:
30 23 1 1
References Related command chg_acs_params on page 3-65
3-224
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_act_alarm
disp_act_alarm ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_act_alarm command displays the active Operator Initiated Clear (OIC) alarms and the active Fault Management Initiated Clear (FMIC) alarms only. Those alarms that have been designated as Intermittent do not appear in the active alarm list. Each device has an active alarm list limit of 200. If there are more than 200 active alarms on the device, only the first 200 are displayed and monitored. The number of alarms displayed after entering disp_act_alarm does not get affected. The output of this command displays up to 200 alarms for each device in the site. Security level
1
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
This command is not allowed while in SYSGEN ON mode.
Format Syntax disp_act_alarm [ ] disp_act_alarm
Input parameters location Specifies the alarm location: 0 or bsc
BSC
1 - 140
BTS
pcu or pcu_0
PCU
all
Specifies all sites.
68P02901W23-S
3-225 Nov 2009
Examples
Chapter 3: Device/function related commands
device_name Device name that uniquely identifies the device. dev_id1 First device identifier. The range of values is 0 to 99. dev_id2 Second device identifier. The range of values is 0 to 99. dev_id3 Third device identifier. The range of values is 0 to 99.
Examples Example 1 This example displays all active Operator Initiated Clear, and Fault Management alarms for DRI 1 0 0 at the BSC. The command does not show all active alarms, since any uncleared intermittent alarm is considered an active alarm, but it cannot appear on any list using the disp_act_alarm command: disp_act_alarm bsc dri 1 0 0 Where:
3-226
is: bsc
location
dri
device_name
1
dev_id1
0
dev_id2
0
dev_id3
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response COMMAND ACCEPTED Site: BSC Device
Alarm
Clear
Code
Type
Tag(hex)
Date/Time
Description
(Subtype) ---------------------------------------------------------------------
MMS 0 0 0
12
N
Bit Error Daily
(XCDR)
Threshold Exceeded
DRI 1 0 0
5
Y
MPH Error: Counter
(DRIM)
Mismatch: Uplink
DRI 1 0 0
1
N
Bad Host Message
(DRIM)
Example 2 This example displays the output when there are no active alarms at site 2. disp_act_alarm 2 Where:
is: 2
location
System response There are no active alarms at site 2.
68P02901W23-S
3-227 Nov 2009
References
Chapter 3: Device/function related commands
References Related information The following responses are received when the disp_act_alarm command is entered: There are no active alarms at site . There are no active alarms on that device. Unknown alarm device Unknown alarm code Error: Could not retrieve alarm description UNKNOWN INVALID CELL If the GPRS option is unrestricted the response is: There are no active alarms at the PCU.
3-228
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_bss
disp_bss ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_bss command displays specific status information for all sites in a BSS site. The BSS device identifier where the command is entered is included in the output. The status information shows the following: •
Sites that are equipped and their status.
•
Number of sectors, or 1 if the site is OMNI.
•
The GSM cell ID that is equipped for each site.
•
Broadcast Control Channel (BCCH) frequency for each of the cells.
The functional Unit Status shows the status of the BSC sites or of the associated cells. The possible values are: •
Critical - indicates a loss of service.
•
Major - indicates a loss of capacity.
•
Minor - indicates a loss of redundancy.
•
Clear - indicates normal operations.
Read the Functional Unit Status across the display. In the example, Site 0 is in Critical status. Cell 4, which is associated with Site 0 is in Clear status, and Cell 5 is in Critical status. If the GPRS feature is unrestricted, a line containing GPRS information appears in the output. {27955A} This includes the (pcu or pcu_0) PCU, if it is equipped, and values of the RAC and BVCI associated with each cell. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
This command is not allowed while in SYSGEN ON mode.
Format Syntax disp_bss
68P02901W23-S
3-229 Nov 2009
Example
Chapter 3: Device/function related commands
Input parameters There are no input parameters associated with this command.
Example This example shows the format of a typical output of the disp_bss command. disp_bss
System response OPER
STATES:
ADMIN STATES:
D:Disabled E:Enabled
B:Busy
L:Locked
E:Equipped
U:Unlocked
NE:Not Equipped S:Shutdown
Status for BSS 1: SITE SITE STATE
FU STATUS “LOSS OF”
GSM CELL id MCC MNC
LAC
CI
LCI RAC
FREQ
BCCH
TYPE
FREQ
---- ----- ------------- ----------------------------- --- ---- ------- -----0
B-U
PCU_0 B-U 1
2
3
D-U
B-U
D-U
Service Capacity UNAVAILABLE UNAVAILABLE
001 01
1 (0001h)
1 (0001h)
0
N/A
PGSM
26
UNAVAILABLE
001 01
1 (0001h)
6 (0006h)
1
4
PGSM
75
Capacity
001 01
1 (0001h)
3 (0001h)
2
4
PGSM
30
CLEAR
001 01
1 (0001h)
8 (0006h)
5
4
PGSM
31
001 01
1 (0001h)
33 (0001h)
3
4
PGSM
10
001 01
1 (0001h)
18 (0012h)
4
N/A
DCS1800 570
Capacity
UNAVAILABLE UNAVAILABLE
4
D-U
UNAVAILABLE UNAVAILABLE
References Related command assess on page 3-54.
3-230
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_bssgp_f_bmap
disp_bssgp_f_bmap ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_bssgp_f_bmap command prints out the database values and SGSN negotiated values of BSSGP features. It prints out values of bssgp_cbl_bit. If the QoS is unrestricted, the command also prints out values of bssgp_pfc_bit. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
The GPRS feature must be unrestricted. This command is only available at the BSC, when sysgen mode is off.
Format Syntax disp_bssgp_f_bmap
Input parameters Displays cell mapping at all equipped PCUs. Specifies the specific PCU, as pcu, pcu_0
Example disp_bssgp_f_bmap PCU_1 Where:
is: PCU_1
68P02901W23-S
PCU ID
3-231 Nov 2009
Example
Chapter 3: Device/function related commands
System response PCU Site 1: Feature-bit
DB value
Negotiated Value
CBL
0 (bssgp_cbl_bit)
0 (CBL feature at PCU disabled)
PFC
0 (bssgp_pfc_bit)
0 (QoS feature at PCU disabled)
END OF REPORT
3-232
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_cal_data
disp_cal_data ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_cal_data command displays the transceiver calibration data stored on the transceiver or in the BSC database on a per DRI basis. If the BSC and BTS are set for PGSM operation, 16 values are displayed. If the system is set so that the frequency_type parameter is EGSM, then all 22 values are displayed. The first six are for EGSM and the next 16 are for PGSM. Security level
1
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
This command is not allowed while in SYSGEN ON mode. This command is not available at an RXCDR.
Format Syntax disp_cal_data dri []
Input parameters location 0 or bsc
BSC
1 - 140
BTS
dri The DRI is the only device permitted for this command. dev_id1 The first device identifier. dev_id2 The second device identifier.
68P02901W23-S
3-233 Nov 2009
Example 1
Chapter 3: Device/function related commands
dev_id3 The third device identifier. This value defaults to 0 if no value is entered.
Example 1 The following example displays the calibration data for transceiver 5 3 0 at site 21: disp_cal_data 21 dri 5 3 0 Where:
is: 21
site
dri
dri device
5
first dev_id
3
second dev_id
0
third dev_id
System response DRI ID 5 3 0 Data read from transceiver Store Calibration Data: enabled Calibration data (All values in Hex): Transmit Power Offsets = 0 Receiver System Data:
Antenna Number
1 2
3 4 5 6
-------------------------------------------------f00,
1100, 114d, 1100, 1066, 1066,
10cd, 1100, 1033, 1100, 104d, 104d, 1100, 1100, 1033, 1100, 1033, 1033, 10e6, 1100, 1033, 1100, 101a, 101a, 10cd, 10cd, 1000, 10cd, 1000, 1000,
3-234
10b3, 10b3, 1000, 10b3, fcd,
fcd,
10cd, 10cd, f66,
10cd, fe6,
fe6,
1033, 10cd, f9a,
10cd, fcd,
fcd,
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Example 1
1066, 10cd, fcd,
10cd, fcd,
fcd,
1066, 10cd, fcd,
10cd, f9a,
f9a,
1033, 10b3, f9a,
10b3, f66,
f66,
1066, 10b3, fcd,
10b3, f9a,
f9a,
1066, 109a, fb3,
109a, f66,
f66,
c9a,
1066, db3,
1066, f80,
f80,
f9a,
1066, ecd,
1066, f33,
f33,
f9a,
1000, ecd,
1000, eb3,
eb3,
NOTE The second line of the system response indicates whether the data is read from the transceiver or the database. In example 1, the information is read from the transceiver.
Example 2 {27236} The following example displays the calibration data for a DRI that has 4 Branch Receive Diversity enabled. disp_cal_data 40 dri 0 0 0 Where:
68P02901W23-S
is: 40
site
dri
dri device
0
first dev_id
0
second dev_id
0
third dev_id
3-235 Nov 2009
References
Chapter 3: Device/function related commands
System response DRI ID: 0 0 0 Data read from transceiver Store Calibration Data:disabled Calibration Data (All values in Hex): Transmit Power Offsets = 12 Receiver System Data: AntennaNumber
1
2
3
4
5
6
7
8
9
10
11
12
b89, e80, e80, c4e, e80, e80, b89, e80, e80, c4e, e80, e80, b7f, e80, e80, ca2, e80, e80, b7f, e80, e80, ca2, e80, e80, b8d, e80, e80, c74, e80, e80, b8d, e80, e80, c74, e80, e80, b8d, e80, e80, c9d, e80, e80, b8d, e80, e80, c9d, e80, e80, b61, e80, e80, c65, e80, e80, b61, e80, e80, c65, e80, e80, b19, e80, e80, c0c, e80, e80, b19, e80, e80, c0c, e80, e80, aff,
e80,
e80, bd3, e80, e80, aff, e80, e80, bd3, e80, e80,
b1d, e80, e80, b54, e80, e80, b1d, e80, e80, b54, e80, e80, b4b, e80, e80, b9f, e80, e80, b4b, e80, e80, b9f, e80, e80, b5b, e80, e80, b85, e80, e80, b5b, e80, e80, b85, e80, e80, b4f, e80, e80, b53, e80, e80, b4f, e80, e80, b53, e80, e80, b4a, e80, e80, b71, e80, e80, b4a, e80, e80, b71, e80, e80, b2d, e80, e80, b59, e80, e80, b2d, e80, e80, b59, e80, e80, b1e, e80, e80, b29, e80, e80, b1e, e80, e80, b29, e80, e80, b08, e80, e80, aab, e80, e80, b08, e80, e80, aab, e80, e80, a8f, e80, e80, a9f, e80, e80, a8f, e80, e80, a9f, e80, e80,
References Related commands clear_cal_data on page 3-169
3-236
store_cal_data on page 3-534
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_cbch_state
disp_cbch_state ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_cbch_state command displays the value of the cbch_enabled field for a specific cell. In addition, the specified background message in a cell is presented. If the CBCH is hopping, the frequency hopping index (fhi) for the CBCH timeslot is also displayed. If the all option is selected for the message number parameter, all background messages associated with the indicated cell display. Security level
1
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
To successfully execute this command, purchase, install, and activate the background message feature.
Operator actions
The Background Message feature must be unrestricted.
Format Syntax disp_cbch_state disp_cbch_state all
Input parameters msg_num Uniquely identifies the number of the message for a given cell by sequence received (up to 4). The range of values is 0 to 3. cell_desc The GSM cell ID of the cell preceded by cell_number=. The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900).
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
68P02901W23-S
3-237 Nov 2009
Examples
Chapter 3: Device/function related commands
The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, place it inside double quotation marks and preceded by cell_name=.
NOTE This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition.
Examples Example 1 This example displays the output where the CBCH is not enabled and no background message is defined for the specified msg_num. The cell_number parameter uses the seven parameter format. disp_cbch_state 3 cell_number=5 4 3 2 1 61986 3494 Where:
is: 3
msg_num
5 4 3 2 1 61986 3494
cell_number
System response Message Number 3 is not defined for the CBCH. The CBCH for cell 5 4 3 2 1 61986 3494 is not enabled.
Example 2 This example displays the output where the CBCH is not enabled and no background message is defined for the specified msg_num. The cell_number parameter uses the four parameter format. disp_cbch_state 3 cell_number=543 21 61986 3494 Where:
is: 3
msg_num
543 21 61986 3494
cell_number
System response Message Number 3 is not defined for the CBCH. The CBCH for cell 5 4 3 2 1 61986 3494 is not enabled.
3-238
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 3 In this example, the affected cell is identified using the cell_name ‘london-south’. disp_cbch_state 3 cell_name=”london-south” Where:
is: 3
msg_num
‘london-south’
cell_name
System response Message Number 3 is not defined for the CBCH. The CBCH for cell 5 4 3 2 1 61986 3494 is not enabled.
Example 4 This is an example of the command succeeding if the CBCH is active and hopping with a background message defined: disp_cbch_state 2 cell_number=5 4 3 2 1 61986 3494 Where:
is: 2
msg_num
5 4 3 2 1 61986 3494
cell_number
System response Message Number 2 for the CBCH is: This is the background message. their escape format
Non alphabetic characters are displayed in
The Message Identifier is 1009 The Geographical Scope is 1 (Normal - PLMN Wide). The Message Code is 0. The update number is 0. The Language Identifier is 3 (French). The CBCH for cell 5 4 3 2 1 61986 3494 is active. The channel description is: Channel Type:
SDCCH/4 Subchannel number 2
Timeslot Number = 0 ARFCN = 107 (BCCH Carrier)
68P02901W23-S
3-239 Nov 2009
References
Chapter 3: Device/function related commands
References Related commands chg_smscb_msg on page 3-150
3-240
del_smscb_msg on page 3-206
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_cell
disp_cell ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_cell command reads back and displays all programmable database parameters for a specified cell. If the disp_cell command is used with the cell description and the optional ‘full’ parameter, the system displays all cell-related elements. If the disp_cell command is used with the cell_description only, the system displays the elements used in theadd_cell command. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
Format Syntax disp_cell [“full”]
Input parameters cell_desc GSM cell number of the cell to be displayed. The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900).
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
cell_id is an invalid parameter. The operator cannot input the cell_number or cell_name preceded by the GSM cell ID or GSM cell name. BSS system responds input error. “full” This optional parameter displays all elements related to the cell. The system displays the elements with non-indexed parameters first, in alphabetical order, followed by the indexed parameters also in alphabetical order.
68P02901W23-S
3-241 Nov 2009
Examples
Chapter 3: Device/function related commands
Examples Example 1 This example displays the programmable database parameters for a GSM cell with a Cell ID of 5 4 3 2 1 61986 34944. disp_cell 5 4 3 2 1 61986 34944 Where:
is: 5 4 3 2 1 61986 34944
cell_id
System response The system displays the cell information specified in the add_cell command at creation of cell 5 4 3 2 1 61986 34944.
Example 2 In this example, the cell is identified using the cell_name ‘london-south’: disp_cell “london-south” Where:
is: ‘london-south’
cell_id
System response The system displays the cell information specified in the add_cell command at creation of cell ‘london-south’.
Example 3 In this example, the cell is identified in the four parameter format, using the cell_number 543 721 62259 08736: disp_cell 543 721 62259 08736 Where:
is: 543 721 62259 08736
cell_id
System response The system displays the cell information specified in the add_cell command at creation of cell 543 721 62259 08736.
3-242
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
Example 4 In this example, all cell-related elements for cell 0 0 1 0 1 1 2 are displayed by using the parameter full. disp_cell 0 0 1 0 1 1 2 full Where:
is: 0010112
cell_id
full
full option (display all cell-related elements).
System response The system displays a complete list of all elements related to cell 0 0 1 0 1 1 2. Non-indexed parameters are displayed first, in alphabetical order, followed by the indexed parameters also in alphabetical order.
Example 5 {26881} This example displays the cell information about cell 0 0 1 0 1 1 4. disp_cell 0 0 1 0 1 1 4 FULL Where:
is: 0010114
cell_id
full
full option (display all cell-related elements).
System response The system displays a complete list of all elements related to cell 0 0 1 0 1 1 4.
References Related commands add_cell on page 3-22
copy_cell on page 3-179
del_cell on page 3-192
disp_gsm_cells on page 3-314
68P02901W23-S
3-243 Nov 2009
disp_cell_map
Chapter 3: Device/function related commands
disp_cell_map ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description Because of the dynamic cell migration in case of failure and recovery, a cell can be mapped to any equipped PCU site. The disp_cell_map command displays the current cell mapping information to a particular PCU. The displayed information includes EGPRS availability.
NOTE The disp_cell_status command shows the status details of the PCU that is currently serving a cell.
Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
This command is not allowed while in SYSGEN ON mode.
Format Syntax disp_cell_map all|location|cell_id
Input parameters
3-244
all
Displays cell mapping at all equipped PCUs.
location
pcu, pcu_0 to pcu_2.
cell_id
Identifier of cell for which mapping to a PCU is required.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Examples Example 1 Display cell mapping at PCUs 1 and 2: disp_cell_map pcu_1 pcu_2 Where:
is: pcu_1
location (site 1)
pcu_2
location (site 2)
System response PCU Site 1: CELL ID
GPRS STATUS
--------------------------
--------------------
001 01 1 (0001h) 4 (0004h)
Barred
001 01 1 (0001h) 5 (0005h)
Unbarred
PCU Site 2: CELL ID
GPRS STATUS
--------------------------
--------------------
001 01 1 (0001h) 7 (0007h)
Barred
001 01 1 (0001h) 8 (0008h)
Unbarred
END OF REPORT
Example 2 Display current PCU mapping of cell 0 0 1 0 1 1 4: disp_cell_map 0 0 1 0 1 1 4 Where:
is: 0010114
cell_desc
System response Current PCU site: PCU_1
68P02901W23-S
3-245 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 3 Display cell mapping at all PCUs: disp_cell_map all Where:
is: all
all option (display cell mapping at all equipped PCUs).
System response PCU Site 0: CELL ID --------------------------
GPRS STATUS --------------------
001 01 1 (0001h) 4 (0004h)
Barred
001 01 1 (0001h) 5 (0005h)
Unbarred
PCU Site 1: CELL ID --------------------------
GPRS STATUS --------------------
001 01 1 (0001h) 7 (0007h)
Barred
001 01 1 (0001h) 8 (0008h)
Unbarred
PCU Site 2: CELL ID --------------------------
GPRS STATUS --------------------
001 01 1 (0001h) 1 (0001h)
Barred
001 01 1 (0001h) 2 (0002h)
Unbarred
END OF REPORT
3-246
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_cell_status
disp_cell_status ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_cell_status command displays information and channel counters of a single GSM cell or all GSM cells at a specific site. Because of the dynamic cell migration in case of failure and recovery, a cell can be mapped to any equipped PCU site. The disp_cell_status command includes the information on the cell active PCU. When the status of a single cell is requested, the cell_name is included in the command output. When the status of all the cells at a location with more than three cells is requested, the information on the first two cells displays, followed with a prompt to continue. The cell_name is not included when all the cells at a site are displayed. If the BTF is not in service for any reason, the system displays an error message. If both the GSM and AMR Half Rate modes are disabled either at the BSS or Cell level for a given cell, the BSS when generating the disp_cell_status command, regards: •
Free generic traffic timeslots in that cell as free full-rate traffic channels.
•
Unavailable generic traffic timeslots in that cell as unavailable full-rate traffic channels.
Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
This command is not allowed while in SYSGEN ON mode.
Format Syntax disp_cell_status disp_cell_status disp_cell_status
68P02901W23-S
3-247 Nov 2009
Format
Chapter 3: Device/function related commands
Input parameters cell_desc The GSM cell ID of the cell to be displayed, preceded by cell_number=. The format for the GSM cell ID depends on: •
The system being used (PGSM, EGSM, DCS1800, PCS1900, or GSM850)
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, place it inside double quotation marks and precede by cell_name=.
NOTE This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition.
location Specifies the element location: 0 or bsc
BSC
1 - 140
BTS
high Indicate that this command is executed in high priority mode which implies that disp_cell_status is handled by BTS and PCU with high priority.
Output fields RAC This field shows the Routing Area Code (part of the cell identifier for GPRS cells). Status •
Barred - A MS cannot access the cell.
•
Unbarred - A MS can access the cell.
GPRS Status This field shows the status of a GPRS cell (barred/unbarred) and (when unbarred) whether EGPRS is available. {34144} GPRS Congestion Status
3-248
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
This field shows the cell GPRS congestion status (TRUE / FALSE / NA) when the GPRS/EDGE feature is unrestricted. •
TRUE - Indicates that the cell GPRS cell utilization has reached the higher threshold without dropping below the lower threshold. The additional switchable PDTCH is allocated during this status.
•
FALSE - Indicates that the cell GPRS cell utilization does not reach the higher threshold. No additional switchable PDTCH is allocated during this status.
•
NA - Indicates that the status is not applicable.
PDCH Status This field shows the GPRS Packet Data traffic channel status. Reset In Progress •
Yes - A reset is in progress. The cell is barred while a reset is in progress.
•
No - A reset is not in progress.
GPRS Reset in Prog This field shows whether a PCU is currently undergoing a Reset. SPI in Progress •
Yes - An SPI (Signaling Point Inaccessibility) is in progress. The cell is barred while an SPI is in progress.
•
No - An SPI is not in progress.
BSS BSSAP Prhb •
Yes - The BSS BSSAP (Base Station System Application Part) Prohibited flag is set to true. The cell is barred while the BSS BSSAP Prohibited flag is true.
•
No - The BSS BSSAP Prohibited flag is not set to true.
•
N/A - Not applicable; the value of this element is not relevant to the status of the cell.
MSC BSSAP Prhb •
Yes - The MSC BSSAP Prohibited flag is set to true. The cell is barred while the MSC BSSAP Prohibited flag is true.
•
No - The MSC BSSAP Prohibited flag is not set to true.
•
N/A - Not applicable; the value of this element is not relevant to the status of the cell.
SPI/MSC SCCP Prhb
68P02901W23-S
3-249 Nov 2009
Format
Chapter 3: Device/function related commands
•
Yes - The SPI/MSC BSSAP Prohibited flag is set to true. The cell is barred while the SPI/MSC BSSAP Prohibited flag is true.
•
No - The SPI/MSC BSSAP Prohibited flag is not set to true.
•
N/A - Not applicable; the value of this element is not relevant to the status of the cell.
AccCLASS Bar This field specifies the access classes of MSs that are barred from the cell. The access class is presented as a decimal value, separated by commas. If the cell is barred or OOS, this field contains N/A. If the cell is unbarred, this field contains None when all access classes have been unbarred. GPRS AccClass Bar This field shows any access class barring of GPRS cells. EGPRS Chan Req This field indicates if 11-bit EGPRS one-phase access is supported in the cell. EPCR is only available in the cell if the BCCH RTF is mapped to a CTU II radio. Full Power Mode This field indicates if the cell is in the full power mode. Ext Range Mode This field shows whether the Extended Range Feature is enabled (on) or disabled (off). SDCCH: FREE; INUSE; UNAVL These fields specify the number of Standalone Dedicated Control Channels (SDCCH) in the cell, that are currently free, in use or unavailable. Norm Outer TCH/F: FREE; INUSE; UNAVL These fields specify the number of Full Rate Traffic Channels (TCH/F) in the outer zone concentric cell that are currently free, in use or unavailable. The UNAVL field includes timeslots that are locked or out of service due to a fault condition. Any timeslot which is unavailable due to being locked or out of service is counted as an unavailable TCH (not SDCCH). This field does not include entire carriers which are out of service. Norm Outer TCH/F: FREE; INUSE; UNAVL These fields specify the number of Full Rate Traffic Channels (TCH/H) in the outer zone concentric cell that are currently free, in use or unavailable. Norm Inner TCH/F: FREE; INUSE; UNAVL These fields specify the number of Full Rate Traffic Channels (TCH/F) in the inner zone concentric cell that are currently free, in use or unavailable.
3-250
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Ext Outer TCH/F: FREE; INUSE; UNAVL These fields specify the number of Full Rate Traffic Channels (TCH/F) in the extended outer concentric cell that are currently free, in use or unavailable. Norm Inner TCH/H: FREE; INUSE; UNAVL These fields specify the number of Half Rate Traffic Channels (TCH/H) in the inner zone concentric cell that are currently free, in use or unavailable. Norm Outer TCH/G: FREE; INUSE; UNAVL These fields specify the number of Generic Traffic Channels (TCH/G) in the outer zone concentric cell that are currently free, in use or unavailable. Norm Inner TCH/G: FREE; INUSE; UNAVL These fields specify the number of Generic Traffic Channels (TCH/G) in the inner zone concentric cell that are currently free, in use or unavailable. PD CHANNEL This field shows the GPRS Packet Data traffic channels currently free, in use or unavailable.
EGPRS PD CHANNEL This field shows the EGPRS Packet Data traffic channels currently free, in use or unavailable. RES PDCH Requested This field shows the RES PDCH requested. SW PDCH Requested This field shows the SW PDCH requested.
Examples Example 1 This example displays the status of Cell ID 5 4 3 2 1 61986 34944 (in decimal and in seven parameter format). disp_cell_status 5 4 3 2 1 61986 34944 Where:
is: 5 4 3 2 1 61986 34944
68P02901W23-S
cell_number
3-251 Nov 2009
Examples
Chapter 3: Device/function related commands
System response GSM CELL ID
MCC 543
LAC
MNC 21
CI
(dec)
61986 34944
(hex)
f222h 8880h
(name)
london-south
-------------------------------------Frequency Type
PGSM
BCCH Frequency
100
-------------------------------------Status
OOS
Reset in Prog
No
SPI in Prog
Yes
BSS BSSAP Prhb
Yes
MSC BSSAP Prhb
Yes
SPI/MSC SCCP Prhb
Yes
AccClass Bar
NA
Full Power Mode
OFF
Extend Range Mode
OFF FREE
INUSE UNAVL
----- ----- ----SDCCH
0
0
0
Norm Outer TCH/F
0
0
0
Norm Inner TCH/F
0
0
0
Ext
0
0
0
Outer TCH/F
End of Report.
Example 2 This example identifies the cell using the cell_name ‘london-south’. disp_cell_status cell_name=”london-south” Where:
is: ‘london-south’
3-252
cell_name
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response GSM CELL ID
MCC 543 MNC 21
LAC
CI
(dec)
61986 34944
(hex)
f222h 8880h
(name)
london-south
-----------------------------------Status
Barred
Reset In Prog
No
SPI in Prog
Yes
BSS BSSAP Prhb
Yes
MSC BSSAP Prhb
No
SPI/MSC SCCP Prhb
No
AccCLASS Bar
NA
Ext Range Mode
OFF FREE
INUSE UNAVL
----- ----- ----SDCCH
0
0
0
Norm Outer TCH/F
0
0
0
Norm Inner TCH/F
0
0
0
Ext
0
0
0
Outer TCH/F
End of Report
Example 3 This example shows the display for a cell where the Concentric Cells feature is enabled. disp_cell_status 0 Where:
is: 0
68P02901W23-S
cell_number
3-253 Nov 2009
Examples
Chapter 3: Device/function related commands
System response Start of report for LOCATION 39: GSM CELL ID
MCC 001
MNC 01
LAC
CI
(dec)
1
39001
(hex)
0001h
9859h
-------------------------------------Frequency Type
PGSM
BCCH Frequency
62
-------------------------------------Status
Unbarred
Reset in Prog
No
SPI in Prog
No
BSS BSSAP Prhb
NA
MSC BSSAP Prhb
NA
SPI/MSC SCCP Prhb
NA
AccClass Bar
None FREE
INUSE UNAVL
----- ----- ----SDCCH
0
0
0
Norm Outer TCH/F
0
0
0
Norm Inner TCH/F
0
0
0
Ext
0
0
0
Outer TCH/F
End of Report.
Example 4 This example displays the status of a BTS site. disp_cell_status 30 Where:
is: 30
3-254
location
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response Start of report for LOCATION 30: GSM CELL ID MCC
001
001
MNC
01
01
LAC
17
(0011h)
17
(0011h)
CI
31
(001Fh)
33
(0021h)
RAC
NA
NA
-----------------------------------------------------------Primary Freq Type
EGSM
EGSM
Secondary Freq Type N/A
N/A
BCCH Frequency
64
5
-----------------------------------------------------------Status
Unbarred
Unbarred
GPRS Status
NA
NA
PDCH Status
Unknown
Unknown
RES PDCH Requested
NA
NA
SW PCDH Requested
NA
NA
Reset in Prog
No
No
GPRS Reset in Prog
NA
NA
SPI in Prog
No
No
BSS BSSAP Prhb
NA
NA
MSC BSSAP Prhb
NA
NA
SPI/MSC SCCP Prhb
NA
NA
AccClass Bar
None
None
GPRS AccClass Bar
NA
NA
Full Power Mode
OFF
OFF
Ext Range Mode
OFF
OFF
Active PCU site
NA
NA
FREE
SDCCH
68P02901W23-S
INUSE UNAVL
FREE
INUSE UNAVL
----- ----- -----
----- ----- -----
8
8
0
0
0
0
3-255 Nov 2009
Examples
Chapter 3: Device/function related commands
Norm Outer TCH/F
0
0
0
0
0
0
Ext
Outer TCH/F
0
0
0
0
0
0
Norm Outer TCH/H
0
0
0
0
0
0
Norm Inner TCH/H
0
0
0
0
0
0
Norm Outer TCH/G
14
NA
0
6
NA
0
Norm Inner TCH/G
0
NA
0
0
NA
0
PD CHANNEL
NA
NA
NA
NA
NA
NA
End of Report.
Example 5 This example shows the display when a location is entered and the GPRS feature is unrestricted. disp_cell_status bsc Where:
is: bsc
location
System response Start of report for LOCATION 0: GSM CELL ID MCC
001
001
MNC
01
01
LAC
1
(0001h)
1
(0001h)
CI
1
(0001h)
6
(0006h)
RAC
8
(0008h)
NA
------------------------------------------------------------Primary Freq Type
PGSM
PGSM
Secondary Freq Type N/A
N/A
BCCH Frequency
85
65
-------------------------------------------------------------
3-256
Status
Unbarred
Barred
GPRS Status
Unbarred
Barred
PDCH Status
PD Available
Unknown
RES PDCH Requested
3
NA
SW PDCH Requested
5
NA
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Reset in Prog
No
No
GPRS Reset in Prog
No
No
SPI in Prog
No
No
BSS BSSAP Prhb
NA
NA
MSC BSSAP Prhb
NA
NA
SPI/MSC SCCP Prhb
NA
NA
AccClass Bar
None
NA
GPRS AccClass Bar
4
NA
Full Power Mode
OFF
OFF
Ext Range Mode
OFF
OFF
Active PCU site
1
N/A
FREE
INUSE UNAVL FREE INUSE UNAVL
----- ----- ----- ----- ----- ----SDCCH
4
0
0
0
0
0
Norm Outer TCH/F
7
0
0
0
0
0
Norm Inner TCH/F
0
0
0
0
0
0
Ext
0
0
0
0
0
0
8
0
0
NA
NA
NA
Outer TCH/F
PD CHANNEL End of Report
Example 6 {34144} This example displays the status of an in-service cell when the GPRS status is unbarred and congestion status is TRUE from the PCU, irrelevant of EGPRS in ON or OFF status. The EGPRS status is displayed in the field. disp_cell_s 3 Where:
is: 3
location
System response Start of report for LOCATION 3: GSM CELL ID MCC
001
MNC
01
68P02901W23-S
3-257 Nov 2009
Examples
Chapter 3: Device/function related commands
LAC
1
CI
1
RAC
NA
Primary Freq Type
(0001h) (0028h)
EGSM
Secondary Freq Type N/A BCCH Frequency
14
Status
Unbarred
GPRS Status
Unbarred
EGPRS Avail
GPRS Congestion
TRUE
PDCH Status
PD Available
RES PDCH Requested
10
SW PDCH Requested
5
Reset in Prog
No
GPRS Reset in Prog
No
SPI in Prog
No
BSS BSSAP Prhb
No
MSC BSSAP Prhb
No
SPI/MSC SCCP Prhb
No
AccClass Bar
NA
GPRS AccClass Bar
4
EGPRS Chan Req
Avail
Full Power Mode
OFF
Ext Range Mode
OFF
Active PCU Site
0
FREE
INUSE
UNAVL
SDCCH
8
0
0
Norm Outer TCH/F
14
0
0
Norm Inner TCH/F
0
0
0
Ext Outer TCH/F
0
0
0
Norm Outer TCH/H
0
0
0
Norm Inner TCH/H
0
0
0
Norm Outer TCH/G
0
NA
0
Norm Inner TCH/G
0
NA
0
PD CHANNEL
1
6
0
EGPRS PD CHANNEL
6
2
0
End of Report.
3-258
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 7 {23311A} This example displays the cell status with both the Extended Range Cell for Data feature (ercgprsOpt) and EGPRS feature (egprsOpt) unrestricted. disp_cell_s 3 Where:
is: 3
location
System response Start of report for LOCATION 3: GSM CELL ID MCC
001
MNC
01
LAC
1
(0001h)
CI
40
(0028h)
RAC
N/A
Primary Freq Type
EGSM
Secondary Freq Type
N/A
BCCH Frequency
14
Status
Unbarred
GPRS Status
Unbarred, EGPRS Avail
PDCH Status
PD Available
RES PDCH Requested
10
SW PDCH Requested
5
Reset in Prog
No
GPRS Reset in Prog
No
SPI in Prog
No
BSS BSSAP Prhb
No
MSC BSSAP Prhb
No
SPI/MSC SCCP Prhb
No
AccClass Bar
N/A
GPRS AccClass Bar
4
EGPRS Chan Req
Avail
Full Power Mode
OFF
Ext Range Mode
ON
Active PCU Site
0 FREE
INUSE UNAVL
----- ----- -----
68P02901W23-S
3-259 Nov 2009
Examples
Chapter 3: Device/function related commands
SDCCH
8
0
0
Norm Outer TCH/F
14
0
0
Norm Inner TCH/F
0
0
0
Ext Outer TCH/F
0
0
0
Norm Outer TCH/H
0
0
0
Norm Inner TCH/H
0
0
0
Norm Outer TCH/G
0
NA
0
Norm Inner TCH/G
0
NA
0
PD CHANNEL
1
6
0
EGPRS PD CHANNEL
2
2
0
Ext PD CHANNEL
2
0
0
Ext EGPRS PD CHANNEL
2
0
0
End of Report.
Example 7 This example runs the disp_cell_status in high priority mode, BTS times out. disp_cell_status 15 high Where:
is: 15
location
high
high priority
System response COMMAND REJECTED: The BTS is very busy, please try again later.
3-260
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_conn
disp_conn ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_conn command displays the MSS connectivity between the RXCDR and the BSS sites connected to it. Security level
1
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
This command is only available at a BSC or RXCDR site.
NOTE The term ‘local site’ refers to the site at which the command is executed; the term ‘remote site’ refers to the site to which the local site is connected.
Format Syntax disp_conn []
Input parameters remote_entity_id The network identity of the remote site. The valid range is 1 to 254.
Examples Example 1 Display all the MMS connectivity between the BSS and all RXCDRs which are connected to it, and are specified by equipped AXCDR devices at the BSC. disp_conn
68P02901W23-S
3-261 Nov 2009
Examples
Chapter 3: Device/function related commands
System response The BSS to RXCDR connectivity is as follows: BSS MMS id 0 1 is connected to RXCDR 4 - MMS id 9 0 BSS MMS id 1 1 is connected to RXCDR 5 - MMS id 4 0 Finished displaying BSS to RXCDR connectivity
Example 2 Display the MMS connectivity between the BSS and RXCDR 5, which is represented by equipped device AXCDR 5 at the BSC. disp_conn 5 Where:
is: 5
remote entity ID.
System response The BSS to RXCDR connectivity is as follows: BSS MMS id 1 1 is connected to RXCDR 5 - MMS id 4 0 Finished displaying BSS to RXCDR connectivity
3-262
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_csfp
disp_csfp ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_csfp command displays the per site CSFP algorithm or flow control values. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
Format disp_csfp []
Input parameters location Specifies the element location: 0 or bsc
BSC
1 - 140
BTS
pcu
PCU
element algorithm
Selects the CSFP algorithm method
flow_control
Selects the flow control value
68P02901W23-S
3-263 Nov 2009
Examples
Chapter 3: Device/function related commands
Examples Example 1 This example shows the inputs required to display the CSFP algorithm at the BSC. disp_csfp bsc algorithm Where:
is: bsc
location
algorithm
element
System response Site
Algorithm
----
---------
0
ANY
Example 2 his example shows the required inputs required to display the CSFP flow control at site 3: disp_csfp 3 flow_control Where:
is: 3
location
flow_control
element
System response Site
Flow Control
----
------------
3
3-264
10
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 3 This example shows the required inputs required to display all elements at site 7. disp_csfp 7 Where:
is: 7
location
System response Site
Flow Control
Algorithm
----
------------
---------
7
10
ANY
Example 4 {25424} This example displays the csfp flow control value of PCU. disp_csfp pcu flow_control Where:
is: pcu
location
System response Site
Flow Control
Algorithm
----
------------
---------
PCU
10
N/A
Example 5 {25424} This example displays the status of PCU CSFP. disp_csfp_status
68P02901W23-S
3-265 Nov 2009
References
Chapter 3: Device/function related commands
System response SITE, ID
CSFP EQUIP
STATUS
0,0
YES
0,1
NO
1,0
YES
3,0
YES
...
...
...
...
...
...
PCU,0
YES
CODE LOADED
CODE LOADED * CODE LOADED SITE/LINK OOS
References Related command chg_csfp on page 3-95.
3-266
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_csfp_status
disp_csfp_status ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_csfp_status command displays the status of all CSFPs equipped in the BSS network. The output generated by this command is a three column listing with the following information: SITE ID
The site number
CSFP EQUIP
Equipped indicator (YES or NO)
STATUS
The status of the CSFP device as shown below:
Where:
is: *
printed only with unequipped indicator.
NOT EQUIPPED
the CSFP equipment is not installed.
DEVICE LOCKED
the CSFP device is locked.
CODE LOADED
the CSFP device is busy-unlocked, and the device is code loaded.
AWAITING CODE
the CSFP device is enabled-unlocked, and the device is in a queue to be loaded, or is currently being downloaded with code.
CSFP OOS
the CSFP device is out of service.
NO CODE
the CSFP device is disabled-unlocked, and the device does not contain a valid software instance.
SITE/LINK OOS
link is out of service.
Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
This command is not allowed while in SYSGEN ON mode.
Format Syntax disp_csfp_status
68P02901W23-S
3-267 Nov 2009
Example
Chapter 3: Device/function related commands
Input parameters There are no input parameters with this command.
Example This example shows the input required to display the status of the CSFP devices in the BSS network and the output when only one device is equipped and is loaded with code. disp_csfp_status
System response SITE,ID 0,0
CSFP EQUIP YES
STATUS CODE LOADED
References Related command chg_csfp on page 3-95.
3-268
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_dte
disp_dte ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_dte command displays DTE addresses. This command is primarily for use by field technicians or installers. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
Format Syntax disp_dte [ ] If no input parameters are specified, all BSS and OMC-R DTE addresses are displayed.
Input parameters link The location of the link: bsc
BSC
omcr
OMC-R
cbc
Cell Broadcast Centre (CBC)
bsc_cbc
BSC DTE Address for the CBC
link_num The link number range: 0 to 3
link at BSC
0 to 7
link at OMC-R
0
link at CBC or BSC_CBC
68P02901W23-S
3-269 Nov 2009
Examples
Chapter 3: Device/function related commands
Examples Example 1 In this example, the DTE link addresses are displayed (in binary coded decimal) when the command is entered: disp_dte
System response BSS DTE addresses: Address #0:
31070863210701
Address #1:
31070863210701
Address #2:
31070863210701
Address #3:
31070863210701
OMCR DTE addresses: Address #0:
31031263245610
Address #1:
31031263245620
Address #2:
31031263245630
Address #3:
31031263245640
Address #4:
31031263245650
Address #5:
31031263245660
Address #6:
31031263245670
Address #7:
31031263245680
Example 2 In this example, the DTE link address and link numbers are displayed when the command is entered: disp_dte bsc 2 Where:
is: bsc
location
2
link_num
System response Address #2:
3-270
31070863210701
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
References Related command chg_dte on page 3-98.
68P02901W23-S
3-271 Nov 2009
disp_element
Chapter 3: Device/function related commands
disp_element ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_element command displays the value of a database parameter in the CM database.
NOTE The syntax required to display each CM database parameter is included in the parameter description in Chapter 6 CM database parameters.
Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
Format Syntax disp_element [,][,] []
Input parameters database_parameter String identifying the database parameter in the CM database. index1 If a database parameter value to be displayed requires an index, the index value must be entered immediately after the database parameter name separated by a comma. Database parameters modified using the chg_cell_element command are stored in a four row data array. The rows in the data array are specified as bins in the chg_cell_element command. Individual database parameter values modified using the chg_cell_element command cannot be displayed using the disp_element command. When the disp_element command is used to display the values of parameters modified using the chg_cell_element command, the row (bin_num) is entered as the index1 value. All 32 values located in the entered row number are displayed. An example is included at the end of the description of this command.
3-272
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
location Specifies the site location: 0 or bsc
BSC
1 - 140
BTS
{27955A} pcu or pcu_0
PCU
all
Specifies all sites.
cell_desc GSM cell ID of the cell to be displayed, preceded by cell_number=. The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900).
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks and be preceded by cell_name=.
NOTE This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition. The cell_desc can also be specified as all.
Examples Example 1 In this example, the bit error rate loss threshold per day is 16 for site number 0: disp_element ber_loss_daily 0 Where:
is: ber_loss_daily
database_parameter
0
location
System response ber_loss_daily = 16
68P02901W23-S
3-273 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 2 In this example, the values of a database element modified using the chg_cell_element command are displayed. The bin number (0) is entered as the index value. disp_element rxlev_dl_ho,0 1 cell_number=5 4 3 2 1 61986 34944 Where:
is: rxlev_dl_ho
database_parameter
0
index (bin num)
1
location
5 4 3 2 1 61986 34944
cell_desc
NOTE This example could have been entered as: disp_element rxlev_dl_ho,0 1 cell_name=”london-south” where the command cell_name had been used to assign the name ‘london-south’ to the cell with ID = 5 4 3 2 1 61986 34944.
System response rxlev_dl_ho[0] = alg_num: 0 alg_data: 8
Example 3 {28337} In this example, the value of the database element ss7_hsp_12_t1 is displayed. disp_element ss7_hsp_l2_t1 0 Where:
is: ss7_hsp_12_t1
database_parameter
0
location
System response ss7_hsp_l2_t1 = 300000
3-274
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 4 {28000} This example displays the prp_fanout_mode parameter. disp_element prp_fanout_mode pcu Where:
is: prp_fanout_mode
database_parameter
pcu
location
System response prp_fanout_mode = 1
Example 5 {31400} This example displays the value of td_enabled element. disp_element td_enabled 0 Where:
is: td_enabled
database_parameter
0
location
System response td_enabled = 0
Example 6 {27508} This example displays the fieldeng_always_enabled element. disp_element fieldeng_always_enabled 0 Where:
68P02901W23-S
is: fieldeng_always_enabled
database_parameter
0
location
3-275 Nov 2009
Examples
Chapter 3: Device/function related commands
System response fieldeng_always_enabled = 1
Example 7 {32340} This example allows the operator to display the value of cell barred delay (in seconds). disp_element cell_barred_delay 0 Where:
is: cell_barred_delay
database_parameter
0
location
System response cell_barred_delay = 180 COMMAND ACCEPTED
Example 8 {26740} This example displays the value of dsp_error_inc element. disp_element dsp_error_inc 0 Where:
is: dsp_error_inc
database_parameter
0
location
System response dsp_error_inc = 30
3-276
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 9 {26881} This example displays the value of ext_ul_dur. disp_element ext_ul_dur 0 Where:
is: ext_ul_dur
database_parameter
0
location
System response ext_ul_dur = 24
Example 10 {31565} This example displays the status of the switch for AGCH flow control. disp_element _cell_data,20 1 cell_number=5 4 3 2 1 61986 34944 Where:
is: _cell_data,20
database_parameter
1
location
5 4 3 2 1 61986 34944
cell description
System Response _cell_data = 1
Example 11 This example displays the value of sig_lnk_tst_allow. disp_elem sig_lnk_tst_allow 0 Where:
is: sig_lnk_tst_allow
database_parameter
0
location
System Response sig_lnk_tst_allow = 1
68P02901W23-S
3-277 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 12 This example displays the value of sig_lnk_tst_allow. disp_elem sig_lnk_tst_allow 0 Where:
is: sig_lnk_tst_allow
database_parameter
0
location
System Response sig_lnk_tst_allow = 0
Example 13 {29693A} This example displays the fer_meas_period value. disp_element fer_meas_period 0 Where:
is: fer_meas_period
database_parameter
0
location
System Response fer_meas_period = 1
Example 14 {34164} This example displays the _bss_data,1 value. disp_element _bss_data,1 0 Where:
is: _bss_data,1
database_parameter
0
location
System Response _bss_data,1 = 1
3-278
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 15 {34164} This example displays the _cell_data,21 value of cell 0 0 1 0 1 99 72 under site 114. disp_element _cell_data,21 114 cell 0 0 1 0 1 99 72 Where:
is: _cell_data,21
database_parameter
114
location
0 0 1 0 1 99 72
cell description
System Response _cell_data,21 = 1
Example 16 {34320G} This example displays the status of the PA Bias feature at site 2 with the feature enabled. disp_element power_save_enable 2 Where:
is: power_save_enable
element name
2
location
System Response power_save_enable = 1
Example 17 {34303} This example displays the value of the Abis status element for H1 BTS (Site id = 1) when the Dual Abis Aware feature is enabled. disp_element _site_data,5 1 Where:
68P02901W23-S
is: _site_data, 5
database_parameter
1
location
3-279 Nov 2009
Examples
Chapter 3: Device/function related commands
System Response _site_data,5 = 0
Example 18 {34303} This example displays the value of the Abis status element for all the BTS sites when the Dual Abis Aware feature is enabled. disp_element _site_data, 5 all Where:
is: _site_data, 5
database_parameter
all
location
System Response ELEMENT: _site_data SITE
ELEMENT VALUE
----
-------------
0
0
11
1
12
0
Example 19 {23306} This example displays the value of the bsp_overload_protection parameter. disp_element bsp_overload_protection bsc Where:
is: bsp_overload_protection
database_parameter
bsc
location
System response bsp_overload_protection = 0
3-280
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 20 {34321} This example displays the _bss_data,10 value. disp_element _bss_data,10 0 Where:
is: _bss_data,10
element name
0
location
System Response _bss_data,10 = 1
Example 21 {34900} This example displays the value of _bss_data,6. disp_element _bss_data,6 0 Where:
is: _bss_data,6
element name
0
location
System Response _bss_data,6 = 0
Example 22 This example displays the nacc_nc2_enabled value. disp_element nacc_nc2_enabled 0 Where:
68P02901W23-S
is: nacc_nc2_enabled
element name
0
location
3-281 Nov 2009
References
Chapter 3: Device/function related commands
System Response nacc_nc2_enabled = 1
References Related information For detailed information on database parameters, refer to CM database parameters presentation on page 6-2.
Related commands chg_element on page 3-106.
3-282
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_equipment
disp_equipment ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_equipment command displays the software and hardware information of equipped devices and functions. Information displayed includes the parameters entered for a specific device or function using the equip command. {34145} The disp_equipment command displays the actual cell GPRS configuration information per PCU and PRP/PXP level along with the existing equipment information. Equipment configurations typically vary by location, therefore, the devices and functions available for display vary from site to site. This command is used to identify the site equipment configuration using location as the only command argument. The full option permits hardware information to be displayed in addition to the equipment parameters. This hardware information includes the hardware version number (hvn) displayed as a numerical value. A single hvn represents one or more kit numbers for a specific printed circuit board. The relationship of the hvn to the kit number is dependent on the equipment configuration. In later releases, a kit number is displayed in place of a hvn. A kit number includes the current hardware and firmware revisions of the printed circuit board. Kit numbers are incremented in response to either a hardware or firmware change. More than one firmware version can exist for any given hardware version of a printed circuit board. Kit numbers use the following format: SLN7133BA Where:
is: SLN7133
a unique value identifying a specific printed circuit board.
B
the hardware version of the printed circuit board represented as an alphabetical value.
A
the firmware version of the printed circuit board.
This can then be followed by further information, dependent on the particular hardware and its revision level, such as:
68P02901W23-S
EFGH
Each letter corresponds to a miscellaneous change made to the printed circuit board in the manufacturing process that did not require new hardware or firmware.
REV 0
This numerical value represents the current revision level of the most recent change.
MEM 0238 - BIT ERROR RATE TEST
This is additional descriptive information related to the last revision to the printed circuit board.
3-283 Nov 2009
Format
Chapter 3: Device/function related commands
The disp_equipment command does not report the hvns for half size boards. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
Format Syntax disp_equipment [ [] []] [full]
Input parameters location Specifies the equipment location: 0 or bsc
BSC
1 - 140
BTS
{27955A} pcu or pcu_0
PCU
dev/func name Literal that uniquely identifies the device or function id1 First identifier or the wild-card character ‘*’. id2 Second identifier or the wild-card character ‘*’. id3 Third identifier or the wild-card character ‘*’. full This is an optional parameter that is used to display the hardware-specific information for a device in addition to the configuration information entered when the device is equipped. When this option is used to display all of the equipment at a site, the output is a table which includes kit and serial numbers.
NOTE The full option is not allowed while in SYSGEN ON mode.
3-284
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
CIC syntax Because the Circuit Identity Code (CIC) device can be specified in different ways, the different forms of syntax are detailed as follows: Valid for local transcoding: disp_equipment CIC Valid for remote transcoding: disp_equipment CIC disp_equipment CIC
Input parameters location Specifies the location of the device: 0 or bsc
BSC
1 - 140
BTS
CIC Literal that uniquely identifies the CIC device. cic_num1 First CIC device number. cic_num2 Last CIC device number in a range. mms_id1 First MMS identifier. mms_id2 Second MMS identifier, or last in a range if TO is used. timeslot1 First timeslot. timeslot2 Second timeslot, or last in a range if TO is used. group1 First group. group2 Second group.
68P02901W23-S
3-285 Nov 2009
Examples
Chapter 3: Device/function related commands
* Indicates all CICs on the MMSs specified in the timeslot, regardless of group.
Examples Example 1 In the following example, all equipment at location 0 are displayed: disp_equipment 0 full Where:
is: 0
location
full
full option
System response Device
FRU
Kit
Number
Serial Number
HVN
---------------- -------------- ----------------- --------------- ----
3-286
GPROC
2
0
0
GPROC2
Not Applicable
Not Applicable
4
GPROC
3
0
0
Unavailable
Unavailable
Unavailable
GPROC
1
0
0
GPROC2
Not Applicable
Not Applicable
4
BSP
0
0
0
GPROC2
Not Applicable
Not Applicable
4
CSFP
0
0
0
Unavailable
Unavailable
Unavailable
MSI
0
0
0
MSII
Not Applicable
Not Applicable
MMS
0
0
0
Unavailable
Unavailable
Unavailable
255
MMS
0
0
0
Unavailable
Unavailable
Unavailable
255
MTL
0
0
0
Unavailable
Unavailable
Unavailable
255
RSL
2
0
0
Unavailable
Unavailable
Unavailable
255
RSL
3
0
0
Unavailable
Unavailable
Unavailable
255
SITE
3
0
0
Unavailable
Unavailable
Unavailable
255
SITE
4
0
0
Unavailable
Unavailable
Unavailable
255
PATH
1
0
0
Unavailable
Unavailable
Unavailable
255
255
255 4
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
BSS
1
0
0
Not Applicable
LCF
1
0
0
Not Applicable
Type
Cage
Slot
HVN
------- -------- -------- ----KSWX
0
21
48
Example 2 In the following example, only KSWX at location 0 are displayed: disp_equipment 0 kswx * * * full Where:
is: 0
location
kswx
device/function name
***
1st, 2nd, and 3rd identifier wild cards.
full
full option
System response Type
Cage
Slot
HVN
----- -------- -------- -------KSWX
0
21
48
Example 3 This example shows the values entered when RTF 0 1 at location 2 was equipped. disp_equipment 2 rtf 0 1 Where:
68P02901W23-S
is: 2
location
rtf
device/func name
0
first identifier
1
second identifier
3-287 Nov 2009
Examples
Chapter 3: Device/function related commands
System response Capacity of carrier: Type of carrier: RTF identifier:
FULL
NON_BCCH 0 1
The primary Unique PATH id is:
0
GSM cell to which this carrier is assigned: Carrier absolute radio freq.
channel:
Carrier frequency hopping indicators: Carrier training sequence codes:
61 0 0 0 0 0 0 0 0
5 5 5 5 5 5 5 5
KSW pair that manages this carrier: Cell zone:
0
0
Number of extended range timeslots allowed: SDCCH load:
262 01 510 211
0
2
SDCCH placement priority:
2
Channel allocation priority:
2
The maximum number of PDCHs:
4
The number of reserved PDCHs: 32 kbps GPRS TRAU allowed:
2
yes
Example 4 This example displays information for PCU 0 (3 TRAU GDS and 2 PMCs equipped on 2 PRPs, 8 64 K air PDTCHs, 81 16 K air PDTCHs) when EGPRS is unrestricted. disp_equipment 0 PCU 0 Where:
3-288
is: 0
location
PCU
device/func name
0
PCU identifier
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response PCU identifier:
0
PCU IP Address[ip_address]:
127.0.0.1
PCU Subnet Mask[subnet_mask]:
255.255.255.255
PCU Router IP Address[router_ip_address]:
127.0.0.1
NSEI: 27 Primary Cells: 001 01 1 1 001 01 1 6 001 01 1 3 001 01 1 33 001 01 1 18 Provisioned
Requested
------------------------Usable PRP PDTCHs:
240
89
Usable 16 K GDS Resources: 372 64 K
Max Configurable PDTCHs:
113 or
32 K
or
16 K
---
----
----
64
75
151
Example 5 {28337} This example displays information for HSP MTL. disp_equipment 0 mtl 1 0 Where:
68P02901W23-S
is: 0
location
mtl
device/func name
1
first identifier
0
second identifier
3-289 Nov 2009
Examples
Chapter 3: Device/function related commands
System response Device ID for the MTL: 1 DS0 channels for this MTL: 31 First MMS identifier for this device: 0 Second MMS identifier for this device: 1 Timeslot on MMS where this device appears: 1
Example 6 {28337} This example displays information for 64 k MTL. disp_equipment 0 mtl 10 0 Where:
is: 0
location
mtl
device/func name
10
first identifier
0
second identifier
System response Device identification for this MTL: 10 DS0 channels for this MTL: 1 First MMS identifier for this device: 1 Second MMS identifier for this device: 0 Timeslot on MMS where this device appears: 8
Example 7 {28337} This example displays an MTL LCF handling the HSP MTL. disp_eq 0 lcf 1 Where:
3-290
is: 0
location
lcf
device/func name
1
first identifier
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response Function ID for the LCF: 1 Number of DS0 channels the LCF can manage as MTLs [max_mtls]: 31 Number of CBLs the LCF can manage[max_cbls]: 0 Number of GSLs the LCF can manage[max_gsls]: 0
Example 8 {28351} This example displays the PXP DPROC with the FULL option. disp_equipment pcu_0 dproc 4 0 full Where:
is: pcu_0
location
dproc
device/function name
4
first identifier
0
second identifier
full
option
System response DPROC id: 4 DPROC type: PXP Hardware Information: PCI Vendor Id: 1223h PCI Device Id: 0048h PCI Revision Id: 1h PCI Type: UNKNOWN HSC Type: UNKNOWN IP Address Information: DPROC (750): 10.0.130.1 Current Cell Mapping: GSM CELL ID SITE MCC MNC LAC CI LCI ---- ------------------------------------ --11 001 01 403 (0193h) 11 (000Bh) 0
68P02901W23-S
3-291 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 9 {28351} The example displays a PXP DPROC. disp_equipment PCU DPROC 1 Where:
is: PCU
location
DPROC
device/function name
1
first identifier
System response DPROC id: 1 DPROC type: PXP
Example 10 {26740} This example displays the ETH device. disp_equipment bsc eth 1 0 0 Where:
is: bsc
location
eth
device/function name
1
first identifier
0
second identifier
0
third identifier
System response PSI identifier: 1 Ethernet port id: 0
3-292
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 11 {26481} This example displays Horizon II micro cabinet at site 5. disp_equip 5 CAB 15 0 0 Where:
is: 5
location
CAB
device/function name
15
first identifier
0
second identifier
0
third identifier
System response CABINET identifier: 15 Cabinet type: HORIZON2MINI_EXT Frequency type: PGSM
Example 12 {34145} This example displays the information for PCU 0 without full option. disp_equipment 0 PCU 0 Where:
68P02901W23-S
is: 0
location
PCU
device/function name
0
first identifier
3-293 Nov 2009
Examples
Chapter 3: Device/function related commands
System response PCU identifier:
0
PCU IP Address[ip_address]:
127.0.0.1
PCU Subnet Mask[subnet_mask]:
255.255.255.255
PCU Router IP Address[router_ip_address]:
127.0.0.1
NSEI: 27 PRP Fanout Mode:
1
GSM CELL ID MCC MNC LAC
CI LCI
--- --- --- --- --001 01
696
26
0
001 01
696
27
2
001 01
696
16
1
001 01
696
72
3 Provisioned
Requested
------------------------Usable PRP PDTCHs:
240
89
Usable 16 K GDS Resources: 372 64 K --Max Configurable PDTCHs:
64
113 or 32 K ---75
or 16 K ---151
Example 13 {34145} This example displays the information for PCU 0 with full option. disp_equipment 0 PCU 0 full Where:
3-294
is: 0
location
PCU
device/function name
0
first identifier
full
option
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response PCU identifier:
0
PCU IP Address[ip_address]:
127.0.0.1
PCU Subnet Mask[subnet_mask]:
255.255.255.255
PCU Router IP Address[router_ip_address]:
127.0.0.1
NSEI: 27 PRP Fanout Mode:
1
GSM CELL ID MCC MNC LAC
CI LCI
--- --- --- --- --001 01
696
26
0
001 01
696
27
2
001 01
696
16
1
001 01
696
72
3 Provisioned
Requested
------------------------Usable PRP PDTCHs:
240
89
Usable 16 K GDS Resources: 372 64 K
113 or 32 K
--Max Configurable PDTCHs:
or 16 K
----
64
----
75
151
Hardware Information: Not Applicable SITE
LCI
PRP
Configured
Database GDS
All PD
16/32/64k
RES/SW
Configured
16/32/64k
---- ------------------------------------
--—
--—
1
0
1
6/0/6
8/4
6/0/6
Yes
10
2
1
0/12/0
8/4
0/12/0
Yes
10
1
2
2/0/6
7/4
2/0/6
No
1
3
2
5/0/3
4/4
5/0/2
Yes
NUMBER OF ACTUAL CONNECTED GCIs: NUMBER OF ACTUAL 16K GCIs:
13
93 RCIs: 13
NUMBER OF ACTUAL 32K GCIs:
24
RCIs: 12
NUMBER OF ACTUAL 64K GCIs:
56
RCIs: 15
NUMBER OF ACTUAL FREE GCI COUNT: 31 NUMBER OF FREE DS0: 7
68P02901W23-S
3-295 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 14 {34145} This example displays the information for PRP DPROC 4 0 0 on PCU 0. disp_equipment pcu DPROC 4 0 0 FULL Where:
is: PCU
location
DPROC
device/function name
4
first identifier
0
second identifier
0
third identifier
FULL
option
System response DPROC id: 4 DPROC type: PRP Hardware Information: PCI Vendor Id: 1146h PCI Device Id: 6750h PCI Revision Id: 1h PCI Type: UNKNOWN HSC Type: UNKNOWN Current Cell Mapping: GSM CELL ID
Configured
Database GDS
All PD
16/32/64k
RES/SW
16/32/64k
Configured
---- ------------------------------------
--—
--—
--—
1
001
01
696
26
0
6/0/6
8/4
6/0/6
Yes
10
001
01
696
27
2
0/12/0
8/4
0/12/0
Yes
10
001
01
696
16
1
2/0/6
7/4
2/0/6
No
1
001
01
696
72
3
5/0/3
4/4
2/0/2
Yes
SITE
MCC
MNC
LAC
CI
LCI
NUMBER OF ACTUAL CONNECTED GCIs:
93
NUMBER OF ACTUAL 16K GCIs:
13
RCIs: 13
NUMBER OF ACTUAL 32K GCIs:
24
RCIs: 12
NUMBER OF ACTUAL 64K GCIs:
56
RCIs: 15
The output is explained as follows: PRP: indicates the PRP device ID. (PXP PPROC Device ID equals to PXP DPROC Device ID plus 16.)
3-296
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Configured 16k: indicates the actual configured 16k INS PDTCH number in a specific cell, which is obtained from PCU. Configured 32k: indicates the actual configured 32k INS PDTCH number in a specific cell, which is obtained from PCU. Configured 64k: indicates the actual configured 64k INS PDTCH number in a specific cell, which is obtained from PCU. Database SW: indicates the switchable PDTCH demands configured in the database (sw_pdtch) for a specific cell. Database RES: indicates the reserved PDTCH demands configured in the database (res_pdtch) for a specific cell. GDS 16k: indicates the number of INS 16k GDS actually configured for these specific cells. Currently, this number is exactly equal to the number of configured 16k PDTCHs. GDS 32k: indicates the number of INS 32k GDS actually configured for these specific cells. Currently, this number is exactly equal to the number of configured 32k PDTCHs. GDS 64k: indicates the number of 64k INS GDS DS0 actually configured for all 64k RTF in specific cells. All PD configured: indicates whether all PDTCH demands required in the database are actually configured in the cells. Yes: When the sum of all configured 16k, 32k, 64k INS PDTCH is greater or equal to the sum of switchable (sw_pdtch) and reserved PDTCH (res_pdtch) demands in the database. No: When the sum of all configured 16k, 32k, 64k INS PDTCH is less than the sum of switchable (sw_pdtch) and reserved PDTCH (res_pdtch) demands in the database. NUMBER OF ACTUAL CONNECTED GCIs: indicates the total GCI actually used in this PCU, PRP/PXP DPROC and PPROC. 1 for one 16k GDS, 2 for one 32k GDS and 4 for one 64k GDS. NUMBER OF ACTUAL 16K/32K/64K GCIs: indicates the 16k/32k/64k GCI actually used in this PCU, PRP/PXP DPROC and PPROC. 1 for one 16k GDS, 2 for one 32k GDS and 4 for one 64k GDS. NUMBER OF ACTUAL 16K/32K/64K RCIs: indicates the 16k/32k/64k radio resource actually used in this PCU, PRP/PXP DPROC and PPROC. 1 for one 16k/32k/64k PDTCH. NUMBER OF ACTUAL FREE GCI COUNT: indicates the free 16k GCI in this PCU. The total 16k GCI depends on the number of TRAU GDSs equipped in a PCU. (Only applicable for per PCU query.)
NOTE If EGPRS is not purchased and 2 GDSs are equipped on a PMC, only 124 GCIs can be used. NUMBER OF FREE DS0: indicates the free 64k GDS DS0 in this PCU. It is similar to the number of actual free 16k GCI in 64k DS0 format. (Only applicable for per PCU query.)
68P02901W23-S
3-297 Nov 2009
Examples
Chapter 3: Device/function related commands
NOTE •
Only when FR 34144 (support the usage of idle TCH for packet burst traffic) is enabled, the sum of all configured 16 k, 32 k and 64 k PDTCH is greater than the sum of switchable and reserved PDTCH demands in the database.
•
All reasons of PDTCH shrink (including stolen by voice call, PDTCH OOS, carrier OOS and insufficient GPRS processing or backhaul resources, and so on) and causes the actual PDTCH number to be less than the demands value in the database is treated as NOT all PDTCH configured.
Example 15 {34145} This example displays the information for PXP DPROC 4 0 0 on PCU 0. disp_equipment pcu DPROC 4 0 0 FULL Where:
3-298
is: PCU
location
DPROC
device/function name
4
first identifier
0
second identifier
0
third identifier
FULL
option
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response DPROC id: 4 DPROC type: PXP Hardware Information: PCI Vendor Id: 1146h PCI Device Id: 6750h PCI Revision Id: 1h PCI Type: UNKNOWN HSC Type: UNKNOWN IP Address Information: DPROC (750): 10.0.130.1 Current Cell Mapping: GSM CELL ID
Configured
Database GDS
All PD
16/32/64k
RES/SW
16/32/64k
Configured
---- ------------------------------------
--—
--—
--—
1
001
01
696
26
0
6/0/6
8/4
6/0/6
Yes
10
001
01
696
27
2
0/12/0
8/4
0/12/0
Yes
10
001
01
696
16
1
2/0/6
7/4
2/0/6
No
1
001
01
696
72
3
5/0/3
4/4
2/0/2
Yes
SITE
MCC
MNC
LAC
CI
LCI
NUMBER OF ACTUAL CONNECTED GCIs:
93
NUMBER OF ACTUAL 16K GCIs:
13
RCIs: 13
NUMBER OF ACTUAL 32K GCIs:
24
RCIs: 12
NUMBER OF ACTUAL 64K GCIs:
56
RCIs: 15
Example 16 This example displays information for PPROC 4 0 0 on PCU 0. disp_equipment pcu PPROC 4 0 0 FULL Where:
68P02901W23-S
is: PCU
location
PPROC
device/function name
4
first identifier
0
second identifier
0
third identifier
FULL
option
3-299 Nov 2009
Examples
Chapter 3: Device/function related commands
System response PPROC id: 4 Hardware Information: PCI Vendor Id: 1146h PCI Device Id: 6750h PCI Revision Id: 1h PCI Type: UNKNOWN HSC Type: UNKNOWN IP Address Information: PPROC: 10.0.130.33 Current Cell Mapping: GSM CELL ID SITE
MCC
Configured MNC
LAC
CI
LCI
16/32/64k
All PD
RES/SW
16/32/64k
Configured
---- ------------------------------------
--—
--—
--—
1
001
01
696
26
0
6/0/6
8/4
6/0/6
Yes
10
001
01
696
27
2
0/12/0
8/4
0/12/0
Yes
10
001
01
696
16
1
2/0/6
7/4
2/0/6
No
1
001
01
696
72
3
5/0/3
4/4
2/0/2
Yes
NUMBER OF ACTUAL CONNECTED GCIs:
3-300
Database GDS
93
NUMBER OF ACTUAL 16K GCIs:
13
RCIs: 13
NUMBER OF ACTUAL 32K GCIs:
24
RCIs: 12
NUMBER OF ACTUAL 64K GCIs:
56
RCIs: 15
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 17 {34145} This example attempts to display information for PRP DPROC 4 0 0 on PCU 0 with full option which is rejected due to the same query being performed by the other MMI session.
NOTE The rejection output is similar for the simultaneous PCU, PXP DPROC and PPROC query by several MMI sessions.
disp_equipment pcu DPROC 4 0 0 FULL Where:
is: PCU
location
DPROC
device/function name
4
first identifier
0
second identifier
0
third identifier
FULL
option
System response DPROC id: 4 DPROC type: PRP Hardware Information: PCI Vendor Id: 1146h PCI Device Id: 6750h PCI Revision Id: 1h PCI Type: UNKNOWN HSC Type: UNKNOWN Current Cell Mapping: GSM CELL ID SITE
MCC
MNC
LAC
CI
LCI
Configured
Database GDS
All PD
16/32/64k
RES/SW
16/32/64k
Configured
--—
--—
--—
---- -----------------------------------Command Rejected: System Busy.
68P02901W23-S
3-301 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 18 {30365} In this example, the BSS supports the display of disp_eq CAB with full information for high power Horizon II micro with FRU type as H2MICRO_HIGH_PWR. disp_eq 4 cab 1 0 full Where:
is: 4
location
cab
device/function name
1
first identifier
0
second identifier
FULL
option
System response CABINET identifier: 1 Cabinet type[cabinet_type]: HORIZON2MICRO_EXT Frequency Type[frequency_type]: DCS1800 [4] Hardware Information: FRU: H2MICRO_HIGH_PWR Kit Number: Not Applicable Serial Number: Not Applicable Hardware Version Number: Unavailable PSU: M14 +27 DC Kit Number: Not Applicable Serial Number: Not Applicable Hardware Version Number: Unavailable PSU: No Battery Kit Number: Not Applicable Serial Number: Not Applicable Hardware Version Number: Unavailable
3-302
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 19 {23311A} This example displays RTF when the Extended Range Cell for Data feature is unrestricted (ercgprsOpt = 1), and also ext_timeslots and ext_pdchs are displayed.
NOTE ext_pdchs is not displayed if the Extended Range Cell for Data feature is restricted (ercgprsOpt = 0).
disp_eq 62 rtf 2 0 Where:
is: 62
location
rtf
device/function name
2
first identifier
0
second identifier
System response Capacity of carrier: FULL Type of carrier: NON_BCCH RTF identifier: 2 0 Primary Unique PATH id is: 0 GSM cell to which this carrier is assigned: 001 01
105 6202
Carrier absolute radio freq. channel: 647 Carrier frequency hopping indicators: 255 255 255 255 255 255 255 255 Carrier training sequence codes: 0 0 0 0 0 0 0 0 Number of extended range timeslots allowed[ext_timeslots]: 0 Number of extended range PDCHs allowed[ext_pdchs]: 0 SDCCH load[sd_load]: 4 SDCCH placement priority[sd_priority]: 0 Channel allocation priority[chan_alloc_priority]: 0 Packet Radio Capability[pkt_radio_type]: 32K Half Rate enabled: 0 allow_8k_trau: Yes
68P02901W23-S
3-303 Nov 2009
References
Chapter 3: Device/function related commands
References Related information The hardware requirements and revision levels are given in Release Notes specific to each software release.
Related commands equip on page 3-403
3-304
modify_value on page 3-456
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_exp_config
disp_exp_config ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_exp_config command displays the CM database configuration of the TDM highway expansion at the specified site (either BSC or BTS). Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
Format Syntax disp_exp_config
Input parameters location Specifies the location of the site. Values are: 0 or bsc
BSC
1 - 140
BTS
Example The following example displays the TDM highway configuration of the BSC: disp_exp_config 0 Where:
is: 0
68P02901W23-S
the location
3-305 Nov 2009
Example
Chapter 3: Device/function related commands
System response Highway 0 (CAGE 0) ----------------Connected to highway 1 by EXP 0 (U21 U9) Connected to highway 2 by EXP 1 (U22 U8) Connected to highway 3 by EXP 2 (U23 U7) Highway 1 (CAGE 1) ----------------Connected to highway 0 by EXP 0 (U21 U9) Connected to highway 2 by EXP 1 (U22 U8) Connected to highway 3 by EXP 2 (U23 U7) Highway 2 (CAGE 2) ----------------Connected to highway 0 by EXP 0 (U21 U9) Connected to highway 1 by EXP 1 (U22 U8) Connected to highway 3 by EXP 2 (U23 U7) Highway 3 (CAGE 3) ----------------Connected to highway 0 by EXP 0 (U21 U9) Connected to highway 1 by EXP 1 (U22 U8) Connected to highway 2 by EXP 2 (U23 U7)
3-306
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_flash
disp_flash ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_flash command displays the version information of the current flash EEPROM load. Use this command to view the software version number, EEPROM creation date, checksum, and size. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
Format Syntax disp_flash
Input parameters There are no input parameters associated with this command.
Example The following example shows the version information of the flash EEPROM: disp_flash
68P02901W23-S
3-307 Nov 2009
Example
Chapter 3: Device/function related commands
System response Version : Date
: 01/04/97
Checksum: Size
1.5.0.0.8 23:51
0x3D691A2
: 838702 Bytes
Where:
3-308
is: Version
the version of the software the system is currently running.
Date
the date and time the current Flash EEPROM load was created. The date is in date/month/year format.
Checksum
the checksum value of the current Flash EEPROM load.
Size
the size of the current EEPROM load, measured in bytes.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_gclk_avgs
disp_gclk_avgs ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_gclk_avgs command displays the Long Term Average (LTA) values for a specific GCLK. The system reads the clock frequency register of each GCLK once every half hour after synchronization if the GCLK is phase locked. A rolling average for each GCLK is calculated of up to 48 clock frequency register readings. This average is the LTA. Security level
1
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
This command is not allowed while in SYSGEN ON mode. This command is not allowed for M-Cell sites.
Format Syntax disp_gclk_avgs
Input parameters location Specifies the location of the GCLK. Values are: 0 or bsc
BSC
1 - 140
BTS
gclk_id Identifier for GCLK. Values are 0 or 1.
68P02901W23-S
3-309 Nov 2009
Example
Chapter 3: Device/function related commands
Example In this example, the LTA values for GCLK 1 at BSC 0 are displayed: disp_gclk_avgs 0 1 Where:
is: 0
location
1
gclk ID
System response The GCLK 1 0 0 Frequency Register values at Site 0 are:
80 80 80 80 8F 8F
Long Term Average = 80 Since the system reads the frequency every 30 minutes, these six samples represent 3 hours. The first value in the display is the oldest. 80 is the value of a GCLK calibrated to 16.384 MHz.
References Related information An alarm is generated if 25% or more of the stored clock frequency readings differ from the calculated LTA by more than the value that is defined by the lta_alarm_range parameter.
Related command clear_gclk_avgs on page 3-173.
3-310
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_gclk_cal
disp_gclk_cal ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_gclk_cal command displays the contents of the clock frequency register when the GCLK is in the phase-lock mode. The clock frequency register gives an indication of the calibration status of the GCLK. When the command is entered the system displays a value in hexadecimal figures. A perfectly calibrated clock displays a reading of 80. Any value more than or less than 80 indicates the degree the GCLK calibration has drifted. As the GCLK ages the value shown in the clock frequency register drifts towards the upper or lower level GCLK calibration limits. If the upper or lower calibration thresholds are met or exceeded, the system generates a recalibration alarm. Using the clock frequency register value can give an estimate of how far the GCLK has drifted from its original calibration and how long it is until the GCLK requires recalibration. Since each GCLK has different aging characteristics, this estimate is not exact. •
The upper level of all GCLKs is E9 (hexadecimal).
•
The lower level is 38 (hex) for revisions 0 through 8.
•
The lower level is 1a (hex) for revision 9.
Use the disp_hardware_version command to view the revision number. This command also reports if the clock is not in phase lock. Security level
1
Supported by OMC GUI-R
No
Command type
A (no operator actions)
Prerequisites
This command is not allowed while in the SYSGEN ON mode. This command is not allowed for M-Cell sites.
Format Syntax disp_gclk_cal
68P02901W23-S
3-311 Nov 2009
Examples
Chapter 3: Device/function related commands
Input parameters location Specifies the location of the GCLK: 0 or bsc
BSC
1 - 140
BTS
gclk_id Specifies the identity of the GCLK. Values are 0 or 1.
Examples Example 1 In this example, GCLK 0 at BSC 0 is not in phase lock mode: disp_gclk_cal 0 0 Where:
is: 0
location
0
gclk_id
System response GCLK 0 0 0 not in phase lock
Example 2 In this example, GCLK 0 at BSC 0 is in phase lock mode: disp_gclk_cal 0 0 Where:
is: 0
location
0
gclk_id
System response GCLK 0 Clock frequency register value = 99
3-312
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
References Related information The system reads the clock frequency register of each GCLK once every half hour after synchronization after the GCLK has phase_locked. A rolling average for each GCLK is calculated of up to 48 clock frequency register readings. This average is the Long Term Average (LTA). An alarm generates if 25% or more of the stored clock frequency readings differ from the calculated LTA by more than the value that is defined by the lta_alarm_range parameter.
Related commands clear_gclk_avgs on page 3-173
68P02901W23-S
disp_gclk_avgs on page 3-309
3-313 Nov 2009
disp_gsm_cells
Chapter 3: Device/function related commands
disp_gsm_cells ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_gsm_cells command displays the GSM cells associated with a specific site (BTS or BSC). Both primary and secondary frequencies are displayed for Dual Band Cells. Primary and secondary frequency types are displayed for dual band cells. Security level
1
Command type
A (no operator actions)
Prerequisites
None
Format Syntax disp_gsm_cells
Input parameter location Specifies the site for which associated GSM cells are to be displayed: 0 or bsc
BSC
1 - 140
BTS
Examples Example 1 In this example, no GSM cells are associated with the BSC: disp_gsm_cells 0 Where:
is: 0
3-314
location
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response There are no associated GSM cells
Example 2 In this example, the GSM cells associated with a BTS are displayed: disp_gsm_cells 11 Where:
is: 11
location
System response Associated GSM cells: GSM CELL ID Freq MCC
MNC
---
---
---------------
543
21
61713 (0xF111h)
RAC: 543
21
RAC: 543
21
RAC:
LAC
8
(0x8h)
BVCI:
61713 (0xF111h) 96 (0x60h)
BVCI:
61713 (0xF111h) N/A
BVCI:
Number of Sectors:
68P02901W23-S
CI -------------4368 (0x1110h)
LCI
Type
Cell Name
--- ----- ---------------0
EGSM
london-south
1
EGSM
london-north
2
EGSM
bexley-west
N/A 8736 (0x2220h) N/A 13114 (0x222Ah)
N/A 3
3-315 Nov 2009
References
Chapter 3: Device/function related commands
References Related commands add_cell on page 3-22
copy_cell on page 3-179
del_cell on page 3-192
disp_cell on page 3-241
3-316
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_hdlc
disp_hdlc ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_hdlc command displays the HDLC channel assignment types of an in-service GPROC device or function. This command permits retrieval of: •
Device, function, and CPU values.
•
The channel configuration and status for every HDLC channel on a GPROC device.
•
The total number of LAPD devices (RSLs or XBLs) equipped on a GPROC device.
•
An indication whether the current HDLC layout matches the current database settings.
•
Channels allocated to GSLs when the GPRS feature is unrestricted at the site.
Security level
1
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
The disp_hdlc command cannot be used for CSPF GPROCs or M-Cell sites.
Format Syntax disp_hdlc
Input parameters location Specifies the equipment location: 0 or bsc
BSC
1 - 140
BTS
all
All sites
68P02901W23-S
3-317 Nov 2009
Example
Chapter 3: Device/function related commands
dev/func name Literal that uniquely identifies the device or function dev/func_id_1 First device or function identifier. dev_func_id_2 Second device or function identifier. dev_func_id_3 Third device or function identifier.
Example Example 1 This example shows how to display the HDLC channel assignments for BSP 0 0 0 at the BSC. disp_hdlc bsc BSP 0 0 0 Where:
is: bsc
location
BSP
device / function name
0
device / function ID
0
device / function ID
0
device / function ID
System response Device:
BSP 0 0 0 (CPU ID: 0x0115)
Function: N/A Number of LAPD Static Links (RSLs/XBLs) allocated to current board: HDLC Channel Range
3-318
1
HDLC Channel Offset 0
1
2
3
------------
----------------------------------------------------
00-03
Test Free
OML 0 0 0
OML Free
OML Free
04-07
OML Free
XBL 0 0 0
RSL Free
RSL Free
08-11
RSL Free
RSL Free
RSL Free
RSL Free
12-15
RSL Free
RSL Free
RSL Free
RSL Free
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Example
Example 2 {28337} This example displays the HDLC channel assignments for LCF 2 0 which has HSP MTL. disp_hdlc 0 lcf 2 Where:
is: 0
location
lcf
device/function name
2
device/function ID
System response Device:
GPROC 5 0 0 (CPU ID: 0x0114)
Function: LCF 2 0 0
Number of static LAPD Links (RSLs/XBLs) allocated to current board: N/A
Legend: G/RSL = Free channel configured for a GSL or RSL.
HDLC Channel
Range
HDLC Channel Offset
0
1
2
3
------------
----------------------------------------------------------------
00-03
Test Free
MTL 1 0 0
MTL 1 0 0
MTL 1 0 0
04-07
MTL 1 0 0
MTL 1 0 0
MTL 1 0 0
MTL 1 0 0
08-11
MTL 1 0 0
MTL 1 0 0
MTL 1 0 0
MTL 1 0 0
12-15
MTL 1 0 0
MTL 1 0 0
MTL 1 0 0
MTL 1 0 0
16-19
MTL 1 0 0
MTL 1 0 0
MTL 1 0 0
MTL 1 0 0
20-23
MTL 1 0 0
MTL 1 0 0
MTL 1 0 0
MTL 1 0 0
24-27
MTL 1 0 0
MTL 1 0 0
MTL 1 0 0
MTL 1 0 0
28-31
MTL 1 0 0
MTL 1 0 0
MTL 1 0 0
MTL 1 0 0
68P02901W23-S
3-319 Nov 2009
disp_hopping
Chapter 3: Device/function related commands
disp_hopping ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_hopping command displays the hopping information for a cell (identified by cell_desc), based on the arguments entered with the command.
cell_desc only If the cell_desc only is entered, the command displays hopping systems for the specific cell. The following information is displayed: •
Frequency hopping indicators (fhi).
•
Hopping sequence numbers.
•
Mobile allocations.
cell_desc and fhi If the fhi is entered along with the cell_desc, a more detailed output of the particular hopping systems is provided. The following information is displayed: •
Carriers that are using the specified hopping system.
•
Timeslots that are using the specified hopping system.
cell_desc and ‘active’ string If the string ‘active’ is entered together with the cell_desc, all of the currently active hopping systems for the cell are displayed. The following information is displayed:
3-320
•
Active hopping systems on a carrier and timeslot basis.
•
Frequency hopping indicators (FHIs).
•
Hopping sequence numbers (HSNs) for each FHI.
•
Mobile allocations.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
Security level
1
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
This command is not allowed while in SYSGEN ON mode when the ‘active’ option is used.
Operator actions
Place the system in the SYSGEN OFF mode if the ‘active’ option is used before entering this command.
Format Syntax disp_hopping [active] disp_hopping [ | active]
Input parameters site Specifies the location: 0 or bsc
BSC
1 - 140
BTS
The system rejects the disp_hopping command at a BTS if the specified cell or site is not local. cell_desc Identifies the GSM cell ID of the cell for which the hopping information is to be displayed, preceded by cell_number=. The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900)
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks and be preceded by cell_name=.
68P02901W23-S
3-321 Nov 2009
Examples
Chapter 3: Device/function related commands
NOTE This command responds to the shortened input parameter cell= allowing entry of either the cell_number or the cell_name without further definition.
fhi Frequency hopping indicator. active The active option displays the currently active hopping systems.
Examples Example 1 In this example, only the GSM cell ID in seven parameter format is entered and the related hopping information for the cell is displayed. disp_hopping cell_number=5 4 3 2 1 61986 34944 Where:
is: 5 4 3 2 1 61986 34944
cell_desc
The example below shows the same cell number in four parameter format: disp_hopping cell_number=543 21 61986 34944 Where:
is: 543 21 61986 34944
cell_desc
System response GSM CELL: 543 21 61986 (f222h) 34944 (8880h) Baseband (BBH) Hopping
3-322
FHI: 0
HSN = 0
MA = 12 30 45
FHI: 1
HSN = 7
MA = 31 37 50
FHI: 2
HSN = 9
MA = 31 32 33 34 45 46
FHI: 3
HSN = 12
MA = 33 76 91
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 2 In this example, the fhi is entered together with the GSM cell ID. The output contains the carriers using the hopping system number in addition to all of the timeslots for each carrier. disp_hopping cell_number=5 4 3 2 1 61986 34944 1 Where:
is: 5 4 3 2 1 61986 34944
cell_desc
1
fhi
System response GSM CELL: 543 21 61986 (f222h) 34944 (8880h) Carrier arfcn:
33 Timeslots:
0 1
Carrier arfcn:
76 Timeslots:
1 2 3 5 7
Carrier arfcn:
91 Timeslots:
0 1 2 3 4 5 6 7
Example 3 In this example, the ‘active’ string is entered together with the GSM cell Id. disp_hopping cell_number=5 4 3 2 1 61986 34944 active Where:
is: 5 4 3 2 1 61986 34944
cell_desc
active
‘active’ string
System response GSM CELL: 543 21 61986 (f222h) 34944 (8880h)
Active Hopping Systems:
Carrier arfcn: 33
Timeslot: 0
FHI: 3
HSN: 0
MA: 33 76 91
Timeslot: 1
FHI: 3
HSN: 0
MA: 33 76 91
Timeslot: 2
FHI: 0xFF
HSN: 0
MA: (no MA)
68P02901W23-S
3-323 Nov 2009
References
Chapter 3: Device/function related commands
References Related command chg_element on page 3-106.
3-324
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_level
disp_level ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_level command displays the current security level. Security level
4
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
None
Format Syntax disp_level
Input parameters There are no input parameters associated with this command.
Example This example displays the output of the disp_level command. disp_level
System response Current security level is 1
References Related commands chg_level on page 3-142
68P02901W23-S
sysgen_mode on page 3-540
3-325 Nov 2009
disp_link
Chapter 3: Device/function related commands
disp_link ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_link command displays RXCDR, OML, MTL, and CBL links between two sites. The sites are the BSC) and either the MSC, the OMC, or the Cell Broadcast Centre, when an RXCDR is being used. Security level
1
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
This command is only available on an RXCDR.
Format Syntax disp_link
Input parameters There are no input parameters associated with this command.
Example In this example, the RXCDR OML and RXCDR MTL links between the BSC and the MSC are displayed: disp_link
3-326
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Example
System response The CEPT nailed connections are as follows:-
Incoming mms id: 0 0 Timeslot: 16 Outgoing MMS Id 1 0 Timeslot: 16
incoming mms id: 0 0 Timeslot: 17 Outgoing MMS Id 1 0 Timeslot: 17
incoming mms id: 0 0 Timeslot: 18 Outgoing MMS Id 1 0 Timeslot: 18
incoming mms id: 0 0 Timeslot: 19 Outgoing MMS Id 1 0 Timeslot: 19
incoming mms id: 0 0 Timeslot: 20 Outgoing MMS Id 1 0 Timeslot: 20
incoming mms id: 0 0 Timeslot: 21 Outgoing MMS Id 1 0 Timeslot: 21
incoming mms id: 0 0 Timeslot: 22 Outgoing MMS Id 1 0 Timeslot: 22
incoming mms id: 0 0 Timeslot: 23 Outgoing MMS Id 1 0 Timeslot: 23
incoming mms id: 0 0 Timeslot: 24 Outgoing MMS Id 1 0 Timeslot: 24
incoming mms id: 0 0 Timeslot: 25 Outgoing MMS Id 1 0 Timeslot: 25
Finished displaying all nailed connections
68P02901W23-S
3-327 Nov 2009
disp_link_usage
Chapter 3: Device/function related commands
disp_link_usage ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_link_usage command displays all PATH devices equipped through a particular MSI/MMS combination at a site. The output from this command is system configuration dependent. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
An MSI and an MMS must be equipped at the site_device.
Format Syntax disp_link_usage
Input parameters location Specifies the location of PATH device: 0 or bsc
Indicates that the MSI/MMS combination is at the BSC
0 to 140
Indicates the site number of the BTS, if the MSI/MMS combination is at a BTS
MSI_identifier Specifies the MSI identifier to be displayed. {22169} 0 to 95
the MSI is at the BSC.
0 to 9
the MSI is at a BTS.
MMS_identifier Specifies the MMS identifier to be displayed. Values are 0 or 1.
3-328
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Example
Example This example displays the PATH devices equipped on MSI/MMS combination 1 0 at site 1. disp_link_usage 1 1 0 Where:
is: 1
location
1
MSI_identifier
0
MMS_identifier
System response Start of Report:
End of Report
SITE ID : 1 MSI ID
: 1
MMS ID
: 0
PATH 1 0 0 PATH 2 0 0 PATH 3 0 0 PATH 4 0 0 PATH 5 0 0 PATH 6 0 0 PATH 7 0 0 PATH 8 0 0 PATH 9 0 0
68P02901W23-S
3-329 Nov 2009
disp_mms_ts_usage
Chapter 3: Device/function related commands
disp_mms_ts_usage ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_mms_ts_usage command displays the timeslot usage on any MMS link. The output gives the status of each timeslot in the form of: •
Unavailable for use (UNAVAILABLE)
•
Unallocated (UNUSED)
•
Allocated to RSL (RSL)
•
Allocated to RTF (RTF)
•
Allocated to GBL (GBL)
•
Allocated to GSL (GSL)
•
Allocated to GDS (GPRS_DATA)
•
Allocated to XBL (XBL)
•
Allocated to OML (OML)
•
Allocated to MTL (MTL)
•
Allocated to terrestrial circuit (CIC)
•
Allocated to CBL (CBL)
•
Allocated to RXCDR link (RXCDR_LINK)
•
Reserved (RESERVED)
•
Nailed (NAILED)
•
Nailed on a path (NAILED PATH Timeslot Usage)
It also displays the timeslots that are reserved for dynamic allocation.
NOTE 16K_DYN_RSL always falls under a 16 K RSL timeslot as the first group. It indicates that 3 extra timeslots are reserved for dynamic allocation.
3-330
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
The display includes the device or function identifiers and the site where the device or function is equipped. {27508} Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
To display timeslot usage at a PCU, the GPRS feature must be unrestricted.
Format Syntax disp_mms_ts_usage
Input parameters location Specifies the location of the device: 0 or bsc
BSC
1 - 140
BTS
{27955A} pcu or pcu_0
PCU
mms_id1 Specifies the 1st digit of the MMS identifier, accordingly: 0 to 5: 0 to 1 is valid for MMS range for MCell-2. 0 to 3 is valid for MMS range for MCell-6. 0 is valid for MMS for MCell micro. mms_id2 Specifies the 2nd digit of the MMS identifier. The header in the display depends on where the MMS is being viewed. •
If the MMS is viewed from a BSC and RXCDR, the header looks like this: TS Port Size Usage Device ID Type Site CIC State RTF Site RTF TS
68P02901W23-S
3-331 Nov 2009
Examples
Chapter 3: Device/function related commands
•
If the MMS is viewed from a BTS, the header looks like this: TS
•
Group
Usage
Device ID
Type
Site
TS
If the MMS is for an HDSL link, only the top line of the display changes slightly to look like this: Site:
3
HDSL (32 timeslot)
MMS: 0 0
The remainder of the display is the same as shown in the examples that follow.
NOTE Using this command with the Integrated MCell HDSL feature enabled, disp_mms_ts_usage indicates whether the MMS supports a 16 or 32 kbit/s timeslot HDSL link.
Examples Example 1 This example displays timeslot usage on a span at site 0 (BSC), MMS 1 0. disp_mms_ts_usage 0 1 0 Where:
is: 0
location
1
1st digit of MMS identifier
0
2nd digit of MMS identifier
System Response Start of Report: Site: 0 MMS: 1 0 General Timeslot Usage: TS
3-332
Port Size
Usage
Device ID
Type
Site
CIC State
RTF
Site RTF
TS
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
0 1
2
3
Examples
UNAVAILABLE 0-1
Ater*
1
IDLE
2-3
Ater*
2
IDLE
4-5
Ater*
3
IDLE
6-7
Ater*
4
IDLE
0-1
Ater*
5
IDLE
2-3
Ater*
6
IDLE
4-5
Ater*
7
IDLE
6-7
Ater*
8
IDLE
0-1
Ater
9
IDLE
2-3
Ater
10
IDLE
4-5
Ater
IDLE
6-7
Ater
IDLE
4
64 K_XBL
128 0 0
64 K
0
5
0-7
Ater
IDLE
6
0-1
Ater
IDLE
2-3
Ater
IDLE
4-5
Ater
IDLE
6-7
Ater
IDLE
7
0-7
Ater
IDLE
8
0-7
Ater
IDLE
9
0-7
Ater
IDLE
68P02901W23-S
3-333 Nov 2009
Examples
Chapter 3: Device/function related commands
10
0-7
Ater
IDLE
11
0-7
Ater
IDLE
12
0-7
Ater
IDLE
13
0-7
Ater
IDLE
14
0-7
Ater
IDLE
15
0-7
Ater
IDLE
16
0-7
Ater
IDLE
17
0-7
Ater
IDLE
19
0-7
Ater
IDLE
20
0-7
Ater
IDLE
21
0-7
Ater
IDLE
22
0-7
Ater
IDLE
23
0-7
Ater
IDLE
24
0-7
Ater
IDLE
25
0-7
Ater
IDLE
26
0-7
Ater
IDLE
27
0-7
Ater
IDLE
28
0-7
Ater
IDLE
29
0-7
Ater
IDLE
30
0-7
Ater
IDLE
31
0-7
Ater
IDLE
Ater*: Timeslot is an Ater but has CIC(s) equipped on it.
3-334
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
End of Report.
Example 2 This example displays the output on an RXCDR MMS showing the status of Ater channels, the Ater channel status, and CICs assigned to the Ater channels. disp_mms_ts_usage 0 18 0 Where:
is: 0
location
18
1st digit of MMS identifier
0
2nd digit of MMS identifier
System response Start of Report: Site: 0
MMS: 18 0
General Timeslot Usage: A S S O C I A T E D TS Port Usage
Device ID
Type
BSS State
CIC
MMS
TS Port
Size 0 1
UNAVAILABLE 0-1
Ater
UNKNOWN
2-3
Ater*
UNKNOWN
63
4 0
31
4-5
Ater*
UNKNOWN
62
4 0
30
6-7
Ater
UNKNOWN
2 3
Size
64 K_XBL
2 1 0
64 K
0
0-1
Ater*
UNKNOWN
36
4 0
4
2-3
Ater*
UNKNOWN
35
4 0
3
68P02901W23-S
3-335 Nov 2009
Examples
Chapter 3: Device/function related commands
4
4-5
Ater*
UNKNOWN
34
4 0
2
6-7
Ater*
UNKNOWN
33
4 0
1
0-1
Ater*
UNKNOWN
40
4 0
8
2-3
Ater*
UNKNOWN
39
4 0
7
Ater*:
Timeslot is an Ater but has CIC(s) equipped on it.
End of Report.
Example 3 The following example displays the timeslot utilization on MMS 0 0 at the BSC, with a 16 kbit/s XBL equipped on timeslot 8, group 3 and a 64 kbit/s XBL equipped on timeslot 9. disp_mms_ts_usage 0 0 0 Where:
is: 0
location
0
1st digit of MMS identifier
0
2nd digit of MMS identifier
System response: Site: 0 MMS: 0
0
General Timeslot Usage:
3-336
TS Usage Device ID Type Site CIC Group CIC State TS Group
RTF Site RTF TS
TS Usage Device ID Type Site CIC Group CIC State TS Group
RTF Site RTF TS
0
UNAVAILABLE
1
CIC
60
0
IDLE
CIC
61
1
IDLE
CIC
62
2
IDLE
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
CIC
63
3
IDLE
CIC
64
0
IDLE
CIC
65
1
IDLE
CIC
66
2
IDLE
CIC
67
3
IDLE
3
CIC
68
0
IDLE
4
NAILED
5
UNUSED
6
UNUSED
7
RESERVED
8
CIC
64
0
IDLE
CIC
65
1
IDLE
CIC
66
2
IDLE
2
9
0 1 0
11
XBL
1 0 0
16
0
XBL
2 0 0
64
0
3
10 UNUSED 11 UNUSED 12 UNUSED 13 UNUSED 14 UNUSED 15 UNUSED 16 MTL
68P02901W23-S
3 0 0
0
3-337 Nov 2009
Examples
Chapter 3: Device/function related commands
17 NAILED
1 0 0
17
18 UNUSED 19 UNUSED 20 UNUSED 21 UNUSED 22 UNUSED 23 UNUSED 24 UNUSED 25 UNUSED 26 UNUSED 27 UNUSED 28 UNUSED 29 UNUSED 30 UNUSED 31 UNUSED
Example 4 This example displays the timeslot usage for an E1 link supporting a GBL. The link runs from a PICP MMS in PCU 0 cabinet to the SGSN. disp_mms_ts_usage pcu_0 6 0 Where:
3-338
is: pcu_0
location
6
1st digit of MMS identifier
0
2nd digit of MMS identifier
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response Start of Report: Site: PCU_0 MMS: 6 0 General Timeslot Usage: TS
Usage
0
UNAVAILABLE
1
UNUSED
2
GBL
0 0 0
PCU_0
3
GBL
0 0 0
PCU_0
4
GBL
0 0 0
PCU_0
5
GBL
0 0 0
PCU_0
6
GBL
0 0 0
PCU_0
7
GBL
0 0 0
PCU_0
8
GBL
0 0 0
PCU_0
9
GBL
0 0 0
PCU_0
10
GBL
0 0 0
PCU_0
11
GBL
0 0 0
PCU_0
12
UNUSED
13
UNUSED
14
UNUSED
68P02901W23-S
Device ID
Site
3-339 Nov 2009
Examples
Chapter 3: Device/function related commands
15
UNUSED
16
UNUSED
17
UNUSED
18
UNUSED
19
UNUSED
20
UNUSED
21
UNUSED
22
UNUSED
23
UNUSED
24
UNUSED
25
UNUSED
26
UNUSED
27
UNUSED
28
UNUSED
29
UNUSED
30
UNUSED
31
UNUSED
End of Report.
3-340
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 5 {28337} This example displays the timeslot usage on MMS which includes the HSP MTL. disp_mms_ts_usage 0 8 0 Where:
is: 0
location
8
1st digit of MMS identifier
0
2nd digit of MMS identifier
System response Start of Report: Site: 0
MMS: 8 0
General Timeslot Usage: TS Port
Usage
Device ID
Size
Type Site
CIC
RTF
Site
0
UNAVAILABLE
1
MTL
0 0 0
0
2
MTL
0 0 0
0
3
MTL
0 0 0
0
4
MTL
0 0 0
0
5
MTL
0 0 0
0
6
MTL
0 0 0
0
7
MTL
0 0 0
0
8
MTL
0 0 0
0
9
MTL
0 0 0
0
10
MTL
0 0 0
0
11
MTL
0 0 0
0
12
MTL
0 0 0
0
13
MTL
0 0 0
0
68P02901W23-S
State RTF
TS
3-341 Nov 2009
References
Chapter 3: Device/function related commands
14
MTL
0 0 0
0
15
MTL
0 0 0
0
16
MTL
0 0 0
0
17
MTL
0 0 0
0
18
MTL
0 0 0
0
19
MTL
0 0 0
0
20
MTL
0 0 0
0
21
MTL
0 0 0
0
22
MTL
0 0 0
0
23
MTL
0 0 0
0
24
MTL
0 0 0
0
25
MTL
0 0 0
0
26
MTL
0 0 0
0
27
MTL
0 0 0
0
28
MTL
0 0 0
0
29
MTL
0 0 0
0
30
MTL
0 0 0
0
31
MTL
0 0 0
0
End of Report.
References Related information The timeslots states display as UNKNOWN when running in sysgen mode.
Related command chg_ts_usage on page 3-161.
3-342
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_neighbor
disp_neighbor ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_neighbor command displays information of a specific neighbor cell or all neighbor cells. It also displays additional information for UTRAN and Blind Search neighbor cells. A neighbor cell can be internal or external. An internal neighbor cell is inside the BSS in which the source cell is located. An external neighbor cell is outside of the BSS in which the source cell is located. The cell_name created using the cell_name command is used to specify the source cell in place of the src_gsm_cell_id. A cell_name is also used to specify an internal neighbor cell in place of the neighbor_cell_id. A cell_name cannot be used to specify an external neighbor cell. When the all option is used, the cell_name for each of the internal neighbor cells is displayed immediately after the neighbor_cell_id. If a cell_name has not been assigned to a neighbor_cell_id, No Name Defined is presented in the Neighbor cell name field. The cell_name for an external neighbor cell is not displayed. If a neighbor cell is an external cell, N/A. is presented in the Neighbor cell name field. If the Inter_RAT (Radio Access Technology) Handover and/or the Enhanced 2G/3G Handover features are unrestricted, this command supports the UTRAN cell identity format. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
For handovers to UTRAN cells, the Inter-RAT handover feature and/or the Enhanced 2G/3G Handover feature must be unrestricted.
Format Syntax disp_neighbor [|all] disp_neighbor [TEST ]
68P02901W23-S
3-343 Nov 2009
Examples
Chapter 3: Device/function related commands
Input parameters src_cell_desc GSM cell ID of the neighbor list owner cell to be displayed. GSM or UTRAN Cell ID of the neighbor list owner cell to be displayed. The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900)
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks. neighbor_cell_desc GSM cell ID of a neighbor cell. The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900)
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, it must be placed inside double quotation marks. test neighbor_cell_desc A test cell can be created to be used for testing. This argument is entered using the string TEST, a space, and a test cell number (1 to 64). An asterisk character (*) is used in place of a test cell number to indicate all test neighbors.
Examples The examples below are possible displays. If the pbgt_alg_type for a cell is any number between 3 and 7 or the adj_chan_intf_test for a cell equals ‘yes’ or 1, the system presents additional prompts. Refer to the description of the add_neighbor command for the prompted power budget parameter values.
3-344
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 1 In this example, a cell has no neighbor cells. This example uses the seven parameter format for the cell number. disp_neighbor 5 4 3 2 1 61986 34944 all Where:
is: 5 4 3 2 1 61986 34944
src_cell_desc
all
all neighbor cells
The example below shows the same cell number in the four parameter format: disp_neighbor 543 21 61986 34944 all Where:
is: 543 21 61986 34944
src_cell_desc
all
all neighbor cells
System response There are no associated neighbor cells
Example 2 In this example, the information describing a neighbor cell is displayed. disp_neighbor 0 0 1 0 1 1 4 0 0 1 0 1 1 1 Where:
is: 0010114
src_cell_desc
0010111
neighbor_cell_desc
System response Neighbor cell id:
00101 1 (0001h) 1 (0001h)
Neighbor cell name:
N/A
Neighbor cell frequency type:
PGSM
Placement:
External
Synchronization enabled:
N/A
Frequency in the ba_sacch list:
1(yes)
Frequency in the ba_bcch list:
1(yes)
68P02901W23-S
3-345 Nov 2009
Examples
Chapter 3: Device/function related commands
BCCH frequency number:
60
Base station identity code:
16
MS transmit power maximum:
37
Neighbor receive level minimum:
15
Neighbor handover margin:
8
Power budget surrounding cell hreqave:
8
Receive quality handover margin:
-63
Receive level handover margin:
-63
Neighbor type 5 handover margin:
63
Neighbor adaptive handover pbgt trigger:
40
Adjacent channel interference test enabled:
0 (no)
Power budget algorithm type:
1
Neighbor congestion handover margin:
8
Range of the neighbor cell:
Normal
End of report
Example 3 In this example, the information describing all of the neighbor cells is displayed. The cell name ‘london-north’ is used in place of the src_cell_desc. disp_neighbor “london-north” all Where:
is: london-north
cell_name
all
all internal neighbor cells
System response Neighbor cell id: Neighbor cell name:
54 3 2 1 633 347 london-south
Placement:
Internal
Synchronization enabled:
1
Frequency in the ba_sacch list:
1
Frequency in the ba_bcch list:
0
BCCH frequency number:
60
Base station identity code (bsic):
16
MS transmit power maximum:
37
Neighbor receive level minimum:
15
Neighbor handover margin:
8
Power budget surrounding cell hreqave:
9
Adjacent channel interference test enabled: 0 (no)
3-346
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Power budget algorithm type:
7
Adjacent channel intf detection ho margin:
-5
Neighbor congestion handover margin:
-8
Neighbor cell id:
54 3 2 1 633 348
Neighbor cell name:
No Name Defined
Placement:
Internal
Synchronization enabled:
1
Frequency in the ba_sacch list:
1
Frequency in the ba_bcch list:
0
BCCH frequency number:
60
Base station identity code (bsic):
16
MS transmit power maximum:
37
Neighbor receive level minimum:
15
Neighbor handover margin:
8
Power budget surrounding cell hreqave:
9
Adjacent channel interference test enabled: 0 (no) Power budget algorithm type:
7
Adjacent channel intf detection ho margin:
-5
Neighbor congestion handover margin:
-8
Neighbor cell id:
5 4 3 2 1 633 349
Neighbor cell name:
N/A
Placement:
External
Synchronization enabled:
N/A
Frequency in the ba_sacch list:
1
Frequency in the ba_bcch list:
0
BCCH frequency number:
100
Base station identity code (bsic):
50
MS transmit power maximum:
37
Neighbor receive level minimum:
15
Neighbor handover margin:
8
Power budget surrounding cell hreqave:
9
Adjacent channel interference test enabled: 0 (no) Power budget algorithm type:
7
Adjacent channel intf detection ho margin:
-5
68P02901W23-S
3-347 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 4 This example displays the information for all test cells. disp_neighbor 5 4 3 2 1 619 394 TEST * Where:
is: 5 4 3 2 1 619 394
src_cell_desc
TEST *
all test cells
System response MCC MNC
LAC
CI
--------------------------------
LOC SYNC SACCH
BCCH
FREQ
BSIC
-------
-----
----
----
----
TEST 7
N/A
N/A
NO
YES
91
N/A
TEST 12
N/A
N/A
YES
YES
101
N/A
BA_
BCCH
GSM CELL ID
Example 5 This example displays the information for an external neighbor cell with the Multiband Inter-Cell Handover feature enabled. disp_neighbor 0 0 1 0 1 1 1 0 0 1 0 1 1 2 Where:
is: 0010111
src_cell_desc
0010112
neighbor_cell_desc
System response Neighbor cell id:
3-348
00101
1 (0001h) 2 (0002h)
Neighbor cell name:
N/A
Neighbor cell frequency type:
PGSM
Placement:
Internal
Synchronization enabled:
0(no)
Frequency in the ba_sacch list:
1(yes)
Frequency in the ba_bcch list:
1(yes)
BCCH frequency number:
60
Base station identity code:
16
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
MS transmit power maximum:
37
Neighbor receive level minimum:
15
Neighbor handover margin:
8
Power budget surrounding cell hreqave:
8
Receive quality handover margin:
-63
Receive level handover margin:
-63
Neighbor type 5 handover margin:
63
Neighbor adaptive handover pbgt trigger:
40
Adjacent channel interference test enabled:
0 (no)
Power budget algorithm type:
1
Neighbor congestion handover margin:
8
Range of the neighbor cell:
Normal
Example 6 This example displays the information for all neighbor cells associated with a cell when the Network Controlled cell reselection feature is enabled. disp_neighbor 0 0 1 0 1 1 1 Where:
is: 0010111
src_cell_desc
System response Start of neighbor report: S
GSM CELL ID MCC MNC
LAC
CI
LOC SYNC
A
B
G
C
C
P
C
C
R
FREQ
BCCH
H
H
S
TYPE
FREQ BSIC
---------------------------------- --- ----
-------
------- ---- ----
001 01
1 (0001h)
6
(0006h)
INT NO
X
X
X
PGSM
75
16
001 01
1 (0001h)
3
(0003h)
INT NO
X
X
X
PGSM
30
16
001 01
1 (0001h)
33 (0021h)
INT NO
X
X
X
PGSM
10
16
001 01
1 (0001h)
41 (0029h)
INT NO
X
X
X
PGSM
90
16
001 01
1 (0001h)
11 (000Bh)
EXT N/A
X
X
X
EGSM
80
16
001 01
1 (0001h)
90 (005Ah)
EXT N/A
X
X
X
PGSM
17
16
End of report
68P02901W23-S
3-349 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 7 This example displays UTRAN cell 4 9 6 2 3 1 1 1 1 as a neighbor of GSM cell 0 0 1 0 1 1 4. disp_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 Where:
is: 0010114
src_cell_desc
496231111
neighbor_cell_desc
System response Start of neighbor report: UTRAN cell id:
496 231 1 (0001h) 1 (0001h) 1 (0001h)
UTRAN BCCH Neighbor:
Yes
UTRAN SACCH Neighbor:
Yes
FDD-ARFCN:
10762
Scrambling code:
200
Diversity enabled:
0 (no)
UMTS measurement margin:
3
Neighbor measurement avg period:
6
End of report
Example 8 This example displays neighbors of GSM cell 0 0 1 0 1 1 4, which has two GSM neighbors, two UTRAN neighbors and two Blind Search neighbors. disp_neighbor 0 0 1 0 1 1 4 Where:
is: 0010114
src_cell_desc
System response Start of neighbor report: S
UTRAN CELL ID
3-350
C
A
B
C
C
C
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
MCC MNC
LAC
Examples
RNC id
CI
H
H
ARFCN SC
DF
---------------------------------------------
-----
----- --- --
496 231
1 (0001h)
1 (0001h)
1 (0001h)
X
X
10762 200
1
496 231
1 (0001h)
2 (0001h)
1 (0001h)
X
X
10762 201
0
Blind Search FDD-ARFCN ---------------------10765 10786 S
GSM CELL ID MCC MNC
C
LAC
CI
C
A
B
G
C
C
P
R
LOC SYNC
FREQ H
H
S
BCCH TYPE
FREQ BSIC
------------------------------------ --- ----
-------
001 01
1 (0001h)
106 (006Ah)
INT NO
X
X
X
------- ---- ---PGSM
75
16
001 01
1 (0001h)
103 (0067h)
INT NO
X
X
X
PGSM
30
16
End of report
Example 9 {31400} This example displays TD-SCDMA cell 4 9 6 2 3 1 1 1 1 as a neighbor of GSM cell 0 0 1 0 1 1 4. disp_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 Where:
is: 0010114
src_cell_desc
496231111
neighbor_cell_desc
System response Start of neighbor report: S A UTRAN CELL ID MCC MNC
LAC
RNC id
CI
--------------------------------------------496 231
1 (0001h)
1 (0001h)
1 (0001h)
B
C
C
C
C
H
H
----X
ARFCN
Param
TSTD
SCTD
----- --- -10110
100
0
0
End of report
68P02901W23-S
3-351 Nov 2009
References
Chapter 3: Device/function related commands
References Related commands
3-352
add_cell on page 3-22
add_neighbor on page 3-35
copy_cell on page 3-179
del_cell on page 3-192
disp_cell on page 3-241
disp_gsm_cells on page 3-314
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_nsvc
disp_nsvc ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_nsvc command displays the requested NSVCs and their configurations. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator action)
Prerequisites
None (If GPRS is restricted, the display still shows the headings.)
Format Syntax disp_nsvc |
Input parameters NS_VCI Specifies the NSVCI as defined by value. pcu_id {27955A} Specifies the pcu or pcu_0 at which the GBL is defined. GBL Specifies the GBL as defined by value. value Varies according to the option chosen.
68P02901W23-S
3-353 Nov 2009
Examples
Chapter 3: Device/function related commands
Examples Example 1 The following example displays NSVCI 68: disp_nsvc NS_VCI 68 Where:
is: NS_VCI
NSVCI
68
NSVCI ID
System response Start of Report: NS-VCI
NSEI
------
PCU GBL
STATUS
DLCI
BC
BE
CIR
---- ---- ---
----------
-----
----
----
----
68
15
0
0
Unblocked
22
0
64
64
68
16
1
0
Unblocked
22
0
64
64
End of Report.
Example 2 The following example displays all the NSVCIs associated with GBL 0 at PCU site 0 during SYSGEN: disp_nsvc pcu_0 GBL 0 Where:
3-354
is: pcu_0
PCU (second equipped)
GBL
GBL
0
GBL 0
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
System response Start of Report: Site: PCU_0 NS Access Rate: 64 GBL
NS-VCI
STATUS
DLCI
BC
BE
CIR
---
-------
----------
-----
----
----
----
0
68
PCU OOS
22
0
64
64
27
PCU OOS
239
0
64
64
102
PCU OOS
91
0
64
64
198
PCU OOS
240
0
64
64
10
PCU OOS
16
0
64
64
23
PCU OOS
200
0
64
64
21
PCU OOS
204
0
64
64
78
PCU OOS
119
0
64
64
69
PCU OOS
213
0
64
64
End of Report.
References Related commands add_nsvc on page 3-48
68P02901W23-S
del_nsvc on page 3-202
3-355 Nov 2009
disp_options
Chapter 3: Device/function related commands
disp_options ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_options command displays the unrestricted and restricted optional features. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
Format Syntax disp_options [all]
Input parameter all Displays both the unrestricted and restricted options. If this parameter is not entered, only the unrestricted options are displayed.
Examples Example 1 In this example, only the unrestricted options are displayed. disp_options
System response The following optional features have unrestricted use: ---------------------------------------------------------------------
3-356
1
A & Um Interface - GSM Phase 2
2
Daisy Chaining
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
3
Encryption Multiple Encryption
4
Frequency Hopping Baseband
5
Frequency Hopping Synthesizer
6
Receiver Spatial Diversity
7
Reserved Timeslots
8
SMS Cell Broadcast (Multiple Background Messages)
9
SMS Point to Point
10
Preventative Cyclic Retransmission
11
Microcell
12
Extended GSM 900
13
SMS Cell Broadcast (CBC Support)
14
Add Nail Connections
15
Directed Retry
16
Alternative Congestion Relief
17
Level 3 Password
18
A5_1 Encryption
19
A5_2 Encryption
20
A5_3 Encryption
21
A5_4 Encryption
22
A5_5 Encryption
23
A5_6 Encryption
24
A5_7 Encryption
25
RTF-PATH Fault Containment
26
Sub-Equipped RTF
27
16 Kbps LAPD RSL
28
16 Kbps LAPD XBL
29
Infrastructure sharing Homogeneous Cabinet
30
Infrastructure Sharing Heterogeneous Cabinet
31
MultiBand Inter-Cell Handover
32
Concentric Cells
33
Aggregate Abis
34
Extended Range Cells
35
Downloadable Transcoder Volume Control (Uplink and Downlink)
36
Enhanced Full Rate
37
Fast GCLK Warmup
38
Integrated M-Cell HDSL Interface
39
BTS Concentration
40
General Packet Radio Service
41
Dual Band Cells
42
900/1800 Horizonmicro2 / Horizoncompact2
43
Enhanced Circuit Error Rate Monitor
44
Network Controlled Cell Reselection
68P02901W23-S
Examples
3-357 Nov 2009
Examples
Chapter 3: Device/function related commands
45
Location Services
47
Coding Scheme 3&4 Enabled
48
Enhanced One Phase Access
49
Enhanced Capacity BSC
50
InterRAT Handover 2G>3G Cell Relocation 3G>2G Dedicated Mode
51
Adaptive Multi-Rate
52
AMR Using Enhanced GDP
53
PBCCH/PCCCH
54
Seamless Cell Reselection
55
AMR Enhanced Capacity
57
TCU-B Support for AMR
58
Prp Capacity
59
Enhanced General Packet Radio Service
60
GSM Half Rate
61
MMSs at Horizonmacro2
62
Quality of Service
63
GPRS Trace
64
Versa Trau
65
Dual Transfer Mode
{30828} 83
CTU2–D Capicity
{31400} 86
TD-SCDMA inter-working
NOTE The actual output of this command depends on the delivery of other optional features.
Example 2 In this example, both the unrestricted and restricted options are displayed. disp_options all Where:
is: all
3-358
all options
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response The following optional features have unrestricted use: 1
A & Um Interface - GSM Phase 2
2
Daisy Chaining
3
Encryption Multiple Encryption
4
Frequency Hopping Baseband
5
Frequency Hopping Synthesizer
6
Receiver Spatial Diversity
7
Reserved Timeslots
8
SMS Cell Broadcast (Multiple Background Messages)
9
SMS Point to Point
10
Preventative Cyclic Retransmission
11
Microcell
12
Extended GSM 900
13
SMS Cell Broadcast (CBC Support)
14
Add Nail Connections
15
Directed Retry
16
Alternative Congestion Relief
17
Level 3 Password
18
A5_1 Encryption
19
A5_2 Encryption
20
A5_3 Encryption
21
A5_4 Encryption
22
A5_5 Encryption
23
A5_6 Encryption
24
A5_7 Encryption
25
RTF-PATH Fault Containment
26
Sub-Equipped RTF
27
16 Kbps LAPD RSL
28
16 Kbps LAPD XBL
29
Infrastructure sharing Homogeneous Cabinet
30
Infrastructure Sharing Heterogeneous Cabinet
31
MultiBand Inter-Cell Handover
32
Concentric Cells
33
Aggregate Abis
34
Extended Range Cells
35
Downloadable Transcoder Volume Control (Uplink and Downlink)
36
Enhanced Full Rate
37
Fast GCLK Warmup
38
Integrated M-Cell HDSL Interface
40
General Packet Radio Service
68P02901W23-S
3-359 Nov 2009
Examples
Chapter 3: Device/function related commands
41
Dual Band Cells
42
900/1800 Horizonmicro2 / Horizoncompact2
43
Enhanced Circuit Error Rate Monitor
44
Network Controlled Cell Reselection
45
Location Services
46
ALM for EGSM carriers
47
Coding Scheme 3&4 Enabled
48
Enhanced One Phase Access
49
Enhanced Capacity BSC
50
InterRAT Handover 2G>3G Cell Relocation 3G>2G Dedicated Mode
51
Adaptive Multi-Rate
52
AMR Using Enhanced GDP
54
Seamless Cell Reselection
55
AMR Enhanced Capacity
56
TCU-A Support for AMR
57
TCU-B Support for AMR
58
Prp Capacity
59
Enhanced General Packet Radio Service
60
GSM Half Rate
61
MMSs at Horizonmacro2
62
SDCCH Increase
63
Network Assisted Cell Change
64
Quality Of Service
65
GPRS Trace
66
Fast Call Setup
67
Enhanced 2G/3G Handover and Cell Reselection
68
Enhanced Multi-level Precedence and Pre-emption Service
69
Intelligent Multi-layer Resource Management
70
VersaTRAU
The following optional features have restricted use: --------------------------------------------------------------------39
BTS Concentration
72
Reserved option
73
Improved Timeslot Sharing
--------------------------------------------------------------------
3-360
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 3 In this example, the operator performs the disp_options command when only the Enhanced Circuit Error Rate Monitor feature is restricted. disp_options all Where:
is: all
all options
System response The following optional features have unrestricted use: --------------------------------------------------------------------1
A & Um Interface - GSM Phase 2
. . . . . . 59
Enhanced General Packet Radio Service
60
GSM Half Rate
61
MMSs at Horizonmacro2
62
SDCCH Increase
63
Network Assisted Cell Change
64
Quality Of Service
65
GPRS Trace
66
Fast Call Setup
67
Enhanced 2G/3G Handover and Cell Reselection
68
Enhanced Multi-level Precedence and Pre-emption Service
69
Intelligent Multi-layer Resource Management
70
VersaTRAU
73
Improved Timeslot Sharing
74
Restricted
The following optional features have restricted use: --------------------------------------------------------------------43
68P02901W23-S
Enhanced Circuit Error Rate Monitor
3-361 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 4 In this example, the operator performs the disp_options command when no features are restricted. disp_options all Where:
is: all
options
System response The following optional features have unrestricted use: --------------------------------------------------------------------1
A & Um Interface - GSM Phase 2
. . . . . . 39
BTS Concentration
. . . . . . 43
Enhanced Circuit Error Rate Monitor
. . . . . .
3-362
59
Enhanced General Packet Radio Service
60
GSM Half Rate
61
MMSs at Horizonmacro2
62
SDCCH Increase
63
Network Assisted Cell Change
64
Quality Of Service
65
GPRS Trace
66
Fast Call Setup
67
Enhanced 2G/3G Handover and Cell Reselection
68
Enhanced Multi-level Precedence and Pre-emption Service
69
Intelligent Multi-layer Resource Management
70
VersaTRAU
73
Improved Timeslot Sharing
74
Restricted
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 5 {26881} This example displays the status of an extended uplink TBF feature when its status is restricted. disp_options all Where:
is: all
options
System response The following optional features have unrestricted use: --------------------------------------------------------------------1
A & Um Interface - GSM Phase 2
2
Daisy Chaining
. . . . . . 56 TCU-A support for AMR 57 TCU-B support for AMR 58 Prp Capacity The following optional features have restricted use: --------------------------------------------------------------------46 ALM for EGSM Carriers 60 Extended Uplink TBF
Example 6 {34320G} This example displays the list of unrestricted features at the BSS. The SW enabler for PA bias switch on/off on the CTU2D feature is displayed in this list if the feature is enabled. disp_options
68P02901W23-S
3-363 Nov 2009
Examples
Chapter 3: Device/function related commands
System response The following optional features have unrestricted use: --------------------------------------------------------------------1
A & Um Interface - GSM Phase 2
2
Daisy Chaining
. . 59
Quality Of Service
60
Network Assisted Cell Change
61
SW enabler for PA bias switch on/off on CTU2D
Example 7 {28938} This example displays the list of unrestricted features at the BSS. disp_options
System response The following optional features have unrestricted use: --------------------------------------------------------------------1
A & Um Interface - GSM Phase 2
2
Daisy Chaining
. . 62
Quality Of Service
63
GPRS Trace
64
VersaTrau
65
Dual Transfer Mode
. . 74
Incell Support
Example 8 {25423} This example displays the list of unrestricted features at the BSS. disp_options all
3-364
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response WARNING: The feature option information object will not be downloaded to NE for "Set NE Patch Level" on OMC. So the old version before the operation will be displayed. PCU objects only upgrade and Patch only upgrade do not require BSC reset, so that any feature option changes will not take effect and they are not recommended in case of feature option changes upgrade. UK_Motorola_Swindon_NPI options for BSGSM-1.9.0.0.15-t1 (26/04/07) The following optional features have unrestricted use: --------------------------------------------------------------------1
A & Um Interface - GSM Phase 2
2
Daisy Chaining
Example 9 {23311A} This example verifies if the Extended Range Cell support for GPRS feature is unrestricted at the BSS. disp_options
System response The following optional features are unrestricted: --------------------------------------------------------------------1
A & Um Interface - GSM Phase 2
2
Daisy Chaining
. . 56
TCU-A support for AMR
57
TCU-B support for AMR
58
Prp Capacity
59
Enhanced 2G/3G Handover and Cell Reselection
60
Extended Uplink TBF
61
Extended Range Cell Support for GPRS
NOTE The actual output of this command depends on the delivery of other new restricted features.
68P02901W23-S
3-365 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 10 {23311A} This example displays the status of the Extended Range Cell support for the GPRS feature when its status is restricted. disp_options all Where:
is: all
all options
System response The following optional features have unrestricted use: --------------------------------------------------------------------1
A & Um Interface - GSM Phase 2
2
Daisy Chaining
. . 56
TCU-A support for AMR
57
TCU-B support for AMR
58
Prp Capacity
The following optional features have restricted use: --------------------------------------------------------------------46
ALM for EGSM Carriers
60
Extended Uplink TBF
61
Extended Range Cell Support for GPRS
NOTE The actual output of this command depends on the delivery of other new restricted features.
3-366
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_processor
disp_processor ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_processor command displays the status of all processor boards at a specific site or all sites. At InCell sites, this command also displays the related devices and functions associated with the processors. If a GPROC is not detected on the LAN in InCell sites, the Off LAN value displays. At M-Cell and Horizonmacro sites, this command displays transceivers, CPU numbers, DRI IDs, and associated RTFs (if any). The Related Device and Related Function columns are not applicable to M-Cell sites. If a DRI is not detected at the MCU ASIC, the No Sync value displays. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
This command is not allowed while in SYSGEN ON mode or during site initialization.
Format Syntax disp_processor
Input parameter location Indicates the number of the BTS or the BSC where the processors are located. 0 or bsc
BSC
1 - 140
BTS
{27955A} pcu or pcu_0
PCU
all
All locations
68P02901W23-S
3-367 Nov 2009
Examples
Chapter 3: Device/function related commands
Examples Example 1 In this example, the status of all processor boards at all InCell sites displays. disp_processor all Where:
is: all
all sites
System response PROCESSOR STATUS INFORMATION FOR LOCATION 0:END OF STATUS REPORT OPER
STATES:
ADMIN STATES:
D:Disabled
E:Enabled
B:Busy
L:Locked
U:Unlocked
E:Equipped
State Reason
NE:Not Equipped Related
Related
Device
Function
CPU#
Processor Name
----
-------------------- ----- ----------------- --------- --------
0115
BSP 0 0
B-U
NO REASON
N/A
N/A
0117
CSFP 0 0
D-U
NO CODE
N/A
N/A
0118
GPROC 2 0 (Off LAN)
D-U
GPROC Not On LAN
N/A
N/A
011a
GPROC 1 0 (LCF 0)
B-U
NO REASON
SITE 1 0
N/A
PROCESSOR STATUS INFORMATION FOR LOCATION 2: OPER
STATES:
ADMIN STATES:
D:Disabled
E:Enabled
B:Busy
L:Locked
U:Unlocked
E:Equipped
CPU# Processor Name
State Reason
NE:Not Equipped Related
Related
Device
Function
---- --------------------- ----- ----------------- --------- -------1015 BTP 0 0
B-U
1019 CSFP 0 0 (Off LAN)
D-U
NO REASON NO REASON
DRI 0 1
RTF 0 0
DRI 0 0
RTF 0 1
N/A
N/A
Example 2 In this example, the status of all processor boards at an M-Cell site displays. disp_processor 1 Where:
is: 1
3-368
an M-Cell site ID.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response PROCESSOR STATUS INFORMATION FOR LOCATION 1: OPER STATES:
D:Disabled
E:Enabled
B:Busy
ADMIN STATES:
L:Locked
U:Unlocked
E:Equipped
CPU# Processor Name
State Reason
NE: Not Equipped Related
Related
Device
Function
--------------------------------------------------------------------1015 BTP 0 0
B-U
NO REASON
N/A
N/A
2001 DRI 0 0 (RTF 0 0)
B-U
COMB Controller
N/A
N/A
2002 DRI 0 1 (RTF 0 2)
B-U
NO REASON
N/A
N/A
2003 DRI 0 2 (RTF 0 3)
B-U
NO REASON
N/A
N/A
2004 DRI 0 3 (RTF 0 1)
B-U
NO REASON
N/A
N/A
2005 DRI 0 4
E-L
NO REASON
N/A
N/A
2006 DRI 0 5 (No Sync)
D-L
NO REASON
N/A
N/A
END OF STATUS REPORT
Example 3 In this example, the status of the GPRS PCU processor boards are displayed. A single DPROC (PICP) configuration provides support up to 20 TRAU GDS links. disp_processor pcu_0 Where:
is: pcu_0
the first equipped PCU.
System response MMI-RAM 0115 -> disp_proc pcu_0 NC:
Not Connected
CPU# Processor Name
State
Reason
Related
Related
PROCESSOR STATUS INFORMATION FOR LOCATION PCU 0: OPER STATES:
D:Disabled
E:Enabled
B:Busy
ADMIN STATES:
L:Locked
U:Unlocked
E:Equipped
NE:Not Equipped Device
Function
---- ------------------ ------ ------------------ -------- -------1107 PSP 0 0
B-U
NO REASON
N/A
N/A
1109 PSP 1 0 (NC)
D-U
Bad or Missing Board
N/A
N/A
1101 DPROC (PICP) 1 0
B-U
NO REASON
MSI 0 0
N/A
GDS 0 0
N/A
GSL 0 0
N/A
68P02901W23-S
3-369 Nov 2009
Examples
Chapter 3: Device/function related commands
1102 DPROC (PRP)
2 0
1103 DPROC (PICP) 3 0
1104 DPROC (PRP)
1105 DPROC (PRP)
1106 DPROC (PRP)
4 0
5 0
6 0
110b DPROC (PICP) 11 0
3-370
B-U
B-U
B-U
B-U
B-U
B-U
NO REASON
NO REASON
NO REASON
NO REASON
NO REASON
NO REASON
GSL 2 0
N/A
GSL 4 0
N/A
GSL 6 0
N/A
GSL 10 0
N/A
GSL 8 0
N/A
MSI 1 0
N/A
GBL 0 0
N/A
(GDS 5 0)
N/A
(GDS 10 0)
N/A
(GDS 11 0)
N/A
(GDS 12 0)
N/A
(GDS 14 0)
N/A
(GDS 16 0)
N/A
MSI 5 0
N/A
GDS 2 0
N/A
MSI 14 0
N/A
GDS 11 0
N/A
MSI 4 0
N/A
GBL 2 0
N/A
GBL 3 0
N/A
(GDS 4 0)
N/A
(GDS 7 0)
N/A
(GDS 3 0)
N/A
MSI 6 0
N/A
GDS 3 0
N/A
MSI 15 0
N/A
GDS 12 0
N/A
MSI 7 0
N/A
GDS 4 0
N/A
MSI 16 0
N/A
GDS 13 0
N/A
MSI 8 0
N/A
GDS 5 0
N/A
MSI 17 0
N/A
GDS 14 0
N/A
MSI 2 0
N/A
GDS 1 0
N/A
GSL 1 0
N/A
GSL 3 0
N/A
GSL 5 0
N/A
GSL 7 0
N/A
GSL 9 0
N/A
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
110c DPROC (PRP) 12 0
110d DPROC (PRP) 13 0
110e DPROC (PRP) 14 0
110f DPROC (PRP) 15 0
1110 DPROC (PRP) 16 0
B-U
B-U
B-U
B-U
B-U
Examples
NO REASON
NO REASON
NO REASON
NO REASON
NO REASON
GSL 11 0
N/A
MSI 3 0
N/A
GBL 1 0
N/A
(GDS 8 0)
N/A
(GDS 2 0)
N/A
(GDS 6 0)
N/A
MSI 9 0
N/A
GDS 6 0
N/A
MSI 18 0
N/A
GDS 15 0
N/A
MSI 10 0
N/A
GDS 7 0
N/A
MSI 19 0
N/A
GDS 16 0
N/A
MSI 11 0
N/A
GDS 8 0
N/A
MSI 20 0
N/A
GDS 17 0
N/A
MSI 12 0
N/A
GDS 9 0
N/A
MSI 21 0
N/A
GDS 18 0
N/A
MSI 13 0
N/A
GDS 10 0
N/A
MSI 22 0
N/A
GDS 19 0
N/A
END OF STATUS REPORT
Example 4 {28351} In this example, the BSC modifies the disp_processor command to support a PXP DPROC. disp_processor pcu Where:
is: pcu
68P02901W23-S
the equipped PCU.
3-371 Nov 2009
Examples
Chapter 3: Device/function related commands
System response PROCESSOR STATUS INFORMATION FOR LOCATION PCU 0: OPER
STATES:
ADMIN STATES: NC:
D:Disabled
E:Enabled
B:Busy
L:Locked
U:Unlocked
E:Equipped
NE:Not Equipped
Not Connected Related
CPU# Processor Name
State Reason
Related
Device
Function
---- ---------------------- ----- ------------------------- ----- -------1107 PSP 0 0
B-U
NO REASON
N/A
N/A
N/A
N/A
1109 PSP 1 0 (NC)
D-U
Bad or Missing Board
1101 DPROC (PICP) 1 0
B-U
NO REASON
MSI 1 0
N/A
GDS 1 0
N/A
GSL 0 1
N/A
Unknown device found 1102 DPROC (PICP) 2 0
B-U
1103 DPROC (PXP) 3 0
B-U
NO REASON
MSI 2 0
N/A
Unknown device found No GDS in service
MSI 3 0
N/A
GBL 0 0
N/A
GDS 3 0
N/A
GSL 0 3
N/A
Unknown device found 1104 DPROC (PRP) 4 0
B-U
NO REASON
MSI 4 0 GDS 4 0
N/A N/A
Unknown device found 1105 DPROC (PXP) 5 0
B-U
NO REASON
MSI 5 0
N/A
NOTE CA queries pCA. PPROC is displayed only when U-DPROC2 is configured as PXP. roglin command is used for querying when the board is configured as PXP.
3-372
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_relay_contact
disp_relay_contact ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_relay_contact command displays the relay state (open or closed circuit) for an EAS device when the device is Busy-Unlocked. The relays are in the deactivated state, as defined during equip EAS, when the EAS is not Busy-Unlocked. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
The EAS device must be equipped and the EAS device parameters established using the equip eas command. Seeequip on page 3-403.
Format Syntax disp_relay_contact
Input parameters location Specifies the location of the device: 0 or bsc
BSC
1 - 140
BTS
device_id Specifies the device ID of the specific PIX card associated with an EAS device. 0 to 7
InCell sites
0 to 15
M-Cell and Horizonmacro sites
68P02901W23-S
3-373 Nov 2009
Example
Chapter 3: Device/function related commands
Example This example displays the relay contacts for all EAS devices. disp_relay_contact
System response Relay 1: Closed
Relay 2: Open Relay 3: Open Relay 4: Closed
References Related command equip on page 3-403
3-374
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_rtf_channel
disp_rtf_channel ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_rtf_channel command displays the status of all timeslots or a single timeslot on a carrier. The display output indicates whether the RTF is equipped for GPRS and EGPRS, and if capable of supporting EGPRS If either AMR or GSM Half Rate channel mode is enabled at both the BSS level and the Cell level for a given cell, the BSS user interface displays generic traffic channels as TCH/G in the output when the disp_rtf_channel command is executed for a half rate RTF in that cell. Security level
1
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
This command is not allowed while in SYSGEN ON mode.
Format Syntax disp_rtf_channel []
Input parameter location Specifies the location: 0 or bsc
BSC
1 - 140
BTS
rtf_id_1 The first identifier of the RTF. The range of values is 0 to 5. rtf_id_2 The second identifier of the RTF. The range of values is 0 to 11. timeslot_number Specifies the timeslot number. The range of values is 0 to 7. When an Extended Range timeslot number is displayed, the word ‘Extended’ is appended to the timeslot number.
68P02901W23-S
3-375 Nov 2009
Examples
Chapter 3: Device/function related commands
Carrier states The carrier states that can be displayed include: •
ACTIVE - the timeslot is active.
•
IDLE - the timeslot is idle.
•
INTRANS - the timeslot is in transition: from active to idle, or from idle to active, or from unavailable to active.
•
OOS - the timeslot is out of service. Due to EGPRS PDs on double density CTU2 carrier A, the paired timeslots on carrier B is blanked out and displayed as OOS.
•
UNAVAILABLE (HOPPING) - the timeslot is unavailable due to hopping reconfiguration.
•
UNAVAILABLE (IBAND) - the timeslot is unavailable due to a poor interference band (Iband).
•
UNAVAILABLE (OPERATOR) - the operator has subequipped an RTF.
•
UNAVAILABLE (TERRESTRIAL) - the carrier is unavailable due to a problem with a terrestrial link.
•
N/A - for a PDTCH, the timeslot is not configured for GPRS.
The GPRS types that can be displayed include: •
SWITCHABLE - the GPRS timeslot is switchable.
•
RESERVED - the GPRS timeslot is reserved.
Examples Example 1 This example displays the status of RTF 0 2 at Site 1 when both EGPRS and GPRS are restricted. disp_rtf_channel 1 0 2 Where:
3-376
is: 1
location
0
rtf_id_1
2
rtf_id_2
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response Start of report for RTF 0 2 at location 1:
TIMESLOT
SUB-CHAN
STATE
------------------------------------------------------0 (TCH/F)
0
ACTIVE
1 (TCH/F)
0
ACTIVE
2 (TCH/F)
0
ACTIVE
3 (TCH/F)
0
ACTIVE
4 (TCH/F)
0
ACTIVE
5 (TCH/F)
0
ACTIVE
6 (TCH/F)
0
ACTIVE
7 (TCH/F)
0
ACTIVE
Example 2 This example displays the status of RTF 0 0 at Site 1 when the RTF is configured for EGPRS and is assigned to a DRI capable of supporting EGPRS (that is, a single density CTU2). disp_rtf_channel 1 0 0 Where:
is: 1
location
0
rtf_id_1
0
rtf_id_2
System response Start of report for RTF 0 0 at location 1:
Packet Radio Capabilities: 64 K RTF currently capable of supporting EGPRS?: YES TIMESLOT
GPRS TYPE
SUB-CHAN
STATE
---------------------------------------------------------------0 (BCCH)
N/A
0
ACTIVE
1 (TCH/F)
N/A
0
ACTIVE
68P02901W23-S
3-377 Nov 2009
Examples
Chapter 3: Device/function related commands
2 (TCH/F)
N/A
0
ACTIVE
3 (64 K PDTCH)
Switchable
0
N/A
4 (64 K PDTCH)
Reserved
0
N/A
5 (64 K PDTCH)
Reserved
0
N/A
6 (64 K PDTCH)
Reserved
0
N/A
7 (64 K PDTCH)
Reserved
0
N/A
Example 3 This example displays the carrier states of RTF 1 0, timeslot 5 (a generic traffic channel) at site 1 with half_rate_enabled element set to 1 (enabled). disp_rtf_channel 1 1 0 5 Where:
is: 1
location
1
rtf_id_1
0
rtf_id_2
5
timeslot
System response TIMESLOT
SUB-CHAN
STATE.
------------------------------------5 (TCH/G)
0
IDLE
End of Report
Example 4 This example displays the timeslot status of Carrier B when Carrier A has three EGPRS PDs on timeslots 5 to 7. disp_rtf_channel 1 0 2 Where:
3-378
is: 1
location
0
rtf_id_1
2
rtf_id_2
5
timeslot
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System Response Start of report for RTF 0 2 at location 1 Packet Radio Capabilities: None RTF currently capable of supporting EGPRS? No TIMESLOT GPRS TYPE SUB-CHAN STATE 0 (TCH/F) N/A 0 ACTIVE 1 (TCH/F) N/A 0 ACTIVE 2 (TCH/F) N/A 0 ACTIVE 3 (TCH/F) N/A 0 ACTIVE 4 (TCH/F) N/A 0 ACTIVE 5 (TCH/F) N/A 0 OOS 6 (TCH/F) N/A 0 OOS 7 (TCH/F) N/A 0 OOS
Example 5 {23311A} This example displays the carrier status of all the timeslots for an RTF channel with extended timeslots pair (2,3), configured as extended PDCHs. disp_rtf_channel 1 0 0 Where:
68P02901W23-S
is: 1
location
0
rtf_id_1
0
rtf_id_2
3-379 Nov 2009
Examples
Chapter 3: Device/function related commands
System response Start of report for RTF 0 0 at location 1: Packet Radio Capabilities: 64k RTF currently capable of supporting EGPRS?: YES TIMESLOT
GPRS TYPE
SUB-CHAN
STATE
---------------------------------------------------------------0 (TCH/F)
N/A
0
ACTIVE
Reserved
0
N/A
4 (64k PDTCH)
Reserved
0
N/A
5 (64k PDTCH)
Reserved
0
N/A
6 (64k PDTCH)
Reserved
0
N/A
7 (64k PDTCH)
Reserved
0
N/A
1 (Extended) 2 (64k PDTCH) 3 (Extended)
3-380
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_rtf_path
disp_rtf_path ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_rtf_path command displays all PATH devices to which the RTF is assigned, including the status of the RTF on that PATH. The status of the RTF is shown as Connected or Redundant. The system shows whether a site supports dynamic allocation. The PATH status includes the designation of SHARED in addition to the CONNECTED and REDUNDANT status. All PATHs which could be used to carry the RTF to the BSC are displayed. For spoke and daisy chain configurations, no redundant PATHs exist. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
This command is available only on RTF functions that are equipped on a remote BTS.
Format Syntax disp_rtf_path
Input parameters location Specifies the number of the BTS where the RTF is located. The range of values is 0 to 140. rtf_id_1 Specifies the 1st RTF identifier. The range of values is 0 to 5. rtf_id_2 Specifies the 2nd RTF identifier. The range of values is 0 to 11.
68P02901W23-S
3-381 Nov 2009
Example
Chapter 3: Device/function related commands
Example This example displays all the PATH devices assigned to RTF 0 0 at BTS 12. disp_rtf_path 12 0 0 Where:
is: 12
location
0
rtf_id_1
0
rtf_id_2
System response Start of Report:
SITE ID:
12
1st RTF Identifier: 0 2nd RTF Identifier: 0 PATH 12 0 0 Status: CONNECTED
Busy Unlocked
End of Report
References Related commands add_rtf_path on page 3-50
chg_rtf_freq on page 3-144
copy_path on page 3-187
del_rtf_path on page 3-204
3-382
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_severity
disp_severity ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description Use the disp_severity command to view the current severity level for device alarms and non-reconfiguration alarms. Security level
1
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
None
Format Syntax disp_severity
Input parameters device_name The name of the device, such as GPROC, that is being modified. alarm_code The decimal number or range that identifies the alarm code or codes for the device that is being modified. The alarm code is defined by all valid numeric values in the range 0 to 254. •
Refer to Alarm devices on page 3-20 for the ranges of alarm codes for each device.
•
Refer to the Maintenance Information: Alarm Handling at the OMC-R (68P02901W26) manual for a list of all alarms and the corresponding alarm codes for each device.
68P02901W23-S
3-383 Nov 2009
Example
Chapter 3: Device/function related commands
Example This example shows how to display the severity of GPROC alarm code 8. disp_severity gproc 8 Where:
is: gproc
device_name
8
alarm_code
System response GPROC Alarm code 8 severity: Investigate
3-384
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_site
disp_site ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_site command displays the site, BSC, or BTS, with which the operator is interacting. Security level
1
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
None
Format Syntax disp_site
Input parameters There are no input parameters associated with this command.
Example This example displays the current site. disp_site
System response Current site number is 6
References Related command equip on page 3-403.
68P02901W23-S
3-385 Nov 2009
disp_throttle
Chapter 3: Device/function related commands
disp_throttle ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_throttle command displays the throttle period for an intermittent alarm. To display the throttle time period for all intermittent alarms, the command is executed with no input parameters. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
Format Syntax disp_throttle [ ]
Input parameters device_name Device name that uniquely identifies the device. alarm_code Identifies the alarm to be throttled. The range of values for the alarm_code is 0 to 254.
Examples Example 1 This example displays the throttle period for device DRI, alarm code 66. disp_throttle dri 66 Where:
3-386
is: dri
device_name
66
alarm_code
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
System response Alarm
Alarm
Throttle
Source
Code
Time
Alarm Description
------
-----
--------
-----------------------------------
DRI
66
5
Superframe Counter Error
Example 2 This example displays the throttle period for all of the intermittent alarms. disp_throttle
System response Alarm
Alarm
Throttle
Source
Code
Time
Alarm Description
--------
------
---------
-------------------------------------
MMS
0
15
Synch Loss Daily Threshold Exceeded
MMS
1
1
Synch Loss Hourly Threshold Exceeded
MMS
4
1
Remote Alarm Daily Threshold Exceeded
1
10
.... DRI
Bad Host Message
....
References Related command chg_throttle on page 3-156.
68P02901W23-S
3-387 Nov 2009
disp_time
Chapter 3: Device/function related commands
disp_time ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_time command displays the current real time of the system. The format of the real time is: •
Day of the week
•
Month
•
Day of the month
•
Hour
•
Minutes
•
Seconds
•
Year
Security level
1
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
None
Format Syntax disp_time
Input parameters There are no input parameters associated with this command.
Example In this example, the system time is displayed. disp_time
3-388
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
System response Fri Nov 12 14:13:48 2002
References Related commands chg_time on page 3-158
68P02901W23-S
time_stamp on page 3-548
3-389 Nov 2009
disp_trace_call
Chapter 3: Device/function related commands
disp_trace_call ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_trace_cell command displays the mode, value, and trace data currently enabled in the BSS and the destination of the trace report. Security level
1
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
This command is not allowed when in SYSGEN ON mode.
Format Syntax disp_trace_call [reference_number]
Input parameter reference_number A number that identifies a particular trace reference. The number can range from 0 to 4294967295. Using a reference number is optional. If the reference number is not used, the system displays all call traces.
Examples Example 1 The following example displays the Call/GPRS Trace criteria that are currently at the BSS. disp_trace_call
System response Start of Trace Report Trace Reference:
3-390
1h
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Scope:
0 0 1 0 1 1(0001h) 4(0004h)
Trigger Event:
combined_all (All Call Trace and GPRS Trace)
Trace Data:
Basic, DTAP, Abis
GPRS trace Data:
Basic, LLC, BSSGP
Trigger Enabled Time:
Not Specified
Data during handover only:
No
Mode
IMSI=003456789012345
Total calls to be traced:
20
Trace beyond scope:
No
Destination of Trace data:
OMC
Triggering enabled:
No
Trace Reference:
67A67h
Scope:
BSS wide
Trigger Event:
gprs (GPRS Trace)
GPRS Trace Data:
Basic, LLC, BSSGP
Data during handover only:
No
Mode
TLLI=c0010329h
Trigger Enabled Time:
Not Specified
Total calls to be traced:
20
Trace beyond scope:
No
Destination of Trace data:
OMC
Triggering enabled:
No
Total mobiles currently traced Trace Reference
Count
-----------------
-----
1h
8
67A67h
5
Total calls currently traced Trace Reference
Count
-----------------
-----
1h
3
Automatic Flow Control:
Not Halted for this BSS.
Automatic Flow Control: Activated by BSS.
68P02901W23-S
3-391 Nov 2009
Examples
Chapter 3: Device/function related commands
Automatic Flow Control:
De-activated by OMC.
Example 2 The following is an example of the specified call trace instance (trace reference 067A67h) currently active in the BSS. disp_trace_call 067A67h Where:
is: 067A67h
reference_number
System response Start of Trace Report Trace Reference:
067A67h
Scope:
BSS wide
Trigger Event:
gprs (GPRS Trace)
GPRS Trace Data:
Basic, LLC, BSSGP, PMRs
Interval (x480msec):
20
Data during handover only:
No
Mode
NthGPRSmobile=5
Trigger Enabled time
Not specified
Total calls to be traced:
20
Trace beyond scope:
No
Destination of Trace data:
OMC
Trigger enabled:
No
Total mobiles currently traced Trace Reference
Count
---------------
-----
067A67h
5
Total calls currently being traced
3-392
Trace Reference
Count
---------------
-----
Automatic Flow Control:
Not Halted for this BSS.
Automatic Flow Control:
Activated by BSS.
Automatic Flow Control:
De-activated by OMC.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
References Related commands trace_call on page 3-550
68P02901W23-S
trace_stop on page 3-564
3-393 Nov 2009
disp_traffic
Chapter 3: Device/function related commands
disp_traffic ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_traffic command displays all RSL and RTFs equipped to a particular PATH at a BTS or all GSLs equipped to a GDS at a PCU. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
The GPRS feature must be unrestricted to display PCU data.
Format Syntax disp_traffic
Input parameters location Specifies the equipment location: {27955A} pcu or pcu_0
PCU
1 - 140
BTS
unique_PATH_identifier Specifies the unique PATH to a particular BTS. The range of values is 0 to 11.
3-394
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Examples Example 1 This example displays the RSL devices and RTF functions equipped on unique PATH 3 at site 1. disp_traffic 1 3 Where:
is: 1
location
3
unique_PATH_identifier
System response Start of Report:
SITE ID:
1
Unique PATH ID:
3
RSL 1 0 0 RTF 0 0 0 RTF 0 1 0 RTF 0 2 0 End of Report
Example 2 This example displays the PCU data. disp_traffic pcu 0 Where:
is: pcu
location
0
unique_PATH_identifier
System response Start of Report: SITE ID:
PCU
Unique GDS ID:
0
GPRS End of Report
68P02901W23-S
3-395 Nov 2009
References
Chapter 3: Device/function related commands
Example 3 {26740} This example displays the data for GDS. disp_traffic pcu_0 0 Where:
is: pcu_0
location
0
unique_PATH_identifier
System response SITE ID: PCU 0 Unique GDS ID: 0 GSL 0 0 0 GSL 0 2 0 GSL 0 4 0 GSL 0 6 0 GSL 0 8 0 GSL 0 10 0 GPRS DATA End of report
References Related command add_rtf_path on page 3-50.
3-396
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_transcoding
disp_transcoding ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_transcoding command displays which Circuit Identifier Codes (CICs) are using the transcoding resources of which GDPs and XCDRs. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
The enhanced GDP provisioning feature must be unrestricted.
Format Syntax disp_transcoding
Input parameters There are no parameters for this command.
Example This example displays the transcoding data. disp_transcoding
68P02901W23-S
3-397 Nov 2009
Example
Chapter 3: Device/function related commands
System response MSC MMS
Transcoding Board
CIC IDs
-------
-----------------
-------
1 0
1 0
1, 2, 3, 4, 5, 6, 7, 8, 9, 10
4 0
4 0
No CICs associated to this GDP/XCDR
------n/a: not applicable N-E: not equipped
3-398
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_version
disp_version ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_version command displays the current software version, patch object version and patch object level. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
This command is not allowed while in SYSGEN ON mode.
Format Syntax disp_version
Input parameters There are no input parameters associated with this command.
Example Example 1 {25423} To display the version, revision numbers, patch version, and patch level of the current software load. disp_version
68P02901W23-S
3-399 Nov 2009
Example
Chapter 3: Device/function related commands
System response
3-400
BSP Code Version:
8.0.0.E
BSP Patch Object Version:
5
BSP Patch Level:
3
BSP Database Level Number:
2C3F
CSFP Code Version:
-
CSFP Patch Object Version:
-
CSFP Database Level Number:
-
BSP Code Version:
8.0.0.E
BSP Patch Object Version:
–
BSP Patch Level:
–
BSP Database Level Number:
2C3F
CSFP Code Version:
-
CSFP Patch Object Version:
-
CSFP Database Level Number:
-
BSP Code Version:
8.0.0.E
BSP Patch Object Version:
5
BSP Patch Level:
0
BSP Database Level Number:
2C3F
CSFP Code Version:
-
CSFP Patch Object Version:
-
CSFP Database Level Number:
-
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
disp_x25config
disp_x25config ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The disp_x25config command displays the X.25 configuration for all the CBLs or OMLs at a BSS. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
None
Format Syntax disp_x25config
Input parameter link type Specifies the type of X.25 link: oml
displays parameters for all OMLs in the BSS. Must be used out of SYSGEN.
cbl
displays parameters for all CBLs in the BSS.
Example The following example displays the X.25 settings for all BSS OMLs. disp_x25 oml Where:
is: oml
68P02901W23-S
link type
3-401 Nov 2009
References
Chapter 3: Device/function related commands
System response: X.25 Packet Size:
128
X.25 Window Size:
2
References Related command chg_x25config on page 3-166.
3-402
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
equip
equip ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The equip command adds devices and functions to the Fault Management portion of the CM database. Since each device and function has specific parameters, there is a corresponding set of prompts. Each device and function also has specific restrictions for equipage. Details of the command prompts and restrictions for equipping the devices and functions are provided in Chapter 2 Equipping the CM database, which also includes charts showing equipage hierarchy. Some devices and functions require the system to be in the SYSGEN ON mode. To enter this mode, enter the sysgen_mode on command. To exit this mode, use the sysgen_mode off command. Some devices require the site to be locked. To lock the site, enter the lock command. To unlock the site, enter the unlock command. If a device or function parameter is optional, there is no need to enter data. Press the ENTER key at the prompt. The equip command can be exited at any time by entering done in response to any prompt.
NOTE The equip command can be entered only at the BSC. This command does not work at a BTS site. Contact the OMC-R for help in setting up a BTS site.
Security level
4
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
Some devices and functions can be equipped only after other devices have been equipped. To equip or modify some devices, the system must be in the SYSGEN ON mode. Some devices require the site to be locked. To equip a device or function with a frequency, it must be first set as allowable with the freq_types_allowed command. The LMTL can be equipped only if the Location Services support feature is unrestricted and the BSS can support a BSS-based SMLC. GPRS devices can be equipped only if the GPRS feature is unrestricted. {28337} HSP MTL can be equipped only when the increased network capacity feature is enabled.
68P02901W23-S
3-403 Nov 2009
Format
Chapter 3: Device/function related commands
Operator actions
Refer to the instructions included with each device or function for specific actions to be taken when using this command (see Chapter 2 Equipping the CM database).
Format Syntax equip
Input parameters location Specifies the location of the device: 0 or bsc
BSC
1 - 140
BTS
{27955A} pcu or pcu_0
PCU
NOTE A BSC of type 1 or 2 must equip remote sites with an LCF.
dev/func_name Identifies the device or function being equipped. The following devices can be equipped with this command:
3-404
ABSS
AXCDR
BSP
BSS
BTP
CAB
CAGE
CBL
CIC
COMB
CSFP
DHP
DPROC
DRI
DYNET
EAS
GBL
GCLK
GDS
GPROC
GSL
KSW
LMTL
MSI
MTL
OML
OPL
PATH
PCU
PSP
RSL
RXCDR
SITE
XBL
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
The following functions can be equipped with this command: LCF
RTF
OMF
NOTE The system responds with a series of command prompts for further input which is dependent on the particular device/function being equipped (see Chapter 2 Equipping the CM database for equipage rules/conditions and system command prompts).
Examples Example 1 In this example, a second CAGE is being equipped at the BSC using expansion: equip bsc cage Where:
is: bsc
location.
cage
device being equipped.
System response Enter the device identification for the cage: 1 Enter the KSW pair that manages the cage: 1 Enter the KSWX connecting cage to KSW for TDM 0: Enter KSWX connecting cage to KSW for TDM 1: Enter the cabinet to which the cage belongs: 1 Is an IAS connected?: Y COMMAND ACCEPTED
Example 2 In this example, a path with two links is equipped to site 2. All the prompts that define the path are included in this example. equip 0 path Where:
68P02901W23-S
is: 0
location.
path
the device being equipped.
3-405 Nov 2009
Examples
Chapter 3: Device/function related commands
System response Enter the terminating SITE id: 2 Enter the Unique PATH identifier: 0 Enter the BSC MSI identifier: 0 0 Enter the SITE identifier: 1 Enter the upstream MSI identifier: 2 0 Enter the downstream MSI identifier: 2 1 Enter the SITE identifier: 2 Enter the upstream MSI identifier: 2 1 COMMAND ACCEPTED
Example 3 This example equips a 64 K RTF at BTS site 2 with a warning that not enough GDS resources are available to handle PDTCHs. equip 2 rtf Where:
is: 2
location
System response Enter capacity of carrier: FULL Enter type of carrier: NON_BCCH Enter the 1st and 2nd RTF id: 0 5 Enter primary Unique PATH id: 1 Enter the optional secondary Unique PATH id: Enter the GSM cell to which this carrier is assigned: 0 0 1 0 1 1 3 Enter carrier absolute radio freq. channel: 620 Enter the 8 carrier frequency hopping indicators: 255 255 255 255 255 255 255 255 Enter the 8 carrier training sequence codes: 0 0 0 0 0 0 0 0 Enter cell zone: 0 Enter the number of extended range timeslots allowed: 0 Enter SDCCH load: 0 Enter channel allocation priority: 0 Enter the packet radio capability (NONE/16 K/32 K/64 K)?: 64K Enter the value for AMR half-rate enabled = 0 COMMAND ACCEPTED: WARNING: Insufficient GDS resources available for all PDTCHs on the PCU.
3-406
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 4 In this example, a PCU site 0 is equipped at the BSC: equip 0 PCU Where:
is: 0
location
System response Enter the PCU identifier (default 0): 0 Enter the PCU IP address: 127.0.0.2 Enter the PCU subnet mask: 255.255.255.0 Enter the PCU router IP address: 127.0.0.1 Enter the NSEI value: 5047 COMMAND ACCEPTED The COMMAND ACCEPTED message is replaced by an error message if a PCU with the same ID exists at the BSC, or the IP address entered is already assigned to another PCU.
Example 5 {27955A} This example attempts to equip pcu_0 as the pcu identifier. equip 0 PCU Where:
is: 0
location
System response Enter the PCU Identifier: 1 Enter the PCU base GDS IP Address: 10.15.255.222 Enter the PCU GDS Subnet Mask: 255.255.255.248 Enter the PCU GDS Router IP Address: 25.134.15.33 Enter the WebMMI IP address: 127.0.0.2 Enter the WebMMI subnet mask: 255.255.255.0 Enter the WebMMI router IP address: 127.0.0.1 Enter the NSEI value: 5047 COMMAND REJECTED ERROR: Range Error, parameter number: 1.
68P02901W23-S
3-407 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 6 {28337} In this example, a 64 k MTL is equipped successfully when the increased network capacity feature is unrestricted. equip 0 mtl Where:
is: 0
location.
mtl
device being equipped.
System response Enter the device identification for this MTL: 4 Enter the number of DS0 channels for this MTL: 1 Enter the first MMS description for this device: 10 Enter the second MMS description for this device: 0 Enter start timeslot on MMS where this device appears: 15 COMMAND ACCEPTED
Example 7 {28337} This example equips an LCF which manages an HSP MTL. equip 0 lcf Where:
is: 0
location.
lcf
device being equipped.
System response Enter the function identification for the LCF: 1 Enter the number of DS0 channels the LCF can manage as MTLs: 31 WARNING: HSP LCF equipage may trigger GPROC preemption. Are you sure (y=yes,n=no)? y COMMAND ACCEPTED
3-408
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 8 {28337} This example attempts to equip an LCF when the gproc_slot does not equal 32. equip 0 lcf Where:
is: 0
location.
lcf
device being equipped.
System response Enter the function identification for the LCF: 1 Enter the number of DS0 channels the LCF can manage as MTLs: 31 WARNING: HSP LCF equipage may trigger GPROC preemption. Are you sure (y=yes,n=no)? y COMMAND REJECTED: Insufficient GPROC timeslots available.
Example 9 {26740} In this example, the PCU is equipped when the increase in the throughput of PRP is restricted. equip 0 pcu Where:
is: 0
location.
pcu
device being equipped.
System response Enter the PCU Identifier: 0 Enter the PCU base GDS IP Address: 10.15.255.222 Enter the PCU GDS Subnet Mask: 255.255.255.0 Enter the WebMMI IP address: 127.0.0.2 Enter the WebMMI subnet mask: equip Enter the WebMMI router IP address: 127.0.0.1 Enter the NSEI value:equip COMMAND ACCEPTED
68P02901W23-S
3-409 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 10 {28351} In this example, two MSI devices of type E1_PMC is supported by the BSC on PXP DPROC. equip pcu msi Where:
is: pcu
device being equipped.
msi
dev_name
System response Enter the MSI Identifier: 1 Enter the DPROC id: 5 Enter the DPROC socket: 1 COMMAND ACCEPTED
Example 11 {26740} In this example, a PSI device is equipped at the BSC.
NOTE The PSI device is equipped only at a BSS or BSC sites.
equip bsc psi Where:
is: bsc
device being equipped.
psi
dev_name
System response Enter the PSI Identifier: 1 Enter the cage number: 0 Enter the slot number: 6 Enter the number of TDM timeslot blocks: 3 Enter the maximum number of GSLs on this PSI: 5 Enter the base IP address for the PSI: 10.0.16.4 Enter the subnet mask: 255.255.255.0 COMMAND ACCEPTED 3-410
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 12 {26740} The BSC rejects the equip command for a PSI device if the slot number is not 6, 7, 12 or 13.
NOTE The BSC rejects the equip command for a PSI device if it is unable to allocate the specified number of timeslot blocks on the TDM highway.
equip bsc psi Where:
is: bsc
device being equipped.
psi
dev_name
System response Enter the PSI Identifier: 3 Enter the cage number: 0 Enter the slot number: 8 Enter the number of TDM timeslot blocks: 3 Enter the maximum number of GSLs on this PSI: 5 Enter the base IP address for the PSI: 10.3.16.4 Enter the subnet mask: 255.255.255.0 COMMAND REJECTED: Received a request for an invalid slot
Example 13 {28000} In this example, pcu is equipped when Increase PRP Throughput feature is unrestricted. equip 0 pcu Where:
68P02901W23-S
is: 0
device being equipped.
pcu
dev_name
3-411 Nov 2009
Examples
Chapter 3: Device/function related commands
System response Enter the PCU Identifier: 0 Enter the PCU base GDS IP Address: 10.15.255.222 Enter the PCU GDS Subnet Mask: 255.255.255.248 Enter the PCU GDS Router IP Address: 10.15.255.221 Enter the WebMMI IP address: 127.0.0.2 Enter the WebMMI subnet mask: 255.255.255.0 Enter the WebMMI router IP address: 127.0.0.1 Enter the NSEI value: 5047 Enter the PRP Fanout Mode: 1 COMMAND ACCEPTED
Example 14 {26481} In this example, the operator attempts to enable the opto alarm (out of range 1-6) for EAS equipped to H2micro cabinet 0 0 0. equip 8 eas Where:
is: 8
device being equipped.
eas
dev_name
System response Enter the first device ID (Cabinet ID) for the EAS: 0 Enter the relay wiring of the 3 relays (0 - N/O, 1 - N/C): 1 1 1 Enter the no alarm condition for the 6 optos(0 - closed, 1 - open): 1 1 0 0 1 1 0 0 1 ERROR: Extra Parameters, received: 9.
3-412
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 15 {26481} This example equips a H2micro extension cabinet to site 12, that is, HORIZONMACRO master cab. equip 12 CAB Where:
is: 12
device being equipped.
CAB
dev_name
System response Enter the CABINET identifier: 1 Enter the cabinet type: HORIZON2MICRO_EXT Enter the frequency type: DCS1800 COMMAND ACCEPTED
Example 16 {27236} This example equips a DRI in double density capacity mode to site 7, resulting in DRI devices 0 0 0 and 0 1 0 being equipped when CTU2-D capacity feature is enabled. equip 7 DRI Where:
68P02901W23-S
is: 7
device being equipped.
dri
dev_name
3-413 Nov 2009
Examples
Chapter 3: Device/function related commands
System response Enter the 1st and 2nd DRI id: 0 0 Enter the density of this DRI: CAPACITY Enter the 2nd DRI id of the associated DRI: 1 Enter the cabinet type identifier: 0 Enter the type of connection to the BTP: direct Enter the port to which the TCU is connected: 0 Enter the 1st and 2nd RTF id: Enter the GSM cell ID where the DRI appears: 0 0 1 0 1 1 1 Enter the antenna select number for this cell: 0 Enter diversity flag for this DRI: 0 Enter the fm cell type: 0 COMMAND ACCEPTED
Example 17 {30828} This example equips a DRI in double density capacity mode to site 7, resulting in DRI devices 0 0 0 and 0 1 0 equipage being rejected when the CTU2-D capacity feature is restricted. equip 7 DRI Where:
is: 7
device being equipped.
dri
dev_name
System response Enter the 1st and 2nd DRI id: 0 0 Enter the density of this DRI: CAPACITY Enter the 2nd DRI id of the associated DRI: 1 Enter the cabinet type identifier: 0 Enter the type of connection to the BTP: direct Enter the port to which the TCU is connected: 0 Enter the 1st and 2nd RTF id: Enter the GSM cell ID where the DRI appears: 0 0 1 0 1 1 1 Enter the antenna select number for this cell: 0 Enter diversity flag for this DRI: 0 Enter the fm cell type: 0 COMMAND REJECTED: Received a request to modify a restricted optional feature
3-414
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
Example 18 {23311A} This example attempts to set ext_pdchs when the Extended Range Cell for Data feature is restricted (ercgprsOpt = 0), ext_pdchs is not prompted, and BSC is internally set ext_pdchs = 0. equip 0 RTF Where:
is: 0
device being equipped.
RTF
dev_name.
System response Enter type of carrier: NON_BCCH Enter the 1st and 2nd RTF identifier: 5 11 Enter the GSM cell assigned to this carrier: 0 0 1 0 1 1 18 Enter carrier absolute radio freq. channel: 70 Enter the 8 carrier frequency hopping indicators: 0 0 0 0 0 0 0 0 Enter the 8 carrier training sequence codes: 0 0 0 0 0 0 0 0 Enter KSW pair that manages this carrier: 0 Enter the number of extended range timeslots allowed: 2 Enter SDCCH load: 0 Enter the packet radio capability: 32k Enter the value for AMR half-rate enabled = 1 Is 8kbps TRAU allowed (yes/no)?: yes COMMAND ACCEPTED
References Related commands disp_equipment on page 3-283
freq_types_allowed on page 3-417
lock_device on page 3-429
modify_value on page 3-456
reassign on page 3-477
shutdown_device on page 3-502
state on page 3-515
unequip on page 3-570
unlock_device on page 3-581
68P02901W23-S
3-415 Nov 2009
Related information
Chapter 3: Device/function related commands
Related information The order and conditions in which devices and functions can be equipped, and the corresponding command prompts that are generated during the execution of the equip command are provided in Chapter 2 Equipping the CM database.
3-416
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
freq_types_allowed
freq_types_allowed ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The freq_types_allowed command specifies the following: •
The frequency types available to the BSS (PGSM, EGSM, DCS1800, PCS1900 systems).
•
The PCS1900 frequency blocks available at the BSS (PCS1900 systems only).
The following are valid frequency types: PGSM systems (default value)
Channels 1 to 124
EGSM systems
Channels 0, 1 to 124, 975 to 1023
DCS1800 systems
Channels 512 to 885
PCS1900 systems
Channels 512 to 810
Security level
4
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
None
Dependencies
The frequency types of extended neighbor cells must be allowed at the BSS.
Operator actions
All existing types and blocks must be entered when specifying a frequency type or frequency block (unless all types or blocks are specified). If the system is in SYSGEN OFF mode, the system does not allow modifying the frequency types if an existing frequency type or frequency block is not entered. If the system is in SYSGEN ON mode, and an existing frequency block or type is not entered, the system deletes that frequency block or type from the list of allowed types.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
68P02901W23-S
3-417 Nov 2009
Format
Chapter 3: Device/function related commands
Format Syntax freq_types_allowed []
Input parameter types Specifies the frequency types available to the BSS. The value is entered as: a text string, a number, or a list of text strings and numbers. The string ‘all’ specifies all frequency types. Possible values and text strings are: Numeric value
Text string
1
pgsm
2
egsm
3
pgsm,egsm
4
dcs1800
5
pgsm, dcs1800
6
egsm, dcs1800
7
pgsm, egsm, dcs1800
8
pcs1900
9
pgsm, pcs1900
10
egsm, pcs1900
11
pgsm, egsm, pcs1900
12
dcs1800, pcs1900
13
pgsm, dcs1800, pcs1900
14
egsm, dcs1800, pcs1900
15
pgsm, egsm, dcs1800, pcs1900
More than one frequency type can be entered. See Example 2, below. If no values are entered, the command displays the frequency types that are currently available.
3-418
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Prompted parameters The prompt for PCS 1900 frequency blocks appear only if ‘all’, ‘pcs1900’ or the number 8 is specified in the command line. If the prompt appears, enter at least one frequency block. Possible values are: a
Frequency block A
Channels 512 to 585
b
Frequency block B
Channels 612 to 685
c
Frequency block C
Channels 737 to 810
d
Frequency block D
Channels 587 to 610
e
Frequency block E
Channels 687 to 710
f
Frequency block F
Channels 712 to 735
all
all PCS1900 frequency blocks allowed in the BSS
See Example 3, below, for an example of the prompts.
Examples Example 1 This example displays the allowed frequency types. freq_types_allowed
System response: Frequency Blocks Allowed: PGSM
(1 - 124)
Example 2 This example modifies the frequency types allowed to include PGSM when DCS 1800 is already allowed. freq_types_allowed pgsm,dcs1800 Where:
68P02901W23-S
is: pgsm
frequency type for PGSM frequencies.
dcs1800
frequency type for DCS1800 frequencies.
3-419 Nov 2009
Examples
Chapter 3: Device/function related commands
System response: COMMAND ACCEPTED
Example 3 This example modifies the allowed frequency blocks to include A and D when blocks C and F are already allowed. freq_types_allowed pcs1900 Where:
is: 8
frequency type for PCS1900 frequencies.
System response: Enter PCS 1900 frequency blocks: a,c,d,f COMMAND ACCEPTED
3-420
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
gclk_cal_mode
gclk_cal_mode ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The gclk_cal_mode command specifies the synchronization function and MCU (Main Control Unit) software that a calibration is to be performed. A prompt displays describing the results of entering the command. The prompt must be acknowledged with a y (yes) to begin the calibration. No call processing can occur involving this MCU during the calibration mode. The MCU resets when the calibration is complete. Security level
2
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
This command is not allowed when in the SYSGEN ON mode. This command can be executed only at M-Cell sites.
Format Syntax gclk_cal_mode
Input parameters There are no input parameters associated with this command.
Example In this example, the GCLK calibration at the local site is started: gclk_cal_mode
68P02901W23-S
3-421 Nov 2009
Example
Chapter 3: Device/function related commands
System response Site starting GCLK CALIBRATION MODE. single MCU site, the site will be down until calibration is complete. If this is a two MCU site, the site will be down until the redundant MCU takes over. If this a Are you sure (y=yes,n=no)? y COMMAND ACCEPTED
3-422
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
ins_device
ins_device ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The ins_device command brings a device into service by locking and then unlocking the device. The following devices are supported: ABSS
AXCDR
BSP
BTP
CAB
{34321}CAGE
CBL
CIC
COMB
CSFP
DHP
DRI
EAS
GCLK
GPROC
KSW
MMS
MSI
MTL
OML
OPL
PATH
PCHN
{26740} PSI
RSL
SITE
XBL
TDM
The ins_device command supports only extension cabinets of type TCU_2, TCU_6, and HORIZONMACRO_EXT. No other extension cabinet types are supported. A standby KSW must be available to use this command on a KSW. {22168} When the BSC is operating in enhanced capacity mode, if a redundant DSW is swapped and replaced by a KSW, then the BSS SW at a BSS rejects an attempt to ins a KSW device, the system displays COMMAND REJECTED: KSW transition not allowed in Dual Mode configuration message. If the BSC with the KSW in the cage is reset, the BSC initializes in single rate mode. If the ins_device command is applied to an active GCLK, and the standby GCLK is phase locking, the system displays an additional warning message. The following GPRS devices are supported if the GPRS feature is unrestricted: {28351} ETH
DPROC
{28351} GSL
PCU
GBL
{28351} GDS
The following warning message is displayed when the TS1 of the BCCH carrier of a cell is INSed and PBCCH/PCCCH is enabled. WARNING: PBCCH/PCCCH timeslot would be lost which can cause GPRS traffic to be disrupted. Are you sure (y=yes, n=no)?. The following device is brought into service at a PCU using this command: MSI
68P02901W23-S
3-423 Nov 2009
Format
Chapter 3: Device/function related commands
A hard reset occurs when this command is entered for the following devices: BSP
BTP
DHP
GPROC
Security level
2
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
This command is not allowed while in SYSGEN ON mode. This command can be entered irrespective of whether the device is locked or unlocked.
Operator actions
Respond to the verification request prompt for an ABSS, AXCDR, BSP, BTP, DHP, GPROC or RSL. Respond to the verification request prompt for an MSI or MMS equipped with an OML.
Format General syntax ins_device
Input parameters location Specifies the location of the device: 0 or bsc
BSC
0 to 140
BTS
{27955A} pcu or pcu_0
PCU
device_name Literal that uniquely identifies the device. device_id1 First device identifier. This definition varies with each device. device_id2 Second device identifier. This definition varies with each device. device_id3 Third device identifier. This definition varies with each device.
3-424
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
CIC syntax A form of syntax is available for each method of specifying a CIC. The following CIC syntax applies to local transcoding: ins_device CIC ins_device CIC TO ins_device CIC ins_device CIC ins_device CIC TO The following CIC syntax applies to remote transcoding:
NOTE For remote transcoding BSC sites, the ins_device command cannot be used for CICs on a per-MMS basis when the BSC is operating in the dynamic allocation mode.
ins_device CIC ins_device CIC TO ins_device CIC ins_device CIC ins_device CIC * ins_device CIC TO
Input parameters location Specifies the location of the device: 0 or bsc
BSC
0 to 140
BTS
pcu, pcu_0 to pcu_2
PCU
CIC Literal that uniquely identifies the CIC device. cic_num1 First CIC device number.
68P02901W23-S
3-425 Nov 2009
Examples
Chapter 3: Device/function related commands
cic_num2 Last CIC device number in a range. mms_id1 First MMS identifier. mms_id2 Second MMS identifier, or last in a range if TO is used. timeslot1 First timeslot. timeslot2 Second timeslot, or last in a range if TO is used. group1 First group. group2 Second group. * Indicates all CICs on the MMSs specified in the timeslot, regardless of the group.
Examples Example 1 This example brings an MSI into service with ID 1 0 at the BSC. ins_device bsc msi 1 0 0 Where:
is: bsc
location
msi
device_name
1
device_id1
0
device_id2
0
device_id3
System response COMMAND ACCEPTED
3-426
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 2 This example brings a range of CICs (remote transcoder) into service; the range is specified by their MMS, TS, and group. ins_device bsc cic 2 1 3 1 TO 5 1 Where:
is: bsc
location
cic
CIC (device_name)
2
mms_id1
1
mms_id2
3
timeslot 3
1
group 1
5
timeslot 5
1
group 1
System response COMMAND ACCEPTED
Example 3 {22168} This example attempts to bring a KSW into service if the BSC is under enhanced capacity mode. ins 0 KSW 1 0 Where:
is: 0
location
KSW
device_name
1
device_id1
0
device_id2
System Response COMMAND REJECTED: KSW transition not allowed in Dual Mode configuration.
68P02901W23-S
3-427 Nov 2009
References
Chapter 3: Device/function related commands
Example 4 {34321} This example brings a cage into service and displays a confirmed command. A warning about the cage INS is displayed. ins_device bsc cage 3 0 Where:
is: bsc
location
cage
device_name
3
device_id1
0
device_id2
System response CAGE 3
This will affect all devices in this CAGE and any associated
Extension CAGEs. Are you sure (y=yes,n=no)? yes COMMAND ACCEPTED
References Related commands lock_device on page 3-429
3-428
reset_device on page 3-485
unlock_device on page 3-581
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
lock_device
lock_device ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The lock_device command locks a specified device. Security level
2
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
This command is not allowed while in SYSGEN ON mode. This command is only valid when the device is in the UNLOCKED state.
Format General syntax lock_device []
Input parameters location Specifies the location of the device: 0 or bsc
BSC
1 - 140
BTS
{27955A} pcu or pcu_0
PCU
The location must be bsc or 0 when specifying the device SITE. A PCU or a PCU device (for example, MSI) can also be locked. device_name Device name that uniquely identifies the device. The following devices can be locked using this command:
68P02901W23-S
3-429 Nov 2009
Format
Chapter 3: Device/function related commands
ABSS
AXCDR
BSP
BTP
CAB
{34321} CAGE
CBL
CIC
COMB
CSFP
DHP
DRI
DPROC
EAS
GBL
GCLK
GDS
GPROC
GSL
KSW
MMS
MSI
MTL
OML
OPL
PATH
PCHN
PCU
RSL
SITE
XBL
The shutdown_device command is available for non-intrusive locking of CIC, DRI, MPRT, and MTL devices. If an MMS at an RXCDR is locked, it does not lock any OMLs or MTLs that are carried on its associated 2 Mbit/s link. However, any traffic circuit carried on this 2 Mbit/s link is blocked. This prevents any inadvertently locking devices at the RXCDR, where their existence on a 2 Mbit/s link is not visible. If locking the MTL or OML is necessary, they should be addressed as individual devices. Entering the lock_device command where the MSI or MMS carries an OML causes the system to display a verification request before actually locking the device. Locking the link between an RXCDR and the BSC MMS makes the associated XBL go out of service (OOS). This means that XBL does not block the circuits. When locking an ABSS or AXCDR, the system presents a warning prompt and a verification prompt. If XBLs are equipped on the first and second links, and the XBL on the first link is locked, the XBL on the first link goes OOS; the XBL on the second link blocks the circuits. If the lock_device command is applied to an active GCLK, and the standby GCLK is phase locked, the system displays an additional warning message. This command is rejected for a KSW if no standby KSW is available. When a KSW is locked, all calls currently on the KSW are lost. Normal call processing resumes when the KSW is unlocked. For remote transcoding BSC sites, CICs cannot be locked on a per-MMS basis when the BSC is operating in the dynamic allocation mode. The lock_device command supports the following extension cabinets: TCU_2, TCU_6, Horizonmacro_EXT, Horizon2macro_ext, Horizon2micro_ext, and Horizon2mini_ext. DRIs and EASs equipped to the cabinet are disabled. No other cabinet types are supported. The following warning message is displayed when the TS1 of the BCCH carrier of a cell is locked and PBCCH/PCCCH is enabled. WARNING: PBCCH/PCCCH timeslot would be lost which can cause GPRS traffic to be disrupted. Are you sure (y=yes, n=no)? A hard reset occurs when this command is entered for the following devices: BSP
DHP
BTP
GPROC
device_id1 First device identifier. This value varies with each device. device_id2 Second device identifier. This value varies with each device.
3-430
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
device_id3 Third device identifier. This value varies with each device. If the specified device is a PCU, the PCU identifier must be entered as device_id1. A PCU or PCU device (for example MSI) can also be locked as a location.
CIC syntax A form of syntax is available for each method of specifying a CIC. The following CIC syntax applies to local transcoding: lock_device CIC lock_device CIC TO lock_device CIC lock_device CIC lock_device CIC TO The following CIC syntax applies to remote transcoding: lock_device CIC lock_device CIC TO lock_device CIC lock_device CIC lock_device CIC * lock_device CIC TO
Input parameters location Specifies the location of the device: 0 or bsc
BSC
1 - 140
BTS
CIC Literal that uniquely identifies the CIC device. cic_num1 First CIC device number. cic_num2 Last CIC device number in a range.
68P02901W23-S
3-431 Nov 2009
Examples
Chapter 3: Device/function related commands
mms_id1 First MMS identifier. mms_id2 Second MMS identifier, or last in a range if TO is used. timeslot1 First timeslot. timeslot2 Second timeslot, or last in a range if TO is used. group1 First group. group2 Second group. * Indicates all CICs on the MMSs specified in the timeslot, regardless of group.
Examples Example 1 This example locks an MSI with ID 1 at the BSC from further use. lock_device bsc msi 1 0 0 Where:
is: bsc
location
msi
device_name
1
device_id1
0
device_id2
0
device_id3
System response COMMAND ACCEPTED
3-432
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 2 This example locks a range of CICs; the range is specified by their MMS, TS, and group. lock_device bsc cic 2 1 3 1 TO 5 1 Where:
is: BSC
location
CIC
device_name
2
mms_id1
1
mms_id2
3
timeslot 3
1
group 1
5
timeslot 5
1
group 1
System response COMMAND ACCEPTED
Example 3 {28351} This example displays PXP DPROC information. lock pcu_0 dproc 4 0 Where:
68P02901W23-S
is: pcu_0
location
dproc
device_name
4
mms_id1
0
mms_id2
3-433 Nov 2009
Examples
Chapter 3: Device/function related commands
System response This command will affect the following link devices --------------------------------------------------GDS 4
The GDS carries GPRS data traffic between the BSC and the PCU Loss of a GDS device will reduce GPRS traffic capacity between the BSC and the PCU. A PXP or PRP DPROC with no GDSs in service will not be able to schedule any GPRS traffic.
GSL 0 0 The GSL carries signaling traffic between the BSC and the PCU. If there are no B-U GSL devices, the PCU will go out of service. GSL 0 2 The GSL carries signaling traffic between the BSC and the PCU. If there are no B-U GSL devices, the PCU will go out of service. Are you sure (y=yes,n=no)?
Example 4 {34321} This example locks a cage and displays a confirmed command. A warning about the cage lock is issued. lock_device bsc cage 1 0 Where:
is: bsc
location
cage
device_name
1
device_id1
0
device_id2
System response CAGE 1
This will affect all devices in this CAGE and any associated
Extension CAGEs. Are you sure (y=yes,n=no)? yes COMMAND ACCEPTED
3-434
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 5 {34321} This example locks a cage when the lock command action results in the standby BSP going out of service. lock_device bsc cage 1 0 Where:
is: bsc
location
cage
device_name
1
device_id1
0
device_id2
System response CAGE 1
This will affect all devices in this CAGE and any associated
Extension CAGEs. WARNING: This will result in the loss of the standby BSP at this BSC. Are you sure (y=yes,n=no)? yes COMMAND ACCEPTED
Example 6 {34321} This example displays warning about links impacted by a cage transition. lock_device 0 cage 1 0 0 Where:
68P02901W23-S
is: 0
location
cage
device_name
1
device_id1
0
device_id2
0
device_id3
3-435 Nov 2009
Examples
Chapter 3: Device/function related commands
System response CAGE 1
This will affect all devices in this CAGE and any associated
Extension CAGEs. This command will affect the following link devices: ---------------------------------------------------OML 1
The OML carries operations and maintenance traffic between the BSS and the OMC. If there are no B-U OML devices, the OMC will not be able to manage the BSS.
MTL 0
The MTL carries signaling traffic between the BSS and the MSC. If there are no B-U MTL devices, all cells in the BSS will become blocked.
MTL 2
The MTL carries signaling traffic between the BSS and the MSC. If there are no B-U MTL devices, all cells in the BSS will become blocked.
RSL 7 0
This command may affect service to the BTS. Use the state command to verify if this is the last RSL to the BTS. The RSL carries signaling traffic between the BSC and a BTS. If there are no B-U RSL devices to a given BTS, all access to the site will be lost.
RSL 7 1
This command may affect service to the BTS. Use the state command to verify if this is the last RSL to the BTS. The RSL carries signaling traffic between the BSC and a BTS. If there are no B-U RSL devices to a given BTS, all access to the site will be lost.
RSL 11 0
This command may affect service to the BTS. Use the state command to verify if this is the last RSL to the BTS. The RSL carries signaling traffic between the BSC and a BTS. If there are no B-U RSL devices to a given BTS, all access to the site will be lost.
RSL 12 0
This command may affect service to the BTS. Use the state command to verify if this is the last RSL to the BTS. The RSL carries signaling traffic between the BSC and a BTS. If there are no B-U RSL devices to a given BTS, all access to the site will be lost.
Are you sure (y=yes,n=no)? yes COMMAND ACCEPTED
3-436
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
References Related commands disp_equipment on page 3-283
equip on page 3-403
reset_device on page 3-485
shutdown_device on page 3-502
state on page 3-515
unequip on page 3-570
unlock_device on page 3-581
68P02901W23-S
3-437 Nov 2009
Login
Chapter 3: Device/function related commands
Login ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{27508}
Description The login command authenticates a qcomm user of certain access level. Security level
1
Supported by OMC-R GUI
No
Command type
B (operator actions required)
Prerequisites
None
Format Syntax login
Example
NOTE •
BSS does not support login command to be executed twice without logout.
•
The password shown in this example is only for information. The passwords are not displayed when entered.
Example 1 This example authenticates an operator to log in with the unix account information or field engineer user information. login
3-438
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Example
System response Please input your UNIX account information. Login: abcdef Password: abcdef COMMAND ACCEPTED
Example 2 {27508} In this example, the OML link is up and fieldeng_always_enabled is set to 0 login
System response Please input your UNIX account information. Login: abcdef Password: abcdef COMMAND ACCEPTED
Example 3 {27508} In this example, the OML link is down and fieldeng_always_enabled is set to 0 login
68P02901W23-S
3-439 Nov 2009
Example
Chapter 3: Device/function related commands
System response Please input your Field Engineer account information. Login: abcd Password: abcdef WARNING: Login incorrect Please input your Field Engineer account information. Login: abcd Password: abcdef WARNING: Login incorrect Please input your Field Engineer account information. Login: abcd Password: abcdef WARNING: Login incorrect COMMAND REJECTED: Login Blocked.
3-440
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Logout
Logout ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
{27508}
Description The logout command terminates all the activities of the current operator. Security level
1
Supported by OMC-R GUI
No
Command type
B (operator actions required)
Prerequisites
None
Format Syntax logout
68P02901W23-S
3-441 Nov 2009
mod_conn
Chapter 3: Device/function related commands
mod_conn ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The mod_conn command modifies the MMS connectivity between the RXCDR and the BSS. This command allows the operator to change the E1 connectivity information identifying which RXCDR is associated with the E1 link and the device identity within the RXCDR to which the E1 link is connected. This connectivity information must be specified for each E1 link connecting to an RXCDR. Security level
4
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
The AXCDR or ABSS device specified in the command must be equipped in the BSS database. No XBL devices can be equipped that use the local MMS when changing the BSS or RXCDR network entity identifier. The local MMS must be locked before the connectivity is modified.
Operator actions
Change the security level to 2. Lock the local MMS before modifying the connectivity.
Format Syntax mod_conn
Input parameters local_mms_id_1 First identifier of the MMS at the local site. The term ‘local site’ refers to the site where the command is being entered. local_mms_id_2 Second identifier of the MMS at the local site.
3-442
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Example
network_entity_id The AXCDR or ABSS device identifier that represents the actual RXCDR or BSS with which this MMS is communicating. remote_mms_id_1 First identifier of the MMS at the remote site. The term ‘remote site’ refers to the site to which the local site is connected. remote_mms_id_2 Second identifier of the MMS at the remote site. The mod_conn command can be executed from either the BSC or the RXCDR. The ranges for several input parameters depend on where the command is executed, as shown in Table 3-32.
Table 3-32
mod_conn valid ranges Execution location
Input parameter
BSC
RXCDR
local_mms_id_1
{22169} 0 to 95
0 to 123
local_mms_id_2
0 or 1
0 or 1
network_entity_id
1 to 254
1 to 254
remote_mms_id_1
0 to 123
{22169} 0 to 95
remote_mms_id_2
0 or 1
0 or 1
Example This example changes MMS connectivity between BSC MMS 4 1 and RXCDR MMS 9 0 of RXCDR 3, which is represented by equipped device AXCDR 3. mod_conn 4 1 3 9 0 Where:
is: 4
local_mms_id_1
1
local_mms_id_2
3
network_entity_id
9
remote_mms_id_1
0
remote_mms_id_2
System response: COMMAND ACCEPTED
68P02901W23-S
3-443 Nov 2009
References
Chapter 3: Device/function related commands
References Related commands add_conn on page 3-33
3-444
del_conn on page 3-195
disp_conn on page 3-261
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
mod_nsvc
mod_nsvc ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The mod_nsvc command modifies the frame relay committed information rate, the frame relay burst size, and the frame relay burst excess for a specified Network Service - Virtual Connection Identifier (NSVCI), at a specific PCU. Security level
4
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
The GPRS feature must be unrestricted.
Operator action
The operator must answer the prompts.
Format Syntax mod_nsvc
Input parameter pcu_id {27955A} Specifies the unique identifier of the PCU, as pcu or pcu_0. ns_vci Specifies the unique identifier of the NSVC mapping and identifier of the object. The range is 0 to 65535. Prompts are then displayed as follows: Enter the Committed Information rate: Enter the Committed Burst Size: Enter the Burst Excess: The first prompt specifies the frame relay committed information rate ns_commit_info_rate (0 to 1984). There is no default. The second specifies the frame relay burst size ns_burst_size (0 to 1984). There is no default.
68P02901W23-S
3-445 Nov 2009
Example
Chapter 3: Device/function related commands
The third specifies the frame relay burst excess ns_burst_excess (0 to 1984). There is no default.
NOTE ns_burst_size and ns_burst_excess, both must not be 0. If either ns_commit_info_rate or ns_burst_size is 0, then both must be 0.
Example The following example modifies the frame relay committed information rate, the frame relay burst size, and the frame relay burst excess for NSVCI 6, at PCU_2 site. mod_nsvc pcu_2 6 Where:
is: pcu_2
PCU site 2
6
NSVCI identifier
System response Enter the Committed Information Rate:64
Enter the Committed Burst Size:64
Enter the Burst Excess:64
WARNING:
This may cause a loss of data.
Are you sure (y=yes, n=no) ? y
COMMAND ACCEPTED
References Related commands del_nsvc on page 3-202
3-446
add_nsvc on page 3-48
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
modify_neighbor
modify_neighbor ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The modify_neighbor command modifies the value of a GSM or UTRAN neighbor cell parameter. The neighbor_cell_id can be a test cell neighbor. The changing of the ba_bcch parameter is only allowed for test neighbors which are on the BA_SACCH list of the cell. To add a neighbor to the BA_BCCH list without adding to the BA_SACCH list, use the add_neighbor command. To remove a neighbor from the BA_BCCH list which is not on the BA_SACCH list, use the del_neighbor command. When pgbt_mode is set to 1, a new neighbor is auto-equipped with its BCCH frequency set to the BCCH frequency of the serving cell. This neighbor cell cannot be modified by the modify_neighbor command. If the Inter-RAT handover feature or Enhanced 2G/3G handover feature (which includes Enhanced Inter-RAT handover) is unrestricted, handovers can be made to UTRAN cells. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
The changing of the synchronized parameter is only allowed for neighbors at the site of the source cell. If the neighbor is a UTRAN cell, the Inter-RAT handover feature must be unrestricted. A UTRAN neighbor specific parameter cannot be modified for a GSM neighbor cell. A GSM neighbor specific parameter cannot be modified for a UTRAN neighbor cell. The specified UTRAN cell identifier must exist as a neighbor cell of the GSM source cell. If the neighbor is a UTRAN cell, the Inter-RAT handover feature or Enhanced 2G/3G handover feature must be unrestricted.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
68P02901W23-S
3-447 Nov 2009
Format
Chapter 3: Device/function related commands
Format Syntax modify_neighbor
Input parameters source_cell_id Cell identity of the source cell. neighbor_cell_id Cell identity of the neighbor cell whose parameter value is being changed. The format for the GSM cell ID depends on: •
The system used (PGSM, EGSM, DCS1800, PCS1900, or GSM850).
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
•
Whether the cell is a UTRAN cell. The cell_id can also be a cell name created using the cell_name command. When the cell name is entered, it must be placed inside double quotation marks.
For an internal neighbor cell only, the cell_id can also be a cell name created using the cell_name command. A cell_name cannot be used to specify an external neighbor cell. When the cell name is entered, it must be placed inside double quotation marks. parameter Neighbor cell parameter to be changed, one of: Parameter
Action
adap_trigger_pbgt_nbr
Specifies the cumulative area for the adaptive handover power budget algorithm; valid only for SACCH and SACCH/BCCH neighbors.
adj_chan_intf_test
Turns adjacent channel interference on or off.
ba_bcch
Adds or deletes a neighbor cell from the BA_BCCH list.
ba_gprs
Adds or deletes a neighbor cell from the BA_GPRS list.
congest_ho_margin
Determines the hand over margin to be used in the event of congestion. This value is only changed when either the Directed Retry or alternate congestion relief feature is enabled. This attribute is only valid for SACCH neighbors. If the directed retry feature is not enabled, the value defaults to the value of the ho_margin_cell of the neighbor. The system does not prompt for the congest_ho_margin value if the Directed Retry option was not purchased. Continued
3-448
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
Parameter
Action
dr_allowed
Allows a directed retry to an external neighbor during the assignment procedure. An external handover is only initiated if either the dr_standard_congest or dr_ho_during_assign parameter is enabled. This attribute is only valid for SACCH neighbors. The system does not prompt for the dr_allowed value if the Directed Retry option was not purchased.
ho_margin_cell
Changes handover margin of a neighbor cell.
ho_margin_rxlev
Sets the value to be applied to the power budget calculation when calls are handed over due to transmission levels (rxlev). If the power budget value minus the ho_margin_rxlev is less than 0 for a cell, that cell is excluded from the neighbor list. This parameter also interacts with the bounce_protect_mar to prevent reverse handovers due to power budget reasons. Refer to the bounce_protect_mar description.
ho_margin_rxqual
Sets the value to be applied to the power budget calculation when calls are handed over due to transmission quality levels (rxqual). If the power budget value minus the ho_margin_rxqual is less than 0 for a cell, that cell is excluded from the neighbor list. This parameter also interacts with the bounce_protect_mar to prevent reverse handovers due to power budget reasons. Refer to the bounce_protect_mar description.
interfering_nbr
Enables or disables the interference algorithm for the inner zone for this neighbor. This is allowed only if both: •
The Concentric Cells feature is enabled.
•
The inner_zone_alg is set to 2. If the interfering_nbr parameter is enabled, the system displays the inner_zone_threshold and inner_zone_margin prompts. Pressing the Return (Enter) key without entering new values for the inner_zone_threshold and the inner_zone_margin prompts will keep any existing values.
ms_txpwr_max_cell
Changes the maximum MS transmitted power for a neighbor cell.
neighboring_range
Changes which range the neighbor borders on in an extended cell.
pbgt_alg_type
Changes the power budget algorithm type.
pbgt_hreqave
Changes the power budget hreqave.
rxlev_min_cell
Changes minimum receive level for a neighbor cell.
synchronized
Allows synchronized handovers for neighbor cells.
fdd_arfcn
Indicates the frequency of a UTRAN cell. Continued
68P02901W23-S
3-449 Nov 2009
Format
Chapter 3: Device/function related commands
Parameter
Action
scr_code
Indicates the primary scrambling code of a UTRAN cell.
diversity_enabled
Indicates whether diversity is applied in a UTRAN cell.
umts_meas_margin
Defines the per neighbor handover threshold. Only valid when a UTRAN BCCH or SACCH neighbor cell is specified.
umts_ncell_avg_period
Defines the per neighbor averaging period. Only valid when a UTRAN BCCH or SACCH neighbor cell is specified.
umts_ba_bcch
Adds or deletes a UTRAN BCCH neighbor from the UMTS_BA_BCCH list.
{31400} tdd_arfcn
Indicates the TD-SCDMA frequency. This is a Read-Write attribute of the UTRAN Neighbor Cell. When tdOpt is restricted, this parameter cannot be modified.
{31400} tdd_cell_param
Indicates the TD-SCDMA cell parameter as defined in TS25.223. This is a Read-Write attribute of the UTRAN Neighbor Cell. When tdOpt is restricted, this parameter cannot be modified.
{31400} tdd_tstd_mode
Indicates the TD-SCDMA Time Switched Transmit Diversity mode. This is a Read-Write attribute of the UTRAN Neighbor Cell. When tdOpt is restricted, this parameter cannot be modified.
{31400} tdd_sctd_mode
Indicates the TD-SCDMA cell diversity capability (Space Code Transmit Diversity). This is a Read-Write attribute of the UTRAN Neighbor Cell.
value The new value of the selected neighbor cell parameter. Values for this field are dependent upon the selected parameter. Parameter
Value
adap_trigger_pbgt_nbr
0 to 255; default is 40 (the value of 40 corresponds to a hreqave of 8 and a handover margin of 5)
adj_chan_intf_test
0 (no) or 1 (yes)
ba_bcch
add or delete
congest_ho_margin
-63 to 63
dr_allowed
0 (no) or 1 (yes)
ho_margin_cell
-63 to 63
ho_margin_rxlev
-63 to 63
ho_margin_rxqual
-63 to 63
ho_margin_type5
-63 to 63
interfering_nbr
0 (no) or 1 (yes)
ms_txpwr_max_cell
PGSM or EGSM: 5 to 39 (odd values only) DCS1800: 0 to 30 (even values only) PCS1900: 0 to 30 (even values only) GSM850: 5 to 39 (odd values only) Continued
3-450
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Parameter
Value
neighboring_range
normal (neighbor is a normal range cell) extended (neighbor is an extended range cell)
pbgt_alg_type
1 to 6
pbgt_hreqave
1 to 31
rxlev_min_cell
0 to 63
synchronized
yes or no
fdd_arfcn
10562 to 10838
scr_code
0 to 511
diversity_enabled
0 or 1
umts_meas_margin
0 to 20 dB; default is 3 dB (for UTRAN BCCH or UTRAN SACCH neighbors if 2G/3G Handover feature is unrestricted)
umts_ncell_avg_period
1 to 12; default is 6 (for UTRAN BCCH or UTRAN SACCH neighbors if 2G/3G Handover feature is unrestricted)
umts_ba_bcch
Add or delete (for UTRAN BCCH neighbors only)
{31400} tdd_arfcn
10054 to 10121
{31400} tdd_cell_param
0 to 127
{31400} tdd_tstd_mode
0 (Disabled) or 1(Enabled); default is 0
{31400} tdd_sctd_mode
0 (Disabled) or 1(Enabled); default is 0
NOTE If the pbgt_alg_type, adj_chan_intf_test or interfering_nbr is modified by this command, additional prompts display. Refer to the description of the add_neighbor command for the prompted parameter values.
Examples Example 1 This example adds the frequency of neighbor cell 5 4 3 2 1 4344 9755 to the BA_BCCH list of source cell 5 4 3 2 1 676 8645. The cell numbers are in seven parameter format. modify_neighbor 5 4 3 2 1 676 8645 5 4 3 2 1 4344 9755 ba_bcch add Where:
68P02901W23-S
is: 5 4 3 2 1 676 8645
src_cell_id
5 4 3 2 1 4344 9755
neighbor_cell_id
ba_bcch
the parameter to be modified.
add
the parameter value.
3-451 Nov 2009
Examples
Chapter 3: Device/function related commands
System response COMMAND ACCEPTED
Example 2 The example below shows the same cell numbers in four parameter format: modify_neighbor 543 21 676 8645 543 21 4344 9755 ba_bcch add Where:
is: 543 21 676 8645
src_cell_id
543 21 4344 9755
neighbor_cell_id
ba_bcch
the parameter to be modified.
add
the parameter value.
System response COMMAND ACCEPTED
Example 3 This example changes the power budget algorithm to 3 for neighbor cell 5 4 3 2 1 344 975 of src_cell 5 4 3 2 1 667 865. Additional prompts display.
NOTE This example shows interaction associated with the M-Cellmicro option.
modify_neighbor 5 4 3 2 1 667 865 5 4 3 2 1 344 975 pbgt_alg_type 3 Where:
is: 5 4 3 2 1 667 865
src_cell_id
5 4 3 2 1 344 975
neighbor_cell_id
pbgt_alg_type
the parameter to be modified.
3
the parameter value.
System response Enter the uplink receive level threshold of the serving cell: 25 COMMAND ACCEPTED Enter the downlink receive level threshold of the serving cell: 25 3-452
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 4 This example sets the interfering_nbr to 1 (yes). modify_neighbor 5 4 3 2 1 667 865 5 4 3 2 1 344 975 interfering_nbr 1 Where:
is: 5 4 3 2 1 667 865
src_cell_id
5 4 3 2 1 344 975
neighbor_cell_id
interfering_nbr
the parameter to be modified.
1
the parameter value.
System response Enter the threshold for inner zone handover: 1
Enter the margin for inner zone handover: 1
COMMAND ACCEPTED
Example 5 This example modifies the scr_code element of UTRAN neighbor cell 4 9 6 2 3 1 1 1 1 to a value of 5 as a neighbor of source GSM cell 0 0 1 0 1 1 4. modify_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 scr_code 5 Where:
is: 0010114
src_cell_id (GSM)
496231111
neighbor_cell_id (UTRAN)
scr_code
the parameter to be modified.
5
the parameter value.
System response COMMAND ACCEPTED
68P02901W23-S
3-453 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 6 This example modifies the umts_ba_type for UTRAN BCCH neighbor l 4 9 6 2 3 1 1 1 1 of GSM cell 0 0 1 0 1 1 4 to include it in the UTRAN BCCH neighbor list. modify_neighbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 umts_ba_bcch add Where:
is: 0010114
src_cell_id (GSM)
496231111
neighbor_cell_id (UTRAN)
umts_ba_bcch
the parameter to be modified.
add
the parameter value.
System response COMMAND ACCEPTED
Example 7 {31400} This example modifies the tdd_cell_param attribute to a value of 100 for TD-SCDMA cell 4 9 6 2 3 1 1 1 1 as a neighbor of GSM cell 0 0 1 0 1 1 4. modify_nieghbor 0 0 1 0 1 1 4 4 9 6 2 3 1 1 1 1 tdd_cell_parameter 100 Where:
is: 0010114
src_cell_id (GSM)
496231111
neighbor_cell_id (UTRAN)
tdd_cell_param
the parameter to be modified.
100
the parameter value.
System response COMMAND ACCEPTED
NOTE This response is also applied for tdd_arfcn, tstd_mode, and tdd_diversity_enabled for TD-SCDMA neighbor cell attributes.
3-454
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
References Related commands add_cell on page 3-22
add_neighbor on page 3-35
copy_cell on page 3-179
del_cell on page 3-192
del_neighbor on page 3-197
disp_cell on page 3-241
disp_gsm_cells on page 3-314
disp_neighbor on page 3-343
68P02901W23-S
3-455 Nov 2009
modify_value
Chapter 3: Device/function related commands
modify_value ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The modify_value command modifies parameter values for equipped devices or functions. These values can be displayed using the disp_equipment command. This command is rejected if a dual band Horizon II macro cabinet contains an invalid HorizonII Dual Band DRI setup.
NOTE Enter this command at the BSC only. This command does not work at a BTS site. Contact the OMC-R for help.
Security level
4
Supported by OMC-R GUI
Yes
Command type
The type is dependent on the parameter being modified.
Prerequisites
The modify_value command can only be entered at the BSC. Individual prerequisites are given for modify_value parameters as relevant. The GPRS PICP MSI type is not supported by this command.
Operator actions
To use all as the location parameter, place the system in the SYSGEN ON mode before entering the command.
NOTE Refer to the descriptions of individual parameters for additional operator actions.
Format Syntax modify_value
Input parameters location
3-456
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
Specifies the location of the device. Values are: 0 or bsc
BSC
1 - 140
BTS
{27955A} pcu or pcu_0
PCU
all
Every equipped device or function of the specified type. Only applicable to MMS, RSL, and XBL. This value is only applicable during SYSGEN ON mode. If all is entered, the parameters dev_func_id1, dev_func_id2 and dev_func_id3 are not required.
value_name The device or function parameter name. Refer to the individual parameter listing in Chapter 8 Device/Function parameters for descriptions and valid values of these parameters. new_value The value to be assigned to the named parameter. Refer to the individual parameter descriptions in Chapter 8 Device/Function parameters for valid values. dev_func This value identifies the device or function affected by the modified parameter. For example, BSP, GCLK, SITE, as relevant to the value_name parameter. See Chapter 8 Device/Function parameters. dev_func_id1 Values are dependent on the device or function type. dev_func_id2 Values are dependent on the device or function type. dev_func_id3 Values are dependent on the device or function type.
NOTE •
When changing certain cabinet types with this command, the following message is displayed: Cannot change to new cab type as bts power control is enabled.
•
68P02901W23-S
When an attempt is made to modify ext_timeslots, or pkt_radio_type, and the requested PDTCHs exceed the GDS or PMC capacity on the PCU, the BSS accepts the request and issues a warning to indicate that there is not enough GDS or PMC resource available.
3-457 Nov 2009
Examples
Chapter 3: Device/function related commands
Examples Example 1 In this example, the maximum number of DRIs on DHP 4 2 0 at site 7 is changed to 5: modify_value 7 max_dris 5 dhp 4 2 0 Where:
is: 7
location
max_dris
value_name
5
new_value
dhp
dev_func
4
dev_func_id1
2
dev_func_id2
0
dev_func_id3
System response COMMAND ACCEPTED
Example 2 This example modifies the value of cic_unblock_thresh when eac_mode is enabled and AMR or GSM HR is unrestricted for an AXCDR at site 0. modify_value 0 cic_unblock_thresh 250 AXCDR 1 2 8 Where:
is: 0
location
cic_unblock_thresh
value_name
250
new_value
AXCDR
dev_func
1
dev_func_id1
2
dev_func_id2
8
dev_func_id3
System response COMMAND ACCEPTED
3-458
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 3 This example disables eac_mode whether AMR HR or GSM HR is enabled or not for an AXCDR at site 0. modify_value 0 eac_mode no AXCDR 1 2 8 Where:
is: 0
location
eac_mode
value_name
no
new_value
AXCDR
dev_func
1
dev_func_id1
2
dev_func_id2
8
dev_func_id3
System response WARNING: Disabling enhanced auto connect mode will terminate all active calls through this Associated RXCDR from the BSC, and configure the CIC Ater assignments as for Auto Connect mode Are you sure (y/n) y COMMAND ACCEPTED
Example 4 This example enables eac_mode with cic_validation enabled and amr_bss_half_rate_enabled and gsm_bss_half_rate_enabled disabled for an AXCDR at site 0. modify_value 0 eac_mode yes AXCDR 1 2 8 Where:
68P02901W23-S
is: 0
location
eac_mode
value_name
yes
new_value
AXCDR
dev_func
1
dev_func_id1
2
dev_func_id2
8
dev_func_id3
3-459 Nov 2009
Examples
Chapter 3: Device/function related commands
System response WARNING: AMR and GSM Half Rate is currently disabled at this BSC. COMMAND ACCEPTED
Example 5 In this example, the frequency_type for a Horizon II macro cabinet is modified from EGSM90000 to EGSM900 and DCS1800 for Dual band on a single cabinet: modify_value 7 frequency_type 6 CAB 0 0 0 Where:
is: 7
location
frequency_type
value_name
6
new_value
CAB
dev_func
0
dev_func_id1
0
dev_func_id2
0
dev_func_id3
System response COMMAND ACCEPTED
Example 6 This example modifies the type of cabinet 15 0 0 from Horizon macro extension to Horizon II mini extension, where the current cabinet has no dependent devices. modify_value 5 cabinet_type 27 CAB 15 0 0 Where:
3-460
is: 5
location
cabinet_type
value_name
27
new_value
CAB
dev_func
15
dev_func_id1
0
dev_func_id2
0
dev_func_id3
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response COMMAND ACCEPTED
Example 7 This example modifies pkt_radio_type from 1 to 3 with a warning that not enough GDS resources handle PDTCHs. modify_value 1 pkt_radio_type 3 rtf 1 1 Where:
is: 1
location
pkt_radio_type
value_name
3
new_value
rtf
dev_func
1
dev_func_id1
1
dev_func_id2
System response Enter the rtf_ds0_count: 6 WARNING: This operation may cause a carrier to be taken out of service and calls affected by this carrier may be lost. Loss of calls depends on the availability of other carriers. Are you sure (y=yes, n=no)? y COMMAND ACCEPTED: WARNING: Insufficient GDS resources available for all PDTCHs on the PCU.
68P02901W23-S
3-461 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 8 {28337} This example modifies max_mtls values to 31 on GPROC3-2. modify_value 0 max_mtls 31 LCF 0 0 0 Where:
is: 0
location
max_mtls
value_name
31
new_value
LCF
dev_func
0
dev_func_id1
0
dev_func_id2
0
dev_func_id3
System response WARNING: HSP LCF equipage may trigger GPROC preemption. Are you sure (y=yes,n=no)? y COMMAND ACCEPTED. WARNING: Resources are not currently available. Parent entity must be manually reset before change takes effect.
Example 9 {28337} This example attempts to modify the max_mtls value to 31 on GPROC3. modify_value 0 max_mtls 31 LCF 1 0 0 Where:
3-462
is: 0
location
max_mtls
value_name
31
new_value
LCF
dev_func
1
dev_func_id1
0
dev_func_id2
0
dev_func_id3
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response WARNING: HSP LCF equipage may trigger GPROC preemption. Are you sure (y=yes,n=no)? y COMMAND ACCEPTED. WARNING: Resources are not currently available. Parent entity must be manually reset before change takes effect.
Example 10 {28337} This example attempts to increase the max_gsls value from 0 on LCF which has already managed HSP MTL. modify_value 0 max_gsls 1 LCF 1 0 0 Where:
is: 0
location
max_mtls
value_name
1
new_value
LCF
dev_func
1
dev_func_id1
0
dev_func_id2
0
dev_func_id3
System response COMMAND REJECTED: Insufficient GPROC timeslots available
68P02901W23-S
3-463 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 11 {28337} This example attempts to increase the max_cbls value from 0 on LCF which has already managed HSP MTL. modify_value 0 max_cbls 1 LCF 1 0 0 Where:
is: 0
location
max_cbls
value_name
1
new_value
LCF
dev_func
1
dev_func_id1
0
dev_func_id2
0
dev_func_id3
System response COMMAND REJECTED: Insufficient GPROC timeslots available
Example 12 {28337} This example attempts to increase the max_opls value from 0 on LCF which has already managed HSP MTL. modify_value 0 max_opls 1 LCF 1 0 0 Where:
is: 0
location
max_opls
value_name
1
new_value
LCF
dev_func
1
dev_func_id1
0
dev_func_id2
0
dev_func_id3
System response COMMAND REJECTED: Insufficient GPROC timeslots available
3-464
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 13 {28351} This example modifies the base IP address of the PCU. modify_value 0 base_ip_address 10.3.16.36 pcu 0 Where:
is: 0
location
base_ip_address
value_name
10.3.16.36
new_value
pcu
dev_func
0
dev_func_id1
System response Enter the GDS subnet mask: 255.255.192.0 WARNING: Changing base_ip_address will cycle device PCU. Are you sure (y=yes,n=no)? y COMMAND ACCEPTED
Example 14 {28351} This example modifies the subnet mask of the PCU. modify_value 0 gds_subnet_mask 255.255.255.22 pcu 0 Where:
is: 0
location
gds_subnet_mask
value_name
255.255.255.22
new_value
pcu
dev_func
0
dev_func_id1
System response WARNING: Changing gds_subnet_mask will cycle device PCU. Are you sure (y=yes,n=no)? y COMMAND ACCEPTED
68P02901W23-S
3-465 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 15 {26481} In this example, the operator attempts to enable opto alarm (out of range 1-6) through modify_val for EAS equipped to H2micro cabinet. modify_value 8 opto_reporting on eas 0 0 0 Where:
is: 8
location
opto_reporting
value_name
on
new_value
eas
dev_func
0
dev_func_id1
0
dev_func_id2
0
dev_func_id3
System response Enter the opto(s) whose state changes should now be reported: 3 6 9 ERROR: Range Error, parameter number: 3.
Example 16 {28351} This example modifies the base IP address of the PSI. modify_value 0 base_ip_address 10.3.16.36 psi 1 Where:
is: 0
location
base_ip_address
value_name
10.3.16.36
new_value
psi
dev_func
1
dev_func_id1
System response Enter the subnet mask: 255.255.255.0 WARNING: Changing base IP address, subnet mask will cycle device ETH. Are you sure (y=yes,n=no)? y COMMAND ACCEPTED
3-466
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 17 {23311A} This example sets the number of extended PDCHs to 3 for RTF 5,11 in site 3. modify_val 3 ext_pdchs 3 rtf 5 11 Where:
is: 3
location
ext_pdchs
value_name
3
new_value
rtf
dev_func
5
dev_func_id1
11
dev_func_id2
System response COMMAND ACCEPTED
Example 18 {23311A} This example attempts to set ext_timeslots for the RTF (5,11) to 2 when RTF 5,11 is configured for Extended GPRS and ext_pdchs is set to 3. modify_value 5 ext_timeslots 2 rtf 5 11 Where:
is: 5
location
ext_timeslots
value_name
2
new_value
rtf
dev_func
5
dev_func_id1
11
dev_func_id2
System response COMMAND REJECTED: Value of ext_timeslots shall be >= ext_pdchs for ERC GPRS RTF
68P02901W23-S
3-467 Nov 2009
References
Chapter 3: Device/function related commands
Example 19 {23311A} This example attempts to change pkt_radio_type = None for the RTF (5,11) when ext_pdchs in the RTF is set to 3. modify_value 5 pkt_radio_type None rtf 5 11 Where:
is: 5
location
pkt_radio_type
value_name
None
new_value
rtf
dev_func
5
dev_func_id1
11
dev_func_id2
System response COMMAND REJECTED: Value of ext_pdchs shall be 0 when pkt_radio_type = NONE for the RTF
References Related commands disp_equipment on page 3-283
3-468
equip on page 3-403
reassign on page 3-477
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
nacc_nc2_enabled
nacc_nc2_enabled ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The per-BSS element nacc_nc2_enabled allows the customer to enable or disable the NC2 mode of NACC. This element can be accessed and updated both in and out of Sysgen mode. Type
A (no operator actions)
Supported by OMC-R GUI
No
Cell description required
No
Dependencies
None
Syntax Change command string chg_element nacc_nc2_enabled
Display command string disp_element nacc_nc2_enabled
Values Value type
Boolean
Valid range
0 to 1
Default value
68P02901W23-S
0
Disables the NC2 mode of NACC.
1
Enables the NC2 mode of NACC.
0
3-469 Nov 2009
page
Chapter 3: Device/function related commands
page ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The page command enables or disables pagination for display commands. The page command can also specify the number of lines displayed per page for display commands.
NOTE The page command applies only to the current session and the current processor board (GPROC, GPROC2, or GPROC3). Setting it from an OMC-R rlogin does not affect any other OMC-R rlogins or TTY MMI logins. Setting it from a TTY MMI login does not affect any other TTY MMI logins or OMC-R rlogins. At every new login, it is reset to off.
Security level
1
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
None
Format Syntax page
Input parameter input Valid input formats are as follows:
3-470
Input
Action
Range
off
Disables pagination.
No range. This is the default value.
Enables pagination and sets the number of lines displayed per page.
Any numeric value between 20 and 255.
none
Displays current page setting.
Not applicable.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Examples Example 1 This example shows that pagination has been enabled, and displays show 30 lines per page. page 30
Example 2 This example shows that pagination has been disabled. page off
Example 3 This example shows no line number entered. The current setting is displayed. page 25
References Related commands The page command affects the output from the following commands. assess on page 3-54
disp_act_alarm on page 3-225
disp_bss on page 3-229
disp_cal_data on page 3-233
disp_cbch_state on page 3-237
disp_cell on page 3-241
disp_cell_status on page 3-247
disp_csfp on page 3-263
disp_csfp_status on page 3-267
disp_dte on page 3-269
disp_enable_stat on page 5-12
disp_equipment on page 3-283
disp_gsm_cells on page 3-314
disp_hdlc on page 3-317
disp_hopping on page 3-320
disp_link on page 3-326
disp_link_usage on page 3-328
disp_mms_ts_usage on page 3-330
disp_neighbor on page 3-343
disp_options on page 3-356
disp_processor on page 3-367
disp_rtf_channel on page 3-375
disp_rtf_path on page 3-381
disp_stats on page 5-34
disp_stat_prop on page 5-24
disp_throttle on page 3-386
disp_trace_call on page 3-390
disp_traffic on page 3-394
man on page 4-8
site_audit on page 3-507
state on page 3-515
status_mode on page 3-530
68P02901W23-S
3-471 Nov 2009
query_audits
Chapter 3: Device/function related commands
query_audits ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The query_audits command performs two different functions. The first is to provide a list of all information for all audits for a specific device at the customer site. The second function provides a list of the audits in progress for a specific device at the customer site. {25002} The query_audits supports display of swap_type on TDM devices at location 0 (BSC or RXCDR). The short option displays the state of all audits for a specific device at a site. The long option displays the information for all of the audits for a specific device at the site. The information includes the state and schedule information. There are only three possible System Responses to a query_audits command: •
The display of results.
•
A COMMAND REJECTED message, with the reason (for example, the device is not in the database).
•
ERROR.
The ERROR response is followed by a display of the error description from the following list: Audit not available for unequipped devices. Audit can only be executed on expanded TDM configuration. Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
An operator at the OMC-R must rlogin to a site before an audit can be performed. To audit a PCU site, the GPRS feature must be unrestricted.
Format Syntax query_audits
3-472
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
Input parameters location Specifies the audit location: 0 or bsc
BSC
1 - 140
BTS
{27955A} pcu or pcu_0
PCU
audit_type Specifies the amount of information required. short
Displays all the audits in progress for a specific device at a customer site.
long
Lists the state and schedule information for all the audits for the specified device.
device_name The name that uniquely identifies the device. The valid device names are: BSP
DRI
KSW
BTP
GCLK
MSI
DHP
GPROC
TDM
The following device can be audited at a PCU site using this command: DPROC
MSI
PSP
device_id1 First device identifier. The range of values is 0 to 99. device_id2 Second device identifier. The range of values is 0 to 99. device_id3 Third device identifier. The range of values is 0 to 99.
NOTE Not all devices require all three device IDs.
68P02901W23-S
3-473 Nov 2009
Examples
Chapter 3: Device/function related commands
Examples Example 1 In the following example, the query lists an audit that is idle for a KSW device at the BSC with ID 0 0 0: query_audits 0 long ksw 0 0 0 Where:
is: 0
location
long
audit_type
ksw
device_name
0
device_id1
0
device_id2
0
device_id3
System response Device: KSW
Device id: 0 0 0
Start Time: 00:00
End Time: 00:00
Audit Type: SAFE On/Off State:
Device: KSW
Interval: 01:00
Idle/Active State: IDLE
Site Audit: ON
Cage Audit: ON
Device Audit: ON
Device id: 0 0 0
Start Time: 02:00 End Time: 04:00 Audit Type: INT_LPBK On/Off State:
Interval: 00:15
Idle/Active State: IDLE
Site Audit: ON
Cage Audit: ON
Device Audit: ON
Example 2 The following example lists the audits in progress on the PCU MSI device: query_audits PCU short MSI 0 Where:
3-474
is: PCU
location
short
audit_type
MSI
device_name
0
device_id1
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response Device: MSI
Device id: 0 0 0
Audit Type: SAFE On/Off State:
Idle/Active State: IDLE
Site Audit: ON
Cage Audit: ON
Device Audit: ON
Example 3 The following example lists in long format, the audits in progress on the MSI device at the first PCU: query_audits PCU_0 long MSI 0 Where:
is: PCU_0
location (PCU site 0)
long
audit_type
MSI
device_name
0
device_id1
System response Device: MSI
Device id: 0 0 0
Start Time: 00:00 Audit Type:SAFE
End Time: 00:00
Interval: 00:10
Idle/Active State:IDLE
On/Off State: Site audit:ON
Cage audit:ON
Device audit:ON
Example 4 {25002} The following example lists in long format, the audits in progress on the tdm device: query_audit 0 long tdm 0 Where:
68P02901W23-S
is: 0
location
long
audit_type
tdm
device_name
0
device_id1
3-475 Nov 2009
References
Chapter 3: Device/function related commands
System Response Device: TDM
Device id : 0 0 0
Start Time: 01:00
End Time: 01:00
Audit Type: SAFE On/Off State:
Device: TDM
Interval: 00:00
Idle/Active State: IDLE
Site Audit: ON
Cage Audit: ON
Device Audit: ON
Device id : 0 0 0
Start Time: 03:00
End Time: 03:00
Audit Type: SWAP_TEST On/Off State:
Interval: 00:00
Idle/Active State: IDLE
Site Audit: ON
Cage Audit: ON
Device Audit: ON
References Related commands cage_audit on page 3-58
chg_audit_sched on page 3-76
device_audit on page 3-210
site_audit on page 3-507
3-476
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
reassign
reassign ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The reassign command changes the assignment of a child_dev device from its current parent_func to a new parent_func. For example, a DRI can be reassigned from one DHP, BTP, or BTF to another DHP, BTP, or BTF. The reassign command removes the device from service until the command is accepted. If the DRI is locked after it has been reassigned, the DRI is assigned to the least loaded GPROC when the DRI is unlocked. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
DRIs can only be assigned to GPROCs in the same cage as the DRI. A site device can be reassigned whether in Sysgen mode or not in Sysgen mode. All other devices must be reassigned when not in Sysgen mode. All GPROCs at the BSC (including the BSP) must be stable for at least five consecutive minutes since any GPROC has been transitioned. No BTS sites can be in the process of code loading.
Format Syntax reassign []
68P02901W23-S
3-477 Nov 2009
Format
Chapter 3: Device/function related commands
Input parameters location Specifies the location of the GPROC from which control of a DRI is to be moved. The values are: 0 or bsc
BSC
1 - 140
BTS
pcu, pcu_0 to pcu_2
PCU
child_name Literal that uniquely identifies the device. Current values are: DRI
CBL
GSL
MTL
SITE
child_dev_id_1 The first child device identifier. Values are in the range 0 to 5. child_dev_id_2 The second child device identifier. Values are in the range 0 to 24. child_dev_id_3 The third child device identifier. Valid value is 0. to Optional text that can be entered to make the command more readable. parent_func_name The literal that defines where the device or function is reassigned. Current values are: BTP
Apply to DRIs
BTF DHP LCF
Applies to: CBL, GSL, MTL, SITE
parent_func_id_1 Values are dependent on the device or function type. parent_func_id_2 Values are dependent on the device or function type. parent_func_id_3 Values are dependent on the device or function type.
3-478
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Example
Example Example 1 In this example, DRI 0 7 0 is reassigned from its current GPROC at BTS 8 to DHP 14 2 0: reassign 8 dri 0 7 0 to dhp 14 2 0 Where:
is: 8
location
dri
child_dev_name
0
dri_id_1
7
dri_id_2
0
dri_id_3
to
option text used to make command more readable.
dhp
parent_func_name
14
parent_func_id_1
2
parent_func_id_2
0
parent_func_id_3
System response: WARNING: This will cause the link to temporarily go out of service. Are you sure (y=yes,n=no)? y
68P02901W23-S
3-479 Nov 2009
Example
Chapter 3: Device/function related commands
Example 2 {28337} In this example, HSP MTL is reassigned onto a GPROC3–2. reassign 0 MTL 1 0 0 LCF 0 0 0 Where:
is: 0
location
MTL
child_dev_name
1
child_dev_id_1
0
child_dev_id_2
0
child_dev_id_3
LCF
parent_func_name
0
parent_func_id_1
0
parent_func_id_2
0
parent_func_id_3
System response: COMMAND ACCEPTED
Example 3 {28337} In this example, HSP MTL is reassigned onto a GPROC3. reassign 0 MTL 1 0 0 LCF 2 0 0 Where:
3-480
is: 0
location
MTL
child_dev_name
1
child_dev_id_1
0
child_dev_id_2
0
child_dev_id_3
LCF
parent_func_name
2
parent_func_id_1
0
parent_func_id_2
0
parent_func_id_3
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Example
System response COMMAND REJECTED Wrong GPROC type, display MTL LCF GPROC type to verify.
Example 4 {28337} In this example, HSP MTL is reassigned onto a non HSP LCF on a GPROC3-2. reassign 0 MTL 1 0 0 LCF 3 0 0 Where:
is: 0
location
MTL
child_dev_name
1
child_dev_id_1
0
child_dev_id_2
0
child_dev_id_3
LCF
parent_func_name
3
parent_func_id_1
0
parent_func_id_2
0
parent_func_id_3
System response COMMAND REJECTED Wrong LCF type, display MTL LCF type to verify.
68P02901W23-S
3-481 Nov 2009
References
Chapter 3: Device/function related commands
References Related information The reassign command does not free the RTF associated with the BUSY-UNLOCKED DRI. The RTF remains associated with the DRI after reassignment to another GPROC. In circumstances where the reassignment fails due to catastrophic events, such as hardware failure, the RTF is freed, one transceiver is available and another is found. Where no standby DRIs are available and a BCCH RTF is free, a search is made for a DRI which is assigned to the GPROC, which has the least number of BCCH carrier-implementing DRIs assigned to it. The main reasons for failure to reassign a DRI: •
The destination BTP, BTF, or DHP has reached the maximum number of supportable DRIs.
•
The DRI or GPROC type is not present or it is in an invalid state.
•
The DRI is not in the same cage as the destination BTP, BTF, or DHP.
•
The DRI is not configured due to catastrophic hardware failure.
Related commands disp_equipment on page 3-283
equip on page 3-403
modify_value on page 3-456
disp_processor on page 3-367
3-482
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
reattempt_pl
reattempt_pl ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The reattempt_pl command causes the GCLK to reattempt phase lock. This is permitted only if the GCLK has previously failed to phase lock. Security level
3
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
This command is not allowed while in SYSGEN ON mode.
Format Syntax reattempt_pl
Input parameters location Specifies the location of the GPROC from which control of a DRI is to be moved: 0 or bsc
BSC
1 - 140
BTS
gclk_id The GCLK identifier. The valid values are 0 or 1.
Example In this example, the GCLK 0 is forced to attempt phase lock. reattempt_pl bsc 0 Where:
68P02901W23-S
is: bsc
location
0
gclk_id
3-483 Nov 2009
References
Chapter 3: Device/function related commands
System response COMMAND ACCEPTED
References Related command chg_element on page 3-106.
3-484
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
reset_device
reset_device ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The reset_device command brings a device into service by locking and then unlocking the device. Additionally, a hard reset is performed if the device supports it. The following devices support soft resets: ABSS
AXCDR
CAB
{34321} CAGE
CBL
CIC
COMB
CSFP
DPROC
EAS
GBL
GCLK
GSL
MMS
MTL
OML
OPL
PATH
PCU
RSL
SITE
XBL
TDM
NOTE The reset_device command supports the resetting of extension cabinets of type TCU_2, TCU_6, and HORIZONMACRO_EXT. No other extension cabinet types are supported. The following devices support hard reset: BTP
BSP
DHP
DRI
GPROC
KSW
MSI
NOTE When a KSW is reset, all calls currently in progress are dropped. Normal call processing resumes when the KSW is brought back into service. When this command is entered where an MSI or MMS has an OML, a warning, and a verification request is presented. When this command is entered for an ABSS or AXCDR, a warning, and a verification request is presented. If the reset_device command is applied to an active GCLK, and the standby GCLK is phase locked, the system displays an additional warning message. The system also displays a warning message if the reset_device command is applied to the GCLK. This action swaps the GCLKs and can cause alarms on other devices. If the reset_site command is attempted while the system is initializing, the system displays a COMMAND REJECTED: System still initializing message. {22168} The BSS SW at a BSS enables enhanced capacity mode through reset_device command if the detected hardware contains only the master and redundant DSW2/DSWXs and not KSW/KSWX.
68P02901W23-S
3-485 Nov 2009
Format
Chapter 3: Device/function related commands
For remote transcoding BSC sites, CICs are not reset on a per-MMS basis when the BSC is operating in the dynamic allocation mode. Security level
2
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
This command is invoked irrespective of whether the device is locked or unlocked.
Operator actions
Respond to the verification prompt that is presented if this command is used to reset an MSI or MMS with an OML.
Format General syntax reset_device
Input parameters location Specifies the location of the device to have a hard reset performed or toggled to the locked state: 0 or bsc
BSC
1 - 140
BTS
{27955A} pcu or pcu_0
PCU
device_name Literal that uniquely identifies the device. device_id1 First device identifier. This definition varies with each device. device_id2 Second device identifier. This definition varies with each device. device_id3 Third device identifier. This definition varies with each device.
3-486
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
CIC syntax A form of syntax is available for each method of specifying a CIC. The following CIC syntax applies to local transcoding: reset_device CIC reset_device CIC TO reset_device CIC reset_device CIC reset_device CIC TO The following CIC syntax applies to remote transcoding: reset_device CIC reset_device CIC TO reset_device CIC reset_device CIC reset_device CIC * reset_device CIC TO
Input parameters location Specifies the location of the device: 0 or bsc
BSC
1 - 140
BTS
CIC Literal that uniquely identifies the CIC device. cic_num1 First CIC device number. cic_num2 Last CIC device number in a range. mms_id1 First MMS identifier.
68P02901W23-S
3-487 Nov 2009
Examples
Chapter 3: Device/function related commands
mms_id2 Second MMS identifier, or last in a range if TO is used. timeslot1 First timeslot. timeslot2 Second timeslot, or last in a range if TO is used. group1 First group. group2 Second group. * Indicates all CICs on the MMSs specified in the timeslot, regardless of group.
Examples Example 1 In this example, the MSI device is locked before the command is invoked. When the reset_device command is invoked, a hard reset of an MSI device with ID=1 at the BSC is performed. reset_device bsc MSI 1 Where:
is: bsc
location
MSI
device_name
1
dev_id
System response COMMAND ACCEPTED
3-488
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 2 In this example, the GCLK is being reset. This example shows the warning message and the prompt the system displays whenever the GCLK is reset. reset_device 0 gclk 0 Where:
is: 0
location
gclk
device_name
0
dev_id
System Response This command will cause a swap of the GCLKs. This may cause alarms on other devices. Are you sure (y=yes,n=no)? y COMMAND ACCEPTED
Example 3 This example resets a range of CICs devices, specifying them by their MMS, TS, and group. reset_device bsc cic 2 1 3 1 TO 5 1 Where:
is: BSC
location
CIC
CIC (device_name)
2
mms_ id1
1
mms_ id2
3
timeslot 3
1
group 1
5
timeslot 5
1
group 1
System response COMMAND ACCEPTED
68P02901W23-S
3-489 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 4 {22168} This example enables enhanced capacity mode if the master and redundant DSW2/DSWXs are present. reset_device 0 TDM 1 0 0 Where:
is: 0
location
TDM
device_name
1
dev_id1
0
dev_id2
0
dev_id3
System response COMMAND ACCEPTED
Example 5 {22168} This example attempts to enable the enhanced capacity mode if the master and redundant DSW/DSWX are present. reset_device 0 TDM Where:
is: 0
location
TDM
device_name
System response COMMAND ACCEPTED
3-490
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
Example 6 {22168} This example attempts to enable the enhanced capacity mode if the KSW/KSWX is present. reset_device 0 TDM Where:
is: 0
location
TDM
device_name
System response COMMAND REJECTED: Wrong Hardware configuration detected in the site.
Example 7 {34321} This example attempts to reset a cage and display a confirmed command. A warning about the cage reset_device is displayed. reset_device bsc cage 1 0 Where:
is: bsc
location
cage
device_name
1
device_id1
0
device_id2
System response CAGE 1
This will affect all devices in this CAGE and any associated
Extension CAGEs. Are you sure (y=yes,n=no)? yes COMMAND ACCEPTED
References Related commands ins_device on page 3-423
68P02901W23-S
lock_device on page 3-429
unlock_device on page 3-581
3-491 Nov 2009
reset_site
Chapter 3: Device/function related commands
reset_site ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The reset_site command selectively reboots available sites without rlogin. Typical scenarios for selective rebooting include the following: •
All sites including BSC.
•
All sites excluding BSC.
•
Multiple sites.
•
Single site.
NOTE The all_sites, all_bts, and list of site options are only allowed at the BSC and outside SYSGEN ON mode.
If a site other than the BSC is reset, the terminal being used to enter the command must be attached to that site GPROC to view the outputs generated during a reset. The reset occurs even if the terminal is not connected to the affected site.
CAUTION Commands must be entered within 10 minutes after the MMI-RAM -> prompt displays. If a command is not entered, the system resets. Security level
3
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
None
Operator actions
Place the system in the SYSGEN ON mode before entering this command. The system does not permit resetting all_sites, all_bts or a list of site options in SYSGEN ON mode.
Format Syntax reset_site []
3-492
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Input parameter location Specifies the sites to be reset. Valid values are: all_sites
all sites including BSC
all_bts
all sites excluding BSC
bsc
BSC (site 0)
bsc, 1 - 100
BSC and multiple sites (1 to 100). The bsc string must be entered as the first item in a list of sites. If bsc is included but is not the first item, the command is rejected.
1 - 140
BTS
{27955A} pcu or pcu_0
PCU
NOTE When in SYSGEN ON mode, only the local site is reset. The command is rejected if 0 is entered for a BSC.
Verification messages One of the following verification messages issues before execution. The specific message depends on the value of the location parameter. WARNING: Command will REBOOT the entire BSS. Are you sure (y=yes, n=no)? WARNING: Command will REBOOT all BTS sites. Are you sure (y=yes, n=no)? WARNING: Command will REBOOT the following site(s):18 21 24 Are you sure (y=yes, n=no)? WARNING: Command will REBOOT site 0 (BSC or RXCDR) Are you sure (y=yes, n=no)?
Examples Example 1 In this example, a single site is reset: reset_site 2
68P02901W23-S
3-493 Nov 2009
Examples
Chapter 3: Device/function related commands
Where:
is: 2
location
System response WARNING: Command will REBOOT the following site(s): 2 Are you sure (y=yes, n=no)? y COMMAND ACCEPTED: WARNING REBOOT SITE: site 2 will reboot now!!
Example 2 In this example, all active BTS sites are reset: reset_site all_bts Where:
is: all_bts
location
System response WARNING: Command will REBOOT all BTS sites. Are you sure (y=yes, n=no)?y SITE REBOOT STATUS ---- ------ ------
3-494
5
OUT OF SERVICE: reset_site request is discarded
7
RESET REQUEST IS IN PROGRESS
9
RESET REQUEST IS IN PROGRESS
10
OUT OF SERVICE: reset_site request is discarded
11
OUT OF SERVICE: reset_site request is discarded
15
OUT OF SERVICE: reset_site request is discarded
20
RESET REQUEST IS IN PROGRESS
25
RESET REQUEST IS IN PROGRESS
30
RESET REQUEST IS IN PROGRESS
40
RESET REQUEST IS IN PROGRESS
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
References Related information If the operator is logged in to a non-BSC site and attempts to reset other sites, the command aborts and the following error message displays: COMMAND REJECTED: current site is not authorized to reboot other site(s). to BSC.
Log-in
The following command examples show various command entry formats and the location from where the commands must be entered: Command syntax
Site
reset_site all_sites
BSC
reset_site all_bts
BSC
reset_site bsc
BSC
reset_site 15 5 25 0 2
BSC
reset_site 15, 5, 25, 0, 2
BSC
reset_site 1
BSC or site 1
reset_site bsc,21,17,3,0
BSC
reset_site
BSC or local site
The MMI TTY displays, on success, one of the following statuses for each site requested: •
BSC (20 seconds) TIMEOUT: while waiting to receive ACK message from this site
•
OUT OF SERVICE: reset_site request is discarded
•
NOT EQUIPPED: reset_site request is discarded
•
RESET REQUEST IS IN PROGRESS
•
OUT OF RANGE: currently this site is not supported by CM Database
Related command sysgen_mode on page 3-540
68P02901W23-S
3-495 Nov 2009
set_full_power
Chapter 3: Device/function related commands
set_full_power ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The set_full_power command turns the Full Power mode on or off for a single cell or all cells in a site. The Full Power mode directs a specified cell or all cells at a site to operate at the system's maximum power for a specified length of time. If a site is specified when the set_full_power command is entered, a status listing of all of the cells affected by the command are displayed. Security level
4
Supported by OMC-R GUI
No
Command type
A (no operator actions)
Prerequisites
None
Format Syntax set_full_power [] on set_full_power [] off set_full_power on set_full_power off
Input parameters cell_desc The GSM cell ID of the cell at which full power is to be set preceded by cell_number=. The format for the GSM cell ID depends on:
3-496
•
The system being used (PGSM, EGSM, DCS1800, PCS1900).
•
Whether the seven parameter GSM cell ID format or the four parameter GSM cell ID format has been enabled.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
The name of the cell created using the cell_name command is entered in place of the cell_number. When the cell name is entered, it must be preceded by cell_name= and be placed inside double quotation marks. location Specifies the location. 0 or bsc
BSC
1 - 140
BTS
on/off Select turning on and off Full Power mode. minutes The length of time for the specified cell or location to operate at full power. The valid range is 1 to 1440.
Examples Example 1 The following example turns on the Full Power mode for GSM cell ID 5 4 3 2 1 31967 45988 for 45 minutes. The ID number is in the seven parameter format. set_full_power cell_number=5 4 3 2 1 31967 45988 on 45 Where:
is: 5 4 3 2 1 31967 45988
cell_number
on
turn Full Power mode on.
45
length of time Full Power mode is turned on.
The example below shows the same cell number in four parameter format: set_full_power cell_number=543 21 31967 45988 on 45 Where:
is: 543 21 31967 45988
cell_number
on
turn Full Power mode on.
45
length of time Full Power mode is turned on.
System response COMMAND ACCEPTED
68P02901W23-S
3-497 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 2 The following example turns off the Full Power mode for GSM cell ID 5 4 3 2 1 31967 45988: set_full_power cell_number=5 4 3 2 1 31967 45988 off Where:
is: 5 4 3 2 1 31967 45988
cell_number.
off
turn Full Power mode off.
System response COMMAND ACCEPTED
Example 3 The following example turns on the Full Power mode for all cells at site 5 for 45 minutes: set_full_power 5 on 45 Where:
is: 5
location.
on
turn Full Power mode on.
45
length of time the Full Power mode is turned on.
System response Full Power mode set ON for CELL ID = 5 4 3 2 1 31987 45977 Full Power mode set ON for CELL ID = 5 4 3 2 1 31987 45978
Example 4 The following example turns off the Full Power mode for all cells at site 5. set_full_power 5 off Where:
3-498
is: 5
location
off
turn Full Power mode off.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response Full Power mode set OFF for CELL ID = 5 4 3 2 1 31987 45977 Full Power mode set OFF for CELL ID = 5 4 3 2 1 31987 45978
Example 5 In this example, the affected cell is identified using the cell_name ‘london-south’: set_full_power cell_name=”london-south” on 45 Where:
is: london-south
cell_name
on
turn Full Power mode on.
45
length of time Full Power mode is turned on.
System response COMMAND ACCEPTED
68P02901W23-S
3-499 Nov 2009
set_relay_contact
Chapter 3: Device/function related commands
set_relay_contact ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The set_relay_contact command specifies the relay state for an EAS device when the device is Busy-Unlocked. When equipping an EAS device, the physical wiring of each relay must be specified. These specifications describe whether the relay is open or closed when the relay is deactivated. All relays are deactivated on site initialization. Once the EAS device is Busy-Unlocked, the relay state can be controlled by use of the set_relay_contact command. Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
The EAS device must be equipped. The physical EAS switches must be manually set to match the software settings specified.
Format Syntax set_relay_contact
Input parameters location Specifies the location of the device: 0 or bsc
BSC
1 - 140
BTS
device_id Specifies the device ID of the specific PIX card associated with an EAS device:
3-500
0 to 7
InCell sites
0 to 15
M-Cell sites
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
relay_number Specifies the physical relay number to be set (1 to 4). contact_setting open or 0
open the relay
closed or 1
close the relay
Examples Example 1 For EAS 0 located at the BSC, set relay 4 to be closed circuit: set_relay_contact bsc 0 4 closed Where:
is: bsc
location
0
device_id
4
relay_number
closed
contact_setting
Example 2 For EAS 0 located at the BSC, set relay 2 to be open circuit: set_relay_contact bsc 0 2 0 Where:
is: bsc
location
0
device_id
2
relay_number
0
contact_setting
References Related command equip on page 3-403.
68P02901W23-S
3-501 Nov 2009
shutdown_device
Chapter 3: Device/function related commands
shutdown_device ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The shutdown_device command non-intrusively locks a specific device from further use. The following devices can be shut down with this command: DRI
CIC
MPRT
MTL
The effect of this command is different for each type of specified device: •
For DRIs, the device is locked when the specified time expires. If there are no active calls on the DRI, the shutdown_device command locks the DRI immediately. If there are active calls, no new calls are allowed on the DRI, but no calls are handed off until the shutdown timer expires. At this time, the resource is freed, and calls are forced to move to another carrier in the same cell only. If there are no free carriers in the cell, the call is dropped.
•
For MTLs, the time parameter is ignored and the device is locked immediately.
•
For remote transcoding BSC sites, CICs are not shutdown on a per-MMS basis when the BSC is operating in the dynamic allocation mode.
Security level
3
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
This command is not allowed while in SYSGEN ON mode. This command is only valid when the device is in the UNLOCKED state. This command has no effect on an already locked device.
Operator actions
Unlock the device to be shutdown before entering this command.
Format General syntax shutdown_device [wait ]
3-502
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
Input parameters location Specifies the location of the device: 0 or bsc
BSC
1 - 140
BTS
device_name Literal that uniquely identifies the device. device_id1 First device identifier. This parameter is device dependent. device_id2 Second device identifier. This parameter is device dependent. device_id3 Third device identifier. This parameter is device dependent. seconds The time limit on the transition in seconds. This parameter is device dependent. The maximum time limit cannot exceed 900 seconds (15 minutes). wait The period the system should wait before blocking a busy device.
NOTE The wait parameter is optional for all devices except the CIC. It is required for the CIC device.
CIC syntax A form of syntax is available for each method of specifying a CIC. The following CIC syntax applies to local transcoding: shutdown_device CIC wait shutdown_device CIC TO wait shutdown_device CIC wait shutdown_device CIC wait shutdown_device CIC TO wait
68P02901W23-S
3-503 Nov 2009
Format
Chapter 3: Device/function related commands
The following CIC syntax applies to remote transcoding: shutdown_device CIC wait shutdown_device CIC TO wait shutdown_device CIC wait shutdown_device CIC wait shutdown_device CIC * wait shutdown_device CIC TO wait
Input parameters location Specifies the location of the device: 0 or bsc
BSC
1 - 140
BTS
CIC Literal that uniquely identifies the CIC device. cic_num1 First CIC device number. cic_num2 Last CIC device number in a range. mms_id1 First MMS identifier. mms_id2 Second MMS identifier, or last in a range if TO is used. timeslot1 First timeslot. timeslot2 Second timeslot, or last in a range if TO is used. group1 First group. group2 Second group.
3-504
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
* Indicates all CICs on the MMSs specified in the timeslot, regardless of group. wait The period the system should wait before blocking a busy device.
NOTE The wait parameter is always required for the CIC device.
Examples Example 1 The following example locks a DRI with the IDs 1 2 at site 3 with a time limit of 20 seconds: shutdown_device 3 dri 1 2 0 20 Where:
is: 3
location
dri
device_name
1
device_id1
2
device_id2
0
device_id3
20
seconds
System response COMMAND ACCEPTED
68P02901W23-S
3-505 Nov 2009
References
Chapter 3: Device/function related commands
Example 2 This example shuts down a range of CICs (remote transcoding), specifying them by their MMS, TS, and group, and waiting 5 seconds before blocking a busy device. shutdown_device bsc cic 2 1 3 1 TO 5 1 wait 5 Where:
is: BSC
location
CIC
device_name
2
First MMS id
1
Second MMS id
3
Timeslot 3
1
Group 1
5
Timeslot 5
1
Group 1
wait
Mandatary for CIC
5
wait period
System response COMMAND ACCEPTED
References Related commands
3-506
disp_equipment on page 3-283
equip on page 3-403
lock_device on page 3-429
state on page 3-515
state on page 3-515
unlock_device on page 3-581
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
site_audit
site_audit ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The site_audit command initiates all audits for all devices at the customer site. It also allows the suspension or resumption of all audits at a specific site. If the GPRS feature is unrestricted, this command supports a GPRS PCU. Using the site_audit off command suspends all audits. Using the site_audit on command resumes all audits. There are only two possible System Responses to a site_audit command: •
The display of results.
•
ERROR.
The ERROR response is followed by a display of the error description from the following list: Audit not available, audits turned off for site. Audits already turned on for this site. Audits already turned off for this site. SAP internal error.
NOTE The error messages listed are specific to a SITE. Devices listed within the SITE can also generate messages specific to the device. For a list of these messages, see device_audit. Only one audit is run at a time.
Security level
4
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
An operator at the OMC-R must rlogin to a site before an audit can be performed. This command is not allowed while in SYSGEN ON mode.
Format Syntax site_audit []
68P02901W23-S
3-507 Nov 2009
Examples
Chapter 3: Device/function related commands
Input parameters location Specifies the audit location: 0 or bsc
BSC
1 - 140
BTS
{27955A} pcu or pcu_0
PCU
control Audit status on
Resumes all audits at a specific site.
off
Suspends all audits at a specific site.
Examples Example 1 The following example executes audits for all devices at the BSC: site_audit 0 Where:
is: 0
location
System response Device: KSW Year: 1994
Device id: 0 0 0 Month: 11
Audit Type: SAFE Device: KSW Year: 1994
3-508
Result:
Hour: 1
Min: 22
Sec: 55
MSec: 10
AUDIT NOT SUPPORTED/AVAILABLE
Device id: 0 0 0, Month: 11
Audit Type: INT_LPBK Device: MSI
Day: 12
Day: 12 Result:
Hour: 1
Min: 22
Sec: 55
MSec: 30
AUDIT NOT SUPPORTED/AVAILABLE
Device id: 1 0 0
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Year: 1994
Month: 11
Audit Type: SAFE Device: DRI Year: 1994
Month: 11
Hour: 1
Min: 22
Sec: 55
MSec: 40
Min: 22
Sec: 55
MSec: 40
Min: 22
Sec:55
Min: 22
Sec: 55
MSec: 100
Min: 22
Sec: 55
MSec: 280
Min: 22
Sec: 55
MSec: 420
PASS
Day: 12 Result:
Hour: 1 PASS
Device id: 0 0 0
Year: 1994
Month: 11
Audit Type: SAFE Device: GCLK
Day: 12 Result:
Hour: 1
MSec: 100
PASS
Device id: 0 0 0
Year: 1994
Month: 11
Audit Type: SAFE Device: GPROC Year: 1994
Day: 12 Result:
Hour: 1 PASS
Device id: 0 0 0
Month: 11
Audit Type: SAFE Device: GPROC Year: 1994
Day: 12 Result:
Device id: 0 1 0
Audit Type: SAFE Device: DRI
Examples
Day: 12 Result:
Hour: 1 PASS
Device id: 1 0 0
Month: 11
Audit Type: SAFE
Day: 12 Result:
Hour: 1 ERROR
ERROR: Audit not available for this device.
Example 2 The following example resumes all of the audits at site 0: site_audit 0 on Where:
is: 0
location
on
control
System response COMMAND ACCEPTED
Example 3 The following example suspends all of the audits at site 0: site_audit 0 off Where:
68P02901W23-S
is: 0
location
off
control
3-509 Nov 2009
References
Chapter 3: Device/function related commands
System response COMMAND ACCEPTED
References Related information The KSW internal loopback test interrupts calls. It should be run only during periods of low traffic. Calls interrupted by this command must be re-established after the audits are completed.
Related commands cage_audit on page 3-58
chg_audit_sched on page 3-76
device_audit on page 3-210
query_audits on page 3-472
3-510
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
soft_reset
soft_reset ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The soft_reset command restarts the processes at one or more sites. An operator logged in to a BTS can restart only the local site. Only an operator logged in to the BSC can restart sites other than the local site. Security level
4
Supported by OMC-R GUI
Yes
Command type
B (operator actions required)
Prerequisites
Sites must be installed to enter this command. The command is abandoned if any response other than y or Y is received.
Operator actions
Respond to the verification prompt that is presented. This format is used to reset the local site only.
Format Syntax The following format is used to reset the local site: soft_reset The following format is used to restart processes at a specified PCU site: soft_reset pcu_n The following format is used to reset all of the sites from the BSC: soft_reset all The following format is used to reset one or more sites identified by site_id. Each site to be reset is separated by a space: soft_reset
NOTE After entering one of the commands, the operator is prompted with a warning and must enter ‘y’ or ‘Y’ (for yes) for the command to execute.
68P02901W23-S
3-511 Nov 2009
Format
Chapter 3: Device/function related commands
Input parameters pcu_n This parameter specifies a PCU for reset: Where:
is: {27955A} pcu or pcu_0
PCU site 0 (or the only PCU) at the BSC.
all This parameter specifies all of the sites at the BSC. site_id This parameter specifies the site to be reset. The range of values is 0 to 100.
NOTE Specifying 0 causes the BSC to reset.
Verification prompts When the command is entered to reset multiple sites, the system displays one of the following verification prompts: Are you sure (y=yes, n=no)? WARNING: Command will RESTART all processes at all BTS sites. WARNING: Command will RESTART all processes at the following sites: Are you sure (y=yes, n=no)? When the command is entered to reset a single site, the system displays the following verification prompt: WARNING: Command will RESTART all processes at site Are you sure (y=yes, n=no)? If y is entered and the command is accepted for a single site, the following warning message displays: COMMAND ACCEPTED: WARNING REBOOT SITE: site (site_id) will reboot now!!!
3-512
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Status displays One of the following statuses display for each requested site: Reboot status
Description
TIMEOUT
The request timed out while waiting to receive ACK message from this site.
OUT OF SERVICE
The site is OOS. The reset_site request is discarded.
NOT EQUIPPED
The site is not equipped. The reset_site request is discarded.
RESET REQUEST IN PROGRESS
The site_reset request is in progress.
Examples Example 1 In the following example, all of the sites are reset from the BSC: soft_reset all Where:
is: all
all sites in the BSS are specified.
System response WARNING: Command will RESTART all processes at all BTS sites. Are you sure (y=yes, n=no)? y 1
OUT OF SERVICE
2
RESET REQUEST IN PROGRESS
3
RESET REQUEST IN PROGRESS
4
NOT M-CELL
Example 2 In the following example sites 1, 4, and 9 are reset: soft_reset 1 4 9 Where:
is: 149
68P02901W23-S
sites to be reset.
3-513 Nov 2009
Examples
Chapter 3: Device/function related commands
System response WARNING: Command will RESTART all processes at the following sites: 1 4 9 Are you sure (y=yes, n=no)? y
3-514
1
RESET REQUEST IN PROGRESS
4
NOT EQUIPPED
9
TIMEOUT
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
state
state ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The state command displays the current status of devices or functions in the system, including when it last changed states. The length of time a device has been in its current state is also displayed. The state command can display specific devices or functions at one or all of the locations in the system based on operating states and identifiers. It can also display all the devices at all of the locations in the system by entering the state all or state all all command.
NOTE The state command does not display the IAS device. The following devices can be investigated with this command: ABSS
AXCDR
BSP
BTP
CAB
CAGE
CBL
CELL
CBUS
CIC
COMB
CSFP
DHP
DRI
EAS
{28351} ETH
GCLK
{28351} GDS
GPROC
KSW
LAN
MMS
MSI
MTL
OML
PATH
PBUS
PCHN
{28351} PSI
{28351} PPROC
RSL
RXCDR
SBUS
SITE
TBUS
TDM
XBL
The following GPRS only devices can be investigated with this command if the GPRS feature is unrestricted: DPROC
GBL
GDS
GSL
PCU
PSP
Security level
1
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
Not available on an RXCDR. This command is not available while in SYSGEN ON mode.
68P02901W23-S
3-515 Nov 2009
Format
Chapter 3: Device/function related commands
Format Syntax state [] [ ] [] [option2]
Input parameters location Specifies the location: 0 or bsc
BSC
1 - 140
BTS
all
Specifies all sites
{27955A} pcu or pcu_0
PCU
filter Optional text string used to select devices or functions in a specific state. Valid values are: busy
enabled-unlocked
ins
locked
oos
unlocked
NOTE For a CIC or range of CICs, filter is not available.
dev/func name Literal that uniquely identifies the device or function. all is entered to specify all devices and functions. In a GPRS system, * is used instead of all. dev/func id First device/function identifier. This definition varies with each device or function. This value is not valid when all is specified for the dev/func argument. dev/func id Second device/function identifier. This definition varies with each device or function. This value is not valid when all is specified for the dev/func argument. dev/func id Third device/function identifier. This definition varies with each device or function. This value is not valid when all is specified for the dev/func argument. option1 option2
3-516
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
The option parameter displays the configuration tags and the device subtypes for the specified devices or functions. There are two options: •
Enter tags to display the configuration tags. Configuration tags are described in OMC-R
Online Help, Network Operations. •
Enter subtypes to display the device subtypes.
The character string for the option can be entered in upper, lower, or mixed case letters. If both parameters are entered together, separate them with a space. When the tags option is entered and multiple devices or functions are specified, the displayed Related Function or Related Device column is replaced with the Config Tag (hex) column.
CIC syntax A form of syntax is available for each method of specifying a CIC. The following CIC syntax applies to local transcoding: state CIC state CIC TO
NOTE The following three state commands are valid only in BC mode.
state CIC state CIC state CIC TO
NOTE For remote transcoding BSC sites, the state command cannot be used for CICs when the BSC is operating in the dynamic allocation mode. The following CIC syntax applies to remote transcoding: state CIC state CIC TO
68P02901W23-S
3-517 Nov 2009
Format
Chapter 3: Device/function related commands
Input parameters location Specifies the location of the device: 0 or bsc
BSC
1 - 140
BTS
CIC Literal that uniquely identifies the CIC device. cic_num1 First CIC device number. cic_num2 Last CIC device number in a range.
NOTE mms_id1, mms_id2, timeslot1, group1, and group2 are valid only in BC mode.
mms_id1 First MMS identifier. mms_id2 Second MMS identifier, or last in a range if TO is used. timeslot1 First timeslot. timeslot2 Second timeslot, or last in a range if TO is used. group1 First group. group2 Second group. * Indicates all CICs on the MMSs specified in the timeslot, regardless of group.
NOTE For a CIC or range of CICs, neither filter nor option are available.
3-518
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Examples Example 1 In this example, the status of the CAB device is displayed: state 7 cab 0 Where:
is: 7
location
cab
dev/func name
0
dev/func ID
System response STATUS INFORMATION: Device: CAB 0 0 0 Administration state: UNLOCKED Operational State: BUSY Reason code: NO REASON Time of last transition: Fri Apr 8 00:01:39 1994 Related Device/Function: None END OF STATUS REPORT
Example 2 In this example, the status of all of the KSW devices at the BSC is displayed using wildcards and the tags option: state bsc ksw * * * tags Where:
68P02901W23-S
is: bsc
location
ksw
dev/func name
*
dev/func ID
*
dev/func ID
*
dev/func ID
tags
tags option
3-519 Nov 2009
Examples
Chapter 3: Device/function related commands
System response DEVICE STATUS INFORMATION FOR LOCATION 0: OPER
STATES: D:Disabled
ADMIN STATES: L:Locked
E:Enabled
B:Busy
U:Unlocked
E:Equipped
Config Tag (hex)
Device
State
Reason
dd/mm
------------
-----
------
----------------
None
14/01 10:36:57
KSW 0 0 0
B-U
S:Shutdown
Last Transition hh:mm:ss
--------00000004
Example 3 In this example, the status of all of the KSW devices at the BSC is displayed using wildcards: state bsc ksw * * * Where:
is: bsc
location
ksw
dev/func name
*
dev/func ID
*
dev/func ID
*
dev/func ID
System response DEVICE STATUS INFORMATION FOR LOCATION 0: OPER
STATES: D:Disabled
ADMIN STATES: L:Locked
E:Enabled
B:Busy
U:Unlocked
E:Equipped
S:Shutdown
Last Transition
3-520
Related
Device
State
Reason
dd/mm
---------
-----
---------------
---------------- ---------
hh:mm:ss Function
KSW 0 0 0
B-U
NO REASON
14/01
10:36:57 None
KSW 1 0 0
B-U
NO REASON
14/01
08:02:31 None
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 4 In this example, the status of all devices and functions at location 7 are displayed: state 7 Where:
is: 7
location
System response DEVICE STATUS INFORMATION FOR LOCATION 7: OPER
STATES:
ADMIN STATES:
D:Disabled
E:Enabled
B:Busy
L:Locked
U:Unlocked
E:Equipped
S:Shutdown
Last Transition
Related Function
Device
State Reason
dd/mm
----------
----- --------------
---------------- ---------
hh:mm:ss
CSFP 0 0 0
B-U
NO REASON
14/01
10:36:57
None
BTP 0 0 0
B-U
NO REASON
14/01
08:02:31
None
DRI 0 0 0
B-U
NO REASON
14/01
08:03:55
RTF 0 0 0
MSI 1 0 0
B-U
NO REASON
14/01
08:02:49
None
MMS 1 0 0
B-U
NO REASON
14/01
08:06:30
None
RSL 0 0 0
D-U
RAM LINK
16/01
08:46:52
None
TBUS 0 0 0
D-U
NO REASON
14/01
08:02:50
None
CAGE 0 0 0
B-U
NO REASON
14/01
08:02:21
None
CAB 0 0 0
B-U
NO REASON
14/01
08:02:23
None
SITE 0 0 0
B-U
NO REASON
14/01
08:04:51
None
PATH 0 0 0
D-U
NO REASON
14/01
08:46:51
None
PATH 0 0 0
B-U
NO REASON
14/01
08:55:18
None
... ... ...
FUNCTION STATUS INFORMATION FOR LOCATION 7: OPER STATES: E:Enabled
B:Busy
ADMIN STATES: E:Equipped Last Transition
Related
Function
State Reason
dd/mm
Device
---------
----- ---------------
---------------- ----------
RTF 0 0 0
B-E
14/01 08:03:43
68P02901W23-S
None
hh:mm:ss
GPROC 0 0 0
3-521 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 5 In this example, the status information for a single MSI, including device subtypes and configuration tags are displayed: state 0 msi 3 subtypes tags Where:
is: 0
location
msi
dev/func name
3
dev/func ID
subtypes
option1
tags
option2
System response STATUS INFORMATION: Device: MSI 3 0 0 (MSI) Administration state:
LOCKED
Operational state: ENABLED Reason code: NO REASON time of last transition:
SAT JAN 5 12:55:18 1980
Related Device/Function:
None
Config Tag (hex):
00000006
END OF STATUS REPORT
Example 6 In this example, the status information for all MSIs at site 0, including device subtypes, are displayed: state 0 msi * subtypes Where:
3-522
is: 0
location
msi
dev/func name
*
wildcard character for dev/func ID
subtypes
option1
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response DEVICE STATUS INFORMATION FOR LOCATION 0: OPER
STATES:
ADMIN STATES:
D:Disabled
E:Enabled
B:Busy
L:Locked
U:Unlocked
E:Equipped
S:Shutdown
Last Transition Device
State
Reason
dd/mm
Related
hh:mm:ss
Function
------------ ------ ------------------------ ---------------
--------
MSI 0 0 0
B-U
NO REASON
05/01
12:44:16
None
B-U
NO REASON
05/01
12:44:23
None
B-U
NO REASON
05/01
12:44:16
None
E-L
NO REASON
05/01
12:55:18
None
(MSI) MSI 1 0 0 (XCDR) MSI 2 0 0 (MSI) MSI 3 0 0 (MSI) END OF STATUS REPORT
Example 7 In this example, the status information for an MMS at site 2 is displayed; there is a failed HDSL modem: state 2 mms * * * Where:
68P02901W23-S
is: 2
location
mms
dev/func name
*
wildcard character for dev/func ID
*
option1
*
option2
3-523 Nov 2009
Examples
Chapter 3: Device/function related commands
System response DEVICE STATUS INFORMATION FOR LOCATION 2: OPER
STATES:
ADMIN STATES: Device
D:Disabled
E:Enabled
B:Busy
L:Locked
U:Unlocked
E:Equipped
State
Reason
S:Shutdown
Last Transition
Related
dd/mm
Function
hh:mm:ss
----------- ------ -------------------------- ---------------- -------MMS 0 0 0
D-U
HDSL Modem bad or missing
13/01
17:18:03
None
MMS 0 1 0
B-U
No Reason
13/01
17:18:03
None
END OF STATUS REPORT
Example 8 This command displays the status of the CAGE device at PCU site 0: state pcu_0 cage 0 Where:
is: pcu_0
location
cage
dev/func name
0
CAGE identifier
System response STATUS INFORMATION: Device: CAGE 0 0 0 Administration state: UNLOCKED Operational state: BUSY Reason code: NO REASON Time of last transition: Tue Jan 3 05:00:30
1999
Related Device/Function: None END OF STATUS REPORT
3-524
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
Example 9 This command displays the status of PCU site 1 at BSC 0: state 0 pcu 1 Where:
is: 0
location
pcu
device name
1
PCU identifier
System response STATUS INFORMATION: Device: PCU 1 0 0 Administration state: UNLOCKED Operational state: BUSY Reason code: NO REASON Time of last transition: Sun Jan 6 01:37:49
2002
Related device/Function: None END OF STATUS REPORT
Example 10 Displays the status of all MSIs at PCU site 0. state PCU_0 MSI * Where:
is: PCU_0
location
MSI
device name
*
all MSIs
System response DEVICE STATUS INFORMATION FOR LOCATION PCU site 0: OPER STATES:
D:Disabled
E:Enabled
B:Busy
ADMIN STATES:
L:Locked
U:Unlocked
E:Equipped
Device
State
S:Shutdown
Last Transition
Related
Reason
dd/mm
hh:mm:ss
Function
MSI 1 0 0
B-U
NO REASON
03/01
05:00:30
None
MSI 2 0 0
B-U
NO REASON
03/01
06:00:00
None
END OF STATUS REPORT
68P02901W23-S
3-525 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 11 {28351} Displays the status of all DPROC devices. state PCU DPROC * Where:
is: PCU
location
DPROC
device name
*
all DPROCs
System response DEVICE STATUS INFORMATION FOR LOCATION 0: OPER
STATES:
ADMIN STATES:
D:Disabled
E:Enabled
B:Busy
L:Locked
U:Unlocked
E:Equipped
S:Shutdown
Last Transition Related Device -------------
State
Reason
dd/mm
hh:mm:ss
Function
-----
---------
-----
--------
--------
DPROC
1 0 0
B-U
NO REASON
08/01
06:59:17
None
DPROC
2 0 0
B-U
NO REASON
08/01
07:00:04
None
DPROC
3 0 0
B-U
NO REASON
08/01
07:00:04
None
END OF STATUS REPORT
Example 11 {34321} Displays the status information of the cage device. state bsc cage 1 Where:
3-526
is: bsc
location
cage
device name
1
CAGE identifier
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
System Response STATUS INFORMATION: Device: CAGE 1 0 0 Administration state: UNLOCKED Operational state: BUSY Reason code: NO REASON Time of last transition: Wed May 7 16:42:03 1980 Related Device/Function: None END OF STATUS REPORT
References Transference of device status When a GPROC card is equipped as a DHP, BSP, or BTP, all references to the state of the GPROC card should use the equipped name (such as DHP, BSP, or BTP). Table 3-33 lists the operational states.
Table 3-33
Operational states
Operational states
Description
Disabled
FM has found the device unserviceable and has taken it out of service.
Enabled
FM has made the device available for use but it is not carrying traffic.
Busy
Device is available for use and is carrying traffic.
Table 3-34 lists the administrative states.
Table 3-34
Administrative states
Admin state
Description
Locked
The operator has taken the device out of service.
Unlocked
The operator has made the device available for service.
Equipped
The device exists in the system.
Table 3-35 lists the device states.
68P02901W23-S
3-527 Nov 2009
References
Chapter 3: Device/function related commands
Table 3-35
Device states
Device state
Description
Not Equipped
The device does not exist in the system.
Disabled Locked
FM and the operator find the device unserviceable.
Enabled Locked
FM finds the device serviceable but the operator does not want it in service.
Disabled Unlocked
FM finds the device unserviceable but the operator wants it in service. The system can periodically audit the device (the operator can force audits) to determine if the device is UNLOCKED.
Enabled Unlocked
FM finds the device serviceable and the operator wants it in service.
Busy Unlocked
The device is in use.
Shutting Down
The device is between the LOCKED and UNLOCKED states. The system is waiting until all processes using the device have terminated before putting the device into the LOCKED state.
NOTE The remaining states LOCKED and NOT EQUIPPED in Table 3-35 cannot exist with any operational component. Table 3-36 lists the reason codes.
3-528
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Table 3-36
References
Reason codes
Reason Codes
Value
Explanation
Applicable to any device NO_REASON
0
No reason.
NO_INIT
1
The device is not initialized.
PARENT_OOS
2
The parent device is out of service.
FAIL_ACT
3
The device failed to activate.
BAD_DB_CONFIG
4
The device is incorrectly configured in the database.
NO_GPROC
5
There is no available GPROC to assign the device.
INHIBITED
6
The device is inhibited from being used.
WAIT
7
The device is waiting for an event.
FREED_FUNCTION
8
The function has been removed from the device.
Indicate progress made by BSC initializing a remote site NO_LINK
9
The RSL link to the BTS has not been established.
ROM_TO_RAM
10
The default link to BTS is active. BTS is in ROM.
RAM_LINK
11
The BTS jumped to RAM without problems.
ROM_LINK
12
The site informs RSL it is a ROM link.
14
Indicates which transceiver is controlling a particular combiner.
Applicable to combiners COMBINER_CONTROLLER
Related commands disp_equipment on page 3-283
equip on page 3-403
unlock_device on page 3-581
shutdown_device on page 3-502
68P02901W23-S
lock_device on page 3-429
3-529 Nov 2009
status_mode
Chapter 3: Device/function related commands
status_mode ■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
■
Description The status_mode command turns the state change notification on or off for the devices at a site that can be equipped. When the status mode is turned on, a notification containing both the old and the new status for a device displays immediately when a state change occurs. The status notification occurs only at the local MMI at which the command was invoked. Only the BSC can display status notification for remote sites. If the status mode is turned off, no notification is provided when a device experiences a state change. This command permits efficient adjustment of the current system configuration where necessary. If no mode is entered, the current alarm status mode displays. If the status_mode command is entered, the current status is displayed. One of the following status messages is displayed: •
Status notification is ON.
•
Status notification is OFF.
•
Site unequipped.
•
Site unavailable.
•
Status notification is already ON.
•
Status notification is already OFF.
Multiple sites are disabled using the same command line by entering the site IDs separated by a space. All sites can be disabled by entering all for the location.
NOTE Location all is only allowed at the BSC.
3-530
Security level
3
Supported by OMC-R GUI
Yes
Command type
A (no operator actions)
Prerequisites
To display the status mode for the PCU, the GPRS feature must be unrestricted.
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Format
Format Syntax status_mode [ ...] []
Input parameters location Specifies the location of the device: 0 or bsc
BSC
1 - 140
BTS
{27955A} pcu or pcu_0
PCU
all
All sites
mode Specifies the state change notification condition: on
state change notification on
off
state change notification off
Examples Example 1 This example turns on the CA device state-change notification at the BSC. When a device is locked, note the output due to the state change that has occurred. status_mode 0 on Where:
is: 0
location
on
mode
System response SITE
STATUS
----
----------------
0
68P02901W23-S
Status notification turned ON
3-531 Nov 2009
Examples
Chapter 3: Device/function related commands
Example 2 This example shows the command string required to display the status mode for an entire BSC. status_mode all Where:
is: all
all sites in the BSC.
System response Site
Status
----
----------------
0
Status mode is OFF
4
Status mode is ON
5
Status mode is ON
Example 3 This example turns off the CA device state change notification at location 6. status_mode 6 off Where:
is: 6
location
off
mode
System response SITE
STATUS
----
----------------
0
3-532
Status notification turned OFF
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
References
Example 4 This example shows the effect of the status mode being turned on when the state of a device changes. In this example, the msi 1 0 0 is being locked. lock_device bsc msi 1 0 0 Where:
is: bsc
location
msi
device_name
1
device_id1
0
device_id2
0
device_id3
System response * STATUS NOTIFICATION -- Tag(hex): * ()
prompt is presented. If a command is not entered, the system resets.
Initial SYSGEN mode The system can be placed in the initial SYSGEN mode by placing the system in the SYSGEN ON mode after the database has been deleted using the clear_database command. Security level
4
Supported by OMC-R GUI
No
Command type
B (operator actions required)
Prerequisites
None
Operator actions
Reset the system to change the SYSGEN mode after entering this command.
Format Syntax sysgen_mode []
Input parameter value Specifies the status of SYSGEN: on
Places the system in the SYSGEN ON mode.
off
Places the system in the SYSGEN OFF mode.
68P02901W23-S
3-541 Nov 2009
Examples
Chapter 3: Device/function related commands
Examples Example 1 In this example, the system is placed in the SYSGEN OFF mode of operation: sysgen_mode off Where:
is: off
the SYSGEN mode in which the system is placed after the next reinitialization.
System response ******* VERIFYING DATABASE BEFORE COMPLETING SYSGEN ******* Frequency hopping verification in progress. SITE 0 Verification. DB Verification passed. COMMAND ACCEPTED.
Example 2 In this example, the system is placed in the SYSGEN ON mode of operation: sysgen_mode on Where:
is: on
the SYSGEN mode in which the system is placed after the next reinitialization.
System response COMMAND ACCEPTED: You must re-init the site to start SYSGEN
Example 3 In the following example, the current SYSGEN mode is displayed and the mode into which the system is placed after the next restart. sysgen_mode
3-542
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Examples
System response Current Sysgen mode: ON Sysgen mode upon next restart: OFF
Example 4 This example attempts to turn off SYSGEN mode with GSM Half Rate enabled but with CIC validation disabled for an AXCDR. sysgen_mode off
System response WARNING: AXCDR CIC validation must be enabled for AMR or GSM HR.
Example 5 In this example SYSGEN mode is turned off when PCU 0 does not have enough GDS resources, and PCU 1 does not have enough PMC resources for res_gprs_pdchs and switch_gprs_pdchs. sysgen_mode off
System response ********** VERIFYING DATABASE BEFORE COMPLETING SYSGEN ********** PCU 0: ----------------------------------------------------------------------WARNING: Insufficient GDS resources available for all PDTCHs on the PCU. PCU 1: ----------------------------------------------------------------------WARNING: Insufficient PMC resources available for all PDTCHs on the PCU. Sysgen OFF warnings were detected. If accepted, this database may cause some loss of service. Still leave sysgen mode? Are you sure (y=yes,n=no)? y
Example 6 In this example SYSGEN mode is turned off when PCU 0 does not have enough GDS resources and PCU 1 does not have enough PMC resources for res_ts_less_one_carrier and sw_ts_less_one_carrier. sysgen_mode off
68P02901W23-S
3-543 Nov 2009
Database errors
Chapter 3: Device/function related commands
System response ********** VERIFYING DATABASE BEFORE COMPLETING SYSGEN ********** PCU 0: ----------------------------------------------------------------------WARNING: Insufficient GDS resources avail for all PDs on the PCU (less one carrier). PCU 1: ----------------------------------------------------------------------WARNING: Insufficient PMC resources avail for all PDs on the PCU (less one carrier). Sysgen OFF warnings were detected. If accepted, this database may cause some loss of service. Still leave sysgen mode? Are you sure (y=yes,n=no)? y
Database errors A database error causes the sysgen_mode off command to be rejected and a database is not created; an error message displays. All error messages are preceded with the DB VERIFY ERROR: string.
General database errors The BSC MUST have an OMF equipped if bsc_type is 2. bsc_type MUST be zero for site type RXCDR. At least one LCF MUST be equipped at site 0 when bsc_type is not 0. At least one LCF MUST have max_mtls greater than zero for this site type. The BSC MUST have at least one BSP equipped. Site does note have a BTP equipped. Site does not have a GCLK equipped. RRSM Timer,8 value at site must be less than SSM Timer,10. No slots available on BSP. No BSP found in CM database. Requested bsc_type not supported. No slots available on LCF. No LCF found in CM database. There is no default RSL equipped to BTS site on any PATH. INVALID DATA IN BIN : decision_1_dl_rxqual_av_h error in cell id
3-544
68P02901W23-S Nov 2009
Technical Description: BSS Command Reference
Database errors
INVALID DATA IN BIN : decision_1_dl_rxlev_av_h error in cell id INVALID DATA IN BIN : decision_1_dl_rxlev_av_ih in cell id INVALID DATA IN BIN : decision_1_p_bgt_rxlev_av_h in cell id (rxlev_dl_ho) INVALID DATA IN BIN : decision_1_p_bgt_rxlev_av_h in cell id (surround_cell) INVALID DATA IN BIN : decision_1_dl_rxqual_av_p in cell id INVALID DATA IN BIN : decision_1_dl_rxlev_av_p in cell id INVALID DATA IN BIN : decision_1_ncell_rxlev_av_h_calc in cell id INVALID DATA IN BIN : decision_1_tim_adv_av_alg in cell id INVALID DATA IN BIN : decision_1_ul_rxqual_av_h in cell id INVALID DATA IN BIN : decision_1_ul_rxlev_av_h in cell id INVALID DATA IN BIN : decision_1_ul_rxlev_av_ih in cell id INVALID DATA IN BIN : decision_1_ul_rxqual_av_p in cell id INVALID DATA IN BIN : decision_1_ul_rxlev_av_p in cell id
General hopping errors Can't have baseband and synthesizer hopping_support values at same site. BCCH frequency cannot have BCCH timeslots which hop. cell =
frequency =
timeslot =
Too many frequencies were defined for the frequency range Unable to format cell-channel description with this many frequencies Cell: defined>
Number Freqs defined:
