Lucent Technologies Metropolis DMXplore Alarm Messages And Trouble Clearing Manual
  1. Manuals
  2. Brands
  3. Lucent Technologies Manuals
  4. Multiplexer
  5. Metropolis DMXplore
  6. Alarm messages and trouble clearing manual
Lucent Technologies Metropolis DMXplore Alarm Messages And Trouble Clearing Manual

Lucent Technologies Metropolis DMXplore Alarm Messages And Trouble Clearing Manual

Access multiplexer
Hide thumbs Also See for Metropolis DMXplore:
1
2
Table Of Contents
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
Table of Contents

Advertisement

Quick Links

Download this manual
Metropolis
DMX plore Access
®
Multiplexer
Release 2.1
Alarm Messages and Trouble Clearing Guide
365-372-333 R2.1
CC109572222
Issue 4
June 2005

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Metropolis DMXplore and is the answer not in the manual?

Questions and answers

Related Manuals for Lucent Technologies Metropolis DMXplore

Summary of Contents for Lucent Technologies Metropolis DMXplore

  • Page 1 Metropolis DMX plore Access ® Multiplexer Release 2.1 Alarm Messages and Trouble Clearing Guide 365-372-333 R2.1 CC109572222 Issue 4 June 2005...
  • Page 2 In rare instances, unauthorized individuals make connections to the telecommunications network. In such an event, applicable tariffs require that the customer pay all network charges for traffic. Lucent Technologies and its predecessors cannot be responsible for such charges and will not make any allowance or give any credit for charges that result from unauthorized access.

  • Page 3: Table Of Contents

    BOOKMARK15::1 Safety Overview BOOKMARK16::Overview Structure of hazard statements BOOKMARK17::Structure of hazard statements General notes on safety BOOKMARK18::General notes on safety ..............................................365-372-333 R2.1 Lucent Technologies C O N T E N T S Issue 4, June 2005 i i i...
  • Page 4 DS1 trmsn test IP 3-22 BOOKMARK40::DS1 trmsn test IP DS3 loopback 3-23 BOOKMARK41::DS3 loopback DS3 trmsn test IP 3-25 BOOKMARK42::DS3 trmsn test IP ..............................................C O N T E N T S Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 5 FE-LAN ANM 3-48 BOOKMARK65::inc. FE-LAN ANM inc. FE-LAN LOS 3-49 BOOKMARK66::inc. FE-LAN LOS inc. OCN line AIS 3-50 BOOKMARK67::inc. OCN line AIS ..............................................365-372-333 R2.1 Lucent Technologies C O N T E N T S Issue 4, June 2005...
  • Page 6 3-72 BOOKMARK89::install program IP lockout of protection 3-73 BOOKMARK90::lockout of protection manual reference switch 3-74 BOOKMARK91::manual reference switch manual switch 3-75 BOOKMARK92::manual switch ..............................................C O N T E N T S Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 7 3-95 BOOKMARK112::version mismatch waiting for download 3-96 BOOKMARK113::waiting for download ..............................................Maintenance overview BOOKMARK114::4 Maintenance overview Overview BOOKMARK115::Overview Introduction BOOKMARK116::Introduction ..............................................365-372-333 R2.1 Lucent Technologies C O N T E N T S Issue 4, June 2005 v i i...
  • Page 8 BOOKMARK139::Procedure 5-9: Clear ″DS1 loopback (to DSX)″ condition Procedure 5-10: Clear ″DS1 loopback (to Fiber)″ condition 5-37 BOOKMARK140::Procedure 5-10: Clear ″DS1 loopback (to Fiber)″ condition ..............................................C O N T E N T S Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 v i i i...
  • Page 9 Procedure 5-34: Clear ″inc. VCG LOA″ condition 5-106 BOOKMARK164::Procedure 5-34: Clear ″inc. VCG LOA″ condition Procedure 5-35: Clear ″inc. VT″ conditions/alarms 5-108 BOOKMARK165::Procedure 5-35: Clear ″inc. VT″ conditions/alarms ..............................................365-372-333 R2.1 Lucent Technologies C O N T E N T S Issue 4, June 2005...
  • Page 10 BOOKMARK185::Procedure 5-55: Clear ″VCG Loss of Partial Capacity″ alarm Procedure 5-56: Clear ″version mismatch″ alarm 5-161 BOOKMARK186::Procedure 5-56: Clear ″version mismatch″ alarm ..............................................Supporting procedures BOOKMARK187::6 Supporting procedures Overview BOOKMARK188::Overview ..............................................C O N T E N T S Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 11 BOOKMARK206::Procedure 6-8: Backup and restore NE database via FTP Procedure 6-8.1: Backup NE database via FTP 6-167 BOOKMARK207::Procedure 6-8.1: Backup NE database via FTP ..............................................365-372-333 R2.1 Lucent Technologies C O N T E N T S Issue 4, June 2005...
  • Page 12 Procedure 6-16: Clean pluggable transmission module 6-225 BOOKMARK225::Procedure 6-16: Clean pluggable transmission module ..............................................Glossary GL-1 BOOKMARK226::Glossary ..............................................Index IN-1 BOOKMARK227::Index ..............................................C O N T E N T S Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 x i i...
  • Page 13 4-17 Protection switching priorities (1+1 switch priority = signal failure) 4-17 Synchronization reference protection switch priorities 4-19 Alarm filtering options 4-26 ..............................................365-372-333 R2.1 Lucent Technologies T A B L E S Issue 4, June 2005 x i i i...
  • Page 15 Legal notice 6-28 Network View 6-29 NE login 6-31 NE level legal notice 6-32 Example of System View (graphical) 6-34 CIT OSI neighbor 6-40 ..............................................365-372-333 R2.1 Lucent Technologies F I G U R E S Issue 4, June 2005...
  • Page 16 6-15 Example of inserting a pluggable transmission module into a socket (wall-mounted shelf) 6-211 6-16 Example of inserting a pluggable transmission module into a socket (rack-mounted shelf) 6-211 ..............................................F I G U R E S Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 x v i...

  • Page 17: About This Information Product

    Justification Count parameter of an individual OC-n line. This information product contains hazard statements for your safety. Safety information Hazard statements are given at points where safety consequences to ..............................................365-372-333 R2.1 Lucent Technologies x v i i Issue 4, June 2005...

  • Page 18: Intended Audience

    DMXplore Access Multiplexer Alarm Messages and Trouble Clearing Guide, 365-372-333. Table 1 Chapter contents Chapter Contents Chapter 1, “Safety” This chapter provides important safety information and ® instructions for Metropolis DMXplore..............................................x v i i i Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 19: Conventions Used

    • indicates lettering designations on the backplane, shelf, This font and circuit packs. Example: LED and LED simultaneously light for MN/ABN ACO/TST approximately 12 seconds and then extinguish..............................................365-372-333 R2.1 Lucent Technologies x i x Issue 4, June 2005...

  • Page 20: User Interface To System

    The procedures in Chapter 6, “Supporting procedures” are referenced from multiple procedures to support a job function you are performing. Go to a supporting procedure only when it is referred to ..............................................Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 21: Related Information

    109 572 222 365-372-333 R2.1 Metropolis DMXplore Access Multiplexer Alarm Messages and Trouble Clearing Guide, 365-372-333 ® 109 572 230 365-372-334 R2.1 Metropolis DMXplore Access Multiplexer Installation Manual, 365-372-334 ..............................................365-372-333 R2.1 Lucent Technologies x x i Issue 4, June 2005...

  • Page 22: Information Product Support

    Release Description (Paper) ® 109 574 061 Metropolis DMXplore Access Multiplexer Release 2.1 Documents (CD-ROM) For questions or concerns about this or any other Lucent Technologies Information product support information product, please contact us at one of the following numbers: •...

  • Page 23: How To Comment

    About this information product To order Lucent Technologies information products, contact your local sales representative, use the following websites, or use the email, phone, and fax contacts linked from “Contact Us” on those sites: • Documentation: Lucent’s Product Documentation Web Site (http://www.lucentdocs.com)

  • Page 25: Safety

    This chapter provides important safety instructions for Metropolis Purpose DMXplore. Contents Structure of hazard statements General notes on safety Laser safety Electrostatic discharge 1-13 Save these safety instructions 1-16 ..............................................365-372-333 R2.1 Lucent Technologies 1 - 1 Issue 4, June 2005...

  • Page 26: Structure Of Hazard Statements

    Structure of hazard statements ..............................................Hazard statements describe the safety risks relevant while performing Overview tasks on Lucent Technologies products during deployment and/or use. Failure to avoid the hazards may have serious consequences. Hazard statements include the following structural elements: General structure...
  • Page 27 When used without the personal injury symbol: Indicates a potentially hazardous situation (low risk) which, if not avoided, may result in property damage, such as service interruption or damage to equipment or other materials..............................................365-372-333 R2.1 Lucent Technologies 1 - 3 Issue 4, June 2005...

  • Page 28: General Notes On Safety

    Special safety instructions discharge (ESD) are vitally important to the equipment. For special safety instructions concerning laser safety and electrostatic discharge, refer to sections “Laser safety” (1-7) “Electrostatic discharge” (1-13)..............................................1 - 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 29 Any conversions or changes to the system or parts of the system (including the software) must be carried out by qualified Lucent Technologies personnel or by expert personnel authorized by Lucent Technologies. All changes carried out by other persons lead to a complete exemption from liability.
  • Page 30 • Non-system software is used at one’s own risk. The use/installation of non-system software can adversely affect the normal functioning of the unit/system..............................................1 - 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 31: Laser Safety

    Use only the following Lucent Approved Class 1 SFP transceivers in the VLNC30 Ethernet circuit pack. Name Pluggable Description Transmission Module Code/Comcode OMFE 100BASE-LX-I1 100 Mb/s optical 100BASE-LX-SM Fast Ethernet SFP 109527812 TRCVR ..............................................365-372-333 R2.1 Lucent Technologies 1 - 7 Issue 4, June 2005...
  • Page 32 Optical energies above 1400 nm cause corneal and skin burns, but do not affect the retina. The thresholds for injury at ..............................................1 - 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 33 5 to 6 inches normally will not cause eye injury provided the power in the fiber is less than a few milliwatts at the near IR wavelengths and a few tens of milliwatts at the far IR wavelengths..............................................365-372-333 R2.1 Lucent Technologies 1 - 9 Issue 4, June 2005...
  • Page 34 Optical port shutters and automatic power reduction (APR), and automatic power shut down (APSD) are engineering controls that are also used to limit the emissions..............................................1 - 1 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 35 LED Sources in the United States or outside the United States, IEC-60825, Part 2 for guidance on the safe use of optical fiber optic communication systems in the workplace..............................................365-372-333 R2.1 Lucent Technologies 1 - 1 1 Issue 4, June 2005...

  • Page 36: Laser Warning Labels

    1. Laser symbol. 2. Laser classification label. This label may show only the laser class or both the laser class and the maximum output power. 3. Laser warning label..............................................1 - 1 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 37: Electrostatic Discharge

    Dry air allows greater static charges to accumulate. Higher potentials are measured in areas with low relative humidity, but potentials high enough to cause damage can occur anywhere..............................................365-372-333 R2.1 Lucent Technologies 1 - 1 3 Issue 4, June 2005...
  • Page 38 To reduce the possibility of ESD damage, the Metropolis DMXplore shelf is equipped with an ESD grounding jack to enable personnel to ground themselves using wrist straps (Figure 1-2, “Static control wrist ..............................................1 - 1 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 39: Static Control Wrist Strap

    The following figure shows the barred-hand symbol. Figure 1-3 Electrostatic discharge warning label (barred-hand symbol) MA-metro-429 ..............................................365-372-333 R2.1 Lucent Technologies 1 - 1 5 Issue 4, June 2005...

  • Page 40: Save These Safety Instructions

    This product should be only operated from the type of power sources indicated on the marking label. Connect this product only to the type of power sources recommended by Lucent Technologies. For information on the ® powering instructions, consult the Metropolis DMXplore Access Multiplexer Installation Manual, 365-372-334.
  • Page 41 Do not connect any lightwave cable or splice and stare into the optical connectors terminating the cables. • Lightwave/lightguide operations should not be performed by a technician who has not satisfactorily completed an approved training course..............................................365-372-333 R2.1 Lucent Technologies 1 - 1 7 Issue 4, June 2005...
  • Page 42 Do not staple or otherwise attach the power supply cord to the building surfaces. • Do not overload wall outlets and extension cords as this can result in the risk of fire or electrical shock..............................................1 - 1 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 43 • If the product has been dropped or the cabinet has been damaged. • If the product exhibits a distinct change in performance. SAVE THESE INSTRUCTIONS..............................................365-372-333 R2.1 Lucent Technologies 1 - 1 9 Issue 4, June 2005...

  • Page 45: Alarm List

    Alarm list Overview ..............................................® This chapter contains the alarm list for the Metropolis DMXplore Purpose Access Multiplexer. Contents Alarm list with alarm levels ..............................................365-372-333 R2.1 Lucent Technologies 2 - 1 Issue 4, June 2005...

  • Page 46: Alarm List With Alarm Levels

    AGNE communication failure PRCDRERR “Procedure 5-3: Clear ″AGNE communication failure″ alarm” (5-14) copy program IP No action necessary. CP failed FACTERM “Procedure 6-4: Replace Combination circuit pack” (6-148) ..............................................2 - 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 47: Metropolis ® Dmxplore, Release 2.1 Alarm List

    Clear ″DS1 loopback (to DSX)″ condition” (5-35) DS1 loopback (to Fiber) LPBKNETWORK “Procedure 5-10: Clear ″DS1 loopback (to Fiber)″ condition” (5-37) DS1 trmsn test IP LPBKNETWORK No action necessary..............................................365-372-333 R2.1 Lucent Technologies 2 - 3 Issue 4, June 2005...
  • Page 48 Clear ″far end not LCAS″ condition” (5-55) FE-LAN CP failed FACTERM “Procedure 5-19: Clear ″FE-LAN CP failed″ alarm” (5-58) forced switch WKSWPR-1 “Procedure 5-20: Clear ″forced switch″ WKSWPR-2 condition” (5-60) ..............................................2 - 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 49 (from fiber) DS3 AIS “Procedure 5-26: Clear ″inc. (from fiber) DS3″ inc. (from fiber) DS3 LOF conditions” (5-79) inc. FE-LAN ANM “Procedure 5-27: Clear ″inc. FE-LAN ANM″ alarm” (5-81) ..............................................365-372-333 R2.1 Lucent Technologies 2 - 5 Issue 4, June 2005...
  • Page 50 Clear ″inc. VCG failed″ alarm” (5-100) inc. VCG LFD MISC “Procedure 5-33: Clear ″inc. VCG LFD″ condition” (5-104) inc. VCG LOA MISC “Procedure 5-34: Clear ″inc. VCG LOA″ condition” (5-106) ..............................................2 - 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 51 (5-116) manual switch WKSWPR-1 “Procedure 5-39: Clear ″manual WKSWPR-2 switch″ condition” (5-117) manual sync. mode switch HLDOVRSYNC “Procedure 5-40: Clear ″manual sync. mode switch″ condition” (5-119) ..............................................365-372-333 R2.1 Lucent Technologies 2 - 7 Issue 4, June 2005...
  • Page 52 (5-130) Pluggable Transmission FACTERM “Procedure 5-46: Clear ″Pluggable Module removed Transmission Module removed″ alarm” (5-132) Port administratively disabled “Procedure 5-47: Clear ″Port administratively disabled″ condition” (5-135) ..............................................2 - 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 53 Clear ″unexpected or Pluggable Transmission Module failed Pluggable Transmission Module″ alarm” (5-150) VCG Failure of LCAS VCGFOPR “Procedure 5-54: Clear ″VCG Failure Protocol (Sink) of LCAS Protocol″ alarms” (5-154) ..............................................365-372-333 R2.1 Lucent Technologies 2 - 9 Issue 4, June 2005...
  • Page 54 Standing conditions that are reported with an ABN condition in the alarm list. They are identified on the SYSCTL faceplate with a lighted ABN LED ( MN/ABN) ..............................................2 - 1 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 55: Alarms, Conditions, And Error Messages

    CP removed or CP failure 3-14 CP software upgrade required 3-15 CPY-MEM <class IP 3-16 dormant/exec code mismatch 3-19 DS1 loopback 3-20 DS1 trmsn test IP 3-22 DS3 loopback 3-23 ..............................................365-372-333 R2.1 Lucent Technologies 3 - 1 Issue 4, June 2005...
  • Page 56 OCN line AIS 3-50 inc. OCN LOF 3-51 inc. OCN LOS 3-52 inc. OCN RFI-L 3-53 inc. OCN sig. degrade (BER) 3-54 inc. OCN sig. failed (BER) 3-55 ..............................................3 - 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 57 3-80 NTP server(s) unreachable 3-81 Pluggable Transmission Module removed 3-82 Port administratively disabled 3-83 Remote client signal failed 3-84 remote install/copy program IP 3-85 ring upgrade mode 3-86 ..............................................365-372-333 R2.1 Lucent Technologies 3 - 3 Issue 4, June 2005...
  • Page 58 3-91 VCG Failure of LCAS Protocol (Sink) 3-92 VCG Failure of LCAS Protocol (Source) 3-93 VCG Loss of Partial Capacity 3-94 version mismatch 3-95 waiting for download 3-96 ..............................................3 - 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 59: -48V Power/Fuse Failed

    Alarm Data Value/Meaning Reported Alarm Critical (CR), Major (MJ), Minor (MN) Level(s) AID (type) fuse Date month/day/year that condition was detected Time hour:minute:second that condition was detected Probable Cause ..............................................365-372-333 R2.1 Lucent Technologies 3 - 5 Issue 4, June 2005...
  • Page 60 2-amp fuse for power feed -48V-B blew. Visible Lighted LED on SYSCTL CR/MJ MN/ABN indication faceplate. “Procedure 5-2: Clear ″-48V Action Proceed to power/fuse FA or FB failed″ alarm” (5-11)..............................................3 - 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 61: Abn Condition

    Lighted MN/ABN LED on SYSCTL faceplate. indication Action Located the corresponding Not Alarmed (SC) in the alarm list and proceed to the appropriate procedure to release/clear the condition..............................................365-372-333 R2.1 Lucent Technologies 3 - 7 Issue 4, June 2005...

  • Page 62: Aco Active

    SYSCTL circuit pack faceplate. Visible Lighted LED on SYSCTL faceplate. ACO/TST indication Action No action necessary. Condition clears automatically when a new alarm is detected or all alarms clear..............................................3 - 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 63: Agne Communication Failure

    Likely Cause AGNE has not been provisioned or has failed. Visible Lighted LED on SYSCTL faceplate. CR/MJ indication “Procedure 5-3: Clear ″AGNE Action Proceed to communication failure″ alarm” (5-14)..............................................365-372-333 R2.1 Lucent Technologies 3 - 9 Issue 4, June 2005...

  • Page 64: Copy Program Ip

    Software → Copy Software Visible None. indication Action No action necessary. Condition clears automatically when the generic is copied to the dormant area of the destination NE..............................................3 - 1 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 65: Cp Failed

    CR/MJ MN/ABN LED on SYSCTL indication faceplate and a continuously lighted FAULT on the failed circuit pack. Action Proceed to “Procedure 6-4: Replace Combination circuit pack” (6-148)..............................................365-372-333 R2.1 Lucent Technologies 3 - 1 1 Issue 4, June 2005...

  • Page 66: Cp Not Allowed - Crs

    LED on SYSCTL indication faceplate and a continuously lighted FAULT on the affected circuit pack. “Procedure 5-4: Clear ″CP not allowed Action Proceed to - crs″ alarm” (5-17)..............................................3 - 1 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 67: Cp Not Allowed - Eqpt

    CR/MJ MN/ABN indication faceplate and a continuously lighted FAULT on the affected circuit pack. “Procedure 5-5: Clear ″CP not allowed Action Proceed to - eqpt″ alarm” (5-20)..............................................365-372-333 R2.1 Lucent Technologies 3 - 1 3 Issue 4, June 2005...

  • Page 68: Cp Removed Or Cp Failure

    MN (NSA). Visible Lighted LED on SYSCTL CR/MJ MN/ABN indication faceplate. “Procedure 5-6: Clear ″CP removed or Action Proceed to CP failure″ alarm” (5-23)..............................................3 - 1 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 69: Cp Software Upgrade Required

    Visible Lighted LED on SYSCTL faceplate. MN/ABN indication “Procedure 5-7: Clear ″CP software Action Proceed to upgrade required″ condition” (5-26)..............................................365-372-333 R2.1 Lucent Technologies 3 - 1 5 Issue 4, June 2005...

  • Page 70: Cpy-Mem Ip

    FTAM/FTP gateway (FTTD), or FTAM is in progress. Alarm Data Value/Meaning Reported Alarm Not Alarmed Level(s) AID (type) Blank Date month/day/year that condition was detected Time hour:minute:second that condition was detected ..............................................3 - 1 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 71 Type Description CPY-MEM restore IP cpy-mem Likely Cause User executed the command through the Configuration → ® WaveStar CIT command: Software → Remote Restore Visible None. indication ..............................................365-372-333 R2.1 Lucent Technologies 3 - 1 7 Issue 4, June 2005...
  • Page 72 CPY-MEM <class> IP Alarms, conditions, and error messages Alarm Data Value/Meaning Action No action necessary. Condition clears automatically when the restore is complete..............................................3 - 1 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 73: Dormant/Exec Code Mismatch

    NE. Visible None. indication “Procedure 5-8: Clear ″dormant/exec Action Proceed to code mismatch″ condition” (5-32)..............................................365-372-333 R2.1 Lucent Technologies 3 - 1 9 Issue 4, June 2005...

  • Page 74: Ds1 Loopback

    Alarm Data Value/Meaning Reported Alarm Not Alarmed Level(s) AID (type) DS1 Port Date month/day/year that condition was detected Time hour:minute:second that condition was detected Probable Cause LPBKNETWORK ..............................................3 - 2 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 75 Fault → Loopback ® WaveStar CIT command: Visible Lighted LED on SYSCTL faceplate. MN/ABN indication “Procedure 5-10: Clear ″DS1 loopback Action Proceed to (to Fiber)″ condition” (5-37)..............................................365-372-333 R2.1 Lucent Technologies 3 - 2 1 Issue 4, June 2005...

  • Page 76: Ds1 Trmsn Test Ip

    Fault → Test → ® the WaveStar CIT command: Transmission Visible Lighted MN/ABN LED on SYSCTL faceplate. indication Action No action necessary. Wait for the test to complete..............................................3 - 2 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 77: Ds3 Loopback

    Alarm Data Value/Meaning Reported Alarm Not Alarmed Level(s) AID (type) DS3 Port Date month/day/year that condition was detected Time hour:minute:second that condition was detected Probable Cause LPBKNETWORK ..............................................365-372-333 R2.1 Lucent Technologies 3 - 2 3 Issue 4, June 2005...
  • Page 78 Fault → Loopback ® WaveStar CIT command: Visible Lighted LED on SYSCTL faceplate. MN/ABN indication “Procedure 5-12: Clear ″DS3 loopback Action Proceed to (to Fiber)″ condition” (5-41)..............................................3 - 2 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 79: Ds3 Trmsn Test Ip

    Fault → Test → ® the WaveStar CIT command: Transmission Visible Lighted MN/ABN LED on SYSCTL faceplate. indication Action No action necessary. Wait for the test to complete..............................................365-372-333 R2.1 Lucent Technologies 3 - 2 5 Issue 4, June 2005...

  • Page 80: Duplicate Tid

    Two network elements have the same provisioned target identifier (TID). Visible Lighted CR/MJ LED on SYSCTL faceplate. indication “Procedure 5-13: Clear ″duplicate TID″ Action Proceed to alarm” (5-43)..............................................3 - 2 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 81: Enet Terminal Loopback

    User executed the opr-lpbk command through the Fault → Loopback ® WaveStar CIT command: Visible Lighted LED on SYSCTL faceplate. MN/ABN indication “Procedure 5-14: Clear ″ENET Action Proceed to terminal loopback″ condition” (5-45)..............................................365-372-333 R2.1 Lucent Technologies 3 - 2 7 Issue 4, June 2005...

  • Page 82: Environmentn

    Some external equipment has operated a contact closure connected to that input. Visible Lighted CR/MJ MN/ABN LED on SYSCTL indication faceplate. “Procedure 5-15: Clear ″environmentn″ Action Proceed to alarm” (5-47)..............................................3 - 2 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 83: Excessive Holdover

    Visible indication Lighted LED on SYSCTL faceplate. MN/ABN “Procedure 5-16: Clear ″excessive holdover″ alarm” Action Proceed to (5-49)..............................................365-372-333 R2.1 Lucent Technologies 3 - 2 9 Issue 4, June 2005...

  • Page 84: Fan Shelf Failed

    Likely Cause The fan shelf failed. Visible Lighted LED on SYSCTL CR/MJ MN/ABN indication faceplate. “Procedure 5-17: Clear ″fan shelf Action Proceed to failed″ alarm” (5-52)..............................................3 - 3 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 85: Far End Not Lcas

    VCG. At the far end, LCAS is either not enabled or not supported. Visible None. indication “Procedure 5-18: Clear ″far end not Action Proceed to LCAS″ condition” (5-55) ..............................................365-372-333 R2.1 Lucent Technologies 3 - 3 1 Issue 4, June 2005...

  • Page 86: Fe-Lan Cp Failed

    LED on SYSCTL faceplate and a indication continuously lighted FAULT LED on the failed circuit pack. “Procedure 5-19: Clear ″FE-LAN CP Action Proceed to failed″ alarm” (5-58)..............................................3 - 3 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 87: Forced Switch

    Protection group or Path Protection group, and provisioned the Switch Type as Forced Visible Lighted LED on SYSCTL faceplate. MN/ABN indication “Procedure 5-20: Clear ″forced switch″ Action Proceed to condition” (5-60)..............................................365-372-333 R2.1 Lucent Technologies 3 - 3 3 Issue 4, June 2005...

  • Page 88: Holdover Mode Active

    Visible indication None. “Procedure 5-21: Clear ″holdover mode active″ condition” Action Proceed to (5-62)..............................................3 - 3 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 89: Illegal Cp Type

    MN/ABN LED on SYSCTL indication faceplate and a continuously lighted FAULT on the alarmed circuit pack. “Procedure 5-22: Clear ″illegal CP Action Proceed to type″ alarm” (5-65)..............................................365-372-333 R2.1 Lucent Technologies 3 - 3 5 Issue 4, June 2005...

  • Page 90: Inc. Ds3 Cbit Mismatch

    LED on SYSCTL indication faceplate and a flashing FAULT LED on the alarmed circuit pack. “Procedure 5-24: Clear ″inc. DS3 Cbit Action Proceed to Mismatch″ alarm” (5-71)..............................................3 - 3 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 91: Inc. Ds3 Sig. Out Of Frequency Defect

    Lighted LED on SYSCTL faceplate and a CR/MJ indication flashing LED on the alarmed circuit pack. FAULT “Procedure 5-25: Clear ″inc. DS3″ Action Proceed to conditions/alarms” (5-75)..............................................365-372-333 R2.1 Lucent Technologies 3 - 3 7 Issue 4, June 2005...

  • Page 92: Inc. (From Dsx) Ds1 Ais

    CR/MJ MN/ABN LED on SYSCTL indication faceplate and a flashing FAULT LED on the alarmed circuit pack. “Procedure 5-23: Clear ″inc. DS1″ Action Proceed to conditions/alarms” (5-68)..............................................3 - 3 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 93: Inc. (From Dsx) Ds1 Lof

    LED on SYSCTL Visible Lighted CR/MJ MN/ABN indication faceplate and a flashing FAULT LED on the alarmed circuit pack. “Procedure 5-23: Clear ″inc. DS1″ Action Proceed to conditions/alarms” (5-68)..............................................365-372-333 R2.1 Lucent Technologies 3 - 3 9 Issue 4, June 2005...

  • Page 94: Inc. (From Dsx) Ds1 Los

    CR/MJ MN/ABN LED on SYSCTL indication faceplate and a flashing FAULT LED on the alarmed circuit pack. “Procedure 5-23: Clear ″inc. DS1″ Action Proceed to conditions/alarms” (5-68)..............................................3 - 4 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 95: Inc. (From Dsx) Ds1 Sig. Failed

    CR/MJ MN/ABN LED on SYSCTL indication faceplate and a flashing FAULT LED on the alarmed circuit pack. “Procedure 5-23: Clear ″inc. DS1″ Action Proceed to conditions/alarms” (5-68)..............................................365-372-333 R2.1 Lucent Technologies 3 - 4 1 Issue 4, June 2005...

  • Page 96: Inc. (From Dsx) Ds3 Ais

    Lighted MN/ABN LED on SYSCTL indication faceplate and a flashing FAULT LED on the alarmed circuit pack. “Procedure 5-25: Clear ″inc. DS3″ Action Proceed to conditions/alarms” (5-75)..............................................3 - 4 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 97: Inc. (From Dsx) Ds3 Lof

    Lighted MN/ABN LED on SYSCTL indication faceplate and a flashing FAULT LED on the alarmed circuit pack. “Procedure 5-25: Clear ″inc. DS3″ Action Proceed to conditions/alarms” (5-75)..............................................365-372-333 R2.1 Lucent Technologies 3 - 4 3 Issue 4, June 2005...

  • Page 98: Inc. (From Dsx) Ds3 Los

    Lighted MN/ABN LED on SYSCTL indication faceplate and a flashing FAULT LED on the alarmed circuit pack. “Procedure 5-25: Clear ″inc. DS3″ Action Proceed to conditions/alarms” (5-75)..............................................3 - 4 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 99: Inc. (From Dsx) Ds3 Sig. Failed

    Lighted MN/ABN LED on SYSCTL indication faceplate and a flashing FAULT LED on the alarmed circuit pack. “Procedure 5-25: Clear ″inc. DS3″ Action Proceed to conditions/alarms” (5-75)..............................................365-372-333 R2.1 Lucent Technologies 3 - 4 5 Issue 4, June 2005...

  • Page 100: Inc. (From Fiber) Ds3 Ais

    A problem/failure at the other network element where the alarmed DS3 is terminated. Visible None. indication “Procedure 5-26: Clear ″inc. (from Action Proceed to fiber) DS3″ conditions” (5-79)..............................................3 - 4 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 101: Inc. (From Fiber) Ds3 Lof

    A problem/failure at the other network element where the alarmed DS3 is terminated. Visible None. indication “Procedure 5-26: Clear ″inc. (from Action Proceed to fiber) DS3″ conditions” (5-79)..............................................365-372-333 R2.1 Lucent Technologies 3 - 4 7 Issue 4, June 2005...

  • Page 102: Inc. Fe-Lan Anm

    LED on SYSCTL CR/MJ MN/ABN faceplate and a flashing LED on the indication FAULT alarmed circuit pack. “Procedure 5-27: Clear ″inc. FE-LAN Action Proceed to ANM″ alarm” (5-81)..............................................3 - 4 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 103: Inc. Fe-Lan Los

    Visible Lighted CR/MJ MN/ABN indication faceplate and a flashing FAULT LED on the alarmed circuit pack. “Procedure 5-28: Clear ″inc. FE-LAN Action Proceed to LOS″ alarm” (5-86)..............................................365-372-333 R2.1 Lucent Technologies 3 - 4 9 Issue 4, June 2005...

  • Page 104: Inc. Ocn Line Ais

    CR/MJ MN/ABN LED on SYSCTL indication faceplate and a flashing FAULT LED on the alarmed circuit pack. “Procedure 5-29: Clear ″inc. OCN″ Action Proceed to conditions/alarms” (5-88)..............................................3 - 5 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 105: Inc. Ocn Lof

    LED on SYSCTL CR/MJ MN/ABN indication faceplate and a flashing LED on the FAULT alarmed circuit pack. “Procedure 5-29: Clear ″inc. OCN″ Action Proceed to conditions/alarms” (5-88)..............................................365-372-333 R2.1 Lucent Technologies 3 - 5 1 Issue 4, June 2005...

  • Page 106: Inc. Ocn Los

    CR/MJ MN/ABN LED on SYSCTL indication faceplate and a flashing FAULT LED on the alarmed circuit pack. “Procedure 5-29: Clear ″inc. OCN″ Action Proceed to conditions/alarms” (5-88)..............................................3 - 5 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 107: Inc. Ocn Rfi-L

    Incoming signal failure detected at the far-end network element. Visible Lighted CR/MJ MN/ABN LED on SYSCTL indication faceplate. “Procedure 5-30: Clear ″inc. OCN Action Proceed to RFI-L″ condition/alarm” (5-92)..............................................365-372-333 R2.1 Lucent Technologies 3 - 5 3 Issue 4, June 2005...

  • Page 108: Inc. Ocn Sig. Degrade (Ber)

    CR/MJ MN/ABN LED on SYSCTL indication faceplate and a flashing FAULT LED on the alarmed circuit pack. “Procedure 5-29: Clear ″inc. OCN″ Action Proceed to conditions/alarms” (5-88)..............................................3 - 5 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 109: Inc. Ocn Sig. Failed (Ber)

    CR/MJ MN/ABN LED on SYSCTL indication faceplate and a flashing FAULT LED on the alarmed circuit pack. “Procedure 5-29: Clear ″inc. OCN″ Action Proceed to conditions/alarms” (5-88)..............................................365-372-333 R2.1 Lucent Technologies 3 - 5 5 Issue 4, June 2005...

  • Page 110: Inc. Stsn Ais

    Visible Lighted CR/MJ MN/ABN LED on SYSCTL indication faceplate. “Procedure 5-31: Clear ″inc. STSN″ Action Proceed to conditions/alarms” (5-96)..............................................3 - 5 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 111: Inc. Stsn Lop

    Lighted LED on SYSCTL CR/MJ MN/ABN indication faceplate a flashing LED on the alarmed FAULT circuit pack. “Procedure 5-31: Clear ″inc. STSN″ Action Proceed to conditions/alarms” (5-96)..............................................365-372-333 R2.1 Lucent Technologies 3 - 5 7 Issue 4, June 2005...

  • Page 112: Inc. Stsn Rfi-P

    An upstream STS-N cross-connection has been deleted; an upstream failure (for example, LOS or LOF) has been detected. Visible None. indication “Procedure 5-31: Clear ″inc. STSN″ Action Proceed to conditions/alarms” (5-96)..............................................3 - 5 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 113: Inc. Stsn Sig. Degrade (Ber)

    CR (SA). A protected line/port failed: MN (NSA). Visible Lighted LED on SYSCTL CR/MJ MN/ABN indication faceplate. “Procedure 5-31: Clear ″inc. STSN″ Action Proceed to conditions/alarms” (5-96)..............................................365-372-333 R2.1 Lucent Technologies 3 - 5 9 Issue 4, June 2005...

  • Page 114: Inc. Stsn Sig. Failed (Ber)

    CR (SA). A protected line/port failed: MN (NSA). Visible Lighted CR/MJ MN/ABN LED on SYSCTL indication faceplate. “Procedure 5-31: Clear ″inc. STSN″ Action Proceed to conditions/alarms” (5-96)..............................................3 - 6 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 115: Inc. Stsn Unequipped

    CR (SA). A protected line/port failed: MN (NSA). Visible Lighted CR/MJ MN/ABN LED on SYSCTL indication faceplate. “Procedure 5-31: Clear ″inc. STSN″ Action Proceed to conditions/alarms” (5-96)..............................................365-372-333 R2.1 Lucent Technologies 3 - 6 1 Issue 4, June 2005...

  • Page 116: Inc. Vcg Failed

    Cross-connection error in one or more VT1.5 or STSN tributaries in the VCG. Visible Lighted CR/MJ LED on SYSCTL faceplate. indication “Procedure 5-32: Clear ″inc. VCG Action Proceed to failed″ alarm” (5-100)..............................................3 - 6 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 117: Inc. Vcg Lfd

    The far end Ethernet circuit pack does not support the ITU-T G.7041/Y.1303 Generic framing procedure (GFP). Visible Lighted MN/ABN LED on SYSCTL faceplate. indication “Procedure 5-33: Clear ″inc. VCG Action Proceed to LFD″ condition” (5-104)..............................................365-372-333 R2.1 Lucent Technologies 3 - 6 3 Issue 4, June 2005...

  • Page 118: Inc. Vcg Loa

    Visible Lighted MN/ABN LED on SYSCTL faceplate. indication “Procedure 5-34: Clear ″inc. VCG Action Proceed to LOA″ condition” (5-106)..............................................3 - 6 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 119: Inc. Vt Ais

    VT AIS. Visible Lighted CR/MJ MN/ABN LED on SYSCTL indication faceplate. “Procedure 5-35: Clear ″inc. VT″ Action Proceed to conditions/alarms” (5-108)..............................................365-372-333 R2.1 Lucent Technologies 3 - 6 5 Issue 4, June 2005...

  • Page 120: Inc. Vt Lop

    MJ (SA). A protected line/port failed: MN (NSA). Visible Lighted CR/MJ MN/ABN LED on SYSCTL indication faceplate. “Procedure 5-35: Clear ″inc. VT″ Action Proceed to conditions/alarms” (5-108)..............................................3 - 6 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 121: Inc. Vt Rfi-V

    VT RFI-V Likely Cause Alarm condition detected at the far end OC-N circuit pack. Visible None. indication “Procedure 5-35: Clear ″inc. VT″ Action Proceed to conditions/alarms” (5-108)..............................................365-372-333 R2.1 Lucent Technologies 3 - 6 7 Issue 4, June 2005...

  • Page 122: Inc. Vt Sig. Degrade (Ber)

    MJ (SA). A protected line/port failed: MN (NSA). Visible Lighted CR/MJ MN/ABN LED on SYSCTL indication faceplate. “Procedure 5-35: Clear ″inc. VT″ Action Proceed to conditions/alarms” (5-108)..............................................3 - 6 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 123: Inc. Vt Unequipped

    MJ (SA). A protected line/port failed: MN (NSA). Visible Lighted CR/MJ MN/ABN LED on SYSCTL indication faceplate. “Procedure 5-35: Clear ″inc. VT″ Action Proceed to conditions/alarms” (5-108)..............................................365-372-333 R2.1 Lucent Technologies 3 - 6 9 Issue 4, June 2005...

  • Page 124: Inconsistent Dcc Values

    Fibers are misconnected or DCC LAPD Role parameter was incorrectly provisioned. Visible Lighted CR/MJ LED on SYSCTL faceplate. indication “Procedure 5-36: Clear ″inconsistent Action Proceed to DCC values″ alarm” (5-112)..............................................3 - 7 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 125: Install Failed

    Visible Lighted LED on SYSCTL faceplate. MN/ABN indication Action Return to the procedure from which you initiated the install and repeat..............................................365-372-333 R2.1 Lucent Technologies 3 - 7 1 Issue 4, June 2005...

  • Page 126: Install Program Ip

    Likely Cause From the WaveStar CIT System View, selected Configuration → Software → Download Software Visible None. indication Action No action necessary. Condition clears when download is complete..............................................3 - 7 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 127: Lockout Of Protection

    Line Protection group or Path Protection group, and provisioned the Switch Type as Lockout Visible Lighted LED on SYSCTL faceplate. MN/ABN indication “Procedure 5-37: Clear ″lockout of Action Proceed to protection″ condition” (5-114)..............................................365-372-333 R2.1 Lucent Technologies 3 - 7 3 Issue 4, June 2005...

  • Page 128: Manual Reference Switch

    Visible Lighted LED on SYSCTL faceplate. MN/ABN indication “Procedure 5-38: Clear ″manual Action Proceed to reference switch″ condition” (5-116)..............................................3 - 7 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 129: Manual Switch

    Line Protection group or Path Protection group, and provisioned the Switch Type as Manual Visible Lighted MN/ABN LED on SYSCTL faceplate. indication “Procedure 5-39: Clear ″manual Action Proceed to switch″ condition” (5-117)..............................................365-372-333 R2.1 Lucent Technologies 3 - 7 5 Issue 4, June 2005...

  • Page 130: Manual Sync. Mode Switch

    Switch Command Mode Switch Holdover Visible Lighted LED on SYSCTL faceplate. MN/ABN indication “Procedure 5-40: Clear ″manual sync. Action Proceed to mode switch″ condition” (5-119)..............................................3 - 7 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 131: Member Signal Unacceptable - Lcas

    VCG. Visible Lighted LED on local SYSCTL faceplate. MN/ABN indication “Procedure 5-41: Clear ″Member Action Proceed to Signal Unacceptable - LCAS″ alarm” (5-120)..............................................365-372-333 R2.1 Lucent Technologies 3 - 7 7 Issue 4, June 2005...

  • Page 132: Neighbor Sysctl Cp Unavailable (Nbr Tid = Tid)

    SYSCTL circuit pack. Visible Lighted CR/MJ LED on local SYSCTL faceplate. indication “Procedure 5-42: Clear ″neighbor Action Proceed to SYSCTL CP unavailable (nbr tid = TID)″ alarm” (5-125)..............................................3 - 7 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 133: Nsap Count In L1 Overflowed

    The number of OSI nodes in the level 1 routing area has exceeded 50. Visible Lighted LED on SYSCTL faceplate. CR/MJ indication “Procedure 5-43: Clear ″NSAP count Action Proceed to in L1 overflowed″ alarm” (5-128)..............................................365-372-333 R2.1 Lucent Technologies 3 - 7 9 Issue 4, June 2005...

  • Page 134: Nsap Count In L1 Threshold Crossed

    Visible Lighted MN/ABN LED on SYSCTL faceplate. indication “Procedure 5-44: Clear ″NSAP count Action Proceed to in L1 threshold crossed″ alarm” (5-129)..............................................3 - 8 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 135: Ntp Server(S) Unreachable

    NTP server(s) unreachable Likely Cause Incorrect provisioning of the NTP feature, LAN or network failures. Visible None. indication “Procedure 5-45: Clear ″NTP server(s) Action Proceed to unreachable″ condition” (5-130)..............................................365-372-333 R2.1 Lucent Technologies 3 - 8 1 Issue 4, June 2005...

  • Page 136: Pluggable Transmission Module Removed

    LED on the socket, and a flashing LED on the circuit FAULT pack. “Procedure 5-46: Clear ″Pluggable Action Proceed to Transmission Module removed″ alarm” (5-132)..............................................3 - 8 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 137: Port Administratively Disabled

    WaveStar CIT command: Configuration → Equipment Visible Lighted MN/ABN LED on SYSCTL faceplate. indication “Procedure 5-47: Clear ″Port Action Proceed to administratively disabled″ condition” (5-135)..............................................365-372-333 R2.1 Lucent Technologies 3 - 8 3 Issue 4, June 2005...

  • Page 138: Remote Client Signal Failed

    Incoming client signal failure at the far-end equipment or a SONET-level failure. Visible Lighted CR/MJ MN/ABN LED on SYSCTL indication faceplate. “Procedure 5-48: Clear ″Remote client Action Proceed to signal failed″ alarm” (5-137)..............................................3 - 8 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 139: Remote Install/Copy Program Ip

    NE. Visible None. indication Action No action necessary. Condition clears automatically when the generic is completely copied into the dormant area of the NE..............................................365-372-333 R2.1 Lucent Technologies 3 - 8 5 Issue 4, June 2005...

  • Page 140: Ring Upgrade Mode

    This command is used in network upgrades. Visible Lighted LED on SYSCTL faceplate. MN/ABN indication “Procedure 5-49: Clear ″ring upgrade Action Proceed to mode″ condition” (5-140)..............................................3 - 8 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 141: Section Dcc Channel Failed

    OC-N circuit pack failure at the near end. Visible Lighted LED on SYSCTL faceplate. MN/ABN indication “Procedure 5-50: Clear ″section DCC Action Proceed to channel failed ″ alarm” (5-142)..............................................365-372-333 R2.1 Lucent Technologies 3 - 8 7 Issue 4, June 2005...

  • Page 142: Sysctl Cp Failed

    Internal equipment failure of the SYSCTL circuit pack. Visible None or lighted CR/MJ LED on SYSCTL indication faceplate. Action Proceed to “Procedure 6-3: Replace a SYSCTL (VLNC1) circuit pack” (6-35)..............................................3 - 8 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 143: Time Of Day Not Provisioned

    Likely Cause The SYSCTL circuit pack has been reset. Visible None. indication “Procedure 5-51: Clear ″time of day Action Proceed to not provisioned″ condition” (5-145)..............................................365-372-333 R2.1 Lucent Technologies 3 - 8 9 Issue 4, June 2005...

  • Page 144: Unexpected Cp Type

    If a node or network upgrade is in progress, no action is necessary. The Standing Condition will clear when the upgrade is complete. Otherwise, proceed to “Procedure 5-52: Clear ″unexpected CP type″ alarm” (5-147)..............................................3 - 9 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 145: Unexpected Or Failed Pluggable Transmission Module

    LED on the failed socket, and a flashing LED on the FAULT circuit pack. “Procedure 5-53: Clear ″unexpected or Action Proceed to failed Pluggable Transmission Module″ alarm” (5-150)..............................................365-372-333 R2.1 Lucent Technologies 3 - 9 1 Issue 4, June 2005...

  • Page 146: Vcg Failure Of Lcas Protocol (Sink)

    LED on SYSCTL faceplate and a MN/ABN indication continuously lighted LED on the alarmed FAULT circuit pack. “Procedure 5-54: Clear ″VCG Failure Action Proceed to of LCAS Protocol″ alarms” (5-154)..............................................3 - 9 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 147: Vcg Failure Of Lcas Protocol (Source)

    LED on SYSCTL faceplate and a MN/ABN indication continuously lighted LED on the alarmed FAULT circuit pack. “Procedure 5-54: Clear ″VCG Failure Action Proceed to of LCAS Protocol″ alarms” (5-154)..............................................365-372-333 R2.1 Lucent Technologies 3 - 9 3 Issue 4, June 2005...

  • Page 148: Vcg Loss Of Partial Capacity

    LED on SYSCTL faceplate and a indication continuously lighted FAULT LED on the alarmed circuit pack. “Procedure 5-55: Clear ″VCG Loss of Action Proceed to Partial Capacity″ alarm” (5-156)..............................................3 - 9 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 149: Version Mismatch

    LED on SYSCTL faceplate and a MN/ABN indication continuously lighted LED on the alarmed FAULT circuit pack. “Procedure 5-56: Clear ″version Action Proceed to mismatch″ alarm” (5-161)..............................................365-372-333 R2.1 Lucent Technologies 3 - 9 5 Issue 4, June 2005...

  • Page 150: Waiting For Download

    Visible Lighted LED on SYSCTL faceplate. MN/ABN indication Action No action necessary. Condition clears automatically when a circuit pack firmware upgrade is complete..............................................3 - 9 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 151 Alarm and status conditions reporting Protection switching 4-11 Unidirectional path-switched ring switching 4-13 1+1 line protection switching 4-16 Synchronization reference protection switching 4-19 Loopbacks 4-21 Tests 4-23 Reports 4-25 ..............................................365-372-333 R2.1 Lucent Technologies 4 - 1 Issue 4, June 2005...

  • Page 152: Maintenance Overview

    Describe the features that are available to monitor and maintain ® Metropolis DMXplore For related procedures, refer to Chapter 5, “Trouble clearing Related procedures procedures” in this document..............................................4 - 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 153: Overview

    Refer to “Procedure 6-2: Connect personal computer (PC) and Reference ® establish WaveStar CIT session” (6-24) Chapter 6, “Supporting ® procedures” for additional information about the WaveStar CIT..............................................365-372-333 R2.1 Lucent Technologies 4 - 3 Issue 4, June 2005...

  • Page 154: Maintenance Philosophy

    (CIT) or TL1 interface may be used to retrieve detailed ® reports about alarms and conditions. Metropolis DMXplore can also be configured for a standard IEEE 802.3 TCP/IP interface..............................................4 - 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 155: Maintenance Signals

    (RDI) upstream to the node that originated the signal. After receiving an RDI that persists for two seconds (±0.5), the originating node (upstream node), generates a remote failure ..............................................365-372-333 R2.1 Lucent Technologies 4 - 5 Issue 4, June 2005...
  • Page 156 DMXplore supports STS-N and VT1.5 path unequipped signals. Path unequipped signals are transmitted to notify downstream equipment that the path is incomplete (for example, the absence of a valid cross-connection)..............................................4 - 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 157: Alarm And Status Conditions Reporting

    VCG LOA OC-3 inc. OCN line AIS OC-12 inc. OCN LOF inc. OCN LOS inc. OCN RFI-L inc. OCN sig. degrade (BER) inc. OCN sig. failed (BER) ..............................................365-372-333 R2.1 Lucent Technologies 4 - 7 Issue 4, June 2005...
  • Page 158 ® WaveStar CIT. In addition, a history of the past 500 notifications is maintained and available for on-demand reporting. Each alarm notification is date and time stamped..............................................4 - 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 159 To minimize the number of alarm conditions reported by an NE, related alarms/status conditions are arranged in hierarchical groups. When more than one alarm or status condition in a hierarchical group ..............................................365-372-333 R2.1 Lucent Technologies 4 - 9 Issue 4, June 2005...
  • Page 160 Because the system is not able to switch to the other side of the ring, this second VT1.5 AIS is reported as a service-affecting inc. VT AIS..............................................4 - 1 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 161: Protection Switching

    The choices are as follows: • 1+1 Line Protection (Port): Lockout, Manual, Forced, or Reset. • Path Protection: Manual, Forced, Lockout, or Reset..............................................365-372-333 R2.1 Lucent Technologies 4 - 1 1 Issue 4, June 2005...
  • Page 162 Manual switch: selects the requested ring path provided the requested ring path is good and there are no existing protection switching requests in place. • Reset: clears an existing lockout, force, or manual switch..............................................4 - 1 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 163: Unidirectional Path-Switched Ring Switching

    LOS, LOF, AIS, STS and VT path AIS, LOP, and UNEQ (most impaired - worst signal quality) • STS-N and VT Path BER exceeding a signal degrade threshold • Path-level signal with no impairments..............................................365-372-333 R2.1 Lucent Technologies 4 - 1 3 Issue 4, June 2005...

  • Page 164: Upsr Switching Example

    UPSR protection switching. The UPSR switching is performed in the receive direction. If the active incoming path-level signal fails, the circuit pack chooses the stand-by path-level signal. In the transmit ..............................................4 - 1 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 165 LOS, LOF, path AIS, LOP, STS-N/VT unequipped, and STS-N/VT path BER performance. This function at the ring exit point is called a tail-end switch..............................................365-372-333 R2.1 Lucent Technologies 4 - 1 5 Issue 4, June 2005...

  • Page 166: 1+1 Line Protection Switching

    Provision, and provisioning 1+1 Protection Priority to be Forced or Signal Failure. The following table lists the 1+1 line protection switch priorities (in ® descending order of priority) used by Metropolis DMXplore when ..............................................4 - 1 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 167 Lockout of Protection WaveStar CIT or OS prevents any switch request (automatic or user-initiated) Signal Failure Automatic (Protection) ® Forced Switch WaveStar CIT or OS Signal Failure (Working) Automatic ..............................................365-372-333 R2.1 Lucent Technologies 4 - 1 7 Issue 4, June 2005...
  • Page 168 Protection switching priorities (1+1 switch priority = signal failure) (continued) Switch Priorities Source of Request (Descending Order) Signal Degrade Automatic ® Manual Switch WaveStar CIT or OS ..............................................4 - 1 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 169: Synchronization Reference Protection Switching

    If neither reference is available, the system automatically switches to holdover timing mode. ® When Metropolis DMXplore is provisioned for synchronization messaging, the system can determine the quality of the line timing ..............................................365-372-333 R2.1 Lucent Technologies 4 - 1 9 Issue 4, June 2005...
  • Page 170 Timing modes may be provisioned using the set-syncn command or Configuration → ® from the WaveStar CIT System View menu, select Timing/Sync ..............................................4 - 2 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 171: Loopbacks

    Figure 4-2 Facility loopback example AIS-P External Cross- Cross- Looped Test Connect Connect Port/Line Circuit Pack Circuit Pack Facility Loopback MA-DMX-322 ..............................................365-372-333 R2.1 Lucent Technologies 4 - 2 1 Issue 4, June 2005...

  • Page 172: Terminal Loopback Example

    Port/Line Circuit Pack Circuit Pack Terminal Loopback = See table below for signal transmitted. If interface type is... Then signal transmitted is... DS1, DS3 Ethernet Open MA-DMXplore-059 ..............................................4 - 2 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 173: Tests

    DMXplore shelf’s IAO LAN is capable of interfacing ® with an IAO LAN hub. From the WaveStar CIT System View menu, Fault → Test → IAO LAN select ..............................................365-372-333 R2.1 Lucent Technologies 4 - 2 3 Issue 4, June 2005...
  • Page 174 Use the command or select ® Transmission from the WaveStar CIT System View menu to test transmission. Additional popup screens are used to facilitate the specific transmission tests..............................................4 - 2 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 175: Reports

    The identity of the condition (for example, OLIU CP failed, or inc. DS1 sig. failed) is included in the report along with a time stamp indicating when the condition was detected..............................................365-372-333 R2.1 Lucent Technologies 4 - 2 5 Issue 4, June 2005...

  • Page 176: Alarm Filtering Options

    Alarm Category Communication Equipment Environment Common Equipment Alarm Level Critical Major Minor Not Alarmed Effect on Service Service Affecting Non-service Affecting Signal Level Affected OC12 STS1 STS3c ..............................................4 - 2 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 177 DMXplore lists recent security-related events (such as NE security log logins, logouts, software downloads) on the NE. This security log can Reports → NE Security Log be retrieved by selecting ..............................................365-372-333 R2.1 Lucent Technologies 4 - 2 7 Issue 4, June 2005...

  • Page 179: Trouble Clearing Procedures

    Then, perform the action(s) deemed appropriate in light of the traffic being carried and the nature of the failure. Contents Before you begin ..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 Issue 4, June 2005...

  • Page 180: Overview

    Procedure 5-20: Clear ″forced switch″ condition 5-60 Procedure 5-21: Clear ″holdover mode active″ 5-62 condition Procedure 5-22: Clear ″illegal CP type″ alarm 5-65 Procedure 5-23: Clear ″inc. DS1″ conditions/alarms 5-68 ..............................................5 - 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 181 Procedure 5-43: Clear ″NSAP count in L1 overflowed″ 5-128 alarm Procedure 5-44: Clear ″NSAP count in L1 threshold 5-129 crossed″ alarm Procedure 5-45: Clear ″NTP server(s) unreachable″ 5-130 condition ..............................................365-372-333 R2.1 Lucent Technologies 5 - 3 Issue 4, June 2005...
  • Page 182 Transmission Module″ alarm Procedure 5-54: Clear ″VCG Failure of LCAS 5-154 Protocol″ alarms Procedure 5-55: Clear ″VCG Loss of Partial Capacity″ 5-156 alarm Procedure 5-56: Clear ″version mismatch″ alarm 5-161 ..............................................5 - 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 183: Before You Begin

    Important! Also refer to the procedure to be performed for other equipment requirements. If other equipment is required to perform a specific procedure, that equipment is listed in the procedure..............................................365-372-333 R2.1 Lucent Technologies 5 - 5 Issue 4, June 2005...

  • Page 184: Procedure 5-1: Address Communication Failure With Network Element

    ″-48V power/fuse FA or FB failed″ alarm” (5-11) ................................Observe the LEDs on the SYSCTL circuit pack faceplate. Are the LEDs constantly cycling? If... Then... Yes, Proceed to Step Continue with Step ..............................................5 - 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 185: Procedure 5-1: Address Communication Failure With

    When the reset is complete, attempt to establish communications with the network element. Was the attempt to log in to the network element successful? If... Then... Yes, STOP! End of Procedure. Continue with Step ..............................................365-372-333 R2.1 Lucent Technologies 5 - 7 Issue 4, June 2005...
  • Page 186 When the reset is complete, attempt to establish communications with the network element. Was the attempt to log in to the network element successful? If... Then... Yes, STOP! End of Procedure. Continue with Step ..............................................5 - 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 187 Attempt to establish communications with the network element. Was the attempt to log in to the network element successful? If... Then... Yes, STOP! End of Procedure..............................................365-372-333 R2.1 Lucent Technologies 5 - 9 Issue 4, June 2005...
  • Page 188 Trouble clearing procedures failure with network element If... Then... Contact your next level of support. “Procedure 6-13: Establish communications with Reference: network element” (6-201) T E P S .................................................................................. 5 - 1 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 189: Procedure 5-2: Clear "-48V Power/Fuse Fa Or Fb Failed" Alarm

    The more probable cause of a failure in a feeder/circuit breaker is a short in the feeder path or a problem with a circuit pack connector..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 1 Issue 4, June 2005...

  • Page 190: Procedure 5-2: Clear "-48V Power/Fuse Fa Or Fb

    Refresh -48V power/fuse failed alarm is no longer Result: present................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm..............................................5 - 1 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 191 Procedure 5-2: Clear ″-48V power/fuse FA Trouble clearing procedures or FB failed″ alarm If... Then... STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 3 Issue 4, June 2005...

  • Page 192: Procedure 5-3: Clear "Agne Communication Failure" Alarm

    Then... Record that TID and the alarm group of the local NE and log into that NE Administration → View NE and select Administration Continue with Step ..............................................5 - 1 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 193: Procedure 5-3: Clear "Agne Communication Failure

    For Remote NE Status, select to enable Remote NE Status. Enabled Important! Note that Remote NE Status must be Enabled in order to provision the alarm group functions..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 5 Issue 4, June 2005...
  • Page 194 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 1 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 195: Procedure 5-4: Clear "Cp Not Allowed - Crs" Alarm

    Reports → Equipment Lists → Pack Select . Click on Shelf and to obtain the Circuit Pack List. Observe the correct circuit Select pack information for the required slot..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 7 Issue 4, June 2005...
  • Page 196 Refer to the appropriate circuit pack replacement procedure in Chapter 6, “Supporting procedures”................................From the System View, click the Alarm List button and click Refresh ..............................................5 - 1 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 197: Procedure 5-4: Clear "Cp Not Allowed - Crs" Alarm

    ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 9 Issue 4, June 2005...

  • Page 198: Procedure 5-5: Clear "Cp Not Allowed - Eqpt" Alarm

    Step 1), determine the circuit pack affected, and note the corresponding slot AID................................Using office records, determine the correct circuit pack type for the required slot..............................................5 - 2 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 199: Procedure 5-5: Clear "Cp Not Allowed - Eqpt" Alarm

    Refer to the appropriate circuit pack replacement procedure in Chapter 6, “Supporting procedures”................................® From the WaveStar CIT System View, click button and Alarm List click Refresh ..............................................365-372-333 R2.1 Lucent Technologies 5 - 2 1 Issue 4, June 2005...
  • Page 200 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 2 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 201: Procedure 5-6: Clear "Cp Removed Or Cp Failure" Alarm

    ..............................................365-372-333 R2.1 Lucent Technologies 5 - 2 3 Issue 4, June 2005...
  • Page 202 Obtain the missing circuit pack and install it into the required slot. Refer to the appropriate circuit pack installation procedure in the ® Metropolis DMXplore Access Multiplexer User Operations Guide, 365-372-332..............................................5 - 2 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 203 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 2 5 Issue 4, June 2005...

  • Page 204: Procedure 5-7: Clear "Cp Software Upgrade Required" Condition

    From the WaveStar CIT System View, click the button Alarm List and click Refresh ................................CP software upgrade required Is the alarm still present? If... Then... Continue with Step ..............................................5 - 2 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 205 If your time format preference is a 24-hour clock, select the Hour: (0-23), Minutes: (0-59), and Seconds: (0-59) from the pull-down menus. From the panel, select Type: Smart. Apply Type ..............................................365-372-333 R2.1 Lucent Technologies 5 - 2 7 Issue 4, June 2005...
  • Page 206 CIT System View, click the Alarm List button and click Refresh ................................CP software upgrade required Is the alarm still present? If... Then... Continue with Step Proceed to Step ..............................................5 - 2 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 207 Minutes: Seconds: the pull-down menus. From the Apply Type panel, select Type: Forced. Click A warning message appears asking you to confirm the execution of this command..............................................365-372-333 R2.1 Lucent Technologies 5 - 2 9 Issue 4, June 2005...
  • Page 208 CP software upgrade required Is the alarm still present? If... Then... You may need to replace the pack. Contact your next level of support. Continue with Step ..............................................5 - 3 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 209 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 3 1 Issue 4, June 2005...

  • Page 210: Procedure 5-8: Clear "Dormant/Exec Code Mismatch" Condition

    Select . The software will install 15 Install In 15 Minutes minutes after you click • Select Specify Install Date/Time and select the Year Month Date Time ..............................................5 - 3 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 211 Approximately 10 minutes after the scheduled apply time, the apply is complete. A warning appears. Click . The System View Result: closes................................Log back into the shelf..............................................365-372-333 R2.1 Lucent Technologies 5 - 3 3 Issue 4, June 2005...
  • Page 212 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 3 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 213: Procedure 5-9: Clear "Ds1 Loopback (To Dsx)" Condition

    (GRP) and VT Group, then select the affected DS1 port and click Select The loopback parameters appear. Result: ................................Select , then click Release Facility Apply ..............................................365-372-333 R2.1 Lucent Technologies 5 - 3 5 Issue 4, June 2005...

  • Page 214: Procedure 5-9: Clear "Ds1 Loopback (To Dsx)

    ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 3 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 215: Procedure 5-10: Clear "Ds1 Loopback (To Fiber)" Condition

    (GRP) and VT Group, then select the affected DS1 port and click Select The loopback parameters appear. Result: ................................Select , then click Release Terminal Apply ..............................................365-372-333 R2.1 Lucent Technologies 5 - 3 7 Issue 4, June 2005...

  • Page 216: Procedure 5-10: Clear "Ds1 Loopback (To Fiber)

    ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 3 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 217: Procedure 5-11: Clear "Ds3 Loopback (To Dsx)" Condition

    . Expand the appropriate group (GRP), then select the affected DS3 port and click Select The loopback parameters appear. Result: ................................Select , then click Release Facility Apply ..............................................365-372-333 R2.1 Lucent Technologies 5 - 3 9 Issue 4, June 2005...

  • Page 218: Procedure 5-11: Clear "Ds3 Loopback (To Dsx)

    ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 4 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 219: Procedure 5-12: Clear "Ds3 Loopback (To Fiber)" Condition

    . Expand the appropriate group (GRP), then select the affected DS3 port and click Select The loopback parameters appear. Result: ................................Select , then click Release Terminal Apply ..............................................365-372-333 R2.1 Lucent Technologies 5 - 4 1 Issue 4, June 2005...

  • Page 220: Procedure 5-12: Clear "Ds3 Loopback (To Fiber)

    ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 4 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 221: Procedure 5-13: Clear "Duplicate Tid" Alarm

    Reference: “Procedure 6-2: Connect personal computer ® (PC) and establish WaveStar CIT session” (6-24) ................................From the System View, click the Alarm List button and click Refresh ..............................................365-372-333 R2.1 Lucent Technologies 5 - 4 3 Issue 4, June 2005...

  • Page 222: Procedure 5-13: Clear "Duplicate Tid" Alarm

    ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 4 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 223: Procedure 5-14: Clear "Enet Terminal Loopback" Condition

    Result: A warning message appears asking you to confirm executing this command. Click Close ................................From the System View, click the Alarm List button and click Refresh ..............................................365-372-333 R2.1 Lucent Technologies 5 - 4 5 Issue 4, June 2005...
  • Page 224 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 4 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 225: Procedure 5-15: Clear "Environmentn" Alarm

    ................................Can you clearly identify the cause of the condition? If... Then... Click Close on the View Miscellaneous Discretes window. Clear using local procedures. Continue with Step ..............................................365-372-333 R2.1 Lucent Technologies 5 - 4 7 Issue 4, June 2005...

  • Page 226: Procedure 5-15: Clear "Environmentn" Alarm

    Result: ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 4 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 227: Procedure 5-16: Clear "Excessive Holdover" Alarm

    Fault → Timing/Sync Protection Switch → Clock Mode select Switch , select Normal , and click ................................From the System View, click the button and click Alarm List Refresh ..............................................365-372-333 R2.1 Lucent Technologies 5 - 4 9 Issue 4, June 2005...

  • Page 228: Procedure 5-16: Clear "Excessive Holdover" Alarm

    Repair the failed timing reference according to local procedures................................Fault → Timing/Sync From the System View menu, select Protection Switch → Clock Mode Switch , select Normal , and click ..............................................5 - 5 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 229 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 5 1 Issue 4, June 2005...

  • Page 230: Procedure 5-17: Clear "Fan Shelf Failed" Alarm

    The fan unit has no power. Check power and alarm cables. If cables are not connected, install power and alarm cables to the shelf and tighten screw locks..............................................5 - 5 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 231: Procedure 5-17: Clear "Fan Shelf Failed" Alarm

    Proceed to Step ................................Is the fan unit running and working properly ( LEDs lighted, PWR ON LED off)? FAN FAULT If... Then... STOP! End of Procedure..............................................365-372-333 R2.1 Lucent Technologies 5 - 5 3 Issue 4, June 2005...
  • Page 232 Slide the old fan unit out from shelf chassis................................Slide the new fan unit back into the shelf chassis. Tighten the captive screw. T E P S .................................................................................. 5 - 5 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 233: Procedure 5-18: Clear "Far End Not Lcas" Condition

    If the far-end Metropolis Then... DMX plore ... supports LCAS and LCAS go to Step 5 and enable LCAS operation is desired, for the required VCG at the far end..............................................365-372-333 R2.1 Lucent Technologies 5 - 5 5 Issue 4, June 2005...

  • Page 234: Procedure 5-18: Clear "Far End Not Lcas" Condition

    . Expand the required Ethernet circuit pack details and select the required VCG port being provisioned. Click Select ................................Click on the LCAS tab and disable the LCAS mode. Click Apply ..............................................5 - 5 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 235 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 5 7 Issue 4, June 2005...

  • Page 236: Procedure 5-19: Clear "Fe-Lan Cp Failed" Alarm

    Then, perform the action(s) deemed appropriate in light of the traffic being carried and the nature of the failure..............................................5 - 5 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 237: Procedure 5-19: Clear "Fe-Lan Cp Failed" Alarm

    Refresh ................................FE-LAN CP failed Is the alarm still present? If... Then... Contact your next level of support. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 5 9 Issue 4, June 2005...

  • Page 238: Procedure 5-20: Clear "Forced Switch" Condition

    Click to release the forced switch. Click Close to exit the Switch Protection window................................From the System View, click the Alarm List button and click Refresh ..............................................5 - 6 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 239: Procedure 5-20: Clear "Forced Switch" Condition

    ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 6 1 Issue 4, June 2005...

  • Page 240: Procedure 5-21: Clear "Holdover Mode Active" Condition

    From the System View, click the button and click Alarm List Refresh ................................holdover mode active Is the condition still present? If... Then... Continue with Step Proceed to Step ..............................................5 - 6 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 241 Protection Switch → Clock Mode Switch , select , and click Normal ................................® From the WaveStar CIT System View, click the Alarm List button and Click Refresh ..............................................365-372-333 R2.1 Lucent Technologies 5 - 6 3 Issue 4, June 2005...
  • Page 242 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 6 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 243: Procedure 5-22: Clear "Illegal Cp Type" Alarm

    Extract the circuit pack from the shelf, fully disconnecting it from the backplane, and therefore removing power. LEDs on the pack extinguish. ACTIVE FAULT Re-seat the pack in the shelf..............................................365-372-333 R2.1 Lucent Technologies 5 - 6 5 Issue 4, June 2005...

  • Page 244: Procedure 5-22: Clear "Illegal Cp Type" Alarm

    From the System View, click the Alarm List button and click Refresh ................................illegal CP type Is the alarm still present? If... Then... Contact your next level of support. Continue with Step ..............................................5 - 6 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 245 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 6 7 Issue 4, June 2005...

  • Page 246: Procedure 5-23: Clear "Inc. Ds1" Conditions/Alarms

    Check cable connections between the access panel and the DSX panel for faulty connections or damage and repair/replace as necessary................................From the System View, click the button and click Alarm List Refresh ..............................................5 - 6 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 247 . Provision the Signal Format and the Line Code appropriately, Select click Apply , and then click Close ................................From the System View, click the button and click Alarm List Refresh ..............................................365-372-333 R2.1 Lucent Technologies 5 - 6 9 Issue 4, June 2005...
  • Page 248 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 7 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 249: Procedure 5-24: Clear "Inc. Ds3 Cbit Mismatch" Alarm

    In the Transmission section on the window, locate and record the provisioned signal format................................Configuration → Equipment From the System View, select , expand the group (GRP), highlight the desired port, and then click Select ..............................................365-372-333 R2.1 Lucent Technologies 5 - 7 1 Issue 4, June 2005...
  • Page 250 ................................In the Transmission section of the Configure Equipment window, change the Signal Format parameter for the port to either C-Bit or Clear Channel and click Apply ..............................................5 - 7 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 251 Click . Continue with Step ................................Click Close on the Configure Equipment window................................From the System View, click the button and click Alarm List Refresh ..............................................365-372-333 R2.1 Lucent Technologies 5 - 7 3 Issue 4, June 2005...
  • Page 252 ................................Are there any other alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 7 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 253: Procedure 5-25: Clear "Inc. Ds3" Conditions/Alarms

    AID................................Are there other incoming signal alarms present? If... Then... Proceed to the appropriate procedure to clear those alarms and continue with Step ..............................................365-372-333 R2.1 Lucent Technologies 5 - 7 5 Issue 4, June 2005...
  • Page 254 From the System View, click the button and click Alarm List Refresh ................................inc. DS3 Is the alarm still present? If... Then... Continue with Step Proceed to Step ..............................................5 - 7 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 255: Procedure 5-25: Clear "Inc. Ds3" Conditions/Alarms

    From the System View, click the Alarm List button and click Refresh ................................inc. DS3 Is the alarm still present? If... Then... Continue with Step Proceed to Step ..............................................365-372-333 R2.1 Lucent Technologies 5 - 7 7 Issue 4, June 2005...
  • Page 256 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 7 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 257: Procedure 5-26: Clear "Inc. (From Fiber) Ds3" Conditions

    Consult and follow local procedures for addressing any DS3-related alarms/conditions at the other network element where the alarmed DS3 is terminated................................At the local network element, click the button and click Alarm List Refresh ..............................................365-372-333 R2.1 Lucent Technologies 5 - 7 9 Issue 4, June 2005...
  • Page 258 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 8 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 259: Procedure 5-27: Clear "Inc. Fe-Lan Anm" Alarm

    Provisioned Duplex Mode • Actual Duplex Mode Operation • Provisioned Line Rate • Actual Line Rate Operation ................................From the View Equipment window, click Flow Control tab..............................................365-372-333 R2.1 Lucent Technologies 5 - 8 1 Issue 4, June 2005...

  • Page 260: Procedure 5-27: Clear "Inc. Fe-Lan Anm" Alarm

    If provisioning changes are Then... required at the... local LAN port, Continue with Step interfacing customer LAN port, Follow local procedures to resolve the provisioning conflicts then proceed to Step ..............................................5 - 8 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 261 Then click the Flow Control tab. The flow control parameters appear. Result: ................................Provision the Flow Control Mode parameter as required to match the interfacing customer LAN port and click Apply ..............................................365-372-333 R2.1 Lucent Technologies 5 - 8 3 Issue 4, June 2005...
  • Page 262 Alarm List button and click Refresh ................................inc. FE-LAN ANM Is the alarm still present? If... Then... Contact your next level of support. STOP! End of Procedure..............................................5 - 8 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 263 Procedure 5-27: Clear ″inc. FE-LAN ANM″ Trouble clearing procedures alarm T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 8 5 Issue 4, June 2005...

  • Page 264: Procedure 5-28: Clear "Inc. Fe-Lan Los" Alarm

    → Update States Proceed to Step ................................Check local cable connections between the shelf backplane and the interconnecting equipment for faulty connections or damage and repair/replace as necessary..............................................5 - 8 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 265: Procedure 5-28: Clear "Inc. Fe-Lan Los" Alarm

    Refresh ................................inc. FE-LAN LOS Is the alarm still present? If... Then... Contact your next level of support. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 8 7 Issue 4, June 2005...

  • Page 266: Procedure 5-29: Clear "Inc. Ocn" Conditions/Alarms

    (SA), MJ (SA), MJ (NSA), MN (NSA), and then Not Alarmed................................Refer to the Probable Cause column in the alarm list, determine the inc. OCN OC-N line affected by the alarm, and note the corresponding AID..............................................5 - 8 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 267 Then, perform the action(s) deemed appropriate in light of the traffic being carried and the nature of the failure. Replace the affected local combination circuit pack..............................................365-372-333 R2.1 Lucent Technologies 5 - 8 9 Issue 4, June 2005...

  • Page 268: Procedure 5-29: Clear "Inc. Ocn" Conditions/Alarms

    From the System View at the local network element, click the Alarm button and click List Refresh ................................inc. OCN Is the condition/alarm still present? If... Then... Continue with Step STOP! End of Procedure..............................................5 - 9 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 269 ................................Are there any conditions/alarms listed? If... Then... Proceed to the appropriate procedure to clear the condition/alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 9 1 Issue 4, June 2005...

  • Page 270: Procedure 5-30: Clear "Inc. Ocn Rfi-L" Condition/Alarm

    CR, (SA), MJ (SA), MJ (NSA), MN (NSA), and then Not Alarmed. Then continue with Step Continue with Step ..............................................5 - 9 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 271: Procedure 5-30: Clear "Inc. Ocn Rfi-L

    ................................From the System View, click the Alarm List button and click Refresh ................................inc. OCN RFI-L Is the condition/alarm still present? If... Then... Continue with Step ..............................................365-372-333 R2.1 Lucent Technologies 5 - 9 3 Issue 4, June 2005...
  • Page 272 Important! At this point, the local network element is operating correctly. The trouble is in the far-end network element or in the fiber/cable between the far-end network element and the local network element..............................................5 - 9 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 273 ................................Are there any conditions/alarms listed? If... Then... Proceed to the appropriate procedure to clear the condition/alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 9 5 Issue 4, June 2005...

  • Page 274: Procedure 5-31: Clear "Inc. Stsn" Conditions/Alarms

    AID................................Note the source address of the STSN alarm/condition reported (for example, m-1-1). Based on the circuit layout or other office records, ..............................................5 - 9 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 275: Procedure 5-31: Clear "Inc. Stsn" Conditions/Alarms

    (for example, main-1-1 to main-1-1 for View → Cross-Connection STS-N). Select the command from the System View menu at each shelf to determine if the time slot ..............................................365-372-333 R2.1 Lucent Technologies 5 - 9 7 Issue 4, June 2005...
  • Page 276 If the LBO receptacle is acceptable, replace the terminating OCN OLIU circuit pack. “Procedure 6-4: Replace Combination circuit Reference: pack” (6-148) ................................From the System View, click the button and click Alarm List Refresh ..............................................5 - 9 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 277 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 9 9 Issue 4, June 2005...

  • Page 278: Procedure 5-32: Clear "Inc. Vcg Failed" Alarm

    From the System View, click the button and click Alarm List Refresh ................................inc. VCG failed Is the alarm still present? If... Then... Continue with Step STOP! End of Procedure..............................................5 - 1 0 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 279: Procedure 5-32: Clear "Inc. Vcg Failed" Alarm

    History and/or Security Logs. Click Important! The network element logs will be lost when the controller is reset unless you choose to save the logs..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 0 1 Issue 4, June 2005...
  • Page 280 Extract the circuit pack from the shelf, fully disconnecting it from the backplane, and therefore removing power. LED on the pack extinguish. ACTIVE FAULT Re-seat the circuit pack in the shelf..............................................5 - 1 0 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 281 ................................inc. VCG failed Is the alarm still present? If... Then... Contact your next level of support. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 0 3 Issue 4, June 2005...

  • Page 282: Procedure 5-33: Clear "Inc. Vcg Lfd" Condition

    If required, replace the near-end or far-end Ethernet circuit pack. “Procedure 6-5: Replace Ethernet circuit pack” Reference: (6-153) ................................From the System View, click the button and click Alarm List Refresh ..............................................5 - 1 0 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 283: Procedure 5-33: Clear "Inc. Vcg Lfd" Condition

    ................................inc. VCG LFD Is the alarm still present? If... Then... Contact your next level of support. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 0 5 Issue 4, June 2005...

  • Page 284: Procedure 5-34: Clear "Inc. Vcg Loa" Condition

    Applications and Planning Guide, 365-372-331 ® Metropolis DMXplore Access Multiplexer User Operations Guide, 365-372-332 ................................From the System View, click the button and click Alarm List Refresh ..............................................5 - 1 0 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 285: Procedure 5-34: Clear "Inc. Vcg Loa" Condition

    ................................inc. VCG LOA Is the alarm still present? If... Then... Contact your next level of support. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 0 7 Issue 4, June 2005...

  • Page 286: Procedure 5-35: Clear "Inc. Vt" Conditions/Alarms

    Based on the circuit layout or other office records, determine the far-end network element where that time slot is supposed to be terminated (cross-connected to a DS1 termination)..............................................5 - 1 0 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 287: Procedure 5-35: Clear "Inc. Vt" Conditions/Alarms

    System View menu at each shelf to determine if the time slot identified in Step 4 is cross-connected as specified in circuit layout or other office records..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 0 9 Issue 4, June 2005...
  • Page 288 Then, perform the action(s) deemed appropriate in light of the traffic being carried and the nature of the failure..............................................5 - 1 1 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 289 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 1 1 Issue 4, June 2005...

  • Page 290: Procedure 5-36: Clear "Inconsistent Dcc Values" Alarm

    If... Then... Proceed to Step Continue with Step ................................Configuration → DCC From the System View menu, select Terminations ..............................................5 - 1 1 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 291 Are there any other alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 1 3 Issue 4, June 2005...

  • Page 292: Procedure 5-37: Clear "Lockout Of Protection" Condition

    Click to release the lockout. Click to exit the Switch Close Protection window................................From the System View, click the Alarm List button and click Refresh ..............................................5 - 1 1 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 293 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 1 5 Issue 4, June 2005...

  • Page 294: Procedure 5-38: Clear "Manual Reference Switch" Condition

    ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 1 1 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 295: Procedure 5-39: Clear "Manual Switch" Condition

    Click to exit the Close Switch Protection window................................From the System View, click the Alarm List button and click Refresh ..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 1 7 Issue 4, June 2005...

  • Page 296: Procedure 5-39: Clear "Manual Switch" Condition

    ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 1 1 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 297: Procedure 5-40: Clear "Manual Sync. Mode Switch" Condition

    ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 1 9 Issue 4, June 2005...

  • Page 298: Procedure 5-41: Clear "Member Signal Unacceptable - Lcas" Alarm

    Then click Retrieve all to obtain the NE History Log................................inc. LOM Are there conditions in the NE History Log? If... Then... Continue with Step ..............................................5 - 1 2 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 299 WaveStar CIT session” (6-24) ................................View → Cross-Connections From the System View menu, use the command to obtain cross-connection information for the required circuit..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 2 1 Issue 4, June 2005...
  • Page 300 → Cross-Connections and use the Cross-Connection Wizard to provision the required pass-through cross-connections................................From the System View, click the button and click Alarm List Refresh ..............................................5 - 1 2 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 301 From the System View, click the Alarm List button and click Refresh ................................Member Signal Unacceptable-LCAS Is the alarm still present? If... Then... Continue with Step ..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 2 3 Issue 4, June 2005...
  • Page 302 ................................Member Signal Unacceptable-LCAS Is the alarm still present? If... Then... Contact your next level of support. STOP! End of Procedure. T E P S .................................................................................. 5 - 1 2 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 303: Procedure 5-42: Clear "Neighbor Sysctl Cp Unavailable (Nbr Tid = Tid)" Alarm

    ................................Log in to the neighboring NE (using its TID) via TCP/IP or OSI or dispatch local craft to the remote site and login to NE..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 2 5 Issue 4, June 2005...
  • Page 304 ″inc. OCN″ conditions/alarms” (5-88) Then continue with Step Proceed to Step ................................From the System View of the remote NE, click the button Alarm List and click Refresh ..............................................5 - 1 2 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 305 Are there any other alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 2 7 Issue 4, June 2005...

  • Page 306: Procedure 5-43: Clear "Nsap Count In L1 Overflowed" Alarm

    ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 1 2 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 307: Procedure 5-44: Clear "Nsap Count In L1 Threshold Crossed" Alarm

    ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 2 9 Issue 4, June 2005...

  • Page 308: Procedure 5-45: Clear "Ntp Server(S) Unreachable" Condition

    Refer to Metropolis DMXplore Access Multiplexer User Operations Guide, 365-372-332. Continue with Step ................................From the System View, click the Alarm List button and click Refresh ..............................................5 - 1 3 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 309 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 3 1 Issue 4, June 2005...

  • Page 310: Procedure 5-46: Clear "Pluggable Transmission Module Removed" Alarm

    Refer to the Probable Cause column in the alarm list, determine the pluggable transmission module removed, and note the corresponding socket AID................................Using office records, determine if the required socket should contain a pluggable transmission module..............................................5 - 1 3 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 311 This system update clears the Pluggable Transmission Module removed alarm................................® From the WaveStar CIT System View, click the button Alarm List and click Refresh ..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 3 3 Issue 4, June 2005...
  • Page 312 Are there any alarms listed? If... Then... Yes, Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 1 3 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 313: Procedure 5-47: Clear "Port Administratively Disabled" Condition

    A warning message appears asking you to confirm Result: executing this command. Click Close ................................From the System View, click the button and click Alarm List Refresh ..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 3 5 Issue 4, June 2005...
  • Page 314 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 1 3 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 315: Procedure 5-48: Clear "Remote Client Signal Failed" Alarm

    Proceed to the appropriate procedure to clear the alarm. Then continue with Step Continue with Step ................................From the System View, click the button and click Alarm List Refresh ..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 3 7 Issue 4, June 2005...
  • Page 316 Configuration → At the near-end network element, use the command to disable the Remote Client Fail parameter for Equipment ..............................................5 - 1 3 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 317 Remote client signal failed Is the alarm still present? If... Then... Contact your next level of support. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 3 9 Issue 4, June 2005...

  • Page 318: Procedure 5-49: Clear "Ring Upgrade Mode" Condition

    Mode to Normal mode. Click MN/ABN LED is turned off on the SYSCTL circuit pack faceplate and the Ring Upgrade mode is removed from the ® WaveStar CIT Alarm List..............................................5 - 1 4 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 319 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 4 1 Issue 4, June 2005...

  • Page 320: Procedure 5-50: Clear "Section Dcc Channel Failed " Alarm

    LAPD Role column read user-side or network-side appropriately for the affected DCC port according to office records? If... Then... Proceed to Step Continue with Step ..............................................5 - 1 4 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 321 Check optical connections for the presence of an incoming signal................................Check the optical signal level and clean the cable ends if needed. If no problem is found, check the line build-outs (LBOs)..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 4 3 Issue 4, June 2005...
  • Page 322 DCC channel failed Is the alarm still present? If... Then... Contact your next level of support. STOP! End of Procedure. T E P S .................................................................................. 5 - 1 4 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 323: Procedure 5-51: Clear "Time Of Day Not Provisioned" Condition

    Refer to the Metropolis DMXplore Access Multiplexer User Operations Guide, 365-372-332. Then proceed to Step not required at the network Proceed to Step element, ..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 4 5 Issue 4, June 2005...
  • Page 324 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 1 4 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 325: Procedure 5-52: Clear "Unexpected Cp Type" Alarm

    Using office records, determine the correct circuit pack type for the required slot................................Compare the correct circuit pack type from office records with the circuit pack that is physically in the required slot..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 4 7 Issue 4, June 2005...
  • Page 326 2. Replace the wrong circuit pack currently in the required slot with the correct circuit pack. Refer to the appropriate circuit pack replacement procedure in Chapter 6, “Supporting procedures”..............................................5 - 1 4 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 327 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 4 9 Issue 4, June 2005...

  • Page 328: Procedure 5-53: Clear "Unexpected Or Failed Pluggable Transmission Module" Alarm

    ................................Refer to the Probable Cause column in your alarm list, and determine the pluggable transmission module affected and note the corresponding socket AID..............................................5 - 1 5 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 329 Replace the affected installed in the correct pluggable transmission module. (Refer socket/circuit pack, “Procedure 6-14: Replace pluggable transmission module” (6-203).) Then continue with Step ..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 5 1 Issue 4, June 2005...
  • Page 330 System → Update Inventory update the system equipment list. 3. Continue with Step ................................From the System View, click the button and click Alarm List Refresh ..............................................5 - 1 5 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 331 ................................Are there any alarms listed? If... Then... Proceed to the appropriate task to clear the alarm. STOP! END OF TASK. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 5 3 Issue 4, June 2005...

  • Page 332: Procedure 5-54: Clear "Vcg Failure Of Lcas Protocol" Alarms

    A dialog box appears asking you to confirm executing this command. Click . Click Close to exit window................................From the System View, click the Alarm List button and click Refresh ..............................................5 - 1 5 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 333 ® (PC) and establish WaveStar CIT session” (6-24) ................................At the far end, repeat Step 1 through Step 5, as required. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 5 - 1 5 5 Issue 4, June 2005...

  • Page 334: Procedure 5-55: Clear "Vcg Loss Of Partial Capacity" Alarm

    Proceed to the appropriate procedure to clear the alarm. Then continue with Step Continue with Step ................................From the System View, click the button and click Alarm List Refresh ..............................................5 - 1 5 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 335 ................................Are there other inc. VCG conditions/alarms in the alarm list? If... Then... Proceed to the appropriate procedure to clear the alarm. Then continue with Step ..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 5 7 Issue 4, June 2005...
  • Page 336 A warning appears asking you to confirm executing Result: this command................................Click to execute the command. Important! You will be logged off the system when the system resets..............................................5 - 1 5 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 337 LED on the pack extinguish. ACTIVE FAULT Re-seat the circuit pack in the shelf................................From the System View, click the button and click Alarm List Refresh ..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 5 9 Issue 4, June 2005...
  • Page 338 VCG Loss of Partial Capacity Is the alarm still present? If... Then... Contact your next level of support. STOP! End of Procedure. T E P S .................................................................................. 5 - 1 6 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 339: Procedure 5-56: Clear "Version Mismatch" Alarm

    CIT System View, click the Alarm List button and click Refresh ................................version mismatch Is the alarm still present? If... Then... Continue with Step Proceed to Step ..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 6 1 Issue 4, June 2005...
  • Page 340 Seconds: the pull-down menus. From the Apply Type panel, select Type: Smart. Click A warning message appears asking you to confirm the execution of this command..............................................5 - 1 6 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 341 From the WaveStar CIT System View, click the Alarm List button and click Refresh ................................version mismatch Is the alarm still present? If... Then... Continue with Step ..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 6 3 Issue 4, June 2005...
  • Page 342 If your time format preference is a 24-hour clock, select the (0-23), (0-59), and (0-59) from Hour: Minutes: Seconds: the pull-down menus. From the Apply Type panel, select Type: Forced..............................................5 - 1 6 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 343 “Procedure 6-2: Connect personal computer Reference: ® (PC) and establish WaveStar CIT session” (6-24) ................................® From the WaveStar CIT System View, click the button Alarm List and click Refresh ..............................................365-372-333 R2.1 Lucent Technologies 5 - 1 6 5 Issue 4, June 2005...
  • Page 344 ................................Are there any alarms listed? If... Then... Proceed to the appropriate procedure to clear the alarm. STOP! End of Procedure. T E P S .................................................................................. 5 - 1 6 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 345: Supporting Procedures

    FTTD (2.1 or later boot code) Procedure 6-3.4: Initial software generic installation 6-80 via FTTD (2.0 boot code) Procedure 6-3.5: Initial software generic installation 6-90 via FTP (2.1 boot code) ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 Issue 4, June 2005...
  • Page 346 Procedure 6-11: Observe FTP progress 6-197 Procedure 6-12: Disable an FTP server 6-199 Procedure 6-13: Establish communications with 6-201 network element Procedure 6-14: Replace pluggable transmission 6-203 module ..............................................6 - 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 347 Procedure 6-15.1: Clean optical fibers 6-217 Procedure 6-15.2: Clean fiber adapters and circuit 6-220 pack connectors Procedure 6-15.3: Optical fiber and connector 6-222 inspection Procedure 6-16: Clean pluggable transmission module 6-225 ..............................................365-372-333 R2.1 Lucent Technologies 6 - 3 Issue 4, June 2005...

  • Page 348: Before You Begin

    Important! Also refer to the procedure to be performed for other equipment requirements. If other equipment is required to perform a specific procedure, that equipment is listed in the procedure..............................................6 - 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 349 Step 2, click on Documents and the List Contents . The readme.txt file contains additional user information, for example, a list of supported network elements..............................................365-372-333 R2.1 Lucent Technologies 6 - 5 Issue 4, June 2005...

  • Page 350: Procedure 6-1: Install Generic And Wavestar Cit Software On The Pc

    PC................................® With the PC not connected to the Metropolis DMXplore shelf, insert the CD-ROM into the PC. Result: The CD autoruns and the following window opens: ..............................................6 - 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 351 Double-click on My Computer on your desktop. Double-click on your Compact Disc icon (often identified as drive D:). Double-click on setup.exe................................Click continue Result: The following window opens: ..............................................365-372-333 R2.1 Lucent Technologies 6 - 7 Issue 4, June 2005...
  • Page 352 Supporting procedures ® WaveStar CIT software on the PC ................................Click CIT Software Result: The following window opens: ................................® Click WaveStar CIT to install the WaveStar CIT software..............................................6 - 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 353 If... Then... Continue with Step Proceed to Step ................................When the following window opens, select Select to: Modify, Update, and then click or Repair the current installation Continue ..............................................365-372-333 R2.1 Lucent Technologies 6 - 9 Issue 4, June 2005...
  • Page 354 WaveStar CIT installation. Select Yes, I want to restart my computer now . Click . After your computer reboots, restart the installation from Step ..............................................6 - 1 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 355 Supporting procedures ® WaveStar CIT software on the PC If you do not see this window, proceed to Step ................................® When theInstallShield Wizard appears, click Next ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 1 Issue 4, June 2005...
  • Page 356 WaveStar CIT software on the PC ................................® Follow the instructions on the different InstallShield Wizard windows, including reading and agreeing to the following two License Agreements..............................................6 - 1 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 357 Procedure 6-1: Install generic and Supporting procedures ® WaveStar CIT software on the PC Click Click ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 3 Issue 4, June 2005...
  • Page 358 ................................® Select where you want the WaveStar CIT software installed on your • Click to select the default Destination Folder: C:\Program Next Files\Lucent Technologies\ • Click Browse and navigate to your desired directory and then click Next ..............................................6 - 1 4 Lucent Technologies 365-372-333 R2.1...
  • Page 359 ID and password to login to the WaveStar • Disable WaveStar CIT logins to allow users to run the ® WaveStar CIT without entering a user ID or password. Click Next ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 5 Issue 4, June 2005...
  • Page 360 Select the following components to complete the WaveStar installation. • Network View • CutThrough View • Command Builder • METRO Graphical Package – METRO On-Line Help Files ..............................................6 - 1 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 361 Space Required on C: will be zero. Because the components are already resident on the computer, there is no additional space required when performing and upgrade..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 7 Issue 4, June 2005...
  • Page 362 ................................Click You are prompted with the choice to install OSI (Open System Interconnect) communications protocol. If you want to install OSI click , otherwise, click ..............................................6 - 1 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 363 Procedure 6-1: Install generic and Supporting procedures ® WaveStar CIT software on the PC Result: The following progress indicator screen appears ® while the InstallShield Wizard installs the required files..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 9 Issue 4, June 2005...
  • Page 364 If you wish to copy the NE software to your PC, select on the following screen................................Did you select Yes or No in Step If... Then... Continue with Step ..............................................6 - 2 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 365 A Copying files, please wait window appears. When the window closes, the software files are successfully copied into the generics directory on your PC. By default, this directory is C:\Program Files\Lucent Technologies\WaveStar CIT\generics\dmxplore\2.1.x\p , however, the actual directory is determined by the path defined in...
  • Page 366 The following icon appears on your desktop. ® Clicking on this short-cut icon launches the WaveStar CIT. If you did not install the NE software in Step 17, proceed to Step ..............................................6 - 2 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 367 Cleanup Wizard that can be used to remove temporary folders/files. Start → Programs → To use the Disk Cleanup Wizard select Accessories → System Tools → Disk Cleanup T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 6 - 2 3 Issue 4, June 2005...

  • Page 368: Procedure 6-2: Connect Personal Computer (Pc) And Establish

    Obtain a valid user ID and password for the required network element. Obtain the Target Identifier (TID)/NE name of the network ® element that you are establishing a WaveStar CIT session with..............................................6 - 2 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 369 Important! You can be connected simultaneously to both the ports. RS232 If you are uncertain that the LAN port has already been provisioned, connecting via the serial port is recommended..............................................365-372-333 R2.1 Lucent Technologies 6 - 2 5 Issue 4, June 2005...

  • Page 370: Wavestar ® Cit Welcome Window

    CIT. You will see either the Network Card selection screen (if you have more than one NIC card on your PC) or the ® WaveStar CIT legal notice (Figure 6-3, “Legal notice” (6-28))..............................................6 - 2 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 371: Wavestar ® Cit Login Window

    Symbols may not include space ( ), commercial at (@), comma (,), colon (:), equals sign (=), quotation mark (″), semicolon (;), ampersand (&), horizontal bar (underscore) (_), question mark (?). • Passwords are case sensitive..............................................365-372-333 R2.1 Lucent Technologies 6 - 2 7 Issue 4, June 2005...

  • Page 372: Legal Notice

    NE. Result: The Legal Notice appears. (Refer to the following figure.) Figure 6-3 Legal notice ................................Read the Legal Notice and click ..............................................6 - 2 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 373: Network View

    CIT, click on the drop-down arrow and select the appropriate NE from the list................................In the field, click on the drop-down arrow and select NE Type: Metropolis(R) DMXplore..............................................365-372-333 R2.1 Lucent Technologies 6 - 2 9 Issue 4, June 2005...
  • Page 374 Important! All procedures in this manual assume that the Graphical button is used. However, the button can be selected to communicate directly with the network element using the TL1 Cut Through or Command Builder interface..............................................6 - 3 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 375: Ne Login

    (To ® change your network element password, refer to the Metropolis DMXplore Access Multiplexer User Operations Guide, 365-372-332.) ..............................................365-372-333 R2.1 Lucent Technologies 6 - 3 1 Issue 4, June 2005...

  • Page 376: Ne Level Legal Notice

    Important! Your NE software Release number and User Privilege Level may be different. Your notice should be similar to Figure 6-6, “NE level legal notice” (6-32). Figure 6-6 NE level legal notice ..............................................6 - 3 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 377 ® The WaveStar CIT System View has a menu bar at the top of the window, and status indicators at the bottom of the window. Each item ..............................................365-372-333 R2.1 Lucent Technologies 6 - 3 3 Issue 4, June 2005...

  • Page 378: Example Of System View (Graphical)

    It is recommended that you create a View List for future convenience. ® From the WaveStar CIT Network View window (NOT the System Administration → Administer Views View window), select T E P S .................................................................................. 6 - 3 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 379: Procedure 6-3: Replace A Sysctl (Vlnc1) Circuit Pack

    “Procedure 6-10: Backup and restore NE database via FTAM” (6-192). Precautions Important! Performing this procedure under the following scenarios may cause transmission losses and/or require a restore from a remote backup..............................................365-372-333 R2.1 Lucent Technologies 6 - 3 5 Issue 4, June 2005...
  • Page 380 The replacement SYSCTL circuit pack will exhibit unique visible cycles to show that compatible software is installed, no software is installed (factory-fresh), or incompatible software is installed. Compatible software on SYSCTL ..............................................6 - 3 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 381 LED flashes 11 times. On flashes 3, 4, 7, 8, and 11, CR/MJ LEDs simultaneously light while MN/ABN ACO/TST LED flashes. On flashes 1, 2, 5, 6, 9, and 10, CR/MJ only the LED flashes. CR/MJ ..............................................365-372-333 R2.1 Lucent Technologies 6 - 3 7 Issue 4, June 2005...
  • Page 382 SYSCTL is now ready to accept a download. Continue with Step ................................Important! If the Network Element was provisioned with non-default values for the NSAP address Organizational ID ..............................................6 - 3 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 383 View →... Important! This is not the menu bar item ; it is View: located above the NE Name pull-down menu (Figure 6-8, “CIT OSI neighbor” (6-40))..............................................365-372-333 R2.1 Lucent Technologies 6 - 3 9 Issue 4, June 2005...

  • Page 384: Cit Osi Neighbor

    Network View, it is possible that OSI was previously disabled on LAN-1. Proceed to “Procedure 6-3.9: Log in serially and enable FTP and/or OSI on the LAN port” (6-134) to log in and enable OSI..............................................6 - 4 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 385 Upon reset, the IP provisioning is again uploaded from the OC-N Main OLIUs, therefore over-writing the new IP provisioning. The default values for the NSAP address Organizational ID (ORG) and Routing Domain (RD) fields are ..............................................365-372-333 R2.1 Lucent Technologies 6 - 4 1 Issue 4, June 2005...
  • Page 386 ................................Enter the following default login/password in NE Login Dialog window (login information is case sensitive) to log in to the NE. LUC01 DMXPLR2.5G User ID: Password: ..............................................6 - 4 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 387 SYSCTL appears in the title bar after Metropolis(R) DMXplore. The figure below indicates that the SYSCTL has 2.1 boot code. Your boot code may be different..............................................365-372-333 R2.1 Lucent Technologies 6 - 4 3 Issue 4, June 2005...
  • Page 388 (preferred) • “Procedure 6-3.4: Initial software generic installation via FTTD (2.0 boot code)” (6-80) • “Procedure 6-3.6: Initial software generic installation via FTP (2.0 boot code)” (6-104) ..............................................6 - 4 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 389 ALL user-provisioned parameters (except circuit IDs) are restored from the OC-N Main OLIUs after the software applied and the shelf reset. Log in to the shelf using your original user ID and password..............................................365-372-333 R2.1 Lucent Technologies 6 - 4 5 Issue 4, June 2005...
  • Page 390 ″Modify parameters on an existing cross-connection,″ click Next and follow the Wizard to provision the circuit ID(s). STOP! End of Procedure. T E P S .................................................................................. 6 - 4 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 391: Procedure 6-3.1: Initial Software Generic Installation Via Ftam (2.1 Or Later Boot Code)

    SYSCTL (VLNC1) with 2.1 or later boot code. Prior to performing this procedure, complete “Procedure 6-3: Replace Before you begin a SYSCTL (VLNC1) circuit pack” (6-35)..............................................365-372-333 R2.1 Lucent Technologies 6 - 4 7 Issue 4, June 2005...
  • Page 392 If your boot code is 2.1 or later, you will see the following screen. Read the material and click to continue with the Initial Wizard Software Download Wizard..............................................6 - 4 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 393 Procedure 6-3.1: Initial software generic Supporting procedures installation via FTAM (2.1 or later boot code) Result: The following welcome screen (Screen 1 of 5) appears..............................................365-372-333 R2.1 Lucent Technologies 6 - 4 9 Issue 4, June 2005...
  • Page 394 FTAM (2.1 or later boot code) ................................On Screen 1, read the material, select FTAM and click Next Important! LAN-1 is the port on the faceplate of the SYSCTL circuit pack..............................................6 - 5 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 395 OSI on LAN-1, refer to the Metropolis DMXplore Access Multiplexer User Operations Guide, 365-372-332................................From Screen 2, ensure that OSI is enabled on LAN-1. Click Next ..............................................365-372-333 R2.1 Lucent Technologies 6 - 5 1 Issue 4, June 2005...
  • Page 396 WaveStar CIT and software generic, the software generics/dmxplore/2.1.0/p/ generic is located in . (If necessary, replace 2.1.0 with your current release, for example 2.1.1.) The ..............................................6 - 5 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 397 CIT as your FTP server, the ® WaveStar CIT fills in the beginning of the default path (C:/Program Files/Lucent Technologies/WaveStar CIT/). If you are not using the ® WaveStar CIT as your FTP server, enter the path starting from the home directory on your FTP server.
  • Page 398 Enabled, initialization removes all cross-connections, and establishes the default 1+1 cross-connections. • Disabled. When the Cross-Connections Initialization parameter is set to Disabled, initialization removes all cross-connections. Click Next ..............................................6 - 5 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 399 Procedure 6-3.1: Initial software generic Supporting procedures installation via FTAM (2.1 or later boot code) Result: Screen 5 appears................................On Screen 5, click Finish ..............................................365-372-333 R2.1 Lucent Technologies 6 - 5 5 Issue 4, June 2005...
  • Page 400 LED simultaneously light for MN/ABN ACO/TST approximately 8 seconds and then extinguish • LED flashes eleven times CR/MJ • All LEDs remain extinguished; the reset is complete..............................................6 - 5 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 401 WaveStar CIT session” (6-24) ................................Is the Generic Software Version correct? If... Then... STOP! End of Procedure. Contact your support center. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 6 - 5 7 Issue 4, June 2005...

  • Page 402: Procedure 6-3.2: Initial Software Generic Installation Via Ftam

    Access Management (FTAM) protocol in a factory-fresh SYSCTL (VLNC1) with 2.0 boot code. Prior to performing this procedure, complete “Procedure 6-3: Replace Before you begin a SYSCTL (VLNC1) circuit pack” (6-35)..............................................6 - 5 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 403 ................................If your boot code is 2.0, you will see the following screen. Read the material and click to continue with the Initial Software Wizard Download Wizard..............................................365-372-333 R2.1 Lucent Technologies 6 - 5 9 Issue 4, June 2005...
  • Page 404 Procedure 6-3.2: Initial software generic Supporting procedures installation via FTAM (2.0 boot code) Result: The following welcome screen (Screen 1 of 4) appears..............................................6 - 6 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 405 Procedure 6-3.2: Initial software generic Supporting procedures installation via FTAM (2.0 boot code) ................................On Screen 1 of 4, read the material, select FTAM and click Next ..............................................365-372-333 R2.1 Lucent Technologies 6 - 6 1 Issue 4, June 2005...
  • Page 406 Continue through the wizard and if you wish to ® disable OSI on LAN-1, refer to the Metropolis DMXplore Access Multiplexer User Operations Guide, 365-372-332..............................................6 - 6 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 407 If you selected the default installation option for the ® WaveStar CIT and software generic, the software generic is located generics/dmxplore/2.1.0/p/ . (If necessary, replace 2.1.0 with ..............................................365-372-333 R2.1 Lucent Technologies 6 - 6 3 Issue 4, June 2005...
  • Page 408 CIT as your FTP server, the ® WaveStar CIT fills in the beginning of the default path (C:/Program Files/Lucent Technologies/WaveStar CIT/). If you are not using the ® WaveStar CIT as your FTP server, enter the path starting from the home directory on your FTP server.
  • Page 409 LED simultaneously light for MN/ABN ACO/TST approximately 12 seconds and then extinguish • LED and LED simultaneously light for MN/ABN ACO/TST approximately 8 seconds and then extinguish ..............................................365-372-333 R2.1 Lucent Technologies 6 - 6 5 Issue 4, June 2005...
  • Page 410 WaveStar CIT session” (6-24) ................................Is the Generic Software Version correct? If... Then... STOP! End of Procedure. Contact your support center. T E P S .................................................................................. 6 - 6 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 411: Procedure 6-3.3: Initial Software Generic Installation Via Fttd (2.1 Or Later Boot Code)

    Overview factory-fresh SYSCTL with 2.1 or later boot code. Prior to performing this procedure, complete “Procedure 6-3: Replace Before you begin a SYSCTL (VLNC1) circuit pack” (6-35)..............................................365-372-333 R2.1 Lucent Technologies 6 - 6 7 Issue 4, June 2005...
  • Page 412 If your boot code is 2.1 or later, you will see the following screen. Read the material and click to continue with the Initial Wizard Software Download Wizard..............................................6 - 6 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 413 FTTD (2.1 or later boot code) Result: The following welcome screen (Screen 1 of 5) appears if you have a VLNC1 with 2.1 boot code..............................................365-372-333 R2.1 Lucent Technologies 6 - 6 9 Issue 4, June 2005...
  • Page 414 Procedure 6-3.3: Initial software generic Supporting procedures installation via FTTD (2.1 or later boot code) ................................On Screen 1 of 5, read the material, select FTAM-FTP (FTTD) Gateway and click Next ..............................................6 - 7 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 415 On Screen 2, enter the TID of the FTAM-FTP Gateway (your gateway network element) in the field and click . The NSAP Get NSAP fields are automatically populated. Click Next ..............................................365-372-333 R2.1 Lucent Technologies 6 - 7 1 Issue 4, June 2005...
  • Page 416 If the WaveStar CIT or your PC is your FTP server and you do not know the IP address: Select from the Windows menu. Start Type and click ..............................................6 - 7 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 417 CIT as your FTP server, the ® WaveStar CIT fills in the beginning of the default path (C:/Program Files/Lucent Technologies/WaveStar CIT/). ® If the FTP server is not the WaveStar CIT, then enter the path starting at the FTP home directory on the server.
  • Page 418 CIT as your FTP server, the ® WaveStar CIT fills in the beginning of the default path (C:/Program Files/Lucent Technologies/WaveStar CIT/). ® If the FTP server is not the WaveStar CIT, then enter the path starting at the FTP home directory on the server.
  • Page 419 NE are not affected. On Screen 4, select the Cross-Connections Initialization parameter you wish for your system (Enabled or Disabled)..............................................365-372-333 R2.1 Lucent Technologies 6 - 7 5 Issue 4, June 2005...
  • Page 420 Enabled, initialization removes all cross-connections, and establishes the default 1+1 cross-connections. • Disabled. When the Cross-Connections Initialization parameter is set to Disabled, initialization removes all cross-connections..............................................6 - 7 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 421 Verify that the information is correct and click The initial software download is a two-part process, totalling approximately 15 minutes. The first part, download of the ..............................................365-372-333 R2.1 Lucent Technologies 6 - 7 7 Issue 4, June 2005...
  • Page 422 Proceed to “Procedure 6-11: Observe FTP progress” (6-197) and then continue with Step Continue with Step ................................After the download is complete, a completion message appears. Click ..............................................6 - 7 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 423 WaveStar CIT session” (6-24) ................................Is the Generic Software Version correct? If... Then... STOP! End of Procedure. Contact your support center. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 6 - 7 9 Issue 4, June 2005...

  • Page 424: Procedure 6-3.4: Initial Software Generic Installation Via Fttd

    Use this procedure to install software generic via FTTD in a Overview factory-fresh SYSCTL with 2.0 boot code. Prior to performing this procedure, complete “Procedure 6-3: Replace Before you begin a SYSCTL (VLNC1) circuit pack” (6-35)..............................................6 - 8 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 425: Boot Code)

    ................................If your boot code is 2.0, you will see the following screen. Read the material and click to continue with the Initial Software Wizard Download Wizard..............................................365-372-333 R2.1 Lucent Technologies 6 - 8 1 Issue 4, June 2005...
  • Page 426 Supporting procedures installation via FTTD (2.0 boot code) Result: The following welcome screen (Screen 1 of 4) appears if you have a VLNC1 with 2.0 boot code..............................................6 - 8 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 427 Procedure 6-3.4: Initial software generic Supporting procedures installation via FTTD (2.0 boot code) ................................On Screen 1 of 4, read the material, select FTAM-FTP (FTTD) Gateway and click Next ..............................................365-372-333 R2.1 Lucent Technologies 6 - 8 3 Issue 4, June 2005...
  • Page 428 On Screen 2, enter the TID of the FTAM-FTP Gateway (your gateway network element) in the field and click Get NSAP . The NSAP fields are automatically populated. Click Next ..............................................6 - 8 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 429 If there is more than one IP address, determine which connection is used to connect to the NE and record the appropriate IP address..............................................365-372-333 R2.1 Lucent Technologies 6 - 8 5 Issue 4, June 2005...
  • Page 430 CIT as your FTP server, the ® WaveStar CIT fills in the beginning of the default path (C:/Program Files/Lucent Technologies/WaveStar CIT/). If you are not using the ® WaveStar CIT as your FTP server, enter the path starting from the home directory on your FTP server.
  • Page 431 . Note: The download source directory is generics/dmxplore/2.1.x/p. The initial software download is a two-part process, totalling approximately 22 minutes. The first part, FTAM download of ..............................................365-372-333 R2.1 Lucent Technologies 6 - 8 7 Issue 4, June 2005...
  • Page 432 All LEDs remain extinguished; the reset is complete................................® Establish a WaveStar CIT session (specifying either OSI or Serial in ® field) and re-log in to your Metropolis Connection Type: DMXplore shelf..............................................6 - 8 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 433 WaveStar CIT session” (6-24) ................................Is the Generic Software Version correct? If... Then... STOP! End of Procedure. Contact your support center. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 6 - 8 9 Issue 4, June 2005...

  • Page 434: Procedure 6-3.5: Initial Software Generic Installation Via Ftp (2.1 Boot Code)

    SYSCTL (VLNC1) with 2.1 or later boot code. Prior to performing this procedure, complete “Procedure 6-3: Replace Before you begin a SYSCTL (VLNC1) circuit pack” (6-35)..............................................6 - 9 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 435 If your boot code is 2.1 or later, you will see the following screen. Read the material and click to continue with the Initial Wizard Software Download Wizard..............................................365-372-333 R2.1 Lucent Technologies 6 - 9 1 Issue 4, June 2005...
  • Page 436 Supporting procedures installation via FTP (2.1 boot code) Result: The following welcome screen (Screen 1 of 5) appears if you have a VLNC1 with 2.1 boot code..............................................6 - 9 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 437 Procedure 6-3.5: Initial software generic Supporting procedures installation via FTP (2.1 boot code) ................................On Screen 1 of 5, read the material, select and click Next ..............................................365-372-333 R2.1 Lucent Technologies 6 - 9 3 Issue 4, June 2005...
  • Page 438 DO NOT change the existing provisioning. You must use the IP address provisioned to complete the FTP software download. If you are unable to use the provisioned IP address, proceed to ..............................................6 - 9 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 439 IP Address, IP Subnet Mask, and/or IP Default Router Address. Click Next Important! LAN-1 is the port on the faceplate of the SYSCTL circuit pack..............................................365-372-333 R2.1 Lucent Technologies 6 - 9 5 Issue 4, June 2005...
  • Page 440 If the WaveStar CIT or your PC is your FTP server and you do not know the IP address: Select from the Windows menu. Start Type and click ..............................................6 - 9 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 441 CIT as your FTP server, the ® WaveStar CIT fills in the beginning of the default path (C:/Program Files/Lucent Technologies/WaveStar CIT/). ® If the FTP server is not the WaveStar CIT, then enter the path starting at the FTP home directory on the server.
  • Page 442 CIT as your FTP server, the ® WaveStar CIT fills in the beginning of the default path (C:/Program Files/Lucent Technologies/WaveStar CIT/). ® If the FTP server is not the WaveStar CIT, then enter the path starting at the FTP home directory on the server.
  • Page 443 NE are not affected. On Screen 4, select the Cross-Connections Initialization parameter you wish for your system (Enabled or Disabled)..............................................365-372-333 R2.1 Lucent Technologies 6 - 9 9 Issue 4, June 2005...
  • Page 444 Enabled, initialization removes all cross-connections, and establishes the default 1+1 cross-connections. • Disabled. When the Cross-Connections Initialization parameter is set to Disabled, initialization removes all cross-connections..............................................6 - 1 0 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 445 Verify that the information is correct and click The initial software download is a two-part process, totalling approximately 15 minutes. The first part, download of the ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 0 1 Issue 4, June 2005...
  • Page 446 Proceed to “Procedure 6-11: Observe FTP progress” (6-197) and then continue with Step Continue with Step ................................After the download is complete, a completion message appears. Click ..............................................6 - 1 0 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 447 WaveStar CIT session” (6-24) ................................Is the Generic Software Version correct? If... Then... STOP! End of Procedure. Contact your support center. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 6 - 1 0 3 Issue 4, June 2005...

  • Page 448: Procedure 6-3.6: Initial Software Generic Installation Via Ftp (2.0 Boot Code)

    Use this procedure to install software generic via FTP in a Overview factory-fresh SYSCTL with 2.0 boot code. Prior to performing this procedure, complete “Procedure 6-3: Replace Before you begin a SYSCTL (VLNC1) circuit pack” (6-35)..............................................6 - 1 0 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 449 If your boot code is 2.0, you will see the following screen. Read the material and click to continue with the Initial Software Wizard Download Wizard..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 0 5 Issue 4, June 2005...
  • Page 450 Supporting procedures installation via FTP (2.0 boot code) Result: The following welcome screen (Screen 1 of 4) appears if you have a VLNC1 with 2.0 boot code..............................................6 - 1 0 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 451 Procedure 6-3.6: Initial software generic Supporting procedures installation via FTP (2.0 boot code) ................................On Screen 1 of 4, read the material, select and click Next ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 0 7 Issue 4, June 2005...
  • Page 452 FTP software download. If you are unable to use the provisioned IP address, proceed to “Procedure 6-3.2: Initial software generic installation via FTAM (2.0 boot code)” (6-58)..............................................6 - 1 0 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 453 If the WaveStar CIT or your PC is your FTP server and you do not know the IP address: Select from the Windows Start menu. Type and click ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 0 9 Issue 4, June 2005...
  • Page 454 The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path C:/Program Files/Lucent Technologies/ names; for example: WaveStar CIT/generics/dmxplore/2.1.0/p .
  • Page 455 The initial software download is a two-part process, totalling approximately 22 minutes. The first part, FTP download of the cpy-mem software ( ), takes approximately 12 minutes. The ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 1 1 Issue 4, June 2005...
  • Page 456 “Procedure 6-11: Observe FTP progress” (6-197) and then continue with Step Continue with Step ................................After the FTP download is complete, a completion message appears. Click ..............................................6 - 1 1 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 457 WaveStar CIT session” (6-24) ................................Is the Generic Software Version correct? If... Then... STOP! End of Procedure. Contact your support center. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 6 - 1 1 3 Issue 4, June 2005...

  • Page 458: Procedure 6-3.7: Initial Software Generic Installation Via Ftp (1.0 Boot Code)

    Overview factory-fresh SYSCTL (VLNC1) with 1.0 boot code. Prior to performing this procedure, complete “Procedure 6-3: Replace Before you begin a SYSCTL (VLNC1) circuit pack” (6-35)..............................................6 - 1 1 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 459 If your boot code is 1.0, you will see the following screen. Read the material and click to continue with the Initial Software Wizard Download Wizard..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 1 5 Issue 4, June 2005...
  • Page 460 VLNC1 with 1.0 boot code................................On Screen 1, read the material and click to continue with the Next Initial Software Download Wizard..............................................6 - 1 1 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 461 Continue through the wizard and if you wish to ® disable OSI on LAN-1, refer to the Metropolis DMXplore Access Multiplexer User Operations Guide, 365-372-332..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 1 7 Issue 4, June 2005...
  • Page 462 If the port already has information provisioned, DO NOT change the existing provisioning. You must use the IP address provisioned to complete the FTP software download. If you are unable to use the ..............................................6 - 1 1 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 463 From Screen 3, follow the instructions to enable TCP/IP function on the LAN port. Click Modify to enter the IP Address, IP Subnet Mask, and/or IP Default Router Address. Click Next Result: Screen 4 appears..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 1 9 Issue 4, June 2005...
  • Page 464 The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name followed by a colon (:) then the path C:/Program Files/Lucent Technologies/ names; for example: WaveStar CIT/generics/dmxplore/2.1.0/p .
  • Page 465 Verify that the information is correct and click cpy-mem The FTP download of the software ( ), takes approximately 12 minutes..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 2 1 Issue 4, June 2005...
  • Page 466 LEDs’ state: • LED extinguishes MN/ABN • LED and LED simultaneously light for MN/ABN ACO/TST approximately 12 seconds and then extinguish ..............................................6 - 1 2 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 467 WaveStar CIT session” (6-24) ................................Is the Generic Software Version correct? If... Then... STOP! End of Procedure. Contact your support center. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 6 - 1 2 3 Issue 4, June 2005...

  • Page 468: Procedure 6-3.8: Initial Software Generic Installation Or Download And Upgrade Via A Serial Connection

    SYSCTL circuit pack. RS232 ® Important! DO NOT establish a WaveStar CIT session................................Double-click on the DMX Family Software folder on your Desktop..............................................6 - 1 2 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 469 The files in this directory are used for serial downloads of the software. (Your software release may be different.) Follow the instructions on the subsequent screens..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 2 5 Issue 4, June 2005...
  • Page 470 Procedure 6-3.8: Initial software generic Supporting procedures installation or download and upgrade via a serial connection ..............................................6 - 1 2 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 471 Procedure 6-3.8: Initial software generic Supporting procedures installation or download and upgrade via a serial connection ................................Press Enter..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 2 7 Issue 4, June 2005...
  • Page 472 SYSTEM TID: LT-DMXPLORE */ LT-DMXPLORE is the default TID. Your TID may be different................................Press Enter and type ACT-USER:LT-DMXPLORE:LUC01:CTAG::DMXPLR2.5G; . (If necessary, replace LT-DMXPLORE with your TID.) ..............................................6 - 1 2 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 473 Supporting procedures installation or download and upgrade via a serial connection Result: The following screen appears................................INS-PRGM:LT-DMXPLORE::CTAG::,,,:PGMTYPE=ALL; Enter . (If necessary, replace LT-DMXPLORE with your TID.) ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 2 9 Issue 4, June 2005...
  • Page 474 100 minutes. The first part, download of the software INS-PRGM ), takes approximately 90 minutes. The second part, the ..............................................6 - 1 3 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 475 Important! Do NOT insert a new circuit pack in the shelf until after you apply the new software generic and clear the dormant/exec version mismatch condition..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 3 1 Issue 4, June 2005...
  • Page 476 Metropolis DMXplore shelf? If... Then... Proceed to “Procedure 6-6: Apply software generic” (6-157) and then continue with Step Continue with Step ..............................................6 - 1 3 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 477 Is this software generic to be installed on other nodes in this network? If... Then... Proceed to “Procedure 6-7: Software generic copy and upgrade to a remote shelf” (6-161). STOP! End of Procedure. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 6 - 1 3 3 Issue 4, June 2005...
  • Page 478 Result: The DMX Family Software folder contains the ® short-cut icon for the Metropolis DMXplore software release to be installed. Your software release may be different..............................................6 - 1 3 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 479 The files in this directory are used for serial downloads of the software. (Your software release may be different.) Follow the instructions on the subsequent screens..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 3 5 Issue 4, June 2005...
  • Page 480 Procedure 6-3.9: Log in serially and enable Supporting procedures FTP and/or OSI on the LAN port ..............................................6 - 1 3 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 481 Procedure 6-3.9: Log in serially and enable Supporting procedures FTP and/or OSI on the LAN port ................................Press Enter..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 3 7 Issue 4, June 2005...
  • Page 482 The response will be ® LT-DMXPLORE is the default TID for Metropolis ® DMXplore/Metropolis DMX. Your TID may be different................................Press Enter and type ACT-USER:LT-DMXPLORE:LUC01:CTAG::DMXPLR2.5G; ..............................................6 - 1 3 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 483 TID, user ID and password, or contact your next level of support. STOP! End of Procedure................................Do you need to enable FTP? If... Then... Continue with Step Proceed to Step ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 3 9 Issue 4, June 2005...
  • Page 484 ® From the Network View, establish a WaveStar CIT session (specifying Serial in the field) and log in to your Connection Type: ® Metropolis DMXplore shelf..............................................6 - 1 4 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 485: Procedure 6-3.9: Log In Serially And Enable Ftp And/Or Osi On The Lan Port

    CIT session” (6-24) ................................Read the material and click to continue with the Initial Wizard Software Download Wizard and determine the boot code of your SYSCTL..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 4 1 Issue 4, June 2005...
  • Page 486 The following welcome screen (Screen 1 of 5) appears if you have a VLNC1 with 2.1 boot code..............................................6 - 1 4 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 487 Supporting procedures FTP and/or OSI on the LAN port The following welcome screen (Screen 1 of 4) appears if you have a VLNC1 with 2.0 boot code..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 4 3 Issue 4, June 2005...
  • Page 488 Supporting procedures FTP and/or OSI on the LAN port The following welcome screen (Screen 1 of 5) appears if you have a VLNC1 with 1.0 boot code..............................................6 - 1 4 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 489 OSI and download the software via FTAM. Continue with Step ................................On Screen 1 of 5, (displayed in Step 13), read the material and click Next ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 4 5 Issue 4, June 2005...
  • Page 490 FTP and/or OSI on the LAN port Result: Screen 2 appears................................Enable OSI on LAN-1. Click and then click to exit the Apply Cancel initial software download wizard..............................................6 - 1 4 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 491 SYSCTL (VLNC1) circuit pack” (6-35) and begin with Step Proceed to “Procedure 6-7: Software generic copy and upgrade to a remote shelf” (6-161). T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 6 - 1 4 7 Issue 4, June 2005...

  • Page 492: Procedure 6-4: Replace Combination Circuit Pack

    System Timing tab. The Active Circuit Pack item reads either main-1 or main-2................................Is the circuit pack that you wish to replace the active circuit pack? If... Then... Continue with Step ..............................................6 - 1 4 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 493 If synchronization autoreconfiguration is disabled, and the active circuit pack is removed, the system enters holdover. Select Enabled for Synchronization Autoreconfiguration and click ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 4 9 Issue 4, June 2005...
  • Page 494 2. Open the faceplate latches and seat the replacement circuit pack in the empty slot by applying steady pressure to the faceplate and latch assemblies..............................................6 - 1 5 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 495 ................................Did you enable system autoreconfiguration in Step If... Then... Continue with Step Proceed to Step ................................Configuration → Timing/Sync From the System View menu, select ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 5 1 Issue 4, June 2005...
  • Page 496 NE Alarm List. Verify that no alarms are present for the installed circuit pack. If required, refer to the appropriate procedure to clear any alarms. T E P S .................................................................................. 6 - 1 5 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 497: Procedure 6-5: Replace Ethernet Circuit Pack

    Important! The VLNC30 Ethernet circuit pack may be equipped with up to two pluggable transmission modules. If required, disconnect the optical cables and remove any pluggable transmission modules from the circuit pack..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 5 3 Issue 4, June 2005...
  • Page 498 Function Group C slot by applying steady pressure to the faceplate and latch assembly. Secure the replacement circuit pack in the shelf using the latch lever..............................................6 - 1 5 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 499 Important! The VLNC30 Ethernet circuit pack may be equipped with up to two pluggable transmission modules. If required, install the pluggable transmission modules and reconnect the optical cables..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 5 5 Issue 4, June 2005...
  • Page 500 If required, refer to the appropriate procedure in the Metropolis DMXplore Access Multiplexer User Operations Guide, 365-372-332 to change any circuit pack/port parameters. T E P S .................................................................................. 6 - 1 5 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 501: Procedure 6-6: Apply Software Generic

    Save As log. Important! Do NOT insert circuit packs into the shelf until after the apply is complete. The apply is not complete if the Alarm ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 5 7 Issue 4, June 2005...
  • Page 502 • If your time format preference is a 24-hour clock, select the Hour: (0-23), Minutes: (0-59), and Seconds: (0-59) from the pull-down menus..............................................6 - 1 5 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 503 The System View closes................................® Establish a WaveStar CIT session (depending on the physical ® connection used) and re-log in to your Metropolis DMXplore shelf..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 5 9 Issue 4, June 2005...
  • Page 504 STOP! End of Procedure. Contact your support center. T E P S .................................................................................. 6 - 1 6 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 505: Procedure 6-7: Software Generic Copy And Upgrade To A Remote Shelf

    Copy of the new system generic software program on your PC or FTP server. • ® Current Metropolis DMXplore Access Multiplexer Software Release Description for the software generic being installed..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 6 1 Issue 4, June 2005...
  • Page 506 Therefore, you will not see remote install/copy program IP condition in this scenario..............................................6 - 1 6 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 507 Do you wish to apply (activate) the software generic that you recently copied to the dormant area of the remote NE? If... Then... Proceed to “Procedure 6-6: Apply software generic” (6-157)..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 6 3 Issue 4, June 2005...
  • Page 508 If... Then... If required, repeat this procedure from Step 2 to copy the software generic to another remote NE. T E P S .................................................................................. 6 - 1 6 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 509: Procedure 6-8: Backup And Restore Ne Database Via Ftp

    Connect the PC and establish a WaveStar CIT session with the gateway NE. Important! You must have direct TCP/IP connectivity to your NE and the NE must have a defined IP address..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 6 5 Issue 4, June 2005...
  • Page 510 FTP” (6-169). performing a system Proceed to “Procedure 6-8.3: Restore restore, NE database via FTP” (6-174). T E P S .................................................................................. 6 - 1 6 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 511: Procedure 6-8.1: Backup Ne Database Via Ftp

    Entries to the Profile pull-down menu may be changed using the Modify Apply , and Save buttons or removed using the Delete button..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 6 7 Issue 4, June 2005...
  • Page 512 CIT directory automatically enters the relative ® path for the WaveStar CIT. The default relative path is C:/Program Files/Lucent Technologies/WaveStar CIT/ If you wish to store your data in a subdirectory within the default backups/<subdirectory>/<filename> path, you may enter the subdirectory exists before the command is sent. Directories will not be created by this command, and therefore the command will be denied if any directory in the path does not already exist.

  • Page 513: Procedure 6-8.2: Provision Automatic Database Backup Schedule Via Ftp

    FTP server should be used................................From the Configure Auto Backup Interval window, select the Files at the top of the window................................In the pull-down menu, select Backup To/Via: ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 6 9 Issue 4, June 2005...
  • Page 514 Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name ..............................................6 - 1 7 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 515 CIT directory automatically enters the relative ® path for the WaveStar CIT. The default relative path is C:/Program Files/Lucent Technologies/WaveStar CIT/ If you wish to store your data in a subdirectory within the default backups/<subdirectory>/<filename> path, you may enter the subdirectory exists before the command is sent. Directories will not be created by this command, and therefore the command will be denied if any directory in the path does not already exist.
  • Page 516 It is recommended that only one backup occur at a time for the CIT. However, larger servers may be able to handle multiple backups at the ..............................................6 - 1 7 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 517 ................................Click A warning appears indicating that executing this Result: command may temporarily affect service. If this is acceptable, select T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 6 - 1 7 3 Issue 4, June 2005...

  • Page 518: Procedure 6-8.3: Restore Ne Database Via Ftp

    ................................In the pull-down menu, select Restore From/Via: ..............................................6 - 1 7 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 519 Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 7 5 Issue 4, June 2005...
  • Page 520 CIT directory automatically enters the relative ® path for the WaveStar CIT. The default relative path is C:/Program Files/Lucent Technologies/WaveStar CIT/ ................................Click You will be asked to verify that you wish to restore the data from the backup file that you entered above. Click if you entered the path correctly.

  • Page 521: Procedure 6-9: Backup And Restore Ne Database Via Fttd

    FTP server. Refer to “Procedure 6-12: Disable an FTP server” (6-199) for instructions for each allowed operating system..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 7 7 Issue 4, June 2005...
  • Page 522 (the NSAP is a 40-digit hex number). This NSAP is required later in this procedure................................® Establish a WaveStar CIT session to the remote Network Element..............................................6 - 1 7 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 523 FTTD” (6-183). performing a system Proceed to “Procedure 6-9.3: Restore restore, NE database via FTTD” (6-188). T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 6 - 1 7 9 Issue 4, June 2005...

  • Page 524: Procedure 6-9.1: Backup Ne Database Via Fttd

    (required value for Psel is 02, Ssel is 5353, is 5454). Tsel Click Modify Replace _template_ with the TID of the FTAM-FTP gateway NE..............................................6 - 1 8 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 525 Save Important! Entries to the pull-down menu may be Profile changed using the , and buttons or removed Modify Apply Save using the Delete button..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 8 1 Issue 4, June 2005...
  • Page 526 CIT directory automatically enters the relative ® path for the WaveStar CIT. The default relative path is C:/Program Files/Lucent Technologies/WaveStar CIT/ If you wish to store your data in a subdirectory, you may enter backups/<subdirectory>/<filename> if the subdirectory exists before the command is sent. Directories will not be created by this command, and therefore the command will be denied if any directory in the path does not already exist.

  • Page 527: Procedure 6-9.2: Provision Automatic Database Backup Schedule Via Fttd

    From the Configure Auto Backup Interval window, select the Files at the top of the window................................In the pull-down menu, select and select the Backup To/Via: FTTD FTTD tab..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 8 3 Issue 4, June 2005...
  • Page 528 . The TID has been added to the pull-down menu for this CIT and you should never need to re-enter the NSAP address for this gateway NE’s TID................................Select the tab..............................................6 - 1 8 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 529 Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root directory. The absolute path must start with the drive name ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 8 5 Issue 4, June 2005...
  • Page 530 CIT directory automatically enters the relative ® path for the WaveStar CIT. The default relative path is C:/Program Files/Lucent Technologies/WaveStar CIT/ If you wish to store your data in a subdirectory, you may enter backups/<subdirectory>/<filename> if the subdirectory exists before the command is sent. Directories will not be created by this command, and therefore the command will be denied if any directory in the path does not already exist.
  • Page 531 ................................Click Result: A warning appears indicating that executing this command may temporarily affect service. If this is acceptable, select T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 6 - 1 8 7 Issue 4, June 2005...

  • Page 532: Procedure 6-9.3: Restore Ne Database Via Fttd

    ................................In the pull-down Restore From/Via: menu, select FTTD and select FTTD tab..............................................6 - 1 8 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 533 . The TID has been added to the pull-down menu for this CIT and you should never need to re-enter the NSAP address for this gateway NE’s TID................................Select the tab..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 8 9 Issue 4, June 2005...
  • Page 534 CIT. Important! The value of the Path field can be either an absolute path or a relative path that is relative to the FTP server root ..............................................6 - 1 9 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 535 CIT directory automatically enters the relative ® path for the WaveStar CIT. The default relative path is C:/Program Files/Lucent Technologies/WaveStar CIT/ ................................Click You will be asked to verify that you wish to restore the data from the backup file that you entered above. Click if you entered the path correctly.

  • Page 536: Procedure 6-10: Backup And Restore Ne Database Via Ftam

    NE database via FTAM” (6-193). performing a system Proceed to “Procedure 6-10.2: Restore restore, NE database via FTAM” (6-195). T E P S .................................................................................. 6 - 1 9 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 537: Procedure 6-10.1: Backup Ne Database Via Ftam

    CIT directory automatically enters the relative ® path for the WaveStar CIT. The default relative path is C:/Program Files/Lucent Technologies/WaveStar CIT/ If you wish to store your data in a subdirectory, you may enter backups/<subdirectory>/<filename> if the subdirectory exists before the command is sent. Directories will not be created by this command, and therefore the command will be denied if any directory in the path does not already exist.
  • Page 538 . Click the button. Remote Backup successful The backup file is now stored. If the default path and a subdirectory were used, the file may be found at: C:/Program Files/Lucent Technologies/WaveStar CIT/backups/<subdirectory>/<filename> T E P S .................................................................................. 6 - 1 9 4 Lucent Technologies 365-372-333 R2.1...

  • Page 539: Procedure 6-10.2: Restore Ne Database Via Ftam

    Enter the path and filename exactly as it was entered in “Procedure 6-10.1: Backup NE database backups/<subdirectory>/ via FTAM” (6-193). For example: <filename> ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 9 5 Issue 4, June 2005...
  • Page 540 CIT directory automatically enters the relative ® path for the WaveStar CIT. The default relative path is C:/Program Files/Lucent Technologies/WaveStar CIT/ ................................Click You will be asked to verify that you wish to restore from the directory that you entered above. Click if you typed the path correctly.

  • Page 541: Procedure 6-11: Observe Ftp Progress

    The following FTP Server window opens. The FTP server may display multiple FTP sessions listed by ID 1, 2..The active session is identified by a green check-mark ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 9 7 Issue 4, June 2005...
  • Page 542 FTP server. Refer to “Procedure 6-12: Disable an FTP server” (6-199) for instructions for each allowed operating system. T E P S .................................................................................. 6 - 1 9 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 543: Procedure 6-12: Disable An Ftp Server

    Services and Applications Services ................................Locate the FTP file that is running and double click the FTP icon................................In the field, click Service Status: Stop ..............................................365-372-333 R2.1 Lucent Technologies 6 - 1 9 9 Issue 4, June 2005...
  • Page 544 Administrative Tools Services ................................Locate the FTP service that is running and select it................................Click , then Stop Close T E P S .................................................................................. 6 - 2 0 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 545: Procedure 6-13: Establish Communications With Network Element

    ENTER times. Is the network element TID displayed? If... Then... Yes, Record the TID that was displayed and continue with Step Proceed to Step ..............................................365-372-333 R2.1 Lucent Technologies 6 - 2 0 1 Issue 4, June 2005...
  • Page 546 Using the TID that was displayed, attempt to log in to the network element. “Procedure 6-2: Connect personal computer (PC) Reference: ® and establish WaveStar CIT session” (6-24) T E P S .................................................................................. 6 - 2 0 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 547: Procedure 6-14: Replace Pluggable Transmission Module

    Ensure that the correct pluggable optical module is available for replacement. Complete the following steps to replace a pluggable transmission Procedure module................................Remove the optical cables from the required pluggable transmission module..............................................365-372-333 R2.1 Lucent Technologies 6 - 2 0 3 Issue 4, June 2005...
  • Page 548 (away from you), then grip the sides of the module and remove it from the socket. Proceed to Step ..............................................6 - 2 0 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 549: Latch Type 3 (Swivel Latch Opened And Closed)

    Proceed to Step ................................Before removing the pluggable transmission module, the swivel latch must be in the open position. Open the swivel latch and pull gently on ..............................................365-372-333 R2.1 Lucent Technologies 6 - 2 0 5 Issue 4, June 2005...

  • Page 550: Latch Type 4 (Swivel Latch Opened And Closed)

    Figure 6-11, “Pluggable transmission module with dust plug” (6-206). Figure 6-11 Pluggable transmission module with dust plug MA-DMX-422 ..............................................6 - 2 0 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 551: Examples Of Dust Plugs

    Refer to the following figure and determine the type of latching mechanism on the pluggable transmission module. Gold Fingers Port Gold Fingers Port Gold Fingers Port Gold Fingers Port MA-DMX-425 ..............................................365-372-333 R2.1 Lucent Technologies 6 - 2 0 7 Issue 4, June 2005...

  • Page 552: Latch Type 3 (Swivel Latch Opened And Closed)

    Figure 6-13 Latch type 3 (swivel latch opened and closed) Swivel Latch Closed Position (to the right) Swivel Latch Open Position (to the left) MA-DMX-423 ..............................................6 - 2 0 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 553: Latch Type 4 (Swivel Latch Opened And Closed)

    With your left hand, hold the pluggable transmission module by the dust plug. The optical ports are in your left hand and the gold fingers are visible (facing you). (Do not insert pluggable transmission module)..............................................365-372-333 R2.1 Lucent Technologies 6 - 2 0 9 Issue 4, June 2005...
  • Page 554 (6-211).) Confirm that the pluggable transmission module is locked in the socket. Verify that all unused sockets on the circuit pack are equipped with dust plugs..............................................6 - 2 1 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 555: Example Of Inserting A Pluggable Transmission Module Into A Socket (Wall-Mounted Shelf)

    Procedure 6-14: Replace pluggable Supporting procedures transmission module Figure 6-15 Example of inserting a pluggable transmission module into a socket (wall-mounted shelf) Socket Gold Fingers MA-DMX-427 ..............................................365-372-333 R2.1 Lucent Technologies 6 - 2 1 1 Issue 4, June 2005...

  • Page 556: Example Of Inserting A Pluggable Transmission Module Into A Socket (Rack-Mounted Shelf)

    Do not rotate the swivel latch or activate the de-latching feature on the pluggable transmission module................................Reconnect the optical cables..............................................6 - 2 1 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 557 If required, refer to the appropriate procedure in the Metropolis DMXplore Access Multiplexer User Operations Guide, 365-372-332 to change any port parameters. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 6 - 2 1 3 Issue 4, June 2005...

  • Page 558: Procedure 6-15: Clean Optical Fibers, Dual Lc Adapters And Lc Lightguide Buildouts (Lbos)

    Note: The equipment and material listed above has been tested and is proven effective when used in conjunction with this procedure. Substitution of equipment or materials is at the discretion of the user and is not recommended..............................................6 - 2 1 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 559 (LBOs) A course on connector cleaning and the connector inspection process Related information is now offered through Lucent Technologies Learning and Performance Center, Course Code: LMC200H Understanding Fiber Optic Cleaning, Inspection and Testing. To learn more about this course, consult your local Lucent Account Representative.
  • Page 560 LC adapters and LC lightguide buildouts (LBOs) ................................To inspect the optics following cleaning, refer to “Procedure 6-15.3: Optical fiber and connector inspection” (6-222). T E P S .................................................................................. 6 - 2 1 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 561: Procedure 6-15.1: Clean Optical Fibers

    Rotate the cassette lever all the way down with your thumb. Do not release the lever. The lever advances the ″dry″ Luminex cleaning cloth inside the case and simultaneously opens the shutter. The CLETOP ..............................................365-372-333 R2.1 Lucent Technologies 6 - 2 1 7 Issue 4, June 2005...
  • Page 562 Be sure the ferrule is pressed snug against the cleaning cloth while dragging the ferrule to assure the proper cleaning action..............................................6 - 2 1 8 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 563 ................................Inspect the connector for cleanliness. If necessary, repeat the cleaning process. “Procedure 6-15.3: Optical fiber and connector Reference: inspection” (6-222) T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 6 - 2 1 9 Issue 4, June 2005...

  • Page 564: Procedure 6-15.2: Clean Fiber Adapters And Circuit Pack Connectors

    ................................Gently insert the Video Fiber Scope probe into the port until the fiber ferrule comes into view..............................................6 - 2 2 0 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 565 Verify that the fiber ferrule is clean. Repeat Step 1 through Step 3 the fiber does not meet the requirements specified. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 6 - 2 2 1 Issue 4, June 2005...

  • Page 566: Procedure 6-15.3: Optical Fiber And Connector Inspection

    ................................Follow the instructions in the manual provided with the Optical Fiber Scope to view the ferrule endface of the fiber under inspection..............................................6 - 2 2 2 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 567 After the connector has been verified to be cleaned, it should be immediately inserted into the adapter buildout of the optical component. This will assure maximum cleanliness and effectiveness of the connector..............................................365-372-333 R2.1 Lucent Technologies 6 - 2 2 3 Issue 4, June 2005...
  • Page 568 Following this procedure, carefully place the cap over the ferrule. When the cleaned connector is ready for assembly, it should be re-inspected for cleanliness prior to connection. T E P S .................................................................................. 6 - 2 2 4 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...

  • Page 569: Procedure 6-16: Clean Pluggable Transmission Module

    Complete the following steps to clean a pluggable transmission Procedure module................................Remove the protective dust plug from the pluggable transmission module. Keep the dust plug clean until reinstalled later, if required..............................................365-372-333 R2.1 Lucent Technologies 6 - 2 2 5 Issue 4, June 2005...
  • Page 570 Rotate the CLETOP stick five full rounds................................Using the stereo zoom scope, visually inspect the pluggable transmission module. If required, repeat Step ..............................................6 - 2 2 6 Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005...
  • Page 571 If required, reinstall the dust plug into the optical ports to maintain cleanliness. T E P S .................................................................................. 365-372-333 R2.1 Lucent Technologies 6 - 2 2 7 Issue 4, June 2005...
  • Page 573 Alarm Gateway Network Element Alarm Indication Signal Alarm Visible or audible signal indicating that an equipment failure or significant event/condition has occurred..............................................365-372-333 R2.1 Lucent Technologies G L O S S A R Y Issue 4, June 2005 G L - 1...
  • Page 574 It is used to exchange requests and acknowledgments for protection switch actions. ASCII American Standard Code for Information Interchange Auto Automatic ..............................................G L O S S A R Y Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 G L - 2...
  • Page 575 Bidirectional Line A transmission path consisting of two fibers that handle traffic in both the transmit and receive directions..............................................365-372-333 R2.1 Lucent Technologies G L O S S A R Y Issue 4, June 2005 G L - 3...
  • Page 576 An international advisory committee under United Nations’ sponsorship that has composed and recommended for adoption worldwide standards for international communications. Recently changed to the International Telecommunications Union Telecommunications Standards Sector ..............................................G L O S S A R Y Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 G L - 4...
  • Page 577 A performance monitoring parameter indicating that bipolar violations of the signal have occurred. Collocated System elements that are located in the same location. Customer Premises Equipment ..............................................365-372-333 R2.1 Lucent Technologies G L O S S A R Y Issue 4, June 2005 G L - 5...
  • Page 578 (DTE) and the line. The DCE may be separate equipment or an integral part of the DTE or of intermediate equipment. A DCE may perform other functions usually performed at ..............................................G L O S S A R Y Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 G L - 6...
  • Page 579 A designated network element that is responsible for administering a database that maps network element names (TIDs) to addresses (NSAPs - network service access points) in an OSI ..............................................365-372-333 R2.1 Lucent Technologies G L O S S A R Y Issue 4, June 2005 G L - 7...
  • Page 580 A trade association of the electronic industry that establishes electrical and functional standards. Electrostatic Discharge (ESD) Static electrical energy potentially harmful to circuit packs and humans..............................................G L O S S A R Y Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 G L - 8...
  • Page 581 A one- or two-way circuit that carries a transmission signal. Facility Loopback A facility loopback is where an entire line is looped back..............................................365-372-333 R2.1 Lucent Technologies G L O S S A R Y Issue 4, June 2005 G L - 9...
  • Page 582 WaveStar Forced Switch, or Manual Switch command..............................................G L O S S A R Y Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 G L - 1 0...
  • Page 583 Graphical User Interface ..............................................Hashed FTP The hashed FTP (digital signature) capability prevents tampering with a downloadable software image..............................................365-372-333 R2.1 Lucent Technologies G L O S S A R Y Issue 4, June 2005 G L - 1 1...
  • Page 584 A term used to describe distances of 15 to 40 km between optical transmitter and receiver without regeneration. See long reach. Internet Protocol Intermediate Reach In Service International Standards Organization ..............................................G L O S S A R Y Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 G L - 1 2...
  • Page 585 Lightguide Build-Out (LBO) An attenuating (signal-reducing) element used to keep an optical output signal strength within desired limits..............................................365-372-333 R2.1 Lucent Technologies G L O S S A R Y Issue 4, June 2005 G L - 1 3...
  • Page 586 Loss of Pointer ..............................................G L O S S A R Y Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 G L - 1 4...
  • Page 587 Allows an operations system to control and monitor equipment collocated within a set of input and output contact closures. Major Alarm Multimode Minor Alarm ..............................................365-372-333 R2.1 Lucent Technologies G L O S S A R Y Issue 4, June 2005 G L - 1 5...
  • Page 588 Network Service Access Point Address (used in the OSI network layer 3). An automatically assigned number that uniquely identifies a Network Element for the purposes of routing DCC ..............................................G L O S S A R Y Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 G L - 1 6...
  • Page 589 Nonreturn to Zero Not Service Affecting NSAP Address Network Service Access Point Address (used in the OSI network layer 3) ..............................................365-372-333 R2.1 Lucent Technologies G L O S S A R Y Issue 4, June 2005 G L - 1 7...
  • Page 590 The capability to access, operate, provision, and administer remote systems through craft interface access from any site in a SONET/SDH network or from a centralized operations system..............................................G L O S S A R Y Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 G L - 1 8...
  • Page 591 Personal Computer PCMCIA Personal Computer Memory Card International Association ..............................................365-372-333 R2.1 Lucent Technologies G L O S S A R Y Issue 4, June 2005 G L - 1 9...
  • Page 592 A feature that allows a user to supress alarm reporting and performance monitoring during provisioning by supporting multiple states (automatic, in-service, and not monitored) for low-speed ports. See Channel State Provisioning..............................................G L O S S A R Y Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 G L - 2 0...
  • Page 593 It may be the adjacent node on a ring, or N nodes away from the ..............................................365-372-333 R2.1 Lucent Technologies G L O S S A R Y Issue 4, June 2005 G L - 2 1...
  • Page 594 The operational mode of a physical entity that indicates that the entity is providing service. This designation will change with each switch action. Severely Errored Seconds ..............................................G L O S S A R Y Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 G L - 2 2...
  • Page 595 1x1 or 1xN protected circuit pack that is not currently carrying service. See Active..............................................365-372-333 R2.1 Lucent Technologies G L O S S A R Y Issue 4, June 2005 G L - 2 3...
  • Page 596 SONET synchronization messaging is used to communicate the quality of network timing, internal timing status, and timing states throughout a subnetwork..............................................G L O S S A R Y Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 G L - 2 4...
  • Page 597 It is a character string of up to 20 characters where the characters are letters, digits, or hyphens (-). TARP Target Identifiers Address Resolution Protocol ..............................................365-372-333 R2.1 Lucent Technologies G L O S S A R Y Issue 4, June 2005 G L - 2 5...
  • Page 598 The ability of the user to assign cross-connections between any tributaries of any lines within a Network Element. Three types of TSI can be defined: Hairpin TSI, Interring TSI (between ..............................................G L O S S A R Y Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 G L - 2 6...
  • Page 599 (for example, West). If the primary ring fails, then the protection ring takes over. UPD/INIT Update/Intialize ..............................................365-372-333 R2.1 Lucent Technologies G L O S S A R Y Issue 4, June 2005 G L - 2 7...
  • Page 600 Each VT group occupies twelve columns of the 9-row structure and, for VT1.5s, contains four VTs per group..............................................G L O S S A R Y Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 G L - 2 8...
  • Page 601 A technique used to reduce the number of consecutive zeros in a line-codes signal (B3ZS for DS3 signals and B8ZS for DS1 signals)..............................................365-372-333 R2.1 Lucent Technologies G L O S S A R Y Issue 4, June 2005 G L - 2 9...
  • Page 603 FTAM, 6-193 to DSX, 3-20, 5-35 customer comments, xxiii FTP, 6-167 to Fiber, 3-20, 5-37 FTTD, 6-180 DS1 trmsn test IP, 3-22 ..............................................365-372-333 R2.1 Lucent Technologies I N D E X Issue 4, June 2005 I N - 1...
  • Page 604 OCN sig. degrade inc. (from DSX) DS1 LOS, (BER), 3-54 3-40 inc. OCN sig. failed inc. (from DSX) DS1 sig. (BER), 3-55 failed, 3-41 ..............................................I N D E X Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 I N - 2...
  • Page 605 Module removed, 3-82, Member Signal classes, 5-132 Unacceptable - LCAS, eye damage, 3-77 Port administratively disabled, 3-83, 5-135 safety, warning labels, 1-11 ..............................................365-372-333 R2.1 Lucent Technologies I N D E X Issue 4, June 2005 I N - 3...
  • Page 606 VCG Failure of LCAS SYSCTL CP failed, 3-88 5-140 Protocol (Source), 3-93, SYSCTL test, 4-23 5-154 VCG Loss of Partial Capacity, 3-94, 5-156 ..............................................I N D E X Lucent Technologies 365-372-333 R2.1 Issue 4, June 2005 I N - 4...
  • Page 607 5-161 VT, inc. VT alarms, 3-65, 5-108 ............waiting for download, 3-96 warning labels, laser, 1-11 WaveStar CIT connect, 6-24 install, overview, ..............................................365-372-333 R2.1 Lucent Technologies I N D E X Issue 4, June 2005 I N - 5...

Table of Contents