BSPLCML
Uploaded by
FlorencioPautangBSPLCML
Uploaded by
FlorencioPautangGSM/EDGE RAN - BR line
Reference
Base transceiver station equipment
BS-4x / 82 II / 240 / 241 / 240XL commands
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED
TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY
OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION
IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2009. All rights reserved
Important Notice on Product Safety
Elevated voltages are inevitably present at specific points in this electrical equipment.
Some of the parts may also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal
injury or in property damage.
Therefore, only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected
has to comply with the applicable safety standards.
The same text in German:
Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Spannung. Einige Teile knnen auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverletzungen und Sachschden fhren.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die
Anlagen installiert und wartet.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene
Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.
Id:0900d80580627b1d
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Table of Contents
This document has 762 pages.
Reason for update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1
1.1
1.1.1
1.1.2
1.1.3
1.1.4
1.2
1.2.1
1.2.2
1.3
1.3.1
1.3.2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure of the manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Structure of the commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ranges for the relative number of the BTSE objects. . . . . . . . . . . . . . .
Command layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Graphical user interface (GUI) representation of the LMT Evolution . . .
Start LMT Evolution window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LMT Evolution windows for GET, CREATE, SET, ..., commands . . . . .
Command tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
BS240, BS241, BS240XL, BS40, BS41, BS40II and BS82II main tree
Alphabetical list of commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Objects and commands in alphabetical order . . . . . . . . . . . . . . . . . . . . 48
A50016-G5100-B333-04-7619
21
21
22
23
23
26
28
28
31
34
34
35
ACDCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CREATE ACDCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DELETE ACDCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GET ACDCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GETTEST ACDCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOCK ACDCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PERFTEST ACDCP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STOPTEST ACDCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNLOCK ACDCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
49
49
51
52
53
55
57
60
62
ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CREATE ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DELETE ACT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GET ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GETTEST ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOCK ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PERFTEST ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STOPTEST ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNLOCK ACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
64
66
67
69
70
72
76
77
BATTERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CREATE BATTERY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DELETE BATTERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GET BATTERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GETTEST BATTERY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOCK BATTERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PERFTEST BATTERY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STOPTEST BATTERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNLOCK BATTERY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
79
79
81
82
84
86
87
91
92
Id:0900d80580627b1d
BS-4x / 82 II / 240 / 241 / 240XL commands
BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
CREATE BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
DELETE BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
GET BCOM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
GETRELATIONSHIP BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
GETTEST BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
GETWIRINGRX BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
GETWIRINGTX BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
LOCK BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
PERFTEST BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
SET BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
SETWIRINGRX BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
SETWIRINGTX BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
STOPTEST BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
UNLOCK BCOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
BPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
CREATE BPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
DELETE BPORT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
GET BPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
LOCK BPORT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
SET BPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
UNLOCK BPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
GET BTS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
GET BTS TIMER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
BTSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
DELETE BTSEP DBFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
FORMAT BTSEP FLASH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
GET BTSEP NOSWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
GET BTSEP SWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
GETACTIVEALARMS BTSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
PERFTEST BTSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
PING BTSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
SET BTSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
STOPTEST BTSEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
BTSETEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
GET BTSETEST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
BTSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
ACTIVATE BTSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
ACTIVATE_DELAYED BTSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
CONNBSC BTSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
DISCBSC BTSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
FWUPGRADE BTSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
GET BTSM NOSWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
GET BTSM OVERLOAD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Id:0900d80580627b1d
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
GET BTSM SWL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOCKREQUEST BTSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET BTSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHUTDOWN BTSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNLOCKREQUEST BTSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
173
174
175
177
178
CESPW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CREATE CESPW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DELETE CESPW. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GET CESPW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOCK CESPW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET CESPW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNLOCK CESPW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
180
180
182
183
185
187
188
CESTUNNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CREATE CESTUNNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DELETE CESTUNNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GET CESTUNNEL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOCK CESTUNNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET CESTUNNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNLOCK CESTUNNEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
190
190
191
192
194
195
196
CHAN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
GET CHAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
A50016-G5100-B333-04-7619
COBA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CREATE COBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DELETE COBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GET COBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GETRELATIONSHIP COBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GETTEST COBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOCK COBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PERFTEST COBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET COBA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STOPTEST COBA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SWITCH COBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNLOCK COBA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
200
200
202
203
205
206
208
209
213
214
216
217
COBAETHINTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GET COBAETHINTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOCK COBAETHINTF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET COBAETHINTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNLOCK COBAETHINTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
219
219
220
221
222
COSA. . . . . . . . . . .
CREATE COSA . . .
DELETE COSA . . .
GET COSA . . . . . .
GETTEST COSA . .
LOCK COSA . . . . .
PERFTEST COSA .
224
224
225
227
228
230
232
.......................................
.......................................
.......................................
.......................................
.......................................
.......................................
.......................................
Id:0900d80580627b1d
BS-4x / 82 II / 240 / 241 / 240XL commands
STOPTEST COSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
UNLOCK COSA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
CU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
CREATE CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
DELETE CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
GET CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
GET CU FWID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
GET CU WIRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
GETTEST CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
LOCK CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
PERFTEST CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
SET CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
STOPTEST CU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
UNLOCK CU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
DIDCTMA . . . . . . . . . .
CREATE DIDCTMA . .
DELETE DIDCTMA. . .
GET DIDCTMA . . . . . .
GETTEST DIDCTMA .
LOCK DIDCTMA. . . . .
PERFTEST DIDCTMA
STOPTEST DIDCTMA
UNLOCK DIDCTMA . .
......
......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
......
......
. . . . . 258
. . . . . 258
. . . . . 259
. . . . . 261
. . . . . 262
. . . . . 264
. . . . . 266
. . . . . 270
. . . . . 271
DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
CREATE DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
DELETE DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
GET DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
GETTEST DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
LOCK DILNA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
PERFTEST DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
SET DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
STOPTEST DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
UNLOCK DILNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
DUAMCO . . . . . . . . . .
DELETE DUAMCO . . .
GET DUAMCO . . . . . .
GETTEST DUAMCO .
LOCK DUAMCO . . . . .
PERFTEST DUAMCO
STOPTEST DUAMCO
UNLOCK DUAMCO . .
......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
......
. . . . . 290
. . . . . 290
. . . . . 291
. . . . . 292
. . . . . 293
. . . . . 294
. . . . . 295
. . . . . 296
DUDCTMA . . . . . . . . .
CREATE DUDCTMA .
DELETE DUDCTMA . .
GET DUDCTMA . . . . .
......
......
......
......
.......
.......
.......
.......
......
......
......
......
.......
.......
.......
.......
......
......
......
......
. . . . . 298
. . . . . 298
. . . . . 300
. . . . . 301
Id:0900d80580627b1d
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
GETTEST DUDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOCK DUDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PERFTEST DUDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STOPTEST DUDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNLOCK DUDCTMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
302
304
306
310
311
DULNA. . . . . . . . . . . . . . . .
CREATE DULNA . . . . . . . .
DELETE DULNA . . . . . . . .
GET DULNA . . . . . . . . . . .
GETTEST DULNA . . . . . . .
LOCK DULNA . . . . . . . . . .
PERFTEST DULNA . . . . . .
SET DULNA. . . . . . . . . . . .
STOPTEST DULNA. . . . . .
UNLOCK DULNA. . . . . . . .
.................................
.................................
.................................
.................................
.................................
.................................
.................................
.................................
.................................
.................................
313
313
315
317
319
321
322
326
328
329
DUVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CREATE DUVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DELETE DUVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GET DUVSWR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GETTEST DUVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOCK DUVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PERFTEST DUVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET DUVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STOPTEST DUVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNLOCK DUVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
331
331
333
335
336
338
340
344
345
346
ENVABTSE . . . . . . . . . . . .
CREATE ENVABTSE . . . .
DELETE ENVABTSE. . . . .
GET ENVABTSE . . . . . . . .
LOCK ENVABTSE . . . . . . .
SET ENVABTSE . . . . . . . .
UNLOCK ENVABTSE . . . .
.............
.............
.............
.............
.............
.............
.............
349
349
353
354
356
358
359
.......................................
.......................................
.......................................
.......................................
.......................................
.......................................
.......................................
361
361
362
362
364
365
366
ETHCON . . . . . . . .
CREATE ETHCON
DELETE ETHCON.
GET ETHCON . . . .
LOCK ETHCON . . .
SET ETHCON . . . .
UNLOCK ETHCON
ETHPORT . . . . . . . . . . . . .
CREATE ETHPORT . . . . .
DELETE ETHPORT. . . . . .
GET ETHPORT . . . . . . . . .
LOCK ETHPORT . . . . . . . .
SET ETHPORT . . . . . . . . .
A50016-G5100-B333-04-7619
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
.................................
.................................
.................................
.................................
.................................
.................................
Id:0900d80580627b1d
368
368
369
370
372
373
BS-4x / 82 II / 240 / 241 / 240XL commands
UNLOCK ETHPORT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
F6DCTMA . . . . . . . . . . . . . . . .
CREATE F6DCTMA . . . . . . . .
DELETE F6DCTMA . . . . . . . .
GET F6DCTMA. . . . . . . . . . . .
GETTEST F6DCTMA . . . . . . .
LOCK F6DCTMA . . . . . . . . . .
PERFTEST F6DCTMA . . . . . .
STOPTEST F6DCTMA . . . . . .
UNLOCK F6DCTMA . . . . . . . .
.......
.......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
......
......
F6LNA . . . . . . . . . . . . .
CREATE F6LNA . . . . .
DELETE F6LNA . . . . .
GET F6LNA . . . . . . . .
GETTEST F6LNA . . . .
LOCK F6LNA . . . . . . .
PERFTEST F6LNA . . .
SET F6LNA. . . . . . . . .
STOPTEST F6LNA. . .
UNLOCK F6LNA. . . . .
......
......
......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
......
......
......
. . . . . . . . . . . . . . . . . . 387
. . . . . . . . . . . . . . . . . . 387
. . . . . . . . . . . . . . . . . . 389
. . . . . . . . . . . . . . . . . . 390
. . . . . . . . . . . . . . . . . . 392
. . . . . . . . . . . . . . . . . . 393
. . . . . . . . . . . . . . . . . . 394
. . . . . . . . . . . . . . . . . . 396
. . . . . . . . . . . . . . . . . . 398
. . . . . . . . . . . . . . . . . . 399
F6TNFP . . . . . . . . . . .
CREATE F6TNFP. . . .
DELETE F6TNFP . . . .
GET F6TNFP . . . . . . .
GETTEST F6TNFP. . .
LOCK F6TNFP . . . . . .
PERFTEST F6TNFP. .
STOPTEST F6TNFP .
UNLOCK F6TNFP . . .
......
......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
......
......
. . . . . 376
. . . . . 376
. . . . . 377
. . . . . 379
. . . . . 380
. . . . . 381
. . . . . 382
. . . . . 384
. . . . . 385
. . . . . 401
. . . . . 401
. . . . . 402
. . . . . 403
. . . . . 405
. . . . . 406
. . . . . 407
. . . . . 409
. . . . . 410
F6VSWRP. . . . . . . . . . . . . . . .
CREATE F6VSWRP . . . . . . . .
DELETE F6VSWRP . . . . . . . .
GET F6VSWRP . . . . . . . . . . .
GETTEST F6VSWRP . . . . . . .
LOCK F6VSWRP . . . . . . . . . .
PERFTEST F6VSWRP . . . . . .
SET F6VSWRP. . . . . . . . . . . .
STOPTEST F6VSWRP. . . . . .
UNLOCK F6VSWRP. . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
FANP . . . . . . . . . . . . .
CREATE FANP . . . . . .
DELETE FANP . . . . . .
GET FANP . . . . . . . . .
GETTEST FANP. . . . .
LOCK FANP . . . . . . . .
.......
.......
.......
.......
.......
.......
Id:0900d80580627b1d
......
......
......
......
......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
. . . . . 424
. . . . . 424
. . . . . 426
. . . . . 427
. . . . . 429
. . . . . 430
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
PERFTEST FANP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
STOPTEST FANP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
UNLOCK FANP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
FCUMAIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CREATE FCUMAIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DELETE FCUMAIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GET FCUMAIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GET FCUMAIN FWID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GET FCUMAIN WIRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GETTEST FCUMAIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOCK FCUMAIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PERFTEST FCUMAIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET FCUMAIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STOPTEST FCUMAIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNLOCK FCUMAIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
439
439
441
443
444
445
446
448
450
454
455
456
FCUTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CREATE FCUTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DELETE FCUTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GET FCUTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GETTEST FCUTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOCK FCUTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PERFTEST FCUTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SET FCUTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STOPTEST FCUTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNLOCK FCUTR. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
458
458
460
461
463
464
466
470
471
472
FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CREATE FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DELETE FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GET FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GETTEST FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOCK FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PERFTEST FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STOPTEST FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNLOCK FTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
474
474
476
477
479
480
482
486
487
FVSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CREATE FVSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DELETE FVSWRP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GET FVSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GETTEST FVSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LOCK FVSWRP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PERFTEST FVSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
STOPTEST FVSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
UNLOCK FVSWRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
489
489
491
492
493
495
497
501
502
LAPDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
CREATE LAPDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
A50016-G5100-B333-04-7619
Id:0900d80580627b1d
BS-4x / 82 II / 240 / 241 / 240XL commands
DELETE LAPDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
GET LAPDLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
RACK . . . . . . . . . . . . .
CREATE RACK . . . . .
DELETE RACK . . . . . .
GET RACK . . . . . . . . .
LOCK RACK . . . . . . . .
SET RACK . . . . . . . . .
UNLOCK RACK . . . . .
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
. . . . . 509
. . . . . 509
. . . . . 511
. . . . . 512
. . . . . 514
. . . . . 515
. . . . . 516
REMINV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
DNLIDFD REMINV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
UPLLIDF REMINV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
SOFTWARE-MANAGEMENT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
DNLALLEXE SOFTWARE-MANAGEMENT. . . . . . . . . . . . . . . . . . . . . 522
UPLBTSLOG SOFTWARE-MANAGEMENT . . . . . . . . . . . . . . . . . . . . 523
SYNCBTSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
GET SYNCBTSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
GETTEST SYNCBTSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
LOCK SYNCBTSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
PERFTEST SYNCBTSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
SET SYNCBTSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
STOPTEST SYNCBTSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
UNLOCK SYNCBTSE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
CREATE TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
DELETE TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
GET TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
GET TMA PRODUCTINFO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
GETTEST TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
LOCK TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
PERFTEST TMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
STOPTEST TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
UNLOCK TMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
TRX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
GET TRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
GETRELATIONSHIP TRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
XCONNECT . . . . . . . .
CREATE XCONNECT
DELETE XCONNECT.
GET XCONNECT . . . .
LOCK XCONNECT . . .
SET XCONNECT . . . .
UNLOCK XCONNECT
3
10
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
. . . . . 560
. . . . . 560
. . . . . 562
. . . . . 563
. . . . . 567
. . . . . 569
. . . . . 570
Parameters/attributes in alphabetical order . . . . . . . . . . . . . . . . . . . . . 572
Id:0900d80580627b1d
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
A50016-G5100-B333-04-7619
a. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ABISCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ABISLKSAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ABISTIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ACBQPFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ACBQPMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ACEFLFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ACFERMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ACLNKTYP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ACMAXEFLDMA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ACMINEFLDMA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ACONN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ACPER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ACTVINC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ALIGCOBA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ALRMCLET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ALRMCOUNTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ALRMPERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ALRMSEVXXX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ALRMT1/2/3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AMRLKAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AMRLKATWFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ANT<x>CELLNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ANT<x>SCNRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ANT<x>WDRX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ANT<x>WDTX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ANTB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ANTHOPHW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ANTHOPMOD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ANTHOPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ANTHOPST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ANTMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ANTSN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ARFACCHACMDF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ASCICIPH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ASEV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ASTRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ASUBLKSAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AVS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
573
573
573
573
574
575
575
575
576
576
577
577
578
578
579
579
579
580
581
581
582
583
584
584
585
586
589
590
591
591
592
592
592
593
593
594
594
595
595
596
596
b. . . . . . . . . . . . . . .
BATTCAP . . . . . . .
BCCHFREQ. . . . . .
BCOMTYPE. . . . . .
BCPBL . . . . . . . . . .
BERT . . . . . . . . . . .
598
598
598
599
600
600
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
Id:0900d80580627b1d
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
11
BS-4x / 82 II / 240 / 241 / 240XL commands
BMWD<x>. . . .
BND<x> . . . . .
BSIC . . . . . . . .
BSWVER . . . .
BTSID . . . . . . .
BTSISHOP . . .
BURNOFFS . .
......
......
......
......
......
......
......
......
......
......
......
......
......
......
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
c . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
CCPBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
CELLNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
CELLTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
CHIDT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
CHTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
CLKACC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
COMBMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
CUCONF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
CUWIRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
d .................
DESTDIR . . . . . . . . . .
DLTESTFREQ . . . . . .
DMACFHSYID . . . . . .
DMCFWID. . . . . . . . . .
DTMHOMTIMER. . . . .
DYNTRACGRAN . . . .
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
. . . . . . . . . . . . . . . . . . . . . . . . 612
. . . . . . . . . . . . . . . . . . . . . . . . 612
. . . . . . . . . . . . . . . . . . . . . . . . 612
. . . . . . . . . . . . . . . . . . . . . . . . 612
. . . . . . . . . . . . . . . . . . . . . . . . 613
. . . . . . . . . . . . . . . . . . . . . . . . 613
. . . . . . . . . . . . . . . . . . . . . . . . 613
e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
EAC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
EANTHOP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
EAUTONEG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615
EAUTOREC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
EEOTD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
EEXCDIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
EFCUSUP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
EFLWCTRL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
EINTSITSYN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
EMT1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
EMT2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
ENTRIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
EQUPOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
ERFACCHALPDMF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
ERFACCHCMDF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
ERSACCHDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
ERSACCHUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
ETOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
ETXDIVTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
EVTYP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
EXCDIST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
12
Id:0900d80580627b1d
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
EXTMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
f ......................................................
F6FWID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FACCHQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FACHBT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FBAND. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FCUMAINWIRING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FCUMODE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FILEFWV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FILEID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FILESWV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FILETYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FPGAFWVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FRANOFFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FWVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
640
640
640
640
641
641
642
643
643
644
645
646
646
647
647
g. . . . . . . . . . . . . . .
GN<x> . . . . . . . . . .
GNA . . . . . . . . . . . .
GNADB . . . . . . . . .
GNR . . . . . . . . . . . .
GSMTIME . . . . . . .
GTWADRV4 . . . . .
648
648
648
649
650
650
651
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
HOPMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
HSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
A50016-G5100-B333-04-7619
i ......................................................
INSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
INSID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
INTAVEPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
INTCLASS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
INTINF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
INTLVBND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IPADR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
653
653
653
653
654
654
654
655
l ......................................................
L1CTRLTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
L1PT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
L1RAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAPDCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAPDOVLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAPDOVLTH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LAPDOVLTRXL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LCONF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LIMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
LMTLSESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
656
656
656
657
657
658
659
660
660
661
662
Id:0900d80580627b1d
13
BS-4x / 82 II / 240 / 241 / 240XL commands
LMTLTIME . . .
LMTUAL . . . . .
LMTUNAME . .
LNAMDB . . . . .
LNAMODE . . .
LNAPRED . . . .
LOCALADDR .
LOCLUDP . . . .
LOCNAME . . .
LOSPKTTH . . .
LPDLMSAT . . .
LRU. . . . . . . . .
LSIND . . . . . . .
......
......
......
......
......
......
......
......
......
......
......
......
......
......
......
......
......
......
......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
.......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
......
......
......
......
......
......
......
. . . . . 662
. . . . . 662
. . . . . 663
. . . . . 663
. . . . . 664
. . . . . 664
. . . . . 667
. . . . . 667
. . . . . 667
. . . . . 668
. . . . . 668
. . . . . 669
. . . . . 669
m . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
MACADDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
MAIO. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
MAXGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
MAXPDV. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
MINGN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
MOBALLOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
MOEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
MONPRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
MORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
MPHERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
MPTSLXX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
MRSYNCT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
MSTXPMAX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
MSTXPMAXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
MTLT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
MTYP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
n ...........
NEPTTREP. . .
NTWTYPC . . .
NTWTYPE . . .
NY1 . . . . . . . . .
NY2 . . . . . . . . .
......
......
......
......
......
......
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
o ...........
OMLAPDRT . .
OST. . . . . . . . .
OUTPUTPR . .
OVERWRITE .
OVPTINS . . . .
......
......
......
......
......
......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
.......
.......
.......
.......
.......
.......
......
......
......
......
......
......
. . . . . 686
. . . . . 686
. . . . . 686
. . . . . 687
. . . . . 687
. . . . . 687
p . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
PCCCHLDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
PEERADDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
14
Id:0900d80580627b1d
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
A50016-G5100-B333-04-7619
PEERUDPPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PKTLAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PNGF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PNGPKT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PNOFACCH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRDINF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRDIRECT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PSTAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PUSG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PWNAME. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PWROUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PWRRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
689
690
690
691
691
691
692
692
693
693
694
694
695
r......................................................
RACHBT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RACHLAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RADIOMG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RADIOMR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RELEQUIPOBJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RELFUNCOBJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
REPTYP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RFRSINDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSACCHRXLDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSACCHRXLUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSACCHTODL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RSACCHTOUL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RXBMAXF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RXBMINF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RXDIVSV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RXLEVADJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RXLEVADJN1D1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RXSIGLEVADJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RXSIGLEVADJC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RXSWCURSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
696
696
696
696
697
697
698
700
701
701
701
702
702
702
703
703
704
704
704
705
705
s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SALUNAME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SBPRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SBSCSLCV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCELLNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCLPRIOLST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SFPSERID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SHLAPDIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SLOTNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SRCDIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SRCPATH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
706
706
706
706
707
708
708
710
710
711
711
712
Id:0900d80580627b1d
15
BS-4x / 82 II / 240 / 241 / 240XL commands
STATIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
STDBYST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 712
SUBUNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
SWBCAPABILITY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
SWBSERVSTATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
SWLCFID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
SWLCVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
SWLDINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
SWLDSAF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
SWLDST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717
SYNCSRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
SYNCSTAT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 718
SYSID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
t . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
T200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
T3105 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
T3115 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
T3151 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
TAADJ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
TCC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
TCCCHLDI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
TDMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
TEI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
TESTMODE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
TESTMON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
TESTNO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
TESTOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
TESTPWRRED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
TESTST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
TIMEDELAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
TNCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
TNFTARGF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
TRXAREA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
TRXCPBL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
TRXFREQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
TRXMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
TSC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
TSLPOOL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
TSYNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
TSYNCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
TSYNCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
TSYNCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 738
TTRAU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
TUPLREP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
TXBMAXF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
TXBMINF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
TXDIVTSEXCPT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
16
Id:0900d80580627b1d
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
TXDIVTSPAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TXLEVADJ. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TXSIGLEVADJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TXSIGLEVADJC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TYPOFETH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TYPRACK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
741
741
742
742
742
743
v. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VENDNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VGSCULFT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VLANID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VSWRTDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
745
745
745
746
747
w .....................................................
WDDUVSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
WDFTNFP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
WDLNA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
748
748
750
752
Nack causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
Appendix: values for ERFACCHALPDMF, ERFACCHCMDF, ERSACCHDL, ERSACCHUL and ETOP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
A50016-G5100-B333-04-7619
Id:0900d80580627b1d
17
BS-4x / 82 II / 240 / 241 / 240XL commands
List of Figures
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
18
BTSEP BR10.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
BTSEP BR10.0: tree view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
BTSEP BR10.0: graphic view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
BTSEP BR10.0 tree view with list of command . . . . . . . . . . . . . . . . . . . 31
BTSP BR10.0: CREATE ... ACDCP command (example) . . . . . . . . . . . 32
BTSP BR10.0: SET ... COBA command (example) . . . . . . . . . . . . . . . . 32
Command viewer window: CREATE ... BPORT command (example) . . 33
Command viewer window: SET ... COBA command (example) . . . . . . . 33
BS240, BS241, BS240XL, BS40, BS41, BS40II and BS82II main tree . 34
Id:0900d80580627b1d
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Reason for update
Reason for update
Issue history
Issue
Date
Summary
01
07/2008
New release BR10.0
02
11/2008
New commands and attributes have been added and modified
03
03/2009
New commands and attributes have been added and modified
04
10/2009
The description of ALRMT1/T2/T3 attributes related to COBA
object has been updated. Default values have been updated too.
Issue 04 for release BR10.0
Chapter/Section
2. Objects and commands in
alphabetical order
Summary
BCOM: CREATE
BTSEP: GETACTIVEALARMS
BTSM: ACTIVATE
COBA: SET
F6DCTMA: CREATE, DELETE, GET, GETTEST,
LOCK, PERFTEST, STOPTEST, UNLOCK.
F6LNA: CREATE, DELETE, GET, GETTEST,
LOCK, PERFTEST, STOPTEST, SET, UNLOCK.
F6TNFP: CREATE, DELETE, GET, GETTEST,
LOCK, PERFTEST, STOPTEST, SET, UNLOCK.
F6VSWRP: CREATE, DELETE, GET, GETTEST,
LOCK, PERFTEST, STOPTEST, SET, UNLOCK.
SOFTWARE-MANAGEMENT: DNLALLEXE
SOFTWARE-MANAGEMENT
For MOC mentioned above the System
Responses, Application Guidelines and Example
section have been updated
3 Parameters/attributes in alpha- Modified attributes: ALRMSEVXXX, BCPBL,
betical order
GTWADRV4, LAPDCH, MORT
A50016-G5100-B333-04-7619
Id:0900d8058064b2a7
19
Reason for update
20
BS-4x / 82 II / 240 / 241 / 240XL commands
Id:0900d8058064b2a7
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Introduction
1 Introduction
1.1
General
This manual describes the commands for the BTSE, necessary to manage the
BS4x/240/241/240XL/BS40II/BS82II (BTSplus Mainline) network elements. Each time
the term BTSplus Mainline is used, the term is referred to the
BS4x/240/241/240XL/BS40II/BS82II.
The way to submit any command to manage the BTSplus Mainline system is represented by LMT Evolution Tool.
The LMT Evolution, that is the interface between the user and the NE, can manage different families of possibly connected network element. For instance, the LMT Evolution
is able to recognize and then to visualize the command trees related to the following
BTS equipments:
BS20, BS21, BS22, BS60, BS61
BS40, BS41, BS40II
BS240, BS241, BS240XL
BS82
BS82II
BS240XS
BS288
The LMT Evolution for Base Station is the application commonly used to configure and
maintain the GSM network through a set of functions and procedures tailored to operate
in a local context. Refer to Operating guidelines: LMT Evolution for more details about
LMT Evolution main functionality.
Local context means that the LMT Evolution is physically connected to the Network
Element through an interface based on proprietary protocols (HALCA and DLHC).
(Refer to Figure 1).
Anyway, out of the local context, LMT Evolution does not have an overall control on the
GSM network and, consequently, available functions are limited to those allowed by
local constraints.
The purpose of LMT is to make Operation and Maintenance easy and to provide all information about the state of an NE.
g Position of COBAs and COSAs. COBA/COSA 0 will be found always on the left side
of the rack and COBA/COSA 1 on the right side of the rack.
A50016-G5100-B333-04-7619
Id:0900d80580598372
21
Introduction
BS-4x / 82 II / 240 / 241 / 240XL commands
Figure 1
1.1.1
BTSEP BR10.0
Structure of the manual
The manual is divided into five main parts:
1. Section 1 provides general information about command structure and LMT Evolution operations
2. Section 2 describes objects and commands, listed in alphabetical order
3. Section 3 describes the parameters of the commands, listed in alphabetical order.
Additionally there is the information in which commands the parameter is used
4. Section 4 lists the NACK causes
5. Section 5 is an appendix. It lists the values for some main parameters
There is the possibility to jump by clicking on the selected item (reference to the parameter description or to the GUI representation in chapter 2; reference to the commands in
chapter 3) to the requested information.
In the command representation (chapter 2) the parameters/attributes in brackets are
optional parameters.
22
Id:0900d80580598372
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
1.1.2
Introduction
Structure of the commands
Both generic commands which can be obtained through selections from the LMT tree
and commands which are created by the operator using the CLI interface must use the
following syntax:
1. Action object [object]:NAME=object:n[/object:n],attribute=value[-value] [,attribute=value];
2. Action object :NAME=object:n[/object:n],attribute=value[&value] [,attribute=value];
3. Action object [object]:NAME=object:n[/object:n],[REQATTL]=attribute [&attribute];
4. Action object [object]:NAME=object:n[/object:n];
g The syntax rules shown in example 2. are used only for GET commands.
where:
"Action" specifies the command that is being executed and that belongs to a list of functions applicable to the BTSE system (for example: "CREATE", "DELETE", "SET", etc).
object represents the hardware or logical identifier that must be submitted to the
command (for example: "RACK", "CU", "BTSM", etc).
[object] logical identifier that must be submitted to the commands DELETE BTSEP
(for example: "DBFILE") FORMAT BTSEP (for example: "FLASH"), GET BTSEP (for
example: "NOSWL", "SWL") or GET CU (for example: "ESN", "NOESN").
"n" specifies the relative number (for example: ACDCP:n n=0, CU:n n=0..11, etc. See
table below). The LMT Evolution CLI allows * or & instead of a simple number for a
object instance (for example: CU:* (all), CU:0&2&3 (0,2,3) or CU:0&&3 (0,1,2,3).
"attribute" is the acronym of the real attribute of an object (for example: LNAPRED=
Low Noise Amplifier Predecessor of DULNA, etc.).
"value" represent the value of the attribute (or the values of its fields). It is possible to
input a value not just using the default data type (usually decimal) but also to input the
data e.g. as hex value or as binary value.
1.1.3
Ranges for the relative number of the BTSE objects
The ranges shown on the LMT Evolution for the relative numbers of the managed
objects depends on the type of hardware to which the LMT Evolution itself is connected.
The following tables show the ranges allowed for the managed objects of the different
type of BTSE racks (i.e. base, extension, service) relevant to BTSplus Mainline.
BS240 /BS241 BS240SR BS240XL
BS241SR
BS240XLSR BS4x
ACDCP
0..1
0..1
ACT
BATTERY
0..3
0..3
0..1
BCOM
0..1
0..1
BPORT
0..7
0..7
0..7
BTS
0..11
0..11
0..3
BTSEP
BTSM
A50016-G5100-B333-04-7619
Id:0900d80580598372
23
Introduction
BS-4x / 82 II / 240 / 241 / 240XL commands
CHAN
0..7
0..7
0..7
COBA
0..1
0..1
0..1
COSA***)
0..1
0..1
0..1
CU
0..7
0..11
0..3
DIDCTMA
0..3
0..7
0..1
DILNA
0..3
0..7
0..1
DUAMCO
0..3
0..5
0..1
DUDCTMA
0..7
0..11
0..3
DULNA
0..7
0..11
0..3
DUVSWR
0..7
0..11
0..3
ENVABTSE
0..56 *)
0..8
0..56 *) **)
0..8 **)
0..56
ETHCON
F6DCTMA
0..3
0..3
F6LNA
0..3
0..3
F6TNFP
0..11
0..11
F6VSWRP
0..1
0..1
FANP***)
0..5
0..5
0..7
0..7
0..5
FCUMAIN
0..7
0..11
0..3
FCUTR
0..15
0..23
0..7
FTNFP
0..7
0..7
0..3
FVSWRP
0..3
0..3
0..1
LAPDLE
0..10
0..10
0..10
0..10
0..10
LMU
RACK
0..7
4..7
0, 1, 3..7
3..7
0, 4..7
BTSETEST
1..255
1..255
1..255
1..255
1..255
TMA***)
0..11
0..15
0..5
SYNCBTSE
TRX
0..23
0..23
0..3
XCONNECT
0..7
0..7
0..7
g *) ENVABTSE object instances 0..56 exist only for rack 0, for other rack instances
the range is 0..8.
g **) ENVABTSE object instances 0 and 1 are not supported by BS240XL,
BS240XLSR.
g ***) COSA, FANP, TMA: no processor
g The LMU function is no longer supported. Do not use any LMU commands.
ACDCP
24
BS40II
BS82II
Id:0900d80580598372
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Introduction
ACT
BATTERY
BCOM
BPORT
0..7
0..3 (note)
BTS
0..3
0..5
BTSEP
BTSM
CHAN
0..7
0..7
COBA
0..1
COSA
0..1
CU
0..3
0..1
DIDCTMA
0..1
DILNA
0..1
DUDCTMA
0..7
0..1
DULNA
0..7
0..1
DUVSWR
0..7
0..1
ENVABTSE
0..56 *)
0..5
ETHCON
F6DCTMA
F6LNA
F6TNFP
F6VSWRP
FANP
0..4
FCUMAIN
0..3
0..1
FCUTR
0..7
0..3
FCUMAIN
0..3
0..1
FCUTR
0..7
0..3
FTNFP
0..7
FVSWRP
0..3
LAPDLE
0..10
0..10 (note)
LMU
RACK
0, 4..7
0..2
BTSETEST
1..255
1..255
TMA
0..7
0..3
SYNCBTSE
TRX
0..3
0..5
A50016-G5100-B333-04-7619
Id:0900d80580598372
25
Introduction
BS-4x / 82 II / 240 / 241 / 240XL commands
XCONNECT
0..7
0..3 (note)
g *) ENVABTSE object instances 0..56 exist only for rack 0, for other rack instances
the range is 0..8.
g BS82II BPORT object: range 0..3 is supported only if COBA4P12 is installed, in all
other cases the range is 0..1.
g BS82II LAPDLE object: in case of COBA4P12 the BTSE will reject the creation of
object instances 5..10.
g BS82II XCONNECT object: instances #2 and #3 are supported only if COBA4P12
is installed, in all other cases only instances 0 and 1 are allowed.
g BS40/41 with its low number of carrier units shall be excluded from switched beam
solution.
g The LMU function is no longer supported. Do not use any LMU commands.
1.1.4
Command layout
The first information given for each command is the phase, or phases, within which the
command can be entered. Then, subsequent selections are shown which are required
to get the command starting from the LMT Evolution Tree.
The command is specified with its syntax and it is followed by the individual fields used
to explain the functions of the command itself.
Command Tree:
The command tree shows the way to get the command and a hint to a GUI example in
chapter 1.
Applicability:
This field shows the working phases and the user profile which allow the execution of
the command. The user profile visibility level is associated with a user identification
"user_id" and password. Four user profiles visibility level are provided:
0
ReadOnly
Command Access
ReadWrite
Super User
Each profile gives the user different access levels to the system features and the higher
is the level the higher is the number of operations which can be performed.
g For User_id and Password contact your local service organization.
Command Description:
This field explains the function of the command transmitted by the LMT Evolution to the
BTSE (when and why it is used, for which operation task).
Long Names:
26
Id:0900d80580598372
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Introduction
This part shows (for an overview) the abbreviations of the parameters/attributes used in
the command and its corresponding long names.
System Responses:
They are response messages sent as acknowledgment for completion of input
commands or they contain information requested by the user. The typical structure of
the response messages contains: the date and time, the command line, the system
response. The response messages can be either normal (successful) or error messages. In such a case they contain the reason for the failure.
Short system messages such as: indication of system loading/downloading functions in
progress, are also reported as information to the LMT Evolution.
Application Guidelines:
These are warnings given when using this command or information related to the environment in which the command is submitted.
Example of Command Execution:
This is an example on how to enter the command with its parameters and their relevant
values.
A50016-G5100-B333-04-7619
Id:0900d80580598372
27
Introduction
BS-4x / 82 II / 240 / 241 / 240XL commands
1.2
Graphical user interface (GUI) representation of the LMT
Evolution
g Reference figures: the reported figures are only for reference and could be not
aligned to the last version of LMT Evolution product.
1.2.1
Start LMT Evolution window
LMT Evolution is the graphical user interface which performs the command interaction
with the Network Element. This enables the user to navigate the object containment
Tree View (see Figure 2) or Graphic View (see Figure 3) of the NE and to select a
specific command from a list of available ones.
From the graphical point of view, the LMT Evolution Main window provides an access
point to all the LMT Evolution functionality and represents an overall monitoring mode
as regards the connection status information.
According to its dynamic and "adaptive" properties, the LMT Evolution Main window is
displayed taking into account the connection and operating parameters that may affect
the visualization of the resulting window functionality.
The main parameters that influence the visualization of LMT Evolution Main Window
are:
Working Context: indicates a mode in which the user is currently working with the
LMT Evolution
Network Element configuration: family, type, phase, version, etc.
By using the LMT Evolution the user can:
Acquire commands, action or scripts
Send and receive messages containing commands or responses to/from the
network element
Have script/commands translation services
Store issued commands and retrieve responses coming from the NE
28
Id:0900d80580598372
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Figure 2
A50016-G5100-B333-04-7619
Introduction
BTSEP BR10.0: tree view
Id:0900d80580598372
29
Introduction
BS-4x / 82 II / 240 / 241 / 240XL commands
Figure 3
30
BTSEP BR10.0: graphic view
Id:0900d80580598372
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
1.2.2
Introduction
LMT Evolution windows for GET, CREATE, SET, ..., commands
The LMT Evolution is mainly used to build CREATE, SET, GET, LOCK, UNLOCK, etc.
commands to be sent to the Network Element. Starting from the containment Tree View
or Graphic View,you can perform the following operations:
Select the functional/equipment/software management object
Select a command from the list of commands displayed by the pop up list box (see
Figure 4)
Figure 4
BTSEP BR10.0 tree view with list of command
The presence of ellipses (see SET ... COBA Command) following the name of the
command indicates that the command could require a further configuration of the attributes before being submitted. In this case the Command Viewer window is opened and
the user can fill in the attribute cells as desired.
If no ellipses are present (see GET COBA Command), the command does not need any
further configuration and it is submitted to the network element without opening the
Command Viewer window.
In case of the presence of ellipses (see CREATE ... BPORT Command in Figure 5 or
SET ... COBA Command in Figure 6) the Command Viewer panel is displayed (see
Figure 7 and Figure 8). The user has to perform the following operations:
Select one or more parameters and choose the appropriate values, the command is
executed after clicking on the Submit button
If, during the translation phase, an error is found in the command string, the
command is not sent to the N.E. In this case reenter the command following the
instructions provided by the diagnostic message shown in the right middle pane.
A50016-G5100-B333-04-7619
Id:0900d80580598372
31
Introduction
32
BS-4x / 82 II / 240 / 241 / 240XL commands
Figure 5
BTSP BR10.0: CREATE ... ACDCP command (example)
Figure 6
BTSP BR10.0: SET ... COBA command (example)
Id:0900d80580598372
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Introduction
Figure 7
Command viewer window: CREATE ... BPORT command (example)
Figure 8
Command viewer window: SET ... COBA command (example)
For all procedures of module replacement the actions to be performed are similar. As
first action, the module must be locked, replaced, tested and finally unlocked. Some
modules have to be replaced without locking and for some others, the BTSEP has to be
switched from phase 3 to 2.
A50016-G5100-B333-04-7619
Id:0900d80580598372
33
Introduction
BS-4x / 82 II / 240 / 241 / 240XL commands
1.3
1.3.1
Command tree
BS240, BS241, BS240XL, BS40, BS41, BS40II and BS82II main tree
MANAGED ELEMENT
BSS-EQUIPMENT
BTSEP
BPORT
CESPW
CESTUNNEL
COBAETHINTF
ETHPORT
LAPDLE
SYNCBTSE
XCONNECT
RACK
BTSETEST
REMINV
ACDCP
ACT
BATTERY
BCOM
COBA
COSA
BSS-FUNCTIONAL
BTSM
CU
DIDCTMA
DILNA
BTS
TRX
CHAN
DUDCTMA
DULNA
DUVSWR
ENVABTSE
FANP
SOFTWARE-MANAGEMENT
FCUMAIN
FCUTR
FTNFP
FVSWRP
F6DTMA
F6LNA
F6TNFP
F6VSWRP
LMU
TMA
ETHCON
DUAMCO
Figure 9
34
BS240, BS241, BS240XL, BS40, BS41, BS40II and BS82II main tree
Id:0900d80580598372
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
1.3.2
Managed Element
Introduction
Alphabetical list of commands
Phase1
Phase2
Phase3
CREATE ACDCP
CREATE ACDCP
DELETE ACDCP
DELETE ACDCP
GET ACDCP
GET ACDCP
GETTEST ACDCP
GETTEST ACDCP
LOCK ACDCP
LOCK ACDCP
PERFTEST ACDCP
PERFTEST ACDCP
STOPTEST ACDCP
STOPTEST ACDCP
UNLOCK ACDCP
UNLOCK ACDCP
Phase2
Phase3
CREATE ACT
CREATE ACT
DELETE ACT
DELETE ACT
GET ACT
GET ACT
GETTEST ACT
GETTEST ACT
LOCK ACT
LOCK ACT
PERFTEST ACT
PERFTEST ACT
STOPTEST ACT
STOPTEST ACT
UNLOCK ACT
UNLOCK ACT
Phase2
Phase3
CREATE BATTERY
CREATE BATTERY
DELETE BATTERY
DELETE BATTERY
GET BATTERY
GET BATTERY
GETTEST BATTERY
GETTEST BATTERY
LOCK BATTERY
LOCK BATTERY
PERFTEST BATTERY
PERFTEST BATTERY
STOPTEST BATTERY
STOPTEST BATTERY
UNLOCK BATTERY
UNLOCK BATTERY
Phase2
Phase3
ACDCP
Managed Element
Phase1
ACT
Managed Element
Phase1
BATTERY
Managed Element
Phase1
A50016-G5100-B333-04-7619
Id:0900d80580598372
35
Introduction
BS-4x / 82 II / 240 / 241 / 240XL commands
BCOM
Managed Element
Phase1
CREATE BCOM
CREATE BCOM
DELETE BCOM
DELETE BCOM
GET BCOM
GET BCOM
GETWIRINGRX BCOM
GETWIRINGRX BCOM
GETWIRINGTX BCOM
GETWIRINGTX BCOM
GETRELATIONSHIP
BCOM
GETRELATIONSHIP
BCOM
GETTEST BCOM
GETTEST BCOM
LOCK BCOM
LOCK BCOM
PERFTEST BCOM
PERFTEST BCOM
SET BCOM
SET BCOM
SETWIRINGRX BCOM
SETWIRINGRX BCOM
SETWIRINGTX BCOM
SETWIRINGTX BCOM
STOPTEST BCOM
STOPTEST BCOM
UNLOCK BCOM
UNLOCK BCOM
Phase2
Phase3
CREATE BPORT
CREATE BPORT
DELETE BPORT
DELETE BPORT
GET BPORT
GET BPORT
LOCK BPORT
LOCK BPORT
SET BPORT
SET BPORT
UNLOCK BPORT
UNLOCK BPORT
Phase2
Phase3
BPORT
Managed Element
Phase1
BTS
GET BTS
GET BTS TIMER
Managed Element
Phase1
Phase2
Phase3
BTSEP
DELETE BTSEP DBFILE
FORMAT BTSEP FLASH
FORMAT BTSEP FLASH
GET BTSEP NOSWL
36
Id:0900d80580598372
GET BTSEP NOSWL
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Managed Element
Introduction
GET BTSEP SWL
GET BTSEP SWL
GETACTIVEALARMS
BTSEP
GETACTIVEALARMS
BTSEP
PERFTEST BTSEP
PERFTEST BTSEP
PING BTSEP
PING BTSEP
SET BTSEP
SET BTSEP
STOPTEST BTSEP
STOPTEST BTSEP
Phase2
Phase3
GET BTSETEST
GET BTSETEST
Phase1
Phase2
Phase3
ACTIVATE BTSM
ACTIVATE BTSM
Phase1
BTSETEST
Managed Element
BTSM
ACTIVATE_DELAYED
BTSM
CONNBSC BTSM
DISCBSC BTSM
FWUPGRADE BTSM
FWUPGRADE BTSM
GET BTSM NOSWL
GET BTSM NOSWL
GET BTSM OVERLOAD
GET BTSM OVERLOAD
GET BTSM SWL
GET BTSM SWL
LOCKREQUEST BTSM
SET BTSM
SHUTDOWN BTSM
UNLOCKREQUEST
BTSM
Managed Element
Phase1
Phase2
Phase3
CREATE CESPW
CREATE CESPW
DELETE CESPW
DELETE CESPW
GET CESPW
GET CESPW
LOCK CESPW
LOCK CESPW
SET CESPW
SET CESPW
CESPW
A50016-G5100-B333-04-7619
Id:0900d80580598372
37
Introduction
Managed Element
BS-4x / 82 II / 240 / 241 / 240XL commands
Phase1
UNLOCK CESPW
UNLOCK CESPW
Phase2
Phase3
CESTUNNEL
CREATE CESTUNNEL
DELETE CESTUNNEL
GET CESTUNNEL
GET CESTUNNEL
LOCK CESTUNNEL
SET CESTUNNEL
SET CESTUNNEL
UNLOCK CESTUNNEL
Managed Element
Phase1
Phase2
Phase3
CHAN
GET CHAN
Managed Element
Phase1
Phase2
Phase3
CREATE COBA
CREATE COBA
DELETE COBA
DELETE COBA
GET COBA
GET COBA
GETRELATIONSHIP
COBA
GETRELATIONSHIP
COBA
GETTEST COBA
GETTEST COBA
LOCK COBA
LOCK COBA
PERFTEST COBA
PERFTEST COBA
SET COBA
SET COBA
STOPTEST COBA
STOPTEST COBA
SWITCH COBA
SWITCH COBA
UNLOCK COBA
UNLOCK COBA
Phase2
Phase3
GET COBAETHINTF
GET COBAETHINTF
COBA
Managed Element
Phase1
COBAETHINTF
LOCK COBAETHINTF
SET COBAETHINTF
38
Id:0900d80580598372
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Introduction
UNLOCK COBAETHINTF
Managed Element
Phase1
Phase2
Phase3
CREATE COSA
CREATE COSA
DELETE COSA
DELETE COSA
GET COSA
GET COSA
GETTEST COSA
GETTEST COSA
LOCK COSA
LOCK COSA
PERFTEST COSA
PERFTEST COSA
STOPTEST COSA
STOPTEST COSA
UNLOCK COSA
UNLOCK COSA
Phase2
Phase3
CREATE CU
CREATE CU
DELETE CU
DELETE CU
GET CU
GET CU
GET CU FWID
GET CU FWID
GET CU WIRING
GET CU WIRING
GETTEST CU
GETTEST CU
LOCK CU
LOCK CU
PERFTEST CU
PERFTEST CU
SET CU
SET CU
STOPTEST CU
STOPTEST CU
UNLOCK CU
UNLOCK CU
Phase2
Phase3
CREATE DIDCTMA
CREATE DIDCTMA
DELETE DIDCTMA
DELETE DIDCTMA
GET DIDCTMA
GET DIDCTMA
GETTEST DIDCTMA
GETTEST DIDCTMA
LOCK DIDCTMA
LOCK DIDCTMA
PERFTEST DIDCTMA
PERFTEST DIDCTMA
COSA
Managed Element
Phase1
CU
Managed Element
Phase1
DIDCTMA
A50016-G5100-B333-04-7619
Id:0900d80580598372
39
Introduction
Managed Element
BS-4x / 82 II / 240 / 241 / 240XL commands
Phase1
STOPTEST DIDCTMA
STOPTEST DIDCTMA
UNLOCK DIDCTMA
UNLOCK DIDCTMA
Phase2
Phase3
CREATE DILNA
CREATE DILNA
DELETE DILNA
DELETE DILNA
GET DILNA
GET DILNA
GETTEST DILNA
GETTEST DILNA
LOCK DILNA
LOCK DILNA
PERFTEST DILNA
PERFTEST DILNA
SET DILNA
SET DILNA
STOPTEST DILNA
STOPTEST DILNA
UNLOCK DILNA
UNLOCK DILNA
Phase2
Phase3
DELETE DUAMCO
DELETE DUAMCO
GET DUAMCO
GET DUAMCO
GETTEST DUAMCO
GETTEST DUAMCO
LOCK DUAMCO
LOCK DUAMCO
PERFTEST DUAMCO
PERFTEST DUAMCO
STOPTEST DUAMCO
STOPTEST DUAMCO
UNLOCK DUAMCO
UNLOCK DUAMCO
Phase2
Phase3
CREATE DUDCTMA
CREATE DUDCTMA
DELETE DUDCTMA
DELETE DUDCTMA
GET DUDCTMA
GET DUDCTMA
GETTEST DUDCTMA
GETTEST DUDCTMA
LOCK DUDCTMA
LOCK DUDCTMA
PERFTEST DUDCTMA
PERFTEST DUDCTMA
STOPTEST DUDCTMA
STOPTEST DUDCTMA
UNLOCK DUDCTMA
UNLOCK DUDCTMA
DILNA
Managed Element
Phase1
DUAMCO
Managed Element
Phase1
DUDCTMA
40
Id:0900d80580598372
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Managed Element
Phase1
Introduction
Phase2
Phase3
CREATE DULNA
CREATE DULNA
DELETE DULNA
DELETE DULNA
GET DULNA
GET DULNA
GETTEST DULNA
GETTEST DULNA
LOCK DULNA
LOCK DULNA
PERFTEST DULNA
PERFTEST DULNA
SET DULNA
SET DULNA
STOPTEST DULNA
STOPTEST DULNA
UNLOCK DULNA
UNLOCK DULNA
Phase2
Phase3
CREATE DUVSWR
CREATE DUVSWR
DELETE DUVSWR
DELETE DUVSWR
GET DUVSWR
GET DUVSWR
GETTEST DUVSWR
GETTEST DUVSWR
LOCK DUVSWR
LOCK DUVSWR
PERFTEST DUVSWR
PERFTEST DUVSWR
SET DUVSWR
SET DUVSWR
STOPTEST DUVSWR
STOPTEST DUVSWR
UNLOCK DUVSWR
UNLOCK DUVSWR
Phase2
Phase3
CREATE ENVABTSE
CREATE ENVABTSE
DELETE ENVABTSE
DELETE ENVABTSE
GET ENVABTSE
GET ENVABTSE
LOCK ENVABTSE
LOCK ENVABTSE
SET ENVABTSE
SET ENVABTSE
UNLOCK ENVABTSE
UNLOCK ENVABTSE
Phase2
Phase3
DULNA
Managed Element
Phase1
DUVSWR
Managed Element
Phase1
ENVABTSE
Managed Element
Phase1
ETHCON
A50016-G5100-B333-04-7619
Id:0900d80580598372
41
Introduction
BS-4x / 82 II / 240 / 241 / 240XL commands
CREATE ETHCON
DELETE ETHCON
GET ETHCON
GET ETHCON
LOCK ETHCON
SET ETHCON
SET ETHCON
UNLOCK ETHCON
Managed Element
Phase1
Phase2
Phase3
CREATE ETHPORT
CREATE ETHPORT
DELETE ETHPORT
DELETE ETHPORT
GET ETHPORT
GET ETHPORT
LOCK ETHPORT
LOCK ETHPORT
SET ETHPORT
SET ETHPORT
UNLOCK ETHPORT
UNLOCK ETHPORT
Phase2
Phase3
CREATE F6DCTMA
CREATE F6DCTMA
DELETE F6DCTMA
DELETE F6DCTMA
GET F6DCTMA
GET F6DCTMA
GETTEST F6DCTMA
GETTEST F6DCTMA
LOCK F6DCTMA
LOCK F6DCTMA
PERFTEST F6DCTMA
PERFTEST F6DCTMA
STOPTEST F6DCTMA
STOPTEST F6DCTMA
UNLOCK F6DCTMA
UNLOCK F6DCTMA
Phase2
Phase3
CREATE F6LNA
CREATE F6LNA
DELETE F6LNA
DELETE F6LNA
GET F6LNA
GET F6LNA
GETTEST F6LNA
GETTEST F6LNA
LOCK F6LNA
LOCK F6LNA
PERFTEST F6LNA
PERFTEST F6LNA
ETHPORT
Managed Element
Phase1
F6DCTMA
Managed Element
Phase1
F6LNA
42
Id:0900d80580598372
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Managed Element
Phase1
Introduction
SET F6LNA
SET F6LNA
STOPTEST F6LNA
STOPTEST F6LNA
UNLOCK F6LNA
UNLOCK F6LNA
Phase2
Phase3
CREATE F6TNFP
CREATE F6TNFP
DELETE F6TNFP
DELETE F6TNFP
GET F6TNFP
GET F6TNFP
GETTEST F6TNFP
GETTEST F6TNFP
LOCK F6TNFP
LOCK F6TNFP
PERFTEST F6TNFP
PERFTEST F6TNFP
STOPTEST F6TNFP
STOPTEST F6TNFP
UNLOCK F6TNFP
UNLOCK F6TNFP
Phase2
Phase3
CREATE F6VSWRP
CREATE F6VSWRP
DELETE F6VSWRP
DELETE F6VSWRP
GET F6VSWRP
GET F6VSWRP
GETTEST F6VSWRP
GETTEST F6VSWRP
LOCK F6VSWRP
LOCK F6VSWRP
PERFTEST F6VSWRP
PERFTEST F6VSWRP
SET F6VSWRP
SET F6VSWRP
STOPTEST F6VSWRP
STOPTEST F6VSWRP
UNLOCK F6VSWRP
UNLOCK F6VSWRP
Phase2
Phase3
CREATE FANP
CREATE FANP
DELETE FANP
DELETE FANP
GET FANP
GET FANP
GETTEST FANP
GETTEST FANP
LOCK FANP
LOCK FANP
PERFTEST FANP
PERFTEST FANP
F6TNFP
Managed Element
Phase1
F6VSWRP
Managed Element
Phase1
FANP
A50016-G5100-B333-04-7619
Id:0900d80580598372
43
Introduction
Managed Element
BS-4x / 82 II / 240 / 241 / 240XL commands
Phase1
STOPTEST FANP
STOPTEST FANP
UNLOCK FANP
UNLOCK FANP
Phase2
Phase3
CREATE FCUMAIN
CREATE FCUMAIN
DELETE FCUMAIN
DELETE FCUMAIN
GET FCUMAIN
GET FCUMAIN
GET FCUMAIN FWID
GET FCUMAIN FWID
GET FCUMAIN WIRING
GET FCUMAIN WIRING
GETTEST FCUMAIN
GETTEST FCUMAIN
LOCK FCUMAIN
LOCK FCUMAIN
PERFTEST FCUMAIN
PERFTEST FCUMAIN
SET FCUMAIN
SET FCUMAIN
STOPTEST FCUMAIN
STOPTEST FCUMAIN
UNLOCK FCUMAIN
UNLOCK FCUMAIN
Phase2
Phase3
CREATE FCUTR
CREATE FCUTR
DELETE FCUTR
DELETE FCUTR
GET FCUTR
GET FCUTR
GETTEST FCUTR
GETTEST FCUTR
LOCK FCUTR
LOCK FCUTR
PERFTEST FCUTR
PERFTEST FCUTR
SET FCUTR
SET FCUTR
STOPTEST FCUTR
STOPTEST FCUTR
UNLOCK FCUTR
UNLOCK FCUTR
Phase2
Phase3
CREATE FTNFP
CREATE FTNFP
DELETE FTNFP
DELETE FTNFP
GET FTNFP
GET FTNFP
GETTEST FTNFP
GETTEST FTNFP
FCUMAIN
Managed Element
Phase1
FCUTR
Managed Element
Phase1
FTNFP
44
Id:0900d80580598372
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Managed Element
Phase1
Introduction
LOCK FTNFP
LOCK FTNFP
PERFTEST FTNFP
PERFTEST FTNFP
STOPTEST FTNFP
STOPTEST FTNFP
UNLOCK FTNFP
UNLOCK FTNFP
Phase2
Phase3
CREATE FVSWRP
CREATE FVSWRP
DELETE FVSWRP
DELETE FVSWRP
GET FVSWRP
GET FVSWRP
GETTEST FVSWRP
GETTEST FVSWRP
LOCK FVSWRP
LOCK FVSWRP
PERFTEST FVSWRP
PERFTEST FVSWRP
STOPTEST FVSWRP
STOPTEST FVSWRP
UNLOCK FVSWRP
UNLOCK FVSWRP
Phase2
Phase3
CREATE LAPDLE
CREATE LAPDLE
DELETE LAPDLE
DELETE LAPDLE
GET LAPDLE
GET LAPDLE
Phase2
Phase3
FVSWRP
Managed Element
Phase1
LAPDLE
Managed Element
Phase1
LMU
The LMU function is no longer supported. Please do not use any LMU commands.
Managed Element
Phase1
Phase2
Phase3
CREATE RACK
CREATE RACK
DELETE RACK
DELETE RACK
GET RACK
GET RACK
LOCK RACK
LOCK RACK
RACK
SET RACK
Managed Element
Phase1
A50016-G5100-B333-04-7619
UNLOCK RACK
UNLOCK RACK
Phase2
Phase3
Id:0900d80580598372
45
Introduction
BS-4x / 82 II / 240 / 241 / 240XL commands
REMINV
Managed Element
DNLIDFD REMINV
DNLIDFD REMINV
UPLLIDF REMINV
UPLLIDF REMINV
UPLLIDF REMINV
Phase1
Phase2
Phase3
DNLALLEXE
SOFTWARE-MANAGEMENT
DNLALLEXE
SOFTWARE-MANAGEMENT
SOFTWARE-MANAGEMENT
Managed Element
Phase1
UPLBTSLOG
SOFTWARE-MANAGEMENT
UPLBTSLOG
SOFTWARE-MANAGEMENT
Phase2
Phase3
GET SYNCBTSE
GET SYNCBTSE
GETTEST SYNCBTSE
GETTEST SYNCBTSE
LOCK SYNCBTSE
LOCK SYNCBTSE
PERFTEST SYNCBTSE
PERFTEST SYNCBTSE
SET SYNCBTSE
SET SYNCBTSE
STOPTEST SYNCBTSE
STOPTEST SYNCBTSE
UNLOCK SYNCBTSE
UNLOCK SYNCBTSE
Phase2
Phase3
CREATE TMA
CREATE TMA
DELETE TMA
DELETE TMA
GET TMA
GET TMA
GET TMA PRODUCTINFO
GET TMA PRODUCTINFO
GETTEST TMA
GETTEST TMA
LOCK TMA
LOCK TMA
PERFTEST TMA
PERFTEST TMA
STOPTEST TMA
STOPTEST TMA
UNLOCK TMA
UNLOCK TMA
SYNCBTSE
Managed Element
Phase1
TMA
46
Id:0900d80580598372
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Managed Element
Phase1
Introduction
Phase2
Phase3
TRX
GET TRX
GETRELATIONSHIP
TRX
Managed Element
Phase1
Phase2
Phase3
CREATE XCONNECT
CREATE XCONNECT
DELETE XCONNECT
DELETE XCONNECT
GET XCONNECT
GET XCONNECT
LOCK XCONNECT
LOCK XCONNECT
SET XCONNECT
SET XCONNECT
UNLOCK XCONNECT
UNLOCK XCONNECT
XCONNECT
A50016-G5100-B333-04-7619
Id:0900d80580598372
47
Objects and commands in alphabetical order
BS-4x / 82 II / 240 / 241 / 240XL commands
2 Objects and commands in alphabetical order
48
Id:0900d80580248205
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ACDCP
ACDCP
The ACDCP converter consists of two different power supply and control units: ACPSC
(AC power supply, charging and supervising of the battery backup system) and DCPSC
(DC power supply).
CREATE ACDCP
CREATE ACDCP
NAME=RACK:0..7/ACDCP:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACDCP h
CREATE ACDCP
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the AC/DC Converter Panel to the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 41
PC Time&Date: 11:55:28 03/23/2005
NE Time&Date: 12:57:03 09/15/2004
USER NAME:
User_a
COMMAND:
Create ACDCP:NAME=RACK:0/ACDCP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 41
JOB: 42
A50016-G5100-B333-04-7619
Id:0900d80580593f21
49
ACDCP
BS-4x / 82 II / 240 / 241 / 240XL commands
PC Time&Date: 11:55:28 03/23/2005
NE Time&Date: 12:57:03 09/15/2004
USER NAME:
User_a
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/ACDCP:0
Availability Status = NULL_value
Notification Identifier = 284
END OF OUTPUT FOR JOB 42
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 43
PC Time&Date: 11:55:28 03/23/2005
NE Time&Date: 12:57:03 09/15/2004
USER NAME:
User_a
COMMAND:
Create ACDCP:NAME=RACK:0/ACDCP:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
MO already created (-159)
END OF OUTPUT FOR JOB 43
Application Guidelines:
The ACDCP is not necessary for the BS240
The ACDCP can not be created for the BS240 Compact Site as it is equipped in the
Energy Station Rack which is not supervised by the SW
The ACDCP can not be created for the BS240, BS241, BS240XL, BS40II
Example of Command Execution:
Create ACDCP:NAME=RACK:0/ACDCP:0;
50
Id:0900d80580593f21
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ACDCP
DELETE ACDCP
DELETE ACDCP
NAME=RACK:0..7/ACDCP:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACDCP h
DELETE ACDCP
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the AC/DC Converter Panel from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 38
PC Time&Date: 11:55:25 03/23/2005
NE Time&Date: 12:57:00 09/15/2004
USER NAME:
User_a
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/ACDCP:0
ChangeInfo = deleted
END OF OUTPUT FOR JOB 38
JOB: 39
PC Time&Date: 11:55:25 03/23/2005
NE Time&Date: 12:57:00 09/15/2004
A50016-G5100-B333-04-7619
Id:0900d80580593f21
51
ACDCP
BS-4x / 82 II / 240 / 241 / 240XL commands
USER NAME:
User_a
COMMAND:
Delete ACDCP:NAME=RACK:0/ACDCP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 39
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
ACDCP must be locked in phase 3 before deletion
The ACDCP can not be deleted for the BS-240 Compact Site as it is equipped in the
Energy Station Rack which is not supervised by the SW
The ACDCP can not be deleted for the BS-40II
Example of Command Execution:
Delete ACDCP:NAME=RACK:0/ACDCP:0;
GET ACDCP
GET ACDCP
NAME=RACK:0..7/ACDCP:0..1 [,REQATTL=ALS, AST,
AVS, OST, PRS, RELFUNCOBJ];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACDCP h
GET ACDCP
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the AC/DC converter Panel of the BTSE.
Long Names:
52
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
PRS
proceduralStatus
Id:0900d80580593f21
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
RELFUNCOBJ
ACDCP
relatedFuncObjects
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 23
PC Time&Date: 11:55:04 03/23/2005
NE Time&Date: 12:56:39 09/15/2004
USER NAME:
User_a
COMMAND:
Get ACDCP:NAME=RACK:0/ACDCP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
operationalState = ENABLED
proceduralStatus = NULL
relatedFuncObjects =
END OF OUTPUT FOR JOB 23
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
The GET ACDCP command cannot be issued for the BS-240 Compact Site as the
ACDCP is equipped in the Energy Station Rack which is not supervised by the SW
The GET ACDCP command cannot be issued for the BS-40II
Example of Command Execution:
Get ACDCP:NAME=RACK:0/ACDCP:0,REQATTL=ALS&AST&AVS&OST&PRS&
RELFUNCOBJ;
GETTEST ACDCP
GETTEST ACDCP
A50016-G5100-B333-04-7619
NAME=RACK:0..7/ACDCP:0..1;
Id:0900d80580593f21
53
ACDCP
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACDCP h
GETTEST ACDCP
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the AC/DC converter test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 36
PC Time&Date: 11:55:22 03/23/2005
NE Time&Date: 12:56:57 09/15/2004
USER NAME:
User_a
COMMAND:
Gettest ACDCP:NAME=RACK:0/ACDCP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/ACDCP:0
testMonitor =
phaseId = PreliminaryTestsAcdcp
phaseStatus = Running
phaseId = CheckAlarmStatusAcdcp
phaseStatus = Waiting
phaseId = EndTestAcdcp
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
END OF OUTPUT FOR JOB 36
54
Id:0900d80580593f21
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ACDCP
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest ACDCP:NAME=RACK:0/ACDCP:0;
LOCK ACDCP
LOCK ACDCP
NAME=RACK:0..7/ACDCP:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACDCP h
LOCK ACDCP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of AC/DC converter Panel of the BTSE.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
A50016-G5100-B333-04-7619
Id:0900d80580593f21
55
ACDCP
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 24
PC Time&Date: 11:55:06 03/23/2005
NE Time&Date: 12:56:41 09/15/2004
USER NAME:
User_a
COMMAND:
Lock ACDCP:NAME=RACK:0/ACDCP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 24
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 25
PC Time&Date: 11:55:06 03/23/2005
NE Time&Date: 12:56:41 09/15/2004
USER NAME:
User_a
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/ACDCP:0
Administrative State = LOCKED
Notification Identifier = 271
END OF OUTPUT FOR JOB 25
Operation Failed
The specified change of administrative state has not been performed (e.g. the object is
redundant and its spare copy is disabled or already locked, a subordinate resource
cannot go into disabled state with "dependency" availability status).
56
Id:0900d80580593f21
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ACDCP
Application Guidelines:
The ACDCP can not be locked for the BS-240 Compact Site as it is equipped in the
Energy Station Rack which is not supervised by the SW
The ACDCP can not be locked for the BS-40II
Example of Command Execution:
Lock ACDCP:NAME=RACK:0/ACDCP:0;
PERFTEST ACDCP
PERFTEST ACDCP
NAME=RACK:0..7/ACDCP:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACDCP h
PERFTEST ACDCP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command requests the execution of a test performed by the ACDCP.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSEP.
JOB: 27
PC Time&Date: 11:55:09 03/23/2005
NE Time&Date: 12:56:44 09/15/2004
USER NAME:
User_a
COMMAND:
Perftest ACDCP:NAME=RACK:0/ACDCP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/ACDCP:0
tO = BTSETEST:3
END OF OUTPUT FOR JOB 27
A50016-G5100-B333-04-7619
Id:0900d80580593f21
57
ACDCP
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 28
PC Time&Date: 11:55:09 03/23/2005
NE Time&Date: 12:56:44 09/15/2004
USER NAME:
User_a
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:3
ChangeInfo = created
END OF OUTPUT FOR JOB 28
JOB: 29
PC Time&Date: 11:55:09 03/23/2005
NE Time&Date: 12:56:44 09/15/2004
USER NAME:
User_a
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/ACDCP:0
Operational State = ENABLED
Availability Status = NULL_value
Notification Identifier = 275
END OF OUTPUT FOR JOB 29
JOB: 30
PC Time&Date: 11:55:09 03/23/2005
NE Time&Date: 12:56:44 09/15/2004
58
Id:0900d80580593f21
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ACDCP
USER NAME:
User_a
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:3
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/ACDCP:0
executedPhases =
PreliminaryTestsAcdcp
CheckAlarmStatusAcdcp
EndTestAcdcp
END OF OUTPUT FOR JOB 30
JOB: 31
PC Time&Date: 11:55:09 03/23/2005
NE Time&Date: 12:56:44 09/15/2004
USER NAME:
User_a
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:3
ChangeInfo = deleted
END OF OUTPUT FOR JOB 31
The test results will be displayed at the end of the test phases.
Result TEST:
A50016-G5100-B333-04-7619
name =
TEST:<n>
testOutcome =
This field represents the test result; one of the following values can be displayed:
Id:0900d80580593f21
59
ACDCP
BS-4x / 82 II / 240 / 241 / 240XL commands
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: Message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
In phase 3 MO must be locked previous to the command execution
Example of Command Execution:
Perftest ACDCP:NAME=RACK:0/ACDCP:0;
STOPTEST ACDCP
STOPTEST ACDCP
60
NAME=RACK:0..7/ACDCP:0..1;
Id:0900d80580593f21
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ACDCP
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACDCP h
STOPTEST ACDCP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command stops a test performed by ACDCP.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
...
.
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
phaseId =
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
Application Guidelines:
None.
A50016-G5100-B333-04-7619
Id:0900d80580593f21
61
ACDCP
BS-4x / 82 II / 240 / 241 / 240XL commands
Example of Command Execution:
Stoptest ACDCP:NAME=RACK:0/ACDCP:0;
UNLOCK ACDCP
UNLOCK ACDCP
NAME=RACK:0..7/ACDCP:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACDCP h
UNLOCK ACDCP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of AC/DC converter.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 34
PC Time&Date: 11:55:18 03/23/2005
NE Time&Date: 12:56:53 09/15/2004
USER NAME:
User_a
COMMAND:
Unlock ACDCP:NAME=RACK:0/ACDCP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 34
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
62
Id:0900d80580593f21
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ACDCP
JOB: 35
PC Time&Date: 11:55:18 03/23/2005
NE Time&Date: 12:56:53 09/15/2004
USER NAME:
User_a
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/ACDCP:0
Administrative State = UNLOCKED
Notification Identifier = 280
END OF OUTPUT FOR JOB 35
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
The ACDCP can not be unlocked for the BS-240 Compact Site as it is equipped in
the Energy Station Rack which is not supervised by the SW
The ACDCP can not be unlocked for the BS-40II
Example of Command Execution:
Unlock ACDCP:NAME=RACK:0/ACDCP:0;
A50016-G5100-B333-04-7619
Id:0900d80580593f21
63
ACT
BS-4x / 82 II / 240 / 241 / 240XL commands
ACT
The ACT (Alarm Collection Terminal) object represents the terminal for the collection of
the alarms.
CREATE ACT
CREATE ACT
NAME=RACK:0..7/ACT:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACT h
CREATE ACT
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the ACT (Alarm Collection Terminal) to the BTSE data base. The
ACT contains the interface to the external alarms (Operator alarms, rack alarms, shelter
alarms,...) and commands and a CAN-BUS interface to the CORE.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 187
PC Time&Date: 16:48:48 03/23/2005
NE Time&Date: 16:46:42 09/15/2004
USER NAME:
User_b
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/ACT:0
ChangeInfo = created
64
Id:0900d80580593f23
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ACT
END OF OUTPUT FOR JOB 187
JOB: 188
PC Time&Date: 16:48:48 03/23/2005
NE Time&Date: 16:46:42 09/15/2004
USER NAME:
User_b
COMMAND:
Create ACT:NAME=RACK:0/ACT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 188
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 72
PC Time&Date: 16:37:54 03/23/2005
NE Time&Date: 16:35:47 09/15/2004
USER NAME:
User_b
COMMAND:
Create ACT:NAME=RACK:0/ACT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
Message cannot be performed (-17)
END OF OUTPUT FOR JOB 72
Application Guidelines:
The ACTC which is a part of the DC Panel and it is always present in every rack to
collect all internal alarms. It has inputs for 16 internal alarms (1 Door, 6 Fans and 9
rack/shelter internal alarms, which can be defined by the operator). The ACTC
supports 9 ENVAs within the range from 0...8. BS82II support 5 internal alarms (1
Door, 1 Fans and 3 rack/shelter internal alarms, which can be defined by the operator)
A50016-G5100-B333-04-7619
Id:0900d80580593f23
65
ACT
BS-4x / 82 II / 240 / 241 / 240XL commands
An ACTM for 48 alarms and 8 commands is used only in the Base Rack to support
the external alarm and command interface for the operator. The ACTM consists of
two boards: the ACTA (Alarm and Command Interfaces) and the ACTP (Processor
Core). The ACTP sends the alarms to the CORE via the CAN BUS.
For the Extension Racks and the Service Racks only few alarms (e.g. temperature
supervision, FAN, ACDC alarms,..) are necessary, so an ACTP with 16 alarm or site
inputs is used. The ACTP sends the alarms to the CORE via the CAN BUS.
On a BS82II (base and extension racks) temp., RDO, FAN alarms are controlled by
the ACT (on other platforms from COBA in Base rack), these inputs are only handled
in a correct way if the ACT is created successfully.
Example of Command Execution:
Create ACT:NAME=RACK:0/ACT:0;
DELETE ACT
DELETE ACT
NAME=RACK:0..7/ACT:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACT h
DELETE ACT
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the ACT (Alarm Collection Terminal) from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 196
PC Time&Date: 16:49:26 03/23/2005
NE Time&Date: 16:47:20 09/15/2004
USER NAME:
User_b
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
66
Id:0900d80580593f23
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ACT
ChangedConfigurationNotification:
name = RACK:0/ACT:0
ChangeInfo = deleted
END OF OUTPUT FOR JOB 196
JOB: 197
PC Time&Date: 16:49:26 03/23/2005
NE Time&Date: 16:47:20 09/15/2004
USER NAME:
User_b
COMMAND:
Delete ACT:NAME=RACK:0/ACT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 197
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
ACT must be locked in phase 3 before deletion
Example of Command Execution:
Delete ACT:NAME=RACK:0/ACT:0;
GET ACT
GET ACT
NAME=RACK:0..7/ACT:0..0 [,REQATTL=ALS, AST, AVS,
OST, PRS, RELFUNCOBJ];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACT h GET
ACT
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
A50016-G5100-B333-04-7619
Id:0900d80580593f23
67
ACT
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Description:
This command displays the attributes of the ACT (Alarm Collection Terminal).
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 189
PC Time&Date: 16:49:05 03/23/2005
NE Time&Date: 16:46:59 09/15/2004
USER NAME:
User_b
COMMAND:
Get ACT:NAME=RACK:0/ACT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NotInstalled
operationalState = DISABLED
proceduralStatus = NULL
relatedFuncObjects =
END OF OUTPUT FOR JOB 189
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
None.
68
Id:0900d80580593f23
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ACT
Example of Command Execution:
Get ACT:NAME=RACK:0/ACT:0,REQATTL=ALS&AST&AVS&OST&
PRS&RELFUNCOBJ;
GETTEST ACT
GETTEST ACT
NAME=RACK:0..7/ACT:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACT h
GETTEST ACT
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the ACT (Alarm Collection Terminal) test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 26
PC Time&Date: 11:55:09 03/23/2005
NE Time&Date: 12:56:44 09/15/2004
USER NAME:
User_b
COMMAND:
Gettest ACT:NAME=RACK:0/ACT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/ACT:0
testMonitor =
phaseId = PreliminaryTestsAct
phaseStatus = Running
phaseId = CheckAlarmStatusAct
phaseStatus = Waiting
A50016-G5100-B333-04-7619
Id:0900d80580593f23
69
ACT
BS-4x / 82 II / 240 / 241 / 240XL commands
phaseId = EndTestAct
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
END OF OUTPUT FOR JOB 26
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest ACT:NAME=RACK:0/ACT:0,REQATTL=ALS&AST&AVS&OST&PRS;
LOCK ACT
LOCK ACT
NAME=RACK:0..7/ACT:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACT h LOCK
ACT
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
70
Id:0900d80580593f23
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ACT
Command Description:
This command changes the administrative state of ACT (Alarm Collection Terminal).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 190
PC Time&Date: 16:49:10 03/23/2005
NE Time&Date: 16:47:04 09/15/2004
USER NAME:
User_b
COMMAND:
Lock ACT:NAME=RACK:0/ACT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 190
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 191
PC Time&Date: 16:49:10 03/23/2005
NE Time&Date: 16:47:04 09/15/2004
USER NAME:
User_b
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/ACT:0
A50016-G5100-B333-04-7619
Id:0900d80580593f23
71
ACT
BS-4x / 82 II / 240 / 241 / 240XL commands
Administrative State = LOCKED
Notification Identifier = 566
END OF OUTPUT FOR JOB 191
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
None.
Example of Command Execution:
Lock ACT:NAME=RACK:0/ACT:0;
PERFTEST ACT
PERFTEST ACT
NAME=RACK:0..7/ACT:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACT h
PERFTEST ACT
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of ACT (Alarm Collection Terminal).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSEP.
JOB: 36
PC Time&Date: 11:55:22 03/23/2005
NE Time&Date: 12:56:57 09/15/2004
USER NAME:
User_b
COMMAND:
Perftest ACT:NAME=RACK:0/ACT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
72
Id:0900d80580593f23
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ACT
MOT = RACK:0/ACT:0
tO = BTSETEST:2
END OF OUTPUT FOR JOB 36
JOB: 37
PC Time&Date: 11:55:22 03/23/2005
NE Time&Date: 12:56:57 09/15/2004
USER NAME:
User_b
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:2
ChangeInfo = created
END OF OUTPUT FOR JOB 37
JOB: 38
PC Time&Date: 11:55:25 03/23/2005
NE Time&Date: 12:57:00 09/15/2004
USER NAME:
User_b
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/ACT:0
Operational State = ENABLED
Availability Status = NULL_value
Notification Identifier = 128
A50016-G5100-B333-04-7619
Id:0900d80580593f23
73
ACT
BS-4x / 82 II / 240 / 241 / 240XL commands
END OF OUTPUT FOR JOB 38
JOB: 39
PC Time&Date: 11:55:25 03/23/2005
NE Time&Date: 12:57:00 09/15/2004
USER NAME:
User_b
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:2
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/ACT:0
executedPhases =
PreliminaryTestsAct
CheckAlarmStatusAct
EndTestAct
END OF OUTPUT FOR JOB 39
JOB: 40
PC Time&Date: 11:55:28 03/23/2005
NE Time&Date: 12:57:03 09/15/2004
USER NAME:
User_b
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:2
ChangeInfo = deleted
END OF OUTPUT FOR JOB 40
74
Id:0900d80580593f23
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ACT
The test results will be displayed at the end of the test phases.
Result TEST:
name =
TEST:<n>
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: Message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
In phase 3 MO must be locked previous to the command execution
A50016-G5100-B333-04-7619
Id:0900d80580593f23
75
ACT
BS-4x / 82 II / 240 / 241 / 240XL commands
Example of Command Execution:
Perftest ACT:NAME=RACK:0/ACT:0;
STOPTEST ACT
STOPTEST ACT
NAME=RACK:0..7/ACT:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACT h
STOPTEST ACT
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
...
.
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
phaseId =
76
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
Id:0900d80580593f23
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ACT
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
Application Guidelines:
None.
Example of Command Execution:
Stoptest ACT:NAME=RACK:0/ACT:0;
UNLOCK ACT
UNLOCK ACT
NAME=RACK:0..7/ACT:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ACT h
UNLOCK ACT
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of ACT (Alarm Collection Terminal).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 192
PC Time&Date: 16:49:15 03/23/2005
NE Time&Date: 16:47:09 09/15/2004
USER NAME:
User_b
COMMAND:
Unlock ACT:NAME=RACK:0/ACT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 192
A50016-G5100-B333-04-7619
Id:0900d80580593f23
77
ACT
BS-4x / 82 II / 240 / 241 / 240XL commands
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 193
PC Time&Date: 16:49:15 03/23/2005
NE Time&Date: 16:47:09 09/15/2004
USER NAME:
User_b
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/ACT:0
Administrative State = UNLOCKED
Notification Identifier = 567
END OF OUTPUT FOR JOB 193
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
None.
Example of Command Execution:
Unlock ACT:NAME=RACK:0/ACT:0;
78
Id:0900d80580593f23
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BATTERY
BATTERY
One backup battery system can be connected to the AC/DC sub-rack. The battery
system can consist of up to four batteries optionally housed in the battery sub-rack. The
DC and Battery Controller (DCBCTRL) installed in the AC/DC subrack is the supervision
unit which provides for the Batteries charging.
CREATE BATTERY
CREATE BATTERY
NAME=RACK:0..7/BATTERY:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BATTERY h
CREATE BATTERY
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the BATTERY (which provides battery backup) to the BTSE data
base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 21
PC Time&Date: 11:54:46 03/23/2005
NE Time&Date: 12:56:21 09/15/2004
USER NAME:
User_c
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/BATTERY:0
A50016-G5100-B333-04-7619
Id:0900d80580593f25
79
BATTERY
BS-4x / 82 II / 240 / 241 / 240XL commands
ChangeInfo = created
END OF OUTPUT FOR JOB 21
JOB: 22
PC Time&Date: 11:54:47 03/23/2005
NE Time&Date: 12:56:22 09/15/2004
USER NAME:
User_c
COMMAND:
Create BATTERY:NAME=RACK:0/BATTERY:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 22
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 23
PC Time&Date: 11:55:04 03/23/2005
NE Time&Date: 12:56:39 09/15/2004
USER NAME:
User_c
COMMAND:
Create BATTERY:NAME=RACK:0/BATTERY:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
MO already created (-159)
END OF OUTPUT FOR JOB 23
Application Guidelines:
80
The AC/DC is necessary for the charging and supervising of the battery backup
system
When a service environment (AC/DC + Battery Backup) is built on at BS60 sites,
after replacement of BS60 with BS-240 a special setting of the attribute "associatedString" in the command "CREATE ENVABTSE" for the corresponding site input
allows the operator to indicate that the support of emergency configuration is
Id:0900d80580593f25
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BATTERY
required for battery backup unit system (Emergency Configuration after AC fault of
3rd party Service Rack)
The BATTERY can not be created for the BS-240 Compact Site as it is equipped in
the Battery Backup Rack and Energy Station Rack which are not supervised by the
SW. In the BS-240 implementation the switch into emergency configuration (due to
a battery discharge alarm) is triggered by an "ALARM STATUS" CAN bus message
that has been received from the CAN node of the AC/DC controller. In the BS-240
Compact Site the AC/DC alarm line for the AC/DC converter and for the battery must
be connected to a site input which is used as a trigger for the emergency configuration. A special setting of the attribute "associatedString" in the command "CREATE
ENVABTSE" for the corresponding site input allows the operator to indicate that the
support of emergency configuration is required for the 3rd party battery backup unit
system
The BATTERY can not be created for the BS-40II
Example of Command Execution:
Create BATTERY:NAME=RACK:0/BATTERY:0;
DELETE BATTERY
DELETE BATTERY
NAME=RACK:0..7/BATTERY:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BATTERY h
DELETE BATTERY
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the BATTERY (which provides battery backup) from the BTSE
data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 19
PC Time&Date: 11:54:44 03/23/2005
NE Time&Date: 12:56:19 09/15/2004
A50016-G5100-B333-04-7619
Id:0900d80580593f25
81
BATTERY
BS-4x / 82 II / 240 / 241 / 240XL commands
USER NAME:
User_c
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/BATTERY:0
ChangeInfo = deleted
END OF OUTPUT FOR JOB 19
JOB: 20
PC Time&Date: 11:54:44 03/23/2005
NE Time&Date: 12:56:19 09/15/2004
USER NAME:
User_c
COMMAND:
Delete BATTERY:NAME=RACK:0/BATTERY:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 20
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
BATTERY must be locked in phase 3 before deletion
The BATTERY can not be deleted for the BS-240 Compact Site as it is equipped in
the Battery Backup Rack and Energy Station Rack which are not supervised by the
SW
The BATTERY can not be deleted for the BS-40II
Example of Command Execution:
Delete BATTERY:NAME=RACK:0/BATTERY:0;
GET BATTERY
GET BATTERY
82
NAME=RACK:0..7/BATTERY:0..3 [,REQATTL=ALS, AST,
AVS, BATTCAP, OST, PRS, RELFUNCOBJ];
Id:0900d80580593f25
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BATTERY
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BATTERY h
GET BATTERY
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the BATTERY.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
BATTCAP
batteryCapacity(*5Ah)
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 5
PC Time&Date: 11:54:18 03/23/2005
NE Time&Date: 12:55:53 09/15/2004
USER NAME:
User_c
COMMAND:
Get BATTERY:NAME=RACK:0/BATTERY:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
batteryCapacity(*5Ah) = 3
operationalState = ENABLED
A50016-G5100-B333-04-7619
Id:0900d80580593f25
83
BATTERY
BS-4x / 82 II / 240 / 241 / 240XL commands
proceduralStatus = NULL
relatedFuncObjects =
END OF OUTPUT FOR JOB 5
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
The GET BATTERY command can not be issued for the BS-240 Compact Site as
the BATTERY is equipped in the Battery Backup Rack and Energy Station Rack
which are not supervised by the SW
The GET BATTERY command can not be issued for the BS-40II
Example of Command Execution:
Get BATTERY:NAME=RACK:0/BATTERY:0,REQATTL=ALS&AST&AVS&
BATTCAP&OST&PRS&RELFUNCOBJ;
GETTEST BATTERY
GETTEST BATTERY
NAME=RACK:0..7/BATTERY:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BATTERY h
GETTEST BATTERY
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the BATTERY test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 14
PC Time&Date: 11:54:31 03/23/2005
84
Id:0900d80580593f25
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BATTERY
NE Time&Date: 12:56:06 09/15/2004
USER NAME:
User_c
COMMAND:
Gettest BATTERY:NAME=RACK:0/BATTERY:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/BATTERY:0
testMonitor =
phaseId = PreliminaryTestsBattery
phaseStatus = Running
phaseId = CheckAlarmStatusBattery
phaseStatus = Waiting
phaseId = EndTestBattery
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
END OF OUTPUT FOR JOB 14
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
A50016-G5100-B333-04-7619
Id:0900d80580593f25
85
BATTERY
BS-4x / 82 II / 240 / 241 / 240XL commands
Example of Command Execution:
Gettest BATTERY:NAME=RACK:0/BATTERY:0;
LOCK BATTERY
LOCK BATTERY
NAME=RACK:0..7/BATTERY:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BATTERY h
LOCK BATTERY
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the BATTERY (which provides
battery backup).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 6
PC Time&Date: 11:54:22 03/23/2005
NE Time&Date: 12:55:57 09/15/2004
USER NAME:
User_c
COMMAND:
Lock BATTERY:NAME=RACK:0/BATTERY:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 6
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
86
Id:0900d80580593f25
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BATTERY
JOB: 7
PC Time&Date: 11:54:22 03/23/2005
NE Time&Date: 12:55:57 09/15/2004
USER NAME:
User_c
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/BATTERY:0
Administrative State = LOCKED
Notification Identifier = 263
END OF OUTPUT FOR JOB 7
Operation Failed
The specified change of administrative state has not been performed (e.g. the object is
redundant and its spare copy is disabled or already locked, a subordinate resource
cannot go into disabled state with "dependency" availability status).
Application Guidelines:
The BATTERY can not be locked for the BS-240 Compact Site as it is equipped in
the Battery Backup Rack and Energy Station Rack which are not supervised by the
SW
The BATTERY can not be locked for the BS-40II
Example of Command Execution:
Lock BATTERY:NAME=RACK:0/BATTERY:0;
PERFTEST BATTERY
PERFTEST BATTERY
NAME=RACK:0..7/BATTERY:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BATTERY h
PERFTEST BATTERY
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
A50016-G5100-B333-04-7619
Id:0900d80580593f25
87
BATTERY
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Description:
This command requests the execution of a test performed by the BATTERY (which
provides battery backup).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSEP.
JOB: 9
PC Time&Date: 11:54:26 03/23/2005
NE Time&Date: 12:56:01 09/15/2004
USER NAME:
User_c
COMMAND:
Perftest BATTERY:NAME=RACK:0/BATTERY:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/BATTERY:0
tO = BTSETEST:2
END OF OUTPUT FOR JOB 9
JOB: 10
PC Time&Date: 11:54:26 03/23/2005
NE Time&Date: 12:56:01 09/15/2004
USER NAME:
User_c
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:2
ChangeInfo = created
88
Id:0900d80580593f25
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BATTERY
END OF OUTPUT FOR JOB 10
JOB: 11
PC Time&Date: 11:54:26 03/23/2005
NE Time&Date: 12:56:01 09/15/2004
USER NAME:
User_c
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/BATTERY:0
Operational State = ENABLED
Availability Status = NULL_value
Notification Identifier = 267
END OF OUTPUT FOR JOB 11
JOB: 12
PC Time&Date: 11:54:26 03/23/2005
NE Time&Date: 12:56:01 09/15/2004
USER NAME:
User_c
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:2
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/BATTERY:0
executedPhases =
PreliminaryTestsBattery
CheckAlarmStatusBattery
EndTestBattery
A50016-G5100-B333-04-7619
Id:0900d80580593f25
89
BATTERY
BS-4x / 82 II / 240 / 241 / 240XL commands
END OF OUTPUT FOR JOB 12
JOB: 13
PC Time&Date: 11:54:26 03/23/2005
NE Time&Date: 12:56:01 09/15/2004
USER NAME:
User_c
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:2
ChangeInfo = deleted
END OF OUTPUT FOR JOB 13
The test results will be displayed at the end of the test phases.
Result TEST:
name =
TEST:<n>
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
90
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
Id:0900d80580593f25
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BATTERY
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: Message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
In phase 3 MO must be locked previous to the command execution
Example of Command Execution:
Perftest BATTERY:NAME=RACK:0/BATTERY:0;
STOPTEST BATTERY
STOPTEST BATTERY
NAME=RACK:0..7/BATTERY:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BATTERY h
STOPTEST BATTERY
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
A50016-G5100-B333-04-7619
Id:0900d80580593f25
91
BATTERY
BS-4x / 82 II / 240 / 241 / 240XL commands
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
...
.
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
phaseId =
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
Application Guidelines:
None
Example of Command Execution:
Stoptest BATTER.Y:NAME=RACK:0/BATTERY:0;
UNLOCK BATTERY
UNLOCK BATTERY
NAME=RACK:0..7/BATTERY:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BATTERY h
UNLOCK BATTERY
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the BATTERY (which provides
battery backup).
92
Id:0900d80580593f25
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BATTERY
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 15
PC Time&Date: 11:54:35 03/23/2005
NE Time&Date: 12:56:10 09/15/2004
USER NAME:
User_c
COMMAND:
Unlock BATTERY:NAME=RACK:0/BATTERY:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 15
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 16
PC Time&Date: 11:54:35 03/23/2005
NE Time&Date: 12:56:10 09/15/2004
USER NAME:
User_c
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/BATTERY:0
Administrative State = UNLOCKED
Notification Identifier = 268
A50016-G5100-B333-04-7619
Id:0900d80580593f25
93
BATTERY
BS-4x / 82 II / 240 / 241 / 240XL commands
END OF OUTPUT FOR JOB 16
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
The BATTERY can not be unlocked for the BS-240 Compact Site as it is equipped
in the Battery Backup Rack and Energy Station Rack which are not supervised by
the SW
The BATTERY can not be unlocked for the BS-40II
Example of Command Execution:
Unlock BATTERY:NAME=RACK:0/BATTERY:0;
94
Id:0900d80580593f25
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BCOM
BCOM
The BCOM (Combining Module) is an equipment object that represents the combining
module supporting up to 6 TRX, all within the same frequency band. The BCOM has no
CAN bus interface and therefore cannot provide the remote inventory data onboard.
New BCOM element shall be handled via IDF editor from LMT. No ACT-C is supported.
MDUX (a small BCOM 6:6) and HYBRID6 can replace FDUAMCOs. MDUX can fit into
2 adjacent ACOM slots of BTSplus mainline rack. If more than 6 transceivers are
required, the HYBRID6 module, containing 6 hybrids and isolators, has to be additionally equipped. This module fits either in a BCOM slot (along with a MDUX) or in an
ACOM- respectively MUCO-slot of the BTSplus mainline rack.
The alarm interface of the MDUX is identical and fully compatible to the BCOM, while
the HYBRID6 is a completely passive module with only RF interfaces. It is therefore not
visible for the software.
The 6:6 combining of the MDUX allows single rack cell configurations which cannot be
supported with the existing combining equipment. With 2 MDUX equipped in a single
BS240 II rack a 2/2/2 dual band configuration becomes possible.
All inventory units of the optional Siemens Service Rack are nob_RIUs which have to be
registered via LMT and IDF editor.
g BCOM command is valid only for BS240 and BS240XL.
The configurations BCOM (MDUX) + HYBRID6 +COAMCO are possible.
The maximum number of carrier unit ports, which are connected to the RX outputs of an
MDUX submodule is:
4 for MDUX only equipped
8 for MDUX and COAMCO equipped.
The maximum number of carrier unit ports which are either directly or via HYBRID6 connected to the TX input of an MDUX submodule is:
1 for MDUX without HYBRID6 equipped
2 for MDUX with HYBRID6 equipped
4 for MDUX with HYBRID6 and COAMCO equipped
CREATE BCOM
CREATE BCOM
NAME=RACK:0..7/BCOM:0..1 [,ANT<x>CELLNO=]
[,ANT<x>SCNRX=] ,ACONN= [,FBAND=] [,BCOMTYPE=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h
CREATE BCOM
A50016-G5100-B333-04-7619
Id:0900d80580593f27
95
BCOM
BS-4x / 82 II / 240 / 241 / 240XL commands
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command is used to create the instances 0 and 1 of BCOM object.
In this CREATE command cell number, an alarm connector or frequency band of Bcom
can be specified.
Furthermore SetWiringRx BCOM and SetWiringTx BCOM commands have to be used
to specify the wiring data. Alarm connector parameter is mandatory at the creation of
BCOM.
Long Names:
NAME
Address of the managed object
ANT<x>CELLNO
ANT<x>SCNRX
ant<x>CellNumber
ant<x>SecondCellNumberRx
ACONN
alarmConnector
FBAND
frequencyBand
BCOMTYPE
bcomType
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of create
command is the following:
Create BCOM:1
JOB: 301
PC Time&Date: 27.02.2008 12:47:48 +01:00
NE Time&Date: 01.01.1990 00:12:06 +00:00
USER NAME:
User_d
SW RELEASE:
01-04-19-01-06-00_08-02-13
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/BCOM:1
ChangeInfo = created
END OF OUTPUT FOR JOB 301
96
Id:0900d80580593f27
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BCOM
Binary Command
02 00 01 01
Binary Response
0d 00 80 00 02 12 00 7f ab 25 00 01 1f 01 00
JOB: 302
PC Time&Date: 27.02.2008 12:47:48 +01:00
NE Time&Date: 01.01.1990 00:12:06 +00:00
USER NAME:
User_d
COMMAND:
Create
BCOM:NAME=RACK:0/BCOM:1,ACONN=ENVA8,BCOMTYPE=SixToSixMDUX,FBAND=Gsm850,ANT0CELLNO=1,ANT0SCNRX=1;
SW RELEASE:
01-04-19-01-06-00_08-02-13
COMMAND RESULT: Operation successful
ant0CellNumber = 1
ant0SecondCellNumberRx = 1
alarmConnector = ENVA8
frequencyBand = Gsm850
bcomType = SixToSixMDUX
END OF OUTPUT FOR JOB 302
A50016-G5100-B333-04-7619
Id:0900d80580593f27
97
BCOM
BS-4x / 82 II / 240 / 241 / 240XL commands
Binary Command
19 00 80 ff 12 02 81 a9 ab 25 00 01 46 01 01 4c 01 01 1e 01
08 71 01 00 70 01 02
Binary Response
19 00 80 00 02 12 01 aa ab 25 00 01 46 01 01 4c 01 01 1e 01
08 71 01 00 70 01 02
Operation Failed
JOB: 287
PC Time&Date: 27.02.2008 12:44:29 +01:00
NE Time&Date: 01.01.1990 00:08:47 +00:00
USER NAME:
User_d
COMMAND:
Create
BCOM:NAME=RACK:0/BCOM:0,ACONN=ENVA3,ANT0CELLNO=0;
SW RELEASE:
01-04-19-01-06-00_08-02-13
COMMAND RESULT: Operation failed
ant0CellNumber = 0
alarmConnector = ENVA3
Message cannot be performed (-17)
END OF OUTPUT FOR JOB 287
Binary Command
10 00 80 ff 12 02 81 a9 ab 25 00 00 46 01 00 1e 01 03
98
Id:0900d80580593f27
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BCOM
Binary Response
11 00 80 00 02 12 01 ab ab 25 00 00 46 01 00 1e 01 03 11
Application Guidelines:
After the CREATE command, commands SetWiringRx BCOM and SetWiringTx BCOM
must be issued to specify antenna combiner wiring.
Creation of BCOM:i is rejected if DUAMCO:(2i) or DUAMCO:(2i+1) is created.
The creation of a BCOM instance is rejected if a DUVSWR or DULNA instance has been
created for at least one of the assigned ACOM slots.
The creation of a BCOM instance is rejected if the ACTC alarm connector is already
used by an ENVABTSE instance.
The creation of a BCOM instance shall be rejected if the ACTC alarm connector is used
by already existing BCOM instance.
SixToSixMDUX, TwelveToSixMDUX, TwelveToSixCOAMO are allowed wiring
combinations for BcomType attribute in the CREATE BCOM command on BTSPlus
Mainline, SixtoSix and TwelvetoSix options in the CREATE BCOM command are
rejected by BTS software.
Example of Command Execution:
Create BCOM:NAME=RACK:0/BCOM:1, ANT0CELLNO=0, ACONN=ENVA0,
FBAND=GSM900, BCOMTYPE=NotSet;
DELETE BCOM
DELETE BCOM
NAME=RACK:0..7/BCOM:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h
DELETE BCOM
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command is used to delete BCOM.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
A50016-G5100-B333-04-7619
Id:0900d80580593f27
99
BCOM
BS-4x / 82 II / 240 / 241 / 240XL commands
Delete BCOM:1
JOB: 6179
PC Time&Date: 31.01.2007 16:25:51 +01:00
NE Time&Date: 31.01.2007 17:25:20 +01:00
USER NAME:
User_d
COMMAND:
Delete BCOM:NAME=RACK:0/BCOM:1;
SW RELEASE:
01-04-18-06-13-04_07-01-26
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 6179
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Delete BCOM:NAME=RACK:0/BCOM:1;
GET BCOM
GET BCOM
NAME=RACK:0..7/BCOM:0..1 [,REQATTL=ALS, AST, AVS,
OST, PRS, RELFUNCOBJ, ANT<x>CELLNO,
ANT<x>SCNRX, ACONN, FBAND, BCOMTYPE];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h
GET BCOM
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the BCOM except the wiring data attributes.
Long Names:
100
NAME
Address of the managed object
REQATTL
Required attribute list
Id:0900d80580593f27
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BCOM
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
ANT<x>CELLNO
ANT<x>SCNRX
ant<x>CellNumber
ant<x>SecondCellNumberRx
ACONN
alarmConnector
FBAND
frequencyBand
BCOMTYPE
bcomType
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 26
PC Time&Date: 12:03:04 03/24/2005
NE Time&Date: 00:02:31 11/29/2004
USER NAME: User_d
COMMAND: Get BCOM:NAME=RACK:0/BCOM:0;
SW RELEASE: 01-04-18-01- 26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CRITICAL
administrativeState = Unlocked
availabilityStatus = Failed
ant<x>CellNumber = 2
ant<x>SecondCellNumberRx = 2
aconn=ENVA0
frequencyBand = Gsm900
relatedFuncObjects =
operationalState = DISABLED
proceduralStatus = NULL
END OF OUTPUT FOR JOB 26
Operation Failed
A50016-G5100-B333-04-7619
Id:0900d80580593f27
101
BCOM
BS-4x / 82 II / 240 / 241 / 240XL commands
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
None.
Example of Command Execution:
BCOM:NAME=RACK:0/BCOM:0,REQATTL=ALS&AST&AVS&ANT<x>CELLNO&ANT
<x>SCNRX&OST&PRS&RELFUNCOBJ&ACONN&FBAND&BCOMTYPE;
GETRELATIONSHIP BCOM
GETRELATIONSHIP
BCOM
NAME=RACK:0..7/BCOM:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h
GETRELATIONSHIP BCOM
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command is used to retrieve the functional relationship information for the selected
HMO (Hardwar Managed Object); the relationship information consists of all FMOs
(Functional Managed Object) using the HMO service.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of getrelationship
command is the following:
JOB: 1227221
PC Time&Date: 01/29/2007 14:44:27 +01:00
NE Time&Date: 01/29/2007 15:44:11 +01:00
USER NAME:
User_d
COMMAND:
Getrelationship BCOM:NAME=RACK:0/BCOM:0;
SW RELEASE:
01-04-18-06-13-04_07-01-26
COMMAND RESULT: Operation successful
102
Id:0900d80580593f27
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BCOM
relatedFuncObjects =
FMO = BTS:0/TRX:4
FMO = BTS:0/TRX:6
FMO = BTS:0/TRX:8
FMO = BTS:0/TRX:10
FMO = BTS:0/TRX:9
FMO = BTS:0/TRX:2
END OF OUTPUT FOR JOB 1227221
JOB: 1227222
PC Time&Date: 01/29/2007 14:44:27 +01:00
NE Time&Date: 01/29/2007 15:44:11 +01:00
USER NAME:
User_d
COMMAND:
Getrelationship BCOM:NAME=RACK:0/BCOM:1;
SW RELEASE:
01-04-18-06-13-04_07-01-26
COMMAND RESULT: Operation successful
relatedFuncObjects =
FMO = BTS:0/TRX:1
FMO = BTS:0/TRX:3
FMO = BTS:0/TRX:5
FMO = BTS:0/TRX:7
FMO = BTS:0/TRX:11
FMO = BTS:0/TRX:0
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Getrelationship BCOM:NAME=RACK:0/BCOM:0;
A50016-G5100-B333-04-7619
Id:0900d80580593f27
103
BCOM
BS-4x / 82 II / 240 / 241 / 240XL commands
GETTEST BCOM
GETTEST BCOM
NAME=RACK:0..7/BCOM:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h
GETTEST BCOM
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the BCOM test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 25
PC Time&Date: 12:01:44 03/24/2005
NE Time&Date: 00:01:11 11/29/2004
USER NAME:
User_d
COMMAND:
Gettest BCOM:NAME=RACK:0/BCOM:0;
SW RELEASE:
01-04-17-06-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/BCOM:0
testMonitor =
phaseId = PreliminaryTestsBcom
phaseStatus = Running
phaseId = CheckAlarmStatusBcom
phaseStatus = Waiting
phaseId = EndTestBcom
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
104
Id:0900d80580593f27
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BCOM
END OF OUTPUT FOR JOB 25
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest BCOM:NAME=RACK:0/BCOM:0,REQATTL=MORT&TESTMON&TESTOUT&
TESTST;
GETWIRINGRX BCOM
GETWIRINGRX BCOM NAME=RACK:0..7/BCOM:0..1 ,REQATTL=ANT<x>WDRX;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h
GETWIRINGRX BCOM
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the wiring data attributes of the BCOM for RX path.
It is applicable only on: BS240, BS240II, BS240XL, BS240XLII, BS241, BS241 II.
A50016-G5100-B333-04-7619
Id:0900d80580593f27
105
BCOM
BS-4x / 82 II / 240 / 241 / 240XL commands
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ANT<x>WDRX
ant<x>WiringDataRx
System Responses:
Operation Completed
A message indicates the result of the operation. An example of getWiringRx command
is the following:
********** Message 60 **********
JOB: 60
PC Time&Date: 17.12.2007 10:20:51 +01:00
NE Time&Date: 01.01.1990 00:07:40 +00:00
USER NAME: User_d
COMMAND: GetWiringRx
BCOM:NAME=RACK:0/BCOM:0,REQATTL=ANT0WDRX&ANT1WDRX&ANT2WDRX
&ANT3WDRX&ANT4WDRX&ANT5WDRX;
SW RELEASE: 01-04-18-01-18-01_07-12-14
COMMAND RESULT:Operation successful
ant0WiringDataRx = CU0N & CU1N & CU2N & CU3N & FCUMAIN5N & FCUMAIN5N1
& FCUMAIN6N & FCUMAIN6N1
ant1WiringDataRx = NULL
ant2WiringDataRx = NULL
ant3WiringDataRx = NULL
ant4WiringDataRx = NULL
ant5WiringDataRx = NULL
END OF OUTPUT FOR JOB 60
Operation Failed
The GETWIRINGRX command has not been successfully executed. A general NACK
will indicate possible errors or a specific NACK strictly related to the single command is
possible.
Application Guidelines:
None.
Example of Command Execution:
GetWiringRxBCOM:NAME=RACK:0/BCOM:0,REQATTL=
ANT0WDRX&ANT1WDRX&ANT2WDRX&ANT3WDRX&ANT4WDRX&ANT5WDRX;
106
Id:0900d80580593f27
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BCOM
GETWIRINGTX BCOM
GETWIRINGTX BCOM
NAME=RACK:0..7/BCOM:0..1 ,REQATTL=ANT<x>WDTX;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h
GETWIRINGTX BCOM
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the wiring data attributes of the BCOM for TX path.
It is applicable only on: BS240, BS240II, BS240XL, BS240XLII, BS241, BS241 II.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ANT<x>WDTX
ant<x>WiringDataTx
System Responses:
Operation Completed
A message indicates the result of the operation. An example of getWiringTx command
is the following:
********** Message 61 **********
JOB: 61
PC Time&Date: 17.12.2007 10:20:59 +01:00
NE Time&Date: 01.01.1990 00:07:48 +00:00
USER NAME: User_d
COMMAND: GetWiringTx
BCOM:NAME=RACK:0/BCOM:0,REQATTL=ANT0WDTX&ANT1WDTX&ANT2WDTX
&ANT3WDTX&ANT4WDTX&ANT5WDTX;
SW RELEASE: 01-04-18-01-18-01_07-12-14
COMMAND RESULT:Operation successful
ant0WiringDataTx = CU0 & CU1 & CU2 & CU3
ant1WiringDataTx = NULL
ant2WiringDataTx = NULL
A50016-G5100-B333-04-7619
Id:0900d80580593f27
107
BCOM
BS-4x / 82 II / 240 / 241 / 240XL commands
ant3WiringDataTx = NULL
ant4WiringDataTx = NULL
ant5WiringDataTx = NULL
END OF OUTPUT FOR JOB 61
Operation Failed
The GETWIRINGTX command has not been successfully executed. A general NACK
will indicate possible errors or a specific NACK strictly related to the single command is
possible.
Application Guidelines:
None.
Example of Command Execution:
GetWiringTx
BCOM:NAME=RACK:0/BCOM:0,REQATTL=ANT0WDTX&ANT1WDTX&ANT2WDTX
&ANT3WDTX&ANT4WDTX&ANT5WDTX;
LOCK BCOM
LOCK BCOM
NAME=RACK:0..7/BCOM:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h
LOCK BCOM
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the BCOM.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 27
PC Time&Date: 12:03:17 03/24/2005
NE Time&Date: 00:02:44 11/29/2004
USER NAME:
108
User_d
Id:0900d80580593f27
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COMMAND:
SW RELEASE:
BCOM
Lock BCOM:NAME=RACK:0/BCOM:0;
01-04-17-06-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 27
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 28
PC Time&Date: 12:03:17 03/24/2005
NE Time&Date: 00:02:44 11/29/2004
USER NAME:
User_d
SW RELEASE:
01-04-17-06-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/BCOM:0
Administrative State = LOCKED
Notification Identifier = 22
END OF OUTPUT FOR JOB 28
Operation Failed
The specified change of administrative state has not been performed (e.g. the object is
redundant and its spare copy is disabled or already locked, a subordinate resource
cannot go into disabled state with "dependency" availability status).
Application Guidelines:
None.
Example of Command Execution:
Lock BCOM:NAME=RACK:0/BCOM:0;
A50016-G5100-B333-04-7619
Id:0900d80580593f27
109
BCOM
BS-4x / 82 II / 240 / 241 / 240XL commands
PERFTEST BCOM
PERFTEST BCOM
NAME=RACK:0..7/BCOM:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h
PERFTEST BCOM
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in BCOM.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object.
JOB: 30
PC Time&Date: 12:03:25 03/24/2005
NE Time&Date: 00:02:52 11/29/2004
USER NAME:
User_d
COMMAND:
Perftest BCOM:NAME=RACK:0/BCOM:0;
SW RELEASE:
01-04-17-06-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/BCOM:0
tO = BTSETEST:1
END OF OUTPUT FOR JOB 30
JOB: 31
PC Time&Date: 12:03:25 03/24/2005
NE Time&Date: 00:02:52 11/29/2004
USER NAME:
110
User_d
Id:0900d80580593f27
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
SW RELEASE:
BCOM
01-04-17-06-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:1
ChangeInfo = created
END OF OUTPUT FOR JOB 31
JOB: 32
PC Time&Date: 12:03:25 03/24/2005
NE Time&Date: 00:02:52 11/29/2004
USER NAME:
User_d
SW RELEASE:
01-04-17-06-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/BCOM:0
Availability Status = Failed
Notification Identifier = 27
END OF OUTPUT FOR JOB 32
JOB: 33
PC Time&Date: 12:03:25 03/24/2005
NE Time&Date: 00:02:52 11/29/2004
USER NAME:
User_d
SW RELEASE:
01-04-17-06-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:1
testOutcome = FAILED
A50016-G5100-B333-04-7619
Id:0900d80580593f27
111
BCOM
BS-4x / 82 II / 240 / 241 / 240XL commands
testTermination = Normal
MOT = RACK:0/BCOM:0
executedPhases =
PreliminaryTestsBcom
EndTestBcom
failedPhases =
phaseId = CheckAlarmStatusBcom
additionalWords =
H`0001
H`0000
H`0000
H`0000
H`0000
H`0000
H`0000
H`0000
proposedRepairActions =
#0#
#0#
#0#
#0#
END OF OUTPUT FOR JOB 33
JOB: 34
PC Time&Date: 12:03:25 03/24/2005
NE Time&Date: 00:02:52 11/29/2004
USER NAME:
User_d
SW RELEASE:
01-04-17-06-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:1
ChangeInfo = deleted
END OF OUTPUT FOR JOB 34
112
Id:0900d80580593f27
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BCOM
The test results will be displayed at the end of the test phases.
Result TEST:
name =
TEST:<n>
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: Message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
None.
A50016-G5100-B333-04-7619
Id:0900d80580593f27
113
BCOM
BS-4x / 82 II / 240 / 241 / 240XL commands
Example of Command Execution:
Perftest BCOM:NAME=RACK:0/BCOM:0;
SET BCOM
SET BCOM
NAME=RACK:0..7/BCOM:0..1 [,ANT<x>CELLNO=]
[,ANT<x>SCNRX=] [,ACONN=] [,FBAND=] [,BCOMTYPE=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h
SET BCOM
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command allows modification of the attributes of the BCOM. For setting of wiring
data attributes of BCOM the commands: SetWiringRx BCOM and SetWiringTx BCOM
must be used.
Long Names:
NAME
Address of the managed object
ANT<x>CELLNO
ANT<x>SCNRX
ant<x>CellNumber
ant<x>SecondCellNumberRx
ACONN
alarmConnector
FBAND
frequencyBand
BCOMTYPE
bcomType
System Responses:
Operation Completed
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
JOB: 46
PC Time&Date: 12:07:06 03/24/2005
NE Time&Date: 00:06:33 11/29/2004
USER NAME:
User_d
COMMAND:
Set BCOM:NAME=RACK:0/BCOM:0;
SW RELEASE:
01-04-17-06-26-51_05-02-23
COMMAND RESULT: Operation successful
114
Id:0900d80580593f27
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BCOM
END OF OUTPUT FOR JOB 46
Operation Failed
The specified attributes have not been set. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible.
Application Guidelines:
The existing state and status attributes shall be assigned to the attributes group
STATES
<x> = 0 .. 5
With the SET BCOM command it is possible to 'unset' the parameters setting the
value 'NULL', e.g. the cell parameters. To 'unset' the parameters first you must use
BCOM SetWiringTx& Set WiringRx commands, then Set command (to unset cell
assignment).
Example:
SetWiringTX BCOM:NAME=RACK:0/BCOM:0, ANT0WDTX=<NULL>,
ANT1WDTX=<NULL>,
ANT2WDTX=<NULL>, ANT3WDTX=<NULL>,
,ANT4WDTX=<NULL>,,ANT5WDTX=<NULL>;
;
SetWiringRX BCOM:NAME=RACK:0/BCOM:0, ANT0WDRX=<NULL>,
ANT1WDRX=<NULL>,
ANT2WDRX=<NULL>, ANT3WDRX=<NULL>,
,ANT4WDRX=<NULL>,,ANT5WDRX=<NULL>;
;
Set BCOM:NAME=RACK:0/BCOM:0,ANT0CELLNO=<NULL>,
ANT0SCNRX=<NULL>,ANT1CELLNO=<NULL>,ANT1SCNRX=<NULL>,
ANT2CELLNO=<NULL>,ANT2SCNRX=<NULL>,ANT3CELLNO=<NULL>,
ANT3SCNRX=<NULL>,ANT4CELLNO=<NULL>,ANT4SCNRX=<NULL>,
ANT5CELLNO=<NULL>,ANT5SCNRX=<NULL>;
Example of Command Execution:
Set BCOM:NAME=RACK:0/BCOM:0,ant<x>CellNumber=2, ant<x>SecondCellNumberRx=2, ACONN=ENVA0,Fband=Gsm900,BCOMTYPE=NotSet;
SETWIRINGRX BCOM
SETWIRINGRX BCOM
A50016-G5100-B333-04-7619
NAME=RACK:0..7/BCOM:0..1 [,ANT<x>WDRX=];
Id:0900d80580593f27
115
BCOM
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h
SETWIRINGRX BCOM
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command allows modification of the wiring data attributes of the BCOM for RX path.
This command shall be used after creation of BCOM object. Up to 8 wiring destinations
can be set allowing to define also the configuration MDUX + HYBRID6 +COAMCO.
This is valid only for: BS240, BS240II, BS240XL, BS240XLII, BS241, BS241 II.
Long Names:
NAME
Address of the managed object
ANT<x>WDRX
ant<x>WiringDataRx
System Responses:
Operation Completed
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of SetWiringRx
command is the following:
JOB: 56
PC Time&Date: 17.12.2007 10:19:03 +01:00
NE Time&Date: 01.01.1990 00:05:52 +00:00
USER NAME: User_d
COMMAND: SetWiringRx
BCOM:NAME=RACK:0/BCOM:0,ANT0WDRX=CU0N&CU1N&CU2N&CU3N&FCUMA
IN5N&FCUMAIN5N1&FCUMAIN6N&FCUMAIN6N1;
SW RELEASE: 01-04-18-01-18-01_07-12-14
COMMAND RESULT:Operation successful
ant0WiringDataRx = CU0N & CU1N & CU2N & CU3N & FCUMAIN5N &
FCUMAIN5N1& FCUMAIN6N & FCUMAIN6N1
END OF OUTPUT FOR JOB 56
Operation Failed
116
Id:0900d80580593f27
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BCOM
In addition to the general NACK causes, a specific NACK cause, which indicates that
the command is inconsistent with the physical configuration, is possible.
Application Guidelines:
The 1 attribute for each antenna shall be assigned to 6 separate groups 'ANTENNA
<x>'
<x> = 0 .. 5
With the SETWIRINGRX BCOM command it is possible to 'unset' the parameters
setting the value 'NULL', for wiringDataRx attributes and with the SETWIRINGTX
BCOM command it is possible to 'unset' the parameters setting the value 'NULL' and
finally by using a command "SET BCOM" to 'unset' the cell parameters
Example:
SetWiringRx
BCOM:NAME=RACK:0/BCOM:0,ANT0WDRX=<NULL>,
ANT1WDRX=<NULL>,ANT2WDRX=<NULL>,
ANT3WDRX=<NULL>, ANT4WDRX=<NULL>, ANT5WDRX=<NULL>,
;
SetWiringTx
BCOM:NAME=RACK:0/BCOM:0,ANT0WDTX=<NULL>,
ANT1WDTX=<NULL>,ANT2WDTX=<NULL>,
ANT3WDTX=<NULL>, ANT4WDTX=<NULL>, ANT5WDTX=<NULL>,
Set BCOM:NAME=RACK:0/BCOM:0,ANT0CELLNO=<NULL>,
ANT0SCNRX=<NULL>,ANT1CELLNO=<NULL>,ANT1SCNRX=<NULL>,
ANT2CELLNO=<NULL>,ANT2SCNRX=<NULL>,ANT3CELLNO=<NULL>,
ANT3SCNRX=<NULL>,ANT4CELLNO=<NULL>,ANT4SCNRX=<NULL>,
ANT5CELLNO=<NULL>,ANT5SCNRX=<NULL>;
Example of Command Execution:
SetWiringRx BCOM:NAME=RACK:0/BCOM:0,
ANT0WDRX=CU0N&CU1N&CU2N&CU3N&FCUMAIN5N&FCUMAIN5N1&FCUMAIN
6N&FCUMAIN6N1;
g The wiring data of cell configurations with MDUX, HYBRID6 and COAMCO are
neither completely visible nor configurable via RC, SetWiringRx BCOM command
not forseen for RC, when to display the wiring for this configuration always max 2
CUs.TX wiring destinations and max 4 CUs Rx wiring destinations for each corresponding BCOM port is displayed even if 4 CUs for TX path and 8 CUs Rx path are
wired.
A50016-G5100-B333-04-7619
Id:0900d80580593f27
117
BCOM
BS-4x / 82 II / 240 / 241 / 240XL commands
SETWIRINGTX BCOM
SETWIRINGTX BCOM
NAME=RACK:0..7/BCOM:0..1 [,ANT<x>WDTX=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h
SETWIRINGTX BCOM
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command allows modification of the wiring data attributes of the BCOM for TX path.
This command shall be used after creation of BCOM object. Up to 4 wiring destinations
can be set allowing to define also the configuration MDUX + HYBRID6 +COAMCO.
This is valid only for: BS240, BS240II, BS240XL, BS240XLII, BS241, BS241 II.
Long Names:
NAME
Address of the managed object
ANT<x>WDTX
ant<x>WiringDataTx
System Responses:
Operation Completed
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of SetWiringTx
command is the following:
JOB: 53
PC Time&Date: 17.12.2007 10:17:53 +01:00
NE Time&Date: 01.01.1990 00:04:42 +00:00
USER NAME: User_d
COMMAND: SetWiringTx
BCOM:NAME=RACK:0/BCOM:0,ANT0WDTX=CU0&CU1&CU2&CU3;
SW RELEASE: 01-04-18-01-18-01_07-12-14
COMMAND RESULT:Operation successful
ant0WiringDataTx = CU0 & CU1 & CU2 & CU3
END OF OUTPUT FOR JOB 53
Operation Failed
None.
118
Id:0900d80580593f27
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BCOM
Application Guidelines:
The 1 attribute for each antenna shall be assigned to 6 separate groups 'ANTENNA
<x>'.
<x> = 0 .. 5
With the SETWIRINGTX BCOM command it is possible to 'unset' the parameters
setting the value 'NULL', for wiringDataTx attributes and with the SETWIRINGRX
BCOM command it is possible to 'unset' the parameters setting the value 'NULL' and
finally by using a command "SET BCOM" to 'unset' the cell parameters.
Example:
SetWiringTx
BCOM:NAME=RACK:0/BCOM:0,ANT0WDTX=<NULL>,
ANT1WDTX=<NULL>,ANT2WDTX=<NULL>,
ANT3WDTX=<NULL>, ANT4WDTX=<NULL>, ANT5WDTX=<NULL>,
SetWiringRx
BCOM:NAME=RACK:0/BCOM:0,ANT0WDRX=<NULL>,
ANT1WDRX=<NULL>,ANT2WDRX=<NULL>,
ANT3WDRX=<NULL>, ANT4WDRX=<NULL>, ANT5WDRX=<NULL>,;
Set BCOM:NAME=RACK:0/BCOM:0,ANT0CELLNO=<NULL>,
ANT0SCNRX=<NULL>,ANT1CELLNO=<NULL>,ANT1SCNRX=<NULL>,
ANT2CELLNO=<NULL>,ANT2SCNRX=<NULL>,ANT3CELLNO=<NULL>,
ANT3SCNRX=<NULL>,ANT4CELLNO=<NULL>,ANT4SCNRX=<NULL>,
ANT5CELLNO=<NULL>,ANT5SCNRX=<NULL>
Example of Command Execution:
SetWiringTx BCOM:NAME=RACK:0/BCOM:0,ANT0WDTX=CU0&CU1&CU2&CU3;
g The wiring data of cell configurations with MDUX, HYBRID6 and COAMCO are
neither completely visible nor configurable via RC. SetWiringTx BCOM command is
not forseen for RC, when the wiring for this configuration is displayed always max 2
CUs.
TX wiring destinations and max 4 CUs Rx wiring destinations for each corresponding BCOM port is displayed even if 4 CUs for TX path and 8 CUs Rx path are wired.
STOPTEST BCOM
STOPTEST BCOM
NAME=RACK:0..7/BCOM:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h
STOPTEST BCOM
Applicability:
Phase 2 and Phase 3.
A50016-G5100-B333-04-7619
Id:0900d80580593f27
119
BCOM
BS-4x / 82 II / 240 / 241 / 240XL commands
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
...
.
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
Application Guidelines:
None.
Example of Command Execution:
Stoptest BCOM:NAME=RACK:0/BCOM:0;
UNLOCK BCOM
UNLOCK BCOM
120
NAME=RACK:0..7/BCOM:0..1;
Id:0900d80580593f27
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BCOM
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h BCOM h
UNLOCK BCOM
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the BCOM.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 36
PC Time&Date: 12:03:45 03/24/2005
NE Time&Date: 00:03:12 11/29/2004
USER NAME:
User_d
COMMAND:
Unlock BCOM:NAME=RACK:0/BCOM:0;
SW RELEASE:
01-04-17-06-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 36
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 37
PC Time&Date: 12:03:45 03/24/2005
NE Time&Date: 00:03:12 11/29/2004
A50016-G5100-B333-04-7619
Id:0900d80580593f27
121
BCOM
BS-4x / 82 II / 240 / 241 / 240XL commands
USER NAME:
User_d
SW RELEASE:
01-04-17-06-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/BCOM:0
Administrative State = UNLOCKED
Notification Identifier = 29
END OF OUTPUT FOR JOB 37
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
None.
Example of Command Execution:
Unlock BCOM:NAME=RACK:0/BCOM:0;
122
Id:0900d80580593f27
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BPORT
BPORT
The object BPORT identifies one of the 2 PCM30/24 interfaces on the COBA and one
of the 6 PCM30/24 interfaces on the COSA. The object BPORT holds the configuration
data of one Abis port.
CREATE BPORT
CREATE BPORT
NAME=BPORT:0..7 [,BERT=] [,L1CTRLTS=] ,L1PT=
[,L1RAT=] ,LCONF= [,LIMP=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h BPORT h CREATE
BPORT
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command is used for the Handling of PCM-Line Configuration and adds the BPORT
(BTSE Port) together with its attributes to the BTSE data base. The object BPORT holds
the configuration data of one Abis port. The instance number of this object is related to
the physical Abis port number (e.g.: Instance 0 is related to the physical port 1 (OVPT),
which allows the connection of the BTSE to the Abis line1 and so on).
Long Names:
NAME
Address of the managed object
BERT
bitErrorRateThreshold
L1CTRLTS
layer1ControlTs
L1PT
layer1ProtocolType
L1RAT
layer1RemoteAlarmType
LCONF
lineConfiguration
LIMP
lineImpedance
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 42
PC Time&Date: 11:55:28 03/23/2005
NE Time&Date: 12:57:03 09/15/2004
A50016-G5100-B333-04-7619
Id:0900d805805944a2
123
BPORT
BS-4x / 82 II / 240 / 241 / 240XL commands
USER NAME:
User_e
SW RELEASE:
cessful
01-04-17-01-26-51_05-02-23 COMMAND RESULT: Operation suc-
ChangedConfigurationNotification:
name = BPORT:1
ChangeInfo = created
END OF OUTPUT FOR JOB 42
JOB: 43
PC Time&Date: 11:55:28 03/23/2005
NE Time&Date: 12:57:03 09/15/2004
USER NAME:
User_e
COMMAND:
Create BPORT:NAME=BPORT:1,L1PT=pcm30crc4,LCONF=star;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
layer1ProtocolType = pcm30crc4
lineConfiguration = star
END OF OUTPUT FOR JOB 43
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 44
PC Time&Date: 11:55:52 03/23/2005
NE Time&Date: 12:57:27 09/15/2004
USER NAME:
User_e
COMMAND:
Create BPORT:NAME=BPORT:2,L1PT=pcm30crc4,LCONF=star;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
124
Id:0900d805805944a2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BPORT
MO already created (-159)
END OF OUTPUT FOR JOB 44
Application Guidelines:
Wildcard addressing is not possible
To guarantee a correct transition of SW releases the operator must use BPort
instance 0 for O&M link
Changing or setting of layer1ProtocolType or layer1RemoteAlarm attributes means
a temporary loss of service for the whole BTSE
Layer1ControlTS must be different to the related BTSM-O&M signalling link
Layer1ControlTS (if activated) must not be used for other purposes (e.g. signalling,
traffic or cross connection and vice versa)
SpecialBitRobbing attribute is allowed only for PCM24 and means that a special bit
(bit 2) is used for signalling of a remote alarm
BPORTs (0&1, 2&3, 4&5, 6&7) form port pairs which are short-circuited during
BTSE coming up
Bport-0 is clock master for BTSE, all other Bports are slaves. Therefore, PCM line
connected to Bport-0 must arrive from different network entity
To configure a line circuit (e.g.: multidrop, loop) 2 BPort objects have to be created
by the operator. As long the 2 objects are not available all BTSEs located behind on
this circuit are not reachable. Line alarms detected by one Abis port are mapped to
the associated BPort instance
One star circuit (only one port is involved) is allowed per port pair and must be
placed on the lower port number
Creation of the second port on a port pair (in case of a multidrop/loop circuit) must
lead always to the same settings of the attributes as the first port has with the following exceptions
1) Activation of a layer1ControlTimeslot is only allowed for the first port in case of a
multidrop circuit
2) Attribute bitErrorRateThresholds can be set independently
If COBA2P8 is installed and COSA is disabled/not Installed, the BPORT:2-7 are in
Enable.null state but they cannot be used because the HW does not support them.
If COBA4P12 is installed and COSA is disabled/not Installed, the BPORT:2,3 are in
Enable.degraded state and the BPORT:4-7 are in Enable.null but they cannot be
used because the HW does not support them
g This is valid for all BTSplus except for 82II.
Example of Command Execution:
Create BPORT:NAME=BPORT:0,L1PT=pcm30crc4,LCONF=star,
BERT=E10_3-E10_3,L1CTRLTS=0-0,L1RAT=ProtocolSignalling,
A50016-G5100-B333-04-7619
Id:0900d805805944a2
125
BPORT
BS-4x / 82 II / 240 / 241 / 240XL commands
LIMP=Imp100or120Ohm;
DELETE BPORT
DELETE BPORT
NAME=BPORT:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h BPORT h DELETE
BPORT
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the BPORT (BTSE port) from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 45
PC Time&Date: 11:55:52 03/23/2005
NE Time&Date: 12:57:27 09/15/2004
USER NAME:
User_e
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
NAME=BPORT:2
ChangeInfo = deleted
END OF OUTPUT FOR JOB 45
JOB: 46
126
Id:0900d805805944a2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BPORT
PC Time&Date: 11:55:56 03/23/2005
NE Time&Date: 12:57:31 09/15/2004
USER NAME:
User_e
COMMAND:
Delete BPORT:NAME=BPORT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 46
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
Before Deletion of a BPort instance in phase 3, the object must be locked before
Deletion in phase 3 is allowed only if no TSL is assigned to BPort (XCONNECT
defined)
The BPORT 0 is one of the "Minimal Parameters" of the BTSE. If the BPORT 0 is
deleted, the entire BTSE is out of service (only Phase 2)
BPORT 0 cannot be deleted in Phase 3
Example of Command Execution:
Delete BPORT:NAME=BPORT:0;
GET BPORT
GET BPORT
NAME=BPORT:0..7 [,REQATTL=ALS, AST, AVS, BERT,
L1CTRLTS, L1PT, L1RAT, LCONF, LSIND, LIMP, OST,
PRDIRECT, PRS, RELFUNCOBJ];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h BPORT h GET
BPORT
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the PCM lines connected to the COBA (Core
Basis).
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
A50016-G5100-B333-04-7619
Id:0900d805805944a2
127
BPORT
BS-4x / 82 II / 240 / 241 / 240XL commands
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
BERT
bitErrorRateThreshold
L1CTRLTS
layer1ControlTs
L1PT
layer1ProtocolType
L1RAT
layer1RemoteAlarmType
LCONF
lineConfiguration
LSIND
lineStatusIndication
LIMP
lineImpedance
OST
operationalState
PRDIRECT
preferredDirection
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 5
PC Time&Date: 11:31:23 03/23/2005
NE Time&Date: 11:29:14 09/15/2004
USER NAME:
User_e
COMMAND:
GET BPORT:NAME=BPORT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
bitErrorRateThreshold =
lowerThreshold = E10_5
upperThreshold = E10_3
layer1ControlTs =
TSL = 0
SSL = 0
layer1ProtocolType = pcm30crc4
128
Id:0900d805805944a2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BPORT
layer1RemoteAlarmType = ProtocolSignalling
lineConfiguration = multidrop
lineStatusIndication =
remoteAlarmInd = FALSE
frameSynchronizationLoss = FALSE
CRCFailure = FALSE
noLevel = FALSE
CRCRemoteEnviroment = FALSE
BERTLowerThreshold = FALSE
BERTUpperThreshold = FALSE
promptMaintenanceAlarmInd = FALSE
lineImpedance = accDIP
operationalState = ENABLED
proceduralStatus = NULL
preferredDirection = Null
relatedFuncObjects =
END OF OUTPUT FOR JOB 5
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
None.
Example of Command Execution:
Get BPORT:NAME=BPORT:0,REQATTL=ALS&AST&AVS&BERT&
L1CTRLTS&L1RAT&L1PT&LCONF&LIMP&LSIND&OST&PRDIRECT&PRS&
RELFUNCOBJ;
LOCK BPORT
LOCK BPORT
NAME=BPORT:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h BPORT h LOCK
BPORT
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
A50016-G5100-B333-04-7619
Id:0900d805805944a2
129
BPORT
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Description:
This command changes the administrative state of the BPORT object.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 47
PC Time&Date: 11:56:00 03/23/2005
NE Time&Date: 12:57:35 09/15/2004
USER NAME:
User_e
COMMAND:
Lock BPORT:NAME=BPORT:0;
SW RELEASE:
cessful
01-04-17-01-26-51_05-02-23 COMMAND RESULT: Operation suc-
administrativeState = LOCKED
END OF OUTPUT FOR JOB 47
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 48
PC Time&Date: 11:56:22 03/23/2005
NE Time&Date: 12:57:57 09/15/2004
USER NAME:
User_e
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME=BPORT:0;
130
Id:0900d805805944a2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BPORT
Administrative State = LOCKED
Notification Identifier = 143452
END OF OUTPUT FOR JOB 48
Operation Failed
The specified change of administrative state has not been performed (e.g. the object is
redundant and its spare copy is disabled or already locked, a subordinate resource
cannot go into disabled state with "dependency" availability status).
Application Guidelines:
BPORT 0 cannot be locked in Phase 3
Example of Command Execution:
Lock BPORT:NAME=BPORT:0;
SET BPORT
SET BPORT
NAME=BPORT:0..7 [,BERT=] [,L1CTRLTS=] [,L1RAT=]
[,LCONF=] [,LIMP=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h BPORT h SET
BPORT
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command permits modification of the attributes of the BPORT (BTSE port), previously created with the (create) CREATE BPORT command. The object BPORT holds
the configuration data of one Abis port.
Long Names:
NAME
Address of the managed object
BERT
bitErrorRateThreshold
L1CTRLTS
layer1ControlTs
L1RAT
layer1RemoteAlarmType
LCONF
lineConfiguration
LIMP
lineImpedance
System Responses:
Operation Completed
The specified attribute has been set. In addition, a Changed Attribute Event Report indicates that the command has been successfully executed:
A50016-G5100-B333-04-7619
Id:0900d805805944a2
131
BPORT
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 15
PC Time&Date: 11:32:16 03/23/2005
NE Time&Date: 11:30:07 09/15/2004
USER NAME:
User_e
COMMAND:
Set BPORT:NAME=BPORT:0,BERT=E10_5-E10_3;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
bitErrorRateThreshold =
lowerThreshold = E10_5
upperThreshold = E10_3
END OF OUTPUT FOR JOB 15
Operation Failed
The specified attributes have not been set. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with physical
configuration, is possible.
Application Guidelines:
The layer1ControlTS attribute is applicable only for the line configuration "Loop"
Changing or setting of layer1RemoteAlarmType attribute means a temporary loss of
service for the whole BTSE
Layer1ControlTS must be different to the related BTSM-O&M signalling link
SpecialBitRobbing attribute is allowed only for PCM24 and means that a special bit
(bit 2) is used for signalling of a remote alarm
Example of Command Execution:
Set BPORT:NAME=BPORT:0,BERT=E10_3-E10_3,L1CTRLTS=0-0,
L1RAT=ProtocolSignalling,LCONF=star,LIMP=Imp100or120Ohm;
UNLOCK BPORT
UNLOCK BPORT
NAME=BPORT:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h BPORT h UNLOCK
BPORT
Applicability:
Phase 2 and Phase 3.
132
Id:0900d805805944a2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BPORT
Visibility level: 1.
Command Description:
This command changes the administrative state of the BPORT (BTSE port).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 185
PC Time&Date: 12:06:51 03/23/2005
NE Time&Date: 13:08:26 09/15/2004
USER NAME:
User_e
COMMAND:
UNLOCK BPORT:NAME=BPORT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = UNLOCKED
END OF OUTPUT FOR JOB 185
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 186
PC Time&Date: 12:06:51 03/23/2005
NE Time&Date: 13:08:26 09/15/2004
USER NAME:
User_e
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
A50016-G5100-B333-04-7619
Id:0900d805805944a2
133
BPORT
BS-4x / 82 II / 240 / 241 / 240XL commands
NAME=BPORT:0;
Administrative State = UNLOCKED
Notification Identifier = 135872
END OF OUTPUT FOR JOB 186
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
None.
Example of Command Execution:
Unlock BPORT:NAME=BPORT:0;
134
Id:0900d805805944a2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTS
BTS
The BTS object locates a cell connected to BSC. Logically it represents all the information related to the cell and to its configuration.
GET BTS
GET BTS
NAME=BTS:0..11 [,REQATTL=ACBQPFF, ACBQPMAX,
ACEFLFF, ACFERMAX, ACLNKTYP, ACMINEFLDMA,
ACMAXEFLDMA, ACPER, AMRLKAT, AMRLKATWFS,
ANTHOPMOD, ANTHOPP, ANTHOPST, ARFACCHACMDF, ASCICIPH, AST, AVS, BCCHFREQ, BSIC,
BTSISHOP, BURNOFFS, SYSID, CELLTYPE, CUCONF,
DTMHOMTIMER, EAC, EANTHOP, EEOTD, EEXCDIST,
ERFACCHALPDMF, ERFACCHCMDF, ERSACCHDL,
ERSACCHUL, ETOP, ETXDIVTS, EXCDIST, FACCHQ,
FACHBT, FRANOFFS, GSMTIME, HOPMODE, INTAVEPAR, INTCLASS, INTLVBND, MSTXPMAX, MSTXPMAXC,
NEPTTREP, NTWTYPE, NY1, NY2, OST, PCCCHLDI,
PNOFACCH, PWROUT, RACHBT, RACHLAS, RELEQUIPOBJ, REPTYP, RFRSINDP, RSACCHRXLDL, RSACCHRXLUL, RSACCHTODL, RSACCHTOUL,
RXSIGLEVADJ, RXSIGLEVADJC, RXSWCURSET, SWBCAPABILITY, SWBSERVSTATE, T3105, T3151,
TCCCHLDI];
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h BTS h GET BTS
Applicability:
Phase 3.
Visibility level: 0.
Command Description:
This command displays the cell-specific global attributes of a chosen BTS.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ACBQPFF
acBQPFgtFac
ACBQPMAX
acBQPMax(%)
ACEFLFF
acEFLFgtFac
ACFERMAX
acFERMax(%)
ACLNKTYP
acLinkType
ACMINEFLDMA
ACMAXEFLDMA
ACPER
A50016-G5100-B333-04-7619
acMinEFLDMA(%)
acMaxEFLDMA(%)
acPeriod
Id:0900d805805944a4
135
BTS
BS-4x / 82 II / 240 / 241 / 240XL commands
AMRLKAT
aMRLinkAdapTuning
AMRLKATWFS
aMRLinkAdapTuningWFS(dB)
ANTHOPMOD
antennaHoppingMode
ANTHOPP
antennaHoppingPeriod
ANTHOPST
antennaHoppingStatus
ARFACCHACMDF
applyRFacchOnAnyCmdFrame
ASCICIPH
enableCiphForASCI
AST
administrativeState
AVS
availabilityStatus
BCCHFREQ
bcchFrequency
BSIC
bsIdentityCode
BTSISHOP
btsIsHopping
BURNOFFS
burstNumberOffset
SYSID
cellAllocationNumber
CELLTYPE
cellType
CUCONF
carrierUnitConfiguration
DTMHOMTIMER
hoDTMTimer(SACCH_multiframe_480/470ms)
EAC
enableAc
EANTHOP
enableAntennaHopping
EEOTD
enableEOTD
EEXCDIST
enableExcessiveDistance
ERFACCHALPDMF
ERFACCHCMDF
enableRFacchOnCmdFrames
ERSACCHDL
enableRSacchDL
ERSACCHUL
enableRSacchUL
ETOP
enableTOP
ETXDIVTS
enableTxDivTimeShift
EXCDIST
excessiveDistance(km)
FACCHQ
facchQual
FACHBT
fachBusyThreshold(dBm)
FRANOFFS
frameNumberOffset
GSMTIME
gsmTime
HOPMODE
hoppingMode
INTAVEPAR
intaveParameter
INTCLASS
enableInterferenceClass
INTLVBND
interferenceLevelBoundaries
MSTXPMAX
mSTxPwrMax(*dBm mapped)
MSTXPMAXC
NEPTTREP
136
enableRFacchOnAnyLapdmFrame
mSTxPwrMaxCompl
notDataRepCount
Id:0900d805805944a4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTS
NTWTYPE
networkType
NY1
ny1
NY2
ny2
OST
operationalState
PCCCHLDI
periodCcchLoadIndication(sec)
PNOFACCH
periodNotificationFACCH(sec)
PWROUT
powerOutputThresholds
RACHBT
rachBusyThreshold(dBm)
RACHLAS
rachLoadAveragingSlots
RELEQUIPOBJ
relatedEquipObjects
REPTYP
reportType
RFRSINDP
rfResourceIndicationPeriod
RSACCHRXLDL
repSacchRxLevDL
RSACCHRXLUL
repSacchRxLevUL
RSACCHTODL
repSacchTimeOutDL
RSACCHTOUL
repSacchTimeOutUL
RXSIGLEVADJ
rxSigLevAdjust
RXSIGLEVADJC
rxSigLevAdjustCompl
RXSWCURSET
rxSwitchCurrentSetting
SWBCAPABILITY
switchedBeamCapability
SWBSERVSTATE
switchedBeamServState
T3105
btsTimer3105(*10ms)
T3151
uplBusyRepRate
TCCCHLDI
thresholdCcchLoadIndication
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 6
PC Time&Date: 05.05.2008 10:43:11 +02:00
NE Time&Date: 05.05.2008 10:27:15 +01:00
USER NAME:
User_f
COMMAND:
Get BTS:NAME=BTS:0;
SW RELEASE:
01-04-19-01-07-01_08-04-03
COMMAND RESULT: Operation successful
A50016-G5100-B333-04-7619
Id:0900d805805944a4
137
BTS
BS-4x / 82 II / 240 / 241 / 240XL commands
acBQPFgtFac = 0.2
acBQPMax(%) = 5
acEFLFgtFac = 0.04
acFERMax(%) = 5.0
acLinkType = UL_SAMPLES_ONLY
acMaxEFLDMA(%) = per_50
acMinEFLDMA(%) = per_10
acPeriod = SACCH_120
administrativeState = Unlocked
aMRLinkAdapTuning = 100
aMRLinkAdapTuningWFS(dB) = 0.0
antennaHoppingMode = ALLTRX
antennaHoppingPeriod = ALL
antennaHoppingStatus = FALSE
applyRFacchOnAnyCmdFrame = FALSE
availabilityStatus = NULL
bcchFrequency = 1
bsIdentityCode =
BCC = 7
NCC = 7
btsIsHopping = FALSE
btsTimer3105(*10ms) = 100
burstNumberOffset = 0
carrierUnitConfiguration = HOMOGENEOUS
cellAllocationNumber = BB900
cellType = STDCELL
enableAc = FALSE
enableAntennaHopping = FALSE
enableCiphForASCI = FALSE
enableEOTD = TRUE
enableExcessiveDistance = FALSE
enableInterferenceClass = TRUE
enableRFacchOnAnyLapdmFrame = NOT_SET
enableRFacchOnCmdFrames = NOT_SET
enableRSacchDL = NOT_SET
enableRSacchUL = NOT_SET
enableTOP = NOT_SET
enableTxDivTimeShift = FALSE
excessiveDistance(km) = 100
138
Id:0900d805805944a4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTS
facchQual = 6
fachBusyThreshold(dBm) = -109
frameNumberOffset = 0
gsmTime = 9624
hoDTMTimer(SACCH_multiframe_480/470ms) = 4
hoppingMode = BBHOP
intaveParameter = 31
interferenceLevelBoundaries =
intThrBou1 = 10
intThsBou2 = 25
intThsBou3 = 40
intThsBou4 = 55
intThsBou5 = 63
mSTxPwrMax(*dBm_mapped) = 15
mSTxPwrMaxCompl = 4
mobileCountryCode =
MCC = "555"
networkType = GSMDCS
notDataRepCount = 3
ny1 = 14
ny2 = 4
operationalState = ENABLED
periodCcchLoadIndication(sec) = 255
periodNotificationFACCH(sec) = 2.5
powerOutputThresholds =
oPwrFaultThreshold = m10db
redOutPwrThreshold = m6db
excesOutPwrThresh = db5
rachBusyThreshold(dBm) = -109
rachLoadAveragingSlots = 204
relatedEquipObjects = Null
reportType = NORMAL
repSacchRxLevDL = 10
repSacchRxLevUL = 7
repSacchTimeOutDL = 4
repSacchTimeOutUL = 4
rfResourceIndicationPeriod = 31
rxSigLevAdjust = Null
rxSigLevAdjustCompl = Null
A50016-G5100-B333-04-7619
Id:0900d805805944a4
139
BTS
BS-4x / 82 II / 240 / 241 / 240XL commands
rxSwitchCurrentSetting = NULL
switchedBeamCapability = none
switchedBeamServState = NULL
thresholdCcchLoadIndication = 10
uplBusyRepRate = 2
END OF OUTPUT FOR JOB 6
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
The attribute HOPMODE (hoppingMode) can be set only if there are no subordinate
frequency hopping system equipped
When the attribute INTCLASS is enabled "RF resource indication" messages (relevant to the attributes INTAVEPAR, INTLVBND and RFRSINDP) are sent to the BSC
Values indicating more than 35 Km in the attribute EXCDIST are valid only for
extended cells
The attributes ETXDIVTS, TXDIVTSEXCPT and TXDIVTSPAR have only functionality for hh=04-01 and hh=04-06
The attributes TXDIVTSEXCPT and TXDIVTSPAR are available with the command
GET BTS TIMER
Example of Command Execution:
Get BTS:NAME=BTS:0,REQATTL=ACBQPFF &ACBQPMAX &ACEFLFF &ACFERMAX&ACLNKTYP &ACMINEFLDMA &ACMAXEFLDMA &ACPER &AMRLKAT&ANTHOPMOD &ANTHOPP &ANTHOPST &ARFACCHACMDF &ASCICIPH
&AST&AVS &BCCHFREQ &BSIC &BTSISHOP &BURNOFFS &SYSID &CELLTYPE&CUCONF &DTMHOMTIMER &EAC &EANTHOP &EEOTD &EEXCDIST
&ERFACCHALPDMF&ERFACCHCMDF &ETOP &ETXDIVTS &EXCDIST &FACCHQ
&FRANOFFS&GSMTIME &HOPMODE &INTAVEPAR &INTCLASS
&INTLVBND&MSTXPMAX &MSTXPMAXC &NTWTYPE &NY1 &NY2 &OST
&PCCCHLDI &PNOFACCH&PWROUT &RACHBT &RACHLAS &RELEQUIPOBJ
&REPTYP &RFRSINDP&RXSIGLEVADJ &RXSIGLEVADJC &RXSWCURSET &SWBCAPABILITY&SWBSERVSTATE &T3105 &TCCCHLDI;
GET BTS TIMER
GET BTS TIMER
NAME=BTS:0..11 ,REQATTL=STATIME, T200, T3115,
TAADJ, TNCH, TSYNC, TSYNCD, TSYNCR, TSYNCU,
TTRAU, TUPLREP, TXDIVTSPAR, TXDIVTSEXCPT, TXSIGLEVADJ, TXSIGLEVADJC, VGSCULFT;
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h BTS h GET BTS
TIMER
140
Id:0900d805805944a4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTS
Applicability:
Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the BTS timer.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
STATIME
startingTime
T200
t200
T3115
t3115(*10ms)
TAADJ
taAdjust(microseconds)
TNCH
tNCH(*multiframes)
TSYNC
tSync(*10ms)
TSYNCD
tSyncD(*10ms)
TSYNCR
tSyncR(*10ms)
TSYNCU
tSyncU(*10ms)
TTRAU
tTrau(*10ms)
TUPLREP
timerUplinkReply
TXDIVTSPAR
txDivTimeShiftParam
TXDIVTSEXCPT
TXSIGLEVADJ
txSigLevAdjust
TXSIGLEVADJC
VGSCULFT
txDivTimeShiftExcept
txSigLevAdjustCompl
voiceGroupUplinkFree(*10ms)
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get timer command is
the following:
JOB: 288
PC Time&Date: 05.05.2008 11:43:09 +02:00
NE Time&Date: 05.05.2008 11:43:11 +01:00
USER NAME:
User_f
COMMAND:
Get BTS Timer:NAME=BTS:0,REQATTL=STATIME&T200&T3115&TADDJ&TNCH&TSYNC&TSYNCD&TSYNCR&TSYNCU&TTRA
U&TUPLREP&TXDIVTSPAR&TXDIVTSEXCPT&TXSIGLEVADJ&TXSIGLEVADJC&VGSCULFT;
A50016-G5100-B333-04-7619
Id:0900d805805944a4
141
BTS
BS-4x / 82 II / 240 / 241 / 240XL commands
SW RELEASE:
01-04-19-01-86-MF_08-04-24
COMMAND RESULT: Operation successful
startingTime = 65535
t200 =
sdcchSAPIO = 44
facchTCHF = 31
facchTCHH = 41
saccchTCHSAPIO = 90
sacchSDCCH = 90
sdcchSAPI3 = 90
sacchTCHSAPI3 = 135
t3115(*10ms) = 3
taAdjust(microseconds) = 0.0
timerUplinkReply = 20
tNCH(*multiframes) = 1
tSync(*10ms) = 1000
tSyncD(*10ms) = 1000
tSyncR(*10ms) = 400
tSyncU(*10ms) = 1000
tTrau(*10ms) = 1000
txDivTimeShiftExcept = NONE
txDivTimeShiftParam = 0.00
txSigLevAdjust = Null
txSigLevAdjustCompl = Null
voiceGroupUplinkFree(*10ms) = 2
END OF OUTPUT FOR JOB 288
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Get BTS Timer:NAME=BTS:0,REQATTL=STATIME&T200&T3115&TADDJ&TNCH&TSYNC&TSYNCD&TSYNCR&TSYNCU&TTRA
U&TUPLREP&TXDIVTSPAR&TXDIVTSEXCPT&TXSIGLEVADJ&TXSIGLEVADJC&VGSCULFT;
142
Id:0900d805805944a4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSEP
BTSEP
The BS240/1 consists of a base rack with up to 8 TRXs. Optionally it can be connected
to two extension racks to reach up to 24 TRX.
The BS240XL consists of a base rack with up to 12 TRXs. Optionally it can be connected
an extension rack to reach up to 24 TRXs.
The BS40/1 and BS40II consists of a base rack with up to 4 TRXs.
The BS82II consists of a base rack with up to 2 TRXs. Optionally it can be connected up
two extension rack to reach up to 6 TRXs.
DELETE BTSEP DBFILE
DELETE BTSEP
DBFILE
NAME=BTSEP:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h DELETE BTSEP
DBFILE
Applicability:
Phase 2.
Visibility level: 2.
Command Description:
This command deletes the data base file.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The data base file has been deleted.
JOB: 55
PC Time&Date: 11:56:59 03/23/2005
NE Time&Date: 12:58:13 09/15/2004
USER NAME:
User_g
COMMAND:
Delete BTSEP DBFILE:NAME=BTSEP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 55
A50016-G5100-B333-04-7619
Id:0900d805805944a6
143
BTSEP
BS-4x / 82 II / 240 / 241 / 240XL commands
Operation Failed
The data base file has not been deleted.
Application Guidelines:
The file related to REMINV isn't affected by the command
The command cause a restart of the BTSE and that the operator has to do a new
login afterward
All HW Objects, which were created per command, will be deleted, including
"Minimal Configuration"
All stored SW Loads will still be available
Only the DB of COBA:0 will be deleted
Example of Command Execution:
Delete BTSEP DBFILE:NAME=BTSEP:0;
FORMAT BTSEP FLASH
FORMAT BTSEP
FLASH
NAME=BTSEP:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h FORMAT BTSEP
FLASH
Applicability:
Phase 1 and Phase 2.
Visibility level: 3.
Dangerous
Command Description:
This command formats the Flash EPROMs of COBA (Core module). Since it is considered a "dangerous" command, a confirmation dialog will ask you to confirm or cancel the
action.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The Flash EPROMs of the COBA have been formatted.
JOB: 56
PC Time&Date: 11:57:07 03/23/2005
NE Time&Date: 12:58:42 09/15/2004
144
Id:0900d805805944a6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSEP
USER NAME:
User_g
COMMAND:
Format BTSEP FLASH:NAME=BTSEP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 56
Operation Failed
The Flash EPROMs of the COBA have not been formatted.
Application Guidelines:
The command cause a restart of the BTSE and that the operator has to do a new
login afterward
All HW Objects and all SW Loads will be deleted, complete formatting in COBA:0 if
COBA:1 is Power Off
Example of Command Execution:
Format BTSEP FLASH:NAME=BTSEP:0;
GET BTSEP NOSWL
GET BTSEP NOSWL
NAME=BTSEP:0..0 [,REQATTL=ALIGCOBA, ALRMSEVXXX, ALS, AST, AVS, CHIDT, EAUTOREC, EQUPOS,
GTWADRV4, LMTLSESS, LMTLTIME, LMTUAL, LMTUNAME, LOCNAME, OST, OVPTINS, PRS, RELFUNCOBJ,
RXDIVSV, SALUNAME, SCLPRIOLST, VENDNA];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h GET BTSEP NOSWL
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes related to the BTSE (BTS Site Equipment).
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALIGCOBA
alignedCoba
ALRMSEVXXX
alarmSeverityXXX
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
A50016-G5100-B333-04-7619
Id:0900d805805944a6
145
BTSEP
BS-4x / 82 II / 240 / 241 / 240XL commands
CHIDT
changeOnIDT
EAUTOREC
enableAutoRecovery
EQUPOS
equipmentPosition
GTWADRV4
gatewayAddressIPv4
LMTLSESS
lmtLogonSession
LMTLTIME
lmtLogonTime
LMTUAL
lmtUserAccessLevel
LMTUNAME
lmtUserName
LOCNAME
locationName
OST
operationalState
OVPTINS
ovptInstalled
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
RXDIVSV
enableRxDiversitySupervision
SALUNAME
salesUniqueName
SCLPRIOLST
serviceClassPrioList
VENDNA
vendorName
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get noswl command is
the following:
JOB: 29
PC Time&Date: 30.05.2008 10:57:41 +02:00
NE Time&Date: 01.01.1990 00:02:14 +00:00
USER NAME:
User_g
COMMAND:
Get BTSEP NOSWL:NAME=BTSEP:0;
SW RELEASE:
01-04-19-01-01-ZS_08-05-29
COMMAND RESULT: Operation successful
alignedCoba = TRUE
alarmSeverityAcdcp = DEFAULT_DB
alarmSeverityAct = DEFAULT_DB
alarmSeverityCoba = DEFAULT_DB
alarmSeverityBattery = DEFAULT_DB
alarmSeverityBcomp = DEFAULT_DB
alarmSeverityCosa = DEFAULT_DB
146
Id:0900d805805944a6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSEP
alarmSeverityCu = DEFAULT_DB
alarmSeverityDidctma = DEFAULT_DB
alarmSeverityDilna = DEFAULT_DB
alarmSeverityDuamco = DEFAULT_DB
alarmSeverityDudctma = DEFAULT_DB
alarmSeverityDulna = DEFAULT_DB
alarmSeverityDuvswr = DEFAULT_DB
alarmSeverityF6dctma = DEFAULT_DB
alarmSeverityF6lna = DEFAULT_DB
alarmSeverityF6tnfp = DEFAULT_DB
alarmSeverityF6vswrp = DEFAULT_DB
alarmSeverityFanp = DEFAULT_DB
alarmSeverityFcumain = DEFAULT_DB
alarmSeverityFcutr = DEFAULT_DB
alarmSeverityFtnfp = DEFAULT_DB
alarmSeverityFvswrp = DEFAULT_DB
alarmSeverityLmu = DEFAULT_DB
alarmSeveritySdulna = DEFAULT_DB
alarmSeveritySdusec = DEFAULT_DB
alarmSeveritySdusubs = DEFAULT_DB
alarmSeveritySdutxsw = DEFAULT_DB
alarmSeverityTma = DEFAULT_DB
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
changeOnIDT = IDTWasChanged
enableAutoRecovery = disabled
equipmentPosition = "010101"
gatewayAddressIPv4 = "192.168.3.20"
lmtLogonSession = ACTIVE
lmtLogonTime = 01.01.2008 00:00:17 +00:00
lmtUserAccessLevel = ACCESS_CONTROL_MANAGEMENT
lmtUserName = "User_g"
locationName = "EARTH"
operationalState = ENABLED
ovptInstalled = TRUE
proceduralStatus = NULL
relatedFuncObjects =
FMO = BTSM:0
A50016-G5100-B333-04-7619
Id:0900d805805944a6
147
BTSEP
BS-4x / 82 II / 240 / 241 / 240XL commands
enableRxDiversitySupervision = disabled
salesUniqueName = ""
serviceClassPrioList =
serviceClass = ces
vlanPrio = vPrio7
dscpClass = dCl5
dscpDropPre = dDP6
vendorName = "Nokia Siemens Networks"
END OF OUTPUT FOR JOB 29
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
The attributes have to be set beforehand, otherwise the response will be a Nack
message
Example of Command Execution:
Get BTSEP NOSWL:NAME=BTSE:0,REQATTL=ALIGCOBA& ALRMSEVXXX&ALRMSEVBCOMP& ALRMSEVDUAMCO&ALRMSEVF6DCTMA&
ALRMSEVF6LNA&ALRMSEVF6TNFP& ALRMSEVF6VSWRP& ALS& AST&
AVS&CHIDT& EAUTOREC& EQUPOS& GTWADRV4& LMTLSESS&LMTLTIME&
LMTUAL& LMTUNAME& LOCNAME& OST&OVPTINS& PRS& RELFUNCOBJ&
RXDIVSV& SALUNAME&SCLPRL& VENDNA;
GET BTSEP SWL
GET BTSEP SWL
NAME=BTSEP:0..0 ,REQATTL=SWLDINT, SWLDSAF,
SWLDST;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h GET BTSEP SWL
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes related to the BTSE (BTS Site Equipment).
Long Names:
148
NAME
Address of the managed object
REQATTL
Required attribute list
SWLDINT
swLoadIntended
SWLDSAF
swLoadSafety
Id:0900d805805944a6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
SWLDST
BTSEP
swLoadsStored
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get swl command is the
following:
JOB: 49
PC Time&Date: 11:56:26 03/23/2005
NE Time&Date: 12:58:01 09/15/2004
USER NAME:
User_g
COMMAND:
SAF&SWLDST
Get BTSEP SWL:NAME=BTSEP:0,REQATTL=SWLDINT&SWLD-
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
swLoadIntended = "HS011907.SWL:01-04-19-01-07-00_08-03-19"
swLoadSafety = ""
swLoadsStored =
SWLD = "HS011907.SWL:01-04-19-01-07-00_08-03-19"
SWLD = "FSFD1901.SWL:FD-04-19-00-01-00_08-01-29"
SWLD = "FSBO1910.SWL:BO-04-19-01-10-03_08-01-08"
END OF OUTPUT FOR JOB 49
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
The attributes have to be set beforehand, otherwise the response will be a Nack
message
Example of Command Execution:
Get BTSEP SWL:NAME=BTSEP:0,REQATTL=SWLDINT&SWLDSAF&SWLDST;
GETACTIVEALARMS BTSEP
GETACTIVEALARMS
BTSEP
A50016-G5100-B333-04-7619
NAME=BTSEP:0..0 [,EVTYP=];
Id:0900d805805944a6
149
BTSEP
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h GETACTIVEALARMS
BTSEP
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command is sent to the BTSE to ask for the active alarms of a certain
failure_event_type.
When a remote connection is made a warning is issued from LMT to inform you that
FER coming from BTS, TRAU and BSC are not received. This must be intended in the
sense that: spontaneous FER are not received when they are originated but active
FER on connected BTS and TRAU can be retrieved by using the command GetActiveAlarm, both from CLI and GUI LMT, present also in RemoteMode.
A Failure Event Report will be displayed, with the following attributes:
eventType
This attribute specifies the type of failure event alarm.
eventTime
It represents the time of the event.
perceivedSeverity
This attribute can assume the following values:
indeterminate
criticalFailure
majorFailure
minorFailure
warningLevelFailure
failureCeased
probableCause
This attribute indicates the probable cause of the failure.
specificProblem
It is a code that has to be referred to the 'Alarm Manual'.
trendIndication
This attribute can assume the following values:
lessSevere
noChange
moreSevere
notificationIdentifier
The range of this attribute is: 0...4294967295
correlatedNotifications
This attribute is composed by the following fields:
identifier: 0...4294967295
relatedMO: object class and object instance refer
to the source object in the father event. During
state and alarm alignment the state class BTSEP
is used.
150
Id:0900d805805944a6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSEP
thresholdInformation
This information element is only present if a threshold is
assigned to the corresponding alarm and the 'perceived
severity' is not 'failure ceased'. If no threshold is
exceeded only the observed value is valid.
additionalText
This is a string of 26 ASCII characters which are specified by the operator for the corresponding envaBTSE
instance (site input). The ASCII characters are not terminated by a NULL character
additionalInformation
This attribute specifies some additional information
(Originator value, FileVersion...)
Long Names:
NAME
Address of the managed object
EVTYP
eventType
System Responses:
Operation Completed
A message indicates the result of the operation. An example of getactivealarms
command is the following:
JOB: 50
PC Time&Date: 11:56:29 03/23/2005
NE Time&Date: 12:58:04 09/15/2004
USER NAME:
User_g
COMMAND:
Getactivealarms BTSEP:NAME=BTSEP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 50
JOB: 51
PC Time&Date: 11:56:29 03/23/2005
NE Time&Date: 12:58:04 09/15/2004
USER NAME:
User_g
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
START ACTIVE ALARM ALIGNMENT BTSEP:
A50016-G5100-B333-04-7619
Id:0900d805805944a6
151
BTSEP
BS-4x / 82 II / 240 / 241 / 240XL commands
name = BTSEP:0
alignmentRequestNo = 0
notificationIdentifier = 288
END OF OUTPUT FOR JOB 51
JOB: 52
PC Time&Date: 11:56:29 03/23/2005
NE Time&Date: 12:58:04 09/15/2004
USER NAME:
User_g
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END ACTIVE ALARM ALIGNMENT BTSEP:
name = BTSEP:0
alignmentResult = SUCCESSFUL
correlatedNotifications =
correlatedNotificationId = 288
sourceObjectInstance = BTSEP:0
END OF OUTPUT FOR JOB 52
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
None.
Example of Command Execution:
Getactivealarms BTSEP: NAME=BTSEP:0,
EVTYP= ENVIRONMENTAL_FAILURE_EVENT;
PERFTEST BTSEP
PERFTEST BTSEP
NAME=BTSEP:0..0 ,MORT=;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h PERFTEST BTSEP
152
Id:0900d805805944a6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSEP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command displays the attributes related to the BTSE (BTS Site Equipment).
Long Names:
NAME
Address of the managed object
MORT
MOT
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSEP
JOB: 55
PC Time&Date: 11:56:59 03/23/2005
NE Time&Date: 12:59:48 09/15/2004
USER NAME:
User_g
COMMAND:
Perftest BTSEP:NAME=BTSEP:0,MORT=RACK:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = BTSEP:0,MORT=RACK:0;
tO = BTSETEST:1
END OF OUTPUT FOR JOB 55
JOB: 56
PC Time&Date: 11:57:07 03/23/2005
NE Time&Date: 12:58:42 09/15/2004
USER NAME:
User_g
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
A50016-G5100-B333-04-7619
Id:0900d805805944a6
153
BTSEP
BS-4x / 82 II / 240 / 241 / 240XL commands
name = BTSETEST:1
ChangeInfo = created
END OF OUTPUT FOR JOB 56
JOB: 57
PC Time&Date: 11:57:14 03/23/2005
NE Time&Date: 12:58:49 09/15/2004
USER NAME:
User_g
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = BTSEP:0,MORT=RACK:0;
Availability Status = Failed
Notification Identifier = 22
END OF OUTPUT FOR JOB 57
JOB: 58
PC Time&Date: 11:57:24 03/23/2005
NE Time&Date: 12:58:59 09/15/2004
USER NAME:
User_g
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:1
testOutcome = FAILED
testTermination = Normal
MOT = BTSEP:0,MORT=RACK:0;
executedPhases =
PreliminaryTestsBtsep
154
Id:0900d805805944a6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSEP
BootEepromTestBtsep
SerialEepromTestBtsep
EndTestBtsep
END OF OUTPUT FOR JOB 58
JOB: 59
PC Time&Date: 11:57:24 03/23/2005
NE Time&Date: 12:58:59 09/15/2004
USER NAME:
User_g
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:1
ChangeInfo = deleted
END OF OUTPUT FOR JOB 59
The test results will be displayed at the end of the test phases.
Result TEST:
A50016-G5100-B333-04-7619
name =
TEST:<n>
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
Id:0900d805805944a6
155
BTSEP
BS-4x / 82 II / 240 / 241 / 240XL commands
executedPhases
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: Message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
In phase 3 MO must be locked previous to the command execution
Example of Command Execution:
Perftest BTSEP:NAME=BTSEP:0,MORT=RACK:0/ACDCP:0;
PING BTSEP
PING BTSEP
NAME=BTSEP:0..0 ,IPADR=;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h PING BTSEP
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
The command is used to ping the BTSE.
After command execution the IP sends a response containing the following information:
-
156
IP address
of the target
Id:0900d805805944a6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSEP
alive
=TRUE/FAL
SE
Long Names:
NAME
Address of the managed object
IPADR
ipAddress
System Responses:
Operation Completed
A message indicates the result of the operation. An example of ping command is the following:
JOB: 60
PC Time&Date: 21.08.2008 13:43:00 +02:00
NE Time&Date: 21.08.2008 13:32:30 +01:00
USER NAME:
User_g
COMMAND:
Ping BTSEP:NAME=BTSEP:0,IPADR="192.168.3.25";
SW RELEASE:
01-04-19-01-12-ZT_08-08-20
COMMAND RESULT: Operation successful
hostReachable = HOST_REACHABLE
ipAddress = "192.168.3.25"
END OF OUTPUT FOR JOB 60
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Ping BTSEP:NAME=BTSEP:0,IPADR="192.168.3.25";
SET BTSEP
SET BTSEP
A50016-G5100-B333-04-7619
NAME=BTSEP:0..0 [,ALIGCOBA=] [,ALRMSEVXXX=]
[,CHIDT=] [,EAUTOREC=] [,EQUPOS=] [,GTWADRV4=]
[,LOCNAME=] [,OVPTINS=] [,RXDIVSV=] [,SALUNAME=]
[,SCLPRIOLST=] [,SWLDSAF=] [,VENDNA=];
Id:0900d805805944a6
157
BTSEP
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h SET BTSEP
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command sets general attributes of the BTS Site Equipment (BTSE). A BTSE is the
physical equipment which is managed by one BTSM.
Long Names:
NAME
Address of the managed object
ALIGCOBA
alignedCoba
ALRMSEVXXX
alarmSeverityXXX
CHIDT
changeOnIDT
EAUTOREC
enableAutoRecovery
EQUPOS
equipmentPosition
GTWADRV4
gatewayAddressIPv4
LOCNAME
locationName
OVPTINS
ovptInstalled
RXDIVSV
enableRxDiversitySupervision
SALUNAME
salesUniqueName
SCLPRIOLST
serviceClassPrioList
SWLDSAF
swLoadSafety
VENDNA
vendorName
System Responses:
Operation Completed
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
JOB: 19
PC Time&Date: 13.03.2008 13:28:24 +01:00
NE Time&Date: 01.01.1990 00:03:37 +00:00
USER NAME:
User_g
COMMAND:
Set BTSEP:NAME=BTSEP:0,GTWADRV4="192.168.5.100/24";
SW RELEASE:
01-04-19-01-06-03_08-03-11
COMMAND RESULT: Operation successful
158
Id:0900d805805944a6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSEP
gatewayAddressIPv4 = "192.168.5.100/24"
END OF OUTPUT FOR JOB 19
Operation Failed
The specified attributes have not been set. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible.
Application Guidelines:
The supplier recommends the identification of swLoadSafety
The swLoadSafety will not be overwritten by a sw download via LMT Evolution
There is no alignment to one of the SW loads stored on the BSC master database
The swLoad must be stored in BTSE and must have at least once a connection with
the BSC
The identification of a SW load as the safety one is only accepted by the BTSE if the
identified load has been activated and running on this BTSE before
An update of the swLoadSafety attribute should be performed in each release; the
swLoad of the previous release should be used as swLoadSafety
Example of Command Execution:
Set BTSEP :NAME=BTSEP:0,Set BTSEP:NAME=BTSEP:0,ALRMSEVACDCP=CRITICAL,ALRMSEVACT=CRITICAL,ALRMSEVBATTERY=CRITICAL,ALRMSEVBCOMP=CRITICAL,ALRMSEVCOBA=CRITICAL,ALRMSEVCOSA=CRITICAL,ALRMS
EVCU=CRITICAL,ALRMSEVDIDCTMA=CRITICAL,ALRMSEVDILNA=CRITICAL,ALRMSEVDUAMCO=CRITICAL,ALRMSEVDUDCTMA=CRITICAL,ALRMSEVDULNA=CRITICAL,ALRMSEVDUVSWR=CRITICAL,ALRMSEVF6DCTMA=CRITI
CAL,ALRMSEVF6LNA=CRITICAL,ALRMSEVF6TNFP=CRITICAL,ALRMSEVF6VSWRP=CRITICAL,ALRMSEVFANP=CRITICAL,ALRMSEVFCUMAIN=CRITICAL,ALRMSEVFCUTR=CRITICAL,ALRMSEVFTNFP=CRITICAL,ALRM
SEVFVSWRP=CRITICAL,ALRMSEVLMU=CRITICAL,ALRMSEVSDULNA=CRITICAL,ALRMSEVSDUSEC=CRITICAL,ALRMSEVSDUSUBS=CRITICAL,ALRMSEVSDUTXSW=CRITICAL,ALRMSEVTMA=CRITICAL,EQUPOS="020101",CHIDT=noCha
ngeOnIDT,
EAUTOREC=disabled,LOCNAME="MUNICH",OVPTINS=true,RXDIVSV=enabled,
SALUNAME="AD042S7449E",SWLDSAF="HS011726.SWL:02-04-17-01-13-00_0409-03",VENDNA="Nokia Siemens Networks";
STOPTEST BTSEP
STOPTEST BTSEP
NAME=BTSEP:0..0 [,MORT=] [,TESTNO=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h STOPTEST BTSEP
Applicability:
Phase 2 and Phase 3.
A50016-G5100-B333-04-7619
Id:0900d805805944a6
159
BTSEP
BS-4x / 82 II / 240 / 241 / 240XL commands
Visibility level: 1.
Command Description:
This command requires the stop of the test on BTSE Plus.
Long Names:
NAME
Address of the managed object
MORT
MOT
TESTNO
testNo
System Responses:
Operation Completed
Test has been stopped.
Operation Failed
Test has not been stopped. This NACK-message can occur
when the specified test is not running or in case of test which
cannot be stopped.
TEST REPORT:
The TEST REPORT provides a list of executed, failed and
skipped phases.
Application Guidelines:
None.
Example of Command Execution:
Stoptest BTSEP:NAME=BTSEP:0, MORT=RACK:0/ACDCP:0,TESTNO=23;
160
Id:0900d805805944a6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSETEST
BTSETEST
The TEST locates a test object in the system; this object is created when an activation
of a diagnostic occurs.
GET BTSETEST
GET BTSETEST
NAME=BTSETEST:1..255 [,REQATTL=MORT, TESTMON,
TESTOUT, TESTST];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h BTSETEST h GET
BTSETEST
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes related to a test. The values 1-255 will be used for
the allocated 'test object instance' to keep track of the related 'MORTs'.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
MORT
MOT
TESTMON
testMonitor
TESTOUT
testOutcome
TESTST
testState
System Responses:
Operation Completed
The output includes a test report containing "Executed Phases", "Failed Phases", "TestOutcome", "Test Termination", "MOT". An example of "Test Report" is the following:
JOB: 19
PC Time&Date: 11:32:14 03/23/2005
NE Time&Date: 11:30:55 09/15/2004
USER NAME:
User_NSN
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report BTSETEST:
A50016-G5100-B333-04-7619
Id:0900d805805944a8
161
BTSETEST
BS-4x / 82 II / 240 / 241 / 240XL commands
name = BTSETEST:1
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/CU:2
executedPhases =
PreliminaryTestsAct
CheckAlarmStatusAct
EndTestAct
END OF OUTPUT FOR JOB 19
Operation Failed
The GETTEST command has not been successfully executed.
A general NACK will indicate possible errors or a specific NACK strictly related to the
single command is possible.
Application Guidelines:
Only intrusive tests are supported
For TESTOUT attribute the value inconclusive is possible only during the start
phase. It indicates that no "Pass" or "Fail" outcome has been determined yet
Example of Command Execution:
Get BTSETEST :NAME=BTSETEST:1,REQATTL=MORTS&TESTMON&TESTOUT&TESTST;
162
Id:0900d805805944a8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSM
BTSM
The BTSM object provides services to control the functionalities of one or more BTSs
located at the same site. It performs all the operation and maintenance functions
common to all transceivers.
ACTIVATE BTSM
ACTIVATE BTSM
NAME=BTSM:0..0 ,FILEID= ,FILESWV=;
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h ACTIVATE BTSM
Applicability:
Phase 1 and Phase 2.
Visibility level: 2.
Command Description:
This command activates one of the three SW loads stored in the BTSE.
Long Names:
NAME
Address of the managed object
FILEID
fileId
FILESWV
fileVersion
System Responses:
Operation Completed
Download START:
JOB: 181
PC Time&Date: 12:06:21 03/23/2005
NE Time&Date: 13:07:57 09/15/2004
USER NAME:
User_NSN
COMMAND:
Activate BTSM:NAME=BTSM:0,FILEID="HS011726.SWL:01-04-1601-59-00_03-11-18";
SW RELEASE: 01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
fileId = "HS011722.SWL"
fileVersion = "01-04-17-01-26-51_05-02-23"
END OF OUTPUT FOR JOB 181
A50016-G5100-B333-04-7619
Id:0900d805805944aa
163
BTSM
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 182
PC Time&Date: 12:06:21 03/23/2005
NE Time&Date: 13:07:57 09/15/2004
USER NAME:
User_NSN
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ID_Message
END OF OUTPUT FOR JOB 182
SW ACTIVATED REPORT:
(a report is displayed)
Operation Failed
(Invalid SVR)
Application Guidelines:
If an incorrect FileVersion is given the system rejects the command
This command is followed by a reset of the BTSE
If the currently running SW version is activated by the command, the SW will be distributed again in the BTSE
If the intended SW is corrupted, the BTSE first tries to come up with the safety load;
if this is not successful, the BTSE tries to start the third SWload, the dischargeable
one
The FileId is a parameter used within the SW download procedures and not of the
type 'GET'. The corresponding attribute is SWLCFID and is related only to the
swLoad-header file. All characters of the ASCII string are to be in upper case.
However, the SW parts in the BTSE handling the file Id are to be case tolerant
The FileVersion is a parameter used within the SW download procedures and not of
the type 'GET'. The corresponding attribute is SWLCVER which is coded identical
as File Version. However the allowed values for 'hh' are different because
SWLCVER is related only to the swLoad-header file
Recent BTS SW productions expect 64M RAM, the SW doesn't work with old
CESCOBA
Example of Command Execution:
Activate BTSM:NAME=BTSM:0,FILEID="vHS011722.SWL",FILESWV="02-04-16-0105-01_03_02_25"
164
Id:0900d805805944aa
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSM
ACTIVATE_DELAYED BTSM
ACTIVATE_DELAYED
BTSM
NAME=BTSM:0..0 ,FILEID= ,FILESWV= ,TIMEDELAY=;
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h ACTIVATE_DELAYED
BTSM
Applicability:
Phase 2.
Visibility level: 2.
Command Description:
This command activates one of the three SW loads stored in the BTSE with a defined
delayed time.
Long Names:
NAME
Address of the managed object
FILEID
fileId
FILESWV
fileVersion
TIMEDELAY
timeDelay(sec)
System Responses:
Operation Completed
USER NAME:
User_NSN
COMMAND:
Activate_delayed BTSM:NAME=BTSM:0,FILEID="123456789123",FILESWV="01-01-16-00-56-00_03-10-16",TIMEDELAY=3;
SW RELEASE:
01-01-17-00-26-51_05-02-23
COMMAND RESULT: Operation successful
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Activate_delayed BTSM:NAME=BTSM:0,FILEID="123456789123",FILESWV="01-0116-00-56-00_03-10-16",TIMEDELAY=3;
CONNBSC BTSM
CONNBSC BTSM
NAME=BTSM:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h CONNBSC BTSM
A50016-G5100-B333-04-7619
Id:0900d805805944aa
165
BTSM
BS-4x / 82 II / 240 / 241 / 240XL commands
Applicability:
Phase 2.
Visibility level: 1.
Command Description:
This command starts the connection between BTS and BSC and is followed by a transition from LMT Phase 2 to LMT Phase 3.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The command has been correctly executed.
JOB: 180
PC Time&Date: 12:06:20 03/23/2005
NE Time&Date: 00:00:00 00/00/0
USER NAME:
User_NSN
COMMAND:
Connbsc BTSM:NAME=BTSM:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 180
SWACTIVATED REPORT
Operation Failed
The command has not been correctly executed.
Application Guidelines:
166
After the execution of this command, the BTSM will be in the administrative state
"Unlocked"
If one of the "Minimal Parameters" of the BTSE is in the locked state, no connection
to the BSC is possible
The CCLK accuracy must be "Medium" or "High" before the connection to the BSC
is possible
The BTSM attribute TEI has to be defined
The BPORT object has to be defined previous LAPDLE
The LAPDLE object has to be defined
Id:0900d805805944aa
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSM
For OMC purposes the Attributes SALUNAME and TYPRACK have to be set. Otherwise the OMC cannot identify the BTSE
Example of Command Execution:
Connbsc BTSM:NAME=BTSM:0;
DISCBSC BTSM
DISCBSC BTSM
NAME=BTSM:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h DISCBSC BTSM
Applicability:
Phase 3.
Visibility level: 1.
Command Description:
This command disconnects the BTS from the BSC and is followed by a transition from
LMT Phase 3 to LMT Phase 2.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The command has been correctly executed.
JOB: 179
PC Time&Date: 12:06:20 03/23/2005
NE Time&Date: 00:00:00 00/00/0
USER NAME:
User_NSN
COMMAND:
Discbsc BTSM:NAME=BTSM:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 179
Operation Failed
The command has not been correctly executed.
A50016-G5100-B333-04-7619
Id:0900d805805944aa
167
BTSM
BS-4x / 82 II / 240 / 241 / 240XL commands
Application Guidelines:
If a connection to the BSC is established, the BTSM must be in the administrative
state "Locked"
If the SW in BTSM in BSC is not the same like in BTSE, BTSM cannot be locked
(At BSC disk no SW is available) and the user cannot come to Phase 2. To come to
phase 2, execute a COBA manual reset.
Example of Command Execution:
Discbsc BTSM:NAME=BTSM:0;
FWUPGRADE BTSM
FWUPGRADE BTSM
NAME=BTSM:0..0 ,FILEID= ,FILEFWV= [,LRU=] [,ACTVINC=];
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h FWUPGRADE BTSM
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command is used to initiate the firmware upgrade.
Long Names:
NAME
Address of the managed object
FILEID
fileId
FILEFWV
fwVersion
LRU
lru
ACTVINC
activationIncluded
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of fwupgrade
command is the following:
JOB: 62
PC Time&Date: 26.03.2008 13:23:37 +01:00
NE Time&Date: 01.01.1990 00:08:35 +00:00
USER NAME:
168
User_NSN
Id:0900d805805944aa
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSM
COMMAND:
FwUpgrade BTSM:NAME=BTSM:0,ACTVINC=TRUE,FILEFWV="BU04-19-00-01-15_08-01-29",FILEID="FSBU1901.SWL";
SW RELEASE:
01-04-19-01-07-00_08-03-19
COMMAND RESULT: Operation successful
fileId = "FSBU1901.SWL"
fwVersion = "BU-04-19-00-01-15_08-01-29"
activationIncluded = TRUE
END OF OUTPUT FOR JOB 62
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
FwUpgrade BTSM:NAME=BTSM:0,ACTVINC=TRUE,FILEFWV="BU-04-19-00-0115_08-01-29",FILEID="FSBU1901.SWL",LRU=HwP-Fcumain-0;
GET BTSM NOSWL
GET BTSM NOSWL
NAME=BTSM:0..0 [,REQATTL=ABISLKSAT, ABISTIME,
ASUBLKSAT, AST, AVS, DYNTRACGRAN, EINTSITSYN,
EMT1, EMT2, LPDLMSAT, OMLAPDRT, OST, RELEQUIPOBJ, TEI, TSLPOOL, SHLAPDIT];
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h GET BTSM NOSWL
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes related to the BTSM (BTS Site Manager).
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ABISLKSAT
sAbisLinkSatellited
ABISTIME
sAbisExternalTime
ASUBLKSAT
sAsubLinkSatellited
AST
administrativeState
A50016-G5100-B333-04-7619
Id:0900d805805944aa
169
BTSM
BS-4x / 82 II / 240 / 241 / 240XL commands
AVS
availabilityStatus
DYNTRACGRAN
dynTraceGranularity
EINTSITSYN
enableInterSiteSync
EMT1
emergencyTimer1(min)
EMT2
emergencyTimer2(min)
LPDLMSAT
lapdleLinkSatellited
OMLAPDRT
omLapdRelTimer(sec)
OST
operationalState
RELEQUIPOBJ
relatedEquipObjects
TEI
tei
TSLPOOL
tslPool
SHLAPDIT
shortLapdIntTimer(sec)
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get noswl command is
the following:
JOB: 20
PC Time&Date: 11:33:34 03/23/2005
NE Time&Date: 11:31:25 09/15/2004
USER NAME:
User_NSN
COMMAND:
Get BTSM NOSWL:NAME=BTSM:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
availabilityStatus = NULL
dynTraceGranularity = 1
emergencyTimer1(min) = 10
emergencyTimer2(min) = 0
enableInterSiteSync = FALSE
lapdleLinkSatellited = terrestrialConnection
omLapdRelTimer(sec) = 30
operationalState = ENABLED
relatedEquipObjects =
HMO = BTSEP:0
sAbisExternalTime =
170
Id:0900d805805944aa
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSM
Year = 2003
Month = Jan
Day = 1
Hour = 20
Minute = 16
Second = 3
sAbisLinkSatellited = terrestrialConnection
sAsubLinkSatellited = terrestrialConnection
shortLapdIntTimer(sec) = 15
tei = 0
JOB: 20
tslPool =
TS01 TS02 TS03 TS04 TS05 TS06 TS07 TS08
TS09 TS10 TS11 TS12 TS13 TS14 TS15 TS16
TS17 TS18 TS19 TS20 TS21 TS22 TS23 TS24
TS25 TS26 TS27 TS28 TS29 TS30 TS31
BPORT0
0000 0000 0000 0000 1111 1111 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000
END OF OUTPUT FOR JOB 23
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
In order to decide whether a "fast" alignment instead of a "full" one must be started,
the BSC reads the shortLAPDIntTimer and increases it of a value currently fixed to
30 seconds; for this reason the suggested values are
shortLAPDIntTimer:
max. attribute length for attribute tslPool increased to 136
Example of Command Execution:
Get BTSM NOSWL:NAME=BTSM:0,REQATTL=ABISLKSAT&ABISTIME&
AST&ASUBLKSAT&AVS&DYNTRACGRAN&EMT1&EMT2&EINTSITSYN&
LPDLMSAT&OMLAPDRT&OST&RELEQUIPOBJ&SHLAPDIT&TEI&TSLPOOL;
A50016-G5100-B333-04-7619
Id:0900d805805944aa
171
BTSM
BS-4x / 82 II / 240 / 241 / 240XL commands
GET BTSM OVERLOAD
GET BTSM OVERLOAD NAME=BTSM:0..0 ,REQATTL=LAPDOVLTH, LAPDOVLT,
LAPDOVLTRXL;
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h GET BTSM
OVERLOAD
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes related to the BTSM (BTS Site Manager).
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
LAPDOVLTH
lapdOverloadThresholds(%)
LAPDOVLT
lapdOverloadTimer(sec)
LAPDOVLTRXL
lapdOverloadTRXList
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get overload command
is the following:
JOB: 5363
PC Time&Date: 30.11.2006 15:59:16 +01:00
NE Time&Date: 30.11.2006 14:59:07 +00:00
USER NAME:
User_NSN
COMMAND:
Get BTSM OVERLOAD:NAME=BTSM:0,REQATTL=LAPDOVLTH&LAPDOVLT&LAPDOVLTRXL;
SW RELEASE:
01-01-18-00-11-00_06-10-03
COMMAND RESULT: Operation successful
lapdOverloadTimer(sec) =
lapdOverloadTimer = 10
lapdUsageOverloadTimer = 0.5
lapdOverloadThresholds(%) =
firstLevUpperThreshold = 80
172
Id:0900d805805944aa
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSM
firstLevLowerThreshold = 70
firstLevReductionStep = 10
secLevUpperThreshold = 90
secLevLowerThreshold = 80
lapdOverloadTRXList =
END OF OUTPUT FOR JOB 5363
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
Number of possible TRX instances for attribute lapdOverloadTrxList increased to 48
Example of Command Execution:
Get BTSM OVERLOAD:NAME=BTSM:0,REQATTL=LAPDOVLT&LAPDOVLTH&
LAPDOVLTRXLL;
GET BTSM SWL
GET BTSM SWL
NAME=BTSM:0..0 ,REQATTL=SWLCFID, SWLCVER,
SBSCSLCV;
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h GET BTSM SWL
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes related to the BTSM (BTS Site Manager).
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
SWLCFID
swLoadCurrentFileId
SWLCVER
swLoadCurrentFileVersion
SBSCSLCV
superordinateBscSwLoadCurrentVersion
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of get swl
command is the following:
A50016-G5100-B333-04-7619
Id:0900d805805944aa
173
BTSM
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 178
PC Time&Date: 12:06:19 03/23/2005
NE Time&Date: 13:03:28 09/15/2004
USER NAME:
User_NSN
COMMAND:
Get BTSM SWL:NAME=BTSM:0,REQATTL=SBSCSLCV;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
superordinateBscSwLoadCurrentVersion = "02-08-01-01-00-30_04-12-14"
swLoadCurrentFileId = "hs011713.SWL"
swLoadCurrentFileVersion = "01-04-17-01-26-51_05-02-23"
END OF OUTPUT FOR JOB 178
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
None.
Example of Command Execution:
Get BTSM SWL:NAME=BTSM:0,SBSCSLCV&SWLCFID&SWLCVER;
LOCKREQUEST BTSM
LOCKREQUEST BTSM NAME=BTSM:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h LOCKREQUEST BTSM
Applicability:
Phase 3.
Visibility level: 1.
Command Description:
This command sends a request to the BSC for immediate locking of the BTSM.
Long Names:
NAME
174
Address of the managed object
Id:0900d805805944aa
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSM
System Responses:
Operation Completed
The specified change of administrative state has been perfomed.
JOB: 56
PC Time&Date: 11:57:07 03/23/2005
NE Time&Date: 12:58:42 09/15/2004
USER NAME:
User_NSN
COMMAND:
Lockrequest BTSM:NAME=BTSM:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 56
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs.
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
This command should only be used when the system is in real danger. The
Shutdown command is preferred
Example of Command Execution:
Lockrequest BTSM:NAME=BTSM:0;
SET BTSM
SET BTSM
NAME=BTSM:0..0 [,ABISLKSAT=] [,ABISTIME=] [,TEI=];
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h SET BTSM
Applicability:
Phase 2.
Visibility level: 2.
Command Description:
This command sets the attributes of the BTS_Site_Manager (BTSM). The BTS Site
Manager represents the O&M functionality related to a site and not to any specific BTS.
A50016-G5100-B333-04-7619
Id:0900d805805944aa
175
BTSM
BS-4x / 82 II / 240 / 241 / 240XL commands
A site is a logical grouping of one or more BTS at a single physical location with common
management needs. This configuration has to match with the related LPDLM-Object in
the BSC.
Long Names:
NAME
Address of the managed object
ABISLKSAT
sAbisLinkSatellited
ABISTIME
sAbisExternalTime
TEI
tei
System Responses:
Operation Completed
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
JOB: 177
PC Time&Date: 12:06:04 03/23/2005
NE Time&Date: 13:07:40 09/15/2004
USER NAME:
User_NSN
COMMAND:
Set BTSM:NAME=BTSM:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 177
Operation Failed
The specified attributes have not been set. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible.
Application Guidelines:
176
TEI is a prerequisite for establishing the connection to the BSC
The BPortNumber must be the same for all abisChannel attributes of the CHAN
instances of the same TRX
Without defining TEI the transition from Phase 2 to Phase 3 is not possible. They are
two of the "Minimal Parameters" of the BTSE
TEI has to have the same value on BTS and on BSC (LPDLM)
If, for TEI, the signalling time slot is correct, but one side has a wrong TEI configured
the layer 2 will be established, and a related message will be received that the TEI
is wrong. Additionally, link disconnection without locking the BTSM is permitted
Id:0900d805805944aa
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
BTSM
Except for timeslot 0 (Synchronization Time Slot) all time slots can be used to
support both, traffic or signalling channels
The ABISTIME attribute is useful for longer operation on site. In transition from
Phase 2 to Phase 3 this attribute is overwritten by the BSC.
Setting of ABISLKSAT in the BTSE and of LPDLMSAT in BSC must be homogenous:
- terrestrialConnection (corresponds in the BSC to 'LPDLMSAT=FALSE')
- satelliteConnection (corresponds in the BSC to 'LPDLMSAT=TRUE')
Example of Command Execution:
Set BTSM:NAME=BTSM:0,ABISLKSAT=terrestrialConnection,
ABISTIME=1999-Oct-28-18-0-0,TEI=0;
SHUTDOWN BTSM
SHUTDOWN BTSM
NAME=BTSM:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h SHUTDOWN BTSM
Applicability:
Phase 3.
Visibility level: 1.
Command Description:
This command will not allow new telecom traffic to be transferred to the BTSM (no
incoming handover, no paging, no call set up). When all calls are terminated, the transfer
to "Locked" will be performed automatically.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed.
JOB: 59
PC Time&Date: 11:57:24 03/23/2005
NE Time&Date: 12:58:59 09/15/2004
USER NAME:
User_NSN
COMMAND:
Shutdown BTSM:NAME=BTSM:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
A50016-G5100-B333-04-7619
Id:0900d805805944aa
177
BTSM
BS-4x / 82 II / 240 / 241 / 240XL commands
END OF OUTPUT FOR JOB 59
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs.
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
None.
Example of Command Execution:
Shutdown BTSM:NAME=REMINV:0;
UNLOCKREQUEST BTSM
UNLOCKREQUEST
BTSM
NAME=BTSM:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h UNLOCKREQUEST
BTSM
Applicability:
Phase 3.
Visibility level: 1.
Command Description:
This command sends a request to the BSC for the unlocking of the BTSM. The BTSM
will be able to handle telecom traffic.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed.
JOB: 57
PC Time&Date: 11:57:14 03/23/2005
NE Time&Date: 12:58:49 09/15/2004
USER NAME:
178
User_NSN
Id:0900d805805944aa
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COMMAND:
SW RELEASE:
BTSM
Unlockrequest BTSM:NAME=BTSM:0;
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 57
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs.
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
Unlocking of BTSM causes a full BTS-Alignment
In case of issuing BTSE configuration commands during an alignment, a new alignment will be started
Example of Command Execution:
Unlockrequest BTSM:NAME=BTSM:0;
A50016-G5100-B333-04-7619
Id:0900d805805944aa
179
CESPW
BS-4x / 82 II / 240 / 241 / 240XL commands
CESPW
The new HMO CESPW represents one UDP stream which is both received and simultaneously transmitted to the peer.
The object is introduced for the following purposes:
setting of the UPD port numbers
configuration of the mapping between CESoPSN payload and internal TDM
highways
adjustment of packetization latency (transmission) and jitter buffer (reception)
CREATE CESPW
CREATE CESPW
NAME=CESPW:0..7 [,PWNAME=] ,LOCLUDP= ,PEERUDPPORT= ,TDMAP= [,PKTLAT=] [,MAXPDV=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESPW h CREATE
CESPW
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the CESPW to the BTSE data base.
Long Names:
NAME
Address of the managed object
PWNAME
pwName
LOCLUDP
localUdpPort
PEERUDPPORT
peerUdpPort
TDMAP
tdmMapping
PKTLAT
packetizationLatency
MAXPDV
maxPdv(ms)
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 60
PC Time&Date: 02.04.2008 09:10:46 +02:00
180
Id:0900d805805944ac
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CESPW
NE Time&Date: 01.01.1990 18:26:24 +00:00
USER NAME:
User_Robert
COMMAND:
Create CESPW:NAME=CESPW:0,LOCLUDP=49200,PEERUDP=49200,TDMAP=1-2-3-4-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;
SW RELEASE:
01-04-19-01-08-CR_08-03-31
COMMAND RESULT: Operation successful
localUdpPort = 49200
peerUdpPort = 49200
tdmMapping =
pTs1 = 1
pTs2 = 2
pTs3 = 3
pTs4 = 4
pTs5 = 0
pTs6 = 0
pTs7 = 0
pTs8 = 0
pTs9 = 0
pTs10 = 0
pTs11 = 0
pTs12 = 0
pTs13 = 0
pTs14 = 0
pTs15 = 0
pTs16 = 0
pTs17 = 0
pTs18 = 0
pTs19 = 0
pTs20 = 0
pTs21 = 0
pTs22 = 0
pTs23 = 0
pTs24 = 0
pTs25 = 0
pTs26 = 0
pTs27 = 0
A50016-G5100-B333-04-7619
Id:0900d805805944ac
181
CESPW
BS-4x / 82 II / 240 / 241 / 240XL commands
pTs28 = 0
pTs29 = 0
pTs30 = 0
pTs31 = 0
END OF OUTPUT FOR JOB 60
Operation Failed
None.
Application Guidelines:
The creation of a CESPW instance is rejected if no CESTUNNEL has been created
before.
Example of Command Execution:
Create CESPW:NAME=CESPW:0,LOCLUDP=49200,MAXPDV=16,PEERUDPPORT=49200,PKTLAT=m1000,PWNAME="trial1",TDMAP=0-0-0-0-0-0-0-0-0-0-0-0-00-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0-0;
DELETE CESPW
DELETE CESPW
NAME=CESPW:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESPW h DELETE
CESPW
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the CESPW from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of delete command
is the following:
JOB: 503
182
Id:0900d805805944ac
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CESPW
PC Time&Date: 05.06.2008 13:45:42 +02:00
NE Time&Date: 01.01.1990 00:42:25 +00:00
USER NAME:
User_Robert
COMMAND:
Delete CESPW:NAME=CESPW:7;
SW RELEASE:
01-04-19-01-09-ZS_08-06-05
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 503
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Delete CESPW:NAME=CESPW:0;
GET CESPW
GET CESPW
NAME=CESPW:0..7 [,REQATTL=ALS, AST, AVS, OST,
PRS, RELFUNCOBJ, PWNAME, LOCLUDP, PEERUDPPORT, TDMAP, PKTLAT, MAXPDV];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESPW h GET
CESPW
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the CESPW.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
A50016-G5100-B333-04-7619
relatedFuncObjects
Id:0900d805805944ac
183
CESPW
BS-4x / 82 II / 240 / 241 / 240XL commands
PWNAME
pwName
LOCLUDP
localUdpPort
PEERUDPPORT
peerUdpPort
TDMAP
tdmMapping
PKTLAT
packetizationLatency
MAXPDV
maxPdv(ms)
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 9
PC Time&Date: 02.10.2008 09:06:43 +02:00
NE Time&Date: 02.10.2008 06:50:36 +01:00
USER NAME:
User_Robert
COMMAND:
Get CESPW:NAME=CESPW:0;
SW RELEASE:
01-04-19-01-12-ZT_08-09-29
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
operationalState = ENABLED
proceduralStatus = NULL
relatedFuncObjects = Null
pwName = "Null"
localUdpPort = 49300
peerUdpPort = 49300
tdmMapping =
pTs1 = 1
pTs2 = 2
pTs3 = 3
pTs4 = 4
pTs5 = 5
pTs6 = 0
pTs7 = 0
184
Id:0900d805805944ac
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CESPW
pTs8 = 0
pTs9 = 0
pTs10 = 0
pTs11 = 0
pTs12 = 0
pTs13 = 0
pTs14 = 0
pTs15 = 0
pTs16 = 0
pTs17 = 0
pTs18 = 0
pTs19 = 0
pTs20 = 0
pTs21 = 0
pTs22 = 0
pTs23 = 0
pTs24 = 0
pTs25 = 0
pTs26 = 0
pTs27 = 0
pTs28 = 0
pTs29 = 0
pTs30 = 0
pTs31 = 0
packetizationLatency = m1000
maxPdv(ms) = 2.000
END OF OUTPUT FOR JOB 9
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Get CESPW:NAME=CESPW:0;REQATTL=ALS&AST&AVS&OST&PRS&RELFUNCOBJ&LOCLUDP&MAXPDV&PEERUDPPORT&PKTLAT&PWNAME&TDMAP;
LOCK CESPW
LOCK CESPW
A50016-G5100-B333-04-7619
NAME=CESPW:0..7;
Id:0900d805805944ac
185
CESPW
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESPW h LOCK
CESPW
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of CESPW.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 29
PC Time&Date: 05.06.2008 13:06:00 +02:00
NE Time&Date: 01.01.1990 00:02:44 +00:00
USER NAME:
User_Robert
COMMAND:
Lock CESPW:NAME=CESPW:0;
SW RELEASE:
01-04-19-01-09-ZS_08-06-03
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 29
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Lock CESPW:NAME=CESPW:0;
186
Id:0900d805805944ac
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CESPW
SET CESPW
SET CESPW
NAME=CESPW:0..7 [,PWNAME=] [,LOCLUDP=] [,PEERUDPPORT=] [,TDMAP=] [,PKTLAT=] [,MAXPDV=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESPW h SET
CESPW
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command sets the attributes of CESPW to the BTSE data base.
Long Names:
NAME
Address of the managed object
PWNAME
pwName
LOCLUDP
localUdpPort
PEERUDPPORT
peerUdpPort
TDMAP
tdmMapping
PKTLAT
packetizationLatency
MAXPDV
maxPdv(ms)
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
JOB: 32
PC Time&Date: 05.06.2008 13:06:09 +02:00
NE Time&Date: 01.01.1990 00:02:53 +00:00
USER NAME:
User_Robert
COMMAND:
Set CESPW:NAME=CESPW:0,MAXPDV=0.125;
SW RELEASE:
01-04-19-01-09-ZS_08-06-03
COMMAND RESULT: Operation successful
maxPdv = 0.125
A50016-G5100-B333-04-7619
Id:0900d805805944ac
187
CESPW
BS-4x / 82 II / 240 / 241 / 240XL commands
END OF OUTPUT FOR JOB 32
Operation Failed
None.
Application Guidelines:
Any modification of the mapping is allowed only if the CESPW has been previously
locked.
Example of Command Execution:
Set CESPW:NAME=CESPW:0,LOCLUDP=49200,PEERUDP=49200,TDMAP=1-2-34-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;
UNLOCK CESPW
UNLOCK CESPW
NAME=CESPW:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESPW h UNLOCK
CESPW
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of CESPW.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 84
PC Time&Date: 05.06.2008 13:17:19 +02:00
NE Time&Date: 01.01.1990 00:14:03 +00:00
USER NAME:
User_Robert
COMMAND:
Unlock CESPW:NAME=CESPW:0;
SW RELEASE:
01-04-19-01-09-ZS_08-06-03
COMMAND RESULT: Operation successful
188
Id:0900d805805944ac
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CESPW
administrativeState = Unlocked
END OF OUTPUT FOR JOB 84
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Unlock CESPW:NAME=CESPW:0;
A50016-G5100-B333-04-7619
Id:0900d805805944ac
189
CESTUNNEL
BS-4x / 82 II / 240 / 241 / 240XL commands
CESTUNNEL
This object represents the PSN tunnel. As the BTSE is uniquely connected to one BSC
there is only one CESTUNNEL instance per BTSE. The CESTUNNEL object is introduced for the following purposes:
setting of the local (BTSE) and peer IP address
setting of attributes which apply for all pseudo wires
CREATE CESTUNNEL
CREATE CESTUNNEL NAME=CESTUNNEL:0..0 ,LOCALADDR= ,PEERADDR=
[,VLANID=] [,LOSPKTTH=] [,ALRMPERT=] [,ALRMCLET=]
[,NTWTYPC=] [,PNGF=] [,PNGPKT=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESTUNNEL h
CREATE CESTUNNEL
Applicability:
Phase 2.
Visibility level: 2.
Command Description:
This command adds the CESTUNNEL to the BTSE data base.
Long Names:
NAME
Address of the managed object
LOCALADDR
localAddress
PEERADDR
peerAddress
VLANID
vlanId
LOSPKTTH
lostPacketThreshold
ALRMPERT
alarmPersistencyTime
ALRMCLET
alarmClearanceTime
NTWTYPC
networkTypeCompensation
PNGF
pingFrequency
PNGPKT
pingPacketSize
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
190
Id:0900d805805944ae
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CESTUNNEL
JOB: 59
PC Time&Date: 18.04.2008 10:07:46 +02:00
NE Time&Date: 01.01.1990 00:17:52 +00:00
USER NAME:
User_Paul
COMMAND:
Create CESTUNNEL:NAME=CESTUNNEL:0,LOCLADR="192.168.3.23", PEERADR="192.168.3.24";
SW RELEASE:
01-04-19-01-07-01_08-04-03
COMMAND RESULT: Operation successful
localAddress = "192.168.3.23"
peerAddress = "192.168.3.24"
END OF OUTPUT FOR JOB 59
Operation Failed
None.
Application Guidelines:
The creation of the CESTUNNEL is rejected if no ETHCON object exists.
Example of Command Execution:
Create CESTUNNEL:NAME=CESTUNNEL:0,ALRMCLET=10,ALRMPERT=3,LOCALADDR="192.168.3.23",LOSPKTTH=1,NTWTYPC=255,NTWTYPC=0,PEERADDR="192.168.3.25",PNGF=0,PNGPKT=TRAFFIC,VLANID=<NULL
>
DELETE CESTUNNEL
DELETE CESTUNNEL
NAME=CESTUNNEL:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESTUNNEL h
DELETE CESTUNNEL
Applicability:
Phase 2.
Visibility level: 2.
Command Description:
This command deletes the CESTUNNEL from the BTSE data base.
A50016-G5100-B333-04-7619
Id:0900d805805944ae
191
CESTUNNEL
BS-4x / 82 II / 240 / 241 / 240XL commands
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
None.
Operation Failed
None.
Application Guidelines:
CESTUNNEL deletion is rejected if a CESPW object exists.
Example of Command Execution:
Delete CESTUNNEL:NAME=CESTUNNEL:0;
GET CESTUNNEL
GET CESTUNNEL
NAME=CESTUNNEL:0..0 [,REQATTL=ALS, AST, AVS,
OST, PRS, RELFUNCOBJ, LOCALADDR, PEERADDR,
VLANID, LOSPKTTH, ALRMPERT, ALRMCLET,
NTWTYPC, PNGF, PNGPKT];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESTUNNEL h GET
CESTUNNEL
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the CESTUNNEL.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
192
relatedFuncObjects
LOCALADDR
localAddress
PEERADDR
peerAddress
VLANID
vlanId
LOSPKTTH
lostPacketThreshold
Id:0900d805805944ae
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CESTUNNEL
ALRMPERT
alarmPersistencyTime
ALRMCLET
alarmClearanceTime
NTWTYPC
networkTypeCompensation
PNGF
pingFrequency
PNGPKT
pingPacketSize
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 75
PC Time&Date: 21.08.2008 13:48:47 +02:00
NE Time&Date: 21.08.2008 13:38:17 +01:00
USER NAME:
User_Paul
COMMAND:
Get CESTUNNEL:NAME=CESTUNNEL:0;
SW RELEASE:
01-04-19-01-12-ZT_08-08-20
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Locked
availabilityStatus = NULL
operationalState = ENABLED
proceduralStatus = NULL
relatedFuncObjects = Null
localAddress = "192.168.3.23"
peerAddress = "192.168.3.25"
vlanId = Null
lostPacketThreshold = 1
alarmPersistencyTime = 3
alarmClearanceTime = 10
networkTypeCompensation = 0
pingFrequency = 0
pingPacketSize = TRAFFIC
END OF OUTPUT FOR JOB 75
Operation Failed
A50016-G5100-B333-04-7619
Id:0900d805805944ae
193
CESTUNNEL
BS-4x / 82 II / 240 / 241 / 240XL commands
None.
Application Guidelines:
None.
Example of Command Execution:
Get
CESTUNNEL:NAME=CESTUNNEL:0,REQATTL=ALS&AST&AVS&OST&PRS&RELFUNCOBJ&ALRMCLET&ALRMPERT&LOCALADDR&LOSPKTTH&NTWTYPC&PEERADDR&PNGF&PNGPKT&VLANID;
LOCK CESTUNNEL
LOCK CESTUNNEL
NAME=CESTUNNEL:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESTUNNEL h LOCK
CESTUNNEL
Applicability:
Phase 2.
Visibility level: 1.
Command Description:
This command changes the administrative state of CESTUNNEL.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 39
PC Time&Date: 05.05.2008 09:07:05 +02:00
NE Time&Date: 05.05.2008 09:03:21 +01:00
USER NAME:
User_Paul
COMMAND:
Lock CESTUNNEL:NAME=CESTUNNEL:0;
SW RELEASE:
01-04-19-01-07-ZT_08-04-30
COMMAND RESULT: Operation successful
administrativeState = Locked
194
Id:0900d805805944ae
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CESTUNNEL
END OF OUTPUT FOR JOB 39
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Lock CESTUNNEL:NAME=CESTUNNEL:0;
SET CESTUNNEL
SET CESTUNNEL
NAME=CESTUNNEL:0..0 [,LOCALADDR=] [,PEERADDR=]
[,VLANID=] [,LOSPKTTH=] [,ALRMPERT=] [,ALRMCLET=]
[,NTWTYPC=] [,PNGF=] [,PNGPKT=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESTUNNEL h SET
CESTUNNEL
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command sets the attributes of CESTUNNEL.
Long Names:
NAME
Address of the managed object
LOCALADDR
localAddress
PEERADDR
peerAddress
VLANID
vlanId
LOSPKTTH
lostPacketThreshold
ALRMPERT
alarmPersistencyTime
ALRMCLET
alarmClearanceTime
NTWTYPC
networkTypeCompensation
PNGF
pingFrequency
PNGPKT
pingPacketSize
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
A50016-G5100-B333-04-7619
Id:0900d805805944ae
195
CESTUNNEL
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 77
PC Time&Date: 21.08.2008 13:49:06 +02:00
NE Time&Date: 21.08.2008 13:38:36 +01:00
USER NAME:
User_Paul
COMMAND:
Set CESTUNNEL:NAME=CESTUNNEL:0,VLANID=<NULL>;
SW RELEASE:
01-04-19-01-12-ZT_08-08-20
COMMAND RESULT: Operation successful
vlanId = Null
END OF OUTPUT FOR JOB 77
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Set CESTUNNEL:NAME=RACK:0/CESTUNNEL:0,ALRMCLET=10,ALRMPERT=3,LOCALADDR="123.20.254.36",LOSPKTTH=1,NTWTYPC=255,NTWTYPC=255,PEERADDR="156.14.26.2",PNGF=0,PNGPKT=TRAFFIC,VLANID=0
UNLOCK CESTUNNEL
UNLOCK CESTUNNEL NAME=CESTUNNEL:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h CESTUNNEL h
UNLOCK CESTUNNEL
Applicability:
Phase 2.
Visibility level: 1.
Command Description:
This command changes the administrative state of CESTUNNEL.
Long Names:
NAME
196
Address of the managed object
Id:0900d805805944ae
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CESTUNNEL
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 47
PC Time&Date: 05.05.2008 09:08:17 +02:00
NE Time&Date: 05.05.2008 09:04:33 +01:00
USER NAME:
User_Paul
COMMAND:
Unlock CESTUNNEL:NAME=CESTUNNEL:0;
SW RELEASE:
01-04-19-01-07-ZT_08-04-30
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 47
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Unlock CESTUNNEL:NAME=CESTUNNEL:0
A50016-G5100-B333-04-7619
Id:0900d805805944ae
197
CHAN
BS-4x / 82 II / 240 / 241 / 240XL commands
CHAN
The CHAN object represents the radio time slot in which the radio carrier is subdivided
into time sharing; it can be differently configured depending on its usage for the telephone application software (full rate or half rate traffic channels, dedicated or common
control channels).
GET CHAN
GET CHAN
NAME=BTS:0..11/TRX:0..23/CHAN:0..7 [,REQATTL=AST,
AVS, CHTYPE, EXTMODE, HSN, MAIO, MOBALLOC, OST,
RELEQUIPOBJ, TSC];
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h BTS h TRX h CHAN
h GET CHAN
Applicability:
Phase 3.
Visibility level: 0.
Command Description:
This command displays the physical radio channel with its specific attributes which
allows logical channels to be mapped onto physical radio channels.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
AST
administrativeState
AVS
availabilityStatus
CHTYPE
channelCombination
EXTMODE
extendedMode
HSN
hoppingSequenceNumber
MAIO
maio
MOBALLOC
arfcnList
OST
operationalState
RELEQUIPOBJ
TSC
relatedEquipObjects
trainingSequenceCode
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 17
198
Id:0900d805805944b0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CHAN
PC Time&Date: 11:33:17 03/23/2005
NE Time&Date: 11:31:08 09/15/2004
USER NAME:
User_n
COMMAND:
Get CHAN:NAME=BTS:0/TRX:0/CHAN:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
availabilityStatus = NULL
channelCombination = MAINBCCH
extendedMode = FALSE
hoppingSequenceNumber = 0
maio = 0
arfcnList =
operationalState = ENABLED
relatedEquipObjects =
trainingSequenceCode = TSC_is_BCC_of_BSIC
END OF OUTPUT FOR JOB 17
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
None.
Example of Command Execution:
Get CHAN:NAME=BTS:0/TRX:0/CHAN:0,REQATTL=AST&AVS&CHTYPE&
EXTMODE&HSN&MAIO&MOBALLOC&OST&RELEQUIPOBJ&TSC;
A50016-G5100-B333-04-7619
Id:0900d805805944b0
199
COBA
BS-4x / 82 II / 240 / 241 / 240XL commands
COBA
The COBA module controls of the entire BTSE, generates the system clocks, provides
for up to 2 Abis-interfaces to BSC or other BTSEs, routes the Abis-data to up to 8 Carrier
Agents, provides for an interface to the LMT/OTP, handles and processes the O&Mmessages.
CREATE COBA
CREATE COBA
NAME=RACK:0..7/COBA:0..1 [,ALRMCOUNTER=]
[,ALRMT1/2/3=] [,EFCUSUP=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h
CREATE COBA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the COBA (Core Basis module) to the BTSE data base.
Long Names:
NAME
Address of the managed object
ALRMCOUNTER
alarmCount
ALRMT1/2/3
alarmTiming1(sec)/alarmTiming2(sec)/alarmTiming3(5 minutes units)
EFCUSUP
enableFcuSupport
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 158
PC Time&Date: 16:45:36 03/23/2005
NE Time&Date: 16:43:30 09/15/2004
USER NAME:
User_Cindy
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
200
Id:0900d80580627a91
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COBA
ChangedConfigurationNotification:
name = RACK:0/COBA:1
ChangeInfo = created
END OF OUTPUT FOR JOB 158
JOB: 159
PC Time&Date: 16:45:36 03/23/2005
NE Time&Date: 16:43:30 09/15/2004
USER NAME:
User_Cindy
COMMAND:
Create COBA:NAME=RACK:0/COBA:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 159
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 71
PC Time&Date: 16:37:54 03/23/2005
NE Time&Date: 16:35:47 09/15/2004
USER NAME:
User_Cindy
COMMAND:
Create COBA:NAME=RACK:0/COBA:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
Object instance unknown (-9)
END OF OUTPUT FOR JOB 71
Application Guidelines:
Only COBA:1 can be created.
A50016-G5100-B333-04-7619
Id:0900d80580627a91
201
COBA
BS-4x / 82 II / 240 / 241 / 240XL commands
Example of Command Execution:
Create COBA:NAME=RACK:0/COBA:1,ALRMCOUNTER=234,ALRMT1=23,
ALRMT2=34,ALRMT3=2, EFCUSUP=TRUE;
DELETE COBA
DELETE COBA
NAME=RACK:0..7/COBA:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h
DELETE COBA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the attributes of the COBA (Core Basis module).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 182
PC Time&Date: 16:48:02 03/23/2005
NE Time&Date: 16:45:56 09/15/2004
USER NAME:
User_Cindy
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/COBA:1
ChangeInfo = deleted
END OF OUTPUT FOR JOB 182
202
Id:0900d80580627a91
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COBA
JOB: 183
PC Time&Date: 16:48:02 03/23/2005
NE Time&Date: 16:45:56 09/15/2004
USER NAME:
User_Cindy
COMMAND:
Delete COBA:NAME=RACK:0/COBA:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 183
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
Only COBA:1 can be deleted
COBA:1 must be locked in Phase 3 before deletion
Example of Command Execution:
Delete COBA:NAME=RACK:0/COBA:1;
GET COBA
GET COBA
NAME=RACK:0..7/COBA:0..1 [,REQATTL=ALRMCOUNTER, ALRMT1/2/3, ALS, AST, AVS, BCPBL, BSWVER,
EFCUSUP, OST, PRS, RELFUNCOBJ, SLOTNO, STDBYST];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h
GET COBA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the COBA (Core Basis module).
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALRMCOUNTER
A50016-G5100-B333-04-7619
alarmCount
Id:0900d80580627a91
203
COBA
BS-4x / 82 II / 240 / 241 / 240XL commands
ALRMT1/2/3
alarmTiming1(sec)/alarmTiming2(sec)/alarmTiming3(5 minutes units)
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
BCPBL
boardCapability
BSWVER
bootSoftwareVersion
EFCUSUP
enableFcuSupport
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
SLOTNO
slotNo
STDBYST
standbyStatus
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 163
USER NAME:
User_Cindy
COMMAND:
Get COBA:NAME=RACK:0/COBA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
acPeriod = 20
alarmCount = 32
alarmTiming1(sec) = 20
alarmTiming2(sec) = 1
alarmTiming3(*5min) = 1 (unit of 5 minutes)
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
boardCapability = twoAbisLines
bootSoftwareVersion = "BTBBCX01.SWI:01-01-11-00-18-00_04-06-13"
enableFcuSupport = FALSE
operationalState = ENABLED
proceduralStatus = NULL
slotNo = leftCOBA
standbyStatus = ProvidingService
204
Id:0900d80580627a91
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COBA
END OF OUTPUT FOR JOB 163
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
COBA:0 is the one with Providing Service Status, COBA:1 is in Standby Status
Example of Command Execution:
Get COBA:NAME=RACK:0/COBA:0,REQATTL=ACPER&ALRMCOUNTER&ALRMT1&ALRMT2&ALRMT3&ALS&AST&AVS&BCPBL&BSWVER&CCLKACC
&EFCUSUP&OST&PRS&SLOTNO&STDBYST;
GETRELATIONSHIP COBA
GETRELATIONSHIP
COBA
NAME=RACK:0..7/COBA:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h
GETRELATIONSHIP COBA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command adds the COBA (Core Basis module) to the BTSE data base.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of getrelationship
command is the following:
JOB: 164
PC Time&Date: 15:08:34 03/23/2005
NE Time&Date: 16:11:29 09/15/2004
USER NAME:
A50016-G5100-B333-04-7619
User_Cindy
Id:0900d80580627a91
205
COBA
BS-4x / 82 II / 240 / 241 / 240XL commands
COMMAND:
Getrelationship COBA:NAME=RACK:0/COBA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 164
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
None.
Example of Command Execution:
Getrelationship COBA:NAME=RACK:0/COBA:0;
GETTEST COBA
GETTEST COBA
NAME=RACK:0..7/COBA:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h
GETTEST COBA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the COBA test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 187
PC Time&Date: 12:07:21 03/23/2005
NE Time&Date: 13:08:54 09/15/2004
USER NAME:
206
User_Cindy
Id:0900d80580627a91
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COMMAND:
SW RELEASE:
COBA
Gettest COBA:NAME=RACK:0/COBA:0;
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/COBA:0
testMonitor =
phaseId = PreliminaryTestsCoba
phaseStatus = Running
phaseId = CheckAlarmStatusCoba
phaseStatus = Waiting
phaseId = EndTestCoba
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
END OF OUTPUT FOR JOB 187
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest COBA:NAME=RACK:0/COBA:0, REQATTL=MORT&TESTMON&
TESTOUT&TESTST;
A50016-G5100-B333-04-7619
Id:0900d80580627a91
207
COBA
BS-4x / 82 II / 240 / 241 / 240XL commands
LOCK COBA
LOCK COBA
NAME=RACK:0..7/COBA:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h
LOCK COBA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the COBA (Core Basis module).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 166
PC Time&Date: 16:46:53 03/23/2005
NE Time&Date: 16:44:47 09/15/2004
USER NAME:
User_Cindy
COMMAND:
Lock COBA:NAME=RACK:0/COBA:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 166
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 167
PC Time&Date: 16:46:53 03/23/2005
NE Time&Date: 16:44:47 09/15/2004
208
Id:0900d80580627a91
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COBA
USER NAME:
User_Cindy
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/COBA:1
Administrative State = LOCKED
Notification Identifier = 551
END OF OUTPUT FOR JOB 167
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
Lock COBA:0 only in Phase 2
Example of Command Execution:
Lock COBA:NAME=RACK:0/COBA:0;
PERFTEST COBA
PERFTEST COBA
NAME=RACK:0..7/COBA:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h
PERFTEST COBA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in COBA.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSEP.
JOB: 188
A50016-G5100-B333-04-7619
Id:0900d80580627a91
209
COBA
BS-4x / 82 II / 240 / 241 / 240XL commands
PC Time&Date: 12:06:51 03/23/2005
NE Time&Date: 13:08:26 09/15/2004
USER NAME:
User_Cindy
COMMAND:
Perftest COBA:NAME=RACK:0/COBA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/COBA:0
tO = BTSETEST:2
END OF OUTPUT FOR JOB 188
JOB: 189
PC Time&Date: 12:07:23 03/23/2005
NE Time&Date: 13:08:53 09/15/2004
USER NAME:
User_Cindy
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:2
ChangeInfo = created
END OF OUTPUT FOR JOB 189
JOB: 190
PC Time&Date: 12:07:38 03/23/2005
NE Time&Date: 13:09:02 09/15/2004
USER NAME:
User_Cindy
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
210
Id:0900d80580627a91
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COBA
CHANGED STATE EVENT REPORT:
NAME = RACK:0/COBA:0
Operational State = ENABLED
Availability Status = NULL_value
Standby Status = Cold_Standby
Notification Identifier = 164
END OF OUTPUT FOR JOB 190
JOB: 191
PC Time&Date: 12:07:52 03/23/2005
NE Time&Date: 13:09:34 09/15/2004
USER NAME:
User_Cindy
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:2
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/COBA:0
executedPhases =
PreliminaryTestsCoba
BootEepromTestCoba
SerialEepromTestCoba
EndTestCoba
END OF OUTPUT FOR JOB 191
JOB: 192
PC Time&Date: 12:08:04 03/23/2005
NE Time&Date: 13:09:28 09/15/2004
USER NAME:
A50016-G5100-B333-04-7619
User_Cindy
Id:0900d80580627a91
211
COBA
BS-4x / 82 II / 240 / 241 / 240XL commands
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:2
ChangeInfo = deleted
END OF OUTPUT FOR JOB 192
The test results will be displayed at the end of the test phases.
Result TEST:
name =
TEST:<n>
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
....
skippedPhases
212
Id:0900d80580627a91
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COBA
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: Message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
In phase 3 COBA must be locked previous to the command
Perftest for COBA:0 in phase 2 only
Example of Command Execution:
Perftest COBA:NAME=RACK:0/COBA:0;
SET COBA
SET COBA
NAME=RACK:0..7/COBA:0..1 [,ALRMCOUNTER=]
[,ALRMT1/2/3=] [,EFCUSUP=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h SET
COBA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command permits modification of the attributes of the COBA (Core Basis module).
Long Names:
NAME
Address of the managed object
ALRMCOUNTER
alarmCount
ALRMT1/2/3
alarmTiming1(sec)/alarmTiming2(sec)/alarmTiming3(5 minutes units)
EFCUSUP
enableFcuSupport
System Responses:
Operation Completed
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
A50016-G5100-B333-04-7619
Id:0900d80580627a91
213
COBA
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 172
PC Time&Date: 16:47:25 03/23/2005
NE Time&Date: 16:45:19 09/15/2004
USER NAME:
User_Cindy
COMMAND:
Set COBA:NAME=RACK:0/COBA:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 172
Operation Failed
The specified attributes have not been set. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible.
Application Guidelines:
The alarm evaluation on BTSE for the layer 1 is based on an "Errored Second"
concept. I.e.: If an error is found active (counted every 2 msec.) for x times (x = 5 for
"No signal", "AIS", "Loss of frame alignment ...) within 1 second, the whole second
is declared faulty otherwise the second is declared as "good". If one "Errored
Second" is detected, the subsequent seconds will be also declared faulty until no
error is detected within one second. This means that the layer 1 alarm handling is
very sensitive. With the default setting of "ALRMT2" which is 1 second a short interruption of 10 msec will cause an alarm generated by the BTSE. In order to increase
the tolerance of the BTSE layer 1 alarm handling against short interruptions on the
lines, the operator can change the value of the timer "ALRMT2" from the default
setting (1 second) to a higher value (e.g. 2 seconds). Nevertheless if the BTSE generates a layer 1 alarm no further actions are performed. Call processing is not inhibited as long as the layer 2 is up or the BSC does not declare the line disabled.
The behaviour of COBA2P8 and COBA4P12 is different, when attribute enableFCUSupport is TRUE and POWER OFF/ON of the COBA board is done. In case of
COBA2P8 the alarm 32805 - DM request a core reset is visible. In case of
COBA4P12 no alarm is visible
Example of Command Execution:
Set COBA:NAME=RACK:0/COBA:0,ACPER=20&ALRMCOUNTER=32,ALRMT1=20,
ALRMT2=2,ALRMT3=1,EFCUSUP=TRUE;
STOPTEST COBA
STOPTEST COBA
NAME=RACK:0..7/COBA:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h
STOPTEST COBA
214
Id:0900d80580627a91
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COBA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
...
.
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
phaseId =
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
Application Guidelines:
None.
Example of Command Execution:
Stoptest COBA:NAME=RACK:0/COBA:0;
A50016-G5100-B333-04-7619
Id:0900d80580627a91
215
COBA
BS-4x / 82 II / 240 / 241 / 240XL commands
SWITCH COBA
SWITCH COBA
NAME=RACK:0..7/COBA:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h
SWITCH COBA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to switch to the standby copy of COBA.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
JOB: 60
PC Time&Date: 11:57:24 03/23/2005
NE Time&Date: 12:58:59 09/15/2004
USER NAME:
User_Cindy
COMMAND:
Switch COBA:NAME=RACK:0/COBA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 60
Operation Failed
JOB: 61
PC Time&Date: 11:57:31 03/23/2005
NE Time&Date: 12:59:06 09/15/2004
USER NAME:
User_Cindy
COMMAND:
Switch COBA:NAME=RACK:0/COBA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
216
Id:0900d80580627a91
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COBA
no redundant core board available (-173)
END OF OUTPUT FOR JOB 61
Application Guidelines:
Only COBA:0 can be switched
No redundancy present in BS82II (the command is not applicable)
Example of Command Execution:
Switch COBA:NAME=RACK:0/COBA:0;
UNLOCK COBA
UNLOCK COBA
NAME=RACK:0..7/COBA:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COBA h
UNLOCK COBA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the COBA (Core Basis module).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 173
PC Time&Date: 16:47:33 03/23/2005
NE Time&Date: 16:45:27 09/15/2004
USER NAME:
User_Cindy
COMMAND:
Unlock COBA:NAME=RACK:0/COBA:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
A50016-G5100-B333-04-7619
Id:0900d80580627a91
217
COBA
BS-4x / 82 II / 240 / 241 / 240XL commands
END OF OUTPUT FOR JOB 173
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 174
PC Time&Date: 16:47:33 03/23/2005
NE Time&Date: 16:45:27 09/15/2004
USER NAME:
User_Cindy
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/COBA:1
Administrative State = UNLOCKED
Notification Identifier = 556
END OF OUTPUT FOR JOB 174
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
Unlock COBA:0 only in phase 2
Example of Command Execution:
Unlock COBA:NAME=RACK:0/COBA:0;
218
Id:0900d80580627a91
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COBAETHINTF
COBAETHINTF
The object represents the Ethernet interface of the new COBA which is connected to the
Zarlink device. It is introduced to configure/retrieve Ethernet interface specific information (similar to UNIX eth<x>) and to indicate state information.
The object is automatically created if a new COBA with CES support is equipped.
GET COBAETHINTF
GET COBAETHINTF
NAME=COBAETHINTF:0..0 [,REQATTL=ALS, AST, AVS,
OST, PRS, RELFUNCOBJ, MACADDR, TYPOFETH];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h COBAETHINTF h GET
COBAETHINTF
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the COBAETHINTF.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
MACADDR
macAddress
TYPOFETH
typeOfEthernet
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 65
PC Time&Date: 02.04.2008 09:11:51 +02:00
NE Time&Date: 01.01.1990 18:27:29 +00:00
USER NAME:
A50016-G5100-B333-04-7619
User_Ross
Id:0900d805805944b4
219
COBAETHINTF
BS-4x / 82 II / 240 / 241 / 240XL commands
COMMAND:
Get COBAETHINTF:NAME=COBAETHINTF:0;
SW RELEASE:
01-04-19-01-08-CR_08-03-31
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
operationalState = ENABLED
proceduralStatus = NULL
macAddress = "08:00:06:78:64:63"
typeOfEthernet = ethernet_II
END OF OUTPUT FOR JOB 65
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Get COBAETHINTF:NAME=COBAETHINTF:0,
REQATTL=ALS&AST&AVS&OST&PRS&RELFUNCOBJ& MACADDR&TYPOFETH;
LOCK COBAETHINTF
LOCK COBAETHINTF
NAME=COBAETHINTF:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h COBAETHINTF h
LOCK COBAETHINTF
Applicability:
Phase 2.
Visibility level: 1.
Command Description:
This command changes the administrative state of COBAETHINTF.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
220
Id:0900d805805944b4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COBAETHINTF
JOB: 89
PC Time&Date: 05.06.2008 13:18:01 +02:00
NE Time&Date: 01.01.1990 00:14:45 +00:00
USER NAME:
User_Ross
COMMAND:
Lock COBAETHINTF:NAME=COBAETHINTF:0;
SW RELEASE:
01-04-19-01-09-ZS_08-06-03
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 89
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Lock COBAETHINTF:NAME=COBAETHINTF:0;
SET COBAETHINTF
SET COBAETHINTF
NAME=COBAETHINTF:0..0 [,TYPOFETH=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h COBAETHINTF h SET
COBAETHINTF
Applicability:
Phase 2.
Visibility level: 2.
Command Description:
This command sets the attributes of COBAETHINTF.
Long Names:
NAME
Address of the managed object
TYPOFETH
typeOfEthernet
System Responses:
Operation Completed
A50016-G5100-B333-04-7619
Id:0900d805805944b4
221
COBAETHINTF
BS-4x / 82 II / 240 / 241 / 240XL commands
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
JOB: 35
PC Time&Date: 11.02.2008 11:34:29 +01:00
NE Time&Date: 01.01.1990 00:40:35 +00:00
USER NAME:
User_Ross
COMMAND:
Set COBAETHINTF:NAME=COBAETHINTF:0,TETH=ethernet_II;
SW RELEASE:
01-04-19-01-01-CR_08-01-11
COMMAND RESULT: Operation successful
typeOfEthernet = ethernet_II
END OF OUTPUT FOR JOB 35
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Set COBAETHINTF:NAME=COBAETHINTF:0,TYPOFETH=ethernet_II;
UNLOCK COBAETHINTF
UNLOCK
COBAETHINTF
NAME=COBAETHINTF:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h COBAETHINTF h
UNLOCK COBAETHINTF
Applicability:
Phase 2.
Visibility level: 1.
Command Description:
This command changes the administrative state of COBAETHINTF.
Long Names:
NAME
222
Address of the managed object
Id:0900d805805944b4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COBAETHINTF
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 98
PC Time&Date: 05.06.2008 13:18:14 +02:00
NE Time&Date: 01.01.1990 00:14:58 +00:00
USER NAME:
User_Ross
COMMAND:
Unlock COBAETHINTF:NAME=COBAETHINTF:0;
SW RELEASE:
01-04-19-01-09-ZS_08-06-03
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 98
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Unlock COBAETHINTF:NAME=COBAETHINTF:0;
A50016-G5100-B333-04-7619
Id:0900d805805944b4
223
COSA
BS-4x / 82 II / 240 / 241 / 240XL commands
COSA
The COSA (Core Satellite Interface module) object is the core controller expansion unit
and it is contained in the base rack only.
CREATE COSA
CREATE COSA
NAME=RACK:0..7/COSA:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COSA h
CREATE COSA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the COSA (Core Satellite interface module) to the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 146
PC Time&Date: 16:44:39 03/23/2005
NE Time&Date: 16:42:33 09/15/2004
USER NAME:
User_Ross
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/COSA:1
ChangeInfo = created
END OF OUTPUT FOR JOB 146
224
Id:0900d805805944b6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COSA
JOB: 147
PC Time&Date: 16:44:39 03/23/2005
NE Time&Date: 16:42:33 09/15/2004
USER NAME:
User_Ross
COMMAND:
Create COSA:NAME=RACK:0/COSA:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 147
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 70
PC Time&Date: 16:37:54 03/23/2005
NE Time&Date: 16:35:47 09/15/2004
USER NAME:
User_Ross
COMMAND:
Create COSA:NAME=RACK:0/COSA:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
Object instance unknown (-9)
END OF OUTPUT FOR JOB 70
Application Guidelines:
No COSA creation in BS82II
Example of Command Execution:
Create COSA:NAME=RACK:0/COSA:0;
DELETE COSA
DELETE COSA
A50016-G5100-B333-04-7619
NAME=RACK:0..7/COSA:0..1;
Id:0900d805805944b6
225
COSA
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COSA h
DELETE COSA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the COSA (Core Satellite interface module) from the BTSE data
base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 156
PC Time&Date: 16:45:32 03/23/2005
NE Time&Date: 16:43:26 09/15/2004
USER NAME:
User_Ross
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/COSA:1
ChangeInfo = deleted
END OF OUTPUT FOR JOB 156
JOB: 157
PC Time&Date: 16:45:32 03/23/2005
NE Time&Date: 16:43:26 09/15/2004
USER NAME:
226
User_Ross
Id:0900d805805944b6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COMMAND:
COSA
Delete COSA:NAME=RACK:0/COSA:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 157
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
COSA must be locked in Phase 3 before deletion
Example of Command Execution:
Delete COSA:NAME=RACK:0/COSA:0;
GET COSA
GET COSA
NAME=RACK:0..7/COSA:0..1 [,REQATTL=ALS, AST, AVS,
OST, PRS, RELFUNCOBJ, SLOTNO, STDBYST];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COSA h
GET COSA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the COSA (Core Satellite interface module).
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
SLOTNO
slotNo
STDBYST
standbyStatus
System Responses:
Operation Completed
A50016-G5100-B333-04-7619
Id:0900d805805944b6
227
COSA
BS-4x / 82 II / 240 / 241 / 240XL commands
A message indicates the result of the operation. An example of get command is the following:
JOB: 148
PC Time&Date: 16:45:02 03/23/2005
NE Time&Date: 16:42:56 09/15/2004
USER NAME:
User_Ross
COMMAND:
Get COSA:NAME=RACK:0/COSA:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NotInstalled
operationalState = DISABLED
proceduralStatus = NULL
relatedFuncObjects =
slotNo = leftCOSA
standbyStatus = NULL
END OF OUTPUT FOR JOB 148
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
COSA:0 is the one with "Providing Service" Status, COSA:1 is in Standby Status
Example of Command Execution:
Get COSA:NAME=RACK:0/COSA:0,REQATTL=ALS&AST&AVS&
RELFUNCOBJ&OST& PRS.
GETTEST COSA
GETTEST COSA
NAME=RACK:0..7/COSA:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COSA h
GETTEST COSA
228
Id:0900d805805944b6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COSA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the COSA test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 193
PC Time&Date: 12:08:22 03/23/2005
NE Time&Date: 13:09:33 09/15/2004
USER NAME:
User_Ross
COMMAND:
Gettest COSA:NAME=RACK:0/COSA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/COSA:0
testMonitor =
phaseId = PreliminaryTestsCosa
phaseStatus = Running
phaseId = CheckAlarmStatusCosa
phaseStatus = Waiting
phaseId = EndTestCosa
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
END OF OUTPUT FOR JOB 193
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
A50016-G5100-B333-04-7619
Id:0900d805805944b6
229
COSA
BS-4x / 82 II / 240 / 241 / 240XL commands
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest COSA:NAME=RACK:0/COSA:0;
LOCK COSA
LOCK COSA
NAME=RACK:0..7/COSA:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COSA h
LOCK COSA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of COSA (Core Satellite interface
module).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
230
Id:0900d805805944b6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COSA
JOB: 149
PC Time&Date: 16:45:07 03/23/2005
NE Time&Date: 16:43:01 09/15/2004
USER NAME:
User_Ross
COMMAND:
Lock COSA:NAME=RACK:0/COSA:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 149
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 150
PC Time&Date: 16:45:07 03/23/2005
NE Time&Date: 16:43:01 09/15/2004
USER NAME:
User_Ross
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/COSA:1
Administrative State = LOCKED
Notification Identifier = 542
END OF OUTPUT FOR JOB 150
Operation Failed
The specified change of administrative state has not been performed.
A50016-G5100-B333-04-7619
Id:0900d805805944b6
231
COSA
BS-4x / 82 II / 240 / 241 / 240XL commands
Application Guidelines:
If the second line does not end in the first station (or is looped back by a plug!) also the
following points must considered for BS-240/241 and BS-40/41:
before a LOCK COSA command (over this board the information of the second line
is distributed within the BS-240/241 and BS-40/41) is applied by the operator, he
should lock the service distributed over the second line to this BTSE otherwise some
channels (associated to a COBA CU) remain enabled
in case of a defective COSA the channels which are associated to a COBA CU but
transported over the second line will remain enabled
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Lock COSA:NAME=RACK:0/COSA:0;
PERFTEST COSA
PERFTEST COSA
NAME=RACK:0..7/COSA:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COSA h
PERFTEST COSA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in COSA.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSE.
JOB: 193
PC Time&Date: 12:08:42 03/23/2005
NE Time&Date: 13:09:41 09/15/2004
232
USER NAME:
User_Ross
COMMAND:
Perftest COSA:NAME=RACK:0/COSA:0;
Id:0900d805805944b6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
SW RELEASE:
COSA
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/COSA:0
tO = BTSETEST:8
END OF OUTPUT FOR JOB 193
JOB: 194
PC Time&Date: 12:08:55 03/23/2005
NE Time&Date: 13:09:59 09/15/2004
USER NAME:
User_Ross
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:8
ChangeInfo = created
END OF OUTPUT FOR JOB 194
JOB: 195
PC Time&Date: 12:09:05 03/23/2005
NE Time&Date: 13:10:11 09/15/2004
USER NAME:
User_Ross
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/COSA:0
Operational State = ENABLED
Availability Status = NULL_value
Standby Status = Cold_Standby
A50016-G5100-B333-04-7619
Id:0900d805805944b6
233
COSA
BS-4x / 82 II / 240 / 241 / 240XL commands
Notification Identifier = 220
END OF OUTPUT FOR JOB 195
JOB: 196
PC Time&Date: 12:09:16 03/23/2005
NE Time&Date: 13:10:22 09/15/2004
USER NAME:
User_Ross
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:8
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/COSA:0
executedPhases =
PreliminaryTestsCosa
SerialEepromTestCosa
EndTestCosa
END OF OUTPUT FOR JOB 196
JOB: 197
PC Time&Date: 12:09:23 03/23/2005
NE Time&Date: 13:10:34 09/15/2004
USER NAME:
User_Ross
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:8
234
Id:0900d805805944b6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COSA
ChangeInfo = deleted
END OF OUTPUT FOR JOB 197
The test results will be displayed at the end of the test phases.
Result TEST:
name =
TEST:<n>
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
A50016-G5100-B333-04-7619
Id:0900d805805944b6
235
COSA
BS-4x / 82 II / 240 / 241 / 240XL commands
This NACK-message occurs in the following cases: Message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
In phase 3 MO must be locked previous to the command execution
Example of Command Execution:
Perftest COSA:NAME=RACK:0/COSA:0;
STOPTEST COSA
STOPTEST COSA
NAME=RACK:0..7/COSA:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COSA h
STOPTEST COSA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
...
.
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
failedPhases
236
Id:0900d805805944b6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COSA
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
phaseId =
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
Application Guidelines:
None.
Example of Command Execution:
Stoptest COSA:NAME=RACK:0/COSA:0;
UNLOCK COSA
UNLOCK COSA
NAME=RACK:0..7/COSA:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h COSA h
UNLOCK COSA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of COSA (Core Satellite interface
module).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 151
PC Time&Date: 16:45:12 03/23/2005
NE Time&Date: 16:43:06 09/15/2004
USER NAME:
A50016-G5100-B333-04-7619
User_Ross
Id:0900d805805944b6
237
COSA
BS-4x / 82 II / 240 / 241 / 240XL commands
COMMAND:
Unlock COSA:NAME=RACK:0/COSA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 151
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 152
PC Time&Date: 16:45:12 03/23/2005
NE Time&Date: 16:43:06 09/15/2004
USER NAME:
User_Ross
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/COSA:0
Administrative State = UNLOCKED
Standby Status = Providing_service
Notification Identifier = 543
END OF OUTPUT FOR JOB 152
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Unlock COSA:NAME=RACK:0/COSA:0;
238
Id:0900d805805944b6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CU
CU
The CU (Carrier Unit) represents the carrier hardware required for a TRX.
CREATE CU
CREATE CU
NAME=RACK:0..7/CU:0..11 [,RXLEVADJ=] [,TXLEVADJ=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h
CREATE CU
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the CU (Carrier Unit) to the BTSE data base.
Long Names:
NAME
Address of the managed object
RXLEVADJ
rxLevAdjust(dB)
TXLEVADJ
txLevAdjust(dB)
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 124
PC Time&Date: 16:43:07 03/23/2005
NE Time&Date: 16:41:01 09/15/2004
USER NAME:
User_Rzan
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/CU:0
ChangeInfo = created
A50016-G5100-B333-04-7619
Id:0900d805805944b8
239
CU
BS-4x / 82 II / 240 / 241 / 240XL commands
END OF OUTPUT FOR JOB 124
JOB: 125
PC Time&Date: 16:43:08 03/23/2005
NE Time&Date: 16:41:02 09/15/2004
USER NAME:
User_Rzan
COMMAND:
Create CU:NAME=RACK:0/CU:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 125
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 69
PC Time&Date: 16:37:54 03/23/2005
NE Time&Date: 16:35:47 09/15/2004
USER NAME:
User_Rzan
COMMAND:
Create CU:NAME=RACK:0/CU:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
Object instance unknown (-9)
END OF OUTPUT FOR JOB 69
Application Guidelines:
When using the CLI interface for the RXLEVADJ parameter, the negative values
must be in brackets (see Examples of Command Execution)
Example of Command Execution:
Create CU:NAME=RACK:0/CU:0,RXLEVADJ=[-1]-0,TXLEVADJ=1;
240
Id:0900d805805944b8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CU
DELETE CU
DELETE CU
NAME=RACK:0..7/CU:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h
DELETE CU
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the CU (Carrier Unit) from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 138
PC Time&Date: 16:44:00 03/23/2005
NE Time&Date: 16:41:54 09/15/2004
USER NAME:
User_Rzan
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/CU:0
ChangeInfo = deleted
END OF OUTPUT FOR JOB 138
JOB: 139
PC Time&Date: 16:44:00 03/23/2005
NE Time&Date: 16:41:54 09/15/2004
A50016-G5100-B333-04-7619
Id:0900d805805944b8
241
CU
BS-4x / 82 II / 240 / 241 / 240XL commands
USER NAME:
User_Rzan
COMMAND:
Delete CU:NAME=RACK:0/CU:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 139
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
CU has to be locked in Phase 3 before deletion
Example of Command Execution:
Delete CU:NAME=RACK:0/CU:0;
GET CU
GET CU
NAME=RACK:0..7/CU:0..11 [,REQATTL=ALS, AST, AVS,
BSWVER, CCPBL, OST, OUTPUTPR, PRS, RELFUNCOBJ, RXLEVADJ, TXLEVADJ, FPGAFWVER, STDBYST];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h GET
CU
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the CU (Carrier Unit).
Long Names:
242
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
BSWVER
bootSoftwareVersion
CCPBL
carrierCapability
OST
operationalState
OUTPUTPR
outputPowerReduction
Id:0900d805805944b8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
PRS
CU
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
RXLEVADJ
rxLevAdjust(dB)
TXLEVADJ
txLevAdjust(dB)
FPGAFWVER
STDBYST
fpgaFwVer
standbyStatus
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 5
PC Time&Date: 26.06.2008 11:13:46 +02:00
NE Time&Date: 01.01.1990 00:13:10 +00:00
USER NAME:
User_Rzan
COMMAND:
Get CU:NAME=RACK:0/CU:0;
SW RELEASE:
01-04-19-01-09-01_08-06-2
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
bootSoftwareVersion = "BTBBIX01.SWI:01-01-11-00-14-00_00-08-29"
carrierCapability = gsm
outputPowerReduction = 0
operationalState = ENABLED
proceduralStatus = NULL
relatedFuncObjects = Null
rxLevAdjust(dB) =
adjustValue = 0.0
adjustDivValue = 0.0
txLevAdjust(dB) = 0.0
standbyStatus = NULL
END OF OUTPUT FOR JOB 5
Operation Failed
A50016-G5100-B333-04-7619
Id:0900d805805944b8
243
CU
BS-4x / 82 II / 240 / 241 / 240XL commands
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
The value for the attribute GSM functional ID in LMT Phase 2 is "not configured"
CCPBL: After creation in advance of a CU object the attribute has the value
"unknown" in case of BTS Mainline or Xs. The value fourRXdiv is always used in
combination with either the value gsm or edge
FPGAFWVER attribute identifier cannot be present in the listOfRequiredAttributes
together with other attribute identifiers and it is not sent by the BTSE if a Get FCUMAIN/Get CU is done without the information element listOfRequiredAttributes
Example of Command Execution:
Get CU:NAME=RACK:0/CU:0,REQATTL=ALS&AST&AVS&BSWVER&CCPBL&OST&
OUTPUTPR&OST&PRS&RELFUNCOBJ&RXLEVADJ&TXLEVADJ&STDBYST;
GET CU FWID
GET CU FWID
NAME=RACK:0..7/CU:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h GET
CU FWID
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command provides information on the FPGA FW images that are contained in the
boards flash prom together with an indication of the active version.
Up to 4 images are provided per board.
For FlexCUv2 or ECUv6 boards the FPGA FW versions are provided together with an
indication whether the FW version is the active one.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 6
PC Time&Date: 26.06.2008 11:13:51 +02:00
244
Id:0900d805805944b8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CU
NE Time&Date: 01.01.1990 00:13:15 +00:00
USER NAME:
User_Rzan
COMMAND:
Get CU FWID:NAME=RACK:0/CU:0;SW
RELEASE:
01-04-19-01-09-01_08-06-23
COMMAND RESULT:
Operation successful
fpgaFwVer = Null
END OF OUTPUT FOR JOB 6
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Get CU FWID:NAME=RACK:0/CU:0,REQATTL=FPGAFWVER;
GET CU WIRING
GET CU WIRING
NAME=RACK:0..7/CU:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h GET
CU WIRING
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the CU (Carrier Unit).
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get wiring command is
the following:
JOB: 127
A50016-G5100-B333-04-7619
Id:0900d805805944b8
245
CU
BS-4x / 82 II / 240 / 241 / 240XL commands
PC Time&Date: 16:43:13 03/23/2005
NE Time&Date: 16:41:07 09/15/2004
USER NAME:
User_Rzan
COMMAND:
Get CU WIRING:NAME=RACK:0/CU:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
cuWiring =
variable
rxNWiring = RACK:0/DULNA:0
END OF OUTPUT FOR JOB 127
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
Refer to CUWIRING
Example of Command Execution:
Get CU WIRING:NAME=RACK:0/CU:0;
GETTEST CU
GETTEST CU
NAME=RACK:0..7/CU:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h
GETTEST CU
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the object test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
246
Id:0900d805805944b8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CU
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 198
PC Time&Date: 12:11:08 03/23/2005
NE Time&Date: 13:12:44 09/15/2004
USER NAME:
User_Rzan
COMMAND:
Gettest CU:NAME=RACK:0/CU:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/CU:0
testMonitor =
phaseId = PreliminaryTestsCu
phaseStatus = Running
phaseId = CheckAlarmStatusCu
phaseStatus = Waiting
phaseId = EndTestCu
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
END OF OUTPUT FOR JOB 198
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
A50016-G5100-B333-04-7619
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
Id:0900d805805944b8
247
CU
BS-4x / 82 II / 240 / 241 / 240XL commands
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest CU:NAME=RACK:0/CU:0;
LOCK CU
LOCK CU
NAME=RACK:0..7/CU:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h LOCK
CU
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of CU (Carrier Unit).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 132
PC Time&Date: 16:43:41 03/23/2005
NE Time&Date: 16:41:35 09/15/2004
USER NAME:
User_Rzan
COMMAND:
Lock CU:NAME=RACK:0/CU:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
248
Id:0900d805805944b8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CU
END OF OUTPUT FOR JOB 132
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 133
PC Time&Date: 16:43:41 03/23/2005
NE Time&Date: 16:41:35 09/15/2004
USER NAME:
User_Rzan
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/CU:0
Administrative State = LOCKED
Notification Identifier = 534
END OF OUTPUT FOR JOB 133
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Lock CU:NAME=RACK:0/CU:0;
PERFTEST CU
PERFTEST CU
NAME=RACK:0..7/CU:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h
PERFTEST CU
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
A50016-G5100-B333-04-7619
Id:0900d805805944b8
249
CU
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Description:
This command is used to start an asynchronous test in the object.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSEP.
JOB: 199
PC Time&Date: 12:11:12 03/23/2005
NE Time&Date: 13:12:48 09/15/2004
USER NAME:
User_Rzan
COMMAND:
Perftest CU:NAME=RACK:0/CU:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/CU:0
tO = BTSETEST:1
END OF OUTPUT FOR JOB 199
JOB: 200
PC Time&Date: 12:11:12 03/23/2005
NE Time&Date: 13:12:48 09/15/2004
USER NAME:
User_Rzan
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:1
ChangeInfo = created
END OF OUTPUT FOR JOB 200
250
Id:0900d805805944b8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CU
JOB: 201
PC Time&Date: 12:11:12 03/23/2005
NE Time&Date: 13:12:59 09/15/2004
USER NAME:
User_Rzan
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/CU:0
Operational State = ENABLED
Availability Status = NULL_value
Standby Status = Cold_Standby
Notification Identifier = 123
END OF OUTPUT FOR JOB 201
JOB: 202
PC Time&Date: 12:11:18 03/23/2005
NE Time&Date: 13:13:11 09/15/2004
USER NAME:
User_Rzan
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:1
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/CU:0
executedPhases =
PreliminaryTestsCu
SerialEepromTestCu
A50016-G5100-B333-04-7619
Id:0900d805805944b8
251
CU
BS-4x / 82 II / 240 / 241 / 240XL commands
EndTestCu
END OF OUTPUT FOR JOB 202
JOB: 203
PC Time&Date: 12:11:20 03/23/2005
NE Time&Date: 13:13:25 09/15/2004
USER NAME:
User_Rzan
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:1
ChangeInfo = deleted
END OF OUTPUT FOR JOB 203
The test results will be displayed at the end of the test phases.
Result TEST:
name =
TEST:<n>
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
252
Id:0900d805805944b8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CU
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: Message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
In phase 3 MO must be locked previous to the command execution
Example of Command Execution:
Perftest CU:NAME=RACK:0/CU:0;
SET CU
SET CU
NAME=RACK:0..7/CU:0..11 [,RXLEVADJ=] [,TXLEVADJ=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h SET
CU
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command sets the attributes of CU (Carrier Unit) to the BTSE data base.
Long Names:
NAME
Address of the managed object
RXLEVADJ
rxLevAdjust(dB)
TXLEVADJ
txLevAdjust(dB)
A50016-G5100-B333-04-7619
Id:0900d805805944b8
253
CU
BS-4x / 82 II / 240 / 241 / 240XL commands
System Responses:
Operation Completed
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
JOB: 131
PC Time&Date: 16:43:27 03/23/2005
NE Time&Date: 16:41:21 09/15/2004
USER NAME:
User_Rzan
COMMAND:
Set CU:NAME=RACK:0/CU:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 131
Operation Failed
The specified attributes have not been set. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible.
Application Guidelines:
When using the CLI interface for the RXLEVADJ parameter, the negative values
must be in brackets (see Example of Command Execution)
The MGMSKOUTPUTP power reduction parameter is used for all existing high
power variants ECUxHPV2 and ECUxHPV3 (x= D or P)
Example of Command Execution:
Set CU:NAME=RACK:0/CU:0,TXLEVADJ=1,RXLEVADJ=[-1]-[-1];
STOPTEST CU
STOPTEST CU
NAME=RACK:0..7/CU:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h
STOPTEST CU
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
254
Id:0900d805805944b8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CU
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
...
.
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
phaseId =
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
Application Guidelines:
None.
Example of Command Execution:
Stoptest CU:NAME=RACK:0/CU:0;
UNLOCK CU
UNLOCK CU
NAME=RACK:0..7/CU:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CU h
UNLOCK CU
A50016-G5100-B333-04-7619
Id:0900d805805944b8
255
CU
BS-4x / 82 II / 240 / 241 / 240XL commands
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of CU (Carrier Unit).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 134
PC Time&Date: 16:43:50 03/23/2005
NE Time&Date: 16:41:44 09/15/2004
USER NAME:
User_Rzan
COMMAND:
Unlock CU:NAME=RACK:0/CU:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 134
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 135
PC Time&Date: 16:43:50 03/23/2005
NE Time&Date: 16:41:44 09/15/2004
USER NAME:
User_Rzan
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
256
Id:0900d805805944b8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CU
CHANGED STATE EVENT REPORT:
NAME = RACK:0/CU:0
Administrative State = UNLOCKED
Notification Identifier = 535
END OF OUTPUT FOR JOB 135
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Unlock CU:NAME=RACK:0/CU:0;
A50016-G5100-B333-04-7619
Id:0900d805805944b8
257
DIDCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
DIDCTMA
The DIDCTMA object represents the power supply module of a TMA (Tower Mounted
Amplifier) connected to DIAMCO.
CREATE DIDCTMA
CREATE DIDCTMA
NAME=RACK:0..7/DIDCTMA:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DIDCTMA h
CREATE DIDCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the DIAMCO_DC_TMA (DC Power Supply Module of TMA) to the
BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 111
PC Time&Date: 16:41:43 03/23/2005
NE Time&Date: 16:39:37 09/15/2004
USER NAME:
User_p
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/DIDCTMA:0
ChangeInfo = created
258
Id:0900d805805944ba
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DIDCTMA
END OF OUTPUT FOR JOB 111
JOB: 112
PC Time&Date: 16:41:43 03/23/2005
NE Time&Date: 16:39:37 09/15/2004
USER NAME:
User_p
COMMAND:
Create DIDCTMA:NAME=RACK:0/DIDCTMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 112
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 68
PC Time&Date: 16:37:54 03/23/2005
NE Time&Date: 16:35:47 09/15/2004
USER NAME:
User_p
COMMAND:
Create DIDCTMA:NAME=RACK:0/DIDCTMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
Message cannot be performed (-17)
END OF OUTPUT FOR JOB 68
Application Guidelines:
None.
Example of Command Execution:
Create DIDCTMA:NAME=RACK:0/DIDCTMA:0;
DELETE DIDCTMA
DELETE DIDCTMA
A50016-G5100-B333-04-7619
NAME=RACK:0..7/DIDCTMA:0..7;
Id:0900d805805944ba
259
DIDCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DIDCTMA h
DELETE DIDCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the DIAMCO_DC_TMA (DC Power Supply Module of TMA) from
the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 120
PC Time&Date: 16:42:08 03/23/2005
NE Time&Date: 16:40:02 09/15/2004
USER NAME:
User_p
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/DIDCTMA:0
ChangeInfo = deleted
END OF OUTPUT FOR JOB 120
JOB: 121
PC Time&Date: 16:42:08 03/23/2005
NE Time&Date: 16:40:02 09/15/2004
USER NAME:
260
User_p
Id:0900d805805944ba
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COMMAND:
DIDCTMA
Delete DIDCTMA:NAME=RACK:0/DIDCTMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 121
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
DIDCTMA must be locked in phase 3 before deletion
Example of Command Execution:
Delete DIDCTMA:NAME=RACK:0/DIDCTMA:0;
GET DIDCTMA
GET DIDCTMA
NAME=RACK:0..7/DIDCTMA:0..7 [,REQATTL=ALS, AST,
AVS, OST, PRS, RELFUNCOBJ];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DIDCTMA h
GET DIDCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the DIAMCO_DC_TMA (DC Power Supply
Module of TMA).
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
System Responses:
Operation Completed
A50016-G5100-B333-04-7619
Id:0900d805805944ba
261
DIDCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
A message indicates the result of the operation. An example of get command is the following:
JOB: 113
PC Time&Date: 16:41:48 03/23/2005
NE Time&Date: 16:39:41 09/15/2004
USER NAME:
User_p
COMMAND:
Get DIDCTMA:NAME=RACK:0/DIDCTMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NotInstalled
operationalState = DISABLED
proceduralStatus = NULL
relatedFuncObjects =
END OF OUTPUT FOR JOB 113
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
None.
Example of Command Execution:
Get DIDCTMA:NAME=RACK:0/DIDCTMA:0,REQATTL=ALS&AST&AVS&OST&PRS;
GETTEST DIDCTMA
GETTEST DIDCTMA
NAME=RACK:0..7/DIDCTMA:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DIDCTMA h
GETTEST DIDCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
262
Id:0900d805805944ba
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DIDCTMA
Command Description:
This command displays the attributes of the object test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 204
PC Time&Date: 12:11:28 03/23/2005
NE Time&Date: 13:13:04 09/15/2004
USER NAME:
User_p
COMMAND:
Gettest DIDCTMA:NAME=RACK:0/DIDCTMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/DIDCTMA:0
testMonitor =
phaseId = PreliminaryTestsDidctma
phaseStatus = Running
phaseId = CheckAlarmStatusDidctma
phaseStatus = Waiting
phaseId = EndTestDidctma
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
END OF OUTPUT FOR JOB 204
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
A50016-G5100-B333-04-7619
Id:0900d805805944ba
263
DIDCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest DIDCTMA:NAME=RACK:0/DIDCTMA:0;
LOCK DIDCTMA
LOCK DIDCTMA
NAME=RACK:0..7/DIDCTMA:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DIDCTMA h
LOCK DIDCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of DIAMCO_DC_TMA (DC Power
Supply Module of TMA).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
264
Id:0900d805805944ba
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DIDCTMA
JOB: 114
PC Time&Date: 16:41:53 03/23/2005
NE Time&Date: 16:39:47 09/15/2004
USER NAME:
User_p
COMMAND:
Lock DIDCTMA:NAME=RACK:0/DIDCTMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 114
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 115
PC Time&Date: 16:41:53 03/23/2005
NE Time&Date: 16:39:47 09/15/2004
USER NAME:
User_p
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/DIDCTMA:0
Administrative State = LOCKED
Notification Identifier = 525
END OF OUTPUT FOR JOB 115
Operation Failed
The specified change of administrative state has not been performed.
A50016-G5100-B333-04-7619
Id:0900d805805944ba
265
DIDCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Lock DIDCTMA:NAME=RACK:0/DIDCTMA:0;
PERFTEST DIDCTMA
PERFTEST DIDCTMA
NAME=RACK:0..7/DIDCTMA:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DIDCTMA h
PERFTEST DIDCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in DIDCTMA.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSEP.
JOB: 205
PC Time&Date: 12:13:07 03/23/2005
NE Time&Date: 13:14:42 09/15/2004
USER NAME:
User_p
COMMAND:
Perftest DIDCTMA:NAME=RACK:0/DIDCTMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/DIDCTMA:0
tO = BTSETEST:2
END OF OUTPUT FOR JOB 205
266
Id:0900d805805944ba
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DIDCTMA
JOB: 206
PC Time&Date: 12:13:22 03/23/2005
NE Time&Date: 13:14:57 09/15/2004
USER NAME:
User_p
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:2
ChangeInfo = created
END OF OUTPUT FOR JOB 206
JOB: 207
PC Time&Date: 12:13:31 03/23/2005
NE Time&Date: 13:15:06 09/15/2004
USER NAME:
User_p
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/DIDCTMA:0
Operational State = ENABLED
Availability Status = NULL_value
Standby Status = Cold_Standby
Notification Identifier = 146
END OF OUTPUT FOR JOB 207
JOB: 208
A50016-G5100-B333-04-7619
Id:0900d805805944ba
267
DIDCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
PC Time&Date: 12:13:35 03/23/2005
NE Time&Date: 13:15:10 09/15/2004
USER NAME:
User_p
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:2
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/DIDCTMA:0
executedPhases =
PreliminaryTestsDidctma
SerialEepromTestDidctma
EndTestDidctma
END OF OUTPUT FOR JOB 208
JOB: 209
PC Time&Date: 12:13:35 03/23/2005
NE Time&Date: 13:15:10 09/15/2004
USER NAME:
User_p
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:2
ChangeInfo = deleted
END OF OUTPUT FOR JOB 209
The test results will be displayed at the end of the test phases.
Result TEST:
name =
268
TEST:<n>
Id:0900d805805944ba
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DIDCTMA
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: Message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
In phase 3 MO must be locked previous to the command execution
Example of Command Execution:
Perftest DIDCTMA:NAME=RACK:0/DIDCTMA:0;
A50016-G5100-B333-04-7619
Id:0900d805805944ba
269
DIDCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
STOPTEST DIDCTMA
STOPTEST DIDCTMA
NAME=RACK:0..7/DIDCTMA:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DIDCTMA h
STOPTEST DIDCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
...
.
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
270
Id:0900d805805944ba
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DIDCTMA
Application Guidelines:
None.
Example of Command Execution:
Stoptest DIDCTMA:NAME=RACK:0/DIDCTMA:0;
UNLOCK DIDCTMA
UNLOCK DIDCTMA
NAME=RACK:0..7/DIDCTMA:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DIDCTMA h
UNLOCK DIDCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of DIAMCO_DC_TMA (DC Power
Supply Module of TMA).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 116
PC Time&Date: 16:41:57 03/23/2005
NE Time&Date: 16:39:51 09/15/2004
USER NAME:
User_p
COMMAND:
Unlock DIDCTMA:NAME=RACK:0/DIDCTMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 116
CHANGED STATE EVENT REPORT:
A50016-G5100-B333-04-7619
Id:0900d805805944ba
271
DIDCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 117
PC Time&Date: 16:41:57 03/23/2005
NE Time&Date: 16:39:51 09/15/2004
USER NAME:
User_p
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/DIDCTMA:0
Administrative State = UNLOCKED
Notification Identifier = 526
END OF OUTPUT FOR JOB 117
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Unlock DIDCTMA:NAME=RACK:0/DIDCTMA:0;
272
Id:0900d805805944ba
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DILNA
DILNA
The DILNA object represents the low noise amplifier of DIAMCO (Diversity Antenna
Multicoupler).
CREATE DILNA
CREATE DILNA
NAME=RACK:0..7/DILNA:0..7 ,CELLNO= [,COMBMD=]
[,LNAPRED=] [,SCELLNO=] ,WDLNA=;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h
CREATE DILNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the DILNA (Low Noise Amplifier of Diversity Multicoupler) together
with its attributes to the BTSE data base.
Long Names:
NAME
Address of the managed object
CELLNO
cellNumber
COMBMD
combMode
LNAPRED
lnaPredecessor
SCELLNO
secondCellNumber
WDLNA
wiringDataLna
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 96
PC Time&Date: 16:40:26 03/23/2005
NE Time&Date: 16:38:20 09/15/2004
USER NAME:
User_q
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
A50016-G5100-B333-04-7619
Id:0900d805805944bc
273
DILNA
BS-4x / 82 II / 240 / 241 / 240XL commands
ChangedConfigurationNotification:
name = RACK:0/DILNA:0
ChangeInfo = created
END OF OUTPUT FOR JOB 96
JOB: 97
PC Time&Date: 16:40:26 03/23/2005
NE Time&Date: 16:38:20 09/15/2004
USER NAME:
User_q
COMMAND:
Create DILNA:NAME=RACK:0/DILNA:0,CELLNO=1,WDLNA=CU0N;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
cellNumber = 1
secondCellNumber = 2
wiringDataLna = CU0N
END OF OUTPUT FOR JOB 97
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 74
PC Time&Date: 16:37:54 03/23/2005
NE Time&Date: 16:35:47 09/15/2004
USER NAME:
User_q
COMMAND:
Create DILNA:NAME=RACK:0/DILNA:0,CELLNO=1,WDLNA=CU0N;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
Message cannot be performed (-17)
274
Id:0900d805805944bc
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DILNA
END OF OUTPUT FOR JOB 74
Application Guidelines:
The DIAMCO_LNA and the CUs are in the same rack and belong to the same cell
Each CU has a 'normal path' RX input and a 'diversity path' RX input and the
operator must indicate which of them is wired to the DIAMCO_LNA
If there is no wiring the operator must not provide a value for the attribute LNAPRED
(if a get is done the attribute identifier will be put into the list of unavailable attributes)
If there is no wiring for the attribute LNAPRED and the operator enters a value, this
error can be corrected by a deletion of the object and a re-creation of the object
The BTSE SW doesn't check if the entered "predecessor (relative number)" is compatible with typeOfBTSE; e.g. an input of TMA 11 is not rejected in a BS40 although
BS40 allows only the creation of TMA 0-5
The BTSE SW doesn't check if the entered "predecessor (rack)" is compatible with
typeOfBTSE; e.g. an input of RACK 1 is not rejected in a BS40 although BS40
allows only the creation of RACK 0
Wildcard addressing is not possible
Example of Command Execution:
Create DILNA:NAME=RACK:1/DILNA:0,CELLNO=0,COMBMD=EightToTwo,
SCELLNO=2,WDLNA=CU0D&CU1D&CU2D&CU3D,
LNAPRED=TMA (RACK:0-TMA:0);
DELETE DILNA
DELETE DILNA
NAME=RACK:0..7/DILNA:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h
DELETE DILNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the DILNA (Low Noise Amplifier of Diversity Multicoupler)
together with its attributes from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
A50016-G5100-B333-04-7619
Id:0900d805805944bc
275
DILNA
BS-4x / 82 II / 240 / 241 / 240XL commands
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 106
PC Time&Date: 16:40:51 03/23/2005
NE Time&Date: 16:38:45 09/15/2004
USER NAME:
User_q
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/DILNA:0
ChangeInfo = deleted
END OF OUTPUT FOR JOB 106
JOB: 107
PC Time&Date: 16:40:51 03/23/2005
NE Time&Date: 16:38:45 09/15/2004
USER NAME:
User_q
COMMAND:
Delete DILNA:NAME=RACK:0/DILNA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 107
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
276
DILNA must be locked in Phase 3, before deletion
If this object is deleted, the related TRXs are out of service
Id:0900d805805944bc
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DILNA
Example of Command Execution:
Delete DILNA:NAME=RACK:0/DILNA:0;
GET DILNA
GET DILNA
NAME=RACK:0..7/DILNA:0..7 [,REQATTL=ALS, AST, AVS,
CELLNO, GNA, COMBMD, LNAMODE, LNAPRED, OST,
PRS, RELFUNCOBJ, SCELLNO, WDLNA];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h
GET DILNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the DILNA (Low Noise Amplifier of Diversity
Multicoupler).
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
CELLNO
cellNumber
GNA
gainAdjust(dB)
COMBMD
combMode
LNAMODE
lnaMode
LNAPRED
lnaPredecessor
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
SCELLNO
secondCellNumber
WDLNA
wiringDataLna
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 99
A50016-G5100-B333-04-7619
Id:0900d805805944bc
277
DILNA
BS-4x / 82 II / 240 / 241 / 240XL commands
PC Time&Date: 16:40:32 03/23/2005
NE Time&Date: 16:38:26 09/15/2004
USER NAME:
User_q
COMMAND:
Get DILNA:NAME=RACK:0/DILNA:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NotInstalled
cellNumber = 1
cableLossAdjust(dB) = Null
combMode = EightToTwo
lnaMode = UNKNOWN
lnaPredecessor = Null
operationalState = DISABLED
proceduralStatus = NULL
relatedFuncObjects =
secondCellNumber = NotUsed
wiringDataLna = CU3N & CU2N & CU0D & CU0N
END OF OUTPUT FOR JOB 99
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
The value for the attribute relatedFuncObjects in LMT Phase 2 is "not configured"
The value for proceduralStatus must be NULL
Example of Command Execution:
Get
DILNA:NAME=RACK:0/DILNA:0,REQATTL=ALS&AST&AVS&CELLNO&GNA&CLAD
J&COMBMD&LNAMODE&LNAPRED&OST&PRS&SCELLNO&WDLNA;
GETTEST DILNA
GETTEST DILNA
278
NAME=RACK:0..7/DILNA:0..7;
Id:0900d805805944bc
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DILNA
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h
GETTEST DILNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the object test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 210
PC Time&Date: 12:13:35 03/23/2005
NE Time&Date: 13:15:10 09/15/2004
USER NAME:
User_q
COMMAND:
Gettest DILNA:NAME=RACK:0/DILNA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/DILNA:0
testMonitor =
phaseId = PreliminaryTestsDilna
phaseStatus = Running
phaseId = CheckAlarmStatusDilna
phaseStatus = Waiting
phaseId = EndTestDilna
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
END OF OUTPUT FOR JOB 210
A50016-G5100-B333-04-7619
Id:0900d805805944bc
279
DILNA
BS-4x / 82 II / 240 / 241 / 240XL commands
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest DILNA:NAME=RACK:0/DILNA:0;
LOCK DILNA
LOCK DILNA
NAME=RACK:0..7/DILNA:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h
LOCK DILNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of DILNA (Low Noise Amplifier of Diversity Multicoupler).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
280
Id:0900d805805944bc
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DILNA
The specified change of administrative state has been perfomed:
JOB: 100
PC Time&Date: 16:40:38 03/23/2005
NE Time&Date: 16:38:32 09/15/2004
USER NAME:
User_q
COMMAND:
Lock DILNA:NAME=RACK:0/DILNA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 100
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 101
PC Time&Date: 16:40:38 03/23/2005
NE Time&Date: 16:38:32 09/15/2004
USER NAME:
User_q
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/DILNA:0
Administrative State = LOCKED
Notification Identifier = 519
END OF OUTPUT FOR JOB 101
Operation Failed
The specified change of administrative state has not been performed.
A50016-G5100-B333-04-7619
Id:0900d805805944bc
281
DILNA
BS-4x / 82 II / 240 / 241 / 240XL commands
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Lock DILNA:NAME=RACK:0/DILNA:0;
PERFTEST DILNA
PERFTEST DILNA
NAME=RACK:0..7/DILNA:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h
PERFTEST DILNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in the object.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSE.
JOB: 211
PC Time&Date: 12:13:39 03/23/2005
NE Time&Date: 13:15:13 09/15/2004
USER NAME:
User_q
COMMAND:
Perftest DILNA:NAME=RACK:0/DILNA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/DILNA:0
tO = BTSETEST:1
END OF OUTPUT FOR JOB 211
282
Id:0900d805805944bc
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DILNA
JOB: 212
PC Time&Date: 12:13:42 03/23/2005
NE Time&Date: 13:15:17 09/15/2004
USER NAME:
User_q
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:1
ChangeInfo = created
END OF OUTPUT FOR JOB 212
JOB: 213
PC Time&Date: 12:13:50 03/23/2005
NE Time&Date: 13:15:25 09/15/2004
USER NAME:
User_q
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/DILNA:0
Operational State = ENABLED
Availability Status = NULL_value
Standby Status = Cold_Standby
Notification Identifier = 168
END OF OUTPUT FOR JOB 213
JOB: 214
A50016-G5100-B333-04-7619
Id:0900d805805944bc
283
DILNA
BS-4x / 82 II / 240 / 241 / 240XL commands
PC Time&Date: 12:13:50 03/23/2005
NE Time&Date: 13:15:25 09/15/2004
USER NAME:
User_q
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:1
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/DILNA:0
executedPhases =
PreliminaryTestsDilna
SerialEepromTestDilna
EndTestDilna
END OF OUTPUT FOR JOB 214
JOB: 215
PC Time&Date: 12:13:50 03/23/2005
NE Time&Date: 13:15:25 09/15/2004
USER NAME:
User_q
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:1
ChangeInfo = deleted
END OF OUTPUT FOR JOB 215
The test results will be displayed at the end of the test phases.
Result TEST:
name =
284
TEST:<n>
Id:0900d805805944bc
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DILNA
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: Message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
In phase 3 MO must be locked previous to the command execution
Example of Command Execution:
Perftest DILNA:NAME=RACK:0/DILNA:0;
A50016-G5100-B333-04-7619
Id:0900d805805944bc
285
DILNA
BS-4x / 82 II / 240 / 241 / 240XL commands
SET DILNA
SET DILNA
NAME=RACK:0..7/DILNA:0..7 [,SCELLNO=] [,WDLNA=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h
SET DILNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command sets the attributes of the DILNA (Low Noise Amplifier of Diversity Multicoupler) to the BTSE data base.
Long Names:
NAME
Address of the managed object
SCELLNO
secondCellNumber
WDLNA
wiringDataLna
System Responses:
Operation Completed
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
JOB: 62
PC Time&Date: 11:57:39 03/23/2005
NE Time&Date: 12:59:14 09/15/2004
USER NAME:
User_q
COMMAND:
Set DILNA:NAME=RACK:0/DILNA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 62
Operation Failed
The specified attributes have not been set. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible.
Application Guidelines:
286
The DIAMCO_LNA and the CUs are in the same rack and belong to the same cell
Id:0900d805805944bc
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DILNA
Each CU has a 'normal path' RX input and a 'diversity path' RX input and the
operator must indicate which of them is wired to the DIAMCO_LNA.
Wildcard addressing is not possible.
All CUs which are listed in a previous GET DILNA for WDLNA have to be locked
(LOCK CU command) before one of these CUs can be removed from WDLNA.
Before locking these CUs first a shutdown of the TRXs related to these CUs should
be done.
Example of Command Execution:
Set DILNA:NAME=RACK:0/DILNA:0,SCELLNO=2,WDLNA=CU0D&CU1D&
CU2D&CU3D;
STOPTEST DILNA
STOPTEST DILNA
NAME=RACK:0..7/DILNA:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h
STOPTEST DILNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
...
.
A50016-G5100-B333-04-7619
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
Id:0900d805805944bc
287
DILNA
BS-4x / 82 II / 240 / 241 / 240XL commands
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
Application Guidelines:
None.
Example of Command Execution:
Stoptest DILNA:NAME=RACK:0/DILNA:0;
UNLOCK DILNA
UNLOCK DILNA
NAME=RACK:0..7/DILNA:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DILNA h
UNLOCK DILNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the DILNA (Low Noise Amplifier of
Diversity Multicoupler).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 102
PC Time&Date: 16:40:43 03/23/2005
NE Time&Date: 16:38:37 09/15/2004
288
Id:0900d805805944bc
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DILNA
USER NAME:
User_q
COMMAND:
Unlock DILNA:NAME=RACK:0/DILNA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 102
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 103
PC Time&Date: 16:40:43 03/23/2005
NE Time&Date: 16:38:37 09/15/2004
USER NAME:
User_q
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/DILNA:0
Administrative State = UNLOCKED
Notification Identifier = 521
END OF OUTPUT FOR JOB 103
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Unlock DILNA:NAME=RACK:0/DILNA:0;
A50016-G5100-B333-04-7619
Id:0900d805805944bc
289
DUAMCO
BS-4x / 82 II / 240 / 241 / 240XL commands
DUAMCO
DUAMCO object is mainly used to represent the status of the firmware download; the
state changes of the DUAMCO object are triggered by subsystems RC, AE and DG as
usual.
DUAMCO object is automatically created if an MFDUAMCO is successfully registered.
DELETE DUAMCO
DELETE DUAMCO
NAME=RACK:0..7/DUAMCO:0..5;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUAMCO h
DELETE DUAMCO
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the DUAMCO from the BTSE data base.
Automatic deletion is also possible.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 71
PC Time&Date: 05.05.2008 11:35:33 +02:00
NE Time&Date: 01.01.1990 00:12:10 +00:00
USER NAME:
User_r
COMMAND:
Delete DUAMCO:NAME=RACK:0/DUAMCO:0;
SW RELEASE:
01-04-19-01-86-MF_08-04-24
COMMAND RESULT: Operation successful
290
Id:0900d805805944be
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUAMCO
END OF OUTPUT FOR JOB 71
Operation Failed
None.
Application Guidelines:
Automatic deletion is not possible in case of a BCOM/FCOM is inserted in ACOM slot.
Example of Command Execution:
DELETE DUAMCO:
NAME=RACK:0/ DUAMCO:0;
GET DUAMCO
GET DUAMCO
NAME=RACK:0..7/DUAMCO:0..5 [,REQATTL=ALS, AST,
AVS, OST, PRS, DMCFWID, RELFUNCOBJ];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUAMCO h
GET DUAMCO
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the DUAMCO.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
PRS
proceduralStatus
DMCFWID
duamcoFwId
RELFUNCOBJ
relatedFuncObjects
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
A50016-G5100-B333-04-7619
Id:0900d805805944be
291
DUAMCO
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 86
PC Time&Date: 05.05.2008 11:35:48 +02:00
NE Time&Date: 01.01.1990 00:12:25 +00:00
USER NAME:
User_r
COMMAND:
Get DUAMCO:NAME=RACK:0/DUAMCO:0;
SW RELEASE:
01-04-19-01-86-MF_08-04-24
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
operationalState = ENABLED
proceduralStatus = NULL
duamcoFwId = "BFDU0250.SWI:00-50-19-02-15-00_08-01-01"
relatedFuncObjects = Null
END OF OUTPUT FOR JOB 86
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Get
DUAMCO:NAME=RACK:0/DUAMCO:0,REQATTL=ALS&AST&AVS&OST&PRS&DM
CFWID&RELFUNCOBJ;
GETTEST DUAMCO
GETTEST DUAMCO
NAME=RACK:0..7/DUAMCO:0..5;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUAMCO h
GETTEST DUAMCO
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
292
Id:0900d805805944be
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUAMCO
Command Description:
This command displays the attributes of the object test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
None.
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Gettest DUAMCO:NAME=RACK:0/DUAMCO:0,REQATTL=MORT&TESTMON&TESTOUT&TESTST;
LOCK DUAMCO
LOCK DUAMCO
NAME=RACK:0..7/DUAMCO:0..5;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUAMCO h
LOCK DUAMCO
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of DUAMCO.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of lock
command is the following:
JOB: 99
PC Time&Date: 05.05.2008 11:36:17 +02:00
A50016-G5100-B333-04-7619
Id:0900d805805944be
293
DUAMCO
BS-4x / 82 II / 240 / 241 / 240XL commands
NE Time&Date: 01.01.1990 00:12:54 +00:00
USER NAME:
User_r
COMMAND:
Lock DUAMCO:NAME=RACK:0/DUAMCO:0;
SW RELEASE:
01-04-19-01-86-MF_08-04-24
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 99
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Lock DUAMCO:NAME=RACK:0/DUAMCO:0, AST=Locked;
PERFTEST DUAMCO
PERFTEST DUAMCO
NAME=RACK:0..7/DUAMCO:0..5;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUAMCO h
PERFTEST DUAMCO
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in the object.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of perftest
command is the following:
JOB: 138
294
Id:0900d805805944be
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUAMCO
PC Time&Date: 05.05.2008 11:36:42 +02:00
NE Time&Date: 01.01.1990 00:13:19 +00:00
USER NAME:
User_r
COMMAND:
Perftest DUAMCO:NAME=RACK:0/DUAMCO:0;
SW RELEASE:
01-04-19-01-86-MF_08-04-24
COMMAND RESULT: Operation successful
MOT = RACK:0/DUAMCO:0
tO = BTSETEST:1
END OF OUTPUT FOR JOB 138
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Perftest DUAMCO:NAME=RACK:0/DUAMCO:0;
STOPTEST DUAMCO
STOPTEST DUAMCO
NAME=RACK:0..7/DUAMCO:0..5;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUAMCO h
STOPTEST DUAMCO
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
None.
Operation Failed
None.
A50016-G5100-B333-04-7619
Id:0900d805805944be
295
DUAMCO
BS-4x / 82 II / 240 / 241 / 240XL commands
Application Guidelines:
None.
Example of Command Execution:
Stoptest DUAMCO:NAME=RACK:0/DUAMCO:0;
UNLOCK DUAMCO
UNLOCK DUAMCO
NAME=RACK:0..7/DUAMCO:0..5;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUAMCO h
UNLOCK DUAMCO
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of DUAMCO.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of unlock
command is the following:
JOB: 108
PC Time&Date: 05.05.2008 11:36:35 +02:00
NE Time&Date: 01.01.1990 00:13:12 +00:00
USER NAME:
User_r
COMMAND:
Unlock DUAMCO:NAME=RACK:0/DUAMCO:0;
SW RELEASE:
01-04-19-01-86-MF_08-04-24
COMMAND RESULT: Operation successful
administrativeState = Unlocked
Operation Failed
None.
296
Id:0900d805805944be
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUAMCO
Application Guidelines:
None.
Example of Command Execution:
Unlock DUAMCO:NAME=RACK:0/DUAMCO:0, AST=Unlocked;
A50016-G5100-B333-04-7619
Id:0900d805805944be
297
DUDCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
DUDCTMA
The DUDCTMA object represents the power supply module of a TMA (Tower Mounted
Amplifier) connected to DUAMCO.
CREATE DUDCTMA
CREATE DUDCTMA
NAME=RACK:0..7/DUDCTMA:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUDCTMA
h CREATE DUDCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the DUAMCO_DC_TMA (DC Power Supply Module of TMA) to the
BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 78
PC Time&Date: 16:38:29 03/23/2005
NE Time&Date: 16:36:23 09/15/2004
USER NAME:
User_s
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/DUDCTMA:0
ChangeInfo = created
298
Id:0900d805805944c0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUDCTMA
END OF OUTPUT FOR JOB 78
JOB: 79
PC Time&Date: 16:38:29 03/23/2005
NE Time&Date: 16:36:23 09/15/2004
USER NAME:
User_s
COMMAND:
Create DUDCTMA:NAME=RACK:0/DUDCTMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 79
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 75
PC Time&Date: 16:37:54 03/23/2005
NE Time&Date: 16:35:47 09/15/2004
USER NAME:
User_s
COMMAND:
Create DUDCTMA:NAME=RACK:0/DUDCTMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
Message cannot be performed (-17)
END OF OUTPUT FOR JOB 75
Application Guidelines:
The commands for the objects DUDCTMA:2n and DUDCTMA:2n+1 are not allowed if
the object DUAMCO:n exists and is in the state OST.AVS = enabled.degraded (firmware download is active).
Example of Command Execution:
Create DUDCTMA:NAME=RACK:0/DUDCTMA:0;
A50016-G5100-B333-04-7619
Id:0900d805805944c0
299
DUDCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
DELETE DUDCTMA
DELETE DUDCTMA
NAME=RACK:0..7/DUDCTMA:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUDCTMA
h DELETE DUDCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the DUAMCO_DC_TMA (DC Power Supply Module of TMA)
from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 90
PC Time&Date: 16:39:22 03/23/2005
NE Time&Date: 16:37:16 09/15/2004
USER NAME:
User_s
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/DUDCTMA:0
ChangeInfo = deleted
END OF OUTPUT FOR JOB 90
JOB: 91
PC Time&Date: 16:39:22 03/23/2005
300
Id:0900d805805944c0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUDCTMA
NE Time&Date: 16:37:16 09/15/2004
USER NAME:
User_s
COMMAND:
Delete DUDCTMA:NAME=RACK:0/DUDCTMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 91
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
DUDCTMA must be locked in phase 3 before deletion
The commands for the objects DUDCTMA:2n and DUDCTMA:2n+1 are not allowed
if the object DUAMCO:n exists and is in the state OST.AVS = enabled.degraded
(firmware download is active)
Example of Command Execution:
Delete DUDCTMA:NAME=RACK:0/DUDCTMA:0;
GET DUDCTMA
GET DUDCTMA
NAME=RACK:0..7/DUDCTMA:0..11 [,REQATTL=ALS,
AST, AVS, OST, PRS, RELFUNCOBJ];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUDCTMA
h GET DUDCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the DUAMCO_DC_TMA (DC Power Supply
Module of TMA).
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
A50016-G5100-B333-04-7619
Id:0900d805805944c0
301
DUDCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 82
PC Time&Date: 16:38:53 03/23/2005
NE Time&Date: 16:36:47 09/15/2004
USER NAME:
User_s
COMMAND:
Get DUDCTMA:NAME=RACK:0/DUDCTMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
operationalState = ENABLED
proceduralStatus = NULL
relatedFuncObjects =
END OF OUTPUT FOR JOB 82
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
None.
Example of Command Execution:
Get DUDCTMA:NAME=RACK:0/DUDCTMA:0,REQATTL=ALS&AST&AVS&
OST&PRS&RELFUNCOBJ;
GETTEST DUDCTMA
GETTEST DUDCTMA
302
NAME=RACK:0..7/DUDCTMA:0..11;
Id:0900d805805944c0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUDCTMA
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUDCTMA
h GETTEST DUDCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the object test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 216
PC Time&Date: 12:13:57 03/23/2005
NE Time&Date: 13:15:32 09/15/2004
USER NAME:
User_s
COMMAND:
Gettest DUDCTMA:NAME=RACK:0/DUDCTMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/DUDCTMA:0
testMonitor =
phaseId = PreliminaryTestsDudctma
phaseStatus = Running
phaseId = CheckAlarmStatusDudctma
phaseStatus = Waiting
phaseId = EndTestDudctma
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
END OF OUTPUT FOR JOB 216
A50016-G5100-B333-04-7619
Id:0900d805805944c0
303
DUDCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest DUDCTMA:NAME=RACK:0/DUDCTMA:0;
LOCK DUDCTMA
LOCK DUDCTMA
NAME=RACK:0..7/DUDCTMA:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUDCTMA
h LOCK DUDCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of DUAMCO_DC_TMA (DC Power
Supply Module of TMA).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
304
Id:0900d805805944c0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUDCTMA
The specified change of administrative state has been perfomed:
JOB: 83
PC Time&Date: 16:38:58 03/23/2005
NE Time&Date: 16:36:52 09/15/2004
USER NAME:
User_s
COMMAND:
Lock DUDCTMA:NAME=RACK:0/DUDCTMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 83
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 84
PC Time&Date: 16:38:58 03/23/2005
NE Time&Date: 16:36:52 09/15/2004
USER NAME:
User_s
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/DUDCTMA:0
Administrative State = LOCKED
Notification Identifier = 511
END OF OUTPUT FOR JOB 84
Operation Failed
The specified change of administrative state has not been performed.
A50016-G5100-B333-04-7619
Id:0900d805805944c0
305
DUDCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
Application Guidelines:
The commands for the objects DUDCTMA:2n and DUDCTMA:2n+1 are not allowed if
the object DUAMCO:n exists and is in the state OST.AVS = enabled.degraded (firmware download is active).
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Lock DUDCTMA:NAME=RACK:0/DUDCTMA:0;
PERFTEST DUDCTMA
PERFTEST DUDCTMA NAME=RACK:0..7/DUDCTMA:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUDCTMA
h PERFTEST DUDCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in the object.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSEP.
JOB: 216
PC Time&Date: 12:13:57 03/23/2005
NE Time&Date: 13:15:32 09/15/2004
USER NAME:
User_s
COMMAND:
Perftest DUDCTMA:NAME=RACK:0/DUDCTMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/DUDCTMA:0
tO = BTSETEST:2
306
Id:0900d805805944c0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUDCTMA
END OF OUTPUT FOR JOB 216
JOB: 217
PC Time&Date: 12:13:58 03/23/2005
NE Time&Date: 13:15:33 09/15/2004
USER NAME:
User_s
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:2
ChangeInfo = created
END OF OUTPUT FOR JOB 217
JOB: 218
PC Time&Date: 12:13:58 03/23/2005
NE Time&Date: 13:15:33 09/15/2004
USER NAME:
User_s
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/DUDCTMA:0
Operational State = ENABLED
Availability Status = NULL_value
Standby Status = Cold_Standby
Notification Identifier = 256
END OF OUTPUT FOR JOB 218
JOB: 219
A50016-G5100-B333-04-7619
Id:0900d805805944c0
307
DUDCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
PC Time&Date: 12:13:58 03/23/2005
NE Time&Date: 13:15:33 09/15/2004
USER NAME:
User_s
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:2
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/DUDCTMA:0
executedPhases =
PreliminaryTestsDudctma
BootEepromTestDudctma
SerialEepromTestDudctma
EndTestDudctma
END OF OUTPUT FOR JOB 219
JOB: 220
PC Time&Date: 12:13:58 03/23/2005
NE Time&Date: 13:15:33 09/15/2004
USER NAME:
User_s
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:2
ChangeInfo = deleted
END OF OUTPUT FOR JOB 220
The test results will be displayed at the end of the test phases.
308
Id:0900d805805944c0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUDCTMA
Result TEST:
name =
TEST:<n>
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: Message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
In phase 3 MO must be locked previous to the command execution
A50016-G5100-B333-04-7619
Id:0900d805805944c0
309
DUDCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
Example of Command Execution:
Perftest DUDCTMA:NAME=RACK:0/DUDCTMA:0;
STOPTEST DUDCTMA
STOPTEST DUDCTMA NAME=RACK:0..7/DUDCTMA:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUDCTMA
h STOPTEST DUDCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
...
.
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
phaseId =
310
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
Id:0900d805805944c0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUDCTMA
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
Application Guidelines:
None.
Example of Command Execution:
Stoptest DUDCTMA:NAME=RACK:0/DUDCTMA:0;
UNLOCK DUDCTMA
UNLOCK DUDCTMA
NAME=RACK:0..7/DUDCTMA:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUDCTMA
h UNLOCK DUDCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of DUAMCO_DC_TMA (DC Power
Supply Module of TMA).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 85
PC Time&Date: 16:39:03 03/23/2005
NE Time&Date: 16:36:57 09/15/2004
USER NAME:
User_s
COMMAND:
Unlock DUDCTMA:NAME=RACK:0/DUDCTMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 85
A50016-G5100-B333-04-7619
Id:0900d805805944c0
311
DUDCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 86
PC Time&Date: 16:39:03 03/23/2005
NE Time&Date: 16:36:57 09/15/2004
USER NAME:
User_s
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/DUDCTMA:0
Administrative State = UNLOCKED
Notification Identifier = 512
END OF OUTPUT FOR JOB 86
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
The commands for the objects DUDCTMA:2n and DUDCTMA:2n+1 are not allowed if
the object DUAMCO:n exists and is in the state OST.AVS = enabled.degraded (firmware download is active).
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Unlock DUDCTMA:NAME=RACK:0/DUDCTMA:0;
312
Id:0900d805805944c0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DULNA
DULNA
The DULNA object represents the low noise amplifier of DUAMCO (Dual Antenna Multicoupler) or FDUAMCO.
CREATE DULNA
CREATE DULNA
NAME=RACK:0..7/DULNA:0..11 ,CELLNO= ,COMBMD=
[,LNAMDB=] [,LNAPRED=] [,SCELLNO=] ,WDLNA=
[,GNADB=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h
CREATE DULNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the DULNA (Low Noise Amplifier of Duplex Antenna Multicoupler)
together with its attributes to the BTSE data base.
Long Names:
NAME
Address of the managed object
CELLNO
cellNumber
COMBMD
combMode
LNAMDB
lnaModeDb
LNAPRED
lnaPredecessor
SCELLNO
secondCellNumber
WDLNA
wiringDataLna
GNADB
gainAdjustDb
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 92
PC Time&Date: 11:59:23 03/23/2005
NE Time&Date: 13:00:58 09/15/2004
A50016-G5100-B333-04-7619
Id:0900d805805944c2
313
DULNA
BS-4x / 82 II / 240 / 241 / 240XL commands
USER NAME:
User_pin
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/DULNA:0
ChangeInfo = created
END OF OUTPUT FOR JOB 92
JOB: 93
PC Time&Date: 11:59:23 03/23/2005
NE Time&Date: 13:00:58 09/15/2004
USER NAME:
User_pin
COMMAND:
Create
DULNA:NAME=RACK:0/DULNA:0,CELLNO=0,COMBMD=OneToOne,WDLNA=CU0N;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
cellNumber = 0
combMode = OneToOne
secondCellNumber = 2
wiringDataLna = CU0N
gainAdjustDb = DIP
END OF OUTPUT FOR JOB 93
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 94
PC Time&Date: 11:59:23 03/23/2005
NE Time&Date: 13:00:58 09/15/2004
314
Id:0900d805805944c2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DULNA
USER NAME:
User_pin
COMMAND:
Create DULNA:NAME=RACK:0/DULNA:2;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
Object instance unknown (-9)
END OF OUTPUT FOR JOB 94
Application Guidelines:
One DUAMCO contains two DUAMCO_LNA. The first DUAMCO within the rack is
put in the first slot, the second DUAMCO in the second slot and so on. This means
that DUAMCO_LNA 0 and DUAMCO_LNA 1 are always physically located in the
first slot within the rack, the DUAMCO_LNA 2 and DUAMCO_LNA 3 in the second
slot and so on
The DUAMCO_LNA and the CUs must be in the same rack and must belong to the
same cell
Each CU has a 'normal path' RX input and a 'diversity path' RX input and the
operator must indicate which of them is wired to the DUAMCO_LNA
If there is no wiring the operator must not provide a value for the attribute LNAPRED
(if a get is done the attribute identifier will be put into the list of unavailable attributes)
If there is no wiring for the attribute LNAPRED and the operator enters a value, this
error can be corrected by a deletion of the object and a re-creation of the object
The BTSE SW doesn't check if the entered "predecessor (relative number)" is compatible with typeOfBTSE; e.g. an input of TMA 11 is not rejected in a BS40 although
BS40 allows only the creation of TMA 0-5
The BTSE SW doesn't check if the entered "predecessor (rack)" is compatible with
typeOfBTSE; e.g. an input of RACK 1 is not rejected in a BS40 although BS40
allows only the creation of RACK 0
Wildcard addressing is not possible
The commands for the objects DULNA:2n and DULNA:2n+1 are not allowed if the
object DUAMCO:n exists and it is in the state OST.AVS = enabled.degraded (firmware download is active)
Example of Command Execution:
Create DULNA:NAME=RACK:1/DULNA:0,CELLNO=0,COMBMD=FourToOne,
SCELLNO=2,WDLNA=CU0N&CU1N&CU2N&CU3N,LNAPRED=DULNA-RACK00,GNADB=DIP,LNAMDB=<DIP>;
DELETE DULNA
DELETE DULNA
A50016-G5100-B333-04-7619
NAME=RACK:0..7/DULNA:0..11;
Id:0900d805805944c2
315
DULNA
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h
DELETE DULNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the DULNA (Low Noise Amplifier of Duplex Antenna Multicoupler) together with its attributes from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 86
PC Time&Date: 11:58:47 03/23/2005
NE Time&Date: 13:00:22 09/15/2004
USER NAME:
User_pin
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/DULNA:0
ChangeInfo = deleted
END OF OUTPUT FOR JOB 86
JOB: 87
PC Time&Date: 11:58:47 03/23/2005
NE Time&Date: 13:00:22 09/15/2004
USER NAME:
316
User_pin
Id:0900d805805944c2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COMMAND:
DULNA
Delete DULNA:NAME=RACK:0/DULNA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 87
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
DULNA must be locked in Phase 3, before deletion
If this object is deleted, the related TRXs are out of service
The commands for the objects DULNA:2n and DULNA:2n+1 are not allowed if the
object DUAMCO:n exists and it is in the state OST.AVS = enabled.degraded (firmware download is active)
Example of Command Execution:
Delete DULNA:NAME=RACK:0/DULNA:0;
GET DULNA
GET DULNA
NAME=RACK:0..7/DULNA:0..11 [,REQATTL=ALS, AST,
AVS, CELLNO, GNA, COMBMD, LNAMDB, LNAMODE,
LNAPRED, OST, PRS, RELFUNCOBJ, SCELLNO, WDLNA,
GNADB];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h
GET DULNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the DULNA (Low Noise Amplifier of Duplex
Antenna Multicoupler).
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
CELLNO
cellNumber
A50016-G5100-B333-04-7619
Id:0900d805805944c2
317
DULNA
BS-4x / 82 II / 240 / 241 / 240XL commands
GNA
gainAdjust(dB)
COMBMD
combMode
LNAMDB
lnaModeDb
LNAMODE
lnaMode
LNAPRED
lnaPredecessor
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
SCELLNO
secondCellNumber
WDLNA
wiringDataLna
GNADB
gainAdjustDb
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 63
PC Time&Date: 11:58:17 03/23/2005
NE Time&Date: 12:59:52 09/15/2004
USER NAME:
User_pin
COMMAND:
Get DULNA:NAME=RACK:0/DULNA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
cellNumber = 0
cableLossAdjust(dB) = N_00
combMode = OneToOne
gainAdjustDb = N_00
lnaMode = AMCO_MODE
lnaModeDb = DIP
lnaPredecessor = Null
operationalState = ENABLED
proceduralStatus = NULL
318
Id:0900d805805944c2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DULNA
relatedFuncObjects =
secondCellNumber = NotUsed
wiringDataLna = CU1
END OF OUTPUT FOR JOB 63
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
The value for the attribute relatedFuncObjects in LMT Phase 2 is "not configured"
The value for proceduralStatus must be NULL
Example of Command Execution:
Get
DULNA:NAME=RACK:0/DULNA:0,REQATTL=ALS&AST&AVS&CELLNO&GNA&CO
MBMD&RELFUNCOBJ&LNAMODE&LNAPRED&OST&PRS&SCELLNO&WDLNA;GNADB&LNAMDB;
GETTEST DULNA
GETTEST DULNA
NAME=RACK:0..7/DULNA:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h
GETTEST DULNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the object test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 72
PC Time&Date: 11:58:33 03/23/2005
A50016-G5100-B333-04-7619
Id:0900d805805944c2
319
DULNA
BS-4x / 82 II / 240 / 241 / 240XL commands
NE Time&Date: 13:00:08 09/15/2004
USER NAME:
User_pin
COMMAND:
Gettest DULNA:NAME=RACK:0/DULNA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/DULNA:0
testMonitor =
phaseId = PreliminaryTestsDulna
phaseStatus = Running
phaseId = CheckAlarmStatusDulna
phaseStatus = Waiting
phaseId = EndTestDulna
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
END OF OUTPUT FOR JOB 72
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
320
Id:0900d805805944c2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DULNA
Example of Command Execution:
Gettest DULNA:NAME=RACK:0/DULNA:0;
LOCK DULNA
LOCK DULNA
NAME=RACK:0..7/DULNA:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h
LOCK DULNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of DULNA (Low Noise Amplifier of
Duplex Antenna Multicoupler).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 73
PC Time&Date: 11:58:33 03/23/2005
NE Time&Date: 13:00:08 09/15/2004
USER NAME:
User_pin
COMMAND:
Lock DULNA:NAME=RACK:0/DULNA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 73
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
A50016-G5100-B333-04-7619
Id:0900d805805944c2
321
DULNA
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 74
PC Time&Date: 11:58:33 03/23/2005
NE Time&Date: 13:00:08 09/15/2004
USER NAME:
User_pin
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/DULNA:0
Administrative State = LOCKED
Notification Identifier = 301
END OF OUTPUT FOR JOB 74
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
The commands for the objects DULNA:2n and DULNA:2n+1 are not allowed if the object
DUAMCO:n exists and it is in the state OST.AVS = enabled.degraded (firmware
download is active).
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Lock DULNA:NAME=RACK:0/DULNA:0;
PERFTEST DULNA
PERFTEST DULNA
NAME=RACK:0..7/DULNA:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h
PERFTEST DULNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
322
Id:0900d805805944c2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DULNA
Command Description:
This command is used to start an asynchronous test in the object.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSEP.
JOB: 77
PC Time&Date: 11:58:39 03/23/2005
NE Time&Date: 13:00:14 09/15/2004
USER NAME:
User_pin
COMMAND:
Perftest DULNA:NAME=RACK:0/DULNA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/DULNA:0
tO = BTSETEST:4
END OF OUTPUT FOR JOB 77
JOB: 78
PC Time&Date: 11:58:39 03/23/2005
NE Time&Date: 13:00:14 09/15/2004
USER NAME:
User_pin
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:4
ChangeInfo = created
END OF OUTPUT FOR JOB 78
A50016-G5100-B333-04-7619
Id:0900d805805944c2
323
DULNA
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 79
PC Time&Date: 11:58:39 03/23/2005
NE Time&Date: 13:00:14 09/15/2004
USER NAME:
User_pin
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/DULNA:0
Operational State = ENABLED
Availability Status = NULL_value
Notification Identifier = 305
END OF OUTPUT FOR JOB 79
JOB: 80
PC Time&Date: 11:58:39 03/23/2005
NE Time&Date: 13:00:14 09/15/2004
USER NAME:
User_pin
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:4
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/DULNA:0
executedPhases =
PreliminaryTestsDulna
CheckAlarmStatusDulna
EndTestDulna
324
Id:0900d805805944c2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DULNA
END OF OUTPUT FOR JOB 80
JOB: 81
PC Time&Date: 11:58:39 03/23/2005
NE Time&Date: 13:00:14 09/15/2004
USER NAME:
User_pin
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:4
ChangeInfo = deleted
END OF OUTPUT FOR JOB 81
The test results will be displayed at the end of the test phases.
Result TEST:
name =
TEST:<n>
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
A50016-G5100-B333-04-7619
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
Id:0900d805805944c2
325
DULNA
BS-4x / 82 II / 240 / 241 / 240XL commands
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: Message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
In phase 3 MO must be locked previous to the command execution
Example of Command Execution:
Perftest DULNA:NAME=RACK:0/DULNA:0;
SET DULNA
SET DULNA
NAME=RACK:0..7/DULNA:0..11 [,LNAMDB=] [,SCELLNO=]
[,WDLNA=] [,GNADB=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h
SET DULNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command sets the attributes of the DULNA (Low Noise Amplifier of Duplex Antenna
Multicoupler) to the BTSE data base.
Long Names:
326
NAME
Address of the managed object
LNAMDB
lnaModeDb
SCELLNO
secondCellNumber
WDLNA
wiringDataLna
GNADB
gainAdjustDb
Id:0900d805805944c2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DULNA
System Responses:
Operation Completed
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
JOB: 75
PC Time&Date: 11:58:36 03/23/2005
NE Time&Date: 13:00:11 09/15/2004
USER NAME:
User_pin
COMMAND:
Set DULNA:NAME=RACK:0/DULNA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 75
Operation Failed
The specified attributes have not been set. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible.
Application Guidelines:
One DUAMCO contains two DUAMCO_LNA. The first DUAMCO within the rack is
put in the first slot, the second DUAMCO in the second slot and so on. This means
that DUAMCO_LNA 0 and DUAMCO_LNA 1 are always physically located in the
first slot within the rack, the DUAMCO_LNA 2 and DUAMCO_LNA 3 in the second
slot and so on
The DUAMCO_LNA and the CUs must be in the same rack and must belong to the
same cell
Each CU has a 'normal path' RX input and a 'diversity path' RX input and the
operator must indicate which of them is wired to the DUAMCO_LNA
Wildcard addressing is not possible
All CUs which are listed in a previous GET DULNA for WDLNA have to be locked
(LOCK CU command) before one of these CUs can be removed from WDLNA.
Before locking these CUs first a shutdown of the TRXs related to these CUs should
be done
The commands for the objects DULNA:2n and DULNA:2n+1 are not allowed if the
object DUAMCO:n exists and it is in the state OST.AVS = enabled.degraded (firmware download is active)
Example of Command Execution:
Set DULNA:NAME=RACK:0/DULNA:0,SCELLNO=2,WDLNA=CU0N&CU1N&
CU2N&CU3N,GNADB=DIP,LNAMDB=<DIP>;
A50016-G5100-B333-04-7619
Id:0900d805805944c2
327
DULNA
BS-4x / 82 II / 240 / 241 / 240XL commands
STOPTEST DULNA
STOPTEST DULNA
NAME=RACK:0..7/DULNA:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h
STOPTEST DULNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
...
.
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
328
Id:0900d805805944c2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DULNA
Application Guidelines:
None.
Example of Command Execution:
Stoptest DULNA:NAME=RACK:0/DULNA:0;
UNLOCK DULNA
UNLOCK DULNA
NAME=RACK:0..7/DULNA:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DULNA h
UNLOCK DULNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the DULNA (Duplex Antenna Multicoupler).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 82
PC Time&Date: 11:58:41 03/23/2005
NE Time&Date: 13:00:16 09/15/2004
USER NAME:
User_pin
COMMAND:
Unlock DULNA:NAME=RACK:0/DULNA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 82
CHANGED STATE EVENT REPORT:
A50016-G5100-B333-04-7619
Id:0900d805805944c2
329
DULNA
BS-4x / 82 II / 240 / 241 / 240XL commands
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 83
PC Time&Date: 11:58:41 03/23/2005
NE Time&Date: 13:00:16 09/15/2004
USER NAME:
User_pin
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/DULNA:0
Administrative State = UNLOCKED
Notification Identifier = 306
END OF OUTPUT FOR JOB 83
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
The commands for the objects DULNA:2n and DULNA:2n+1 are not allowed if the object
DUAMCO:n exists and it is in the state OST.AVS = enabled.degraded (firmware
download is active).
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Unlock DULNA:NAME=RACK:0/DULNA:0;
330
Id:0900d805805944c2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUVSWR
DUVSWR
The DUVSWR object represents the VSWR of DUAMCO; a VSWR alarm indicates an
antenna failure.
CREATE DUVSWR
CREATE DUVSWR
NAME=RACK:0..7/DUVSWR:0..11 ,CELLNO= ,COMBMD=
,WDDUVSWR= [,VSWRTDB=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h
CREATE DUVSWR
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the DUVSWR (Voltage Standing Wave Ratio Duplex Antenna Multicoupler) together with its attributes to the BTSE data base.
Long Names:
NAME
Address of the managed object
CELLNO
cellNumber
COMBMD
combMode
WDDUVSWR
wiringDuamcoVswr
VSWRTDB
vswrThresholdDb
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 112
PC Time&Date: 12:00:05 03/23/2005
NE Time&Date: 13:01:40 09/15/2004
USER NAME:
User_pon
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
A50016-G5100-B333-04-7619
Id:0900d805805944c4
331
DUVSWR
BS-4x / 82 II / 240 / 241 / 240XL commands
ChangedConfigurationNotification:
name = RACK:0/DUVSWR:0
ChangeInfo = created
END OF OUTPUT FOR JOB 112
JOB: 113
PC Time&Date: 12:00:05 03/23/2005
NE Time&Date: 13:01:40 09/15/2004
USER NAME:
User_pon
COMMAND:
Create DUVSWR:NAME=RACK:0/DUVSWR:0,CELLNO=0,WDDUVSWR=CU0,COMBMD=OneToOne;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
cellNumber = 0
wiringDuamcoVswr = CU0
combMode = OneToOne
vswrThresholdDb = LOW_2_0_HIGH_3_0
END OF OUTPUT FOR JOB 113
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 114
PC Time&Date: 12:00:05 03/23/2005
NE Time&Date: 13:01:40 09/15/2004
USER NAME:
User_pon
COMMAND:
Create DUVSWR:NAME=RACK:0/DUVSWR:2;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
Object instance unknown (-9)
332
Id:0900d805805944c4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUVSWR
END OF OUTPUT FOR JOB 114
Application Guidelines:
One DUAMCO contains two DUAMCO_VSWR. The first DUAMCO within the rack
is put in the first slot, the second DUAMCO in the second slot and so on. This means
that DUAMCO_VSWR 0 and DUAMCO_VSWR 1 are always physically located in
the first slot within the rack, the DUAMCO_VSWR 2 and DUAMCO_VSWR 3 in the
second slot and so on
The DUAMCO_VSWR and the CUs must be in the same rack and must belong to
the same cell
Due to the physical properties of the DUAMCO_VSWR, up to 4 CUs can be connected
Wildcard addressing is not possible
The commands for the objects DUVSWR:2n and DUVSWR:2n+1 are not allowed if
the object DUAMCO:n exists and it is in the state OST.AVS = enabled.degraded
(firmware download is active)
Example of Command Execution:
Create DUVSWR:NAME=RACK:0/DUVSWR:0,CELLNO=0,COMBMD=TwoToTwo,
WDDUVSWR=CU0&CU1,VSWRTDB=LOW_2_0_HIGH_3_0;
DELETE DUVSWR
DELETE DUVSWR
NAME=RACK:0..7/DUVSWR:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h
DELETE DUVSWR
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the DUVSWR (Voltage Standing Wave Ratio Duplex Antenna
Multicoupler) together with its attributes from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
A50016-G5100-B333-04-7619
Id:0900d805805944c4
333
DUVSWR
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 110
PC Time&Date: 11:59:58 03/23/2005
NE Time&Date: 13:01:33 09/15/2004
USER NAME:
User_pon
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/DUVSWR:0
ChangeInfo = deleted
END OF OUTPUT FOR JOB 110
JOB: 111
PC Time&Date: 11:59:58 03/23/2005
NE Time&Date: 13:01:33 09/15/2004
USER NAME:
User_pon
COMMAND:
Delete DUVSWR:NAME=RACK:0/DUVSWR:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 111
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
334
DUVSWR must be locked in Phase 3, before deletion
If this object is deleted, the related TRXs are out of service
The commands for the objects DUVSWR:2n and DUVSWR:2n+1 are not allowed if
the object DUAMCO:n exists and it is in the state OST.AVS = enabled.degraded
(firmware download is active)
Id:0900d805805944c4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUVSWR
Example of Command Execution:
Delete DUVSWR:NAME=RACK:0/DUVSWR:0;
GET DUVSWR
GET DUVSWR
NAME=RACK:0..7/DUVSWR:0..11 [,REQATTL=ALS, AST,
AVS, CELLNO, COMBMD, OST, PRS, RELFUNCOBJ,
WDDUVSWR, VSWRTDB];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h
GET DUVSWR
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the DUVSWR (Voltage Standing Wave Ratio
Duplex Antenna Multicoupler).
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
CELLNO
cellNumber
COMBMD
combMode
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
WDDUVSWR
wiringDuamcoVswr
VSWRTDB
vswrThresholdDb
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 95
PC Time&Date: 11:59:35 03/23/2005
NE Time&Date: 13:01:10 09/15/2004
A50016-G5100-B333-04-7619
Id:0900d805805944c4
335
DUVSWR
BS-4x / 82 II / 240 / 241 / 240XL commands
USER NAME:
User_pon
COMMAND:
Get DUVSWR:NAME=RACK:0/DUVSWR:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Locked
availabilityStatus = NULL
cellNumber = 0
combMode = TwoToTwo
operationalState = ENABLED
proceduralStatus = NULL
relatedFuncObjects =
BTS:0/TRX:2
vswrThresholdDb = LOW_2_0_HIGH_3_0
wiringDuamcoVswr = CU0
END OF OUTPUT FOR JOB 95
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
The value for the attribute gsmFunctionalID in LMT Phase 2 is "not configured"
The value for proceduralStatus must be NULL
Example of Command Execution:
Get DUVSWR:NAME=RACK:0/DUVSWR:0,REQATTL=ALS&AST&AVS&CELLNO&
COMBMD&OST&PRS&RELFUNCOBJ&WDDUVSWR&VSWRTDB;
GETTEST DUVSWR
GETTEST DUVSWR
NAME=RACK:0..7/DUVSWR:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h
GETTEST DUVSWR
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the object test.
336
Id:0900d805805944c4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUVSWR
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 101
PC Time&Date: 11:59:50 03/23/2005
NE Time&Date: 13:01:25 09/15/2004
USER NAME:
User_pon
COMMAND:
Gettest DUVSWR:NAME=RACK:0/DUVSWR:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/DUVSWR:0
testMonitor =
phaseId = PreliminaryTestsDuvswr
phaseStatus = Running
phaseId = CheckAlarmStatusDuvswr
phaseStatus = Waiting
phaseId = EndTestDuvswr
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
END OF OUTPUT FOR JOB 101
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
A50016-G5100-B333-04-7619
Id:0900d805805944c4
337
DUVSWR
BS-4x / 82 II / 240 / 241 / 240XL commands
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest DUVSWR:NAME=RACK:0/DUVSWR:0;
LOCK DUVSWR
LOCK DUVSWR
NAME=RACK:0..7/DUVSWR:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h
LOCK DUVSWR
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of DUVSWR (Voltage Standing Wave
Ratio Duplex Antenna Multicoupler).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
338
Id:0900d805805944c4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUVSWR
JOB: 99
PC Time&Date: 11:59:48 03/23/2005
NE Time&Date: 13:01:23 09/15/2004
USER NAME:
User_pon
COMMAND:
Lock DUVSWR:NAME=RACK:0/DUVSWR:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 99
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 100
PC Time&Date: 11:59:48 03/23/2005
NE Time&Date: 13:01:23 09/15/2004
USER NAME:
User_pon
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/DUVSWR:0
Administrative State = LOCKED
Notification Identifier = 312
END OF OUTPUT FOR JOB 100
Operation Failed
The specified change of administrative state has not been performed.
A50016-G5100-B333-04-7619
Id:0900d805805944c4
339
DUVSWR
BS-4x / 82 II / 240 / 241 / 240XL commands
Application Guidelines:
The commands for the objects DUVSWR:2n and DUVSWR:2n+1 are not allowed if the
object DUAMCO:n exists and it is in the state OST.AVS = enabled.degraded (firmware
download is active).
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Lock DUVSWR:NAME=RACK:0/DUVSWR:0;
PERFTEST DUVSWR
PERFTEST DUVSWR
NAME=RACK:0..7/DUVSWR:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h
PERFTEST DUVSWR
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in the object.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSEP.
JOB: 102
PC Time&Date: 11:59:50 03/23/2005
NE Time&Date: 13:01:25 09/15/2004
USER NAME:
User_pon
COMMAND:
Perftest DUVSWR:NAME=RACK:0/DUVSWR:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/DUVSWR:0
340
Id:0900d805805944c4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUVSWR
tO = BTSETEST:5
END OF OUTPUT FOR JOB 102
JOB: 103
PC Time&Date: 11:59:50 03/23/2005
NE Time&Date: 13:01:25 09/15/2004
USER NAME:
User_pon
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:5
ChangeInfo = created
END OF OUTPUT FOR JOB 103
JOB: 104
PC Time&Date: 11:59:50 03/23/2005
NE Time&Date: 13:01:25 09/15/2004
USER NAME:
User_pon
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/DUVSWR:0
Operational State = ENABLED
Availability Status = NULL_value
Notification Identifier = 316
END OF OUTPUT FOR JOB 104
JOB: 105
A50016-G5100-B333-04-7619
Id:0900d805805944c4
341
DUVSWR
BS-4x / 82 II / 240 / 241 / 240XL commands
PC Time&Date: 11:59:50 03/23/2005
NE Time&Date: 13:01:25 09/15/2004
USER NAME:
User_pon
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:5
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/DUVSWR:0
executedPhases =
PreliminaryTestsDuvswr
CheckAlarmStatusDuvswr
EndTestDuvswr
END OF OUTPUT FOR JOB 105
JOB: 106
PC Time&Date: 11:59:50 03/23/2005
NE Time&Date: 13:01:25 09/15/2004
USER NAME:
User_pon
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:5
ChangeInfo = deleted
END OF OUTPUT FOR JOB 106
The test results will be displayed at the end of the test phases.
Result TEST:
342
Id:0900d805805944c4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUVSWR
name =
TEST:<n>
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: Message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
In phase 3 MO must be locked previous to the command execution
Example of Command Execution:
Perftest DUVSWR:NAME=RACK:0/DUVSWR:0;
A50016-G5100-B333-04-7619
Id:0900d805805944c4
343
DUVSWR
BS-4x / 82 II / 240 / 241 / 240XL commands
SET DUVSWR
SET DUVSWR
NAME=RACK:0..7/DUVSWR:0..11 [,WDDUVSWR=]
[,VSWRTDB=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h
SET DUVSWR
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command sets the attributes of the DUVSWR (Voltage Standing Wave Ratio
Duplex Antenna Multicoupler) to the BTSE data base.
Long Names:
NAME
Address of the managed object
WDDUVSWR
wiringDuamcoVswr
VSWRTDB
vswrThresholdDb
System Responses:
Operation Completed
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
JOB: 109
PC Time&Date: 11:59:53 03/23/2005
NE Time&Date: 13:01:28 09/15/2004
USER NAME:
User_pon
COMMAND:
Set DUVSWR:NAME=RACK:0/DUVSWR:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 109
Operation Failed
The specified attributes have not been set. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible.
344
Id:0900d805805944c4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUVSWR
Application Guidelines:
One DUAMCO contains two DUAMCO_VSWR. The first DUAMCO within the rack
is put in the first slot, the second DUAMCO in the second slot and so on. This means
that DUAMCO_VSWR 0 and DUAMCO_VSWR 1 are always physically located in
the first slot within the rack, the DUAMCO_VSWR 2 and DUAMCO_VSWR 3 in the
second slot and so on
The DUAMCO_VSWR and the CUs must be in the same rack and must belong to
the same cell
Due to the physical properties of the DUAMCO_VSWR, up to 4 CUs can be connected
Wildcard addressing is not possible
All CUs which are listed in a previous GET DUVSWR for WDDUVSWR have to be
locked (LOCK CU command) before one of these CUs can be removed from
WDDUVSWR. Before locking these CUs first a shutdown of the TRXs related to
these CUs should be done
The commands for the objects DUVSWR:2n and DUVSWR:2n+1 are not allowed if
the object DUAMCO:n exists and it is in the state OST.AVS = enabled.degraded
(firmware download is active)
Example of Command Execution:
Set DUVSWR:NAME=RACK:0/DUVSWR:0,WDDUVSWR=CU0N&CU1N&CU2N&CU3N,VSWRTDB=LOW_2_0_HIGH_3_0;
STOPTEST DUVSWR
STOPTEST DUVSWR
NAME=RACK:0..7/DUVSWR:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h
STOPTEST DUVSWR
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
A50016-G5100-B333-04-7619
Id:0900d805805944c4
345
DUVSWR
BS-4x / 82 II / 240 / 241 / 240XL commands
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
...
.
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
phaseId =
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
Application Guidelines:
None.
Example of Command Execution:
Stoptest DUVSWR:NAME=RACK:0/DUVSWR:0;
UNLOCK DUVSWR
UNLOCK DUVSWR
NAME=RACK:0..7/DUVSWR:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DUVSWR h
UNLOCK DUVSWR
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the DUVSWR (Voltage Standing
Wave Ratio Duplex Antenna Multicoupler).
346
Id:0900d805805944c4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUVSWR
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 97
PC Time&Date: 11:59:44 03/23/2005
NE Time&Date: 13:01:19 09/15/2004
USER NAME:
User_pon
COMMAND:
Unlock DUVSWR:NAME=RACK:0/DUVSWR:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 97
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 98
PC Time&Date: 11:59:44 03/23/2005
NE Time&Date: 13:01:19 09/15/2004
USER NAME:
User_pon
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/DUVSWR:0
Administrative State = UNLOCKED
Notification Identifier = 311
A50016-G5100-B333-04-7619
Id:0900d805805944c4
347
DUVSWR
BS-4x / 82 II / 240 / 241 / 240XL commands
END OF OUTPUT FOR JOB 98
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
The commands for the objects DUVSWR:2n and DUVSWR:2n+1 are not allowed if the
object DUAMCO:n exists and it is in the state OST.AVS = enabled.degraded (firmware
download is active).
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Unlock DUVSWR:NAME=RACK:0/DUVSWR:0;
348
Id:0900d805805944c4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ENVABTSE
ENVABTSE
The ENVABTSE object is used to manage the enviromental alarms of the BTSE.
CREATE ENVABTSE
CREATE ENVABTSE
NAME=RACK:0..7/ENVABTSE:0..56 [,ASEV=]
[,ASTRING=] ,INTINF=;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ENVABTSE
h CREATE ENVABTSE
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command configures one of the 9 possible environmental alarms (in the Base Rack
optionally the ACTM can be installed that supplies 48 additional ENVAs) in the BTSE
database (BS40/41, BS240/241, BS240XL, BS40II).
For BS82II this command configures one of the 6 possible environmental alarms.
Long Names:
NAME
Address of the managed object
ASEV
associatedSeverity
ASTRING
associatedString
INTINF
interfaceInformation
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 116
PC Time&Date: 12:00:26 03/23/2005
NE Time&Date: 13:02:01 09/15/2004
USER NAME:
User_titti
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
A50016-G5100-B333-04-7619
Id:0900d805805944c6
349
ENVABTSE
BS-4x / 82 II / 240 / 241 / 240XL commands
ChangedConfigurationNotification:
name = RACK:0/ENVABTSE:0
ChangeInfo = created
END OF OUTPUT FOR JOB 116
JOB: 117
PC Time&Date: 12:00:26 03/23/2005
NE Time&Date: 13:02:01 09/15/2004
USER NAME:
User_titti
COMMAND:
Create ENVABTSE:NAME=RACK:0/ENVABTSE:0,INTINF=low;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
interfaceInformation = low
END OF OUTPUT FOR JOB 117
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 119
PC Time&Date: 12:00:31 03/23/2005
NE Time&Date: 13:02:06 09/15/2004
USER NAME:
User_titti
COMMAND:
Create ENVABTSE:NAME=RACK:0/ENVABTSE:1,INTINF=high;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
Message cannot be performed (-17)
END OF OUTPUT FOR JOB 119
350
Id:0900d805805944c6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ENVABTSE
Application Guidelines:
For BS241:
All ENVAs can be left as not equipped
In the Base Rack with only ACTC installed 9 ENVAs within the range from 0...8 are
supported as shown in the table below. In the Base Rack optionally the ACTM can
be installed that supplies 48 additional ENVAs
In the other Racks with ACTC installed 9 ENVAs within the range from 0...8 are supported as shown in the table below
ENVA No.
Application
Heatexchanger - 0
Heatexchanger - 1
Heatexchanger - 2
Rack/Shelter in service
Smoke
Battery Fuse 0, 1, 2
Over Voltage Protection (it has to be configured with "HIGH")
7
8
Microwave
For BS240 Compact Site:
The AC/DC alarm line for the AC/DC converter and for the battery must be connected to a site input which is used as a trigger for the emergency configuration.
A special setting of the attribute "associatedString" in the corresponding site input
allows the operator to indicate that the support of emergency configuration is
required for the 3rd party battery backup unit system. The string indicates from
which source, AC/DC CAN node or site input, the trigger for the emergency configuration is expected. In case the string pattern is set to "##ACDC_FAULT" the trigger
is expected from the site input of the corresponding ENVABTSE object. In all other
cases the normal behavior is maintained.
For simplicity there is no check if the string "##ACDC_FAULT" is used for more than
one ENVABTSE object. If the operator has set the "associatedString" attribute of an
ENVABTSE object to "##ACDC_FAULT" for the AC/DC alarm line, the emergency
configuration is deactivated if all trigger sources have ceased their alarm.
ENVA No.
Application
Severity
String
HIGH
CRITICAL
Over Voltage Protection ()
HIGH
CRITICAL
Shelter door open
10
HIGH
CRITICAL
Conditioners FAULT
A50016-G5100-B333-04-7619
Id:0900d805805944c6
351
ENVABTSE
BS-4x / 82 II / 240 / 241 / 240XL commands
11
HIGH
CRITICAL
Shelter Temperature Out Tolerance
12
HIGH
CRITICAL
Shelter in service
13
HIGH
CRITICAL
Not connected
14
HIGH
CRITICAL
Mains Breakdown
15
HIGH
CRITICAL
Critical Battery Breakdown
16
HIGH
CRITICAL
Critical Battery Charging Fault
17
HIGH
CRITICAL
-48 dc Out Tolerance
18
HIGH
CRITICAL
Redundancy Lost
19
HIGH
CRITICAL
Not connected
20
HIGH
CRITICAL
Not connected
21
HIGH
CRITICAL
Not connected
22
HIGH
CRITICAL
Not connected
27
HIGH
CRITICAL
Critical Smoke
28
HIGH
CRITICAL
Critical Available 1
29
HIGH
CRITICAL
Critical Available 2
30
HIGH
CRITICAL
Critical AC lightning Protection
31
HIGH
CRITICAL
Critical Available 3
32
HIGH
CRITICAL
Critical Available 4
33
HIGH
CRITICAL
Critical Available 5
34
HIGH
CRITICAL
Critical Conditioner ALM
34
HIGH
CRITICAL
Critical Filters ALM
36
HIGH
CRITICAL
Critical Available 6
37
HIGH
CRITICAL
Critical Available 7
38
HIGH
CRITICAL
Critical Available 8
39
HIGH
CRITICAL
Critical Available 9
40
HIGH
CRITICAL
Critical Available 10
For BS40II:
The FAN5 alarm is not utilized in the case of a BS-40II (deactivated by S/W).
ACTC-3 alarms
ENVA No.
352
High / Low Active
High / Low Active
High / Low Active Mains Breackdown (MBR) note 1 and 2
High / Low Active Battery Breackdown (BBR) note 1
Id:0900d805805944c6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ENVABTSE
SMOKE - High / Low Active
Battery Breacker (BB) - High / Low Active
Over Voltage Protection(OVP) - High / Low Active
High / Low Active - Battery Charger Fault (BCHF) note 1
High / Low Active - -48Vdc Out of Tolerance (48OTB) note 1
Note:
1. Only relevant for BS with AC/DC system, all AC/DC alarms are "High Active".
2. For MBR alarm the 'associated string' must be: '##ACDC_FAULT' to make this
alarm trigger the 'emergency configuration'.'emergency configuration'
Example of Command Execution:
Create ENVABTSE:NAME=RACK:0/ENVABTSE:17,INTINF=high,
ASEV=CRITICAL, ASTRING="Air Condition. Sys. Fault";
DELETE ENVABTSE
DELETE ENVABTSE
NAME=RACK:0..7/ENVABTSE:0..56;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ENVABTSE
h DELETE ENVABTSE
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
BS24x, BS4x
This command deletes one of the 9 possible environmental alarms (in the Base Rack
optionally the ACTM can be installed that supplies 48 additional ENVAs) from the BTSE
database.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 130
PC Time&Date: 12:00:52 03/23/2005
A50016-G5100-B333-04-7619
Id:0900d805805944c6
353
ENVABTSE
BS-4x / 82 II / 240 / 241 / 240XL commands
NE Time&Date: 13:02:27 09/15/2004
USER NAME:
User_titti
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/ENVABTSE:0
ChangeInfo = deleted
END OF OUTPUT FOR JOB 130
JOB: 131
PC Time&Date: 12:00:52 03/23/2005
NE Time&Date: 13:02:27 09/15/2004
USER NAME:
User_titti
COMMAND:
Delete ENVABTSE:NAME=RACK:0/ENVABTSE:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 131
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
ENVABTSE must be locked in phase 3 before deletion
Example of Command Execution:
Delete ENVABTSE:NAME=RACK:0/ENVABTSE:17;
GET ENVABTSE
GET ENVABTSE
354
NAME=RACK:0..7/ENVABTSE:0..56 [,REQATTL=ALS,
ASEV, AST, ASTRING, AVS, INTINF, OST, PRS, RELFUNCOBJ];
Id:0900d805805944c6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ENVABTSE
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ENVABTSE
h GET ENVABTSE
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the specified Environmental Alarm stored in the
BTSE database.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
ASEV
associatedSeverity
AST
administrativeState
ASTRING
associatedString
AVS
availabilityStatus
INTINF
interfaceInformation
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 118
PC Time&Date: 12:00:29 03/23/2005
NE Time&Date: 13:02:04 09/15/2004
USER NAME:
User_titti
COMMAND:
Get ENVABTSE:NAME=RACK:0/ENVABTSE:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
associatedSeverity = DEFAULT_DB
administrativeState = Unlocked
A50016-G5100-B333-04-7619
Id:0900d805805944c6
355
ENVABTSE
BS-4x / 82 II / 240 / 241 / 240XL commands
associatedString =
availabilityStatus = NULL
interfaceInformation = low
operationalState = ENABLED
proceduralStatus = NULL
relatedFuncObjects =
END OF OUTPUT FOR JOB 118
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
For BS24x all environmental alarms can be left as not equipped (default value)
See Application Guidelines: in CREATE ENVABTSE command for more detailed
information
Example of Command Execution:
Get ENVABTSE:NAME=RACK:0/ENVABTSE:17,REQATTL=ALS&ASEV&
ASTRING&AST&AVS&INTINF&OST&PRS&RELFUNCOBJ;
LOCK ENVABTSE
LOCK ENVABTSE
NAME=RACK:0..7/ENVABTSE:0..56;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ENVABTSE
h LOCK ENVABTSE
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the environmental alarms.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 128
356
Id:0900d805805944c6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ENVABTSE
PC Time&Date: 12:00:47 03/23/2005
NE Time&Date: 13:02:22 09/15/2004
USER NAME:
User_titti
COMMAND:
Lock ENVABTSE:NAME=RACK:0/ENVABTSE:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 1286
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 129
PC Time&Date: 12:00:47 03/23/2005
NE Time&Date: 13:02:22 09/15/2004
USER NAME:
User_titti
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/ENVABTSE:0
Administrative State = LOCKED
Notification Identifier = 332
END OF OUTPUT FOR JOB 129
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
If the administrative state is set to locked, no alarms will be caused
Example of Command Execution:
Lock ENVABTSE:NAME=RACK:0/ENVABTSE:0;
A50016-G5100-B333-04-7619
Id:0900d805805944c6
357
ENVABTSE
BS-4x / 82 II / 240 / 241 / 240XL commands
SET ENVABTSE
SET ENVABTSE
NAME=RACK:0..7/ENVABTSE:0..56 [,INTINF=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ENVABTSE
h SET ENVABTSE
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command configures one of the 9 possible environmental alarms (in the Base Rack
optionally the ACTM can be installed that supplies 48 additional ENVAs) in the BTSE
database.
Long Names:
NAME
Address of the managed object
INTINF
interfaceInformation
System Responses:
Operation Completed
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
JOB: 125
PC Time&Date: 12:00:39 03/23/2005
NE Time&Date: 13:02:14 09/15/2004
USER NAME:
User_titti
COMMAND:
Set ENVABTSE:NAME=RACK:0/ENVABTSE:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 125
Operation Failed
The specified attributes have not been set. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible.
Application Guidelines:
358
For BS24x all environmental alarms can be left as not equipped (default value)
Id:0900d805805944c6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ENVABTSE
See Application Guidelines: in CREATE ENVABTSE command for more detailed
information
For BS41 and BS241 the smoke alarm must be set on low-active or high-active
depending on the respective installed sensor type
Example of Command Execution:
Set ENVABTSE:NAME=RACK:0/ENVABTSE:4,INTINF=high;
UNLOCK ENVABTSE
UNLOCK ENVABTSE
NAME=RACK:0..7/ENVABTSE:0..56;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ENVABTSE
h UNLOCK ENVABTSE
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the environmental alarms.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 126
PC Time&Date: 12:00:41 03/23/2005
NE Time&Date: 13:02:16 09/15/2004
USER NAME:
User_titti
COMMAND:
Unlock ENVABTSE:NAME=RACK:0/ENVABTSE:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 126
A50016-G5100-B333-04-7619
Id:0900d805805944c6
359
ENVABTSE
BS-4x / 82 II / 240 / 241 / 240XL commands
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 127
PC Time&Date: 12:00:41 03/23/2005
NE Time&Date: 13:02:16 09/15/2004
USER NAME:
User_titti
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/ENVABTSE:0
Administrative State = UNLOCKED
Notification Identifier = 330
END OF OUTPUT FOR JOB 127
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
None.
Example of Command Execution:
Unlock ENVABTSE:NAME=RACK:0/ENVABTSE:0;
360
Id:0900d805805944c6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ETHCON
ETHCON
The ETHCON board provides external electrical and optical Ethernet interfaces to
connect the BSC, other BTS in multidrop-like configurations and test equipment for Abis
monitoring.
It therefore houses a manageable Ethernet switch which is controlled by the COBA.
Nevertheless the board is able to operate autonomously from the COBA in order to
maintain multidrop-like connections to other BTSE e.g. in case of a COBA reset.
The ETHCON board (ETHernet CONnection) is modeled by:
one ETHCON instance representing the board
n ETHPORT instances representing the external Ethernet ports (except for monitoring port(s))
The ETHCON object is introduced for state indication and alarm reporting. The object
state comprise the board, the traffic link and the switch management link to the COBA.
CREATE ETHCON
CREATE ETHCON
NAME=RACK:0..7/ETHCON:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ETHCON h
CREATE ETHCON
Applicability:
Phase 2.
Visibility level: 2.
Command Description:
This command adds an Ethernet Connection board to the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 1154
PC Time&Date: 01.04.2008 08:23:43 +02:00
NE Time&Date: 01.01.1990 12:57:35 +00:00
USER NAME:
Brad_1i
COMMAND:
CREATE ETHCON:NAME = RACK:0/ETHCON:0;
SW RELEASE:
A50016-G5100-B333-04-7619
01-04-19-01-07-00_08-03-19
Id:0900d805805944ca
361
ETHCON
BS-4x / 82 II / 240 / 241 / 240XL commands
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 1154
Operation Failed
None.
Application Guidelines:
The creation is rejected if a COBA2P8 or COBA4P12 is already equipped.
Example of Command Execution:
Create ETHCON:NAME=RACK:0/ETHCON:0;
DELETE ETHCON
DELETE ETHCON
NAME=RACK:0..7/ETHCON:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ETHCON h
DELETE ETHCON
Applicability:
Phase 2.
Visibility level: 2.
Command Description:
This command deletes the ETHCON (ETHernet CONnection) board from the BTSE
data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
None.
Operation Failed
None.
Application Guidelines:
The deletion is rejected as long as an ETHPORT and/or CESTUNNEL object exists.
Example of Command Execution:
Delete ETHCON:NAME=RACK:0/ETHCON:0;
GET ETHCON
GET ETHCON
362
NAME=RACK:0..7/ETHCON:0..0 [,REQATTL=ALS, AST,
AVS, OST, PRS, FWVER, RELFUNCOBJ, MONPRT];
Id:0900d805805944ca
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ETHCON
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ETHCON h
GET ETHCON
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the ETHCON.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
PRS
proceduralStatus
FWVER
firmwareVersion
RELFUNCOBJ
MONPRT
relatedFuncObjects
monitoringPort
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 1244
PC Time&Date: 01.04.2008 08:29:03 +02:00
NE Time&Date: 01.01.1990 13:02:55 +00:00
USER NAME:
Brad_1i
COMMAND:
GET ETHCON:NAME=RACK:0/ETHCON:0;
SW RELEASE:
01-04-19-01-07-00_08-03-19
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
A50016-G5100-B333-04-7619
Id:0900d805805944ca
363
ETHCON
BS-4x / 82 II / 240 / 241 / 240XL commands
operationalState = ENABLED
proceduralStatus = NULL
relatedFuncObjects = Null
monitoringPort = none
END OF OUTPUT FOR JOB 1244
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Get ETHCON:NAME=RACK:0/ETHCON:0,REQATTL=ALS&AST&AVS&OST& PRS&
FWVER &RELFUNCOBJ& MONPRT;
LOCK ETHCON
LOCK ETHCON
NAME=RACK:0..7/ETHCON:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ETHCON h
LOCK ETHCON
Applicability:
Phase 2.
Visibility level: 1.
Command Description:
This command changes the administrative state of ETHCON board.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 18
PC Time&Date: 08.02.2008 13:13:04 +01:00
NE Time&Date: 01.01.1990 00:40:00 +00:00
364
USER NAME:
Brad_1i
COMMAND:
Unlock ETHCON:NAME=RACK:0/ETHCON:0;
Id:0900d805805944ca
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
SW RELEASE:
ETHCON
01-04-19-01-01-CR_08-02-08
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 18
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Lock ETHCON:NAME=RACK:0/ETHCON:0;
SET ETHCON
SET ETHCON
NAME=RACK:0..7/ETHCON:0..0 [,MONPRT=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ETHCON h
SET ETHCON
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command sets the attributes of ETHCON board to the BTSE data base.
Long Names:
NAME
Address of the managed object
MONPRT
monitoringPort
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
OB: 22
PC Time&Date: 08.02.2008 13:13:19 +01:00
NE Time&Date: 01.01.1990 00:40:15 +00:00
A50016-G5100-B333-04-7619
Id:0900d805805944ca
365
ETHCON
BS-4x / 82 II / 240 / 241 / 240XL commands
USER NAME:
Brad_1i
COMMAND:
Set ETHCON:NAME=RACK:0/ETHCON:0,MONPRT=port3;
SW RELEASE:
01-04-19-01-01-CR_08-02-08
COMMAND RESULT: Operation successful
monitoringPort = port3
END OF OUTPUT FOR JOB 22
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Set ETHCON:NAME=RACK:0/ETHCON:0,MONPRT=coba;
UNLOCK ETHCON
UNLOCK ETHCON
NAME=RACK:0..7/ETHCON:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h ETHCON h
UNLOCK ETHCON
Applicability:
Phase 2.
Visibility level: 1.
Command Description:
This command changes the administrative state of the ETHCON board.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 18
PC Time&Date: 08.02.2008 13:13:04 +01:00
NE Time&Date: 01.01.1990 00:40:00 +00:00
366
Id:0900d805805944ca
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ETHCON
USER NAME:
Brad_1i
COMMAND:
Unlock ETHCON:NAME=RACK:0/ETHCON:0;
SW RELEASE:
01-04-19-01-01-CR_08-02-08
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 18
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Unlock ETHCON:NAME=RACK:0/ETHCON:0;
A50016-G5100-B333-04-7619
Id:0900d805805944ca
367
ETHPORT
BS-4x / 82 II / 240 / 241 / 240XL commands
ETHPORT
The ETHPORT object is introduced to indicate the state of the Ethernet port and to allow
the configuration of port specific attributes. There is no ETHPORT instance for Ethernet
ports which are not externally visible (connection to COBA) nor used for monitoring.
The Ethernet port supports full duplex mode.
CREATE ETHPORT
CREATE ETHPORT
NAME=ETHPORT:0..3 [,EAUTONEG=] [,EFLWCTRL=]
,PUSG=;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h ETHPORT h CREATE
ETHPORT
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the ETHPORT to the BTSE data base.
Long Names:
NAME
Address of the managed object
EAUTONEG
enableAutoNegotiation
EFLWCTRL
enableFlowControl
PUSG
portUsage
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 39
PC Time&Date: 08.02.2008 13:20:45 +01:00
NE Time&Date: 01.01.1990 00:47:41 +00:00
USER NAME:
User_Pitt
COMMAND:
Create ETHPORT:NAME=ETHPORT:0;
SW RELEASE:
368
01-04-19-01-01-CR_08-02-08
Id:0900d805805944cc
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ETHPORT
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 39
Operation Failed
None.
Application Guidelines:
Default values apply for the typical Abis Ethernet configuration.
An ETHPORT object can be only created if the ETHCON object has been created
before. Physical ports of the Ethernet switch without related ETHPORT object (except
for the monitoring port(s)) are blocked.
Example of Command Execution:
Create ETHPORT:NAME=ETHPORT:0,EAUTONEG=TRUE,EFLWCTRL=FALSE,PUSG=bscLink;
DELETE ETHPORT
DELETE ETHPORT
NAME=ETHPORT:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h ETHPORT h DELETE
ETHPORT
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the ETHPORT from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of delete command
is the following:
JOB: 39
PC Time&Date: 30.05.2008 11:00:01 +02:00
A50016-G5100-B333-04-7619
Id:0900d805805944cc
369
ETHPORT
BS-4x / 82 II / 240 / 241 / 240XL commands
NE Time&Date: 01.01.1990 00:04:34 +00:00
USER NAME:
User_Pitt
COMMAND:
Delete ETHPORT:NAME=ETHPORT:0;
SW RELEASE:
01-04-19-01-01-ZS_08-05-29
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 39
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Delete ETHPORT:NAME=ETHPORT:0;
GET ETHPORT
GET ETHPORT
NAME=ETHPORT:0..3 [,REQATTL=ALS, AST, AVS, OST,
PRS, RELFUNCOBJ, EAUTONEG, EFLWCTRL, MTYP,
PSTAT, PUSG, SFPSERID];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h ETHPORT h GET
ETHPORT
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the ETHPORT.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
370
relatedFuncObjects
Id:0900d805805944cc
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ETHPORT
EAUTONEG
enableAutoNegotiation
EFLWCTRL
enableFlowControl
MTYP
mediaType
PSTAT
portStatus
PUSG
portUsage
SFPSERID
sfpSerialId
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 77
PC Time&Date: 18.04.2008 10:12:28 +02:00
NE Time&Date: 01.01.1990 00:07:58 +00:00
USER NAME:
User_Pitt
COMMAND:
Get ETHPORT:NAME=ETHPORT:0;
SW RELEASE:
01-04-19-01-07-01_08-04-03
COMMAND RESULT: Operation successful
alarmStatus = MAJOR
administrativeState = Unlocked
availabilityStatus = Degraded
operationalState = ENABLED
proceduralStatus = NULL
relatedFuncObjects = Null
enableAutoNegotiation = TRUE
enableFlowControl = FALSE
mediaType = electrical
portStatus = Null
portUsage = null
sfpSerialId = Null
END OF OUTPUT FOR JOB 77
Operation Failed
None.
A50016-G5100-B333-04-7619
Id:0900d805805944cc
371
ETHPORT
BS-4x / 82 II / 240 / 241 / 240XL commands
Application Guidelines:
None.
Example of Command Execution:
Get ETHPORT:NAME=ETHPORT:0,REQATTL=ALS&AST&AVS&OST&PRS&RELFUNCOBJ&EAUTONEG&EFLWCTRL&MTYP&PSTAT&PUSG&SPFSERID;
LOCK ETHPORT
LOCK ETHPORT
NAME=ETHPORT:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h ETHPORT h LOCK
ETHPORT
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of ETHPORT.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 49
PC Time&Date: 27.08.2008 14:16:31 +02:00
NE Time&Date: 27.08.2008 14:05:17 +01:00
USER NAME:
User_Pitt
COMMAND:
Lock ETHPORT:NAME=ETHPORT:0;
SW RELEASE:
01-04-19-01-11-ZT_08-08-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 49
Operation Failed
None.
372
Id:0900d805805944cc
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ETHPORT
Application Guidelines:
None.
Example of Command Execution:
Lock ETHPORT:NAME=ETHPORT:0;
SET ETHPORT
SET ETHPORT
NAME=ETHPORT:0..3 [,EAUTONEG=] [,EFLWCTRL=]
[,PUSG=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h ETHPORT h SET
ETHPORT
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command sets the attributes of ETHPORT to the BTSE data base.
Long Names:
NAME
Address of the managed object
EAUTONEG
enableAutoNegotiation
EFLWCTRL
enableFlowControl
PUSG
portUsage
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
JOB: 35
PC Time&Date: 30.05.2008 10:59:41 +02:00
NE Time&Date: 01.01.1990 00:04:14 +00:00
USER NAME:
User_Pitt
COMMAND:
Set ETHPORT:NAME=ETHPORT:0,PUSG=null;
SW RELEASE:
01-04-19-01-01-ZS_08-05-29
COMMAND RESULT: Operation successful
A50016-G5100-B333-04-7619
Id:0900d805805944cc
373
ETHPORT
BS-4x / 82 II / 240 / 241 / 240XL commands
portUsage = null
END OF OUTPUT FOR JOB 35
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Set ETHPORT:NAME=ETHPORT:0,EAUTONEG=TRUE,EFLWCTRL=FALSE,PUSG=null;
UNLOCK ETHPORT
UNLOCK ETHPORT
NAME=ETHPORT:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h ETHPORT h UNLOCK
ETHPORT
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of ETHPORT.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 52
PC Time&Date: 27.08.2008 14:16:56 +02:00
NE Time&Date: 27.08.2008 14:05:42 +01:00
USER NAME:
User_Pitt
COMMAND:
Unlock ETHPORT:NAME=ETHPORT:0;
SW RELEASE:
01-04-19-01-11-ZT_08-08-23
COMMAND RESULT: Operation successful
374
Id:0900d805805944cc
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ETHPORT
administrativeState = Unlocked
END OF OUTPUT FOR JOB 52
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Unlock ETHPORT:NAME=ETHPORT:0;
A50016-G5100-B333-04-7619
Id:0900d805805944cc
375
F6DCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
F6DCTMA
This object represents the TMA power supply of one antenna port. The functionality of
the object is identical to the DUDCTMA object of an MFDUAMCO.
CREATE F6DCTMA
CREATE F6DCTMA
NAME=RACK:0..7/F6DCTMA:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6DCTMA h
CREATE F6DCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the F6DCTMA to the BTSE data base. The creation of the
F6DCTMA object implicitly switches on the TMA power supply. The power supply may
be also switched on via DIP switch.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of create
command is the following:
JOB: 288
PC Time&Date: 17.10.2008 09:24:24 +02:00
NE Time&Date: 01.01.1990 19:05:33 +00:00
USER NAME:
User_NSN
COMMAND:
Create F6DCTMA:NAME=RACK:0/F6DCTMA:0;
SW RELEASE:
01-04-19-01-11-07_08-10-16
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 288
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
376
Id:0900d8058059598c
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6DCTMA
JOB: 34
PC Time&Date: 25.09.2008 14:46:58 +02:00
NE Time&Date: 02.01.1990 00:03:39 +00:00
USER NAME:
User_NSN
COMMAND:
Create F6DCTMA:NAME=RACK:0/F6DCTMA:0;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation failed
Creation out of sequence (-162)
END OF OUTPUT FOR JOB 34
Application Guidelines:
None.
Example of Command Execution:
Create F6DCTMA:NAME=RACK:0/F6DCTMA:0;
DELETE F6DCTMA
DELETE F6DCTMA
NAME=RACK:0..7/F6DCTMA:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6DCTMA h
DELETE F6DCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the F6DCTMA from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
A50016-G5100-B333-04-7619
Id:0900d8058059598c
377
F6DCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 59
PC Time&Date: 17.10.2008 09:05:13 +02:00
NE Time&Date: 01.01.1990 18:46:22 +00:00
USER NAME:
User_NSN
COMMAND:
Delete F6DCTMA:NAME=RACK:0/F6DCTMA:0;
SW RELEASE:
01-04-19-01-11-07_08-10-16
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 59
Operation Failed
The specified Object has not been deleted. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 137
PC Time&Date: 24.09.2008 15:06:31 +02:00
NE Time&Date: 01.01.1990 00:23:14 +00:00
USER NAME:
User_NSN
COMMAND:
Delete F6DCTMA:NAME=RACK:0/F6DCTMA:0;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation failed
MO or MOT not locked (-151)
END OF OUTPUT FOR JOB 137
Application Guidelines:
None.
Example of Command Execution:
Delete F6DCTMA:NAME=RACK:0/F6DCTMA:0;
378
Id:0900d8058059598c
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6DCTMA
GET F6DCTMA
GET F6DCTMA
NAME=RACK:0..7/F6DCTMA:0..3 [,REQATTL=ALS, AST,
AVS, OST, PRS, RELFUNCOBJ];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6DCTMA h
GET F6DCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the F6DCTMA.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 140
PC Time&Date: 16.09.2008 15:59:02 +02:00
NE Time&Date: 01.01.1990 00:19:44 +00:00
USER NAME:
User_NSN
COMMAND:
Get F6DCTMA:NAME=RACK:0/F6DCTMA:0;
SW RELEASE:
01-04-19-01-12-MB_08-09-16
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
A50016-G5100-B333-04-7619
Id:0900d8058059598c
379
F6DCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
availabilityStatus = NotInstalled
operationalState = DISABLED
proceduralStatus = NULL
relatedFuncObjects = Null
END OF OUTPUT FOR JOB 140
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Get F6DCTMA:NAME=RACK:0/F6DCTMA:0,
REQATTL=ALS&AST&AVS&OST&PRS&&RELFUNCOBJ;
GETTEST F6DCTMA
GETTEST F6DCTMA
NAME=RACK:0..7/F6DCTMA:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6DCTMA h
GETTEST F6DCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the object test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 173
PC Time&Date: 28.10.2008 16:31:01 +01:00
NE Time&Date: 01.01.1990 00:21:30 +00:00
USER NAME:
380
User_NSN
Id:0900d8058059598c
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
COMMAND:
F6DCTMA
Gettest F6DCTMA:NAME=RACK:0/F6DCTMA:0;
SW RELEASE:
01-04-19-01-11-08_08-10-17
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 173
Operation Failed
The specified action cannot be performed. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 48
PC Time&Date: 17.10.2008 09:04:29 +02:00
NE Time&Date: 01.01.1990 18:45:38 +00:00
USER NAME:
User_NSN
COMMAND:
Gettest F6DCTMA:NAME=RACK:0/F6DCTMA:0;
SW RELEASE:
01-04-19-01-11-07_08-10-16
COMMAND RESULT: Operation failed
MOT = RACK:0/F6DCTMA:0
Object instance unknown or not allowed (-9)
END OF OUTPUT FOR JOB 48
Application Guidelines:
None.
Example of Command Execution:
Gettest F6DCTMA:NAME=RACK:0/F6DCTMA:0;
LOCK F6DCTMA
LOCK F6DCTMA
NAME=RACK:0..7/F6DCTMA:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6DCTMA h
LOCK F6DCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
A50016-G5100-B333-04-7619
Id:0900d8058059598c
381
F6DCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Description:
This command changes the administrative state of F6DCTMA.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 40
PC Time&Date: 17.10.2008 09:04:19 +02:00
NE Time&Date: 01.01.1990 18:45:28 +00:00
USER NAME:
User_NSN
COMMAND:
Lock F6DCTMA:NAME=RACK:0/F6DCTMA:0;
SW RELEASE:
01-04-19-01-11-07_08-10-16
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 40
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Lock F6DCTMA:NAME=RACK:0/F6DCTMA:1;
PERFTEST F6DCTMA
PERFTEST F6DCTMA
NAME=RACK:0..7/F6DCTMA:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6DCTMA h
PERFTEST F6DCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
382
Id:0900d8058059598c
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6DCTMA
Command Description:
This command is used to start an asynchronous test in the object.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. An example is
the following:
JOB: 43
PC Time&Date: 17.10.2008 09:04:27 +02:00
NE Time&Date: 01.01.1990 18:45:36 +00:00
USER NAME:
User_NSN
COMMAND:
Perftest F6DCTMA:NAME=RACK:0/F6DCTMA:0;
SW RELEASE:
01-04-19-01-11-07_08-10-16
COMMAND RESULT: Operation successful
MOT = RACK:0/F6DCTMA:0
tO = BTSETEST:1
END OF OUTPUT FOR JOB 43
Operation Failed
The specified test cannot be performed. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 140
PC Time&Date: 24.09.2008 15:06:41 +02:00
NE Time&Date: 01.01.1990 00:23:24 +00:00
USER NAME:
User_NSN
COMMAND:
Perftest F6DCTMA:NAME=RACK:0/F6DCTMA:0;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation failed
A50016-G5100-B333-04-7619
Id:0900d8058059598c
383
F6DCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
MOT = RACK:0/F6DCTMA:0
Physical configuration cannot be performed (-30)
END OF OUTPUT FOR JOB 140
Application Guidelines:
None.
Example of Command Execution:
Perftest F6DCTMA:NAME=RACK:0/F6DCTMA:0;
STOPTEST F6DCTMA
STOPTEST F6DCTMA
NAME=RACK:0..7/F6DCTMA:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6DCTMA h
STOPTEST F6DCTMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
...
.
384
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
Id:0900d8058059598c
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6DCTMA
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
phaseId =
Operation Failed
The specified test cannot be stopped. In addition to the general NACK causes, a specific
NACK cause, which indicates that the command is inconsistent with the physical configuration, is possible. An example is the following:
JOB: 55
PC Time&Date: 17.10.2008 09:04:59 +02:00
NE Time&Date: 01.01.1990 18:46:08 +00:00
USER NAME:
User_NSN
COMMAND:
Stoptest F6DCTMA:NAME=RACK:0/F6DCTMA:0;
SW RELEASE:
01-04-19-01-11-07_08-10-16
COMMAND RESULT: Operation failed
MOT = RACK:0/F6DCTMA:0
Object instance unknown or not allowed (-9)
END OF OUTPUT FOR JOB 55
Application Guidelines:
None.
Example of Command Execution:
Stoptest F6DCTMA:NAME=RACK:0/F6DCTMA:0;
UNLOCK F6DCTMA
UNLOCK F6DCTMA
NAME=RACK:0..7/F6DCTMA:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6DCTMA h
UNLOCK F6DCTMA
A50016-G5100-B333-04-7619
Id:0900d8058059598c
385
F6DCTMA
BS-4x / 82 II / 240 / 241 / 240XL commands
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of F6DCTMA.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 56
PC Time&Date: 17.10.2008 09:05:06 +02:00
NE Time&Date: 01.01.1990 18:46:15 +00:00
USER NAME:
User_NSN
COMMAND:
Unlock F6DCTMA:NAME=RACK:0/F6DCTMA:0;
SW RELEASE:
01-04-19-01-11-07_08-10-16
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 56
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Unlock F6DCTMA:NAME=RACK:0/F6DCTMA:0;
386
Id:0900d8058059598c
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6LNA
F6LNA
The F6LNA object integrates hw functionality both of DILNA and DULNA objects.
CREATE F6LNA
CREATE F6LNA
NAME=RACK:0..7/F6LNA:0..3 ,CELLNO= [,SCELLNO=]
[,GNADB=] [,LNAPRED=] ,WDLNA= [,LNAMDB=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h
CREATE F6LNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the F6LNA to the BTSE data base.
Long Names:
NAME
Address of the managed object
CELLNO
cellNumber
SCELLNO
secondCellNumber
GNADB
gainAdjustDb
LNAPRED
lnaPredecessor
WDLNA
wiringDataLna
LNAMDB
lnaModeDb
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of create
command is the following:
JOB: 71
PC Time&Date: 26.09.2008 13:12:42 +02:00
NE Time&Date: 26.09.2008 10:20:00 +01:00
USER NAME:
User_NSN
COMMAND:
Create
F6LNA:NAME=RACK:0/F6LNA:1,CELLNO=1,WDLNA=FCUMAIN1N;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation successful
A50016-G5100-B333-04-7619
Id:0900d8058059598e
387
F6LNA
BS-4x / 82 II / 240 / 241 / 240XL commands
cellNumber = 1
wiringDataLna = FCUMAIN1N
END OF OUTPUT FOR JOB 71
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 9
PC Time&Date: 25.09.2008 14:46:05 +02:00
NE Time&Date: 02.01.1990 00:02:46 +00:00
USER NAME:
User_NSN
COMMAND:
Create
F6LNA:NAME=RACK:0/F6LNA:1,CELLNO=0,GNADB=N_00,LNAPRED=TMA(RACK
0-TMA1),WDLNA=CU0D;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation failed
cellNumber = 0
gainAdjustDb = N_00
lnaPredecessor =
predType =
TMA
predRack = RACK0
predNo = TMA1
wiringDataLna = CU0D
message cannot be performed (-17)
END OF OUTPUT FOR JOB 9
Application Guidelines:
F6LNA creation attempts with more than 6 wiring paths specified in wiringDataLna
attribute are rejected by BTS SW.
388
Id:0900d8058059598e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6LNA
Example of Command Execution:
Create F6LNA:NAME=RACK:0/F6LNA:1,CELLNO=1,WDLNA=FCUMAIN1N
DELETE F6LNA
DELETE F6LNA
NAME=RACK:0..7/F6LNA:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h
DELETE F6LNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the F6LNA from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 29
PC Time&Date: 25.09.2008 14:46:53 +02:00
NE Time&Date: 02.01.1990 00:03:34 +00:00
USER NAME:
User_NSN
COMMAND:
Delete F6LNA:NAME=RACK:0/F6LNA:0;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 29
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible. An example is the following:
A50016-G5100-B333-04-7619
Id:0900d8058059598e
389
F6LNA
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 12
PC Time&Date: 25.09.2008 14:46:19 +02:00
NE Time&Date: 02.01.1990 00:03:00 +00:00
USER NAME:
User_NSN
COMMAND:
Delete F6LNA:NAME=RACK:0/F6LNA:0;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation failed
MO or MOT not locked (-151)
END OF OUTPUT FOR JOB 12
Application Guidelines:
None.
Example of Command Execution:
Delete F6LNA:NAME=RACK:0/F6LNA:0;
GET F6LNA
GET F6LNA
NAME=RACK:0..7/F6LNA:0..3 [,REQATTL=ALS, AST,
OST, PRS, AVS, CELLNO, SCELLNO, GNA, GNADB,
LNAPRED, WDLNA, LNAMDB, LNAMODE, RELFUNCOBJ];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h
GET F6LNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the F6LNA.
Long Names:
390
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
OST
operationalState
Id:0900d8058059598e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6LNA
PRS
proceduralStatus
AVS
availabilityStatus
CELLNO
cellNumber
SCELLNO
secondCellNumber
GNA
gainAdjust(dB)
GNADB
gainAdjustDb
LNAPRED
lnaPredecessor
WDLNA
wiringDataLna
LNAMDB
lnaModeDb
LNAMODE
lnaMode
RELFUNCOBJ
relatedFuncObjects
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 60
PC Time&Date: 17.10.2008 09:05:21 +02:00
NE Time&Date: 01.01.1990 18:46:30 +00:00
USER NAME:
User_NSN
COMMAND:
Get F6LNA:NAME=RACK:0/F6LNA:0;
SW RELEASE:
01-04-19-01-11-07_08-10-16
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
operationalState = ENABLED
proceduralStatus = NULL
availabilityStatus = NULL
cellNumber = 0
secondCellNumber = NotUsed
gainAdjust(dB) = N_00
gainAdjustDb = DIP
lnaPredecessor = Null
wiringDataLna = CU0N & CU1N & CU2N & CU3N
lnaModeDb = DIP
A50016-G5100-B333-04-7619
Id:0900d8058059598e
391
F6LNA
BS-4x / 82 II / 240 / 241 / 240XL commands
lnaMode = AMCO_MODE
relatedFuncObjects = Null
END OF OUTPUT FOR JOB 60
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Get F6LNA:NAME=RACK:0/F6LNA:0;REQATTL= ALS& AST& OST& PRS& AVS&
CELLNO& SCELLNO& GNA& GNADB&LNAPRED& WDLNA& LNAMDB&
LNAMODE& RELFUNCOBJ;
GETTEST F6LNA
GETTEST F6LNA
NAME=RACK:0..7/F6LNA:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h
GETTEST F6LNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the object test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 273
PC Time&Date: 17.10.2008 09:21:19 +02:00
NE Time&Date: 01.01.1990 19:02:28 +00:00
392
USER NAME:
User_NSN
COMMAND:
Gettest F6LNA:NAME=RACK:0/F6LNA:1;
Id:0900d8058059598e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
SW RELEASE:
F6LNA
01-04-19-01-11-07_08-10-16
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 273
Operation Failed
The GETTEST command has not been successfully executed. A general NACK will
indicate possible errors or a specific NACK strictly related to the single command is possible. An example of specific NACK is the following:
JOB: 69
PC Time&Date: 17.10.2008 09:05:40 +02:00
NE Time&Date: 01.01.1990 18:46:49 +00:00
USER NAME:
User_NSN
COMMAND:
Gettest F6LNA:NAME=RACK:0/F6LNA:0;
SW RELEASE:
01-04-19-01-11-07_08-10-16
COMMAND RESULT: Operation failed
MOT = RACK:0/F6LNA:0
Object instance unknown or not allowed (-9)
END OF OUTPUT FOR JOB 69
Application Guidelines:
None.
Example of Command Execution:
Gettest F6LNA:NAME=RACK:0/F6LNA:0;
LOCK F6LNA
LOCK F6LNA
NAME=RACK:0..7/F6LNA:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h
LOCK F6LNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
A50016-G5100-B333-04-7619
Id:0900d8058059598e
393
F6LNA
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Description:
This command changes the administrative state of F6LNA.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of lock
command is the following:
JOB: 113
PC Time&Date: 28.10.2008 16:26:55 +01:00
NE Time&Date: 01.01.1990 00:17:24 +00:00
USER NAME:
User_NSN
COMMAND:
Lock F6LNA:NAME=RACK:0/F6LNA:0;
SW RELEASE:
01-04-19-01-11-08_08-10-17
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 113
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Lock F6LNA:NAME=RACK:0/F6LNA:0
PERFTEST F6LNA
PERFTEST F6LNA
NAME=RACK:0..7/F6LNA:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h
PERFTEST F6LNA
394
Id:0900d8058059598e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6LNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in the object.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of perftest
command is the following:
JOB: 13
PC Time&Date: 26.09.2008 13:05:27 +02:00
NE Time&Date: 26.09.2008 10:12:45 +01:00
USER NAME:
User_NSN
COMMAND:
Perftest F6LNA:NAME=RACK:0/F6LNA:0;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation successful
MOT = RACK:0/F6LNA:0
tO = BTSETEST:7
END OF OUTPUT FOR JOB 13
Operation Failed
The specified test cannot be performed. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 145
PC Time&Date: 16.09.2008 16:01:13 +02:00
NE Time&Date: 01.01.1990 00:21:55 +00:00
USER NAME:
A50016-G5100-B333-04-7619
User_NSN
Id:0900d8058059598e
395
F6LNA
BS-4x / 82 II / 240 / 241 / 240XL commands
COMMAND:
Perftest F6LNA:NAME=RACK:0/F6LNA:0;
SW RELEASE:
01-04-19-01-12-MB_08-09-16
COMMAND RESULT: Operation failed
MOT = RACK:0/F6LNA:0
MO or MOT not locked (-151)
END OF OUTPUT FOR JOB 145
Application Guidelines:
None.
Example of Command Execution:
Perftest F6LNA:NAME=RACK:0/F6LNA:0;
SET F6LNA
SET F6LNA
NAME=RACK:0..7/F6LNA:0..3 [,SCELLNO=] [,GNADB=]
[,WDLNA=] [,LNAMDB=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h
SET F6LNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command sets the attributes of F6LNA.
Long Names:
NAME
Address of the managed object
SCELLNO
secondCellNumber
GNADB
gainAdjustDb
WDLNA
wiringDataLna
LNAMDB
lnaModeDb
System Responses:
Operation Completed
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
JOB: 219
396
Id:0900d8058059598e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6LNA
PC Time&Date: 24.09.2008 14:37:37 +02:00
NE Time&Date: 24.09.2008 10:46:11 +00:00
USER NAME:
User_NSN
COMMAND:
Set F6LNA:NAME=RACK:0/F6LNA:0,GNADB=N_00;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation successful
gainAdjustDb = N_00
END OF OUTPUT FOR JOB 219
Operation Failed
The specified Object has not been set. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 216
PC Time&Date: 24.09.2008 14:37:13 +02:00
NE Time&Date: 24.09.2008 10:45:47 +00:00
USER NAME:
User_NSN
COMMAND:
Set
F6LNA:NAME=RACK:0/F6LNA:0,GNADB=N_11,LNAMDB=AMCO_MODE,SCELLNO
=N_00,WDLNA=CU0D&CU1D;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation failed
secondCellNumber = N_00
gainAdjustDb = N_11
wiringDataLna = CU0D & CU1D
lnaModeDb = AMCO_MODE
message cannot be performed (-17)
END OF OUTPUT FOR JOB 216
A50016-G5100-B333-04-7619
Id:0900d8058059598e
397
F6LNA
BS-4x / 82 II / 240 / 241 / 240XL commands
Application Guidelines:
None.
Example of Command Execution:
Set F6LNA:NAME=RACK:0/F6LNA:0,GNADB=N_00;
STOPTEST F6LNA
STOPTEST F6LNA
NAME=RACK:0..7/F6LNA:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h
STOPTEST F6LNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
...
.
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
398
Id:0900d8058059598e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6LNA
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
phaseId =
Operation Failed
The specified test cannot be stopped. In addition to the general NACK causes, a specific
NACK cause, which indicates that the command is inconsistent with the physical configuration, is possible. An example is the following:
JOB: 274
PC Time&Date: 17.10.2008 09:21:25 +02:00
NE Time&Date: 01.01.1990 19:02:34 +00:00
USER NAME:
User_NSN
COMMAND:
Stoptest F6LNA:NAME=RACK:0/F6LNA:1;
SW RELEASE:
01-04-19-01-11-07_08-10-16
COMMAND RESULT: Operation failed
MOT = RACK:0/F6LNA:1
Object instance unknown or not allowed (-9)
END OF OUTPUT FOR JOB 274
Application Guidelines:
None.
Example of Command Execution:
Stoptest F6LNA:NAME=RACK:0/F6LNA:1;
UNLOCK F6LNA
UNLOCK F6LNA
NAME=RACK:0..7/F6LNA:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6LNA h
UNLOCK F6LNA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of F6LNA.
A50016-G5100-B333-04-7619
Id:0900d8058059598e
399
F6LNA
BS-4x / 82 II / 240 / 241 / 240XL commands
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of unlock
command is the following:
JOB: 18
PC Time&Date: 26.09.2008 13:06:03 +02:00
NE Time&Date: 26.09.2008 10:13:21 +01:00
USER NAME:
User_NSN
COMMAND:
Unlock F6LNA:NAME=RACK:0/F6LNA:0;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 18
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Unlock F6LNA:NAME=RACK:0/F6LNA:0;
400
Id:0900d8058059598e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6TNFP
F6TNFP
The object provides functionality to configure and supervise the turnable narrowband
filter of one TX path.
CREATE F6TNFP
CREATE F6TNFP
NAME=RACK:0..7/F6TNFP:0..11 ,WDFTNFP=;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6TNFP h
CREATE F6TNFP
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the F6TNFP to the BTSE data base.
Long Names:
NAME
Address of the managed object
WDFTNFP
wiringDataFtnfp
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of create
command is the following:
JOB: 201
PC Time&Date: 17.10.2008 09:13:37 +02:00
NE Time&Date: 01.01.1990 18:54:46 +00:00
USER NAME:
User_q
COMMAND:
FVSWRP0;
Create F6TNFP:NAME=RACK:0/F6TNFP:0,WDFTNFP=CU0-
SW RELEASE:
01-04-19-01-11-07_08-10-16
COMMAND RESULT: Operation successful
wiringDataFtnfp =
CUWiring = CU0
FVSWRPWiring = FVSWRP0
A50016-G5100-B333-04-7619
Id:0900d80580595990
401
F6TNFP
BS-4x / 82 II / 240 / 241 / 240XL commands
END OF OUTPUT FOR JOB 201
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 322
PC Time&Date: 17.09.2008 16:20:44 +02:00
NE Time&Date: 17.09.2008 13:29:17 +01:00
USER NAME:
User_q
COMMAND:
FVSWRP1;
Create F6TNFP:NAME=RACK:0/F6TNFP:0,WDFTNFP=CU2-
SW RELEASE:
01-04-19-01-12-MB_08-09-12
COMMAND RESULT: Operation failed
wiringDataFtnfp =
CUWiring = CU2
FVSWRPWiring = FVSWRP1
message cannot be performed (-17)
END OF OUTPUT FOR JOB 322
Application Guidelines:
The creation is rejected as long as the related F6VSWRP object does not exist in the
database.
Example of Command Execution:
Create F6TNFP:NAME=RACK:0/F6TNFP:0,WDFTNFP=CU0-FVSWRP0;
DELETE F6TNFP
DELETE F6TNFP
NAME=RACK:0..7/F6TNFP:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6TNFP h
DELETE F6TNFP
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
402
Id:0900d80580595990
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6TNFP
Command Description:
This command deletes the F6TNFP from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 90
PC Time&Date: 17.10.2008 09:07:57 +02:00
NE Time&Date: 01.01.1990 18:49:06 +00:00
USER NAME:
User_q
COMMAND:
Delete F6TNFP:NAME=RACK:0/F6TNFP:0;
SW RELEASE:
01-04-19-01-11-07_08-10-16
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 90
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Delete F6TNFP:NAME=RACK:0/F6TNFP:0;
GET F6TNFP
GET F6TNFP
NAME=RACK:0..7/F6TNFP:0..11 [,REQATTL=ALS, AST,
AVS, OST, PRS, RELFUNCOBJ, TNFTARGF, WDFTNFP];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6TNFP h
GET F6TNFP
Applicability:
Phase 2 and Phase 3.
A50016-G5100-B333-04-7619
Id:0900d80580595990
403
F6TNFP
BS-4x / 82 II / 240 / 241 / 240XL commands
Visibility level: 0.
Command Description:
This command displays the attributes of the F6TNFP.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
TNFTARGF
tnfTargetFrequency
WDFTNFP
wiringDataFtnfp
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 88
PC Time&Date: 17.10.2008 09:07:54 +02:00
NE Time&Date: 01.01.1990 18:49:03 +00:00
USER NAME:
User_q
COMMAND:
Get F6TNFP:NAME=RACK:0/F6TNFP:0;
SW RELEASE:
01-04-19-01-11-07_08-10-16
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Locked
availabilityStatus = Dependency
operationalState = DISABLED
proceduralStatus = NULL
relatedFuncObjects = Null
tnfTargetFrequency = Null
wiringDataFtnfp =
404
Id:0900d80580595990
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6TNFP
CUWiring = CU0
FVSWRPWiring = FVSWRP0
END OF OUTPUT FOR JOB 88
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Get F6TNFP:NAME=RACK:0/F6TNFP:0;
GETTEST F6TNFP
GETTEST F6TNFP
NAME=RACK:0..7/F6TNFP:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6TNFP h
GETTEST F6TNFP
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the object test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 90
PC Time&Date: 29.10.2008 16:24:05 +01:00
NE Time&Date: 01.01.1990 00:14:34 +00:00
USER NAME:
User_q
COMMAND:
Gettest F6TNFP:NAME=RACK:0/F6TNFP:0;
A50016-G5100-B333-04-7619
Id:0900d80580595990
405
F6TNFP
BS-4x / 82 II / 240 / 241 / 240XL commands
SW RELEASE:
01-04-19-01-11-08_08-10-17
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 90
Operation Failed
The gettest command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible. An
example is the following:
JOB: 85
PC Time&Date: 28.10.2008 16:24:05 +01:00
NE Time&Date: 01.01.1990 00:14:34 +00:00
USER NAME:
User_q
COMMAND:
Gettest F6TNFP:NAME=RACK:0/F6TNFP:0;
SW RELEASE:
01-04-19-01-11-08_08-10-17
COMMAND RESULT: Operation failed
MOT = RACK:0/F6TNFP:0
Object instance unknown or not allowed (-9)
END OF OUTPUT FOR JOB 85
Application Guidelines:
None.
Example of Command Execution:
Gettest F6TNFP:NAME=RACK:0/F6TNFP:0;
LOCK F6TNFP
LOCK F6TNFP
NAME=RACK:0..7/F6TNFP:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6TNFP h
LOCK F6TNFP
Applicability:
Phase 2 and Phase 3.
406
Id:0900d80580595990
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6TNFP
Visibility level: 1.
Command Description:
This command changes the administrative state of F6TNFP.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 153
PC Time&Date: 24.09.2008 15:14:50 +02:00
NE Time&Date: 01.01.1990 00:31:33 +00:00
USER NAME:
User_q
COMMAND:
Lock F6TNFP:NAME=RACK:0/F6TNFP:1;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 153
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Lock F6TNFP:NAME=RACK:0/F6TNFP:1;
PERFTEST F6TNFP
PERFTEST F6TNFP
NAME=RACK:0..7/F6TNFP:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6TNFP h
PERFTEST F6TNFP
Applicability:
Phase 2 and Phase 3.
A50016-G5100-B333-04-7619
Id:0900d80580595990
407
F6TNFP
BS-4x / 82 II / 240 / 241 / 240XL commands
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in the object.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started.
JOB: 23
PC Time&Date: 26.09.2008 13:06:13 +02:00
NE Time&Date: 26.09.2008 10:13:31 +01:00
USER NAME:
User_q
COMMAND:
Perftest F6TNFP:NAME=RACK:0/F6TNFP:0;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation successful
MOT = RACK:0/F6TNFP:0
tO = BTSETEST:8
END OF OUTPUT FOR JOB 23
Operation Failed
The specified test cannot be performed. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 89
PC Time&Date: 24.09.2008 14:21:15 +02:00
NE Time&Date: 24.09.2008 10:29:49 +00:00
USER NAME:
User_q
COMMAND:
Perftest F6TNFP:NAME=RACK:0/F6TNFP:1;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation failed
408
Id:0900d80580595990
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6TNFP
MOT = RACK:0/F6TNFP:1
MO or MOT not locked (-151)
END OF OUTPUT FOR JOB 89
Application Guidelines:
None.
Example of Command Execution:
Perftest F6TNFP:NAME=RACK:0/F6TNFP:0;
STOPTEST F6TNFP
STOPTEST F6TNFP
NAME=RACK:0..7/F6TNFP:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6TNFP h
STOPTEST F6TNFP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
...
.
A50016-G5100-B333-04-7619
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
Id:0900d80580595990
409
F6TNFP
BS-4x / 82 II / 240 / 241 / 240XL commands
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
phaseId =
Operation Failed
The specified test has not been stopped. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 214
PC Time&Date: 17.10.2008 09:14:33 +02:00
NE Time&Date: 01.01.1990 18:55:42 +00:00
USER NAME:
User_q
COMMAND:
Stoptest F6TNFP:NAME=RACK:0/F6TNFP:0;
SW RELEASE:
01-04-19-01-11-07_08-10-16
COMMAND RESULT: Operation failed
MOT = RACK:0/F6TNFP:0
Object instance unknown or not allowed (-9)
END OF OUTPUT FOR JOB 214
Application Guidelines:
None.
Example of Command Execution:
Stoptest F6TNFP:NAME=RACK:0/F6TNFP:0;
UNLOCK F6TNFP
UNLOCK F6TNFP
NAME=RACK:0..7/F6TNFP:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6TNFP h
UNLOCK F6TNFP
410
Id:0900d80580595990
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6TNFP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of F6TNFP.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 93
PC Time&Date: 24.09.2008 14:21:38 +02:00
NE Time&Date: 24.09.2008 10:30:12 +00:00
USER NAME:
User_q
COMMAND:
Unlock F6TNFP:NAME=RACK:0/F6TNFP:0;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 93
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Unlock F6TNFP:NAME=RACK:0/F6TNFP:0;
A50016-G5100-B333-04-7619
Id:0900d80580595990
411
F6VSWRP
BS-4x / 82 II / 240 / 241 / 240XL commands
F6VSWRP
The F6VSWRP object represents common functions of one FICOM6. The objects
creation is therefore mandatory if the module is equipped.
CREATE F6VSWRP
CREATE F6VSWRP
NAME=RACK:0..7/F6VSWRP:0..1 ,CELLNO=
[,VSWRTDB=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h
CREATE F6VSWRP
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the F6VSWRP to the BTSE data base.
Long Names:
NAME
Address of the managed object
CELLNO
cellNumber
VSWRTDB
vswrThresholdDb
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of create
command is the following:
JOB: 36
PC Time&Date: 25.09.2008 14:47:06 +02:00
NE Time&Date: 02.01.1990 00:03:47 +00:00
USER NAME:
User_s
COMMAND:
Create
F6VSWRP:NAME=RACK:0/F6VSWRP:0,CELLNO=0,VSWRTDB=LOW_2_5_HIGH_3
_5;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation successful
cellNumber = 0
412
Id:0900d80580595992
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6VSWRP
vswrThresholdDb = LOW_2_5_HIGH_3_5
END OF OUTPUT FOR JOB 36
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 85
PC Time&Date: 16.09.2008 15:48:10 +02:00
NE Time&Date: 01.01.1990 00:08:52 +00:00
USER NAME:
User_s
COMMAND:
Create F6VSWRP:NAME=RACK:0/F6VSWRP:0,CELLNO=1;
SW RELEASE:
01-04-19-01-12-MB_08-09-16
COMMAND RESULT: Operation failed
cellNumber = 1
message cannot be performed (-17)
END OF OUTPUT FOR JOB 85
Application Guidelines:
The creation is mandatory if the module is equipped
The creation is rejected if any other combiner instance (DUAMCO, DUVSWR,
DULNA, DUDCTMA, FVSWRP, FTNFP, BCOM) is already created for the related
ACOM slots
The creation of any other combiner object has to be rejected if a FICOM6 object is
created for the slot(s)
Example of Command Execution:
Create
F6VSWRP:NAME=RACK:0/F6VSWRP:0,CELLNO=0,VSWRTDB=LOW_2_5_HIGH_3
_5;
DELETE F6VSWRP
DELETE F6VSWRP
NAME=RACK:0..7/F6VSWRP:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h
DELETE F6VSWRP
A50016-G5100-B333-04-7619
Id:0900d80580595992
413
F6VSWRP
BS-4x / 82 II / 240 / 241 / 240XL commands
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the F6VSWRP from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of create
command is the following:
JOB: 25
PC Time&Date: 25.09.2008 14:46:50 +02:00
NE Time&Date: 02.01.1990 00:03:31 +00:00
USER NAME:
User_s
COMMAND:
Delete F6VSWRP:NAME=RACK:0/F6VSWRP:0;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 25
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 26
PC Time&Date: 25.09.2008 14:46:50 +02:00
NE Time&Date: 02.01.1990 00:03:31 +00:00
USER NAME:
User_s
COMMAND:
Delete F6VSWRP:NAME=RACK:0/F6VSWRP:0;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation failed
414
Id:0900d80580595992
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6VSWRP
Deletion out of sequence (-166)
END OF OUTPUT FOR JOB 26
Application Guidelines:
The deletion of the F6VSWRP object has to be rejected as long as another FICOM6
object (F6TNFP, F6LNA, F6DCTMA) exists for the same ACOM slots.
Example of Command Execution:
Delete F6VSWRP:NAME=RACK:0/F6VSWRP:0;
GET F6VSWRP
GET F6VSWRP
NAME=RACK:0..7/F6VSWRP:0..1 [,REQATTL=ALS, AST,
AVS, CELLNO, OST, PRS, RELFUNCOBJ, VSWRTDB,
F6FWID];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h
GET F6VSWRP
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the F6VSWRP.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
CELLNO
cellNumber
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
VSWRTDB
vswrThresholdDb
F6FWID
ficom6FwId
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
A50016-G5100-B333-04-7619
Id:0900d80580595992
415
F6VSWRP
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 148
PC Time&Date: 16.09.2008 16:06:01 +02:00
NE Time&Date: 01.01.1990 00:26:43 +00:00
USER NAME:
User_s
COMMAND:
Get F6VSWRP:NAME=RACK:0/F6VSWRP:0;
SW RELEASE:
01-04-19-01-12-MB_08-09-16
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NotInstalled
cellNumber = 1
operationalState = DISABLED
proceduralStatus = NULL
relatedFuncObjects = Null
vswrThresholdDb = LOW_2_0_HIGH_3_0
ficom6FwId = "BFFCiihh.SWI:00-hh-19-ii-ss-00_08-01-01"
END OF OUTPUT FOR JOB 148
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Get F6VSWRP:NAME=F6VSWRP:0, REQATTL=ALS& AST& AVS& CELLNO& OST&
PRS& RELFUNCOBJ& VSWRTDB& F6FWID;
GETTEST F6VSWRP
GETTEST F6VSWRP
NAME=RACK:0..7/F6VSWRP:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h
GETTEST F6VSWRP
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
416
Id:0900d80580595992
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6VSWRP
Command Description:
This command displays the attributes of the object test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 296
PC Time&Date: 17.09.2008 16:12:51 +02:00
NE Time&Date: 17.09.2008 13:21:24 +01:00
USER NAME:
User_s
COMMAND:
Gettest F6VSWRP:NAME=RACK:0/F6VSWRP:1;
SW RELEASE:
01-04-19-01-12-MB_08-09-12
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 296
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Gettest F6VSWRP:NAME=RACK:0/F6VSWRP:0;
LOCK F6VSWRP
LOCK F6VSWRP
NAME=RACK:0..7/F6VSWRP:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h
LOCK F6VSWRP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
A50016-G5100-B333-04-7619
Id:0900d80580595992
417
F6VSWRP
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Description:
This command changes the administrative state of F6VSWRP.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 228
PC Time&Date: 17.09.2008 16:03:11 +02:00
NE Time&Date: 17.09.2008 13:11:44 +01:00
USER NAME:
User_s
COMMAND:
Lock F6VSWRP:NAME=RACK:0/F6VSWRP:0;
SW RELEASE:
01-04-19-01-12-MB_08-09-12
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 228
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Lock F6VSWRP:NAME=RACK:0/F6VSWRP:0;
PERFTEST F6VSWRP
PERFTEST F6VSWRP
NAME=RACK:0..7/F6VSWRP:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h
PERFTEST F6VSWRP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
418
Id:0900d80580595992
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6VSWRP
Command Description:
This command is used to start an asynchronous test in the object.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of perftest
command is the following:
JOB: 35
PC Time&Date: 26.09.2008 13:06:37 +02:00
NE Time&Date: 26.09.2008 10:13:55 +01:00
USER NAME:
User_s
COMMAND:
Perftest F6VSWRP:NAME=RACK:0/F6VSWRP:0;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation successful
MOT = RACK:0/F6VSWRP:0
tO = BTSETEST:9
END OF OUTPUT FOR JOB 35
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Perftest F6VSWRP:NAME=RACK:0/F6VSWRP:0;
SET F6VSWRP
SET F6VSWRP
NAME=RACK:0..7/F6VSWRP:0..1 [,VSWRTDB=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h
SET F6VSWRP
Applicability:
Phase 2 and Phase 3.
A50016-G5100-B333-04-7619
Id:0900d80580595992
419
F6VSWRP
BS-4x / 82 II / 240 / 241 / 240XL commands
Visibility level: 2.
Command Description:
This command sets general attributes of the F6VSWRP.
Long Names:
NAME
Address of the managed object
VSWRTDB
vswrThresholdDb
System Responses:
Operation Completed
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
JOB: 53
PC Time&Date: 24.09.2008 14:13:35 +02:00
NE Time&Date: 24.09.2008 10:22:09 +00:00
USER NAME:
User_s
COMMAND:
Set
F6VSWRP:NAME=RACK:0/F6VSWRP:0,VSWRTDB=LOW_3_0_HIGH_4_0;
SW RELEASE:
03-04-19-01-11-05_08-09-24
COMMAND RESULT: Operation successful
vswrThresholdDb = LOW_3_0_HIGH_4_0
END OF OUTPUT FOR JOB 53
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Set F6VSWRP:NAME=RACK:0/F6VSWRP:0,VSWRTDB=LOW_3_0_HIGH_4_0;
STOPTEST F6VSWRP
STOPTEST F6VSWRP
420
NAME=RACK:0..7/F6VSWRP:0..1;
Id:0900d80580595992
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6VSWRP
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h
STOPTEST F6VSWRP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
...
.
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
Operation Failed
The specified action has not been performed. In addition to the general NACK causes,
a specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 244
A50016-G5100-B333-04-7619
Id:0900d80580595992
421
F6VSWRP
BS-4x / 82 II / 240 / 241 / 240XL commands
PC Time&Date: 17.09.2008 16:07:01 +02:00
NE Time&Date: 17.09.2008 13:15:34 +01:00
USER NAME:
User_s
COMMAND:
Stoptest F6VSWRP:NAME=RACK:0/F6VSWRP:1;
SW RELEASE:
01-04-19-01-12-MB_08-09-12
COMMAND RESULT: Operation failed
MOT = RACK:0/F6VSWRP:1
Object instance unknown or not allowed (-9)
END OF OUTPUT FOR JOB 244
Application Guidelines:
None.
Example of Command Execution:
Stoptest F6VSWRP:NAME=RACK:0/F6VSWRP:0;
UNLOCK F6VSWRP
UNLOCK F6VSWRP
NAME=RACK:0..7/F6VSWRP:0..1;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h F6VSWRP h
UNLOCK F6VSWRP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of F6VSWRP.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 227
422
Id:0900d80580595992
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
F6VSWRP
PC Time&Date: 17.09.2008 16:03:02 +02:00
NE Time&Date: 17.09.2008 13:11:35 +01:00
USER NAME:
User_s
COMMAND:
Unlock F6VSWRP:NAME=RACK:0/F6VSWRP:0;
SW RELEASE:
01-04-19-01-12-MB_08-09-12
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 227
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Unlock F6VSWRP:NAME=RACK:0/F6VSWRP:0;
A50016-G5100-B333-04-7619
Id:0900d80580595992
423
FANP
BS-4x / 82 II / 240 / 241 / 240XL commands
FANP
The self controlled central FAN units are used in order to guarantee a sufficient airflow
for convection cooling of the modules. Two fans are responsible for each sub-rack. An
integrated temperature sensor enables the fan control.
CREATE FANP
CREATE FANP
NAME=RACK:0..7/FANP:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FANP h
CREATE FANP
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the FANP unit to the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 147
PC Time&Date: 12:01:41 03/23/2005
NE Time&Date: 13:03:16 09/15/2004
USER NAME:
User_t
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/FANP:0
ChangeInfo = created
424
Id:0900d80580595994
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FANP
END OF OUTPUT FOR JOB 147
JOB: 148
PC Time&Date: 12:01:41 03/23/2005
NE Time&Date: 13:03:16 09/15/2004
USER NAME:
User_t
COMMAND:
Create FANP:NAME=RACK:0/FANP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 148
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 149
PC Time&Date: 12:02:04 03/23/2005
NE Time&Date: 13:03:39 09/15/2004
USER NAME:
User_t
COMMAND:
Create FANP:NAME=RACK:0/FANP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
message cannot be performed (-17)
END OF OUTPUT FOR JOB 149
Application Guidelines:
In operation, all FANPs must be created
The maximum number of FANPs is: 6 for BS240/241/240SR/241SR and BS40/41,
8 for BS240XL/BS240XLSR, 5 for BS40II and 1 for BS82II
The FANP object is always created with status unlocked.enable.null.null.cleared. If
the HW is not connected or not present or if the board has a HW failure the object is
then immediatly set to unlocked.disabled.failed
A50016-G5100-B333-04-7619
Id:0900d80580595994
425
FANP
BS-4x / 82 II / 240 / 241 / 240XL commands
If the operator creates in advance the object FANP in an extension rack which is not
yet connected to the Base rack or if the ACT is not enabled, the FANP always keep
the states unlocked.enabled.null.null.cleared and no alarm is visible, even if the
FAN-HW is not present or the board has an HW-failure
In the BS82 II the ACT must also be enabled in the base rack for correct displaying
of the FAN status
Example of Command Execution:
Create FANP:NAME=RACK:0/FANP:0;
DELETE FANP
DELETE FANP
NAME=RACK:0..7/FANP:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FANP h
DELETE FANP
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the FANP unit from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 145
PC Time&Date: 12:01:38 03/23/2005
NE Time&Date: 13:03:13 09/15/2004
USER NAME:
User_t
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/FANP:0
426
Id:0900d80580595994
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FANP
ChangeInfo = deleted
END OF OUTPUT FOR JOB 145
JOB: 146
PC Time&Date: 12:01:38 03/23/2005
NE Time&Date: 13:03:13 09/15/2004
USER NAME:
User_t
COMMAND:
Delete FANP:NAME=RACK:0/FANP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 146
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
FANP must be locked in Phase 3, before deletion
The deletion of a FANP is critical in operation
Example of Command Execution:
Delete FANP:NAME=RACK:0/FANP:0;
GET FANP
GET FANP
NAME=RACK:0..7/FANP:0..7 [,REQATTL=ALS, AST, AVS,
OST, PRS, RELFUNCOBJ];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FANP h GET
FANP
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the FANP units of the BTSE.
Long Names:
NAME
A50016-G5100-B333-04-7619
Address of the managed object
Id:0900d80580595994
427
FANP
BS-4x / 82 II / 240 / 241 / 240XL commands
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 132
PC Time&Date: 12:01:18 03/23/2005
NE Time&Date: 13:02:53 09/15/2004
USER NAME:
User_t
COMMAND:
Get FANP:NAME=RACK:0/FANP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
operationalState = ENABLED
proceduralStatus = NULL
relatedFuncObjects =
END OF OUTPUT FOR JOB 132
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
The value for ProcStatus must be Null Status
The relatedFuncObjects always empty
Example of Command Execution:
Get FANP:NAME=RACK:0/FANP:0,REQATTL=ALS&AST&AVS&OST&PRS;
428
Id:0900d80580595994
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FANP
GETTEST FANP
GETTEST FANP
NAME=RACK:0..7/FANP:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FANP h
GETTEST FANP
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the FANP test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 140
PC Time&Date: 12:01:25 03/23/2005
NE Time&Date: 13:03:00 09/15/2004
USER NAME:
User_t
COMMAND:
Gettest FANP:NAME=RACK:0/FANP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/FANP:0
testMonitor =
phaseId = PreliminaryTestsFanp
phaseStatus = Running
phaseId = CheckAlarmStatusFanp
phaseStatus = Waiting
phaseId = EndTestFanp
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
A50016-G5100-B333-04-7619
Id:0900d80580595994
429
FANP
BS-4x / 82 II / 240 / 241 / 240XL commands
END OF OUTPUT FOR JOB 140
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest FANP:NAME=RACK:0/FANP:0;
LOCK FANP
LOCK FANP
NAME=RACK:0..7/FANP:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FANP h
LOCK FANP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the FANP unit of the BTSE.
Long Names:
NAME
430
Address of the managed object
Id:0900d80580595994
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FANP
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 143
PC Time&Date: 12:01:36 03/23/2005
NE Time&Date: 13:03:11 09/15/2004
USER NAME:
User_t
COMMAND:
Lock FANP:NAME=RACK:0/FANP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 143
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 144
PC Time&Date: 12:01:36 03/23/2005
NE Time&Date: 13:03:11 09/15/2004
USER NAME:
User_t
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/FANP:0
Administrative State = LOCKED
Notification Identifier = 341
END OF OUTPUT FOR JOB 144
A50016-G5100-B333-04-7619
Id:0900d80580595994
431
FANP
BS-4x / 82 II / 240 / 241 / 240XL commands
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
After locking of the FANP, the FANP will still be in operation, but in the administrative
state Locked
Example of Command Execution:
Lock FANP:NAME=RACK:0/FANP:0;
PERFTEST FANP
PERFTEST FANP
NAME=RACK:0..7/FANP:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FANP h
PERFTEST FANP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in FANP.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSEP.
JOB: 136
PC Time&Date: 12:01:25 03/23/2005
NE Time&Date: 13:03:00 09/15/2004
USER NAME:
User_t
COMMAND:
Perftest FANP:NAME=RACK:0/FANP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/FANP:0
tO = BTSETEST:6
432
Id:0900d80580595994
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FANP
END OF OUTPUT FOR JOB 136
JOB: 137
PC Time&Date: 12:01:25 03/23/2005
NE Time&Date: 13:03:00 09/15/2004
USER NAME:
User_t
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:6
ChangeInfo = created
END OF OUTPUT FOR JOB 137
JOB: 138
PC Time&Date: 12:01:25 03/23/2005
NE Time&Date: 13:03:00 09/15/2004
USER NAME:
User_t
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/FANP:0
Operational State = ENABLED
Availability Status = NULL_value
Notification Identifier = 339
END OF OUTPUT FOR JOB 138
A50016-G5100-B333-04-7619
Id:0900d80580595994
433
FANP
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 139
PC Time&Date: 12:01:25 03/23/2005
NE Time&Date: 13:03:00 09/15/2004
USER NAME:
User_t
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:6
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/FANP:0
executedPhases =
PreliminaryTestsFanp
CheckAlarmStatusFanp
EndTestFanp
END OF OUTPUT FOR JOB 139
JOB: 140
PC Time&Date: 12:01:25 03/23/2005
NE Time&Date: 13:03:00 09/15/2004
USER NAME:
User_t
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:6
ChangeInfo = deleted
END OF OUTPUT FOR JOB 140
The test results will be displayed at the end of the test phases.
434
Id:0900d80580595994
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FANP
Result TEST:
name =
TEST:<n>
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
In phase 3 MO must be locked previous to the command execution
A50016-G5100-B333-04-7619
Id:0900d80580595994
435
FANP
BS-4x / 82 II / 240 / 241 / 240XL commands
Example of Command Execution:
Perftest FANP:NAME=RACK:0/FANP:0;
STOPTEST FANP
STOPTEST FANP
NAME=RACK:0..7/FANP:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FANP h
STOPTEST FANP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
...
.
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
phaseId =
436
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
Id:0900d80580595994
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FANP
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
Application Guidelines:
None.
Example of Command Execution:
Stoptest FANP:NAME=RACK:0/FANP:0;
UNLOCK FANP
UNLOCK FANP
NAME=RACK:0..7/FANP:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FANP h
UNLOCK FANP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the FANP unit of the BTSE.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 141
PC Time&Date: 12:01:28 03/23/2005
NE Time&Date: 13:03:03 09/15/2004
USER NAME:
User_t
COMMAND:
Unlock FANP:NAME=RACK:0/FANP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 141
A50016-G5100-B333-04-7619
Id:0900d80580595994
437
FANP
BS-4x / 82 II / 240 / 241 / 240XL commands
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 142
PC Time&Date: 12:01:28 03/23/2005
NE Time&Date: 13:03:03 09/15/2004
USER NAME:
User_t
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/FANP:0
Administrative State = UNLOCKED
Notification Identifier = 340
END OF OUTPUT FOR JOB 142
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
After locking of the FANP, the FANP will still be in operation, but in the administrative
state Locked
Example of Command Execution:
Unlock FANP:NAME=RACK:0/FANP:0;
438
Id:0900d80580595994
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUMAIN
FCUMAIN
The FlexCU board is modeled with three HMO instances: 1 instance of the FCUMAIN
HMO and 2 instances of the FCUTR HMO. The FCUMAIN instance represents that part
of the board which performs board related activities and the FCUTR instances represent
carrier (TRX) specific activities. There is a dependency of the FCUTR instances towards
the FCUMAIN instance of a FlexCU.
CREATE FCUMAIN
CREATE FCUMAIN
NAME=RACK:0..7/FCUMAIN:0..11 [,FCUMODE=] [,RXLEVADJ=] [,RXLEVADJN1D1=] [,TCC=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h
CREATE FCUMAIN
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the FCUMAIN unit to the BTSE data base.
Long Names:
NAME
Address of the managed object
FCUMODE
fcuMode
RXLEVADJ
rxLevAdjust(dB)
RXLEVADJN1D1
TCC
rxLevAdjustN1D1(dB)
txCoherentComb
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 56
PC Time&Date: 16:34:31 03/23/2005
NE Time&Date: 16:32:25 09/15/2004
USER NAME:
user_Eberhard
COMMAND:
Create FCUMAIN:NAME=RACK:0/FCUMAIN:0,FCUMODE=singleCUMode,RXLEVADJ=1-1,RXLEVADJN1D1=1-1;
A50016-G5100-B333-04-7619
Id:0900d80580595996
439
FCUMAIN
BS-4x / 82 II / 240 / 241 / 240XL commands
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/FCUMAIN:0
ChangeInfo = created
M
END OF OUTPUT FOR JOB 56
JOB: 57
PC Time&Date: 16:34:31 03/23/2005
NE Time&Date: 16:32:25 09/15/2004
USER NAME:
user_Eberhard
COMMAND: Create FCUMAIN:NAME=RACK:0/FCUMAIN:0,FCUMODE=singleCUMode,RXLEVADJ=1-1,RXLEVADJN1D1=1-1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
fcuMode = singleCUMode
rxLevAdjust(dB) =
adjustValue = 1.0
adjustDivValue = 1.0
rxLevAdjustN1D1(dB) =
adjustValueN1 = 1.0
adjustDivValueD1 = 1.0
END OF OUTPUT FOR JOB 57
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 76
PC Time&Date: 16:37:54 03/23/2005
NE Time&Date: 16:35:47 09/15/2004
440
Id:0900d80580595996
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
USER NAME:
FCUMAIN
user_Eberhard
COMMAND:
Create FCUMAIN:NAME=RACK:0/FCUMAIN:0,FCUMODE=singleCUMode,RXLEVADJ=1-1,RXLEVADJN1D1=1-1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation failed
fcuMode = singleCUMode
rxLevAdjust(dB) =
adjustValue = 1.0
adjustDivValue = 1.0
rxLevAdjustN1D1(dB) =
adjustValueN1 = 1.0
adjustDivValueD1 = 1.0
message cannot be performed (-17)
END OF OUTPUT FOR JOB 76
Application Guidelines:
None.
Example of Command Execution:
Create FCUMAIN: NAME=RACK:0/FCUMAIN:0,FCUMODE=singleCUMode,
RXLEVADJ-20,RXLEVADJN1D1-20;
DELETE FCUMAIN
DELETE FCUMAIN
NAME=RACK:0..7/FCUMAIN:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h
DELETE FCUMAIN
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the FCUMAIN unit from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
A50016-G5100-B333-04-7619
Id:0900d80580595996
441
FCUMAIN
BS-4x / 82 II / 240 / 241 / 240XL commands
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 66
PC Time&Date: 16:35:23 03/23/2005
NE Time&Date: 16:33:17 09/15/2004
USER NAME:
user_Eberhard
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/FCUMAIN:0
ChangeInfo = deleted
END OF OUTPUT FOR JOB 66
JOB: 67
PC Time&Date: 16:35:23 03/23/2005
NE Time&Date: 16:33:17 09/15/2004
USER NAME:
user_Eberhard
COMMAND:
Delete FCUMAIN:NAME=RACK:0/FCUMAIN:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 67
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
None.
Example of Command Execution:
Delete FCUMAIN:NAME=RACK:0/FCUMAIN:0;
442
Id:0900d80580595996
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUMAIN
GET FCUMAIN
GET FCUMAIN
NAME=RACK:0..7/FCUMAIN:0..11 [,REQATTL=ALS, AST,
AVS, BSWVER, FCUMODE, OST, PRS, RELFUNCOBJ,
RXLEVADJ, RXLEVADJN1D1, FPGAFWVER, TCC];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h
GET FCUMAIN
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the FCUMAIN unit of the BTSE.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
BSWVER
bootSoftwareVersion
FCUMODE
fcuMode
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
RXLEVADJ
relatedFuncObjects
rxLevAdjust(dB)
RXLEVADJN1D1
FPGAFWVER
TCC
rxLevAdjustN1D1(dB)
fpgaFwVer
txCoherentComb
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 8
PC Time&Date: 26.06.2008 11:13:56 +02:00
NE Time&Date: 01.01.1990 00:13:20 +00:00
USER NAME:
A50016-G5100-B333-04-7619
user_Eberhard
Id:0900d80580595996
443
FCUMAIN
BS-4x / 82 II / 240 / 241 / 240XL commands
COMMAND:
Get FCUMAIN:NAME=RACK:0/FCUMAIN:1;
SW RELEASE:
01-04-19-01-09-01_08-06-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
bootSoftwareVersion = ""
fcuMode = doubleCUMode
operationalState = DISABLED
proceduralStatus = initializing
relatedFuncObjects = Null
rxLevAdjust(dB) =
adjustValue = 0.0
adjustDivValue = 0.0
rxLevAdjustN1D1(dB) =
adjustValueN1 = 0.0
adjustDivValueD1 = 0.0
END OF OUTPUT FOR JOB 8
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
FPGAFWVER attribute identifier cannot be present in the listOfRequiredAttributes
together with other attribute identifiers and it is not sent by the BTSE if a Get FCUMAIN/Get CU is done without the information element listOfRequiredAttributes
Example of Command Execution:
Get FCUMANIN:NAME=RACK:0/FTNFP:0,REQATTL=ALS&AST&AVS&BSWVER&
FCUMODE&OST&PRS&RELFUNCOBJ& RXLEVADJ&RXLEVADJN1D1&TCC;
GET FCUMAIN FWID
GET FCUMAIN FWID
NAME=RACK:0..7/FCUMAIN:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h
GET FCUMAIN FWID
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
444
Id:0900d80580595996
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUMAIN
Command Description:
This command provides information on the FPGA FW images that are contained in the
boards flash prom together with an indication of the active version.
Up to 4 images are provided per board.
For FlexCUv2 or ECUv6 boards the FPGA FW versions are provided together with an
indication whether the FW version is the active one.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
JOB: 9
PC Time&Date: 26.06.2008 11:14:02 +02:00
NE Time&Date: 01.01.1990 00:13:26 +00:00
USER NAME:
user_Eberhard
COMMAND:
Get FCUMAIN FWID:NAME=RACK:0/FCUMAIN:1;
SW RELEASE:
01-04-19-01-09-01_08-06-23
COMMAND RESULT:
Operation successful
fpgaFwVer = Null
END OF OUTPUT FOR JOB 9
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
Get FCUMAIN FWID:NAME=RACK:0/FCUMAIN:1, REQATTL=FPGAFWVER;
GET FCUMAIN WIRING
GET FCUMAIN WIRING NAME=RACK:0..7/FCUMAIN:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h
GET FCUMAIN WIRING
Applicability:
Phase 2 and Phase 3.
A50016-G5100-B333-04-7619
Id:0900d80580595996
445
FCUMAIN
BS-4x / 82 II / 240 / 241 / 240XL commands
Visibility level: 0.
Command Description:
This command displays the attributes of the FCUMAIN unit of the BTSE.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of create
command is the following:
JOB: 221
PC Time&Date: 12:13:58 03/23/2005
NE Time&Date: 13:15:33 09/15/2004
USER NAME:
user_Eberhard
COMMAND:
Get FCUMAIN WIRING:NAME=RACK:0/FCUMAIN:1;
SW RELEASE:
cessful
01-04-17-01-26-51_05-02-23COMMAND RESULT: Operation suc-
fcumainWiring =
variable
END OF OUTPUT FOR JOB 221
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
Refer to FCUMAINWIRING
Example of Command Execution:
Get FCUMAIN WIRING:NAME=RACK:0/FCUMAIN:0;
GETTEST FCUMAIN
GETTEST FCUMAIN
446
NAME=RACK:0..7/FCUMAIN:0..11;
Id:0900d80580595996
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUMAIN
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h
GETTEST FCUMAIN
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the FCUMAIN test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 221
PC Time&Date: 12:13:58 03/23/2005
NE Time&Date: 13:15:33 09/15/2004
USER NAME:
user_Eberhard
COMMAND:
Gettest FCUMAIN:NAME=RACK:0/FCUMAIN:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/FCUMAIN:0
testMonitor =
phaseId = PreliminaryTestsFCUMAIN
phaseStatus = Running
phaseId = CheckAlarmStatusFCUMAIN
phaseStatus = Waiting
phaseId = EndTestFCUMAIN
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
END OF OUTPUT FOR JOB 221
A50016-G5100-B333-04-7619
Id:0900d80580595996
447
FCUMAIN
BS-4x / 82 II / 240 / 241 / 240XL commands
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest FCUMAIN:NAME=RACK:0/FCUMAIN:0;
LOCK FCUMAIN
LOCK FCUMAIN
NAME=RACK:0..7/FCUMAIN:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h
LOCK FCUMAIN
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the FCUMAIN object of the BTSE.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
448
Id:0900d80580595996
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUMAIN
JOB: 60
PC Time&Date: 16:35:08 03/23/2005
NE Time&Date: 16:33:02 09/15/2004
USER NAME:
user_Eberhard
COMMAND:
Lock FCUMAIN:NAME=RACK:0/FCUMAIN:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 60
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 61
PC Time&Date: 16:35:08 03/23/2005
NE Time&Date: 16:33:02 09/15/2004
USER NAME:
user_Eberhard
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/FCUMAIN:0
Administrative State = LOCKED
Notification Identifier = 494
END OF OUTPUT FOR JOB 61
Operation Failed
The specified change of administrative state has not been performed.
A50016-G5100-B333-04-7619
Id:0900d80580595996
449
FCUMAIN
BS-4x / 82 II / 240 / 241 / 240XL commands
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Lock FCUMAIN:NAME=RACK:0/FCUMANIN:0
PERFTEST FCUMAIN
PERFTEST FCUMAIN
NAME=RACK:0..7/FCUMAIN:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h
PERFTEST FCUMAIN
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in FCUMAIN .
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSEP.
JOB: 222
PC Time&Date: 12:14:01 03/23/2005
NE Time&Date: 13:15:36 09/15/2004
USER NAME:
user_Eberhard
COMMAND:
Perftest FCUMAIN:NAME=RACK:0/FCUMAIN:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/FCUMAIN:0
tO = BTSETEST:6
END OF OUTPUT FOR JOB 222
450
Id:0900d80580595996
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUMAIN
JOB: 223
PC Time&Date: 12:14:01 03/23/2005
NE Time&Date: 13:15:36 09/15/2004
USER NAME:
user_Eberhard
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:6
ChangeInfo = created
END OF OUTPUT FOR JOB 223
JOB: 224
PC Time&Date: 12:14:01 03/23/2005
NE Time&Date: 13:15:36 09/15/2004
USER NAME:
user_Eberhard
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/FCUMAIN:0
Operational State = ENABLED
Availability Status = NULL_value
Notification Identifier = 139
END OF OUTPUT FOR JOB 224
JOB: 225
A50016-G5100-B333-04-7619
Id:0900d80580595996
451
FCUMAIN
BS-4x / 82 II / 240 / 241 / 240XL commands
PC Time&Date: 12:14:01 03/23/2005
NE Time&Date: 13:15:36 09/15/2004
USER NAME:
user_Eberhard
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:6
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/FCUMAIN:0
executedPhases =
PreliminaryTestsFCUMAIN
CheckAlarmStatusFCUMAIN
EndTestFCUMAIN
END OF OUTPUT FOR JOB 225
JOB: 226
PC Time&Date: 12:14:01 03/23/2005
NE Time&Date: 13:15:36 09/15/2004
USER NAME:
user_Eberhard
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:6
ChangeInfo = deleted
END OF OUTPUT FOR JOB 226
The test results will be displayed at the end of the test phases.
Result TEST:
name =
452
TEST:<n>
Id:0900d80580595996
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUMAIN
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
None.
Example of Command Execution:
Perftest FCUMAIN:NAME=RACK:0/FCUMANIN:0
A50016-G5100-B333-04-7619
Id:0900d80580595996
453
FCUMAIN
BS-4x / 82 II / 240 / 241 / 240XL commands
SET FCUMAIN
SET FCUMAIN
NAME=RACK:0..7/FCUMAIN:0..11 [,RXLEVADJ=]
[,RXLEVADJN1D1=] [,TCC=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h
SET FCUMAIN
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command is used to set the attributes of the specified FCUMAIN .
Long Names:
NAME
Address of the managed object
RXLEVADJ
rxLevAdjust(dB)
RXLEVADJN1D1
TCC
rxLevAdjustN1D1(dB)
txCoherentComb
System Responses:
Operation Completed
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
JOB: 176
PC Time&Date: 12:05:36 03/23/2005
NE Time&Date: 13:07:12 09/15/2004
USER NAME:
user_Eberhard
COMMAND:
Set FCUMAIN:NAME=RACK:0/FCUMAIN:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 176
Operation Failed
The specified attributes have not been set. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible.
454
Id:0900d80580595996
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUMAIN
Application Guidelines:
None.
Example of Command Execution:
Set FCUMAIN:NAME=RACK:0/FCUMANIN:0,RXLEVADJ=-2,RXLEVADJN1D1=-2
STOPTEST FCUMAIN
STOPTEST FCUMAIN
NAME=RACK:0..7/FCUMAIN:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h
STOPTEST FCUMAIN
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
...
.
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
A50016-G5100-B333-04-7619
Id:0900d80580595996
455
FCUMAIN
BS-4x / 82 II / 240 / 241 / 240XL commands
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
phaseId =
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
Application Guidelines:
None.
Example of Command Execution:
Stoptest FCUMAIN:NAME=RACK:0/FCUMANIN:0;
UNLOCK FCUMAIN
UNLOCK FCUMAIN
NAME=RACK:0..7/FCUMAIN:0..11;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUMAIN h
UNLOCK FCUMAIN
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the FCUMAIN object of the BTSE.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 62
PC Time&Date: 16:35:12 03/23/2005
NE Time&Date: 16:33:06 09/15/2004
USER NAME:
user_Eberhard
COMMAND:
Unlock FCUMAIN:NAME=RACK:0/FCUMAIN:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
456
Id:0900d80580595996
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUMAIN
END OF OUTPUT FOR JOB 62
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 63
PC Time&Date: 16:35:12 03/23/2005
NE Time&Date: 16:33:06 09/15/2004
USER NAME:
user_Eberhard
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/FCUMAIN:0
Administrative State = UNLOCKED
Notification Identifier = 495
END OF OUTPUT FOR JOB 63
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Unlock FCUMAIN:NAME=RACK:0/FCUMANIN:0;
A50016-G5100-B333-04-7619
Id:0900d80580595996
457
FCUTR
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUTR
The FlexCU board is modeled with three HMO instances: 1 instance of the FCUMAIN
HMO and 2 instances of the FCUTR HMO. The FCUMAIN instance represents that part
of the board which performs board related activities and the FCUTR instances represent
carrier (TRX) specific activities. There is a dependency of the FCUTR instances towards
the FCUMAIN instance of a FlexCU.
CREATE FCUTR
CREATE FCUTR
NAME=RACK:0..7/FCUTR:0..23 [,TXLEVADJ=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h
CREATE FCUTR
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the FCUTR unit to the BTSE data base.
Long Names:
NAME
Address of the managed object
TXLEVADJ
txLevAdjust(dB)
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 56
PC Time&Date: 16:34:31 03/23/2005
NE Time&Date: 16:32:25 09/15/2004
USER NAME:
user_Frank
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
458
Id:0900d80580595998
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUTR
name = RACK:0/FCUTR:0
ChangeInfo = created
END OF OUTPUT FOR JOB 56
JOB: 57
PC Time&Date: 16:34:31 03/23/2005
NE Time&Date: 16:32:25 09/15/2004
USER NAME:
user_Frank
COMMAND:
Create FCUTR:NAME=RACK:0/FCUTR:0,TXLEVADJ=1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
txLevAdjust(dB) = 1.0
END OF OUTPUT FOR JOB 57
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 76
PC Time&Date: 16:37:54 03/23/2005
NE Time&Date: 16:35:47 09/15/2004
USER NAME:
user_Frank
COMMAND:
Create FCUTR:NAME=RACK:0/FCUTR:0,TXLEVADJ=1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation failed
txLevAdjust(dB) = 1.0
Creation out of sequence (-162)
END OF OUTPUT FOR JOB 76
Application Guidelines:
None.
A50016-G5100-B333-04-7619
Id:0900d80580595998
459
FCUTR
BS-4x / 82 II / 240 / 241 / 240XL commands
Example of Command Execution:
Create FCUTR:NAME=RACK:0/FCUTR:0,TXLEVADJ=-20;
DELETE FCUTR
DELETE FCUTR
NAME=RACK:0..7/FCUTR:0..23;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h
DELETE FCUTR
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the FCUTR unit from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 66
PC Time&Date: 16:35:23 03/23/2005
NE Time&Date: 16:33:17 09/15/2004
USER NAME:
user_Frank
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/FCUTR:0
ChangeInfo = deleted
END OF OUTPUT FOR JOB 66
JOB: 67
460
Id:0900d80580595998
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUTR
PC Time&Date: 16:35:23 03/23/2005
NE Time&Date: 16:33:17 09/15/2004
USER NAME:
user_Frank
COMMAND:
Delete FCUTR:NAME=RACK:0/FCUTR:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 67
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
None.
Example of Command Execution:
Delete FCUTR:NAME=RACK:0/FCUTR:0;
GET FCUTR
GET FCUTR
NAME=RACK:0..7/FCUTR:0..23 [,REQATTL=ALS, AST,
AVS, CCPBL, OST, OUTPUTPR, PRS, RELFUNCOBJ,
TXLEVADJ, STDBYST];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h
GET FCUTR
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the FCUTR unit of the BTSE.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
CCPBL
carrierCapability
A50016-G5100-B333-04-7619
Id:0900d80580595998
461
FCUTR
BS-4x / 82 II / 240 / 241 / 240XL commands
OST
operationalState
OUTPUTPR
outputPowerReduction
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
TXLEVADJ
txLevAdjust(dB)
STDBYST
standbyStatus
System Responses:
Operation Completed
A message indicates the result of the operation. An example of GETcommand is the following:
JOB: 59
PC Time&Date: 16:34:52 03/23/2005
NE Time&Date: 16:32:46 09/15/2004
USER NAME: user_Frank
COMMAND: Get FCUTR:NAME=RACK:0/FCUTR:0;
SW RELEASE: 01-04-17-01-26-51_05-02-23
COMMAND RESULT:Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
carrierCapability = edgeFourRxDiv
operationalState = ENABLED
outputPowerReduction = db0
proceduralStatus = NULL
relatedFuncObjects =
FMO = BTS:2/TRX:6
standbyStatus = ColdStandBy
txLevAdjust(dB) = 0.0
END OF OUTPUT FOR JOB 59
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
None.
Example of Command Execution:
Get FCUTR:NAME=RACK:0/FCUTR:0,REQATTL=ALS&AST&AVS& CCPBL&OUTPUTPR&OST&PRS&RELFUNCOBJ& TXLEVADJ;
462
Id:0900d80580595998
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUTR
GETTEST FCUTR
GETTEST FCUTR
NAME=RACK:0..7/FCUTR:0..23;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h
GETTEST FCUTR
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the FCUTR test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 221
PC Time&Date: 12:13:58 03/23/2005
NE Time&Date: 13:15:33 09/15/2004
USER NAME:
user_Frank
COMMAND:
Gettest FCUTR:NAME=RACK:0/FCUTR:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/FTNFP:0
testMonitor =
phaseId = PreliminaryTestsFCUTR
phaseStatus = Running
phaseId = CheckAlarmStatusFCUTR
phaseStatus = Waiting
phaseId = EndTestFCUTR
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
A50016-G5100-B333-04-7619
Id:0900d80580595998
463
FCUTR
BS-4x / 82 II / 240 / 241 / 240XL commands
END OF OUTPUT FOR JOB 221
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest FCUTR:NAME=RACK:0/FCUTR:0;
LOCK FCUTR
LOCK FCUTR
NAME=RACK:0..7/FCUTR:0..23;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h
LOCK FCUTR
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the FCUTR object of the BTSE.
Long Names:
NAME
464
Address of the managed object
Id:0900d80580595998
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUTR
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 60
PC Time&Date: 16:35:08 03/23/2005
NE Time&Date: 16:33:02 09/15/2004
USER NAME:
user_Frank
COMMAND:
Lock FCUTR:NAME=RACK:0/FCUTR:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 60
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 61
PC Time&Date: 16:35:08 03/23/2005
NE Time&Date: 16:33:02 09/15/2004
USER NAME:
user_Frank
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/FCUTR:0
Administrative State = LOCKED
Notification Identifier = 494
END OF OUTPUT FOR JOB 61
A50016-G5100-B333-04-7619
Id:0900d80580595998
465
FCUTR
BS-4x / 82 II / 240 / 241 / 240XL commands
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Lock FCUTR:NAME=RACK:0/FCUTR:0;
PERFTEST FCUTR
PERFTEST FCUTR
NAME=RACK:0..7/FCUTR:0..23;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h
PERFTEST FCUTR
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in FCUTR.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSEP.
JOB: 222
PC Time&Date: 12:14:01 03/23/2005
NE Time&Date: 13:15:36 09/15/2004
USER NAME:
user_Frank
COMMAND:
Perftest FCUTR:NAME=RACK:0/FCUTR:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/FCUTR:0
tO = BTSETEST:6
466
Id:0900d80580595998
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUTR
END OF OUTPUT FOR JOB 222
JOB: 223
PC Time&Date: 12:14:01 03/23/2005
NE Time&Date: 13:15:36 09/15/2004
USER NAME:
user_Frank
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:6
ChangeInfo = created
END OF OUTPUT FOR JOB 223
JOB: 224
PC Time&Date: 12:14:01 03/23/2005
NE Time&Date: 13:15:36 09/15/2004
USER NAME:
user_Frank
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/FCUTR:0
Operational State = ENABLED
Availability Status = NULL_value
Notification Identifier = 139
END OF OUTPUT FOR JOB 224
A50016-G5100-B333-04-7619
Id:0900d80580595998
467
FCUTR
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 225
PC Time&Date: 12:14:01 03/23/2005
NE Time&Date: 13:15:36 09/15/2004
USER NAME:
user_Frank
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:6
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/FCUTR:0
executedPhases =
PreliminaryTestsFCUTR
CheckAlarmStatusFCUTR
EndTestFCUTR
END OF OUTPUT FOR JOB 225
JOB: 226
PC Time&Date: 12:14:01 03/23/2005
NE Time&Date: 13:15:36 09/15/2004
USER NAME:
user_Frank
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:6
ChangeInfo = deleted
END OF OUTPUT FOR JOB 226
The test results will be displayed at the end of the test phases.
468
Id:0900d80580595998
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUTR
Result TEST:
name =
TEST:<n>
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
None.
A50016-G5100-B333-04-7619
Id:0900d80580595998
469
FCUTR
BS-4x / 82 II / 240 / 241 / 240XL commands
Example of Command Execution:
Perftest FCUTR:NAME=RACK:0/FCUTR:0;
SET FCUTR
SET FCUTR
NAME=RACK:0..7/FCUTR:0..23 [,TXLEVADJ=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h
SET FCUTR
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command is used to set the attributes of the specified RACK.
Long Names:
NAME
Address of the managed object
TXLEVADJ
txLevAdjust(dB)
System Responses:
Operation Completed
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
JOB: 176
PC Time&Date: 12:05:36 03/23/2005
NE Time&Date: 13:07:12 09/15/2004
USER NAME:
user_Frank
COMMAND:
Set FCUTR:NAME=RACK:0/FCUTR:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 176
Operation Failed
The specified attributes have not been set. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible.
470
Id:0900d80580595998
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUTR
Application Guidelines:
None.
Example of Command Execution:
Set FCUTR:NAME=RACK:0/FCUTR:0;
STOPTEST FCUTR
STOPTEST FCUTR
NAME=RACK:0..7/FCUTR:0..23;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h
STOPTEST FCUTR
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
...
.
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
A50016-G5100-B333-04-7619
Id:0900d80580595998
471
FCUTR
BS-4x / 82 II / 240 / 241 / 240XL commands
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
phaseId =
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
Application Guidelines:
None.
Example of Command Execution:
Stoptest FCUTR:NAME=RACK:0/FCUTR:0;
UNLOCK FCUTR
UNLOCK FCUTR
NAME=RACK:0..7/FCUTR:0..23;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FCUTR h
UNLOCK FCUTR
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the FCUTR object of the BTSE.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 62
PC Time&Date: 16:35:12 03/23/2005
NE Time&Date: 16:33:06 09/15/2004
USER NAME:
user_Frank
COMMAND:
Unlock FCUTR:NAME=RACK:0/FCUTR:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
472
Id:0900d80580595998
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUTR
END OF OUTPUT FOR JOB 62
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 63
PC Time&Date: 16:35:12 03/23/2005
NE Time&Date: 16:33:06 09/15/2004
USER NAME:
user_Frank
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/FCUTR:0
Administrative State = UNLOCKED
Notification Identifier = 495
END OF OUTPUT FOR JOB 63
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Unlock FCUTR:NAME=RACK:0/FCUTR:0;
A50016-G5100-B333-04-7619
Id:0900d80580595998
473
FTNFP
BS-4x / 82 II / 240 / 241 / 240XL commands
FTNFP
The FTNFP object represents the hardware of the tunable filters in the dowlink direction
(from BTS to MS).
CREATE FTNFP
CREATE FTNFP
NAME=RACK:0..7/FTNFP:0..7 ,CELLNO= ,WDFTNFP=;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FTNFP h
CREATE FTNFP
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the FICOM_TNF unit to the BTSE data base.
Long Names:
NAME
Address of the managed object
CELLNO
cellNumber
WDFTNFP
wiringDataFtnfp
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 56
PC Time&Date: 16:34:31 03/23/2005
NE Time&Date: 16:32:25 09/15/2004
USER NAME:
user_v
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/FTNFP:0
ChangeInfo = created
474
Id:0900d8058059599a
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FTNFP
END OF OUTPUT FOR JOB 56
JOB: 57
PC Time&Date: 16:34:31 03/23/2005
NE Time&Date: 16:32:25 09/15/2004
USER NAME:
user_v
COMMAND:
Create FTNFP:NAME=RACK:0/FTNFP:0,CELLNO=1,WDFTNFP=CU0-FVSWRP0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
cellNumber = 1
wiringDataFtnfp =
CUWiring = CU0
FVSWRPWiring = FVSWRP0
END OF OUTPUT FOR JOB 57
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 76
PC Time&Date: 16:37:54 03/23/2005
NE Time&Date: 16:35:47 09/15/2004
USER NAME:
user_v
COMMAND:
Create FTNFP:NAME=RACK:0/FTNFP:0,CELLNO=1,WDFTNFP=CU0-FVSWRP0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
message cannot be performed (-17)
END OF OUTPUT FOR JOB 76
A50016-G5100-B333-04-7619
Id:0900d8058059599a
475
FTNFP
BS-4x / 82 II / 240 / 241 / 240XL commands
Application Guidelines:
The FICOM_TNFP, the CU and the FICOM_VSWRP are in the same rack and
belong to the same cell
Creation of FTNFP:i is rejected if DUAMCO:(i/2) is created
Example of Command Execution:
Create FTNFP:NAME=RACK:0/FTNFP:0,CELLNO=0,WDFTNFP=CU0-FVSWRP0;
DELETE FTNFP
DELETE FTNFP
NAME=RACK:0..7/FTNFP:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FTNFP h
DELETE FTNFP
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the FICOM_TNF unit from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 66
PC Time&Date: 16:35:23 03/23/2005
NE Time&Date: 16:33:17 09/15/2004
USER NAME:
user_v
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/FTNFP:0
ChangeInfo = deleted
476
Id:0900d8058059599a
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FTNFP
END OF OUTPUT FOR JOB 66
JOB: 67
PC Time&Date: 16:35:23 03/23/2005
NE Time&Date: 16:33:17 09/15/2004
USER NAME:
user_v
COMMAND:
Delete FTNFP:NAME=RACK:0/FTNFP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 67
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
FTNFP must be locked in Phase 3, before deletion
If this object is deleted, the related TRX is out of service
Example of Command Execution:
Delete FTNFP:NAME=RACK:0/FTNFP:0;
GET FTNFP
GET FTNFP
NAME=RACK:0..7/FTNFP:0..7 [,REQATTL=ALS, AST,
AVS, CELLNO, OST, PRS, RELFUNCOBJ, TNFTARGF,
WDFTNFP];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FTNFP h
GET FTNFP
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the FICOM_TNF unit of the BTSE.
Long Names:
NAME
A50016-G5100-B333-04-7619
Address of the managed object
Id:0900d8058059599a
477
FTNFP
BS-4x / 82 II / 240 / 241 / 240XL commands
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
CELLNO
cellNumber
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
TNFTARGF
tnfTargetFrequency
WDFTNFP
wiringDataFtnfp
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 59
PC Time&Date: 16:34:52 03/23/2005
NE Time&Date: 16:32:46 09/15/2004
USER NAME:
user_v
COMMAND:
Get FTNFP:NAME=RACK:0/FTNFP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NotInstalled
cellNumber = 1
operationalState = DISABLED
proceduralStatus = NULL
relatedFuncObjects =
tnfTargetFrequency = Null
wiringDataFtnfp =
CUWiring = CU0
FVSWRPWiring = FVSWRP0
END OF OUTPUT FOR JOB 59
Operation Failed
478
Id:0900d8058059599a
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FTNFP
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
The value for the attribute relatedFuncObjects in LMT Evolution Phase 2 is "not configured"
Example of Command Execution:
Get FTNFP:NAME=RACK:0/FTNFP:0,REQATTL=ALS&AST&AVS&CELLNO&
RELFUNCOBJ&OST&PRS&TNFTARGF&WDFTNFP;
GETTEST FTNFP
GETTEST FTNFP
NAME=RACK:0..7/FTNFP:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FTNFP h
GETTEST FTNFP
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the FTNFP test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 221
PC Time&Date: 12:13:58 03/23/2005
NE Time&Date: 13:15:33 09/15/2004
USER NAME:
user_v
COMMAND:
Gettest FTNFP:NAME=RACK:0/FTNFP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/FTNFP:0
A50016-G5100-B333-04-7619
Id:0900d8058059599a
479
FTNFP
BS-4x / 82 II / 240 / 241 / 240XL commands
testMonitor =
phaseId = PreliminaryTestsFtnfp
phaseStatus = Running
phaseId = CheckAlarmStatusFtnfp
phaseStatus = Waiting
phaseId = EndTestFtnfp
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
END OF OUTPUT FOR JOB 221
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest FTNFP:NAME=RACK:0/FTNFP:0;
LOCK FTNFP
LOCK FTNFP
NAME=RACK:0..7/FTNFP:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FTNFP h
LOCK FTNFP
480
Id:0900d8058059599a
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FTNFP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the FICOM_TNF object of the BTSE.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 60
PC Time&Date: 16:35:08 03/23/2005
NE Time&Date: 16:33:02 09/15/2004
USER NAME:
user_v
COMMAND:
Lock FTNFP:NAME=RACK:0/FTNFP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 60
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 61
PC Time&Date: 16:35:08 03/23/2005
NE Time&Date: 16:33:02 09/15/2004
USER NAME:
user_v
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
A50016-G5100-B333-04-7619
Id:0900d8058059599a
481
FTNFP
BS-4x / 82 II / 240 / 241 / 240XL commands
CHANGED STATE EVENT REPORT:
NAME = RACK:0/FTNFP:0
Administrative State = LOCKED
Notification Identifier = 494
END OF OUTPUT FOR JOB 61
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Lock FTNFP:NAME=RACK:0/FTNFP:0
PERFTEST FTNFP
PERFTEST FTNFP
NAME=RACK:0..7/FTNFP:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FTNFP h
PERFTEST FTNFP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in FTNFP.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSEP.
JOB: 222
PC Time&Date: 12:14:01 03/23/2005
NE Time&Date: 13:15:36 09/15/2004
482
Id:0900d8058059599a
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FTNFP
USER NAME:
user_v
COMMAND:
Perftest FTNFP:NAME=RACK:0/FTNFP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/FTNFP:0
tO = BTSETEST:6
END OF OUTPUT FOR JOB 222
JOB: 223
PC Time&Date: 12:14:01 03/23/2005
NE Time&Date: 13:15:36 09/15/2004
USER NAME:
user_v
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:6
ChangeInfo = created
END OF OUTPUT FOR JOB 223
JOB: 224
PC Time&Date: 12:14:01 03/23/2005
NE Time&Date: 13:15:36 09/15/2004
USER NAME:
user_v
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
A50016-G5100-B333-04-7619
Id:0900d8058059599a
483
FTNFP
BS-4x / 82 II / 240 / 241 / 240XL commands
NAME = RACK:0/FTNFP:0
Operational State = ENABLED
Availability Status = NULL_value
Notification Identifier = 139
END OF OUTPUT FOR JOB 224
JOB: 225
PC Time&Date: 12:14:01 03/23/2005
NE Time&Date: 13:15:36 09/15/2004
USER NAME:
user_v
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:6
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/FTNFP:0
executedPhases =
PreliminaryTestsFtnfp
CheckAlarmStatusFtnfp
EndTestFtnfp
END OF OUTPUT FOR JOB 225
JOB: 226
PC Time&Date: 12:14:01 03/23/2005
NE Time&Date: 13:15:36 09/15/2004
USER NAME:
user_v
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
484
Id:0900d8058059599a
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FTNFP
ChangedConfigurationNotification:
name = BTSETEST:6
ChangeInfo = deleted
END OF OUTPUT FOR JOB 226
The test results will be displayed at the end of the test phases.
Result TEST:
name =
TEST:<n>
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A50016-G5100-B333-04-7619
A list of most probable fail probable causes is shown
(max four messages)
Id:0900d8058059599a
485
FTNFP
BS-4x / 82 II / 240 / 241 / 240XL commands
Operation Failed
This NACK-message occurs in the following cases: message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
In phase 3 MO must be locked previous to the command execution
Example of Command Execution:
Perftest FTNFP:NAME=RACK:0/FTNFP:0;
STOPTEST FTNFP
STOPTEST FTNFP
NAME=RACK:0..7/FTNFP:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FTNFP h
STOPTEST FTNFP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
...
.
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
failedPhases
486
Id:0900d8058059599a
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FTNFP
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
phaseId =
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
Application Guidelines:
None.
Example of Command Execution:
Stoptest FTNFP:NAME=RACK:0/FTNFP:0;
UNLOCK FTNFP
UNLOCK FTNFP
NAME=RACK:0..7/FTNFP:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FTNFP h
UNLOCK FTNFP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the FICOM_TNF object of the BTSE.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 62
PC Time&Date: 16:35:12 03/23/2005
NE Time&Date: 16:33:06 09/15/2004
USER NAME:
A50016-G5100-B333-04-7619
user_v
Id:0900d8058059599a
487
FTNFP
BS-4x / 82 II / 240 / 241 / 240XL commands
COMMAND:
Unlock FTNFP:NAME=RACK:0/FTNFP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 62
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 63
PC Time&Date: 16:35:12 03/23/2005
NE Time&Date: 16:33:06 09/15/2004
USER NAME:
user_v
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/FTNFP:0
Administrative State = UNLOCKED
Notification Identifier = 495
END OF OUTPUT FOR JOB 63
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Unlock FTNFP:NAME=RACK:0/FTNFP:0;
488
Id:0900d8058059599a
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FVSWRP
FVSWRP
The FVSWR object represents the hardware of the tunable filters in the dowlink direction (from BTS to MS). There is only one FVSWR per cell, which performs also some
functionalities common to the cell (e.g. alarm generation).
CREATE FVSWRP
CREATE FVSWRP
NAME=RACK:0..7/FVSWRP:0..3 ,CELLNO=;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FVSWRP h
CREATE FVSWRP
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the FICOM_VSWR unit to the BTSE data base.
Long Names:
NAME
Address of the managed object
CELLNO
cellNumber
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 40
PC Time&Date: 16:31:19 03/23/2005
NE Time&Date: 16:29:13 09/15/2004
USER NAME:
user_val
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/FVSWRP:0
ChangeInfo = created
A50016-G5100-B333-04-7619
Id:0900d8058059599c
489
FVSWRP
BS-4x / 82 II / 240 / 241 / 240XL commands
END OF OUTPUT FOR JOB 40
JOB: 41
PC Time&Date: 16:31:19 03/23/2005
NE Time&Date: 16:29:13 09/15/2004
USER NAME:
user_val
COMMAND:
Create FVSWRP:NAME=RACK:0/FVSWRP:0,CELLNO=1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
cellNumber = 1
END OF OUTPUT FOR JOB 41
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 77
PC Time&Date: 16:37:54 03/23/2005
NE Time&Date: 16:35:47 09/15/2004
USER NAME:
user_val
COMMAND:
Create FVSWRP:NAME=RACK:0/FVSWRP:0,CELLNO=1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
Object instance unknown (-9)
END OF OUTPUT FOR JOB 77
Application Guidelines:
Creation of FVSWRP:i is rejected if DUAMCO:i is created.
Example of Command Execution:
Create FVSWRP:NAME=RACK:0/FVSWRP:0,CELLNO=0;
490
Id:0900d8058059599c
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FVSWRP
DELETE FVSWRP
DELETE FVSWRP
NAME=RACK:0..7/FVSWRP:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FVSWRP h
DELETE FVSWRP
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the FICOM_VSWR unit from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 51
PC Time&Date: 16:33:29 03/23/2005
NE Time&Date: 16:31:23 09/15/2004
USER NAME:
user_val
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/FVSWRP:0
ChangeInfo = deleted
END OF OUTPUT FOR JOB 51
JOB: 52
PC Time&Date: 16:33:29 03/23/2005
NE Time&Date: 16:31:23 09/15/2004
A50016-G5100-B333-04-7619
Id:0900d8058059599c
491
FVSWRP
BS-4x / 82 II / 240 / 241 / 240XL commands
USER NAME:
user_val
COMMAND:
Delete FVSWRP:NAME=RACK:0/FVSWRP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 52
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
FVSWRP must be locked in Phase 3, before deletion
If this object is deleted, the related TRXs are out of service
Example of Command Execution:
Delete FVSWRP:NAME=RACK:0/FVSWRP:0;
GET FVSWRP
GET FVSWRP
NAME=RACK:0..7/FVSWRP:0..3 [,REQATTL=ALS, AST,
AVS, CELLNO, OST, PRS, RELFUNCOBJ];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FVSWRP h
GET FVSWRP
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the FICOM_VSWR unit of the BTSE.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
CELLNO
cellNumber
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
492
relatedFuncObjects
Id:0900d8058059599c
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FVSWRP
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 43
PC Time&Date: 16:32:46 03/23/2005
NE Time&Date: 16:30:40 09/15/2004
USER NAME:
user_val
COMMAND:
Get FVSWRP:NAME=RACK:0/FVSWRP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NotInstalled
cellNumber = 1
operationalState = DISABLED
proceduralStatus = NULL
relatedFuncObjects =
END OF OUTPUT FOR JOB 43
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
The value for the attribute relatedFuncObjects in LMT Phase 2 is "not configured"
Example of Command Execution:
Get FVSWRP:NAME=RACK:0/FVSWRP:0,REQATTL=ALS&AST&AVS&CELLNO&
RELFUNCOBJ&OST&PRS;
GETTEST FVSWRP
GETTEST FVSWRP
NAME=RACK:0..7/FVSWRP:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FVSWRP h
GETTEST FVSWRP
A50016-G5100-B333-04-7619
Id:0900d8058059599c
493
FVSWRP
BS-4x / 82 II / 240 / 241 / 240XL commands
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the FVSWRP test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 227
PC Time&Date: 12:14:01 03/23/2005
NE Time&Date: 13:15:36 09/15/2004
USER NAME:
user_val
COMMAND:
Gettest FVSWRP:NAME=RACK:0/FVSWRP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/FVSWRP:0
testMonitor =
phaseId = PreliminaryTestsFvswrp
phaseStatus = Running
phaseId = CheckAlarmStatusFvswrp
phaseStatus = Waiting
phaseId = EndTestFvswrp
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
END OF OUTPUT FOR JOB 227
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
494
Id:0900d8058059599c
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
testMonitor
phaseId =
phaseStatus =
FVSWRP
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest FVSWRP:NAME=RACK:0/FVSWRP:0;
LOCK FVSWRP
LOCK FVSWRP
NAME=RACK:0..7/FVSWRP:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FVSWRP h
LOCK FVSWRP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of FICOM_VSWR unit of the BTSE.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 45
A50016-G5100-B333-04-7619
Id:0900d8058059599c
495
FVSWRP
BS-4x / 82 II / 240 / 241 / 240XL commands
PC Time&Date: 16:33:14 03/23/2005
NE Time&Date: 16:31:08 09/15/2004
USER NAME:
user_val
COMMAND:
Lock FVSWRP:NAME=RACK:0/FVSWRP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 45
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 46
PC Time&Date: 16:33:14 03/23/2005
NE Time&Date: 16:31:08 09/15/2004
USER NAME:
user_val
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/FVSWRP:0
Administrative State = LOCKED
Notification Identifier = 487
END OF OUTPUT FOR JOB 46
Operation Failed
The specified change of administrative state has not been performed.
496
Id:0900d8058059599c
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FVSWRP
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Lock FVSWRP:NAME=RACK:0/FVSWRP:0;
PERFTEST FVSWRP
PERFTEST FVSWRP
NAME=RACK:0..7/FVSWRP:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FVSWRP h
PERFTEST FVSWRP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in FVSWRP.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSEP.
JOB: 228
PC Time&Date: 12:14:07 03/23/2005
NE Time&Date: 13:15:42 09/15/2004
USER NAME:
user_val
COMMAND:
Perftest FVSWRP:NAME=RACK:0/FVSWRP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/FVSWRP:0
tO = BTSETEST:1
END OF OUTPUT FOR JOB 228
A50016-G5100-B333-04-7619
Id:0900d8058059599c
497
FVSWRP
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 229
PC Time&Date: 12:14:18 03/23/2005
NE Time&Date: 13:15:49 09/15/2004
USER NAME:
user_val
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:1
ChangeInfo = created
END OF OUTPUT FOR JOB 229
JOB: 230
PC Time&Date: 12:14:18 03/23/2005
NE Time&Date: 13:15:49 09/15/2004
USER NAME:
user_val
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/FVSWRP:0
Operational State = ENABLED
Availability Status = NULL_value
Notification Identifier = 238
END OF OUTPUT FOR JOB 230
JOB: 231
498
Id:0900d8058059599c
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FVSWRP
PC Time&Date: 12:14:23 03/23/2005
NE Time&Date: 13:15:52 09/15/2004
USER NAME:
user_val
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:1
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/FVSWRP:0
executedPhases =
PreliminaryTestsFvswrp
CheckAlarmStatusFvswrp
EndTestFvswrp
END OF OUTPUT FOR JOB 231
JOB: 232
PC Time&Date: 12:14:41 03/23/2005
NE Time&Date: 13:16:05 09/15/2004
USER NAME:
user_val
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:1
ChangeInfo = deleted
END OF OUTPUT FOR JOB 232
The test results will be displayed at the end of the test phases.
Result TEST:
name =
A50016-G5100-B333-04-7619
TEST:<n>
Id:0900d8058059599c
499
FVSWRP
BS-4x / 82 II / 240 / 241 / 240XL commands
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
....
skippedPhases
phaseId =
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines
In phase 3 MO must be locked previous to the command execution
Example of Command Execution:
Perftest FVSWRP:NAME=RACK:0/FVSWRP:0;
500
Id:0900d8058059599c
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FVSWRP
STOPTEST FVSWRP
STOPTEST FVSWRP
NAME=RACK:0..7/FVSWRP:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FVSWRP h
STOPTEST FVSWRP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
...
.
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
A50016-G5100-B333-04-7619
Id:0900d8058059599c
501
FVSWRP
BS-4x / 82 II / 240 / 241 / 240XL commands
Application Guidelines:
None.
Example of Command Execution:
Stoptest FVSWRP:NAME=RACK:0/FVSWRP:0;
UNLOCK FVSWRP
UNLOCK FVSWRP
NAME=RACK:0..7/FVSWRP:0..3;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h FVSWRP h
UNLOCK FVSWRP
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of FICOM_VSWR unit of the BTSE.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 47
PC Time&Date: 16:33:19 03/23/2005
NE Time&Date: 16:31:13 09/15/2004
USER NAME:
user_val
COMMAND:
Unlock FVSWRP:NAME=RACK:0/FVSWRP:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 47
CHANGED STATE EVENT REPORT:
502
Id:0900d8058059599c
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FVSWRP
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 48
PC Time&Date: 16:33:19 03/23/2005
NE Time&Date: 16:31:13 09/15/2004
USER NAME:
user_val
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/FVSWRP:0
Administrative State = UNLOCKED
Notification Identifier = 488
END OF OUTPUT FOR JOB 48
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Unlock FVSWRP:NAME=RACK:0/FVSWRP:0;
A50016-G5100-B333-04-7619
Id:0900d8058059599c
503
LAPDLE
BS-4x / 82 II / 240 / 241 / 240XL commands
LAPDLE
The LAPDLE object identifies the logical link used by the BTSEP to communicate with
the BSC for operational and maintenance purposes. The object LAPDLE on BTSEP
side is a HW object which correspond to the FMO LPDLM at BSC side. It is possible
configure in the BSC more than one LPDLM object for each BTSM object instance (up
to eight LPDLM links for each BTSM on the four PCMB lines, and the LAPD links are
either all 64 Kb/s or all 16 Kb/s, and either all satellited or all no satellited, for the same
BTSEP).
CREATE LAPDLE
CREATE LAPDLE
NAME=LAPDLE:0..10 ,LAPDCH=;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h LAPDLE h CREATE
LAPDLE
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds a LAPDLE object in the BTSE database.
Long Names:
NAME
Address of the managed object
LAPDCH
lapdChannel
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 150
PC Time&Date: 12:02:21 03/23/2005
NE Time&Date: 13:03:56 09/15/2004
USER NAME:
user_val1
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
504
Id:0900d8058059599e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
LAPDLE
name = LAPDLE:2
ChangeInfo = created
END OF OUTPUT FOR JOB 150
JOB: 151
PC Time&Date: 12:02:31 03/23/2005
NE Time&Date: 13:04:06 09/15/2004
USER NAME:
user_val1
COMMAND:
SSL0_16KB;
Create LAPDLE:NAME=LAPDLE:2,LAPDCH=BPORT0-1-
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 151
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 152
PC Time&Date: 12:02:31 03/23/2005
NE Time&Date: 13:04:06 09/15/2004
USER NAME:
user_val1
COMMAND:
SSL0_16KB;
Create LAPDLE:NAME=LAPDLE:1,LAPDCH=BPORT0-1-
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
MO already created (-159)
END OF OUTPUT FOR JOB 152
Application Guidelines:
The LAPDLE object must be always created before the corresponding LPDLM
object on the BSC side, otherwise the Abis Alignment is going to fail
A50016-G5100-B333-04-7619
Id:0900d8058059599e
505
LAPDLE
BS-4x / 82 II / 240 / 241 / 240XL commands
Example of Command Execution:
Create LAPDLE:NAME=LAPDLE:0,LAPDCH=2-2-FULL_64KB;
DELETE LAPDLE
DELETE LAPDLE
NAME=LAPDLE:0..10;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h LAPDLE h DELETE
LAPDLE
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the LAPDLE from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 158
PC Time&Date: 12:03:55 03/23/2005
NE Time&Date: 13:05:22 09/15/2004
USER NAME:
user_val1
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = NAME=LAPDLE:2;
ChangeInfo = deleted
END OF OUTPUT FOR JOB 158
JOB: 159
506
Id:0900d8058059599e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
LAPDLE
PC Time&Date: 12:04:03 03/23/2005
NE Time&Date: 13:05:35 09/15/2004
USER NAME:
user_val1
COMMAND:
Delete LAPDLE:NAME=LAPDLE:2;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 159
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
None.
Example of Command Execution:
Delete LAPDLE:NAME=LAPDLE:0;
GET LAPDLE
GET LAPDLE
NAME=LAPDLE:0..10 [,REQATTL=ALS, AST, AVS,
LAPDCH, OST, PRS, RELFUNCOBJ, STDBYST];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h LAPDLE h GET
LAPDLE
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the LAPDLE unit of the BTSE.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
LAPDCH
lapdChannel
OST
operationalState
A50016-G5100-B333-04-7619
Id:0900d8058059599e
507
LAPDLE
BS-4x / 82 II / 240 / 241 / 240XL commands
PRS
proceduralStatus
RELFUNCOBJ
STDBYST
relatedFuncObjects
standbyStatus
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 149
PC Time&Date: 12:02:04 03/23/2005
NE Time&Date: 13:03:39 09/15/2004
USER NAME:
user_val1
COMMAND:
Get LAPDLE:NAME=LAPDLE:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
lapdChannel =
BPORT = BPORT0
TSL = 17
SSL = FULL_64KB
operationalState = ENABLED
proceduralStatus = NULL
relatedFuncObjects =
standbyStatus = ColdStandBy
END OF OUTPUT FOR JOB 149
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
The value for the attribute relatedFuncObjects in LMT Phase 2 is "not configured"
Example of Command Execution:
Get LAPDLE:NAME=RACK:0,REQATTL=ALS&AST&AVS&LAPCH&
RELFUNCOBJ&OST&PRS&STBYST;
508
Id:0900d8058059599e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
RACK
RACK
The BS240/1 consists of a base rack with up to 8 TRXs. Optionally it can be connected
to two extension racks to reach up to 24 TRX. The BS240XL consists of a base rack with
up to 12 TRXs. Optionally it can be connected to an extension rack to reach up to 24
TRXs.
CREATE RACK
CREATE RACK
NAME=RACK:0..7 ,TYPRACK=;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h CREATE
RACK
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the object RACK together with its attributes to the BTSE data base.
Long Names:
NAME
Address of the managed object
TYPRACK
typeOfBtse
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further messagee indicates the result of the operation. An example of create
command is the following:
JOB: 230
PC Time&Date: 14:50:07 03/23/2005
NE Time&Date: 00:17:45 09/15/2004
USER NAME:
user_ NSN
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
A50016-G5100-B333-04-7619
Id:0900d805805959a0
509
RACK
BS-4x / 82 II / 240 / 241 / 240XL commands
name = RACK:1
ChangeInfo = created
END OF OUTPUT FOR JOB 230
JOB: 231
PC Time&Date: 14:50:08 03/23/2005
NE Time&Date: 00:17:46 09/15/2004
USER NAME:
user_ NSN
COMMAND:
Create RACK:NAME=RACK:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT Operation successful
END OF OUTPUT FOR JOB 231
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 232
PC Time&Date: 14:50:08 03/23/2005
NE Time&Date: 00:17:46 09/15/2004
USER NAME:
user_ NSN
COMMAND:
Create RACK:NAME=RACK:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
MO already created (-159)
END OF OUTPUT FOR JOB 232
Application Guidelines:
510
RACK:0 can never be created. It had to be set, with Set RACK as first command
If an other rack type for RACK:0 is create, you had to format the flash and had to
make a power on; e.g. if you have at coba in DB (rack0) racktype BS242 (pico) and
want a racktype 240XL at coba. You had to format the flash and had to make a
Id:0900d805805959a0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
RACK
power on at coba. With set rack or delete db this is not possible. (here you have different SW)
g The Create RACK command is no longer supported for BS240SWB, BS241SWB
and BS240XLSWB
Example of Command Execution:
Create RACK:NAME=RACK:1,TYPRACK=BS240;
DELETE RACK
DELETE RACK
NAME=RACK:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h DELETE
RACK
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the object RACK together with its attributes from the BTSE data
base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 233
PC Time&Date: 14:50:08 03/23/2005
NE Time&Date: 00:17:46 09/15/2004
USER NAME:
user_ NSN
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:1
A50016-G5100-B333-04-7619
Id:0900d805805959a0
511
RACK
BS-4x / 82 II / 240 / 241 / 240XL commands
ChangeInfo = deleted
END OF OUTPUT FOR JOB 233
JOB: 234
PC Time&Date: 14:50:08 03/23/2005
NE Time&Date: 00:17:46 09/15/2004
USER NAME:
user_ NSN
COMMAND:
Delete RACK:NAME=RACK:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 234
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
RACK:0 can never be deleted by DELETE command only using FORMAT FLASH
and power on
Example of Command Execution:
Delete RACK:NAME=RACK:1
The object can be deleted with format flash and power on.
GET RACK
GET RACK
NAME=RACK:0..7 [,REQATTL=ALS, AST, AVS, OST, PRS,
RELFUNCOBJ, TYPRACK];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h GET RACK
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes related to the specified RACK.
Long Names:
NAME
512
Address of the managed object
Id:0900d805805959a0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
RACK
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
TYPRACK
relatedFuncObjects
typeOfBtse
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 5
PC Time&Date: 12:03:10 03/23/2005
NE Time&Date: 12:01:00 09/15/2004
USER NAME:
user_ NSN
COMMAND:
Get RACK:NAME=RACK:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = MINOR
administrativeState = Unlocked
availabilityStatus = NULL
operationalState = ENABLED
proceduralStatus = NULL
relatedFuncObjects =
typeOfBtse = BS240XL
END OF OUTPUT FOR JOB 5
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
None.
A50016-G5100-B333-04-7619
Id:0900d805805959a0
513
RACK
BS-4x / 82 II / 240 / 241 / 240XL commands
Example of Command Execution:
Get RACK:NAME=RACK:0,REQATTL=ALS&AST&AVS&RELFUNCOBJ&OST&
PRS&TYPRACK;
LOCK RACK
LOCK RACK
NAME=RACK:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h LOCK RACK
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the object RACK.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 235
PC Time&Date: 14:50:08 03/23/2005
NE Time&Date: 00:17:46 09/15/2004
USER NAME:
user_ NSN
COMMAND:
Lock RACK:NAME=RACK:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 235
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
514
Id:0900d805805959a0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
RACK
JOB: 236
PC Time&Date: 14:50:08 03/23/2005
NE Time&Date: 00:17:46 09/15/2004
USER NAME:
user_ NSN
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:1
Administrative State = LOCKED
Notification Identifier = 147
END OF OUTPUT FOR JOB 236
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
RACK:0 can never be locked
Example of Command Execution:
Lock RACK:NAME=RACK:1;
SET RACK
SET RACK
NAME=RACK:0..7 [,TYPRACK=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h SET RACK
Applicability:
Phase 2.
Visibility level: 2.
Command Description:
This command is used to set the attributes of the specified RACK.
Long Names:
NAME
Address of the managed object
TYPRACK
typeOfBtse
System Responses:
Operation Completed
A50016-G5100-B333-04-7619
Id:0900d805805959a0
515
RACK
BS-4x / 82 II / 240 / 241 / 240XL commands
After command execution, a message of Changed Attribute Event Report is displayed.
A further message indicates the result of the operation. An example of set command is
the following:
JOB: 176
PC Time&Date: 12:05:36 03/23/2005
NE Time&Date: 13:07:12 09/15/2004
USER NAME:
user_ NSN
COMMAND:
Set RACK:NAME=RACK:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 176
Operation Failed
The specified attributes have not been set. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible.
Application Guidelines:
The attribute TYPRACK must be set. Otherwise the OMC is not able to identify the
BTSE
RACK:0 has to be set, otherwise no object can be created
RACK:0 cannot be changed, it has to be deleted by delete BTSEPDBFILE (e.g., if
you have a coba with rack BS240 and want a racktype 240XL you have to delete
dbfile (delete DB). Here you have the same SW)
g The Set RACK command is no longer supported for BS240SWB, BS241SWB and
BS240XLSWB
Example of Command Execution:
Set RACK:NAME=RACK:0,TYPRACK=BS240;
UNLOCK RACK
UNLOCK RACK
NAME=RACK:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h UNLOCK
RACK
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
516
Id:0900d805805959a0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
RACK
Command Description:
This command changes the administrative state of the object RACK.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 237
PC Time&Date: 14:50:08 03/23/2005
NE Time&Date: 00:17:46 09/15/2004
USER NAME:
user_ NSN
COMMAND:
Unlock RACK:NAME=RACK:1;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 237
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 238
PC Time&Date: 14:50:09 03/23/2005
NE Time&Date: 00:17:47 09/15/2004
USER NAME:
user_ NSN
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:1
A50016-G5100-B333-04-7619
Id:0900d805805959a0
517
RACK
BS-4x / 82 II / 240 / 241 / 240XL commands
Administrative State = UNLOCKED
Notification Identifier = 321
END OF OUTPUT FOR JOB 237
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
None.
Example of Command Execution:
Unlock RACK:NAME=RACK:0;
518
Id:0900d805805959a0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
REMINV
REMINV
The REMINV (Remote Inventory) object manages the BTSE local Inventory Data Table
(IDT) in case of installation of new hardware objects or replacement of already existing
hardware objects.
DNLIDFD REMINV
DNLIDFD REMINV
NAME=REMINV:0..0 [,SRCDIR=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h REMINV h DNLIDFD
REMINV
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command executes the download of the NOB file (containing nob_RIUs of the IDF)
from the LMT hard disk to the BTSE flash EPROMs.
Long Names:
NAME
Address of the managed object
SRCDIR
sourceDir
System Responses:
Operation Completed
After command execution, a further message indicates the result of the operation. An
example of dnlidfd command is the following:
JOB: 155
PC Time&Date: 12:03:15 03/23/2005
NE Time&date: 0:00:00 00/00/0
USER NAME:
user_ NSN
COMMAND:
Dnlidfd REMINV:NAME=REMINV:0,SRCDIR="C:\labuser\BsPlus";
SW RELEASE:
N.A.
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 155
Operation Failed
None.
A50016-G5100-B333-04-7619
Id:0900d805805959a2
519
REMINV
BS-4x / 82 II / 240 / 241 / 240XL commands
Application Guidelines:
This file is to be created previously using the "IDF-Editor". The name for BTSE is fix
"BTS_NRIU".
Example of Command Execution:
Dnlidfd REMINV:SRCDIR="C:\Programme\IdfEditor|\dnload";
UPLLIDF REMINV
UPLLIDF REMINV
NAME=REMINV:0..0 [,DESTDIR=] [,FILE=] ,OVERWRITE=;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h REMINV h UPLLIDF
REMINV
Applicability:
Phase 1 and Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command executes the uploading of the IDF (Inventory Data File) from the BTSE
flash EPROMs to the LMT hard disk.
Long Names:
NAME
Address of the managed object
DESTDIR
destinationDir
FILE
file
OVERWRITE
Overwrite
System Responses:
Operation Completed
After command execution, a further message indicates the result of the operation. An
example of upllidf command is the following:
JOB: 156
PC Time&Date: 12:03:18 03/23/2005
NE Time&date: 0:00:00 00/00/0
USER NAME:
user_ NSN
COMMAND:
Upllidf REMINV:NAME=REMINV:0,OVERWRITE=YES;
SW RELEASE:
N.A.
COMMAND RESULT: Operation successful
Uploading File: BTSE.IDT
520
Id:0900d805805959a2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
REMINV
To: BTSE.IDT
On Directory: ..\Idf\Upload
END OF OUTPUT FOR JOB 156
JOB: 157
PC Time&Date: 12:03:19 03/23/2005
NE Time&date: 00:00:00 00/00/0
USER NAME:
user_ NSN
COMMAND:
Upllidf REMINV:NAME=REMINV:0,OVERWRITE=YES;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Upload End: File BTSE.IDT Transfer Completed
END OF OUTPUT FOR JOB 157
Operation Failed
None.
Application Guidelines:
The offline tool "IDF-Editor" is used to display and modify the uploaded IDT. It is
used also for converting the IDT into an IDF or to extract the NOB file
The default value of FILE is BTSE.IDT
Example of Command Execution:
Uplidfd REMINV:DESTDIR="c:\rem_inve",FILE="bts_inv.idt",OVERWRITE=YES;
A50016-G5100-B333-04-7619
Id:0900d805805959a2
521
SOFTWARE-MANAGEMENT
BS-4x / 82 II / 240 / 241 / 240XL commands
SOFTWARE-MANAGEMENT
The SOFTWARE-MANAGEMENT object provide the functionality to execute BSS software management and to administrate the BTSE file system.
DNLALLEXE SOFTWARE-MANAGEMENT
DNLALLEXE
SRCPATH= ,OVERWRITE=;
SOFTWARE-MANAGEMENT
Command Tree:
MANAGED-ELEMENT h SOFTWARE-MANAGEMENT h DNLALLEXE
SOFTWARE-MANAGEMENT
Applicability:
Phase 1 and Phase 2.
Visibility level: 0.
Command Description:
This command executes the software downloading of the BTS-SW from the LMT PC
hard disk to the COBA.
Long Names:
IDSOFTWARE-MANAGEMENT
SRCPATH
srcpath
OVERWRITE
Overwrite
Address of the managed object
System Responses:
Operation Completed
Download START. After command execution, a further message indicates the result of
the operation. An example of dnlallexe command is the following:
JOB: 175
PC Time&Date: 12:05:17 03/23/2005
NE Time&date: 0:00:00 00/00/0
USER NAME:
User_NSN
COMMAND:
DNLALLEXE:SRCPATH="<disk partition>:\<installation directory>\
hs031785\HS011722.SWL",OVERWRITE=YES;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Downloading File: HS011726.SWL:01-04-17-01-26-51_05-02-23
522
Id:0900d805805959a4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
SOFTWARE-MANAGEMENT
Version: 02-08-01-01-00-27_04-11-19
END OF OUTPUT FOR JOB 175
Operation Failed
= (invalid SW-Version, defective SW)
Application Guidelines:
If the incorrect SW version is given, the system will reject the command
The SWLoadSafety will not be overwritten
In Phase 1 this command is followed by a forced download
In Phase 2 the command is followed by a forced download if the SwVersion is identical to the currentSWLoad
Recent BTS SW productions expect 64M RAM, the SW doesn't work with old
CESCOBA
Example of Command Execution:
Dnlallexe:SRCPATH="c:\path\HS011722.SWL", OVERWRITE= YES;
UPLBTSLOG SOFTWARE-MANAGEMENT
UPLBTSLOG
FILETYPE= ,DESTDIR= ,FILE= [,ENTRIES=] ,OVERSOFTWARE-MANAGE- WRITE=;
MENT
Command Tree:
MANAGED-ELEMENT h SOFTWARE-MANAGEMENT h UPLBTSLOG
SOFTWARE-MANAGEMENT
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
The uUser_NSNe of this command is reserved to the R&D and should be used only
under R&D request.
Long Names:
IDSOFTWARE-MANAGEMENT
FILETYPE
FileType
DESTDIR
destinationDir
FILE
file
ENTRIES
entries
OVERWRITE
Overwrite
Address of the managed object
System Responses:
Operation Completed
A50016-G5100-B333-04-7619
Id:0900d805805959a4
523
SOFTWARE-MANAGEMENT
BS-4x / 82 II / 240 / 241 / 240XL commands
After command execution, a further message indicates the result of the operation. An
example of uplbtslog command is the following:
JOB: 177
PC Time&Date: 12:06:04 03/23/2005
NE Time&date: 0:00:00 00/00/0
USER NAME:
User_NSN
COMMAND:
WRITE=YES;
UPLBTSLOG:DESTDIR="D:\DocumentBtsplus",FILE="240xl",OVER-
SW RELEASE:
N.A.
COMMAND RESULT: Operation successful
Uploading File: 240xl
To: 240xl
On Directory: D:\DocumentBtsplus
END OF OUTPUT FOR JOB 177
JOB: 178
PC Time&Date: 12:06:25 03/23/2005
NE Time&date: 00:00:00 00/00/0
USER NAME:
User_NSN
COMMAND:
WRITE=YES;
UPLBTSLOG:DESTDIR="D:\DocumentBtsplus",FILE="240xl",OVER-
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Uploading File 240xl:
100 packets received
END OF OUTPUT FOR JOB 178
Operation Failed
None.
Application Guidelines:
None.
524
Id:0900d805805959a4
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
SOFTWARE-MANAGEMENT
Example of Command Execution:
The execution of this command is reserved to the R&D and should be executed only
under R&D request.
A50016-G5100-B333-04-7619
Id:0900d805805959a4
525
SYNCBTSE
BS-4x / 82 II / 240 / 241 / 240XL commands
SYNCBTSE
The SYNCBTSE object which holds operator configurable parameters and indicates the
synchronization state and accuracy. This is sufficient to maintain configuration and
states, so no further modeling of the external GPS equipment is necessary.
GET SYNCBTSE
GET SYNCBTSE
NAME=SYNCBTSE:0..0 [,REQATTL=ALS, AST, AVS,
CLKACC, MPHERR, MRSYNCT, OST, PRS, RELFUNCOBJ, SBPRT, SYNCSRC, SYNCSTAT];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h SYNCBTSE h GET
SYNCBTSE
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the SYNCBTSE of the BTSE.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
CLKACC
clockAccuracy
MPHERR
maxPhaseError(microsec)
MRSYNCT
maxResyncTime(min)
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
SBPRT
syncBport
SYNCSRC
syncSource
SYNCSTAT
syncState
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 7
526
Id:0900d805805959a6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
SYNCBTSE
PC Time&Date: 16:24:35 03/23/2005
NE Time&Date: 16:22:29 09/15/2004
USER NAME:
User_NSN
COMMAND:
Get SYNCBTSE:NAME=SYNCBTSE:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
clockAccuracy = high
maxPhaseError(microsec) = 1.5
maxResyncTime(min) = 180
operationalState = ENABLED
proceduralStatus = NULL
relatedFuncObjects =
syncSource = abis
syncState = abis
END OF OUTPUT FOR JOB 7
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
None.
Example of Command Execution:
Get SYNCBTSE:NAME=SYNCBTSE:0,REQATTL=ALS&AST&AVS&BCPBL&
CLKACC&MPHERR&MRSYNCT&OST&PRS&RELFUNCOBJ&SYNCSRC&
SYNCSTAT;
GETTEST SYNCBTSE
GETTEST SYNCBTSE
NAME=SYNCBTSE:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h SYNCBTSE h
GETTEST SYNCBTSE
A50016-G5100-B333-04-7619
Id:0900d805805959a6
527
SYNCBTSE
BS-4x / 82 II / 240 / 241 / 240XL commands
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the SYNCBTSE test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
JOB: 300
PC Time&Date: 14:50:17 03/23/2005
NE Time&Date: 00:17:55 09/15/2004
USER NAME:
User_NSN
COMMAND:
Gettest SYNCBTSE:NAME=SYNCBTSE:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = SYNCBTSE:0
testMonitor =
phaseId = PreliminaryTestsSYNCBTSE
phaseStatus = Running
phaseId = CheckAlarmStatusSYNCBTSE
phaseStatus = Waiting
phaseId = EndTestSYNCBTSE
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
END OF OUTPUT FOR JOB 300
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
528
Id:0900d805805959a6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
testMonitor
phaseId =
phaseStatus =
SYNCBTSE
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest SYNCBTSE:NAME=SYNCBTSE:0,REQATTL=MORT&TESTMON&
TESTOUT&TESTST;
LOCK SYNCBTSE
LOCK SYNCBTSE
NAME=SYNCBTSE:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h SYNCBTSE h LOCK
SYNCBTSE
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the SYNCBTSE of the BTSE.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
A50016-G5100-B333-04-7619
Id:0900d805805959a6
529
SYNCBTSE
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 8
PC Time&Date: 16:24:42 03/23/2005
NE Time&Date: 16:22:36 09/15/2004
USER NAME:
User_NSN
COMMAND:
Lock SYNCBTSE:NAME=SYNCBTSE:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 8
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 9
PC Time&Date: 16:24:42 03/23/2005
NE Time&Date: 16:22:36 09/15/2004
USER NAME:
User_NSN
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = SYNCBTSE:0
Administrative State = LOCKED
Notification Identifier = 461
END OF OUTPUT FOR JOB 9
Operation Failed
The specified change of administrative state has not been performed (e.g. the object is
redundant and its spare copy is disabled or already locked, a subordinate resource
cannot go into disabled state with "dependency" availability status).
530
Id:0900d805805959a6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
SYNCBTSE
Application Guidelines:
Lock of SYNCBTSE (= SET administrativeState to locked) is rejected if syncSource =
ext_1pps_only.
Example of Command Execution:
Lock SYNCBTSE:NAME=SYNCBTSE:0;
PERFTEST SYNCBTSE
PERFTEST SYNCBTSE NAME=SYNCBTSE:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h SYNCBTSE h
PERFTEST SYNCBTSE
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in SYNCBTSE.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSE.
JOB: 240
PC Time&Date: 14:50:09 03/23/2005
NE Time&Date: 00:17:47 09/15/2004
USER NAME:
User_NSN
COMMAND:
Perftest SYNCBTSE:NAME=SYNCBTSE:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = SYNCBTSE
tO = BTSETEST:1
END OF OUTPUT FOR JOB 240
A50016-G5100-B333-04-7619
Id:0900d805805959a6
531
SYNCBTSE
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 241
PC Time&Date: 14:50:09 03/23/2005
NE Time&Date: 00:17:47 09/15/2004
USER NAME:
User_NSN
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:1
ChangeInfo = created
END OF OUTPUT FOR JOB 241
JOB: 242
PC Time&Date: 14:50:12 03/23/2005
NE Time&Date: 00:17:51 09/15/2004
USER NAME:
User_NSN
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = SYNCBTSE:0
Operational State = ENABLED
Availability Status = NULL_value
Notification Identifier = 143
END OF OUTPUT FOR JOB 242
JOB: 243
PC Time&Date: 14:50:12 03/23/2005
NE Time&Date: 00:17:51 09/15/2004
USER NAME:
532
User_NSN
Id:0900d805805959a6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
SW RELEASE:
SYNCBTSE
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:1
testOutcome = PASSED
testTermination = Normal
MOT = SYNCBTSE:0
executedPhases =
PreliminaryTestsSYNCBTSE
CheckAlarmStatusSYNCBTSE
EndTestSYNCBTSE
END OF OUTPUT FOR JOB 243
JOB: 244
PC Time&Date: 14:50:09 03/23/2005
NE Time&Date: 00:17:47 09/15/2004
USER NAME:
User_NSN
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:1
ChangeInfo = deleted
END OF OUTPUT FOR JOB 244
The test results will be displayed at the end of the test phases.
Result TEST:
name =
TEST:<n>
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
A50016-G5100-B333-04-7619
Id:0900d805805959a6
all the test phases are successfully
performed.
533
SYNCBTSE
BS-4x / 82 II / 240 / 241 / 240XL commands
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: Message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
None.
Example of Command Execution:
Perftest SYNCBTSE:NAME=SYNCBTSE:0;
SET SYNCBTSE
SET SYNCBTSE
534
NAME=SYNCBTSE:0..0 [,MPHERR=] [,MRSYNCT=]
[,SYNCSRC=];
Id:0900d805805959a6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
SYNCBTSE
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h SYNCBTSE h SET
SYNCBTSE
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command sets the attributes for the mapping of the SYNCBTSE.
Long Names:
NAME
Address of the managed object
MPHERR
maxPhaseError(microsec)
MRSYNCT
maxResyncTime(min)
SYNCSRC
syncSource
System Responses:
Operation Completed
The specified attribute has been set. In addition, a Changed Attribute Event Report indicates that the command has been successfully executed:
JOB: 20
PC Time&Date: 12:06:33 03/23/2005
NE Time&Date: 12:04:23 09/15/2004
USER NAME:
User_NSN
COMMAND:
SRC=abis;
Set SYNCBTSE:NAME=SYNCBTSE:0,MPHERR=1.5,SYNC-
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
maxPhaseError(microsec) = 1.5
syncSource = abis
END OF OUTPUT FOR JOB 20
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible.
A50016-G5100-B333-04-7619
Id:0900d805805959a6
535
SYNCBTSE
BS-4x / 82 II / 240 / 241 / 240XL commands
Application Guidelines:
Setting syncSource to "ext_1pps_only" is rejected for COBA different than COBA4P12
version 2 or CESCOBA.
Setting syncSource to "ext_1pps_only" is rejected if administrativeState of SYNCBTSE
is locked.
Example of Command Execution:
Set SYNCBTSE:NAME=SYNCBTSE:0,MPHERR=1.5,MRSYNCT=200,
SYNCSRC=extGPS;
STOPTEST SYNCBTSE
STOPTEST SYNCBTSE NAME=SYNCBTSE:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h SYNCBTSE h
STOPTEST SYNCBTSE
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
...
.
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
failedPhases
536
Id:0900d805805959a6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
SYNCBTSE
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
phaseId =
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
Application Guidelines:
None.
Example of Command Execution:
Stoptest SYNCBTSE:NAME=SYNCBTSE:0;
UNLOCK SYNCBTSE
UNLOCK SYNCBTSE
NAME=SYNCBTSE:0..0;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h SYNCBTSE h
UNLOCK SYNCBTSE
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the SYNCBTSE to the BTSE.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 10
PC Time&Date: 16:24:48 03/23/2005
NE Time&Date: 16:22:42 09/15/2004
USER NAME:
A50016-G5100-B333-04-7619
User_NSN
Id:0900d805805959a6
537
SYNCBTSE
BS-4x / 82 II / 240 / 241 / 240XL commands
COMMAND:
Unlock SYNCBTSE:NAME=SYNCBTSE:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 10
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 11
PC Time&Date: 16:24:48 03/23/2005
NE Time&Date: 16:22:42 09/15/2004
USER NAME:
User_NSN
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = SYNCBTSE:0
Administrative State = UNLOCKED
Notification Identifier = 462
END OF OUTPUT FOR JOB 11
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
None.
Example of Command Execution:
Unlock SYNCBTSE:NAME=SYNCBTSE:0;
538
Id:0900d805805959a6
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
TMA
TMA
The TMA object represents the tower mounted amplifier.
CREATE TMA
CREATE TMA
NAME=RACK:0..7/TMA:0..15;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h
CREATE TMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command adds the TMA (Tower Mounted Amplifier) to the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 5
PC Time&Date: 16:24:23 03/23/2005
NE Time&Date: 16:22:17 09/15/2004
USER NAME:
User_Chris
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/TMA:0
ChangeInfo = created
END OF OUTPUT FOR JOB 5
A50016-G5100-B333-04-7619
Id:0900d805805959a8
539
TMA
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 6
PC Time&Date: 16:24:23 03/23/2005
NE Time&Date: 16:22:17 09/15/2004
USER NAME:
User_Chris
COMMAND:
Create TMA:NAME=RACK:0/TMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 6
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 80
PC Time&Date: 16:37:54 03/23/2005
NE Time&Date: 16:35:47 09/15/2004
USER NAME:
User_Chris
COMMAND:
Create TMA:NAME=RACK:0/TMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
Object instance unknown (-9)
END OF OUTPUT FOR JOB 80
Application Guidelines:
The DUAMCO/DIAMCO amplifier has two different operation modes which can be
selected by e.g. DIP switches. In case a TMA is used the DUAMCO/DIAMCO must
be configured in the MUCO mode. If no TMA is used the DUAMCO/DIAMCO must
be configured in the AMCO mode
As in the MUCO mode the gain is reduced to about 0 dB, the exact gain of the
DUAMCO/DIAMCO to compensate the cable losses must be adjusted once during
the installation of the BTSE by the service personnel
Example of Command Execution:
Create TMA:NAME=RACK:0/TMA:0;
540
Id:0900d805805959a8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
TMA
DELETE TMA
DELETE TMA
NAME=RACK:0..7/TMA:0..15;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h
DELETE TMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the TMA (Tower Mounted Amplifier) to the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 14
PC Time&Date: 16:24:59 03/23/2005
NE Time&Date: 16:22:53 09/15/2004
USER NAME:
User_Chris
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = RACK:0/TMA:0
ChangeInfo = deleted
END OF OUTPUT FOR JOB 14
JOB: 15
PC Time&Date: 16:24:59 03/23/2005
NE Time&Date: 16:22:53 09/15/2004
A50016-G5100-B333-04-7619
Id:0900d805805959a8
541
TMA
BS-4x / 82 II / 240 / 241 / 240XL commands
USER NAME:
User_Chris
COMMAND:
Delete TMA:NAME=RACK:0/TMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 15
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
TMA must be locked in phase 3 before deletion
If a DULNA or DILNA with attribute "InaPredecessor" containing a TMA should be
deleted, then the tMA contained the attribute has to be deleted before
Example of Command Execution:
Delete TMA:NAME=RACK:0/TMA:0;
GET TMA
GET TMA
NAME=RACK:0..7/TMA:0..15 [,REQATTL=ALS, AST, AVS,
OST, PRS, RELFUNCOBJ, PRDINF, ANTMN, ANTSN,
BND<x>, BMWD<x>, GN<x>, SUBUNT, RXBMINF,
RXBMAXF, TXBMINF, TXBMAXF, MAXGN, MINGN, GNR,
INSD, INSID, BTSID, SCID, ANTB, MTLT];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h GET
TMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of TMA.
Long Names:
542
NAME
Address of the managed object
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
OST
operationalState
Id:0900d805805959a8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
PRS
TMA
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
PRDINF
productInfo(prodNbr_SN_HwVer_SwVer)
ANTMN
antennaModelNumber
ANTSN
antennaSerialNumber
BND<x>
band<x>
BMWD<x>
beamWidth<x>(degree)
GN<x>
gain0(dBi*1<x>)
SUBUNT
subUnitType
RXBMINF
rxBandMinFreq(kHz*100)
RXBMAXF
rxBandMaxFreq(kHz*100)
TXBMINF
txBandMinFreq(kHz*100)
TXBMAXF
txBandMaxFreq(kHz*100)
MAXGN
maxGain(dB*4)
MINGN
minGain(dB*4)
GNR
gainResolution(dB*4)
INSD
installDate
INSID
installerId
BTSID
baseStationId
SCID
sectorId
ANTB
antennaBearing(degree)
MTLT
mechanicalTilt(degree*10)
System Responses:
Operation Completed
None.
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
GET TMA: NAME=RACK:0/TMA:0, REQATTL=ALS&AST&AVS&OST&PRS&RELFUNCOBJ& ANTMN& ANTSN& BND0& BMWD0& GN0& BND1& BMWD1& GN1&
BND2& BMWD2& GN2& BND3& BMWD3& GN3& SUBUNT& RXBMINF& RXBMAXF&
TXBMINF& TXBMAXF& MAXGN& MINGN& GNR& INSD& INSID& BTSID& SCID&
ANTB& MTLT;
GET TMA PRODUCTINFO
GET TMA PRODUCTINFO
A50016-G5100-B333-04-7619
NAME=RACK:0..7/TMA:0..15;
Id:0900d805805959a8
543
TMA
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h GET
TMA PRODUCTINFO
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command shows all the specific information related to TMA productinfo.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of get
product info command is the following:
JOB: 90
PC Time&Date: 15.05.2008 10:09:30 +02:00
NE Time&Date: 01.01.1990 00:05:05 +00:00
USER NAME:
User_Chris
COMMAND:
Get TMA PRODUCTINFO:NAME=RACK:0/TMA:0;
SW RELEASE:
01-04-19-01-01-MB_08-05-13
COMMAND RESULT: Operation successful
productInfo(prodNbr_SN_HwVer_SwVer) = "CS7299111.02; X9081012052;
HW_V_A06; FW_V02.02.00_BL_V02.02.00"
END OF OUTPUT FOR JOB 90
Binary Command
544
Id:0900d805805959a8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
TMA
0d 00 80 ff 12 02 81 81 ab 1a 00 00 1a 01 a1
Binary Response
4a 00 80 00 02 12 01 82 ab 1a 00 00 a1 3e 43 53 37 32 39 39
31 31 31 2e 30 32 3b 20 58 39 30 38 31 30 31 32 30 35 32 3b
20 48 57 5f 56 5f 41 30 36 3b 20 46 57 5f 56 30 32 2e 30 32
2e 30 30 5f 42 4c 5f 56 30 32 2e 30 32 2e 30 30
Operation Failed
None.
Application Guidelines:
None.
Example of Command Execution:
GET TMA PRODUCTINFO: NAME=RACK:0TMA:0, REQATTL= PRDINF;
GETTEST TMA
GETTEST TMA
NAME=RACK:0..7/TMA:0..15;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h
GETTEST TMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the TMA test.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of gettest command is the
following:
A50016-G5100-B333-04-7619
Id:0900d805805959a8
545
TMA
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 239
PC Time&Date: 14:50:09 03/23/2005
NE Time&Date: 00:17:47 09/15/2004
USER NAME:
User_Chris
COMMAND:
Gettest TMA:NAME=RACK:0/TMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/TMA:0
testMonitor =
phaseId = PreliminaryTestsTma
phaseStatus = Running
phaseId = CheckAlarmStatusTma
phaseStatus = Waiting
phaseId = EndTestTma
phaseStatus = Waiting
testOutcome = INCONCLUSIVE
testState = INITIALIZING
END OF OUTPUT FOR JOB 239
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
testMonitor
phaseId =
phaseStatus =
it is a list of all test phases related to the
selected object; for each phase the
related phaseStatus is provided (Passed,
Failed, Running or Waiting).
phaseId =
phaseStatus =
...
...
testOutcome
546
It represents the test result: it can be
Inconclusive (if the phases already
executed were successful) or Fail (if at
least one of the executed phases failed).
Id:0900d805805959a8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
TMA
testState = Testing
It can assume one of the following values:
not_initialized, idle, initializing, suspended, testing, terminating and disabled.
Application Guidelines:
None.
Example of Command Execution:
Gettest TMA:NAME=RACK:0/TMA:0;
LOCK TMA
LOCK TMA
NAME=RACK:0..7/TMA:0..15;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h
LOCK TMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the TMA (Tower Mounted Amplifier)
of the BTSE.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 8
PC Time&Date: 16:24:42 03/23/2005
NE Time&Date: 16:22:36 09/15/2004
USER NAME:
User_Chris
COMMAND:
Lock TMA:NAME=RACK:0/TMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 8
A50016-G5100-B333-04-7619
Id:0900d805805959a8
547
TMA
BS-4x / 82 II / 240 / 241 / 240XL commands
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 9
PC Time&Date: 16:24:42 03/23/2005
NE Time&Date: 16:22:36 09/15/2004
USER NAME:
User_Chris
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/TMA:0
Administrative State = LOCKED
Notification Identifier = 461
END OF OUTPUT FOR JOB 9
Operation Failed
The specified change of administrative state has not been performed (e.g. the object is
redundant and its spare copy is disabled or already locked, a subordinate resource
cannot go into disabled state with "dependency" availability status).
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Lock TMA:NAME=RACK:0/TMA:0;
PERFTEST TMA
PERFTEST TMA
NAME=RACK:0..7/TMA:0..15;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h
PERFTEST TMA
548
Id:0900d805805959a8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
TMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to start an asynchronous test in TMA.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
Test configuration has been set and the specified test has been started. The System
response will not be addressed to the MOT but to the object BTSE.
JOB: 240
PC Time&Date: 14:50:09 03/23/2005
NE Time&Date: 00:17:47 09/15/2004
USER NAME:
User_Chris
COMMAND:
Perftest TMA:NAME=RACK:0/TMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
MOT = RACK:0/TMA:0
tO = BTSETEST:1
END OF OUTPUT FOR JOB 240
JOB: 241
PC Time&Date: 14:50:09 03/23/2005
NE Time&Date: 00:17:47 09/15/2004
USER NAME:
User_Chris
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
A50016-G5100-B333-04-7619
Id:0900d805805959a8
549
TMA
BS-4x / 82 II / 240 / 241 / 240XL commands
name = BTSETEST:1
ChangeInfo = created
END OF OUTPUT FOR JOB 241
JOB: 242
PC Time&Date: 14:50:12 03/23/2005
NE Time&Date: 00:17:51 09/15/2004
USER NAME:
User_Chris
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = RACK:0/TMA:0
Operational State = ENABLED
Availability Status = NULL_value
Notification Identifier = 143
END OF OUTPUT FOR JOB 242
JOB: 243
PC Time&Date: 14:50:12 03/23/2005
NE Time&Date: 00:17:51 09/15/2004
USER NAME:
User_Chris
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
Test Report:
name = BTSETEST:1
testOutcome = PASSED
testTermination = Normal
MOT = RACK:0/TMA:0
executedPhases =
PreliminaryTestsTma
550
Id:0900d805805959a8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
TMA
CheckAlarmStatusTma
EndTestTma
END OF OUTPUT FOR JOB 243
JOB: 244
PC Time&Date: 14:50:09 03/23/2005
NE Time&Date: 00:17:47 09/15/2004
USER NAME:
User_Chris
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = BTSETEST:1
ChangeInfo = deleted
END OF OUTPUT FOR JOB 244
The test results will be displayed at the end of the test phases.
Result TEST:
name =
TEST:<n>
testOutcome =
This field represents the test result; one of the following values can be displayed:
Pass
all the test phases are successfully
performed.
Inconclusive
the test is aborted by the system or
the test is terminated by the operator.
Fail
if at least one of the executed phases
fail.
mOts =
It is the identifier of the hardware object under test.
testTermination =
It specifies how the test is terminated, it can assume
the following values:
Normal
all the test phases are performed.
Abort
the test is aborted by system.
Cancel
the test is terminated by operator.
executedPhases
A50016-G5100-B333-04-7619
Id:0900d805805959a8
551
TMA
BS-4x / 82 II / 240 / 241 / 240XL commands
phaseId =
additionalWords =
....
It represents the list of the executed test phases (in
case of successful test result, all the test phases will
be listed).
failedPhases
phaseId =
It represents the list of the failed test phase; additional information is provided for each phase.
phaseId =
....
skippedPhases
phaseId =
It represents the list of the skipped phases; they are
displayed only for test stopped during it execution.
phaseId =
....
poprosedRepair Action
=
A list of most probable fail probable causes is shown
(max four messages)
Operation Failed
This NACK-message occurs in the following cases: Message cannot be performed, test
not supported, capacity restrictions, physical configuration cannot be performed, object
not locked.
Application Guidelines:
In phase 3 MO must be locked previous to the command execution
Example of Command Execution:
Perftest TMA:NAME=RACK:0/TMA:0;
STOPTEST TMA
STOPTEST TMA
NAME=RACK:0..7/TMA:0..15;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h
STOPTEST TMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command is used to stop a diagnostic previously started.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
552
Id:0900d805805959a8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
TMA
Test has been stopped. The System Responses will not be addressed to the MOT but
to the object BTSEP.
Result TEST:
name =
TEST:<n>
testOutcome =
inconclusive
mOts =
It is the identifier of the hardware object under test.
testTermination =
Cancel
executedPhases
phaseId =
It represents the list of the executed test phases; the
list is not shown for test in the waiting list (queued).
...
.
failedPhases
phaseId =
It represents the list of the failed test phase;
phaseId =
additional information is provided for each phase.
....
skippedPhases
phaseId =
It represents the list of the skipped phases;the list is
not shown for test in the waiting list (queued).
phaseId =
Operation Failed
Test has not been stopped. This NACK-message can occur when the specified test is
not running or in case of test which cannot be stopped.
Application Guidelines:
None.
Example of Command Execution:
Stoptest TMA:NAME=RACK:0/TMA:0;
UNLOCK TMA
UNLOCK TMA
NAME=RACK:0..7/TMA:0..15;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h RACK h TMA h
UNLOCK TMA
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
A50016-G5100-B333-04-7619
Id:0900d805805959a8
553
TMA
BS-4x / 82 II / 240 / 241 / 240XL commands
Command Description:
This command changes the administrative state of the TMA (Tower Mounted Amplifier)
to the BTSE.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 10
PC Time&Date: 16:24:48 03/23/2005
NE Time&Date: 16:22:42 09/15/2004
USER NAME:
User_Chris
COMMAND:
Unlock TMA:NAME=RACK:0/TMA:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Unlocked
END OF OUTPUT FOR JOB 10
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 11
PC Time&Date: 16:24:48 03/23/2005
NE Time&Date: 16:22:42 09/15/2004
USER NAME:
User_Chris
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
554
Id:0900d805805959a8
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
TMA
NAME = RACK:0/TMA:0
Administrative State = UNLOCKED
Notification Identifier = 462
END OF OUTPUT FOR JOB 11
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
While a Frequency Redefinition procedure is ongoing, the lock/unlock of all HMO's
actually related to a TRX is forbidden because that could lead to minor SELIC problem
or major SELIC problem alarms.
Example of Command Execution:
Unlock TMA:NAME=RACK:0/TMA:0;
A50016-G5100-B333-04-7619
Id:0900d805805959a8
555
TRX
BS-4x / 82 II / 240 / 241 / 240XL commands
TRX
The TRX object locates the transceivers connected to a certain BSC.
GET TRX
GET TRX
NAME=BTS:0..11/TRX:0..23 [,REQATTL=ABISCH,
ANTHOPHW, AST, AVS, DLTESTFREQ, DMACFHSYID,
MOEC, OST, PWRRED, RADIOMG, RADIOMR, TEI, TESTMODE, TESTPWRRED, TRXAREA, TRXCPBL, TRXFREQ,
TRXMD];
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h BTS h TRX h GET
TRX
Applicability:
Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the specified Transceiver.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
ABISCH
abisChannel
ANTHOPHW
antennaHoppingHw
AST
administrativeState
AVS
availabilityStatus
DLTESTFREQ
dlTestFrequency
DMACFHSYID
dmaCFHSyId
MOEC
memberOfEmergencyConfig
OST
operationalState
PWRRED
txPwrMaxReduction(*-2dB)
RADIOMG
radioMeasGran
RADIOMR
radioMeasRep
TEI
tei
TESTMODE
enableTestMode
TESTPWRRED
556
testPowerReduction
TRXAREA
trxArea
TRXCPBL
trxCapability
TRXFREQ
carrierFrequency
TRXMD
trxMode
Id:0900d805805959ab
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
TRX
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 18
PC Time&Date: 11:33:24 03/23/2005
NE Time&Date: 11:31:14 09/15/2004
USER NAME:
User_Christian
COMMAND:
Get TRX:NAME=BTS:0/TRX:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
abisChannel =
BPORT = 0
TSL = 1
SSL = NOT_USED
antennaHoppingHw =
administrativeState = Unlocked
availabilityStatus = Dependency
dlTestFrequency = NONE
enableTestMode = NONE
memberOfEmergencyConfig = TRUE
operationalState = DISABLED
txPwrMaxReduction(*-2dB) = 6
radioMeasGran = 1
radioMeasRep = ON
trxArea = NONE
carrierFrequency = 21
tei = 1
testPowerReduction = NONE
trxCapability = UNKNOWN
trxMode = GSM
END OF OUTPUT FOR JOB 18
Operation Failed
A50016-G5100-B333-04-7619
Id:0900d805805959ab
557
TRX
BS-4x / 82 II / 240 / 241 / 240XL commands
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
The TRX attribute trxCapability reflects the type of CU (GSM or EDGE) which is allocated to the TRX. If no CU isallocated, the attribute is set to "none". This static
assignment is not reasonable, because even if the TRX is disabled a CU may be still
allocated to the TRX (e.g. faulty combiner equipment)
Example of Command Execution:
Get TRX:NAME=BTS:0/TRX:0,REQATTL=ABISCH &ANTHOPHW &AST &AVS &DLTESTFREQ &DMACFHSYID &MOEC &OST &PWRRED &RADIOMG &RADIOMR &TEI
&TESTMODE &TESTPWRRED &TRXAREA &TRXCPBL &TRXFREQ &TRXMD;
GETRELATIONSHIP TRX
GETRELATIONSHIP
TRX
NAME=BTS:0..11/TRX:0..23;
Command Tree:
MANAGED-ELEMENT h BSS-FUNCTIONAL h BTSM h BTS h TRX h
GETRELATIONSHIP TRX
Applicability:
Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of the specified Transceiver.
Long Names:
NAME
Address of the managed object
REQATTL
Required attribute list
System Responses:
Operation Completed
A message indicates the result of the operation. An example of getrelationship
command is the following:
JOB: 161
PC Time&Date: 12:04:08 03/23/2005
NE Time&Date: 13:05:43 09/15/2004
USER NAME:
User_Christian
COMMAND:
Getrelationship TRX:NAME=BTS:0/TRX:0;
SW RELEASE:
558
01-04-17-01-26-51_05-02-23
Id:0900d805805959ab
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
TRX
COMMAND RESULT: Operation successful
relatedEquipObjects =
RACK:0/COBA:0
RACK:0/CU:3
RACK:0/DUVSWR:3
RACK:0/DULNA:2
RACK:0/TMA:2
RACK:0/DUDCTMA:2
RACK:0/DULNA:3
RACK:0/TMA:3
RACK:0/DUDCTMA:3
END OF OUTPUT FOR JOB 161
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
None.
Example of Command Execution:
Getrelationship TRX:NAME=BTS:0/TRX:0;
A50016-G5100-B333-04-7619
Id:0900d805805959ab
559
XCONNECT
BS-4x / 82 II / 240 / 241 / 240XL commands
XCONNECT
The XCONNECT object represents an hardware BTSE object that enables the crossconnection between PCM timeslots of different ports with a BTSE.
CREATE XCONNECT
CREATE XCONNECT
NAME=XCONNECT:0..7 [,MPTSLXX=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h XCONNECT h
CREATE XCONNECT
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command provides the XCONNECT (Multidrop-Star CrossConnect) of 64Kbit/s
timeslots and additionally a mapping of the timeslot position is provided. This command
allows also the PCM30/24 conversion.
Long Names:
NAME
Address of the managed object
MPTSLXX
mappingTSLXX
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed.
A further message indicates the result of the operation. An example of create command
is the following:
JOB: 15
PC Time&Date: 12:05:31 03/23/2005
NE Time&Date: 12:03:22 09/15/2004
USER NAME:
User_NSN
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = XCONNECT:0
ChangeInfo = created
560
Id:0900d805805959ad
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
XCONNECT
END OF OUTPUT FOR JOB 15
JOB: 16
PC Time&Date: 12:05:31 03/23/2005
NE Time&Date: 12:03:22 09/15/2004
USER NAME:
User_NSN
COMMAND:
Create XCONNECT:NAME=XCONNECT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 16
Operation Failed
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible. An example is the following:
JOB: 81
PC Time&Date: 16:37:54 03/23/2005
NE Time&Date: 16:35:47 09/15/2004
USER NAME:
User_NSN
COMMAND:
Create XCONNECT:NAME=XCONNECT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: OPERATION FAILED
Object instance unknown (-9)
END OF OUTPUT FOR JOB 81
Application Guidelines:
A XConnect instance is always related to a primary BPort instance. So this target
BPort instance must be created before and configured as StarX
A cross connection can only be established between a primary circuit and a secondary circuit, but not between two primary circuits or secondary circuits
A secondary circuit can only be used for cross connect functionality
A remapping can only be performed for a primary circuit. Only for traffic or signalling
timeslots the remapping is applicable, but not for a layer1 control timeslot
A50016-G5100-B333-04-7619
Id:0900d805805959ad
561
XCONNECT
BS-4x / 82 II / 240 / 241 / 240XL commands
TS 0 means to delete the TS of the XConnect
Example of Command Execution:
Create XCONNECT:NAME=XCONNECT:0,MPTSL01=0-0;
DELETE XCONNECT
DELETE XCONNECT
NAME=XCONNECT:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h XCONNECT h
DELETE XCONNECT
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command deletes the XCONNECT (Multidrop-Star CrossConnect) of 64Kbit/s
timeslots from the BTSE data base.
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
After command execution, a message of Changed Configuration Notification is displayed. A further message indicates the result of the operation. An example of delete
command is the following:
JOB: 25
PC Time&Date: 12:07:08 03/23/2005
NE Time&Date: 12:04:59 09/15/2004
USER NAME:
User_NSN
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
ChangedConfigurationNotification:
name = XCONNECT:0
ChangeInfo = deleted
END OF OUTPUT FOR JOB 25
562
Id:0900d805805959ad
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
XCONNECT
JOB: 26
PC Time&Date: 12:07:08 03/23/2005
NE Time&Date: 12:04:59 09/15/2004
USER NAME:
User_NSN
COMMAND:
Delete XCONNECT:NAME=XCONNECT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
END OF OUTPUT FOR JOB 26
Operation Failed
The specified Object has not been deleted. Additionally to the general NACK causes, a
specific NACK cause, meaning that the command is inconsistent with physical configuration, is possible.
Application Guidelines:
Deletion of a secondary circuit is only allowed, if there are no cross connections
established to the related BPort instance
Deletion of XConnect is possible in phase 2 or phase 3
In phase 3 the XConnect object must be locked before it can be deleted
Example of Command Execution:
Delete XCONNECT:NAME=XCONNECT:0;
GET XCONNECT
GET XCONNECT
NAME=XCONNECT:0..7 [,REQATTL=ALS, AST, AVS,
MPTSLXX, OST, PRS, RELFUNCOBJ];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h XCONNECT h GET
XCONNECT
Applicability:
Phase 2 and Phase 3.
Visibility level: 0.
Command Description:
This command displays the attributes of XCONNECT (Multidrop-Star CrossConnect)
and additionally of the timeslot position mapping.
Long Names:
NAME
A50016-G5100-B333-04-7619
Address of the managed object
Id:0900d805805959ad
563
XCONNECT
BS-4x / 82 II / 240 / 241 / 240XL commands
REQATTL
Required attribute list
ALS
alarmStatus
AST
administrativeState
AVS
availabilityStatus
MPTSLXX
mappingTSLXX
OST
operationalState
PRS
proceduralStatus
RELFUNCOBJ
relatedFuncObjects
System Responses:
Operation Completed
A message indicates the result of the operation. An example of get command is the following:
JOB: 17
PC Time&Date: 12:05:47 03/23/2005
NE Time&Date: 12:03:37 09/15/2004
USER NAME:
User_NSN
COMMAND:
Get XCONNECT:NAME=XCONNECT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
alarmStatus = CLEARED
administrativeState = Unlocked
availabilityStatus = NULL
mappingTSL01 =
targetBport = 0
targetTSL = 0
mappingTSL02 =
targetBport = 0
targetTSL = 0
mappingTSL03 =
targetBport = 0
targetTSL = 0
mappingTSL04 =
targetBport = 0
targetTSL = 0
mappingTSL05 =
564
Id:0900d805805959ad
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
XCONNECT
targetBport = 0
targetTSL = 0
mappingTSL06 =
targetBport = 0
targetTSL = 0
mappingTSL07 =
targetBport = 0
targetTSL = 0
mappingTSL08 =
targetBport = 0
targetTSL = 0
mappingTSL09 =
targetBport = 0
targetTSL = 0
mappingTSL10 =
targetBport = 0
targetTSL = 0
mappingTSL11 =
targetBport = 0
targetTSL = 0
JOB: 17
mappingTSL12 =
targetBport = 0
targetTSL = 0
mappingTSL13 =
targetBport = 0
targetTSL = 0
mappingTSL14 =
targetBport = 0
targetTSL = 0
mappingTSL15 =
targetBport = 0
targetTSL = 0
mappingTSL16 =
targetBport = 0
targetTSL = 0
mappingTSL17 =
targetBport = 0
targetTSL = 0
A50016-G5100-B333-04-7619
Id:0900d805805959ad
565
XCONNECT
BS-4x / 82 II / 240 / 241 / 240XL commands
mappingTSL18 =
targetBport = 0
targetTSL = 0
mappingTSL19 =
targetBport = 0
targetTSL = 0
mappingTSL20 =
targetBport = 0
targetTSL = 0
mappingTSL21 =
targetBport = 0
targetTSL = 0
mappingTSL22 =
targetBport = 0
targetTSL = 0
mappingTSL23 =
targetBport = 0
targetTSL = 0
mappingTSL24 =
targetBport = 0
targetTSL = 0
mappingTSL25 =
targetBport = 0
targetTSL = 0
mappingTSL26 =
targetBport = 0
targetTSL = 0
mappingTSL27 =
targetBport = 0
targetTSL = 0
JOB: 17
mappingTSL28 =
targetBport = 0
targetTSL = 0
mappingTSL29 =
targetBport = 0
targetTSL = 0
mappingTSL30 =
targetBport = 0
566
Id:0900d805805959ad
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
XCONNECT
targetTSL = 0
mappingTSL31 =
targetBport = 0
targetTSL = 0
operationalState = ENABLED
proceduralStatus = NULL
relatedFuncObjects =
END OF OUTPUT FOR JOB 17
Operation Failed
The GET command has not been successfully executed. A general NACK will indicate
possible errors or a specific NACK strictly related to the single command is possible.
Application Guidelines:
None.
Example of Command Execution:
Get XCONNECT:NAME=XCONNECT:0,REQATTL=ALS&AST&AVS&MPTSL01&MPTSL02&MPTSL03&MPTSL04&M
PTSL05&MPTSL06&MPTSL07&MPTSL08&MPTSL09&MPTSL10&MPTSL11&MPTS
L12&MPTSL13&MPTSL14&MPTSL15&MPTSL16&MPTSL17&MPTSL18&MPTSL19&
MPTSL20&MPTSL21&MPTSL22&MPTSL23&MPTSL24&MPTSL25&MPTSL26&MPT
SL27&MPTSL28&MPTSL29&MPTSL30&MPTSL31&OST&PRS&RELFUNCOBJ;
LOCK XCONNECT
LOCK XCONNECT
NAME=XCONNECT:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h XCONNECT h LOCK
XCONNECT
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the XCONNECT (Multidrop-Star
CrossConnect).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
A50016-G5100-B333-04-7619
Id:0900d805805959ad
567
XCONNECT
BS-4x / 82 II / 240 / 241 / 240XL commands
JOB: 19
PC Time&Date: 12:06:07 03/23/2005
NE Time&Date: 12:03:58 09/15/2004
USER NAME:
User_NSN
COMMAND:
Lock XCONNECT:NAME=XCONNECT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
administrativeState = Locked
END OF OUTPUT FOR JOB 19
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 18
PC Time&Date: 12:06:02 03/23/2005
NE Time&Date: 12:03:54 09/15/2004
USER NAME:
User_NSN
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = XCONNECT:0
Administrative State = LOCKED
Notification Identifier = 3151
END OF OUTPUT FOR JOB 18
Operation Failed
The specified change of administrative state has not been performed (e.g. the object is
redundant and its spare copy is disabled or already locked, a subordinate resource
cannot go into disabled state with "dependency" availability status).
568
Id:0900d805805959ad
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
XCONNECT
Application Guidelines:
This command has no effect on the established connections
Example of Command Execution:
Lock XCONNECT:NAME=XCONNECT:0;
SET XCONNECT
SET XCONNECT
NAME=XCONNECT:0..7 [,MPTSLXX=];
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h XCONNECT h SET
XCONNECT
Applicability:
Phase 2 and Phase 3.
Visibility level: 2.
Command Description:
This command sets the attributes for the mapping of the XCONNECT (Multidrop-Star
CrossConnect) 64Kbit/s timeslot position.
Long Names:
NAME
Address of the managed object
MPTSLXX
mappingTSLXX
System Responses:
Operation Completed
The specified attribute has been set. In addition, a Changed Attribute Event Report indicates that the command has been successfully executed:
JOB: 20
PC Time&Date: 12:06:33 03/23/2005
NE Time&Date: 12:04:23 09/15/2004
USER NAME:
User_NSN
COMMAND:
Set XCONNECT:NAME=XCONNECT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: SET-NACK
Operation successful
END OF OUTPUT FOR JOB 20
Operation Failed
A50016-G5100-B333-04-7619
Id:0900d805805959ad
569
XCONNECT
BS-4x / 82 II / 240 / 241 / 240XL commands
The specified Object has not been created. In addition to the general NACK causes, a
specific NACK cause, which indicates that the command is inconsistent with the
physical configuration, is possible.
Application Guidelines:
A secondary circuit cannot be changed to a primary circuit and vice versa via a SET
command
A remapping can only be performed for a primary circuit
Only for traffic or signalling timeslots the remapping is applicable, but not for a layer1
control timeslot
Example of Command Execution:
Set XCONNECT:NAME=XCONNECT:0,MPTSL01=0-0;
UNLOCK XCONNECT
UNLOCK XCONNECT
NAME=XCONNECT:0..7;
Command Tree:
MANAGED-ELEMENT h BSS-EQUIPMENT h BTSEP h XCONNECT h
UNLOCK XCONNECT
Applicability:
Phase 2 and Phase 3.
Visibility level: 1.
Command Description:
This command changes the administrative state of the XCONNECT (Multidrop-Star
CrossConnect).
Long Names:
NAME
Address of the managed object
System Responses:
Operation Completed
The specified change of administrative state has been perfomed:
JOB: 22
PC Time&Date: 12:06:46 03/23/2005
NE Time&Date: 12:04:37 09/15/2004
USER NAME:
User_NSN
COMMAND:
Unlock XCONNECT:NAME=XCONNECT:0;
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
570
Id:0900d805805959ad
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
XCONNECT
administrativeState = Unlocked
END OF OUTPUT FOR JOB 22
CHANGED STATE EVENT REPORT:
This provides information about the administrative state, the operational state and the
availability status every time a state change occurs:
JOB: 21
PC Time&Date: 12:06:46 03/23/2005
NE Time&Date: 12:04:37 09/15/2004
USER NAME:
User_NSN
SW RELEASE:
01-04-17-01-26-51_05-02-23
COMMAND RESULT: Operation successful
CHANGED STATE EVENT REPORT:
NAME = XCONNECT:0
Administrative State = UNLOCKED
Notification Identifier = 3154
END OF OUTPUT FOR JOB 21
Operation Failed
The specified change of administrative state has not been performed.
Application Guidelines:
This command has no effect on the established connections
Example of Command Execution:
Unlock XCONNECT:NAME=XCONNECT:0;
A50016-G5100-B333-04-7619
Id:0900d805805959ad
571
Parameters/attributes in alphabetical order
BS-4x / 82 II / 240 / 241 / 240XL commands
3 Parameters/attributes in alphabetical order
g Please note that the abbreviations marked with an * are not real parameters.
572
Id:0900d80580248208
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
a
ABISCH
abisChannel
This attribute identifies the Timeslot Number and Sublot Number allocated on the Abisinterface.This attribute exists only for TRX. The attribute refers to a radio signalling link
(RSL): it indicates just the default channel for the RSL - a more actual information is
reflected in the object LAPDLE.
Validity Range
BPORT
(TRX)
00-07
(for BS-82 II only, BPortNumber 00-03 is allowed)
TSL
1-31 (PCM30)
SSL
SSL0
a (bits 8,7)
SSL1
b (bits 6,5)
SSL2
c (bits 4,3)
SSL3
d (bits 2,1)
1-24 (PCM24)
NOT_USED
64 kb/s signalling
(the value NOT_USED reflects at the MMI that RSL operates with 64 kb/s)
Default Value
None.
Contained in the following commands:
GET TRX
ABISLKSAT
sAbisLinkSatellited
The attribute informs the BTSE SW about the presence of a satellite on the Asub interface.
Validity Range
terrestrialConnection
satelliteConnection
Default Value
terrestrialConnection
Contained in the following commands:
GET BTSM NOSWL, SET BTSM
ABISTIME
sAbisExternalTime
A50016-G5100-B333-04-7619
Id:0900d80580627a8f
573
BS-4x / 82 II / 240 / 241 / 240XL commands
This attribute provides the time-of-day time of the BTSE. This attribute functions as a
reference for all time stamp activities in the BTSE. A daily update of the attribute is performed via Abis. Additionally the attribute is update after each successful Abis-alignment.
Validity Range
In commands GET BTSM NOSWL:
<ANY>
<NULL>
In commands SET BTSM:
year
1992 - 2099
month
1 - 12
day
1 - 31
hour
0 - 23
min
0 - 59
sec
0 - 59
offsetHour
-12 - 14
offsetMinute
0 - 45
Default Value
None.
Contained in the following commands:
GET BTSM NOSWL, SET BTSM
ACBQPFF
acBQPFgtFac
acBQPFgtFac defines the forgetting factor for the time exponential filter used for BQP
averaging. A change of the attribute becomes effective at the next AC period.
Validity Range
0.1 - 1.0
10 entries can be selected:
- 1 corresponds to the attribute value 0.1
- 10 corresponds to the attribute value 1.0
Default Value
0.2
Contained in the following commands:
GET BTS
574
Id:0900d80580627a8f
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ACBQPMAX
acBQPMax(%)
acBQPMax specifies the maximum tolerated Bad Quality Probability (outage probability)
in the cell. If e.g. acFERMax is 5% and acBQPMax is 10% it indicates that more than
10% of the speech samples having a FER with more than 5% is not acceptable. A
change of the attribute becomes effective at the next AC period.
Validity Range
2 - 10
9 entries can be selected:
- 2 corresponds to the attribute value 2%
- 10 corresponds to the attribute value 10%
Default Value
5%
Contained in the following commands:
GET BTS
ACEFLFF
acEFLFgtFac
acEFLFgtFac defines the forgetting factor for the exponential filter used for fractional
load averaging. A change of the attribute becomes effective at the next AC period.
Validity Range
0.02 - 0.20
10 entries can be selected:
- 1 corresponds to the attribute value 0.02
- 10 corresponds to the attribute value 0.20
Default Value
0.04
Contained in the following commands:
GET BTS
ACFERMAX
acFERMax(%)
acFERMax is a criterion for the speech quality in terms of frame erasure rate (FER).
acFERMax specifies the maximum tolerated FER for speech samples taken over 4
SACCH periods, e.g. acFERMax = 5.0% requires that not more than 5% bad speech
frames are allowed in a sample taken over 4 SACCH periods, i.e. the FER over the
sampling period of 4 SACCH frames shall be less or equal to 5%. In other words, if the
percentage of bad frames (FER > acFERMax) is greater than acFERMax the respective
A50016-G5100-B333-04-7619
Id:0900d80580627a8f
575
BS-4x / 82 II / 240 / 241 / 240XL commands
sample will increase the BQP. A change of the attribute becomes effective at the next
AC period.
Validity Range
1.0 - 10.0
19 entries can be selected:
- 1 corresponds to the attribute value 1.0%
- 19 corresponds to the attribute value 10.0%
(the step size is 0.5%)
Default Value
5.0%
Contained in the following commands:
GET BTS
ACLNKTYP
acLinkType
acLinkType defines the type of samples to be collected. It also specifies the way they
will be used for the BQP evaluation.
acLinkType == 0 and acLinkType == 2 require EMR (ENHANCED MEASUREMENT
REPORTING). A change of the attribute becomes effective at the next AC period.
Validity Range
UL_AND_DL_SAMPLES_S
EPARATELY
UL_SAMPLES_ONLY
UL_AND_DL_SAMPLES_
COMMONLY
Default Value
UL_SAMPLES_ONLY (Collect and evaluate UL samples only)
Contained in the following commands:
GET BTS
ACMAXEFLDMA
acMaxEFLDMA(%)
acMaxEFLDMA specifies the maximum effective frequency load (EFL). The value is
valid for each DMA layer of the cell. A change of the attribute becomes effective at the
next AC period.
Validity Range
10%
576
Id:0900d80580627a8f
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
15%
.
100%
(starting from 10, 19 entries could be selected, with step size = 5)
Default Value
50%
Contained in the following commands:
GET BTS
ACMINEFLDMA
acMinEFLDMA(%)
acMinEFLDMA specifies the minimum EFL. The value is valid for each DMA layer of the
cell. A change of the attribute becomes effective at the next AC period.
Validity Range
5
5%
10 10%
..
..
50
50%
(starting from 5, the entries could be selected, with step size=5)
Default Value
50%
Contained in the following commands:
GET BTS
ACONN
alarmConnector
The MDUX alarm line can be assigned to any ACTC alarm connector which is freely
configurable via an ENVABTSE object. The relative ENVABTSE must not be created if
the related connector is used for the MDUX.
Validity Range
ENVA0
ENVA1
...
A50016-G5100-B333-04-7619
Id:0900d80580627a8f
577
BS-4x / 82 II / 240 / 241 / 240XL commands
ENVA8
Default Value
None.
Contained in the following commands:
CREATE BCOM, GET BCOM, SET BCOM
ACPER
acPeriod
acPeriod specifies the time/length of every Admission Control Period in measurement
reporting periods (480 milliseconds) (e.g. 100 periods) used for the periodic AC evaluation and the periodic reporting to the BSC via the 'Radio Link Admission Control
Message. A change of the attribute becomes effective at the next AC period.
Validity Range
20
20 measurement reporting periods
24
24 measurement reporting periods
measurement reporting periods
measurement reporting periods
396 396 measurement reporting periods
400 400 measurement reporting periods
(96 possible entries with step size equal to 4)
Default Value
120 measurement reporting periods
Contained in the following commands:
GET BTS
ACTVINC
activationIncluded
This attribute indicates whether the installed FW is be activated automatically by LRU
reset or not.
Validity Range
TRUE
FALSE
Default Value
None.
Contained in the following commands:
FWUPGRADE BTSM
578
Id:0900d80580627a8f
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ALIGCOBA
alignedCoba
The attribute indicates that the flash content is potentially incomplete due to a previously
interrupted
COBA alignment. 16
The alignedCOBA attribute is automatically set to 'False' by the BTSE if the passive
COBA could not be aligned. If the attribute is set to TRUE by the operator (to indicate,
that he checked and, if necessary, corrected the Flash-contents to his needs) the
according alarm is ceased.
The setting to 'False' via command is rejected.
Validity Range
TRUE
FALSE
Default Value
TRUE
Contained in the following commands:
GET BTSEP NOSWL, SET BTSEP
ALRMCLET
alarmClearanceTime
An alarm must not be active at least for this time before it is ceased. The time is
expressed by the number of polling periods (1 s).
Validity Range
1 - 20
Default Value
10
Contained in the following commands:
CREATE CESTUNNEL, GET CESTUNNEL, SET CESTUNNEL
ALRMCOUNTER
alarmCount
The BTSE supports a filter mechanism for the following failure event
reports related to pcm line problems (and is valid for all created
BPORT instances).
1. "lower BER threshold exceeded"
A50016-G5100-B333-04-7619
Id:0900d80580627a8f
579
BS-4x / 82 II / 240 / 241 / 240XL commands
2. "external signal absence"
3. "AIS alarm"
4. "frame alignment loss"
5. "higher BER threshold exceeded"
6. "remote alarm"
The following filter mechanism is applied for the failure event reports
1-6 listed above.
An alarm is generated because of 2 possible events:
a) If it is found active for a time interval equal or greater than
alarmTiming2.
b) If it is found active with a duration less than alarmTiming2 but it is
found active at least as often as alarmCount in a time interval equal
to alarmTiming3. The number of the alarm is incremented every time
a transition 'not active' to 'active' is detected.
The alarm contains an information in the additional information
parameter whether it was detected due to event a) or event b).
An active alarm is cleared if no alarm is found for a time interval
equal to alarmTiming1.
Validity Range
1 - 254
Default Value
32
Contained in the following commands:
CREATE COBA, GET COBA, SET COBA
ALRMPERT
alarmPersistencyTime
All alarms which could toggle must persist at least for this time before an alarm is
reported. The time is expressed by the number of polling periods (1 s).
Validity Range
1 - 20
Default Value
3
Contained in the following commands:
CREATE CESTUNNEL, GET CESTUNNEL, SET CESTUNNEL
580
Id:0900d80580627a8f
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ALRMSEVXXX
alarmSeverityXXX
This attribute defines the severity that the BTSE SW has to use for
the given type of HW board in case of state transitions from 'enabled'
to 'disabled failed'.
A change of the attribute becomes effective with the start of a new
failure, i.e. if the attribute is changed and a failure is still pending the
change of the attribute will not trigger a 'failure ceased' failure event
report together with a failure event report with the new alarmSeverityXXX.
List of BS240, BS24XL, BS241, BS40, BS41 HW:
ALRMSEVACDC, ALRMSEVACT, ALRMSEVBATTERY, ALRMSEVBCOMP,
ALRMSEVCOBA, ALRMSEVCOSA, ALRMSEVCU,
ALRMSEVDIDCTMA, ALRMSEVDILNA, ALRMSEVDUAMCO,
ALRMSEVDUDCTMA,
ALRMSEVDULNA, ALRMSEVDUVSWR, ALRMSEVF6DCTMA,
ALRMSEVF6LNA, ALRMSEVF6TNFP, ALRMSEVF6VSWRP,
ALRMSEVFANP, ALRMSEVFCUMAIN,ALRMSEVFCUTR,
ALRMSEVFTNFP, ALRMSEVFVSWRP, ALRMSEVTMA
Validity Range
CRITICAL
MAJOR
MINOR
DEFAULT_DB
Default Value
DEFAULT_DB
Contained in the following commands:
GET BTSEP NOSWL, SET BTSEP
ALRMT1/2/3
alarmTiming1(sec)/2(sec)/3(unit of 5 minutes)
The attribute value is valid for all created BPORT instances.
A50016-G5100-B333-04-7619
Id:0900d80580627a8f
581
BS-4x / 82 II / 240 / 241 / 240XL commands
The BTSE supports a filter mechanism for the following failure event
reports related to pcm line problems:
1. "lower BER threshold exceeded"
2. "external signal absence"
3. "AIS alarm"
4. "frame alignment loss"
5. "higher BER threshold exceeded"
6. "remote alarm"
The following filter mechanism is applied for the failure event reports
listed above.
An alarm is generated because of 2 possible events:
a) If it is found active for a time interval equal or greater than
alarmTiming2.
b) If it is found active with a duration less than alarmTiming2 but it is
found active at least as often as alarmCount in a time interval equal
to alarmTiming3. The number of the alarm is incremented every time
a transition 'not active' to 'active' is detected.
- The alarm contains an information in the additional information
parameter whether it was detected due to event a) or event b).
- An active alarm is cleared if no alarm is found for a time interval
equal to alarmTiming1.
Validity Range
g The alrmt1 and alrmt2 attributes are indicated in seconds (with 1 second step size).
The alrmt3 attribute is indicated in minutes (with 5 minutes steps size).
1 - 254
Default Value
alrmt1 : 20 seconds
alrmt1 : 1 second
alrmt1 : 1 (5 minutes)
Contained in the following commands:
CREATE COBA, GET COBA, SET COBA
ALS
alarmStatus
This attribute shows the highest severity of all active alarm conditions related to the
managed object. In case of summarization objects a proprietary semantics is used.
Validity Range
CLEARED
582
Id:0900d80580627a8f
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
MINOR
MAJOR
CRITICAL
Default Value
CLEARED
Contained in the following commands:
GET ACDCP, GET ACT, GET BATTERY, GET BCOM, GET BPORT, GET BTSEP
NOSWL, GET CESPW, GET CESTUNNEL, GET COBA, GET COBAETHINTF, GET
COSA, GET CU, GET DIDCTMA, GET DILNA, GET DUAMCO, GET DUDCTMA,
GET DULNA, GET DUVSWR, GET ENVABTSE, GET ETHCON, GET ETHPORT,
GET F6DCTMA, GET F6LNA, GET F6TNFP, GET F6VSWRP, GET FANP, GET
FCUMAIN, GET FCUTR, GET FTNFP, GET FVSWRP, GET LAPDLE, GET RACK,
GET SYNCBTSE, GET TMA, GET XCONNECT
AMRLKAT
aMRLinkAdapTuning
This parameter is used by the AMR Uplink Codec Mode Adaptation in the BTS. It tunes
the transition between codec modes determined by internal thresholds. A value higher
than the default shifts the transition towards higher carrier-to-interferer or signal-to-noise
ratios. A value lower than the default has the opposite effect. The step size is 0,1dB.
Adaptation of AMR Half Rate and AMR Full Rate is affected simultaneously. All possible
transitions between modes are generally shifted by the same amount.
However, to account for a limited range of the underlying measurements, shifts of transitions near the upper range limit tend to saturate when shifted closer to the limit. The
default value is the optimum setting and normally requires no modification.
Validity Range
<0x00...0xC8>
(i.e. -10 dB to 10 dB), step: 1 (0.1 dB), as follows:
0 - 200
00
-100
01
-99
99
-1
100
101
+1
200
+100
(-10 dB)
(0 dB)
(10 dB)
The values have the following meaning:
0x00 -10 dB
0x01 -9.9 dB
A50016-G5100-B333-04-7619
Id:0900d80580627a8f
583
BS-4x / 82 II / 240 / 241 / 240XL commands
..
0x63 -0.1 dB
0x64 0 dB
..
0xC8 10 dB
Default Value
0 dB
Contained in the following commands:
GET BTS
AMRLKATWFS
aMRLinkAdapTuningWFS(dB)
Uplink codec mode adaptation for TCH/WFS.
Validity Range
-10.0 - 10.0
Default Value
None.
Contained in the following commands:
GET BTS
ANT<x>CELLNO
ant<x>CellNumber
This attribute specifies the number of the cell. The value corresponds to the instance
number of the object BTS. The attribute can be only modified if no wiring destinations
are configured.
Note: <x> ... <0...5>
so the names of the attributes read:
GUI: ant0CellNumber
CLI: ANT0CELLNO
ant1CellNumber
ANT1CELLNO
ant2CellNumber
ANT2CELLNO
ant3CellNumber
ANT3CELLNO
ant4CellNumber
ANT4CELLNO
ant5CellNumber
ANT5CELLNO
g With the SET BCOM command it is possible to "delete" the parameters setting the
value "NULL", not all together but first the wiring date and in a second command the
cell parameters (see Application Guidelines: of SET BCOM).
584
Id:0900d80580627a8f
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
In commands CREATE BCOM, SET BCOM:
0 - 11
<NULL>
In commands GET BCOM:
<ANY>
Default Value
In moc(s) BCOM:
None.
In moc(s) BCOM:
NULL
Contained in the following commands:
CREATE BCOM, GET BCOM, SET BCOM
ANT<x>SCNRX
ant<x>SecondCellNumberRx
This attribute is available only for the object class BCOM, and only if "typeOfBTSE" is
set to "BS288". This attribute allows sharing of one antenna by 2 cells for receive diversity.
Note: <x> ... <0...5>
so the names of the attributes read:
GUI: ant0SecondCellNumberRx CLI: ANT0SCNRX
ant1SecondCellNumberRx
ANT1SCNRX
ant2SecondCellNumberRx
ANT2SCNRX
ant3SecondCellNumberRx
ANT3SCNRX
ant4SecondCellNumberRx
ANT4SCNRX
ant5SecondCellNumberRx
ANT5SCNRX
g With the SET BCOM command it is possible to "delete" the parameters setting the
value "NULL", not all together but first the wiring date and in a second command the
cell parameters (see Application Guidelines: of SET BCOM).
Validity Range
In commands CREATE BCOM, SET BCOM:
0 - 11
A50016-G5100-B333-04-7619
Id:0900d80580627a8f
585
BS-4x / 82 II / 240 / 241 / 240XL commands
<NULL>
In commands GET BCOM:
<ANY>
Default Value
In moc(s) BCOM:
None.
In moc(s) BCOM:
NULL
Contained in the following commands:
CREATE BCOM, GET BCOM, SET BCOM
ANT<x>WDRX
ant<x>WiringDataRx
The attribute specifies the carrier unit ports, which are connected to the Rx outputs of a
MDUX submodule. The maximum number of destinations is:
4 if MDUX only equipped
8 if MDUX and DUAMCO equipped
Note: <x> ... <0...5> so the names of the attributes read:
GUI: ant0WiringDataRx CLI: ANT0WDRX
ant1WiringDataRx
ANT1WDRX
ant2WiringDataRx
ANT2WDRX
ant3WiringDataRx
ANT3WDRX
ant4WiringDataRx
ANT4WDRX
ant5WiringDataRx
ANT5WDRX
The following values are possible for 'RX_wiring n':
H'0012FF00 CU0N (CU0 normal path)
H'00FF00 CU0D (CU0 diversity path)
H'0012FF01 CU1N (CU1 normal path)
H'0112FF01 CU1D (CU1 diversity path)
H'0012FF02 CU2N (CU2 normal path)
H'0112FF02 CU2D (CU2diversity path)
H'0012FF03 CU3N (CU3 normal path)
H'0112FF03 CU3D (CU3 diversity path)
H'0012FF04 CU4N (CU4 normal path)
H'0112FF04 CU4D (CU4 diversity path)
H'0012FF05 CU5N (CU5 normal path)
H'0112FF05 CU5D (CU5 diversity path)
586
Id:0900d80580627a8f
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
H'002AFF00 FCUMAIN0N (FCUMAIN0 normal path)
H'012AFF00 FCUMAIN0D (FCUMAIN0 diversity path)
H'022AFF00 FCUMAIN0N1 (FCUMAIN0 Rx C / N1 path)
g With the SET BCOM command it is possible to "delete" the parameters setting the
value "NULL", not all together but first the wiring date and in a second command the
cell parameters (see Application Guidelines: of SET BCOM).
Validity Range
1 to 8 items of
CU0N
CU0D
CU1N
CU1D
CU2N
CU2D
CU3N
CU3D
CU4N
CU4D
CU5N
CU5D
CU6N
CU6D
CU7N
CU7D
CU8N
CU8D
CU9N
CU9D
CU10N
CU10D
CU11N
CU11D
FCUMAIN0N
FCUMAIN0D
FCUMAIN0N1
FCUMAIN0D1
A50016-G5100-B333-04-7619
Id:0900d80580627a8f
587
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUMAIN1N
FCUMAIN1D
FCUMAIN1N1
FCUMAIN1D1
FCUMAIN2N
FCUMAIN2D
FCUMAIN2N1
FCUMAIN2D1
FCUMAIN3N
FCUMAIN3D
FCUMAIN3N1
FCUMAIN3D1
FCUMAIN4N
FCUMAIN4D
FCUMAIN4N1
FCUMAIN4D1
FCUMAIN5N
FCUMAIN5D
FCUMAIN5N1
FCUMAIN5D1
FCUMAIN6N
FCUMAIN6D
FCUMAIN6N1
FCUMAIN6D1
FCUMAIN7N
FCUMAIN7D
FCUMAIN7N1
FCUMAIN7D1
FCUMAIN8N
FCUMAIN8D
FCUMAIN8N1
FCUMAIN8D1
FCUMAIN9N
FCUMAIN9D
FCUMAIN9N1
FCUMAIN9D1
588
Id:0900d80580627a8f
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUMAIN10N
FCUMAIN10D
FCUMAIN10N1
FCUMAIN10D1
FCUMAIN11N
FCUMAIN11D
FCUMAIN11N1
FCUMAIN11D1
NULL
<NULL>
Default Value
None.
Contained in the following commands:
SETWIRINGRX BCOM
ANT<x>WDTX
ant<x>WiringDataTx
The attribute specifies the carrier unit ports which are either directly or via HYBRID6
connected to the TX input of an MDUX submodule. The maximum number of destinations is:
1 if MDUX without HYBRID6 equipped
2 if MDUX with HYBRID6 equipped
4 if MDUX with HYBRID6 and COAMCO equipped
Validity Range
1 to 4 items of
CU0
CU1
CU2
CU3
CU4
CU5
CU6
CU7
CU8
CU9
CU10
A50016-G5100-B333-04-7619
Id:0900d80580627a8f
589
BS-4x / 82 II / 240 / 241 / 240XL commands
CU11
FCUMAIN0TX0
FCUMAIN0TX1
FCUMAIN1TX0
FCUMAIN1TX1
FCUMAIN2TX0
FCUMAIN2TX1
FCUMAIN3TX0
FCUMAIN3TX1
FCUMAIN4TX0
FCUMAIN4TX1
FCUMAIN5TX0
FCUMAIN5TX1
FCUMAIN6TX0
FCUMAIN6TX1
FCUMAIN7TX0
FCUMAIN7TX1
FCUMAIN8TX0
FCUMAIN8TX1
FCUMAIN9TX0
FCUMAIN9TX1
FCUMAIN10TX0
FCUMAIN10TX1
FCUMAIN11TX0
FCUMAIN11TX1
NULL
<NULL>
Default Value
None.
Contained in the following commands:
SETWIRINGTX BCOM
ANTB
antennaBearing(degree)
Attribute data provided by the TMA.
590
Id:0900d80580627a8f
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
0 - 65535
<NULL>
Default Value
None.
Contained in the following commands:
GET TMA
ANTHOPHW
antennaHoppingHw
The attribute shows which antenna hardware is used by a TRX for
antenna hopping. The attribute doesn't show how often an antenna
hardware is used - i.e. the attribute doesn't reflect the actual antenna
hopping sequence. The attribute length is 0 for hh-ii=04-01 if no
antenna hopping is used.
Not BR8.0: In a switched beam cell, the attribute shows a list of
SDUSEC instances which are enabled in the cell and offer service to
the input TRXs (in this case 0 < n < 10).
type of HW = DUVSWR or SDUSEC
N <= 98 (decimal)
0 <= n < 24
Validity Range
0 to 23 items of
Pathname
Default Value
None.
Contained in the following commands:
GET TRX
ANTHOPMOD
antennaHoppingMode
This attribute specifies whether the BCCH transceiver has to be included in the hopping
sequence for Antenna Hopping or not. The attribute is only valid if the feature Antenna
Hopping is enabled (attribute enableAntennaHopping).
Validity Range
NOBCCHTRX
ALLTRX
A50016-G5100-B333-04-7619
Id:0900d80580627a8f
591
BS-4x / 82 II / 240 / 241 / 240XL commands
Default Value
NOBCCHTRX
Contained in the following commands:
GET BTS
ANTHOPP
antennaHoppingPeriod
This attribute specifies how many frames will be transmitted over each antenna before
the next antenna will be used to send the frames. The number of antenna changes
depends on the number of used antennas and service (4-4-5 used for EDGE).The attribute is only valid if the feature Antenna Hopping is enabled (attribute enableAntennaHopping).
Validity Range
ALL
SECOND
FOURTH
SEQ_445
Default Value
SECOND
Contained in the following commands:
GET BTS
ANTHOPST
antennaHoppingStatus
This attribute indicates the current status of Antenna Hopping. For a BTS only using
FICOM (FVSWRP) in transmit direction the attribute value is 'hopping off'. (FALSE =
hopping off)
Validity Range
TRUE
FALSE
Default Value
FALSE
Contained in the following commands:
GET BTS
ANTMN
antennaModelNumber
592
Id:0900d80580627a8f
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Attribute data provided by the TMA.
Validity Range
0..15 characters string
Default Value
None.
Contained in the following commands:
GET TMA
ANTSN
antennaSerialNumber
Attribute data provided by the TMA.
Validity Range
0..17 characters string
Default Value
None.
Contained in the following commands:
GET TMA
ARFACCHACMDF
applyRFacchOnAnyCmdFrame
This attribute determines the LAPDm frame type on which R-FACCH (Repeated
FACCH) is allowed, if the latter has been enabled by the parameter enableRFACCH on
the respective codec type. The parameter is implemented as a bitmap consisting of 4
bits:
Bitmap Frame Type LAPDm Frame Type Description
0/1 I (ASSHOCMD) Only I-frames carrying ASS_CMD and HO_CMD. See note 1.
0/1 UI (PHSY_INFO) UI-frames carrying the PHSY_INFO. See note 1.
0/1 I (COMPLEMENTARY) I-frames excluding I (ASSHOCMD). See note 2.
0/1 UA UA response frames. See note 3.
The value '0' denotes R-FACCH is allowed while the value '1' denotes R-FACCH is not
allowed on the respective LAPDm frame type.
A50016-G5100-B333-04-7619
Id:0900d80580627a8f
593
BS-4x / 82 II / 240 / 241 / 240XL commands
g Notes:
1. R-FACCH shall not be used on command frames other than I-frames and UI-frames.
Both I-frames and UI-frames of LAPDm protocol are used for Information transfer
i.e. they contain payload of higher signaling layer. I-frames are transferred in
acknowledged mode whereas UI-frames are transferred in Unacknowledged mode.
2. Distinguishing between I-frames carrying ASS_CMD and HO_CMD: I(ASSHOCMD)
and the rest of I-frames: I(COMPLEMENTARY) is necessary due to problems anticipated with some types of legacy MS when receiving (COMPLEMENTARY) frames
in R-FACCH mode.
3. UA-frames are not allowed by the 3GPP-standard now, but a Change Request to
allow R-FACCH on UA-frames might be issued in the future. UA-frames of LAPDm
protocol are sent as Unnumbered Acknowledgement i.e. they are used to send
response to commands delivered previously in S-frames (Supervisory) frames.
Validity Range
TRUE
FALSE
Default Value
None.
Contained in the following commands:
GET BTS
ASCICIPH
enableCiphForASCI
The attribute enableCiphForASCI indicates whether ciphering for VGCS (Voice Group
Call Service) is
enabled or disabled. VGCS ciphering allows to offer a secured path on the radio interface for mobiles engaged in point to multipoint connections, as it was already possible
for the point to point calls.
Validity Range
TRUE
FALSE
Default Value
None.
Contained in the following commands:
GET BTS
ASEV
associatedSeverity
594
Id:0900d80580627a8f
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
The attribute allows the operator to define a specific severity for the failure event report
related to a envaBTSE instance (site input).
The severity of alarm database is used (DEFAULT_DB) as default value.
Validity Range
CRITICAL
MAJOR
MINOR
DEFAULT_DB
Default Value
DEFAULT_DB
Contained in the following commands:
CREATE ENVABTSE, GET ENVABTSE
AST
administrativeState
This attribute indicates whether the management services have permitted or prohibited
the use of the resource.
Validity Range
Locked
Unlocked
ShuttingDown
Default Value
Locked for functional objects
Unlocked for equipment objects
Contained in the following commands:
GET ACDCP, GET ACT, GET BATTERY, GET BCOM, GET BPORT, GET BTS,
GET BTSEP NOSWL, GET BTSM NOSWL, GET CESPW, GET CESTUNNEL, GET
CHAN, GET COBA, GET COBAETHINTF, GET COSA, GET CU, GET DIDCTMA,
GET DILNA, GET DUAMCO, GET DUDCTMA, GET DULNA, GET DUVSWR, GET
ENVABTSE, GET ETHCON, GET ETHPORT, GET F6DCTMA, GET F6LNA, GET
F6TNFP, GET F6VSWRP, GET FANP, GET FCUMAIN, GET FCUTR, GET FTNFP,
GET FVSWRP, GET LAPDLE, GET RACK, GET SYNCBTSE, GET TMA, GET TRX,
GET XCONNECT
ASTRING
associatedString
A50016-G5100-B333-04-7619
Id:0900d80580627a8f
595
BS-4x / 82 II / 240 / 241 / 240XL commands
This attribute allows the operator to define a specific text string for the failure event
report related to an environmental alarm. It will be put into the information element "additional text" of the failure event report. In case of hh=04 a specific string
(##ACDC_FAULT) can be used to indicate that the support of emergency configuration
in case of e.g. third party battery backup units is derived from the corresponding
envaBTSE instance.
The ASCII characters are not terminated by a NULL character.
Validity Range
0..26 characters string
Default Value
""
Contained in the following commands:
CREATE ENVABTSE, GET ENVABTSE
ASUBLKSAT
sAsubLinkSatellited
This attribute informs the BTSE SW about the presence of a satellite on the Asub interface.
Validity Range
terrestrialConnection
satelliteConnection
Default Value
terrestrialConnection
Contained in the following commands:
GET BTSM NOSWL
AVS
availabilityStatus
This attribute elaborates the Operational state and gives detailed information about the
actions that occur.
Validity Range
1 to 6 items of
InTest
Failed
PowerOff
596
Id:0900d80580627a8f
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
OffLine
OffDuty
Dependency
Degraded
NotInstalled
NULL
Default Value
Not Installed
for equipment objects
Off line
for TRX
NULL value
for BTS / CHAN / BTSM
Contained in the following commands:
GET ACDCP, GET ACT, GET BATTERY, GET BCOM, GET BPORT, GET BTS,
GET BTSEP NOSWL, GET BTSM NOSWL, GET CESPW, GET CESTUNNEL, GET
CHAN, GET COBA, GET COBAETHINTF, GET COSA, GET CU, GET DIDCTMA,
GET DILNA, GET DUAMCO, GET DUDCTMA, GET DULNA, GET DUVSWR, GET
ENVABTSE, GET ETHCON, GET ETHPORT, GET F6DCTMA, GET F6LNA, GET
F6TNFP, GET F6VSWRP, GET FANP, GET FCUMAIN, GET FCUTR, GET FTNFP,
GET FVSWRP, GET LAPDLE, GET RACK, GET SYNCBTSE, GET TMA, GET TRX,
GET XCONNECT
A50016-G5100-B333-04-7619
Id:0900d80580627a8f
597
BS-4x / 82 II / 240 / 241 / 240XL commands
b
BATTCAP
batteryCapacity(*5Ah)
This attribute contains the value of the actual capacity of the installed battery in units of
5 Ah. The attribute reflects the setting of the DIP switch on the ACDCP controller board.
The value 0 corresponds to no battery backup.
The value 255 corresponds to battery backup 1275 Ah.
Note: The value 'no battery backup (0 Ah)' for a created object 'BATTERY' means that
the operational state of the object will be "disabled". All other values result in the operational state "enabled".
Validity Range
0 - 255
<NULL>
Default Value
None.
Contained in the following commands:
GET BATTERY
BCCHFREQ
bcchFrequency
This attribute is used for the objects BTS and ADJC and ADJCUMTS.
It contains the absolute radio frequency channel number of the BCCH
channel. It is identical to the GSM attribute BCCH ARFCN.
598
cellAllocationNumber
Hex
Decimal
GSM900 "BB900"
0001 ... 007C
1 ... 124
GSM EXTENDED
"F2ONLY900"
0000 ... 007C
0 ... 124
03CF ... 03FF
975 ... 1023
GSM EXTENDED
REDUCED
"EXT900"
0000 ... 007C
0 ... 124
03CF ... 03FF
975 ... 1023
DCS 1800
"DCS1800"
0200 ... 0375
512 ... 885
PCS 1900
0200 ... 032A
512 ... 810
GSM-R
03BB ... 03CE
955 ... 974
Id:0900d8058051e6ce
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
GSM-DCS
0000 ... 007C
0 ... 124
03CF ... 03FF
975 ... 1023
0200 ... 0375
512 ... 885
GSM850
0080 ... 00FB
128 ... 251
GSM850-PCS
0080 ... 00FB
128 ... 251
0200 ... 032A
512 ... 810
0080 ... 00FB
128 ... 251
0200 ... 0375
512 ... 885
GSM850-DCS
Validity Range
0 - 1023
Default Value
None.
Contained in the following commands:
GET BTS
BCOMTYPE
bcomType
The attribute specifies the BCOM type. It is highly recommended to set this attribute to
the correct value in order to ensure software checks for a consistent wiring in terms of
the number of carrier units which can be wired to the BCOM.
It is the operator's responsibility to configure the correct value because the system
cannot check if the value fits to the equipped hardware.
Validity Range
SixToSix
TwelveToSix
SixToSixMDUX
TwelveToSixMDUX
TwelveToSixCOAMCO
NotSet
Default Value
NotSet
Contained in the following commands:
CREATE BCOM, GET BCOM, SET BCOM
A50016-G5100-B333-04-7619
Id:0900d8058051e6ce
599
BS-4x / 82 II / 240 / 241 / 240XL commands
BCPBL
boardCapability
This attribute returns the amount of configurable BPort interfaces on the related COBA
board.
Values are: 0\ twoAbisLines\ 1\ fourAbisLines\ 2\ ces
Validity Range
twoAbisLines
fourAbisLines
ces
<NULL>
Default Value
None.
Contained in the following commands:
GET COBA
BERT
bitErrorRateThreshold
This attribute defines thresholds allowed for a PCM30 or PCM24 line. The Bit Error Rate
is estimated using code violation counters. The specified thresholds influence the
setting of the corresponding status bits of the attribute 'lineStatusIndication'. When the
lower or upper threshold is reached, a failure event report is sent. Reaching the upper
threshold in a loop configuration triggers a direction switch.
Note: The values indicated as 'GET only' are values which were stored in a previous
release in the BTSE flash eprom when these values were still allowed in a SET
command.
Validity Range
In commands CREATE BPORT, SET BPORT:
lowerThreshold
E10_3
E10_4
...
E10_9
upperThreshold
E10_3
E10_4
E10_5
In commands GET BPORT:
lowerThreshold
E10_0
E10_1
600
Id:0900d8058051e6ce
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
...
E10_9
upperThreshold
E10_0
E10_1
...
E10_5
Default Value
In moc(s) BPORT:
None.
In moc(s) BPORT:
lowerThreshold
E10_5
upperThreshold
E10_3
Contained in the following commands:
CREATE BPORT, GET BPORT, SET BPORT
BMWD<x>
beamWidth<x>(degree)
Attribute data provided by the TMA.
Validity Range
0 - 65535
<NULL>
Default Value
None.
Contained in the following commands:
GET TMA
BND<x>
band<x>
Attribute data provided by the TMA.
Validity Range
operating_band_I
operating_band_II
operating_band_III
operating_band_IV
operating_band_V
A50016-G5100-B333-04-7619
Id:0900d8058051e6ce
601
BS-4x / 82 II / 240 / 241 / 240XL commands
operating_band_VI
operating_band_VII
operating_band_VIII
operating_band_IX
<NULL>
Default Value
None.
Contained in the following commands:
GET TMA
BSIC
bsIdentityCode
This attribute contains the Base Transceiver Station Identity Code (BSIC), which is
transmitted on the SCH and used for identifying a BTS. The BSIC consists of the
Network Colour Code (NCC) and the Base Station Colour Code (BCC).
Validity Range
BCC
0-7
NCC
0-7
Default Value
None.
Contained in the following commands:
GET BTS
BSWVER
bootSoftwareVersion
This attribute defines the firmware item code number. It can be read from the Boot
EPROM of each processor module. The values for this attribute are identical with the
SW image format (file ID and version) used in the swLoad-header-file. (exception: two
bootSoftwareVersions for the TPU) or 'Not Existing' for Modules that are not equipped
with a processor.
Each single field of the validity range has the following meaning.
bootSWfield 'BTBrrrhh.SWI', where:
rr BCX for COBA
BIX for CU
LMX for LMU (not used)
hh identical with the corresponding part of the bootSWversion
bootSwVersion 'cn-hh-vv-ii-ss-pp_yy-mm-dd, where:
602
Id:0900d8058051e6ce
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
cn Version part (network operator code)
hh Version part (HW/SW compatibility code)
vv Version part (feature package code)
ii Version part (sub-feature package code)
ss Version part (actual state)
pp Patch version (usually 00)
yy-mm-dd Production date (optional)
Validity Range
39..39 characters string
Default Value
None.
Contained in the following commands:
GET COBA, GET CU, GET FCUMAIN,
BTSID
baseStationId
Attribute data provided by the TMA.
Validity Range
0..32 characters string
Default Value
None.
Contained in the following commands:
GET TMA
BTSISHOP
btsIsHopping
This attribute indicates whether the BTS uses frequency hopping or not.
FALSE = Indicates that none of the channels in the BTS hops from the O&M point of
view; from radio signalling point of view this can mean either that there is really no
hopping at all or that there is hopping over a single frequency.
TRUE = Means that hopping is specified on a per channel basis.
Validity Range
TRUE
FALSE
Default Value
FALSE
A50016-G5100-B333-04-7619
Id:0900d8058051e6ce
603
BS-4x / 82 II / 240 / 241 / 240XL commands
Contained in the following commands:
GET BTS
BURNOFFS
burstNumberOffset
This attribute allows to adjust the burst number offset for a cell. Equal burst number
offsets result in synchronized TDMA frames.
This attribute is only meaningful if and the attribute enableInterSiteSync is set to 'TRUE'.
Validity Range
0-7
Default Value
0
Contained in the following commands:
GET BTS
604
Id:0900d8058051e6ce
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
c
CCPBL
carrierCapability
This attribute describes the call processing capabilities of the CU and FCUTR.
- In case of CU the attribute value is derived from the ESN/PID value of the CU.
- In case of FCUTR the attribute value depends on the istance number and the fcuMode
of the corrisponding FCUMAIN object.
The attribute is read-only from the Abis/LMT point of view (GET CU/ GET FCUTR). After
creation in advance of a CU/FCUTR object the attribute has the value "unknown" in case
of hh-ii =04-01.
The BTSE SW maps the values of the attribute carrierCapability to the values of the attribute trxCapability
In case of FCUTR object, the validity range is:
- unknown
- edge
- edgeFourRXdiv
- in case of FCUTR both the values 'edge' and 'edgeFourRXdiv' are mapped to 'trxCapability=edge'.
Validity Range
In commands GET CU:
unknown
gsm
edge
In commands GET FCUTR:
unknown
edge
edgeFourRxDiv
Default Value
None.
Contained in the following commands:
GET CU, GET FCUTR
CELLNO
cellNumber
A50016-G5100-B333-04-7619
Id:0900d80580592b9a
605
BS-4x / 82 II / 240 / 241 / 240XL commands
This attribute indicates the cell number to which a HW object for the antenna combining
(DILNA, DULNA, DUVSWR, FTNFP, FVSWRP, SDUSEC) is related to. It allows to have
more than one antenna combining object in a cell.
Validity Range
0 - 11
Default Value
None.
Contained in the following commands:
CREATE DILNA, CREATE DULNA, CREATE DUVSWR, CREATE F6LNA, CREATE
F6VSWRP, CREATE FTNFP, CREATE FVSWRP, GET DILNA, GET DULNA, GET
DUVSWR, GET F6LNA, GET F6VSWRP, GET FTNFP, GET FVSWRP,
CELLTYPE
cellType
This attribute indicates the type of cell. It is used by BTSE for compatibility checks of the
HW of a cell.
Validity Range
STDCELL
EXTCELL
DBSTDCELL
Default Value
None.
Contained in the following commands:
GET BTS
CHIDT
changeOnIDT
This attribute indicates a potential change of the IDTwF file. Whenever the IDFwF file
was uploaded by the BSC the value is set to 'no change on IDT'. If a change of objects
and attributes with relation to the IDT file occurs the value is set to 'IDT was changed'.
If a local download of IDT data is done the value must be set manually to 'IDT was
changed'.
Validity Range
noChangeOnIDT
IDTWasChanged
Default Value
IDTWasChanged
606
Id:0900d80580592b9a
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Contained in the following commands:
GET BTSEP NOSWL, SET BTSEP
CHTYPE
channelCombination
This attribute defines the logical channel combination mapped onto
the physical channel (timeslot).Changing or setting this attribute
means a temporary loss of service for the whole TRX.
00 TCHFULL:
TCH/F + FACCH/F + SACCH/TF
03 SDCCH:
SDCCH/8 + SACCH/C8
Note 3
04 MAINBCCH:
FCCH + SCH + BCCH + CCCH
Note 4
05 MBCCHC:
FCCH + SCH + BCCH + CCCH
+SDCCH/4 + SACCH/C4
Note 4
06 CCCH:
BCCH + CCCH
Note 5
07 SCBCH:
SDCCH/8 + SACCH/C8 + CBCH
Note
1/6
08 BCBCH:
FCCH + SCH + BCCH + CCCH +
SDCCH/4 + SACCH/4 + CBCH
Note
1/7
09
TCHF_HLF:
TCH/H(0,1) + FACCH/H(0,1) +
SACCH/TH (0,1) or TCH/F + FACCH/F +
SACCH/TF
Note 2
0A TCHSD:
TCH/H(0,1) + FACCH/H(0,1) +
SACCH/TH (0,1) or TCH/F + FACCH/F +
SACCH/TF or SDCCH/8 + SACCH/C8
Note
2/3
Note 1:
These two channel combinations are created by
replacing the logical channel SDCCH number 2 with
the CBCH channel.
Note 2:
The actual mode is decided on a per call basis.
Note 3:
Not allowed for CHAN #0 of BCCH-TRX. Only
allowed up to 3 times together with SDCCH/4 on
BCCH-TRX. With no SDCCH/4 on the BCCH
carrier up to four SDCCH/8 are allowed on the
BCCH carrier. (For hh=04 this restriction may be
dropped in a later release).
Note 4:
Allowed only for CHAN #0 of BCCH-TRX.
Note 5:
Allowed only for CHAN #2, #4, #6 of BCCH-TRX.
Not allowed together with SDCCH/4.
Note 6:
Allowed only for CHAN #0, #1, #2, #3. Not allowed
for CHAN #0 of BCCH-TRX. Only one CBCH is
allowed per cell.
A50016-G5100-B333-04-7619
Id:0900d80580592b9a
607
BS-4x / 82 II / 240 / 241 / 240XL commands
Note 7:
Only one CBCH is allowed per cell.
Note 8:
BSC checks guarantee that the first SDCCH/8 is
created on the BCCH TRX and that a CBCH is
allowed only on the BCCH TRX.
where:
TCH =
Traffic Channel
FACCH =
Fast Associated Control Channel
SACCH =
Slow Associated Control Channel
/H =
Half Rate
/F =
Full Rate
FCCH =
Frequency Correction Channel
SCH =
Synchronization Channel
BCCH =
Broadcast Control Channel
CCCH =
Common Control Channel (CCCH = PCH + RACH
+ AGCH)
PCH =
Paging Channel
RACH =
Random Access Channel
AGCH =
Access Grant Channel
CBCH =
Cell Broadcast Channel
The SDCCH combinations for the BCCH-TRX can be summarized as
follows:
1 MAIN BCCH + 4 SDCCH/8
1 MAIN BCCH COMBINED (SDCCH/4) + 3 SDCCH/8
1 MAIN BCCH + SCBCH (SDCCH/7) + 3 SDCCH/8
1 BCBCH (SDCCH/3) + 3 SDCCH/8
Validity Range
TCHFULL
SDCCH
MAINBCCH
MBCCHC
CCCH
SCBCH
BCBCH
TCHF_HLF
TCHSD
Default Value
None.
608
Id:0900d80580592b9a
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Contained in the following commands:
GET CHAN
CLKACC
clockAccuracy
This attribute indicates the accuracy of the clock.
Validity Range
high
medium
low
phase
Default Value
None.
Contained in the following commands:
GET SYNCBTSE
COMBMD
combMode
This attribute describes the combining mode of ACOM, DUVSWR (DUAMCO_VSRW),
DULNA (DUAMCO_LNA) and DILNA(DIAMCO_LNA) . The "n:m" values listed below
have the meaning "n RF inputs are combined to m RF output(s) by the ACOM,
DUAMCO/FDUAMCO or DIAMCO board ". The values are not checked by BTSE applications, the values are only stored for the convenience of the operator.
Validity Range
In commands CREATE DILNA, GET DILNA:
EightToTwo
In commands CREATE DULNA, CREATE DUVSWR, GET DULNA, GET DUVSWR:
OneToOne
TwoToOne
TwoToTwo
FourToTwo
EightToTwo
TwoToOneCOAMCO8
Default Value
In moc(s) DULNA, DUVSWR:
None.
In moc(s) DILNA:
A50016-G5100-B333-04-7619
Id:0900d80580592b9a
609
BS-4x / 82 II / 240 / 241 / 240XL commands
EightToTwo
Contained in the following commands:
CREATE DILNA, CREATE DULNA, CREATE DUVSWR, GET DILNA, GET DULNA,
GET DUVSWR
CUCONF
carrierUnitConfiguration
This attributes describes, if in a cell a homogeneous configuration of
carrier units is present (default value) or if one of the defined exceptions is configured.
The following configurations are defined:
-
CU_FlexCU_BS82II: This value has to be set if the cell is
served by a BS82II and has an inhomogeneous carrier unit
configuration with FlexCU and CU/ECU/GCU.
CU_ECU_DCSPCS: This value has to be set if the cell has an
inhomogeneous carrier unit configuration with old 1800/1900
MHz CUs (45.3 dBm output power) and ECU V2/3/3a of the
same frequency band. This value replaces the former setting
of the CU attribute maxGMSKOutputPower to dBm46_3.
homogeneous: This value has to be set if the carrier unit configuration is homogeneous or shall be considered as homogeneous. All carrier units use the maximum output power, which
is provided by the hardware. No adaptation of the output
power is performed. This implies, that output power differences greater than 2 dB will be accepted. This setting corresponds to the current system behaviour.
Validity Range
homogenous
CU_FlexCU_BS82II
CU_ECU_DCSPCS
Default Value
homogeneous
Contained in the following commands:
GET BTS
CUWIRING
cuWiring
The attribute describes the Tx and Rx wiring of the CU to the combining equipment. The
attribute identifier cannot be present in the listOfRequiredAttributes together attribute
610
Id:0900d80580592b9a
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
identifiers; the attribute is not sent by the BTSE if a Get CU is done without the information element listOfRequiredAttributes.
Below are indicated some details about the validity range.
choice tag:
1 0-3 optional subfields of fixed length follow (length=4-16)
txWiringPresence: (present only if choice tag is 1)
1 the next 4 bytes contain object class & instance of the object wired to the TX output
0 object class & instance don't follow
rxNWiringPresence: (present only if choice tag is 1, Octet position is variable)
1 the next 4 bytes contain object class & instance of the object wired to the RX output N
0 object class & instance don't follow
rxDWiringPresence: (present only if choice tag is 1, Octet position is variable)
1 the next 4 bytes contain object class & instance of the object wired to the RX output D
0 object class & instance don't follow
Validity Range
<ANY>
Default Value
None.
Contained in the following commands:
GET CU WIRING
A50016-G5100-B333-04-7619
Id:0900d80580592b9a
611
BS-4x / 82 II / 240 / 241 / 240XL commands
d
DESTDIR
destinationDir
Destination directory
This attribute specifies the directory on the LMT hard disk where the
BTSE alarm buffer sw will be copied (UPLBTSLOG).
This attribute specifies the directory on the LMT hard disk where the
IDT file will be copied (UPLLIDF).
Validity Range
1..80 characters string
Default Value
None.
Contained in the following commands:
UPLBTSLOG SOFTWARE-MANAGEMENT, UPLLIDF REMINV
DLTESTFREQ
dlTestFrequency
This attribute defines the transmit frequency (ARFCN value) if the downlink interference
analysis mode is enabled.
Validity Range
<ANY>
Default Value
None.
Contained in the following commands:
GET TRX
DMACFHSYID
dmaCFHSyId
This attribute is used for distinguishing DMA-enabled TRXs, which are operating on different frequency bands or at different subbands in the same cell.
Validity Range
usedOnCFHSY0
usedOnCFHSY1
612
Id:0900d8058024e34f
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
notUsed
Default Value
DMA not used on TRX
Contained in the following commands:
GET TRX
DMCFWID
duamcoFwId
This attribute provides information of the file ID and the FW version that is active on a
MFDUAMCO board.
Validity Range
39..39 characters string
Default Value
None.
Contained in the following commands:
GET DUAMCO
DTMHOMTIMER
hoDTMTimer(SACCH_multiframe_480/470ms)
This attribute determines whether handover due to DTM(Dual Transfer Mode) power
budget is enabled.
This attribute is only relevant if inter-cell handover is enabled in the cell (see attribute
enableInterCellHO).
DTM Power budget handover means: handover to another cell if this cell offers a higher
transmission level. No matter if the power level of the actual cell is above the minimum
or not.
Validity Range
1 - 21
Default Value
None.
Contained in the following commands:
GET BTS
DYNTRACGRAN
dynTraceGranularity
A50016-G5100-B333-04-7619
Id:0900d8058024e34f
613
BS-4x / 82 II / 240 / 241 / 240XL commands
dynTraceGranularity is an attribute of the BTSM and specifies the granularity (multiples
of SACCH reporting period) in which the TRACE MEASUREMENT RESULT messages
are transmitted on the Abis interface in case the trace is activated. A value of N means
that every N-th message is transmitted. The trace is activated per channel via the
acknowledged message START TRACE. The trace is stopped via the acknowledged
message STOP TRACE on the radio signalling link; it is stopped also implicitly at a
release of the channel.
The validity range is indicated in number of "SACCH multiframes"
Validity Range
1 - 254
Default Value
1
Contained in the following commands:
GET BTSM NOSWL
614
Id:0900d8058024e34f
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
e
EAC
enableAc
This attribute determines, whether Admission Control evaluation must be performed. A
change of the attribute becomes effective in the next AC period.
(TRUE = AC evaluation enabled)
Validity Range
TRUE
FALSE
Default Value
FALSE (AC evaluation disabled)
Contained in the following commands:
GET BTS
EANTHOP
enableAntennaHopping
This attribute indicates whether Antenna Hopping is enabled or disabled for BTS. All
TRX which are not connected to FICOM will hop.
A change of the attribute becomes effective with starting time algorithm handled internally by the BTSE.
TRUE = enabled
Validity Range
TRUE
FALSE
Default Value
FALSE (disabled)
Contained in the following commands:
GET BTS
EAUTONEG
enableAutoNegotiation
The attribute indicates whether the Ethernet auto negotiation for speed, duplex mode
and optionally flow control is enabled for the instance of an Ethernet port.
If auto negotiation is disabled the speed will be set to 100M and duplex mode will be
enabled. Also in case when this attribute is set to TRUE there will be propagated only
A50016-G5100-B333-04-7619
Id:0900d8058024e358
615
BS-4x / 82 II / 240 / 241 / 240XL commands
100M and duplex mode. If the peer Ethernet device cannot provide 100M Duplex mode,
then the link remains down. Only FlowControl is really negotiated according to the
setting of the attribute "enableFlowControl".
AutoNegotiation is only relevant for electrical Ethernet interfaces.
Validity Range
TRUE
FALSE
Default Value
TRUE
Contained in the following commands:
CREATE ETHPORT, GET ETHPORT, SET ETHPORT
EAUTOREC
enableAutoRecovery
This attribute indicates whether an automatic recovery is enabled or disabled. Prerequisites for an automatic recovery in case the feature is enabled are:
- HW-Reset cause is "Power-On"
- The board is disabled.failed.unlocked
Validity Range
disabled
enabled
Default Value
disabled
Contained in the following commands:
GET BTSEP NOSWL, SET BTSEP
EEOTD
enableEOTD
This attribute indicates if the Location Services (LCS) positioning method 'Enhanced
Observed Time difference' (EOTD) is being used.
(TRUE = enabled)
Validity Range
TRUE
FALSE
616
Id:0900d8058024e358
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Default Value
FALSE (disabled)
Contained in the following commands:
GET BTS
EEXCDIST
enableExcessiveDistance
This attribute indicates whether the sending of call release is enabled/disabled when the
distance between Mobile Station and BTS exceeds the excessive distance.
TRUE = enabled
Validity Range
FALSE
TRUE
Default Value
TRUE (enabled)
Contained in the following commands:
GET BTS
EFCUSUP
enableFcuSupport
For a COB4P12, 'TRUE' is the only possible value and will be
assigned by the BTSE-software in case no value is provided by the
operator; the attribute value 'TRUE' cannot be changed by the operator.
For COBA2P8 both values are possible.
- 'FALSE' will be assigned by the BTSE-software in case no value is
provided by the operator. In this case the BTSE handles up to 24 CU
boards (distributed to rack 0-2). If enableFcuSupport is set to
'FALSE', the creation of the objects FCUMAIN / FCUTR is possible
but any created objects FCUMAIN / FCUTR will remain in state: operationalState 'DISABLED', availabilityStatus 'Not Installed'.
- 'TRUE' means that the BTSE can handle only up to 12 boards.
Within these 12 boards (allowed only in base rack in case of
BTS240XL, respectively allowed only in base rack and the first 4
instances of 1st extension-rack in case of BTS240 distributed to rack
0-2) any mix of CU boards and FlexCU boards (modeled as
FCUMAIN and FCUTR objects) is possible.
--> The creation of any boards (CU or FlexCU) will be answered with
a NACK by the BTSE, if:
A50016-G5100-B333-04-7619
Id:0900d8058024e358
617
BS-4x / 82 II / 240 / 241 / 240XL commands
typeofBTSE is BS240XL and the board to be created is in the
extension rack
typeofBTSE is BS240 and the board to be created is in the 1st
extension rack and would have an instance number greater 3,
or is in the 2nd extension rack.
A change of the attribute value is possible only on a COBA2P8 and
causes a reset of the BTSE. In LMTphase 3 a change of the attribute
value is allowed only if the administrativeState of BTSM is 'Locked'.
--> The BTSE SW will answer with a NACK if the operator tries to set
the attribute to 'TRUE' if:
-
typeofBTSE is BS240XL and a board (FlexCU or CU) is
created in an extension rack
typeofBTSE is BS240 and a FlexCU or CU with an instance
greater than 3 is created in 1st extension rack or any instance
is created in 2nd extension rack.
The value FALSE in the validity range means:
support of FLEXCU disabled
The value TRUE in the validity range means:
support of FLEXCU enabled
Validity Range
TRUE
FALSE
Default Value
None.
Contained in the following commands:
CREATE COBA, GET COBA, SET COBA
EFLWCTRL
enableFlowControl
The attribute enables the Ethernet flow control. Flow control requires full duplex operation. Received Ethernet PAUSE frames are ignored if set to false.
The following attribute is relevant: enableAutonegotiation
Validity Range
TRUE
FALSE
618
Id:0900d8058024e358
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Default Value
FALSE
Contained in the following commands:
CREATE ETHPORT, GET ETHPORT, SET ETHPORT
EINTSITSYN
enableInterSiteSync
The attribute enableInterSiteSync allows to disable or enable the inter site synchronization.
If intersite synchronisation is enabled, the BTS attributes burstNumberOffset and frameNumberOffset become effective. As a result different transceivers of the same BTSE
may have asynchronous frame and burst numbers.
TRUE = enabled
Validity Range
TRUE
FALSE
Default Value
FALSE (disabled)
Contained in the following commands:
GET BTSM NOSWL
EMT1
emergencyTimer1(min)
This attribute specifies after which time (minutes) the BTSE will be switched to an emergency configuration if a "battery backup operation" (due to "mains breakdown") occurs.
The switch includes the power-down of TRX related equipment.
BS241: emerg. timer starts if first ACDC fails.
(step size 1 minute)
Validity Range
0 - 1400
Default Value
10 minutes
Contained in the following commands:
GET BTSM NOSWL
A50016-G5100-B333-04-7619
Id:0900d8058024e358
619
BS-4x / 82 II / 240 / 241 / 240XL commands
EMT2
emergencyTimer2(min)
This attribute specifies after which time (minutes) the BTSE will be switched to a zero
carrier configuration if a switch to emergency configuration has been performed due to
a "battery backup operation". The switch includes the power-down of TRX related equipment. The value 0 means the emergencyTimer2 is not valid, i.e. the BTSE will not switch
to a zero carrier configuration. For other values the zero carrier configuration will be
reached after the sum of the times specified in emergencyTimer1 and
emergencyTimer2.
Validity Range
0 - 1400
Default Value
0 minutes
Contained in the following commands:
GET BTSM NOSWL
ENTRIES
entries
Number of entries
This attribute is used to indicate the number of the entries to be
uploaded.
Validity Range
Number of the requested Entries <1-65534>
Getting all Entries stored in the buffer 65535
For the upload of MIB_DATA_HW_STATES only the value 65535 is used.
For the upload of INVENTORY_DATA_TABLE, MIT and SCA the attribute has no
meaning.
Default Value
None.
Contained in the following commands:
UPLBTSLOG SOFTWARE-MANAGEMENT
EQUPOS
equipmentPosition
The attribute contains the room / row and rack number as 6 ASCII characters not terminated by a NUL character. The attribute should be set by the operator before a upload
of the IDT is performed.
620
Id:0900d8058024e358
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
6..6 characters string
Default Value
"010101"
Contained in the following commands:
GET BTSEP NOSWL, SET BTSEP
ERFACCHALPDMF
enableRFacchOnAnyLapdmFrame
This attribute determines whether the feature DL Repeated FACCH is enabled on a per
cell basis for different codec types and only for those MS that have signaled their
Repeated FACCH Capability as 1. To enable R-FACCH on any LAPDm command and
response frame for a certain codec in the cell the name of that codec shall be entered
in a list.
See Appendix for the values.
Validity Range
NOT_SET
AFS
AHS
AFS_AHS
EFS
AFS_EFS
AHS_EFS
AFS_AHS_EFS
FS
AFS_FS
AHS_FS
AFS_AHS_FS
EFS_FS
AFS_EFS_FS
AHS_EFS_FS
AFS_AHS_EFS_FS
HS
AFS_HS
AHS_HS
AFS_AHS_HS
A50016-G5100-B333-04-7619
Id:0900d8058024e358
621
BS-4x / 82 II / 240 / 241 / 240XL commands
EFS_HS
AFS_EFS_HS
AHS_EFS_HS
AFS_AHS_EFS_HS
FS_HS
AFS_FS_HS
AHS_FS_HS
AFS_AHS_FS_HS
EFS_FS_HS
AFS_EFS_FS_HS
AHS_EFS_FS_HS
AFS_AHS_EFS_FS_HS
WFS
AFS_WFS
AHS_WFS
AFS_AHS_WFS
EFS_WFS
AFS_EFS_WFS
AHS_EFS_WFS
AFS_AHS_EFS_WFS
FS_WFS
AFS_FS_WFS
AHS_FS_WFS
AFS_AHS_FS_WFS
EFS_FS_WFS
AFS_EFS_FS_WFS
AHS_EFS_FS_WFS
AFS_AHS_EFS_FS_WFS
HS_WFS
AFS_HS_WFS
AHS_HS_WFS
AFS_AHS_HS_WFS
EFS_HS_WFS
AFS_EFS_HS_WFS
AHS_EFS_HS_WFS
AFS_AHS_EFS_HS_WFS
622
Id:0900d8058024e358
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FS_HS_WFS
AFS_FS_HS_WFS
AHS_FS_HS_WFS
AFS_AHS_FS_HS_WFS
EFS_FS_HS_WFS
AFS_EFS_FS_HS_WFS
AHS_EFS_FS_HS_WFS
AFS_AHS_EFS_FS_HS_
WFS
Default Value
None.
Contained in the following commands:
GET BTS
ERFACCHCMDF
enableRFacchOnCmdFrames
This attribute determines whether the feature DL Repeated FACCH is enabled on a per
cell basis for different codec types and only for those MS that have signaled their
Repeated FACCH Capability as 1. To enable R-FACCH on any LAPDm command and
response frame for a certain codec in the cell the name of that codec shall be entered
in a list.
See Appendix for the values.
Validity Range
NOT_SET
AFS
AHS
AFS_AHS
EFS
AFS_EFS
AHS_EFS
AFS_AHS_EFS
FS
AFS_FS
AHS_FS
AFS_AHS_FS
EFS_FS
AFS_EFS_FS
A50016-G5100-B333-04-7619
Id:0900d8058024e358
623
BS-4x / 82 II / 240 / 241 / 240XL commands
AHS_EFS_FS
AFS_AHS_EFS_FS
HS
AFS_HS
AHS_HS
AFS_AHS_HS
EFS_HS
AFS_EFS_HS
AHS_EFS_HS
AFS_AHS_EFS_HS
FS_HS
AFS_FS_HS
AHS_FS_HS
AFS_AHS_FS_HS
EFS_FS_HS
AFS_EFS_FS_HS
AHS_EFS_FS_HS
AFS_AHS_EFS_FS_HS
WFS
AFS_WFS
AHS_WFS
AFS_AHS_WFS
EFS_WFS
AFS_EFS_WFS
AHS_EFS_WFS
AFS_AHS_EFS_WFS
FS_WFS
AFS_FS_WFS
AHS_FS_WFS
AFS_AHS_FS_WFS
EFS_FS_WFS
AFS_EFS_FS_WFS
AHS_EFS_FS_WFS
AFS_AHS_EFS_FS_WFS
HS_WFS
AFS_HS_WFS
624
Id:0900d8058024e358
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
AHS_HS_WFS
AFS_AHS_HS_WFS
EFS_HS_WFS
AFS_EFS_HS_WFS
AHS_EFS_HS_WFS
AFS_AHS_EFS_HS_WFS
FS_HS_WFS
AFS_FS_HS_WFS
AHS_FS_HS_WFS
AFS_AHS_FS_HS_WFS
EFS_FS_HS_WFS
AFS_EFS_FS_HS_WFS
AHS_EFS_FS_HS_WFS
AFS_AHS_EFS_FS_HS_
WFS
Default Value
None.
Contained in the following commands:
GET BTS
ERSACCHDL
enableRSacchDL
The attribute is implemented as a list of values representing combinations of signaling
and allowed codec types and/or signaling. This list is present in Appendix.
For the binary representation 0 means that R-SACCH in DL on a per cell basis is not
applied for specified speech codec type and /or signaling. Value 1 means that R-SACCH
in DL is applied for specified speech codec type and/or signaling.
Value 0x00 has specific meaning and should be read as R-SACCH in DL is not applied
for any speech codec type.
When enabling R-SACCH feature on BTS, where only old CUs are created, SET is
acked but ignored locally.
Validity Range
NOT_SET
AFS
AHS
AFS_AHS
EFS
A50016-G5100-B333-04-7619
Id:0900d8058024e358
625
BS-4x / 82 II / 240 / 241 / 240XL commands
AFS_EFS
AHS_EFS
AFS_AHS_EFS
FS
AFS_FS
AHS_FS
AFS_AHS_FS
EFS_FS
AFS_EFS_FS
AHS_EFS_FS
AFS_AHS_EFS_FS
HS
AFS_HS
AHS_HS
AFS_AHS_HS
EFS_HS
AFS_EFS_HS
AHS_EFS_HS
AFS_AHS_EFS_HS
FS_HS
AFS_FS_HS
AHS_FS_HS
AFS_AHS_FS_HS
EFS_FS_HS
AFS_EFS_FS_HS
AHS_EFS_FS_HS
AFS_AHS_EFS_FS_HS
WFS
AFS_WFS
AHS_WFS
AFS_AHS_WFS
EFS_WFS
AFS_EFS_WFS
AHS_EFS_WFS
AFS_AHS_EFS_WFS
FS_WFS
626
Id:0900d8058024e358
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
AFS_FS_WFS
AHS_FS_WFS
AFS_AHS_FS_WFS
EFS_FS_WFS
AFS_EFS_FS_WFS
AHS_EFS_FS_WFS
AFS_AHS_EFS_FS_WFS
HS_WFS
AFS_HS_WFS
AHS_HS_WFS
AFS_AHS_HS_WFS
EFS_HS_WFS
AFS_EFS_HS_WFS
AHS_EFS_HS_WFS
AFS_AHS_EFS_HS_WFS
FS_HS_WFS
AFS_FS_HS_WFS
AHS_FS_HS_WFS
AFS_AHS_FS_HS_WFS
EFS_FS_HS_WFS
AFS_EFS_FS_HS_WFS
AHS_EFS_FS_HS_WFS
AFS_AHS_EFS_FS_HS_
WFS
SIGNALING
AFS_SIGNALING
AHS_SIGNALING
AFS_AHS_SIGNALING
EFS_SIGNALING
AFS_EFS_SIGNALING
AHS_EFS_SIGNALING
AFS_AHS_EFS_SIGNALIN
G
FS_SIGNALING
AFS_FS_SIGNALING
AHS_FS_SIGNALING
A50016-G5100-B333-04-7619
Id:0900d8058024e358
627
BS-4x / 82 II / 240 / 241 / 240XL commands
AFS_AHS_FS_SIGNALIN
G
EFS_FS_SIGNALING
AFS_EFS_FS_SIGNALING
AHS_EFS_FS_SIGNALIN
G
AFS_AHS_EFS_FS_SIGN
ALING
HS_SIGNALING
AFS_HS_SIGNALING
AHS_HS_SIGNALING
AFS_AHS_HS_SIGNALIN
G
EFS_HS_SIGNALING
AFS_EFS_HS_SIGNALIN
G
AHS_EFS_HS_SIGNALIN
G
AFS_AHS_EFS_HS_SIGN
ALING
FS_HS_SIGNALING
AFS_FS_HS_SIGNALING
AHS_FS_HS_SIGNALING
AFS_AHS_FS_HS_SIGNA
LING
EFS_FS_HS_SIGNALING
AFS_EFS_FS_HS_SIGNA
LING
AHS_EFS_FS_HS_SIGNA
LING
AFS_AHS_EFS_FS_HS_S
IGNALING
WFS_SIGNALING
AFS_WFS_SIGNALING
AHS_WFS_SIGNALING
AFS_AHS_WFS_SIGNALI
NG
EFS_WFS_SIGNALING
AFS_EFS_WFS_SIGNALI
NG
628
Id:0900d8058024e358
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
AHS_EFS_WFS_SIGNALI
NG
AFS_AHS_EFS_WFS_SIG
NALING
FS_WFS_SIGNALING
AFS_FS_WFS_SIGNALIN
G
AHS_FS_WFS_SIGNALIN
G
AFS_AHS_FS_WFS_SIGN
ALING
EFS_FS_WFS_SIGNALIN
G
AFS_EFS_FS_WFS_SIGN
ALING
AHS_EFS_FS_WFS_SIGN
ALING
AFS_AHS_EFS_FS_WFS_
SIGNALING
HS_WFS_SIGNALING
AFS_HS_WFS_SIGNALIN
G
AHS_HS_WFS_SIGNALIN
G
AFS_AHS_HS_WFS_SIGN
ALING
EFS_HS_WFS_SIGNALIN
G
AFS_EFS_HS_WFS_SIGN
ALING
AHS_EFS_HS_WFS_SIGN
ALING
AFS_AHS_EFS_HS_WFS
_SIGNALING
FS_HS_WFS_SIGNALING
AFS_FS_HS_WFS_SIGNA
LING
AHS_FS_HS_WFS_SIGNA
LING
AFS_AHS_FS_HS_WFS_
SIGNALING
A50016-G5100-B333-04-7619
Id:0900d8058024e358
629
BS-4x / 82 II / 240 / 241 / 240XL commands
EFS_FS_HS_WFS_SIGNA
LING
AFS_EFS_FS_HS_WFS_S
IGNALING
AHS_EFS_FS_HS_WFS_
SIGNALING
AFS_AHS_EFS_FS_HS_
WFS_SIGNALING
Default Value
None.
Contained in the following commands:
GET BTS
ERSACCHUL
enableRSacchUL
The attribute is implemented as a list of values representing combinations of signaling
and allowed codec types and/or signaling. This list is present in Appendix.
For the binary representation 0 means that R-SACCH in DL on a per cell basis is not
applied for specified speech codec type and /or signaling. Value 1 means that RSACCH in DL is applied for specified speech codec type and/or signaling.
Value 0x00 has specific meaning and should be read as R-SACCH in DL is not applied
for any speech codec type.
This attribute is used to enable the featureR-SACCH in UL on a per cell basis for different codec types and /or signaling only for MS with R-ACCH_CAP = 1.
When enabling R-SACCH feature on BTS, where only old CUs are created, SET is
acked but ignored locally.
Validity Range
NOT_SET
AFS
AHS
AFS_AHS
EFS
AFS_EFS
AHS_EFS
AFS_AHS_EFS
FS
AFS_FS
AHS_FS
AFS_AHS_FS
630
Id:0900d8058024e358
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
EFS_FS
AFS_EFS_FS
AHS_EFS_FS
AFS_AHS_EFS_FS
HS
AFS_HS
AHS_HS
AFS_AHS_HS
EFS_HS
AFS_EFS_HS
AHS_EFS_HS
AFS_AHS_EFS_HS
FS_HS
AFS_FS_HS
AHS_FS_HS
AFS_AHS_FS_HS
EFS_FS_HS
AFS_EFS_FS_HS
AHS_EFS_FS_HS
AFS_AHS_EFS_FS_HS
WFS
AFS_WFS
AHS_WFS
AFS_AHS_WFS
EFS_WFS
AFS_EFS_WFS
AHS_EFS_WFS
AFS_AHS_EFS_WFS
FS_WFS
AFS_FS_WFS
AHS_FS_WFS
AFS_AHS_FS_WFS
EFS_FS_WFS
AFS_EFS_FS_WFS
AHS_EFS_FS_WFS
AFS_AHS_EFS_FS_WFS
A50016-G5100-B333-04-7619
Id:0900d8058024e358
631
BS-4x / 82 II / 240 / 241 / 240XL commands
HS_WFS
AFS_HS_WFS
AHS_HS_WFS
AFS_AHS_HS_WFS
EFS_HS_WFS
AFS_EFS_HS_WFS
AHS_EFS_HS_WFS
AFS_AHS_EFS_HS_WFS
FS_HS_WFS
AFS_FS_HS_WFS
AHS_FS_HS_WFS
AFS_AHS_FS_HS_WFS
EFS_FS_HS_WFS
AFS_EFS_FS_HS_WFS
AHS_EFS_FS_HS_WFS
AFS_AHS_EFS_FS_HS_
WFS
SIGNALING
AFS_SIGNALING
AHS_SIGNALING
AFS_AHS_SIGNALING
EFS_SIGNALING
AFS_EFS_SIGNALING
AHS_EFS_SIGNALING
AFS_AHS_EFS_SIGNALIN
G
FS_SIGNALING
AFS_FS_SIGNALING
AHS_FS_SIGNALING
AFS_AHS_FS_SIGNALIN
G
EFS_FS_SIGNALING
AFS_EFS_FS_SIGNALING
AHS_EFS_FS_SIGNALIN
G
AFS_AHS_EFS_FS_SIGN
ALING
HS_SIGNALING
632
Id:0900d8058024e358
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
AFS_HS_SIGNALING
AHS_HS_SIGNALING
AFS_AHS_HS_SIGNALIN
G
EFS_HS_SIGNALING
AFS_EFS_HS_SIGNALIN
G
AHS_EFS_HS_SIGNALIN
G
AFS_AHS_EFS_HS_SIGN
ALING
FS_HS_SIGNALING
AFS_FS_HS_SIGNALING
AHS_FS_HS_SIGNALING
AFS_AHS_FS_HS_SIGNA
LING
EFS_FS_HS_SIGNALING
AFS_EFS_FS_HS_SIGNA
LING
AHS_EFS_FS_HS_SIGNA
LING
AFS_AHS_EFS_FS_HS_S
IGNALING
WFS_SIGNALING
AFS_WFS_SIGNALING
AHS_WFS_SIGNALING
AFS_AHS_WFS_SIGNALI
NG
EFS_WFS_SIGNALING
AFS_EFS_WFS_SIGNALI
NG
AHS_EFS_WFS_SIGNALI
NG
AFS_AHS_EFS_WFS_SIG
NALING
FS_WFS_SIGNALING
AFS_FS_WFS_SIGNALIN
G
AHS_FS_WFS_SIGNALIN
G
A50016-G5100-B333-04-7619
Id:0900d8058024e358
633
BS-4x / 82 II / 240 / 241 / 240XL commands
AFS_AHS_FS_WFS_SIGN
ALING
EFS_FS_WFS_SIGNALIN
G
AFS_EFS_FS_WFS_SIGN
ALING
AHS_EFS_FS_WFS_SIGN
ALING
AFS_AHS_EFS_FS_WFS_
SIGNALING
HS_WFS_SIGNALING
AFS_HS_WFS_SIGNALIN
G
AHS_HS_WFS_SIGNALIN
G
AFS_AHS_HS_WFS_SIGN
ALING
EFS_HS_WFS_SIGNALIN
G
AFS_EFS_HS_WFS_SIGN
ALING
AHS_EFS_HS_WFS_SIGN
ALING
AFS_AHS_EFS_HS_WFS
_SIGNALING
FS_HS_WFS_SIGNALING
AFS_FS_HS_WFS_SIGNA
LING
AHS_FS_HS_WFS_SIGNA
LING
AFS_AHS_FS_HS_WFS_
SIGNALING
EFS_FS_HS_WFS_SIGNA
LING
AFS_EFS_FS_HS_WFS_S
IGNALING
AHS_EFS_FS_HS_WFS_
SIGNALING
AFS_AHS_EFS_FS_HS_
WFS_SIGNALING
Default Value
None.
634
Id:0900d8058024e358
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Contained in the following commands:
GET BTS
ETOP
enableTOP
This attribute determines whether TOP(Temporary Overpower) is enabled or disabled
on cell basis for the specified codec type. See Appendix for the values.
Validity Range
NOT_SET
AFS
AHS
AFS_AHS
EFS
AFS_EFS
AHS_EFS
AFS_AHS_EFS
FS
AFS_FS
AHS_FS
AFS_AHS_FS
EFS_FS
AFS_EFS_FS
AHS_EFS_FS
AFS_AHS_EFS_FS
HS
AFS_HS
AHS_HS
AFS_AHS_HS
EFS_HS
AFS_EFS_HS
AHS_EFS_HS
AFS_AHS_EFS_HS
FS_HS
AFS_FS_HS
AHS_FS_HS
AFS_AHS_FS_HS
A50016-G5100-B333-04-7619
Id:0900d8058024e358
635
BS-4x / 82 II / 240 / 241 / 240XL commands
EFS_FS_HS
AFS_EFS_FS_HS
AHS_EFS_FS_HS
AFS_AHS_EFS_FS_HS
WFS
AFS_WFS
AHS_WFS
AFS_AHS_WFS
EFS_WFS
AFS_EFS_WFS
AHS_EFS_WFS
AFS_AHS_EFS_WFS
FS_WFS
AFS_FS_WFS
AHS_FS_WFS
AFS_AHS_FS_WFS
EFS_FS_WFS
AFS_EFS_FS_WFS
AHS_EFS_FS_WFS
AFS_AHS_EFS_FS_WFS
HS_WFS
AFS_HS_WFS
AHS_HS_WFS
AFS_AHS_HS_WFS
EFS_HS_WFS
AFS_EFS_HS_WFS
AHS_EFS_HS_WFS
AFS_AHS_EFS_HS_WFS
FS_HS_WFS
AFS_FS_HS_WFS
AHS_FS_HS_WFS
AFS_AHS_FS_HS_WFS
EFS_FS_HS_WFS
AFS_EFS_FS_HS_WFS
AHS_EFS_FS_HS_WFS
AFS_AHS_EFS_FS_HS_
WFS
636
Id:0900d8058024e358
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Default Value
None.
Contained in the following commands:
GET BTS
ETXDIVTS
enableTxDivTimeShift
The attribute indicates whether Tx Diversity Time Shift is enabled or disabled for a BTS.
As a consequence all TRXs of the cell will operate in "double-power/half capacity" Mode
(called Coverage Mode) or in "normal-power/normal capacity" Mode (called Capacity
Mode).
The value 'TRUE' means that all CUs or FCUTRs in the a cell operate as CU pairs or
FCUTR pairs in a master slave mode. Pairs are defined as follows (k=0, 1, 2, etc.):
- A CU pair consists of the master CU (instance 2k) and the slave CU (instance 2k+1)
- A FCUTR pair consists of the master FCUTR (instance 2k) and the slave FCUTR
(instance 2k+1).
The two members of each pair should be wired to different antennas of the same cell
otherwise the combining loss would nullify the additional gain of the coverage mode. A
change of the attribute becomes effective after reconfiguration of the cell handled internally by the BTSE and causes a reset of the related CU or FCUMAIN objects. The BSC
takes care that the BTS object is locked whenever the value of the attribute is changed.
Validity Range
TRUE
FALSE
Default Value
FALSE (disabled)
Contained in the following commands:
GET BTS
EVTYP
eventType
This attribute specifies the type of failure event alarm.
Validity Range
COMMUNICATION_FAILU
RE_EVENT
A50016-G5100-B333-04-7619
Id:0900d8058024e358
637
BS-4x / 82 II / 240 / 241 / 240XL commands
QUAL_SERVICE_FAILUR
E_EVENT
PROCESSING_FAILURE_
EVENT
EQUIPMENT_FAILURE_E
VENT
ENVIRONMENTAL_FAILU
RE_EVENT
Default Value
None.
Contained in the following commands:
GETACTIVEALARMS BTSEP
EXCDIST
excessiveDistance(km)
This attribute indicates the distance limit to be used for call release when the distance
between Mobile Station and BTS exceeds the excessiveDistance. Value indicating more
35 km are valid only for extended cells. A change of the attribute becomes effective in
the next SACCH multiframe.
Validity Range
1 - 100
Default Value
100 Km
Contained in the following commands:
GET BTS
EXTMODE
extendedMode
This attribute indicates whether a channel instance operates in the extended mode
(usage of two radio timeslots) which is needed for extended cells. The value TRUE is
allowed only for even channel instances. Before an even channel instance N can be
created with the value TRUE for the extendedMode it must be guaranteed that channel
instance N+1 does not exist.
Validity Range
TRUE
FALSE
Default Value
FALSE
638
Id:0900d8058024e358
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Contained in the following commands:
GET CHAN
A50016-G5100-B333-04-7619
Id:0900d8058024e358
639
BS-4x / 82 II / 240 / 241 / 240XL commands
f
F6FWID
ficom6FwId
This attribute provides information of the file ID and the FW version that is active on
a FICOM6 board.
Validity Range
39..39 characters string
Default Value
None.
Contained in the following commands:
GET F6VSWRP
FACCHQ
facchQual
This attribute defines the number of FACCH (stealing flags minus 1) to be received for
detecting a FACCH frame.
(step size 1 FACCH frame)
Validity Range
0-7
Default Value
5
Contained in the following commands:
GET BTS
FACHBT
fachBusyThreshold(dBm)
This attribute defines a threshold for the received signal level during handover procedure when mobile station transmits HANDOVER ACCESS or ASCI uplink access burst
message on the FACCH (Fast Associated Control Channel). A signal exceeding this
threshold is interpreted as a busy FACCH.
Validity Range
<ANY>
Default Value
None.
640
Id:0900d805805ca193
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Contained in the following commands:
GET BTS
FBAND
frequencyBand
The attribute specifies the frequency band of the BCOM. It is highly recommended to set
this attribute to the correct value in order to ensure software checks for a consistent
wiring especially in case of dual band configurations.
It is the operator's responsibility to configure the correct value because the system
cannot check if the value fits to the equipped hardware.
Validity Range
Gsm850
Gsm900
Dcs1800
Pcs1900
NotSet
Default Value
NotSet
Contained in the following commands:
CREATE BCOM, GET BCOM, SET BCOM
FCUMAINWIRING
fcumainWiring
The attribute describes the Tx and Rx wiring of the FlexCU board to the combining
equipment. The attribute identifier cannot be present in the listOfRequiredAttributes
together with other attribute identifiers and it is not sent by the BTSE if a "Get FCUMAIN"
is done without the information element listOfRequiredAttributes.
The attribute is not visible at the RC.
Validity Range
choice tag
1 = 'variable'
tx0WiringPresence:
1 = the next 4 bytes contain object class & instance of the object wired to the TX output 0
0 = object class & instance don't follow
rxNWiringPresence: Octect position is variable
A50016-G5100-B333-04-7619
Id:0900d805805ca193
641
BS-4x / 82 II / 240 / 241 / 240XL commands
1 = the next 4 bytes contain object class & instance of the object wired to the RX output
N
0 = object class & instance don't follow
rxDWiringPresence: Octect position is variable
1 = the next 4 bytes contain object class & instance of the object wired to the RX output
D
0 = object class & instance don't follow
tx1WiringPresence: Octect position is variable
1 = the next 4 bytes contain object class & instance of the object wired to the TX output 1
0 = object class & instance don't follow
rxN1WiringPresence: Octect position is variable
1 = the next 4 bytes contain object class & instance of the object wired to the RX output
N1
0 = object class & instance don't follow
rxD1WiringPresence: Octect position is variable
1 = the next 4 bytes contain object class & instance of the object wired to the RX output
D1
0 = object class & instance don't follow
Default Value
None.
Contained in the following commands:
GET FCUMAIN WIRING
FCUMODE
fcuMode
This attribute specifies in which mode a FlexCU board shall operate.
A FlexCU in 'singleCUMode'
-
Does not allow the creation of the odd instance of the FCUTR
object;
Does not support the feature 'TX diversity time shift'. If the
value of the attribute 'enableTxDivTimeShift' is 'TRUE', an
appropriate FCUMAIN alarm is emitted and the FCUMAIN
and FCUTR instance are set to disabled;
Supports only 1 TRX with up to 4 RX branches
A FlexCU board in 'doubleCUMode' supports up to 2 TRX instances:
642
Id:0900d805805ca193
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Support of two TRX instances ('enableTxDivTimeShift' is
'FALSE');
Support of 1 TRX with 'TX diversity time shift' ('enableTxDivTimeShift' is 'TRUE').
Validity Range
singleCUMode
doubleCUMode
Default Value
doubleCUMode
Contained in the following commands:
CREATE FCUMAIN, GET FCUMAIN
FILE
file
This attribute specifies the file within the destinationDirectory on the LMT hard disk
where the BTSE alarm buffer sw will be copied (UPLBTSLOG) or where the IDT file will
be copied (UPLLIDF).
Validity Range
1..30 characters string
Default Value
None.
Contained in the following commands:
UPLBTSLOG SOFTWARE-MANAGEMENT, UPLLIDF REMINV
FILEFWV
fwVersion
This attribute states the name and version of the fwImage file. The file is transferred to
the dedicated board to perform the FW upgrade.
Validity Range
26..26 characters string
Default Value
None.
Contained in the following commands:
FWUPGRADE BTSM
A50016-G5100-B333-04-7619
Id:0900d805805ca193
643
BS-4x / 82 II / 240 / 241 / 240XL commands
FILEID
fileId
The FileId is a parameter used within the SW download procedures
and not of the type 'GET'. The corresponding attribute is swLoadCurrentFileId and is related only to the swLoad-header file. All characters of the ASCII string are to be in upper case. However, the SW
parts in the BTSE handling the file Id are to be case tolerant.
This attribute is a string of 12 alphanumerical characters with the following format:
ASCII String for:
For download
of test SW from
local LMT acc.
For download
of boot SW
from local LMT
acc.
for swLoadheader file
HScnvvss.SWL
HSTTvvss.SWL
HSBBvvss.SWL
for the VAM
table file
VScnvvss.VAM
VSTTvvss.VAM
VSBBvvss.VAM
for swImages
BTSrrrhh.SWI
BTTrrrhh.SWI
BTBrrrhh.SWI
for PID files
PSBBvvss.PID
hh, cn, vv and ss are identical with the corresponding parts of the
FILESWV - please note that thevalues of 'hh' in the FileId of
swImages do not reflect the BTSE family but reflect the HW version
of the board. (eg.BTSBIX01.SWI is for the CU and the file
BTSBIX07.SWI is for newer CU-variants, eg. the ECU).
The 3 characters used for 'rrr' identify different units:
rrr
BS240, BS241, BS240XL,
BS240SR,BS241SR, BS240XLSR,
BS40, BS40II, BS41, BS82, BS82II
BCX
for COBA
BIX
for CU
LMX
for LMU (only BS240, BS241, BS240XL)
g This value may only be used in conjunction with the FileVersion "00 " (indicating the
destination "Easy-Disk").
Validity Range
12..12 characters string
Default Value
None.
644
Id:0900d805805ca193
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Contained in the following commands:
ACTIVATE BTSM, ACTIVATE_DELAYED BTSM, FWUPGRADE BTSM
FILESWV
fileVersion
The File Version is a parameter used within the SW download procedures and not of the
type 'GET'. The corresponding attribute is swLoadCurrentVersion and is coded identical
as File Version. However the allowed values for 'hh' are different because wLoadCurrentVersion is related only to the swLoad-header file.
Validity Range
ASCII string: cn-hh-vv-ii-ss-pp_yy-mm-dd, where:
cn
Version part (network operator code)
01 = Ciphering A5.0 + A5.1 + A5.2
02 = Ciphering A5.0 + A5.2 12
03 = Ciphering A5.0 only
hh
Version part (HW/SW compatibility code)
vv
Version part (feature package code)
02 = BR 2.0
03 = BR 2.1
04 = BR 3.0
07 = BR 3.7
08,09 = BR 4.0
10 = BR 4.5
11 = BR 5.0
12 = BR 5.5
13 = BR 6.0
14 = BR 6.01
15 = BR 6.02
16 = BR 7.0 / 7.01
17 = BR 8.0
18 = BR 9.0
19 = BR 10.0
ii: Version part (sub-feature package code). This field assumes the values: 21 (BTSplus
mainline), 26 (BTSplus basic), 25 (BTSplus eMicro)
ss: Version part (actual state)
pp: Patch version (usually 00)
yy-mm-dd production date (optional)
Note:
A50016-G5100-B333-04-7619
Id:0900d805805ca193
645
BS-4x / 82 II / 240 / 241 / 240XL commands
1) For the SWL file of the downloadable test SW of BS240, BS241, BS240XL, and BS40,
BS40II, BS41, BS82II, BS82, BS240XS, BS288 the following special value is used:
cn = TT
2) For the SWL file of the downloadable boot SW of BS240, BS241, BS240XL, and
BS40, BS40II, BS41, BS82II, BS82, BS240XS, BS288 the following special value is
used:
cn = BB
In addition to the ASCII string described above values, the following values are allowed
for generic filedownload.
"00" ....Destination ID for Easy-Disk (remaining 24 characters are filled with blanks)
"01" ....Destination ID for Light-Disk Partition 1 (reserved)
"02" ....Destination ID for Light-Disk Partition 2 (reserved)
"03" ....Destination ID for Light-Disk Partition 3 (reserved)
Default Value
None.
Contained in the following commands:
ACTIVATE BTSM, ACTIVATE_DELAYED BTSM
FILETYPE
FileType
This parameter specifies the file type to be transferred.
Validity Range
ALARM_BUFFER
TRACE_FILE
Default Value
None.
Contained in the following commands:
UPLBTSLOG SOFTWARE-MANAGEMENT
FPGAFWVER
fpgaFwVer
This attribute gives information on the FPGA FW images that are contained in the
board's flash prom together with an indication of the active version. Available FPGAimage-types are identifiable via their file-ID. Up to 4 FPGA-images can be displayed on
GUI. Their order is not fixed
The attribute identifier cannot be present in the listOfRequiredAttributes together with
other attribute identifiers and it is not sent by the BTSE if a "Get FCUMAIN"/"Get CU"is
done without the information element listOfRequiredAttributes.
646
Id:0900d805805ca193
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
1 to 4 items of
FPGAfwVer
39..39 characters
string
activeFlag
active
stored
Default Value
None.
Contained in the following commands:
GET CU, GET CU FWID, GET FCUMAIN, GET FCUMAIN FWID
FRANOFFS
frameNumberOffset
This attribute allows to adjust the TDMA frame number offset for a cell. Equal frame and
burst number offsets result in synchronized TDMA frames and synchronized TDMA
frame numbers.
This attribute is only meaningful enableInterSiteSync is set to 'TRUE'.
Validity Range
0 - 255
Default Value
0
Contained in the following commands:
GET BTS
FWVER
firmwareVersion
This attribute provides the firmware version stored on the ETHCON board.
Validity Range
0 - 255
<NULL>
Default Value
None.
Contained in the following commands:
GET ETHCON
A50016-G5100-B333-04-7619
Id:0900d805805ca193
647
BS-4x / 82 II / 240 / 241 / 240XL commands
g
GN<x>
gain0(dBi*1<x>)
Attribute data provided by the TMA.
The attribute shows the gain of the operating band<X> in (dBi * 10).
Validity Range
0 - 255
<NULL>
Default Value
None.
Contained in the following commands:
GET TMA
GNA
gainAdjust(dB)
The attribute provides the attenuation value which is actually set for the RX amplifier
chain of the combiner, either the DIP switch value, the aligned database value or the
value due to the fail safe mechanism.
UNKNOWN means that no hardware is equipped.
ILLEGAL_VALUE means a wrong DIP switch setting of an (F)DUAMCO (formerly indicated as 7 dB).
Validity Range
In commands GET DILNA, GET DULNA, GET F6LNA:
N_00
N_01
N_02
N_03
N_04
N_05
N_06
N_07
N_08
N_09
N_10
N_11
648
Id:0900d8058051e6d2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
N_12
ILLEGAL_VALUE
UNKNOWN
<NULL>
In commands GET DILNA, GET DULNA:
N_00
N_01
N_02
N_03
N_04
N_05
N_06
N_07
N_08
N_09
N_10
N_11
N_12
ILLEGAL_VALUE
UNKNOWN
Default Value
None.
Contained in the following commands:
GET DILNA, GET DULNA, GET F6LNA
GNADB
gainAdjustDb
The attribute sets the attenuation value of an MFDUAMCO RX amplifier chain in the
database. The value will be aligned with the combiner if a MFDUAMCO is equipped. If
the value DIP is set, the MFDUAMCO DIP switch setting will be used.
The attribute is meaningless if an old DUAMCO or FDUAMCO is equipped. Nevertheless the value will be stored in the database and used if an MFDUAMCO will be
equipped later on.
Validity Range
N_00
N_01
N_02
A50016-G5100-B333-04-7619
Id:0900d8058051e6d2
649
BS-4x / 82 II / 240 / 241 / 240XL commands
N_03
N_04
N_05
N_06
N_07
N_08
N_09
N_10
N_11
N_12
DIP
Default Value
DIP
Contained in the following commands:
CREATE DULNA, CREATE F6LNA, GET DULNA, GET F6LNA, SET DULNA, SET
F6LNA
GNR
gainResolution(dB*4)
Attribute data provided by the TMA.
Validity Range
0 - 255
<NULL>
Default Value
None.
Contained in the following commands:
GET TMA
GSMTIME
gsmTime
This attribute represents the current frame number of the radio interface. It is counted
as a binary presentation 'frame number modulus 42432'.
Validity Range
0 - 42432
<NULL>
650
Id:0900d8058051e6d2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Default Value
None.
Contained in the following commands:
GET BTS
GTWADRV4
gatewayAddressIPv4
This attribute specifies IPv4 address of the default IP gateway including the subnetwork
information.
The address is input in the usual IPv4 format. The subnetwork is added in CIDR notation.
Example for CIDR notation:
192.168.2.7/24 corresponds to the host address 192.168.2.7 with subnet mask
255.255.255.0
g Value 0.0.0.0/0 and 0.0.0.0 are intrepreted as attribute not set.
This attribute is visible and configurable only in phase 2 in LMT local.
Validity Range
0..18 characters string
Default Value
""
Contained in the following commands:
GET BTSEP NOSWL, SET BTSEP
A50016-G5100-B333-04-7619
Id:0900d8058051e6d2
651
BS-4x / 82 II / 240 / 241 / 240XL commands
h
HOPMODE
hoppingMode
This attribute specifies whether baseband hopping or synthesizer hopping is to be done.
This attribute can be changed only when hopping is switched off (Attribute btsIsHopping). A prerequisite for synthesizer hopping is that the corresponding HW (TPU + PA)
is installed.
Validity Range
BBHOP
SYNHOP
Default Value
None.
Contained in the following commands:
GET BTS
HSN
hoppingSequenceNumber
This attribute determines the order in which the allocated frequencies are used.
This parameter is used in the frequency hopping algorithm. Any instance of the CHAN
object, which is not assigned to any explicit frequency hopping system instance should
contain the default value 0 for this attribute.
Changing this attribute is allowed only if there is no hopping (i.e. attribute btsIsHopping
= FALSE).
Validity Range
0 - 63
Default Value
0
Contained in the following commands:
GET CHAN
652
Id:0900d8058024e371
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
i
INSD
installDate
Attribute data provided by the TMA.
Validity Range
0..6 characters string
Default Value
None.
Contained in the following commands:
GET TMA
INSID
installerId
Attribute data provided by the TMA.
Validity Range
0..5 characters string
Default Value
None.
Contained in the following commands:
GET TMA
INTAVEPAR
intaveParameter
This attribute contains the measurement and averaging period for the interference classification of idle traffic channels in units of SACCH multiframes.
Validity Range
1 - 31
Default Value
31
Contained in the following commands:
GET BTS
A50016-G5100-B333-04-7619
Id:0900d80580592b9c
653
BS-4x / 82 II / 240 / 241 / 240XL commands
INTCLASS
enableInterferenceClass
This attribute indicated whether the interference classification of idle traffic channels is
enabled or disabled.
A change of the attribute becomes effective in the next SACCH multiframe.
A consequence of the value 'disabled' is that no 'RF resource indication' messages are
sent to the BSC.
(TRUE = enabled)
Validity Range
FALSE
TRUE
Default Value
TRUE (enabled)
Contained in the following commands:
GET BTS
INTINF
interfaceInformation
This attribute is used to configure one of the envaBTSE instances with the following
information:
positive logic with external detector
or
negative logic with external detector
Validity Range
low
high
Default Value
None.
Contained in the following commands:
CREATE ENVABTSE, GET ENVABTSE, SET ENVABTSE
INTLVBND
interferenceLevelBoundaries
This attribute defines the boundary limits of five interference bands for the unallocated
timeslots.
The BSC maps the averaged interference level measurements into these five bands.
A change of the attribute becomes effective in the next SACCH multiframe.
654
Id:0900d80580592b9c
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
The validity range of the attribute is 0 ... 63 (less than -110 dBm...more than -48 dBm)
in steps of 1 dBm.
Validity Range
intThrBou1
0 - 63
intThsBou2
0 - 63
intThsBou3
0 - 63
intThsBou4
0 - 63
intThsBou5
0 - 63
Default Value
intThrBou1 : 2
intThsBou2 : 6
intThsBou3 : 12
intThsBou4 : 22
intThsBou5 : 63
Contained in the following commands:
GET BTS
IPADR
ipAddress
This attribute specifies IP address of the host which shall respond to the ping request.
The address is input in the usual IPv4. Length may vary from minimum length (7 ) ->
1.3.6.9 up to maximum length (15) -> 192.120. 110.124
Validity Range
7..15 characters string
Default Value
None.
Contained in the following commands:
PING BTSEP
A50016-G5100-B333-04-7619
Id:0900d80580592b9c
655
BS-4x / 82 II / 240 / 241 / 240XL commands
l
L1CTRLTS
layer1ControlTs
This attribute defines in case of a LOOP configuration which dedicated layer 1 16kbit/s
subchannel is to be used for the layer 1 supervision. In a star or multidrop configuration
the given time slot is used for a loopback supervision.
Below are indicated some more detailed information about the attribute validity range:
- TimeSlotNumber for Time Slot in 2 Mb/s link:
validity range: 1..31 (if dedicated 16k subchannel is used fo supervision
- TimeSlotNumber for Time Slot in 1,5 Mb/s link:
validity range: 1..21 (if dedicated 16k subchannel is used fo supervision
- SubSlotNumber for SubSlot within time slot
validity range: 0..3 (if dedicated 16k subchannel is used fo supervision
Validity Range
TSL
0 - 31
SSL
0-3
Default Value
TimeSlotNumber:
0 (deactivated)
SubSlotNumber:
octet #2 = 3
octet #4 = 0
Contained in the following commands:
CREATE BPORT, GET BPORT, SET BPORT
L1PT
layer1ProtocolType
"This attribute defines the type of protocol that is used on layer 1 of the Abis-line. One
of the following values has to be set by the operator at installation time for a PCM30 line:
The value 'pcm30crc4' means that a cyclic redundancy check (CRC4) is performed, the
value 'pcm30noncrc4doubleframe' means that CRC4 is not performed and that the line
remains in Doubleframe mode.
656
Id:0900d80580592b9e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
The value 'pcm24sf' means the 'superframe' format is used.
The value 'pcm24crc6esf' means the 'extended superframe' format is used and a cyclic
redundancy check (CRC6) is performed.
Validity Range
pcm30crc4
pcm30noncrc4doubleframe
pcm24sf
pcm24crc6esf
Default Value
None.
Contained in the following commands:
CREATE BPORT, GET BPORT
L1RAT
layer1RemoteAlarmType
This attribute defines how the signalling of a remote alarm is done for both detection and
transmission. It must be set accordingly in the remote environment. 'Special Bit Robbing'
is allowed only for PCM24 and means that a special bit (bit 2) is used for signalling a
remote alarm.
Validity Range
ProtocolSignalling
SpecialBitRobbing
Default Value
ProtocolSignalling
Contained in the following commands:
CREATE BPORT, GET BPORT, SET BPORT
LAPDCH
lapdChannel
This attribute exists for only for LAPDLE. It identifies the BPortNumber, Timeslot
Number and Subslot Number allocated on the Abis-interface for the LAPD signalling
links to the BSC.
- BPortNumber (BPORT)
00-07 for BTSplus Mainline (enums: BPORT0, BPORT1, ..., BPORT7)
00
for eMICRO (enum: BPORT0)
00-03 for BTSXS (enum: BPORT0, ..., BPORT3)
A50016-G5100-B333-04-7619
Id:0900d80580592b9e
657
BS-4x / 82 II / 240 / 241 / 240XL commands
( ! ) For BS82II only BPortNumber 00-03 is allowed
- the TSL field has the following ranges:
- 1... 31 for PCM30
- 0... 24 for PCM24
- the SSL field has the following bit associations:
- a (bits 8.7)
SSL0_16KB
- b (bits 6,5)
SSL1_16KB
- c (bits 4,3)
SSL2_16KB
- d (bits 2,1)
SSL3_16KB
- 64 kb/s signalling
FULL_64KB
Validity Range
BPORT
BPORT0
BPORT1
...
BPORT7
TSL
1 - 31
SSL
SSL0_16KB
SSL1_16KB
SSL2_16KB
SSL3_16KB
FULL_64KB
Default Value
None.
Contained in the following commands:
CREATE LAPDLE, GET LAPDLE
LAPDOVLT
lapdOverloadTimer(sec)
The attribute defines the time between two subsequent 'LAPD overload' messages (in
seconds), as long as any radio signalling LAPD link on Abis is overloaded.
The validity range is indicated in seconds.
Validity Range
658
lapdOverloadTimer
1 - 60
lapdUsageOverloadTimer
0.5 - 10.0
Id:0900d80580592b9e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Default Value
lapdOverloadTimer: 1 second
lapdUsageOverloadTimer: 1 second
Contained in the following commands:
GET BTSM OVERLOAD
LAPDOVLTH
lapdOverloadThresholds(%)
The thresholds give the percentage of the LAPD transmit queue
filling, allowed range is 10 to 100 (decimal):
a)
first level upper threshold : when exceeded sending of measurement report messages on Abis will be suspended.
b)
second level upper threshold : when exceeded on any of the
LAPD links the periodical sending 'LAPD overload' message is
started.
c)
first level lower threshold: when filling level falls below, sending
of measurement reports on Abis will resume.
d)
second level lower threshold : when filling level falls below,
sending of 'LAPD overload' indication will be stopped.
For thresholds the following restriction is valid:
-
first level lower threshold < first level upper threshold =<
second level lower threshold < second level upper threshold
Default Value:
80
first level upper threshold
60
first level lower threshold
90
second level upper threshold
80
second level lower threshold
10
firstLevReductionStep
Validity Range
firstLevUpperThreshold
10 - 100
firstLevLowerThreshold
10 - 100
firstLevReductionStep
10 - 100
secLevUpperThreshold
10 - 100
secLevLowerThreshold
10 - 100
A50016-G5100-B333-04-7619
Id:0900d80580592b9e
659
BS-4x / 82 II / 240 / 241 / 240XL commands
Default Value
None.
Contained in the following commands:
GET BTSM OVERLOAD
LAPDOVLTRXL
lapdOverloadTRXList
This attribute indicates a list of congested TRX instances, up to 48. Congestion in this
context means that a certain threshold in the LAPD transmit queue has been exceeded,
(second level upper threshold as defined in attribute lapdOverloadThresholds).
Some details about the validity range values are indicated:
0=<N=<48, 2=<n=<194
Validity Range
1 to 24 items of
Pathname
Default Value
None.
Contained in the following commands:
GET BTSM OVERLOAD
LCONF
lineConfiguration
This attribute defines the configuration of the BTSEs on the Abis
interface.
Notes:
660
a)
'star' means either a BTSE which is directly connected to the
BSC or the last BTSE of a multidrop chain.
b)
In general 'star' is allowed only for even BPORT instances.
Only for hh-ii = 04-01 'star' may be used also for odd BPORT
instances (2k+1, k=0, 1, 2, 3) - in this case the related even
BPORT instance (2k, k=0, 1, 2, 3) must be configured as 'star'
too.
c)
more information can be found in the document 'Configuration
Rules for BTSE Abis Line Interface'.
Id:0900d80580592b9e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
star
multidrop
loop
starX
Default Value
None.
Contained in the following commands:
CREATE BPORT, GET BPORT, SET BPORT
LIMP
lineImpedance
This attribute defines the impedance setting of the related Abis
(BPort) interface.
Notes:
a)
On a COBA2P8 the adjustment of the impedance is done by
DIP switches. So the only acceptedvalue on a COBA2P8 is
'AccDIP'.
b)
On a COBA4P12 the adjustment is performed by software. So
the value must be 'Imp100or120Ohm' or 'Imp75Ohm'.
c)
If a value which is not allowed is entered the BTSE SW will
answer with a NACK.
d)
The initial value 02 will be changed by BTSE subsystem A1 to
00 in case of COBA4P12."
e)
In case of backup from COBA2P8 to COBA4P12 it is handled
"fault tolerantly", SET message will be acknowledged and
alarm will be issued. A1 subsystem will change value of the
attribute to appropriate default value 00 automatically.
Validity Range
Imp100or120Ohm
Imp75Ohm
accDIP
Default Value
accDIP (fully correct for COBA2P8 internal used by subsystem DM)
Contained in the following commands:
CREATE BPORT, GET BPORT, SET BPORT
A50016-G5100-B333-04-7619
Id:0900d80580592b9e
661
BS-4x / 82 II / 240 / 241 / 240XL commands
LMTLSESS
lmtLogonSession
This attribute indicates if a LMT session is active or not.
Validity Range
NOT_ACTIVE
ACTIVE
Default Value
NOT_ACTIVE
Contained in the following commands:
GET BTSEP NOSWL
LMTLTIME
lmtLogonTime
This attribute specifies the date and time of the logon attempt. It is set by the BTSE when
the T- interface message 'Logon' from the local LMT is received.
Validity Range
year
1990 - 2037
month
1 - 12
day
1 - 31
hour
0 - 23
minute
0 - 59
second
0 - 59
offsetHour
-12 - 14
offsetMinute
0 - 45
Default Value
year
: 1995
month
:8
day
:1
hour
:0
minute
:0
second
:0
Contained in the following commands:
GET BTSEP NOSWL
LMTUAL
lmtUserAccessLevel
662
Id:0900d80580592b9e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
This attribute indicates the LMT user profile.
Validity Range
READ_ONLY
COMMAND
READ_WRITE
ACCESS_CONTROL_MA
NAGEMENT
SECURITY_OPERATOR
NOT_DEFINED
Default Value
NOT_DEFINED
Contained in the following commands:
GET BTSEP NOSWL
LMTUNAME
lmtUserName
The user name consists of a character string containing maximal 7
characters for the user name. The user name must be terminated by
a NUL character value (last byte of the user name). The content of
this attribute is identical with the content of the information element
'user identification' of the T-interface message 'Logon'.
Default Value: octet 3-10 = 00, octet 2 = 07
Validity Range
1..14 characters string
Default Value
octet 3-10 = 0, octet 2 = 7
Contained in the following commands:
GET BTSEP NOSWL
LNAMDB
lnaModeDb
The attribute sets the LNA mode value of an MFDUAMCO RX path in the database. The
value will be aligned with the combiner if a MFDUAMCO is equipped. If the value DIP is
set, the MFDUAMCO DIP switch setting will be used.
The attribute is meaningless if an old DUAMCO or FDUAMCO is equipped. Nevertheless the value will be stored in the database and used if an MFDUAMCO will be
equipped later on.
A50016-G5100-B333-04-7619
Id:0900d80580592b9e
663
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
MUCO_MODE
AMCO_MODE
DIP
Default Value
DIP
Contained in the following commands:
CREATE DULNA, CREATE F6LNA, GET DULNA, GET F6LNA, SET DULNA, SET
F6LNA
LNAMODE
lnaMode
This attribute indicates the current amplification mode of a DUAMCO_LNA or
DIAMCO_LNA. (The information is derived from the setting of the DIP switch 'mode
switch' and from the actual situation e.g. regarding the TMA) This attribute is 'readonly'.
Validity Range
MUCO_MODE
AMCO_MODE
UNKNOWN
Default Value
UNKNOWN
Contained in the following commands:
GET DILNA, GET DULNA, GET F6LNA
LNAPRED
lnaPredecessor
This attribute is optional and indicates the wiring of the RX input of a DUAMCO_LNA/
DIAMCO_LNA to the RX cascade output (RXCA) of another
DUAMCO_LNA/DIAMCO_LNA or to the RX output of a TMA.
From SW point of view the FDUAMCO is considered just as an HW variant of the
DUAMCO, so an extra term like 'FDUAMCO_LNA' is not introduced.
If there is no wiring the operator must not provide a value for the attribute.
If there is no wiring and the operator enters a value for the attribute he can correct the
error only by a deletion of the object and a re-creation of the object.
Detailed information about the validity range:
predecessor (Type):
DULNA (not allowed for BS82II)
664
Id:0900d80580592b9e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DILNA (not allowed for BS82II)
F6LNA: [0-3]
TMA
predecessor (Rack):
RACK0
RACK1
RACK2
If predecessor(type) is TMA the predecessor(rack) must be the same as the rack of the
DILNA/DULNA, i.e. the TMA connected to a DILNA/DULNA must be created in the same
rack as the DILNA/DULNA object.
predecessor (relative number):
DULNA 0 ... 7
DILNA 0 ... 7 (for BS240XL only 4 ... 7)
TMA 0 ... 15 (for BS240XL only 12 ... 15)
Validity Range
In commands CREATE DILNA, CREATE DULNA, CREATE F6LNA:
predType
DILNA
predRack
RACK0
RACK1
RACK2
predNo
DILNA0
DILNA1
...
DILNA7
DULNA
predRack
RACK0
RACK1
RACK2
predNo
DULNA0
DULNA1
...
DULNA7
TMA
predRack
RACK0
RACK1
RACK2
predNo
TMA0
TMA1
...
TMA15
A50016-G5100-B333-04-7619
Id:0900d80580592b9e
665
BS-4x / 82 II / 240 / 241 / 240XL commands
F6LNA
predRack
RACK0
RACK1
RACK2
predNo
F6LNA0
F6LNA1
...
F6LNA3
In commands GET DILNA, GET DULNA, GET F6LNA:
predType
DILNA
predRack
RACK0
RACK1
RACK2
predNo
DILNA0
DILNA1
...
DILNA7
DULNA
predRack
RACK0
RACK1
RACK2
predNo
DULNA0
DULNA1
...
DULNA7
TMA
predRack
RACK0
RACK1
RACK2
predNo
TMA0
TMA1
...
TMA15
F6LNA
predRack
RACK0
RACK1
RACK2
predNo
F6LNA0
F6LNA1
...
F6LNA3
666
Id:0900d80580592b9e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
<NULL>
Default Value
None.
Contained in the following commands:
CREATE DILNA, CREATE DULNA, CREATE F6LNA, GET DILNA, GET DULNA,
GET F6LNA
LOCALADDR
localAddress
Local IP address of the Circuit Emulation Service Tunnel. The address is input in the
usual IPv4 format. For addressing examples please see also attribute ipAddress. The
object must be locked before modifying the address via the SET command.
Validity Range
7..15 characters string
Default Value
None.
Contained in the following commands:
CREATE CESTUNNEL, GET CESTUNNEL, SET CESTUNNEL
LOCLUDP
localUdpPort
Local UDP port number of the CESPW instance. It is recommended to use identical port
numbers for the local and the peer UDP port. The object must be locked before modifying the port number via the SET command.
Validity Range
49152 - 65535
Default Value
None.
Contained in the following commands:
CREATE CESPW, GET CESPW, SET CESPW
LOCNAME
locationName
This attribute is a ASCII string (max 37 characters) which identifies a
location.
Default Value: EARTH
A50016-G5100-B333-04-7619
Id:0900d80580592b9e
667
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
1..37 characters string
Default Value
None.
Contained in the following commands:
GET BTSEP NOSWL, SET BTSEP
LOSPKTTH
lostPacketThreshold
This attribute determines minimum number of lost packets per polling period within
CESPW which shall trigger the packet loss state.
Validity Range
1 - 100
Default Value
1
Contained in the following commands:
CREATE CESTUNNEL, GET CESTUNNEL, SET CESTUNNEL
LPDLMSAT
lapdleLinkSatellited
The attribute informs the BTSE SW about the settings in the BSC regarding the
presence of a satellite on the Abis interface. The attribute is sent only during the 'BTSE
Alignment Procedure'. The BTSE SW stores the value only as information for the operator. However when the attribute is stored the BTSE SW performs a semantic check
which compares the value of lapdmLinkSatellited with the value of the attribute sAbisLinkSatellited (ABISLKSAT). The BTSE SW reports a minor alarm if both values do not
match. The BTSE object is set to enabled.degraded as long as the alarm is active. In
order to clear the alarm the operator has to take steps that LPDLMSAT and ABISLKSAT
have a consistent value - a consequence of this action is an interruption of the Abis link
(as a change of ABISLKSAT is only possible at the BTSE-LMT in phase 2 and a change
of LPDLMSAT requires a deletion and re-creation of the BTSM object at the BSC-LMT
or at the RC).
Validity Range
terrestrialConnection
satelliteConnection
Default Value
terrestrialConnection (corresponds in the BSC to 'LPDLMSAT=FALSE')
668
Id:0900d80580592b9e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Contained in the following commands:
GET BTSM NOSWL
LRU
lru
This attribute describes an object class and instance of a specific board that is affected
by the firmware upgrade.
Validity Range
siemensHw
HwP
HwXS
typeOfHw
Cu
Coba
Fcumain
Duamco
Ficom6
rackNbr
0-2
boardNbr
0 - 11
Default Value
None.
Contained in the following commands:
FWUPGRADE BTSM
LSIND
lineStatusIndication
This attribute identifies the PCM link status values, that additionally
will be displayed via LED(s) at the LI or COBA/COSA. More than one
status might be valid at a time.
Bit 0: RemoteAlarmIndication
01
TRUE
00
FALSE always FALSE in case of ISDN S0
Bit 1: FrameSynchronizationLoss
01
TRUE
00
FALSE
Bit 2: CRCFailure
01
TRUE
00
FALSE always FALSE in case of ISDN S0
A50016-G5100-B333-04-7619
Id:0900d80580592b9e
669
BS-4x / 82 II / 240 / 241 / 240XL commands
Bit 3: NoLevel (Line is broken)
01
TRUE
00
FALSE
Bit 4: CRCFailureRemoteEnvironment
01
TRUE
00
FALSE always FALSE in case of ISDN S0
Bit 5: BitErrorRate > lowerThreshold of 'bitErrorRateThresholds'
01
TRUE
00
FALSE always FALSE in case of ISDN S0
Bit 6: BitErrorRate > upperThreshold of 'bitErrorRateThresholds'
01
TRUE
00
FALSE always FALSE in case of ISDN S0
Bit 7: PromptMaintenanceAlarmIndication
01
TRUE
00
FALSE
Validity Range
RemoteAlarmInd
FALSE
TRUE
FrameSynchroniza- FALSE
tionLoss
TRUE
CRCFailure
FALSE
TRUE
NoLevel
FALSE
TRUE
CRCRemoteEnviro- FALSE
ment
TRUE
BERTLowerThresh- FALSE
old
TRUE
BERTUpperThresh- FALSE
old
TRUE
PromptMaintenanceAlarmInd
FALSE
TRUE
670
Id:0900d80580592b9e
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
<NULL>
Default Value
None.
Contained in the following commands:
GET BPORT
A50016-G5100-B333-04-7619
Id:0900d80580592b9e
671
BS-4x / 82 II / 240 / 241 / 240XL commands
m
MACADDR
macAddress
This attribute provides the MAC address of the Ethernet port instance. Attribute is coded
as a string with 17 characters with hexadecimal representation of the MAC address (e.g.
09:03:20:ae:ec:7b).
Validity Range
17..17 characters string
Default Value
None.
Contained in the following commands:
GET COBAETHINTF
MAIO
maio
"Hopping physical channels on the same timeslot with the same mobile allocation (contained in the aRFCNList) must use the same value of hoppingSequenceNumber and different values for MAIO (Mobile Allocation Index Offset). This prevents frequency
collision.
The maximum value of mAIO depends on the number of frequencies in the attached
ARFCNList. For a set of N allocated frequencies in the ARFCNList there must be N different values for mAIO (0...N-1).
Any instance of the object CHAN which is not assigned to any explicit frequency hopping
system instance should contain the default value 0 for this attribute."
Changing this attribute is allowed only if there is no hopping (i.e. attribute btsIsHopping
= FALSE).
Validity Range
0 - 63
Default Value
0
Contained in the following commands:
GET CHAN
MAXGN
maxGain(dB*4)
Attribute data provided by the TMA.
672
Id:0900d8058051e910
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
0 - 255
<NULL>
Default Value
None.
Contained in the following commands:
GET TMA
MAXPDV
maxPdv(ms)
The attribute defines the maximum packet delay variation value. It is used for dimensioning of the jitter buffer. The object must be locked before modifying the maxPdv value via
SET command.
Validity Range
0.125 - 30.000
Default Value
2.000
Contained in the following commands:
CREATE CESPW, GET CESPW, SET CESPW
MINGN
minGain(dB*4)
Attribute data provided by the TMA.
Validity Range
0 - 255
<NULL>
Default Value
None.
Contained in the following commands:
GET TMA
MOBALLOC
arfcnList
mobileAllocation / trxFrequency
A50016-G5100-B333-04-7619
Id:0900d8058051e910
673
BS-4x / 82 II / 240 / 241 / 240XL commands
This attribute is contained in the functional objects transceiver and
channel.
Octet 2 tells the number of frequencies in the list. The remaining
number of octets of this information element (aRFCNList) is twice the
value of this field.
If the attribute is contained in a message related to the transceiver the
value of "Number of ARFCNs in List" must be 1, i.e. only one ARFCN
is allowed. (The name at the GUI is 'trxFrequency" in this case.
If the attribute is contained in a message related to the channel (The
name at the GUI is 'mobileAllocation" in this case.) the value of
"Number of ARFCNs in List" is : <00-40>, <0- 64> (decimal)
The value 0 has the special meaning that the corresponding channel
instance is not assigned to any frequency hopping system instance
and that the BTSE has to use the ARFCN value of the TRX which
contains the channel.
ARFCN1..ARFCNn shall be contained in ascending order with no
duplicates.
cellAllocationNumber
Hex
Decimal
GSM900 "BB900"
0001 ... 007C
1 ... 124
GSM EXTENDED
"F2ONLY900"
0000 ... 007C
0 ... 124
03CF ... 03FF
975 ... 1023
GSM EXTENDED
REDUCED
"EXT900"
0000
0000 ... 007C
0 ... 124
03CF ... 03FF
975 ... 1023
DCS 1800
"DCS1800"
0200 ... 0375
512 ... 885
PCS 1900
0200 ... 032A
512 ... 810
GSM-R
03BB ... 03CE
955 ... 974
GSM-DCS
0000 ... 007C
0 ... 124
03CF ... 03FF
975 ... 1023
0200 ... 0375
512 ... 885
GSM850
0080 ... 00FB
128 ... 251
GSM850-PCS
0080 ... 00FB
128 ... 251
0200 ... 032A
512 ... 810
0080 ... 00FB
128 ... 251
0200 ... 0375
512 ... 885
GSM850-DCS
674
Id:0900d8058051e910
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Changing or setting this attribute for a TRX means a temporary loss
of service for the TRX.
Changing this attribute for a CHAN is allowed only if there is no frequency hopping (i.e. attribute btsIsHopping = FALSE).
Validity Range
0 to 64 items of
0 - 1023
Default Value
octet #2 = 0 (only for aRFCNList related to "CHAN")
Contained in the following commands:
GET CHAN
MOEC
memberOfEmergencyConfig
The attribute memberOfEmergencyConfiguration specifies whether a TRX should still
operate for a given time (emergencyTimer1) if a "battery backup operation" (due to
"mains breakdown") occurs. If an emergency because of overtemperature occurs, this
attribute specifies a TRX which is not powered off immediately.
If this feature is wanted the value TRUE should be used at least for the BCCH TRX. If
FALSE is used for the BCCH TRX and TRUE is used for another TRX in the cell a BCCH
reconfiguration would be triggered if a "battery backup operation" (due to "mains breakdown") or overtemperature occurs.
Note:
The switch to emergency configuration or zero configuration in case of overtemperature
only depends on the temperature itself (two different values for emergency and zero
configuration) and doesn't depend on the emergencyTimer1/2.
Validity Range
TRUE
FALSE
Default Value
TRUE
Contained in the following commands:
GET TRX
MONPRT
monitoringPort
This attribute defines the port which is used for Abis traffic monitoring on the ETHCON
module.
A50016-G5100-B333-04-7619
Id:0900d8058051e910
675
BS-4x / 82 II / 240 / 241 / 240XL commands
The attribute enables mirroring of packets for the configured monitoringPort. The port
number corresponds to the ETHPORT instance number. Port mirroring can be enabled
for maximum one port.
The system does not check if the referenced port is already created.
Validity Range
none
port0
port1
port2
port3
coba
Default Value
none
Contained in the following commands:
GET ETHCON, SET ETHCON
MORT
MOT
This Attribute describes an object instance. The MOT attribute defines the HW-MO that
will have its internal resources tested.
Below are reported some detailed information about the validity range.
For:
BS240,
676
BS40, BS41 BS40II
BS82II
BS240SR,
BS241,
BS241SR,
BS240XL
BS240XLS
R
ACDCP
ACT
BATTERY
BCOM
COBA #)
COSA
CU
DIDCTMA
DILNA
Id:0900d8058051e910
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DUDCTMA
DULNA
DUVSWR
F6DCTMA
F6LNA
F6TNFP
F6VSWRP
FANP *)
FCUMAIN
FCUTR
FTNFP
LMU
TMA *)
*) no processor #) COBA #0 only possible via local LMT on
phase 2
Validity Range
Pathname
Default Value
None.
Contained in the following commands:
GET BTSETEST, PERFTEST BTSEP, STOPTEST BTSEP
MPHERR
maxPhaseError(microsec)
This attribute specifies the desired maximum phase deviation of the base clock on the
COBA in respect to the GPS clock. If the current phase deviation exceeds this desired
maximum value an alarm is issued and the attribute clockAccuracy is set to the reduced
accuracy level 'high'. This attribute is only meaningful if the attribute syncSource is set
to 'extGPS' and the attribute enableInterSiteSync is set to 'TRUE'.
Validity Range
1.5 - 15.0
Default Value
1.5
A50016-G5100-B333-04-7619
Id:0900d8058051e910
677
BS-4x / 82 II / 240 / 241 / 240XL commands
Contained in the following commands:
GET SYNCBTSE, SET SYNCBTSE
MPTSLXX
mappingTSLXX
This attribute describes to which "time slot" of the specified Bport the TS xx of the Bport
related to the given XConnect instance is to be mapped; e. g. 'mappingTSL02' of
XConnect 0 describes the mapping of time slot 2 of BPort 0 (which corresponds to
XConnect 0) to a time slot (targetTSL) of a BPort instance (targetBPort). If the 'target
BPort' value is equal to the value of the XConnect instance this means that a "remapping" between the time slot position on the Abis line and the BTSE internal position is
done- this is allowed only in LMT phase 2. The purpose for this "remapping" usually is
to have the traffic data and signalling data in the BTSE at the same positions as at the
PCM lines directly connected to the BSC (and as indicated in the attributes abisChannel
and lapdChannel)- this is needed e.g. if there is a sequence of several PCM lines
between BSC and BTSE involving multidrop/loop and cross connect configurations.
In case of PCM24 only mappingTSL01..mappingTSL24 are meaningful.
XConnect instance 0 is related to BPORT instance 0
XConnect instance 1 is related to BPORT instance 1
XConnect instance 2 is related to BPORT instance 2
XConnect instance 3 is related to BPORT instance 3
XConnect instance 4 is related to BPORT instance 4
XConnect instance 5 is related to BPORT instance 5
XConnect instance 6 is related to BPORT instance 6
XConnect instance 7 is related to BPORT instance 7
note on targetTSL validity range:
- targetTSL : 0 ... 24 for time slot in 1,5 Mb/s link
- targetTSL : 0 ... 31 for time slot in 2 Mb/s link
targetBport = 0 and targetTSL = 0 mean 'no mapping'
Validity Range
targetBport
0-7
targetTSL
0 - 31
Default Value
targetBport
targetTSL
Contained in the following commands:
CREATE XCONNECT, GET XCONNECT, SET XCONNECT
678
Id:0900d8058051e910
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
MRSYNCT
maxResyncTime(min)
This attribute allows the operator to adjust the maximum re-synchronization time to
reach the desired phase accuracy defined with the attribute maxPhaseError. If the estimated re-synchronization time exceeds this value an alarm is issued, which informs the
operator that a manual re-synchronization should be considered. The time can be
adjusted between 0 and 24 hours (i.e. 0-1440 minutes). This attribute is only meaningful
if the attribute syncSource is set to 'extGPS' and the attribute enableInterSiteSync is set
to 'TRUE'.
Validity Range
0 - 1440
Default Value
180
Contained in the following commands:
GET SYNCBTSE, SET SYNCBTSE
MSTXPMAX
mSTxPwrMax(*dBm mapped)
This attribute indicates the maximum power level an MS may use in the serving cell. In
case of GSMDCS, GSM850-PCS and GSM850-DCS mixed cells the attribute represents the maximum power level a MS may use in the band to which the BCCH belongs.
Below are listed some detailed validity range values
GSM / GSM-R:
39 dBm
37 dBm
:
33 dBm, Default Value
:
15 dBm
13 dBm
DCS 1800:
30 dBm, Default Value
28 dBm
:
02 dBm
00 dBm
PCS 1900:
A50016-G5100-B333-04-7619
Id:0900d8058051e910
679
BS-4x / 82 II / 240 / 241 / 240XL commands
30 dBm, Default Value
28 dBm
:
02 dBm
00 dBm
33 dBm
32 dBm
Validity Range
0 - 31
Default Value
None.
Contained in the following commands:
GET BTS
MSTXPMAXC
mSTxPwrMaxCompl
This attribute is meaningful only in case of GSM-DCS, GSM850-PCS and GSM850DCS mixed cells and represents the maximum power level a MS can use in the band of
the serving cell to which the BCCH doesn't belong. A change of the attribute becomes
effective with the next call.
BCCH is in the DCS or PCS band - the MS can use the specified value
for the maximum power in the GSM band (i.e. in the band complementary
to the BCCH band)
39 dBm
37 dBm
:
33 dBm, Default Value
:
15 dBm
13 dBm
BCCH is in the GSM band - the MS can use the specified value for the
maximum power in the DCS band (i.e. in the band complementary to
the BCCH band)
30 dBm, Default Value
28 dBm
:
02 dBm
680
Id:0900d8058051e910
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
00 dBm
BCCH is in the GSM band - the MS can use the specified value for the
maximum power in the PCS band (i.e. in the band complementary to
the BCCH band)
30 dBm, Default Value
28 dBm
:
02 dBm
00 dBm
33 dBm
32 dBm
Validity Range
0 - 31
Default Value
None.
Contained in the following commands:
GET BTS
MTLT
mechanicalTilt(degree*10)
Attribute data provided by the TMA.
Validity Range
0 - 65535
<NULL>
Default Value
None.
Contained in the following commands:
GET TMA
MTYP
mediaType
This attribute indicates the type of the physical medium used for the given instance of
Ethernet port.
Validity Range
electrical
A50016-G5100-B333-04-7619
Id:0900d8058051e910
681
BS-4x / 82 II / 240 / 241 / 240XL commands
optical
<NULL>
Default Value
None.
Contained in the following commands:
GET ETHPORT
682
Id:0900d8058051e910
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
n
NEPTTREP
notDataRepCount
This attribute determines the number of repetitions for the not_data message per cell.
Up to 3 repetitions can be configured. The repetition rate is constant 200 ms.
Validity Range
0-3
Default Value
None.
Contained in the following commands:
GET BTS
NTWTYPC
networkTypeCompensation
The attribute allows to choose between different PDV compensation parameter sets
which are optimized to certain network behaviors.
Validity Range
0 - 255
Default Value
0
Contained in the following commands:
CREATE CESTUNNEL, GET CESTUNNEL, SET CESTUNNEL
NTWTYPE
networkType
This attribute defines the type of network (in terms of frequency band(s)) the BTS is
working in. Further more it indicates the type of a possible complementary frequency
band when handling Dual Band Mobiles.
Below are listed some details about the attribute validity range:
GSMDCS:
GSM 900
DCS 900
GSM EXTENDED
A50016-G5100-B333-04-7619
Id:0900d8058024e3aa
683
BS-4x / 82 II / 240 / 241 / 240XL commands
GMS EXTENDED REDUCED
GMS-DCS
GSMPCS:
GSM 900
GSM EXTENDED
GMS EXTENDED REDUCED
PCS 1900
GSMR:
GSM-R
.
.
GSM850PCS:
PCS 1900
GSM850
GSM850PCS
GSM850DCS:
DCS 1800
GSM850
GSM850DCS
GSMRAIL PUB:
GSM 900
DCS 1800
GSM EXTENDED
GMS EXTENDED REDUCED
GSM-R
GSM-DCS
Validity Range
GSMDCS
GSMPCS
GSMR
GSM850PCS
GSM850DCS
684
Id:0900d8058024e3aa
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Default Value
None.
Contained in the following commands:
GET BTS
NY1
ny1
This attribute indicates the maximum number of repetitions of the PHYSICAL INFORMATION message on the radio interface. This message is sent by the BTS to the MS
during a handover procedure between two not synchronised cells, in order to establish
a physical channel connection on the new cell. If the maximum number of repetitions is
reached, the newly allocated channels are released and the context related to the
handover is abandoned. ny1 is a binary presentation of maximum number of repetitions
of PHYSICAL INFORMATION.
Note: (ny1) * (BTS Air Timer t3105) must be greater than the maximum Um Layer 2
response time.
Validity Range
1 - 254
Default Value
30
Contained in the following commands:
GET BTS
NY2
ny2
As a result of an Uplink Access of a mobile station the network grants the uplink to the
mobile station by sending a VGCS UPLINK GRANT message periodically. ny2 is the
counter value which defines the number of repetitions of sending the message.
Validity Range
1 - 254
Default Value
20
Contained in the following commands:
GET BTS
A50016-G5100-B333-04-7619
Id:0900d8058024e3aa
685
BS-4x / 82 II / 240 / 241 / 240XL commands
o
OMLAPDRT
omLapdRelTimer(sec)
At the detection time of the Abis link failure (which may happen at different times in
BTSE and BSC) the BTSE starts the timer omLAPDRelTimer and the BSC starts the
timer shortLAPDIntTimer. If the timer omLAPDRelTimer expires, the BTSE blocks the
call processing. After that the BTSE forces the BSC (via a RestartSendingEventReports-NACK message) to perform a complete Abis alignment. If none of the two
timers expires, the BSC performs a 'Short Abis alignment'. The default value of omLAPDRelTimer should be kept greater than the default value of the attribute shortLAPDIntTimer.
The validity range step size is 1 second.
Validity Range
3 - 300
Default Value
30 seconds
Contained in the following commands:
GET BTSM NOSWL
OST
operationalState
This attribute defines whether or not the resource is physically installed and working.
Validity Range
DISABLED
ENABLED
Default Value
DISABLED for Functional Objects
Contained in the following commands:
GET ACDCP, GET ACT, GET BATTERY, GET BCOM, GET BPORT, GET BTS,
GET BTSEP NOSWL, GET BTSM NOSWL, GET CESPW, GET CESTUNNEL, GET
CHAN, GET COBA, GET COBAETHINTF, GET COSA, GET CU, GET DIDCTMA,
GET DILNA, GET DUAMCO, GET DUDCTMA, GET DULNA, GET DUVSWR, GET
ENVABTSE, GET ETHCON, GET ETHPORT, GET F6DCTMA, GET F6LNA, GET
F6TNFP, GET F6VSWRP, GET FANP, GET FCUMAIN, GET FCUTR, GET FTNFP,
GET FVSWRP, GET LAPDLE, GET RACK, GET SYNCBTSE, GET TMA, GET TRX,
GET XCONNECT
686
Id:0900d8058024e3bf
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
OUTPUTPR
outputPowerReduction
The attribute specifies if and how the maximum output power of the carrier unit / FlexCU
carrier has to be reduced because of the setting of the BTS attribute 'carrierUnitConfiguration.
Attribute valid only for CU and FlexCU.
Validity Range
db0
db1
...
db4
Default Value
None.
Contained in the following commands:
GET CU, GET FCUTR
OVERWRITE
Overwrite
This attribute specifies whether the existing BTS-SW on the BSC
hard disk will be overwritten (YES) or not (NO) (UPLBTSLOG).
This attribute specifies whether the existing file containing the Alarm
Buffer SW will be overwritten (YES) or not (NO) (UPLBTSLOG).
This attribute specifies whether the existing IDT file will be overwritten
(YES) or not (NO) (UPLLIDF).
Validity Range
NO
YES
Default Value
None.
Contained in the following commands:
DNLALLEXE SOFTWARE-MANAGEMENT, UPLBTSLOG SOFTWARE-MANAGEMENT, UPLLIDF REMINV
OVPTINS
ovptInstalled
A50016-G5100-B333-04-7619
Id:0900d8058024e3bf
687
BS-4x / 82 II / 240 / 241 / 240XL commands
This attribute indicates whether an OVPT board is installed or not. It can be set only in
LMT phase 2. The attribute is used to adapt the pulse mask according to the recommendations.
Validity Range
TRUE
FALSE
Default Value
TRUE
Contained in the following commands:
GET BTSEP NOSWL, SET BTSEP
688
Id:0900d8058024e3bf
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
p
PCCCHLDI
periodCcchLoadIndication(sec)
This attribute indicates the frequency with which the CCCH load indication is sent to the
BSC. This attribute is also used to enable the Paging Overload Handling.
The value 0 has two meanings:
- the CCCH Load Indication message is sent only once, every time an overload occurs,
with no repetition (frequency = 0)
- the feature Paging Overload Handling is not enabled
Validity Range
0 - 255
Default Value
255 seconds
Contained in the following commands:
GET BTS
PEERADDR
peerAddress
Peer IP address of the Circuit Emulation Service Tunnel.The address is input in the
usual IPv4 format. The object must be locked before modifying the address via the SET
command.
Validity Range
7..15 characters string
Default Value
None.
Contained in the following commands:
CREATE CESTUNNEL, GET CESTUNNEL, SET CESTUNNEL
PEERUDPPORT
peerUdpPort
Peer UDP port number of the CESPW instance. It is recommended to use identical port
numbers for the local and the peer UDP port. The object must be locked before modifying the port number via the SET command.
A50016-G5100-B333-04-7619
Id:0900d8058024fcdc
689
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
49152 - 65535
Default Value
None.
Contained in the following commands:
CREATE CESPW, GET CESPW, SET CESPW
PKTLAT
packetizationLatency
The attribute defines the number of frames which are contained in the payload of each
UDP packet.
The latency is expressed in micro seconds. Every 125 sec correspond to 1 TDM
frame in the payload. A lower value means a lower delay but a bigger protocol overhead.
The object must be locked before modifying the latency value via SET command.
Validity Range
m125
m500
m1000
m2000
m3000
m4000
m5000
Default Value
m1000
Contained in the following commands:
CREATE CESPW, GET CESPW, SET CESPW
PNGF
pingFrequency
The attribute is only meaningful if the ping delay measurement is activated via the PM
scanner SCANBTSM - RNDTDELBTS. It defines how many ping request packets are
sent per minute.
SCANBTSM provides only ping delay measurement results if the attribute is set to a
value greater than 0.
Validity Range
0 - 120
690
Id:0900d8058024fcdc
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Default Value
0
Contained in the following commands:
CREATE CESTUNNEL, GET CESTUNNEL, SET CESTUNNEL
PNGPKT
pingPacketSize
The attribute is only meaningful if the ping delay measurement is activated via the PM
scanner SCANBTSM - RNDTDELBTS. It defines the size of a ping request packet. The
value small corresponds to the default packet size of the ICMP ping request. Value
traffic corresponds to the maximum packet size within the pseudo wires of the tunnel.
Validity Range
SMALL
TRAFFIC
Default Value
TRAFFIC
Contained in the following commands:
CREATE CESTUNNEL, GET CESTUNNEL, SET CESTUNNEL
PNOFACCH
periodNotificationFACCH(sec)
The attribute defines the period (repetition rate) for the FACCH notification for a given
ASCI call.
A change of the attribute becomes effective at expiration of the current time period,
latest after the time given by "periodNotificationFACCH".
Validity Range
1.0 - 5.0
Default Value
2.5 seconds
Contained in the following commands:
GET BTS
PRDINF
productInfo(prodNbr_SN_HwVer_SwVer)
A50016-G5100-B333-04-7619
Id:0900d8058024fcdc
691
BS-4x / 82 II / 240 / 241 / 240XL commands
The attribute shows product specific information of the TMA if HDLC signaling is used
and information is provided by the TMA. It is represented by a single string, consisting
of four parts, separated by a couple of defined delimiters:
delimiter1 ;
delimiter2 (a white space)
This attribute will be retrieved by own command get TMA prodInfo.
Validity Range
0..77 characters string
Default Value
None.
Contained in the following commands:
GET TMA, GET TMA PRODUCTINFO
PRDIRECT
preferredDirection
The attribute indicates whether the RX downlink information is gained from the related
BPORT or not. In a loop configuration the preferred direction is changed, if e.g. the Bit
Error Rate is greater than a certain threshold or if the link fails.
'TRUE' means that the RX data at the given BPORT instance is used as input data.
'FALSE' means that the RX data at the given BPORT instance is not used as input data.
The attribute is meaningful only in a loop configuration. If a GET is done in other configurations the length will be set to 0.
Validity Range
TRUE
FALSE
<NULL>
Default Value
None.
Contained in the following commands:
GET BPORT
PRS
proceduralStatus
This attribute is contained in all equipment related managed objects. It indicates whether
the assigned HW board performs an initialization procedure. For non processor HW
boards, the proceduralStatus is always NULL.
This attribute is readable by the operator but is not contained in the "Changed State
Event Report" notification.
692
Id:0900d8058024fcdc
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
NULL
initializing
Default Value
NULL
Contained in the following commands:
GET ACDCP, GET ACT, GET BATTERY, GET BCOM, GET BPORT, GET BTSEP
NOSWL, GET CESPW, GET CESTUNNEL, GET COBA, GET COBAETHINTF, GET
COSA, GET CU, GET DIDCTMA, GET DILNA, GET DUAMCO, GET DUDCTMA,
GET DULNA, GET DUVSWR, GET ENVABTSE, GET ETHCON, GET ETHPORT,
GET F6DCTMA, GET F6LNA, GET F6TNFP, GET F6VSWRP, GET FANP, GET
FCUMAIN, GET FCUTR, GET FTNFP, GET FVSWRP, GET LAPDLE, GET RACK,
GET SYNCBTSE, GET TMA, GET XCONNECT
PSTAT
portStatus
This attribute provides the result of the auto negotiation procedure. If auto negotiation is
disabled the current setting of the port is shown.
Validity Range
speed
speed100M
speed1000M
duplexMode
disabled
enabled
flowControl
disabled
enabled
Default Value
None.
Contained in the following commands:
GET ETHPORT
PUSG
portUsage
This attribute determines usage of the Ethernet port at BTSE. Only one ETHPORT
instance can be set to BSClink. From one BTS only one port can be configured as multidropLink. If the base stations are synchronized via Abis it is recommended to limit the
number of cascaded stations to 5.
Validity Range
bscLink
A50016-G5100-B333-04-7619
Id:0900d8058024fcdc
693
BS-4x / 82 II / 240 / 241 / 240XL commands
multidropLink
Default Value
None.
Contained in the following commands:
CREATE ETHPORT, GET ETHPORT, SET ETHPORT
PWNAME
pwName
This attribute specifies optional symbolic name of the pseudo wire, the same name
should be configured at the peer side. The name has to be unique within all CESPW
instances on given host.
Validity Range
1..80 characters string
Default Value
None.
Contained in the following commands:
CREATE CESPW, GET CESPW, SET CESPW
PWROUT
powerOutputThresholds
This attribute defines the three power output thresholds:
-
Output Power Fault Threshold: defines the minimal output
power level "transmitter-fault", which results in generating an
alarm.
Reduced Output Power Threshold: defines the power level,
when an alarm (warning) is generated (Pout alm red) due to
less output power.
Excessive Output Power Threshold: defines the power level,
when an alarm is generated (Pout alm fault) due to too much
power level at the output of the power amplifier.
The attribute value is indicated in dB.
The letter "m" before the value range values, means minus
Validity Range
oPwrFaultThreshold m10db
m8db
694
Id:0900d8058024fcdc
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
redOutPwrThreshold
m10db
m8db
m6db
m4db
excesOutPwrThresh db3
db5
Default Value
m10dB = -10dB
m6db = - 6dB
db5 = 5dB
Contained in the following commands:
GET BTS
PWRRED
txPwrMaxReduction(*-2dB)
This attribute specifies the number of 2dB steps the TRX should be reduced from the
maximum transmit power, for tuning the cell coverage. The resulting attenuated transmit
power is the maximum nominal power Pn.
(values from 0 dB to -12 dB, with step size - 2 dB)
Validity Range
0-9
Default Value
None.
Contained in the following commands:
GET TRX
A50016-G5100-B333-04-7619
Id:0900d8058024fcdc
695
BS-4x / 82 II / 240 / 241 / 240XL commands
r
RACHBT
rachBusyThreshold(dBm)
This attribute defines a threshold for the received signal level concerning both:
-
RACH access bursts
intercell HO access bursts.
A signal level exceeding this threshold is interpreted as a busy RACH
respective as a valid burst due to an intercell HO.
Validity Range
<ANY>
Default Value
109
Contained in the following commands:
GET BTS
RACHLAS
rachLoadAveragingSlots
This attribute defines the number of RACH bursts over which RACH measurements are
performed.
Validity Range
102 - 65535
Default Value
204 = 4 CCCH multiframes
Contained in the following commands:
GET BTS
RADIOMG
radioMeasGran
This is an attribute of the TRX and specifies the granularity (multiples of 480 ms) in
which the radio measurements have to be transmitted on the Abis interface in case they
are enabled.
The attribute is indicated in SACCH multiframes
696
Id:0900d8058051e912
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
1 - 254
Default Value
254 in SACCH multiframe
Contained in the following commands:
GET TRX
RADIOMR
radioMeasRep
This is an attribute of the TRX and specifies whether the radio measurements have to be transmitted on the Abis interface.
Notes:
-
A consequence of the value 'disabled' is that no 'Measurement result' messages are sent to the BSC.
Special care has to be applied if the attribute is set to "ON" for
several TRXs: the appropriate Abis signalling capacity must
be provided by creating a sufficient number of LAPDLE
instances each with a full 64 KBit/s timeslot. If this prerequisite
is not fulfilled (e.g. just 1 LAPDLE and 11 TRXs with full and
half rate are fully exploited - FEKAT CR2826) the Call Failure
Rate will increase (increased delay times in the BTSE LAPD
queues due to the huge amount of measurement result
messages lead to more CHANNEL REQUIRED messages
because of a too late Immediate Assignment command etc.
etc.). This is especially critical if RADIOMG is set to 1 (corresponding to 480 ms).
(ON = enabled)
Validity Range
OFF
ON
Default Value
OFF (disabled)
Contained in the following commands:
GET TRX
RELEQUIPOBJ
relatedEquipObjects
A50016-G5100-B333-04-7619
Id:0900d8058051e912
697
BS-4x / 82 II / 240 / 241 / 240XL commands
This attribute represents the relationships between a specific FMO
instance and none, one or several HMO instances. The HMO
instances in this list offers their services to the given FMO instance.
This attribute is only allowed for BTSM, BTS, TRX and CHANNEL.
FMO
maximal number of
related HMOs
N (decimal)
BTS
BTSM
CHAN
TRX
30
122
Validity Range
0 to 47 items of
Pathname
Default Value
None.
Contained in the following commands:
GET BTS, GET BTSM NOSWL, GET CHAN, GETRELATIONSHIP TRX
RELFUNCOBJ
relatedFuncObjects
This attribute represents the relationships between a specific HMO
instance and none, one or several FMO instances. The FMO
instances in this list make use of the services of the given HMO
instance. This attribute is allowed for each HMO instance of the actual
hardware variant. Currently only BTSM and TRX are contained in the
list.
Since the maximal number of related FMO instances in the list
depends on the special type of HMO, the following list shows the realistic values for the each HMO that may contain related FMO
instances. The table shows for each HMO the maximal number of
FMO instances and the maximum number of octets of the attribute
including the attribute identifier and attribute length field.
698
HMO
maximal number of
related FMOs
N (decimal)
BPORT
BTSE
Id:0900d8058051e912
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CESPW
CESTUNNEL
COBAETHINF
ENVABTSE
LAPDLE
RACK
SYNCBTSE
48
194
XCONNECT
HMO
maximal number of
related FMOs
N (decimal)
ACDCP
ACT
BATTERY
BCOM
12 (see note 1)
50
COBA
48
194
COSA
24 (see note 2)
98
CU
DIDCTMA
24
98
DILNA
24
98
DUAMCO
DUDCTMA
24
98
DULNA
24
98
DUVSWR
24
98
ETHCON
F6DCTMA
12 (see note 3)
50
F6LNA
12 (see note 3)
50
F6TNFP
F6VSWRP
26
FANP
FCUMAIN
10
FCUTR
FTNFP
FVSWRP
34
LMU
SDULNA
34
SDUSEC
18
A50016-G5100-B333-04-7619
Id:0900d8058051e912
699
BS-4x / 82 II / 240 / 241 / 240XL commands
SDUSUBSEC
34
SDUTXSW
TMA
24
98
Note 1: only for BS288/BS289 (for BS240XS:6 FMOs)
Note 2: COSA old (if enableFcuSupport = TRUE) and COSA new only
can handle up to 12 FCU (24 TRX)
Note 3: If using a double "cross-cascading" FICOM6 configuration
with SDTMA
Validity Range
0 to 48 items of
Pathname
Default Value
None.
Contained in the following commands:
GET ACDCP, GET ACT, GET BATTERY, GET BCOM, GET BPORT, GET BTSEP
NOSWL, GET CESPW, GET CESTUNNEL, GET COBA, GET COBAETHINTF, GET
COSA, GET CU, GET DIDCTMA, GET DILNA, GET DUAMCO, GET DUDCTMA,
GET DULNA, GET DUVSWR, GET ENVABTSE, GET ETHCON, GET ETHPORT,
GET F6DCTMA, GET F6LNA, GET F6TNFP, GET F6VSWRP, GET FANP, GET
FCUMAIN, GET FCUTR, GET FTNFP, GET FVSWRP, GET LAPDLE, GET RACK,
GET SYNCBTSE, GET TMA, GET XCONNECT, GETRELATIONSHIP BCOM, GETRELATIONSHIP COBA
REPTYP
reportType
This parameter is used to indicate to the mobile station to use the ENHANCED MEASUREMENT REPORT or MEASUREMENT REPORT messages for reporting, and it
can assume two values:
- NORMAL: the MS uses the MEASUREMENT REPORT message for reporting
- ENHANCED: the MS uses the ENHANCED MEASUREMENT REPORT message for
reporting if at least one BSIC (Base Station Identity Code) is allocated to each frequency
of the BA (BCCH Allocation) list . Otherwise, the MEASUREMENT REPORT message
is used.
Validity Range
ENHANCED
700
Id:0900d8058051e912
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
NORMAL
ENHANCED_ONLY_FOR_
R43G_MS
Default Value
None.
Contained in the following commands:
GET BTS
RFRSINDP
rfResourceIndicationPeriod
This attribute indicates the sending rate of the signalling message RF RES IND to the
BSC.
The attribute is indicated in unit of SACCH multiframes
Validity Range
1 - 254
Default Value
60 in unit of SACCH multiframe
Contained in the following commands:
GET BTS
RSACCHRXLDL
repSacchRxLevDL
This attribute is used to define, on a per cell basis, the threshold for RXLEV_DL_SUB
used in the decision algorithm for activating R-SACCH in DL and UL for MS with
Repeated SACCH Capability, i.e. R-ACCH_CAP = 1.
Validity Range
0 - 25
Default Value
None.
Contained in the following commands:
GET BTS
RSACCHRXLUL
repSacchRxLevUL
A50016-G5100-B333-04-7619
Id:0900d8058051e912
701
BS-4x / 82 II / 240 / 241 / 240XL commands
This attribute is used to define, on a per cell basis, the threshold for RXLEV_UL_SUB
used in the decision algorithm for activating R-SACCH in DL and UL for MS with
Repeated SACCH Capability, i.e. R-ACCH_CAP = 1.
Validity Range
0 - 25
Default Value
None.
Contained in the following commands:
GET BTS
RSACCHTODL
repSacchTimeOutDL
This attribute is used to define, on a per cell basis, the threshold for deactivation of RSACCH mode in the decision algorithm for R-SACCH in DL for MS with Repeated
SACCH Capability, i.e. RACCH_CAP = 1.
Validity Range
0 - 10
Default Value
None.
Contained in the following commands:
GET BTS
RSACCHTOUL
repSacchTimeOutUL
This attribute is used to define, on a per cell basis, the threshold for deactivation of RSACCH mode in the decision algorithm for R-SACCH in UL for MS with Repeated
SACCH Capability, i.e. RACCH_CAP = 1.
Validity Range
0 - 10
Default Value
None.
Contained in the following commands:
GET BTS
RXBMAXF
rxBandMaxFreq(kHz*100)
702
Id:0900d8058051e912
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Attribute data provided by the TMA.
Validity Range
0 - 65535
<NULL>
Default Value
None.
Contained in the following commands:
GET TMA
RXBMINF
rxBandMinFreq(kHz*100)
Attribute data provided by the TMA.
Validity Range
0 - 65535
<NULL>
Default Value
None.
Contained in the following commands:
GET TMA
RXDIVSV
enableRxDiversitySupervision
The attribute enableRxDiversitySupervision of the object 'BTSE' indicates whether the
supervision of the RX levels and the signal to noise ratio of both receiver branches is
enabled or disabled. A prerequisite is that diversity is configured and that a TCH or
SDCCH is on at least 2 time slots of the TRX. Due to the supervision failure event reports
for the TPU / CU related to a TRX may be sent.
Validity Range
disabled
enabled
Default Value
disabled
Contained in the following commands:
GET BTSEP NOSWL, SET BTSEP
A50016-G5100-B333-04-7619
Id:0900d8058051e912
703
BS-4x / 82 II / 240 / 241 / 240XL commands
RXLEVADJ
rxLevAdjust(dB)
This attribute specifies the value needed to adjust the RXLEV value of both receiver
branches ("N" and "D") of the TPU, CU and of the FCUMAIN.
The attribute has no functionality in case a FCUMAIN is wired to a SDUAMCO.
(values from -24 dB to +23 dB)
Validity Range
adjustValue
-24.0 - 24.0
adjustDivValue
-24.0 - 24.0
Default Value
adjustValue
0.0
adjustDivValue
0.0
Contained in the following commands:
CREATE CU, CREATE FCUMAIN, GET CU, GET FCUMAIN, SET CU, SET
FCUMAIN
RXLEVADJN1D1
rxLevAdjustN1D1(dB)
This attribute specifies the value needed to adjust the RXLEV value of the additional
receiver branches "Rx C / N1" and "Rx D / D1" of the FCUMAIN.
The attribute has no functionality in case a FCUMAIN is wired to a SDUAMCO).
Validity Range
adjustValueN1
-24.0 - 24.0
adjustDivValueD1
-24.0 - 24.0
Default Value
adjustValueN1
0.0
adjustDivValueD1
0.0
Contained in the following commands:
CREATE FCUMAIN, GET FCUMAIN, SET FCUMAIN
RXSIGLEVADJ
rxSigLevAdjust
The attribute specifies the signal level adjust values which shall be applied to the receive
paths of transceivers using the same frequency band as the BCCH transceiver.
704
Id:0900d8058051e912
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
<ANY>
Default Value
None.
Contained in the following commands:
GET BTS
RXSIGLEVADJC
rxSigLevAdjustCompl
The attribute specifies the signal level adjust values which shall be applied to the
transmit paths oftransceivers using the complementary frequency band. The value is
only meaningful in case of a multiband cell.
Validity Range
<ANY>
Default Value
None.
Contained in the following commands:
GET BTS
RXSWCURSET
rxSwitchCurrentSetting
Usually the content of this attribute is identical to the value of the attribute rxSwitchReqSetting. A deviation is possible e.g. in case of HW failures - in these cases the attribute
shows the real situation. The attribute has a meaning only if the value of the attribute
switchedBeamCapability has the value four_beams.
A change of the attribute value is sent by the BTSE via CAER to the BSC.
Validity Range
NULL
Default Value
None.
Contained in the following commands:
GET BTS
A50016-G5100-B333-04-7619
Id:0900d8058051e912
705
BS-4x / 82 II / 240 / 241 / 240XL commands
s
SALUNAME
salesUniqueName
The attribute contains an ASCII string with 11 characters which don't
contain a NUL character. The operator has always to enter 11 characters for the attribute. If the operator has not yet supplied a value for
the attribute but does a GET, the BTSE SW will return the 'default
value'. The attribute should be set by the operator before a upload of
the IDT is performed.
The attribute is also used during the Abis alignment for checking if the
right BTSE is connected to the Abis link.
Default Value: length = 1, octet 3 = 0
Validity Range
In commands GET BTSEP NOSWL:
1..11 characters string
In commands SET BTSEP:
11..11 characters string
Default Value
length = 1, octet 3 = 0
Contained in the following commands:
GET BTSEP NOSWL, SET BTSEP
SBPRT
syncBport
This attribute indicates the port which is currently used for synchronization. This information is specially useful in case of a PCM loop configuration.
Validity Range
<ANY>
Default Value
None.
Contained in the following commands:
GET SYNCBTSE
SBSCSLCV
superordinateBscSwLoadCurrentVersion
706
Id:0900d8058024ebff
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
This attribute contains the version number of the software load (26 bytes) that is currently running in the BSC.
Note: this attribute will not be stored in the BSC MIB master copy; it will be evaluated at
run-time by the system taking the information from the System Download SW Functional
area.
ASCII string: "SS-VV-RR-PR-LL-CL_yy-mm-dd" where
SS : System (02 = BSS)
VV : Version ("major version": e.g. 10 for BR10.x)
RR : Release ("minor version": e.g. 05 for BR9.5)
PR : Point Relase (usually 01, sometimes 02)
LL : Load Level (incremented at each CM load, starting form 00)
CL : Consolidation level (incremented at each crunch)
yy-mm-dd : production date (optional)
Validity Range
26..26 characters string
Default Value
None.
Contained in the following commands:
GET BTSM SWL
SCELLNO
secondCellNumber
This attribute allows to indicate a second cell number for the objects DILNA and DULNA.
Value <FF> means that a secondCellNumber is not used.
The second cell number allows sharing an antenna for receive diversity, i.e. it allows that
two cells with different MNC (Mobile Network Code) which cover the same area (e.g. the
same sector) at the BTSE site can share the same DUAMCO/FDUAMCO or IAMCO if
receive diversity is required. As a consequence a DULNA-, DILNA- or TMA instance
may belong to two cells.
The relation between a carrier unit and cell is derived from the TX wiring only, i.e. the
attribute cellNumber of the wired DUVSWR object determines the cell a CU/FCUTR
belongs to. The BTSE checks for each CU that one of the attributes cellNumber and secondCellNumber of all wired DULNA/DILNA objects matches with the attribute cellNumber of the wired DUVSWR.
It is strongly recommended to ensure for each CU/FCUTR that the attribute cellNumber
of one wired DULNA object matches with the cellNumber of the wired DUVSWR.
Validity Range
N_00
N_01
N_02
A50016-G5100-B333-04-7619
Id:0900d8058024ebff
707
BS-4x / 82 II / 240 / 241 / 240XL commands
N_03
N_04
N_05
N_06
N_07
N_08
N_09
N_10
N_11
NotUsed
Default Value
None.
Contained in the following commands:
CREATE DILNA, CREATE DULNA, CREATE F6LNA, GET DILNA, GET DULNA,
GET F6LNA, SET DILNA, SET DULNA, SET F6LNA
SCID
sectorId
Attribute data provided by the TMA.
Validity Range
0..32 characters string
Default Value
None.
Contained in the following commands:
GET TMA
SCLPRIOLST
serviceClassPrioList
Default settings of this attribute for CES service correspond to expedited forwarding:
service
Class
708
CES
Service
class to
whitch the
priority
settings
apply
Id:0900d8058024ebff
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
vlanPrio
The attribute
is not
relevant if
vlanid is set
to NULL
dscpClass
DSCP class
selector.
The value is
the decimal
representation of the
DSCP bits
0-2.
dscpDropPre
DSCP drop
precedence. The
value is the
decimal representation
of the DSCP
bits 3-5.
List of up to 8 service classes. Currently only the service class CES is supported. When
value CES is set for serviceClass all other attributes must not be set to default values.
Maximum one list entry is allowed for each service class.
Validity Range
1 to 8 items of
serviceClass
ces
vlanPrio
vPrio0
vPrio1
...
vPrio7
dscpClass
dCl0
dCl1
...
dCl7
dscpDropPre
dDP0
dDP1
...
dDP7
A50016-G5100-B333-04-7619
Id:0900d8058024ebff
709
BS-4x / 82 II / 240 / 241 / 240XL commands
Default Value
serviceClass
ces
vlanPrio
vPrio7
dscpClass
dCl5
dscpDropPre
dDP6
Contained in the following commands:
GET BTSEP NOSWL, SET BTSEP
SFPSERID
sfpSerialId
This attribute represents serial Id data if a SFP module is equipped.
The attribute is only meaningful for ports with SFP cages, i.e. it is not relevant for the
ETHPORT instances 0 and 1.
The structure of the octet string is compliant to the addresses 0 - 127 of the Serial ID
data at address A0.
Validity Range
0 to 128 items of
H#0 - H#ff
Default Value
None.
Contained in the following commands:
GET ETHPORT
SHLAPDIT
shortLapdIntTimer(sec)
The BTSE uses the value of this timer to calculate the value of timer T202 which is used
for the TEI assignment procedure.
This attribute is the timer used by the BSC in case of Abis link failure in order to discriminate between a "fast alignment" or a "full alignment". With the detection of the link failure
(which may happen at different times in BTSE and BSC) the BTSE starts the timer
'omLAPDRelTimer' and the BSC starts the timer 'shortLAPDIntTimer'. If any LAPD link
on any of the LAPDLE signalling timeslots is up again within a certain time (i.e. the timer
'shortLAPDIntTimer' in the BSC has not yet expired) the BSC may decide to perform the
fast alignment procedure.
At the detection time of the Abis link failure the BTSE starts the timer omLAPDRelTimer
and the BSC starts the timer shortLAPDIntTimer. If the timer omLAPDRelTimer expires,
the BTSE blocks the call processing. After that the BTSE forces the BSC (via a Restart
Sending Event Reports NACK message) to perform a complete Abis alignment. If none
of the two timers expires, the BSC performs a 'Short Abis alignment'.
(step size 1 second)
710
Id:0900d8058024ebff
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
3 - 20
Default Value
15 seconds
Contained in the following commands:
GET BTSM NOSWL
SLOTNO
slotNo
The attribute indicates the slot number of the COBA and COSA. Since the modelling of
the MO COBA is fixed (active COBA/COSA always COBA(0)/COSA(0), passive
COBA/COSA always COBA(1)/COSA(1)), this is the only way to find out the slot of the
active / passive COBA/COSA.
Validity Range
leftCOBA
rightCOBA
leftCOSA
rightCOSA
Default Value
None.
Contained in the following commands:
GET COBA, GET COSA
SRCDIR
sourceDir
The sourceDirectory indicates the directory containing the BTS-SW
to be downloaded (DNLALLEXE).
The sourceDirectory indicates the directory containing the BTSE nobRIU file to be downloaded (DNLIDFD).
Validity Range
1..80 characters string
Default Value
None.
Contained in the following commands:
DNLIDFD REMINV
A50016-G5100-B333-04-7619
Id:0900d8058024ebff
711
BS-4x / 82 II / 240 / 241 / 240XL commands
SRCPATH
srcpath
The sourceDirectory indicates the directory containing the BTS-SW to be downloaded
(DNLALLEXE).
Validity Range
1..92 characters string
Default Value
None.
Contained in the following commands:
DNLALLEXE SOFTWARE-MANAGEMENT
STATIME
startingTime
This attribute is only used together with btsIsHopping and can not be set by the operator.
Current Frame No is a binary presentation Frame Number Modulus 42432.
Note: startingTime is only used together with btsIsHopping.
Validity Range
0 - 65535
<NULL>
Default Value
None.
Contained in the following commands:
GET BTS TIMER
STDBYST
standbyStatus
The resource is not providing service but it is able to take over the role of the resource
to be backed-up without an initialization. The resource is providing service and it is
backing up another resource.
ColdStandBy:
The Carrier Unit is not providing service but is able to take over the active role.
ProvidingService:
The Carrier Unit is assigned to a TRX and is providing service.
NULL:
712
Id:0900d8058024ebff
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
The Carrier unit is not able to take over the active role because of failures or missing
configuration data.
Validity Range
Reserved
ColdStandBy
ProvidingService
NULL
Default Value
None.
Contained in the following commands:
GET COBA, GET COSA, GET CU, GET FCUTR, GET LAPDLE
SUBUNT
subUnitType
Attribute data provided by the TMA.
Validity Range
vswr
bypass
<NULL>
Default Value
None.
Contained in the following commands:
GET TMA
SWBCAPABILITY
switchedBeamCapability
This attribute reflects the capability of the BTSE hardware and software. A change of the
attribute value is sent by the BTSE via CAER to the BSC.
- unknown means the BTSE is not yet fully configured (e.g. SDUSEC not yet created)
- none means the BTSE hardware and/or software does not support switched beams.
- four_beams means the BTSE hardware and software supports 4 switched beams.
A50016-G5100-B333-04-7619
Id:0900d8058024ebff
713
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
none
Default Value
None.
Contained in the following commands:
GET BTS
SWBSERVSTATE
switchedBeamServState
The attribute indicates the current state of the switched beam functionality. A change of
the attribute value is sent by the BTSE via CAER to the BSC. The values have the following meaning:
NULL Initial value if BTSE is not aligned or default value if the BTSE type does not
support switched beams.
Validity Range
NULL
Default Value
None.
Contained in the following commands:
GET BTS
SWLCFID
swLoadCurrentFileId
This attribute contains the fileID (name of the SW load, 12 byte) of the software load that
is currently running in the BTSE. A SW load is the SW for the whole NE, that is able to
run on the processors of the NE at the same time. It consists of a certain number of SW
images, that are not shown to the operator for the BTSE.
Notes on validity range:
ASCII String: 'HScnvvss.SWL" (swLoad-header file), where:
cn Version part (network operator code)
01 = Ciphering A5.0 + A5.1 + A5.2
02 = Ciphering A5.0 + A5.2 12
03 = Ciphering A5.0 only
vv Version part (feature package code)
ss Version part (actual state)
714
Id:0900d8058024ebff
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
12..12 characters string
Default Value
None.
Contained in the following commands:
GET BTSM SWL
SWLCVER
swLoadCurrentFileVersion
This attribute contains the version number of the software load (26 bytes) that is currently running in the BTSE. Under normal operation conditions it is the same as the
version number of the swLoadIntended (SWLDINT). If the latter SW load is corrupted,
the swLoadCurrentVersion is identical to the version number of the swLoadSafety
(SWLDSAF) or the version number of the third SW load that is stored in the BTSE (the
dischargeable one). It is guaranteed that only SW loads are automatically started by the
BTSE, which have been executed on that BTSE before.
Notes on validity range:
ASCII String:cn-hh-vv-ii-ss-pp_yy-mm-dd, where:
cn Version part (network operator code)
01 = Ciphering A5.0 + A5.1 + A5.2
02 = Ciphering A5.0 + A5.2 12
03 = Ciphering A5.0 only
hh Version part (HW/SW compatibility code)
01 = BS20, BS21E, BS60, BS61E or BS22
04 = BS240, BS241, BS240XL, BS240SR, BS241SR,
BS240XLSR, BS40, BS40II, BS41, BS82II, BS82,
BS240XS, BS288
vv Version part (feature package code)
ii Version part (sub-feature package code)
00 = independent (e.g. loadable boot/test SW
01 = BS240, BS241, BS240XL, BS40, BS40II, BS41,
BS82II
05 = BS82
06 = BS240XS, BS288
ss Version part (actual state)
pp Patch version (usually 00)
A50016-G5100-B333-04-7619
Id:0900d8058024ebff
715
BS-4x / 82 II / 240 / 241 / 240XL commands
yy-mm-dd production date (optional)
Validity Range
26..26 characters string
Default Value
None.
Contained in the following commands:
GET BTSM SWL
SWLDINT
swLoadIntended
This attribute is divided into 2 parts and defines the file ID (=file name) and version
number of the SW load stored in the BTSE, that has been activated over the Abis- or Tinterface with the latest 'Activate SW' message. This SW load is automatically activated
from the BTSE firmware at power on time.
The file ID (= file ID for a SW load) and the version number () are supplied by the BTSE
after the 'Activate SW' message was sent. The value for both parts is 'not valid', if there
was no 'Activate SW' message before, or "swLoadCurrent", if the intended SW load is
corrupted.
Notes on validity range:
swLoadIntendedFileId: Coding according to swLoadCurrentFileId
Default Value: 0"filename.ext"
Octet #15 contains the ASCII character ":".
swLoadIntendedVersion: Coding according to swLoadCurrentVersion
Default Value: "cn-hh-vv-ii-ss-pp_yy-mm-dd"
The value 'not valid' for this attribute is indicated via '0' as byte 3.
Validity Range
39..39 characters string
Default Value
None.
Contained in the following commands:
GET BTSEP SWL
SWLDSAF
swLoadSafety
716
Id:0900d8058024ebff
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
This attribute is divided into 2 parts and describes the file ID (= file ID for a SW load) and
the version number () of the SW load stored in the BTSE, that is identified by the
operator at the OMC or LMT (via a 'Set Attribute' message at the Abis- or T- interface or
a M-SET service at the O-interface) as the most trusted SW load (in the sense of its
ability to handle the Abis-link to build up a connection to the BSC). It is used if the
swLoadIntended is damaged in some way. There is no alignment to one of the SW loads
stored on the BSC master database. It is even not necessary, that this SW load is stored
in the BSC master database. The identification of a SW load as the safety one is only
accepted by the BTSE, if the identified load has been activated and executed on this
BTSE before. It is recommended that an update of the attribute is performed in each
release and that the swLoad of the previous release is used as 'swLoadSafety'.
The value 'not valid' indicates that the safety SW load is corrupted or has not been identified by the operator.
Notes on validity range:
swLoadSafetyFileId: Coding according to 'swLoadCurrentFileId'
default value: 0"filename.ext"
Octet #15 contains the ASCII character ":".
swLoadSafetyVersion: Coding according to 'swLoadCurrentVersion'
default value: "cn-hh-vv-ii-ss-pp_yy-mm-dd"
The value 'not valid' for this attribute is indicated via '0' as byte 3.
Validity Range
39..39 characters string
Default Value
None.
Contained in the following commands:
GET BTSEP SWL, SET BTSEP
SWLDST
swLoadsStored
This attribute contains the file IDs (= file ID for a SW load) and version numbers of up to
three SW loads, that are stored in the BTSE Flash Eprom. The attribute is divided into
3 main parts, each part split up in the fileID and file version of one SW load.
In principle there are two different 'kinds' of values for one load version: one indicating
the file ID and load version number of the SW load of the BTSE, that has been successfully downloaded and that has been recognized by the BTSE as a complete load; the
second one, the 'not valid' value, indicating that no load has been downloaded into that
partition of the BTSE Flash Eprom, or that the download is not complete, or that the
stored SW load is corrupted as the check sum is not correct any more.
Octets #15, #55 and #93 contain the ASCII character ":".
The value 'not valid' is indicated as 0 (hexadecimal) for the octets #3 or #42 or #81.
A50016-G5100-B333-04-7619
Id:0900d8058024ebff
717
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
3 to 3 items of
39..39 characters string
Default Value
None.
Contained in the following commands:
GET BTSEP SWL
SYNCSRC
syncSource
This attribute specifies the preferred synchronization source, i.e. whether the BTSE
should be synchronized via Abis or to a 3rd party GPS receiver.
If the attribute value is extGPS further attributes become relevant:
- enableInterSiteSync
- burstNumberOffset
- frameNumberOffset
- maxPhaseError
- maxResyncTime
By setting the syncSource attribute to ext_1pps_only the BTSE 1 is synchronized to an
external device which delivers 1pps pulses. There is no switching to a secondary synchronization source if the 1pps signal fails.
The attribute "1pps only" is supported only for COBA4P12v2 and CESCOBA.
Validity Range
abis
extGPS
ext_1pps_only
Default Value
abis
Contained in the following commands:
GET SYNCBTSE, SET SYNCBTSE
SYNCSTAT
syncState
This attribute indicates the details of the synchronisation process of the BTSE.
Validity Range
init
718
Id:0900d8058024ebff
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
ready
abis
abisHoldMode
syncUnit
syncUnitHoldMode
Default Value
None.
Contained in the following commands:
GET SYNCBTSE
SYSID
cellAllocationNumber
This attribute indicates the frequency band used by the traffic channels.
Validity Range
BB900
DCS1800
F2ONLY900
EXT900
PCS1900
GSMR
GSMDCS
GSM850
GSM850PCS
GSM850DCS
Default Value
None.
Contained in the following commands:
GET BTS
A50016-G5100-B333-04-7619
Id:0900d8058024ebff
719
BS-4x / 82 II / 240 / 241 / 240XL commands
t
T200
t200
This attribute contains values for the LapDm timer T200 to be used on different control
channels.
Validity Range
sdcchSAPIO
0 - 255
facchTCHF
0 - 255
facchTCHH
0 - 255
saccchTCHSAPIO
0 - 255
sacchSDCCH
0 - 255
sdcchSAPI3
0 - 255
sacchTCHSAPI3
0 - 255
Default Value
SDCCH
29 ms
FACCH/Full rate
31 ms
FACCH/Half rate
38 ms
SDCCH SAPI3
90 ms
SACCH with TCH SAPI0 70 ms
SACCH with SDCCH
SACCH with TCH
29 ms
168 ms
Contained in the following commands:
GET BTS TIMER
T3105
btsTimer3105(*10ms)
This attribute contains the value of the timer T3105, which is used for the repetition of
the PHYSICAL INFORMATION message.
The attribute step size is 10 msec.
Validity Range
1 - 254
Default Value
1 (corresponding to 10 ms)
Contained in the following commands:
GET BTS
720
Id:0900d80580592ba0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
T3115
t3115(*10ms)
T3115 is a timer to define the repetition rate of sending the VGCS UPLINK GRANT
message. In case of a ASCI-call the network grants the uplink to one mobile station by
sending a VGCS UPLINK GRANT message to the mobile station. After having sent this
message the BTS starts T3115 to repeat this message as long as a counter not reached
the value of ny2 or a correctly decoded frame was received.
(value indicated in milliseconds; step size 10 ms)
Validity Range
1 - 254
Default Value
4 (corresponding to 40 ms)
Contained in the following commands:
GET BTS TIMER
T3151
uplBusyRepRate
This attribute determines the repetition rate for the upl_busy message per cell. Default
suggested value: 3 sec.
Validity Range
1-9
Default Value
None.
Contained in the following commands:
GET BTS
TAADJ
taAdjust(microseconds)
This attribute takes the propagation delay created on the BTS internal signal path into
account. It comprises both transmit and receive direction i.e. it is the sum of the transmit
delay and the receive delay. The attribute taAdjust refers to the whole cell.
(value indicated in nanoseconds; step size 100 ns).
Validity Range
0.0 - 10.0
Default Value
0 (0 nanoseconds)
A50016-G5100-B333-04-7619
Id:0900d80580592ba0
721
BS-4x / 82 II / 240 / 241 / 240XL commands
Contained in the following commands:
GET BTS TIMER
TCC
txCoherentComb
This attribute allows the user to enable/disable the transmission coherent combining for
FlexCU V2 feature.
Validity Range
TRUE
The user can set the TRUE value only when THE
FCUMODE attribute equals doubleCUMode
FALSE
Default Value
FALSE
Contained in the following commands:
CREATE FCUMAIN, GET FCUMAIN, SET FCUMAIN
TCCCHLDI
thresholdCcchLoadIndication
This attribute is used if the Paging Overload Handling is active in the BTS (see "periodCCHLoadInd"), to stop the Paging Overload Regulation, when the Paging Load goes
below the threshold.
Suggested value is: 50 (hex).
Note that when Paging Overload is active, all Pagings with IMSI are discharged until the
Paging Load goes below the threshold.
Note: in case of ASCI enabled in the cell, that is P1 Rest Octets for NCH info are set in
Paging Request Type 1, only one IMSI could fit in a Paging Request Type 1 and even
though Paging Load is only 50%, there is not enough space for the second IMSI in
Paging Request Type 1. In this case it could make sense to set the threshold to lower
values but take care that meanwhile all Pagings with IMSI are discharged.
The attribute value is indicated in %.
Validity Range
0 - 100
Default Value
100%
Contained in the following commands:
GET BTS
722
Id:0900d80580592ba0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
TDMAP
tdmMapping
This attribute determines the mapping of the payload data to internal TDM ports of virtual
BPORT corresponding to the given instance of CESPW. For each payload time slot
(pTs), which is contained in the UDP stream the target time slot number on the virtual
bport has to be set. Only subsequent payload time slots beginning with pTs1 can be
selected. The value 0 means no mapping.
Validity Range
pTs1
0 - 31
pTs2
0 - 31
pTs3
0 - 31
pTs4
0 - 31
pTs5
0 - 31
pTs6
0 - 31
pTs7
0 - 31
pTs8
0 - 31
pTs9
0 - 31
pTs10
0 - 31
pTs11
0 - 31
pTs12
0 - 31
pTs13
0 - 31
pTs14
0 - 31
pTs15
0 - 31
pTs16
0 - 31
pTs17
0 - 31
pTs18
0 - 31
pTs19
0 - 31
pTs20
0 - 31
pTs21
0 - 31
pTs22
0 - 31
pTs23
0 - 31
pTs24
0 - 31
pTs25
0 - 31
pTs26
0 - 31
pTs27
0 - 31
pTs28
0 - 31
pTs29
0 - 31
A50016-G5100-B333-04-7619
Id:0900d80580592ba0
723
BS-4x / 82 II / 240 / 241 / 240XL commands
pTs30
0 - 31
pTs31
0 - 31
Default Value
None.
Contained in the following commands:
CREATE CESPW, GET CESPW, SET CESPW
TEI
tei
This attribute contains the Terminal Endpoint Identifier used in the layer2 addressing on
the Abis-Interface for the logical O&M or Radio Signalling Link.
The values 0..63 of the validity range refers tro the 'Initial TEI'
Validity Range
In commands GET BTSM NOSWL, GET TRX:
0 - 128
In commands SET BTSM:
0 - 63
Default Value
None.
Contained in the following commands:
GET BTSM NOSWL, GET TRX, SET BTSM
TESTMODE
enableTestMode
This attribute determines whether transceiver test mode can be activated. This is only
possible for non BCCH transceivers if their administrative state is "locked". If the test
mode is activated, the transceiver sends dummy bursts on all time slots with the frequency dlTestFrequency and the output power reduced by testPowerReduction. All
other transceiver attributes are meaningless in test mode in the DL direction. In UL direction the transceiver attributes for normal operation apply.
If the test mode is deactivated, the attributes for normal operation apply in DL direction
again and the attributes dlTestFrequency and testPowerReduction are meaningless
instead.
Validity Range
TRUE
FALSE
724
Id:0900d80580592ba0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Default Value
None.
Contained in the following commands:
GET TRX
TESTMON
testMonitor
Up to 6 testMonitorInfo fields can present (depend on the board).
Working phases:
ACDCP
ACT
PreliminaryTestsAcdcp
BootEepromTestCu
EndTestAcdcp
SerialEepromTestCu
PreliminaryTestsAct
LocalTestLoopCu
CheckAlarmStatusAct
EndTestCu
PreliminaryTestsDilna
CheckAlarmStatusDilna
CheckAlarmStatusBattery
EndTestDilna
DIDCTMA
PreliminaryTestsDidctma
PreliminaryTestsCoba
CheckAlarmStatusDidctma
BootEepromTestCoba
EndTestDidctma
SerialEepromTestCoba
COSA
DILNA
PreliminaryTestsBattery
EndTestBattery
COBA
PreliminaryTestsCu
CheckAlarmStatusAcdcp
EndTestAct
BATTERY
CU
DUDCTMA PreliminaryTestsDudctma
EndTestCoba
CheckAlarmStatusDudctma
PreliminaryTestsCosa
EndTestDudctma
SerialEepromTestCosa
DULNA
EndTestCosa
PreliminaryTestsDulna
CheckAlarmStatusDulna
EndTestDulna
Working phases:
DUVSWR
FANP
PreliminaryTestsDuvswr
LMU
CheckAlarmStatusDuvswr
CheckAlarmStatusLmu
EndTestDuvswr
EndTestLmu
PreliminaryTestsFanp
FTNFP
PreliminaryTestsFtnfp
CheckAlarmStatusFanp
CheckAlarmStatusFtnfp
EndTestFanp
EndTestFtnfp
FCUMAIN PreliminaryTestsFcumain
FVSWRP
BootEepromTestFcumain
A50016-G5100-B333-04-7619
PreliminaryTestsLmu
Id:0900d80580592ba0
PreliminaryTestsFvswrp
CheckAlarmStatusFvswrp
725
BS-4x / 82 II / 240 / 241 / 240XL commands
SerialEepromTestFcumain
EndTestFcumain
FCUTR
EndTestFvswrp
SYNCBTSE
PreliminaryTestsSyncbtse
PreliminaryTestsFcutr
ResyncTestSyncbtse
LocalTestLoopFcutr
EndTestSyncbtse
EndTestFcutr
TMA
PreliminaryTestsTma
CheckAlarmStatusTma
EndTestTma
Validity Range
1 to 6 items of
phaseId
PreliminaryTestsAct
PreliminaryTestsCu
PreliminaryTestsCoba
PreliminaryTestsCosa
PreliminaryTestsFanp
PreliminaryTestsDilna
PreliminaryTestsDuvswr
PreliminaryTestsDulna
PreliminaryTestsBattery
PreliminaryTestsBcom
PreliminaryTestsTma
PreliminaryTestsDudctma
PreliminaryTestsDidctma
PreliminaryTestsAcdcp
PreliminaryTestsFvswrp
PreliminaryTestsFtnfp
726
Id:0900d80580592ba0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
PreliminaryTestsLmu
PreliminaryTestsSdulna
PreliminaryTestsSdusec
PreliminaryTestsSdusubsec
PreliminaryTestsSdutxsw
EndTestAct
EndTestCu
EndTestCoba
EndTestCosa
EndTestFanp
EndTestDilna
EndTestDuvswr
EndTestDulna
EndTestBattery
EndTestTma
EndTestDudctma
EndTestDidctma
EndTestFvswrp
EndTestFtnfp
EndTestLmu
EndTestSdulna
EndTestSdusec
EndTestSdusubsec
EndTestSdutxsw
SerialEepromTestCu
SerialEepromTestCoba
SerialEepromTestCosa
BootEepromTestCu
BootEepromTestCoba
A50016-G5100-B333-04-7619
Id:0900d80580592ba0
727
BS-4x / 82 II / 240 / 241 / 240XL commands
CheckAlarmStatusAct
CheckAlarmStatusFanp
CheckAlarmStatusDilna
CheckAlarmStatusDuvswr
CheckAlarmStatusDulna
CheckAlarmStatusBattery
CheckAlarmStatusBcom
CheckAlarmStatusTma
CheckAlarmStatusDudctma
CheckAlarmStatusDidctma
CheckAlarmStatusAcdcp
CheckAlarmStatusFvswrp
CheckAlarmStatusFtnfp
CheckAlarmStatusLmu
CheckAlarmStatusSdulna
CheckAlarmStatusSdusec
CheckAlarmStatusSdusubsec
CheckAlarmStatusSdutxsw
LocalTestLoopCu
SerialEepromTestFcumain
ResynctestSyncBtse
728
Id:0900d80580592ba0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
PreliminaryTestsSyncBtse
PreliminaryTestsFcutr
PreliminaryTestsFcumain
LocalTestLoopFcutr
EndTestSyncBtse
EndTestBcom
EndTestFcutr
EndTestFcuMain
BootEepromTestFcumain
PreliminaryTestsDuamco
CheckAlarmStatusDuamco
EndTestDuamco
PreliminaryTestsF6
dctma
PreliminaryTestsF6l
na
PreliminaryTestsF6t
nfP
PreliminaryTestsF6v
swrP
CheckAlarmStatusF
6dctma
CheckAlarmStatusF
6lna
CheckAlarmStatusF
6tnfP
CheckAlarmStatusF
6vswrP
EndTestF6dctma
EndTestF6lna
EndTestF6tnfP
EndTestF6vswrP
phaseStatus
Waiting 00
Pass 01
A50016-G5100-B333-04-7619
Id:0900d80580592ba0
729
BS-4x / 82 II / 240 / 241 / 240XL commands
Fail 02
Running 03
Default Value
None.
Contained in the following commands:
GET BTSETEST
TESTNO
testNo
This attribute corrisponde to the instance numeber of the test object.
Validity Range
0 - 255
Default Value
None.
Contained in the following commands:
STOPTEST BTSEP
TESTOUT
testOutcome
This attribute informs the operator about the outcome of the current test phase. It is contained in the "Test Report" and can be queried by the user during the test via a "GET".
INCONCLUSIVE indicates that no "Pass" or " Fail" outcome has been determinated yet.
PASSED and FAIL are possible for all phases of the test. Further information (e.g. about
the number of the failed test phase) is only available in the test report which is sent at
the end of the test.
PASSED generally indicates that the test was executed correctly and no problems were
found.
FAILED generally indicates that the test was executed correctly and a problem was
found.
Validity Range
INCONCLUSIVE
PASSED
FAILED
Default Value
None.
730
Id:0900d80580592ba0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Contained in the following commands:
GET BTSETEST
TESTPWRRED
testPowerReduction
This attribute defines the output power reduction if the transceiver test mode is activated. Its value is adapted to the static power reduction range.
The default value means that the testPowerReduction is not set and as a consequence
the test mode can not be enabled.
Validity Range
<ANY>
Default Value
None.
Contained in the following commands:
GET TRX
TESTST
testState
This attribute defines the current state of the test.
Validity Range
IDLE
INITIALIZING
TESTING
TERMINATING
Default Value
None.
Contained in the following commands:
GET BTSETEST
TIMEDELAY
timeDelay(sec)
This parameter is sent in the 'Activate SW Delayed' command by the BSC. It identifies
the number of seconds that the BTSE waits before activating the specified SW version.
Validity Range
0 - 254
A50016-G5100-B333-04-7619
Id:0900d80580592ba0
731
BS-4x / 82 II / 240 / 241 / 240XL commands
Default Value
None.
Contained in the following commands:
ACTIVATE_DELAYED BTSM
TNCH
tNCH(*multiframes)
This attribute describes the minimum repetition period for the Notification/NCH messages. The NCH blocks are a subset of the CCCH blocks reserved for AGCH.
The attribute doesn't denote the minimum repetition period within one CCCH block.
Within a CCCH block 1 ... 7 NCH blocks can be used.
(the attribute is indicated in units of multiframes)
Validity Range
1 - 254
Default Value
16
Contained in the following commands:
GET BTS TIMER
TNFTARGF
tnfTargetFrequency
This attribute defines the target frequency the TNF is to be tuned. It is
set internally by the BTSE after creation, frequency update or deletion
of any functional-related TRX instance and is read-only for any
external interface of the BTSE.
In case of "FTNFP" the attribute shows the "actual frequency" of the
TNF: this means that the value of the attribute changes during the
"tuning" of the TNF or during the "parking" of the TNF.
732
cellAllocationNumber
Hex
Decimal
GSM900 "BB900"
0001 ... 007C
1 ... 124
GSM EXTENDED
"F2ONLY900"
0000 ... 007C
0 ... 124
03CF ... 03FF
975 ... 1023
GSM EXTENDED
REDUCED
"EXT900"
0000
0000
0000 ... 007C
0 ... 124
03CF ... 03FF
975 ... 1023
Id:0900d80580592ba0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
DCS 1800
"DCS1800"
0200 ... 0375
512 ... 885
PCS 1900
0200 ... 032A
512 ... 810
GSM-R
not supported
not supported
ANY (only Parking
position)
FF00
65280
Validity Range
0 - 65535
<NULL>
Default Value
None.
Contained in the following commands:
GET F6TNFP, GET FTNFP
TRXAREA
trxArea
This attribute specifies whether a TRX belongs to a concentric cell and to which area it
belongs.
The attribute also indicates whether the concentric cell intracell handover algorithm is
enable (value 01 or 02) or disabled (value 00). If it is enabled it will be executed before
the conventional inter/intracell handover algorithms.
Validity Range
NONE
INNER
COMPLETE
Default Value
NONE - TRX doesn't belong to a concentric cell
Contained in the following commands:
GET TRX
TRXCPBL
trxCapability
This attribute reflects the real capabilities of a TRX after harware has been assigned to
it. It is set after the TRX allocation by the BTSE. If the TRX object is created in advance
or hardware is not allocated to the TRX the attribute has the value unknown. It is readonly from the Abis/LMT point of view (GET TRX). The BSC has to perform a GET on this
attribute each time the TRX performs a transition to "enabled".
A50016-G5100-B333-04-7619
Id:0900d80580592ba0
733
BS-4x / 82 II / 240 / 241 / 240XL commands
Validity Range
UNKNOWN
GSM
EDGE
Default Value
UNKNOWN
Contained in the following commands:
GET TRX
TRXFREQ
carrierFrequency
This attribute defines the radio frequency allocated and available to a
cell.
cellAllocationNumber
Decimal
GSM900 "BB900"
1 ... 124
GSM EXTENDED
"F2ONLY900"
0 ... 124
GSM-R
955 ... 974
GSM EXTENDED
REDUCED
"EXT900"
0 ... 124
DCS 1800
"DCS1800"
512 ... 885
PCS 1900
512 ... 810
GSM-DCS
0 ... 124
975 ... 1023
975 ... 1023
975 ... 1023
512 ... 885
GSM850
128 ... 251
GSM850-PCS
128 ... 251
512 ... 810
GSM850-DCS
128 ... 251
512 ... 885
Validity Range
0 to 64 items of
734
Id:0900d80580592ba0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
0 - 1023
Default Value
None.
Contained in the following commands:
GET TRX
TRXMD
trxMode
This attribute defines the mode of a TRX that required from the operator. Depending on
it's value the BTSE tries to allocate an appropriate hardware to the TRX object.
Validity Range
GSM
EDGE
Default Value
GSM
Contained in the following commands:
GET TRX
TSC
trainingSequenceCode
This attribute contains the Training Sequence Code (TSC) of a radio
channel. If the TSC value is set NULL, TSC is always equal to the
BCC (Base Transceiver Station Colour Code) for both control and
traffic channels.
Notes:
1.
A NULL (FF) value is possible for both control and traffic
channels and signifies that the BCC (BS colour code of attribute "bsIdentityCode / BSIC") shall be used as the TSC value
for the channel.
2.
In case of a control channel only the NULL (FF) value can be
specified, i.e. only a reference to the BCC is allowed.
Validity Range
TSC_00
TSC_01
TSC_02
TSC_03
A50016-G5100-B333-04-7619
Id:0900d80580592ba0
735
BS-4x / 82 II / 240 / 241 / 240XL commands
TSC_04
TSC_05
TSC_06
TSC_07
TSC_is_BCC_of_BSIC
Default Value
None.
Contained in the following commands:
GET CHAN
TSLPOOL
tslPool
This attribute defines the pool of Abis timeslots (TSL) on a granularity
of 16Kbit/s subslots (SSL) which can be used for traffic within a
BTSE.
The attribute contains an entry of 17 bytes for each used BPort:
-
the first byte indicates the number of the BPort (BPortNumber),
the following 16 bytes (BPortBitmap) contain a bitmap - the
subslots which can be used for traffic are indicated by setting
the corresponding bits in the BPortBitmap bytes to 1. In case
of PCM24 the TSL 0 and TSL 25-31 don't exist, therefore the
related bits are set to 0.
Out of this pool the BSC assigns dynamically the Abis timeslots to a
call. The information about the actual timeslot/subslot ("Abis
Resources") is sent by the BSC to the BTSE on the radio signalling
link at the begin of each call ("channel Activation") and during the call
("Modify Abis Channel") if a modification is necessary.
The BportNumber validity range is specified as follows:
00..07 (not only for BS82II)
00..03 (only for BS82II)
Validity Range
1 to 8 items of
BPortNumber
BPORT0
BPORT1
...
BPORT7
BPortBitMap
736
16 to 16 items of
Id:0900d80580592ba0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
B#0 - B#11111111
Default Value
None.
Contained in the following commands:
GET BTSM NOSWL
TSYNC
tSync(*10ms)
This attribute defines the timer value, that will be used by the BTS to supervise timeout
of TRAU frame handling. This timer is used only if a BTS-TRAU traffic connection is
already established. If the BTSE detects a loss of frame synchronisation it starts the
timer tSync. It is cleared, if a frame is received again. If it expired, a connection failure
indication is reported to the BSC.
A change of the attribute becomes effective after the reception of a TRAU frame i.e. in
the case after 20 ms and in the worst case after the expiration of the current timer.
(value indicated in milliseconds; step size 10 ms)
Validity Range
10 - 10000
Default Value
1000 (corresponding to 10 sec.)
Contained in the following commands:
GET BTS TIMER
TSYNCD
tSyncD(*10ms)
This attribute defines the timer value, that will be used by the BTS to supervise timeout
of downlink TRAU frame handling in case of 14.5kbit/s data connections. If loss of frame
synchronization detected by the BTS it starts a timer TsyncD and starts sending Data
TRAU Frames in the uplink direction to trigger the TRAU to start sending Data TRAU
Frames in the downlink direction to be used for downlink Synchronization Recovery.
TsyncD is reset every time frame synchronization is again obtained. If TsyncD expires
before frame synchronization is again obtained, a connection failure indication is
reported to the BSC.
(value indicated in milliseconds; step size 10 ms)
Validity Range
10 - 10000
A50016-G5100-B333-04-7619
Id:0900d80580592ba0
737
BS-4x / 82 II / 240 / 241 / 240XL commands
Default Value
1000 (corresponding to 100 sec.)
Contained in the following commands:
GET BTS TIMER
TSYNCR
tSyncR(*10ms)
This attribute defines the timer value, that will be used by the BTS to supervise the uplink
Synchronization Recovery in case of 14.5kbit/s data connections. When the BTS
receives an Extended Data TRAU Frame indicating an Uplink Frame Error and which
has no errors on the synchronization pattern and the control bits, it starts the timer
TsyncR. TsyncR is reset every time three consecutive TRAU frames are received
without Uplink Frame Error indication, without errors on the frame synchronization
pattern and on the control bits. If TsyncR expires before frame synchronization is again
obtained, the BTS starts sending Data TRAU Frames in the uplink direction to be used
for uplink Synchronization Recovery.
(value indicated in milliseconds; step size 10 ms)
Validity Range
10 - 10000
Default Value
400 (corresponding to 4 sec.)
Contained in the following commands:
GET BTS TIMER
TSYNCU
tSyncU(*10ms)
This attribute defines the timer value, that will be used by the BTS to supervise timeout
of uplink TRAU frame handling in case of 14.5kbit/s data connections. When the BTS
receives an Extended Data TRAU Frame indicating an Uplink Frame Error and which
has no errors on the synchronization pattern and the control bits, it starts a timer
TsyncU. TsyncU is reset every time three consecutive TRAU frames are received
without Uplink Frame Error indication, without errors on the frame synchronization
pattern and on the control bits. If TsyncU expires before frame synchronization is again
obtained, a connection failure indication is reported to the BSC.
(value indicated in milliseconds; step size 10 ms)
Validity Range
10 - 10000
738
Id:0900d80580592ba0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Default Value
1000 (corresponding to 10 sec.)
Contained in the following commands:
GET BTS TIMER
TTRAU
tTrau(*10ms)
This attribute defines the timer value, that will be used by the BTS to supervise timeout
of TRAU datalink (traffic) at connection establishment or handover. It is set with sending
the first TRAU dataframe uplink and cleared, when the first frame downlink arrives. If it
is expires, a connection failure indication is reported to the BSC.
(value indicated in milliseconds; step size 10 ms)
Validity Range
10 - 10000
Default Value
1000 (corresponding to 10 sec.)
Contained in the following commands:
GET BTS TIMER
TUPLREP
timerUplinkReply
The attribute defines the timer for the repetition of the UplinkFree message with "reply
on uplink access request".
Validity Range
5 - 60
Default Value
20 seconds
Contained in the following commands:
GET BTS TIMER
TXBMAXF
txBandMaxFreq(kHz*100)
Attribute data provided by the TMA.
Validity Range
0 - 65535
A50016-G5100-B333-04-7619
Id:0900d80580592ba0
739
BS-4x / 82 II / 240 / 241 / 240XL commands
<NULL>
Default Value
None.
Contained in the following commands:
GET TMA
TXBMINF
txBandMinFreq(kHz*100)
Attribute data provided by the TMA.
Validity Range
0 - 65535
<NULL>
Default Value
None.
Contained in the following commands:
GET TMA
TXDIVTSEXCPT
txDivTimeShiftExcept
The TX Diversity Time Shift operation might be disabled for certain type of TX burst,
which are timing-sensitive (e.g. SCH channel for location services). In this case the
parallel transmission of the slave CU is disabled when the certain burst type is going to
be transmitted. The attribute txDivTimeShiftExcept allows to configure time slots or
logical channels, which shall be excluded from applying the Tx Diversity Time Shift. The
call processing software supervises bursts to be transmitted and disables the slave
transmission if the burst should not be transmitted. The attribute is only valid if the
feature Tx Diversity Time Shift is enabled (attribute enableTxDivTimeShift). A change of
the attribute value causes a traffic interruption on all TRX of the BTS and a restart of the
feature Tx Diversity Time Shift.
Validity Range
NONE
SCH
BCCHTRXTS0
BCCHTRX
Default Value
NONE (diversity applied for all channel)
740
Id:0900d80580592ba0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Contained in the following commands:
GET BTS TIMER
TXDIVTSPAR
txDivTimeShiftParam
The attribute txDivTimeShiftParam is used to set the time shift between the transmit
signals of the master and the slave CU. The time shift is specified on a symbol base in
the range between -5 .... +5 symbols in steps of 0,25 symbols. A symbol represents one
information unit (e.g. 1 bit) is transmitted within 3,693 s. The attribute is only valid if the
feature Tx Diversity Time Shift is enabled (attribute enableTxDivTimeShift). A change of
the attribute value causes a traffic interruption on all TRX of the BTS and a restart of the
feature Tx Diversity Time Shift.
Validity Range
-5.00 - 5.00
Default Value
-1 symbol, but has to be evaluated during field tests
Contained in the following commands:
GET BTS TIMER
TXLEVADJ
txLevAdjust(dB)
The attribute specifies the value needed to adjust the TXLEV value of
the transmit path of the CU/FCUTR. For a FCUTR with an even object
instance the related transmit path is TX0, for a FCUTR with an odd
object instance the related transmit path is TX1.
The attribute value which will be used to compensate attenuation
effects caused by combiner equipment, RF cabling and amplification
effects of optionally used booster equipment. The operator has to set
a reasonable value according the following formula:
txLevAdjust =
Attention Factor of used Combiner + Attention
Factor of RF Cable - Amplification Factor of used
Booster
Validity Range
-63.0 - 63.0
Default Value
0.0
Contained in the following commands:
CREATE CU, CREATE FCUTR, GET CU, GET FCUTR, SET CU, SET FCUTR
A50016-G5100-B333-04-7619
Id:0900d80580592ba0
741
BS-4x / 82 II / 240 / 241 / 240XL commands
TXSIGLEVADJ
txSigLevAdjust
The attribute specifies the signal level adjust values which shall be applied to the
transmit paths oftransceivers using the same frequency band as the BCCH transceiver.
Validity Range
<ANY>
Default Value
None.
Contained in the following commands:
GET BTS TIMER
TXSIGLEVADJC
txSigLevAdjustCompl
The attribute specifies the signal level adjust values which shall be applied to the
transmit paths oftransceivers using the complementary frequency band. The value is
only meaningful in case of a multiband cell.
Validity Range
<ANY>
Default Value
None.
Contained in the following commands:
GET BTS TIMER
TYPOFETH
typeOfEthernet
The attribute defines the type of Ethernet framing which is used for transmitted packets.
Validity Range
ethernet_II
iEEE802_SNAP
Default Value
ethernet_II
Contained in the following commands:
GET COBAETHINTF, SET COBAETHINTF
742
Id:0900d80580592ba0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
TYPRACK
typeOfBtse
This attribute identifies the type of BTSE.
This attribute defines the type of the rack.
For the BTSE family given by 'hh=04' it is possible to set the value of typeOfBTSE for
rack #0 only once - if the operator wants to change the stored value he has to format the
FLASH EPROM first or delete the Flash-DB.
For an rack instance number <> 0 an update of the attribute is blocked by the BTSE SW.
This means if an operator wants to change the attribute value in a rack <> 0 he has to
delete the rack first and then recreate it with the new value of typeOfBTSE.
Below are reported more detailed information about the validity range:
BS20 (value only possible for rack #0)
BS21E (value only possible for rack #0)
BS22 (value only possible for rack #0)
BS60 (value only possible for rack #0)
BS61E (value only possible for rack #0)
not_valid (value possible only in LMT phase 2 as result of a
GET command for rack #0)
Validity Range
In commands CREATE RACK, SET RACK:
BS240
BS241
BS240SR
BS241SR
BS40
BS40II
BS41
BS240XL
BS240XLSR
BS82II
In commands GET RACK:
BS240
BS241
BS240SR
BS241SR
BS40
BS41
BS240XL
A50016-G5100-B333-04-7619
Id:0900d80580592ba0
743
BS-4x / 82 II / 240 / 241 / 240XL commands
BS240XLSR
BS240XS
BS240SWB
BS241SWB
BS240XLSWB
BS82II
BS40II
not_valid
Default Value
None.
Contained in the following commands:
CREATE RACK, GET RACK, SET RACK
744
Id:0900d80580592ba0
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
v
VENDNA
vendorName
This attribute type identifies the vendor of the associated Object. This attribute is defined
as an "ASCII String" and is not terminated by a NULL character.
Validity Range
1..37 characters string
Default Value
None.
Contained in the following commands:
GET BTSEP NOSWL, SET BTSEP
VGSCULFT
voiceGroupUplinkFree(*10ms)
If the uplink of the group call is free, and also no talker is in the cell on
a dedicated channel, the network provides an UPLINK FREE
message on the main signalling channel periodically. The timer
vgscULFreeTimer plus an offset of 440ms defines the repetition rate
of sending this message; the BTS limits the maximum repetition rate
on 1440ms.
The BTSE stops the timer when the uplink is free again, and also no
talker is in the cell on a dedicated channel.
Setting this attribute to the lowest possible value means that a talker
request by a mobile station can be started with most minimal delay.
On the other side, a high repetition rate of UPLINK FREE messages
leads to a certain speech frame erasure rate, which may cause an
audible degradation of the speech quality on the group downlink
channel; although there is no talker in the group call at this state, there
may be dispatchers speaking on the group downlink channel.
vgcsULFreeTimer
value (decimal)
vgcsULFreeTimer
UPLINK FREE
* 10 ms
repetition rate
10 ms
450 ms
20 ms
460 ms
30 ms
470 ms
100
100 ms
1440 ms
A50016-G5100-B333-04-7619
Id:0900d80580592ba2
745
BS-4x / 82 II / 240 / 241 / 240XL commands
Default Value: 10 ms
Validity Range
1 - 100
Default Value
10 ms
Contained in the following commands:
GET BTS TIMER
VLANID
vlanId
This attribute defines optional virtual LAN (VLAN) identifier. The vlanId is used by all
pseudo wires (CESPW) of the CESTUNNEL instance.
If vlanId is set to none the VLAN tag in the Ethernet Header will be omitted. The object
must be locked before modifying the vlanId via the SET command.
Validity Range
In commands CREATE CESTUNNEL, CREATE CESTUNNEL, SET CESTUNNEL:
0 - 4094
<NULL>
In commands GET CESTUNNEL:
<ANY>
Meaning:
1..4094 :Tagged frame mode: IEEE 802.1q
TX: All frames contain vlan tags with value of attribute vlanId and priority tags;
default priority is 7 if no other value is configured with BTSE attribute serviceClassPrioList.
RX: Only tagged frames with vlanId=attribute value are accepted; untagged frames
(no vlan tag and no priority tag) are discarded
0: Tagged frame mode: IEEE 802.1p
TX:all frames contain vlan tags with vlanId=0 and priority tags with default value=7
if no other value is configured with BTSE attribute serviceClassPrioList.
RX: frames with priority tag + vlan tag =0 must be accepted, untagged frames with
no vlan tag and no priority tag should be also accepted; all others are discarded
None: Untagged frame mode:
TX:all frames are untagged (no vlan tag and no priority tag)
RX:untagged frames with no vlan tag and no priority tag must be accepted, frames
with priority tag + vlan tag=0 should be also accepted; all others are discarded
Default Value
In moc(s) CESTUNNEL:
None.
746
Id:0900d80580592ba2
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
In moc(s) CESTUNNEL:
NULL
Contained in the following commands:
CREATE CESTUNNEL, GET CESTUNNEL, SET CESTUNNEL
VSWRTDB
vswrThresholdDb
The value sets the TX return loss threshold value of an MFDUAMCO antenna branch.
The value will be aligned with the combiner if a MFDUAMCO is equipped.
The value will be aligned with the combiner if a FICOM6 is equipped.
The object is set to degraded if the low threshold is crossed. Crossing the high threshold
leads to disabled state.
The attribute is meaningless if an old DUAMCO or FDUAMCO is equipped. Nevertheless the value will be stored in the database and used if an MFDUAMCO will be
equipped later on.
Validity Range
LOW_2_0_HIGH_3_0
LOW_2_5_HIGH_3_5
LOW_3_0_HIGH_4_0
Default Value
LOW_2_0_HIGH_3_0
Contained in the following commands:
CREATE DUVSWR, CREATE F6VSWRP, GET DUVSWR, GET F6VSWRP, SET
DUVSWR, SET F6VSWRP
A50016-G5100-B333-04-7619
Id:0900d80580592ba2
747
BS-4x / 82 II / 240 / 241 / 240XL commands
w
WDDUVSWR
wiringDuamcoVswr
This attribute represents the wiring between a DUAMCO_VSWR and several CUs (TX
output)/FCUMAINs (TX0 output or TX1 output) which the operator has to perform at
installation time.
In case of FCUMAIN with fcuMode=singleCUMode or in case of CU, the
DUAMCO_VSWR and the CUs/FCUMAINs are in the same rack and belong to the
same cell.
In case of FCUMAIN with fcuMode=douleCUMode, the objects can belong to two different cells.
Due to the physical properties of the DUAMCO_VSWR, up to 4 CUs/FCUMAINs can be
connected."
From SW point of view the FDUAMCO is considered just as an HW variant of the
DUAMCO, so an extra term like 'FDUAMCO_DUVSWR' is not introduced.
The BTSE SW doesn't check if the entered value is compatible with typeOfBTSE; e.g.
an input of CU7 isn't rejected in a BS40 although BS40 allows only the creation of CU
0-3.
Notes:
- All CUs/FCUMAINs which are listed in a GET DUVSWR for WDDUVSWR have to be
locked before the cabling of one of these CUs/FCUMAINs can be removed from WDDUVSWR.
- The UIDL construct used is enumList.
Below are reported some detailed information about validity range values:
CU0 ... CU11 (CU4 ... CU7 only for BS240 and BS241)
(CU4 ... CU11 only for BS240XL)
FCUMAIN0TX0
FCUMAIN0TX1
:
FCUMAIN11TX0
FCUMAIN11TX1
(FCUMAIN4TX0 ... FCUMAIN7TX1 only for BS240
and BS241)
:
(FCUMAIN4TX0 ... FCUMAIN11TX1 only for
BS240XL)
Validity Range
1 to 4 items of
748
Id:0900d8058024e40a
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
CU0
CU1
CU2
CU3
CU4
CU5
CU6
CU7
CU8
CU9
CU10
CU11
FCUMAIN0TX0
FCUMAIN0TX1
FCUMAIN1TX0
FCUMAIN1TX1
FCUMAIN2TX0
FCUMAIN2TX1
FCUMAIN3TX0
FCUMAIN3TX1
FCUMAIN4TX0
FCUMAIN4TX1
FCUMAIN5TX0
FCUMAIN5TX1
FCUMAIN6TX0
FCUMAIN6TX1
FCUMAIN7TX0
FCUMAIN7TX1
FCUMAIN8TX0
FCUMAIN8TX1
FCUMAIN9TX0
FCUMAIN9TX1
FCUMAIN10TX0
FCUMAIN10TX1
FCUMAIN11TX0
FCUMAIN11TX1
A50016-G5100-B333-04-7619
Id:0900d8058024e40a
749
BS-4x / 82 II / 240 / 241 / 240XL commands
Default Value
None.
Contained in the following commands:
CREATE DUVSWR, GET DUVSWR, SET DUVSWR
WDFTNFP
wiringDataFtnfp
This attribute defines the pool of Abis timeslots (TSL) on a granularity
of 16Kbit/s subslots (SSL) which can be used for traffic within a
BTSE.
This attribute represents the wiring:
-
between the TX input of a FICOM_TNFP and the TX output of
a CU
between the TX input of a FICOM_TNFP and the TX0 or TX1
output of a FCUMAIN
and furtheron it describes to which FICOM_VSWR the
FICOM_TNFP is related to. The wiring has to be done by the
operator at installation time.
In case of FCUMAIN with fcuMode=singleCUMode or in case of CU,
the FICOM_TNFP, the CU/FCUMAIN and the FICOM_VSWRP are
in the same rack and belong to the same cell.
In case of FCUMAIN with fcuMode=douleCUMode, the objects can
belong to two different cells.
The BTSE SW doesn't check if the entered value is compatible with
typeOfBTSE; e.g. an input of CU7 isn't rejected in a BS40 although
BS40 allows only the creation of CU 0-3.
Note: 'CU_wiring' is used for CU as well as for FCUMAIN, the name
'CU_wiring' has not been changed because it is used in LMTGUI/CLI.
The following values are possible for 'CU_wiring':
CU0 ... CU11 (CU4 ... CU7 only for BS240 and BS241)
(CU4 ... CU11 only for BS240XL)
FCUMAIN0TX0
FCUMAIN0TX1
:
FCUMAIN11TX0
FCUMAIN11TX1
(FCUMAIN4TX0 ... FCUMAIN7TX1 only for BS240
and BS241)
:
750
Id:0900d8058024e40a
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
(FCUMAIN4TX0 ... FCUMAIN11TX1 only for
BS240XL)
The following values are possible for 'FVSWRP wiring':
FVSWRP0
FVSWRP1
FVSWRP2
FVSWRP3
Validity Range
CUWiring
CU0
CU1
CU2
CU3
CU4
CU5
CU6
CU7
CU8
CU9
CU10
CU11
FCUMAIN0TX0
FCUMAIN0TX1
FCUMAIN1TX0
FCUMAIN1TX1
FCUMAIN2TX0
FCUMAIN2TX1
FCUMAIN3TX0
FCUMAIN3TX1
FCUMAIN4TX0
FCUMAIN4TX1
FCUMAIN5TX0
FCUMAIN5TX1
FCUMAIN6TX0
FCUMAIN6TX1
FCUMAIN7TX0
FCUMAIN7TX1
A50016-G5100-B333-04-7619
Id:0900d8058024e40a
751
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUMAIN8TX0
FCUMAIN8TX1
FCUMAIN9TX0
FCUMAIN9TX1
FCUMAIN10TX0
FCUMAIN10TX1
FCUMAIN11TX0
FCUMAIN11TX1
FVSWRPWiring
FVSWRP0
FVSWRP1
...
FVSWRP3
Default Value
None.
Contained in the following commands:
CREATE F6TNFP, CREATE FTNFP, GET F6TNFP, GET FTNFP
WDLNA
wiringDataLna
This attribute represents the wiring between a DUAMCO_LNA or a DIAMCO_LNA and
several CUs/FCUMAINs the operator has to perform at installation time and that is not
foreseen to be fixed by the configuration rules.
In case of FCUMAIN with fcuMode=singleCUMode or in case of CU, the
DUAMCO/DIAMCO_LNA and the CUs/FCUMAINs are in the same rack and belong to
the same cell.
In case of FCUMAIN with fcuMode=douleCUMode, the objects can belong to two different cells.
When a second cell number is indicated (see attribute secondCellNumber), also in case
of CU the objects can belong to two different cells.
Due to the physical properties of the DUAMCO_VSWR, up to 8 different Us/FCUMAINs
can be connected. Each CU has a 'normal path' RX input and a 'diversity path' RX input
and the operator must indicate which of them is wired to the DUAMCO/DIAMCO_LNA.
The FCUMAIN supports the 'normal path' RX input, the diversity path RX input and two
further Rx inputs: Rx C / N1 and Rx D / D1.
The BTSE SW doesn't check if the entered value is compatible with typeOfBTSE; e.g.
an input of CU7N / CU7D isn't rejected in a BS40 although BS40 allows only the creation
of CU 0-3.
Validity Range (object DILNA/DULNA) are possible for 'RX_wiring n':
CU0N (CU0 normal path)
CU0D (CU0 diversity path)
752
Id:0900d8058024e40a
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
:
CU11N (CU11 normal path)
CU11D (CU11 diversity path)
FCUMAIN0N (FCUMAIN0 normal path)
FCUMAIN0D (FCUMAIN0 diversity path)
FCUMAIN0N1 (FCUMAIN0 Rx C / N1 path)
FCUMAIN0D1 (FCUMAIN0 Rx D / D1 path)
:
FCUMAIN11N (FCUMAIN11 normal path)
FCUMAIN011D (FCUMAIN11 diversity path)
FCUMAIN11N1 (FCUMAIN11 Rx C / N1 path)
FCUMAIN11D1 (FCUMAIN011 Rx D / D1 path)
(CU4 ... CU7 only for BS240 and BS241)
(CU4 ... CU11 only for BS240XL)
(FCUMAIN4N ... FCUMAIN7D1 only for BS240 and BS241)
(FCUMAIN4N ... FCUMAIN11D1 only for BS240XL)
Validity Range
1 to 8 items of
CU0N
CU0D
CU1N
CU1D
CU2N
CU2D
CU3N
CU3D
CU4N
CU4D
CU5N
CU5D
CU6N
CU6D
CU7N
CU7D
CU8N
CU8D
CU9N
A50016-G5100-B333-04-7619
Id:0900d8058024e40a
753
BS-4x / 82 II / 240 / 241 / 240XL commands
CU9D
CU10N
CU10D
CU11N
CU11D
FCUMAIN0N
FCUMAIN0D
FCUMAIN0N1
FCUMAIN0D1
FCUMAIN1N
FCUMAIN1D
FCUMAIN1N1
FCUMAIN1D1
FCUMAIN2N
FCUMAIN2D
FCUMAIN2N1
FCUMAIN2D1
FCUMAIN3N
FCUMAIN3D
FCUMAIN3N1
FCUMAIN3D1
FCUMAIN4N
FCUMAIN4D
FCUMAIN4N1
FCUMAIN4D1
FCUMAIN5N
FCUMAIN5D
FCUMAIN5N1
FCUMAIN5D1
FCUMAIN6N
FCUMAIN6D
FCUMAIN6N1
FCUMAIN6D1
FCUMAIN7N
FCUMAIN7D
FCUMAIN7N1
754
Id:0900d8058024e40a
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
FCUMAIN7D1
FCUMAIN8N
FCUMAIN8D
FCUMAIN8N1
FCUMAIN8D1
FCUMAIN9N
FCUMAIN9D
FCUMAIN9N1
FCUMAIN9D1
FCUMAIN10N
FCUMAIN10D
FCUMAIN10N1
FCUMAIN10D1
FCUMAIN11N
FCUMAIN11D
FCUMAIN11N1
FCUMAIN11D1
Default Value
None.
Contained in the following commands:
CREATE DILNA, CREATE DULNA, CREATE F6LNA, GET DILNA, GET DULNA,
GET F6LNA, SET DILNA, SET DULNA, SET F6LNA
A50016-G5100-B333-04-7619
Id:0900d8058024e40a
755
Nack causes
BS-4x / 82 II / 240 / 241 / 240XL commands
4 Nack causes
String table for ABIS nack causes used by the LMT Evolution
756
H'1,
Incorrect message structure
H'2,
Invalid message type value
H'3,
<reserved>
H'4,
<reserved>
H'5,
Invalid object class value
H'6,
Object class not supported
H'7,
BTS no. unknown
H'8,
Transceiver no. unknown
H'9,
Object instance unknown
H'A,
<reserved>
H'B,
<reserved>
H'C,
Invalid attribute identifier value
H'D,
Attribute identifier not supported
H'E,
Parameter value outside permitted range
H'F,
Inconsistency in attribute list
H'10,
Specified implementation not supported
H'11,
Message cannot be performed
H'12,
Busy
H'13,
<reserved>
H'14,
<reserved>
H'15,
<reserved>
H'16,
<reserved>
H'17,
<reserved>
H'18,
<reserved>
H'19,
Resource not implemented
H'1A,
Resource not available
H'1B,
Frequency not available
H'1C,
Test not supported
H'1D,
Capacity restrictions
H'1E,
Physical configuration cannot be performed
H'1F,
Test not initiated
H'20,
Physical configuration cannot be restored
H'21,
No such test
H'22,
Test cannot be stopped
Id:0900d805805bfe1b
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Nack causes
H'23,
Message inconsistent with physical config.
H'24,
File already received
H'25,
Complete file not received
H'26,
File not available at destination
H'27,
File cannot be activated
H'28,
Request not granted
H'29,
Wait
H'2A,
<reserved>
H'7F,
<reserved>
H'80,
BTSE not able to begin DB Transmission
H'81,
DB Transmission failed
H'82,
Conflicting channel assignment
H'83,
Specified connection does not exist
H'84,
Specified Test is not running
H'85,
swLoad-header not stored
H'86,
swLoad-header mismatch with swImage or VAM file id
H'87,
Files listed in swLoad header not stored
H'88,
Request already in progress
H'89,
Load has not been activated before
H'8A,
Starting Time already in use
H'8B,
Configuration of specified object not allowed during alignment
H'8C,
Update of specified object not allowed in LMT Evolution phase 3
H8D,
Configuration of specified object not allowed during FW download
H'90,
invalid file name
H'91,
invalid file type
H'92,
file not found
H'93,
file in use
H'94,
file present
H'95,
file corrupted
H'96,
file test failed
H'97,
MO or MOT not locked
H'98,
VAM check failed
H'99,
VAM file not stored in Flash Eprom
H'9A,
Scanner is suspended
H'9B,
TEI already in use
H'9C,
Update not allowed from Abis interface
A50016-G5100-B333-04-7619
Id:0900d805805bfe1b
757
Nack causes
BS-4x / 82 II / 240 / 241 / 240XL commands
H'9D,
Update not allowed from T interface
H'9E,
Update not allowed
H'9F,
MO already created
H'A0,
requested information exceeds maximal message length
H'A1,
sw load not compatible with typeOfBTSE
H'A2,
Creation out of sequence
H'A3,
Invalid attribute value
H'A4,
Conflicting timeslot assignment
H'A5,
Deletion not possible in Phase3
H'A6,
Deletion out of sequence
H'A7,
Related BPort instance not created
H'A8,
Configuration of remapped timeslots not possible in Phase3
H'A9,
feature not released
H'AA,
typeOfBTSE has to be set first
H'AB,
typeOfBTSE not compatible with typeOfBTSE in other rack(s)
H'AC,
max number of object instances is already created
H'AD,
no redundant core board available
HAE,
TRX/LPDM related LADPLE doesnt exist or isnt consistent
HAF,
Requested data not available
HB0,
Conflicting feature activation
HB1,
Re-synchronization not possible
HB2,
Inconsistency in wiring configuration
HB3,
No FPGA on board
HB4-F3,
Not used
H'F4,
Change password failed: syntax error
H'F5,
Change password failed: new pwd is the same as old pwd
HF6-F7,
Not used
H'F8,
Mandatory security attribute missing
H'F9,
Security transmission failed
H'FA,
Security transmission missing
H'FB-FE,
Not used
H'FF,
NULL
String table for LMT Evolution nack causes used by BTSE
758
H'01,
Incorrect message structure
H'02,
Invalid message type value
H'03,
<reserved>
Id:0900d805805bfe1b
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Nack causes
H'04,
<reserved>
H'05,
Invalid object class value
H'06,
Object class not supported
H'07,
BTS no. unknown
H08,
Transceiver no. unknown
H09,
Object instance unknown
H0A,
<reserved>
H0B,
<reserved>
H'0C,
Invalid attribute identifier value
H0D,
Attribute identifier not supported
H0E,
Parameter value outside permitted range
H0F,
Inconsistency in attribute list
H10,
Specified implementation not supported
H'11,
Message cannot be performed
H'12,
System busy
H13,
<reserved>
H14,
<reserved>
H15,
<reserved>
H16,
<reserved>
H17,
<reserved>
H18,
<reserved>
A50016-G5100-B333-04-7619
Id:0900d805805bfe1b
759
Appendix: values for ERFACCHALPDMF, ERFACCHCMDF, ERSACCHDL, ERSACCHUL and ETOP
BS-4x / 82 II / 240 / 241 / 240XL commands
5 Appendix: values for ERFACCHALPDMF,
ERFACCHCMDF, ERSACCHDL, ERSACCHUL and ETOP
Assigned Values
Binary
Dec
Hex
TCH_WFS TCH_HS TCH_FS TCH_EFS TCH_AHS TCH_AFS
0
00
0x00
01
0x01
02
0x02
03
0x03
04
0x04
05
0x05
06
0x06
07
0x07
08
0x08
09
0x09
10
0x0A
11
0x0B
12
0x0C
13
0x0D
14
0x0E
15
0x0F
16
0x10
17
0x11
18
0x12
19
0x13
20
0x14
21
0x15
22
0x16
23
0x17
24
0x18
25
0x19
26
0x1A
27
0x1B
28
0x1C
760
Id:0900d80580248212
A50016-G5100-B333-04-7619
BS-4x / 82 II / 240 / 241 / 240XL commands
Appendix: values for ERFACCHALPDMF, ERFACCHCMDF, ERSACCHDL, ERSACCHUL and ETOP
29
0x1D
30
0x1E
31
0x1F
32
0x20
33
0x21
34
0x22
35
0x23
36
0x24
37
0x25
38
0x26
39
0x27
40
0x28
41
0x29
42
0x2A
43
0x2B
44
0x2C
45
0x2D
46
0x2E
47
0x2F
48
0x30
49
0x31
50
0x32
51
0x33
52
0x34
53
0x35
54
0x36
55
0x37
56
0x38
57
0x39
58
0x3A
59
0x3B
60
0x3C
61
0x3D
62
0x3E
63
0x3F
g ERFACCHALPDMF:
A50016-G5100-B333-04-7619
Id:0900d80580248212
761
Appendix: values for ERFACCHALPDMF, ERFACCHCMDF, ERSACCHDL, ERSACCHUL and ETOP
BS-4x / 82 II / 240 / 241 / 240XL commands
For the binary representation 0 means that R-FACCH for any LAPDm command or
response frames is not applied for specified speech codec type and 1 means that RFACCH for any LAPDm 5 command or response frames is applied for specified
speech codec type.Value 0x00 has specific meaning and should be read as RFACCH for any LAPDm command or response frames is not applied for any speech
codec type. All other values are reserved for the future use.
ERFACCHCMDF: For the binary representation 0 means that R-FACCH on LAPDm
command frames is not applied for specified speech codec type and 1means that RFACCH on LAPDm command frames is applied for apecified speech codec type.
Value 0x00 has specific meaning and should be read as R-FACCH on LAPDm
command frames is not applied for any speech codec type. All other values are
reserved for the future use.
ETOP:
For the binary representation 0 means that TOP is not applied for specified speech
codec type and 1 means that TOP is applied for specified speech codec type.Value
0x00 has specific meaning and should be read as TOP is not applied for any speech
codec type. All other values are reserved for the future use.
762
Id:0900d80580248212
A50016-G5100-B333-04-7619
You might also like
- ATV340 Ethernet Embedded Manual NVE61653 03No ratings yetATV340 Ethernet Embedded Manual NVE61653 03156 pages
- ProCash DDC V1400 ProConsult DDC V1200 UserGuide en100% (2)ProCash DDC V1400 ProConsult DDC V1200 UserGuide en432 pages
- ATV900 Ethernet Manual Embedded NHA80940 03No ratings yetATV900 Ethernet Manual Embedded NHA80940 03148 pages
- Procash/Ndc V3.0/00 Proconsult/Ndc V3.0/00: User Guide100% (1)Procash/Ndc V3.0/00 Proconsult/Ndc V3.0/00: User Guide438 pages
- NEC Application Manager APM System Installation ManualNo ratings yetNEC Application Manager APM System Installation Manual66 pages
- ABB Drives: Protocol Manual - Ethernet/IP Ethernet Adapter Module FENA-01No ratings yetABB Drives: Protocol Manual - Ethernet/IP Ethernet Adapter Module FENA-01116 pages
- Altivar Process 900 Ethernet Manual en NHA80940 01No ratings yetAltivar Process 900 Ethernet Manual en NHA80940 01156 pages
- ACS850 ACQ810 Appl Programming Appl Guide B PDFNo ratings yetACS850 ACQ810 Appl Programming Appl Guide B PDF100 pages
- M29W640FT M29W640FB: 64 Mbit (8Mb x8 or 4Mb x16, Page, Boot Block) 3V Supply Flash MemoryNo ratings yetM29W640FT M29W640FB: 64 Mbit (8Mb x8 or 4Mb x16, Page, Boot Block) 3V Supply Flash Memory73 pages
- ProCash NDC V1400 ProConsult NDC V1200 UserGuide en100% (2)ProCash NDC V1400 ProConsult NDC V1200 UserGuide en398 pages
- OpenScape 4000 V7, Volume 3 - Feature Usage Examples, Service Documentation, Issue 6.No ratings yetOpenScape 4000 V7, Volume 3 - Feature Usage Examples, Service Documentation, Issue 6.2,037 pages
- Procash/Ndc V1.3/00 Proconsult/Ndc V1.1/00: User GuideNo ratings yetProcash/Ndc V1.3/00 Proconsult/Ndc V1.1/00: User Guide50 pages
- Timeprovider 1000 and 1100 Edge Clock: Tl1 Reference GuideNo ratings yetTimeprovider 1000 and 1100 Edge Clock: Tl1 Reference Guide190 pages
- ProCash NDC V2000 ProConsult NDC V2000 UserGuide en100% (1)ProCash NDC V2000 ProConsult NDC V2000 UserGuide en420 pages
- DOC00301 Verix EOS Volume I Operating System Programmers Manual Rev A.3 18sept090% (1)DOC00301 Verix EOS Volume I Operating System Programmers Manual Rev A.3 18sept09872 pages
- En ACS880 Ethernet Tool Network Guide ANo ratings yetEn ACS880 Ethernet Tool Network Guide A42 pages
- Handling System: Comau Robotics Instruction HandbookNo ratings yetHandling System: Comau Robotics Instruction Handbook54 pages
- M28W640CT M28W640CB: 64 Mbit (4Mb x16, Boot Block) 3V Supply Flash MemoryNo ratings yetM28W640CT M28W640CB: 64 Mbit (4Mb x16, Boot Block) 3V Supply Flash Memory54 pages
- Ganong Et Al - A Meta-Analytic Review of Family Structure Stereotypes - 1990No ratings yetGanong Et Al - A Meta-Analytic Review of Family Structure Stereotypes - 199012 pages
- Essentials of Anatomy and Physiology 3rd Edition Full Download100% (1)Essentials of Anatomy and Physiology 3rd Edition Full Download406 pages
- SJB Institute of Technology: Department of Information Science & EngineeringNo ratings yetSJB Institute of Technology: Department of Information Science & Engineering14 pages
- STD 10 Math Probability All Types Ques.No ratings yetSTD 10 Math Probability All Types Ques.15 pages
- Salsabeel Mahfod - Why Celebrating Black History All Year Is Critical - Blog Paragraph 1No ratings yetSalsabeel Mahfod - Why Celebrating Black History All Year Is Critical - Blog Paragraph 13 pages
- Microcontroller Based Neural Network Controlled Low Cost Autonomous VehicleNo ratings yetMicrocontroller Based Neural Network Controlled Low Cost Autonomous Vehicle4 pages
- Answer Key - Unit 3. Speaking Part 1 - Hobbies & InterestsNo ratings yetAnswer Key - Unit 3. Speaking Part 1 - Hobbies & Interests3 pages
- 8 Comparative Analysis of Tunnel Formwork and AluminiumNo ratings yet8 Comparative Analysis of Tunnel Formwork and Aluminium3 pages
- English Test 6 Grade Name: - Date: - Read The DialogueNo ratings yetEnglish Test 6 Grade Name: - Date: - Read The Dialogue6 pages
- DOUBLE-SECTION-CAR-GATE-INSTALLATION-GUIDE - Peele DoorNo ratings yetDOUBLE-SECTION-CAR-GATE-INSTALLATION-GUIDE - Peele Door44 pages