You are on page 1of 489

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

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
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

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
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

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
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

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
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
24.1 Version 3.3.................................................................................................................................................294 24.2 Version 2.0.................................................................................................................................................295 24.3 Version 1.3.................................................................................................................................................296

25 Tellabs 8110 CTE-S G.703 SHDSL NTU: DPZ654 DSP Software ........................ 297
25.1 Version 3.3.................................................................................................................................................297 25.2 Version 2.0.................................................................................................................................................298 25.3 Version 1.3.................................................................................................................................................299

26 Tellabs 8110 CTE-S and CTE-S/208 SHDSL NTU: SBZ673 Unit Software ......... 300
26.1 Version 3.0.................................................................................................................................................300 26.2 Version 2.0.................................................................................................................................................301 26.3 Version 1.0.................................................................................................................................................302

27 Tellabs 8110 CTU-512 HDSL NTU: SBZ672 Unit Software .................................. 303
27.1 Version 3.0.................................................................................................................................................303 27.2 Version 2.1.................................................................................................................................................304 27.3 Version 2.0.................................................................................................................................................305 27.4 Version 1.0.................................................................................................................................................306

10004_22 © 2008 Tellabs.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
9

.....................319 28..........................................2..310 28.......................1............................................4 Version 4........................................................................................10 Version 2..................................................................................................................................................................................................0.......................................3 Version 4.................................................314 28.............................................................................................2 Version 1.................................................................................................................................1...............8......................13 Version 2..............................2.....5 Version 1...........................0.................................0........317 28................315 28...........................................318 28.......................................7 Version 3.321 29....................................4 Version 1..........................323 29...................................................................................................................3......................................................................................................................1 Version 4.........................................................319 29 Tellabs 8110 CTU-R HDSL NTU: SBZ671 Unit Software .....318 28.....................................................................5 Version 4..............................0.......................4..............................0............1..................311 28....................................................... 331 32............1 Version 5...............................................................312 28.....................................................Table of Contents 28 Tellabs 8110 CTU-R HDSL..................................................................................................15 Version 1..............................................3.........................1.............................................0...1 Version 1.................................6......................8 Version 3.....................................6 Version 3.....................................................................17 Version 1...........11 Version 2.......................1 Version 2..................................................................................................................................................................326 30........................1 Version 3.1..............................................................................................................................................................5....................................... Tellabs 8110 CTE-R SHDSL...........................................................................325 30..............4....................................................... 329 31.......................................................................................................0.................................................................. 325 30.........................................2 Version 4.330 32 Tellabs 8120 Mini Node M: SMZ414 Unit Software ..........................................2 Version 1........................................................................2..315 28....331 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 10 10004_22 © 2008 Tellabs....................................................................322 29...........................................................................................16 Version 1..................................................0....................................4...................................................................................................................................329 31...................................................4 Version 1..........................................324 30 Tellabs 8110 CTU-S HDSL NTU: SBZ605 Unit Software....................................................................... Tellabs 8110 CTER/208 SHDSL and Tellabs 8110 STE-10M SHDSL NTUs: SBZ670 Unit Software307 28............................7............................................................................................................4.........18 Version 1....................328 31 Tellabs 8110 STE-10M NTU: SBZ792 Unit Software .................................. 320 29....1.................................................................................................0.....................................................................307 28......2 Version 2.......327 30..................................................318 28....................................3 Version 1...................................................................................................................................................12 Version 2....................................................................................................................................................................................3................316 28....................................3 Version 1..............................................................................................................14 Version 1......................... ..320 29..........2...309 28.................317 28.318 28......................317 28........9 Version 2....................

........3.................................................4 Version 3.................................................................13.................5.....1 Version 10....1............................336 32..............4..............................332 32.......3.................................2 Version 2..0..................................................................3 Version 4...................................................................................346 34......................349 35 XCG Unit: SMZ538 Unit Software ......................333 32...............................................................................................................................................................................................................1............................................................................ Tellabs® 8100 Managed Access System Unit Software Version Dependencies 11 ................10......................................3............................................345 34..........................................................................................................................................1.........................................................................................................4 Version 4.......................................333 32.............340 34 VCM-A UNIT: VCZ285A Unit Software ................................................................................0.......................................................................7 Version 2.................................................................................16 Version 2..........344 34..............................6 Version 3............................................................8 Version 3.......................................353 35................................9 Version 3.........................................................352 35..........2..0................................................5 Version 2.............................................................................................................................................................................................................................................................................344 34......................................2 Version 3...........................7 Version 3....................2................334 32..8....................................................................358 35.....12.................................................354 35...........................................8 Version 2.......................................................5 Version 3....347 34...........................................................................................................................................................................................................................................................348 34..............................................................6 Version 2............................5 Version 4.10 Version 2...........................................................................................7 Version 2.....................................................................................................................................................................................6..1................12 Version 2............................................15 Version 2....Table of Contents 32.........................................3 Version 3..............................................9 Version 2................................11 Version 1....................................................................359 35.................................346 34.............11.........................................2.................................................................................341 34....................................................................................................................................348 34......................3 Version 10................0..................................................................................................343 34..................................................................................................14.......2 Version 10.............................................................................................................11 Version 2..................1..................................................357 35........................................................................................................2 Version 4......................................................9 Version 2.....................................................................347 34...............................................................................................................................342 34............................................................... 341 34.........................................9........................2..........................................................................................................................................6 Version 4.......... 340 33....................................................................................................................................................10 Version 2.........................3............0....................................4 Version 2.........1.......................343 34.........................................................1 Version 2.......8 Version 2....338 33 Tellabs 8130 Micro Node (SMH-U): SMZ533 Unit Software............361 10004_22 © 2008 Tellabs.......355 35..2..............................345 34...........................3..........5..................................................................................................349 34.......... 351 35......................................6.....................................................4..................................356 35.................................................13 Version 2....................337 32................................4.............................................360 35....................340 33...............................................14 Version 2.......................332 32...........7...................................................................................................................................................351 35.................................................0.......................1 Version 3..........

................3 AIU Unit: ACZ7001 Unit Software .....................................1...............................392 36.....0..........................................................3 Version 1......7 CEU Unit: ACZ7004 Unit Software .............................5.......6 CEU Unit: ABZ607 Unit Software ..............11....0.......1.........................5..................... 363 36...............................................11......................2......................................385 36.367 36.................................................................................9...........................................2 Version 1..............................................................................................374 36.............................0.................................................5..........................................................................................................367 36.......................................7........................................................................................................................................................2 Version 2................................................................................3 Version 2..... ..........................1..........379 36.................................383 36....................................................................5 Version 2.......364 36...........................9............................3............................................................................................374 36..............................1 Version 1..2 Version 1....................382 36.....3..............................0..............................383 36.......................................................372 36...............368 36.........................................................................................................371 36.............................2...................................................373 36......................................................................................................................................................1 Version 2.9.............................................................................1............................366 36..........................................................................383 36........................387 36.........................5 Version 1....6 Version 1................................392 36......................6..5 CEU Unit: ABP732 Unit Software ......391 36.................367 36.......1............0..........................................................3............................8..............................................................0....................378 36..............................................................388 36......2 Version 1........................................9.........................................................................................1 Version 1...........3 Version 2...........1 Version 1..4.................373 36...............................................................................387 36................................................369 36......................6.....2 Version 1...................370 36..............................................................384 36.................7......................................................................6...................................................................................................................................4......................................................3 Version 1..............1 Version 2........0...........8.2 Version 2.........1...387 36.....................................................................................4 Version 2...................4.............3 Version 1................3.......5 Version 2.....................................................................................................................................................................................................................................................................1 Version 1.1......................4.............11......11...........6 Version 2.................................................................367 36...................1..................................4 Version 1..........................391 36.............................................................................................7...7....3........................................................................390 36...................................................363 36.........3 Version 1...............0.........................377 36..........................................377 36...........................................1 Version 1.11......380 36.....................018........1 Version 2.....375 36...1 Version 1...................................................................................3....................................6...................................019......8 ECS Unit: UBZ439 Unit Software...............................9................10 ESO Unit: ESZ8000 Boot Software............6.................................3 Version 1.......11..............................................................381 36..6............................................................................................11 ESO Unit: ESZ8001 Unit Software ......388 36................Table of Contents 36 Unit Software Version Dependencies in Discontinued Products ......................2.............................................................................................................5......................................385 36..............................................................................................................................................................................................................................................7......................................11.......................................................................1 AIU Unit: ABZ531 Unit Software ...................4....10..................................................1........4 CCO and CCS Units: CCZ445 Unit Software .......................................................386 36.......................9....365 36........................................................................................................................................................................................................................2.........4 Version 1..............383 36.......3...................................3...........................5......376 36.............380 36.......12 ESO Unit: UBZ 536 Unit Software....1 Version 1.......................................................................................................................6 Version 2..........2 Version 2...1 Version 3..2.....................................................................................................375 36.4............2 AIU Unit/Module ACP514: ACZ7000 Boot Software ..9...............................363 36.9 EPS-5T and EPS-10T Units: UBZ441 Unit Software.....................................0.......................7 Version 1........................................................0.....................................4 Version 2.........................................................................................................................................................................393 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 12 10004_22 © 2008 Tellabs............................................................389 36.....................5...............................................2 Version 3.................................

....................16 GCH-A Unit: GCZ284A Unit Software.................................................................414 36............................2...................16......2.......14...............393 36.........................................15 FRU Unit/Module FRE: FRZ535 Unit Software ........................................................399 36..............................11 Version 2..............16..............................12 Version 2................................................................................................................................................................21................4 Version 2....................................405 36..............21............................................................................423 36.......... 415 36..418 36.................6...................................................21.9 Version 2................................................................................................7.....................3 Version 3...5.....396 36.....1 Version 1..............4 Version 2....................9 Version 2.............................................................................1 Version 0..............................19.....................................................................9...............410 36.........................................................3 Version 1.........................................................................................................1 Version 2.....1 Version 3......................................10 Version 2..15.....403 36..............414 36.........................406 36............................................................0............8..................................................................417 36................................................................................................................................................................1...2 Version 2.......................................3 Version 1.........12...........................................................406 36.....................................................................................................422 36.....2 Version 3.................................................................21...........0.....10................................................................................................................................................19............4 Version 1...........................................................................................1 Version 2...............4......................7................4.....403 36....408 36.......12.....408 36....................1...................................................................21.......................409 36..............................................400 36................................................0.....................17............10 Version 2......................17 GMU-M Unit: GMZ546 Unit Software ...................7............................16...................................................................................................................................409 36........18.............................................. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 13 ............................................................................2...............................16.............................397 36...............................................................................................................5........................................5.........................................................................6 Version 1.................................421 36...................8 Version 2....411 36......................................................................................................................416 36...........................................................403 36.........................................................5 Version 2............................19..................14........1 Version 1.405 36.........................................................................................................................................11...16......................16....................3...............419 36..............................19...................................413 36.2 Version 1..........14..............................Table of Contents 36........................................2............412 36.....................................422 36......1 Version 1...................................................................407 36.................................................................................6 Version 2........................6 Version 2........405 36...................................................5 Version 1...................404 36............................0.................................0..................394 36...........1....................................19 ISD-LT and ISD-NT Units: UBZ532 Unit Software ........401 36..........................................398 36.................14...............21...........................................7 Version 2.........21............................................................................................................410 36..............................................424 10004_22 © 2008 Tellabs..........................................................3......................................................16............................................... IUM-10T and IUM-8 Units: UBZ436 Unit Software ...423 36....................402 36........................................6............3.........................................................................................20 ISD-LT16 Unit: IBZ610 Unit Software .................................................................................................1............................395 36.415 36....................395 36.................11 Version 2...............................2 Version 0...................................................2.............406 36.........................................................................................................4..............18 GMU-M Unit: GMZ547 Unit Software ..........................................................................19...................0...........................3.....6 Version 1...............14 FRU Unit: UBZ534 Unit Software ..................................16.......................................................................8.......................................................................................................1 Version 10...........................14.....3 Version 2...................................13 FBU Unit: FBZ612 Unit Software ............394 36.................................................420 36............0.............................................1 Version 1......401 36...........................................................16...................21..........................................15.........13........................................................................................2 Version 1...........19.........................5 Version 1...........4......8 Version 2...................................................................................1 Version 10.......21...................................411 36..20..............404 36............................4 Version 1......................................................................................1..................................................................21........5......5 Version 2...............................................7 Version 2...................................21 IUM-5T........21..412 36..14..............................................................16...........................................................0...16..........4......21..........

..................29.................................1 Version 8...................29.....................................................1 Version 1........................................................1......................3 Version 1................22............2 Version 1......................25...................1..2.........................................448 36......................................................................................................1 Version 1.......................................3 Version 1.....5 Version 8........................5 Version 2..............................................438 36................................................................................................................0..............447 36.....................................434 36................................436 36...............3 Version 3.54...........449 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 14 10004_22 © 2008 Tellabs...30....................................................................................................................................................................24................................................. 427 36........437 36............443 36...............15 Version 1......................28 SBM 64E NTU: SBE381 Unit Software......................441 36....................................................................22................432 36..........................................4.....2.....................................................................................................................30........446 36.............................24 NTU-2M Unit: SBZ542 Unit Software...............................................2 Version 1............................................439 36...............25.................................................445 36...................31........................425 36.........................................................................29.....................................25 SBM 384A NTU: SBA380 Unit Software .........................................4 Version 3.............2 Version 1........427 36.............................................................................3...............14 Version 1......................................................................................................................................3 Version 1..........443 36....1 Version 3.....................3..............26...0..................3..........3.22................1......................2 Version 1............6................................2........................1 Version 1..................................................................................................................4...............................................................435 36..........................................................................................21...............30 SCP Module: SCZ281 Unit Software .........3...........................................1 Version 1....2 Version 8................0........435 36..................................................................................................433 36.440 36...........................0.......435 36.......................................................434 36.................1..........4 Version 1...22 LIU-H Unit (ERH581 Module): ERZ550 Unit Software ...................................433 36.........................3 Version 8..................2.......................27......30.4 Version 1...........Table of Contents 36.....0......................................425 36...................................441 36.....2 Version 1...........................................................................................27...............31 SCU Unit: SCZ280 Unit Software ..................3...1 Version 1....................................................................................438 36.......30.............................445 36....................................................................................................4..............................................22...........................23.................................................2.............................................................................27.......442 36..6 Version 8...................................424 36.........................................430 36................................2 Version 3..............................................................435 36...............2...........29............................1....................446 36.......444 36............................2 Version 1.........2 Version 1....................................................................................................................26.....1................28.......431 36..................................441 36..................................30.....................3.......................................................................................................3..........................0.........................................................................................................................................................23............................4............1 Version 1.................................................28................................................................................................................................................................27 SBM 64A NTU: SBA381 Unit Software ..2 Version 1............................................................4.........................................................................444 36...........................2..............3 Version 1.....................446 36..................................5 Version 1.........440 36.........22...........31........................................2....................442 36..................................................................................................................4 Version 1.436 36.1..................25................5....................................................................438 36........................................................440 36............................0............................................................................................................432 36..............................................................................21....................................1 Version 1............................437 36.........................1 Version 1...........................24..........................5 Version 1......................429 36..........................23 LIU-H Unit: UBZ543 Unit Software ..........................31.........13 Version 1............31...................................................................................................... .......................................26 SBM 384E NTU: SBE380 Unit Software ...............437 36...............................................23...........................................434 36..........27...31..........................................................................4 Version 8.........................................5............439 36........................................448 36.....................................................................................................................1...................................3 Version 1......25...............428 36..................................3.........................................................................................................................4 Version 1............................................................................25...............................................................29 SBM 768A NTU: SBA382 Unit Software ......................21..........................................................................................31..................................

..........462 36........................470 36.................................................465 36.................................................................................................................................37................................477 36..........................................10 Version 1............................4 Version 1..........31.....................473 36..........................................8 Version 8....................................................................1 Version 1..................................467 36................34..................................................................................................................................................................................................4........480 36.............................................3 Version 2.................0............33.............................................................478 36.......................................37............35........................................................................................................464 36..................................................................................................................................32.......34....................................12 Version 1....................................458 36...................37...................................460 36......451 36....................463 36................................................................................................................................................455 36..476 36..9 Version 7..................................................1........34....................................1 Version 1............469 36........4 Version 1..................................7 Version 1.1 Version 1........1.........2..............................37.......................................................................................3.......................37....459 36..................................................11.......................2 Version 1...............................................4........33................................472 36...................................................454 36.......................454 36.................0.....462 36...........35............9 Version 1..........................38................................34........................35...............6..3.........................5..481 36...............1.........................5 Version 1..........................................................................................................462 36...................................................................1.....................................................................8....462 36.................................7..........0......................32 STU-56 DSL NTU: SBZ388 Unit Software ...............................1.....35 SXU-V Unit: SXZ630 Unit Software ....................37...............................36...................................471 36..................4 Version 1..................................................................463 36.......................................3 Version 1...........6 Version 1..........462 36............2...........................1.........460 36..........................37..........................................................461 36.......453 36.......Table of Contents 36..........................................................................466 36.........................................2 Version 2.............1 Version 1........................................................0.34..............................3 Version 1..................34.............10 Version 7..........33.......5 Version 1...........................34 SXU-V Unit: ESZ8003 Unit Software.............................................................................2....................................456 36..........8.........482 36...........................................33 STU-1088/2048 NTU: SBZ384 Unit Software ..........................................................468 36............................................2 Version 1.........................................................................................................................2....37.............2 Version 1......................4.37 Tellabs 8110 STU-160 DSL NTU: SBZ385 Unit Software .............................................37..........459 36...........................................................................1..........38 Tellabs 8110 STU-320/576/1088-2W/2304 SDSL NTUs: SBZ387 Unit Software ....................34........5 Version 1......31......................................................................................................467 36..............455 36............3 Version 1...................................4 Version 1........................................................3.........................................455 36..465 36...............36 Tellabs 8110 HTU-2M NTU: SBZ389 Unit Software ....................................6 Version 1...................................................................................................................................5....................................................................37..10..........................4....................................34..............37.......35.................................................461 36............38.......476 36..............................................................................0..0.........................35..................2 Version 2..........................................................6................................................. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 15 .....................................................................................7 Version 8.................3 Version 1...475 36...........................1 Version 1........................3................................2 Version 1.........474 36..............................................................................................................................4 Version 1.............................................35......................................31..................................................1 Version 2....................................................................... 468 36.................................1...........................9 Version 1.........................7..................................................................38......................8 Version 1.....................................................................................................37...........................................33................................1.......................................................452 36......................................................2.....................450 36..........................................6....................7 Version 1...................................................................................2..3.....................................................................................34...10 Version 1...38....................465 36............................................................................................................................................................32..........................483 10004_22 © 2008 Tellabs...............................5 Version 1...........................................................................................8 Version 1....33........................11 Version 1.....0..............................................31....................5................ 480 36......................................................................1 Version 2.............................................457 36..............................6 Version 1...........................454 36.....0..............34..

............................. C.......................................................1.........4 Version 1........................................484 36....................................................41.......................................1......................................................................................................................................................2 Version 1......0.. VG and E: SMZ430 Unit Software................489 36..................... VM........40............1 Version 1..................3...........................40........................................................................................................41 VMM Unit: VMZ295 Unit Software ........................................40 Tellabs 8120 Mini Node V............Table of Contents 36...........0..............................................................................................................1..............................2 Version 1..........41.........489 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 16 10004_22 © 2008 Tellabs..........................41...................487 36.......1 Version 2......486 36...................................485 36................ ..39.....0................................................................40............0..........39.......489 36.........484 36..................................................................3 Version 2...484 36...............................3 Version 1...............485 36...1 Version 1..............................................................................................................................2 Version 2.................................................................40..........................3...489 36...................39 Tellabs 8120 Mini Node PM: SMZ611 Unit Software .................................485 36...................................................

The latest version is always described first. interface units. If this is the case. The following utterances are used in the release notes.) The same information can be found in the relevant unit software description in a more detailed format. restrictions and bugs. If this is the case. Under every unit software version there are three to four items. in some cases. 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. nodes and network terminating units (NTUs) in the Tellabs® 8100 managed access system. unit software and base unit hardware. (See Chapter 1. Some general information of the unit(s) and unit software is given. In old release notes. They may.1 for more details on the table. At the beginning of the manual there is an interrelations table where you can find version dependencies information in a compact form. Each following chapter defines the features of different unit software. cause problems. please. If you have base unit versions in your network that are not mentioned in this document. The text No restrictions under version information means that there are no restrictions when using this version of software. The chapter is divided in subchapters according to different versions. 10004_22 © 2008 Tellabs. please. they may be sample or prototype units preceding actual production units. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 17 . contact Tellabs Oy. contact Tellabs Oy. dependencies. their versions and the version dependencies between e. the text No dependencies under version information means that all production hardware versions have been compatible at the time. enhancements and fixed bugs (if applicable). they are most probably sample or prototype versions. • • • The text No known bugs means that there are no bugs known to Tellabs Oy.g. They can also be versions currently regarded inadequate and consequently taken out of production.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). If you have unit software versions in your network that are missing from this document.

the unit concerned is not protected. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 18 10004_22 © 2008 Tellabs. Unit software version whose dependencies are described in that row. Version Indicator Notation Version number Description Strong dependency • A specific unit software version is required. No dependency • There is no logical connection. Note that only the official production versions of the software are listed in the table. • In the case of control/cross-connect units. Hardware version of the base unit. The notations used in the rows of the control and cross-connect unit data are explained in the following table. Note that XCG is listed under control unit data column although it is both a control and a cross-connect unit. the unit concerned is protected. . Rows marked in bold indicate SW products in production. Hardware base unit where the unit software is downloaded. The first Tellabs 8000 manager release that supports all functionality of the product is indicated. this information can be found in the release note of the unit software. Column Tellabs 8100 Network Elements Base Units HW Version Unit SW USW Version Description Commercial product name. 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.1 Interrelations The interrelations table below shows in compact form dependencies between Tellabs 8100 unit software. and dependencies between the unit software version of the particular row and Tellabs® 8000 network manager releases. 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). • In the case of control/cross-connect units. Basic Data consists of the following columns. • A particular network element is not required. The meaning of the different columns and notations are described below. See the release note of a relevant network element for more information.General 1.) A unit software version may work with an earlier or later version of another software. (Note that MartisDXX Manager is referred to as Tellabs 8100 manager in R13 or higher and Tellabs 8000 manager in R15 or higher. Unit software product code name. Weak dependency • Any version of the unit software is compatible.

9 SXU-C SW 2.5 - 6.0 2.5 CCU SW 2.1 - 9.0 1.4 8.1 10.0 8.4 2.1 1.10 1.4 2.9 6.1 8.2 ACZ7001 1.1 3.0 3.4 8. 1.4 2.4 Control Unit Data SCP SW 3.4 2.0 ABP551 2.0A SP3 9.0 2.2 2.1 10.11 - 1.1 - 3.9 6.0 10.0 Any Any 10.0A SP3 9.0 ABP513 1.1 10.4 1.0 1.0 10004_22 © 2005 Tellabs.1 Any 3.0 1.10 1.11 SXU-V SW 1.9 6.0 ABP551 2.1 3.0 ACZ7001 ACZ7001 CAZ287 CCZ445 1.0 CXUM SW 10.5 3.9 2.3 1.10 1.0 Unit SW USW Vers.2 1.0A SP3 ABZ531 ABZ531 ABZ531 ABZ531 ACZ7001 ACZ7001 1.0A SP3 AIU1:1/ AIU1:4 AIU1:1/ AIU1:4 CAE CCO/CCS ACP514 ACP514 CAE224 CAE258/ CAE227 1.5 3.4 8.2 1.4 Any 8.1 1.0/3.2 ABZ531 1.2 2.0 1.0 1.4 3.11 2.4 8.5 3.1 3.0 1.0 2.0 ACZ7000 1.0A SP3 8.2 ACZ7001 1.8 - Any - 6.11 2.5 GMX2 SW Any Any SXUA/B SW 6.6 1.0A SP3 9.10 1.4 1.0 ABP551 HW 1.7 5.1 3.10 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 19 .1 ABP551 HW 1.11 2.10 XCG SW 2.5 3.1 10.9 5.6 ABP513 1.5 3.1 10.2 ACZ7000 1.4 - 3.0 AIU1:1/ AIU1:4 ACP514 1.6 2.1 Other Data Other Units Tellabs 8100/8000 Manager Release 9.General Basic Data Tellabs 8100 Network Elements AIU AIU AIU AIU AIU1:1/ AIU1:4 Base Units ABU257 ABU257 ABU257 ABU257 ACP514 HW Vers.10 1.0A SP3 9.0 ACZ7001 1.1 SCU SW 8.4 8.9 6.11 - 9.1 3.0 ACZ7000 1.0A SP3 9.0 2.0 ACZ7000 1.10 2.11 2.4 2.0 1.1 1.1 8.4 2.6 ABP513 HW 1.3 1.7 2.5 3.0 2.2 ACZ7001 1.4 SCU-H SW 1. 1.11 2.1 3.1 Cross-Connect Unit Data GMX SW 3.9 6.

0 1.5 2.0 1.0 2.1 3.1 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 20 10004_22 © 2005 Tellabs.17 3.0 4.1 3.1 2.15 3.1 1.1 Cross-Connect Unit Data GMX SW 3.6 1.1A ACZ7004 1.1A 10.0 2.1 3.4 8.1 1.4 8.4 8.1 1.018 12 12 12A CCZ539 CCZ539 CCZ539 CCZ539 CCZ539 CCZ539 SCZ286 SCZ286 SCZ286 SCZ286 ABP732 ABP732 ABZ607 ESZ8003 1.10 1.17 3. 3.0 Unit SW USW Vers.1A 10.11 2.0 1.0 2.10 1.1 1.17 3.8 3.15 GMX2 SW Any Any Any Any SXUA/B SW Any Any Any Any Any Any 6.11 2.6 2.4 8.1 SCU SW 8.8 ESZ8003 1.8 ESZ8003 1.1A 10.6 1.2 1.9 6.8 5.1 3.0 3.0 ACZ7004 2.10 1.0 2.0 ABZ607 1.0 ABP732 1.1 3.1 3.0 CCU SW 2.6 1.1 10.1A 10.0 4. 5.1 Other Data Other Units Tellabs 8100/8000 Manager Release 12A SP3 12A SP3 12A SP2 11 SP1 11 SP1 10.0 2.4 8.0 2.9 SXU-C SW 2.1 1.0 2.1 3.1 1.11 SXU-V SW 2.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.1 3.5 Control Unit Data SCP SW 3.17 3. .1 1.4 8.1 3.0 4.5 2.4 8.019 1.5 2.018 2.0 ACZ7004 1.10 XCG SW 2.4 SCU-H SW 1.0 2.0 2.1 10.1 3.10 1.4 8.2 4.0 ABZ607 1.15 3.2 1.9 6.1 2.0 2.7 2.1 3.8 3.7 5.0 2.0 CXUM SW Any Any Any Any 10.6 1.

5 2.10 XCG SW 2.0 2.9 SXU-C SW 2.1 1.0 OMZ675 3.11 2.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.5 - Control Unit Data SCP SW 3.0 1.018 ABZ607 1.0 2.0 OMZ675 3.2 EMZ642 1.2 EMZ642 1.0 - - - - - - - - - - - 13A SP1 CTE-R CTE-S V.35 CTE-S V.36 CTE-S/208 X.3 - - - - - - - - - - - 15A DPZ653 2.0 1.0 OMZ675 1.018 DPZ653 3.0 EMZ642 1.0 SBZ673 3.0 2.1 - Other Data Other Units Tellabs 8100/8000 Manager Release 12 12A 12 15A ABZ607 ACZ7004 ACZ7004 SBZ674 ACZ7004 1.0 2.0 SBZ673 2.0 2.0 2.0 CXUM SW 10.0 SBZ674 1.0 OMZ675 1.1 1.0 2.10 1.0 2.0 2.0 2.0 ABP732 1.4 SCU-H SW 1.21 CTE-R CTE-S V.15 3.0 13 10004_22 © 2005 Tellabs.1 3.3 SBZ670 3.9 6.21 CTE689 CTE685 CTE688 CTE686 CTE807 CTE803 CTE806 CTE804 CTE689 CTE685 CTE688 CTE686 1.0 1.15 3.35 CTE-S/208 V.1 3.0 DPZ653 3.0 1.35 CTE-S V.0 1.11 2.0 SBZ674 1.36 CTE-S X.0 2.4 8.0 1. 1.0 - - - - - - - - - - - SBZ670 3.0 DPZ653 1.0 ABP732 1.1 - Cross-Connect Unit Data GMX SW 3. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 21 .10 1.21 CTE-R/208 CTE-S/208 V.36 CTE-S X.1 10.1 SCU SW 8.0 CCU SW 2.9 6.0 2.018 ABZ607 2.0 SBZ670 3. 2.1 10.0 Unit SW USW Vers.0 2.5 2.15 GMX2 SW SXUA/B SW 6.0 1.4 8.0 ABP732 1.11 SXU-V SW 1.

0 2.0 SBZ673 2.35 CTE-S V.0 SBZ673 2.2 DPZ653 1.21 CTE-S/208 G.0 OMZ675 1.703 CTE-S V.36 CTE-S X.0 SBZ673 3.0 2.0 1.0 2.0 2.21 CTE-S G.36 CTE-S X.703 CTE-S V.0 2.0 2.0 DPZ654 3.0 1. .2 EMZ642 1.0 2.0 - - - - - - - - - - - 13 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 22 10004_22 © 2005 Tellabs.35 CTE-S V.35 CTE-S V.2 EMZ642 1.1 OMZ675 1.0 1.35 CTE-S/208 V.35 CTE-S V.703 CTE-S/208 G.1 DPZ654 1.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.0 Unit SW USW Vers.0 1. 1.3 3.1 DPZ654 1.0 2.0 1.21 CTE-S G.General Basic Data Tellabs 8100 Network Elements CTE-R CTE-S V.0 2.703 CTE-S/208 V. 1.36 CTE-S X.0 1.0 OMZ675 1.0 1.0 2.0 2.703 CTE-S G.3 2.0 SBZ673 1.2 DPZ653 1.0 2.21 CTE-S G.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.0 2.0 15A 13 13 15A - - - - - - - - - - OMZ675 1.1 13 SBZ673 1.0 OMZ675 1.703 CTE-S G.703 CTE-S G.0 SBZ673 1.0 2.2 EMZ642 1.0 1.36 CTE-S/208 X.36 CTE-S X.0 2.0 DPZ653 3.0 1.0 - - - - - - - - - - - SBZ670 3.0 OMZ675 3.703 CTE-S V.0 SBZ674 1.0 OMZ675 3.

0 SBZ671 1.0 1.0 1.0 2.1 - - - - - - - - - - - 15 10004_22 © 2005 Tellabs. 1.0 QMZ540 10.0 1.0 1.0 SBZ672 SBZ672 SBZ672 SBZ670 2.21 CTU-512 V.0 DPZ653 1.0 1.35 CTU-512 X.0 1.0 SBZ792 1.0 SBZ672 GMZ283 10.35 CTU-512 X.0 SBZ671 1.0 1.0 SBZ671 1.0 1.General Basic Data Tellabs 8100 Network Elements CTU-512 V.0 SBZ792 1.0 SBZ792 1.3 SBZ674 1.0 1. 3.0 1.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.0 1.0 2.21 Control Unit Data Unit SW USW Vers.0 QMZ540 10.3 SBZ674 2.21 CTU-512 V.3 - - - - - - - - - - - 15B SBZ670 4.0 1.3 SBZ674 2.0 1.0 DPZ794 1.0 1.0 DPZ653 3.3 SBZ792 1.0 DPZ653 3.0 1.0 1.21 CTU-512 V.5 GMZ283 10.0 QMZ540 10.35 CTU-512 X.0 4.0 1.0 DPZ794 1.5 GMZ283 10.0 1.5 SBZ671 1.0 1.35 CTU-512 X.5 GMZ283 10.0 DPZ653 3.2 - - - - - - - - - - - 15A SBZ670 4.0 2.0 CCU SW 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 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 2.0 DPZ794 1.0 2.3 SBZ674 2.0 DPZ794 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 23 .0 QMZ540 10.

0 QMZ540 10.4 2.0 SBZ671 1.2 SBZ671 1.0 2.0 QMZ540 10.3 1.2 3.5 SBZ670 1.3 SBZ671 1.0 1.1 SBZ671 1.1 SBZ670 1.0 1.0 QMZ540 10.3 SBZ674 1.0 1.0 DPZ653 1.0 DPZ653 1.5 SBZ670 1.2 SBZ671 1.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.3 1.0 1.5 2.0 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 14A 3P1 SBZ670 SBZ670 SBZ670 SBZ670 SBZ670 SBZ670 SBZ670 SBZ671 SBZ671 SBZ671 SBZ671 3. .4 1.0 Unit SW USW Vers.0 1.0 1.0 1.5 GMZ283 10.0 2.0 1.8 1.0 1.5 SBZ670 1.0 1. 4.5 GMZ283 10.3 SBZ671 1.3 SBZ674 1.3 SBZ674 1.0 1.5 13A SP1 13A SP1 13 SP1 13 SP1 12 SP1 12 SP1 14 14 12 SP1 12 SP1 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 24 10004_22 © 2005 Tellabs.2 - - - - - - - - - - - SBZ671 1.0 QMZ540 10.0 1.5 GMZ283 10.0 1.3 SBZ792 1.0 DPZ794 1.0 2.0 DPZ653 1. 2.5 GMZ283 10.

0B SP12 9.5 GMZ283 10.35 CTU-S X.0B SP12 9.35 CTU-S X.10 2.21 CTU-S G703 CTU-S V.5 GMZ283 10.0 1.1 2.10 2.6 10.0B SP12 9.0 10.5 GMZ283 10.0B SP12 SBZ671 SBZ605 SBZ605 SBZ605 SBZ605 SXZ288 SXZ288 SXZ288 SXZ288 SXZ288 SXZ288 SXZ288 SBZ670 1.21 CTU-S G703 CTU-S V.10 2.0B SP12 9.35 CTU-S X.0 1.2 10.0 5.1 3.21 CTU-S G.1 2.2 10.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.3 10.0 QMZ540 10.0 1.4 10.0 1.0 2.10 2.General Basic Data Tellabs 8100 Network Elements CTU-R CTU-S G703 CTU-S V.0 <5.10 2.5 GMZ283 10.0 Unit SW USW Vers.5 10004_22 © 2005 Tellabs.3 10.0B SP12 9.0 1.0 5.5 GMZ283 10.0 5.6 10.15 Cross-Connect Unit Data GMX SW GMX2 SW SXUA/B SW SXU-C SW 2.0B SP12 9.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.0 QMZ540 10.0 1.0 1.0 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 25 .0 1.0 <5.0 5.0 QMZ540 10.17 2.0 QMZ540 10.0 1.0 1.703 CTU-S V.0 5.10 SXU-V SW - Other Data Other Units Tellabs 8100/8000 Manager Release 12 SP1 14 14 11 SP2 11 SP2 9.1 1.17 2.0 1.4 10. 1.0 QMZ540 10. 1.35 CTU-S X.10 2.0 1.

0 Any Any Any Any Any Any Any Any CXUM SW 2.2 10.0 1.4 SCU-H SW 1.6 XCG SW 2.1A 10.4 ESZ8000 1.6 1.0 Other Data Other Units Tellabs 8100/8000 Manager Release 9.0 1.4 8.9 SXU-C SW 2.1 3.10 2.1 1.1 Any Any Any Any Any Any 3.1 10.0 9.7 CCU SW Any Any Any Any - Control Unit Data SCP SW 3.0A 10.6 1.5 2.4 8.0B SP12 13 8.13 2.1 1.0/2.0 1.0 1.0 Any Any Any Any Any 8.0 1.0 2.0 10.12 Any - Cross-Connect Unit Data GMX SW Any GMX2 SW Any SXUA/B SW Any Any Any 10. <5.9 2.4 GMZ283 6.6 1. .0B SP12 9.10 Any SXU-V SW Any 1.0B SP12 9.1 1.10 2.9 UBZ536 2.14 2.6 1.0 1.0 <5.0/2.1 PDF593 HW 2.14 2.1 1.0 1.0 1.1 6.0 Unit SW USW Vers.6 2.9 6.0 1.13 2.4 GMZ283 6.0 1.4 ESZ8000 1.6 1. 2.0A SXZ288 SXZ288 SXZ288 GPZ641 EAZ418 UBZ439 UBZ441 UBZ441 UBZ441 UBZ441 ESZ8001 ESZ8001 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 26 10004_22 © 2005 Tellabs.0 1.6 1.0 1.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.0 1.7 3.6 1.4 2.1 1.12 1.0 1.1 SCU SW 8.6 2.0 <5.9 10.0A SP2 UBZ536 2.0A SP2 10.6 1.2 10.0 3.0A SP2 10.

0 SBZ674 1.9 ESZ8001 2.0 GMZ460/461 1.179 with GMU450 HW 1.4 SCU-H SW 1.0.0.12 CCU SW Any Control Unit Data SCP SW 3.1 15 10004_22 © 2005 Tellabs.5 Any 4. SCO785 HW 3.1 GMZ460/461 1. GMZ460/461 1.5 Any Any UBZ536 2.0 SBZ674 1.0 2.7 with GMU450 HW 2.6 1.9 UBZ534 1. SCO785 HW 3.0A 15 ESZ8001 UBZ536 EMZ642 ESU ESU783/ ESM784 1.4 1.0 EMZ642 1.9 6.1 Any 10.1 3.4 8. 2.0.4 GMZ283 6.5 SXU-C SW Any SXU-V SW 1.6 1.1 GMX2 SW Any SXUA/B SW 6.1 3. GMZ460/461 1. 1.1 8.4 ESZ8000 1.0.0 Unit SW USW Vers.179 with GMU450 HW 1.11 Any 3. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 27 .7 with GMU450 HW 2.5 GMZ283 6.6 3.9 10.1 Any Other Data Other Units Tellabs 8100/8000 Manager Release 10.0 1.5 CXUM SW Any Cross-Connect Unit Data GMX SW 4.General Basic Data Tellabs 8100 Network Elements ESO ESO ESU Base Units ESO570 UBU254 ESU783/ ESM784 HW Vers.1 SCU SW 8.6 XCG SW Any Any 3.4 8.4 1.0A 10.6 2.

0 SBZ674 1.1 8.7 with GMU450 HW 2.0 EMZ642 1.5 Any Any ESU ESU783/ ESM784 1.4 1.General Basic Data Tellabs 8100 Network Elements ESU Base Units ESU783/ ESM784 HW Vers.6 3.0 GMZ460/461 1.7 with GMU450 HW 2. GMZ460/461 1.19 - Any Any Any GMZ460/461 1.0 Any 3.0 SBZ674 1.179 with GMU450 HW 1.1 - 10.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. GMZ460/461 1. 1.4 SCU-H SW 1.0 SBZ674 1.4 1.0 EMZ642 1.5 Any 4. GMZ460/461 1.1 8.0 GMZ460/461 1.5 CXUM SW Any Cross-Connect Unit Data GMX SW 4.6 2.1 SCU SW 8. .0.6 XCG SW 3.0 Unit SW USW Vers.0.9 Any 3.7 with GMU450 HW 2.0.8 Any 3. 1.179 with GMU450 HW 1.179 with GMU450 HW 1.10 CCU SW Any Control Unit Data SCP SW 3.0 14 SP3 14 SP1 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 28 10004_22 © 2005 Tellabs.

0 1.9 FRZ535 0.9 6.9 2.9 FRZ535 0.12 2.0 SBZ674 1.7 GMZ283 6.7 3.1 8.0 CXUM SW Any Cross-Connect Unit Data GMX SW 3.1 3.1 1.11 2. GMZ460/461 1.7 2.9 FRZ535 0.19 GMX2 SW SXUA/B SW Any SXU-C SW Any SXU-V SW Any Other Data Other Units Tellabs 8100/8000 Manager Release 14 SP1 EMZ642 ESU ESU783/ ESM784 1.11 2.4 1.0 FBZ612 UBZ534 UBZ534 UBZ534 UBZ534 UBZ534 1.0 Unit SW USW Vers.0B SP6 9.01.6 2. 1.0 Any 2.0.6 XCG SW 2.4 1.0 Any 3.2 2.0 SBZ674 1.0.0 1.18 - Any Any Any GMZ460/461 1. 1.0 1.7 GMZ283 6.0B SP6 9.7 with GMU450 HW 2.9 6. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 29 .9 12A SP1 11 SP3 11 SP2 9.1 8.6 1.7 CCU SW Any Control Unit Data SCP SW 3.1 3.8 2.4 1.1 2.4 8.4 SCU-H SW 1.5 6.0 GMZ460/461 1.9 6.179 with GMU450 HW 1.1 SCU SW 8.0 S35755.0 - 10.2 1.7 2.8 3.4 8.9 FRZ535 0.179 with GMU450 HW 1.6 1.1 3.6 2.A0 13A SP1 FBU FRU FRU FRU FRU FRU FBU763 UBU259 UBU259 UBU259 UBU259 UBU259 1.2 - 3.10 1.7 GMZ283 6.4 8.1 GMZ283 6.General Basic Data Tellabs 8100 Network Elements ESU Base Units ESU783/ ESM784 HW Vers.0 8.2 3.1 - C1.3 Any 3.9 6.0B SP6 10004_22 © 2005 Tellabs. GMZ460/461 1.10 1.6 1.0 EMZ642 1.3 1.8 Any 1.1 3.12 2.0 FRZ535 0.2 1.8 2.1 3.2 Any Any Any Any Any - 6.4 8.1 GMZ283 6.0 1.1 1.10 2.7 with GMU450 HW 2.

0 8.2 10.x Unit SW USW Vers.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.0B SP6 8. .0 GDM 298 HW 1.3 2.10 2.2 2.9 2.1 0.0A 8.0 6.5 6.0B SP6 9.x GDM 298 HW 1.9 10.6 SXU-V SW 1.9 5.0 10.0 CCU SW 2.6 2.1 1.0 4.4 8.0 3.0 Any Any Any Any Any Any Any Any Any SCU-H SW 1.0A FRZ535 FRZ535 GCZ284A GCZ284 GMZ283 GMZ283 GMZ283 GMZ283 GMZ283 GMZ438 GMZ438 GMZ438 GMZ438 UBZ534 1.9 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 30 10004_22 © 2005 Tellabs.x GDM 298 HW 1.0 10.1 3.1 1.0 5.1 Any Any Any Any Any Any Any Any Any SCU SW 8.0 5.4 Any Any Any Any Any 6.10 6.0 12 12 10.1 1.1 1.0A 8.0A 8. 1.0 1.1 10.0 1.5 6.1 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.x 1.9 6.6 2.6 2.x GDM 298 HW 1.0 8.0 GMZ283 6.x 1.4 5.6 1.1 - Other Data Other Units Tellabs 8100/8000 Manager Release 9.6 1.0 1.0 4.6 1.12 1.5 SXU-C SW 2.8 Any Any Any Any Any 2.x 1.9 UBZ534 1.7 2.0 GMZ283 6.0 5.2 Any Any Any Any Any Any Any Any Any Control Unit Data SCP SW 3.04.5 6.8 2.4 8.x 8. 0.1 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.

7 2.6 CCU SW Any Any Any Any Any Any Any Any Any Any Any Control Unit Data SCP SW 3.6 1.0 1.8 1.1 1.7 2.0 2.7 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 31 .8 1.7 DSU453 HW 1.0 GMZ461 1.0 GMZ460 1. 1.5 8.1 1.7 2.5 1.4 1.6 1.1 2.10 1.5 8.7 2.1 2.1 3.5 8.0/2.6 GMZ461 1.7 1.8 DSU453 HW 1.0 GMZ460 1.4 DSU453 HW 2.7 2.0 GMZ460 1.5 8.1 3.1 CXUM SW 2.8 6.6 1.7 2.1 3.0 1.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.6 10004_22 © 2005 Tellabs.6 XCG SW 2.6 1.8 6.1 3.1 2.7 2.0/2.7 SXU-V SW 1.7 2.1 1.0 1.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.8 6. 1.0 10.5 8.7 2.0 1.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.1 2.6 1.0 Unit SW USW Vers.7 2.0 1.7 2.1 SCU SW 8.1 2.7 2.8 6.7 2.7 2.1 2.8 DSU453 HW 1.8 6.5 8.8 SXU-C SW 2.5 8.1 3.1 1.1 3.1 1.0/2.1 2.0 1.1 1.8 6.1 1.11 1.1 3.7 DSU453 HW 1.8 DSU453 HW 1.6 1.0 1.0 1.1 Other Data Other Units Tellabs 8100/8000 Manager Release 12A SP3 12A SP3 12A SP3 10.0 GMZ461 1.6 1.0/2.6 1.1 3.8 DSU453 HW 1.1 2.1 1.7 1.7 2.6 1.0 GMZ460 1.1 2.5 8.8 6.5 GMZ461 1.0 GMZ461 1.0 1.8 6.0 GMZ460 1.7 2.8 6.1 1.8 DSU453 HW 2.1 3.6 1.7 2.5 8.7 2.1 3.0 GMZ460 1.1 2.7 2.5 SCU-H SW 1.0/2.6 1.8 6.4 8.9 1.

3 - - - - 11 SP4 11 SP4 11 SP4 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 32 10004_22 © 2005 Tellabs.5 1.4 8.0 10.0/2.4 3.3 4.1 Do not use!!! 3.11 1.4 4.0 3.11 1.4 GMZ547 10.7 - Cross-Connect Unit Data GMX SW Any Any Any Any 4.0 1.22 3.0 1.6 1.6 1.1 3.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.6/ 3.7 2.6 4.0 3.5 GMZ460 1.0 10. 1.24 3.24 4.0/2.6 1.1 2.1 2.11 - - 3.4 SCU-H SW 1.21/ 4.0 GMX GMX GMX GMX588 GMX588 GMX588 1.0 10.0 3.0 3.1 3.7 SXU-V SW 1.0 GMZ546 10.0 3.0 GMZ544 GMZ544 GMZ544 - - - 1.0 4.1 CXUM SW 2.22 4.0 1.21 CCU SW Any Any Any Any - Control Unit Data SCP SW 3.9 SXU-C SW 2.1 3.6 1.0 10.1 GMX2 SW Any SXUA/B SW 6.7 2. .0 1.6 3.7 2.7 2.2 4.0 Unit SW USW Vers.11 1.3/ 3.4/ 3.1 2.7 2.1 SCU SW 8.1 - Other Data Other Units Tellabs 8100/8000 Manager Release 10.22/ 4.11 1.4 10.9 6.24/ 4.4 8.21 4.8 6.2 4.11 XCG SW 2.0 1.11 1.0 11 SP4 11 SP4 11 SP4 11 SP4 11 SP4 GMZ461 GMZ461 GMZ546 GMZ547 GMZ544 GMZ544 GMZ544 GMZ544 GMZ544 GMZ460 1.4 8.11 1. 1.0/2.8 6.7 2.

0 Unit SW USW Vers.5 3.0/2.11 1.0 1.11 1.0 QMZ540 10.6/1.16 1.1A GMZ544 GMZ544 GMZ544 GMZ544 GMZ544 GMZ544 GMZ544 GMZ802 GMZ802 GMZ802 GMZ802 GMZ802 SBZ389 10004_22 © 2005 Tellabs.0 1.0/2.0/2.20 1.0 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 33 . 3.0 1.18 2.15 3.5 10.15 3.18 2.0 1.18 2.21 1.15 1.0 1.0/2.19 3.1A 10.18 1.6/1.0 1.0 1.0 CCU SW - Control Unit Data SCP SW SCU SW SCU-H SW 1.2 GMX2 SW 1.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.0 1.18 3.5 3.6 2.18 3.11 1.0 1.18 2.17 3.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.16 1.20 1.19 3.6 1.6 1.8 3.2 1.6/1.1A 16A SP2 16A SP2 16A SP2 16A SP2 16A SP2 GMZ238 10. 1.6/1.17 3.18 XCG SW CXUM SW - Cross-Connect Unit Data GMX SW 3.0 1.6 1.18 1.21 1.8 3.6/1.0 1.

1 with STU315 HW 5.1 8. .1 2.4 SCU-H SW 1.0 SBZ385 2.0 1.10 1.8 - 3.1 with STU315 HW 5.1 8.1 12 SP1 IUM-8 UBU768 2.0 SBZ385 2.1 12 SP1 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 34 10004_22 © 2005 Tellabs.1 - 3.4 1.4 8.0 1.4 1.0 2.0 UBZ436 3.0 - Any - Any - 1.0 UBZ436 2.0 SBZ385 2.4 1.5 - Control Unit Data SCP SW 3.0 UBZ436 3.1 Other Data Other Units Tellabs 8100/8000 Manager Release 11 SP1 10.2 CCU SW 2.0 1.0 8. 1.4 1.8 3.0 1.6 2.5 1.1 with STU315 HW 5.2 SXU-V SW 1.6 2.1A 12A SP3 SBZ385 1.0 2.6 1.6 2.0 8.17 Any GMX2 SW Any Any Any SXUA/B SW Any Any Any Any SXU-C SW 10.0 3.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.0 12 SP1 UBZ532 UBZ532 IBZ610 UBZ436 IUM-8 UBU768 2.8 with STU315 HW 4.0 SBZ385 1.6 1.6 XCG SW 2.0 CXUM SW 10.0 2.1 - Cross-Connect Unit Data GMX SW 3. 1.0 - 3.8 with STU315 HW 4.0 - Any - Any - 1.1 8.1 12 SP1 IUM-5T/ IUM-10T/ IUM-8 UBU239/ UBU255/ UBU768 2.8 with STU315 HW 4.8 with STU315 HW 4.1 1.0 Unit SW USW Vers.1 with STU315 HW 5.0 - Any - Any - 1.1 SCU SW 8.0 2.0 SBZ385 1.0 SBZ385 2.0 SBZ385 1.1 3.

0 2.0 SBZ385 1.1 10.4 SBZ385 1.2 8.4 1.1A 10.6 1.1 1.0 VCZ285A 10.8 with STU315 HW 4.4 8.0 SBZ389 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 35 .6 2.0 Any Any Any Any Any Any Any Any Any - Any Any Any Any Any Any Any Any 1.2 1.0 1.0 12 SP1 IUM-5T/ IUM-10T IUM-5T/ IUM-10T LAN Module UBU239/ UBU255 UBU239/ UBU255 EHI392/ EBH718/ EBH719 2.2 1.4 1.4 8.0 SBZ385 2.6 - 2.1 SBZ385 1.0 UBZ543 1.0 1.7 CCU SW - Control Unit Data SCP SW 3.2 3.0 Unit SW USW Vers.0A SP2 LIU-H LIU-H LIU-H LIU-H UBU714/ ERH581 UBU714/ ERH581 UBU714/ ERH581 UBU714 1.1 1.4 SCU-H SW 1.1A 10.2 3.8 with STU315 HW 4.1 Other Data Other Units Tellabs 8100/8000 Manager Release 12 SP1 UBZ436 IUM-5T/ IUM-10T/ IUM-8 UBU239/ UBU255/ UBU768 2. 2.6 2.0 1.1 SMZ414 5.0 - - Any Any - - Any Any - - SBZ384 1.1 with STU315 HW 5.1 3.1A 10004_22 © 2005 Tellabs.1 UBZ543 1.1A 10.0 1.0 ERZ550 ERZ550 ERZ550 UBZ543 1.1 - 8.0 2.General Basic Data Tellabs 8100 Network Elements IUM-5T/ IUM-10T/ IUM-8 Base Units UBU239/ UBU255/ UBU768 HW Vers.1 with STU315 HW 5.0 2.4 1.5 SBZ387 1.0 1.2 - 3.0 CXUM SW - Cross-Connect Unit Data GMX SW Any GMX2 SW SXUA/B SW Any SXU-C SW SXU-V SW 1.0 UBZ436 2.6 1.0 1.0 2.0 1.0A 10.6 XCG SW 2.4 8.3 1.1 SCU SW 8.0 2.3 1.4 8.2 10.0 - Any - Any - 1.0 1.1 UBZ543 1.6 1.2 3.4 - 1.4 2.6 1.1 8.0 1.0 SBZ385 2. 2.1 ERZ550 1.2 Any Any Any Any 3.0 UBZ436 UBZ436 EHZ541 2.5 - 3.

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.4 8.5 10.0 2.1 1.5 3.9 10.4 8.0 1.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.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 Other Data Other Units Tellabs 8100/8000 Manager Release 10.2 4.0 3.1 1.4 8.0 SCO HW 4. 1.6 XCG SW 2.1 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 36 10004_22 © 2005 Tellabs.0 SCO HW 4.1 3.0 CXUM SW Any Any Any Any Any Any Any Any Any Any Any Any Cross-Connect Unit Data GMX SW Any 4. .5 10.0 2.6 1.3 3.1 3.6 1.6 1.0 3.6 1. 1.1 1.2 10.2 3.5 10.6 1.0/2.6 1.10 10.2 GMZ283 6.0 3.1 3.0 SCO HW 3.2 4.1 1.0 1.0 1.7 10.0 3.10 SCO HW 4.5 3.0 3.5 3.1 3.5 2.6 1.0 2.1 1.0 1.6 1.0 3.1 Any Any Any Any Any Any Any GMX2 SW Any Any Any Any Any SXUA/B SW Any 10.11 10.2 3.6 1.1 Any Any Any Any Any 1.4 Any Any Any Any Any Any SCU-H SW 1.4 8.1 1.0 2.0 3.6 1.0 2.0 3.4 8.1 3.0 2.5 CCU SW Any Any Any Any Any Any Any Any Any Any Any Any Control Unit Data SCP SW 3.0 3.2 4.1 3.6 1.1 Any Any Any Any Any Any SCU SW 8.8 10.0 2.0 Unit SW USW Vers.

0 8.0 1.0 2.12 GMZ283 6.6 1.0 1.0/2.0 8.5 1.5 GCZ284 2.0 1.0 GMZ283 any GCZ284 2.0 8.0 1.0 2.5 1.0 8.3 1.6 1.6 1.3 2.0/2.0 10.0 1.12 GCZ284 2.0/2.0 1.0 1.0 3.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.6 1.0 2.6 1.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 1.12 GMZ283 6. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 37 .5 GMZ283 6.0/2.0 2.1 11 SP1 8.1 1.6 XCG SW 2.0 Unit SW USW Vers.1 6.0 2. 10.1 1.6 1.0 1.0 QMZ540 QMZ540 QMZ540 QMZ540 QMZ540 QMZ540 SBA381 SBE381 SBA380 SBE380 SBA382 SMZ430 SMZ430 GMZ283 any GMZ283 any GMZ283 any 10004_22 © 2005 Tellabs. 3.4 2.0 1.0 1.3 1.1 - Other Data Other Units Tellabs 8100/8000 Manager Release 11 SP1 12 SP1 12 SP1 10.0 8.4 1.3 1.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.0 1.0 8.

2.0 1.0 2.1 3.0 2.8 3. .0 3. 6.0 2.0 Unit SW USW Vers.0 6.2 OMZ675 1.1 3.1 1.2 15A 14 SP3 13A SP5 13 13 9.3 5.0 2.6 4.0 2.0 3.1 6.4 1.2 OMZ675 1.0 10.0 5.1A SP7 10.0 3.8 GMX2 SW SXUA/B SW Any SXU-C SW Any SXU-V SW 1.0 OMZ675 2.1 1.0 1.1 2.1A SP7 10.1A SP7 12 SP2 11 SP2 11 SP2 OMZ675 3.3 1.6 SCU-H SW XCG SW CXUM SW - Cross-Connect Unit Data GMX SW 3.0 2.0 3.0 4.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.0 SMZ430 SMZ414 SMZ414 SMZ414 SMZ611 UTZ549 UTZ549 DPZ652 DPZ652 DPZ652 DPZ652 DPZ652 SCZ281 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 38 10004_22 © 2005 Tellabs.0 OMZ675 1.3 CCU SW - Control Unit Data SCP SW SCU SW 7.1 Other Data Other Units Tellabs 8100/8000 Manager Release 8.0 4.4 1.

1 1.13 1.5 8.1 1.1A SP3 10.1 1.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.0 1.1 1.1 1.0 3.1 1.1A SP3 10.1 3.1 1.11 1.1A SP3 10.2/4.1 1.1 - Other Data Other Units Tellabs 8100/8000 Manager Release 9.2/4.0 8.0 9.0 3.4 2.0 2.0 10.0 2.1 1.0 8. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 39 .6 7.6 2.1A SP3 10. 3.6 CCU SW - Control Unit Data SCP SW 3.0 9.1 1.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.0 3.0 8.6 7.1A SP3 10.1A SP3 10.10 1.1 1.14 1.1 1.1 1.0 3.1 1.0 SCU SW 7.2 3.1 Unit SW USW Vers. 3.18 1.1A SP3 SCZ281 SCZ281 SCZ281 SCZ280 SCZ280 SCZ545 SCZ545 SCZ545 SCZ545 SCZ545 SCZ545 SCZ545 SCZ545 10004_22 © 2005 Tellabs.0 3.1A SP3 10.

General Basic Data Tellabs 8100 Network Elements SMH-U (Micro Node) STE-10M Base Units SMH502/ 503/505/506 STE790 HW Vers.2 1.0 SBZ792 1.3 UBZ436 2.0 IUM-5T/10T HW 1.7 - - - - - - - - - - - DPZ794 1.0 5.3 UBZ436 2.9.0 SCO HW 3.5 CXUM SW - Cross-Connect Unit Data GMX SW 4.0 4.0 1. 1.0 EMZ642 1.1 SBZ670 4.8 1.5 - 4. OMH HW 1.1 - 10.0.10.0A Tellabs® 8100 Managed Access System Unit Software Version Dependencies 40 10004_22 © 2005 Tellabs.0 OMZ675 2.1 GMX2 SW Any SXUA/B SW 10.0 EMZ642 1.0 1.0 SBZ388 SBZ385 SBZ385 SBZ385 SBZ385 SBZ385 1.0 4.0 OMZ675 2.3 UBZ436 2. .0 OMH HW 1.0A 10.0 UBZ436 2.1 2.0 SCO HW 3.0 - - - - 3.1 2.1 CCU SW - Control Unit Data SCP SW SCU SW SCU-H SW XCG SW 3. ESU HW 1.0 SBZ670 4. 2.0A 10.0 5.5 - - STU-56 STU-160 STU-160 STU-160 STU-160 STU-160 STU325 STU315 STU315 STU315 STU315 STU315 1.5 SXU-C SW SXU-V SW - Other Data Other Units Tellabs 8100/8000 Manager Release 9.0 Unit SW USW Vers.0B 14 10. ESU HW 1.3 14 SP3 9.0A 10.3 UBZ436 2.2 2.0 DPZ794 1.0 5.0 14 SP6 SMZ533 SBZ792 STE-10M STE790 1.

5 1.3 10.2 10.10 QMZ540 10.5 10.0 - - 9.5 10.0 SBZ384 SXZ282 SXZ282 SXZ282 SXZ282 SXZ282 SXZ282 SXZ282 1.6 - - - - 10.0 5.0 SBZ387 1.3 CCU SW 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 10.4 10.3 GMZ283 6.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.2 - - - - - - - - - - - 10.0B 13A SP5 13A SP5 13A SP5 13A SP5 10004_22 © 2005 Tellabs.3 UBZ436 2.0 - Any Any Any Any Any Any Any Any Any Any Any Any Any Any 1.6 1.0A 10. 1.4 10.6 1.0 5.0 SBZ385 SBZ385 SBZ387 UBZ436 2.0A 10. 4.0 5.3 GMZ283 6.3 10.0/2.2 10.0/2.0 1.10 QMZ540 10.6 1.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 10.10 1.0 5.6 1.0 5.0 4.4 10.0 5.6 10.6 1.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.3 GMZ283 6.1 10.0 5.6 1.6 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 41 .6 10.

10 2.9 6.6 1.10 2.6 1.1 ESZ8002 1.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.5 IBZ610 1.12 2.0B SP12 9.9 6.11 1.1 QMZ540 10.11 1.10 - Cross-Connect Unit Data GMX SW GMX2 SW SXUA/B SW 6.0B SP12 9.2 10.0 ESZ8003 1.10 2.0B SP12 9.0 2.0B SP12 ESZ8003 1.0 4.2 10.1 QMZ540 10.11 1.10 2. 4.0 Unit SW USW Vers.8 CCZ539 5.0 5.0B SP12 9.1 4.11 1.1 5.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.10 - - - - - - 1.10 SXU-V SW 2.0 SXZ630 1.1 4.1 QMZ540 10.0 12 SP2 SXU-V SXU758 1.4 GMZ283 10.5 IBZ610 1.11 - - - 1.11 2.10 2.0 ESZ8003 1.1 Other Data Other Units Tellabs 8100/8000 Manager Release SXZ282 SXZ282 SXZ289 SXZ289 SXZ289 SXZ289 SXZ289 SXZ630 9.1 12 SP2 SXU-V ESX717 1.0 CCZ539 5.2 GMZ283 10.5 SXZ630 2. .1 - - - 1.1 CCZ539 5.4 GMZ283 10.11 1.11 12 SP2 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 42 10004_22 © 2005 Tellabs.1 4.10 XCG SW CXUM SW 2.8 10.1 1.11 2.0 2.8 SXU-C SW 10.12 2. 6.10 - - - - - - 1.

0 Unit SW USW Vers.1 ESZ8002 1.1 CCZ539 5.1 1.4 6.8 SXU-V ESX717 1.1 4.4 5.1 1.10 - - - - - - 1.6 1.0 2.9 - Any - 1. 1.0 12 SP1 10004_22 © 2005 Tellabs.1A 10. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 43 .1 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 CCZ539 5.5 IBZ610 1.4 5.4 5.6 - Any Any Any Any Any - Any - Any Any Any Any - Any - 5.6 1.14 1.0 ESZ8003 1.1 ESZ8002 1.1 - - - 1. 1.1 GDH521/ GDH522 HW 1.10 - - - - - - 1.0 ESZ8003 1.1A 8.5 Any - Any Any Any Any Any - Any Any Any Any Any - 1.1 SXZ630 2.1 QMZ540 10.1 CCZ539 5.General Basic Data Tellabs 8100 Network Elements SXU-V Base Units ESX717 HW Vers.2 VCZ285A VCZ285A VCZ285A VCZ285A VMZ295 SMZ538 10.3 3.6 1.0 2.0 SXZ630 1.6 1.1A 10.0 SXZ630 2.10 Other Data Other Units Tellabs 8100/8000 Manager Release 12 SP2 ESZ8003 SXU-V ESX717 1.1 ESZ8002 1.1 10.10 CCU SW - Control Unit Data SCP SW SCU SW SCU-H SW 1.1 QMZ540 10.4 GMZ283 10.0 3.1 4.1 QMZ540 10.5 IBZ610 1.10 XCG SW CXUM SW - Cross-Connect Unit Data GMX SW GMX2 SW SXUA/B SW SXU-C SW SXU-V SW 1.2 GMZ283 10.1A 10.2 10.4 GMZ283 10.8 - - - 1.03.

0 2.3 2.0 Unit SW USW Vers.2 2. .0 1.1 3.0 SMZ538 SMZ538 SMZ538 SMZ538 SMZ538 SMZ538 GDH521/ GDH522 HW 1.2 2.1 GDH521/ GDH522 HW 1. 2.1 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 44 10004_22 © 2005 Tellabs.2 1.4 3.1 GDH521/ GDH522 HW 1. 3.3 3.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.0 9.1 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 12 SP1 12 SP1 12 SP1 11 SP1 9.1 GDH521/ GDH522 HW 1.

XCG (SMZ538) ) software can be any version MartisDXX Manager support for this unit is available in Release 8.2 with only the CIF signalling parameter verification error fixed.2 Version 2.3 This is an unofficial version based on CAZ287 release r2.1 or higher SCP (SCZ281) software can be any version SCU (SCZ280) software can be any version. 10004_22 © 2008 Tellabs. SCU-H (SCZ545) software version must be 1.6 or higher. Bugs • The internal signalling parameter verification operates incorrectly.8 or higher.1 Version 2. Restrictions • No restrictions.0. SXU-V (SXZ630) software version must be 1.2 Dependencies • • • • • • • • • Base unit must be version 2. Tellabs 8160 A111 and Tellabs 8140 midi nodes. This error produces very short signalling bit errors about once in 15 sec in every channel. This version should not be used once the next official version is available. 2. 2. GMX (GMZ544) software version must be 3.CAE Unit: CAZ287 Unit Software 2 CAE Unit: CAZ287 Unit Software The software CAZ287 is used on the CAE unit in Tellabs 8150 basic. SXU-A/B (SXZ282) software version must be 5. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 45 .7 or higher.0 or higher.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies 46 10004_22 © 2008 Tellabs. This error produces very short signalling bit errors about once in 15 sec in every channel. Module conflict fault is set active even if module type is not defined. Interface object operates faulty (set fault mask) corrected (attribute is not set by NMS). SXU-V (SXZ630) software version must be 1. XD IA is allocated even if not needed. . Bugs • • • • • • • • • • • • Locking object bug. Interface object allows change to coding parameter in a locked interface.0.7 or higher.8 or higher. Module types can not be read from unit when unit is not in inventory. COMBO/ADPCM faults are activated incorrectly. Restrictions • • • Level supervision is not supported. SCU-H (SCZ545) software version must be 1.CAE Unit: CAZ287 Unit Software 2.0 or higher. The internal signalling parameter verification operates incorrectly. USW test object not supported (used by production testing). Interface blocking fault is not monitored. External groud mask value is not returned correctly (CSE251 modules).1 or higher SCP (SCZ281) software can be any version SCU (SCZ280) software can be any version.6 or higher. Inventory operations do not affect hardware parameters. XCG (SMZ538) ) software can be any version MartisDXX Manager support for this unit is available in Release 8.3 Version 2. In some load situations unit may reset (internal message buffers). GMX (GMZ544) software version must be 3. X-Bus test port is not allocated.1 Dependencies • • • • • • • • • Base unit must be version 2. SXU-A/B (SXZ282) software version must be 5. Using signalling modules may in some cases disturb other units in the same node.

1 or later. Bugs • • • • • • • • • • • • Locking object bug. Does not use whole interface address allocation. Module types can not be read from unit when unit is not in inventory. Interface object allows change to coding parameter in a locked interface.7 or higher. XD IA is allocated even if not needed.0 or higher.0 to 2. This is needed because of a signalling data cross connect error in SXZ282. SXU-A/B (SXZ282) software version must be 5. Inventory operations do not affect hardware parameters. Restrictions • • • • Level supervision is not supported. USW test object not supported (used by production testing). The internal signalling parameter verification operates incorrectly. This error produces very short signalling bit errors about once in 15 sec in every channel. COMBO/ADPCM faults are activated incorrectly. Interface blocking fault is not monitored.1 or higher SCP (SCZ281) software can be any version SCU (SCZ280) software can be any version. Module conflict fault is set active even if module type is not defined. Interface object operates faulty (set fault mask) corrected (attribute is not set by NMS). Tellabs® 8100 Managed Access System Unit Software Version Dependencies 47 . Note that unrecoverable errors may occur if CAE has locked interfaces with allocated XD capacity when updating CAZ287 version 2.0 Dependencies • • • • • • • • • Base unit must be version 2. External groud mask value is not returned correctly (CSE251 modules). XCG (SMZ538) ) software can be any version MartisDXX Manager support for this unit is available in Release 8.8 or higher. • 10004_22 © 2008 Tellabs. XD IA is allocated with such parameters that SXZ282 can not operate correctly with it.0.CAE Unit: CAZ287 Unit Software 2.4 Version 2.6 or higher. SXU-V (SXZ630) software version must be 1. X-Bus test port is not allocated. SCU-H (SCZ545) software version must be 1. GMX (GMZ544) software version must be 3. Using signalling modules may in some cases disturb other units in the same node. In some load situations unit may reset (internal message buffers).

SCU-H (SCZ545) software version must be 1. MartisDXX Manager support for new countries (CRF ID 4005109) is available in Release 12A Service Pack 3 or higher. SXU-V (SXZ630) software version must be 2. Enhancements and Fixed Bugs • Terminating calls to CCS-UNI lead to continuous cadence (CR ID 200011089).2 functionality. SXU-A/B (SXZ282) software version can be any version. SXU-V (ESZ8003) software version must be 1. Tellabs 8150 basic and Tellabs 8160 A111 nodes. While using CAS functionality.1 Version 5. While using V5.1 or higher.2 is available in Release 12 Service Pack 2 or higher.1 or higher. interface parameters in the Tellabs 8100 manager database should be updated from hardware to remove a consistency check failure.8 or higher. SXU-V (SXZ630) software version must be 1.10 or higher. SCU-H (SCZ545) software version must be 1. The version 5.6 or higher while using CAS functionality. If v1.8 can be downloaded to CCS-UNI units having the version 3. Dependencies • • • • • • • • • • • • • CCS-UNI (base unit PBU560) hardware must be 3. SCP (SCZ281) software version must be 3. 3. GMX (GMZ544) software version must be 3. While using V5.2 functionality. SXU-V (ESZ8003) software version must be 1.0 or higher.8 This version is only available for CCS-UNI. SCU (SCZ280) software version must be 8. While using CAS functionality.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.2 functionality.1 or higher (SCP unit is optional).1 or higher. XCG (SMZ538) software version must be 2. .1 of PBU560. µ-law is not supported.17 or higher. Restrictions • • PCM coding and decoding are only according to A-law. While using V5.4 or higher.1 or higher.0 of CCS-UNI is replaced with this version. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 48 10004_22 © 2008 Tellabs. MartisDXX Manager support for V5.

SCP (SCZ281) software version must be 3.1 or higher (SCP unit is optional).CCS-UNI and CCO-UNI Units: CCZ539 Unit Software Bugs • No known bugs. XCG (SMZ538) software version must be 2. While using V5. While using V5. Dependencies • • • • • • • • • • • • • CCS-UNI (base unit PBU560) hardware must be 3.2 functionality. Mexico1 V5.4 or higher. 3. If v1. While using V5.7 This version is only available for CCS-UNI. SXU-V (SXZ630) software version must be 1. While using CAS functionality. SCU (SCZ280) software version must be 8. SCU-H (SCZ545) software version must be 1. MartisDXX Manager support for V5. GMX (GMZ544) software version must be 3.2 settings changed.8 or higher.2 is available in Release 12 Service Pack 2 or higher.6 or higher while using CAS functionality.2 functionality.1 or higher. 10004_22 © 2008 Tellabs.17 or higher. SXU-A/B (SXZ282) software version can be any version.10 or higher.1 or higher.2 settings changed.1 or higher. SXU-V (SXZ630) software version must be 2.2 Version 5.1 or higher. MartisDXX Manager support for new countries (CRF ID 4005109) is available in Release 12A Service Pack 3 or higher. SXU-V (ESZ8003) software version must be 1. Enhancements and Fixed Bugs • • • Reduced battery pulsing too slow fixed.0 of CCS-UNI is replaced with this version.2 functionality. interface parameters in the Tellabs 8100 manager database should be updated from hardware to remove a consistency check failure. Malaysia V5.0 or higher. While using CAS functionality. Bugs • No known bugs. SCU-H (SCZ545) software version must be 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 49 . Restrictions • • PCM coding and decoding are only according to A-law. SXU-V (ESZ8003) software version must be 1. µ-law is not supported.

GMX (GMZ544) software version must be 3. . SXU-V (SXZ630) software version must be 1. (CRF ID 4005109). (CRF ID 4005077). XCG (SMZ538) software version must be 2. When there is a switch over between SXU-Vs. Germany. MartisDXX Manager support for V5.-24.17 or higher. CCS-UNI Country support. Mexico2. With some gain values (down gain = -5dB . Chile. CCS-UNI can't communicate with SXU-V via TV5-channel anymore. SXU-V (ESZ8003) software version must be 1. SCU (SCZ280) software version must be 8.4 doesn't really change gain settings when using freely selectable gain values. (CRF ID 4004974). Malaysia. • • • • • Dependencies • • • • • • • • • • • • • CCS-UNI (base unit PBU560) hardware must be 3. Spain. Productional improvements (CRF ID 4005124).8 or higher. Hungary and Austria. Enhancements and Fixed Bugs • CCS-UNI: Incorrect reference point. South Africa. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 50 10004_22 © 2008 Tellabs. This is a non-production version based on version 5. Currently supported countries are: Finland.1 or higher. Argentina. SXU-A/B (SXZ282) software version can be any version.2 is available in Release 12 Service Pack 2 or higher. SCU-H (SCZ545) software version must be 1. India.4 or higher. Gain values must be set to fixed list values before using freely selectable values. While using V5.1 or higher (SCP unit is optional). Sweden. SXU-V (SXZ630) software version must be 2. CCS-UNI problems when rising interface state. While using CAS functionality.4 This version is only available for CCS-UNI. (CRF ID 4005162). Mexico3. CCS-UNI v5.0 or higher. phones that are off hook will not receive dial tone until they go on hook and off hook. up attenuation > -1. SCU-H (SCZ545) software version must be 1. Brazil. SXU-V (ESZ8003) software version must be 1.6 or higher while using CAS functionality. While using V5.9dB.1 or higher. While using CAS functionality.5dB) speech channel is over damped (13dB extra damping). X-bus switch-over problem in CCS-UNI (CRF ID 4005322): when switchover from Xbus1 to Xbus2 occurs in SXU-V in switch node.10 or higher. SCP (SCZ281) software version must be 3.3 Version 5. While using V5. Mexico.1 or higher. No dial tone after SXU-V switch over.2 functionality. Ireland.2 functionality. MartisDXX Manager support for new countries (CRF ID 4005109) is available in Release 12A Service Pack 3 or higher.CCS-UNI and CCO-UNI Units: CCZ539 Unit Software 3. Denmark.2 functionality.2. United Kingdom.1 or higher.

(CRF ID 4004530) There is an IN USE group operation failure on CCS-UNI while doing a large amount of changes. If v1.17 or higher. µ-law is not supported. (CRF ID 4003704) Dependencies • • • • • • • • • • CCS-UNI (base unit PBU560) hardware version must be 3. GMX (GMZ544) software version must be 3. interface parameters in the Tellabs 8100 manager database should be updated from hardware to remove a consistency check failure. Enhancements and Fixed bugs • • • • • Production test phase is enhanced by removing unnecessary faults in test setup.1. (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. SCU (SCZ280) software version must be 8. interrupt handler hang-up causes unit reset in V5.4 or higher.0 of CCS-UNI is replaced with this version.6 or higher. V5. Bugs • No known bugs.2 This version is only available for CCS-UNI. 10004_22 © 2008 Tellabs. SCU-H (SCZ545) software version must be 1.2 is available in Release 12A Service Pack 2 or higher.1.0 or higher. 3.4 Version 5. MartisDXX Manager support for V5.2 use. SXU-V (ESZ8003) software version must be 1. SCP (SCZ281) software version must be 3.1.1 or higher (SCP unit is optional). Tellabs® 8100 Managed Access System Unit Software Version Dependencies 51 . SXU-A/B (SXZ282) software version can be any version.2 TV5 support. XCG (SMZ538) software version must be 2. SXU-V (SXZ630) software version must be 1.CCS-UNI and CCO-UNI Units: CCZ539 Unit Software Restrictions • • PCM coding and decoding are only according to A-law.

µ-law is not supported. Restrictions • • PCM coding and decoding are only according to A-law. SXU-A/B (SXZ282) software version can be any version.0 of CCS-UNI is replaced with this version. MartisDXX Manager support for V5.6 or higher.0 or higher.1 or higher (SCP unit is optional). XCG (SMZ538) software version must be 2. GMX (GMZ544) software version must be 3. Dependencies • • • • • • • • • CCS-UNI (base unit PBU560) hardware version must be 3.5 Version 5. interface parameters in the Tellabs 8100 manager database should be updated from hardware to remove a consistency check failure.1.4 or higher. . SCP (SCZ281) software version must be 3. interface parameters in the Tellabs 8100 manager database should be updated from hardware to remove a consistency check failure. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 52 10004_22 © 2008 Tellabs.1 This version is a test version only for CCS-UNI. If v1. µ-law is not supported. SCU-H (SCZ545) software version must be 1.17 or higher.2 is available in Release 12 Service Pack 2 or higher. SXU-V (SXZ630) software version must be 1. Bugs • No known bugs. 3.0 of CCS-UNI is replaced with this version. Bugs • No known bugs.CCS-UNI and CCO-UNI Units: CCZ539 Unit Software Restrictions • • PCM coding and decoding are only according to A-law. Enhancements and Fixed Bugs • The unit hanging problem in interface blocking and unblocking is solved. In case v1. SCU (SCZ280) software version must be 8.1.

17 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 53 .2 use. SCP (SCZ281) software version must be 3.CCS-UNI and CCO-UNI Units: CCZ539 Unit Software 3.6 or higher.4 or higher.0 of CCS-UNI is replaced with this version. In case v1. Enhancements and Fixed Bugs • • • • V5. Bugs • The unit may hang if flash memory copying starts while blocking or unblocking an interface. interrupt handler hang-up causes unit reset in V5. XCG (SMZ538) software version must be 2. (CRF ID 4004239) On CCS-UNI the port unlocking is possible even though a port contains circuits/crossconnections with the Service Computer. SCU (SCZ280) software version must be 8. Restrictions • • PCM coding and decoding are only according to A-law. SXU-V (SXZ630) software version must be 1.0 This is an internal test version based on version 2. 10004_22 © 2008 Tellabs. SXU-A/B (SXZ282) software version can be any version. interface parameters in the Tellabs 8100 manager database should be updated from hardware to remove a consistency check failure.1 or higher (SCP unit is optional).0 only for CCS-UNI.0 or higher. (CRF ID 4004506) A change of the unit version in a subrack results in an interface parameter corruption. GMX (GMZ544) software version must be 3. SCU-H (SCZ545) software version must be 1. MartisDXX Manager support for this unit/interface card is available in Release 10.1 or higher.6 Version 5. (CRF ID 4003704) Dependencies • • • • • • • • • CCS-UNI (base unit PBU560) hardware version must be 3. (CRF ID 4004530) There is an IN USE group operation failure on CCS-UNI while doing a large amount of changes. µ-law is not supported.1A Service Pack 7 or Release 11 Service Pack 1 or higher.1.2 TV5 support.

0.0 or higher. CCO555 and CCS554 hardware versions must be at least 2. SXU-V (SXZ630) software version must be 1.17 or higher. Restrictions • PCM coding and decoding are only according to A-law.4 or higher.0 This version is only available for CCS-UNI. SCP (SCZ281) software version must be 3.6 or higher. XCG (SMZ538) software version must be 2.1. µ-law is not supported.0.1 or higher (SCP unit is optional). SCU-H (SCZ545) software version must be 1. SXU-V (SXZ630) software version must be 1.1A Service Pack 7 or Release 11 Service Pack 1 or higher.7 Version 4.8 Version 2. XCG (SMZ538) software version must be 2. 3. Dependencies • • • • • • • • CCS-UNI and CCO-UNI (base unit PBU560) hardware version must be 2. Dependencies • • • • • • • • • CCS-UNI (base unit PBU560) hardware version must be 3. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 54 10004_22 © 2008 Tellabs.1 or higher. . MartisDXX Manager support for this unit/interface card is available in Release 10.4 or higher. SCP (SCZ281) software version must be 3. SCU (SCZ280) software version must be 8. GMX (GMZ544) software version must be 3. SXU-A/B (SXZ282) software version can be any version.0 cannot be directly replaced with this version.0 or higher.1 or higher. SCU (SCZ280) software version must be 8.6 or higher.0.0 This version is available for CCS-UNI and CCO-UNI hardware product version 2. Bugs • Version 1.1 or higher (SCP unit is optional). SCU-H (SCZ545) software version must be 1.CCS-UNI and CCO-UNI Units: CCZ539 Unit Software 3. SXU-A/B (SXZ282) software version can be any version.

0.4 or higher.0 or higher.0 This version is available for CCS-UNI and CCO-UNI hardware product version 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 55 .0 does not support Mercury signalling.0. 10004_22 © 2008 Tellabs. Version 1. Restrictions • • PCM coding and decoding are only according to A-law. Bugs • • The application can be disabled. SCU (SCZ280) software version must be 8.1 or higher (SCP unit is optional).1A or higher. Restrictions • • PCM coding and decoding are only according to A-law. CCZ359 2. µ-law is not supported.9 Version 1. SCP (SCZ281) software version must be 3. The interface can be unlocked even if it is cross-connected. 3.6 or higher. MartisDXX Manager support for this unit/interface card is available in Release 10. SXU-V (SXZ630) software version must be 1. Other countries will be supported in MartisDXX Manager Release 11 Service Pack 2.1 or higher. SCU-H (SCZ545) software version must be 1.0 is designed mainly to adopt South-African POTS interface specifications into the units.0 cannot be directly replaced with this version. Dependencies • • • • • • • • CCS-UNI and CCO-UNI (base unit PBU560) hardware version must be 1.1A Service Pack 1 or Release 11 Service pack 1 or higher. SXU-A/B (SXZ282) software version can be any version. Bugs • • The application can be disabled. CCZ539 v1. µ-law is not supported. XCG (SMZ538) software version must be 2.CCS-UNI and CCO-UNI Units: CCZ539 Unit Software • MartisDXX Manager support for this unit/interface card is available in Release 10.

2.). The GCI (General Command Interpreter) will now accept the special void messages sent during those operations. all the links will be lost. (CR ID 200031024) Dependencies • • • CCU (base unit SCU210) hardware version must be 4.. Bugs • No known bugs. 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.7 Enhancements • The problem preventing CCU inventory operations has been fixed. MartisDXX Manager support for CCU is available in release 10. CXU-M (SXZ288) software version can be any version.1 Version 2.. The version 2.y of SCZ286 (where y=0. If this problem occurs.CCU Unit: SCZ286 Unit Software 4 CCU Unit: SCZ286 Unit Software The software SCZ286 is used on CCU units.0 or higher to support the PFU-A and PFU-B generated signal to detect the power off situation. this generates the loss of service for all the node.7 can be downloaded to CCU units having the version 2. . 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 56 10004_22 © 2008 Tellabs. 4.1A or higher. 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 effect on traffic is essentially smaller.CCU Unit: SCZ286 Unit Software 4.1A or higher.6 Enhancements • • • The switch-over has been optimized and it happens faster. (CR ID 200031024) 10004_22 © 2008 Tellabs.0 or higher to support the PFU-A and PFU-B generated signal to detect the power off situation. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 57 . all the links will be lost. 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. (CR ID 200013068) The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) have check for internal structure of envelope messages. If this problem occurs. (CR ID 200013759) Dependencies • • • CCU (base unit SCU210) hardware version must be 4.6 will otherwise operate normally.2 Version 2. Only a successful unit poll with a long delay will activate this delta fault. MartisDXX Manager support for CCU is available in release 10. (CR ID 200013489) Two fault conditions have 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. In the case of active forced mode when switch over can not happen this fault was activated erroneously. 2) The "Switch-over has happened because of long delay" fault operated erroneously. An installed (upgraded) CCU with ESW version 2. This bug in now fixed. 1) A bug in testing for fault "Delay has increased" has been fixed. CXU-M (SXZ288) software version can be any version. this generates the loss of service for all the node. Bugs • The inventory add and delete operations for CCU unit are impossible.

all the links will be lost. Restrictions • • • The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) do not check the internal structure of envelope messages. In the case of missing CXU-M or software download this delta fault repeats itself continuously and fills the CCU fault history.5 Enhancements • The “CXU-M in slot 31 is PRIMARY” parameter and “CXU-M Secondary Active” fault for CCU in SCZ286 have been added.0 will support this (ON/OFF) signal. . In the case of active forced mode when switch over can not happen this fault is activated erroneously.1A or higher. • • Dependencies • • • CCU (base unit SCU210) hardware version must be 4. If this problem occurs. The new SCU hardware version 4. MartisDXX Manager support for CCU is available in release 10. The switch-over has not been optimized.3 Version 2. 1) There is a bug in testing for fault "Delay has increased". In the particular case that power of the main master shelf fails (where the control circuit card resides) of the Tellabs 8170 cluster node. 2) The "Switch-over has happened because of long delay" fault operates erroneously.0 or higher to support the PFU-A and PFU-B generated signal to detect the power off situation. This alarm shows whether the Tellabs 8170 cluster node is using the upper or lower shelf of the node. PFU-A and PFU-B provide a signal for detecting the power off situation. 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. Bugs • Two faults operate incorrectly.CCU Unit: SCZ286 Unit Software 4. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 58 10004_22 © 2008 Tellabs. this generates the loss of service for all the node. CXU-M (SXZ288) software version can be any version.

If this problem occurs. This version should not be used once the official version 2.2 Restrictions • • • • • • The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) do not check the internal structure of envelope messages. Bugs • • Activity state error in Tellabs 8170 cluster node CXU-M units. • 10004_22 © 2008 Tellabs. Does not support the faults “Delay increased” and “Switchover has happened because of long delay”. Restrictions • • • • The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) do not check the internal structure of envelope messages. all the links will be lost.2 with a bug fix for the CRF ID 4002472. this generates the loss of service for all the node. essential node operations may be disabled. Does not support the faults “Delay increased” and “Switchover has happened because of long delay”.5 Version 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 59 . The switch-over has not been optimized. If this problem occurs. all the links will be lost. Maintenance event alarm (MEI) for active CXU-M switchover is not supported.5 is available.4 This is an unofficial version based on SCZ286 version 2. In the particular case that power of the main master shelf fails (where the control circuit card resides) of the Tellabs 8170 cluster node. Bugs • No known bugs.4 Version 2. PFU-A/PFU-B power off alarm in SCU/CCU is not supported. If the node ends up in this state. 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. In the particular case that power of the main master shelf fails (where the control circuit card resides) of the Tellabs 8170 cluster node. The switch-over has not been optimized.CCU Unit: SCZ286 Unit Software 4. 4. this generates the loss of service for all the node. Longer timeout when polling CXU-M.

all the links will be lost. The clock direction options for the synchronous SCC interface are not supported. 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. If the node ends up in this state. The optional security management for the SC interface is not supported. Bugs • • Activity state error in Tellabs 8170 cluster node CXU-M units. The switch-over has not been optimized. Does not support the faults “Delay increased” and “Switchover has happened because of long delay”.CCU Unit: SCZ286 Unit Software • The timeout CCU needs when polling CXU-M has been changed from 2 seconds to 4 seconds. In the particular case that power of the main master shelf fails (where the control circuit card resides) of the Tellabs 8170 cluster node. essential node operations may be disabled. Longer timeout when polling CXU-M. . PFU-A/PFU-B power off alarm in SCU/CCU is not supported. (CRF ID 4002472) • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 60 10004_22 © 2008 Tellabs. Maintenance event alarm (MEI) for active CXU-M switchover is not supported. this generates the loss of service for all the node.6 Version 2. 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 this problem occurs. 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.1 Restrictions • • • • • • • • The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) do not check the internal structure of envelope messages.

The optional security management for the SC interface 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. The switch-over has not been optimized. If this problem occurs. Activity state error in Tellabs 8170 cluster node CXU-M units. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 61 . The clock direction options for the synchronous SCC interface are not supported. Does not support the faults “Delay increased” and “Switchover has happened because of long delay”. (CRF ID 4002472) • • 10004_22 © 2008 Tellabs. Longer timeout when polling CXU-M. Maintenance event alarm (MEI) for active CXU-M switchover is not supported. The timeout CCU needs when polling CXU-M has been changed from 2 seconds to 4 seconds. essential node operations may be disabled. If the node ends up in this state. this generates the loss of service for all the node. all the links will be lost.CCU Unit: SCZ286 Unit Software 4. Bugs • • • The unit cannot copy the settings for the SCL415 options from the backup settings to its own use when the unit is replaced. PFU-A/PFU-B power off alarm in SCU/CCU is not supported. 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. 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.7 Version 2.0 Restrictions • • • • • • • • The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) do not check the internal structure of envelope messages.

The network layer protocol software cannot handle all illegal routing elements. The clock direction options for the synchronous SCC interface are not supported.CCU Unit: SCZ286 Unit Software 4. 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. The switch-over has not been optimized. The asynchronous protocol software does not work correctly with heavy full-duplex traffic. this generates the loss of service for all the node. The timeout CCU needs when polling CXU-M has been changed from 2 seconds to 4 seconds. . (CRF ID 4002472) • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 62 10004_22 © 2008 Tellabs. Longer timeout when polling CXU-M. Maintenance event alarm (MEI) for active CXU-M switchover is not supported. The LLC3 protocol software cannot handle one exceptional case associated with negative acknowledgement. The optional security management for the SC interface is not supported. Does not support the faults “Delay increased” and “Switchover has happened because of long delay”. 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. all the links will be lost. PFU-A/PFU-B power off alarm in SCU/CCU 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. Bugs • • • The unit cannot copy the settings for the SCL415 options from the backup settings to its own use when the unit is replaced. essential node operations may be disabled. If the node ends up in this state. These two communication problems are not likely to happen but they can cause a deadlock in the communication system CCU.8 Version 1. If this problem occurs. Activity state error in Tellabs 8170 cluster node CXU-M units.5 Restrictions • • • • • • • • The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) do not check the internal structure of envelope messages.

The clock direction options for the synchronous SCC interface are 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. These two communication problems are not likely to happen but they can cause a deadlock in the communication system CCU. essential node operations may be disabled. If the node ends up in this state. PFU-A/PFU-B power off alarm in SCU/CCU is not supported. The asynchronous protocol software does not work correctly with heavy full-duplex traffic. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 63 . Maintenance event alarm (MEI) for active CXU-M switchover is not supported. this generates the loss of service for all the node. 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. Does not support the alarm interface module SCL415. Does not support the faults “Delay increased” and “Switchover has happened because of long delay”. The switch-over has not been optimized. If this problem occurs. all the links will be lost. The network layer protocol software cannot handle all illegal routing elements. 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. The optional security management for the SC interface is not supported. Activity state error in Tellabs 8170 cluster node CXU-M units. Longer timeout when polling CXU-M. (CRF ID 4002472) • • • • • 10004_22 © 2008 Tellabs. Bugs • • • The unit cannot copy the settings for the SCL415 options from the backup settings to its own use when the unit is replaced.4 Restrictions • • • • • • • • • The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) do not check the internal structure of envelope messages.9 Version 1. The timeout CCU needs when polling CXU-M has been changed from 2 seconds to 4 seconds. The LLC3 protocol software cannot handle one exceptional case associated with negative acknowledgement.CCU Unit: SCZ286 Unit Software 4.

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. MartisDXX Manager support for priority bumping functionality is available in Release 9.6 Enhancements and Fixed Bugs • • • SCU or SCU-H reset in slave subrack does not any more cause cluster node switch over.4. 5. 5. Bugs • No known bugs.1 Version 10.0 or higher. SXU-C (SXZ289) software version must be 2.2 Version 10. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 64 10004_22 © 2008 Tellabs.0B Service Pack 12 or higher. (CR ID 300067522) The handling of flash list record status has been corrected. Restrictions • No restrictions.10 or higher. (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 300091551) Dependencies • • • • CXU-M (base unit SXU212) hardware version must be 5. .5 This is an unofficial version based on SXZ288 version 10. CCU (SCZ286) software version can be any version.

Phase Locked Loop Alarm and External Clock Warning has been fixed. Bugs • SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. MartisDXX Manager support for priority bumping functionality is available in Release 9.4 Version 10. (CR ID 200036673) • 10004_22 © 2008 Tellabs. CCU (SCZ286) software version can be any version. (CR ID 300062665) Dependencies • • • • CXU-M (base unit SXU212) hardware version must be 5. (CR ID 300023465) Fallback List Warning fault has been restored.4 Enhancements and Fixed Bugs • • Wrong fault mapping concerning the faults Loss of External Clock. (CR ID 200031025) Master clock RAI support has been fixed. The problem is more probable with SCU-H than with SCU as it has a longer startup time.3 Enhancements and Fixed Bugs • The problem preventing CXU-M inventory operations has been fixed. Restrictions • No restrictions. (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. This Fault can be enabled or disabled with master clock quality level enable.0 or higher. The GCI (General Command Interpreter) will now accept the special void messages sent during those operations.3 Version 10. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. (CR ID 300091551) • • 5.0B Service Pack 12 or higher. (CR ID 300107078) Fallback list warning fault enable polarity is wrong. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 65 .CXU-M Unit: SXZ288 Unit Software 5. The time difference in the slave status polling between the primary and secondary sides may be several seconds.10 or higher. SXU-C (SXZ289) software version must be 2.

Bugs • SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. • • 5.0 or higher.0B Service Pack 12 or higher. (CR ID 200013179) The cross-connect memory background verification (MXA monitoring) is now active as default. (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. The time difference in the slave status polling between the primary and secondary sides may be several seconds. (CR ID 200013488) • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 66 10004_22 © 2008 Tellabs. . Previously the verification was off as default. CCU (SCZ286) software version can be any version. (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. The problem is more probable with SCU-H than with SCU as it has a longer startup time. (CR ID 200013327) The cross-connect memory background verification (MXA monitoring) is now capable of handling also SCP ports. MartisDXX Manager support for priority bumping functionality is available in Release 9. After this modification the neighbour node can apply the defined QL of the internal clock correctly.2 Enhancements and Fixed Bugs • The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) message envelope structure is verified before the message is executed. SXU-C (SXZ289) software version must be 2. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. (CR ID 200012002) When CXU-M sends the state of the used clock source to the interface units. Restrictions • No restrictions.CXU-M Unit: SXZ288 Unit Software Dependencies • • • • CXU-M (base unit SXU212) hardware version must be 5. Phase Locked Loop Alarm and External Clock Warning (CR ID 300023465). (CR ID 200012825) The detection time of missing SXU-C unit has been reduced by code optimization. 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. This reduces the probability of problems followed by possibly corrupted message. (CR ID 300091551) Wrong fault activation bug concerning the faults Loss of External Clock.10 or higher.5 Version 10. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover.

0 or higher.0B Service Pack 12 or higher. Phase Locked Loop Alarm and External Clock Warning (CR ID 300023465). This problem only concerns versions 10. The same change has already earlier been done to Tellabs 8160 A111/GMX. 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. Restrictions • No restrictions. Bugs • SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover.10 or higher.0B Service Pack 12 or higher. (CR ID 300091551) Wrong fault activation bug concerning the faults Loss of External Clock. SXU-C (SXZ289) software version must be 2.2 and 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 67 . (CR ID 200005090) • Dependencies • • • • CXU-M (base unit SXU212) hardware version must be 5.0 or higher.6 Version 10. XCG. CCU (SCZ286) software version can be any version. MartisDXX Manager support for priority bumping functionality is available in Release 9.CXU-M Unit: SXZ288 Unit Software • "Fallback list warning" faults are not anymore generated.10 or higher. 10004_22 © 2008 Tellabs. These have been replaced with "Faulty clock source of choice n" faults. The time difference in the slave status polling between the primary and secondary sides may be several seconds. CXU-M unit can not be added in or removed from the node inventory. This problem does not have any effect on the CXU-M units in operative state. (CR ID 200031025) Master clock RAI does not operate.1 Dependencies • • • • CXU-M (base unit SXU212) hardware version must be 5. The GCI (General Command Interpreter) message verification does not accept the special void messages sent by Tellabs 8100 network manager during those operations. (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 200005248) Memory overflow problem in master clock software module has been fixed. (CR ID 200036673) • • • • 5. SXU-C (SXZ289) software version must be 2. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. MartisDXX Manager support for priority bumping functionality is available in Release 9. SXU-A and SXU-B.13. CCU (SCZ286) software version can be any version.

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. The Fall Back List Warning fault exists in the faults list. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. • • • • • 5. Memory overflow problem in master clock software module. 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. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. (CR ID 300091551) When CXU-M sends the state of the used clock source to the interface units. (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 GCI (General Command Interpreter) and SCI (Slow Command Interpreter) are not able to detect possible internal errors in message envelope structure. Restrictions • • • • The detection time of missing SXU-C unit has not been optimized. (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.0. Note that the verification process is not executing if it is not explicitly activated.0 Dependencies • • CXU-M (base unit SXU212) hardware version must be 5. 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.7 Version 10.CXU-M Unit: SXZ288 Unit Software 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 problem is more probable with SCU-H than with SCU as it has a longer startup time. The time difference in the slave status polling between the primary and secondary sides may be several seconds. Does not support background verification of CXU-A cross-connect memory. MartisDXX Manager support for priority bumping functionality is available in Release 9. Bugs • SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover.0B Service Pack 12 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 68 10004_22 © 2008 Tellabs.

Does not support indication of faulty intersubrack cable installation in fault history. The connections created for those ports will become inoperable after monitoring has been activated with auto fix option. After a while the GMM state is properly updated and it is selected in the SYB bus. When CXU-M receives 1001th X-Group ID activation command after unit initialization. Erroneous warnings can be seen as the test method is too sensitive. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The time difference in the slave status polling between the primary and secondary sides may be several seconds. MXA monitoring (CXU-A memory background check) does not operate properly if there are SCP control channel ports. The problem is more probable with SCU-H than with SCU as it has a longer startup time. 1) If the fallback list contains three or more clocks from the same subrack and the current MCL becomes faulty. There are two GMM-related problems in the node master clock selection. X-Group IDs are used in swap circuit and time controlled circuit applications. This happens because the used port type is not properly handled. (CR ID 300091551) When CXU-M sends the state of the used clock source to the interface units. (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. This may lead to one switch-over when both CXU-M units are initializing at the same time. After a while the node starts to use the valid GMM as MCL. The primary reason for the slave resets is the RAM list monitoring. In stable state invalid activation is not possible. the next choices (GMM) status is temporarily marked in fail state and the fourth choice is selected instead for the SYB. It is however very unlikely that the number of activations would reach a very large number.CXU-M Unit: SXZ288 Unit Software • • Does not support the enhanced Asic Latch Warning fault monitoring. Bugs • SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 69 . It takes about 4 seconds too long before the node starts using an external clock after holdover state. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. the node may temporarily start using the internal clock. 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. • • • • • • • • 10004_22 © 2008 Tellabs. If the master is not able to update its own list properly while the slaves are. (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 result is a checksum mismatch. 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. Both SXU-C and CXU-M must support this feature before the fault can be detected. 2) If the node clock fails and the next choice is GMM. During CXU-M initialization the fault Clock Failure Switch Over may unnecessarily be activated for a short time period.

15.16 This is an unofficial version based on SXZ288 version 2. Bugs • No known bugs. CCU (SCZ286) software version can be any version.0. (CR ID 300107078) The Fallback List Warning fault can be enabled by setting the use master clock quality levels parameter to disabled state. MartisDXX Manager support for priority bumping functionality is available in Release 9.9 Version 2.8 Version 2. (CR ID 300062665) Tellabs® 8100 Managed Access System Unit Software Version Dependencies 70 10004_22 © 2008 Tellabs. (CR ID 300091551) Dependencies • • • • CXU-M (base unit SXU212) hardware version must be lower than 5.10 or higher. 5. 5. (CR ID 300067522) The handling of flash list record status has been corrected. (CR ID 300023465) Fallback List Warning fault has been restored. Phase Locked Loop Alarm and External Clock Warning has been fixed.17 Enhancements and Fixed Bugs • • • SCU or SCU-H reset in slave subrack does not any more cause cluster node switch over. This Fault can be enabled or disabled with master clock quality level enable.10 Version 2. Restrictions • No restrictions.CXU-M Unit: SXZ288 Unit Software 5.15 Enhancements and Fixed Bugs • • Wrong fault mapping concerning the faults Loss of External Clock. SXU-C (SXZ289) software version must be 2. .0B Service Pack 12 or higher.

The GCI (General Command Interpreter) will now accept the special void messages sent during those operations.0B Service Pack 12 or higher. MartisDXX Manager support for priority bumping functionality is available in Release 9. (CR ID 200036673) Downloading software in the CXU-M unit in the lower shelf is possible. (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.0B Service Pack 12 or higher.11 Version 2. CCU (SCZ286) software version can be any version.0. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. SXU-C (SXZ289) software version must be 2. 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. (CR ID 200031025) Master clock RAI support has been fixed. (CR ID 200036481) • • Dependencies • • • • CXU-M (base unit SXU212) hardware version must be lower than 5. Restrictions • No restrictions. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 71 . SXU-C (SXZ289) software version must be 2. Restrictions • No restrictions. Bugs • SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. CCU (SCZ286) software version can be any version. MartisDXX Manager support for priority bumping functionality is available in Release 9.10 or higher.0. 10004_22 © 2008 Tellabs. The problem is more probable with SCU-H than with SCU as it has a longer startup time.10 or higher.CXU-M Unit: SXZ288 Unit Software Dependencies • • • • CXU-M (base unit SXU212) hardware version must be lower than 5. (CR ID 300091551) • • 5. (CR ID 300107078) Fallback list warning fault enable polarity is wrong.14 Enhancements and Fixed Bugs • The problem preventing CXU-M inventory operations has been fixed.

(CR ID 300091551) Wrong fault activation bug concerning the faults Loss of External Clock. 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. (CR ID 200013179) The cross-connect memory background verification (MXA monitoring) is now active as default. These have been replaced with "Faulty clock source of choice n" faults. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The same change has already earlier been done to Tellabs 8160 A111/GMX. The time difference in the slave status polling between the primary and secondary sides may be several seconds.13 Enhancements and Fixed Bugs • The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) message envelope structure is verified before the message is executed. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. (CR ID 200005248) The problem related with the 1001th X-Group ID activation command in CXU-M has been fixed. (CR ID 200013329) The cross-connect memory background verification (MXA monitoring) is now capable of handling also SCP ports. Previously the verification was off as default. After this modification the neighbour node can apply the defined QL of the internal clock correctly. SXU-A and SXU-B. (CR ID 200012002) When CXU-M sends the state of the used clock source to the interface units. • • 5. This reduces the probability of problems followed by possibly corrupted message. Phase Locked Loop Alarm and External Clock Warning (CR ID 300023465). (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 200013488) "Fallback list warning" faults are not anymore generated. (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 200004868) Memory overflow problem in master clock software module has been fixed. XCG.12 Version 2. (CR ID 200012825) The detection time of missing SXU-C unit has been reduced by code optimization. (CR ID 200005090) • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 72 10004_22 © 2008 Tellabs. The problem is more probable with SCU-H than with SCU as it has a longer startup time.CXU-M Unit: SXZ288 Unit Software Bugs • SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover.

2 and 2. MartisDXX Manager support for priority bumping functionality is available in Release 9. CCU (SCZ286) software version can be any version. Restrictions • No restrictions. The GCI (General Command Interpreter) message verification does not accept the special void messages sent by Tellabs 8100 network manager during those operations.13 Version 2.10 or higher. The time difference in the slave status polling between the primary and secondary sides may be several seconds. CCU (SCZ286) software version can be any version.0.0B Service Pack 12 or higher. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. (CR ID 2000) Downloading software in the CXU-M unit in the lower shelf may be unsuccesfull. (CR ID 200036481) • • • • • 5. This problem only concerns versions 10.CXU-M Unit: SXZ288 Unit Software Dependencies • • • • CXU-M (base unit SXU212) hardware version must be lower than 5.13. MartisDXX Manager support for priority bumping functionality is available in Release 9.12 Dependencies • • • • CXU-M (base unit SXU212) hardware version must be lower than 5. This problem does not have any effect on the CXU-M units in operative state. Bugs • SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover.0. Phase Locked Loop Alarm and External Clock Warning (CR ID 300023465). SXU-C (SXZ289) software version must be 2. The problem is more probable with SCU-H than with SCU as it has a longer startup time.10 or higher. CXU-M unit can not be added in or removed from the node inventory.0B Service Pack 12 or higher. SXU-C (SXZ289) software version must be 2. 10004_22 © 2008 Tellabs. (CR ID 300091551) Wrong fault activation bug concerning the faults Loss of External Clock. (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 200031025) Master clock RAI does not operate. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 73 . 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. 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. X-Group IDs are used in swap circuit and time controlled circuit applications. This may lead to one switch-over when both CXU-M units are initializing at the same time. The cross-connect memory background verification (MXA monitoring) is not active as default. (CR ID 200036481) When CXU-M sends the state of the used clock source to the interface units. • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 74 10004_22 © 2008 Tellabs.CXU-M Unit: SXZ288 Unit Software Restrictions • • • • • • The detection time of missing SXU-C unit has not been optimized. (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 problem is more probable with SCU-H than with SCU as it has a longer startup time. When CXU-M receives 1001th X-Group ID activation command after unit initialization. (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. If the master is not able to update its own list properly while the slaves are. The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) are not able to detect possible internal errors in message envelope structure. Memory overflow problem in master clock software module. . The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. Bugs • SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. 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. 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. During CXU-M initialization the fault Clock Failure Switch Over may unnecessarily be activated for a short time period. In stable state invalid activation is not possible. The Fall Back List Warning fault exists in the faults list. It is however very unlikely that the number of activations would reach a very large number. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. Both SXU-C and CXU-M must support this feature before the fault can be detected. Note that the verification process is not executing if it is not explicitly activated. The primary reason for the slave resets is the RAM list monitoring. (CR ID 300091551) Downloading software in the CXU-M unit in the lower shelf may be unsuccesfull. the result is a checksum mismatch. Does not support indication of faulty intersubrack cable installation in fault history. Holdover mode of the master clock is not supported.

14 Version 2.CXU-M Unit: SXZ288 Unit Software 5. Bugs • SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. Erroneous warnings can be seen as the test method is too sensitive. (CR ID 300091551) When CXU-M sends the state of the used clock source to the interface units. MartisDXX Manager support for priority bumping functionality is available in Release 9. (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. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The time difference in the slave status polling between the primary and secondary sides may be several seconds. • • • • 10004_22 © 2008 Tellabs. This may lead to one switch-over when both CXU-M units are initializing at the same time. Restrictions • • • • • • • • The detection time of missing SXU-C unit has not been optimized. the next choices (GMM) status is temporarily marked in fail state and the fourth choice is selected instead for the SYB. 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.10 Dependencies • • CXU-M (base unit SXU212) hardware version must be lower than 5. Does not support the enhanced Asic Latch Warning fault monitoring. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 75 . Does not support background verification of CXU-A cross-connect memory. During CXU-M initialization the fault Clock Failure Switch Over may unnecessarily be activated for a short time period.0B Service Pack 12 or higher. Holdover mode of the master clock is not supported. Does not support indication of faulty intersubrack cable installation in fault history. The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) are not able to detect possible internal errors in message envelope structure. In stable state invalid activation is not possible. The problem is more probable with SCU-H than with SCU as it has a longer startup time. 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).0. After a while the GMM state is properly updated and it is selected in the SYB bus. The Fall Back List Warning fault exists in the faults list. 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. Both SXU-C and CXU-M must support this feature before the fault can be detected.

Does not indicate the used fallback list entry in the fault history.0. Does not support the enhanced Asic Latch Warning fault monitoring. It is however very unlikely that the number of activations would reach a very large number.10 is available. This version should not be used once the official version 2. If the master is not able to update its own list properly while the slaves are. Does not support background verification of CXU-A cross-connect memory. the result is a checksum mismatch.7 Dependencies • CXU-M base unit SXU212 version must be lower than 5. 5. 5. This version should not be used once the official version 2. The primary reason for the slave resets is the RAM list monitoring. • 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. . Tellabs® 8100 Managed Access System Unit Software Version Dependencies 76 10004_22 © 2008 Tellabs. Erroneous warnings can be seen as the test method is too sensitive.10 is available.8 This is an unofficial version based on SXZ288 version 2. The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) are not able to detect possible internal errors in message envelope structure. the node may temporarily start using the internal clock.16 Version 2.15 Version 2.17 Version 2. Restrictions • • • • • • The detection time of missing SXU-C unit has not been optimized. This version does not include a bug fix for the master clock ASIC configuration problem. 5.10. After a while the node starts to use the valid GMM as MCL. The Fall Back List Warning fault exists in the faults list. X-Group IDs are used in swap circuit and time controlled circuit applications.7 with a bug fix only for the swap circuit unidirectional connection problem. ASIC is temporarily configured incorrectly when the new clock interface frequency differs from the previous frequency and the change happens suddenly (interrupt).9 This is an unofficial version almost equal to SXZ288 version 2.CXU-M Unit: SXZ288 Unit Software 2) If the node clock fails and the next choice is GMM.

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). There may exist an unnecessary Unstable SSM fault when master clock quality levels are disabled. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 77 . If a quality source mode other than poll is used.CXU-M Unit: SXZ288 Unit Software • 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). the quality level information is not properly transmitted to neighbour nodes. the frequency dependent ASIC • • • • • • • • • • • • • 10004_22 © 2008 Tellabs. 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. Both SXU-C and CXU-M must support this feature before the fault can be detected. 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. 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 resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. The time difference in the slave status polling between the primary and secondary sides may be several seconds. A unit does not disappear from the list of available clock sources when the unit is removed from inventory. (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. 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. The problem is more probable with SCU-H than with SCU as it has a longer startup time. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack. Does not support indication of faulty intersubrack cable installation in fault history. 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). Holdover mode of the master clock is not supported. The quality level 6 (used for internal clock) is translated to SDH SSM code SEC though it should be DNU. • • Bugs • SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. When the master clock starts using an interface with a different frequency than the previous frequency and the change happens suddenly (interrupt). A problem may occur if a new GMU unit is added to a node where a GMU unit has already been in inventory. (CR ID 300091551) When CXU-M sends the state of the used clock source to the interface units.

• • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 78 10004_22 © 2008 Tellabs. The GCI (General Command Interpreter) and SCI (Slow Command Interpreter) are not able to detect possible internal errors in message envelope structure. the result is a checksum mismatch. The Fall Back List Warning fault exists in the faults list. 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. When CXU-M receives 1001th X-Group ID activation command after unit initialization.6 Dependencies • CXU-M base unit SXU212 version must be lower than 5. 2) If the node clock fails and the next choice is GMM. 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. X-Group IDs are used in swap circuit and time controlled circuit applications. Does not support indication of faulty intersubrack cable installation in fault history. Does not support background verification of CXU-A cross-connect memory. The primary reason for the slave resets is the RAM list monitoring. Erroneous warnings can be seen as the test method is too sensitive. Does not support the enhanced Asic Latch Warning fault monitoring. • There are two GMM-related problems in the node master clock selection. No support for GMU.CXU-M Unit: SXZ288 Unit Software parameters may temporarily be configured incorrectly.0. the node may temporarily start using the internal clock. . Holdover mode of the master clock is not supported. As a result synchronization to the new clock source is a little slower but the final state is however correct. 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). Restrictions • • • • • • • The detection time of missing SXU-C unit has not been optimized. After a while the node starts to use the valid GMM as MCL. If the master is not able to update its own list properly while the slaves are. Both SXU-C and CXU-M must support this feature before the fault can be detected. Does not indicate the used fallback list entry in the fault history.18 Version 2. • 5. It is however very unlikely that the number of activations would reach a very large number. After a while the GMM state is properly updated and it is selected in the SYB bus.

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). the result is a checksum mismatch. If an external clock is the current clock source and the external clock input is broken. The resulting uncertainty in the status information in the CCU control unit may cause an invalid switchover. (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. 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. Supports only 10 simultaneous cross-connect object commands in a single GCI message. X-Group IDs are used in swap circuit and time controlled circuit applications. This may result from the unsynchronized slave SXU-C status polls carried out by the CXU-M units in the master subrack.CXU-M Unit: SXZ288 Unit Software Bugs • SCU/SCU-H reset may cause a Tellabs 8170 cluster node switchover. 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. (CR ID 300091551) When CXU-M sends the state of the used clock source to the interface units. 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. When the master clock starts using an interface with a different frequency than the previous frequency and the change happens suddenly (interrupt). It is however very unlikely that the number of activations would reach a very large number. The primary reason for the slave resets is the RAM list monitoring. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 79 . As a result synchronization to the new clock source is a little slower but the final state is however correct. it is possible that the next clock is not correctly selected from the fallback list. An unnecessary Fallback List warning fault may appear if there are still usable clock sources. the next choices (GMM) status is temporarily marked in fail state and the fourth choice is selected instead for the SYB. A unit does not disappear from the list of available clock sources when the unit is removed from inventory. the frequency dependent ASIC parameters may temporarily be configured incorrectly. After a while the GMM state is properly updated and it is selected in the SYB bus. the node may temporarily start using the internal clock. If the master is not able to update its own list properly while the slaves are. 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. 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). 2) If the node clock fails and the next choice is GMM. • • • • • • • • • • • • 10004_22 © 2008 Tellabs. The problem is more probable with SCU-H than with SCU as it has a longer startup time. 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 time difference in the slave status polling between the primary and secondary sides may be several seconds.

CXU-M Unit: SXZ288 Unit Software

5.19 Version 2.5
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. 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.

• •

• •

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
80

10004_22 © 2008 Tellabs.

CXU-M Unit: SXZ288 Unit Software

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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
81

CXU-M Unit: SXZ288 Unit Software

5.20 Version 2.4
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. 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.

• •

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
82

10004_22 © 2008 Tellabs.

CXU-M Unit: SXZ288 Unit Software

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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
83

CXU-M Unit: SXZ288 Unit Software

5.21 Version 2.3
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. 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.

• •

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
84

10004_22 © 2008 Tellabs.

CXU-M Unit: SXZ288 Unit Software

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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
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
Enhancements and Fixed Bugs

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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
88

10004_22 © 2008 Tellabs.

SXU-V (SXZ630) software can be any version. ESU BPDU (STP) transparency configuration needs to be configured to all members of the link aggregation group. if GMU450 hardware version is 2.0 or higher to support sync pulse. ESU unit with SCO: The Line Loop (LiL) is not supported in case of SCO interfaces connected to any NTU. SXU-A/B (SXZ282) software version must be 10. Tellabs 8000 manager support for Spanning Tree Transparency is available in Release 15 or higher.7 or higher. Tellabs 8100 manager support for Input Rate Monitoring and Fault Masking functionalities are available in Release 14 Service Pack 1 or higher. Bugs • • • • Extra faults are generated in other aggregation groups (X-bus and DSL) when Ethernet cable is cut.179 or higher if GMU450 hardware version is 1. (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. Tellabs 8100 manager support for this unit is available in Release 13A Service Pack 1 or higher. (CR ID 300054363) • 10004_22 © 2008 Tellabs. (CR ID 300046507) Contrary to other ESU group operations. CTE-R (SBZ674) software version must be 1. • • • • • • • • Restrictions • • Cross-connections to timeslot 144 and above that are not supported. Tellabs 8100 manager support for this unit and Tellabs 8110 STE-10M NTU is available in Release 14 Service Pack 3 or higher.ESU Unit: EMZ642 Unit Software • • GMX2 (GMZ802) software version can be any version. Over 8M cross-connection ports are not supported.5 or higher to support over 8M crossconnection ports. Over 8M cross-connection ports are not supported. GMU (GMZ460 and GMZ461) software version must be 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 89 .0.0 and software version must be 1. SXU-C (SXZ289) software can be any version. (CR ID 300047268) ESU static MAC addresses list and address statistics information conflict. (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.

Over 8M cross-connection ports are not supported. Over 8M cross-connection ports are not supported. (CR ID 300037430) More SNMP query related bugs have been fixed.19. CCU (SCZ286) software can be any version. XCG (SMZ538) software version must be 2. if GMU450 hardware version is 2. Tellabs 8100 manager support for Input Rate Monitoring and Fault Masking functionalities are available in Release 14 Service Pack 1 or higher. SCU-H (SCZ545) software version must be 1.5 or higher to support over 8M cross-connection ports. GMX (GMZ544) software version must be 3.4 or higher to support extra backups for other units in the node. SXU-A/B (SXZ282) software version must be 10. ifType. ifPhysAddress. and 3. (CR IDs 300038858 and 300032720) Dependencies • • • • • • • • • • ESU (ESU783 and ESM784) hardware version must be 1.ESU Unit: EMZ642 Unit Software 8.0 and software version must be 1.1 or higher to support extra backups for other units in the node.11 and TXA642_1. or 4. ifInUnknownProtos. and 3. ifOutDiscards and ifOutErrors.0 or higher to support 4-pair line modes.11 contains EMZ642_1.1 or higher to support over 8M crossconnection ports.179 or higher if GMU450 hardware version is 1.2 Version 1. SXU-V (SXZ630) software can be any version.7 or higher. CXU-M (SXZ288) software can be any version.11 The version 1.0 or higher to support extra backups for other units in the node. ifAdminStatus. Tellabs 8100 manager support for this unit and Tellabs 8110 STE-10M NTU is available in Release 14 Service Pack 3 or higher. Enhancements and Fixed Bugs • • End-customer spanning tree transparency added.1 or higher to support 3088 kbit/s line rates with Tellabs 8110 STE-10M NTU.5 or higher to support over 8M crossconnection ports. ifMtu. Tellabs 8100 manager support for this unit is available in Release 13A Service Pack 1 or higher.0 or higher.1. SCO interface module version must be 3. ifSpeed. • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 90 10004_22 © 2008 Tellabs. SCP (SCZ281) software version must be 3. GMU (GMZ460 and GMZ461) software version must be 1.0. Behavior of the following objects has been changed: ifDescr. .6 or higher to support unlocking the ports without failures. SCU (SCZ280) software version must be 8. SXU-C (SXZ289) software can be any version.

0 or higher to support sync pulse.6 or higher to support unlocking the ports without failures. (CR IDs 200032065.0 or higher. ESU unit with SCO: The Line Loop (LiL) is not supported in case of SCO interfaces connected to any NTU. SCP (SCZ281) software version must be 3. (CR ID 200020353) SNMP query related bugs have been fixed. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 91 10004_22 © 2008 Tellabs.3 Version 1. Enhancements and Fixed Bugs • • More flexibility has been added for ESU MAC address limit. and 3. SCU (SCZ280) software version must be 8. SCU-H (SCZ545) software version must be 1.ESU Unit: EMZ642 Unit Software • • Tellabs 8000 manager support for Spanning Tree Transparency is available in Release 15 or higher. (CR ID 300054363) • 8. XCG (SMZ538) software version must be 2.10 The version 1.5 or higher to support over 8M cross-connection ports.1 or higher to support extra backups for other units in the node.0 or higher to support extra backups for other units in the node. CTE-R (SBZ674) software version must be 1. (CR ID 300046507) Contrary to other ESU group operations. Bugs • • • • Extra faults are generated in other aggregation groups (X-bus and DSL) when Ethernet cable is cut. .10 contains EMZ642_1.1. CCU (SCZ286) software can be any version. Restrictions • • Cross-connections to timeslot 144 and above that are not supported.4 or higher to support extra backups for other units in the node. (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.10 and TXA642_1. (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. 200037770 and 200037938) Dependencies • • • • • • ESU (ESU783 and ESM784) hardware version must be 1. 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 IDs 300038858 and 300032720). Enhancements and Fixed Bugs • • 10M SHDSL support for ESU.9 The version 1. SXU-V (SXZ630) software can be any version. Over 8M cross-connection ports are not supported.0. SXU-A/B (SXZ282) software version must be 10. if GMU450 hardware version is 2. or 4. CTE-R (SBZ674) software version must be 1.4 Version 1. (CR ID 200028425) ESU FPGA modification for supporting over 8 Mbits/s line speeds. 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. .7 or higher.5 or higher to support over 8M crossconnection ports.19. • • • • • • • Restrictions • ESU unit with SCO: The Line Loop (LiL) is not supported in case of SCO interfaces connected to any NTU. 8.1 or higher to support over 8M crossconnection ports.9 contains EMZ642_1.ESU Unit: EMZ642 Unit Software • • • CXU-M (SXZ288) software can be any version. Tellabs 8100 manager support for Input Rate Monitoring and Fault Masking functionalities are available in Release 14 Service Pack 1 or higher.179 or higher if GMU450 hardware version is 1. GMX (GMZ544) software version must be 3. Bugs • Still some SNMP query related bugs.0 or higher to support sync pulse. Tellabs 8100 manager support for this unit and Tellabs 8110 STE-10M NTU is available in Release 14 Service Pack 3 or higher.9 and TXA642_1. SXU-C (SXZ289) software can be any version. GMU (GMZ460 and GMZ461) software version must be 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 92 10004_22 © 2008 Tellabs.0 or higher.0 and software version must be 1. (CR ID 200034611) Dependencies • • • ESU (ESU783 and ESM784) hardware version must be 1.1.1 or higher to support extra backups for other units in the node. CCU (SCZ286) software can be any version. SCP (SCZ281) software version must be 3.

1 or higher to support over 8M crossconnection ports. SXU-C (SXZ289) software can be any version. CXU-M (SXZ288) software can be any version. CTE-R (SBZ674) software version must be 1.19. Tellabs 8100 manager support for Input Rate Monitoring and Fault Masking functionalities are available in Release 14 Service Pack 1 or higher.7 or higher.0.0 and software version must be 1. Tellabs 8100 manager support for this unit is available in Release 13A Service Pack 1 or higher. and 3.0 or higher to support extra backups for other units in the node.0 or higher to support sync pulse.4 or higher to support extra backups for other units in the node. or 4. Tellabs 8100 manager support for this unit and Tellabs 8110 STE-10M NTU is available in Release 14 Service Pack 3 or higher. XCG (SMZ538) software version must be 2. • • • • • • • Restrictions • ESU unit with SCO: The Line Loop (LiL) is not supported in case of SCO interfaces connected to any NTU. (CR ID 200032065) 10004_22 © 2008 Tellabs. SXU-V (SXZ630) software can be any version. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 93 . Over 8M cross-connection ports are not supported.5 or higher to support over 8M crossconnection ports.ESU Unit: EMZ642 Unit Software • • • • • • SCU (SCZ280) software version must be 8. Over 8M cross-connection ports are not supported. SCU-H (SCZ545) software version must be 1. if GMU450 hardware version is 2. GMX (GMZ544) software version must be 3.6 or higher to support unlocking the ports without failures.179 or higher if GMU450 hardware version is 1. Bugs • There is a SNMP walk related problem.5 or higher to support over 8M cross-connection ports. GMU (GMZ460 and GMZ461) software version must be 1. SXU-A/B (SXZ282) software version must be 10.

CCU (SCZ286) software can be any version.8 The version 1. SXU-A/B (SXZ282) software can be any version. SXU-C (SXZ289) software can be any version. SCP (SCZ281) software version must be 3. • • • • • • Restrictions • • • ESU unit with SCO: The Line Loop (LiL) is not supported in case of SCO interfaces connected to any NTU.5 Version 1.0 or higher to support extra backups for other units in the node. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 94 10004_22 © 2008 Tellabs.ESU Unit: EMZ642 Unit Software 8.0 and software version must be 1. Enhancements and Fixed Bugs • Fixed SNMP Reply source port problem (CR ID 200020528). SXU-V (SXZ630) software can be any version.6 or higher to support unlocking the ports without failures. SXU-A/B/C does not support 12M trunks.1 or higher to support extra backups for other units in the node.0 or higher to support sync pulse. GMU (GMZ460 and GMZ461) software version must be 1. SCU (SCZ280) software version must be 8.179 or higher if GMU450 hardware version is 1.8 and TXA642_1.0. SCU-H (SCZ545) software version must be 1. if GMU450 hardware version is 2.8 contains EMZ642_1.19 or higher to support 12M trunk.0 or higher. GMX (GMZ544) software version must be 3. CXU-M (SXZ288) software can be any version. XCG (SMZ538) software version must be 2. .7 or higher. Dependencies • • • • • • • • • ESU (ESU783 and ESM784) hardware version must be 1. Tellabs 8100 manager support for this unit is available in Release 13A Service Pack 1 or higher. XCG does not support 12M trunks. Tellabs 8100 manager support for Input Rate Monitoring and Fault Masking functionalities are available in Release 14 Service Pack 1 or higher.0. CTE-R (SBZ674) software version must be 1.4 or higher to support extra backups for other units in the node.

CXU-M (SXZ288) software can be any version.7 contains EMZ642_1.ESU Unit: EMZ642 Unit Software Bugs • There is a SNMP walk related problem. • • • • • • 10004_22 © 2008 Tellabs. SCU (SCZ280) software version must be 8. XCG (SMZ538) software version must be 2. GMU (GMZ460 and GMZ461) software version must be 1.0.179 or higher if GMU450 hardware version is 1.4 or higher to support extra backups for other units in the node.19 or higher to support 12M trunk. Fixed LMI interoperability problem (CR ID 200014315). SXU-C (SXZ289) software can be any version.0 or higher.0 or higher to support extra backups for other units in the node. CTE-R (SBZ674) software version must be 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 95 .0 and software version must be 1. Enhancements and Fixed Bugs • • • • Port based rate limiting on external Ethernet ports (CR ID 200012088). SCU-H (SCZ545) software version must be 1.0 or higher to support sync pulse.0. GMX (GMZ544) software version must be 3. TXA642 version is shown correctly in File Management Dialog (CR ID 200012161). if GMU450 hardware version is 2.6 or higher to support unlocking the ports without failures. Fault Masking supported also on X-bus and Ethernet interfaces (CR ID 200012092). SXU-A/B (SXZ282) software can be any version. SXU-V (SXZ630) software can be any version.7 The version 1. Tellabs 8100 manager support for this unit is available in Release 13A Service Pack 1 or higher.1 or higher to support extra backups for other units in the node. Tellabs 8100 manager support for Input Rate Monitoring and Fault Masking functionalities are available in Release 14 Service Pack 1 or higher.7 and TXA642_1. SCP (SCZ281) software version must be 3. CCU (SCZ286) software can be any version.7 or higher.6 Version 1. Dependencies • • • • • • • • • ESU (ESU783 and ESM784) hardware version must be 1. (CR ID 200032065) 8.

SCU (SCZ280) software version must be 8.4 or higher to support extra backups for other units in the node. Dependencies • • • • ESU (ESU783 and ESM784) hardware version must be 1.0. .3 The version 1. Enhancements and Fixed Bugs • This is the first official version. 8.5 This is an internal test version.ESU Unit: EMZ642 Unit Software 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.8 Version 1. 8. XCG does not support 12M trunks.7 Version 1.0 or higher.10 Version 1. Bugs • SNMP reply is sent using a wrong source port (CR ID 200020528). 8.3 and TXA642_1. SCP (SCZ281) software version must be 3.6 This is an internal test version. 8.9 Version 1.1 or higher to support extra backups for other units in the node.3 contains EMZ642_1.4 This is an internal test version. CCU (SCZ286) software can be any version. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 96 10004_22 © 2008 Tellabs.

SXU-A/B (SXZ282) software can be any version.7 or higher.0 or higher to support sync pulse. SXU-V (SXZ630) software can be any version. if GMU450 hardware version is 2.179 or higher if GMU450 hardware version is 1. 10004_22 © 2008 Tellabs. Bugs • TXA642 version 1. SXU-A/B/C does not support 12M trunks.0 and software version must be 1.0 or higher to support extra backups for other units in the node. CTE-R (SBZ674) software version must be 1. GMU (GMZ460 and GMZ461) software version must be 1. XCG does not support 12M trunks.ESU Unit: EMZ642 Unit Software • • • • • SCU-H (SCZ545) software version must be 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 97 .19 or higher to support 12M trunk. GMX (GMZ544) software version must be 3. The version number is shown correctly if TXA642 has been downloaded using Tellabs 8100 network manager. CXU-M (SXZ288) software can be any version. Tellabs 8100 manager support for this unit is available in Release 13A Service Pack 1 or higher. XCG (SMZ538) software version must be 2.0. • • • • • Restrictions • • • ESU unit with SCO: The Line Loop (LiL) is not supported in case of SCO interfaces connected to any NTU.6 or higher to support unlocking the ports without failures. SXU-C (SXZ289) software can be any version.10 in the File Management dialog.0 is incorrectly shown as version 0.

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 8160 A111 and Tellabs 8170 cluster nodes as well as in Tellabs 8184 and Tellabs 8188 access switches. SXU-A/B (SXZ282) software version can be any version.1 or higher. XCG (SMZ538) software version can be any version. SCU-H (SCZ545) software version can be any version. The version 10. SCP (SCZ281) software version can be any version. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 98 10004_22 © 2008 Tellabs. . 2.y of GMZ283 (where y = 0. CXU-M (SXZ288) software version can be any version. SXU-V (SXZ630) software version must be 1. Tellabs 8150 basic. MartisDXX Manager support for the GMH unit is available in Release 12 or higher to support V5. 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). GMH (GMZ283) software version can be any version.2 can be only downloaded to the GMH units having the version 10. Dependencies • • • • • • • • • • • • • • GMH (base unit GMH220) hardware version must be 5.0 or higher. GMX (GMZ544) software version can be any version.1 Version 10.2 functionality and in Release 11 or higher to support the other functionalities. GMX2 (GMZ802) software version can be any version.…). SCU (SCZ280) software version can be any version. CCU (SCZ286) software version can be any version.2 Enhancements • The reason for this release is fixes in 1+1 protection functionality. Software supports all versions of the base unit. SXU-C (SXZ289) software version can be any version. 9. Restrictions • No restrictions. 1.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies 99 .g.2 Version 10. (CR ID 300088866).1 or higher. CCU (SCZ286) software version can be any version. (CRF 4003938) Downloaded GMH USW cannot be disabled by NMS. (CRF 4003647) Preliminary HDLC link timeout support for satellite connections for GMH has been done. SCU (SCZ280) software version can be any version.2 that SXU-V (or SCU-H) polls the trunk interface faults and monitors or sets Sa7-bit in E1 trunk. XCG (SMZ538) software version can be any version.2 functionality and in Release 11 or higher to support the other functionalities. Bugs • 1+1 protection switch does not work reliably if an interface is configured in 2M unframed mode. SXU-A/B (SXZ282) software version can be any version. 9.1 Enhancements • V5.GMH Unit: GMZ283 Unit Software Bugs • No known bugs. SCU-H (SCZ545) software version can be any version. Restrictions • No restrictions. GMX (GMZ544) software version can be any version. To prevent big delays FCI (Fast Command Interpreter) has been used instead of GCI (General Command Interpreter). download feature. GMH (GMZ283) software version can be any version.2 functionality is supported. SCP (SCZ281) software version can be any version. SXU-C (SXZ289) software version can be any version. because download is required for GMH to be fully operational. GMX2 (GMZ802) software version can be any version. (CRF 4003555) • • Dependencies • • • • • • • • • • • • • • GMH (base unit GMH220) hardware version must be 5. 10004_22 © 2008 Tellabs. CXU-M (SXZ288) software version can be any version.0 or higher. Without download only minimum set of operations are working e. It is required in V5. MartisDXX Manager support for the GMH unit is available in Release 12 or higher to support V5. SXU-V (SXZ630) software version must be 1.

(CR ID 300088866) • • • • 9. CCU (SCZ286) software version can be any version.0. (CRF 4002702) Parameters to OTE-LASER (OTE-LP) module cannot be set in new GMH version 5. CXU-M (SXZ288) software version can be any version. When HCE module and BTE module is assembled in the same GMH. (CRF 4003633) 1+1 protection switch does not work reliably if an interface is configured in 2M unframed mode.0. XCG (SMZ538) software version can be any version. Restrictions • USW 10. (CRF 4003268 and CRF 4003772) There is compatibility problem with BTE and HCE modules in GMH. GMX (GMZ544) software version can be any version.GMH Unit: GMZ283 Unit Software 9.0 Dependencies • GMH220 HW version must be at least 5. (CRF 4003357) Fast squelch of clock (GMH) interface. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 100 10004_22 © 2008 Tellabs. SCP (SCZ281) software version can be any version.3 Version 10.10 Dependencies • • • • • • • • • • GMH (base unit GMH220) hardware version must be less than 5. Interface windows show values correctly.4 Version 6.0.0 when USW is 10. Bugs • • • Communication to HTU-2M is lost after setting a Neighbor Node Loop (NNL) from the modem.0 version does not support BTE-384 modules. GMH (GMZ283) software version can be any version. but PMS gets wrong values. SCU-H (SCZ545) software version can be any version. SCU (SCZ280) software version can be any version. (CRF 4003322) Available time in 1+1 protected trunk performance data is always 100% in GMH units even if interfaces are cut. GMX2 (GMZ802) software version can be any version. . the line statistics window of HCE module cannot be opened. (CRF 4003959) VTP bus is making errors and this causes wrong time stamp values.

8 or 64 frame buffers in Tellabs 8170 cluster nodes.9 Dependencies • GMH (base unit GMH220) hardware version must be less than 5.1.10 Rx signal missing alarm for IF 2 is not reported when framing is off. Bugs • • DEG alarm with S-status does not work properly. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 101 .9 version does not support BTE-320. TS0 bit inversion. Restrictions • • • GMH220 HW versions 1. BTE-2304 modules.10 version does not support HCE-2M-1P and HCE-2M-2P modules. TS0 bit inversion. 1.2 do not support 4.1 or higher. BTE-576. An alarm will be generated when using x-connected time slot for HDLC. USW 6. SXU-C (SXZ289) software version can be any version.9 version does not support HCE-2M-1P and HCE-2M-2P modules.0. and 1. USW 6. MartisDXX Manager support for the GMH unit is available in Release 10. Bugs • In USW 6. Restrictions • • • • • GMH220 HW versions 1.2 do not support 4. Unnecessary Tx-Clock fault when using BTE-4096 module.1. 9. 1.0. BTE-1088-2W. 10004_22 © 2008 Tellabs. and 1.0. USW 6.5 Version 6. SXU-V (SXZ630) software version must be 1. 8 or 64 frame buffers in Tellabs 8170 cluster nodes.GMH Unit: GMZ283 Unit Software • • • • SXU-A/B (SXZ282) software version can be any version.

TS0 bit inversion.7 version does not support DEG/EXC BER alarms. 1.7 version does not support CAS at 2M < bit rate < 8M. BTE-1088-2W. Frequency difference alarm does not meet the G. . BTE-576.0.6 Version 6. No alarm when neighbor makes V. Restrictions • • • • • • • • • • • GMH220 HW versions 1. USW 6.7 version does not support HCE-2M-1P and HCE-2M-2P modules. Unnecessary Tx-Clock fault when using BTE-4096 module. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist.1.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.2 do not support 4. USW 6. 8 or 64 frame buffers in cluster usage.0. An alarm will be generated when using a x-connected time slot for HDLC. BTE-2304 modules. and 1. • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 102 10004_22 © 2008 Tellabs. Handling of erroneous message from VTP-bus.7 version does not support BTE-320. USW 6.7 version does not support micro BTS.54 loop. USW 6. USW 6.7 Dependencies • GMH (base unit GMH220) hardware version must be less than 5.GMH Unit: GMZ283 Unit Software 9.

USW 6. An alarm will be generated when using x-connected time slot for HDLC.0.6 version does not support AIS detection in unframed mode. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 103 . Handling of erroneous message from VTP-bus. USW 6.6 version does not support CAS at 2M < bit rate < 8M.6 version does not support sync.0.7 Version 6.54 loop.6 Dependencies • GMH (base unit GMH220) hardware version must be less than 5.1. Unnecessary Tx-Clock fault when using BTE-4096 module. USW 6. line divider updating.6 version does not support BTE-320.6 version does not support micro BTS. USW 6.6 version does not support RAI-Xcon mode. BTE-2304 modules.6 version does not support BTE-2048-2W module. BTE-576. 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. • • • • 10004_22 © 2008 Tellabs. USW 6. 1. USW 6. USW 6. No alarm when neighbor makes V. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist.6 version does not support DEG/EXC BER alarms. Frequency difference alarm does not meet G. BTE-1088-2W.823 updated standard (1993).GMH Unit: GMZ283 Unit Software 9. and 1. Restrictions • • • • • • • • • • • • • GMH220 HW versions 1. USW 6. 8 or 64 frame buffers in Tellabs 8170 cluster nodes. TS0 bit inversion.6 version does not support HCE-2M-1P and HCE-2M-2P modules.2 do not support 4. USW 6.

823 updated standard (1993). Context checker prevents 2 frame buffer usage (updating of parameters). USW 6.5 version does not support HCE-2M-1P and HCE-2M-2P modules.5 version does not support RAI-Xcon mode.2 do not support 4. BTE-576. and 1. BTE-1088-2W. An alarm will be generated when using x-connected time slot for HDLC. USW 6.5 version does not support CAS at 2M < bit rate < 8M.5 version does not support BTE-320. 8 or 64 frame buffers in Tellabs 8170 cluster nodes.5 version does not support AIS detection in unframed mode. Unnecessary Tx-Clock fault when using BTE-4096 module. USW 6.5 version does not support DEG/EXC BER alarms. USW 6.54 loop. USW 6.5 version does not support micro BTS.GMH Unit: GMZ283 Unit Software 9. USW 6.5 Dependencies • GMH (base unit GMH220) hardware version must be less than 5. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist.5 version does not support sync.1.8 Version 6. Frequency difference alarm does not meet G. 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. . • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 104 10004_22 © 2008 Tellabs. BTE-2304 modules.5 version does not support BTE-2048-2W module.0. Restrictions • • • • • • • • • • • • • GMH220 HW versions 1. USW 6. line divider updating. USW 6. USW 6. Handling of erroneous message from VTP-bus. 1.0. TS0 bit inversion. No alarm when neighbor makes V.

USW 6. USW 6.54 loop.4 Dependencies • GMH (base unit GMH220) hardware version must be less than 5.4 version does not support RAI-Xcon mode.4 version does not support CAS at 2M < bit rate < 8M. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist.0. USW 6.0.GMH Unit: GMZ283 Unit Software 9.4 version does not support preventing of VTP-bus corruption when the VTPoscillator fails. line divider updating. 8 or 64 frame buffers in Tellabs 8170 cluster nodes.823 updated standard (1993). An alarm will be generated when using x-connected time slot for HDLC. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 105 .4 version does not support BTE-1088.4 version does not support HCE-2M-1P and HCE-2M-2P modules. USW 6. 1.4 version does not support AIS detection in unframed mode. No alarm when neighbor makes V. BTE-2304 modules.4 version does not support DEG/EXC BER alarms.4 version does not support micro BTS. G703-120. USW 6. Handling of erroneous message from VTP-bus. USW 6. and 1.1.2 do not support 4. BTE-1088-2W. USW 6. BTE-4096. G703-75. Restrictions • • • • • • • • • • • • • • • • GMH220 HW versions 1. USW 6.4 version does not support sync. • • • 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. G703-8M modules. USW 6. Frequency difference alarm does not meet G.4 version does not support BTE-320. USW 6. TS0 bit inversion. USW 6. USW 6. BTE-576.9 Version 6.4 version does not support BTE-2048-2W module.4 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 micro BTS. and 1. Restrictions • • • • • • • • • • • • • • • • • • GMH220 HW versions 1. . USW 6.3 version does not support DEG/EXC BER alarms. No alarm when neighbor makes V.3 version does not support BTE-1088.3 version does not support CAS at 2M < bit rate < 8M. USW 6. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist. USW 6.54 loop. G703-8M modules. Handling of erroneous message from VTP-bus. 8 or 64 frame buffers in Tellabs 8170 cluster nodes. BTE-4096. 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. USW 6. USW 6.0.0. An alarm will be generated when using x-connected time slot for HDLC. USW 6.3 version does not support sync. • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 106 10004_22 © 2008 Tellabs.3 version does not support BTE-2048-2W module. USW 6.3 version does not support HCE-2M-1P and HCE-2M-2P modules.3 version does not support BTE-384 module wetting current strapping info (in the new version BTE-384 strapping possibility). USW 6. G703-120. BTE-1088-2W. USW 6. 1.GMH Unit: GMZ283 Unit Software 9.3 version does not support FSW-RAI usage: X-sync. line divider updating. TS0 bit inversion. V35-G704S and X21-G704S modules.3 version does not support preventing of VTP-bus corruption when the VTPoscillator fails.3 Dependencies • GMH (base unit GMH220) hardware version must be less than 5. G703-75. USW 6. Frequency difference alarm does not meet G.3 version does not support BTE-320.10 Version 6. BTE-2304 modules.823 updated standard (1993). BTE-576.1. USW 6.3 version does not support RAI-Xcon mode. USW 6. USW 6.3 version does not support BTE-2048.2 do not support 4.3 version does not support AIS detection in unframed mode.

USW 6. and 1. G703-120.2 version does not support BTE-384 module wetting current strapping info (in the new version BTE-384 strapping possibility).2 version does not support CAS at 2M < bit rate < 8M. USW 6. BTE-4096. 9. Frequency difference alarm does not meet G. TS0 bit inversion.1. USW 6.2 version does not support preventing of VTP-bus corruption when the VTPoscillator fails.0.2 version does not support BTE-2048-2W module. USW 6.2 do not support 4.2 version does not support bit rate 33 x 64 kbit/s. BTE-2304 modules. USW 6. USW 6. USW 6.2 version does not support DEG/EXC BER alarms. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 107 . BTE-576. USW 6. G703-8M modules. Restrictions • • • • • • • • • • • • • • • • • • • • GMH220 HW versions 1. 8 or 64 frame buffers in Tellabs 8170 cluster nodes.2 version does not support RAI-Xcon mode.2 version does not support FSW-RAI usage: X-sync.2 version does not support BTE-1088. 1.2 version does not support AIS detection in unframed mode.2 version does not support BTE-2048. BTE-1088-2W. USW 6.2 version does not support V35-G704B and X21-G704 modules.2 version does not support micro BTS. USW 6.2 version does not support HCE-2M-1P and HCE-2M-2P modules.2 Dependencies • GMH (base unit GMH220) hardware version must be less than 5. An alarm will be generated when using x-connected time slot for HDLC. USW 6.11 Version 6. USW 6. V35-G704S and X21-G704S modules. G703-75. 10004_22 © 2008 Tellabs. USW 6. USW 6.0.823 updated standard (1993).GMH Unit: GMZ283 Unit Software • 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).2 version does not support BTE-320. USW 6.2 version does not support sync. line divider updating. USW 6.

8 or 64 frame buffers in Tellabs 8170 cluster nodes. USW 6. USW 6.1 version does not support bit rate 33 x 64 kbit/s.54 loop. No alarm when neighbor makes V. 1. BTE-1088-2W.1 version does not support CAS at 2M < bit rate < 8M. G703-120.1 version does not support V35-G704B and X21-G704 modules. V35-G704S and X21-G704S modules.1 version does not support preventing of VTP-bus corruption when the VTPoscillator fails. • • • • 9. USW 6.1 Dependencies • GMH (base unit GMH220) hardware version must be less than 5. .0. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 108 10004_22 © 2008 Tellabs.1 version does not support HCE-2M-1P and HCE-2M-2P modules.12 Version 6. BTE-576.1 version does not support micro BTS. An alarm will be generated when using x-connected time slot for HDLC. TS0 bit inversion.1 version does not support BTE-320.1 version does not support BTE-2048. USW 6.1 version does not support BTE-384 module wetting current strapping info (in the new version BTE-384 strapping possibility). BTE-4096.1 version does not support BTE-1088.1 and 1. USW 6.1 version does not support FSW-RAI usage: X-sync. USW 6.GMH Unit: GMZ283 Unit Software 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. USW 6. USW 6.823 updated standard (1993). USW 6.0. USW 6. Handling of erroneous message from VTP-bus. USW 6. USW 6.2 do not support 4.1 version does not support DEG/EXC BER alarms. G703-75. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist. G703-8M modules. Frequency difference alarm does not meet G. Restrictions • • • • • • • • • • • • • • • • GMH220 HW versions 1. BTE-2304 modules. 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).

Does not support ring synchronization. • • • • • • • 9.1 version does not support sync. USW 5. Restrictions • • • • • • • • • • GMH220 HW versions 1. Frequency difference alarm does not meet G. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist. USW 5. 8 or 64 frame buffers in Tellabs 8170 cluster nodes.0. No alarm when neighbor makes V. USW 5. 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. An alarm will be generated when using x-connected time slot for HDLC.13 Version 5. USW 5. 1.1 version does not support BTE-2048-2W module.54 loop. USW 5. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 109 .8 version does not support BTE-320.8 version does not support HCE-2M-1P and HCE-2M-2P modules. 10004_22 © 2008 Tellabs.1 version does not support RAI-Xcon mode. TS0 bit inversion . USW 5.8 version does not support V35-G704B and X21-G704 modules.GMH Unit: GMZ283 Unit Software • • • • USW 6.0. USW 6.8 version does not support DEG/EXC BER alarms.823 updated standard (1993).1 and 1. line divider updating. USW 6. BTE-576. Handling of erroneous message from VTP-bus. Does not support signalling when bit rate is 18…31 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).1 version does not support AIS detection in unframed mode.8 version does not support CAS at 2M < bit rate < 8M. BTE-1088-2W. Fault mask alarm with S status which will start the recovery operation. USW 6.2 do not support 4.8 version does not support micro BTS.8 Dependencies • GMH (base unit GMH220) hardware version must be less than 5. BTE-2304 modules.

BTE-576.8 version does not support FSW-RAI usage: X-sync.8 version does not support BTE-384 module wetting current strapping info (in the new version BTE-384 strapping possibility).1 and 1. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist. Restrictions • • • • GMH220 HW versions 1.2 do not support 4. USW 5. 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. G703-8M modules.54 loop.14 Version 5. USW 5. TS0 bit inversion.0. BTE-2304 modules. 10004_22 © 2008 Tellabs. No alarm when neighbor makes V.7 Dependencies • GMH (base unit GMH220) hardware version must be less than 5. 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). V35-G704S and X21-G704S modules.8 version does not support preventing of VTP-bus corruption when the VTPoscillator fails. USW 5. USW 5.8 version does not support RAI-Xcon mode. USW 5.0. BTE-1088-2W.7 version does not support BTE-320. USW 5.8 version does not support V35-G704 and V36-G704 modules nor BTE-768 modules. line divider updating. USW 5. USW 5.8 version does not support sync.8 version does not support AIS detection in unframed mode. G703-120. USW 5.GMH Unit: GMZ283 Unit Software • • • • • • • • • • • • USW 5. USW 5. USW 5.8 version does not support BTE-2048-2W module.8 version does not support BTE-1088. USW 5. • • • • 9. G703-75. 8 or 64 frame buffers in Tellabs 8170 cluster nodes. Handling of erroneous message from VTP-bus.7 version does not support HCE-2M-1P and HCE-2M-2P modules.8 version does not support 1+1 protected trunks. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 110 .8 version does not support BTE-2048.8 version does not support bit rate 33 x 64 kbit/s. 1. USW 5. BTE-4096.

7 version does not support RAI-Xcon mode.7 version does not support CAS at 2M < bit rate < 8M. USW 5. BTE-4096.7 version does not support BTE-1088.823 updated standard (1993). USW 5. USW 5. G703-75.7 version does not support AIS detection in unframed mode. No alarm when neighbor makes V. USW 5.7 version does not support preventing of VTP-bus corruption when the VTPoscillator fails.7 version does not support sync. USW 5.7 version does not support V35-G704B nor X21-G704 modules. G703-8M modules.7 version does not support FSW-RAI usage: X-sync. Fault mask alarm with S status which will start the recovery operation. USW 5. USW 5.7 version does not support bit rate 33 x 64 kbit/s.7 version does not support BTE-384 module wetting current strapping info (in the new version BTE-384 strapping possibility). USW 5. USW 5. USW 5. USW 5.7 version does not support 1+1 protected trunks. USW 5.7 version does not support BTE-2048. Bugs • Mismatch of 2 frame buffer with uneven bus allocation can occur if locked interface buffer length is changed. USW 5.7 version does not support ring synchronization.54 loop. Handling of erroneous message from VTP-bus.GMH Unit: GMZ283 Unit Software • • • • • • • • • • • • • • • • • • An alarm will be generated when using x-connected time slot for HDLC. line divider updating.7 version does not support signalling when bit rate is 18…31 x 64 kbit/s.7 version does not support micro BTS. USW 5. USW 5. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist. V35-G704S and X21-G704S modules. USW 5. USW 5. then the CAS state is changed and finally buffer length is changed to 2 frame. USW 5. 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). Frequency difference alarm does not meet G. • • • • • • • 10004_22 © 2008 Tellabs. G703-120.7 version does not support V35-G704 nor V36-G704 modules nor BTE-768 modules.7 version does not support DEG/EXC BER alarms. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 111 .7 version does not support BTE-2048-2W module.

5 version does not support bit rate 33 x 64 kbit/s. 1. USW 5.5 Dependencies • GMH (base unit GMH220) hardware version must be less than 5. BTE-576. USW 5.5 version does not support BTE-2048-2W module.5 version does not support preventing of VTP-bus corruption when the VTPoscillator fails. USW 5. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 112 10004_22 © 2008 Tellabs.5 version does not support FSW-RAI usage: X-sync. USW 5. 8 or 64 frame buffers in Tellabs 8170 cluster nodes. . BTE-2304 modules.0. USW 5. G703-75.5 version does not support micro BTS. USW 5.15 Version 5. An alarm will be generated when using x-connected time slot for HDLC. G703-8M modules.5 version does not support HCE-2M-1P and HCE-2M-2P modules.5 version does not support BTE-1088.5 version does not support CAS at 2M < bit rate < 8M.GMH Unit: GMZ283 Unit Software 9. USW 5. USW 5.5 version does not support RAI-Xcon mode. Restrictions • • • • • • • • • • • • • • • • • • • • • • GMH220 HW versions 1. USW 5.5 version does not support V35-G704 nor V36-G704 modules nor BTE-768 modules. USW 5.5 version does not support BTE-384 module wetting current strapping info (in the new version BTE-384 strapping possibility).2 do not support 4. USW 5. USW 5.5 version does not support 1+1 protected trunks.5 version does not support AIS detection in unframed mode. USW 5. line divider updating.5 version does not support BTE-2048. USW 5.0.5 version does not support BTE-320. Frequency difference alarm does not meet G. V35-G704S and X21-G704S modules.5 version does not support V35-G704B nor X21-G704 modules. USW 5.1 and 1. TS0 bit inversion. USW 5. G703-120. USW 5. BTE-1088-2W. BTE-4096.823 updated standard (1993).5 version does not support DEG/EXC BER alarms. USW 5.5 version does not support sync.

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. BTE-576.2 version does not support micro BTS. USW 5.2 version does not support bit rate 33 x 64 kbit/s. USW 5. Does not support split trunk usage.5 version Does not support signalling when bit rate is 18…31 x 64 kbit/s. TS0 bit inversion. Handling of erroneous message from VTP-bus.2 do not support 4. USW 5. USW 5.16 Version 5. An alarm will be generated when using x-connected time slot for HDLC.1 and 1.2 version does not support V35-G704B nor X21-G704 modules. BTE-2304 modules.0. USW 5. 8 or 64 frame buffers in Tellabs 8170 cluster nodes.2 version does not support 1+1 protected trunks.2 version does not support DEG/EXC BER alarms. • • • • • • • • 9.GMH Unit: GMZ283 Unit Software 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.2 version does not support CAS at 2M < bit rate < 8M.2 version does not support BTE-320.54 loop. USW 5.823 updated standard (1993). Fault mask alarm with S status which will start the recovery operation. USW 5. Restrictions • • • • • • • • • • • • • • GMH220 HW versions 1.5 version does not support ring synchronization. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 113 . USW 5. No alarm when neighbor makes V. 1. BTE-1088-2W. Frequency difference alarm does not meet G. V35-G704S and X21-G704S modules.2 version does not support BTE-2048.2 Dependencies • GMH (base unit GMH220) hardware version must be less than 5.2 version does not support HCE-2M-1P and HCE-2M-2P modules.2 version does not support V35-G704 nor V36-G704 modules nor BTE-768 modules. USW 5. USW 5. USW 5. 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). USW 5.0.

line divider updating. USW 5. USW 5. No alarm when neighbor makes V. G703-75. Fault mask alarm with S status which will start the recovery operation.54 loop. USW 5.2 version does not support Tellabs 8170 cluster nodes. USW 5.2 version does not support sync. BTE-4096. Handling of erroneous message from VTP-bus. USW 5. • • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 114 10004_22 © 2008 Tellabs.2 version does not support ring synchronization. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist.2 version does not support RAI-Xcon mode. USW 5. USW 5.GMH Unit: GMZ283 Unit Software • • • • • • • • USW 5. G703-120. USW 5. USW 5. G703-8M modules. 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.2 version does not support BTE-2048-2W module.2 version does not support split trunk usage. .2 version does not support signalling when bit rate is 18…31 x 64 kbit/s.2 version does not support BTE-1088. USW 5.2 version does not support preventing of VTP-bus corruption when the VTPoscillator fails.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 FSW-RAI usage: X-sync.2 version does not support AIS detection in unframed mode. 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).

USW 5. USW 5.1 version does not support BTE-384 module wetting current strapping info (in the new version BTE-384 strapping possibility).1 version does not support BTE-320.1 version does not support V35-G704 nor V36-G704 nor BTE-768 modules. USW 5. Restrictions • • • • • • • • • • • • • • • • • • • • • • GMH220 HW versions 1.0.823 updated standard (1993). USW 5. USW 5.1 version does not support AIS detection in unframed mode.1 version does not support FSW-RAI usage: X-sync. USW 5. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 115 .1 version does not support BTE-2048-2W module.1 version does not support DEG/EXC BER alarms. V35-G704S and X21-G704S modules.2 do not support 4. TS0 bit inversion.1 version does not support HCE-2M-1P and HCE-2M-2P modules. BTE-4096. USW 5. USW 5. USW 5.1 version does not support BTE-1088. G703-75.1 and 1.17 Version 5. USW 5. USW 5. USW 5. USW 5.1 Dependencies • GMH (base unit GMH220) hardware version must be less than 5. BTE-2304 modules. USW 5.0. An alarm will be generated when using x-connected time slot for HDLC. Frequency difference alarm does not meet G. 8 or 64 frame buffers in Tellabs 8170 cluster nodes. USW 5. 10004_22 © 2008 Tellabs. line divider updating.1 version does not support CAS at 2M < bit rate < 8M. USW 5.GMH Unit: GMZ283 Unit Software 9.1 version does not support BTE-2048.1 version does not support bit rate 33 x 64 kbit/s.1 version does not support RAI-Xcon mode. BTE-1088-2W.1 version does not support preventing of VTP-bus corruption when the VTPoscillator fails.1 version does not support 1+1 protected trunks. USW 5. USW 5. 1. G703-120.1 version does not support sync.1 version does not support V35-G704B nor X21-G704 modules.1 version does not support micro BTS. BTE-576. G703-8M modules.

0) USW 5. Errors in the sent MCLK RAI when the bit is configured into the payload and no crossconnections to that port exist.1 version does not support signalling when the bit rate is 18…31 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). . No alarm when neighbour makes V.GMH Unit: GMZ283 Unit Software 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.1 version does not support BTE Rx level and quality info.1 version does not support Tellabs 8170 cluster nodes. Sending of CRCE bits at permanent 0 and 1 state fails.1 version does not support split trunk usage.54 loop. USW 5. Fault mask alarm with S status which will start the recovery operation.1 version does not generate multiframe far-end alarm to the NMS.1 version does not support GDH 75/120 info (GDH module version ≥ 4.1 version does not support ring synchronization. USW 5. USW 5. • • • • • • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 116 10004_22 © 2008 Tellabs. USW 5. Handling of erroneous message from VTP-bus. USW 5. USW 5.

. SCU-H (SCZ545) software version can be any version.6 or higher. GMX (GMZ544) software version can be any version.5 or higher.1 or higher MartisDXX Manager should be Release 8. SXU-V (SXZ630) software version 1. SCU (SCZ280) software version can be any version. Previously trunk conditioning wasn’t removed until the red alarm disappeared. 10004_22 © 2008 Tellabs. GMH (GMZ283) software version can be any version. SCP (SCZ281) software version can be any version..3 Enhancements and Fixed Bugs • When a unit is in a red alarm state and the defect causing the state disappears.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.x CCU (SCZ286) software version can be any version. the trunk conditioning should be removed immediately.3 can be downloaded to GMM units having the version 2.0a or higher. XCG (SMZ538) software version can be any version. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 117 . 10. Tellabs 8160 A111 and Tellabs 8170 cluster nodes. 1.1 Version 2. The version 2. 2. SXU-C (SXZ289) software version must be 2.). SXU-A/B (SXZ282) software version must be 6. CXU-M (SXZ288) software version can be any version. (CR ID 300042935) Dependencies • • • • • • • • • • • • • • GMM unit (GMM253) hardware version must be 1.x GDM298 hardware version must be 1.y of GMZ438 (where y=0.

6 or higher. SCP (SCZ281) software version can be any version. TR170 says that the red alarm should be declared without idling the yellow. The NMS and T1. the unit in fact does idle the yellow. • Bugs • No known bugs. 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.GMM Unit: GMZ438 Unit Software Restrictions • • • • • If a red alarm condition arises during a yellow alarm.5 or higher. The T1 transceivers in the GDM 298 module do not always initialize properly.403 reports do indicate the correct situation. In CSU TR54016. Instead. SCU (SCZ280) software version can be any version. CXU-M (SXZ288) software version can be any version. XCG (SMZ538) software version can be any version.x CCU (SCZ286) software version can be any version. SXU-V (SXZ630) software version 1.x GDM298 hardware version must be 1. GMH (GMZ283) software version can be any version. SCU-H (SCZ545) software version can be any version. SXU-C (SXZ289) software version must be 2. 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. 10.2 Version 2.1 or higher Tellabs® 8100 Managed Access System Unit Software Version Dependencies 118 10004_22 © 2008 Tellabs. If a signalling connection is setup. If protection is forced to the active interface during the delay prior to a switchover then the switchover will happen anyway. with a Remote Line Loop already active. SXU-A/B (SXZ282) software version must be 6. the signalling will not pass correctly until the Loop is removed. GMX (GMZ544) software version can be any version. Another minor deviation from TR170: if LOF is injected on top of AIS then AIS is cleared before LOF is declared.2 Enhancements and Fixed Bugs • GMM T1 IF fault state is not updated correctly. (CR ID 200012722) Dependencies • • • • • • • • • • • • • GMM unit (GMM253) hardware version must be 1. .

x GDM298 hardware version must be 1. In CSU TR54016. CXU-M (SXZ288) software version can be any version. 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. GMX (GMZ544) software version can be any version. If protection is forced to the active interface during the delay prior to a switchover then the switchover will happen anyway. SCU-H (SCZ545) software version can be any version. Dependencies • • • • • • • • • • • • GMM253 hardware version must be 1. Another minor deviation from TR170: if LOF is injected on top of AIS then AIS is cleared before LOF is declared. the signalling will not pass correctly until the Loop is removed. • Bugs • When a unit is in a red alarm state and the defect causing the state disappears.3 Version 2. The NMS and T1. TR170 says that the red alarm should be declared without idling the yellow. (CR ID 300042935) 10. the trunk conditioning should be removed immediately. GMH (GMZ283) software version can be any version.5 or higher. XCG (SMZ538) software version can be any version. the unit in fact does idle the yellow. If a signalling connection is setup.x CCU (SCZ286) software version can be any version. Restrictions • • • • • If a red alarm condition arises during a yellow alarm.0a or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 119 . SCP (SCZ281) software version can be any version. Instead.GMM Unit: GMZ438 Unit Software • MartisDXX Manager should be Release 8. SCU (SCZ280) software version can be any version. SXU-C (SXZ289) software version must be 2. 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. SXU-A/B (SXZ282) software version must be 6.1 Enhancements and Fixed Bugs • Supports 1536K reference clock for node. 10004_22 © 2008 Tellabs.403 reports do indicate the correct situation. with a Remote Line Loop already active.6 or higher.

SXU-C (SXZ289) software version must be 2.GMM Unit: GMZ438 Unit Software • MartisDXX Manager should be Release 8. CXU-M (SXZ288) software version can be any version. SCU (SCZ280) software version can be any version. In CSU TR54016. the unit in fact does idle the yellow. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 120 10004_22 © 2008 Tellabs. GMX (GMZ544) software version can be any version. XCG (SMZ538) software version can be any version.x CCU (SCZ286) software version can be any version. 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 signalling will not pass correctly until the Loop is removed. • Bugs • GMM T1 IF fault state is not updated correctly. The T1 transceivers in the GDM 298 module not do not always initialize properly.0a or higher. MartisDXX Manager should be Release 8. (CR ID 200012722) 10. If a signalling connection is setup.0 Dependencies • • • • • • • • • • • • • GMM253 hardware version must be 1.5 or higher.4 Version 2. Another minor deviation from TR170: if LOF is injected on top of AIS then AIS is cleared before LOF is declared. Restrictions • • • • • If a red alarm condition arises during a yellow alarm.6 or higher.x GDM298 hardware version must be 1. TR170 says that the red alarm should be declared without idling the yellow. If protection is forced to the active interface during the delay prior to a switchover then the switchover will happen anyway. The NMS and T1. 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. . Instead. SXU-A/B (SXZ282) software version must be 6.0a or higher. GMH (GMZ283) software version can be any version.403 reports do indicate the correct situation. with a Remote Line Loop already active. SCU-H (SCZ545) software version can be any version. SCP (SCZ281) software version can be any version.

If a signalling connection is setup. Instead. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 121 . the signalling will not pass correctly until the Loop is removed.GMM Unit: GMZ438 Unit Software Restrictions • • • • • If a red alarm condition arises during a yellow alarm. 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.403 reports do indicate the correct situation. If protection is forced to the active interface during the delay prior to a switchover then the switchover will happen anyway. 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. with a Remote Line Loop already active. Another minor deviation from TR170: if LOF is injected on top of AIS then AIS is cleared before LOF is declared. The NMS and T1. the unit in fact does idle the yellow. In CSU TR54016. TR170 says that the red alarm should be declared without idling the yellow. 10004_22 © 2008 Tellabs. • Bugs • Does not support 1536K reference clock for node.

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. Applies to GMU-A only: SYN-34-E interface module works also for GMU-A (CR ID 200011636).0 boards. Tellabs 8160 A111 and Tellabs 8170 cluster nodes.8 can be downloaded to GMU-A or GMU having the version 1. Software GMZ460 is for the main processor and software GMZ461 is for the ASIC processor. GMZ460 version 1.y of GMZ460 (where y=0. 200011641).. Tellabs 8150 basic. Applies to GMU-A only: now it is not possible to cause illegal VC-12-mc configuration by using Tellabs 8100 network manager’s Node Manager copy/paste from a single VC12 (asynchronous mode) into VC12-mc/VC-12 (CR ID 200011098). 200011635. GMU is composed of GMU450 v1. GMU-A is composed of GMU450 v1. 200011636).). 11. • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 122 10004_22 © 2008 Tellabs. CR ID 200005303. .0. 'uneven' X-bus distribution is used however. Fixed corruption of Rx buffer centring.0 and DSU453 v2..8 Enhancements and Fixed Bugs • Applies to GMU-A only: when X-bus distribution is set to 'even' while P12s signal mapping mode is 'asynchronous'.0 and DSU453 v1.0 boards.0 or higher. Base unit hardware version is 2. 2. Base unit hardware version is 1. which caused traffic degradation in GMU (CR ID 200007236). (Technical note ID SOL2005). 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). Fixed wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047. SYN-34-E interface module internal test does not fail unintentionally and no fault ‘Initialization error (GMZ461)’ is produced anymore (CR ID 200004414. 1.1 Version 1.

5 or higher. MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher.1 standard on multiplex section (MS) layer.2 voice support. if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335. it is absolutely necessary to do "Remove from Inventory" for GMU-A. CXU-M (SXZ288) software version must be 2.GMU and GMU-A Units: GMZ460 Unit Software Dependencies • • • • • • • • • • • • • • • • • GMU hardware version must be 1.1 or higher. CR ID 200004858).1. CCU (SCZ286) software version can be any version. but not by GMU.1 or higher. SXU-C (SXZ289) software version must be 2. however GMU can be replaced with GMU-A. SCP (SCZ281) software version must be 3. are supported only by GMU-A.0 or higher.7 or higher.7 or higher.8 or higher.1 or higher. 10004_22 © 2008 Tellabs. SXU-V (SXZ630) software version must be 1.0. SXU-A/B (SXZ282) software version must be 6. GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12. background block error (BBE) count is not according to the standard due to hardware restrictions. Performance threshold values are not according to the EN 301 167 v. GMU-A hardware version must be 2. asynchronous mapping.1.8 or higher. GMX (GMZ544) software version can be any version. GMZ461 software version must be 1. CR ID 200005084). • Bugs • Tellabs 8100 control channel is not working in VC-2/VC-12 payload. On MS layer. MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 123 . XCG (SMZ538) software version must be 2. Restrictions • • • It is not supported to replace GMU-A with GMU. 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. In GMU-A standard method can be used if BIP-1 based MS block error calculation is selected (CRF ID 4003017). SCU software version must be 8. SCU-H (SCZ545) software version must be 1. P12s termination and V5.6 or higher. GMU-A specific features. Before inserting GMU unit into a slot where GMU-A has been (in the inventory).

are supported only by GMU-A.7 or higher. 10004_22 © 2008 Tellabs. SXU-V (SXZ630) software version must be 1. On MS layer.1.0.1 standard on multiplex section (MS) layer. Bugs • Tellabs 8100 control channel is not working in VC-2/VC-12 payload.GMU and GMU-A Units: GMZ460 Unit Software 11. GMU-A specific features. CR ID 200005084). SCU software version must be 8. XCG (SMZ538) software version must be 2. SXU-C (SXZ289) software version must be 2. CCU (SCZ286) software version can be any version.6 or higher.179. which caused traffic degradation in GMU (CR ID 200007236).2 Version 1. background block error (BBE) count is not according to the standard due to hardware restrictions.8 or higher. SXU-A/B (SXZ282) software version must be 6. This software is intended for GMU only. GMX (GMZ544) software version can be any version. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 124 . asynchronous mapping. SCP (SCZ281) software version must be 3. NOTE: Do not download this software in GMU-A. Restrictions • • • • Do not download this software version in GMU-A. however GMU can be replaced with GMU-A.1 or higher. (Technical note ID SOL2005). CXU-M (SXZ288) software version must be 2. In GMU-A standard method can be used if BIP-1 based MS block error calculation is selected (CRF ID 4003017). SCU-H (SCZ545) software version must be 1.1 or higher. but not by GMU.7 or higher. Enhancements and Fixed Bugs • Fixed corruption of Rx buffer centring.179 This is a non-production version based on version 1.1 or higher. Dependencies • • • • • • • • • • • • • GMU hardware version must be 1. P12s termination and V5. GMZ461 software version must be 1.2 voice support. it is absolutely necessary to do "Remove from Inventory" for GMU-A.5 or higher. This software is intended for GMU only.1. Performance threshold values are not according to the EN 301 167 v. if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335.7. It is not supported to replace GMU-A with GMU. Before inserting GMU unit into a slot where GMU-A has been (in the inventory).

Fix in node master clock “rank”: illegal value 0 was sometimes reported to neighbour nodes. some faults were never reported (CRF ID 4005206. Fault reporting bug fixed. Enhancements and Fixed Bugs • • • • • • • • • • • Enhancement in performance data collection.GMU and GMU-A Units: GMZ460 Unit Software 11.5 or higher. XCG (SMZ538) software version must be 2.3 Version 1. Fixed incorrect MLOF alarm with asynchronous SNC/N protected VC-12 with Channel Associated Signalling and P12s termination (CR ID 200005740). SXU-C (SXZ289) software version must be 2. CR ID 200005406).1 or higher. P12 layer fault reporting enhanced.7 NOTE: Do not download this software in GMU. Dependencies • • • • • • • • • • • • • • GMU-A hardware version must be 2.1 or higher. SCP (SCZ281) software version must be 3.0 or higher. Fixed flash corruption problem (CRF ID 4005110). MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher. CXU-M (SXZ288) software version must be 2. SXU-A/B (SXZ282) software version must be 6. G. a delta-type alarm is set active (CRF ID 4003054). also P12 layer fault events are reported.7 or higher. If fault event reporting is defined for a VC-12. SCU software version must be 8.1 or higher.7. . CR ID 200004858).7 or higher.8 or higher. BIP-1/BIP-24 block size based MS operation in GMU-A (CRF ID 4003330. CCU (SCZ286) software version can be any version. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 125 10004_22 © 2008 Tellabs. GMX (GMZ544) software version can be any version. SXU-V (SXZ630) software version must be 1. Extended production test support (CRF ID 4004928). MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher. GMZ461 software version must be 1. Fixed fault classification of UNAVAIL. QOS and QOSTR faults (CRF ID 4003428). SCU-H (SCZ545) software version must be 1. If 15-minute performance counter has other value than zero.826 performance monitoring data is collected also when TU cross-connection is missing (CRF ID 4004714).6 or higher. This software is intended for GMU-A only.

6 NOTE: Do not download this software in GMU. It is possible to cause illegal VC-12-mc configuration by using Tellabs 8100 network manager’s Node Manager copy/paste from a single VC12 (asynchronous mode) into VC12mc/VC-12 (CR ID 200011098). Tellabs® 8100 Managed Access System Unit Software Version Dependencies 126 10004_22 © 2008 Tellabs. Enhancements and Fixed Bugs • • • • • Asynchronous 2 Mbit/s signal mapping. Because of a bug in LTA ASIC. Before inserting GMU unit into a slot where GMU-A has been (in the inventory). 200011636). 200011635. CR ID 200005084). CR ID 200004858). • Bugs • • • SYN-34-E interface module does not work reliably (CR ID 200011636). • • • 11.1.1.e. V5. P12s (G. Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047. Restrictions • • • It is not supported to replace GMU-A with GMU. The byte can also be set with Tellabs 8100 Network Manager (interface window/overhead bytes) (CRF ID 4003371). This software is intended for GMU-A only. Transmitted NU2 byte in STM1 RSOH is balanced. Performance threshold values are not according to the EN 301 167 v. Tellabs 8100 control channel is not working in VC-2/VC-12 payload. 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).GMU and GMU-A Units: GMZ460 Unit Software • GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12. On MS layer. . it is absolutely necessary to do "Remove from Inventory" for GMU-A. Therefore. background block error (BBE) count is not according to the standard due to hardware restrictions. 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. SS bit values in AU4 pointer do not have to be ‘10’ anymore.704) termination. if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335. SYN-34-E interface module internal test fails unintentionally and produces fault ‘Initialization error (GMZ461)’ (CR ID 200004414. this software version can be used to connect GMU-A to SONET equipment (CRF ID 4004547). however GMU can be replaced with GMU-A.2 voice interface support in Tellabs 8150 basic node. In GMU-A standard method can be used if BIP-1 based MS block error calculation is selected (CRF ID 4003017). it has equal number of ‘0’ and ‘1’ bits (value 0xAA). CR ID 200005303).1 standard on multiplex section (MS) layer.4 Version 1. i.

1 or higher. ES. SES and secSesThreshold are compared correctly (CRF ID 4004442). Note: if software is downloaded to existing GMU-A. MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 127 .0 or higher. CR ID 200005406 (CR ID 200004414. SCU-H (SCZ545) software version must be 1. SXU-C (SXZ289) software version must be 2. SXU-A/B (SXZ282) software version must be 6. Bugs • • SYN-34-E interface module does not work reliably (CR ID 200011636). Other threshold values (ES and SES) are according to the standard. CXU-M (SXZ288) software version must be 2.GMU and GMU-A Units: GMZ460 Unit Software • • GMU-A does not cause “Unit IA” fault in Tellabs 8160 A111 after power up (CRF ID 4004646).7 or higher. however GMU can be replaced with GMU-A. MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher. execution of “Factory settings” is required for this feature (CRF ID 4003017).1 or higher. 200011636). Dependencies • • • • • • • • • • • • • • • GMU-A hardware version must be 2. VC-2. XCG (SMZ538) software version must be 2.5 or higher.1.1.8 or higher. GMZ461 software version must be 1.6.1 standard on multiplex section (MS) layer. Restrictions • • It is not supported to replace GMU-A with GMU. On MS layer. SCP (SCZ281) software version must be 3. VC-4. this fault is not shown by Tellabs 8100 network manager because of fault reporting bug CRF ID 4005206. GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12.6 or higher.7 or higher. SXU-V (SXZ630) software version must be 1. However. Threshold values on other layers (RS. SYN-34-E interface module internal test fails unintentionally and produces fault ‘Initialization error (GMZ461)’. GMX (GMZ544) software version can be any version. Performance monitoring thresholds lower BBE. Performance threshold values are not according to the EN 301 167 v. 200011635. SCU software version must be 8. CCU (SCZ286) software version can be any version. 10004_22 © 2008 Tellabs. VC-12) are according to the standard. background block error (BBE) count is not according to the standard due to hardware restrictions.1 or higher.

1. Tellabs 8100 control channel is not working in VC-2/VC-12 payload.8. The byte can also be set with Tellabs 8100 Network Manager (interface window/overhead bytes) (CRF ID 4003371). Incorrect MLOF alarm is reported with asynchronous SNC/N protected VC-12 with Channel Associated Signalling and P12s termination (CR ID 200005740). SXU-A/B software version must be at least 6. CR ID 200005084).GMU and GMU-A Units: GMZ460 Unit Software • It is possible to cause illegal VC-12-mc configuration by using Tellabs 8100 network manager’s Node Manager copy/paste from a single VC12 (asynchronous mode) into VC12mc/VC-12 (CR ID 200011098). CXU-M software version must be at least 2.5. Enhancements and Fixed Bugs • • • GMU does not cause “Unit IA” fault in Tellabs 8160 A111 after power up (CRF ID 4004646). • • • • • • • • 11.1. Node master clock “rank” is sometimes reported as illegal value “0” to neighbour nodes.e. XCG software version must be at least 2. NOTE: Do not download this software in GMU-A. Fault reporting bug. Because of a bug in LTA ASIC. CR ID 200005406). GMZ461 software version must be 1. CR ID 200005303). Dependencies • • • • • • • SCU software version must be at least 8.5. this software version can be used to connect GMU to SONET equipment (CRF ID 4004547).7. some faults are never reported (CRF ID 4005206. SS bit values in AU4 pointer do not have to be ‘10’ anymore. if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335. . SXU-C software version must be at least 2.102 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 128 10004_22 © 2008 Tellabs. it has equal number of ‘0’ and ‘1’ bits (value 0xAA). Transmitted NU2 byte in STM1 RSOH is balanced. Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047. Flash corruption problem (CRF ID 4005110). i. This software is intended for GMU only. QOS and QOSTR faults (CRF ID 4003428). SCP software version must be at least 3.7. Wrong fault classification of UNAVAIL. 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).5 Version 1. Therefore.102 This is a non-production version based on version 1.

SXU-C software version must be at least 2. XCG software version must be at least 2. however GMU can be replaced with GMU-A.6 Version 1.1. The user can minimize this problem by configuring monitoring TTPs of an SNC group to have the same values as the terminating TTP. Dependencies • • • • • • • SCU software version must be at least 8. Wrong fault classification of UNAVAIL.5 NOTE: Do not download this software in GMU-A. CR ID 200005084).5. GMZ461 software version must be 1. Versions 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 129 . SXU-A/B software version must be at least 6.7. 11. This software is intended for GMU only.0 and later. SES and secSesThreshold are compared incorrectly (CRF ID 4004442). It is not supported to replace GMU-A with GMU. Bugs • • • • • • Tellabs 8100 control channel is not working in VC-2/VC-12 payload. this may cause inconsistency between database and hardware. 10004_22 © 2008 Tellabs. Node master clock “rank” is sometimes reported as illegal value “0” to neighbour nodes.5. CXU-M software version must be at least 2. SCP software version must be at least 3. Performance monitoring thresholds lower BBE. Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047. Flash corruption problem (CRF ID 4005110). if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335.GMU and GMU-A Units: GMZ460 Unit Software Restrictions • • • Software can not be downloaded to GMU-A. ES.7.1. QOS and QOSTR faults (CRF ID 4003428). If SNC groups are configured by earlier NMS versions.8. CR ID 200005303).4 and later of GMU support advanced SNC group configuration but in MartisDXX Manager NMS this feature is supported in Release 10.

4. SXU-A/B software version must be at least 6. Dependencies • • • • • • • SCU software version must be at least 8. Wrong fault classification of UNAVAIL. SXU-C software version must be at least 2.GMU and GMU-A Units: GMZ460 Unit Software Restrictions • • • Software can not be downloaded to GMU-A. The user can minimize this problem by configuring monitoring TTPs of an SNC group to have the same values as the terminating TTP. CR ID 200005084). if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335.4 and later of GMU support advanced SNC group configuration but in MartisDXX Manager NMS this feature is supported in Release 10.7. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 130 10004_22 © 2008 Tellabs.7. CXU-M software version must be at least 2. If SNC groups are configured by earlier NMS versions.8. . XCG software version must be at least 2.4. QOS and QOSTR faults (CRF ID 4003428). 11.4 NOTE: Do not download this software in GMU-A. Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047.7 Version 1. It is not supported to replace GMU-A with GMU. SCP software version must be at least 3. Node master clock “rank” is sometimes reported as illegal value “0” to neighbour nodes. CR ID 200005303).1. GMZ461 software version must be 1. GMU causes “Unit IA” fault in Tellabs 8160 A111 after power up (CRF ID 4004646).1. however GMU can be replaced with GMU-A. Performance monitoring thresholds lower BBE. Flash corruption problem (CRF ID 4005110). ES. 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. this may cause inconsistency between database and hardware. This software is intended for GMU only.0 and later. Versions 1. SES and secSesThreshold are compared incorrectly (CRF ID 4004442).

Control channel in VC payload is not supported. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547). Group DEG does not work with SNC/N protection. It is not supported to replace GMU-A with GMU. Node master clock “rank” is sometimes reported as illegal value “0” to neighbour nodes. signal degrade seconds. GMU causes “Unit IA” fault in Tellabs 8160 A111 after power up (CRF ID 4004646). Recovery does not work between GMUs when they are located in Tellabs 8150 basic node. signal degrade threshold and TIMaAisenabled attributes cannot be changed in VCgtp if SNC/I protection is used. CAS.4 of GMU supports advanced SNC group configuration but in MartisDXX Manager NMS this feature is supported in Release 10. QOS and QOSTR faults (CRF ID 4003428). Spontaneous messages of TU12Ctps do not work. The performance management system of GMU fails to detect alarms from far end when receiving alarms from near end. if GMU is moved from Tellabs 8150 basic node to Tellabs 8170 cluster node or vice versa. Wrong fault classification of UNAVAIL.GMU and GMU-A Units: GMZ460 Unit Software Restrictions • • • • Software can not be downloaded to GMU-A. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 131 . CAS signaling does not work. Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047. this may cause inconsistency between database and hardware. AIS fault of SYN-34-E interface module does not work. ES. if GMU is a replacement unit. Spontaneous messages do not work. CAS signaling does not go through GMU. 10004_22 © 2008 Tellabs.0 and later. Version 1. If SNC groups are configured by earlier NMS versions. Expected TI. The user can minimize this problem by configuring monitoring TTPs of an SNC group to have the same values as the terminating TTP. CR ID 200005303). however GMU can be replaced with GMU-A. • Bugs • • • • • • • • • • • • • • Flash corruption problem (CRF ID 4005110). Performance monitoring thresholds lower BBE. SES and secSesThreshold are compared incorrectly (CRF ID 4004442).

CR ID 200005303). SSM enabling and disabling are not supported.8 Version 1.3 NOTE: Do not download this software in GMU-A. SCU backuping is not supported.3. Restrictions • • • • • • • • • • • Software can not be downloaded to GMU-A. Dependencies • • • • • • SCU software version must be at least 8. SCP software version must be at least 3. XCG is not supported. Wrong fault classification of UNAVAIL. X-bus slip counters of VC2s and VC12s are not supported. QOS and QOSTR faults (CRF ID 4003428). The supervisory unequipped feature of VC2 and VC12 is not supported. This software is intended for GMU only.7. Monitoring VCs of SNC group do not count far end bit errors.0. CXU-M software version must be at least 2. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547). . Tellabs® 8100 Managed Access System Unit Software Version Dependencies 132 10004_22 © 2008 Tellabs.GMU and GMU-A Units: GMZ460 Unit Software 11. Node master clock “rank” is sometimes reported as illegal value “0” to neighbour nodes. Control channel in VC payload is not supported. Bugs • • • • • • • Flash corruption problem (CRF ID 4005110). GMZ461 software version must be 1. It is not supported to replace GMU-A with GMU. SXU-C software version must be at least 2. Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047. TU12-LOMs exist for a short time. Advanced SNC configuration is not supported. If 34M-PsTTP alarm is activated and fault declare value is between 1-9. Ps34M performance thresholds are seen as MS thresholds if SYN-34-E interface module is configured.7. SXU-A/B software version must be at least 6. however GMU can be replaced with GMU-A.3. Configurable TIM consequent actions are not supported.8.

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

X-bus slip counters of VC2s and VC12s are not supported. NNM gives an alarm even if there is no corresponding control channel. Node master clock “rank” is sometimes reported as illegal value “0” to neighbour nodes. If MS 1+1 protection is active. Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047.GMU and GMU-A Units: GMZ460 Unit Software Restrictions • • • • • • • • • • • • Software can not be downloaded to GMU-A. XCG is not supported. Monitoring VCs of an SNC group do not count far end bit errors. If an equipment loop is set and LOS is detected. Wrong fault classification of UNAVAIL. If vcGtp is set to lock state and one VC locking fails. It is not supported to replace GMU-A with GMU. all VCs are not returned to the unlock state. however GMU can be replaced with GMU-A. RS-AIS is still sent to the RX direction and SSF is set to the lower level instances. DEG fault exists when an SLM fault of VC2/12 exists. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547). QOS and QOSTR faults (CRF ID 4003428). NNM1 alarms are seen as NNM2 alarms and NNM2 does not give alarms. In case of subnetwork connection protection auto switch does not clear manual switch. Configurable TIM consequent actions are not supported. VC4 LOM affects the performance data of VC4s. all read and write operations to interface loops are denied. 522 bytes of a non-volatile setting are not sent to SCU. Advanced SNC configuration is not supported. this means that part of spontaneous event reporting configurations are not backed up. SSM enabling and disabling are not supported. Control channel in VC payload is not supported. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 134 10004_22 © 2008 Tellabs. Bugs • • • • • • • • • • • • • • • • Flash corruption problem (CRF ID 4005110). The supervisory unequipped feature of VC2 and VC12 is not supported. . After 1+1 multiplex section protection switch VC2/12s could have an SSF fault without a reason. In case of SNCP monitoring VCs have fault status PMA although it should be DMA. CR ID 200005303). The SYN-34-E interface module is not supported. DEG fault exists shortly after an SSF fault of VC2/12. SCU backuping is not supported.

Restrictions • • • • Software can not be downloaded to GMU-A.7. if GMU is moved from Tellabs 8150 basic node to Tellabs 8170 cluster node or vice versa. SES and secSesThreshold are compared incorrectly (CRF ID 4004442). If VC4 TIM or LOM is active. If MS-AIS is received. Spontaneous messages of TU12Ctps do not work.1 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. Attribute waitToRestoreTime affects SNPO switch even if there has been manual switch. SXU-A/B software version must be at least 6. Performance monitoring thresholds lower BBE. The SYN-34-E interface module is not supported. Control channel in VC payload is not supported. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 135 . SCP software version must be at least 3. 11.1. SSF should be set too in MSTTPBid. AIS fault of SYN-34-E interface module does not work.0. The performance management system of GMU fails to detect alarms from far end when receiving alarms from near end. After GMU reset RS and VC4 AIS mask is not set on in case of dTIM. CAS signaling does not go through GMU. CXU-M software version must be at least 2. The attribute should affect SNPO switch only after SF/SD switch. VC4 UNEQ. if GMU is a replacement unit. GMZ461 software version must be 1. CAS signaling does not work. It should be in No Request state.7. ES. If SNPO switch is revertive and waitToRestore state is on. Spontaneous messages do not work. 10004_22 © 2008 Tellabs. This may occur when signal quality is very bad.10 Version 1.GMU and GMU-A Units: GMZ460 Unit Software • • • • • • • • • • • • • • • VC4 SLM. It is not supported to replace GMU-A with GMU. however GMU can be replaced with GMU-A. Recovery does not work between GMUs when they are located in Tellabs 8150 basic node.8. GMU causes “Unit IA” fault in Tellabs 8160 A111 after power up (CRF ID 4004646). SXU-C software version must be at least 2. 34M SLM and 34M UNEQ alarm may exist without a reason. Group DEG does not work with SNC/N protection.3. switchStatus of protecting side is in wait-to-restore state. the received trace identifier J1 is masked to NULL.

QOS and QOSTR faults (CRF ID 4003428). X-bus slip counters of VC2s and VC12s are not supported. all read and write operations to interface loops are denied. With a certain configuration of VCs. The DEG fault exists shortly after an SSF fault of VC2/12. If vcGtp is set to lock state and one VC locking fails. A fault in Tx signal (RDI or enough FEBE). Node master clock “rank” is sometimes reported as illegal value “0” to neighbour nodes. Wrong fault classification of UNAVAIL. the DEG fault exists when an SLM fault of VC2/12 exists.GMU and GMU-A Units: GMZ460 Unit Software • • • • • • • • • • • Control channel data is not protected in VC4 POH bytes in case of MS 1+1 protection. Monitoring VCs of an SNC group do not count far end bit errors. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547). If a certain instance has an SSF alarm. Bugs • • • • • • • • • • • • • • • • • • Flash corruption problem (CRF ID 4005110). 10004_22 © 2008 Tellabs. the trace identifier of the corresponding instance is not masked to value null. XCG is not supported. If equipment loop is set and LOS is detected. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 136 . 522 bytes of a non-volatile setting are not sent to SCU. does not generate unavailability. this means that part of spontaneous event reporting configurations are not backed up. NNM1 alarms are seen as NNM2 alarms and NNM2 does not give alarms. VC4 LOM affects the performance data of VC4s. Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047. Advanced SNC configuration is not supported. SCU backuping is not supported. VC2/VC12 FEBEs are not counted when TU connection is bidirectional. NNM gives an alarm even if there is no corresponding control channel. If MS 1+1 protection is active. the GMU restart is failed after node reset. Configurable TIM consequent actions are not supported. In case of SNCP monitoring VCs have fault status PMA although it should be DMA. The supervisory unequipped feature of VC2 and VC12 is not supported. SSM enabling and disabling are not supported. After 1+1 multiplex section protection switch VC2/12s could have an SSF fault without a reason. all VCs are not returned to the unlock state. RS-AIS is still sent to the RX direction and SSF is set to the lower level instances. CR ID 200005303). In case of subnetwork connection protection auto switch does not clear the manual switch. It is possible to delete control channel related VC2/12 and cross-connections.

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

The base unit hardware version is 1.1 or higher. SCU-H (SCZ545) software version must be 1.8 or higher CCU (SCZ286) software version can be any version. This software is intended for GMU-A only (HW version 2.0. Tellabs 8150 basic. Software GMZ460 is for the main processor and software GMZ461 is for the ASIC processor.0 or higher.... (CR ID 300070271) Dependencies • • • • • • • • • • • • GMU-A hardware version must be 2.0 boards.7 or higher. SXU-V (SXZ630) software version must be 1. . Tellabs® 8100 Managed Access System Unit Software Version Dependencies 138 10004_22 © 2008 Tellabs.y of GMZ461 (where y=0.0 or higher. CXU-M (SXZ288) software version must be 2.). GMZ461 version 1.0 boards. 1.).6 or higher.1 Version 1.10 can be downloaded to GMU having the version 1. 2.0)..1 or higher.8 or higher.GMU and GMU-A Units: GMZ461 Unit Software 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.10. SXU-C (SXZ289) software version must be 2.11 NOTE: Do not download this software in GMU (HW version 1. SCU software version must be 8. XCG (SMZ538) software version must be 2.0). The base unit hardware version is 2.0.y of GMZ461 (where y=0.11 can be downloaded to GMU-A having the version 1. Enhancements and Fixed Bugs • Under certain circumstances SLM and UNEQ alarms might stay on even if the alarm cause has disappeared.5 or higher. GMX (GMZ544) software version can be any version.0 and DSU453 v1. Tellabs 8160 A111 and Tellabs 8170 cluster nodes. SCP (SCZ281) software version must be 3. GMU is composed of the GMU450 v1. 2. 12. SXU-A/B (SXZ282) software version must be 6. GMZ461 version 1. For the HW version 1. GMZ460 software version must be 1.0 and DSU453 v2. 1. use the SW version 1.1 or higher. GMU-A is composed of the GMU450 v1.7 or higher.

MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher. it is absolutely necessary to do "Remove from Inventory" for GMU-A.0 or higher. In the old interface module version B2-counting mode is always "Large Block" regardless of the NMS settings.11. Before inserting the GMU unit into a slot where GMU-A has been (in the inventory). 10004_22 © 2008 Tellabs. are supported only by GMU-A. Enhancements and Fixed Bugs • Under certain circumstances SLM and UNEQ alarms might stay on even if the alarm cause has disappeared. background block error (BBE) count is not according to the standard due to hardware restrictions. Restrictions • • • It is not supported to replace GMU-A with GMU.8. use the SW version 1.0).10 NOTE: Do not download this software in GMU-A (HW version 2. GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12.0. GMZ460 software version must be 1.1.0 do not support "Small block" B2-counting. In GMU-A a standard method can be used if BIP-1 based MS block error calculation is selected (CRF ID 4003017). This software is intended for GMU only (HW version 1. (CR ID 300070271) Dependencies • • • • GMU hardware version must be 1. Performance threshold values are not according to the EN 301 167 v.2 voice support. On MS layer. not by GMU.GMU and GMU-A Units: GMZ461 Unit Software • • • • GMU-A specific features. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 139 . however GMU can be replaced with GMU-A. • • Bugs • Tellabs 8100 control channel is not working in VC-2/VC-12 payload. For the HW version 2. CR ID 200005084) 12. 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.1 standard on multiplex section (MS) layer. CR ID 200004858). MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher.0). STM-1 interface modules older than version 2. P12s termination and V5.2 Version 1. CCU (SCZ286) software version can be any version. if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335.1.0. GMU-A hardware version must be 2. asynchronous mapping.

it is absolutely necessary to do "Remove from Inventory" for GMU-A.2 voice support. CR ID 200004858). On MS layer. SCU software version must be 8. CR ID 200005084). GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12.7 or higher.8 or higher.1 or higher. however GMU can be replaced with GMU-A. asynchronous mapping. but not by GMU. GMX (GMZ544) software version can be any version.1 do not initialize properly (CR ID 200015744) Tellabs® 8100 Managed Access System Unit Software Version Dependencies 140 10004_22 © 2008 Tellabs.6 or higher. P12s termination and V5.3 (CR ID 200005361) Old interface units with OTP v.5 or higher. MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher. . SXU-V (SXZ630) software version must be 1. Restrictions • • • It is not supported to replace GMU-A with GMU. SXU-A/B (SXZ282) software version must be 6. Performance threshold values are not according to the EN 301 167 v. SXU-C (SXZ289) software version must be 2. • Bugs • • • • Tellabs 8100 control channel is not working in VC-2/VC-12 payload. CXU-M (SXZ288) software version must be 2. background block error (BBE) count is not according to the standard due to hardware restrictions.1 or higher.1 standard on multiplex section (MS) layer.1. if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335. SCU-H (SCZ545) software version must be 1. In GMU-A a standard method can be used if BIP-1 based MS block error calculation is selected (CRF ID 4003017). Before inserting GMU unit into a slot where GMU-A has been (in the inventory).GMU and GMU-A Units: GMZ461 Unit Software • • • • • • • • • • • • • SCP (SCZ281) software version must be 3. VC-2 trunks work unreliably ( CR IDs 200016173. GMU-A specific features. MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher.1.1 or higher. are supported only by GMU-A. 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.7 or higher. XCG (SMZ538) software version must be 2. 200013679) SSM does not work with 34 M interface units with the OTP v.

MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher. GMZ460 software version must be 1.1 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 141 .3 Version 1. • • Dependencies • • • • • • • • • • • • • • • • GMU-A hardware version must be 2.0).1 or higher.8 or higher.8.9 NOTE: Do not download this software in GMU (HW version 1.GMU and GMU-A Units: GMZ461 Unit Software 12.7 or higher. An initialization error with old interface units with OTP ASIC version 1 has been fixed.0). CXU-M (SXZ288) software version must be 2. GMU-A specific features. MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher. SXU-V (SXZ630) software version must be 1. 10004_22 © 2008 Tellabs. XCG (SMZ538) software version must be 2.2 voice support. This software is intended for GMU-A only (HW version 2.0 (CR ID 200015744). Enhancements and Fixed Bugs (compared with version x. This bug does not concern GDH456 modules that have been manufactured before 06/2004 (CR ID 200005361). For HW version 1.1 or higher. SXU-C (SXZ289) software version must be 2.7 or higher.6 or higher. P12s termination and V5.1) • A bug in the version 1.0.0 or higher. Now it is possible to use all old hardware modules with GMU-A base unit HW version 2.8 that caused bit errors and MAIS alarms on VC2 links with GMUA has been fixed (CR IDs 200016173 and 200013679). SCU-H (SCZ545) software version must be 1. A bug with SSM message handling in 34 M interfaces (GDH456) has been fixed. but not by GMU. SCP (SCZ281) software version must be 3. asynchronous mapping.5 or higher. SXU-A/B (SXZ282) software version must be 6. GMX (GMZ544) software version can be any version. use SW version 1. SCU software version must be 8. GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12. are supported only by GMU-A.8 or higher CCU (SCZ286) software version can be any version.

1.1 standard on multiplex section (MS) layer. STM-1 interface modules older than version 2. 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. 200011641). Because of a traffic affecting bug in GMZ461 1. background block error (BBE) count is not according to the standard due to hardware restrictions. 'uneven' X-bus distribution is used however. Applies to GMU-A only: now it is not possible to cause illegal VC-12-mc configuration by using Tellabs 8100 network manager’s Node Manager copy/paste from a single VC12 (asynchronous mode) into VC12-mc/VC-12 (CR ID 200011098). it is absolutely necessary to do "Remove from Inventory" for GMU-A.0).0 do not support "Small block" B2-counting. use version 1.1. however GMU can be replaced with GMU-A. 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).GMU and GMU-A Units: GMZ461 Unit Software Restrictions • • • It is not supported to replace GMU-A with GMU. SYN-34-E interface module internal test does not fail unintentionally and no fault ‘Initialization error (GMZ461)’ is produced anymore (CR ID 200004414.4 Version 1. • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 142 10004_22 © 2008 Tellabs. CR ID 200005303. CR ID 200005084) Under certain circumstances SLM and UNEQ alarms might stay on even if alarm cause has disappeared. Enhancements and Fixed Bugs • Applies to GMU-A only: when X-bus distribution is set to 'even' while P12s signal mapping mode is 'asynchronous'. . (CR ID 300070271) 12. Performance threshold values are not according to the EN 301 167 v.8 NOTE: Do not use this software in GMU-A (HW version 2. which caused traffic degradation in GMU (CR ID 200007236). • • Bugs • • Tellabs 8100 control channel is not working in VC-2/VC-12 payload. Fixed corruption of Rx buffer centring. Applies to GMU-A only: SYN-34-E interface module works also for GMU-A (CR ID 11636).8. if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335. Before inserting GMU unit into a slot where GMU-A has been (in the inventory). (Technical note ID SOL2005).9 in GMU-A instead. In GMU-A a standard method can be used if BIP-1 based MS block error calculation is selected (CRF ID 4003017). 200011635. CR ID 200004858). 200011636). On MS layer. In old interface module version B2-counting mode is always "Large Block" regardless of NMS settings. Fixed wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047.

In GMU-A a standard method can be used if BIP-1 based MS block error calculation is selected (CRF ID 4003017).7 or higher. CR ID 200004858).1. background block error (BBE) count is not according to the standard due to hardware restrictions. 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. MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher. XCG (SMZ538) software version must be 2. SXU-A/B (SXZ282) software version must be 6.1 or higher.1 or higher.1 or higher. P12s termination and V5. SXU-C (SXZ289) software version must be 2.2 voice support. GMZ460 software version must be 1. Restrictions • • • It is not supported to replace GMU-A with GMU. GMU-A hardware version must be 2. it is absolutely necessary to do "Remove from Inventory" for GMU-A.8 or higher. On MS layer. asynchronous mapping.6 or higher.5 or higher.0 or higher. CCU (SCZ286) software version can be any version.GMU and GMU-A Units: GMZ461 Unit Software Dependencies • • • • • • • • • • • • • • • • • GMU hardware version must be 1. Before inserting GMU unit into a slot where GMU-A has been (in the inventory). Tellabs® 8100 Managed Access System Unit Software Version Dependencies 143 .8.1 standard on multiplex section (MS) layer. but not by GMU. are supported only by GMU-A. Performance threshold values are not according to the EN 301 167 v. MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher. SXU-V (SXZ630) software version must be 1. GMU-A specific features. GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12. CXU-M (SXZ288) software version must be 2.0. however GMU can be replaced with GMU-A. • 10004_22 © 2008 Tellabs.1.7 or higher. GMX (GMZ544) software version can be any version. SCP (SCZ281) software version must be 3. SCU-H (SCZ545) software version must be 1. SCU software version must be 8.

NOTE: Do not download this software in GMU-A. SCP (SCZ281) software version must be 3.0.7.5 or higher. SXU-V (SXZ630) software version must be 1.179.1 or higher.1 do not initialize properly (CR ID 200015744) Under certain circumstances SLM and UNEQ alarms might stay on even if alarm cause has disappeared. VC-2 trunks work unreliably ( CR IDs 200016173. CCU (SCZ286) software version can be any version. which caused traffic degradation (CR ID 200007236). Dependencies • • • • • • • • • • • • GMU hardware version must be 1. GMX (GMZ544) software version can be any version. CXU-M (SXZ288) software version must be 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 144 10004_22 © 2008 Tellabs. if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335.1 or higher. (Technical note ID SOL2005).8 or higher. 200013679) SSM does not work with 34 M interface units with the OTP v.6 or higher. SCU software version must be 8.GMU and GMU-A Units: GMZ461 Unit Software Bugs • • • • • Tellabs 8100 control channel is not working in VC-2/VC-12 payload. (CR ID 300070271) 12.5 Version 1. SXU-C (SXZ289) software version must be 2. CR ID 200005084).7 or higher. .179 This is a non-production version based on version 1. SCU-H (SCZ545) software version must be 1.7 or higher.3 (CR ID 200005361) Old interface units with OTP v. SXU-A/B (SXZ282) software version must be 6. GMZ460 software version must be 1. XCG (SMZ538) software version must be 2. This software is intended for GMU only.1 or higher. Enhancements and Fixed Bugs • Fixed corruption of Rx buffer centring.

1 do not initialize properly (CR ID 200015744) 12.3 (CR ID 200005361) Old interface units with OTP v. also P12 layer fault events are reported. If 15-minute performance counter has other value than zero. BIP-1/BIP-24 block size based MS operation in GMU-A (CRF ID 4003330. Fault reporting bug fixed. On MS layer.1. P12 layer fault reporting enhanced. 10004_22 © 2008 Tellabs. CR ID 200005406). SSM does not work with 34 M interface units with the OTP v. Fix in node master clock “rank”: illegal value 0 was sometimes reported to neighbour nodes. Performance threshold values are not according to the EN 301 167 v. CR ID 200005084). G. Fixed flash corruption problem (CRF ID 4005110). if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335. This software is intended for GMU-A only. Bugs • • • Tellabs 8100 control channel is not working in VC-2/VC-12 payload. Before inserting GMU unit into a slot where GMU-A has been (in the inventory). background block error (BBE) count is not according to the standard due to hardware restrictions (CRF ID 4003017).1 standard on multiplex section (MS) layer. If fault event reporting is defined for a VC-12. This software is intended for GMU only. some faults were never reported (CRF ID 4005206. QOS and QOSTR faults (CRF ID 4003428). Tellabs® 8100 Managed Access System Unit Software Version Dependencies 145 .826 performance monitoring data is collected also when TU cross-connection is missing (CRF ID 4004714). it is absolutely necessary to do "Remove from Inventory" for GMU-A.7 NOTE: Do not download this software in GMU. however GMU can be replaced with GMU-A. Enhancements and Fixed Bugs • • • • • • • • • • • Enhancement in performance data collection. Extended production test support (CRF ID 4004928). Fixed fault classification of UNAVAIL. a delta-type alarm is set active (CRF ID 4003054). CR ID 200004858). Fixed incorrect MLOF alarm with asynchronous SNC/N protected VC-12 with Channel Associated Signalling and P12s termination (CR ID 200005740).1. It is not supported to replace GMU-A with GMU.GMU and GMU-A Units: GMZ461 Unit Software Restrictions • • • • Do not download this software version in GMU-A.6 Version 1.

In GMU-A a standard method can be used if BIP-1 based MS block error calculation is selected (CRF ID 4003017).7. 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. Performance threshold values are not according to the EN 301 167 v.1 or higher.1. • Bugs • • • SYN-34-E interface module does not work reliably (CR ID 200011636). 200011635. however GMU can be replaced with GMU-A. SXU-A/B (SXZ282) software version must be 6. background block error (BBE) count is not according to the standard due to hardware restrictions. SYN-34-E interface module internal test fails unintentionally and produces fault ‘Initialization error (GMZ461)’ (CR ID 200004414. Because of a bug in LTA ASIC. On MS layer.1 or higher.8 or higher.6 or higher. SXU-C (SXZ289) software version must be 2.1. 200011636). CXU-M (SXZ288) software version must be 2. Before inserting GMU unit into a slot where GMU-A has been (in the inventory). SXU-V (SXZ630) software version must be 1. CR ID 200004858).1 or higher. GMZ460 software version must be 1. SCP (SCZ281) software version must be 3. It is possible to cause illegal VC-12-mc configuration by using Tellabs 8100 network manager’s Node Manager copy/paste from a single VC12 (asynchronous mode) into VC12mc/VC-12 (CR ID 200011098). MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher. XCG (SMZ538) software version must be 2.7 or higher. SCU-H (SCZ545) software version must be 1. GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12. CCU (SCZ286) software version can be any version.1 standard on multiplex section (MS) layer.0 or higher. 10004_22 © 2008 Tellabs. it is absolutely necessary to do "Remove from Inventory" for GMU-A. 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). SCU software version must be 8. • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 146 . Restrictions • • • It is not supported to replace GMU-A with GMU. GMX (GMZ544) software version can be any version.5 or higher.7 or higher.GMU and GMU-A Units: GMZ461 Unit Software Dependencies • • • • • • • • • • • • • • • GMU-A hardware version must be 2. MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher.

V5. Enhancements and Fixed Bugs • • • • • Asynchronous 2 Mbit/s signal mapping.0 or higher. CXU-M (SXZ288) software version must be 2. i. SCU software version must be 8. if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335.704) termination. SCP (SCZ281) software version must be 3. GMX (GMZ544) software version can be any version. SS bit values in AU4 pointer do not have to be ‘10’ anymore. Transmitted NU2 byte in STM1 RSOH is balanced.e. XCG (SMZ538) software version must be 2. GMU does not cause “Unit IA” fault in Tellabs 8160 A111 after power up (CRF ID 4004646). ES. P12s (G.6 NOTE: Do not download this software in GMU. Therefore. this software version can be used to connect GMU-A to SONET equipment (CRF ID 4004547).3 (CR ID 200005361) Old interface units with OTP v.6 or higher.1 or higher.1 do not initialize properly (CR ID 200015744) 12.6. Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047. SCU-H (SCZ545) software version must be 1.7 or higher. The byte can also be set with Tellabs 8100 Network Manager (interface window/overhead bytes) (CRF ID 4003371). SXU-C (SXZ289) software version must be 2. SSM does not work with 34 M interface units with the OTP v.1 or higher. 10004_22 © 2008 Tellabs. CCU (SCZ286) software version can be any version.1 or higher.2 voice interface support in Tellabs 8150 basic node. Performance monitoring thresholds lower BBE.7 Version 1. This software is intended for GMU-A only.5 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 147 . CR ID 200005303). SXU-A/B (SXZ282) software version must be 6. SXU-V (SXZ630) software version must be 1.7 or higher. GMZ460 software version must be 1.8 or higher. it has equal number of ‘0’ and ‘1’ bits (value 0xAA). CR ID 200005084).GMU and GMU-A Units: GMZ461 Unit Software • • • • Tellabs 8100 control channel is not working in VC-2/VC-12 payload. • • Dependencies • • • • • • • • • • • • GMU-A hardware version must be 2. SES and secSesThreshold are compared correctly (CRF ID 4004442).

On MS layer. Because of a bug in LTA ASIC. 200011635. GMU-A (and GMU) supports GMU functionality in MartisDXX Manager Releases 11 and 12. VC-4.1. It is possible to cause illegal VC-12-mc configuration by using Tellabs 8100 network manager’s Node Manager copy/paste from a single VC12 (asynchronous mode) into VC12mc/VC-12 (CR ID 200011098). Performance threshold values are not according to the EN 301 167 v.1 do not initialize properly (CR ID 200015744) • • • • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 148 10004_22 © 2008 Tellabs. execution of “Factory settings” is required for this feature (CRF ID 4003017). CR ID 200005406).1. some faults are never reported (CRF ID 4005206. VC-12) are according to the standard. if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335. Other threshold values (ES and SES) are according to the standard. .3 (CR ID 200005361) Old interface units with OTP v. Restrictions • • It is not supported to replace GMU-A with GMU. Threshold values on other layers (RS. Wrong fault classification of UNAVAIL. However. Tellabs 8100 control channel is not working in VC-2/VC-12 payload. background block error (BBE) count is not according to the standard due to hardware restrictions. CR ID 200005406 (CR ID 200004414. SSM does not work with 34 M interface units with the OTP v. 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). Note: if software is downloaded to existing GMU. Bugs • • SYN-34-E interface module does not work reliably (CR ID 200011636). this fault is not shown by Tellabs 8100 network manager because of fault reporting bug CRF ID 4005206. however GMU can be replaced with GMU-A. CR ID 200005303). QOS and QOSTR faults (CRF ID 4003428).GMU and GMU-A Units: GMZ461 Unit Software • • • MartisDXX Manager supports GMU-A functionality in Release 12A Service Pack 2 or higher. Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047. CR ID 200005084).1 standard on multiplex section (MS) layer. VC-2. Incorrect MLOF alarm is reported with asynchronous SNC/N protected VC-12 with Channel Associated Signalling and P12s termination (CR ID 200005740). 200011636). Fault reporting bug. Node master clock “rank” is sometimes reported as illegal value “0” to neighbour nodes. Flash corruption problem (CRF ID 4005110). MartisDXX Manager supports asynchronous monitoring VC-12 (and SNC/N protected asynchronous VC-12) in Release 12A Service Pack 3 or higher. SYN-34-E interface module internal test fails unintentionally and produces fault ‘Initialization error (GMZ461)’.

102 This is a non-production version based on version 1.1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 149 . CXU-M software version must be at least 2. 10004_22 © 2008 Tellabs. this may cause inconsistency between database and hardware.0 and later.4 and later of GMU support advanced SNC group configuration but in MartisDXX Manager NMS this feature is supported in Release 10.8.8 Version 1. Transmitted NU2 byte in STM1 RSOH is balanced. Versions 1. Therefore. The user can minimize this problem by configuring monitoring TTPs of an SNC group to have the same values as the terminating TTP. however GMU can be replaced with GMU-A. SXU-A/B software version must be at least 6. SXU-C software version must be at least 2.7. If SNC groups are configured by earlier NMS versions.102 Restrictions • • • Software can not be downloaded to GMU-A. SCP software version must be at least 3.GMU and GMU-A Units: GMZ461 Unit Software 12. This software is intended for GMU only. The byte can also be set with Tellabs 8100 Network Manager (interface window/overhead bytes) (CRF ID 4003371).5. SS bit values in AU4 pointer do not have to be ‘10’ anymore. this software version can be used to connect GMU to SONET equipment (CRF ID 4004547). NOTE: Do not download this software in GMU-A.1. XCG software version must be at least 2. It is not supported to replace GMU-A with GMU. Dependencies • • • • • • • SCU software version must be at least 8. Enhancements and Fixed Bugs • • • GMU does not cause “Unit IA” fault in Tellabs 8160 A111 after power up (CRF ID 4004646). it has equal number of ‘0’ and ‘1’ bits (value 0xAA).e.7. GMZ460 software version must be 1.5. i.

Versions 1. Flash corruption problem (CRF ID 4005110).1. Performance monitoring thresholds lower BBE. XCG software version must be at least 2.5. It is not supported to replace GMU-A with GMU. if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335. CR ID 200005303). GMZ460 software version must be 1. SES and secSesThreshold are compared incorrectly (CRF ID 4004442). This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547). however GMU can be replaced with GMU-A. Node master clock “rank” is sometimes reported as illegal value “0” to neighbour nodes.0 and later. CXU-M software version must be at least 2.4 and later of GMU support advanced SNC group configuration but in MartisDXX Manager NMS this feature is supported in Release 10.1. this may cause inconsistency between database and hardware.5 NOTE: Do not download this software in GMU-A. SXU-C software version must be at least 2. SXU-A/B software version must be at least 6. Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047. This software is intended for GMU only.7.8. SCP software version must be at least 3.1 do not initialize properly (CR ID 200015744) 12. The user can minimize this problem by configuring monitoring TTPs of an SNC group to have the same values as the terminating TTP.7. Wrong fault classification of UNAVAIL.GMU and GMU-A Units: GMZ461 Unit Software Bugs • • • • • • • • Tellabs 8100 control channel is not working in VC-2/VC-12 payload. SSM does not with 34 M interface units with the OTP v. . Dependencies • • • • • • • SCU software version must be at least 8. ES. QOS and QOSTR faults (CRF ID 4003428). Restrictions • • • Software can not be downloaded to GMU-A. If SNC groups are configured by earlier NMS versions.5.9 Version 1. • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 150 10004_22 © 2008 Tellabs.3 (CR ID 200005361) Old interface units with OTP v. CR ID 200005084).

XCG software version must be at least 2.10 Version 1. CXU-M software version must be at least 2.4 of GMU supports advanced SNC group configuration but in MartisDXX Manager NMS this feature is supported in Release 10. This software is intended for GMU only. GMZ460 software version must be 1. CR ID 200005084).3 (CR ID 200005361) Old interface units with OTP v.1. SES and secSesThreshold are compared incorrectly (CRF ID 4004442). It is not supported to replace GMU-A with GMU. CR ID 200005303). GMU causes “Unit IA” fault in Tellabs 8160 A111 after power up (CRF ID 4004646).GMU and GMU-A Units: GMZ461 Unit Software Bugs • • • • • • • • • Tellabs 8100 control channel is not working in VC-2/VC-12 payload. Version 1. Wrong fault classification of UNAVAIL. SSM does not with 34 M interface units with the OTP v.4. SXU-C software version must be at least 2. SCP software version must be at least 3. Restrictions • • • • Software can not be downloaded to GMU-A. however GMU can be replaced with GMU-A. If SNC groups are configured by earlier NMS versions.4.7.8. • 10004_22 © 2008 Tellabs. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 151 . Control channel in VC payload is not supported.7.1 do not initialize properly (CR ID 200015744) 12. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547). Performance monitoring thresholds lower BBE.4 NOTE: Do not download this software in GMU-A. Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047. this may cause inconsistency between database and hardware.1. SXU-A/B software version must be at least 6. The user can minimize this problem by configuring monitoring TTPs of an SNC group to have the same values as the terminating TTP. Flash corruption problem (CRF ID 4005110). Node master clock “rank” is sometimes reported as illegal value “0” to neighbour nodes. ES. if CAS is enabled for the VC-2/VC-12 (CRF ID 4005335.0 and later. QOS and QOSTR faults (CRF ID 4003428). Dependencies • • • • • • • SCU software version must be at least 8.

Performance monitoring thresholds lower BBE. Spontaneous messages do not work. Spontaneous messages of TU12Ctps do not work.3 (CR ID 200005361) Old interface units with OTP v.3. CAS signaling does not work.7.0. Group DEG does not work with SNC/N protection. Dependencies • • • • • • SCU software version must be at least 8. ES. signal degrade seconds. GMU causes “Unit IA” fault in Tellabs 8160 A111 after power up (CRF ID 4004646).3.1 do not initialize properly (CR ID 200015744) 12. SCP software version must be at least 3. Node master clock “rank” is sometimes reported as illegal value “0” to neighbour nodes. SSM does not with 34 M interface units with the OTP v. CAS signaling does not go through GMU. Expected TI. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 152 10004_22 © 2008 Tellabs. CXU-M software version must be at least 2.7. . if GMU is moved from Tellabs 8150 basic node to Tellabs 8170 cluster node or vice versa. CAS. 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. Wrong fault classification of UNAVAIL. This software is intended for GMU only.GMU and GMU-A Units: GMZ461 Unit Software Bugs • • • • • • • • • • • • • • • • Flash corruption problem (CRF ID 4005110).11 Version 1. SXU-C software version must be at least 2. QOS and QOSTR faults (CRF ID 4003428). Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047. GMZ460 software version must be 1. SES and secSesThreshold are compared incorrectly (CRF ID 4004442). if GMU is a replacement unit. SXU-A/B software version must be at least 6. CR ID 200005303).8.3 NOTE: Do not download this software in GMU-A. signal degrade threshold and TIMaAisenabled attributes cannot be changed in VCgtp if SNC/I protection is used.

CR ID 200005303). Monitoring VCs of SNC group do not count far end bit errors. TU12-LOMs exist for a short time. SSM enabling and disabling are not supported. however GMU can be replaced with GMU-A. VC4 LOM affects the performance data of VC4s. If MS 1+1 protection is active. SCU backuping is not supported. all read and write operations to interface loops are denied. If MS-AIS is received. The attribute should affect SNPO switch only after SF/SD switch. VC4 SLM. The supervisory unequipped feature of VC2 and VC12 is not supported. This may occur when signal quality is very bad. 34M SLM and 34M UNEQ alarms may exist without a reason. Advanced SNC configuration is not supported. Ps34M performance thresholds are seen as MS thresholds if SYN-34-E interface module is configured. Bugs • • • • • • • • • • • • • • • • • Flash corruption problem (CRF ID 4005110). VC4 UNEQ. XCG is not supported. If SNPO switch is revertive and waitToRestore state is on. NNM gives an alarm even if there is no corresponding control channel. SSF should be set too in MSTTPBid. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 153 10004_22 © 2008 Tellabs. It is not supported to replace GMU-A with GMU. QOS and QOSTR faults (CRF ID 4003428). Configurable TIM consequent actions are not supported. X-bus slip counters of VC2s and VC12s are not supported. Node master clock “rank” is sometimes reported as illegal value “0” to neighbour nodes. the received trace identifier J1 is masked to NULL. Control channel in VC payload is not supported. In case of SNCP monitoring VCs have fault status PMA although it should be DMA. Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047. switchStatus of protecting side is in wait-to-restore state. . If 34M-PsTTP alarm is activated and fault declare value is between 1-9. It should be in No Request state. Attribute waitToRestoreTime affects SNPO switch even if there has been manual switch. Wrong fault classification of UNAVAIL. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547). If VC4 TIM or LOM is active. NNM1 alarms are seen as NNM2 alarms and NNM2 does not give alarms.GMU and GMU-A Units: GMZ461 Unit Software Restrictions • • • • • • • • • • • Software can not be downloaded to GMU-A.

X-bus slip counters of VC2s and VC12s are not supported. SXU-A/B software version must be at least 6. . Spontaneous messages do not work. SSM does not with 34 M interface units with the OTP v. ES. GMU causes “Unit IA” fault in Tellabs 8160 A111 after power up (CRF ID 4004646). SXU-C software version must be at least 2.7.12 Version 1. Spontaneous messages of TU12Ctps do not work. SCP software version must be at least 3.3.8.3 (CR ID 200005361) Old interface units with OTP v. The AIS fault of SYN-34-E interface module does not work. CAS signaling does not work. if GMU is moved from Tellabs 8150 basic node to Tellabs 8170 cluster node or vice versa. The SYN-34-E interface module is not supported. SCU backuping is not supported. This software is intended for GMU only. GMZ460 software version must be 1. It is not supported to replace GMU-A with GMU. however GMU can be replaced with GMU-A.GMU and GMU-A Units: GMZ461 Unit Software • • • • • • • • • • • • After GMU reset RS and VC4 AIS mask is not set on in case of dTIM.2 NOTE: Do not download this software in GMU-A. if GMU is a replacement unit. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 154 10004_22 © 2008 Tellabs. CAS signaling does not go through GMU.2. Dependencies • • • • • • SCU software version must be at least 8.7. Group DEG does not work with SNC/N protection. CXU-M software version must be at least 2. Restrictions • • • • • • • Software can not be downloaded to GMU-A. The performance management system of GMU fails to detect alarms from far end when receiving alarms from near end. Performance monitoring thresholds lower BBE. Control channel in VC payload is not supported.0. SES and secSesThreshold are compared incorrectly (CRF ID 4004442). Recovery does not work between GMUs when they are located in Tellabs 8150 basic node. Advanced SNC configuration is not supported.1 do not initialize properly (CR ID 200015744) 12.

NNM1 alarms are seen as NNM2 alarms and NNM2 does not give alarms. Wrong alarm handling in bits C2 (VC-4) and V5 (VC-2/VC-12) (CRF ID 4005047. It should be in No Request state. 34M SLM and 34M UNEQ alarm may exist without a reason. If VC4 TIM or LOM is active. Wrong fault classification of UNAVAIL. If MS-AIS is received. This software version can not be used to connect GMU to SONET equipment (CRF ID 4004547). If SNPO switch is revertive and waitToRestore state is on. all read and write operations to interface loops are denied. Monitoring VCs of an SNC group do not count far end bit errors. Configurable TIM consequent actions are not supported. If an equipment loop is set and LOS is detected. VC4 UNEQ. After GMU reset RS and VC4 AIS mask is not set on in case of dTIM. SSF should be set too in MSTTPBid. DEG fault exists when an SLM fault of VC2/12 exists. In case of SNCP monitoring VCs have fault status PMA although it should be DMA. switchStatus of protecting side is in wait-to-restore state. VC4 LOM affects the performance data of VC4s. Bugs • • • • • • • • • • • • • • • • • • • • • • Flash corruption problem (CRF ID 4005110). This may occur when signal quality is very bad. If vcGtp is set to lock state and one VC locking fails. In case of subnetwork connection protection auto switch does not clear manual switch. VC4 SLM. The attribute should affect SNPO switch only after SF/SD switch. the received trace identifier J1 is masked to NULL. QOS and QOSTR faults (CRF ID 4003428). The supervisory unequipped feature of VC2 and VC12 is not supported. 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. DEG fault exists shortly after an SSF fault of VC2/12.GMU and GMU-A Units: GMZ461 Unit Software • • • • • XCG is not supported. If MS 1+1 protection is active. all VCs are not returned to the unlock state. 10004_22 © 2008 Tellabs. After 1+1 multiplex section protection switch VC2/12s could have an SSF fault without a reason. NNM gives an alarm even if there is no corresponding control channel. Attribute waitToRestoreTime affects SNPO switch even if there has been manual switch. CR ID 200005303). SSM enabling and disabling are not supported. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 155 . RS-AIS is still sent to the RX direction and SSF is set to the lower level instances. this means that part of spontaneous event reporting configurations are not backed up.

1 NOTE: Do not download this software in GMU-A.0. ES. SES and secSesThreshold are compared incorrectly (CRF ID 4004442). SSM does not with 34 M interface units with the OTP v. the trace identifier of the corresponding instance is not masked to value null.1 do not initialize properly (CR ID 200015744) 12. Recovery does not work between GMUs when they are located in Tellabs 8150 basic node. SXU-A/B software version must be at least 6.7. however GMU can be replaced with GMU-A. Control channel in VC payload is not supported. SCP software version must be at least 3. AIS fault of SYN-34-E interface module does not work. if GMU is moved from Tellabs 8150 basic node to Tellabs 8170 cluster node or vice versa. SXU-C software version must be at least 2.13 Version 1. Dependencies • • • • • • SCU software version must be at least 8.7. if GMU is a replacement unit. Advanced SNC configuration is not supported. Performance monitoring thresholds lower BBE. Control channel data is not protected in VC4 POH bytes in case of MS 1+1 protection. Restrictions • • • • • • • • Software can not be downloaded to GMU-A.3. . GMZ460 software version must be 1.1. CAS signaling does not work. Group DEG does not work with SNC/N protection. Spontaneous messages of TU12Ctps do not work. GMU causes “Unit IA” fault in Tellabs 8160 A111 after power up (CRF ID 4004646).8.GMU and GMU-A Units: GMZ461 Unit Software • • • • • • • • • • • The performance management system of GMU fails to detect alarms from far end when receiving alarms from near end. CAS signaling does not go through GMU. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 156 10004_22 © 2008 Tellabs. CXU-M software version must be at least 2. It is possible to delete control channel related VC2/12 and cross-connections. If a certain instance has an SSF alarm. Spontaneous messages do not work.3 (CR ID 200005361) Old interface units with OTP v. This software is intended for GMU only. It is not supported to replace GMU-A with GMU. The SYN-34-E interface module is not supported.

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

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

In the case GMX is protected. 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). downloadable code 2. MartisDXX Manager support for this unit without SBU functionality is available in Release 10. LOF fault is not reported if P12s AIS reporting is disabled (CR ID 300021812).b and the downloadable version is c. SCU-H (SCZ545) software version must be 1. except during the middle phase of the software upgrade process.d.11 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). both GMXs must have an interface module.1A Service Pack 3 or higher. If GMX is protected.6 Enhancements and Fixed Bugs (compared with version 4.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. Dependencies • When GMXs are equipment protected (both GMXs installed) and synchronization input is taken from the STM-1 interface.5 or higher. even if the STM-1 interface in the protecting GMX is not used.24) • • • • 1+1 protection switch does not cause fake SSF alarms on P12s (CR ID 300070961). the software versions of both GMXs must be the same. If the boot version is a. However if the hardware versions are different the software version must be the functionally equal version mentioned above. The major version number indicates if the boot code is compatible with the downloadable code.1 Version 4. • • • • • • • • • 10004_22 © 2008 Tellabs. Flash list record status bit handling has been fixed (CR ID 300092117).4 / functionally same as 3. GMX hardware version must be 3. 13. they are compatible if and only if a = c. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 159 . For example. boot software and downloadable software.6 or higher.0 or higher. Two software products are needed for the GMX unit. STM-1 loop timeout is not truncated in an STM-1 interface #2 (CR ID 300021040). In the case GMX is not protected the node works correctly only if SCU-H has SW version 1. Flash checksum calculation works correctly only if SCU-H has SW version 1. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher.0 cannot be downloaded if boot code version is 1.5.

Monitoring VC-12/2s in GMX use the same TU-bus internal resources as VC-12s in SBU. 13. #VC2M = number of monitoring VC-2s. when X-bus-AIS (=B2-AIS) is detected.3 / functionally same as 3. Control channels in the first octet of VC-12 payload are not supported. Control channels in VC-4 POH with MS 1+1 protection are not supported. 63 SNC/N protected GMX’s VC-12s or. Dual ended (bidirectional) MS 1+1 is not supported. #VC12M = number of monitoring VC-12s. a combination of the alternatives above so that 2*#E1 + #VC12M + 3*#VC2M ≤ 126 and #VC12T + 3*#VC2T ≤ 63. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. The total capacity for VC-12/2s is (in the case of two protected GMXs): • • • • • 63 VC-12s of SBU + 63 GMX’s VC-12s or. Bugs • No known bugs.22) • SLM and UNEQ alarms will get cleared after the alarm cause has disappeared (CR ID 300074269). It means that 62 VC-12s may have CAS capacity. signal label values are not copied automatically from the terminating VCs to the monitoring VCs. . Tx AIS is not generated in G.3 Version 4. where #E1 = number of VC-12s of SBU.2 Version 4. #VC12T = number of terminating VC-12s and #VC2T = number of terminating VC-2s. • • • • • • • One timeslot (64 kbit) of GMXBUS1 cannot be allocated. 31 VC-12s may have CAS capacity inside one GMXBUS.704 termination.5 This is an unofficial test version. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 160 10004_22 © 2008 Tellabs. 20 SNC/N protected GMX’s VC-2s + 3 SNC/N protected GMX’s VC-12s or. In the case of SNC/N protection. 31 SNC/N protected VC-12s of SBU + 63 GMX’s VC-12s or.4 Enhancements and Fixed Bugs (compared with version 4. 13.GMX Unit: GMZ544 Unit Software Restrictions • • The control channel in the R0 byte of VC-12 is forbidden because of unreliable HW functionality.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies 161 . In the case GMX is protected.6 or higher. 20 SNC/N protected GMX’s VC-2s + 3 SNC/N protected GMX’s VC-12s or. • • • Dependencies • When GMXs are equipment protected (both GMXs installed) and synchronization input is taken from the STM-1 interface. MartisDXX Manager support for this unit without SBU functionality is available in Release 10. The X-bus object attribute in GMX uses a correct macro (CR ID 300074470). 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). where #E1 = number of VC-12s of SBU.11 or higher. #VC12M = number of monitoring VC-12s. 31 SNC/N protected VC-12s of SBU + 63 GMX’s VC-12s or. 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). Message deleter deactivation added to all possible error branches (CR ID 300069654). a combination of the alternatives above so that 2*#E1 + #VC12M + 3*#VC2M ≤ 126 and #VC12T + 3*#VC2T ≤ 63. The total capacity for VC-12/2s is (in the case of two protected GMXs): • • • • • 63 VC-12s of SBU + 63 GMX’s VC-12s or. both GMXs must have an interface module. 63 SNC/N protected GMX’s VC-12s or. However if the hardware versions are different the software version must be the functionally equal version mentioned above.1A Service Pack 3 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1.GMX Unit: GMZ544 Unit Software • The option to select a Fallback List Warning alarm in GMX is now using correct polarity. If GMX is protected. • • • • • • • • • 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 software versions of both GMXs must be the same. GMX hardware version must be 3.0 or higher. SCU-H (SCZ545) software version must be 1. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. #VC2M = number of monitoring VC-2s. except during the middle phase of the software upgrade process. Trunk swap operates also when swap operations are done between the X-buses (CR ID 300073896). even if the STM-1 interface in the protecting GMX is not used. 10004_22 © 2008 Tellabs. Flash checksum calculation works correctly only if SCU-H has SW version 1. Fallback List Warning alarm generation is enabled when the Use quality levels option is disabled (CR ID 300067521).5 or higher.

both GMXs must have an interface module. (CR ID 300046898) EEIO (Eeprom IO) module semafore problem has been fixed.704 termination. when X-bus-AIS (=B2-AIS) is detected. even if the STM-1 interface in the protecting GMX is not used. It means that 62 VC-12s may have CAS capacity. (CR ID 300047579) The MS protection switching time measurement does not any more use the internal timer in OTP ASIC but only QP timer. (CR ID 300027029) EEPROM hardware read access is supported. The fault Fallback list warning is activated if QL (Master clock quality level) use is enabled. • • • • • • • One timeslot (64 kbit) of GMXBUS1 cannot be allocated. The 50ms switch time requirement measuring has been fixed. signal label values are not copied automatically from the terminating VCs to the monitoring VCs. The fault Initialization error GMX A/B is activated if FPGA init has eventually not been successful. Dual ended (bidirectional) MS 1+1 is not supported. (CR ID 300041527). Control channels in the first octet of VC-12 payload are not supported.2 / functionally same as 3. . (CR ID 300035385) FLS (Flash settings) module semafore problem 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. Control channels in VC-4 POH with MS 1+1 protection are not supported. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. Fault activation is a customer requirement.3 Enhancements and Fixed Bugs (compared with version 4. In the case of SNC/N protection.21) • XSC FPGA init sequence has been modified to support init retries during unit initialization if FPGA initialization has been unsuccessful. (CR ID 300038153) MC RAI (Master Clock Remote Alarm Indication) problem has been fixed. This will reduce the probability of FPGA remaining in an uninitialized state. (CR ID 300038862) The fault Reconfiguring X-Connect Database does not any more activate unnecessarily in unprotected node after inventory create operation.GMX Unit: GMZ544 Unit Software #VC12T = number of terminating VC-12s and #VC2T = number of terminating VC-2s. The ASIC timer has shown to be unreliable in some units. Bugs • No known bugs. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 162 10004_22 © 2008 Tellabs. Tx AIS is not generated in G. 31 VC-12s may have CAS capacity inside one GMXBUS.4 Version 4. 13.

1A Service Pack 3 or higher. In the case GMX is protected. It means that 62 VC-12s may have CAS capacity. when X-bus-AIS (=B2-AIS) is detected.6 or higher. Monitoring VC-12/2s in GMX use the same TU-bus internal resources as VC-12s in SBU.5 or higher. • • • • • • • One timeslot (64 kbit) of GMXBUS1 cannot be allocated. • • • • • • • Restrictions • • The control channel in the R0 byte of VC-12 is forbidden because of unreliable HW functionality. Control channels in the first octet of VC-12 payload are not supported. where #E1 = number of VC-12s of SBU. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. 20 SNC/N protected GMX’s VC-2s + 3 SNC/N protected GMX’s VC-12s or. In the case of SNC/N protection. 63 SNC/N protected GMX’s VC-12s or. However if the hardware versions are different the software version must be the functionally equal version mentioned above. If GMX is protected. Flash checksum calculation works correctly only if SCU-H has SW version 1. a combination of the alternatives above so that 2*#E1 + #VC12M + 3*#VC2M ≤ 126 and #VC12T + 3*#VC2T ≤ 63. Tx AIS is not generated in G.0 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1. 10004_22 © 2008 Tellabs. 31 SNC/N protected VC-12s of SBU + 63 GMX’s VC-12s or. Dual ended (bidirectional) MS 1+1 is not supported. 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). signal label values are not copied automatically from the terminating VCs to the monitoring VCs. 31 VC-12s may have CAS capacity inside one GMXBUS. #VC12T = number of terminating VC-12s and #VC2T = number of terminating VC-2s.704 termination. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 163 . SCU-H (SCZ545) software version must be 1. except during the middle phase of the software upgrade process. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. #VC2M = number of monitoring VC-2s.11 or higher. #VC12M = number of monitoring VC-12s. the software versions of both GMXs must be the same. 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).GMX Unit: GMZ544 Unit Software • • GMX hardware version must be 3. Control channels in VC-4 POH with MS 1+1 protection are not supported. MartisDXX Manager support for this unit without SBU functionality is available in Release 10. The total capacity for VC-12/2s is (in the case of two protected GMXs): • • • • • 63 VC-12s of SBU + 63 GMX’s VC-12s or.

The versions 3.18 / functionally same as 3. not vice versa (CR ID 300067521). Missing message deleter deactivation. . The fault Reconfiguring X-connect database now activates a red led properly. This may cause X-bus FAT allocation conflicts.1 and the problem exists only in GMZ544 software version 4. a GMU resets or the active GMX resets (CR ID 200026307). Fallback list warning alarm generation should be enabled when "Use quality levels" is disabled. It is now possible to connect the whole capacity of all over-8M ports with a single management operation (CR ID 200010985 and 200014991). This change is needed to support STE-10M when speeds over 8960 kbit/s are used. The X-bus object attribute in GMX uses a wrong macro (CR ID 300074470). • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 164 10004_22 © 2008 Tellabs. Option to select Fallback List Warning alarm in GMX mistakenly used wrong polarity.5 Version 4.2 This is emergency version to fix flash memory related problems in the device driver level. Therefore.19) • If ports bigger than 140 timeslots are used the IA test timeslot does not overlap with port. Otherwise data traffic would be affected (CR ID 200027037). Memory overflow does not happen anymore when a GMU added to the node inventory or deleted from the node inventory. This version is functionally identical to version 4. 13. Flash problems have caused download and setup problems in some units. In very rare circumstances it is possible that this causes unit to stop responding to NMS messages (CR ID 300069654). FAT allocation table resources may not be de-allocated during swap or unswap operation. Trunk swap does not operate correctly in GMX unit when swap between X-buses is applied (swap ports in upper and lower shelf). • • • 13. Swap inside one X-bus operates correctly (CR ID 300073896). (CR ID 200026983). 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).GMX Unit: GMZ544 Unit Software Bugs • • Under certain circumstances SLM and UNEQ alarms might stay on even if the alarm cause has disappeared (CR ID 300074269).6 Version 4. a switch over during reconfiguration is not anymore possible if a fault causing a switch over is activated.20 and 4.1.2 can be used together and replaced with each other in same node.1 Note: This version has serious flash device driver errors and it must not be used! Enhancements and Fixed Bugs (compared with version 3.

Immediate switch over will automatically follow preventing the wrong GMX becoming active (CR ID 200013506).2003). The check of incoming message integrity is improved. In a protected node this fault must have been disappeared on both the GMX units before it is safe to start configuring GMXs. This will make the unit much more reliable in case of any communication problem.GMX Unit: GMZ544 Unit Software • 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. The actual selection logic in the unit has been working without any problems and remains unchanged (CR ID 200011222). This change concerns only the reporting of QL values. effective date 17. A component batch problem detected in October 2003 in STM-1-LH-13 (ODH454. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 165 . 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. 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. ODH703) interface modules has been corrected with component change (CCN2003108. A new introduced fault Unit Initializing is active until it is safe to start configuring the unit. • • • • • • • • 10004_22 © 2008 Tellabs. The processing of the invalid message is prevented. 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).11. The reason was that the GMX with incomplete copy of the cross connection database could become active in the node reset. the neighbour node is able to apply the defined QL of the internal clock correctly (CR ID 200012836). Also the EXT clock QL is set to value 7 (DNU) when there is an active problem in the external clock source. The USW logic is changed to prevent the HW problem (CR ID 200012048). 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. This component problem causes the USW to report LOF fault instead of LOS fault when the input signal is missing in that interface. (CR ID 200018176). 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. (CR ID 200012351) The possibility of GMX reset associated with table overflow in Fault Mask object has been fixed (CR ID 200012686). The GMX unit is able to detect a message that has a consistency problem in the internal data structure. Wrong alarm handling in bit V5 fixed (VC-2/VC-12) (CR ID 200012057). Therefore.

Monitoring VC-12/2s in GMX use the same TU-bus internal resources as VC-12s in SBU.GMX Unit: GMZ544 Unit Software Dependencies • • • • • • • • • GMX hardware version must be 3. MartisDXX Manager support for this unit without SBU functionality is available in Release 10.704 termination. #VC2M = number of monitoring VC-2s. 10004_22 © 2008 Tellabs. SCU-H (SCZ545) software version must be 1. Flash checksum calculation works correctly only if SCU-H has SW version 1. 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). when X-bus-AIS (=B2-AIS) is detected. signal label values are not copied automatically from the terminating VCs to the monitoring VCs.11 or higher. It means that 62 VC-12s may have CAS capacity. In the case of SNC/N protection. where #E1 = number of VC-12s of SBU. the software versions of GMXs must be the same. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1. 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). except during the middle phase of software upgrade process. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer.0 or higher. 20 SNC/N protected GMX’s VC-2s + 3 SNC/N protected GMX’s VC-12s or. a combination of the alternatives above so that 2*#E1 + #VC12M + 3*#VC2M ≤ 126 and #VC12T + 3*#VC2T ≤ 63. • • • • • • One timeslot (64 kbit) of GMXBUS1 cannot be allocated. 31 VC-12s may have CAS capacity inside one GMXBUS.6 or higher.5 or higher. Control channels in the first octet of VC-12 payload are not supported. In the case GMX is protected.1A Service Pack 3 or higher. Tx AIS is not generated in G. 63 SNC/N protected GMX’s VC-12s or. The total capacity for VC-12/2s is (in the case of two protected GMXs): • • • • • 63 VC-12s of SBU + 63 GMX’s VC-12s or. #VC12M = number of monitoring VC-12s. #VC12T = number of terminating VC-12s and #VC2T = number of terminating VC-2s. 31 SNC/N protected VC-12s of SBU + 63 GMX’s VC-12s or. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 166 . Dual ended (bidirectional) MS 1+1 is not supported. Restrictions • • The control channel in the R0 byte of VC-12 is forbidden because of unreliable HW functionality. In the case GMX is protected.

22 / functionally same as 4. SCU-H (SCZ545) software version must be 1. (CR ID 300047579) The MS protection switching may fail due to OTP ASIC internal timer problem in some units. otherwise GMX hardware version must be 1. (CR ID 300056746) • • • • • 13. (CR ID 300027029) EEPROM hardware read access is not supported. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 167 . This bug may cause problems in unit download and unit non volatile parameters. Flash list record status bit handling has been fixed (CR ID 300092117). (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. • • • 10004_22 © 2008 Tellabs.0 or higher. except during the middle phase of the software upgrade process.11 or higher.0 or higher for S-bus/X-bus (VC-12 of SBU connected to GMX’s VC-12) connections to be used.6) • • • • 1+1 protection switch does not cause fake SSF alarms on P12s (CR ID 300070961). GMX hardware version must be 2. FPGA init fail is traffic affecting. The 50ms switch time measuring has a small problem. the software versions of both GMXs must be the same. Fault activation is customer requirement. STM-1 loop timeout is not truncated in an STM-1 interface #2 (CR ID 300021040). The activated fault does not disappear without service actions.GMX Unit: GMZ544 Unit Software • Control channels in VC-4 POH with MS 1+1 protection are not supported. If GMX is protected. both GMXs must have an interface module. even if the STM-1 interface in the protecting GMX is not used.7 Version 3. (CR ID 300038862) The fault Reconfiguring X-Connect Database may activate unnecessarily after inventory create operation in unprotected node. XSC FPGA init may fail during unit initialization. LOF fault is not reported if P12s AIS reporting is disabled (CR ID 300021812). However if the hardware versions are different the software version must be the functionally equal version mentioned above. Dependencies • When GMXs are equipment protected (both GMXs installed) and synchronization input is taken from the STM-1 interface. The unit has no fault indication if this error happens.24 Enhancements and Fixed Bugs (compared with version 3. Bugs • • • • Flash driver is not completely compatible with the used flash memory type. (CR ID 300041527 ) The fault Fallback list warning does not activate. (CR ID 300038153) MC RAI (Master Clock Remote Alarm Indication) feature does not operate because of a bug in application. In the case GMX is protected.

GMX Unit: GMZ544 Unit Software

• • • • • •

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 VC-12/2s is (in the case of two protected GMXs):
• • • • •

63 VC-12s of SBU + 63 GMX’s VC-12s or, 31 SNC/N protected VC-12s of SBU + 63 GMX’s VC-12s or, 63 SNC/N protected GMX’s VC-12s or, 20 SNC/N protected GMX’s VC-2s + 3 SNC/N protected GMX’s 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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
168

10004_22 © 2008 Tellabs.

GMX Unit: GMZ544 Unit Software

13.8 Version 3.23
This is an unofficial test version.

13.9 Version 3.22
Enhancements and Fixed Bugs (compared with version 3.21 / functionally same as 4.4)
• •

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 GMX’s 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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
169

GMX Unit: GMZ544 Unit Software

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 GMX’s VC-12s or, 31 SNC/N protected VC-12s of SBU + 63 GMX’s VC-12s or, 63 SNC/N protected GMX’s VC-12s or, 20 SNC/N protected GMX’s VC-2s + 3 SNC/N protected GMX’s 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.10 Version 3.21
Enhancements and Fixed Bugs (compared with version 3.20 / functionally same as 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)
10004_22 © 2008 Tellabs.

• •

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
170

GMX Unit: GMZ544 Unit Software

• • • • •

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 GMX’s 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 VC-12/2s is (in the case of two protected GMXs):
• • • • •

63 VC-12s of SBU + 63 GMX’s VC-12s or, 31 SNC/N protected VC-12s of SBU + 63 GMX’s VC-12s or, 63 SNC/N protected GMX’s VC-12s or, 20 SNC/N protected GMX’s VC-2s + 3 SNC/N protected GMX’s VC-12s or, a combination of the alternatives above so that 2*#E1 + #VC12M + 3*#VC2M ≤ 126 and #VC12T + 3*#VC2T ≤ 63, where #E1 =
Tellabs® 8100 Managed Access System Unit Software Version Dependencies
171

10004_22 © 2008 Tellabs.

GMX Unit: GMZ544 Unit Software

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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
172

10004_22 © 2008 Tellabs.

GMX Unit: GMZ544 Unit Software

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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
173

GMX Unit: GMZ544 Unit Software

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 GMX’s 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):
• • • • •

63 VC-12s of SBU + 63 GMX’s VC-12s or, 31 SNC/N protected VC-12s of SBU + 63 GMX’s VC-12s or, 63 SNC/N protected GMX’s VC-12s or, 20 SNC/N protected GMX’s VC-2s + 3 SNC/N protected GMX’s 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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
174

10004_22 © 2008 Tellabs.

GMX Unit: GMZ544 Unit Software

• • • • • • •

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
• • •

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
Enhancements and Fixed Bugs (compared with version 3.17)

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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
175

GMX Unit: GMZ544 Unit Software

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 GMX’s VC-12/2s can now be used together with S-bus connections (VC-12s of SBU connected to GMX’s 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 GMX’s 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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
176

10004_22 © 2008 Tellabs.

GMX Unit: GMZ544 Unit Software

• • • • • •

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):
• • • • •

63 VC-12s of SBU + 63 GMX’s VC-12s or, 31 SNC/N protected VC-12s of SBU + 63 GMX’s VC-12s or, 63 SNC/N protected GMX’s VC-12s or, 20 SNC/N protected GMX’s VC-2s + 3 SNC/N protected GMX’s 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.

10004_22 © 2008 Tellabs.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
177

GMX Unit: GMZ544 Unit Software

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
Enhancements and Fixed Bugs (compared with version 3.16)

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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
178

10004_22 © 2008 Tellabs.

GMX Unit: GMZ544 Unit Software

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 GMX’s 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 GMX’s VC-12/2s cannot be used if S-bus (VC-12s of SBU connected to GMX’s 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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
179

GMX Unit: GMZ544 Unit Software

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. GMX’s 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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
180

10004_22 © 2008 Tellabs.

GMX Unit: GMZ544 Unit Software

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 GMX’s 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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
181

GMX Unit: GMZ544 Unit Software

• • • • • • • • •

Does not support the use of ESU (CR ID 200005401). SNC/N protection for GMX’s VC-12/2s cannot be used if S-bus (VC-12s of SBU connected to GMX’s 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. GMX’s 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).

• • • • • • •

• •

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
182

10004_22 © 2008 Tellabs.

GMX Unit: GMZ544 Unit Software

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:
• • •

• •

• •

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.

13.16 Version 3.15
Enhancements and Fixed Bugs (compared with version 3.8)
• • • • • •

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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
183

when X-bus-AIS (=B2-AIS) is detected. 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). SNC protection works only if SCU-H has SW version 1.3 or higher. Tx AIS is not generated in G.704 termination. This may lead the node to lose cross connections (CR ID 200026983). SNC/N protection for GMX’s VC-12/2s cannot be used if S-bus (VC-12s of SBU connected to GMX’s TU12s or VC-12s) connections are used and vice versa. MartisDXX Manager support for this unit without SBU functionality is available in Release 10.1A Service Pack 3 or higher. . Therefore. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1. • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 184 10004_22 © 2008 Tellabs.3 or higher.6 or higher. Bugs • The fault Reconfiguring X-connect database activates a yellow led instead of a proper red led. signal label values are not copied automatically from the terminating VCs to the monitoring VCs. 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).5 or higher. a switch over during reconfiguration is possible if a fault causing a switch over is activated. Dual ended (bidirectional) MS 1+1 is not supported. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. It means that 62 VC-12s may have CAS capacity. One timeslot (64 kbit) of GMXBUS1 cannot be allocated. In the case of SNC/N protection. Supports reconfiguration with reset only (CR ID 200005094). 31 VC-12s may have CAS capacity inside one GMXBUS. otherwise GMX hardware version must be 1. Control channels in the first octet of VC-12 payload are not supported. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. This error has no functional effects but may be confusing (CR ID 200011222). • • • • • • • • Restrictions • • • • • • • • • • • The control channel in the R0 byte of VC-12 should not be used because of unreliable HW functionality. 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.0 or higher for S-bus/X-bus (VC-12 of SBU connected to GMX’s VC-12) connections to be used. Does not support the use of ESU (CR ID 200005401).0 or higher SCU-H (SCZ545) software version must be 1. Flash checksum calculation works correctly only if SCU-H has SW version 1. Control channels in VC-4 POH with MS 1+1 protection are not supported.GMX Unit: GMZ544 Unit Software • GMX hardware version must be 2.

The flag should be copied from the protected interface to the protecting interface. Purposeless power supply alarms may appear in certain rare situations (CR ID 200008442). the VC-4 timaAisEnabled flag gets the default value (ON) in the protecting interface. a burst of interrupts resulting from GMX switchover (equipment protection switch) may cause fault monitoring inconsistency and/or SDH ASIC register values corruptions. In the case GMX is protected and lower GMX is the active cross-connection unit. Performance source setting is inactive in the Tellabs 8100 network manager interface parameters window for VC-12/2s. Therefore those faults appear twice in FMS (CR ID 200005169). Performance monitoring QOSTR lower SES threshold is compared faulty (should be permanently = 0). With a small probability. With a small probability. Purposeless Crc. Then all cross-connected timeslots are shown with usage 'free' instead of the correct usage information 'In use' (CR ID 200005293).GMX Unit: GMZ544 Unit Software • • • • • • • In rare occasions. Because of a bug in LTA ASIC. if the protected interface does have this flag OFF. 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). delta event faults may not be transferred to Tellabs 8100 network manager (CR ID 200005197). the performance source does not change in HW (CR ID 200005199). Performance counting is stopped when TU cross-connection for VC-12/VC-2 is missing (CR ID 200005168). Alarm problems: • • • • • • • • • • • • 10004_22 © 2008 Tellabs. P12s performance monitoring does not count unavailable time during AIS and LOF signal fail conditions (CR ID 200005178). 15 minutes performance event delta fault is announced by both GMXs of the node for VC12/2. In case this realizes the timestamp is always circa 497 days too old (=0xFFFFFFFF in 10 ms units) (CR ID 200005139). SETUP0 checksum calculation and comparing between GMXs does not work reliably in all situations. leading to erroneous faults and/or deteriorated data. This causes DB/HW inconsistency. 'TS usage' of VC-12/2 parameters is shown faulty by NMS. 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. GMX’s fault timestamps may be shown incorrectly (very rarely) in FMS. viz.and P12 –layers. When MS 1+1 parameters are updated to GMX. some SDH ASIC register values may become corrupted during GMX switchover (equipment protection switch) and cause data deterioration. Purposeless reset alarms without a reset can occur rarely (CR ID 200005079). With a small probability. err LAC RAM 1/2/3/4 alarm can occur sometimes (CR ID 200005197). 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. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 185 . 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.

MartisDXX Manager support for this unit without SBU functionality is available in Release 10.0 or higher. VC4 fault filtering does not work if MS 1+1 protection is activated and protection switch uses the interface of the passive GMX. This prevents GMX to be connected to SONET equipment.1A Service Pack 3 or higher. This version should not be used once the next official version is available.13 This is an official emergency version based on version 3.5 or higher. GMX generates fault Loss of AU4 pointer if SS-bit values in AU4 pointer differ from ‘10’. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 186 10004_22 © 2008 Tellabs.6 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1. SNC protection works only if SCU-H has SW version 1. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1.17 Version 3. PLL alarm does not work in the case of a clock loop.3 or higher. Does not support the use of ESU (CR ID 200005401).12. except during the middle phase of software upgrade process. . One timeslot (64 kbit) of GMXBUS1 cannot be allocated. It means that 62 VC-12s may have CAS capacity. SNC/N protection for GMX’s VC-12/2s cannot be used if S-bus (VC-12s of SBU connected to GMX’s TU12s) connections are used and vice versa. 31 VC-12s may have CAS capacity inside one GMXBUS. SCU-H (SCZ545) software version must be 1. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. Supports reconfiguration with reset only (CR ID 200005094). 13.GMX Unit: GMZ544 Unit Software • • • The Phase locked loop and 20 MHz node clock missing alarms are active for a while after GMX reset. Control channels in the first octet of VC-12 payload are not supported.3 or higher. Restrictions • • • • • • • • • The control channel in the R0 byte of VC-12 should not be used because of unreliable HW functionality. the software versions of GMXs must be the same. Dependencies • • • • • • • • In the case GMX is protected. Cross-connections between E1VC-12s (VC12 of SBU) and GMX's VC-12s are not supported. GMX hardware version must be 1.

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

SES lower threshold is compared erroneously to the given SES threshold which should act as upper limit only.GMX Unit: GMZ544 Unit Software • With a small probability. 13. Supports reconfiguration with reset only (CR ID 200005094).11. lower ES and lower SES (always = 0) are compared faulty. Dependencies • • • • • • • • In the case GMX is protected. 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.3 or higher. GMX hardware version must be 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 188 10004_22 © 2008 Tellabs. SNC protection works only if SCU-H has SW version 1. Performance monitoring thresholds QOSTR lower BBE. TTI expected value of SNC/I protected E1VC-12 (VC-12 of SBU) cannot be changed Alarm problems: • • • • • • • The Phase locked loop and 20 MHz node clock missing alarms are active for a while after GMX reset.18 Version 3.6 or higher.1A Service Pack 3 or higher.5 or higher. MartisDXX Manager support for this unit without SBU functionality is available in Release 10. a burst of interrupts resulting from GMX switchover (equipment protection switch) may cause fault monitoring inconsistency and/or SDH ASIC register values corruptions.0 or higher.3 or higher. Flash checksum calculation works correctly only if SCU-H has SW version 1. Recreating at least one timeslot connection with CAS will enable all connections for that trunk again. VC-4 fault filtering does not work if MS 1+1 protection is activated and protection switch uses the interface of the passive GMX. SCU-H (SCZ545) software version must be 1. . This version should not be used once the next official version is available. the software versions of GMXs must be the same. Deleting one or more timeslot connections with CAS will disable all other CAS connections for the corresponding trunk. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1. PLL alarm does not work in the case of a clock loop. 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 =)). except during the middle phase of software upgrade process.12 This is an official emergency version based on version 3.

Performance counting is stopped when TU cross-connection for VC-12/VC-2 is missing (CR ID 200005168).GMX Unit: GMZ544 Unit Software • • • • • • • • • • • Does not support the use of ESU (CR ID 200005401). GMX’s fault timestamps may be shown incorrectly (very rarely) in FMS. Purposeless Crc. Control channels in the first octet of VC-12 payload are not supported. SNC/N protection for GMX’s VC-12/2s cannot be used if S-bus (VC-12s of SBU connected to GMX’s TU12s) connections are used and vice versa. One timeslot (64 kbit) of GMXBUS1 cannot be allocated. Tx AIS is not generated in G. Control channels in VC-4 POH with MS 1+1 protection are not supported. when X-bus-AIS (=B2-AIS) is detected. In case this realizes the timestamp is always circa 497 days too old (=0xFFFFFFFF in 10 ms units) (CR ID 200005139). signal label values are not copied automatically from the terminating VCs to the monitoring VCs. a switch over during reconfiguration is possible if a fault causing a switch over is activated. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. GMX generates fault Loss of AU4 pointer if SS-bit values in AU4 pointer differ from ‘10’. 31 VC-12s may have CAS capacity inside one GMXBUS. err LAC RAM 1/2/3/4 alarm can occur sometimes (CR ID 200005197). 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). SETUP0 checksum calculation and comparing between GMXs does not work reliably in all situations. Bugs • The fault Reconfiguring X-connect database activates a yellow led instead of a proper red led. This error has no functional effects but may be confusing (CR ID 200011222). Because of a bug in LTA ASIC. Therefore. 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. It means that 62 VC-12s may have CAS capacity. • • • • • • • • • • 10004_22 © 2008 Tellabs. 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). In rare occasions. In the case of SNC/N protection. Dual ended (bidirectional) MS 1+1 is not supported. 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. delta event faults may not be transferred to Tellabs 8100 network manager (CR ID 200005197). This may lead the node to lose cross connections (CR ID 200026983). Tellabs® 8100 Managed Access System Unit Software Version Dependencies 189 . This prevents GMX to be connected to SONET equipment.704 termination. Cross-connections between E1VC-12s (VC-12 of SBU) and GMX's VC-12s are not supported.

19 Version 3. 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. SES lower threshold is compared erroneously to the given SES threshold which should act as upper limit only. GMX hardware version must be 1. 13.9. With a small probability. When MS 1+1 parameters are updated to GMX. lower ES and lower SES (always = 0) are compared faulty. Performance monitoring thresholds QOSTR lower BBE. With a small probability.11 This is an official emergency version based on version 3. Recreating at least one timeslot connection with CAS will enable all connections for that trunk again. . 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 =)). the GMX unit may go to software reset at random times. the VC-4 timaAisEnabled flag gets the default value (ON) in the protecting interface.0 or higher. some SDH ASIC register values may become corrupted during GMX switchover (equipment protection switch). In the case GMX is protected and lower GMX is the active cross-connection unit. if the protected interface does have this flag OFF. 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: • • • • • • • • • • • • The Phase locked loop and 20 MHz node clock missing alarms are active for a while after GMX reset. The flag should be copied from the protected interface to the protecting interface. Dependencies • • In the case GMX is protected. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 190 10004_22 © 2008 Tellabs. the software versions of GMXs must be the same. handling of LTA ASIC hardware link between GMXs of a node during GMX switchover (equipment protection switch) may not function correctly. after which the unit continues to work normally. With a small probability. With this software version. except during the middle phase of software upgrade process. VC-4 fault filtering does not work if MS 1+1 protection is activated and protection switch uses the interface of the passive GMX. This causes DB/HW inconsistency. However. This version should not be used once the next official version is available. PLL alarm does not work in the case of a clock loop. 'TS usage' of VC-12/2 parameters is shown faulty by NMS.GMX Unit: GMZ544 Unit Software • • P12s performance monitoring does not count unavailable time during AIS and LOF signal fail conditions (CR ID 200005178). Then all cross-connected timeslots are shown with usage 'free' instead of the correct usage information 'In use' (CR ID 200005293).

In rare occasions. Tx AIS is not generated in G. when X-bus-AIS (=B2-AIS) is detected. MartisDXX Manager support for this unit without SBU functionality is available in Release 10. err LAC RAM 1/2/3/4 alarm can occur sometimes (CR ID 200005197).1A Service Pack 3 or higher.6 or higher. delta event faults may not be transferred to Tellabs 8100 network manager (CR ID 200005197).704 termination. SNC/N protection for GMX’s VC-12/2s cannot be used if S-bus (VC-12s of SBU connected to GMX’s TU12s) connections are used and vice versa. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 191 . Control channels in VC-4 POH with MS 1+1 protection are not supported. Restrictions • • • • • • • • • • • • • The control channel in the R0 byte of VC-12 should not be used because of unreliable HW functionality. Purposeless Crc. Flash checksum calculation works correctly only if SCU-H has SW version 1. In the case of SNC/N protection.3 or higher.3 or higher. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1. Therefore. 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. • • • 10004_22 © 2008 Tellabs. SNC protection works only if SCU-H has SW version 1. 31 VC-12s may have CAS capacity inside one GMXBUS. This prevents GMX to be connected to SONET equipment.5 or higher.GMX Unit: GMZ544 Unit Software • • • • • • SCU-H (SCZ545) software version must be 1. a switch over during reconfiguration is possible if a fault causing a switch over is activated. Supports reconfiguration with reset only (CR ID 200005094). Dual ended (bidirectional) MS 1+1 is not supported. Control channels in the first octet of VC-12 payload are not supported. It means that 62 VC-12s may have CAS capacity. GMX generates fault Loss of AU4 pointer if SS-bit values in AU4 pointer differ from ‘10’. 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. Does not support the use of ESU (CR ID 200005401). signal label values are not copied automatically from the terminating VCs to the monitoring VCs. This may lead the node to lose cross connections (CR ID 200026983). Cross-connections between E1VC-12s (VC12 of SBU) and GMX's VC-12s are not supported. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. This error has no functional effects but may be confusing (CR ID 200011222). Bugs • The fault Reconfiguring X-connect database activates a yellow led instead of a proper red led.

GMX’s fault timestamps may be shown incorrectly (very rarely) in FMS. the GMX unit may go to software reset at random times. With a small probability. 'TS usage' of VC-12/2 parameters is shown faulty by NMS. if the protected interface does have this flag OFF. Because of a bug in LTA ASIC. SES lower threshold is compared erroneously to the given SES threshold which should act as upper limit only. 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. With a small probability. the VC-4 timaAisEnabled flag gets the default value (ON) in the protecting interface. Deleting one or more timeslot connections with CAS will disable all other CAS connections for the corresponding trunk. However. In case this realizes the timestamp is always circa 497 days too old (=0xFFFFFFFF in 10 ms units) (CR ID 200005139). lower ES and lower SES (always = 0) are compared faulty. after which the unit continues to work normally. . In the case GMX is protected and lower GMX is the active cross-connection unit. When MS 1+1 parameters are updated to GMX. handling of LTA ASIC hardware link between GMXs of a node during GMX switchover (equipment protection switch) may not function correctly. 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. a burst of interrupts resulting from GMX switchover (equipment protection switch) may cause fault monitoring inconsistency and/or SDH ASIC register values corruptions. 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 =)).GMX Unit: GMZ544 Unit Software • • • • • Performance counting is stopped when TU cross-connection for VC-12/VC-2 is missing (CR ID 200005168). 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). P12s performance monitoring does not count unavailable time during AIS and LOF signal fail conditions (CR ID 200005178). The flag should be copied from the protected interface to the protecting interface. the probability of the reset is low. some SDH ASIC register values may become corrupted during GMX switchover (equipment protection switch). Recreating at least one timeslot connection with CAS will enable all connections for that trunk again. Purposeless power supply alarms may appear in certain rare situations (CR ID 200008442). 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: • • • • • • • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 192 10004_22 © 2008 Tellabs. Performance monitoring thresholds QOSTR lower BBE. Purposeless reset alarms without a reset can occur rarely (CR ID 200005079). With this software version. SETUP0 checksum calculation and comparing between GMXs does not work reliably in all situations. This causes DB/HW inconsistency.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies 193 .3.2 .8 is fixed. This version should not be used once the next official version is available. VC-4 fault filtering does not work if MS 1+1 protection is activated and protection switch uses the interface of the passive GMX.9 This is an official emergency version almost equal to version 3.20 Version 3. The only difference is that the bug concerning SNC/N protected vcGtps in versions 3.8.GMX Unit: GMZ544 Unit Software • • • The Phase locked loop and 20 MHz node clock missing alarms are active for a while after GMX reset. 13. 10004_22 © 2008 Tellabs. PLL alarm does not work in the case of a clock loop.

0 or higher. Restrictions • • • • • • • • • • • • • • The control channel in the R0 byte of VC-12 should not be used because of unreliable HW functionality. SNC/N protection for GMX’s VC-12/2s cannot be used if S-bus (VC-12s of SBU connected to GMX’s TU12s) connections are used and vice versa. except during the middle phase of software upgrade process. 31 VC-12s may have CAS capacity inside one GMXBUS.3 or higher. Cross-connections between E1VC-12s (VC-12 of SBU) and GMX's VC-12s are not supported. Control channels in VC-4 POH with MS 1+1 protection are not supported. signal label values are not copied automatically from the terminating VCs to the monitoring VCs. It means that 62 VC-12s may have CAS capacity. SCU-H (SCZ545) software version must be 1. Supports reconfiguration with reset only (CR ID 200005094). One timeslot (64 kbit) of GMXBUS1 cannot be allocated. MartisDXX Manager support for this unit with SBU functionality is available in Release 11 Service Pack 2 or higher. SNC protection works only if SCU-H has SW version 1. Does not support the enhanced internal state monitoring test features.21 Version 3. In the case of SNC/N protection.GMX Unit: GMZ544 Unit Software 13.5 or higher. .3 or higher.1A Service Pack 3 or higher. MartisDXX Manager support for this unit without SBU functionality is available in Release 10. Flash checksum calculation works correctly only if SCU-H has SW version 1.8 Dependencies • • • • • • • • In the case GMX is protected.704 termination. Tx AIS is not generated in G.6 or higher. GMX hardware version must be 1. 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. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 194 10004_22 © 2008 Tellabs. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1. when X-bus-AIS (=B2-AIS) is detected. Dual ended (bidirectional) MS 1+1 is not supported. Does not support the use of ESU (CR ID 200005401). the software versions of GMXs must be the same. Control channels in the first octet of VC-12 payload are not supported.

if the protected interface does have this flag OFF. Because of a bug in LTA ASIC. P12s performance monitoring does not count unavailable time during AIS and LOF signal fail conditions (CR ID 200005178). Purposeless reset alarms without a reset can occur rarely (CR ID 200005079). GMX’s fault timestamps may be shown incorrectly (very rarely) in FMS. Purposeless Crc. With a small probability. delta event faults may not be transferred to Tellabs 8100 network manager (CR ID 200005197). With a small probability. a switch over during reconfiguration is possible if a fault causing a switch over is activated. Recreating at least one timeslot connection with CAS will enable all connections for that trunk again. Deleting one or more timeslot connections with CAS will disable all other CAS connections for the corresponding trunk. This causes DB/HW inconsistency. This may lead the node to lose cross connections (CR ID 200026983). 'TS usage' of VC-12/2 parameters is shown faulty by NMS. In rare occasions. 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). The flag should be copied from the protected interface to the protecting interface. 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. Then all cross-connected timeslots are shown with usage 'free' instead of the correct usage information 'In use' (CR ID 200005293). In the case GMX is protected and lower GMX is the active cross-connection unit. some SDH ASIC register values may become corrupted during GMX switchover (equipment protection switch). a burst of interrupts resulting from GMX switchover (equipment protection switch) may cause fault monitoring inconsistency and/or SDH ASIC register values corruptions. Performance counting is stopped when TU cross-connection for VC-12/VC-2 is missing (CR ID 200005168).GMX Unit: GMZ544 Unit Software Bugs • The fault Reconfiguring X-connect database activates a yellow led instead of a proper red led. err LAC RAM 1/2/3/4 alarm can occur sometimes (CR ID 200005197). 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. This error has no functional effects but may be confusing (CR ID 200011222). the VC-4 timaAisEnabled flag gets the default value (ON) in the protecting interface. When MS 1+1 parameters are updated to GMX. 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. With a small probability. Purposeless power supply alarms may appear in certain rare situations (CR ID 200008442). Tellabs® 8100 Managed Access System Unit Software Version Dependencies 195 . Therefore. handling of LTA ASIC hardware link between GMXs of a node during GMX switchover (equipment protection switch) may not function correctly. SETUP0 checksum calculation and comparing between GMXs does not work reliably in all situations.

With this software version. If GMX for any reason ends up in a reconfiguration state there is a small probability that the operation fails. Does not support the use of ESU (CR ID 200005401). Restrictions • • • The control channel in the R0 byte of VC-12 should not be used because of unreliable HW functionality. 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 =)).GMX Unit: GMZ544 Unit Software • Performance monitoring thresholds QOSTR lower BBE.1A Service Pack 3 or higher. Data through VC-12 circuits may be cut when using SNC/N protected vcGtps. SNC protection works only if SCU-H has SW version 1. SCU-H (SCZ545) software version must be 1. VC-4 fault filtering does not work if MS 1+1 protection is activated and protection switch uses the interface of the passive GMX. SES lower threshold is compared erroneously to the given SES threshold which should act as upper limit only.3 or higher. the software versions of GMXs must be the same. . Tellabs® 8100 Managed Access System Unit Software Version Dependencies 196 10004_22 © 2008 Tellabs. except during the middle phase of software upgrade process. This leads to unnecessary reset of passive GMX unit. Flash checksum calculation works correctly only if SCU-H has SW version 1. In the case GMX is not protected the node works correctly only if SCU-H has SW version 1. the probability of the reset is low.6 or higher.3 or higher. MartisDXX Manager support for this unit is available in Release 10. Eventually the unit is able to perform reconfiguration.5 or higher. However.5 Dependencies • • • • • • • In the case GMX is protected.0 or higher. after which the unit continues to work normally. the GMX unit may go to software reset at random times. Supports reconfiguration with reset only (CR ID 200005094).22 Version 3. 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. 13. GMX hardware version must be 1. PLL alarm does not work in the case of a clock loop. lower ES and lower SES (always = 0) are compared faulty. TTI expected value of SNC/I protected E1VC-12 (VC-12 of SBU) cannot be changed Alarm problems: • • • • • • • • • • The Phase locked loop and 20 MHz node clock missing alarms are active for a while after GMX reset.

Purposeless Crc. Does not support the enhanced internal state monitoring test features. err LAC RAM 1/2/3/4 alarm can occur sometimes (CR ID 200005197). 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. delta event faults may not be transferred to Tellabs 8100 network manager (CR ID 200005197). Tellabs® 8100 Managed Access System Unit Software Version Dependencies 197 . Therefore. In rare occasions. Bugs • The fault Reconfiguring X-connect database activates a yellow led instead of a proper red led. 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. Performance counting is stopped when TU cross-connection for VC-12/VC-2 is missing (CR ID 200005168). 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). Control channels in VC-4 POH with MS 1+1 protection are not supported. This causes DB/HW inconsistency. signal label values are not copied automatically from the terminating VCs to the monitoring VCs. SETUP0 checksum calculation and comparing between GMXs does not work reliably in all situations. 31 VC-12s may have CAS capacity inside one GMXBUS. when X-bus-AIS (=B2-AIS) is detected. In the case of SNC/N protection. This may lead the node to lose cross connections (CR ID 200026983). One timeslot (64 kbit) of GMXBUS1 cannot be allocated. Purposeless reset alarms without a reset can occur rarely (CR ID 200005079). a switch over during reconfiguration is possible if a fault causing a switch over is activated. Dual ended (bidirectional) MS 1+1 is not supported. Tx AIS is not generated in G. SBU and E1Mapper modules (E1M-75 and E1M-120) are not supported. This prevents GMX to be connected to SONET equipment. It means that the last VC-12 of GMXBUS 1 has to be locked using a long X-bus buffer. It means that 62 VC-12s may have CAS capacity.GMX Unit: GMZ544 Unit Software • • • • • • • • • • GMX generates fault Loss of AU4 pointer if SS-bit values in AU4 pointer differ from ‘10’. Control channels in the first octet of VC-12 payload are not supported. 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. if the • • • • • • • • • • • • 10004_22 © 2008 Tellabs. Purposeless power supply alarms may appear in certain rare situations (CR ID 200008442). the VC-4 timaAisEnabled flag gets the default value (ON) in the protecting interface. This error has no functional effects but may be confusing (CR ID 200011222). GMX’s fault timestamps may be shown incorrectly (very rarely) in FMS.704 termination. Because of a bug in LTA ASIC.

Remote case of trunk swap (trunks from separate X-buses) may cause bit errors within the corresponding circuits during the first 2 minutes. The flag should be copied from the protected interface to the protecting interface. some SDH ASIC register values may become corrupted during GMX switchover (equipment protection switch). • 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. Deleting one or more timeslot connections with CAS will disable all other CAS connections for the corresponding trunk. the GMX unit may go to software reset at random times. Data through VC-12 circuits may be cut when using SNC/N protected vcGtps. With this software version. With a small probability. Then all cross-connected timeslots are shown with usage 'free' instead of the correct usage information 'In use' (CR ID 200005293). However.GMX Unit: GMZ544 Unit Software protected interface does have this flag OFF. With a small probability. • 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. Recreating at least one timeslot connection with CAS will enable all connections for that trunk again. Alarm problems: • • • • • • • • • • • • • • • The Phase locked loop and 20 MHz node clock missing alarms are active for a while after GMX reset. Performance monitoring thresholds QOSTR lower BBE. If GMX for any reason ends up in a reconfiguration state there is a small probability that the operation fails. Extended links of SCU-H (IP links 3-16 and HDLC links 1-16) do not work. after which the unit continues to work normally. handling of LTA ASIC hardware link between GMXs of a node during GMX switchover (equipment protection switch) may not function correctly. the probability of the reset is low. 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. • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 198 10004_22 © 2008 Tellabs. . This leads to unnecessary reset of passive GMX unit. SES lower threshold is compared erroneously to the given SES threshold which should act as upper limit only. With a small probability. 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 =)). after reset the SNC protection logic cannot use the lower interface. a burst of interrupts resulting from GMX switchover (equipment protection switch) may cause fault monitoring inconsistency and/or SDH ASIC register values corruptions. lower ES and lower SES (always = 0) are compared faulty. Eventually the unit is able to perform reconfiguration. Trunk swap does not work between VC-12s of the GMX when the VC-12s are allocated from the same X-bus (local swap). 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.

Tx AIS is not generated in G. except during the middle phase of software upgrade process. when X-bus-AIS (=B2-AIS) is detected. In the case GMX is not protected the node works slowly via Tellabs 8100 network manager. One timeslot (64 kbit) of GMXBUS1 cannot be allocated. It means that 62 VC-12s may have CAS capacity. In the case of SNC/N.1A-3 Installation and Release Notes. Restrictions • • • • • • • • • • • • • • The control channel in the R0 byte of VC-12 should not be used because of unreliable HW functionality.3 or higher. FMS system is incomplete in the case of MS 1+1 protection and SNC/N protection.GMX Unit: GMZ544 Unit Software 13. GMX generates fault Loss of AU4 pointer if SS-bit values in AU4 pointer differ from ‘10’. the Protection Criteria attribute of an SNC protection group cannot be set to active. 31 VC-12s may have CAS capacity inside one GMXBUS. signal label values are not copied automatically from the terminating VCs to the monitoring VCs.704 termination. It means that the last VC-12s of GMXBUS 1 has to be locked using long X-bus buffer. 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). SNC protection works only if SCU-H has SW version 1. Dual ended (bidirectional) MS 1+1 is not supported. SCU-H (SCZ545) software version must be 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 199 . Control channels in VC-4 POH with MS 1+1 protection are not supported.1A Service Pack 3 or higher. Control channels in the first octet of VC-12 payload are not supported. • • • 10004_22 © 2008 Tellabs. the software versions of GMXs must be the same.2 Dependencies • • • • • In the case GMX is protected. In the case of SNC/N protection. GMX hardware version must be 1. Supports reconfiguration with reset only (CR ID 200005094). MartisDXX Manager support for this unit is available in Release 10.23 Version 3. Does not support the enhanced internal state monitoring test features. See MartisDXX Manager R10. Passivation or activation of a swapped trunk is not restricted by USW though it should be (this is a forbidden operation by definition). This prevents GMX to be connected to SONET equipment.3 or higher.0 or higher. Does not support the use of ESU (CR ID 200005401). 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).

Purposeless Crc. Then all cross-connected timeslots are shown with usage 'free' instead of the correct usage information 'In use' (CR ID 200005293). When MS 1+1 parameters are updated to GMX.GMX Unit: GMZ544 Unit Software • • Flash operations are relatively slow (approximately 10 times faster in version 3. if the protected interface does have this flag OFF. err LAC RAM 1/2/3/4 alarm can occur sometimes (CR ID 200005197). In case this realizes the timestamp is always circa 497 days too old (=0xFFFFFFFF in 10 ms units) (CR ID 200005139). With a small probability. With a small probability. Because of a bug in LTA ASIC. GMX’s fault timestamps may be shown incorrectly (very rarely) in FMS. Purposeless reset alarms without a reset can occur rarely (CR ID 200005079).5). In rare occasions. Bugs • The fault Reconfiguring X-connect database activates a yellow led instead of a proper red led. the VC-4 timaAisEnabled flag gets the default value (ON) in the protecting interface. This may lead the node to lose cross connections (CR ID 200026983). 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. a switch over during reconfiguration is possible if a fault causing a switch over is activated. SBU and E1Mapper modules (E1M-75 and E1M-120) are not supported. delta event faults may not be transferred to Tellabs 8100 network manager (CR ID 200005197). In the case GMX is protected and lower GMX is the active cross-connection unit. Purposeless power supply alarms may appear in certain rare situations (CR ID 200008442). Performance counting is stopped when TU cross-connection for VC-12/VC-2 is missing (CR ID 200005168). This error has no functional effects but may be confusing (CR ID 200011222). some SDH ASIC register values may become corrupted during GMX switchover (equipment protection switch). With a small probability. The flag should be copied from the protected interface to the protecting interface. 'TS usage' of VC-12/2 parameters is shown faulty by NMS. Therefore. a burst of interrupts resulting from GMX switchover (equipment protection switch) may cause fault monitoring inconsistency and/or SDH ASIC register values corruptions. This causes DB/HW inconsistency. P12s performance monitoring does not count unavailable time during AIS and LOF signal fail conditions (CR ID 200005178). handling of LTA ASIC hardware link between GMXs of a node during GMX switchover (equipment protection switch) may not function correctly. • • • • • • • • • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 200 10004_22 © 2008 Tellabs. SETUP0 checksum calculation and comparing between GMXs does not work reliably in all situations. 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). . 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.

P12 alarms are working correctly. 10004_22 © 2008 Tellabs. If the Performance Source attribute has value P12s or VC12 and P12s.GMX Unit: GMZ544 Unit Software • Deleting one or more timeslot connections with CAS will disable all other CAS connections for the corresponding trunk. the GMX unit may go to software reset at random times. Flash checksum calculation works unreliably. If GMX for any reason ends up in a reconfiguration state there is a small probability that the operation fails. signal degrade threshold and TIMaAisenabled attributes cannot be changed in concatenation if SNC/I protection is used. This leads to unnecessary reset of passive GMX unit. Alarm problems: • • • • • • • • • • • • The Phase locked loop and 20 MHz node clock missing alarms are active for a while after GMX reset. SES lower threshold is compared erroneously to the given SES threshold which should act as upper limit only. Data through VC-12 circuits may be cut when using SNC/N protected vcGtps. The functional state of the portmode attribute is always Monitored after reset. the probability of the reset is low. P12 alarms do not work after GMX reset. Recreating at least one timeslot connection with CAS will enable all connections for that trunk again. 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 =)). Received trail trace of interface 2 is not masked to NULL in RS and VC-4 layers when the TSF signal has been received. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 201 . Trunk swap in the remote case (trunks from separate X-buses) does not work. However. P12 performance alarms (UNAVAIL. signal degrade seconds. 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. after which the unit continues to work normally. lower ES and lower SES (always = 0) are compared faulty. PLL alarm does not work in the case of clock loop. Reset of the passive GMX affects to the synchronization sources of the active GMX. the HDLC/X-bus in same TS alarm may be active without reason. Performance monitoring thresholds QOSTR lower BBE. CAS. Trunk swap does not work between VC-12s of the GMX. VC-4 fault filtering does not work if MS 1+1 protection is activated and protection switch uses the interface of the passive GMX. QOS and QOSTR) may stay active even if P12 is in transparent mode. Extended links of SCU-H (IP links 3-16 and HDLC links 1-16) do not work. If control channel is located in SOH or VC4-POH bytes. With this software version. • • • • • • • • • The expected TI. If P12 attribute values are updated after reset. Eventually the unit is able to perform reconfiguration.

If SCU-H (SCZ545) software version is 1.6 or higher.1 Version 1. Bugs • No known bugs 14. Tellabs 8000 network manager support for this unit is available in Release 16A SP2 or higher. If SCU-H (SCZ545) software version is 2.x then version must be 1.2 Version 1. Restrictions • No restrictions.0 or higher.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. The synchronization connection initialization specific to GMU-A or GMU has been fixed (CR ID 300109943). Flash memory access updated.x then version must be 2. 14. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 202 10004_22 © 2008 Tellabs. (CR ID 300095583). .20 Enhancements and Fixed Bugs • • Improved 1/0-protection switching during equipment protection.21 Enhancements and Fixed Bugs • • VC-12 CAS AIS insertion into Rx signal does not work properly (CR ID 300110017).18 or higher. Dependencies • • • • GMX2 unit hardware version must be 1. Minimal data interruption during change of the active unit.

Restrictions • No restrictions. Restrictions • No restrictions. Dependencies • • • • GMX2 unit hardware version must be 1. Tellabs 8000 network manager support for this unit is available in Release 16A SP2 or higher. Bugs • The synchronization connection initialization specific to GMU-A or GMU is not valid. (CR ID 300097924). This error may cause unexpected random faults in the node. Tellabs 8000 network manager support for this unit is available in Release 16A SP2 or higher.0 or higher. Bugs • The synchronization connection initialization specific to GMU-A or GMU is not valid. 10004_22 © 2008 Tellabs.x then version must be 1.6 or higher.18 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 203 .0 or higher.18 Enhancements and Fixed Bugs • STM-4 IF output jitter is not according to the G. This error may cause unexpected random faults in the node.GMX2 Unit: GMZ802 Unit Software Dependencies • • • • GMX2 unit hardware version must be 1.813 specification. If SCU-H (SCZ545) software version is 1.3 Version 1.18 or higher. If SCU-H (SCZ545) software version is 2. 14.x then version must be 2. If SCU-H (SCZ545) software version is 1.x then version must be 1.6 or higher. If SCU-H (SCZ545) software version is 2.x then version must be 2.

Dependencies • • • • GMX2 unit hardware version must be 1. If SCU-H (SCZ545) software version is 2. Tellabs 8000 network manager support for this unit is available in Release 16A SP2 or higher.x then version must be 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 204 10004_22 © 2008 Tellabs. If SCU-H (SCZ545) software version is 1. (CR ID 300097924).0 or higher.18 or higher.18 or higher. Tellabs 8000 network manager support for this unit is available in Release 16A SP2 or higher.x then version must be 2.15 Enhancements and Fixed Bugs • Compatible with Tellabs 8000 network manager Release 16A SP2 or higher. If SCU-H (SCZ545) software version is 2.16 Enhancements and Fixed Bugs • CAS does not work reliably (CR ID 300095743). .6 or higher. Restrictions • No restrictions.6 or higher. The synchronization connection initialization specific to GMU-A or GMU is not valid. This error may cause unexpected random faults in the node 14.813 specification.5 Version 1.0 or higher. Restrictions • No restrictions.x then version must be 1.x then version must be 1. Dependencies • • • • GMX2 unit hardware version must be 1. If SCU-H (SCZ545) software version is 1.GMX2 Unit: GMZ802 Unit Software 14.4 Version 1. Bugs • • STM-4 IF output jitter is not according to the G.

Restrictions • • • This version can be used only with Tellabs 8000 network manager Release 16A SP1.6 or higher.x then version must be 2. If SCU-H (SCZ545) software version is 1. CAS does not work reliably. If SCU-H (SCZ545) software version is 2. This error may cause unexpected random faults in the node 14. (CR ID 300097924).813 specification. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 205 . VC-12 R-byte cross-connection is supported. Traffic is not recovered reliably after cable cuts.18 or higher. (CR ID 300097924).0 or higher. Dependencies • • • • GMX2 unit hardware version must be 1. SNC/N is not supported by Tellabs 8000 network manager Release 16A SP1.GMX2 Unit: GMZ802 Unit Software Bugs • • • STM-4 IF output jitter is not according to the G.12 Enhancements and Fixed Bugs • • Channel Associated Signalling (CAS) is supported. This version is not recommended to be used in live networks. Tellabs 8000 network manager support for this unit is available in Release 16A SP1.813 specification. The synchronization connection initialization specific to GMU-A or GMU is not valid. Bugs • • • STM-4 IF output jitter is not according to the G. CAS does not work reliably.x then version must be 1. 10004_22 © 2008 Tellabs.6 Version 1.

0 Enhancements and Fixed Bugs • This is the first official version.x then version must be 2. Restrictions • • • • • Channel Associated Signalling (CAS) is not supported.6 or higher.GMX2 Unit: GMZ802 Unit Software 14. This version is not recommended to be used in live networks. Tellabs 8000 network manager support for this unit is available in Release 16A SP1. If SCU-H (SCZ545) software version is 2.18 or higher. . This version can be used only with Tellabs 8000 network manager Release 16A SP1.0 or higher.813 specification. If SCU-H (SCZ545) software version is 1. Dependencies • • • • GMX2 unit hardware version must be 1. (CR ID 300097924). VC-12 R-byte cross-connection is not supported. Bugs • • STM-4 IF output jitter is not according to the G.7 Version 1. Traffic is not recovered reliably after cable cuts. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 206 10004_22 © 2008 Tellabs. SNC/N is not supported by Tellabs 8000 network manager Release 16A SP1.x then version must be 1.

).5. STU-1088-2W and STU-2304 (SBZ387) SDSL Network Terminating Unit support for IP filtering is available in version 1.0.y of EHZ541 (where y=0. but in this case the unit software will internally use 8 minutes as the parameter value.2 can be downloaded to LAN Modules having the version 1.LAN Module: EHZ541 Unit Software 15 LAN Module: EHZ541 Unit Software The software EHZ541 is used on a LAN Module. This restriction is related to correction of traffic cut problem. 15.1.0A SP2.4. STU-160 (SBZ385) DSL Network Terminating Unit support for IP filtering is available in version 1. STU-576.2 Dependencies • • • • • • • STU-1088/2048 (SBZ384) baseband modem support for IP filtering is available in version 1. HTU-2M (SBZ389) HDSL Network Terminating Unit’s support for IP filtering is available in version 1. 10004_22 © 2008 Tellabs. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 207 . MartisDXX Manager support for IP filtering is available in Release 10. STU-320.0. 2. Mini Node SBM 2048M (SMZ414) support for LAN Module is available in version 5... Restrictions • The address table expiration timer is configurable in 4 minute intervals from 8 minutes up to 252. Bugs • No known bugs.0. VCM-5T-A/VCM-10T-A (VCZ285A) interface unit support for LAN Module is available in version 10. The user interface may allow the setting of this value also to 0 or 4 (corrected at MartisDXX Manager R11SP3). 1. The version 1.1 Version 1.

STU-1088-2W and STU-2304 (SBZ387) SDSL Network Terminating Unit support for IP filtering is available in version 1. This can be solved by setting the address table expiration time to 16 minutes.4. HTU-2M (SBZ389) HDSL Network Terminating Unit support for IP filtering is available in version 1. . which works in most cases. Mini Node SBM 2048M (SMZ414) support for LAN Module is available in version 5. STU-160 (SBZ385) DSL 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 Dependencies • • • • • • • STU-1088/2048 (SBZ384) baseband modem support for IP filtering is available in version 1. STU-320.5. MartisDXX Manager support for IP filtering is available in Release 10.2 Version 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 208 10004_22 © 2008 Tellabs. Restrictions • No restrictions.0.LAN Module: EHZ541 Unit Software 15. STU-576.0A SP2.1.0. Bugs • LAN Module cuts traffic in "heavy traffic" load.

Restrictions • No restrictions. STU-320. Bugs • LAN Module cuts traffic in "heavy traffic" load. MartisDXX Manager support for LAN Module is available in Release 9.0. This can be solved by setting the address table expiration time to 16 minutes. Mini Node SBM 2048M (SMZ414) support for LAN Module is available in version 5.0 Dependencies • • • • • • • STU-1088/2048 (SBZ384) baseband modem support for LAN Module is available in version 1.0. which works in most cases. STU-160 (SBZ385) DSL Network Terminating Unit support for LAN Module is available in version 1.0.0B.3 Version 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 209 .LAN Module: EHZ541 Unit Software 15. STU-1088-2W and STU-2304 (SBZ387) SDSL Network Terminating Unit support for LAN Module is available in version 1.1. VCM-5T-A/VCM-10T-A (VCZ285A) interface unit support for LAN Module is available in version 10. HTU-2M (SBZ389) HDSL Network Terminating Unit support for LAN Module is available in version 1.3.3. 10004_22 © 2008 Tellabs. STU-576.

it is not anymore possible to change back to the OMH unit type without removing all the services attached. SCP (SCZ281) software version must be 3.4 supports max 139 timeslots cross-connections with over 8M cross-connection ports. XCG software version 3. The OMH-A unit is a version of OMH771 base unit (version 3. Tellabs 8150 basic.0 or higher to support 4-pair modes. In this case. and 3. Tellabs 8160 A111 and Tellabs 8170 cluster nodes as well as in Tellabs 8184 and Tellabs 8188 access switches. SCO interface module version (which is based on SCO SW DPZ652 version) must be 3.1 Version 3.2) • HCO synchronization problem with NTU using bit rate 72x64kbps is fixed (CR ID 300091819 and CR ID 300108076).4 or higher to support extra backups for other units in the node..0 or higher to support 208 kbit/s line rates.1 or higher to support 3088 kbit/s line rates with Tellabs 8110 STE-10M NTU. XCG (SMZ538) software version must be 2.0 or higher).6 or higher to support unlocking the ports without failures. SCU (SCZ280) software version must be 8. Once the OMH unit type is changed to the OMH-A unit type. 16.y or 3.y. 2. SCU-H (SCZ545) software version must be 1. which is capable of 12.0 or higher (OMH-A) to support the 4 x 3088 kbit/s operation mode.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. The OMH unit can be replaced with the OMH-A unit without removing the services attached.5 or higher to fully support over 8M cross-connection ports.3 can be downloaded to OMH units having the version 1. and it is also referred to as the OMH-A unit in Tellabs 8000 manager starting from Release 15A..1 or higher to support extra backups for other units in the node. CCU (SCZ286) software can be any version. The version 3.3 Mbit/s data rate. 1. and 3.0 or higher to support extra backups for other units in the node.y of OMZ675 (where y=0.). Dependencies • • OMH (base unit OMH771) hardware version must be 3. . unit type must be changed to the new OMH-A type with Node Editor in Tellabs 8000 manager. 2.3 Enhancements and Fixed Bugs (compared with version 3. • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 210 10004_22 © 2008 Tellabs. SCO interface module version must be 4.

Baseband statistics corrected when line is in 1x3M. SXU-A/B (SXZ282) software version must be 10. SCO interface module version must be 4. 16.OMH/OMH-A Unit: OMZ675 Unit Software • GMX (GMZ544) software version must be 3. Dependencies • • OMH (base unit OMH771) hardware version must be 3. which is capable of 12.4 support max 139 timeslots cross-connections with over 8M cross-connection ports.17 and 3.0 or higher to support 4-pair modes.0) • • OMH-A SCO frame synchronization handling improved when 2-pair line mode is used (CR ID 300092758). SXU-V (SXZ630) software can be any version.0 or higher (OMH-A) to support the 4 x 3088 kbit/s operation mode. The OMH unit. Values seen from OMH side are more reliable. 4.1 or higher to support 3088 kbit/s line rates with Tellabs 8110 STE-10M NTU. Over 8M cross-connection ports are not supported. and 3. SXU-A/B software versions 10.2 or higher to fully support over 8M cross-connection ports.3 and 10. activation requested from neighbour unit) are not supported in case of HCO interface module in interfaces 2. Note: because of this fix line statistics may show different values in OMH side than in NTU.19. Support for 3088 kbit/s line rates and 4-pair modes with Tellabs 8110 STE-10M NTU is available in Release 14-SP3. CCU (SCZ286) software can be any version. GMX2 (GMZ802) software version can be any version. 2x3M or 4x3M mode (CR ID 300093143).18 support max 139 timeslots cross-connections with over 8M cross-connection ports. is referred to as the OMH-A unit in Release 15A. or 4. 6 and 8. Tellabs 8170 cluster node softwares CXU-M (SXZ288) and SXU-C (SXZ289) can be any version. SCO interface module version (which is based on SCO SW DPZ652 version) must be 3.3 Mbit/s data rate. • • • • • Restrictions • • The Line Loop (LiL) is not supported in case of HCO or SCO interfaces connected to any NTU. GMX software versions 3.2 Enhancements and Fixed Bugs (compared with version 3. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 211 . activation requested from neighbour NTU) and the Remote Line Loop (RLL.0 or higher to support 208 kbit/s line rates. Over 8M cross-connection ports are not supported. Tellabs 8100 manager support for this unit is available in Release 13. Support for 208 kbit/s line rates is available in Tellabs 8000 manager Release 15A.2 Version 3. • 10004_22 © 2008 Tellabs. The Neighbour Node Loop (NNL.5 or higher to fully support over 8M cross-connection ports.

SCU (SCZ280) software version must be 8. activation requested from neighbour NTU) and the Remote Line Loop (RLL. SXU-A/B software versions 10.4 support max 139 timeslots cross-connections with over 8M cross-connection ports. 4. . GMX software versions 3. GMX (GMZ544) software version must be 3.2 or higher to fully support over 8M cross-connection ports.5 or higher to fully support over 8M cross-connection ports.17 and 3. is referred to as the OMH-A unit in Release 15A. Over 8M cross-connection ports are not supported.3 Version 3. Tellabs 8170 cluster node softwares CXU-M (SXZ288) and SXU-C (SXZ289) can be any version.0.18 support max 139 timeslots cross-connections with over 8M cross-connection ports. SXU-A/B (SXZ282) software version must be 10. XCG (SMZ538) software version must be 2.4 or higher to support extra backups for other units in the node.1 This is a non-production version based on version 3.OMH/OMH-A Unit: OMZ675 Unit Software • • • • SCP (SCZ281) software version must be 3.4 supports max 139 timeslots cross-connections with over 8M cross-connection ports. XCG software version 3. or 4.1 or higher to support extra backups for other units in the node. 6 and 8. and 3. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 212 10004_22 © 2008 Tellabs.3 Mbit/s data rate.19.0 or higher to support extra backups for other units in the node. Over 8M cross-connection ports are not supported.3 and 10. Tellabs 8100 manager support for this unit is available in Release 13. The OMH unit.5 or higher to fully support over 8M cross-connection ports. activation requested from neighbour unit) are not supported in case of HCO interface module in interfaces 2. GMX2 (GMZ802) software version can be any version. 16. SCU-H (SCZ545) software version must be 1. The Line Loop (LiL) is not supported in case of HCO or SCO interfaces connected to any NTU.6 or higher to support unlocking the ports without failures. Support for 208 kbit/s line rates is available in Tellabs 8000 manager Release 15A. • • • • • • Restrictions • • • OMH-A with HCO module cannot use bit rate 72x64kbps (CR ID 300091819 and CR ID 300108076). which is capable of 12. The Neighbour Node Loop (NNL. Support for 3088 kbit/s line rates and 4-pair modes with Tellabs 8110 STE-10M NTU is available in Release 14-SP3. SXU-V (SXZ630) software can be any version.

• Dependencies • • OMH (base unit OMH771) hardware version must be 3.19. SCO interface module version must be 4. or 4.6 or higher to support unlocking the ports without failures. Tellabs 8100 manager support for this unit is available in Release 13.OMH/OMH-A Unit: OMZ675 Unit Software 16.0 or higher to support extra backups for other units in the node.0 or higher to support 4-pair modes. XCG (SMZ538) software version must be 2.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). SXU-A/B (SXZ282) software version must be 10.0 or higher (OMH-A) to support the 4 x 3088 kbit/s operation mode.1 or higher to support 3088 kbit/s line rates with Tellabs 8110 STE-10M NTU. Tellabs 8170 cluster node softwares CXU-M (SXZ288) and SXU-C (SXZ289) can be any version. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 213 .2 or higher to fully support over 8M cross-connection ports.1 or higher to support extra backups for other units in the node.17 and 3. SXU-V (SXZ630) software can be any version. GMX (GMZ544) software version must be 3. Over 8M cross-connection ports are not supported.0 Enhancements (compared with version 2.3 Mbit/s data rate. is referred to as the OMH-A unit in Release 15A. and 3. SXU-A/B software versions 10. A top data rate of 12. GMX software versions 3.0 supports 208 kbit/s line rates in 1 and 2-pair modes. SCU (SCZ280) software version must be 8. Support for 208 kbit/s line rates is available in Tellabs 8000 manager Release 15A. which is capable of 12.4 or higher to support extra backups for other units in the node.5 or higher to fully support over 8M cross-connection ports.0) • OMH-A hardware (version 3.18 support max 139 timeslots cross-connections with over 8M cross-connection ports.4 supports max 139 timeslots cross-connections with over 8M cross-connection ports. SCU-H (SCZ545) software version must be 1. • • • • • • • • • • 10004_22 © 2008 Tellabs.5 or higher to fully support over 8M cross-connection ports. The OMH unit. SCP (SCZ281) software version must be 3. and 3.4 support max 139 timeslots cross-connections with over 8M cross-connection ports.0 or higher to support 208 kbit/s line rates. Over 8M cross-connection ports are not supported.4 Version 3.0 or higher) and SCO interface module support 3088 kbit/s line rate in 4-pair mode. SCO interface module version (which is based on SCO SW DPZ652 version) must be 3.3 and 10. Support for 3088 kbit/s line rates and 4-pair modes with Tellabs 8110 STE-10M NTU is available in Release 14-SP3. CCU (SCZ286) software can be any version. New SCO interface module version 4. XCG software version 3.

1 or higher to support extra backups for other units in the node. SCO supports 592. GMX (GMZ544) software version must be 3. SCU-H (SCZ545) software version must be 1. 2064.0. SXU-A/B software versions 10. GMX software versions 3.17 and 3. XCG (SMZ538) software version must be 2. activation requested from neighbour unit) are not supported in case of HCO interface module in interfaces 2. 1168. CCU (SCZ286) software can be any version.6 or higher to support unlocking the ports without failures. 16.2 Mbit/s can be reached by using the 4 x 2320 kbit/s operation mode together with Tellabs 8110 STE-10M NTU. 2320 and 3088 kbit/s line rates in 1. XCG software version 3. "Ntu power off" fault service status is changed to be "Service affecting fault" (S). or 4. 2064 and 2320 kbit/s line rates in 4-pair mode. • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 214 10004_22 © 2008 Tellabs. • Dependencies • • OMH (base unit OMH771) hardware version must be 1. SCU (SCZ280) software version must be 8. and 3. activation requested from neighbour NTU) and the Remote Line Loop (RLL. A top data rate of 9. SXU-V (SXZ630) software can be any version. 4. Over 8M cross-connection ports are not supported.5 or higher to fully support over 8M cross-connection ports. 6 and 8.18 support max 139 timeslots cross-connections with over 8M cross-connection ports. and 592.0 or higher to support 4-pair modes.19.2 or higher to fully support over 8M cross-connection ports.5 or higher to fully support over 8M cross-connection ports.and 2-pair modes.5 Version 2.0 or 2.3 and 10. SXU-A/B (SXZ282) software version must be 10.1 or higher to support 3088 kbit/s line rates with Tellabs 8110 STE-10M NTU. "Ntu power off" interface fault masks "Rx signal missing" fault. In addition. The Neighbour Node Loop (NNL. SCP (SCZ281) software version must be 3.0 or higher to support extra backups for other units in the node.2) • OMH unit with new SCO interface module supports new Tellabs 8110 STE-10M network terminating unit.4 supports max 139 timeslots cross-connections with over 8M cross-connection ports.0 Enhancements (compared with version 1. SCO interface module version (which is based on SCO SW DPZ652 version) must be 3.4 or higher to support extra backups for other units in the node.OMH/OMH-A Unit: OMZ675 Unit Software Restrictions • • The Line Loop (LiL) is not supported in case of HCO or SCO interfaces connected to any NTU. and 3. 1168. .4 support max 139 timeslots cross-connections with over 8M cross-connection ports.

CXU-M (SXZ288) software can be any version. activation requested from neighbour NTU) and the Remote Line Loop (RLL.6 or higher to support unlocking the ports without failures. 10004_22 © 2008 Tellabs. XCG (SMZ538) software version must be 2. Restrictions • • • Cross-connections to timeslot 144 and above that are not supported. The Neighbour Node Loop (NNL. 6 and 8.0 or 2. Support for 3088 kbit/s line rates and 4-pair modes with Tellabs 8110 STE-10M NTU is available in Release 14-SP3. SXU-C (SXZ289) software can be any version.0 or higher to support extra backups for other units in the node. GMX (GMZ544) software can be any version. Tellabs 8100 manager support for this unit is available in Release 13. Tellabs 8100 manager support for this unit is available in Release 13. 16.2 Dependencies • • • • • • • • • • • • OMH (base unit OMH771) hardware version must be 1. SXU-V (SXZ630) software can be any version. SCU-H (SCZ545) software version must be 1. SCP (SCZ281) software version must be 3. activation requested from neighbour unit) are not supported in case of HCO interface module in interfaces 2. The Line Loop (LiL) is not supported in case of HCO or SCO interfaces connected to any NTU. 6 and 8. The Neighbour Node Loop (NNL. SXU-A/B (SXZ282) software can be any version.4 or higher to support extra backups for other units in the node.1 or higher to support extra backups for other units in the node.0. Over 8M cross-connection ports are not supported. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 215 . Restrictions • • The Line Loop (LiL) is not supported in case of HCO or SCO interfaces connected to any NTU. activation requested from neighbour unit) are not supported in case of HCO interface module in interfaces 2. SCU (SCZ280) software version must be 8.6 Version 1. 4. CCU (SCZ286) software can be any version. 4. activation requested from neighbour NTU) and the Remote Line Loop (RLL.OMH/OMH-A Unit: OMZ675 Unit Software • • Tellabs 8170 cluster node softwares CXU-M (SXZ288) and SXU-C (SXZ289) can be any version.

0 or higher.x can be downloaded to QMH units having the version 1.0 or higher. Tellabs 8160 A111 and Tellabs 8170 cluster nodes as well as in Tellabs 8184 and Tellabs 8188 access switches. GMX2 (GMZ802) software version can be any version. 1. 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). Tellabs® 8100 Managed Access System Unit Software Version Dependencies 216 10004_22 © 2008 Tellabs.x software versions) or the QMH-M unit (whose base unit is QMH740) (6. Dependencies • • • • • • • • • • • • • • • QMH (base unit QMH509) hardware version must be 3. SXU-C (SXZ289) software version can be any version.x and 10. SCP (SCZ281) software version can be any version.x PROMs of QMZ540 (where x=0. The version 10. CXU-M (SXZ288) software version can be any version. The version 1. . 2. SCU (SCZ280) software version can be any version.1 or higher.x can be downloaded to QMH-M units having the version 6. GMH (GMZ283) software version can be any version.11 can be downloaded to QMH units having the version 10. XCG (SMZ538) software version must be 2. 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.6 or higher.). The version 6. SXU-V (SXZ630) software version must be 1.x PROMs of QMZ540. 17.x software versions) in Tellabs 8140 midi.x PROMs of QMZ540. SCU-H (SCZ545) software version must be 1..11 Enhancements and Fixed Bugs • The reason for this release is fixes in 1+1 protection functionality. Tellabs 8150 basic.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. CCU (SCZ286) software version can be any version. SXU-A/B (SXZ282) software version can be any version.. GMX (GMZ544) software version can be any version.1 Version 10.

SXU-V (SXZ630) software version must be 1.QMH and QMH-M Units: QMZ540 Unit Software Restrictions • This software version does not support QMH-M (QMH740) unit. CXU-M (SXZ288) software version can be any version. MartisDXX Manager support for the pilot bit and ring protection are available in Release 12 or higher. Restrictions • This software version does not support QMH-M (QMH740) unit. Bugs • A replacement unit shows a wrong fault status. the Ntu power off fault service status is changed to a Service affecting fault (S). Tellabs® 8100 Managed Access System Unit Software Version Dependencies 217 . PMA. 17.6 or higher. CCU (SCZ286) software version can be any version. SCU (SCZ280) software version can be any version. In addition. SXU-C (SXZ289) software version can be any version. 10004_22 © 2008 Tellabs.2 Version 10. In this software version “Ntu power fault” interface fault masks the “Loss of input signal” fault. SXU-A/B (SXZ282) software version can be any version. SCU-H (SCZ545) software version must be 1. Tellabs 8100 manager supports the enhanced interface fault masking in Release 13 or higher. in 1+1 protected trunk mode if a protecting trunk fails. XCG (SMZ538) software version must be 2.0 or higher.1 or higher.0 or higher. GMX2 (GMZ802) software version can be any version.10 Enhancements and Fixed Bugs • The reason for this release is changes in fault handling (CR ID 300023242). GMH (GMZ283) software version can be any version. Thus NTU power off will cause just “Ntu power fault” fault. Dependencies • • • • • • • • • • • • • • • QMH (base unit QMH509) hardware version must be 3. GMX (GMZ544) software version can be any version. SCP (SCZ281) software version can be any version.

Restrictions • This software version does not support QMH-M (QMH740) unit. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 218 10004_22 © 2008 Tellabs. CXU-M (SXZ288) software version can be any version. (CR ID 300089699) 17. CCU (SCZ286) software version can be any version. .9 This version is based on a test version 10. SXU-C (SXZ289) software version can be any version. MartisDXX Manager support for the pilot bit and ring protection are available in Release 12 or higher. XCG (SMZ538) software version must be 2.0 or higher. Enhancements and Fixed Bugs • Changing interface module type allowed while unit is out of inventory.1 or higher.3 Version 10. SCP (SCZ281) software version can be any version.6 or higher. GMX (GMZ544) software version can be any version. SCU (SCZ280) software version can be any version. Tellabs 8100 manager supports the enhanced interface fault masking in Release 13 or higher.QMH and QMH-M Units: QMZ540 Unit Software Bugs • • A replacement unit shows a wrong fault status. 1+1 protection switch does not work reliably if an interface is configured in 2M unframed mode. (CR ID 200012191) Dependencies • • • • • • • • • • • • • • QMH (base unit QMH509) hardware version must be 3. in 1+1 protected trunk mode if a protecting trunk fails. PMA.91. SXU-V (SXZ630) software version must be 1. SCU-H (SCZ545) software version must be 1. SXU-A/B (SXZ282) software version can be any version. GMH (GMZ283) software version can be any version.0 or higher.

SCU-H (SCZ545) software version must be 1. Restrictions • This software version does not support QMH-M (QMH740) unit. in 1+1 protected trunk mode if a protecting trunk fails.QMH and QMH-M Units: QMZ540 Unit Software Bugs • • A replacement unit shows a wrong fault status. CXU-M (SXZ288) software version can be any version.4 Version 10. SXU-C (SXZ289) software version can be any version. (CR ID 200009698) Reliability of restoring backups in a boot phase has been improved. 1+1 protection switch does not work reliably if an interface is configured in 2M unframed mode. PMA. CCU (SCZ286) software version can be any version. SXU-A/B (SXZ282) software version can be any version.0 or higher. (CR ID 300089699) 17.0 or higher. 10004_22 © 2008 Tellabs. MartisDXX Manager support for the pilot bit and ring protection are available in Release 12 or higher.6 or higher. GMX (GMZ544) software version can be any version. (CR ID 200010516) Dependencies • • • • • • • • • • • • • • QMH (base unit QMH509) hardware version must be 3.1 or higher. SCU (SCZ280) software version can be any version.111. GMH (GMZ283) software version can be any version. Tellabs 8100 manager supports the enhanced interface fault masking in Release 13 or higher. Enhancements and Fixed Bugs • • Robustness of internal node communication has been improved. SXU-V (SXZ630) software version must be 1. SCP (SCZ281) software version can be any version.8 This version is based on a test version 10. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 219 . XCG (SMZ538) software version must be 2.

7 Enhancements and Fixed Bugs • Enhancement for production testing. in 1+1 protected trunk mode if a protecting trunk fails. Restrictions • This software version does not support QMH-M (QMH740) unit. MartisDXX Manager support for the pilot bit and ring protection are available in Release 12 or higher. GMX (GMZ544) software version can be any version. SXU-C (SXZ289) software version can be any version. Tellabs 8100 manager supports the enhanced interface fault masking in Release 13 or higher.0 or higher. SXU-A/B (SXZ282) software version can be any version. SCU (SCZ280) software version can be any version. PMA. SCP (SCZ281) software version can be any version. SXU-V (SXZ630) software version must be 1. GMH (GMZ283) software version can be any version. (CR ID 300089699) Tellabs® 8100 Managed Access System Unit Software Version Dependencies 220 10004_22 © 2008 Tellabs. 1+1 protection switch does not work reliably if an interface is configured in 2M unframed mode. . 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.5 Version 10. SCU-H (SCZ545) software version must be 1. CCU (SCZ286) software version can be any version.0 or higher.1 or higher.6 or higher. PMA. (CR ID 200005560) Dependencies • • • • • • • • • • • • • • QMH (base unit QMH509) hardware version must be 3. XCG (SMZ538) software version must be 2. Bugs • • A replacement unit shows a wrong fault status.QMH and QMH-M Units: QMZ540 Unit Software Bugs • • A replacement unit shows a wrong fault status. (CR ID 300089699) 17. CXU-M (SXZ288) software version can be any version.

Tellabs 8100 Manager supports the enhanced interface fault masking in Release 13 or higher.6 or higher.1 or higher. CXU-M (SXZ288) software version can be any version. (CRF ID 4004099) Clock status DNU is sent via NNM if a unit can not get locked to a node clock. Enhancements and Fixed Bugs • • • • • • • • • HCQ errors are directed to specific interface. 10004_22 © 2008 Tellabs. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 221 . (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.6 This is a non-production version and this should not be used when the next official version is available. SCP (SCZ281) software version can be any version. XCG (SMZ538) software version must be 2. Dependencies • • • • • • • • • • • • • • QMH (base unit QMH509) hardware version must be 3.0 or higher. SXU-V (SXZ630) software version must be 1. GMH (GMZ283) software version can be any version. CCU (SCZ286) software version can be any version. SCU (SCZ280) software version can be any version. (CRF ID 4004922). not monitored and fault mask on. SCU-H (SCZ545) software version must be 1.QMH and QMH-M Units: QMZ540 Unit Software 17. SXU-C (SXZ289) software version can be any version. (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 to the specific line number. MartisDXX Manager support for the pilot bit and ring protection are available in Release 12 or higher. SXU-A/B (SXZ282) software version can be any version.0 or higher. GMX (GMZ544) software version can be any version.6 Version 10.

GMH (GMZ283) software version can be any version. Bugs • • A replacement unit shows a wrong fault status. in 1+1 protected trunk mode if a protecting trunk fails. SXU-C (SXZ289) software version can be any version. SCP (SCZ281) software version can be any version. (CRF ID 4004149 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 222 10004_22 © 2008 Tellabs. XCG (SMZ538) software version must be 2. 1+1 protection switch does not work reliably if an interface is configured in 2M unframed mode.6 or higher. Bugs • Clock status sending in QMH doesn’t work when SXU fails.0 or higher. NMS can now disable download QMH software.0 or higher. CCU (SCZ286) software version can be any version. SXU-A/B (SXZ282) software version can be any version.5 Enhancements • • • This software version supports freely allocated pilot bit. SCU-H (SCZ545) software version must be 1. SCU (SCZ280) software version can be any version. PMA. This software version supports HCQ (HCQ739) module. CXU-M (SXZ288) software version can be any version. (CRF ID 4003834) Dependencies • • • • • • • • • • • • • QMH (base unit QMH509) hardware version must be 3. Restrictions • This software version does not support QMH-M (QMH740) unit. GMX (GMZ544) software version can be any version. (CR ID 300089699) 17.1 or higher. MartisDXX Manager support for the pilot bit and ring protection are available in Release 12 or higher. SXU-V (SXZ630) software version must be 1. .7 Version 10.QMH and QMH-M Units: QMZ540 Unit Software Restrictions • This software version does not support QMH-M (QMH740) unit.

CCU (SCZ286) software version can be any version.g. This software version supports the ring protection mode. SXU-C (SXZ289) software version can be any version.0 Hardware (e. (CRF ID 4004149) 1+1 protection switch does not work reliably if an interface is configured in 2M unframed mode.6 or higher. Dependencies • • • • • • • • • • • • QMH (base unit QMH509) hardware version must be 3. This software version does not support HCQ (HCQ739) module. This software version does not support SXU-V (SXU758) unit. SCU-H (SCZ545) software version must be 1.QMH and QMH-M Units: QMZ540 Unit Software • 1+1 protection switch does not work reliably if an interface is configured in 2M unframed mode. QDX Asic).8 Version 10. Restrictions • • • • This software version does not support QMH-M (QMH740) unit. SCP (SCZ281) software version can be any version. MartisDXX Manager support for the QMH unit is available in Release 11 Service Pack 1 or higher. available time (AT) is always 100% even if both trunks have been simultaneously cut. GMX (GMZ544) software version can be any version.0 or higher. (CR ID 300089699)) 17.0 or higher. Bugs • When creating a G. CXU-M (SXZ288) software version can be any version. XCG (SMZ538) software version must be 2. (CR ID 300089699) • • 10004_22 © 2008 Tellabs.3 Enhancements • • This software version is an update for the QMH509 v3. This software version does not support freely allocated pilot bit. GMH (GMZ283) software version can be any version. (CRF ID 4003959) Clock status sending in QMH doesn’t work when SXU fails. SCU (SCZ280) software version can be any version. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 223 .821 Report for 1+1 protected trunks in Performance Management System. SXU-A/B (SXZ282) software version can be any version.

SXU-C (SXZ289) software version can be any version. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 224 10004_22 © 2008 Tellabs.0 Dependencies • • • • • • • • • • • • • QMH-M (QMH740) hardware version must be 1.9 Version 6.6 or higher. .QMH and QMH-M Units: QMZ540 Unit Software 17.0. SCU (SCZ280) software version can be any version. Restrictions • • • • • This software version does not support HCQ (HCQ739) module. CCU (SCZ286) software version can be any version. This software version does not support BTQ-1088 and BTQ-2304 modules. SCP (SCZ281) software version can be any version. This software version does not support QMH unit.0 or higher. SXU-A/B (SXZ282) software version can be any version. MartisDXX Manager support for the QMH unit is available in Release 11 Service Pack 1 or higher.1 or higher. This software version does not support framed mode. XCG (SMZ538) software version must be 2. SCU-H (SCZ545) software version must be 1. QMH-M does not support SXU-V in V5. SXU-V (SXZ630) software version must be 1. 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.2 use Bugs • No known bugs.

Restrictions • • • This software version does not support ring protection. MartisDXX Manager support for the pilot bit is available in Release 12 service pack 1 or higher.QMH and QMH-M Units: QMZ540 Unit Software 17. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 225 . 10004_22 © 2008 Tellabs.1 or higher.6. SXU-C (SXZ289) software version can be any version.6 This is a version based on QMZ540 version 1. XCG (SMZ538) software version must be 2. SXU-A/B (SXZ282) software version can be any version.6 or higher. CCU (SCZ286) software version can be any version.5 with features from QMZ540 version 10. CXU-M (SXZ288) software version can be any version.0 or higher.x) must be used. SXU-V (SXZ630) software version must be 1. SCU (SCZ280) software version can be any version. (CR ID 300089699). GMX (GMZ544) software version can be any version. GMH (GMZ283) software version can be any version. Bugs • 1+1 protection switch does not work reliably if an interface is configured in 2M unframed mode. GMX2 (GMZ802) software version can be any version. SCP (SCZ281) software version can be any version.10 Version 1.x or 2. (CRF ID 4004440) AIS fault is restrained with equipment loop when pilot bit is set (CRF ID 4004569) Dependencies • • • • • • • • • • • • • • QMH (QMH509) hardware (1. This software version does not support HCQ module. This software version does not support QMH-M unit. SCU-H (SCZ545) software version must be 1. 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.

QMH and QMH-M Units: QMZ540 Unit Software 17.0 or higher. (CRF ID 4003959). (CRF ID 4003834) QMH IF4 fault history does not report any more too many “MUX/DEMUX back to line” alarms. . This software version does not support QMH-M unit. Bugs • • Line loop does not work in interfaces.11 Version 1. SCP (SCZ281) software version can be any version. Restrictions • • • This software version does not support ring protection. (CRF ID 4004404) Clock status sending in QMH doesn’t work when SXU fails. NMS can now disable download QMH software. SXU-C (SXZ289) software version can be any version. CXU-M (SXZ288) software version can be any version.x) must be used.x or 2.5 This is a version based on QMZ540 version 1. where pilotbit parameters are set on. This software version does not support HCQ module. SCU (SCZ280) software version can be any version. GMH (GMZ283) software version can be any version. SXU-A/B (SXZ282) software version can be any version. This software version supports SXU-V. GMX (GMZ544) software version can be any version. This software version supports a G. (CRF ID 40003924) Dependencies • • • • • • • • • • • • QMH (QMH509) hardware (1. Enhancements and Fixed Bugs • • • • • This software version supports freely allocated pilot bit.6 or higher.5. CCU (SCZ286) software version can be any version.821 Report for 1+1 protected trunks in Performance Management System. MartisDXX Manager support for the pilot bit is available in Release 12 service pack 1 or higher. XCG (SMZ538) software version must be 2.4 with features from QMZ540 version 10. (CRF ID 4004149) Tellabs® 8100 Managed Access System Unit Software Version Dependencies 226 10004_22 © 2008 Tellabs. SCU-H (SCZ545) software version must be 1.

12 Version 1.6 or higher. available time (AT) is always 100% even if both trunks have been simultaneously cut. SXU-A/B (SXZ282) software version can be any version. SCP (SCZ281) software version can be any version. CXU-M (SXZ288) software version can be any version.QMH and QMH-M Units: QMZ540 Unit Software 17. (CRF ID 4004404) Clock status sending in QMH doesn’t work when SXU fails.0 or higher.x or 2. GMH (GMZ283) software version can be any version. (CRF ID 40003924) Dependencies • • • • • • • • • • • • QMH (QMH509) hardware (1. SXU-C (SXZ289) software version can be any version. XCG (SMZ538) software version must be 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 227 . SCU (SCZ280) software version can be any version. CCU (SCZ286) software version can be any version. GMX (GMZ544) software version can be any version. MartisDXX Manager support for the pilot bit is available in Release 12 service pack 1 or higher. Bugs • • • Line loop does not work in interfaces. where pilotbit parameters are set on. NMS can now disable download QMH software.5. 10004_22 © 2008 Tellabs.x) must be used.3 with some features from QMZ540 version 10. (CRF ID 4004149) When creating a G. Restrictions • • • This software version does not support ring protection. (CRF ID 4003834) QMH IF4 fault history does not report any more too many “MUX/DEMUX back to line” alarms.821 Report for 1+1 protected trunks in Performance Management System. SCU-H (SCZ545) software version must be 1. This software version does not support QMH-M unit.4 This is an unofficial version based on QMZ540 version 1. This software version does not support HCQ module. This software version supports SXU-V. Enhancements and Fixed Bugs • • • • This software version supports freely allocated pilot bit. (CRF ID 4003959).

QMH and QMH-M Units: QMZ540 Unit Software 17.3 Dependencies • • QMH (QMH509) hardware (1. (CRF ID 4004149) • 17.x or 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 228 10004_22 © 2008 Tellabs. This software version does not support QMH-M unit. Bugs • The following faults reported from IF4 are not constant when a fault is active: MUX/DMUX back to line. This software version does not support HCQ module. Restrictions • • • • • • This software version does not support ring protection. This software version does not support pilot bit. Line Loop made by neighbour. This software version does not support QMH-M unit.x) must be used. Restrictions • • • • • This software version does not support ring protection. This software version does not support HCQ module.x) must be used.2 Emergency version! Dependencies • QMH (QMH509) hardware (1.14 Version 1. . This software version does not support BTQ-1088 and BTQ-2304 modules. This software version does not support SXU-V unit. This software version does not support SXU-V unit. MartisDXX Manager support for this unit is available in Release 10. Remote controlled line loop and AIS in signalling.0 or higher.13 Version 1. Clock status sending in QMH doesn’t work when SXU fails. This software version does not support pilot bit.x or 2.

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 software version does not support HCQ module. it may cause neighbour node monitoring to fail to communicate with the node connected to the interface.QMH and QMH-M Units: QMZ540 Unit Software Bugs • When the interface use of any of the four interfaces is changed from MUAP/SUAP to general.x) must be used. When the interface use of any of the four interfaces is changed from MUAP/SUAP to general and HDLC parameters are changed. Bugs • If NNM parameters are monitored and a hard/physical loop is placed. This happens only on interface 1. and the HDLC parameters are changed. The following faults reported from IF4 are not constant when a fault is active: MUX/DMUX back to line. 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. 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).1 Dependencies • QMH (QMH509) hardware (1. NNM sees the loop correctly. Clock status sending in QMH doesn’t work when SXU fails. This software version does not support QMH-M unit.x or 2.15 Version 1. If the loop is taken off. Restrictions • • • • • • This software version does not support ring protection. Clock status sending in QMH doesn’t work when SXU fails. it may cause neighbour node nonitoring to fail to communicate with the node connected to the interface. Remote controlled line loop and AIS in signalling. (CRF ID 4004149) • • • 10004_22 © 2008 Tellabs. The same happens if a trunk is connected from interface 1. When QMH is configured as 1+1 mode. NNM fails to detect the changed condition and reports NO CONNECTION state. (CRF ID 4004149) • • • 17. Line Loop made by neighbour. This software version does not support pilot bit. This software version does not support BTQ-1088 and BTQ-2304 modules. This software version does not support SXU-V unit. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 229 . 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.

x) must be used. This happens only on interface 1. Restrictions • • • • • • This software version does not support ring protection. it may cause neighbour node monitoring to fail to communicate with the node connected to the interface. 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 software version does not support SXU-V unit. NNM fails to detect the changed condition and reports NO CONNECTION state. Bugs • • • The IA activity missing alarm can become activated without a reason. The same happens if a trunk is connected from interface 1. If NNM parameters are monitored and a hard/physical loop is placed. 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. When the interface use of any of the four interfaces is changed from MUAP/SUAP to general.0 Dependencies • QMH (QMH509) hardware (1. Clock status sending in QMH doesn’t work when SXU fails. This software version does not support pilot bit. NNM sees the loop correctly. Not completely tested. This software version does not support HCQ module.QMH and QMH-M Units: QMZ540 Unit Software 17. and HDLC parameters are changed.16 Version 1. This software version does not support QMH-M unit.x or 2. This software version does not support BTQ-1088 and BTQ-2304 modules. (CRF ID 4004149) • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 230 10004_22 © 2008 Tellabs. If the loop is taken off. . When QMH is configured in 1+1 mode.

Upgrading the unit to USW version 2. which means that it is always shown when the received trace identifier does not match with the expected one. However. Version is functionally identical to version 2. The previously explained feature does not affect the trace identifier mismatch fault (TIM). however. changing the expected parameters.2 by downloading is however recommended for units that have USW 2.1 Version 2. It is. It is not possible to change Trail Trace Identifier if SNC/I protection is used. 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. • • 10004_22 © 2008 Tellabs. possible to manually update the field in this case by e. if the count is 0 there have not been errors. the received TTI which does not comply with the standard format is not displayed in the field.8 or higher. GMX (GMZ544) software version must be 3.0 or higher.1 Enhancements and Fixed Bugs (compared with version 1. Restrictions • • SNC/N protection cannot be used in GMX if the SBU units are used in the node. if the transmitter sends constant null character.g.1. 18. MartisDXX Manager support for this unit is available in Release 11 Service Pack 2 or higher. 18. there have been an unknown number of errors. The same applies to the empty field.2 This is emergency version to fix flash driver problem first detected in GMX. HDB3 counters do not indicate the exact number of errors unless the count is 0. In SBU unit functional flash related problems have not been found. Dependencies • • • SBU hardware version must be 2. the field shows the latest valid TTI with CRC-7 and the field is not updated.e. Therefore.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.0) • Support for new flash. i.2 Version 2. If the count is other than zero.1 to prevent the small possibility of flash problem. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 231 .

x. which means that it is always shown when the received trace identifier does not match with the expected one. MartisDXX Manager support for this unit is available in Release 11 Service Pack 2 or higher. 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. Restrictions • • SNC/N protection cannot be used in GMX if the SBU units are used in the node. 18. The same applies to the empty field. . changing the expected parameters. however. Therefore. • • Bugs • No known bugs.8 or higher.0 Dependencies • • • SBU (base unit UTU720) hardware version must be 1. there have been an unknown number of errors. However. It is not possible to change Trail Trace Identifier if SNC/I protection is used.3 Version 1. GMX (GMZ544) software version must be 3.SBU UNIT: UTZ549 Unit Software Bugs • No known bugs. if the count is 0 there have not been errors. HDB3 counters do not indicate the exact number of errors unless the count is 0. If the count is other than zero.e. i. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 232 10004_22 © 2008 Tellabs.g. the field shows the latest valid TTI with CRC-7 and the field is not updated. the received TTI which does not comply with the standard format is not displayed in the field. if the transmitter sends constant null character. The previously explained feature does not affect the trace identifier mismatch fault (TIM). possible to manually update the field in this case by e. It is.

(CR ID 300056272) Metalink firmware 6.0 or higher.0 or higher (board with FPGA) but this software does not support ESHDSL modes in this hardware. Restrictions • • Neighbor node loop does not work with 1x208k and 2x208k line modes (because 114 clocking cannot be set at CTE in these modes). Dependencies • • • • Tellabs SCO 786 hardware version must be 3. Bugs • No known bugs. 10004_22 © 2008 Tellabs.4 in use.1 Version 4. when one line is without attenuation and there is attenuation in the other line.822. OMH (OMZ675) software version must be 3.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.1) • • Support for ESHDSL line modes. "power back-off" may be ON or may be OFF for both lines.0 or higher (board with FPGA). Tellabs 8100 network manager ESHDSL support is available in Release 15A or higher.1 Enhancements and Fixed Bugs (compared with version 3. In case of two-pair mode. 19. Tellabs SCO785 hardware version must be 3. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 233 .

4-pair modes added.821. Tellabs SCO785 hardware version must be 2.SCO Module: DPZ652 DSP Software 19. Tellabs SCO785 hardware version must be 3.0 or higher (board with FPGA). I=1.4 Enhancements and Fixed Bugs (compared with version 1. Support for N=32 interoperable mode is available in Release R13A Service Pack 5. master. when one line is without attenuation and there is attenuation in the other line. Dependencies • • • • Tellabs SCO786 hardware version must be 2.3) • • New interoperable mode (N=32.0 or higher to support 4-pair modes and n=48 modes. Restrictions • In case of two-pair mode.0 or lower (without FPGA). Grouped 1-pair operation fixed to be more reliable. 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. OMH (OMZ675) software version must be 1.0 or lower (without FPGA).9 in use.2 or higher to support SCO module. Metalink firmware 6.2 Version 3. .3 Version 1.4) • • • 48x64 modes added. OMH (OMZ675) software version must be 2. 19. Dependencies • • • • Tellabs SCO786 hardware version must be 3. Tellabs 8100 manager support for this unit is available in Release 13. "power back-off" may be ON or may be OFF for both lines.0 or higher (board with FPGA).1 Enhancements and Fixed Bugs (compared with version 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 234 10004_22 © 2008 Tellabs. no EOC) added. Bugs • No known bugs.

Compatible with ESU. OMH (OMZ675) software version must be 1. Tellabs 8100 manager support for this unit is available in Release 13 or higher. Dependencies • • • • Tellabs SCO786 hardware version must be 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 235 . Dependencies • • • • Tellabs SCO786 hardware version must be 2. Bugs • Grouped 1-pair mode may not activate when after changing modes. Restrictions • In case of two-pair mode.4 Version 1. Bugs • No known bugs. 19.82.SCO Module: DPZ652 DSP Software Restrictions • In case of two-pair mode. Tellabs SCO785 (for ESU) is not supported. OMH (OMZ675) software version must be 1.2 or higher to support SCO module.8 in use. when one line is without attenuation and there is attenuation in the other line. Tellabs 8100 manager support for this unit is available in Release 13 or higher. Tellabs SCO785 hardware version must be 2.0 or lower (without FPGA). "power back-off" may be ON or may be OFF for both lines.0 or lower (without FPGA). when one line is without attenuation and there is attenuation in the other line. 10004_22 © 2008 Tellabs.2) • • Metalink firmware 6.2 or higher to support SCO module.5 Version 1.1 Enhancements and Fixed Bugs • This is the first official version. 19. "power back-off" may be ON or may be OFF for both lines.0 or lower (without FPGA).3 Enhancements and Fixed Bugs (compared with version 1.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies 236 10004_22 © 2008 Tellabs. Bugs • No known bugs. .SCO Module: DPZ652 DSP Software Restrictions • In case of two-pair mode. "power back-off" may be ON or may be OFF for both lines. when one line is without attenuation and there is attenuation in the other line.

For example. Restrictions • • This version cannot be downloaded to SCU-H which has software version 1. GMX2 (GMZ802) software version can be any version.0 cannot be downloaded if boot code version is 1. MartisDXX Manager support for this unit/interface card/functionality is available in Release 10.6 Enhancements and Fixed Bugs (compared with version 2. GMX (GMZ544) software version can be any version.5. Tellabs 8184 access switch.2) • Support for GMX2.g. they are compatible if and only if a = c. boot software and downloadable software.1 or higher.1A Service Pack 3 or higher. SXU-A/B (SXZ282) software version can be any version. Tellabs 8160 A111. SXU-C (SXZ289) software version can be any version.1 Version 2.d. Tellabs 8188 access switch and Tellabs 8170 cluster nodes. 10004_22 © 2008 Tellabs. If the boot version is a. SCP-H does not allow a shorter address mask than its IP address class requires (e. downloadable code 2. 20. SXU-V (SXZ630) software version must be 1.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 8184 access switch and Tellabs 8188 access switch. Bugs • • Removing lower (active) GMX from inventory does not activate upper GMX. Dependencies • • • • • • • SCU-H base unit hardware version must be 2.x.0 or higher to support Tellabs 8170 cluster node. The major version number indicates if the boot code is compatible with the downloadable code.b and the downloadable version is c. the minimum requirement for the address mask length is 24 bits). if class C IP address is used. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 237 . Passive GMX is not activated when active GMX download is finished.

3 Version 2. SCP-H does not allow a shorter address mask than its IP address class requires (e. Restrictions • • This version cannot be downloaded to SCU-H which has software version 1. GMX2 is not activated when GMX1 (active) download is finished. MartisDXX Manager support for this unit/interface card/functionality is available in Release 10.1 or higher. SXU-C (SXZ289) software version can be any version.14) • Support for new flash. Dependencies • • • • • • SCU-H base unit hardware version must be 2. .1. SXU-V (SXZ630) software version must be 1. the minimum requirement for the address mask length is 24 bits). In SCU-H unit functional flash related problems have not been found.1 Enhancements and Fixed Bugs (compared with version 1. Version is functionally identical to version 2. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version can be any version.0 or higher to support Tellabs 8170 cluster node.1A Service Pack 3 or higher.2 by downloading is however recommended for units that have USW 2.x.2 This is emergency version to fix flash driver problem first detected in GMX. Bugs • • Removing lower (active) GMX from inventory does not activate upper GMX. Upgrading the unit to USW version 2. 20.2 Version 2.g.SCU-H UNIT: SCZ545 Unit Software 20. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 238 10004_22 © 2008 Tellabs. if class C IP address is used.1 to prevent the small possibility of flash problem.

SCU-H UNIT: SCZ545 Unit Software 20.1 or higher to support Tellabs 8170 cluster node.18 Enhancements and Fixed Bugs (compared with version 1.14) • Support for GMX2. Bugs • • Removing lower (active) GMX from inventory does not activate upper GMX. Restrictions • • • Extended links do not work correctly with GMX if GMX SW version is under 3.13) • • • SCU-H USW 1. Passive GMX is not activated when active GMX download is finished. Dependencies • • • • • • • SCU-H (base unit SCU587) hardware version must be 1.4 Version 1. if class C IP address is used.g. MartisDXX Manager support for this unit/interface card/functionality is available in Release 10. the minimum requirement for the address mask length is 24 bits).1 or higher. Tellabs 8184 access switch and Tellabs 8188 access switch. GMX (GMZ544) software version can be any version.6.1. Tellabs 8170 cluster node support does not work if SCU-H HW version is under 1.5 Version 1. SXU-C (SXZ289) software version can be any version.14 Enhancements and Fixed Bugs (compared with version 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 239 . GMX2 (GMZ802) software version can be any version.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. SXU-A/B (SXZ282) software version can be any version. SCP-H does not allow a shorter address mask than its IP address class requires (e. SXU-V (SXZ630) software version must be 1. 20.1A Service Pack 3 or higher.

1 or higher to support Tellabs 8170 cluster node. SXU-A/B (SXZ282) software version can be any version. 20. SXU-V (SXZ630) software version must be 1. the minimum requirement for the address mask length is 24 bits). SXU-C (SXZ289) software version can be any version. Restrictions • • • Extended links do not work correctly with GMX if GMX SW version is under 3.6.1A Service Pack 3 or higher. (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash. GMX (GMZ544) software version can be any version. SXU-A/B (SXZ282) software version can be any version.g.1. SXU-V (SXZ630) software version must be 1. GMX2 is not activated when GMX1 (active) download is finished. Tellabs 8170 cluster node support does not work if SCU-H HW version is under 1.6 Version 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 240 10004_22 © 2008 Tellabs. (CR ID 200008856) HDLC channel 13 is now working properly.1A Service Pack 3 or higher. (CR ID 200005521) Improvements to CLT operation.12) • • • • SCU-H resets under heavy load in Tellabs 8170 cluster node. . if class C IP address is used. GMX (GMZ544) software version can be any version. Dependencies • • • • • • SCU-H (base unit SCU587) hardware version must be 1. MartisDXX Manager support for this unit/interface card/functionality is available in Release 10. SCP-H does not allow a shorter address mask than its IP address class requires (e.13 Enhancements and Fixed Bugs (compared with version 1. Bugs • • Removing lower (active) GMX from inventory does not activate upper GMX.1 or higher to support Tellabs 8170 cluster node. SXU-C (SXZ289) software version can be any version.1 or higher.1 or higher.SCU-H UNIT: SCZ545 Unit Software Dependencies • • • • • • SCU-H (base unit SCU587) hardware version must be 1. MartisDXX Manager support for this unit/interface card/functionality is available in Release 10.

the minimum requirement for the address mask length is 24 bits). if class C IP address is used. SXU-A/B (SXZ282) software version can be any version.SCU-H UNIT: SCZ545 Unit Software Restrictions • • • Extended links do not work correctly with GMX if GMX SW version is under 3.g.6. Bugs • • Removing lower (active) GMX from inventory does not activate upper GMX. SXU-C (SXZ289) software version can be any version. Tellabs 8170 cluster node support does not work if SCU-H HW version is under 1. Restrictions • • • Extended links do not work correctly with GMX if GMX SW version is under 3. 10004_22 © 2008 Tellabs.1A Service Pack 3 or higher. 20.1 or higher to support Cluster Node.6.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. Cluster support does not work if SCU-H HW version is under 1. SXU-V (SXZ630) software version must be 1. if class C IP address is used.11.1. SCP-H does not allow a shorter address mask than its IP address class requires (e.1. Enhancements and Fixed Bugs (compared with version 1. GMX2 is not activated when GMX1 (active) download is finished. (CRF 4004981) Dependencies • • • • • • SCU-H (base unit SCU587) hardware version must be 1.g.7 Version 1. SCP-H does not allow a shorter address mask than its IP address class requires (e. MartisDXX Manager support for this unit/interface card/functionality is available in Release 10. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 241 . the minimum requirement for the address mask length is 24 bits). GMX (GMZ544) software version can be any version.1 or higher.12 This is a non-production version based on version 1.

SCP-H does not allow a shorter address mask than its IP address class requires (e. Cluster support does not work if SCU-H HW version is under 1.SCU-H UNIT: SCZ545 Unit Software Bugs • • • • • Removing lower (active) GMX from inventory does not activate upper GMX. HDLC channel 13 is not working properly. • Dependencies • • • • • • SCU-H (base unit SCU587) hardware version must be 1. SCU-H resets under heavy load in Cluster Node.g. MartisDXX Manager support for this unit/interface card/functionality is available in Release 10. (CR ID 200005521) 20. Old value might have caused inter-subrack communication problems in Cluster Nodes (CRF ID 4004982). the minimum requirement for the address mask length is 24 bits). Changes to GMX switchover logic (equipment protection switch) have been implemented. GMX2 is not activated when GMX1 (active) download is finished. HDLC channel 13 is not working properly. if class C IP address is used. SXU-A/B (SXZ282) software version can be any version.8 Version 1.1 or higher. Restrictions • • • Extended links do not work correctly with GMX if GMX SW version is under 3. Bugs • • • Removing lower (active) GMX from inventory does not activate upper GMX. SXU-C (SXZ289) software version can be any version.1 or higher to support Cluster Node.1. GMX2 is not activated when GMX1 (active) download is finished.11 Enhancements and Fixed Bugs (compared with version 1. SXU-V (SXZ630) software version must be 1.6. GMX (GMZ544) software version can be any version.1A Service Pack 3 or higher. 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. . (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 242 10004_22 © 2008 Tellabs.10) • • A bug that may cause A111 node internal clock disturbance during a GMX hardware switchover has been fixed.

1A Service Pack 3 or higher. (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash.1 or higher to support Cluster Node. MartisDXX Manager support for this unit/interface card/functionality is available in Release 10. SCU-H resets under heavy load in Cluster Node.6. HDLC channel 13 is not working properly. SCU-H resets under heavy load in Cluster Node.SCU-H UNIT: SCZ545 Unit Software • • • SCU-H unit gives power alarm when using protected PAU-10T. (CR ID 200005521) 10004_22 © 2008 Tellabs. Restrictions • • • Extended links do not work correctly with GMX if GMX SW version is under 3. (CR ID 200005521) 20.9 Version 1. the minimum requirement for the address mask length is 24 bits). (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash.10 Dependencies • • • • • • SCU-H (base unit SCU587) hardware version must be 1. SCP-H does not allow a shorter address mask than its IP address class requires (e. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 243 .1.g. Removing lower (active) GMX from inventory does not activate upper GMX. SXU-A/B (SXZ282) software version can be any version. SXU-V (SXZ630) software version must be 1.1 or higher. GMX (GMZ544) software version can be any version. Cluster support does not work if SCU-H HW version is under 1. Bugs • • • • • • A111 node internal clock may be disturbed during a GMX hardware switchover. if class C IP address is used. SXU-C (SXZ289) software version can be any version. GMX2 is not activated when GMX1 (active) download is finished.

10 Version 1. Bugs • • • • • A111 node internal clock may be disturbed during a GMX hardware switchover. MartisDXX Manager support for this unit/interface card/functionality is available in Release 10.6 Dependencies • • • • • • SCU-H (base unit SCU587) hardware version must be 1. SCP-H is not supported. SXU-V (SXZ630) software version must be 1. . (CR ID 200005521) Tellabs® 8100 Managed Access System Unit Software Version Dependencies 244 10004_22 © 2008 Tellabs.1 or higher to support Cluster Node. GMX2 is not activated when GMX1 (active) download is finished. Removing lower (active) GMX from inventory does not activate upper GMX. SXU-C (SXZ289) software version can be any version.1A Service Pack 3 or higher. GMX (GMZ544) software version can be any version.SCU-H UNIT: SCZ545 Unit Software 20. SCU-H resets under heavy load in Cluster Node (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash.1 or higher. Restrictions • • Basic and Cluster Node support is not fully tested with this version. SXU-A/B (SXZ282) software version can be any version.

(CR ID 200005521) 10004_22 © 2008 Tellabs. Removing lower (active) GMX from inventory does not activate upper GMX. SCP-H is not supported. Spontaneous reporting does not work correctly. Restrictions • • Basic and Cluster Node support is not fully tested with this version.1 or higher. Bugs • • • • • • • • A111 node internal clock may be disturbed during a GMX hardware switchover. SXU-A/B (SXZ282) software version can be any version. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 245 . Retrying will help. SXU-V (SXZ630) software version must be 1. In some cases unlocking the port fails. (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash. SCU-H reset may interfere with GMX functionality. SXU-C (SXZ289) software version can be any version. SCU-H resets under heavy load in Cluster Node.SCU-H UNIT: SCZ545 Unit Software 20.11 Version 1.1A Service Pack 3 or higher. GMX (GMZ544) software version can be any version. MartisDXX Manager support for this unit/interface card/functionality is available in Release 10.3 Dependencies • • • • • • SCU-H (base unit SCU587) hardware version must be 1. GMX2 is not activated when GMX1 (active) download is finished.1 or higher to support Cluster Node.

SCU-H resets under heavy load in Cluster Node. In some cases unlocking the port fails. GMX2 is not activated when GMX1 (active) download is finished.12 Version 1. This version cannot be used if SNC protection is used in GMX. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 246 10004_22 © 2008 Tellabs. Restrictions • • • Basic and Cluster Node support is not fully tested with this version. Spontaneous reporting does not work correctly. This version cannot be used if SNC protection is used in GMX. .SCU-H UNIT: SCZ545 Unit Software 20. (CR ID 200005521) 20. SCP-H is not supported.13 Version 1. Restrictions • • • Basic and Cluster Node support is not fully tested with this version. SCU-H reset may interfere with GMX functionality. (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash.2 Dependencies • No dependencies. Bugs • • • • • • • • A111 node internal clock may be disturbed during a GMX hardware switchover. Retrying will help. Removing lower (active) GMX from inventory does not activate upper GMX. SCP-H is not supported.1 Dependencies • No dependencies.

SCU-H resets under heavy load in Cluster Node. SCU-H activates GMX too late in node reset -> GMU fails. Spontaneous reporting does not work correctly. SCU-H resets under heavy load in Cluster Node. SCU-H activates GMX too late in node reset -> GMU fails.SCU-H UNIT: SCZ545 Unit Software Bugs • • • • • • • • • A111 node internal clock may be disturbed during a GMX hardware switchover.0 Dependencies • No dependencies. In some cases unlocking the port fails. In some cases unlocking the port fails. SCP-H is not supported. Restrictions • • • • Basic and Cluster Node support is not fully tested with this version. (CR ID 200005521) 20. (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash.14 Version 1. If the circuit test loop is activated and SCU-H is reset the test port will remain reserved. PFU-H and FAN eeprom checksums are missing. Spontaneous reporting does not work correctly. Removing lower (active) GMX from inventory does not activate upper GMX. This version cannot be used if SNC protection is used in GMX. GMX2 is not activated when GMX1 (active) download is finished. Retrying will help. Bugs • • • • • • • • • • A111 node internal clock may be disturbed during a GMX hardware switchover. Removing lower (active) GMX from inventory does not activate upper GMX. SCU-H reset may interfere with GMX functionality. GMX2 is not activated when GMX1 (active) download is finished. SCU-H reset may interfere with GMX functionality. Retrying will help. (CR ID 200005521) 10004_22 © 2008 Tellabs. (CR ID 200005318) NNM messages in HDLC channels cause SCU-H unit to crash. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 247 .

(CR ID 300038096) There is a possibility for enhanced detection of RAM faults during a functional test. SCU-H (SCZ545) software version must be 1. Restrictions • No restrictions. Bugs • No known bugs. SCP (SCZ281) software version can be any version. SCU (SCZ280) software version can be any version. This fault is a customer requirement.0.5) • The fault Fallback list warning is activated according to the master clock state if Use Quality Levels is selected in master clock status window. . (CR ID 300038625) • • Dependencies • • • • • SXU-A/SXU-B (base unit SXU212/SXU218) hardware versions must be 5. (CR ID 300035785) The fault Reconfiguring X-conn DB does not any more activate in unprotected node when the inventory is created.6 Enhancements and Fixed Bugs (compared with version 10. Tellabs 8100 manager support for the extended XB port capacity is available in Release 13 Service Pack 5 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 248 10004_22 © 2008 Tellabs.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 or higher.

(CR ID 200031045) The background sending of the cross-connected timeslots (Free Time Slot sending) operates correctly for ports over 8448 kbit/s. This will make the unit much more reliable in case of any communication problem.SXU-A and SXU-B Units: SXZ282 Unit Software 21. Data errors would follow if this message was not sent by SXU. (CR ID 200033949) The test timeslot used internally for port IA testing depends on the port capacity. SCU (SCZ280) software version can be any version. (CR ID 300038625) The fault Fallback list warning is not activated.5 Enhancements and Fixed Bugs (compared with version 10. SCU-H (SCZ545) software version must be 1. The processing of the invalid message is prevented. Restrictions • • Does not have the possibility for enhanced detection of RAM faults during functional test. The SXU unit is able to detect a message that has a consistency problem in the internal data structure. (CR ID 300038096) 10004_22 © 2008 Tellabs. This fault is a customer requirement. 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. Immediate switch over after reset will automatically follow preventing the wrong SXU becoming active. An interface unit needs this information to function correctly. SCP (SCZ281) software version can be any version.4) • The testing of the incoming message integrity is improved. (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. Tellabs 8100 manager support for the extended XB port capacity is available in Release 13 Service Pack 5 or higher.2 Version 10. (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 200033778) • • • Dependencies • • • • • SXU-A/SXU-B (base unit SXU212/SXU218) hardware versions must be 5.6 or higher. 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.0. The error was possible because the SXU with incomplete copy of the X-connect database could become active after node reset. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 249 .

SCP (SCZ281) software version can be any version. .3 Version 10. (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 200033778) Does not support the improved check of incoming message integrity. SCU (SCZ280) software version can be any version. Restrictions • • • Does not have the possibility for enhanced detection of RAM faults during functional test.4 Enhancements and Fixed Bugs (compared with version 10. (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. (CR ID 200031045) • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 250 10004_22 © 2008 Tellabs. An interface unit needs this information to function correctly. The activation is a customer requirement. SCU-H (SCZ545) software version must be 1. Data errors will follow if this message is not sent by SXU. (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 300038625) The fault Fallback list warning is not activated.6 or higher. Dependencies • • • • • SXU-A/SXU-B (base unit SXU212/SXU218) hardware versions must be 5.SXU-A and SXU-B Units: SXZ282 Unit Software 21.3) • The support of high capacity X-bus ports is added (up to 192*64 kbit/s). Tellabs 8100 manager support for the extended XB port capacity is available in Release 13 Service Pack 5 or higher.0.

4 Version 10. The same change has already earlier been done to Tellabs 8160 A111/GMX and XCG.g. SCU-H (SCZ545) software version must be 1.0. (CR ID 200033778) Does not support the improved check of incoming message integrity. SCP (SCZ281) software version can be any version. The possibility of an incomplete initialization state of SXU is not anymore possible. Tellabs 8100 manager support for the extended XB port capacity is available in Release 13 Service Pack 5 or higher.6 or higher. Minor flash system bug causing rare flash memory corruptions is fixed. (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. Restrictions • • Does not have the possibility for enhanced detection of RAM faults during a functional test.SXU-A and SXU-B Units: SXZ282 Unit Software 21. Neighbour node monitoring (NNM) polling status problems cannot cause wrong clock selection anymore. if SCU-H is used and if the whole node is reset (e.g. 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. These have been replaced with Faulty clock source of choice n faults. Fallback list warning faults are not anymore generated. the node parameters related to the inventory were neither lost nor changed. AIU). ESU. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 251 . • • • Dependencies • • • • • SXU-A/SXU-B (base unit SXU212/SXU218) hardware versions must be 5. FRU. This error can happen if all the existing server or interface units in the node have long power up times (e. This change concerns only the reporting of QL values. This state was permanent. This incomplete initialization state looked as if the node had lost inventory. 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. In the case of NNM link communication problem the QL value is set to 7 (DNU) to prevent wrong clock source selection.2) • • • X-Connect RAM fault now disappears automatically when the error condition has ended. (CR ID 200033949) Does not support cross connections of high capacity (> 8 Mbit/s) X-bus ports • • 10004_22 © 2008 Tellabs. SCU (SCZ280) software version can be any version. However. Also the EXT clock QL is set to value 7 (DNU) when there is an active problem in the external clock source.3 Enhancements and Fixed Bugs (compared with version 10. if SXU is not protected. Traffic was not recovered at power up and the node was not usable before SXU unit was reset again. The actual selection logic in the unit has been working without any problems and remains unchanged. after power failure).

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.SXU-A and SXU-B Units: SXZ282 Unit Software Bugs • Flash operations slower than in version 10. Time period is about 30 seconds. Restrictions • • Does not have the possibility for enhanced detection of RAM faults during functional test. 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. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. (CR ID 200033949) The XB port capacity up to 192x64kbit/s is not supported.5 Version 10. When SXU is not visible. 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.2 Dependencies • SXU212/SXU218 versions must be 5. • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 252 10004_22 © 2008 Tellabs. . SXU is visible 15 seconds and then unvisible 30 seconds. FRU.g. Fallback list warning faults are shown. (CR ID 200033778) Does not support the improved check of incoming message integrity. Flash system has a bug causing rare flash memory corruptions.2 which may cause TIMEOUT messages in user interface 21. There is a possibility of an incomplete initialization in SXU.0. However the node parameters related to the inventory are neither lost nor changed. if SCU-H is used and if the whole node is reset (e. (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. This permanent error state looks like if the node has lost inventory. after power failure). This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. it is not possible to add SXU to the inventory. • • • Bugs • X-Connect RAM Fault does not disappear when the error condition causing it is over.g. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. This error can happen if all the existing server or interface units in the node have long power up times (e. This is a clear but minor problem. AIU). The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. if SXU is not protected. ESU.

(CR ID 200033778) Does not support the improved check of incoming message integrity. the alarm Passive Flash Version Fault is always activated which is wrong. This error can happen if all the existing server or interface units in the node have long power up times (e. if SXU is not protected. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. after power failure). Above 2400 bauds there is sufficient time to complete the operations and no problem exists. Restrictions • • Does not have the possibility for enhanced detection of RAM faults during a functional test. Frame errors may happen during switch over.0. Existing extended lists are not cleared when SXU is put in an unprotected node.6 Version 10. 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. Fallback list warning faults are shown. Extended lists (clear channel configuration) are not cleared when SXU is removed from the inventory.SXU-A and SXU-B Units: SXZ282 Unit Software 21. AIU). Tellabs® 8100 Managed Access System Unit Software Version Dependencies 253 . when the EPS Clear Channel is used. • • • Bugs • X-Connect RAM Fault does not disappear when the error condition causing it is over.g. (CR ID 200033949) The XB port capacity up to 192x64kbit/s is not supported. 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. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. Cross-connection protection will correct this problem in a protected node. • • • • • • • • • 10004_22 © 2008 Tellabs.g. an internal software timer expires too fast and disconnects the Clear Channel prematurely. There is an about 4-second delay when changing the clock from internal to external clock. When version r10. 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. which may lead to invalid clear channel parameters. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. When the fault remains active after the problem the switch over logic does not operate. if SCU-H is used and if the whole node is reset (e. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. FRU. There is a possibility of an incomplete initialization in SXU. ESU.1 Dependencies • SXU212/SXU218 versions must be 5.1 and an older version is used in the same protected node. (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. At slow modem baud rates of 2400 or less.

• 21. if SXU is not protected. (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. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 254 10004_22 © 2008 Tellabs. However this is not a critical problem because units are not in operative state.7 Version 10. To get rid of the unnecessary but rare fault the unit has to be reset.0. AIU). It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown.g. (CR ID 200033778) Does not support the improved check of incoming message integrity. FRU. The effect of this is a bit slower clock stabilization. (CR ID 200033949) Does not support EPS clear channel dynamic cross-connections. Flash system has a bug causing rare flash memory corruptions. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied.0 Dependencies • SXU212/SXU218 versions must be 5. ESU. When the fault remains active after the problem the switch over logic does not operate. Fallback list warning faults are shown. after power failure). During unit initialization after reset the Clock Switchover Fault is activated for a short time period.g. • • • • • Bugs • X-Connect RAM Fault does not disappear when the error condition causing it is over. This error can happen if all the existing server or interface units in the node have long power up times (e. . This permanent error state looks like if the node has lost inventory. This may lead to unnecessary switchover. SXU does not select the next best choice at once but there may be some intermediate states. if SCU-H is used and if the whole node is reset (e.SXU-A and SXU-B Units: SXZ282 Unit Software • • It is possible to change port parameters when the port is in swapped state. Swapped ports are expected to be equal. Restrictions • • Does not have the possibility for enhanced detection of RAM faults during a functional test. When the node master clock becomes faulty. 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. 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. There is a possibility of an incomplete initialization in SXU.

This value should be DNU (Do Not Use). 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. This version should not be used once the official r6. This version should not be used once the official r6. During unit initialization after reset the Clock Switchover fault is activated for a short time period.8 Version 6.10 This is an unofficial version based on SXZ282 release r6. There is an about 4-second delay when changing the clock from internal to external clock.9 development version with CIF port type support.9 is available. 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). 10004_22 © 2008 Tellabs. 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. • • • • • • • • 21. This alarm does not affect node operation and it is cleared after next FBL update. It does not affect the other units in that node. SXU uses SDH SSM code SEC for quality level 6 (internal clock). there will be a permanent PLL alarm in the passive SXU. 21. This may lead to unnecessary switchover. it may lead to continuous switching of the active SXU. 2) the entry currently used is the only valid one.11 This is an unofficial version based on SXZ282 release r6. 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. • Bit errors may occur during node synchronization source changes when the following conditions are true: 1) There are at least 3 entries in FBL.8 with bug fix for clustered point to multipoint (PMP) Server port init problem. Swapped ports are expected to be equal.9 is available. The effect of this is a bit slower clock stabilization. However this is not a critical problem because units are not in operative state. When the node master clock becomes faulty. SXU does not select the next best choice at once but there may be some intermediate states. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 255 .SXU-A and SXU-B Units: SXZ282 Unit Software However the node parameters related to the inventory are neither lost nor changed. The problem will only occur when adding a new GMU to a node and it will disappear after any change in the node synchronization.9 Version 6. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. It is possible to change port parameters when the port is in swapped state.

9 Dependencies • SXU212/SXU218 versions must be lower than 5. The XB port capacity up to 192x64kbit/s is not supported. FRU. 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. There is a possibility of an incomplete initialization in SXU. No support for base unit version 5.0. after power failure). Traffic is not recovered at power up and the node is not usable before SXU unit is reset again.g. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. 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. AIU). This error can happen if all the existing server or interface units in the node have long power up times (e. • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 256 10004_22 © 2008 Tellabs. It does not affect the other units in that node. Flash system has a bug causing rare flash memory corruptions. (CR ID 200033949) Does not support EPS clear channel dynamic cross-connections. Restrictions • • Does not have the possibility for enhanced detection of RAM faults during functional test.10 Version 6.g. . 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 problem will only occur when adding a new GMU to a node and it will disappear after any change in the node synchronization. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. (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. Fallback list warning faults are shown. if SCU-H is used and if the whole node is reset (e. • • • • • • 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. (CR ID 200033778) Does not support the improved check of incoming message integrity. ESU. However the node parameters related to the inventory are neither lost nor changed.0.SXU-A and SXU-B Units: SXZ282 Unit Software 21. This permanent error state looks like if the node has lost inventory. if SXU is not protected. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Adding a new GMU to a node may sometimes lead to unexpected faults on the GMU unit and problems in its operation. To get rid of the unnecessary but rare fault the unit has to be reset.

SXU-A and SXU-B Units: SXZ282 Unit Software • • SXU uses SDH SSM code SEC for quality level 6 (internal clock).0. • • • • • 21. it may lead to continuous switching of the active SXU. The effect of this is a bit slower clock stabilization. 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 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. This value should be DNU (Do Not Use). Does not support EPS clear channel dynamic cross connections. (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. 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.8 Dependencies • SXU212/SXU218 versions must be lower than 5. No support for base unit version 5. Frame errors may happen during switch over. SXU does not select the next best choice at once but there may be some intermediate states. During unit initialization after reset the Clock Switchover Fault is activated for a short time period.0. 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). Restrictions • • Does not have the possibility for enhanced detection of RAM faults during a functional test. However this is not a critical problem because units are not in operative state. It is possible to change port parameters when the port is in swapped state. (CR ID 200033778) Does not support the improved check of incoming message integrity. Clock changes are not indicated in fault history. Swapped ports are expected to be equal. This may lead to unnecessary switchover. Does not indicate synchronization source changes in fault history. • • • • • • • • • 10004_22 © 2008 Tellabs. (CR ID 200033949) No support for improved and nearly hitless change over. When the node master clock becomes faulty. There is an about 4-second delay when changing the clock from internal to external clock.11 Version 6. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 257 .

This error can happen if all the existing server or interface units in the node have long power up times (e. If there is a clustered point to multipoint (PMP) Server that has locked ports in the node. the real QL value used in the clock selection is not sent to the neighbour node. AIU). FRU. 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 permanent error state looks like if the node has lost inventory. If an active SXU loses external clock protection. 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. When using a quality source other than polled. However the node parameters related to the inventory are neither lost nor changed. ports for unit 14 are allocated incorrectly. • • • • • • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 258 10004_22 © 2008 Tellabs. ESU. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. These ports can be cross-connected but the connections do not operate. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. Flash system has a bug causing rare flash memory corruptions.g. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. The port object allows changing the even/uneven bus allocation parameter for an existing port. Removing a passive SXU in a protected node causes errors in traffic.SXU-A and SXU-B Units: SXZ282 Unit Software • • The XB port capacity up to 192x64kbit/s is not supported. after power failure). This value should be DNU (Do Not Use). The problem will only occur when adding a new GMU to a node and it will disappear after any change in the node synchronization. . With SXU-A in an unprotected node. 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. There is a possibility of an incomplete initialization in SXU. if SXU is not protected. SXU uses SDH SSM code SEC for quality level 6 (internal clock). Adding a new GMU to a node may sometimes lead to unexpected faults on the GMU unit and problems in its operation. 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. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. When the fault remains active after the problem the switch over logic does not operate. This happens with all the node types allowed with SXU-A. it may lead to continuous switching of the active SXU. Fallback list warning faults are shown. Bugs • X-Connect RAM Fault does not disappear when the error condition causing it is over.g. This happens even if a passive SXU had a valid external clock. To get rid of the unnecessary but rare fault the unit has to be reset. 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 does not affect the other units in that node. if SCU-H is used and if the whole node is reset (e.

7 This version is forbidden.6 Dependencies • SXU212/SXU218 versions must be lower than 5. Restrictions • • Does not have the possibility for enhanced detection of RAM faults during a functional test. Fallback list warning faults are shown. (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. No support for base unit version 5. 21. 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.0. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 259 . When the node master clock becomes faulty. SXU does not select the next best choice at once but there may be some intermediate states.12 Version 6. The XB port capacity up to 192x64kbit/s is not supported. (CR ID 200033949) No support for improved and nearly hitless change over. It is possible to change port parameters when the port is in swapped state. 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. (CR ID 200033778) Does not support the improved check of incoming message integrity. Does not indicate the synchronization source changes in fault history. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied.0. 21. Swapped ports are expected to be equal. Does not support EPS clear channel dynamic cross connections. • • • • • • • • • • • 10004_22 © 2008 Tellabs. Clock changes are not indicated in fault history.13 Version 6.SXU-A and SXU-B Units: SXZ282 Unit Software • • • There is an about 4-second delay when changing the clock from internal to external clock. The effect of this is a bit slower clock stabilization. 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).

• • • • • • • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 260 10004_22 © 2008 Tellabs. 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. This happens even if a passive SXU had a valid external clock.g. To get rid of the unnecessary but rare fault the unit has to be reset. The average delay is 1 min and the maximum value is 2 min. after power failure).g. if SCU-H is used and if the whole node is reset (e. If active SXU loses the external clock protection. When using a quality source other than polled. the real QL value used in the clock selection is not sent to the neighbour node. Flash system has a bug causing rare flash memory corruptions.SXU-A and SXU-B Units: SXZ282 Unit Software Bugs • X-Connect RAM Fault does not disappear when the error condition causing it is over. Removing a passive SXU from a protected node causes errors in traffic. 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. 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. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window. . With SXU-A in an unprotected node ports for unit 14 are allocated incorrectly. Circuit functioning may have some delay when using xgroup IDs if more than one ID state is changed within a few seconds. There is a possibility of an incomplete initialization in SXU. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. FRU. When the fault remains active after the problem the switch over logic does not operate. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. ESU. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. If both SXUs in a protected Basic Node experience an SW reset almost simultaneously. These ports can be cross-connected but the connections do not operate. Under these circumstances. After setting CAS on it is not possible to set it off or delete the connection. The port object allows changing the even/uneven bus allocation parameter for an existing port. This error can happen if all the existing server or interface units in the node have long power up times (e. switching is not done but either the next clock from the fallback list is chosen or the node starts to use the internal clock. the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list. 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. 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. it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. if SXU is not protected. 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. This happens with all the node types allowed with SXU-A. AIU). c) EXT is chosen to master clock of the node and d) EXT is in failed state.

There is an about 4-second delay when changing the clock from internal to external clock. 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. When the node master clock becomes faulty. Swapped ports are expected to be equal.0. SXU uses SDH SSM code SEC for quality level 6 (internal clock). 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. Does not indicate synchronization source changes in fault history.5 Dependencies • SXU212/SXU218 versions must be lower than 5. 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. it may lead to continuous switching of the active SXU. 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. Clock changes are not indicated in fault history. It does not affect the other units in that node. 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). 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 is possible to change port parameters when the port is in swapped state. • • • • • • • 10004_22 © 2008 Tellabs. Adding a new GMU to a node may sometimes lead to unexpected faults on the GMU unit and problems in its operation. No support for improved and nearly hitless change over. 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).14 Version 6. (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 200033949) No support for GMU. Restrictions • • Does not have the possibility for enhanced detection of RAM faults during a functional test. (CR ID 200033778) Does not support the improved check of incoming message integrity. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 261 . • • • • • • 21.SXU-A and SXU-B Units: SXZ282 Unit Software • If there is a clustered point to multipoint (PMP) Server that has locked ports in the node.

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

it may lead to continuous switching of the active SXU. The effect of this is a bit slower clock stabilization. Under these circumstances. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 263 .SXU-A and SXU-B Units: SXZ282 Unit Software structures are corrupted (as just explained) b) EXT clock is on the fallback list. There is an about 4-second delay when changing the clock from internal to external clock. 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). Clock changes are not indicated in fault history. (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. No T1 support. When the node master clock becomes faulty. Swapped ports are expected to be equal. 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). Does not indicate synchronization source changes in fault history • • • • • • • • • 10004_22 © 2008 Tellabs. Slow cross-connect operations.15 Version 6. It is possible to change port parameters when the port is in swapped state.3 Dependencies • SXU212/SXU218 versions must be lower than 5. • • • 21. the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list.0. No support for improved and nearly hitless change over. The port object allows changing the even/uneven bus allocation parameter for an existing port. Restrictions • • Does not have the possibility for enhanced detection of RAM faults during a functional test. SXU does not select the next best choice at once but there may be some intermediate states. No support for GMU. c) EXT is chosen as the master clock of the node and d) EXT is in failed state. (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. 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.

Bugs • X-Connect RAM Fault does not disappear when the error condition causing it is over.g. 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. after power failure). 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.0. FRU. There is a possibility of an incomplete initialization in SXU. if SCU-H is used and if the whole node is reset (e. A unit does not disappear from the list of available clock sources when the unit is removed from inventory. Loss of the external clock causes a switch over. The list of available ports for the master clock is not updated when the unit is removed from the inventory. After setting CAS on it is not possible to set it off or delete the connection. AIU). 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. An unnecessary Fallback list warning fault may rise if there are still usable clock sources. When the fault remains active after the problem the switch over logic does not operate. Fallback list warning faults are shown. This error can happen if all the existing server or interface units in the node have long power up times (e. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Does not support EPS clear channel dynamic cross connections.g. .SXU-A and SXU-B Units: SXZ282 Unit Software • • • • • • 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. If a unit belongs to the node inventory but it is physically missing while SXU is resetting. it is possible that the next clock is not correctly picked from the fallback list. ESU. c) EXT is • • • • • • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 264 10004_22 © 2008 Tellabs. PLL alarm does not affect the clock selection. 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. If the external clock is the current clock source and the external clock input is broken. The XB port capacity up to 192x64kbit/s is not supported. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. 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. 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. If both SXUs in a protected Basic Node experience an SW reset almost simultaneously. No support for base unit version 5. if SXU is not protected. This permanent error state looks like if the node has lost inventory. it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. SXU may assume that the missing unit is still outputting usable clock signal.

16 Version 6. • • • Removing a passive SXU in a protected node causes errors in traffic. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window. 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). There is an about 4-second delay when changing the clock from internal to external clock. (CR ID 200033949) Setting the signaling bit idle value is not supported. Slow cross-connect operations. The port object allows changing the even/uneven bus allocation parameter for existing port. It is possible to change port parameters when the port is in swapped state. The effect of this is a bit slower clock stabilization.0. the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list. SXU does not select the next best choice at once but there may be some intermediate states.0. No T1 support. No support for base unit version 5. it may lead to continuous switching of the active SXU. (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. • • • 21. (CR ID 200033778) Does not support the improved check of incoming message integrity. 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). Tellabs® 8100 Managed Access System Unit Software Version Dependencies 265 . When the node master clock becomes faulty. No support for improved and nearly hitless change over. Restrictions • • Does not have the possibility for enhanced detection of RAM faults during a functional test. • • • • • • • • • • • 10004_22 © 2008 Tellabs. No support for GMU. 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.SXU-A and SXU-B Units: SXZ282 Unit Software chosen as the master clock of the node and d) EXT is in failed state. Under these circumstances. Swapped ports are expected to be equal. Clock changes are not indicated in fault history.2 Dependencies • SXU212/SXU218 versions must be lower than 5.

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

(CR ID 200033778) Does not support the improved check of incoming message integrity. 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.SXU-A and SXU-B Units: SXZ282 Unit Software next clock from the fallback list. (CR ID 200033949) Setting the signaling bit idle value is not supported. Restrictions • • Does not have the possibility for enhanced detection of RAM faults during a functional test. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 267 . • • • 21. No support for improved and nearly hitless change over. The port object allows changing the even/uneven bus allocation parameter for existing port. • • • Removing a passive SXU in a protected node causes errors in traffic. Swapped ports are expected to be equal. • • • • • • • • • • • 10004_22 © 2008 Tellabs.0.17 Version 6. Slow cross-connect operations. There is an about 4-second delay when changing the clock from internal to external clock. it may lead to continuous switching of the active SXU. Clock changes are not indicated in fault history. (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. The effect of this is a bit slower clock stabilization. It is possible to change port parameters when the port is in swapped state. 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). When node master clock becomes faulty SXU does not select the next best choice at once but there may be some intermediate states.1 Dependencies • SXU212/SXU218 versions must be lower than 5. Does not support using of contradirectional synchronization clock sources in a protected ring network topology. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window. No support for GMU. No T1 support. 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).

Fallback list warning faults are shown. SXU may assume that the missing unit is still outputting usable clock signal. AIU). However the node parameters related to the inventory are neither lost nor changed. it is possible that the next clock is not correctly picked from the fallback list. There is a possibility of an incomplete initialization in SXU. This permanent error state looks like if the node has lost inventory. Loss of external clock causes a switch over. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. after power failure). Flash system has a bug causing rare flash memory corruptions. b) EXT clock is on the fallback list. FRU. The bug appears if all of the following happens simultaneously: a) data structures are corrupted (as just explained). If an external clock is the current clock source and the external clock input is broken. 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 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.g.0.SXU-A and SXU-B Units: SXZ282 Unit Software • • • • • No support for base unit version 5. This error can happen if all the existing server or interface units in the node have long power up times (e. the active SXU fails to realize the failure of EXT and does not choose the • • • • • • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 268 10004_22 © 2008 Tellabs. ESU. Bugs • X-Connect RAM Fault does not disappear when the error condition causing it is over. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. PLL alarm does not affect the clock selection. 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. . To get rid of the unnecessary but rare fault the unit has to be reset. If both SXUs in a protected Basic Node experience an SW reset almost simultaneously. The list of available ports for the master clock is not updated when the unit is removed from inventory. The XB port capacity up to 192x64kbit/s is not supported. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. c) EXT is chosen as the master clock of the node and d) EXT is in failed state. If a unit belongs to the node inventory but it is physically missing while SXU is resetting. it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. NMS disaster recovery cannot be used. if SXU is not protected.g. When the fault remains active after the problem the switch over logic does not operate. Does not support EPS clear channel dynamic cross connections. if SCU-H is used and if the whole node is reset (e. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. A unit does not disappear from the list of available clock sources when the unit is removed from inventory. After setting CAS on it is not possible to set it off or delete the connection. Under these circumstances.

No support for improved and nearly hitless change over. Does not support using of contradirectional synchronization clock sources in a protected ring network topology. Swapped ports are expected to be equal.0 Dependencies • SXU212/SXU218 versions must be lower than 5. • • • • • • • • • • • 10004_22 © 2008 Tellabs. The port object allows changing the even/uneven bus allocation parameter for existing port. • • • Removing a passive SXU in a protected node causes errors in traffic. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window. When the node master clock becomes faulty SXU does not select the next best choice at once but there may be some intermediate states. Clock changes are not indicated in fault history. Slow cross-connect operations. • • • 21. (CR ID 200033949) Setting the signalling bit idle value is not supported. No T1 support. it may lead to continuous switching of the active SXU.SXU-A and SXU-B Units: SXZ282 Unit Software next clock from the fallback list. Restrictions • • Does not have the possibility for enhanced detection of RAM faults during a functional test. 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. It is possible to change port parameters when the port is in swapped state. No support for GMU.0. 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). (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. There is an about 4-second delay when changing the clock from internal to external clock.18 Version 6. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 269 . The effect of this is a bit slower clock stabilization. (CR ID 200033778) Does not support the improved check of incoming message integrity. 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).

The real time clock can be used only in adaptive mode. b) the EXT clock is on the fallback list. after power failure). Does not support EPS clear channel dynamic cross connections. The XB port capacity up to 192x64kbit/s is not supported. if SXU is not protected. Loss of external clock causes a switch over. Flash system has a bug causing rare flash memory corruptions. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. To get rid of the unnecessary but rare fault the unit has to be reset. 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. 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. ESU. If an external clock is the current clock source and the external clock input is broken. However the node parameters related to the inventory are neither lost nor changed.g. 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. After setting CAS on it is not possible to set it off or delete the connection. SXU may assume that the missing unit is still outputting usable clock signal. If a unit belongs to the node inventory but it is physically missing while SXU is resetting. AIU).SXU-A and SXU-B Units: SXZ282 Unit Software • • • • • No support for base unit version 5. The bug appears if all of the following happens simultaneously: a) data structures are corrupted (as just explained). A unit does not disappear from the list of available clock sources when the unit is removed from the inventory. Fallback list warning faults are shown.g. When the fault remains active after the problem the switch over logic does not operate. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. . The whole bit connection capacity cannot be taken in use in SXU-A. it is possible that the next clock is not correctly picked from the fallback list.0. FRU. PLL alarm does not affect the clock selection. This permanent error state looks like if the node has lost inventory. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. Bugs • X-Connect RAM Fault does not disappear when the error condition causing it is over. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. c) EXT • • • • • • • • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 270 10004_22 © 2008 Tellabs. The list of available ports for the master clock is not updated when the unit is removed from the inventory. 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. If both SXUs in a protected Basic Node experience an SW reset almost simultaneously. NMS disaster recovery cannot be used. if SCU-H is used and if the whole node is reset (e.

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). Restrictions • • Does not have the possibility for enhanced detection of RAM faults during a functional test.0. Under these circumstances. When the node master clock becomes faulty SXU does not select the next best choice at once but there may be some intermediate states. Slow cross-connect operations. Swapped ports are expected to be equal. No T1 support. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window. (CR ID 200033778) Does not support the improved check of incoming message integrity. Does not indicate synchronization source changes in fault history • • • • • • • • • • 10004_22 © 2008 Tellabs. it may lead to continuous switching of the active SXU. The effect of this is a bit slower clock stabilization.19 Version 5.SXU-A and SXU-B Units: SXZ282 Unit Software is chosen as the master clock of the node and d) EXT is in failed state. (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. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 271 . • • • Removing the passive SXU in a protected node causes errors in traffic. 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). the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list. Does not support the using of contradirectional synchronisation clock sources in a protected ring network topology. No support for GMU. The port object allows changing the even/uneven bus allocation parameter for the existing port. Clock changes are not indicated in fault history. • • • 21. (CR ID 200033949) Setting the signalling bit idle value is not supported. No support for improved and nearly hitless change over.9 Dependencies • SXU212/SXU218 versions must be lower than 4. 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.

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. Bugs • X-Connect RAM Fault does not disappear when the error condition causing it is over. No support for base unit version 5. There is a possibility of an incomplete initialization in SXU. AIU). The XB port capacity up to 192x64kbit/s is not supported. Flash system has a bug causing rare flash memory corruptions. However the node parameters related to the inventory are neither lost nor changed.g. The list of available ports for the master clock is not updated when the unit is removed from the inventory. if SCU-H is used and if the whole node is reset (e. • • • • • • • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 272 10004_22 © 2008 Tellabs. After setting CAS on it is not possible to set it off or delete the connection. if SXU is not protected.0. The real time clock can be used only in adaptive mode. PLL alarm does not affect the clock selection. If an external clock is the current clock source and the external clock input is broken.g. Does not support EPS clear channel dynamic cross connections. This permanent error state looks like if the node has lost inventory. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. . SXU may assume that the missing unit is still outputting usable clock signal. ESU. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. This error can happen if all the existing server or interface units in the node have long power up times (e. Fallback list warning faults are shown. it is possible that the next clock is not correctly picked from the fallback list.SXU-A and SXU-B Units: SXZ282 Unit Software • • • • • • 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. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. 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. NMS disaster recovery cannot be used. The whole bit connection capacity cannot be taken in use in SXU-A. If a unit belongs to node inventory but it is physically missing while the SXU is resetting. 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. after power failure). A unit does not disappear from the list of available clock sources when the unit is removed from the inventory. Loss of external clock causes a switch 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. FRU. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value.

Clock changes are not indicated in fault history.20 Version 5. Removing a passive SXU in a protected node causes errors in traffic. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window. it may lead to continuous switching of active SXU. • • • • • • • • 10004_22 © 2008 Tellabs. (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. No support for improved and nearly hitless change over.0. Under these circumstances.SXU-A and SXU-B Units: SXZ282 Unit Software • If both SXUs in a protected Basic Node experience an SW reset almost simultaneously. No T1 support. It is possible to change port parameters when the port is in swapped state. No support for GMU. (CR ID 200033949) Setting the signalling bit idle value is not supported. 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). There is an about 4-second delay when changing the clock from internal to external clock. • • • • • • 21. it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. Does not support the using of contradirectional synchronization clock sources in a protected ring network topology.8 Dependencies • SXU212/SXU218 versions must be lower than 4. The port object allows changing the even/uneven bus allocation parameter for the existing port. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 273 . the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list. Slow cross-connect operations. Restrictions • • Does not have the possibility for enhanced detection of RAM faults during a functional test. b) the EXT clock is on the fallback list. When the node master clock becomes faulty. Swapped ports are expected to be equal. The bug appears if all of the following happens simultaneously: a) data structures are corrupted (as just explained). c) EXT is chosen as the master clock of the node and d) EXT is in failed state. The effect of this is a bit slower clock stabilization. SXU does not select the next best choice at once but there may be some intermediate states.

g. AIU). ESU. A unit does not disappear from the list of available clock sources when the unit is removed from the inventory. The whole bit connection capacity cannot be taken in use in SXU-A. To get rid of the unnecessary but rare fault the unit has to be reset. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. This permanent error state looks like if the node has lost inventory. The list of available ports for the master clock is not updated when the unit is removed from the inventory. it is possible that the next clock is not correctly picked from the fallback list. . after power failure). NMS disaster recovery cannot be used. If a unit belongs to the node inventory but it is physically missing while the SXU is resetting. 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. Does not support EPS clear channel dynamic cross connections. This error can happen if all the existing server or interface units in the node have long power up times (e. Loss of external clock causes a switch over. PLL alarm does not affect the clock selection. 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. There is a possibility of an incomplete initialization in SXU. Flash system has a bug causing rare flash memory corruptions. if SCU-H is used and if the whole node is reset (e.SXU-A and SXU-B Units: SXZ282 Unit Software • • • • • • • • 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. However the node parameters related to the inventory are neither lost nor changed. No support for base unit version 5. Real time clock can be used only in adaptive mode. When the fault remains active after the problem the switch over logic does not operate. Fallback list warning faults are shown. if SXU is not protected. SXU may assume that the missing unit is still outputting usable clock signal. If an external clock is the current clock source and the external clock input is broken. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value.0. Bugs • X-Connect RAM Fault does not disappear when the error condition causing it is over.g. • • • • • • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 274 10004_22 © 2008 Tellabs. FRU. The XB port capacity up to 192x64kbit/s is not supported. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown.

Under these circumstances. (CR ID 200033778) Does not support the improved check of incoming message integrity. (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. Restrictions • • Does not have the possibility for enhanced detection of RAM faults during a functional test. It is possible to change port parameters when the port is in swapped state. 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). b) the EXT clock is on the fallback list.7 Dependencies • SXU212/SXU218 versions must be lower than 4. The port object allows changing the even/uneven bus allocation parameter for the existing port. the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list. The effect of this is a bit slower clock stabilization.SXU-A and SXU-B Units: SXZ282 Unit Software • 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. it may lead to continuous switching of the active SXU.21 Version 5. There is an about 4-second delay when changing the clock from internal to external clock. No T1 support. Slow cross-connect operations.0. • • • • • • • 21. When the node master clock becomes faulty. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window. it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. c) EXT is chosen as the master clock of the node and d) EXT is in failed state. (CR ID 200033949) Setting the signalling bit idle value is not supported. • • • • • • 10004_22 © 2008 Tellabs. Removing a passive SXU in a protected node causes errors in traffic. SXU does not select the next best choice at once but there may be some intermediate states. The bug appears if all of the following happens simultaneously: a) data structures are corrupted (as just explained). If both SXUs in a protected Basic Node experience an SW reset almost simultaneously. Does not support using of contradirectional synchronisation clock sources in a protected ring network topology. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 275 . Swapped ports are expected to be equal. No support for GMU. After setting CAS on it is not possible to set it off or delete the connection.

Bugs • X-Connect RAM Fault does not disappear when the error condition causing it is over. after power failure). Flash system has a bug causing rare flash memory corruptions. 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). Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. Clock changes are not indicated in fault history. The XB port capacity up to 192x64kbit/s is not supported. PLL alarm does not affect the clock selection. This permanent error state looks like if the node has lost inventory. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. The real time clock can be used only in adaptive mode. if SCU-H is used and if the whole node is reset (e. if SXU is not protected. NMS disaster recovery cannot be used. Fallback list warning faults are shown. Loss of external clock causes a switch over. . The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value.SXU-A and SXU-B Units: SXZ282 Unit Software • • • • • • • • • • No support for improved and nearly hitless change over. FRU. When the fault remains active after the problem the switch over logic does not operate. There is a possibility of an incomplete initialization in SXU. The whole bit connection capacity cannot be taken in use in SXU-A. • • • • • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 276 10004_22 © 2008 Tellabs.g. it is possible that the next clock is not correctly picked from the fallback list.g. If an external clock is the current clock source and the external clock input is broken. AIU). It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. This error can happen if all the existing server or interface units in the node have long power up times (e. 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. ESU. To get rid of the unnecessary but rare fault the unit has to be reset. A unit does not disappear from the list of available clock sources when the unit is removed from the inventory.0. However the node parameters related to the inventory are neither lost nor changed. No support for base unit version 5. The list of available ports for the master clock is not updated when the unit is removed from the inventory. 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. 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.

SXU-A and SXU-B Units: SXZ282 Unit Software • • If a unit belongs to the node inventory but it is physically missing while the SXU is resetting. SXU does not select the next best choice at once but there may be some intermediate states. Swapped ports are expected to be equal. Removing a passive SXU in a protected node causes errors in traffic. • • • • • • • 21. 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). Tellabs® 8100 Managed Access System Unit Software Version Dependencies 277 . There is an about 4-second delay when changing the clock from internal to external clock. b) the EXT clock is on the fallback list. After setting CAS on it is not possible to set it off or delete the connection. Restrictions • • Does not have the possibility for enhanced detection of RAM faults during a functional test.6 Dependencies • SXU212/SXU218 versions must be lower than 4. SXU may assume that the missing unit is still outputting usable clock signal. If both SXUs in a protected Basic Node experience an SW reset almost simultaneously. (CR ID 200033778) Does not support the improved check of incoming message integrity. Setting the signalling bit idle value is not supported. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window. c) EXT is chosen as the master clock of the node and d) EXT is in failed state. it may lead to continuous switching of the active SXU. the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list. The bug appears if all of the following happens simultaneously: a) data structures are corrupted (as just explained). it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. 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. • • • • 10004_22 © 2008 Tellabs. (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. It is possible to change port parameters when the port is in swapped state.0.22 Version 5. The port object allows changing the even/uneven bus allocation parameter for the existing port. Under these circumstances. 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 effect of this is a bit slower clock stabilization. (CR ID 200033949) Does not support EPS clear channel dynamic cross-connections. When the node master clock becomes faulty.

This permanent error state looks like if the node has lost inventory. CAE unit is not supported. 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. Flash system has a bug causing rare flash memory corruptions. When the fault remains active after the problem the switch over logic does not operate. The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied.SXU-A and SXU-B Units: SXZ282 Unit Software • • • • • • • • • • • • • Slow cross-connect operations. Loss of external clock causes switch over. The real time clock can be used only in adaptive mode. The XB port capacity up to 192x64kbit/s is not supported. No T1 support. No support for GMU. AIU). There is a possibility of an incomplete initialization in SXU. ESU. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again. This error can happen if all the existing server or interface units in the node have long power up times (e. FRU. . • • • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 278 10004_22 © 2008 Tellabs. Bugs • X-Connect RAM Fault does not disappear when the error condition causing it is over.g. To get rid of the unnecessary but rare fault the unit has to be reset. PLL alarm does not affect the clock selection. However the node parameters related to the inventory are neither lost nor changed. The list of available ports for the master clock is not updated when the unit is removed from the inventory.0. No support for base unit version 5. NMS disaster recovery cannot be used. 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). No support for improved and nearly hitless change over. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. Clock changes are not indicated in fault history. 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. Fallback list warning faults are shown.g. if SCU-H is used and if the whole node is reset (e. The whole bit connection capacity cannot be taken in use in SXU-A. after power failure). if SXU is not protected. Does not support using of contradirectional synchronization clock sources in a protected ring network topology.

It is possible to change port parameters when the port is in swapped state. b) the EXT clock is on the fallback list. The problem can be solved by updating (changing) the fallback list manually through the NMS Master Clock window. 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). (CR ID 200033949) Setting the signalling bit idle value is not supported.5 Dependencies • SXU212/SXU218 versions must be lower than 4.0. If an external clock is the current clock source and the external clock input is broken. Removing a passive SXU in a protected node causes errors in traffic. it is possible that the next clock is not correctly picked from the fallback list. When the node master clock becomes faulty SXU does not select the next best choice at once but there may be some intermediate states. (CR ID 200033778) Does not support the improved check of incoming message integrity. There is an about 4-second delay when changing the clock from internal to external clock. 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. If both SXUs in a protected Basic Node experience an SW reset almost simultaneously. • • 10004_22 © 2008 Tellabs. Swapped ports are expected to be equal. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 279 . • • • • • • • 21. If a unit belongs to the node inventory but it is physically missing while the SXU is resetting. the active SXU fails to realize the failure of EXT and does not choose the next clock from the fallback list. Under these circumstances. (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. The effect of this is a bit slower clock stabilization. The bug appears if all of the following happens simultaneously: a) data structures are corrupted (as just explained). it is possible that the internal master clock RAM data structures of the active SXU end up in a corrupted state. After setting CAS on it is not possible to set it off or delete the connection.23 Version 5. c) EXT is chosen as the master clock of the node and d) EXT is in failed state.SXU-A and SXU-B Units: SXZ282 Unit Software • • • • A unit does not disappear from the list of available clock sources when the unit is removed from the inventory. it may lead to continuous switching of the active SXU. Restrictions • • Does not have the possibility for enhanced detection of RAM faults during a functional test. SXU may assume that the missing unit is still outputting usable clock signal.

AIU). The Neighbour node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. There is a possibility of an incomplete initialization in SXU. Bugs • X-Connect RAM Fault does not disappear when the error condition causing it is over. after power failure). FRU. No T1 support. The real time clock cannot be used. No support for base unit version 5. No support for improved and nearly hitless change over. No support for GMU. 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. 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. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Flash system has a bug causing rare flash memory corruptions. This permanent error state looks like if the node has lost inventory. 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. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown.SXU-A and SXU-B Units: SXZ282 Unit Software • • • • • • • • • • • • • • • Slow cross-connect operations. . if SXU is not protected. Time controlled circuits do not work. NMS disaster recovery cannot be used. The whole bit connection capacity cannot be taken in use in SXU-A. To get rid of the unnecessary but rare fault the unit has to be reset.0. CAE unit is not supported. When the fault remains active after the problem the switch over logic does not operate. Does not support the using of contradirectional synchronization clock sources in a protected ring network topology. However the node parameters related to the inventory are neither lost nor changed. ESU. Fallback list warning faults are shown. This error can happen if all the existing server or interface units in the node have long power up times (e. • • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 280 10004_22 © 2008 Tellabs. if SCU-H is used and if the whole node is reset (e. The XB port capacity up to 192x64kbit/s is not supported. Traffic is not recovered at power up and the node is not usable before SXU unit is reset again.g. Clock changes are not indicated in fault history. Does not support EPS clear channel dynamic cross connections. The real time clock can be used only in adaptive mode.g.

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

• • Restrictions • No restrictions.1 Version 10.0B-12 or later.0 is fixed. MartisDXX NMS release must be 9.11 or higher to support cluster node. This happens for example if SCU is changed to SCU-H unit in a slave. In earlier versions the cluster VTP clock parameter.2 Version 10. This version should not be used once the next official version is available. SXU-C base unit SXU212 version must be 5. 22. If priority bumping is used. 22.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.2 Dependencies • SCU-H (SCZ545) software version must be 1. Bugs • No known bugs.0. The only difference is that the interface lock/unlock operation bug described for version 10.0. . if not set correctly.1 This is an unofficial version almost equal to version 10. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 282 10004_22 © 2008 Tellabs. may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly.

0. 22.11 or higher to support cluster node. Bugs • Channel unit interface lock or unlock may cause communication deadlock state in SXU-C leading eventually to unit reset.0 Dependencies • SCU-H (SCZ545) software version must be 1. may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly. may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly. SXU-C base unit SXU212 version must be lower than 5. SXU-C base unit SXU212 version must be 5.SXU-C Unit: SXZ289 Unit Software 22.11 or higher to support cluster node.0.0B-12 or later. This problem however is very improbable.13 Enhancements and Fixed Bugs • The problem with node traffic going down when Secondary SXU-C is active and SCU is pulled out from slave subrack is fixed. • • Restrictions • • Does not support indication of wrong intersubrack cable installation in fault history. MartisDXX NMS release must be 9. if not set correctly. If priority bumping is used.0B-12 or later. Both SXU-C and CXU-M must support this feature before fault indication can be expected. This happens for example if SCU is changed to SCU-H unit in a slave. After reset the unit operates without problems. The problem concerns only version 10. Dependencies • SCU-H (SCZ545) software version must be 1. (cq200006418). In earlier versions the cluster VTP clock parameter. 10004_22 © 2008 Tellabs. if not set correctly.0. • • Restrictions • No restrictions Bugs • No known bugs. This happens for example if SCU is changed to SCU-H unit in a slave.3 Version 10.4 Version 2. If priority bumping is used MartisDXX NMS version must be 9. In earlier versions the cluster VTP clock parameter. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 283 . Does not support background monitoring and fixing of the possible inconsistencies in SXU-C cross-connect memory (ARAM).

0B-12 or later. Does not support background monitoring and fixing of the possible inconsistencies in SXU-C cross-connect memory (ARAM).11 Dependencies • SCU-H (SCZ545) software version must be 1.SXU-C Unit: SXZ289 Unit Software 22. This happens for example if SCU is changed to SCU-H unit in a slave. This happens for example if SCU is changed to SCU-H unit in a slave. If priority bumping is used MartisDXX NMS version must be 9.11 or higher to support cluster node. If priority bumping is used. SXU-C base unit SXU212 version must be lower than 5. In earlier versions the cluster VTP clock parameter. .11 or higher to support cluster node. Both SXU-C and CXU-M must support this feature before fault indication can be expected.0. MartisDXX NMS release must be 9.0B-12 or later. SXU-C base unit SXU212 version must be lower than 5. 22. may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly.5 Version 2. if not set correctly.0. may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly.12 Dependencies • SCU-H (SCZ545) software version must be 1. • • Restrictions • • Does not support indication of wrong intersubrack cable installation in fault history. if not set correctly. • • Restrictions • No restrictions Bugs • Traffic is down when Secondary SXU-C is active and SCU is pulled out from slave subrack. In earlier versions the cluster VTP clock parameter. Bugs • No known bugs. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 284 10004_22 © 2008 Tellabs.6 Version 2.

In earlier versions the cluster VTP clock parameter. Does not support background monitoring and fixing of the possible inconsistencies in SXU-C cross-connect memory (ARAM).10 is available. If priority bumping is used. may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly. Bugs • Port operations (channel unit interface lock or unlock) may cause deadlock state in SXU-C leading eventually to unit reset. SXU-C base unit SXU212 version must be lower than 5. 22. After reset the unit operates without problems. 22. 10004_22 © 2008 Tellabs.10.10 Dependencies • SCU-H (SCZ545) software version must be 1.8 This is an unofficial version based on SXZ289 version 2. This version should not be used once the official version 2. if not set correctly. Both SXU-C and CXU-M must support this feature before fault indication can be expected. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 285 .0.10 is available.10. The problem concerns only version 2.SXU-C Unit: SXZ289 Unit Software 22.7 Version 2.8 Version 2. 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.11 or higher to support cluster node.9 Version 2.0B-12 or later.7 with only the CIF port type support modification. This behaviour however is very improbable. This happens for example if SCU is changed to SCU-H unit in a slave. MartisDXX NMS release must be 9.9 This is an unofficial version almost equal to version 2. • • Restrictions • • Does not support indication of wrong intersubrack cable installation in fault history.

SXU-C Unit: SXZ289 Unit Software 22. If there is only one unit in the subrack and there is some reason causing an IA fault.7 Dependencies • SCU-H (SCZ545) software version must be 1. This may lead to data errors if the channel unit still believes the port to be even. there is a small probability that X-bus allocation is corrupted. Does not support background monitoring and fixing of the possible inconsistencies in SXU-C cross-connect memory (ARAM). This happens as during the inventory operations there are two simultaneous and mutually unprotected sources of allocation changes. Removing the passive SXU-C from the node may cause short errors in traffic. Does not support indication of wrong intersubrack cable installation in fault history. • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 286 10004_22 © 2008 Tellabs.0. It is possible to modify parameters of a swapped trunk. In earlier versions the cluster VTP clock parameter. Both SXU-C and CXU-M must support this feature before fault indication can be expected. this leads to a state where the node changes the active side continuously which disturbs the traffic seriously. SXU-C base unit SXU212 version must be lower than 5.11 or higher to support cluster node. When using ports with CAS and octet capacity more than 2M but less than 8M. 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). 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. may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly. .10 Version 2. 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. It is possible to affect the port even/uneven parameter in port object M-SET operation. if not set correctly. Allows CAS ON modification to connected port descriptor which causes conflict. This happens for example if SCU is changed to SCU-H unit in a slave. • 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. This may also lead to X-bus integrity problems when a port modified in this way is connected or disconnected. When a GMU unit is added to inventory or removed from inventory. the port modify operation (enable or disable CAS) uses a wrong rule for the change which may lead to X-bus allocation integrity problem.

This may also lead to X-bus integrity problems when a port modified this way is connected or disconnected. This happens for example if SCU is changed to SCU-H unit in a slave. 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). • 10004_22 © 2008 Tellabs.6 Dependencies • SCU-H (SCZ545) software version must be 1. 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. if not set correctly. This can cause continuous traffic errors in the node. Does not support background monitoring and fixing of the possible inconsistencies in SXU-C cross-connect memory (ARAM).0. 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.SXU-C Unit: SXZ289 Unit Software • The cross-connections created by range format cannot be initialised due to an error in the cross-connect object. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 287 . CXU-M will never leave the init state of the slave containing those connections.11 or higher to support cluster node. 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. • 22. Removing the passive SXU-C from the node may cause short errors in traffic. This may lead to data errors if the channel unit still believes the port to be even. may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly. Both SXU-C and CXU-M must support this feature before fault indication can be expected. 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. Does not support indication of wrong intersubrack cable installation in fault history. SXU-C base unit SXU212 version must be lower than 5. • Restrictions • • • • No support for GMU. Allows CAS ON modification to connected port descriptor which causes conflict. In earlier versions the cluster VTP clock parameter. A unit does not disappear from the list of available clock sources when the unit is removed from the inventory. It is possible to affect the port even/uneven parameter in port object M-SET operation.11 Version 2.

Both SXU-C and CXU-M must support this feature before fault indication can be expected. Removing the passive SXU-C from the node may cause short errors in traffic. The cross-connections created by range format cannot be initialised due to an error in the cross-connect object. This can cause continuous traffic errors in the node.0. .5 Dependencies • SCU-H (SCZ545) software version must be 1. • • • 22.12 Version 2. It is possible to modify parameters of a swapped trunk.11 or higher to support cluster node. Does not support indication of wrong intersubrack cable installation in fault history. In earlier versions the cluster VTP clock parameter. 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). Allows CAS ON modification to connected port descriptor which causes conflict. Does not support background monitoring and fixing of the possible inconsistencies in SXU-C cross-connect memory (ARAM).SXU-C Unit: SXZ289 Unit Software • If there is only one unit in the subrack and there is some reason causing an IA fault. 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. A unit does not disappear from the list of available clock sources when the unit is removed from inventory. No support for GMU. may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly. • Restrictions • • • • • No T1 support. 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. this leads to a state where the node changes the active side continuously which disturbs the traffic seriously. CXU-M will never leave the init state of the slave containing those connections. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 288 10004_22 © 2008 Tellabs. SXU-C base unit SXU212 version must be lower than 5. 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. if not set correctly. 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. This happens for example if SCU is changed to SCU-H unit in a slave.

No support for GMU. This can cause continuous traffic errors in the node. This happens for example if SCU is changed to SCU-H unit in a slave. In earlier versions the cluster VTP clock parameter. This may lead to data errors if the channel unit still believes the port to be even. may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly. • Restrictions • • • • • • No T1 support.SXU-C Unit: SXZ289 Unit Software • It is possible to affect the port even/uneven parameter in port object M-SET operation.13 Version 2. 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. 10004_22 © 2008 Tellabs. Does not support background monitoring and fixing of the possible inconsistencies in SXU-C cross-connect memory (ARAM). Does not support indication of wrong intersubrack cable installation in fault history. this leads to a state where the node changes the active side continuously which disturbs the traffic seriously.11 or higher to support cluster node. The cross-connections created by range format cannot be initialised due to an error in the cross-connect object. SXU-C base unit SXU212 version must be lower than 5. CXU-M will never leave the init state of the slave containing those connections. 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.0.4 Dependencies • SCU-H (SCZ545) software version must be 1. Both SXU-C and CXU-M must support this feature before fault indication can be expected. It is possible to modify parameters of a swapped trunk. 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. Does not support contradirectional synchronisation clock sources in protected ring network topology. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 289 . • • • • 22. if not set correctly.

SXU-C base unit SXU212 version must be lower than 5. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 290 10004_22 © 2008 Tellabs. Removing the passive SXU-C from the node may cause short errors in traffic. • • • • • 22. • Restrictions • • • No T1 support. may cause severe slave communication problems because the default parameter value in setup is interpreted incorrectly. A unit does not disappear from the list of available clock sources when the unit is removed from inventory. It is possible to affect the port even/uneven parameter in port object M-SET operation. CXU-M will never leave the init state of the slave containing those connections. this leads to a state where the node changes the active side continuously which disturbs the traffic seriously. This may lead to data errors if the channel unit still believes the port to be even. No support for GMU. Does not support contradirectional synchronisation clock sources in protected ring network topology. 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. It is possible to modify parameters of a swapped trunk. In earlier versions the cluster VTP clock parameter.11 or higher to support cluster node.0.SXU-C Unit: SXZ289 Unit Software 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).3 Dependencies • SCU-H (SCZ545) software version must be 1. 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. if not set correctly. .14 Version 2. Allows CAS ON modification to connected port descriptor which causes conflict. This happens for example if SCU is changed to SCU-H unit in a slave. This can cause continuous traffic errors in the node. If there is only one unit in the subrack and there is some reason causing an IA fault. This may also lead to X-bus integrity problems when a port modified this way is connected or disconnected. The cross-connections created by range format cannot be initialised due to an error in the cross-connect object. 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.

It is possible to modify parameters of a swapped trunk. It is possible to affect the port even/uneven parameter in port object M-SET operation. The real time clock can be used only in adaptive mode. This may lead to data errors if the channel unit still believes the port to be even. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 291 . Does not support background monitoring and fixing of the possible inconsistencies in SXU-C cross-connect memory (ARAM). • • • • • • • 10004_22 © 2008 Tellabs.255s but should not be set to any value other than '0s'. If there is only one unit in the subrack and there is some reason causing an IA fault. Master clock 'clock acceptance time' can be set to any value between 0s. 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. CXU-M will never leave the init state of the slave containing those connections. Allows CAS ON modification to connected port descriptor which causes conflict. The cross-connections created by range format cannot be initialised due to an error in the cross-connect object. This may also lead to X-bus integrity problems when a port modified this way is connected or disconnected. Removing the passive SXU-C from the node may cause short errors in traffic. 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. 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. 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).SXU-C Unit: SXZ289 Unit Software • • • 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. This can cause continuous traffic errors in the node.. 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. this leads to a state where the node changes the active side continuously which disturbs the traffic seriously.. A unit does not disappear from the list of available clock sources when the unit is removed from inventory.

Tellabs 8110 CTE-R (DPZ653) DSP software version must be 1.2 or higher to support SCO module.0 or higher.0 Enhancements and Fixed Bugs (compared with version 1. 1.. Tellabs 8100 network manager support for CTE-R unit is available in Release 13A Service Pack 1 or higher.0 or higher to support new ESHDSL line modes.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. Tellabs 8110 CTE-R (DPZ653) DSP software version must be 3. New ESHDSL line modes are available at version 3.). ESU (EMZ642) software version must be 1. OMH (OMZ675) software version must be 3. (CR ID 300056275) Support for CTE-R/208 modem. Tellabs 8110 CTE-R/208 (CTE807) hardware version must be 1.0 or higher..0) • • Support for ESHDSL line modes. .3 or higher when used with CTE-R.0 can be downloaded to units having the version 1.y of SBZ674 (where y=0. 23.0 or higher when used with CTE-R/208.y or 2.0 or higher.0 or higher. Tellabs 8110 CTE-R (SBZ670) router software version must be 3. Neighbor node loop does not work with 1x208k and 2x208k line modes.1 Version 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 292 10004_22 © 2008 Tellabs. (CR ID 300056275) Dependencies • • • • • • • • • • • Tellabs 8110 CTE-R (CTE689) hardware version must be 1.0 or higher. OMH (OMZ675) software version must be 1. 2. Tellabs 8000 network manager support for CTE-R/208 unit is available in Release 15A or higher. The version 2. SCO module version must be 4.0 or higher to support ESHDSL line modes. Restrictions • • CTE-R/208 can not be used with ESU.

Restrictions • Version 1. Tellabs 8110 CTE-R (SBZ670) router software version must be 3. OMH (OMZ675) software version must be 1. Dependencies • • • • • • Tellabs 8110 CTE-R (CTE689) hardware version must be 1. Bugs • No known bugs.0 of SBZ674 can not be used with CTE-R/208 modem.Tellabs 8110 CTE-R and CTE-R/208 SHDSL NTU: SBZ674 Unit Software Bugs • No known bugs.0 or higher.2 or higher to support SCO module. Tellabs 8110 CTE-R (DPZ653) DSP software version must be 1.3 or higher.0 or higher. ESU (EMZ642) software version must be 1.2 Version 1.0 or higher. 23. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 293 .0 Enhancements and Fixed Bugs • This is the first official version. 10004_22 © 2008 Tellabs. Tellabs 8100 manager support for this unit is available in Release 13A Service Pack 1 or higher.

36 and CTES/208 X. CTE-S V. USW software (SBZ673) for Tellabs 8110 CTE-S/208 V.x of DPZ653 but then point-to-point operation is not available.21 (CTE686).0) • • Support for ESHDSL line modes. OMH (OMZ675) software version must be 3. CTE-S/208 V.0 or higher. CTE-R (CTE689) units must be version 2.35 (CTE803). USW software (SBZ673) for Tellabs 8110 CTE CTE-S V. CTE-R (CTE689). 1.0 can be downloaded to CTE-S/208 units having the version 3. . CTE-R and CTE-R/208 SHDSL NTU: DPZ653 DSP Software The software DPZ653 is used on Tellabs 8110 CTE-S V. Tellabs 8110 CTE-S/208 hardware version must be 2. (CR ID 300056272) Dependencies • • • • • • • • • • Tellabs 8110 CTE-S hardware version must be 2.35 (CTE685).y and 2.0 or higher. CTE-S/208.3 Enhancements and Fixed Bugs (compared with version 2.0 or higher.0 or higher to support ESHDSL line modes Tellabs 8100 network manager support for CTE-S units is available in Release 13 or higher.). CTE-S X. CTE-S/208 X.36 (CTE688).1 Version 3.0 or higher to support ESHDSL line modes.2 or higher to support SCO module. 1. 2.36 (CTE806).21 (CTE804) and CTE-R/208 (CTE807) units.21 must be version 3. (CR ID 300056272) Support for CTE-S/208 modems.) Version 3.35 (CTE685).0 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 294 10004_22 © 2008 Tellabs.35. 24. The version 3. CTE-R and CTE-R/208 SHDSL NTU: DPZ653 DSP Software 24 Tellabs 8110 CTE-S.y of DPZ653 (where y=0.3 can be downloaded to CTE-S units having the version 3. CTE-S/208 V. Tellabs 8110 CTE-R (CTE689) hardware version must be 1. 2. OMH (OMZ675) software version must be 1.. CTE-S X.36 (CTE688).. Tellabs 8110 CTE-R/208 (CTE807) hardware version must be 1..21 (CTE686). The version 3. CTE-S V.Tellabs 8110 CTE-S.0 can also be downloaded to units having the version 1.0 or higher. CTE-S/208 V. CTE-S/208..y of DPZ653 (where y=0. SCO module version must be 4.0 or higher.

x and unit SW version 1.35 (CTE685).2 or higher to support SCO module. OMH (OMZ675) software version must be 1. Tellabs 8110 CTE-R hardware version must be 1.36 (CTE688). when one line is without attenuation and there is attenuation in the other line. Restrictions • • In case of two-pair mode. This version can be used with HW version 1.x but in that case point-to-point operation is not supported. Bugs • No known bugs.0 Enhancements and Fixed Bugs (compared with version 1. 10004_22 © 2008 Tellabs.0 or higher. "power back-off" may be ON or may be OFF for both lines.36 and CTE-S X. In case of two-pair mode. USW software (SBZ673) for Tellabs 8110 CTE CTE-S V. CTE-R and CTE-R/208 SHDSL NTU: DPZ653 DSP Software • Tellabs 8000 network manager support for CTE-S/208 unit is available in Release 15A or higher.0 or higher. (CR ID 200013029) Dependencies • • • • • Tellabs 8110 CTE-S hardware version must be 2. when one line is without attenuation and there is attenuation in the other line. 24.21 (CTE686). CTE-S X.0 or higher. Tellabs 8100 manager support for this unit is available in Release 13 or higher. CTE-S V. CTE-S/208.Tellabs 8110 CTE-S.0) • Point to point feature for CTE-S. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 295 .2 Version 2. "power back-off" may be ON or may be OFF for both lines. This version can be used with HW version 1.35. Bugs • No known bugs.21 must be version 1. CTE-S V. Restrictions • • • • Neighbor node loop does not work with 1x208k and 2x208k line modes.x but in that case point-to-point operation is not supported. USW software (SBZ673) for Tellabs 8110 CTE-S V.0 does not support ESHDSL modes.x and unit SW version 1. CTE-R (CTE689) units below version 3.

Restrictions • • In case of two-pair mode.21 must be version 1.Tellabs 8110 CTE-S.35. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 296 10004_22 © 2008 Tellabs. OMH (OMZ675) software version must be 1. CTE-R and CTE-R/208 SHDSL NTU: DPZ653 DSP Software 24. Dependencies • • • • • Tellabs 8110 CTE-S hardware version must be 1. This version can be used with HW version 1.0 or higher. CTE-S V. USW software (SBZ673) for Tellabs 8110 CTE-S V. CTE-S/208.x and unit SW version 1. "power back-off" may be ON or may be OFF for both lines.3 Version 1. . Tellabs 8100 manager support for this unit is available in Release 13 or higher.0.3 Enhancements and Fixed Bugs • This is the first official version. when one line is without attenuation and there is attenuation in the other line.x but in that case point-to-point operation is not supported. Tellabs 8110 CTE-R (CTE689) hardware version must be 1.0 or higher.2 or higher to support SCO module.36 and CTE-S X. Bugs • No known bugs.

3 can be downloaded to CTE-S/208 units having the version 3.). 10004_22 © 2008 Tellabs.703 (CTE805) modems.0) • • Support for ESHDSL line modes. SCO module version must be 4.. USW software (SBZ673) for Tellabs 8110 CTE-S G. 1. (CR ID 300056272) Dependencies • • • • • • • • • Tellabs 8110 CTE-S hardware version must be 2.703 SHDSL NTU: DPZ654 DSP Software The software DPZ654 is used on Tellabs 8110 CTE-S G. 1. 2. OMH (OMZ675) software version must be 1.1 Version 3.3 can be downloaded to CTE-S units having the version 3.0 or higher to support ESHDSL line modes. The version 3.703 (CTE805) units must be version 3.y and 2.703 (CTE687) and CTE-S/208 G.0 or higher.703 SHDSL NTU: DPZ654 DSP Software 25 Tellabs 8110 CTE-S G.0 or higher.x of DPZ654 but then point-to-point operation is not available.0 or higher to support ESHDSL line modes Tellabs 8100 network manager support for CTE-S units is available in Release 13 or higher.703 (CTE687) unit must be version 2. 25.) Version 3.Tellabs 8110 CTE-S G. 2.. USW software (SBZ673) for Tellabs 8110 CTE-S/208 G. Tellabs 8110 CTE-S/208 hardware version must be 2. OMH (OMZ675) software version must be 3.2 or higher to support SCO module.703 (CTE805) units.y of DPZ654 (where y=0.. Tellabs 8000 network manager support for CTE-S/208 unit is available in Release 15A or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 297 .3 can also be downloaded to units having the version 1.3 Enhancements and Fixed Bugs (compared with version 2. (CR ID 300056272) Support for CTE-S/208 G.y of DPZ654 (where y=0..0 or higher.0 or higher. The version 3.

USW software (SBZ673) for Tellabs 8110 CTE-S G.703 (CTE687) unit below version 3. USW software (SBZ673) for Tellabs 8110 CTE-S G. Restrictions • • In case of two-pair mode. Bugs • No known bugs.2 Version 2.0 or higher. (CR ID 200013029) Dependencies • • • • Tellabs 8110 CTE-S hardware version must be 2.Tellabs 8110 CTE-S G. Bugs • No known bugs. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 298 10004_22 © 2008 Tellabs. Tellabs 8100 manager support for this unit is available in Release 13 or higher. when one line is without attenuation and there is attenuation in the other line. This version can be used with HW version 1.0 does not support ESHDSL modes.2 or higher to support SCO module.703 (CTE687) and CTE-S/208 G.703 (CTE805) units must be version 1. 25. This version can be used with HW version 1.0 or higher.x but in that case point-to-point operation is not supported.0 Enhancements and Fixed Bugs (compared with version 1. "power back-off" may be ON or may be OFF for both lines.x and unit SW version 1. . "power back-off" may be ON or may be OFF for both lines.x but in that case point-to-point operation is not supported. when one line is without attenuation and there is attenuation in the other line. OMH (OMZ675) software version must be 1.703 SHDSL NTU: DPZ654 DSP Software Restrictions • • • • Neighbor node loop does not work with 1x208k and 2x208k line modes. In case of two-pair mode.0) • Point to point feature for CTE-S.x and unit SW version 1.

10004_22 © 2008 Tellabs. Bugs • No known bugs. Restrictions • • In case of two-pair mode.Tellabs 8110 CTE-S G. Dependencies • • • • Tellabs 8110 CTE-S hardware version must be 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 299 . OMH (OMZ675) software version must be 1. This version can be used with HW version 1. Tellabs 8100 manager support for this unit is available in Release 13 or higher.2 or higher to support SCO module.0 or higher. when one line is without attenuation and there is attenuation in the other line.x but in that case point-to-point operation is not supported.0.3 Enhancements and Fixed Bugs • This is the first official version. USW software (SBZ673) for Tellabs 8110 CTE-S G. "power back-off" may be ON or may be OFF for both lines.703 SHDSL NTU: DPZ654 DSP Software 25.703 (CTE805) units must be version 1.3 Version 1.x and unit SW version 1.703 (CTE687) and CTE-S/208 G.

1. 2.0 Enhancements and Fixed Bugs (compared with version 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 300 10004_22 © 2008 Tellabs.1 Version 3. 26.0 or higher to support ESHDSL line modes.0 or higher.y of SBZ673 (where y=0.703 (CTE805) units.21 must be version 3. DSP software (DPZ654) for Tellabs 8110 CTE-S G. 1. SCO module version must be 4. .36 and CTE-S X..y of SBZ673 (where y=0.x of SBZ673 but then point-to-point operation is not available. OMH (OMZ675) software version must be 3.) Version 3.21 (CTE686).703 must be version 3.).21 (CTE804) and CTE-S/208 G.35 (CTE685). CTE-S/208 V.0 can be downloaded to CTE-S units having the version 3.35.2 or higher to support SCO module..0 or higher to support ESHDSL line modes Tellabs 8100 network manager support for CTE-S units is available in Release 13 or higher. CTE-S X.. CTE-S/208 V.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.36 (CTE806).703 must be version 1.36 (CTE688). Tellabs 8110 CTE-S/208 hardware version must be 2.0 can be downloaded to CTE-S/208 units having the version 3. CTE-S/208 X.0 or higher.0 or higher. (CR ID 300056272) Support for CTE-S/208 modems.35 (CTE803).0) • • Support for ESHDSL line modes.35.. The version 3. CTE-S/208 V. CTE-S G. (CR ID 300056272) Dependencies • • • • • • • • • • • Tellabs 8110 CTE-S hardware version must be 2.1 or higher.0 can also be downloaded to units having the version 1. 2. DSP software (DPZ654) for Tellabs 8110 CTE-S/208 G.y and 2.36 and CTES/208 X. Tellabs 8000 network manager support for CTE-S/208 unit is available in Release 15A or higher.21 must be version 1. DSP software (DPZ653) for Tellabs 8110 CTE-S/208 V.703 (CTE687). DSP software (DPZ653) for Tellabs 8110 CTE-S V. OMH (OMZ675) software version must be 1.0 or higher.1 or higher. CTE-S V. The version 3. CTE-S V.

36 and CTE-S X.0 or higher.21 must be version 1. Version 2. Bugs • No known bugs.35. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 301 .36 and CTE-S X.Tellabs 8110 CTE-S and CTE-S/208 SHDSL NTU: SBZ673 Unit Software Restrictions • Neighbor node loop does not work with 1x208k and 2x208k line modes.1 or higher. CTE-S V. Bugs • No known bugs. 10004_22 © 2008 Tellabs. Tellabs 8100 manager support for this unit is available in Release 13 or higher.703 must be version 1.0) • Point to point feature for CTE-S.2 or higher to support SCO module. DSP software (DPZ653) for Tellabs 8110 CTE-S V. (CR ID 200013029) Dependencies • • • • • Tellabs 8110 CTE-S hardware version must be 2.2 Version 2.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.0 or higher if point-to-point feature is to be utilized. Restrictions • • • DSP software (DPZ653) for Tellabs 8110 CTE-S V. CTE-S V.0 Enhancements and Fixed Bugs (compared with version 1.0 of SBZ673 can not be used with CTE-S/208 modems. 26.35.703 must be version 2. OMH (OMZ675) software version must be 1. DSP software (DPZ654) for Tellabs 8110 CTE-S G.1 or higher.

OMH (OMZ675) software version must be 1.2 or higher to support SCO module. Dependencies • • • • • Tellabs 8110 CTE-S hardware version must be 1.Tellabs 8110 CTE-S and CTE-S/208 SHDSL NTU: SBZ673 Unit Software 26. Restrictions • Version 1.703 must be version 1. Bugs • No known bugs. CTE-S V. DSP software (DPZ653) for Tellabs 8110 CTE-S V.21 must be version 1. .0 of SBZ673 can not be used with CTE-S/208 modems.0 Enhancements and Fixed Bugs • This is the first official version.35. Tellabs 8100 manager support for this unit is available in Release 13 or higher.0. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 302 10004_22 © 2008 Tellabs. DSP software (DPZ654) for Tellabs 8110 CTE-S G.36 and CTE-S X.1 or higher.3 Version 1.1 or higher.

10004_22 © 2008 Tellabs. Tellabs 8100 manager support for time dependent DTE capacity control is available in Release 14 or higher.2 or earlier). MartisDXX Manager support for this unit is available in Release 12A or higher..5 or higher to support HCQ-2M module.1 Version 3. The version 3. GMH (GMZ283) software version must be 10. These units support only unidirectional EECRC. and with STU-320.. CTU-512 hardware version must be 2.110/CRC feature (EECRC) is not fully compatible with HTU-2M (USW SBZ389 V1. 1.0 can be downloaded to CTU-512 units having the version 3. Enhancement.35 (CTU680) and CTU-512 X. Restrictions • The End-to-End V. 2.0 or higher if point-to-point feature is to be utilized. • Bugs • No known bugs. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 303 .0).0 or higher. 27.21 (CTU681) units. QMH (QMZ540) software version must be 10.0 or higher to support HCE-2M-1P and HCE-2M-2P modules.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. and therefore bidirectional EECRC in CTU-512 misinterprets path to be constantly UNAVAILABLE. STU-576.0 Enhancements and Fixed Bugs • Support for AMIC flash. (CR ID 200025832) Dependencies • • • • • CTU-512 hardware version must be 1. STU-1088-2W and STU-2304 (USW SBZ387 V 1.).y of SBZ672 (where y=0.

QMH (QMZ540) software version must be 10.2 or earlier). . These units support only unidirectional EECRC. STU-576. Bug. and with STU-320. • Bugs • No known bugs.1 Enhancements and Fixed Bugs • CTU-512 uses wrong HW version bit mask when deciding is the HW capable of point-topoint operation. Restrictions • The End-to-End V. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 304 10004_22 © 2008 Tellabs.Tellabs 8110 CTU-512 HDSL NTU: SBZ672 Unit Software 27.5 or higher to support HCQ-2M module. STU-1088-2W and STU-2304 (USW SBZ387 V 1. MartisDXX Manager support for this unit is available in Release 12A or higher. (CR ID 200025220) Dependencies • • • • • CTU-512 hardware version must be 1.0 or higher if point-to-point feature is to be utilized.0 or higher to support HCE-2M-1P and HCE-2M-2P modules. CTU-512 hardware version must be 2. Tellabs 8100 manager support for time dependent DTE capacity control is available in Release 14 or higher.0). and therefore bidirectional EECRC in CTU-512 misinterprets path to be constantly UNAVAILABLE.2 Version 2. GMH (GMZ283) software version must be 10.110/CRC feature (EECRC) is not fully compatible with HTU-2M (USW SBZ389 V1.0 or higher.

(CR ID 200015080) CTU-512 sent 'G.Tellabs 8110 CTU-512 HDSL NTU: SBZ672 Unit Software 27. Tellabs 8100 manager support for time dependent DTE capacity control is available in Release 14 or higher. and therefore bidirectional EECRC in CTU-512 misinterprets path to be constantly UNAVAILABLE. STU-576. (CR ID 200005461) Dependencies • • • • • CTU-512 hardware version must be 1. Enhancement. CTU-512 hardware version must be 2.0 or higher if point-to-point feature is to be utilized. These units support only unidirectional EECRC.0). and with STU-320. Tellabs 8100 Network Manager read wrong counter values from CTU (current counter values were not moved to history table before reading took place).0 or higher to support HCE-2M-1P and HCE-2M-2P modules. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 305 . (CR ID 200013025) Possibility to change the DTE capacity depending on the time of day. As a result. Now this bug is fixed. Enhancement. (CR ID 200025220) 10004_22 © 2008 Tellabs.5 or higher to support HCQ-2M module. STU-1088-2W and STU-2304 (USW SBZ387 V 1. MartisDXX Manager support for this unit is available in Release 12A or higher.3 Version 2. QMH (QMZ540) software version must be 10. • Bugs • CTU-512 uses wrong HW version bit mask when deciding is the HW capable of point-topoint operation. Bug. Restrictions • The End-to-End V.2 or earlier).0 or higher.0 Enhancements and Fixed Bugs • • • Point-to-point feature for CTU-512.826 performance event' alarms too early. GMH (GMZ283) software version must be 10.110/CRC feature (EECRC) is not fully compatible with HTU-2M (USW SBZ389 V1.

0). STU-1088-2W and STU-2304 (USW SBZ387 V 1. (CR ID 200005461) Tellabs® 8100 Managed Access System Unit Software Version Dependencies 306 10004_22 © 2008 Tellabs. Dependencies • • • • CTU-512 hardware version must be 1. and with STU-320. Restrictions • The End-to-End V.4 Version 1.2 or earlier).826 performance event'-alarms too early. QMH (QMZ540) software version must be 10. STU-576. .1. MartisDXX Manager support for this unit is available in Release 12A or higher. and therefore bidirectional EECRC in CTU-512 misinterprets path to be constantly UNAVAILABLE.110/CRC feature (EECRC) is not fully compatible with HTU-2M (USW SBZ389 V1. These units support only unidirectional EECRC.0 or higher to support HCE-2M-1P and HCE-2M-2P modules. GMH (GMZ283) software version must be 10. Bugs • CTU-S sends 'G.Tellabs 8110 CTU-512 HDSL NTU: SBZ672 Unit Software 27.0 Enhancements and Fixed Bugs • This is the first official version.0 or 1.5 or higher to support HCQ-2M module.

0 or higher. NOTE! No attempt should be made to download versions prior to 4.0 or higher. 2. 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. Tellabs 8110 CTE-R/208 SHDSL and Tellabs 8110 STE-10M SHDSL NTUs: SBZ670 Unit Software 28 Tellabs 8110 CTU-R HDSL.4 can be downloaded to Tellabs 8110 CTE-R units having the version x. 1.4 can be downloaded to Tellabs 8110 CTE-R/208 units having the version 4. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 307 .0 or higher..y of SBZ670 (where y=0...3) • Frame Relay fragmentation. 1. 2.3 or higher.).).).Tellabs 8110 CTU-R HDSL.0 or higher. The version 4. 28. Tellabs 8110 CTER SHDSL. Tellabs 8110 STE-10M (STE790) hardware version must be 1.. The version 4. 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..) then factory default configuration is set. Tellabs 8110 CTU-R (SBZ671) unit software version must be 1. 2. Tellabs 8110 CTE-R SHDSL. 1. Tellabs 8110 CTE-R (CTE689) hardware version must be 1. The version 4.1 Version 4.y of SBZ670 (where x is 1.4 can be downloaded to Tellabs 8110 STE-10M units having the version 4..4 can be downloaded to Tellabs 8110 CTU-R units having the version x.. 1.y of SBZ670 (where y=0. Tellabs 8110 CTE-R/208 (CTE807) hardware version must be 1. The version 4.y of SBZ670 (where x is 3 or 4 and y=0. If version before download was 1. 2..y (where y=0.y or 2.0 to Tellabs 8110 STE-10M.4 Enhancements and Fixed Bugs (compared with version 4..). 1.. 10004_22 © 2008 Tellabs. (CR ID 300079019) Dependencies • • • • • Tellabs 8110 CTU-R (CTU399) hardware version must be 2. 3 or 4 and y=0.

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

0 or higher. Tellabs 8110 CTU-R (SBZ671) unit software version must be 1. Ethernet/VLAN encapsulation on WAN side for routed traffic. Tellabs 8110 STE-10M (SBZ792) unit software version must be 1.2) • • Ethernet MAC/PHY link down alarm is generated if Ethernet cable is unplugged. MartisDXX Manager support for Tellabs 8110 CTU-R is available in Release 12 Service Pack 1 or higher.0 or higher. (CR ID 300036351) Pause frames were mistakenly forwarded when spanning tree transparency was enabled.3 or higher. Tellabs 8110 CTE-R/208 SHDSL and Tellabs 8110 STE-10M SHDSL NTUs: SBZ670 Unit Software 28. Tellabs 8110 CTE-R (SBZ674) unit software version must be 1. Tellabs 8110 CTE-R/208 (CTE807) hardware version must be 1. Tellabs 8110 STE-10M (STE790) hardware version must be 1. background connectivity monitoring tool.Tellabs 8110 CTU-R HDSL.0 or higher when used with CTE-R/208. packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher. Tellabs 8100 manager support for Tellabs 8110 CTE-R is available in Release 13A Service Pack 1 or higher. Tellabs 8110 CTE-R SHDSL. and LMI functionalities are available in Release 13 Service Pack 1 or higher. Tellabs 8100 manager support for Spanning Tree Transparency is available in Release 15 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 309 . Tellabs 8110 STE-10M (DPZ794) unit software version must be 1. Tellabs 8100 manager support for Tellabs 8110 STE-10M is available in Release 14 Service Pack 3 or higher. Tellabs 8110 CTE-R (CTE689) hardware version must be 1. logging.2 Version 4.0 or higher. Tellabs 8100 manager support for enhanced ping. Tellabs 8000 network manager support for “Ethernet MAC/PHY link down” alarm is available in Release 15B or higher.0 or higher. • • • • 10004_22 © 2008 Tellabs.0 or higher. OSPFv2 and IP routing table enlargement to 4000 routes are available in Release 13A Service Pack 1 or higher. Tellabs 8110 CTE-R (DPZ653) data pump software version must be 1.3 Enhancements and Fixed Bugs (compared with version 4.3 or higher when used with CTE-R and version 3.0 or higher when used with CTE-R and version 2. MartisDXX Manager support for NAT. VLAN ID mapping. Tellabs 8100 manager support for DiffServ. tunnelling. bridge CoS. VLAN filtering.0 or higher. (CR ID 300073486) Dependencies • • • • • • • • • • • • • • Tellabs 8110 CTU-R (CTU399) hardware version must be 2. traceroute.0 or higher when used with CTE-R/208. Older versions show it as “Undefined error code” with GPT 63 and SPT 90. Tellabs 8000 network manager support for Tellabs 8110 CTE-R/208 is available in Release 15A or higher.

28. Bugs • No known bugs. Tellabs 8110 STE-10M (STE790) hardware version must be 1. and LMI functionalities are available in Release 13 Service Pack 1 or higher. 13A.2 Enhancements and Fixed Bugs (compared with version 4. Tellabs 8100 manager support for Tellabs 8110 CTE-R is available in Release 13A Service Pack 1 or higher.0 or higher. VLAN ID mapping. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 310 10004_22 © 2008 Tellabs. 14 or 15 then Rule management.3 Version 4. 13.0 or higher when used with CTE-R/208. Tellabs 8110 CTE-R (DPZ653) data pump software version must be 1. MartisDXX Manager support for NAT. Tellabs 8110 CTU-R (SBZ671) unit software version must be 1. OSPFv2 and IP routing table enlargement to 4000 routes are available in Release 13A Service Pack 1 or higher. logging. 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. background connectivity monitoring tool.0 or higher. Tellabs 8110 STE-10M (SBZ792) unit software version must be 1. packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher.Tellabs 8110 CTU-R HDSL.0 or higher when used with CTE-R and version 2. VLAN filtering. The restriction has been fixed in Tellabs 8000 manager release R15-SP2.0 or higher. Tellabs 8110 CTE-R SHDSL. NAT management and Packet filtering menus are not accessible. Tellabs 8110 CTE-R/208 (CTE807) hardware version must be 1. . traceroute.3 or higher when used with CTE-R and version 3.0 or higher when used with CTE-R/208. Tellabs 8100 manager support for DiffServ.3 and R15A. tunnelling. Tellabs 8110 CTE-R (CTE689) hardware version must be 1. Tellabs 8110 STE-10M (DPZ794) unit software version must be 1. Tellabs 8100 manager support for enhanced ping. Ethernet/VLAN encapsulation on WAN side for routed traffic.0 or higher. bridge CoS. Tellabs 8110 CTE-R/208 SHDSL and Tellabs 8110 STE-10M SHDSL NTUs: SBZ670 Unit Software Restrictions • If used MartisDXX Manager or Tellabs 8100 Manager or Tellabs 8000 manager Release is 12A.1) • Traffic prioritization does not work correctly.0 or higher. Tellabs 8110 CTE-R (SBZ674) 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.3 or higher.

0 or higher.4 Version 4.0 or higher. MartisDXX Manager support for Tellabs 8110 CTU-R is available in Release 12 Service Pack 1 or higher. Bugs • Pause frames are mistakenly forwarded when spanning tree transparency is enabled. 13. (CR ID 300037420) Dependencies • • • • • • • • • • • Tellabs 8110 CTU-R (CTU399) hardware version must be 2. Tellabs 8110 STE-10M (SBZ792) unit software version must be 1.Tellabs 8110 CTU-R HDSL.0 or higher. Tellabs 8110 CTE-R (SBZ674) unit software version must be 1. 10004_22 © 2008 Tellabs.0 or higher. Tellabs 8110 STE-10M (DPZ794) unit software version must be 1. Tellabs 8110 CTE-R/208 (CTE807) hardware version must be 1. 13A.0 or higher when used with CTE-R/208.0 or higher. Tellabs 8110 CTE-R (DPZ653) data pump software version must be 1.3 and R15A. Tellabs 8000 network manager support for Tellabs 8110 CTE-R/208 is available in Release 15A or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 311 . Tellabs 8100 manager support for Spanning Tree Transparency is available in Release 15 or higher.1 Enhancements and Fixed Bugs (compared with version 4.3 or higher.0 or higher when used with CTE-R and version 2. Tellabs 8110 STE-10M (STE790) hardware version must be 1. Tellabs 8110 CTE-R SHDSL. Tellabs 8110 CTU-R (SBZ671) unit software version must be 1. NAT management and Packet filtering menus are not accessible. Tellabs 8100 manager support for Tellabs 8110 CTE-R is available in Release 13A Service Pack 1 or higher. 28. Restrictions • If used MartisDXX Manager or Tellabs 8100 Manager or Tellabs 8000 manager Release is 12A. 14 or 15 then Rule management.0 or higher. Tellabs 8110 CTE-R (CTE689) hardware version must be 1. The restriction has been fixed in Tellabs 8000 manager release R15-SP2.0 or higher when used with CTE-R/208. Tellabs 8110 CTE-R/208 SHDSL and Tellabs 8110 STE-10M SHDSL NTUs: SBZ670 Unit Software • • • Tellabs 8100 manager support for Tellabs 8110 STE-10M is available in Release 14 Service Pack 3 or higher.0) • Spanning Tree Transparency.3 or higher when used with CTE-R and version 3. This is a new feature which enables transparent forwarding of customer’s bridge control protocol PDUs. (CR ID 300073486).

bridge CoS. and LMI functionalities are available in Release 13 Service Pack 1 or higher. traceroute. Tellabs 8000 network manager support for Tellabs 8110 CTE-R/208 is available in Release 15A or higher • • • Restrictions • If used MartisDXX Manager or Tellabs 8100 Manager or Tellabs 8000 manager Release is 12A. Tellabs 8110 CTU-R (SBZ671) unit software version must be 1. packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher.0 or higher.0 Enhancements and Fixed Bugs (compared with version 3. Tellabs 8100 manager support for Tellabs 8110 STE-10M is available in Release 14 Service Pack 3 or higher.5 Version 4.0 or higher. Tellabs 8100 manager support for Spanning Tree Transparency is available in Release 15 or higher. Tellabs 8110 CTE-R/208 (CTE807) hardware version must be 1. The restriction has been fixed in Tellabs 8000 manager release R15-SP2. Rule management (ICMP) does not work correctly with Tellabs 8110 STE-10M. Tellabs 8110 STE-10M (STE790) hardware version must be 1. Tellabs 8100 manager support for enhanced ping.3 and R15A. Tellabs 8110 CTU-R and Tellabs 8110 CTE-R. tunnelling. background connectivity monitoring tool. 13A. NAT management and Packet filtering menus are not accessible. In overload situations real time traffic does not get any higher priority than other traffic classes. Tellabs 8110 CTE-R (CTE689) hardware version must be 1. 28. (CR ID 300052014) Pause frames are mistakenly forwarded when spanning tree transparency is enabled. 14 or 15 then Rule management. Bugs • • Traffic prioritization does not work correctly.3 or higher. (CR ID 200035758) Dependencies • • • • • Tellabs 8110 CTU-R (CTU399) hardware version must be 2. OSPFv2 and IP routing table enlargement to 4000 routes are available in Release 13A Service Pack 1 or higher. . Tellabs 8100 manager support for DiffServ. VLAN ID mapping. (CR ID 300073486). logging.Tellabs 8110 CTU-R HDSL.0 or higher. Tellabs 8110 CTE-R/208 SHDSL and Tellabs 8110 STE-10M SHDSL NTUs: SBZ670 Unit Software • • • MartisDXX Manager support for NAT.2) • • Support for Tellabs 8110 STE-10M.0 or higher. VLAN filtering. 13. Tellabs 8110 CTE-R SHDSL. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 312 10004_22 © 2008 Tellabs. Ethernet/VLAN encapsulation on WAN side for routed traffic.

Tellabs 8100 manager support for DiffServ. Bugs • Traffic prioritization does not work correctly. Ethernet/VLAN encapsulation on WAN side for routed traffic. MartisDXX Manager support for Tellabs 8110 CTU-R is available in Release 12 Service Pack 1 or higher.3 or higher when used with CTE-R and version 3. • • Restrictions • If used MartisDXX Manager or Tellabs 8100 Manager or Tellabs 8000 manager Release is 12A.Tellabs 8110 CTU-R HDSL. Tellabs 8110 CTE-R/208 SHDSL and Tellabs 8110 STE-10M SHDSL NTUs: SBZ670 Unit Software • • • • • • • • • Tellabs 8110 CTE-R (SBZ674) unit software version must be 1. Tellabs 8100 manager support for Tellabs 8110 CTE-R is available in Release 13A Service Pack 1 or higher. background connectivity monitoring tool. Tellabs 8100 manager support for Tellabs 8110 STE-10M is available in Release 14 Service Pack 3 or higher. Tellabs 8110 CTE-R SHDSL. The restriction has been fixed in Tellabs 8000 manager release R15-SP2. Tellabs 8110 STE-10M (DPZ794) unit software version must be 1. 13.3 and R15A. In overload situations real time traffic does not get any higher priority than other traffic classes. 14 or 15 then Rule management.0 or higher when used with CTE-R and version 2. and LMI functionalities are available in Release 13 Service Pack 1 or higher. VLAN ID mapping. 13A. Tellabs 8110 CTE-R (DPZ653) data pump software version must be 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 313 .0 or higher when used with CTE-R/208. MartisDXX Manager support for NAT.0 or higher.0 or higher when used with CTE-R/208. Tellabs 8000 network manager support for Tellabs 8110 CTE-R/208 is available in Release 15A or higher. NAT management and Packet filtering menus are not accessible. traceroute. bridge CoS. (CR ID 300052014) 10004_22 © 2008 Tellabs. Tellabs 8100 manager support for enhanced ping. Tellabs 8110 STE-10M (SBZ792) unit software version must be 1.0 or higher. VLAN filtering. tunnelling. OSPFv2 and IP routing table enlargement to 4000 routes are available in Release 13A Service Pack 1 or higher. logging. packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher.

Tellabs 8110 CTE-R (SBZ674) software version must be 1. Tellabs 8100 manager support for DiffServ. Tellabs 8100 manager support for enhanced ping. logging.0.0) • • • • Enhancement: Buffer handling adjustment for better performance in bi-directional traffic flow tests (CR ID 200011373).6 Version 3. bridge CoS.0 or higher. Tellabs 8100 manager support for Tellabs 8110 CTE-R is available in Release 13A Service Pack 1 or higher.3 or higher. Tellabs 8110 CTE-R (CTE689) hardware version must be 1. Tellabs 8110 CTU-R (SBZ671) software version must be 1.0 (CR ID 200011433) Enhancement: Added “N/A” state to the background connectivity monitoring tool in order to achive similar behaviour to ESU. OSPFv2 and IP routing table enlargement to 4000 routes are available in Release 13A Service Pack 1 or higher.0 or higher. (CR ID 200035758) Tellabs® 8100 Managed Access System Unit Software Version Dependencies 314 10004_22 © 2008 Tellabs.0. Tellabs 8110 CTE-R/208 SHDSL and Tellabs 8110 STE-10M SHDSL NTUs: SBZ670 Unit Software 28. MartisDXX Manager support for NAT. Ethernet/VLAN encapsulation on WAN side for routed traffic.0 or higher. Tellabs 8110 CTE-R (DPZ653) data pump software version must be 1. Dependencies • • • • • • • • • • Tellabs 8110 CTU-R (CTU399) hardware version must be 2. packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher. and LMI functionalities are available in Release 13 Service Pack 1 or higher. Tellabs 8110 CTU-R and Tellabs 8110 CTE-R. background connectivity monitoring tool.Tellabs 8110 CTU-R HDSL. . VLAN ID mapping. Restrictions • This version should NOT be downloaded to STE-10M. traceroute. MartisDXX Manager support for Tellabs 8110 CTU-R is available in Release 12 Service Pack 1 or higher. tunnelling.2 Enhancements and Fixed Bugs (compared with version 3. Bug fix: Possible to set (OSPF) Router ID back to 0. Enhancement: MAC address may exist in multiple VLANs on the WAN side of CTUR/CTE-R (CR ID 200011413). VLAN filtering. Bugs • Rule management (ICMP) does not work correctly with Tellabs 8110 STE-10M. Tellabs 8110 CTE-R SHDSL.3 or higher.

Tellabs 8110 CTE-R (DPZ653) data pump software version must be 1. 28. and LMI functionalities are available in Release 13 Service Pack 1 or higher. Tellabs 8110 CTE-R (SBZ674) software version must be 1.0 Enhancements and Fixed Bugs (compared with version 2.4) • • • • • • Differentiated Services (DiffServ) and bridge CoS OSPFv2 Ethernet/VLAN encapsulation on WAN side for routed traffic VLAN filtering. Tellabs 8100 manager support for enhanced ping. Bugs • No known bugs. Tellabs 8110 CTE-R/208 SHDSL and Tellabs 8110 STE-10M SHDSL NTUs: SBZ670 Unit Software 28. 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. Tellabs 8110 CTE-R SHDSL.0 or higher. 10004_22 © 2008 Tellabs. MartisDXX Manager support for Tellabs 8110 CTU-R is available in Release 12 Service Pack 1 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 315 . logging. tunnelling. Tellabs 8110 CTE-R (CTE689) hardware version must be 1.Tellabs 8110 CTU-R HDSL.0 or higher.7 Version 3. Tellabs 8100 manager support for Tellabs 8110 CTE-R is available in Release 13A Service Pack 1 or higher. background connectivity monitoring tool. Restrictions • This version should NOT be downloaded to Tellabs 8110 STE-10M. MartisDXX Manager support for NAT. Ethernet/VLAN encapsulation on WAN side for routed traffic. packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher. traceroute.3 or higher.8 Version 3.1 This is an internal test version.3 or higher. bridge CoS. VLAN filtering. Tellabs 8100 manager support for DiffServ. Tellabs 8110 CTU-R (SBZ671) software version must be 1.0 or higher. OSPFv2 and IP routing table enlargement to 4000 routes are available in Release 13A Service Pack 1 or higher. VLAN ID mapping.

and LMI functionalities are available in Release 13 Service Pack 1 or higher.0 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 316 10004_22 © 2008 Tellabs. MartisDXX Manager support for NAT. Bugs • No known bugs. Tellabs 8110 CTE-R SHDSL. (CRF ID 4005274) Bug fix: Ethernet interface did not come up after a power down reset if Ethernet operation mode was forced (i. Tellabs 8100 Manager support for enhanced ping.9 Version 2.3) • • • Bug fix: Receiving of an Ethernet message destined to certain (rare) multicasts addresses in Router or BRouter mode hung Tellabs 8110 CTU-R. logging. 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. traceroute. Restrictions • This version should NOT be downloaded to Tellabs 8110 STE-10M.2 or higher MartisDXX Manager support for this unit is available in Release 12 Service Pack 1 or higher.Tellabs 8110 CTU-R HDSL.4 Enhancements and Fixed Bugs (compared with version 2.e. packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher. Tellabs 8110 CTE-R/208 SHDSL and Tellabs 8110 STE-10M SHDSL NTUs: SBZ670 Unit Software 28. Tellabs 8110 CTU-R (SBZ671) software version must be 1. .

Tellabs 8100 manager support for enhanced ping. packet filtering and reset/factory settings restore functionalities are available in Release 12A Service Pack 1 or higher. logging. 10004_22 © 2008 Tellabs.10 Version 2. Restrictions • This version should NOT be downloaded to Tellabs 8110 STE-10M.12 Version 2. Tellabs 8110 CTU-R (SBZ671) software version must be 1.8) • • • • • • • • • 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.Tellabs 8110 CTU-R HDSL.2 or higher MartisDXX Manager support for this unit is available in Release 12 Service Pack 1 or higher. Tellabs 8110 CTE-R/208 SHDSL and Tellabs 8110 STE-10M SHDSL NTUs: SBZ670 Unit Software 28. traceroute. and LMI functionalities are available in Release 13 Service Pack 1 or higher. Tellabs 8110 CTE-R SHDSL. MartisDXX Manager support for NAT. Bugs • No known bugs. 28.0 or higher.2 This is an internal test version. 28.11 Version 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 317 .1 This is an internal test version.3 Enhancements and Fixed Bugs (compared with version 1.

0 This is an internal test version. Tellabs 8110 CTE-R/208 SHDSL and Tellabs 8110 STE-10M SHDSL NTUs: SBZ670 Unit Software 28. (CRF ID 4004760) Enhancement: Opaque VLAN (IEEE 802. 28.1 or higher MartisDXX Manager support for this unit is available in Release 12 Service Pack 1 or higher.8 Enhancements and Fixed Bugs (compared with version 1.7 This is an internal test version.5) • • 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.6 This is an internal test version. Bugs • No known bugs.14 Version 1.13 Version 2. 28. 28. Tellabs 8110 CTE-R SHDSL.15 Version 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 318 10004_22 © 2008 Tellabs. Restrictions • This version should NOT be downloaded to Tellabs 8110 STE-10M.0 or higher.Tellabs 8110 CTU-R HDSL.16 Version 1. Tellabs 8110 CTU-R (SBZ671) software version must be 1.1Q and Cisco ISL) frame bridging support (CRF ID 4004761) Dependencies • • • Tellabs 8110 CTU-R (CTU399) hardware version must be 1. .

Restrictions • This version should NOT be downloaded to Tellabs 8110 STE-10M.4) • Tellabs 8110 CTU-R sends HDLC flags (bit pattern "01111110") to WAN (DSL) interface when there are no data packets to be sent. Tellabs 8110 CTE-R/208 SHDSL and Tellabs 8110 STE-10M SHDSL NTUs: SBZ670 Unit Software 28. (CRF ID 4004648) Dependencies • • • Tellabs 8110 CTU-R (CTU399) hardware version must be 1.0 or higher.17 Version 1. Tellabs 8110 CTU-R (SBZ671) software version must be 1.18 Version 1. Restrictions • This version should NOT be downloaded to Tellabs 8110 STE-10M. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 319 .0 or higher.5 Enhancements and Fixed Bugs (compared with version 1. Tellabs 8110 CTE-R SHDSL. 28. Bugs • No known bugs.4 This is an unofficial version and it should not be used once the next official version is available.Tellabs 8110 CTU-R HDSL. Dependencies • • • Tellabs 8110 CTU-R (CTU399) hardware version must be 1. Bugs • No known bugs. 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.1 or higher MartisDXX Manager support for this unit is available in Release 12 Service Pack 1 or higher. 10004_22 © 2008 Tellabs.

0 or higher to support HCE-2M-1P and HCE-2M-2P modules.0). 2.110/CRC feature (EECRC) is not fully compatible with Tellabs 8110 HTU-2M (USW SBZ389 V1. Tellabs 8110 CTU-R (SBZ670) software version must be 1.5 or higher to support HCQ module. The version 2. STU-576.)... and with Tellabs 8110 STU-320. Bugs • No known bugs. Enhancement.1 Version 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 320 10004_22 © 2008 Tellabs. QMH (QMZ540) software version must be 10. STU-1088-2W and STU-2304 (USW SBZ387 V 1.2 or earlier).0 Enhancements and Fixed Bugs • Support for AMIC flash.5 or higher. and therefore bi-directional EECRC in Tellabs 8110 CTU-R misinterprets path to be constantly UNAVAILABLE. 29. MartisDXX Manager support for this unit is available in Release 12 Service Pack 1 or higher. (CR ID 200025830) Dependencies • • • • • • Tellabs 8110 CTU-R (CTU399) hardware version must be 1.0 can be downloaded to units having the version 2. Restrictions • The End-to-End V.y of SBZ671 (where y=1. These units support only unidirectional EECRC. Tellabs 8100 manager support for time dependent DTE capacity control is available in Release 14 or higher. .0 or higher. 3. GMH (GMZ283) software version must be 10.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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies 321 . STU-1088-2W and STU-2304 (USW SBZ387 V 1. GMH (GMZ283) software version must be 10. Bugs • No known bugs.110/CRC feature (EECRC) is not fully compatible with Tellabs 8110 HTU-2M (USW SBZ389 V1.0 or higher.4 Enhancements and Fixed Bugs • Possibility to change the DTE capacity of CTU-R depending on the time of day. QMH (QMZ540) software version must be 10. These units support only unidirectional EECRC.0 or higher to support HCE-2M-1P and HCE-2M-2P modules.5 or higher to support HCQ module.2 or earlier).2 Version 1.Tellabs 8110 CTU-R HDSL NTU: SBZ671 Unit Software 29. Tellabs 8110 CTU-R (SBZ670) software version must be 1. STU-576. and with Tellabs 8110 STU-320. Restrictions • The End-to-End V. Enhancement. MartisDXX Manager support for this unit is available in Release 12 Service Pack 1 or higher. (CR ID 200015077) Dependencies • • • • • • Tellabs 8110 CTU-R (CTU399) hardware version must be 1.0).5 or higher. 10004_22 © 2008 Tellabs. and therefore bi-directional EECRC in Tellabs 8110 CTU-R misinterprets path to be constantly UNAVAILABLE. Tellabs 8100 manager support for time dependent DTE capacity control is available in Release 14 or higher.

These units support only unidirectional EECRC. Tellabs 8110 CTU-R (SBZ670) software version must be 1. Bugs • No known bugs. Restrictions • The End-to-End V. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 322 10004_22 © 2008 Tellabs.3 Enhancements and Fixed Bugs • • Bug fix for quota problem. (CRF ID 4005048) G. (CRF ID 4005267) Dependencies • • • • • Tellabs 8110 CTU-R (CTU399) hardware version must be 1. Under some rare circumstances.Tellabs 8110 CTU-R HDSL NTU: SBZ671 Unit Software 29. STU-1088-2W and STU-2304 (USW SBZ387 V 1.0).3 Version 1. MartisDXX Manager support for this unit is available in Release 12 Service Pack 1 or higher. STU-576. . Tellabs 8110 CTU-R could reset itself due to lack of transport layer quotas.5 or higher.110/CRC feature (EECRC) is not fully compatible with Tellabs 8110 HTU-2M (USW SBZ389 V1.0 or higher. GMH (GMZ283) software version must be 10.826 15 minutes trigger alarms were generated ten seconds too early.2 or earlier). QMH (QMZ540) software version must be 10. and with Tellabs 8110 STU-320. and therefore bi-directional EECRC in Tellabs 8110 CTU-R misinterprets path to be constantly UNAVAILABLE.0 or higher to support HCE-2M-1P and HCE-2M-2P modules.5 or higher to support HCQ module.

0 or higher to support HCE-2M-1P and HCE-2M-2P modules. (CRF ID 4004667) Ability to reset router processor with Tellabs 8100 Manager. STU-1088-2W and STU-2304 (USW SBZ387 V 1.2 or earlier). GMH (GMZ283) software version must be 10. (CRF ID 4004897) Reserved new objects for router use. and therefore bi-directional EECRC in Tellabs 8110 CTU-R misinterprets path to be constantly UNAVAILABLE. Recovery function fixed. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 323 .5 or higher to support HCQ module. (CRF ID 4005048) G. These units support only unidirectional EECRC. QMH (QMZ540) software version must be 10.4 Version 1. Tellabs 8110 CTU-R (SBZ670) software version must be 1. Restrictions • The End-to-End V. STU-576. Tellabs 8110 CTU-R might reset itself due to lack of transport layer quotas.826 15 minutes trigger alarms are generated ten seconds too early.0 or higher. (CRF ID 4005267) 10004_22 © 2008 Tellabs.0). and with Tellabs 8110 STU-320. MartisDXX Manager support for this unit is available in Release 12 Service Pack 1 or higher.5 or higher.110/CRC feature (EECRC) is not fully compatible with Tellabs 8110 HTU-2M (USW SBZ389 V1.2 Enhancements and Fixed Bugs • • • Simultaneous modem parameter update with power failure (very unlikely to happen) might lead to corruption of setup data. (CRF ID 4004687) Dependencies • • • • • Tellabs 8110 CTU-R (CTU399) hardware version must be 1.Tellabs 8110 CTU-R HDSL NTU: SBZ671 Unit Software 29. Bugs • • Under some rare circumstances.

STU-1088-2W and STU-2304 (USW SBZ387 V 1.0 or higher to support HCE-2M-1P and HCE-2M-2P modules. Tellabs 8110 CTU-R might reset itself due to lack of transport layer quotas. These units support only unidirectional EECRC. MartisDXX Manager support for this unit is available in Release 12 Service Pack 1 or higher.826 15 minutes trigger alarms are generated ten seconds too early.2 or earlier). (CRF ID 4004897) Under some rare circumstances.0 or higher.5 or higher. GMH (GMZ283) software version must be 10.1 Dependencies • • • • • Tellabs 8110 CTU-R (CTU399) hardware version must be 1. (CRF ID 4005048) G. QMH (QMZ540) software version must be 10. (CRF ID 4005267) Tellabs® 8100 Managed Access System Unit Software Version Dependencies 324 10004_22 © 2008 Tellabs.Tellabs 8110 CTU-R HDSL NTU: SBZ671 Unit Software 29. . STU-576. Bugs • • • Simultaneous modem parameter update with power failure (very unlikely to happen) might lead to corruption of setup data. Restrictions • The End-to-End V. and with Tellabs 8110 STU-320.110/CRC feature (EECRC) is not fully compatible with Tellabs 8110 HTU-2M (USW SBZ389 V1. and therefore bi-directional EECRC in Tellabs 8110 CTU-R misinterprets path to be constantly UNAVAILABLE. Tellabs 8110 CTU-R (SBZ670) software version must be 1.5 or higher to support HCQ module.0).5 Version 1.

0 Enhancements and Fixed Bugs • Support for AMIC Flash.703 (CTU397) units. QMH (QMZ540) software version must be 10. MartisDXX Manager support for this unit is available in Release 11 Service Pack 2 or higher.2 or earlier). 30. and therefore bidirectional EECRC in CTU-S misinterprets path to be constantly UNAVAILABLE. Enhancement. Restrictions • The End-to-End V.703.110/CRC feature (EECRC) is not fully compatible with HTU-2M (USW SBZ389 V1. and with STU-320. CTU-S hardware version must be 2.. 2.21 (CTU396) and CTU-S G.5 or higher to support HCQ-2M module.). STU-576. Tellabs 8100 manager support for time dependent DTE capacity control is available in Release 14 or higher.1 Version 3. GMH (GMZ283) software version must be 10.35 (CTU395).0 or higher to support HCE-2M-1P and HCE-2M-2P modules.0 or higher if point-to-point feature is to be utilized.x of SBZ605 (where x=0. • • Bugs • No known bugs.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..0 can be downloaded to CTU-S units having the version 3. STU-1088-2W and STU-2304 (USW SBZ387 V 1. The version 3.0). Time dependent DTE rate control is not available for CTU-S G. 1. (CR ID 200025496) Dependencies • • • • • CTU-S hardware version must be 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 325 . These units support only unidirectional EECRC. 10004_22 © 2008 Tellabs. CTU-S X.0 or higher.

0).703. STU-1088-2W and STU-2304 (USW SBZ387 V 1. Enhancement. MartisDXX Manager support for this unit is available in Release 11 Service Pack 2 or higher.0 or higher.0 or higher to support HCE-2M-1P and HCE-2M-2P modules. (CR ID 200005461) Dependencies • • • • • CTU-S hardware version must be 1. and with STU-320. STU-576. GMH (GMZ283) software version must be 10. and therefore bidirectional EECRC in CTU-S misinterprets path to be constantly UNAVAILABLE. Now this bug is fixed.2 Version 2. As a result.Tellabs 8110 CTU-S HDSL NTU: SBZ605 Unit Software 30. Tellabs 8100 manager support for time dependent DTE capacity control is available in Release 14 or higher.110/CRC feature (EECRC) is not fully compatible with HTU-2M (USW SBZ389 V1.826 performance event' alarms too early. CTU-S hardware version must be 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 326 10004_22 © 2008 Tellabs.0 Enhancements and Fixed Bugs • • • Point-to-point feature for CTU-S.0 or higher if point-to-point feature is to be utilized. Time dependent DTE rate control is not available for CTU-S G. . (CR ID 200013025) Possibility to change the DTE capacity depending on the time of day. Restrictions • The End-to-End V. Tellabs 8100 Network Manager read wrong counter values from CTU (current counter values were not moved to history table before reading took place).5 or higher to support HCQ-2M module. • • Bugs • No known bugs. (CR ID 200013815) CTU-S sent 'G. These units support only unidirectional EECRC.2 or earlier). Enhancement. QMH (QMZ540) software version must be 10.

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

and with STU-320.1. Bugs • Short line breaks may cause loss of management communication channel. .35 and X.0). Restrictions • The End-to-End V.110/CRC feature (EECRC) is not fully compatible with HTU-2M (USW SBZ389 V1. (CRF ID 4004248) The DTE interface code error counter is inoperative.2 or earlier).21 DTE-types only (not G.826 performance event'-alarms too early. QMH (QMZ540) software version must be 10. STU-1088-2W and STU-2304 (USW SBZ387 V 1. This problem concerns G.0 or higher to support HCE-2M-1P and HCE-2M-2P modules. This problem concerns V.703 DTEtype only. and therefore bidirectional EECRC in CTU-S misinterprets path to be constantly UNAVAILABLE. GMH (GMZ283) software version must be 10. Dependencies • • • • CTU-S hardware version must be 1.703). until the line is dropped or the HDLC channel is forced to the all ones signal for a couple of seconds. MartisDXX Manager support for this unit is available in Release 11 Service Pack 2 or higher.0 This version was used only in Field Validation Tests. (CRF ID 4004247) Reset of the Rx buffer slip counter clears the Tx counter and reset of Tx clears the Rx counter. the test interface terminal responses INVOKE ERROR for active faults query. STU-576. (CRF ID 4004350) CTU-S sends 'G.5 or higher to support HCQ-2M module.Tellabs 8110 CTU-S HDSL NTU: SBZ605 Unit Software 30.0 or 1. During the malfunction. These units support only unidirectional EECRC.4 Version 1. (CR ID 200005461) • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 328 10004_22 © 2008 Tellabs.

0 or higher to support 3 Mbit/s line modes.0 or higher. ESU (ESU783 and ESM784) hardware version must be 1. Tellabs 8100 manager support for 3 Mbit/s line modes is available in Release 14 Service Pack 6 or higher.). or 4.19. Tellabs 8110 STE-10M (DPZ794) DSP software version must be 1.0 or higher to support extra backups for other units in the node.1 Enhancements and Fixed Bugs • Support for 3 Mbit/s line modes added. 31.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.5 or higher to support over 8M cross-connection ports. GMX (GMZ544) software version must be 3.0 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 329 . Dependencies • • • • • • • • • • • • • Tellabs 8110 STE-10M (STE790) hardware version must be 1.0 or higher. XCG (SMZ538) software version must be 2. The version 1.1 Version 1. SCO interface module version must be 3.0 or higher. OMH (OMZ675) software version must be 2. 10004_22 © 2008 Tellabs. Tellabs 8100 manager support for this unit is available in Release 14 Service Pack 3 or higher.1 can be downloaded to STE-10M units having the version 1.1 or higher to support over 8M crossconnection ports. ESU (EMZ642) software version must be 1.1 or higher...0 or higher. SXU-A/B (SXZ282) software version must be 10.10 or higher. Tellabs 8110 STE-10M (SBZ670) router software version must be 4. 1.y of SBZ792 (where y=0. Restrictions • No restrictions. OMH (OMH771) hardware version must be 1. 2.5 or higher to support over 8M crossconnection ports. and 3.

GMX (GMZ544) software version must be 3.0 or higher.0 or higher.9 or higher.5 or higher to support over 8M cross-connection ports. OMH (OMH771) hardware version must be 1. Bugs • No known bugs.Tellabs 8110 STE-10M NTU: SBZ792 Unit Software Bugs • No known bugs. ESU (ESU783 and ESM784) hardware version must be 1.0 or higher. XCG (SMZ538) software version must be 2. or 4. Dependencies • • • • • • • • • • • • Tellabs 8110 STE-10M (STE790) hardware version must be 1. 31. Tellabs 8100 manager support for this unit is available in Release 14 Service Pack 3 or higher.1 or higher to support over 8M crossconnection ports.5 or higher to support over 8M crossconnection ports.2 Version 1. SXU-A/B (SXZ282) software version must be 10.0 or higher to support extra backups for other units in the node.0 or higher. Restrictions • No restrictions.0 Enhancements and Fixed Bugs • This is the first official version.19. OMH (OMZ675) software version must be 2. Tellabs 8110 STE-10M (DPZ794) DSP software version must be 1.0 or higher to support 4-pair modes. ESU (EMZ642) software version must be 1. and 3. Tellabs 8110 STE-10M (SBZ670) router software version must be 4. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 330 10004_22 © 2008 Tellabs. .0 or higher. SCO interface module version must be 3.0 or higher.

2. etc. The kernel package resides in the ROM memory. Note: If the application package is disabled. The SBM 2048M software is structured into two packages: kernel and application.…).0 can be downloaded to SBM 2048s with the revision 5.1A SP7. Does not support VCM type interface parameter menus. only the services provided by the kernel package are available. LAN Bridge parameters have to be set with MartisDXX Manager. 32.y of SMZ414 (where y = 0.1 Version 5. Restrictions • • • LAN Bridge parameters are located in its own flash memory. 2. The version 5.1. and the basic system services: command interpreter. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 331 . 1. 10004_22 © 2008 Tellabs. when replacing a LAN Module. Bugs • No known bugs. flash memory programming support. downloading support. 1. communications services for the SC. Does not support CAS at 2048 kbit/s<bitrate<8448 kbit/s. The version 4. Requires HW version 6.y of SMZ414 (where y = 0. The application package is downloadable and resides in the flash memory.6 can be downloaded to SBM 2048s with the revision 4. Therefore.0 Dependencies • • MartisDXX Manager support for LAN Module and HSSI interface modules are available in Release 10.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 kernel package contains the operating system.…).

BTE-576. The control channel fails if MartisDXX Manager sends too low HDLC link timeout parameter values. Bugs • • Unnecessary TX-Clock fault when using BTE-4096 module. Does not support all bit rates between 2M-8M (IF3. Restrictions • • Does not support VCM type interface parameter menus. Restrictions • • • • • • Does not support BTE-320.0. 114/115 contra and 114/115 invert timing mode do not work at rates over 2048 kbibt/s. Displaying wrong G.3 Version 4.821 statistics DM information.6). .Tellabs 8120 Mini Node M: SMZ414 Unit Software 32. Bugs • • • The current practise in production after 1999 is set to year value 100 which is not possible with the current unit software. BTE-1088-2W and BTE-2304 modules. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 332 10004_22 © 2008 Tellabs.823 updated standard (1993). Does not support X and E bits.2 Version 4.6 Dependencies • Requires HW version 6. Does not support CAS at 2048 kbit/s<bitrate<8448 kbit/s.. Does not support DEG/EXC BER alarms. Frequency difference alarm does not meet G.4 Dependencies • No dependencies. An alarm will be generated when using x-connected timeslot for HDLC. 32.

BTE-1088-2W and BTE-2304 modules.. An alarm will be generated when using x-connected timeslot for HDLC. Does not support DEG/EXC BER alarms.5 Version 4. Does not support BTE-2048-2W module. Frequency difference alarm does not meet G.823 updated standard (1993). Does not support X and E bits. Does not support AIS detection in unframed mode. Frequency difference alarm does not meet G. Does not support BTE-2048. BTE-576..6). BTE-576. 32. Does not support RAI-Xcon mode. Does not support all bit rates between 2M-8M (IF3. An alarm will be generated when using x-connected timeslot for HDLC.4 Version 4. Bugs • • Unnecessary TX-Clock fault when using BTE-4096 module.Tellabs 8120 Mini Node M: SMZ414 Unit Software 32. Does not support X and E bits. Does not support FSW-RAI usage: X-sync.6). 114/115 contra and 114/115 invert timing mode do not work at rates over 2048 kbibt/s. Does not support 105 off delay parameters. BTE-1088-2W and BTE-2304 modules.3 Dependencies • No dependencies. Does not support DEG/EXC BER alarms.1 Dependencies • No dependencies. V35-G704S and X21-G704S modules.823 updated standard (1993). 10004_22 © 2008 Tellabs. Restrictions • • • • • • • • Does not support BTE-320. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 333 . Restrictions • • • • • • • • • • Does not support BTE-320. Does not support all bit rates between 2M-8M (IF3.

Does not support DEG/EXC BER alarms. High speed correction at 4Mbit < bit rate < 8Mbit. Does not support BTE-384 module wetting current strapping info (in the new version BTE384 strapping possibility). Restrictions • • • • • • • Does not support BTE-320.Tellabs 8120 Mini Node M: SMZ414 Unit Software • 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. LCD menu test pattern selections (IF3…IF6) when M > 6 are not correct. Does not support BTE-2048-2W module.54 loop activation control.6 Version 4. Frequency difference alarm does not meet G. G703-75. When GMH interface has loop to interface and unframed mode and no x-connections. G703-8M modules. G703-120.. Does not support all bit rates between 2M-8M (IF3. .6). BTE-1088-2W and BTE-2304 modules. BTE-576. An alarm will be generated when using x-connected timeslot for HDLC. Does not support 114 invert timing mode. Does not support fan fault supervision. V. 114/115 contra and 114/115 invert timing mode do not work at rates over 2048 kbibt/s. Does not support X and E bits. Does not support 105 off delay parameters.0 Dependencies • No dependencies.35-G704B nor X. Does not support V.21-G704 modules (lower modules). 32. Bugs • • • • • • • Unnecessary TX-Clock fault when using BTE-4096 module. 106 delay corrections. BTE-4096. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 334 10004_22 © 2008 Tellabs. AIS (not RX signal) shall be sent. Does not support AIS detection in unframed mode. Does not support BTE-1088. Does not support RAI-Xcon mode.823 updated standard (1993).

54 loop activation control 106 delay corrections 10004_22 © 2008 Tellabs. Continuous unit report sending (if sending enabled) when faults are masked. LCD menu test pattern selections (IF3…IF6) when M > 6 are not correct. Does not support BTE-2048. Does not support 114 invert timing mode.35-V. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 335 . Does not support 105 off delay parameters. V35-G704S and X21-G704S modules. Does not support BTE-2048-2W module. Does not support cluster usage. Bugs • • • • • • • • • • • • • • Unnecessary TX-Clock fault when using BTE-4096 module. G703-120. Illegal parameter choices in the LCD menu when handling the loop parameters of G703-64-M module. Does not support BTE-1088. Does not support FSW-RAI usage: X-sync. AIS (not RX signal) shall be sent. Does not support bit rate 33 x 64 kbit/s (lower modules). 114/115 contra and 114/115 invert timing mode do not work at rates over 2048 kbibt/s. Does not support power supply identification info. High speed correction at 4Mbit < bit rate < 8Mbit V.24 module (upper modules). BTE-4096. Does not support RAI-Xcon mode. Does not support fan fault supervision. XB capacity allocation error in the case of X. 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 AIS detection in unframed mode.Tellabs 8120 Mini Node M: SMZ414 Unit Software • • • • • • Does not support V. MartisDXX Manager Disaster Recovery cannot be used.21 (upper modules) and C/I transfer. Bit rates below 8 kbit/s do not work. Power-off indication from DTE does not work (upper modules). G703-8M modules. Does not support BTE-384 module wetting current strapping info (in the new version BTE384 strapping possibility). When GMH interface has loop to interface and unframed mode and no x-connections. G703-75.

BTE-4096. Does not support BTE-2048-2W module. 114/115 contra and 114/115 invert timing mode do not work at rates over 2048 kbit/s. Restrictions • • • • • • • • • • Does not support BTE-320. Does not support new type of flash memory.823 updated standard (1993). AIS (not RX signal) shall be sent. Does not support RAI-Xcon mode. High speed correction at 4Mbit < bit rate < 8Mbit Tellabs® 8100 Managed Access System Unit Software Version Dependencies 336 10004_22 © 2008 Tellabs. Does not support X and E bits. Does not support BTE-1088. G703-120. When GMH interface has loop to interface and unframed mode and no x-connections. Frequency difference alarm does not meet G. BTE-1088-2W and BTE-2304 modules.Tellabs 8120 Mini Node M: SMZ414 Unit Software 32. Does not support fan fault supervision.6). Does not support AIS detection in unframed mode. Does not support DEG/EXC BER alarms. Does not support all bit rates between 2M-8M (IF3. Does not support FSW-RAI usage: X-sync. LCD menu test pattern selections (IF3…IF6) when M > 6 are not correct.7 Version 3. . Does not support 105 off delay parameters.3 Dependencies • No dependencies. Does not support 114 invert timing mode. An alarm will be generated when using x-connected timeslot for HDLC. Bugs • • • • • Unnecessary TX-Clock fault when using BTE-4096 module. 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 BTE-384 module wetting current strapping info (in the new version BTE384 strapping possibility). G703-75. BTE-576. G703-8M modules. V35-G704S and X21-G704S modules. Does not support BTE-2048.

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 power supply identification info. BTE-1088-2W and BTE-2304 modules. Does not support V.24 module (upper modules).8 Version 3. G703-8M modules.54 loop activation control 106 delay corrections 32. An alarm will be generated when using x-connected timeslot for HDLC.6). BTE-576. Frequency difference alarm does not meet G. 10004_22 © 2008 Tellabs. Does not support 114 invert timing mode. Does not support BTE-2048.V.35 . Does not support fan fault supervision. Does not support new type of flash memory.35-G704B nor X.21-G704 modules (lower modules). G703-120. Does not support BTE-2048-2W module. Does not support 105 off delay parameters. Does not support RAI-Xcon mode. Does not support AIS detection in unframed mode. Does not support FSW-RAI usage: X-sync. Does not support BTE-384 module wetting current strapping info (in the new version BTE384 strapping possibility). BTE-4096.823 updated standard (1993).2 Dependencies • No dependencies. Does not support X and E bits. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 337 .Tellabs 8120 Mini Node M: SMZ414 Unit Software • • V. Does not support BTE-1088. G703-75. Does not support all bit rates between 2M-8M (IF3. Does not support DEG/EXC BER alarms. Restrictions • • • • • • • • • • • • • • Does not support BTE-320. V35-G704S and X21-G704S modules.. Does not support bit rate 33 x 64 kbit/s (lower modules). Does not support V.

35-V. When GMH interface has loop to interface and unframed mode and no x-connections.9 Version 3.24 module (upper modules).1 Dependencies • No dependencies. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 338 10004_22 © 2008 Tellabs. Does not support cluster usage. MartisDXX Manager Disaster Recovery cannot be used. . BTE-576. Does not support DEG/EXC BER alarms. AIS (not RX signal) shall be sent. Does not support V. High speed correction at 4Mbit < bit rate < 8Mbit V. Does not support all bit rates between 2M-8M (IF3. Does not support bit rate 33 x 64 kbit/s (lower modules). Does not support power supply identification info. Restrictions • • • • • • • • • • • • Does not support BTE-320.21-G704 modules (lower modules). LCD menu test pattern selections (IF3…IF6) when M > 6 are not correct. Does not support V. Power-off indication from DTE does not work (upper modules).35-G704B nor X.Tellabs 8120 Mini Node M: SMZ414 Unit Software Bugs • • • • • • • • • • • • • • Unnecessary TX-Clock fault when using BTE-4096 module. 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.21 (upper modules) and C/I transfer. An alarm will be generated when using x-connected timeslot for HDLC. Frequency difference alarm does not meet G.6). Does not support new type of flash memory. XB capacity allocation error in the case of X.823 updated standard (1993). Bit rates below 8 kbit/s do not work. Does not support X and E bits. Does not support BTE-2048..54 loop activation control 106 delay corrections 32. 114/115 contra and 114/115 invert timing mode do not work at rates over 2048 kbibt/s. V35-G704S and X21-G704S modules. BTE-1088-2W and BTE-2304 modules.

Does not support 114 invert timing mode. Does not support fan fault supervision. Does not support cluster usage. LCD menu test pattern selections (IF3…IF6) when M > 6 are not correct. Illegal parameter choices in the LCD menu when handling the loop parameters of G703-64-M module. Does not support RAI-Xcon mode. Does not support BTE-1088. MartisDXX Manager Disaster Recovery cannot be used. Bugs • • • • • • • • • • • • • • • • • Unnecessary TX-Clock fault when using BTE-4096 module. Does not support AIS detection in unframed mode. Does not support signalling when the bit rate is 18…31 x 64 kbit/s. AIS (not RX signal) shall be sent. XB capacity allocation error in case of X. Bit rates below 8 kbit/s do not work. Continuous unit report sending (if sending enabled) when faults are masked. Does not support BTE-384 module wetting current strapping info (in the new version BTE384 strapping possibility). Copying the connections of a split trunk control port IF21 by using the front panel keys accesses the wrong node.54 loop activation control 106 delay corrections 10004_22 © 2008 Tellabs. High speed correction at 4Mbit < bit rate < 8Mbit V.21 (upper modules) and C/I transfer. 114/115 contra and 114/115 invert timing mode do not work at rates over 2048 kbibt/s.Tellabs 8120 Mini Node M: SMZ414 Unit Software • • Does not support FSW-RAI usage: X-sync. BTE-4096. 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 105 off delay parameters. G703-8M modules. Does not support BTE-2048-2W module. Power-off indication from DTE does not work (upper modules). G703-75. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 339 . G703-120. When GMH interface has loop to interface and unframed mode and no x-connections. Does not support ring synchronization.

HDLC link timeout over satellite.2 Version 2.1 Dependencies • No dependencies. Frequency difference alarm does not meet the G. 33. Bugs • No known bugs. TS0 invert and Rx monitor without CRC. BTE-1088-2W. Version 2. Restrictions • No restrictions.823 updated standard (1993). BTE-576.1 Version 2. Support for fast download (in Prom of 2. Does not support the DEG/EXC BER alarms.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.2 Dependencies • No dependencies. Support XC ASICs to “80186 bus mode” (all registers at even address). .0 or 2. Bugs • No alarm when neighbour makes a V.54 loop. Restrictions • • • • • • • • • Does not support the BTE-320. An alarm will be generated when using the x-connected timeslot for HDLC. Does not support the micro BTS.2 can be downloaded to Tellabs 8130 micro nodes with version 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 340 10004_22 © 2008 Tellabs. BTE-2304 modules.2).2 of SMZ533. 33.

IA activity missing and Rx buffer slip faults might shortly occur. Restrictions • VCM LAN module parameters are located in its own flash memory. When replacing a VCM unit including a VCM LAN module. 2. 1.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.. 2. SCP (SCZ281) software version can be any. GMX (GMZ544) software version can be any.1A or higher.. The version 10. MartisDXX Manager support for VCM LAN and HSSI interface modules are available in Release 10. but it does not support V5.y of VCZ285A (where y=0.y of VCZ285A (where y=0.). 10004_22 © 2008 Tellabs. VCM LAN module parameters have to be set with MartisDXX Manager.0 or higher. In such cases the alarms do not disturb the data stream..2 itself and its functionality is like with SXU-A. The release 2. SCU-H (SCZ545) software version must be 1.14 can be downloaded to VCM-A units having the version 2. VCM-A can be in the same node with SXU-V.6 or higher. 34.4 or higher.1 Version 10.. After a cross-connection has been deleted from a VCM interface. SCU (SCZ280) software version can be any.2 can be downloaded to VCM-A units having the version 10. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 341 .2 Dependencies • • • • • • • • • • VCM-A (base unit VCM222A / VCM223A) hardware version must be 4. SXU-A/B (SXZ282) software version must be 5. Bugs • • Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80. VCM-A does not support Cluster Node. XCG (SMZ538) software version can be any.). 1. 144 and 160 kbit/s.

(CRF 4002303) Problems with some data speeds ( 7104. (CRF 4002693) VCM X. After a cross-connection has been deleted from a VCM interface.0) circuit loop test resource does't fuction correctly if control channel is NONE. VCM bridge parameters have to be set with MartisDXX Manager.1A. (CRF 4002650) Bit rates over 32 x 64 kbit/s in VCM A cards can be changed even if the interface is locked. 7168 and 7232 kbit/s ) of the VCM X. IA activity missing and Rx buffer slip faults might shortly occur. Restrictions • • Requires 4.21.2 Version 10.1 Dependencies • MartisDXX Manager support for VCM Bridge and HSSI interface modules are available in Release 10. (CRF 4003715) Tellabs® 8100 Managed Access System Unit Software Version Dependencies 342 10004_22 © 2008 Tellabs. 144 and 160 kbit/s. . VCM-5T-A (hw4. VCM Bridge parameters are located in its own flash memory so.21 does not function with X21 S+B timing and S_inv. (CRF 4002470) Problem to reset loop from the VCM unit when there have been clocking problems.VCM-A UNIT: VCZ285A Unit Software 34.0 hardware. when replacing a VCM unit including a VCM bridge module.0/usw 10. In such cases the alarms do not disturb the data stream. Bugs • • • • • • • Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80.

8M. USW version 2. After a cross-connection has been deleted from a VCM interface. IA activity missing and Rx buffer slip faults might shortly occur.0 hardware.14 does not fully support V.3 Version 10. IF does not activate if 113/115 clock is not connected.14 does not support X and E bits. In such cases the alarms do not disturb the data stream. 34. IA activity missing and Rx buffer slip faults might shortly occur. 144 and 160 kbit/s.VCM-A UNIT: VCZ285A Unit Software 34. In such cases the alarms do not disturb the data stream.24 DTE LL and RL loops. 10004_22 © 2008 Tellabs. Bugs • • Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80.14 Dependencies • No dependencies. 144 and 160 kbit/s. Restrictions • • • • USW version 2.4 Version 2. After a cross-connection has been deleted from a VCM interface. USW version 2.x hardware. USW version 2. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80.0 Dependencies • No dependencies.14 does not support all bit rates between 2M . Restrictions • Requires 4. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 343 .14 requires 3. Bugs • • • • 114/115 contradir and 114/115 invert timing modes do not work over 2048 kbit/s bit rates.

105: Fixed off. See the restrictions of version 2.6 Version 2. No support for V24-PMP tail eater module.5 Version 2.14. 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. 144 and 160 kbit/s. After a cross-connection has been deleted from a VCM interface. 105: Fixed off Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80. Bugs • • • Wrong X-bus capacity when Control channel: none.12 Dependencies • No dependencies Restrictions • • • No support for 105 off delay parameter. 144 and 160 kbit/s. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80. 34. . In such cases the alarms do not disturb the data stream. Wrong X-bus capacity when Control channel: none. Restrictions • See the restrictions of version 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 344 10004_22 © 2008 Tellabs.VCM-A UNIT: VCZ285A Unit Software 34.13. IA activity missing and Rx buffer slip faults might shortly occur.13 Dependencies • No dependencies. Bugs • • • • AIS from PCM inverts data towards X-Bus to all zeros in 6703-PDA.

Restrictions • See the restrictions of version 2. In such cases the alarms do not disturb the data stream.54. 144 and 160 kbit/s.7 Version 2.11 Dependencies • No dependencies. 144 and 160 kbit/s. No support for V24-PMP tail eater module. In such cases the alarms do not disturb the data stream. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80. Restrictions • • • No ASYNC test support for CTS.10 Dependencies • No dependencies. Bugs • • • • • • • High speed problems between 4Mbit/s and 8Mbit/s. Wrong X-bus capacity when Control channel: none.54 loop activation not according to spec. IA activity missing and Rx buffer slip faults might shortly occur. 105: Fixed off. 105: Fixed off. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80. After a cross-connection has been deleted from a VCM interface. 10004_22 © 2008 Tellabs. V. Bugs • • • Wrong X-bus capacity when Control channel: none. See the restrictions of version 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 345 . No 114 inverted timing mode. After a cross-connection has been deleted from a VCM interface. IA activity missing and Rx buffer slip faults might shortly occur. You cannot bring 106 delay back below 255.12.VCM-A UNIT: VCZ285A Unit Software 34. V.8 Version 2.11. 34.

XB capacity allocation error in case of X. 105: Fixed off. 144 and 160 kbit/s.21 module and C/I transfer. After a cross-connection has been deleted from a VCM interface. 105: Fixed off.703-PDA (GPL245) support. Restrictions • • No G.VCM-A UNIT: VCZ285A Unit Software 34.8 Dependencies • No dependencies. Wrong X-bus capacity when Control channel: none. In such cases the alarms do not disturb the data stream. See the restrictions of version 2. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80. 34. In such cases the alarms do not disturb the data stream. Bugs • • • • • • Bit rates below 8 kbit do not work.9 Dependencies • No dependencies.10 Version 2. Restrictions • See the restrictions of version 2. .10. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 346 10004_22 © 2008 Tellabs. After a cross-connection has been deleted from a VCM interface.9 Version 2. Bit rates from 4 Mbit/s to 8448 kbits/s does not work. Bugs • • • Wrong X-bus capacity when Control channel: none.9. IA activity missing and Rx buffer slip faults might shortly occur. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80. IA activity missing and Rx buffer slip faults might shortly occur. 144 and 160 kbit/s.

VCM-A UNIT: VCZ285A Unit Software 34.11 Version 2.0. Restrictions • • No PMP cluster support. Bugs • • • No known bugs. In such cases the alarms do not disturb the data stream. 34. 10004_22 © 2008 Tellabs. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80.7. In such cases the alarms do not disturb the data stream.8. See the restrictions of version 2. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 347 .1). Restrictions • • VCM 222A/VCM 223A version must be 3. IA activity missing and Rx buffer slip faults might shortly occur.12 Version 2. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80.7 Dependencies • No dependencies. After a cross-connection has been deleted from a VCM interface. See the restrictions of version 2. IA activity missing and Rx buffer slip faults might shortly occur.6 Dependencies • No support for Rev. After a cross-connection has been deleted from a VCM interface.3 IFMOD ASIC ( Hw-version 3. 144 and 160 kbit/s. Bugs • • • Asic timing error (octet pulse). 144 and 160 kbit/s.

Restrictions • • No PMP locking object.14 Version 2. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80. 34.5. Bugs • • • Buffer slip alarms in case of X30 framer.6. . IA activity missing and Rx buffer slip faults might shortly occur. In such cases the alarms do not disturb the data stream. IA activity missing and Rx buffer slip faults might shortly occur. In such cases the alarms do not disturb the data stream. After a cross-connection has been deleted from a VCM interface.5 Dependencies • No dependencies. See the restrictions of version 2.VCM-A UNIT: VCZ285A Unit Software 34. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80. After a cross-connection has been deleted from a VCM interface. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 348 10004_22 © 2008 Tellabs.13 Version 2. 144 and 160 kbit/s. 144 and 160 kbit/s.4 Dependencies • No dependencies. Bugs • • • In case of 113/115 clocking with VDS242 module 113 clock can be erroneous. Restrictions • See the restrictions of version 2.

In such cases the alarms do not disturb the data stream. Some faults have zero GPT (General Problem Type). In case the X30 framer & no control channel connection capacity is too high. See the restrictions of version 2. Restrictions • • • • 8 kbit/s is not available.3. In case the N*64 kbit/s & V13 & CRC ON connection capacity is too high. The Alarm bit on V110 frame is inverted.16 Version 2. See the restrictions of version 2. Bit rates up to 8448 kbit/s are not supported. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 349 . Restrictions • • Pmp server functions is not supported.VCM-A UNIT: VCZ285A Unit Software 34. 10004_22 © 2008 Tellabs. SXU IA testing is not supported. IA activity missing and Rx buffer slip faults might shortly occur. Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80. Bugs • • • • • Buffer sizes at >64 kbit/s are not optimal.0 Dependencies • No dependencies.15 Version 2. Bugs • • • • • • Some buffer sizes should be greater in case of codirectional clocking. If Interface Module is none.4.3 Dependencies • No dependencies. In case the X30 framer & no control channel connection capacity is too high. The Alarm bit on V110 frame is inverted. 144 and 160 kbit/s. After a cross-connection has been deleted from a VCM interface. 34. unit informs Code-error fault.

VCM-A UNIT: VCZ285A Unit Software • • Tx buffer alignment and Rx buffer alignment alarms occur in bit rates 80. In such cases the alarms do not disturb the data stream. 144 and 160 kbit/s. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 350 10004_22 © 2008 Tellabs. After a cross-connection has been deleted from a VCM interface. . IA activity missing and Rx buffer slip faults might shortly occur.

The version 3.5 Enhancements and Fixed Bugs • • Trunk swap does not cause data errors. Restrictions • No restrictions. The interface unit needs this information to function correctly. 1.5 can be downloaded to XCG units having the version 3.1 Version 3.).1 or higher.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. 10004_22 © 2008 Tellabs. Bugs • HDLC link timeout value 11 is impossible. (CR ID 200032287) The test timeslot used internally for port IA testing has been changed depending on the port capacity.. Data errors would follow if this message is not sent by XCG..2 or higher. MartisDXX Manager support for pilot bit feature of XCG unit is available in Release 12 Service Pack 1 or higher. (CR ID 200031040) • • Dependencies • • • XCG (base unit XCG525) hardware version must be 2. 2. (CR ID 200035773) The background sending of the cross-connected timeslots (Free Time Slot sending) operates correctly for ports over 8448kbit/s. XCG interface modules G703-75-4CH (base unit GDH521) and G703-120-4CH (base unit GDH522) hardware version must be 1. 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. 35. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 351 .x of SMZ538 (where x=0.

The actual selection logic in the unit has been working without any problems and remains unchanged. MartisDXX Manager support for pilot bit feature of XCG unit is available in Release 12 Service Pack 1 or higher.2 or higher. This will make the unit much more reliable in case of any communication problem. (CR ID 200012801) Module type set operation is now possible also when the XCG unit is not in inventory. .1 or higher. (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. The interface unit gets the QL from neighbor node by the NNM mechanism. (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.4 Enhancements and Fixed Bugs • • The XB port capacity is supported to up to 192x64 kbit/s. (CR ID 200012800) ‘X-Connect RAM fault’ now disappears automatically when the error condition has ended. (CR ID 200011615) Neighbor node monitoring (NNM) polling status problems cannot cause wrong clock selection anymore. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 352 10004_22 © 2008 Tellabs. (CR ID 200012802) The Separate Command Bit TS0/B1 operation is fixed. (CR ID 200012805) • • • • • • • Dependencies • • • XCG (base unit XCG525) hardware version must be 2. This is required for the ESU unit.2 Version 3. Restrictions • No restrictions.XCG Unit: SMZ538 Unit Software 35. XCG interface modules G703-75-4CH (base unit GDH521) and G703-120-4CH (base unit GDH522) hardware version must be 1. This change concerns only the reporting of QL values. (CR ID 200011615) The 1+1 Protection Mode dependent fault status is set correctly after reset. The bug could have had an effect on the initialization of the control channels during node installation. The XCG unit is able to detect a message that has a consistency problem in the internal data structure. Normally the master clock QL value of a clock source is obtained from an interface unit by polling it inside the node. (CR ID 200011656) The check of incoming message integrity is improved. In the case of NNM link communication problem the QL value is set to 7 (DNU) to prevent wrong clock source selection. The processing of the invalid message is prevented. Also the EXT clock QL is set to value 7 (DNU) when there is an active problem in the external clock source.

The interface unit needs this information to function correctly. (CRF ID 4004049) Memory management enhanced. (CRF ID 4004904) Dependencies • • • XCG (base unit XCG525) hardware version must be 2. (CRF ID 4004718) AIS fault is restrained with equipment loop when pilot bit is set. the IA test timeslot overlaps with payload data and data errors will follow. (CRF ID 4004979) Fallback List Warning alarm is removed. (CRF ID 4004406) G. (CR ID 200011656) 10004_22 © 2008 Tellabs.2 or higher.1 or higher. (CR ID 200031044) The inventory add and delete operations for XCG unit are impossible.4 will otherwise operate normally. between DXX server and XCG. (CR ID 200031040) HDLC link timeout value 11 is impossible. (CRF ID 4005001) Clock QL state is forced to DNU if NNM is down. • • • • 35. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. MartisDXX Manager support for pilot bit feature of XCG unit is available in Release 12 Service Pack 1 or higher. under heavy loading condition is fixed. (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. An installed (upgraded) XCG with ESW version 3.821 statistics for 1+1 protected trunk fixed.3 Version 3. (CR ID 200032287) If a port bigger than 140*64 kbit/s is used. (CRF ID 4004992) Line loop bug with pilot bit fixed. (CRF ID 4005098) Clock status DNU is sent via NNM if unit can not get locked to node clock.3 Enhancements and Fixed Bugs • • • • • • • • • The problem with a failing asynchronous link. XCG interface modules G703-75-4CH (base unit GDH521) and G703-120-4CH (base unit GDH522) hardware version must be 1. (CRF ID 4004658) The problem with available time in 1+1 trunk performance data always remaining 100% fixed. The problem concerns only the swapped trunks that may belong to any interface in the node. Data errors will follow if this message is not sent by XCG. Restrictions • The XB port capacity of up to 192x64 kbit/s is not supported. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 353 .XCG Unit: SMZ538 Unit Software Bugs • There may be data errors after trunk swap for 2 minutes or shorter time.

(CR ID 200011615) The 1+1 Protection Mode dependent fault status may be wrong after reset if the 1+1 Protection Mode was activated. The processing of the invalid message is not prevented. (CRF ID 4004049) Occurrence of a random Missing Unit fault fixed. This does not effect on the information given by the NMS Fault Management System (FMS). (CR ID 200012800) ‘X-Connect RAM fault‘ does not disappear automatically when the error condition has ended. MartisDXX Manager support for pilot bit feature of XCG unit is available in Release 12 Service Pack 1 or higher. 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. This may have effect on the initialization of the control channels during node installation. . (CR ID 200012801) Module type set operation is not possible when the XCG unit is not in inventory. (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.1 or higher.4 Version 3. This version should not be used once the next official version is available.2 or higher. (CR ID 200012803) The interface 1+1 Protection Mode activation or deactivation may cause occasional and unintentional reset of the fault history buffer. (CR ID 200011615) The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. • • • • • • 35. (CR ID 200012802) The Separate Command Bit TS0/B1 does not operate correctly.XCG Unit: SMZ538 Unit Software Bugs • • • The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 354 10004_22 © 2008 Tellabs. (CRF ID 4004837) • Dependencies • • • XCG (base unit XCG525) hardware version must be 2. (CR ID 200012805) HDLC link timeout value 11 is impossible. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown.1. XCG interface modules G703-75-4CH (base unit GDH521) and G703-120-4CH (base unit GDH522) hardware version must be 1.2 This is an unofficial version based on version 3.

XCG Unit: SMZ538 Unit Software Restrictions • The XB port capacity of up to 192x64 kbit/s is not supported.1 Enhancements and Fixed Bugs • • Pilot bit feature in own interfaces 1 . Restrictions • The XB port capacity of up to 192x64 kbit/s is not supported. Bugs • • • • The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. (CR ID 200012800) ‘X-Connect RAM fault‘ does not disappear automatically when the error condition has ended. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied.4 of XCG unit. XCG interface modules G703-75-4CH (base unit GDH521) and G703-120-4CH (base unit GDH522) hardware version must be 1.1 or higher. (CR ID 200011656) Bugs • • • The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. (CRF ID 4003830) Dependencies • • • XCG (base unit XCG525) hardware version must be 2. (CR ID 200012801) The Separate Command Bit TS0/B1 does not operate correctly. (CRF ID 4004062) Disabling of downloaded software is not any more possible. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 355 . • • 35. (CR ID 200012800) ‘X-Connect RAM fault‘ does not disappear automatically when the error condition has ended. (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. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. The processing of the invalid message is not prevented.2 or higher. MartisDXX Manager support for pilot bit feature of XCG unit is available in Release 12 Service Pack 1 or higher. The processing of the invalid message is not prevented. (CR ID 200012803) 10004_22 © 2008 Tellabs. (CR ID 200012803) The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value.5 Version 3. 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 200012801) The Separate Command Bit TS0/B1 does not operate correctly.

(CR ID 200012801) The Separate Command Bit TS0/B1 does not operate correctly.4 of XCG unit is available in Release 11 Service Pack 1 or higher. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied.6 Version 3. 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 200012803) The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. (CR ID 200012800) ‘X-Connect RAM fault‘ does not disappear automatically when the error condition has ended.0 Enhancements and Fixed Bugs • HDLC channels in own interfaces 3 . (CR ID 200012805) • 35. Restrictions • • The XB port capacity of up to 192x64 kbit/s is not supported. (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. The processing of the invalid message is not prevented. XCG interface modules G703-75-4CH (base unit GDH521) and G703-120-4CH (base unit GDH522) hardware version must be 1.1 or higher.2 or higher. (CR ID 200011656) No pilot bit feature. (CR ID 200012805) • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 356 10004_22 © 2008 Tellabs. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. MartisDXX Manager support for HDLC channels in own interfaces 3 .XCG Unit: SMZ538 Unit Software • The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value.4 of XCG unit. Bugs • • • • The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. (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. . Dependencies • • • XCG (base unit XCG525) hardware version must be 2.

(CR ID 200011656) No pilot bit feature.3 Enhancements and Fixed Bugs • 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.7 Version 2. There can be incorrect IN USE information of timeslots in interfaces 3 and 4 when 1+1 protection is on. Bugs • • • • The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. 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 200012803) The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. (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. The G. No HDLC channels in interfaces 3 – 4. Restrictions • • • The XB port capacity of up to 192x64 kbit/s is not supported. • • • • • • 10004_22 © 2008 Tellabs. 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.XCG Unit: SMZ538 Unit Software 35. Slow neighbour alarm when a cable is removed from interface 1.821 unavailable state alarm is missing. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 357 . (CR ID 200012801) The Separate Command Bit TS0/B1 does not operate correctly. (CR ID 200012805) Master clock hold over does not work. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. The HDLC channel fails if NMS sends too low HDLC LINK TIMEOUT parameter values.

XCG Unit: SMZ538 Unit Software 35. (CR ID 200012803) The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value.821 unavailable state alarm is missing. (CR ID 200011656) No pilot bit feature. The G. (CR ID 200012800) ‘X-Connect RAM fault‘ does not disappear automatically when the error condition has ended. (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. (CRF ID 4004837) Dependencies • MartisDXX Manager support for XCG unit is available in Release 9 Service Pack 1 or higher. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. No HDLC channels in interfaces 3 – 4. 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. There can be incorrect IN USE information of timeslots in interfaces 3 and 4 when 1+1 protection is on. (CR ID 200012801) The Separate Command Bit TS0/B1 does not operate correctly. Restrictions • • • The XB port capacity of up to 192x64 kbit/s is not supported. • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 358 10004_22 © 2008 Tellabs.1. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. Master clock source through STM-1 interface of GMU shows wrong QL status. The processing of the invalid message is not prevented. Slow neighbour alarm when a cable is removed from interface 1. (CR ID 200012805) Master clock hold over does not work. Bugs • • • • The XCG unit is not able to detect a message that has a consistency problem in the internal data structure.2 This is a non-production version based on version 2. The HDLC channel fails if NMS sends too low HDLC LINK TIMEOUT parameter values.8 Version 2. .

No HDLC channels in interfaces 3 – 4. Support for Micro BTS.9 Version 2. Slow neighbour alarm when a cable is removed from interface 1. (CR ID 200012800) ‘X-Connect RAM fault‘ does not disappear automatically when the error condition has ended. (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. Difference alarm. . Tellabs® 8100 Managed Access System Unit Software Version Dependencies 359 • • • • • 10004_22 © 2008 Tellabs. New detection criteria in the Freq. Restrictions • • • The XB port capacity of up to 192x64 kbit/s is not supported. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. The HDLC channel fails if NMS sends too low HDLC LINK TIMEOUT parameter values. The processing of the invalid message is not prevented. (CR ID 200012805) Master clock hold over does not work. (CR ID 200012801) The Separate Command Bit TS0/B1 does not operate correctly.1 Enhancements and Fixed Bugs • • • • • • • • • Support for GMU and GMU-M units.XCG Unit: SMZ538 Unit Software 35. (CR ID 200011656) No pilot bit feature. New feature: TS0 invert and Rx monitor without CRC. (CR ID 200012803) The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. New BER alarms (Exc/Deg). This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. The new HDLC/X-bus overlap alarm. Voltage bus alarm filtering for PAU-5T. There can be incorrect IN USE information of timeslots in interfaces 3 and 4 when 1+1 protection is on. Dependencies • MartisDXX Manager support for XCG unit is available in Release 9 Service Pack 1 or higher. Bugs • • • • The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. HDLC link over satellite feature. Node synchronisation source change alarms.

(CR ID 200012803) The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. The processing of the invalid message is not prevented.10 Version 2.XCG Unit: SMZ538 Unit Software • • It is possible that there occur faulty Missing unit alarms. (CR ID 200011656) No pilot bit feature. 35. (CR ID 200012800) ‘X-Connect RAM fault‘ does not disappear automatically when the error condition has ended. Old detection criteria in the Freq. Bugs • • • • The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. No feature: TS0 invert and Rx monitor without CRC. No support for GMU and GMU-M units. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. . The old HDLC/X-bus overlap alarm. (CR ID 200012801) The Separate Command Bit TS0/B1 does not operate correctly. No HDLC channels in interfaces 3 – 4. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. Dependencies • MartisDXX Manager support for XCG unit is available in Release 9 Service Pack 1 or higher. Difference alarm.0 Enhancements and Fixed Bugs • Extended backup support. No voltage bus alarm filtering for PAU-5T. The G. No support for Micro BTS. No node synchronisation source change alarms. No new BER alarms (Exc/Deg). Restrictions • • • • • • • • • • • • The XB port capacity of up to 192x64 kbit/s is not supported.821 unavailable state alarm is missing. No HDLC link over satellite feature. (CR ID 200012805) • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 360 10004_22 © 2008 Tellabs. (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.

No support for Micro BTS. Dependencies • MartisDXX Manager support for XCG unit is available in Release 9 Service Pack 1 or higher. The G. Restrictions • • • • • • • • • • • • • The XB port capacity of up to 192x64 kbit/s is not supported. 10004_22 © 2008 Tellabs. It is possible that there occur faulty Missing unit alarms.11 Version 1. No support for GMU and GMU-M units.821 unavailable state alarm is missing. No voltage bus alarm filtering for PAU-5T.XCG Unit: SMZ538 Unit Software • • • • • • Master clock hold over does not work. Difference alarm. No extended backup support.0 Enhancements and Fixed Bugs • First version. The old HDLC/X-bus overlap alarm. No HDLC channels in interfaces 3 – 4. No node synchronisation source change alarms. 35. No feature: TS0 invert and Rx monitor without CRC. Slow neighbour alarm when a cable is removed from interface 1. No new BER alarms (Exc/Deg). no enhancements. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 361 . (CR ID 200011656) No pilot bit feature. Old detection criteria in the Freq. This is a requirement for ESU unit but only if bigger than 8M port capacity is applied. No HDLC link over satellite feature. There can be incorrect IN USE information of timeslots in interfaces 3 and 4 when 1+1 protection is on. The HDLC channel fails if NMS sends too low HDLC LINK TIMEOUT parameter values.

(CR ID 200012800) ‘X-Connect RAM fault‘ does not disappear automatically when the error condition has ended. (CR ID 200012803) The Neighbor node monitoring (NNM) polling problems caused by the control channel link do not affect properly the used QL value. The G. The processing of the invalid message is not prevented. (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. It is possible that there occur faulty missing unit alarms. Incorrect HW type code of Mini Node (SMZ430) in compatibility check: system part/application part. It is not always correctly set to 7 (DNU) in order to prevent wrong clock source selection when the actual QL is unknown. • • • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 362 10004_22 © 2008 Tellabs. (CR ID 200012805) Master clock hold over does not work. .821 unavailable state alarm is missing. Slow neighbour alarm when a cable is removed from interface 1. There can be incorrect IN USE information of timeslots in interfaces 3 and 4 when 1+1 protection is on. (CR ID 200012801) The Separate Command Bit TS0/B1 does not operate correctly.XCG Unit: SMZ538 Unit Software Bugs • • • • The XCG unit is not able to detect a message that has a consistency problem in the internal data structure. The HDLC channel fails if NMS sends too low HDLC LINK TIMEOUT parameter values.

SCU-H (SCZ545) software version must be 1. CCU (SCZ286) software version must be 2. Basic and Cluster Nodes.0 or 3. XCG (SMZ538) software version must be 2.1 or higher.3 Enhancements and Fixed Bugs • Changing Functional testing for AIU1:1 and AIU1:4. 10004_22 © 2008 Tellabs.4 or higher. 1.1 Version 1.y of ABZ531 (where y=0.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.1 AIU Unit: ABZ531 Unit Software The software ABZ531 is used on the DXX processor module (ABU) of AIU unit in Midi.1 or higher. MartisDXX Manager support for the AIU is available in Release 9.3 can be downloaded to AIU units having the version 1. GMX (GMZ544) software version must be 3. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 363 .0A-3 or higher.1. SXU-A/B (SXZ282) software version must be 6.11 or higher. SCP (SCZ281) software version must be 3. SXU-C (SXZ289) software version must be 2. 2.9 or higher. CXU-M (SXZ288) software version must be 10..). 36.5 or higher. (CRF ID 4004812) Dependencies • • • • • • • • • • • ABU257 hardware version must be 1.4 or higher.0 or higher. The software ACZ7001 is used on the ATM processor module (ACP514) of AIU. 36. The version 1. See the corresponding release note for more information.. SCU (SCZ280) software version must be 8.10 or higher.0 or higher.

CCU (SCZ286) software version must be 2. CXU-M (SXZ288) software version must be 10. MartisDXX Manager support for the AIU is available in Release 9. Restrictions • Before updating ABZ531 software from the earlier version make sure that the ATM Processor Module (ACP) software ACZ7001 version is 1. SXU-C (SXZ289) software version must be 2.2 or higher. Bugs • No known bugs.0 or higher. Bugs • No known bugs. SCU (SCZ280) software version must be 8.5 or higher. No software support for production testing. SCP (SCZ281) software version must be 3.9 or higher.0A-3 or higher. . 36. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 364 10004_22 © 2008 Tellabs.Unit Software Version Dependencies in Discontinued Products Restrictions • • Before updating ABZ531 software from the earlier version make sure that the ATM Processor Module (ACP) software ACZ7001 version is 1.2 Dependencies • • • • • • • • • • • ABU257 hardware version must be 1. SXU-A/B (SXZ282) software version must be 6. GMX (GMZ544) software version must be 3. XCG (SMZ538) software version must be 2.4 or higher.2 Version 1.0 or higher. SCU-H (SCZ545) software version must be 1.4 or higher.2 or higher.1.11 or higher.1 or higher.1 or higher.10 or higher.

3 Version 1.1 or higher.1 Dependencies • • • • • • • • • • • ABU257 hardware version must be 1.10 or higher. SCP (SCZ281) software version must be 3. SXU-C (SXZ289) software version must be 2. MartisDXX Manager support for the AIU is available in Release 9.0 or higher.0A-3 or higher. 10004_22 © 2008 Tellabs. CXU-M (SXZ288) software version must be 10.Unit Software Version Dependencies in Discontinued Products 36. CCU (SCZ286) software version must be 2. Locking and unlocking >2Mbit/s virtual trunk interfaces in A111 node often fails. SCU (SCZ280) software version must be 8.4 or higher. XCG (SMZ538) software version must be 2.11 or higher. Bugs • No known bugs.1. SCU-H (SCZ545) software version must be 1. SXU-A/B (SXZ282) software version must be 6.1 or higher. GMX (GMZ544) software version must be 3.0 or higher.4 or higher.2 or higher.5 or higher. Restrictions • • Before updating ABZ531 software from the earlier version make sure that the ATM Processor Module (ACP) software ACZ7001 version is 1.9 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 365 .

4 or higher. CCU (SCZ286) software version must be 2.Unit Software Version Dependencies in Discontinued Products 36. • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 366 10004_22 © 2008 Tellabs.4 Version 1. MartisDXX Manager support for the AIU is available in Release 9. SXU-C (SXZ289) software version must be 2. XCG (SMZ538) software version must be 2.1 or higher.9 or higher.1.11 or higher.1 or higher.0 or higher. SCU-H (SCZ545) software version must be 1. These alarms should always be ignored. 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).4 or higher.0 Dependencies • • • • • • • • • • • ABU257 hardware version must be 1. Unnecessary ‘16/20 MHz clocks not locked’ alarms may exist in the alarm reports of AIU. or a node inventory operation (add/remove AIU. SCP (SCZ281) software version must be 3. 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.5 or higher. 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.10 or higher.0A-3 or higher.0 or higher.1 or earlier. GMX (GMZ544) software version must be 3. SXU-A/B (SXZ282) software version must be 6. CXU-M (SXZ288) software version must be 10. create/delete inventory) is performed very soon after inserting a unit into the node. SCU (SCZ280) software version must be 8. .

Unit Software Version Dependencies in Discontinued Products

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
Enhancements and Fixed Bugs

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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
367

Unit Software Version Dependencies in Discontinued Products

• • • • • • • • • • • •

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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
368

10004_22 © 2008 Tellabs.

Unit Software Version Dependencies in Discontinued Products

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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
369

Unit Software Version Dependencies in Discontinued Products

36.3.4 Version 1.2
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.

Bugs

Newly created ATM circuits do not always work. (CRF 4003503).

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
370

10004_22 © 2008 Tellabs.

Unit Software Version Dependencies in Discontinued Products

36.3.5 Version 1.1
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
• • • •

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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
371

Unit Software Version Dependencies in Discontinued Products

36.3.6 Version 1.0
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
• • • •

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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
372

10004_22 © 2008 Tellabs.

Unit Software Version Dependencies in Discontinued Products

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 CCO’s Overload and PBX Voltage alarms has been improved (1.104 and 1.106). Filtering of CCS’s 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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
373

Unit Software Version Dependencies in Discontinued Products

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. CCO’s 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. CCO’s 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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
374

10004_22 © 2008 Tellabs.

Unit Software Version Dependencies in Discontinued Products

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.

Tellabs® 8100 Managed Access System Unit Software Version Dependencies
375

SXU-C (SXZ289) software version must be 2.10 or higher.15 or higher. XCG (SMZ538) software version must be 2. Restrictions • No restrictions.0 or higher. SCP (SCZ281) software version must be 3. MartisDXX Manager support for this unit functionality is available in Release 12 or higher. Bugs • No known bugs.1 or higher. CXU-M (SXZ288) software version must be 10.1 or higher. SXU-V (SXZ630) software version must be 1.018 Dependencies • • • • • • • • • • • • • • ABP732 hardware version must be 1.0 or higher. SXU-A/B (SXZ282) software version must be 6. CCU (SCZ286) software version must be 2.0 or higher.1 or higher.2 Version 1.5.9 or higher. ABU257 (ABZ607) software version must be 1. GMX (GMZ544) software version must be 3. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 376 10004_22 © 2008 Tellabs.Unit Software Version Dependencies in Discontinued Products 36.5 or higher. . SCU (SCZ280) software version must be 8. SCU-H (SCZ545) software version must be 1. ACP735 (ACZ7004) software version must be 1.4 or higher.0 or higher.11 or higher.

SXU-C (SXZ289) software version must be 2. 36. Tellabs 8150 basic.). ACP735 (ACZ7004) software version must be 2.0 or higher. SXU-A/B (SXZ282) software version must be 6. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 377 . 2. ABP732 (ABP732) software version must be 1.11 or higher.10 or higher.0 can be downloaded to CEU units having the version 2.5 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. .0. The ACZ7004 software is used on the ATM processor module of CEU. SCP (SCZ281) software version must be 3.4 or higher. 10004_22 © 2008 Tellabs. Bugs • No known bugs. 1. XCG (SMZ538) software version must be 2. Enhancements and Fixed Bugs • CAS alignment corrected for cluster node.9 or higher.15 or higher. SCU-H (SCZ545) software version must be 1.6.1 or higher. MartisDXX Manager support for this unit functionality is available in Release 12A or higher.018 or higher.0 or higher. Tellabs 8160 A111 and Tellabs 8170 cluster nodes. The version 2.y of ABZ607 (where y=0.1 Version 2. CXU-M (SXZ288) software version must be 10. SCU (SCZ280) software version must be 8. See the corresponding release notes for more information. GMX (GMZ544) software version must be 3.1 This is a non-production version based on version 2. Dependencies • • • • • • • • • • • • • • ABU257 hardware version must be 2. CCU (SCZ286) software version must be 2.. Restrictions • No restrictions.6 CEU Unit: ABZ607 Unit Software The software ABZ607 is used on CEU unit (whose base unit is ABU257) in the Tellabs 8140 midi.1 or higher.0 or higher.Unit Software Version Dependencies in Discontinued Products 36..

SXU-C (SXZ289) software version must be 2. SCU (SCZ280) software version must be 8.15 or higher. . Bugs • No known bugs. GMX (GMZ544) software version must be 3.5 or higher. MartisDXX Manager support for this unit functionality is available in Release 12A or higher. SXU-V (SXZ630) software version must be 1. QOS and QOSTR errors’ GPT codes changed from 60 to 49.018 or higher. ABP732 (ABP732) software version must be 1.4 or higher.1 or higher. Restrictions • No restrictions.6. CXU-M (SXZ288) software version must be 10. 2) of the synchronization buses of the node. XCG (SMZ538) software version must be 2.9 or higher.1 or higher. G.0 or higher. SCU-H (SCZ545) software version must be 1.0 or higher. Dependencies • • • • • • • • • • • • • • ABU257 hardware version must be 2. Recovered clock from STM-1 interface can be delivered to either (SYB 1. SCP (SCZ281) software version must be 3.10 or higher.0 Enhancements and Fixed Bugs • • • • In band management channels in all (32pcs) 2M framed connections.2 Version 2. ACP735 (ACZ7004) software version must be 2.1 or higher. CCU (SCZ286) software version must be 2.826 Limit Event added (GPT 91).Unit Software Version Dependencies in Discontinued Products 36. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 378 10004_22 © 2008 Tellabs. SXU-A/B (SXZ282) software version must be 6.11 or higher.0 or higher.

10004_22 © 2008 Tellabs. Synchronization buses of the node are not supported. CXU-M (SXZ288) software version must be 10. Bugs • No known bugs. ABP732 (ABP732) software version must be 1. ACP735 (ACZ7004) software version must be 1.10 or higher. SCP (SCZ281) software version must be 3. XCG (SMZ538) software version must be 2. SXU-V (SXZ630) software version must be 1.0 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 379 .1 or higher. SCU (SCZ280) software version must be 8. CCU (SCZ286) software version must be 2. GMX (GMZ544) software version must be 3.1 or higher.4 or higher. SCU-H (SCZ545) software version must be 1. SXU-A/B (SXZ282) software version must be 6.6.15 or higher.0 or higher. SXU-C (SXZ289) software version must be 2. MartisDXX Manager support for this unit functionality is available in Release 12 or higher. Restrictions • • DXX control-channels are not supported.1 or higher.0 Dependencies • • • • • • • • • • • • • • ABU257 hardware version must be 2.0 or higher.3 Version 1.9 or higher.5 or higher.Unit Software Version Dependencies in Discontinued Products 36.11 or higher.0 or higher.

0 or higher.1 This is a non-production version based on version 2. ABU257 (ABZ607) software version must be 2.7 CEU Unit: ACZ7004 Unit Software The software ACZ7004 is used on CEU unit (whose base unit is ACP735) in the Tellabs 8140 midi. SCP (SCZ281) software version must be 3. ABP732 (ABP732) software version must be 1. MartisDXX Manager support for this unit functionality is available in Release 12A or higher.). The ABZ607 software is used on the DXX processor module of CEU.1 Version 2.Unit Software Version Dependencies in Discontinued Products 36.7. SCU-H (SCZ545) software version must be 1. 36. CXU-M (SXZ288) software version must be 10.1 can be downloaded to CEU units having the version 1. CCU (SCZ286) software version must be 2.1 or higher. See the corresponding release notes for more information. SXU-C (SXZ289) software version must be 2. .5 or higher.0.4 or higher.y of ACP735 (where y=0.1 or higher.018 or higher. SCU (SCZ280) software version must be 8.0 or higher. (CRF ID 4005184) Dependencies • • • • • • • • • • • • • • ACP735 hardware version must be 1. GMX (GMZ544) software version must be 3. Compatibility with other vendors’ circuit emulation units is not guaranteed.. The version 2. 2.15 or higher.9 or higher.0) • Deleting a logical port may cause bit errors to another logical port..0 or higher. Tellabs 8160 A111 and Tellabs 8170 cluster nodes. SXU-V (SXZ630) software version must be 1. Restrictions • • CEU logical port performance (AAL1 level) counters are not correct in some cases. 1. XCG (SMZ538) software version must be 2.11 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 380 10004_22 © 2008 Tellabs.10 or higher. Enhancements and Fixed Bugs (compared with version 2. SXU-A/B (SXZ282) software version must be 6. Tellabs 8150 basic.1 or higher.

added G. XCG (SMZ538) software version must be 2. Bugs • Deleting a logical port may cause bit errors to another logical port 10004_22 © 2008 Tellabs. SXU-A/B (SXZ282) software version must be 6. ABP732 (ABP732) software version must be 1. Dependencies • • • • • • • • • • • • • • ACP735 hardware version must be 1. SXU-V (SXZ630) software version must be 1.1 or higher.9 or higher.2 Version 2.0 or higher.11 or higher.0 Enhancements and Fixed Bugs • • • • In band management channels in all (32pcs) 2M framed connections.1 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 381 . SCP (SCZ281) software version must be 3.10 or higher. SXU-C (SXZ289) software version must be 2. MartisDXX Manager support for this unit functionality is available in Release 12A or higher.4 or higher. Compatibility with other vendors’ circuit emulation units is not guaranteed.7. SCU (SCZ280) software version must be 8. CXU-M (SXZ288) software version must be 10. CCU (SCZ286) software version must be 2. Restrictions • • CEU logical port performance (AAL1 level) counters are not correct in some cases.1 or higher. QOS and QOSTR errors’ GPT codes changed from 60 to 49. 2) of the synchronization buses of the node.0 or higher. SCU-H (SCZ545) software version must be 1.15 or higher.018 or higher.826 Limit Event (GPT 91).Unit Software Version Dependencies in Discontinued Products 36.0 or higher.5 or higher. GMX (GMZ544) software version must be 3. Recovered clock from STM-1 interface can be delivered to either (SYB 1. ABU257 (ABZ607) software version must be 2.

In band management channels in all (32pcs) 2M framed connections is not supported. CXU-M (SXZ288) software version must be 10. SCU (SCZ280) software version must be 8. MartisDXX Manager support for this unit functionality is available in Release 12 or higher.1 or higher.9 or higher.0 Dependencies • • • • • • • • • • • • • • ACP735 hardware version must be 1. Bugs • QOS and QOSTR errors’ have a wrong GPT code. Clock recovery from STM-1 interface is not supported.1 or higher. XCG (SMZ538) software version must be 2.Unit Software Version Dependencies in Discontinued Products 36. CCU (SCZ286) software version must be 2. SXU-V (SXZ630) software version must be 1.7.0 or higher. .0 or higher. SXU-C (SXZ289) software version must be 2.0 or higher.10 or higher. Compatibility with other vendors’ circuit emulation units is not guaranteed. Restrictions • • • • CEU logical port performance (AAL1 level) counters are not correct in some cases.0 or higher.11 or higher. GMX (GMZ544) software version must be 3. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 382 10004_22 © 2008 Tellabs. SCP (SCZ281) software version must be 3.3 Version 1.1 or higher.15 or higher. SCU-H (SCZ545) software version must be 1. ABP732 (ABP732) software version must be 1. ABU257 (ABZ607) software version must be 1.5 or higher. SXU-A/B (SXZ282) software version must be 6.4 or higher.

See restrictions below.Unit Software Version Dependencies in Discontinued Products 36. USW version 10. Restrictions • When used with MartisDXX Manager release 10.1.0A-2 (OS2) and 10. it is recommended that switching to a clear channel be done on detecting 2100 Hz. a CLC should be added to a CCG only when the state of the CCG is Installed or In USE. In order to be properly configured.2. 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. For reliable clear channel operation. any CLCs should be deleted from the CCG prior to raising the state of the CCG. 36. Restrictions • No restrictions. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 383 .0 or 10.8. Additionally. SXU hardware version 5. 36.6 Dependencies (for High Speed Modem Operation) • • • EPS441 hardware with versions 2. • 10004_22 © 2008 Tellabs. 36. Note: USW version 10.1 restriction concerning clear channel operation at 2400 baud or less.9 EPS-5T and EPS-10T Units: UBZ441 Unit Software The software UBZ441 is used on EPS-5T and EPS-10T units. and the optional 2100 Hz with phase reversal not be used. if the state of a CCG is lowered to Planned.7 Dependencies • MartisDXX Manager support for this unit is available in Release 9.1 Version 1.1A (NT).9.1 Version 3. Bugs • No known bugs.8 ECS Unit: UBZ439 Unit Software The software UBZ439 is used on ECS units.0.0 and above.2 fixed a 10. MartisDXX Manager support for this unit is available in Release 10.

0 and above. This lock up situation can be released by disconnecting and again connecting the channel by NMS. Additionally. . is not capable of assigning specific CcgId & CmcId. the channel will stop operation. if the state of a CCG is lowered to Planned.0A-2 (OS2) and 10. 36.5 Dependencies (for High Speed Modem Operation) • • • EPS441 hardware with versions 2. Restrictions • When used with MartisDXX Manager release 10. When issuing S-Commands from the Unit Debugger for Clear Channel operation. MartisDXX Manager support for this unit is available in Release 10. Alternative way to release the lock up is to make a reset to the whole EPS unit. Clear channel fax operation at any speed is not affected. See bugs below. This problem can be avoided if all the EPS Channels are utilised.1.2 Version 3. SXU hardware version 5. and Activated on a different EPS Channel using the same CcgId & CmcId. 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. then deleted. MartisDXX Manager operation. 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.0 or 10. avoid duplicate CcgId & CmcId on separate Channels which inhibits Activation and switching to a clear channel. any CLCs should be deleted from the CCG prior to raising the state of the CCG.9. See restrictions below. which inhibits Activation and switching to a Clear Channel. This duplication is possible when an EPS Channel is Activated. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 384 10004_22 © 2008 Tellabs.1. however. For reliable clear channel operation. • • • • Bugs • EPS Clear Channel memory is capable of retaining duplicate CcgId & CmcId in separate Configuration Channels.1A (NT). and the optional 2100 Hz with phase reversal not be used.Unit Software Version Dependencies in Discontinued Products Bugs • EPS 8 kb/s compressed channel may lock up after about 6000 fax transmissions. it is recommended that switching to a clear channel be done on detecting 2100 Hz. USW version 10. version 10.1. 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.

5 Dependencies (for High Speed Modem Operation) • • • EPS441 hardware with versions less than 2.2.9. Additionally. USW version 10. See restrictions below. and the optional 2100 Hz with phase reversal not be used. MartisDXX Manager support for this unit is available in Release 10. SXU hardware version 5. Restrictions • When used with MartisDXX Manager release 10. it is recommended that switching to a Clear Channel be done on detecting 2100 Hz. version 10.1. and the optional 2100 Hz with phase reversal not be used. For reliable Clear Channel operation. USW version 10. a CLC should be added to a CCG only when the state of the CCG is Installed or In USE. In order to be properly configured.1A (NT).1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 385 .1.9. if the state of a CCG is lowered to Planned. 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. See restrictions below.0 or 10.6 Dependencies (for High Speed Modem Operation) • • • EPS441 hardware with versions less than 2. MartisDXX Manager support for this unit is available in Release 10.1 restriction concerning Clear Channel operation at 2400 baud or less.1A (NT).2 fixed a 10.0. • Bugs • No known bugs.Unit Software Version Dependencies in Discontinued Products 36. Note: USW version 10. SXU hardware version 5. • • • 10004_22 © 2008 Tellabs. 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.0. if the state of a CCG is lowered to Planned.4 Version 2. any CLCs should be deleted from the CCG prior to raising the state of the CCG. a CLC should be added to a CCG only when the state of the CCG is Installed or In USE. For reliable Clear Channel operation. 36. Additionally.0A-2 (OS2) and 10. Restrictions • When used with MartisDXX Manager release 10. any CLCs should be deleted from the CCG prior to raising the state of the CCG. it is recommended that switching to a Clear Channel be done on detecting 2100 Hz.0 or 10.1 Clear Channel Fax operation at any speed is not affected. In order to be properly configured.3 Version 2.0A-2 (OS2) and 10. 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.

. See bugs below. is not capable of assigning specific CcgId & CmcId. which inhibits Activation and switching to a Clear Channel. and the optional 2100 Hz with phase reversal not be used. SXU hardware version 5.0 supports fax operation not using Clear Channel with 8 kbit/s Transmission Rate.5 Version 2.1. version 10. if the state of a CCG is lowered to Planned. however.0 or 10. is not capable of assigning specific CcgId & CmcId. it is recommended that switching to a Clear Channel be done on detecting 2100 Hz. This problem can be avoided if all the EPS Channels are utilised. USW version 10. Fax operation without Clear Channel does not operate reliably with EPS 8kbit/s Transmission Rate. any CLCs should be deleted from the CCG prior to raising the state of the CCG. Bugs • EPS Clear Channel memory is capable of retaining duplicate CcgId & CmcId in separate Configuration Channels. See restrictions below. Restrictions • When used with MartisDXX Manager release 10. avoid duplicate CcgId & CmcId on separate Channels which inhibits Activation and switching to a Clear Channel. and Activated on a different EPS Channel using the same CcgId & CmcId.1.1 Clear Channel Fax operation at any speed is not affected. MartisDXX Manager operation.Unit Software Version Dependencies in Discontinued Products • When issuing S-Commands from the Unit Debugger for Clear Channel operation. For reliable Clear Channel operation. MartisDXX Manager support for this unit is available in Release 10. MartisDXX Manager operation. See bugs below.0A-2 (OS2) and 10.9. When issuing S-Commands from the Unit Debugger for Clear Channel operation. however. In order to be properly configured. 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.4 Dependencies (for High Speed Modem Operation) • • • EPS441 hardware with versions less than 2. Additionally. • • • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 386 10004_22 © 2008 Tellabs. This problem can be avoided if all the EPS Channels are utilised. 36.1A (NT). a CLC should be added to a CCG only when the state of the CCG is Installed or In USE. Fax operation through a Clear Channel with EPS 8kbit/s Transmission Rate must have EPS FAX set to OFF. then deleted. avoid duplicate CcgId & CmcId on separate Channels which inhibits Activation and switching to a Clear Channel. EPS load 2. 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. This duplication is possible when an EPS Channel is Activated.0.

The ESO-570 is a part of the ESO V5.4 is to be flashed to ESO-570 Release 01 (PCB Code 760057001).Unit Software Version Dependencies in Discontinued Products Bugs • • Sync loss during fax operation with EPS 8 kbit/s Transmission Rate with EPS FAX settings NSF DISABLED and NSF ENABLED.10 ESO Unit: ESZ8000 Boot Software ESZ8000 is the boot software which starts up the ESO-570 hw-module. 36. Restrictions • Must be used with ESZ8001 application software version 2. then deleted.0 Dependencies • The MartisDXX Manager support for these units is available in Release 8. Bugs • No known bugs. Restrictions • No restrictions. This duplication is possible when an EPS Channel is Activated.10.6 Version 2. 10004_22 © 2008 Tellabs.0.0 or higher. 36. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 387 .9. and Activated on a different EPS Channel using the same CcgId & CmcId. designed to enhance the capability of DXX Basic and DXX Cluster Nodes.1 Version 1.4 Dependencies • Version 1. 36. which inhibits Activation and switching to a Clear Channel. EPS Clear Channel memory is capable of retaining duplicate CcgId & CmcId in separate Configuration Channels. Bugs • No known bugs.1 Signaling Server Unit.

9 can be downloaded to ESO units having the version 2. HDLC-4CH (SCP211) (SCZ281) software version must be at least 3. MartisDXX Manager support for ESO is available in Release 10. SCU-H (SCZ545) software version must be 1. XCG (SMZ538) software version can be any version.. 7.). GMH (GMZ283) software version must be at least 6.y of ESZ8001 (where y= 5. SCU (SCZ280) software version must be at least 8. Bugs • There are no known bugs.1 Version 2.11.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.. 36. Restrictions • There are no known restrictions. Dependencies • • • • • • • • • • UBU processor module software (UBZ536) version must be at least 2.6 or higher.Unit Software Version Dependencies in Discontinued Products 36.9 Enhancements and Fixed Bugs • This version provides support for PSTN user ports. SXU-V (SXZ630) software version must be 1.0A.4.1 or higher.9.4.9.1. 6. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 388 10004_22 © 2008 Tellabs. ESZ boot (ESZ8000) software version must be at least 1. .4. SXU-A/B (SXZ282) software version must be at least 6. The version 2.

4. Restrictions • This version supports only ISDN user ports. ESZ boot (ESZ8000) software version must be at least 1.1 or higher. SXU-A/B (SXZ282) software version must be at least 6. (CR ID 200004985) The version also includes support for version 2 of the ETSI V5 Standard.Unit Software Version Dependencies in Discontinued Products 36.4. GMH (GMZ283) software version must be at least 6.8 This is a non-production version based on version 2. Dependencies • • • • • • • • • • UBU processor module software (UBZ536) version must be at least 2.6 or higher. SCU (SCZ280) software version must be at least 8. SCU-H (SCZ545) software version must be 1.9. PSTN user ports are not supported.11. XCG (SMZ538) software version can be any version. MartisDXX Manager support for ESO is available in Release 10.9. HDLC-4CH (SCP211) (SCZ281) software version must be at least 3.0A. Enhancements and Fixed Bugs This version contains the solution for the following CRs: • • • Abnormal drop of L1 between ESO and ISD-LT.1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 389 . SXU-V (SXZ630) software version must be 1. 10004_22 © 2008 Tellabs.2 Version 2.7. (CR ID 200005437) ESO is too sensitive to port configuration mismatch between AN and LE. Bugs • There are no known bugs.4.

2. Request restart returns misleading error code. 9. PSTN port unblocking problem in ESO when requested from LE side.6 or higher. V5. 6. SCU (SCZ280) software version must be at least 8. XCG (SMZ538) software version can be any version. Incorrect error code from USW causes incorrect error message displayed in Tellabs 8100 manager when requesting restart using unlocked variant.4. CCS-UNI signalling conversion for V5. 5. Checking not done for variant 0x14. Base register: bits controlling CS requires checking. 10. HDLC-4CH (SCP211) (SCZ281) software version must be at least 3. MartisDXX Manager support for ESO is available in Release 10.0A.9. changing. SXU-A/B (SXZ282) software version must be at least 6. PortType of Semi permanent leased line not allowed for ISDN ports. SCU-H (SCZ545) software version must be 1.Unit Software Version Dependencies in Discontinued Products 36. 7. Dependencies • • • • • • • • • • UBU processor module software (UBZ536) version must be at least 2.1. 4.11. 3. Spain country mapping.4. CurrentAnVariantID goes to FF even when interface Restarted.3 Version 2. Bugs • No known bugs. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 390 10004_22 © 2008 Tellabs.1 or higher. Restrictions • No restrictions. GMH (GMZ283) software version must be at least 6. SXU-V (SXZ630) software version must be 1. . ESZ boot (ESZ8000) software version must be at least 1.1 link recovery problem when using C-channel data service in multiple channel setting. 8.7 Enhancements and Fixed Bugs This version contains the solution for the following change requests: 1.4.1. Software corrupted when using large download block sizes.9.

11. SCU (SCZ280) software version must be at least 8. Dependencies • • • • • • • UBU processor module software (UBZ536) version must be at least 2. Restrictions • No restrictions.0A. SXU-A/B (SXZ282) software version must be at least 6. MartisDXX Manager support for ESO is available in Release 10.Unit Software Version Dependencies in Discontinued Products 36.4.9 Restrictions • No restrictions. ESZ boot (ESZ8000) software version must be at least 1.9 GMH (GMZ283) software version must be at least 6. SCU (SCZ280) software version must be at least 8. Dependencies • • • • • • • UBU processor module software (UBZ536) version must be at least 2.4.0A. 10004_22 © 2008 Tellabs.4.9. HDLC-4CH (SCP211) (SCZ281) software version must be at least 3.1. 36.4 Version 2.4 HDLC-4CH (SCP211) (SCZ281) software version must be at least 3.5 Version 2.6 Enhancements and Fixed Bugs • This version contains the solution for CRF ID 4002782.4.5 Enhancements and Fixed Bugs • This version contains the solution for CRF ID 4002375. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 391 . MartisDXX Manager support for ESO is available in Release 10. Bugs • No known bugs. ESZ boot (ESZ8000) software version must be at least 1.4.1 SXU-A/B (SXZ282) software version must be at least 6. Bugs • No known bugs.11. GMH (GMZ283) software version must be at least 6.9.

0. ESZ boot (ESZ8000) software version must be at least 1.0A.9 HDLC-4CH (SCP211) SCZ281 software version must be at least 3. Bugs • No known bugs. SCU (SCZ280) software version must be at least 8.0 Dependencies • • • UBU processor module software version must be at least 1.3.4 SXZ282 software version must be at least 6. Dependencies • • • • • • • UBU processor module software (UBZ536) version must be at least 2. Restrictions • No restrictions. MartisDXX Manager support for ESO is available in Release 10. . HDLC-4CH (SCP211) (SCZ281) software version must be at least 3. GMH (GMZ283) software version must be at least 6.7 Version 1.11. 36.4.9. SXU-A/B (SXZ282) software version must be at least 6.9. MartisDXX Manager support for ESO is available in Release 10. CAE is not supported.4.6 Version 2.Unit Software Version Dependencies in Discontinued Products 36. ESO in Tellabs 8150 basic node: SCU SXU GMH SCZ280 software version must be at least 8.9 GMZ283 software version must be at least 6.1.0A.2 Enhancements and Fixed Bugs • This version contains the implementation of the national PSTN-V5 mapping for the country of Chile. Bugs • No known bugs. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 392 10004_22 © 2008 Tellabs.11.1 Restrictions • • 14 ISDN circuits per link allowed in this version.

Unit Software Version Dependencies in Discontinued Products 36. ISD-LT (UBZ534) software version must be 1. Restrictions • No restrictions.1 or higher. MartisDXX Manager support for this unit is available in Release 10.0 or higher ESO570 processor module software (ESZ8001) version must be at least 2. 36.9 or higher.4 Enhancements and Fixed Bugs • Contains support for CustomSettings configuration attribute of NMS object 0x80 (ESO_OBJECT). The version 2. 10004_22 © 2008 Tellabs..5.4 can be downloaded to ESO units having the version 2.y of UBZ536 (where y=0.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.0 or higher.6 or higher. SCU (SCZ280) software version must be 8. If this attribute is set to 0x01.).12. GMH (GMZ283) software version must be 6. SCU-H (SCZ545) software version must be 1.1 Version 2. Dependencies • • • • • • • • • • • ESO (base unit UBU254) hardware version must be 2.4 or higher. SXU-V (SXZ630) software version must be 1.1 or higher. 1. the feature of ignoring the ISDN deactivation message from the Local Exchange will be turned on.9 or higher. Bugs • No known bugs. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 393 . SCP (SCZ281) software version must be 3.. SXU-A/B (SXZ282) software version must be 6. XCG (SMZ538) software version can be any.0A or higher. 2.

0 or higher. CCU (SCZ286) software version can be any version. SCU (SCZ280) software version must be 8. CXU-M (SXZ288) software version must be 10. SXU-C (SXZ289) software version must be 2. Restrictions • Only 3 HDLC links are recommended.13.Unit Software Version Dependencies in Discontinued Products 36.6 or higher. In any case.5 or higher.0 or higher.7 or higher.13 FBU Unit: FBZ612 Unit Software The software FBZ612 is used on FBU unit (whose base unit is FBU763) in the Tellabs 8140 midi.0 or higher.1 or higher. GMX (GMZ544) software version must be 3. The FBU Manager version should be C1. SXU-V (SXZ630) software version can be any version. SCP (SCZ281) software version must be 3.0 or higher. but the NMS should not use them all as a control channel.1 Version 1. 36. FBU framer module (FFM765) software version must be S35755.1 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 394 10004_22 © 2008 Tellabs.0 or higher. FBU processor module (SCM766) hardware version must be 2.01.1 or higher. XCG (SMZ538) software version must be 2. FBU interface module (FIM764) hardware version must be 1. SCU-H (SCZ545) software version must be 1. SXU-V (ESZ80003) software version can be any version. the NNM can be activated in all 16 interfaces.A0 (Nokia part USW). Tellabs 8150 basic.0 or higher.0 or later (Nokia manager). FBU framer module (FFM765) hardware version must be 1. SXU-A/B (SXZ282) software version must be 6. Tellabs 8160 A111 and Tellabs 8170 cluster nodes. MartisDXX Manager support for this unit is available in Release 12A SP1 or higher. . Bugs • No known bugs.8 or higher.2 Dependencies • • • • • • • • • • • • • • • • • • • FBU base unit (FBU763) hardware version must be 1. FBU power supply module (PDF767) hardware version must be 1.

2 or higher. CCU (SCZ286) software version must be 2. GMX (GMZ544) software version must be 3..0 or higher. Dependencies • • • • • • • • • • • • • • • FRU (base unit UBU259) hardware version must be 1. 1. SXU-V (SXZ630) software version must be 1.Unit Software Version Dependencies in Discontinued Products 36. SCU-H (SCZ545) software version must be 1.1 or higher GMH (GMZ283) software version must be 6.0 or higher. MartisDXX Manager support for overbooking of logical port is available in Release 11 Service Pack 2 or higher.2 or higher. FRE processor module software (FRZ535) version must be 1. SCU (SCZ280) software version must be 8. MartisDXX Manager support for setting the congestion threshold to a trunk type logical port is available in Release 11 Service Pack 3 or higher.4.11 or higher. SXU-A/B (SXZ282) software version must be 6.12 or higher.1 or higher. SCP (SCZ281) software version must be 3.10 or higher. 2.). emergency update 6 or higher. SXU-C (SXZ289) software version must be 2. The software FRZ535 is used on the FRE processor module of FRU.5 This is a non-production version based on version 1.y of UBZ534 (where y=0..1 Version 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 395 .4 can be downloaded to FRU units having the version 1. Restrictions • FRU initialization can take more than 10 minutes in a heavily configured unit. MartisDXX Manager support for setting the congestion threshold to a user type logical port is available in Release 9.14. CXU-M (SXZ288) software version must be 2. 10004_22 © 2008 Tellabs. Enhancements and Fixed Bugs (compared with version 1. Tellabs 8160 A111 and Tellabs 8170 cluster nodes. The version 1.9 or higher.9 or higher. 36.0b.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.4 or higher.4) • Setting 0 kbit/s CIR value to FR circuit (PVC) is allowed (CRF 4005120).

Bugs • When a new UBU load is downloaded via the File Manager. It is successful. If the back up is not complete when the node manager makes a request to query data from the FRE.4 or higher. .9 or higher.2 Version 1. During the initialization period when data is being backed up.0 or higher.4 Enhancements and Fixed Bugs • If congestion rate of a logical port exceeds the congestion threshold of that port. (Get Operation failure. MartisDXX Manager support for setting the congestion threshold to a user type logical port is available in Release 9. SCU-H (SCZ545) software version must be 1.2 or higher. FRE processor module software (FRZ535) version must be 1. SXU-V (SXZ630) software version must be 1.14. After the UBU initialization is completed. it is prevented from doing this and the error occurs. This does not invalidate the download.1 or higher GMH (GMZ283) software version must be 6. fault condition ‘FR logical port one minute congestion threshold exceeded’ will be set.11 or higher.9 or higher.2 or higher. SCP (SCZ281) software version must be 3. Operation 3 (GET) reject 253 locking error).12 or higher.0b. it is possible that the File Manager will get error 707. CCU (SCZ286) software version must be 2. the downloaded UBU load is shown to be active. if the file manager is closed and then re-opened.10 or higher. emergency update 6 or higher. (CRF ID 4004172) Dependencies • • • • • • • • • • • • • • • FRU (base unit UBU259) hardware version must be 1. SXU-C (SXZ289) software version must be 2. the NMS is prevented from querying the FRE.1 or higher. SXU-A/B (SXZ282) software version must be 6. This happens after the UBU load has been downloaded and when the FRE is reinitialising.0 or higher.Unit Software Version Dependencies in Discontinued Products 36. GMX (GMZ544) software version must be 3. CXU-M (SXZ288) software version must be 2. MartisDXX Manager support for setting the congestion threshold to a trunk type logical port is available in Release 11 Service Pack 3 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 396 10004_22 © 2008 Tellabs. MartisDXX Manager support for overbooking of logical port is available in Release 11 Service Pack 2 or higher. SCU (SCZ280) software version must be 8. Restrictions • FRU initialization can take more than 10 minutes in a heavily configured unit.

14. Modified performance statistics quering of a circuit (CRF ID 4003385). emergency update 6 or higher. it is prevented from doing this and the error occurs.0 or higher. SXU-C (SXZ289) software version must be 2. This happens after the UBU load has been downloaded and when the FRE is reinitialising. SCU (SCZ280) software version must be 8. This does not invalidate the download.(CRF ID 4003740) Start time of 24h performance period is set to 00:00 after reset (CRF ID 4003385).2 or higher. CCU (SCZ286) software version must be 2. CXU-M (SXZ288) software version must be 2. SCU-H (SCZ545) software version must be 1. MartisDXX Manager support for overbooking of logical port is available in Release 11 Service Pack 2 or higher.1 or higher.11 or higher. Dependencies • • • • • • • • • • • • • FRU (base unit UBU259) hardware version must be 1.2 or higher. During the initialization period when data is being backed up. it is possible that the File Manager will get error 707.Unit Software Version Dependencies in Discontinued Products 36. GMH (GMZ283) software version must be 6.0b.12 or higher. 10004_22 © 2008 Tellabs. Bugs • When a new UBU load is downloaded via the File Manager.10 or higher. Operation 3 (GET) reject 253 locking error).0 or higher. Restrictions • FRU initialization can take more than 10 minutes in a heavily configured unit. After the UBU initialization is completed.3 Version 1.3 Enhancements • • • Overbooking of logical ports is enabled. (Get Operation failure.4 or higher. MartisDXX Manager support for this unit is available in Release 9. SXU-A/B (SXZ282) software version must be 6. the downloaded UBU load is shown to be active. SCP (SCZ281) software version must be 3. the NMS is prevented from querying the FRE.9 or higher.9 or higher. It is successful. If the back up is not complete when the node manager makes a request to query data from the FRE. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 397 . FRE processor module software (FRZ535) version must be 1. if the file manager is closed and then re-opened. GMX (GMZ544) software version must be 3.

14. It is successful. Operation 3 (GET) reject 253 locking error).2. the NMS is prevented from querying the FRE. After the UBU initialization is completed.4 Version 1.Unit Software Version Dependencies in Discontinued Products 36. (Get Operation failure. If the back up is not complete when the node manager makes a request to query data from the FRE. SXU-C (SXZ289) software version must be 2. SXU-A/B (SXZ282) software version must be 6. it is prevented from doing this and the error occurs.1 or higher. any existing frame relay circuits must be disconnected and the graceful discard status reset. Bugs • When a new UBU load is downloaded via the File Manager. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 398 10004_22 © 2008 Tellabs.7 or higher.0b. it is possible that the File Manager will get error 707. When upgrading to version 1. GMH (GMZ283) software version must be 6.8 or higher. .9 or higher. Restrictions • • FRU initialization can take more than 10 minutes in a heavily configured unit.9 or higher. the downloaded UBU load is shown to be active. During the initialization period when data is being backed up. This happens after the UBU load has been downloaded and when the FRE is reinitialising.2 Dependencies • • • • • • • FRE processor module software (FRZ535) version must be 0. SCU (SCZ280) software version must be 8. This does not invalidate the download. MartisDXX Manager support for this unit is available in Release 9. emergency update 6 or higher. Failure to do this will not correct the problem.4 or higher. if the file manager is closed and then re-opened. SCP (SCZ281) software version must be 3.

When graceful discard is set to ON by the NMS.2. it is set OFF in the FRE and vice versa. the NMS is prevented from querying the FRE. This does not invalidate the download. it is possible that the File Manager will get error 707.7 or higher. If the back up is not complete when the node manager makes a request to query data from the FRE. SCU (SCZ280) software version must be 8. Assignment of graceful discard on frame relay circuit is not done correctly in FRE. the downloaded UBU load is shown to be active. This happens after the UBU load has been downloaded and when the FRE is reinitializing.8 or higher. After the UBU initialization is completed. MartisDXX Manager support for this unit is available in Release 9.14. any existing frame relay circuits must be disconnected and the graceful discard status must be reset to the opposite value that is desired. SCP (SCZ281) software version must be 3. if the file manager is closed and then re-opened. It is successful. SXU-C (SXZ289) software version must be 2. Failure to do this will cause an incorrect setting if the unit is reset or replaced. During the period in the initialization when data is being backed up.0b. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 399 . GMH (GMZ283) software version must be 6. The user should set the graceful discard to the opposite value to the desired for it to work properly. it is prevented from doing this and the error occurs.1 or higher. SXU-A/B (SXZ282) software version must be 6.9 or higher.9 or higher.Unit Software Version Dependencies in Discontinued Products 36. Bugs • When a new UBU load is downloaded via the File Manager.5 Version 1. emergency update 6 or higher. Restrictions • • FRU initialization can take more than 10 minutes in a heavily configured unit.1 Dependencies • • • • • • • FRE processor module software (FRZ535) version must be 0.4 or higher. Operation 3 (GET) reject 253 locking error). (Get Operation failure. • 10004_22 © 2008 Tellabs. If an FRU is downgraded from 1.

SXU-A/B (SXZ282) software version must be 6. (Get Operation failure.6 Version 1. After the UBU initialization is completed. . MartisDXX Manager support for this unit is available in Release 9.2. It is successful. This does not invalidate the download.1 or higher. If a PRAM erase is performed. Bugs • When a new UBU load is downloaded via the File Manager. attempts to reconfigure a management DLCI which existed will fail. This happens after the UBU load has been downloaded and when the FRE is reinitializing.9 or higher. SCP (SCZ281) software version must be 3. it is set OFF in the FRE and vice versa. Restrictions • • • Only 512 PVCs are supported. the NMS is prevented from querying the FRE.9 or higher. If the FRU is reset or replaced. the downloaded UBU load is shown to be active. Failure to do this will cause an incorrect setting if the unit is reset or replaced. When graceful discard is set to ON by the NMS.8 or higher. SCU (SCZ280) software version must be 8. During the period in the initialization when data is being backed up. the unit software will allow a new management DLCI to be created on a logical port where one already existed. even if it is up. If the back up is not complete when the node manager makes a request to query data from the FRE. FRU initialization can take more than 10 minutes in a heavily configured unit.7 or higher. GMH (GMZ283) software version must be 6. SXU-C (SXZ289) software version must be 2. the entire FRU must be reset before re-configuring the unit.0 Dependencies • • • • • • • FRE processor module software (FRZ535) version must be 0.14. The user should set the graceful discard to the opposite value to the desired for it to work properly. if the file manager is closed and then re-opened. If an FRU is downgraded from 1.4 or higher. it is prevented from doing this and the error occurs. If only the FRE is reset. • • • • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 400 10004_22 © 2008 Tellabs. Operation 3 (GET) reject 253 locking error).0b. a fault will report that the LMI for the logical port is down. If a user logical port is configured to have some type of LMI active.Unit Software Version Dependencies in Discontinued Products 36. any existing frame relay circuits must be disconnected and the graceful discard status must be reset to the opposite value that is desired. emergency update 6 or higher. Assignment of graceful discard on frame relay circuit is not done correctly in FRE. it is possible that the File Manager will get error 707.

1.1 Dependencies • • • UBU Processor Module software version must be at least 1. • FRU in Cluster Node: • • • • Restrictions • None (800 circuits are allowed). HDLC-4CH (SCP211) (SCZ281) software version must be at least 3. SCU (SCZ280) software version must be at least 8. SXU (SXZ289) software version must be at least 2. emergency release 6 FRU in Basic Node: • • • • SCU (SCZ280) software version must be at least 8.8. MartisDXX Manager support for FRU is available in Release 9.0. Bugs • No known bugs.0b. GMH (GMZ283) software version must be at least 6.4.8. Release 0.15. SXU (SXZ282) software version must be at least 6.4. 10004_22 © 2008 Tellabs.1.1 Version 0. 36.1 of the FRZ535 software can be downloaded to the FRU. GMH (GMZ283) software version must be at least 6.Unit Software Version Dependencies in Discontinued Products 36. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 401 .9.8. HDLC-4CH (SCP211) (SCZ281) software version must be at least 3.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. The software UBZ534 is used on the UBU processor module of FRU. See the corresponding release note for more information.

. 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.8. SXU (SXZ289) software version must be at least 2.9. HDLC-4CH (SCP211) (SCZ281) software version must be at least 3. and the FRU resets.Unit Software Version Dependencies in Discontinued Products 36.1. SCU (SCZ280) software version must be at least 8.8. MartisDXX Manager support for FRU is available in Release 9. GMH (GMZ283) software version must be at least 6. Bugs • If a circuit has been created with a defined path using a node number instead of a trunk logical port.4. FRU in Basic Node: • • • • SCU (SCZ280) software version must be at least 8.4. If a circuit is created without adequate bandwidth available. This could potentially cause traffic to be disrupted if the trunk now in the defined path goes down.15. GMH (GMZ283) software version must be at least 6.8. • FRU in Cluster Node: • • • • Restrictions • 512 circuits allowed in this release.0. the node number is changed in the defined path to a trunk logical port.7 Dependencies • • • UBU Processor Module software version must be at least 1.1. • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 402 10004_22 © 2008 Tellabs.2 Version 0. the FRE gets into an unstable state. SXU (SXZ282) software version must be at least 6. emergency release 6.0b. HDLC-4CH (SCP211) (SCZ281) software version must be at least 3.

12 can be downloaded to GCH-A units with the revision 2. 36.2 Version 2.11 Dependencies • No dependencies. …).1 and 4. You cannot bring 106 delay back below 255.4 or later.0. 10004_22 © 2008 Tellabs.16. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 403 .54 loop activation is not according to spec.16. V.0 if there are no dependencies or restrictions.x of GCZ284A (where x = 0. This software requires SXZ282 version 5.1 Version 2. 1. 3. 36.54. Restrictions • No restrictions. Allowed HW versions for the base unit are 3. Version 2. Restrictions • Does not support BTE64 and BTE384 module wetting current strapping info.Unit Software Version Dependencies in Discontinued Products 36. Bugs • • V.16 GCH-A Unit: GCZ284A Unit Software The software GCZ284A is used on GCH-A units. 2. Bugs • No known bugs.12 Dependencies • No dependencies.

9 Dependencies • No dependencies.3 Version 2. GCH 221A version must be 3. 36. BTE 768 does not work.Unit Software Version Dependencies in Discontinued Products 36.0 or 3. Restrictions • • Does not support BTE64 and BTE384 module wetting current strapping info. Restrictions • • Does not support BTE64 and BTE384 module wetting current strapping info.1. . 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.16.1. Bugs • No known bugs.1. GCH 221A version must be 3.4 Version 2.10 Dependencies • No dependencies. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 404 10004_22 © 2008 Tellabs. BTE 3 kbit/s does not work.16.0 or 3.

BTE 3 kbit/s does not work. GCH 221A version must be 3.16. 10004_22 © 2008 Tellabs. No pmp cluster support. 3 IFMOD ASIC (HW version 3.8 Dependencies • No dependencies.0.16. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 405 .Unit Software Version Dependencies in Discontinued Products 36. No SBM 64A support. 36.6 Version 2.7 Version 2. Restrictions • • Does not support BTE64 and BTE384 module wetting current strapping info.0 or 3.1. Restrictions • • • • Does not support BTE64 and BTE384 module wetting current strapping info.7 Dependencies • No dependencies.5 Version 2. Restrictions • • Does not support BTE64 and BTE384 module wetting current strapping info. Bugs • • NTU-A (SBM 64A) with Xb rate of 8 kbit/s is erroneous. Bugs • BTE 3 kbit/s does not work.16.1).6 Dependencies • No support of Rev. GCH 221A version must be 3. GCH 221A version must be 3.0. 36. Bugs • An existing ASIC timing error (octet pulse) is corrected by software.

GCH 221A version must be 3.16. 36.5 Dependencies • No dependencies. No interface signal missing alarm (PMA) if wetting current is on and there is a line break/short-circuit. Bugs • No known bugs. No pmp locking object. 36. GCH 221A version must be 3.10 Version 2.3 Dependencies • No dependencies.0 Bugs • Buffer slip alarms in the case of X30 framer.9 Version 2.8 Version 2. 8 kbit/s is not available. GCH 221A version must be 3. Restrictions • • Does not support BTE64 and BTE384 module wetting current strapping info.16. PMP Server functions not supported.4 Dependencies • No dependencies.0 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 406 10004_22 © 2008 Tellabs. Restrictions • • • • Does not support BTE64 and BTE384 module wetting current strapping info.Unit Software Version Dependencies in Discontinued Products 36.16. Restrictions • • • • Does not support BTE64 and BTE384 module wetting current strapping info. .0.

the connection capacity is too high. If interface module is none. In the case of N*64 kbit/s and V13 and CRC ON. Bugs • • • • • • • Some buffer lengths should be greater in the case of codirectional clocking. Some faults have zero GPT. The alarm bit on V110 frame is inverted. In the case of X30 framer and no control channel. Restrictions • • • • • • Does not support BTE64 and BTE384 module wetting current strapping info.Unit Software Version Dependencies in Discontinued Products Bugs • • • Buffer sizes at >64 kbit/s are not optimal. the unit informs of a Code error fault. 8 kbit/s is not available. GCH 221A version must be 3.0. 36. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 407 . the connection capacity is too high. Starting problems with BTE modules after reset.0 Dependencies • No dependencies. BTE n x 3 kbit/s not supported. In the case of X30 framer and no control channel. PMP Server functions not supported. The alarm bit on the V110 frame is inverted. the connection capacity is too high.16. 10004_22 © 2008 Tellabs.11 Version 2. SXU IA testing not supported.

1. SXU-A/B software version must be at least 6.0 can be downloaded to GMU-Ms having the revision 10..8. The user can minimize this problem by configuring monitoring TTPs of SNCgroup to the same values than the terminating TTP.4. GMZ547 software version must be 10.17. 36. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 408 10004_22 © 2008 Tellabs.0 of GMU-M supports advanced SNC group configuration but in MartisDXX Manager this feature is supported in version 10. Software GMZ546 is for the main processor and software GMZ547 is for the ASIC processor.2. Version 10. this may cause inconsistency between database and hardware. Restrictions • • Control channel in VC’s payload is not supported.0.1.1 Version 10.y of GMZ546 (where y=0. .1. XCG software version must be at least 2. GMZ546 version 10. SCP software version must be at least 3.Unit Software Version Dependencies in Discontinued Products 36.0 and later.0 Dependencies • • • • • SCU software version must be at least 8. If SNC groups are configured by earlier MartisDXX Manager releases.).17 GMU-M Unit: GMZ546 Unit Software Two software products are needed on GMU-M unit. Bugs • No known bugs..

18. Software GMZ546 is for main processor and software GMZ547 is for asic processor.).0 can be downloaded to GMU-M´s having the revision 10. 10004_22 © 2008 Tellabs. Bugs • No known bugs..2. GMZ547 version 10.y of GMZ547 (where y=0. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 409 . If SNC groups are configured by earlier MartisDXX Manager releases. Version 10.18 GMU-M Unit: GMZ547 Unit Software Two software products is needed on GMU-M unit. The user can minimize this problem by configuring monitoring TTPs of SNCgroup to the same values than the terminating TTP.1.. 36. this may cause inconsistency between database and hardware.0 Dependencies − GMZ546 software version must be 10.Unit Software Version Dependencies in Discontinued Products 36.1 Version 10.0 of GMU-M supports advanced SNC group configuration but in MartisDXX Manager this feature is supported in version 10.0. Restrictions • • Control channel in VC’s payload is not supported.0 and later.

19. Restrictions • Release R11 Service Pack 1 of MartisDXX Manager does not yet support ISD circuits between Basic node and A111 node.. MartisDXX Manager from Release R11 SP1 supports new port creations of ISD-NT.5 can be downloaded to ISD units having the version 1.1A supports new port creations of ISD-LT.y of UBZ532 (where y=0.1.19 ISD-LT and ISD-NT Units: UBZ532 Unit Software The software UBZ532 is used on ISD-LT and ISD-NT units. MartisDXX Manager support for this enhancement is available in Release R11 Service Pack 1 or higher.1 Version 1. Bugs • No known bugs..). Dependencies • • • • GMX (GMZ544) software version must be 3. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 410 10004_22 © 2008 Tellabs.Unit Software Version Dependencies in Discontinued Products 36. MartisDXX Manager from Release R10.5 Enhancements • ISD-NT support for A111 node (CRF ID 4003825). 36.2. .8 or higher to support this enhancement. The release 1.

19.4 Enhancements • ISD-LT support for A111 node (CRF ID 4001917).1A supports new port creations of ISD-LT.2 Version 1.19.1A supports all new faults. Restrictions • • No support for A111 node in ISD-NT. ISD event logs and new degraded/excessive errored seconds management interface feature and all error counters (R10. 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.0A service pack may support some of these things). 10004_22 © 2008 Tellabs. Dependencies • MartisDXX Manager from Release R10. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 411 .Unit Software Version Dependencies in Discontinued Products 36.3 Version 1. Restrictions • No support for A111 node in ISD-NT. Bugs • No known bugs. 36.3 Dependencies • MartisDXX Manager Release R10.

Restrictions • • • • • No support for A111 node in ISD-NT. No support for A111 node in ISD-LT.1 Dependencies • No dependencies.5 Version 1.Unit Software Version Dependencies in Discontinued Products 36. No ISD event log support. Restrictions • • • • • No support for A111 node in ISD-NT.19.19. No support for degraded/excessive errored seconds management interface. No ISD event log support. No support for A111 node in ISD-LT. . the ISD unit may disappear from the node inventory and the unit cannot be configured. No support for degraded/excessive errored seconds management interface. 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. • 36.4 Version 1. No support for all error counters. When using (very) bad communication lines.821 statistics 24 hours last only for 23 hours and 45 minutes.2 Dependencies • No dependencies. No support for all error counters. In the G. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 412 10004_22 © 2008 Tellabs. Sometimes the unit recovers from this by itself but sometimes it requires manual reset.

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. the ISD unit may disappear from the node inventory and the unit cannot be configured. No support for all error counters. • • 36. No support for A111 node in ISD-LT.821 statistics 24 hours last only for 23 hours and 45 minutes.Unit Software Version Dependencies in Discontinued Products 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. Sometimes the unit recovers from this by itself but sometimes it requires manual reset.0A. The U interface activation process on ISD-NT does not work correctly if there is no NT1 device connected to ISD-LT. the ISD unit may disappear from the node inventory and the unit cannot be configured. In the G. Restrictions • • • • • No support for A111 node in ISD-NT. Sometimes the unit recovers from this by itself but sometimes it requires manual reset. No support for degraded/excessive errored seconds management interface. The U interface activation process on ISD-NT does not work correctly if there is no NT1 device connected to ISD-LT. The test loops do not work with MartisDXX Manager.6 Version 1. In the G.0 Dependencies • Full NMS support for this unit is available in MartisDXX Manger Release R9.19. The S interface not activated alarm does not get through the ISDs from the customer premises to exchange. No ISD event log support. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 413 . When using (very) bad communication lines. • • • • 10004_22 © 2008 Tellabs.821 statistics 24 hours last only for 23 hours and 45 minutes.

36. Restrictions • ISD-LT16 unit can be furnished only with two line cards when using IBZ610 V1.17 or higher. SXU-C (SXZ289) software version must be 10.20.0 or higher..1 Version 1.5 or higher. The dependency between software ISD-LT16 (IBZ610).2. Bugs • • Missing support for "Out of frame” fault in ISD-LT16 (CRF ID 4005330). SCP (SCZ281) software version must be 3.2.1 or higher. SXU-A/B (SXZ282) software version can be any version.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.1 or higher to support functionality of V5. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 414 10004_22 © 2008 Tellabs.2 or higher.Unit Software Version Dependencies in Discontinued Products 36.2.10 or higher to support functionality of V5. The MartisDXX Manager support for this ISD-LT16 unit is available in Release 12A SP3 or higher. Tellabs 8160 A111 and Tellabs 8170 cluster nodes.826” fault in ISD-LT16 (CRF ID 4005329).0 or higher. SCU (SCZ280) software version must be 8. SXU-V (SXZ630) and SCU-H (SCZ545) is functionality of V5. CCU (SCZ286) software version must be 2.. SXU-V (SXZ630) software version must be 2. The version 1. Missing support for "Performance event for G. CXU-M (SXZ288) software version must be 10.1 or higher. 2. Dependencies • • • • • • • • • • • • • ISD-LT16 (base unit IBU726) hardware version must be 1.0.0 Enhancements and Fixed Bugs • This is the first official version.0 of IBU726.) can be downloaded to ISD-LT16 units having the version 1. . Tellabs 8150 basic. XCG (SMZ538) software version must be 2. GMX (GMZ544) software version must be 3.y (where y=0. 1. SCU-H (SCZ545) software version must be 1.4 or higher.

. Version 2.4 or higher. SCP (SCZ281) software version must be 3.y of UBZ436 (where y=0. IUM-10T and IUM-8 units having the version 2.8 or higher. 1.0 or higher. (CR ID 300045360) Dependencies • • • • • • • • • • • IUM-8 base unit (UBU768) hardware version must be 2.21.. SXU-V (SXZ630) software version must be 1.6 or higher.1 or higher. STU-160 (STU315) hardware version 5. Tellabs 8150 basic and Tellabs 8160 A111 nodes.Unit Software Version Dependencies in Discontinued Products 36.2 can be downloaded to IUM-8 unit having the version 3. SCU (SCZ280) software version must be 8. SCU-H (SCZ545) software version must be 1. Restrictions • NTU setting backup feature (Plug and Play/PNP) requires SCP SW version 3.0.1 or higher. Enhancements • This software version has improved tolerance against disturbances in VTP bus which could lead to unit disappearing from inventory. 2.1 or higher.. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 415 . 10004_22 © 2008 Tellabs. IUM-10T and IUM-8 Units: UBZ436 Unit Software The unit software UBZ436 is used on IUM-5T. STU-160 (STU315) hardware version 4. 36.2 This version is only for IUM-8 hardware version 2.8 can be downloaded to IUM-5T. 2.). Version 3.1 and/or SCU SW version 8..1 Version 3. SXU-A/B (SXZ282) software version can be any version. 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.0. IUM-10T and IUM-8 units the Tellabs 8140 midi. XCG (SMZ538) software version must be 2.0 (SBZ385) software version must be 1. MartisDXX Manager support for IUM-8 is available in Release 12 Service Pack 1 or higher.4 or XCG SW version 2.0 (SBZ385) software version must be 2.21 IUM-5T.y of UBZ436 (where y=0.). Bugs • No known bugs. 1. GMX (GMZ544) software version can be any version.0 or higher.

21. STU-160 (STU315) hardware version 5. Thus NTU power off will cause just “Ntu power fault” fault.1 or higher.6 or higher. STU-160 (STU315) hardware version 4.0.1 or higher.Unit Software Version Dependencies in Discontinued Products 36.0 (SBZ385) software version must be 1. 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.1 and/or SCU SW version 8. In this software version “Ntu power fault” interface fault masks the “Loss of input signal” and “No response to NNM message” faults. .4 or higher.4 or XCG SW version 2. In addition.0 or higher.1 This version is only for IUM-8 hardware version 2. SCU-H (SCZ545) software version must be 1.2 Version 3.0 or higher. XCG (SMZ538) software version must be 2. Enhancements • The reason for this release is changes in fault handling (CR ID 300023226). SXU-V (SXZ630) software version must be 1. Bugs • No known bugs.8 or higher. GMX (GMZ544) software version can be any version.0 (SBZ385) software version must be 2. MartisDXX Manager support for IUM-8 is available in Release 12 Service Pack 1 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 416 10004_22 © 2008 Tellabs.0. Restrictions • NTU setting backup feature (Plug and Play/PNP) requires SCP SW version 3.1 or higher. Dependencies • • • • • • • • • • • IUM-8 base unit (UBU768) hardware version must be 2. SCP (SCZ281) software version must be 3. SCU (SCZ280) software version must be 8. the Ntu power off fault service status is changed to be a Service affecting fault (S). SXU-A/B (SXZ282) software version can be any version.

4 or XCG SW version 2. the plug-in-unit.1 or higher.1 or higher.0 This version is only for IUM-8 hardware version 2.0 (SBZ385) software version must be 1. GMX (GMZ544) software version can be any version.0 or higher. XCG (SMZ538) software version must be 2. SXU-A/B (SXZ282) software version can be any version. SXU-V (SXZ630) software version must be 1. SCU-H (SCZ545) software version must be 1.6 or higher.Unit Software Version Dependencies in Discontinued Products 36. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 417 . STU-160 (STU315) hardware version 4. SCU (SCZ280) software version must be 8.1 and/or SCU SW version 8. 10004_22 © 2008 Tellabs.1 or higher.0 or higher. Enhancements and Fixed Bugs • The reason for this release is to serve new hardware version of IUM-8. STU-160 (STU315) hardware version 5. SCP (SCZ281) software version must be 3.21.4 or higher. Bugs • No known bugs.0.0. Restrictions • NTU setting backup feature (Plug and Play/PNP) requires SCP SW version 3. MartisDXX Manager support for IUM-8 is available in Release 12 Service Pack 1 or higher. Dependencies • • • • • • • • • • • IUM-8 base unit (UBU768) hardware version must be 2.8 or higher.0 (SBZ385) software version must be 2. 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.3 Version 3.

4 or XCG SW version 2.21.8 This is a production version based on version 2.7. SXU-A/B (SXZ282) software version can be any version.0 or higher.0 or higher. IUM-10T base unit (UBU255) hardware version must be 1.1 or higher.4 Version 2.0A supports NTU setting backup and line information features. SCP (SCZ281) software version must be 3.Unit Software Version Dependencies in Discontinued Products 36. When using IUM-8 STU-160 (STU315) hardware version 5. Bugs • No known bugs.0 or higher. Restrictions • NTU setting backup feature (Plug and Play/PNP) requires SCP SW version 3. the Ntu power off fault service status is changed to be a Service affecting fault (S). In this software version “Ntu power fault” interface fault masks the “Loss of input signal” and “No response to NNM message” faults.1 or higher.0 (SBZ385) software version must be 2. GMX (GMZ544) software version can be any version. When using IUM-8 STU-160 (STU315) hardware version 4.0.4 or higher. XCG (SMZ538) software version must be 2.0 or higher. Thus NTU power off will cause just “Ntu power fault” fault. Enhancements • The reason for this release is changes in fault handling (CR ID 300023241). SCU-H (SCZ545) software version must be 1.6 or higher. Dependencies • • • • • • • • • • • • • • IUM-8 base unit (UBU768) hardware version must be 1. SXU-V (SXZ630) software version must be 1.1 and/or SCU SW version 8. 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-10T or IUM-8 (8 x IUM-5T) XCG: 10 x IUM-10T or IUM-8(21 x IUM-5T) • SCP: no limit.1 or higher. MartisDXX Manager support for IUM-8 is available in Release 12 Service Pack 1 or higher. In addition. SCU (SCZ280) software version must be 8.0 (SBZ385) software version must be 1.8 or higher. IUM-5T base unit (UBU239) hardware version must be 2. . Tellabs® 8100 Managed Access System Unit Software Version Dependencies 418 10004_22 © 2008 Tellabs. MartisDXX Manager Release 10.

SCP (SCZ281) software version must be 3. When using IUM-8 STU-160 (STU315) hardware version 4. When using IUM-8 STU-160 (STU315) hardware version 5.6. IUM-10T base unit (UBU255) hardware version must be 1. IUM-5T base unit (UBU239) hardware version must be 2. MartisDXX Manager support for IUM-8 is available in Release 12 Service Pack 1 or higher. GMX (GMZ544) software version can be any version. XCG (SMZ538) software version must be 2. SCU (SCZ280) software version must be 8.1 or higher.1 or higher.0 or higher.Unit Software Version Dependencies in Discontinued Products 36.8 or higher.4 or XCG SW version 2.0 (SBZ385) software version must be 1.0 or higher. SCU-H (SCZ545) software version must be 1.21.1 or higher. Enhancements and Fixed Bugs • IF module detection correction. 10004_22 © 2008 Tellabs.1 and/or SCU SW version 8. 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-10T or IUM-8 (8 x IUM-5T) XCG: 10 x IUM-10T or IUM-8(21 x IUM-5T) • SCP: no limit. Restrictions • NTU setting backup feature (Plug and Play/PNP) requires SCP SW version 3. Bugs • No known bugs.7 This is a production version based on version 2. (CR ID 200010407) Dependencies • • • • • • • • • • • • • • IUM-8 base unit (UBU768) hardware version must be 1.0 or higher.5 Version 2.0 (SBZ385) software version must be 2.0. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 419 .0A supports NTU setting backup and line information features. SXU-A/B (SXZ282) software version can be any version. MartisDXX Manager Release 10.6 or higher.4 or higher.0 or higher. SXU-V (SXZ630) software version must be 1.

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-10T or IUM-8 (8 x IUM-5T) XCG: 10 x IUM-10T or IUM-8(21 x IUM-5T) • SCP: no limit. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 420 10004_22 © 2008 Tellabs.21.4 or XCG SW version 2.1 or higher.8 or higher.0 or higher. IUM-10T base unit (UBU255) hardware version must be 1. IUM-5T base unit (UBU239) hardware version must be 2.1 or higher. CR ID 200008596) Dependencies • • • • • • • • • • • • • • IUM-8 base unit (UBU768) hardware version must be 1.Unit Software Version Dependencies in Discontinued Products 36.1 and/or SCU SW version 8. Restrictions • NTU setting backup feature (Plug and Play/PNP) requires SCP SW version 3. SCU-H (SCZ545) software version must be 1.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. (CR ID 200005421. Bugs • No known bugs.0 or higher. SXU-A/B (SXZ282) software version can be any version. XCG (SMZ538) software version must be 2. MartisDXX Manager Release 10. SCU (SCZ280) software version must be 8.0 (SBZ385) software version must be 1. LOS fault was not active after resetting IUM.0 or higher.0 (SBZ385) software version must be 2. SCP (SCZ281) software version must be 3.6 Version 2.5. When using IUM-8 STU-160 (STU315) hardware version 5.0. Enhancements and Fixed Bugs • • NTU power fault detection correction. GMX (GMZ544) software version can be any version.1 or higher.6 or higher. (CR ID 200008412) LOS fault correction. When using IUM-8 STU-160 (STU315) hardware version 4.6 This is a non-production version based on version 2.4 or higher.0 or higher. SXU-V (SXZ630) software version must be 1.

0 or higher. of the plug-in-unit.0 or higher.4 or higher.0 (SBZ385) software version must be 2. IUM-10T base unit (UBU255) hardware version must be 1. GMX (GMZ544) software version can be any version.0 (SBZ385) software version must be 1. Dependencies • • • • • • • • • • • • • • IUM-8 base unit (UBU 768) hardware version must be 1. SXU-A/B (SXZ282) software version can be any version.7 Version 2. Bugs • No known bugs.1 and/or SCU SW version 8. When using IUM-8 STU-160 (STU315) hardware version 4.Unit Software Version Dependencies in Discontinued Products 36. This release serves also older hardware types. SCU (SCZ280) software version must be 8.0. IUM-8.4 or XCG SW version 2.21.1 or higher. IUM-5T and IUM-10T. MartisDXX Manager Release 10. When using IUM-8 STU-160 (STU315) hardware version 5.1 or higher. SXU-V (SXZ630) software version must be 1. 10004_22 © 2008 Tellabs.1 or higher. SCU-H (SCZ545) software version must be 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 421 .8 or higher. Restrictions • NTU setting backup feature (Plug and Play/PNP) requires SCP SW version 3.0A supports NTU setting backup and line information features.5 Enhancements • The reason for this release is to serve also new hardware version. XCG (SMZ538) software version must be 2. SCP (SCZ281) software version must be 3. 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-10T or IUM-8 (8 x IUM-5T) XCG: 10 x IUM-10T or IUM-8(21 x IUM-5T) SCP: no limit. IUM-5T base unit (UBU 239) hardware version must be 2.0 or higher.6 or higher. MartisDXX Manager support for IUM-8 is available in Release 12 Service Pack 1 or higher.0 or higher.

only NMS communication. Restrictions • No restrictions. .3 Dependencies • NTU setting backup feature (Plug and Play/PNP) requires SCP SW version 3. • NMS release 10.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-10T (8 x IUM-5T) XCG: 10 x IUM-10T (21 x IUM-5T) SCP: no limit. Disappearing does not effect data. • MartisDXX Manager Release 10.0A supports NTU setting backup and line information features.0A supports NTU setting backup and line information features. Bugs • If there are more than two bad communication lines between the IUM and the NTUs. Restrictions • No restrictions. the IUM unit may disappear from node inventory.1 and/or SCU SW version 8.4 Dependencies • NTU setting backup feature (Plug and Play/PNP) requires SCP SW version 3. Bugs • No known bugs. 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-10T (8 x IUM-5T) XCG: 10 x IUM-10T (21 x IUM-5T) SCP: no limit.21. 36.1 and/or SCU SW version 8.4 or XCG SW version 2.Unit Software Version Dependencies in Discontinued Products 36.8 Version 2. Very rarely unit recovers from this itself and therefore unit must be reset manually.4 or XCG SW version 2.21. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 422 10004_22 © 2008 Tellabs.9 Version 2.0.

2 Dependencies • No dependencies.10 Version 2. In G. Sometimes unit recovers from this itself but sometimes it requires manual reset. the IUM unit may run out of xport quotas and disappears from node inventory and unit cannot be configured. Restrictions • • No NTU setting backup support (plug and play). No line information support. • 10004_22 © 2008 Tellabs. Bugs • When there are bad communication lines between the IUM and the NTUs. Bugs • When there are bad communication lines between the IUM and the NTUs.1 Dependencies • No dependencies. Double rack with SXU-A cannot be filled up with the IUM units because of the limitation of 8 kbit/s cross-connections. the IUM unit may run out of xport quotas and disappears from node inventory and unit cannot be configured. No line information support. Sometimes unit recovers from this itself but sometimes it requires manual reset.Unit Software Version Dependencies in Discontinued Products 36. In G. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 423 . Restrictions • • • No NTU setting backup support (plug and play).821 statistics 24 hours last only 23 hours and 45 minutes.821 statistics 24 hours last only 23 hours and 45 minutes. • 36.21.21.11 Version 2.

When there are bad communication lines between the IUM and the NTUs. Sometimes unit recovers from this itself but sometimes it requires manual reset.821 limit events under unavailable time. IUM-10T (wide unit with eight interfaces) is not supported.821 statistics 24 hours last only 23 hours and 45 minutes.Unit Software Version Dependencies in Discontinued Products 36.12 Version 2. When there are bad communication lines between the IUM and the NTUs. Sometimes unit recovers from this itself but sometimes it requires manual reset. the IUM unit may run out of xport quotas and disappears from node inventory and unit cannot be configured. Bugs • • • Erroneous G. No line information support. the IUM unit may run out of xport quotas and disappears from node inventory and unit cannot be configured. In G.821 statistics 24 hours last only 23 hours and 45 minutes. . Does not work correctly in the Create Inventory operation (does not always unlock all ports).0 Dependencies • No dependencies.21. Double rack with SXU-A cannot be filled up with the IUM units because of the limitation of 8 kbit/s cross-connections. Does not work correctly in the Create Inventory operation (does not always unlock all ports). • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 424 10004_22 © 2008 Tellabs.21. 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.821 limit events under unavailable time. Restrictions • • • No NTU setting backup support (plug and play). Restrictions • • • • No NTU setting backup support (plug and play).13 Version 1. In G.3 Dependencies • No dependencies. • 36. Bugs • • • Erroneous G.

Interface alarms are activated although interface is unlocked (incorrect LED handling). Restrictions • • • • • • No NTU setting backup support (plug and play).21.821 limit events under unavailable time. 10004_22 © 2008 Tellabs. the IUM unit may run out of xport quotas and disappears from node inventory and unit cannot be configured. IUM-10T (wide unit with eight interfaces) is not supported. Sometimes unit recovers from this itself but sometimes it requires manual reset. In this state the IUM unit may be unstable. Double rack with SXU-A cannot be filled up with the IUM units because of the limitation of 8 kbit/s cross-connections. After IUM mode change..g. Double rack with SXU-A cannot be filled up with the IUM units because of the limitation of 8 kbit/s cross-connections.Unit Software Version Dependencies in Discontinued Products 36. in STU-160) is not supported. No line information support. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 425 . Restrictions • • • • No NTU setting backup support (plug and play). • 36. In G.14 Version 1. Does not work correctly in the Create Inventory operation (does not always unlock all ports). only B-channels are supported (not the D-channel) Setting remote loop at remote unit (e.821 statistics 24 hours last only 23 hours and 45 minutes.1 Dependencies • No dependencies. In Terminal and Exchange modes. Bugs • • • • • Erroneous G.15 Version 1. Interface mode must be set after IUM mode change.0 Dependencies • NMS support for this unit is available in Release 8.21. When there are bad communication lines between the IUM and the NTUs.0. IUM-10T (wide unit with eight interfaces) is not supported. No line information support. interface mode is undefined (conflict).

Sometimes unit recovers from this itself but sometimes it requires manual reset. In G. Interface mode must be set after IUM mode change. In this state the IUM unit may be unstable. After IUM mode change.) If a downloaded version of the software is in use. it is possible. interface mode is undefined (conflict).) It may happen that when IUM is removed from node (for example. Module type. due to HW fault) and a replace unit of the same type is inserted to its place. Erroneous G. it is possible that the IUM introduces a 125 us delay between the two 64 kbit/s channels. but correctable with software.821 statistics limits. Retrying the operation usually helps. that parameterizing the unit or downloading new software leads to software reset. the new unit does not get the correct backup parameters from the old unit (and the user has to reconfigure something). 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). (This bug materializes rarely. When there are bad communication lines between the IUM and the NTUs.Unit Software Version Dependencies in Discontinued Products Bugs • • • • • • The interface handler processes’ stack may be too small in some cases and therefore unpredictive errors may occur. This will. (Actually a HW bug. due to erroneous synchronization between interrupt handling software and flash memory software. 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).821 limit events under unavailable time. Unit mode. NNM parameters ‘Deficient’: Loop timeout. If a 128 kbit/s circuit is routed through IF 1 of an IUM. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 426 10004_22 © 2008 Tellabs. The reason is that SCU has not obtained the latest backup settings. totally corrupt the 128 kbit/s circuit. • • • • ‘Correct’: G. .821 statistics 24 hours last only 23 hours and 45 minutes. ‘correct’ and ‘deficient’. changing the latter ones is not automatically backed up by SCU. the IUM unit may run out of xport quotas and disappears from node inventory and unit cannot be configured. of course. U interface mode There is a remedy: once you change some of the ‘deficient’ parameters. There are two types of settings. also change some ‘correct’ parameter.

1 Version 1.1 or higher. After the ERZ550 software is rebooted.y (where y=0. the following two steps are required in order to activate the downloaded version: 1.2.0 or higher.4 can be downloaded to ERH581 module having the version 1. Now the recently downloaded software is up and running and it is approved to be in permanent use.1 or higher. XCG (SMZ538) software version must be 2. The size of the ERZ550 file is 1.0 or higher. Cluster and Midi Nodes and A111. MartisDXX Manager support for this LIU-H/bridging or routing is available in Release 10.0 (43). 1.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.).. CXU-M (SXZ288) software version can be any version. SXU-A/B (SXZ282) software version can be any version. SXU-V (SXZ630) software version must be 1..2 or higher to support 24 kB backup storage needed by LIU-H. 36.4 NOTE! The release numbering conforms to the convention of Tellabs Oy although the version number of ERZ550 is 5.22.6 or higher. SCU-H (SCZ545) software version must be 1. NOTE! After the downloading has completed. 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. UBU714 and ERH581 hardware modules together with their software modules make up a LIU-H bridge/router unit. SCP (SCZ281) software version must be 3.102 bytes. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 427 . (CRF 4004294) Dependencies • • • • • • • • • • • • • ERH581 hardware version must be 1. The version 1. 2. (CRF 4004720) IP routing works for a fifth Frame Relay port. ERH581 hardware module has to be reset by giving command “reboot” at the LIU command shell to make the downloaded ERZ550 version run.1A or higher. 10004_22 © 2008 Tellabs. UBU714 (UBZ543) software version must be 1.112.4 or higher to support 24 kB backup storage needed by LIU-H. SCU (SCZ280) software version must be 8. GMX (GMZ544) software version can be any version. SXU-C (SXZ289) software version can be any version. CCU (SCZ286) software version can be any version. 2. command “markimage ok” must be given at LIU command shell.Unit Software Version Dependencies in Discontinued Products 36.

Dependencies • • • • • • ERH581 hardware version must be 1.4 or higher to support 24 kB backup storage needed by LIU-H. SCP (SCZ281) software version must be 3. • • • 36.1A or higher.799 bytes Enhancements • Rebooting the LIU-H unit takes shorter time than earlier.2 or higher to support 24 kB backup storage needed by LIU-H. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 428 10004_22 © 2008 Tellabs. Depending on the configuration the “reinit” command may cause the LIU-H to reboot itself. Multicast OSPF and RIP/RIP-2 protocols do not work over Frame Relay links.111. Restrictions • Version 1. UBU714 (UBZ543) software version must be 1.1 or higher.Unit Software Version Dependencies in Discontinued Products Restrictions • • • • • Version 1.0 (42). .3 NOTE! The release numbering conforms to the convention of Tellabs Oy although the version number of ERZ550 is 5.2. 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.1 or earlier versions. The maximum number of ports to which Frame Relay link protocol can be applied simultaneously is 5. The status information describing that WAN link is down is not reported in MartisDXX Manager FMS.0 or higher. MartisDXX Manager support for this LIU-H/bridging or routing is available in Release 10. The size of the ERZ550 file is 1.0 or higher.4 shall not be downgraded to 1.3 shall not be downgraded to 1. Dynamic routing (OSPF. SCU (SCZ280) software version must be 8.1 or earlier versions.22. XCG (SMZ538) software version must be 2. Bugs • • Activation of PPP over SCPP -ports needs reboot.2 Version 1. 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. RIP/RIP-2) over unnumbered links is not supported.

2. The status information describing that WAN link is down is not reported in MartisDXX Manager FMS. Encryption (DES. Dynamic routing (OSPF. The maximum number of ports to which Frame Relay link protocol can be applied simultaneously is 5. The “reinit” command is available to be used for activating configuration changes without rebooting the system. The size of the ERZ550 file is 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 429 . RIP/RIP-2) over unnumbered links is not supported. IP address saving for CPE links can be used. After configuring Frame Relay link it needs to be activated by giving the command “reboot” at the LIU-H command shell. 3DES) for PPP links is supported. Dependencies • • ERH581 hardware version must be 1. Depending on the configuration the “reinit” command may cause the LIU-H to reboot itself. Network address translation (NAT) functionality is added. Point-to-multipoint CPE connections for Frame Relay links are supported. Bandwidth limitation for CPE links is supported. Enhancements • • • • • • • • • • • DHCP server and relay agent functionality is added. • • • 36. UBU (the software of UBU714) software version must be 1. The “ifstat” command is added on with option –l to select port. 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. Bugs • • Activation of PPP over SCPP -ports needs reboot.1 or higher.075 bytes. One command shows all IP filters.111. 10004_22 © 2008 Tellabs. Multicast OSPF and RIP/RIP-2 protocols do not work over Frame Relay links. Now the maximum number of Frame Relay DLCIs is 256.0 (40).0 or higher.3 Version 1.Unit Software Version Dependencies in Discontinued Products • • • • Activating and deactivating the bridge function needs reboot. Now the pagination of terminal display output can be done as follows: |more.2 NOTE! The release numbering conforms to the convention of Tellabs Oy although the version number of ERZ550 is 5.22.

The status information describing that WAN link is down is not reported in MartisDXX Manager FMS.0 or higher. LIU-H will become inoperable. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 430 10004_22 © 2008 Tellabs.4 or higher to support 24 kB backup storage needed by LIU-H.4 Version 1. The maximum number of ports to which Frame Relay link protocol can be applied simultaneously is 5. UBU714 (UBZ543) software version must be 1.0 or higher. SCP (SCZ281) software version must be 3. Multicast OSPF and RIP/RIP-2 protocols do not work over Frame Relay links.2 or higher to support 24 kB backup storage needed by LIU-H.1A or higher.0 (31).4 or higher to support 24 kBytes backup storage needed by LIU-H. Depending on the configuration the “reinit” command may cause the LIU-H to reboot itself. Version 1. .2 shall not be downgraded to earlier versions. Dynamic routing (OSPF. 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. Restrictions • • • • • • The maximum number of supported MCPP ports is 62.22. SCU (SCZ280) software version must be 8. RIP/RIP-2) over unnumbered links is not supported. 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. MartisDXX Manager support for this LIU-H/bridging or routing is available in Release 10. Dependencies • • • • ERH581 hardware version must be 1. SCU (SCZ280) software version must be 8.1 or higher. Activation of PPP over SCPP ports needs reboot.2 or higher to support 24 kBytes backup storage needed by LIU-H.0. • • • 36. Bugs • • • If more than 62 MCPP ports are configured.Unit Software Version Dependencies in Discontinued Products • • • • SCP (SCZ281) software version must be 3.1 NOTE! The release numbering conforms to the convention of Tellabs Oy although the version number of ERZ550 is 5. XCG (SMZ538) software version must be 2.

SCP (SCZ281) software version must be 3.0 or higher. Dependencies • • • • • • ERH581 hardware version must be 1.22.0 or higher.4 or higher to support 24 kB backup storage needed by LIU-H. MartisDXX Manager support for this LIU-H/bridging or routing is available in Release 10. Frame Relay link protocol over MCPP ports does not work.0. XCG (SMZ538) software version must be 2. It may happen that LIU-H reboots itself as it becomes overloaded with data traffic.1 Service Pack A or higher. Restrictions • No restrictions. Bugs • No known bugs.Unit Software Version Dependencies in Discontinued Products • • XCG (SMZ538) software version must be 2. MartisDXX Manager support for this LIU-H/bridging or routing is available in Release 10.0 (29).1A or higher.5 Version 1. 36. SCU (SCZ280) software version must be 8.0 NOTE! The release numbering conforms to the convention of Tellabs Oy although the version number of ERZ550 is 5.2 or higher to support 24 kB backup storage needed by LIU-H. Restrictions • No restrictions. UBU714 (UBZ543) software version must be 1.0 or higher. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 431 .1 or higher. Bugs • • • The spanning tree algorithm does not work correctly (related to Bridge functionality). 10004_22 © 2008 Tellabs.

SCP is needed and each LIU-H unit requires 24 kilobytes of flash memory from SCP. Reset RM button in the MartisDXX Manager Node Manager LIU Unit Parameter window makes a hardware reset on the router module.2 or higher. SCU-H (SCZ545) software version must be 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 432 10004_22 © 2008 Tellabs.Unit Software Version Dependencies in Discontinued Products 36. Extra reboot fault fixed.0A-2.1 or higher.0 or higher. CCU (SCZ286) software version can be any version.1 Version 1. 36. The release 1.23.0 (x). CXU-M (SXZ288) software can be any version. The software version of ERH module has to be 5. Bugs • No known bugs. Restrictions • If SCU is used. . SCU (SCZ280) software version must be 8. SXU-C (SXZ289) software version can be any version.6 or higher. The ERH module performs as a bridge. SXU-A/B (SXZ282) software version can be any version. (CRF 4004818) Dependencies • • • • • • • • • • • • • LIU-H (base unit UBU714) hardware must be 1..1A.0. SXU-V (SXZ630) software version must be 1.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. an IP router or as a brouter. MartisDXX Manager preplanning support for this unit is available in Release 10.0 or higher.. Cluster and Midi Nodes and A111.).2. where the value of x is 31 or greater.2 Enhancements and Fixed Bugs • Some functions related to router module (ERH) rebooting and reboot state detection corrected.2 of the UBZ543 can be downloaded to LIU-H units having the version 1. Full support will be available in Release 10.4 or higher. SCP (SCZ281) software version must be 3.y of UBZ543 (where y=0. XCG (SMZ538) software version must be 2. GMX (GMZ544) software version can be any version.1. UBZ543 communicates with the ERZ550 software of the ERH module (ERH581 processor board) utilizing a dual-port RAM.

Bugs • No known bugs.0. SCZ280 program.3 Version 1. version 2. The software version of ERH module has to be 5. • Each LIU unit requires 24 kilobytes of flash memory from the SCP. SCP is needed. version 3.0. Restrictions The LIU-H unit requires the following units and modules in the subrack. 10004_22 © 2008 Tellabs. version 3. where the value of x is 31 or greater. • Each LIU-H unit requires 24 kilobytes of flash memory from the SCP. • If the node uses SCU.0A. version 2. Full support will be available in later service packs. Full support will be available in Release 10.23. • If the node uses SCU. The software version of ERH module has to be 5.0. version 8. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 433 .23. Restrictions The LIU-H unit requires the following units and modules in the subrack. SCZ280 program.4 SCZ281 program.2 Version 1.2 If the node uses XCG SMZ538 program.0A-2.0. 36.0 (29).1A.1 Dependencies • • MartisDXX Manager preplanning support for this unit is available in Release 10. version 8. SCP is needed.0 (x).4 SCZ281 program.Unit Software Version Dependencies in Discontinued Products 36.0 Dependencies • • MartisDXX Manager preplanning support for the LIU unit is available in Release 10.2 If the node uses XCG SMZ538 program.

. 2000 after midnight of February 28. 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.0 Dependencies • Preliminary MartisDXX Manager support for this unit is available in Release 9.2.). Preliminary MartisDXX Manager support for this unit is available in Release 9. Restrictions • No restrictions.0.3.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.. 2000). MartisDXX Manager support specifically for this unit will be available in Release 10. Bugs • No known bugs. 36. Hence the UBU date becomes March 1.24.0.0.0.Unit Software Version Dependencies in Discontinued Products Bugs • UBU date management does not detect that year 2000 is a leap year.24.1 Version 1.1. Version 1. MartisDXX Manager support for DTE error counters is available in Release 10.1 Dependencies • • • Does not support ‘frequency difference’ and ‘DTE out of sync’ alarms with NTU-2M hardware version 1.2 Version 1.24 NTU-2M Unit: SBZ542 Unit Software The software SBZ542 is used on NTU-2M network terminating units.INI includes definition NTU_2M=TRUE ).INI includes definition NTU_2M=TRUE ). MartisDXX Manager support specifically for this unit will be available in Release 10.1 can be downloaded to NTU-2M having the revision 1. 2000 (it should become February 29.y of SBZ542 (where y=0.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. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 434 . 10004_22 © 2008 Tellabs. 36. 36.

5 Dependencies • No dependencies.1 Version 1.25.Unit Software Version Dependencies in Discontinued Products Bugs • ‘BER more than 10E-3’ does not work correctly. If it is grounded. 10004_22 © 2008 Tellabs. 4-wire) is not fast enough for certain PDA 64 applications.25. No support for implementing 144 kbit/s line rate instead of 56 kbit/s. Bugs • No known bugs.2 Version 1. 36.25 SBM 384A NTU: SBA380 Unit Software The software SBA380 is used on SBM 384A NTU.25. Restrictions • No restrictions. Software determines which oscillator is assembled from connector TP4 pin 6. 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. the oscillator must be changed.4 Dependencies • No dependencies. oscillator for rate 144 kbit/s is assumed. Circuit 109 response time (64 kbit/s.3 Dependencies • No dependencies. Restrictions • • • In 2-wire operation the configuration scrambler: none is not allowed. 36. If 144kbit/s is implemented. 36.3 Version 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 435 . 36.

No support for VGX332. the oscillator must be changed. If 144 kbit/s is implemented. No support for implementing 144 kbit/s line rate instead of 56 kbit/s.4 Version 1.25.25. oscillator for rate 144 kbit/s is assumed. the oscillator must be changed. 36. 4-wire) is not fast enough for certain PDA 64 applications. . If it is grounded. Restrictions • • • • • • In 2-wire operation the configuration scrambler: none is not allowed.2 Dependencies • No dependencies. No support for VGM334.Unit Software Version Dependencies in Discontinued Products Bugs • RLBtime: 4 min and RLBtime: 8 min are 4 min too long. Neighbour node supervision parameterization is not possible from the NTU keys. Circuit 109 response time (64 kbit/s. If 144 kbit/s is implemented. Circuit 109 response time (64 kbit/s.5 Version 1. oscillator for rate 144 kbit/s is assumed. Software determines which oscillator is assembled from connector TP4 pin 6.1 Dependencies • No dependencies. Restrictions • • • • • In 2-wire operation the configuration scrambler: none is not allowed. If it is grounded. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 436 10004_22 © 2008 Tellabs. Software determines which oscillator is assembled from connector TP4 pin 6. No support for implementing 144 kbit/s line rate instead of 56 kbit/s. 36. No support for VGM334. Neighbour node supervision parameterization is not possible from the NTU keys. Bugs • RLBtime: 4 min and RLBtime: 8 min are 4 min too long. 4-wire) is not fast enough for certain PDA 64 applications.

36. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 437 .4 Dependencies • No dependencies. Bugs • No known bugs. No support for implementing 144kbit/s line rate instead of 56kbit/s.4-wire) is not fast enough for certain PDA64 applications. oscillator for rate 144 kbit/s is assumed. If 144 kbit/s is implemented. Bugs • No known bugs.2 Version 1. the oscillator must be changed.26.26 SBM 384E NTU: SBE380 Unit Software The software SBE380 is used on SBM 384E NTU.3 Dependencies • No dependencies.Unit Software Version Dependencies in Discontinued Products Bugs • • Adaptive real-time does not work. 36. 10004_22 © 2008 Tellabs.26. 36.1 Version 1. RLBtime: 4 min and RLBtime: 8 min are 4 min too long. If it is grounded. Restrictions • • Circuit 109 response time (64kbit/s. Restrictions • No restrictions. Software determines which oscillator is assembled from connector TP4 pin 6.

Bugs • Bug in G. No asynchronous Circuit Loop Test support.27.27.1 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 438 10004_22 © 2008 Tellabs.Unit Software Version Dependencies in Discontinued Products 36. Bugs • No known bugs.821 statistics.1 Version 1. Restrictions • • In 2-wire operation the configuration scrambler: none is not allowed. Circuit Loop Test does not generate correct G.27 SBM 64A NTU: SBA381 Unit Software The software SBA381 is used on SBM64A NTU. Restrictions • No restrictions.2 Dependencies • No dependencies.3 Dependencies • No dependencies. 36.2 Version 1. .821 statistics. 36.

Circuit Loop Test does not generate correct G. Circuit 109 response time (64 kbit/s. Bug in G. 10004_22 © 2008 Tellabs. Bugs • • • • Unnecessary alarms when GCH interface is not connected. Bug in G.Unit Software Version Dependencies in Discontinued Products 36. 36.4 Version 1.821 statistics. Bug in menu if X. Restrictions • • • In 2-wire operation the configuration scrambler: none is not allowed. No asynchronous Circuit Loop Test support. Bug in the menu if X.821 statistics.821 statistics.1 Dependencies • No dependencies. Bugs • • • Unnecessary alarms when GCH interface is not connected.821 statistics. Circuit Loop Test does not generate correct G.0 Dependencies • No dependencies. Circuit 109 response time (64 kbit/s. NTU cannot follow the rate from DTE. 4-wire) is not fast enough for certain PDA 64 applications. Restrictions • • • In 2-wire operation the configuration scrambler: none is not allowed.27.3 Version 1. 4-wire) is not fast enough for certain PDA 64 applications. No asynchronous Circuit Loop Test support.27.21 DTE card and no framing on the line: the LL state appears only when the left scroll key (<) is used.21 DTE card and no framing on the line: the LL state appears only when the left scroll key (<) is used. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 439 .

28.Unit Software Version Dependencies in Discontinued Products 36. In 2-wire operation the configuration scrambler: none is not allowed. Restrictions • No restrictions. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 440 10004_22 © 2008 Tellabs. Restrictions • • Circuit 109 response time is not fast enough for certain PDA64 applications.28. .3 Dependencies • No dependencies. Bugs • No known bugs.1 Version 1.2 Version 1.2 Dependencies • No dependencies. Bugs • No known bugs.28 SBM 64E NTU: SBE381 Unit Software The software SBE381 is used on SBM 64E NTU. 36. 36.

29 is always used. No scrambler selection. 36.4 Dependencies • No dependencies.29 SBM 768A NTU: SBA382 Unit Software The software SBA382 is used on SBM 768A NTU.Unit Software Version Dependencies in Discontinued Products 36. Restrictions • No restrictions.3 Dependencies • No dependencies. but you should use differential line coding when there is no frame on the line.2 Version 1. Note: Now you can select line code and framing independently. V.29. Bugs • RLBtime: 4min and 8min are 4 min too long.29. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 441 . Bugs • No known bugs. 36.1 Version 1. 10004_22 © 2008 Tellabs. Restrictions • • Line code and framing cannot be selected independently.

No scrambler selection.Unit Software Version Dependencies in Discontinued Products 36. No scrambler selection. Bugs • RLBtime: 4min and 8min are 4 min too long. Line code and framing cannot be selected independently.4 Version 1. V. Restrictions • • • Cannot be used as repeater if frame is on.29. V.2 Dependencies • No dependencies.29. Cannot be used as repeater if frame is on. 36.1 Dependencies • No dependencies. Bugs • RLBtime: 4min and 8min are 4 min too long.29 is always used.29 is always used. Neighbour node supervision parameterization is not possible from the NTU keys. Restrictions • • • • • No support for VGM334.3 Version 1. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 442 10004_22 © 2008 Tellabs. Line code and framing cannot be selected independently. .

NNM message handling implemented in receive direction. 36. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 443 . 32 or 64 kbit/s circuits over the Tellabs 8100 network.0 extended setting backup and downloading is not supported.30 SCP Module: SCZ281 Unit Software The software SCZ281 is used on SCP211 modules piggybacked on SCU.0 or higher. SXU-A/B (SXZ282) software version can be any version. 2. SXU-C (SXZ289) software version can be any version.3 Enhancements and Fixed Bugs • • Flash system improvement. 32 or 64 kbit/s circuit is one of the SCU ports 1. When settings backup resources offered by the SCU is insufficient. The shortcut control channels are HDLC links which can be connected through the 8.30.1 Version 3. Dependencies • • • • • • SCP (base unit SCP211) hardware version must be 3. Its main functions are to support the end points of shortcut control channels and to offer extended setting backup resources. SXU-V (SXZ630) software version must be 1. 16.0 or higher.Unit Software Version Dependencies in Discontinued Products 36. 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. Restrictions • With SCP211 version 2. SCU (SCZ280) software version must be 7. 3 or 4 associated with the HDLC channels 1. the SCP module offers extended settings backup space of up to 333 kB.0 or higher. 16. The cross-connection port at the end of the 8.6 or higher and SCU210 hardware version 2. 2.1 or higher. Bugs • No known bugs. 10004_22 © 2008 Tellabs. MartisDXX Manager support for this module is available in Release 9.

SXU-A/B (SXZ282) software version can be any version. SXU-V (SXZ630) software version must be 1.2 Enhancements and Fixed Bugs • Fault management improvement. Bugs • No known bugs. Restrictions • With SCP211 version 2.6 or higher and SCU210 hardware version 2.0 extended setting backup and downloading is not supported.0 or higher. . Dependencies • • • • • • SCP (base unit SCP211) hardware version must be 3.0 extended setting backup and downloading is not supported.0 (or greater). Restrictions • With SCP211 version 2.0a. Bugs • Incoming NNM messages through HDCL link break the management communication to SCP off. MartisDXX Manager support for this module is available in Release 9.2 Version 3.1 Enhancements and Fixed Bugs • Extended backup improvement.6 (or greater) and with SCP211 version 3.30.1 or higher.0 or higher.0 (or greater) with the SCZ280 version 7.Unit Software Version Dependencies in Discontinued Products 36. SCU (SCZ280) software version must be 7.3 Version 3. SXU-C (SXZ289) software version can be any version. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 444 10004_22 © 2008 Tellabs.0 or higher. Dependencies • • It requires the SCU210 version 2. 36. MartisDXX Manager supports new error codes in Release 9.30.

0 (or greater).30. Dependencies • • • It requires the SCU210 version 2.4 Version 3. No SCP backup space info support. 10004_22 © 2008 Tellabs.30.0 Enhancements and Fixed Bugs • Extended backup implemented. With SCP211 version 2. MartisDXX Manager support (downloading and new error codes) for this unit is available in Release 9.0 (or greater). No extended testing support (only one SCU/SCP combination can be fitted in same rack).0 extended setting backup and downloading is not supported.0 Dependencies • It requires the SCU210 version 2. Restrictions • • • • No extended setting backup support.Unit Software Version Dependencies in Discontinued Products 36.5 Version 2.0 (or greater) with the SCZ280 version 7. Restrictions • • No SCP backup space info supported (CRF ID 4000779).6 (or greater) and with SCP211 version 3. No SW downloading support. Bugs • No known bugs. 36.6 (or greater) and with SCP211 version 2.0. Bugs • No known bugs. Some units (for example AIU) cannot utilize SCP extended setting backup without backup space info support. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 445 .0 (or greater) with the SCZ280 version 7. No extended testing support (only one SCU/SCP combination can be fitted in same rack).

5 36...2 Version 8.31 SCU Unit: SCZ280 Unit Software The software SCZ280 is used on SCU units (whose base unit is SCU210).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. .31. Enhancements and Fixed Bugs (compared with version 8.6 Enhancements and Fixed Bugs (compared with version 8.5.54 This is a non-production version based on version 8.y of SCZ280 (where y=0. 2. (CR ID 200008860) Dependencies • See 1.3 Version 8. It supports the normal control unit functions for all versions of the base unit.3 Version 8.6 can be downloaded to SCUs having the version 8.1 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.). 36. 1. (CRF ID 4004049) Dependencies • See 1.31.5 Tellabs® 8100 Managed Access System Unit Software Version Dependencies 446 10004_22 © 2008 Tellabs.Unit Software Version Dependencies in Discontinued Products 36. The version 8.

10004_22 © 2008 Tellabs. SCU needs SCP215 with hardware version 1.2 kbit/s may indicate errors Inject error function produces a few errors. the test resource has the following limitations: • • At bit rates Nx3. SXU-A/B (SXZ282) software version can be any version. SXU-C (SXZ289) software version can be any version.0 or higher. Restrictions • No restrictions. MartisDXX Manager support for this unit is available in Release 8.5 Dependencies • • With SCU hardware version 1. • • • • • • • With SCU hardware version 3. SXU-V (SXZ630) software version must be 1.x.3 Version 8. With SCU hardware version 2.0 or higher.1 or higher. there are not the limitations mentioned above.1 or newer to make LABP connection between two SCUs work through X. SCP (SCZ281) software version must be 3.x.Unit Software Version Dependencies in Discontinued Products 36. the channel test or control channel support is not available.25 interface.0 kbit/s and Nx3.31.x. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 447 . Bugs • No known bugs.

31.Unit Software Version Dependencies in Discontinued Products 36. Inject error function produces a few errors. the channel test or control channel support is not available. the test resource has the following limitations: • • At bit rates Nx3. With SCU hardware version 2. there are not the limitations mentioned above.x. • • With SCU hardware version 3.4 Version 8. AIU) Tellabs® 8100 Managed Access System Unit Software Version Dependencies 448 10004_22 © 2008 Tellabs.2 kbit/s may indicate errors.x. there are not the limitations mentioned above.x.4 Dependencies • • With SCU hardware version 1. (CRF ID 4000906) SCU bus voltage alarm filtering in Tellabs 8140 midi node.1 or newer to make LABP connection between two SCUs work through X.25 interface.25 interface.x. (CRF ID 4001590) 36. the test resource has the following limitations: • • At bit rates Nx3.2 kbit/s may indicate errors Inject error function produces a few errors. • • With SCU hardware version 3.31. .0 kbit/s and Nx3. the channel test or control channel support is not available.g.x. With SCU hardware version 2.0 kbit/s and Nx3.1 or newer to make LABP connection between two SCUs work through X.5 Version 8. Restrictions • No support for extra backups for other units in the node (e. SCU needs SCP215 with hardware version 1.x. SCU needs SCP215 with hardware version 1.3 Dependencies • • With SCU hardware version 1. Restrictions • No restrictions Bugs • • • Maintenance event alarm (MEI) for active SXU switchover. (CRF ID 4001479) Support for PFU-A/PFU-B power off alarm in SCU/CCU.

there are not the limitations mentioned above. (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.0 kbit/s and Nx3.x. Bugs • • • • • Maintenance event alarm (MEI) for active SXU switchover. (CRF ID 4001590) SCU reported some GMHs falsely missing units due to VTP errors.x. the test resource has the following limitations: • • At bit rates Nx3. (CRF ID 4000906) SCU bus voltage alarm filtering in Tellabs 8140 midi node.g. (CRF ID 4001479) Support for PFU-A/PFU-B power off alarm in SCU/CCU.Unit Software Version Dependencies in Discontinued Products Bugs • • • Maintenance event alarm (MEI) for active SXU switchover. (CRF ID 2000170) NRP update for block extension in GMU.2 Dependencies • • With SCU hardware version 1. • With SCU hardware version 3. (CRF ID 2000202) 10004_22 © 2008 Tellabs. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 449 . The clock direction options for the synchronous SCC interface are not supported.2 kbit/s may indicate errors.x.6 Version 8. With SCU hardware version 2. (CRF ID 4001590) 36. the channel test or control channel support is not available. Restrictions • • • No support for extra backups for other units in the node (e. AIU) Communication through X.25 interface between two SCUs not supported. Inject error function produces a few errors.31.

there are not the limitations mentioned above. Bugs • • • • • • • Maintenance event alarm (MEI) for active SXU switchover. (CRF ID 2000170) NRP update for block extension in GMU. AIU) Communication through X. The optional security management for the SC interface is not supported.0 kbit/s and Nx3. (CRF ID 4001590) SCU reported some GMHs falsely missing units due to VTP errors. A bug in the G. Restrictions • • • • • No support for extra backups for other units in the node (e.1 Dependencies • • With SCU hardware version 1. The clock direction options for the synchronous SCC interface are not supported. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 450 10004_22 © 2008 Tellabs. the test resource has the following limitations: • • At bit rates Nx3.x. (CRF ID 2000202) Unexpected bit errors at rate 704 kbit/s in the channel loop test. .7 Version 8. (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. • With SCU hardware version 3.25 interface between two SCUs not supported The async channel loop test is not supported.g.31.821 statistics of the channel loop test support. Inject error function produces a few errors.2 kbit/s may indicate errors.x. With SCU hardware version 2.x. the channel test or control channel support is not available.Unit Software Version Dependencies in Discontinued Products 36.

The clock direction options for the synchronous SCC interface are not supported. The operation "Create inventory" cannot be used if the units have active connections. • With SCU hardware version 3. With SCU hardware version 2.0 Dependencies • • With SCU hardware version 1. Restrictions • • • • • No support for extra backups for other units in the node (e.Unit Software Version Dependencies in Discontinued Products 36.x.g.25 interface between two SCUs not supported The async channel loop test is not supported. (CRF ID 4001479) Support for PFU-A/PFU-B power off alarm in SCU/CCU. The optional security management for the SC interface is not supported.x. AIU) Communication through X.x. the test resource has the following limitations: • • At bit rates Nx3. A bug in the G. (CRF ID 4001590) SCU reported some GMHs falsely missing units due to VTP errors. 10004_22 © 2008 Tellabs. (CRF ID 4000906) SCU bus voltage alarm filtering in Tellabs 8140 midi node. the channel test or control channel support is not available. Tellabs® 8100 Managed Access System Unit Software Version Dependencies 451 .8 Version 8.0 kbit/s and Nx3.821 statistics of the channel loop test support. (CRF ID 2000202) Unexpected bit errors at rate 704 kbit/s in the channel loop test. (CRF ID 2000170) NRP update for block extension in GMU.31. there are not the limitations mentioned above. Bugs • • • • • • • • Maintenance event alarm (MEI) for active SXU switchover.2 kbit/s may indicate errors Inject error function produces a few errors.

AIU).g. A bug in the G. The operation "Create inventory" cannot be used if the units have active connections. These two communication problems are not likely to happen but they can cause a deadlock in the communication system SCU. The LLC3 protocol software can not handle one exceptional case associated with negative acknowledgement.x. (CRF ID 4001479) Support for PFU-A/PFU-B power off alarm in SCU/CCU.25 interface between two SCUs not supported. The trunks of a node can not be looped physically back to the node while management messages are sent through the trunk. the test resource has the following limitations: • • At bit rates Nx3. The clock direction options for the synchronous SCC interface are not supported. The async channel loop test is not supported. (CRF ID 4001590) SCU reported some GMHs falsely missing units due to VTP errors. The network layer protocol software can not handle all illegal routing elements. The asynchronous protocol software does not work correctly with heavy full-duplex traffic. Communication through X.9 Version 7. With SCU hardware version 2. there are not the limitations mentioned above.0 kbit/s and Nx3. (CRF ID 2000170) NRP update for block extension in GMU. • Tellabs® 8100 Managed Access System Unit Software Version Dependencies 452 10004_22 © 2008 Tellabs. The optional security management for the SC interface is not supported. (CRF ID 4000906) SCU bus voltage alarm filtering in Tellabs 8140 midi node.Unit Software Version Dependencies in Discontinued Products 36. Inject error function produces a few errors.2 kbit/s may indicate errors. • With SCU hardware version 3.31. Otherwise SCU has continuous troubles.x. Restrictions • • • • • No support for extra backups for other units in the node (e. .x. (CRF ID 2000202) Unexpected bit errors at rate 704 kbit/s in the channel loop test. Bugs • • • • • • • • • • • Maintenance event alarm (MEI) for active SXU switchover.6 Dependencies • • With SCU hardware version 1. the channel test or control channel support is not available.821 statistics of the channel loop test support.

Does not support the alarm interface module SCL415.g. The trunks of a node can not be looped physically back to the node while management messages are sent through the trunk. With SCU hardware version 2. The LLC3 protocol software can not handle one exceptional case associated with negative acknowledgement. the channel test or control channel support is not available. Bugs • • • • • • • • • • • • Maintenance event alarm (MEI) for active SXU switchover. Otherwise SCU has continuous troubles. The network layer protocol software can not handle all illegal routing elements. The clock direction options for the synchronous SCC interface are not supported. (CRF ID 4001479) Support for PFU-A/PFU-B power off alarm in SCU/CCU. The asynchronous protocol software does not work correctly with heavy full-duplex traffic. Does not support the correct control channel port handling for SCP211. The operation "Create inventory" cannot be used if the units have active connections.5 Dependencies • • With SCU hardware version 1.0 kbit/s and Nx3. The optional security management for the SC interface is not supported. • With SCU hardware version 3. (CR