22

Tellabs 8100 Managed Access System Unit Software Version Dependencies
10004_22 19.12.08
Document Information
Revision History
Document No. 10004_22 Date 19.12.08 Description of Changes New unit software versions have been added: CXU-M SXZ288 v2.17 and v10.6 GMX GMZ544 v4.6 and v3.24 GMX2 GMZ802 v1.20 and v1.21 OMH-A OMZ675 v3.3 10004_21 25.06.08 New unit software versions have been added: ESU EMZ642 v1.12 GMH GMZ283 v10.2 GMX2 GMZ802 v1.16 and v1.18 OMH/OMH-A OMZ675 v3.2 QMH QMZ540 v10.11 10004_20 08.04.08 New unit software versions have been added: CTE-R, CTE-R/208, CTU-R and STE-10M SBZ670 v4.4 SCU-H SCZ545 v2.6 and v1.18 New product has been added: GMX2 GMZ802 v1.15 GMX2 column has been added in the product interrelations table.
2008 Tellabs. All rights reserved. This Tellabs manual is owned by Tellabs or its licensors and protected by U.S. and international copyright laws, conventions and treaties. Your right to use this manual is subject to limitations and restrictions imposed by applicable licenses and copyright laws. Unauthorized reproduction, modification, distribution, display or other use of this manual may result in criminal and civil penalties. The following trademarks and service marks are owned by Tellabs Operations, Inc. or its affiliates in the United States and/or other countries: TELLABS, TELLABS logo, TELLABS and T symbol, and T symbol. Any other company or product names may be trademarks of their respective companies. The specifications and information regarding the products in this manual are subject to change without notice. All statements, information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind, express or implied. Users must take full responsibility for their application of any products. Adobe Reader are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Contact Information: Email: fi-documentation@tellabs.com Fax: +358.9.4131.2286

2
10004_22 2008 Tellabs.
Table of Contents
Table of Contents
1 General ........................................................................................................................ 17
1.1 Interrelations ..................................................................................................................................................18
2 CAE Unit: CAZ287 Unit Software .............................................................................. 45

2.1 Version 2.3.....................................................................................................................................................45 2.2 Version 2.2.....................................................................................................................................................45 2.3 Version 2.1.....................................................................................................................................................46 2.4 Version 2.0.....................................................................................................................................................47
3 CCS-UNI and CCO-UNI Units: CCZ539 Unit Software ............................................. 48

3.1 Version 5.8.....................................................................................................................................................48 3.2 Version 5.7.....................................................................................................................................................49 3.3 Version 5.4.....................................................................................................................................................50 3.4 Version 5.2.....................................................................................................................................................51 3.5 Version 5.1.....................................................................................................................................................52 3.6 Version 5.0.....................................................................................................................................................53 3.7 Version 4.0.....................................................................................................................................................54 3.8 Version 2.0.....................................................................................................................................................54 3.9 Version 1.0.....................................................................................................................................................55
4 CCU Unit: SCZ286 Unit Software .............................................................................. 56

4.1 Version 2.7.....................................................................................................................................................56 4.2 Version 2.6.....................................................................................................................................................57 4.3 Version 2.5.....................................................................................................................................................58 4.4 Version 2.4.....................................................................................................................................................59 4.5 Version 2.2.....................................................................................................................................................59 4.6 Version 2.1.....................................................................................................................................................60 4.7 Version 2.0.....................................................................................................................................................61 4.8 Version 1.5.....................................................................................................................................................62 4.9 Version 1.4.....................................................................................................................................................63
5 CXU-M Unit: SXZ288 Unit Software........................................................................... 64
10004_22 2008 Tellabs.

3
Table of Contents
5.1 Version 10.6...................................................................................................................................................64 5.2 Version 10.5...................................................................................................................................................64 5.3 Version 10.4...................................................................................................................................................65 5.4 Version 10.3...................................................................................................................................................65 5.5 Version 10.2...................................................................................................................................................66 5.6 Version 10.1...................................................................................................................................................67 5.7 Version 10.0...................................................................................................................................................68 5.8 Version 2.17...................................................................................................................................................70 5.9 Version 2.16...................................................................................................................................................70 5.10 Version 2.15.................................................................................................................................................70 5.11 Version 2.14.................................................................................................................................................71 5.12 Version 2.13.................................................................................................................................................72 5.13 Version 2.12.................................................................................................................................................73 5.14 Version 2.10.................................................................................................................................................75 5.15 Version 2.9...................................................................................................................................................76 5.16 Version 2.8...................................................................................................................................................76 5.17 Version 2.7...................................................................................................................................................76 5.18 Version 2.6...................................................................................................................................................78 5.19 Version 2.5...................................................................................................................................................80 5.20 Version 2.4...................................................................................................................................................82 5.21 Version 2.3...................................................................................................................................................84
6 E3C Unit: GPZ641 Unit Software ............................................................................... 86

6.1 Version 1.0.....................................................................................................................................................86
7 EAE Unit: EAZ418 Unit Software............................................................................... 87

7.1 Version 1.1.....................................................................................................................................................87 7.2 Version 1.0.....................................................................................................................................................87
8 ESU Unit: EMZ642 Unit Software .............................................................................. 88

8.1 Version 1.12...................................................................................................................................................88 8.2 Version 1.11...................................................................................................................................................90 8.3 Version 1.10...................................................................................................................................................91 8.4 Version 1.9.....................................................................................................................................................92 8.5 Version 1.8.....................................................................................................................................................94 8.6 Version 1.7.....................................................................................................................................................95 8.7 Version 1.6.....................................................................................................................................................96 8.8 Version 1.5.....................................................................................................................................................96 8.9 Version 1.4.....................................................................................................................................................96 8.10 Version 1.3...................................................................................................................................................96
9 GMH Unit: GMZ283 Unit Software ............................................................................. 98

4
10004_22 2008 Tellabs.
Table of Contents
9.1 Version 10.2...................................................................................................................................................98 9.2 Version 10.1...................................................................................................................................................99 9.3 Version 10.0.................................................................................................................................................100 9.4 Version 6.10.................................................................................................................................................100 9.5 Version 6.9...................................................................................................................................................101 9.6 Version 6.7...................................................................................................................................................102 9.7 Version 6.6...................................................................................................................................................103 9.8 Version 6.5...................................................................................................................................................104 9.9 Version 6.4...................................................................................................................................................105 9.10 Version 6.3.................................................................................................................................................106 9.11 Version 6.2.................................................................................................................................................107 9.12 Version 6.1.................................................................................................................................................108 9.13 Version 5.8.................................................................................................................................................109 9.14 Version 5.7.................................................................................................................................................110 9.15 Version 5.5.................................................................................................................................................112 9.16 Version 5.2.................................................................................................................................................113 9.17 Version 5.1.................................................................................................................................................115
10 GMM Unit: GMZ438 Unit Software......................................................................... 117

10.1 Version 2.3.................................................................................................................................................117 10.2 Version 2.2.................................................................................................................................................118 10.3 Version 2.1.................................................................................................................................................119 10.4 Version 2.0.................................................................................................................................................120
11 GMU and GMU-A Units: GMZ460 Unit Software .................................................. 122

11.1 Version 1.8.................................................................................................................................................122 11.2 Version 1.179.............................................................................................................................................124 11.3 Version 1.7.................................................................................................................................................125 11.4 Version 1.6.................................................................................................................................................126 11.5 Version 1.102.............................................................................................................................................128 11.6 Version 1.5.................................................................................................................................................129 11.7 Version 1.4.................................................................................................................................................130 11.8 Version 1.3.................................................................................................................................................132 11.9 Version 1.2.................................................................................................................................................133 11.10 Version 1.1...............................................................................................................................................135
12 GMU and GMU-A Units: GMZ461 Unit Software .................................................. 138

12.1 Version 1.11...............................................................................................................................................138 12.2 Version 1.10...............................................................................................................................................139 12.3 Version 1.9.................................................................................................................................................141 12.4 Version 1.8.................................................................................................................................................142 12.5 Version 1.179.............................................................................................................................................144 12.6 Version 1.7.................................................................................................................................................145 12.7 Version 1.6.................................................................................................................................................147
10004_22 2008 Tellabs.

5
Table of Contents
12.8 Version 1.102.............................................................................................................................................149 12.9 Version 1.5.................................................................................................................................................150 12.10 Version 1.4...............................................................................................................................................151 12.11 Version 1.3...............................................................................................................................................152 12.12 Version 1.2...............................................................................................................................................154 12.13 Version 1.1...............................................................................................................................................156
13 GMX Unit: GMZ544 Unit Software ......................................................................... 159

13.1 Version 4.6.................................................................................................................................................159 13.2 Version 4.5.................................................................................................................................................160 13.3 Version 4.4.................................................................................................................................................160 13.4 Version 4.3.................................................................................................................................................162 13.5 Version 4.2.................................................................................................................................................164 13.6 Version 4.1.................................................................................................................................................164 13.7 Version 3.24...............................................................................................................................................167 13.8 Version 3.23...............................................................................................................................................169 13.9 Version 3.22...............................................................................................................................................169 13.10 Version 3.21.............................................................................................................................................170 13.11 Version 3.20.............................................................................................................................................172 13.12 Version 3.19.............................................................................................................................................173 13.13 Version 3.18.............................................................................................................................................175 13.14 Version 3.17.............................................................................................................................................178 13.15 Version 3.16.............................................................................................................................................181 13.16 Version 3.15.............................................................................................................................................183 13.17 Version 3.13.............................................................................................................................................186 13.18 Version 3.12.............................................................................................................................................188 13.19 Version 3.11.............................................................................................................................................190 13.20 Version 3.9...............................................................................................................................................193 13.21 Version 3.8...............................................................................................................................................194 13.22 Version 3.5...............................................................................................................................................196 13.23 Version 3.2...............................................................................................................................................199
14 GMX2 Unit: GMZ802 Unit Software ....................................................................... 202

14.1 Version 1.21...............................................................................................................................................202 14.2 Version 1.20...............................................................................................................................................202 14.3 Version 1.18...............................................................................................................................................203 14.4 Version 1.16...............................................................................................................................................204 14.5 Version 1.15...............................................................................................................................................204 14.6 Version 1.12...............................................................................................................................................205 14.7 Version 1.0.................................................................................................................................................206
15 LAN Module: EHZ541 Unit Software ..................................................................... 207

15.1 Version 1.2.................................................................................................................................................207 15.2 Version 1.1.................................................................................................................................................208

6
10004_22 2008 Tellabs.
Table of Contents
15.3 Version 1.0.................................................................................................................................................209
16 OMH/OMH-A Unit: OMZ675 Unit Software............................................................ 210

16.1 Version 3.3.................................................................................................................................................210 16.2 Version 3.2.................................................................................................................................................211 16.3 Version 3.1.................................................................................................................................................212 16.4 Version 3.0.................................................................................................................................................213 16.5 Version 2.0.................................................................................................................................................214 16.6 Version 1.2.................................................................................................................................................215
17 QMH and QMH-M Units: QMZ540 Unit Software .................................................. 216

17.1 Version 10.11.............................................................................................................................................216 17.2 Version 10.10.............................................................................................................................................217 17.3 Version 10.9...............................................................................................................................................218 17.4 Version 10.8...............................................................................................................................................219 17.5 Version 10.7...............................................................................................................................................220 17.6 Version 10.6...............................................................................................................................................221 17.7 Version 10.5...............................................................................................................................................222 17.8 Version 10.3...............................................................................................................................................223 17.9 Version 6.0.................................................................................................................................................224 17.10 Version 1.6...............................................................................................................................................225 17.11 Version 1.5...............................................................................................................................................226 17.12 Version 1.4...............................................................................................................................................227 17.13 Version 1.3...............................................................................................................................................228 17.14 Version 1.2...............................................................................................................................................228 17.15 Version 1.1...............................................................................................................................................229 17.16 Version 1.0...............................................................................................................................................230
18 SBU UNIT: UTZ549 Unit Software ......................................................................... 231

18.1 Version 2.2.................................................................................................................................................231 18.2 Version 2.1.................................................................................................................................................231 18.3 Version 1.0.................................................................................................................................................232
19 SCO Module: DPZ652 DSP Software .................................................................... 233

19.1 Version 4.1.................................................................................................................................................233 19.2 Version 3.1.................................................................................................................................................234 19.3 Version 1.4.................................................................................................................................................234 19.4 Version 1.3.................................................................................................................................................235 19.5 Version 1.1.................................................................................................................................................235
10004_22 2008 Tellabs.

7
Table of Contents
20 SCU-H UNIT: SCZ545 Unit Software ..................................................................... 237

20.1 Version 2.6.................................................................................................................................................237 20.2 Version 2.2.................................................................................................................................................238 20.3 Version 2.1.................................................................................................................................................238 20.4 Version 1.18...............................................................................................................................................239 20.5 Version 1.14...............................................................................................................................................239 20.6 Version 1.13...............................................................................................................................................240 20.7 Version 1.12...............................................................................................................................................241 20.8 Version 1.11...............................................................................................................................................242 20.9 Version 1.10...............................................................................................................................................243 20.10 Version 1.6...............................................................................................................................................244 20.11 Version 1.3...............................................................................................................................................245 20.12 Version 1.2...............................................................................................................................................246 20.13 Version 1.1...............................................................................................................................................246 20.14 Version 1.0...............................................................................................................................................247
21 SXU-A and SXU-B Units: SXZ282 Unit Software.................................................. 248

21.1 Version 10.6...............................................................................................................................................248 21.2 Version 10.5...............................................................................................................................................249 21.3 Version 10.4...............................................................................................................................................250 21.4 Version 10.3...............................................................................................................................................251 21.5 Version 10.2...............................................................................................................................................252 21.6 Version 10.1...............................................................................................................................................253 21.7 Version 10.0...............................................................................................................................................254 21.8 Version 6.11...............................................................................................................................................255 21.9 Version 6.10...............................................................................................................................................255 21.10 Version 6.9...............................................................................................................................................256 21.11 Version 6.8...............................................................................................................................................257 21.12 Version 6.7...............................................................................................................................................259 21.13 Version 6.6...............................................................................................................................................259 21.14 Version 6.5...............................................................................................................................................261 21.15 Version 6.3...............................................................................................................................................263 21.16 Version 6.2...............................................................................................................................................265 21.17 Version 6.1...............................................................................................................................................267 21.18 Version 6.0...............................................................................................................................................269 21.19 Version 5.9...............................................................................................................................................271 21.20 Version 5.8...............................................................................................................................................273 21.21 Version 5.7...............................................................................................................................................275 21.22 Version 5.6...............................................................................................................................................277 21.23 Version 5.5...............................................................................................................................................279
22 SXU-C Unit: SXZ289 Unit Software ....................................................................... 282

22.1 Version 10.2...............................................................................................................................................282 22.2 Version 10.1...............................................................................................................................................282 22.3 Version 10.0...............................................................................................................................................283

8
10004_22 2008 Tellabs.
Table of Contents
22.4 Version 2.13...............................................................................................................................................283 22.5 Version 2.12...............................................................................................................................................284 22.6 Version 2.11...............................................................................................................................................284 22.7 Version 2.10...............................................................................................................................................285 22.8 Version 2.9.................................................................................................................................................285 22.9 Version 2.8.................................................................................................................................................285 22.10 Version 2.7...............................................................................................................................................286 22.11 Version 2.6...............................................................................................................................................287 22.12 Version 2.5...............................................................................................................................................288 22.13 Version 2.4...............................................................................................................................................289 22.14 Version 2.3...............................................................................................................................................290
23 Tellabs 8110 CTE-R and CTE-R/208 SHDSL NTU: SBZ674 Unit Software......... 292
23.1 Version 2.0.................................................................................................................................................292 23.2 Version 1.0.................................................................................................................................................293
24 Tellabs 8110 CTE-S, CTE-S/208, CTE-R and CTE-R/208 SHDSL NTU: DPZ653 DSP Software .......................................................................................................... 294
25 Tellabs 8110 CTE-S G.703 SHDSL NTU: DPZ654 DSP Software ........................ 297
26 Tellabs 8110 CTE-S and CTE-S/208 SHDSL NTU: SBZ673 Unit Software ......... 300
27 Tellabs 8110 CTU-512 HDSL NTU: SBZ672 Unit Software .................................. 303
10004_22 2008 Tellabs.

9
Table of Contents
28 Tellabs 8110 CTU-R HDSL, Tellabs 8110 CTE-R SHDSL, Tellabs 8110 CTER/208 SHDSL and Tellabs 8110 STE-10M SHDSL NTUs: SBZ670 Unit Software307
28.1 Version 4.4.................................................................................................................................................307 28.2 Version 4.3.................................................................................................................................................309 28.3 Version 4.2.................................................................................................................................................310 28.4 Version 4.1.................................................................................................................................................311 28.5 Version 4.0.................................................................................................................................................312 28.6 Version 3.2.................................................................................................................................................314 28.7 Version 3.1.................................................................................................................................................315 28.8 Version 3.0.................................................................................................................................................315 28.9 Version 2.4.................................................................................................................................................316 28.10 Version 2.3...............................................................................................................................................317 28.11 Version 2.2...............................................................................................................................................317 28.12 Version 2.1...............................................................................................................................................317 28.13 Version 2.0...............................................................................................................................................318 28.14 Version 1.8...............................................................................................................................................318 28.15 Version 1.7...............................................................................................................................................318 28.16 Version 1.6...............................................................................................................................................318 28.17 Version 1.5...............................................................................................................................................319 28.18 Version 1.4...............................................................................................................................................319
29 Tellabs 8110 CTU-R HDSL NTU: SBZ671 Unit Software ..................................... 320
29.1 Version 2.0.................................................................................................................................................320 29.2 Version 1.4.................................................................................................................................................321 29.3 Version 1.3.................................................................................................................................................322 29.4 Version 1.2.................................................................................................................................................323 29.5 Version 1.1.................................................................................................................................................324
30 Tellabs 8110 CTU-S HDSL NTU: SBZ605 Unit Software...................................... 325

31 Tellabs 8110 STE-10M NTU: SBZ792 Unit Software ............................................ 329

31.1 Version 1.1.................................................................................................................................................329 31.2 Version 1.0.................................................................................................................................................330
32 Tellabs 8120 Mini Node M: SMZ414 Unit Software .............................................. 331

32.1 Version 5.0.................................................................................................................................................331

10
10004_22 2008 Tellabs.
Table of Contents
32.2 Version 4.6.................................................................................................................................................332 32.3 Version 4.4.................................................................................................................................................332 32.4 Version 4.3.................................................................................................................................................333 32.5 Version 4.1.................................................................................................................................................333 32.6 Version 4.0.................................................................................................................................................334 32.7 Version 3.3.................................................................................................................................................336 32.8 Version 3.2.................................................................................................................................................337 32.9 Version 3.1.................................................................................................................................................338
33 Tellabs 8130 Micro Node (SMH-U): SMZ533 Unit Software................................. 340

33.1 Version 2.2.................................................................................................................................................340 33.2 Version 2.1.................................................................................................................................................340
34 VCM-A UNIT: VCZ285A Unit Software .................................................................. 341

34.1 Version 10.2...............................................................................................................................................341 34.2 Version 10.1...............................................................................................................................................342 34.3 Version 10.0...............................................................................................................................................343 34.4 Version 2.14...............................................................................................................................................343 34.5 Version 2.13...............................................................................................................................................344 34.6 Version 2.12...............................................................................................................................................344 34.7 Version 2.11...............................................................................................................................................345 34.8 Version 2.10...............................................................................................................................................345 34.9 Version 2.9.................................................................................................................................................346 34.10 Version 2.8...............................................................................................................................................346 34.11 Version 2.7...............................................................................................................................................347 34.12 Version 2.6...............................................................................................................................................347 34.13 Version 2.5...............................................................................................................................................348 34.14 Version 2.4...............................................................................................................................................348 34.15 Version 2.3...............................................................................................................................................349 34.16 Version 2.0...............................................................................................................................................349
35 XCG Unit: SMZ538 Unit Software .......................................................................... 351

35.1 Version 3.5.................................................................................................................................................351 35.2 Version 3.4.................................................................................................................................................352 35.3 Version 3.3.................................................................................................................................................353 35.4 Version 3.2.................................................................................................................................................354 35.5 Version 3.1.................................................................................................................................................355 35.6 Version 3.0.................................................................................................................................................356 35.7 Version 2.3.................................................................................................................................................357 35.8 Version 2.2.................................................................................................................................................358 35.9 Version 2.1.................................................................................................................................................359 35.10 Version 2.0...............................................................................................................................................360 35.11 Version 1.0...............................................................................................................................................361
10004_22 2008 Tellabs.

11
Table of Contents
36 Unit Software Version Dependencies in Discontinued Products ...................... 363

36.1 AIU Unit: ABZ531 Unit Software .............................................................................................................363 36.1.1 Version 1.3........................................................................................................................................363 36.1.2 Version 1.2........................................................................................................................................364 36.1.3 Version 1.1........................................................................................................................................365 36.1.4 Version 1.0........................................................................................................................................366 36.2 AIU Unit/Module ACP514: ACZ7000 Boot Software ..............................................................................367 36.2.1 Version 1.0........................................................................................................................................367 36.3 AIU Unit: ACZ7001 Unit Software ...........................................................................................................367 36.3.1 Version 1.5........................................................................................................................................367 36.3.2 Version 1.4........................................................................................................................................368 36.3.3 Version 1.3........................................................................................................................................369 36.3.4 Version 1.2........................................................................................................................................370 36.3.5 Version 1.1........................................................................................................................................371 36.3.6 Version 1.0........................................................................................................................................372 36.4 CCO and CCS Units: CCZ445 Unit Software ...........................................................................................373 36.4.1 Version 1.2........................................................................................................................................373 36.4.2 Version 1.1........................................................................................................................................374 36.4.3 Version 1.0........................................................................................................................................374 36.5 CEU Unit: ABP732 Unit Software ............................................................................................................375 36.5.1 Version 1.019....................................................................................................................................375 36.5.2 Version 1.018....................................................................................................................................376 36.6 CEU Unit: ABZ607 Unit Software ............................................................................................................377 36.6.1 Version 2.1........................................................................................................................................377 36.6.2 Version 2.0........................................................................................................................................378 36.6.3 Version 1.0........................................................................................................................................379 36.7 CEU Unit: ACZ7004 Unit Software ..........................................................................................................380 36.7.1 Version 2.1........................................................................................................................................380 36.7.2 Version 2.0........................................................................................................................................381 36.7.3 Version 1.0........................................................................................................................................382 36.8 ECS Unit: UBZ439 Unit Software.............................................................................................................383 36.8.1 Version 1.7........................................................................................................................................383 36.9 EPS-5T and EPS-10T Units: UBZ441 Unit Software................................................................................383 36.9.1 Version 3.6........................................................................................................................................383 36.9.2 Version 3.5........................................................................................................................................384 36.9.3 Version 2.6........................................................................................................................................385 36.9.4 Version 2.5........................................................................................................................................385 36.9.5 Version 2.4........................................................................................................................................386 36.9.6 Version 2.0........................................................................................................................................387 36.10 ESO Unit: ESZ8000 Boot Software.........................................................................................................387 36.10.1 Version 1.4......................................................................................................................................387 36.11 ESO Unit: ESZ8001 Unit Software .........................................................................................................388 36.11.1 Version 2.9......................................................................................................................................388 36.11.2 Version 2.8......................................................................................................................................389 36.11.3 Version 2.7......................................................................................................................................390 36.11.4 Version 2.6......................................................................................................................................391 36.11.5 Version 2.5......................................................................................................................................391 36.11.6 Version 2.2......................................................................................................................................392 36.11.7 Version 1.0......................................................................................................................................392 36.12 ESO Unit: UBZ 536 Unit Software..........................................................................................................393

12
10004_22 2008 Tellabs.
Table of Contents
36.12.1 Version 2.4......................................................................................................................................393 36.13 FBU Unit: FBZ612 Unit Software ...........................................................................................................394 36.13.1 Version 1.2......................................................................................................................................394 36.14 FRU Unit: UBZ534 Unit Software ..........................................................................................................395 36.14.1 Version 1.5......................................................................................................................................395 36.14.2 Version 1.4......................................................................................................................................396 36.14.3 Version 1.3......................................................................................................................................397 36.14.4 Version 1.2......................................................................................................................................398 36.14.5 Version 1.1......................................................................................................................................399 36.14.6 Version 1.0......................................................................................................................................400 36.15 FRU Unit/Module FRE: FRZ535 Unit Software .....................................................................................401 36.15.1 Version 0.1......................................................................................................................................401 36.15.2 Version 0.7......................................................................................................................................402 36.16 GCH-A Unit: GCZ284A Unit Software...................................................................................................403 36.16.1 Version 2.12....................................................................................................................................403 36.16.2 Version 2.11....................................................................................................................................403 36.16.3 Version 2.10....................................................................................................................................404 36.16.4 Version 2.9......................................................................................................................................404 36.16.5 Version 2.8......................................................................................................................................405 36.16.6 Version 2.7......................................................................................................................................405 36.16.7 Version 2.6......................................................................................................................................405 36.16.8 Version 2.5......................................................................................................................................406 36.16.9 Version 2.4......................................................................................................................................406 36.16.10 Version 2.3....................................................................................................................................406 36.16.11 Version 2.0....................................................................................................................................407 36.17 GMU-M Unit: GMZ546 Unit Software ...................................................................................................408 36.17.1 Version 10.0....................................................................................................................................408 36.18 GMU-M Unit: GMZ547 Unit Software ...................................................................................................409 36.18.1 Version 10.0....................................................................................................................................409 36.19 ISD-LT and ISD-NT Units: UBZ532 Unit Software ...............................................................................410 36.19.1 Version 1.5......................................................................................................................................410 36.19.2 Version 1.4......................................................................................................................................411 36.19.3 Version 1.3......................................................................................................................................411 36.19.4 Version 1.2......................................................................................................................................412 36.19.5 Version 1.1......................................................................................................................................412 36.19.6 Version 1.0......................................................................................................................................413 36.20 ISD-LT16 Unit: IBZ610 Unit Software ...................................................................................................414 36.20.1 Version 1.0......................................................................................................................................414 36.21 IUM-5T, IUM-10T and IUM-8 Units: UBZ436 Unit Software ............................................................... 415 36.21.1 Version 3.2......................................................................................................................................415 36.21.2 Version 3.1......................................................................................................................................416 36.21.3 Version 3.0......................................................................................................................................417 36.21.4 Version 2.8......................................................................................................................................418 36.21.5 Version 2.7......................................................................................................................................419 36.21.6 Version 2.6......................................................................................................................................420 36.21.7 Version 2.5......................................................................................................................................421 36.21.8 Version 2.4......................................................................................................................................422 36.21.9 Version 2.3......................................................................................................................................422 36.21.10 Version 2.2....................................................................................................................................423 36.21.11 Version 2.1....................................................................................................................................423 36.21.12 Version 2.0....................................................................................................................................424
10004_22 2008 Tellabs.

13
Table of Contents
36.21.13 Version 1.3....................................................................................................................................424 36.21.14 Version 1.1....................................................................................................................................425 36.21.15 Version 1.0....................................................................................................................................425 36.22 LIU-H Unit (ERH581 Module): ERZ550 Unit Software ......................................................................... 427 36.22.1 Version 1.4......................................................................................................................................427 36.22.2 Version 1.3......................................................................................................................................428 36.22.3 Version 1.2......................................................................................................................................429 36.22.4 Version 1.1......................................................................................................................................430 36.22.5 Version 1.0......................................................................................................................................431 36.23 LIU-H Unit: UBZ543 Unit Software .......................................................................................................432 36.23.1 Version 1.2......................................................................................................................................432 36.23.2 Version 1.1......................................................................................................................................433 36.23.3 Version 1.0......................................................................................................................................433 36.24 NTU-2M Unit: SBZ542 Unit Software....................................................................................................434 36.24.1 Version 1.1......................................................................................................................................434 36.24.2 Version 1.0......................................................................................................................................434 36.25 SBM 384A NTU: SBA380 Unit Software ...............................................................................................435 36.25.1 Version 1.5......................................................................................................................................435 36.25.2 Version 1.4......................................................................................................................................435 36.25.3 Version 1.3......................................................................................................................................435 36.25.4 Version 1.2......................................................................................................................................436 36.25.5 Version 1.1......................................................................................................................................436 36.26 SBM 384E NTU: SBE380 Unit Software ................................................................................................437 36.26.1 Version 1.4......................................................................................................................................437 36.26.2 Version 1.3......................................................................................................................................437 36.27 SBM 64A NTU: SBA381 Unit Software .................................................................................................438 36.27.1 Version 1.3......................................................................................................................................438 36.27.2 Version 1.2......................................................................................................................................438 36.27.3 Version 1.1......................................................................................................................................439 36.27.4 Version 1.0......................................................................................................................................439 36.28 SBM 64E NTU: SBE381 Unit Software..................................................................................................440 36.28.1 Version 1.3......................................................................................................................................440 36.28.2 Version 1.2......................................................................................................................................440 36.29 SBM 768A NTU: SBA382 Unit Software ...............................................................................................441 36.29.1 Version 1.4......................................................................................................................................441 36.29.2 Version 1.3......................................................................................................................................441 36.29.3 Version 1.2......................................................................................................................................442 36.29.4 Version 1.1......................................................................................................................................442 36.30 SCP Module: SCZ281 Unit Software ......................................................................................................443 36.30.1 Version 3.3......................................................................................................................................443 36.30.2 Version 3.2......................................................................................................................................444 36.30.3 Version 3.1......................................................................................................................................444 36.30.4 Version 3.0......................................................................................................................................445 36.30.5 Version 2.0......................................................................................................................................445 36.31 SCU Unit: SCZ280 Unit Software ...........................................................................................................446 36.31.1 Version 8.6......................................................................................................................................446 36.31.2 Version 8.54....................................................................................................................................446 36.31.3 Version 8.5......................................................................................................................................447 36.31.4 Version 8.4......................................................................................................................................448 36.31.5 Version 8.3......................................................................................................................................448 36.31.6 Version 8.2......................................................................................................................................449

14
10004_22 2008 Tellabs.
Table of Contents
36.31.7 Version 8.1......................................................................................................................................450 36.31.8 Version 8.0......................................................................................................................................451 36.31.9 Version 7.6......................................................................................................................................452 36.31.10 Version 7.5....................................................................................................................................453 36.32 STU-56 DSL NTU: SBZ388 Unit Software ............................................................................................454 36.32.1 Version 1.1......................................................................................................................................454 36.32.2 Version 1.0......................................................................................................................................454 36.33 STU-1088/2048 NTU: SBZ384 Unit Software ........................................................................................455 36.33.1 Version 1.4......................................................................................................................................455 36.33.2 Version 1.3......................................................................................................................................455 36.33.3 Version 1.2......................................................................................................................................456 36.33.4 Version 1.1......................................................................................................................................457 36.33.5 Version 1.0......................................................................................................................................458 36.34 SXU-V Unit: ESZ8003 Unit Software.....................................................................................................459 36.34.1 Version 1.11....................................................................................................................................459 36.34.2 Version 1.10....................................................................................................................................460 36.34.3 Version 1.8......................................................................................................................................460 36.34.4 Version 1.7......................................................................................................................................461 36.34.5 Version 1.6......................................................................................................................................461 36.34.6 Version 1.5......................................................................................................................................462 36.34.7 Version 1.4......................................................................................................................................462 36.34.8 Version 1.3......................................................................................................................................462 36.34.9 Version 1.2......................................................................................................................................462 36.34.10 Version 1.1....................................................................................................................................462 36.35 SXU-V Unit: SXZ630 Unit Software ......................................................................................................463 36.35.1 Version 2.1......................................................................................................................................463 36.35.2 Version 2.0......................................................................................................................................464 36.35.3 Version 1.4......................................................................................................................................465 36.35.4 Version 1.3......................................................................................................................................465 36.35.5 Version 1.2......................................................................................................................................465 36.35.6 Version 1.1......................................................................................................................................466 36.36 Tellabs 8110 HTU-2M NTU: SBZ389 Unit Software .............................................................................467 36.36.1 Version 1.0......................................................................................................................................467 36.37 Tellabs 8110 STU-160 DSL NTU: SBZ385 Unit Software ..................................................................... 468 36.37.1 Version 2.2......................................................................................................................................468 36.37.2 Version 2.1......................................................................................................................................469 36.37.3 Version 2.0......................................................................................................................................470 36.37.4 Version 1.8......................................................................................................................................471 36.37.5 Version 1.7......................................................................................................................................472 36.37.6 Version 1.6......................................................................................................................................473 36.37.7 Version 1.5......................................................................................................................................474 36.37.8 Version 1.4......................................................................................................................................475 36.37.9 Version 1.3......................................................................................................................................476 36.37.10 Version 1.2....................................................................................................................................476 36.37.11 Version 1.1....................................................................................................................................477 36.37.12 Version 1.0....................................................................................................................................478 36.38 Tellabs 8110 STU-320/576/1088-2W/2304 SDSL NTUs: SBZ387 Unit Software ................................. 480 36.38.1 Version 1.3......................................................................................................................................480 36.38.2 Version 1.2......................................................................................................................................481 36.38.3 Version 1.1......................................................................................................................................482 36.38.4 Version 1.0......................................................................................................................................483
10004_22 2008 Tellabs.

15
Table of Contents
36.39 Tellabs 8120 Mini Node PM: SMZ611 Unit Software ............................................................................484 36.39.1 Version 1.1......................................................................................................................................484 36.39.2 Version 1.0......................................................................................................................................484 36.40 Tellabs 8120 Mini Node V, VM, C, VG and E: SMZ430 Unit Software.................................................485 36.40.1 Version 2.3......................................................................................................................................485 36.40.2 Version 2.1......................................................................................................................................485 36.40.3 Version 2.0......................................................................................................................................486 36.40.4 Version 1.0......................................................................................................................................487 36.41 VMM Unit: VMZ295 Unit Software .......................................................................................................489 36.41.1 Version 1.3......................................................................................................................................489 36.41.2 Version 1.1......................................................................................................................................489 36.41.3 Version 1.0......................................................................................................................................489

16
10004_22 2008 Tellabs.
General
1 General
This Unit Software Version Dependencies manual consists of the unit software release notes of different common units (control units and cross-connect units), interface units, nodes and network terminating units (NTUs) in the Tellabs 8100 managed access system. At the beginning of the manual there is an interrelations table where you can find version dependencies information in a compact form. (See Chapter 1.1 for more details on the table.) The same information can be found in the relevant unit software description in a more detailed format. Each following chapter defines the features of different unit software, their versions and the version dependencies between e.g. unit software and base unit hardware. Each unit software chapter follows the same structure:

The chapter heading gives the name of the unit and the name of the unit software in question. Some general information of the unit(s) and unit software is given. The chapter is divided in subchapters according to different versions. The latest version is always described first. Under every unit software version there are three to four items; enhancements and fixed bugs (if applicable), dependencies, restrictions and bugs.
The following utterances are used in the release notes.

The text No known bugs means that there are no bugs known to Tellabs Oy. The text No restrictions under version information means that there are no restrictions when using this version of software. In old release notes, the text No dependencies under version information means that all production hardware versions have been compatible at the time.
If you have base unit versions in your network that are not mentioned in this document, they may be sample or prototype units preceding actual production units. They may, in some cases, cause problems. If this is the case, please, contact Tellabs Oy.
If you have unit software versions in your network that are missing from this document, they are most probably sample or prototype versions. They can also be versions currently regarded inadequate and consequently taken out of production. If this is the case, please, contact Tellabs Oy.
10004_22 2008 Tellabs.

17
General
1.1 Interrelations
The interrelations table below shows in compact form dependencies between Tellabs 8100 unit software. See the release note of a relevant network element for more information. Note that only the official production versions of the software are listed in the table.
Rows marked in bold indicate SW products in production.
The meaning of the different columns and notations are described below. Basic Data consists of the following columns.
Column Tellabs 8100 Network Elements Base Units HW Version Unit SW USW Version Description Commercial product name. Hardware base unit where the unit software is downloaded. Hardware version of the base unit. Unit software product code name. Unit software version whose dependencies are described in that row.
Control Unit Data and Cross-Connect Unit Data consist of all Tellabs 8100 control units and cross-connect units so that a particular unit software version supports the widest range of functionalities of the unit software version of a particular horizontal row. Note that XCG is listed under control unit data column although it is both a control and a cross-connect unit. The notations used in the rows of the control and cross-connect unit data are explained in the following table.
Version Indicator Notation Version number Description Strong dependency A specific unit software version is required. In the case of control/cross-connect units, the unit concerned is protected. Weak dependency Any version of the unit software is compatible. No dependency There is no logical connection. A particular network element is not required. In the case of control/cross-connect units, the unit concerned is not protected.
Word Any Hyphen (-)
Other Data consists of information on dependencies between the unit software version of the particular row and software of other units (product code and version are indicated), and dependencies between the unit software version of the particular row and Tellabs 8000 network manager releases. The first Tellabs 8000 manager release that supports all functionality of the product is indicated. (Note that MartisDXX Manager is referred to as Tellabs 8100 manager in R13 or higher and Tellabs 8000 manager in R15 or higher.)
A unit software version may work with an earlier or later version of another software; this information can be found in the release note of the unit software.

18
10004_22 2008 Tellabs.
General
Basic Data Tellabs 8100 Network Elements AIU AIU AIU AIU AIU1:1/ AIU1:4 Base Units ABU257 ABU257 ABU257 ABU257 ACP514 HW Vers. 1.0/3.0 1.0 1.0 1.0 1.0 Unit SW USW Vers. 1.3 1.2 1.1 1.0 1.5 CCU SW 2.4 2.4 2.4 2.4 2.4
Control Unit Data SCP SW 3.1 3.1 3.1 3.1 3.1 SCU SW 8.4 8.4 8.4 8.4 8.4 SCU-H SW 1.10 1.10 1.10 1.10 1.10 XCG SW 2.0 2.0 2.0 2.0 2.0 CXUM SW 10.1 10.1 10.1 10.1 10.1
Cross-Connect Unit Data GMX SW 3.5 3.5 3.5 3.5 3.5 GMX2 SW Any Any SXUA/B SW 6.9 6.9 6.9 6.9 6.9 SXU-C SW 2.11 2.11 2.11 2.11 2.11 SXU-V SW 1.1 1.1 1.1
Other Data Other Units Tellabs 8100/8000 Manager Release 9.0A SP3 9.0A SP3 9.0A SP3 9.0A SP3 9.0A SP3
ABZ531 ABZ531 ABZ531 ABZ531 ACZ7001
ACZ7001 1.2 ACZ7001 1.2 ACZ7001 1.2 ACZ7001 1.1 ABP551 HW 1.0 ABP551 2.6 ABP513 HW 1.0 ABP513 1.2 ABZ531 1.0 ACZ7000 1.0 ABP551 HW 1.0 ABP551 2.6 ABP513 1.2 ACZ7000 1.0 ACZ7000 1.0 ACZ7000 1.0
AIU1:1/ AIU1:4
ACP514
1.0
ACZ7001
1.4
2.4
3.1
8.4
1.10
2.0
10.1
3.5
6.9
2.11
9.0A SP3
AIU1:1/ AIU1:4 AIU1:1/ AIU1:4 CAE CCO/CCS
ACP514 ACP514 CAE224 CAE258/ CAE227
1.0 1.0 3.0 1.0
ACZ7001 ACZ7001 CAZ287 CCZ445
1.3 1.2 2.2 1.2
2.4 2.4 -
3.1 3.1 Any 3.1
8.4 8.4 Any 8.4
1.10 1.10 1.6 1.6
2.0 2.0 Any Any
10.1 10.1 -
3.5 3.5 3.8 -
Any -
6.9 6.9 5.7 5.7
2.11 2.11 -
1.1 -
9.0A SP3 9.0A SP3 8.0 8.0
10004_22 2005 Tellabs.

19
General
Basic Data Tellabs 8100 Network Elements CCS-UNI CCS-UNI CCS-UNI CCS-UNI CCO-UNI/ CCS-UNI CCO-UNI/ CCS-UNI CCU CCU CCU CCU CEU CEU CEU Base Units PBU560 PBU560 PBU560 PBU560 PBU560 PBU560 SCU210 SCU210 SCU210 SCU210 ABP732 ABP732 ABU257 HW Vers. 3.1 3.1 3.1 3.1 2.0 1.0 4.0 4.0 4.0 3.2 1.0 1.0 2.0 Unit SW USW Vers. 5.8 5.7 5.2 4.0 2.0 1.0 2.7 2.6 2.5 2.2 1.019 1.018 2.0 CCU SW 2.5 2.5 2.5
Control Unit Data SCP SW 3.1 3.1 3.1 3.1 3.1 3.1 3.1 3.1 3.1 SCU SW 8.4 8.4 8.4 8.4 8.4 8.4 8.4 8.4 8.4 SCU-H SW 1.10 1.10 1.6 1.6 1.6 1.6 1.10 1.10 1.10 XCG SW 2.0 2.0 2.0 2.0 2.0 2.0 2.0 2.0 2.0 CXUM SW Any Any Any Any 10.1 10.1 10.1
Cross-Connect Unit Data GMX SW 3.17 3.17 3.17 3.17 3.8 3.8 3.15 3.15 3.15 GMX2 SW Any Any Any Any SXUA/B SW Any Any Any Any Any Any 6.9 6.9 6.9 SXU-C SW 2.11 2.11 2.11 SXU-V SW 2.1 2.1 1.1 1.1 1.1 1.1 1.1 1.1 1.1
Other Data Other Units Tellabs 8100/8000 Manager Release 12A SP3 12A SP3 12A SP2 11 SP1 11 SP1 10.1A 10.1A 10.1A 10.1A 10.1A ACZ7004 1.0 ABZ607 1.0 ACZ7004 1.0 ABZ607 1.0 ACZ7004 2.0 ABP732 1.018 12 12 12A
CCZ539 CCZ539 CCZ539 CCZ539 CCZ539 CCZ539 SCZ286 SCZ286 SCZ286 SCZ286 ABP732 ABP732 ABZ607
ESZ8003 1.8 ESZ8003 1.8 ESZ8003 1.1

20
10004_22 2005 Tellabs.
General
Basic Data Tellabs 8100 Network Elements CEU CEU CEU CTE-R CTE-R/208 CTE-R Base Units ABU257 ACP735 ACP735 CTE689 CTE807 CTE689 HW Vers. 2.0 1.0 1.0 1.0 Unit SW USW Vers. 1.0 2.0 1.0 2.0 CCU SW 2.5 2.5 2.5 -
Control Unit Data SCP SW 3.1 3.1 3.1 SCU SW 8.4 8.4 8.4 SCU-H SW 1.10 1.10 1.10 XCG SW 2.0 2.0 2.0 CXUM SW 10.1 10.1 10.1 -
Cross-Connect Unit Data GMX SW 3.15 3.15 3.15 GMX2 SW SXUA/B SW 6.9 6.9 6.9 SXU-C SW 2.11 2.11 2.11 SXU-V SW 1.1 1.1 1.1 -
Other Data Other Units Tellabs 8100/8000 Manager Release 12 12A 12 15A
ABZ607 ACZ7004 ACZ7004 SBZ674
ACZ7004 1.0 ABP732 1.018 ABZ607 2.0 ABP732 1.018 ABZ607 1.0 ABP732 1.018 DPZ653 3.0 SBZ670 3.0 OMZ675 3.0 EMZ642 1.0 DPZ653 1.3 SBZ670 3.0 OMZ675 1.2 EMZ642 1.0 SBZ673 3.0 OMZ675 3.0
1.0
SBZ674
1.0
13A SP1
CTE-R CTE-S V.35 CTE-S V.36 CTE-S X.21 CTE-R/208 CTE-S/208 V.35 CTE-S/208 V.36 CTE-S/208 X.21 CTE-R CTE-S V.35 CTE-S V.36 CTE-S X.21
CTE689 CTE685 CTE688 CTE686 CTE807 CTE803 CTE806 CTE804 CTE689 CTE685 CTE688 CTE686
1.0 2.0 2.0 2.0 1.0 2.0 2.0 2.0 1.0 2.0 2.0 2.0
DPZ653
3.3
15A
DPZ653
2.0
SBZ670 3.0 SBZ673 2.0 SBZ674 1.0 OMZ675 1.2 EMZ642 1.0
13
10004_22 2005 Tellabs.

21
General
Basic Data Tellabs 8100 Network Elements CTE-R CTE-S V.35 CTE-S V.36 CTE-S X.21 CTE-S G.703 CTE-S/208 G.703 CTE-S G.703 CTE-S G.703 CTE-S G.703 CTE-S V.35 CTE-S V.36 CTE-S X.21 CTE-S/208 G.703 CTE-S/208 V.35 CTE-S/208 V.36 CTE-S/208 X.21 CTE-S G.703 CTE-S V.35 CTE-S V.36 CTE-S X.21 CTE-S G.703 CTE-S V.35 CTE-S V.36 CTE-S X.21 Base Units CTE689 CTE685 CTE688 CTE686 CTE687 CTE805 CTE687 CTE687 CTE687 CTE685 CTE688 CTE686 CTE805 CTE803 CTE806 CTE804 CTE687 CTE685 CTE688 CTE686 CTE687 CTE685 CTE688 CTE686 HW Vers. 1.0 1.0 1.0 1.0 2.0 2.0 2.0 1.0 2.0 2.0 2.0 2.0 2.0 2.0 2.0 2.0 2.0 2.0 2.0 2.0 1.0 1.0 1.0 1.0 SBZ673 2.0 Unit SW USW Vers. 1.3 CCU SW -
Control Unit Data SCP SW SCU SW SCU-H SW XCG SW CXUM SW -
Cross-Connect Unit Data GMX SW GMX2 SW SXUA/B SW SXU-C SW SXU-V SW -
Other Data Other Units Tellabs 8100/8000 Manager Release 13
DPZ653
DPZ654 DPZ654 DPZ654 SBZ673
3.3 2.0 1.3 3.0
SBZ670 3.0 SBZ673 1.0 SBZ674 1.0 OMZ675 1.2 EMZ642 1.0 SBZ673 3.0 OMZ675 3.0 SBZ673 2.0 OMZ675 1.2 EMZ642 1.0 SBZ673 1.0 OMZ675 1.2 EMZ642 1.0 OMZ675 3.0 DPZ653 3.0 DPZ654 3.0
15A 13 13 15A
OMZ675 1.2 DPZ653 1.1 DPZ654 1.1 OMZ675 1.2 DPZ653 1.1 DPZ654 1.1
13
SBZ673
1.0
13

22
10004_22 2005 Tellabs.
General
Basic Data Tellabs 8100 Network Elements

CTU-512 V.35 CTU-512 X.21 CTU-512 V.35 CTU-512 X.21 CTU-512 V.35 CTU-512 X.21 CTU-512 V.35 CTU-512 X.21
Control Unit Data Unit SW USW Vers. 3.0 CCU SW SCP SW SCU SW SCU-H SW XCG SW CXUM SW -
Other Data Other Units Tellabs 8100/8000 Manager Release 14
Base Units CTU680 CTU681 CTU680 CTU681 CTU680 CTU681 CTU680 CTU681 CTU399 CTE689 CTE807 STE790 CTU399 CTE689 CTE807 STE790 CTU399 CTE689 CTE807 STE790 CTU399 CTE689 STE790
HW Vers. 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 2.0 1.0 1.0 1.0 2.0 1.0 1.0 1.0 2.0 1.0 1.0 1.0 2.0 1.0 1.0
SBZ672
GMZ283 10.0 QMZ540 10.5 GMZ283 10.0 QMZ540 10.5 GMZ283 10.0 QMZ540 10.5 GMZ283 10.0 QMZ540 10.5 SBZ671 1.3 SBZ674 2.0 DPZ653 3.0 SBZ792 1.0 DPZ794 1.0 SBZ671 1.3 SBZ674 2.0 DPZ653 3.0 SBZ792 1.0 DPZ794 1.0 SBZ671 1.3 SBZ674 2.0 DPZ653 3.0 SBZ792 1.0 DPZ794 1.0 SBZ671 1.3 SBZ674 1.0 DPZ653 1.3 SBZ792 1.0 DPZ794 1.0
SBZ672 SBZ672 SBZ672 SBZ670
2.1 2.0 1.0 4.4
14 14 12A 16 SP1
CTU-R CTE-R CTE-R/208 STE-10M CTU-R CTE-R CTE-R/208 STE-10M CTU-R CTE-R CTE-R/208 STE-10M CTU-R CTE-R STE-10M
SBZ670
4.3
15B
SBZ670
4.2
15A
SBZ670
4.1
15
10004_22 2005 Tellabs.

23
General
Basic Data Tellabs 8100 Network Elements CTU-R CTE-R STE-10M CTU-R CTE-R CTU-R CTE-R CTU-R CTU-R CTU-R CTU-R CTU-R CTU-R CTU-R CTU-R Base Units CTU399 CTE689 STE790 CTU399 CTE689 CTU399 CTE689 CTU399 CTU399 CTU399 CTU399 CTU399 CTU399 CTU399 CTU399 HW Vers. 2.0 1.0 1.0 2.0 1.0 2.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 Unit SW USW Vers. 4.0 CCU SW -
Other Data Other Units Tellabs 8100/8000 Manager Release 14A 3P1
SBZ670
SBZ670 SBZ670 SBZ670 SBZ670 SBZ670 SBZ670 SBZ671 SBZ671 SBZ671 SBZ671
3.2 3.0 2.4 2.3 1.8 1.5 2.0 1.4 1.3 1.2
SBZ671 1.3 SBZ674 1.0 DPZ653 1.3 SBZ792 1.0 DPZ794 1.0 SBZ671 1.3 SBZ674 1.0 DPZ653 1.3 SBZ671 1.3 SBZ674 1.0 DPZ653 1.3 SBZ671 1.2 SBZ671 1.2 SBZ671 1.1 SBZ671 1.1 SBZ670 1.5 GMZ283 10.0 QMZ540 10.5 SBZ670 1.5 GMZ283 10.0 QMZ540 10.5 SBZ670 1.5 GMZ283 10.0 QMZ540 10.5 SBZ670 1.5 GMZ283 10.0 QMZ540 10.5
13A SP1 13A SP1 13 SP1 13 SP1 12 SP1 12 SP1 14 14 12 SP1 12 SP1

24
10004_22 2005 Tellabs.
General
Basic Data Tellabs 8100 Network Elements CTU-R CTU-S G703 CTU-S V.35 CTU-S X.21 CTU-S G703 CTU-S V.35 CTU-S X.21 CTU-S G703 CTU-S V.35 CTU-S X.21 CTU-S G.703 CTU-S V.35 CTU-S X.21 CXU-M CXU-M CXU-M CXU-M CXU-M CXU-M CXU-M Base Units CTU399 CTU397 CTU395 CTU396 CTU397 CTU395 CTU396 CTU397 CTU395 CTU396 CTU397 CTU395 CTU396 CXU212 CXU212 CXU212 CXU212 CXU212 CXU212 CXU212 HW Vers. 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 5.0 5.0 5.0 5.0 5.0 <5.0 <5.0 Unit SW USW Vers. 1.1 3.0 2.0 1.1 1.0 10.6 10.4 10.3 10.2 10.1 2.17 2.15 CCU SW Any Any Any Any Any Any Any
Control Unit Data SCP SW SCU SW SCU-H SW XCG SW CXUM SW 10.6 10.4 10.3 10.2 10.1 2.17 2.15
Cross-Connect Unit Data GMX SW GMX2 SW SXUA/B SW SXU-C SW 2.10 2.10 2.10 2.10 2.10 2.10 2.10 SXU-V SW -
Other Data Other Units Tellabs 8100/8000 Manager Release 12 SP1 14 14 11 SP2 11 SP2 9.0B SP12 9.0B SP12 9.0B SP12 9.0B SP12 9.0B SP12 9.0B SP12 9.0B SP12
SBZ671 SBZ605 SBZ605 SBZ605 SBZ605 SXZ288 SXZ288 SXZ288 SXZ288 SXZ288 SXZ288 SXZ288
SBZ670 1.5 GMZ283 10.0 QMZ540 10.5 GMZ283 10.0 QMZ540 10.5 GMZ283 10.0 QMZ540 10.5 GMZ283 10.0 QMZ540 10.5 GMZ283 10.0 QMZ540 10.5
10004_22 2005 Tellabs.

25
General
Basic Data Tellabs 8100 Network Elements CXU-M CXU-M CXU-M E3C EAE/ ADPCM ECS-5T ECS-10T EPS-5T EPS-5T EPS-10T EPS-5T EPS-10T EPS-5T EPS-10T ESO ESO Base Units CXU212 CXU212 CXU212 GPT782 EAE229 UBU254 UBU256 + ECS440 UBU254 + EPS442 UBU254 UBU256 + EPS442 UBU254 UBU256 + EPS442 UBU254 UBU256 + EPS442 ESO570 ESO570 HW Vers. <5.0 <5.0 <5.0 1.0 1.0 1.0/2.0 1.0/2.0 1.0 2.0 3.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 Unit SW USW Vers. 2.14 2.13 2.12 1.0 1.1 1.7 3.6 2.6 2.5 2.4 2.9 2.7 CCU SW Any Any Any Any -
Control Unit Data SCP SW 3.1 Any Any Any Any Any Any 3.1 3.1 SCU SW 8.4 8.0 Any Any Any Any Any 8.4 8.4 SCU-H SW 1.6 1.6 1.6 1.6 1.6 1.6 1.6 1.6 1.6 XCG SW 2.0 Any Any Any Any Any Any Any Any CXUM SW 2.14 2.13 2.12 Any -
Cross-Connect Unit Data GMX SW Any GMX2 SW Any SXUA/B SW Any Any Any 10.2 10.2 10.1 10.1 6.9 6.9 SXU-C SW 2.10 2.10 2.10 Any SXU-V SW Any 1.1 1.1 1.1 1.1 1.1 PDF593 HW 2.0
Other Data Other Units Tellabs 8100/8000 Manager Release 9.0B SP12 9.0B SP12 9.0B SP12 13 8.0 9.0 10.1A 10.0A SP2 10.0A SP2 10.0A SP2 UBZ536 2.4 ESZ8000 1.4 GMZ283 6.9 UBZ536 2.4 ESZ8000 1.4 GMZ283 6.9 10.0A 10.0A
SXZ288 SXZ288 SXZ288 GPZ641 EAZ418 UBZ439 UBZ441 UBZ441 UBZ441 UBZ441 ESZ8001 ESZ8001

26
10004_22 2005 Tellabs.
General
Basic Data Tellabs 8100 Network Elements ESO ESO ESU Base Units ESO570 UBU254 ESU783/ ESM784 HW Vers. 1.0 2.0 1.0 Unit SW USW Vers. 2.6 2.4 1.12 CCU SW Any
Control Unit Data SCP SW 3.1 3.1 3.1 SCU SW 8.4 8.4 8.4 SCU-H SW 1.6 1.6 1.6 XCG SW Any Any 3.5 CXUM SW Any
Cross-Connect Unit Data GMX SW 4.1 GMX2 SW Any SXUA/B SW 6.9 6.9 10.5 SXU-C SW Any SXU-V SW 1.1 Any
Other Data Other Units Tellabs 8100/8000 Manager Release 10.0A 10.0A 15
ESZ8001 UBZ536 EMZ642
ESU
ESU783/ ESM784
1.0
EMZ642
1.11
Any
3.1
8.4
1.6
3.5
Any
4.1
Any
10.5
Any
Any
UBZ536 2.4 ESZ8000 1.4 GMZ283 6.9 ESZ8001 2.5 GMZ283 6.9 UBZ534 1.0 GMZ460/461 1.7 with GMU450 HW 2.0; GMZ460/461 1.179 with GMU450 HW 1.0 SBZ674 1.0; SCO785 HW 3.1 GMZ460/461 1.7 with GMU450 HW 2.0; GMZ460/461 1.179 with GMU450 HW 1.0 SBZ674 1.0; SCO785 HW 3.1
15
10004_22 2005 Tellabs.

27
General
Basic Data Tellabs 8100 Network Elements ESU Base Units ESU783/ ESM784 HW Vers. 1.0 Unit SW USW Vers. 1.10 CCU SW Any
Control Unit Data SCP SW 3.1 SCU SW 8.4 SCU-H SW 1.6 XCG SW 3.5 CXUM SW Any
Cross-Connect Unit Data GMX SW 4.1 GMX2 SW SXUA/B SW 10.5 SXU-C SW Any SXU-V SW Any
Other Data Other Units Tellabs 8100/8000 Manager Release 14 SP3
EMZ642
ESU
ESU783/ ESM784
1.0
EMZ642
1.9
Any
3.1
8.4
1.6
3.5
Any
4.1
10.5
Any
Any
ESU
ESU783/ ESM784
1.0
EMZ642
1.8
Any
3.1
8.4
1.6
2.0
Any
3.19
Any
Any
Any
GMZ460/461 1.7 with GMU450 HW 2.0; GMZ460/461 1.179 with GMU450 HW 1.0 SBZ674 1.0 GMZ460/461 1.7 with GMU450 HW 2.0; GMZ460/461 1.179 with GMU450 HW 1.0 SBZ674 1.0 GMZ460/461 1.7 with GMU450 HW 2.0; GMZ460/461 1.179 with GMU450 HW 1.0 SBZ674 1.0
14 SP3
14 SP1

28
10004_22 2005 Tellabs.
General
Basic Data Tellabs 8100 Network Elements ESU Base Units ESU783/ ESM784 HW Vers. 1.0 Unit SW USW Vers. 1.7 CCU SW Any
Control Unit Data SCP SW 3.1 SCU SW 8.4 SCU-H SW 1.6 XCG SW 2.0 CXUM SW Any
Cross-Connect Unit Data GMX SW 3.19 GMX2 SW SXUA/B SW Any SXU-C SW Any SXU-V SW Any
EMZ642
ESU
ESU783/ ESM784
1.0
EMZ642
1.3
Any
3.1
8.4
1.6
2.0
Any
3.18
Any
Any
Any
GMZ460/461 1.7 with GMU450 HW 2.0; GMZ460/461 1.179 with GMU450 HW 1.0 SBZ674 1.0 GMZ460/461 1.7 with GMU450 HW 2.0; GMZ460/461 1.179 with GMU450 HW 1.0 SBZ674 1.0
S35755.01.A0
13A SP1
FBU FRU FRU FRU FRU FRU
FBU763 UBU259 UBU259 UBU259 UBU259 UBU259
1.1 1.0 1.0 1.0 1.0 1.0
FBZ612 UBZ534 UBZ534 UBZ534 UBZ534 UBZ534
1.2 1.4 1.3 1.2 1.1 1.0
Any 2.2 2.2 -
3.1 3.1 3.1 3.1 3.1 3.1
8.0 8.4 8.4 8.4 8.4 8.4
1.6 1.10 1.10 1.6 1.6 1.6
2.0 -
10.1 2.12 2.12 2.10 2.7 2.7
3.8 3.2 3.2 Any Any Any
Any Any -
6.5 6.9 6.9 6.9 6.9 6.9
2.7 2.11 2.11 2.8 2.8 2.8
Any 1.1 -
C1.0 FRZ535 0.1 GMZ283 6.9 FRZ535 0.1 GMZ283 6.9 FRZ535 0.7 GMZ283 6.9 FRZ535 0.7 GMZ283 6.9 FRZ535 0.7 GMZ283 6.9
12A SP1 11 SP3 11 SP2 9.0B SP6 9.0B SP6 9.0B SP6
10004_22 2005 Tellabs.

29
General
Basic Data Tellabs 8100 Network Elements FRU FRU GCH-A GCH GMH GMH GMH GMH GMH GMM GMM GMM GMM Base Units FRE515 FRE515 GCH221A GCH221 GMH220 GMH220 GMH220 GMH220 GMH220 GMM253 GMM253 GMM253 GMM253 HW Vers. 1.0 1.0 3.04.0 1.0 5.0 5.0 5.0 4.0 4.0 1.x 1.x 1.x 1.x Unit SW USW Vers. 0.1 0.7 2.12 1.9 10.2 10.1 10.0 6.10 6.9 2.3 2.2 2.1 2.0 CCU SW 2.2 Any Any Any Any Any Any Any Any Any
Control Unit Data SCP SW 3.1 3.1 Any Any Any Any Any Any Any Any Any SCU SW 8.4 8.4 8.0 8.0 Any Any Any Any Any Any Any Any Any SCU-H SW 1.6 1.6 1.6 1.6 Any Any Any Any Any Any Any Any Any XCG SW Any Any Any Any Any Any Any Any Any Any Any CXUM SW 2.10 2.7 Any Any Any Any Any Any Any Any Any
Cross-Connect Unit Data GMX SW Any Any Any Any Any Any Any Any Any Any Any GMX2 SW Any Any Any Any SXUA/B SW 6.9 6.9 5.4 5.4 Any Any Any Any Any 6.5 6.5 6.5 6.5 SXU-C SW 2.8 2.8 Any Any Any Any Any 2.6 2.6 2.6 2.6 SXU-V SW 1.1 1.1 1.1 1.1 1.1 1.1 -
Other Data Other Units Tellabs 8100/8000 Manager Release 9.0B SP6 9.0B SP6 8.0 8.0 12 12 10.0 10.0 10.0 GDM 298 HW 1.x GDM 298 HW 1.x GDM 298 HW 1.x GDM 298 HW 1.x 8.0A 8.0A 8.0A 8.0A
FRZ535 FRZ535 GCZ284A GCZ284 GMZ283 GMZ283 GMZ283 GMZ283 GMZ283 GMZ438 GMZ438 GMZ438 GMZ438
UBZ534 1.0 GMZ283 6.9 UBZ534 1.0 GMZ283 6.9

30
10004_22 2005 Tellabs.
General
Basic Data Tellabs 8100 Network Elements GMU GMU-A GMU GMU-A GMU GMU-A GMU GMU GMU-A GMU GMU-A GMU GMU GMU-A GMU GMU-A Base Units GMU450 GMU450 GMU450 GMU450 GMU450 GMU450 GMU450 GMU450 GMU450 GMU450 GMU450 HW Vers. 1.0 1.0 1.0 1.0 1.0 2.0 1.0 1.0 1.0 1.0 1.0 Unit SW USW Vers. 1.8 1.7 1.6 1.5 1.4 1.11 1.10 1.9 1.8 1.7 1.6 CCU SW Any Any Any Any Any Any Any Any Any Any Any
Control Unit Data SCP SW 3.1 3.1 3.1 3.1 3.1 3.1 3.1 3.1 3.1 3.1 3.1 SCU SW 8.5 8.5 8.5 8.5 8.4 8.5 8.5 8.5 8.5 8.5 8.5 SCU-H SW 1.6 1.6 1.6 1.6 1.6 1.6 1.6 1.6 1.6 1.6 1.6 XCG SW 2.1 2.1 2.1 2.1 2.1 2.1 2.1 2.1 2.1 2.1 2.1 CXUM SW 2.7 2.7 2.7 2.7 2.7 2.7 2.7 2.7 2.7 2.7 2.7
Cross-Connect Unit Data GMX SW Any Any Any Any Any Any Any Any Any Any Any GMX2 SW Any Any Any SXUA/B SW 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 6.8 SXU-C SW 2.7 2.7 2.7 2.7 2.7 2.7 2.7 2.7 2.7 2.7 2.7 SXU-V SW 1.1 1.1 1.1 1.1 1.1 1.1 1.1 1.1 1.1 1.1
Other Data Other Units Tellabs 8100/8000 Manager Release 12A SP3 12A SP3 12A SP3 10.0 10.0 12A SP3 12A SP3 12A SP3 12A SP3 12A SP3 12A SP3
GMZ460 GMZ460 GMZ460 GMZ460 GMZ460 GMZ461 GMZ461 GMZ461 GMZ461 GMZ461 GMZ461
DSU453 HW 1.0/2.0 GMZ461 1.8 DSU453 HW 1.0/2.0 GMZ461 1.7 DSU453 HW 1.0/2.0 GMZ461 1.6 GMZ461 1.5 GMZ461 1.4 DSU453 HW 2.0 GMZ460 1.8 DSU453 HW 1.0 GMZ460 1.8 DSU453 HW 2.0 GMZ460 1.8 DSU453 HW 1.0 GMZ460 1.8 DSU453 HW 1.0/2.0 GMZ460 1.7 DSU453 HW 1.0/2.0 GMZ460 1.6
10004_22 2005 Tellabs.

31
General
Basic Data Tellabs 8100 Network Elements GMU GMU GMU-M GMU-M GMX GMX GMX GMX GMX Base Units GMU450 GMU450 GMU450 GMU450 GMX588 GMX588 GMX588 GMX588 GMX588 HW Vers. 1.0 1.0 1.0 1.0 3.0 3.0 3.0 3.0 3.0 Unit SW USW Vers. 1.5 1.4 10.0 10.0 4.6 4.4 4.3 4.2 4.1 Do not use!!! 3.24 3.22 3.21 CCU SW Any Any Any Any -
Control Unit Data SCP SW 3.1 3.1 3.1 3.1 SCU SW 8.4 8.4 8.4 8.4 SCU-H SW 1.6 1.6 1.6 1.6 1.11 1.11 1.11 1.11 1.11 XCG SW 2.1 2.1 2.1 2.1 CXUM SW 2.7 2.7 2.7 2.7 -
Cross-Connect Unit Data GMX SW Any Any Any Any 4.6/ 3.24 4.4/ 3.22 4.3/ 3.21 4.2 4.1 GMX2 SW Any SXUA/B SW 6.8 6.8 6.9 6.9 SXU-C SW 2.7 2.7 2.7 2.7 SXU-V SW 1.1 -
Other Data Other Units Tellabs 8100/8000 Manager Release 10.0 10.0 10.0 10.0 11 SP4 11 SP4 11 SP4 11 SP4 11 SP4
GMZ461 GMZ461 GMZ546 GMZ547 GMZ544 GMZ544 GMZ544 GMZ544 GMZ544
GMZ460 1.5 GMZ460 1.4 GMZ547 10.0 GMZ546 10.0
GMX GMX GMX
GMX588 GMX588 GMX588
1.0/2.0 1.0/2.0 1.0/2.0
GMZ544 GMZ544 GMZ544
1.11 1.11 1.11
3.24/ 4.6 3.22/ 4.4 3.21/ 4.3
11 SP4 11 SP4 11 SP4

32
10004_22 2005 Tellabs.
General
Basic Data Tellabs 8100 Network Elements GMX GMX GMX GMX GMX GMX GMX GMX2 GMX2 GMX2 GMX2 GMX2 HTU-2M Base Units GMX588 GMX588 GMX588 GMX588 GMX588 GMX588 GMX588 GMX811 GMX811 GMX811 GMX811 GMX811 HTU329 HW Vers. 1.0/2.0 1.0/2.0 1.0/2.0 1.0/2.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 1.0 Unit SW USW Vers. 3.19 3.18 3.17 3.15 3.8 3.5 3.2 1.21 1.20 1.18 1.16 1.15 1.0 CCU SW -
Control Unit Data SCP SW SCU SW SCU-H SW 1.11 1.11 1.11 1.6 1.6 1.6 1.6 2.6/1.18 2.6/1.18 2.6/1.18 2.6/1.18 2.6/1.18 XCG SW CXUM SW -
Cross-Connect Unit Data GMX SW 3.19 3.18 3.17 3.15 3.8 3.5 3.2 GMX2 SW 1.21 1.20 1.18 1.16 1.15 SXUA/B SW SXU-C SW SXU-V SW -
Other Data Other Units Tellabs 8100/8000 Manager Release 11 SP4 11 SP4 11 SP4 11 SP4 11 SP2 10.1A 10.1A 16A SP2 16A SP2 16A SP2 16A SP2 16A SP2 GMZ238 10.0 QMZ540 10.5 10.1A
GMZ544 GMZ544 GMZ544 GMZ544 GMZ544 GMZ544 GMZ544 GMZ802 GMZ802 GMZ802 GMZ802 GMZ802 SBZ389
10004_22 2005 Tellabs.

33
General
Basic Data Tellabs 8100 Network Elements ISD-LT/ ISD-NT ISD-LT/ ISD-NT ISD-LT16 IUM-8 Base Units UBU255/ ISD519/ IUM437 UBU255/ ISD519/ IUM437 IBU726 UBU768 HW Vers. 1.0 1.0 1.0 2.0 Unit SW USW Vers. 1.5 1.4 1.0 3.2 CCU SW 2.5 -
Control Unit Data SCP SW 3.1 3.1 SCU SW 8.0 8.0 8.4 8.4 SCU-H SW 1.6 1.6 1.10 1.6 XCG SW 2.0 2.0 2.0 2.0 CXUM SW 10.1 -
Cross-Connect Unit Data GMX SW 3.8 3.17 Any GMX2 SW Any Any Any SXUA/B SW Any Any Any Any SXU-C SW 10.2 SXU-V SW 1.1 2.1 1.1
Other Data Other Units Tellabs 8100/8000 Manager Release 11 SP1 10.1A 12A SP3 SBZ385 1.8 with STU315 HW 4.0 SBZ385 2.1 with STU315 HW 5.0 SBZ385 1.8 with STU315 HW 4.0 SBZ385 2.1 with STU315 HW 5.0 SBZ385 1.8 with STU315 HW 4.0 SBZ385 2.1 with STU315 HW 5.0 SBZ385 1.8 with STU315 HW 4.0 SBZ385 2.1 with STU315 HW 5.0 12 SP1
UBZ532 UBZ532 IBZ610 UBZ436
IUM-8
UBU768
2.0
UBZ436
3.1
3.1
8.4
1.6
2.0
Any
Any
1.1
12 SP1
IUM-8
UBU768
2.0
UBZ436
3.0
3.1
8.4
1.6
2.0
Any
Any
1.1
12 SP1
IUM-5T/ IUM-10T/ IUM-8
UBU239/ UBU255/ UBU768
2.0 1.0 1.0
UBZ436
2.8
3.1
8.4
1.6
2.0
Any
Any
1.1
12 SP1

34
10004_22 2005 Tellabs.
General
Basic Data Tellabs 8100 Network Elements IUM-5T/ IUM-10T/ IUM-8 Base Units UBU239/ UBU255/ UBU768 HW Vers. 2.0 1.0 1.0 Unit SW USW Vers. 2.7 CCU SW -
Control Unit Data SCP SW 3.1 SCU SW 8.4 SCU-H SW 1.6 XCG SW 2.0 CXUM SW -
Cross-Connect Unit Data GMX SW Any GMX2 SW SXUA/B SW Any SXU-C SW SXU-V SW 1.1
UBZ436
IUM-5T/ IUM-10T/ IUM-8
UBU239/ UBU255/ UBU768
2.0 1.0 1.0
UBZ436
2.5
3.1
8.4
1.6
2.0
Any
Any
1.1
SBZ385 1.8 with STU315 HW 4.0 SBZ385 2.1 with STU315 HW 5.0 SBZ385 1.8 with STU315 HW 4.0 SBZ385 2.1 with STU315 HW 5.0
12 SP1
IUM-5T/ IUM-10T IUM-5T/ IUM-10T LAN Module
UBU239/ UBU255 UBU239/ UBU255 EHI392/ EBH718/ EBH719
2.0 2.0 1.2 1.0 1.0
UBZ436 UBZ436 EHZ541
2.4 2.3 1.2
3.1 3.1 -
8.4 8.4 -
1.6 1.6 -
2.0 2.0 -
Any Any -
Any Any -
SBZ384 1.4 SBZ385 1.5 SBZ387 1.0 SBZ389 1.0 VCZ285A 10.1 SMZ414 5.0 UBZ543 1.1 UBZ543 1.1 UBZ543 1.1 ERZ550 1.2 10.0A 10.0A SP2
LIU-H LIU-H LIU-H LIU-H
UBU714/ ERH581 UBU714/ ERH581 UBU714/ ERH581 UBU714
1.0 1.0 1.0 1.0
ERZ550 ERZ550 ERZ550 UBZ543
1.4 1.3 1.2 1.2
Any Any Any Any
3.2 3.2 3.2 3.2
8.4 8.4 8.4 8.4
1.6 1.6 1.6 1.6
2.0 2.0 2.0 2.0
Any Any Any Any
Any Any Any Any
Any -
Any Any Any Any
Any Any Any Any
1.1 1.1 1.1
10.1A 10.1A 10.1A 10.1A
10004_22 2005 Tellabs.

35
General
Basic Data Tellabs 8100 Network Elements LIU-H NTU-2M OMH/OMHA OMH/OMHA OMH/OMHA OMH OMH QMH QMH QMH QMH QMH QMH Base Units UBU714 STU352 OMH771 OMH771 OMH771 OMH771 OMH771 QMH509 QMH509 QMH509 QMH509 QMH509 QMH509 HW Vers. 1.0 1.1 3.0 3.0 3.0 1.0/2.0 1.0 3.0 3.0 3.0 3.0 3.0 3.0 Unit SW USW Vers. 1.1 1.1 3.3 3.2 3.0 2.0 1.2 10.11 10.10 10.9 10.8 10.7 10.5 CCU SW Any Any Any Any Any Any Any Any Any Any Any Any
Control Unit Data SCP SW 3.2 3.1 3.1 3.1 3.1 3.1 Any Any Any Any Any Any SCU SW 8.4 8.4 8.4 8.4 8.4 8.4 Any Any Any Any Any Any SCU-H SW 1.6 1.6 1.6 1.6 1.6 1.6 1.6 1.6 1.6 1.6 1.6 1.6 XCG SW 2.0 3.5 3.5 3.5 3.5 2.0 2.0 2.0 2.0 2.0 2.0 2.0 CXUM SW Any Any Any Any Any Any Any Any Any Any Any Any
Cross-Connect Unit Data GMX SW Any 4.2 4.2 4.2 4.1 Any Any Any Any Any Any Any GMX2 SW Any Any Any Any Any SXUA/B SW Any 10.5 10.5 10.5 10.5 Any Any Any Any Any Any Any SXU-C SW Any Any Any Any Any Any Any Any Any Any Any Any SXU-V SW 1.1 Any Any Any Any Any 1.1 1.1 1.1 1.1 1.1 1.1
Other Data Other Units Tellabs 8100/8000 Manager Release 10.1A 10.0 15A 15A 15A 14 SP3 13 GMZ283 any GMZ283 any GMZ283 any GMZ283 any GMZ283 any GMZ283 any 13 13 13 13 13 12
UBZ543 SBZ542 OMZ675 OMZ675 OMZ675 OMZ675 OMZ675 QMZ540 QMZ540 QMZ540 QMZ540 QMZ540 QMZ540
ERZ550 1.2 GMZ283 6.10 SCO HW 4.0 SCO HW 4.0 SCO HW 4.0 SCO HW 3.1

36
10004_22 2005 Tellabs.
General
Basic Data Tellabs 8100 Network Elements QMH QMH QMH QMH QMH QMH-M SBM 64A SBM 64E SBM 384A SBM 384E SBM 768A SBM 2048C /V/VM/VG SBM 2048E Base Units QMH509 QMH509 QMH509 QMH509 QMH509 QMH740 SBM311 SBM311 SBM310 SBM310 HBU312 SMU401 SMU501 HW Vers. 3.0 1.0/2.0 1.0/2.0 1.0/2.0 1.0/2.0 1.0 1.0 1.0 1.0 1.0 1.0 3.1 1.0 Unit SW USW Vers. 10.3 1.6 1.5 1.3 1.1 6.0 1.3 1.3 1.5 1.4 1.4 2.3 2.3 CCU SW Any Any Any Any Any Any -
Control Unit Data SCP SW Any Any Any Any SCU SW Any Any Any Any Any Any SCU-H SW 1.6 1.6 1.6 1.6 1.6 1.6 XCG SW 2.0 2.0 2.0 2.0 2.0 2.0 CXUM SW Any Any Any Any Any Any -
Cross-Connect Unit Data GMX SW Any Any Any Any Any Any GMX2 SW Any Any SXUA/B SW Any Any Any Any Any Any SXU-C SW Any Any Any Any Any Any SXU-V SW 1.1 1.1 -
Other Data Other Units Tellabs 8100/8000 Manager Release 11 SP1 12 SP1 12 SP1 10.0 10.0 GMZ283 any GCZ284 2.12 GCZ284 2.12 GMZ283 6.5 GMZ283 6.5 GCZ284 2.12 GMZ283 6.1 11 SP1 8.0 8.0 8.0 8.0 8.0 8.0 8.0
QMZ540 QMZ540 QMZ540 QMZ540 QMZ540 QMZ540 SBA381 SBE381 SBA380 SBE380 SBA382 SMZ430 SMZ430
GMZ283 any GMZ283 any GMZ283 any
10004_22 2005 Tellabs.

37
General
Basic Data Tellabs 8100 Network Elements SBM 2048C /VG/VM SBM 2048M SBM 2048M SBM 2048M SBM 2048PM SBU SBU SCO SCO SCO SCO SCO SCP Base Units SMU747 SMU701 SMU701 SMU401 SMU759 UTU720 UTU720 SCO786 SCO786 SCO785 SCO786 SCO785 SCO786 SCO785 SCO786 SCP211 HW Vers. 6.0 6.1 6.0 5.0 1.0 2.0 1.0 3.0 3.0 3.0 2.0 2.0 2.0 2.0 2.0 3.0 Unit SW USW Vers. 2.3 5.0 4.6 4.4 1.1 2.1 1.0 4.1 3.1 1.4 1.3 1.1 3.3 CCU SW -
Control Unit Data SCP SW SCU SW 7.6 SCU-H SW XCG SW CXUM SW -
Cross-Connect Unit Data GMX SW 3.8 3.8 GMX2 SW SXUA/B SW Any SXU-C SW Any SXU-V SW 1.1
Other Data Other Units Tellabs 8100/8000 Manager Release 8.0 10.1A SP7 10.1A SP7 10.1A SP7 12 SP2 11 SP2 11 SP2 OMZ675 3.0 OMZ675 2.0 OMZ675 1.2 OMZ675 1.2 OMZ675 1.2 15A 14 SP3 13A SP5 13 13 9.0
SMZ430 SMZ414 SMZ414 SMZ414 SMZ611 UTZ549 UTZ549 DPZ652 DPZ652 DPZ652 DPZ652 DPZ652 SCZ281

38
10004_22 2005 Tellabs.
General
Basic Data Tellabs 8100 Network Elements SCP SCP SCP SCU SCU SCU-H SCU-H SCU-H SCU-H SCU-H SCU-H SCU-H SCU-H Base Units SCP211 SCP211 SCP211 SCU210 SCU210 SCU587/ SCM725 SCU587/ SCM725 SCU587/ SCM725 SCU587/ SCM725 SCU587/ SCM725 SCU587/ SCM725 SCU587/ SCM725 SCU587/ SCM725 HW Vers. 3.0 3.0 3.0 3.2/4.0 3.2/4.0 2.0 2.0 1.1 1.1 1.1 1.1 1.1 1.1 Unit SW USW Vers. 3.2 3.1 3.0 8.5 8.4 2.6 2.1 1.18 1.14 1.13 1.11 1.10 1.6 CCU SW -
Control Unit Data SCP SW 3.0 3.0 SCU SW 7.6 7.6 7.6 SCU-H SW XCG SW CXUM SW -
Cross-Connect Unit Data GMX SW Any Any Any Any Any Any Any Any GMX2 SW Any Any SXUA/B SW Any Any Any Any Any Any Any Any Any Any Any Any Any SXU-C SW Any Any Any Any Any Any Any Any Any Any Any Any Any SXU-V SW 1.1 1.1 1.1 1.1 1.1 1.1 1.1 1.1 1.1 -
Other Data Other Units Tellabs 8100/8000 Manager Release 9.0 9.0 9.0 8.0 8.0 10.1A SP3 10.1A SP3 10.1A SP3 10.1A SP3 10.1A SP3 10.1A SP3 10.1A SP3 10.1A SP3
SCZ281 SCZ281 SCZ281 SCZ280 SCZ280 SCZ545 SCZ545 SCZ545 SCZ545 SCZ545 SCZ545 SCZ545 SCZ545
10004_22 2005 Tellabs.

39
General
Basic Data Tellabs 8100 Network Elements SMH-U (Micro Node) STE-10M Base Units SMH502/ 503/505/506 STE790 HW Vers. 1.0 1.0 Unit SW USW Vers. 2.2 1.1 CCU SW -
Control Unit Data SCP SW SCU SW SCU-H SW XCG SW 3.5 CXUM SW -
Cross-Connect Unit Data GMX SW 4.1 GMX2 SW Any SXUA/B SW 10.5 SXU-C SW SXU-V SW -
Other Data Other Units Tellabs 8100/8000 Manager Release 9.0 14 SP6
SMZ533 SBZ792
STE-10M
STE790
1.0
SBZ792
1.0
3.5
4.1
10.5
STU-56 STU-160 STU-160 STU-160 STU-160 STU-160
STU325 STU315 STU315 STU315 STU315 STU315
1.0 5.0 5.0 5.0 4.0 4.0
SBZ388 SBZ385 SBZ385 SBZ385 SBZ385 SBZ385
1.1 2.2 2.1 2.0 1.8 1.7
DPZ794 1.1 SBZ670 4.0 OMZ675 2.0 OMH HW 1.0 EMZ642 1.10, ESU HW 1.0 SCO HW 3.0 DPZ794 1.0 SBZ670 4.0 OMZ675 2.0, OMH HW 1.0 EMZ642 1.9, ESU HW 1.0 SCO HW 3.0 IUM-5T/10T HW 1.0 UBZ436 2.3 UBZ436 2.3 UBZ436 2.3 UBZ436 2.3 UBZ436 2.3
14 SP3
9.0B 14 10.0A 10.0A 10.0A 10.0A

40
10004_22 2005 Tellabs.
General
Basic Data Tellabs 8100 Network Elements STU-160 STU-160

STU-320 STU-576 STU-1088-2W STU-2304 STU-320 STU-576 STU-1088-2W STU-2304
Control Unit Data Unit SW USW Vers. 1.6 1.5 1.3 CCU SW SCP SW SCU SW SCU-H SW XCG SW CXUM SW -
Other Data Other Units Tellabs 8100/8000 Manager Release 10.0A 10.0A 10.0
Base Units STU315 STU315 STU327 STU328 STU319 STU318 STU327 STU328 STU319 STU318 STU314 STU316 SXU212/ SXU218 SXU212/ SXU218 SXU212/ SXU218 SXU212/ SXU218 SXU212/ SXU218 SXU212/ SXU218 SXU212/ SXU218
HW Vers. 4.0 4.0 1.0/2.0
SBZ385 SBZ385 SBZ387
UBZ436 2.3 UBZ436 2.3 GMZ283 6.10 QMZ540 10.3 GMZ283 6.10 QMZ540 10.3 GMZ283 6.10
1.0/2.0
SBZ387
1.2
10.0
STU-1088 STU-2048 SXU-A/ SXU-B SXU-A/ SXU-B SXU-A/ SXU-B SXU-A/ SXU-B SXU-A/ SXU-B SXU-A/ SXU-B SXU-A/ SXU-B
1.0 5.0 5.0 5.0 5.0 5.0 5.0 5.0
SBZ384 SXZ282 SXZ282 SXZ282 SXZ282 SXZ282 SXZ282 SXZ282
1.4 10.6 10.5 10.4 10.3 10.2 10.1 10.0
Any Any Any Any Any Any Any
Any Any Any Any Any Any Any
1.6 1.6 1.6 1.6 1.6 1.6 1.6
10.6 10.5 10.4 10.3 10.2 10.1 10.0
9.0B 13A SP5 13A SP5 13A SP5 13A SP5
10004_22 2005 Tellabs.

41
General
Basic Data Tellabs 8100 Network Elements SXU-A/ SXU-B SXU-A/ SXU-B SXU-C SXU-C SXU-C SXU-C SXU-C SXU-V Base Units SXU212/ SXU218 SXU212/ SXU218 SXU212 SXU212 SXU212 SXU212 SXU212 SXU758 HW Vers. 4.1 4.1 5.0 5.0 4.1 4.1 4.1 1.0 Unit SW USW Vers. 6.9 6.8 10.2 10.0 2.12 2.11 2.10 2.1 CCU SW -
Control Unit Data SCP SW Any Any Any Any Any Any Any SCU SW Any Any Any Any Any Any Any SCU-H SW 1.6 1.6 1.11 1.11 1.11 1.11 1.11 1.10 XCG SW CXUM SW 2.10 2.10 2.10 2.10 2.10 -
Cross-Connect Unit Data GMX SW GMX2 SW SXUA/B SW 6.9 6.8 SXU-C SW 10.2 10.0 2.12 2.11 2.10 SXU-V SW 2.1
Other Data Other Units Tellabs 8100/8000 Manager Release
SXZ282 SXZ282 SXZ289 SXZ289 SXZ289 SXZ289 SXZ289 SXZ630
9.0B SP12 9.0B SP12 9.0B SP12 9.0B SP12 9.0B SP12 ESZ8003 1.8 CCZ539 5.4 GMZ283 10.1 QMZ540 10.5 IBZ610 1.0 ESZ8003 1.0 CCZ539 5.2 GMZ283 10.1 QMZ540 10.5 SXZ630 2.1 ESZ8002 1.1 CCZ539 5.4 GMZ283 10.1 QMZ540 10.5 IBZ610 1.0 12 SP2
SXU-V
SXU758
1.0
SXZ630
1.1
1.10
1.1
12 SP2
SXU-V
ESX717
1.0
ESZ8003
1.11
1.10
1.11
12 SP2

42
10004_22 2005 Tellabs.
General
Basic Data Tellabs 8100 Network Elements SXU-V Base Units ESX717 HW Vers. 1.0 Unit SW USW Vers. 1.10 CCU SW -
Control Unit Data SCP SW SCU SW SCU-H SW 1.10 XCG SW CXUM SW -
Cross-Connect Unit Data GMX SW GMX2 SW SXUA/B SW SXU-C SW SXU-V SW 1.10
ESZ8003
SXU-V
ESX717
1.0
ESZ8003
1.8
1.10
1.8
SXU-V
ESX717
1.0
ESZ8003
1.1
1.10
1.1
SXZ630 2.1 ESZ8002 1.1 CCZ539 5.4 GMZ283 10.1 QMZ540 10.5 IBZ610 1.0 SXZ630 2.1 ESZ8002 1.1 CCZ539 5.4 GMZ283 10.1 QMZ540 10.5 IBZ610 1.0 SXZ630 1.1 ESZ8002 1.1 CCZ539 5.2 GMZ283 10.1 QMZ540 10.5
12 SP2
12 SP2
VCM-5T-A/ VCM-10T-A VCM-5T-A/ VCM-10T-A VCM-5T-A/ VCM-10T-A VCM-5T-A/ VCM-10T-A VMM XCG
VCM222A/ VCM223A VCM222/ VCM223A VCM222/ VCM223A VCM222/ VCM223A VMM249 XCG525
4.1 4.1 4.0 3.03.1 1.0 2.2
VCZ285A VCZ285A VCZ285A VCZ285A VMZ295 SMZ538
10.2 10.1 10.0 2.14 1.3 3.5
Any -
Any Any Any Any Any -
1.6 1.6 1.6 1.6 1.6 -
Any -
Any Any Any Any -
Any -
5.4 5.4 5.4 5.4 6.9 -
Any -
1.1 1.1 GDH521/ GDH522 HW 1.1
10.1A 10.1A 10.1A 10.1A 8.0 12 SP1
10004_22 2005 Tellabs.

43
General
Basic Data Tellabs 8100 Network Elements XCG XCG XCG XCG XCG XCG Base Units XCG525 XCG525 XCG525 XCG525 XCG525 XCG525 HW Vers. 2.2 2.2 2.2 2.2 1.0 1.0 Unit SW USW Vers. 3.4 3.3 3.1 3.0 2.3 2.1 CCU SW -
Other Data Other Units Tellabs 8100/8000 Manager Release 12 SP1 12 SP1 12 SP1 11 SP1 9.0 9.0
SMZ538 SMZ538 SMZ538 SMZ538 SMZ538 SMZ538
GDH521/ GDH522 HW 1.1 GDH521/ GDH522 HW 1.1 GDH521/ GDH522 HW 1.1 GDH521/ GDH522 HW 1.1

44
10004_22 2005 Tellabs.
CAE Unit: CAZ287 Unit Software
2 CAE Unit: CAZ287 Unit Software

The software CAZ287 is used on the CAE unit in Tellabs 8150 basic, Tellabs 8160 A111 and Tellabs 8140 midi nodes.
2.1 Version 2.3

This is an unofficial version based on CAZ287 release r2.2 with only the CIF signalling parameter verification error fixed. This version should not be used once the next official version is available.
2.2 Version 2.2

Dependencies

Base unit must be version 2.0. SCU-H (SCZ545) software version must be 1.6 or higher. GMX (GMZ544) software version must be 3.8 or higher. SXU-A/B (SXZ282) software version must be 5.7 or higher. SXU-V (SXZ630) software version must be 1.1 or higher SCP (SCZ281) software can be any version SCU (SCZ280) software can be any version. XCG (SMZ538) ) software can be any version MartisDXX Manager support for this unit is available in Release 8.0 or higher.
Restrictions
No restrictions.
Bugs
The internal signalling parameter verification operates incorrectly. This error produces very short signalling bit errors about once in 15 sec in every channel.
10004_22 2008 Tellabs.

45
2.3 Version 2.1

Dependencies

Restrictions

Level supervision is not supported. X-Bus test port is not allocated. USW test object not supported (used by production testing).
Bugs

Locking object bug. Module conflict fault is set active even if module type is not defined. External groud mask value is not returned correctly (CSE251 modules). COMBO/ADPCM faults are activated incorrectly. Inventory operations do not affect hardware parameters. Interface object operates faulty (set fault mask) corrected (attribute is not set by NMS). Interface object allows change to coding parameter in a locked interface. XD IA is allocated even if not needed. Using signalling modules may in some cases disturb other units in the same node. Interface blocking fault is not monitored. Module types can not be read from unit when unit is not in inventory. In some load situations unit may reset (internal message buffers). The internal signalling parameter verification operates incorrectly. This error produces very short signalling bit errors about once in 15 sec in every channel.

46
10004_22 2008 Tellabs.
2.4 Version 2.0

Dependencies

Restrictions

Level supervision is not supported. X-Bus test port is not allocated. USW test object not supported (used by production testing). Does not use whole interface address allocation. This is needed because of a signalling data cross connect error in SXZ282.
Bugs

Locking object bug. Module conflict fault is set active even if module type is not defined. External groud mask value is not returned correctly (CSE251 modules). COMBO/ADPCM faults are activated incorrectly. Inventory operations do not affect hardware parameters. Interface object operates faulty (set fault mask) corrected (attribute is not set by NMS). Interface object allows change to coding parameter in a locked interface. XD IA is allocated even if not needed. Using signalling modules may in some cases disturb other units in the same node. Interface blocking fault is not monitored. Module types can not be read from unit when unit is not in inventory. In some load situations unit may reset (internal message buffers). XD IA is allocated with such parameters that SXZ282 can not operate correctly with it. Note that unrecoverable errors may occur if CAE has locked interfaces with allocated XD capacity when updating CAZ287 version 2.0 to 2.1 or later. The internal signalling parameter verification operates incorrectly. This error produces very short signalling bit errors about once in 15 sec in every channel.
10004_22 2008 Tellabs.

47
CCS-UNI and CCO-UNI Units: CCZ539 Unit Software
3 CCS-UNI and CCO-UNI Units: CCZ539 Unit Software

The software CCZ539 is used on CCS-UNI unit (whose base unit is PBU560) in the Tellabs 8140 midi, Tellabs 8150 basic and Tellabs 8160 A111 nodes. The version 5.8 can be downloaded to CCS-UNI units having the version 3.1 of PBU560.
3.1 Version 5.8

This version is only available for CCS-UNI. Enhancements and Fixed Bugs
Terminating calls to CCS-UNI lead to continuous cadence (CR ID 200011089).
Dependencies

CCS-UNI (base unit PBU560) hardware must be 3.1 or higher. SCP (SCZ281) software version must be 3.1 or higher (SCP unit is optional). SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.6 or higher while using CAS functionality. While using V5.2 functionality, SCU-H (SCZ545) software version must be 1.10 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMX (GMZ544) software version must be 3.17 or higher. SXU-A/B (SXZ282) software version can be any version. While using CAS functionality, SXU-V (SXZ630) software version must be 1.1 or higher. While using CAS functionality, SXU-V (ESZ8003) software version must be 1.1 or higher. While using V5.2 functionality, SXU-V (SXZ630) software version must be 2.1 or higher. While using V5.2 functionality, SXU-V (ESZ8003) software version must be 1.8 or higher. MartisDXX Manager support for V5.2 is available in Release 12 Service Pack 2 or higher. MartisDXX Manager support for new countries (CRF ID 4005109) is available in Release 12A Service Pack 3 or higher.
Restrictions

PCM coding and decoding are only according to A-law, -law is not supported. If v1.0 of CCS-UNI is replaced with this version, interface parameters in the Tellabs 8100 manager database should be updated from hardware to remove a consistency check failure.

48
10004_22 2008 Tellabs.
Bugs
No known bugs.
3.2 Version 5.7

This version is only available for CCS-UNI. Enhancements and Fixed Bugs

Reduced battery pulsing too slow fixed. Malaysia V5.2 settings changed. Mexico1 V5.2 settings changed.
Dependencies

Restrictions

Bugs
No known bugs.
10004_22 2008 Tellabs.

49
3.3 Version 5.4

This version is only available for CCS-UNI. This is a non-production version based on version 5.2. Enhancements and Fixed Bugs
CCS-UNI: Incorrect reference point. (CRF ID 4004974). With some gain values (down gain = -5dB - -24.9dB, up attenuation > -1.5dB) speech channel is over damped (13dB extra damping). No dial tone after SXU-V switch over. (CRF ID 4005077). When there is a switch over between SXU-Vs, phones that are off hook will not receive dial tone until they go on hook and off hook. CCS-UNI problems when rising interface state. (CRF ID 4005162). CCS-UNI v5.4 doesn't really change gain settings when using freely selectable gain values. Gain values must be set to fixed list values before using freely selectable values. CCS-UNI Country support. (CRF ID 4005109). Currently supported countries are: Finland, Denmark, Germany, United Kingdom, Sweden, Chile, South Africa, Mexico, Spain, Brazil, Ireland, Argentina, Malaysia, Mexico2, Mexico3, India, Hungary and Austria. Productional improvements (CRF ID 4005124). X-bus switch-over problem in CCS-UNI (CRF ID 4005322): when switchover from Xbus1 to Xbus2 occurs in SXU-V in switch node, CCS-UNI can't communicate with SXU-V via TV5-channel anymore.
Dependencies


50
10004_22 2008 Tellabs.
Restrictions

Bugs
No known bugs.
3.4 Version 5.2

This version is only available for CCS-UNI. Enhancements and Fixed bugs

Production test phase is enhanced by removing unnecessary faults in test setup. V5.2 TV5 support, interrupt handler hang-up causes unit reset in V5.2 use. (CRF ID 4004530) There is an IN USE group operation failure on CCS-UNI while doing a large amount of changes. (CRF ID 4004506) A change of the unit version in a subrack results in an interface parameter corruption. (CRF ID 4004239) On CCS-UNI the port unlocking is possible even though a port contains circuits/crossconnections with the Service Computer. (CRF ID 4003704)
Dependencies

CCS-UNI (base unit PBU560) hardware version must be 3.1. SCP (SCZ281) software version must be 3.1 or higher (SCP unit is optional). SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMX (GMZ544) software version must be 3.17 or higher. SXU-A/B (SXZ282) software version can be any version. SXU-V (SXZ630) software version must be 1.1. SXU-V (ESZ8003) software version must be 1.1. MartisDXX Manager support for V5.2 is available in Release 12A Service Pack 2 or higher.
10004_22 2008 Tellabs.

51
Restrictions

Bugs
No known bugs.
3.5 Version 5.1

This version is a test version only for CCS-UNI. Enhancements and Fixed Bugs
The unit hanging problem in interface blocking and unblocking is solved.
Dependencies

CCS-UNI (base unit PBU560) hardware version must be 3.1. SCP (SCZ281) software version must be 3.1 or higher (SCP unit is optional). SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMX (GMZ544) software version must be 3.17 or higher. SXU-A/B (SXZ282) software version can be any version. SXU-V (SXZ630) software version must be 1.1. MartisDXX Manager support for V5.2 is available in Release 12 Service Pack 2 or higher.
Restrictions

PCM coding and decoding are only according to A-law, -law is not supported. In case v1.0 of CCS-UNI is replaced with this version, interface parameters in the Tellabs 8100 manager database should be updated from hardware to remove a consistency check failure.
Bugs
No known bugs.

52
10004_22 2008 Tellabs.
3.6 Version 5.0

This is an internal test version based on version 2.0 only for CCS-UNI. Enhancements and Fixed Bugs

V5.2 TV5 support, interrupt handler hang-up causes unit reset in V5.2 use. (CRF ID 4004530) There is an IN USE group operation failure on CCS-UNI while doing a large amount of changes. (CRF ID 4004506) A change of the unit version in a subrack results in an interface parameter corruption. (CRF ID 4004239) On CCS-UNI the port unlocking is possible even though a port contains circuits/crossconnections with the Service Computer. (CRF ID 4003704)
Dependencies

CCS-UNI (base unit PBU560) hardware version must be 3.1. SCP (SCZ281) software version must be 3.1 or higher (SCP unit is optional). SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMX (GMZ544) software version must be 3.17 or higher. SXU-A/B (SXZ282) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit/interface card is available in Release 10.1A Service Pack 7 or Release 11 Service Pack 1 or higher.
Restrictions

PCM coding and decoding are only according to A-law, -law is not supported. In case v1.0 of CCS-UNI is replaced with this version, interface parameters in the Tellabs 8100 manager database should be updated from hardware to remove a consistency check failure.
Bugs
The unit may hang if flash memory copying starts while blocking or unblocking an interface.
10004_22 2008 Tellabs.

53
3.7 Version 4.0

This version is only available for CCS-UNI. Dependencies

CCS-UNI (base unit PBU560) hardware version must be 3.1. SCP (SCZ281) software version must be 3.1 or higher (SCP unit is optional). SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMX (GMZ544) software version must be 3.17 or higher. SXU-A/B (SXZ282) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit/interface card is available in Release 10.1A Service Pack 7 or Release 11 Service Pack 1 or higher.
Restrictions
PCM coding and decoding are only according to A-law, -law is not supported.
Bugs
Version 1.0 cannot be directly replaced with this version.
3.8 Version 2.0

This version is available for CCS-UNI and CCO-UNI hardware product version 2.0. Dependencies

CCS-UNI and CCO-UNI (base unit PBU560) hardware version must be 2.0. CCO555 and CCS554 hardware versions must be at least 2.0. SCP (SCZ281) software version must be 3.1 or higher (SCP unit is optional). SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. SXU-A/B (SXZ282) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher.

54
10004_22 2008 Tellabs.
MartisDXX Manager support for this unit/interface card is available in Release 10.1A Service Pack 1 or Release 11 Service pack 1 or higher.
Restrictions

PCM coding and decoding are only according to A-law, -law is not supported. CCZ359 2.0 is designed mainly to adopt South-African POTS interface specifications into the units. Other countries will be supported in MartisDXX Manager Release 11 Service Pack 2.
Bugs

The application can be disabled. Version 1.0 cannot be directly replaced with this version.
3.9 Version 1.0

This version is available for CCS-UNI and CCO-UNI hardware product version 1.0. Dependencies

CCS-UNI and CCO-UNI (base unit PBU560) hardware version must be 1.0. SCP (SCZ281) software version must be 3.1 or higher (SCP unit is optional). SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. SXU-A/B (SXZ282) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit/interface card is available in Release 10.1A or higher.
Restrictions

PCM coding and decoding are only according to A-law, -law is not supported. CCZ539 v1.0 does not support Mercury signalling.
Bugs

The application can be disabled. The interface can be unlocked even if it is cross-connected.
10004_22 2008 Tellabs.

55
CCU Unit: SCZ286 Unit Software
4 CCU Unit: SCZ286 Unit Software

The software SCZ286 is used on CCU units. The channel test functions or the shortcut control channels are not supported because CCU is not physically connected to the cross-connection bus in the master subrack of the Tellabs 8170 cluster node. The version 2.7 can be downloaded to CCU units having the version 2.y of SCZ286 (where y=0, 1, 2...).
4.1 Version 2.7

Enhancements
The problem preventing CCU inventory operations has been fixed. The GCI (General Command Interpreter) will now accept the special void messages sent during those operations. (CR ID 200031024)
Dependencies

CCU (base unit SCU210) hardware version must be 4.0 or higher to support the PFU-A and PFU-B generated signal to detect the power off situation. CXU-M (SXZ288) software version can be any version. MartisDXX Manager support for CCU is available in release 10.1A or higher.
Restrictions
In the particular case that power of the main master shelf fails (where the control circuit card resides) of the Tellabs 8170 cluster node, this generates the loss of service for all the node. If this problem occurs, all the links will be lost.
Bugs
No known bugs.

56
10004_22 2008 Tellabs.
4.2 Version 2.6

Enhancements

The switch-over has been optimized and it happens faster. The effect on traffic is essentially smaller. (CR ID 200013068) The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) have check for internal structure of envelope messages. (CR ID 200013489) Two fault conditions have been fixed. 1) A bug in testing for fault "Delay has increased" has been fixed. In the case of missing CXU-M or software download this delta fault does not any more repeat itself continuously and fill the CCU fault history. Only a successful unit poll with a long delay will activate this delta fault. 2) The "Switch-over has happened because of long delay" fault operated erroneously. In the case of active forced mode when switch over can not happen this fault was activated erroneously. This bug in now fixed. (CR ID 200013759)
Dependencies

Restrictions
In the particular case that power of the main master shelf fails (where the control circuit card resides) of the Tellabs 8170 cluster node, this generates the loss of service for all the node. If this problem occurs, all the links will be lost.
Bugs
The inventory add and delete operations for CCU unit are impossible. An installed (upgraded) CCU with ESW version 2.6 will otherwise operate normally. (CR ID 200031024)
10004_22 2008 Tellabs.

57
4.3 Version 2.5

Enhancements
The CXU-M in slot 31 is PRIMARY parameter and CXU-M Secondary Active fault for CCU in SCZ286 have been added. This alarm shows whether the Tellabs 8170 cluster node is using the upper or lower shelf of the node. A delta alarm (CXU-M in slot 15 Active and CXU-M in slot 31 Active) for each change-over of the cross-connection system has been added. PFU-A and PFU-B provide a signal for detecting the power off situation. The new SCU hardware version 4.0 will support this (ON/OFF) signal.
Dependencies

Restrictions

The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) do not check the internal structure of envelope messages. The switch-over has not been optimized. In the particular case that power of the main master shelf fails (where the control circuit card resides) of the Tellabs 8170 cluster node, this generates the loss of service for all the node. If this problem occurs, all the links will be lost.
Bugs
Two faults operate incorrectly. 1) There is a bug in testing for fault "Delay has increased". In the case of missing CXU-M or software download this delta fault repeats itself continuously and fills the CCU fault history. 2) The "Switch-over has happened because of long delay" fault operates erroneously. In the case of active forced mode when switch over can not happen this fault is activated erroneously.

58
10004_22 2008 Tellabs.
4.4 Version 2.4

This is an unofficial version based on SCZ286 version 2.2 with a bug fix for the CRF ID 4002472. This version should not be used once the official version 2.5 is available. Restrictions

The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) do not check the internal structure of envelope messages. The switch-over has not been optimized. Does not support the faults Delay increased and Switchover has happened because of long delay. In the particular case that power of the main master shelf fails (where the control circuit card resides) of the Tellabs 8170 cluster node, this generates the loss of service for all the node. If this problem occurs, all the links will be lost.
Bugs
No known bugs.
4.5 Version 2.2

Restrictions

The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) do not check the internal structure of envelope messages. The switch-over has not been optimized. Does not support the faults Delay increased and Switchover has happened because of long delay. PFU-A/PFU-B power off alarm in SCU/CCU is not supported. Maintenance event alarm (MEI) for active CXU-M switchover is not supported. In the particular case that power of the main master shelf fails (where the control circuit card resides) of the Tellabs 8170 cluster node, this generates the loss of service for all the node. If this problem occurs, all the links will be lost.
Bugs

Activity state error in Tellabs 8170 cluster node CXU-M units; In some cases the CXU-M units in Tellabs 8170 cluster node adopt wrong activity role compared to the CCU protection parameters and SXU-C states. If the node ends up in this state, essential node operations may be disabled. Longer timeout when polling CXU-M;
10004_22 2008 Tellabs.

59
The timeout CCU needs when polling CXU-M has been changed from 2 seconds to 4 seconds. Also two new faults were implemented to show in 3 seconds a warning that timeout has been increased and in 4 seconds that switchover to the protective CXU-M had happened because of timeout. (CRF ID 4002472)
4.6 Version 2.1

Restrictions

The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) do not check the internal structure of envelope messages. The switch-over has not been optimized. Does not support the faults Delay increased and Switchover has happened because of long delay. The clock direction options for the synchronous SCC interface are not supported. The optional security management for the SC interface is not supported. PFU-A/PFU-B power off alarm in SCU/CCU is not supported. Maintenance event alarm (MEI) for active CXU-M switchover is not supported. In the particular case that power of the main master shelf fails (where the control circuit card resides) of the Tellabs 8170 cluster node, this generates the loss of service for all the node. If this problem occurs, all the links will be lost.
Bugs

Activity state error in Tellabs 8170 cluster node CXU-M units; In some cases the CXU-M units in Tellabs 8170 cluster node adopt wrong activity role compared to the CCU protection parameters and SXU-C states. If the node ends up in this state, essential node operations may be disabled. Longer timeout when polling CXU-M; The timeout CCU needs when polling CXU-M has been changed from 2 seconds to 4 seconds. Also two new faults were implemented to show in 3 seconds a warning that timeout has been increased and in 4 seconds that switchover to the protective CXU-M had happened because of timeout. (CRF ID 4002472)

60
10004_22 2008 Tellabs.
4.7 Version 2.0

Restrictions

Bugs

The unit cannot copy the settings for the SCL415 options from the backup settings to its own use when the unit is replaced. Activity state error in Tellabs 8170 cluster node CXU-M units; In some cases the CXU-M units in Tellabs 8170 cluster node adopt wrong activity role compared to the CCU protection parameters and SXU-C states. If the node ends up in this state, essential node operations may be disabled. Longer timeout when polling CXU-M; The timeout CCU needs when polling CXU-M has been changed from 2 seconds to 4 seconds. Also two new faults were implemented to show in 3 seconds a warning that timeout has been increased and in 4 seconds that switchover to the protective CXU-M had happened because of timeout. (CRF ID 4002472)
10004_22 2008 Tellabs.

61
4.8 Version 1.5

Restrictions

Bugs

The unit cannot copy the settings for the SCL415 options from the backup settings to its own use when the unit is replaced. The network layer protocol software cannot handle all illegal routing elements. The LLC3 protocol software cannot handle one exceptional case associated with negative acknowledgement. These two communication problems are not likely to happen but they can cause a deadlock in the communication system CCU. The asynchronous protocol software does not work correctly with heavy full-duplex traffic. Activity state error in Tellabs 8170 cluster node CXU-M units; In some cases the CXU-M units in Tellabs 8170 cluster node adopt wrong activity role compared to the CCU protection parameters and SXU-C states. If the node ends up in this state, essential node operations may be disabled. Longer timeout when polling CXU-M; The timeout CCU needs when polling CXU-M has been changed from 2 seconds to 4 seconds. Also two new faults were implemented to show in 3 seconds a warning that timeout has been increased and in 4 seconds that switchover to the protective CXU-M had happened because of timeout. (CRF ID 4002472)

62
10004_22 2008 Tellabs.
4.9 Version 1.4

Restrictions

The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) do not check the internal structure of envelope messages. The switch-over has not been optimized. Does not support the faults Delay increased and Switchover has happened because of long delay. Does not support the alarm interface module SCL415. The clock direction options for the synchronous SCC interface are not supported. The optional security management for the SC interface is not supported. PFU-A/PFU-B power off alarm in SCU/CCU is not supported. Maintenance event alarm (MEI) for active CXU-M switchover is not supported. In the particular case that power of the main master shelf fails (where the control circuit card resides) of the Tellabs 8170 cluster node, this generates the loss of service for all the node. If this problem occurs, all the links will be lost.
Bugs

The unit cannot copy the settings for the SCL415 options from the backup settings to its own use when the unit is replaced. The network layer protocol software cannot handle all illegal routing elements. The LLC3 protocol software cannot handle one exceptional case associated with negative acknowledgement. These two communication problems are not likely to happen but they can cause a deadlock in the communication system CCU. The asynchronous protocol software does not work correctly with heavy full-duplex traffic. Activity state error in Tellabs 8170 cluster node CXU-M units; In some cases the CXU-M units in Tellabs 8170 cluster node adopt wrong activity role compared to the CCU protection parameters and SXU-C states. If the node ends up in this state, essential node operations may be disabled. Longer timeout when polling CXU-M; The timeout CCU needs when polling CXU-M has been changed from 2 seconds to 4 seconds. Also two new faults were implemented to show in 3 seconds a warning that timeout has been increased and in 4 seconds that switchover to the protective CXU-M had happened because of timeout. (CRF ID 4002472)
10004_22 2008 Tellabs.

63
CXU-M Unit: SXZ288 Unit Software
5 CXU-M Unit: SXZ288 Unit Software

The unit software SXZ288 is used on the cross-connection unit CXU-M in Tellabs 8170 cluster master subracks.
5.1 Version 10.6

Enhancements and Fixed Bugs

SCU or SCU-H reset in slave subrack does not any more cause cluster node switch over. (CR ID 300107078) The Fallback List Warning fault can be enabled by setting the use master clock quality levels parameter to disabled state. (CR ID 300067522) The handling of flash list record status has been corrected. (CR ID 300091551) Dependencies
CXU-M (base unit SXU212) hardware version must be 5.0 or higher. CCU (SCZ286) software version can be any version. SXU-C (SXZ289) software version must be 2.10 or higher. MartisDXX Manager support for priority bumping functionality is available in Release 9.0B Service Pack 12 or higher. Restrictions
No restrictions. Bugs
No known bugs.
5.2 Version 10.5

This is an unofficial version based on SXZ288 version 10.4.

64
10004_22 2008 Tellabs.
5.3 Version 10.4


Wrong fault mapping concerning the faults Loss of External Clock, Phase Locked Loop Alarm and External Clock Warning has been fixed. (CR ID 300023465) Fallback List Warning fault has been restored. This Fault can be enabled or disabled with master clock quality level enable. (CR ID 300062665) Dependencies
SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The time difference in the slave status polling between the primary and secondary sides may be several seconds. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The problem is more probable with SCU-H than with SCU as it has a longer startup time. (CR ID 300107078) Fallback list warning fault enable polarity is wrong. (CR ID 300067522) An invalid flash list record status may cause a problem in the node even though the record status error is very improbable. (CR ID 300091551)
5.4 Version 10.3

The problem preventing CXU-M inventory operations has been fixed. The GCI (General Command Interpreter) will now accept the special void messages sent during those operations. (CR ID 200031025) Master clock RAI support has been fixed. (CR ID 200036673)
10004_22 2008 Tellabs.

65
Dependencies

SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The time difference in the slave status polling between the primary and secondary sides may be several seconds. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The problem is more probable with SCU-H than with SCU as it has a longer startup time. (CR ID 300107078) An invalid flash list record status may cause a problem in the node even though the record status error is very improbable. (CR ID 300091551) Wrong fault activation bug concerning the faults Loss of External Clock, Phase Locked Loop Alarm and External Clock Warning (CR ID 300023465).
5.5 Version 10.2

The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) message envelope structure is verified before the message is executed. This reduces the probability of problems followed by possibly corrupted message. (CR ID 200012825) The detection time of missing SXU-C unit has been reduced by code optimization. (CR ID 200013179) The cross-connect memory background verification (MXA monitoring) is now active as default. Previously the verification was off as default. (CR ID 200013327) The cross-connect memory background verification (MXA monitoring) is now capable of handling also SCP ports. (CR ID 200004877) A CXU-S card that exists in the subrack inventory but is either physically missing or initializing in the active side now causes a switch-over. (CR ID 200012002) When CXU-M sends the state of the used clock source to the interface units, the state value of the clock source data is not any more set to NOT_OK (255) if the used clock is internal and the FBL is not empty. After this modification the neighbour node can apply the defined QL of the internal clock correctly. (CR ID 200013488)

66
10004_22 2008 Tellabs.
"Fallback list warning" faults are not anymore generated. These have been replaced with "Faulty clock source of choice n" faults. The same change has already earlier been done to Tellabs 8160 A111/GMX, XCG, SXU-A and SXU-B. (CR ID 200005248) Memory overflow problem in master clock software module has been fixed. (CR ID 200005090)
Dependencies

CXU-M (base unit SXU212) hardware version must be 5.0 or higher. CCU (SCZ286) software version can be any version. SXU-C (SXZ289) software version must be 2.10 or higher. MartisDXX Manager support for priority bumping functionality is available in Release 9.0B Service Pack 12 or higher.
Restrictions
No restrictions.
Bugs
SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The time difference in the slave status polling between the primary and secondary sides may be several seconds. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The problem is more probable with SCU-H than with SCU as it has a longer startup time. (CR ID 300107078) An invalid flash list record status may cause a problem in the node even though the record status error is very improbable. (CR ID 300091551) Wrong fault activation bug concerning the faults Loss of External Clock, Phase Locked Loop Alarm and External Clock Warning (CR ID 300023465). CXU-M unit can not be added in or removed from the node inventory. The GCI (General Command Interpreter) message verification does not accept the special void messages sent by Tellabs 8100 network manager during those operations. This problem does not have any effect on the CXU-M units in operative state. This problem only concerns versions 10.2 and 2.13. (CR ID 200031025) Master clock RAI does not operate. (CR ID 200036673)
5.6 Version 10.1

Dependencies

CXU-M (base unit SXU212) hardware version must be 5.0 or higher. CCU (SCZ286) software version can be any version. SXU-C (SXZ289) software version must be 2.10 or higher. MartisDXX Manager support for priority bumping functionality is available in Release 9.0B Service Pack 12 or higher.
10004_22 2008 Tellabs.

67
Restrictions

The detection time of missing SXU-C unit has not been optimized. The Fall Back List Warning fault exists in the faults list. The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) are not able to detect possible internal errors in message envelope structure. The cross-connect memory background verification (MXA monitoring) is not active as default.
Bugs
SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The time difference in the slave status polling between the primary and secondary sides may be several seconds. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The problem is more probable with SCU-H than with SCU as it has a longer startup time. (CR ID 300107078) An invalid flash list record status may cause a problem in the node even though the record status error is very improbable. (CR ID 300091551) When CXU-M sends the state of the used clock source to the interface units, the state value of the clock source data is set to NOT_OK (255) if the used clock is internal and the FBL is not empty and therefore the neighbour node does not apply the defined QL of the internal clock correctly. (CR ID 200013488) A CXU-S card that exists in the subrack inventory but is either physically missing or initializing in the active side does not cause a switch-over. The cross-connect memory background verification (MXA monitoring) produces invalid and repeating fault indication if there is a certain port type in some of the slaves (SCP control channel port) and the extended check mode is activated. Note that the verification process is not executing if it is not explicitly activated. Memory overflow problem in master clock software module.
5.7 Version 10.0

Dependencies

CXU-M (base unit SXU212) hardware version must be 5.0. MartisDXX Manager support for priority bumping functionality is available in Release 9.0B Service Pack 12 or higher.
Restrictions

The detection time of missing SXU-C unit has not been optimized. The Fall Back List Warning fault exists in the faults list. The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) are not able to detect possible internal errors in message envelope structure. Does not support background verification of CXU-A cross-connect memory.

68
10004_22 2008 Tellabs.
Does not support the enhanced Asic Latch Warning fault monitoring. Erroneous warnings can be seen as the test method is too sensitive. Does not support indication of faulty intersubrack cable installation in fault history. Both SXU-C and CXU-M must support this feature before the fault can be detected.
Bugs
SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The time difference in the slave status polling between the primary and secondary sides may be several seconds. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The problem is more probable with SCU-H than with SCU as it has a longer startup time. (CR ID 300107078) An invalid flash list record status may cause a problem in the node even though the record status error is very improbable. (CR ID 300091551) When CXU-M sends the state of the used clock source to the interface units, the state value of the clock source data is set to NOT_OK (255) if the used clock is internal and the FBL is not empty and therefore the neighbour node does not apply the defined QL of the internal clock correctly. (CR ID 200013488) A CXU-S card that exists in the subrack inventory but is either physically missing or initializing in the active side does not cause a switch-over. MXA monitoring (CXU-A memory background check) does not operate properly if there are SCP control channel ports. The connections created for those ports will become inoperable after monitoring has been activated with auto fix option. This happens because the used port type is not properly handled. There are two GMM-related problems in the node master clock selection. 1) If the fallback list contains three or more clocks from the same subrack and the current MCL becomes faulty, the next choices (GMM) status is temporarily marked in fail state and the fourth choice is selected instead for the SYB. After a while the GMM state is properly updated and it is selected in the SYB bus. 2) If the node clock fails and the next choice is GMM, the node may temporarily start using the internal clock. After a while the node starts to use the valid GMM as MCL. During CXU-M initialization the fault Clock Failure Switch Over may unnecessarily be activated for a short time period. This may lead to one switch-over when both CXU-M units are initializing at the same time. In stable state invalid activation is not possible. It takes about 4 seconds too long before the node starts using an external clock after holdover state. When CXU-M receives 1001th X-Group ID activation command after unit initialization, there is a problem updating the internal X-Group RAM database and this may lead to reset in all the slaves on the same side regardless of whether the CXU-M unit is in the active or passive side. The primary reason for the slave resets is the RAM list monitoring. If the master is not able to update its own list properly while the slaves are, the result is a checksum mismatch. It is however very unlikely that the number of activations would reach a very large number. X-Group IDs are used in swap circuit and time controlled circuit applications.
10004_22 2008 Tellabs.

69
5.8 Version 2.17


SCU or SCU-H reset in slave subrack does not any more cause cluster node switch over. (CR ID 300107078) The Fallback List Warning fault can be enabled by setting the use master clock quality levels parameter to disabled state. (CR ID 300067522) The handling of flash list record status has been corrected. (CR ID 300091551)
Dependencies

CXU-M (base unit SXU212) hardware version must be lower than 5.0. CCU (SCZ286) software version can be any version. SXU-C (SXZ289) software version must be 2.10 or higher. MartisDXX Manager support for priority bumping functionality is available in Release 9.0B Service Pack 12 or higher.
Restrictions
No restrictions.
Bugs
No known bugs.
5.9 Version 2.16

This is an unofficial version based on SXZ288 version 2.15.
5.10 Version 2.15


Wrong fault mapping concerning the faults Loss of External Clock, Phase Locked Loop Alarm and External Clock Warning has been fixed. (CR ID 300023465) Fallback List Warning fault has been restored. This Fault can be enabled or disabled with master clock quality level enable. (CR ID 300062665)

70
10004_22 2008 Tellabs.
Dependencies

Restrictions
No restrictions.
Bugs
SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The time difference in the slave status polling between the primary and secondary sides may be several seconds. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The problem is more probable with SCU-H than with SCU as it has a longer startup time. (CR ID 300107078) Fallback list warning fault enable polarity is wrong. (CR ID 300067522) An invalid flash list record status may cause a problem in the node even though the record status error is very improbable. (CR ID 300091551)
5.11 Version 2.14

The problem preventing CXU-M inventory operations has been fixed. The GCI (General Command Interpreter) will now accept the special void messages sent during those operations. (CR ID 200031025) Master clock RAI support has been fixed. (CR ID 200036673) Downloading software in the CXU-M unit in the lower shelf is possible. (CR ID 200036481)
Dependencies

Restrictions
No restrictions.
10004_22 2008 Tellabs.

71
Bugs
SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The time difference in the slave status polling between the primary and secondary sides may be several seconds. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The problem is more probable with SCU-H than with SCU as it has a longer startup time. (CR ID 300107078) An invalid flash list record status may cause a problem in the node even though the record status error is very improbable. (CR ID 300091551) Wrong fault activation bug concerning the faults Loss of External Clock, Phase Locked Loop Alarm and External Clock Warning (CR ID 300023465).
5.12 Version 2.13

The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) message envelope structure is verified before the message is executed. This reduces the probability of problems followed by possibly corrupted message. (CR ID 200012825) The detection time of missing SXU-C unit has been reduced by code optimization. (CR ID 200013179) The cross-connect memory background verification (MXA monitoring) is now active as default. Previously the verification was off as default. (CR ID 200013329) The cross-connect memory background verification (MXA monitoring) is now capable of handling also SCP ports. (CR ID 200004877) A CXU-S card that exists in the subrack inventory but is either physically missing or initializing in the active side now causes a switch-over. (CR ID 200012002) When CXU-M sends the state of the used clock source to the interface units, the state value of the clock source data is not any more set to NOT_OK (255) if the used clock is internal and the FBL is not empty. After this modification the neighbour node can apply the defined QL of the internal clock correctly. (CR ID 200013488) "Fallback list warning" faults are not anymore generated. These have been replaced with "Faulty clock source of choice n" faults. The same change has already earlier been done to Tellabs 8160 A111/GMX, XCG, SXU-A and SXU-B. (CR ID 200005248) The problem related with the 1001th X-Group ID activation command in CXU-M has been fixed. (CR ID 200004868) Memory overflow problem in master clock software module has been fixed. (CR ID 200005090)

72
10004_22 2008 Tellabs.
Dependencies

Restrictions
No restrictions.
Bugs
SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The time difference in the slave status polling between the primary and secondary sides may be several seconds. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The problem is more probable with SCU-H than with SCU as it has a longer startup time. (CR ID 300107078) An invalid flash list record status may cause a problem in the node even though the record status error is very improbable. (CR ID 300091551) Wrong fault activation bug concerning the faults Loss of External Clock, Phase Locked Loop Alarm and External Clock Warning (CR ID 300023465). CXU-M unit can not be added in or removed from the node inventory. The GCI (General Command Interpreter) message verification does not accept the special void messages sent by Tellabs 8100 network manager during those operations. This problem does not have any effect on the CXU-M units in operative state. This problem only concerns versions 10.2 and 2.13. (CR ID 200031025) Master clock RAI does not operate. (CR ID 2000) Downloading software in the CXU-M unit in the lower shelf may be unsuccesfull. (CR ID 200036481)
5.13 Version 2.12

Dependencies

10004_22 2008 Tellabs.

73
Restrictions

The detection time of missing SXU-C unit has not been optimized. The Fall Back List Warning fault exists in the faults list. The cross-connect memory background verification (MXA monitoring) is not active as default. The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) are not able to detect possible internal errors in message envelope structure. Holdover mode of the master clock is not supported. Does not support indication of faulty intersubrack cable installation in fault history. Both SXU-C and CXU-M must support this feature before the fault can be detected.
Bugs
SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The time difference in the slave status polling between the primary and secondary sides may be several seconds. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The problem is more probable with SCU-H than with SCU as it has a longer startup time. (CR ID 300107078) An invalid flash list record status may cause a problem in the node even though the record status error is very improbable. (CR ID 300091551) Downloading software in the CXU-M unit in the lower shelf may be unsuccesfull. (CR ID 200036481) When CXU-M sends the state of the used clock source to the interface units, the state value of the clock source data is set to NOT_OK (255) if the used clock is internal and the FBL is not empty and therefore the neighbour node does not apply the defined QL of the internal clock correctly. (CR ID 200013488) A CXU-S card that exists in the subrack inventory but is either physically missing or initializing in the active side does not cause a switch-over. The cross-connect memory background verification (MXA monitoring) produces invalid and repeating fault indication if there is a certain port type in some of the slaves (SCP control channel port) and the extended check mode is activated. Note that the verification process is not executing if it is not explicitly activated. Memory overflow problem in master clock software module. During CXU-M initialization the fault Clock Failure Switch Over may unnecessarily be activated for a short time period. This may lead to one switch-over when both CXU-M units are initializing at the same time. In stable state invalid activation is not possible. When CXU-M receives 1001th X-Group ID activation command after unit initialization, there is a problem updating the internal X-Group RAM database and this may lead to reset in all the slaves on the same side regardless of whether the CXU-M unit is in the active or passive side. The primary reason for the slave resets is the RAM list monitoring. If the master is not able to update its own list properly while the slaves are, the result is a checksum mismatch. It is however very unlikely that the number of activations would reach a very large number. X-Group IDs are used in swap circuit and time controlled circuit applications.

74
10004_22 2008 Tellabs.
5.14 Version 2.10

Dependencies

CXU-M (base unit SXU212) hardware version must be lower than 5.0. MartisDXX Manager support for priority bumping functionality is available in Release 9.0B Service Pack 12 or higher.
Restrictions

The detection time of missing SXU-C unit has not been optimized. The Fall Back List Warning fault exists in the faults list. The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) are not able to detect possible internal errors in message envelope structure. Does not support background verification of CXU-A cross-connect memory. Does not support the enhanced Asic Latch Warning fault monitoring. Erroneous warnings can be seen as the test method is too sensitive. Holdover mode of the master clock is not supported. Does not support indication of faulty intersubrack cable installation in fault history. Both SXU-C and CXU-M must support this feature before the fault can be detected. During CXU-M initialization the fault Clock Failure Switch Over may unnecessarily be activated for a short time period. This may lead to one switch-over when both CXU-M units are initializing at the same time. In stable state invalid activation is not possible.
Bugs
SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The time difference in the slave status polling between the primary and secondary sides may be several seconds. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The problem is more probable with SCU-H than with SCU as it has a longer startup time. (CR ID 300107078) An invalid flash list record status may cause a problem in the node even though the record status error is very improbable. (CR ID 300091551) When CXU-M sends the state of the used clock source to the interface units, the state value of the clock source data is set to NOT_OK (255) if the used clock is internal and the FBL is not empty and therefore the neighbour node does not apply the defined QL of the internal clock correctly (CR ID 200013488). A CXU-S card that exists in the subrack inventory but is either physically missing or initializing in the active side does not cause a switch-over. There are two GMM-related problems in the node master clock selection. 1) If the fallback list contains three or more clocks from the same subrack and the current MCL becomes faulty, the next choices (GMM) status is temporarily marked in fail state and the fourth choice is selected instead for the SYB. After a while the GMM state is properly updated and it is selected in the SYB bus.
10004_22 2008 Tellabs.

75
2) If the node clock fails and the next choice is GMM, the node may temporarily start using the internal clock. After a while the node starts to use the valid GMM as MCL.
When CXU-M receives 1001th X-Group ID activation command after unit initialization, there is a problem updating the internal X-Group RAM database and this may lead to reset in all the slaves on the same side regardless of whether the CXU-M unit is in the active or passive side. The primary reason for the slave resets is the RAM list monitoring. If the master is not able to update its own list properly while the slaves are, the result is a checksum mismatch. It is however very unlikely that the number of activations would reach a very large number. X-Group IDs are used in swap circuit and time controlled circuit applications.
5.15 Version 2.9

This is an unofficial version almost equal to SXZ288 version 2.10. This version does not include a bug fix for the master clock ASIC configuration problem. ASIC is temporarily configured incorrectly when the new clock interface frequency differs from the previous frequency and the change happens suddenly (interrupt). This version should not be used once the official version 2.10 is available.
5.16 Version 2.8

This is an unofficial version based on SXZ288 version 2.7 with a bug fix only for the swap circuit unidirectional connection problem. This version should not be used once the official version 2.10 is available.
5.17 Version 2.7

Dependencies
CXU-M base unit SXU212 version must be lower than 5.0.
Restrictions

The detection time of missing SXU-C unit has not been optimized. The Fall Back List Warning fault exists in the faults list. The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) are not able to detect possible internal errors in message envelope structure. Does not support background verification of CXU-A cross-connect memory. Does not support the enhanced Asic Latch Warning fault monitoring. Erroneous warnings can be seen as the test method is too sensitive. Does not indicate the used fallback list entry in the fault history.

76
10004_22 2008 Tellabs.
Does not support the new external clock protection system (switch-over happens only after all other possible valid choices have failed and the next choice would be the node internal clock). Holdover mode of the master clock is not supported. Does not support indication of faulty intersubrack cable installation in fault history. Both SXU-C and CXU-M must support this feature before the fault can be detected.
Bugs
SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The time difference in the slave status polling between the primary and secondary sides may be several seconds. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The problem is more probable with SCU-H than with SCU as it has a longer startup time. (CR ID 300107078) An invalid flash list record status may cause a problem in the node even though the record status error is very improbable. (CR ID 300091551) When CXU-M sends the state of the used clock source to the interface units, the state value of the clock source data is set to NOT_OK (255) if the used clock is internal and the FBL is not empty and therefore the neighbour node does not apply the defined QL of the internal clock correctly (CR ID 200013488). A CXU-S card that exists in the subrack inventory but is either physically missing or initializing in the active side does not cause a switch-over. A unit does not disappear from the list of available clock sources when the unit is removed from inventory. Swap circuits with unidirectional connections and trunk swap operate properly only if the swap port of the master port is in the same subrack with the original master port and destination port 1 is in a different subrack than destination port 2. The combined swap and passivation state of trunks does not operate properly and it may lead to problems in connections and thus must not be used (MartisDXX Manager priority bumping feature). There may exist an unnecessary Unstable SSM fault when master clock quality levels are disabled. There may exist irrelevant master clock faults in backup CXU-M as this unit does not receive the quality level information of SDH clock sources defined in the fallback list. The quality level 6 (used for internal clock) is translated to SDH SSM code SEC though it should be DNU. If a quality source mode other than poll is used, the quality level information is not properly transmitted to neighbour nodes. A problem may occur if a new GMU unit is added to a node where a GMU unit has already been in inventory. This is due to the fact that unit inventory add operation does not step forward the state machine controlling the clock commands of each GMU unit in a node and the GMU will receive the same command that was sent to the GMU unit previously removed from inventory. Supports only 10 simultaneous cross-connect object commands in a single GCI message. When the master clock starts using an interface with a different frequency than the previous frequency and the change happens suddenly (interrupt), the frequency dependent ASIC
10004_22 2008 Tellabs.

77
parameters may temporarily be configured incorrectly. As a result synchronization to the new clock source is a little slower but the final state is however correct.
There are two GMM-related problems in the node master clock selection. 1) If the fallback list contains three or more clocks from the same subrack and the current MCL becomes faulty, the next choices (GMM) status is temporarily marked in fail state and the fourth choice is selected instead for the SYB. After a while the GMM state is properly updated and it is selected in the SYB bus. 2) If the node clock fails and the next choice is GMM, the node may temporarily start using the internal clock. After a while the node starts to use the valid GMM as MCL. When CXU-M receives 1001th X-Group ID activation command after unit initialization, there is a problem updating the internal X-Group RAM database and this may lead to reset in all the slaves on the same side regardless of whether the CXU-M unit is in the active or passive side. The primary reason for the slave resets is the RAM list monitoring. If the master is not able to update its own list properly while the slaves are, the result is a checksum mismatch. It is however very unlikely that the number of activations would reach a very large number. X-Group IDs are used in swap circuit and time controlled circuit applications.
5.18 Version 2.6

Dependencies
Restrictions

The detection time of missing SXU-C unit has not been optimized. The Fall Back List Warning fault exists in the faults list. The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) are not able to detect possible internal errors in message envelope structure. Does not support background verification of CXU-A cross-connect memory. Does not support the enhanced Asic Latch Warning fault monitoring. Erroneous warnings can be seen as the test method is too sensitive. Does not indicate the used fallback list entry in the fault history. Does not support the new external clock protection system (switch-over happens only after all other possible valid choices have failed and the next choice would be the node internal clock). No support for GMU. Holdover mode of the master clock is not supported. Does not support indication of faulty intersubrack cable installation in fault history. Both SXU-C and CXU-M must support this feature before the fault can be detected.

78
10004_22 2008 Tellabs.
Bugs
SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The time difference in the slave status polling between the primary and secondary sides may be several seconds. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The problem is more probable with SCU-H than with SCU as it has a longer startup time. (CR ID 300107078) An invalid flash list record status may cause a problem in the node even though the record status error is very improbable. (CR ID 300091551) When CXU-M sends the state of the used clock source to the interface units, the state value of the clock source data is set to NOT_OK (255) if the used clock is internal and the FBL is not empty and therefore the neighbour node does not apply the defined QL of the internal clock correctly (CR ID 200013488). A CXU-S card that exists in the subrack inventory but is either physically missing or initializing in the active side does not cause a switch-over. A unit does not disappear from the list of available clock sources when the unit is removed from inventory. The combined swap and passivation state of trunks does not operate properly and it may lead to problems in connections and thus must not be used (MartisDXX Manager priority bumping feature). An unnecessary Fallback List warning fault may appear if there are still usable clock sources. If an external clock is the current clock source and the external clock input is broken, it is possible that the next clock is not correctly selected from the fallback list. Swap circuits with unidirectional connections and trunk swap operate properly only if the swap port of the master port is in the same subrack with the original master port and destination port 1 is in a different subrack than destination port 2. Supports only 10 simultaneous cross-connect object commands in a single GCI message. When the master clock starts using an interface with a different frequency than the previous frequency and the change happens suddenly (interrupt), the frequency dependent ASIC parameters may temporarily be configured incorrectly. As a result synchronization to the new clock source is a little slower but the final state is however correct. There are two GMM-related problems in the node master clock selection. 1) If the fallback list contains three or more clocks from the same subrack and the current MCL becomes faulty, the next choices (GMM) status is temporarily marked in fail state and the fourth choice is selected instead for the SYB. After a while the GMM state is properly updated and it is selected in the SYB bus. 2) If the node clock fails and the next choice is GMM, the node may temporarily start using the internal clock. After a while the node starts to use the valid GMM as MCL. When CXU-M receives 1001th X-Group ID activation command after unit initialization, there is a problem updating the internal X-Group RAM database and this may lead to reset in all the slaves on the same side regardless of whether the CXU-M unit is in the active or passive side. The primary reason for the slave resets is the RAM list monitoring. If the master is not able to update its own list properly while the slaves are, the result is a checksum mismatch. It is however very unlikely that the number of activations would reach a very large number. X-Group IDs are used in swap circuit and time controlled circuit applications.
10004_22 2008 Tellabs.

79
5.19 Version 2.5

Dependencies
Restrictions

The detection time of missing SXU-C unit has not been optimized. The Fall Back List Warning fault exists in the faults list. The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) are not able to detect possible internal errors in message envelope structure. Does not support background verification of CXU-A cross-connect memory. Does not support the enhanced Asic Latch Warning fault monitoring. Erroneous warnings can be seen as the test method is too sensitive. Does not indicate the used fallback list entry in the fault history. Does not support the new external clock protection system (switch-over happens only after all other possible valid choices have failed and the next choice would be the node internal clock). No support for GMU. Holdover mode of the master clock is not supported. Does not support indication of faulty intersubrack cable installation in fault history. Both SXU-C and CXU-M must support this feature before the fault can be detected.
Bugs
SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The time difference in the slave status polling between the primary and secondary sides may be several seconds. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The problem is more probable with SCU-H than with SCU as it has a longer startup time. (CR ID 300107078) An invalid flash list record status may cause a problem in the node even though the record status error is very improbable. (CR ID 300091551) When CXU-M sends the state of the used clock source to the interface units, the state value of the clock source data is set to NOT_OK (255) if the used clock is internal and the FBL is not empty and therefore the neighbour node does not apply the defined QL of the internal clock correctly (CR ID 200013488). A CXU-S card that exists in the subrack inventory but is either physically missing or initializing in the active side does not cause a switch-over. Deletion of unidirectional group format cross-connection does not work correctly. This connection type or format combination is not used at the moment by MartisDXX Manager tools. A unit does not disappear from the list of available clock sources when the unit is removed from inventory.

80
10004_22 2008 Tellabs.
The combined swap and passivation state of trunks does not operate properly and it may lead to problems in connections and thus must not be used (MartisDXX Manager priority bumping feature). An unnecessary Fallback list warning fault may appear if there are still usable clock sources. If an external clock is the current clock source and the external clock input is broken, it is possible that the next clock is not correctly selected from the fallback list. Swap circuits with unidirectional connections and trunk swap operate properly only if the swap port of the master port is in the same subrack with the original master port and destination port 1 is in a different subrack than destination port 2. Supports only 10 simultaneous cross-connect object commands in a single GCI message. When the master clock starts using an interface with a different frequency than the previous frequency and the change happens suddenly (interrupt), the frequency dependent ASIC parameters may temporarily be configured incorrectly. As a result, synchronization to the new clock source is a little slower but the final state is however correct. There are two GMM-related problems in the node master clock selection. 1) If the fallback list contains three or more clocks from the same subrack and the current MCL becomes faulty, the next choices (GMM) status is temporarily marked in fail state and the fourth choice is selected instead for the SYB. After a while the GMM state is properly updated and it is selected in the SYB bus. 2) If the node clock fails and the next choice is GMM, the node may temporarily start using the internal clock. After a while the node starts to use the valid GMM as MCL. When CXU-M receives 1001th X-Group ID activation command after unit initialization, there is a problem updating the internal X-Group RAM database and this may lead to reset in all the slaves on the same side regardless of whether the CXU-M unit is in the active or passive side. The primary reason for the slave resets is the RAM list monitoring. If the master is not able to update its own list properly while the slaves are, the result is a checksum mismatch. It is however very unlikely that the number of activations would reach a very large number. X-Group IDs are used in swap circuit and time controlled circuit applications.
10004_22 2008 Tellabs.

81
5.20 Version 2.4

Dependencies
Restrictions

The detection time of missing SXU-C unit has not been optimized. The Fall Back List Warning fault exists in the faults list. The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) are not able to detect possible internal errors in message envelope structure. Does not support background verification of CXU-A cross-connect memory. Does not support the enhanced Asic Latch Warning fault monitoring. Erroneous warnings can be seen as the test method is too sensitive. Does not indicate the used fallback list entry in the fault history. Does not support the new external clock protection system (switch-over happens only after all other possible valid choices have failed and the next choice would be the node internal clock). Does not support contradirectional synchronization clock sources in protected ring network topology. No support for GMU. Holdover mode of the master clock is not supported. Does not support indication of faulty intersubrack cable installation in fault history. Both SXU-C and CXU-M must support this feature before the fault can be detected.
Bugs
SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The time difference in the slave status polling between the primary and secondary sides may be several seconds. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The problem is more probable with SCU-H than with SCU as it has a longer startup time. (CR ID 300107078) An invalid flash list record status may cause a problem in the node even though the record status error is very improbable. (CR ID 300091551) When CXU-M sends the state of the used clock source to the interface units, the state value of the clock source data is set to NOT_OK (255) if the used clock is internal and the FBL is not empty and therefore the neighbour node does not apply the defined QL of the internal clock correctly (CR ID 200013488). A CXU-S card that exists in the subrack inventory but is either physically missing or initializing in the active side does not cause a switch-over.

82
10004_22 2008 Tellabs.
Deletion of unidirectional group format cross-connection does not work correctly. This connection type or format combination is not used at the moment by MartisDXX Manager tools. A unit does not disappear from the list of available clock sources when the unit is removed from inventory. The combined swap and passivation state of trunks does not operate properly and it may lead to problems in connections and thus must not be used (MartisDXX Manager priority bumping feature). If an external clock is the current clock source and the external clock input is broken, it is possible that the next clock is not correctly selected from the fallback list. Swap circuits with unidirectional connections and trunk swap operate properly only if the swap port of the master port is in the same subrack with the original master port and destination port 1 is in a different subrack than destination port 2. Supports only 10 simultaneous cross-connect object commands in a single GCI message. When the master clock starts using an interface with a different frequency than the previous frequency and the change happens suddenly (interrupt), the frequency dependent ASIC parameters may temporarily be configured incorrectly. As a result, synchronization to the new clock source is a little slower but the final state is however correct. There are two GMM-related problems in the node master clock selection. 1) If the fallback list contains three or more clocks from the same subrack and the current MCL becomes faulty, the next choices (GMM) status is temporarily marked in fail state and the fourth choice is selected instead for the SYB. After a while the GMM state is properly updated and it is selected in the SYB bus. 2) If the node clock fails and the next choice is GMM, the node may temporarily start using the internal clock. After a while the node starts to use the valid GMM as MCL. When CXU-M receives 1001th X-Group ID activation command after unit initialization, there is a problem updating the internal X-Group RAM database and this may lead to reset in all the slaves on the same side regardless of whether the CXU-M unit is in the active or passive side. The primary reason for the slave resets is the RAM list monitoring. If the master is not able to update its own list properly while the slaves are, the result is a checksum mismatch. It is however very unlikely that the number of activations would reach a very large number. X-Group IDs are used in swap circuit and time controlled circuit applications.
10004_22 2008 Tellabs.

83
5.21 Version 2.3

Dependencies
Restrictions

The detection time of missing SXU-C unit has not been optimized. The Fall Back List Warning fault exists in the faults list. The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) are not able to detect possible internal errors in message envelope structure. Does not support background verification of CXU-A cross-connect memory. Does not support the enhanced Asic Latch Warning fault monitoring. Erroneous warnings can be seen as the test method is too sensitive. Does not indicate the used fallback list entry in the fault history. Does not support the new external clock protection system (switch-over happens only after all other possible valid choices have failed and the next choice would be the node internal clock). Does not support contradirectional synchronization clock sources in protected ring network topology. Does not support the CCU additional filtering mechanism to avoid unnecessary crossconnection protection switch-over. No support for GMU. Holdover mode of the master clock is not supported. Does not support indication of faulty intersubrack cable installation in fault history. Both SXU-C and CXU-M must support this feature before the fault can be detected.
Bugs
SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The time difference in the slave status polling between the primary and secondary sides may be several seconds. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The problem is more probable with SCU-H than with SCU as it has a longer startup time. (CR ID 300107078) An invalid flash list record status may cause a problem in the node even though the record status error is very improbable. (CR ID 300091551) When CXU-M sends the state of the used clock source to the interface units, the state value of the clock source data is set to NOT_OK (255) if the used clock is internal and the FBL is not empty and therefore the neighbour node does not apply the defined QL of the internal clock correctly (CR ID 200013488). A CXU-S card that exists in the subrack inventory but is either physically missing or initializing in the active side does not cause a switch-over.

84
10004_22 2008 Tellabs.
Deletion of unidirectional group format cross-connection does not work correctly. This connection type or format combination is not used at the moment by MartisDXX Manager tools. The real time clock can be used only in adaptive mode. Master clock output control does not work. A unit does not disappear from the list of available clock sources when the unit is removed from inventory. The combined swap and passivation state of trunks does not operate properly and it may lead to problems in connections and thus must not be used (MartisDXX Manager priority bumping feature). If an external clock is the current clock source and the external clock input is broken, it is possible that the next clock is not correctly selected from the fallback list. Swap circuits with unidirectional connections and trunk swap operate properly only if the swap port of the master port is in the same subrack with the original master port and destination port 1 is in a different subrack than destination port 2. Supports only 10 simultaneous cross-connect object commands in a single GCI message. When the master clock starts using an interface with a different frequency than the previous frequency and the change happens suddenly (interrupt), the frequency dependent ASIC parameters may temporarily be configured incorrectly. As a result, synchronization to the new clock source is a little slower but the final state is however correct. There are two GMM-related problems in the node master clock selection. 1) If the fallback list contains three or more clocks from the same subrack and the current MCL becomes faulty, the next choices (GMM) status is temporarily marked in fail state and the fourth choice is selected instead for the SYB. After a while the GMM state is properly updated and it is selected in the SYB bus. 2) If the node clock fails and the next choice is GMM, the node may temporarily start using the internal clock. After a while the node starts to use the valid GMM as MCL. When CXU-M receives 1001th X-Group ID activation command after unit initialization, there is a problem updating the internal X-Group RAM database and this may lead to reset in all the slaves on the same side regardless of whether the CXU-M unit is in the active or passive side. The primary reason for the slave resets is the RAM list monitoring. If the master is not able to update its own list properly while the slaves are, the result is a checksum mismatch. It is however very unlikely that the number of activations would reach a very large number. X-Group IDs are used in swap circuit and time controlled circuit applications.
10004_22 2008 Tellabs.

85
E3C Unit: GPZ641 Unit Software
6 E3C Unit: GPZ641 Unit Software

The software GPZ641 is used on E3C unit (whose base unit is GPT782) in Tellabs 8150 basic, Tellabs 8170 cluster, Tellabs 8160 A111 and Tellabs 8140 midi nodes.
6.1 Version 1.0

This is the first official version.
Dependencies

E3C base unit (GPT782) hardware version must be 1.0 or higher. E3C power supply module (PDF593) hardware version must be 2.0 or higher. CCU (SCZ286) software version can be any version. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version can be any version. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version can be any version. Tellabs 8100 network manager support for this unit is available in Release 13 or higher.
Restrictions
Lack of reliability on the control channel (HDLC) when used bit rate is 4 kbit/s.
Bugs
No known bugs.

86
10004_22 2008 Tellabs.
EAE Unit: EAZ418 Unit Software
7 EAE Unit: EAZ418 Unit Software

The software EAZ418 is used in EAE units.
7.1 Version 1.1

Dependencies
EAE unit software requires SCZ280 version 8.0 or later to function correctly. Using earlier SCZ280 versions may cause problems with the Create inventory operation.
Restrictions
No restrictions.
Bugs
No known bugs.
New Features
Converted port descriptors are returned when ports are locked.
7.2 Version 1.0

Dependencies
No dependencies.
Restrictions
No restrictions.
Bugs

Inventory operations do not affect hardware parameters. Module types cannot be read from the unit when the unit is not in inventory.
10004_22 2008 Tellabs.

87
ESU Unit: EMZ642 Unit Software
8 ESU Unit: EMZ642 Unit Software

The software EMZ642 and FPGA code TXA642 are used on the ESU unit (ESU783 and ESM784) in Tellabs 8140 midi, Tellabs 8150 basic, Tellabs 8160 A111 and Tellabs 8170 cluster nodes as well as in Tellabs 8184 and Tellabs 8188 access switches. The version 1.12 can be downloaded to the ESU units having the version 1.y of EMZ642 (where y=0, 1, 2...).
8.1 Version 1.12

The version 1.12 contains EMZ642_1.12 and TXA642_1.1. Enhancements and Fixed Bugs
Baseband statistics corrected when line is in 1x3M, 2x3M or 4x3M mode (CR ID 300096026). Note: as a result of this fix line statistics may show different values in the ESU side than in NTU. Values seen from the ESU side are more reliable. SNMP Mib-2-interface-ifTable-ifEntry-ifDescr includes only an interface type and a number. (CR ID 300077594) Deleting VLAN ID with calculate statistics option releases statistics calculation resource (CR ID 300041818) ESU MAC addresses list is correctly shown when all addresses are queried (CR ID 300045431). However, there is still a bug in a static address list query (CR ID 300100261)
Dependencies

ESU (ESU783 and ESM784) hardware version must be 1.0 or higher. SCO interface module version must be 3.0 or higher to support 4-pair line modes, and 3.1 or higher to support 3088 kbit/s line rates with Tellabs 8110 STE-10M NTU. CCU (SCZ286) software can be any version. SCP (SCZ281) software version must be 3.1 or higher to support extra backups for other units in the node. SCU (SCZ280) software version must be 8.4 or higher to support extra backups for other units in the node. SCU-H (SCZ545) software version must be 1.6 or higher to support unlocking the ports without failures. XCG (SMZ538) software version must be 2.0 or higher to support extra backups for other units in the node, and 3.5 or higher to support over 8M cross-connection ports. CXU-M (SXZ288) software can be any version. GMX (GMZ544) software version must be 3.19, or 4.1 or higher to support over 8M crossconnection ports.

88
10004_22 2008 Tellabs.
GMX2 (GMZ802) software version can be any version. GMU (GMZ460 and GMZ461) software version must be 1.7 or higher, if GMU450 hardware version is 2.0 and software version must be 1.179 or higher if GMU450 hardware version is 1.0. SXU-A/B (SXZ282) software version must be 10.5 or higher to support over 8M crossconnection ports. SXU-C (SXZ289) software can be any version. Over 8M cross-connection ports are not supported. SXU-V (SXZ630) software can be any version. Over 8M cross-connection ports are not supported. Tellabs 8100 manager support for this unit is available in Release 13A Service Pack 1 or higher. Tellabs 8100 manager support for Input Rate Monitoring and Fault Masking functionalities are available in Release 14 Service Pack 1 or higher. Tellabs 8100 manager support for this unit and Tellabs 8110 STE-10M NTU is available in Release 14 Service Pack 3 or higher. Tellabs 8000 manager support for Spanning Tree Transparency is available in Release 15 or higher. CTE-R (SBZ674) software version must be 1.0 or higher to support sync pulse.
Restrictions

Cross-connections to timeslot 144 and above that are not supported. ESU unit with SCO: The Line Loop (LiL) is not supported in case of SCO interfaces connected to any NTU.
Bugs

Extra faults are generated in other aggregation groups (X-bus and DSL) when Ethernet cable is cut. (CR ID 300046507) Contrary to other ESU group operations, ESU BPDU (STP) transparency configuration needs to be configured to all members of the link aggregation group. (CR ID 300047268) ESU static MAC addresses list and address statistics information conflict. (CR ID 300100261) When MAC address limitation function is enabled ESU lets through only unicast frames that (this bug does not apply to multicast and broadcast frames) have both source and destination MAC address in the MAC switching table. (CR ID 300054360) Frame content may be corrupted in certain situations where constant high load is offered via a high capacity ingress link and traffic is switched to a lower capacity egress link. (CR ID 300054363)
10004_22 2008 Tellabs.

89
8.2 Version 1.11


End-customer spanning tree transparency added. (CR ID 300037430) More SNMP query related bugs have been fixed. Behavior of the following objects has been changed: ifDescr, ifType, ifMtu, ifSpeed, ifPhysAddress, ifAdminStatus, ifInUnknownProtos, ifOutDiscards and ifOutErrors. (CR IDs 300038858 and 300032720)
Dependencies

ESU (ESU783 and ESM784) hardware version must be 1.0 or higher. SCO interface module version must be 3.0 or higher to support 4-pair line modes, and 3.1 or higher to support 3088 kbit/s line rates with Tellabs 8110 STE-10M NTU. CCU (SCZ286) software can be any version. SCP (SCZ281) software version must be 3.1 or higher to support extra backups for other units in the node. SCU (SCZ280) software version must be 8.4 or higher to support extra backups for other units in the node. SCU-H (SCZ545) software version must be 1.6 or higher to support unlocking the ports without failures. XCG (SMZ538) software version must be 2.0 or higher to support extra backups for other units in the node, and 3.5 or higher to support over 8M cross-connection ports. CXU-M (SXZ288) software can be any version. GMX (GMZ544) software version must be 3.19, or 4.1 or higher to support over 8M crossconnection ports. GMU (GMZ460 and GMZ461) software version must be 1.7 or higher, if GMU450 hardware version is 2.0 and software version must be 1.179 or higher if GMU450 hardware version is 1.0. SXU-A/B (SXZ282) software version must be 10.5 or higher to support over 8M crossconnection ports. SXU-C (SXZ289) software can be any version. Over 8M cross-connection ports are not supported. SXU-V (SXZ630) software can be any version. Over 8M cross-connection ports are not supported. Tellabs 8100 manager support for this unit is available in Release 13A Service Pack 1 or higher. Tellabs 8100 manager support for Input Rate Monitoring and Fault Masking functionalities are available in Release 14 Service Pack 1 or higher. Tellabs 8100 manager support for this unit and Tellabs 8110 STE-10M NTU is available in Release 14 Service Pack 3 or higher.

90
10004_22 2008 Tellabs.
Tellabs 8000 manager support for Spanning Tree Transparency is available in Release 15 or higher. CTE-R (SBZ674) software version must be 1.0 or higher to support sync pulse.
Restrictions

Cross-connections to timeslot 144 and above that are not supported. ESU unit with SCO: The Line Loop (LiL) is not supported in case of SCO interfaces connected to any NTU.
Bugs

Extra faults are generated in other aggregation groups (X-bus and DSL) when Ethernet cable is cut. (CR ID 300046507) Contrary to other ESU group operations, ESU BPDU (STP) transparency configuration needs to be configured to all members of the link aggregation group. (CR ID 300047268) ESU MAC addresses list and address statistics information conflict. (CR ID 300045431) When MAC address limitation function is enabled ESU lets through only unicast frames that (this bug does not apply to multicast and broadcast frames) have both source and destination MAC address in the MAC switching table. (CR ID 300054360) Frame content may be corrupted in certain situations where constant high load is offered via a high capacity ingress link and traffic is switched to a lower capacity egress link. (CR ID 300054363)
8.3 Version 1.10


More flexibility has been added for ESU MAC address limit. (CR ID 200020353) SNMP query related bugs have been fixed. (CR IDs 200032065, 200037770 and 200037938)
Dependencies

ESU (ESU783 and ESM784) hardware version must be 1.0 or higher. CCU (SCZ286) software can be any version. SCP (SCZ281) software version must be 3.1 or higher to support extra backups for other units in the node. SCU (SCZ280) software version must be 8.4 or higher to support extra backups for other units in the node. SCU-H (SCZ545) software version must be 1.6 or higher to support unlocking the ports without failures. XCG (SMZ538) software version must be 2.0 or higher to support extra backups for other units in the node, and 3.5 or higher to support over 8M cross-connection ports.
91
10004_22 2008 Tellabs.
CXU-M (SXZ288) software can be any version. GMX (GMZ544) software version must be 3.19, or 4.1 or higher to support over 8M crossconnection ports. GMU (GMZ460 and GMZ461) software version must be 1.7 or higher, if GMU450 hardware version is 2.0 and software version must be 1.179 or higher if GMU450 hardware version is 1.0. SXU-A/B (SXZ282) software version must be 10.5 or higher to support over 8M crossconnection ports. SXU-C (SXZ289) software can be any version. Over 8M cross-connection ports are not supported. SXU-V (SXZ630) software can be any version. Over 8M cross-connection ports are not supported. Tellabs 8100 manager support for this unit is available in Release 13A Service Pack 1 or higher. Tellabs 8100 manager support for Input Rate Monitoring and Fault Masking functionalities are available in Release 14 Service Pack 1 or higher. Tellabs 8100 manager support for this unit and Tellabs 8110 STE-10M NTU is available in Release 14 Service Pack 3 or higher. CTE-R (SBZ674) software version must be 1.0 or higher to support sync pulse.
Restrictions
ESU unit with SCO: The Line Loop (LiL) is not supported in case of SCO interfaces connected to any NTU.
Bugs
Still some SNMP query related bugs. (CR IDs 300038858 and 300032720).
8.4 Version 1.9


10M SHDSL support for ESU. (CR ID 200028425) ESU FPGA modification for supporting over 8 Mbits/s line speeds. (CR ID 200034611)
Dependencies

ESU (ESU783 and ESM784) hardware version must be 1.0 or higher. CCU (SCZ286) software can be any version. SCP (SCZ281) software version must be 3.1 or higher to support extra backups for other units in the node.

92
10004_22 2008 Tellabs.
SCU (SCZ280) software version must be 8.4 or higher to support extra backups for other units in the node. SCU-H (SCZ545) software version must be 1.6 or higher to support unlocking the ports without failures. XCG (SMZ538) software version must be 2.0 or higher to support extra backups for other units in the node, and 3.5 or higher to support over 8M cross-connection ports. CXU-M (SXZ288) software can be any version. GMX (GMZ544) software version must be 3.19, or 4.1 or higher to support over 8M crossconnection ports. GMU (GMZ460 and GMZ461) software version must be 1.7 or higher, if GMU450 hardware version is 2.0 and software version must be 1.179 or higher if GMU450 hardware version is 1.0. SXU-A/B (SXZ282) software version must be 10.5 or higher to support over 8M crossconnection ports. SXU-C (SXZ289) software can be any version. Over 8M cross-connection ports are not supported. SXU-V (SXZ630) software can be any version. Over 8M cross-connection ports are not supported. Tellabs 8100 manager support for this unit is available in Release 13A Service Pack 1 or higher. Tellabs 8100 manager support for Input Rate Monitoring and Fault Masking functionalities are available in Release 14 Service Pack 1 or higher. Tellabs 8100 manager support for this unit and Tellabs 8110 STE-10M NTU is available in Release 14 Service Pack 3 or higher. CTE-R (SBZ674) software version must be 1.0 or higher to support sync pulse.
Restrictions
ESU unit with SCO: The Line Loop (LiL) is not supported in case of SCO interfaces connected to any NTU.
Bugs
There is a SNMP walk related problem. (CR ID 200032065)
10004_22 2008 Tellabs.

93
8.5 Version 1.8

Fixed SNMP Reply source port problem (CR ID 200020528).
Dependencies

ESU (ESU783 and ESM784) hardware version must be 1.0 or higher. CCU (SCZ286) software can be any version. SCP (SCZ281) software version must be 3.1 or higher to support extra backups for other units in the node. SCU (SCZ280) software version must be 8.4 or higher to support extra backups for other units in the node. SCU-H (SCZ545) software version must be 1.6 or higher to support unlocking the ports without failures. XCG (SMZ538) software version must be 2.0 or higher to support extra backups for other units in the node. CXU-M (SXZ288) software can be any version. GMX (GMZ544) software version must be 3.19 or higher to support 12M trunk. GMU (GMZ460 and GMZ461) software version must be 1.7 or higher, if GMU450 hardware version is 2.0 and software version must be 1.179 or higher if GMU450 hardware version is 1.0. SXU-A/B (SXZ282) software can be any version. SXU-C (SXZ289) software can be any version. SXU-V (SXZ630) software can be any version. Tellabs 8100 manager support for this unit is available in Release 13A Service Pack 1 or higher. Tellabs 8100 manager support for Input Rate Monitoring and Fault Masking functionalities are available in Release 14 Service Pack 1 or higher. CTE-R (SBZ674) software version must be 1.0 or higher to support sync pulse.
Restrictions

ESU unit with SCO: The Line Loop (LiL) is not supported in case of SCO interfaces connected to any NTU. SXU-A/B/C does not support 12M trunks. XCG does not support 12M trunks.

94
10004_22 2008 Tellabs.
Bugs
There is a SNMP walk related problem. (CR ID 200032065)
8.6 Version 1.7


Port based rate limiting on external Ethernet ports (CR ID 200012088). Fault Masking supported also on X-bus and Ethernet interfaces (CR ID 200012092). TXA642 version is shown correctly in File Management Dialog (CR ID 200012161). Fixed LMI interoperability problem (CR ID 200014315).
Dependencies

ESU (ESU783 and ESM784) hardware version must be 1.0 or higher. CCU (SCZ286) software can be any version. SCP (SCZ281) software version must be 3.1 or higher to support extra backups for other units in the node. SCU (SCZ280) software version must be 8.4 or higher to support extra backups for other units in the node. SCU-H (SCZ545) software version must be 1.6 or higher to support unlocking the ports without failures. XCG (SMZ538) software version must be 2.0 or higher to support extra backups for other units in the node. CXU-M (SXZ288) software can be any version. GMX (GMZ544) software version must be 3.19 or higher to support 12M trunk. GMU (GMZ460 and GMZ461) software version must be 1.7 or higher, if GMU450 hardware version is 2.0 and software version must be 1.179 or higher if GMU450 hardware version is 1.0. SXU-A/B (SXZ282) software can be any version. SXU-C (SXZ289) software can be any version. SXU-V (SXZ630) software can be any version. Tellabs 8100 manager support for this unit is available in Release 13A Service Pack 1 or higher. Tellabs 8100 manager support for Input Rate Monitoring and Fault Masking functionalities are available in Release 14 Service Pack 1 or higher. CTE-R (SBZ674) software version must be 1.0 or higher to support sync pulse.
10004_22 2008 Tellabs.

95
Restrictions

Bugs
SNMP reply is sent using a wrong source port (CR ID 200020528).
8.7 Version 1.6

This is an internal test version.
8.8 Version 1.5

8.9 Version 1.4

8.10 Version 1.3

Dependencies

ESU (ESU783 and ESM784) hardware version must be 1.0 or higher. CCU (SCZ286) software can be any version. SCP (SCZ281) software version must be 3.1 or higher to support extra backups for other units in the node. SCU (SCZ280) software version must be 8.4 or higher to support extra backups for other units in the node.

96
10004_22 2008 Tellabs.
SCU-H (SCZ545) software version must be 1.6 or higher to support unlocking the ports without failures. XCG (SMZ538) software version must be 2.0 or higher to support extra backups for other units in the node. CXU-M (SXZ288) software can be any version. GMX (GMZ544) software version must be 3.19 or higher to support 12M trunk. GMU (GMZ460 and GMZ461) software version must be 1.7 or higher, if GMU450 hardware version is 2.0 and software version must be 1.179 or higher if GMU450 hardware version is 1.0. SXU-A/B (SXZ282) software can be any version. SXU-C (SXZ289) software can be any version. SXU-V (SXZ630) software can be any version. Tellabs 8100 manager support for this unit is available in Release 13A Service Pack 1 or higher. CTE-R (SBZ674) software version must be 1.0 or higher to support sync pulse.
Restrictions

Bugs
TXA642 version 1.0 is incorrectly shown as version 0.10 in the File Management dialog. The version number is shown correctly if TXA642 has been downloaded using Tellabs 8100 network manager.
10004_22 2008 Tellabs.

97
GMH Unit: GMZ283 Unit Software
9 GMH Unit: GMZ283 Unit Software

The software GMZ283 is used on the GMH units (whose base unit is GMH220) in Tellabs 8140 midi, Tellabs 8150 basic, Tellabs 8160 A111 and Tellabs 8170 cluster nodes as well as in Tellabs 8184 and Tellabs 8188 access switches. The version 10.2 can be only downloaded to the GMH units having the version 10.y of GMZ283 (where y = 0, 1, 2,). Software supports all versions of the base unit.
9.1 Version 10.2

Enhancements
The reason for this release is fixes in 1+1 protection functionality. In this software version 1+1 protection switch is working correctly when an interface is in 2M unframed mode (CR ID 300088866 and CR ID 300089844).
Dependencies

GMH (base unit GMH220) hardware version must be 5.0 or higher. CCU (SCZ286) software version can be any version. SCP (SCZ281) software version can be any version. SCU (SCZ280) software version can be any version. SCU-H (SCZ545) software version can be any version. XCG (SMZ538) software version can be any version. GMH (GMZ283) software version can be any version. CXU-M (SXZ288) software version can be any version. GMX (GMZ544) software version can be any version. GMX2 (GMZ802) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for the GMH unit is available in Release 12 or higher to support V5.2 functionality and in Release 11 or higher to support the other functionalities.
Restrictions
No restrictions.

98
10004_22 2008 Tellabs.
Bugs
No known bugs.
9.2 Version 10.1

Enhancements
V5.2 functionality is supported. It is required in V5.2 that SXU-V (or SCU-H) polls the trunk interface faults and monitors or sets Sa7-bit in E1 trunk. To prevent big delays FCI (Fast Command Interpreter) has been used instead of GCI (General Command Interpreter). (CRF 4003938) Downloaded GMH USW cannot be disabled by NMS, because download is required for GMH to be fully operational. Without download only minimum set of operations are working e.g. download feature. (CRF 4003647) Preliminary HDLC link timeout support for satellite connections for GMH has been done. (CRF 4003555)
Dependencies

GMH (base unit GMH220) hardware version must be 5.0 or higher. CCU (SCZ286) software version can be any version. SCP (SCZ281) software version can be any version. SCU (SCZ280) software version can be any version. SCU-H (SCZ545) software version can be any version. XCG (SMZ538) software version can be any version. GMH (GMZ283) software version can be any version. CXU-M (SXZ288) software version can be any version. GMX (GMZ544) software version can be any version. GMX2 (GMZ802) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for the GMH unit is available in Release 12 or higher to support V5.2 functionality and in Release 11 or higher to support the other functionalities.
Restrictions
No restrictions.
Bugs
1+1 protection switch does not work reliably if an interface is configured in 2M unframed mode. (CR ID 300088866).
10004_22 2008 Tellabs.

99
9.3 Version 10.0

Dependencies
GMH220 HW version must be at least 5.0.
Restrictions
USW 10.0 version does not support BTE-384 modules.
Bugs

Communication to HTU-2M is lost after setting a Neighbor Node Loop (NNL) from the modem. (CRF 4002702) Parameters to OTE-LASER (OTE-LP) module cannot be set in new GMH version 5.0 when USW is 10.0. (CRF 4003268 and CRF 4003772) There is compatibility problem with BTE and HCE modules in GMH. When HCE module and BTE module is assembled in the same GMH, the line statistics window of HCE module cannot be opened. (CRF 4003357) Fast squelch of clock (GMH) interface. (CRF 4003322) Available time in 1+1 protected trunk performance data is always 100% in GMH units even if interfaces are cut. Interface windows show values correctly, but PMS gets wrong values. (CRF 4003959) VTP bus is making errors and this causes wrong time stamp values. (CRF 4003633) 1+1 protection switch does not work reliably if an interface is configured in 2M unframed mode. (CR ID 300088866)
9.4 Version 6.10

Dependencies

GMH (base unit GMH220) hardware version must be less than 5.0. CCU (SCZ286) software version can be any version. SCP (SCZ281) software version can be any version. SCU (SCZ280) software version can be any version. SCU-H (SCZ545) software version can be any version. XCG (SMZ538) software version can be any version. GMH (GMZ283) software version can be any version. CXU-M (SXZ288) software version can be any version. GMX (GMZ544) software version can be any version. GMX2 (GMZ802) software version can be any version.

100
10004_22 2008 Tellabs.
SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for the GMH unit is available in Release 10.
Restrictions

GMH220 HW versions 1.0, 1.1, and 1.2 do not support 4, 8 or 64 frame buffers in Tellabs 8170 cluster nodes. USW 6.10 version does not support HCE-2M-1P and HCE-2M-2P modules. TS0 bit inversion.
Bugs
In USW 6.10 Rx signal missing alarm for IF 2 is not reported when framing is off.
9.5 Version 6.9

Dependencies
GMH (base unit GMH220) hardware version must be less than 5.0.
Restrictions

GMH220 HW versions 1.0, 1.1, and 1.2 do not support 4, 8 or 64 frame buffers in Tellabs 8170 cluster nodes. USW 6.9 version does not support HCE-2M-1P and HCE-2M-2P modules. TS0 bit inversion. USW 6.9 version does not support BTE-320, BTE-576, BTE-1088-2W, BTE-2304 modules. An alarm will be generated when using x-connected time slot for HDLC.
Bugs

DEG alarm with S-status does not work properly. Unnecessary Tx-Clock fault when using BTE-4096 module.
10004_22 2008 Tellabs.

101
9.6 Version 6.7

Dependencies
Restrictions

GMH220 HW versions 1.0, 1.1, and 1.2 do not support 4, 8 or 64 frame buffers in cluster usage. USW 6.7 version does not support HCE-2M-1P and HCE-2M-2P modules. TS0 bit inversion. USW 6.7 version does not support BTE-320, BTE-576, BTE-1088-2W, BTE-2304 modules. An alarm will be generated when using a x-connected time slot for HDLC. USW 6.7 version does not support DEG/EXC BER alarms. USW 6.7 version does not support micro BTS. USW 6.7 version does not support CAS at 2M < bit rate < 8M. Frequency difference alarm does not meet the G.823 updated standard (1993). Bugs Mismatch of 2 frame buffer with uneven bus allocation can occur if locked interface buffer length is changed then the CAS state is changed and finally buffer length is changed to 2 frame. Handling of erroneous message from VTP-bus. No alarm when neighbor makes V.54 loop. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist. Unnecessary Tx-Clock fault when using BTE-4096 module.

102
10004_22 2008 Tellabs.
9.7 Version 6.6

Dependencies
Restrictions

GMH220 HW versions 1.0, 1.1, and 1.2 do not support 4, 8 or 64 frame buffers in Tellabs 8170 cluster nodes. USW 6.6 version does not support HCE-2M-1P and HCE-2M-2P modules. TS0 bit inversion. USW 6.6 version does not support BTE-320, BTE-576, BTE-1088-2W, BTE-2304 modules. An alarm will be generated when using x-connected time slot for HDLC. USW 6.6 version does not support DEG/EXC BER alarms. USW 6.6 version does not support micro BTS. USW 6.6 version does not support CAS at 2M < bit rate < 8M. Frequency difference alarm does not meet G.823 updated standard (1993). USW 6.6 version does not support BTE-2048-2W module. USW 6.6 version does not support AIS detection in unframed mode. USW 6.6 version does not support RAI-Xcon mode. USW 6.6 version does not support sync. line divider updating.
Bugs
Mismatch of 2 frame buffer with uneven bus allocation can occur if locked interface buffer length is changed then the CAS state is changed and finally buffer length is changed to 2 frame. Handling of erroneous message from VTP-bus. No alarm when neighbor makes V.54 loop. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist. Unnecessary Tx-Clock fault when using BTE-4096 module.
10004_22 2008 Tellabs.

103
9.8 Version 6.5

Dependencies
Restrictions

GMH220 HW versions 1.0, 1.1, and 1.2 do not support 4, 8 or 64 frame buffers in Tellabs 8170 cluster nodes. USW 6.5 version does not support HCE-2M-1P and HCE-2M-2P modules. TS0 bit inversion. USW 6.5 version does not support BTE-320, BTE-576, BTE-1088-2W, BTE-2304 modules. An alarm will be generated when using x-connected time slot for HDLC. USW 6.5 version does not support DEG/EXC BER alarms. USW 6.5 version does not support micro BTS. USW 6.5 version does not support CAS at 2M < bit rate < 8M. Frequency difference alarm does not meet G.823 updated standard (1993). USW 6.5 version does not support BTE-2048-2W module. USW 6.5 version does not support AIS detection in unframed mode. USW 6.5 version does not support RAI-Xcon mode. USW 6.5 version does not support sync. line divider updating.
Bugs
Mismatch of 2 frame buffer with uneven bus allocation can occur if locked interface buffer length is changed then the CAS state is changed and finally buffer length is changed to 2 frame. Handling of erroneous message from VTP-bus. No alarm when neighbor makes V.54 loop. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist. Context checker prevents 2 frame buffer usage (updating of parameters). Unnecessary Tx-Clock fault when using BTE-4096 module.

104
10004_22 2008 Tellabs.
9.9 Version 6.4

Dependencies
Restrictions

GMH220 HW versions 1.0, 1.1, and 1.2 do not support 4, 8 or 64 frame buffers in Tellabs 8170 cluster nodes. USW 6.4 version does not support HCE-2M-1P and HCE-2M-2P modules. TS0 bit inversion. USW 6.4 version does not support BTE-320, BTE-576, BTE-1088-2W, BTE-2304 modules. An alarm will be generated when using x-connected time slot for HDLC. USW 6.4 version does not support DEG/EXC BER alarms. USW 6.4 version does not support micro BTS. USW 6.4 version does not support CAS at 2M < bit rate < 8M. Frequency difference alarm does not meet G.823 updated standard (1993). USW 6.4 version does not support BTE-1088, BTE-4096, G703-75, G703-120, G703-8M modules. USW 6.4 version does not support BTE-384 module wetting current strapping info (in the new version BTE-384 strapping possibility). USW 6.4 version does not support preventing of VTP-bus corruption when the VTPoscillator fails. USW 6.4 version does not support BTE-2048-2W module. USW 6.4 version does not support AIS detection in unframed mode. USW 6.4 version does not support RAI-Xcon mode. USW 6.4 version does not support sync. line divider updating.
Bugs
Mismatch of 2 frame buffer with uneven bus allocation can occur if locked interface buffer length is changed then the CAS state is changed and finally buffer length is changed to 2 frame. Handling of erroneous message from VTP-bus. No alarm when neighbor makes V.54 loop. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist.
10004_22 2008 Tellabs.

105
9.10 Version 6.3

Dependencies
Restrictions

GMH220 HW versions 1.0, 1.1, and 1.2 do not support 4, 8 or 64 frame buffers in Tellabs 8170 cluster nodes. USW 6.3 version does not support HCE-2M-1P and HCE-2M-2P modules. TS0 bit inversion. USW 6.3 version does not support BTE-320, BTE-576, BTE-1088-2W, BTE-2304 modules. An alarm will be generated when using x-connected time slot for HDLC. USW 6.3 version does not support DEG/EXC BER alarms. USW 6.3 version does not support micro BTS. USW 6.3 version does not support CAS at 2M < bit rate < 8M. Frequency difference alarm does not meet G.823 updated standard (1993). USW 6.3 version does not support BTE-2048, V35-G704S and X21-G704S modules. USW 6.3 version does not support FSW-RAI usage: X-sync. USW 6.3 version does not support BTE-1088, BTE-4096, G703-75, G703-120, G703-8M modules. USW 6.3 version does not support BTE-384 module wetting current strapping info (in the new version BTE-384 strapping possibility). USW 6.3 version does not support preventing of VTP-bus corruption when the VTPoscillator fails. USW 6.3 version does not support BTE-2048-2W module. USW 6.3 version does not support AIS detection in unframed mode. USW 6.3 version does not support RAI-Xcon mode. USW 6.3 version does not support sync. line divider updating.
Bugs
Mismatch of 2 frame buffer with uneven bus allocation can occur if locked interface buffer length is changed then the CAS state is changed and finally buffer length is changed to 2 frame. Handling of erroneous message from VTP-bus. No alarm when neighbor makes V.54 loop. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist.

106
10004_22 2008 Tellabs.
When a unit gets different protection mode as backup settings from the SCU (after reset) it is possible that fault blocks 1 and 2 PMA and S alarm status are wrong (until next reset).
9.11 Version 6.2

Dependencies
Restrictions

GMH220 HW versions 1.0, 1.1, and 1.2 do not support 4, 8 or 64 frame buffers in Tellabs 8170 cluster nodes. USW 6.2 version does not support HCE-2M-1P and HCE-2M-2P modules. TS0 bit inversion. USW 6.2 version does not support BTE-320, BTE-576, BTE-1088-2W, BTE-2304 modules. An alarm will be generated when using x-connected time slot for HDLC. USW 6.2 version does not support DEG/EXC BER alarms. USW 6.2 version does not support micro BTS. USW 6.2 version does not support CAS at 2M < bit rate < 8M. Frequency difference alarm does not meet G.823 updated standard (1993). USW 6.2 version does not support V35-G704B and X21-G704 modules. USW 6.2 version does not support bit rate 33 x 64 kbit/s. USW 6.2 version does not support BTE-2048, V35-G704S and X21-G704S modules. USW 6.2 version does not support FSW-RAI usage: X-sync. USW 6.2 version does not support BTE-1088, BTE-4096, G703-75, G703-120, G703-8M modules. USW 6.2 version does not support BTE-384 module wetting current strapping info (in the new version BTE-384 strapping possibility). USW 6.2 version does not support preventing of VTP-bus corruption when the VTPoscillator fails. USW 6.2 version does not support BTE-2048-2W module. USW 6.2 version does not support AIS detection in unframed mode. USW 6.2 version does not support RAI-Xcon mode. USW 6.2 version does not support sync. line divider updating.
10004_22 2008 Tellabs.

107
Bugs
Mismatch of 2 frame buffer with uneven bus allocation can occur if locked interface buffer length is changed then the CAS state is changed and finally buffer length is changed to 2 frame. Handling of erroneous message from VTP-bus. No alarm when neighbor makes V.54 loop. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist. When a unit gets different protection mode as backup settings from the SCU (after reset) it is possible that fault blocks 1 and 2 PMA and S alarm status are wrong (until next reset).
9.12 Version 6.1

Dependencies
Restrictions

GMH220 HW versions 1.0, 1.1 and 1.2 do not support 4, 8 or 64 frame buffers in Tellabs 8170 cluster nodes. USW 6.1 version does not support HCE-2M-1P and HCE-2M-2P modules. TS0 bit inversion. USW 6.1 version does not support BTE-320, BTE-576, BTE-1088-2W, BTE-2304 modules. An alarm will be generated when using x-connected time slot for HDLC. USW 6.1 version does not support DEG/EXC BER alarms. USW 6.1 version does not support micro BTS. USW 6.1 version does not support CAS at 2M < bit rate < 8M. Frequency difference alarm does not meet G.823 updated standard (1993). USW 6.1 version does not support V35-G704B and X21-G704 modules. USW 6.1 version does not support bit rate 33 x 64 kbit/s. USW 6.1 version does not support BTE-2048, V35-G704S and X21-G704S modules. USW 6.1 version does not support FSW-RAI usage: X-sync. USW 6.1 version does not support BTE-1088, BTE-4096, G703-75, G703-120, G703-8M modules. USW 6.1 version does not support BTE-384 module wetting current strapping info (in the new version BTE-384 strapping possibility). USW 6.1 version does not support preventing of VTP-bus corruption when the VTPoscillator fails.

108
10004_22 2008 Tellabs.
USW 6.1 version does not support BTE-2048-2W module. USW 6.1 version does not support AIS detection in unframed mode. USW 6.1 version does not support RAI-Xcon mode. USW 6.1 version does not support sync. line divider updating.
Bugs
Mismatch of 2 frame buffer with uneven bus allocation can occur if locked interface buffer length is changed then the CAS state is changed and finally buffer length is changed to 2 frame. Handling of erroneous message from VTP-bus. No alarm when neighbor makes V.54 loop. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist. Fault mask alarm with S status which will start the recovery operation. Does not support ring synchronization. Does not support signalling when bit rate is 1831 x 64 kbit/s. When a unit gets different protection mode as backup settings from the SCU (after reset) it is possible that fault blocks 1 and 2 PMA and S alarm status are wrong (until next reset).
9.13 Version 5.8

Dependencies
Restrictions

GMH220 HW versions 1.0, 1.1 and 1.2 do not support 4, 8 or 64 frame buffers in Tellabs 8170 cluster nodes. USW 5.8 version does not support HCE-2M-1P and HCE-2M-2P modules. TS0 bit inversion . USW 5.8 version does not support BTE-320, BTE-576, BTE-1088-2W, BTE-2304 modules. An alarm will be generated when using x-connected time slot for HDLC. USW 5.8 version does not support DEG/EXC BER alarms. USW 5.8 version does not support micro BTS. USW 5.8 version does not support CAS at 2M < bit rate < 8M. Frequency difference alarm does not meet G.823 updated standard (1993). USW 5.8 version does not support V35-G704B and X21-G704 modules.
10004_22 2008 Tellabs.

109
USW 5.8 version does not support V35-G704 and V36-G704 modules nor BTE-768 modules. USW 5.8 version does not support bit rate 33 x 64 kbit/s. USW 5.8 version does not support 1+1 protected trunks. USW 5.8 version does not support BTE-2048, V35-G704S and X21-G704S modules. USW 5.8 version does not support FSW-RAI usage: X-sync. USW 5.8 version does not support BTE-1088, BTE-4096, G703-75, G703-120, G703-8M modules. USW 5.8 version does not support BTE-384 module wetting current strapping info (in the new version BTE-384 strapping possibility). USW 5.8 version does not support preventing of VTP-bus corruption when the VTPoscillator fails. USW 5.8 version does not support BTE-2048-2W module. USW 5.8 version does not support AIS detection in unframed mode. USW 5.8 version does not support RAI-Xcon mode. USW 5.8 version does not support sync. line divider updating.
Bugs
Mismatch of 2 frame buffer with uneven bus allocation can occur if locked interface buffer length is changed then the CAS state is changed and finally buffer length is changed to 2 frame. Handling of erroneous message from VTP-bus. No alarm when neighbor makes V.54 loop. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist. When a unit gets different protection mode as backup settings from the SCU (after reset) it is possible that fault blocks 1 and 2 PMA and S alarm status are wrong (until next reset).
9.14 Version 5.7

Dependencies
Restrictions

GMH220 HW versions 1.0, 1.1 and 1.2 do not support 4, 8 or 64 frame buffers in Tellabs 8170 cluster nodes. USW 5.7 version does not support HCE-2M-1P and HCE-2M-2P modules. TS0 bit inversion. USW 5.7 version does not support BTE-320, BTE-576, BTE-1088-2W, BTE-2304 modules.
10004_22 2008 Tellabs.

110
An alarm will be generated when using x-connected time slot for HDLC. USW 5.7 version does not support DEG/EXC BER alarms. USW 5.7 version does not support micro BTS. USW 5.7 version does not support CAS at 2M < bit rate < 8M. Frequency difference alarm does not meet G.823 updated standard (1993). USW 5.7 version does not support V35-G704B nor X21-G704 modules. USW 5.7 version does not support V35-G704 nor V36-G704 modules nor BTE-768 modules. USW 5.7 version does not support bit rate 33 x 64 kbit/s. USW 5.7 version does not support 1+1 protected trunks. USW 5.7 version does not support BTE-2048, V35-G704S and X21-G704S modules. USW 5.7 version does not support FSW-RAI usage: X-sync. USW 5.7 version does not support BTE-1088, BTE-4096, G703-75, G703-120, G703-8M modules. USW 5.7 version does not support BTE-384 module wetting current strapping info (in the new version BTE-384 strapping possibility). USW 5.7 version does not support preventing of VTP-bus corruption when the VTPoscillator fails. USW 5.7 version does not support BTE-2048-2W module. USW 5.7 version does not support AIS detection in unframed mode. USW 5.7 version does not support RAI-Xcon mode. USW 5.7 version does not support sync. line divider updating.
Bugs
Mismatch of 2 frame buffer with uneven bus allocation can occur if locked interface buffer length is changed, then the CAS state is changed and finally buffer length is changed to 2 frame. Handling of erroneous message from VTP-bus. No alarm when neighbor makes V.54 loop. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist. Fault mask alarm with S status which will start the recovery operation. USW 5.7 version does not support ring synchronization. USW 5.7 version does not support signalling when bit rate is 1831 x 64 kbit/s. When a unit gets different protection mode as backup settings from the SCU (after reset) it is possible that fault blocks 1 and 2 PMA and S alarm status are wrong (until next reset).
10004_22 2008 Tellabs.

111
9.15 Version 5.5

Dependencies
Restrictions

GMH220 HW versions 1.0, 1.1 and 1.2 do not support 4, 8 or 64 frame buffers in Tellabs 8170 cluster nodes. USW 5.5 version does not support HCE-2M-1P and HCE-2M-2P modules. TS0 bit inversion. USW 5.5 version does not support BTE-320, BTE-576, BTE-1088-2W, BTE-2304 modules. An alarm will be generated when using x-connected time slot for HDLC. USW 5.5 version does not support DEG/EXC BER alarms. USW 5.5 version does not support micro BTS. USW 5.5 version does not support CAS at 2M < bit rate < 8M. Frequency difference alarm does not meet G.823 updated standard (1993). USW 5.5 version does not support V35-G704B nor X21-G704 modules. USW 5.5 version does not support V35-G704 nor V36-G704 modules nor BTE-768 modules. USW 5.5 version does not support bit rate 33 x 64 kbit/s. USW 5.5 version does not support 1+1 protected trunks. USW 5.5 version does not support BTE-2048, V35-G704S and X21-G704S modules. USW 5.5 version does not support FSW-RAI usage: X-sync. USW 5.5 version does not support BTE-1088, BTE-4096, G703-75, G703-120, G703-8M modules. USW 5.5 version does not support BTE-384 module wetting current strapping info (in the new version BTE-384 strapping possibility). USW 5.5 version does not support preventing of VTP-bus corruption when the VTPoscillator fails. USW 5.5 version does not support BTE-2048-2W module. USW 5.5 version does not support AIS detection in unframed mode. USW 5.5 version does not support RAI-Xcon mode. USW 5.5 version does not support sync. line divider updating.

112
10004_22 2008 Tellabs.
Bugs
Mismatch of 2 frame buffer with uneven bus allocation can occur if locked interface buffer length is changed then the CAS state is changed and finally buffer length is changed to 2 frame. Handling of erroneous message from VTP-bus. No alarm when neighbor makes V.54 loop. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist. Does not support split trunk usage. Fault mask alarm with S status which will start the recovery operation. USW 5.5 version does not support ring synchronization. USW 5.5 version Does not support signalling when bit rate is 1831 x 64 kbit/s. When a unit gets different protection mode as backup settings from the SCU (after reset) it is possible that fault blocks 1 and 2 PMA and S alarm status are wrong (until next reset).
9.16 Version 5.2

Dependencies
Restrictions

GMH220 HW versions 1.0, 1.1 and 1.2 do not support 4, 8 or 64 frame buffers in Tellabs 8170 cluster nodes. USW 5.2 version does not support HCE-2M-1P and HCE-2M-2P modules. TS0 bit inversion. USW 5.2 version does not support BTE-320, BTE-576, BTE-1088-2W, BTE-2304 modules. An alarm will be generated when using x-connected time slot for HDLC. USW 5.2 version does not support DEG/EXC BER alarms. USW 5.2 version does not support micro BTS. USW 5.2 version does not support CAS at 2M < bit rate < 8M. Frequency difference alarm does not meet G.823 updated standard (1993). USW 5.2 version does not support V35-G704B nor X21-G704 modules. USW 5.2 version does not support V35-G704 nor V36-G704 modules nor BTE-768 modules. USW 5.2 version does not support bit rate 33 x 64 kbit/s. USW 5.2 version does not support 1+1 protected trunks. USW 5.2 version does not support BTE-2048, V35-G704S and X21-G704S modules.
10004_22 2008 Tellabs.

113
USW 5.2 version does not support FSW-RAI usage: X-sync. USW 5.2 version does not support BTE-1088, BTE-4096, G703-75, G703-120, G703-8M modules. USW 5.2 version does not support BTE-384 module wetting current strapping info (in the new version BTE-384 strapping possibility). USW 5.2 version does not support preventing of VTP-bus corruption when the VTPoscillator fails. USW 5.2 version does not support BTE-2048-2W module. USW 5.2 version does not support AIS detection in unframed mode. USW 5.2 version does not support RAI-Xcon mode. USW 5.2 version does not support sync. line divider updating.
Bugs
Mismatch of 2 frame buffer with uneven bus allocation can occur if locked interface buffer length is changed then the CAS state is changed and finally buffer length is changed to 2 frame. Handling of erroneous message from VTP-bus. No alarm when neighbor makes V.54 loop. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist. USW 5.2 version does not support split trunk usage. USW 5.2 version does not support Tellabs 8170 cluster nodes. Fault mask alarm with S status which will start the recovery operation. USW 5.2 version does not support ring synchronization. USW 5.2 version does not support signalling when bit rate is 1831 x 64 kbit/s. When a unit gets different protection mode as backup settings from the SCU (after reset) it is possible that fault blocks 1 and 2 PMA and S alarm status are wrong (until next reset).

114
10004_22 2008 Tellabs.
9.17 Version 5.1

Dependencies
Restrictions

GMH220 HW versions 1.0, 1.1 and 1.2 do not support 4, 8 or 64 frame buffers in Tellabs 8170 cluster nodes. USW 5.1 version does not support HCE-2M-1P and HCE-2M-2P modules. TS0 bit inversion. USW 5.1 version does not support BTE-320, BTE-576, BTE-1088-2W, BTE-2304 modules. An alarm will be generated when using x-connected time slot for HDLC. USW 5.1 version does not support DEG/EXC BER alarms. USW 5.1 version does not support micro BTS. USW 5.1 version does not support CAS at 2M < bit rate < 8M. Frequency difference alarm does not meet G.823 updated standard (1993). USW 5.1 version does not support V35-G704B nor X21-G704 modules. USW 5.1 version does not support V35-G704 nor V36-G704 nor BTE-768 modules. USW 5.1 version does not support bit rate 33 x 64 kbit/s. USW 5.1 version does not support 1+1 protected trunks. USW 5.1 version does not support BTE-2048, V35-G704S and X21-G704S modules. USW 5.1 version does not support FSW-RAI usage: X-sync. USW 5.1 version does not support BTE-1088, BTE-4096, G703-75, G703-120, G703-8M modules. USW 5.1 version does not support BTE-384 module wetting current strapping info (in the new version BTE-384 strapping possibility). USW 5.1 version does not support preventing of VTP-bus corruption when the VTPoscillator fails. USW 5.1 version does not support BTE-2048-2W module. USW 5.1 version does not support AIS detection in unframed mode. USW 5.1 version does not support RAI-Xcon mode. USW 5.1 version does not support sync. line divider updating.
10004_22 2008 Tellabs.

115
Bugs
Mismatch of 2 frame buffer with uneven bus allocation can occur if locked interface buffer length is changed then the CAS state is changed and finally buffer length is changed to 2 frame. Handling of erroneous message from VTP-bus. No alarm when neighbour makes V.54 loop. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist. USW 5.1 version does not support BTE Rx level and quality info. USW 5.1 version does not support GDH 75/120 info (GDH module version 4.0) USW 5.1 version does not generate multiframe far-end alarm to the NMS. Sending of CRCE bits at permanent 0 and 1 state fails. USW 5.1 version does not support Tellabs 8170 cluster nodes. USW 5.1 version does not support split trunk usage. Fault mask alarm with S status which will start the recovery operation. USW 5.1 version does not support ring synchronization. USW 5.1 version does not support signalling when the bit rate is 1831 x 64 kbit/s. When a unit gets different protection mode as backup settings from the SCU (after reset) it is possible that fault blocks 1 and 2 PMA and S alarm status are wrong (until next reset).

116
10004_22 2008 Tellabs.
GMM Unit: GMZ438 Unit Software
10 GMM Unit: GMZ438 Unit Software

The software GMZ438 is used on GMM unit (whose base unit is GMM253) in the Tellabs 8140 midi, Tellabs 8150 basic, Tellabs 8160 A111 and Tellabs 8170 cluster nodes. The version 2.3 can be downloaded to GMM units having the version 2.y of GMZ438 (where y=0, 1, 2...).
10.1 Version 2.3

When a unit is in a red alarm state and the defect causing the state disappears, the trunk conditioning should be removed immediately. Previously trunk conditioning wasnt removed until the red alarm disappeared. (CR ID 300042935)
Dependencies

GMM unit (GMM253) hardware version must be 1.x GDM298 hardware version must be 1.x CCU (SCZ286) software version can be any version. SCP (SCZ281) software version can be any version. SCU (SCZ280) software version can be any version. SCU-H (SCZ545) software version can be any version. XCG (SMZ538) software version can be any version. GMH (GMZ283) software version can be any version. CXU-M (SXZ288) software version can be any version. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version must be 6.5 or higher. SXU-C (SXZ289) software version must be 2.6 or higher. SXU-V (SXZ630) software version 1.1 or higher MartisDXX Manager should be Release 8.0a or higher.
10004_22 2008 Tellabs.

117
Restrictions

If a red alarm condition arises during a yellow alarm, TR170 says that the red alarm should be declared without idling the yellow. Instead, the unit in fact does idle the yellow. Another minor deviation from TR170: if LOF is injected on top of AIS then AIS is cleared before LOF is declared. In G802 mode if an incoming alarm causes AIS and is then removed the AIS is turned off immediately instead of waiting the full decay period. If protection is forced to the active interface during the delay prior to a switchover then the switchover will happen anyway. In CSU TR54016, if a payload loopback is setup and the interface configuration is subsequently changed to full CSU then the status returned in subsequent TR54016 queries does not report loopback. The NMS and T1.403 reports do indicate the correct situation. If a signalling connection is setup, with a Remote Line Loop already active, the signalling will not pass correctly until the Loop is removed.
Bugs
No known bugs.
10.2 Version 2.2

GMM T1 IF fault state is not updated correctly. The T1 transceivers in the GDM 298 module do not always initialize properly. (CR ID 200012722)
Dependencies

GMM unit (GMM253) hardware version must be 1.x GDM298 hardware version must be 1.x CCU (SCZ286) software version can be any version. SCP (SCZ281) software version can be any version. SCU (SCZ280) software version can be any version. SCU-H (SCZ545) software version can be any version. XCG (SMZ538) software version can be any version. GMH (GMZ283) software version can be any version. CXU-M (SXZ288) software version can be any version. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version must be 6.5 or higher. SXU-C (SXZ289) software version must be 2.6 or higher. SXU-V (SXZ630) software version 1.1 or higher

118
10004_22 2008 Tellabs.
MartisDXX Manager should be Release 8.0a or higher.
Restrictions

Bugs
When a unit is in a red alarm state and the defect causing the state disappears, the trunk conditioning should be removed immediately. (CR ID 300042935)
10.3 Version 2.1

Supports 1536K reference clock for node.
Dependencies

GMM253 hardware version must be 1.x GDM298 hardware version must be 1.x CCU (SCZ286) software version can be any version. SCP (SCZ281) software version can be any version. SCU (SCZ280) software version can be any version. SCU-H (SCZ545) software version can be any version. XCG (SMZ538) software version can be any version. GMH (GMZ283) software version can be any version. CXU-M (SXZ288) software version can be any version. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version must be 6.5 or higher. SXU-C (SXZ289) software version must be 2.6 or higher.
10004_22 2008 Tellabs.

119
MartisDXX Manager should be Release 8.0a or higher.
Restrictions

Bugs
GMM T1 IF fault state is not updated correctly. The T1 transceivers in the GDM 298 module not do not always initialize properly. (CR ID 200012722)
10.4 Version 2.0

Dependencies

GMM253 hardware version must be 1.x GDM298 hardware version must be 1.x CCU (SCZ286) software version can be any version. SCP (SCZ281) software version can be any version. SCU (SCZ280) software version can be any version. SCU-H (SCZ545) software version can be any version. XCG (SMZ538) software version can be any version. GMH (GMZ283) software version can be any version. CXU-M (SXZ288) software version can be any version. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version must be 6.5 or higher. SXU-C (SXZ289) software version must be 2.6 or higher. MartisDXX Manager should be Release 8.0a or higher.

120
10004_22 2008 Tellabs.
Restrictions

Bugs
Does not support 1536K reference clock for node.
10004_22 2008 Tellabs.

121
GMU and GMU-A Units: GMZ460 Unit Software
11 GMU and GMU-A Units: GMZ460 Unit Software

Two software products are needed on GMU and GMU-A units in Tellabs 8140 midi, Tellabs 8150 basic, Tellabs 8160 A111 and Tellabs 8170 cluster nodes. Software GMZ460 is for the main processor and software GMZ461 is for the ASIC processor. GMZ460 version 1.8 can be downloaded to GMU-A or GMU having the version 1.y of GMZ460 (where y=0, 1, 2...). GMU is composed of GMU450 v1.0 and DSU453 v1.0 boards. Base unit hardware version is 1.0. GMU-A is composed of GMU450 v1.0 and DSU453 v2.0 boards. Base unit hardware version is 2.0 or higher.
11.1 Version 1.8

Applies to GMU-A only: when X-bus distribution is set to 'even' while P12s signal mapping mode is 'asynchronous', 'uneven' X-bus distribution is used however. This is because of a bug in LTA ASIC causing the combination of X-bus distribution being 'even' and P12s signal mapping mode being 'asynchronous' for VC12 not to work reliably in all situations (CR ID 200011752). Applies to GMU-A only: now it is not possible to cause illegal VC-12-mc configuration by using Tellabs 8100 network managers Node Manager copy/paste from a single VC12 (asynchronous mode) into VC12-mc/VC-12 (CR ID 200011098). Applies to GMU-A only: SYN-34-E interface module works also for GMU-A (CR ID 200011636). SYN-34-E interface module internal test does not fail unintentionally and no fault Initialization error (GMZ461) is produced anymore (CR ID 200004414, 200011635, 200011636). Fixed wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303, 200011641). Fixed corruption of Rx buffer centring, which caused traffic degradation in GMU (CR ID 200007236), (Technical note ID SOL2005).

122
10004_22 2008 Tellabs.
Dependencies

GMU hardware version must be 1.0. GMU-A hardware version must be 2.0 or higher. GMZ461 software version must be 1.8 or higher. CCU (SCZ286) software version can be any version. SCP (SCZ281) software version must be 3.1 or higher. SCU software version must be 8.5 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.1 or higher. CXU-M (SXZ288) software version must be 2.7 or higher. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version must be 6.8 or higher. SXU-C (SXZ289) software version must be 2.7 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. GMU-A specific features, asynchronous mapping, P12s termination and V5.2 voice support, are supported only by GMU-A, but not by GMU. MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher. MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher. GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12.
Restrictions

It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Before inserting GMU unit into a slot where GMU-A has been (in the inventory), it is absolutely necessary to do "Remove from Inventory" for GMU-A. Performance threshold values are not according to the EN 301 167 v.1.1.1 standard on multiplex section (MS) layer. On MS layer, background block error (BBE) count is not according to the standard due to hardware restrictions. In GMU-A standard method can be used if BIP-1 based MS block error calculation is selected (CRF ID 4003017). BIP-1 / BIP-24 block size based MS operation is supported only by GMU-A with Tellabs 8100 Network Manager Release 13A or higher (CRF ID 4003330, CR ID 200004858).
Bugs
Tellabs 8100 control channel is not working in VC-2/VC-12 payload, if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335, CR ID 200005084).
10004_22 2008 Tellabs.

123
11.2 Version 1.179

This is a non-production version based on version 1.7. NOTE: Do not download this software in GMU-A. This software is intended for GMU only. Enhancements and Fixed Bugs
Fixed corruption of Rx buffer centring, which caused traffic degradation in GMU (CR ID 200007236), (Technical note ID SOL2005).
Dependencies

GMU hardware version must be 1.0. GMZ461 software version must be 1.179. CCU (SCZ286) software version can be any version. SCP (SCZ281) software version must be 3.1 or higher. SCU software version must be 8.5 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.1 or higher. CXU-M (SXZ288) software version must be 2.7 or higher. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version must be 6.8 or higher. SXU-C (SXZ289) software version must be 2.7 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. GMU-A specific features, asynchronous mapping, P12s termination and V5.2 voice support, are supported only by GMU-A, but not by GMU.
Restrictions

Do not download this software version in GMU-A. This software is intended for GMU only. It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Before inserting GMU unit into a slot where GMU-A has been (in the inventory), it is absolutely necessary to do "Remove from Inventory" for GMU-A. Performance threshold values are not according to the EN 301 167 v.1.1.1 standard on multiplex section (MS) layer. On MS layer, background block error (BBE) count is not according to the standard due to hardware restrictions. In GMU-A standard method can be used if BIP-1 based MS block error calculation is selected (CRF ID 4003017).
Bugs
Tellabs 8100 control channel is not working in VC-2/VC-12 payload, if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335, CR ID 200005084).
10004_22 2008 Tellabs.

124
11.3 Version 1.7

NOTE: Do not download this software in GMU. This software is intended for GMU-A only. Enhancements and Fixed Bugs

Enhancement in performance data collection. If 15-minute performance counter has other value than zero, a delta-type alarm is set active (CRF ID 4003054). BIP-1/BIP-24 block size based MS operation in GMU-A (CRF ID 4003330, CR ID 200004858). G.826 performance monitoring data is collected also when TU cross-connection is missing (CRF ID 4004714). Extended production test support (CRF ID 4004928). If fault event reporting is defined for a VC-12, also P12 layer fault events are reported. P12 layer fault reporting enhanced. Fixed flash corruption problem (CRF ID 4005110). Fixed fault classification of UNAVAIL, QOS and QOSTR faults (CRF ID 4003428). Fault reporting bug fixed, some faults were never reported (CRF ID 4005206, CR ID 200005406). Fix in node master clock rank: illegal value 0 was sometimes reported to neighbour nodes. Fixed incorrect MLOF alarm with asynchronous SNC/N protected VC-12 with Channel Associated Signalling and P12s termination (CR ID 200005740).
Dependencies

GMU-A hardware version must be 2.0 or higher. GMZ461 software version must be 1.7. CCU (SCZ286) software version can be any version. SCP (SCZ281) software version must be 3.1 or higher. SCU software version must be 8.5 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.1 or higher. CXU-M (SXZ288) software version must be 2.7 or higher. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version must be 6.8 or higher. SXU-C (SXZ289) software version must be 2.7 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher. MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher.
125
10004_22 2008 Tellabs.
GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12.
Restrictions

It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Before inserting GMU unit into a slot where GMU-A has been (in the inventory), it is absolutely necessary to do "Remove from Inventory" for GMU-A. Performance threshold values are not according to the EN 301 167 v.1.1.1 standard on multiplex section (MS) layer. On MS layer, background block error (BBE) count is not according to the standard due to hardware restrictions. In GMU-A standard method can be used if BIP-1 based MS block error calculation is selected (CRF ID 4003017). BIP-1 / BIP-24 block size based MS operation is supported only by GMU-A with Tellabs 8100 Network Manager Release 13A or higher (CRF ID 4003330, CR ID 200004858).
Bugs

SYN-34-E interface module does not work reliably (CR ID 200011636). SYN-34-E interface module internal test fails unintentionally and produces fault Initialization error (GMZ461) (CR ID 200004414, 200011635, 200011636). It is possible to cause illegal VC-12-mc configuration by using Tellabs 8100 network managers Node Manager copy/paste from a single VC12 (asynchronous mode) into VC12mc/VC-12 (CR ID 200011098). Because of a bug in LTA ASIC, the combination of X-bus distribution being even and P12s signal mapping mode being asynchronous for VC12 does not work reliably in all situations (CR ID 200011752). Tellabs 8100 control channel is not working in VC-2/VC-12 payload, if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335, CR ID 200005084). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303).
11.4 Version 1.6


Asynchronous 2 Mbit/s signal mapping. P12s (G.704) termination. V5.2 voice interface support in Tellabs 8150 basic node. SS bit values in AU4 pointer do not have to be 10 anymore. Therefore, this software version can be used to connect GMU-A to SONET equipment (CRF ID 4004547). Transmitted NU2 byte in STM1 RSOH is balanced, i.e. it has equal number of 0 and 1 bits (value 0xAA). The byte can also be set with Tellabs 8100 Network Manager (interface window/overhead bytes) (CRF ID 4003371).

126
10004_22 2008 Tellabs.
GMU-A does not cause Unit IA fault in Tellabs 8160 A111 after power up (CRF ID 4004646). Performance monitoring thresholds lower BBE, ES, SES and secSesThreshold are compared correctly (CRF ID 4004442).
Dependencies

GMU-A hardware version must be 2.0 or higher. GMZ461 software version must be 1.6. CCU (SCZ286) software version can be any version. SCP (SCZ281) software version must be 3.1 or higher. SCU software version must be 8.5 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.1 or higher. CXU-M (SXZ288) software version must be 2.7 or higher. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version must be 6.8 or higher. SXU-C (SXZ289) software version must be 2.7 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher. MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher. GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12.
Restrictions

It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Performance threshold values are not according to the EN 301 167 v.1.1.1 standard on multiplex section (MS) layer. On MS layer, background block error (BBE) count is not according to the standard due to hardware restrictions. Other threshold values (ES and SES) are according to the standard. Threshold values on other layers (RS, VC-4, VC-2, VC-12) are according to the standard. Note: if software is downloaded to existing GMU-A, execution of Factory settings is required for this feature (CRF ID 4003017).
Bugs

SYN-34-E interface module does not work reliably (CR ID 200011636). SYN-34-E interface module internal test fails unintentionally and produces fault Initialization error (GMZ461). However, this fault is not shown by Tellabs 8100 network manager because of fault reporting bug CRF ID 4005206, CR ID 200005406 (CR ID 200004414, 200011635, 200011636).
10004_22 2008 Tellabs.

127
It is possible to cause illegal VC-12-mc configuration by using Tellabs 8100 network managers Node Manager copy/paste from a single VC12 (asynchronous mode) into VC12mc/VC-12 (CR ID 200011098). Because of a bug in LTA ASIC, the combination of X-bus distribution being even and P12s signal mapping mode being asynchronous for VC12 does not work reliably in all situations (CR ID 200011752). Incorrect MLOF alarm is reported with asynchronous SNC/N protected VC-12 with Channel Associated Signalling and P12s termination (CR ID 200005740). Tellabs 8100 control channel is not working in VC-2/VC-12 payload, if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335, CR ID 200005084). Flash corruption problem (CRF ID 4005110). Wrong fault classification of UNAVAIL, QOS and QOSTR faults (CRF ID 4003428). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303). Fault reporting bug, some faults are never reported (CRF ID 4005206, CR ID 200005406). Node master clock rank is sometimes reported as illegal value 0 to neighbour nodes.
11.5 Version 1.102


GMU does not cause Unit IA fault in Tellabs 8160 A111 after power up (CRF ID 4004646). SS bit values in AU4 pointer do not have to be 10 anymore. Therefore, this software version can be used to connect GMU to SONET equipment (CRF ID 4004547). Transmitted NU2 byte in STM1 RSOH is balanced, i.e. it has equal number of 0 and 1 bits (value 0xAA). The byte can also be set with Tellabs 8100 Network Manager (interface window/overhead bytes) (CRF ID 4003371).
Dependencies

SCU software version must be at least 8.5. SCP software version must be at least 3.1. SXU-A/B software version must be at least 6.8. SXU-C software version must be at least 2.7. CXU-M software version must be at least 2.7. XCG software version must be at least 2.1. GMZ461 software version must be 1.102

128
10004_22 2008 Tellabs.
Restrictions

Software can not be downloaded to GMU-A. It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Versions 1.4 and later of GMU support advanced SNC group configuration but in MartisDXX Manager NMS this feature is supported in Release 10.0 and later. If SNC groups are configured by earlier NMS versions, this may cause inconsistency between database and hardware. The user can minimize this problem by configuring monitoring TTPs of an SNC group to have the same values as the terminating TTP.
Bugs

Tellabs 8100 control channel is not working in VC-2/VC-12 payload, if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335, CR ID 200005084). Flash corruption problem (CRF ID 4005110). Wrong fault classification of UNAVAIL, QOS and QOSTR faults (CRF ID 4003428). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303). Node master clock rank is sometimes reported as illegal value 0 to neighbour nodes. Performance monitoring thresholds lower BBE, ES, SES and secSesThreshold are compared incorrectly (CRF ID 4004442).
11.6 Version 1.5

NOTE: Do not download this software in GMU-A. This software is intended for GMU only. Dependencies

SCU software version must be at least 8.5. SCP software version must be at least 3.1. SXU-A/B software version must be at least 6.8. SXU-C software version must be at least 2.7. CXU-M software version must be at least 2.7. XCG software version must be at least 2.1. GMZ461 software version must be 1.5.
10004_22 2008 Tellabs.

129
Restrictions

Software can not be downloaded to GMU-A. It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Versions 1.4 and later of GMU support advanced SNC group configuration but in MartisDXX Manager NMS this feature is supported in Release 10.0 and later. If SNC groups are configured by earlier NMS versions, this may cause inconsistency between database and hardware. The user can minimize this problem by configuring monitoring TTPs of an SNC group to have the same values as the terminating TTP. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547).
Bugs

Tellabs 8100 control channel is not working in VC-2/VC-12 payload, if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335, CR ID 200005084). Flash corruption problem (CRF ID 4005110). Wrong fault classification of UNAVAIL, QOS and QOSTR faults (CRF ID 4003428). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303). Node master clock rank is sometimes reported as illegal value 0 to neighbour nodes. GMU causes Unit IA fault in Tellabs 8160 A111 after power up (CRF ID 4004646). Performance monitoring thresholds lower BBE, ES, SES and secSesThreshold are compared incorrectly (CRF ID 4004442).
11.7 Version 1.4



130
10004_22 2008 Tellabs.
Restrictions

Software can not be downloaded to GMU-A. It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Control channel in VC payload is not supported. Version 1.4 of GMU supports advanced SNC group configuration but in MartisDXX Manager NMS this feature is supported in Release 10.0 and later. If SNC groups are configured by earlier NMS versions, this may cause inconsistency between database and hardware. The user can minimize this problem by configuring monitoring TTPs of an SNC group to have the same values as the terminating TTP. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547).
Bugs

Flash corruption problem (CRF ID 4005110). Wrong fault classification of UNAVAIL, QOS and QOSTR faults (CRF ID 4003428). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303). Node master clock rank is sometimes reported as illegal value 0 to neighbour nodes. The performance management system of GMU fails to detect alarms from far end when receiving alarms from near end. Expected TI, CAS, signal degrade seconds, signal degrade threshold and TIMaAisenabled attributes cannot be changed in VCgtp if SNC/I protection is used. AIS fault of SYN-34-E interface module does not work. Recovery does not work between GMUs when they are located in Tellabs 8150 basic node. CAS signaling does not go through GMU. CAS signaling does not work, if GMU is moved from Tellabs 8150 basic node to Tellabs 8170 cluster node or vice versa. Group DEG does not work with SNC/N protection. Spontaneous messages do not work, if GMU is a replacement unit. Spontaneous messages of TU12Ctps do not work. GMU causes Unit IA fault in Tellabs 8160 A111 after power up (CRF ID 4004646). Performance monitoring thresholds lower BBE, ES, SES and secSesThreshold are compared incorrectly (CRF ID 4004442).
10004_22 2008 Tellabs.

131
11.8 Version 1.3


SCU software version must be at least 8.3. SCP software version must be at least 3.0. SXU-A/B software version must be at least 6.8. SXU-C software version must be at least 2.7. CXU-M software version must be at least 2.7. GMZ461 software version must be 1.3.
Restrictions

Software can not be downloaded to GMU-A. It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Control channel in VC payload is not supported. Advanced SNC configuration is not supported. X-bus slip counters of VC2s and VC12s are not supported. SCU backuping is not supported. XCG is not supported. SSM enabling and disabling are not supported. The supervisory unequipped feature of VC2 and VC12 is not supported. Configurable TIM consequent actions are not supported. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547).
Bugs

Flash corruption problem (CRF ID 4005110). Wrong fault classification of UNAVAIL, QOS and QOSTR faults (CRF ID 4003428). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303). Node master clock rank is sometimes reported as illegal value 0 to neighbour nodes. Ps34M performance thresholds are seen as MS thresholds if SYN-34-E interface module is configured. If 34M-PsTTP alarm is activated and fault declare value is between 1-9, TU12-LOMs exist for a short time. Monitoring VCs of SNC group do not count far end bit errors.

132
10004_22 2008 Tellabs.
In case of SNCP monitoring VCs have fault status PMA although it should be DMA. NNM1 alarms are seen as NNM2 alarms and NNM2 does not give alarms. NNM gives an alarm even if there is no corresponding control channel. If MS 1+1 protection is active, all read and write operations to interface loops are denied. VC4 LOM affects the performance data of VC4s. VC4 SLM, VC4 UNEQ, 34M SLM and 34M UNEQ alarms may exist without a reason. This may occur when signal quality is very bad. Attribute waitToRestoreTime affects SNPO switch even if there has been manual switch. The attribute should affect SNPO switch only after SF/SD switch. If SNPO switch is revertive and waitToRestore state is on, switchStatus of protecting side is in wait-to-restore state. It should be in No Request state. If MS-AIS is received, SSF should be set too in MSTTPBid. If VC4 TIM or LOM is active, the received trace identifier J1 is masked to NULL. After GMU reset RS and VC4 AIS mask is not set on in case of dTIM. The performance management system of GMU fails to detect alarms from far end when receiving alarms from near end. The AIS fault of SYN-34-E interface module does not work. Recovery does not work between GMUs when they are located in Tellabs 8150 basic node. CAS signaling does not go through GMU. CAS signaling does not work, if GMU is moved from Tellabs 8150 basic node to Tellabs 8170 cluster node or vice versa. Group DEG does not work with SNC/N protection. Spontaneous messages do not work, if GMU is a replacement unit. Spontaneous messages of TU12Ctps do not work. GMU causes Unit IA fault in Tellabs 8160 A111 after power up (CRF ID 4004646). Performance monitoring thresholds lower BBE, ES, SES and secSesThreshold are compared incorrectly (CRF ID 4004442).
11.9 Version 1.2


10004_22 2008 Tellabs.

133
Restrictions

Software can not be downloaded to GMU-A. It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Control channel in VC payload is not supported. The SYN-34-E interface module is not supported. Advanced SNC configuration is not supported. X-bus slip counters of VC2s and VC12s are not supported. SCU backuping is not supported. XCG is not supported. SSM enabling and disabling are not supported. The supervisory unequipped feature of VC2 and VC12 is not supported. Configurable TIM consequent actions are not supported. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547).
Bugs

Flash corruption problem (CRF ID 4005110). Wrong fault classification of UNAVAIL, QOS and QOSTR faults (CRF ID 4003428). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303). Node master clock rank is sometimes reported as illegal value 0 to neighbour nodes. 522 bytes of a non-volatile setting are not sent to SCU, this means that part of spontaneous event reporting configurations are not backed up. If an equipment loop is set and LOS is detected, RS-AIS is still sent to the RX direction and SSF is set to the lower level instances. After 1+1 multiplex section protection switch VC2/12s could have an SSF fault without a reason. If vcGtp is set to lock state and one VC locking fails, all VCs are not returned to the unlock state. DEG fault exists shortly after an SSF fault of VC2/12, DEG fault exists when an SLM fault of VC2/12 exists. In case of subnetwork connection protection auto switch does not clear manual switch. Monitoring VCs of an SNC group do not count far end bit errors. In case of SNCP monitoring VCs have fault status PMA although it should be DMA. NNM1 alarms are seen as NNM2 alarms and NNM2 does not give alarms. NNM gives an alarm even if there is no corresponding control channel. If MS 1+1 protection is active, all read and write operations to interface loops are denied. VC4 LOM affects the performance data of VC4s.

134
10004_22 2008 Tellabs.
VC4 SLM, VC4 UNEQ, 34M SLM and 34M UNEQ alarm may exist without a reason. This may occur when signal quality is very bad. Attribute waitToRestoreTime affects SNPO switch even if there has been manual switch. The attribute should affect SNPO switch only after SF/SD switch. If SNPO switch is revertive and waitToRestore state is on, switchStatus of protecting side is in wait-to-restore state. It should be in No Request state. If MS-AIS is received, SSF should be set too in MSTTPBid. If VC4 TIM or LOM is active, the received trace identifier J1 is masked to NULL. After GMU reset RS and VC4 AIS mask is not set on in case of dTIM. The performance management system of GMU fails to detect alarms from far end when receiving alarms from near end. AIS fault of SYN-34-E interface module does not work. Recovery does not work between GMUs when they are located in Tellabs 8150 basic node. CAS signaling does not go through GMU. CAS signaling does not work, if GMU is moved from Tellabs 8150 basic node to Tellabs 8170 cluster node or vice versa. Group DEG does not work with SNC/N protection. Spontaneous messages do not work, if GMU is a replacement unit. Spontaneous messages of TU12Ctps do not work. GMU causes Unit IA fault in Tellabs 8160 A111 after power up (CRF ID 4004646). Performance monitoring thresholds lower BBE, ES, SES and secSesThreshold are compared incorrectly (CRF ID 4004442).
11.10 Version 1.1


Restrictions

Software can not be downloaded to GMU-A. It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Control channel in VC payload is not supported. The SYN-34-E interface module is not supported.
10004_22 2008 Tellabs.

135
Control channel data is not protected in VC4 POH bytes in case of MS 1+1 protection. It is possible to delete control channel related VC2/12 and cross-connections. If a certain instance has an SSF alarm, the trace identifier of the corresponding instance is not masked to value null. Advanced SNC configuration is not supported. X-bus slip counters of VC2s and VC12s are not supported. SCU backuping is not supported. XCG is not supported. SSM enabling and disabling are not supported. The supervisory unequipped feature of VC2 and VC12 is not supported. Configurable TIM consequent actions are not supported. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547).
Bugs

Flash corruption problem (CRF ID 4005110). Wrong fault classification of UNAVAIL, QOS and QOSTR faults (CRF ID 4003428). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303). Node master clock rank is sometimes reported as illegal value 0 to neighbour nodes. VC2/VC12 FEBEs are not counted when TU connection is bidirectional. A fault in Tx signal (RDI or enough FEBE). does not generate unavailability. With a certain configuration of VCs, the GMU restart is failed after node reset. 522 bytes of a non-volatile setting are not sent to SCU, this means that part of spontaneous event reporting configurations are not backed up. If equipment loop is set and LOS is detected, RS-AIS is still sent to the RX direction and SSF is set to the lower level instances. After 1+1 multiplex section protection switch VC2/12s could have an SSF fault without a reason. If vcGtp is set to lock state and one VC locking fails, all VCs are not returned to the unlock state. The DEG fault exists shortly after an SSF fault of VC2/12, the DEG fault exists when an SLM fault of VC2/12 exists. In case of subnetwork connection protection auto switch does not clear the manual switch. Monitoring VCs of an SNC group do not count far end bit errors. In case of SNCP monitoring VCs have fault status PMA although it should be DMA. NNM1 alarms are seen as NNM2 alarms and NNM2 does not give alarms. NNM gives an alarm even if there is no corresponding control channel. If MS 1+1 protection is active, all read and write operations to interface loops are denied. VC4 LOM affects the performance data of VC4s.
10004_22 2008 Tellabs.

136
VC4 SLM, VC4 UNEQ, 34M SLM and 34M UNEQ alarm may exist without a reason. This may occur when signal quality is very bad. Attribute waitToRestoreTime affects SNPO switch even if there has been manual switch. The attribute should affect SNPO switch only after SF/SD switch. If SNPO switch is revertive and waitToRestore state is on, switchStatus of protecting side is in wait-to-restore state. It should be in No Request state. If MS-AIS is received, SSF should be set too in MSTTPBid. After GMU reset RS and VC4 AIS mask is not set on in case of dTIM. The performance management system of GMU fails to detect alarms from far end when receiving alarms from near end. AIS fault of the SYN-34-E interface module does not work. Recovery does not work between GMUs when they are located in Tellabs 8150 basic node. CAS signaling does not go through GMU. CAS signaling does not work, if GMU is moved from Tellabs 8150 basic node to Tellabs 8170 cluster node or vice versa. Group DEG does not work with SNC/N protection. Spontaneous messages do not work, if GMU is a replacement unit. Spontaneous messages of TU12Ctps do not work. GMU causes Unit IA fault in Tellabs 8160 A111 after power up (CRF ID 4004646). Performance monitoring thresholds lower BBE, ES, SES and secSesThreshold are compared incorrectly (CRF ID 4004442).
10004_22 2008 Tellabs.

137
12 GMU and GMU-A Units: GMZ461 Unit Software

Two software products are needed on the GMU and GMU-A units in Tellabs 8140 midi, Tellabs 8150 basic, Tellabs 8160 A111 and Tellabs 8170 cluster nodes. Software GMZ460 is for the main processor and software GMZ461 is for the ASIC processor. GMZ461 version 1.11 can be downloaded to GMU-A having the version 1.y of GMZ461 (where y=0, 1, 2...). GMZ461 version 1.10 can be downloaded to GMU having the version 1.y of GMZ461 (where y=0, 1, 2...). GMU is composed of the GMU450 v1.0 and DSU453 v1.0 boards. The base unit hardware version is 1.0. GMU-A is composed of the GMU450 v1.0 and DSU453 v2.0 boards. The base unit hardware version is 2.0 or higher.
12.1 Version 1.11

NOTE: Do not download this software in GMU (HW version 1.0). This software is intended for GMU-A only (HW version 2.0). For the HW version 1.0, use the SW version 1.10. Enhancements and Fixed Bugs
Under certain circumstances SLM and UNEQ alarms might stay on even if the alarm cause has disappeared. (CR ID 300070271)
Dependencies

GMU-A hardware version must be 2.0 or higher. GMZ460 software version must be 1.8 or higher CCU (SCZ286) software version can be any version. SCP (SCZ281) software version must be 3.1 or higher. SCU software version must be 8.5 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.1 or higher. CXU-M (SXZ288) software version must be 2.7 or higher. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version must be 6.8 or higher. SXU-C (SXZ289) software version must be 2.7 or higher. SXU-V (SXZ630) software version must be 1.1 or higher.

138
10004_22 2008 Tellabs.
GMU-A specific features, asynchronous mapping, P12s termination and V5.2 voice support, are supported only by GMU-A, not by GMU. MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher. MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher. GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12.
Restrictions

It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Before inserting the GMU unit into a slot where GMU-A has been (in the inventory), it is absolutely necessary to do "Remove from Inventory" for GMU-A. Performance threshold values are not according to the EN 301 167 v.1.1.1 standard on multiplex section (MS) layer. On MS layer, background block error (BBE) count is not according to the standard due to hardware restrictions. In GMU-A a standard method can be used if BIP-1 based MS block error calculation is selected (CRF ID 4003017). BIP-1 / BIP-24 block size based MS operation is supported only by GMU-A with Tellabs 8100 network manager Release 13A or higher (CRF ID 4003330, CR ID 200004858). STM-1 interface modules older than version 2.0 do not support "Small block" B2-counting. In the old interface module version B2-counting mode is always "Large Block" regardless of the NMS settings.
Bugs
Tellabs 8100 control channel is not working in VC-2/VC-12 payload, if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335, CR ID 200005084)
12.2 Version 1.10

NOTE: Do not download this software in GMU-A (HW version 2.0). This software is intended for GMU only (HW version 1.0). For the HW version 2.0, use the SW version 1.11. Enhancements and Fixed Bugs
Under certain circumstances SLM and UNEQ alarms might stay on even if the alarm cause has disappeared. (CR ID 300070271)
Dependencies

GMU hardware version must be 1.0. GMU-A hardware version must be 2.0 or higher. GMZ460 software version must be 1.8. CCU (SCZ286) software version can be any version.
10004_22 2008 Tellabs.

139
SCP (SCZ281) software version must be 3.1 or higher. SCU software version must be 8.5 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.1 or higher. CXU-M (SXZ288) software version must be 2.7 or higher. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version must be 6.8 or higher. SXU-C (SXZ289) software version must be 2.7 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. GMU-A specific features, asynchronous mapping, P12s termination and V5.2 voice support, are supported only by GMU-A, but not by GMU. MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher. MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher. GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12.
Restrictions

It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Before inserting GMU unit into a slot where GMU-A has been (in the inventory), it is absolutely necessary to do "Remove from Inventory" for GMU-A. Performance threshold values are not according to the EN 301 167 v.1.1.1 standard on multiplex section (MS) layer. On MS layer, background block error (BBE) count is not according to the standard due to hardware restrictions. In GMU-A a standard method can be used if BIP-1 based MS block error calculation is selected (CRF ID 4003017). BIP-1 / BIP-24 block size based MS operation is supported only by GMU-A with Tellabs 8100 network manager Release 13A or higher (CRF ID 4003330, CR ID 200004858).
Bugs

Tellabs 8100 control channel is not working in VC-2/VC-12 payload, if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335, CR ID 200005084). VC-2 trunks work unreliably ( CR IDs 200016173, 200013679) SSM does not work with 34 M interface units with the OTP v.3 (CR ID 200005361) Old interface units with OTP v.1 do not initialize properly (CR ID 200015744)

140
10004_22 2008 Tellabs.
12.3 Version 1.9

NOTE: Do not download this software in GMU (HW version 1.0). This software is intended for GMU-A only (HW version 2.0). For HW version 1.0, use SW version 1.8. Enhancements and Fixed Bugs (compared with version x.1)
A bug in the version 1.8 that caused bit errors and MAIS alarms on VC2 links with GMUA has been fixed (CR IDs 200016173 and 200013679). A bug with SSM message handling in 34 M interfaces (GDH456) has been fixed. This bug does not concern GDH456 modules that have been manufactured before 06/2004 (CR ID 200005361). An initialization error with old interface units with OTP ASIC version 1 has been fixed. Now it is possible to use all old hardware modules with GMU-A base unit HW version 2.0 (CR ID 200015744).
Dependencies

GMU-A hardware version must be 2.0 or higher. GMZ460 software version must be 1.8 or higher CCU (SCZ286) software version can be any version. SCP (SCZ281) software version must be 3.1 or higher. SCU software version must be 8.5 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.1 or higher. CXU-M (SXZ288) software version must be 2.7 or higher. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version must be 6.8 or higher. SXU-C (SXZ289) software version must be 2.7 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. GMU-A specific features, asynchronous mapping, P12s termination and V5.2 voice support, are supported only by GMU-A, but not by GMU. MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher. MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher. GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12.
10004_22 2008 Tellabs.

141
Restrictions

It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Before inserting GMU unit into a slot where GMU-A has been (in the inventory), it is absolutely necessary to do "Remove from Inventory" for GMU-A. Performance threshold values are not according to the EN 301 167 v.1.1.1 standard on multiplex section (MS) layer. On MS layer, background block error (BBE) count is not according to the standard due to hardware restrictions. In GMU-A a standard method can be used if BIP-1 based MS block error calculation is selected (CRF ID 4003017). BIP-1 / BIP-24 block size based MS operation is supported only by GMU-A with Tellabs 8100 Network Manager Release 13A or higher (CRF ID 4003330, CR ID 200004858). STM-1 interface modules older than version 2.0 do not support "Small block" B2-counting. In old interface module version B2-counting mode is always "Large Block" regardless of NMS settings.
Bugs

Tellabs 8100 control channel is not working in VC-2/VC-12 payload, if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335, CR ID 200005084) Under certain circumstances SLM and UNEQ alarms might stay on even if alarm cause has disappeared. (CR ID 300070271)
12.4 Version 1.8

NOTE: Do not use this software in GMU-A (HW version 2.0). Because of a traffic affecting bug in GMZ461 1.8, use version 1.9 in GMU-A instead. Enhancements and Fixed Bugs
Applies to GMU-A only: when X-bus distribution is set to 'even' while P12s signal mapping mode is 'asynchronous', 'uneven' X-bus distribution is used however. This is because of a bug in LTA ASIC causing the combination of X-bus distribution being 'even' and P12s signal mapping mode being 'asynchronous' for VC12 not to work reliably in all situations (CR ID 200011752). Applies to GMU-A only: now it is not possible to cause illegal VC-12-mc configuration by using Tellabs 8100 network managers Node Manager copy/paste from a single VC12 (asynchronous mode) into VC12-mc/VC-12 (CR ID 200011098). Applies to GMU-A only: SYN-34-E interface module works also for GMU-A (CR ID 11636). SYN-34-E interface module internal test does not fail unintentionally and no fault Initialization error (GMZ461) is produced anymore (CR ID 200004414, 200011635, 200011636). Fixed wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303, 200011641). Fixed corruption of Rx buffer centring, which caused traffic degradation in GMU (CR ID 200007236), (Technical note ID SOL2005).

142
10004_22 2008 Tellabs.
Dependencies

GMU hardware version must be 1.0. GMU-A hardware version must be 2.0 or higher. GMZ460 software version must be 1.8. CCU (SCZ286) software version can be any version. SCP (SCZ281) software version must be 3.1 or higher. SCU software version must be 8.5 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.1 or higher. CXU-M (SXZ288) software version must be 2.7 or higher. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version must be 6.8 or higher. SXU-C (SXZ289) software version must be 2.7 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. GMU-A specific features, asynchronous mapping, P12s termination and V5.2 voice support, are supported only by GMU-A, but not by GMU. MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher. MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher. GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12.
Restrictions

It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Before inserting GMU unit into a slot where GMU-A has been (in the inventory), it is absolutely necessary to do "Remove from Inventory" for GMU-A. Performance threshold values are not according to the EN 301 167 v.1.1.1 standard on multiplex section (MS) layer. On MS layer, background block error (BBE) count is not according to the standard due to hardware restrictions. In GMU-A a standard method can be used if BIP-1 based MS block error calculation is selected (CRF ID 4003017). BIP-1 / BIP-24 block size based MS operation is supported only by GMU-A with Tellabs 8100 Network Manager Release 13A or higher (CRF ID 4003330, CR ID 200004858).
10004_22 2008 Tellabs.

143
Bugs

Tellabs 8100 control channel is not working in VC-2/VC-12 payload, if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335, CR ID 200005084). VC-2 trunks work unreliably ( CR IDs 200016173, 200013679) SSM does not work with 34 M interface units with the OTP v.3 (CR ID 200005361) Old interface units with OTP v.1 do not initialize properly (CR ID 200015744) Under certain circumstances SLM and UNEQ alarms might stay on even if alarm cause has disappeared. (CR ID 300070271)
12.5 Version 1.179

Fixed corruption of Rx buffer centring, which caused traffic degradation (CR ID 200007236), (Technical note ID SOL2005).
Dependencies

GMU hardware version must be 1.0. GMZ460 software version must be 1.179. CCU (SCZ286) software version can be any version. SCP (SCZ281) software version must be 3.1 or higher. SCU software version must be 8.5 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.1 or higher. CXU-M (SXZ288) software version must be 2.7 or higher. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version must be 6.8 or higher. SXU-C (SXZ289) software version must be 2.7 or higher. SXU-V (SXZ630) software version must be 1.1 or higher.

144
10004_22 2008 Tellabs.
Restrictions

Do not download this software version in GMU-A. This software is intended for GMU only. It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Before inserting GMU unit into a slot where GMU-A has been (in the inventory), it is absolutely necessary to do "Remove from Inventory" for GMU-A. Performance threshold values are not according to the EN 301 167 v.1.1.1 standard on multiplex section (MS) layer. On MS layer, background block error (BBE) count is not according to the standard due to hardware restrictions (CRF ID 4003017).
Bugs

Tellabs 8100 control channel is not working in VC-2/VC-12 payload, if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335, CR ID 200005084). SSM does not work with 34 M interface units with the OTP v.3 (CR ID 200005361) Old interface units with OTP v.1 do not initialize properly (CR ID 200015744)
12.6 Version 1.7


Enhancement in performance data collection. If 15-minute performance counter has other value than zero, a delta-type alarm is set active (CRF ID 4003054). BIP-1/BIP-24 block size based MS operation in GMU-A (CRF ID 4003330, CR ID 200004858). G.826 performance monitoring data is collected also when TU cross-connection is missing (CRF ID 4004714). Extended production test support (CRF ID 4004928). If fault event reporting is defined for a VC-12, also P12 layer fault events are reported. P12 layer fault reporting enhanced. Fixed flash corruption problem (CRF ID 4005110). Fixed fault classification of UNAVAIL, QOS and QOSTR faults (CRF ID 4003428). Fault reporting bug fixed, some faults were never reported (CRF ID 4005206, CR ID 200005406). Fix in node master clock rank: illegal value 0 was sometimes reported to neighbour nodes. Fixed incorrect MLOF alarm with asynchronous SNC/N protected VC-12 with Channel Associated Signalling and P12s termination (CR ID 200005740).
10004_22 2008 Tellabs.

145
Dependencies

GMU-A hardware version must be 2.0 or higher. GMZ460 software version must be 1.7. CCU (SCZ286) software version can be any version. SCP (SCZ281) software version must be 3.1 or higher. SCU software version must be 8.5 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.1 or higher. CXU-M (SXZ288) software version must be 2.7 or higher. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version must be 6.8 or higher. SXU-C (SXZ289) software version must be 2.7 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher. MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher. GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12.
Restrictions

It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Before inserting GMU unit into a slot where GMU-A has been (in the inventory), it is absolutely necessary to do "Remove from Inventory" for GMU-A. Performance threshold values are not according to the EN 301 167 v.1.1.1 standard on multiplex section (MS) layer. On MS layer, background block error (BBE) count is not according to the standard due to hardware restrictions. In GMU-A a standard method can be used if BIP-1 based MS block error calculation is selected (CRF ID 4003017). BIP-1 / BIP-24 block size based MS operation is supported only by GMU-A with Tellabs 8100 Network Manager Release 13A or higher (CRF ID 4003330, CR ID 200004858).
Bugs

SYN-34-E interface module does not work reliably (CR ID 200011636). SYN-34-E interface module internal test fails unintentionally and produces fault Initialization error (GMZ461) (CR ID 200004414, 200011635, 200011636). It is possible to cause illegal VC-12-mc configuration by using Tellabs 8100 network managers Node Manager copy/paste from a single VC12 (asynchronous mode) into VC12mc/VC-12 (CR ID 200011098). Because of a bug in LTA ASIC, the combination of X-bus distribution being even and P12s signal mapping mode being asynchronous for VC12 does not work reliably in all situations (CR ID 200011752).
10004_22 2008 Tellabs.

146
Tellabs 8100 control channel is not working in VC-2/VC-12 payload, if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335, CR ID 200005084). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303). SSM does not work with 34 M interface units with the OTP v.3 (CR ID 200005361) Old interface units with OTP v.1 do not initialize properly (CR ID 200015744)
12.7 Version 1.6


Asynchronous 2 Mbit/s signal mapping. P12s (G.704) termination. V5.2 voice interface support in Tellabs 8150 basic node. SS bit values in AU4 pointer do not have to be 10 anymore. Therefore, this software version can be used to connect GMU-A to SONET equipment (CRF ID 4004547). Transmitted NU2 byte in STM1 RSOH is balanced, i.e. it has equal number of 0 and 1 bits (value 0xAA). The byte can also be set with Tellabs 8100 Network Manager (interface window/overhead bytes) (CRF ID 4003371). GMU does not cause Unit IA fault in Tellabs 8160 A111 after power up (CRF ID 4004646). Performance monitoring thresholds lower BBE, ES, SES and secSesThreshold are compared correctly (CRF ID 4004442).
Dependencies

GMU-A hardware version must be 2.0 or higher. GMZ460 software version must be 1.6. CCU (SCZ286) software version can be any version. SCP (SCZ281) software version must be 3.1 or higher. SCU software version must be 8.5 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.1 or higher. CXU-M (SXZ288) software version must be 2.7 or higher. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version must be 6.8 or higher. SXU-C (SXZ289) software version must be 2.7 or higher. SXU-V (SXZ630) software version must be 1.1 or higher.
10004_22 2008 Tellabs.

147
MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher. MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher. GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12.
Restrictions

It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Performance threshold values are not according to the EN 301 167 v.1.1.1 standard on multiplex section (MS) layer. On MS layer, background block error (BBE) count is not according to the standard due to hardware restrictions. Other threshold values (ES and SES) are according to the standard. Threshold values on other layers (RS, VC-4, VC-2, VC-12) are according to the standard. Note: if software is downloaded to existing GMU, execution of Factory settings is required for this feature (CRF ID 4003017).
Bugs

SYN-34-E interface module does not work reliably (CR ID 200011636). SYN-34-E interface module internal test fails unintentionally and produces fault Initialization error (GMZ461). However, this fault is not shown by Tellabs 8100 network manager because of fault reporting bug CRF ID 4005206, CR ID 200005406 (CR ID 200004414, 200011635, 200011636). It is possible to cause illegal VC-12-mc configuration by using Tellabs 8100 network managers Node Manager copy/paste from a single VC12 (asynchronous mode) into VC12mc/VC-12 (CR ID 200011098). Because of a bug in LTA ASIC, the combination of X-bus distribution being even and P12s signal mapping mode being asynchronous for VC12 does not work reliably in all situations (CR ID 200011752). Incorrect MLOF alarm is reported with asynchronous SNC/N protected VC-12 with Channel Associated Signalling and P12s termination (CR ID 200005740). Tellabs 8100 control channel is not working in VC-2/VC-12 payload, if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335, CR ID 200005084). Flash corruption problem (CRF ID 4005110). Wrong fault classification of UNAVAIL, QOS and QOSTR faults (CRF ID 4003428). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303). Fault reporting bug, some faults are never reported (CRF ID 4005206, CR ID 200005406). Node master clock rank is sometimes reported as illegal value 0 to neighbour nodes. SSM does not work with 34 M interface units with the OTP v.3 (CR ID 200005361) Old interface units with OTP v.1 do not initialize properly (CR ID 200015744)

148
10004_22 2008 Tellabs.
12.8 Version 1.102


GMU does not cause Unit IA fault in Tellabs 8160 A111 after power up (CRF ID 4004646). SS bit values in AU4 pointer do not have to be 10 anymore. Therefore, this software version can be used to connect GMU to SONET equipment (CRF ID 4004547). Transmitted NU2 byte in STM1 RSOH is balanced, i.e. it has equal number of 0 and 1 bits (value 0xAA). The byte can also be set with Tellabs 8100 Network Manager (interface window/overhead bytes) (CRF ID 4003371).
Dependencies

SCU software version must be at least 8.5. SCP software version must be at least 3.1. SXU-A/B software version must be at least 6.8. SXU-C software version must be at least 2.7. CXU-M software version must be at least 2.7. XCG software version must be at least 2.1. GMZ460 software version must be 1.102
Restrictions

Software can not be downloaded to GMU-A. It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Versions 1.4 and later of GMU support advanced SNC group configuration but in MartisDXX Manager NMS this feature is supported in Release 10.0 and later. If SNC groups are configured by earlier NMS versions, this may cause inconsistency between database and hardware. The user can minimize this problem by configuring monitoring TTPs of an SNC group to have the same values as the terminating TTP.
10004_22 2008 Tellabs.

149
Bugs

Tellabs 8100 control channel is not working in VC-2/VC-12 payload, if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335, CR ID 200005084). Flash corruption problem (CRF ID 4005110). Wrong fault classification of UNAVAIL, QOS and QOSTR faults (CRF ID 4003428). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303). Node master clock rank is sometimes reported as illegal value 0 to neighbour nodes. Performance monitoring thresholds lower BBE, ES, SES and secSesThreshold are compared incorrectly (CRF ID 4004442). SSM does not with 34 M interface units with the OTP v.3 (CR ID 200005361) Old interface units with OTP v.1 do not initialize properly (CR ID 200015744)
12.9 Version 1.5


Restrictions

Software can not be downloaded to GMU-A. It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Versions 1.4 and later of GMU support advanced SNC group configuration but in MartisDXX Manager NMS this feature is supported in Release 10.0 and later. If SNC groups are configured by earlier NMS versions, this may cause inconsistency between database and hardware. The user can minimize this problem by configuring monitoring TTPs of an SNC group to have the same values as the terminating TTP. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547).

150
10004_22 2008 Tellabs.
Bugs

Tellabs 8100 control channel is not working in VC-2/VC-12 payload, if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335, CR ID 200005084). Flash corruption problem (CRF ID 4005110). Wrong fault classification of UNAVAIL, QOS and QOSTR faults (CRF ID 4003428). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303). Node master clock rank is sometimes reported as illegal value 0 to neighbour nodes. GMU causes Unit IA fault in Tellabs 8160 A111 after power up (CRF ID 4004646). Performance monitoring thresholds lower BBE, ES, SES and secSesThreshold are compared incorrectly (CRF ID 4004442). SSM does not with 34 M interface units with the OTP v.3 (CR ID 200005361) Old interface units with OTP v.1 do not initialize properly (CR ID 200015744)
12.10 Version 1.4


Restrictions

Software can not be downloaded to GMU-A. It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Control channel in VC payload is not supported. Version 1.4 of GMU supports advanced SNC group configuration but in MartisDXX Manager NMS this feature is supported in Release 10.0 and later. If SNC groups are configured by earlier NMS versions, this may cause inconsistency between database and hardware. The user can minimize this problem by configuring monitoring TTPs of an SNC group to have the same values as the terminating TTP. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547).
10004_22 2008 Tellabs.

151
Bugs

Flash corruption problem (CRF ID 4005110). Wrong fault classification of UNAVAIL, QOS and QOSTR faults (CRF ID 4003428). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303). Node master clock rank is sometimes reported as illegal value 0 to neighbour nodes. The performance management system of GMU fails to detect alarms from far end when receiving alarms from near end. Expected TI, CAS, signal degrade seconds, signal degrade threshold and TIMaAisenabled attributes cannot be changed in VCgtp if SNC/I protection is used. AIS fault of SYN-34-E interface module does not work. Recovery does not work between GMUs when they are located in Tellabs 8150 basic node. CAS signaling does not go through GMU. CAS signaling does not work, if GMU is moved from Tellabs 8150 basic node to Tellabs 8170 cluster node or vice versa. Group DEG does not work with SNC/N protection. Spontaneous messages do not work, if GMU is a replacement unit. Spontaneous messages of TU12Ctps do not work. GMU causes Unit IA fault in Tellabs 8160 A111 after power up (CRF ID 4004646). Performance monitoring thresholds lower BBE, ES, SES and secSesThreshold are compared incorrectly (CRF ID 4004442). SSM does not with 34 M interface units with the OTP v.3 (CR ID 200005361) Old interface units with OTP v.1 do not initialize properly (CR ID 200015744)
12.11 Version 1.3



152
10004_22 2008 Tellabs.
Restrictions

Software can not be downloaded to GMU-A. It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Control channel in VC payload is not supported. Advanced SNC configuration is not supported. X-bus slip counters of VC2s and VC12s are not supported. SCU backuping is not supported. XCG is not supported. SSM enabling and disabling are not supported. The supervisory unequipped feature of VC2 and VC12 is not supported. Configurable TIM consequent actions are not supported. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547).
Bugs

Flash corruption problem (CRF ID 4005110). Wrong fault classification of UNAVAIL, QOS and QOSTR faults (CRF ID 4003428). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303). Node master clock rank is sometimes reported as illegal value 0 to neighbour nodes. Ps34M performance thresholds are seen as MS thresholds if SYN-34-E interface module is configured. If 34M-PsTTP alarm is activated and fault declare value is between 1-9, TU12-LOMs exist for a short time. Monitoring VCs of SNC group do not count far end bit errors. In case of SNCP monitoring VCs have fault status PMA although it should be DMA. NNM1 alarms are seen as NNM2 alarms and NNM2 does not give alarms. NNM gives an alarm even if there is no corresponding control channel. If MS 1+1 protection is active, all read and write operations to interface loops are denied. VC4 LOM affects the performance data of VC4s. VC4 SLM, VC4 UNEQ, 34M SLM and 34M UNEQ alarms may exist without a reason. This may occur when signal quality is very bad. Attribute waitToRestoreTime affects SNPO switch even if there has been manual switch. The attribute should affect SNPO switch only after SF/SD switch. If SNPO switch is revertive and waitToRestore state is on, switchStatus of protecting side is in wait-to-restore state. It should be in No Request state. If MS-AIS is received, SSF should be set too in MSTTPBid. If VC4 TIM or LOM is active, the received trace identifier J1 is masked to NULL.
153
10004_22 2008 Tellabs.
After GMU reset RS and VC4 AIS mask is not set on in case of dTIM. The performance management system of GMU fails to detect alarms from far end when receiving alarms from near end. The AIS fault of SYN-34-E interface module does not work. Recovery does not work between GMUs when they are located in Tellabs 8150 basic node. CAS signaling does not go through GMU. CAS signaling does not work, if GMU is moved from Tellabs 8150 basic node to Tellabs 8170 cluster node or vice versa. Group DEG does not work with SNC/N protection. Spontaneous messages do not work, if GMU is a replacement unit. Spontaneous messages of TU12Ctps do not work. GMU causes Unit IA fault in Tellabs 8160 A111 after power up (CRF ID 4004646). Performance monitoring thresholds lower BBE, ES, SES and secSesThreshold are compared incorrectly (CRF ID 4004442). SSM does not with 34 M interface units with the OTP v.3 (CR ID 200005361) Old interface units with OTP v.1 do not initialize properly (CR ID 200015744)
12.12 Version 1.2


Restrictions

Software can not be downloaded to GMU-A. It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Control channel in VC payload is not supported. The SYN-34-E interface module is not supported. Advanced SNC configuration is not supported. X-bus slip counters of VC2s and VC12s are not supported. SCU backuping is not supported.

154
10004_22 2008 Tellabs.
XCG is not supported. SSM enabling and disabling are not supported. The supervisory unequipped feature of VC2 and VC12 is not supported. Configurable TIM consequent actions are not supported. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547).
Bugs

Flash corruption problem (CRF ID 4005110). Wrong fault classification of UNAVAIL, QOS and QOSTR faults (CRF ID 4003428). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303). Node master clock rank is sometimes reported as illegal value 0 to neighbour nodes. 522 bytes of a non-volatile setting are not sent to SCU, this means that part of spontaneous event reporting configurations are not backed up. If an equipment loop is set and LOS is detected, RS-AIS is still sent to the RX direction and SSF is set to the lower level instances. After 1+1 multiplex section protection switch VC2/12s could have an SSF fault without a reason. If vcGtp is set to lock state and one VC locking fails, all VCs are not returned to the unlock state. DEG fault exists shortly after an SSF fault of VC2/12, DEG fault exists when an SLM fault of VC2/12 exists. In case of subnetwork connection protection auto switch does not clear manual switch. Monitoring VCs of an SNC group do not count far end bit errors. In case of SNCP monitoring VCs have fault status PMA although it should be DMA. NNM1 alarms are seen as NNM2 alarms and NNM2 does not give alarms. NNM gives an alarm even if there is no corresponding control channel. If MS 1+1 protection is active, all read and write operations to interface loops are denied. VC4 LOM affects the performance data of VC4s. VC4 SLM, VC4 UNEQ, 34M SLM and 34M UNEQ alarm may exist without a reason. This may occur when signal quality is very bad. Attribute waitToRestoreTime affects SNPO switch even if there has been manual switch. The attribute should affect SNPO switch only after SF/SD switch. If SNPO switch is revertive and waitToRestore state is on, switchStatus of protecting side is in wait-to-restore state. It should be in No Request state. If MS-AIS is received, SSF should be set too in MSTTPBid. If VC4 TIM or LOM is active, the received trace identifier J1 is masked to NULL. After GMU reset RS and VC4 AIS mask is not set on in case of dTIM.
10004_22 2008 Tellabs.

155
The performance management system of GMU fails to detect alarms from far end when receiving alarms from near end. AIS fault of SYN-34-E interface module does not work. Recovery does not work between GMUs when they are located in Tellabs 8150 basic node. CAS signaling does not go through GMU. CAS signaling does not work, if GMU is moved from Tellabs 8150 basic node to Tellabs 8170 cluster node or vice versa. Group DEG does not work with SNC/N protection. Spontaneous messages do not work, if GMU is a replacement unit. Spontaneous messages of TU12Ctps do not work. GMU causes Unit IA fault in Tellabs 8160 A111 after power up (CRF ID 4004646). Performance monitoring thresholds lower BBE, ES, SES and secSesThreshold are compared incorrectly (CRF ID 4004442). SSM does not with 34 M interface units with the OTP v.3 (CR ID 200005361) Old interface units with OTP v.1 do not initialize properly (CR ID 200015744)
12.13 Version 1.1


Restrictions

Software can not be downloaded to GMU-A. It is not supported to replace GMU-A with GMU, however GMU can be replaced with GMU-A. Control channel in VC payload is not supported. The SYN-34-E interface module is not supported. Control channel data is not protected in VC4 POH bytes in case of MS 1+1 protection. It is possible to delete control channel related VC2/12 and cross-connections. If a certain instance has an SSF alarm, the trace identifier of the corresponding instance is not masked to value null. Advanced SNC configuration is not supported.

156
10004_22 2008 Tellabs.
X-bus slip counters of VC2s and VC12s are not supported. SCU backuping is not supported. XCG is not supported. SSM enabling and disabling are not supported. The supervisory unequipped feature of VC2 and VC12 is not supported. Configurable TIM consequent actions are not supported. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547).
Bugs

Flash corruption problem (CRF ID 4005110). Wrong fault classification of UNAVAIL, QOS and QOSTR faults (CRF ID 4003428). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047, CR ID 200005303). Node master clock rank is sometimes reported as illegal value 0 to neighbour nodes. VC2/VC12 FEBEs are not counted when TU connection is bidirectional. A fault in Tx signal (RDI or enough FEBE). does not generate unavailability. With a certain configuration of VCs, the GMU restart is failed after node reset. 522 bytes of a non-volatile setting are not sent to SCU, this means that part of spontaneous event reporting configurations are not backed up. If equipment loop is set and LOS is detected, RS-AIS is still sent to the RX direction and SSF is set to the lower level instances. After 1+1 multiplex section protection switch VC2/12s could have an SSF fault without a reason. If vcGtp is set to lock state and one VC locking fails, all VCs are not returned to the unlock state. The DEG fault exists shortly after an SSF fault of VC2/12, the DEG fault exists when an SLM fault of VC2/12 exists. In case of subnetwork connection protection auto switch does not clear the manual switch. Monitoring VCs of an SNC group do not count far end bit errors. In case of SNCP monitoring VCs have fault status PMA although it should be DMA. NNM1 alarms are seen as NNM2 alarms and NNM2 does not give alarms. NNM gives an alarm even if there is no corresponding control channel. If MS 1+1 protection is active, all read and write operations to interface loops are denied. VC4 LOM affects the performance data of VC4s. VC4 SLM, VC4 UNEQ, 34M SLM and 34M UNEQ alarm may exist without a reason. This may occur when signal quality is very bad. Attribute waitToRestoreTime affects SNPO switch even if there has been manual switch. The attribute should affect SNPO switch only after SF/SD switch.
10004_22 2008 Tellabs.

157
If SNPO switch is revertive and waitToRestore state is on, switchStatus of protecting side is in wait-to-restore state. It should be in No Request state. If MS-AIS is received, SSF should be set too in MSTTPBid. After GMU reset RS and VC4 AIS mask is not set on in case of dTIM. The performance management system of GMU fails to detect alarms from far end when receiving alarms from near end. AIS fault of the SYN-34-E interface module does not work. Recovery does not work between GMUs when they are located in Tellabs 8150 basic node. CAS signaling does not go through GMU. CAS signaling does not work, if GMU is moved from Tellabs 8150 basic node to Tellabs 8170 cluster node or vice versa. Group DEG does not work with SNC/N protection. Spontaneous messages do not work, if GMU is a replacement unit. Spontaneous messages of TU12Ctps do not work. GMU causes Unit IA fault in Tellabs 8160 A111 after power up (CRF ID 4004646). Performance monitoring thresholds lower BBE, ES, SES and secSesThreshold are compared incorrectly (CRF ID 4004442). SSM does not with 34 M interface units with the OTP v.3 (CR ID 200005361) Old interface units with OTP v.1 do not initialize properly (CR ID 200015744)

158
10004_22 2008 Tellabs.
GMX Unit: GMZ544 Unit Software
13 GMX Unit: GMZ544 Unit Software

The software GMZ544 is used on the GMX unit (whose base unit is GMX588) in Tellabs 8160 A111. Two software products are needed for the GMX unit; boot software and downloadable software. The major version number indicates if the boot code is compatible with the downloadable code. If the boot version is a.b and the downloadable version is c.d, they are compatible if and only if a = c. For example, downloadable code 2.0 cannot be downloaded if boot code version is 1.5.
13.1 Version 4.6

Enhancements and Fixed Bugs (compared with version 4.4 / functionally same as 3.24)

1+1 protection switch does not cause fake SSF alarms on P12s (CR ID 300070961). Flash list record status bit handling has been fixed (CR ID 300092117). STM-1 loop timeout is not truncated in an STM-1 interface #2 (CR ID 300021040). LOF fault is not reported if P12s AIS reporting is disabled (CR ID 300021812).
Dependencies
When GMXs are equipment protected (both GMXs installed) and synchronization input is taken from the STM-1 interface, both GMXs must have an interface module, even if the STM-1 interface in the protecting GMX is not used. GMX hardware version must be 3.0 or higher. If GMX is protected, the software versions of both GMXs must be the same, except during the middle phase of the software upgrade process. However if the hardware versions are different the software version must be the functionally equal version mentioned above. In the case GMX is protected, SCU-H (SCZ545) software version must be 1.11 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1.6 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1.5 or higher. MartisDXX Manager support for this unit without SBU functionality is available in Release 10.1A Service Pack 3 or higher. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. MartisDXX Manager support for group operation for setting recovery restriction for trunk operations is available in Release 11 Service Pack 4 or higher (CRF ID 4004476). MartisDXX Manager support for optional restricting of set operations while downloading unit software is available in Release 11 Service Pack 4 or higher (CRF ID 4004515).
10004_22 2008 Tellabs.

159
Restrictions

The control channel in the R0 byte of VC-12 is forbidden because of unreliable HW functionality. Monitoring VC-12/2s in GMX use the same TU-bus internal resources as VC-12s in SBU. The total capacity for VC-12/2s is (in the case of two protected GMXs):

63 VC-12s of SBU + 63 GMXs VC-12s or, 31 SNC/N protected VC-12s of SBU + 63 GMXs VC-12s or, 63 SNC/N protected GMXs VC-12s or, 20 SNC/N protected GMXs VC-2s + 3 SNC/N protected GMXs VC-12s or, a combination of the alternatives above so that 2*#E1 + #VC12M + 3*#VC2M 126 and #VC12T + 3*#VC2T 63, where #E1 = number of VC-12s of SBU, #VC12M = number of monitoring VC-12s, #VC2M = number of monitoring VC-2s, #VC12T = number of terminating VC-12s and #VC2T = number of terminating VC-2s.
One timeslot (64 kbit) of GMXBUS1 cannot be allocated. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. 31 VC-12s may have CAS capacity inside one GMXBUS. It means that 62 VC-12s may have CAS capacity. Control channels in the first octet of VC-12 payload are not supported. Tx AIS is not generated in G.704 termination, when X-bus-AIS (=B2-AIS) is detected. In the case of SNC/N protection, signal label values are not copied automatically from the terminating VCs to the monitoring VCs. Dual ended (bidirectional) MS 1+1 is not supported. Control channels in VC-4 POH with MS 1+1 protection are not supported.
Bugs
No known bugs.
13.2 Version 4.5

This is an unofficial test version.
13.3 Version 4.4

SLM and UNEQ alarms will get cleared after the alarm cause has disappeared (CR ID 300074269).

160
10004_22 2008 Tellabs.
The option to select a Fallback List Warning alarm in GMX is now using correct polarity. Fallback List Warning alarm generation is enabled when the Use quality levels option is disabled (CR ID 300067521). Trunk swap operates also when swap operations are done between the X-buses (CR ID 300073896). Message deleter deactivation added to all possible error branches (CR ID 300069654). The X-bus object attribute in GMX uses a correct macro (CR ID 300074470).
Dependencies
When GMXs are equipment protected (both GMXs installed) and synchronization input is taken from the STM-1 interface, both GMXs must have an interface module, even if the STM-1 interface in the protecting GMX is not used. GMX hardware version must be 3.0 or higher. If GMX is protected, the software versions of both GMXs must be the same, except during the middle phase of the software upgrade process. However if the hardware versions are different the software version must be the functionally equal version mentioned above. In the case GMX is protected, SCU-H (SCZ545) software version must be 1.11 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1.6 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1.5 or higher. MartisDXX Manager support for this unit without SBU functionality is available in Release 10.1A Service Pack 3 or higher. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. MartisDXX Manager support for group operation for setting recovery restriction for trunk operations is available in Release 11 Service Pack 4 or higher (CRF ID 4004476). MartisDXX Manager support for optional restricting of set operations while downloading unit software is available in Release 11 Service Pack 4 or higher (CRF ID 4004515).
Restrictions


63 VC-12s of SBU + 63 GMXs VC-12s or, 31 SNC/N protected VC-12s of SBU + 63 GMXs VC-12s or, 63 SNC/N protected GMXs VC-12s or, 20 SNC/N protected GMXs VC-2s + 3 SNC/N protected GMXs VC-12s or, a combination of the alternatives above so that 2*#E1 + #VC12M + 3*#VC2M 126 and #VC12T + 3*#VC2T 63, where #E1 = number of VC-12s of SBU, #VC12M = number of monitoring VC-12s, #VC2M = number of monitoring VC-2s,
10004_22 2008 Tellabs.

161
#VC12T = number of terminating VC-12s and #VC2T = number of terminating VC-2s.

Bugs
No known bugs.
13.4 Version 4.3

XSC FPGA init sequence has been modified to support init retries during unit initialization if FPGA initialization has been unsuccessful. This will reduce the probability of FPGA remaining in an uninitialized state. The fault Initialization error GMX A/B is activated if FPGA init has eventually not been successful. (CR ID 300041527). The fault Fallback list warning is activated if QL (Master clock quality level) use is enabled. Fault activation is a customer requirement. (CR ID 300038862) The fault Reconfiguring X-Connect Database does not any more activate unnecessarily in unprotected node after inventory create operation. (CR ID 300038153) MC RAI (Master Clock Remote Alarm Indication) problem has been fixed. (CR ID 300027029) EEPROM hardware read access is supported. (CR ID 300035385) FLS (Flash settings) module semafore problem has been fixed. (CR ID 300046898) EEIO (Eeprom IO) module semafore problem has been fixed. (CR ID 300047579) The MS protection switching time measurement does not any more use the internal timer in OTP ASIC but only QP timer. The ASIC timer has shown to be unreliable in some units. The 50ms switch time requirement measuring has been fixed. (CR ID 300056746)
Dependencies
When GMXs are equipment protected (both GMXs installed) and synchronization input is taken from the STM-1 interface, both GMXs must have an interface module, even if the STM-1 interface in the protecting GMX is not used.

162
10004_22 2008 Tellabs.
GMX hardware version must be 3.0 or higher. If GMX is protected, the software versions of both GMXs must be the same, except during the middle phase of the software upgrade process. However if the hardware versions are different the software version must be the functionally equal version mentioned above. In the case GMX is protected, SCU-H (SCZ545) software version must be 1.11 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1.6 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1.5 or higher. MartisDXX Manager support for this unit without SBU functionality is available in Release 10.1A Service Pack 3 or higher. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. MartisDXX Manager support for group operation for setting recovery restriction for trunk operations is available in Release 11 Service Pack 4 or higher (CRF ID 4004476). MartisDXX Manager support for optional restricting of set operations while downloading unit software is available in Release 11 Service Pack 4 or higher (CRF ID 4004515).
Restrictions


10004_22 2008 Tellabs.

163
Bugs

Under certain circumstances SLM and UNEQ alarms might stay on even if the alarm cause has disappeared (CR ID 300074269). Option to select Fallback List Warning alarm in GMX mistakenly used wrong polarity. Fallback list warning alarm generation should be enabled when "Use quality levels" is disabled, not vice versa (CR ID 300067521). Trunk swap does not operate correctly in GMX unit when swap between X-buses is applied (swap ports in upper and lower shelf). This may cause X-bus FAT allocation conflicts. FAT allocation table resources may not be de-allocated during swap or unswap operation. Swap inside one X-bus operates correctly (CR ID 300073896). Missing message deleter deactivation. In very rare circumstances it is possible that this causes unit to stop responding to NMS messages (CR ID 300069654). The X-bus object attribute in GMX uses a wrong macro (CR ID 300074470).
13.5 Version 4.2

This is emergency version to fix flash memory related problems in the device driver level. Flash problems have caused download and setup problems in some units. This version is functionally identical to version 4.1 and the problem exists only in GMZ544 software version 4.1. The versions 3.20 and 4.2 can be used together and replaced with each other in same node.
13.6 Version 4.1

Note: This version has serious flash device driver errors and it must not be used! Enhancements and Fixed Bugs (compared with version 3.18 / functionally same as 3.19)
If ports bigger than 140 timeslots are used the IA test timeslot does not overlap with port. This change is needed to support STE-10M when speeds over 8960 kbit/s are used. Otherwise data traffic would be affected (CR ID 200027037). The fault Reconfiguring X-connect database now activates a red led properly. Therefore, a switch over during reconfiguration is not anymore possible if a fault causing a switch over is activated. (CR ID 200026983). Memory overflow does not happen anymore when a GMU added to the node inventory or deleted from the node inventory, a GMU resets or the active GMX resets (CR ID 200026307). It is now possible to connect the whole capacity of all over-8M ports with a single management operation (CR ID 200010985 and 200014991). The user cannot anymore cause an illegal configuration by making copy/paste from a single VC-12 (asynchronous mode) to VC-12-mc/VC-12 using Tellabs 8100 network manager (CR ID 200011099).

164
10004_22 2008 Tellabs.
The QL value reported from the unit to the Master Clock State window is set to value 7 (Do Not Use) when there is an active problem in the clock source. Also the EXT clock QL is set to value 7 (DNU) when there is an active problem in the external clock source. This change concerns only the reporting of QL values. The actual selection logic in the unit has been working without any problems and remains unchanged (CR ID 200011222). Signalling cross connections cannot anymore accidentally to be made in timeslots that do not support CAS when creating cross connections for over-8M capacity ports (CR ID 200012052). The check of incoming message integrity is improved. The GMX unit is able to detect a message that has a consistency problem in the internal data structure. The processing of the invalid message is prevented. This will make the unit much more reliable in case of any communication problem. (CR ID 200012351) The possibility of GMX reset associated with table overflow in Fault Mask object has been fixed (CR ID 200012686). When GMX sends the state of the used clock source to the interface units the state value of the clock source data is not incorrectly set to NOT_OK (255) anymore in case the internal clock is used and the fallback list is not empty. Therefore, the neighbour node is able to apply the defined QL of the internal clock correctly (CR ID 200012836). The node reset (or simultaneous reset of both GMXs) during cross connection database reconfiguration cannot cause the corruption of cross connection database of GMX anymore. The reason was that the GMX with incomplete copy of the cross connection database could become active in the node reset. This is now prevented by storing the reconfiguration state in flash memory during reconfiguration and activating the Reconfiguring X-connect database fault again after reset according to the non-volatile fault state. Immediate switch over will automatically follow preventing the wrong GMX becoming active (CR ID 200013506). A new introduced fault Unit Initializing is active until it is safe to start configuring the unit. Note that this fault is introduced to inform operations personnel and there is no mechanism to prevent parameter changes if those are done in spite of the fault. In a protected node this fault must have been disappeared on both the GMX units before it is safe to start configuring GMXs. (CR ID 200018176). Wrong alarm handling in bit V5 fixed (VC-2/VC-12) (CR ID 200012057). A component batch problem detected in October 2003 in STM-1-LH-13 (ODH454, ODH703) interface modules has been corrected with component change (CCN2003108, effective date 17.11.2003). This component problem causes the USW to report LOF fault instead of LOS fault when the input signal is missing in that interface. The USW logic is changed to prevent the HW problem (CR ID 200012048).
10004_22 2008 Tellabs.

165
Dependencies

GMX hardware version must be 3.0 or higher. In the case GMX is protected, the software versions of GMXs must be the same, except during the middle phase of software upgrade process. In the case GMX is protected, SCU-H (SCZ545) software version must be 1.11 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1.6 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1.5 or higher. MartisDXX Manager support for this unit without SBU functionality is available in Release 10.1A Service Pack 3 or higher. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. MartisDXX Manager support for group operation for setting recovery restriction for trunk operations is available in Release 11 Service Pack 4 or higher (CRF ID 4004476). MartisDXX Manager support for optional restricting of set operations while downloading unit software is available in Release 11 Service Pack 4 or higher (CRF ID 4004515).
Restrictions


One timeslot (64 kbit) of GMXBUS1 cannot be allocated. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. 31 VC-12s may have CAS capacity inside one GMXBUS. It means that 62 VC-12s may have CAS capacity. Control channels in the first octet of VC-12 payload are not supported. Tx AIS is not generated in G.704 termination, when X-bus-AIS (=B2-AIS) is detected. In the case of SNC/N protection, signal label values are not copied automatically from the terminating VCs to the monitoring VCs. Dual ended (bidirectional) MS 1+1 is not supported.
10004_22 2008 Tellabs.

166
Control channels in VC-4 POH with MS 1+1 protection are not supported.
Bugs

Flash driver is not completely compatible with the used flash memory type. This bug may cause problems in unit download and unit non volatile parameters. XSC FPGA init may fail during unit initialization. FPGA init fail is traffic affecting. The unit has no fault indication if this error happens. (CR ID 300041527 ) The fault Fallback list warning does not activate. Fault activation is customer requirement. (CR ID 300038862) The fault Reconfiguring X-Connect Database may activate unnecessarily after inventory create operation in unprotected node. The activated fault does not disappear without service actions. (CR ID 300038153) MC RAI (Master Clock Remote Alarm Indication) feature does not operate because of a bug in application. (CR ID 300027029) EEPROM hardware read access is not supported. (CR ID 300035385) Initialization of FLS (Flash Settings) module has an internal problem with semafore handling. (CR ID 300046898) EEIO (Eeprom IO) module has an internal problem with semafore handling. (CR ID 300047579) The MS protection switching may fail due to OTP ASIC internal timer problem in some units. The 50ms switch time measuring has a small problem. (CR ID 300056746)
13.7 Version 3.24


1+1 protection switch does not cause fake SSF alarms on P12s (CR ID 300070961). Flash list record status bit handling has been fixed (CR ID 300092117). STM-1 loop timeout is not truncated in an STM-1 interface #2 (CR ID 300021040). LOF fault is not reported if P12s AIS reporting is disabled (CR ID 300021812).
Dependencies
When GMXs are equipment protected (both GMXs installed) and synchronization input is taken from the STM-1 interface, both GMXs must have an interface module, even if the STM-1 interface in the protecting GMX is not used. If GMX is protected, the software versions of both GMXs must be the same, except during the middle phase of the software upgrade process. However if the hardware versions are different the software version must be the functionally equal version mentioned above. GMX hardware version must be 2.0 or higher for S-bus/X-bus (VC-12 of SBU connected to GMXs VC-12) connections to be used, otherwise GMX hardware version must be 1.0 or higher. In the case GMX is protected, SCU-H (SCZ545) software version must be 1.11 or higher.
10004_22 2008 Tellabs.

167
In the case GMX is not protected the node works correctly only if SCU-H has SW version 1.6 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1.5 or higher. MartisDXX Manager support for this unit without SBU functionality is available in Release 10.1A Service Pack 3 or higher. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. MartisDXX Manager support for group operation for setting recovery restriction for trunk operations is available in Release 11 Service Pack 4 or higher (CRF ID 4004476). MartisDXX Manager support for optional restricting of set operations while downloading unit software is available in Release 11 Service Pack 4 or higher (CRF ID 4004515).
Restrictions


Bugs
No known bugs.

168
10004_22 2008 Tellabs.
13.8 Version 3.23

This is an unofficial test version.
13.9 Version 3.22


SLM and UNEQ alarms will get cleared after alarm cause has disappeared (CR ID 300074269). Option to select Fallback List Warning alarm in GMX is now using correct polarity. Fallback List Warning alarm generation is enabled when "Use quality levels" is disabled (CR ID 300067521). Trunk swap operates also when swap operations are done between the X-buses (CR ID 300073896). Message deleter deactivation added to all possible error branches (CR ID 300069654). The X-bus object attribute in GMX uses a correct macro (CR ID 300074470).
Dependencies
When GMXs are equipment protected (both GMXs installed) and synchronization input is taken from the STM-1 interface, both GMXs must have an interface module, even if the STM-1 interface in the protecting GMX is not used. If GMX is protected, the software versions of both GMXs must be the same, except during the middle phase of the software upgrade process. However if the hardware versions are different the software version must be the functionally equal version mentioned above. GMX hardware version must be 2.0 or higher for S-bus/X-bus (VC-12 of SBU connected to GMXs VC-12) connections to be used, otherwise GMX hardware version must be 1.0 or higher. In the case GMX is protected, SCU-H (SCZ545) software version must be 1.11 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1.6 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1.5 or higher. MartisDXX Manager support for this unit without SBU functionality is available in Release 10.1A Service Pack 3 or higher. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. MartisDXX Manager support for group operation for setting recovery restriction for trunk operations is available in Release 11 Service Pack 4 or higher (CRF ID 4004476). MartisDXX Manager support for optional restricting of set operations while downloading unit software is available in Release 11 Service Pack 4 or higher (CRF ID 4004515).
10004_22 2008 Tellabs.

169
Restrictions


Bugs
No known bugs.
13.10 Version 3.21

XSC FPGA init sequence has been modified to support init retries during unit initialization if FPGA initialization has been unsuccessful. This will reduce the probability of FPGA remaining in an uninitialized state. The fault Initialization error GMX A/B is activated if FPGA init has eventually not been successful. (CR ID 300041527). The fault Fallback list warning is activated if QL (Master clock quality level) use is enabled. Fault activation is a customer requirement. (CR ID 300038862) The fault Reconfiguring X-Connect Database does not any more activate unnecessarily in unprotected node after inventory create operation. (CR ID 300038153)
10004_22 2008 Tellabs.

170
MC RAI (Master Clock Remote Alarm Indication) problem has been fixed. (CR ID 300027029) EEPROM hardware read access is supported. (CR ID 300035385) FLS (Flash settings) module semafore problem has been fixed. (CR ID 300046898) EEIO (Eeprom IO) module semafore problem has been fixed. (CR ID 300047579) The MS protection switching time measurement does not any more use the internal timer in OTP ASIC but only QP timer. The ASIC timer has shown to be unreliable in some units. The 50ms switch time requirement measuring has been fixed. (CR ID 300056746)
Dependencies
When GMXs are equipment protected (both GMXs installed) and synchronization input is taken from the STM-1 interface, both GMXs must have an interface module, even if the STM-1 interface in the protecting GMX is not used. If GMX is protected, the software versions of both GMXs must be the same, except during the middle phase of the software upgrade process. However if the hardware versions are different the software version must be the functionally equal version mentioned above. GMX hardware version must be 2.0 or higher for S-bus/X-bus (VC-12 of SBU connected to GMXs VC-12) connections to be used, otherwise GMX hardware version must be 1.0 or higher. In the case GMX is protected, SCU-H (SCZ545) software version must be 1.11 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1.6 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1.5 or higher. MartisDXX Manager support for this unit without SBU functionality is available in Release 10.1A Service Pack 3 or higher. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. MartisDXX Manager support for group operation for setting recovery restriction for trunk operations is available in Release 11 Service Pack 4 or higher (CRF ID 4004476). MartisDXX Manager support for optional restricting of set operations while downloading unit software is available in Release 11 Service Pack 4 or higher (CRF ID 4004515).
Restrictions


63 VC-12s of SBU + 63 GMXs VC-12s or, 31 SNC/N protected VC-12s of SBU + 63 GMXs VC-12s or, 63 SNC/N protected GMXs VC-12s or, 20 SNC/N protected GMXs VC-2s + 3 SNC/N protected GMXs VC-12s or, a combination of the alternatives above so that 2*#E1 + #VC12M + 3*#VC2M 126 and #VC12T + 3*#VC2T 63, where #E1 =
171
10004_22 2008 Tellabs.
number of VC-12s of SBU, #VC12M = number of monitoring VC-12s, #VC2M = number of monitoring VC-2s, #VC12T = number of terminating VC-12s and #VC2T = number of terminating VC-2s.

One timeslot (64 kbit) of GMXBUS1 cannot be allocated. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. 31 VC12s may have CAS capacity inside one GMXBUS. It means that 62 VC-12s may have CAS capacity. Control channels in the first octet of VC-12 payload are not supported. Tx AIS is not generated in G.704 termination, when X-bus-AIS (=B2-AIS) is detected. In the case of SNC/N protection, signal label values are not copied automatically from the terminating VCs to the monitoring VCs. Dual ended (bidirectional) MS 1+1 is not supported. Control channels in VC-4 POH with MS 1+1 protection are not supported.
Bugs

Under certain circumstances SLM and UNEQ alarms might stay on even if the alarm cause has disappeared (CR ID 300074269). Option to select Fallback List Warning alarm in GMX mistakenly used wrong polarity. Fallback list warning alarm generation should be enabled when "Use quality levels" is disabled, not vice versa (CR ID 300067521). Trunk swap does not operate correctly in GMX unit when swap between X-buses is applied (swap ports in upper and lower shelf). This may cause XBUS FAT allocation conflicts. FAT allocation table resources may not be de-allocated during swap or unswap operation . Swap inside one XBUS operates correctly (CR ID 300073896). Missing message deleter deactivation. In very rare circumstances it is possible that this causes unit to stop responding to NMS messages (CR ID 300069654). The X-bus object attribute in GMX uses a wrong macro (CR ID 300074470).
13.11 Version 3.20

This is emergency version to achieve operative compatibility between GMX hardware versions 1.0, 2.0 and 3.0. The software version 3.20 used in hardware versions 1.0 and 2.0 is functionally identical and compatible with software version 4.2 used in hardware version 3.0. When compared to 3.19 one communication delay was adjusted according to the version 4.2. (CR ID 300038634). The versions 3.20 and 4.2 can be used together and replaced with each other in same node.

172
10004_22 2008 Tellabs.
13.12 Version 3.19

Enhancements and Fixed Bugs (compared with version 3.18)
If ports bigger than 140 timeslots are used the IA test timeslot does not overlap with port. This change is needed to support STE-10M when speeds over 8960 kbit/s are used. Otherwise data traffic would be affected (CR ID 200027037). The fault Reconfiguring X-connect database now activates a red led properly. Therefore, a switch over during reconfiguration is not anymore possible if a fault causing a switch over is activated. (CR ID 200026983). Memory overflow does not happen anymore when a GMU added to the node inventory or deleted from the node inventory, a GMU resets or the active GMX resets (CR ID 200026307). It is now possible to connect the whole capacity of all over-8M ports with a single management operation (CR ID 200010985 and 200014991). The user cannot anymore cause an illegal configuration by making copy/paste from a single VC-12 (asynchronous mode) to VC-12-mc/VC-12 using Tellabs 8100 network manager (CR ID 200011099). The QL value reported from the unit to the Master Clock State window is set to value 7 (Do Not Use) when there is an active problem in the clock source. Also the EXT clock QL is set to value 7 (DNU) when there is an active problem in the external clock source. This change concerns only the reporting of QL values. The actual selection logic in the unit has been working without any problems and remains unchanged (CR ID 200011222). Signalling cross connections cannot anymore accidentally to be made in timeslots that do not support CAS when creating cross connections for over-8M capacity ports (CR ID 200012052). The check of incoming message integrity is improved. The GMX unit is able to detect a message that has a consistency problem in the internal data structure. The processing of the invalid message is prevented. This will make the unit much more reliable in case of any communication problem. (CR ID 200012351) The possibility of GMX reset associated with table overflow in Fault Mask object has been fixed (CR ID 200012686). When GMX sends the state of the used clock source to the interface units the state value of the clock source data is not incorrectly set to NOT_OK (255) anymore in case the internal clock is used and the fallback list is not empty. Therefore, the neighbour node is able to apply the defined QL of the internal clock correctly (CR ID 200012836). The node reset (or simultaneous reset of both GMXs) during cross connection database reconfiguration cannot cause the corruption of cross connection database of GMX anymore. The reason was that the GMX with incomplete copy of the cross connection database could become active in the node reset. This is now prevented by storing the reconfiguration state in flash memory during reconfiguration and activating the Reconfiguring X-connect database fault again after reset according to the non-volatile fault state. Immediate switch over will automatically follow preventing the wrong GMX becoming active (CR ID 200013506). A new introduced fault Unit Initializing is active until it is safe to start configuring the unit. Note that this fault is introduced to inform operations personnel and there is no mechanism to prevent parameter changes if those are done in spite of the fault. In a protected node this
10004_22 2008 Tellabs.

173
fault must have been disappeared on both the GMX units before it is safe to start configuring GMXs. (CR ID 200018176).

Wrong alarm handling in bit V5 fixed (VC-2/VC-12) (CR ID 200012057). A component batch problem detected in October 2003 in STM1-LH-13 (ODH454, ODH703) interface modules has been corrected with component change (CCN2003108, effective date 17.11.2003). This component problem causes the USW to report LOF fault instead of LOS fault when the input signal is missing in that interface. The USW logic is changed to prevent the HW problem (CR ID 200012048).
Dependencies

In the case GMX is protected, the software versions of GMXs must be the same, except during the middle phase of software upgrade process. GMX hardware version must be 2.0 or higher for S-bus/X-bus (VC-12 of SBU connected to GMXs VC-12) connections to be used, otherwise GMX hardware version must be 1.0 or higher. In the case GMX is protected, SCU-H (SCZ545) software version must be 1.11 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1.6 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1.5 or higher. MartisDXX Manager support for this unit without SBU functionality is available in Release 10.1A Service Pack 3 or higher. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. MartisDXX Manager support for group operation for setting recovery restriction for trunk operations is available in Release 11 Service Pack 4 or higher (CRF ID 4004476). MartisDXX Manager support for optional restricting of set operations while downloading unit software is available in Release 11 Service Pack 4 or higher (CRF ID 4004515).
Restrictions

The control channel in the R0 byte of VC-12 is forbidden because of unreliable HW functionality. Monitoring VC-12/2s in GMX use the same TU-bus internal resources as VC-12s in SBU. The total capacity for VC12/2s is (in the case of two protected GMXs):


174
10004_22 2008 Tellabs.
Bugs

XSC FPGA init may fail during unit initialization. FPGA init fail is traffic affecting. The unit has no fault indication if this error happens. (CR ID 300041527 ) The fault Fallback list warning does not activate. Fault activation is customer requirement. (CR ID 300038862) The fault Reconfiguring X-Connect Database may activate unnecessarily after inventory create operation in unprotected node. The activated fault does not disappear without service actions. (CR ID 300038153) MC RAI (Master Clock Remote Alarm Indication) feature does not operate because of a bug in application. (CR ID 300027029) EEPROM hardware read access is not supported. (CR ID 300035385) Initialization of FLS (Flash Settings) module has an internal problem with semafore handling. (CR ID 300046898) EEIO (Eeprom IO) module has an internal problem with semafore handling. (CR ID 300047579) The MS protection switching may fail due to OTP ASIC internal timer problem in some units. The 50ms switch time measuring has a small problem. (CR ID 300056746)
13.13 Version 3.18

GMX now supports reconfiguration of cross-connections on the passive GMX without resets. This eliminates unnecessary resets on the passive side affecting the traffic in STM-1 interface of the passive GMX. It also prevents a possible rare reset loop condition in the passive GMX caused by reconfigurations initiated by Recovery Server. (CR ID 200005094). Supports the use of ESU in Tellabs 8160 A111 (CR ID 200005401). No purposeless power supply alarms appear anymore in certain rare situations, because the statistical handling of voltage measurement samples has been corrected (CR ID 200008442). When X-bus distribution is set to 'even' while P12s signal mapping mode is 'asynchronous', 'uneven' X-bus distribution is used however. This is because of a bug in LTA ASIC causing
10004_22 2008 Tellabs.

175
the combination of X-bus distribution being 'even' and P12s signal mapping mode being 'asynchronous' for VC-12 not to work reliably in all situations.

R0 byte of VC-12 cannot be used for control channel anymore because of unreliable HW functionality. SETUP0 checksum calculation and comparison between GMXs works reliably. GMX's fault timestamps are now shown always correctly in FMS apart from very rare situation of timestamp being circa 497 days too old (=0xFFFFFFFF in 10 ms units) (CR ID 200005139). SNC/N protection for GMXs VC-12/2s can now be used together with S-bus connections (VC-12s of SBU connected to GMXs TU12s or VC-12s). Also VC-12s of SBU can be SNC/N protected. AIS and LOF from P12 adaptation layer generate now UNAVAIL to P12sTTP (CR ID 200005178). When MS 1+1 parameters are updated to GMX, the VC-4 timaAisEnabled flag is copied from the protected interface to the protecting interface. A possible DB/HW inconsistency in Tellabs 8100 network manager is therefore prevented. VC-4 fault filtering works now correctly also if MS 1+1 protection is activated and the protection switch uses the interface of the passive GMX. GMX switchover reliability has been further improved by adding TUG3 structure refresh (settings reside in LAC ASIC) mechanism at the end of the switchover sequence. 15 minutes performance event delta faults are not shown twice anymore, because only the active GMX of the node announces the fault for VC-12/2- and P12 -layers (CR ID 200005169). TS usage for VC-12/2 parameters is now shown correctly by Tellabs 8100 network manager also in the case GMX is protected and the lower GMX is the active crossconnection unit (CR ID 200005293). All delta event faults are now transferred to Tellabs 8100 network manager (CR ID 200005197). Purposeless Crc. err LAC RAM 1/2/3/4 alarm cannot occur anymore (CR ID 200005197). Performance counting is not stopped anymore in case TU cross-connection for VC-12/VC2 is missing (CR ID 200005168). Purposeless reset alarms without a reset cannot occur anymore (CR ID 200005079). Bit errors do not occur anymore if update is pressed in the Tellabs 8100 network manager interface parameters window of one of the P12s objects (CR ID 200008033). Performance source setting works now in the Tellabs 8100 network manager interface parameters window for VC-12/2s (CR ID 200005199).
Dependencies

In the case GMX is protected, the software versions of GMXs must be the same, except during the middle phase of software upgrade process. GMX hardware version must be 2.0 or higher for S-bus/X-bus (VC-12 of SBU connected to GMXs VC-12) connections to be used, otherwise GMX hardware version must be 1.0 or higher. In the case GMX is protected, SCU-H (SCZ545) software version must be 1.11 or higher.

176
10004_22 2008 Tellabs.
In the case GMX is not protected the node works correctly only if SCU-H has SW version 1.6 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1.5 or higher. MartisDXX Manager support for this unit without SBU functionality is available in Release 10.1A Service Pack 3 or higher. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. MartisDXX Manager support for group operation for setting recovery restriction for trunk operations is available in Release 11 Service Pack 4 or higher (CRF ID 4004476). MartisDXX Manager support for optional restricting of set operations while downloading unit software is available in Release 11 Service Pack 4 or higher (CRF ID 4004515).
Restrictions

Does not support the improved check of incoming message integrity (CR ID 200012351). Does not support the fault Unit Initializing (CR ID 200018176). The control channel in the R0 byte of VC-12 is forbidden because of unreliable HW functionality. Monitoring VC-12/2s in GMX use the same TU-bus internal resources as VC-12s in SBU. The total capacity for VC-12/2s is (in the case of two protected GMXs):

10004_22 2008 Tellabs.

177
Bugs
If ports bigger than 140 timeslots are used the IA test timeslot overlaps with port data causing data errors. Therefore IA test is modified so that a bigger test timeslot is automatically used (CR ID 200027037). The fault Reconfiguring X-connect database activates a yellow led instead of a proper red led. Therefore, a switch over during reconfiguration is possible if a fault causing a switch over is activated. This may lead the node to lose cross connections (CR ID 200026983). Memory overflow may happen when a GMU added to the node inventory or deleted from the node inventory, a GMU resets or the active GMX resets (CR ID 200026307). It is not possible to connect the whole capacity of all over-8M ports with a single management operation (CR ID 200010985 and 200014991). The quality level value of external clock input in master clock status window is shown as set in parameters even when the actual used quality level may be DNU because of an active problem. This error has no functional effects but may be confusing (CR ID 200011222). Signalling cross connections can accidentally to be made in timeslots that do not support CAS when creating cross connections for over-8M capacity ports (CR ID 200012052). There is a possibility of reset associated with Fault Mask object has been fixed (CR ID 200012686). When GMX sends the state of the used clock source to the interface units the state value of the clock source data is set to NOT_OK (255) if the used clock is internal and the FBL is not empty and therefore the neighbor node does not apply the defined QL of the internal clock correctly (CR ID 200012836). Node cross-connection database corruption in GMX may follow after node reset if reconfiguration has not been complete before it. The reason is the possibility of Xconnection database incomplete copy in the GMX that becomes active in the node (CR 200013506). Wrong alarm handling in bit V5 (VC-2/VC-12) (CR ID 200012057). A HW bug in STM1-LH-13 interface module has been noticed during Oct. 2003 and component change CCN2003108 has been planned to solve the problem. When realized, the bug makes OTP asic to see erroneous dLOS and dLOF values, which further makes the USW to not report LOS and LOF faults correctly in that interface (CR ID 200012048). Alarm problems:

The Phase locked loop and 20 MHz node clock missing alarms are active for a while after GMX reset. PLL alarm does not work in the case of a clock loop.
13.14 Version 3.17

Fault HDLC/XBUS in same TS is not raised needlessly anymore. In version 3.16, this happened if control channel 2 was set to VC-4 POH and there existed a VC-12/2 with Xbus port 1 and its timeslot 0 was connected to X-bus (CRF ID 4005016). However, both traffic and control channel worked despite the alarm.

178
10004_22 2008 Tellabs.
Dependencies

In the case GMX is protected, the software versions of GMXs must be the same, except during the middle phase of software upgrade process. GMX hardware version must be 2.0 or higher for S-bus/X-bus (VC-12 of SBU connected to GMXs VC-12) connections to be used, otherwise GMX hardware version must be 1.0 or higher In the case GMX is protected, SCU-H (SCZ545) software version must be 1.11 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1.6 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1.5 or higher. MartisDXX Manager support for this unit without SBU functionality is available in Release 10.1A Service Pack 3 or higher. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. MartisDXX Manager support for group operation for setting recovery restriction for trunk operations is available in Release 11 Service Pack 4 or higher (CRF ID 4004476). MartisDXX Manager support for optional restricting of set operations while downloading unit software is available in Release 11 Service Pack 4 or higher (CRF ID 4004515).
Restrictions

The control channel in the R0 byte of VC-12 should not be used because of unreliable HW functionality. Supports reconfiguration with reset only (CR ID 200005094). Does not support the use of ESU (CR ID 200005401). SNC/N protection for GMXs VC-12/2s cannot be used if S-bus (VC-12s of SBU connected to GMXs TU12s or VC-12s) connections are used and vice versa. One timeslot (64 kbit) of GMXBUS1 cannot be allocated. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. 31 VC-12s may have CAS capacity inside one GMXBUS. It means that 62 VC-12s may have CAS capacity. Control channels in the first octet of VC-12 payload are not supported. Tx AIS is not generated in G.704 termination, when X-bus-AIS (=B2-AIS) is detected. In the case of SNC/N protection, signal label values are not copied automatically from the terminating VCs to the monitoring VCs. Dual ended (bidirectional) MS 1+1 is not supported. Control channels in VC-4 POH with MS 1+1 protection are not supported.
Bugs
The fault Reconfiguring X-connect database activates a yellow led instead of a proper red led. Therefore, a switch over during reconfiguration is possible if a fault causing a switch over is activated. This may lead the node to lose cross connections (CR ID 200026983).
10004_22 2008 Tellabs.

179
The quality level value of external clock input in master clock status window is shown as set in parameters even when the actual used quality level may be DNU because of an active problem. This error has no functional effects but may be confusing (CR ID 200011222). In rare occasions, delta event faults may not be transferred to Tellabs 8100 network manager (CR ID 200005197). Purposeless Crc. err LAC RAM 1/2/3/4 alarm can occur sometimes (CR ID 200005197). Performance counting is stopped when TU cross-connection for VC-12/VC-2 is missing (CR ID 200005168). Purposeless reset alarms without a reset can occur rarely (CR ID 200005079). Purposeless power supply alarms may appear in certain rare situations (CR ID 200008442). A burst of bit errors occurs if update is pressed in the Tellabs 8100 network manager interface parameters window of one of the P12s objects of (CR ID 200008033). Because of a bug in LTA ASIC, the combination of X-bus distribution being even and P12s signal mapping mode being asynchronous for VC-12 does not work reliably in all situations. Performance source setting is inactive in the Tellabs 8100 network manager interface parameters window for VC-12/2s, viz. the performance source does not change in HW (CR ID 200005199). SETUP0 checksum calculation and comparing between GMXs does not work reliably in all situations. GMXs fault timestamps may be shown incorrectly (very rarely) in FMS. In case this realizes the timestamp is always circa 497 days too old (=0xFFFFFFFF in 10 ms units) (CR ID 200005139). P12s performance monitoring does not count unavailable time during AIS and LOF signal fail conditions (CR ID 200005178). When MS 1+1 parameters are updated to GMX, the VC-4 timaAisEnabled flag gets the default value (ON) in the protecting interface. This causes DB/HW inconsistency, if the protected interface does have this flag OFF. The flag should be copied from the protected interface to the protecting interface. 15 minutes performance event delta fault is announced by both GMXs of the node for VC12/2- and P12 layers. Therefore those faults appear twice in FMS (CR ID 200005169). In the case GMX is protected and lower GMX is the active cross-connection unit, 'TS usage' of VC12/2 parameters is shown faulty by NMS. Then all cross-connected timeslots are shown with usage 'free' instead of the correct usage information 'In use' (CR ID 200005293). Alarm problems:

The Phase locked loop and 20 MHz node clock missing alarms are active for a while after GMX reset. VC-4 fault filtering does not work if MS 1+1 protection is activated and protection switch uses the interface of the passive GMX. PLL alarm does not work in the case of a clock loop.

180
10004_22 2008 Tellabs.
13.15 Version 3.16

This is an official emergency version based on version 3.15. This version should not be used once the next official version is available. Enhancements and Fixed Bugs (compared with version 3.15)

ASIC register monitoring process has been implemented. The process monitors all SDH ASICs of GMX on background and corrects possible corrupted values in registers. Handling of LTA ASIC hardware link between GMXs of a node has been fixed. This bug could prevent SNC switch proper functioning after GMX switchover (equipment protection switch) in earlier versions. Interrupt and fault monitoring activity filtering during GMX switchover sequence (equipment protection switch) has been implemented. This adds switchover reliability against fault monitoring or ASIC register corruption, which was possible to take place and cause erroneous faults and/or deterioration of data in earlier versions. A bug in master clock module being able to cause spontaneous reset of GMX unit with very low probability has been corrected. Performance monitoring QOSTR lower SES threshold is now compared correctly against zero.
Dependencies

In the case GMX is protected, the software versions of GMXs must be the same, except during the middle phase of software upgrade process. GMX hardware version must be 2.0 or higher for S-bus/X-bus (VC-12 of SBU connected to GMXs VC-12) connections to be used, otherwise GMX hardware version must be 1.0 or higher In the case GMX is protected, SCU-H (SCZ545) software version must be 1.11 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1.6 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1.5 or higher. MartisDXX Manager support for this unit without SBU functionality is available in Release 10.1A Service Pack 3 or higher. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. MartisDXX Manager support for group operation for setting recovery restriction for trunk operations is available in Release 11 Service Pack 4 or higher (CRF ID 4004476). MartisDXX Manager support for optional restricting of set operations while downloading unit software is available in Release 11 Service Pack 4 or higher (CRF ID 4004515).
Restrictions

The control channel in the R0 byte of VC-12 should not be used because of unreliable HW functionality. Supports reconfiguration with reset only (CR ID 200005094).
10004_22 2008 Tellabs.

181
Does not support the use of ESU (CR ID 200005401). SNC/N protection for GMXs VC-12/2s cannot be used if S-bus (VC-12s of SBU connected to GMXs TU12s or VC-12s) connections are used and vice versa. One timeslot (64 kbit) of GMXBUS1 cannot be allocated. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. 31 VC-12s may have CAS capacity inside one GMXBUS. It means that 62 VC-12s may have CAS capacity. Control channels in the first octet of VC-12 payload are not supported. Tx AIS is not generated in G.704 termination, when X-bus-AIS (=B2-AIS) is detected. In the case of SNC/N protection, signal label values are not copied automatically from the terminating VCs to the monitoring VCs. Dual ended (bidirectional) MS 1+1 is not supported. Control channels in VC-4 POH with MS 1+1 protection are not supported.
Bugs
The fault Reconfiguring X-connect database activates a yellow led instead of a proper red led. Therefore, a switch over during reconfiguration is possible if a fault causing a switch over is activated. This may lead the node to lose cross connections (CR ID 200026983). The quality level value of external clock input in master clock status window is shown as set in parameters even when the actual used quality level may be DNU because of an active problem. This error has no functional effects but may be confusing (CR ID 200011222). In rare occasions, delta event faults may not be transferred to Tellabs 8100 network manager (CR ID 200005197). Purposeless Crc. err LAC RAM 1/2/3/4 alarm can occur sometimes (CR ID 200005197). Performance counting is stopped when TU cross-connection for VC-12/VC-2 is missing (CR ID 200005168). Purposeless reset alarms without a reset can occur rarely (CR ID 200005079). Purposeless power supply alarms may appear in certain rare situations (CR ID 200008442). A burst of bit errors occurs if update is pressed in the Tellabs 8100 network manager interface parameters window of one of the P12s objects of (CR ID 200008033). Because of a bug in LTA ASIC, the combination of X-bus distribution being even and P12s signal mapping mode being asynchronous for VC-12 does not work reliably in all situations. Performance source setting is inactive in the Tellabs 8100 network manager interface parameters window for VC-12/2s, viz. the performance source does not change in HW (CR ID 200005199). SETUP0 checksum calculation and comparing between GMXs does not work reliably in all situations. GMXs fault timestamps may be shown incorrectly (very rarely) in FMS. In case this realizes the timestamp is always circa 497 days too old (=0xFFFFFFFF in 10 ms units) (CR ID 200005139). P12s performance monitoring does not count unavailable time during AIS and LOF signal fail conditions (CR ID 200005178).

182
10004_22 2008 Tellabs.
When MS 1+1 parameters are updated to GMX, the VC-4 timaAisEnabled flag gets the default value (ON) in the protecting interface. This causes DB/HW inconsistency, if the protected interface does have this flag OFF. The flag should be copied from the protected interface to the protecting interface. 15 minutes performance event delta fault is announced by both GMXs of the node for VC12/2- and P12 layers. Therefore those faults appear twice in FMS (CR ID 200005169). In the case GMX is protected and lower GMX is the active cross-connection unit, 'TS usage' of VC-12/2 parameters is shown faulty by NMS. Then all cross-connected timeslots are shown with usage 'free' instead of the correct usage information 'In use' (CR ID 200005293). Fault HDLC/XBUS in same TS is raised needlessly if control channel 2 is set to VC-4 POH and there exists a VC-12/2 with X-bus port 1 and its timeslot 0 is connected to X-bus. Alarm problems:

13.16 Version 3.15


Cross-connections between E1VC-12s (VC12 of SBU) and GMX's VC-12s are supported (CRF ID 4004076). SS-bit values in AU4 pointer do not have to be 10 anymore. Therefore, this software version can be used to connect GMX to SONET equipment. (CRF ID 4004546). This version prevents GMX from performing spontaneous resets. The reasons were found and corresponding fixes were done (CRF ID 4004477). Cause for cuts in data through SNC/N protected vcGtps (virtual concatenation groups) of VC-12/2s was found and corrected (CRF ID 4004229). Deleting and creating timeslot connections with CAS do not affect other CAS connections for the corresponding trunk anymore (CRF ID 4004509). 15 minutes performance event delta fault is announced for RS-, MS-, VC4-, VC-12/2- or P12 layer if there has been performance deterioration during the previous 15-minute period (CRF ID 4003053). Performance monitoring thresholds QOSTR lower BBE and lower ES are compared correctly (CRF ID 4003406).
Dependencies
In the case GMX is protected, the software versions of GMXs must be the same, except during the middle phase of software upgrade process.
10004_22 2008 Tellabs.

183
GMX hardware version must be 2.0 or higher for S-bus/X-bus (VC-12 of SBU connected to GMXs VC-12) connections to be used, otherwise GMX hardware version must be 1.0 or higher SCU-H (SCZ545) software version must be 1.3 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1.6 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1.5 or higher. SNC protection works only if SCU-H has SW version 1.3 or higher. MartisDXX Manager support for this unit without SBU functionality is available in Release 10.1A Service Pack 3 or higher. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. MartisDXX Manager support for group operation for setting recovery restriction for trunk operations is available in Release 11 Service Pack 4 or higher (CRF ID 4004476). MartisDXX Manager support for optional restricting of set operations while downloading unit software is available in Release 11 Service Pack 4 or higher (CRF ID 4004515).
Restrictions

The control channel in the R0 byte of VC-12 should not be used because of unreliable HW functionality. Supports reconfiguration with reset only (CR ID 200005094). Does not support the use of ESU (CR ID 200005401). SNC/N protection for GMXs VC-12/2s cannot be used if S-bus (VC-12s of SBU connected to GMXs TU12s or VC-12s) connections are used and vice versa. One timeslot (64 kbit) of GMXBUS1 cannot be allocated. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. 31 VC-12s may have CAS capacity inside one GMXBUS. It means that 62 VC-12s may have CAS capacity. Control channels in the first octet of VC-12 payload are not supported. Tx AIS is not generated in G.704 termination, when X-bus-AIS (=B2-AIS) is detected. In the case of SNC/N protection, signal label values are not copied automatically from the terminating VCs to the monitoring VCs. Dual ended (bidirectional) MS 1+1 is not supported. Control channels in VC-4 POH with MS 1+1 protection are not supported.
Bugs
The fault Reconfiguring X-connect database activates a yellow led instead of a proper red led. Therefore, a switch over during reconfiguration is possible if a fault causing a switch over is activated. This may lead the node to lose cross connections (CR ID 200026983). The quality level value of external clock input in master clock status window is shown as set in parameters even when the actual used quality level may be DNU because of an active problem. This error has no functional effects but may be confusing (CR ID 200011222).

184
10004_22 2008 Tellabs.
In rare occasions, delta event faults may not be transferred to Tellabs 8100 network manager (CR ID 200005197). Purposeless Crc. err LAC RAM 1/2/3/4 alarm can occur sometimes (CR ID 200005197). Performance counting is stopped when TU cross-connection for VC-12/VC-2 is missing (CR ID 200005168). Purposeless reset alarms without a reset can occur rarely (CR ID 200005079). Purposeless power supply alarms may appear in certain rare situations (CR ID 200008442). A burst of bit errors occurs if update is pressed in the Tellabs 8100 network manager interface parameters window of one of the P12s objects of (CR ID 200008033). Because of a bug in LTA ASIC, the combination of X-bus distribution being even and P12s signal mapping mode being asynchronous for VC-12 does not work reliably in all situations. Performance source setting is inactive in the Tellabs 8100 network manager interface parameters window for VC-12/2s, viz. the performance source does not change in HW (CR ID 200005199). SETUP0 checksum calculation and comparing between GMXs does not work reliably in all situations. GMXs fault timestamps may be shown incorrectly (very rarely) in FMS. In case this realizes the timestamp is always circa 497 days too old (=0xFFFFFFFF in 10 ms units) (CR ID 200005139). P12s performance monitoring does not count unavailable time during AIS and LOF signal fail conditions (CR ID 200005178). When MS 1+1 parameters are updated to GMX, the VC-4 timaAisEnabled flag gets the default value (ON) in the protecting interface. This causes DB/HW inconsistency, if the protected interface does have this flag OFF. The flag should be copied from the protected interface to the protecting interface. 15 minutes performance event delta fault is announced by both GMXs of the node for VC12/2- and P12 layers. Therefore those faults appear twice in FMS (CR ID 200005169). In the case GMX is protected and lower GMX is the active cross-connection unit, 'TS usage' of VC-12/2 parameters is shown faulty by NMS. Then all cross-connected timeslots are shown with usage 'free' instead of the correct usage information 'In use' (CR ID 200005293). With a small probability, some SDH ASIC register values may become corrupted during GMX switchover (equipment protection switch) and cause data deterioration. With a small probability, handling of LTA ASIC hardware link between GMXs of a node during GMX switchover (equipment protection switch) may not function correctly and cause improper functioning of SNC protection switch. With a small probability, a burst of interrupts resulting from GMX switchover (equipment protection switch) may cause fault monitoring inconsistency and/or SDH ASIC register values corruptions, leading to erroneous faults and/or deteriorated data. Performance monitoring QOSTR lower SES threshold is compared faulty (should be permanently = 0). The SES count is compared erroneously to the given SES threshold which acts now as the upper and lower limit while it should act as upper limit only. Alarm problems:
10004_22 2008 Tellabs.

185
The Phase locked loop and 20 MHz node clock missing alarms are active for a while after GMX reset. VC4 fault filtering does not work if MS 1+1 protection is activated and protection switch uses the interface of the passive GMX. PLL alarm does not work in the case of a clock loop.
13.17 Version 3.13

This is an official emergency version based on version 3.12. This version should not be used once the next official version is available. Dependencies

In the case GMX is protected, the software versions of GMXs must be the same, except during the middle phase of software upgrade process. GMX hardware version must be 1.0 or higher. SCU-H (SCZ545) software version must be 1.3 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1.6 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1.5 or higher. SNC protection works only if SCU-H has SW version 1.3 or higher. MartisDXX Manager support for this unit without SBU functionality is available in Release 10.1A Service Pack 3 or higher. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher.
Restrictions

The control channel in the R0 byte of VC-12 should not be used because of unreliable HW functionality. Supports reconfiguration with reset only (CR ID 200005094). Does not support the use of ESU (CR ID 200005401). GMX generates fault Loss of AU4 pointer if SS-bit values in AU4 pointer differ from 10. This prevents GMX to be connected to SONET equipment. SNC/N protection for GMXs VC-12/2s cannot be used if S-bus (VC-12s of SBU connected to GMXs TU12s) connections are used and vice versa. Cross-connections between E1VC-12s (VC12 of SBU) and GMX's VC-12s are not supported. One timeslot (64 kbit) of GMXBUS1 cannot be allocated. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. 31 VC-12s may have CAS capacity inside one GMXBUS. It means that 62 VC-12s may have CAS capacity. Control channels in the first octet of VC-12 payload are not supported.

186
10004_22 2008 Tellabs.
Tx AIS is not generated in G.704 termination, when X-bus-AIS (=B2-AIS) is detected. In the case of SNC/N protection, signal label values are not copied automatically from the terminating VCs to the monitoring VCs. Dual ended (bidirectional) MS 1+1 is not supported. Control channels in VC-4 POH with MS 1+1 protection are not supported.
Bugs
The fault Reconfiguring X-connect database activates a yellow led instead of a proper red led. Therefore, a switch over during reconfiguration is possible if a fault causing a switch over is activated. This may lead the node to lose cross connections (CR ID 200026983). The quality level value of external clock input in master clock status window is shown as set in parameters even when the actual used quality level may be DNU because of an active problem. This error has no functional effects but may be confusing (CR ID 200011222). In rare occasions, delta event faults may not be transferred to Tellabs 8100 network manager (CR ID 200005197). Purposeless Crc. err LAC RAM 1/2/3/4 alarm can occur sometimes (CR ID 200005197). Performance counting is stopped when TU cross-connection for VC-12/VC-2 is missing (CR ID 200005168). Purposeless reset alarms without a reset can occur rarely (CR ID 200005079). Purposeless power supply alarms may appear in certain rare situations (CR ID 200008442). A burst of bit errors occurs if update is pressed in the Tellabs 8100 network manager interface parameters window of one of the P12s objects of (CR ID 200008033). Because of a bug in LTA ASIC, the combination of X-bus distribution being even and P12s signal mapping mode being asynchronous for VC12 does not work reliably in all situations. SETUP0 checksum calculation and comparing between GMXs does not work reliably in all situations. GMXs fault timestamps may be shown incorrectly (very rarely) in FMS. In case this realizes the timestamp is always circa 497 days too old (=0xFFFFFFFF in 10 ms units) (CR ID 200005139). P12s performance monitoring does not count unavailable time during AIS and LOF signal fail conditions (CR ID 200005178). When MS 1+1 parameters are updated to GMX, the VC-4 timaAisEnabled flag gets the default value (ON) in the protecting interface. This causes DB/HW inconsistency, if the protected interface does have this flag OFF. The flag should be copied from the protected interface to the protecting interface. In the case GMX is protected and lower GMX is the active cross-connection unit, 'TS usage' of VC-12/2 parameters is shown faulty by NMS. Then all cross-connected timeslots are shown with usage 'free' instead of the correct usage information 'In use' (CR ID 200005293). With a small probability, some SDH ASIC register values may become corrupted during GMX switchover (equipment protection switch). With a small probability, handling of LTA ASIC hardware link between GMXs of a node during GMX switchover (equipment protection switch) may not function correctly.
10004_22 2008 Tellabs.

187
With a small probability, a burst of interrupts resulting from GMX switchover (equipment protection switch) may cause fault monitoring inconsistency and/or SDH ASIC register values corruptions. Deleting one or more timeslot connections with CAS will disable all other CAS connections for the corresponding trunk. Recreating at least one timeslot connection with CAS will enable all connections for that trunk again. Performance monitoring thresholds QOSTR lower BBE, lower ES and lower SES (always = 0) are compared faulty. Now QOSTR lower BBE and lower ES are activated when the number of BBE or ES in the 15 minute period is less than (<) the threshold value (should be less or equal (< or =)). SES lower threshold is compared erroneously to the given SES threshold which should act as upper limit only. TTI expected value of SNC/I protected E1VC-12 (VC-12 of SBU) cannot be changed Alarm problems:

13.18 Version 3.12


Restrictions

The control channel in the R0 byte of VC-12 should not be used because of unreliable HW functionality. Supports reconfiguration with reset only (CR ID 200005094).

188
10004_22 2008 Tellabs.
Does not support the use of ESU (CR ID 200005401). GMX generates fault Loss of AU4 pointer if SS-bit values in AU4 pointer differ from 10. This prevents GMX to be connected to SONET equipment. SNC/N protection for GMXs VC-12/2s cannot be used if S-bus (VC-12s of SBU connected to GMXs TU12s) connections are used and vice versa. Cross-connections between E1VC-12s (VC-12 of SBU) and GMX's VC-12s are not supported. One timeslot (64 kbit) of GMXBUS1 cannot be allocated. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. 31 VC-12s may have CAS capacity inside one GMXBUS. It means that 62 VC-12s may have CAS capacity. Control channels in the first octet of VC-12 payload are not supported. Tx AIS is not generated in G.704 termination, when X-bus-AIS (=B2-AIS) is detected. In the case of SNC/N protection, signal label values are not copied automatically from the terminating VCs to the monitoring VCs. Dual ended (bidirectional) MS 1+1 is not supported. Control channels in VC-4 POH with MS 1+1 protection are not supported.
Bugs
The fault Reconfiguring X-connect database activates a yellow led instead of a proper red led. Therefore, a switch over during reconfiguration is possible if a fault causing a switch over is activated. This may lead the node to lose cross connections (CR ID 200026983). The quality level value of external clock input in master clock status window is shown as set in parameters even when the actual used quality level may be DNU because of an active problem. This error has no functional effects but may be confusing (CR ID 200011222). In rare occasions, delta event faults may not be transferred to Tellabs 8100 network manager (CR ID 200005197). Purposeless Crc. err LAC RAM 1/2/3/4 alarm can occur sometimes (CR ID 200005197). Performance counting is stopped when TU cross-connection for VC-12/VC-2 is missing (CR ID 200005168). Purposeless reset alarms without a reset can occur rarely (CR ID 200005079). Purposeless power supply alarms may appear in certain rare situations (CR ID 200008442). A burst of bit errors occurs if update is pressed in the Tellabs 8100 network manager interface parameters window of one of the P12s objects of (CR ID 200008033). Because of a bug in LTA ASIC, the combination of X-bus distribution being even and P12s signal mapping mode being asynchronous for VC-12 does not work reliably in all situations. SETUP0 checksum calculation and comparing between GMXs does not work reliably in all situations. GMXs fault timestamps may be shown incorrectly (very rarely) in FMS. In case this realizes the timestamp is always circa 497 days too old (=0xFFFFFFFF in 10 ms units) (CR ID 200005139).
10004_22 2008 Tellabs.

189
P12s performance monitoring does not count unavailable time during AIS and LOF signal fail conditions (CR ID 200005178). When MS 1+1 parameters are updated to GMX, the VC-4 timaAisEnabled flag gets the default value (ON) in the protecting interface. This causes DB/HW inconsistency, if the protected interface does have this flag OFF. The flag should be copied from the protected interface to the protecting interface. In the case GMX is protected and lower GMX is the active cross-connection unit, 'TS usage' of VC-12/2 parameters is shown faulty by NMS. Then all cross-connected timeslots are shown with usage 'free' instead of the correct usage information 'In use' (CR ID 200005293). With a small probability, some SDH ASIC register values may become corrupted during GMX switchover (equipment protection switch). With a small probability, handling of LTA ASIC hardware link between GMXs of a node during GMX switchover (equipment protection switch) may not function correctly. With a small probability, a burst of interrupts resulting from GMX switchover (equipment protection switch) may cause fault monitoring inconsistency and/or SDH ASIC register values corruptions. Deleting one or more timeslot connections with CAS will disable all other CAS connections for the corresponding trunk. Recreating at least one timeslot connection with CAS will enable all connections for that trunk again. Performance monitoring thresholds QOSTR lower BBE, lower ES and lower SES (always = 0) are compared faulty. Now QOSTR lower BBE and lower ES are activated when the number of BBE or ES in the 15 minute period is less than (<) the threshold value (should be less or equal (< or =)). SES lower threshold is compared erroneously to the given SES threshold which should act as upper limit only. With this software version, the GMX unit may go to software reset at random times, after which the unit continues to work normally. However, the probability of the reset is low. TTI expected value of SNC/I protected E1VC-12 (VC-12 of SBU) cannot be changed Alarm problems:

13.19 Version 3.11


In the case GMX is protected, the software versions of GMXs must be the same, except during the middle phase of software upgrade process. GMX hardware version must be 1.0 or higher.

190
10004_22 2008 Tellabs.
SCU-H (SCZ545) software version must be 1.3 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1.6 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1.5 or higher. SNC protection works only if SCU-H has SW version 1.3 or higher. MartisDXX Manager support for this unit without SBU functionality is available in Release 10.1A Service Pack 3 or higher. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher.
Restrictions

The control channel in the R0 byte of VC-12 should not be used because of unreliable HW functionality. Supports reconfiguration with reset only (CR ID 200005094). Does not support the use of ESU (CR ID 200005401). GMX generates fault Loss of AU4 pointer if SS-bit values in AU4 pointer differ from 10. This prevents GMX to be connected to SONET equipment. SNC/N protection for GMXs VC-12/2s cannot be used if S-bus (VC-12s of SBU connected to GMXs TU12s) connections are used and vice versa. Cross-connections between E1VC-12s (VC12 of SBU) and GMX's VC-12s are not supported. One timeslot (64 kbit) of GMXBUS1 cannot be allocated. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. 31 VC-12s may have CAS capacity inside one GMXBUS. It means that 62 VC-12s may have CAS capacity. Control channels in the first octet of VC-12 payload are not supported. Tx AIS is not generated in G.704 termination, when X-bus-AIS (=B2-AIS) is detected. In the case of SNC/N protection, signal label values are not copied automatically from the terminating VCs to the monitoring VCs. Dual ended (bidirectional) MS 1+1 is not supported. Control channels in VC-4 POH with MS 1+1 protection are not supported.
Bugs
The fault Reconfiguring X-connect database activates a yellow led instead of a proper red led. Therefore, a switch over during reconfiguration is possible if a fault causing a switch over is activated. This may lead the node to lose cross connections (CR ID 200026983). The quality level value of external clock input in master clock status window is shown as set in parameters even when the actual used quality level may be DNU because of an active problem. This error has no functional effects but may be confusing (CR ID 200011222). In rare occasions, delta event faults may not be transferred to Tellabs 8100 network manager (CR ID 200005197). Purposeless Crc. err LAC RAM 1/2/3/4 alarm can occur sometimes (CR ID 200005197).
10004_22 2008 Tellabs.

191
Performance counting is stopped when TU cross-connection for VC-12/VC-2 is missing (CR ID 200005168). Purposeless reset alarms without a reset can occur rarely (CR ID 200005079). Purposeless power supply alarms may appear in certain rare situations (CR ID 200008442). A burst of bit errors occurs if update is pressed in the Tellabs 8100 network manager interface parameters window of one of the P12s objects of (CR ID 200008033). Because of a bug in LTA ASIC, the combination of X-bus distribution being even and P12s signal mapping mode being asynchronous for VC-12 does not work reliably in all situations. SETUP0 checksum calculation and comparing between GMXs does not work reliably in all situations. GMXs fault timestamps may be shown incorrectly (very rarely) in FMS. In case this realizes the timestamp is always circa 497 days too old (=0xFFFFFFFF in 10 ms units) (CR ID 200005139). P12s performance monitoring does not count unavailable time during AIS and LOF signal fail conditions (CR ID 200005178). When MS 1+1 parameters are updated to GMX, the VC-4 timaAisEnabled flag gets the default value (ON) in the protecting interface. This causes DB/HW inconsistency, if the protected interface does have this flag OFF. The flag should be copied from the protected interface to the protecting interface. In the case GMX is protected and lower GMX is the active cross-connection unit, 'TS usage' of VC-12/2 parameters is shown faulty by NMS. Then all cross-connected timeslots are shown with usage 'free' instead of the correct usage information 'In use' (CR ID 200005293). With a small probability, some SDH ASIC register values may become corrupted during GMX switchover (equipment protection switch). With a small probability, handling of LTA ASIC hardware link between GMXs of a node during GMX switchover (equipment protection switch) may not function correctly. With a small probability, a burst of interrupts resulting from GMX switchover (equipment protection switch) may cause fault monitoring inconsistency and/or SDH ASIC register values corruptions. Deleting one or more timeslot connections with CAS will disable all other CAS connections for the corresponding trunk. Recreating at least one timeslot connection with CAS will enable all connections for that trunk again. Performance monitoring thresholds QOSTR lower BBE, lower ES and lower SES (always = 0) are compared faulty. Now QOSTR lower BBE and lower ES are activated when the number of BBE or ES in the 15 minute period is less than (<) the threshold value (should be less or equal (< or =)). SES lower threshold is compared erroneously to the given SES threshold which should act as upper limit only. With this software version, the GMX unit may go to software reset at random times, after which the unit continues to work normally. However, the probability of the reset is low. Background memory check process may realize with very low probability to a CPU bug that causes uncontrollable reset TTI expected value of SNC/I protected E1VC-12 (VC-12 of SBU) cannot be changed Alarm problems:

192
10004_22 2008 Tellabs.
13.20 Version 3.9

This is an official emergency version almost equal to version 3.8. The only difference is that the bug concerning SNC/N protected vcGtps in versions 3.2 - 3.8 is fixed. This version should not be used once the next official version is available.
10004_22 2008 Tellabs.

193
13.21 Version 3.8

Dependencies

Restrictions

The control channel in the R0 byte of VC-12 should not be used because of unreliable HW functionality. Supports reconfiguration with reset only (CR ID 200005094). Does not support the use of ESU (CR ID 200005401). GMX generates fault Loss of AU4 pointer if SS-bit values in AU4 pointer differ from 10. This prevents GMX to be connected to SONET equipment. SNC/N protection for GMXs VC-12/2s cannot be used if S-bus (VC-12s of SBU connected to GMXs TU12s) connections are used and vice versa. Does not support the enhanced internal state monitoring test features. Cross-connections between E1VC-12s (VC-12 of SBU) and GMX's VC-12s are not supported. One timeslot (64 kbit) of GMXBUS1 cannot be allocated. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. 31 VC-12s may have CAS capacity inside one GMXBUS. It means that 62 VC-12s may have CAS capacity. Control channels in the first octet of VC-12 payload are not supported. Tx AIS is not generated in G.704 termination, when X-bus-AIS (=B2-AIS) is detected. In the case of SNC/N protection, signal label values are not copied automatically from the terminating VCs to the monitoring VCs. Dual ended (bidirectional) MS 1+1 is not supported. Control channels in VC-4 POH with MS 1+1 protection are not supported.

194
10004_22 2008 Tellabs.
Bugs
The fault Reconfiguring X-connect database activates a yellow led instead of a proper red led. Therefore, a switch over during reconfiguration is possible if a fault causing a switch over is activated. This may lead the node to lose cross connections (CR ID 200026983). The quality level value of external clock input in master clock status window is shown as set in parameters even when the actual used quality level may be DNU because of an active problem. This error has no functional effects but may be confusing (CR ID 200011222). In rare occasions, delta event faults may not be transferred to Tellabs 8100 network manager (CR ID 200005197). Purposeless Crc. err LAC RAM 1/2/3/4 alarm can occur sometimes (CR ID 200005197). Performance counting is stopped when TU cross-connection for VC-12/VC-2 is missing (CR ID 200005168). Purposeless reset alarms without a reset can occur rarely (CR ID 200005079). Purposeless power supply alarms may appear in certain rare situations (CR ID 200008442). A burst of bit errors occurs if update is pressed in the Tellabs 8100 network manager interface parameters window of one of the P12s objects of (CR ID 200008033). Because of a bug in LTA ASIC, the combination of X-bus distribution being even and P12s signal mapping mode being asynchronous for VC-12 does not work reliably in all situations. SETUP0 checksum calculation and comparing between GMXs does not work reliably in all situations. GMXs fault timestamps may be shown incorrectly (very rarely) in FMS. In case this realizes the timestamp is always circa 497 days too old (=0xFFFFFFFF in 10 ms units) (CR ID 200005139). P12s performance monitoring does not count unavailable time during AIS and LOF signal fail conditions (CR ID 200005178). When MS 1+1 parameters are updated to GMX, the VC-4 timaAisEnabled flag gets the default value (ON) in the protecting interface. This causes DB/HW inconsistency, if the protected interface does have this flag OFF. The flag should be copied from the protected interface to the protecting interface. In the case GMX is protected and lower GMX is the active cross-connection unit, 'TS usage' of VC-12/2 parameters is shown faulty by NMS. Then all cross-connected timeslots are shown with usage 'free' instead of the correct usage information 'In use' (CR ID 200005293). With a small probability, some SDH ASIC register values may become corrupted during GMX switchover (equipment protection switch). With a small probability, handling of LTA ASIC hardware link between GMXs of a node during GMX switchover (equipment protection switch) may not function correctly. With a small probability, a burst of interrupts resulting from GMX switchover (equipment protection switch) may cause fault monitoring inconsistency and/or SDH ASIC register values corruptions. Deleting one or more timeslot connections with CAS will disable all other CAS connections for the corresponding trunk. Recreating at least one timeslot connection with CAS will enable all connections for that trunk again.
10004_22 2008 Tellabs.

195
Performance monitoring thresholds QOSTR lower BBE, lower ES and lower SES (always = 0) are compared faulty. Now QOSTR lower BBE and lower ES are activated when the number of BBE or ES in the 15 minute period is less than (<) the threshold value (should be less or equal (< or =)). SES lower threshold is compared erroneously to the given SES threshold which should act as upper limit only. With this software version, the GMX unit may go to software reset at random times, after which the unit continues to work normally. However, the probability of the reset is low. Background memory check process may realize with very low probability to a CPU bug that causes uncontrollable reset The test condition of the fault X-Connect Flash List Conflict is wrong. If GMX for any reason ends up in a reconfiguration state there is a small probability that the operation fails. This leads to unnecessary reset of passive GMX unit. Eventually the unit is able to perform reconfiguration. Data through VC-12 circuits may be cut when using SNC/N protected vcGtps. TTI expected value of SNC/I protected E1VC-12 (VC-12 of SBU) cannot be changed Alarm problems:

13.22 Version 3.5

Dependencies

In the case GMX is protected, the software versions of GMXs must be the same, except during the middle phase of software upgrade process. GMX hardware version must be 1.0 or higher. SCU-H (SCZ545) software version must be 1.3 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1.6 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1.5 or higher. SNC protection works only if SCU-H has SW version 1.3 or higher. MartisDXX Manager support for this unit is available in Release 10.1A Service Pack 3 or higher.
Restrictions

The control channel in the R0 byte of VC-12 should not be used because of unreliable HW functionality. Supports reconfiguration with reset only (CR ID 200005094). Does not support the use of ESU (CR ID 200005401).

196
10004_22 2008 Tellabs.
GMX generates fault Loss of AU4 pointer if SS-bit values in AU4 pointer differ from 10. This prevents GMX to be connected to SONET equipment. Does not support the enhanced internal state monitoring test features. One timeslot (64 kbit) of GMXBUS1 cannot be allocated. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. 31 VC-12s may have CAS capacity inside one GMXBUS. It means that 62 VC-12s may have CAS capacity. Control channels in the first octet of VC-12 payload are not supported. Tx AIS is not generated in G.704 termination, when X-bus-AIS (=B2-AIS) is detected. In the case of SNC/N protection, signal label values are not copied automatically from the terminating VCs to the monitoring VCs. Dual ended (bidirectional) MS 1+1 is not supported. Control channels in VC-4 POH with MS 1+1 protection are not supported. SBU and E1Mapper modules (E1M-75 and E1M-120) are not supported.
Bugs
The fault Reconfiguring X-connect database activates a yellow led instead of a proper red led. Therefore, a switch over during reconfiguration is possible if a fault causing a switch over is activated. This may lead the node to lose cross connections (CR ID 200026983). The quality level value of external clock input in master clock status window is shown as set in parameters even when the actual used quality level may be DNU because of an active problem. This error has no functional effects but may be confusing (CR ID 200011222). In rare occasions, delta event faults may not be transferred to Tellabs 8100 network manager (CR ID 200005197). Purposeless Crc. err LAC RAM 1/2/3/4 alarm can occur sometimes (CR ID 200005197). Performance counting is stopped when TU cross-connection for VC-12/VC-2 is missing (CR ID 200005168). Purposeless reset alarms without a reset can occur rarely (CR ID 200005079). Purposeless power supply alarms may appear in certain rare situations (CR ID 200008442). A burst of bit errors occurs if update is pressed in the Tellabs 8100 network manager interface parameters window of one of the P12s objects of (CR ID 200008033). Because of a bug in LTA ASIC, the combination of X-bus distribution being even and P12s signal mapping mode being asynchronous for VC-12 does not work reliably in all situations. SETUP0 checksum calculation and comparing between GMXs does not work reliably in all situations. GMXs fault timestamps may be shown incorrectly (very rarely) in FMS. In case this realizes the timestamp is always circa 497 days too old (=0xFFFFFFFF in 10 ms units) (CR ID 200005139). P12s performance monitoring does not count unavailable time during AIS and LOF signal fail conditions (CR ID 200005178). When MS 1+1 parameters are updated to GMX, the VC-4 timaAisEnabled flag gets the default value (ON) in the protecting interface. This causes DB/HW inconsistency, if the
10004_22 2008 Tellabs.

197
protected interface does have this flag OFF. The flag should be copied from the protected interface to the protecting interface.
In the case GMX is protected and lower GMX is the active cross-connection unit, 'TS usage' of VC-12/2 parameters is shown faulty by NMS. Then all cross-connected timeslots are shown with usage 'free' instead of the correct usage information 'In use' (CR ID 200005293). With a small probability, some SDH ASIC register values may become corrupted during GMX switchover (equipment protection switch). With a small probability, handling of LTA ASIC hardware link between GMXs of a node during GMX switchover (equipment protection switch) may not function correctly. With a small probability, a burst of interrupts resulting from GMX switchover (equipment protection switch) may cause fault monitoring inconsistency and/or SDH ASIC register values corruptions. Deleting one or more timeslot connections with CAS will disable all other CAS connections for the corresponding trunk. Recreating at least one timeslot connection with CAS will enable all connections for that trunk again. Performance monitoring thresholds QOSTR lower BBE, lower ES and lower SES (always = 0) are compared faulty. Now QOSTR lower BBE and lower ES are activated when the number of BBE or ES in the 15 minute period is less than (<) the threshold value (should be less or equal (< or =)). SES lower threshold is compared erroneously to the given SES threshold which should act as upper limit only. With this software version, the GMX unit may go to software reset at random times, after which the unit continues to work normally. However, the probability of the reset is low. Background memory check process may realize with very low probability to a CPU bug that causes uncontrollable reset The test condition of the fault X-Connect Flash List Conflict is wrong. If GMX for any reason ends up in a reconfiguration state there is a small probability that the operation fails. This leads to unnecessary reset of passive GMX unit. Eventually the unit is able to perform reconfiguration. Data through VC-12 circuits may be cut when using SNC/N protected vcGtps. Remote case of trunk swap (trunks from separate X-buses) may cause bit errors within the corresponding circuits during the first 2 minutes. Alarm problems:

There is an SNC protection bug in the interface 2 when the lower GMX is active: if optical interface module is placed to the lower GMX, after reset the SNC protection logic cannot use the lower interface. Trunk swap does not work between VC-12s of the GMX when the VC-12s are allocated from the same X-bus (local swap). Extended links of SCU-H (IP links 3-16 and HDLC links 1-16) do not work.

198
10004_22 2008 Tellabs.
13.23 Version 3.2

Dependencies

In the case GMX is protected, the software versions of GMXs must be the same, except during the middle phase of software upgrade process. GMX hardware version must be 1.0 or higher. SCU-H (SCZ545) software version must be 1.3 or higher. SNC protection works only if SCU-H has SW version 1.3 or higher. MartisDXX Manager support for this unit is available in Release 10.1A Service Pack 3 or higher.
Restrictions

The control channel in the R0 byte of VC-12 should not be used because of unreliable HW functionality. Supports reconfiguration with reset only (CR ID 200005094). Does not support the use of ESU (CR ID 200005401). GMX generates fault Loss of AU4 pointer if SS-bit values in AU4 pointer differ from 10. This prevents GMX to be connected to SONET equipment. Does not support the enhanced internal state monitoring test features. One timeslot (64 kbit) of GMXBUS1 cannot be allocated. It means that the last VC-12s of GMXBUS 1 has to be locked using long X-bus buffer. 31 VC-12s may have CAS capacity inside one GMXBUS. It means that 62 VC-12s may have CAS capacity. Control channels in the first octet of VC-12 payload are not supported. Tx AIS is not generated in G.704 termination, when X-bus-AIS (=B2-AIS) is detected. In the case of SNC/N protection, signal label values are not copied automatically from the terminating VCs to the monitoring VCs. Dual ended (bidirectional) MS 1+1 is not supported. Control channels in VC-4 POH with MS 1+1 protection are not supported. FMS system is incomplete in the case of MS 1+1 protection and SNC/N protection. See MartisDXX Manager R10.1A-3 Installation and Release Notes. In the case of SNC/N, the Protection Criteria attribute of an SNC protection group cannot be set to active. So TIM alarm will not trigger SNC/N protection switch (which it would do if the Protection Criteria attribute were used and the attribute worked). In the case GMX is not protected the node works slowly via Tellabs 8100 network manager. Passivation or activation of a swapped trunk is not restricted by USW though it should be (this is a forbidden operation by definition). Changing CAS on/off for a swapped port is not restricted by USW though it should be (this is a forbidden operation because swapped ports have to be equal).
10004_22 2008 Tellabs.

199
Flash operations are relatively slow (approximately 10 times faster in version 3.5). SBU and E1Mapper modules (E1M-75 and E1M-120) are not supported.
Bugs
The fault Reconfiguring X-connect database activates a yellow led instead of a proper red led. Therefore, a switch over during reconfiguration is possible if a fault causing a switch over is activated. This may lead the node to lose cross connections (CR ID 200026983). The quality level value of external clock input in master clock status window is shown as set in parameters even when the actual used quality level may be DNU because of an active problem. This error has no functional effects but may be confusing (CR ID 200011222). In rare occasions, delta event faults may not be transferred to Tellabs 8100 network manager (CR ID 200005197). Purposeless Crc. err LAC RAM 1/2/3/4 alarm can occur sometimes (CR ID 200005197). Performance counting is stopped when TU cross-connection for VC-12/VC-2 is missing (CR ID 200005168). Purposeless reset alarms without a reset can occur rarely (CR ID 200005079). Purposeless power supply alarms may appear in certain rare situations (CR ID 200008442). A burst of bit errors occurs if update is pressed in the Tellabs 8100 network manager interface parameters window of one of the P12s objects of (CR ID 200008033). Because of a bug in LTA ASIC, the combination of X-bus distribution being even and P12s signal mapping mode being asynchronous for VC-12 does not work reliably in all situations. SETUP0 checksum calculation and comparing between GMXs does not work reliably in all situations. GMXs fault timestamps may be shown incorrectly (very rarely) in FMS. In case this realizes the timestamp is always circa 497 days too old (=0xFFFFFFFF in 10 ms units) (CR ID 200005139). P12s performance monitoring does not count unavailable time during AIS and LOF signal fail conditions (CR ID 200005178). When MS 1+1 parameters are updated to GMX, the VC-4 timaAisEnabled flag gets the default value (ON) in the protecting interface. This causes DB/HW inconsistency, if the protected interface does have this flag OFF. The flag should be copied from the protected interface to the protecting interface. In the case GMX is protected and lower GMX is the active cross-connection unit, 'TS usage' of VC-12/2 parameters is shown faulty by NMS. Then all cross-connected timeslots are shown with usage 'free' instead of the correct usage information 'In use' (CR ID 200005293). With a small probability, some SDH ASIC register values may become corrupted during GMX switchover (equipment protection switch). With a small probability, handling of LTA ASIC hardware link between GMXs of a node during GMX switchover (equipment protection switch) may not function correctly. With a small probability, a burst of interrupts resulting from GMX switchover (equipment protection switch) may cause fault monitoring inconsistency and/or SDH ASIC register values corruptions.

200
10004_22 2008 Tellabs.
Deleting one or more timeslot connections with CAS will disable all other CAS connections for the corresponding trunk. Recreating at least one timeslot connection with CAS will enable all connections for that trunk again. Performance monitoring thresholds QOSTR lower BBE, lower ES and lower SES (always = 0) are compared faulty. Now QOSTR lower BBE and lower ES are activated when the number of BBE or ES in the 15 minute period is less than (<) the threshold value (should be less or equal (< or =)). SES lower threshold is compared erroneously to the given SES threshold which should act as upper limit only. With this software version, the GMX unit may go to software reset at random times, after which the unit continues to work normally. However, the probability of the reset is low. Background memory check process may realize with very low probability to a CPU bug that causes uncontrollable reset The test condition of the fault X-Connect Flash List Conflict is wrong. If GMX for any reason ends up in a reconfiguration state there is a small probability that the operation fails. This leads to unnecessary reset of passive GMX unit. Eventually the unit is able to perform reconfiguration. Data through VC-12 circuits may be cut when using SNC/N protected vcGtps. Alarm problems:

The Phase locked loop and 20 MHz node clock missing alarms are active for a while after GMX reset. VC-4 fault filtering does not work if MS 1+1 protection is activated and protection switch uses the interface of the passive GMX. PLL alarm does not work in the case of clock loop. If control channel is located in SOH or VC4-POH bytes, the HDLC/X-bus in same TS alarm may be active without reason. If the Performance Source attribute has value P12s or VC12 and P12s, P12 performance alarms (UNAVAIL, QOS and QOSTR) may stay active even if P12 is in transparent mode. P12 alarms do not work after GMX reset. If P12 attribute values are updated after reset, P12 alarms are working correctly. The functional state of the portmode attribute is always Monitored after reset.
The expected TI, CAS, signal degrade seconds, signal degrade threshold and TIMaAisenabled attributes cannot be changed in concatenation if SNC/I protection is used. Trunk swap does not work between VC-12s of the GMX. Trunk swap in the remote case (trunks from separate X-buses) does not work. Flash checksum calculation works unreliably. Reset of the passive GMX affects to the synchronization sources of the active GMX. Received trail trace of interface 2 is not masked to NULL in RS and VC-4 layers when the TSF signal has been received. Extended links of SCU-H (IP links 3-16 and HDLC links 1-16) do not work.
10004_22 2008 Tellabs.

201
GMX2 Unit: GMZ802 Unit Software
14 GMX2 Unit: GMZ802 Unit Software

The software GMZ802 is used on GMX2 unit (whose base unit is GMX811) in Tellabs 8184 access switch and Tellabs 8188 access switch.
14.1 Version 1.21


VC-12 CAS AIS insertion into Rx signal does not work properly (CR ID 300110017). The synchronization connection initialization specific to GMU-A or GMU has been fixed (CR ID 300109943).
Dependencies

GMX2 unit hardware version must be 1.0 or higher. If SCU-H (SCZ545) software version is 1.x then version must be 1.18 or higher. If SCU-H (SCZ545) software version is 2.x then version must be 2.6 or higher. Tellabs 8000 network manager support for this unit is available in Release 16A SP2 or higher.
Restrictions
No restrictions.
Bugs
No known bugs
14.2 Version 1.20


Improved 1/0-protection switching during equipment protection. Minimal data interruption during change of the active unit. (CR ID 300095583). Flash memory access updated.

202
10004_22 2008 Tellabs.
Dependencies

Restrictions
No restrictions.
Bugs
The synchronization connection initialization specific to GMU-A or GMU is not valid. This error may cause unexpected random faults in the node.
14.3 Version 1.18

STM-4 IF output jitter is not according to the G.813 specification. (CR ID 300097924).
Dependencies

Restrictions
No restrictions.
Bugs
The synchronization connection initialization specific to GMU-A or GMU is not valid. This error may cause unexpected random faults in the node.
10004_22 2008 Tellabs.

203
14.4 Version 1.16

CAS does not work reliably (CR ID 300095743).
Dependencies

Restrictions
No restrictions.
Bugs

STM-4 IF output jitter is not according to the G.813 specification. (CR ID 300097924). The synchronization connection initialization specific to GMU-A or GMU is not valid. This error may cause unexpected random faults in the node
14.5 Version 1.15

Compatible with Tellabs 8000 network manager Release 16A SP2 or higher.
Dependencies

Restrictions
No restrictions.

204
10004_22 2008 Tellabs.
Bugs

STM-4 IF output jitter is not according to the G.813 specification. (CR ID 300097924). CAS does not work reliably. The synchronization connection initialization specific to GMU-A or GMU is not valid. This error may cause unexpected random faults in the node
14.6 Version 1.12


Channel Associated Signalling (CAS) is supported. VC-12 R-byte cross-connection is supported.
Dependencies

GMX2 unit hardware version must be 1.0 or higher. If SCU-H (SCZ545) software version is 1.x then version must be 1.18 or higher. If SCU-H (SCZ545) software version is 2.x then version must be 2.6 or higher. Tellabs 8000 network manager support for this unit is available in Release 16A SP1.
Restrictions

This version can be used only with Tellabs 8000 network manager Release 16A SP1. SNC/N is not supported by Tellabs 8000 network manager Release 16A SP1. This version is not recommended to be used in live networks.
Bugs

STM-4 IF output jitter is not according to the G.813 specification. (CR ID 300097924). CAS does not work reliably. Traffic is not recovered reliably after cable cuts.
10004_22 2008 Tellabs.

205
14.7 Version 1.0

Dependencies

GMX2 unit hardware version must be 1.0 or higher. If SCU-H (SCZ545) software version is 1.x then version must be 1.18 or higher. If SCU-H (SCZ545) software version is 2.x then version must be 2.6 or higher. Tellabs 8000 network manager support for this unit is available in Release 16A SP1.
Restrictions

Channel Associated Signalling (CAS) is not supported. VC-12 R-byte cross-connection is not supported. This version can be used only with Tellabs 8000 network manager Release 16A SP1. SNC/N is not supported by Tellabs 8000 network manager Release 16A SP1. This version is not recommended to be used in live networks.
Bugs

STM-4 IF output jitter is not according to the G.813 specification. (CR ID 300097924). Traffic is not recovered reliably after cable cuts.

206
10004_22 2008 Tellabs.
LAN Module: EHZ541 Unit Software
15 LAN Module: EHZ541 Unit Software

The software EHZ541 is used on a LAN Module. The version 1.2 can be downloaded to LAN Modules having the version 1.y of EHZ541 (where y=0, 1, 2...).
15.1 Version 1.2

Dependencies

STU-1088/2048 (SBZ384) baseband modem support for IP filtering is available in version 1.4. STU-160 (SBZ385) DSL Network Terminating Unit support for IP filtering is available in version 1.5. STU-320, STU-576, STU-1088-2W and STU-2304 (SBZ387) SDSL Network Terminating Unit support for IP filtering is available in version 1.0. HTU-2M (SBZ389) HDSL Network Terminating Units support for IP filtering is available in version 1.0. VCM-5T-A/VCM-10T-A (VCZ285A) interface unit support for LAN Module is available in version 10.1. Mini Node SBM 2048M (SMZ414) support for LAN Module is available in version 5.0. MartisDXX Manager support for IP filtering is available in Release 10.0A SP2.
Restrictions
The address table expiration timer is configurable in 4 minute intervals from 8 minutes up to 252. The user interface may allow the setting of this value also to 0 or 4 (corrected at MartisDXX Manager R11SP3), but in this case the unit software will internally use 8 minutes as the parameter value. This restriction is related to correction of traffic cut problem.
Bugs
No known bugs.
10004_22 2008 Tellabs.

207
15.2 Version 1.1

Dependencies

STU-1088/2048 (SBZ384) baseband modem support for IP filtering is available in version 1.4. STU-160 (SBZ385) DSL Network Terminating Unit support for IP filtering is available in version 1.5. STU-320, STU-576, STU-1088-2W and STU-2304 (SBZ387) SDSL Network Terminating Unit support for IP filtering is available in version 1.0. HTU-2M (SBZ389) HDSL Network Terminating Unit support for IP filtering is available in version 1.0. VCM-5T-A/VCM-10T-A (VCZ285A) interface unit support for LAN Module is available in version 10.1. Mini Node SBM 2048M (SMZ414) support for LAN Module is available in version 5.0. MartisDXX Manager support for IP filtering is available in Release 10.0A SP2.
Restrictions
No restrictions.
Bugs
LAN Module cuts traffic in "heavy traffic" load. This can be solved by setting the address table expiration time to 16 minutes, which works in most cases.

208
10004_22 2008 Tellabs.
15.3 Version 1.0

Dependencies

STU-1088/2048 (SBZ384) baseband modem support for LAN Module is available in version 1.3. STU-160 (SBZ385) DSL Network Terminating Unit support for LAN Module is available in version 1.3. STU-320, STU-576, STU-1088-2W and STU-2304 (SBZ387) SDSL Network Terminating Unit support for LAN Module is available in version 1.0. HTU-2M (SBZ389) HDSL Network Terminating Unit support for LAN Module is available in version 1.0. VCM-5T-A/VCM-10T-A (VCZ285A) interface unit support for LAN Module is available in version 10.1. Mini Node SBM 2048M (SMZ414) support for LAN Module is available in version 5.0. MartisDXX Manager support for LAN Module is available in Release 9.0B.
Restrictions
No restrictions.
Bugs
LAN Module cuts traffic in "heavy traffic" load. This can be solved by setting the address table expiration time to 16 minutes, which works in most cases.
10004_22 2008 Tellabs.

209
OMH/OMH-A Unit: OMZ675 Unit Software
16 OMH/OMH-A Unit: OMZ675 Unit Software

The software OMZ675 is used on OMH and OMH-A units (whose base unit is OMH771) in the Tellabs 8140 midi, Tellabs 8150 basic, Tellabs 8160 A111 and Tellabs 8170 cluster nodes as well as in Tellabs 8184 and Tellabs 8188 access switches. The version 3.3 can be downloaded to OMH units having the version 1.y, 2.y or 3.y of OMZ675 (where y=0, 1, 2...). The OMH-A unit is a version of OMH771 base unit (version 3.0 or higher), which is capable of 12.3 Mbit/s data rate, and it is also referred to as the OMH-A unit in Tellabs 8000 manager starting from Release 15A. The OMH unit can be replaced with the OMH-A unit without removing the services attached. In this case, unit type must be changed to the new OMH-A type with Node Editor in Tellabs 8000 manager. Once the OMH unit type is changed to the OMH-A unit type, it is not anymore possible to change back to the OMH unit type without removing all the services attached.
16.1 Version 3.3

HCO synchronization problem with NTU using bit rate 72x64kbps is fixed (CR ID 300091819 and CR ID 300108076).
Dependencies

OMH (base unit OMH771) hardware version must be 3.0 or higher (OMH-A) to support the 4 x 3088 kbit/s operation mode. SCO interface module version (which is based on SCO SW DPZ652 version) must be 3.0 or higher to support 4-pair modes, and 3.1 or higher to support 3088 kbit/s line rates with Tellabs 8110 STE-10M NTU. SCO interface module version must be 4.0 or higher to support 208 kbit/s line rates. CCU (SCZ286) software can be any version. SCP (SCZ281) software version must be 3.1 or higher to support extra backups for other units in the node. SCU (SCZ280) software version must be 8.4 or higher to support extra backups for other units in the node. SCU-H (SCZ545) software version must be 1.6 or higher to support unlocking the ports without failures. XCG (SMZ538) software version must be 2.0 or higher to support extra backups for other units in the node, and 3.5 or higher to fully support over 8M cross-connection ports. XCG software version 3.4 supports max 139 timeslots cross-connections with over 8M cross-connection ports.

210
10004_22 2008 Tellabs.
GMX (GMZ544) software version must be 3.19, or 4.2 or higher to fully support over 8M cross-connection ports. GMX software versions 3.17 and 3.18 support max 139 timeslots cross-connections with over 8M cross-connection ports. GMX2 (GMZ802) software version can be any version. SXU-A/B (SXZ282) software version must be 10.5 or higher to fully support over 8M cross-connection ports. SXU-A/B software versions 10.3 and 10.4 support max 139 timeslots cross-connections with over 8M cross-connection ports. SXU-V (SXZ630) software can be any version. Over 8M cross-connection ports are not supported. Tellabs 8170 cluster node softwares CXU-M (SXZ288) and SXU-C (SXZ289) can be any version. Over 8M cross-connection ports are not supported. Tellabs 8100 manager support for this unit is available in Release 13. Support for 3088 kbit/s line rates and 4-pair modes with Tellabs 8110 STE-10M NTU is available in Release 14-SP3. Support for 208 kbit/s line rates is available in Tellabs 8000 manager Release 15A. The OMH unit, which is capable of 12.3 Mbit/s data rate, is referred to as the OMH-A unit in Release 15A.
Restrictions

The Line Loop (LiL) is not supported in case of HCO or SCO interfaces connected to any NTU. The Neighbour Node Loop (NNL, activation requested from neighbour NTU) and the Remote Line Loop (RLL, activation requested from neighbour unit) are not supported in case of HCO interface module in interfaces 2, 4, 6 and 8.
16.2 Version 3.2


OMH-A SCO frame synchronization handling improved when 2-pair line mode is used (CR ID 300092758). Baseband statistics corrected when line is in 1x3M, 2x3M or 4x3M mode (CR ID 300093143). Note: because of this fix line statistics may show different values in OMH side than in NTU. Values seen from OMH side are more reliable.
Dependencies

OMH (base unit OMH771) hardware version must be 3.0 or higher (OMH-A) to support the 4 x 3088 kbit/s operation mode. SCO interface module version (which is based on SCO SW DPZ652 version) must be 3.0 or higher to support 4-pair modes, and 3.1 or higher to support 3088 kbit/s line rates with Tellabs 8110 STE-10M NTU. SCO interface module version must be 4.0 or higher to support 208 kbit/s line rates. CCU (SCZ286) software can be any version.
10004_22 2008 Tellabs.

211
SCP (SCZ281) software version must be 3.1 or higher to support extra backups for other units in the node. SCU (SCZ280) software version must be 8.4 or higher to support extra backups for other units in the node. SCU-H (SCZ545) software version must be 1.6 or higher to support unlocking the ports without failures. XCG (SMZ538) software version must be 2.0 or higher to support extra backups for other units in the node, and 3.5 or higher to fully support over 8M cross-connection ports. XCG software version 3.4 supports max 139 timeslots cross-connections with over 8M cross-connection ports. GMX (GMZ544) software version must be 3.19, or 4.2 or higher to fully support over 8M cross-connection ports. GMX software versions 3.17 and 3.18 support max 139 timeslots cross-connections with over 8M cross-connection ports. GMX2 (GMZ802) software version can be any version. SXU-A/B (SXZ282) software version must be 10.5 or higher to fully support over 8M cross-connection ports. SXU-A/B software versions 10.3 and 10.4 support max 139 timeslots cross-connections with over 8M cross-connection ports. SXU-V (SXZ630) software can be any version. Over 8M cross-connection ports are not supported. Tellabs 8170 cluster node softwares CXU-M (SXZ288) and SXU-C (SXZ289) can be any version. Over 8M cross-connection ports are not supported. Tellabs 8100 manager support for this unit is available in Release 13. Support for 3088 kbit/s line rates and 4-pair modes with Tellabs 8110 STE-10M NTU is available in Release 14-SP3. Support for 208 kbit/s line rates is available in Tellabs 8000 manager Release 15A. The OMH unit, which is capable of 12.3 Mbit/s data rate, is referred to as the OMH-A unit in Release 15A.
Restrictions

OMH-A with HCO module cannot use bit rate 72x64kbps (CR ID 300091819 and CR ID 300108076). The Line Loop (LiL) is not supported in case of HCO or SCO interfaces connected to any NTU. The Neighbour Node Loop (NNL, activation requested from neighbour NTU) and the Remote Line Loop (RLL, activation requested from neighbour unit) are not supported in case of HCO interface module in interfaces 2, 4, 6 and 8.
16.3 Version 3.1

This is a non-production version based on version 3.0.

212
10004_22 2008 Tellabs.
16.4 Version 3.0

Enhancements (compared with version 2.0)
OMH-A hardware (version 3.0 or higher) and SCO interface module support 3088 kbit/s line rate in 4-pair mode. A top data rate of 12.3 Mbit/s can be reached by using the 4 x 3088 kbit/s operation mode together with Tellabs 8110 STE-10M NTU (CR ID 300048238). New SCO interface module version 4.0 supports 208 kbit/s line rates in 1 and 2-pair modes.
Dependencies

OMH (base unit OMH771) hardware version must be 3.0 or higher (OMH-A) to support the 4 x 3088 kbit/s operation mode. SCO interface module version (which is based on SCO SW DPZ652 version) must be 3.0 or higher to support 4-pair modes, and 3.1 or higher to support 3088 kbit/s line rates with Tellabs 8110 STE-10M NTU. SCO interface module version must be 4.0 or higher to support 208 kbit/s line rates. CCU (SCZ286) software can be any version. SCP (SCZ281) software version must be 3.1 or higher to support extra backups for other units in the node. SCU (SCZ280) software version must be 8.4 or higher to support extra backups for other units in the node. SCU-H (SCZ545) software version must be 1.6 or higher to support unlocking the ports without failures. XCG (SMZ538) software version must be 2.0 or higher to support extra backups for other units in the node, and 3.5 or higher to fully support over 8M cross-connection ports. XCG software version 3.4 supports max 139 timeslots cross-connections with over 8M cross-connection ports. GMX (GMZ544) software version must be 3.19, or 4.2 or higher to fully support over 8M cross-connection ports. GMX software versions 3.17 and 3.18 support max 139 timeslots cross-connections with over 8M cross-connection ports. SXU-A/B (SXZ282) software version must be 10.5 or higher to fully support over 8M cross-connection ports. SXU-A/B software versions 10.3 and 10.4 support max 139 timeslots cross-connections with over 8M cross-connection ports. SXU-V (SXZ630) software can be any version. Over 8M cross-connection ports are not supported. Tellabs 8170 cluster node softwares CXU-M (SXZ288) and SXU-C (SXZ289) can be any version. Over 8M cross-connection ports are not supported. Tellabs 8100 manager support for this unit is available in Release 13. Support for 3088 kbit/s line rates and 4-pair modes with Tellabs 8110 STE-10M NTU is available in Release 14-SP3. Support for 208 kbit/s line rates is available in Tellabs 8000 manager Release 15A. The OMH unit, which is capable of 12.3 Mbit/s data rate, is referred to as the OMH-A unit in Release 15A.
10004_22 2008 Tellabs.

213
Restrictions

16.5 Version 2.0

Enhancements (compared with version 1.2)
OMH unit with new SCO interface module supports new Tellabs 8110 STE-10M network terminating unit. SCO supports 592, 1168, 2064, 2320 and 3088 kbit/s line rates in 1- and 2-pair modes, and 592, 1168, 2064 and 2320 kbit/s line rates in 4-pair mode. A top data rate of 9.2 Mbit/s can be reached by using the 4 x 2320 kbit/s operation mode together with Tellabs 8110 STE-10M NTU. "Ntu power off" interface fault masks "Rx signal missing" fault. In addition, "Ntu power off" fault service status is changed to be "Service affecting fault" (S).
Dependencies

OMH (base unit OMH771) hardware version must be 1.0 or 2.0. SCO interface module version (which is based on SCO SW DPZ652 version) must be 3.0 or higher to support 4-pair modes, and 3.1 or higher to support 3088 kbit/s line rates with Tellabs 8110 STE-10M NTU. CCU (SCZ286) software can be any version. SCP (SCZ281) software version must be 3.1 or higher to support extra backups for other units in the node. SCU (SCZ280) software version must be 8.4 or higher to support extra backups for other units in the node. SCU-H (SCZ545) software version must be 1.6 or higher to support unlocking the ports without failures. XCG (SMZ538) software version must be 2.0 or higher to support extra backups for other units in the node, and 3.5 or higher to fully support over 8M cross-connection ports. XCG software version 3.4 supports max 139 timeslots cross-connections with over 8M cross-connection ports. GMX (GMZ544) software version must be 3.19, or 4.2 or higher to fully support over 8M cross-connection ports. GMX software versions 3.17 and 3.18 support max 139 timeslots cross-connections with over 8M cross-connection ports. SXU-A/B (SXZ282) software version must be 10.5 or higher to fully support over 8M cross-connection ports. SXU-A/B software versions 10.3 and 10.4 support max 139 timeslots cross-connections with over 8M cross-connection ports. SXU-V (SXZ630) software can be any version. Over 8M cross-connection ports are not supported.

214
10004_22 2008 Tellabs.
Tellabs 8170 cluster node softwares CXU-M (SXZ288) and SXU-C (SXZ289) can be any version. Over 8M cross-connection ports are not supported. Tellabs 8100 manager support for this unit is available in Release 13. Support for 3088 kbit/s line rates and 4-pair modes with Tellabs 8110 STE-10M NTU is available in Release 14-SP3.
Restrictions

Cross-connections to timeslot 144 and above that are not supported. The Line Loop (LiL) is not supported in case of HCO or SCO interfaces connected to any NTU. The Neighbour Node Loop (NNL, activation requested from neighbour NTU) and the Remote Line Loop (RLL, activation requested from neighbour unit) are not supported in case of HCO interface module in interfaces 2, 4, 6 and 8.
16.6 Version 1.2

Dependencies

OMH (base unit OMH771) hardware version must be 1.0 or 2.0. CCU (SCZ286) software can be any version. SCP (SCZ281) software version must be 3.1 or higher to support extra backups for other units in the node. SCU (SCZ280) software version must be 8.4 or higher to support extra backups for other units in the node. SCU-H (SCZ545) software version must be 1.6 or higher to support unlocking the ports without failures. XCG (SMZ538) software version must be 2.0 or higher to support extra backups for other units in the node. CXU-M (SXZ288) software can be any version. GMX (GMZ544) software can be any version. SXU-A/B (SXZ282) software can be any version. SXU-C (SXZ289) software can be any version. SXU-V (SXZ630) software can be any version. Tellabs 8100 manager support for this unit is available in Release 13.
Restrictions

10004_22 2008 Tellabs.

215
QMH and QMH-M Units: QMZ540 Unit Software
17 QMH and QMH-M Units: QMZ540 Unit Software

The software QMZ540 is used on the QMH unit (whose base unit is QMH509) (1.x and 10.x software versions) or the QMH-M unit (whose base unit is QMH740) (6.x software versions) in Tellabs 8140 midi, Tellabs 8150 basic, Tellabs 8160 A111 and Tellabs 8170 cluster nodes as well as in Tellabs 8184 and Tellabs 8188 access switches. The version 1.x can be downloaded to QMH units having the version 1.x PROMs of QMZ540. The version 6.x can be downloaded to QMH-M units having the version 6.x PROMs of QMZ540. The version 10.11 can be downloaded to QMH units having the version 10.x PROMs of QMZ540 (where x=0, 1, 2...).
17.1 Version 10.11

The reason for this release is fixes in 1+1 protection functionality. In this software version 1+1 protection switch is working correctly when an interface is in 2M unframed mode (CR ID 300089699 and CR ID 300089844).
Dependencies

QMH (base unit QMH509) hardware version must be 3.0 or higher. CCU (SCZ286) software version can be any version. SCU (SCZ280) software version can be any version. SCP (SCZ281) software version can be any version. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMH (GMZ283) software version can be any version. GMX (GMZ544) software version can be any version. GMX2 (GMZ802) software version can be any version. CXU-M (SXZ288) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. Tellabs 8100 manager supports the enhanced interface fault masking in Release 13 or higher. MartisDXX Manager support for the pilot bit and ring protection are available in Release 12 or higher.

216
10004_22 2008 Tellabs.
Restrictions
This software version does not support QMH-M (QMH740) unit.
Bugs
A replacement unit shows a wrong fault status, PMA, in 1+1 protected trunk mode if a protecting trunk fails.
17.2 Version 10.10

The reason for this release is changes in fault handling (CR ID 300023242). In this software version Ntu power fault interface fault masks the Loss of input signal fault. Thus NTU power off will cause just Ntu power fault fault. In addition, the Ntu power off fault service status is changed to a Service affecting fault (S).
Dependencies

QMH (base unit QMH509) hardware version must be 3.0 or higher. CCU (SCZ286) software version can be any version. SCU (SCZ280) software version can be any version. SCP (SCZ281) software version can be any version. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMH (GMZ283) software version can be any version. GMX (GMZ544) software version can be any version. GMX2 (GMZ802) software version can be any version. CXU-M (SXZ288) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. Tellabs 8100 manager supports the enhanced interface fault masking in Release 13 or higher. MartisDXX Manager support for the pilot bit and ring protection are available in Release 12 or higher.
Restrictions
10004_22 2008 Tellabs.

217
Bugs

A replacement unit shows a wrong fault status, PMA, in 1+1 protected trunk mode if a protecting trunk fails. 1+1 protection switch does not work reliably if an interface is configured in 2M unframed mode. (CR ID 300089699)
17.3 Version 10.9

This version is based on a test version 10.91. Enhancements and Fixed Bugs
Changing interface module type allowed while unit is out of inventory. (CR ID 200012191)
Dependencies

QMH (base unit QMH509) hardware version must be 3.0 or higher. CCU (SCZ286) software version can be any version. SCU (SCZ280) software version can be any version. SCP (SCZ281) software version can be any version. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMH (GMZ283) software version can be any version. GMX (GMZ544) software version can be any version. CXU-M (SXZ288) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. Tellabs 8100 manager supports the enhanced interface fault masking in Release 13 or higher. MartisDXX Manager support for the pilot bit and ring protection are available in Release 12 or higher.
Restrictions

218
10004_22 2008 Tellabs.
Bugs

17.4 Version 10.8

This version is based on a test version 10.111. Enhancements and Fixed Bugs

Robustness of internal node communication has been improved. (CR ID 200009698) Reliability of restoring backups in a boot phase has been improved. (CR ID 200010516)
Dependencies

Restrictions
10004_22 2008 Tellabs.

219
Bugs

17.5 Version 10.7

Enhancement for production testing. (CR ID 200005560)
Dependencies

Restrictions
Bugs


220
10004_22 2008 Tellabs.
17.6 Version 10.6

This is a non-production version and this should not be used when the next official version is available. Enhancements and Fixed Bugs

HCQ errors are directed to specific interface, not to the specific line number. (CRF ID 4004099) Clock status DNU is sent via NNM if a unit can not get locked to a node clock. (CRF ID 4004149) Line loop bug with pilot bit fixed (CRF ID 4004404) Operational testing improvement (CRF ID 4004416) Clock QL state is forced to DNU if NNM is down. (CRF ID 4004440) AIS fault is restrained with equipment loop when pilot bit is set (CRF ID 4004569) HDLC timeout value fixed (CRF ID 4004719) Synchronization source problem with QMH/HCQ 72x64kbit/s fixed (CRF ID 4005023) Interface fault mask can have following options: monitored, not monitored and fault mask on. (CRF ID 4004922).
Dependencies

QMH (base unit QMH509) hardware version must be 3.0 or higher. CCU (SCZ286) software version can be any version. SCU (SCZ280) software version can be any version. SCP (SCZ281) software version can be any version. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMH (GMZ283) software version can be any version. GMX (GMZ544) software version can be any version. CXU-M (SXZ288) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. Tellabs 8100 Manager supports the enhanced interface fault masking in Release 13 or higher. MartisDXX Manager support for the pilot bit and ring protection are available in Release 12 or higher.
10004_22 2008 Tellabs.

221
Restrictions
Bugs

17.7 Version 10.5

Enhancements

This software version supports freely allocated pilot bit. This software version supports HCQ (HCQ739) module. NMS can now disable download QMH software. (CRF ID 4003834)
Dependencies

QMH (base unit QMH509) hardware version must be 3.0 or higher. CCU (SCZ286) software version can be any version. SCU (SCZ280) software version can be any version. SCP (SCZ281) software version can be any version. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMH (GMZ283) software version can be any version. GMX (GMZ544) software version can be any version. CXU-M (SXZ288) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for the pilot bit and ring protection are available in Release 12 or higher.
Restrictions
Bugs
Clock status sending in QMH doesnt work when SXU fails. (CRF ID 4004149

222
10004_22 2008 Tellabs.
1+1 protection switch does not work reliably if an interface is configured in 2M unframed mode. (CR ID 300089699))
17.8 Version 10.3

Enhancements

This software version is an update for the QMH509 v3.0 Hardware (e.g. QDX Asic). This software version supports the ring protection mode.
Dependencies

QMH (base unit QMH509) hardware version must be 3.0 or higher. CCU (SCZ286) software version can be any version. SCU (SCZ280) software version can be any version. SCP (SCZ281) software version can be any version. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMH (GMZ283) software version can be any version. GMX (GMZ544) software version can be any version. CXU-M (SXZ288) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. MartisDXX Manager support for the QMH unit is available in Release 11 Service Pack 1 or higher.
Restrictions

This software version does not support QMH-M (QMH740) unit. This software version does not support HCQ (HCQ739) module. This software version does not support SXU-V (SXU758) unit. This software version does not support freely allocated pilot bit.
Bugs
When creating a G.821 Report for 1+1 protected trunks in Performance Management System, available time (AT) is always 100% even if both trunks have been simultaneously cut. (CRF ID 4003959) Clock status sending in QMH doesnt work when SXU fails. (CRF ID 4004149) 1+1 protection switch does not work reliably if an interface is configured in 2M unframed mode. (CR ID 300089699)
10004_22 2008 Tellabs.

223
17.9 Version 6.0

Dependencies

QMH-M (QMH740) hardware version must be 1.0. CCU (SCZ286) software version can be any version. SCU (SCZ280) software version can be any version. SCP (SCZ281) software version can be any version. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMH (GMZ283) software version can be any version. GMX (GMZ544) software version can be any version. CXU-M (SXZ288) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for the QMH unit is available in Release 11 Service Pack 1 or higher.
Restrictions

This software version does not support HCQ (HCQ739) module. This software version does not support BTQ-1088 and BTQ-2304 modules. This software version does not support framed mode. This software version does not support QMH unit. QMH-M does not support SXU-V in V5.2 use
Bugs
No known bugs.

224
10004_22 2008 Tellabs.
17.10 Version 1.6

This is a version based on QMZ540 version 1.5 with features from QMZ540 version 10.6. Enhancements and Fixed Bugs

Clock status DNU is sent via NNM if a unit can not get locked to a node clock. (CRF ID 4004149) Line loop bug with pilot bit fixed (CRF ID 4004404) Clock QL state is forced to DNU if NNM is down. (CRF ID 4004440) AIS fault is restrained with equipment loop when pilot bit is set (CRF ID 4004569)
Dependencies

QMH (QMH509) hardware (1.x or 2.x) must be used. CCU (SCZ286) software version can be any version. SCU (SCZ280) software version can be any version. SCP (SCZ281) software version can be any version. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMH (GMZ283) software version can be any version. GMX (GMZ544) software version can be any version. GMX2 (GMZ802) software version can be any version. CXU-M (SXZ288) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for the pilot bit is available in Release 12 service pack 1 or higher.
Restrictions

This software version does not support ring protection. This software version does not support QMH-M unit. This software version does not support HCQ module.
Bugs
1+1 protection switch does not work reliably if an interface is configured in 2M unframed mode. (CR ID 300089699).
10004_22 2008 Tellabs.

225
17.11 Version 1.5

This is a version based on QMZ540 version 1.4 with features from QMZ540 version 10.5. Enhancements and Fixed Bugs

This software version supports freely allocated pilot bit. This software version supports SXU-V. This software version supports a G.821 Report for 1+1 protected trunks in Performance Management System. (CRF ID 4003959). NMS can now disable download QMH software. (CRF ID 4003834) QMH IF4 fault history does not report any more too many MUX/DEMUX back to line alarms. (CRF ID 40003924)
Dependencies

QMH (QMH509) hardware (1.x or 2.x) must be used. CCU (SCZ286) software version can be any version. SCU (SCZ280) software version can be any version. SCP (SCZ281) software version can be any version. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMH (GMZ283) software version can be any version. GMX (GMZ544) software version can be any version. CXU-M (SXZ288) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. MartisDXX Manager support for the pilot bit is available in Release 12 service pack 1 or higher.
Restrictions

Bugs

Line loop does not work in interfaces, where pilotbit parameters are set on. (CRF ID 4004404) Clock status sending in QMH doesnt work when SXU fails. (CRF ID 4004149)

226
10004_22 2008 Tellabs.
17.12 Version 1.4

This is an unofficial version based on QMZ540 version 1.3 with some features from QMZ540 version 10.5. Enhancements and Fixed Bugs

This software version supports freely allocated pilot bit. This software version supports SXU-V. NMS can now disable download QMH software. (CRF ID 4003834) QMH IF4 fault history does not report any more too many MUX/DEMUX back to line alarms. (CRF ID 40003924)
Dependencies

QMH (QMH509) hardware (1.x or 2.x) must be used. CCU (SCZ286) software version can be any version. SCU (SCZ280) software version can be any version. SCP (SCZ281) software version can be any version. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMH (GMZ283) software version can be any version. GMX (GMZ544) software version can be any version. CXU-M (SXZ288) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. MartisDXX Manager support for the pilot bit is available in Release 12 service pack 1 or higher.
Restrictions

Bugs

Line loop does not work in interfaces, where pilotbit parameters are set on. (CRF ID 4004404) Clock status sending in QMH doesnt work when SXU fails. (CRF ID 4004149) When creating a G.821 Report for 1+1 protected trunks in Performance Management System, available time (AT) is always 100% even if both trunks have been simultaneously cut. (CRF ID 4003959).
10004_22 2008 Tellabs.

227
17.13 Version 1.3

Dependencies

QMH (QMH509) hardware (1.x or 2.x) must be used. MartisDXX Manager support for this unit is available in Release 10.0 or higher.
Restrictions

This software version does not support ring protection. This software version does not support pilot bit. This software version does not support QMH-M unit. This software version does not support HCQ module. This software version does not support SXU-V unit.
Bugs
The following faults reported from IF4 are not constant when a fault is active: MUX/DMUX back to line, Line Loop made by neighbour, Remote controlled line loop and AIS in signalling. Clock status sending in QMH doesnt work when SXU fails. (CRF ID 4004149)
17.14 Version 1.2

Emergency version! Dependencies
QMH (QMH509) hardware (1.x or 2.x) must be used.
Restrictions

This software version does not support ring protection. This software version does not support pilot bit. This software version does not support QMH-M unit. This software version does not support BTQ-1088 and BTQ-2304 modules. This software version does not support HCQ module. This software version does not support SXU-V unit.

228
10004_22 2008 Tellabs.
Bugs
When the interface use of any of the four interfaces is changed from MUAP/SUAP to general, and the HDLC parameters are changed, it may cause neighbour node monitoring to fail to communicate with the node connected to the interface. When QMH is configured as 1+1 mode, all messages that NMS sends to link 6 are incorrectly sent to link 3 or 4 depending on the interface from which Rx data is selected (1+1 switch). So this can cause messages to be sent to the wrong destination depending on whether interface 3 or interface 4 is used by some other party. The following faults reported from IF4 are not constant when a fault is active: MUX/DMUX back to line, Line Loop made by neighbour, Remote controlled line loop and AIS in signalling. Clock status sending in QMH doesnt work when SXU fails. (CRF ID 4004149)
17.15 Version 1.1

Dependencies
Restrictions

Bugs
If NNM parameters are monitored and a hard/physical loop is placed, NNM sees the loop correctly. If the loop is taken off, NNM fails to detect the changed condition and reports NO CONNECTION state. This happens only on interface 1. The same happens if a trunk is connected from interface 1. When the interface use of any of the four interfaces is changed from MUAP/SUAP to general and HDLC parameters are changed, it may cause neighbour node nonitoring to fail to communicate with the node connected to the interface. When QMH is configured as 1+1 mode, all messages that NMS sends to link 6 are incorrectly sent to link 3 or 4 depending on the interface from which Rx data is selected (1+1 switch). This can cause messages to be sent to the wrong destination depending on whether interface 3 or interface 4 is used by some other party. Clock status sending in QMH doesnt work when SXU fails. (CRF ID 4004149)
10004_22 2008 Tellabs.

229
17.16 Version 1.0

Dependencies
Restrictions

Bugs

The IA activity missing alarm can become activated without a reason. Not completely tested. If NNM parameters are monitored and a hard/physical loop is placed, NNM sees the loop correctly. If the loop is taken off, NNM fails to detect the changed condition and reports NO CONNECTION state. This happens only on interface 1. The same happens if a trunk is connected from interface 1. When the interface use of any of the four interfaces is changed from MUAP/SUAP to general, and HDLC parameters are changed, it may cause neighbour node monitoring to fail to communicate with the node connected to the interface. When QMH is configured in 1+1 mode, all messages that NMS sends to link 6 are incorrectly sent to link 3 or 4 depending on the interface from which Rx data is selected (1+1 switch). This can cause messages to be sent to the wrong destination depending on whether interface 3 or interface 4 is used by some other party. Clock status sending in QMH doesnt work when SXU fails. (CRF ID 4004149)

230
10004_22 2008 Tellabs.
SBU UNIT: UTZ549 Unit Software
18 SBU UNIT: UTZ549 Unit Software

The software UTZ549 is used on the SBU unit in Tellabs 8160 A111 node.
18.1 Version 2.2

This is emergency version to fix flash driver problem first detected in GMX. In SBU unit functional flash related problems have not been found. Upgrading the unit to USW version 2.2 by downloading is however recommended for units that have USW 2.1 to prevent the small possibility of flash problem. Version is functionally identical to version 2.1.
18.2 Version 2.1

Support for new flash.
Dependencies

SBU hardware version must be 2.0 or higher. GMX (GMZ544) software version must be 3.8 or higher. MartisDXX Manager support for this unit is available in Release 11 Service Pack 2 or higher.
Restrictions

SNC/N protection cannot be used in GMX if the SBU units are used in the node. HDB3 counters do not indicate the exact number of errors unless the count is 0. Therefore, if the count is 0 there have not been errors. If the count is other than zero, there have been an unknown number of errors. The latest received Trail Trace Identifier which complies with the standard format (including CRC-7) is always shown in the field of the received TTI in the MartisDXX Manager. However, the received TTI which does not comply with the standard format is not displayed in the field. The same applies to the empty field, i.e. if the transmitter sends constant null character, the field shows the latest valid TTI with CRC-7 and the field is not updated. It is, however, possible to manually update the field in this case by e.g. changing the expected parameters. The previously explained feature does not affect the trace identifier mismatch fault (TIM), which means that it is always shown when the received trace identifier does not match with the expected one. It is not possible to change Trail Trace Identifier if SNC/I protection is used.
10004_22 2008 Tellabs.

231
SBU UNIT: UTZ549 Unit Software
Bugs
No known bugs.
18.3 Version 1.0

Dependencies

SBU (base unit UTU720) hardware version must be 1.x. GMX (GMZ544) software version must be 3.8 or higher. MartisDXX Manager support for this unit is available in Release 11 Service Pack 2 or higher.
Restrictions

SNC/N protection cannot be used in GMX if the SBU units are used in the node. HDB3 counters do not indicate the exact number of errors unless the count is 0. Therefore, if the count is 0 there have not been errors. If the count is other than zero, there have been an unknown number of errors. The latest received Trail Trace Identifier which complies with the standard format (including CRC-7) is always shown in the field of the received TTI in the MartisDXX Manager. However, the received TTI which does not comply with the standard format is not displayed in the field. The same applies to the empty field, i.e. if the transmitter sends constant null character, the field shows the latest valid TTI with CRC-7 and the field is not updated. It is, however, possible to manually update the field in this case by e.g. changing the expected parameters. The previously explained feature does not affect the trace identifier mismatch fault (TIM), which means that it is always shown when the received trace identifier does not match with the expected one. It is not possible to change Trail Trace Identifier if SNC/I protection is used.
Bugs
No known bugs.

232
10004_22 2008 Tellabs.
SCO Module: DPZ652 DSP Software
19 SCO Module: DPZ652 DSP Software

The software DPZ652 is used on Tellabs SCO (SCO786 with OMH and SCO785 with ESU) interface modules.
19.1 Version 4.1


Support for ESHDSL line modes. (CR ID 300056272) Metalink firmware 6.822.4 in use.
Dependencies

Tellabs SCO 786 hardware version must be 3.0 or higher (board with FPGA). Tellabs SCO785 hardware version must be 3.0 or higher (board with FPGA) but this software does not support ESHDSL modes in this hardware. OMH (OMZ675) software version must be 3.0 or higher. Tellabs 8100 network manager ESHDSL support is available in Release 15A or higher.
Restrictions

Neighbor node loop does not work with 1x208k and 2x208k line modes (because 114 clocking cannot be set at CTE in these modes). In case of two-pair mode, when one line is without attenuation and there is attenuation in the other line, "power back-off" may be ON or may be OFF for both lines.
Bugs
No known bugs.
10004_22 2008 Tellabs.

233
19.2 Version 3.1


48x64 modes added. 4-pair modes added. Metalink firmware 6.821.9 in use.
Dependencies

Tellabs SCO786 hardware version must be 3.0 or higher (board with FPGA). Tellabs SCO785 hardware version must be 3.0 or higher (board with FPGA). OMH (OMZ675) software version must be 2.0 or higher to support 4-pair modes and n=48 modes. Tellabs 8100 manager support for this unit is available in Release 13. Support for 3088 kbit/s line rates and 4-pair modes with Tellabs 8110 STE-10M NTU is available in Release 14-SP3.
Restrictions
In case of two-pair mode, when one line is without attenuation and there is attenuation in the other line, "power back-off" may be ON or may be OFF for both lines.
Bugs
No known bugs.
19.3 Version 1.4


New interoperable mode (N=32, master, I=1, no EOC) added. Grouped 1-pair operation fixed to be more reliable.
Dependencies

Tellabs SCO786 hardware version must be 2.0 or lower (without FPGA). Tellabs SCO785 hardware version must be 2.0 or lower (without FPGA). OMH (OMZ675) software version must be 1.2 or higher to support SCO module. Tellabs 8100 manager support for this unit is available in Release 13. Support for N=32 interoperable mode is available in Release R13A Service Pack 5.

234
10004_22 2008 Tellabs.
Restrictions
Bugs
No known bugs.
19.4 Version 1.3


Metalink firmware 6.82.8 in use. Compatible with ESU.
Dependencies

Tellabs SCO786 hardware version must be 2.0 or lower (without FPGA). Tellabs SCO785 hardware version must be 2.0 or lower (without FPGA). OMH (OMZ675) software version must be 1.2 or higher to support SCO module. Tellabs 8100 manager support for this unit is available in Release 13 or higher.
Restrictions
Bugs
Grouped 1-pair mode may not activate when after changing modes.
19.5 Version 1.1

Dependencies

Tellabs SCO786 hardware version must be 2.0 or lower (without FPGA). Tellabs SCO785 (for ESU) is not supported. OMH (OMZ675) software version must be 1.2 or higher to support SCO module. Tellabs 8100 manager support for this unit is available in Release 13 or higher.
10004_22 2008 Tellabs.

235
Restrictions
Bugs
No known bugs.

236
10004_22 2008 Tellabs.
SCU-H UNIT: SCZ545 Unit Software
20 SCU-H UNIT: SCZ545 Unit Software

Two software products are needed for the SCU-H unit (whose base unit is SCU587) in Tellabs 8150 basic, Tellabs 8160 A111, Tellabs 8184 access switch, Tellabs 8188 access switch and Tellabs 8170 cluster nodes, boot software and downloadable software. The major version number indicates if the boot code is compatible with the downloadable code. If the boot version is a.b and the downloadable version is c.d, they are compatible if and only if a = c. For example, downloadable code 2.0 cannot be downloaded if boot code version is 1.5.
20.1 Version 2.6

Support for GMX2, Tellabs 8184 access switch and Tellabs 8188 access switch.
Dependencies

SCU-H base unit hardware version must be 2.0 or higher to support Tellabs 8170 cluster node. GMX2 (GMZ802) software version can be any version. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit/interface card/functionality is available in Release 10.1A Service Pack 3 or higher.
Restrictions

This version cannot be downloaded to SCU-H which has software version 1.x. SCP-H does not allow a shorter address mask than its IP address class requires (e.g. if class C IP address is used, the minimum requirement for the address mask length is 24 bits).
Bugs

Removing lower (active) GMX from inventory does not activate upper GMX. Passive GMX is not activated when active GMX download is finished.
10004_22 2008 Tellabs.

237
20.2 Version 2.2

This is emergency version to fix flash driver problem first detected in GMX. In SCU-H unit functional flash related problems have not been found. Upgrading the unit to USW version 2.2 by downloading is however recommended for units that have USW 2.1 to prevent the small possibility of flash problem. Version is functionally identical to version 2.1.
20.3 Version 2.1

Support for new flash.
Dependencies

SCU-H base unit hardware version must be 2.0 or higher to support Tellabs 8170 cluster node. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit/interface card/functionality is available in Release 10.1A Service Pack 3 or higher.
Restrictions

This version cannot be downloaded to SCU-H which has software version 1.x. SCP-H does not allow a shorter address mask than its IP address class requires (e.g. if class C IP address is used, the minimum requirement for the address mask length is 24 bits).
Bugs

Removing lower (active) GMX from inventory does not activate upper GMX. GMX2 is not activated when GMX1 (active) download is finished.

238
10004_22 2008 Tellabs.
20.4 Version 1.18

Support for GMX2, Tellabs 8184 access switch and Tellabs 8188 access switch.
Dependencies

SCU-H (base unit SCU587) hardware version must be 1.1 or higher to support Tellabs 8170 cluster node. GMX2 (GMZ802) software version can be any version. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit/interface card/functionality is available in Release 10.1A Service Pack 3 or higher.
Restrictions

Extended links do not work correctly with GMX if GMX SW version is under 3.6. Tellabs 8170 cluster node support does not work if SCU-H HW version is under 1.1. SCP-H does not allow a shorter address mask than its IP address class requires (e.g. if class C IP address is used, the minimum requirement for the address mask length is 24 bits).
Bugs

Removing lower (active) GMX from inventory does not activate upper GMX. Passive GMX is not activated when active GMX download is finished.
20.5 Version 1.14


SCU-H USW 1.13 disabled (CR ID 200020227) SCU-H does not ARP for default gateway (CR ID 200022591) SCU-H should support storing GMX debug information (CR ID 200023772)
10004_22 2008 Tellabs.

239
Dependencies

SCU-H (base unit SCU587) hardware version must be 1.1 or higher to support Tellabs 8170 cluster node. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit/interface card/functionality is available in Release 10.1A Service Pack 3 or higher.
Restrictions

Bugs

20.6 Version 1.13


SCU-H resets under heavy load in Tellabs 8170 cluster node. (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash. (CR ID 200005521) Improvements to CLT operation. (CR ID 200008856) HDLC channel 13 is now working properly.
Dependencies

SCU-H (base unit SCU587) hardware version must be 1.1 or higher to support Tellabs 8170 cluster node. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit/interface card/functionality is available in Release 10.1A Service Pack 3 or higher.

240
10004_22 2008 Tellabs.
Restrictions

Bugs

20.7 Version 1.12

This is a non-production version based on version 1.11. Enhancements and Fixed Bugs (compared with version 1.11) The use of this version is recommended only to correct the following problem with SCU-H:
SCU-H unit gives power alarm when using protected PAU-10T. (CRF 4004981)
Dependencies

SCU-H (base unit SCU587) hardware version must be 1.1 or higher to support Cluster Node. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit/interface card/functionality is available in Release 10.1A Service Pack 3 or higher.
Restrictions

Extended links do not work correctly with GMX if GMX SW version is under 3.6. Cluster support does not work if SCU-H HW version is under 1.1. SCP-H does not allow a shorter address mask than its IP address class requires (e.g. if class C IP address is used, the minimum requirement for the address mask length is 24 bits).
10004_22 2008 Tellabs.

241
Bugs

Removing lower (active) GMX from inventory does not activate upper GMX. GMX2 is not activated when GMX1 (active) download is finished. HDLC channel 13 is not working properly. SCU-H resets under heavy load in Cluster Node. (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash. (CR ID 200005521)
20.8 Version 1.11


A bug that may cause A111 node internal clock disturbance during a GMX hardware switchover has been fixed. Changes to GMX switchover logic (equipment protection switch) have been implemented. This adds reliability to switchover against GMX fault monitoring or ASIC register corruption. Cluster VTP clock default value changed from 512kbit/s to 1024kbit/s. Old value might have caused inter-subrack communication problems in Cluster Nodes (CRF ID 4004982).
Dependencies

Restrictions

Bugs

Removing lower (active) GMX from inventory does not activate upper GMX. GMX2 is not activated when GMX1 (active) download is finished. HDLC channel 13 is not working properly.

242
10004_22 2008 Tellabs.
SCU-H unit gives power alarm when using protected PAU-10T. SCU-H resets under heavy load in Cluster Node. (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash. (CR ID 200005521)
20.9 Version 1.10

Dependencies

Restrictions

Bugs

A111 node internal clock may be disturbed during a GMX hardware switchover. Removing lower (active) GMX from inventory does not activate upper GMX. GMX2 is not activated when GMX1 (active) download is finished. HDLC channel 13 is not working properly. SCU-H resets under heavy load in Cluster Node. (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash. (CR ID 200005521)
10004_22 2008 Tellabs.

243
20.10 Version 1.6

Dependencies

Restrictions

Basic and Cluster Node support is not fully tested with this version. SCP-H is not supported.
Bugs

A111 node internal clock may be disturbed during a GMX hardware switchover. Removing lower (active) GMX from inventory does not activate upper GMX. GMX2 is not activated when GMX1 (active) download is finished. SCU-H resets under heavy load in Cluster Node (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash. (CR ID 200005521)

244
10004_22 2008 Tellabs.
20.11 Version 1.3

Dependencies

Restrictions

Basic and Cluster Node support is not fully tested with this version. SCP-H is not supported.
Bugs

A111 node internal clock may be disturbed during a GMX hardware switchover. In some cases unlocking the port fails. Retrying will help. Removing lower (active) GMX from inventory does not activate upper GMX. GMX2 is not activated when GMX1 (active) download is finished. Spontaneous reporting does not work correctly. SCU-H reset may interfere with GMX functionality. SCU-H resets under heavy load in Cluster Node. (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash. (CR ID 200005521)
10004_22 2008 Tellabs.

245
20.12 Version 1.2

Dependencies
No dependencies.
Restrictions

Basic and Cluster Node support is not fully tested with this version. This version cannot be used if SNC protection is used in GMX. SCP-H is not supported.
Bugs

A111 node internal clock may be disturbed during a GMX hardware switchover. In some cases unlocking the port fails. Retrying will help. Removing lower (active) GMX from inventory does not activate upper GMX. GMX2 is not activated when GMX1 (active) download is finished. Spontaneous reporting does not work correctly. SCU-H reset may interfere with GMX functionality. SCU-H resets under heavy load in Cluster Node. (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash. (CR ID 200005521)
20.13 Version 1.1

Dependencies
No dependencies.
Restrictions

Basic and Cluster Node support is not fully tested with this version. This version cannot be used if SNC protection is used in GMX. SCP-H is not supported.

246
10004_22 2008 Tellabs.
Bugs

A111 node internal clock may be disturbed during a GMX hardware switchover. SCU-H activates GMX too late in node reset -> GMU fails. In some cases unlocking the port fails. Retrying will help. Removing lower (active) GMX from inventory does not activate upper GMX. GMX2 is not activated when GMX1 (active) download is finished. Spontaneous reporting does not work correctly. SCU-H reset may interfere with GMX functionality. SCU-H resets under heavy load in Cluster Node. (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash. (CR ID 200005521)
20.14 Version 1.0

Dependencies
No dependencies.
Restrictions

Basic and Cluster Node support is not fully tested with this version. PFU-H and FAN eeprom checksums are missing. This version cannot be used if SNC protection is used in GMX. SCP-H is not supported.
Bugs

A111 node internal clock may be disturbed during a GMX hardware switchover. SCU-H activates GMX too late in node reset -> GMU fails. In some cases unlocking the port fails. Retrying will help. Removing lower (active) GMX from inventory does not activate upper GMX. GMX2 is not activated when GMX1 (active) download is finished. Spontaneous reporting does not work correctly. If the circuit test loop is activated and SCU-H is reset the test port will remain reserved. SCU-H reset may interfere with GMX functionality. SCU-H resets under heavy load in Cluster Node. (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash. (CR ID 200005521)
10004_22 2008 Tellabs.

247
SXU-A and SXU-B Units: SXZ282 Unit Software
21 SXU-A and SXU-B Units: SXZ282 Unit Software

The software SXZ282 is used on the cross-connection units SXU-A/ SXU-B in Tellabs 8150 basic node.
21.1 Version 10.6

The fault Fallback list warning is activated according to the master clock state if Use Quality Levels is selected in master clock status window. This fault is a customer requirement. (CR ID 300035785) The fault Reconfiguring X-conn DB does not any more activate in unprotected node when the inventory is created. (CR ID 300038096) There is a possibility for enhanced detection of RAM faults during a functional test. (CR ID 300038625)
Dependencies

SXU-A/SXU-B (base unit SXU212/SXU218) hardware versions must be 5.0. SCP (SCZ281) software version can be any version. SCU (SCZ280) software version can be any version. SCU-H (SCZ545) software version must be 1.6 or higher. Tellabs 8100 manager support for the extended XB port capacity is available in Release 13 Service Pack 5 or higher.
Restrictions
No restrictions.
Bugs
No known bugs.

248
10004_22 2008 Tellabs.
21.2 Version 10.5

The testing of the incoming message integrity is improved. The SXU unit is able to detect a message that has a consistency problem in the internal data structure. The processing of the invalid message is prevented. This will make the unit much more reliable in case of any communication problem. (CR ID 200033949) The test timeslot used internally for port IA testing depends on the port capacity. This modification is needed to support Tellabs 8110 STE-10M network terminating unit and any other product when speeds over 8960 kbit/s are used. (CR ID 200031045) The background sending of the cross-connected timeslots (Free Time Slot sending) operates correctly for ports over 8448 kbit/s. An interface unit needs this information to function correctly. Data errors would follow if this message was not sent by SXU. (CR ID 200032284) The node reset or simultaneous reset of both SXUs during X-connect database reconfiguration process cannot cause the corruption of X-connect database of SXU. The error was possible because the SXU with incomplete copy of the X-connect database could become active after node reset. This possibility is prevented by storing the reconfiguration state in flash memory during reconfiguration and activating the Reconfiguring X-connect database fault again after reset according to the non-volatile fault state. Immediate switch over after reset will automatically follow preventing the wrong SXU becoming active. (CR ID 200033778)
Dependencies

Restrictions

Does not have the possibility for enhanced detection of RAM faults during functional test. (CR ID 300038625) The fault Fallback list warning is not activated. This fault is a customer requirement. (CR ID 300035785)
Bugs
The fault Reconfiguring X-conn DB may activate and stay active in unprotected node when the inventory is created. (CR ID 300038096)
10004_22 2008 Tellabs.

249
21.3 Version 10.4

The support of high capacity X-bus ports is added (up to 192*64 kbit/s).
Dependencies

Restrictions

Does not have the possibility for enhanced detection of RAM faults during functional test. (CR ID 300038625) The fault Fallback list warning is not activated. The activation is a customer requirement. (CR ID 300035785) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949)
Bugs
The background sending of the cross connected timeslots (FTS or Free Time Slot sending) of high capacity X-bus ports (over 8M) does not operate correctly. An interface unit needs this information to function correctly. Data errors will follow if this message is not sent by SXU. (CR ID 200032284) If a port bigger than 140*64 kbit/s is used the IA test timeslot overlaps with payload data and data errors will follow. (CR ID 200031045)

250
10004_22 2008 Tellabs.
21.4 Version 10.3


X-Connect RAM fault now disappears automatically when the error condition has ended. Minor flash system bug causing rare flash memory corruptions is fixed. Fallback list warning faults are not anymore generated. These have been replaced with Faulty clock source of choice n faults. The same change has already earlier been done to Tellabs 8160 A111/GMX and XCG. The QL value reported from the unit to the Master Clock State window is set to value 7 (Do Not Use) when there is an active problem in the clock source. Also the EXT clock QL is set to value 7 (DNU) when there is an active problem in the external clock source. This change concerns only the reporting of QL values. The actual selection logic in the unit has been working without any problems and remains unchanged. Neighbour node monitoring (NNM) polling status problems cannot cause wrong clock selection anymore. In the case of NNM link communication problem the QL value is set to 7 (DNU) to prevent wrong clock source selection. Normally the master clock QL value of a clock source is obtained from an interface unit by polling it inside the node. The interface unit gets the QL from neighbour node by the NNM mechanism. The possibility of an incomplete initialization state of SXU is not anymore possible. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This incomplete initialization state looked as if the node had lost inventory. However, the node parameters related to the inventory were neither lost nor changed. This state was permanent. Traffic was not recovered at power up and the node was not usable before SXU unit was reset again.
Dependencies

Restrictions

Does not have the possibility for enhanced detection of RAM faults during a functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) Does not support cross connections of high capacity (> 8 Mbit/s) X-bus ports
10004_22 2008 Tellabs.

251
Bugs
Flash operations slower than in version 10.2 which may cause TIMEOUT messages in user interface
21.5 Version 10.2

Dependencies
SXU212/SXU218 versions must be 5.0.
Restrictions

Does not have the possibility for enhanced detection of RAM faults during functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) The XB port capacity up to 192x64kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Fallback list warning faults are shown.
Bugs
X-Connect RAM Fault does not disappear when the error condition causing it is over. When the fault remains active after the problem the switch over logic does not operate. To get rid of the unnecessary but rare fault the unit has to be reset. Flash system has a bug causing rare flash memory corruptions. The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. There is a possibility of an incomplete initialization in SXU. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This permanent error state looks like if the node has lost inventory. However the node parameters related to the inventory are neither lost nor changed. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. The SXU unit disappears periodically from the Units Not in Inventory list of Subrack Inventory dialog when there is an EPS unit in the node and the node inventory has been deleted. Time period is about 30 seconds. SXU is visible 15 seconds and then unvisible 30 seconds. When SXU is not visible, it is not possible to add SXU to the inventory. This is a clear but minor problem.

252
10004_22 2008 Tellabs.
21.6 Version 10.1

Dependencies
Restrictions

Does not have the possibility for enhanced detection of RAM faults during a functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) The XB port capacity up to 192x64kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Fallback list warning faults are shown.
Bugs
X-Connect RAM Fault does not disappear when the error condition causing it is over. When the fault remains active after the problem the switch over logic does not operate. To get rid of the unnecessary but rare fault the unit has to be reset. Flash system has a bug causing rare flash memory corruptions. The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. There is a possibility of an incomplete initialization in SXU. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This permanent error state looks like if the node has lost inventory. However the node parameters related to the inventory are neither lost nor changed. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. Extended lists (clear channel configuration) are not cleared when SXU is removed from the inventory. Existing extended lists are not cleared when SXU is put in an unprotected node, which may lead to invalid clear channel parameters. Cross-connection protection will correct this problem in a protected node. Frame errors may happen during switch over. There is an about 4-second delay when changing the clock from internal to external clock. When version r10.1 and an older version is used in the same protected node, the alarm Passive Flash Version Fault is always activated which is wrong. At slow modem baud rates of 2400 or less, when the EPS Clear Channel is used, an internal software timer expires too fast and disconnects the Clear Channel prematurely. Above 2400 bauds there is sufficient time to complete the operations and no problem exists.
10004_22 2008 Tellabs.

253
It is possible to change port parameters when the port is in swapped state. Swapped ports are expected to be equal. When the node master clock becomes faulty, SXU does not select the next best choice at once but there may be some intermediate states. The effect of this is a bit slower clock stabilization. During unit initialization after reset the Clock Switchover Fault is activated for a short time period. This may lead to unnecessary switchover. However this is not a critical problem because units are not in operative state.
21.7 Version 10.0

Dependencies
Restrictions

Does not have the possibility for enhanced detection of RAM faults during a functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) Does not support EPS clear channel dynamic cross-connections. Does not support the CIF port type (bit capacity) that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-Bus allocation. The XB port capacity up to 192x64kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Fallback list warning faults are shown.
Bugs
X-Connect RAM Fault does not disappear when the error condition causing it is over. When the fault remains active after the problem the switch over logic does not operate. To get rid of the unnecessary but rare fault the unit has to be reset. Flash system has a bug causing rare flash memory corruptions. The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. There is a possibility of an incomplete initialization in SXU. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This permanent error state looks like if the node has lost inventory.

254
10004_22 2008 Tellabs.
However the node parameters related to the inventory are neither lost nor changed. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again.
Bit errors may occur during node synchronization source changes when the following conditions are true: 1) There are at least 3 entries in FBL, 2) the entry currently used is the only valid one, 3) the clock becomes suddenly faulty due to a physical reason and 4) after that the node starts using the internal clock. Adding a new GMU to a node may sometimes lead to unexpected faults on the GMU unit and problems in its operation. This is due to an invalid clock state command sent from SXU to GMU because the state machine controlling the commands is not initialized properly according to the inventory state change. The problem will only occur when adding a new GMU to a node and it will disappear after any change in the node synchronization. It does not affect the other units in that node. SXU uses SDH SSM code SEC for quality level 6 (internal clock). This value should be DNU (Do Not Use). If there is only one channel unit in a protected node that has locked ports and the fault Xconnection Bus Alarm is activated and the reason for that fault is not a problem in the active SXU (the problem cannot be solved by switching the active SXU), it may lead to continuous switching of the active SXU. When a clock source interface is removed from FBL and EXT clock is updated in the FBL with a single operation in a protected Basic Node, there will be a permanent PLL alarm in the passive SXU. This alarm does not affect node operation and it is cleared after next FBL update. There is an about 4-second delay when changing the clock from internal to external clock. It is possible to change port parameters when the port is in swapped state. Swapped ports are expected to be equal. When the node master clock becomes faulty, SXU does not select the next best choice at once but there may be some intermediate states. The effect of this is a bit slower clock stabilization. During unit initialization after reset the Clock Switchover fault is activated for a short time period. This may lead to unnecessary switchover. However this is not a critical problem because units are not in operative state.
21.8 Version 6.11

This is an unofficial version based on SXZ282 release r6.8 with bug fix for clustered point to multipoint (PMP) Server port init problem. This version should not be used once the official r6.9 is available.
21.9 Version 6.10

This is an unofficial version based on SXZ282 release r6.9 development version with CIF port type support. This version should not be used once the official r6.9 is available.
10004_22 2008 Tellabs.

255
21.10 Version 6.9

Dependencies
SXU212/SXU218 versions must be lower than 5.0.
Restrictions

Does not have the possibility for enhanced detection of RAM faults during functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) Does not support EPS clear channel dynamic cross-connections. Does not support the CIF port type (bit capacity) that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-Bus allocation. No support for base unit version 5.0. The XB port capacity up to 192x64kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Fallback list warning faults are shown.
Bugs
X-Connect RAM Fault does not disappear when the error condition causing it is over. When the fault remains active after the problem the switch over logic does not operate. To get rid of the unnecessary but rare fault the unit has to be reset. Flash system has a bug causing rare flash memory corruptions. The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. There is a possibility of an incomplete initialization in SXU. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This permanent error state looks like if the node has lost inventory. However the node parameters related to the inventory are neither lost nor changed. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. Adding a new GMU to a node may sometimes lead to unexpected faults on the GMU unit and problems in its operation. This is due to an invalid clock state command sent from SXU to GMU because the state machine controlling the commands is not initialized properly according to the inventory state change. The problem will only occur when adding a new GMU to a node and it will disappear after any change in the node synchronization. It does not affect the other units in that node.

256
10004_22 2008 Tellabs.
SXU uses SDH SSM code SEC for quality level 6 (internal clock). This value should be DNU (Do Not Use). If there is only one channel unit in a protected node that has locked ports and the fault XConnection Bus Alarm is activated and the reason for that fault is not a problem in the active SXU (the problem cannot be solved by switching the active SXU), it may lead to continuous switching of the active SXU. Frame errors may happen during switch over. There is an about 4-second delay when changing the clock from internal to external clock. It is possible to change port parameters when the port is in swapped state. Swapped ports are expected to be equal. When the node master clock becomes faulty, SXU does not select the next best choice at once but there may be some intermediate states. The effect of this is a bit slower clock stabilization. During unit initialization after reset the Clock Switchover Fault is activated for a short time period. This may lead to unnecessary switchover. However this is not a critical problem because units are not in operative state.
21.11 Version 6.8

Dependencies
Restrictions

Does not have the possibility for enhanced detection of RAM faults during a functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) No support for improved and nearly hitless change over. Clock changes are not indicated in fault history. Does not support the improved external clock protection (switch over happens if the node starts using the internal clock and the passive SXU still has a valid external clock). Does not indicate synchronization source changes in fault history. Does not support the CIF port type (octet capacity) that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-Bus allocation. No support for base unit version 5.0. Does not support EPS clear channel dynamic cross connections. Does not support the CIF port type (bit capacity) that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-Bus allocation.
10004_22 2008 Tellabs.

257
The XB port capacity up to 192x64kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Fallback list warning faults are shown.
Bugs
X-Connect RAM Fault does not disappear when the error condition causing it is over. When the fault remains active after the problem the switch over logic does not operate. To get rid of the unnecessary but rare fault the unit has to be reset. Flash system has a bug causing rare flash memory corruptions. The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. There is a possibility of an incomplete initialization in SXU. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This permanent error state looks like if the node has lost inventory. However the node parameters related to the inventory are neither lost nor changed. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. Removing a passive SXU in a protected node causes errors in traffic. The port object allows changing the even/uneven bus allocation parameter for an existing port. If an active SXU loses external clock protection, switching is not done but either the next clock from the fallback list is chosen or the node starts to use the internal clock. This happens even if a passive SXU had a valid external clock. With SXU-A in an unprotected node, ports for unit 14 are allocated incorrectly. These ports can be cross-connected but the connections do not operate. This happens with all the node types allowed with SXU-A. When using a quality source other than polled, the real QL value used in the clock selection is not sent to the neighbour node. If there is a clustered point to multipoint (PMP) Server that has locked ports in the node, SXU is unable to init the ports during unit reset due to lack of stack space and the unit will stay in reset loop until it is removed from the node. Adding a new GMU to a node may sometimes lead to unexpected faults on the GMU unit and problems in its operation. This is due to an invalid clock state command sent from SXU to GMU because the state machine controlling the commands is not initialized properly according to the inventory state change. The problem will only occur when adding a new GMU to a node and it will disappear after any change in the node synchronization. It does not affect the other units in that node. SXU uses SDH SSM code SEC for quality level 6 (internal clock). This value should be DNU (Do Not Use). If there is only one channel unit in a protected node that has locked ports and the fault CConnection Bus alarm is activated and the reason for that fault is not a problem in the active SXU (the problem cannot be solved by switching the active SXU), it may lead to continuous switching of the active SXU.

258
10004_22 2008 Tellabs.
There is an about 4-second delay when changing the clock from internal to external clock. It is possible to change port parameters when the port is in swapped state. Swapped ports are expected to be equal. When the node master clock becomes faulty, SXU does not select the next best choice at once but there may be some intermediate states. The effect of this is a bit slower clock stabilization.
21.12 Version 6.7

This version is forbidden.
21.13 Version 6.6

Dependencies
Restrictions

Does not have the possibility for enhanced detection of RAM faults during a functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) No support for improved and nearly hitless change over. Clock changes are not indicated in fault history. Does not support the improved external clock protection (switch over happens if the node starts using the internal clock and the passive SXU still has a valid external clock). Does not indicate the synchronization source changes in fault history. Does not support the CIF port type (octet capacity) that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-Bus allocation. No support for base unit version 5.0. Does not support EPS clear channel dynamic cross connections. Does not support the CIF port type (bit capacity) that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-Bus allocation. The XB port capacity up to 192x64kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Fallback list warning faults are shown.
10004_22 2008 Tellabs.

259
Bugs
X-Connect RAM Fault does not disappear when the error condition causing it is over. When the fault remains active after the problem the switch over logic does not operate. To get rid of the unnecessary but rare fault the unit has to be reset. Flash system has a bug causing rare flash memory corruptions. The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. There is a possibility of an incomplete initialization in SXU. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This permanent error state looks like if the node has lost inventory. However the node parameters related to the inventory are neither lost nor changed. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. Circuit functioning may have some delay when using xgroup IDs if more than one ID state is changed within a few seconds. The average delay is 1 min and the maximum value is 2 min. In SXU-B the communication channels for S1/K3 bytes between GMU and SXU may stop operating depending on how the cross-connect ASIC numbers happen to be allocated for this purpose. This allocation may change when the unit is reset or the GMU is removed and added QL enable parameter does not affect the Unstable SSM fault. The port object allows setting CAS on for a connected port if the following conditions are true: Data connection to CAS ts is created with xgroup ID and that ID is not active. After setting CAS on it is not possible to set it off or delete the connection. If both SXUs in a protected Basic Node experience an SW reset almost simultaneously, it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. The bug appears if all of the following happens simultaneously: a) data structures are corrupted (as just explained) b) EXT clock is on the fallback list, c) EXT is chosen to master clock of the node and d) EXT is in failed state. Under these circumstances, the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window. Removing a passive SXU from a protected node causes errors in traffic. The port object allows changing the even/uneven bus allocation parameter for an existing port. If active SXU loses the external clock protection, switching is not done but either the next clock from the fallback list is chosen or the node starts to use the internal clock. This happens even if a passive SXU had a valid external clock. With SXU-A in an unprotected node ports for unit 14 are allocated incorrectly. These ports can be cross-connected but the connections do not operate. This happens with all the node types allowed with SXU-A. When using a quality source other than polled, the real QL value used in the clock selection is not sent to the neighbour node.

260
10004_22 2008 Tellabs.
If there is a clustered point to multipoint (PMP) Server that has locked ports in the node, SXU is unable to init the ports during unit reset due to lack of stack space and the unit will stay in reset loop until it is removed from the node. Adding a new GMU to a node may sometimes lead to unexpected faults on the GMU unit and problems in its operation. This is due to an invalid clock state command sent from SXU to GMU because the state machine controlling the commands is not initialized properly according to the inventory state change. The problem will only occur when adding a new GMU to a node and it will disappear after any change in the node synchronization. It does not affect the other units in that node. SXU uses SDH SSM code SEC for quality level 6 (internal clock). This value should be DNU (Do Not Use). If there is only one channel unit in a protected node that has locked ports and the fault XConnection Bus Alarm is activated and the reason for that fault is not a problem in the active SXU (the problem cannot be solved by switching the active SXU), it may lead to continuous switching of the active SXU. There is an about 4-second delay when changing the clock from internal to external clock. It is possible to change port parameters when the port is in swapped state. Swapped ports are expected to be equal. When the node master clock becomes faulty, SXU does not select the next best choice at once but there may be some intermediate states. The effect of this is a bit slower clock stabilization.
21.14 Version 6.5

Dependencies
Restrictions

Does not have the possibility for enhanced detection of RAM faults during a functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) No support for GMU. No support for improved and nearly hitless change over. Clock changes are not indicated in fault history. Does not support the improved external clock protection (switch over happens if the node starts using the internal clock and the passive SXU still has a valid external clock). Does not indicate synchronization source changes in fault history. Does not support the CIF port type (octet capacity) that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-Bus allocation.
10004_22 2008 Tellabs.

261
No support for base unit version 5.0. Does not support EPS clear channel dynamic cross connections. Does not support the CIF port type (bit capacity) that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-Bus allocation. The XB port capacity up to 192x64kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Fallback list warning faults are shown.
Bugs
X-Connect RAM Fault does not disappear when the error condition causing it is over. When the fault remains active after the problem the switch over logic does not operate. To get rid of the unnecessary but rare fault the unit has to be reset. Flash system has a bug causing rare flash memory corruptions. The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. There is a possibility of an incomplete initialization in SXU. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This permanent error state looks like if the node has lost inventory. However the node parameters related to the inventory are neither lost nor changed. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. The list of available ports for the master clock is not updated when the unit is removed from inventory. PLL alarm does not affect the clock selection. Loss of external clock causes a switch over. A unit does not disappear from the list of available clock sources when the unit is removed from the inventory. If an external clock is the current clock source and the external clock input is broken, it is possible that the next clock is not correctly picked from the fallback list. An unnecessary Fallback list warning fault may rise if there are still usable clock sources. If a unit belongs to the node inventory but it is physically missing while SXU is resetting, SXU may assume that the missing unit is still outputting usable clock signal. Circuit functioning may have some delay when using xgroup IDs if more than one ID state is changed within a few seconds. The average delay is 1 min and the maximum value is 2 min. The port object allows setting CAS on for connected port if the following conditions are true: Data connection to CAS ts is created with xgroup ID and that ID is not active. After setting CAS on it is not possible to set it off or delete the connection. If both SXUs in a protected Basic Node experience an SW reset almost simultaneously, it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. The bug appears if all of the following happens simultaneously: a) data

262
10004_22 2008 Tellabs.
structures are corrupted (as just explained) b) EXT clock is on the fallback list, c) EXT is chosen as the master clock of the node and d) EXT is in failed state. Under these circumstances, the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window.

Removing a passive SXU in a protected node causes errors in traffic. The port object allows changing the even/uneven bus allocation parameter for an existing port. If there is only one channel unit in a protected node that has locked ports and the fault XConnection Bus Alarm is activated and the reason for that fault is not a problem in the active SXU (the problem cannot be solved by switching the active SXU), it may lead to continuous switching of the active SXU. There is an about 4-second delay when changing the clock from internal to external clock. It is possible to change port parameters when the port is in swapped state. Swapped ports are expected to be equal. When the node master clock becomes faulty, SXU does not select the next best choice at once but there may be some intermediate states. The effect of this is a bit slower clock stabilization.
21.15 Version 6.3

Dependencies
Restrictions

Does not have the possibility for enhanced detection of RAM faults during a functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) Setting the signaling bit idle value is not supported. Slow cross-connect operations. No T1 support. No support for GMU. No support for improved and nearly hitless change over. Clock changes are not indicated in fault history. Does not support the improved external clock protection (switch over happens if a node starts using the internal clock and the passive SXU still has a valid external clock). Does not indicate synchronization source changes in fault history
10004_22 2008 Tellabs.

263
Does not support the CIF port type (octet capacity) that is used to fix a certain CIF ASIC bug in the interface unit with using a slightly different X-Bus allocation. No support for base unit version 5.0. Does not support EPS clear channel dynamic cross connections. Does not support the CIF port type (bit capacity) that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-Bus allocation. The XB port capacity up to 192x64kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Fallback list warning faults are shown.
Bugs
X-Connect RAM Fault does not disappear when the error condition causing it is over. When the fault remains active after the problem the switch over logic does not operate. To get rid of the unnecessary but rare fault the unit has to be reset. Flash system has a bug causing rare flash memory corruptions. The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. There is a possibility of an incomplete initialization in SXU. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This permanent error state looks like if the node has lost inventory. However the node parameters related to the inventory are neither lost nor changed. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. The list of available ports for the master clock is not updated when the unit is removed from the inventory. PLL alarm does not affect the clock selection. Loss of the external clock causes a switch over. A unit does not disappear from the list of available clock sources when the unit is removed from inventory. If the external clock is the current clock source and the external clock input is broken, it is possible that the next clock is not correctly picked from the fallback list. An unnecessary Fallback list warning fault may rise if there are still usable clock sources. If a unit belongs to the node inventory but it is physically missing while SXU is resetting, SXU may assume that the missing unit is still outputting usable clock signal. The port object allows setting CAS on for connected port if the following conditions are true: Data connection to CAS ts is created with xgroup ID and that ID is not active. After setting CAS on it is not possible to set it off or delete the connection. If both SXUs in a protected Basic Node experience an SW reset almost simultaneously, it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. The bug appears if all of the following happens simultaneously: a) data structures are corrupted (as just explained) b) EXT clock is on the fallback list, c) EXT is

264
10004_22 2008 Tellabs.
chosen as the master clock of the node and d) EXT is in failed state. Under these circumstances, the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window.

Removing a passive SXU in a protected node causes errors in traffic. The port object allows changing the even/uneven bus allocation parameter for existing port. If there is only one channel unit in a protected node that has locked ports and the fault XConnection Bus Alarm is activated and the reason for that fault is not a problem in the active SXU (the problem cannot be solved by switching the active SXU), it may lead to continuous switching of the active SXU. There is an about 4-second delay when changing the clock from internal to external clock. It is possible to change port parameters when the port is in swapped state. Swapped ports are expected to be equal. When the node master clock becomes faulty, SXU does not select the next best choice at once but there may be some intermediate states. The effect of this is a bit slower clock stabilization.
21.16 Version 6.2

Dependencies
Restrictions

Does not have the possibility for enhanced detection of RAM faults during a functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) Setting the signaling bit idle value is not supported. Slow cross-connect operations. No T1 support. No support for GMU. No support for improved and nearly hitless change over. Clock changes are not indicated in fault history. Does not support the improved external clock protection (switch over happens if the node starts using the internal clock and the passive SXU still has a valid external clock). Does not indicate synchronization source changes in fault history Does not support the CIF port type (octet capacity) that is used to fix a certain CIF ASIC bug in the interface unit with using a slightly different X-Bus allocation. No support for base unit version 5.0.
10004_22 2008 Tellabs.

265
Does not support EPS clear channel dynamic cross connections. Does not support the CIF port type (bit capacity) that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-Bus allocation. The XB port capacity up to 192x64kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Fallback list warning faults are shown.
Bugs
X-Connect RAM Fault does not disappear when the error condition causing it is over. When the fault remains active after the problem the switch over logic does not operate. To get rid of the unnecessary but rare fault the unit has to be reset. Flash system has a bug causing rare flash memory corruptions. The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. There is a possibility of an incomplete initialization in SXU. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This permanent error state looks like if the node has lost inventory. However the node parameters related to the inventory are neither lost nor changed. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. NMS disaster recovery cannot be used. The list of available ports for the master clock is not updated when the unit is removed from inventory. PLL alarm does not affect the clock selection. Loss of external clock causes a switch over. A unit does not disappear from the list of available clock sources when the unit is removed from the inventory. If the external clock is the current clock source and the external clock input is broken, it is possible that the next clock is not correctly picked from the fallback list. An unnecessary Fallback list warning fault may rise if there are still usable clock sources. If a unit belongs to the node inventory but it is physically missing while SXU is resetting, SXU may assume that the missing unit is still outputting usable clock signal. The port object allows setting CAS on for connected port if the following conditions are true: Data connection to CAS ts is created with xgroup ID and that ID is not active. After setting CAS on it is not possible to set it off or delete the connection. If both SXUs in a protected Basic Node experience an SW reset almost simultaneously, it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. The bug appears if all of the following happen simultaneously: a) data structures are corrupted (as just explained), b) EXT clock is on fallback list, c) EXT is chosen as the master clock of the node and d) EXT is in failed state. Under these circumstances, the active SXU fails to realize the failure of EXT and does not choose the

266
10004_22 2008 Tellabs.
next clock from the fallback list. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window.

Removing a passive SXU in a protected node causes errors in traffic. The port object allows changing the even/uneven bus allocation parameter for existing port. If there is only one channel unit in a protected node that has locked ports and the fault XConnection Bus Alarm is activated and the reason for that fault is not a problem in the active SXU (the problem cannot be solved by switching the active SXU), it may lead to continuous switching of the active SXU. There is an about 4-second delay when changing the clock from internal to external clock. It is possible to change port parameters when the port is in swapped state. Swapped ports are expected to be equal. When node master clock becomes faulty SXU does not select the next best choice at once but there may be some intermediate states. The effect of this is a bit slower clock stabilization.
21.17 Version 6.1

Dependencies
Restrictions

Does not have the possibility for enhanced detection of RAM faults during a functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) Setting the signaling bit idle value is not supported. Slow cross-connect operations. Does not support using of contradirectional synchronization clock sources in a protected ring network topology. No T1 support. No support for GMU. No support for improved and nearly hitless change over. Clock changes are not indicated in fault history. Does not support the improved external clock protection (switch over happens if the node starts using the internal clock and the passive SXU still has a valid external clock). Does not indicate synchronization source changes in fault history Does not support the CIF port type (octet capacity) that is used to fix a certain CIF ASIC bug in the interface unit with using a slightly different X-Bus allocation.
10004_22 2008 Tellabs.

267
Bugs
X-Connect RAM Fault does not disappear when the error condition causing it is over. When the fault remains active after the problem the switch over logic does not operate. To get rid of the unnecessary but rare fault the unit has to be reset. Flash system has a bug causing rare flash memory corruptions. The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. There is a possibility of an incomplete initialization in SXU. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This permanent error state looks like if the node has lost inventory. However the node parameters related to the inventory are neither lost nor changed. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. NMS disaster recovery cannot be used. The list of available ports for the master clock is not updated when the unit is removed from inventory. PLL alarm does not affect the clock selection. Loss of external clock causes a switch over. A unit does not disappear from the list of available clock sources when the unit is removed from inventory. If an external clock is the current clock source and the external clock input is broken, it is possible that the next clock is not correctly picked from the fallback list. If a unit belongs to the node inventory but it is physically missing while SXU is resetting, SXU may assume that the missing unit is still outputting usable clock signal. The port object allows setting CAS on for connected port if the following conditions are true: Data connection to CAS ts is created with xgroup ID and that ID is not active. After setting CAS on it is not possible to set it off or delete the connection. If both SXUs in a protected Basic Node experience an SW reset almost simultaneously, it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. The bug appears if all of the following happens simultaneously: a) data structures are corrupted (as just explained), b) EXT clock is on the fallback list, c) EXT is chosen as the master clock of the node and d) EXT is in failed state. Under these circumstances, the active SXU fails to realize the failure of EXT and does not choose the

268
10004_22 2008 Tellabs.
next clock from the fallback list. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window.

Removing a passive SXU in a protected node causes errors in traffic. The port object allows changing the even/uneven bus allocation parameter for existing port. If there is only one channel unit in a protected node that has locked ports and the fault XConnection Bus Alarm is activated and the reason for that fault is not a problem in the active SXU (the problem cannot be solved by switching the active SXU), it may lead to continuous switching of the active SXU. There is an about 4-second delay when changing the clock from internal to external clock. It is possible to change port parameters when the port is in swapped state. Swapped ports are expected to be equal. When the node master clock becomes faulty SXU does not select the next best choice at once but there may be some intermediate states. The effect of this is a bit slower clock stabilization.
21.18 Version 6.0

Dependencies
Restrictions

Does not have the possibility for enhanced detection of RAM faults during a functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) Setting the signalling bit idle value is not supported. Slow cross-connect operations. Does not support using of contradirectional synchronization clock sources in a protected ring network topology. No T1 support. No support for GMU. No support for improved and nearly hitless change over. Clock changes are not indicated in fault history. Does not support the improved external clock protection (switch over happens if the node starts using the internal clock and the passive SXU still has a valid external clock). Does not indicate synchronization source changes in fault history Does not support the CIF port type (octet capacity) that is used to fix a certain CIF ASIC bug in the interface unit with using a slightly different X-Bus allocation.
10004_22 2008 Tellabs.

269
Bugs
X-Connect RAM Fault does not disappear when the error condition causing it is over. When the fault remains active after the problem the switch over logic does not operate. To get rid of the unnecessary but rare fault the unit has to be reset. Flash system has a bug causing rare flash memory corruptions. The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. There is a possibility of an incomplete initialization in SXU. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This permanent error state looks like if the node has lost inventory. However the node parameters related to the inventory are neither lost nor changed. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. The whole bit connection capacity cannot be taken in use in SXU-A. NMS disaster recovery cannot be used. The real time clock can be used only in adaptive mode. The list of available ports for the master clock is not updated when the unit is removed from the inventory. PLL alarm does not affect the clock selection. Loss of external clock causes a switch over. A unit does not disappear from the list of available clock sources when the unit is removed from the inventory. If an external clock is the current clock source and the external clock input is broken, it is possible that the next clock is not correctly picked from the fallback list. If a unit belongs to the node inventory but it is physically missing while SXU is resetting, SXU may assume that the missing unit is still outputting usable clock signal. The port object allows setting CAS on for connected port if the following conditions are true: Data connection to CAS ts is created with xgroup ID and that ID is not active. After setting CAS on it is not possible to set it off or delete the connection. If both SXUs in a protected Basic Node experience an SW reset almost simultaneously, it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. The bug appears if all of the following happens simultaneously: a) data structures are corrupted (as just explained), b) the EXT clock is on the fallback list, c) EXT

270
10004_22 2008 Tellabs.
is chosen as the master clock of the node and d) EXT is in failed state. Under these circumstances, the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window.

Removing the passive SXU in a protected node causes errors in traffic. The port object allows changing the even/uneven bus allocation parameter for the existing port. If there is only one channel unit in a protected node that has locked ports and the fault XConnection Bus Alarm is activated and the reason for that fault is not a problem in the active SXU (the problem cannot be solved by switching the active SXU), it may lead to continuous switching of the active SXU. There is an about 4-second delay when changing the clock from internal to external clock. It is possible to change port parameters when the port is in swapped state. Swapped ports are expected to be equal. When the node master clock becomes faulty SXU does not select the next best choice at once but there may be some intermediate states. The effect of this is a bit slower clock stabilization.
21.19 Version 5.9

Dependencies
Restrictions

Does not have the possibility for enhanced detection of RAM faults during a functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) Setting the signalling bit idle value is not supported. Slow cross-connect operations. Does not support the using of contradirectional synchronisation clock sources in a protected ring network topology. No T1 support. No support for GMU. No support for improved and nearly hitless change over. Clock changes are not indicated in fault history. Does not support the improved external clock protection (switch over happens if the node starts using internal clock and the passive SXU still has a valid external clock). Does not indicate synchronization source changes in fault history
10004_22 2008 Tellabs.

271
Does not support the CIF port type (octet capacity) that is used to fix a certain CIF ASIC bug in the interface unit with using a slightly different XBUS allocation. No support for base unit version 5.0. Does not support EPS clear channel dynamic cross connections. Does not support the CIF port type (bit capacity) that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-Bus allocation. The XB port capacity up to 192x64kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Fallback list warning faults are shown.
Bugs
X-Connect RAM Fault does not disappear when the error condition causing it is over. When the fault remains active after the problem the switch over logic does not operate. To get rid of the unnecessary but rare fault the unit has to be reset. Flash system has a bug causing rare flash memory corruptions. The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. There is a possibility of an incomplete initialization in SXU. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This permanent error state looks like if the node has lost inventory. However the node parameters related to the inventory are neither lost nor changed. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. The whole bit connection capacity cannot be taken in use in SXU-A. NMS disaster recovery cannot be used. The real time clock can be used only in adaptive mode. The list of available ports for the master clock is not updated when the unit is removed from the inventory. PLL alarm does not affect the clock selection. Loss of external clock causes a switch over. A unit does not disappear from the list of available clock sources when the unit is removed from the inventory. If an external clock is the current clock source and the external clock input is broken, it is possible that the next clock is not correctly picked from the fallback list. If a unit belongs to node inventory but it is physically missing while the SXU is resetting, SXU may assume that the missing unit is still outputting usable clock signal. The port object allows setting CAS on for connected port if the following conditions are true: Data connection to CAS ts is created with xgroup ID and that ID is not active. After setting CAS on it is not possible to set it off or delete the connection.

272
10004_22 2008 Tellabs.
If both SXUs in a protected Basic Node experience an SW reset almost simultaneously, it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. The bug appears if all of the following happens simultaneously: a) data structures are corrupted (as just explained), b) the EXT clock is on the fallback list, c) EXT is chosen as the master clock of the node and d) EXT is in failed state. Under these circumstances, the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window. Removing a passive SXU in a protected node causes errors in traffic. The port object allows changing the even/uneven bus allocation parameter for the existing port. If there is only one channel unit in a protected node that has locked ports and the fault XConnection Bus Alarm is activated and the reason for that fault is not a problem in the active SXU (the problem cannot be solved by switching the active SXU), it may lead to continuous switching of active SXU. There is an about 4-second delay when changing the clock from internal to external clock. It is possible to change port parameters when the port is in swapped state. Swapped ports are expected to be equal. When the node master clock becomes faulty, SXU does not select the next best choice at once but there may be some intermediate states. The effect of this is a bit slower clock stabilization.
21.20 Version 5.8

Dependencies
Restrictions

Does not have the possibility for enhanced detection of RAM faults during a functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) Setting the signalling bit idle value is not supported. Slow cross-connect operations. Does not support the using of contradirectional synchronization clock sources in a protected ring network topology. No T1 support. No support for GMU. No support for improved and nearly hitless change over. Clock changes are not indicated in fault history.
10004_22 2008 Tellabs.

273
Does not support the improved external clock protection (switch over happens if the node starts using the internal clock and the passive SXU still has a valid external clock). Does not indicate synchronization source changes in fault history Does not support the CIF port type (octet capacity) that is used to fix a certain CIF ASIC bug in the interface unit with using a slightly different X-Bus allocation. No support for base unit version 5.0. Does not support EPS clear channel dynamic cross connections. Does not support the CIF port type (bit capacity) that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-Bus allocation. The XB port capacity up to 192x64kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Fallback list warning faults are shown.
Bugs
X-Connect RAM Fault does not disappear when the error condition causing it is over. When the fault remains active after the problem the switch over logic does not operate. To get rid of the unnecessary but rare fault the unit has to be reset. Flash system has a bug causing rare flash memory corruptions. The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. There is a possibility of an incomplete initialization in SXU. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This permanent error state looks like if the node has lost inventory. However the node parameters related to the inventory are neither lost nor changed. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. The whole bit connection capacity cannot be taken in use in SXU-A. NMS disaster recovery cannot be used. Real time clock can be used only in adaptive mode. The list of available ports for the master clock is not updated when the unit is removed from the inventory. PLL alarm does not affect the clock selection. Loss of external clock causes a switch over. A unit does not disappear from the list of available clock sources when the unit is removed from the inventory. If an external clock is the current clock source and the external clock input is broken, it is possible that the next clock is not correctly picked from the fallback list. If a unit belongs to the node inventory but it is physically missing while the SXU is resetting, SXU may assume that the missing unit is still outputting usable clock signal.

274
10004_22 2008 Tellabs.
The port object allows setting CAS on for connected port if the following conditions are true: Data connection to CAS ts is created with xgroup ID and that ID is not active. After setting CAS on it is not possible to set it off or delete the connection. If both SXUs in a protected Basic Node experience an SW reset almost simultaneously, it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. The bug appears if all of the following happens simultaneously: a) data structures are corrupted (as just explained), b) the EXT clock is on the fallback list, c) EXT is chosen as the master clock of the node and d) EXT is in failed state. Under these circumstances, the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window. Removing a passive SXU in a protected node causes errors in traffic. The port object allows changing the even/uneven bus allocation parameter for the existing port. If there is only one channel unit in a protected node that has locked ports and the fault XConnection Bus Alarm is activated and the reason for that fault is not a problem in the active SXU (the problem cannot be solved by switching the active SXU), it may lead to continuous switching of the active SXU. There is an about 4-second delay when changing the clock from internal to external clock. It is possible to change port parameters when the port is in swapped state. Swapped ports are expected to be equal. When the node master clock becomes faulty, SXU does not select the next best choice at once but there may be some intermediate states. The effect of this is a bit slower clock stabilization.
21.21 Version 5.7

Dependencies
Restrictions

Does not have the possibility for enhanced detection of RAM faults during a functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) Setting the signalling bit idle value is not supported. Slow cross-connect operations. Does not support using of contradirectional synchronisation clock sources in a protected ring network topology. No T1 support. No support for GMU.
10004_22 2008 Tellabs.

275
No support for improved and nearly hitless change over. Clock changes are not indicated in fault history. Does not support the improved external clock protection (switch over happens if a node starts using the internal clock and the passive SXU still has a valid external clock). Does not indicate synchronization source changes in fault history Does not support the CIF port type (octet capacity) that is used to fix a certain CIF ASIC bug in the interface unit with using a slightly different XBUS allocation. No support for base unit version 5.0. Does not support EPS clear channel dynamic cross-connections. Does not support the CIF port type (bit capacity) that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-Bus allocation. The XB port capacity up to 192x64kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Fallback list warning faults are shown.
Bugs
X-Connect RAM Fault does not disappear when the error condition causing it is over. When the fault remains active after the problem the switch over logic does not operate. To get rid of the unnecessary but rare fault the unit has to be reset. Flash system has a bug causing rare flash memory corruptions. The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. There is a possibility of an incomplete initialization in SXU. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This permanent error state looks like if the node has lost inventory. However the node parameters related to the inventory are neither lost nor changed. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. The whole bit connection capacity cannot be taken in use in SXU-A. NMS disaster recovery cannot be used. The real time clock can be used only in adaptive mode. The list of available ports for the master clock is not updated when the unit is removed from the inventory. PLL alarm does not affect the clock selection. Loss of external clock causes a switch over. A unit does not disappear from the list of available clock sources when the unit is removed from the inventory. If an external clock is the current clock source and the external clock input is broken, it is possible that the next clock is not correctly picked from the fallback list.

276
10004_22 2008 Tellabs.
If a unit belongs to the node inventory but it is physically missing while the SXU is resetting, SXU may assume that the missing unit is still outputting usable clock signal. The port object allows setting CAS on for connected port if the following conditions are true: Data connection to CAS ts is created with xgroup ID and that ID is not active. After setting CAS on it is not possible to set it off or delete the connection. If both SXUs in a protected Basic Node experience an SW reset almost simultaneously, it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. The bug appears if all of the following happens simultaneously: a) data structures are corrupted (as just explained), b) the EXT clock is on the fallback list, c) EXT is chosen as the master clock of the node and d) EXT is in failed state. Under these circumstances, the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window. Removing a passive SXU in a protected node causes errors in traffic. The port object allows changing the even/uneven bus allocation parameter for the existing port. If there is only one channel unit in a protected node that has locked ports and the fault XConnection Bus Alarm is activated and the reason for that fault is not a problem in the active SXU (the problem cannot be solved by switching the active SXU), it may lead to continuous switching of the active SXU. There is an about 4-second delay when changing the clock from internal to external clock. It is possible to change port parameters when the port is in swapped state. Swapped ports are expected to be equal. When the node master clock becomes faulty, SXU does not select the next best choice at once but there may be some intermediate states. The effect of this is a bit slower clock stabilization.
21.22 Version 5.6

Dependencies
Restrictions

Does not have the possibility for enhanced detection of RAM faults during a functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) Does not support EPS clear channel dynamic cross-connections. Does not support the CIF port type (bit capacity) that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-Bus allocation. Setting the signalling bit idle value is not supported.
10004_22 2008 Tellabs.

277
Slow cross-connect operations. CAE unit is not supported. Does not support using of contradirectional synchronization clock sources in a protected ring network topology. No T1 support. No support for GMU. No support for improved and nearly hitless change over. Clock changes are not indicated in fault history. Does not support the improved external clock protection (switch over happens if the node starts using internal clock and the passive SXU still has a valid external clock). Does not indicate synchronization source changes in fault history Does not support the CIF port type (octet capacity) that is used to fix a certain CIF ASIC bug in the interface unit with using a slightly different X-Bus allocation. No support for base unit version 5.0. The XB port capacity up to 192x64kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Fallback list warning faults are shown.
Bugs
X-Connect RAM Fault does not disappear when the error condition causing it is over. When the fault remains active after the problem the switch over logic does not operate. To get rid of the unnecessary but rare fault the unit has to be reset. Flash system has a bug causing rare flash memory corruptions. The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. There is a possibility of an incomplete initialization in SXU. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This permanent error state looks like if the node has lost inventory. However the node parameters related to the inventory are neither lost nor changed. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. The whole bit connection capacity cannot be taken in use in SXU-A. NMS disaster recovery cannot be used. The real time clock can be used only in adaptive mode. The list of available ports for the master clock is not updated when the unit is removed from the inventory. PLL alarm does not affect the clock selection. Loss of external clock causes switch over.

278
10004_22 2008 Tellabs.
A unit does not disappear from the list of available clock sources when the unit is removed from the inventory. If an external clock is the current clock source and the external clock input is broken, it is possible that the next clock is not correctly picked from the fallback list. If a unit belongs to the node inventory but it is physically missing while the SXU is resetting, SXU may assume that the missing unit is still outputting usable clock signal. The port object allows setting CAS on for connected port if the following conditions are true: Data connection to CAS ts is created with xgroup ID and that ID is not active. After setting CAS on it is not possible to set it off or delete the connection. If both SXUs in a protected Basic Node experience an SW reset almost simultaneously, it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. The bug appears if all of the following happens simultaneously: a) data structures are corrupted (as just explained), b) the EXT clock is on the fallback list, c) EXT is chosen as the master clock of the node and d) EXT is in failed state. Under these circumstances, the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window. Removing a passive SXU in a protected node causes errors in traffic. The port object allows changing even/uneven bus allocation parameter for existing port. If there is only one channel unit in a protected node that has locked ports and the fault XConnection Bus Alarm is activated and the reason for that fault is not a problem in the active SXU (the problem cannot be solved by switching the active SXU), it may lead to continuous switching of the active SXU. There is an about 4-second delay when changing the clock from internal to external clock. It is possible to change port parameters when the port is in swapped state. Swapped ports are expected to be equal. When the node master clock becomes faulty SXU does not select the next best choice at once but there may be some intermediate states. The effect of this is a bit slower clock stabilization.
21.23 Version 5.5

Dependencies
Restrictions

Does not have the possibility for enhanced detection of RAM faults during a functional test. (CR ID 300038625) Does not support the Reconfiguring X-connect database fault state saving in flash to prevent the possibility of X-connect database corruption in the rare case of simultaneous reset of both SXUs in a protected node. (CR ID 200033778) Does not support the improved check of incoming message integrity. (CR ID 200033949) Setting the signalling bit idle value is not supported.
10004_22 2008 Tellabs.

279
Slow cross-connect operations. CAE unit is not supported. Does not support the using of contradirectional synchronization clock sources in a protected ring network topology. No T1 support. No support for GMU. No support for improved and nearly hitless change over. Clock changes are not indicated in fault history. Does not support the improved external clock protection (switch over happens if the node starts using the internal clock and the passive SXU still has a valid external clock). Does not indicate synchronization source changes in fault history Does not support the CIF port type (octet capacity) that is used to fix a certain CIF ASIC bug in the interface unit with using a slightly different X-Bus allocation. No support for base unit version 5.0. Does not support EPS clear channel dynamic cross connections. Does not support the CIF port type (bit capacity) that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-Bus allocation. The XB port capacity up to 192x64kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Fallback list warning faults are shown.
Bugs
X-Connect RAM Fault does not disappear when the error condition causing it is over. When the fault remains active after the problem the switch over logic does not operate. To get rid of the unnecessary but rare fault the unit has to be reset. Flash system has a bug causing rare flash memory corruptions. The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. There is a possibility of an incomplete initialization in SXU. This error can happen if all the existing server or interface units in the node have long power up times (e.g. ESU, FRU, AIU), if SXU is not protected, if SCU-H is used and if the whole node is reset (e.g. after power failure). This permanent error state looks like if the node has lost inventory. However the node parameters related to the inventory are neither lost nor changed. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. The real time clock cannot be used. The whole bit connection capacity cannot be taken in use in SXU-A. Time controlled circuits do not work. NMS disaster recovery cannot be used. The real time clock can be used only in adaptive mode.

280
10004_22 2008 Tellabs.
The list of available ports for the master clock is not updated when the unit is removed from inventory. PLL alarm does not affect the clock selection. Loss of external clock causes a switch over. A unit does not disappear from the list of available clock sources when the unit is removed from the inventory. If an external clock is the current clock source and the external clock input is broken, it is possible that the next clock is not correctly picked from the fallback list. If a unit belongs to node inventory but it is physically missing while the SXU is resetting, SXU may assume that the missing unit is still outputting usable clock signal. The port object allows setting CAS on for connected port if the following conditions are true: Data connection to CAS ts is created with xgroup ID and that ID is not active. After setting CAS on it is not possible to set it off or delete the connection. If both SXUs in a protected Basic Node experience an SW reset almost simultaneously, it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. The bug appears if all of the following happens simultaneously: a) data structures are corrupted (as just explained), b) the EXT clock is on the fallback list, c) EXT is chosen as the master clock of the node and d) EXT is in failed state. Under these circumstances, the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window. Removing a passive SXU in a protected node causes errors in traffic. The port object allows changing the even/uneven bus allocation parameter for the existing port. If there is only one channel unit in a protected node that has locked ports and the fault XConnection Bus Alarm is activated and the reason for that fault is not a problem in the active SXU (the problem cannot be solved by switching the active SXU), it may lead to continuous switching of the active SXU. There is an about 4-second delay when changing the clock from internal to external clock. It is possible to change port parameters when the port is in swapped state. Swapped ports are expected to be equal. When the node master clock becomes faulty, SXU does not select the next best choice at once but there may be some intermediate states. The effect of this is a bit slower clock stabilization.
10004_22 2008 Tellabs.

281
SXU-C Unit: SXZ289 Unit Software
22 SXU-C Unit: SXZ289 Unit Software

The unit software SXZ289 is used on the cross-connection unit SXU-C in Cluster slave subracks.
22.1 Version 10.2

Dependencies
SCU-H (SCZ545) software version must be 1.11 or higher to support cluster node. In earlier versions the cluster VTP clock parameter, if not set correctly, may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly. This happens for example if SCU is changed to SCU-H unit in a slave. SXU-C base unit SXU212 version must be 5.0. If priority bumping is used, MartisDXX NMS release must be 9.0B-12 or later.
Restrictions
No restrictions.
Bugs
No known bugs.
22.2 Version 10.1

This is an unofficial version almost equal to version 10.0. The only difference is that the interface lock/unlock operation bug described for version 10.0 is fixed. This version should not be used once the next official version is available.

282
10004_22 2008 Tellabs.
22.3 Version 10.0

Dependencies
SCU-H (SCZ545) software version must be 1.11 or higher to support cluster node. In earlier versions the cluster VTP clock parameter, if not set correctly, may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly. This happens for example if SCU is changed to SCU-H unit in a slave. SXU-C base unit SXU212 version must be 5.0. If priority bumping is used, MartisDXX NMS release must be 9.0B-12 or later.
Restrictions

Does not support indication of wrong intersubrack cable installation in fault history. Both SXU-C and CXU-M must support this feature before fault indication can be expected. Does not support background monitoring and fixing of the possible inconsistencies in SXU-C cross-connect memory (ARAM).
Bugs
Channel unit interface lock or unlock may cause communication deadlock state in SXU-C leading eventually to unit reset. After reset the unit operates without problems. This problem however is very improbable. The problem concerns only version 10.0.
22.4 Version 2.13

The problem with node traffic going down when Secondary SXU-C is active and SCU is pulled out from slave subrack is fixed. (cq200006418).
Dependencies
SCU-H (SCZ545) software version must be 1.11 or higher to support cluster node. In earlier versions the cluster VTP clock parameter, if not set correctly, may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly. This happens for example if SCU is changed to SCU-H unit in a slave. SXU-C base unit SXU212 version must be lower than 5.0. If priority bumping is used MartisDXX NMS version must be 9.0B-12 or later.
Restrictions
No restrictions
Bugs
No known bugs.
10004_22 2008 Tellabs.

283
22.5 Version 2.12

Dependencies
SCU-H (SCZ545) software version must be 1.11 or higher to support cluster node. In earlier versions the cluster VTP clock parameter, if not set correctly, may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly. This happens for example if SCU is changed to SCU-H unit in a slave. SXU-C base unit SXU212 version must be lower than 5.0. If priority bumping is used MartisDXX NMS version must be 9.0B-12 or later.
Restrictions
No restrictions
Bugs
Traffic is down when Secondary SXU-C is active and SCU is pulled out from slave subrack.
22.6 Version 2.11

Dependencies
SCU-H (SCZ545) software version must be 1.11 or higher to support cluster node. In earlier versions the cluster VTP clock parameter, if not set correctly, may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly. This happens for example if SCU is changed to SCU-H unit in a slave. SXU-C base unit SXU212 version must be lower than 5.0. If priority bumping is used, MartisDXX NMS release must be 9.0B-12 or later.
Restrictions

Bugs
No known bugs.

284
10004_22 2008 Tellabs.
22.7 Version 2.10

Dependencies
SCU-H (SCZ545) software version must be 1.11 or higher to support cluster node. In earlier versions the cluster VTP clock parameter, if not set correctly, may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly. This happens for example if SCU is changed to SCU-H unit in a slave. SXU-C base unit SXU212 version must be lower than 5.0. If priority bumping is used, MartisDXX NMS release must be 9.0B-12 or later.
Restrictions

Bugs
Port operations (channel unit interface lock or unlock) may cause deadlock state in SXU-C leading eventually to unit reset. After reset the unit operates without problems. This behaviour however is very improbable. The problem concerns only version 2.10.
22.8 Version 2.9

This is an unofficial version almost equal to version 2.10. The only difference is that the X-bus consistency fault is incorrectly activated when any channel unit has more than 30 port descriptors. This version should not be used once the official version 2.10 is available.
22.9 Version 2.8

This is an unofficial version based on SXZ289 version 2.7 with only the CIF port type support modification. This version should not be used once the official version 2.10 is available.
10004_22 2008 Tellabs.

285
22.10 Version 2.7

Dependencies
SCU-H (SCZ545) software version must be 1.11 or higher to support cluster node. In earlier versions the cluster VTP clock parameter, if not set correctly, may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly. This happens for example if SCU is changed to SCU-H unit in a slave. SXU-C base unit SXU212 version must be lower than 5.0.
Restrictions

Does not support the CIF port type that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-bus allocation. Does not support indication of wrong intersubrack cable installation in fault history. Both SXU-C and CXU-M must support this feature before fault indication can be expected. Does not support background monitoring and fixing of the possible inconsistencies in SXU-C cross-connect memory (ARAM).
Bugs
The combined swap and passivation state of trunks does not operate properly and it may lead to problems in connections and thus it must not be used (NMS priority bumping feature). Allows CAS ON modification to connected port descriptor which causes conflict. Removing the passive SXU-C from the node may cause short errors in traffic. When using ports with CAS and octet capacity more than 2M but less than 8M, the port modify operation (enable or disable CAS) uses a wrong rule for the change which may lead to X-bus allocation integrity problem. There is a problem with error handling when it is tried to connect 8M port TS that does not have CAS capacity with CAS and CAS is only partly enabled in the port descriptor. The result is that the XB resource is reserved and remains reserved after error return from object and the new XB connection for that TS is not possible until the port has been unlocked and locked again. When a GMU unit is added to inventory or removed from inventory, there is a small probability that X-bus allocation is corrupted. This happens as during the inventory operations there are two simultaneous and mutually unprotected sources of allocation changes. It is possible to affect the port even/uneven parameter in port object M-SET operation. This may lead to data errors if the channel unit still believes the port to be even. This may also lead to X-bus integrity problems when a port modified in this way is connected or disconnected. If there is only one unit in the subrack and there is some reason causing an IA fault, this leads to a state where the node changes the active side continuously which disturbs the traffic seriously. It is possible to modify parameters of a swapped trunk.

286
10004_22 2008 Tellabs.
The cross-connections created by range format cannot be initialised due to an error in the cross-connect object. CXU-M will never leave the init state of the slave containing those connections. Swapped trunk initialise may send a wrong port descriptor to the channel unit (the channel unit may start using a wrong IA number) when the active SXU-C is reset. This can cause continuous traffic errors in the node.
22.11 Version 2.6

Dependencies
Restrictions

No support for GMU. Does not support the CIF port type that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-bus allocation. Does not support indication of wrong intersubrack cable installation in fault history. Both SXU-C and CXU-M must support this feature before fault indication can be expected. Does not support background monitoring and fixing of the possible inconsistencies in SXU-C cross-connect memory (ARAM).
Bugs

The combined swap and passivation state of trunks does not operate properly and it may lead to problems in connections and thus must not be used (NMS priority bumping feature). A unit does not disappear from the list of available clock sources when the unit is removed from the inventory. Allows CAS ON modification to connected port descriptor which causes conflict. Removing the passive SXU-C from the node may cause short errors in traffic. There is a problem with error handling when it is tried to connect 8M port TS that does not have CAS capacity with CAS and CAS is only partly enabled in the port descriptor. The result is that the XB resource is reserved and remains reserved after error return from object and the new XB connection for that TS is not possible until the port has been unlocked and locked again. It is possible to affect the port even/uneven parameter in port object M-SET operation. This may lead to data errors if the channel unit still believes the port to be even. This may also lead to X-bus integrity problems when a port modified this way is connected or disconnected.
10004_22 2008 Tellabs.

287
If there is only one unit in the subrack and there is some reason causing an IA fault, this leads to a state where the node changes the active side continuously which disturbs the traffic seriously. It is possible to modify parameters of a swapped trunk. The cross-connections created by range format cannot be initialised due to an error in the cross-connect object. CXU-M will never leave the init state of the slave containing those connections. Swapped trunk initialise may send a wrong port descriptor to the channel unit (the channel unit may start using a wrong IA number) when the active SXU-C is reset. This can cause continuous traffic errors in the node.
22.12 Version 2.5

Dependencies
Restrictions

No T1 support. No support for GMU. Does not support the CIF port type that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-bus allocation. Does not support indication of wrong intersubrack cable installation in fault history. Both SXU-C and CXU-M must support this feature before fault indication can be expected. Does not support background monitoring and fixing of the possible inconsistencies in SXU-C cross-connect memory (ARAM).
Bugs

The combined swap and passivation state of trunks does not operate properly and it may lead to problems in connections and thus must not be used (NMS priority bumping feature). A unit does not disappear from the list of available clock sources when the unit is removed from inventory. Allows CAS ON modification to connected port descriptor which causes conflict. Removing the passive SXU-C from the node may cause short errors in traffic. There is a problem with error handling when it is tried to connect 8M port TS that does not have CAS capacity with CAS and CAS is only partly enabled in the port descriptor. The result is that the XB resource is reserved and remains reserved after error return from object and the new XB connection for that TS is not possible until the port has been unlocked and locked again.

288
10004_22 2008 Tellabs.
It is possible to affect the port even/uneven parameter in port object M-SET operation. This may lead to data errors if the channel unit still believes the port to be even. This may also lead to X-bus integrity problems when a port modified this way is connected or disconnected. If there is only one unit in the subrack and there is some reason causing an IA fault, this leads to a state where the node changes the active side continuously which disturbs the traffic seriously. It is possible to modify parameters of a swapped trunk. The cross-connections created by range format cannot be initialised due to an error in the cross-connect object. CXU-M will never leave the init state of the slave containing those connections. Swapped trunk initialise may send a wrong port descriptor to the channel unit (the channel unit may start using a wrong IA number) when the active SXU-C is reset. This can cause continuous traffic errors in the node.
22.13 Version 2.4

Dependencies
Restrictions

No T1 support. Does not support contradirectional synchronisation clock sources in protected ring network topology. No support for GMU. Does not support the CIF port type that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-bus allocation. Does not support indication of wrong intersubrack cable installation in fault history. Both SXU-C and CXU-M must support this feature before fault indication can be expected. Does not support background monitoring and fixing of the possible inconsistencies in SXU-C cross-connect memory (ARAM).
10004_22 2008 Tellabs.

289
Bugs

The combined swap and passivation state of trunks does not operate properly and it may lead to problems in connections and thus must not be used (NMS priority bumping feature). A unit does not disappear from the list of available clock sources when the unit is removed from inventory. Allows CAS ON modification to connected port descriptor which causes conflict. Removing the passive SXU-C from the node may cause short errors in traffic. There is a problem with error handling when it is tried to connect 8M port TS that does not have CAS capacity with CAS and CAS is only partly enabled in the port descriptor. The result is that the XB resource is reserved and remains reserved after error return from object and the new XB connection for that TS is not possible until the port has been unlocked and locked again. It is possible to affect the port even/uneven parameter in port object M-SET operation. This may lead to data errors if the channel unit still believes the port to be even. This may also lead to X-bus integrity problems when a port modified this way is connected or disconnected. If there is only one unit in the subrack and there is some reason causing an IA fault, this leads to a state where the node changes the active side continuously which disturbs the traffic seriously. It is possible to modify parameters of a swapped trunk. The cross-connections created by range format cannot be initialised due to an error in the cross-connect object. CXU-M will never leave the init state of the slave containing those connections. Swapped trunk initialise may send a wrong port descriptor to the channel unit (the channel unit may start using a wrong IA number) when the active SXU-C is reset. This can cause continuous traffic errors in the node.
22.14 Version 2.3

Dependencies
Restrictions

No T1 support. Does not support contradirectional synchronisation clock sources in protected ring network topology. No support for GMU.

290
10004_22 2008 Tellabs.
Does not support the CIF port type that is used to fix a certain CIF ASIC bug in the interface unit using a slightly different X-bus allocation. Does not support indication of wrong intersubrack cable installation in fault history. Both SXU-C and CXU-M must support this feature before fault indication can be expected. Does not support background monitoring and fixing of the possible inconsistencies in SXU-C cross-connect memory (ARAM).
Bugs

The combined swap and passivation state of trunks does not operate properly and it may lead to problems in connections and thus must not be used (NMS priority bumping feature). A unit does not disappear from the list of available clock sources when the unit is removed from inventory. Allows CAS ON modification to connected port descriptor which causes conflict. Removing the passive SXU-C from the node may cause short errors in traffic. There is a problem with error handling when it is tried to connect 8M port TS that does not have CAS capacity with CAS and CAS is only partly enabled in the port descriptor. The result is that the XB resource is reserved and remains reserved after error return from object and the new XB connection for that TS is not possible until the port has been unlocked and locked again. The real time clock can be used only in adaptive mode. Master clock 'clock acceptance time' can be set to any value between 0s...255s but should not be set to any value other than '0s'. It is possible to affect the port even/uneven parameter in port object M-SET operation. This may lead to data errors if the channel unit still believes the port to be even. This may also lead to X-bus integrity problems when a port modified this way is connected or disconnected. If there is only one unit in the subrack and there is some reason causing an IA fault, this leads to a state where the node changes the active side continuously which disturbs the traffic seriously. It is possible to modify parameters of a swapped trunk. The cross-connections created by range format cannot be initialised due to an error in the cross-connect object. CXU-M will never leave the init state of the slave containing those connections. Swapped trunk initialise may send a wrong port descriptor to the channel unit (the channel unit may start using a wrong IA number) when the active SXU-C is reset. This can cause continuous traffic errors in the node.
10004_22 2008 Tellabs.

291
Tellabs 8110 CTE-R and CTE-R/208 SHDSL NTU: SBZ674 Unit Software
23 Tellabs 8110 CTE-R and CTE-R/208 SHDSL NTU: SBZ674 Unit Software
The software SBZ674 is used on Tellabs 8110 CTE-R (CTE689) and CTE-R/208 (CTE807) units. The version 2.0 can be downloaded to units having the version 1.y or 2.y of SBZ674 (where y=0, 1, 2...).
23.1 Version 2.0


Support for ESHDSL line modes. (CR ID 300056275) Support for CTE-R/208 modem. (CR ID 300056275)
Dependencies

Tellabs 8110 CTE-R (CTE689) hardware version must be 1.0 or higher. Tellabs 8110 CTE-R/208 (CTE807) hardware version must be 1.0 or higher. Tellabs 8110 CTE-R (DPZ653) DSP software version must be 1.3 or higher when used with CTE-R. New ESHDSL line modes are available at version 3.0 or higher. Tellabs 8110 CTE-R (DPZ653) DSP software version must be 3.0 or higher when used with CTE-R/208. Tellabs 8110 CTE-R (SBZ670) router software version must be 3.0 or higher. OMH (OMZ675) software version must be 1.2 or higher to support SCO module. OMH (OMZ675) software version must be 3.0 or higher to support new ESHDSL line modes. SCO module version must be 4.0 or higher to support ESHDSL line modes. ESU (EMZ642) software version must be 1.0 or higher. Tellabs 8100 network manager support for CTE-R unit is available in Release 13A Service Pack 1 or higher. Tellabs 8000 network manager support for CTE-R/208 unit is available in Release 15A or higher.
Restrictions

CTE-R/208 can not be used with ESU. Neighbor node loop does not work with 1x208k and 2x208k line modes.

292
10004_22 2008 Tellabs.
Tellabs 8110 CTE-R and CTE-R/208 SHDSL NTU: SBZ674 Unit Software
Bugs
No known bugs.
23.2 Version 1.0

Dependencies

Tellabs 8110 CTE-R (CTE689) hardware version must be 1.0 or higher. Tellabs 8110 CTE-R (DPZ653) DSP software version must be 1.3 or higher. Tellabs 8110 CTE-R (SBZ670) router software version must be 3.0 or higher. OMH (OMZ675) software version must be 1.2 or higher to support SCO module. ESU (EMZ642) software version must be 1.0 or higher. Tellabs 8100 manager support for this unit is available in Release 13A Service Pack 1 or higher.
Restrictions
Version 1.0 of SBZ674 can not be used with CTE-R/208 modem.
Bugs
No known bugs.
10004_22 2008 Tellabs.

293
Tellabs 8110 CTE-S, CTE-S/208, CTE-R and CTE-R/208 SHDSL NTU: DPZ653 DSP Software
24 Tellabs 8110 CTE-S, CTE-S/208, CTE-R and CTE-R/208 SHDSL NTU: DPZ653 DSP Software
The software DPZ653 is used on Tellabs 8110 CTE-S V.35 (CTE685), CTE-S V.36 (CTE688), CTE-S X.21 (CTE686), CTE-R (CTE689), CTE-S/208 V.35 (CTE803), CTE-S/208 V.36 (CTE806), CTE-S/208 X.21 (CTE804) and CTE-R/208 (CTE807) units. The version 3.3 can be downloaded to CTE-S units having the version 3.y and 2.y of DPZ653 (where y=0, 1, 2...) Version 3.0 can also be downloaded to units having the version 1.x of DPZ653 but then point-to-point operation is not available. The version 3.0 can be downloaded to CTE-S/208 units having the version 3.y of DPZ653 (where y=0, 1, 2...).
24.1 Version 3.3


Support for ESHDSL line modes. (CR ID 300056272) Support for CTE-S/208 modems. (CR ID 300056272)
Dependencies

Tellabs 8110 CTE-S hardware version must be 2.0 or higher. Tellabs 8110 CTE-S/208 hardware version must be 2.0 or higher. Tellabs 8110 CTE-R (CTE689) hardware version must be 1.0 or higher. Tellabs 8110 CTE-R/208 (CTE807) hardware version must be 1.0 or higher. USW software (SBZ673) for Tellabs 8110 CTE CTE-S V.35 (CTE685), CTE-S V.36 (CTE688), CTE-S X.21 (CTE686), CTE-R (CTE689) units must be version 2.0 or higher. USW software (SBZ673) for Tellabs 8110 CTE-S/208 V.35, CTE-S/208 V.36 and CTES/208 X.21 must be version 3.0 or higher. OMH (OMZ675) software version must be 1.2 or higher to support SCO module. OMH (OMZ675) software version must be 3.0 or higher to support ESHDSL line modes. SCO module version must be 4.0 or higher to support ESHDSL line modes Tellabs 8100 network manager support for CTE-S units is available in Release 13 or higher.

294
10004_22 2008 Tellabs.
Tellabs 8000 network manager support for CTE-S/208 unit is available in Release 15A or higher.
Restrictions

Neighbor node loop does not work with 1x208k and 2x208k line modes. In case of two-pair mode, when one line is without attenuation and there is attenuation in the other line, "power back-off" may be ON or may be OFF for both lines. This version can be used with HW version 1.x and unit SW version 1.x but in that case point-to-point operation is not supported. USW software (SBZ673) for Tellabs 8110 CTE CTE-S V.35 (CTE685), CTE-S V.36 (CTE688), CTE-S X.21 (CTE686), CTE-R (CTE689) units below version 3.0 does not support ESHDSL modes.
Bugs
No known bugs.
24.2 Version 2.0

Point to point feature for CTE-S. (CR ID 200013029)
Dependencies

Tellabs 8110 CTE-S hardware version must be 2.0 or higher. Tellabs 8110 CTE-R hardware version must be 1.0 or higher. OMH (OMZ675) software version must be 1.2 or higher to support SCO module. USW software (SBZ673) for Tellabs 8110 CTE-S V.35, CTE-S V.36 and CTE-S X.21 must be version 1.0 or higher. Tellabs 8100 manager support for this unit is available in Release 13 or higher.
Restrictions

In case of two-pair mode, when one line is without attenuation and there is attenuation in the other line, "power back-off" may be ON or may be OFF for both lines. This version can be used with HW version 1.x and unit SW version 1.x but in that case point-to-point operation is not supported.
Bugs
No known bugs.
10004_22 2008 Tellabs.

295
24.3 Version 1.3

Dependencies

Tellabs 8110 CTE-S hardware version must be 1.0. Tellabs 8110 CTE-R (CTE689) hardware version must be 1.0 or higher. OMH (OMZ675) software version must be 1.2 or higher to support SCO module. USW software (SBZ673) for Tellabs 8110 CTE-S V.35, CTE-S V.36 and CTE-S X.21 must be version 1.0 or higher. Tellabs 8100 manager support for this unit is available in Release 13 or higher.
Restrictions

Bugs
No known bugs.

296
10004_22 2008 Tellabs.
Tellabs 8110 CTE-S G.703 SHDSL NTU: DPZ654 DSP Software
25 Tellabs 8110 CTE-S G.703 SHDSL NTU: DPZ654 DSP Software

The software DPZ654 is used on Tellabs 8110 CTE-S G.703 (CTE687) and CTE-S/208 G.703 (CTE805) units. The version 3.3 can be downloaded to CTE-S units having the version 3.y and 2.y of DPZ654 (where y=0, 1, 2...) Version 3.3 can also be downloaded to units having the version 1.x of DPZ654 but then point-to-point operation is not available. The version 3.3 can be downloaded to CTE-S/208 units having the version 3.y of DPZ654 (where y=0, 1, 2...).
25.1 Version 3.3


Support for ESHDSL line modes. (CR ID 300056272) Support for CTE-S/208 G.703 (CTE805) modems. (CR ID 300056272)
Dependencies

Tellabs 8110 CTE-S hardware version must be 2.0 or higher. Tellabs 8110 CTE-S/208 hardware version must be 2.0 or higher. USW software (SBZ673) for Tellabs 8110 CTE-S G.703 (CTE687) unit must be version 2.0 or higher. USW software (SBZ673) for Tellabs 8110 CTE-S/208 G.703 (CTE805) units must be version 3.0 or higher. OMH (OMZ675) software version must be 1.2 or higher to support SCO module. OMH (OMZ675) software version must be 3.0 or higher to support ESHDSL line modes. SCO module version must be 4.0 or higher to support ESHDSL line modes Tellabs 8100 network manager support for CTE-S units is available in Release 13 or higher. Tellabs 8000 network manager support for CTE-S/208 unit is available in Release 15A or higher.
10004_22 2008 Tellabs.

297
Restrictions

Neighbor node loop does not work with 1x208k and 2x208k line modes. In case of two-pair mode, when one line is without attenuation and there is attenuation in the other line, "power back-off" may be ON or may be OFF for both lines. This version can be used with HW version 1.x and unit SW version 1.x but in that case point-to-point operation is not supported. USW software (SBZ673) for Tellabs 8110 CTE-S G.703 (CTE687) unit below version 3.0 does not support ESHDSL modes.
Bugs
No known bugs.
25.2 Version 2.0

Dependencies

Tellabs 8110 CTE-S hardware version must be 2.0 or higher. OMH (OMZ675) software version must be 1.2 or higher to support SCO module. USW software (SBZ673) for Tellabs 8110 CTE-S G.703 (CTE687) and CTE-S/208 G.703 (CTE805) units must be version 1.0 or higher. Tellabs 8100 manager support for this unit is available in Release 13 or higher.
Restrictions

Bugs
No known bugs.

298
10004_22 2008 Tellabs.
25.3 Version 1.3

Dependencies

Tellabs 8110 CTE-S hardware version must be 1.0. OMH (OMZ675) software version must be 1.2 or higher to support SCO module. USW software (SBZ673) for Tellabs 8110 CTE-S G.703 (CTE687) and CTE-S/208 G.703 (CTE805) units must be version 1.0 or higher. Tellabs 8100 manager support for this unit is available in Release 13 or higher.
Restrictions

Bugs
No known bugs.
10004_22 2008 Tellabs.

299
Tellabs 8110 CTE-S and CTE-S/208 SHDSL NTU: SBZ673 Unit Software
26 Tellabs 8110 CTE-S and CTE-S/208 SHDSL NTU: SBZ673 Unit Software
The software SBZ673 is used on Tellabs 8110 CTE-S V.35 (CTE685), CTE-S V.36 (CTE688), CTE-S X.21 (CTE686), CTE-S G.703 (CTE687), CTE-S/208 V.35 (CTE803), CTE-S/208 V.36 (CTE806), CTE-S/208 X.21 (CTE804) and CTE-S/208 G.703 (CTE805) units. The version 3.0 can be downloaded to CTE-S units having the version 3.y and 2.y of SBZ673 (where y=0, 1, 2...) Version 3.0 can also be downloaded to units having the version 1.x of SBZ673 but then point-to-point operation is not available. The version 3.0 can be downloaded to CTE-S/208 units having the version 3.y of SBZ673 (where y=0, 1, 2...).
26.1 Version 3.0


Support for ESHDSL line modes. (CR ID 300056272) Support for CTE-S/208 modems. (CR ID 300056272)
Dependencies

Tellabs 8110 CTE-S hardware version must be 2.0 or higher. Tellabs 8110 CTE-S/208 hardware version must be 2.0 or higher. DSP software (DPZ653) for Tellabs 8110 CTE-S V.35, CTE-S V.36 and CTE-S X.21 must be version 1.1 or higher. DSP software (DPZ653) for Tellabs 8110 CTE-S/208 V.35, CTE-S/208 V.36 and CTES/208 X.21 must be version 3.0 or higher. DSP software (DPZ654) for Tellabs 8110 CTE-S G.703 must be version 1.1 or higher. DSP software (DPZ654) for Tellabs 8110 CTE-S/208 G.703 must be version 3.0 or higher. OMH (OMZ675) software version must be 1.2 or higher to support SCO module. OMH (OMZ675) software version must be 3.0 or higher to support ESHDSL line modes. SCO module version must be 4.0 or higher to support ESHDSL line modes Tellabs 8100 network manager support for CTE-S units is available in Release 13 or higher. Tellabs 8000 network manager support for CTE-S/208 unit is available in Release 15A or higher.

300
10004_22 2008 Tellabs.
Restrictions
Neighbor node loop does not work with 1x208k and 2x208k line modes.
Bugs
No known bugs.
26.2 Version 2.0

Dependencies

Tellabs 8110 CTE-S hardware version must be 2.0 or higher. OMH (OMZ675) software version must be 1.2 or higher to support SCO module. DSP software (DPZ653) for Tellabs 8110 CTE-S V.35, CTE-S V.36 and CTE-S X.21 must be version 1.1 or higher. DSP software (DPZ654) for Tellabs 8110 CTE-S G.703 must be version 1.1 or higher. Tellabs 8100 manager support for this unit is available in Release 13 or higher.
Restrictions

DSP software (DPZ653) for Tellabs 8110 CTE-S V.35, CTE-S V.36 and CTE-S X.21 must be version 2.0 or higher if point-to-point feature is to be utilized. DSP software (DPZ654) for Tellabs 8110 CTE-S G.703 must be version 2.0 or higher if point-to-point feature is to be utilized. Version 2.0 of SBZ673 can not be used with CTE-S/208 modems.
Bugs
No known bugs.
10004_22 2008 Tellabs.

301
26.3 Version 1.0

Dependencies

Tellabs 8110 CTE-S hardware version must be 1.0. OMH (OMZ675) software version must be 1.2 or higher to support SCO module. DSP software (DPZ653) for Tellabs 8110 CTE-S V.35, CTE-S V.36 and CTE-S X.21 must be version 1.1 or higher. DSP software (DPZ654) for Tellabs 8110 CTE-S G.703 must be version 1.1 or higher. Tellabs 8100 manager support for this unit is available in Release 13 or higher.
Restrictions
Version 1.0 of SBZ673 can not be used with CTE-S/208 modems.
Bugs
No known bugs.

302
10004_22 2008 Tellabs.
Tellabs 8110 CTU-512 HDSL NTU: SBZ672 Unit Software
27 Tellabs 8110 CTU-512 HDSL NTU: SBZ672 Unit Software

The software SBZ672 is used in Tellabs 8110 CTU-512 V.35 (CTU680) and CTU-512 X.21 (CTU681) units. The version 3.0 can be downloaded to CTU-512 units having the version 3.y of SBZ672 (where y=0, 1, 2...).
27.1 Version 3.0

Support for AMIC flash. Enhancement. (CR ID 200025832)
Dependencies

CTU-512 hardware version must be 1.0 or higher. GMH (GMZ283) software version must be 10.0 or higher to support HCE-2M-1P and HCE-2M-2P modules. QMH (QMZ540) software version must be 10.5 or higher to support HCQ-2M module. MartisDXX Manager support for this unit is available in Release 12A or higher. Tellabs 8100 manager support for time dependent DTE capacity control is available in Release 14 or higher.
Restrictions
The End-to-End V.110/CRC feature (EECRC) is not fully compatible with HTU-2M (USW SBZ389 V1.0), and with STU-320, STU-576, STU-1088-2W and STU-2304 (USW SBZ387 V 1.2 or earlier). These units support only unidirectional EECRC, and therefore bidirectional EECRC in CTU-512 misinterprets path to be constantly UNAVAILABLE. CTU-512 hardware version must be 2.0 or higher if point-to-point feature is to be utilized.
Bugs
No known bugs.
10004_22 2008 Tellabs.

303
27.2 Version 2.1

CTU-512 uses wrong HW version bit mask when deciding is the HW capable of point-topoint operation. Bug. (CR ID 200025220)
Dependencies

Restrictions
Bugs
No known bugs.

304
10004_22 2008 Tellabs.
27.3 Version 2.0


Point-to-point feature for CTU-512. Enhancement. (CR ID 200013025) Possibility to change the DTE capacity depending on the time of day. Enhancement. (CR ID 200015080) CTU-512 sent 'G.826 performance event' alarms too early. As a result, Tellabs 8100 Network Manager read wrong counter values from CTU (current counter values were not moved to history table before reading took place). Now this bug is fixed. (CR ID 200005461)
Dependencies

Restrictions
Bugs
CTU-512 uses wrong HW version bit mask when deciding is the HW capable of point-topoint operation. Bug. (CR ID 200025220)
10004_22 2008 Tellabs.

305
27.4 Version 1.0

Dependencies

CTU-512 hardware version must be 1.0 or 1.1. GMH (GMZ283) software version must be 10.0 or higher to support HCE-2M-1P and HCE-2M-2P modules. QMH (QMZ540) software version must be 10.5 or higher to support HCQ-2M module. MartisDXX Manager support for this unit is available in Release 12A or higher.
Restrictions
The End-to-End V.110/CRC feature (EECRC) is not fully compatible with HTU-2M (USW SBZ389 V1.0), and with STU-320, STU-576, STU-1088-2W and STU-2304 (USW SBZ387 V 1.2 or earlier). These units support only unidirectional EECRC, and therefore bidirectional EECRC in CTU-512 misinterprets path to be constantly UNAVAILABLE.
Bugs
CTU-S sends 'G.826 performance event'-alarms too early. (CR ID 200005461)

306
10004_22 2008 Tellabs.
Tellabs 8110 CTU-R HDSL, Tellabs 8110 CTE-R SHDSL, Tellabs 8110 CTE-R/208 SHDSL and Tellabs 8110 STE-10M SHDSL NTUs: SBZ670 Unit Software
28 Tellabs 8110 CTU-R HDSL, Tellabs 8110 CTER SHDSL, Tellabs 8110 CTE-R/208 SHDSL and Tellabs 8110 STE-10M SHDSL NTUs: SBZ670 Unit Software
The software SBZ670 is used on Tellabs 8110 CTU-R (CTU399) and Tellabs 8110 CTE-R (CTE689) and Tellabs 8110 STE-10M (STE790) and Tellabs 8110 CTE-R/208 (CTE807) units. The version 4.4 can be downloaded to Tellabs 8110 CTU-R units having the version x.y of SBZ670 (where x is 1, 2, 3 or 4 and y=0, 1, 2...). If version before download was 1.y or 2.y (where y=0, 1, 2...) then factory default configuration is set. The version 4.4 can be downloaded to Tellabs 8110 CTE-R units having the version x.y of SBZ670 (where x is 3 or 4 and y=0, 1, 2...). The version 4.4 can be downloaded to Tellabs 8110 STE-10M units having the version 4.y of SBZ670 (where y=0, 1...). The version 4.4 can be downloaded to Tellabs 8110 CTE-R/208 units having the version 4.y of SBZ670 (where y=0, 1...). NOTE! No attempt should be made to download versions prior to 4.0 to Tellabs 8110 STE-10M.
28.1 Version 4.4

Frame Relay fragmentation. This is a new feature that enables short frames of real-time interactive applications to interrupt the transmissions of large frames that carry noninteractive traffic. (CR ID 300079019)
Dependencies

Tellabs 8110 CTU-R (CTU399) hardware version must be 2.0 or higher. Tellabs 8110 CTE-R (CTE689) hardware version must be 1.0 or higher. Tellabs 8110 STE-10M (STE790) hardware version must be 1.0 or higher. Tellabs 8110 CTE-R/208 (CTE807) hardware version must be 1.0 or higher. Tellabs 8110 CTU-R (SBZ671) unit software version must be 1.3 or higher.
10004_22 2008 Tellabs.

307
Tellabs 8110 CTE-R (SBZ674) unit software version must be 1.0 or higher when used with CTE-R and version 2.0 or higher when used with CTE-R/208. Tellabs 8110 CTE-R (DPZ653) data pump software version must be 1.3 or higher when used with CTE-R and version 3.0 or higher when used with CTE-R/208. Tellabs 8110 STE-10M (SBZ792) unit software version must be 1.0 or higher. Tellabs 8110 STE-10M (DPZ794) unit software version must be 1.0 or higher. MartisDXX Manager support for Tellabs 8110 CTU-R is available in Release 12 Service Pack 1 or higher. Tellabs 8100 manager support for Tellabs 8110 CTE-R is available in Release 13A Service Pack 1 or higher. MartisDXX Manager support for NAT, packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher. Tellabs 8100 manager support for enhanced ping, traceroute, logging, and LMI functionalities are available in Release 13 Service Pack 1 or higher. Tellabs 8100 manager support for DiffServ, bridge CoS, Ethernet/VLAN encapsulation on WAN side for routed traffic, VLAN filtering, tunnelling, VLAN ID mapping, background connectivity monitoring tool, OSPFv2 and IP routing table enlargement to 4000 routes are available in Release 13A Service Pack 1 or higher. Tellabs 8100 manager support for Tellabs 8110 STE-10M is available in Release 14 Service Pack 3 or higher. Tellabs 8100 manager support for Spanning Tree Transparency is available in Release 15 or higher. Tellabs 8000 network manager support for Tellabs 8110 CTE-R/208 is available in Release 15A or higher. Tellabs 8000 network manager support for Ethernet MAC/PHY link down alarm is available in Release 15B or higher. Older versions show it as Undefined error code with GPT 63 and SPT 90. Tellabs 8000 network manager support for Frame Relay fragmentation is available in Release 16 Service Pack 1 or higher.
Restrictions
If used MartisDXX Manager or Tellabs 8100 Manager or Tellabs 8000 manager Release is 12A, 13, 13A, 14 or 15 then Rule management, NAT management and Packet filtering menus are not accessible. The restriction has been fixed in Tellabs 8000 manager release R15-SP2.3 and R15A.
Bugs
No known bugs.

308
10004_22 2008 Tellabs.
28.2 Version 4.3


Ethernet MAC/PHY link down alarm is generated if Ethernet cable is unplugged. (CR ID 300036351) Pause frames were mistakenly forwarded when spanning tree transparency was enabled. (CR ID 300073486)
Dependencies

Tellabs 8110 CTU-R (CTU399) hardware version must be 2.0 or higher. Tellabs 8110 CTE-R (CTE689) hardware version must be 1.0 or higher. Tellabs 8110 STE-10M (STE790) hardware version must be 1.0 or higher. Tellabs 8110 CTE-R/208 (CTE807) hardware version must be 1.0 or higher. Tellabs 8110 CTU-R (SBZ671) unit software version must be 1.3 or higher. Tellabs 8110 CTE-R (SBZ674) unit software version must be 1.0 or higher when used with CTE-R and version 2.0 or higher when used with CTE-R/208. Tellabs 8110 CTE-R (DPZ653) data pump software version must be 1.3 or higher when used with CTE-R and version 3.0 or higher when used with CTE-R/208. Tellabs 8110 STE-10M (SBZ792) unit software version must be 1.0 or higher. Tellabs 8110 STE-10M (DPZ794) unit software version must be 1.0 or higher. MartisDXX Manager support for Tellabs 8110 CTU-R is available in Release 12 Service Pack 1 or higher. Tellabs 8100 manager support for Tellabs 8110 CTE-R is available in Release 13A Service Pack 1 or higher. MartisDXX Manager support for NAT, packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher. Tellabs 8100 manager support for enhanced ping, traceroute, logging, and LMI functionalities are available in Release 13 Service Pack 1 or higher. Tellabs 8100 manager support for DiffServ, bridge CoS, Ethernet/VLAN encapsulation on WAN side for routed traffic, VLAN filtering, tunnelling, VLAN ID mapping, background connectivity monitoring tool, OSPFv2 and IP routing table enlargement to 4000 routes are available in Release 13A Service Pack 1 or higher. Tellabs 8100 manager support for Tellabs 8110 STE-10M is available in Release 14 Service Pack 3 or higher. Tellabs 8100 manager support for Spanning Tree Transparency is available in Release 15 or higher. Tellabs 8000 network manager support for Tellabs 8110 CTE-R/208 is available in Release 15A or higher. Tellabs 8000 network manager support for Ethernet MAC/PHY link down alarm is available in Release 15B or higher. Older versions show it as Undefined error code with GPT 63 and SPT 90.
10004_22 2008 Tellabs.

309
Restrictions
Bugs
No known bugs.
28.3 Version 4.2

Traffic prioritization does not work correctly. In overload situations real time traffic does not get any higher priority than other traffic classes. (CR ID 300052014)
Dependencies

Tellabs 8110 CTU-R (CTU399) hardware version must be 2.0 or higher. Tellabs 8110 CTE-R (CTE689) hardware version must be 1.0 or higher. Tellabs 8110 STE-10M (STE790) hardware version must be 1.0 or higher. Tellabs 8110 CTE-R/208 (CTE807) hardware version must be 1.0 or higher. Tellabs 8110 CTU-R (SBZ671) unit software version must be 1.3 or higher. Tellabs 8110 CTE-R (SBZ674) unit software version must be 1.0 or higher when used with CTE-R and version 2.0 or higher when used with CTE-R/208. Tellabs 8110 CTE-R (DPZ653) data pump software version must be 1.3 or higher when used with CTE-R and version 3.0 or higher when used with CTE-R/208. Tellabs 8110 STE-10M (SBZ792) unit software version must be 1.0 or higher. Tellabs 8110 STE-10M (DPZ794) unit software version must be 1.0 or higher. MartisDXX Manager support for Tellabs 8110 CTU-R is available in Release 12 Service Pack 1 or higher. Tellabs 8100 manager support for Tellabs 8110 CTE-R is available in Release 13A Service Pack 1 or higher. MartisDXX Manager support for NAT, packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher. Tellabs 8100 manager support for enhanced ping, traceroute, logging, and LMI functionalities are available in Release 13 Service Pack 1 or higher. Tellabs 8100 manager support for DiffServ, bridge CoS, Ethernet/VLAN encapsulation on WAN side for routed traffic, VLAN filtering, tunnelling, VLAN ID mapping, background connectivity monitoring tool, OSPFv2 and IP routing table enlargement to 4000 routes are available in Release 13A Service Pack 1 or higher.

310
10004_22 2008 Tellabs.
Tellabs 8100 manager support for Tellabs 8110 STE-10M is available in Release 14 Service Pack 3 or higher. Tellabs 8100 manager support for Spanning Tree Transparency is available in Release 15 or higher. Tellabs 8000 network manager support for Tellabs 8110 CTE-R/208 is available in Release 15A or higher.
Restrictions
Bugs
Pause frames are mistakenly forwarded when spanning tree transparency is enabled. (CR ID 300073486).
28.4 Version 4.1

Spanning Tree Transparency. This is a new feature which enables transparent forwarding of customers bridge control protocol PDUs. (CR ID 300037420)
Dependencies

Tellabs 8110 CTU-R (CTU399) hardware version must be 2.0 or higher. Tellabs 8110 CTE-R (CTE689) hardware version must be 1.0 or higher. Tellabs 8110 STE-10M (STE790) hardware version must be 1.0 or higher. Tellabs 8110 CTE-R/208 (CTE807) hardware version must be 1.0 or higher. Tellabs 8110 CTU-R (SBZ671) unit software version must be 1.3 or higher. Tellabs 8110 CTE-R (SBZ674) unit software version must be 1.0 or higher when used with CTE-R and version 2.0 or higher when used with CTE-R/208. Tellabs 8110 CTE-R (DPZ653) data pump software version must be 1.3 or higher when used with CTE-R and version 3.0 or higher when used with CTE-R/208. Tellabs 8110 STE-10M (SBZ792) unit software version must be 1.0 or higher. Tellabs 8110 STE-10M (DPZ794) unit software version must be 1.0 or higher. MartisDXX Manager support for Tellabs 8110 CTU-R is available in Release 12 Service Pack 1 or higher. Tellabs 8100 manager support for Tellabs 8110 CTE-R is available in Release 13A Service Pack 1 or higher.
10004_22 2008 Tellabs.

311
MartisDXX Manager support for NAT, packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher. Tellabs 8100 manager support for enhanced ping, traceroute, logging, and LMI functionalities are available in Release 13 Service Pack 1 or higher. Tellabs 8100 manager support for DiffServ, bridge CoS, Ethernet/VLAN encapsulation on WAN side for routed traffic, VLAN filtering, tunnelling, VLAN ID mapping, background connectivity monitoring tool, OSPFv2 and IP routing table enlargement to 4000 routes are available in Release 13A Service Pack 1 or higher. Tellabs 8100 manager support for Tellabs 8110 STE-10M is available in Release 14 Service Pack 3 or higher. Tellabs 8100 manager support for Spanning Tree Transparency is available in Release 15 or higher. Tellabs 8000 network manager support for Tellabs 8110 CTE-R/208 is available in Release 15A or higher
Restrictions
Bugs

Traffic prioritization does not work correctly. In overload situations real time traffic does not get any higher priority than other traffic classes. (CR ID 300052014) Pause frames are mistakenly forwarded when spanning tree transparency is enabled. (CR ID 300073486).
28.5 Version 4.0


Support for Tellabs 8110 STE-10M. Rule management (ICMP) does not work correctly with Tellabs 8110 STE-10M, Tellabs 8110 CTU-R and Tellabs 8110 CTE-R. (CR ID 200035758)
Dependencies

Tellabs 8110 CTU-R (CTU399) hardware version must be 2.0 or higher. Tellabs 8110 CTE-R (CTE689) hardware version must be 1.0 or higher. Tellabs 8110 STE-10M (STE790) hardware version must be 1.0 or higher. Tellabs 8110 CTE-R/208 (CTE807) hardware version must be 1.0 or higher. Tellabs 8110 CTU-R (SBZ671) unit software version must be 1.3 or higher.

312
10004_22 2008 Tellabs.
Tellabs 8110 CTE-R (SBZ674) unit software version must be 1.0 or higher when used with CTE-R and version 2.0 or higher when used with CTE-R/208. Tellabs 8110 CTE-R (DPZ653) data pump software version must be 1.3 or higher when used with CTE-R and version 3.0 or higher when used with CTE-R/208. Tellabs 8110 STE-10M (SBZ792) unit software version must be 1.0 or higher. Tellabs 8110 STE-10M (DPZ794) unit software version must be 1.0 or higher. MartisDXX Manager support for Tellabs 8110 CTU-R is available in Release 12 Service Pack 1 or higher. Tellabs 8100 manager support for Tellabs 8110 CTE-R is available in Release 13A Service Pack 1 or higher. MartisDXX Manager support for NAT, packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher. Tellabs 8100 manager support for enhanced ping, traceroute, logging, and LMI functionalities are available in Release 13 Service Pack 1 or higher. Tellabs 8100 manager support for DiffServ, bridge CoS, Ethernet/VLAN encapsulation on WAN side for routed traffic, VLAN filtering, tunnelling, VLAN ID mapping, background connectivity monitoring tool, OSPFv2 and IP routing table enlargement to 4000 routes are available in Release 13A Service Pack 1 or higher. Tellabs 8100 manager support for Tellabs 8110 STE-10M is available in Release 14 Service Pack 3 or higher. Tellabs 8000 network manager support for Tellabs 8110 CTE-R/208 is available in Release 15A or higher.
Restrictions
Bugs
Traffic prioritization does not work correctly. In overload situations real time traffic does not get any higher priority than other traffic classes. (CR ID 300052014)
10004_22 2008 Tellabs.

313
28.6 Version 3.2


Enhancement: Buffer handling adjustment for better performance in bi-directional traffic flow tests (CR ID 200011373). Enhancement: MAC address may exist in multiple VLANs on the WAN side of CTUR/CTE-R (CR ID 200011413). Bug fix: Possible to set (OSPF) Router ID back to 0.0.0.0 (CR ID 200011433) Enhancement: Added N/A state to the background connectivity monitoring tool in order to achive similar behaviour to ESU.
Dependencies

Tellabs 8110 CTU-R (CTU399) hardware version must be 2.0 or higher. Tellabs 8110 CTE-R (CTE689) hardware version must be 1.0 or higher. Tellabs 8110 CTU-R (SBZ671) software version must be 1.3 or higher. Tellabs 8110 CTE-R (SBZ674) software version must be 1.0 or higher. Tellabs 8110 CTE-R (DPZ653) data pump software version must be 1.3 or higher. MartisDXX Manager support for Tellabs 8110 CTU-R is available in Release 12 Service Pack 1 or higher. Tellabs 8100 manager support for Tellabs 8110 CTE-R is available in Release 13A Service Pack 1 or higher. MartisDXX Manager support for NAT, packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher. Tellabs 8100 manager support for enhanced ping, traceroute, logging, and LMI functionalities are available in Release 13 Service Pack 1 or higher. Tellabs 8100 manager support for DiffServ, bridge CoS, Ethernet/VLAN encapsulation on WAN side for routed traffic, VLAN filtering, tunnelling, VLAN ID mapping, background connectivity monitoring tool, OSPFv2 and IP routing table enlargement to 4000 routes are available in Release 13A Service Pack 1 or higher.
Restrictions
This version should NOT be downloaded to STE-10M.
Bugs
Rule management (ICMP) does not work correctly with Tellabs 8110 STE-10M, Tellabs 8110 CTU-R and Tellabs 8110 CTE-R. (CR ID 200035758)

314
10004_22 2008 Tellabs.
28.7 Version 3.1

28.8 Version 3.0


Differentiated Services (DiffServ) and bridge CoS OSPFv2 Ethernet/VLAN encapsulation on WAN side for routed traffic VLAN filtering, tunnelling and VLAN ID mapping Background connectivity monitoring tool IP routing table enlargement to 4000 routes
Dependencies

Tellabs 8110 CTU-R (CTU399) hardware version must be 2.0 or higher. Tellabs 8110 CTE-R (CTE689) hardware version must be 1.0 or higher. Tellabs 8110 CTU-R (SBZ671) software version must be 1.3 or higher. Tellabs 8110 CTE-R (SBZ674) software version must be 1.0 or higher. Tellabs 8110 CTE-R (DPZ653) data pump software version must be 1.3 or higher. MartisDXX Manager support for Tellabs 8110 CTU-R is available in Release 12 Service Pack 1 or higher. Tellabs 8100 manager support for Tellabs 8110 CTE-R is available in Release 13A Service Pack 1 or higher. MartisDXX Manager support for NAT, packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher. Tellabs 8100 manager support for enhanced ping, traceroute, logging, and LMI functionalities are available in Release 13 Service Pack 1 or higher. Tellabs 8100 manager support for DiffServ, bridge CoS, Ethernet/VLAN encapsulation on WAN side for routed traffic, VLAN filtering, tunnelling, VLAN ID mapping, background connectivity monitoring tool, OSPFv2 and IP routing table enlargement to 4000 routes are available in Release 13A Service Pack 1 or higher.
Restrictions
This version should NOT be downloaded to Tellabs 8110 STE-10M.
Bugs
No known bugs.
10004_22 2008 Tellabs.

315
28.9 Version 2.4


Bug fix: Receiving of an Ethernet message destined to certain (rare) multicasts addresses in Router or BRouter mode hung Tellabs 8110 CTU-R. (CRF ID 4005274) Bug fix: Ethernet interface did not come up after a power down reset if Ethernet operation mode was forced (i.e. not auto-sensing) (CRF ID 4005301) Bug fix: Spanning tree message age was not decreased properly causing Spanning tree not to function correctly in certain reconfiguration situations (CR ID 200005971)
Dependencies

Tellabs 8110 CTU-R (CTU399) hardware version must be 1.0 or higher. Tellabs 8110 CTU-R (SBZ671) software version must be 1.2 or higher MartisDXX Manager support for this unit is available in Release 12 Service Pack 1 or higher. MartisDXX Manager support for NAT, packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher. Tellabs 8100 Manager support for enhanced ping, traceroute, logging, and LMI functionalities are available in Release 13 Service Pack 1 or higher.
Restrictions
Bugs
No known bugs.

316
10004_22 2008 Tellabs.
28.10 Version 2.3


NAT (network address translation ) support packet filtering support ping has time measurement and test packet size configuration traceroute support logging functionality LMI functionality reset and factory settings restore functionality PPP negotiation enhanced RIP v1 compatibility mode enhanced
Dependencies

Tellabs 8110 CTU-R (CTU399) hardware version must be 1.0 or higher. Tellabs 8110 CTU-R (SBZ671) software version must be 1.2 or higher MartisDXX Manager support for this unit is available in Release 12 Service Pack 1 or higher. MartisDXX Manager support for NAT, packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher. Tellabs 8100 manager support for enhanced ping, traceroute, logging, and LMI functionalities are available in Release 13 Service Pack 1 or higher.
Restrictions
Bugs
No known bugs.
28.11 Version 2.2

28.12 Version 2.1

10004_22 2008 Tellabs. Tellabs 8100 Managed Access System Unit Software Version Dependencies
317
28.13 Version 2.0

28.14 Version 1.8


Bug fix: Tellabs 8110 CTU-R frees the buffers of packets that are destined to CTU-R and carry unsupported transport layer protocols such as TCP. (CRF ID 4004760) Enhancement: Opaque VLAN (IEEE 802.1Q and Cisco ISL) frame bridging support (CRF ID 4004761)
Dependencies

Tellabs 8110 CTU-R (CTU399) hardware version must be 1.0 or higher. Tellabs 8110 CTU-R (SBZ671) software version must be 1.1 or higher MartisDXX Manager support for this unit is available in Release 12 Service Pack 1 or higher.
Restrictions
Bugs
No known bugs.
28.15 Version 1.7

28.16 Version 1.6


318
10004_22 2008 Tellabs.
28.17 Version 1.5

Tellabs 8110 CTU-R sends HDLC flags (bit pattern "01111110") to WAN (DSL) interface when there are no data packets to be sent. (CRF ID 4004648)
Dependencies

Restrictions
Bugs
No known bugs.
28.18 Version 1.4

This is an unofficial version and it should not be used once the next official version is available. Dependencies

Restrictions
Bugs
No known bugs.
10004_22 2008 Tellabs.

319
Tellabs 8110 CTU-R HDSL NTU: SBZ671 Unit Software
29 Tellabs 8110 CTU-R HDSL NTU: SBZ671 Unit Software

The software SBZ671 is used on Tellabs 8110 CTU-R (CTU399) unit. The version 2.0 can be downloaded to units having the version 2.y of SBZ671 (where y=1, 2, 3...).
29.1 Version 2.0

Support for AMIC flash. Enhancement. (CR ID 200025830)
Dependencies

Tellabs 8110 CTU-R (CTU399) hardware version must be 1.0 or higher. Tellabs 8110 CTU-R (SBZ670) software version must be 1.5 or higher. GMH (GMZ283) software version must be 10.0 or higher to support HCE-2M-1P and HCE-2M-2P modules. QMH (QMZ540) software version must be 10.5 or higher to support HCQ module. MartisDXX Manager support for this unit is available in Release 12 Service Pack 1 or higher. Tellabs 8100 manager support for time dependent DTE capacity control is available in Release 14 or higher.
Restrictions
The End-to-End V.110/CRC feature (EECRC) is not fully compatible with Tellabs 8110 HTU-2M (USW SBZ389 V1.0), and with Tellabs 8110 STU-320, STU-576, STU-1088-2W and STU-2304 (USW SBZ387 V 1.2 or earlier). These units support only unidirectional EECRC, and therefore bi-directional EECRC in Tellabs 8110 CTU-R misinterprets path to be constantly UNAVAILABLE.
Bugs
No known bugs.

320
10004_22 2008 Tellabs.
29.2 Version 1.4

Possibility to change the DTE capacity of CTU-R depending on the time of day. Enhancement. (CR ID 200015077)
Dependencies

Tellabs 8110 CTU-R (CTU399) hardware version must be 1.0 or higher. Tellabs 8110 CTU-R (SBZ670) software version must be 1.5 or higher. GMH (GMZ283) software version must be 10.0 or higher to support HCE-2M-1P and HCE-2M-2P modules. QMH (QMZ540) software version must be 10.5 or higher to support HCQ module. MartisDXX Manager support for this unit is available in Release 12 Service Pack 1 or higher. Tellabs 8100 manager support for time dependent DTE capacity control is available in Release 14 or higher.
Restrictions
Bugs
No known bugs.
10004_22 2008 Tellabs.

321
29.3 Version 1.3


Bug fix for quota problem. Under some rare circumstances, Tellabs 8110 CTU-R could reset itself due to lack of transport layer quotas. (CRF ID 4005048) G.826 15 minutes trigger alarms were generated ten seconds too early. (CRF ID 4005267)
Dependencies

Tellabs 8110 CTU-R (CTU399) hardware version must be 1.0 or higher. Tellabs 8110 CTU-R (SBZ670) software version must be 1.5 or higher. GMH (GMZ283) software version must be 10.0 or higher to support HCE-2M-1P and HCE-2M-2P modules. QMH (QMZ540) software version must be 10.5 or higher to support HCQ module. MartisDXX Manager support for this unit is available in Release 12 Service Pack 1 or higher.
Restrictions
Bugs
No known bugs.

322
10004_22 2008 Tellabs.
29.4 Version 1.2


Simultaneous modem parameter update with power failure (very unlikely to happen) might lead to corruption of setup data. Recovery function fixed. (CRF ID 4004897) Reserved new objects for router use. (CRF ID 4004667) Ability to reset router processor with Tellabs 8100 Manager. (CRF ID 4004687)
Dependencies

Restrictions
Bugs

Under some rare circumstances, Tellabs 8110 CTU-R might reset itself due to lack of transport layer quotas. (CRF ID 4005048) G.826 15 minutes trigger alarms are generated ten seconds too early. (CRF ID 4005267)
10004_22 2008 Tellabs.

323
29.5 Version 1.1

Dependencies

Restrictions
Bugs

Simultaneous modem parameter update with power failure (very unlikely to happen) might lead to corruption of setup data. (CRF ID 4004897) Under some rare circumstances, Tellabs 8110 CTU-R might reset itself due to lack of transport layer quotas. (CRF ID 4005048) G.826 15 minutes trigger alarms are generated ten seconds too early. (CRF ID 4005267)

324
10004_22 2008 Tellabs.
Tellabs 8110 CTU-S HDSL NTU: SBZ605 Unit Software
30 Tellabs 8110 CTU-S HDSL NTU: SBZ605 Unit Software

The software SBZ605 is used on Tellabs 8110 CTU-S V.35 (CTU395), CTU-S X.21 (CTU396) and CTU-S G.703 (CTU397) units. The version 3.0 can be downloaded to CTU-S units having the version 3.x of SBZ605 (where x=0, 1, 2...).
30.1 Version 3.0

Support for AMIC Flash. Enhancement. (CR ID 200025496)
Dependencies

CTU-S hardware version must be 1.0 or higher. GMH (GMZ283) software version must be 10.0 or higher to support HCE-2M-1P and HCE-2M-2P modules. QMH (QMZ540) software version must be 10.5 or higher to support HCQ-2M module. MartisDXX Manager support for this unit is available in Release 11 Service Pack 2 or higher. Tellabs 8100 manager support for time dependent DTE capacity control is available in Release 14 or higher.
Restrictions
The End-to-End V.110/CRC feature (EECRC) is not fully compatible with HTU-2M (USW SBZ389 V1.0), and with STU-320, STU-576, STU-1088-2W and STU-2304 (USW SBZ387 V 1.2 or earlier). These units support only unidirectional EECRC, and therefore bidirectional EECRC in CTU-S misinterprets path to be constantly UNAVAILABLE. CTU-S hardware version must be 2.0 or higher if point-to-point feature is to be utilized. Time dependent DTE rate control is not available for CTU-S G.703.
Bugs
No known bugs.
10004_22 2008 Tellabs.

325
30.2 Version 2.0


Point-to-point feature for CTU-S. Enhancement. (CR ID 200013025) Possibility to change the DTE capacity depending on the time of day. Enhancement. (CR ID 200013815) CTU-S sent 'G.826 performance event' alarms too early. As a result, Tellabs 8100 Network Manager read wrong counter values from CTU (current counter values were not moved to history table before reading took place). Now this bug is fixed. (CR ID 200005461)
Dependencies

CTU-S hardware version must be 1.0 or higher. GMH (GMZ283) software version must be 10.0 or higher to support HCE-2M-1P and HCE-2M-2P modules. QMH (QMZ540) software version must be 10.5 or higher to support HCQ-2M module. MartisDXX Manager support for this unit is available in Release 11 Service Pack 2 or higher. Tellabs 8100 manager support for time dependent DTE capacity control is available in Release 14 or higher.
Restrictions
The End-to-End V.110/CRC feature (EECRC) is not fully compatible with HTU-2M (USW SBZ389 V1.0), and with STU-320, STU-576, STU-1088-2W and STU-2304 (USW SBZ387 V 1.2 or earlier). These units support only unidirectional EECRC, and therefore bidirectional EECRC in CTU-S misinterprets path to be constantly UNAVAILABLE. CTU-S hardware version must be 2.0 or higher if point-to-point feature is to be utilized. Time dependent DTE rate control is not available for CTU-S G.703.
Bugs
No known bugs.

326
10004_22 2008 Tellabs.
30.3 Version 1.1

Short line breaks may cause loss of management communication channel, until the line is dropped or the HDLC channel is forced to the all ones signal for a couple of seconds. During the malfunction, the test interface terminal responses INVOKE ERROR for active faults query. Bug fix. (CRF ID 4004247) Reset of the Rx buffer slip counter clears the Tx counter and reset of Tx clears the Rx counter. This problem concerns V.35 and X.21 DTE-types only (not G.703). Bug fix. (CRF ID 4004248) The DTE interface code error counter is inoperative. This problem concerns G.703 DTEtype only. Bug fix. (CRF ID 4004350)
Dependencies

CTU-S hardware version must be 1.0 or 1.1. GMH (GMZ283) software version must be 10.0 or higher to support HCE-2M-1P and HCE-2M-2P modules. QMH (QMZ540) software version must be 10.5 or higher to support HCQ-2M module. MartisDXX Manager support for this unit is available in Release 11 Service Pack 2 or higher.
Restrictions
The End-to-End V.110/CRC feature (EECRC) is not fully compatible with HTU-2M (USW SBZ389 V1.0), and with STU-320, STU-576, STU-1088-2W and STU-2304 (USW SBZ387 V 1.2 or earlier). These units support only unidirectional EECRC, and therefore bidirectional EECRC in CTU-S misinterprets path to be constantly UNAVAILABLE.
Bugs
CTU-S sends 'G.826 performance event'-alarms too early. (CR ID 200005461)
10004_22 2008 Tellabs.

327
30.4 Version 1.0

This version was used only in Field Validation Tests. Dependencies

CTU-S hardware version must be 1.0 or 1.1. GMH (GMZ283) software version must be 10.0 or higher to support HCE-2M-1P and HCE-2M-2P modules. QMH (QMZ540) software version must be 10.5 or higher to support HCQ-2M module. MartisDXX Manager support for this unit is available in Release 11 Service Pack 2 or higher.
Restrictions
The End-to-End V.110/CRC feature (EECRC) is not fully compatible with HTU-2M (USW SBZ389 V1.0), and with STU-320, STU-576, STU-1088-2W and STU-2304 (USW SBZ387 V 1.2 or earlier). These units support only unidirectional EECRC, and therefore bidirectional EECRC in CTU-S misinterprets path to be constantly UNAVAILABLE.
Bugs
Short line breaks may cause loss of management communication channel, until the line is dropped or the HDLC channel is forced to the all ones signal for a couple of seconds. During the malfunction, the test interface terminal responses INVOKE ERROR for active faults query. (CRF ID 4004247) Reset of the Rx buffer slip counter clears the Tx counter and reset of Tx clears the Rx counter. This problem concerns V.35 and X.21 DTE-types only (not G.703). (CRF ID 4004248) The DTE interface code error counter is inoperative. This problem concerns G.703 DTEtype only. (CRF ID 4004350) CTU-S sends 'G.826 performance event'-alarms too early. (CR ID 200005461)

328
10004_22 2008 Tellabs.
Tellabs 8110 STE-10M NTU: SBZ792 Unit Software
31 Tellabs 8110 STE-10M NTU: SBZ792 Unit Software

The software SBZ792 is used on Tellabs 8110 STE-10M (STE790) units. The version 1.1 can be downloaded to STE-10M units having the version 1.y of SBZ792 (where y=0, 1, 2...).
31.1 Version 1.1

Support for 3 Mbit/s line modes added.
Dependencies

Tellabs 8110 STE-10M (STE790) hardware version must be 1.0 or higher. Tellabs 8110 STE-10M (DPZ794) DSP software version must be 1.1 or higher. Tellabs 8110 STE-10M (SBZ670) router software version must be 4.0 or higher. OMH (OMH771) hardware version must be 1.0 or higher. OMH (OMZ675) software version must be 2.0 or higher. ESU (ESU783 and ESM784) hardware version must be 1.0 or higher. ESU (EMZ642) software version must be 1.10 or higher. SCO interface module version must be 3.0 or higher to support 3 Mbit/s line modes. XCG (SMZ538) software version must be 2.0 or higher to support extra backups for other units in the node, and 3.5 or higher to support over 8M cross-connection ports. GMX (GMZ544) software version must be 3.19, or 4.1 or higher to support over 8M crossconnection ports. SXU-A/B (SXZ282) software version must be 10.5 or higher to support over 8M crossconnection ports. Tellabs 8100 manager support for this unit is available in Release 14 Service Pack 3 or higher. Tellabs 8100 manager support for 3 Mbit/s line modes is available in Release 14 Service Pack 6 or higher.
Restrictions
No restrictions.
10004_22 2008 Tellabs.

329
Tellabs 8110 STE-10M NTU: SBZ792 Unit Software
Bugs
No known bugs.
31.2 Version 1.0

Dependencies

Tellabs 8110 STE-10M (STE790) hardware version must be 1.0 or higher. Tellabs 8110 STE-10M (DPZ794) DSP software version must be 1.0 or higher. Tellabs 8110 STE-10M (SBZ670) router software version must be 4.0 or higher. OMH (OMH771) hardware version must be 1.0 or higher. OMH (OMZ675) software version must be 2.0 or higher. ESU (ESU783 and ESM784) hardware version must be 1.0 or higher. ESU (EMZ642) software version must be 1.9 or higher. SCO interface module version must be 3.0 or higher to support 4-pair modes. XCG (SMZ538) software version must be 2.0 or higher to support extra backups for other units in the node, and 3.5 or higher to support over 8M cross-connection ports. GMX (GMZ544) software version must be 3.19, or 4.1 or higher to support over 8M crossconnection ports. SXU-A/B (SXZ282) software version must be 10.5 or higher to support over 8M crossconnection ports. Tellabs 8100 manager support for this unit is available in Release 14 Service Pack 3 or higher.
Restrictions
No restrictions.
Bugs
No known bugs.

330
10004_22 2008 Tellabs.
Tellabs 8120 Mini Node M: SMZ414 Unit Software
32 Tellabs 8120 Mini Node M: SMZ414 Unit Software

The software SMZ414 is used on Tellabs 8120 mini node M (SBM 2048 M). The version 5.0 can be downloaded to SBM 2048s with the revision 5.y of SMZ414 (where y = 0, 1, 2,). The version 4.6 can be downloaded to SBM 2048s with the revision 4.y of SMZ414 (where y = 0, 1, 2,). The SBM 2048M software is structured into two packages: kernel and application. The kernel package contains the operating system, communications services for the SC, and the basic system services: command interpreter, flash memory programming support, downloading support, etc. The kernel package resides in the ROM memory. The application package is downloadable and resides in the flash memory. Note: If the application package is disabled, only the services provided by the kernel package are available.
32.1 Version 5.0

Dependencies

MartisDXX Manager support for LAN Module and HSSI interface modules are available in Release 10.1A SP7. Requires HW version 6.1.
Restrictions

LAN Bridge parameters are located in its own flash memory. Therefore, when replacing a LAN Module, LAN Bridge parameters have to be set with MartisDXX Manager. Does not support VCM type interface parameter menus. Does not support CAS at 2048 kbit/s<bitrate<8448 kbit/s.
Bugs
No known bugs.
10004_22 2008 Tellabs.

331
32.2 Version 4.6

Dependencies
Requires HW version 6.0.
Restrictions

Does not support VCM type interface parameter menus. Does not support CAS at 2048 kbit/s<bitrate<8448 kbit/s.
Bugs

The current practise in production after 1999 is set to year value 100 which is not possible with the current unit software. Displaying wrong G.821 statistics DM information. The control channel fails if MartisDXX Manager sends too low HDLC link timeout parameter values.
32.3 Version 4.4

Dependencies
No dependencies.
Restrictions

Does not support BTE-320, BTE-576, BTE-1088-2W and BTE-2304 modules. Does not support DEG/EXC BER alarms. Frequency difference alarm does not meet G.823 updated standard (1993). An alarm will be generated when using x-connected timeslot for HDLC. Does not support all bit rates between 2M-8M (IF3..6). Does not support X and E bits.
Bugs

Unnecessary TX-Clock fault when using BTE-4096 module. 114/115 contra and 114/115 invert timing mode do not work at rates over 2048 kbibt/s.

332
10004_22 2008 Tellabs.
32.4 Version 4.3

Dependencies
No dependencies.
Restrictions

Does not support BTE-320, BTE-576, BTE-1088-2W and BTE-2304 modules. Does not support DEG/EXC BER alarms. Frequency difference alarm does not meet G.823 updated standard (1993). An alarm will be generated when using x-connected timeslot for HDLC. Does not support all bit rates between 2M-8M (IF3..6). Does not support X and E bits. Does not support BTE-2048-2W module. Does not support AIS detection in unframed mode. Does not support RAI-Xcon mode. Does not support 105 off delay parameters.
Bugs

Unnecessary TX-Clock fault when using BTE-4096 module. 114/115 contra and 114/115 invert timing mode do not work at rates over 2048 kbibt/s.
32.5 Version 4.1

Dependencies
No dependencies.
Restrictions

Does not support BTE-320, BTE-576, BTE-1088-2W and BTE-2304 modules. Does not support DEG/EXC BER alarms. Frequency difference alarm does not meet G.823 updated standard (1993). An alarm will be generated when using x-connected timeslot for HDLC. Does not support all bit rates between 2M-8M (IF3..6). Does not support X and E bits. Does not support BTE-2048, V35-G704S and X21-G704S modules. Does not support FSW-RAI usage: X-sync.
10004_22 2008 Tellabs.

333
Does not support cross-connection:

CAS idle object enhancement to cross-connect RAM maintenance functions
Does not support async test possibility for circuit loop tester. Does not support 114 invert timing mode. Does not support BTE-1088, BTE-4096, G703-75, G703-120, G703-8M modules. Does not support BTE-384 module wetting current strapping info (in the new version BTE384 strapping possibility). Does not support fan fault supervision. Does not support BTE-2048-2W module. Does not support AIS detection in unframed mode. Does not support RAI-Xcon mode. Does not support 105 off delay parameters.
Bugs

Unnecessary TX-Clock fault when using BTE-4096 module. 114/115 contra and 114/115 invert timing mode do not work at rates over 2048 kbibt/s. LCD menu test pattern selections (IF3IF6) when M > 6 are not correct. When GMH interface has loop to interface and unframed mode and no x-connections, AIS (not RX signal) shall be sent. High speed correction at 4Mbit < bit rate < 8Mbit. V.54 loop activation control. 106 delay corrections.
32.6 Version 4.0

Dependencies
No dependencies.
Restrictions

Does not support BTE-320, BTE-576, BTE-1088-2W and BTE-2304 modules. Does not support DEG/EXC BER alarms. Frequency difference alarm does not meet G.823 updated standard (1993). An alarm will be generated when using x-connected timeslot for HDLC. Does not support all bit rates between 2M-8M (IF3..6). Does not support X and E bits. Does not support V.35-G704B nor X.21-G704 modules (lower modules).

334
10004_22 2008 Tellabs.
Does not support V.35-V.24 module (upper modules). Does not support power supply identification info. Does not support bit rate 33 x 64 kbit/s (lower modules). Does not support BTE-2048, V35-G704S and X21-G704S modules. Does not support FSW-RAI usage: X-sync. Does not support cross-connection:

Bugs

Unnecessary TX-Clock fault when using BTE-4096 module. 114/115 contra and 114/115 invert timing mode do not work at rates over 2048 kbibt/s. Continuous unit report sending (if sending enabled) when faults are masked. Illegal parameter choices in the LCD menu when handling the loop parameters of G703-64-M module. MartisDXX Manager Disaster Recovery cannot be used. Bit rates below 8 kbit/s do not work. Power-off indication from DTE does not work (upper modules). XB capacity allocation error in the case of X.21 (upper modules) and C/I transfer. Does not support cluster usage. LCD menu test pattern selections (IF3IF6) when M > 6 are not correct. When GMH interface has loop to interface and unframed mode and no x-connections, AIS (not RX signal) shall be sent. High speed correction at 4Mbit < bit rate < 8Mbit V.54 loop activation control 106 delay corrections
10004_22 2008 Tellabs.

335
32.7 Version 3.3

Dependencies
No dependencies.
Restrictions

Does not support BTE-320, BTE-576, BTE-1088-2W and BTE-2304 modules. Does not support DEG/EXC BER alarms. Frequency difference alarm does not meet G.823 updated standard (1993). An alarm will be generated when using x-connected timeslot for HDLC. Does not support all bit rates between 2M-8M (IF3..6). Does not support X and E bits. Does not support new type of flash memory. Does not support BTE-2048, V35-G704S and X21-G704S modules. Does not support FSW-RAI usage: X-sync. Does not support cross-connection:

Bugs

Unnecessary TX-Clock fault when using BTE-4096 module. 114/115 contra and 114/115 invert timing mode do not work at rates over 2048 kbit/s. LCD menu test pattern selections (IF3IF6) when M > 6 are not correct. When GMH interface has loop to interface and unframed mode and no x-connections, AIS (not RX signal) shall be sent. High speed correction at 4Mbit < bit rate < 8Mbit

336
10004_22 2008 Tellabs.
V.54 loop activation control 106 delay corrections
32.8 Version 3.2

Dependencies
No dependencies.
Restrictions

Does not support BTE-320, BTE-576, BTE-1088-2W and BTE-2304 modules. Does not support DEG/EXC BER alarms. Frequency difference alarm does not meet G.823 updated standard (1993). An alarm will be generated when using x-connected timeslot for HDLC. Does not support all bit rates between 2M-8M (IF3..6). Does not support X and E bits. Does not support new type of flash memory. Does not support V.35-G704B nor X.21-G704 modules (lower modules). Does not support V.35 - V.24 module (upper modules). Does not support power supply identification info. Does not support bit rate 33 x 64 kbit/s (lower modules). Does not support BTE-2048, V35-G704S and X21-G704S modules. Does not support FSW-RAI usage: X-sync. Does not support cross-connection:

10004_22 2008 Tellabs.

337
Bugs

Unnecessary TX-Clock fault when using BTE-4096 module. 114/115 contra and 114/115 invert timing mode do not work at rates over 2048 kbibt/s. Continuous unit report sending (if sending enabled) when faults are masked. Illegal parameter choices in the LCD menu when handling the loop parameters of the G703-64-M module. MartisDXX Manager Disaster Recovery cannot be used. Bit rates below 8 kbit/s do not work. Power-off indication from DTE does not work (upper modules). XB capacity allocation error in the case of X.21 (upper modules) and C/I transfer. Does not support cluster usage. LCD menu test pattern selections (IF3IF6) when M > 6 are not correct. When GMH interface has loop to interface and unframed mode and no x-connections, AIS (not RX signal) shall be sent. High speed correction at 4Mbit < bit rate < 8Mbit V.54 loop activation control 106 delay corrections
32.9 Version 3.1

Dependencies
No dependencies.
Restrictions

Does not support BTE-320, BTE-576, BTE-1088-2W and BTE-2304 modules. Does not support DEG/EXC BER alarms. Frequency difference alarm does not meet G.823 updated standard (1993). An alarm will be generated when using x-connected timeslot for HDLC. Does not support all bit rates between 2M-8M (IF3..6). Does not support X and E bits. Does not support new type of flash memory. Does not support V.35-G704B nor X.21-G704 modules (lower modules). Does not support V.35-V.24 module (upper modules). Does not support power supply identification info. Does not support bit rate 33 x 64 kbit/s (lower modules). Does not support BTE-2048, V35-G704S and X21-G704S modules.

338
10004_22 2008 Tellabs.
Does not support FSW-RAI usage: X-sync. Does not support cross-connection:

Bugs

Unnecessary TX-Clock fault when using BTE-4096 module. 114/115 contra and 114/115 invert timing mode do not work at rates over 2048 kbibt/s. Copying the connections of a split trunk control port IF21 by using the front panel keys accesses the wrong node. Does not support ring synchronization. Does not support signalling when the bit rate is 1831 x 64 kbit/s. Continuous unit report sending (if sending enabled) when faults are masked. Illegal parameter choices in the LCD menu when handling the loop parameters of G703-64-M module. MartisDXX Manager Disaster Recovery cannot be used. Bit rates below 8 kbit/s do not work. Power-off indication from DTE does not work (upper modules). XB capacity allocation error in case of X.21 (upper modules) and C/I transfer. Does not support cluster usage. LCD menu test pattern selections (IF3IF6) when M > 6 are not correct. When GMH interface has loop to interface and unframed mode and no x-connections, AIS (not RX signal) shall be sent. High speed correction at 4Mbit < bit rate < 8Mbit V.54 loop activation control 106 delay corrections
10004_22 2008 Tellabs.

339
Tellabs 8130 Micro Node (SMH-U): SMZ533 Unit Software
33 Tellabs 8130 Micro Node (SMH-U): SMZ533 Unit Software

The software SMZ533 is used on Tellabs 8130 micro node. Version 2.2 can be downloaded to Tellabs 8130 micro nodes with version 2.0 or 2.2 of SMZ533.
33.1 Version 2.2

Dependencies
No dependencies.
Restrictions
No restrictions.
Bugs
No known bugs.
33.2 Version 2.1

Dependencies
No dependencies.
Restrictions

Does not support the BTE-320, BTE-576, BTE-1088-2W, BTE-2304 modules. An alarm will be generated when using the x-connected timeslot for HDLC. Does not support the DEG/EXC BER alarms. Does not support the micro BTS. Frequency difference alarm does not meet the G.823 updated standard (1993). Support for fast download (in Prom of 2.2). Support XC ASICs to 80186 bus mode (all registers at even address). TS0 invert and Rx monitor without CRC. HDLC link timeout over satellite.
Bugs
No alarm when neighbour makes a V.54 loop.

340
10004_22 2008 Tellabs.
VCM-A UNIT: VCZ285A Unit Software
34 VCM-A UNIT: VCZ285A Unit Software

The software VCZ285A is used on VCM-A units in Basic and Midi Nodes and A111. The version 10.2 can be downloaded to VCM-A units having the version 10.y of VCZ285A (where y=0, 1, 2...). The release 2.14 can be downloaded to VCM-A units having the version 2.y of VCZ285A (where y=0, 1, 2...).
34.1 Version 10.2

Dependencies

VCM-A (base unit VCM222A / VCM223A) hardware version must be 4.0 or higher. VCM-A does not support Cluster Node. SCP (SCZ281) software version can be any. SCU (SCZ280) software version can be any. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version can be any. GMX (GMZ544) software version can be any. SXU-A/B (SXZ282) software version must be 5.4 or higher. VCM-A can be in the same node with SXU-V, but it does not support V5.2 itself and its functionality is like with SXU-A. MartisDXX Manager support for VCM LAN and HSSI interface modules are available in Release 10.1A or higher.
Restrictions
VCM LAN module parameters are located in its own flash memory. When replacing a VCM unit including a VCM LAN module, VCM LAN module parameters have to be set with MartisDXX Manager.
Bugs

Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80, 144 and 160 kbit/s. In such cases the alarms do not disturb the data stream. After a cross-connection has been deleted from a VCM interface, IA activity missing and Rx buffer slip faults might shortly occur.
10004_22 2008 Tellabs.

341
34.2 Version 10.1

Dependencies
MartisDXX Manager support for VCM Bridge and HSSI interface modules are available in Release 10.1A.
Restrictions

Requires 4.0 hardware. VCM Bridge parameters are located in its own flash memory so, when replacing a VCM unit including a VCM bridge module, VCM bridge parameters have to be set with MartisDXX Manager.
Bugs

Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80, 144 and 160 kbit/s. In such cases the alarms do not disturb the data stream. After a cross-connection has been deleted from a VCM interface, IA activity missing and Rx buffer slip faults might shortly occur. VCM-5T-A (hw4.0/usw 10.0) circuit loop test resource does't fuction correctly if control channel is NONE. (CRF 4002470) Problem to reset loop from the VCM unit when there have been clocking problems. (CRF 4002303) Problems with some data speeds ( 7104, 7168 and 7232 kbit/s ) of the VCM X.21. (CRF 4002693) VCM X.21 does not function with X21 S+B timing and S_inv. (CRF 4002650) Bit rates over 32 x 64 kbit/s in VCM A cards can be changed even if the interface is locked. (CRF 4003715)

342
10004_22 2008 Tellabs.
34.3 Version 10.0

Dependencies
No dependencies.
Restrictions
Requires 4.0 hardware.
Bugs

34.4 Version 2.14

Dependencies
No dependencies.
Restrictions

USW version 2.14 requires 3.x hardware. USW version 2.14 does not support all bit rates between 2M - 8M. USW version 2.14 does not support X and E bits. USW version 2.14 does not fully support V.24 DTE LL and RL loops.
Bugs

114/115 contradir and 114/115 invert timing modes do not work over 2048 kbit/s bit rates. IF does not activate if 113/115 clock is not connected. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80, 144 and 160 kbit/s. In such cases the alarms do not disturb the data stream. After a cross-connection has been deleted from a VCM interface, IA activity missing and Rx buffer slip faults might shortly occur.
10004_22 2008 Tellabs.

343
34.5 Version 2.13

Dependencies
No dependencies.
Restrictions
See the restrictions of version 2.14.
Bugs

Wrong X-bus capacity when Control channel: none, 105: Fixed off Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80, 144 and 160 kbit/s. In such cases the alarms do not disturb the data stream. After a cross-connection has been deleted from a VCM interface, IA activity missing and Rx buffer slip faults might shortly occur.
34.6 Version 2.12

Dependencies
No dependencies
Restrictions

No support for 105 off delay parameter. No support for V24-PMP tail eater module. See the restrictions of version 2.13.
Bugs

AIS from PCM inverts data towards X-Bus to all zeros in 6703-PDA. Wrong X-bus capacity when Control channel: none, 105: Fixed off. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80, 144 and 160 kbit/s. In such cases the alarms do not disturb the data stream. After a cross-connection has been deleted from a VCM interface, IA activity missing and Rx buffer slip faults might shortly occur.

344
10004_22 2008 Tellabs.
34.7 Version 2.11

Dependencies
No dependencies.
Restrictions
Bugs

High speed problems between 4Mbit/s and 8Mbit/s. V.54 loop activation not according to spec. V.54. You cannot bring 106 delay back below 255. No support for V24-PMP tail eater module. Wrong X-bus capacity when Control channel: none, 105: Fixed off. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80, 144 and 160 kbit/s. In such cases the alarms do not disturb the data stream. After a cross-connection has been deleted from a VCM interface, IA activity missing and Rx buffer slip faults might shortly occur.
34.8 Version 2.10

Dependencies
No dependencies.
Restrictions

No ASYNC test support for CTS. No 114 inverted timing mode. See the restrictions of version 2.11.
Bugs

Wrong X-bus capacity when Control channel: none, 105: Fixed off. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80, 144 and 160 kbit/s. In such cases the alarms do not disturb the data stream. After a cross-connection has been deleted from a VCM interface, IA activity missing and Rx buffer slip faults might shortly occur.
10004_22 2008 Tellabs.

345
34.9 Version 2.9

Dependencies
No dependencies.
Restrictions
Bugs

Bit rates below 8 kbit do not work. Bit rates from 4 Mbit/s to 8448 kbits/s does not work. XB capacity allocation error in case of X.21 module and C/I transfer. Wrong X-bus capacity when Control channel: none, 105: Fixed off. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80, 144 and 160 kbit/s. In such cases the alarms do not disturb the data stream. After a cross-connection has been deleted from a VCM interface, IA activity missing and Rx buffer slip faults might shortly occur.
34.10 Version 2.8

Dependencies
No dependencies.
Restrictions

No G.703-PDA (GPL245) support. See the restrictions of version 2.9.
Bugs

Wrong X-bus capacity when Control channel: none, 105: Fixed off. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80, 144 and 160 kbit/s. In such cases the alarms do not disturb the data stream. After a cross-connection has been deleted from a VCM interface, IA activity missing and Rx buffer slip faults might shortly occur.

346
10004_22 2008 Tellabs.
34.11 Version 2.7

Dependencies
No dependencies.
Restrictions

VCM 222A/VCM 223A version must be 3.0. See the restrictions of version 2.8.
Bugs

Asic timing error (octet pulse). Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80, 144 and 160 kbit/s. In such cases the alarms do not disturb the data stream. After a cross-connection has been deleted from a VCM interface, IA activity missing and Rx buffer slip faults might shortly occur.
34.12 Version 2.6

Dependencies
No support for Rev.3 IFMOD ASIC ( Hw-version 3.1).
Restrictions

No PMP cluster support. See the restrictions of version 2.7.
Bugs

No known bugs. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80, 144 and 160 kbit/s. In such cases the alarms do not disturb the data stream. After a cross-connection has been deleted from a VCM interface, IA activity missing and Rx buffer slip faults might shortly occur.
10004_22 2008 Tellabs.

347
34.13 Version 2.5

Dependencies
No dependencies.
Restrictions
Bugs

In case of 113/115 clocking with VDS242 module 113 clock can be erroneous. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80, 144 and 160 kbit/s. In such cases the alarms do not disturb the data stream. After a cross-connection has been deleted from a VCM interface, IA activity missing and Rx buffer slip faults might shortly occur.
34.14 Version 2.4

Dependencies
No dependencies.
Restrictions

No PMP locking object. See the restrictions of version 2.5.
Bugs

Buffer slip alarms in case of X30 framer. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80, 144 and 160 kbit/s. In such cases the alarms do not disturb the data stream. After a cross-connection has been deleted from a VCM interface, IA activity missing and Rx buffer slip faults might shortly occur.

348
10004_22 2008 Tellabs.
34.15 Version 2.3

Dependencies
No dependencies.
Restrictions

Pmp server functions is not supported. See the restrictions of version 2.4.
Bugs

Buffer sizes at >64 kbit/s are not optimal. In case the X30 framer & no control channel connection capacity is too high. The Alarm bit on V110 frame is inverted. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80, 144 and 160 kbit/s. In such cases the alarms do not disturb the data stream. After a cross-connection has been deleted from a VCM interface, IA activity missing and Rx buffer slip faults might shortly occur.
34.16 Version 2.0

Dependencies
No dependencies.
Restrictions

8 kbit/s is not available. SXU IA testing is not supported. Bit rates up to 8448 kbit/s are not supported. See the restrictions of version 2.3.
Bugs

Some buffer sizes should be greater in case of codirectional clocking. Some faults have zero GPT (General Problem Type). If Interface Module is none, unit informs Code-error fault. In case the N*64 kbit/s & V13 & CRC ON connection capacity is too high. In case the X30 framer & no control channel connection capacity is too high. The Alarm bit on V110 frame is inverted.
10004_22 2008 Tellabs.

349

350
10004_22 2008 Tellabs.
XCG Unit: SMZ538 Unit Software
35 XCG Unit: SMZ538 Unit Software

The software SMZ538 is used on XCG unit (whose base unit is XCG525) in Tellabs 8140 midi node and Tellabs 8150 basic node. The version 3.5 can be downloaded to XCG units having the version 3.x of SMZ538 (where x=0, 1, 2...).
35.1 Version 3.5


Trunk swap does not cause data errors. (CR ID 200035773) The background sending of the cross-connected timeslots (Free Time Slot sending) operates correctly for ports over 8448kbit/s. The interface unit needs this information to function correctly. Data errors would follow if this message is not sent by XCG. (CR ID 200032287) The test timeslot used internally for port IA testing has been changed depending on the port capacity. This modification is needed to support Tellabs 8110 STE-10M and any other product when speeds over 8960 kbit/s are used. (CR ID 200031044) The problem preventing XCG inventory operations has been fixed. (CR ID 200031040)
Dependencies

XCG (base unit XCG525) hardware version must be 2.2 or higher. XCG interface modules G703-75-4CH (base unit GDH521) and G703-120-4CH (base unit GDH522) hardware version must be 1.1 or higher. MartisDXX Manager support for pilot bit feature of XCG unit is available in Release 12 Service Pack 1 or higher.
Restrictions
No restrictions.
Bugs
HDLC link timeout value 11 is impossible.
10004_22 2008 Tellabs.

351
35.2 Version 3.4


The XB port capacity is supported to up to 192x64 kbit/s. This is required for the ESU unit. (CR ID 200011656) The check of incoming message integrity is improved. The XCG unit is able to detect a message that has a consistency problem in the internal data structure. The processing of the invalid message is prevented. This will make the unit much more reliable in case of any communication problem. (CR ID 200012800) X-Connect RAM fault now disappears automatically when the error condition has ended. (CR ID 200012801) Module type set operation is now possible also when the XCG unit is not in inventory. The bug could have had an effect on the initialization of the control channels during node installation. (CR ID 200012802) The Separate Command Bit TS0/B1 operation is fixed. (CR ID 200012803) The interface 1+1 Protection Mode activation or deactivation does not any more cause occasional and unintentional clear of fault history buffer. (CR ID 200011615) The 1+1 Protection Mode dependent fault status is set correctly after reset. (CR ID 200011615) Neighbor node monitoring (NNM) polling status problems cannot cause wrong clock selection anymore. In the case of NNM link communication problem the QL value is set to 7 (DNU) to prevent wrong clock source selection. Normally the master clock QL value of a clock source is obtained from an interface unit by polling it inside the node. The interface unit gets the QL from neighbor node by the NNM mechanism. (CR ID 200012804) The QL value reported from the unit to the Master Clock State window is set to value 7 (Do Not Use) when there is an active problem in the clock source. Also the EXT clock QL is set to value 7 (DNU) when there is an active problem in the external clock source. This change concerns only the reporting of QL values. The actual selection logic in the unit has been working without any problems and remains unchanged. (CR ID 200012805)
Dependencies

Restrictions
No restrictions.

352
10004_22 2008 Tellabs.
Bugs
There may be data errors after trunk swap for 2 minutes or shorter time. The problem concerns only the swapped trunks that may belong to any interface in the node. (CR ID 200035773) The background sending of the cross-connected timeslots (Free Time Slot sending) for ports over 8448 kbit/s does not operate correctly. The interface unit needs this information to function correctly. Data errors will follow if this message is not sent by XCG. (CR ID 200032287) If a port bigger than 140*64 kbit/s is used, the IA test timeslot overlaps with payload data and data errors will follow. (CR ID 200031044) The inventory add and delete operations for XCG unit are impossible. An installed (upgraded) XCG with ESW version 3.4 will otherwise operate normally. (CR ID 200031040) HDLC link timeout value 11 is impossible.
35.3 Version 3.3


The problem with a failing asynchronous link, between DXX server and XCG, under heavy loading condition is fixed. (CRF ID 4004049) Memory management enhanced. (CRF ID 4005098) Clock status DNU is sent via NNM if unit can not get locked to node clock. (CRF ID 4004992) Line loop bug with pilot bit fixed. (CRF ID 4004406) G.821 statistics for 1+1 protected trunk fixed. (CRF ID 4005001) Clock QL state is forced to DNU if NNM is down. (CRF ID 4004718) AIS fault is restrained with equipment loop when pilot bit is set. (CRF ID 4004658) The problem with available time in 1+1 trunk performance data always remaining 100% fixed. (CRF ID 4004979) Fallback List Warning alarm is removed. (CRF ID 4004904)
Dependencies

Restrictions
The XB port capacity of up to 192x64 kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. (CR ID 200011656)
10004_22 2008 Tellabs.

353
Bugs

The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. The processing of the invalid message is not prevented. (CR ID 200012800) X-Connect RAM fault does not disappear automatically when the error condition has ended. (CR ID 200012801) Module type set operation is not possible when the XCG unit is not in inventory. This may have effect on the initialization of the control channels during node installation. (CR ID 200012802) The Separate Command Bit TS0/B1 does not operate correctly. (CR ID 200012803) The interface 1+1 Protection Mode activation or deactivation may cause occasional and unintentional reset of the fault history buffer. This does not effect on the information given by the NMS Fault Management System (FMS). (CR ID 200011615) The 1+1 Protection Mode dependent fault status may be wrong after reset if the 1+1 Protection Mode was activated. (CR ID 200011615) The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. (CR ID 200012804) The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. (CR ID 200012805) HDLC link timeout value 11 is impossible.
35.4 Version 3.2

This is an unofficial version based on version 3.1. This version should not be used once the next official version is available. Enhancements and Fixed Bugs The use of this version is recommended only to correct the following problems with XCG:
Asynchronous link between DXX server and XCG is used and access to nodes often fails and control channel broken faults frequently occur in some nodes of the network. (CRF ID 4004049) Occurrence of a random Missing Unit fault fixed. (CRF ID 4004837)
Dependencies


354
10004_22 2008 Tellabs.
Restrictions
The XB port capacity of up to 192x64 kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied.
Bugs

The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. The processing of the invalid message is not prevented. (CR ID 200012800) X-Connect RAM fault does not disappear automatically when the error condition has ended. (CR ID 200012801) The Separate Command Bit TS0/B1 does not operate correctly. (CR ID 200012803) The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. (CR ID 200012804) The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. (CR ID 200012805) Asynchronous link might still fail under a heavy loading condition.
35.5 Version 3.1


Pilot bit feature in own interfaces 1 - 4 of XCG unit. (CRF ID 4004062) Disabling of downloaded software is not any more possible. (CRF ID 4003830)
Dependencies

Restrictions
The XB port capacity of up to 192x64 kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. (CR ID 200011656)
Bugs

The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. The processing of the invalid message is not prevented. (CR ID 200012800) X-Connect RAM fault does not disappear automatically when the error condition has ended. (CR ID 200012801) The Separate Command Bit TS0/B1 does not operate correctly. (CR ID 200012803)
10004_22 2008 Tellabs.

355
The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. (CR ID 200012804) The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. (CR ID 200012805)
35.6 Version 3.0

HDLC channels in own interfaces 3 - 4 of XCG unit.
Dependencies

XCG (base unit XCG525) hardware version must be 2.2 or higher. XCG interface modules G703-75-4CH (base unit GDH521) and G703-120-4CH (base unit GDH522) hardware version must be 1.1 or higher. MartisDXX Manager support for HDLC channels in own interfaces 3 - 4 of XCG unit is available in Release 11 Service Pack 1 or higher.
Restrictions

The XB port capacity of up to 192x64 kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. (CR ID 200011656) No pilot bit feature.
Bugs

The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. The processing of the invalid message is not prevented. (CR ID 200012800) X-Connect RAM fault does not disappear automatically when the error condition has ended. (CR ID 200012801) The Separate Command Bit TS0/B1 does not operate correctly. (CR ID 200012803) The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. (CR ID 200012804) The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. (CR ID 200012805)

356
10004_22 2008 Tellabs.
35.7 Version 2.3

XCG shows right QL status for clock source through STM-1 interface of GMU
Dependencies
MartisDXX Manager support for XCG unit is available in Release 9 Service Pack 1 or higher.
Restrictions

The XB port capacity of up to 192x64 kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. (CR ID 200011656) No pilot bit feature. No HDLC channels in interfaces 3 4.
Bugs

The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. The processing of the invalid message is not prevented. (CR ID 200012800) X-Connect RAM fault does not disappear automatically when the error condition has ended. (CR ID 200012801) The Separate Command Bit TS0/B1 does not operate correctly. (CR ID 200012803) The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. (CR ID 200012804) The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. (CR ID 200012805) Master clock hold over does not work. There can be incorrect IN USE information of timeslots in interfaces 3 and 4 when 1+1 protection is on. Slow neighbour alarm when a cable is removed from interface 1. The HDLC channel fails if NMS sends too low HDLC LINK TIMEOUT parameter values. The G.821 unavailable state alarm is missing.
10004_22 2008 Tellabs.

357
35.8 Version 2.2

This is a non-production version based on version 2.1. This version should not be used once the next official version is available Enhancements and Fixed Bugs
Occurrence of a random Missing Unit fault fixed. (CRF ID 4004837)
Dependencies
Restrictions

Bugs

The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. The processing of the invalid message is not prevented. (CR ID 200012800) X-Connect RAM fault does not disappear automatically when the error condition has ended. (CR ID 200012801) The Separate Command Bit TS0/B1 does not operate correctly. (CR ID 200012803) The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. (CR ID 200012804) The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. (CR ID 200012805) Master clock hold over does not work. There can be incorrect IN USE information of timeslots in interfaces 3 and 4 when 1+1 protection is on. Slow neighbour alarm when a cable is removed from interface 1. The HDLC channel fails if NMS sends too low HDLC LINK TIMEOUT parameter values. The G.821 unavailable state alarm is missing. Master clock source through STM-1 interface of GMU shows wrong QL status.

358
10004_22 2008 Tellabs.
35.9 Version 2.1


Support for GMU and GMU-M units. Support for Micro BTS. HDLC link over satellite feature. New BER alarms (Exc/Deg). New detection criteria in the Freq. Difference alarm. New feature: TS0 invert and Rx monitor without CRC. The new HDLC/X-bus overlap alarm. Node synchronisation source change alarms. Voltage bus alarm filtering for PAU-5T.
Dependencies
Restrictions

Bugs

The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. The processing of the invalid message is not prevented. (CR ID 200012800) X-Connect RAM fault does not disappear automatically when the error condition has ended. (CR ID 200012801) The Separate Command Bit TS0/B1 does not operate correctly. (CR ID 200012803) The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. (CR ID 200012804) The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. (CR ID 200012805) Master clock hold over does not work. There can be incorrect IN USE information of timeslots in interfaces 3 and 4 when 1+1 protection is on. Slow neighbour alarm when a cable is removed from interface 1. The HDLC channel fails if NMS sends too low HDLC LINK TIMEOUT parameter values.
359
10004_22 2008 Tellabs.
It is possible that there occur faulty Missing unit alarms. The G.821 unavailable state alarm is missing.
35.10 Version 2.0

Extended backup support.
Dependencies
Restrictions

The XB port capacity of up to 192x64 kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. (CR ID 200011656) No pilot bit feature. No HDLC channels in interfaces 3 4. No support for GMU and GMU-M units. No support for Micro BTS. No HDLC link over satellite feature. No new BER alarms (Exc/Deg). Old detection criteria in the Freq. Difference alarm. No feature: TS0 invert and Rx monitor without CRC. The old HDLC/X-bus overlap alarm. No node synchronisation source change alarms. No voltage bus alarm filtering for PAU-5T.
Bugs

The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. The processing of the invalid message is not prevented. (CR ID 200012800) X-Connect RAM fault does not disappear automatically when the error condition has ended. (CR ID 200012801) The Separate Command Bit TS0/B1 does not operate correctly. (CR ID 200012803) The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. (CR ID 200012804) The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. (CR ID 200012805)

360
10004_22 2008 Tellabs.
Master clock hold over does not work. There can be incorrect IN USE information of timeslots in interfaces 3 and 4 when 1+1 protection is on. Slow neighbour alarm when a cable is removed from interface 1. The HDLC channel fails if NMS sends too low HDLC LINK TIMEOUT parameter values. It is possible that there occur faulty Missing unit alarms. The G.821 unavailable state alarm is missing.
35.11 Version 1.0

First version, no enhancements.
Dependencies
Restrictions

The XB port capacity of up to 192x64 kbit/s is not supported. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. (CR ID 200011656) No pilot bit feature. No HDLC channels in interfaces 3 4. No support for GMU and GMU-M units. No support for Micro BTS. No HDLC link over satellite feature. No new BER alarms (Exc/Deg). Old detection criteria in the Freq. Difference alarm. No feature: TS0 invert and Rx monitor without CRC. The old HDLC/X-bus overlap alarm. No node synchronisation source change alarms. No voltage bus alarm filtering for PAU-5T. No extended backup support.
10004_22 2008 Tellabs.

361
Bugs

The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. The processing of the invalid message is not prevented. (CR ID 200012800) X-Connect RAM fault does not disappear automatically when the error condition has ended. (CR ID 200012801) The Separate Command Bit TS0/B1 does not operate correctly. (CR ID 200012803) The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. (CR ID 200012804) The QL value reported in the Master Clock State window is not always set to 7 (DNU) when there is an active problem in a clock source. (CR ID 200012805) Master clock hold over does not work. There can be incorrect IN USE information of timeslots in interfaces 3 and 4 when 1+1 protection is on. Slow neighbour alarm when a cable is removed from interface 1. The HDLC channel fails if NMS sends too low HDLC LINK TIMEOUT parameter values. It is possible that there occur faulty missing unit alarms. The G.821 unavailable state alarm is missing. Incorrect HW type code of Mini Node (SMZ430) in compatibility check: system part/application part.

362
10004_22 2008 Tellabs.
Unit Software Version Dependencies in Discontinued Products
36 Unit Software Version Dependencies in Discontinued Products

The unit software version dependencies of discontinued Tellabs 8100/MartisDXX products are listed below.
36.1 AIU Unit: ABZ531 Unit Software

The software ABZ531 is used on the DXX processor module (ABU) of AIU unit in Midi, Basic and Cluster Nodes. The version 1.3 can be downloaded to AIU units having the version 1.y of ABZ531 (where y=0, 1, 2...). The software ACZ7001 is used on the ATM processor module (ACP514) of AIU. See the corresponding release note for more information.
36.1.1 Version 1.3
Changing Functional testing for AIU1:1 and AIU1:4. (CRF ID 4004812)
Dependencies

ABU257 hardware version must be 1.0 or 3.0 or higher. CCU (SCZ286) software version must be 2.4 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version must be 10.1 or higher. GMX (GMZ544) software version must be 3.5 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.11 or higher. MartisDXX Manager support for the AIU is available in Release 9.0A-3 or higher.
10004_22 2008 Tellabs.

363
Restrictions

Before updating ABZ531 software from the earlier version make sure that the ATM Processor Module (ACP) software ACZ7001 version is 1.2 or higher. No software support for production testing.
Bugs
No known bugs.
36.1.2 Version 1.2
Dependencies

ABU257 hardware version must be 1.0 or higher. CCU (SCZ286) software version must be 2.4 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version must be 10.1 or higher. GMX (GMZ544) software version must be 3.5 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.11 or higher. MartisDXX Manager support for the AIU is available in Release 9.0A-3 or higher.
Restrictions
Before updating ABZ531 software from the earlier version make sure that the ATM Processor Module (ACP) software ACZ7001 version is 1.2 or higher.
Bugs
No known bugs.

364
10004_22 2008 Tellabs.
36.1.3 Version 1.1
Dependencies

Restrictions

Before updating ABZ531 software from the earlier version make sure that the ATM Processor Module (ACP) software ACZ7001 version is 1.2 or higher. Locking and unlocking >2Mbit/s virtual trunk interfaces in A111 node often fails.
Bugs
No known bugs.
10004_22 2008 Tellabs.

365
36.1.4 Version 1.0

Dependencies

Restrictions
When updating ABZ 531 software it is strongly recommended that the software of the ATM Processor Module (ACP) is updated first if the version of ACZ7001 software is 1.1 or earlier.
Bugs
The locking state (locked/unlocked) of an ATM virtual trunk interface may become incorrect in the following cases: MartisDXXprocessor software restarts without reseting the ATM processor software (for example after downloading a new version of ABZ 531), or a node inventory operation (add/remove AIU, create/delete inventory) is performed very soon after inserting a unit into the node. Unnecessary 16/20 MHz clocks not locked alarms may exist in the alarm reports of AIU. These alarms should always be ignored. Removing a replacement AIU from the node (approximately within 60 seconds after a reset) before it has been able to restore all of the backup parameters may prevent the AIU from being taken into the node inventory in another slot.

366
10004_22 2008 Tellabs.
36.2 AIU Unit/Module ACP514: ACZ7000 Boot Software

ACZ7000 is a boot software starting up the ACP 514 module. ACP 514 is a part of the ATM interface unit designed to enhance the capability of Basic and Cluster Nodes.
36.2.1 Version 1.0
Dependencies
The version 1.0 is to be flashed to ACP 514 Release 02 (PCB Code 760051402).
Restrictions
No method in use to identify application software.
Bugs
No known bugs.
36.3 AIU Unit: ACZ7001 Unit Software

The software ACZ7001 is used on the ATM processor module (ACP) of AIU unit (whose base unit is ABU257) in the Tellabs 8140 midi, Tellabs 8150 basic, Tellabs 8160 A111 and Tellabs 8170 cluster nodes. The version 1.5 can be downloaded to AIU units having the version 1.x of ACZ7001. The software ABZ531 is used on the ABU257 base unit of AIU. See the corresponding release note for more information. The production testing support can be used with ABZ531 v. 1.3 or higher.
36.3.1 Version 1.5

Changing functional testing for AIU1:1 and AIU1:4. (CRF ID 4004813)
Dependencies

ACP514 hardware version must be 1.0 or higher. ABP551 hardware version must be 1.0 or higher. ABP551 software (downloadable FPGA) version must be 2.6 or higher to support Tellabs 8170 cluster node. ABP513 hardware version must be 1.0 or higher. ABP513 software (downloadable FPGA) version must be 1.2 or higher.
10004_22 2008 Tellabs.

367
AIU (ABZ531) software must be 1.0 or higher CCU (SCZ286) software version must be 2.4 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version must be 10.1 or higher. GMX (GMZ544) software version must be 3.5 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.11 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for the AIU is available in Release 9.0A-3 or higher.
Restrictions

Cell counters in Motorola ASIC are not correct in some cases. OAM continuity check is not guaranteed to work with other vendors implementations. SNMP agent is no longer supported.
Bugs
No known bugs.
36.3.2 Version 1.4

Dependencies

ACP514 hardware version must be 1.0 or higher. ABP551 hardware version must be 1.0 or higher. ABP551 software version must be 2.6 or higher. ABP513 version must be 1.2 or higher. CCU (SCZ286) software version must be 2.4 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version must be 10.1 or higher. GMX (GMZ544) software version must be 3.5 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.11 or higher.

368
10004_22 2008 Tellabs.
MartisDXX Manager support for the AIU is available in Release 9.0A-3 or higher.
Restrictions

Cell counters in Motorola ASIC are not correct in some cases. OAM continuity check is not guaranteed to work with other vendors implementations. SNMP agent is no longer supported. No software support for production testing.
Bugs
No known bugs.
36.3.3 Version 1.3

Dependencies

ACP514 hardware version must be 1.0 or higher. CCU (SCZ286) software version must be 2.4 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version must be 10.1 or higher. GMX (GMZ544) software version must be 3.5 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.11 or higher. MartisDXX Manager support for the AIU is available in Release 9.0A-3 or higher.
Restrictions

Cell counters in Motorola ASIC are not correct in some cases. OAM continuity check is not guaranteed to work with other vendors implementations. Configuration of SNMP-related parameters (IP address, SNMP managers, etc) does not work with older MartisDXX Manager releases (older than Release 10.0A). The actual values of MIB variables can be set only by SNMP. These variables are sysName, sysLocation, sysContact, ifAlias and ifLinkUpDownTrapEnable. All MartisDXX Manager settings related to these variables do not affect to the actual MIB variables and SNMP functionality.
Bugs
Newly created ATM circuits do not always work. (CRF 4003503)
10004_22 2008 Tellabs.

369
36.3.4 Version 1.2

Dependencies

Restrictions

Cell counters in Motorola ASIC are not correct in some cases. OAM continuity check is not guaranteed to work with other vendors implementations.
Bugs
Newly created ATM circuits do not always work. (CRF 4003503).

370
10004_22 2008 Tellabs.
36.3.5 Version 1.1

Dependencies

Restrictions

Maximum 60 VP cross-connections are supported. Transmission of cells with GFC bits set is not guaranteed. Cell counters in Motorola ASIC are not correct in some cases. OAM continuity check is not guaranteed to work with other vendors implementations.
Bugs

LCD condition of virtual trunk IF and some minor faults are not recognized. FMO Abort function does not work properly. Access Interface uses idle cells instead of unassigned cells for dell delineation. Locked status can be erroneously changed to unlocked for virtual trunk IF. Newly created ATM circuits do not always work (CRF 4003503).
10004_22 2008 Tellabs.

371
36.3.6 Version 1.0

Dependencies

Restrictions

Maximum 60 VP cross-connections are supported. Transmission of cells with GFC bits set is not guaranteed. Cell counters in Motorola ASIC are not correct in some cases. OAM continuity check is not guaranteed to work with other vendors implementations.
Bugs

Improper configuration of STM-1 interface may cause cells to be dropped. Incompatible with ABP551 from v.2.4 onwards.

372
10004_22 2008 Tellabs.
36.4 CCO and CCS Units: CCZ445 Unit Software

The software CCZ445 is used on CCO and CCS units.
36.4.1 Version 1.2

This version contains fixes for the dial tone delay problems and CLI support. Masking of ring signal when the handset is lifted has been improved as well. There have been three intermediate test versions: 1.102, 1.104 and 1.106. Version 1.106 is the same as r1.2, except that the version number has changed. The following changes have been made between 1.1 and 1.2:

Read/write operations of combo-codec chip have been optimized to speed up the off-hook response time (1.102, 1.104 and 1.106). CLI support has been added (1.104 and 1.106). Masking of the A-bit downstream (Ring Signal) has been improved to filter ring noise (1.104 and 1.106). Filtering of CCOs Overload and PBX Voltage alarms has been improved (1.104 and 1.106). Filtering of CCSs Power 50V alarm has been improved slightly (1.104 and 1.106). A bug which sometimes left ports blocked after reset on CCS has been fixed (1.106).
Dependencies
New hardware revisions are required to support the Caller ID feature, but this version can be used with the current hardware.
Restrictions
No restrictions.
Bugs
Hotline (CCS-CCS) feature works differently from previous releases: if the handset is lifted at the other end, the other phone always rings if it is on-hook.
This is due to changes that were made to filter ring noise (CCO-CCS application), which was a problem with r1.1 and CLI-enhanced hardware.
10004_22 2008 Tellabs.

373
36.4.2 Version 1.1

Dependencies
MartisDXX Manager support for this unit is available in release 8.0A.
Restrictions
No support for CLI.
Bugs

Delay in dial tone. Audible ring noise. CCOs Overload and PBX voltage faults in heavy use. CCS may leave the port blocked after reset until the phone goes off-hook.
36.4.3 Version 1.0

Dependencies
MartisDXX Manager support for this unit is available in release 7.1.
Restrictions

No support for CLI. No support for Finnish units and modules.
Bugs

Delay in dial tone. Audible ring noise. CCOs Overload and PBX voltage faults in heavy use. CCS may leave the port blocked after reset until the phone goes off-hook. Blocked bit value does not go through MartisDXX from CCS to CCO. Overload fault does not block interface. In CCS off-hook state ring bit coming from MartisDXX is written directly to the interface. This produces audible noise in the phone. Overload and PBX voltage loss fault conditions are not valid.

374
10004_22 2008 Tellabs.
36.5 CEU Unit: ABP732 Unit Software

The software ABP732 is used on CEU unit (whose base unit is ABP732) in the Tellabs 8140 midi, Tellabs 8150 basic, Tellabs 8160 A111 and Tellabs 8170 cluster nodes. The version 1.019 can be downloaded to CEU units having the version 1.018 of ABP732. The ABZ607 and ACZ7004 software are used on the other modules of CEU. See the corresponding release notes for more information.
36.5.1 Version 1.019

Dependencies

ABP732 hardware version must be 1.0 or higher. ACP735 (ACZ7004) software version must be 1.0 or higher. ABU257 (ABZ607) software version must be 1.0 or higher. CCU (SCZ286) software version must be 2.5 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version must be 10.1 or higher. GMX (GMZ544) software version must be 3.15 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.11 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit functionality is available in Release 12 or higher.
Restrictions
No restrictions.
Bugs
No known bugs.
10004_22 2008 Tellabs.

375
36.5.2 Version 1.018

Dependencies

ABP732 hardware version must be 1.0 or higher. ACP735 (ACZ7004) software version must be 1.0 or higher. ABU257 (ABZ607) software version must be 1.0 or higher. CCU (SCZ286) software version must be 2.5 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version must be 10.1 or higher. GMX (GMZ544) software version must be 3.15 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.11 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit functionality is available in Release 12 or higher.
Restrictions
No restrictions.
Bugs
No known bugs.

376
10004_22 2008 Tellabs.
36.6 CEU Unit: ABZ607 Unit Software

The software ABZ607 is used on CEU unit (whose base unit is ABU257) in the Tellabs 8140 midi, Tellabs 8150 basic, Tellabs 8160 A111 and Tellabs 8170 cluster nodes. The version 2.0 can be downloaded to CEU units having the version 2.y of ABZ607 (where y=0, 1, 2, ...). The ACZ7004 software is used on the ATM processor module of CEU. See the corresponding release notes for more information.
36.6.1 Version 2.1

This is a non-production version based on version 2.0. Enhancements and Fixed Bugs
CAS alignment corrected for cluster node.
Dependencies

ABU257 hardware version must be 2.0 or higher. ACP735 (ACZ7004) software version must be 2.0 or higher. ABP732 (ABP732) software version must be 1.018 or higher. CCU (SCZ286) software version must be 2.5 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version must be 10.1 or higher. GMX (GMZ544) software version must be 3.15 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.11 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit functionality is available in Release 12A or higher.
Restrictions
No restrictions.
Bugs
No known bugs.
10004_22 2008 Tellabs.

377
36.6.2 Version 2.0


In band management channels in all (32pcs) 2M framed connections. Recovered clock from STM-1 interface can be delivered to either (SYB 1, 2) of the synchronization buses of the node. QOS and QOSTR errors GPT codes changed from 60 to 49. G.826 Limit Event added (GPT 91).
Dependencies

ABU257 hardware version must be 2.0 or higher. ACP735 (ACZ7004) software version must be 2.0 or higher. ABP732 (ABP732) software version must be 1.018 or higher. CCU (SCZ286) software version must be 2.5 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version must be 10.1 or higher. GMX (GMZ544) software version must be 3.15 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.11 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit functionality is available in Release 12A or higher.
Restrictions
No restrictions.
Bugs
No known bugs.

378
10004_22 2008 Tellabs.
36.6.3 Version 1.0

Dependencies

ABU257 hardware version must be 2.0 or higher. ACP735 (ACZ7004) software version must be 1.0 or higher. ABP732 (ABP732) software version must be 1.0 or higher. CCU (SCZ286) software version must be 2.5 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version must be 10.1 or higher. GMX (GMZ544) software version must be 3.15 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.11 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit functionality is available in Release 12 or higher.
Restrictions

DXX control-channels are not supported. Synchronization buses of the node are not supported.
Bugs
No known bugs.
10004_22 2008 Tellabs.

379
36.7 CEU Unit: ACZ7004 Unit Software

The software ACZ7004 is used on CEU unit (whose base unit is ACP735) in the Tellabs 8140 midi, Tellabs 8150 basic, Tellabs 8160 A111 and Tellabs 8170 cluster nodes. The version 2.1 can be downloaded to CEU units having the version 1.y of ACP735 (where y=0, 1, 2...). The ABZ607 software is used on the DXX processor module of CEU. See the corresponding release notes for more information.
36.7.1 Version 2.1

This is a non-production version based on version 2.0. Enhancements and Fixed Bugs (compared with version 2.0)
Deleting a logical port may cause bit errors to another logical port. (CRF ID 4005184)
Dependencies

ACP735 hardware version must be 1.0 or higher. ABU257 (ABZ607) software version must be 2.0 or higher. ABP732 (ABP732) software version must be 1.018 or higher. CCU (SCZ286) software version must be 2.5 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version must be 10.1 or higher. GMX (GMZ544) software version must be 3.15 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.11 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit functionality is available in Release 12A or higher.
Restrictions

CEU logical port performance (AAL1 level) counters are not correct in some cases. Compatibility with other vendors circuit emulation units is not guaranteed.

380
10004_22 2008 Tellabs.
36.7.2 Version 2.0


In band management channels in all (32pcs) 2M framed connections. Recovered clock from STM-1 interface can be delivered to either (SYB 1, 2) of the synchronization buses of the node. QOS and QOSTR errors GPT codes changed from 60 to 49. added G.826 Limit Event (GPT 91).
Dependencies

ACP735 hardware version must be 1.0 or higher. ABU257 (ABZ607) software version must be 2.0 or higher. ABP732 (ABP732) software version must be 1.018 or higher. CCU (SCZ286) software version must be 2.5 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version must be 10.1 or higher. GMX (GMZ544) software version must be 3.15 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.11 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit functionality is available in Release 12A or higher.
Restrictions

CEU logical port performance (AAL1 level) counters are not correct in some cases. Compatibility with other vendors circuit emulation units is not guaranteed.
Bugs
Deleting a logical port may cause bit errors to another logical port
10004_22 2008 Tellabs.

381
36.7.3 Version 1.0

Dependencies

ACP735 hardware version must be 1.0 or higher. ABU257 (ABZ607) software version must be 1.0 or higher. ABP732 (ABP732) software version must be 1.0 or higher. CCU (SCZ286) software version must be 2.5 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version must be 10.1 or higher. GMX (GMZ544) software version must be 3.15 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.11 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit functionality is available in Release 12 or higher.
Restrictions

CEU logical port performance (AAL1 level) counters are not correct in some cases. Compatibility with other vendors circuit emulation units is not guaranteed. In band management channels in all (32pcs) 2M framed connections is not supported. Clock recovery from STM-1 interface is not supported.
Bugs
QOS and QOSTR errors have a wrong GPT code.

382
10004_22 2008 Tellabs.
36.8 ECS Unit: UBZ439 Unit Software

The software UBZ439 is used on ECS units.
36.8.1 Version 1.7

Dependencies
MartisDXX Manager support for this unit is available in Release 9.0.
Restrictions
No restrictions.
Bugs
No known bugs.
36.9 EPS-5T and EPS-10T Units: UBZ441 Unit Software

The software UBZ441 is used on EPS-5T and EPS-10T units.
36.9.1 Version 3.6

Dependencies (for High Speed Modem Operation)

EPS441 hardware with versions 2.0 and above. MartisDXX Manager support for this unit is available in Release 10.0A-2 (OS2) and 10.1A (NT). See restrictions below. SXU hardware version 5, USW version 10.2. Note: USW version 10.2 fixed a 10.1 restriction concerning clear channel operation at 2400 baud or less.
Restrictions
When used with MartisDXX Manager release 10.0 or 10.1, CLCs that are added to a CCG when the CCG is in the Planned state will not be properly written to hardware when the CCG state is raised from Planned. In order to be properly configured, a CLC should be added to a CCG only when the state of the CCG is Installed or In USE. Additionally, if the state of a CCG is lowered to Planned, any CLCs should be deleted from the CCG prior to raising the state of the CCG. For reliable clear channel operation, it is recommended that switching to a clear channel be done on detecting 2100 Hz, and the optional 2100 Hz with phase reversal not be used.
10004_22 2008 Tellabs.

383
Bugs
EPS 8 kb/s compressed channel may lock up after about 6000 fax transmissions, the channel will stop operation. This lock up situation can be released by disconnecting and again connecting the channel by NMS. Alternative way to release the lock up is to make a reset to the whole EPS unit.
36.9.2 Version 3.5


EPS441 hardware with versions 2.0 and above. MartisDXX Manager support for this unit is available in Release 10.0A-2 (OS2) and 10.1A (NT). See restrictions below. SXU hardware version 5, USW version 10.1.
Restrictions
When used with MartisDXX Manager release 10.0 or 10.1, CLCs that are added to a CCG when the CCG is in the Planned state will not be properly written to hardware when the CCG state is raised from Planned. In order to be properly configured, a CLC should be added to a CCG only when the state of the CCG is Installed or In USE. Additionally, if the state of a CCG is lowered to Planned, any CLCs should be deleted from the CCG prior to raising the state of the CCG. For reliable clear channel operation, it is recommended that switching to a clear channel be done on detecting 2100 Hz, and the optional 2100 Hz with phase reversal not be used. Clear channel operation at modem speeds of 2400 baud or less may switch back to compressed operation due to a short time out setting on the SXU282, version 10.1. Clear channel fax operation at any speed is not affected. When issuing S-Commands from the Unit Debugger for Clear Channel operation, avoid duplicate CcgId & CmcId on separate Channels which inhibits Activation and switching to a clear channel. MartisDXX Manager operation, however, is not capable of assigning specific CcgId & CmcId. This problem can be avoided if all the EPS Channels are utilised. See bugs below.
Bugs
EPS Clear Channel memory is capable of retaining duplicate CcgId & CmcId in separate Configuration Channels, which inhibits Activation and switching to a Clear Channel. This duplication is possible when an EPS Channel is Activated, then deleted, and Activated on a different EPS Channel using the same CcgId & CmcId.

384
10004_22 2008 Tellabs.
36.9.3 Version 2.6


EPS441 hardware with versions less than 2.0. MartisDXX Manager support for this unit is available in Release 10.0A-2 (OS2) and 10.1A (NT). See restrictions below. SXU hardware version 5, USW version 10.2. Note: USW version 10.2 fixed a 10.1 restriction concerning Clear Channel operation at 2400 baud or less.
Restrictions
When used with MartisDXX Manager release 10.0 or 10.1, CLCs that are added to a CCG when the CCG is in the Planned state will not be properly written to hardware when the CCG state is raised from Planned. In order to be properly configured, a CLC should be added to a CCG only when the state of the CCG is Installed or In USE. Additionally, if the state of a CCG is lowered to Planned, any CLCs should be deleted from the CCG prior to raising the state of the CCG. For reliable Clear Channel operation, it is recommended that switching to a Clear Channel be done on detecting 2100 Hz, and the optional 2100 Hz with phase reversal not be used.
Bugs
No known bugs.
36.9.4 Version 2.5


EPS441 hardware with versions less than 2.0. MartisDXX Manager support for this unit is available in Release 10.0A-2 (OS2) and 10.1A (NT). See restrictions below. SXU hardware version 5, USW version 10.1.
Restrictions
When used with MartisDXX Manager release 10.0 or 10.1, CLCs that are added to a CCG when the CCG is in the Planned state will not be properly written to hardware when the CCG state is raised from Planned. In order to be properly configured, a CLC should be added to a CCG only when the state of the CCG is Installed or In USE. Additionally, if the state of a CCG is lowered to Planned, any CLCs should be deleted from the CCG prior to raising the state of the CCG. For reliable Clear Channel operation, it is recommended that switching to a Clear Channel be done on detecting 2100 Hz, and the optional 2100 Hz with phase reversal not be used. Clear Channel operation at modem speeds of 2400 baud or less may switch back to Compressed operation due to a short Time Out setting on the SXU282, version 10.1 Clear Channel Fax operation at any speed is not affected.
10004_22 2008 Tellabs.

385
When issuing S-Commands from the Unit Debugger for Clear Channel operation, avoid duplicate CcgId & CmcId on separate Channels which inhibits Activation and switching to a Clear Channel. MartisDXX Manager operation, however, is not capable of assigning specific CcgId & CmcId. This problem can be avoided if all the EPS Channels are utilised. See bugs below.
Bugs
EPS Clear Channel memory is capable of retaining duplicate CcgId & CmcId in separate Configuration Channels, which inhibits Activation and switching to a Clear Channel. This duplication is possible when an EPS Channel is Activated, then deleted, and Activated on a different EPS Channel using the same CcgId & CmcId.
36.9.5 Version 2.4


EPS441 hardware with versions less than 2.0. MartisDXX Manager support for this unit is available in Release 10.0A-2 (OS2) and 10.1A (NT). See restrictions below. SXU hardware version 5, USW version 10.1.
Restrictions
When used with MartisDXX Manager release 10.0 or 10.1, CLCs that are added to a CCG when the CCG is in the Planned state will not be properly written to hardware when the CCG state is raised from Planned. In order to be properly configured, a CLC should be added to a CCG only when the state of the CCG is Installed or In USE. Additionally, if the state of a CCG is lowered to Planned, any CLCs should be deleted from the CCG prior to raising the state of the CCG. Fax operation through a Clear Channel with EPS 8kbit/s Transmission Rate must have EPS FAX set to OFF. Fax operation without Clear Channel does not operate reliably with EPS 8kbit/s Transmission Rate. EPS load 2.0 supports fax operation not using Clear Channel with 8 kbit/s Transmission Rate. For reliable Clear Channel operation, it is recommended that switching to a Clear Channel be done on detecting 2100 Hz, and the optional 2100 Hz with phase reversal not be used. Clear Channel operation at modem speeds of 2400 baud or less may switch back to Compressed operation due to a short Time Out setting on the SXU282, version 10.1 Clear Channel Fax operation at any speed is not affected. When issuing S-Commands from the Unit Debugger for Clear Channel operation, avoid duplicate CcgId & CmcId on separate Channels which inhibits Activation and switching to a Clear Channel. MartisDXX Manager operation, however, is not capable of assigning specific CcgId & CmcId. This problem can be avoided if all the EPS Channels are utilised. See bugs below.

386
10004_22 2008 Tellabs.
Bugs

Sync loss during fax operation with EPS 8 kbit/s Transmission Rate with EPS FAX settings NSF DISABLED and NSF ENABLED. EPS Clear Channel memory is capable of retaining duplicate CcgId & CmcId in separate Configuration Channels, which inhibits Activation and switching to a Clear Channel. This duplication is possible when an EPS Channel is Activated, then deleted, and Activated on a different EPS Channel using the same CcgId & CmcId.
36.9.6 Version 2.0

Dependencies
The MartisDXX Manager support for these units is available in Release 8.0.
Restrictions
No restrictions.
Bugs
No known bugs.
36.10 ESO Unit: ESZ8000 Boot Software

ESZ8000 is the boot software which starts up the ESO-570 hw-module. The ESO-570 is a part of the ESO V5.1 Signaling Server Unit, designed to enhance the capability of DXX Basic and DXX Cluster Nodes.
36.10.1 Version 1.4

Dependencies
Version 1.4 is to be flashed to ESO-570 Release 01 (PCB Code 760057001).
Restrictions
Must be used with ESZ8001 application software version 2.0 or higher.
Bugs
No known bugs.
10004_22 2008 Tellabs.

387
36.11 ESO Unit: ESZ8001 Unit Software

The software ESZ8001 is used on the ESO unit (whose base unit is ESO 570) in the Tellabs 8140 midi and Tellabs 8150 basic nodes. The version 2.9 can be downloaded to ESO units having the version 2.y of ESZ8001 (where y= 5, 6, 7...).
36.11.1 Version 2.9

This version provides support for PSTN user ports.
Dependencies

UBU processor module software (UBZ536) version must be at least 2.4. MartisDXX Manager support for ESO is available in Release 10.0A. ESZ boot (ESZ8000) software version must be at least 1.4. SCU-H (SCZ545) software version must be 1.6 or higher. SCU (SCZ280) software version must be at least 8.4. HDLC-4CH (SCP211) (SCZ281) software version must be at least 3.1. XCG (SMZ538) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. SXU-A/B (SXZ282) software version must be at least 6.9. GMH (GMZ283) software version must be at least 6.9.
Restrictions
There are no known restrictions.
Bugs
There are no known bugs.

388
10004_22 2008 Tellabs.
36.11.2 Version 2.8

This is a non-production version based on version 2.7. Enhancements and Fixed Bugs This version contains the solution for the following CRs:

Abnormal drop of L1 between ESO and ISD-LT. (CR ID 200005437) ESO is too sensitive to port configuration mismatch between AN and LE. (CR ID 200004985) The version also includes support for version 2 of the ETSI V5 Standard.
Dependencies

Restrictions
This version supports only ISDN user ports; PSTN user ports are not supported.
Bugs
There are no known bugs.
10004_22 2008 Tellabs.

389
36.11.3 Version 2.7

Enhancements and Fixed Bugs This version contains the solution for the following change requests: 1. 2. 3. 4. 5. 6. 7. 8. 9. V5.1 link recovery problem when using C-channel data service in multiple channel setting. PortType of Semi permanent leased line not allowed for ISDN ports. Incorrect error code from USW causes incorrect error message displayed in Tellabs 8100 manager when requesting restart using unlocked variant. Request restart returns misleading error code. Checking not done for variant 0x14. CurrentAnVariantID goes to FF even when interface Restarted. PSTN port unblocking problem in ESO when requested from LE side. Software corrupted when using large download block sizes. CCS-UNI signalling conversion for V5.1, Spain country mapping.
10. Base register: bits controlling CS requires checking, changing. Dependencies

Restrictions
No restrictions.
Bugs
No known bugs.

390
10004_22 2008 Tellabs.
36.11.4 Version 2.6

This version contains the solution for CRF ID 4002782.
Dependencies

UBU processor module software (UBZ536) version must be at least 2.4. MartisDXX Manager support for ESO is available in Release 10.0A. ESZ boot (ESZ8000) software version must be at least 1.4. SCU (SCZ280) software version must be at least 8.4. HDLC-4CH (SCP211) (SCZ281) software version must be at least 3.1. SXU-A/B (SXZ282) software version must be at least 6.9. GMH (GMZ283) software version must be at least 6.9.
Restrictions
No restrictions.
Bugs
No known bugs.
36.11.5 Version 2.5

This version contains the solution for CRF ID 4002375.
Dependencies

UBU processor module software (UBZ536) version must be at least 2.4. MartisDXX Manager support for ESO is available in Release 10.0A. ESZ boot (ESZ8000) software version must be at least 1.4. SCU (SCZ280) software version must be at least 8.4 HDLC-4CH (SCP211) (SCZ281) software version must be at least 3.1 SXU-A/B (SXZ282) software version must be at least 6.9 GMH (GMZ283) software version must be at least 6.9
Restrictions
No restrictions.
Bugs
No known bugs.
10004_22 2008 Tellabs.

391
36.11.6 Version 2.2

This version contains the implementation of the national PSTN-V5 mapping for the country of Chile.
Dependencies

UBU processor module software (UBZ536) version must be at least 2.3. MartisDXX Manager support for ESO is available in Release 10.0A. ESZ boot (ESZ8000) software version must be at least 1.4. SCU (SCZ280) software version must be at least 8.4. HDLC-4CH (SCP211) (SCZ281) software version must be at least 3.1. SXU-A/B (SXZ282) software version must be at least 6.9. GMH (GMZ283) software version must be at least 6.9.
Restrictions
No restrictions.
Bugs
No known bugs.
36.11.7 Version 1.0

Dependencies

UBU processor module software version must be at least 1.0. MartisDXX Manager support for ESO is available in Release 10.0A. ESO in Tellabs 8150 basic node: SCU SXU GMH SCZ280 software version must be at least 8.4 SXZ282 software version must be at least 6.9 GMZ283 software version must be at least 6.9 HDLC-4CH (SCP211) SCZ281 software version must be at least 3.1
Restrictions

14 ISDN circuits per link allowed in this version. CAE is not supported.
Bugs
No known bugs.

392
10004_22 2008 Tellabs.
36.12 ESO Unit: UBZ 536 Unit Software

The software UBZ536 is used on the ESO unit (whose base unit is UBU254) in the Tellabs 8140 midi and Tellabs 8150 basic nodes. The version 2.4 can be downloaded to ESO units having the version 2.y of UBZ536 (where y=0, 1, 2...).
36.12.1 Version 2.4

Contains support for CustomSettings configuration attribute of NMS object 0x80 (ESO_OBJECT). If this attribute is set to 0x01, the feature of ignoring the ISDN deactivation message from the Local Exchange will be turned on.
Dependencies

ESO (base unit UBU254) hardware version must be 2.0 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version can be any. GMH (GMZ283) software version must be 6.9 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. ISD-LT (UBZ534) software version must be 1.0 or higher ESO570 processor module software (ESZ8001) version must be at least 2.5. MartisDXX Manager support for this unit is available in Release 10.0A or higher.
Restrictions
No restrictions.
Bugs
No known bugs.
10004_22 2008 Tellabs.

393
36.13 FBU Unit: FBZ612 Unit Software

The software FBZ612 is used on FBU unit (whose base unit is FBU763) in the Tellabs 8140 midi, Tellabs 8150 basic, Tellabs 8160 A111 and Tellabs 8170 cluster nodes.
36.13.1 Version 1.2
Dependencies

FBU base unit (FBU763) hardware version must be 1.1 or higher. FBU framer module (FFM765) hardware version must be 1.0 or higher. FBU interface module (FIM764) hardware version must be 1.0 or higher. FBU processor module (SCM766) hardware version must be 2.0 or higher. FBU power supply module (PDF767) hardware version must be 1.0 or higher. CCU (SCZ286) software version can be any version. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.0 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version must be 10.1 or higher. GMX (GMZ544) software version must be 3.8 or higher. SXU-A/B (SXZ282) software version must be 6.5 or higher. SXU-C (SXZ289) software version must be 2.7 or higher. SXU-V (SXZ630) software version can be any version. SXU-V (ESZ80003) software version can be any version. FBU framer module (FFM765) software version must be S35755.01.A0 (Nokia part USW). MartisDXX Manager support for this unit is available in Release 12A SP1 or higher. The FBU Manager version should be C1.0 or later (Nokia manager).
Restrictions
Only 3 HDLC links are recommended. In any case, the NNM can be activated in all 16 interfaces, but the NMS should not use them all as a control channel.
Bugs
No known bugs.

394
10004_22 2008 Tellabs.
36.14 FRU Unit: UBZ534 Unit Software

The software UBZ534 is used on the DXX processor module (UBU) of FRU unit (whose base unit is UBU259) in Tellabs 8150 basic, Tellabs 8160 A111 and Tellabs 8170 cluster nodes. The version 1.4 can be downloaded to FRU units having the version 1.y of UBZ534 (where y=0, 1, 2...). The software FRZ535 is used on the FRE processor module of FRU.
36.14.1 Version 1.5

Setting 0 kbit/s CIR value to FR circuit (PVC) is allowed (CRF 4005120).
Dependencies

FRU (base unit UBU259) hardware version must be 1.0 or higher. FRE processor module software (FRZ535) version must be 1.0 or higher. CCU (SCZ286) software version must be 2.2 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. CXU-M (SXZ288) software version must be 2.12 or higher. GMX (GMZ544) software version must be 3.2 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.11 or higher. SXU-V (SXZ630) software version must be 1.1 or higher GMH (GMZ283) software version must be 6.9 or higher. MartisDXX Manager support for setting the congestion threshold to a user type logical port is available in Release 9.0b, emergency update 6 or higher. MartisDXX Manager support for overbooking of logical port is available in Release 11 Service Pack 2 or higher. MartisDXX Manager support for setting the congestion threshold to a trunk type logical port is available in Release 11 Service Pack 3 or higher.
Restrictions
FRU initialization can take more than 10 minutes in a heavily configured unit.
10004_22 2008 Tellabs.

395
36.14.2 Version 1.4

If congestion rate of a logical port exceeds the congestion threshold of that port, fault condition FR logical port one minute congestion threshold exceeded will be set. (CRF ID 4004172)
Dependencies

FRU (base unit UBU259) hardware version must be 1.0 or higher. FRE processor module software (FRZ535) version must be 1.0 or higher. CCU (SCZ286) software version must be 2.2 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. CXU-M (SXZ288) software version must be 2.12 or higher. GMX (GMZ544) software version must be 3.2 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.11 or higher. SXU-V (SXZ630) software version must be 1.1 or higher GMH (GMZ283) software version must be 6.9 or higher. MartisDXX Manager support for setting the congestion threshold to a user type logical port is available in Release 9.0b, emergency update 6 or higher. MartisDXX Manager support for overbooking of logical port is available in Release 11 Service Pack 2 or higher. MartisDXX Manager support for setting the congestion threshold to a trunk type logical port is available in Release 11 Service Pack 3 or higher.
Restrictions
Bugs
When a new UBU load is downloaded via the File Manager, it is possible that the File Manager will get error 707, (Get Operation failure. Operation 3 (GET) reject 253 locking error). This happens after the UBU load has been downloaded and when the FRE is reinitialising. During the initialization period when data is being backed up, the NMS is prevented from querying the FRE. If the back up is not complete when the node manager makes a request to query data from the FRE, it is prevented from doing this and the error occurs. This does not invalidate the download. It is successful. After the UBU initialization is completed, if the file manager is closed and then re-opened, the downloaded UBU load is shown to be active.

396
10004_22 2008 Tellabs.
36.14.3 Version 1.3

Enhancements

Overbooking of logical ports is enabled.(CRF ID 4003740) Start time of 24h performance period is set to 00:00 after reset (CRF ID 4003385). Modified performance statistics quering of a circuit (CRF ID 4003385).
Dependencies

FRU (base unit UBU259) hardware version must be 1.0 or higher. FRE processor module software (FRZ535) version must be 1.0 or higher. CCU (SCZ286) software version must be 2.2 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. CXU-M (SXZ288) software version must be 2.12 or higher. GMX (GMZ544) software version must be 3.2 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.11 or higher. GMH (GMZ283) software version must be 6.9 or higher. MartisDXX Manager support for this unit is available in Release 9.0b, emergency update 6 or higher. MartisDXX Manager support for overbooking of logical port is available in Release 11 Service Pack 2 or higher.
Restrictions
Bugs
10004_22 2008 Tellabs.

397
36.14.4 Version 1.2

Dependencies

FRE processor module software (FRZ535) version must be 0.7 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher. SXU-C (SXZ289) software version must be 2.8 or higher. GMH (GMZ283) software version must be 6.9 or higher. MartisDXX Manager support for this unit is available in Release 9.0b, emergency update 6 or higher.
Restrictions

FRU initialization can take more than 10 minutes in a heavily configured unit. When upgrading to version 1.2, any existing frame relay circuits must be disconnected and the graceful discard status reset. Failure to do this will not correct the problem.
Bugs

398
10004_22 2008 Tellabs.
36.14.5 Version 1.1

Dependencies

Restrictions

FRU initialization can take more than 10 minutes in a heavily configured unit. If an FRU is downgraded from 1.2, any existing frame relay circuits must be disconnected and the graceful discard status must be reset to the opposite value that is desired. Failure to do this will cause an incorrect setting if the unit is reset or replaced.
Bugs
When a new UBU load is downloaded via the File Manager, it is possible that the File Manager will get error 707, (Get Operation failure. Operation 3 (GET) reject 253 locking error). This happens after the UBU load has been downloaded and when the FRE is reinitializing. During the period in the initialization when data is being backed up, the NMS is prevented from querying the FRE. If the back up is not complete when the node manager makes a request to query data from the FRE, it is prevented from doing this and the error occurs. This does not invalidate the download. It is successful. After the UBU initialization is completed, if the file manager is closed and then re-opened, the downloaded UBU load is shown to be active. Assignment of graceful discard on frame relay circuit is not done correctly in FRE. When graceful discard is set to ON by the NMS, it is set OFF in the FRE and vice versa. The user should set the graceful discard to the opposite value to the desired for it to work properly.
10004_22 2008 Tellabs.

399
36.14.6 Version 1.0

Dependencies

Restrictions

Only 512 PVCs are supported. FRU initialization can take more than 10 minutes in a heavily configured unit. If an FRU is downgraded from 1.2, any existing frame relay circuits must be disconnected and the graceful discard status must be reset to the opposite value that is desired. Failure to do this will cause an incorrect setting if the unit is reset or replaced.
Bugs
When a new UBU load is downloaded via the File Manager, it is possible that the File Manager will get error 707, (Get Operation failure. Operation 3 (GET) reject 253 locking error). This happens after the UBU load has been downloaded and when the FRE is reinitializing. During the period in the initialization when data is being backed up, the NMS is prevented from querying the FRE. If the back up is not complete when the node manager makes a request to query data from the FRE, it is prevented from doing this and the error occurs. This does not invalidate the download. It is successful. After the UBU initialization is completed, if the file manager is closed and then re-opened, the downloaded UBU load is shown to be active. If a user logical port is configured to have some type of LMI active, a fault will report that the LMI for the logical port is down, even if it is up. If a PRAM erase is performed, the entire FRU must be reset before re-configuring the unit. If only the FRE is reset, attempts to reconfigure a management DLCI which existed will fail. If the FRU is reset or replaced, the unit software will allow a new management DLCI to be created on a logical port where one already existed. Assignment of graceful discard on frame relay circuit is not done correctly in FRE. When graceful discard is set to ON by the NMS, it is set OFF in the FRE and vice versa. The user should set the graceful discard to the opposite value to the desired for it to work properly.

400
10004_22 2008 Tellabs.
36.15 FRU Unit/Module FRE: FRZ535 Unit Software

The software FRZ535 is used on the Frame Relay processor module (FRE) of FRU unit in Basic and Cluster Nodes. Release 0.1 of the FRZ535 software can be downloaded to the FRU. The software UBZ534 is used on the UBU processor module of FRU. See the corresponding release note for more information.
36.15.1 Version 0.1

Dependencies

UBU Processor Module software version must be at least 1.0. MartisDXX Manager support for FRU is available in Release 9.0b, emergency release 6 FRU in Basic Node:

SCU (SCZ280) software version must be at least 8.4. HDLC-4CH (SCP211) (SCZ281) software version must be at least 3.1. SXU (SXZ282) software version must be at least 6.9. GMH (GMZ283) software version must be at least 6.8. SCU (SCZ280) software version must be at least 8.4. HDLC-4CH (SCP211) (SCZ281) software version must be at least 3.1. SXU (SXZ289) software version must be at least 2.8. GMH (GMZ283) software version must be at least 6.8.
FRU in Cluster Node:

Restrictions
None (800 circuits are allowed).
Bugs
No known bugs.
10004_22 2008 Tellabs.

401
36.15.2 Version 0.7

Dependencies

UBU Processor Module software version must be at least 1.0. MartisDXX Manager support for FRU is available in Release 9.0b, emergency release 6. FRU in Basic Node:

SCU (SCZ280) software version must be at least 8.4. HDLC-4CH (SCP211) (SCZ281) software version must be at least 3.1. SXU (SXZ282) software version must be at least 6.9. GMH (GMZ283) software version must be at least 6.8. SCU (SCZ280) software version must be at least 8.4. HDLC-4CH (SCP211) (SCZ281) software version must be at least 3.1. SXU (SXZ289) software version must be at least 2.8. GMH (GMZ283) software version must be at least 6.8.
FRU in Cluster Node:

Restrictions
512 circuits allowed in this release.
Bugs
If a circuit has been created with a defined path using a node number instead of a trunk logical port, and the FRU resets, the node number is changed in the defined path to a trunk logical port. This could potentially cause traffic to be disrupted if the trunk now in the defined path goes down. If a circuit is created without adequate bandwidth available, the FRE gets into an unstable state. Circuit deletion can cause the FRE to lock up and a reset of the FRE will result in the loss of all configuration on the FRE.

402
10004_22 2008 Tellabs.
36.16 GCH-A Unit: GCZ284A Unit Software

The software GCZ284A is used on GCH-A units. Version 2.12 can be downloaded to GCH-A units with the revision 2.x of GCZ284A (where x = 0, 1, 2, ). Allowed HW versions for the base unit are 3.0, 3.1 and 4.0 if there are no dependencies or restrictions. This software requires SXZ282 version 5.4 or later.
36.16.1 Version 2.12

Dependencies
No dependencies.
Restrictions
No restrictions.
Bugs
No known bugs.
36.16.2 Version 2.11

Dependencies
No dependencies.
Restrictions
Does not support BTE64 and BTE384 module wetting current strapping info.
Bugs

V.54 loop activation is not according to spec. V.54. You cannot bring 106 delay back below 255.
10004_22 2008 Tellabs.

403
36.16.3 Version 2.10

Dependencies
No dependencies.
Restrictions

Does not support BTE64 and BTE384 module wetting current strapping info. GCH 221A version must be 3.0 or 3.1.
Bugs
No known bugs.
36.16.4 Version 2.9

Dependencies
No dependencies.
Restrictions

Bugs

Bit rates below 8 kbit/s do not work. NTU-A (SBM 64A) with Xb rate of 8 kbit/s does not work in the case of HW version 3.1. BTE 3 kbit/s does not work. BTE 768 does not work.

404
10004_22 2008 Tellabs.
36.16.5 Version 2.8

Dependencies
No dependencies.
Restrictions

Bugs

NTU-A (SBM 64A) with Xb rate of 8 kbit/s is erroneous. BTE 3 kbit/s does not work.
36.16.6 Version 2.7

Dependencies
No dependencies.
Restrictions

Does not support BTE64 and BTE384 module wetting current strapping info. GCH 221A version must be 3.0.
Bugs
An existing ASIC timing error (octet pulse) is corrected by software.
36.16.7 Version 2.6

Dependencies
No support of Rev. 3 IFMOD ASIC (HW version 3.1).
Restrictions

Does not support BTE64 and BTE384 module wetting current strapping info. No pmp cluster support. No SBM 64A support. GCH 221A version must be 3.0.
Bugs
BTE 3 kbit/s does not work.
10004_22 2008 Tellabs.

405
36.16.8 Version 2.5

Dependencies
No dependencies.
Restrictions

Does not support BTE64 and BTE384 module wetting current strapping info. GCH 221A version must be 3.0.
Bugs
No known bugs.
36.16.9 Version 2.4

Dependencies
No dependencies.
Restrictions

Does not support BTE64 and BTE384 module wetting current strapping info. No pmp locking object. No interface signal missing alarm (PMA) if wetting current is on and there is a line break/short-circuit. GCH 221A version must be 3.0
Bugs
Buffer slip alarms in the case of X30 framer.
36.16.10 Version 2.3

Dependencies
No dependencies.
Restrictions

Does not support BTE64 and BTE384 module wetting current strapping info. 8 kbit/s is not available. PMP Server functions not supported. GCH 221A version must be 3.0

406
10004_22 2008 Tellabs.
Bugs

Buffer sizes at >64 kbit/s are not optimal. In the case of X30 framer and no control channel, the connection capacity is too high. The alarm bit on V110 frame is inverted.
36.16.11 Version 2.0

Dependencies
No dependencies.
Restrictions

Does not support BTE64 and BTE384 module wetting current strapping info. 8 kbit/s is not available. PMP Server functions not supported. SXU IA testing not supported. BTE n x 3 kbit/s not supported. GCH 221A version must be 3.0.
Bugs

Some buffer lengths should be greater in the case of codirectional clocking. Some faults have zero GPT. If interface module is none, the unit informs of a Code error fault. In the case of N*64 kbit/s and V13 and CRC ON, the connection capacity is too high. In the case of X30 framer and no control channel, the connection capacity is too high. The alarm bit on the V110 frame is inverted. Starting problems with BTE modules after reset.
10004_22 2008 Tellabs.

407
36.17 GMU-M Unit: GMZ546 Unit Software

Two software products are needed on GMU-M unit. Software GMZ546 is for the main processor and software GMZ547 is for the ASIC processor. GMZ546 version 10.0 can be downloaded to GMU-Ms having the revision 10.y of GMZ546 (where y=0,1,2...).
36.17.1 Version 10.0

Dependencies

SCU software version must be at least 8.4. SCP software version must be at least 3.1. SXU-A/B software version must be at least 6.8. XCG software version must be at least 2.1. GMZ547 software version must be 10.0.
Restrictions

Control channel in VCs payload is not supported. Version 10.0 of GMU-M supports advanced SNC group configuration but in MartisDXX Manager this feature is supported in version 10.0 and later. If SNC groups are configured by earlier MartisDXX Manager releases, this may cause inconsistency between database and hardware. The user can minimize this problem by configuring monitoring TTPs of SNCgroup to the same values than the terminating TTP.
Bugs
No known bugs.

408
10004_22 2008 Tellabs.
36.18 GMU-M Unit: GMZ547 Unit Software

Two software products is needed on GMU-M unit. Software GMZ546 is for main processor and software GMZ547 is for asic processor. GMZ547 version 10.0 can be downloaded to GMU-Ms having the revision 10.y of GMZ547 (where y=0,1,2...).
36.18.1 Version 10.0

Dependencies GMZ546 software version must be 10.0. Restrictions

Control channel in VCs payload is not supported. Version 10.0 of GMU-M supports advanced SNC group configuration but in MartisDXX Manager this feature is supported in version 10.0 and later. If SNC groups are configured by earlier MartisDXX Manager releases, this may cause inconsistency between database and hardware. The user can minimize this problem by configuring monitoring TTPs of SNCgroup to the same values than the terminating TTP.
Bugs
No known bugs.
10004_22 2008 Tellabs.

409
36.19 ISD-LT and ISD-NT Units: UBZ532 Unit Software

The software UBZ532 is used on ISD-LT and ISD-NT units. The release 1.5 can be downloaded to ISD units having the version 1.y of UBZ532 (where y=0,1,2...).
36.19.1 Version 1.5

Enhancements
ISD-NT support for A111 node (CRF ID 4003825).
Dependencies

GMX (GMZ544) software version must be 3.8 or higher to support this enhancement. MartisDXX Manager support for this enhancement is available in Release R11 Service Pack 1 or higher. MartisDXX Manager from Release R11 SP1 supports new port creations of ISD-NT. MartisDXX Manager from Release R10.1A supports new port creations of ISD-LT.
Restrictions
Release R11 Service Pack 1 of MartisDXX Manager does not yet support ISD circuits between Basic node and A111 node.
Bugs
No known bugs.

410
10004_22 2008 Tellabs.
36.19.2 Version 1.4

Enhancements
ISD-LT support for A111 node (CRF ID 4001917).
Dependencies
MartisDXX Manager from Release R10.1A supports new port creations of ISD-LT.
Restrictions
No support for A111 node in ISD-NT.
Bugs
No known bugs.
36.19.3 Version 1.3

Dependencies
MartisDXX Manager Release R10.1A supports all new faults, ISD event logs and new degraded/excessive errored seconds management interface feature and all error counters (R10.0A service pack may support some of these things).
Restrictions

No support for A111 node in ISD-NT. No support for A111 node in ISD-LT.
Bugs
Some ISD units reports the Fault in Xilinx 2 fault and reconfigures FPGA without any real reason and every reconfiguration causes little break on traffic.
10004_22 2008 Tellabs.

411
36.19.4 Version 1.2

Dependencies
No dependencies.
Restrictions

No support for A111 node in ISD-NT. No support for A111 node in ISD-LT. No ISD event log support. No support for degraded/excessive errored seconds management interface. No support for all error counters.
Bugs

Some ISD units reports the Fault in Xilinx 2 fault and reconfigures FPGA without any real reason and every reconfiguration causes little break on traffic. When using (very) bad communication lines, the ISD unit may disappear from the node inventory and the unit cannot be configured. Sometimes the unit recovers from this by itself but sometimes it requires manual reset. In the G.821 statistics 24 hours last only for 23 hours and 45 minutes.
36.19.5 Version 1.1

Dependencies
No dependencies.
Restrictions


412
10004_22 2008 Tellabs.
Bugs

Some ISD units reports the Fault in Xilinx 2 fault and reconfigures FPGA without any real reason and every reconfiguration causes little break on traffic. When using (very) bad communication lines, the ISD unit may disappear from the node inventory and the unit cannot be configured. Sometimes the unit recovers from this by itself but sometimes it requires manual reset. In the G.821 statistics 24 hours last only for 23 hours and 45 minutes. The U interface activation process on ISD-NT does not work correctly if there is no NT1 device connected to ISD-LT.
36.19.6 Version 1.0

Dependencies
Full NMS support for this unit is available in MartisDXX Manger Release R9.0A.
Restrictions

Bugs

Some ISD units reports the Fault in Xilinx 2 fault and reconfigures FPGA without any real reason and every reconfiguration causes little break on traffic. When using (very) bad communication lines, the ISD unit may disappear from the node inventory and the unit cannot be configured. Sometimes the unit recovers from this by itself but sometimes it requires manual reset. In the G.821 statistics 24 hours last only for 23 hours and 45 minutes. The S interface not activated alarm does not get through the ISDs from the customer premises to exchange. The test loops do not work with MartisDXX Manager. The U interface activation process on ISD-NT does not work correctly if there is no NT1 device connected to ISD-LT.
10004_22 2008 Tellabs.

413
36.20 ISD-LT16 Unit: IBZ610 Unit Software

The software IBZ610 is used on ISD-LT16 unit (whose base unit is IBU726) in the Tellabs 8140 midi, Tellabs 8150 basic, Tellabs 8160 A111 and Tellabs 8170 cluster nodes. The version 1.y (where y=0, 1, 2...) can be downloaded to ISD-LT16 units having the version 1.0 of IBU726.
36.20.1 Version 1.0

Dependencies

ISD-LT16 (base unit IBU726) hardware version must be 1.0 or higher. CCU (SCZ286) software version must be 2.5 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.10 or higher to support functionality of V5.2. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version must be 10.1 or higher. GMX (GMZ544) software version must be 3.17 or higher. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version must be 10.2 or higher. SXU-V (SXZ630) software version must be 2.1 or higher to support functionality of V5.2. The dependency between software ISD-LT16 (IBZ610), SXU-V (SXZ630) and SCU-H (SCZ545) is functionality of V5.2. The MartisDXX Manager support for this ISD-LT16 unit is available in Release 12A SP3 or higher.
Restrictions
ISD-LT16 unit can be furnished only with two line cards when using IBZ610 V1.0.
Bugs

Missing support for "Out of frame fault in ISD-LT16 (CRF ID 4005330). Missing support for "Performance event for G.826 fault in ISD-LT16 (CRF ID 4005329).

414
10004_22 2008 Tellabs.
36.21 IUM-5T, IUM-10T and IUM-8 Units: UBZ436 Unit Software

The unit software UBZ436 is used on IUM-5T, IUM-10T and IUM-8 units the Tellabs 8140 midi, Tellabs 8150 basic and Tellabs 8160 A111 nodes. Version 3.2 can be downloaded to IUM-8 unit having the version 3.y of UBZ436 (where y=0, 1, 2...). Version 2.8 can be downloaded to IUM-5T, IUM-10T and IUM-8 units having the version 2.y of UBZ436 (where y=0, 1, 2...).
36.21.1 Version 3.2

This version is only for IUM-8 hardware version 2.0. Enhancements
This software version has improved tolerance against disturbances in VTP bus which could lead to unit disappearing from inventory. (CR ID 300045360)
Dependencies

IUM-8 base unit (UBU768) hardware version must be 2.0 or higher. STU-160 (STU315) hardware version 4.0 (SBZ385) software version must be 1.8 or higher. STU-160 (STU315) hardware version 5.0 (SBZ385) software version must be 2.1 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for IUM-8 is available in Release 12 Service Pack 1 or higher.
Restrictions
NTU setting backup feature (Plug and Play/PNP) requires SCP SW version 3.1 and/or SCU SW version 8.4 or XCG SW version 2.0. The maximum number of IUMs with the PNP feature enabled in one node (double or single) depends on the extended backup unit:

SCU: 4 x IUM-8 XCG: 10 x IUM-8 SCP: no limit.
Bugs
No known bugs.
10004_22 2008 Tellabs.

415
36.21.2 Version 3.1

This version is only for IUM-8 hardware version 2.0. Enhancements
The reason for this release is changes in fault handling (CR ID 300023226). In this software version Ntu power fault interface fault masks the Loss of input signal and No response to NNM message faults. Thus NTU power off will cause just Ntu power fault fault. In addition, the Ntu power off fault service status is changed to be a Service affecting fault (S).
Dependencies

Restrictions

SCU: 4 x IUM-8 XCG: 10 x IUM-8
SCP: no limit.
Bugs
No known bugs.

416
10004_22 2008 Tellabs.
36.21.3 Version 3.0

This version is only for IUM-8 hardware version 2.0. Enhancements and Fixed Bugs
The reason for this release is to serve new hardware version of IUM-8, the plug-in-unit.
Dependencies

Restrictions

SCU: 4 x IUM-8 XCG: 10 x IUM-8
SCP: no limit.
Bugs
No known bugs.
10004_22 2008 Tellabs.

417
36.21.4 Version 2.8

This is a production version based on version 2.7. Enhancements
The reason for this release is changes in fault handling (CR ID 300023241). In this software version Ntu power fault interface fault masks the Loss of input signal and No response to NNM message faults. Thus NTU power off will cause just Ntu power fault fault. In addition, the Ntu power off fault service status is changed to be a Service affecting fault (S).
Dependencies

IUM-8 base unit (UBU768) hardware version must be 1.0 or higher. IUM-5T base unit (UBU239) hardware version must be 2.0 or higher. IUM-10T base unit (UBU255) hardware version must be 1.0 or higher. When using IUM-8 STU-160 (STU315) hardware version 4.0 (SBZ385) software version must be 1.8 or higher. When using IUM-8 STU-160 (STU315) hardware version 5.0 (SBZ385) software version must be 2.1 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager Release 10.0A supports NTU setting backup and line information features. MartisDXX Manager support for IUM-8 is available in Release 12 Service Pack 1 or higher.
Restrictions

SCU: 4 x IUM-10T or IUM-8 (8 x IUM-5T) XCG: 10 x IUM-10T or IUM-8(21 x IUM-5T)
SCP: no limit.
Bugs
No known bugs.

418
10004_22 2008 Tellabs.
36.21.5 Version 2.7

This is a production version based on version 2.6. Enhancements and Fixed Bugs
IF module detection correction. (CR ID 200010407)
Dependencies

Restrictions

SCP: no limit.
Bugs
No known bugs.
10004_22 2008 Tellabs.

419
36.21.6 Version 2.6

This is a non-production version based on version 2.5. Enhancements and Fixed Bugs

NTU power fault detection correction. (CR ID 200008412) LOS fault correction. LOS fault was not active after resetting IUM. (CR ID 200005421, CR ID 200008596)
Dependencies

Restrictions

SCP: no limit.
Bugs
No known bugs.

420
10004_22 2008 Tellabs.
36.21.7 Version 2.5

Enhancements
The reason for this release is to serve also new hardware version, IUM-8, of the plug-in-unit. This release serves also older hardware types, IUM-5T and IUM-10T.
Dependencies

IUM-8 base unit (UBU 768) hardware version must be 1.0 or higher. IUM-5T base unit (UBU 239) hardware version must be 2.0 or higher. IUM-10T base unit (UBU255) hardware version must be 1.0 or higher. When using IUM-8 STU-160 (STU315) hardware version 4.0 (SBZ385) software version must be 1.8 or higher. When using IUM-8 STU-160 (STU315) hardware version 5.0 (SBZ385) software version must be 2.1 or higher. SCP (SCZ281) software version must be 3.1 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager Release 10.0A supports NTU setting backup and line information features. MartisDXX Manager support for IUM-8 is available in Release 12 Service Pack 1 or higher.
Restrictions

SCU: 4 x IUM-10T or IUM-8 (8 x IUM-5T) XCG: 10 x IUM-10T or IUM-8(21 x IUM-5T) SCP: no limit.
Bugs
No known bugs.
10004_22 2008 Tellabs.

421
36.21.8 Version 2.4

Dependencies

SCU: 4 x IUM-10T (8 x IUM-5T) XCG: 10 x IUM-10T (21 x IUM-5T) SCP: no limit.
MartisDXX Manager Release 10.0A supports NTU setting backup and line information features.
Restrictions
No restrictions.
Bugs
No known bugs.
36.21.9 Version 2.3

Dependencies

SCU: 4 x IUM-10T (8 x IUM-5T) XCG: 10 x IUM-10T (21 x IUM-5T) SCP: no limit.
NMS release 10.0A supports NTU setting backup and line information features.
Restrictions
No restrictions.
Bugs
If there are more than two bad communication lines between the IUM and the NTUs, the IUM unit may disappear from node inventory. Very rarely unit recovers from this itself and therefore unit must be reset manually. Disappearing does not effect data, only NMS communication.

422
10004_22 2008 Tellabs.
36.21.10 Version 2.2

Dependencies
No dependencies.
Restrictions

No NTU setting backup support (plug and play). No line information support.
Bugs
When there are bad communication lines between the IUM and the NTUs, the IUM unit may run out of xport quotas and disappears from node inventory and unit cannot be configured. Sometimes unit recovers from this itself but sometimes it requires manual reset. In G.821 statistics 24 hours last only 23 hours and 45 minutes.
36.21.11 Version 2.1

Dependencies
No dependencies.
Restrictions

No NTU setting backup support (plug and play). No line information support. Double rack with SXU-A cannot be filled up with the IUM units because of the limitation of 8 kbit/s cross-connections.
Bugs
When there are bad communication lines between the IUM and the NTUs, the IUM unit may run out of xport quotas and disappears from node inventory and unit cannot be configured. Sometimes unit recovers from this itself but sometimes it requires manual reset. In G.821 statistics 24 hours last only 23 hours and 45 minutes.
10004_22 2008 Tellabs.

423
36.21.12 Version 2.0

Dependencies
No dependencies.
Restrictions

No NTU setting backup support (plug and play). No line information support. Double rack with SXU-A cannot be filled up with the IUM units because of the limitation of 8 kbit/s cross-connections.
Bugs

Erroneous G.821 limit events under unavailable time. Does not work correctly in the Create Inventory operation (does not always unlock all ports). When there are bad communication lines between the IUM and the NTUs, the IUM unit may run out of xport quotas and disappears from node inventory and unit cannot be configured. Sometimes unit recovers from this itself but sometimes it requires manual reset. In G.821 statistics 24 hours last only 23 hours and 45 minutes.
36.21.13 Version 1.3

Dependencies
No dependencies.
Restrictions

No NTU setting backup support (plug and play). No line information support. IUM-10T (wide unit with eight interfaces) is not supported. Double rack with SXU-A cannot be filled up with the IUM units because of the limitation of 8 kbit/s cross-connections.
Bugs

Erroneous G.821 limit events under unavailable time. Does not work correctly in the Create Inventory operation (does not always unlock all ports). When there are bad communication lines between the IUM and the NTUs, the IUM unit may run out of xport quotas and disappears from node inventory and unit cannot be configured. Sometimes unit recovers from this itself but sometimes it requires manual reset. In G.821 statistics 24 hours last only 23 hours and 45 minutes.

424
10004_22 2008 Tellabs.
36.21.14 Version 1.1

Dependencies
No dependencies.
Restrictions

No NTU setting backup support (plug and play). No line information support. IUM-10T (wide unit with eight interfaces) is not supported. Double rack with SXU-A cannot be filled up with the IUM units because of the limitation of 8 kbit/s cross-connections.
Bugs

Erroneous G.821 limit events under unavailable time. Does not work correctly in the Create Inventory operation (does not always unlock all ports). Interface alarms are activated although interface is unlocked (incorrect LED handling). After IUM mode change, interface mode is undefined (conflict). In this state the IUM unit may be unstable. Interface mode must be set after IUM mode change. When there are bad communication lines between the IUM and the NTUs, the IUM unit may run out of xport quotas and disappears from node inventory and unit cannot be configured. Sometimes unit recovers from this itself but sometimes it requires manual reset. In G.821 statistics 24 hours last only 23 hours and 45 minutes.
36.21.15 Version 1.0

Dependencies
NMS support for this unit is available in Release 8.0.
Restrictions

No NTU setting backup support (plug and play). No line information support. IUM-10T (wide unit with eight interfaces) is not supported. In Terminal and Exchange modes, only B-channels are supported (not the D-channel) Setting remote loop at remote unit (e.g., in STU-160) is not supported. Double rack with SXU-A cannot be filled up with the IUM units because of the limitation of 8 kbit/s cross-connections.
10004_22 2008 Tellabs.

425
Bugs

The interface handler processes stack may be too small in some cases and therefore unpredictive errors may occur. Erroneous G.821 limit events under unavailable time. Does not work correctly in the Create Inventory operation (does not always unlock all ports) Interface alarms are activated although interface is unlocked (incorrect LED handling). After IUM mode change, interface mode is undefined (conflict). In this state the IUM unit may be unstable. Interface mode must be set after IUM mode change. If a 128 kbit/s circuit is routed through IF 1 of an IUM, it is possible that the IUM introduces a 125 us delay between the two 64 kbit/s channels. This will, of course, totally corrupt the 128 kbit/s circuit. This problem takes place when the TS0 of IF1 of the IUM is allocated among the last 5 to 10 time slots of the X-Bus (consisting of 1056 time slots). (Actually a HW bug, but correctable with software.) If a downloaded version of the software is in use, it is possible, due to erroneous synchronization between interrupt handling software and flash memory software, that parameterizing the unit or downloading new software leads to software reset. (This bug materializes rarely. Retrying the operation usually helps.) It may happen that when IUM is removed from node (for example, due to HW fault) and a replace unit of the same type is inserted to its place, the new unit does not get the correct backup parameters from the old unit (and the user has to reconfigure something). The reason is that SCU has not obtained the latest backup settings. There are two types of settings, correct and deficient; changing the latter ones is not automatically backed up by SCU. When there are bad communication lines between the IUM and the NTUs, the IUM unit may run out of xport quotas and disappears from node inventory and unit cannot be configured. Sometimes unit recovers from this itself but sometimes it requires manual reset. In G.821 statistics 24 hours last only 23 hours and 45 minutes.
Correct: G.821 statistics limits, NNM parameters Deficient: Loop timeout, Module type, Unit mode, U interface mode There is a remedy: once you change some of the deficient parameters, also change some correct parameter.

426
10004_22 2008 Tellabs.
36.22 LIU-H Unit (ERH581 Module): ERZ550 Unit Software

The software ERZ550 is used on the ERH581 hardware module (whose base module is UBU714) with unit software UBZ543 in Basic, Cluster and Midi Nodes and A111. UBU714 and ERH581 hardware modules together with their software modules make up a LIU-H bridge/router unit. The version 1.4 can be downloaded to ERH581 module having the version 1.y (where y=0, 1, 2...). NOTE! After the downloading has completed, the following two steps are required in order to activate the downloaded version: 1. ERH581 hardware module has to be reset by giving command reboot at the LIU command shell to make the downloaded ERZ550 version run. 2. After the ERZ550 software is rebooted, command markimage ok must be given at LIU command shell. Now the recently downloaded software is up and running and it is approved to be in permanent use.
36.22.1 Version 1.4

NOTE! The release numbering conforms to the convention of Tellabs Oy although the version number of ERZ550 is 5.2.0 (43). The size of the ERZ550 file is 1,112,102 bytes. Enhancements and Fixed Bugs

LIU-H will not end up in reboot loop after a reboot command or a spontaneous reboot when several PPP links are active. (CRF 4004720) IP routing works for a fifth Frame Relay port. (CRF 4004294)
Dependencies

ERH581 hardware version must be 1.0 or higher. UBU714 (UBZ543) software version must be 1.1 or higher. CCU (SCZ286) software version can be any version. SCP (SCZ281) software version must be 3.2 or higher to support 24 kB backup storage needed by LIU-H. SCU (SCZ280) software version must be 8.4 or higher to support 24 kB backup storage needed by LIU-H. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software version can be any version. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this LIU-H/bridging or routing is available in Release 10.1A or higher.
10004_22 2008 Tellabs.

427
Restrictions

Version 1.4 shall not be downgraded to 1.1 or earlier versions. Activating and deactivating the bridge function needs reboot. After configuring Frame Relay link it needs to be activated by giving command reboot at the LIU-H command shell. The maximum number of ports to which Frame Relay link protocol can be applied simultaneously is 5. Dynamic routing (OSPF, RIP/RIP-2) over unnumbered links is not supported.
Bugs

Activation of PPP over SCPP -ports needs reboot. The use of RAW IP link protocol cause harm to the operation of LIU-H in the situation where the logical port using RAW IP protocol is configured to use another link layer protocol. Multicast OSPF and RIP/RIP-2 protocols do not work over Frame Relay links. Depending on the configuration the reinit command may cause the LIU-H to reboot itself. The status information describing that WAN link is down is not reported in MartisDXX Manager FMS.
36.22.2 Version 1.3

NOTE! The release numbering conforms to the convention of Tellabs Oy although the version number of ERZ550 is 5.2.0 (42). The size of the ERZ550 file is 1,111,799 bytes Enhancements
Rebooting the LIU-H unit takes shorter time than earlier.
Dependencies

ERH581 hardware version must be 1.0 or higher. UBU714 (UBZ543) software version must be 1.1 or higher. SCP (SCZ281) software version must be 3.2 or higher to support 24 kB backup storage needed by LIU-H. SCU (SCZ280) software version must be 8.4 or higher to support 24 kB backup storage needed by LIU-H. XCG (SMZ538) software version must be 2.0 or higher. MartisDXX Manager support for this LIU-H/bridging or routing is available in Release 10.1A or higher.
Restrictions
Version 1.3 shall not be downgraded to 1.1 or earlier versions.

428
10004_22 2008 Tellabs.
Activating and deactivating the bridge function needs reboot. After configuring Frame Relay link it needs to be activated by giving the command reboot at the LIU-H command shell. The maximum number of ports to which Frame Relay link protocol can be applied simultaneously is 5. Dynamic routing (OSPF, RIP/RIP-2) over unnumbered links is not supported.
Bugs

Activation of PPP over SCPP -ports needs reboot. The use of RAW IP link protocol cause harm to the operation of LIU-H in the situation where the logical port using RAW IP protocol is configured to use another link layer protocol. Multicast OSPF and RIP/RIP-2 protocols do not work over Frame Relay links. Depending on the configuration the reinit command may cause the LIU-H to reboot itself. The status information describing that WAN link is down is not reported in MartisDXX Manager FMS.
36.22.3 Version 1.2

NOTE! The release numbering conforms to the convention of Tellabs Oy although the version number of ERZ550 is 5.2.0 (40). The size of the ERZ550 file is 1,111,075 bytes. Enhancements

DHCP server and relay agent functionality is added. Network address translation (NAT) functionality is added. IP address saving for CPE links can be used. Point-to-multipoint CPE connections for Frame Relay links are supported. Bandwidth limitation for CPE links is supported. Encryption (DES, 3DES) for PPP links is supported. The reinit command is available to be used for activating configuration changes without rebooting the system. Now the maximum number of Frame Relay DLCIs is 256. One command shows all IP filters. The ifstat command is added on with option l to select port. Now the pagination of terminal display output can be done as follows: |more.
Dependencies

ERH581 hardware version must be 1.0 or higher. UBU (the software of UBU714) software version must be 1.1 or higher.
10004_22 2008 Tellabs.

429
SCP (SCZ281) software version must be 3.2 or higher to support 24 kB backup storage needed by LIU-H. SCU (SCZ280) software version must be 8.4 or higher to support 24 kB backup storage needed by LIU-H. XCG (SMZ538) software version must be 2.0 or higher. MartisDXX Manager support for this LIU-H/bridging or routing is available in Release 10.1A or higher.
Restrictions

The maximum number of supported MCPP ports is 62. Version 1.2 shall not be downgraded to earlier versions. Activating and deactivating the bridge function needs reboot After configuring Frame Relay link it needs to be activated by giving the command reboot at the LIU-H command shell. The maximum number of ports to which Frame Relay link protocol can be applied simultaneously is 5. Dynamic routing (OSPF, RIP/RIP-2) over unnumbered links is not supported.
Bugs

If more than 62 MCPP ports are configured, LIU-H will become inoperable. Activation of PPP over SCPP ports needs reboot. The use of RAW IP link protocol cause harm to the operation of LIU-H in the situation where the logical port using RAW IP protocol is configured to use another link layer protocol. Multicast OSPF and RIP/RIP-2 protocols do not work over Frame Relay links. Depending on the configuration the reinit command may cause the LIU-H to reboot itself. The status information describing that WAN link is down is not reported in MartisDXX Manager FMS.
36.22.4 Version 1.1

NOTE! The release numbering conforms to the convention of Tellabs Oy although the version number of ERZ550 is 5.0.0 (31). Dependencies

ERH581 hardware version must be 1.0 or higher. UBU714 (UBZ543) software version must be 1.1 or higher. SCP (SCZ281) software version must be 3.2 or higher to support 24 kBytes backup storage needed by LIU-H. SCU (SCZ280) software version must be 8.4 or higher to support 24 kBytes backup storage needed by LIU-H.

430
10004_22 2008 Tellabs.
XCG (SMZ538) software version must be 2.0 or higher. MartisDXX Manager support for this LIU-H/bridging or routing is available in Release 10.1 Service Pack A or higher.
Restrictions
No restrictions.
Bugs

The spanning tree algorithm does not work correctly (related to Bridge functionality). Frame Relay link protocol over MCPP ports does not work. It may happen that LIU-H reboots itself as it becomes overloaded with data traffic.
36.22.5 Version 1.0

NOTE! The release numbering conforms to the convention of Tellabs Oy although the version number of ERZ550 is 5.0.0 (29). Dependencies

ERH581 hardware version must be 1.0 or higher. UBU714 (UBZ543) software version must be 1.1 or higher. SCP (SCZ281) software version must be 3.2 or higher to support 24 kB backup storage needed by LIU-H. SCU (SCZ280) software version must be 8.4 or higher to support 24 kB backup storage needed by LIU-H. XCG (SMZ538) software version must be 2.0 or higher. MartisDXX Manager support for this LIU-H/bridging or routing is available in Release 10.1A or higher.
Restrictions
No restrictions.
Bugs
No known bugs.
10004_22 2008 Tellabs.

431
36.23 LIU-H Unit: UBZ543 Unit Software

UBZ543 is a unit software running on the UBU714 processor board used on the LIU-H unit in Basic, Cluster and Midi Nodes and A111. UBZ543 communicates with the ERZ550 software of the ERH module (ERH581 processor board) utilizing a dual-port RAM. The ERH module performs as a bridge, an IP router or as a brouter. The release 1.2 of the UBZ543 can be downloaded to LIU-H units having the version 1.y of UBZ543 (where y=0,1,2...).
36.23.1 Version 1.2

Some functions related to router module (ERH) rebooting and reboot state detection corrected. Extra reboot fault fixed. Reset RM button in the MartisDXX Manager Node Manager LIU Unit Parameter window makes a hardware reset on the router module. (CRF 4004818)
Dependencies

LIU-H (base unit UBU714) hardware must be 1.0 or higher. CCU (SCZ286) software version can be any version. SCP (SCZ281) software version must be 3.2 or higher. SCU (SCZ280) software version must be 8.4 or higher. SCU-H (SCZ545) software version must be 1.6 or higher. XCG (SMZ538) software version must be 2.0 or higher. CXU-M (SXZ288) software can be any version. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager preplanning support for this unit is available in Release 10.0A-2. Full support will be available in Release 10.1A. The software version of ERH module has to be 5.0.0 (x), where the value of x is 31 or greater.
Restrictions
If SCU is used, SCP is needed and each LIU-H unit requires 24 kilobytes of flash memory from SCP.
Bugs
No known bugs.

432
10004_22 2008 Tellabs.
36.23.2 Version 1.1

Dependencies

MartisDXX Manager preplanning support for this unit is available in Release 10.0A-2. Full support will be available in Release 10.1A. The software version of ERH module has to be 5.0.0 (x), where the value of x is 31 or greater.
Restrictions The LIU-H unit requires the following units and modules in the subrack.
If the node uses SCU, SCP is needed. SCZ280 program, version 8.4 SCZ281 program, version 3.2 If the node uses XCG SMZ538 program, version 2.0.
Each LIU unit requires 24 kilobytes of flash memory from the SCP. Bugs
No known bugs.
36.23.3 Version 1.0

Dependencies

MartisDXX Manager preplanning support for the LIU unit is available in Release 10.0A. Full support will be available in later service packs. The software version of ERH module has to be 5.0.0 (29).
Restrictions The LIU-H unit requires the following units and modules in the subrack.
If the node uses SCU, SCP is needed. SCZ280 program, version 8.4 SCZ281 program, version 3.2 If the node uses XCG SMZ538 program, version 2.0.
Each LIU-H unit requires 24 kilobytes of flash memory from the SCP.
10004_22 2008 Tellabs.

433
Bugs
UBU date management does not detect that year 2000 is a leap year. Hence the UBU date becomes March 1, 2000 after midnight of February 28, 2000 (it should become February 29, 2000).
36.24 NTU-2M Unit: SBZ542 Unit Software

The software SBZ542 is used on NTU-2M network terminating units. Version 1.1 can be downloaded to NTU-2M having the revision 1.y of SBZ542 (where y=0,1,2,3...).
36.24.1 Version 1.1

Dependencies

Does not support frequency difference and DTE out of sync alarms with NTU-2M hardware version 1.0. MartisDXX Manager support for DTE error counters is available in Release 10.0. Preliminary MartisDXX Manager support for this unit is available in Release 9.0B-EME6 (NTU-2M and STU-2048 baseband NTUs cannot be distinguished from each other because an STU-2048 NTU is shown as an NTU-2M if MartisDXX Manager configuration file DXXNMS.INI includes definition NTU_2M=TRUE ). MartisDXX Manager support specifically for this unit will be available in Release 10.0.
Restrictions
No restrictions.
Bugs
No known bugs.
36.24.2 Version 1.0

Dependencies
Preliminary MartisDXX Manager support for this unit is available in Release 9.0B-EME6 (NTU-2M and STU-2048 baseband NTUs cannot be distinguished from each other because an STU-2048 NTU is shown as an NTU-2M if MartisDXX Manager configuration file DXXNMS.INI includes definition NTU_2M=TRUE ). MartisDXX Manager support specifically for this unit will be available in Release 10.0.
Restrictions
Alarms not supported DTE out of sync BER10E-6 Frequency difference
GPT 30 16 30
SPT 45 46 47
Does not support DTE error counters.

10004_22 2008 Tellabs.

434
Bugs
BER more than 10E-3 does not work correctly.
36.25 SBM 384A NTU: SBA380 Unit Software

The software SBA380 is used on SBM 384A NTU.
36.25.1 Version 1.5

Dependencies
No dependencies.
Restrictions
No restrictions.
Bugs
No known bugs.
36.25.2 Version 1.4

Dependencies
No dependencies.
Restrictions
In 2-wire operation the configuration scrambler: none is not allowed
Bugs
RLBtime: 4 min and RLBtime: 8 min are 4 min too long.
36.25.3 Version 1.3

Dependencies
No dependencies.
Restrictions

In 2-wire operation the configuration scrambler: none is not allowed. Circuit 109 response time (64 kbit/s, 4-wire) is not fast enough for certain PDA 64 applications. No support for implementing 144 kbit/s line rate instead of 56 kbit/s. If 144kbit/s is implemented, the oscillator must be changed. Software determines which oscillator is assembled from connector TP4 pin 6. If it is grounded, oscillator for rate 144 kbit/s is assumed.
10004_22 2008 Tellabs.

435
Bugs
36.25.4 Version 1.2

Dependencies
No dependencies.
Restrictions

In 2-wire operation the configuration scrambler: none is not allowed. No support for VGM334. Neighbour node supervision parameterization is not possible from the NTU keys. Circuit 109 response time (64 kbit/s, 4-wire) is not fast enough for certain PDA 64 applications. No support for implementing 144 kbit/s line rate instead of 56 kbit/s. If 144 kbit/s is implemented, the oscillator must be changed. Software determines which oscillator is assembled from connector TP4 pin 6. If it is grounded, oscillator for rate 144 kbit/s is assumed.
Bugs
36.25.5 Version 1.1

Dependencies
No dependencies.
Restrictions

In 2-wire operation the configuration scrambler: none is not allowed. No support for VGM334. No support for VGX332. Neighbour node supervision parameterization is not possible from the NTU keys. Circuit 109 response time (64 kbit/s, 4-wire) is not fast enough for certain PDA 64 applications. No support for implementing 144 kbit/s line rate instead of 56 kbit/s. If 144 kbit/s is implemented, the oscillator must be changed. Software determines which oscillator is assembled from connector TP4 pin 6. If it is grounded, oscillator for rate 144 kbit/s is assumed.

436
10004_22 2008 Tellabs.
Bugs

Adaptive real-time does not work. RLBtime: 4 min and RLBtime: 8 min are 4 min too long.
36.26 SBM 384E NTU: SBE380 Unit Software

The software SBE380 is used on SBM 384E NTU.
36.26.1 Version 1.4

Dependencies
No dependencies.
Restrictions
No restrictions.
Bugs
No known bugs.
36.26.2 Version 1.3

Dependencies
No dependencies.
Restrictions

Circuit 109 response time (64kbit/s,4-wire) is not fast enough for certain PDA64 applications. No support for implementing 144kbit/s line rate instead of 56kbit/s. If 144 kbit/s is implemented, the oscillator must be changed. Software determines which oscillator is assembled from connector TP4 pin 6. If it is grounded, oscillator for rate 144 kbit/s is assumed.
Bugs
No known bugs.
10004_22 2008 Tellabs.

437

The software SBA381 is used on SBM64A NTU.
36.27.1 Version 1.3

Dependencies
No dependencies.
Restrictions
No restrictions.
Bugs
No known bugs.
36.27.2 Version 1.2

Dependencies
No dependencies.
Restrictions

In 2-wire operation the configuration scrambler: none is not allowed. No asynchronous Circuit Loop Test support.
Bugs
Bug in G.821 statistics. Circuit Loop Test does not generate correct G.821 statistics.1

438
10004_22 2008 Tellabs.
36.27.3 Version 1.1

Dependencies
No dependencies.
Restrictions

In 2-wire operation the configuration scrambler: none is not allowed. No asynchronous Circuit Loop Test support. Circuit 109 response time (64 kbit/s, 4-wire) is not fast enough for certain PDA 64 applications.
Bugs

Unnecessary alarms when GCH interface is not connected. Bug in the menu if X.21 DTE card and no framing on the line: the LL state appears only when the left scroll key (<) is used. Bug in G.821 statistics. Circuit Loop Test does not generate correct G.821 statistics.
36.27.4 Version 1.0

Dependencies
No dependencies.
Restrictions

In 2-wire operation the configuration scrambler: none is not allowed. No asynchronous Circuit Loop Test support. Circuit 109 response time (64 kbit/s, 4-wire) is not fast enough for certain PDA 64 applications.
Bugs

Unnecessary alarms when GCH interface is not connected. NTU cannot follow the rate from DTE. Bug in menu if X.21 DTE card and no framing on the line: the LL state appears only when the left scroll key (<) is used. Bug in G.821 statistics. Circuit Loop Test does not generate correct G.821 statistics.
10004_22 2008 Tellabs.

439
36.28 SBM 64E NTU: SBE381 Unit Software

The software SBE381 is used on SBM 64E NTU.
36.28.1 Version 1.3

Dependencies
No dependencies.
Restrictions
No restrictions.
Bugs
No known bugs.
36.28.2 Version 1.2

Dependencies
No dependencies.
Restrictions

Circuit 109 response time is not fast enough for certain PDA64 applications. In 2-wire operation the configuration scrambler: none is not allowed.
Bugs
No known bugs.

440
10004_22 2008 Tellabs.

The software SBA382 is used on SBM 768A NTU.
36.29.1 Version 1.4

Dependencies
No dependencies.
Restrictions
No restrictions.
Note: Now you can select line code and framing independently, but you should use differential line coding when there is no frame on the line. Bugs
No known bugs.
36.29.2 Version 1.3

Dependencies
No dependencies.
Restrictions

Line code and framing cannot be selected independently. No scrambler selection. V.29 is always used.
Bugs
RLBtime: 4min and 8min are 4 min too long.
10004_22 2008 Tellabs.

441
36.29.3 Version 1.2

Dependencies
No dependencies.
Restrictions

Cannot be used as repeater if frame is on. Line code and framing cannot be selected independently. No scrambler selection. V.29 is always used.
Bugs
36.29.4 Version 1.1

Dependencies
No dependencies.
Restrictions

No support for VGM334. Neighbour node supervision parameterization is not possible from the NTU keys. Cannot be used as repeater if frame is on. Line code and framing cannot be selected independently. No scrambler selection. V.29 is always used.
Bugs

442
10004_22 2008 Tellabs.
36.30 SCP Module: SCZ281 Unit Software

The software SCZ281 is used on SCP211 modules piggybacked on SCU. Its main functions are to support the end points of shortcut control channels and to offer extended setting backup resources. The shortcut control channels are HDLC links which can be connected through the 8, 16, 32 or 64 kbit/s circuits over the Tellabs 8100 network. The cross-connection port at the end of the 8, 16, 32 or 64 kbit/s circuit is one of the SCU ports 1, 2, 3 or 4 associated with the HDLC channels 1, 2, 3 or 4 of the SCP211 module. The speed options can be selected separately for the channel pairs: a common speed for the channels 1 and 2 and another choice for the channels 3 and 4. When settings backup resources offered by the SCU is insufficient, the SCP module offers extended settings backup space of up to 333 kB.
36.30.1 Version 3.3

Flash system improvement. NNM message handling implemented in receive direction.
Dependencies

SCP (base unit SCP211) hardware version must be 3.0 or higher. SCU (SCZ280) software version must be 7.6 or higher and SCU210 hardware version 2.0 or higher. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this module is available in Release 9.0 or higher.
Restrictions
With SCP211 version 2.0 extended setting backup and downloading is not supported.
Bugs
No known bugs.
10004_22 2008 Tellabs.

443
36.30.2 Version 3.2
Fault management improvement.
Dependencies

SCP (base unit SCP211) hardware version must be 3.0 or higher. SCU (SCZ280) software version must be 7.6 or higher and SCU210 hardware version 2.0 or higher. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this module is available in Release 9.0 or higher.
Restrictions
Bugs
Incoming NNM messages through HDCL link break the management communication to SCP off.
36.30.3 Version 3.1
Extended backup improvement.
Dependencies

It requires the SCU210 version 2.0 (or greater) with the SCZ280 version 7.6 (or greater) and with SCP211 version 3.0 (or greater). MartisDXX Manager supports new error codes in Release 9.0a.
Restrictions
Bugs
No known bugs.

444
10004_22 2008 Tellabs.
36.30.4 Version 3.0
Extended backup implemented.
Dependencies

It requires the SCU210 version 2.0 (or greater) with the SCZ280 version 7.6 (or greater) and with SCP211 version 3.0 (or greater). With SCP211 version 2.0 extended setting backup and downloading is not supported. MartisDXX Manager support (downloading and new error codes) for this unit is available in Release 9.0.
Restrictions

No SCP backup space info supported (CRF ID 4000779). Some units (for example AIU) cannot utilize SCP extended setting backup without backup space info support. No extended testing support (only one SCU/SCP combination can be fitted in same rack).
Bugs
No known bugs.
36.30.5 Version 2.0
Dependencies
It requires the SCU210 version 2.0 (or greater) with the SCZ280 version 7.6 (or greater) and with SCP211 version 2.0 (or greater).
Restrictions

No extended setting backup support. No SW downloading support. No SCP backup space info support. No extended testing support (only one SCU/SCP combination can be fitted in same rack).
Bugs
No known bugs.
10004_22 2008 Tellabs.

445
36.31 SCU Unit: SCZ280 Unit Software

The software SCZ280 is used on SCU units (whose base unit is SCU210). The version 8.6 can be downloaded to SCUs having the version 8.y of SCZ280 (where y=0, 1, 2...). It supports the normal control unit functions for all versions of the base unit.
36.31.1 Version 8.6
Enhancements and Fixed Bugs (compared with version 8.54) The use of this version is recommended only to correct the following problems with SCU:
Circuit loop test (CLT) is giving bit errors when test resource in SCU is used. (CR ID 200008860)
Dependencies
See 1.3 Version 8.5
36.31.2 Version 8.54

This is a non-production version based on version 8.5. Enhancements and Fixed Bugs (compared with version 8.5) The use of this version is recommended only to correct the following problems with SCU:
Asynchronous link between DXX Server and SCU is used and access to nodes often fails and the Control channel broken faults frequently occur in some nodes of the network. (CRF ID 4004049)
Dependencies
See 1.3 Version 8.5

446
10004_22 2008 Tellabs.
36.31.3 Version 8.5
Dependencies

With SCU hardware version 1.x, the channel test or control channel support is not available. With SCU hardware version 2.x, the test resource has the following limitations:

At bit rates Nx3.0 kbit/s and Nx3.2 kbit/s may indicate errors Inject error function produces a few errors.
With SCU hardware version 3.x, there are not the limitations mentioned above. SCU needs SCP215 with hardware version 1.1 or newer to make LABP connection between two SCUs work through X.25 interface. SCP (SCZ281) software version must be 3.0 or higher. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. MartisDXX Manager support for this unit is available in Release 8.0 or higher.
Restrictions
No restrictions.
Bugs
No known bugs.
10004_22 2008 Tellabs.

447
36.31.4 Version 8.4
Dependencies


With SCU hardware version 3.x, there are not the limitations mentioned above. SCU needs SCP215 with hardware version 1.1 or newer to make LABP connection between two SCUs work through X.25 interface.
Restrictions
No restrictions
Bugs

Maintenance event alarm (MEI) for active SXU switchover. (CRF ID 4000906) SCU bus voltage alarm filtering in Tellabs 8140 midi node. (CRF ID 4001479) Support for PFU-A/PFU-B power off alarm in SCU/CCU. (CRF ID 4001590)
36.31.5 Version 8.3
Dependencies


At bit rates Nx3.0 kbit/s and Nx3.2 kbit/s may indicate errors. Inject error function produces a few errors.
With SCU hardware version 3.x, there are not the limitations mentioned above. SCU needs SCP215 with hardware version 1.1 or newer to make LABP connection between two SCUs work through X.25 interface.
Restrictions
No support for extra backups for other units in the node (e.g. AIU)

448
10004_22 2008 Tellabs.
Bugs

Maintenance event alarm (MEI) for active SXU switchover. (CRF ID 4000906) SCU bus voltage alarm filtering in Tellabs 8140 midi node. (CRF ID 4001479) Support for PFU-A/PFU-B power off alarm in SCU/CCU. (CRF ID 4001590)
36.31.6 Version 8.2
Dependencies


With SCU hardware version 3.x, there are not the limitations mentioned above.
Restrictions

No support for extra backups for other units in the node (e.g. AIU) Communication through X.25 interface between two SCUs not supported. The clock direction options for the synchronous SCC interface are not supported.
Bugs

Maintenance event alarm (MEI) for active SXU switchover. (CRF ID 4000906) SCU bus voltage alarm filtering in Tellabs 8140 midi node. (CRF ID 4001479) Support for PFU-A/PFU-B power off alarm in SCU/CCU. (CRF ID 4001590) SCU reported some GMHs falsely missing units due to VTP errors. (CRF ID 2000170) NRP update for block extension in GMU. (CRF ID 2000202)
10004_22 2008 Tellabs.

449
36.31.7 Version 8.1
Dependencies


Restrictions

No support for extra backups for other units in the node (e.g. AIU) Communication through X.25 interface between two SCUs not supported The async channel loop test is not supported. The clock direction options for the synchronous SCC interface are not supported. The optional security management for the SC interface is not supported.
Bugs

Maintenance event alarm (MEI) for active SXU switchover. (CRF ID 4000906) SCU bus voltage alarm filtering in Tellabs 8140 midi node. (CRF ID 4001479) Support for PFU-A/PFU-B power off alarm in SCU/CCU. (CRF ID 4001590) SCU reported some GMHs falsely missing units due to VTP errors. (CRF ID 2000170) NRP update for block extension in GMU. (CRF ID 2000202) Unexpected bit errors at rate 704 kbit/s in the channel loop test. A bug in the G.821 statistics of the channel loop test support.

450
10004_22 2008 Tellabs.
36.31.8 Version 8.0
Dependencies


Restrictions

No support for extra backups for other units in the node (e.g. AIU) Communication through X.25 interface between two SCUs not supported The async channel loop test is not supported. The clock direction options for the synchronous SCC interface are not supported. The optional security management for the SC interface is not supported.
Bugs

Maintenance event alarm (MEI) for active SXU switchover. (CRF ID 4000906) SCU bus voltage alarm filtering in Tellabs 8140 midi node. (CRF ID 4001479) Support for PFU-A/PFU-B power off alarm in SCU/CCU. (CRF ID 4001590) SCU reported some GMHs falsely missing units due to VTP errors. (CRF ID 2000170) NRP update for block extension in GMU. (CRF ID 2000202) Unexpected bit errors at rate 704 kbit/s in the channel loop test. A bug in the G.821 statistics of the channel loop test support. The operation "Create inventory" cannot be used if the units have active connections.
10004_22 2008 Tellabs.

451
36.31.9 Version 7.6
Dependencies


Restrictions

No support for extra backups for other units in the node (e.g. AIU). Communication through X.25 interface between two SCUs not supported. The async channel loop test is not supported. The clock direction options for the synchronous SCC interface are not supported. The optional security management for the SC interface is not supported.
Bugs

Maintenance event alarm (MEI) for active SXU switchover. (CRF ID 4000906) SCU bus voltage alarm filtering in Tellabs 8140 midi node. (CRF ID 4001479) Support for PFU-A/PFU-B power off alarm in SCU/CCU. (CRF ID 4001590) SCU reported some GMHs falsely missing units due to VTP errors. (CRF ID 2000170) NRP update for block extension in GMU. (CRF ID 2000202) Unexpected bit errors at rate 704 kbit/s in the channel loop test. A bug in the G.821 statistics of the channel loop test support. The operation "Create inventory" cannot be used if the units have active connections. The trunks of a node can not be looped physically back to the node while management messages are sent through the trunk. Otherwise SCU has continuous troubles. The network layer protocol software can not handle all illegal routing elements. The LLC3 protocol software can not handle one exceptional case associated with negative acknowledgement. These two communication problems are not likely to happen but they can cause a deadlock in the communication system SCU. The asynchronous protocol software does not work correctly with heavy full-duplex traffic.

452
10004_22 2008 Tellabs.
36.31.10 Version 7.5
Dependencies


Restrictions

No support for extra backups for other units in the node (e.g. AIU) Communication through X.25 interface between two SCUs not supported The async channel loop test is not supported. The clock direction options for the synchronous SCC interface are not supported. The optional security management for the SC interface is not supported. Does not support the alarm interface module SCL415. Does not support the correct test port handling for the test resource. Does not support the correct control channel port handling for SCP211.
Bugs

Maintenance event alarm (MEI) for active SXU switchover. (CRF ID 4000906) SCU bus voltage alarm filtering in Tellabs 8140 midi node. (CRF ID 4001479) Support for PFU-A/PFU-B power off alarm in SCU/CCU. (CRF ID 4001590) SCU reported some GMHs falsely missing units due to VTP errors. (CRF ID 2000170) NRP update for block extension in GMU. (CRF ID 2000202) Unexpected bit errors at rate 704 kbit/s in the channel loop test. A bug in the G.821 statistics of the channel loop test support. The asynchronous protocol software does not work correctly with heavy full-duplex traffic. The operation "Create inventory" cannot be used if the units have active connections. The trunks of a node can not be looped physically back to the node while management messages are sent through the trunk. Otherwise SCU has continuous troubles. The network layer protocol software can not handle all illegal routing elements. The LLC3 protocol software can not handle one exceptional case associated with negative acknowledgement. These two communication problems are not likely to happen but they can cause a deadlock in the communication system SCU. The asynchronous protocol software does not work correctly with heavy full-duplex traffic.
10004_22 2008 Tellabs.

453
36.32 STU-56 DSL NTU: SBZ388 Unit Software

The software SBZ388 is used on STU-56 (STU325) network terminating units. The version 1.1 can be downloaded to units having the version 1.y of SBZ388 (where y=0, 1, 2...).
36.32.1 Version 1.1

Local loop test works now without connection to IUM unit.
Dependencies

STU-56 (base unit STU325) hardware version must be 1.0 or higher. IUM-5T (UBU239) and IUM-10T (UBU255) hardware version must be 1.0 or higher. MartisDXX Manager support for this unit is available in Release 9.0B or higher.
Restrictions
STU-56 is not fully compatible with IUM-8 unit. STU-56 hangs up when IUM-8 v1.0 or IUM-8 v2.0 is powered off line connected. (CR ID 200007601)
Bugs
Neighbour node loop does not always work (CRF ID 4003588).
36.32.2 Version 1.0

Dependencies

STU-56 (base unit STU325) hardware version must be 1.0 or higher. IUM-5T (UBU239) and IUM-10T (UBU255) hardware version must be 1.0 or higher. MartisDXX Manager support for this unit is available in Release 9.0B or higher.
Restrictions
STU-56 is not fully compatible with IUM-8 unit. STU-56 hangs up when IUM-8 v1.0 or IUM-8 v2.0 is powered off line connected. (CR ID 200007601)
Bugs

Neighbour node loop does not always work. (CRF ID 4003588) Local loop test does not work without connection to IUM unit.

454
10004_22 2008 Tellabs.
36.33 STU-1088/2048 NTU: SBZ384 Unit Software

The software SBZ384 is used on STU-1088/STU-2048 baseband NTUs. Version 1.4 can be downloaded to STU-1088/STU-2048s having the revision 1.y of SBZ384 (where y=0, 1, 2, 3...).
36.33.1 Version 1.4

Dependencies
No dependencies
Restrictions
No restrictions
Bugs
No known bugs
36.33.2 Version 1.3

Dependencies
MartisDXX Manager support for EHI392 interface card is available in Release 9.0B.
Restrictions

Does not support 32-bit error counter of the test transmitter and receiver. File Management application does not show correct software version after software disable or EPROM change. Does not support panel keys total locking. Does not support IP filter table handling with a LAN Bridge interface card.
Bugs

DTE rate adaptation does not function according to the specification. Digital loop and Digital loop made by neighbour alarms are active simultaneously when digital loop is activated by neighbour. 106 signal stays fixed OFF when RFS delay parameter is changed from 600ms to any other value during 105 signal OFF-state.
10004_22 2008 Tellabs.

455
36.33.3 Version 1.2

Dependencies
No dependencies
Restrictions

Does not support 32-bit error counter of the test transmitter and receiver Does not support EHI392 interface card (LAN Bridge with 10Base-T and 10Base-2 connectors) Does not support the File Management of Network Element application with full file information (last modification date, time and modifier) Does not support new FPGA version FZ031412 (8kb/s control channel is forced to AIS when carrier parameter 8kb/s is not in use) Does not support panel keys total locking.
Bugs

DTE rate adaptation does not function according to the specification. Digital loop and Digital loop made by neighbour alarms are active simultaneously when digital loop is activated by neighbour. 106 signal stays fixed OFF when RFS delay parameter is changed from 600ms to any other value during 105 signal OFF-state.

456
10004_22 2008 Tellabs.
36.33.4 Version 1.1

Dependencies
MartisDXX Manager support for GHI374, GHI375, VMI377, and XMI378 interface cards is available in Release 9.0.
Restrictions

Does not support 32-bit error counter of the test transmitter and receiver. Does not support the File Management of Network Element application with full file information (last modification date, time and modifier). Does not support new FPGA version FZ031412 (8kb/s control channel is forced to AIS when carrier parameter 8kb/s is not in use). Does not support EHI392 interface card (LAN Bridge with 10Base-T and 10Base-2 connectors). Does not support data timing by 114 clock in NNL/NNLTR cases. Does not support panel keys total locking.
Bugs

DTE rate adaptation does not function according to the specification. Digital loop and Digital loop made by neighbour alarms are active simultaneously when digital loop is activated by neighbour. The data state information for the Circuit Loop Test application is always normal. G.821 statistics is not in unavailable state under line break (also G.821 unavailable alarm is not activated although G.821 supervisor is in use). The line rate adaptation does not work with default timing setting (113) in the repeater master mode. The DTE rate parameter is possible to set fromDTE with GHI-375 interface card (from the panel keys). 106 signal stays fixed OFF when RFS delay parameter is changed from 600ms to any other value during 105 signal OFF-state.
10004_22 2008 Tellabs.

457
36.33.5 Version 1.0

Dependencies
MartisDXX Manager support for this unit is available in Release 8.0A.
Restrictions

Does not support 32-bit error counter of the test transmitter and receiver. Does not support the File Management of Network Element application with full file information (last modification date, time and modifier). Does not support new FPGA version FZ031412 (8 kb/s control channel is forced to AIS when carrier parameter 8kb/s is not in use). Does not support EHI392 interface card (LAN Bridge with 10Base-T and 10Base-2 connectors). Does not support GHI374 and GHI375 interface cards (G.703 2M 120/75). Does not support VMI377 and XMI378 interface cards (V.35 ISO2593 and X.21 ISO4903 connectors). Does not support data timing by 114 clock in NNL/NNLTR cases. Does not support automatic timing source switching when the original timing source is not available. Does not support panel keys total locking.
Bugs

The data state information for the Circuit Loop Test application is always normal. G.821 statistics is not in unavailable state under line break (also G.821 unavailable alarm is not activated although G.821 supervisor is in use). The state information of the DTE signals is invert. RFS delay 600ms is actually 128ms. 106 signal stays fixed OFF when RFS delay parameter is changed from 600ms to any other value during 105 signal OFF state. The clock signal 114 is not available to DTE in 113/115meso timing mode. DTE rate adaptation does not work correctly in transparent mode. BER more than 10E-3 alarm is always inactive.

458
10004_22 2008 Tellabs.
36.34 SXU-V Unit: ESZ8003 Unit Software

The software ESZ8003 is used on the ESX daughter module of the SXU-V unit in the Tellabs 8140 midi and Tellabs 8150 basic nodes. The version 1.11 can be downloaded to SXU-V having version 1.x of ESZ8003 software.
36.34.1 Version 1.11

The V5.2 link id procedure does not work correctly (CR ID 200012412). SXU-V link unblock register values for South Africa (CR ID 200011019).
Dependencies

ESX717 hardware version must be 1.0 or higher. SXU-V base unit software (SXZ630) version must be 2.1 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. ESX717 boot software (ESZ8002) must be version 1.1 or higher. In V5.2 use, GMH (GMZ283) software version must be 10.1 or higher (V5 links between LE and AN). In V5.2 use, QMH (QMZ540) software version must be 10.5 or higher (V5 links between LE and AN). CCS-UNI (CCZ539) software version must be 5.4 or higher to support V5.2 functionality. ISD-LT16 (IBZ610) software version must be 1.0 or higher to support V5.2 functionality. MartisDXX Manager support for this unit is available in R12 SP2 or higher.
Restrictions
No restrictions.
Bugs
No known bugs.
10004_22 2008 Tellabs.

459
36.34.2 Version 1.10
During high call rate some cross-connections are not properly cleared (CQ ID 200003709).
Dependencies

ESX717 hardware version must be 1.0 or higher. SXU-V base unit software (SXZ630) version must be 2.1 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. ESX717 Boot Software (ESZ8002) must be version 1.1 or higher In V5.2 use, GMH (GMZ283) software version must be 10.1 or higher (V5 links between LE and AN). In V5.2 use, QMH (QMZ540) software version must be 10.5 or higher (V5 links between LE and AN). CCS-UNI (CCZ539) software version must be 5.4 or higher to support V5.2 functionality. ISD-LT16 (IBZ610) software version must be 1.0 or higher to support V5.2 functionality. MartisDXX Manager support for this unit is available in R12 SP2 or higher.
Restrictions
No known restrictions.
Bugs
Deleting ISDN port descriptor causes CCS TV5 link go down (CQ ID 200005847).
36.34.3 Version 1.8

Support active X-bus switching. (CRF ID 4005325) Ability to create ISD descriptors for ISD-LT16 or CCS descriptor for CCS-UNI in slot 18 of Tellabs 8150 basic node double subrack. (CRF ID 4005049) Attain dial tone after SXU-V switchover. (CRF ID 4005077) Clearing dynamic cross-connections from the passive SXU-V after a switchover. (CRF ID 4005157) Correct link ID mismatch reported to NMS. (CRF ID 4005158). Upon deleting a standby C-channel, the SXU-V releases the port that was assigned to the C-channel. (CRF ID 4005159)

460
10004_22 2008 Tellabs.
SXU-V can handle 32 access units (any combination of CCS-UNIs and ISD-LT16s). (CRF ID 4005161) Fixed the phantom faults generated by the ESX. (CRF ID 4004840) Support deferred and non-deferred link blocking. (CRF ID 4004841) Fixed the L3 configuration mismatch between SXU-Vs. (CRF ID 4005078)
Dependencies

ESX717 hardware version must be 1.0 or higher. SXU-V base unit software (SXZ630) version must be 2.1 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. ESX717 Boot Software (ESZ8002) must be version 1.1 or higher In V5.2 use, GMH (GMZ283) software version must be 10.1 or higher (V5 links between LE and AN). In V5.2 use, QMH (QMZ540) software version must be 10.5 or higher (V5 links between LE and AN). CCS-UNI (CCZ539) software version must be 5.4 or higher to support V5.2 functionality. ISD-LT16 (IBZ610) software version must be 1.0 or higher to support V5.2 functionality. MartisDXX Manager support for this unit is available in R12 SP2 or higher.
Restrictions
No known restrictions.
Bugs
No known bugs.
36.34.4 Version 1.7

This is an internal test version based on ESZ8003 version 1.6 with ISDN port activation failure indication and reset pulse digit recognition for PSTN ports state machine.
36.34.5 Version 1.6

This is an internal test version based on ESZ8003 version 1.5 with a bug fix for de-allocating buffers associated with non-existent ISDN ports.
10004_22 2008 Tellabs.

461
36.34.6 Version 1.5

This is an internal test version based on ESZ8003 version 1.4. This version incorporated SXUV port assignment for PG2 Standby C-channels; and the creation of ISD descriptor for ISD- LT16 or CCS descriptor for CCS-UNI in slot 18 of Tellabs 8150 basic node double subrack (CRF ID 4005049).
36.34.7 Version 1.4

This is an internal test version based on ESZ8003 version 1.3. This version incorporated support for ETSI version EN 300 347-1 of V5.2 standard and ISDN BRI ports
36.34.8 Version 1.3

This is an internal test version based on ESZ8003 version 1.2 with modifications to the start up procedure to restore cross connections.
36.34.9 Version 1.2

This is an internal test version based on ESZ8003 version 1.1 with enhancements to make the system more robust.
36.34.10 Version 1.1
Static cross-connections are properly restored at power-up.
Dependencies

ESX717 hardware version must be 1.0 or higher. SXU-V base unit software (SXZ630) version must be 1.1 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. ESX717 Boot Software (ESZ8002) must be version 1.1 or higher In V5.2 use, GMH (GMZ283) software version must be 10.1 or higher (V5 links between LE and AN). In V5.2 use, QMH (QMZ540) software version must be 10.5 or higher (V5 links between LE and AN). CCS-UNI (CCZ539) software version must be 5.2 or higher to support V5.2 functionality.

462
10004_22 2008 Tellabs.
MartisDXX Manager support for this unit is available in R12 SP2 or higher.
Restrictions

Link ID should not be used. ISDN BRI ports are not supported.
Bugs
Deferred/Non-deferred blocking of V5 links is not working.
36.35 SXU-V Unit: SXZ630 Unit Software

The software SXZ630 is used on SXU-V cross-connection unit (whose base unit is SXU 758) in the Tellabs 8140 midi and Tellabs 8150 basic nodes. The version 2.1 can be downloaded to SXU-V unit having the hardware version 1.0 of SXU758.
36.35.1 Version 2.1
Enhancements and Fixed Bugs (compared with previous official version 1.1)
When a cross connection bus switch-over from Xbus1 to Xbus2 occurs in SXU-V in switch node, SXZ630 doesn't send change information to ESZ8003. ESZ8003 v1.7 has a related bug and has to be updated to r1.8 to set the right XBUS information to ESX FPGA. (CRF ID 4005324). (fixed in v 2.1). Expanded flash device support. (fixed in v 2.0). The SXU-V (SXU758) hardware version number should be written to the flash as 1.0 (as it is) instead of 5.0. (fixed in v 1.2). Unexpected switchovers should not occur during the Enhanced External Clock test. (CRF ID 4004844). (fixed in v 1.2). Cross-connection data corruption during simultaneous commands from NMS and ESX was fixed. The problem was very rare but possible. (CRF ID 4004842). (fixed in v 1.2).
Dependencies

SXU-V (base unit SXU758) hardware version must be 1.0 or higher. SCU-H (SCZ545) software version must be 1.10 or higher to support SXU-V. In V5.2 use, ESX717 (ESZ8003) software version must be 1.8 or higher to support XBUS 2 of Tellabs 8140 midi and Tellabs 8150 basic nodes (CRF ID 4005324). In V5.2 use, GMH (GMZ283) software version must be 10.1 or higher (V5 links between LE and AN). In V5.2 use, QMH (QMZ540) software version must be 10.5 or higher (V5 links between LE and AN). CCS-UNI (CCZ539) software version must be 5.4 or higher to support V5.2.
10004_22 2008 Tellabs.

463
ISD-NT16 (IBZ610) software version must be 1.0 or higher to support V5.2. MartisDXX Manager support for this unit is available in Release 12 Service Pack 2 or higher.
Restrictions
No restrictions.
Bugs
The SXU-V unit disappears periodically from the list of available units when there is an EPS unit in the node and the node inventory has been deleted. The time period is about 30 seconds. This is a clear but minor problem (CRF ID 4004951).
36.35.2 Version 2.0

Expanded flash device support.
Dependencies

SXU-V (base unit SXU758) hardware version must be 1.0 or higher. SCU-H (SCZ545) software version must be 1.10 or higher to support SXU-V. In V5.2 use, ESX717 (ESZ8003) software version must be 1.0 or higher. In V5.2 use, GMH (GMZ283) software version must be 10.1 or higher (V5 links between LE and AN). In V5.2 use, QMH (QMZ540) software version must be 10.5 or higher (V5 links between LE and AN). CCS-UNI (CCZ539) software version must be 5.2 or higher to support V5.2 functionality. ISD-NT16 (IBZ610) software version must be 1.0 or higher to support V5.2. MartisDXX Manager support for this unit is available in Release 12 Service Pack 2 or higher.
Restrictions
No restrictions.
Bugs

464
10004_22 2008 Tellabs.
36.35.3 Version 1.4

This is an internal test version based on version 1.3. Enhancements and Fixed Bugs (compared with version 1.3)
E1 Layer1 Sa7 polling time 100ms. One link is polled every 100 ms. All 16 links will be polled once in 1.6s instead of 3.2s.
36.35.4 Version 1.3

This is an internal test version based on version 1.2 Enhancements and Fixed Bugs (compared with version 1.2)
XBUS 2 fix for ESZ8003, see the version 2.1. (CRF ID 4005324)
36.35.5 Version 1.2


The SXU-V (SXU758) hardware version number should be written to the flash as 1.0 (as it is) instead of 5.0. Unexpected switchovers should not occur during the Enhanced External Clock test. (CRF ID 4004844) Cross-connection data corruption during simultaneous commands from NMS and ESX was fixed. The problem was very rare but possible. (CRF ID 4004842)
Dependencies

SXU-V (base unit SXU758) hardware version must be 1.0 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. In V5.2 use, ESX717 (ESZ8003) software version must be 1.0 or higher. In V5.2 use, GMH (GMZ283) software version must be 10.1 or higher (V5 links between LE and AN). In V5.2 use, QMH (QMZ540) software version must be 10.5 or higher (V5 links between LE and AN). CCS-UNI (CCZ539) software version must be 5.2 or higher to support V5.2 functionality. MartisDXX Manager support for this unit is available in R12 SP2 or higher.
Restrictions
No restrictions.
465
10004_22 2008 Tellabs.
Bugs
36.35.6 Version 1.1
Dependencies

SXU-V (base unit SXU758) hardware version must be 1.0 or higher. SCU-H (SCZ545) software version must be 1.10 or higher. In V5.2 use, ESX717 (ESZ8003) software version must be 1.0 or higher. In V5.2 use, GMH (GMZ283) software version must be 10.1 or higher (V5 links between LE and AN). In V5.2 use, QMH (QMZ540) software version must be 10.5 or higher (V5 links between LE and AN). CCS-UNI (CCZ539) software version must be 5.2 or higher to support V5.2 functionality. MartisDXX Manager support for this unit is available in R12 SP2 or higher.
Restrictions
No restrictions.
Bugs
The SXU-V (SXU758) hardware version number has to be written as 5.0 (not 1.0) to the flash. The fake version number will not affect the normal operation of the unit. The priority level is low. Unexpected switchovers can occur during the Enhanced External Clock test, the priority level is medium. (CRF ID 4004844) Cross-connection data may corrupt during simultaneous commands from NMS and ESX. The problem is very rare but possible. (CRF ID 4004842) The SXU-V unit disappears periodically from the list of available units when there is an EPS unit in the node and the node inventory has been deleted. The time period is about 30 seconds. This is a clear but minor problem (CRF ID 4004951).

466
10004_22 2008 Tellabs.
36.36 Tellabs 8110 HTU-2M NTU: SBZ389 Unit Software

The software SBZ389 is used in HTU-2M HDSL NTU.
36.36.1 Version 1.0
Dependencies
No dependencies.
Restrictions

Line framing is always ON. Version 1.0 does not support 2 ms 106 delay. Version 1.0 does not support a 8 kbit/s carrier. Remote loop logic (V.54) does not work with a V.13 simulated carrier. If FSW&RAI usage is X-conn, TS0B1 must be X-conn. If FSW&RAI usage is regenerate, TS0B1 must be CRC.
Bugs
In OTU modes the menu might show that the EOC channel was disabled although it is always disabled in these modes.
10004_22 2008 Tellabs.

467
36.37 Tellabs 8110 STU-160 DSL NTU: SBZ385 Unit Software

The software SBZ385 is used on Tellabs 8110 STU-160 (STU315) network terminating units. Version 2.2 can be downloaded to units having the version 2.y of SBZ385 (where y=0, 1, 2...).
36.37.1 Version 2.2
Possibility to change the DTE capacity of STU-160 depending on the time of day. Enhancement. (CR ID 200015081)
Dependencies

Tellabs 8110 STU-160 hardware version must be 5.0 or higher. IUM-5T/IUM-10T/IUM-8 (UBZ436) software version must be 2.3 or higher. Tellabs 8100 manager support for all features of this unit is available in Release 14 or higher.
Restrictions

NTU settings backup support is only available in the downloadable version of SBZ385. NTU settings backup support requires IUM SW version 2.3 and SCP SW version 3.1 and/or SCU SW version 8.4 and/or XCG SW version 2.0 (or later versions). Note! Backup support return settings when the replaced NTU and the new NTU have the same type of DTE interface cards. If the DTE cards differ, the backup information is read from the NTU and the old backup information is lost. Control channel mode V.13 AIS detection is possible only when using DTE rate 64 or 128 kbit/s. Time dependent DTE capacity control is only available for interface 1. Time dependent DTE capacity control is not available with V.24 or G.703 64 kbits interface cards.
Bugs
No known bugs.

468
10004_22 2008 Tellabs.
36.37.2 Version 2.1
After IUM-8 reset modem might fail to reactivate line (CR ID 200010936).
Dependencies

Tellabs 8110 STU-160 hardware version must be 5.0 or higher. IUM-5T/IUM-10T/IUM-8 (UBZ436) software version must be 2.3 or higher. MartisDXX Manager support for all features of this unit is available in Release 10.0A or higher.
Restrictions

NTU settings backup support is only available in the downloadable version of SBZ385. NTU settings backup support requires IUM SW version 2.3 and SCP SW version 3.1 and/or SCU SW version 8.4 and/or XCG SW version 2.0 (or later versions). Note! Backup support return settings when the replaced NTU and the new NTU have the same type of DTE interface cards. If the DTE cards differ, the backup information is read from the NTU and the old backup information is lost. Control channel mode V.13 AIS detection is possible only when using DTE rate 64 or 128 kbit/s.
Bugs
No known bugs.
10004_22 2008 Tellabs.

469
36.37.3 Version 2.0
Neighbour node loop activation is now reliable (CRF ID 4003588).
Dependencies

Tellabs 8110 STU-160 hardware version must be 5.0 or higher. IUM-5T/IUM-10T/IUM-8 (UBZ436) software version must be 2.3 or higher. MartisDXX Manager support for all features of this unit is available in Release 10.0A or higher.
Restrictions

Bugs

470
10004_22 2008 Tellabs.
36.37.4 Version 1.8
Neighbour node loop activation is now reliable (CRF ID 4003588).
Dependencies

IUM-5T/IUM-10T/IUM-8 (UBZ436) software version must be 2.3 or higher. MartisDXX Manager support for all features of this unit is available in Release 10.0A or higher.
Restrictions

Bugs
No known bugs
10004_22 2008 Tellabs.

471
36.37.5 Version 1.7
Dependencies

Restrictions

Bugs
Neighbour node loop does not always work (CRF ID 4003588).

472
10004_22 2008 Tellabs.
36.37.6 Version 1.6
Improved reliability in unstable powering environment (CRF ID 4004103).
Dependencies

Restrictions

Bugs

After IUM-8 reset, modem might fail to reactivate line (CR ID 200010936). Neighbour node loop does not always work (CRF ID 4003588).
10004_22 2008 Tellabs.

473
36.37.7 Version 1.5

IP filtering support for LAN module now available (CRF ID 4002091). Local loop test works now without connection to IUM unit (CRF ID 4002085). X-bit polarity update used to cut traffic when data rate was 64 or 128 kbit/s. The bug is now fixed (CRF ID 4002329).
Dependencies
MartisDXX Manager support for all features of this unit is available in Release 10.0A or higher.
Restrictions

Bugs

After IUM-8 reset modem might fail to reactivate line (CR ID 200010936). Neighbour node loop does not always work (CRF ID 4003588). Unstable powering environment can affect modem start up (CRF ID 4004103).

474
10004_22 2008 Tellabs.
36.37.8 Version 1.4

AIS state in circuit loop test after trunk fail will return to Normal without resetting the counters (CRF ID 4001547). Degraded minutes value in G.821 menu branch is now correct.
Dependencies

MartisDXX Manager support for NTU backup is available in Release 10.0A. MartisDXX Manager support for X-bit and E-bits states in the V.110 frame are available in Release 10.0A. MartisDXX Manager support for V.13 AIS detection is available in Release 10.0A.
Restrictions

Bugs

After IUM-8 reset modem might fail to reactivate line (CR ID 200010936). Neighbour node loop does not always work (CRF ID 4003588). Version 1.4 does not support the IP filtering functionality of EHI392 (CRF ID 4002091). Local loop test does not work without connection to IUM unit (CRF ID 4002085). Unstable powering environment can affect modem start up (CRF ID 4004103). X-bit polarity update cuts traffic when data rate is 64 or 128 kbit/s (CRF ID 4002329).
10004_22 2008 Tellabs.

475
36.37.9 Version 1.3
Dependencies
MartisDXX Manager support for the EHI392 interface card is available in Release 9.0B.
Restrictions

No support for NTU backup support. (CRF ID 4000480) No support for V.13 AIS detection. (CRF ID 4001043) No support for totally locked menu panel. (CRF ID 4001395) No support for polarity change of X-bit in the V.110 frame. (CRF ID 4001485) No support for E-bits' (E1, E2 and E3) permanent 0 state in the V.110 frame. (CRF ID 4001487)
Bugs

After IUM-8 reset modem might fail to reactivate line (CR ID 200010936). Neighbour node loop does not always work (CRF ID 4003588). AIS state in circuit loop test after trunk fail will not return to Normal unless counters are reset (CRF ID 4001547). Degraded minutes in G.821 menu branch does not show the right value (always 0). Local loop test does not work without connection to IUM unit (CRF ID 4002085). Unstable powering environment can affect modem start up (CRF ID 4004103).
36.37.10 Version 1.2
Dependencies
No dependencies.
Restrictions

No support for NTU backup support. (CRF ID 4000480) No support for V.13 AIS detection. (CRF ID 4001043) No support for totally locked menu panel. (CRF ID 4001395) No support for polarity change of X-bit in the V.110 frame. (CRF ID 4001485) No support for E-bits' (E1, E2 and E3) permanent 0 state in the V.110 frame. (CRF ID 4001487) Does not support the EHI392 interface card (LAN Bridge with 10Base-T and 10Base-2 connectors).

476
10004_22 2008 Tellabs.
Does not support the File Management of the Network Element application with full file information (last modification date, time and modifier).
Bugs

After IUM-8 reset modem might fail to reactivate line (CR ID 200010936). Neighbour node loop does not always work (CRF ID 4003588). AIS state in circuit loop test after trunk fail will not return to Normal unless counters are reset. (CRF ID 4001547) Degraded minutes in G.821 menu branch does not show the right value (always 0). Node Loop activation and deactivation fails with the IF5-IF8 of IUM-10T (NTU does not support routing extension). Menu goes to the main menu level when the Exit button is pressed after failed remote loop activation (panel keys locked). Local loop test does not work without connection to IUM unit (CRF ID 4002085). Unstable powering environment can affect modem start up (CRF ID 4004103).
36.37.11 Version 1.1

Dependencies
No dependencies.
Restrictions

No support for NTU backup support. (CRF ID 4000480) No support for V.13 AIS detection. (CRF ID 4001043) No support for totally locked menu panel. (CRF ID 4001395) No support for polarity change of X-bit in the V.110 frame. (CRF ID 4001485) No support for E-bits' (E1, E2 and E3) permanent 0 state in the V.110 frame. (CRF ID 4001487) Does not support the EHI392 interface card (LAN Bridge with 10Base-T and 10Base-2 connectors). Does not support the File Management of the Network Element application with full file information (last modification date, time and modifier). No support for the VMI377 interface module (V.35 with the ISO 2593 connector). No support for the XMI378 interface module (X.21 with the ISO 4903 connector). No support for G.703 64 kB timing. No support for V.110b 56 kB synchronization.
Bugs

After IUM-8 reset modem might fail to reactivate line (CR ID 200010936). Neighbour node loop does not always work (CRF ID 4003588).
10004_22 2008 Tellabs.

477
AIS state in circuit loop test after trunk fail will not return to Normal unless counters are reset. (CRF ID 4001547). Degraded minutes in G.821 menu branch does not show the right value (always 0). Node Loop activation and deactivation fails with the IF5-IF8 of IUM-10T (NTU does not support routing extension). Menu goes to the main menu level when the Exit button is pressed after failed remote loop activation (panel keys locked). Line quality indication does not work correctly (it may halt after line break). The rules for parameter setting are not according to the software definition. CRC error counter in the LCD menu always shows zero. Faulty parameter scrolling in the LCD menu when handling 106 delay. Unnecessary errors at the start of Transmit & Receive test. G.821 interface alarms can be active even if the interface is not in use. Local loop test does not work without connection to IUM unit (CRF ID 4002085). Unstable powering environment can affect modem start up (CRF ID 4004103).
36.37.12 Version 1.0
Dependencies
MartisDXX Manager support for this NTU is available in Release 8.0.
Restrictions

No support for NTU backup support. (CRF ID 4000480) No support for V.13 AIS detection. (CRF ID 4001043) No support for totally locked menu panel. (CRF ID 4001395) No support for polarity change of X-bit in the V.110 frame. (CRF ID 4001485) No support for E-bits' (E1, E2 and E3) permanent 0 state in the V.110 frame. (CRF ID 4001487) Does not support the EHI392 interface card (LAN Bridge with 10Base-T and 10Base-2 connectors). Does not support the File Management of the Network Element application with full file information (last modification date, time and modifier). No support for the VMI377 interface module (V.35 with the ISO 2593 connector). No support for the XMI378 interface module (X.21 with the ISO 4903 connector). No support for the GMI373 interface module (G.703 64 K). No support for V.110b 56 kB synchronization.

478
10004_22 2008 Tellabs.
Bugs

After IUM-8 reset modem might fail to reactivate line (CR ID 200010936). Neighbour node loop does not always work (CRF ID 4003588). AIS state in circuit loop test after trunk fail will not return to Normal unless counters are reset. (CRF4001547). Degraded minutes in G.821 menu branch does not show the right value (always 0). Node Loop activation and deactivation fails with the IF5-IF8 of IUM-10T (NTU does not support routing extension). Line quality indication does not work correctly (it may halt after line break). The rules for parameter setting are not according to the software definition. CRC error counter in the LCD menu always shows zero. Faulty parameter scrolling in the LCD menu when handling 106 delay. Unnecessary errors at the start of Transmit & Receive test. G.821 interface alarms can be active even if the interface is not in use. Fault texts +12V and -5V have changed places. NTU identification number information is missing from the INFO menu. Downloaded SW indication not supported. Test menus not according to specification when panel keys are locked. The node loop is available when panel keys are locked. The menu hangs sometimes on main menu level after a visit to G.821 statistics. The response of panel keys is too slow. The hardware version of the DTE interface card is 1.7 when the interface card is disconnected. Signals and timing modes are named incorrectly for the X.21 interface card. Transferred bits and Errored bits are cleared when a test is aborted by test time-out. Local loop test does not work without connection to IUM unit (CRF ID 4002085). Unstable powering environment can affect modem start up (CRF ID 4004103).
10004_22 2008 Tellabs.

479
36.38 Tellabs 8110 STU-320/576/1088-2W/2304 SDSL NTUs: SBZ387 Unit Software

The software SBZ387 is used on STU-320/576/1088-2W/2304 SDSL NTUs. The version 1.3 can be downloaded to STU-320/576/1088-2W/2304 units having the version 1.y of SBZ387 (where y=0, 1, 2...).
36.38.1 Version 1.3
CFE bit polarity in the end-to-end CRC frame is changed. This makes EECRC compatible with CTU-S and CTU-R. This does not affect compatibility with other units because CTUs are first units to use bi-directional G.826. (CRF ID 4004042). Possible flash erasing at power up is prevented. This was caused by D type flip-flop that could go to an unspecified state after power up. (CRF ID 4004413).
Dependencies

STU-320/576/1088-2W/2304 (base unit STU327, STU328, STU319, STU318, respectively) hardware version must be 1.0 or higher. GMH (GMZ283) software version should be 6.10 or higher. QMH (QMZ540) software version should be 10.3 or higher. MartisDXX Manager support for this unit is available in Release 10.0 or higher.
Restrictions
Downloading this version to units with an older version (SBZ387 v1.0, v1.1 or v1.2) in PROM will not solve the flash erasing bug. If that problem exists, the only way to fix it is to change the PROM. HW version 1.0: Line framing is always ON. Does not support 2 ms 106 delay. Does not support 8 kbit/s carrier. Remote loop logic (V.54) does not work with the V.13 simulated carrier. If FSW&RAI usage is X-conn, TS0B1 must be X-conn. If FSW&RAI usage is regenerate, TS0B1 must be CRC
Bugs
No known bugs.

480
10004_22 2008 Tellabs.
36.38.2 Version 1.2

Support for MIF-V1 ASIC (CRF ID 4002493). The interface loop (IFL) works now even if the Rx signal is missing. The DTE rate adaptation works also in STU-320. The FSW&RAI usage parameters X-conn and X-conn (no inv.) works.
Dependencies

Restrictions

HW version 1.0: Line framing is always ON. Does not support 2 ms 106 delay. Does not support 8 kbit/s carrier. Remote loop logic (V.54) does not work with the V.13 simulated carrier. If FSW&RAI usage is X-conn, TS0B1 must be X-conn. If FSW&RAI usage is regenerate, TS0B1 must be CRC
Bugs
There is a very small possibility that the unit erases its flash settings at power up (CRF ID 4004413).
10004_22 2008 Tellabs.

481
36.38.3 Version 1.1
The self-test can be initiated by pressing the enter button twice in the configuration locked state (CRF ID 4002127).
Dependencies

Restrictions

Bugs

The menu structure of LAN Modules parameters IPaddress and IPmask have wrong characters (IP address class) in the text field. The interface loop (IFL) does not work if the Rx signal is missing. The DTE rate adaptation does not work in STU-320. The FSW&RAI usage parameter X-conn and X-conn (no inv.) does not work. There is a very small possibility that the unit erases its flash settings at power up (CRF ID 4004413).

482
10004_22 2008 Tellabs.
36.38.4 Version 1.0
Dependencies

Restrictions

Bugs

The menu structure of LAN Module parameters IPaddress and IPmask have wrong characters (IP address class) in the text field. The interface loop (IFL) does not work if the Rx signal is missing. The DTE rate adaptation does not work in STU-320. The FSW&RAI usage parameter X-conn and X-conn (no inv.) does not work. There is a very small possibility that the unit erases its flash settings at power up (CRF ID 4004413).
10004_22 2008 Tellabs.

483
36.39 Tellabs 8120 Mini Node PM: SMZ611 Unit Software

The software SMZ611 is used on the Tellabs 8120 mini node PM (SBM 2048PM) whose base unit is SMU759.
36.39.1 Version 1.1
Dependencies
MartisDXX Manager support is available in Release 12 service pack 2.
Restrictions
No restrictions.
Bugs
No known bugs.
36.39.2 Version 1.0
Dependencies
MartisDXX Manager support is available in Release 12 service pack 2.
Restrictions
No restrictions.
Bugs
The POTS interface faults are mapped incorrectly internally. Because of this bug all POTS interface problems activate a wrong fault. The wrong fault is shown to the user both in the LCD display and fault management application. This problem is not traffic affecting.

484
10004_22 2008 Tellabs.
36.40 Tellabs 8120 Mini Node V, VM, C, VG and E: SMZ430 Unit Software
Software SMZ430 is used in the Tellabs 8120 mini nodes V, VM, C, VG and E (SBM 2048V, SBM 2048VM, SBM 2048C, SBM 2048VG and SBM 2048E, respectively).
36.40.1 Version 2.3
Dependencies
No dependencies.
Restrictions
No restrictions.
Bugs
No known bugs.
36.40.2 Version 2.1
Dependencies
No dependencies.
Restrictions

Does not support AIS detection in unframed mode. Does not support 105 off delay parameters. Does not support BTE2048-2W module. Does not support X-connecting TS0Bit3.
Bugs

IA faults are mapped incorrectly, for example IA fault for block 1 is seen as RAM fault and IA fault for block 2 is seen as EPROM fault. Loop timeout parameter cannot be set. Setting for the SMU configuration NONE-NONE (C-type Mini Nodes) cannot be done. If alarm I/O forced control is used to set the alarm from on state to normal, the alarm led will still be on.
10004_22 2008 Tellabs.

485
36.40.3 Version 2.0
Dependencies
No dependencies.
Restrictions

No cooling fan monitoring support. No support for modules BTE-1088, BTE-4096. No support for modules G703-75, G703-120, G703-8M. High speed correction at 4Mbit < bit rate < 8Mbit (CRF 2000167). V.54 loop activation control. 106 delay corrections. Does not support BTE-384 module wetting current strapping info (in new version BTE-384 strapping possibility). Does not support AIS detection in unframed mode. Does not support 105 off delay parameters. Does not support BTE-2048-2W module. Does not support X-connecting TS0Bit3.
Bugs

LCD menu displays wrong names for modules V35-G704S and X21-G704S. IA faults are mapped incorrectly, for example IA fault for block 1 is seen as RAM fault and IA fault for block 2 is seen as EPROM fault. Loop timeout parameter cannot be set. Setting for the SMU configuration NONE-NONE (C-type Mini Nodes) cannot be done. If alarm I/O forced control is used to set the alarm from on-state to normal, the alarm led will still be on.

486
10004_22 2008 Tellabs.
36.40.4 Version 1.0
Dependencies
No dependencies.
Restrictions

No support for VCM432 channel board (VG and E type Mini Node). No support for the alarm interface module. Cross-connection (No support for CAS idle object, Not using enhanced cross connect RAM maintenance functions). Front panel push button support for cross-connection delete does not exist. No async test possibility in circuit loop tester. No 114 invert parameter in clock parameters. No support for BTE2048, V35-G704S and X21-G704S modules. Does not support Fsw-Rai usage: X-sync. No cooling fan monitoring support. No support for modules BTE-1088, BTE-4096. No support for modules G703-75,G703-120,G703-8M. High speed correction at 4Mbit < bit rate < 8Mbit (CRF 2000167). V.54 loop activation control. 106 delay corrections. Does not support BTE-384 module wetting current strapping info (in new version BTE-384 strapping possibility). Does not support AIS detection in unframed mode. Does not support 105 off delay parameters. Does not support BTE2048-2W module. Does not support X-connecting TS0Bit3.
10004_22 2008 Tellabs.

487
Bugs

There may occur an irrelevant module fault condition if the CAE application is active and uses only one module. Provisioning object allows to set 20 VF interfaces when SMU configuration restricts the number to 10 VF interfaces. Wrong GMH interface module choices in push button menu. Flash is always swapped after reset. Minor error in EAE parameter update. Error in CAE signalling bit update. LCD menu module choices of IF2 are not correct. When the GMH interface has loop to interface and unframed mode and no x-connections AIS (not RX signal) will be sent. Loop timeout parameter cannot be set. Setting for the SMU configuration NONE-NONE (C-type Mini Nodes) cannot be done.

488
10004_22 2008 Tellabs.
36.41 VMM Unit: VMZ295 Unit Software

The software VMZ295 is used on VMM units. Version 1.3 can be downloaded to VMM units with revision 1.y of VMZ295 (where y = 0, 1, 2,). Software supports all versions of the base unit.
36.41.1 Version 1.3

Dependencies
SXZ282 (SXU) SW version 6.9 (or newer) is needed to support TS0 integrity problem.
Restrictions
No restrictions.
Bugs
No known bugs.
36.41.2 Version 1.1

Dependencies
No dependencies.
Restrictions
Does not support satellite link.
Bugs
TS0 integrity problem with other timeslots.
36.41.3 Version 1.0

Dependencies
No dependencies.
Restrictions
Does not support satellite link.
Bugs

The updating of parameters of VDH471 interface module did not work correctly. TS0 integrity problem with other timeslots.
10004_22 2008 Tellabs.

489

22

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

22

Uploaded by

Copyright:

Available Formats

Tellabs 8100 Managed Access System Unit Software Version Dependencies

Tellabs 8100 Managed Access System Unit Software Version Dependencies

10004_22 2008 Tellabs.

2 CAE Unit: CAZ287 Unit Software .............................................................................. 45

3 CCS-UNI and CCO-UNI Units: CCZ539 Unit Software ............................................. 48

4 CCU Unit: SCZ286 Unit Software .............................................................................. 56

5 CXU-M Unit: SXZ288 Unit Software........................................................................... 64

10004_22 2008 Tellabs.

Tellabs 8100 Managed Access System Unit Software Version Dependencies

6 E3C Unit: GPZ641 Unit Software ............................................................................... 86

7 EAE Unit: EAZ418 Unit Software............................................................................... 87

8 ESU Unit: EMZ642 Unit Software .............................................................................. 88

9 GMH Unit: GMZ283 Unit Software ............................................................................. 98

Tellabs 8100 Managed Access System Unit Software Version Dependencies

10004_22 2008 Tellabs.

10 GMM Unit: GMZ438 Unit Software......................................................................... 117

11 GMU and GMU-A Units: GMZ460 Unit Software .................................................. 122

12 GMU and GMU-A Units: GMZ461 Unit Software .................................................. 138

10004_22 2008 Tellabs.

Tellabs 8100 Managed Access System Unit Software Version Dependencies

13 GMX Unit: GMZ544 Unit Software ......................................................................... 159

14 GMX2 Unit: GMZ802 Unit Software ....................................................................... 202

15 LAN Module: EHZ541 Unit Software ..................................................................... 207

Tellabs 8100 Managed Access System Unit Software Version Dependencies

10004_22 2008 Tellabs.

15.3 Version 1.0.................................................................................................................................................209

16 OMH/OMH-A Unit: OMZ675 Unit Software............................................................ 210

17 QMH and QMH-M Units: QMZ540 Unit Software .................................................. 216

18 SBU UNIT: UTZ549 Unit Software ......................................................................... 231

19 SCO Module: DPZ652 DSP Software .................................................................... 233

10004_22 2008 Tellabs.

Tellabs 8100 Managed Access System Unit Software Version Dependencies

20 SCU-H UNIT: SCZ545 Unit Software ..................................................................... 237

21 SXU-A and SXU-B Units: SXZ282 Unit Software.................................................. 248

22 SXU-C Unit: SXZ289 Unit Software ....................................................................... 282

Tellabs 8100 Managed Access System Unit Software Version Dependencies

10004_22 2008 Tellabs.

10004_22 2008 Tellabs.

Tellabs 8100 Managed Access System Unit Software Version Dependencies

30 Tellabs 8110 CTU-S HDSL NTU: SBZ605 Unit Software...................................... 325

31 Tellabs 8110 STE-10M NTU: SBZ792 Unit Software ............................................ 329

32 Tellabs 8120 Mini Node M: SMZ414 Unit Software .............................................. 331

Tellabs 8100 Managed Access System Unit Software Version Dependencies

10004_22 2008 Tellabs.

33 Tellabs 8130 Micro Node (SMH-U): SMZ533 Unit Software................................. 340

34 VCM-A UNIT: VCZ285A Unit Software .................................................................. 341

35 XCG Unit: SMZ538 Unit Software .......................................................................... 351

10004_22 2008 Tellabs.

Tellabs 8100 Managed Access System Unit Software Version Dependencies

36 Unit Software Version Dependencies in Discontinued Products ...................... 363

Tellabs 8100 Managed Access System Unit Software Version Dependencies

10004_22 2008 Tellabs.

10004_22 2008 Tellabs.

Tellabs 8100 Managed Access System Unit Software Version Dependencies

Tellabs 8100 Managed Access System Unit Software Version Dependencies

10004_22 2008 Tellabs.

10004_22 2008 Tellabs.

Tellabs 8100 Managed Access System Unit Software Version Dependencies

Tellabs 8100 Managed Access System Unit Software Version Dependencies

10004_22 2008 Tellabs.

The following utterances are used in the release notes.

10004_22 2008 Tellabs.

Tellabs 8100 Managed Access System Unit Software Version Dependencies