Atm RM 1354

Alcatel-Lucent
1354 BM-ATM | Release 7.1

Operator's Handbook
3AG86577ABAATQZZA
July 2006
Issue 3
All rights reserved. Passing on and copying of this
document, use and communication of its contents
not permitted without written authorisation from
Alcatel
3AG 86577 ABAA Ed3

HANDBOOK
OPERATOR’S
ATM boards in OMSN

Broadband Manager of
1 3 5 4 BM ATM R e l . 7 . 1
Ed 3: 2006-07-25
1/725
Alcatel
3AG 86577 ABAA Ed3

2/725
Contents
1 GENERALITIES................................................................................................................................. 24
1.1 OVERVIEW .................................................................................................................................... 25
1.1.1 Management layers .................................................................................................................. 26
1.1.2 Positioning............................................................................................................................... 27
1.1.3 The network from various points of view................................................................................... 28
1.2 INTERFACES .................................................................................................................................. 31
Alcatel
1.2.1 1354 BM 1353 NM interface.................................................................................................. 32

1.2.2 1354 BM 1354 RM interface.................................................................................................. 32
1.3 ATM BASIC CONCEPTS .................................................................................................................. 33
1.3.1 Cell.......................................................................................................................................... 33
1.3.2 Transmission path, VP and VC................................................................................................. 33
1.3.3 Inverse Multiplexing ATM (IMA).............................................................................................. 34
1.3.4 ATM connection....................................................................................................................... 35
1.3.5 Quality of service ..................................................................................................................... 36
1.4 FUNCTIONAL DOMAINS .................................................................................................................. 38
1.4.1 Network construction ............................................................................................................... 38
1.4.1.1 Sub-network.................................................................................................................................. 39
1.4.1.2 ATM NE and ENE ........................................................................................................................ 40
1.4.1.3 Transmission path, IMA transmission path (IMA group), IMA link................................................. 40
1.4.1.4 ATM termination and ETP............................................................................................................. 41
1.4.1.5 Transmission path / IMA transmission path partition ...................................................................... 44
1.4.2 Network management............................................................................................................... 47
1.4.2.1 Hard PVC ..................................................................................................................................... 48
1.4.2.2 Soft PVC....................................................................................................................................... 48
1.4.2.3 Routing management..................................................................................................................... 50
1.4.2.4 UPC/NPC management ................................................................................................................. 51
1.4.2.5 Output shaping.............................................................................................................................. 51
1.4.2.6 Point-to-multi-points PVC management ......................................................................................... 52
1.4.2.7 Overbooking management ............................................................................................................. 56
1.4.3 Maintenance management........................................................................................................ 58
1.4.3.1 Fault management ......................................................................................................................... 58
1.4.3.2 OAM management ........................................................................................................................ 64
1.4.4 Performance management........................................................................................................ 66
1.4.5 Administration management ..................................................................................................... 67
1.4.5.1 PNNI management ........................................................................................................................ 68
1.4.5.2 ATM Traffic management ............................................................................................................. 69
1.4.5.3 VN management............................................................................................................................ 69
1.4.6 Utilities.................................................................................................................................... 70
1.4.6.1 Plug & play................................................................................................................................... 70
1.4.6.2 NE audit........................................................................................................................................ 71
1.4.6.3 NE alignment ................................................................................................................................ 71
1.4.6.4 NE force alignment ....................................................................................................................... 72
1.4.7 System management ................................................................................................................. 73
1.4.7.1 Operator profile management......................................................................................................... 73
1.5 SYSTEM ENVIRONMENT ................................................................................................................. 75
1.5.1 General environment................................................................................................................ 75
1.5.2 User interface .......................................................................................................................... 75
2 USER INTERFACE OVERVIEW...................................................................................................... 76
2.1 GENERALITIES .............................................................................................................................. 77
2.1.1 Vocabulary used in the user interface ....................................................................................... 78
2.1.2 User interface windows ............................................................................................................ 79
2.1.2.1 Main view..................................................................................................................................... 80
2.1.2.2 Graphical views............................................................................................................................. 81
2.1.2.3 List windows................................................................................................................................. 83
2.1.2.4 Data display windows.................................................................................................................... 86
2.1.2.5 Data acquisition windows .............................................................................................................. 87
2.1.2.6 Dialog and message boxes ............................................................................................................. 88
2.1.3 Window management ............................................................................................................... 90
2.1.4 Selection rules.......................................................................................................................... 91
2.1.5 String character agreement ...................................................................................................... 92
3AG 86577 ABAA Ed3 3/725

2.1.6 Sensitive help ........................................................................................................................... 92
2.1.7 Buttons .................................................................................................................................... 95

2.1.7.1 Option buttons............................................................................................................................... 95

2.1.7.2 Radio buttons ................................................................................................................................ 95
2.2 GETTING STARTED ........................................................................................................................ 96
2.2.1 Starting the 1354 BM GUI........................................................................................................ 96
2.2.1.1 On an HP workstation.................................................................................................................... 96
2.2.1.2 On a PC ........................................................................................................................................ 98
2.2.2 Starting the Command Line Interface (CLI) ............................................................................ 100
Alcatel
2.2.3 Starting the Alarm Surveillance GUI ...................................................................................... 101

2.2.4 Starting the performance monitoring GUI .............................................................................. 103
2.3 ADMINISTERING THE 1354 BM .................................................................................................... 114
2.3.1 List of EML-IM ...................................................................................................................... 115
2.3.1.1 Add an EML-IM ......................................................................................................................... 116
2.3.1.2 Remove an EML-IM ................................................................................................................... 117
2.3.2 Set the 1354 BM configuration parameters............................................................................. 118
2.3.3 Display 1354 BM log file........................................................................................................ 120
2.4 MAIN VIEW ................................................................................................................................. 122
2.4.1 Using the tree......................................................................................................................... 124
2.5 ACCESSING THE FUNCTIONS ......................................................................................................... 128
2.5.1 From the menus ..................................................................................................................... 128
2.5.2 From the icons ....................................................................................................................... 129
2.5.3 General toolbar ..................................................................................................................... 130
2.5.3.1 Contextual toolbar....................................................................................................................... 131
2.5.4 From the contextual menu ...................................................................................................... 132
2.5.5 From the tree ......................................................................................................................... 133
2.5.6 Conventions ........................................................................................................................... 133
2.6 WINDOW MENU ........................................................................................................................... 134
2.6.1 Arrange the windows.............................................................................................................. 134
2.6.2 Choose the active window ...................................................................................................... 141
2.7 MAIN MENU ................................................................................................................................ 142
2.8 VIEW MENU ................................................................................................................................ 143
2.8.1 Select a background map........................................................................................................ 144
2.8.2 Save a sub-network or global view.......................................................................................... 145
2.8.3 Network representation .......................................................................................................... 146
2.8.4 Selection rules in a graphical view ......................................................................................... 148
2.8.5 Sub-network views ................................................................................................................. 148
2.8.5.1 Sub-network views in transmission path domain........................................................................... 149
2.8.5.2 Sub-network views in VP domain ................................................................................................ 151
2.8.5.3 Sub-network views in VC domain................................................................................................ 153
2.8.5.4 Open a sub-network..................................................................................................................... 155
2.8.5.5 Open a grouped link .................................................................................................................... 156
2.8.5.6 Navigate through an off-page connector ....................................................................................... 157
2.8.6 Global views .......................................................................................................................... 158
2.8.6.1 Global views in transmission path domain.................................................................................... 159
2.8.6.2 Global views in VP domain ......................................................................................................... 160
2.8.6.3 Global views in VC domain......................................................................................................... 161
2.8.6.4 Open / close a sub-network .......................................................................................................... 162
2.9 HELP MENU ................................................................................................................................. 164
2.9.1 General help .......................................................................................................................... 165
2.9.2 Contextual help...................................................................................................................... 168
3 NETWORK CONSTRUCTION........................................................................................................ 170
3.1 MANAGING SUB-NETWORKS ........................................................................................................ 172
3.1.1 Display the sub-network list ................................................................................................... 173
3.1.2 Create a sub-network ............................................................................................................. 175
3.1.3 Modify a sub-network............................................................................................................. 177
3.1.4 Delete a sub-network.............................................................................................................. 178
3.1.5 Get the sub-networks properties ............................................................................................. 179
3.2 MANAGING NES.......................................................................................................................... 180
3.2.1 Display the NE list ................................................................................................................. 181
3.2.2 Define a NE ........................................................................................................................... 184
3AG 86577 ABAA Ed3 4/725

3.2.2.1 Display the available NE list........................................................................................................ 184
3.2.2.2 Add a NE.................................................................................................................................... 186

3.2.3 Modify a NE........................................................................................................................... 188

3.2.4 Delete a NE ........................................................................................................................... 189
3.2.5 Upload the NE terminations ................................................................................................... 190
3.2.6 Synchronize the NE terminations ............................................................................................ 191
3.2.7 Acquit the NE LAC state......................................................................................................... 192
3.2.8 Display the termination list .................................................................................................... 193
3.2.9 Audit the NE terminations ...................................................................................................... 195
Alcatel
3.2.10 Configure a termination..................................................................................................... 197

3.2.11 De-configure a termination................................................................................................ 198
3.2.12 Get the NE properties ........................................................................................................ 199
3.2.13 Show equipment view......................................................................................................... 200
3.3 MANAGING ENES ....................................................................................................................... 201
3.3.1 Display the ENE list ............................................................................................................... 202
3.3.2 Create an ENE....................................................................................................................... 204
3.3.3 Modify an ENE ...................................................................................................................... 206
3.3.4 Delete an ENE ....................................................................................................................... 207
3.3.5 Display the ETP list ............................................................................................................... 208
3.3.6 Create ETPs........................................................................................................................... 210
3.3.7 Delete an ETP........................................................................................................................ 211
3.3.8 Assign NAD Label to ETPs..................................................................................................... 213
3.3.9 Get the ENE properties .......................................................................................................... 214
3.4 MANAGING TRANSMISSION PATHS / IMA TRANSMISSION PATHS .................................................... 215
3.4.1 Display the transmission paths list.......................................................................................... 217
3.4.2 Create a transmission path..................................................................................................... 221
3.4.3 Display the IMA link list......................................................................................................... 227
3.4.3.1 Add an IMA link to an IMA transmission path ............................................................................. 229
3.4.3.2 Remove an IMA link from an IMA transmission path................................................................... 231
3.4.3.3 Finalize an IMA link ................................................................................................................... 233
3.4.3.4 Display the IMA link extremities ................................................................................................. 234
3.4.3.5 Display the IMA link properties................................................................................................... 235
3.4.3.6 Display the fault localization........................................................................................................ 236
3.4.4 Finalize a transmission path................................................................................................... 238
3.4.5 Finalize an IMA transmission path ......................................................................................... 239
3.4.6 Modify a transmission path .................................................................................................... 240
3.4.7 Delete a transmission path ..................................................................................................... 242
3.4.8 Lock a transmission path........................................................................................................ 244
3.4.9 Unlock a transmission path .................................................................................................... 246
3.4.10 Configure a transmission path ........................................................................................... 247
3.4.11 Configure NIM for a transmission path.............................................................................. 249
3.4.12 Partition a transmission path............................................................................................. 250
3.4.12.1 Explanation about the transmission path partitioning .................................................................... 253
3.4.13 Display the transmission path extremities........................................................................... 255
3.4.14 Display the transmission path bandwidth load ................................................................... 257
3.4.14.1 For hard routing service............................................................................................................... 258
3.4.14.2 For soft routing service ................................................................................................................ 260
3.4.15 Display the fault localization ............................................................................................. 261
3.4.16 Display the transmission path properties............................................................................ 263
4 NETWORK MANAGEMENT.......................................................................................................... 265
4.1 MANAGING HARD PVPCS ............................................................................................................ 267
4.1.1 Display the hard PVPC list..................................................................................................... 270
4.1.2 Define a hard PVPC............................................................................................................... 275
4.1.3 Modify a hard PVPC.............................................................................................................. 280
4.1.4 Delete a hard PVPC............................................................................................................... 282
4.1.5 Allocate a hard PVPC ............................................................................................................ 283
4.1.6 De-allocate a hard PVPC....................................................................................................... 287
4.1.7 Implement a hard PVPC......................................................................................................... 289
4.1.8 De-implement a hard PVPC ................................................................................................... 291
4.1.9 Commission a hard PVPC...................................................................................................... 293
4.1.10 De-commission a hard PVPC............................................................................................. 294
3AG 86577 ABAA Ed3 5/725

4.1.11 Lock a hard PVPC............................................................................................................. 295
4.1.12 Unlock a hard PVPC ......................................................................................................... 296

4.1.13 Assign NAD Label to a hard PVPC .................................................................................... 297

4.1.14 Activate the output shaping on a hard PVPC...................................................................... 298
4.1.15 Deactivate the output shaping on a hard PVPC.................................................................. 300
4.1.16 Activate UPC / NPC on a hard PVPC ................................................................................ 301
4.1.17 Deactivate UPC / NPC on a hard PVPC ............................................................................ 302
4.1.18 Activate CC on a hard PVPC ............................................................................................. 303
Alcatel
4.1.19 Deactivate CC on a hard PVPC ......................................................................................... 305

4.1.20 Modify the bandwidth of a hard PVPC ............................................................................... 307
4.1.21 Display the hard PVPC extremities.................................................................................... 310
4.1.22 Display the hard PVPC properties ..................................................................................... 312
4.1.23 Display the hard PVPC bandwidth load............................................................................. 314
4.1.24 Display the hard PVPC traffic properties........................................................................... 317
4.1.25 Display the hard PVPC routing properties......................................................................... 318
4.1.26 Display the hard PVPC graphical view.............................................................................. 319
4.1.27 Display the fault localization on hard PVPC ...................................................................... 321
4.1.28 Display the hard PVPC NE NIM list .................................................................................. 323
4.1.28.1 Configure / de-configure the hard PVPC NE NIMs....................................................................... 325
4.1.29 Display hard PVPC NIM CC list........................................................................................ 327
4.1.29.1 Activate NIM CC ........................................................................................................................ 329
4.1.29.2 Deactivate NIM CC..................................................................................................................... 330
4.1.30 Display the hard PVPC Constraints list ............................................................................. 331
4.1.30.1 Add a constraint to a hard PVPC.................................................................................................. 333
4.1.30.2 Delete a constraint from a hard PVPC .......................................................................................... 335
4.2 MANAGING HARD PVPC LEGS .................................................................................................... 336
4.2.1 Display the hard PVPC Leg list.............................................................................................. 339
4.2.2 Show the associated Legs ....................................................................................................... 342
4.2.3 Define a hard PVPC Leg........................................................................................................ 343
4.2.4 Modify a hard PVPC Leg ....................................................................................................... 345
4.2.5 Delete a hard PVPC Leg ........................................................................................................ 346
4.2.6 Allocate a hard PVPC Leg ..................................................................................................... 347
4.2.7 De-allocate a hard PVPC Leg ................................................................................................ 350
4.2.8 Implement a hard PVPC Leg.................................................................................................. 351
4.2.9 De-implement a hard PVPC Leg............................................................................................. 352
4.2.10 Commission a hard PVPC Leg........................................................................................... 353
4.2.11 De-commission a hard PVPC Leg...................................................................................... 354
4.2.12 Display the hard PVPC Leg extremities ............................................................................. 355
4.2.13 Display the hard PVPC Leg properties .............................................................................. 356
4.2.14 Display the hard PVPC Leg routing properties .................................................................. 357
4.2.15 Display the hard PVPC Leg graphical view ....................................................................... 358
4.2.16 Display the hard PVPC Leg NE NIM list............................................................................ 360
4.2.16.1 Configure / de-configure the hard PVPC Leg NE NIMs ................................................................ 362
4.2.17 Display the hard PVPC Leg Constraints list....................................................................... 364
4.2.17.1 Add a constraint to a hard PVPC Leg ........................................................................................... 366
4.2.17.2 Delete a constraint from a hard PVPC Leg ................................................................................... 368
4.3 MANAGING HARD PVCCS ........................................................................................................... 369
4.3.1 Display the hard PVCC list .................................................................................................... 372
4.3.2 Define a hard PVCC .............................................................................................................. 376
4.3.3 Modify a hard PVCC.............................................................................................................. 382
4.3.4 Delete a hard PVCC............................................................................................................... 384
4.3.5 Allocate a hard PVCC............................................................................................................ 385
4.3.6 De-allocate a hard PVCC....................................................................................................... 389
4.3.7 Implement a hard PVCC ........................................................................................................ 390
4.3.8 De-implement a hard PVCC................................................................................................... 392
4.3.9 Commission a hard PVCC...................................................................................................... 394
4.3.10 De-commission a hard PVCC ............................................................................................ 395
4.3.11 Assign NAD Label to a hard PVCC.................................................................................... 396
4.3.12 Activate UPC / NPC on a hard PVCC................................................................................ 397
4.3.13 Deactivate UPC / NPC on a hard PVCC............................................................................ 398
4.3.14 Activate CC on a hard PVCC............................................................................................. 399
3AG 86577 ABAA Ed3 6/725

4.3.15 Deactivate CC on a hard PVCC......................................................................................... 401
4.3.16 Modify the bandwidth of a hard PVCC............................................................................... 403

4.3.17 Display the hard PVCC extremities.................................................................................... 406

4.3.18 Display the hard PVCC properties..................................................................................... 408
4.3.19 Display the hard PVCC traffic properties........................................................................... 409
4.3.20 Display the hard PVCC routing properties......................................................................... 410
4.3.21 Display the hard PVCC graphical view.............................................................................. 411
4.3.22 Display the fault localization on a hard PVCC ................................................................... 413
Alcatel
4.3.23 Display hard PVCC NE NIM list........................................................................................ 415

4.3.23.1 Configure / de-configure the hard PVCC NE NIMs ...................................................................... 417
4.3.24 Display hard PVCC NIM CC list ....................................................................................... 419
4.3.24.1 Activate NIM CC ........................................................................................................................ 421
4.3.24.2 Deactivate NIM CC..................................................................................................................... 422
4.3.25 Display hard PVCC Constraints list................................................................................... 423
4.3.25.1 Add a constraint to a hard PVCC ................................................................................................. 425
4.3.25.2 Delete a constraint from a hard PVCC.......................................................................................... 427
4.4 MANAGING HARD PVCC LEGS .................................................................................................... 428
4.4.1 Display the hard PVCC Leg list.............................................................................................. 431
4.4.2 Show associated Legs............................................................................................................. 434
4.4.3 Define a hard PVCC Leg........................................................................................................ 435
4.4.4 Modify a hard PVCC Leg ....................................................................................................... 437
4.4.5 Delete a hard PVCC Leg........................................................................................................ 438
4.4.6 Allocate a hard PVCC Leg ..................................................................................................... 439
4.4.7 De-allocate a hard PVCC Leg................................................................................................ 442
4.4.8 Implement a hard PVCC Leg.................................................................................................. 443
4.4.9 De-implement a hard PVCC Leg ............................................................................................ 445
4.4.10 Commission a hard PVCC Leg........................................................................................... 447
4.4.11 De-commission a hard PVCC Leg...................................................................................... 448
4.4.12 Display the hard PVCC Leg extremities ............................................................................. 449
4.4.13 Display the hard PVCC Leg properties .............................................................................. 450
4.4.14 Display the hard PVCC Leg routing properties .................................................................. 451
4.4.15 Display the hard PVCC Leg graphical view ....................................................................... 452
4.4.16 Display the hard PVCC Leg NE NIM list ........................................................................... 454
4.4.16.1 Configure the hard PVCC Leg NE NIMs...................................................................................... 456
4.4.17 Display the hard PVCC Leg Constraint list........................................................................ 458
4.4.17.1 Add a constraint to a hard PVCC Leg........................................................................................... 460
4.4.17.2 Delete a constraint from a hard PVCC Leg ................................................................................... 462
4.5 MANAGING SOFT PVPCS ............................................................................................................. 463
4.5.1 Display the soft PVPC description list .................................................................................... 465
4.5.2 Define a soft PVPC ................................................................................................................ 468
4.5.3 Modify a soft PVPC................................................................................................................ 472
4.5.4 Delete a soft PVPC ................................................................................................................ 473
4.5.5 Set-up a soft PVPC................................................................................................................. 474
4.5.6 Release a soft PVPC............................................................................................................... 476
4.5.7 Display the soft PVPC characteristic list ................................................................................ 477
4.5.8 Activate the output shaping on a soft PVPC ............................................................................ 480
4.5.9 Deactivate the output shaping on a soft PVPC ........................................................................ 482
4.5.10 Activate UPC / NPC on a soft PVPC.................................................................................. 483
4.5.11 Deactivate UPC / NPC on a soft PVPC.............................................................................. 484
4.5.12 Display the soft PVPC extremities...................................................................................... 485
4.5.13 Display the soft PVPC properties....................................................................................... 486
4.5.14 Display the soft PVPC bandwidth load............................................................................... 487
4.5.15 Display the soft PVPC traffic properties............................................................................. 489
4.5.16 Display the soft PVPC routing properties........................................................................... 490
4.5.17 Activate/deactivate the CC on a soft PVPC (change CC direction) ..................................... 490
4.5.18 Display the soft PVPC graphical view................................................................................ 490
4.6 MANAGING SOFT PVCCS............................................................................................................. 491
4.6.1 Display the soft PVCC description list.................................................................................... 493
4.6.2 Define a soft PVCC ................................................................................................................ 496
4.6.3 Modify a soft PVCC ............................................................................................................... 500
4.6.4 Delete a soft PVCC ................................................................................................................ 501
3AG 86577 ABAA Ed3 7/725

4.6.5 Set-up a soft PVCC ................................................................................................................ 502
4.6.6 Release a soft PVCC .............................................................................................................. 504

4.6.7 Display the soft PVCC characteristic list................................................................................ 505

4.6.8 Activate UPC / NPC on a soft PVCC ...................................................................................... 508
4.6.9 Deactivate UPC / NPC on a soft PVCC .................................................................................. 509
4.6.10 Display the soft PVCC extremities ..................................................................................... 510
4.6.11 Display the soft PVCC properties....................................................................................... 511
4.6.12 Display the soft PVCC traffic properties ............................................................................ 512
Alcatel
4.6.13 Display the soft PVCC routing properties .......................................................................... 513

4.6.14 Activate/deactivate the CC on a soft PVCC (change CC direction) ..................................... 513
4.6.15 Display the soft PVCC graphical view ............................................................................... 513
5 MAINTENANCE MANAGEMENT................................................................................................. 515
6 PERFORMANCE MANAGEMENT ................................................................................................ 520

6.1 GENERALITIES ............................................................................................................................ 521
6.1.1 Non-OAM PM management.................................................................................................... 522
6.1.2 OAM PM management ........................................................................................................... 523
6.2 MANAGING PM MEASURES ......................................................................................................... 524
6.2.1 Display the PM Measure list .................................................................................................. 526
6.2.2 Create a PM Measure ............................................................................................................ 529
6.2.3 Modify a PM Measure............................................................................................................ 531
6.2.4 Delete a PM Measure............................................................................................................. 533
6.2.5 Associate a PM Measure to a Periodic Report Profile............................................................. 534
6.2.6 Dissociate a PM Measure from a Periodic Report Profile....................................................... 536
6.2.7 Activate a PM Measure .......................................................................................................... 538
6.2.8 De-activate a PM Measure..................................................................................................... 540
6.2.9 Force a data collection........................................................................................................... 542
6.2.10 Display the PM Measure properties................................................................................... 543
6.2.11 Show performance data ..................................................................................................... 544
6.2.12 Display the PM Transport list............................................................................................ 545
6.2.12.1 Associate a PM Transport to a PM Measure ................................................................................. 547
6.2.12.2 Dissociate a PM Transport........................................................................................................... 553
6.2.13 Display the PP List............................................................................................................ 554
6.2.13.1 Associate a PP to a PM transport.................................................................................................. 557
6.2.13.2 Dissociate a PP from a PM transport ............................................................................................ 558
6.3 MANAGING PERIODIC REPORT PROFILES ...................................................................................... 559
6.3.1 Display the Periodic Report Profile list .................................................................................. 560
6.3.2 Create a Periodic Report Profile ............................................................................................ 562
6.3.3 Modify a Periodic Report Profile............................................................................................ 565
6.3.4 Delete a Periodic Report Profile............................................................................................. 567
6.3.5 Display the Periodic Report Profile properties ....................................................................... 568
6.4 MANAGING TCA PROFILES ......................................................................................................... 570
6.4.1 Display the TCA Profile list.................................................................................................... 571
6.4.2 Display the TCA Profile properties......................................................................................... 572
7 ADMINISTRATION MANAGEMENT............................................................................................ 574
7.1 PNNI MANAGEMENT ................................................................................................................... 575
7.1.1 Display the NE list for administration..................................................................................... 576
7.1.2 Observe a NE......................................................................................................................... 578
7.1.3 Configure the PNNI node ATM address.................................................................................. 579
7.1.4 Activate a PNNI node............................................................................................................. 580
7.1.5 Deactivate a PNNI node......................................................................................................... 581
7.1.6 Display the termination list for administration........................................................................ 582
7.1.7 Configure the PNNI interface ATM address............................................................................ 584
7.2 ATM TRAFFIC MANAGEMENT ...................................................................................................... 586
7.2.1 Traffic descriptor management............................................................................................... 586
7.2.1.1 Display the traffic descriptor list .................................................................................................. 588
7.2.1.2 Create a traffic descriptor............................................................................................................. 590
7.2.1.3 Create a traffic descriptor from another one.................................................................................. 593
7.2.1.4 Modify a traffic descriptor ........................................................................................................... 594
3AG 86577 ABAA Ed3 8/725

7.2.1.5 Delete a traffic descriptor............................................................................................................. 595
7.2.2 Traffic profile management .................................................................................................... 595

7.2.2.1 Traffic profile list ........................................................................................................................ 597

7.2.2.2 Create a traffic profile.................................................................................................................. 599
7.2.2.3 Create a traffic profile from another one....................................................................................... 601
7.2.2.4 Modify a traffic profile ................................................................................................................ 602
7.2.2.5 Delete a traffic profile.................................................................................................................. 603
7.2.2.6 Display the traffic profile properties............................................................................................. 604
7.3 OPERATOR PROFILE MANAGEMENT .............................................................................................. 605
Alcatel
8 UTILITIES ........................................................................................................................................ 609

8.1 PLUG & PLAY .............................................................................................................................. 610
8.1.1 Start the plug & play .............................................................................................................. 613
8.1.2 Upload the SDH transmission Paths....................................................................................... 617
8.1.3 Discover the transmission path characteristics ....................................................................... 618
8.1.4 Discover the traffic descriptors............................................................................................... 620
8.1.5 Discover the VP connections .................................................................................................. 621
8.1.6 Recover the hard PVPCs ........................................................................................................ 623
8.1.7 Discover the VC connections.................................................................................................. 625
8.1.8 Recover the hard PVCCs........................................................................................................ 627
8.1.9 Clean-up the terminations ...................................................................................................... 628
8.1.10 Clean-up the connections................................................................................................... 628
8.1.11 End the plug & play........................................................................................................... 629
8.1.12 Open the NE list ................................................................................................................ 631
8.1.13 What to do in case of warnings during the plug & play....................................................... 632
8.2 TIME SCHEDULING....................................................................................................................... 633
8.3 PNNI AUDIT ............................................................................................................................... 633
8.4 NE AUDIT / ALIGNMENT TOOL ..................................................................................................... 634
8.4.1 Start the NE audit / alignment ................................................................................................ 635
8.4.2 NE audit tool.......................................................................................................................... 636
8.4.2.1 Audit NE(s)................................................................................................................................. 639
8.4.3 NE alignment tool .................................................................................................................. 641
8.4.3.1 Display the file list ...................................................................................................................... 642
8.4.3.1.1 Display an audit file ................................................................................................... 643
8.4.3.1.2 Align NE(s) from a directory or from an audit file ........................................ 644
8.4.3.1.3 Force alignment NE(s) from a directory or from an audit file .................. 646
8.4.4 End the audit / alignment ....................................................................................................... 650
9 GLOSSARY....................................................................................................................................... 651
10 APPENDIX ....................................................................................................................................... 699

10.1 LIMITS ........................................................................................................................................ 700
10.2 COMMAND LINE INTERFACE SYNTAX ........................................................................................... 703
10.3 USER PROFILE MANAGEMENT ..................................................................................................... 716
3AG 86577 ABAA Ed3 9/725

Table of figures
Figure 1-1 1354 BM positioning ..................................................................................................................... 27

Figure 1-2 Real ATM/SDH Network................................................................................................................ 28
Figure 1-3 SDH-NML point of view................................................................................................................. 29
Figure 1-4 ATM-NML point of view ................................................................................................................ 30
Figure 1-5 1354 BM interfaces........................................................................................................................ 31
Figure 1-6 Transmission hierarchy ................................................................................................................. 33
Alcatel
Figure 1-7 IMA hierarchy ............................................................................................................................... 34

Figure 1-8 IMA bandwidth optimization.......................................................................................................... 34
Figure 1-9 Usage of the different qualities of service ....................................................................................... 37
Figure 1-10 Sub-network levels....................................................................................................................... 39
Figure 1-11 ATM termination (TP/VP_A)........................................................................................................ 42
Figure 1-12 ATM termination (TP/IMA_A)...................................................................................................... 42
Figure 1-13 Termination on ENE.................................................................................................................... 43
Figure 1-14 Transmission path partition ......................................................................................................... 46
Figure 1-15 PVC point-to-point representation ............................................................................................... 47
Figure 1-16 Transit soft PVC .......................................................................................................................... 48
Figure 1-17 Infrastructure soft PVC................................................................................................................ 49
Figure 1-18 Soft PVC with called endpoint on ATM NE................................................................................... 49
Figure 1-19 Soft PVC with called endpoint on ENE......................................................................................... 50
Figure 1-20 Shaping protection mode : Grooming........................................................................................... 51
Figure 1-21 Shaping protection mode : Edge................................................................................................... 51
Figure 1-22 Shaping protection mode : Grooming + Edge............................................................................... 52
Figure 1-23 PVPC point-to-multipoints presentation....................................................................................... 54
Figure 1-24 PVCC point-to-multipoints presentation....................................................................................... 55
Figure 1-25 Example of Trail Signal Fail alarm and Alarm Indication Signal alarm........................................ 60
Figure 1-26 Example of Trail Signal Fail alarm .............................................................................................. 60
Figure 1-27 Example of Trail Signal Fail, Alarm Indication Signal and Remote Defect Indication alarm ......... 61
Figure 1-28 NIM points presentation............................................................................................................... 63
Figure 1-29 Continuity Check service activation on a bi-directional segment................................................... 65
Figure 1-30 PNNI peer group representation .................................................................................................. 68
Figure 2-1 Example of a main view ................................................................................................................. 80
Figure 2-2 Example of a graphical view.......................................................................................................... 81
Figure 2-3 Example of a list window ............................................................................................................... 83
Figure 2-4 Example of descending order......................................................................................................... 84
Figure 2-5 Example of ascending order........................................................................................................... 84
Figure 2-6 Example of creation order ............................................................................................................. 85
Figure 2-7 Example of a data display window ................................................................................................. 86
Figure 2-8 Example of a data acquisition window ........................................................................................... 87
Figure 2-9 Example of a confirmation box....................................................................................................... 88
Figure 2-10 Example of a confirmation box for a multi-selection..................................................................... 88
Figure 2-11 Example of a message box ........................................................................................................... 89
Figure 2-12 Example of a message box for several selections .......................................................................... 89
Figure 2-13 System bar................................................................................................................................... 90
Figure 2-14 Example of a field providing sensitive help................................................................................... 93
Figure 2-15 Example of a sensitive help in action............................................................................................ 93
Figure 2-16 Example of an option button ........................................................................................................ 95
Figure 2-17 Example of radio buttons ............................................................................................................. 95
Figure 2-18 Front panel on HP....................................................................................................................... 96
Figure 2-19 TMN-OSs Management main view ............................................................................................... 97
Figure 2-20 Confirmation box (on HP)............................................................................................................ 98
Figure 2-21 User Authentication window (on PC) ........................................................................................... 98
Figure 2-22 Confirmation box (on PC)............................................................................................................ 99
Figure 2-23 Command Line Interface window............................................................................................... 100
Figure 2-24 AS Current Alarm Counter Summary window............................................................................. 101
Figure 2-25 As Current Alarm Sublist window: Network Element .................................................................. 102
Figure 2-26 PM Report Request Control window .......................................................................................... 105
Figure 2-27 PM Report Request Control window (with PM Measures) .......................................................... 107
Figure 2-28 PM Report Request Control window (with two Performance Entities selected) 108
3AG 86577 ABAA Ed3 10/725

Figure 2-29 Performance Counter Graphical window ................................................................................... 112
Figure 2-30 Performance Counter Tabular window....................................................................................... 113

Figure 2-31 EML-IM List window................................................................................................................. 115

Figure 2-32 Add one EML-IM window .......................................................................................................... 116
Figure 2-33 Confirmation box to remove an EML-IM.................................................................................... 117
Figure 2-34 1354 BM Parameters Definition window.................................................................................... 118
Figure 2-35 Log Management window .......................................................................................................... 120
Figure 2-36 1354 BM Log File window (from Log Management window) ...................................................... 120
Alcatel
Figure 2-37 1354 BM Log File window......................................................................................................... 121

Figure 2-38 Main view.................................................................................................................................. 122
Figure 2-39 Tree structure ............................................................................................................................ 126
Figure 2-40 Example of a contextual toolbar for a list window ...................................................................... 132
Figure 2-41 Example of a contextual menu.................................................................................................... 132
Figure 2-42 Example of a Window menu ....................................................................................................... 134
Figure 2-43 Example of a desktop before arranging the windows .................................................................. 135
Figure 2-44 Desktop with horizontal tile arrangement................................................................................... 136
Figure 2-45 Desktop with mostly horizontal tile arrangement ........................................................................ 137
Figure 2-46 Desktop with vertical tile arrangement....................................................................................... 138
Figure 2-47 Desktop with mostly vertical tile arrangement ............................................................................ 139
Figure 2-48 Desktop with cascade arrangement............................................................................................ 140
Figure 2-49 Select a New Map for Background window................................................................................. 144
Figure 2-50 Transmission path domain sub-network view.............................................................................. 149
Figure 2-51 VP domain sub-network view ..................................................................................................... 151
Figure 2-52 VC domain sub-network view..................................................................................................... 153
Figure 2-53 Example of a sub-network view showing the content of a sub-network ........................................ 155
Figure 2-54 Example of a link view ............................................................................................................... 156
Figure 2-55 Transmission path domain global view....................................................................................... 159
Figure 2-56 VP domain global view .............................................................................................................. 160
Figure 2-57 VC domain global view.............................................................................................................. 161
Figure 2-58 Example of a closed sub-network ............................................................................................... 162
Figure 2-59 Example of an opened sub-network ............................................................................................ 163
Figure 2-60 Home page of the on line help.................................................................................................... 165
Figure 2-61 Search page of the on line help .................................................................................................. 166
Figure 2-62 Glossary page of the on line help ............................................................................................... 167
Figure 2-63 Example of an About 1354 BM dialog box.................................................................................. 168
Figure 3-1 Network construction chain ......................................................................................................... 171
Figure 3-2 Sub-network management chain................................................................................................... 172
Figure 3-3 Sub-network List window............................................................................................................. 173
Figure 3-4 Sub-network Search window ........................................................................................................ 174
Figure 3-5 Sub-network Creation window ..................................................................................................... 175
Figure 3-6 Sub-network Modification window ............................................................................................... 177
Figure 3-7 Confirmation box for deleting several sub-networks ..................................................................... 178
Figure 3-8 Sub-network Properties window................................................................................................... 179
Figure 3-9 NE management chain................................................................................................................. 180
Figure 3-10 NE / ENE List window NE panel ............................................................................................. 181
Figure 3-11 NE Search window..................................................................................................................... 182
Figure 3-12 Available NE List window.......................................................................................................... 184
Figure 3-13 Available NE Search window ..................................................................................................... 185
Figure 3-14 NE Adding window for one NE................................................................................................... 186
Figure 3-15 NE Adding window for several Nes ............................................................................................ 186
Figure 3-16 NE Modification window ........................................................................................................... 188
Figure 3-17 Confirmation box for deleting one NE........................................................................................ 189
Figure 3-18 Confirmation box for deleting several NEs ................................................................................. 189
Figure 3-19 Confirmation box for uploading the terminations of one NE ....................................................... 190
Figure 3-20 Confirmation box for uploading the terminations of several NEs ................................................ 190
Figure 3-21 Confirmation box for synchronizing the terminations of one NE ................................................. 191
Figure 3-22 Confirmation box for synchronizing the terminations of several NEs .......................................... 191
Figure 3-23 Confirmation box for acquitting the LAC state of one NE ........................................................... 192
Figure 3-24 Confirmation box for acquitting the LAC state of several NEs .................................................... 192
Figure 3-25 Termination List window (for an ATM Card 4x4_E - 260 ports) ................................................. 193
Figure 3-26 Termination Search window....................................................................................................... 194
3AG 86577 ABAA Ed3 11/725

Figure 3-27 Termination Transmission Characteristics Audit window ........................................................... 195
Figure 3-28 Termination Configuration window............................................................................................ 197

Figure 3-29 Confirmation box to de-configure a termination ......................................................................... 198

Figure 3-30 Confirmation box to de-configure several terminations............................................................... 198
Figure 3-31 NE Properties window ............................................................................................................... 199
Figure 3-32 Confirmation box to navigate towards equipment view ............................................................... 200
Figure 3-33 ENE management chain............................................................................................................. 201
Figure 3-34 NE / ENE List window ENE panel ........................................................................................... 202
Alcatel
Figure 3-35 ENE Search window .................................................................................................................. 203

Figure 3-36 ENE Creation window ............................................................................................................... 204
Figure 3-37 ENE Modification Window......................................................................................................... 206
Figure 3-38 Confirmation box for deleting one ENE...................................................................................... 207
Figure 3-39 Confirmation box for deleting several ENEs............................................................................... 207
Figure 3-40 ETP List window ....................................................................................................................... 208
Figure 3-41 ETP Search window................................................................................................................... 209
Figure 3-42 ETP Creation window................................................................................................................ 210
Figure 3-43 Confirmation box for deleting one ETP ...................................................................................... 211
Figure 3-44 Confirmation box for deleting several ETPs ............................................................................... 212
Figure 3-45 NAD Label Assignment window for one ETP.............................................................................. 213
Figure 3-46 NAD Label Assignment window for several ETPs....................................................................... 213
Figure 3-47 ENE Properties window............................................................................................................. 214
Figure 3-48 Transmission path management chain (network construction) .................................................... 215
Figure 3-49 Transmission Path List window.................................................................................................. 217
Figure 3-50 Transmission Path Search window............................................................................................. 219
Figure 3-51 Transmission Path Creation window.......................................................................................... 222
Figure 3-52 Transmission Path Creation window with an ENE not managed by RM ...................................... 223
Figure 3-53 Transmission Path Creation window with an ENE managed by RM............................................ 224
Figure 3-54 IMA Link List window................................................................................................................ 227
Figure 3-55 IMA Link Search window........................................................................................................... 228
Figure 3-56 Add IMA link window ................................................................................................................ 229
Figure 3-57 Confirmation box for removing one IMA link ............................................................................. 231
Figure 3-58 Confirmation box for removing several IMA links ...................................................................... 231
Figure 3-59 Confirmation box for finalizing one IMA link ............................................................................. 233
Figure 3-60 Confirmation box for finalizing several IMA links ...................................................................... 233
Figure 3-61 IMA Link Extremities window .................................................................................................... 234
Figure 3-62 IMA Link Properties window...................................................................................................... 235
Figure 3-63 Fault Localization List (IMA link).............................................................................................. 236
Figure 3-64 Confirmation box for displaying the fault localization list........................................................... 237
Figure 3-65 Confirmation box for finalizing one transmission path................................................................ 238
Figure 3-66 Confirmation box for finalizing several transmission paths......................................................... 238
Figure 3-67 Confirmation box for finalizing one IMA transmission path........................................................ 239
Figure 3-68 Confirmation box for finalizing several IMA transmission paths ................................................. 239
Figure 3-69 Transmission path Modification Window.................................................................................... 240
Figure 3-70 Confirmation box for deleting one transmission path.................................................................. 242
Figure 3-71 Confirmation box for deleting several transmission paths........................................................... 242
Figure 3-72 Confirmation box for locking one transmission path................................................................... 244
Figure 3-73 Confirmation box for locking several transmission paths............................................................ 244
Figure 3-74 Confirmation box for unlocking one transmission path ............................................................... 246
Figure 3-75 Confirmation box for unlocking several transmission paths ........................................................ 246
Figure 3-76 Transmission Path Configuration window.................................................................................. 247
Figure 3-77 Transmission Path NIM Configuration window .......................................................................... 249
Figure 3-78 Transmission Path Partitioning window..................................................................................... 251
Figure 3-79 Example of disjoined partitions.................................................................................................. 253
Figure 3-80 Example of not disjoined partitions ............................................................................................ 253
Figure 3-81 Transmission Path Extremities window (without ENE) ............................................................... 255
Figure 3-82 Transmission Path Extremities window (with an ENE) ............................................................... 256
Figure 3-83 Hard Transmission Path Bandwidth Load window ..................................................................... 258
Figure 3-84 Soft Transmission Path Bandwidth Load window ....................................................................... 260
Figure 3-85 Fault Localization List (Transmission Path)............................................................................... 261
Figure 3-87 Transmission Path Properties window ....................................................................................... 263
3AG 86577 ABAA Ed3 12/725

Figure 4-1 Network management chain......................................................................................................... 266
Figure 4-2 Hard point-to-point PVPC management chain ............................................................................. 268

Figure 4-3 Hard PVPC provisioning state..................................................................................................... 269

Figure 4-4 Hard PVPC List window.............................................................................................................. 270
Figure 4-5 Hard PVPC Search window......................................................................................................... 272
Figure 4-6 Hard PVPC Definition window.................................................................................................... 276
Figure 4-7 Hard PVPC Definition (extended view)........................................................................................ 278
Figure 4-8 Hard PVPC Modification............................................................................................................. 280
Alcatel
Figure 4-9 Confirmation box for deleting one hard PVPC ............................................................................. 282
Figure 4-10 Confirmation box for deleting several hard PVPCs .................................................................... 282
Figure 4-11 Hard PVPC Allocation .............................................................................................................. 283
Figure 4-12 Allocation for several Hard PVPCs............................................................................................ 283
Figure 4-13 Automatic routing mode with no constraint ................................................................................ 284
Figure 4-14 Semi-automatic routing mode with constraints ........................................................................... 284
Figure 4-15 Manual routing mode with constraints ....................................................................................... 285
Figure 4-16 Confirmation box for de-allocating one hard PVPC ................................................................... 287
Figure 4-17 Confirmation box for de-allocating several hard PVPCs ............................................................ 287
Figure 4-18 Confirmation box for implementing one hard PVPC................................................................... 289
Figure 4-19 Confirmation box for implementing several hard PVPCs ............................................................ 289
Figure 4-20 Confirmation box for de-implementing one hard PVPC .............................................................. 291
Figure 4-21 Confirmation box for de-implementing several hard PVPCs ....................................................... 291
Figure 4-22 Confirmation box for commissioning one hard PVPC................................................................ 293
Figure 4-23 Confirmation box for commissioning several hard PVPCs.......................................................... 293
Figure 4-24 Confirmation box for de-commissioning one hard PVPC ............................................................ 294
Figure 4-25 Confirmation box for de-commissioning several hard PVPCs ..................................................... 294
Figure 4-26 Confirmation box for locking one hard PVPC ............................................................................ 295
Figure 4-27 Confirmation box for locking several hard PVPCs ..................................................................... 295
Figure 4-28 Confirmation box for unlocking one hard PVPC......................................................................... 296
Figure 4-29 Confirmation box for unlocking several hard PVPCs.................................................................. 296
Figure 4-30 NAD Label assignment window for one hard PVPC ................................................................... 297
Figure 4-31 NAD Label assignment window for several hard PVPCs ............................................................ 297
Figure 4-32 Confirmation box for activating the output shaping on one hard PVPC ...................................... 298
Figure 4-33 Confirmation box for activating the output shaping on several hard PVPCs................................ 299
Figure 4-34 Confirmation box for deactivating the output shaping on one hard PVPC................................... 300
Figure 4-35 Confirmation box for deactivating the output shaping on several hard PVPCs ............................ 300
Figure 4-36 Confirmation box for activating UPC / NPC on one hard PVPC................................................. 301
Figure 4-37 Confirmation box for activating UPC / NPC on several hard PVPCs.......................................... 301
Figure 4-38 Confirmation box for deactivating UPC / NPC on one hard PVPC ............................................. 302
Figure 4-39 Confirmation box for deactivating UPC / NPC on several hard PVPCs ...................................... 302
Figure 4-40 Confirmation box for activating CC on one hard PVPC.............................................................. 303
Figure 4-41 Confirmation box for activating CC on several hard PVPCs....................................................... 303
Figure 4-42 Confirmation box for deactivating CC on one hard PVPC .......................................................... 305
Figure 4-43 Confirmation box for deactivating CC on several hard PVPCs ................................................... 305
Figure 4-44 Hard PVPC Bandwidth Modification window............................................................................. 307
Figure 4-45 Hard PVPC Bandwidth Modification window (extended view).................................................... 308
Figure 4-46 Point-to-Point Hard PVPC Extremities window ......................................................................... 310
Figure 4-47 Point-Multipoints Hard PVPC Extremities window .................................................................... 311
Figure 4-48 Hard PVPC Properties window.................................................................................................. 313
Figure 4-49 Point-to-Point Hard PVPC Bandwidth Load window.................................................................. 314
Figure 4-50 Point-MultiPoints Hard PVPC Bandwidth Load window ............................................................ 315
Figure 4-51 Hard PVPC Traffic Properties window ...................................................................................... 317
Figure 4-52 Hard PVPC Traffic Properties window ...................................................................................... 317
Figure 4-53 Hard PVPC Routing Properties window..................................................................................... 318
Figure 4-54 Sub-network view showing the transmission paths used by the hard PVPC ................................. 319
Figure 4-55 Fault Localization List (Hard PVPC) ......................................................................................... 321
Figure 4-57 Hard PVPC NE NIM List window .............................................................................................. 323
Figure 4-58 Hard PVPC NE NIM Search window ......................................................................................... 324
Figure 4-59 Hard PVPC NE NIM Configuration window .............................................................................. 325
Figure 4-60 Hard PVPC NIM CC List window.............................................................................................. 327
Figure 4-61 Hard PVPC NIM CC Search window ......................................................................................... 328
3AG 86577 ABAA Ed3 13/725

Figure 4-62 Confirmation box for activating NIM CC on one hard PVPC...................................................... 329
Figure 4-63 Confirmation box for activating NIM CC on several hard PVPCs............................................... 329
Figure 4-64 Confirmation box for deactivating NIM CC on one hard PVPC .................................................. 330
Figure 4-65 Confirmation box for deactivating NIM CC on several hard PVPCs ........................................... 330
Figure 4-66 Hard PVPC Constraint List window........................................................................................... 331
Figure 4-67 Hard PVPC Constraint Search window...................................................................................... 332
Figure 4-68 Constraint Definition window .................................................................................................... 333
Figure 4-69 Confirmation box for deleting one Constraint............................................................................. 335
Alcatel
Figure 4-70 Confirmation box for deleting several Constraints...................................................................... 335

Figure 4-71 Hard PVPC Leg management chain........................................................................................... 337
Figure 4-72 Hard PVPC Leg provisioning state ............................................................................................ 338
Figure 4-73 Hard PVPC Leg List window ..................................................................................................... 339
Figure 4-74 Hard PVPC Leg Search window ................................................................................................ 340
Figure 4-75 Point-Multipoints Hard PVPC View showing the Legs used by the hard PVPC ........................... 342
Figure 4-76 Hard PVPC Leg Definition window............................................................................................ 343
Figure 4-77 Hard PVPC Leg Modification window ....................................................................................... 345
Figure 4-78 Confirmation box for deleting one hard PVPC Leg..................................................................... 346
Figure 4-79 Confirmation box for deleting several hard PVPC Legs.............................................................. 346
Figure 4-80 Hard PVPC Leg Allocation........................................................................................................ 347
Figure 4-81 Confirmation box for allocating several hard PVPC Legs........................................................... 348
Figure 4-82 Confirmation box for de-allocating one hard PVPC Leg............................................................. 350
Figure 4-83 Confirmation box for de-allocating several hard PVPC Legs...................................................... 350
Figure 4-84 Confirmation box for implementing one hard PVPC Leg ............................................................ 351
Figure 4-85 Confirmation box for implementing several hard PVPC Legs ..................................................... 351
Figure 4-86 Confirmation box for de-implementing one hard PVPC Leg ....................................................... 352
Figure 4-87 Confirmation box for de-implementing several hard PVPC Legs ................................................ 352
Figure 4-88 Confirmation box for commissioning one hard PVPC Leg ......................................................... 353
Figure 4-89 Confirmation box for commissioning several hard PVPC Legs ................................................... 353
Figure 4-90 Confirmation box for de-commissioning one hard PVPC Leg ..................................................... 354
Figure 4-91 Confirmation box for de-commissioning several hard PVPC Legs .............................................. 354
Figure 4-92 Hard PVPC Leg Extremities window.......................................................................................... 355
Figure 4-93 Hard PVPC Leg Properties window........................................................................................... 356
Figure 4-94 Hard PVPC Leg Routing Properties window.............................................................................. 357
Figure 4-95 Sub-network view showing the transmission paths used by the hard PVPC ................................. 358
Figure 4-96 Hard PVPC Leg NE NIM List window........................................................................................ 360
Figure 4-97 Hard PVPC Leg NE NIM Search window................................................................................... 361
Figure 4-98 Hard PVPC Leg NE NIM Configuration window........................................................................ 362
Figure 4-99 Hard PVPC Leg Constraints List window................................................................................... 364
Figure 4-100 Hard PVPC Leg Constraint Search window ............................................................................. 365
Figure 4-101 Hard PVPC Leg Constraint Definition window ........................................................................ 366
Figure 4-102 Confirmation box for deleting one Constraint from a Hard PVPC Leg...................................... 368
Figure 4-103 Confirmation box for deleting several Constraints from a Hard PVPC Leg............................... 368
Figure 4-104 Hard PVCC management chain ............................................................................................... 370
Figure 4-105 Hard PVCC provisioning state................................................................................................. 371
Figure 4-106 Hard PVCC List window.......................................................................................................... 372
Figure 4-107 Hard PVCC Search window..................................................................................................... 373
Figure 4-108 Hard PVCC Definition window................................................................................................ 377
Figure 4-109 Hard PVCC Definition window (extended view) ....................................................................... 379
Figure 4-110 Hard PVCC Modification window............................................................................................ 382
Figure 4-111 Confirmation box for deleting one hard PVCC ......................................................................... 384
Figure 4-112 Confirmation box for deleting several hard PVCCs .................................................................. 384
Figure 4-113 Hard PVCC Allocation ............................................................................................................ 385
Figure 4-114 Confirmation box for allocating several hard PVCCs ............................................................... 385
Figure 4-115 Automatic routing mode with no constraint .............................................................................. 386
Figure 4-116 Semi-automatic routing mode with constraints ......................................................................... 386
Figure 4-117 Manual routing mode with constraints ..................................................................................... 387
Figure 4-118 Confirmation box for de-allocating one hard PVCC ................................................................. 389
Figure 4-119 Confirmation box for de-allocating several hard PVCCs .......................................................... 389
Figure 4-120 Confirmation box for implementing one hard PVCC................................................................. 390
Figure 4-121 Confirmation box for implementing several hard PVCCs.......................................................... 390
Figure 4-122 Confirmation box for de-implementing one hard PVCC............................................................ 392
3AG 86577 ABAA Ed3 14/725

Figure 4-123 Confirmation box for de-implementing several hard PVCCs ..................................................... 392
Figure 4-124 Confirmation box for commissioning one hard PVCC............................................................... 394
Figure 4-125 Confirmation box for commissioning several hard PVCCs........................................................ 394
Figure 4-126 Confirmation box for de-commissioning one hard PVCC.......................................................... 395
Figure 4-127 Confirmation box for de-commissioning several hard PVCCs................................................... 395
Figure 4-128 NAD Label assignment window for one hard PVCC ................................................................. 396
Figure 4-129 NAD Label assignment window for several hard PVCCs .......................................................... 396
Figure 4-130 Confirmation box for activating UPC / NPC on one hard PVCC............................................... 397
Alcatel
Figure 4-131 Confirmation box for activating UPC / NPC on several hard PVCCs........................................ 397
Figure 4-132 Confirmation box for deactivating UPC / NPC on one hard PVCC ........................................... 398
Figure 4-133 Confirmation box for deactivating UPC / NPC on several hard PVCCs .................................... 398
Figure 4-134 Confirmation box for activating CC on one hard PVCC ........................................................... 399
Figure 4-135 Confirmation box for activating CC on several hard PVCCs..................................................... 399
Figure 4-136 Confirmation box for deactivating CC on one hard PVCC........................................................ 401
Figure 4-137 Confirmation box for deactivating CC on several hard PVCCs ................................................. 401
Figure 4-138 Hard PVCC Bandwidth Modification window .......................................................................... 403
Figure 4-139 Hard PVCC Bandwidth Modification window (extended view).................................................. 404
Figure 4-140 Point-to-Point Hard PVCC Extremities window ....................................................................... 406
Figure 4-141 Point-Multipoints Hard PVCC Extremities window .................................................................. 407
Figure 4-142 Hard PVCC Properties window ............................................................................................... 408
Figure 4-143 Point-to-Point Hard PVCC Traffic Properties window ............................................................. 409
Figure 4-144 Point-Multipoints Hard PVCC Traffic Properties window ........................................................ 409
Figure 4-145 Hard PVCC Routing Properties window .................................................................................. 410
Figure 4-146 Sub-network View showing the VPCs used by the hard PVCC................................................... 411
Figure 4-147 Fault Localization List (Hard PVCC)....................................................................................... 413
Figure 4-148 Confirmation box for displaying the fault localization list......................................................... 414
Figure 4-149 Hard PVCC NE NIM List window............................................................................................ 415
Figure 4-150 Hard PVCC NE NIM Search window ....................................................................................... 416
Figure 4-151 Hard PVCC NE NIM Configuration window ............................................................................ 417
Figure 4-152 Hard PVCC NIM CC List window............................................................................................ 419
Figure 4-153 Hard PVCC NIM CC Search window....................................................................................... 420
Figure 4-154 Confirmation box for activating NIM CC on one hard PVCC.................................................... 421
Figure 4-155 Confirmation box for activating NIM CC on several hard PVCCs............................................. 421
Figure 4-156 Confirmation box for deactivating NIM CC on one hard PVCC ................................................ 422
Figure 4-157 Confirmation box for deactivating NIM CC on several hard PVCCs ......................................... 422
Figure 4-158 Hard PVCC Constraints List window ...................................................................................... 423
Figure 4-159 Hard PVCC Constraint Search window.................................................................................... 424
Figure 4-160 Constraint Definition window .................................................................................................. 425
Figure 4-161 Confirmation box for deleting one Constraint........................................................................... 427
Figure 4-162 Confirmation box for deleting several Constraints.................................................................... 427
Figure 4-163 Hard PVCC Leg management chain......................................................................................... 429
Figure 4-164 Hard PVCC Leg provisioning state .......................................................................................... 430
Figure 4-165 Hard PVCC Leg List window ................................................................................................... 431
Figure 4-166 Hard PVCC Leg Search window .............................................................................................. 432
Figure 4-167 Point-Multipoints Hard PVCC View showing the Legs used by the hard PVCC......................... 434
Figure 4-168 Hard PVCC Leg Definition window ......................................................................................... 435
Figure 4-169 Hard PVCC Leg Modification window ..................................................................................... 437
Figure 4-170 Confirmation box for deleting one hard PVCC Leg................................................................... 438
Figure 4-171 Confirmation box for deleting several hard PVCC Legs............................................................ 438
Figure 4-172 Hard PVCC Leg Allocation...................................................................................................... 439
Figure 4-173 Confirmation box for allocating several hard PVCC Legs ........................................................ 440
Figure 4-174 Confirmation box for de-allocating one hard PVCC Leg........................................................... 442
Figure 4-175 Confirmation box for de-allocating several hard PVCC Legs.................................................... 442
Figure 4-176 Confirmation box for implementing one hard PVCC Leg .......................................................... 443
Figure 4-177 Confirmation box for implementing several hard PVCC Legs ................................................... 443
Figure 4-178 Confirmation box for de-implementing one hard PVCC Leg ..................................................... 445
Figure 4-179 Confirmation box for de-implementing several hard PVCC Legs .............................................. 445
Figure 4-180 Confirmation box for commissioning one hard PVCC Leg ........................................................ 447
Figure 4-181 Confirmation box for commissioning several hard PVCC Legs ................................................. 447
Figure 4-182 Confirmation box for de-commissioning one hard PVCC Leg ................................................... 448
Figure 4-183 Confirmation box for de-commissioning several hard PVCC Legs ............................................ 448
3AG 86577 ABAA Ed3 15/725

Figure 4-184 Hard PVCC Leg Extremities window........................................................................................ 449
Figure 4-185 Hard PVCC Leg Properties window......................................................................................... 450

Figure 4-186 Hard PVCC Leg Routing Properties window............................................................................ 451

Figure 4-187 Sub-network view showing the VPCs used by the hard PVCC ................................................... 452
Figure 4-188 Hard PVCC Leg NE NIM List window ..................................................................................... 454
Figure 4-189 Hard PVCC Leg NE NIM Search window................................................................................. 455
Figure 4-190 Hard PVCC Leg NE NIM Configuration window...................................................................... 456
Figure 4-191 Hard PVCC Leg Constraint List window.................................................................................. 458
Alcatel
Figure 4-192 Hard PVCC Leg Constraint Search window ............................................................................. 459
Figure 4-193 Hard PVCC Leg Constraint Definition window ........................................................................ 460
Figure 4-194 Confirmation box for deleting a Constraint from a Hard PVCC Leg ......................................... 462
Figure 4-195 Confirmation box for deleting several Constraints from a Hard PVCC Leg............................... 462
Figure 4-196 Soft PVPC management chain.................................................................................................. 463
Figure 4-197 Soft PVPC provisioning state ................................................................................................... 464
Figure 4-198 Soft PVPC List window Description panel ............................................................................. 465
Figure 4-199 Soft PVPC Description Search window .................................................................................... 466
Figure 4-200 Soft PVPC Definition window .................................................................................................. 469
Figure 4-201 Soft PVPC Definition window (extended view).......................................................................... 470
Figure 4-202 Soft PVPC Modification........................................................................................................... 472
Figure 4-203 Confirmation box for deleting one soft PVPC ........................................................................... 473
Figure 4-204 Confirmation box for deleting several soft PVPCs .................................................................... 473
Figure 4-205 Confirmation box for setting-up one soft PVPC ........................................................................ 474
Figure 4-206 Confirmation box for setting-up several soft PVPCs ................................................................. 474
Figure 4-207 Confirmation box for releasing one soft PVPC ......................................................................... 476
Figure 4-208 Confirmation box for releasing several soft PVPCs .................................................................. 476
Figure 4-209 Soft PVPC List window Characteristics panel ....................................................................... 477
Figure 4-210 Soft PVPC Characteristics Search window............................................................................... 478
Figure 4-211 Confirmation box for activating the output shaping on one soft PVPC ...................................... 480
Figure 4-212 Confirmation box for activating the output shaping on several soft PVPCs ............................... 480
Figure 4-213 Confirmation box for deactivating the output shaping on one soft PVPC................................... 482
Figure 4-214 Confirmation box for deactivating the output shaping on several soft PVPCs............................ 482
Figure 4-215 Confirmation box for activating UPC / NPC on one soft PVPC................................................. 483
Figure 4-216 Confirmation box for activating UPC / NPC on several soft PVPCs.......................................... 483
Figure 4-217 Confirmation box for deactivating UPC / NPC on one soft PVPC ............................................. 484
Figure 4-218 Confirmation box for deactivating UPC / NPC on several soft PVPCs ...................................... 484
Figure 4-219 Soft PVPC Extremities window ................................................................................................ 485
Figure 4-220 Soft PVPC Properties window.................................................................................................. 486
Figure 4-221 Soft PVPC Bandwidth Load window......................................................................................... 487
Figure 4-222 Soft PVPC Traffic Properties window ...................................................................................... 489
Figure 4-223 Soft PVCC management chain.................................................................................................. 491
Figure 4-224 Soft PVCC provisioning state ................................................................................................... 492
Figure 4-225 Soft PVCC List window Description panel............................................................................. 493
Figure 4-226 Soft PVCC Description Search window .................................................................................... 494
Figure 4-227 Soft PVCC Definition window .................................................................................................. 497
Figure 4-228 Soft PVCC Definition window (extended view) ......................................................................... 498
Figure 4-229 Soft PVCC Modification........................................................................................................... 500
Figure 4-230 Confirmation box for deleting one soft PVCC........................................................................... 501
Figure 4-231 Confirmation box for deleting several soft PVCCs.................................................................... 501
Figure 4-232 Confirmation box for setting-up one soft PVCC........................................................................ 502
Figure 4-233 Confirmation box for setting-up several soft PVCCs ................................................................. 502
Figure 4-234 Confirmation box for releasing one soft PVCC......................................................................... 504
Figure 4-235 Confirmation box for releasing several soft PVCCs .................................................................. 504
Figure 4-236 Soft PVCC List window Characteristics panel ....................................................................... 505
Figure 4-237 Soft PVCC Characteristics Search window............................................................................... 506
Figure 4-238 Confirmation box for activating UPC / NPC on one soft PVCC ................................................ 508
Figure 4-239 Confirmation box for activating UPC / NPC on several soft PVCCs ......................................... 508
Figure 4-240 Confirmation box for deactivating UPC / NPC on one soft PVCC............................................. 509
Figure 4-241 Confirmation box for deactivating UPC / NPC on several soft PVCCs...................................... 509
Figure 4-242 Soft PVCC Extremities window ................................................................................................ 510
Figure 4-243 Soft PVCC Properties window.................................................................................................. 511
Figure 4-244 Soft PVCC Traffic Properties window ...................................................................................... 512
3AG 86577 ABAA Ed3 16/725

Figure 6-1 Available Non-OAM PM counters................................................................................................ 522
Figure 6-2 PM Measure chain ...................................................................................................................... 524

Figure 6-3 PM Measure interdependencies ................................................................................................... 525

Figure 6-4 PM Measure List window ............................................................................................................ 526
Figure 6-5 PM Measure Search window........................................................................................................ 527
Figure 6-6 PM Measure Creation window..................................................................................................... 529
Figure 6-7 PM Measure Modification window............................................................................................... 531
Figure 6-8 Confirmation box for deleting one PM Measure ........................................................................... 533
Alcatel
Figure 6-9 Confirmation box for deleting several PM Measures .................................................................... 533
Figure 6-10 PM Measure / Report Profile association window ...................................................................... 534
Figure 6-11 PM Measure / Report Profile association window (multi-selection) ............................................ 535
Figure 6-12 PM Measure / Report Profile dissociation window ..................................................................... 536
Figure 6-13 PM Measure / Report Profile dissociation window (multi-selection) ........................................... 536
Figure 6-14 Confirmation box for activating one PM Measure ...................................................................... 538
Figure 6-15 Confirmation box for activating several PM Measures ............................................................... 539
Figure 6-16 Confirmation box for de-activating one PM Measure ................................................................. 540
Figure 6-17 Confirmation box for de-activating several PM Measures .......................................................... 540
Figure 6-18 Confirmation box for force data collection on one PM Measure ................................................. 542
Figure 6-19 Confirmation box for force data collection on several PM Measures .......................................... 542
Figure 6-20 PM Measure Properties window ................................................................................................ 543
Figure 6-21 Confirmation box to navigate towards PMDS (from PM Measure List)....................................... 544
Figure 6-22 Confirmation box to navigate towards PMDS (from PM Transport List)..................................... 544
Figure 6-23 PM Transport List window (if PM Measure Layer is Transmission Path).................................... 545
Figure 6-24 PM Transport Search window.................................................................................................... 546
Figure 6-25 PM Transport Association window (PM Measure Layer is Transmission Path)........................... 549
Figure 6-26 PM Transport Association window (PM Measure Layer is PVPC).............................................. 550
Figure 6-27 PM Transport Association window (PM Measure Layer is PVCC).............................................. 551
Figure 6-28 PM Transport Association window (PM Measure Layer is PVC) ................................................ 552
Figure 6-29 Confirmation box for dissociate one PM Transport .................................................................... 553
Figure 6-30 Confirmation box for dissociate several PM Transports ............................................................. 553
Figure 6-31 PP List for a PM measure with Transport Type = Transmission Path (between two NEs)............ 554
Figure 6-32 PP List for a PM measure with Transport Type = Hard PVPC ................................................... 554
Figure 6-33 PP List for a PM measure with Transport Type = Hard PVCC................................................... 555
Figure 6-34 PP Search window..................................................................................................................... 556
Figure 6-35 Confirmation box for associate one PP to a PM transport .......................................................... 557
Figure 6-36 Confirmation box for associate several PP to a PM transport..................................................... 557
Figure 6-37 Confirmation box for dissociate one PP from a PM transport..................................................... 558
Figure 6-38 Confirmation box for dissociate several PP from a PM transport ............................................... 558
Figure 6-39 Periodic Report Profile List window .......................................................................................... 560
Figure 6-40 Periodic Report Profile Search window...................................................................................... 561
Figure 6-41 Periodic Report Profile creation window (Report Kind = Counter)............................................. 562
Figure 6-42 Periodic Report Profile creation window (Report Kind = Transport State) ................................. 563
Figure 6-43 Periodic Report Profile creation window (Report Kind = Counter Threshold) ............................ 563
Figure 6-44 Periodic Report Profile modification window ............................................................................. 565
Figure 6-45 Confirmation box for deleting one Report Profile ....................................................................... 567
Figure 6-46 Confirmation box for deleting several Reports Profiles............................................................... 567
Figure 6-47 Periodic Report Profile Properties window (Report Kind = Counter) ......................................... 568
Figure 6-48 Periodic Report Profile Properties window (Report Kind = Transport State) .............................. 568
Figure 6-49 Periodic Report Profile Properties window (Report Kind = Counter Threshold)......................... 569
Figure 6-50 TCA Profile List window............................................................................................................ 571
Figure 6-51 TCA Profile Properties window.................................................................................................. 572
Figure 7-1 PNNI management chain ............................................................................................................. 575
Figure 7-2 NE List (Administration) window ................................................................................................. 576
Figure 7-3 NE Search (Administration) window ............................................................................................ 577
Figure 7-4 NE Observation window .............................................................................................................. 578
Figure 7-5 PNNI Node ATM Address Configuration window ......................................................................... 579
Figure 7-6 Confirmation box for activating one PNNI node........................................................................... 580
Figure 7-7 Confirmation box for activating several PNNI nodes.................................................................... 580
Figure 7-8 Confirmation box for deactivating one PNNI node ....................................................................... 581
Figure 7-9 Confirmation box for deactivating several PNNI nodes ................................................................ 581
Figure 7-10 Termination List (Administration) window ................................................................................. 582
3AG 86577 ABAA Ed3 17/725

Figure 7-11 Termination Search (Administration) window ............................................................................ 583
Figure 7-12 PNNI Interface ATM Address Configuration window.................................................................. 584

Figure 7-13 Three ways of encoding ATM Address........................................................................................ 585

Figure 7-14 Traffic Descriptor List window................................................................................................... 588
Figure 7-15 Traffic Descriptor Search window.............................................................................................. 589
Figure 7-16 Traffic Descriptor Creation window........................................................................................... 590
Figure 7-17 Traffic Descriptor Creation window........................................................................................... 593
Figure 7-18 Traffic Descriptor Modification window..................................................................................... 594
Alcatel
Figure 7-19 Confirmation box for deleting one traffic descriptor ................................................................... 595
Figure 7-20 Confirmation box for deleting several traffic descriptors ............................................................ 595
Figure 7-21 Traffic Profile List window ........................................................................................................ 597
Figure 7-22 Traffic Profile Search window.................................................................................................... 598
Figure 7-23 Traffic Profile Creation window................................................................................................. 599
Figure 7-24 Traffic Profile Creation window (when creating a traffic profile from an existing one)................ 601
Figure 7-25 Traffic Profile Modification window........................................................................................... 602
Figure 7-26 Confirmation box for deleting one traffic profile......................................................................... 603
Figure 7-27 Confirmation box for deleting several traffic profiles.................................................................. 603
Figure 7-28 Traffic Profile Properties window .............................................................................................. 605
Figure 7-29 Global User Management window ............................................................................................ 607
Figure 7-30 User creation window................................................................................................................ 608
Figure 8-1 Plug & play chain........................................................................................................................ 611
Figure 8-2 Confirmation box for starting the plug & play.............................................................................. 613
Figure 8-3 NE List (Plug & Play) window..................................................................................................... 614
Figure 8-4 Application locked message box................................................................................................... 615
Figure 8-5 NE Search (Plug & Play) window................................................................................................ 615
Figure 8-6 Confirmation box for uploading the SDH transmission paths........................................................ 617
Figure 8-7 Confirmation box for discovering the transmission path characteristics........................................ 618
Figure 8-8 Confirmation box for discovering the traffic descriptors............................................................... 620
Figure 8-9 Confirmation box for discovering the VP connections .................................................................. 621
Figure 8-10 Confirmation box for recovering the Hard PVPCs...................................................................... 623
Figure 8-11 Confirmation box for discovering the VC connections ................................................................ 625
Figure 8-12 Confirmation box for recovering the Hard PVCCs ..................................................................... 627
Figure 8-13 Confirmation box for ending the plug & play.............................................................................. 629
Figure 8-14 Message box in case of ending the plug & play procedure .......................................................... 629
Figure 8-15 Message box in case of exiting the application ........................................................................... 630
Figure 8-16 Message box in case of warnings during the plug & play............................................................ 632
Figure 8-17 Confirmation box for starting the audit / alignment session ........................................................ 635
Figure 8-18 NE List (Audit) window.............................................................................................................. 637
Figure 8-19 Audit NE Search window ........................................................................................................... 638
Figure 8-20 Confirmation box for start audit on one NE................................................................................ 639
Figure 8-21 Confirmation box for start audit on several NEs......................................................................... 639
Figure 8-22 NE Alignment Directory List window ......................................................................................... 641
Figure 8-23 List of audit's files for NE alignment .......................................................................................... 642
Figure 8-24 Confirmation box to start alignment procedure (for a directory)................................................. 644
Figure 8-25 Confirmation box to start alignment procedure (for one NE) ...................................................... 645
Figure 8-26 Confirmation box to start alignment procedure (for several NEs) ............................................... 645
Figure 8-27 Confirmation box to start force alignment procedure (for a directory) ........................................ 646
Figure 8-28 Confirmation box to start force alignment procedure (for one NE).............................................. 647
Figure 8-29 Confirmation box to start force alignment procedure (for several NEs)....................................... 647
Figure 8-30 Confirmation box for ending the audit / alignment session.......................................................... 650
3AG 86577 ABAA Ed3 18/725

HISTORY
Ed 01: 05-03-16
Created document from 3AG 23912 AAAA (ed 4) document
Updated for 1354 BM 7.1 (IMA management, DS3 management, Hard

Alcatel
PVPC/PVCC routing properties” windows modification, Hard PVCC Leg

graphical view description , “Transmission Path Creation” window modification)
Updated Ed 01: 05-09-16
Added ENE enhancement content according to 1354BMATM R7.1.3PL5.
(see chapter3)
Updated Ed 01: 05-11-06
Added Loop Back feature(see chapter5)
Updated Ed 01:06-01-19
Added restored key words for transmission path in chapter 10 according to

1354BMATM R7.1.3PL6
Added NE Download mode management in chapter 3 according to 1354BMATM

R7.1.4
Added Alarm debouching management, Minimum Active IMA link number and
Progress dialog window in GUI according to 1354BMATM R7.1.4PL1
REFERENCED DOCUMENTS
[1] ALMAP Alarm surveillance 5.3 – User’s guide
3BP 21640 0004 PCZZA Ed 2
[2] ALMAP Security management 5.0 – User’s guide
3BP 21635 0006 PCZZA Ed 2
[3] SMF System Management Function – User’s guide
3AL 21645 0001 PCZZA
[4] PMDS Performance Monitoring Display system – User’s guide
8CT 00019 BP 21645 0001 PCZZA
3AG 86577 ABAA Ed3 19/725

Alcatel
3AG 86577 ABAA Ed3

20/725
PREFACE
Scope
This handbook is a user's guide for the 1354 BM.
It describes how to use the 1354 BM package for configuring and monitoring
Alcatel
ATM networks.
Applicability
This handbook applies to 1354 BM R7.1
Pre-requisite
This handbook assumes the user is familiar with the function of
telecommunication networks and has had some exposure to the X-Window /
Motif and Microsoft Windows environments.
Structure
The document includes ten chapters:
1. Generalities: presents the 1354 BM product, provides some basic concepts

and introduces the functional domains.
2. User interface overview: gives a descriptive overview of the user interface

and the main principles for using it.
3. Network construction: to define sub-networks, NEs and transmission paths.
4. Network management: to define PVCs and manage them.
5. Maintenance management: to monitor the network.
6. Performance management: offers the operator the possibility to have some

information about the managed entities. Two kinds of information are
provided: counters, and alarms by threshold crossing mechanism.
7. Administration management: to manage PNNI, the ATM traffic, the user's

access rights and the virtual networks.
8. Utilities: to use the plug & play, NE audit, NE alignment, NE force alignment
services.
9. Glossary: gives the definitions of the terms used in the user interface and in
the ATM world.
10. Appendix: gives the limitations of the 1354 BM product.
3AG 86577 ABAA Ed3 21/725

CONVENTIONS
Icons
The meaning of the different icons used in this document is given below.
Indicates how the user can access a function.

Alcatel
Indicates a sorting possibility in a list window.
Indicates a filtering possibility in a list window.
Indicates the actions the user can perform from a list window.
Indicates the points the user has to check before accessing a function.
Draws the user’s attention to an important point.
Warning the user about the consequences of an action.
3AG 86577 ABAA Ed3 22/725

Alcatel
3AG 86577 ABAA Ed3

23/725
1 Generalities

Alcatel
1 Generalities
This chapter presents the 1354 BM product.
1.1 Overview
1.2 Interfaces
1.3 ATM basic concepts
1.4 Functional domains
1.5 System environment
3AG 86577 ABAA Ed3 24/725

1 Generalities
1.1 Overview
The network construction chain gives the order in which the construction must be
performed.
Alcatel
Operators are currently faced with a huge increase in data traffic on the network,
and at the same time a diversification of services such as Virtual Network (VN),
Internet, Asynchronous Transfer Mode (ATM).
In addition to full Synchronous Digital Hierarchy (SDH) transport features, the

OPTINEX Multi Service Nodes (O-MSN) offer integrated Internet Protocol (IP)
switching and ATM routing capabilities, avoiding overlay networks and reducing
the cost of introducing new data services.
Operators are designing IP and/or ATM based networks to solve problems such as
bandwidth and Quality of Service (QoS).
However, managing and configuring these networks without the right management
tools is a technically complex task that increases the risk and cost of a widespread
deployment.
The feature-rich Alcatel 1354 BM provides the Telecom operator with a network-
centric solution which allows to reduce operating expenses while saving a
considerable amount of time in the process of provisioning and managing IP an/or
ATM services.
3AG 86577 ABAA Ed3 25/725

1 Generalities
1.1.1 Management layers
The network management may be split into four layers presented hereafter.
Physical Layer
Alcatel
It concerns the physical equipment.
Element Management Layer (EML)
It manages each Network Element (NE) on an individual basis and supports an

abstraction of the functions provided by the Physical Layer. The EML has a set of
element managers that are individually responsible, on a devolved basis from the
management layer, for some subsets of NEs.
Network Management Layer (NML)
It has the responsibility for the management of a set of NEs, as presented by the
EML, both individually and as a set. It is not concerned with how a particular
element provides services internally.
Functions addressing the management on a wide geographical area are located at

this layer. Complete visibility of the whole network is typical and a vendor
independent view will need to be maintained.
Service Management Layer (SML)
It offers services such as network analyze or Virtual Network (VN) management.
3AG 86577 ABAA Ed3 26/725

1 Generalities
1.1.2 Positioning
The figure below shows the 1354 BM positioning in terms of management layers
and in the already existing offer.
Alcatel
SML 1355 NA 1355 VPN

Network Analyzer Virtual Private Network Manager
NML
ISN
1354 BM
1354 NN Broadband Manager
Network Manager (ATM)
1354 RM
1354 NP Subnetwork Manager
Backbone Manager (SDH/Optical Networks)
EML
1353 NM
Element Manager
PHYSICAL
LAYER
PFE ADM DWDM

DXC
SLTE
Optical NEs
Submarine NEs Optical
SDH NEs + ISA
Repeater MW DXC
(O-MSN)
Figure 1-1 1354 BM positioning
3AG 86577 ABAA Ed3 27/725

1 Generalities
At EML level, the 1353 NM manages both SDH NEs and ATM cards.
At NML level, the 1354 RM manages SDH equipment (ADM, DXC, MW, SUBM)
and the 1354 BM manages ATM equipment (O-MSN).
The O-MSN equipment is an Add and Drop Multiplexer (ADM) including one or
several ATM cards. Such a type of equipment is also called Integrated SDH/ATM
Alcatel
(ISA) NE.
1.1.3 The network from various points of view

The figure below shows a real view of a mixed ATM/SDH topology.
ISA NE
A ISA NE
D
STM-1 ADM
E ADM
STM-16 F
34 MB
ATM Switch
3 Router
IP/ATM
External ATM sub network ISA NE ISA NE 4
B C
STM-1
ATM Switch
2
ATM card
External ATM sub -network
Figure 1-2 Real ATM/SDH Network
The topology above is made up of the following elements:

− ISA NEs fully equipped with ATM cards
− ADM without any ATM card
− other ATM elements: switch, another sub-network…
3AG 86577 ABAA Ed3 28/725

1 Generalities
The figure below shows the same topology at SDH-NML (1354 RM) point of view.
SDH paths link the different NEs.
A
Alcatel
STM-1 E
F
34 MB
ENE
ENE
ATM Switch
3 Router
IP/ATM
External ATM sub network B C 4
STM-1
ENE
ATM Switch
ATM card 2

Transmission paths
Figure 1-3 SDH-NML point of view
Each transmission path has an SDH path ending on an ATM card of a different ISA
NE or an external NE.
The elements not managed by the SDH-NML manager but linked to a managed NE
by an STM-n link are created as external NEs.
3AG 86577 ABAA Ed3 29/725

1 Generalities
The figure below shows the same network topology at ATM-NML point of view.
A
D
Alcatel
ENE
ENE
ATM Switch
3 Router
IP/ATM
External ATM sub network B1 C 4
B2
ENE
ATM Switch
ATM card 2

Transmission paths
Figure 1-4 ATM-NML point of view
Each ATM board is defined as one ATM NE with its own characteristics (identify,
capacity) and the transmission paths are created as follow: the access to the ATM
matrix passes through the SDH matrix.
So, the transmission path is supported by an SDH path.
Combining network management of ATM switching, IP routing and SDH/WDM

transport, the integrated 1353/1354 product portfolio guarantees cost effective and
simplified operation and maintenance.
3AG 86577 ABAA Ed3 30/725

1 Generalities
1.2 Interfaces
The figure below details the interfaces used by the 1354 BM.
Alcatel
Coopera ting Systems

Ma na gement
CORBA/ ASCII
Systems
N etwork
1354 BM ASCII Q3 1354 RM

ISN
dispatcher
CO RBA Q3
Mana gement
Equipment
Systems
1353NSH
1353 M
SH
SN M P
Equipment
Q3
la yer
ATM
ATM O MSN
SDH
ATM SDH
Figure 1-5 1354 BM interfaces
The SDH part of the ISA NE is managed by the 1354 RM by using the Q3 protocol.
Each ATM card of the ISA NE is managed by the 1354 BM as a single ATM NE
with its own IP address, by using the SNMP protocol, then a CORBA interface.
3AG 86577 ABAA Ed3 31/725

1 Generalities
1.2.1 1354 BM – 1353 NM interface
This CORBA-based interface is mainly used for:

− the NE discovery and any configuration change in the NE
Alcatel
− the management of the hard/soft PVCs and the routing discovery for soft PVCs
− the PNNI and peer group management
− the activation/deactivation of the PM counters
− TP/VP-A Upload
− the bandwidth loading
− the connection characteristics
− the OAM management.
1.2.2 1354 BM – 1354 RM interface

This ASCII-based interface is mainly used for the management of the SDH paths
that support the ATM transmission paths and that are provided through the ISN
dispatcher.
3AG 86577 ABAA Ed3 32/725

1 Generalities
1.3 ATM basic concepts
1.3.1 Cell
ATM is a “cell relay” technology. The data are carried in small, fixed-length
Alcatel
packets called “cells”. Each cell is 53 bytes long (5 bytes are the header and 48
bytes are the payload).
The fixed length cell gives some key advantages from earlier packet technology.
The first is that the short cells can be switched in hardware, so that ATM can be
switched quickly and economically.
The second advantage is that queuing delays caused by long, variable length frames
can be reduced to the wait time for a 53-bytes cell, allowing time-dependent voice
and video to be transported.
1.3.2 Transmission path, VP and VC

ATM provides the user with an on-connection service, based on a transmission
hierarchy.
T ra ns m is sio n
VC VP VP VC
MTedia
ransm issio n
VC VP VP VC
P ath
VC VP VP VC
Figure 1-6 Transmission hierarchy
A transmission path is a link between two NEs. It may be used by several VPs
(Virtual Paths).
A transmission path can be declared as a transmission path IMA (=IMA group). It

is composed of IMA links and used by several VPs (see chapter 1.3.3).
In the same way, a VP may be used by several VCs (Virtual Channels).
3AG 86577 ABAA Ed3 33/725

1 Generalities
1.3.3 Inverse Multiplexing ATM (IMA)

Inverse Multiplexing ATM (IMA) permits to transport aggregate ATM streams into
multiple physical links (E1, VC-12 and VC-3 transmission paths).
The ATM traffic is then dispatched on several parallel E1, VC-12, VC-3 SDH paths
and rebuild on the receiving NE (or ENE). The ATM cell order is preserved on the
Alcatel
re-composed streams.
The aggregate E1, VC-12 or VC-3 link can be seen as a logical link of nxE1/VC-12
or VC-3 capacity.
A physical link (a SDH path) is called IMA link and a logical link is called
transmission path IMA (= IMA group).
3 x VC-12 IMA links in 1 IMA group (= IMA logical link)
IMA NE IMA NE
Transmission path Transmission path IMA (= IMA group)
Figure 1-7 IMA hierarchy
Between two NEs, VC-12/VC-3 capacities are authorized. Between one NE and
one ENE, E1/VC-12/VC-3 capacities are authorized.
IMA reduces the bandwidth consumption on the SDH paths by optimizing the
filling of the link. A single VPC is carried by multiple SDH paths.
The figure bellow illustrates this: the cells for stream VP0, VP1 and VP2 are
indifferently transported by TP1 and TP2 IMA links. The cells are emitted by IMA
device by cyclically allocating to the transmission paths with a round-robin policy.
VP1 VP2
VP2 VP2
VP0
TP1 TP2 TP1 IM A link TP2 IM A link
TP0 IM A group
Two classical VC12 ATM transmission paths. IMA group maid of 2xVC-12 IMA links.
Figure 1-8 IMA bandwidth optimization
3AG 86577 ABAA Ed3 34/725

1 Generalities
When the required bandwidth does not justify the use of an expensive VC-3 link, it
permits to build a network by incrementally adding parallel VC-12. Thanks to IMA

the use of VC-12 links does not limits the maximum capacity of the individual held
VPC. VPC with a capacity between VC-12 to VC-3 can be transported by the IMA
link.
A transmission path IMA (= IMA group) is composed of the same type of transport
Alcatel
type E1, VC-3, VC-12 on each IMA link.
IMA links can be added and removed from an IMA group without cutting the
traffic.
1.3.4 ATM connection

Two connection types exist:
− Permanent Virtual Path Connection (PVPC):
A PVPC is composed of one or several VPs.
The PVPC facilitates the VC commutation, because it connects whole sections

of the ATM network. In case PVPCs would not exist, routing complications
would dramatically increase, because that, for each connection between users, it
would be needed to process all the routing tables of the traversed nodes.
For example, this fact would be reflected in an increment of the time needed to
establish a connection.
Each cell belonging to a same PVPC is identified through the Virtual Path
Identifier (VPI) field contained in the header.
A Quality of Service (QoS) is attached to each PVPC.
− Permanent Virtual Channel Connection (PVCC):

A PVCC is composed of one or several VCs.
A PVCC is an unidirectional connection between users, so if a Full Duplex

communication is desired among these two users, two PVCC are required.
The PVCC, besides transporting data among users, is also used to transport the
network signalling and the network management information.
Each cell belonging to a same PVCC is identified through the Virtual Channel
Identifier (VCI) field contained in the header.
A Quality of Service (QoS) is attached to each PVCC.
3AG 86577 ABAA Ed3 35/725

1 Generalities
The ATM traffic is transported between the different ATM NEs by the
Synchronous Digital Hierarchy (SDH) and the Plesiochronous Digital Hierarchy
(PDH) circuits (VC-12, VC-3, VC-4, VC-4-4c, E1, E3, DS3), named SDH paths in
this documentation.
Alcatel
Another technology could also transport the ATM traffic (pure ATM example) but
it is not defined in this document.
1.3.5 Quality of service

ATM technology provides the user with various Quality of Service (QoS) to cover
his various needs.
A QoS is defined by a class of service and according to this class of service by

some of the parameters in the following list :
− PCR (Peak Cell Rate = Maximum instantaneous rate at which the user will
transmit),
− SCR (Sustainable Cell Rate = The average rate as measured over a long
interval),
− MCR (Minimum Cell Rate = The minimum cell rate desired by user),
− MBS (Maximum Burst Size = The maximum number of cells that can be sent
at the peak cell rate),
− CDVT (Cell Delay Variation Tolerance = The difference of the maximum and
minimum dell delay variation experienced during the connection life).
In the following table are listed different usage that can be done of each class of
service (ITU terminology), and the parameters that define each of them:
3AG 86577 ABAA Ed3 36/725

1 Generalities
I.371 ATM Transfer Capability

QoS
Example of application Transfer Parameters
class
Capability
Circuit emulation DBR class 1 PCR, CDVT
Alcatel
Real-time Audio/Video DBR class 1 PCR, CDVT

communication
SBR.1 class 1 PCR, CDVT, SCR, MBS
Delay sensitive DBR class 1 PCR, CDVT

applications that produce
variable bit rate traffic
Non real-time audio/video SBR1 class 2 PCR, CDVT, SCR, MBS

communications
(requiring low cell loss) DBR class 2 PCR, CDVT
Support of SMDS, FMBS, SBR.1 class 2 PCR, CDVT, SCR, MBS

IP SBR.2 class 3
SBR.3 class 3
Video-on-Demand DBR class 1 PCR, CDVT

(limited receive buffer)
SBR.1 class 1 PCR, CDVT, SCR, MBS
Elastic Audio/Video SBR.2 class 3 PCR, CDVT, SCR, MBS

communication
File transfer SBR.2 class 3 PCR, CDVT, SCR, MBS

Image transfer
Database enquiry SBR.2 / class 3 PCR, CDVT, SCR, MBS

SBR.3
Virtual Private Network DBR class 1 PCR, CDVT

(transport of any traffic
through a VP network) SBR.1 class 1 PCR, CDVT, SCR, MBS
IP support (edge-to-edge DBR class U PCR, CDVT

router connection)
Figure 1-9 Usage of the different qualities of service
3AG 86577 ABAA Ed3 37/725

1 Generalities
1.4 Functional domains
The 1354 BM is in charge of the following:

− Network construction
− Network management
Alcatel
− Maintenance management
− Performance management
− Administration management
− Utilities.
1.4.1 Network construction

The network construction consists in:
• defining, modifying, removing and configuring the following entities of the

network topology:
− sub-networks
− ATM NEs and External NEs (ENE)
− transmission paths, transmission paths IMA (IMA group), IMA links
− terminations and External Termination Points (ETP)
• partitioning the transmission path / transmission path IMA.
3AG 86577 ABAA Ed3 38/725

1 Generalities
1.4.1.1 Sub-network
The network is structured into sub-networks.
Main network (Root) Level 1

Alcatel
Sub-network
Level 2
ENE
ATM NE
Level 3
Level 4
Figure 1-10 Sub-network levels
Four levels (by default) may be defined. The first level is the top corresponding to
the main network. Only sub-networks and ENEs can be defined.
3AG 86577 ABAA Ed3 39/725

1 Generalities
− sub-networks can be defined in levels 1, 2 or 3

− ATM NEs can be defined in levels 2, 3 or 4

− ENEs can be defined in all levels
A sub-network may contain sub-networks (except in last level), ATM NEs and/or
ENEs
Alcatel
1.4.1.2 ATM NE and ENE

An ATM NE is defined as telecommunication equipment. It corresponds physically
to the ATM card of an ISA NE (ATM matrix).
For the purpose of network management, NEs are to be considered in terms of their
actual or potential connections.
An ENE represents an NE or a set of NEs not managed by the 1354 BM, for
example an ATM NE contained in an adjacent sub-network not accessible by the
1354 BM manager, but linked to a managed NE by a transmission path.
1.4.1.3 Transmission path, IMA transmission path (IMA group), IMA link
The transmission paths represent the ATM physical links providing the ATM traffic
transport. SDH paths support them.
An IMA transmission path (= IMA group) transports the ATM traffic into multiple
links (nxE1, VC-12 or VC-3) called IMA links. Each IMA link is supported by one
SDH path. At least one IMA link must exist on an IMA transmission path.
The interface type and the possible use of a transmission path / IMA transmission
path depend on the location where the NEs that support the transmission path
extremities are:
− NNI (Network to Network Interface): both extremities are on NEs belonging to
the same network
− ICI (Inter-Carrier Interface): one extremity is on an NE belonging to another
network
− UNI (User Network Interface): one extremity is on an NE belonging to a user
network
Both ICI and UNI interfaces can be used only for hard routing services, while the
NNI can be used for both hard and soft routing.
The operations on the transmission paths / IMA transmission paths are entirely
dependent upon the 1354 BM operator who must see to the usage of the effective
bandwidth.
For a transmission path, the effective bandwidth is the effective bandwidth of the
corresponding SDH path.
3AG 86577 ABAA Ed3 40/725

1 Generalities
For an IMA transmission path, the effective bandwidth is the sum of around 99% of
the effective bandwidth of each IMA link (corresponding to the effective bandwidth
of the SDH path).
A possible scenario is, if at the time of the demand of the ATM provisioning PVC,
there are not sufficient resources, then the 1354 BM operator can ask for the
creation of the transmission path or add an IMA link on the IMA transmission path.
Alcatel
Once the transmission path / IMA transmission path is established, it becomes

available resources for the PVC management after the configuration of its
characteristics.
Several PVCs may use the same transmission path / IMA transmission path
according to the available capacity.
1.4.1.4 ATM termination and ETP

A transmission path links two terminations.
A termination can represent:

− An ATM termination located in a NE.
− An External Termination Point (ETP) located in an ENE.
ATM termination:
An ATM termination is represented by a SDH Trail Termination Point (TTP)

associated:
− to a Transmission Path to Virtual Path Adapter (TP/VP_A) (see Figure 1-11)
− or to a Transmission Path to IMA Adapter (TP/IMA_A) (see Figure 1-12).
It corresponds to a physical port of the ATM NE available to the ATM handling.
3AG 86577 ABAA Ed3 41/725

1 Generalities
SDH matrix
Alcatel
SDH TTP SDH TTP

(bit rate = VC-3) (bit rate = VC-4)
TP/VP_As
ATM card
ATM NE
Figure 1-11 ATM termination (TP/VP_A)
In the previous case, the transmission path termination located in an ATM NE is

represented by the SDH TTP associated to a TP/VP_A.
SDH matrix
SDH TTP
(bit rate = VC-3)
TP/IMA_A
IMA_T
IMA/VP_A(3xVC-3) ATM card
ATM card ATM NE
Figure 1-12 ATM termination (TP/IMA_A)
In this case, the transmission path termination located in an ATM NE is represented

by the SDH TTP associated to a TP/IMA_A.
3AG 86577 ABAA Ed3 42/725

1 Generalities
External Termination Point (ETP):

The 1354 BM also manages a list of ENEs to house the unmanaged terminations of
transmission paths.
An ETP represents a transmission path termination located in an ENE (see the

figure below).
Alcatel
SDH matrix
SDH TTP SDH TTP

(bit rate = VC-3) (bit rate = VC-4)
STM-1
card SDH NE
ETP
ENE
External sub-network
Figure 1-13 Termination on ENE
Before the transmission path creation, a set of SDH TTPs must be defined.
For this, the 1354 BM specifies bit rates of all SDH TTPs in the ATM NE
according to the ATM matrix capacity.
This request is sent to the 1354 RM via the ISN dispatcher (by zooming of the SDH
TTPs definition application).
The 1354 RM is in charge of the creation/deletion of the requested SDH TTPs.
The associated TP/VP_A is automatically created (by NE). Then the 1354 BM gets
the set of the existing SDH TTPs via the ISN dispatcher.
3AG 86577 ABAA Ed3 43/725

1 Generalities
1.4.1.5 Transmission path / IMA transmission path partition

With the aim of managing better the available bandwidth, the user needs to know at
any time how much bandwidth it stays in each transmission path / IMA
transmission path and which type of VPC he can again create.
Alcatel
For that purpose, the notion of physical and logical bandwidth is introduced.
Physical bandwidth:
Physical bandwidth is defined as being the real bandwidth of a transmission

path. It can never exceed 100 %.
Logical bandwidth:
This notion of logical bandwidth is introduced to allow to the user to:

- control its bandwidth following the type of VPC which he wishes to create
- specialize the transmission path if needed (a transmission path can carry only
DBR Class 1&2 or DBR Class U (=UBR) and so on).
So, the physical bandwidth could be shared between four logical partitions:
− DBR Class 1&2 partition,
− DBR Class U partition,
− UBR+ partition,
− SBR partition.
For each partition, the maximum bandwidth can be limited to a percentage of the
bandwidth.
The sum of percentages can be greater than 100% of the total bandwidth of the
transmission path.
When creating the transmission path, default values are proposed. They can be
modified.
Each partition represents a logical resource management even though the

transmission path manages physical resources.
Sharing the Transmission Path bandwidth allows to provide a way to control it,
according to operator's needs. For example, it may be interesting to dedicate the
bandwidth only to DBR Class 1&2 traffic type.
Transmission Path partition operation aims to share the physical bandwidth of a

transmission path between the different traffic contracts available (DBR Class 1&2,
DBR Class U, UBR+ and SBR) in order to limit the number of DBR Class U VPC
(without reserving physical bandwidth) and to preserve the DBR Class 1&2 VPC,
UBR+ VPC priority.
This is called partitioning.
3AG 86577 ABAA Ed3 44/725

1 Generalities
The following rules are followed concerning DBR Class U connections:

− DBR Class U cells are sent during the silences of other type of connections
(DBR Class 1&2, UBR+ and SBR); in case of bandwidth overload at given
time, DBR Class U cells, which have the lowest priority, are delayed.
− No physical bandwidth is reserved for the DBR Class U connections.
− The number of DBR Class U connections of a Transmission Path is limited
Alcatel
to a max value, according to its bit rate.
The allocation of DBR Class 1&2 (or UBR+ or SBR) VPC reserves bandwidth in
logical (DBR Class 1&2 (or UBR+ or SBR) partition) and physical resources of
each involved transmission path.
The allocation of DBR Class U VPC only reserves bandwidth in logical (DBR
Class U partition) resources of each involved transmission path.
The reserved bandwidth is defined by a configuration parameter (This parameter

allows to limit the number of DBR Class U VPC).
3AG 86577 ABAA Ed3 45/725

1 Generalities
Partitions : This partition does not reserve any

bandwidth on the transmission path
Hard_BW_Available DBR ClassU PARTITION Total bandwidth of

Alcatel
DBR ClassU partition

Hard_BW_Used (logical)
TRANSMISSION PATH (HARD)

Total bandwidth
of transmission path Hard_BW_Available
(physical)
DBR Class1 PARTITION Total bandwidth of
DBR Class1 partition (logical)
Hard_BW_Used
Hard_BW_xx are cell rates.
Figure 1-14 Transmission path partition
Hard_BW_Available: available bandwidth on a given partition. This indication is

computed by 1354 BM for each direction (forward / backward) each time a Hard
VPC is allocated or de-allocated and when the partition characteristics are changed.
Hard_BW_Used: used bandwidth on a given partition by allocated, implemented,

commissioned Hard VPCs and by uploaded connections (Plug&Play). This
indication is computed by 1354 BM for each direction (forward / backward) each
time a Hard VPC is allocated or de-allocated and when the partition characteristics
are changed.
This possibility is reserved for the transmission path with the hard routing service.
3AG 86577 ABAA Ed3 46/725

1 Generalities
1.4.2 Network management

Once the network topology is built, the user can establish Permanent Virtual
Circuits (PVC) between NEs (ATM NEs or ENEs) and manage them.
Alcatel
VCL VCL
VPL VPL VPL
NE NE NE NE
Termination Termination
VPL_T VPL_T VPL_T
VPL_T VPL_T VPL_T VP_T VP_T VP_T
VP_T
VCL_T VCL_T VCL_T VCL_T
VC_T VP cross-connect VC cross-connect VC_T
Transmission path
PVPC
PVCC
VP_T: Virtual Path Termination VPL_T: Virtual Path Link Termination
VC_T: Virtual Channel Termination VCL_T: Virtual Channel Link Termination
VPL: Virtual Path Link VCL: Virtual Channel Link
VP_T and VPL_T identify VPi

VC_T and VCL_T identify VPi/VCi
VPL identifies transmission path and VPi used on it
VCL identifies VPC and VCi used on it
Figure 1-15 PVC point-to-point representation
PVC is a generic term used to indicate a PVPC or a PVCC.
PVPC and PVCC are the ATM connections. They are hierarchically layered: the
PVCC are held by PVPC which themselves are held by Transmissions Paths.
A PVPC is composed of a VPL or a concatenation of cross-connected VPLs. Each

PVPC may use one or several transmission paths.
3AG 86577 ABAA Ed3 47/725

1 Generalities
A unitary PVPC is made of only one VPL.

A PVCC is composed of a VCL or a concatenation of cross-connected VCLs. Each

PVCC may use one PVPC or several cross-connected PVPCs.
A unitary PVCC is made of only one VCL.

Alcatel
A PVC may be hard or soft, according to the way the connection is established.
1.4.2.1 Hard PVC

To establish a hard PVC, the operator has to create hard PVPCs (or hard PVCCs)
by specifying the extremities and the characteristics of each of them.
Then the 1354 BM determinates the PVPC (or PVCC) routes, checks if the
available bandwidth is sufficient and configures the ATM matrix of the concerned
NEs.
A hard PVC can be point to point or point to multi-points.
Operator has the possibilit y to define flexible unitaries hard PVPCs that use a
specific traffic profile without any characterist ic (ATC, PCR, MCR, CDVT, ...).
This kind of PVPC does not consume any bandwidth of the transmissio n path.
1.4.2.2 Soft PVC

A soft PVC can be only point to point.
The 1354 BM manages two kinds of soft PVCs:
− Transit soft PVCs:
ENE ATM NE ENE

ATM NE
1354 BM managed network

VP_T
Transit Soft PVPCs
Soft PVCC
Figure 1-16 Transit soft PVC
The soft PVPC goes from an ENE to another ENE.

Soft PVCCs are carried transparently by the soft PVPC.
− Infrastructure soft PVCs:
3AG 86577 ABAA Ed3 48/725

1 Generalities
ENE ATM NE ATM NE ATM NE ATM NE ENE
VP_T 1354 BM managed network

Alcatel
Infrastructure Soft PVPCs

Soft PVCC
Figure 1-17 Infrastructure soft PVC
The soft PVPC has one or two extremities in the managed network and goes from
an ENE to another ENE. Soft PVCCs are carried transparently by the soft PVPC.
An infrastructure soft PVPC uses a calling endpoint and a called endpoint.
The calling endpoint always belongs to an ATM NE. It is associated to a

connection endpoint that is a VP termination. The calling endpoint and the
connection endpoint are connected together by a hard PVPC (or hard PVCC)
dedicated to the soft PVC management (i.e. assigned to a VP tunnel).
The called endpoint may belong to an ATM NE or an ENE.
If the called endpoint belongs to an ATM NE, it is associated with a connection

endpoint, like the calling endpoint.
Resulting Soft PVC

ATM N E
ATM N E Soft PVC Hard PVC 2 or EN E
Hard PVC 1
or EN E
Connection endpoint 1 Calling endpoint Called endpoint Connection endpoint 2

VP_T or VC_T VPL_T or VCL_T VPL_T or VCL_T VP_T or VC_T
Figure 1-18 Soft PVC with called endpoint on ATM NE
If the called endpoint belongs to an ENE, no connection endpoint is managed and it

can be supported by the soft PVC.
3AG 86577 ABAA Ed3 49/725

1 Generalities
Resulting soft PVC

ATM N E Hard PVC 1 Soft PVC EN E

or EN E
Connection endpoint 1 Calling endpoint Called endpoint

Alcatel
VP_T or VC_T VPL_T or VCL_T VPL_T or VCL_T
Figure 1-19 Soft PVC with called endpoint on ENE
To establish a soft PVC, the operator has to create soft PVPCs (or soft PVCCs) by
specifying the extremities and the characteristics of each of them. Then the 1354
BM sends the request of the PVC establishment to the calling NE (at an extremity).
PNNI is in charge of determining the route and establishing the PVC.
1.4.2.3 Routing management

In the aim to manage hard PVCs and soft PVCs, one part of each transmission path
is dedicated to the hard PVC routing service and the other one is reserved to the soft
PVC routing service (PNNI management).
So as to share the resources between both services, the operator indicates for each
transmission path the percentage of the bandwidth and the VPI/VCI ranges
dedicated to the PNNI management.
This information can be configurable (given by default). Then, in function of these

values, at the transmission path creation, the resources are attributed by default to
the hard PVC routing service or to the PNNI management. The split information is
downloaded to the TP/VP_As at the extremities of the transmission path.
Depending on the respective need of each routing service, the operator can modify
the mean of distribution concerning the free resources without disturbing the traffic.
In release R7, all the resources of a transmissio n path are completely dedicated
either to the hard PVC routing service or to the soft PVC routing service (only 0%
or 100% of a resource can be dedicated to hard or soft routing service).
In both cases, at the PVC definition the couple ATC - QoS has to be provided.
Therefore, the traffic descriptor format depends on the ATC and QoS values.
3AG 86577 ABAA Ed3 50/725

1 Generalities
1.4.2.4 UPC/NPC management

The UPC/NPC (Usage Parameter Control / Network Parameter Control)
management consists in activating/deactivating an ATM police control on a given
PVC. If the traffic contract assigned to a PVC is not respected by a user, the
connection is automatically cut.
Alcatel
1.4.2.5 Output shaping

The output shaping is used to delay some cells in order not to overflow the
negotiated PCR. That function may be activated/deactivated on a PVC by the
operator.
Three shaping protection mode are available.
Grooming
Figure 1-20 Shaping protection mode : Grooming
Edge
Figure 1-21 Shaping protection mode : Edge
3AG 86577 ABAA Ed3 51/725

1 Generalities
Grooming + Edge

Alcatel
Figure 1-22 Shaping protection mode : Grooming + Edge
1.4.2.6 Point-to-multi-points PVC management

This functionality provides an unidirectional point-to-multipoints PVC in order to
allow the traffic broad-cast.
It is clearly used at VC level for all VCCs and at VP level for the VPCs between
ENEs.
A point-to-multipoints PVC is composed of one or more legs.
A leg is a point-to-point, unidirectional PVC.
Each leg starts from the same origin extremity as the point-multipoints PVC but
ends on a specific destination extremity. The point-multipoints PVC is so the
aggregation of all legs composing it.
For this, a point-to-multipoints PVC has at least one unidirectional point-to-

multipoints connection: it is a connection where two (or more) link terminations are
cross-connected each one to another link termination. This is a broadcast point.
All legs of a given point-to-multipoints PVC share the same resources from the
origin extremity and till the broadcast point.
Point-to-multipoints connection performs the ATM Cell multicast function.
3AG 86577 ABAA Ed3 52/725

1 Generalities
The NE provides two kinds of multicast technics:

Spatial multicast: The cross-connection of the point-to-multipoints root is based

on different Transmission Paths (i.e. The multiple cell copies (of received traffic
flow) have to be sent to different Transmission Paths).
Logical multicast: The cross-connection of the point-to-multipoints root is based

Alcatel
on the same Transmission Path and have the different VPI/VCI values (i.e. The
multiple cell copies share the same transmission Path and have to be sent with
different VPI/VCI values).
The two next figures describe hard PVPC and hard PVCC point-to-multipoints
presentations.
3AG 86577 ABAA Ed3 53/725

1 Generalities
VPC Leg 1
VPL 11 VPL 12 VPL 13

Alcatel
Origin ENE ATM NE ATM NE Leg 1 Destination ENE
VPL_T Root VPL_T Leaf VPL_T VPL_T

VPL_T VPL_T
VP_T VP_T
Leaf VPL_T
VP cross-connect VP cross-connect
1 n 1 1
Broadcast point
ATM NE
Leg 2 Destination ENE
VP cross-connect
1 1
VP_T
Transmission Path Termination
Hard VPC
VPC Leg 2
VPL 21 VPL 22 VPL 23
VP_T: Virtual Path Termination
VPL: Virtual Path Link VP_T and VPL_T identify VPi

VPL identifies Transmission Path and VPi used on it
VPL_T: Virtual Path Link Termination
VP_T:
In theVirtual
figure,Path
VPL Termination
11 and VPL21 share the same resources.
Figure 1-23 PVPC point-to-multipoints presentation
3AG 86577 ABAA Ed3 54/725

1 Generalities
VCC Leg 1
VCL 11 VCL 12
VPL VPL VPL
Origin ENE ATM NE ATM NE Leg 1 Destination ENE

Alcatel
VP_T VPL_T VPL_T VP_T
VPL_T VPL_T
VPL_T Root VCL_T Leaf VCL_T VPL_T
VCL_T VCL_T
Leaf VCL_T VP cross-connect
VC_T 1 n VC cross-connect 1 1 VC_T
ATM NE Leg 2 Destination ENE
Transmission Path VP cross-connect

1 1
VCL_T
VPC VC_T
VPL_T VPL_T VP_T
VPL_T
Termination
VCC
VCC Leg 2
VCL 21 VCL 22
VPL VPL VPL
VP_T: Virtual Path Termination
VPL_T: Virtual Path Link Termination
VPL: Virtual Path Link
VP_T and VPL_T identify VPi VC_T: Virtual Channel Termination

VC_T and VCL_T identify VPi/VCi VCL_T: Virtual Channel Link Termination
VPL identifies Transmission Path and VPi used on it
VCL: Virtual Channel Link
VCL identifies VPC and VCi used on it
In the figure, VCL 11 and VCL21 share the same resources.
Figure 1-24 PVCC point-to-multipoints presentation
3AG 86577 ABAA Ed3 55/725

1 Generalities
1.4.2.7 Overbooking management
The overbooking functionality is the capability to allocate more bandwidth than the
physical line allows.
Actually, if bandwidth for the maximum requirements of every connection is

Alcatel
provided in a network, it results in a high service quality, but it also causes low
network usage, because all connections do not continually operate at maximum
bandwidth at the same time.
In order to provide increased connections, overbooking can be performed.
It provides a high network utilization, but during peak usage periods, the service
quality will be low on all the connections (and not only on those which are
overbooked). Which means that congestion problems such as cell lost could occur.
The transmission path is managed as if it has a higher bandwidth than its real bit-
rate; but in this way, the ATM NE admits more connections than the Qos
guarantees allow.
The overbooking is not allowed for DBR Class 1 connections, allowed for the
others.
It has an impact on the partitioning transmission path management.
Two 1354 BM independent parameters (modifiable constantly without connection

deletion) allow to reserve less bandwidth than the actually used for a connection:
− Overbooking factor:
Has to be configured at transmission path level during the definition of the
transmission path characteristics (see chapter § 3.4.11).
Overbooking factor can have a value from 100% to 1000% (default value =
100%).
Equal to 100% means overbooking is not enable.
Greater than 100% means that NE admits more connections than usual. Cell loss
and cell delay guarantees are forfeited for all connections.
Example: Overbooking factor equal to 200% means that the reserved bandwidth
is divided by 2.
− Utilization factor:
Has to be configured at VPL level during the Hard PVPC definition (see chapter
§ 4.1.2) and at VCL level during the Hard PVCC definition (see chapter § 4.3.2)
(not allowed for Soft PVPC/PVCC).
Utilization factor can have a value from 1% to 100% (default value = 100%).
− Equal to 100% means the reserved bandwidth is used at 100%.
3AG 86577 ABAA Ed3 56/725

1 Generalities
− Less than 100% means a reduction of the reserved bandwidth of the

concerned hard PVPC/PVCC.

For the hard PVPC (which contains the hard PVCC with utilization factor
modified), it permits to create more hard PVCCs.
For the transmission path (which contains the hard PVPC with utilization factor
modified), it permits to create more hard PVPCs.
Alcatel
Example: Utilization factor equal to 50% means that the reserved bandwidth is
divided by 2.
3AG 86577 ABAA Ed3 57/725

1 Generalities
1.4.3 Maintenance management

The maintenance management includes:
− the fault management (see § 1.4.3.1)
− the Operation And Maintenance (OAM) management (see §1.4.3.2)
Alcatel
1.4.3.1 Fault management

The 1354 BM provides the following functions about the PVC failure management:
− current alarm management
− alarm history management
− acknowledgement management
− fault localization management
− surveillance points management (also called Non Intrusive Monitoring (NIM))
Current alarm management

As soon as an alarm is generated, a current alarm entity is created in the 1354 BM
and added in the list of current alarm.
So, the alarm status of the origin entity is updated following the severity of the
alarm.
The current alarm list is updated, in real time, according to any new generation of
alarm or end of alarm.
When an alarm is generated, a current alarm entity is created and when an alarm is
ended, the current alarm entity is deleted.
If it is a TP/VP_A alarm, the 1354 BM retrieves the transmission path, which is

impacted by this alarm and updates its availability status. This alarm is not
propagated on the PVPCs and PVCCs carried by this transmission path.
If it is a TP/IMA_A alarm, the 1354 BM retrieves the IMA link, which is impacted
by this alarm and updates its availability status.
If it is an IMA_T or IMA/VP_A alarm, the 1354 BM retrieves the IMA

transmission path (= IMA group), which is impacted by this alarm and updates its
availability status.
If it is a VP_T or a VPL_T alarm, the 1354 BM retrieves the PVPC, which is

affected by this alarm and updates its availability status. This alarm is not
propagated on the PVCCs carried by this PVPC.
If it is a VC_T or a VCL_T alarm, the 1354 BM retrieves the PVCC, which is

affected by this alarm and updates its availability status.
If it is an ATM NE alarm, the 1354 BM retrieves the NE, which is affected by this
alarm and updates its operational state.
3AG 86577 ABAA Ed3 58/725

1 Generalities
When the 1354 BM receives a message indicating that an alarm has been cleared, it
deletes the associated current entity alarm from the current alarm list and updates
the availability status of the transmission paths or PVCs which were impacted by
this alarm.
Each availability status modification of a PVC or of a transmission path is logged in

an alarm history.
Alcatel
The list below resumes the different probable causes of alarms and the physical
entities, which are impacted by these alarms:
Probable cause : Physical Entity Fault Severity

communication alarms (default)
Alarm Indication signal (AIS) VP_T, VC_T, VPL_T, VCL_T Warning
Loss of Cell Delineation (LCD) TP/VP_A, TP/IMA_A Major
Remote Defect Indication (RDI) VP_T, VC_T, VPL_T, VCL_T, Warning

IMA_T
Loss Of Continuity (LOC) VP_T, VC_T, VPL_T, VCL_T Minor
Trail Signal Degraded (TSD) IMA/VP_A Major
Loss Of IMA Frame (LIF) IMA_T Major
Link Out of Delay IMA_T Major

Synchronization (LODS)
Trail Signal Fail (TSF) TP/VP_A, IMA/VP_A, Major

TP/IMA_A
Resource Isolation ATM NE Critical
Transport Path not working SDH path (RM) Major
Alarm category: threshold Physical Entity Fault Severity

crossing (default)
Alarm when a threshold is TP/VP_A, IMA/VP_A Minor

crossed (TCA)
3AG 86577 ABAA Ed3 59/725

1 Generalities
NE.1 NE.2 NE.3

Alcatel
cross-connect
TSF a la rm TP/ VP_A

UnplugN E.1 AIS a larm on VP_T
Transmission Path
VPC
Figure 1-25 Example of Trail Signal Fail alarm and Alarm Indication Signal alarm
NE.1 NE.2 NE.3
cross-connect
TSF a la rm on TP/ VP_A Unplug N E.2 TSF a la rm on TP/ VP_A
Transmission Path
VPC
Figure 1-26 Example of Trail Signal Fail alarm
3AG 86577 ABAA Ed3 60/725

1 Generalities
NE.1 NE.2 NE.3

Alcatel
cross-connect
AIS a larm on TP/ VP_A TSF a la rm on TP/ VP_A RDI a larm on TP/ VP_A
Transmission Path
Cut of Tx
VPC
Figure 1-27 Example of Trail Signal Fail, Alarm Indication Signal and Remote Defect
Indication alarm
3AG 86577 ABAA Ed3 61/725

1 Generalities
Alarm history management

The alarm history contains the current alarm and the alarms, which have been
cleared.
Alcatel
Acknowledgement management
The failure management offers the possibility to acknowledge a current alarm.
When a new alarm occurs, a signal is emitted to inform the operator. As long as the
alarm has not been taken into account, the signal is emitted. To stop it, the operator
has to acknowledge the alarm.
Fault localization management
The fault localization management offers the possibility to display information on

the physical entities (TP/VP_A, VPL_T, VCL_T) alarms on a transmission path,
hard/soft PVPC or PVCC.
Surveillance points management (also called NIM)

Surveillance points provide a capability for assessing the status, the connectivity or
the performance of a PVC point-to-point or point-to-multipoints (end-to-end) at
intermediate points using non-intrusive monitoring (NIM).
The defined non-intrusive monitoring functions are:

− VP AIS/RDI state detection
− Loss of continuity defect detection
These function may be activated / de-activated separately per PVC.
They are non-intrusive in the sense that, when activated, the ATM cell transfer
performance of the PVC should not be affected.
Non-intrusive monitoring of any type (AIS NIM, RDI NIM, CC NIM) of end-to-
end PVC may be performed at any intermediate point along the PVC.
3AG 86577 ABAA Ed3 62/725

1 Generalities
Two kinds of surveillance points are available in 1354 BM:

1) NIM points are used for AIS or RDI alarm detection on the PVC's intermediate
points.
By default, the points on which can raise alarms, are the transmission path or
PVC endpoints. The operator may want to make the alarm raise possible on
Alcatel
intermediate points of a PVC.
On cross-connected VPL_Ts / VCL_Ts of a PVC, there are potentially two NIM

points by VPL_T / VCL_T: a NIM point for the incoming (ingress) direction and
a NIM point for the outgoing (egress) direction.
NIM points are created on PVC at least allocated and they become operational
only when PVC is at least implemented.
Figure 1-28 NIM points presentation
To create or to delete NIM points, the operator has the possibility to choose:
− a transmission path:
NIM points could be created on all VPL_Ts and / or VCL_Ts of all the PVCs
passing through the chosen transmission path.
−or a PVC:
from a PVC NIM list, NIM points could be created on a selected NE user label /
TP/VP_A / VPI / VCI and for incoming (ingress) / outgoing (egress) direction.
2) NIM CC = surveillance points used for OAM services such as continuity

check
Continuity check detection may be activated on the surveillance points created for
loss of continuity (LOC) detection (see § 1.4.3.2).
3AG 86577 ABAA Ed3 63/725

1 Generalities
1.4.3.2 OAM management

The OAM management consists in:
− estimating the quality of service (QoS) of a PVC
− detecting possible deterioration or failure in a PVC
Alcatel
The available functions are:

− Continuity Check (CC). The CC function tests the continuity on a PVC
end-to-end or on a PVC segment. If the continuity is not respected, an alarm is
emitted.
− Loopback (LB). The LB function assures the smooth running of a PVC
end-to-end or of a PVC segment. (not implemented in BM R7)
− Performance Monitoring (OAM PM). The OAM PM function estimates the
quality of a PVC end-to-end or of a PVC segment. (not implemented in BM R7)
In order to determine performance provided by the ATM layer, surveillance actions
must be carried out. For that the OAM flow of the ATM layer is used.
There are two flows:

− F4, for the supervision of the virtual path
− F5, for the supervision of the virtual circuits
The OAM flow of the ATM layer is always implemented in the same way.
The information is carried by specific cells: the OAM cells.
These performance supervision cells are recurrent with a minimal frequency (an
OAM cell for about N user cells) which results in a compromise between the
precision of the measure and overflow caused by the maintenance flow which
penalises the available capacity for the user traffic.
The OAM cells of the F4 flow have the same VPI values as the user cells of the
PVPC and are identified by a pre-assigned VCI value.
The OAM cells of the F5 flow must take the same physical path as the PVCC. The
distinction is made thanks to the PT field, which indicates the nature of the cell.
The F4 and F5 flows can be established:

− either on the entire PVC
− either on PVC portions, called “Segment”
3AG 86577 ABAA Ed3 64/725

1 Generalities
A segment may cover:

− a single PVC bi-directional link connection

− a single PVC bi-directional matrix connection i.e a PVC bi-directional sub-
network connection delimited by the Connections Points (CPs) located at the
ingress/egress of an ATM NE
− a concatenation of PVC bi-directional link connections and PVC bi-directional
Alcatel
matrix connections.
Continuity Check management
This OAM service is performed by inserting OAM CC cells into the user cell flow
of a segment at insertion points, to check the continuity of the cell flow at detection
points.
Insertion points may be one endpoint of the segment (see 1 & 1' in Figure 1-29
Continuity Check service activation on a bi-directional segment), while detection
points may be the other segment endpoint (see 2 & 2') but also surveillance points
(called NIM CC).
The OAM CC cell may be insert and retrieve from an ENE, so this OAM service is
possible even if a PVC has not insertion points and / or detection points.
The figure below describes the different operations needed to manage Continuity
Check on a segment and specifies on which points (segment endpoints and
surveillance points) these operations can apply. The segment is supported by a bi-
directional PVC, and has been defined as bi-directional itself.
2 2 Segment 2
1
ingress egress
egress ingress
1’
2’
2’ 2’
ATM NE ATM NE
ATM NE
OAM CC cells insertion (optional) OAM CC cells detection (mandatory) OAM CC cells detection (optional)
1 OAM CC cells insertion activation in A to Z direction 1’ OAM CC cells insertion activation in Z to A direction
2 OAM CC cells detection activation in A to Z direction 2’ OAM CC cells detection activation in Z to A direction
egress
Cross-connected VPL_T/VCL_T : “After matrix” NIM Point (i.e. outgoing)
PVC endpoint ingress : “Before matrix” NIM Point (i.e. incoming)
Figure 1-29 Continuity Check service activation on a bi-directional segment
OAM CC cells detection could be done if NIMs have been created at cross-
connected VPL_T / VCL_T points.
3AG 86577 ABAA Ed3 65/725

1 Generalities
1.4.4 Performance management

The Performance Monitoring (PM) consists in informing the user about possible
default on an NE or in a PVC.
The performance monitoring uses performance counters that can be activated by the
Alcatel
user. When a counter threshold is crossed, an alarm event report is sent.
The thresholds can be set or modified by the user.
The PM primitives are divided into two categories:

− the non-OAM PM primitives are related to events local to the NE (e.g received,
transmitted or discarded cells). The purpose is the maintenance of Transmission
Paths, and the connection management of PVCs.
− the OAM PM primitives are associated to the PM OAM flow, to monitor the
quality of service of a PVC or a segment.
The OAM PM of a PVC segment is performed by inserting OAM cells into the
transmitted user information cell stream.
OAM cells may be introduced into the cell stream at any VP or VC termination or
connecting point, and may be observed or extracted at any similar point
downstream.
Measurement methods based on OAM functions use information:

− carried by the performance monotoring OAM cells
− gathered at the point where performance is estimated
The PM can be activated/deactivated. It is deactivated by default. The operator
should explicitly activate it.
The PM data collection and history process applies to both the non-OAM PM and
OAM PM counters to provide the 15min and 24h current and history data.
Graphical or textual reports on PM counters are available from PMDS application

(see § 2.2.4).
3AG 86577 ABAA Ed3 66/725

1 Generalities
1.4.5 Administration management

The administration services offered by the 1354 BM are:
− the Private Network to Network Interface (PNNI) management
− the ATM traffic management
Alcatel
− the Virtual Network (VN) management (*)
(*) This function is not implemented in release R7.
3AG 86577 ABAA Ed3 67/725

1 Generalities
1.4.5.1 PNNI management

The PNNI defines the organisation of the Peer Groups (PG).
A peer group is a collection of logical nodes (physical NEs or logical group nodes)
grouped for purposes of creating a routing hierarchy.
Alcatel
A12 PG (B)
PG (A1) PG (A2)
B1
B2
B2 B3
A11
B4
A1 A2
PG (A) A1
PG (A)
A B
Lowest level node LGN Peer group leader
Horizontal link (physical)

Horizontal link (logical)
(i.e ATM transmission path
Uplink
with resources dedicated to soft PVC)
Figure 1-30 PNNI peer group representation
PNNI hierarchy is organised like a tree of PGs, so each PG is belonging to a level

of the tree.
The peer groups are populated with logical nodes. There are two kinds of logical
nodes: lowest level nodes and Logical Group Nodes (LGN).
The LGNs are “virtual” nodes that can be used to summarise a peer group while
lowest level nodes are used to model equipment. So, an equipment can be
composed of several logical nodes, one lowest level node and n LGNs.
3AG 86577 ABAA Ed3 68/725

1 Generalities
The routing hierarchy and the configuration of each logical node are defined by the
ATM network administrator. Then, at the network activation the logical nodes
discover them automatically, and provide the hierarchy defined by the
administrator.
In 1354 BM R7, only a simple PNNI (called flat PNNI) has been implemented.
This consists in only using the notion of lowest level node.
Alcatel
1.4.5.2 ATM Traffic management

This function allows the management of:
− the traffic descriptors
− the traffic profiles
1.4.5.3 VN management
A Virtual Network (VN) is a set of functions and resources associated to each
customer.
A set of VNs is predefined. This distribution cannot be updated since it does not
appear to be necessary to modify it. This set is made of:
− one VN including all transmission paths
− one VN including all public resources (transmission path and VPLs)
− one VN per customer including his resources (transmission path, VPLs, PVPCs,
VCLs and PVCCs)
The VN management allows the following functions:

− VN resource addition, modification and deletion
− VN checking
Some indicators associated to a VN are provided, such as performance counters and
alarms.
3AG 86577 ABAA Ed3 69/725

1 Generalities
1.4.6 Utilities
The utilities offered by the 1354 BM are:
− Plug & Play (also called NE discovery)
− Time scheduling (*)
Alcatel
− PNNI audit (*)

− NE audit
− NE alignment
− NE force alignment
(*) These functions are not implemented in release R7.
1.4.6.1 Plug & play

The plug & play feature is useful to discover the Transmission Paths and the hard
PVCs created without using 1354 BM or before having installed it.
The objectives of this feature are as follows:

− Traffic descriptor discovery
− Upload the SDH transmission paths
− Transmission path characteristic discovery
− Hard PVC discovery
− Clean-up (*)
(*) Not implemented in release R7.
The plug & play applies on the set of ATM NEs given by the operator or on all
ATM NEs defined in 1354 BM.
3AG 86577 ABAA Ed3 70/725

1 Generalities
1.4.6.2 NE audit
This tool is used to detect differences between the 1354 BM database and the ATM
NE Management Information Base (MIB).
Audit can be performed on one ATM NE, on a list of ATM NEs or on all ATM
NEs managed by the 1354 BM.
Alcatel
During this step, the tool does a difference between data stored in 1354 BM and
data read from equipment MIB. The result is stored in a text file (ASCII format).
This file contains:
a) Entities existing into 1354 BM database but not into equipment MIB,
b) Entities existing into equipment MIB but not into 1354 BM database,
c) Entities existing both into equipment MIB and in 1354 BM database but with
some different values.
1.4.6.3 NE alignment
This tool is used to align the ATM NE MIB with the contents of the 1354 BM
database (see case a) in previous paragraph).
Plug & Play utility is in charge of 1354 BM database alignment (see case b) in
previous paragraph).
Concerning entities with different attributes (see case c) in previous paragraph), it

is up to the operator to decide which is the right value (MIB or 1354 BM database)
and to modify (using 1354 BM GUI or 1320 CT) the entity attribute.
Values used to align equipment MIB are read from the text file produced during
the audit phase.
Alignment can be performed on one ATM NE, on a list of ATM NEs or on all
ATM NEs managed by the 1354 BM.
For the selected ATM NEs, the 1354 BM downloads its data towards the ATM
NEs.
3AG 86577 ABAA Ed3 71/725

1 Generalities
1.4.6.4 NE force alignment

This tool is used to force the ATM NE MIB to reflect the exact image of the 1354
BM database (regarding transmission and connections domains only).
If an element is present in the 1354 BM database but not in ATM NE MIB, it is

crated in the ATM NE MIB.
Alcatel
If an element is present in the ATM NE MIB but not in the 1354 BM database, it is
deleted in the ATM NE MIB.
If an element is present in ATM NE MIB and in the 1354 BM database with

different characteristics, the ATM NE MIB is aligned with the 1354 BM database
taken as reference.
3AG 86577 ABAA Ed3 72/725

1 Generalities
1.4.7 System management

The main system management offered functions concern the operator profile
management.
The System management is taken in charge by the System Management Function

Alcatel
(SMF) external application of ALMAP.
For more information about SMF, refer to the SMF documentation [3].
1.4.7.1 Operator profile management

This set of service is based on the following concepts:
− FAD:
Set of functional access domains, e.g. a set of management functions.
− NAD:
Set of network access domains, e.g. a set of functional resources that may be:
− an ETP
− indirectly Transmission Path for which their NAD is inherited from their
terminations
− a hard PVPC
− a hard PVCC
− Initiator:
Gives the access rights on the NAD. By default, they are seven initiators:
“Administrator”, “Free Pool”, "NAD1", …., "NAD5".
The “Free Pool” NAD is a pool of resources that can be used by all 1354 BM
users. The “BM Administrator” NAD groups resources that can only be used
by the user that have the “BM Administrator” initiator.
NAD of the resource Required initiator to modify the NAD of the resource
BM Administrator BM administrator
Free Pool BM administrator, Free Pool
Other BM administrator, Other
3AG 86577 ABAA Ed3 73/725

1 Generalities
− Operator profile:
Set of FADs that an operator will be allowed to access.

− User:
Operator identified by a login and a password and associated to one operator
profile and one initiator.
Alcatel
A user must be assigned to no more than one operator profile. A user is only
allowed to access the management functions and the management entities
included in his operator profile and his initiator he have been assigned to.
− Access control database:
The database which contains all the information relative to the access control
management, e.g. users, operator profiles, operator profile assignments and so
on.
The actors who interact with this set of services are the following:
− The administrator, a kind of user allowed to administer the 1354 BM
application and to operating system.
− The network constructor who has rights to only manage the sub-networks, NE,
ENE and transmission paths.
− The network manager who has rights to configure and get information about
the network.
− The viewer who has rights to only get information about the network.
− The north interface manager who has rights to configure and get information
about the network (transmission paths, PVPCs, PVCCs entities).
− The north interface viewer who has rights to only get information about the
network (transmission paths, PVPCs, PVCCs entities).
For more details on available operations for each actor, please refer to chapter 10.2.
The operator profile management allows only for the administrator users, the
following functions:
− user creation (= association of one operator profile + one initiator to an
operator), modification and deletion.
3AG 86577 ABAA Ed3 74/725

1 Generalities
1.5 System environment
1.5.1 General environment

The 1354 BM is currently implemented with the 1354 RM and the 1353 NM
Alcatel
software products.
1354 BM and 1354 RM (or/and 1353 NM) could be co-hosted (software are
installed on the same workstation (or server)).
1.5.2 User interface

The 1354 BM has a dual-user interface, which means that operators can access the
1354 BM functions by using command lines or a graphical interface.
Moreover, an operator can use the 1354 BM from an HP workstation or a PC

terminal.
When the 1354 BM software is running, the software execution is distributed

among the HP workstation and the various PC terminals connected to the
workstation.
The 1354 BM is multi-user, which means that several operators can have access to
1354 BM functions at the same time.
Actually, due to the system architecture, there could be one operator connected on
the HP workstation and one operator connected on each PC terminal.
3AG 86577 ABAA Ed3 75/725

2 User interface overview

Alcatel
This chapter gives general information about the 1354 BM

user interface.
2.1 Generalities
2.2 Getting started
2.3 Administering the 1354 BM
2.4 Main view
2.5 Accessing the functions
2.6 Window menu
2.7 Main menu
2.8 View menu
2.9 Help menu
3AG 86577 ABAA Ed3 76/725

This chapter contains the following sections:

Generalities: gives some general information for using the user

interface
Getting started: describes how to access the user interface
Administering the 1354 BM:
Alcatel
gives the rules of 1354 BM administering

Main view: presents the first view that is displayed at user
interface launching
Accessing the functions:
presents all the ways to access the user interface
functions
Window menu: explains how to make active a window
Main menu: explains how to set user’s preferences and exit the
user interface
View menu: explains how to access the graphical views and
navigate within them
Help menu: describes the help mechanisms provided by the user
interface
2.1 Generalities
This section gives some general information useful for the 1354 BM user interface
user, such as:
vocabulary used in the user interface (refer to § 2.1.1)
user interface windows (refer to § 2.1.2)
window management (refer to § 2.1.3)
selection rules (refer to § 2.1.4)
string character agreement (refer to § 2.1.5)
sensitive help (refer to § 2.1.6)
buttons (refer to § 2.1.7)
3AG 86577 ABAA Ed3 77/725

2.1.1 Vocabulary used in the user interface

Active Describes the selected window or icon.
Click Press and release the left or right mouse button.
Command Word or phrase, usually found in a menu, that you choose
Alcatel
in order to carry an action.

Contextual menu On network display window and list window, menu
related to the currently selected object and displayed by
clicking with the right mouse button.
Dialog box Window used to display a question to the user.
Drag and drop Direct mouse action to move an object. First, by selection
of the object beneath the cursor with the left mouse button,
then dragging it anywhere, keeping the left mouse button
pushed. At the chosen right place, a final drop of the left
mouse button stops the move.
Menu bar Horizontal bar located at the top of the main view under
the title bar and containing the menus.
Message box Window used to display a message to the user.
Multi-select Select several objects.
Pointer Graphical symbol that identifies the current position on
screen.
Resource That word indicates an object which is manageable by the
1354 BM (ATM NE, ENE, transmission path, PVC,…).
Scroll Move text or graphics up or down or left or right, in order
to see parts of the window content that cannot fit on the
screen.
Select Indicate one object by left clicking on it.
Sensitive help In a window with text entry fields, if available (the cursor
becomes a hand shape), the sensitive help provides the
user with a list of values to be used for filling out the field.
Open the sensitive help window with a right mouse click,
hold the button and select the desired value in displayed
list.
System bar Located in most of the windows, that bar allows the user
to iconify, minimise / maximise and close the window.
Tab key In a window with text entry fields, use the Tab key to
move from field to field.
Title bar Horizontal bar located at the top of a window and
containing the window title. On many windows, the title
bar also contains the system bar.
Tool tip A tool tip provides information about a component or area
when the user rests the pointer on it (and does not press a
3AG 86577 ABAA Ed3 78/725

mouse button). These small rectangles of text can be used

anywhere in your application. A tool tip is commonly

associated with an interface element, where it provides a
short description of the component's function.
Toolbar Horizontal bar located at the top of the main window
under the menu bar and containing the shortcut icons. The
toolbar is divided into two parts: general toolbar and
Alcatel
contextual toolbar.
Tree Part of the main view, the tree presents the network in a
hierarchical way.
Window Rectangular area on the screen, used to view an
application or a document. Each window has a title bar
and some of them have a menu bar and two scroll bars.
The labels used in the 1354 BM windows are explained in chapter 9.
2.1.2 User interface windows

The different types of window are as follows:
− Main view
− Graphical views
− List windows
− Data display windows
− Data acquisition windows
− Dialog and message boxes
Each type of window has its specificities, as described hereafter.
3AG 86577 ABAA Ed3 79/725

2.1.2.1 Main view

The main view is the first window that appears at the user interface launching and
from which the user can access all the 1354 BM features.
Alcatel
Figure 2-1 Example of a main view
The main view is described in section 2.4. It displays all the views and windows
described hereafter.
3AG 86577 ABAA Ed3 80/725

2.1.2.2 Graphical views

A graphical view represents the network topology by using graphical symbols.

Each graphical view represents an aspect of the network topology from a specific
point of view.
Alcatel
Figure 2-2 Example of a graphical view
3AG 86577 ABAA Ed3 81/725

There are two main types of graphical views:

− The sub-network views display the content of a specific sub-network with

geographical aspects.
− The global views display the network topology with hierarchical aspects.
Alcatel
A graphical view contains, from top to bottom:

− a title bar that displays, from left to right:
− an icon corresponding to the content of the window
− the type of graphical view (Sub-network or Global)
− the name of the domain (Hard Trans. Path, …)
− the name of the sub-network (Root, …)
− a system bar (refer to § 2.1.3)
− a graphical area that displays a set of symbols representing sub-networks, NEs,
ENEs and transmission paths. The background is a map or a neutral pattern.
Two scroll bars allow the user to navigate within the graphical area if it is larger
than the graphical view.
The selection rules in a graphical view are described in § 2.1.4.
The View menu (refer to § 2.8) allows the user to access the graphical views and
navigate within them.
3AG 86577 ABAA Ed3 82/725

2.1.2.3 List windows

A list window allows the user to get information about a type of resource.
Alcatel
Figure 2-3 Example of a list window
A list window contains, from top to bottom:

− the name of the list (Sub-network, Transmission Path, …)
− sometimes, an acquisition area (ex : Parent Subnetwork User Label)
− a list area in the form of a table
− an information area that displays, from left to right:
− the number of Elements currently listed
− an indication on the filters used (No Filters or Free use)
The selection rules in a list window are described in § 2.1.4.
Each column can be resized and moved. By default, the width of a column is
adapted to the size of its title.
To resize a column:
− Move the cursor on the right line of the column head. The cursor becomes a
double-arrow.
− Drag and drop this double-arrow either to the left to reduce the width of the
column or to the right to extend it. The widths of the other columns increase or
decrease proportionally.
3AG 86577 ABAA Ed3 83/725

To move a column,
− Drag and drop the column head.

When a data does not appear entirely in the list, the user can point it by using the
mouse. This opens a small box showing the whole data.
Some columns use colours to draw the user’s attention to the data they contain.
Alcatel
Sorting
One or several columns of the list window may be used as sorting criteria.
There are three sorting order:

− ascending order
− descending order
− creation order
By default, the elements of the lists are sorted by creation order on the identifier
(User Label or Id.) column.
To change the sorting order of a column, click on its header as many time as
necessary. At each click, the column header becomes as shown in Figure 2-4 to
Figure 2-6.
Figure 2-4 Example of descending order
Figure 2-5 Example of ascending order
3AG 86577 ABAA Ed3 84/725


Alcatel
Figure 2-6 Example of creation order
To change the sorting criteria, click on the header of another column that may be
used as sorting criterion. The order by default is ascending.
Filtering
Filters may be applied to all the list windows in order to facilitate the search of an
element in the list. To know what filters are currently used, look at the Filters field
at the bottom of the list window.
When a window is open, a default filter is applied so that all the elements are
brought back. The default values displayed in the Filters field are ‘*’ for a string
and ‘All’ for fields allowing a limited number of values.
The fields used as filtering criteria are chosen in a separate window (search
window) which is called from the list window either by using the contextual
menu, the contextual toolbar or the menu bar. Clicking on the Ok button in the
search window applies the filter.
The icon of the toolbar will stay sunken if there is a current active filter.
3AG 86577 ABAA Ed3 85/725

2.1.2.4 Data display windows

A data display window allows the user to get information about a resource.
Alcatel
Figure 2-7 Example of a data display window
A data display window contains, from top to bottom:

− the name of the window
− an information area
Such a window is read-only. Nothing may be entered.
To close the window, click on the cross in the system bar.
3AG 86577 ABAA Ed3 86/725

2.1.2.5 Data acquisition windows

A data acquisition window allows the user to enter some parameters, in most
cases at the creation of a resource.
Alcatel
Figure 2-8 Example of a data acquisition window
A data acquisition window contains, from top to bottom:

− the name of the window
− an acquisition area
− two buttons (Ok, Cancel)
To move from a field to another one, you can use the Tab key.
The white fields are to be filled in. When a field is optional, its label is in italics.
Fill out the fields then click either on Ok or on Cancel:

− Clicking on Ok validates the modifications and executes the action related to
the window. If the operation is successful, the window is closed and an
information message is displayed in the status bar. Otherwise, the error is
displayed in a message box. At the end, the window is closed.
Pressing the Enter key has the same effect.

− Clicking on Cancel closes the window without taking into account the
modifications. No action is executed.
As soon as Ok is clicked, the action related to the window is launched and cannot
be stopped any more, even by clicking on Cancel.
3AG 86577 ABAA Ed3 87/725

2.1.2.6 Dialog and message boxes

A dialog box allows the 1354 BM to ask the user a question. For example a dialog
box may ask the user for confirming an action.
The main type of dialog box is the confirmation box.

Alcatel
Figure 2-9 Example of a confirmation box
The user has to answer by clicking either on Yes or No:

− Clicking on Yes closes the confirmation box and executes the action, except if
an error is displayed in a message box.
− Clicking on No aborts the action and closes the confirmation box.
For a multi-selection, the confirmation box is as follows:
Figure 2-10 Example of a confirmation box for a multi-selection
If you click on:

− All, the action is performed for all the items selected in the list.
− Yes, the action is performed for the displayed item in the confirmation box.
Then another confirmation box is displayed for the next selected item.
− No, the action is not performed for the displayed item in the confirmation box.
Then another confirmation box is displayed for the next selected item.
− Cancel, the action is not performed for the displayed item and the next ones.
The appearance order of the items in the confirmation boxes is the reverse order
of the list where they are selected.
3AG 86577 ABAA Ed3 88/725

A message box allows the 1354 BM to inform the user. For example a message
box may give the cause of an unsuccessful operation.
The title bar of a message box is slightly different on a PC or an HP workstation,

but the box content is the same.
Alcatel
Figure 2-11 Example of a message box
The user has to acknowledge the message by clicking on OK.
When errors occur during operations performed on a multi-selection, the message

box is as follows:
Figure 2-12 Example of a message box for several selections
The table gives the list of the items on which the wished operations have not been
performed and the reason of the errors.
The user has to acknowledge the message by clicking on OK.
3AG 86577 ABAA Ed3 89/725

2.1.3 Window management

The rules of window management inside the desktop of the main view are as
follows:
− The windows (except the graphical views) are singletons: only one window
Alcatel
instance at a time for each window type. If the opening of a window is

requested when it is already opened, it comes to foreground.
− Window activation can be controlled by using the Window menu (refer to §
2.6).
− Data acquisition windows and data display windows can be only iconified or
closed. The list windows and the graphical views can be also minimized,
maximized and resized.
− Dialog boxes and message boxes can be only moved and closed.
− A list window loses its context (filter rule) when it is closed then open again.
List windows, data acquisition windows and graphical views are refreshed in the
following cases:
− an element is created or deleted
− one of the management states of an element has changed (alarms, …)
Partition windows and properties windows are not refreshed even if an
information has changed. To refresh these windows, the operator has to close
them and re-open them.
System bar
The system bar is displayed in the title bar of any window (except in modal
windows). It can be used to iconify, minimise / maximise and close the window.
Figure 2-13 System bar
Modal windows
Modal windows are not resizable and have to be acknowledged before any other
operation. However they can be closed by clicking either on the x on the top right
(on a PC) or on the – on the top left (on an HP workstation).
Only dialog boxes and message boxes are modal.
3AG 86577 ABAA Ed3 90/725

2.1.4 Selection rules

Simple selections are performed by only using the mouse:
− A left click selects a symbol in a graphical view or a line in a list window.
− Another left click deselects all the previous selections and starts a new one.
Alcatel
In a graphical view, the contour of a selected symbol is highlighted.
In a list window, the background of a selected line is coloured.
Once a symbol or a line is selected, the user can access the contextual menu (refer
to §2.5.3.1).
To de-select a line in a list window or to de-select an object in the tree, use ctrl +
click. In a graphical view, just click outside a symbol (or a line) to de-select it.
Multi-selection
The multi-selection in a graphical view or in a list window allows the user to
perform an operation on several elements.
Multi-selections in a list window

− Shift key
To select adjacent lines, left click on the first line to select it, then press the
Shift key while clicking on the last line to be selected. All the lines between the
first one and the last one are selected. You can also move the mouse while
keeping the left click on.
− Ctrl key
To select several (and not adjacent) lines, press the Ctrl key while left clicking
on the lines.
When a selection begins in a window or in the tree, all the previous selections are
aborted.
Selection rules in a graphical view

Other selection rules specific to the graphical views are described in §.0
From here and in the who le user’s guide, ‘click’ means ‘left click’. Only the right
click is specified.
3AG 86577 ABAA Ed3 91/725

2.1.5 String character agreement

Three types of text entry field exist in the data acquisition windows: Identifier,
User Label and Comment.
The rules to be respected for filling out those fields are as follows (except for the
Alcatel
Search field):
− the size must be <= 60 characters
− the ASCII character values must be > 0x20 (blank character) and < 0x7F
− the forbidden characters are:
− for Identifier and User Label fields: * % ‘ ? { } \ / [ ] | = space
− for Comment fields: * % ‘ ? { } \
2.1.6 Sensitive help

The sensitive help may be sometimes available in a data acquisition window. Its
aim is to help the user to fill out some text entry fields by choosing a value in a
pull-down list.
When the user moves the cursor on a field, for which the sensitive help is
available, the cursor becomes a hand (slightly different on a PC or on a
workstation).
3AG 86577 ABAA Ed3 92/725


Alcatel
Figure 2-14 Example of a field providing sensitive help
When the user right clicks on that field, the list of the available values is
displayed.
Figure 2-15 Example of a sensitive help in action
3AG 86577 ABAA Ed3 93/725

When the pull-down list is displayed, the user can:

− select a value
− in case of a list in form of a tree, expand it (refer to § 2.4.1)
− close the list by clicking in the field to be filled in (in that case, the field remain
empty)
Alcatel
The sensit ive help is only proposed. The user keeps the possibilit y to manually
keyboard a value in the field without using the sensit ive help.
3AG 86577 ABAA Ed3 94/725

2.1.7 Buttons
In most of windows, various types of buttons allows the user to select parameters
or perform actions. In addition to the push buttons (Ok, Cancel, All, Yes, No)
already presented in the previous paragraphs, there are:
− option buttons
Alcatel
− radio buttons
2.1.7.1 Option buttons

The option button is used in some data acquisition windows. It allows the user to
choose a value in a list of predefined values.
Figure 2-16 Example of an option button
To use an option button:

− Click on the option button. The list of predefined values is displayed.
− If the list is very long, search the desired value by entering its first character.
− Click on a value to select it.
− The selected value replaces the previously one displayed on the option button.
2.1.7.2 Radio buttons

The option button is used in some data acquisition windows. It allows the user to
make an exclusive choice.
Figure 2-17 Example of radio buttons
To use radio buttons:

− Click on one of the radio button. A black point appears in the center of the
selected radio button.
3AG 86577 ABAA Ed3 95/725

2.2 Getting started
This section explains how to:

− start the 1354 BM GUI, refer to § 2.2.1
− start the 1354 BM CLI, refer to § 2.2.2
Alcatel
− start the Alarm Surveillance GUI, refer to § 2.2.3

− start the Performance Monitoring GUI, refer to 2.2.4
− administer the 1354 BM, refer to §2.3
2.2.1 Starting the 1354 BM GUI

The way to start the 1354 BM user interface depends on the used hardware (PC or
HP workstation).
2.2.1.1 On an HP workstation
Starting the 1354 BM
To access the 1354 BM user interface from an HP workstation, proceed as follows
from the front panel:
Figure 2-18 Front panel on HP
In the front panel, click on the TMN-OSs Management System icon
Temporarily, an initialization window appears.
Then the TMN-OSs Management main view is displayed.
3AG 86577 ABAA Ed3 96/725


Alcatel
Figure 2-19 TMN-OSs Management main view
TMN-OSs Management main view contains at least one 1354 BM application

icon.
In case of co-hosted configuration, it could be also contain 1353 NM / 1354 RM

applications.
The application icons background can assume different colours and each colour
identifies a different application operational status:
Green colour indicates that the application is in Active status (running).

Blue colour indicates that the application is in Stopped status (not running).
Red colour indicates that the application is in Wrong status (one or more
processes are not active).
Yellow colour indicates that the application is working, but it is not possible to
define one of the previous described operational status.
When the 1354 BM application icon is selected, the operator can access to the
1354 BM functions.
To start the 1354 BM GUI (when the 1354 BM application icon is green), from
the Actions menu, select the Network and Start 1354BM ATM USM command
(or select the icon in the contextual toolbar).
3AG 86577 ABAA Ed3 97/725

Exiting from the 1354 BM

To exit from the 1354 BM user interface, proceed as follows:
In the 1354 BM main view, click on the Main pull down menu, then select the
Exit option. The following confirmation box is displayed:
Alcatel
Figure 2-20 Confirmation box (on HP)

Click on Yes to exit from the 1354 BM.
Clicking on No closes the confirmation box and returns to the main view.
2.2.1.2 On a PC
Accessing the 1354 BM main view

To access the 1354 BM user interface from a PC, proceed as follows:
− In the Windows desktop, double click on the 1354 BM icon. The following
window is displayed:
Figure 2-21 User Authentication window (on PC)

− Enter your Login and your Password.
− Click on Ok.
The Server URL field is automatically filled with the address of the server used
for the connection.
The 1354 BM main view is displayed. The operator can access the 1354 BM
functions.
3AG 86577 ABAA Ed3 98/725

Exiting from the 1354 BM

To exit from the 1354 BM user interface, proceed as follows:

− In the 1354 BM main view, click on the Main pull down menu, then select the
Exit option.
Alcatel
The following confirmation box is displayed:
Figure 2-22 Confirmation box (on PC)

Click on Yes to exit from the 1354 BM.
Clicking on No closes the confirmation box and returns to the main view.
3AG 86577 ABAA Ed3 99/725

2.2.2 Starting the Command Line Interface (CLI)

When the 1354 BM application icon is selected, the operator can access to the
1354 BM functions.
To start the 1354 BM CLI (when the 1354 BM application icon is green), from the
Alcatel
Actions menu, select the Network and Start 1354BM ATM CLI command.
The following window is displayed:
Figure 2-23 Command Line Interface window
The Command Line Interface allows executing commands without using ATM
USM (Abstract CLI syntax is available in § 10.2).
3AG 86577 ABAA Ed3 100/725

2.2.3 Starting the Alarm Surveillance GUI

The Alarm Surveillance (AS) application mainly consists in:
− managing the current alarms
− managing the historical alarms
Alcatel
− managing alarm acknowledgement

− to navigate to 1354 BM fault localization window (except for NE entity)
(Refer to chapter 1 for further details)
To access the AS commands from an HP workstation, proceed as follows from the

front panel (see Figure 2-18 Front panel on HP):
− Click on the TMN-OSs Management System icon. Then the TMN-OSs
Management main view is displayed (see Figure 2-19 TMN-OSs Management
main view)
− From the Actions menu, select the Alarms command (or select the icon in
the contextual toolbar).
Figure 2-24 AS Current Alarm Counter Summary window
3AG 86577 ABAA Ed3 101/725

Eight alarms sub-lists are displayed in the AS main view:

− Network Element
− Transmission Path
− Hard PVPC
− Hard PVPC Leg
Alcatel
− Hard PVCC
− Hard PVCC Leg
− Soft PVPC
− Soft PVCC
To reach a specific alarm sub-list from this window, proceed as follows:

Click on a sub-list (the selected sublist bar becomes black)
Select the Sublist menu
Select Open
The following window is now displayed:
Figure 2-25 As Current Alarm Sublist window: Network Element
From the current alarm sub-list (except from Network Element sub-list), you can:
Display the fault localization list, refer to § 3.4.17 (from a selected

alarm)
For more details about the operations available from these windows, refer to the
document [1].
3AG 86577 ABAA Ed3 102/725

2.2.4 Starting the performance monitoring GUI

Performance data in a network management system is collected for three
purposes:
a) Maintenance
Alcatel
Reports of the ’raw’ collected performance data will give the operator
insight in performance of some parts of the network and can help during
failure analysis.
b) Accounting & Quality

From the collected performance data the path Availability and Quality can
be evaluated and can be used as input for a billing application.
c ) Preventive maintenance
Availability and Quality derived from the collected performance data can be
compared with Availability and Quality thresholds in order to predict if a
path will satisfy the required Quality or not.
The Performance Monitoring Display System (PMDS) module is a reporting

application and creates the following reports:
Maintenance
− Textual report on ’raw’ performance counters
− Graphical report on ’raw’ performance counters
− State Change History report, reports on all path state changes.
Accounting & Quality
− Path Usage report, reporting the Availability and Quality for a path during
a selected report interval.
Preventive Maintenance
− Quality of Path (QOP) Guarding report, reports on all paths crossing the
warning QOP threshold or the critical QOP threshold
− Graphical report on Availability and quality trend.
Furthermore, PMDS offers the capabilities:

− to archive the Performance Monitoring data
− to restore in a dedicated memory space the archived PM data (thus having on
the system two different PM data: the on line PM data and the restored one, on
both it is possible to require reports)
− to manage the schedule report activation.
3AG 86577 ABAA Ed3 103/725

PMDS offers the generation of the following Reports (for ATM counters):
− On-Demand, Graphical Report on «NON OAM» counters;

− On-Demand, Textual Report, formatted for Direct Printing on «NON
OAM» counters (included software thresholds);
− On-Demand, Textual Report, formatted for Direct Printing on Path State
Alcatel
History;
− Scheduled, Textual Report, formatted for Direct Printing on «NON
OAM» counters;
− Scheduled, Textual Report, formatted for Direct Printing on «NON
OAM» counters when defined threshold are exceeded;
− Scheduled, Textual Report, formatted for Direct Printing on Path State
History;
− Scheduled, Textual Report, in CSV format on «NON OAM» counters.
To access the PMDS commands from an HP workstation, proceed as follows from

the front panel (see Figure 2-18 Front panel on HP):
Management main view is displayed (see Figure 2-19 TMN-OSs Management
main view).
− Select the 1354 BM icon background.
− From the Actions menu, select Performance Monitoring command (or select
the icon in the contextual toolbar).
3AG 86577 ABAA Ed3 104/725

If no PM Measure is available, the following window is displayed:


Alcatel
Figure 2-26 PM Report Request Control window
3AG 86577 ABAA Ed3 105/725

The main window is used to collect the report requests and generate reports. It
consists of these areas:

− The Network Tree area presents a ’Network Tree Filter’ pull–down list
and a tree view on the monitored Performance Entities,
− The Reporting Criteria area consists of several controls to direct the
contents of the report, which consists of 3 sub areas:
Alcatel
- The Report Period area defines the start and end time of this report.
- The Other Criteria area let the operator define granularity, report
destination, report type, report style.
- The Optional area can let the operator do some optional settings,
including selecting performance parameters, setting thresholds and
setting presentation options.
The Status area is a single line, showing the status of the main window.
3AG 86577 ABAA Ed3 106/725

If, at least, one PM Measure is available, the following window is displayed:


Alcatel
Figure 2-27 PM Report Request Control window (with PM Measures)
The available PM measures User Labels are displayed in the Network Tree area.
3AG 86577 ABAA Ed3 107/725

Alcatel
3AG 86577 ABAA Ed3

selected)
Figure 2-28 PM Report Request Control window (with two Performance Entities
108/725
To reach a specific PM report from this window, in RRC Window, do the

following:
(Optional) Choose a filter combination to filter the Performance Entity tree.
The operator can do filtering by choosing one certain filter or a combination of
filters. Basic filters available are:
Alcatel
− No Filtering,
− Monitored for 15min,
− Monitored for hour,
− Monitored for day,
− Monitored (Any granularity).
In addition, there is one filter that can be co-used to do the filtering:
Monitored As Active,
After filtering, the performance entity tree will show only those performance
entities that match the filtering criteria.
Select Performance Entities in the Performance Entity tree.
One or more Performance Entities may already be selected. The following
actions are allowed to manipulate the set of selected Performance Entities:
− Open a branch in the selection tree by clicking the [+] sign,
− Close a branch in the selection tree by clicking the [–] sign,
− Select a single Performance Entity by clicking on the Performance Entity
label. All Performance Entities that were already selected will be
deselected,
− Select multiple Performance Entities by using the <Ctrl> key (selection
and deselecting of a single Performance Entity) and the <Shift> key
(selection of a range of Performance Entities).
(Optional) Use ‘search’ functions to select Performance Entities in the

Performance Entity tree.
Four searches are provided:
− Search TP by Name and Type
− Search TP by Value
− Search Measure
− Search Transport
(Optional) Select Performance Parameters of the selected Performance Entities

(all supported performance parameters are selected by default),
(Optional) Set threshold for Performance Entities,
(Optional) Set presentation options for the report that will be generated,
Set Reporting Criteria (report period, granularity, report destination, report type,
report style),
3AG 86577 ABAA Ed3 109/725

The Reporting Period can be specified on four ways:
1) User Selection Period

The operator must enter the ’From Date and Time’ and the ’To Date
and Time’ manually.
Alcatel
The From Date starts at the earliest of 1 January 1970, the To Date ends
at the latest of 31 December 2037. The pre-selected periods are grayed–
out.
2) The Last Period
The operator can choose from the following options:
• 15min: last 15 minutes
• hour: last hour
• day: yesterday
• week: last week
• month: last month
• year: last year
The ’From Date and Time’ and the ’To Date and Time’ are updated
automatically according to the selected period and cannot be modified
anymore.
3) The current period
• 15min: these 15 minutes
• hour: this hour
• day: today
• week: this week starting with Monday
• month: this month
• year: this year
The ’From Date and Time’ and the ’To Date and Time’ are updated
automatically according to the selected period and cannot be modified
anymore.
4) The Last … Until period
• 15min: 15 minutes
• hour: 1 hour
• day: 24 hours
• week: 1 week
3AG 86577 ABAA Ed3 110/725

• month: 1 month
• year: 1 year
The ‘To Date and Time’ is entered by the operator manually. The
’From Date and Time’ is updated automatically according to the
selected period and cannot be modified anymore.
Alcatel
A Reporting Period cannot be set for Reference Value Reports.
Operator can use the up and down arrow key to roll the selected time fields
quickly.
Selecting Granularity from a list of selectable Granularities. Granularity

cannot be set for Reference Value Reports.
Specifying the Report Destination:
• Screen, Mail, File or Printer.
Specifying the Report Type:

PCT – Performance Counter Tabular Reports
PCG – Performance Counter Graphical Reports
PSH – Path State History Reports
PAR – Path Accounting Reports
AQT – Availability and Quality Trend Reports
QPG – Quality of Path Guarding Reports
CMP – Comparison Reports
REF – Reference Value Reports (entry fields for Granularity and
Reporting Period are grayed–out for this Report Type).
Specifying the Report Style:
• Tabular or Graphical.
Typically the report style is changed automatically according to the

selected Report Type. Operator only has to specify the report style if the
selected Report Type supports both 2 Report Styles. For example, ‘CMP’
report type.
3AG 86577 ABAA Ed3 111/725

− Trigger the Report Generation using the Apply button.

The contents of the report that will be generated depending on the current
set of Selected Performance Entities and Reporting Criteria, Manipulate
Reports (tabular or graphical report...).
Alcatel
If the chosen report style is Graphical, the following window is displayed:
Figure 2-29 Performance Counter Graphical window
3AG 86577 ABAA Ed3 112/725

If the chosen report style is Graphical, the following window is displayed:


Alcatel
Figure 2-30 Performance Counter Tabular window
3AG 86577 ABAA Ed3 113/725

2.3 Administering the 1354 BM

The administration functions consist in:
− list the EML-IM, adding one EML-IM and removing one EML-IM
− setting the 1354 BM parameters
Alcatel
− display the 1354 BM log file
To access these functions, click on the TMN-OSs Management System icon

from the front panel (see Figure 2-18 Front panel on HP).
Then the TMN-OSs Management main view is displayed (see Figure 2-19
TMN-OSs Management main view).
Administration functions are available from the Actions menu of this view.
3AG 86577 ABAA Ed3 114/725

2.3.1 List of EML-IM

From the TMN-OSs Management window, menu: Actions => Administration
=> EML-IMs Management
The fo llowing window is now displa yed:

Alcatel
Figure 2-31 EML-IM List window
EML-IM state column is not refreshed automatically. Refresh button is to be used

to do this.
From the List of EML-IMs list window, you can:
Add an EML-IM, refer to § 2.3.1.1
Remove an EML-IM, refer to § 2.3.1.2
3AG 86577 ABAA Ed3 115/725

2.3.1.1 Add an EML-IM
From the List of EML-IMs window, select the Add button.

Alcatel
Figure 2-32 Add one EML-IM window
To add an EML-IM, enter the following data:

− name of the EML-IM (authorized characters: [a..z], [A..Z], [0..9], _ , # )
− EML domain number of the EML-IM
− data concerning the station on which the 1353 NM is installed:
− NM IP address
− NM hostname
− NM instance namef: the full instance name of NM
(ex: 1353NM_<X-Y.Z>)
3AG 86577 ABAA Ed3 116/725

- If you are in the NM cluster configurat ion:
• the NM IP address has to be completed with the virtual NM IP

address and not with the phys ical NM IP address,
Alcatel
• the file /etc/hosts has to be updated manually in adding the physical

NM IP addresses.
2.3.1.2 Remove an EML-IM

From the List of EML-IMs window, select one EML-IM in the list and click on,
Remove button.
Figure 2-33 Confirmation box to remove an EML-IM
After confirmation, the EML-IM is removed from the List of EML-IMs.
3AG 86577 ABAA Ed3 117/725

2.3.2 Set the 1354 BM configuration parameters

From the TMN-OSs Management window, menu: Actions => Administration
=> Set 1354 BM Parameters
Alcatel
Figure 2-34 1354 BM Parameters Definition window
3AG 86577 ABAA Ed3 118/725

To change the configuration parameters, proceed as follows:

− Click on a value field.

− Modify the parameter (repeat these two operations as many times as needed).
− In Actions menu of the window, select Apply & Exit command.
The configuration parameters are now updated.
Alcatel
3AG 86577 ABAA Ed3 119/725

2.3.3 Display 1354 BM log file

From the TMN-OSs Management window, menu: Actions => SMF => Log
Management
The main Log Management window appears:

Alcatel
Figure 2-35 Log Management window
In the Log File area, select the '1354 BM ATM System Log' item. Then, the Logs
Records area displays the 1354 BM Log events:
Figure 2-36 1354 BM Log File window (from Log Management window)
3AG 86577 ABAA Ed3 120/725

A dynamic 1354 BM Log File window is automat ically launched and is

posit ioned in the top of the screen, on a blue font, on the workstation/server where
1354 BM is launched (= started from the Process Monitoring Control so ftware).
Alcatel
Figure 2-37 1354 BM Log File window
3AG 86577 ABAA Ed3 121/725

2.4 Main view
The main view is the first window displayed at user interface launching.
Alcatel
Figure 2-38 Main view
The elements composing the main view are as follows:

− Title bar:
− contains the product name:“1354 BM” and the system bar.
− Menu bar:
− contains the titles from which pull down menus and cascading menus are
open. The menu bar displayed depends on the user profile.
3AG 86577 ABAA Ed3 122/725

− General and contextual toolbars:

− displays shortcut icons to access the main 1354 BM functions. For more
detailed information about the general toolbar, refer to § 2.5.3. The
contextual toolbar depends on the desktop active window (refer to §
2.5.3.1).
Alcatel
− Desktop:
− displays all the other windows.
− ATM resources tree:

− the tree area shows all the managed ATM resources in a hierarchical way.
For more information about the use of the tree, refer to § 2.4.1
− Status bar:
− displays from left to right:
− the user’s login
− the user’s profile
− the connection status
Icon Meaning
It indicates that the GUI is no more connected to the application

as long as the load of this is too important. The GUI is not
refreshed.
It indicates that the GUI is re-connecting to the application. At

the end of this re-connection, the GUI is refreshed.
No icon
It indicates that the GUI is connected to the application. The
GUI is refreshed continuously.
− the title of the active window or the result of the last performed action
− the Alcatel logo
The relative sizes of the tree and desktop areas may be modified by using the drag
and drop mechanism on the vertical separation bar.
3AG 86577 ABAA Ed3 123/725

2.4.1 Using the tree

Meaning of the symbols
The symbols used in the tree area are as follows:
Symbol Meaning
Alcatel
Closed directory
Open directory
Closed sub-network directory
Open sub-network directory
NE operational
NE not operational
ENE
Transmission path (IMA or not), hard / soft PVPC / PVCC
IMA transmission path in failure
Elements of the list are not displayed
A directory represents a set of network items of the same type (sub-network, NE,
ENE, transmission path, hard / soft PVPC / PVCC).
When everything is all right, all the symbols are as above, apart from the ENE
symbols that are always grey (not significant).
− For an NE, this means its alarm status is None (no alarm).
− For a transmission path, a PVPC or a PVCC, this means its availability status is
Normal.
− For a sub-network directory, this means all the elements it contains are all
right.
The symbol appears in the tree when there are too many elements to be
displayed for the selected directory.
By default, the symbol appears when the list to be displayed is greater than 40
elements.
Click on the symbol to open the associated list in the main view.
If the list is lower than 40, all concerned element are listed in the tree.
3AG 86577 ABAA Ed3 124/725

If a problem occurs, the green colour is replaced by another colour or by another

symbol:
− For NE, the green square is replaced by a square with a red cross ( ).
Alcatel
− For transmission paths, PVPCs and PVCCs (if they are implemented or
commissioned), the green sphere is replaced by a symbol depending on the
availability status.
Availability status Symbol
Degraded
In failure
− For a sub-network directory, this depends on the elements it contains:

− If the contained elements are NEs, the sphere takes the colour of the NE
whose alarm status is in the highest severity.
− If the contained elements are transmission paths, PVPCs or PVCCs, the
sphere is replaced by the symbol of the element whose availability status
is the most serious.
3AG 86577 ABAA Ed3 125/725

Tree structure

Alcatel
Figure 2-39 Tree structure
The first level directories (‘Construction’ and ‘Management’) are used for the
classification only. No action is available from them.
The ‘Construction’ directory contains the ‘Network Elements’ and ‘Transmission

Paths’ directories.
The ‘Network Elements’ is divided into sub-network directories that contain NEs
and ENEs gathered in ‘NE’ and ‘ENE’ sub-directories.
The ‘Management’ directory contains the ‘Hard PVPC’, ‘Hard PVCC’, ‘Soft
PVPC’ and ‘Soft PVCC’ directories. Each of them is divided into sub-network
directories that contain the corresponding entities.
Available actions
3AG 86577 ABAA Ed3 126/725

To open/close a directory or a sub-directory, either double-click on its name or

click on the symbol located right on the left.
To perform actions from the tree, the user must use the contextual menu (refer to
§ 2.5.4). The actions available in this contextual menu depend on the selected
symbol.
Alcatel
3AG 86577 ABAA Ed3 127/725

2.5 Accessing the functions
The functions of the 1354 BM user interface may be accessed:

− from the menus
− from the icons
Alcatel
− from the contextual menus

− from the tree
2.5.1 From the menus

To access a function, click on the desired menu in the menu bar of the main view.
Example: to access the Transmission path creation function from the menus:
− Click on the Construction menu, then select the Transmission Paths option.
The Transmission Path List window is displayed.
− Click again on the Construction menu, then select the Create option.
The Transmission Path Creation window is displayed.
A greyed menu option means it is not available because it cannot apply to the
current select ion.
When po int ing a menu or a menu option with the mouse, a small box appears to
briefly indicate its meaning or the reason why it is greyed.
3AG 86577 ABAA Ed3 128/725

2.5.2 From the icons

To access a function, click on the desired icon in the general or contextual toolbar.
Example: to access the Transmission path creation function from the icons:
− If a graphical view is displayed:
Alcatel
Click on the icon.
− If no graphical view are displayed:
Click on the icon.
Click on the icon.
The Transmission Path Creation window is displayed.
A greyed icon means it is not available because it cannot apply to the current
select ion.
When po int ing an icon with the mouse, a small box appears to briefly indicate its
meaning or the reason why it is greyed.
In the main view, the icons are displayed in the toolbar.
The toolbar is divided into two parts:

− the general toolbar
− the contextual toolbar
3AG 86577 ABAA Ed3 129/725

2.5.3 General toolbar

The general toolbar is always available. It contains the following icons:
Icon Equivalent menu option Displayed window
Main => Print Not available in release R7.

Alcatel
Reload all information showed

to the operator (*)
Sub-network View –
View => Sub-network View => Hard => Hard Transmission Path Domain
Transmission Path Domain - Root
Construction => Sub-networks Sub-network List
NE / ENE List
Construction => NE / ENE (NE panel)
NE / ENE List
Construction => NE / ENE (ENE panel)
Construction => Transmission Path Transmission Path List
Management => Hard => VPC Hard VPC List
Management => Hard => VCC Hard VCC List
Soft VPC List

Management => Soft => VPC (Description panel)
Soft VCC List
Management => Soft => VCC (Description panel)
(*) Reload button:
Click on this button to reload all information showed to the operator.
In some cases, showed information is not relevant any more. The choice was to
close corresponding windows during the reload:
− the tree: it remains opened in the same state as before the reload except when a
name of sub-network changed, the corresponding sub-network is closed if it
was opened.
− graphical views: if the name of the shown sub-network changed or do not exist
any more, the corresponding view is closed.
− lists: if the list does reference to an entity which does not exist any more or
which changed name, it is closed (ex: the list of the legs of one PVC).
− properties window, bandwidth load window, extremities window: if the entity
does not exist any more or if its name changed, the window is closed.
3AG 86577 ABAA Ed3 130/725

2.5.3.1 Contextual toolbar

The icons available in the contextual toolbar depend on the current displayed
window (graphical views or list windows) and the current selection.
Graphical views
Alcatel
When a graphical view is active in the desktop of the main view, the contextual
toolbar may contain the following icons:
Icon Equivalent menu option Displayed window

Sub-network view displayed
View => Back (contextual) just before
Sub-network view displayed
View => Forward (contextual) just after
Sub-network view showing the
parent sub-network
View => Up (contextual)
Sub-network view showing the
main sub-network
View => Root (contextual)
Construction => Sub-networks
then Create (contextual) Sub-network Creation
Construction => NE
then Define (contextual) Available NE List
Construction => ENE

then Create (contextual) ENE Creation
Construction => Transmission Paths
then Create (contextual) Transmission Path Creation
Sub-network view
showing the content of a
View => Open Sub-network (contextual)
sub-network or the links
or View => Show Link List (contextual)
contained in a grouped
link
View => Properties (contextual) Properties
View => Delete (contextual) Dialog box to confirm the

delet ion
Other icons may be available but there are completely explicit.
3AG 86577 ABAA Ed3 131/725

List windows
When a list window is active in the desktop of the main view, the contextual
toolbar contains only explicit icons.
Alcatel
Figure 2-40 Example of a contextual toolbar for a list window
2.5.4 From the contextual menu

The contextual menu allows the user to access all available operations applicable
on the selection
A contextual menu can be displayed in a list window, a graphical view or the tree
area of the main view.
Figure 2-41 Example of a contextual menu
To access a function, select one or several symbols in a graphical view or a line in

a list window or an element in the tree area of the main view, then click with the
right mouse button.
Example: to access the Transmission path creation function from a graphical

view by using the contextual menu:
− Select the NE origin and the NE / ENE destination.
− Click on the right mouse button. The contextual menu is displayed.
− Select the Create Transmission Path option.
The Transmission Path Creation window is displayed with User Label fields for
Origin and Destination already filled.
3AG 86577 ABAA Ed3 132/725

If a contextual menu is also requested outside the current selection, the selection is
aborted.
The contextual menu is updated according to the active window and the selection.
The same principle as for the menu bar is used to add, remove and shadow options
in the contextual menu.
Alcatel
Those options are in the same state as their associated menu options in the menu
bar and their associated icons in the toolbars.
A greyed contextual menu option means it is not available because it cannot apply
to the current select ion.
When po int ing a contextual menu option with the mouse, a small box (called tool
tip) appears to briefly indicate its meaning or the reason why it is greyed.
2.5.5 From the tree

From the tree, the user can access to all available operations applicable on the
selected selection.
A contextual menu is displayed in the tree area when the user selects one symbol
and then clicks with the right mouse button.
2.5.6 Conventions
From here and in the whole user’s guide, the access to the functions of the
1354 BM user interface will be given by using the menu bar.
3AG 86577 ABAA Ed3 133/725

2.6 Window menu

Alcatel
Figure 2-42 Example of a Window menu
The Window menu allows the user to:

− arrange the windows open on the desktop (refer to § 2.6.1)
− choose the active window (refer to § 2.6.2)
2.6.1 Arrange the windows

By using the Windows Arrangement item of the Window menu, the user accesses
a sub-menu proposing five ways of displaying the current windows.
The figures below illustrate those arrangements.
The windows that cannot be resized keep the same dimensio ns.
3AG 86577 ABAA Ed3 134/725

Alcatel
3AG 86577 ABAA Ed3

Before arranging the windows
Figure 2-43 Example of a desktop before arranging the windows
135/725
Alcatel
3AG 86577 ABAA Ed3

Horizontally tile arranging
Figure 2-44 Desktop with horizontal tile arrangement
136/725
Alcatel
3AG 86577 ABAA Ed3

Mostly horizontally tile arranging
Figure 2-45 Desktop with mostly horizontal tile arrangement
137/725
Alcatel
3AG 86577 ABAA Ed3

Vertically tile arranging
Figure 2-46 Desktop with vertical tile arrangement
138/725
Alcatel
3AG 86577 ABAA Ed3

Mostly vertically tile arranging
Figure 2-47 Desktop with mostly vertical tile arrangement
139/725
Cascade arranging

Alcatel
Figure 2-48 Desktop with cascade arrangement
The tile arrangement applies only to non-iconified windows when the cascade
arrangement concerns all the windows.
3AG 86577 ABAA Ed3 140/725

2.6.2 Choose the active window

The Window menu displays all the windows currently open on the desktop of the
main view. A tick indicates the active window.
To activate another window, click on the corresponding title in the Window menu.
Alcatel
3AG 86577 ABAA Ed3 141/725

2.7 Main menu
The Main menu allows the user to set its preferences and exit from the user
interface.
It includes the following options:

Alcatel
− Print… : not yet implemented in 1354 BM R7.

− Reload : to resynchronize all opened elements.
− Options : to change the user preferences.
The options are as follows:
− Show / Hide Toolbar: to make visible or not the toolbars
− Show / Hide Tree: to make visible or not the tree area
− Close : to close the current window.
− Exit : to exit from the 1354 BM user interface.
3AG 86577 ABAA Ed3 142/725

2.8 View menu
The View menu allows the user to access the graphical views and navigate within
them.
It includes the following options:

Alcatel
− Sub-network view: to display the sub-networks from a geographical point of

view
− Global view: to display the global network from a hierarchical point of view
For each type of view, two options are available:
− Hard: to display hard domain views
− Soft: to display soft domain views
For each domain, three possibilities:
− Transmission Path Domain: to perform actions on sub-networks, NEs /
ENEs (isolated or as extremities of transmission paths) and transmission
paths.
− VP Domain: to perform actions on sub-networks, NEs / ENEs (as
extremities of transmission paths) and PVPC.
− VC Domain: to perform actions on sub-networks, NEs / ENEs (as
extremities of PVPCs), and PVCCs.
When a sub-network view is active, the following options are added:
− Back: to display the view shown before the current view.
− Forward: to display the view shown after the current view.
− Up: to display the parent sub-network view of the current sub-network view.
− Root: to display the root sub-network view.
− Zoom in: to zoom in the current sub-network view (CTRL+Z).
− Zoom out: to stop zoom in the current sub-network view (CTRL+U).
− Select Background: to select the map to be used as background for the current
sub-network view (refer to § 2.8.1).
− Save: to memorize the last map used as a background in all views (refer to §
2.8.2).
Other menu options may be added depending on the graphical view and/or the
selected symbol type: Sub-network, NE, ENE, Transmission Path (refer to § 3).
The sub-network views and the global views use symbols for representing the
elements of the network (refer to § 2.8.3).
The selection rules specific to the graphical views are described in § 2.8.4.
3AG 86577 ABAA Ed3 143/725

2.8.1 Select a background map

This option is available for a sub-network or global view in transmission path

domain. It consists in associating an image as a background of the view.
From the sub-network or global view, menu: View => Select Background
Alcatel
Figure 2-49 Select a New Map for Background window
To choose a map:
− Click on a map in the list. The map appears in the right part of the window.
− When the map is chosen, click on Ok.
The selected map is displayed in the background of the current view.
To memorise that new background map, use the Save option (refer to § 2.8.2) or
quit the active graphical window.
3AG 86577 ABAA Ed3 144/725

2.8.2 Save a sub-network or global view

This option is only available in the transmission path domain.
It consists in saving all views with its last selected background map and the
position of each symbol on it.
Alcatel
From the sub-network or global view, menu: View => Save
The background map and the posit ion of each symbo l are automat ically saved
when:
− the application is closed
− the sub-network or global view is closed
− the operator navigates inside the network
3AG 86577 ABAA Ed3 145/725

2.8.3 Network representation

The symbols used for representing the network are as follows:
Symbo l Meaning
Alcatel
Sub-network
NE operational
ENE
Transmission Path not configured (*)
Hard Link (transmissio n path, PVPC or PVCC) (*)
Soft Link (transmissio n path, PVPC or PVCC) (*)
Grouped links
Off-page connector. Only used in sub-network views

when a link extremit y belo ngs to another sub-network
view
NE with LAC state equal to Granted
NE with LAC state equal to Post-granted
(*) The colours are configurable (refer to the Administration Guide)
3AG 86577 ABAA Ed3 146/725

When all is all right, the sub-network, NE and off-page connector symbols are as
above (surrounded in green).

− For an NE, this means its alarm status is None (no alarm).
− For an off-page connector, this means the alarm status of the NE it represents is
None (no alarm).
− For a sub-network, this means all the elements it contains are all right.
Alcatel
If a problem occurs, the green colour that surrounds the symbol is replaced by
another colour, and/or another small symbol may be added.
− For NEs and off-page connectors, the colour depends on the NE severity alarm
(refer to chapter 9).
− For links (if they are commissioned), another small symbol depending on the
availability status is added to the link symbol.
− For a sub-network, this depends on the states of the elements it contains.
− The surrounder of the symbol takes the colour of the NE whose alarm
status is in the highest severity.
− If the availability status of at least one link contained in the sub-network is
not normal, the small symbol present on the link whose availability status
is the most serious is added to the sub-network symbol.
The table below shows some examples of symbols representing faulty elements.
Symbol Meaning
NE not operational
Link whose availability status is In failure
Grouped link containing at least one link whose availability

status is Degraded
Sub-network whose global alarm status is Major (filled with

orange) and containing at least one link whose availability
status is In failure
3AG 86577 ABAA Ed3 147/725

2.8.4 Selection rules in a graphical view

In addition to those described in § 2.1.4, the graphical views have their own
selection rules.
Double-click
Alcatel
The double–click on each symbol is available and allows the user to visualise a
specific view or open a specific window according to the selected symbol.
− Sub-network: Display, in the current window, the content of the sub-network
− Off-page connector: Display, in the current window, the content of the sub-
network which contains the equipment represented by the off-page connector.
− NE/ENE: Open the NE/ENE properties window
− Link: Open the link extremities window
− Grouped link: Open the link view window
Multi-selection
To select several symbols, press the Shift key while left clicking on the symbols.
A multi-selection of symbols can be moved (by using the drag and drop
mechanism) as a single symbol.
2.8.5 Sub-network views

The sub-network views allow the user to visualise a specific sub-network from a
geographical point of view.
There are three domains:

− Transmission path
− Virtual Path (VP)
− Virtual Channel (VC)
3AG 86577 ABAA Ed3 148/725

2.8.5.1 Sub-network views in transmission path domain

The sub-network views in transmission path domain show the transmission paths
existing between NEs / ENEs that belong or not to sub-networks. At least one
extremity of the transmission path must be in the sub-network.
From the Main view, menu: View => Sub-network View => Hard or Soft =>
Alcatel
Transmission Path Domain
Figure 2-50 Transmission path domain sub-network view
3AG 86577 ABAA Ed3 149/725

The first displayed sub-network view corresponds to the root sub-network. It may
contain only sub-networks, ENEs and transmission paths between them.
From a sub-network view in transmission path domain, you can:

− create sub-networks, NEs (except in sub-network Root), ENEs and
Alcatel
transmission paths
− select a symbol and perform actions from it (refer to chapter 3 and 4)
− open a sub-network (refer to § 2.8.5.4)
− open a grouped link (refer to § 2.8.5.5)
− navigate through an off-page connector (refer to § 2.8.5.6)
− select a background map (refer to § 2.8.1)
− save a sub-network or global view (refer to § 2.8.2)
3AG 86577 ABAA Ed3 150/725

2.8.5.2 Sub-network views in VP domain
The sub-network views in VP domain show the PVPCs existing between NEs /
ENEs that belong or not to sub-networks.
Alcatel
VP Domain
Figure 2-51 VP domain sub-network view
3AG 86577 ABAA Ed3 151/725

contain only sub-networks, ENEs and PVPCs between them.
From a sub-network view in VP domain, you can:

Alcatel
− define PVPCs
− select a symbol and perform actions from it (refer to chapter 3)
3AG 86577 ABAA Ed3 152/725

2.8.5.3 Sub-network views in VC domain

The sub-network views in VC domain show the PVCCs existing between NEs /
ENEs that belong or not to sub-networks.
VC Domain
Alcatel
Figure 2-52 VC domain sub-network view
3AG 86577 ABAA Ed3 153/725

contain only sub-networks, ENEs and PVCCs between them.
From a sub-network view in VC domain, you can:

− define PVCCs
Alcatel

3AG 86577 ABAA Ed3 154/725

2.8.5.4 Open a sub-network
A sub-network may contain NEs, ENEs and/or other sub-networks.
From a Sub-network View, select a sub-network => View => Open Sub-network
Alcatel
Double-clicking on the sub-network symbo l has the same effect.
A new sub-network view replaces the current one and the map disappears.
Figure 2-53 Example of a sub-network view showing the content of a sub-network
3AG 86577 ABAA Ed3 155/725

2.8.5.5 Open a grouped link

A grouped link may contain several transmission paths or several PVPCs or

several PVCCs.
From a Sub-network View, select a grouped link => View => Show Links List
Alcatel
Double-clicking on the grouped link symbo l has the same effect.
Figure 2-54 Example of a link view
In a link view - Hard Transmission Path Domain, you can select a NE to have its
properties or a transmission path then:
− delete it
− display its extremities
− display its properties
− configure it
− display its bandwidth load
− lock/unlock a transmission path
− partition a transmission path
− display the fault localization list (if an alarm impacts the selected transmission
path)
(refer to chapter 3 to have details about these commands).
3AG 86577 ABAA Ed3 156/725

2.8.5.6 Navigate through an off-page connector
An off-page connector symbol represents a NE that belongs to another sub-

network. It can be used to navigate from a sub-network to another one.
From a Sub-network View, select an off-page connector => View => Show Real
Alcatel
Extremity
Double-clicking on the off-page connector symbo l has the same effect.
The view of the sub-network containing the other extremity of the off-page
connector replaces the current sub-network view.
3AG 86577 ABAA Ed3 157/725

2.8.6 Global views

The global views allow the user to visualise the network in its totality. Here, there
are no geographical aspects but hierarchical aspects.
There are three domains:

Alcatel
− Transmission Path
− Virtual Path (VP)
− Virtual Channel (VC)
Any sub-network displayed in a global view can be opened / closed in order to
know what it contains (refer to § 2.8.6.4).
3AG 86577 ABAA Ed3 158/725

2.8.6.1 Global views in transmission path domain

The global views in transmission path domain show the transmission paths
existing between NEs / ENEs that belong or not to sub-networks.
From the Main view, menu: View => Glo bal View => Hard or Soft =>
Transmission Path Domain
Alcatel
Figure 2-55 Transmission path domain global view
The global view displayed by default may only contain sub-networks, ENEs and
transmission paths between them.
From this view, you can:

− create sub-networks, NEs (except in sub-network Root), ENEs and
transmission paths
− expand a sub-network (refer to § 2.8.6.4)
− select a background map (refer to § 2.8.1)
− save a sub-network or global view (refer to § 2.8.2)
3AG 86577 ABAA Ed3 159/725

2.8.6.2 Global views in VP domain

The global views in VP domain show the PVPCs existing between NEs / ENEs
that belong or not to sub-networks.
From the Main view, menu: View => Global View => Hard or Soft => VP
Domain
Alcatel
Figure 2-56 VP domain global view
PVPCs between them.

− define PVPCs
3AG 86577 ABAA Ed3 160/725

2.8.6.3 Global views in VC domain

The global views in VC domain show the PVCCs existing between NEs / ENEs
that belong or not to sub-networks.
From the Main view, menu: View => Global View => Hard or Soft => VC
Domain
Alcatel
Figure 2-57 VC domain global view
PVCCs between them.

− define PVCCs
3AG 86577 ABAA Ed3 161/725

2.8.6.4 Open / close a sub-network

This option applies only on a sub-network symbol. It allows the user to know
what a sub-network contains.
Both following figures illustrate the open / close mechanism applied to a sub-
network as example.
Alcatel
Figure 2-58 Example of a closed sub-network
3AG 86577 ABAA Ed3 162/725

Open a sub-network
From a Glo bal View, select a sub-network => View => Open Sub-network
The global view becomes as follows:

Alcatel
Figure 2-59 Example of an opened sub-network
Close a sub-network
From the Global View, select a NE, an ENE or a link belo nging to a sub-network
=> View => Close Sub-network
The global view becomes as before again.
3AG 86577 ABAA Ed3 163/725

2.9 Help menu
The help is an important aspect of the 1354 BM user interface. By using this
functionality the user can get information on actions he/she is carrying out.
The help is based on the world web technologies. The topics are written in html.
Alcatel
A browser is used to navigate through the html pages.
Access to the 1354 BM help is possible in two different ways: permanent accesses
and access when using the 1354 BM.
− Permanent access: any time the user needs information, he/she can start the
browser and access the 1354 BM. It is not necessary to have a 1354 BM
product running, but just a browser:
Management main view is displayed
− From the Actions menu, select the On Line Help command.
− Access when using the 1354 BM: once launched, the 1354 BM provides the
user with:
− a general help (refer to § 2.9.1)
− a contextual help (refer to § 2.9.2)
3AG 86577 ABAA Ed3 164/725

2.9.1 General help

To access the general help, use the Help menu in the menu bar of the main view.
The Help menu options are as follows:

− Contents and Index: displays the home page of the on line help
Alcatel
Figure 2-60 Home page of the on line help
3AG 86577 ABAA Ed3 165/725

− Search for Help on …: displays the search page of the on line help

Alcatel
Figure 2-61 Search page of the on line help
3AG 86577 ABAA Ed3 166/725

− Glossary: displays the user interface glossary


Alcatel
Figure 2-62 Glossary page of the on line help

− Alcatel on the Web: launchs the Internet browser to the www.alcatel.com
address
− On window: launchs the Internet browser and provides the help concerning the
selected window.
3AG 86577 ABAA Ed3 167/725

− About 1354 BM: displays copyright and version information about 1354 BM

Alcatel
Figure 2-63 Example of an About 1354 BM dialog box
2.9.2 Contextual help

To access the contextual help from any 1354 BM window, there are two
possibilities:
− Press the F1 key
− Use the help menu in the menu bar of the main view and select the “on
window” option.
The on line help opens at the page corresponding to the current active window.
3AG 86577 ABAA Ed3 168/725

Alcatel
3AG 86577 ABAA Ed3

169/725
3 Network construction

Alcatel
The network construction consists in:
3.1 Managing sub-networks
3.2 Managing NEs
3.3 Managing ENEs
3.4 Managing transmission paths
3AG 86577 ABAA Ed3 170/725

The network construction chain gives the order in which the construction must be
performed.
Creating sub-networks
Alcatel
Defining NEs Creating ENEs
Creating transmission paths
Figure 3-1 Network construction chain
3AG 86577 ABAA Ed3 171/725

3.1 Managing sub-networks

In order to be managed more easily the network is structured into sub-networks.
Each sub-network is linked up with a sub-network or the main network.

According to its level, a sub-network may contain other sub-networks, NEs or
Alcatel
ENEs.
The sub-network management, part of the network construction, consists in:

− performing actions such as creating / modifying / deleting sub-networks
− displaying sub-network information such as sub-network list, properties
Several rules must be respected:
− the main network is created by the 1354 BM (root by default namely if it was
not modified during the installation step)
− the main network is only composed of sub-networks and ENEs
The sub-network management chain gives the order in which the available actions
may be performed.
Create s ub-network
Modify sub-network
Delete s ub-network
Figure 3-2 Sub-network management chain
For managing sub-networks, you can:
display the sub-network list, refer to § 3.1.1
3AG 86577 ABAA Ed3 172/725

3.1.1 Display the sub-network list

The Sub-network List window presents all the sub-networks and their attributes.
From the Main view, menu: Construction => Sub-networks

Alcatel
Figure 3-3 Sub-network List window
The attributes displayed for each sub-network are:

− User Label
− Parent Sub-network User Label
− Comment
For column description, refer to chapter 9.
Sort by clicking on the column header that you want to sort.
The sorting criteria are as follows:

− User Label
Filter by clicking on Search in the toolbar.
The search funct ion is available only wit h no selection in the list. For de-select ion
command, refer to § 2.1.4.
3AG 86577 ABAA Ed3 173/725


Alcatel
Figure 3-4 Sub-network Search window
Enter the chosen filtering criteria then click on Ok.
From the Sub-network List window, you can:
create a sub-network, refer to § 3.1.2 (if no sub-network selected)
create a sub-network inside the selected sub-network, refer to § 3.1.2
modify a sub-network, refer to § 3.1.3
delete a sub-network, refer to § 3.1.4
get the sub-network properties, refer to § 3.1.5
3AG 86577 ABAA Ed3 174/725

3.1.2 Create a sub-network

This function consists in adding a sub-network to the main network or to another

sub-network. It is also possible to create a sub-network inside another one.
- The parent sub-network must be previously created.

Alcatel
- The maximum number of sub-network levels must not be reached.
- The maximum number of sub-networks must not be reached.
- The User Label must be different as one which is already used by another sub-
network or one which is reserved for the main network.
From the Main view, menu: Construction => Sub-networks => Create
This funct ion is available only wit h no selection in the list. For de-select ion
From a selected sub-network (in hard or soft transmissio n path domain graphical
views, sub-network list or in the tree) the command beco mes Create inside.
Figure 3-5 Sub-network Creation window
To create a sub-network:
− Enter an User Label.
− Choose the Parent sub-network User Label by using the sensitive help. If a
sub-network has been previously selected in a graphical view or in the tree area
of the main view, this field is automatically filled.
− Enter a Comment (optional).
− Click on Ok.
3AG 86577 ABAA Ed3 175/725

The sub-network is created.

The tree area, the sub-network list and the opened graphical views are updated.
The sub-networks are displayed in bold types in the tree area.
It is then possible to define ATM NEs, ENEs or create a sub-network in this sub-
network.
Alcatel
3AG 86577 ABAA Ed3 176/725

3.1.3 Modify a sub-network

The sub-network modification gives the possibility to modify:

− Sub-network User Label
− Comment
Alcatel
- The sub-network must be previously created.
- If the User Label is modified, the new User Label must be different as one
which is already used by another sub-network or one which is reserved for the
main network.
From the Main view, menu: Construction => Sub-networks => select one sub-
network in the list => Modify
Figure 3-6 Sub-network Modification window
To modify a sub-network:
− Enter a New User Label
− Modify the Comment
Then, the sub-network list, the tree area and the opened graphical views are
updated.
3AG 86577 ABAA Ed3 177/725

3.1.4 Delete a sub-network

This function consists in deleting a sub-network from the 1354 BM supervision.
- The sub-network must be empt y (i.e. containing neit her sub-network neither
NE nor ENE).
Alcatel
From the Main view, menu: Construction => Sub-networks => select one or
several sub-networks in the list => Delete
A confirmation box is displayed.
Figure 3-7 Confirmation box for deleting one sub-network
Figure 3-7 Confirmation box for deleting several sub-networks
After confirmation, the sub-networks are removed.
The sub-network list, the tree area and the opened graphical views are updated.
3AG 86577 ABAA Ed3 178/725

3.1.5 Get the sub-networks properties

This function consists in easily getting information about a sub-network.
From the Main view, menu: Construction => Sub-network => select a sub-
Alcatel
network in the list => Properties
Figure 3-8 Sub-network Properties window
To display all the Comment field, rest the pointer on it (and does not press a
mouse button). A small rectangle of text appears.
3AG 86577 ABAA Ed3 179/725

3.2 Managing NEs

The NE management, part of the network construction, consists in:

performing actions such as:
defining / modifying / deleting NEs
Alcatel
defining and uploading the terminations

displaying NE information such as:
defined NE list
available NE list
termination list
properties
equipment view (if the 1353 NM application or 1353 NM presentation
instance is installed on the same workstation/server as the
1354 BM)
alarm(s) (if the NE has alarm(s)).
The NE management chain gives the order in which the available actions may be
performed.
Define NE Show equipment view
SH instance installed on
Upload terminations BM workstation/server
Show alarm(s)
If NE has alarm(s)
Define terminations Modify NE
NE managed by RM
Delete NE
Configure terminations
NE not managed by RM
Figure 3-9 NE management chain
For managing NEs, you can:
display the NE list, refer to § 3.2.1
3AG 86577 ABAA Ed3 180/725

3.2.1 Display the NE list

The NE list presents all the NEs managed (i.e. already defined) by the 1354 BM,
and their attributes.
From the Main view, menu: Construction => NE/ENE => select the NE panel
Alcatel
Figure 3-10 NE / ENE List window – NE panel
By default, the list window displays all NEs belonging to the Root sub-network.
To modify this filter, enter a new Parent Sub-network User Label by using the
sensitive help (or enter * value to have the complete list) and click on Load
button.
The attributes displayed for each NE are:

− User Label
− SH Operator Label
− Operational State
− Consistency State (Consistent, Not consistent)
− LAC State
− Alarm State (Inhibited, Allowed)
− RM
− Activity State (None, Audit/Alig. In Progress, Synchro. In Progress)
3AG 86577 ABAA Ed3 181/725



− User Label
Alcatel
Figure 3-11 NE Search window
Enter the chosen filtering criteria then click on Ok
3AG 86577 ABAA Ed3 182/725

From the NE list, you can:

define a NE, refer to § 3.2.2 then:
− display the available NE list, refer to § 3.2.2.1
− add a NE, refer to § 3.2.2.2

Alcatel
modify a NE, refer to § 3.2.3
delete a NE, refer to § 3.2.4
upload the NE terminations, refer to § 3.2.5
synchronize a NE termination, refer to § 3.2.6
acquit the NE LAC state, refer to § 3.2.7
display the termination list, refer to § 3.2.8
audit the NE termination, refer to § 3.2.9
configure a NE termination, refer to § 3.2.10
de-configure a NE termination, refer to § 3.2.11
get the NE properties, refer to § 3.2.12
show equipment view, refer to § 3.2.13
show alarms, refer to § 2.2.3
3AG 86577 ABAA Ed3 183/725

3.2.2 Define a NE
Also called ‘NE discovery’, this function consists in assigning a NE to the 1354
BM management by getting its characteristics (matrix, capacity, …) from the
ATM management part of the 1353 NM.
3.2.2.1 Display the available NE list

Alcatel
The list presents all the available NEs at EML level (i.e. not yet assigned to the
1354 BM) and their attributes.
=> Define
Figure 3-12 Available NE List window

− NM Operator Label
− Type (Card4x4, Card8x8, Card4x4_E, Card4x4_D3)
− Version (1.0, 1.1, 2.0, 2.1)
− Address
3AG 86577 ABAA Ed3 184/725


The sorting criterion is as follows:

− NM Operator Label
Alcatel
command, refer to § 2.1.4
Figure 3-13 Available NE Search window
From the Available NE List window, you can:
add a NE, refer to § 3.2.2.2
3AG 86577 ABAA Ed3 185/725

3.2.2.2 Add a NE
- An ATM NE cannot be defined into the main network.
- The NE to be added must be available (managed by the 1353 NM).
- The maximum number of NEs in the parent sub-network must not be reached.
Alcatel
- The parent sub-network must already exist.
- The maximum number of NEs must not be reached.
- The NE User Label must be different as a NE or ENE User Label which is

already used.
From the Available NE List window, select one or several NEs in the list, then
menu: Construction => Add
Figure 3-14 NE Adding window for one NE
Figure 3-15 NE Adding window for several Nes
3AG 86577 ABAA Ed3 186/725

To add one NE:

− Enter a User Label (equal to NM Operator Label by default).

− Choose the Parent Sub-network User Label by using the sensitive help. If a
sub-network has been previously selected, this field is automatically filled.
− Decide whether the NE is managed by the 1354 RM or not, by respectively
ticking or not the Is Managed By RM check box.
Alcatel
− By default, the NE is not managed by the 1354 RM.

− Click on Ok.
The NE is defined into the 1354 BM with the following states:

− Consistency state : Consistent
− Operational state : Enabled
− PNNI node state : Disabled
− LAC state : Denied
− Alarm State : Inhibited
− Activity State : None
The tree area, the graphical views and the NE list are updated.
The NE is removed from the Available NE List window.
Once the NE is defined, do not forget:

− to configure the terminations (refer to § 3.2.10) if the NE is not managed by the
1354 RM
− to configure the node ATM address (refer to chapter 7.1.3) if the NE is to be
used by soft PVCs.
3AG 86577 ABAA Ed3 187/725

3.2.3 Modify a NE
The NE modification gives the possibility to modify:

− NE User Label
- The NE must be previously created.

Alcatel
which is already used by another NE or ENE.
=> select one NE in the NE list => Modify
This funct ion is available only if a NE is selected.
Figure 3-16 NE Modification window
To modify one NE:

− Enter a New User Label.
3AG 86577 ABAA Ed3 188/725

3.2.4 Delete a NE
This function consists in deleting a NE from the 1354 BM supervision.
- All the terminations belo nging to the NE must be free, i.e. not invo lved in a
transmissio n path.
Alcatel
- Act ivit y state of the selected NE must be None (= no audit/alignment or

synchronisat ion with 1354 RM in progress on this NE).
From the main view, menu: Construction => NE/ENE => select the NE panel
=> select one or several NEs in the list => Delete
A confirmation box is displayed:
Figure 3-17 Confirmation box for deleting one NE
Figure 3-18 Confirmation box for deleting several NEs
After confirmation, the NEs are removed from the NE list and added to the
Available NE List window.
The tree area, the opened graphical views and the NE list are updated.
3AG 86577 ABAA Ed3 189/725

3.2.5 Upload the NE terminations

This function consists in uploading the NE terminations and their characteristics.
The terminat ion uploading is automat ically performed at NE definit io n and each
time terminat ions have been created or deleted in the 1354 RM.
Alcatel
From the main view, menu: Construction => NE/ENE => select the NE panel
=> select an NE in the list => Upload
Figure 3-19 Confirmation box for uploading the terminations of one NE
Figure 3-20 Confirmation box for uploading the terminations of several NEs
After confirmation the SDH TTPs, as well as the associated TP/VP_As, are
created or removed in the 1354 BM.
3AG 86577 ABAA Ed3 190/725

3.2.6 Synchronize the NE terminations

This function consists in synchronizing, for a given ATM NE, the transmission
characteristics (bit rate and technology) of its terminations.
- The NE must not be managed by the 1354 RM.

Alcatel
- The NE LAC state must not be granted.
=> select one or several NEs in the list => Synchronize
Figure 3-21 Confirmation box for synchronizing the terminations of one NE
Figure 3-22 Confirmation box for synchronizing the terminations of several NEs
After confirmation the terminations characteristics in the 1354 BM are

synchronized with the ATM NE (i.e. characteristics found in the ATM NE are
stored in the 1354 BM database).
3AG 86577 ABAA Ed3 191/725

3.2.7 Acquit the NE LAC state

When the LAC state of the NE is equal to Post-granted, this function allows the
operator to acknowledge the possible misalignment between the 1354 BM and the
ATM NE due to a possible modification from the 1320CT.
As the 1353 NM could authorize the local access to a NE from the 1320 CT, the
Alcatel
data stored in 1354 BM could be different.
To resolve this possible misalignment, the operator can perform a NE audit and a
NE alignment to download 1354 BM data to the NE) or Plug & Play (to upload
NE data to 1354 BM).
- The NE LAC state must be Post-granted.
=> select one or several NEs in the list => Acquit
Figure 3-23 Confirmation box for acquitting the LAC state of one NE
Figure 3-24 Confirmation box for acquitting the LAC state of several NEs
After confirmation the LAC state of the concerned NEs is set to Denied and the
NE List is updated.
3AG 86577 ABAA Ed3 192/725

3.2.8 Display the termination list

The Terminations List window presents all the NE terminations and their
attributes.
=> select an NE in the list => Term. List
Alcatel
Figure 3-25 Termination List window (for an ATM Card 4x4_E - 260 ports)
The attributes displayed for each termination are:

− Identifier
− Technology
− Bit Rate
− Usage State
− Transmission Path User Label
− ATM address
− Alarm Status
3AG 86577 ABAA Ed3 193/725



− Identifier
− Technology
Alcatel
− Alarm Status
Figure 3-26 Termination Search window
From the Terminat ion List window, you can:
configure a termination, refer to § 3.2.10
de-configure a termination, refer to 3.2.11
3AG 86577 ABAA Ed3 194/725

3.2.9 Audit the NE terminations

This function consists in auditing the terminations characteristics (bit rate and
technology) of an NE and allows the operator to check if the characteristics he has
entered match those implemented on the ATM NE.
- The NE must be defined.

Alcatel
=> select an NE in the list => Term. Audit
Figure 3-27 Termination Transmission Characteristics Audit window
3AG 86577 ABAA Ed3 195/725

The attributes displayed for each Termination are:

− Identifier
− BM Technology
− BM Bit Rate
− NE Technology
− NE Bit Rate
Alcatel
The Actualize button allows to refresh the Termination Transmission

Characteristics Audit window. The Upload Date field is also updated.
3AG 86577 ABAA Ed3 196/725

3.2.10 Configure a termination

This function consists in configuring (locally in the 1354 BM) the SDH
transmission characteristic (bit rate) of a termination.

Alcatel
- The terminat ion must not be invo lved in a transmission path.
=> select an NE in the list => Term. List => select a terminat ion in the list =>
Configure
Figure 3-28 Termination Configuration window
To configure the termination:

− Click on the Bit Rate option button then choose a bit rate.
− Click on Ok.
The Termination List is updated.
Once the termination is defined, do not forget to configure the termination ATM
address (refer to chapter 7.1.7) if the termination is to be used by soft PVCs.
3AG 86577 ABAA Ed3 197/725

3.2.11 De-configure a termination

This function consists in de-configuring (locally in the 1354 BM) the SDH
transmission characteristic (bit rate) of a termination.

Alcatel
- The terminat ion must not be invo lved in a transmission path.
=> select an NE in the list => Term. List => select one or several terminat ions in
the list => De-configure
Figure 3-29 Confirmation box to de-configure a termination
Figure 3-30 Confirmation box to de-configure several terminations
3AG 86577 ABAA Ed3 198/725

3.2.12 Get the NE properties

This function consists in easily getting information about a NE.
Alcatel
=> select an NE in the list => Properties
Figure 3-31 NE Properties window
To display all the ATM Address fie ld, rest the pointer on it (and does not press a
3AG 86577 ABAA Ed3 199/725

3.2.13 Show equipment view

This functionality, available from the NE List, is to be used when an operator

wants to display the equipment view.
Alcatel
- The 1353 NM application or a 1353 NM presentation instance must be

installed on the same workstation/server as the 1354 BM.
- The operator login must be declared on both 1353 NM and 1354 BM (ex: alcatel
login)
=> select one NE in the list => Show Equipment
Figure 3-32 Confirmation box to navigate towards equipment view
After confirmation, the equipment view of the selected NE is opened (like on the
1354 NM).
3AG 86577 ABAA Ed3 200/725

3.3 Managing ENEs

The ENE management, part of the network construction, consists in:

− performing actions such as:
creating / modifying / deleting ENEs
Alcatel
creating / deleting ETPs

assigning NAD label to ETPs
− displaying ENE information such as:
ENE list
ETP list
Properties
The ENE management chain gives the order in which the available actions may be
performed.
Create ENE
Modify ENE
Create ETP Delete ENE
Delete ETP Assign NAD label to ETP
Figure 3-33 ENE management chain
For managing ENEs, you can:
display the ENE list, refer to § 3.3.1
3AG 86577 ABAA Ed3 201/725

3.3.1 Display the ENE list

The ENE list presents all the ENEs and their attributes.
From the Main view, menu: Construction => NE/ENE => select the ENE panel
Alcatel
Figure 3-34 NE / ENE List window – ENE panel
By default, the list window displays all ENEs belonging to the Root sub-network.
button.
The attributes displayed for each ENE are:

− User Label
− Comment

− User Label
3AG 86577 ABAA Ed3 202/725


Alcatel
Figure 3-35 ENE Search window
From the ENE list, you can:
create an ENE, refer to § 3.3.2
modify an ENE, refer to § 3.3.3
delete an ENE, refer to § 3.3.4
display the ETP list, refer to § 3.3.5
get the ENE properties, refer to § 3.3.9
3AG 86577 ABAA Ed3 203/725

3.3.2 Create an ENE

This function consists in making visible for the 1354 BM, a NE or a set of NEs
not managed by the 1354 BM, for example an ATM NE contained in an adjacent
sub-network not accessible by the 1354 BM.
It is authorised to create an ENE in the main parent sub-network.

Alcatel
- The parent sub-network must already exist.
- The maximum number of ENEs in the parent sub-network must not be reached.
- The maximum number of ENEs must not be reached.
- The ENE User Label must be different as one which is already used by another
ENE or NE.
=> Create
Figure 3-36 ENE Creation window
3AG 86577 ABAA Ed3 204/725

To create an ENE:
− Enter a User Label.

− Choose a Parent Sub-network User Label by using the sensitive help. If a sub-
network has been previously selected, this field is automatically filled.
− Click on Ok.
Alcatel
The ENE is created in the 1354 BM with ten ETPs which are created
automatically.
The tree area, the opened graphical views and the ENE list are updated.
3AG 86577 ABAA Ed3 205/725

3.3.3 Modify an ENE

The ENE modification gives the possibility to modify:

− ENE User Label
− Comment
Alcatel
- The ENE must be previously created.
which is already used by another ENE or NE.
=> select one ENE in the ENE list => Modify
This funct ion is available only an ENE is selected.
Figure 3-37 ENE Modification Window
To modify an ENE:
− Change the Comment
3AG 86577 ABAA Ed3 206/725

3.3.4 Delete an ENE

This function consists in deleting an ENE and its ETPs from the 1354 BM
supervision.
- The usage state of the ETPs belonging to the ENE must be idle.
Alcatel
=> select one or several ENEs in the list => Delete
Figure 3-38 Confirmation box for deleting one ENE
Figure 3-39 Confirmation box for deleting several ENEs
After confirmation, the ENEs and their ETPs are deleted.
The tree area, the opened graphical views and the ENE list are updated.
3AG 86577 ABAA Ed3 207/725

3.3.5 Display the ETP list

The ETP List window presents all the External Termination Points (ETP) of an
ENE and their attributes.
=> select an ENE in the list => ETP List
Alcatel
Figure 3-40 ETP List window
The attributes displayed for each ETP are:

− Identifier
− Technology
− Bit Rate
− Site Label
− SDH NE Label
− Port Label
− TP Label
− Usage State
− NAD Label
3AG 86577 ABAA Ed3 208/725



− Identifier
− Technology
Alcatel
− NAD Label
Figure 3-41 ETP Search window
From the ETP List window, you can:
create ETPs, refer to § 3.3.6
delete an ETP, refer to § 0
assign NAD Label to ETPs, refer to § 3.3.9
3AG 86577 ABAA Ed3 209/725

3.3.6 Create ETPs

This function consists in creating ETPs that represent transmission path

extremities located in the selected ENE.
- The maximum number of ETPs in the ENE must not be reached.

Alcatel
=> select an ENE in the list => ETP List => Create
Figure 3-42 ETP Creation window
To create ETPs:
− Enter the First Id.: numerical value corresponding to the ETP first number to
be used.
− Enter the Number of ETP to be created. It is a numerical value between 1 and
the maximum number of ETPs which can be created on a ENE.
− Click on Ok.
The ETPs are created with the following state and parameters:
− usage state : Idle
− technology : “-“ (not yet defined)
− bit Rate : “-“ (not yet defined)
− NAD Label : Administrator
The ETP identifiers (three-digit numbers) are automatically generated by the
1354 BM and the ETP List window is updated.
3AG 86577 ABAA Ed3 210/725

3.3.7 Modify an ETP comment

This function consists in modifing an ETP comment from the selected ETP
=> select an ENE in the list => ETP List => select one or several ETPs in the list
=> Modify Etp Comment
Alcatel
Figure 3-43 ETP Modify window
To modify an ETP:
− Change the ETP Comment
3.3.8 Delete an ETP

This function consists in deleting an ETP from the selected ENE.
- The usage state of the ETP must be idle (i.e. not invo lved in a transmission
path).
=> select an ENE in the list => ETP List => select one or several ETPs in the list
=> Delete
Figure 3-44 Confirmation box for deleting one ETP
3AG 86577 ABAA Ed3 211/725

Figure 3-45 Confirmation box for deleting several ETPs

Alcatel
After confirmation, the ETPs are removed.
The ETP List window is updated.
3AG 86577 ABAA Ed3 212/725

3.3.9 Assign NAD Label to ETPs

This function consists in assigning a NAD Label to ETPs of a ENE.
Alcatel
=> select an ENE in the list => ETP List => select one or more ETPs in the list
=> Assign NAD Label
Figure 3-46 NAD Label Assignment window for one ETP
Figure 3-47 NAD Label Assignment window for several ETPs
To assign a NAD Label to the selected ETP:

− Choose the NAD Label by using the sensitive help (a list of available initiators
is proposed)
− Click on Ok.
The selected ETP is updated with the selected NAD label and the ETP List
window is updated.
3AG 86577 ABAA Ed3 213/725

3.3.10 Get the ENE properties

This function consists in easily getting information about an ENE.
Alcatel
=> select an ENE in the list => Properties
Figure 3-48 ENE Properties window
The fields have been filled out at the ENE creation (refer to § 3.3.2) time.
To display all the Comment field, rest the pointer on it (and does not press a
3AG 86577 ABAA Ed3 214/725

3.4 Managing transmission paths / IMA transmission paths

The transmission path management, part of the network construction, consists in:
creating / finalizing / modifying / deleting transmission paths
Alcatel
configuring transmission paths

adding / removing IMA links
− managing the use of the transmission paths:
configure NIMs
partition function
lock / unlock function
− displaying transmission path information such as:
transmission path list
IMA link list (in case of IMA transmission path)
extremities and properties
fault localization
bandwidth load
The transmission path management chain gives the order in which the available
actions may be performed.
Create transmission path Finalize transmission path
Delete transmission path

Modify transmission path
Add / remove IMA link (only

for transmission path IMA)
Configure transmission path
Partition transmission path

Configure NIMs
Lock transmission path Unlock transmission path
Figure 3-49 Transmission path management chain (network construction)
3AG 86577 ABAA Ed3 215/725

The transmission path management is performed from the Transmission Path List
window
For managing transmission paths, you can:
display the transmission paths list, refer to § 3.4.1

Alcatel
3AG 86577 ABAA Ed3 216/725

3.4.1 Display the transmission paths list

The transmission path list presents all the transmission paths / all the
transmissions paths IMA and their attributes.
From the Main view, menu: Construction => Transmission Paths

Alcatel
Figure 3-50 Transmission Path List window
A Transmission Path (IMA or not) will be displayed in a Parent Sub-network User

Label common to its two extremities.
By default, the list window displays all Transmission Paths belonging to the Root
sub-network.
button.
3AG 86577 ABAA Ed3 217/725

The attributes displayed for each transmission path are:

− User Label
− IMA (= IMA transmission path or not)
− Bit Rate (None, VC-3, VC-12, DS3
− Routing Service Type (Hard, Soft)
− Usage State (Idle, Busy, None)
Alcatel
− Activity State
− Consistency State (Consistent, Not consistent, Indeterminate)
− Availability Status (Normal, In failure)
− NAD Label

− User Label
− Routing Service Type
− Availability Status
− NAD Label
3AG 86577 ABAA Ed3 218/725

Alcatel
3AG 86577 ABAA Ed3


Figure 3-51 Transmission Path Search window
219/725
From the all transmissio n path list (depending of the provisio ning state of the
selected transmissio n path) you can:
create a transmission path, refer to § 3.4.2
display the IMA link list (available if an IMA transmission path is

selected), refer to § 3.4.4
Alcatel
finalize a transmission path (available if its consistency state is Not

Consistent), refer to § 3.4.5
finalize an IMA transmission path (available if its consistency state is

Not Consistent), refer to § 3.4.6
modify a transmission path, refer to § 3.4.7
delete a transmission path, refer to § 3.4.8
lock a transmission path, refer to § 3.4.9
unlock a transmission path, refer to § 3.4.10
configure a transmission path, refer to § 3.4.11
configure NIM for a transmission path, refer to § 3.4.12
partition a transmission path, refer to § 3.4.13
display the transmission path extremities, refer to § 3.4.15
display the transmission path bandwidth load, refer to § 3.4.16
for hard routing service, refer to § 3.4.16.1
for soft routing service, refer to § 3.4.16.2
display the fault localization, refer to § 3.4.17
display the transmission path properties, refer to § 3.4.18
3AG 86577 ABAA Ed3 220/725

3.4.2 Display Link List View

The link list view gives a graphical representation of all links of the Grouped Link
From the Grouped Link, menu: Show Links List
Alcatel
Figure 3-52 Link List View window

This Link List View will display a graphical representation of all links of the Grouped Link including ETP
comment.
3.4.3 Create a transmission path

This function consists in identifying the transmission path and determining its bit
rate and the ATM NEs (and/or ENEs) that support its extremities.
A transmission path may be created either between two ATM NEs (managed by
the 1354 RM or not) or between one ATM NE (managed by the 1354 RM or not)
and one ENE (on a ETP).
If the two extremities are managed by the 1354 BM, the Transmission Path is
considered as being managed bu the 1354 RM.
- The chosen ATM NE(s) must be defined.
- The chosen ENE must be created.
- The terminat ion must be defined and free (usage state = Idle) or configured if it
is not managed by the RM.
- The ETP must be created and free (usage state = Idle).
From the Main view, menu: Construction => Transmission Paths => Create
3AG 86577 ABAA Ed3 221/725


Alcatel
Figure 3-53 Transmission Path Creation window
To create a transmission path:

Decide if the transmission path to create will be an IMA transmission path or not,
by ticking or not the IMA check box
Enter an User Label
If IMA check box is not ticked, choose a Bit Rate by using the option button
Choose the Technology by clicking on the SDH or PDH radio button. If the
previously selected transmission path bit rate is VC-4 or VC-4-4C, it is not
possible to choose the PDH technology
Use the Alarm Resources option button to specify whether the alarmed
ressources may be used (Enabled) or not (Disabled) for the creation.
Enter a Comment (optional)
In the Origin (A) area:
Choose the User Label by using the sensitive help.
Choose the Termination Id. by using the sensitive help (the NE User Label
field has to be previously filled out)
In the Destination (Z) area:
3AG 86577 ABAA Ed3 222/725

If the NE is an ATM NE, choose its User Label and Termination Id. by
proceeding as in the Origin area
If the NE is an ENE, tick the ENE check box. The Transmission Path Creation
window becomes as follows:
Alcatel
Figure 3-54 Transmission Path Creation window with an ENE not managed by RM
Decide whether the ENE is managed by the 1354 RM or not, by respectively

ticking or not the Is Managed by RM check box
Choose the ENE User Label and Termination Id. by processing as in the Origin
(A) area
In the ‘Adjacent OMSN’ area (mandatory if the ENE is managed by RM), fill out
the:
− Site Label,
− OMSN Label (= the user label of the OMSN),
− In the ‘Adjacent OMSN Termination’ area, it exists two possibilities to fill the
Port Label and TP label fields: Manually or by click on Retrieve on OMSN
button
By clicking on the Retrieve on OMSN button, 1354 BM uploads port label
and TP label compatible with the previously chosen Bit Rate
3AG 86577 ABAA Ed3 223/725

. Port Label (= name of the OMSN concatened with the board used to connect
to the ENE) (Ex: Eqpt383/r01s1b08p01c01)
. TP Label (payload position of the VC4, VC3, VC12 in the related AU4)
fields according to the adjacent NE characteristics.
TP Label is greyed for creation of a transmissio n path PDH (bit rate = E1, E3 or
Alcatel
DS3) between ATM NE and ENE managed by RM.
Figure 3-55 Transmission Path Creation window with an ENE managed by RM
TP Label = 01/2 => 01 is AU4, 2 is TU3-VC3 number in AU4
The TP Label ident ifier has a structure alike as indicated in the RM trail sructure
3AG 86577 ABAA Ed3 224/725

Ex : for VC12 SDH : 01/3/2.7, for VC3 SDH : 02/1, for VC4 SDH : 01
Click on Ok to create the transmission path.
The transmission path is created with the following states:

Alcatel
− operational state : Disabled

− administrative state : None
− activity state : None (or CreationInProgress *)
− consistency state : Consistent (or Not Consistent *)
− cost : None
If the transmission path is IMA, its routing service is set to Hard.
The usage state of the transmission path extremities (terminations and/or ETP)
changes to Busy.
If the two extremities are managed by the 1354 BM, a SDH Path Definition
request is sent to the 1354 RM.
* The activity state is set to CreationInProgress (and consistency state is set to Not
Consistent) if the two extremities of the Transmission Path are managed by the
1354 RM. A request is sent to the 1354 RM to create the Transmission Path.
When the notification of creation is sent from the 1354 RM to the 1354 BM,
activity state is set to None and consistency state is set to Consistent if the
operation is performed in 1354 RM. If the operation fails, consistency state is set
to Not Consistent and the operator can retry the creation of the Transmission Path
by using the command Finalize (refer to § 0).
The tree area, the opened graphical views, and the Transmission Path List window
are updated.
In the Transmission Path List window:

− the created Transmission Path will be displayed in the Parent Sub-network
User Label common to the two extremities.
− the availability status reflects the status of the SDH path.
When an extremity of the new transmission path is an ENE, the ETP List window
is also updated (Technology and Bit Rate columns). If an extremity is a NE, the
Termination List window is updated.
Once the transmission path is created, do not forget to configure it (refer to §

3.4.11).
3AG 86577 ABAA Ed3 225/725

Alcatel
3AG 86577 ABAA Ed3

226/725
3.4.4 Display the IMA link list

The IMA Link list presents all the IMA links contained in the previously selected
IMA transmission path.
- The selected IMA transmissio n path must be configured.

Alcatel
From the Main view, menu: Construction => Transmission Paths => select one
IMA transmission path in the list => IMA Link List
Figure 3-56 IMA Link List window
The attributes displayed for each IMA link are:

− User Label
− Activity State

− User Label
3AG 86577 ABAA Ed3 227/725


Alcatel
Figure 3-57 IMA Link Search window
From the IMA link list, you can:
add an IMA link, refer to § 3.4.4.1
remove an IMA link, refer to § 3.4.4.2
finalize an IMA link, refer to § 3.4.4.3
display the IMA link extremities, refer to § 3.4.4.4
display the IMA link properties, refer to § 3.4.4.5
display the fault localization on IMA link, refer to § 3.4.4.6
show alarms, refer to § 2.2.3
3AG 86577 ABAA Ed3 228/725

3.4.4.1 Add an IMA link to an IMA transmission path

This function consists in associating one or several IMA links to an IMA

transmission path.
- The maximum number of IMA link added to the IMA transmission path is not
reached.
Alcatel
- The usage state of the chosen IMA transmissio n path must be None or Idle (i.e.
without any traffic).
- For a chosen transmissio n path managed by the 1354RM, its activit y state must
be none and its consistency state must be consistent.
- The IMA transmissio n path must be unlocked.
IMA transmission path in the list => IMA Link List => Add
This funct ion is available only wit h no selection in the IMA Link list. For de-
select ion command, refer to § 2.1.4.
Figure 3-58 Add IMA link window
To add an IMA link to an IMA transmission path:

− Choose, with the contextual help, one available Transmission Path User
Label to add. The available transmission paths have the same ATM Nes
extremeties and same bit rate as the parent IMA transmission path.
− Click on Ok
The transmission path is transformed in an IMA link associated to the Parent IMA
Group User Label.
3AG 86577 ABAA Ed3 229/725

If the transmission path has the operational state enable (Connection

characteristics defined on ATM NEs), the 1354 BM sends a request of de-
activation of TP/VP_A on ATM NEs.
The extremities (ATM NE, ENE if Z extremity is an ENE and TP or ETP) and
characteristics (bit rate, technology) of transmission path extremities are used to
create an IMA Link.
Alcatel
A request is sent to the ATM NEs extremities:

− to create the TP/IMA_A,
− to configure the IMA_T (associate the IMA link to the parent IMA
transmission path, by giving to the IMA Link, the IMA transmission path
termination),
− to activate the TP/IMA_A.
At the activation of TP/IMA_A, the bit rate of the IMA transmission path is
incremented of the bit rate of the IMA link following a formula.
The bandwidth of the added IMA link is added to the bandwidth of the IMA
transmission path containing this IMA link.
The transmission path transformed in an IMA link is deleted from the

transmission path list and from the tree area and is created in the IMA Link list.
The IMA link is created with its consistency state and availability status equal to
the consistency state and availability status of the initial transmission path.
At the first IMA link addition, bit rate and technology of the parent IMA
transmission path will be defined (by deduction) with the same bit rate and
technology as the added IMA link.
Each time an IMA link will be added, the bit rate of the parent IMA transmission
path will be increased.
The process fails (= IMA link not inserted in the IMA transmissio n path) in the
fo llo wing cases:
− De-activation of TP/VP_A is not accepted by the ATM NEs.
− Creation of TP/IMA_A failed in the ATM Nes
− Configuration of IMA_T faile in the ATM NEs
− Activation of TP/IMA_A is refused by the ATM NEs
3AG 86577 ABAA Ed3 230/725

3.4.4.2 Remove an IMA link from an IMA transmission path

This function consists in removing an IMA link from an IMA transmission path
and to transform it to a transmission path.
- The LAC state of the NEs extremit ies must not be granted.
Alcatel
- Enough available bandwidth on IMA transmissio n path must be available.
IMA transmission path in the list => IMA Link List => select one or several
IMA links in the list => Remove
Figure 3-59 Confirmation box for removing one IMA link
Figure 3-60 Confirmation box for removing several IMA links
After confirmation, the 1354 BM checks if the available bandwidth of the IMA
transmission path is lower or equal than the bandwidth of the IMA link(s) to
remove.
3AG 86577 ABAA Ed3 231/725

IMA Link2 Available Available

VC-12 Bandwidth Bandwidth
Used
Bandwidth
IMA Link 1
VC-12 Used
Bandwidth
Tra nsmission Ca se 1: Ca se 2:
Alcatel
pa th IM A with 2 Ava ilable ba ndwidth not Ava ila ble ba ndwidth sufficient
IM A links VC12 sufficient to remove a n IM A Link to remove a n I MA Link
If there is enough available bandwidth on the IMA transmission path, the 1354
BM sends a deletion of the TP/IMA_A request to the ATM NEs extremities.
The IMA link(s) is/(are) removed from the IMA Link list and from the associated
IMA transmission path and transformed in transmission path(s).
Then, the transmission path list and tree area are updated. The removed IMA
link(s) appear(s) again in the transmission path list like transmission path
entity(ies).
Each transformed transmission path is automatically re-configured if the 1354 RM

manages it.
Else, it stays in non-configured state (it loses the “Lock”, “Cost” attributes which
it had before it addition to an IMA transmission path).
Each transformed transmission path is created with its consistency state and
availability status equal to the consistency state and availability status of the
removed IMA link.
At the last IMA link removing from an IMA transmission path, bit rate and
technology of the IMA transmission path will be set to none.
3AG 86577 ABAA Ed3 232/725

3.4.4.3 Finalize an IMA link

This function consists to try to pass an inconsistent IMA link in a consistency

state. A creation request is re-sent to the 1354 RM.
- The IMA link must have these two extremit ies managed by the 1354 RM.
Alcatel
- The consistency state of the IMA link must be Not Consistent.
- The activit y state of the IMA link must be None.
IMA transmission path in the list => IMA Link List => select one or several
IMA links in the list => Finalize
Figure 3-61 Confirmation box for finalizing one IMA link
Figure 3-62 Confirmation box for finalizing several IMA links
After confirmation:
− Activity state is set to CreationInProgress.
− A SDH Path creation request is sent to the 1354 RM.
− After positive receipt of the creation from the 1354 RM, activity state is set to
None and consistency state is set to Consistent.
The IMA Link List window is updated.
If there is no more IMA Link inconsistent, the associated IMA transmission path
becomes consistent.
3AG 86577 ABAA Ed3 233/725

3.4.4.4 Display the IMA link extremities

This function consists in displaying information about an IMA link.
IMA transmission path in the list => IMA Link List => select one IMA link in
the list => Extremities
Alcatel
Figure 3-63 IMA Link Extremities window
The first two fields have been filled out at the transmission path creation (refer to
§ 3.4.2) time.
The fields Last Action, Last Action Date give information about the last action
performed on the transmission path.
The field “Is managed by RM” depends if the NE extremities are managed or not
by 1354 RM.
3AG 86577 ABAA Ed3 234/725

3.4.4.5 Display the IMA link properties

This function consists in displaying information about an IMA link.
IMA transmission path in the list => IMA Link List => select one IMA link in
the list => Properties
Alcatel
Figure 3-64 IMA Link Properties window
§ 3.4.2) time.
performed on the IMA link.
The field “Is Managed by RM” depends if the IMA link is managed or not by
1354 RM.
3AG 86577 ABAA Ed3 235/725

3.4.4.6 Display the fault localization

This function consists in displaying physical entities alarms for an IMA link.
- The availabilit y status of the IMA link must be either Degraded or In Failure.
Alcatel
IMA transmission path in the list => IMA Link List => select an IMA link with
alarm in the list => Fault Localization List
Figure 3-65 Fault Localization List (IMA link)
The attributes displayed for each logical entity are:

− NE User Label
− Operator Label
− Alarm Status
− Date
− Probable Cause
− Specific Problem
3AG 86577 ABAA Ed3 236/725

The 1354 BM will display up to 100 alarms. When the number of alarms is
superior to 100, the fo llowing confirmation box is displayed:

Alcatel
Figure 3-66 Confirmation box for displaying the fault localization list
After confirmation, the truncated list is displayed.
The data displayed are never refreshed in real time. A Actualize button is
available.
3AG 86577 ABAA Ed3 237/725

3.4.5 Finalize a transmission path

This function could be used to try to finish the transmission path creation when
the creation (from the 1354 BM) of a transmission path managed by the 1354 RM
has not been completed successfully by the 1354 RM, and its consistency state has
become Not Consistent.
Alcatel
- The transmissio n path must have these two extremit ies managed by the 1354
RM.
- The consistency state of the transmissio n path must be Not Consistent.
- The activit y state of the transmissio n path must be None.
or several transmissio n paths (managed by the 1354 RM) in the list => Finalize
Figure 3-67 Confirmation box for finalizing one transmission path
Figure 3-68 Confirmation box for finalizing several transmission paths
After confirmation:
− Activity state is set to CreationInProgress.
− A SDH Path creation request is sent to the 1354 RM.
− After positive receipt of the creation from the 1354 RM, activity state is set to
None and consistency state is set to Consistent.
The tree area, the graphical views and the Trans. Path List window are updated.
3AG 86577 ABAA Ed3 238/725

3.4.6 Finalize an IMA transmission path

This function could be used to try to finalize the inconsistent IMA link included in
the selected inconsistent IMA transmission path.
IMA transmission path pass to Not Consistent when at least one IMA link pass to
Not Consistent.
Alcatel
IMA link pass not consistent when its creation is partial on the 1354 RM or when
1354 BM has received a 1354 RM notification that the SDH path is not
commissioned.
- The consistency state of the IMA transmissio n path must be Not Consistent.
or several not consistent IMA transmissio n paths in the list => Finalize
Figure 3-69 Confirmation box for finalizing one IMA transmission path
Figure 3-70 Confirmation box for finalizing several IMA transmission paths
After confirmation:
− A SDH Path creation request is sent to the 1354 RM for each not consistent
IMA link.
− After positive receipt of each concerned IMA link, consistency state of the
IMA transmission path is set to Consistent. If one IMA link stays in Not
Consistency state, IMA transmission path stays also in Not Consistency state.
The tree area, the graphical views and the Trans. Path List window are updated.
3AG 86577 ABAA Ed3 239/725

3.4.7 Modify a transmission path

This function consists in modifying some characteristics of the Transmission Path.

− Comment
− Cost (if the transmission path is configured)
Alcatel
− Overbooking information
- - The Transmissio n Path must be previously created.
- The Transmissio n Path User Label must be different as one which is already
used by another Transmission Path.
- The Consistency State must be Consistent.
- The transmissio n path must not be managed by the 1354 RM.
transmissio n path in the list => Modify
This funct ion is available only if a transmissio n path is selected.
Figure 3-71 Transmission path Modification Window
3AG 86577 ABAA Ed3 240/725

To modify a transmission path:

Enter a New User Label

Change the Comment (optional)
Change the Cost (if the transmission path is configured)
Change the Overbooking Factor:
− Select one or more traffic contracts for which the overbooking function
Alcatel
will be applied.
Choose the overbooking factor value (range between 100 (default value) and
1000; 100 means no overbooking, greater than 100 implies an increase of
the PVPC connections by a reduction of the reserved bandwidth).
If a New User Label is entered, the Transmission Path List is updated and, if the
Transmission Path is managed by the 1354 RM, a request is sent to it specifying
the new user label.
3AG 86577 ABAA Ed3 241/725

3.4.8 Delete a transmission path

This function consists in deleting a transmission path from the 1354 BM

supervision.
- The usage state of the Hard transmissio n path must be Idle.

Alcatel
- In case of Transmissio n Path managed by the 1354 RM, the consistency state
must not be Indeterminate (Indeterminate indicates that the link between the
1353 NM and the 1354 RM is cut).
- Act ivit y state of the associated NEs must be None (= no audit/alignment or
synchronisat ion with 1354 RM in progress on these NEs).
- The transmissio n path must not be under Performance Monitoring.
or several transmissio n paths in the list => Delete
Figure 3-72 Confirmation box for deleting one transmission path
Figure 3-73 Confirmation box for deleting several transmission paths
After confirmation:
- if the transmission paths are not managed by the 1354 RM:
- they are removed and the usage states of the transmission path extremities
(terminations and/or ETP) change to Idle.
3AG 86577 ABAA Ed3 242/725

- if the transmission paths are managed by the 1354 RM:

- Activity states are set to DeletionInProgress

-A SDH Path deletion request is sent to the 1354 RM
- Consistency states are set to Not Consistent (until the 1354 RM sends a
positive receipt of the deletion)
Alcatel
The tree area, the graphical views and the Transmission Path List window are
updated.
If the transmissio n paths to delete are IMA and contain IMA links, these IMA
links will be also deleted. They will be converted into transmissio n paths and will
be displayed again in the Transmissio n Path list.
When the IMA transmissio n path is wit hout IMA Link, a delet ion request is sent
to the ATM NEs extremit ies to delete the IMA/VP_A. On the ATM NE, the
delet ion corresponds to a de-activat ion (if act ivated before) and a delet ion of the
IMA/VP_A.
Then, the IMA transmissio n path is deleted on 1354 BM, and its (external)
terminat ions are freed on ATM NE (ENE).
If the operation delet ion fails, and the 2 IMA/VP_As couldn’t be aligned (one
IMA/VP_A is deact ivated, and the second IMA/VP_A is activated), the IMA
transmissio n path operational state is Disabled and the 1354 BM automat ically
tries to solve the misalignment at the next IMA transmissio n path delet ion or
configuration request.
3AG 86577 ABAA Ed3 243/725

3.4.9 Lock a transmission path

This function consists in preventing the transmission path to be used for the cell
transport.
Once locked, the transmission path cannot be used by other hard or soft PVPCs
but the already supported PVPCs are not impacted.
Alcatel
- The transmissio n path must be created.
- The administrative state of the transmission path must be Unlocked.
or several transmissio n paths in the list => Lock
Figure 3-74 Confirmation box for locking one transmission path
Figure 3-75 Confirmation box for locking several transmission paths
After confirmation, the administrative state of the selected transmission paths

changes to Locked.
The transmission path list is updated.
The allocated or implemented or commissioned hard PVPCs, already using the

transmission path, are not impacted by the lock request. They can be de-
commissioned, de-implemented and de-allocated.
3AG 86577 ABAA Ed3 244/725

The transmission path cannot be used for the allocation of a new hard PVPC or
soft PVPC.
The implementation of other hard PVPCs whose route uses the transmission path
is prohibited.
The established soft PVPCs, already using the transmission path, are not impacted
by the lock request. They can be released.
Alcatel
The transmission path cannot be used for the establishment of a new soft PVPC.
3AG 86577 ABAA Ed3 245/725

3.4.10 Unlock a transmission path

This function consists in unlocking a previously locked transmission path.
- The administrative state of the transmission path must be Locked.

Alcatel
or several transmissio n paths in the list => Unlock
Figure 3-76 Confirmation box for unlocking one transmission path
Figure 3-77 Confirmation box for unlocking several transmission paths
After confirmation, the administrative states of the transmission paths change to

Unlocked.
The transmission path list is updated.
3AG 86577 ABAA Ed3 246/725

3.4.11 Configure a transmission path

This function consists in defining the transmission path characteristics as follows:

− routing service (hard or soft) (not available for an IMA transmission path),
− interface type (NNI, ICI or UNI),
− overbooking parameters,
Alcatel
− VPI and VCI ranges.
- If the transmissio n path is already configured and the user wants to change the
routing service fro m hard to soft, the user has first to:
. lock the transmissio n path (refer to § 3.4.9) to avoid other hard PVPCs to
use it,
. display the transmissio n path bandwidth load (refer to § 3.4.16) in order to
make sure not any hard PVPCs are using the transmissio n path,
. if some hard PVPCs are using the transmission path, de-commission, de-
implement then de-allocate them (refer to chapter 4).
- Act ivit y state of the associated NEs must be None (= no audit/alignment or
- The transmissio n path must not be under Performance Monitoring.
From the Main view, menu: Construction => Transmission Paths => select a
transmissio n path in the list => Configure
Figure 3-78 Transmission Path Configuration window
3AG 86577 ABAA Ed3 247/725

To configure a transmission path:

− It it is not an IMA transmission path, choose the Routing Service (Hard or

Soft) by using the option button,

− Choose the Interface Type (UNI, ICI, NNI) by using the option button. The
available interface types depends on the NE types previously chosen (see the
table below).
NE-NE NE-ENE
Alcatel
UNI - X
ICI - X
NNI X X
For the soft routing service, only the NNI interface type can be used.
− In the Overbooking area:
− Select one or more traffic contracts for which the overbooking function
will be applied.
− Choose the overbooking factor value (range between 100 (default value)
and 1000; 100 means no overbooking, greater than 100 implies an increase
of the PVPC connections by a reduction of the reserved bandwidth).
− In the VPI Range area:
− The First VPI number is configurable to 0 or 1.
− Enter a Last VPI number by using the option button.
− The possible values are:
0, 1, 3, 7, 15, 31 (default value), 63, 127 or 255 for UNI InterfaceType,
0, 1, 3, 7, 15, 31 (default value), 63, 127, 255, 1023, 2047 or 4095 for ICI or
NNI Interface Type.
− In the Default VCI range area:
− The First VCI number is automatically set to 32.
− Enter a Last VCI number by using the option button.
− The possible values are 63, 127, 255 (default value), 511, 1023, 2047,
4095 or 8191.
− Click on Ok.
A configuration request is sent to the NEs extremities with these values.

After the NEs responses, the transmission path is configured. Its operational state
changes to Enabled.
If the transmission path has been hard configured (routing service type = hard), its
administrative state changes to Unlocked and its usage state is set to Idle.
If the transmission path has been soft configured, its usage state is set to None.
If the transmission path is IMA, bit rate and technology are not defined. They will
be defined (by deduction) at the first IMA link addition.
The Transmission Path List window is updated.
3AG 86577 ABAA Ed3 248/725

3.4.12 Configure NIM for a transmission path

This function allows to create NIM points on the VPL_Ts and/or VCL_Ts of all
the PVCs (hard VPCs/ hard VCCs) passing through a transmission path extremity.
- The transmissio n path must be configured for the Hard routing service and its
Alcatel
usage state set to Busy.
transmissio n path in the list => Configure NIM
Figure 3-79 Transmission Path NIM Configuration window
From this window, it is possible to create or delete NIM for the selected extremity
of a transmission path.
To configure NIM on the extremity:

− Select the wished action type (Create NIM or Delete NIM)
− Choose the User Label by using the option button. Only NE extremitie(s) of
the transmission path is(are) proposed.
− Choose the Layer (VPC, VCC, both) by using the option button
− Choose the Direction (A->Z, Z->A, both) by using the option button
− Click on Ok.
One NIM point is created if Direction is A->Z, or Z->A. Two NIM points are
created if both direction is selected.
The NIM point(s) is(are) created in the 1354 BM for each allocated, implemented,
commissioned hard PVCs using the transmission path.
For each implemented, commissioned hard PVCs (in function of the chosen layer)
using the transmission path, a request is sent to the impacted NE to create the
required NIMs.
3AG 86577 ABAA Ed3 249/725

3.4.13 Modify MiniActiveImaLink Num

This function allows to Modify Mini active IMA link num which range is
restricted automatically by IMA link.
his function allows to create NIM points on the VPL_Ts and/or VCL_Ts of all the
PVCs (hard VPCs/ hard VCCs) passing through a transmission path extremity.
Alcatel
- The IMA value can be Modified in any state, default value is 1 and rang is 1-16
when the IMA have no any IMA link.
IAM in the list => Modify MiniActiveImaLink Num
Range of Min ImaLink Num is restricted automatically by IMA link(1-16 or 1-32).
3.4.14 Partition a transmission path

This function consists in separating bandwidth management for DBR Class 1&2,
DBR Class U (=UBR), UBR+ and SBR traffic contracts.
To have more information about partition, refer to §1.4.1
- The transmissio n path must be configured for the Hard routing service.
The 1354 BM automat ically creates default partit ioning at the time o f the
configuration of the transmissio n paths. This function just consists in modifying
the partit ioning by default.
3AG 86577 ABAA Ed3 250/725

transmissio n path in the list => Partition
Alcatel
Figure 3-80 Transmission Path Partitioning window
The window shown above appears in ITU-T mode (default mode). When using
the ATM Forum mode, the traffic contracts terminology changes. For equivalence
table, refer to chapter 9, 'Traffic contracts standards' sect ion.
The window is split into four areas:

− The Forward Available Bandwidth area gives the available bandwidth in A to
Z (the transpath extremities) direction, according to DBR Class 1&2, DBR
Class U, UBR+ and SBR traffic contracts.
− The Backward Available bandwidth area gives the available bandwidth in Z to

A (the transpath extremities) direction, according to DBR Class 1&2, DBR
Class U, UBR+ and SBR traffic contracts.
3AG 86577 ABAA Ed3 251/725

− The Used Bandwidth area gives the percentage of used bandwidth dedicated to
the DBR Class 1&2, DBR Class U, UBR+ and SBR traffic contracts (higher
value between forward and backward).
− The Max Partition area gives the maximum percentage of bandwidth dedicated
to the DBR Class 1&2, DBR Class U, UBR+ and SBR traffic contracts:
− Enter a DBR Class 1&2 percentage value (this value means the max
Alcatel
percentage value of transmission path that will be dedicated to the DBR

Class 1&2 logical partition).
− Enter a DBR Class U percentage value (this value means the max
percentage value of transmission path that will be dedicated to the DBR
Class U logical partition).
− Enter a UBR+ percentage value (this value means the max percentage
value of transmission path that will be dedicated to the UBR+ logical
partition).
− Enter a SBR percentage value (this value means the max percentage
value of transmission path that will be dedicated to the SBR logical
partition).
Click on Ok to validate the partitioning.
3AG 86577 ABAA Ed3 252/725

3.4.14.1 Explanation about the transmission path partitioning

The maximum size of each partition is specified in terms of percentage of the

physical Transmission Path bandwidth.
These four partitions can be disjoined (sum of these partitions <= 100 %) or not
(sum of these partitions > 100%).
Alcatel
Example of disjoined partitions
In this example, the sum of the four partitions is less than 100%:
DBR Class 1&2 DBR Class U partition UBR + partition SBR partition
partition
60 % 10 % 15 % 10 %
Figure 3-81 Example of disjoined partitions
The amount of physical bandwidth used by DBR Class 1&2 connections can
never exceed 60% of the transmission path's bandwidth.
The amount of physical bandwidth used by DBR Class U connections can never
exceed 10%.
The amount of physical bandwidth used by UBR+ connections can never exceed
15%.
The amount of physical bandwidth used by SBR connections can never exceed
10%.
Example of not disjoined partitions
In this example, the sum of the four partitions is greater than 100%:
DBR Class 1&2 DBR Class U partition UBR + partition SBR partition
partition
80 % 30 % 40 % 20 %
Figure 3-82 Example of not disjoined partitions
The amount of physical bandwidth used by DBR Class 1&2 connections can
never exceed 80%.
The amount of physical bandwidth used by DBR Class U connections can never
exceed 30%.
The amount of physical bandwidth used by UBR+ connections can never exceed
40%.
The amount of physical bandwidth used by SBR connections can never exceed
20%.
The sum of these four partitions is greater than 100% but the amount of physical
bandwidth that can be used by DBR Class1&2, DBR Class U, UBR+ and SBR
connections cannot exceed 100%.
3AG 86577 ABAA Ed3 253/725

If 80% of the physical bandwidth is used by DBR Class 1&2 connections, the
DBR Class U, UBR+ and SBR connections cannot use more than the remaining
available physical bandwidth (20 % in this case).
In the following figure, no SBR partition is defined, 15 % of the physical

bandwidth is not used; these resources can be used to establish some DBR Class
1&2 or UBR + connections.
Alcatel
For example, the whole 15 % free bandwidth could be used by DBR VPCs, since
40 % remains in the DBR Class 1 section.
But UBR+ VPCs could use only 5% in the 15% free, before the UBR+ partition
max is reached.
In the DBR Class 1&2 partition, among the 40 % of logical available bandwidth,
only 15 % are usable to establish connections, because only 15 % of available
physical bandwidth remains.
Available physical
bandwidth (allowing to 15 Security margin
establish new %
5
DBR/UBR+
connections)
partition size
50 % UBR+
45
25 %
% Logical available
bandwidth Logical
partition size
Physical total bandwidth

80 % DBR
in DBR Class 1&2 bandwidth

= 100% 85
15 used in UBR+
%
% partition
Logical usable bandwidth
= available physical
Effective physical
bandwidth
bandwidth used 40
% Logical bandwidth
used in DBR class
1&2 partition
Transmission Path DBR Class 1&2 UBR+

Hard resources partition partition
The 1354 BM provides also the possibilit y to configure a securit y margin on the
bandwidth of the transmissio n path (i.e. a percentage of bandwidth that can never
be used by PVCs of a given part ition, even if the partitions are not disjo ined).
This configurat ion is global to the network (i.e. the securit y margin is applied on
all the transmissio n paths).
3AG 86577 ABAA Ed3 254/725

3.4.15 Display the transmission path extremities

This function consists in displaying information about the ATM NEs (and/or
ENEs) that support the transmission path extremities.
Alcatel
transmissio n path in the list => Extremities
The window that opens depends on the type of the NE used as the destination of
the transmission path.
When the NE is an ENE, the Transmission Path Extremities window gives

information concerning the adjacent NE whose card is linked to the ETP.
Figure 3-83 Transmission Path Extremities window (without ENE)
3AG 86577 ABAA Ed3 255/725


Alcatel
Figure 3-84 Transmission Path Extremities window (with an ENE)
In both cases, the fields have been filled out at the transmission path creation
(refer to § 3.4.2) time.
3AG 86577 ABAA Ed3 256/725

3.4.16 Display the transmission path bandwidth load

This function consists in providing the user with the bandwidth load of a
transmission path.
In the aim to increase/decrease the transmission path capacity (by adding /

removing the SDH paths), this function informs the operator about the loading of
Alcatel
bandwidth and the number of used VPIs for the transmission path as follow:
− The transmission path is empty: the operator is informed that some reserved
resources are not used (no PVPC carried by the transmission path). The
operator may then send a transmission path deletion request to free the unused
resources.
− The transmission path is loaded (maximum number of connections and/or
overhead of bandwidth threshold): the operator is informed that the
transmission path has no more available resources (the loading crosses a given
threshold). Then, the operator may send a new transmission path creation
request.
The transmissio n path must be configured (operational state = enabled).
transmissio n path in the list => Bandwidth Load
The window that opens depends on the type of routing service (hard or soft)
offered by the transmission path.
3AG 86577 ABAA Ed3 257/725

3.4.16.1 For hard routing service


Alcatel
Figure 3-85 Hard Transmission Path Bandwidth Load window
The window is split into four areas:

− The Overbooking information area give information about the use or not of the
overbooking function. If Overbooking Factor is greater than 100%, it means
that overbooking is applied on the ticked traffic contract(s).
− The Forward Bandwidth and the Backward Bandwidth areas give the following
information for each direction used by the hard PVPCs:
3AG 86577 ABAA Ed3 258/725

. Total (cell/s): total number of cells per second passing through the
transmission path
. Commissioned (%): percentage of bandwidth used by hard PVPCs whose

provisioning state is Commissioned
The hard PVPCs used in soft PVPCs are taken into account in this
percentage.
Alcatel
. Implemented (%): percentage of bandwidth used by hard PVPCs whose

provisioning state is Implemented
. Allocated (%): percentage of bandwidth used by hard PVPCs whose

provisioning state is Allocated
. Reserved (%): percentage of bandwidth reserved during the plug & play
operation (for more information, refer to chapter 8.1)
. Available (%): percentage of bandwidth not used by any hard PVPCs
Pie-chart showing in another way the previous percentages.
− The Nb. PVPC area gives:

− The total number of hard PVPCs using the transmission path
− The number of hard PVPCs using the transmission path according to their
provisioning state
− The number of hard PVPCs whose usage state is reserved.
The percentage of used bandwidth is not explicitly indicated. It is the sum of the
Commissioned, Implemented, Allocated and Reserved percentages.
3AG 86577 ABAA Ed3 259/725

3.4.16.2 For soft routing service


Alcatel
Figure 3-86 Soft Transmission Path Bandwidth Load window
The Forward Bandwidth and the Backward Bandwidth areas give the following
information for each direction used by the soft PVPCs:
− Total (cell/s): total number of cells per second passing through the
transmission path.
− Established (%): percentage of bandwidth used by soft PVPCs whose
provisioning state is Established.
− Available (%): percentage of bandwidth not used by any soft PVPCs.
− bar-chart showing in another way the previous percentages.
3AG 86577 ABAA Ed3 260/725

3.4.17 Display the fault localization

This function consists in displaying physical entities (TP/VP_A, VPL_T, VCL_T)

alarms for a transmission path.
Alcatel
- The availabilit y status of the transmissio n path must be either Degraded or In

Failure.
transmissio n path in the list => Fault Localization List
Figure 3-87 Fault Localization List (Transmission Path)

− NE User Label
− Operator Label
− Alarm Status
− Date
− Probable Cause
3AG 86577 ABAA Ed3 261/725

The 1354 BM will display up to 100 alarms. When the number of alarms is
superior to 100, the fo llowing confirmation box is displayed:
Alcatel
The data displayed are never refreshed in real t ime. A Actualize button is
available.
3AG 86577 ABAA Ed3 262/725

3.4.18 Display the transmission path properties

This function consists in displaying information about a transmission path.
transmissio n path in the list => Properties
Alcatel
Figure 3-89 Transmission Path Properties window
3AG 86577 ABAA Ed3 263/725

§ 3.4.2) time.
performed on the transmission path.
The field “IMA” depends if the transmission has been created as an IMA
transmission path or not.
Alcatel
If the transmission path is not IMA, the field “Is managed by RM” is displayed
and depends if the NE extremities are managed or not by 1354 RM.
3AG 86577 ABAA Ed3 264/725

4 Network Management

Alcatel
4 Network management
The network management consists in:
4.1 Managing hard PVPCs
4.2 Managing hard PVPC Legs
4.3 Managing hard PVCCs
4.4 Managing hard PVCC Legs
4.5 Managing soft PVPCs
4.6 Managing soft PVCCs
3AG 86577 ABAA Ed3 265/725

The network management chain gives the order in which the management must be performed.
Manage Transmission Paths Network construction

(refer to chapter 3)
Alcatel
Network management
(this chapter)
Define hard point-to- Define hard point-

Define soft PVPCs
multipoints PVPCs to-point PVPCs
Define hard
PVPCs Legs
Define hard point-to- Define hard point- Define soft PVCCs

multipoints PVCCs to-point PVCCs
Define hard
PVCCs Legs
Figure 4-1 Network management chain
3AG 86577 ABAA Ed3 266/725

4.1 Managing hard PVPCs
The hard PVPC management, part of the network management, consists in:
defining hard PVPCs:
Alcatel
traffic profile
extremities
legs (optional)
defining / deleting routing constraints
modifying hard PVPCs or hard PVPCs Legs user label and / or comment
setting in / out of service hard PVPCs:
allocation / de-allocation function
implementation / de-implementation function
commissioning / de-commissioning function
managing the use of the hard PVPCs:
− lock / unlock function
NAD Label assignment function
UPC / NPC activation / deactivation function
output shaping activation / deactivation function
activating / deactivating the continuity check (CC) on hard PVPCs
modifying their bandwidth by choosing another traffic profile
NIM and NIM CC configuration function
− displaying hard PVPC information such as:

hard PVPC list, hard PVPC NIM list, hard PVPC NIM CC list, hard PVPC
Constraints list, hard PVPC Leg list
extremities and properties
bandwidth load, traffic and routing
fault localization
graphical view
3AG 86577 ABAA Ed3 267/725

The hard PVPC management chain gives the order in which the available actions
may be performed.
Delete
Define
Alcatel
Lock /
Modify Unlock
Activate / De-
activate
UPC/NPC
Allocate
De-allocate
Activate / De-
Configure / activate
De-configure output shaping
NIM
Modify
Assign bandwidth
NAD Label
Implement De-implement
Activate/
deactivate CC
Commission De-commission
Figure 4-2 Hard point-to-point PVPC management chain
3AG 86577 ABAA Ed3 268/725

The figure below shows the evolution of the provisioning state according to the
operation performed on the hard PVPC.
Define Commi ssion Commissioned

Alcatel
Implement
Implemented
Allocate De-commission
Allocated
De-implement
Defined
De-allocate De-implement *
Delete
* Allows to de-implement a PVC whose some NEs caused problems during a previous try
Figure 4-3 Hard PVPC provisioning state
For managing hard PVPCs, you can:
display the hard PVPC list, refer to § 4.1.1
3AG 86577 ABAA Ed3 269/725

4.1.1 Display the hard PVPC list

The hard PVPC list presents all the hard point-to-point PVPCs and point-to-
multipoints PVPCs managed by the 1354 BM and their descriptive attributes.
Alcatel
The hard PVPCs used in soft PVPCs are not listed here.
From the Main view, menu: Management => Hard => PVPC
Figure 4-4 Hard PVPC List window
By default, the list window displays all Hard PVPCs belonging to the Root sub-
network.
sensitive help (or enter * value to have the complete list) and click on Load button.
The descriptive attributes displayed for each hard PVPC are:

− User Label
− Provis. State
− Usage State
− Activity State
− Cast Type
− Traffic Contract
− NAD Label
3AG 86577 ABAA Ed3 270/725


− User Label
− Provisionning State
Alcatel
− NAD Label
3AG 86577 ABAA Ed3 271/725

Alcatel
3AG 86577 ABAA Ed3


Figure 4-5 Hard PVPC Search window
272/725
From the hard PVPC list, you can:
define a hard PVPC, refer to § 4.1.2
modify a hard PVPC, refer to § 4.1.3

Alcatel
delete a hard PVPC, refer to § 4.1.4
allocate a hard PVPC, refer to § 4.1.5
de-allocate a hard PVPC, refer to § 4.1.6
implement a hard PVPC, refer to § 4.1.7
de-implement a hard PVPC, refer to § 4.1.8
commission a hard PVPC, refer to § 4.1.9
decommission a hard PVPC, refer to § 4.1.10
lock a hard PVPC, refer to § 4.1.11
unlock a hard PVPC, refer to § 4.1.12
assign NAD Label to a Hard PVPC, refer to § 4.1.13
activate the output shaping on a hard PVPC, refer to § 4.1.14
deactivate the output shaping on a hard PVPC, refer to § 4.1.15
activate UPC / NPC on a hard PVPC, refer to § 4.1.16
deactivate UPC / NPC on a hard PVPC, refer to § 4.1.17
activate CC on a hard PVPC, refer to § 4.1.18
deactivate CC on a hard PVPC, refer to § 4.1.19
modify the bandwidth of a hard PVPC, refer to § 4.1.20
display the hard PVPC extremities, refer to § 4.1.21
display the hard PVPC properties, refer to § 4.1.22
display the hard PVPC bandwidth load, refer to § 4.1.23
display the hard PVPC traffic properties, refer to § 4.1.24
display the hard PVPC routing properties, refer to § 4.1.25
display the hard PVPC graphical view, refer to § 4.1.26
3AG 86577 ABAA Ed3 273/725

display the fault localization on hard PVPC, refer to § 4.1.27

display the hard PVPC NE NIM list, refer to § 4.1.28
configure the hard PVPC NE NIMs, refer to § 4.1.28.1
display the hard PVPC NIM CC list, refer to § 4.1.29

Alcatel
display the hard PVPC constraints list, refer to § 4.1.29.1
add constraint to the hard PVPC, refer to § 4.1.30.1
delete constraint from a hard PVPC, refer to § 4.1.30.2
if the Hard PVPC selected is a Point-Multipoints Hard PVPC:
display the Hard PVPC Legs List, refer to § 4.2.1
show the associated Legs, refer to § 4.2.2
3AG 86577 ABAA Ed3 274/725

4.1.2 Define a hard PVPC

This function consists in identifying the hard PVPC and determining its traffic
profile and the ATM NEs (and/or ENEs) that support its extremities.
- The ATM NEs (and/or ENEs) supporting the extremit ies of the hard PVPC must
Alcatel
be previously defined.
- Both transmission paths supporting the extremit ies of the hard PVPC must exist
and be configured.
- The maximum number of PVPCs must not be reached.
From the Main view, menu: Management => Hard => PVPC => no hard PVPC
selected in the list => Define Hard PVPC
3AG 86577 ABAA Ed3 275/725


Alcatel
Figure 4-6 Hard PVPC Definition window
To define a hard PVPC:

− Enter a User Label
− Enter a Comment (optional)
− Choose a Target:
− Defined: this state show only the definition of the hard PVPC.
3AG 86577 ABAA Ed3 276/725

− Allocated: in this state, the 1354 BM automatically retrieves the hard PVPC
characteristics and searches eligible Transmission Paths among those which

verify conditions (Transmission Path operational state is enabled, and type is
hard, and administrative state is unlocked).
− Implemented: this state consists in directly doing the establishment of all
involved VPL and the establishment of the required cross-connections end
end-connections.
Alcatel
− Enter the Utilization Factor (optional):

Utilization factor can have a value from 1% to 100% (default value = 100%).
concerned hard PVPC.
divided by 2.
- Utilizat ion factor must be set to 100% for hard PVPC DBR Class 1.
− Tick the Point-to-Multipoint check box if you want to define a Point-Multipoint
hard PVPC.
If Point-to-Multipoint check box is ticked, enter the Leg User Label.
- An unidirect ional Traffic Profile must be previously defined (refer to §

7.2.2.2).
- Extremit ies must be ENEs.
- A PVPC Leg (with the entered Leg User Label value) will be
automat ically defined and associated to the point-mult ipoints hard PVPC
at the end of Hard PVPC definit ion.
- The state of the Leg will be the same as the hard PVPC (defined,
allocated, or implemented).
− In the Profile area:
− Choose the traffic profile by using the Service Type and Description option
buttons (the items proposed by the Description option button depend on the
Service Type previously chosen).
− To get detailed information about the parameters of the chosen profile, click
on Properties. The window becomes as below.
- To define a flexible unitary hard PVPC (which will not consume any
bandwidth on the transmissio n path that will carry it), selects the specific
traffic profile wit h Service Type = FLEXIBLE, Descript ion = FOR_VPC.
Any kind o f hard PVCC can be established over it.
3AG 86577 ABAA Ed3 277/725

− Shaping Protection Mode (None, grooming, edge, grooming+edge) option

button is available if the choosen Target is Allocated or Implemented.
Alcatel
Figure 4-7 Hard PVPC Definition (extended view)
− In the Origin (A) and Destination (Z) areas, enter the identification parameters of
the NEs and/or ENEs that support the hard PVPC extremities:
− Tick the ENE check box if the extremity is supported by an ENE.

− Choose the NE (or ENE) User Label by using the sensitive help.
− Choose the Termination Id. (or ETP Id. if the extremity is supported by an
ENE) by using the sensitive help.
- The choosen Terminat ion Id. determinates the transmissio n paths

extremit ies. The VCI range of the hard PVPC is inherited fro m the transmissio n
paths connected to the extremit ies. Note that the VCI ranges of the two
transmissio n paths must be the same.
3AG 86577 ABAA Ed3 278/725

− Enter a VPI number by using the sensitive help:

The VPI field displays the first ten values which do not belong to any
PVPCs (even for defined PVPCs).
− The VPI field is empty if there are no idle VPIs on the transmission path.
Click on Ok.
Alcatel
The traffic contracts of hard VPCs which are authorized are:

− DBR Class 1, DBR Class 2 cell based
− DBR Class U (UBR.1) cell based
− UBR+ (= DBR Class U (UBR.2) with MDCR > 0) cell based
− SBR.1 Class 1, SBR.1 Class 2, SBR.2 Class 3, SBR.3 Class 3 cell based
The hard PVPC is defined into the 1354 BM with the following states:
− provisioning state : Defined, Allocated or Implemented (depending the
target choosen)
− consistency state : Consistent
− availability status : None (not significant)
− cast type : Point-to-Point or Point-to-Multipoints
− usage state of each transmission path at extremities of the hard PVPC is changed
to busy if it was idle.
− UPC/NPC state:
Disabled if the interface types of the transmission paths of both extremities
are NNI
Enabled if the interface type of at least one transmission path of both
extremities is ICI or UNI
− shaping state : Disabled
The hard PVPC list is updated.
3AG 86577 ABAA Ed3 279/725

4.1.3 Modify a hard PVPC

The hard PVPC modification gives the possibility to modify:
− User Label
− Comment
Alcatel
− Cost (only if the Provisioning State is at least Allocated)

− Utilization Factor
From the Main view, menu: Management => Hard => PVPC => select one hard
PVPCs in the list => Modify
This funct ion is available only if a hard PVPC is selected.
Figure 4-8 Hard PVPC Modification
To modify a hard PVPC:

− Change the comment
− Change the cost (depending the provisioning state)
− Change the Utilization Factor. It can have a value from 1% to 100%.
concerned hard PVPC.
divided by 2.
Utilization factor must be set to 100% for hard PVPC DBR Class 1.
3AG 86577 ABAA Ed3 280/725

The effective bandwidth of the hard PVPC is re-computed according to the new
value of utilization factor.
If the hard PVPC is allocated, the bandwidth consumption on the associated

transmission path is re-computed. If the hard PVPC is implemented, the new
utilization factor is downloaded to the NE.
Alcatel
Then, the hard PVPC list, the tree area and the opened graphical views are updated.
The process fails in the fo llowing cases:

− The New User Label already exists.
− If the Utilizat ion Factor is different of 100% and the traffic contract of the
hard PVPC is DBR Class 1.
3AG 86577 ABAA Ed3 281/725

4.1.4 Delete a hard PVPC

This function consists in deleting a hard PVPC from the 1354 BM supervision.
- The provisio ning state of the hard PVPC must be Defined.

Alcatel
- If the hard PVPC is point-mult ipo ints, all Legs belonging to the hard PVPC are
deleted.
From the Main view, menu: Management => Hard => PVPC => select one or
several hard PVPCs in the list => Delete
Figure 4-9 Confirmation box for deleting one hard PVPC
Figure 4-10 Confirmation box for deleting several hard PVPCs
After confirmation, the hard PVPCs are removed.
3AG 86577 ABAA Ed3 282/725

4.1.5 Allocate a hard PVPC

This function consists in searching for transmission paths that may provide
bandwidth for a hard PVPC. The available bandwidth has to satisfy the requirement
of the hard PVPC in terms of traffic contract.
Alcatel
- The provisio ning state of the hard point-to-point PVPC must be Defined.
- The maximum number of PVPCs in each transmis sion path must not be reached.
- There is no control of available bandwidth on the transmissio n path when
allocat ing a flexible hard PVPC.
several hard PVPCs in the list => Allocate
Figure 4-11 Hard PVPC Allocation
Figure 4-12 Allocation for several Hard PVPCs
3AG 86577 ABAA Ed3 283/725

To allocate a hard PVPC, you have to defined some characteristics:

Choose the allocation mode:

− Automatic (with no constraint): consists in searching available bandwidth
on each segment of connection, in each direction, according to the traffic
descriptors of the hard PVPC.
Alcatel
In the figure below, the allocator find a route from A to Z using whatever the
available resources.
Figure 4-13 Automatic routing mode with no constraint
− Semi automatic (wih constraints): consists in associating the hard PVPC

with a list of transmission path or NEs with the indication “To be used” or
“To be excluded”. This list will be taken account during the search of the
route in the aim to find a route according to these constraints (See Display the
constraints list, refer to §4.1.30).
Figure 4-14 Semi-automatic routing mode with constraints
3AG 86577 ABAA Ed3 284/725

− Manual (all the route is specified by the operator): the complete list of
Transmission Path must be previously given as a list of contiguous positive

link constraints (list of transmission paths optionally associated with the VPI
that must be used). (See Display the constraints list, refer to §4.1.30).A
check is done to verify the route continuity.
Alcatel
Figure 4-15 Manual routing mode with constraints
− Select the cost model:

− Shortest path model: by default, each transmission path has length of 1.
Therefore, the shortest path cost model is equivalent to counting the number
of transmission paths used in hard PVPC.
− Cheapest path model: the transmission path weight is a cost. Each
transmission path involved in the routing is associated with a cost value. By
default, the cost is 1. The operator can modify each transmission path cost.
The cost model is accessible only for automat ic and semi automatic mode.
Then, the hard PVPC allocation process is launched:

− Once the eligible transmission paths are identified, the 1354 BM searches for the
shortest (or cheapest) route (passing through the minimum of transmission paths)
that will bind both extremities of the hard PVPC. The hard PVPC route is made of
Virtual Path Links (VPL).
− A VP connection is generated for each ATM NE involved in the hard PVPC in
order to establish the connection between two VPLs and/or the end of the hard
PVPC.
3AG 86577 ABAA Ed3 285/725


− There is not enough bandwidth on origin or destination Transmission Path.
− The origin or the destination Transmission Path is locked.
− The route is not found.
Alcatel
When the process is finished, the provisioning state of the hard PVPC(s) changes to
Allocated. For a point-multipoints hard PVPC, all Legs in defined provisioning state
belonging to the hard PVPC are allocated too.
The Usage State of each transmission path used by the hard PVPC changes to Busy
(if it was not yet).
The bandwidth load of each transmission path used by the hard PVPC is updated for
both directions (forward and backward for bidirectional, only forward for
unidirectional traffic).
The transmission path list and the transmission path bandwidth load windows are
updated too.
The Administrative State changes from None to Unlocked.
3AG 86577 ABAA Ed3 286/725

4.1.6 De-allocate a hard PVPC

This function consists in releasing all the resources involved in a hard PVPC.
- The provisio ning state of the hard PVPC must be Allocated.

Alcatel
- The usage state of the hard PVPC must be Idle.
- The hard PVPC must not be associated to a PM Measure.
several hard PVPCs in the list => De-allocate
Figure 4-16 Confirmation box for de-allocating one hard PVPC
Figure 4-17 Confirmation box for de-allocating several hard PVPCs
After confirmation, the hard PVPCs are de-allocated.
Their provisioning states change to Defined.
For a point-multipoints hard PVPC, all allocated Legs change to Defined too.
The Usage State of each transmission path used by the hard PVPC is changed to Idle
if not any other hard PVPCs or Legs are carried.
3AG 86577 ABAA Ed3 287/725

The bandwidth load of each transmission path used by the hard PVPC is updated
(forward and backward for a point-to-point PVPC, forward for a point-multipoints

PVPC).
The transmission path list and the transmission path bandwidth load windows are
Alcatel
updated too.
3AG 86577 ABAA Ed3 288/725

4.1.7 Implement a hard PVPC

This function consists in implementing all the VPLs involved in a hard PVPC (refer
to § 4.1.2). Thus all the ATM NEs providing the end-connections and cross-
connections along the hard PVPC route have to satisfy the traffic contract
requirements (ATC, QoS).
Alcatel
- The provisio ning state of the hard PVPC must be Allocated.
- The consistency state of the hard PVPC must be Consistent.
- Act ivit y state of the concerned NEs must be None (= no audit/alignment or

several hard PVPCs in the list => Implement
Figure 4-18 Confirmation box for implementing one hard PVPC
Figure 4-19 Confirmation box for implementing several hard PVPCs
After confirmation, the hard PVPC implementation process is launched.
3AG 86577 ABAA Ed3 289/725

Only the transmissio n paths invo lved in the hard PVPC and whose administrative
state is Unlocked will be taken into account.
If at least one ATM NE rejects the implementation, all the already implemented
cross-connections and end-connections are de-implemented. A message is displayed
asking the operator to cancel the implementation or to authorize the search for
Alcatel
another route. This process can be repeated N times. (Not available in release R7)
If all the concerned ATM NEs accept the requirements of the new hard PVPC, the
implementation is successful.
The hard PVPC provisioning state changes to Implemented and their availability
status are updated and managed in function of the alarms.
both directions (forward and backward).
The transmission path bandwidth load window is updated too.
3AG 86577 ABAA Ed3 290/725

4.1.8 De-implement a hard PVPC

This function consists in removing all the end-connections and cross-connections
involved in a hard PVPC and previously performed at ATM NE level.
- The provisio ning state of the hard PVPC must be Implemented or Allocated.
Alcatel
- The tunnel state of the hard PVPC must be Disable d.
- The provisio ning states of all the PVCCs passing through the hard PVPC must be
Allocated or Defined.
- CC and PM must not be running.

several hard PVPCs in the list => De-implement
Figure 4-20 Confirmation box for de-implementing one hard PVPC
Figure 4-21 Confirmation box for de-implementing several hard PVPCs
3AG 86577 ABAA Ed3 291/725

After confirmation, the hard PVPC de-implementation process is launched.

If at least one ATM NE rejects the de-implementation, all the already de-
implemented cross-connections and end-connections remain de-implemented and the
1354 BM keeps de-implementing the other connections. But the hard PVPC
provisioning state changes to Allocated.
Alcatel
If all the concerned ATM NEs accept the de-implementation, the process is
successful. The hard PVPC provisioning state changes to Allocated and the
availability status change to None (no more significant).
3AG 86577 ABAA Ed3 292/725

4.1.9 Commission a hard PVPC

This function consists in setting in service a hard PVPC.
- The provisio ning state of the hard PVPC must be Implemented.

Alcatel
several hard PVPCs in the list => Commission
Figure 4-22 Confirmation box for commissioning one hard PVPC
Figure 4-23 Confirmation box for commissioning several hard PVPCs
After confirmation, the hard PVPCs are commissioned. Their provisioning states
change to Commissioned.
3AG 86577 ABAA Ed3 293/725

4.1.10 De-commission a hard PVPC

This function consists in setting out of service a hard PVPC.
- The provisio ning state of the hard PVPC must be Commissio ned.
Alcatel
- The provisio ning state of all the hard PVCCs passing through the hard PVPC
must not be Commissio ned.
several hard PVPCs in the list => De-commission
Figure 4-24 Confirmation box for de-commissioning one hard PVPC
Figure 4-25 Confirmation box for de-commissioning several hard PVPCs
After confirmation, the hard PVPCs are de-commissioned. Their provisioning states
change to Implemented.
3AG 86577 ABAA Ed3 294/725

4.1.11 Lock a hard PVPC

This function consists in preventing the hard PVPC to be used for the cell transport.
- The provisio ning state of the hard PVPC must be Allocated, Implemented or
Commissio ned.
Alcatel
- The administrative state of the hard PVPC must be Unlocked.
several hard PVPCs in the list => Lock
Figure 4-26 Confirmation box for locking one hard PVPC
Figure 4-27 Confirmation box for locking several hard PVPCs
After confirmation, the administrative states of the hard PVPCs change to Locked.
The allocated or implemented hard PVCCs, already using the hard PVPC, are not
impacted by the lock request. They can be de-implemented and de-allocated.
The hard PVPC cannot be used for the allocation of a new hard PVCC.
The implementation of other hard PVCCs whose route uses the hard PVPC is
prohibited.
The established soft PVCCs, already using the hard PVPC, are not impacted by the
lock request. They can be released.
3AG 86577 ABAA Ed3 295/725

4.1.12 Unlock a hard PVPC

This function consists in unlocking a previously locked hard PVPC.
- The administrative state of the hard PVPC must be Locked.

Alcatel
several hard PVPC in the list => Unlock
Figure 4-28 Confirmation box for unlocking one hard PVPC
Figure 4-29 Confirmation box for unlocking several hard PVPCs
After confirmation, the administrative states of the hard PVPCs change to Unlocked.
3AG 86577 ABAA Ed3 296/725

4.1.13 Assign NAD Label to a hard PVPC

This function consists in assigning a NAD Label to a hard PVPC.
Alcatel
several hard PVPCs in the list => Assign NAD Label
Figure 4-30 NAD Label assignment window for one hard PVPC
Figure 4-31 NAD Label assignment window for several hard PVPCs
To assign a NAD Label to the selected hard PVPC:

− Choose the NAD Label by using the sensitive help (a list of available initiators is
proposed)
− Click on Ok.
The selected hard PVPC is updated with the selected NAD label and the Hard PVPC
List window is updated.
3AG 86577 ABAA Ed3 297/725

4.1.14 Activate the output shaping on a hard PVPC

This function consists in enabling the output-shaping feature on a hard PVPC.
negotiated PCR.
Alcatel
- The provisio ning state of the hard PVPC must be Defined or Allocated.
- The shaping state of the hard PVPC must be Disabled.
- The traffic contract of the hard PVPC must be DBR class 1 with a PCR included
between a minimum and a maximum value (refer to §10.1).
- All the ATM NEs used by the hard PVPC have to support the output shaping
feature.
- The maximum number of shaped PVPC must not be reach (refer to §10.1).
- The hard PVPC must not be unitary.
several hard PVPCs in the list => Act. Shap.
Figure 4-32 Confirmation box for activating the output shaping on one hard PVPC
3AG 86577 ABAA Ed3 298/725


Alcatel
Figure 4-33 Confirmation box for activating the output shaping on several hard PVPCs
To activate the output shaping on one hard PVPC:

− Choose the location where the output shaping will be activated, by using the
Shaping Protection Mode option button:
− Grooming: the output shaping is activated only at the extremity of a
terminated PVPC (source point).
− Edge: the output shaping is activated only at the edge of the network. In this
case, there is no impact about the quality of the PVPC.
− Click on Ok.
To activate the output shaping on several hard PVPCs:

− If you click on All, the chosen parameter are valid for each selected hard PVPC.
− If you click on Yes, the parameter is valid only for the hard PVPC currently
displayed in the confirmation box.
The shaping state of the hard PVPC changes to Enabled.
At next implementation of the hard PVPC, the output shaping activation request will
be sent to the chosen NEs.
3AG 86577 ABAA Ed3 299/725

4.1.15 Deactivate the output shaping on a hard PVPC

This function consists in disabling the output shaping function on a hard PVPC.
- The shaping state of the hard PVPC must be Enabled.

Alcatel
- The usage state of the hard PVPC must be Idle, if shaping mode is not edge
A VPC output shaped for grooming or grooming + edge is able to carry VCCs with
any traffic contract.
When the output shaping is deact ivated, the VPC becomes a classical DBR class1
VPC, and it should respect the traffic compatibilit y rules ( a DBR class1 VPC is able
to carry only DBR class1 and DBR class2 VCCs).
In order to avoid some traffic inco mpat ibilit y between the VPC and the carried
VCCs, the deactivat ion of output shaping (grooming or grooming + edge) is
forbidden if the VPC usage state is busy.
several hard PVPCs in the list => Deact. Shap.
Figure 4-34 Confirmation box for deactivating the output shaping on one hard PVPC
Figure 4-35 Confirmation box for deactivating the output shaping on several hard PVPCs
After confirmation, the shaping state of each hard PVPCs changes to Disabled.
3AG 86577 ABAA Ed3 300/725

4.1.16 Activate UPC / NPC on a hard PVPC

This function consists in activating an ATM police control on a hard PVPC that
passes through the ATM network.
- The provisio ning state of the hard PVPC must be Defined, Allocated or Partially
Alcatel
Allocated.
- The UPC / NPC state of the hard PVPC must be Disabled.
- The interface type of the hard VPC must be ICI or UNI.
When these condit ions are respected, the UPC / NPC is by default activated.
several hard PVPCs in the list => Act. UPC
Figure 4-36 Confirmation box for activating UPC / NPC on one hard PVPC
Figure 4-37 Confirmation box for activating UPC / NPC on several hard PVPCs
After confirmation, the UPC / NPC state of each hard PVPC changes to Enabled.
At next implementation of the hard PVPC, the UPC / NPC activation request will be
sent to the first NE (linked to the ENE) in the border of the network.
3AG 86577 ABAA Ed3 301/725

4.1.17 Deactivate UPC / NPC on a hard PVPC

This function consists in deactivating the ATM police control on a hard PVPC.
- The UPC / NPC state of the hard PVPC must be Enabled.

Alcatel
several hard PVPCs in the list => Deact. UPC
Figure 4-38 Confirmation box for deactivating UPC / NPC on one hard PVPC
Figure 4-39 Confirmation box for deactivating UPC / NPC on several hard PVPCs
After confirmation, the UPC / NPC states of the hard PVPCs change to Disabled.
3AG 86577 ABAA Ed3 302/725

4.1.18 Activate CC on a hard PVPC

This function consists in activating the Continuity Check (CC) for one or both
direction of a hard PVPC point-to-point in its extremities.
- The provisio ning state of the hard PVPC point-to-point must be Implemented or
Alcatel
Commissio ned.
- The CC state of the hard PVPC must be Deact ivated or Partially Act ivated.
several hard PVPCs in the list => Activate CC
Figure 4-40 Confirmation box for activating CC on one hard PVPC
Figure 4-41 Confirmation box for activating CC on several hard PVPCs
To activate the Continuity Check service on the selected hard PVPC:

− Choose the OAM CC Direction (A->Z, Z->A, both) compatible with the
direction of the selected hard PVPC.
3AG 86577 ABAA Ed3 303/725

After confirmation, activation requests are sent to each extremity following the
procedure below:
In A to Z direction if the selected direction is A->Z:
. Activate CC request is sent to A endpoint (if the point is an ATM NE) to
activate the insertion process of the Continuity Check.
. Activate CC request is sent to Z endpoint (if the point is an ATM NE) to
Alcatel
activate the detection process of the Continuity Check.

In Z to A direction if the selected direction is Z->A:
activate the insertion process of the Continuity Check.
. Activate CC request is sent to A endpoint (if the point is an ATM NE) to
In both ways if the hard PVPC is bidirectional:
. Requests for the A to Z direction.
. Requests for the Z to A direction.
Then, the Continuity Check is activated on the hard PVPC extremities and the CC
state of each hard PVPC changes to Activated.
If detection process failed (ex : if the NE is not available or if its LAC state is equal
to Granted), the CC state is set to Partially Activated. The operator has the
possibility to re-launch the activate CC command in order to complete the CC
activation (detection process part).
3AG 86577 ABAA Ed3 304/725

4.1.19 Deactivate CC on a hard PVPC

This function consists in deactivating the Continuity Check on a hard PVPC.
- The CC state of the hard PVPC must be Act ivated or Partially Act ivated.
Alcatel
several hard PVPCs in the list => Deact. CC
Figure 4-42 Confirmation box for deactivating CC on one hard PVPC
Figure 4-43 Confirmation box for deactivating CC on several hard PVPCs
The system retrieves the extremities and all NIM points of the hard PVPC where the
Continuity Check on detection is activated (NIM called NIM CC).
3AG 86577 ABAA Ed3 305/725

The deactivation requests are sent to each extremity following the below procedure:
In A to Z direction:
. Deactivate CC request is sent to all NIM CC points and after to the Z
endpoint (if the point is an ATM NE) to deactivate the detection-process of
the Continuity Check.
. Deactivate CC request is sent to A endpoint (if the point is an ATM NE)
Alcatel
to deactivate the insertion-process of the Continuity Check.

In Z to A direction:
. Deactivate CC request is sent to all NIM CC points and after to the A
. Deactivate CC request is sent to Z endpoint (if the point is an ATM NE)
In the both way:
Then, the Continuity Check is de-activated on all NIM CC points and on all the
surveillance points of the hard PVPC and its CC state changes to Deactivated.
3AG 86577 ABAA Ed3 306/725

4.1.20 Modify the bandwidth of a hard PVPC

This function consists in modifying the traffic profile of a point-to-point hard PVPC.
The modification is limited to the PCR and the MCR and implies a traffic
perturbation.
Alcatel
- The provisio ning state of the hard PVPC must not be in the Co mmissioned state.
- The hard PVPC must be point-to-point and between two ENEs.
- The hard PVPC and the transmissio n path(s) carrying the hard PVPC must not be
locked.
- At least, another compat ible traffic profile must be available (with same traffic
type and same direct ion as the current profile). If not, the error message 'No
available traffic profile' is displayed.
- A lock of concurrent sessio ns will be done just before starting the bandwidth
modificat ion treatment (= on click on Ok button).
PVPCs in the list => Modify BW
This funct ion is available only if a Hard PVPC is selected.
Figure 4-44 Hard PVPC Bandwidth Modification window
3AG 86577 ABAA Ed3 307/725

To modify the bandwidth of a hard PVPC:

− Select a New Traffic in the New Profile area. New traffics suggested have the
same traffic type and same direction as the current profile.
To get detailed information about the parameters of the chosen profile, click on
Alcatel
Properties. The window becomes as below:
Figure 4-45 Hard PVPC Bandwidth Modification window (extended view)
The 1354 BM locks the others opened sessions and checks:
3AG 86577 ABAA Ed3 308/725

− if all the NEs on the hard PVPC route are reachable,

− if, in case of bandwidth increase, there is enough available bandwidh on the

transmission paths that compose the hard PVPC route and in the partition related
to the hard PVPC traffic type.
− if, in case of bandwidth decrease, the new hard PVPC bandwidth is rather large to
carry the hard PVCC(s) already implemented and allocated.
Alcatel
After all the checks, the 1354 BM:

− de-implements the hard PVCC(s) which provisioning state is implemented,
− de-implements the hard PVPC,
− assigns the new traffic profile to the hard PVPC,
− re-implements the hard PVPC with its new traffic profile (if needed, the traffic
descriptor is created on the NEs),
− re-implements the hard PVCC(s).

− One (or more) NE(s) on the hard PVPC route is (are) unreachable.
− Not enough available bandwidth on the transmission paths that compose the hard
PVPC route.
− Not enough available bandwidth for the hard PVCCs carried by the hard PVPC.
3AG 86577 ABAA Ed3 309/725

4.1.21 Display the hard PVPC extremities

This function consists in displaying information about the ATM NEs (and/or ENEs)
that support the hard PVPC extremities.
Alcatel
From the Main view, menu: Management => Hard => PVPC => select a hard
PVPC in the list => Extremities
Figure 4-46 Point-to-Point Hard PVPC Extremities window
3AG 86577 ABAA Ed3 310/725

If the selected Hard PVPC is point-to-MultiPoints, the following window is

displayed:
Alcatel
Figure 4-47 Point-Multipoints Hard PVPC Extremities window
The fields have been filled out at the hard PVPC definition (refer to § 4.1.2) time.
3AG 86577 ABAA Ed3 311/725

4.1.22 Display the hard PVPC properties

This function consists in displaying information concerning the last action performed
on a hard PVPC.
Alcatel
PVPC in the list => Properties
The first fields have been filled out at the hard PVPC definition (refer to § 4.1.2)
time.
The last two ones give information about the last action performed on the hard
PVPC.
3AG 86577 ABAA Ed3 312/725

Alcatel
3AG 86577 ABAA Ed3

Figure 4-48 Hard PVPC Properties window
313/725
4.1.23 Display the hard PVPC bandwidth load

This function consists in displaying information about the hard PVPC bandwidth
load and the number of hard PVCCs using this hard PVPC.
Alcatel
Commissio ned.
PVPC in the list => Bandwidth Load
Figure 4-49 Point-to-Point Hard PVPC Bandwidth Load window
3AG 86577 ABAA Ed3 314/725


Alcatel
Figure 4-50 Point-MultiPoints Hard PVPC Bandwidth Load window
The window is split into areas:

information for each direction used by the PVCCs:
− Total (cell/s): total number of cells per second passing through the hard
PVPC
− Commissioned (%): percentage of bandwidth used by PVCCs whose
provisioning state is Commissioned
For a point-mult ipo ints hard PVCC only the Forward Bandwidth informat ions are
displayed.
3AG 86577 ABAA Ed3 315/725

The hard PVCCs used in so ft PVCCs are taken into account in this percentage.
Implemented (%): percentage of bandwidth used by PVCCs whose provisioning
state is Implemented
Allocated (%): percentage of bandwidth used by PVCCs whose provisioning state
is Allocated
Alcatel
Reserved (%): percentage of bandwidth reserved during the plug & play operation
(for more information, refer to chapter 7)
Available (%): percentage of bandwidth not used by any PVCCs
Pie-chart showing in another way the previous percentages
− The Nb. PVCC area gives:

the total number of PVCCs using the hard PVPC
the number of PVCCs using the hard PVPC according to their provisioning state
the number of PVCCs whose usage state is reserved
The percentage of used bandwidth is not explicitly indicated. It is the sum of the
Commissioned, Implemented, Allocated and Reserved percentages.
3AG 86577 ABAA Ed3 316/725

4.1.24 Display the hard PVPC traffic properties

This function consists in displaying information about the traffic contract performed
by a hard PVPC.
Alcatel
PVPC in the list => Traffic
Figure 4-51 Hard PVPC Traffic Properties window
Figure 4-52 Hard PVPC Traffic Properties window
The number of items displayed in the Forward and Backward areas depends on the
traffic contract.
3AG 86577 ABAA Ed3 317/725

4.1.25 Display the hard PVPC routing properties

This function consists in displaying the list of the VPLs used by the hard PVPC.
A VPL is defined by a transmission path and a VPi used on it.

Alcatel
Commissio ned.
PVPC in the list => Routing
Figure 4-53 Hard PVPC Routing Properties window
The attributes displayed in the Route area are:

− VPI
− IMA (if the transmission path is IMA or not)
− Bit Rate
− Is Managed by RM (if the transmission path is managed by the 1354 RM or
not)
− Under PM (if the transmission path is under PM or not)
3AG 86577 ABAA Ed3 318/725

4.1.26 Display the hard PVPC graphical view

This function consists in displaying the graphical view (hard transmission path
domain) corresponding to the sub-network that contains the transmission paths used
by the hard PVPC.
Alcatel
Commissio ned.
PVPC in the list => Display Route
Figure 4-54 Sub-network view showing the transmission paths used by the hard PVPC
3AG 86577 ABAA Ed3 319/725

The following commands are available from the graphical view, depending on the
selected object and its position on the route:

− With no selection: Begin and End commands allow to highlight the NE used for
the beginning or the end of the route
− With a selected entity (NE, transmission path, ENE, Off page connector): Begin
and End commands are completed by other commands depending on the selected
Alcatel
entity.
3AG 86577 ABAA Ed3 320/725

4.1.27 Display the fault localization on hard PVPC

alarms for a hard PVPC.
- The availabilit y status of the hard PVPC must be eit her Degraded or In failure.
Alcatel
PVPC in the list => Fault Localization List
Figure 4-55 Fault Localization List (Hard PVPC)

− NE User Label
− Operator Label (user label + ATM port)
− Alarm Status
− Date of the alarm reception
− Probable Cause
3AG 86577 ABAA Ed3 321/725

The 1354 BM will display up to 100 alarms. When the number of alarms is superior
to 100, the fo llowing confirmat ion box is displaye d:
Alcatel
The data displayed are never refreshed in real t ime. A Actualize button is available.
3AG 86577 ABAA Ed3 322/725

4.1.28 Display the hard PVPC NE NIM list

The hard PVPC NE NIM presents all the switched VCLs constituting the selected
hard PVPC and allows to configure the NIMs on each intermediate point of the hard
PVPC.
Alcatel
- The hard PVPC must be point-to-point, at least Allocated and not unitary.
PVPC in the list => NE NIM List
Figure 4-57 Hard PVPC NE NIM List window
The descriptive attributes displayed for each hard PVPC NE NIM are:
− NE User Label
− A Term Id.
− A Vpi
− A Ing.
− A Ing. State (None, On NE, On 1354 BM)
− A Egr.
− A Egr. State (None, On NE, On 1354 BM)
− Z Term Id.
− Z Vpi
− Z Ing.
− Z Ing. State (None, On NE, On 1354 BM)
− Z Egr.
− Z Egr. State (None, On NE, On 1354 BM)
3AG 86577 ABAA Ed3 323/725



− NE User Label
Alcatel
Figure 4-58 Hard PVPC NE NIM Search window
From the hard PVPC NE NIM list, you can:
configure / de-configure the hard PVPC NE NIMs, refer to § 4.1.28.1
3AG 86577 ABAA Ed3 324/725

4.1.28.1 Configure / de-configure the hard PVPC NE NIMs

This function allows the NIM's configuration / de-configuration of the selected Hard
PVPC.
- It is not possible to de-configure a hard PVPC NE NIM if cont inuit y check is

Alcatel
activated on it.
PVPC in the list => NE NIM List => select one NE User label in the list =>
Configure
Figure 4-59 Hard PVPC NE NIM Configuration window
In the Origin (A) and / or Destination (Z) area(s), tick (or untick) the Ingress and / or
the Egress check bock(s) if you want to configure (or de-configure) the NIM(s) of
the selected NE User Label chosen in the Hard PVPC NIM List.
Click on Ok.
3AG 86577 ABAA Ed3 325/725

In case of NE NIM configuration:

If the hard PVPC provisioning state is established, implemented or

commissioned, a request is sent to the intermediate VPL_Ts chosen by the
operator to create the required NIM Points (on the given direction). The NIM
Point state becomes On NE.
Alcatel
If the hard PVPC provisioning state is allocated, the NIM Point state becomes On
1354 BM and the NIM Point creation will to be done on the ATM NE at the hard
PVPC implementation (the NIM Point state will become On NE).
Configured NIMs are added in the hard PVPC NIM CC List.
In case of NE NIM de-configuration:
If the hard PVPC provisioning state is implemented or commissioned, a request

is sent to each chosen intermediate VPL_T composing the given hard PVPC and
supporting an NIM Point, to delete them if no OAM service uses those NIMs
Points.
If the hard PVPC is de-implemented, all the NIM Points created when
implemented, are automatically deleted from the ATM NEs. These NIM Points
are only existing on 1354 BM. The NIM Point state becomes On 1354 BM.
3AG 86577 ABAA Ed3 326/725

4.1.29 Display hard PVPC NIM CC list

The hard PVPC CC NIM list presents all the continuity check detection points that
can be activated / de-activated among the surveillance points of the selected hard
PVPC.
Alcatel
- The hard PVPC must be Implemented, the NIM(s) must be configured and the
continuit y check is activated on this hard PVPC.
PVPC in the list => NIM CC List
Figure 4-60 Hard PVPC NIM CC List window
This window is automatically closed when CC is de-activated on the hard PVPC.
The descriptive attributes displayed for each hard PVPC NIM CC are:
− NE User Label
− Term Id.
− Vpi
− Signal Monitoring Direction (Ingress, Egress)
− CC State (Acitvated, Deactivated)
3AG 86577 ABAA Ed3 327/725


− NE User Label
− CC State
Alcatel
Figure 4-61 Hard PVPC NIM CC Search window
From the hard PVPC NIM CC list, you can:
activate NIMs CC, refer to § 4.1.29.1
deactivate NIMs CC, refer to § 4.1.29.2
3AG 86577 ABAA Ed3 328/725

4.1.29.1 Activate NIM CC

This function consists in activating the Continuity Check (CC) on NIM hard PVPC
intermediate points.
- The provisio ning state of the hard PVPC point-to-point must be implemented or
Alcatel
commissio ned.
- The CC state of the hard PVPC must be act ivated (CC activation on end points is
done)
- The CC state of the hard PVPC NIM intermediate points must be de-activated.
PVPC in the list => NIM CC List => select one or several hard PVPC NIMs =>
Activate
Figure 4-62 Confirmation box for activating NIM CC on one hard PVPC
Figure 4-63 Confirmation box for activating NIM CC on several hard PVPCs
After confirmation, a request is sent to the selected NIMs to activate the detection-
process of the Continuity Check.
3AG 86577 ABAA Ed3 329/725

4.1.29.2 Deactivate NIM CC

This function consists in deactivating the NIM Continuity Check on a hard PVPC.
- The CC state of the hard PVPC must be act ivated.

Alcatel
- The CC state of the hard PVPC NIM intermediate points must be activated.
PVPC in the list => NIM CC List => select one or several hard PVPC NIMs =>
Deactivate
Figure 4-64 Confirmation box for deactivating NIM CC on one hard PVPC
Figure 4-65 Confirmation box for deactivating NIM CC on several hard PVPCs
The Continuity Check service is de-activated on the selected NIM CC points.
The CC state of the hard PVPC remains activated.
3AG 86577 ABAA Ed3 330/725

4.1.30 Display the hard PVPC Constraints list

The hard PVPC constraints list presents all the hard PVPCs constraints managed by
the 1354 BM and their descriptive attributes.
Alcatel
PVPC in the list => Constraint
Figure 4-66 Hard PVPC Constraint List window
The descriptive attributes displayed for each hard PVPC constraint are:
− User Label
− Constraint Kind
− VPI

− User Label
3AG 86577 ABAA Ed3 331/725

Alcatel
Figure 4-67 Hard PVPC Constraint Search window
From the hard PVPC Constraint List, you can:
Add a constraint to a hard PVPC, refer to § 4.1.30.1
Delete a constraint from a hard PVPC, refer to § 4.1.30.2
3AG 86577 ABAA Ed3 332/725

4.1.30.1 Add a constraint to a hard PVPC

This function consists in associating one or several allocation constraints to an
existing hard PVPC.
Alcatel
PVPC => Constraint List => Add a constraint
This funct ion is available only wit h no selection in the constraint list. For de-
Figure 4-68 Constraint Definition window
To define a constraint to a hard PVPC:

− Select the Constraint Kind:
− Positive Node: consist in defining a list of NE to be crossed
− Negative Node: consist in defining some NEs that must not be used for the
hard PVPC allocation.
− Positive Link: consist in forcing the use of one or several Transmission
Paths.
− Negative Link: consist in defining some Transmission Paths that must not be
used for hard PVPC allocation.
3AG 86577 ABAA Ed3 333/725

All combinat ions constraint forms are allowed.
− For a Node Constraint:

− Enter the NE User Label by using the sensitive help.
Alcatel
− For a Link Constraint:

− Enter a Transmission Path User Label
− Enter VPI (optional)

− Too many constraints.
− One of the constraint does not correspond to en existing entity.
− One of the constraint is given more than one time in the list.
3AG 86577 ABAA Ed3 334/725

4.1.30.2 Delete a constraint from a hard PVPC

This function consists in deleting constraints from a Hard PVPC.
- The constraint of the hard PVPC must be Created.

Alcatel
PVPC => Constraint List => select one or several constraints in the list => Delete
Figure 4-69 Confirmation box for deleting one Constraint
Figure 4-70 Confirmation box for deleting several Constraints
After confirmation, the Constraints are removed.
The constraints list is updated.
3AG 86577 ABAA Ed3 335/725

4.2 Managing hard PVPC Legs
A point-to-multipoints PVPC is composed of one or more multidirectional Legs.
A Leg is a point-to-point, unidirectional PVPC.

Alcatel
Each Leg starts from the same origin extremity as the point-multipoints PVPC but
ends on a specific destination extremity.
The point-multipoints PVPC is so the aggregation of all Legs composing it.
In order to create a point-multipoints hard PVPC, the operator must define a hard
PVPC choosing the point-multipoints characteristic.
Then, one Leg is automatically defined with extremities and the traffic characteristics
of the hard PVPC defined.
Some other legs of this point-multipoints hard PVPC can then be added by giving
their destination extremity.
Their common origin extremity is inherited from the point-multipoints hard PVPC.
Each Leg is associated to the point-multipoints hard PVPC but is managed
independently.
The operator can do a global operation on the point-multipoints hard PVPC and then
the operation is implicitly done on each Leg composing it or he can do an operation
on a specific Leg.
The hard PVPC Leg management, part of the network management, consists in:
− defining / modifying / deleting hard PVPC Leg
− defining / deleting routing constraints
− setting in / out of service hard PVPC Leg:
− allocation / de-allocation function
− implementation / de-implementation function
− commissioning / de-commissioning function
− displaying hard PVPC Leg information such as:
− hard PVPC Leg list
− routing properties
− graphical view
3AG 86577 ABAA Ed3 336/725

The hard PVPC Leg management chain gives the order in which the available actions
may be performed.
Alcatel
Define Delete
Allocate Modify Co mmission
De-allocate Implement De-co mmission
De-implement
Figure 4-71 Hard PVPC Leg management chain
3AG 86577 ABAA Ed3 337/725

operation performed on the hard PVPC Leg.
Define Commi ssion Commissioned

Alcatel
Implement
Implemented
Allocate De-commission
Allocated
De-implement
Defined
De-allocate De-implement *
Delete
* Allows to de-implement a PVC whose some NEs caused problems during a previous try
Figure 4-72 Hard PVPC Leg provisioning state
For managing hard PVPC Legs, you can:
display the hard PVPC Leg list, refer to § 4.2.1
3AG 86577 ABAA Ed3 338/725

4.2.1 Display the hard PVPC Leg list

The hard PVPC Leg list presents all the hard PVPC Legs managed by the 1354 BM
and their descriptive attributes.
Alcatel
From the Main view, menu: Management => Hard => PVPC => select one point-
to-mult ipo ints hard PVPC => Leg List
Figure 4-73 Hard PVPC Leg List window
The descriptive attributes displayed for each hard PVPC Leg are:
− User Label
− Provis. State
− Activity State

− User Label
3AG 86577 ABAA Ed3 339/725

Alcatel
Figure 4-74 Hard PVPC Leg Search window
3AG 86577 ABAA Ed3 340/725

From the hard PVPC Leg descript ion list, you can:
define a hard PVPC Leg, refer to § 4.2.3

Alcatel
modify a hard PVPC Leg, refer to § 4.2.4
delete a hard PVPC Leg, refer to § 4.2.5
allocate a hard PVPC Leg, refer to § 4.2.6
de-allocate a hard PVPC Leg, refer to § 4.2.7
implement a hard PVPC Leg, refer to § 4.2.8
de-implement a hard PVPC Leg, refer to § 4.2.9
commission a hard PVPC Leg, refer to § 4.2.10
decommission a hard PVPC Leg, refer to § 4.2.11
display the hard PVPC Leg extremities, refer to § 0
display the hard PVPC Leg properties, refer to § 4.2.13
display the hard PVPC Leg routing properties, refer to § 4.2.14
display the Hard PVPC Leg graphical view, refer to § 4.2.15
display the hard PVPC Leg NE NIM list, refer to § 4.2.16
configure the hard PVPC Leg NE NIMs, refer to § 4.2.16.1
display the hard PVPC Leg constraints list, refer to § 4.2.17
add constraint to the hard PVPC Leg, refer to § 4.2.17.1
delete constraint from a hard PVPC Leg, refer to § 4.2.17.2
3AG 86577 ABAA Ed3 341/725

4.2.2 Show the associated Legs

This function consists in displaying Legs associated to a Point-Multipoints Hard
PVPC.
Alcatel
to-mult ipo ints hard PVPC => Show Legs
Figure 4-75 Point-Multipoints Hard PVPC View showing the Legs used by the hard
PVPC
3AG 86577 ABAA Ed3 342/725

4.2.3 Define a hard PVPC Leg

This function consists in identifying the hard PVPC Leg and determining its traffic
profile and the ATM ENEs that support its extremities.
- Transmission Paths at extremit ies o f the Leg must be created and must have their
Alcatel
connection characterist ics defined.
- End VPIs of the Leg must be in VPI range of both Transmission Paths at
extremit ies.
- Transmission Paths at extremit ies must have the same VCI range as the point-
mult ipoints hard PVPC
- VPI at destinat ion extremit y must be idle (not reserved nor busy).
to-mult ipo ints hard PVPC => Leg List => Define
This funct ion is available only wit h no selection in the Leg list. For de-select ion
Figure 4-76 Hard PVPC Leg Definition window
3AG 86577 ABAA Ed3 343/725

To define a hard PVPC Leg:

− Enter a PVPC Leg User Label

Alcatel
− Destination point Z:
− Enter a ENE User Label by using the sensitive help
− Choose a Termination Id. by using the sensitive help
− Select a VPI by using the sensitive help
− Tick the PVPC Prov. State Alignment to align the provisioning state of the Leg
on the PVPC.
− Tick the Shaping Protection Edge to activate the output shaping on the leg to be
created.

− The Leg User Label is not unique for all the point-multipoints hard PVPC.
− At the destination extremity of the Leg, the Transmission Path does not exist
or is not configured.
− At the destination extremity of the Leg, VPI is out of the VPI range of the
Transmission Path.
− At the destination extremity of the Leg, VPI is already used on the
Transmission Path.
− At the destination extremity of the Leg, the Transmission Path has a VCI
range different from the VCI range of the point-multipoints VPC.
3AG 86577 ABAA Ed3 344/725

4.2.4 Modify a hard PVPC Leg

The Hard PVPC Leg modification gives the possibility to modify:
− User Label
− Comment
Alcatel
to-mult ipo ints hard PVPC in the list => Leg List => select one PVPC Leg in the list
=>Modify
This function is available only if a Leg is selected.
Figure 4-77 Hard PVPC Leg Modification window
To modify a Hard PVPC Leg:

− Change the Comment (optional)
The process fails if the New User Label already exists.
3AG 86577 ABAA Ed3 345/725

4.2.5 Delete a hard PVPC Leg

This function consists in deleting a given hard PVPC Leg from a point-multipoints
hard PVPC.
- The provisio ning state of the hard PVPC Leg must be Defined.
Alcatel
During point-mult ipo ints hard PVPC delet ion, this current part is automat ically
invoked for all Legs co mposing it in order to delete the Legs.
From the Main view, menu: Management => Hard => PVPC => select a point-to-
mult ipoints hard PVPC in the list => Leg List => select one or several Legs in the
list => Delete
Figure 4-78 Confirmation box for deleting one hard PVPC Leg
Figure 4-79 Confirmation box for deleting several hard PVPC Legs
After confirmation, the hard PVPC Legs are removed.
The hard PVPC Leg list is updated.
3AG 86577 ABAA Ed3 346/725

4.2.6 Allocate a hard PVPC Leg

bandwidth for a hard PVPC Leg. The available bandwidth has to satisfy the
requirement of the hard PVPC Leg in terms of traffic contract.
Alcatel
- The provisio ning state of the hard PVPC Leg must be Defined.
mult ipoints hard PVPC in the list => Leg List => select one or several hard PVPC
Legs in the list =>Allocate
Figure 4-80 Hard PVPC Leg Allocation
3AG 86577 ABAA Ed3 347/725


Alcatel
Figure 4-81 Confirmation box for allocating several hard PVPC Legs
To allocate a hard PVPC Leg, you must defined some characteristics:

− Choose the allocation mode:
− Automatic: the 1354 BM automatically searches the shortest route binding
the two extremities of the Leg. The broadcast point is automatically found by
the 1354 BM or given by the operator.
− Semi automatic: consists in searching a route according to the constraints
defined on the Leg. The broadcast point is automatically found by the 1354
BM or given by the operator.
− Manual: The route of the Leg is fully given by the operator. It is given from
the broadcast point and till the destination extremity.

- The cost model is accessible only for automat ic and semi-automat ic allocation
mode.
− Define the Broadcast point:
3AG 86577 ABAA Ed3 348/725

− Select the NE User Label by using the sensitive help.

− Choose the Termination Id.

− Choose the VPI.
- For the first Leg allocat ion, the broadcast point is the origin extremit y of the Leg.
Alcatel

− There is not enough bandwidth on destination Transmission Path.
− Destination Transmission Path is locked.
When the process is finished, the provisioning state of the hard PVPC Leg changes to
Allocated.
The point-multipoints hard PVPC provisioning state changes to Allocated if all Legs
are allocated.
3AG 86577 ABAA Ed3 349/725

4.2.7 De-allocate a hard PVPC Leg

This function consists in freeing resources of the selected Leg from the broadcast
point and till the destination extremity.
- The provisio ning state of the hard PVPC Leg must be Allocated.
Alcatel
- The provisio ning state of all the hard PVCCs passing through the hard PVPC Leg
- The hard PVPC Leg must not be associated to a PM Measure.
mult ipoints hard PVPC in the list => Leg List => select one hard PVPC Legs in the
list =>De-Allocate
Figure 4-82 Confirmation box for de-allocating one hard PVPC Leg
Figure 4-83 Confirmation box for de-allocating several hard PVPC Legs
After confirmation, the hard PVPC Legs are de-allocated. Their provisioning states
change to Defined.
The hard PVPC point-multipoints provisioning state changes to Defined if all Legs
are de-allocated.
3AG 86577 ABAA Ed3 350/725

4.2.8 Implement a hard PVPC Leg

This function consists in implementing all the VPLs involved in a hard PVPC Leg.
Thus all the ATM ENEs providing the end-connections and cross-connections along
the hard PVPC Leg route have to satisfy the traffic contract requirements (ATC,
QoS).
Alcatel
- The provisio ning state of the hard PVPC Leg must be Allocated.

Legs in the list => Implement
Figure 4-84 Confirmation box for implementing one hard PVPC Leg
Figure 4-85 Confirmation box for implementing several hard PVPC Legs
After confirmation, the hard PVPC Leg implementation process is launched.
The hard PVPC Leg provisioning state changes from Allocated to Implemented.
The hard PVPC Leg availability status is updated and managed in function of alarms
(according to the 1354 BM configuration).
The hard PVPC point-multipoints provisioning state changes to Implemented if all

Legs are implemented.
3AG 86577 ABAA Ed3 351/725

4.2.9 De-implement a hard PVPC Leg

involved in a hard PVPC Leg and previously performed at ATM NE level.
- The provisio ning state of the hard PVPC Leg must be Implemented or Allocated.
Alcatel

Legs in the list => De-Implement
Figure 4-86 Confirmation box for de-implementing one hard PVPC Leg
Figure 4-87 Confirmation box for de-implementing several hard PVPC Legs
After confirmation, the hard PVPC Leg de-implementation process is launched.
The de-implementation of a hard PVPC Leg works as a hard PVPC de-

implementation (refer to § 4.1.8), but only the connections not still used by other
implemented/commissioned Legs of the point-multipoints hard PVPC are removed
from the ATM ENEs.
The hard PVPC point-multipoints provisioning state changes to Allocated if all Legs
are de-implemented. The hard PVPC Leg list is updated.
3AG 86577 ABAA Ed3 352/725

4.2.10 Commission a hard PVPC Leg

This function consists in setting in service a hard PVPC Leg.
- The provisio ning state of the hard PVPC must be Implemented.

Alcatel
Legs in the list => Commission
Figure 4-88 Confirmation box for commissioning one hard PVPC Leg
Figure 4-89 Confirmation box for commissioning several hard PVPC Legs
After confirmation, the hard PVPC Legs are commissioned.
The hard PVPC point-multipoints provisioning state changes to Commissioned if all

Legs are commissioned.
3AG 86577 ABAA Ed3 353/725

4.2.11 De-commission a hard PVPC Leg

This function consists in setting out of service a hard PVPC Leg.
Alcatel
From the Main view, menu: Management => Hard => PVPC => select a point-
Legs in the list => De-Commission
Figure 4-90 Confirmation box for de-commissioning one hard PVPC Leg
Figure 4-91 Confirmation box for de-commissioning several hard PVPC Legs
After confirmation, the hard PVPC Legs are de-commissioned. Their provisioning
states change to Implemented.
The hard PVPC point-multipoints state can change in other provisioning state
following the provisioning state of its Legs.
3AG 86577 ABAA Ed3 354/725

4.2.12 Display the hard PVPC Leg extremities

This function consists in displaying information about the ATM ENEs that support
the hard PVPC Leg extremities.
Alcatel
mult ipoints hard PVPC in the list => Leg List => select a hard PVPC Leg in the list
=> Extremities
Figure 4-92 Hard PVPC Leg Extremities window
The fields have been filled out at the hard PVPC Leg definition (refer to § 4.2.3)
time.
3AG 86577 ABAA Ed3 355/725

4.2.13 Display the hard PVPC Leg properties

This function consists in displaying information concerning the last action performed
on a hard PVPC Leg.
Alcatel
=> Properties
The first fields have been filled out at the hard PVPC Leg definition (refer to § 4.2.3)
time.
PVPC.
Figure 4-93 Hard PVPC Leg Properties window
3AG 86577 ABAA Ed3 356/725

4.2.14 Display the hard PVPC Leg routing properties

This function consists in displaying the list of the VPLs used by the hard PVPC Leg.
A VPL is defined by a transmission path and a VPI used on it.

Alcatel
- The provisio ning state of the hard PVPC Leg must be Allocated, Implemented or
Commissio ned.
=> Routing
Figure 4-94 Hard PVPC Leg Routing Properties window

− VPI
3AG 86577 ABAA Ed3 357/725

4.2.15 Display the hard PVPC Leg graphical view

This function consists in displaying the graphical view (hard transmission path
domain) corresponding to the sub-network that contains the transmission paths used
by the hard PVPC Leg.
Alcatel
- The provisio ning state of the hard PVPC Leg must be Allocated, Implemented or
Commissio ned.
From the Main view, menu: Management => Hard => PVPC => select a Point-
Mult ipo ints hard PVPC in the list => Leg List => select a Hard PVPC Leg in the list
=> Display Route
Figure 4-95 Sub-network view showing the transmission paths used by the hard PVPC
3AG 86577 ABAA Ed3 358/725


− With a selected entity (NE, transmission path, ENE, Off page connector): Begin
and End commands are completed by other commands depending on the selected
Alcatel
entity.
3AG 86577 ABAA Ed3 359/725

4.2.16 Display the hard PVPC Leg NE NIM list

The hard PVPC Leg NE NIM list presents all the switched VPLs constituting the
selected hard PVPC Leg and allows to configure the NIMs on each intermediate
point of the hard PVPC Leg.
Alcatel
- The hard PVPC Leg must be at least Allo cated.
PVPC point-mult ipoint in the list => Leg List => select one leg in the list => NE
NIM List
Figure 4-96 Hard PVPC Leg NE NIM List window
The descriptive attributes displayed for each hard PVPC Leg NE NIM are:
− NE User Label
− A Term Id.
− A Vpi
− A Ing.
− A Egr.
− Z Term Id.
− Z Vpi
− Z Ing.
− Z Egr.

− NE User Label
3AG 86577 ABAA Ed3 360/725

Alcatel
Figure 4-97 Hard PVPC Leg NE NIM Search window
From the hard PVPC Leg NE NIM list, you can:
configure / de-configure the hard PVPC Leg NE NIMs, refer to § 4.2.16.1
3AG 86577 ABAA Ed3 361/725

4.2.16.1 Configure / de-configure the hard PVPC Leg NE NIMs

PVPC Leg.
PVPC point-mult ipoint in the list => Leg List => select one leg in the list => NE
Alcatel
NIM List => select one NE User label in the list => Configure
Figure 4-98 Hard PVPC Leg NE NIM Configuration window
the selected NE User Label chosen in the Hard PVPC Leg NE NIM List.
Click on Ok.
3AG 86577 ABAA Ed3 362/725


If the hard PVPC Leg provisioning state is established, implemented or

commissioned, a request is sent to the intermediate VPL_Ts chosen by the
Alcatel
If the hard PVPC Leg provisioning state is allocated, the NIM Point state
becomes On 1354 BM and the NIM Point creation will to be done on the ATM
NE at the hard PVPC implementation (the NIM Point state will become On NE).
Configured NIMs are added in the hard PVPC Leg NIM CC List.
If the hard PVPC Leg provisioning state is implemented or commissioned, a

request is sent to each chosen intermediate VPL_T composing the given hard
PVPC and supporting an NIM Point, to delete them if no OAM service uses those
NIMs Points.
If the hard PVPC Leg is de-implemented, all the NIM Points created when
3AG 86577 ABAA Ed3 363/725

4.2.17 Display the hard PVPC Leg Constraints list

The hard PVPC Legs constraints list presents all the hard PVPCs Leg constraint
managed by the 1354 BM and their descriptive attributes.
Alcatel
=> Constraint
Figure 4-99 Hard PVPC Leg Constraints List window
The descriptive attributes displayed for each hard PVPC constraints are:
− User Label
− Constraint Kind
− VPI

− User Label
3AG 86577 ABAA Ed3 364/725

Alcatel
Figure 4-100 Hard PVPC Leg Constraint Search window
From the hard PVPC Constraint List, you can:
Add a constraint to a hard PVPC Leg, refer to § 4.2.17.1
Delete a constraint from a hard PVPC Leg, refer to § 4.2.17.2
3AG 86577 ABAA Ed3 365/725

4.2.17.1 Add a constraint to a hard PVPC Leg

existing hard PVPC Leg.
Alcatel
=> Constraint List => Add a constraint
Figure 4-101 Hard PVPC Leg Constraint Definition window
To define a hard PVPC Leg constraint:

− Negative Node: consists in defining some NE that must not be used for the
− Positive Link: consists in forcing the use of one or several Transmission
Paths.
− Negative Link: consists in defining some Transmission Paths that must not
be used for hard PVPC allocation.
3AG 86577 ABAA Ed3 366/725


− Enter the NE User Label by using the sensitive help
Alcatel


− One of the constraint is given more than one time in the lists.
3AG 86577 ABAA Ed3 367/725

4.2.17.2 Delete a constraint from a hard PVPC Leg

- The constraint of the hard PVPC must be Created.

Alcatel
PVPC in the list => Leg List => select a hard PVPC Leg in the list => Constraint
List => select one or several constraints in the list => Delete
Figure 4-102 Confirmation box for deleting one Constraint from a Hard PVPC Leg
Figure 4-103 Confirmation box for deleting several Constraints from a Hard PVPC Leg
3AG 86577 ABAA Ed3 368/725

4.3 Managing hard PVCCs
The hard PVCC management, part of the network management, consists in:
defining hard PVCCs:
Alcatel
− traffic profile
− extremities
− legs (optional)
modifying hard PVCCs or hard PVCCs Legs user label and / or comment
setting in / out of service hard PVCCs:
managing the use of the hard PVCCs:
− NAD Label assignment function
− UPC / NPC activation / deactivation function
− activating / deactivating the continuity check on hard PVCCs
− modifying their bandwidth by choosing another traffic profile
− NIM and NIM CC configuration function
− displaying hard PVCC information such as:

− hard PVCC list, hard PVCC NIM list, hard PVCC NIM CC list, hard PVCC
Constraints list, hard PVCC Leg list
− extremities and properties
− traffic and routing
− fault localization
− graphical view
The hard PVCC management chain gives the order in which the available actions
may be performed.
3AG 86577 ABAA Ed3 369/725

Delete
Define
Modify
Alcatel
Allocate
De-allocate
Activate / De-
Configure / activate
De-configure UPC/NPC
NIM
Modify
Assign bandwidth
NAD Label
Implement De-implement
Activate/
deactivate CC
Commission De-commission
Figure 4-104 Hard PVCC management chain
3AG 86577 ABAA Ed3 370/725

operation performed on the hard PVCC.

Alcatel
Figure 4-105 Hard PVCC provisioning state
For managing hard PVCCs, you can:
display the hard PVCC list, refer to § 4.3.1
3AG 86577 ABAA Ed3 371/725

4.3.1 Display the hard PVCC list

The hard PVCC list presents all the point-to-point and point-multipoints hard PVCCs
The hard PVCCs used in so ft PVCCs are not listed here.

Alcatel
From the Main view, menu: Management => Hard => PVCC
Figure 4-106 Hard PVCC List window
By default, the list window displays all Hard PVCCs belonging to the Root sub-
network.
sensitive help (or enter * value to have the complete list) and click on Load button.
The descriptive attributes displayed for each hard PVCC are:

− User Label
− Provis State
− Activity State
− Cast Type
− NAD Label

− User Label
3AG 86577 ABAA Ed3 372/725

− NAD Label

Alcatel
Figure 4-107 Hard PVCC Search window
3AG 86577 ABAA Ed3 373/725

From the hard PVCC list, you can:
define a hard PVCC, refer to § 0
modify a hard PVCC, refer to § 4.3.3
delete a hard PVCC, refer to § 4.3.4

Alcatel
allocate a hard PVCC, refer to § 4.3.5
de-allocate a hard PVCC, refer to § 4.3.6
implement a hard PVCC, refer to § 4.3.7
de-implement a hard PVCC, refer to § 4.3.8
commission a hard PVCC, refer to § 4.3.9
de-commission a hard PVCC, refer to § 4.3.10
assign NAD Label to a Hard PVCC, refer to § 4.3.11
activate UPC / NPC on a hard PVCC, refer to § 4.3.12
deactivate UPC / NPC on a hard PVCC, refer to § 4.3.13
activate CC on a hard PVCC, refer to § 4.3.14
deactivate CC on a hard PVCC, refer to § 4.3.15
modify the bandwidth of a hard PVCC, refer to § 4.3.16
display the hard PVCC extremities, refer to § 4.3.17
display the hard PVCC properties, refer to § 4.3.18
display the hard PVCC traffic properties, refer to § 4.3.19
display the hard PVCC routing properties, refer to § 4.3.20
display the hard PVCC graphical view, refer to § 4.3.21
display the fault localization on hard PVCC, refer to § 4.3.22
display the hard PVCC NE NIM List, refer to § 4.3.23
configure the hard PVCC NE NIMs, refer to § 4.3.23.1
display the hard PVCC NIM CC List, refer to § 4.3.24
display the hard PVCC constraint List, refer to § 4.3.25
add constraint to the hard PVCC, refer to § 4.3.25.1
3AG 86577 ABAA Ed3 374/725

delete constraint from the hard PVCC, refer to § 4.3.25.2

if the Hard PVCC selected is a Point-Multipoints Hard PVCC:
display the hard PVCC Leg List, refer to § 4.4.1

Alcatel
3AG 86577 ABAA Ed3 375/725

4.3.2 Define a hard PVCC

This function consists in identifying the hard PVCC and determining its traffic
profile and the NEs (and/or ENEs) that support its extremities.
- The NEs (and/or ENEs) supporting the extremit ies of the hard PVCC must be
Alcatel
previously defined.
- Both hard PVPCs supporting the extremit ies of the hard PVCC must exist and be
configured.
- The maximum number of PVCCs must not be reached.
From the Main view, menu: Management => Hard => PVCC => no hard PVCC
selected in the list => Define Hard PVCC
3AG 86577 ABAA Ed3 376/725

Alcatel
3AG 86577 ABAA Ed3

Figure 4-108 Hard PVCC Definition window
377/725
To define a hard PVCC:


− Choose a Target:
− Defined: this state show only the definition of the hard VPCC.
Alcatel
− Allocated: in this state, the 1354 BM automatically retrieves the hard PVCC
characteristics and searches Transmission Paths and hard PVPCs among
those verify conditions.
− Implemented: this state consists in directly doing the establishment of all
involved VCL and the establishment of the required cross-connections and
end-connexions.
− Enter the Utilization Factor
It can have a value from 1% to 100% (default value = 100%).
concerned hard PVCC. For the hard PVPC (which contains the hard PVCC
with utilization factor modified), it permits to create more hard PVCCs.
divided by 2.
- Utilization factor must be set to 100% for hard PVCC DBR Class 1.
− Tick the Point-to-Multipoint check box if you want to define a Point-to-

Multipoint hard PVCC.
If the hard PVCC cast type is point-mult ipo ints:

− A PVCC Leg is automatically defined associated to the point-multipoints
hard PVCC.
− The state of the Leg will be the same as the hard PVCC (defined, allocated,
or implemented).
If you tick the Point-to-Multipoints check box:

− an unidirectional Traffic Profile must be previously defined (refer to §
6.2.2.).
− extremities must be ENEs.
3AG 86577 ABAA Ed3 378/725


Properties. The window becomes as below.
Alcatel
Figure 4-109 Hard PVCC Definition window (extended view)
− In the Origin (A) and Destination (Z) areas, enter the identification parameters of
the NEs and/or ENEs that support the hard PVCC extremities:
− Choose the NE User Label by using the sensitive help.
− Choose the Termination Id. by using the sensitive help.
3AG 86577 ABAA Ed3 379/725

− Enter a VPI number by using the sensitive help:

− The VPI field displays the first ten values which is associated to PVPC
whose provisioning state is at least defined.
− The VPI field is empty if there are no idle VPIs on the PVPC.
− Enter a VCI number by using the sensitive help:

Alcatel
− The VCI field displays the first ten values which do not belong to any
PVCCs (even for defined PVCCs).
− The VCI field is empty if there are no idle VCIs on the PVPC.
− Click on Ok.
The traffic contracts of hard PVCCs which are authorized are:

− DBR Class 1, DBR Class 2 cell based
− DBR Class U (UBR.1) cell based or frame based
− DBR Class U (UBR.2) cell based or frame based
− UBR+ frame based
− GFR.2 frame based
− SBR.1 Class 1, SBR.1 Class 2, SBR.2 Class 3, SBR.3 Class 3 cell based
(authorized only for Hard PVCC between two ENEs)
Also, the traffic contracts of hard VPCs and hard VCCs have to be compat ible:
Hard PVPCs Supported Hard PVCCs

DBR class 1 cross-connected DBR class 1, DBR class 2, SBR.1 class 1
DBR class 2 cross-connected or not DBR class 2, SBR.1 class 2
DBR class 1 shaped (grooming) or DBR class 1 no Any kind of hard PVCC
cross-connected
DBR class U (UBR.1) cross-connected DBR class U (UBR.1 and UBR2 cell based)
DBR class U (UBR.2) cross-connected DBR class U (UBR.2 cell based)
DBR class U (UBR.1) no cross-connected DBR class U (UBR.1 and UBR.2 cell or frame based)
DBR class U (UBR.2) no cross-connected DBR class U (UBR.2 cell or frame based)
UBR+ (= DBR class U (UBR.2) with MDCR >0) UBR + (frame based)
cross-connected or not (cell based)
SBR.1 class 1, SBR.1 class 2, SBR.2 class 3, SBR.3 SBR.1 class 1, SBR.1 class 2, SBR.2 class 3, SBR.3 class 3
class 3 cross-connected
Flexible unitary hard PVPC Any kind of hard PVCC
• cross-connected means : PVPC made of two VPLs or more

• no cross-connected means : PVPC made of one VPL
3AG 86577 ABAA Ed3 380/725

The hard PVCC is defined into the 1354 BM with the following states:
− provisioning state : Defined

− consistency state : Consistent
− activity state : None
Alcatel
− UPC/NPC state :
− Disabled if the interface type of the hard PVPC is NNI
− Enabled if the interface type of the hard PVPC is ICI or UNI
The hard PVCC list is updated.
The usage state of each hard PVPC (extremities only) used by the hard PVCC
changes to Busy (if it was not yet).
3AG 86577 ABAA Ed3 381/725

4.3.3 Modify a hard PVCC

The Hard PVCC modification gives the possibility to modify:
− User Label
− Comment
Alcatel
− Utilization Factor
From the Main view, menu: Management => Hard => PVCC => select one hard
PVCC in the list => Modify
Figure 4-110 Hard PVCC Modification window
To modify a Hard PVCC:

− Change the comment (optional)
− Change the Utilization Factor. It can have a value from 1% to 100%.
concerned hard PVCC. For the hard PVPC (which contains the hard PVCC
with utilization factor modified), it permits to create more hard PVCCs.
divided by 2.
Utilization factor must be set to 100% for hard PVCC DBR Class 1.
The effective bandwidth of the hard PVCC is re-computed according to the new
value of utilization factor.
3AG 86577 ABAA Ed3 382/725

If the hard PVCC is allocated, the bandwidth consumption on the associated hard
PVPC is re-computed. If the hard PVCC is implemented, the new utilization

factor is downloaded to the NE.
Then, the hard PVCC list, the tree area and the opened graphical views are updated.
Alcatel

− The New User Label is already used by another hard PVCC.
− The hard PVCC activity state is Implementation in progess or
Deimplementation in progress.
− If the Utilization Factor is different of 100% and the traffic contract of the
hard PVCC is DBR Class 1.
3AG 86577 ABAA Ed3 383/725

4.3.4 Delete a hard PVCC

This function consists in deleting a hard PVCC from the 1354 BM supervision.
- The provisio ning state of the hard PVCC must be Defined.

Alcatel
- If the PVCC is point-mult ipo ints, all Legs belo nging to the PVCC are deleted.
From the Main view, menu: Management => Hard => PVCC => select one or
several hard PVCCs in the list => Delete
Figure 4-111 Confirmation box for deleting one hard PVCC
Figure 4-112 Confirmation box for deleting several hard PVCCs
After confirmation, the hard PVCCs are removed.
The usage state of each hard PVPC (extremities only) used by the hard PVCC
changes to Idle (if it was not yet).
3AG 86577 ABAA Ed3 384/725

4.3.5 Allocate a hard PVCC

bandwidth for a hard PVCC. The available bandwidth has to satisfy the requirement
of the hard PVCC in terms of traffic contract.
Alcatel
- The provisio ning state of the hard PVCC must be Defined.
- The maximum number of PVCCs in each transmission path must not be reached.
several hard PVCCs in the list => Allocate
Figure 4-113 Hard PVCC Allocation
Figure 4-114 Confirmation box for allocating several hard PVCCs
3AG 86577 ABAA Ed3 385/725

To allocate a hard PVCC, you must defined some characteristics:

− Choose the allocation mode

− Automatic (with no constraint): consists in searching available bandwidth
on each segment of connection, in each direction, according to the traffic
descriptors of the hard PVCC.
Alcatel
In the figure below, the allocator find a route from A to Z using whatever the
available resources.
Figure 4-115 Automatic routing mode with no constraint
− Semi automatic (wih constraints): consists in associating the hard PVCC

with a list of hard PVPC or NEs with the indication “To be used” or “To be
excluded”. This list will be taken account during the search of the route in the
aim to find a route according to these constraints (Display the constraints list,
refer to §4.3.25).
Figure 4-116 Semi-automatic routing mode with constraints
3AG 86577 ABAA Ed3 386/725

− Manual (all the route is specified by the operator): the complete list of
hard PVPC must be previously given as a list of contiguous positive link

constraints (list of hard PVPC optionally associated with the VCI that must
be used). (See Display the constraints list, refer to §4.3.25).A check is done
to verify the route continuity.
Alcatel
Figure 4-117 Manual routing mode with constraints

of transmission paths used in hard PVCC.
The cost model is accessible only for automat ic and semi automatic mode.

− There is not enough bandwidth on origin or destination Hard VPC.
− The origin or the destination of the Hard PVC is locked.
− The route is not found.
When the process is finished, the provisioning state of the hard PVCC(s) changes to
Allocated.
The Usage State of each transmission path used by the hard PVCC changes to Busy
(if it was not yet).
The bandwidth load of each transmission path used by the hard PVCC is updated for
3AG 86577 ABAA Ed3 387/725

The hard PVCC list is updated. The transmission path lists and the transmission path
bandwidth load windows are updated too.
For a point-multipoints PVCC, all Legs in defined provisioning state belonging to the
PVCC are allocated.
Alcatel
3AG 86577 ABAA Ed3 388/725

4.3.6 De-allocate a hard PVCC

This function consists in releasing all the resources involved in a hard PVCC.
- The provisio ning state of the hard PVCC must be Allocated.

Alcatel
- The hard PVCC must not be associated to a PM Measure.
several hard PVCCs in the list => De-allocate
Figure 4-118 Confirmation box for de-allocating one hard PVCC
Figure 4-119 Confirmation box for de-allocating several hard PVCCs
After confirmation, the hard PVCCs are de-allocated. Their provisioning states
change to Defined. For a point-multipoints hard PVCC, all Legs belonging to it are
de-allocated.
The usage state of each hard PVPC (except the extremities) used by the hard PVCC
is changed to Idle if not any other hard PVCCs are carried.
The bandwidth load of each hard PVPC used by the hard PVCC is updated for both
directions (forward and backward).
The hard PVPC list and the hard PVPC bandwidth load windows are updated too.
3AG 86577 ABAA Ed3 389/725

4.3.7 Implement a hard PVCC

This function consists in implementing all the VCLs involved in a hard PVCC (refer
to § 4.3.20). Thus all the ATM NEs providing the end-connections and cross-
connections along the hard PVCC route have to satisfy the traffic contract
Alcatel
- The provisio ning state of the hard PVCC must be Allocated.
- The consistency state of the hard PVCC must be Consistent.
- The provisio ning state of those hard PVPCs must be Implemented or

Commissio ned.

several hard PVCCs in the list => Implement
Figure 4-120 Confirmation box for implementing one hard PVCC
Figure 4-121 Confirmation box for implementing several hard PVCCs
After confirmation, the hard PVCC implementation process is launched.
Only the PVPCs involved in the hard PVCC and whose administrative state is
Unlocked will be taken into account.
3AG 86577 ABAA Ed3 390/725

cross-connections and end-connections are de-implemented.
A message is displayed asking the operator to cancel the implementation or to

authorize the search for another route. This process can be repeated N times. (Not
available in release R7)
Alcatel
If the hard PVCC is point-multipoints then all Legs belonging it are implemented.
If all the concerned ATM NEs accept the requirements of the new hard PVCC, the
implementation is successful. The hard PVCC provisioning state changes to
Implemented.
The hard PVPC bandwidth load windows are updated too.
The availability status are updated and managed in function of the alarms.
3AG 86577 ABAA Ed3 391/725

4.3.8 De-implement a hard PVCC

involved in a hard PVCC and previously performed at ATM NE level.
- The provisio ning state of the hard PVCC must be Implemented or Allocated.
Alcatel

several hard PVCCs in the list => De-implement
Figure 4-122 Confirmation box for de-implementing one hard PVCC
Figure 4-123 Confirmation box for de-implementing several hard PVCCs
After confirmation, the hard PVCC de-implementation process is launched.
1354 BM keeps de-implementing the other connections.
But the hard PVCC provisioning state changes to Allocated and the availability
status change to None (not significant)
3AG 86577 ABAA Ed3 392/725

successful. The hard PVCC provisioning state changes to Allocated and the
availability status change to None (not significant).
Alcatel
If the hard PVCC is point-multipoints then all Legs belonging it are de-implemented.
3AG 86577 ABAA Ed3 393/725

4.3.9 Commission a hard PVCC

This function consists in setting in service a hard PVCC.
- The provisio ning state of the hard PVCC must be Implemented.

Alcatel
- The provisio ning state of the hard PVPCs involved in the hard PVCC must be
Implemented or Commissio ned.
several hard PVCCs in the list => Commission
Figure 4-124 Confirmation box for commissioning one hard PVCC
Figure 4-125 Confirmation box for commissioning several hard PVCCs
After confirmation, the hard PVCCs are commissioned. Their provisioning states
change to Commissioned.
If the hard PVCC is point-multipoints then all Legs belonging it are commissioned.
The hard PVCC list is updated. The hard PVPC bandwidth load windows are
updated too.
3AG 86577 ABAA Ed3 394/725

4.3.10 De-commission a hard PVCC

This function consists in setting out of service a hard PVCC.
- The provisio ning state of the hard PVCC must be Commissio ned.
Alcatel
several hard PVCCs in the list => De-commission
Figure 4-126 Confirmation box for de-commissioning one hard PVCC
Figure 4-127 Confirmation box for de-commissioning several hard PVCCs
After confirmation, the hard PVCCs are de-commissioned. Their provisioning states
change to Implemented.
3AG 86577 ABAA Ed3 395/725

4.3.11 Assign NAD Label to a hard PVCC

This function consists in assigning a NAD Label to a hard PVCC.
Alcatel
several hard PVCCs in the list => Assign NAD Label
Figure 4-128 NAD Label assignment window for one hard PVCC
Figure 4-129 NAD Label assignment window for several hard PVCCs
To assign a NAD Label to the selected hard PVCC:

− Choose the NAD Label by using the sensitive help (a list of availaible initiators is
proposed)
− Click on Ok.
The selected hard PVCC is updated with the selected NAD label and the Hard PVCC
List window is updated.
3AG 86577 ABAA Ed3 396/725

4.3.12 Activate UPC / NPC on a hard PVCC

This function consists in activating an ATM police control on a hard PVCC that
- The provisio ning state of the hard PVCC must be Defined , Allo cated or Partially
Alcatel
Allocated.
- The UPC/NPC state of the hard PVCC must be Disabled.
- At least one hard PVPC used at the extremit y of the hard PVCC must have an ICI
or UNI interface t ype.
several hard PVCCs in the list => Act. UPC
Figure 4-130 Confirmation box for activating UPC / NPC on one hard PVCC
Figure 4-131 Confirmation box for activating UPC / NPC on several hard PVCCs
After confirmation, the UPC / NPC state of each hard PVCC changes to Enabled.
At next implementation of the hard PVCC, the UPC / NPC activation request will be
sent to the first NE (linked to the ENE) in the border of the network. The hard PVCC
list is updated.
The hard PVCC properties list is updated.
3AG 86577 ABAA Ed3 397/725

4.3.13 Deactivate UPC / NPC on a hard PVCC

This function consists in deactivating the ATM police control on a hard PVCC.
- The UPC / NPC state of the hard PVCC must be Enabled.

Alcatel
several hard PVCCs in the list => Deact. UPC
Figure 4-132 Confirmation box for deactivating UPC / NPC on one hard PVCC
Figure 4-133 Confirmation box for deactivating UPC / NPC on several hard PVCCs
After confirmation, the UPC / NPC states of the hard PVCCs change to Disabled.
The hard PVPC properties list is updated.
3AG 86577 ABAA Ed3 398/725

4.3.14 Activate CC on a hard PVCC

This function consists in activating the Continuity Check (CC) for one or both
direction of a hard PVCC point-to-point in its extremities.
- The provisio ning state of the hard PVCC point-to-point must be Implemented or
Alcatel
Commissio ned.
- The CC state of the hard PVCC must be Deact ivated or Partially Act ivated.
several hard PVCCs in the list => Activate CC
Figure 4-134 Confirmation box for activating CC on one hard PVCC
Figure 4-135 Confirmation box for activating CC on several hard PVCCs
To activate the Continuity Check service on the selected Hard PVCC:

− Choose the OAM CC Direction (A->Z, Z->A, both) compatible with the
direction of the selected Hard PVCC.
3AG 86577 ABAA Ed3 399/725

After confirmation, activation requests are sent to each extremity following the
procedure below:
In A to Z direction if the selected direction is A->Z:
. Activate CC request is sent to A endpoint (if the point is an ATM NE)
to activate the insertion process of the Continuity Check.
Alcatel

In Z to A direction if the selected direction is Z->A:
activate the insertion-process of the Continuity Check.
. Activate CC request is sent to A endpoint (if the point is an ATM NE)
to activate the detection process of the Continuity Check.
In both ways if the hard PVPC is bidirectional:
Then, the Continuity Check is activated on the hard PVCC(s) extremities and the CC
state of each hard PVCC changes to Activated.
If detection process failed (ex : if the NE is not available or if its LAC state is equal
to Granted), the CC state is set to Partially Activated. The operator has the
possibility to re-launch the activate CC command in order to complete the CC
activation (detection process part).
3AG 86577 ABAA Ed3 400/725

4.3.15 Deactivate CC on a hard PVCC

This function consists in deactivating the Continuity Check on a hard PVCC.
- The CC state of the hard PVCC must be Act ivated or Partially Act ivated.
Alcatel
several hard PVCCs in the list => Deact. CC
Figure 4-136 Confirmation box for deactivating CC on one hard PVCC
Figure 4-137 Confirmation box for deactivating CC on several hard PVCCs
The system retrieves the extremities and all NIM points of the hard PVCC where the
Continuity Check on detection is activated (NIM called NIM CC).
3AG 86577 ABAA Ed3 401/725

The deactivation requests are sent to each extremity following the below procedure:
In A to Z direction:
. Deactivate CC request is sent to all NIM CC points and after to the Z
. Deactivate CC request is sent to A endpoint (if the point is an ATM NE)
Alcatel

In Z to A direction:
. Deactivate CC request is sent to all NIM CC points and after to the A
. Deactivate CC request is sent to Z endpoint (if the point is an ATM NE)
In the both way:
Then, the Continuity Check is de-activated on all NIM CC points and on all the
surveillance points of the hard PVCC and its CC state changes to Deactivated.
3AG 86577 ABAA Ed3 402/725

4.3.16 Modify the bandwidth of a hard PVCC

This function consists in modifying the traffic profile of a point-to-point hard PVCC.
The modification is limited to the PCR and the MCR and implies a traffic
perturbation.
Alcatel
- The provisio ning state of the hard PVCC must not be in the Co mmissioned state.
- The hard PVCC must be point-to-point and between two ENEs.
- The hard PVPC(s) carrying the hard PVCC must not be locked.
- At least, another compat ible traffic profile must be available (with same traffic
type and same direct ion as the current profile). If not, the error message 'No
available traffic profile' is displayed.
- A lock of concurrent sessio ns will be done just before starting the bandwidth
modificat ion treatment (= on click on Ok button).
PVCCs in the list => Modify BW
This funct ion is available only if a hard PVCC is selected.
Figure 4-138 Hard PVCC Bandwidth Modification window
3AG 86577 ABAA Ed3 403/725

To modify the bandwidth of a hard PVCC:

− Select a New Traffic in the New Profile area. New traffics suggested have the
same traffic type and same direction as the current profile.
Alcatel
Properties. The window becomes as below:
Figure 4-139 Hard PVCC Bandwidth Modification window (extended view)
3AG 86577 ABAA Ed3 404/725

The 1354 BM locks the others opened sessions and checks:

− if all the NEs on the hard PVCC route are reachable,

− if, in case of bandwidth increase, there is enough available bandwidh on the hard
PVPCs that compose the hard PVCC route.
Alcatel
After that, the 1354 BM:

− de-implements the hard PVCC,
− assigns the new traffic profile to the hard PVCC,
− re-implements the hard PVCC with its new traffic profile (if needed, the traffic
descriptor is created on the NEs).

− One (or more) NE(s) on the hard PVCC route is (are) unreachable.
− Not enough available bandwidth on the hard PVPCs that compose the hard
PVCC route.
3AG 86577 ABAA Ed3 405/725

4.3.17 Display the hard PVCC extremities

that support the hard PVCC extremities.
From the Main view, menu: Management => Hard => PVCC => select a hard
Alcatel
PVCC in the list => Extremities
Figure 4-140 Point-to-Point Hard PVCC Extremities window
3AG 86577 ABAA Ed3 406/725


Alcatel
Figure 4-141 Point-Multipoints Hard PVCC Extremities window
The fields have been filled out at the hard PVCC definition (refer to § 0) time.
3AG 86577 ABAA Ed3 407/725

4.3.18 Display the hard PVCC properties

This function consists in displaying information about the last action performed on a
hard PVCC.
Alcatel
PVCC in the list => Properties
Figure 4-142 Hard PVCC Properties window
The first fields have been filled out at the hard PVCC definition (refer to § 0) time.
PVCC.
3AG 86577 ABAA Ed3 408/725

4.3.19 Display the hard PVCC traffic properties

by a hard PVCC.
Alcatel
PVPC in the list => Traffic
Figure 4-143 Point-to-Point Hard PVCC Traffic Properties window
Figure 4-144 Point-Multipoints Hard PVCC Traffic Properties window
traffic contract.
3AG 86577 ABAA Ed3 409/725

4.3.20 Display the hard PVCC routing properties

This function consists in displaying the list of the VCLs used by the hard PVCC.
A VCL is defined by a hard PVPC and a VCI used on it.

Alcatel
- The provisio ning state of the hard PVCC must be Allocated, Implemented or
Commissio ned.
PVCC in the list => Routing
Figure 4-145 Hard PVCC Routing Properties window

− PVPC User Label
− VCI
− Forward Total Bandwidth (in cells/s)
− Backward Total Bandwidth (in cells/s)
− Under PM (if the transmission path is under PM or not)
3AG 86577 ABAA Ed3 410/725

4.3.21 Display the hard PVCC graphical view

This function consists in displaying the graphical view (VP domain) corresponding
to the sub-network that contains the VPCs used by the hard PVCC.
Alcatel
The provisio ning state of the hard PVCC must be Allocated, Implemented or
Commissio ned.
PVCC in the list => Display Route
Figure 4-146 Sub-network View showing the VPCs used by the hard PVCC
3AG 86577 ABAA Ed3 411/725

− With no selection: Begin and End commands allow to highlight the NE used
for the beginning or the end of the route
− With a selected entity (NE, VPC, ENE, Off page connector): Begin and End
commands are completed by other commands depending on the selected
entity.
Alcatel
3AG 86577 ABAA Ed3 412/725

4.3.22 Display the fault localization on a hard PVCC

alarms for a hard PVCC.
- The availabilit y status of the hard PVCC must be eit her Degraded or In failure.
Alcatel
PVCC in the list => Fault Localization List
Figure 4-147 Fault Localization List (Hard PVCC)

− NE User Label
− Operator Label (user label + ATM port)
− Alarm Status
− Date of the alarm reception
− Probable Cause
3AG 86577 ABAA Ed3 413/725

The 1354 BM will display up to 100 alarms. When the number of alarms is superior
to 100, the fo llowing confirmat ion box is displaye d:
Alcatel
The data displayed are never refreshed in real t ime. A Actualize button is available.
3AG 86577 ABAA Ed3 414/725

4.3.23 Display hard PVCC NE NIM list

The hard PVCC NE NIM list presents all the switched VCLs constituting the
selected hard PVCC and allows to configure the NIMs on each intermediate point of
the hard PVCC.
Alcatel
- The hard PVCC must be point-to-point and at least Allo cated.
PVCC in the list => NE NIM List
Figure 4-149 Hard PVCC NE NIM List window
The descriptive attributes displayed for each hard PVCC NE NIM are:
− NE User Label
− A Term Id.
− A Vpi
− A Ing.
− A Egr.
− Z Term Id.
− Z Vpi
− Z Ing.
− Z Egr.
3AG 86577 ABAA Ed3 415/725


− NE User Label
Alcatel
Figure 4-150 Hard PVCC NE NIM Search window
From the hard PVCC NE NIM list, you can:
configure / de-configure the hard PVCC NE NIMs, refer to § 4.3.23.1
3AG 86577 ABAA Ed3 416/725

4.3.23.1 Configure / de-configure the hard PVCC NE NIMs

PVCC.
- It is not possible to de-configure a hard PVPC NE NIM if cont inuit y check is

Alcatel
activated on it.
PVCC in the list => NE NIM List => select one NE User label in the list =>
Configure
Figure 4-151 Hard PVCC NE NIM Configuration window
3AG 86577 ABAA Ed3 417/725

the selected NE User Label chosen in the Hard PVPC NIM List.
Click on Ok.

Alcatel
If the hard PVCC provisioning state is established, implemented or

commissioned, a request is sent to the intermediate VCL_Ts chosen by the
If the hard PVCC provisioning state is allocated, the NIM Point state becomes
On 1354 BM and the NIM Point creation will to be done on the ATM NE at the
hard PVPC implementation (the NIM Point state will become On NE).
Configured NIMs are added in the hard PVCC NIM CC List.
If the hard PVCC provisioning state is implemented or commissioned, a request

is sent to each chosen intermediate VCL_T composing the given hard PVCC and
supporting an NIM Point, to delete them if no OAM service uses those NIMs
Points.
If the hard PVCC is de-implemented, all the NIM Points created when
3AG 86577 ABAA Ed3 418/725

4.3.24 Display hard PVCC NIM CC list

The hard PVCC CC NIM list presents all the continuity check detection points that
can be activated / de-activated among the surveillance points of the selected hard
PVCC.
Alcatel
- The hard PVCC must be Implemented, the NIM(s) must be configured and the
continuit y check is activated on this hard PVCC.
PVCC in the list => NIM CC List
Figure 4-152 Hard PVCC NIM CC List window
This window is automatically closed when CC is de-activated on the hard PVCC.
The descriptive attributes displayed for each hard PVCC NIM CC are:
− NE User Label
− Term Id.
− Vpi
− Signal Monitoring Direction (Ingress, Egress)
− CC State (Activated, Deactivated)

− NE User Label
− CC State
3AG 86577 ABAA Ed3 419/725

Alcatel
Figure 4-153 Hard PVCC NIM CC Search window
From the hard PVCC NIM CC list, you can:
activate NIMs CC, refer to § 4.3.24.1
deactivate NIMs CC, refer to § 4.3.24.2
3AG 86577 ABAA Ed3 420/725

4.3.24.1 Activate NIM CC

This function consists in activating the Continuity Check (CC) on NIM hard PVCC
intermediate points.
- The provisio ning state of the hard PVCC point-to-point must be implemented or
Alcatel
commissio ned.
- The CC state of the hard PVCC must be activated (CC activat ion on end po ints is
done).
- The CC state of the hard PVCC NIM intermediate points must be de-activated.
PVCC in the list => NIM CC List => select one or several hard PVCC NIMs =>
Activate
Figure 4-154 Confirmation box for activating NIM CC on one hard PVCC
Figure 4-155 Confirmation box for activating NIM CC on several hard PVCCs
After confirmation, a request is sent to the selected NIMs to activate the detection-
process of the Continuity Check.
3AG 86577 ABAA Ed3 421/725

4.3.24.2 Deactivate NIM CC
This function consists in deactivating the NIM Continuity Check on a hard PVCC.
- The CC state of the hard PVCC must be activated.

Alcatel
- The CC state of the hard PVCC NIM intermediate points must be activated.
PVCC in the list => NIM CC List => select one or several hard PVCC NIMs =>
Deactivate
Figure 4-156 Confirmation box for deactivating NIM CC on one hard PVCC
Figure 4-157 Confirmation box for deactivating NIM CC on several hard PVCCs
The Continuity Check service is de-activated on the selected NIM CC points.
The CC state of the hard PVCC remains activated.
3AG 86577 ABAA Ed3 422/725

4.3.25 Display hard PVCC Constraints list

The hard PVCC Constraints list presents all the constraints managed by the 1354 BM
for the hard PVCC allocation.
Alcatel
PVCC in the list => Constraint
Figure 4-158 Hard PVCC Constraints List window
The descriptive attributes displayed for each hard PVCC constraints are:
− User Label
− Constraint Kind
− Termination Id.

− User Label
3AG 86577 ABAA Ed3 423/725

Alcatel
Figure 4-159 Hard PVCC Constraint Search window
From the hard PVCC Constraint List, you can:
Add a constraint to a hard PVCC, refer to § 4.3.25.1
Delete a constraint from a hard PVCC, refer to § 4.3.25.2
3AG 86577 ABAA Ed3 424/725

4.3.25.1 Add a constraint to a hard PVCC

existing hard PVCC.
Alcatel
PVCC => Constraint List => Add a constraint
Figure 4-160 Constraint Definition window
To define a hard PVCC constraint:

− Positive Node: consist in definig a list of NE to be crossed
− Negative Node: consists in defining some NE that would not be used for the
hard PVCC allocation.
Paths.
− Negative Link: consists in defining some Transmission Paths that would not
be used for hard PVCC allocation.
3AG 86577 ABAA Ed3 425/725


Alcatel
− Enter a Hard PVPC User Label

− Enter VCI (optional)

3AG 86577 ABAA Ed3 426/725

4.3.25.2 Delete a constraint from a hard PVCC

This function consists in deleting constraints from a Hard PVCC.
- The constraint of the hard PVCC must be Defined.

Alcatel
PVCC => Constraint List => select one or several constraints in the list => Delete
Figure 4-161 Confirmation box for deleting one Constraint
Figure 4-162 Confirmation box for deleting several Constraints
3AG 86577 ABAA Ed3 427/725

4.4 Managing hard PVCC Legs
The hard PVCC Leg management, part of the network management, consists in:
defining hard PVCC Leg:
Alcatel
− traffic profile
− extremities
setting in / out of service hard PVCC Leg:
− displaying hard PVCC Leg information such as:

− hard PVCC Leg list
− graphical view
The hard PVCC Leg management chain gives the order in which the available
actions may be performed.
3AG 86577 ABAA Ed3 428/725

Define Delete
Alcatel
Allocate De-allocate
Modify
Implement
De-implement
Commission
De-commission
Figure 4-163 Hard PVCC Leg management chain
3AG 86577 ABAA Ed3 429/725

operation performed on the hard PVCC Leg.

Alcatel
Figure 4-164 Hard PVCC Leg provisioning state
For managing hard PVCC Legs, you can:
display the hard PVCC Leg list, refer to § 4.4.1
3AG 86577 ABAA Ed3 430/725

4.4.1 Display the hard PVCC Leg list

The hard PVCC Leg list presents all the hard PVCC Legs managed by the 1354 BM
Alcatel
The hard PVCC Legs used in so ft PVCC Legs are not listed here.
PVCC => Leg List
Figure 4-165 Hard PVCC Leg List window
The descriptive attributes displayed for each hard PVCC Leg are:
− User Label
− Provis. State
− Activity State

− User Label
− Provisioning State
3AG 86577 ABAA Ed3 431/725

Alcatel
Figure 4-166 Hard PVCC Leg Search window
3AG 86577 ABAA Ed3 432/725

From the hard PVCC Leg list, you can:
show associated Legs, refer to § 4.4.2
define a hard PVCC Leg, refer to § 4.4.3

Alcatel
modify a hard PVCC Leg, refer to § 4.4.4
delete a hard PVCC Leg, refer to § 4.4.5
allocate a hard PVCC Leg, refer to § 4.4.6
de-allocate a hard PVCC Leg, refer to § 4.4.7
implement a hard PVCC Leg, refer to § 4.4.8
de-implement a hard PVCC Leg, refer to § 4.4.9
commission a hard PVCC Leg, refer to § 4.4.10
de-commission a hard PVCC Leg, refer to § 4.4.11
display the hard PVCC Leg extremities, refer to § 4.4.12
display the hard PVCC Leg properties, refer to § 4.4.13
display the hard PVCC Leg routing properties, refer to § 4.4.14
display the Hard PVCC Leg graphical view, refer to § 4.4.15
display the hard PVCC Leg NE NIM list, refer to § 4.4.16
configure the hard PVCC Leg NE NIMs, refer to § 4.4.16.1
display the hard PVCC Leg constraint list, refer to § 4.4.17
add constraint to a hard PVCC Leg, refer to § 4.4.17.1
delete constraint from a hard PVCC Leg, refer to § 4.4.17.2
3AG 86577 ABAA Ed3 433/725

4.4.2 Show associated Legs

This function consists in displaying Legs associated to a Point-Multipoints Hard
PVCC.
Alcatel
From the Main view, menu: Management => Hard => PVCC => select one point-
to-mult ipo ints hard PVCC => Show Legs
Figure 4-167 Point-Multipoints Hard PVCC View showing the Legs used by the hard
PVCC
3AG 86577 ABAA Ed3 434/725

4.4.3 Define a hard PVCC Leg

This function consists in identifying the hard PVCC Leg and determining its traffic
profile and the ATM ENEs that support its extremities.
The point-mult ipo ints VCC must be at least defined.

Alcatel
Hard PVPC at extremit ies of the Leg must be defined.
End VCIs of the Leg must be in VCI range o f both Hard VPCs at extremit ies.
VCI at destinat ion extremit y must be idle (not reserved nor used).
From the Main view, menu: Management => Hard => PVCC => select a point-
mult ipoints hard PVCC in the list => Leg List => Define
Figure 4-168 Hard PVCC Leg Definition window
3AG 86577 ABAA Ed3 435/725

To define a hard PVCC Leg:


Alcatel
− Destination point Z:
− Enter a ENE User Label
− Choose a termination Id. by using the sensitive help
− Enter a VPI by using the sensitive help
− Enter a VCI
− Tick the PVCC Prov. State Alignment to align the provisioning state of the Leg
on the PVCC.

− The point-multipoints does not exist.
− The Leg User Label is not unique for all the point-multipoints hard PVCCs.
− Comment is invalid.
− Destination extremity of the Leg is not a ENE.
− At the destination extremity of Leg, the hard PVPC does not exist.
− At the destination extremity of Leg, VCI is out of the VCI range of the hard
PVPC.
− At the destination extremity of Leg, VCI is already used on the hard PVPC.
3AG 86577 ABAA Ed3 436/725

4.4.4 Modify a hard PVCC Leg

The Hard PVPC Leg modification gives the possibility to modify:
User Label
Comment
Alcatel
mult ipoints hard PVCC in the list => Leg List => select a PVCC Leg in the list
=>Modify
This funct ion is available only if a Leg is selected.
Figure 4-169 Hard PVCC Leg Modification window
To modify a Hard PVCC Leg:

The process fails if the New User Label already exists.
3AG 86577 ABAA Ed3 437/725

4.4.5 Delete a hard PVCC Leg

This function consists in deleting a hard PVCC Leg from the 1354 BM supervision.
- The provisio ning state of the hard PVCC Leg must be Defined.
Alcatel
mult ipoints hard PVCC in the list => Leg List => select one or several hard PVCC
Legs in the list => Delete
Figure 4-170 Confirmation box for deleting one hard PVCC Leg
Figure 4-171 Confirmation box for deleting several hard PVCC Legs
After confirmation, the hard PVCC Legs are removed.
The hard PVCC Leg list is updated.
The usage state of each hard PVPC (extremities only) used by the hard PVCC Leg
changes to Idle (if it was not yet).
3AG 86577 ABAA Ed3 438/725

4.4.6 Allocate a hard PVCC Leg

This function describes the hard PVCC Leg allocation.
The provisio ning state of the hard PVCC Leg must be Defined.
Alcatel
Legs in the list =>Allocate
Figure 4-172 Hard PVCC Leg Allocation
3AG 86577 ABAA Ed3 439/725


Alcatel
Figure 4-173 Confirmation box for allocating several hard PVCC Legs
To allocate a hard PVCC Leg, you must defined some characteristics:

− Choose the Allocation Mode:
− Automatic: the 1354 BM automatically searches the shortest route binding
the two extremities of the Leg. The broadcast point is automatically found by
the 1354 BM or given by the operator.
− Semi automatic: consists in searching a route according to the constraints
defined on the Leg. The broadcast point is automatically found by the 1354
BM or given by the operator.
− Manual: The route of the Leg is fully given by the operator. It is given from
the broadcast point and till the destination extremity.

- The cost model is accessible only for automat ic and semi-automat ic allocation
mode.
3AG 86577 ABAA Ed3 440/725

− Define the Broadcast point:

− Select the NE User Label by using the sensitive help.

− Choose the Termination Id.
− Choose the VPI.
− Choose the VCI.
Alcatel
- For the first Leg allocat ion, the broadcast point is the origin extremit y of the Leg.

− There is not enough bandwidth on destination Transmission Path.
− Destination Transmission Path is locked.
When the process is finished, the provisioning state of the hard PVCC Leg changes
to Allocated.
The point-multipoints hard PVCC provisioning state changes to Allocated if all Legs
are allocated.
3AG 86577 ABAA Ed3 441/725

4.4.7 De-allocate a hard PVCC Leg

This function consists in releasing all the resources involved in a hard PVCC Leg.
- The provisio ning state of the hard PVCC Leg must be Allocated.
Alcatel
- The hard PVCC Leg must not be associated to a PM Measure.
Legs in the list => De-allocate
Figure 4-174 Confirmation box for de-allocating one hard PVCC Leg
Figure 4-175 Confirmation box for de-allocating several hard PVCC Legs
After confirmation, the hard PVCC Legs are de-allocated. Their provisioning states
change to Defined.
The usage state of each hard PVPC (except the extremities) used by the hard PVCC
Leg is changed to Idle if not any other hard PVCC Legs are carried.
The bandwidth load of each hard PVPC used by the hard PVCC Leg is updated for
3AG 86577 ABAA Ed3 442/725

4.4.8 Implement a hard PVCC Leg

This function consists in implementing all the VCLs involved in a hard PVCC Leg
(refer to § 4.3.7). Thus all the ATM NEs providing the end-connections and cross-
connections along the hard PVCC Leg route have to satisfy the traffic contract
Alcatel
- The provisio ning state of the hard PVCC Leg must be Allocated.
- The provisio ning state of those hard PVPCs must be Implemented or

Commissio ned.

Legs in the list => Implement
Figure 4-176 Confirmation box for implementing one hard PVCC Leg
Figure 4-177 Confirmation box for implementing several hard PVCC Legs
After confirmation, the hard PVCC Leg implementation process is launched.
Only the PVPCs involved in the hard PVCC Leg and whose administrative state is
Unlocked will be taken into account.
3AG 86577 ABAA Ed3 443/725

cross-connections and end-connections are de-implemented.
A message is displayed asking the operator to cancel the implementation or to

authorize the search for another route. This process can be repeated N times. (Not
available in release R7)
Alcatel
If all the concerned ATM NEs accept the requirements of the new hard PVCC Leg,
the implementation is successful. The hard PVCC Leg provisioning state changes to
Implemented.
The availability status are updated and managed in function of the alarms.
3AG 86577 ABAA Ed3 444/725

4.4.9 De-implement a hard PVCC Leg

involved in a hard PVCC Leg and previously performed at ATM NE level.
- The provisio ning state of the hard PVCC Leg must be Implemented or Allocated.
Alcatel

From the Main view, menu: Management => Hard => select a point-mult ipo ints
hard PVCC in the list => Leg List => select one or several hard PVCC Legs in the
list => De-implement
Figure 4-178 Confirmation box for de-implementing one hard PVCC Leg
Figure 4-179 Confirmation box for de-implementing several hard PVCC Legs
After confirmation, the hard PVCC Leg de-implementation process is launched.
1354 BM keeps de-implementing the other connections.
3AG 86577 ABAA Ed3 445/725

But the hard PVCC Leg provisioning state changes to Allocated and the availability
status change to None (not significant)
successful. The hard PVCC Leg provisioning state changes to Allocated and the
availability status change to None (not significant).
Alcatel
3AG 86577 ABAA Ed3 446/725

4.4.10 Commission a hard PVCC Leg

This function consists in setting in service a hard PVCC Leg.
- The provisio ning state of the hard PVCC Leg must be Implemented.
Alcatel
- The provisio ning state of the hard PVPCs involved in the hard PVCC Leg must be
Implemented or Commissio ned.
list => Commission
Figure 4-180 Confirmation box for commissioning one hard PVCC Leg
Figure 4-181 Confirmation box for commissioning several hard PVCC Legs
After confirmation, the hard PVCC Legs are commissioned. Their provisioning
states change to Commissioned.
3AG 86577 ABAA Ed3 447/725

4.4.11 De-commission a hard PVCC Leg

This function consists in setting out of service a hard PVCC Leg.
- The provisio ning state of the hard PVCC Leg must be Commissio ned.
Alcatel
list => De-commission
Figure 4-182 Confirmation box for de-commissioning one hard PVCC Leg
Figure 4-183 Confirmation box for de-commissioning several hard PVCC Legs
After confirmation, the hard PVCC Legs are de-commissioned. Their provisioning
states change to Implemented.
3AG 86577 ABAA Ed3 448/725

4.4.12 Display the hard PVCC Leg extremities

that support the hard PVCC Leg extremities.
Alcatel
mult ipoints hard PVCC in the list => Leg List => select a hard PVCC Leg in the list
=> Extremities
Figure 4-184 Hard PVCC Leg Extremities window
The fields have been filled out at the hard PVCC Leg definition (refer to § 0) time.
3AG 86577 ABAA Ed3 449/725

4.4.13 Display the hard PVCC Leg properties

hard PVCC Leg.
Alcatel
=> Properties
Figure 4-185 Hard PVCC Leg Properties window
The first fields have been filled out at the hard PVCC Leg definition (refer to § 0)
time.
PVCC Leg.
3AG 86577 ABAA Ed3 450/725

4.4.14 Display the hard PVCC Leg routing properties

This function consists in displaying the list of the VCLs used by the hard PVCC Leg.
A VCL is defined by a hard PVPC and a VCI used on it.
- The provisio ning state of the hard PVCC Leg must be Allocated, Implemented or
Alcatel
Commissio ned.
=> Routing
Figure 4-186 Hard PVCC Leg Routing Properties window

− PVPC User Label
− VCI
3AG 86577 ABAA Ed3 451/725

4.4.15 Display the hard PVCC Leg graphical view

to the sub-network that contains the VPCs used by the hard PVPC Leg.
Alcatel
- The provisio ning state of the hard PVCC Leg must be Allocated, Implemented or
Commissio ned.
From the Main view, menu: Management => Hard => PVCC => select a Point-
Mult ipo ints hard PVCC in the list => Leg List => select a Hard PVCC Leg in the list
=> Display Route
Figure 4-187 Sub-network view showing the VPCs used by the hard PVCC
3AG 86577 ABAA Ed3 452/725


With a selected entity (NE, transmission path, ENE, Off page connector): Begin and
Alcatel
End commands are completed by other commands depending on the selected entity.
3AG 86577 ABAA Ed3 453/725

4.4.16 Display the hard PVCC Leg NE NIM list

The hard PVCC Leg NE NIM list presents all the switched VCLs constituting the
selected hard PVCC Leg and allows to configure the NIMs on each intermediate
point of the hard PVCC Leg.
Alcatel
- The hard PVCC Leg must be at least Allocated.
PVCC point-mult ipo int in the list => Leg List => select one leg in the list => NE
NIM List
Figure 4-188 Hard PVCC Leg NE NIM List window
The descriptive attributes displayed for each hard PVCC Leg NE NIM are:
− NE User Label
− A Term Id.
− A Vpi
− A Ing.
− A Egr.
− Z Term Id.
− Z Vpi
− Z Ing.
− Z Egr.
3AG 86577 ABAA Ed3 454/725



− NE User Label
Alcatel
Figure 4-189 Hard PVCC Leg NE NIM Search window
From the hard PVCC Leg NE NIM list, you can:
configure the hard PVCC Leg NE NIMs, refer to § 4.4.16.1
3AG 86577 ABAA Ed3 455/725

4.4.16.1 Configure the hard PVCC Leg NE NIMs

This function allows the NIM's configuration of the selected Hard PVCC Leg.
PVCC point-mult ipo int in the list => Leg List => select one leg in the list => NE
NIM List => select one NE User label in the list => Configure
Alcatel
Figure 4-190 Hard PVCC Leg NE NIM Configuration window
In the Origin (A) and / or Destination (Z) area(s), tick the Ingress and / or the Egress
check bock(s) if you want to configure the NIM(s) of the selected NE User Label
chosen in the Hard PVCC Leg NIM List.
Click on Ok.
3AG 86577 ABAA Ed3 456/725


If the hard PVCC Leg provisioning state is established, implemented or

commissioned, a request is sent to the intermediate VCL_Ts chosen by the
Alcatel
If the hard PVCC Leg provisioning state is allocated, the NIM Point state
becomes On 1354 BM and the NIM Point creation will to be done on the ATM
NE at the hard PVPC implementation (the NIM Point state will become On NE).
Configured NIMs are added in the hard PVCC Leg NIM CC List.
If the hard PVCC Leg provisioning state is implemented or commissioned, a

request is sent to each chosen intermediate VCL_T composing the given hard
PVCC and supporting an NIM Point, to delete them if no OAM service uses those
NIMs Points.
If the hard PVCC Leg is de-implemented, all the NIM Points created when
3AG 86577 ABAA Ed3 457/725

4.4.17 Display the hard PVCC Leg Constraint list

The hard PVCC Leg Constraint list presents all the hard PVCCs Leg constraint
Alcatel
=> Constraint
Figure 4-191 Hard PVCC Leg Constraint List window
The descriptive attributes displayed for each hard PVCC constraints are:
− User Label
− Constraint Kind
− Term. Id.

− User Label
3AG 86577 ABAA Ed3 458/725

Alcatel
Figure 4-192 Hard PVCC Leg Constraint Search window
From the hard PVCC Constraint List, you can:
Add a constraint to a hard PVCC Leg, refer to § 4.4.17.1
Delete a constraint from a hard PVCC Leg, refer to § 4.4.17.2
3AG 86577 ABAA Ed3 459/725

4.4.17.1 Add a constraint to a hard PVCC Leg

existing hard PVCC Leg.
Alcatel
=> Constraint List => Add a constraint
Figure 4-193 Hard PVCC Leg Constraint Definition window
To define a hard PVCC Leg constraint:

− Negative Node: consists in defining some NE that must not be used for the
Paths.
− Negative Link: consists in defining some Transmission Paths that must not
be used for hard PVCC allocation.
3AG 86577 ABAA Ed3 460/725


Alcatel


3AG 86577 ABAA Ed3 461/725

4.4.17.2 Delete a constraint from a hard PVCC Leg

- The constraint of the hard PVCC Leg must be Created.

Alcatel
PVCC => Leg List => select a hard PVCC Leg in the list => Constraint List =>
select one or several constraints in the list => Delete
Figure 4-194 Confirmation box for deleting a Constraint from a Hard PVCC Leg
Figure 4-195 Confirmation box for deleting several Constraints from a Hard PVCC Leg
3AG 86577 ABAA Ed3 462/725

4.5 Managing soft PVPCs
The soft PVPC management, part of the network management, consists in:
defining soft PVPCs:
Alcatel
− traffic profile
− extremities
deleting, modifying soft PVPCs
setting in/out of service soft PVPCs:
− set-up/release function
− activating / deactivating the continuity check on soft PVPCs
− activating / deactivating the output shaping on soft PVPCs
− activating / deactivating the UPC/NPC on soft PVPCs
− displaying soft PVPC information such as:
− soft PVPC list
− bandwidth load, traffic and routing
− graphical view
The soft PVPC management chain gives the order in which the available actions may
be performed.
Activate/
deactivate CC
Define
Delete
Modify
Activate/ deactivate
output shaping
Set-up Release
UPC/NPC
Figure 4-196 Soft PVPC management chain
3AG 86577 ABAA Ed3 463/725

operation performed on the soft PVPC.
Define
Establishing
Alcatel
Set-up
Established
Defined
Release
Delete
Figure 4-197 Soft PVPC provisioning state
The soft PVPC management is performed from the Soft PVPC List window that
includes two panels as follows:
− Description
− Characteristics
For managing soft PVPCs, you can:
display the soft PVPC description list, refer to § 4.5.1
display the soft PVPC characteristic list, refer to § 4.5.7
3AG 86577 ABAA Ed3 464/725

4.5.1 Display the soft PVPC description list

The soft PVPC description list presents all the soft PVPCs managed by the 1354 BM
From the Main view, menu: Management => Soft => PVPC => select the
Alcatel
Description panel
Figure 4-198 Soft PVPC List window – Description panel
The descriptive attributes displayed for each soft PVPC are:

− User Label
− Provis. State
− Calling conn. End Point
− Called conn. End Point

− User Label
3AG 86577 ABAA Ed3 465/725

Alcatel
Figure 4-199 Soft PVPC Description Search window
3AG 86577 ABAA Ed3 466/725

From the so ft PVPC descript ion list, you can:
define a soft PVPC, refer to § 4.5.2
modify a soft PVPC, refer to § 4.5.3

Alcatel
delete a soft PVPC, refer to § 4.5.4
set-up a soft PVPC, refer to § 4.5.5
release a soft PVPC, refer to § 4.5.6
display the soft PVPC characteristics list, refer to § 4.5.7
activate the output shaping on a soft PVPC, refer to § 4.5.8
deactivate the output shaping on a soft PVPC, refer to § 4.5.9
activate UPC / NPC on a soft PVPC, refer to § 4.5.10
deactivate UPC / NPC on a soft PVPC, refer to § 4.5.11
display the soft PVPC extremities, refer to § 4.5.12
display the soft PVPC properties, refer to § 4.5.13
display the soft PVPC bandwidth load, refer to § 4.5.14
display the soft PVPC traffic properties, refer to § 4.5.15
display the soft PVPC routing properties, refer to § 4.5.16
activate/deactivate the CC on a soft PVPC (change CC direction), refer to §

4.5.17
display the soft PVPC graphical view, refer to § 4.5.18
3AG 86577 ABAA Ed3 467/725

4.5.2 Define a soft PVPC

This function consists in identifying the soft PVPC and determining its traffic profile
and the NEs (and/or ENEs) that support its extremities. To have more information
about Soft PVPC, refer to § 1.4.2
Alcatel
- The NEs (and/or ENEs) supporting the extremit ies of the soft PVPC must be
previously defined.
- Both transmission paths supporting the extremit ies of the soft PVPC must exist
and be configured with the same configurat ion.
- The maximum number of PVPCs must not be reached.
Description panel => Define Soft PVPC
3AG 86577 ABAA Ed3 468/725


Alcatel
Figure 4-200 Soft PVPC Definition window
To define a soft PVPC:

− Enter a PVPC User Label
3AG 86577 ABAA Ed3 469/725


Alcatel
Figure 4-201 Soft PVPC Definition window (extended view)
The traffic contracts of Soft VPCs which are authorized are:

− DBR Class 1
− UBR + (= DBR Class U (UBR.2) with MCR > 0) cell based
− In the Calling End Point and Called End Point areas, enter the identification
parameters of the NEs and/or ENEs that support the soft PVPC extremities:
− Only for the called end point, tick the ENE check box if the extremity is
supported by an ENE.
− Enter an ATM Address number.
− Enter a VPI number.
3AG 86577 ABAA Ed3 470/725

− Optional parameters: in the Calling Connection End Point and Called

Connection End Point areas, enter the identification parameters of the NEs
and/or ENEs that support the extremities of the hard PVPCs associated to the
soft PVPC:
Alcatel
− Enter a VPI number.
If the connect ion endpo int is not specified, it is deduced by the 1354 BM, as being
the point contiguous to the respective calling/called endpo int.
− Click on Ok.
The soft PVPC is defined into the 1354 BM with the following states:
− UPC/NPC state :
− Disabled if the interface types of the transmission paths of both extremities
are NNI
− Enabled if the interface type of at least one transmission path of both
− shaping state : Disabled
The soft PVPC description and characteristic lists are updated.
3AG 86577 ABAA Ed3 471/725

4.5.3 Modify a soft PVPC

The soft PVPC modification gives the possibility to modify:
User Label
Comment
Alcatel
- The provisio ning state of the soft PVPC must be Defined.
Description panel => select one or several soft PVPCs in the list => Delete
Figure 4-202 Soft PVPC Modification
After confirmation, the parameters of the soft PVPC are modified.
3AG 86577 ABAA Ed3 472/725

4.5.4 Delete a soft PVPC

This function consists in deleting a soft PVPC from the 1354 BM supervision.

Alcatel
Description panel => select one or several soft PVPCs in the list => Delete
Figure 4-203 Confirmation box for deleting one soft PVPC
Figure 4-204 Confirmation box for deleting several soft PVPCs
After confirmation, the soft PVPCs are removed.
3AG 86577 ABAA Ed3 473/725

4.5.5 Set-up a soft PVPC

This function consists in setting in service a soft PVPC. This establishes a connection
using PNNI.
- The provisio ning state of the soft PVPC must be defined.

Alcatel
- Both calling and called NEs must belong to a peer group (not implemented in
release R7).
Description panel => select one or several defined soft PVPCs in the list => Set-up
Figure 4-205 Confirmation box for setting-up one soft PVPC
Figure 4-206 Confirmation box for setting-up several soft PVPCs

After confirmation, the soft PVPC set-up process is launched. The 1354 BM:
− creates the hard PVPC between the calling end point and the calling connection
end point
− creates the hard PVPC between the called end point and the called connection end
point, except if the called end point is an ENE
− allocates, implements and commissions the hard PVPC(s)
− sends a set-up request to the calling NE so that it searches for a path to reach the
called NE
The calling ATM NE is in charge of searching a path to reach the called ATM NE.
If there is no way to establish the soft PVPC by using the existing resources, new
transmission paths have to be created before the user requests another set-up.
3AG 86577 ABAA Ed3 474/725

The provisioning state changes to Establishing if the NE accepts the set-up request.
If the set-up is successful, the soft PVPC provisioning state changes to Establishing
and its availability status is updated and managed in function of the alarms. The soft
PVPC description and characteristic lists are updated.
Alcatel
3AG 86577 ABAA Ed3 475/725

4.5.6 Release a soft PVPC

This function consists in setting out of service a soft PVPC.
- The provisio ning state of all the so ft PVCCs passing through the soft PVPC must
be Defined.
Alcatel
- The provisio ning state of the soft PVPC must be Established or Establishing.
- The soft PVPC must not be associated to a PM Measure.
Description panel => select one or several established so ft PVPCs in the list =>
Release
Figure 4-207 Confirmation box for releasing one soft PVPC
Figure 4-208 Confirmation box for releasing several soft PVPCs
After confirmation, the soft PVPC release process is launched. The 1354 BM:
− sends the release resquest to the calling NE that is in charge of releasing the
resources used by the soft PVPC
− de-commissions, de-implements, de-allocates and delete the hard PVPC(s)
associated to the soft PVPC.
When the release process is finished, the soft PVPC provisional state changes to
Defined and its availability status changes to None (no more significant).
3AG 86577 ABAA Ed3 476/725

4.5.7 Display the soft PVPC characteristic list

The soft PVPC characteristic list presents all the soft PVPCs managed by the 1354
BM and their characteristic attributes.
Characteristics panel
Alcatel
Figure 4-209 Soft PVPC List window – Characteristics panel
The characteristic attributes displayed for each soft PVPC are:

− User Label
− Provis. State
− Direction
− VCI Range
− Interface Type
− Shap. State
− Shaping Mode
− UPC / NPC state
− Avail. Status

− User Label
3AG 86577 ABAA Ed3 477/725


Alcatel
Figure 4-210 Soft PVPC Characteristics Search window
From the so ft PVPC characterist ic list, you can:
define a soft PVPC, refer to § 4.5.2
modify a soft PVPC, refer to § 4.5.3
delete a soft PVPC, refer to § 4.5.4
set-up a soft PVPC, refer to § 4.5.5
release a soft PVPC, refer to § 4.5.6
activate the output shaping on a soft PVPC, refer to § 4.5.8
deactivate the output shaping on a soft PVPC, refer to § 4.5.9
activate UPC / NPC on a soft PVPC, refer to § 4.5.10
deactivate UPC / NPC on a soft PVPC, refer to § 4.5.11
display the soft PVPC extremities, refer to § 4.5.12
display the soft PVPC properties, refer to § 4.5.13
display the soft PVPC bandwidth load, refer to § 4.5.14
display the soft PVPC traffic properties, refer to § 4.5.15
display the soft PVPC routing properties, refer to § 4.5.16
activate/deactivate the CC on a soft PVPC (change CC direction), refer to §

4.5.17
3AG 86577 ABAA Ed3 478/725

Alcatel
3AG 86577 ABAA Ed3

display the soft PVPC graphical view, refer to § 4.5.18
479/725
4.5.8 Activate the output shaping on a soft PVPC

This function consists in enabling the output shaping feature on a soft PVPC.
negotiated PCR.
Alcatel
- The shaping state of the soft PVPC must be Disabled.
- The traffic contract of the soft PVPC must be DBR class 1 with a PCR greater or
equal to 180 cell/s.
- All the ATM NEs used by the soft PVPC have to support the output shaping
feature.
- The maximum number of shaped PVPC must not be reached.
Characteristics panel => select one or several soft PVPCs in the list => Act. Shap.
Figure 4-211 Confirmation box for activating the output shaping on one soft PVPC
Figure 4-212 Confirmation box for activating the output shaping on several soft PVPCs
3AG 86577 ABAA Ed3 480/725

To activate the output shaping on one soft PVPC:

− Choose the location where the output shaping will be activated, by using the
Shaping Protection Mode option button.
− Click on Ok.
Alcatel
To activate the output shaping on several soft PVPCs:

− If you click on All, the parameter is available for all the selected soft PVPCs.
− If you click on Yes, the parameter is available only for the soft PVPC currently
displayed in the confirmation box.
The shaping state of the soft PVPC changes to Enabled.
At next set-up of the soft PVPC, the output shaping activation request will be sent to
the chosen NEs.
The soft PVPC characteristic list is updated.
3AG 86577 ABAA Ed3 481/725

4.5.9 Deactivate the output shaping on a soft PVPC

This function consists in disabling the output shaping function on a soft PVPC.
- The shaping state of the soft PVPC must be Enabled.

Alcatel
Characteristics panel => select one or several so ft PVPCs in the list => Deact.
Shap.
Figure 4-213 Confirmation box for deactivating the output shaping on one soft PVPC
Figure 4-214 Confirmation box for deactivating the output shaping on several soft PVPCs
After confirmation, the shaping state of the soft PVPCs change to Disabled.
3AG 86577 ABAA Ed3 482/725

4.5.10 Activate UPC / NPC on a soft PVPC

This function consists in activating an ATM police control on a soft PVPC that

Alcatel
- The UPC / NPC state of the soft PVPC must be Disabled.
- At least one transmissio n path used at the extremit y o f the soft PVPC must have
an ICI or UNI interface t ype.
Characteristics panel => select one or several so ft PVPCs in the list => Act. UPC
Figure 4-215 Confirmation box for activating UPC / NPC on one soft PVPC
Figure 4-216 Confirmation box for activating UPC / NPC on several soft PVPCs
After confirmation, the UPC / NPC state of each soft PVPC changes to Enabled.
At next implementation of the soft PVPC, the UPC / NPC activation request will be
3AG 86577 ABAA Ed3 483/725

4.5.11 Deactivate UPC / NPC on a soft PVPC

This function consists in deactivating the ATM police control on a soft PVPC.
- The UPC / NPC state of the soft PVPC must be Enabled.

Alcatel
Characteristics panel => select one or several so ft PVPCs in the list => Deact. UPC
Figure 4-217 Confirmation box for deactivating UPC / NPC on one soft PVPC
Figure 4-218 Confirmation box for deactivating UPC / NPC on several soft PVPCs
After confirmation, the UPC / NPC state of each soft PVPC changes to Disabled.
3AG 86577 ABAA Ed3 484/725

4.5.12 Display the soft PVPC extremities

that support the soft PVPC extremities.
Alcatel
Characteristics panel => select a soft PVPC in the list => Extremities
Figure 4-219 Soft PVPC Extremities window
The fields have been filled out at the soft PVPC definition (refer to § 4.5.2) time.
3AG 86577 ABAA Ed3 485/725

4.5.13 Display the soft PVPC properties

soft PVPC.
Alcatel
Characteristics panel => select a soft PVPC in the list => Properties
Figure 4-220 Soft PVPC Properties window
The first fields have been filled out at the soft PVPC definition (refer to § 4.5.2) time.
The last two ones give information about the last action performed on the soft PVPC.
3AG 86577 ABAA Ed3 486/725

4.5.14 Display the soft PVPC bandwidth load

This function consists in displaying information about the soft PVPC bandwidth load
and the number of soft PVCCs using this soft PVPC.
- The provisio ning state of the soft PVPC must be Establishing or Established.
Alcatel
Characteristics panel => select a soft PVPC in the list => Bandwidth Load
Figure 4-221 Soft PVPC Bandwidth Load window
3AG 86577 ABAA Ed3 487/725

The window is split into three areas:

information for each direction used by the PVCCs:
− Total (cell/s): total number of cells per second passing through the soft PVPC
− Established (%): percentage of bandwidth used by PVCCs whose
Alcatel
provisioning state is Established or Establishing

− Available (%): percentage of bandwidth not used by any PVCCs
− Bar-chart showing in another way the previous percentages
− The Nb. VCI area gives:

− the total number of VCIs using the PVPC
− the number of VCIs established
All the forward bandwidth values are set to zero in the fo llowing cases:
− The called end point extremity is an ENE
− The called connection end point extremity is an ENE
− The calling connection end point extremity is an ENE
3AG 86577 ABAA Ed3 488/725

4.5.15 Display the soft PVPC traffic properties

by a soft PVPC.
Alcatel
Characteristics panel => select a soft PVPC in the list => Traffic
Figure 4-222 Soft PVPC Traffic Properties window
traffic contract.
3AG 86577 ABAA Ed3 489/725

4.5.16 Display the soft PVPC routing properties

This function consists in displaying information about the transmission paths and
VPis used by a soft PVPC.
Not implemented in release R7.

Alcatel
4.5.17 Activate/deactivate the CC on a soft PVPC (change CC

direction)
This function consists in activating/deactivating the Continuity Check (CC) for one
or both directions of a soft PVPC.
4.5.18 Display the soft PVPC graphical view

This function consists in displaying the graphical view (transmission path domain)
corresponding to the sub-network that contains the transmission paths used by the
soft PVPC.
3AG 86577 ABAA Ed3 490/725

4.6 Managing soft PVCCs
The soft PVCC management, part of the network management, consists in:
defining soft PVCCs:
Alcatel
− traffic profile
− extremities
deleting, modifying soft PVCCs
setting in/out of service soft PVCCs:
− set-up/release function
activating / deactivating the continuity check on soft PVCCs
activating / deactivating the UPC/NPC on soft PVCCs
− displaying soft PVCC information such as:
− soft PVCC list
− graphical view
The soft PVCC management chain gives the order in which the available actions may
be performed.
Define Activate/
deactivate CC
Delete
Modify
Set-up Release
UPC/NPC
Figure 4-223 Soft PVCC management chain
3AG 86577 ABAA Ed3 491/725

operation performed on the soft PVCC.
Define
Establishing
Alcatel
Set-up
Established
Defined
Release
Delete
Figure 4-224 Soft PVCC provisioning state
The soft PVCC management is performed from the Soft PVCC List window that
includes two panels as follows:
Description
Characteristics
For managing soft PVCCs, you can:
display the soft PVCC description list, refer to § 4.6.1
display the soft PVCC characteristic list, refer to § 4.6.7
3AG 86577 ABAA Ed3 492/725

4.6.1 Display the soft PVCC description list

The soft PVCC description list presents all the soft PVCCs managed by the 1354 BM
From the Main view, menu: Management => Soft => PVCC => select the
Alcatel
Description panel
Figure 4-225 Soft PVCC List window – Description panel
The descriptive attributes displayed for each soft PVCC are:

− User Label
− Provisioning State
− Calling connection End Point
− Called connection End Point

− User Label
3AG 86577 ABAA Ed3 493/725

Alcatel
Figure 4-226 Soft PVCC Description Search window
3AG 86577 ABAA Ed3 494/725

From the so ft PVCC descript ion list, you can:
define a soft PVCC, refer to § 4.6.2
modify a soft PVCC, refer to § 4.6.3

Alcatel
delete a soft PVCC, refer to § 4.6.4
set-up a soft PVCC, refer to § 4.6.5
release a soft PVCC, refer to § 4.6.6
display the soft PVCC characteristic list, refer to § 4.6.7
activate UPC / NPC on a soft PVCC, refer to § 4.6.8
deactivate UPC / NPC on a soft PVCC, refer to § 4.6.9
display the soft PVCC extremities, refer to § 4.6.10
display the soft PVCC properties, refer to § 4.6.11
display the soft PVCC traffic properties, refer to § 4.6.12
display the soft PVCC routing properties, refer to § 4.6.13
activate/deactivate the CC on a soft PVCC (change CC direction), refer to §

4.6.14
display the soft PVCC graphical view, refer to § 4.6.15
3AG 86577 ABAA Ed3 495/725

4.6.2 Define a soft PVCC

This function consists in identifying the soft PVCC and determining its traffic profile
and the ATM NEs (and/or ENEs) that support its extremities.
To have more information about Soft PVPC, refer to § 1.4.2

Alcatel
A so ft PVCC does not necessarily need soft PVPCs to carry it. It can use direct ly so ft
configured transmissio n paths.
- The NEs (and/or ENEs) supporting the extremit ies of the soft PVCC must be
previously defined.
- The maximum number of PVCCs must not be exceeded.
Description panel => Define Soft PVCC
3AG 86577 ABAA Ed3 496/725


Alcatel
Figure 4-227 Soft PVCC Definition window
To define a soft PVCC:

− Enter a PVCC User Label
3AG 86577 ABAA Ed3 497/725


Alcatel
Figure 4-228 Soft PVCC Definition window (extended view)
− In the Calling End Point and Called End Point areas, enter the identification
parameters of the NEs and/or ENEs that support the soft PVCC extremities:
. Only for the called end point, tick the ENE check box if the extremity is
supported by an ENE.
. Choose the NE (or ENE) User Label by using the sensitive help.
. Choose the Termination Id. by using the sensitive help.
. Enter an ATM Address number.
. Enter a VPI number.
. Enter a VCI number.
− In the Calling Connection End Point and Called Connection End Point areas
(optional parameters), enter the identification parameters of the NEs and/or ENEs
that support the extremities of the hard PVCCs associated to the soft PVCC:
. Tick the ENE check box if the extremity is supported by an ENE.
. Choose the NE (or ENE) User Label by using the sensitive help.
. Choose the Termination Id. by using the sensitive help.
. Enter a VPI number.
. Enter a VCI number.
− Click on Ok.
3AG 86577 ABAA Ed3 498/725

The traffic contracts of Soft VCCs which are authorized are:

− DBR Class 1
− DBR Class 2
− DBR Class U (UBR.1) frame based and cell based
− DBR Class U (UBR.2) frame based and cell based
Alcatel
− UBR+ frame based
Also the traffic contracts of soft VPCs and so ft VCCs have to be compatible:
ê Soft VPCs ê Supported Soft VCCs
ê DBR class1 cross-connected ê DBR class1, DBR class2
ê DBR class1 shaped (grooming) ê DBR class1, DBR class2, DBR
or DBRclass1 no cross-connected classU (UBR1 and UBR2 cell based
or frame based), UBR+ (frame based)
ê DBR classU (UBR1) cross- ê DBR classU (UBR1 and UBR2
connected cell based)
ê DBR classU (UBR2) cross- ê DBR classU (UBR2 cell based)
connected
ê DBR classU (UBR1 or UBR2) ê DBR classU (UBR1 and UBR2
no cross-connected cell or frame based)
ê UBR+ (= DBRclassU (UBR2) ê UBR+ (frame based)
with MDCR > 0) cross-connected or
not (cell based)
• cross connected means : VPC made of two VCLs or more
• no cross connected means : VPC made of one VCL
The soft PVCC is defined into the 1354 BM with the following states:
− UPC/NPC state :
− Disabled if the interface types of the transmission paths of both extremities
are NNI
− Enabled if the interface type of at least one transmission path of both
The soft PVCC description and characteristic lists are updated.
3AG 86577 ABAA Ed3 499/725

4.6.3 Modify a soft PVCC

The soft PVCC modification gives the possibility to modify:
− User Label
− Comment
Alcatel
- The provisio ning state of the soft PVCC must be Defined.
Description panel => select one or several soft PVCCs in the list => Delete
Figure 4-229 Soft PVCC Modification
After confirmation, the parameters of the soft PVCC are modified.
3AG 86577 ABAA Ed3 500/725

4.6.4 Delete a soft PVCC

This function consists in deleting a soft PVCC from the 1354 BM supervision.

Alcatel
Description panel => select one or several soft PVCCs in the list => Delete
Figure 4-230 Confirmation box for deleting one soft PVCC
Figure 4-231 Confirmation box for deleting several soft PVCCs
After confirmation, the soft PVCCs are removed.
3AG 86577 ABAA Ed3 501/725

4.6.5 Set-up a soft PVCC

This function consists in setting in service a soft PVCC. This establishes a
connection using PNNI.

Alcatel
- Both calling and called NEs must belong to a peer group (not implemented in
release R7).
Description panel => select one or several defined soft PVCCs in the list => Set-up
Figure 4-232 Confirmation box for setting-up one soft PVCC
Figure 4-233 Confirmation box for setting-up several soft PVCCs
3AG 86577 ABAA Ed3 502/725

After confirmation, the soft PVCC set-up process is launched. The 1354 BM:
− creates the hard PVCC between the calling end point and the calling connection
end point
− creates the hard PVCC between the called end point and the called connection end
point, except if the called end point is an ENE
− allocates, implements and commisions the hard PVCC(s)
Alcatel
− sends a set-up request to the calling NE so that it searches for a path to reach the
called NE
The calling ATM NE is in charge of searching a path to reach the called ATM NE.
If there is no way to establish the soft PVCC by using the existing resources, new
transmission paths have to be created before the user requests another set-up.
The provisioning state changes to Establishing if the NE accepts the set-up request.
If the set-up is successful, the soft PVCC provisioning state changes to Established
and its availability status is updated and managed in function of the alarms. The soft
PVCC description and characteristic lists are updated.
3AG 86577 ABAA Ed3 503/725

4.6.6 Release a soft PVCC

This function consists in setting out of service a soft PVCC.
- The provisio ning state of the soft PVCC must be Established or Establishing.
Alcatel
- The soft PVCC must not be associated to a PM Measure.
Description panel => select one or several established so ft PVCCs in the list =>
Release
Figure 4-234 Confirmation box for releasing one soft PVCC
Figure 4-235 Confirmation box for releasing several soft PVCCs
After confirmation, the soft PVCC release process is launched. The 1354 BM:
− sends the release resquest to the calling NE that is in charge of releasing the
resources used by the soft PVCC.
− de-commissions, de-implements, de-allocates and delete the hard PVCC(s)
associated to the soft PVCC.
When the release process is finished, the soft PVCC provisioning state changes to
Defined and its availability status changes to None (no more significant).
3AG 86577 ABAA Ed3 504/725

4.6.7 Display the soft PVCC characteristic list

The soft PVCC characteristic list presents all the soft PVCCs managed by the 1354
BM and their characteristic attributes.
Alcatel
Characteristics panel
Figure 4-236 Soft PVCC List window – Characteristics panel
The characteristic attributes displayed for each soft PVCC are:

− User Label
− Provis. State
− Direction
− Interface Type
− UPC / NPC State
− Avail. Status

− User Label
3AG 86577 ABAA Ed3 505/725

Alcatel
Figure 4-237 Soft PVCC Characteristics Search window
3AG 86577 ABAA Ed3 506/725

From the so ft PVCC characterist ic list, you can:
define a soft PVCC, refer to § 4.6.2
modify a soft PVCC, refer to § 4.6.3

Alcatel
delete a soft PVCC, refer to § 4.6.4
set-up a soft PVCC, refer to § 4.6.5
release a soft PVCC, refer to § 4.6.6
activate UPC / NPC on a soft PVCC, refer to § 4.6.8
deactivate UPC / NPC on a soft PVCC, refer to § 4.6.9
display the soft PVCC extremities, refer to § 4.6.10
display the soft PVCC properties, refer to § 4.6.11
display the soft PVCC traffic properties, refer to § 4.6.12
display the soft PVCC routing properties, refer to § 4.6.13
activate/deactivate the CC on a soft PVCC (change CC direction), refer to §

4.6.14
display the soft PVCC graphical view, refer to § 4.6.15
3AG 86577 ABAA Ed3 507/725

4.6.8 Activate UPC / NPC on a soft PVCC

This function consists in activating an ATM police control on a soft PVCC that

Alcatel
- The UPC / NPC state of the soft PVCC must be Disabled.
- At least one transmissio n path used at the extremit y o f the soft PVCC must have
an ICI or UNI interface t ype.
Characteristics panel => select one or several so ft PVCCs in the list => Act. UPC
Figure 4-238 Confirmation box for activating UPC / NPC on one soft PVCC
Figure 4-239 Confirmation box for activating UPC / NPC on several soft PVCCs
After confirmation, the UPC / NPC state of each soft PVCC changes to Enabled.
At next implementation of the soft PVCC, the UPC / NPC activation request will be
The soft PVCC characteristic list is updated.
3AG 86577 ABAA Ed3 508/725

4.6.9 Deactivate UPC / NPC on a soft PVCC

This function consists in deactivating the ATM police control on a soft PVCC.
- The UPC / NPC state of the soft PVCC must be Enabled.

Alcatel
Characteristics panel => select one or several so ft PVCCs in the list => Deact.
UPC
Figure 4-240 Confirmation box for deactivating UPC / NPC on one soft PVCC
Figure 4-241 Confirmation box for deactivating UPC / NPC on several soft PVCCs
After confirmation, the UPC / NPC states of the soft PVCCs change to Disabled.
The soft PVCC characteristic list is updated.
3AG 86577 ABAA Ed3 509/725

4.6.10 Display the soft PVCC extremities

that support the soft PVCC extremities.
Alcatel
Characteristics panel => select a soft PVCC in the list => Extremities
Figure 4-242 Soft PVCC Extremities window
The fields have been filled out at the soft PVCC definition (refer to § 4.6.2) time.
3AG 86577 ABAA Ed3 510/725

4.6.11 Display the soft PVCC properties

soft PVCC.
Alcatel
Characteristics panel => select a soft PVCC in the list => Properties
Figure 4-243 Soft PVCC Properties window
The first fields have been filled out at the soft PVCC definition (refer to § 4.6.2)
time.
The last two ones give information about the last action performed on the soft PVCC.
3AG 86577 ABAA Ed3 511/725

4.6.12 Display the soft PVCC traffic properties

by a soft PVCC.
Alcatel
Characteristics panel => select a soft PVCC in the list => Traffic
Figure 4-244 Soft PVCC Traffic Properties window
traffic contract.
3AG 86577 ABAA Ed3 512/725

4.6.13 Display the soft PVCC routing properties

This function consists in displaying information about the PVPCs and VCIs used by
a soft PVCC.
Not implemented in R7.

Alcatel
4.6.14 Activate/deactivate the CC on a soft PVCC (change CC

direction)
This function consists in activating/deactivating the Continuity Check (CC) for one
or both directions of a soft PVCC.
Not implemented in R7.
4.6.15 Display the soft PVCC graphical view

to the sub-network that contains the VPs used by the soft PVCC.
3AG 86577 ABAA Ed3 513/725

Alcatel
3AG 86577 ABAA Ed3

514/725
5 maintenance management

Alcatel
5 Maintenance management
This chapter deals with the ways to monitor

the ATM network.
5.1 Test management

Test management mainly include NIM management, Segment management, Continunity management and
LookBack management.
5.1.1 Loop Back Test

The ATM layer loopback capability allows to insert LB(Loop Back) cells at one location along a
VPC/VCC and return them (or looped back) at a different location, without having to take the
connection out-of-service. LB cells can be inserted at an accessible point along the VPC/VCC (i.e. at an
endpoint or any CP(connection point)) without disrupting the sequence of user cells. The cell is looped
back at a downstream point according to the information contained in its information field (i.e. The LB
cell contains the designation of the point where it must be looped back).
Loopback applies to the two ATM VP and VC levels. VP level is referenced as F4 maintenance flow,
while VC is referenced as F5 maintenance flow.
The loopback process is activated on a VPL_T or VCL_T. Only end-to-end loopback application is
supported by ISA board: An end-to-end LB cell is inserted at one connection point of the PVC
(including the end-points). It is looped back by the egress connection end-point and discarded by the NE
where the insertion has been performed. Note that if the LB cell arrives to the insertion point after a 5
seconds delay, then it is passed-thought and discarded by the ingress connection end-point (see figure
below).
3AG 86577 ABAA Ed3 515/725

LB Cell insertion
ingress egress
VPL_T
Alcatel
LB cells discard. If LB cell arrives before the 5s Loop back point.

timer expires:
- LB Cells removal
Connection endpoint - Test result storage
If timer expires before LB cell

Connection point
is returned:
- Test result storage
End-to-end loopback process can be activated only as a single loopback (one LB cell is sent and looped).
Two kinds of loopback mechanisms can be performed:
network-side loopback: The ATM matrix is crossed.
line-side loopback: The ATM matrix is not crossed.
On the next figure, two loopback test are described, started on the same VPL_T but using the two different
modes, line-side and network-side. Note that depending on the mode the LB cell is opposite direction.
N etwork- side Line- side

VPL_T
VP-Forward
egress
X
egress
VP_Backward
In the example below, the loopback tests are performed toward the same connection end-point, using the two
different mode. Note that the LB cell is not inserted in the same VPL_T.
N etwork- side VPL_T VPL_T Line- side
VP-Forward
egress
X
VP_Backward
On a connection end-point (terminated VPL_T), only the line-side loopback can be applied.
Tested VP/VC connection must be bidirectional, as a consequence it is not applicable to point-to-multipoints
PVC.
The network is able to proceed a loopback without a command from the BM. For example, a customer outside
the BM-managed domain may initiate a loopback. This does not preclude the reporting of loopback results to the
BM.
5.1.1.1 Start LoopBack on HVPC
From the Main view, menu:Maintenance=>OAM=>Loopback
3AG 86577 ABAA Ed3 516/725


Alcatel
Figure 5-1 Hard VPC/Hard VCC List for Loopback
Select a tested Hard VPC VPC_M1_M2 in items Hard VPC,dot mouse’s right key,
pop-up Start Hard VPC Loopback window:
Figure 5-2 Start Hard VPC Loopback

Input related fileds using sensitive help selection,Enter “ok” button,implement Loopback procedure:
Figure 5-3 implement Hard VPC Loopback
If loopback point is a ENE,you will input loopback point ID(LLID) manually.
5.1.1.2 Start LoopBack on HVCC

From the Main view, menu:Maintenance=>OAM=>Loopback
Select Hard VCC item
3AG 86577 ABAA Ed3 517/725


Alcatel
Figure 5-4 Hard VPC/Hard VCC List for Loopback
Select a tested Hard VCC VPC_1.11_1.12 in items Hard VCC,dot mouse’s right key,
pop-up Start Hard VCC Loopback window:
Figure 5-5 Start Hard VCC Loopback
Figure 5-6 implement Hard VCC Loopback
If loopback point is a ENE,you will input loopback point ID(LLID) manually.
3AG 86577 ABAA Ed3 518/725

5.1.1.3 Modify NE’s ingress and egress ID

Normally, NE’s ingress and egress ID for LoopBack is generated automatically when
defining NE,but you also can modify them manually as follows:
on a selected NE,mouse’s right key dot=>Modify

Alcatel
Figure 5-7 Modify NE’s ingress and egress ID
3AG 86577 ABAA Ed3 519/725

6 Performance Management

Alcatel
6 Performance management
This chapter deals with the performance

management offered by the 1354 BM.
6.2 Managing PM Measures
6.3 Managing Periodic Report Profiles
6.4 Managing TCA Profiles
3AG 86577 ABAA Ed3 520/725

6.1 Generalities
The Performance Monitoring management is divided into two categories:

− The non-OAM PM primitives are related to events local to the NE (e.g
received, transmitted or discarded cells). The purpose is the maintenance of
Alcatel
Transmission Paths, and the connection management of PVCs.

The non-OAM PM can be applied on a Transmission Path if it is configured,
or on a PVC if it is either implemented or comissioned.
− The OAM PM primitives are associated to the PM OAM flow, to monitor the
quality of service of a PVC or a segment. The OAM PM can be applied on a
segment of PVC, when the PVC owning the segment is either implemented or
commissioned.
The OAM PM category is not implemented in R7.
The Network management can retrieve some performance information counters:

− By threshold crossing mechanism
− By collecting data.
All the counters are deactivated by default. The counters are maintained and
reported at two granularities: 15 Min and 24 H.
For a given measurement point, the counters activation / de-activation is done for
the whole block of counters available (i.e. the different counters of a measurement
point cannot be started separately).
The Performance Monitoring management can be managed with the following set
of functionnalities:
− PM Measures management (refer to § 6.2)
− PM Data collect (refer to § 6.2.7)
− PM data visualization (refer to § 6.2.11)
− Periodic reports profiles management (refer to § 6.3)
− Threshold Crossing Alamr (TCA) profile management (refer to § 6.4)
3AG 86577 ABAA Ed3 521/725

6.1.1 Non-OAM PM management

The Non-OAM Performances, used for maintenance or connection monitoring,
are provided on three different layers:
− Transmission Path layer (on TP/VP_A measurement point)
Alcatel
− VP layer (on cross-connected VPL_T measurement point)

− VC layer (on cross-connected VC L_T measurement point)
For each layer, a block of Non-OAM PM counters is available:
Layer Name Description Traffic TCA Purpose

Type
TP/VP_A INVHEC Number of invalid HEC events Any Y Maintenance
DISHEC Number of cells discarded due to invalid HEC event Y Maintenance
DISHVPIVCI Number of cells discarded due to invalid Header/VPI/VCI Y Maintenance
RXCELL Number of received cells N Maintenance
TXCELL Number of transmitted cells N Maintenance
VPL_T RXCELL Number of received cells (CLP0+1) Any N Connection monitoring

VCL_T TXCELL Number of transmitted cells (CLP0+1) N Connection monitoring
DISCELL Number of discarded cells (CLP0+1) N Connection monitoring
RXCELL0 Number of received cells (CLP0) SBR.2, N Connection monitoring
SBR.3,
TXCELL0 Number of transmitted cells (CLP0) or GFR N Connection monitoring
DISCELL0 Number of discarded cells (CLP0) SBR.2 N Connection monitoring
TAGCELL Number of tagged cells SBR.3, or N Connection monitoring
GFR
Figure 6-1 Available Non-OAM PM counters
3AG 86577 ABAA Ed3 522/725

6.1.2 OAM PM management

The OAM Performances, used to estimate the Quality of Service of PVCs, are
provided on two different layers:
− VP layer
Alcatel
− VC layer
The OAM PM can be applied on two kinds of measurement points of a segment:

− Endpoints of a Segment
− Surveillance Points, on cross-connected VPL_Ts/VCL_Ts of a Segment.
Potentially, there are two possible Surveillance Points by VPL_T/VCL_T:
. a Surveillance Point for the incoming (ingress) direction
. a Surveillance Point for the outgoing (egress) direction.
ATM NE Segment
ingress egress
ATM ATM
ingress NE
NE egress
egress
Cross-connected VPL_T/VCL_T : “After matrix” Surveillance point (i.e. outgoing)
Segment endpoint ingress : “Before matrix” Surveillance point (i.e. incoming)
- A segment can be the who le PVC (if the PVC has its extremit ies on ATM
NEs), or a portion of the PVC.
3AG 86577 ABAA Ed3 523/725

6.2 Managing PM Measures

Alcatel
Modify Measure
Create Measure
Delete Measure
Associate Transport Dissociate Transport
Associate
Performance Points
Activate Measure De-activate Measure
Figure 6-2 PM Measure chain
The procedure to manage Performance Monitoring in 1354 BM is the following:

− Create a PM Measure (from PM Measure List, refer to 6.2.1)
− Associate a Transport to the PM Measure (from PM Transport List, refer to
6.2.12)
− Associate Performance Points (PPs) to the PM Transport (from Performance
Point List, refer to 6.2.13)
− Activate the PM Measure to start the PM counters on the involved PPs (from
PM Measure List, refer to 6.2.1).
The term Transport refers to:

− a Transmission Path
− a PVC (Hard/Soft PVPC, Hard/Soft PVCC)
− a PVC Leg (Hard/Soft PVPC Leg, Hard/Soft PVCC Leg).
The term PM Transport refers to a Transport associated to a PM Measure.
3AG 86577 ABAA Ed3 524/725

A PM Measure can be associated to one or several Transports (Transmission Path,

Hard/Soft PVPC, Hard/Soft PVPC Leg, Hard/Soft PVCC, Hard/Soft PVCC Leg).
In each PM Transport, some Performance Points (PPs) can be inserted.
Those performance points (PPs) are the physical entities of the Transport on
which the measurement applies.
Alcatel
A given Transport can be associated to two PM Measures:

− one PM Measure with granularity 15 Min
− one PM Measure with granularity 24 H.
For Non-OAM PM, only one Leg of a given multi-points PVC can be associated
to a PM measure at a given time.
If a Leg of a PVC is associated to a PM Measure, no other Leg of this PVC can be

associated to a PM Measure.
This means that Non-OAM Performance PM cannot be managed on several Legs

of a given PVC at the same time.
Figure 6-3 PM Measure interdependencies
3AG 86577 ABAA Ed3 525/725

6.2.1 Display the PM Measure list

The PM Measure List window presents all the PM Measure managed (i.e. already
defined) by the 1354 BM, and their attributes.
From the Main view, menu: Performance => PM Measure

Alcatel
Figure 6-4 PM Measure List window
The attributes displayed for each PM Measure are:

− User Label
− Category
− Layer (Transmission Path, PVPC, PVCC, PVC)
− Granularity (15 Min, 24 H)
− PM Measure State (Planned, Active, Stopped, Stand-by)
− Activity State (None, Start in progress, Stop in progress)
For column description, refer to chapter Error! Reference source not found..

− User Label
− Category
− Layer
3AG 86577 ABAA Ed3 526/725


Alcatel
Figure 6-5 PM Measure Search window
3AG 86577 ABAA Ed3 527/725

From the PM Measure List window, you can:
Create PM Measure, refer to § 6.2.2
Modify PM Measure, refer to § 6.2.3

Alcatel
Delete PM Measure, refer to § 6.2.4
Associate a PM Measure to a Periodic Report Profile, refer to § 6.2.5
Dissociate a PM measure from a Periodic Report Profile, refer to § 6.2.6
Activate a PM Measure, refer to § 6.2.7
De-activate a PM Measure, refer to § 6.2.8
Force the Data Collection of a PM Measure, refer to § 6.2.9
Display the PM Measure properties, refer to § 6.2.10
Show Performance Data, refer to § 6.2.11
Display the PM Transport List, refer to § 6.2.12
3AG 86577 ABAA Ed3 528/725

6.2.2 Create a PM Measure

This function consists in defining a performance monitoring measure, for a given
granularity, for a given layer of transport, and for Non-OAM category of PM.
From the Main view, menu: Performance => PM Measure => Create
Alcatel
Figure 6-6 PM Measure Creation window
To create a PM Measure:
− Enter a PM Measure User Label
− Enter a Start Time (optional) (date/time syntax : yyyy mm dd hh mm ss)
− Enter a Stop Time (optional) (date/time syntax : yyyy mm dd hh mm ss)
− Choose a PM Layer (Transmission Path, PVPC, PVCC, PVC (i.e PVPC &
PVCC))
− Choose a Granularity (15 Min or 24 H)
Click on Ok.
3AG 86577 ABAA Ed3 529/725

The PM Measure is created with the following states:

− Operational state : Disabled until it has been associated to a Transport

− PM Measure state : Planned (= defined but never activated)
− Activity state : None
− Consistency state : Consistent
Alcatel
The PM Measure List is updated too.
Start and stop time management rules:
If start time is entered, the PM Measure will be activated automatically when the
start time is reached. But it can also be activated manually before the automatic
start occurs, or after the PM Measure stop.
If start time is not entered, the PM Measure can only be activated manually.
If stop time is entered, the PM Measure will be stopped automatically when the
stop time is reached. But it can also be stopped manually before the automatic
stop occurs.
If stop time is not entered, the PM Measure can only be stopped manually.
It is allowed to enter a start time without entering stop time. The PM Measure will
be activated automatically, but it shall be stopped manually.
It is allowed to enter a stop time without entering start time: the PM Measure shall
be started manually. If the manual start occurs before the stop time elapsed, the
PM Measure will be stopped automatically. If the manual start occurs after the
stop time elapsed, the automatic stop won’t occur, and the PM Measure shall be
stopped manually.
At the 1354 BM start-up, if some Stopped or Planned PM Measures have their

start time elapsed, these PM Measures are started, and warning messages are
logged.
At the 1354 BM start-up, if some active PM Measures have their stop time
elapsed, they are automatically stopped, and stop time is reset on these PM
Measures.
3AG 86577 ABAA Ed3 530/725

6.2.3 Modify a PM Measure

This function consists in modifying following parameters:
− PM Measure User Label
− Comment
Alcatel
− Start / Stop Time
- The PM Measure must be previously created and its Act ivit y state must be
None.
- The new PM Measure User Label must be different as one which is already
used by another PM Measure.
From the Main view, menu: Performance => PM Measure => select one PM
Measure in the list => Modify
This funct ion is available only if a PM Measure is selected.
Figure 6-7 PM Measure Modification window
3AG 86577 ABAA Ed3 531/725

To modify a PM Measure:
− Enter a New User Label (optional)

− Change the Start Time (optional)
− Change the Stop Time (optional)
Alcatel
If a New User Label is entered, the opened PM Measure List is updated.
3AG 86577 ABAA Ed3 532/725

6.2.4 Delete a PM Measure

This function consists in deleting a PM Measure from 1354 BM.
- This operation is allowed if the PM Measure contains no Transport

(operational state must be Disabled).
Alcatel
- This operation is prohibited if the measure is in Disabled operational state but

contains PM transports state in Deleted state.
From the Main view, menu: Performance => PM Measure => select one or
several PM Measures in the list => Delete
Figure 6-8 Confirmation box for deleting one PM Measure
Figure 6-9 Confirmation box for deleting several PM Measures
After confirmation, the PM Measure(s) is (are) removed from the PM Measure

List.
If the PM Measure(s) removed was (were) associated to one or several Periodic

Report Profiles, it is automatically dissociated from these Periodic Report
Profiles.
3AG 86577 ABAA Ed3 533/725

6.2.5 Associate a PM Measure to a Periodic Report Profile

This function is used when the operator wants to get generated PM Periodic
reports.
The association of a PM Measure to a Periodic Report Profile consists in

specifying the PM Measures that must be taken into account in the periodic report
Alcatel
generation.
The operator selects one or several PM Measures and selected the Periodic Report
Profile to associate.
A PM Measure could be associated to more than one Periodic Report Profile.
- At least, one Periodic Report Profile must be previously created.
- The PM Measure must match the Granularit y and the PM layer of the Periodic
Report Profile.
more PM Measures in the list => Associate to Report Profile
This funct ion is available only if, at least, a PM Measure is selected.
Figure 6-10 PM Measure / Report Profile association window
3AG 86577 ABAA Ed3 534/725


Alcatel
Figure 6-11 PM Measure / Report Profile association window (multi-selection)
To associate a PM Measure to a Report Profile:

− Choose a Report Profile User Label by using the sensitive help (only the not
already associated reports (with the same granularity and the same layer) are
displayed).
Click on Ok (or Yes or All) button.
The selected PM Measures are associated to the report profile.
Periodic reports will be generated at the required frequency, as soon as one PM

measure is activated.
If one PM measure is active at the association, the production of the report is

immediately enabled.
The report profile is updated with the following states:

− operational state : Enabled
− active state : Inactive or Active if at least, one measure is active.
3AG 86577 ABAA Ed3 535/725

6.2.6 Dissociate a PM Measure from a Periodic Report Profile

This function is used when the operator wants to modify the content of a PM
Periodic Report Profile, or when he wants to stop the generation of a PM Periodic
Report.
Alcatel
The operator selects one or several PM Measures and selected the Periodic Report
Profile to dissociate.
The dissociation is applicable for any PM measure state (i.e. Planned, Active or
Stopped). If the PM Measure is in Active state, the production of the report is
stopped for this PM Measure.
- At least, one Periodic Report Profile must be previously associated to the

selected PM Measure(s).
more PM Measures in the list => Dissociate from Report Profile
Figure 6-12 PM Measure / Report Profile dissociation window
Figure 6-13 PM Measure / Report Profile dissociation window (multi-selection)
To dissociate a PM Measure to a Report Profile:
3AG 86577 ABAA Ed3 536/725

− Choose a Report Profile User Label by using the sensitive help.

Sensitive help lists the reports used by the selected PM Measure.

Click on Ok button.
To dissociate several PM Measures to a Report Profile:

Alcatel
− Choose a Report Profile User Label Label by using the sensitive help.
Sensitive help lists all the existing reports even if they are not associated to a
PM Measure.
Click on Yes or All button.
The PM measure(s) is (are) dissociated from the report profile. No more periodic
report will be generated concerning this measure.
The report profile is updated with the following states:

− operational state : becomes Disabled if no more PM Measure is associated
to the report.
− active state : Inactive or Active if at least, one PM measure
associated to this report profile is active.
3AG 86577 ABAA Ed3 537/725

6.2.7 Activate a PM Measure

A PM Measure can become active when:
− Its start time is reached (automatic activation)
− The operator activates manually the PM Measure
Alcatel
This function is used when the operator wants to active manually a PM Measure.
This operation consists in starting the PM counters, for each involved PP

(Performance Point) of each PM Transport of the PM Measure.
- PM Measure can be act ivated if:

. its Operational state is Enabled (i.e. the PM Measure owns one or some PM
Transports)
. the PM transport(s) associated to the PM Measure is(are) at least
implemented (case hard PVC) or established (case soft PVC)
. its PM Measure state is Planned or Stopped
. its PM Measure state is Act ive and its Consistency state is equal to Not
Consistent. In this case, the activate command applies to the PPs which are
stopped and Not consistent.
more PM Measures in the list => Activate
Figure 6-14 Confirmation box for activating one PM Measure
3AG 86577 ABAA Ed3 538/725


Alcatel
Figure 6-15 Confirmation box for activating several PM Measures
The PM Measure Activity state takes the value 'Start in progress', waiting for the
end of counters activation.
When all operations are finished on all the PPs, the PM Measure is updated with
the following states:
− PM measure state : Active
The PM Transport state of each PM Transport becomes Active (if Transport is at
least implemented, established or configured) or Stand-by. If PM Transport List is
opened, it is updated.
The PP state of each PP becomes Active. If PP List (of the activated PM measure)
is opened, it is updated.
The Start Time of the PM Measure is updated with the date of manual activation.
The collect is automatically is launched by the 1353 NM, according to the

granularity of the PM Measure to collect.
The collect occurs at specific time, according to the periodicity of the collect. For
example, if 15 Min counters are collected every hour, and 24 H counters are
collected every day, the time of collect is:
− Granularity 15 Min : the collect occurs at 10h00 + delta, 11h00 + delta, …
− Granularity 24 H : the collect occurs at 00h00 + delta
Delta is a delay which allows the NE to end the storage of counters on the current
period into the history tables.
When the 1353 NM has finished the collect, it fills some export files with the
collected data.
The 1354 BM, by polling mechanism, get these files by FTP, and read their
content, which is stored in the 1354 BM database.
To display the PM counters, the operator has to launch PMDS application (refer to
§ 6.2.11).
3AG 86577 ABAA Ed3 539/725

6.2.8 De-activate a PM Measure

A PM Measure can become de-active when:
− Its stop time is reached (automatic de-activation)
− The operator de-activates manually the PM Measure
Alcatel
This function is used when the operator wants to de-active one or several PM
Measures (i.e. stop counters on the involved NE).
This operation consists in starting the PM counters, for each involved PP

(Performance Point) of each PM Transport of the PM.
- PM Measure could be de-act ivated if it s PM Measures state is Act ivated or if it

is Stopped and Consistency state equal to Not Consistent. In this case, the de-
activate command applies to the PPs which are st ill act ivated and Not
consistent.
more PM Measures in the list => Deactivate
Figure 6-16 Confirmation box for de-activating one PM Measure
Figure 6-17 Confirmation box for de-activating several PM Measures
3AG 86577 ABAA Ed3 540/725

The PM Measure Activity state takes the value 'Stop in progress', waiting for the
end of counters de-activation.
When all operations are finished on all the PPs, the PM Measure is updated with
the following states:
Alcatel
− PM measure state : Stopped
The PM Transport state of each PM Transport becomes Stopped. If PM Transport

List is opened, it is updated.
The PP state of each PP becomes Stopped. If PP List (of the activated PM

measure) is opened, it is updated.
The Stop Time of the PM Measure is updated with the date of manual de-
activation.
3AG 86577 ABAA Ed3 541/725

6.2.9 Force a data collection

This function is used when the operator wants to force the data collection on one
or several PM Measures in order to visualize the PM history data of the PM
measures, which have not been collected yet, and does not want to wait for the
automatic periodic collect timeout.
Alcatel
This operation is applicable only to PM Measures with granularity 15 mn.
- PM Measure must be activated or stopped.
- Operational State of PM Measure must be enabled (i.e. the PM Measure owns

some PM Transports).
more PM Measures in the list => Force Data Collection
Figure 6-18 Confirmation box for force data collection on one PM

Measure
Figure 6-19 Confirmation box for force data collection on several PM

Measures
3AG 86577 ABAA Ed3 542/725

6.2.10 Display the PM Measure properties

This function consists in displaying information about a PM Measure.
From the Main view, menu: Performance => PM Measure => select a PM
Measures in the list => Properties
Alcatel
Figure 6-20 PM Measure Properties window
Start Time and/or Stop Time field(s) not filled ('-' value), means that they have not
been filled at the creation of the PM Measure.
The last two fields give information about the last action performed on the PM
Measure.
3AG 86577 ABAA Ed3 543/725

6.2.11 Show performance data

This functionality, available from the PM Measure List and from the PM
Transport List, is to be used when an operator wants to display the PM Measure
counter.
Alcatel
Measure in the list => Show Performance Data
From the PM Measure List:
Figure 6-21 Confirmation box to navigate towards PMDS (from PM Measure List)
From the PM Transport List:
Figure 6-22 Confirmation box to navigate towards PMDS (from PM Transport List)
See chapter 2.2.4 for more information on PMDS component.
3AG 86577 ABAA Ed3 544/725

6.2.12 Display the PM Transport list

This PM Transport List window presents all the Transports associated to a PM
Measure.
- The term Transport refers to:

Alcatel
. a Transmissio n Path
. a PVC (Hard/Soft PVPC, Hard/Soft PVCC)
. a PVC Leg (Hard/Soft PVPC Leg, Hard/Soft PVCC Leg).
- The term PM Transport refers to a Transport associated to a PM Measure.
Measure in the list => PM Transport List
This funct ion is available only if a PM Measure is selected.
Seven different PM Transport lists could be displayed.
The Type column could be Transmission Path, Hard / Soft PVPC, Hard / Soft
PVCC, VPC Leg, VCC Leg and depends on the Layer value of the selected PM
Measure.
Figure 6-23 PM Transport List window (if PM Measure Layer is Transmission

Path)
3AG 86577 ABAA Ed3 545/725

The attributes displayed for each PM Transport are:

− User Label
− Type (Transmission Path,Hard PVPC, Hard PVCC, Soft PVPC, Soft PVCC,
PVPC Leg, PVCC Leg)
− PM Transport State (Planned, Deleted, Active, Stand-by)
Alcatel

For column description, refer to chapter Error! Reference source not found.

− User Label
− Type
Figure 6-24 PM Transport Search window
From the PM Transport List window, you can:
Associate a PM transport to a PM Measure, refer to § 6.2.12.1
Dissociate a PM transport, refer to § 6.2.12.2
Display the Performance Points List, refer to § 6.2.13
Show Performance Data, refer to § 6.2.11
3AG 86577 ABAA Ed3 546/725

6.2.12.1 Associate a PM Transport to a PM Measure

This function consists in association of one or several transports to a PM Measure.
A transport can be associated at most to two different PM Measures:

− one PM Measure with granularity 15 Min
Alcatel
− one PM Measure with granularity 24 H.
- If the chosen transport is:
. a Hard PVC, it must be at least allocated
. a Soft PVC, it must be established.
- The PM Measure must not be in the Active state.
Measure in the list => PM Transport List => Associate
This funct ion is available only if no PM Transport is selected.
The content of the displayed PM Transport Association window depends on the

Layer value of the PM Measure.
Four different windows could be displayed (see the description of the four cases
in the following pages).
3AG 86577 ABAA Ed3 547/725

The 1354 BM inserts automatically the following default Performance Points

(PPs) in the PM Transport:

Case Transmission Path: Each TP/VP_A becomes a PP.
ATM NE ATM NE ATM NE

Alcatel
TransPath TransPath ENE
Default PP
Default PPs
Case Hard PVPC or Hard PVCC or Leg: The first VPL_Ts/VCL_Ts adjacent to
endpoints become PPs.
Hard VPC or Hard VCC or Leg

ATM NE ATM NE ATM NE ATM NE
or ENE or ENE or ENE or ENE
Default PPs Default PPs
Case Soft PVPC or Soft PVCC: The first VPL_Ts/VCL_Ts adjacent to endpoints
become PPs.
Soft PVC route
Hybrid Hard PVC route Soft VPC or VCC with unitary hard PVCs at extremities

or ENE ENE
or ENE or ENE
Called
Endpoint
Default PPs: Calling endpoint and Called endpoint
Default PP: Calling Endpoint
Soft VPC or VCC with non-unitary hard PVCs at extremities
ATM NE
ATM NE
or ENE ATM NE ATM NE ENE
or ENE or ENE
ATM NE Called
Default PP Endpoint
Default PPs
3AG 86577 ABAA Ed3 548/725

Case 1: Transport is a Transmission Path


Alcatel
Figure 6-25 PM Transport Association window (PM Measure Layer is Transmission Path)
Choose the Transmission Path User Label by using the sensitive help.
The authorised Transmission Paths are displayed.
Click on Ok button to associate the selected transmission path to the PM Measure.
3AG 86577 ABAA Ed3 549/725

Case 2: Transport is a PVPC


Alcatel
Figure 6-26 PM Transport Association window (PM Measure Layer is PVPC)
Tick the wished Transport Type (Hard PVPC, Soft PVPC or PVPC Leg).
Choose the PVPC User Label by using the sensitive help. If Transport Type is:
− Hard PVPC, only the not unitaries point-to-point Hard PVPCs at least allocated
are displayed.
− Soft PVPC, only the Soft PVPCs established are displayed.
− PVPC Leg, only the not unitaries point-to-point Hard PVPCs at least allocated
are displayed. Choose also the PVPC Leg User Label by using the help
sensitive. Only the PVPC Legs at least allocated are displayed.
If a Hard PVPC Leg is already associated to this PM Measure, the

corresponding Hard PVPC will not appear in the sensit ive help of the
PVPC User Label fie ld.
Click on Ok button to associate the selected PVPC to the PM Measure.
3AG 86577 ABAA Ed3 550/725

Case 3: Transport is a PVCC


Alcatel
Figure 6-27 PM Transport Association window (PM Measure Layer is PVCC)
Tick the wished Transport Type (Hard PVCC, Soft PVCC or PVCC Leg)
Choose the PVCC User Label by using the sensitive help. If the Transport Type
is:
− Hard PVCC, only the not unitaries point-to-point Hard PVCCs at least
allocated are displayed.
− Soft PVCC, only the Soft PVCCs established are displayed.
− PVCC Leg, only the not unitaries point-to-point Hard PVCCs at least allocated
are displayed. Choose also the PVCC Leg User Label by using the help
sensitive. Only the PVCC Legs at least allocated are displayed.
If a Hard PVCC Leg is already associated to this PM Measure, the

corresponding Hard PVCC will not appear in the sensit ive help of the
PVCC User Label field.
Click on Ok button to associate the selected PVCC to the PM Measure.
3AG 86577 ABAA Ed3 551/725

Case 4: Transport is a PVC


Alcatel
Figure 6-28 PM Transport Association window (PM Measure Layer is PVC)
Tick the wished Transport Type (Hard PVPC or PVCC, Soft PVPC or PVCC,
PVPC or PVCC Leg)
Choose the PVC User Label by using the sensitive help. If the Transport Type is:
− Hard PVPC, only the not unitaries point-to-point Hard PVPCs at least allocated
are displayed.
− Hard PVCC, only the not unitaries point-to-point Hard PVCCs at least
allocated are displayed.
− Soft PVPC, only the Soft PVPCs established are displayed.
− Soft PVCC, only the Soft PVCCs established are displayed.
− PVPC Leg, only the not unitaries point-to-point Hard PVPCs at least allocated
are displayed. Choose also the PVC Leg User Label by using the help
sensitive. Only the PVC Legs at least allocated are displayed.
− PVCC Leg, only the not unitaries point-to-point Hard PVCCs at least allocated
are displayed. Choose also the PVC Leg User Label by using the help
sensitive. Only the PVC Legs at least allocated are displayed.
Click on Ok button to associate the selected PVC to the PM Measure.
For all the cases, when all operations are finished, the transport is associated to the
PM Measure and the following state are updated:
− PM Measure operational state : Enabled
− PM Transport state : takes the same value as the PM Measure
tate (Planned or Stopped)
The PM Measure List and PM Transport List are updated too.
3AG 86577 ABAA Ed3 552/725

6.2.12.2 Dissociate a PM Transport

This function consists in dissociating PM Transports from a PM Measure.
- The Operational state of the PM Measure must be Enabled (i.e. the PM

Measure owns at least one PM Transport).
Alcatel
- The PM Transport state must not be Deleted (i.e a delet ion request is already
on going).
Measure in the list => PM Transport List => select one or more PM Transports
in the list => Dissociate
Figure 6-29 Confirmation box for dissociate one PM Transport
Figure 6-30 Confirmation box for dissociate several PM Transports
After confirmation, if the PM Measure state of the PM Measure is in Active, the

dissociation is accepted and the PM is stopped on the selected PM Transport(s).
The PM Transport state becomes Deleted until 1354 BM received all the stopped
counter notifications.
The PM Transport(s) (and all associated PPs) is (are) deleted from the PM
Measure. All the archived counters of the involved PPs are removed from the
database (i.e. history of PM counters are lost).
Then, the PM Transport(s) is (are) removed from the PM Transport List.

A dissociated PM Transport is still considered to be associated with a measure
until all stopped counter notifications have been received correctly.
3AG 86577 ABAA Ed3 553/725

6.2.13 Display the PP List

For a selected PM Measure and PM Transport, this list presents all the
performance points (including those by default) which can be associated to a PM
Transport.
Alcatel
The content of the displayed PP List depends on the PM Transport Type of the
PM Measure.
Measure in the list => PM Transport List => select one PM Transport in the list
=> PP List
Figure 6-31 PP List for a PM measure with Transport Type = Transmission Path (between two
NEs)
No command is available fro m this previous list.
Figure 6-32 PP List for a PM measure with Transport Type = Hard

PVPC
3AG 86577 ABAA Ed3 554/725


Alcatel
Figure 6-33 PP List for a PM measure with Transport Type = Hard PVCC
The attributes displayed for each PM Measure in PP List are:

− NE User Label
− Termination Id.
− VPI ("-"value if not significant)
− VCI ("-"value if not significant)
− Type (Tpvpa, pc, vc)
− OAM Direction
− Activity State
− PP State (Planned, Active, Stopped, Stand-by)
− Default PP (True, False)
− Association State (Associated, Dissociated)

− NE User Label
− Association State
3AG 86577 ABAA Ed3 555/725

Alcatel
Figure 6-34 PP Search window
From the PP List window, you can:
Associate, refer to § 6.2.13.1
Dissociate, refer to § 6.2.13.2
3AG 86577 ABAA Ed3 556/725

6.2.13.1 Associate a PP to a PM transport

This function consists in association of one or several Performance Points (PPs) to
a PM Transport.
- This funct ion is not applicable to a PM Measure wit h Transmissio n Path layer,
Alcatel
because TP/VP_As are default PPs (i.e. they are always associated to the PM
Transport by default).
- No operation in progress on the PM Measure. Activit y state of the PM
Measure must be None.
- The PM transport state of the selected PM transport must not be Deleted (i.e.
in a delet ing (from a PM Measure) phase).
Measure in the list => PM Transport List => select one PM transport in the list
=> PP List => select one or more PPs in the list => Associate
Figure 6-35 Confirmation box for associate one PP to a PM transport
Figure 6-36 Confirmation box for associate several PP to a PM transport
After confirmation, the PP(s) is (are) associated to the PM Transport.
The operation is allowed even if the PM Measure is in the Active PM Measure

state. In this case, the PM counters are implicitly started on the new PP.
The PP State of the PP(s) takes the same value as the PM Transport State
(Planned, Active, Stopped or Stand-by).
3AG 86577 ABAA Ed3 557/725

6.2.13.2 Dissociate a PP from a PM transport

This function allows to the operator to dissociate one or several Performance

Points (PPs) to a PM Transport.
- This funct ion is not applicable to a PM Measure wit h Transmissio n Path layer,
because TP/VP_As are default PPs (i.e. they are always associated to the PM
Alcatel
Transport by default).
- The PP must be associated to the PM transport.
- The PP must not be a default PP.
- No operation in progress on the PM Measure. Activit y state of the PM
Measure must be None and PM Measure state is not active.
Measure in the list => PM Transport List => select one PM transport in the list
=> PP List => select one or more PPs in the list => Dissociate
Figure 6-37 Confirmation box for dissociate one PP from a PM transport
Figure 6-38 Confirmation box for dissociate several PP from a PM transport
After confirmation, the PP(s) is (are) dissociated from the PM Transport.
The PP State of the PP(s) takes the same value as the PM Transport State
(Planned, Active, Stopped or Stand-by).
3AG 86577 ABAA Ed3 558/725

6.3 Managing Periodic Report Profiles
Periodic Report Profiles allow to generate automatically some PM results in

periodic report on different outputs (printer, file and mail).
These Periodic Report Profiles are created from the 1354 BM application, and the
Alcatel
periodic generation of the reports (related to these profiles) is provided by the

component PMDS.
The following PM Periodic Report Profiles are managed:

− Periodic Counters reports: they contain collected information on counters.
− Periodic Parameters (Ratios) reports: they contain ratios computed with
collected counters. (*)
− Periodic Threshold Counters reports: they contain collected information on
counters that exceed some user’s defined thresholds.
− Periodic Threshold Parameters (Ratios) reports: they contain ratios computed
with collected counters, exceeding some user’s defined thresholds. (*)
− Periodic Transport State reports: they contain state transitions history during
the observation period. The 1354 BM will handle provisioning state
(Allocated, Implemented and Commissioned) and availability status (Normal,
Degraded and In Failure).
(*) Not available in R7.
3AG 86577 ABAA Ed3 559/725

6.3.1 Display the Periodic Report Profile list

The Periodic Report Profile List window presents all the reports profiles and their
attributes.
Alcatel
From the Main view, menu: Performance => Periodic Report Profile
Figure 6-39 Periodic Report Profile List window
The attributes displayed for each Periodic Report Profile List are:
− User Label
− Frequency
− Kind
− Active State
− Layer
− Granularity

− User Label
3AG 86577 ABAA Ed3 560/725


Alcatel
Figure 6-40 Periodic Report Profile Search window
From the Periodic Report Profile List window, you can:
Create a Periodic Report Profile, refer to § 6.3.2
Modify a Periodic Report Profile, refer to § 6.3.3
Delete a Periodic Report Profile, refer to § 6.3.4
Display the Periodic Report Profile properties, refer to § 6.3.5
3AG 86577 ABAA Ed3 561/725

6.3.2 Create a Periodic Report Profile

This function allows to define Periodic Report Profile of performance counters
(based on thresholds or not) or Transport state. These periodic report profiles
allow to generate PM results in periodic reports.
Alcatel
From the Main view, menu: Performance => Periodic Report Profile =>
Create
Figure 6-41 Periodic Report Profile creation window (Report Kind =

Counter)
To create a Periodic Report Profile:

− Enter a Periodic Report Profile User Label
− In the Characteristics area, choose the Report Kind (Counter, Counter
Threshold or Transport state)
Following the Report Kind selected, the fields to be entered are not the same, see
hereafter the different proposed windows:
3AG 86577 ABAA Ed3 562/725


Alcatel
Figure 6-42 Periodic Report Profile creation window (Report Kind = Transport State)
Figure 6-43 Periodic Report Profile creation window (Report Kind = Counter
Threshold)
3AG 86577 ABAA Ed3 563/725

− If Transport State value is selected in Report Kind field, choose the State
Report Type. This option allows to get periodic report on transport state
transition based on Provisioning State, Availability Status or both.
− Choose the PM Layer (Transmission Path, PVPC, PVCC, PVC (=PVPC &
PVCC))
− Choose the Granularity (15 Min or 24 H)
Alcatel
− Choose the PM Frequency (depends of the choosen granularity value).

Frequency of a periodic report must be equal or greater than the value of the
granularity, so that the report contains information of at least one period.
Granularity Frequency
15 Min 15 Min / 1 Hour / 2 Hours / 1 Day
24 H 1 Day / 1 Week / 1 Month / 2 Months / 1 Year
− Choose the Output Type (mail, printer or file)

− Choose the Output Name (mail address, printer name or file name)
− Enter the PM Threshold Values (if the choosen Report Kind is Counter
Threshold)
Click on Ok.
The Periodic Report Profile is created with the following states:

− operational state : Disabled (= no associated PM Measure)
− active state : None
The Periodic Report Profile List is updated too.
3AG 86577 ABAA Ed3 564/725

6.3.3 Modify a Periodic Report Profile

This function consists in modifying some characteristics of a Periodic Report
Profile:
− Periodic Report Profile User Label
Alcatel
− Comment
− PM Frequency
− Output Type
− Output Name
- The new Periodic Report Profile User Label must be different as one which is
already used by another Periodic Report Profile.
From the Main view, menu: Performance => Periodic Report Profile => select
one Periodic Report Profile in the list => Modify
This funct ion is available only if a Periodic Report Profile is selected.
Figure 6-44 Periodic Report Profile modification window
3AG 86577 ABAA Ed3 565/725

To modify a Periodic Report Profile:

− Enter a New User Label (optional)

− Change the PM Frequency (optional)
− Change the Output Type (optional)
Alcatel
− Change the Output Name (optional)
If a New User Label is entered, the Periodic Report Profile List is updated.
3AG 86577 ABAA Ed3 566/725

6.3.4 Delete a Periodic Report Profile

This function consists in deleting one or several Periodic Reports Profiles.
- The Periodic Report Profile must be empt y (not associated to any measure).
Alcatel
From the Main view, menu: Performance => Periodic Report Profile => select
one or several Periodic Report Profile in the list => Delete
This funct ion is available only if at least one Periodic Report Profile is selected.
Figure 6-45 Confirmation box for deleting one Report Profile
Figure 6-46 Confirmation box for deleting several Reports Profiles
After confirmation, the Report Profile is deleted.
The Periodic Report Profile List is updated.
3AG 86577 ABAA Ed3 567/725

6.3.5 Display the Periodic Report Profile properties

This function consists in displaying information about a Periodic Report Profile.
From the Main view, menu: Performance => Periodic Report Profile => select a
Periodic Report Profile in the list => Properties
Alcatel
Figure 6-47 Periodic Report Profile Properties window (Report Kind = Counter)
Figure 6-48 Periodic Report Profile Properties window (Report Kind = Transport State)
3AG 86577 ABAA Ed3 568/725

Alcatel
3AG 86577 ABAA Ed3

Figure 6-49 Periodic Report Profile Properties window (Report Kind = Counter Threshold)
569/725
6.4 Managing TCA Profiles
The thresholds of the PM Counters may be set or modified.
When a threshold is crossed, an alarm event report is sent. This alarm is called
TCA (Threshold Crossing Alarm).
Alcatel
For Non-OAM PM management, the TCA profiles are available only on the
TP/VP_A layer.
The TCA profile defines the thresholds for each counter available at the TP/VP_A
layer, on which TCA is supported (see Figure 6-1 Available Non-OAM PM
counters, column TCA).
The ATM NE provides a set of 12 default TCA profiles (one per granularity and
per bit rate).
The 1354 BM provides to the operator 12 pre-defined profiles. They are

configured at the installation, and their content can be displayed but not modified
or deleted.
Each TCA profile are created with the following parameters:

− TCA profile user label
− PM category : NON-OAM
− PM Layer : Transmission Path
− Granularity : 15 Min or 24 H
− Bit rate : VC4-4C, VC-4, VC-3, VC-12, 2 Mb/s, 34 Mb/s
− For each counter on which TCA is settable:
− Low threshold value
− High threshold value.
3AG 86577 ABAA Ed3 570/725

6.4.1 Display the TCA Profile list

The TCA Profile List window presents all the TCA profiles and their attributes.
From the Main view, menu: Performance => TCA Profile

Alcatel
Figure 6-50 TCA Profile List window
The attributes displayed for each TCA profile are:

− User Label
− Granularity
− Bit Rate

− User Label
− Granularity
− Bit Rate
From the TCA Profile List window, you can:
Display the TCA Profile properties, refer to § 6.4.2
3AG 86577 ABAA Ed3 571/725

6.4.2 Display the TCA Profile properties

This function consists in displaying information about a TCA Profile.
From the Main view, menu: Performance => TCA Profile => select a TCA
Profile in the list => Properties
Alcatel
Figure 6-51 TCA Profile Properties window
3AG 86577 ABAA Ed3 572/725

Alcatel
3AG 86577 ABAA Ed3

573/725
7 Administration Management

Alcatel
7 Administration management
This chapter deals with the administration

services offered by the 1354 BM.
7.1 PNNI management
7.2 ATM traffic contract profile management
7.3 Operator profile management
3AG 86577 ABAA Ed3 574/725

7.1 PNNI management
The PNNI management, part of the administration management, consists in:

− configuring node ATM addresses
Alcatel
− activating / deactivating nodes

− configuring interface ATM addresses
− displaying administration information such as:
− NE list
− NE counter observation
− termination list
The PNNI management chain gives the order in which the available actions may
be performed.
Define NE
Define terminations Configure terminations
Network construction
(refer to chapter 3)
Configure PNNI node

ATM address
Activate Deactivate
PNNI node PNNI node
Configure PNNI interface

ATM address
Figure 7-1 PNNI management chain
For managing PNNI, you can:

display the NE list for administration, refer to § 7.1.1
3AG 86577 ABAA Ed3 575/725

7.1.1 Display the NE list for administration

The NE List (Administration) window presents all the NEs managed (i.e. already
defined) by the 1354 BM, and their attributes.
From the Main view, menu: Administration => PNNI

Alcatel
Figure 7-2 NE List (Administration) window

− User Label
− Type
− Version
− ATM Address
− PNNI Node State
3AG 86577 ABAA Ed3 576/725


− User Label
Alcatel
Figure 7-3 NE Search (Administration) window
From the NE List (Administration) window, you can:
observe a NE, refer to § 7.1.2
configure the PNNI node ATM address, refer to § 7.1.3
activate a PNNI node, refer to § 7.1.4
deactivate a PNNI node, refer to § 7.1.5
display the termination list for administration, refer to § 7.1.6
3AG 86577 ABAA Ed3 577/725

7.1.2 Observe a NE
This function consists in getting information about a NE in order to administer it.
From the Main view, menu: Administration => PNNI => select an NE in the list
=> Observe
Alcatel
Figure 7-4 NE Observation window
The last four fields give the states of NE counters that have been retrieved during
the last upload (whose date is also displayed). They allow the user to know how
many hard or soft connections can still be used.
The Maximum Connections value includes PVPC/PVCC cross-connections and

end-connections.
The maximum number of hard connect ions is equal to the Maximum Connect ions
value minus the Maximum Soft Connect ions value.
The Maximum Soft Connections value by default is null. To modify it:

− Enter a new value.
− Click on Ok.
3AG 86577 ABAA Ed3 578/725

7.1.3 Configure the PNNI node ATM address

This function consists in giving an ATM address to a NE, so that it can be used as
a PNNI node by soft PVCs, after being activated (refer to § 7.1.4).
- The PNNI node state of the NE must be Disabled.

Alcatel
- Act ivit y state of the NE must be None (= no audit/alignment or

=> Configure
Figure 7-5 PNNI Node ATM Address Configuration window
To configure the PNNI node ATM address:

− Enter the ATM Address: two formats are available (DCC/ICD, Generic).
− Click on Ok.
The NE is dedicated to the PNNI management.
The NE List (Administration) window is updated.
Once the PNNI node ATM address is configured, do not forget to activate the
PNNI node (refer to § 7.1.4) so that it can be used by soft PVCs.
3AG 86577 ABAA Ed3 579/725

7.1.4 Activate a PNNI node

This function consists in enabling a PNNI node to be used by soft PVCs.
- The PNNI node state of the NE must be Disabled.

Alcatel
- The PNNI node ATM address must be configured.

From the Main view, menu: Administration => PNNI => select one or several
NEs in the list => Activate
Figure 7-6 Confirmation box for activating one PNNI node
Figure 7-7 Confirmation box for activating several PNNI nodes
After confirmation, the PNNI nodes are activated.
Their PNNI node states change to Enabled.
The NE List (Administration) window is updated.
3AG 86577 ABAA Ed3 580/725

7.1.5 Deactivate a PNNI node

This function consists in deactivating a previously activated PNNI node.
- The PNNI node state of the NE must be Enabled.

Alcatel

From the Main view, menu: Administration => PNNI => select one or several
NEs in the list => Deactivate
Figure 7-8 Confirmation box for deactivating one PNNI node
Figure 7-9 Confirmation box for deactivating several PNNI nodes
After confirmation, the PNNI nodes are deactivated.
Their PNNI node states change to Disabled.
The NE List (Administration and Construction) windows are updated.
Now, the PNNI node ATM addresses can be modified (refer to §7.1.2).
3AG 86577 ABAA Ed3 581/725

7.1.6 Display the termination list for administration

The Terminations List (Administration) window presents all the NE terminations

and their attributes.
=> Term. List
Alcatel
Figure 7-10 Termination List (Administration) window
The attributes displayed for each termination are:

− Id.
− Technology
− Bit Rate
− ATM address
3AG 86577 ABAA Ed3 582/725

− Id.
− Technology

Alcatel
Figure 7-11 Termination Search (Administration) window
From the Terminat ion List (Administration) window, you can:
configure the PNNI interface ATM address, refer to § 7.1.7
3AG 86577 ABAA Ed3 583/725

7.1.7 Configure the PNNI interface ATM address

This function consists in giving an ATM address to a termination, so that soft
PVCs can use it as a PNNI interface.
- The terminat ion must be defined (or configured if it is not managed by the
Alcatel
RM).

=> Term. List => select a terminat ion in the list => Configure
Figure 7-12 PNNI Interface ATM Address Configuration window
To configure the PNNI interface ATM address:

− Enter the ATM Address on twenty bytes (last byte corresponding to selector
must be equal to ‘00’).
Three formats are available (DCC, ICD, E.164) (see the Figure 7-13 Three
ways of encoding ATM Address)
− Click on Ok.
3AG 86577 ABAA Ed3 584/725


Alcatel
Figure 7-13 Three ways of encoding ATM Address
Then, the NE is dedicated to the PNNI management.
The Termination List (Administration and Construction) windows are updated.
Once the PNNI interface ATM address is configured, do not forget to activate a
PNNI node so that it can be used by so ft PVC.
The configurat ion with an empt y ATM address will remo ve the ATM address
associated to the termination.
3AG 86577 ABAA Ed3 585/725

7.2 ATM traffic management
The management of the ATM traffic is divided into two parts:

− the traffic descriptor management
− the traffic profile management
Alcatel
The traffic descriptors are applied to a traffic contract type and the associated
traffic parameters that have been negotiated.
A traffic profile is defined by:

− a service type and its associated description
− transmission mode parameters (direction, allocation type, re-routing)
− traffic descriptors
Traffic profiles are useful to simplify the PVC designing operations by hiding the
traffic descriptor aspect.
In the equipment, the traffic descriptors of the connections are associated to an

index. This index will be known by the 1354 BM and used like reference of traffic
descriptors.
The number of traffic descriptors is limited in the equipment (refer to § 10.1).
Because of this limitation, the number of traffic descriptors is limited in the

profile management (limitation defined by a configurable value).
As the traffic profile will be able to be used for the hard and so ft PVC definit io n,
the informat ion like allocat ion type will not be defined at the creation of the traffic
profile but at the PVC definit ion.
1354 BM applicat ion provides pre-fixed traffic descriptors and traffic profiles.
7.2.1 Traffic descriptor management

The traffic descriptor management allows the user to create, modify and delete
traffic descriptors.
As long as a traffic descriptor is used by at least one PVC, it cannot be deleted.
At the 1354 BM installation, some traffic descriptors are pre-defined in its

database.
3AG 86577 ABAA Ed3 586/725

They can be modified or deleted (excepted that contains any characteristic (no
PCR, no MCR, no CDVT …), not frame based and used by the specific traffic
profile which allows to define a flexible unitary hard PVPC).
Alcatel
For managing traffic descriptors, you can:
display the traffic descriptor list, refer to § 7.2.1.1
3AG 86577 ABAA Ed3 587/725

7.2.1.1 Display the traffic descriptor list

The Traffic Descriptor List window presents all the traffic descriptors and their
attributes.
Alcatel
From the Main view, menu: Administration => Traffic => Traffic descriptors
Figure 7-14 Traffic Descriptor List window
The attributes displayed for each traffic descriptor are:

− User Label
− Comment
− PCR
− CDVT PCR
− MCR
− CDVT MCR
− MBS
− MFS
− Frame Based
3AG 86577 ABAA Ed3 588/725


− User Label
Alcatel
command , refer to § 2.1.4.
Figure 7-15 Traffic Descriptor Search window
From the Traffic Descriptor List window, you can:
create a traffic descriptor, refer to § 7.2.1.2
create a traffic descriptor from another one, refer to § 7.2.1.3
modify a traffic descriptor, refer to § 7.2.1.4
delete a traffic descriptor, refer to § 7.2.1.5
3AG 86577 ABAA Ed3 589/725

7.2.1.2 Create a traffic descriptor

This function consists in defining a traffic descriptor that will be used in traffic
profiles.
- The maximum number of traffic descriptors must not be reached.

Alcatel
- The traffic contract, the PCR value and the CDVT PCR value of the new traffic
descriptor must be different fro m those of an already exist ing traffic
descriptor.
- The CDVT must be greater than the time arrival 1/PCR
From the Main view, menu: Administration => Traffic => Traffic Descriptors
=> Create
command , refer to § 2.1.4.
Figure 7-16 Traffic Descriptor Creation window
3AG 86577 ABAA Ed3 590/725

To create a traffic descriptor:

− Enter a Traffic Descriptor User Label

− Choose a Traffic Contract by using the option button:
− DBR (Deterministic Bit Rate) Class 1, Class 2 or Class U:
Constant bit rate with time reference.
Alcatel
Used for the voice, video and DSL transfers.

Also called CBR (Constant Bit Rate) for DBR Class1 and DBR Class2
or UBR (Unspecified Bit Rate) for DBR ClassU, by the ATM Forum.
− GFR.2 (Guaranteed Frame Rate):
One part with a guaranteed bandwidth measured in frame per second,
another part called Best Effort.
Used for the data transfer.
− UBR+:
UBR with a Minimum desired Cell Rate.
Designed for providing Minimum Rate guarantees to the ATM
Unspecific Bit Rate Service and improving performance of TCP over
ATM_UBR service.
− SBR.1 Class1, SBR.1 Class 2, SBR.2 Class 3, SBR.3 Class3 (Statistic
Bit Rate):
Variable bit rate without time reference.
Used for the file transfer.
Also called VBR (Variable Bit Rate) by the ATM Forum.
The parameters defining a Traffic Contract in the 1354 BM are:

ATC (ATM layer Transfer Capabilit y)
QoS (Qualit y of Service)
Authorized only for VCC level and only for DBR Class U (UBR.1 and UBR.2)
and UBR+ traffic contracts, tick the Frame Based box if the user wish to use
the ATM frame based mechanism.
GFR.2 traffic contract is always Frame Based
Enter a Comment (optional)
3AG 86577 ABAA Ed3 591/725

In the Traffic Descriptor area, enter the required parameters.

The number of parameters to enter depends on the traffic contract previously

chosen. The fields to be filled in are white (see values range in chapter 10.1 -
Limits):
− PCR
Alcatel
− CDVT PCR
− MCR : value must be lower than PCR
− SCR : value must be lower than PCR
− MBS
− MFS
Click on Ok.
The traffic descriptor is created.
The Traffic Descriptor List window is updated.
3AG 86577 ABAA Ed3 592/725

7.2.1.3 Create a traffic descriptor from another one

This function consists in defining a traffic descriptor from another one that
already exists, in order to reduce the number of data to be keyboarded.
- The maximum number of traffic descriptors must not be reached.

Alcatel
- The traffic contract, the PCR value and the CDVT PCR value of the new traffic
descriptor must be different fro m those of an already exist ing traffic
descriptor.
=> select a traffic descriptor in the list => Create From
Figure 7-17 Traffic Descriptor Creation window
The fields are already filled in with the values of the selected traffic descriptor.
To create the new traffic descriptor:
− Enter a new Traffic Descriptor User Label
− Possibly modify one or several parameters (for more details, refer to §7.2.1.2)
− Click on Ok.
The new traffic descriptor is created
3AG 86577 ABAA Ed3 593/725

7.2.1.4 Modify a traffic descriptor
This function consists in modifying one or several parameters of a traffic

descriptor.
Alcatel
- The traffic descriptor "TD_FOR_FLEXIBLE_HARD_VPC" used for define

flexible VPs can't be modified.
=> select a traffic descriptor in the list => Modify
Figure 7-18 Traffic Descriptor Modification window
The fields are already filled in with the values of the selected traffic profile.
To modify the traffic profile:

− Modify the Traffic Descriptor User Label or the Comment.
− Click on Ok.
The traffic descriptor is modified.
The traffic Descriptor List window is updated.
3AG 86577 ABAA Ed3 594/725

7.2.1.5 Delete a traffic descriptor

This function consists in deleting a traffic descriptor from the 1354 BM.
- The traffic descriptor to be deleted must not be used in a traffic profile or by a

PVC.
Alcatel
- The traffic descriptor "TD_FOR_FLEXIBLE_HARD_VPC" used for define

flexible VPs can't be deleted.
=> select a traffic descriptor in the list => Delete
Figure 7-19 Confirmation box for deleting one traffic descriptor
Figure 7-20 Confirmation box for deleting several traffic descriptors
After confirmation, the traffic descriptors are deleted.
7.2.2 Traffic profile management

The traffic profile management allows the user to create, modify and delete traffic
profiles.
3AG 86577 ABAA Ed3 595/725

It is independent of the PVC management (refer to chapter 4). Actually, a traffic

profile provides a support for the PVC definition. As soon as a PVC is defined, it
uses only its own traffic descriptors that cannot be modified or deleted.
It is why the traffic profiles can be modified or deleted without any impact on the
PVCs.
Alcatel
The association of a service type and a description identifies a traffic profile.
At the 1354 BM installation, some traffic profiles are pre-defined in its database.
They can be modified or deleted (excepted that used for define a flexible unitary
hard PVPC).
The traffic profile "FLEXIBLE" can be used only for unitary hard PVPC.
For managing traffic profiles, you can:
display the traffic profile list, refer to § 7.2.2.1
3AG 86577 ABAA Ed3 596/725

7.2.2.1 Traffic profile list

The Traffic Profile List window presents all the traffic profiles and their
attributes.
From the Main view, menu: Administration => Traffic => Traffic Profile
Alcatel
Figure 7-21 Traffic Profile List window
The attributes displayed for each traffic profile are:

− Service Type
− Description
− Comment
− Forward Traffic Descriptor User Label
− Backward Traffic Descriptor User Label

− Service Type
− Description
3AG 86577 ABAA Ed3 597/725

Alcatel
Figure 7-22 Traffic Profile Search window
From the Traffic Profile List window, you can:
create a traffic profile, refer to 7.2.2.2
create a traffic profile from another one, refer to § 7.2.2.3
modify a traffic profile, refer to § 7.2.2.4
delete a traffic profile, refer to § 7.2.2.5
display the traffic profile properties, refer to § 7.2.2.6
3AG 86577 ABAA Ed3 598/725

7.2.2.2 Create a traffic profile

This function consists in defining the parameters (service type, transmission mode
and traffic descriptors) of a traffic profile.
From the Main view, menu: Administration => Traffic => Traffic Profile =>
Create
Alcatel
Figure 7-23 Traffic Profile Creation window
To create a traffic profile:

− Choose a Service Type by using the sensitive help.
− Enter a Description that indicates the traffic profile.
− In the Transmission Mode area, choose the Direction by using the option
button.
− In the Traffic Descriptor area:

− Enter a Forward Traffic Descriptor User Label by using the sensitive
help which displays the table of the Traffic Descriptor List window (refer to
§ 7.2.1.1).
− Only if the Direction previously chosen in the Transmission Mode area is
Bidir, enter a Backward Traffic Descriptor User Label by using the
sensitive help which displays the table of the Traffic Descriptor List window
(refer to § 7.2.1.1).
3AG 86577 ABAA Ed3 599/725

The forward and backward descriptors must have the same traffic contract.
− Click on Ok.
Alcatel
The traffic profile is created in the 1354 BM. It is available for the definition of
hard and soft PVC.
The Traffic Profile List window is updated.
3AG 86577 ABAA Ed3 600/725

7.2.2.3 Create a traffic profile from another one

This function consists in defining a traffic profile from another one that already
exists, in order to reduce the number of data to be keyboarded.
select a traffic profile in the list => Create From
Alcatel
Figure 7-24 Traffic Profile Creation window

(when creating a traffic profile from an existing one)
To create the new traffic profile:

− Modify one (at least Service type or Description) or several parameters.
− Click on Ok.
The new traffic profile is created.
3AG 86577 ABAA Ed3 601/725

7.2.2.4 Modify a traffic profile

This function consists in modifying one or several parameters of a traffic profile.
- The traffic profile "FLEXIBLE" used for define flexible VPs can't be modified.
Alcatel
select a traffic profile in the list => Modify
Figure 7-25 Traffic Profile Modification window
To modify the traffic profile:

− Modify one or several parameters. The Service Type and Description fields
cannot be changed.
− Click on Ok.
The traffic profile is modified.
The traffic Profile List window is updated.
3AG 86577 ABAA Ed3 602/725

7.2.2.5 Delete a traffic profile

This function consists in deleting a traffic profile from the 1354 BM.
- The traffic profile "FLEXIBLE" used for define flexible VPs can't be deleted.
Alcatel
select a traffic profile in the list => Delete
Figure 7-26 Confirmation box for deleting one traffic profile
Figure 7-27 Confirmation box for deleting several traffic profiles
After confirmation, the traffic profiles are deleted from the 1354 BM without any
impact on the existing PVCs.
3AG 86577 ABAA Ed3 603/725

7.2.2.6 Display the traffic profile properties

This function consists in displaying information about all the parameters of a

traffic profile.
select a traffic profile in the list => Properties
Alcatel
3AG 86577 ABAA Ed3 604/725

Figure 7-28 Traffic Profile Properties window

In the Forward and Backward areas, the number of fields containing information
depends on the traffic contract.
7.3 Operator profile management

Alcatel
The operator profile management consists in defining operators and assigning

them access rights to the 1354 BM functional and network domains (for more
details, report you to § 10.2).
The following operator profiles are available:

− Administrator : he is in charge the system and operator
administration
− Network Constructor : he is in charge the network commissioning
− Network Manager : he is in charge the PVC provisioning
− Viewer : look only
− NI manager : configure and get information about
transmission paths, PVPCs and PVCCs entities
− NI viewer : only get information about transmission paths,
PVPCs and PVCCs entities
The operator administration permits to create, configure and delete operators that
will be able to access the 1354 BM (see also §1.4.7.1).
To access to the operator management functions, click on the TMN-OSs

Management System icon. Then the TMN-OSs Management main view is
displayed (see Figure 2-19 TMN-OSs Management main view).
Select the 1354 BM application icon. From the Actions menu, select the SMF =>
Operators administration command.
These funct ions are also available fro m Global Actions menu and Global
Operators Administration command.
In this case, the operators thus created are authorized to access several
applicat ions (if installed on the workstation/server) (ex : an operator can be
authorized to access the 1354 BM and 1354 RM).
3AG 86577 ABAA Ed3 605/725

Alcatel
3AG 86577 ABAA Ed3

606/725


Alcatel
Figure 7-29 Global User Management window
User management functions (creation, update and deletion) are available from the
User menu.
3AG 86577 ABAA Ed3 607/725

The next figure shows the User creation window.


Alcatel
Figure 7-30 User creation window
One operator could be defined with more than one profile.
3AG 86577 ABAA Ed3 608/725

8 Utilities

Alcatel
8 Utilities
This chapter deals with some utilities offered

to the user to manage the network.
8.1 Plug & play
8.2 Time scheduling
8.3 PNNI audit
8.4 NE audit / alignment
3AG 86577 ABAA Ed3 609/725

8 Utilities
8.1 Plug & play
The plug & play function is useful to discover the transmission paths and the hard
PVCs created without using 1354 BM or before having installed it.
Alcatel
The objectives of this feature are as follows:

− Traffic descriptor discovery
− Upload the SDH transmission paths
− Transmission path characteristic discovery
− Hard PVC discovery
− Clean-up (*)
(*) Not available in R7.
A plug & play session begins with the Start command and ends with the End
command:
− Start: before performing plug & play actions, the 1354 BM has to save
its data. Then, the operator selects a set of NEs for which the plug & play
actions will be performed. During the plug & play session, only plug & play
actions can be performed.
All the other 1354 BM functions are not accessible (except the display of the
lists).
− End: at any time of the plug & play session, the operator can either
validate all the operations performed during the session or abort them. In the
last case, the 1354 BM data saved during the start command are restored.
3AG 86577 ABAA Ed3 610/725

8 Utilities
The plug & play chain gives the order in which the actions must be performed.
End plug & play

Alcatel
Open the NE List

Start plug & play
Discover traffic
descriptors
Upload SDH
transmission paths
Discover transmission
path characteristics
Discover VP connections
Clean-up terminations
Recover hard PVPC

Clean-up connections
Discover VC connections
Recover hard PVCC
Not available in release R7
Figure 8-1 Plug & play chain
3AG 86577 ABAA Ed3 611/725

8 Utilities
For starting the plug & play session, you must:

start the plug & play, refer to § 8.1.1
Once the plug & play session is open, you can at any time:
open the NE list, refer to § 8.1.12

Alcatel
end the plug & play, refer to § 8.1.11
During the plug & play operations, warnings may occur. To know what to do in
such a case, refer to § 0
3AG 86577 ABAA Ed3 612/725

8 Utilities
8.1.1 Start the plug & play

This function consists in preparing the 1354 BM to perform plug & play actions.
Before to start the plug & play, the sub-networks, the NEs and the ENEs, the
Alcatel
transmission paths (not managed by the 1354 RM) have to be defined in the
1354 BM.
The transmission paths (managed by the 1354 RM) will be recovered with the
'Upload the SDH transmission paths' command (available from NE List
(Plug & Play) window) (see chapter 8.1.2).
Managed by the 1354 RM means that the NEs are managed by the 1354 RM.
Not managed by the 1354 RM means that the NEs (or one NE of the
transmission path extremity) are(is) not managed by the 1354 RM.
From the Main view, menu: Utilities => Plug & Play => Start
Figure 8-2 Confirmation box for starting the plug & play
Once the plug & play session is started, the 1354 BM data are saved.
All the other 1354 BM functions are not available any more (except the lists and
the Transmission path creation function).
3AG 86577 ABAA Ed3 613/725

8 Utilities


Alcatel
Figure 8-3 NE List (Plug & Play) window

− User Label
− LAC State (Denied, Granted, Post-Granted)
− Alarm State (Inhibited, Allowed)
− RM
− Activity State (None, Audit/Alig. In Progress, Synchro. In Progress)
3AG 86577 ABAA Ed3 614/725

8 Utilities
When a plug & play sessio n is in progress, the fo llowing message box appears on
the others graphical sessio ns.
Alcatel
Figure 8-4 Application locked message box.
The graphical sessions are locked and the message is displayed until the end of the
plug & play. By clicking on the Exit button, it is possible to quit the system.

− User Label
Figure 8-5 NE Search (Plug & Play) window
3AG 86577 ABAA Ed3 615/725

8 Utilities
From the NE List (Plug & Play) window, you can:
upload the SDH transmission paths, refer to § 8.1.2
discover the transmission path characteristics, refer to § Error!

Reference source not found.
Alcatel
discover the traffic descriptors, refer to § 8.1.4
discover the VP connections, refer to § 8.1.5
recover the hard PVPCs, refer to § 8.1.6
discover the VC connections, refer to § 8.1.7
recover the hard PVCCs, refer to § 8.1.8
clean-up the terminations, refer to § 8.1.9
clean-up the connections, refer to § 8.1.10
3AG 86577 ABAA Ed3 616/725

8 Utilities
8.1.2 Upload the SDH transmission Paths

This function consists in uploading the SDH transmission paths on the selected
NE (managed by 1354 RM).
- The link between 1354 BM and 1354 RM must be operational.

Alcatel
- The selected NE must be managed by the 1354 RM.
From the NE List (Plug & Play) window, select one or several NEs (managed by
the 1354 RM) in the list => Upload SDH Trans. Path
Figure 8-6 Confirmation box for uploading the SDH transmission paths
After confirmation, for each NE, the upload is started.
Then, the uploaded Transmission Paths appear in Transmission Path List (Plug &
Play) window.
All transmissions paths created in 1354 RM and not in 1354 BM are recovered in
1354 BM database.
For a transmissio n ending on an ETP, recovery is also done and 1354 BM creates
one ENE automatically at the extremit y o f the transmissio n path (in the same sub-
network of the adjacent ATM NE [= the other extremit y o f the transmissio n
path]). The ENE user label is ENE_<Adjacent ATM NE User Label>.
3AG 86577 ABAA Ed3 617/725

8 Utilities
8.1.3 Discover the transmission path characteristics

This function consists in discovering the characteristics of the previously
discovered transmission paths.
- The transmissio n paths must have been discovered.

Alcatel
From the NE List (Plug & Play) window, select one or several NEs in the list =>
Trans. Path Characs.
Figure 8-7 Confirmation box for discovering the transmission path characteristics
After confirmation, each termination (TP/VP_A) of each involved ATM NE,

having a usage state at Busy, is uploaded. The 1354 BM sends a request to each
ATM NE in order to retrieve the connection characteristics of these terminations.
The retrieved characteristics are as follows:

− Routing service (hard or soft)
− VPI range
− VCI range
− Interface type (UNI, ICI or NNI)
The terminations having a configured transmission path connected on (operational

state at Enabled) are not updated with the uploaded configuration. If the
configuration has changed, a warning message is displayed to the user.
The characteristics of the transmission paths ending on uploaded terminations are

updated with the retrieved information only if both terminations have the same
configuration.
3AG 86577 ABAA Ed3 618/725

8 Utilities
For a transmission path ending on an ETP, no request is sent to this extremity and
the transmission path characteristics are updated with the information retrieved
from the termination extremity.
The characteristics of each transmission path not already configured are updated:
− the operational state changes to Enabled
Alcatel
− the usage state changes to Reserved
The transmission path is deleted from the Transmission Path List (Plug & Play)
and is added to the Transmission Path List (Construction part).
3AG 86577 ABAA Ed3 619/725

8 Utilities
8.1.4 Discover the traffic descriptors

This function consists in uploading the traffic descriptors implemented on ATM
NEs. The involved ATM NEs are those that are not yet used by any PVCs already
managed by the 1354 BM.
Alcatel
Traffic Desc.
Figure 8-8 Confirmation box for discovering the traffic descriptors
After confirmation, a request is sent to each selected NE in order to retrieve all the
traffic descriptors implemented on it.
The traffic descriptors not already existing in the 1354 BM are created. They are
marked as coming from the plug & play procedure.
The already existing traffic descriptors are compared with the uploaded ones.
If at least one parameter is not the same, a warning message is displayed to the
user and the parameters previously saved in the 1354 BM (at the beginning of the
plug & play procedure) are kept.
3AG 86577 ABAA Ed3 620/725

8 Utilities
8.1.5 Discover the VP connections

This function consists in discovering the VP connections implemented on ATM
NEs. The involved ATM NEs are those that are not yet used by any PVPCs
already managed by the 1354 BM.
Alcatel
- The transmissio n path characteristics must have been discovered.
Discover VP Cnct.
Figure 8-9 Confirmation box for discovering the VP connections
VP connections (cross-connections and end-connections) implemented on it.
To be created, the retrieved connections have to include a termination belonging

to a transmission path whose characteristics are as follows:
− routing service : Hard
− VPI range including one of the endpoints of the connection
− operational state : Enabled
The created connections are marked as coming from the plug & play procedure.
The resources (bandwidth and VPI) involved in connection terminations are

reserved.
The usage state of each transmission path involved in connection terminations is

set to Reserved.
3AG 86577 ABAA Ed3 621/725

8 Utilities
The retrieved VP connections implemented on involved NEs, already existing in

1354 BM, not belonging to any hard PVPC and having some different
characteristics are updated.
These connections can have been retrieved during a previous plug & play session
and have not been used for any hard PVC recovery.
Alcatel
If some characteristics of an existing connection involved in a hard PVPC have

changed, a warning message is displayed to the user and the characteristics are not
updated.
3AG 86577 ABAA Ed3 622/725

8 Utilities
8.1.6 Recover the hard PVPCs

This function consists in recovering the hard PVPCs not already managed by the
1354 BM, according to the discovered connections.
- The VP connect ions must have been discovered.

Alcatel
From the NE List (Plug & Play) window (no NE selected): Recover Hard PVPC
Figure 8-10 Confirmation box for recovering the Hard PVPCs
After confirmation, the hard PVPC recovering procedure is launched.
The 1354 BM chooses an end-connection among the previously discovered VP

connections.
Then it identifies the transmission paths and the inter-connected VP connections

by progressing step by step until a compatible end-connection (same ATC, QoS
and traffic descriptors as the origin end-connection) or an ENE is reached.
Only previously discovered VP connections are taken into account during the
search.
The hard PVPC is created with the VP_Ts corresponding to the end-connections.
Its traffic contract is consistent with the identified connections.
3AG 86577 ABAA Ed3 623/725

8 Utilities
The hard PVPC is created as follows:

− its identifier is automatically generated

− its provisioning state is Implemented
− its administrative state is Unlocked
− its usage state is Idle
Alcatel
− its direction parameter (unidirectional or bi-directional) is deduced from the

traffic descriptors
− its tunnel state is Disabled
− its availability status is updated
− shaping state and UPC/NPC state are updated according to the information
uploaded during the VP connection discovery phase.
A VPL is created for each identified transmission path. Each used connection is
associated with the hard PVPC.
The bandwidth consumed by the just created hard PVPC is deduced from the
traffic contract (traffic descriptors).
The usage state of each transmission path used by the hard PVPC changes to Busy
if it was Reserved or Idle. Otherwise it remains unchanged.
The same procedure is repeated for each discovered end-connection.
In the case it exists an incoherence, the shaping state and the UPC/NPC state are
set to unknown but the traffic is not disturbed.
If the operator would like to re-implement the hard PVPC, he will have to restore
the output shaping (Act ivate/Deactivate the Out Put Shaping on a hard PVPC:
refer to § 4.1.15 and § 4.1.16).
3AG 86577 ABAA Ed3 624/725

8 Utilities
8.1.7 Discover the VC connections

This function consists in discovering the VC connections implemented on ATM
NEs.
The involved ATM NEs are those that are not yet used by any PVCCs already
Alcatel
managed by the 1354 BM.
- The hard PVPCs must have been recovered.
Discover VC Cnct.
Figure 8-11 Confirmation box for discovering the VC connections
VC connections (cross-connections and end-connections) implemented on it.
To be created, the retrieved connections have to include a termination belonging

to a hard PVPC whose characteristic is as follows:
− VCI range including one of the endpoints of the connection
The created connections are marked as coming from the plug & play procedure.
The resources (bandwidth and VCI) involved in connection terminations are

reserved.
The usage state of each hard PVPC involved in connection terminations is set to
Reserved.
The retrieved VC connections implemented on involved NEs, already existing in

1354 BM, not belonging to any hard PVCC and having some different
characteristics are updated.
These connections can have been retrieved during a previous plug & play session
and have not been used for any hard PVC recovery.
3AG 86577 ABAA Ed3 625/725

8 Utilities
If some characteristics of an existing connection involved in a hard PVCC have

changed, a warning message is displayed to the user and the characteristics are not
updated.
Alcatel
3AG 86577 ABAA Ed3 626/725

8 Utilities
8.1.8 Recover the hard PVCCs

This function consists in recovering the hard PVCCs not already managed by the
1354 BM, according to the discovered connections.
- The VC connect ions must have been discovered.

Alcatel
From the NE List (Plug & Play) window(no NE selected): Recover Hard PVCC
Figure 8-12 Confirmation box for recovering the Hard PVCCs
After confirmation, the hard PVCC recovering procedure is launched.
The 1354 BM chooses an end-connection among the previously discovered VC

connections.
Then it identifies the hard PVPCs and the inter-connected VC connections by

progressing step by step until a compatible end-connection (same ATC, QoS and
traffic descriptors as the origin end-connection) or an ENE is reached.
Only previously discovered VC connections are taken into account during the
search.
The hard PVCC is created with the VC_Ts corresponding to the end-connections.
Its traffic contract is consistent with the identified connections.
The hard PVCC is created as follows:

− its identifier is automatically generated
− its provisioning state is Implemented
− its direction parameter (unidirectional or bi-directional) is deduced from the
traffic descriptors
− its availability status is updated
− shaping state and UPC/NPC state are updated according to the information
uploaded during the VC connection discovery phase.
3AG 86577 ABAA Ed3 627/725

8 Utilities
In the case it exists an incoherence, the shaping state and the UPC/NPC state are
set to unknown but the traffic is not disturbed.
A VCL is created for each identified hard PVPC. Each used connection is
associated with the hard PVCC.
Alcatel
The bandwidth consumed by the just created hard PVCC is deduced from the
traffic contract (traffic descriptors).
The usage state of each hard PVPC used by the hard PVCC changes to Busy if it
was Reserved or Idle. Otherwise it remains unchanged.
The same procedure is repeated for each discovered end-connection.
8.1.9 Clean-up the terminations

This function consists in updating the usage state (from Reserved to Idle) of the
terminations for which no transmission path has been discovered during the
transmission path discovery.
8.1.10 Clean-up the connections

This function consists in removing from the 1354 BM supervision all the
discovered VP and VC connections that have not been used during the hard PVPC
recovery.
3AG 86577 ABAA Ed3 628/725

8 Utilities
8.1.11 End the plug & play

This function consists in ending the plug & play session.
Alcatel
From the Main view, menu: Utilities => Plug & Play => End
Figure 8-13 Confirmation box for ending the plug & play
The plug & play ending procedure acts on the 1354 BM data:
If you click on Yes, the current state of the data is validated.
If you click on No, the data saved when starting the plug & play session are
restored.
If you click on Cancel, the system returns to the plug & play session in progress.
After clicking on Yes, the following actions are done

− The tree is closed
− All windows which are opened are refreshed
− The alarms resynchronization is automatically started
After clicking on No, the following message box is displayed:
Figure 8-14 Message box in case of ending the plug & play procedure
3AG 86577 ABAA Ed3 629/725

8 Utilities
After clicking on OK, the 1354 BM displays the following window, stops and
restarts (the GUI does not restart automatically). Please wait a moment.
Alcatel
Figure 8-15 Message box in case of exiting the application
3AG 86577 ABAA Ed3 630/725

8 Utilities
8.1.12 Open the NE list

This function consists in re-opening the NE list at any time during the plug & play
session.
From the Main view, menu: Utilities => Plug & Play => NE
Alcatel
The NE list window displayed is the same as the “Figure 8-3 NE List (Plug &
Play) window” shown in § 8.1.1.
The commands available from this list are also the same as in § 8.1.1 “Start the
plug & play”.
3AG 86577 ABAA Ed3 631/725

8 Utilities
8.1.13 What to do in case of warnings during the plug & play

When warnings occur during the plug & play, a message box as follows appears.
Alcatel
Figure 8-16 Message box in case of warnings during the plug & play
As specified in the message box, the user has to open the log file to know more
precisely what the warnings are.
See § 2.3.3 to see how to display this file from SMF.
3AG 86577 ABAA Ed3 632/725

Alcatel
8 Utilities
3AG 86577 ABAA Ed3

8.3 PNNI audit
8.2 Time scheduling

633/725
8 Utilities
8.4 NE audit / Alignment tool
Two functions are available from this tool:

− NE audit
− NE alignment
Alcatel
A NE audit / alignment session begins with the Start command and ends with the
End command:
Start: The operator has the possibility to start an audit or an alignment on one (or
more) NE(s). At the beginning of an audit, the selected NEs are 'locked' [some
operations (ex: delete the NE) are not authorized]. All the other 1354 BM
functions are accessible.
End: At any time of the audit / alignment session, the operator can close the
session. An 'unlock' of the NEs will be done.
For starting the audit / alignment session, you must:
start the audit / alignment session, refer to § 8.4.1
Once the session is open, you can at any time:

− perform an audit, refer to § 8.4.2
− perform an alignment, refer to § 8.4.3
− perform a force alignment, refer to § 8.4.3.1.3
− display an audit file result, refer to § 8.4.3.1.1
− end the audit / alignment session, refer to § 8.4.4
3AG 86577 ABAA Ed3 634/725

8 Utilities
8.4.1 Start the NE audit / alignment

This function consists in preparing the 1354 BM to perform audit / alignment
actions.
Alcatel
From the Main view, menu: Utilities => Audit/Alignment => Start
Figure 8-17 Confirmation box for starting the audit / alignment session
- A 'lock' of NEs will be done just before starting the audit procedure until the end
of audit / alignment procedure.
Once the audit / alignment session is started, the NE List (Audit) window is
displayed and the command to perform an audit is available.
If the operator wants to perform directly an alignment, the associated commands

are available from the menu Utilities => Audit/Alignment => Directory
(Alignment)
All the other 1354 BM functions are available.
3AG 86577 ABAA Ed3 635/725

8 Utilities
8.4.2 NE audit tool

This function allows to perform an audit between data stored in 1354 BM
database and data read from ATM NE MIB.
Entities concerned are:

Alcatel
- Traffic descriptors:
Traffic type, PCR, MBS, MFS CDVT/PCR, CDVT/MCR, Frame or cell

based.
- TP/VP_A characteristics:
Routing service type (Hard, Soft), Interface type (UNI, NNI, ICI), VPI
& VCI ranges, Bit rate technology (PDH, SDH), Overbooking
configuration (alpha, traffic type activation).
- IMA/VP_A characteristics:
Routing service type (always Hard), Interface type (UNI, NNI, ICI),
VPI & VCI ranges, Overbooking configuration (alpha, traffic type
activation).
- IMA link termination:
IMA group identifier (IMA/VP_A identifier), Bit rate, Technology

(PDH, SDH).
- VPC connections:
Connection type (VP/VC End/Cross, Soft PVC initiator, Soft PVC

target), TP identifier, Cast type (point-to-point, point-to-multi-point
root, point-to-multi-point leaf), VPI, Tx & Rx Traffic descriptor
indexes, Shaping type, UPC/NPC mode, Utilization factor.
- VP/VC_A characteristics:
Activation status, TP identifier, VPI & VCI ranges, Routing service

type (Hard, Soft), Interface type (UNI, NNI, ICI).
- VCC connections:
Connection type (VP/VC End/Cross, Soft PVC initiator, Soft PVC

target), TP identifier, Cast type (point-to-point, point-to-multi-point
root, point-to-multi-point leaf), VPI & VCI, Tx & Rx Traffic descriptor
indexes, Shaping type, UPC/NPC mode, Utilization factor.
- PNNI characteristics:
NE ATM address, TP/VP_A address.
3AG 86577 ABAA Ed3 636/725

8 Utilities
Audit can be done on one ATM NE, on a list of ATM NEs managed by the 1354
BM.
The audit's result is stored in a text file (ASCII format).

Alcatel
- For TP/VP_A, only ent ities with Act ivat ion Status "ON" are compared.
From the Main view, menu: Utilities => Audit/Alignment => NE (Audit)
The NE List (Audit) window is displayed:
Figure 8-18 NE List (Audit) window
The search funct ion is available only wit h no selection in the list. For de-select ion
3AG 86577 ABAA Ed3 637/725

8 Utilities

Alcatel
Figure 8-19 Audit NE Search window

From the NE list (Audit) window, you can:

start an audit, refer to § 8.4.2.1
3AG 86577 ABAA Ed3 638/725

8 Utilities
8.4.2.1 Audit NE(s)
This function consists in starting the audit on the previously selected NE(s).

Alcatel
- Act ivit y state of selected NE(s) must be:

- None
- Or Audit/alig. In Progress (due to an audit/alignment procedure launched
on the NE(s) by the operator himself).
From the Main view, menu: Utilities => Audit/Alignment => NE (Audit) =>
select one or several NE(s) in the NE list => Start Audit
A confirmation box is displayed for each selected NE:
Figure 8-20 Confirmation box for start audit on one NE
Figure 8-21 Confirmation box for start audit on several NEs
3AG 86577 ABAA Ed3 639/725

8 Utilities
When the audit is in progress on a selected NE, the NE is 'lo cked'. Some
operations are not authorized (ex : delete the NE, delete the transmissio n paths
that has at least one NE concerned by audit / alignment sessio n, …).
After confirmation, the results of audit are stored into a directory which is
Alcatel
available from the Directory List window of the Alignment function. (see § 8.4.3).
Into this directory (named Audit_YYYYMMDD_HHMM_SS), one file by

audited NE (AuditAlign_<NE_UserLabel>.txt) is stored.
When the audit is completed on all selected NEs, a message is displayed in the
status bar.
The main steps of the audit are listed into the 1354 BM Log file. If some errors or
warning occur, they are listed in this file too and in an error message window.
3AG 86577 ABAA Ed3 640/725

8 Utilities
8.4.3 NE alignment tool

This function allows to perform an alignment which consists on updating ATM
NE MIB with data existing into 1354 BM database.
Alignment can be done on one ATM NE, on a list of ATM NEs managed by the
Alcatel
1354 BM.
From the Main view, menu: Utilities => Audit/Alignment => Directory
(Alignment)
Figure 8-22 NE Alignment Directory List window
A list of directories appears. "Creation Date" is the starting date and time of audits
done on the workstation.
From the Directory list, you can:
display the file list, refer to § 8.4.3.1
start an alignment, refer to § 8.4.3.1.2
start a force alignment, refer to § 8.4.3.1.3
3AG 86577 ABAA Ed3 641/725

8 Utilities
8.4.3.1 Display the file list

This function consists in displaying a list of files names generated by an audit.
From the Main view, menu: Utilities => Alignment => Directory => select one
Alcatel
directory in the list => File List
The following window appears:
Figure 8-23 List of audit's files for NE alignment
A list of audit files is displayed, one file per ATM NE.
The file name is built with the NE User Label: AuditAlign_<NE_user_label>.
Three actions are available:
1. Display Audit File : to display the result of an audit action
2. Start Alignment : to launch the alignment procedure
3. Start Force Alignment : to launch the force alignment procedure.
3AG 86577 ABAA Ed3 642/725

8 Utilities
8.4.3.1.1 Display an audit file

This function consists in displaying the result of an audit file.
From the Main view, menu: Utilities => Alignment => Directory => select one
directory in the list => File List => select one file in the list => Display
Alcatel
The following read-only window appears:
3AG 86577 ABAA Ed3 643/725

8 Utilities
For each NE entity (traffic descriptor, TPVP_A, VP connections, VPVC_A, VC

connections), three sections are listed:

- "New <NE entity> detected into 1354 BM database" section:
In this section are listed all entities existing into 1354 BM database but not
into NE MIB.
- "New <NE Entity> detected into NE MIB database" section:
Alcatel
In this section are listed all entities existing into NE MIB but not into 1354
BM database. This section is not used by alignment.
- "Modified <NE entity> detected" section:
In this section are listed entities existing into 1354 BM and NE MIB database
but with some different attribute values. This section is not used by alignment.
8.4.3.1.2 Align NE(s) from a directory or from an audit file
Alignment can be launch from the Directory List window or from the File List
window.
Case 1) Alignment is launched from the Directory List window:
A confirmation is required before beginning the alignment procedure with the

contents of all the files contained in the selected directory. The following window
appears:
Figure 8-24 Confirmation box to start alignment procedure (for a directory)
Click on Yes button to start the alignment.
Case 2) Alignment is launched from the File List window:
A confirmation is required before beginning the alignment procedure with the

selected file(s). The following windows appear:
3AG 86577 ABAA Ed3 644/725

8 Utilities

Alcatel
Figure 8-25 Confirmation box to start alignment procedure (for one NE)
Figure 8-26 Confirmation box to start alignment procedure (for several NEs)
Click on Yes (or All) button to start the alignment.
Alignment tool reads the list of files given and proceeds NE by NE.
If alignment fails for one NE, the tool proceeds with the next NE in the list.
Alignment consists on updating Equipment MIB with data existing into 1354 BM
database only.
The 1354 BM database is also updated, only if some traffic descriptors are re-
created. During an alignment, the following steps are done:
- Open the data file.
- Check NE identifier (NE keyword into file): it must be the same as one given
as entry parameter.
- Recreate Traffic Descriptor existing into 1354 BM database and not into
Equipment MIB. Only entities describes into "New Traffic Descriptor(s)
detected into BM Database" section file are taken into account.
- Configure and activate TP/VP_A characteristics existing into 1354 BM

database and not into Equipment MIB. Only entities describes "New
TP/VP_A detected into BM Database" section file are taken into account.
- Recreate IMA/VP_A existing into 1354 BM database and not into Equipment
MIB. Only entities describes into "New Traffic IMA/VP_A detected into BM
Database" section file are taken into account.
3AG 86577 ABAA Ed3 645/725

8 Utilities
- Configure and activate IMA link existing into 1354 BM database and not into
Equipment MIB. Only entities describes "New IMA link detected into BM
- Recreate VPC connections existing into 1354 BM database and not into
Equipment MIB. Only entities describes "New VP Connection(s) detected into
BM Database" section file are taken into account.
Alcatel
- Recreate VP/VC_A characteristics existing into 1354 BM database and not

into Equipment MIB. Only entities describes "New VPVCA detected into BM
- Recreate VCC connections existing into 1354 BM database and not into
Equipment MIB. Only entities describes "New VC Connection(s) detected
into BM Database" section file are taken into account.
When the alignment is completed on all selected NEs, a message is displayed in

the status bar.
The main steps of the alignment are listed into the 1354 BM Log file. If some
errors or warning occur, they are listed in this file too and in an error message
window.
8.4.3.1.3 Force alignment NE(s) from a directory or from an audit file
Force alignment can be launch from the Directory List window or from the File
List window.
Case 1) Force alignment is launched from the Directory List window:
A confirmation is required before beginning the force alignment procedure with

the contents of all the files contained in the selected directory. The following
window appears:
Figure 8-27 Confirmation box to start force alignment procedure (for a directory)
Click on Yes button to start the force alignment.
Case 2) Force alignment is launched from the File List window:
3AG 86577 ABAA Ed3 646/725

8 Utilities
A confirmation is required before beginning the forece alignment procedure with

the selected file(s). The following windows appear:

Alcatel
Figure 8-28 Confirmation box to start force alignment procedure (for one NE)
Figure 8-29 Confirmation box to start force alignment procedure (for several NEs)
Click on Yes (or All) button to start the force alignment.
Taking the 1354 BM as the reference, the force alignment purpose is to force the
ATM NE to reflect the exact image of the 1354 BM database (regarding
transmission & connections domains only not PM neither OAM aspect)
The operator selects one or several file(s) or one directory.
The selected audit files corresponds to an audit that has been launched in the
current audit/alignment procedure by the operator itself.
The force alignment is done on all the ATM NE involved in the files of the
selected directory. If force alignment fails for one NE, the tool proceeds with the
next NE in the list.
3AG 86577 ABAA Ed3 647/725

8 Utilities
The force alignment main policy is summarized in the following rules:

Case a) An element is present in the 1354 BM but not in the ATM NE MIB =>
Create it on the ATM NE.
Case b) An element is present in the ATM NE MIB but not in the 1354 BM =>
Delete it from the ATM NE MIB. This case should be minimized by the use of the
Alcatel
plug and play.
Case c) An element is present in the 1354 BM and also in the ATM NE MIB but
with different characteristics => Align the ATM NE taking the 1354 BM as the
reference.
The force alignment follows the following steps:
1) Clean-up VCC (Case b))
2) Clean-up VP/VC_A (Case b))
3) Clean-up VPC (Case b))
4) Clean-up the PNNI TP/VP_A configuration (Case b))
5) Clean-up TP/VP_A (Case b))
6) Clean-up IMA link (Case b))
7) Clean-up IMA/VP_A (Case b))
8) Clean-up Traffic Descriptors (Case b))
9) Clean-up the PNNI NE configuration (Case b))
10) TP/VP_A alignment (one by one): (Case c))

− Remove the held VC connections, VP/VC_A and then VP connections
− Align TP/VP_A
− Create new Traffic Descriptor if needed
− Built-in VP connections, VP/VC_A, VC connections (eventually with new
characteristics)
11) IMA/VP_A alignment (one by one): (Case c))
− Remove the held VC connections, VP/VC_A and then VP connections
− Align the IMA/VP_A (de-activate, configure, activate)
− Create new traffic descriptor if needed
− Buid-back the VP connections, VP/VC_A connections (eventually with aligned
characteristics)
12) IMA link alignment (one by one): (Case c))
3AG 86577 ABAA Ed3 648/725

8 Utilities
− De-activate the IMA link

− Configure it with the good characteristics (IMA group identifier)

− Activate it back
13) VP connection alignment (one by one): (Case c))
− Remove held VC, VP/VC_A
Alcatel
− Align the VP connections

− Create new Trafic Descriptor if needed
− Built-in VP/VC_A, VC connections (eventually with new characteristics)
14) VP/VC_A Alignment (one by one): (Case c))
− Remove held VC
− Align the VP/VC_A
− Create new Trafic Descriptor if needed
− Built-in VC connections (eventually with new characteristics)
15) VC connections alignment (one by one): (Case c))
− Traffic Descriptors creation if needed
− Align the VC connection
16) Traffic Descriptor alignment: (Case c))
− Traffic Descriptor clean-up
17) PNNI Node alignment: (Case c))
18) PNNI TP/VP_A alignment: (Case c))
19) Traffic Descriptor downloading: (Case a))
20) PNNI Node downloading: (Case a))
21) TP/VP_A downloading: (Case a))
22) Overbooking TP/VP_A downloading: (Case a))
23) PNNI TP/VP_A downloading: (Case a))
24) VP Connections downloading: (Case a))
25) VP/VC_A downloading: (Case a))
26) VC Connections downloading: (Case a))
3AG 86577 ABAA Ed3 649/725

8 Utilities
8.4.4 End the audit / alignment

This function consists in ending the audit / alignment session.
Alcatel
From the Main view, menu: Utilities => Audit/Alignment => End
Figure 8-30 Confirmation box for ending the audit / alignment session
The concurrent sessions are unlocked.
3AG 86577 ABAA Ed3 650/725

9 Glossary

Alcatel
9 Glossary
This chapter provides the definition of the

abbreviations and terms used in this manual,
and refers to the windows of the 1354 BM
user interface that use them.
3AG 86577 ABAA Ed3 651/725

9 Glossary
The abbreviations and definitions used in this manual are given in alphabetical
order.
For each item, the windows of the user interface where it appears are listed in
Italics.
Alcatel
Acquit the NE LAC state

When the LAC state of the NE is equal to Post-granted, this function allows the
operator to acknowledge the possible misalignment between the 1354 BM and the
ATM NE due to a possible modification from the 1320 CT.
See Acquit the NE LAC state function (chapter 3.2.7).
Address
The ATM NE address includes the NE IP address followed by a four-digit suffix
that corresponds to a port number.
NE / ENE List window (NE panel)

Available NE List window
NE Properties window
NE List for Plug & Play
Adjacent NE
This NE is not directly managed by the 1354 BM. It is represented by an ENE and
linked to the managed network by means of an ETP and a transmission path.
An adjacent NE is defined by a site label, an SDH NE label, a port label and a TP

label.
Transmission Path Extremities window
ADM Add and Drop Multiplexer

Type of network equipment.
Administrative state
The administrative state reflects the operator decision concerning the use of a
transmission path (or a hard PVPC) for supporting hard PVPCs (or respectively
hard PVCCs).
At the creation time, the administrative state of a transmission path is not

significant (value None). When it is configured, the administrative state becomes
Unlocked.
3AG 86577 ABAA Ed3 652/725

9 Glossary
When the administrative state of a (hard configured) transmission path (or a hard
PVPC) is Locked, no new hard PVPC (or respectively hard PVCC) can use it.
Transmission Path List window
Transmission Path Search window
Hard PVPC Characteristics Search window
Alcatel
AFI Authority and Format Identifier

See ATM Address.
AIS Alarm Indication Signal

Probable cause of an alarm.
Alarm severity
See Alarm status.
Alarm state
The alarm state indicates if the NE is allowed to send its alarms to the 1353 NM
and to the 1354 BM (= Allowed value) or not (= Inhibited value).
See NE/ENE List window (NE panel)
NE Search window
Alarm status
The alarm status corresponds to the presence of alarms:
on the ATM card for an NE
on a TP/VP_A or TP/IMA_A for a termination
It gives the upper severity of the current alarms: Critical, Major, Minor, Warning
or Indeterminate. If there is no alarm, the alarm status is None.
A color is associated to each alarm severity, as shown in the table below.
Alarm severity Color
None Green
Indeterminate White
Warning Mauve
Minor Yellow
Major Orange
Critical Red
3AG 86577 ABAA Ed3 653/725

9 Glossary
These colors are used to surround the symbols in the graphical views as well as in
the Alarm Status column of the list windows.
Fault Localization List window (transmission path)

Fault Localization List window (hard PVPC)
Alcatel
Fault Localization List window (hard PVCC)

Termination List window
Termination Search window
Alignment
This function allows to perform an alignment which consists on updating ATM
NE MIB with data existing into 1354 BM database.
See NE Alignment tool (chapter 8.4)
Allocation mode
Three modes are available:
− Automatic: consists in searching available bandwidth on each segment of
connection, in each direction, according to the traffic descriptors of the hard
PVPC/PVCC
− Semi automatic: consists in associate the hard PVPC/PVCC with a list of
segments of connection or Nes with the indication “To be used” or “To be
excluded”. This list will be taken account during the search of the route in
the aim to find a route according to these constraints
− Manual: the complete list of Transmission Path must be given to specify
the route. A check is done to verify the route continuity.
Hard PVPC Allocation window
Hard PVPC Leg Allocation window
Hard PVCC Allocation window
Hard PVCC Leg Allocation window
Allocation type
This parameter is used to define the transmission mode of a traffic profile.
Authorized values are: point-to-point and point-to-multipoints.
See also Transmission mode.
Hard PVPC / Hard PVCC / Soft PVPC / Soft PVCC Definition windows
Traffic Profile Creation window
Traffic Profile Creation window (from an existing traffic profile)
Traffic Profile Modification window
Traffic Profile Properties window
3AG 86577 ABAA Ed3 654/725

9 Glossary
A NE User Label
This identifies the origin (NE) of a transmission path.

Hard PVPC / Hard PVCC / Soft PVPC / Soft PVCC List windows
Alcatel
Hard PVPC / Hard PVCC / Soft PVPC / Soft PVCC Extremities windows
Transmission Path List (Plug & Play) window
AS Alarm Surveillance
ALMAP generic component
ASAP Alarm Severity Assignment Profile
ATC ATM layer Transfer Capability

The ATC defines the type of service offered by the ATM layer:
− DBR (Deterministic Bit Rate) Class 1, Class 2 or Class U
Constant bit rate with time reference.
Used for the voice, video and DSL transfers.
Also called CBR (Constant Bit Rate) for DBR Class1 and DBR Class2
or UBR (Unspecified Bit Rate) for DBR ClassU, by the ATM Forum.
− GFR.2 (Guaranteed Frame Rate):
One part with a guaranteed bandwidth measured in frame per second,
another part called Best Effort.
Used for the data transfer.
− UBR+:
UBR with a Minimum desired Cell Rate.
Designed for providing Minimum Rate guarantees to the ATM
Unspecific Bit Rate Service and improving performance of TCP over
ATM_UBR service.
− SBR (Statistic Bit Rate): (not implemented in BM release 6)
Variable bit rate without time reference.
Used for the file transfer.
Also called VBR (Variable Bit Rate) by the ATM Forum.
See also Traffic contract.
ATM Asynchronous Transfer Mode

International standard for cell relay in which multiple service types (such as voice,
video or data) are conveyed in fixed-length (53-bytes) cells. Fixed-length cells
allow cell processing to occur in hardware, thereby reducing transit delays. ATM
3AG 86577 ABAA Ed3 655/725

9 Glossary
is designed to take advantage of high-speed transmission media such as E3,

SONET and T3.
ATM address
The ATM address allows ATM NEs and ATM NE terminations to be used as
nodes in PNNI management.
Alcatel
Two formats (each encoded in twenty octets) are available for the ATM address:
DCC/ICD format:
− AFI: one-octet field which specifies the format of the rest of the prefix and
the authority responsible for allocating it.
− DCC/ICD: two-octet field which specifies the authority (country or
international organization) responsible for allocating the rest of the prefix.
− H0-DSP: ten-octet field that is the rest of the network prefix, and may be
structured hierarchically to reflect the network topology or address
authorities.
− ESI: six-octet field that identifies an end system. It is unique for a given
network prefix.
− Selector: that one-octet field is read-only because not now used (always set
to 00 value).
Generic format:
− PNNI address prefix: identifies the default PNNI summary address prefix
that is encoded by using thirteen octets.
− ESI: six-octet field that identifies an end system and is unique for a given
network prefix.
− Selector: that one-octet field is read-only because not now used (always set
to 00 value).
NE/ENE List window (NE panel)
Soft PVPC Definition window
Soft PVCC Definition window
Soft PVPC Extremities window
Soft PVCC Extremities window
NE List (Administration) window
PNNI Node ATM Address Configuration window
Termination List (Administration) window
PNNI Interface ATM Address Configuration window
ATM connection
An ATM connection is a concatenation of PVCs. It provides access points with
end-to-end information transfer capability.
ATM Forum
This association of some 700 manufacturers and providers of telecommunication
equipment has an important role in ATM procedure standardization.
3AG 86577 ABAA Ed3 656/725

9 Glossary
ATM NE
An ATM NE corresponds physically to the ATM card of an ISA NE.
See also NE.
Audit
Alcatel
This function is provided in order to check that all entities (Transmission Paths,
Traffic Descriptors, Hard PVC’s) existing inside 1354 BM are well provisioned
inside ATM NE(s). The differences discovered by the audit are collected in files.
See NE Audit tool (chapter 8.4)
Availability status
The availability status is used in transmission path management and PVC
management.
For a transmission path, it corresponds to the presence (or not) of alarms on the
TP/VP_As of the transmission path extremities.
For a PVPC, it corresponds to the presence (or not) of alarms at all the VP_Ts or
VPL_Ts of the PVPC.
For a PVCC, it corresponds to the presence (or not) of alarms at all the VC_Ts or
VCL_Ts of the PVCC.
The availability status can be Normal, Degraded or In Failure, depending on the

alarm severity on both extremities, as illustrated in the table below.
Alarm severity on extremity B

Alarm severity on
extremity A
Critical or Major Minor or Warning no alarm
Critical or Major In Failure In Failure In Failure
Minor or Warning In Failure Degraded Degraded
No alarm In Failure Degraded Normal
A color is associated to each availability status, as shown in the table below.
Availability status Color
Normal Green
Degraded sky blue
3AG 86577 ABAA Ed3 657/725

9 Glossary
In Failure Red
These colors are used in the Availability Status column of the list windows.
For a transmission path, the availability status also depends on the working state
Alcatel
of the SDH path that supports the transmission path. The working state is
provided by the 1354 RM.
When the working state is Disabled, the availability status is In Failure. When the
working state is Enabled, the availability status depends on the most severe alarm
on the extremities as shown in table above.
As long as a hard PVPC is not commissioned or implemented, its availability

status is not significant (value None in the list windows).

Hard PVPC Search window
Hard PVCC Search window
Soft PVPC Characteristics Search window
Soft PVCC Characteristics Search window
Transmission Path Search (Plug & Play) window
B
Backward Traffic Descriptor Id. Backward Traffic Descriptor Identifier

See Traffic profile.
Traffic Profile List window

Bandwidth
The bandwidth is the difference between the highest and lowest frequencies
assigned to a communication channel or used on a transmission medium. The
higher the bandwidth is the more the data throughput and thus the capacity.
In ATM context, the bandwidth represents the capacity of a transmission path (or
a PVPC) in term of number of supported PVPCs (or respectively PVCCs).
See also Bandwidth load.
3AG 86577 ABAA Ed3 658/725

9 Glossary
Bandwidth load
This defines the use rate of a transmission path or a PVPC in term of bandwidth.
The bandwidth load may be different according to the direction of the

transmission path or PVPC.
Hard Transmission Path Bandwidth Load window

Alcatel
Soft Transmission Path Bandwidth Load window

Hard PVPC Bandwidth Load window
Bit rate
The bit rate is an SDH transmission characteristic that defines the number of bit
per second that can be supported by a transmission path.
The bit rate value can be VC-12, VC-3, VC-4, VC-4-4c (only for 8 x 8 cards), E1
(2 Mb/s), E3 (34 Mb/s) or DS3 (45Mb/s) (only for D3 and 4x4 enhanced boards).
At the ETP creation time, the bit rate is not yet defined (value “-“ in the list
windows). The bit rate is defined during the transmission path creation.

Termination Configuration window
ETP List window
ETP Search window
Transmission Path Creation window
Termination Search (Administration) window
BM Bit Rate
This defines the bit rate characteristic entered by the operator for a given NE. The
BM bit rate value can be VC-12, VC-3, VC-4, VC-4-4c (only for 8 x 8 cards), 2
Mb/s or 34 Mb/s.
Termination Transmission Characteristics Audit
See also Bit rate.
3AG 86577 ABAA Ed3 659/725

9 Glossary
BM Technology
This defines the technology characteristic entered by the operator for a given NE.
The BM technology value can be SDH or PDH.
See also Technology.

Alcatel
Cast type
This indicates if the hard PVPC or hard PVCC is point-to-point or point-to-multi-
points.
Hard PVPC List window
Hard PVCC List window
CBR Constant Bit Rate

ATM service type which supports a constant or guaranteed rate to transport
services such as video or voice as well as circuit emulation which requires
rigorous timing control and performance parameters.
See also ATC.
CC Continuity Check
This function tests the continuity on a PVC end-to-end or a PVC segment. If the
continuity is down, an alarm is emitted.
See also CC Direction.
CC direction
This indicates the direction (A to Z, Z to A, both or not any) on which the
Continuity Check (CC) can be activated or not.
CC state
The CC state indicates if the Continuity Check function is Activated, Partially
Activated (= detection endpoint not activated) or Deactivated.
3AG 86577 ABAA Ed3 660/725

9 Glossary
Activate / Deactivate Hard PVPC windows

Hard PVPC Properties window

Activate / Deactivate Hard PVCC windows
Hard PVCC Properties window

Alcatel
CDV Cell Delay Variation

This is the degree of variation in the Cell Transfer Delay (CTD) of a virtual
connection. It is induced by buffering and cell scheduling.
See also CDVT.
CDVT CDV Tolerance

See also CDVT PCR and CDVT MCR.
CDVT MCR
This negotiated traffic parameter is the CDVT referred to the Minimum Cell Rate
(MCR).
See also Traffic descriptor.
Traffic Descriptor List window
Traffic Descriptor Creation window
Traffic Descriptor Creation window (from an existing traffic descriptor)
CDVT PCR
This negotiated traffic parameter is the CDVT referred to the Peak Cell Rate
(PCR).
The CDVT must be greater than the time arrival 1/PCR. The calculation is
CDVT/(10E6*10) > 1/(8*53*PCR) with CDVT in 10 micro second and PCR in
cell par second.
Hard PVPC / Hard PVCC / Soft PVPC / Soft PVCC Properties windows
3AG 86577 ABAA Ed3 661/725

9 Glossary
CLI Command Line Interface

The Command Line Interface allows to execute commands without using ATM
USM (Abstract CLI syntax is available in § 10.2).
CLP Cell Loss Priority

This bit in the ATM cell header determines whether a cell can be preferentially
Alcatel
deleted or not during periods of congestion.
Cells with CLP=1 are deleted to preserve the CLR of cells with CLP=0.
CLR Cell Loss Ratio

This negotiated QoS parameter is the number of lost cells divided by the total
number of transmitted cells.
Comment
Text associated to a network component (sub-network, ENE, transmission path,
PVC) and entered by the operator at the creation or definition time.
Sub-network List window

Sub-network Creation window
NE / ENE List window (ENE panel)
ENE Creation window
ENE Properties window
Transmission Path Properties window
Hard PVPC / Hard PVCC / Soft PVPC / Soft PCVCC Definition window
Hard PVPC / Hard PVCC Search window
Hard PVPC / Hard PVCC Modification window
Soft PVPC / Soft PVCC Description Search window
Traffic Profile Search window
3AG 86577 ABAA Ed3 662/725

9 Glossary
Connection
See ATM connection
Consistency state
The consistency state represents the 1354 BM capability to manage an ATM NE,a
Tranmssion Path, a hard PVPC, a hard PVCC.
Alcatel
The consistency state can be Consistent, Not Consistent or Inderminate (*)
(*) : Indeterminate : possible value only managed at Transmision Path level.
It changes to Not Consistent in the following cases:

− mismatch of NE parameters between the 1354 BM and the 1353 NM
− mismatch about NE assignment
− problem during the creation/deletion of Transmission path in the 1354 RM.
It changes to Indeterminate in the following case:
− when the Transmission Path is managed by the 1354 RM and the link is cut
between the 1354 BM and the 1354 RM.
The consistency state represents also the consistency of a PM measure (or a PM
transport or a Performance Point).
See NE / ENE List window (NE panel)

NE Search window
Hard PVPC / PVCC List windows
Hard PVPC / PVCC Leg List windows
PM Measure List window
PM Transport List window
PP List window
NE List (Plug & Play)
Constraint
The 1354 BM gives the possibility to attach a set of routing constraints to a Hard
PVPC, a Hard PVPC Leg, a Hard PVCC, or a Hard PVCC Leg. The routing
constraints can have the following forms:
3AG 86577 ABAA Ed3 663/725

9 Glossary
Positive Node: consist in defining a list of NE to be crossed

Negative Node: consist in defining some NEs that must not be used for the
routing allocation.
Positive Link: consist in forcing the use of one or several Transmission
Paths.
Negative Link: consist in defining some Transmission Paths that must not
be used for routing allocation.
Alcatel
CORBA Common Object Request Broker Architecture
Cost model
Two kind of cost could be selected:
Hard PVPC / Hard PVCC Allocation windows
Hard PVPC / Hard PVCC Leg Allocation windows
CP Connection Point
A connection point is an extremity of a PVC. It is used by an ATM connection
and located on an ATM NE or an ENE. It can be an endpoint or a cross-
connection point.
See also Endpoint and Cross-connection point.
CRC Cyclic Redundancy Check
Cross-connection point
A cross-connection point is only located on an ATM NE. It allows the connection
between two PVCs.
See also Connection.
CTD Cell Transfer Delay

This negotiated QoS parameter is the elapsed time between a cell exit event at the
measurement point 1(e.g., at the source UNI) and the corresponding cell entry
event at measurement point 2 (e.g., the destination UNI) for a particular
connection. The cell transfer delay between two measurement points is the sum of
the total inter-ATM-node transmission delay and the total ATM-node processing
delay.
3AG 86577 ABAA Ed3 664/725

9 Glossary
D
DBR Deterministic Bit Rate

ITU-T designation that corresponds to CBR for the ATM Forum.
See also ATC.

Alcatel
DCC Data Country Code

This two-octet field specifies the country in which an address is registered. Both
octets are encoded in Binary Coded Decimal syntax. The code is left justified and
padded on the right with the hexadecimal value “F” to fill the two octets.
See ATM address.
Default VCI range

The default VCI range is defined by the first and last VCIs whose values are
between 1 and 31.

Transmission Path Configuration window
Transmission Path Bandwidth Load window
Description
This text field is associated with the Service Type field to identify a traffic profile.
See also Service type and Traffic profile.
Direction
This parameter is used to define the transmission mode of a traffic profile. It can
be bi-directional (Bidir) or unidirectional (Unidir).
Hard PVPC List / Hard PVCC List windows

Soft PVPC List / Soft PVCC List windows (Characteristics panel)
3AG 86577 ABAA Ed3 665/725

9 Glossary
DS3
Third level of the North-American plesiochronous digital hierarchy of

transmission systems, with a bit rate of 44 738 Mbit/s.
DTL Designated Transmit List

List of nodes and optical link identifiers that completely specify a path across a
Alcatel
single PNNI peer group.
DXC
Kind of NE.
E
EDGE
See Shaping (Protection) Mode.
EML Element Management Layer

Abstraction of the functions provided by systems that manage each network
element on an individual basis.
Endpoint
An endpoint is an extremity of an ATM connection. It is located on an ATM NE
or an ENE.
See also Connection.
ENE External Network Element

An ENE represents an NE or a set of NEs not managed by the 1354 BM, for
example, an ATM NE contained in an adjacent sub-network not accessible to
1354 BM manager.
The ENE is known in the 1354 BM thanks to its identifier.
See also ENE User Label
ENE User Label

This identifies an ENE. The ENE identifier is created by the operator.

ENE Adding window
ENE Modifying window
ENE Deleting window
ENE Search window
ETP List window
3AG 86577 ABAA Ed3 666/725

9 Glossary
ETP Creation window


ESI End System Identifier

Alcatel
This six-octet field distinguishes multiple nodes at the same level in case the
lower level peer group is partitioned.
See also ATM address.
ETP External Termination Point

Transmission path extremity located in an ENE. See also ETP Id.
ETP Id. ETP Identifier

This identifies an ETP.
See also ETP.
ETP List window
FAD Function Access Domain

A FAD defines a set of functions that can be accessed by an operator according to
its profile.
Flexible VP
A flexible VP is a unitary hard PVPC (i.e not cross-connected) that uses a specific
traffic profile without any characteristic (ATC, PCR, MCR, CDVT, ...). This kind
of hard PVPC does not consume any bandwidth of the transmission path. It will
not reserve any bandwidth to it.
Its reason to be comes from the fact that when a hard PVPC is established
between two adjacent nodes, there is in principle, no reason to characterize its
traffic characteristics because the hard PVPC is transparent to the traffic
management blocks, that work on the carried hard PVCCs.
Any kind of hard PVCC can be set up over a flexible unitary hard PVPC.
The flexible unitary hard PVPC is an Alcatel proprietary concept not defined in
ATM-forum and ITU-T standard.
3AG 86577 ABAA Ed3 667/725

9 Glossary
Forward Traffic Descriptor Id. Forward Traffic Descriptor Identifier

See Traffic profile.

Alcatel

Frame based
Indicates that the PVC is requested to treat data as frames rather than as
individuals cells.
See Traffic Descriptor List window
GFR Guaranteed Frame Rate

See ATC.
Graphical view
A graphical view represents the network by using graphical symbols.
See also View.
Sub-network View Hard Transmission Path Domain

Sub-network View Hard VP Domain
Sub-network View Hard VC Domain
Global view Hard Transmission Path Domain
Global view Hard VP Domain
Global view Hard VC Domain
Sub-network view showing the transmission paths used by the hard PVPC
Sub-network view showing the VPs used by the hard PVCC
Grooming
See Shaping (Protection) Mode.
3AG 86577 ABAA Ed3 668/725

9 Glossary
H
HEC Header Error Control

By using the fifth octet in the ATM cell header, ATM equipment may check for
an error and corrects the contents of the header. The check character is calculated
by using a CRC algorithm allowing a single bit error in the header to be corrected
Alcatel
or multiple errors to be detected.
ICD International Code Designator

This two-octet field identifies an international organization.
See ATM address.
ICI Inter-Carrier Interface

See Interface type.
IMA Inverse Multiplexing ATM
ATM capabilities to transport ATM data flows over several different E1, VC-12
or VC-3 links.
See chapter 1.3.3.
IMA group
Physical links grouped to form a higher-bandwidth logical link whose rate is

approximately the sum of the individual link rates = groups of links at one end
used to establish an IMA link to other end.
Also called IMA transmission path.
IMA link
Link established between two IMA units over a number of physical links
(transmission path IMA).
IMA link is supported by a SDH path. It is a component of an IMA transmission
path.
See IMA Link List window
IMA_T IMA Termination
It represents the termination of an IMA link.
IMA/VP_A IMA to Virtual Path Adaptation

It represents the termination of an IMA transmission path.
3AG 86577 ABAA Ed3 669/725

9 Glossary
Initiator
Initiator gives the access rights on the NAD.
See Operator profile management chapter 1.4.7.1
Interface type
Alcatel
The interface type indicates where the extremities of a transmission path are
located:
NNI : both extremities are on NEs belonging to the same network
ICI : one extremity is on an NE belonging to another network
UNI : one extremity is on an NE belonging to a user network
See Transmission Path List window

Enabled Transmission Path Search window
Soft PVPC List window (Characteristics panel)
Soft PVCC List window (Characteristics panel)
IP Internet Protocol
Originally developed by the Department of Defense to allow dissimilar computers
to be interconnected in a same network, this protocol works in conjunction with
the Transmission Control Protocol (TCP) and is usually identified as TCP/IP.
IP address
This 32-bit address is assigned to hosts using TCP/IP. An IP address belongs to
one of five classes (A, B, C, D or E) and is written as 4 octets separated by
periods (dotted decimal format).
Each IP address consists in a network number, an optional sub-network number

and a host number. A subnet mask is used to extract network and sub-network
information from the IP address.
The format of the IP address is w.x.y.z on 4x8 bits.

ISA Integrated SDH / ATM

Defines a NE that includes SDH and ATM cards allowing it to be used in SDH
and ATM networks.
3AG 86577 ABAA Ed3 670/725

9 Glossary
ISN Interface Service Network

ITU-T International Telecommunications Union Telecommunications

International body of member countries whose task is to define recommendations
and standards related to the international telecommunication industry. The
fundamental standards for ATM have been defined and published by the ITU-T
(formerly CCITT).
Alcatel
LAC Local Access Control

Possible values: Granted / Denied / Post-granted
When the LAC state is Granted, the NE is controlled by another system than 1354
BM, and all the operator requests involving this ATM NE are refused.
When the LAC state is Denied, the 1354 BM controls the ATM NE.
When the LAC state is Post-granted, the operator can acknowledge the ATM NE
possible misalignment (see § 3.2.7), after the LAC State is set to Denied.
See NE / ENE List window (NE panel)
LAN Local Area Network

Network interconnecting devices over a geographically small area, typically in
one building or a part of a building. The most popular LAN type is Ethernet.
LB Loop Back
This function allows the insertion of information data at one location along a PVC
and the return (or loop back) at a different location, without setting the connection
out of service.
LCD Loss of Cell Delineation

Leg
A Leg is a point-to-point unidirectional PVC. Each Leg starts from the same
extremity as the point-multipoints PVC but ends on a specific destination
extremity.
LIF Loss Of IMA Frame

LGN Logical Group Node

It is a single node that represents the lowest level peer groups in the respective
higher-level peer group.
3AG 86577 ABAA Ed3 671/725

9 Glossary
LOC Loss Of Continuity

Logical node
Abstract representation of a peer group or a switching system as a single point.
Alcatel
Main view
The main view is the first window that is displayed at the user interface launching.
See also View.
Main view
Max DBR Class 1

This defines the maximum percentage of bandwidth which can be dedicated to
DBR class 1 traffic contract.
Transmission Path Partitioning window
Max DBR Class U

DBR class U traffic contract.
Max SBR
SBR traffic contract.
Max UBR+
UBR+ traffic contract.
MBS Maximum Burst Size

This negotiated traffic parameter is the maximum time or number of cells for
which the source can transmit the PCR.
3AG 86577 ABAA Ed3 672/725

9 Glossary

Alcatel
MCR Minimum Cell Rate

This negotiated traffic parameter is the minimum cell rate guaranteed by the
network.
MFS Maximum Frame Size

Maximum frame size expressed in cells
MIB Management Information Base
3AG 86577 ABAA Ed3 673/725

9 Glossary
N
NAD Network Access Domain

An NAD defines a set of functional resources (ETP, indirectly transmission paths,
hard PVPC, hard PVCC) that can be accessed by an operator according to its
profile.
Alcatel
See also Operator profile management (chapter 1.4.7.1).
NE Network Element
Generic term to indicate telecommunication equipment.
In this document, NE is used to indicate a NE managed by the 1354 BM, contrary

to an ENE that is not directly managed by the 1354 BM.
The NE is known in the 1354 BM thanks its identifier.
See also NE User Label
NE Bit Rate
This defines the bit rate characteristic implemented on the ATM NE. The NE bit
rate value can be VC-12, VC-3, VC-4, VC-4-4c (only for 8 x 8 cards), 2 Mb/s or
34 Mb/s.
See also Bit rate.
NE User Label
This identifies a NE.
Fault Localization List window (transmission path)

Fault Localization List window (hard PVPC)
Fault Localization List window (hard PVCC)
NE Search window
Available NE Search window
NE Adding window
NE Modifying window
3AG 86577 ABAA Ed3 674/725

9 Glossary


Hard PVPC Search / Hard PVCC Search windows
Alcatel
Hard PVPC NIM List / Hard PVCC NIM List windows

Hard PVPC Leg NIM List / Hard PVCC Leg NIM List windows
Soft PVPC Description Search / Soft PVCC Description Search windows
NE Search (Administration) window
PNNI Node ATM Address Configuration window
Termination Transmission Characteristics Audit window
NE List (Plug & Play) window
NE Search (Plug & Play) window
NE Technology
This defines the technology characteristic implemented on the ATM NE. The NE
technology value can be SDH or PDH.
See also Technology.
NIM Non-Intrusive Monitoring

This provides a capability for assessing the status, the connectivity, or the
performance of a VPC (end-to-end or segment) at intermediate point. The defined
non-intrusive monitoring functions are: VP AIS/RDI state detection (called NIM)
and Loss of Continuity defect detection (called NIM CC).
These functions may be activated/deactivated separately per VPC. They are non-
intrusive in sense that, when activated, the ATM cell transfer performance of the
PVC should not be affected.
See also Hard PVPC NIM List window
Hard PVPC NIM CC List window
Hard PVCC NIM List window
Hard PVCC NIM CC List window
3AG 86577 ABAA Ed3 675/725

9 Glossary
NML Network Management Layer

Abstraction of the functions provided by systems which manage NEs on a

collective basis, so as to monitor and control the network end-to-end.
NNI Network-to-Network Interface

See Interface type.
Alcatel
OAM Operation And Maintenance

Group of network management functions that provide network fault indication,
performance information, and data and diagnosis functions.
Operational state
It represents the capability to support traffic.
The operational state indicates:

- either the accessibility of an NE:
This state is computed by the 1354 BM and deduced from three information:
- NE supervision state (sent by 1353 NM),
- NE operation state (sent by 1353 NM),
- EML link state (managed by 1354 BM).
- either the transmission path capability to support soft PVCs.
The operational state can be Enabled or Disabled.
For a NE, the operational state changes to Disabled when the NE is unreachable.
For a transmission path, the operational state changes to Enabled as soon as the
transmission path is configured.

NE Search window
Output shaping
The purpose of the output shaping function is to delay some cells in order not to
overflow the negotiated PCR. This function may be activated on a PVC by the
operator.
For more information about the shaping protection mode, refer to chapter 1.4.2.5
3AG 86577 ABAA Ed3 676/725

9 Glossary
Overbooking
The overbooking functionality is the capability to allocate more bandwidth than

the physical line allows.
Overbooking is not allowed for DBR Class 1 connections.
See also chapter 1.4.2.7
Alcatel
Overbooking factor
Overbooking factor could be configured at transmission path level
It must be in the range [100, 1000]:

Equal to 100% means overbooking is not enable.
Greater than 100% means that NE admits more connections than usual. Cell
loss and cell delay guarantees are forfeited for all connections.
Example: Overbooking factor equal to 200% means that the reserved bandwidth is
divided by 2.
See also Transmission Path Configuration window
Transmission Path Modification window
Parent sub-network
The parent sub-network of a sub-network (or a NE or an ENE or a transmission
path) is the sub-network that contains it.
Parent Sub-network User Label

This identifies a parent sub-network.

Sub-network Search window
NE Search window
NE Adding window
ENE Search window
ENE Creation window
3AG 86577 ABAA Ed3 677/725

9 Glossary

Hard PVPC / PVCC Search windows

Soft PVPC / PVCC List windows (Description panel)
Soft PVPC / PVCC Description Search windows
Alcatel

PCR Peak Cell Rate

This negotiated traffic parameter is the maximum bit rate that may be transmitted
from a source.
PDH Plesiochronous Digital Hierarchy

Network technology that has been developed to carry digitalised voice over
twisted pairs.
PGL Peer Group Leader

Single real physical system which has been elected to perform some of the
functions associated to a logical group node.
PM Performance Monitoring
The performance monitoring consists in informing the user about possible default
on a NE or in a PVC.
PMDS Performance Monitoring Display System
Application allowing the visualization of PM ATM counters (refer to § 2.2.4).
PNNI Private Network-to-Network Interface

The PNNI defines the organization of the peer groups used in the soft routing.
PNNI node state

The PNNI node state reflects the capability of a NE to be used as a logical node in
the PNNI management.
3AG 86577 ABAA Ed3 678/725

9 Glossary
The PNNI node state can be:

Enabled if the NE has been activated as a PNNI node (see chapter 7.1.4)
Disabled if the NE is not activated
NE properties window
Alcatel
Port Label
See Adjacent NE.

ETP List window
Provisioning state
The provisioning state indicates the status of a PVC during the PVC management.
For a hard point-to-point PVC, the provisioning state can be Defined, Allocated,
implemented, or Commissioned.
For a point-multipoints PVC, the provisioning state depends of the state of its
Legs. It can be Defined, Allocated, partially Allocated, Implemented, partially
Implemented, Commissioned or partially Commissioned.
For a soft PVC, the provisioning state can be Defined, Establishing or

Established.

Soft PVPC List window (Description panel)
Soft PVPC Description Search window
Soft PVCC List window (Description panel)
Soft PVCC Description Search window
PVC Permanent Virtual Circuit

This is a link with static route defined in advance, usually by manual set-up.
PVCC Permanent Virtual Channel Connection

A permanent VCC is a VCC which is provisioned through some network
management functions and left up indefinitely.
3AG 86577 ABAA Ed3 679/725

9 Glossary
PVCC User Label

This identifies a hard or soft PVCC.

Hard PVCC Definition window
Alcatel
Hard PVCC Modification window

Hard PVCC Extremities window
Hard PVCC Properties window
Hard PVCC Traffic Properties window
Hard PVCC Routing Properties window
Soft PVCC List window (Description panel)
Soft PVCC Description Search window
Soft PVCC Modification window
Soft PVCC Properties window
Soft PVCC Traffic Properties window
PVPC Permanent Virtual Circuit Path Connection

A permanent VPC is a VPC that is provisioned through some network
management function and left up indefinitely.
PVPC User Label

This identifies a hard or soft PVPC.

Hard PVPC Definition window
Hard PVPC Modification window
PVPC Output Shaping Activation window (for a hard PVPC)
Hard PVPC Extremities window
Hard PVPC Properties window
Hard PVPC Traffic Properties window
Hard PVPC Routing Properties window
Soft PVPC List window (Description panel)
Soft PVPC Description Search window
Soft PVPC Definition window
Soft PVPC Modification window
3AG 86577 ABAA Ed3 680/725

9 Glossary


PVPC Output Shaping Activation window (for a soft PVPC)
Soft PVPC Extremities window
Soft PVPC Properties window
Soft PVPC Bandwidth Load window
Alcatel
Soft PVPC Traffic Properties window

Q
QoS Quality of Service

The QoS is associated to the ATC to define a traffic contract.
The QoS is defined by the CDV, CLR, CLP and CTD parameters.
Five classes are defined depending on the use of one or several of these
parameters:
class 1: stringent class that defines bounds on the CTD, CDV, CLR for CLP 0+1
cell flow, (for circuit emulation, CBR video)
class 2: tolerant class that defines a bound on the CLR for CLP 0+1 cell flow, (for
VBR audio and video)
class 3: bi-level class that defines a bound on the CLR for CLP 0 cell flow,
(circuit switched data traffic)
class 4: stringent bi-level class that defines bounds on the CTD, CDV, CLR for
CLP 0 cell flow (for circuitless data traffic)
class U: unspecified, that does not define any bound
See also Traffic contract.
RDI Remote Defect Indication

Re-routing
See Transmission mode.
3AG 86577 ABAA Ed3 681/725

9 Glossary
RM 1354 RM
When ticked, a RM check box indicates that a network component is managed by

the 1354 RM.

NE Adding window
Alcatel

NE List (Plug & Play) window
Routing Service Type

The routing service type indicates whether a transmission path will be used to
support hard or soft PVCs.
So the routing service type can be Hard or Soft.

S
SBR Statistical Bit Rate

ITU-T designation that corresponds to VBR for the ATM Forum.
See also ATC.
SCR Sustained Cell Rate
Sustainable cell rate at which cells will be sent
SDH Synchronous Digital Hierarchy

International standard for defining a network technology that allows the
transmission of information over optical fibres.
SDH NE Label
See Adjacent NE.
ETP List window

3AG 86577 ABAA Ed3 682/725

9 Glossary
SDH-NML
Corresponds to the 1354 RM application.
SDH TTP
Defines an extremity of a transmission path.
Alcatel
See also SDH, TTP and figure 1-8.
Service type
This text field is associated with the Description field to identify a traffic profile.
See also Description and Traffic profile.
Shaping (Protection) Mode

This parameter is used in the output shaping function. There are three available
options:
Grooming: the output shaping is activated only at the extremity of a terminated
PVPC (source point)
Edge: the output shaping is activated only at the edge of the network (network
means “managed by the BM”). In this case, there is no impact about the quality
of the PVPC.
Grooming + Edge: the output shaping is activated on all the available points
(source and last NE)
PVPC Output Shaping Activation window (for a hard PVPC)
PVPC Output Shaping Activation window (for a soft PVPC)
Shaping state
The shaping state indicates if the output shaping function is activated (Enabled) or
not (Disabled).

3AG 86577 ABAA Ed3 683/725

9 Glossary
Site Label
See Adjacent NE.
ETP List window

Alcatel
SMF System Management Functions

Application in charge of the management of the 1354 BM system.
SML Service Management Layer

Abstraction of the functions provided by systems which supply services used in
the network management.
SNMP Simple Network Management Protocol

Originally designed for the Department of Defense network to support TCP/IP
network management, this protocol has been widely implemented to support the
management of a broad range of network products and functions.
State
NE state
Operational State: Enabled/Disabled
It represents the NE accessibility. The operational state changes to disabled

when the NE is unreachable. This state is computed by the 1354 BM
Consistency State: Consistent / Not Consistent
It is computed on checking with the 1353 NM information. The consistency

state change to No Consistent in the case of mismatch of NE parameters or
mismatch NE assignment state, between 1354 BM and 1353 NM.
PNNI Node State: Enabled / Disabled
The PNNI node state reflects the capability of a NE to be used as a logical node
in the PNNI management.
LAC State: None / Denied / Granted / Post Granted
This state indicates if operations from the 1354 BM are authorized or not.
Alarm State
The alarm state corresponds to the presence of alarms.
Activity State: None / Align. In Progress / Synchro. In Progress
3AG 86577 ABAA Ed3 684/725

9 Glossary
This state indicates if an audit/alignment or a synchronisation (if the NE is

managed by the 1354 RM) is in progress on the NE.
The activity state changes to Synchro. In Progress (only if the NE is managed

by the 1354 RM) at the NE definition or after a 1354 RM isolation or after a
Plug & Play procedure when the 1354 BM uploads, from the 1354 RM, the
transmission paths associated to this NE, recovers the alarms and status of
Alcatel
these transmission paths.
Transmission Path State
Operational State: Enabled/Disabled
It represents the transmission path capability to support hard and/or soft

PVPCs. It is enabled if its connection characteristics have been defined
Administrative State: Unlocked / Locked
It reflects the operator decision concerning the use of the transmission path for
cell transport by hard PVPC. If the administrative state is locked, the
transmission path is excluded from the routing algorithm during the allocation
of a hard PVPC (no impact on the existing hard
Usage State: Idle / Busy / Reserved / None
It changes to busy if the transmission path carries at least one hard PVPC and
changes to idle when no more hard PVPC is carried by the transmission path.
This state is computed by the 1354 BM
Activity State: None / CreationInProgress / DeletionInProgress
During creation/deletion phase, a request is sent to the 1354 RM to

create/delete the Transmission Path if the two extremities of the Transmission
Path are managed by the RM.
Activity state is set to CreationInProgress/DeletionInProgress until the 1354

BM receives a notification from the 1354 RM. After reception, activity state is
set to None.
Consistency State: Consistent / Not consistent / Indeterminate
When the Transmission Path is managed by the 1354 RM, Indeterminate state
indicates that the link is cut between the 1354 BM and the 1354 RM.
Hard PVPC state
Administrative State: unlocked / locked

It reflects the operator decision concerning the use of the hard PVPC for cell
transport by hard PVCC. If the administrative state is locked then no more hard
PVCC can be allocated / implemented on the hard PVPC (no impact on the
already implemented hard PVCCs)
3AG 86577 ABAA Ed3 685/725

9 Glossary
Usage State: Idle / Busy / Reserved

It changes to busy if the hard PVPC carries at least one hard PVCC and
changes to idle if no PVCC is carried. This state is computed by the 1354 BM
Provisioning State: Defined / Allocated / Implemented / Commissioned
It indicates the result of the provisioning (updated by the 1354 BM after an

Alcatel
operation)
Hard PVCC state
Provisioning State: Defined / Allocated / Implemented / Commissioned

operation)
Soft PVCC state
Provisioning State: Defined / Established / Establishing

operation)
STM Synchronous Transport Module

STM-1 corresponds to a flow of 155 Mb/s on an SDH line.
SUBM Submarine
Kind of NE.
Sub-network
A sub-network is a group of network elements. Each sub-network is linked up
with a sub-network or with the main network. A sub-network may contain some
sub-networks, NEs and/or ENEs.
Sub-network User Label

This identifies a sub-network.

Sub-network Search window
Sub-network Modification window
Sub-network Deletion window
SVC Switched Virtual Connection

This is a connection established by signaling. The user defines the endpoints when
the call is initiated.
3AG 86577 ABAA Ed3 686/725

9 Glossary
Synchronize NE terminations
The characteristics of the ATM ports found in the ATM NE replaces the
characteristics found in the 1354 BM.
See Synchronize the NE terminations function (chapter3.2.6)
T
Alcatel
TCA Threshold Crossing Alarm
Technology
Defines the way used to transmit information in a network.
The network technology can be SDH or PDH.
At the ETP creation time, the technology is not yet defined (value “-“ in the list
windows). The technology is defined during the transmission path creation.

ETP List window
Termination
Transmission path extremity located on a NE.
The maximum number is 16 terminations for a 4 x 4 card, 32 for a 8 x 8 card, 252

for a 4x4 enhanced card.
Termination Id. Termination Identifier

This identifies a termination.

TP Label Termination Point Label

See Adjacent NE.
ETP List window

3AG 86577 ABAA Ed3 687/725

9 Glossary

TP/IMA_A Transport Path to IMA Adaptation

This represents the adaptation of the SDH TTP at ATM card level (for IMA
functionality).
Alcatel
TP_T Transmission Path Termination

A TP_T is represented by an SDH TTP associated to a TP/VP_A.
TP/VP_A Transport Path to Virtual Path Adaptation

This represents the adaptation of the SDH TTP at ATM card level.
Traffic contract
A traffic contract is defined by the couple ATC - QoS
Hard PVPC / Hard PVCC / Soft PVPC / Soft PVCC Traffic Properties windows
Hard PVPC / Hard PVCC List windows
Hard PVPC Search / Hard PVCC Search windows
Soft PVPC / Soft PVCC List windows (Description panel)
Soft PVPC / Soft PVCC Description Search windows
Traffic Descriptor Search window
3AG 86577 ABAA Ed3 688/725

9 Glossary
Traffic contracts standards

The ATM Forum Specification on Traffic Management defines the ATM traffic
contracts as associations between ATM services and Conformance Definitions.
The following table provides a comparison between the ITU-T and ATM Forum
terminology:
Alcatel
ATM TRAFFIC TYPE QoS CLASS HARD HARD SOFT SOFT

ITU-T
FORUM PARAMETER PARAMETER VPC VCC VPC VCC
DBR Class 1 CBR.1 PCR0+1, CDVT CTD =< 400ms, CDV =< C C C C
3ms, CLR0+1 < 1.10-9
DBR Class 2 - PCR0+1, CDVT CLR0+1 < 1.10-5 C C - C
DBR Class U UBR.1 PCR0+1, CDVT Without tagging C F or C C F or C

(UBR.1)
DBR Class U UBR.2 PCR0+1, CDVT With tagging C F or C C F or C

(UBR.2)
SBR.1 Class 1 rt-VBR.1 PCR0+1, CDVT, CTD =< 400ms, CDV =< C C C C
SCR0+1, MBS 3ms, CLR0+1 < 1.10-9
SBR.1 Class 2 nrt-VBR.1 PCR0+1, CDVT, CLR0+1 < 1.10-5 C C C C

SCR0+1, MBS
SBR.2 Class 3 nrt-VBR.2 PCR0+1, CDVT, SCR0, CLR0 < 1.10-5 C C C C

MBS
SBR.3 Class 3 nrt-VBR.3 PCR0+1, CDVT, SCR0, CLR0 < 1.10-5 C C C C

MBS
- GFR.2 PCR0+1, CDVT, Minimum CLR/FLR for - F - -

MCR0, MBS, MFS high priority cells/frames
UBR+ UBR+ PCR0+1, CDVT, With tagging C F - -

MCR0,
In column Hard PVC / VCC, Soft VPC / VCC: C means Cell based and F means
Frame based.
3AG 86577 ABAA Ed3 689/725

9 Glossary
Traffic descriptor
A traffic descriptor is defined by:
a traffic descriptor identifier
a traffic contract
traffic parameters (MCR, SCR, PCR, MBS and MFS) and associated tolerances
Alcatel
(CDV for PCR)
Traffic Descriptor User Label

This identifies a traffic descriptor.
Hard PVPC / Hard PVCC / Soft PVPC / Soft PVCC Traffic Properties windows
Traffic profile
A traffic profile is defined by:
a service type
a description
a transmission mode
one or two traffic descriptors, according to the transmission mode:
− the forward traffic descriptor is used alone in an uni-directional hard VPC
− the backward traffic descriptor is only used in a bi-directional hard VPC, in
addition to the forward traffic descriptor
Hard PVPC Definition window
Transmission mode
The transmission mode defines for a traffic profile:
the direction
the allocation type
the re-routing capability
Transmission path
A transmission path is defined as a bi-directional cell flow exchanged between
two associated termination points and represents the ATM physical links
providing the transport of the ATM traffic.
A transmission path is supported by an SDH path with at least one extremity

ending on an ATM NE.
A transmission path can be declared as an IMA transmission path (=IMA group).

It is composed of IMA links and used by several VPs (see chapter 1.3.3).
3AG 86577 ABAA Ed3 690/725

9 Glossary
Transmission Path User Label

This identifies a transmission path.

ETP List window
Alcatel
Transmission Path List / Search windows

TTP Trail Termination Point

Extremity point of an SDH path.
TTP User Label

See User label.
Type
Defines the type of the ATM card.
Card4x4 represents an ATM card supporting an ATM matrix equivalent to a 4x4

STM-1 matrix and supports up to 16 ports.
Card8x8 represents an ATM card supporting an ATM matrix equivalent to a 8x8

STM-1 matrix and support up 32 ports.
Card4x4_E is an enhanced version of ATM card 4x4 designed to support until

252 E1/VC-12 ports required for UMTS applications, with IMA functionality and
DS3 interfaces.
Card4x4_D3 supports up to 16 ports, with IMA functionality and DS3 interfaces.

NE Search window
Available NE Search window
3AG 86577 ABAA Ed3 691/725

9 Glossary

UBR Unspecified Bit Rate

UBR is an ATM service category. The traffic is not sensitive to delay or
bandwidth availability; it essentially uses what is available. An example of this
Alcatel
traffic is a massive file transfer such as a system backup.
UBR+ Unspecified Bit Rate+

UBR+ is a new ATM service category for improve the performance of TCP over
ATM-UBR service.
UBR+ connections can only be hard-PVC.
UBR+ with MDCR=0 connections are equivalent to UBR connections.
UNI User Network Interface

See Interface type.
Unitary PVC
PVC not cross-connected (only made of one VPL/VCL)
UPC / NPC Usage Parameter Control / Network Parameter Control

The purpose of the UPC / NPC is to verify on a PVC if the user respects its traffic
contract.
For more information about the UPC/NPC management, refer to chapter 1.4.2
UPC / NPC state

The UPC / NPC state indicates if the UPC / NPC function is activated (Enabled)
or not (Disabled).
Hard PVPC / Hard PVCC List window

Soft PVPC / Soft PVCC List window (Characteristics panel)
Upload NE terminations
This function explicitly asks RM to provide for each NE selected its terminations
list. The 1354 BM database is updated with the retrieved information.
See Upload NE terminations function (chapter 3.2.5)
Usage state
The usage state gives information about the use of an ATM resource (termination,
ETP, transmission path, hard PVPC).
3AG 86577 ABAA Ed3 692/725

9 Glossary
The usage can be Idle, Busy or Reserved.

The usage state of a termination (or an ETP) changes to Busy if this termination
(or ETP) supports a transmission path.
The usage state of a transmission path changes to Busy if this transmission path
carries at least one hard or soft PVC.
Alcatel
The usage state of a hard PVPC changes to Busy if this PVPC carries at least one
hard PVCC.
The usage state changes to Reserved during Plug & Play discovery phase until
Plug & Play recovery phase.

ETP List window
ETP Search window
Termination Search (Administration) window
User label
A User Label is a string of alphanumeric characters used to identify (in a unique
way) an element of the network. It may be composed of the following fields:
<ISA NE label> / rrsbb where:
<ISA NE user label> may be <site> <NE> with:
− <site> is a name defining the equipment location
− <NE> is a name defining the ISA NE
− rr is the index of the rack where the board takes place
− s is the index of the sub-rack
− bb is the index of the board in the NE
See A NE User Label
See ENE User Label
See ETP User Label
See NE User Label.
See Parent Sub-network User Label
See PM Measure User Label
See PVCC User Label
3AG 86577 ABAA Ed3 693/725

9 Glossary
See PVPC User Label

See Sub-network User Label
See Termination User Label
See Transmission Path User Label

Alcatel
See Z NE User Label
Utilization factor
Utilization factor could be at VPL level during the hard PVPC definition and at
VCL level during the hard PVCC definition (not allowed for Soft PVCC).
It can have a value from 1% to 100% (default value = 100%).

Equal to 100% means the reserved bandwidth is used at 100%.
Less than 100% means a reduction of the reserved bandwidth of the concerned
hard PVPC/PVCC.
For the hard PVPC (which contains the hard PVCC with utilization factor
modified), it permits to create more hard PVCCs.
divided by 2.
See also Hard PVPC / Hard PVCC Definition window
Hard PVPC / Hard PVCC Modification window
V
VBR Variable Bit Rate

ATM service type that supports variable bit rate data traffic with average and peak
traffic parameters.
See also ATC.
VC Virtual Channel
Logical channel created to ensure reliable communication between two network
devices. A virtual channel is defined by a Virtual Path Identifier (VPI)/Virtual
Channel Identifier (VCI) pair, and can be either permanent (PVC) or switched
(SVC).
VCC Virtual Channel Connection

A VCC is part of an ATM connection where switching is performed on the
VPI/VCI fields of each cell.
3AG 86577 ABAA Ed3 694/725

9 Glossary
See also PVCC.

VCI Virtual Channel Identifier

Sixteen-bit field of the ATM cell header that identifies the virtual channel over
which the cell has to travel.
Alcatel

Hard PVCC Extremities window
VCI range
Numerical value giving the range of the VPI.
See Transmission Path Configuration window.

Soft PVPC Bandwidth Load window
VCL Virtual Channel Link

A VCL identifies a PVPC and the VCI used on it.
VCL_T Virtual Channel Link Termination

Extremity of a VCL.
VC_T Virtual Channel Termination

Extremity of a PVCC.
Version
Release number of the ATM card
The format is x.y

View
The 1354 BM user interface uses a main view and some graphical views.
See also Main view and Graphical view.
3AG 86577 ABAA Ed3 695/725

9 Glossary
VN Virtual Network
A virtual network is a set of functions and resources associated to a customer.
VP Virtual Path
Unidirectional logical association or set of VCs.
Alcatel
VPC Virtual Path Connection

A VPC is an ATM connection where switching is performed only on the VPI field
of each cell.
See also PVPC.
VPI Virtual Path Identifier

Eight-bit field of the ATM cell header that identifies the virtual path over which
the cell has to travel.
VPI range
Numerical value giving the range of the VPI.
See Transmission Path Configuration window.

VPL Virtual Path Link

A VPL identifies a transmission path and the VPI used on it.
VPL_T Virtual Path Link Termination

Extremity of a VPL.
VP_T Virtual Path Termination
Extremity of a PVPC.
VP shaped
A VP shaped is a hard PVPC with the output shaping activated.
VP tunnel
A VP tunnel is a hard PVPC dedicated to the soft PVCC.
3AG 86577 ABAA Ed3 696/725

9 Glossary
WS Work Station
Alcatel
WDM Wavelength Division Multiplex

X
Y
Z
Z NE User Label
This identifies the destination (NE or ENE) of a transmission path.

Soft PVPC / PVCC List window (Description panel)
3AG 86577 ABAA Ed3 697/725

Alcatel
9 Glossary
3AG 86577 ABAA Ed3

698/725
Alcatel
10 Appendix
3AG 86577 ABAA Ed3

10 Appendix
product.
This appendix gives some limitations of the 1354 BM
699/725
10 Appendix
10.1 Limits
This appendix provides a reminder of every limits and constraints that are managed by the
1354 BM application.
Alcatel
Sub-network
Maximum number of sub-networks 500
Maximum number of sub-network levels (by default) 3
Maximum number of NEs/ENEs in one sub-network 75
Maximum number of sub-networks in one sub-network 10
ATM NE
Maximum number of cross-connections supported by the 2047

NE (with 4x4 matrix)

NE (with 4x4 enhanced matrix)

NE (with D3 matrix)

NE (with 8x8 matrix)
ENE
Maximum number of ENEs managed by 1354 BM 500
ATM Transmission path
Maximum number of transmission paths depends of the

ATM matrix.
The number of Transmission Path depends on the number

of NEs, the NEs capacity, and the chosen bit rate (more
VC-12 Transmission Paths can be created than VC-4-c).
ETP
Maximum number of ETPs in one NE 380
3AG 86577 ABAA Ed3 700/725

10 Appendix
IMA
Maximum number of IMA links per IMA transmission 32 E1 or

path for a 4x4 enhanced board VC-12 or
12 VC-3
Alcatel
Maximum number of IMA links per IMA transmission 16 E1 or

path for D3 board VC-12 or
12 VC-3
Maximum number of IMA transmission paths in a 4x4 126

enhanced board
Maximum number of IMA transmission paths in a D3 16

board
Maximum number of ATM interfaces (both physical 252

ports and IMA transmission path) that can be activate at
the same time in a 4x4 enhanced board
Operator profiles
Maximum number of operator profiles 6
Minimum & maximum characters of the operator name 3-8
Minimum & maximum characters for the operator 5-8

password (with at least one digit)
Hard PVCC
Maximum number of constraints (for the Allocation) 30
Hard PVCC Leg
Hard PVPC
Maximum number of shaped PVPC by NE (with 4x4 32

matrix )
3AG 86577 ABAA Ed3 701/725

10 Appendix
Maximum number of shaped PVPC by NE (with 8x8

32+32
matrix)
Minimum PCR value for output shaping 181 c/s
Maximum PCR value for output shaping 91696 c/s

Alcatel
Hard PVPC Leg
Traffic Descriptors
Maximum number of traffic descriptors (by NE) 200
Maximum number of traffic descriptors created by 1354 200

BM operator
Maximum number of traffic descriptors created by 1354 200

BM (it includes traffic descriptor created by 1354 BM
operators and uploaded traffic descriptors (during plug &
play phase))
Values range for PCR 1-

1320754
Values range for CDVT PCR 20 -

20000000
Values range for MCR 1-

1320754
Values range for MBS 0 - 1000
Values range for MFS 0 - 1000
3AG 86577 ABAA Ed3 702/725

10 Appendix
10.2 Command Line Interface syntax
The Abstract Syntax below describes all of the valid CLI command constructions for each 1354 BM
management operation domain.
Alcatel
10.2.1 CLI Services

LOGIN <login> <password>
PAUSE <seconds>
QUIT
SET DATE
SET RECORDER [ <fileName> ]
SET USERLABEL
UNSET DATE
UNSET RECORDER
UNSET USERLABEL
10.2.2 Network Construction
10.2.2.1 NET
COUNT NET
GET NET
GET NET <NETUserLabel>
CREATE NET <parentNetUserLabel> <netUserLabel> <comment>
DELETE NET <parentNetUserLabel> <netUserLabel>
MODIFY NET <oldNetUserLabel> <newNetUserLabel> <comment>
10.2.2.2 NE
COUNT NE
GET NE
GET NE <NEUserLabel>
GET NE AVAILABLE
DEFINE NE <parentSubnetworkUserLabel> <SHOperatorLabel> <NEUserLabel>
<RMFlag>
DELETE NE <parentSubnetUserLabel> <NEUserLabel>
DOWNLOADENABLE <ne_user_label> <value> (value = {true, false, force})
MODIFY NE <oldNEUserLabel> <newNEUserLabel>
MODIFY NE <oldNEUserLabel> <newNEUserLabel> <IngressID> <EgressID>
<LoopbackEnalbed>
10.2.2.3 ENE
COUNT ENE
GET ENE
GET ENE <ENEUserLabel>
CREATE ENE <parentSubnetUserLabel> <ENEUserLabel> <comment>
DELETE ENE <parentSubnetUserLabel> <ENEUserLabel>
MODIFY ENE <oldENEUserLabel> <newENEUserLabel> <comment>
10.2.2.4 TERM
GET TERM <NEUserLabel>
COUNT TERM <NEUserLabel>
CONFIGURE TERM <NEUserLabel> <termId> <bitRate>
3AG 86577 ABAA Ed3 703/725

10 Appendix
DECONFIGURE TERM <NEUserLabel> <termId>

SYNCHRONIZE TERM <NEUserLabel>

UPLOAD TERM <NEUserLabel>
10.2.2.5 ETERM
GET ETERM <ENEUserLabel>
COUNT ETERM <ENEUserLabel>
Alcatel
CREATE ETERM <ENEUserLabel> <firstTermNb> <termRange> <EtpComment>

DELETE ETERM <ENEUserLabel> <ETermId>
MODIFY ETERM <ENEUserLabel> <EtermId> <EtpComment>
10.2.2.6 TRANSPATH
COUNT TRANSPATH
GET TRANSPATH
GET TRANSPATH <transpathUserLabel>
CREATE TRANSPATH <transpathUserLabel> <bitRate> <alarmRsc> <comment> <AEnd>
< AEndTermId > <ZEnd> <ZEndTermId> // for NEs (AEnd = NEUserLabel)
CREATE TRANSPATH <transpathUserLabel> <bitRate> <alarmRsc> <comment>
<AEnd> <AEndTermId> <ZEnd> <ZEndTermId> <EtpComment> <managedByRM> // for
ENEs and not managed by RM
CREATE TRANSPATH <transpathUserLabel> <bitRate> <alarmRsc> <comment>
<AEnd> <AEndTermId> <ZEnd> <ZEndTermId> <EtpComment> <managedByRM>
<siteLabal><NELabel> <portLabel> <TermLabel> // for ENEs and managed by RM
CREATE IMATRANSPATH <imaTranspathUserLabel> <alarmRsc> <comment>
<AEnd> <AEndTermId> <ZEnd> <ZEndTermId> <isZExternal> // for IMA
Transmission Path
CREATE IMATRANSPATH <imaTranspathUserLabel> <alarmRsc> <comment>
<AEnd> <AEndTermId> <ZEnd> <ZEndTermId> <isZExternal> <EtpComment> // for
IMA Transmission Path and ENEZ
DELETE TRANSPATH <transpathUserLabel>
CONFIGURE TRANSPATH <transpathUserLabel> <routingSrv> <interfaceType>

<VPIMin> <VPIMax> <VCIMin> <VCIMax> <dbr2Activated> <gfr2Activated>
<ubrPlusActivated> <sbr1Class1Activated> <otherSbrActivated> <alpha>
CONFIGURE TRANSPATH NIM <neUserLabel> <termId> <layer> <oamDirection>
<createAlarm> //layer=[VPC VCC Both] oamDirection=[AZ ZA Both]
<createAlarm>=[true false]
// For non configured, soft-configured transpaths and for other transpaths

but without cost modification
MODIFY TRANSPATH <oldTranspathUserLabel> <newTranspathUserLabel> <comment>
<dbr2Activated> <gfr2Activated> <ubrPlusActivated> <sbr1Class1Activated>
<otherSbrActivated> <alpha>
// For hard-configured transpaths and with cost modification

MODIFY TRANSPATH <oldTranspathUserLabel> <newTranspathUserLabel> <comment>
<dbr2Activated> <gfr2Activated> <ubrPlusActivated> <sbr1Class1Activated>
<otherSbrActivated> <alpha> <cost>
MODIFY TRANSPATH <oldUserLabel> <newUserLabel> <comment> <dbr2Activated>
<gfr2Activated> <ubrPlusActivated> <sbr1Class1Activated>
<otherSbrActivated> <alpha>
MODIFY TRANSPATH <userLabel> <newEtpComment>
MODIFY IMAGROUP <userLabel> <minImaLinkNum>
LOCK TRANSPATH <transpathUserLabel>

UNLOCK TRANSPATH <transpathUserLabel>
10.2.2.7 IMALINK
GET IMALINK <imaLinkUserLabel>
3AG 86577 ABAA Ed3 704/725

10 Appendix
GET IMALINKLIST <imaTransPathUserLabel>

COUNT IMALINK <imaTransPathUserLabel>
ADD IMALINK <transPathUserLabel> <imaTransPathUserLabel>

REMOVE IMALINK <imaLinkUserLabel> <imaTransPathUserLabel>
10.2.3 Hard PVC Management

Alcatel
10.2.3.1 HARDVPC
GET HARDVPC
COUNT HARDVPC
// HARD VPC Point to Point

DEFINE HARDVPC <vpcUserLabel> <comment> <serviceType> <serviceDesc> <beta>
<isENE> <AEndUserLabel> <ATermId> <AVPI> <isENE> <ZEndUserLAbel> <ZTermId>
<ZVPI>
// HARD VPC Point Multipoint
DEFINE HARDVPC <vpcUserLabel> <comment> <vpcLegUserLabel> <serviceType>
<serviceDesc> <beta> <AEndUserLabel> <AETPId> <AVPI> <ZEndUserLabel>
<ZETPId> <ZVPI>
// For Hard VPCs which provisioning state is defined and for the other VPC
but without cost modification
MODIFY HARDVPC <oldVpcUserLabel> <newVpcUserLabel> <comment> <beta>
// For Hard VPCs which provisioning state is at least allocated
MODIFY HARDVPC <oldVpcUserLabel> <newVpcUserLabel> <comment> <cost> <beta>
DELETE HARDVPC <vpcUserLabel>
// Simple allocation for a hard VPC Point to Point or Point Multipoint

ALLOCATE HARDVPC <vpcUserLabel> <routingMode> <costModel>
// Define and allocation one shot for a shaped Hard VPC Point to Point
ALLOCATE HARDVPC <vpcUserLabel> <comment> <serviceType> <serviceDesc>
<beta> <AIsENE> <AEndUserLabel> <ATermId> <AVPI> <ZIsENE> <ZEndUserLAbel>
<ZTermId> <ZVPI> <shapingProtectionMode> <routingMode> <costModel>
// Define and allocation for a no shaped Hard VPC Point to Point
ALLOCATE HARDVPC <vpcUserLabel> <comment> <serviceType> <serviceDesc>
<ZTermId> <ZVPI>
<routingMode> <costModel>
// Define, allocation and implementation for a shaped Hard VPC Point to

Point
IMPLEMENT HARDVPC <vpcUserLabel> <comment> <serviceType> <serviceDesc>
<ZTermId> <ZVPI> <shapingProtectionMode> <routingMode> <costModel>
// Define, allocation and implementation for no a shaped Hard VPC Point to
Point
IMPLEMENT HARDVPC <vpcUserLabel> <comment> <serviceType> <serviceDesc>
<ZTermId> <ZVPI> <routingMode> <costModel>
// Allocation and Implementation for a Hard VPC Point to Point or Point to
Multipoint
IMPLEMENT HARDVPC <vpcUserLabel> <routingMode> <costModel>
// Simple implementation for a Hard VPC Point to Point or Point to
Multipoint
IMPLEMENT HARDVPC <vpcUserLabel>
COMMISSION HARDVPC <vpcUserLabel>
3AG 86577 ABAA Ed3 705/725

10 Appendix
DEALLOCATE HARDVPC <vpcUserLabel>

DEIMPLEMENT HARDVPC <vpcUserLabel>

DECOMMISSION HARDVPC <vpcUserLabel>

ACTIVATE HARDVPC <vpcUserLabel> OUTPUTSHAPING <shapingProtectionMode>
ACTIVATE HARDVPC <vpcUserLabel> UPCNPC
ACTIVATE HARDVPC <vpcUserLabel> CC <oamDirection> //oamDirection=[AZ ZA
Both]
DEACTIVATE HARDVPC <vpcUserLabel> OUTPUTSHAPING
Alcatel
DEACTIVATE HARDVPC <vpcUserLabel> UPCNPC

DEACTIVATE HARDVPC <vpcUserLabel> CC
LOCK HARDVPC <vpcUserLabel>

UNLOCK HARDVPC <vpcUserLabel>
10.2.3.2 HARDVPCLEG
GET HARDVPCLEG <vpcUserLabel>
COUNT HARDVPCLEG <vpcUserLabel>
// Add Hard VPC Leg

DEFINE HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel> <comment>
<destENEUserLabel> <destETPId> <destVpi> <shapingProtectionModeFlag>
<provisionningState>
MODIFY HARDVPCLEG <vpcUserLabel> <oldVpcLegUserLabel> <newVpcLegUserLabel>

<comment>
DELETE HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel>
// Allocation without broadcast point

ALLOCATE HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel> <routingMode>
<costModel>
// Allocation with broadcast point
ALLOCATE HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel> <routingMode>
<costModel> <broadcastNeUserLabel> <broadcastTpId> <broadcastVpi>
// Allocation and Implementation with a Broadcast Point

IMPLEMENT HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel> <routingMode>
// Allocation and Implementation without broadcast point
IMPLEMENT HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel> <routingMode>
<costModel>
// Simple implementation
IMPLEMENT HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel>
COMMISSION HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel>

DEALLOCATE HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel>
DEIMPLEMENT HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel>
DECOMMISSION HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel>
ACTIVATE HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel> OUTPUTSHAPING
<shapingProtectionMode>
DEACTIVATE HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel> OUTPUTSHAPING
10.2.3.3 HARDVCC
GET HARDVCC
COUNT HARDVCC
// VCC Point To Point
3AG 86577 ABAA Ed3 706/725

10 Appendix
DEFINE HARDVCC <vccUserLabel> <comment> <serviceType> <serviceDesc> <beta>

<isENE> <AEndUserLabel> <ATermId> <AVPI> <AVCI> <IsENE> <ZEndUserLabel>

<ZTermId> <ZVPI> <ZVCI>
// VCC Point Multi Point

DEFINE HARDVCC <vccUserLabel> <comment> <vccLegUserLabel> <serviceType>
<serviceDesc> <beta> <AEndUserLabel> <AETPId> <AVPI> <AVCI> <ZEndUserLabel>
<ZETPId> <ZVPI> <ZVCI>
Alcatel
DEFINE HARDVCC <vccUserLabel> <comment> <vccLegUserLabel> <serviceType>

<serviceDesc> <beta> <AEndUserLabel> <ATPId> <AVPI> <AVCI>
<ZEndUserLabel> <ZTPId> <ZVPI> <ZVCI>
MODIFY HARDVCC <oldVccUserLabel> <newVccUserLabel> <comment> <beta>
DELETE HARDVCC <vccUserLabel>
// Define and allocation for a Hard VCC Point to Point

ALLOCATE HARDVCC <vccUserLabel> <comment> <serviceType> <serviceDesc>
<beta> <isENE> <AEndUserLabel> <ATermId> <AVPI> <AVCI> <AIsENE>
<ZEndUserLabel> <ZTermId> <ZVPI> <ZVCI> <routingMode> <costModel>
// Simple allocation for a hard VPC Point to Point or Point Multipoint
ALLOCATE HARDVCC <vccUserLabel> <routingMode> <costModel>
// Define, allocation and implementation for a Hard VCC Point to Point

IMPLEMENT HARDVCC <vccUserLabel> <comment> <serviceType> <serviceDesc>
<beta> <isENE> <AEndUserLabel> <ATermId> <AVPI> <AVCI> <AIsENE>
<ZEndUserLabel> <ZTermId> <ZVPI> <ZVCI> <routingMode> <costModel>
// Allocation and Implementation for a Hard VCC Point to Point or Point
Multipoint
IMPLEMENT HARDVCC <vccUserLabel> <routingMode> <costModel>
// Simple implementation a Hard VCC Point to Point or Point Multipoint
IMPLEMENT HARDVCC <vccUserLabel>
COMMISSION HARDVCC <vccUserLabel>

DEALLOCATE HARDVCC <vccUserLabel>
DEIMPLEMENT HARDVCC <vccUserLabel>
DECOMMISSION HARDVCC <vccUserLabel>
ACTIVATE HARDVCC <vccUserLabel> UPCNPC
ACTIVATE HARDVCC <vccUserLabel> CC <oamDirection> //oamDirection=[AZ ZA
Both]
DEACTIVATE HARDVCC <vccUserLabel> UPCNPC
DEACTIVATE HARDVCC <vccUserLabel> CC
10.2.3.4 HARDVCCLEG
GET HARDVCCLEG <vccUserLabel>
COUNT HARDVCCLEG <vccUserLabel>
// Add Hard VCC LEG

DEFINE HARDVCCLEG <vccUserLabel> <vccLegUserLabel> <comment>
<destENEUserLabel> <destETPId> <destVpi> <destVci> <provisionningState>
MODIFY HARDVCCLEG <vccUserLabel> <oldVccLegUserLabel> <newVccLegUserLabel>

<comment>
DELETE HARDVCCLEG <vccUserLabel> <vccLegUserLabel>
// Allocate without broadcast point

ALLOCATE HARDVCCLEG <vccUserLabel> <vccLegUserLabel> <routingMode>
<costModel>
// Allocate with broadcast point
3AG 86577 ABAA Ed3 707/725

10 Appendix
ALLOCATE HARDVCCLEG <vccUserLabel> <vccLegUserLabel> <routingMode>


<broadcastVci>
// Simple implementation
IMPLEMENT HARDVCCLEG <vccUserLabel> <vccLegUserLabel>
// Allocation and Implementation without broadcast point
IMPLEMENT HARDVCCLEG <vccUserLabel> <vccLegUserLabel> <routingMode>
Alcatel
<costModel>
// Allocation and Implementation with broadcast point
IMPLEMENT HARDVCCLEG <vccUserLabel> <vccLegUserLabel> <routingMode>
<broadcastVci>
COMMISSION HARDVCCLEG <vccUserLabel> <vccLegUserLabel>

DEALLOCATE HARDVCCLEG <vccUserLabel> <vccLegUserLabel>
DEIMPLEMENT HARDVCCLEG <vccUserLabel> <vccLegUserLabel>
DECOMMISSION HARDVCCLEG <vccUserLabel> <vccLegUserLabel>
10.2.4 Soft PVC Management
10.2.4.1 SOFTVPC
GET SOFTVPC
COUNT SOFTVPC
DEFINE SOFTVPC <vpcUserLabel> <comment> <serviceType> <serviceDescr>

<userLabelCallingEnd> <tpIdentCallingEnd> <vpiCallingEnd>
<isCallingEndExternal> <userLabelCalledEnd> <tpIdentCalledEnd>
<vpiCalledEnd> <isCalledEndExternal> <atmAddressCalledEnd>
<userLabelCallingConnexionEnd> <tpCallingConnexionEnd>
<vpiCallingConnexionEnd> <isCallingConnexionEndExternal>
<userLabelCalledConnexionEnd> <tpCalledConnexionEnd>
<vpiCalledConnexionEnd> <isCalledConnexionEndExternal>
DELETE SOFTVPC <vpcUserLabel>
MODIFY SOFTVPC <oldVpcUserLabel> <newVpcUserLabel> <comment>
SETUP SOFTVPC <vpcUserLabel>

RELEASE SOFTVPC <vpcUserLabel>
ACTIVATE SOFTVPC <vpcUserLabel> UPCNPC

DEACTIVATE SOFTVPC <vpcUserLabel> UPCNPC
10.2.4.2 SOFTVCC
GET SOFTVCC
COUNT SOFTVCC
DEFINE SOFTVCC <vccUserLabel> <comment> <serviceType> <serviceDescr>

<userLabelCallingEnd> <tpIdentCallingEnd> <vpiCallingEnd> <vciCallingEnd>
<isCallingEndExternal> <userLabelCalledEnd> <tpIdentCalledEnd>
<vpiCalledEnd> <vciCalledEnd> <isCalledEndExternal> <atmAddressCalledEnd>
<userLabelCallingConnexionEnd> <tpCallingConnexionEnd>
<vpiCallingConnexionEnd> <vciCallingConnexionEnd>
<isCallingConnexionEndExternal> <userLabelCalledConnexionEnd>
<tpCalledConnexionEnd> <vpiCalledConnexionEnd> <vciCalledConnexionEnd>
<isCalledConnexionEndExternal>
DELETE SOFTVCC <vccUserLabel>
3AG 86577 ABAA Ed3 708/725

10 Appendix
MODIFY SOFTVCC <oldVccUserLabel> <newVccUserLabel> <comment>

SETUP SOFTVCC <vccUserLabel>

RELEASE SOFTVCC <vccUserLabel>
ACTIVATE SOFTVCC <vccUserLabel> UPCNPC

DEACTIVATE SOFTVCC <vccUserLabel> UPCNPC
Alcatel
10.2.5 Constraint Management
10.2.5.1 HARDVPC
GET CONSTRAINT HARDVPC <vpcUserLabel>
COUNT CONSTRAINT HARDVPC <vpcUserLabel>
CREATE CONSTRAINT HARDVPC <vpcUserLabel> NE <entityTypeUserLabel>

<isPositive>
CREATE CONSTRAINT HARDVPC <vpcUserLabel> TRANSPATH <entityTypeUserLabel>
<isPositive>
CREATE CONSTRAINT HARDVPC <vpcUserLabel> TRANSPATH <entityTypeUserLabel>
<optionalTerminationIndex>
DELETE CONSTRAINT HARDVPC <vpcUserLabel> NE <entityTypeUserLabel>

<isPositive>
DELETE CONSTRAINT HARDVPC <vpcUserLabel> TRANSPATH <entityTypeUserLabel>
<isPositive>
10.2.5.2 HARDVPCLEG
GET CONSTRAINT HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel>
COUNT CONSTRAINT HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel>
CREATE CONSTRAINT HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel> NE

<entityTypeUserLabel> <isPositive>
CREATE CONSTRAINT HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel> TRANSPATH

// This kind of constraint is always a positive link
CREATE CONSTRAINT HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel> TRANSPATH
<entityTypeUserLabel> <optionalTerminationIndex>
DELETE CONSTRAINT HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel> NE

DELETE CONSTRAINT HARDVPCLEG <vpcUserLabel> <vpcLegUserLabel> TRANSPATH
10.2.5.3 HARDVCC
GET CONSTRAINT HARDVCC <vccUserLabel>

COUNT CONSTRAINT HARDVCC <vccUserLabel>
CREATE CONSTRAINT HARDVCC <vccUserLabel> NE <entityTypeUserLabel>

<isPositive>
CREATE CONSTRAINT HARDVCC <vccUserLabel> HARDVPC <entityTypeUserLabel>
<isPositive>
CREATE CONSTRAINT HARDVCC <vccUserLabel> HARDVPC <entityTypeUserLabel>
<optionalVcIndex>
3AG 86577 ABAA Ed3 709/725

10 Appendix
DELETE CONSTRAINT HARDVCC <vccUserLabel> NE <entityTypeUserLabel>

<isPositive>
DELETE CONSTRAINT HARDVCC <vccUserLabel> HARDVPC <entityTypeUserLabel>

<isPositive>
10.2.5.4 HARDVCCLEG
GET CONSTRAINT HARDVCCLEG <vccUserLabel> <vccLegUserLabel>

Alcatel
COUNT CONSTRAINT HARDVCCLEG <vccUserLabel> <vccLegUserLabel>
CREATE CONSTRAINT HARDVCCLEG <vccUserLabel> <vccLegUserLabel> NE

CREATE CONSTRAINT HARDVCCLEG <vccUserLabel> <vccLegUserLabel> HARDVPC
CREATE CONSTRAINT HARDVCCLEG <vccUserLabel> <vccLegUserLabel> HARDVPC
<entityTypeUserLabel> <optionalVcIndex>
DELETE CONSTRAINT HARDVCCLEG <vccUserLabel> <vccLegUserLabel> NE

DELETE CONSTRAINT HARDVCCLEG <vccUserLabel> <vccLegUserLabel> HARDVPC
10.2.6 Traffic Profile Management
10.2.6.1 DESCRIPTOR
GET DESCRIPTOR
// Traffic descriptor which the frame based value is predefined

CREATE DESCRIPTOR <trafficDescriptorUserLabel> <trafficContract1>
<comment> <PCR> <CDVT_PCR> <MCR> <SCR> <MBS> <MFS>
trafficContract1 = [DBRCLASS-1 DBRCLASS-2 GFR-2 SBR1-CLASS1 SBR1-CLASS2
SBR2-CLASS3 SBR3-CLASS3]
CREATE DESCRIPTOR <trafficDescriptorUserLabel> <trafficContract2>

<frameFlag> <comment> <PCR> <CDVT_PCR> <MCR>
trafficContract2 = [DBRCLASSU-1 DBRCLASSU-2 UBR+]
DELETE DESCRIPTOR < trafficDescriptorUserLabel >
10.2.6.2 PROFILE
GET PROFILE
CREATE PROFILE <serviceType> <description> <comment> <direction>
<forwardTrafficDescriptorUserLabel> <backwardTrafficDescriptorUserLabel>
// direction =Bidir
CREATE PROFILE <serviceType> <description> <comment> <direction>
<forwardTrafficDescriptorUserLabel> // direction =Unidir
MODIFY PROFILE <serviceType> <description> <comment> <direction>
<forwardTrafficDescriptorUserLabel> <backwardTrafficDescriptorUserLabel>
// direction =Bidir
MODIFY PROFILE <serviceType> <description> <comment> <direction>
<forwardTrafficDescriptorUserLabel> // direction =Unidir
DELETE PROFILE <serviceType> <description>
10.2.6.3 PMMEASURE
GET PMMEASURE
COUNT PMMEASURE
3AG 86577 ABAA Ed3 710/725

10 Appendix
// Create a PM Measure
CREATE PMMEASURE <pmMeasureUserLabel> <pmLayer> <granularity>

<startTime> <stopTime> <comment>
pmLayer= [LayerTpath LayerPvpc LayerPvcc LayerPvc]
granularity=[15Min 24H]
startTime/stopTime=[yyyy.mm.dd hh:mm:ss]
Alcatel
// Delete a PM Measure
DELETE PMMEASURE <pmMeasureUserLabel>
// Modify a PM Measure
MODIFY PMMEASURE <oldPmMeasureUserLabel> <newPmMeasureUserLabel>
<startTime> <stopTime> <comment>
// Activate a PM Measure
ACTIVATE PMMEASURE <pmMeasureUserLabel>
// Deactivate a PM Measure
DEACTIVATE PMMEASURE <pmMeasureUserLabel>
COLLECT PMMEASURE <pmMeasureUserLabel>
10.2.6.4 PMTRANSPORT
GET PMTRANSPORT <pmMeasureUserLabel>
COUNT PMTRANSPORT <pmMeasureUserLabel>
// Associate a transport to a PM Measure

ASSOCIATE PMTRANSPORT <pmMeasureUserLabel> <pmTransportUserLabel>
<transportType>
// Dissociate a transport from a PM Measure

DISSOCIATE PMTRANSPORT <pmMeasureUserLabel> <pmTransportUserLabel>
<transportType>
10.2.6.5 REPORT
GET REPORT
COUNT REPORT
// Create a Report Profile

CREATE REPORT <reportProfileUserLabel> <reportKind> <stateReportKind>
<pmLayer> <granularity> <pmFrequency> <outputType> <comment>
<outputName>
<outputName> <receivedCells> <transmittedCells> <invalidHecEvents>
<discardCells> <discardCellsVpiVci>
<outputName> <receivedCells> <transmittedCells> <receivedCellsClp0>
<transmittedCellsClp0> <discardCells> <discardCellsClp0> <taggedCells>
reportKind= [Counter CounterThr TransportState]
stateReportKind= [None ProvState AvailStatus Both]
pmLayer=[LayerTpath LayerPvpc LayerPvcc LayerPvc]
granularity=[15Min 24H]
pmFrequency=[15Min 1H 2H 1D 1W 1M 2M 1Y]
outputType= [File Printer Mail]
// Delete a Report Profile

DELETE REPORT <reportProfileUserLabel>
3AG 86577 ABAA Ed3 711/725

10 Appendix
// Modify a Report Profile

MODIFY REPORT <oldReportProfileUserLabel> <newReportProfileUserLabel>

<pmFrequency> <pmOutputType> <outputName> <comment>
10.2.6.6 TCA
GET TCA
Alcatel
COUNT TCA
10.2.6.7 PP
GET PP <pmMeasureUserLabel> <pmTransportUserLabel> <transportType>
COUNT PP <pmMeasureUserLabel> <pmTransportUserLabel> <transportType>
// Associate a PP
ASSOCIATE PP <neUserLabel> <termId> <VPI> <VCI> <ppType>
<pmMeasureUserLabel> <pmTransportUserLabel> <transportType> ppType=[Tpvpa
vp vc]
transportType=[TranspTpath TranspHardVpc TranspHardVcc TranspSoftVpc
TranspSoftVcc TranspPvpcLeg TranspPvccLeg]
// Dissociate a PP
DISSOCIATE PP <neUserLabel> <termId> <VPI> <VCI> <ppType>
<pmMeasureUserLabel> <pmTransportUserLabel> <transportType>
ppType=[Tpvpa vp vc]
transportType=[TranspTpath TranspHardVpc TranspHardVcc TranspSoftVpc
TranspSoftVcc TranspPvpcLeg TranspPvccLeg]
10.2.6.8 HARDVPCNENIM
GET HARDVPCNENIM <vpcUserLabel>
COUNT HARDVPCNENIM <vpcUserLabel>
CONFIGURE HARDVPCNENIM <vpcUserLabel> <neUserLabel> <ATermId> <AVPI>
<AIngress> <AEgress> <ZTermId> <ZVPI> <ZIngress> <ZEgress>
10.2.6.9 HARDVPCLEGNENIM
GET HARDVPCLEGNENIM <vpcUserLabel> <vpcLegUserLabel>
COUNT HARDVPCLEGNENIM <vpcUserLabel> <vpcLegUserLabel>
CONFIGURE HARDVPCLEGNENIM <vpcUserLabel> <vpcLegUserLabel> <neUserLabel>
<ATermId> <AVPI> <AIngress> <AEgress> <ZTermId> <ZVPI> <ZIngress> <ZEgress>
10.2.6.10 HARDVCCNENIM
GET HARDVCCNENIM <vccUserLabel>
COUNT HARDVCCNENIM <vccUserLabel>
CONFIGURE HARDVCCNENIM <vccUserLabel> <neUserLabel> <ATermId> <AVPI>
<AVCI> <AIngress> <AEgress> <ZTermId> <ZVPI> <ZVCI> <ZIngress> <ZEgress>
10.2.6.11 HARDVCCLEGNENIM
GET HARDVCCLEGNENIM <vccUserLabel> <vccLegUserLabel>
COUNT HARDVCCLEGNENIM <vccUserLabel> <vccLegUserLabel>
CONFIGURE HARDVCCLEGNENIM <vccUserLabel> <vccLegUserLabel> <neUserLabel>
<ATermId> <AVPI> <AVCI> <AIngress> <AEgress> <ZTermId> <ZVPI> <ZVCI>
<ZIngress> <ZEgress>
3AG 86577 ABAA Ed3 712/725

10 Appendix
10.2.6.12 HARDVPCNIMCC
GET HARDVPCNIMCC <vpcUserLabel>

COUNT HARVPCNIMCC <vpcUserLabel>
ACTIVATE HARDVPCNIMCC <vpcUserLabel> <neUserLabel> <termId> <VPI>
<signalMonitoringDirection> //signalMonitoringDirection=[Ingress Egress]
DEACTIVATE HARDVPCNIMCC <vpcUserLabel> <neUserLabel> <termId> <VPI>
Alcatel
10.2.6.13 HARDVCCNIMCC
GET HARDVCCNIMCC <vccUserLabel>
COUNT HARVCCNIMCC <vccUserLabel>
ACTIVATE HARDVCCNIMCC <vccUserLabel> <neUserLabel> <termId> <VPI> <VCI>
DEACTIVATE HARDVCCNIMCC <vccUserLabel> <neUserLabel> <termId> <VPI> <VCI>
10.2.7 Parameter Description

The table below defines, for each kind of command parameter, the range of valid values
and if the values are case-sensitive:
Parameter Values Case

sensitive?
RMFlag, isENE, {true, false}
isPositive, Yes
isMultipoint
Comment Must be delimited by double quotes.
Accepts almost all printable characters Yes
including spaces and line feeds.
BitRate {VC-3, VC-4, VC-12, VC4-4C, E1, E3, DS3}
E1, E3 and DS3 bit rates are only for Yes
termination management purpose.
Techno {SDH, PDH}
Yes
alarmRsc {true, false}
Note : true -> Enabled Yes
false -> Disabled
RoutingSrv {Hard, Soft}
Yes
InterfaceType {ICI, NNI, UNI}
Yes
ShapingProtectionMode {Grooming, Edge, Grooming+Edge}
Yes
ShapingProtectionMode {true, false}
Flag Note : true -> shaped (Edge) Yes
false -> not shaped
PnPFlag {true, false}
Note : true -> only resources recovered by PnP Yes
false -> all resources
Direction {Bidir, Unidir}
Yes
ServiceType, All the predefined Traffic Profiles and the one
serviceDesc created by the operator. Yes
frameFlag {true, false}
Yes
trafficContract1 {DBRCLASS-1, DBRCLASS-2, GFR-2, SBR1-CLASS1,
SBR1-CLASS2, SBR2-CLASS3, SBR3-CLASS3} Yes
3AG 86577 ABAA Ed3 713/725

10 Appendix

sensitive?
trafficContract2 {DBRCLASSU-1, DBRCLASSU-2, UBR+}
Yes
PCR an integer.
required for any trafficContract type
CDVT_PCR an integer.
required for any trafficContract type
Alcatel
MCR an integer.
if trafficContract = UBR+ or GFR-2
MBS an integer.
if trafficContract = GFR-2, SBR1-CLASS1, SBR1-
CLASS2, SBR2-CLASS3 or SBR3-CLASS3
MFS an integer.
if trafficContract = GFR-2
SCR an integer.
if trafficContract = SBR1-CLASS1, SBR1-CLASS2,
SBR2-CLASS3 or SBR3-CLASS3
RoutingMode {Automatic, Semi-automatic, Manual}
Yes
Cost an integer
CostModel {Shortest, Cheapest}
Yes
ProvisionningState {true, false}
Yes
Alpha 100 (default value) up to 1000
Beta 1 up to 100 (default value)
IsCallingEndExternal, {true, false}

isCalledEndExternal, Yes
isCallingConnexionEnd
External,
isCalledConnexionEndE
xternal
Dbr2Activated, {true, false}
gfr2Activated, Yes
UbrPlusActivated,
sbr1Class1Activated
otherSbrActivated
PmLayer (LayerTpath, LayerPvpc, LayerPvcc, LayerPvc)
Yes
Granularity (15Min, 24H)
Yes
StartTime Yyyy.mm.dd hh:mm:ss
Yes
StopTime Yyyy.mm.dd hh:mm:ss
Yes
TransportType (TranspTpath, TranspHardVpc, TranspHardVcc,
TranspSoftVpc, TranspSoftVcc, TranspPvpcLeg, Yes
TranspPvccLeg)
ReportKind (Counter, CounterThr, TransportState)
Yes
StateReportKind (None, ProvState, AvailStatus, Both)
Yes
PmFrequency (15Min, 1H, 2H, 1D, 1W, 1M, 2M, 1Y)
Yes
OutputType (File, Printer, Mail)
PpType (Tpvpa,vp,vc)
Yes
SignalMonitoringDirec (Ingress,Egress)
tion Yes
3AG 86577 ABAA Ed3 714/725

10 Appendix

sensitive?
Aingress,Aegress,ZIng {true, false}
ress,ZEgress Yes
Layer (VPC, VCC, Both)
Yes
createAlarm (true,false)
Alcatel
3AG 86577 ABAA Ed3 715/725

10 Appendix
10.3 User Profile Management
The following table presents the set of operations available for each user profile.
Alcatel
ADMINISTRATOR = ADM A N N V
NETWORK CONSTRUCTOR = NC D C M I
VIEWER = VIEW M E
NETWORK MANAGER = NM W
NETWORK CONSTRUCTION
Sub-network list / search ü ü ü ü
Sub-network creation ü ü
Sub-network modification ü ü
Sub-network deletion ü ü
Sub-network properties ü ü ü ü
NE list / search ü ü ü ü
NE available list / search ü ü
NE definition ü ü
NE modification ü ü
NE deletion ü ü
NE properties ü ü ü ü
Show equipment view ü ü ü ü
ENE list / search ü ü ü ü
ENE creation ü ü
ENE modification ü ü
ENE deletion ü ü
ENE properties ü ü ü ü
3AG 86577 ABAA Ed3 716/725

10 Appendix
Termination list / search ü ü ü ü
Termination definition ü ü
Termination configuration ü ü
Alcatel
Termination de-configuration ü ü
Termination characteristics audit ü ü
Termination upload ü ü
Termination synchronisation with ü ü ü ü

ATM NE
ETP list / search ü ü ü ü
ETP creation ü ü
ETP deletion ü ü
Transmission path list / search ü ü ü ü
Transmission path creation ü ü
IMA transmission path creation ü ü
IMA link list / search ü ü ü ü
IMA link creation / deletion ü ü
Transmission path modification ü ü
Transmission path deletion ü ü
Transmission path configuration ü ü
Transmission path finalization ü ü
IMA Transmission path finalization ü ü
Transmission path loading of the ü ü ü

bandwidth
Transmission path properties ü ü ü ü
3AG 86577 ABAA Ed3 717/725

10 Appendix
ü ü ü ü
Transmission path extremities

Transmission path lock ü ü
Transmission path unlock ü ü
Transmission path partitioning ü ü ü

Alcatel
SDH Path routing discovery ü ü
NETWORK MANAGEMENT: VPC
Hard VPC list / search ü ü ü
Hard VPC definition ü ü
Hard VPC modification ü ü
Hard VPC deletion ü ü
Hard VPC allocation ü ü
Hard VPC de-allocation ü ü
Hard VPC implementation ü ü
Hard VPC de-implementation ü ü
Hard VPC commissioning ü ü
Hard VPC de-commissioning ü ü
Hard VPC routing properties ü ü ü
Hard VPC loading of bandwidth ü ü ü
Hard VPC lock ü ü
Hard VPC unlock ü ü
Hard VPC extremities ü ü ü
Hard VPC properties ü ü ü
Hard VPC traffic properties ü ü ü
Hard VPC constraint list ü ü
Hard VPC constraint addition ü ü
Hard VPC constraint deletion ü ü
3AG 86577 ABAA Ed3 718/725

10 Appendix
Hard VPC Leg list / search ü ü ü
Hard VPC Leg definition ü ü
Hard VPC Leg modification ü ü

Alcatel
Hard VPC Leg deletion ü ü
Hard VPC Leg allocation ü ü
Hard VPC Leg de-allocation ü ü
Hard VPC Leg implementation ü ü
Hard VPC Leg de-implementation ü ü
Hard VPC Leg commissioning ü ü
Hard VPC Leg de-commissioning ü ü
Hard VPC Leg routing properties ü ü ü
Hard VPC Leg extremities ü ü ü
Hard VPC Leg properties ü ü ü
Hard VPC Leg constraint list ü ü ü
Hard VPC Leg constraint addition ü ü ü
Hard VPC Leg constraint deletion ü ü ü
Soft VPC list / search ü ü ü
Soft VPC definition ü ü
Soft VPC deletion ü ü
Soft VPC set-up ü ü
Soft VPC release ü ü
Soft VPC routing properties ü ü
Soft VPC extremities ü ü ü
Soft VPC properties ü ü ü
3AG 86577 ABAA Ed3 719/725

10 Appendix
ü ü ü
Soft VPC traffic properties

Soft VPC loading of bandwidth ü ü ü
NETWORK MANAGEMENT: VCC

Alcatel
Hard VCC list / search ü ü ü
Hard VCC definition ü ü
Hard VCC modification ü ü
Hard VCC deletion ü ü
Hard VCC allocation ü ü
Hard VCC de-allocation ü ü
Hard VCC implementation ü ü
Hard VCC de-implementation ü ü
Hard VCC commissioning ü ü
Hard VCC de-commissioning ü ü
Hard VCC routing properties ü ü ü
Hard VCC extremities ü ü ü
Hard VCC properties ü ü ü
Hard VCC traffic properties ü ü ü
Hard VCC constraint list ü ü ü
Hard VCC constraint addition ü ü ü
Hard VCC constraint deletion ü ü ü
Hard VCC Leg list / search ü ü ü
Hard VCC Leg definition ü ü
Hard VCC Leg modification ü ü
Hard VCC Leg deletion ü ü
Hard VCC Leg allocation ü ü
3AG 86577 ABAA Ed3 720/725

10 Appendix
ü ü
Hard VCC Leg de-allocation

Hard VCC Leg implementation ü ü
Hard VCC Leg de-implementation ü ü
Hard VCC Leg commissioning ü ü

Alcatel
Hard VCC Leg de-commissioning ü ü
Hard VCC Leg extremities ü ü ü
Hard VCC Leg properties ü ü ü
Hard VCC Leg routing properties ü ü ü
Hard VCC Leg constraint list ü ü ü
Hard VCC Leg constraint addition ü ü ü
Hard VCC Leg constraint deletion ü ü ü
Soft VCC list / search ü ü ü
Soft VCC definition ü ü ü
Soft VCC modification ü ü
Soft VCC deletion ü ü
Soft VCC set-up ü ü
Soft VCC release ü ü
Soft VCC routing properties ü ü
Soft VCC extremities ü ü ü
Soft VCC properties ü ü ü
Soft VCC traffic properties ü ü ü
NETWORK MANAGEMENT: PVC UPC/NPC

PVC UPC/NPC activation ü ü
PVC UPC/NPC de-activation ü ü
PVC output shaping activation ü ü
3AG 86577 ABAA Ed3 721/725

10 Appendix
ü ü
PVC output shaping de-activation

NETWORK MAINTENANCE
Fault localization ü ü ü
Alcatel
PERFORMANCE MANAGEMENT
PM Measure list / search ü ü ü ü
PM Measure creation ü ü
PM Measure modification ü ü
PM Measure deletion ü ü
PM Measure association/dissociation ü ü
PM Measure activation/de-activation ü ü
Force data collection on a PM ü ü

Measure
PM Measure properties ü ü
PM Transport list / search ü ü ü ü
NETWORK ADMINISTRATION
Traffic contract profile list / search ü ü ü
Traffic contract profile creation ü ü
Traffic contract profile deletion ü ü
Traffic contract profile modification ü ü
Traffic contract profile properties ü ü ü
Traffic contract profile create from ü ü

operation
Traffic descriptor list / search ü ü ü
Traffic descriptor creation ü ü
3AG 86577 ABAA Ed3 722/725

10 Appendix
ü ü
Traffic descriptor deletion

Traffic descriptor create from ü ü

operation
Alcatel
NE ATM address provisioning ü
Termination ATM addresses ü

provisioning
PNNI NE list / search ü ü
PNNI Termination list / search ü ü
PNNI node activation ü
PNNI node de-activation ü
NE observation ü
NETWORK PLUG AND PLAY
All operations ü
AUDIT / ALIGNMENT / FORCE ALIGNMENT
All operations ü ü
OTHERS GRAPHICAL USER INTERFACE ACTIONS
Select / save map ü ü
Sub-network view manipulation: ü ü ü ü

transmission path
Sub-network view manipulation: VPC ü ü ü

and VCC
Global view manipulation ü
SYSTEM MANAGEMENT (SMF)
All operations (operator creation, ü

deletion, …)
3AG 86577 ABAA Ed3 723/725
10 Appendix
deletion, …)
Operator (view operators, change ü ü ü ü

password, view current login, list
successful/unsuccessful login)
Console (list operator consoles) ü ü ü ü

Alcatel
Log (list system messages, display ü ü ü ü

1354 BM log file)
Periodic action (show scheduling ü ü ü ü

time)
Stop / Start application (show system ü ü ü ü

status, show autostart status)
1354 BM system version ü ü ü ü
1354 BM administration (EML-IMs ü

management, set 1354 BM
parameters)
ALARM SURVEILLANCE (AS)
All operations ü ü ü ü
PERFORMANCE MEASURE DISPLAY SYSTEM (PMDS)
All operations ü ü ü ü
CDE CONFIGURATION
Time/Date ü ü ü ü
Load ü ü ü ü
Text editor / Terminal ü
File manager ü ü ü
3AG 86577 ABAA Ed3 724/725

Alcatel
10 Appendix
3AG 86577 ABAA Ed3

Mail
Printer
Lock, exit
Work space switch
ü
ü
ü
ü
ü
ü
ü
ü
ü
ü
ü
ü
ü
ü
ü
ü
725/725

Atm RM 1354

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Atm RM 1354

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent

1354 BM-ATM | Release 7.1

3AG 86577 ABAA Ed3

ATM boards in OMSN

3AG 86577 ABAA Ed3

not permitted without written authorisation from

1.2.1 1354 BM 1353 NM interface.................................................................................................. 32

3AG 86577 ABAA Ed3 3/725

2.1.7 Buttons .................................................................................................................................... 95

2.1.7.1 Option buttons............................................................................................................................... 95

2.2.3 Starting the Alarm Surveillance GUI ...................................................................................... 101

3AG 86577 ABAA Ed3 4/725

3.2.2.2 Add a NE.................................................................................................................................... 186

not permitted without written authorisation from

3.2.3 Modify a NE........................................................................................................................... 188

3.2.10 Configure a termination..................................................................................................... 197

3AG 86577 ABAA Ed3 5/725

4.1.12 Unlock a hard PVPC ......................................................................................................... 296

4.1.13 Assign NAD Label to a hard PVPC .................................................................................... 297

4.1.19 Deactivate CC on a hard PVPC ......................................................................................... 305

3AG 86577 ABAA Ed3 6/725

4.3.16 Modify the bandwidth of a hard PVCC............................................................................... 403

4.3.17 Display the hard PVCC extremities.................................................................................... 406

4.3.23 Display hard PVCC NE NIM list........................................................................................ 415

3AG 86577 ABAA Ed3 7/725

4.6.6 Release a soft PVCC .............................................................................................................. 504

4.6.7 Display the soft PVCC characteristic list................................................................................ 505

4.6.13 Display the soft PVCC routing properties .......................................................................... 513

6 PERFORMANCE MANAGEMENT ................................................................................................ 520

3AG 86577 ABAA Ed3 8/725

7.2.2 Traffic profile management .................................................................................................... 595

not permitted without written authorisation from

7.2.2.1 Traffic profile list ........................................................................................................................ 597

8 UTILITIES ........................................................................................................................................ 609

10 APPENDIX ....................................................................................................................................... 699

3AG 86577 ABAA Ed3 9/725

not permitted without written authorisation from

Figure 1-1 1354 BM positioning ..................................................................................................................... 27

Figure 1-7 IMA hierarchy ............................................................................................................................... 34

3AG 86577 ABAA Ed3 10/725

Figure 2-30 Performance Counter Tabular window....................................................................................... 113

Figure 2-31 EML-IM List window................................................................................................................. 115

Figure 2-37 1354 BM Log File window......................................................................................................... 121

3AG 86577 ABAA Ed3 11/725

Figure 3-28 Termination Configuration window............................................................................................ 197

Figure 3-29 Confirmation box to de-configure a termination ......................................................................... 198

Figure 3-35 ENE Search window .................................................................................................................. 203

3AG 86577 ABAA Ed3 12/725

Figure 4-2 Hard point-to-point PVPC management chain ............................................................................. 268

Figure 4-3 Hard PVPC provisioning state..................................................................................................... 269

3AG 86577 ABAA Ed3 13/725

Figure 4-70 Confirmation box for deleting several Constraints...................................................................... 335

3AG 86577 ABAA Ed3 14/725

3AG 86577 ABAA Ed3 15/725

Figure 4-185 Hard PVCC Leg Properties window......................................................................................... 450

Figure 4-186 Hard PVCC Leg Routing Properties window............................................................................ 451

3AG 86577 ABAA Ed3 16/725

Figure 6-2 PM Measure chain ...................................................................................................................... 524

Figure 6-3 PM Measure interdependencies ................................................................................................... 525

3AG 86577 ABAA Ed3 17/725

Figure 7-12 PNNI Interface ATM Address Configuration window.................................................................. 584

Figure 7-13 Three ways of encoding ATM Address........................................................................................ 585

3AG 86577 ABAA Ed3 18/725