Tellabs OSN

8/13/2019 Tellabs OSN

1/92

Copyright 2003 Tellabs. All rights reserved.

Technical Documentation

Product family Tellabs6300 ManagedTransport System

Product name Tellabs6300 Network Manager

Title Managing Tellabs 7200 OpticalTransport System

Document Users ManualMA326 / Revision A1


2/92

Tellabs 6300Network Manager Legal Notices

Managing Tellabs 7200 Optical Transport System

2 MA326 Rev. A1

Legal Notices

Copyright Statement This Tellabs manual is owned by Tellabs or its licensors and protected by U.S.and international copyright laws, conventions, and treaties. Your right to usethis manual is subject to limitations and restrictions imposed by applicable li-censes and copyright laws. Unauthorized reproduction, modification, distri-bution, display or other use of this manual may result in criminal and civilpenalties.

Trademark Notice The following trademarks and service marks are owned by Tellabs Opera-tions, Inc., or its affiliates in the United States and/or other countries: AUDIOPLUS, CABLESPAN, CEC-128, DYNAMIC SIGNAL TRANSFER,DXX, DXX logo, EC DUO, ENHANCED AUDIO PLUS, EX-PRESS/PATH, FOCUS, MARTIS, MARTISDXX, MARTIS logo, MAR-TISDXX logo, METROVANTAGE, METROWATCH, NETREACH,NETWISE, SCULPTURED SOUND, TELLABS, TELLABS and T sym-bol, T symbol, TELLABS PROPARTNER, TEL/MAP, TEL/MOR, THEWORLD COMMUNICATES THROUGH TELLABS, TITAN, VERITY,YOUR NETWORKING PARTNER.

Any other company or product names may be trademarks of their respectivecompanies.


3/92

Tellabs 6300Network Manager Revision Information


MA326 Rev. A1 3

Revision Information

Revision history This manual has changed as follows:

Rev. Date Description of Changes

A1 Mar. 17, 2003 First revision.


4/92

Tellabs 6300Network Manager Revision Information


4 MA326 Rev. A1


5/92

MA326 Rev. A1 5

Tellabs 6300

Network Manager Contents

Managing Tellabs

7200 Optical Transport System

Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Revision Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

1 Configuring Non-intrusive Monitoring . . . . . . . . . . . . . . . . . . . . . . 7

1.1 What is Non-intrusive Monitoring? . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 The Ports Available for Non-intrusive Monitoring . . . . . . . . . . . . . . . . 8

1.3 Creating a Non-intrusive Monitoring Point at a Port . . . . . . . . . . . . . . 9

1.4 The Non-intrusive Monitoring (NIM) Window . . . . . . . . . . . . . . . . . . 11

1.5 Attributes in the Non-intrusive Monitoring (NIM) Window . . . . . . . . . 12

1.6 Deleting a Non-intrusive Monitoring Point . . . . . . . . . . . . . . . . . . . . . 15

1.7 Viewing/Editing the Configuration of a Non-intrusive Monitoring Point . .

17

2 Testing a Tellabs 7200 System Network Element . . . . . . . . . . . . 192.1 Safety Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

2.2 Automatic Power Shutdown Safety Feature . . . . . . . . . . . . . . . . . . . 22

2.3 Activating Tellabs 7200 System Lasers after an Automatic Power

Shutdown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.4 Description of a Laser Test Process . . . . . . . . . . . . . . . . . . . . . . . . . 232.5 The Optical Ports Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

2.6 Shutting Down a Laser Automatically . . . . . . . . . . . . . . . . . . . . . . . . 24

2.7 Restarting a Laser Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2.8 Testing a Laser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

2.9 Forcing a Laser to be On and Remain On . . . . . . . . . . . . . . . . . . . . 28

2.10 Forcing a Laser to be Switched Off and Remain Off . . . . . . . . . . . . . 29

2.11 Activating a Laser that has been Forced Off . . . . . . . . . . . . . . . . . . . 30

2.12 Adjusting the Attenuator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

2.13 Setting the Decision Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

2.14 Setting the Output Power Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

2.15 Setting the Output Channel Power . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2.16 Attributes in the Optical Ports Window . . . . . . . . . . . . . . . . . . . . . . . 34

2.17 Viewing and/or Changing the Laser Power-level Thresholds . . . . . . 37

3 Configuring Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413.1 Automatic Generation of Alarms by an NE . . . . . . . . . . . . . . . . . . . . 41

3.2 Configuring the Severity Level of and Destination for a Specific Alarm .

41

3.3 Setting the Fault Persistency Attributes . . . . . . . . . . . . . . . . . . . . . . 43

3.4 Suppressing a Specific Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

3.5 Configuring Alarms Generated by Auxiliary Equipment . . . . . . . . . . 45

3.5.1 Using Auxiliary Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . 45

3.5.2 Configuring Alarms Generated by Auxiliary Equipment. . . . . 49

3.6 Enabling/Disabling Laser Power-level Threshold Alarms . . . . . . . . . 50

3.7 Sending Alarms to a Specific Management Center . . . . . . . . . . . . . . 52

4 Tellabs 7200 System Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5 Configuring and Viewing Performance Data . . . . . . . . . . . . . . . . 615.1 Monitor Points, Data Registers and Event Counters . . . . . . . . . . . . . 61

5.1.1 Non-historical Performance Data. . . . . . . . . . . . . . . . . . . . . . 61

5.1.2 Historical Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . 64

5.2 Viewing the Non-historical Performance Data . . . . . . . . . . . . . . . . . . 66

5.3 Monitoring Power Levels at Termination Points . . . . . . . . . . . . . . . . 68

5.4 Specifying Which Historical Performance Data to Display . . . . . . . . 72

5.5 Viewing the Historical Performance Data . . . . . . . . . . . . . . . . . . . . . 74

5.5.1 The Data Presented in List Form. . . . . . . . . . . . . . . . . . . . . . 75

5.5.2 The Data Presented as a Graph . . . . . . . . . . . . . . . . . . . . . . 77


6/92


7/92MA326 Rev. A1 7

Tellabs 6300Network Manager 1 Configuring Non-intrusive Monitoring


1 Configuring Non-intrusive Monitoring

Introduction Non-intrusive monitoring enables you to monitor the status of a path segmentwithout terminating the path. It is a monitoring function only and the moni-tored signal is not influenced in any way, even if a failure is detected. Non-in-trusive monitoring is described in:

1.1 What is Non-intrusive Monitoring? on page 7

1.2 The Ports Available for Non-intrusive Monitoring on page 8

1.3 Creating a Non-intrusive Monitoring Point at a Port on page 9

1.5 Attributes in the Non-intrusive Monitoring (NIM) Window on page12

1.6 Deleting a Non-intrusive Monitoring Point on page 15

1.7 Viewing/Editing the Configuration of a Non-intrusive Monitoring

Point on page 17

1.1 What is Non-intrusive Monitoring?

A network example In the example traffic is being transmitted from end-to-end between station Aand station F. Operator X has to buy capacity from operator Y who operatesstation B, C and D. In order for Y to fulfil his obligation towards X, he wantsto monitor the path segment going through his network. As Y cannot termi-nate the path or in any way influence the signal, he must use Non-intrusiveMonitoring (NIM) of station B and station D.


8/928 MA326 Rev. A1



The properties that can

be monitored

Non-intrusive monitoring provides the same capabilities that the correspond-ing monitoring of termination points does (see 6 Configuring the Termina-tion Points of a Port on page 79). It can:

emit alarms

monitor performance

collect the performance records

check for any mismatch between the expected TTI and the received TTI

set the TTI mismatch detection status.

The parts of a signal that

you can monitor

Non-intrusive monitoring can be created and deleted independently for eachdirection of a path on the incoming signal (in the sink direction).

1.2 The Ports Available for Non-intrusive Monitoring

The ports available for

monitoring

The ports available for non-intrusive monitoring are dependent on the mod-ules installed in the NE. The table shows the modules and the ports availablefor each module.

Note: Non-intrusive monitoring is not supported by all TRP-rx (2P) and TRP-tx (2P) modules. If the TRP-rx (2P) or TRP-tx (2P) module installed inyour NE does not support non-intrusive monitoring, the module willnot be represented in the Ports:list in the Non-intrusive Monitoring (NIM)window.

Module Ports Available for Monitoring

TRP-bd (4P) ClientIn, WDMInTRP-rx (2P) In

TRP-tx (2P) In


9/92MA326 Rev. A1 9



1.3 Creating a Non-intrusive Monitoring Point at a Port

To create a non-intrusive

monitoring point on anincoming signal at a port

This procedure describes how to create a non-intrusive monitoring (NIM)point on an incoming signal through a single port, or a number of selectedports in the NE.

Step Action

1 Select TransportNon-intrusive Monitoring...in the pop-up menuof the NE matrix icon.

The Non-intrusive Monitoring (NIM) window appears.

The Ports:field of the Non-intrusive Monitoring (NIM) window shows

the ports for the NE in a tree structure. The ports available for mon-itoring are dependent on the modules installed in the NE (see Theports available for monitoring on page 8).

Note: You will only see the ports of modules that exist in the NEmodel (see the Expected:field in the Equipmentwindow).


10/9210 MA326 Rev. A1



2 Select the port where you wish to create a non-intrusive monitoringpoint.

The port is highlighted and the Incoming Signalgroup box becomesactive.

Note: When more than one port is selected, only data common toall selected ports are displayed.

3 Click on the Create NIMbutton in the Incoming Signalgroup box.

The Creating NIMwindow appears.

4 Specify the signal type and the bit rate of the client signal in the Sig-nal Type:drop-down list and the Bit Rate:drop-down list.

The signal type can be either SDHor SONET, and the bit rate can be622 Mbit/s, 2488 Mbit/sor 9953 Mbit/s.

5 Click OK.

The Creating NIMwindow closes.

Non-intrusive monitoring for the port takes effect immediately. Thenon-intrusive monitoring configuration attributes appear in the In-coming Signalgroup box. An upward pointing arrow appears be-side the selected port indicating that non-intrusive monitoring hasbeen created on the incoming signal.

Step Action


11/92MA326 Rev. A1 11



1.4 The Non-intrusive Monitoring (NIM) Window

The Non-intrusive

Monitoring (NIM) window

The Non-intrusive Monitoring (NIM) window appears when you select Trans-portNon-intrusive Monitoring...in the pop-up menu of an NE matrix icon.

6 Assign values to the attributes and check the check box if required.

See 1.5 Attributes in the Non-intrusive Monitoring (NIM) Windowon page 12.

Note: If you selected a single port in Step 2, the attribute setting willapply to the single port. If you selected several ports, the attributesetting will apply to all the ports.

7 Repeat steps 3to 6until you have created non-intrusive monitoringand set the attributes for all the ports of interest.

8 Click OK.

The NE is updated with the data and the Non-intrusive Monitoring(NIM) window closes.

Step Action
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


12/9212 MA326 Rev. A1



Description of the arrows

in the Non-intrusive

Monitoring (NIM) window

An upward pointing arrow alongside a port in the Ports:field shows that anon-intrusive monitoring point exists on the incoming signal throgh theport. Non-intrusive monitoring of the signal starts as soon as the arrow ap-pears, and can only be stopped by deleting the non-intrusive monitoring

point. All non-intrusive monitoring points are created with a default configu-ration. That is, with pre-defined values for its attributes, but these values canbe changed.

1.5 Attributes in the Non-intrusive Monitoring (NIM) Window

Attributes and check

boxes

The attributes and check boxes included in the Non-intrusive Monitoring (NIM)window are described below:

Bit Rate (MBit/s) on page 12

Detect TTI Mismatch on page 12

Expected TTI on page 13 Port ID and Module on page 13

Received TTI on page 13

Signal Type on page 14

Threshold on page 14

TPoint Mode on page 14.

Bit Rate (MBit/s)

Shows the bit rate of the client signal (selected in the Creating NIMwindow, see1.3 Creating a Non-intrusive Monitoring Point at a Port on page 9).

This attribute is read-only.

Detect TTI Mismatch

This attribute, which is shown as a check box, determines whether a mismatch

alarm is generated when the Expected TTIattribute is not equal to the ReceivedTTIattribute. It also determines whether or not a value can be entered in theExpected TTI:field.

Value Description

622 The bit rate of the client signal is 622 Mbit/s.



Value Description

selected Enables a value to be entered in the Expected TTI:field, and enables a Section trace mismatchalarmto be generated if a mismatch is detected. If a mis-match is detected, an AIS replaces the signal.

deselected Any mismatch is not detected, and therefore nomismatch alarms are generated. The text field ofthe Expected TTIattribute is deactivated.


13/92MA326 Rev. A1 13



Expected TTI

This attribute is used in the process that verifies that the signal from a trans-mitting NE is routed correctly. This is the trail trace identifier that the NE ex-pects to receive from the transmitting NE at the other end of the trail. The ex-

pected TTI must be assigned the same value as the transmitted TTI of the NEat the other end of the trail. (see 6.3 How to Use Trail Trace Identifiers (TTIs)on page 80).

You must select the Detect TTI Mismatch:check box if you want to enter a valuefor this attribute. If the Expected TTIattribute does not match the Received TTIattribute a mismatch is detected, aSection trace mismatchalarm is generated,and an alarm indication signal (AIS) replaces the signal.

Port ID and Module

Shows the rack, subrack, slot, port name and module of the port selected in thetree structure in the Ports:field. If more than one port is selected in the Ports:field, this field will be empty.


Received TTI

This is the trail trace identifier transmitted by the NE at the other end of thetrail received at this NE. This attribute is read-only.

Value Description

15 byte string If you specify a TTI of less than 15 characters, thesystem adds NULL characters. For example ifyou only enter 14 characters, the system will add

one NULL character to the end of the entered val-ue.

Note: It is not possible to visually distinguish be-tween a space and a NULL character as both arerepresented by a blank character.

Value Description

[//] []

Identifies the port and its location in the NE.

Value Description

15 characters A read-only field showing the trail trace identifier(TTI) received from the other end of the trail thatends here. If the Detect TTI Mismatchcheck box isselected, this value is compared with the value ofthe Expected TTIattribute, to verify that the signalsent to the NE is routed correctly. If a mismatch isdetected, a Section trace mismatchalarm is gener-ated.


14/9214 MA326 Rev. A1



Signal Type

Shows the signal type of the client signal (selected in the Creating NIMwindow,see 1.3 Creating a Non-intrusive Monitoring Point at a Port on page 9).


Threshold

Determines the threshold for activation of the Degraded signalalarm.

TPoint Mode

Determines whether alarms from the monitoring point in question are report-ed to the management center.

16 bytes are not repetitively received and there-fore the value is not read.


This will typically be due to a server layer fault,but in rare cases to a configuration fault at thetransmitting end.

The value NULL is received.


This will typically be due to a server layer fault,an unequipped VC signal or because the accep-tance criterion (16 bytes repetitively received) isnot met.

Value Description

Value Description

SDH The client signal is an SDH signal.SONET The client signal is a SONET signal.

Value Description

1E-5, 1E-6, 1E-7, 1E-8,

1E-9, 1E-10If, on average, one bit error is found in 105, 106,107, 108, 109, 1010bits, respectively, the monitoredsignal is considered degraded and the NE will

generate aDegraded signal

alarm.

Value Description

Monitored Alarms at this monitoring point can be read inthe NEs Current Problem Listwindow. If eventreporting has been enabled for the NE, thesealarms will also be able to be read in the AlarmsViewwindow of the Tellabs 6300 manager.


15/92MA326 Rev. A1 15



1.6 Deleting a Non-intrusive Monitoring Point

To delete a non-intrusive

monitoring point

This procedure describes how you delete a non-intrusive monitoring point.The only way to stop non-intrusive monitoring is to delete the non-intrusivemonitoring point.

Not monitored Alarms will neither be able to be read in the NEsCurrent Problem Listwindow, nor in the Alarms

View window of the Tellabs 6300 manager even ifevent reporting has been enabled for the NE.

Value Description

Step Action



The Ports:field of the Non-intrusive Monitoring (NIM) window showsthe ports for the NE in a tree structure. The ports available for mon-itoring are dependent on the modules installed in the NE (see Theports available for monitoring on page 8).



16/9216 MA326 Rev. A1



2 Select the port where the non-intrusive monitoring point, you wishto delete, is located.

The port is highlighted and the Incoming Signalgroup box displaysattribute values of the selected port.


3 Click on the Delete NIMbutton in the Incoming Signalgroup box.

Note: If performance monitoring is enabled for the port then awarning message will appear asking you to confirm the deletion.Click Yesif you are prepared to lose existing performance data.

The non-intrusive monitoring point is deleted and the arrow along-side the selected port in the Ports:field is removed. The attributesassociated with the non-intrusive monitoring point are also re-moved from the Incoming Signalgroup box.

4 Repeat steps 2and 3for all the non-intrusively monitored ports thatyou want to deactivate.

5 Click OK.

The Non-intrusive Monitoring (NIM)window closes.

Step Action
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-


17/92MA326 Rev. A1 17



1.7 Viewing/Editing the Configuration of a Non-intrusiveMonitoring Point

To view/edit the

configuration of a non-

intrusive monitoring point

This procedure describes how you view/edit the configuration of a non-intru-sive monitoring point.

Step Action



The Ports:field of the Non-intrusive Monitoring (NIM) window shows

the ports for the NE in a tree structure. The ports available for mon-itoring are dependent on the modules installed in the NE (see Theports available for monitoring on page 8).


Note: Ports with non-intrusive monitoring already created are indi-cated by an arrow.


18/9218 MA326 Rev. A1



2 Select the port containing the non-intrusive monitoring point thatyou wish to view or change the configuration of.

The port is highlighted and the Incoming Signalgroup box displaysattribute values of the selected port.


3 Assign values to the attributes and select/deselect the check box.See 1.5 Attributes in the Non-intrusive Monitoring (NIM) Windowon page 12.

Note: If you selected a single port in Step 2, the attribute setting will

apply to the single port. If you selected several ports, the attributesetting will apply to all the ports.

4 Repeat Steps 2and 3until you have edited the attributes for all thenon-intrusive monitoring points of interest.

5 Click OK.

All changes are updated in the NE and the window closes.

Step Action


19/92MA326 Rev. A1 19

Tellabs 6300Network Manager 2 Testing a Tellabs 7200 System Network Element


2 Testing a Tellabs 7200 System Network Element

Handling lasers You can configure an NE so that faults which may arise on individual lasersare handled automatically or manually. You can perform tests on a laser andyou also have the possibility of switching individual lasers on or off manually.The following topics are described:

2.1 Safety Precautions on page 19

2.2 Automatic Power Shutdown Safety Feature on page 22

2.3 Activating Tellabs 7200 System Lasers after an Automatic Power Shut-down on page 23

2.4 Description of a Laser Test Process on page 23

2.5 The Optical Ports Window on page 24

2.6 Shutting Down a Laser Automatically on page 24

2.7 Restarting a Laser Manually on page 25

2.8 Testing a Laser on page 27

2.9 Forcing a Laser to be On and Remain On on page 28

2.10 Forcing a Laser to be Switched Off and Remain Off on page 29

2.11 Activating a Laser that has been Forced Off on page 30

2.12 Adjusting the Attenuator on page 30

2.13 Setting the Decision Threshold on page 31

2.14 Setting the Output Power Offset on page 32

2.15 Setting the Output Channel Power on page 33 2.16 Attributes in the Optical Ports Window on page 34

2.17 Viewing and/or Changing the Laser Power-level Thresholds onpage 37.

2.1 Safety Precautions

Safety classification The Tellabs 7200 system is classified as a Class 3A laser product in accordancewith IEC 825, i.e. exposure to hazardous laser radiation is impossible duringnormal operation and maintenance. When the system has been installed, thelaser radiation is effectively enclosed in the optical fiber path between opticalmodules at each end.

The applied lasers are 980, 1310, 1480 and 1550 nm semiconductor lasers. Asseparate components these lasers are classified as Class 1 (1310 and 1550 nm)or Class 3B (980 and 1480 nm), however when built into the modules and con-nected into WDM systems, the Tellabs 7200 system is a Class 3A system.

Tellabs 7200 system equipment is configured per default, so that in case of aninterruption of the optical fiber trail by accident (e.g. cable rupture) an auto-matic safety mechanism will result in a periodic shutdown of the transmitterlaser. Hence, the laser radiation from any fiber end is restricted to a 2 secondperiod, which is repeated every 70 seconds.

Exposure to laser radiation risked during service or installation can be hazard-ous in case of double fault conditions.


20/9220 MA326 Rev. A1



IEC 825 classification

limits

The following table shows the IEC 825 classification limits of optical power ra-diated from single mode fiber ends.

Classification Power at 1550 nm

Class 1 Regarded as safe for all nor-mal viewing conditions(viewing time less than 100seconds).

up to +10 dBm

Class 3A Regarded as safe for casual di-rect viewing, but unsafe whenviewed with viewing aids.

+10 to +17 dBm

Class 3B Direct intrabeam viewing ishazardous.

+17 to +27 dBm


21/92MA326 Rev. A1 21



Laser warning The illustration describes laser safety rules.


22/9222 MA326 Rev. A1



2.2 Automatic Power Shutdown Safety Feature

Automatic power

shutdown safety featureof lasers

For eye-safety reasons, lasers in Tellabs 7200 system TRP-tx and TRP-rx mod-ules can be configured to shut down automatically if, and when, the size of theinput signal to the Tellabs 7200 system module falls below a certain pre-con-figured loss of signal(LOS) threshold which is pre-set in the module.

How the automatic

power shutdown safetyfeature functions

The process that causes lasers to shut down automatically, is illustrated by theexample of a broken optical path between the network element that functionsas an in-line amplifier (ILA) and the network element acting as a multiplexer(MDX).

Stage Description

1 The optical path between the ILA and the input to the multiplexer(MDX) at Site B is broken.

2 No input signal will be received at B.

3 This will generate automatically shutdown of the correspondinglaser transmitter in the forward direction (that is, the laser at C).

4 The lack of a signal at D will cause the Tellabs 6330 node terminalmultiplexer to generate a Loss of signal(LOS) alarm. This alarmwill automatically shut down all the laser transmitters in the Tel-labs 6330 node network element.

5 This means that no optical signal will be sent by the laser transmit-ter E.

6 Therefore no input signal will be received at input port F of theMDX at Site B.

7 This will automatically shut down the corresponding laser trans-mitter in the forward direction (that is, the laser at G).

8 This means that no optical signal will be sent by the laser transmit-ter at G.

9 Therefore no input signal will be received at input port H of thenetwork element functioning as an ILA.

10 This will automatically shut down the corresponding laser trans-mitter in the forward direction (that is, the laser at I), and so on un-til all the lasers have shut down.


23/92


24/9224 MA326 Rev. A1



2.5 The Optical Ports Window

The window where you

configure the lasers

You can see a representation of the optical ports in the Optical Portswindow.It is in this window that you configure the lasers for each port. The window isopened by selecting the menu item Operation and TestOptical Ports...in thepop-up menu of the NE matrix icon.

2.6 Shutting Down a Laser Automatically

Default setting of

automatic power

shutdown attribute

During production, lasers in relevant Tellabs 7200 system modules (TRP-tx(2P), TRP-rx (2P), TRP-bd (4P) WDM side, TRP-bd (4P) Client side, MA-OFA(4P) and OFA (2P) modules) are configured to shut down automatically whena loss of signal is detected on the input port. In addition TRP-bd (4P) modulesare configured to shut down automatically when a loss of frame is detected.The setting of the Laser Control attribute must be Normal for TRP modules andAutomaticfor OFA modules. Normalrespectively Automaticmeans that the au-tomatic power shutdown (APSD) feature of the laser is enabled. The value ofthis attribute can be viewed and set in the Optical Ports window in the LaserControl drop-down list.

How does the laser

become active again

after a power shutdown?

After a laser has shut down automatically, it does not try to start itself upagain. However, it will become active again as soon as it receives an input sig-nal which is as great, or greater than the loss of signal alarm limit (see2.3 Activating Tellabs 7200 System Lasers after an Automatic Power Shut-down on page 23).

5 A signal will be sent to F. The signal received at F will be largeenough to allow the laser at G to be active again and send the sig-

nal on to H, and so on, until all the relevant lasers in the closed net-work are active again.

Stage Description


25/92MA326 Rev. A1 25



To configure a laser to

shut down automatically

This procedure describes how you configure a laser to shut down automati-cally if, and when, the size of the input signal to it falls below the loss of signalalarm limit.

Warning: Read 2.1 Safety Precautions on page 19before performing this pro-cedure.

2.7 Restarting a Laser Manually

To manually restart a

laser

A laser that has been automatically shut down can be restarted manually. Forsafety reasons, lasers do not automatically try to restart themselves after anautomatic power shutdown. They can however be used to perform a test

Step Action

1 Select Operation and TestOptical Ports...in the pop-up menu ofthe NE matrix icon.

The Optical Portswindow appears.

2 In the Ports:field, select the module where the laser of interest is lo-cated.

The module is highlighted, and its attributes are shown in the fieldsin the top of the window.

3 Read the lasers mode of operation in the Laser Control:field. If you have selected a TRP module and the lasers mode of oper-

ation is not Normal, open the Laser Control:drop-down list, andselect Normal.

If you have selected an OFA module and the lasers mode of op-eration is not Automatic, open the Laser Control:drop-down list,and select Automatic.

4 Click OK.

The mode of operation of the laser is changed in the NEs databaseand the window closes.


26/9226 MA326 Rev. A1



when the operator is sure that nobody is likely to be exposed to the laser inquestion. The procedure is as follows.


Step Action



2 In the Ports:field, click on the module in question.

The module is highlighted, and its attributes are shown in the fieldsin the top of the window.

When the laser at an optical port has been automatically shut down(see 2.2 Automatic Power Shutdown Safety Feature on page 22)

its Laser Status attribute will be Off, and its Laser Control at-tribute will be Normalif it is a TRP module

its Laser Control attribute will be Automaticif it is an OFA mod-ule.

3 Click on the relevant test button (either the 9-sec testor the 90-sectestbutton).

Note: The length of the optical path will determine the duration ofthe laser pulse chosen to test the optical path.

A laser pulse (of either 9 seconds or 90 seconds duration) is sent outby the laser transmitter at the output port in question.

If the optical path is intact, the input signal to all Tellabs 7200system modules will be above the lower-high threshold level,and therefore the laser transmitters at the modules output portswill become active and send the signal on to the next mod-ule.The laser will remain active until the input signal falls belowthe input ports lower-low threshold power-level.

If the optical path is not intact, the lasers will not be activated.

Note: 3 seconds after the test starts, the Laser Statusattribute of aTRP module is updated. It should change to show In test. If it doesnot, you can click on the Refreshbutton. If the test has started, thestatus should change to In test.

4 Check the network for additional faults in the optical path.


27/92MA326 Rev. A1 27



2.8 Testing a Laser

To test a laser This procedure describes how you test the laser(s) for a specific module of anNE. This procedure assumes that the automatic power shutdown feature is ac-tivated (see Default setting of automatic power shutdown attribute on page24) or that the lasers have been forced off (see 2.10 Forcing a Laser to beSwitched Off and Remain Off on page 29).


5 Repeat Steps 1to 4until the optical path is intact and the Tellabs7200 system lasers are activated.

Step Action

Step Action



2 Select the module of interest in the Ports:field

The module is highlighted and its attributes are shown in the fieldsin the top of the window.

3 Click on the 90-sec testbutton.

The laser is restarted for a period of 90 seconds in which you canperform laser tests.
http://-/?-http://-/?-http://-/?-http://-/?-


28/9228 MA326 Rev. A1



2.9 Forcing a Laser to be On and Remain On

To force a laser

transmitter on a TRP

module to remain on

This procedure describes how to force a particular laser transmitter on a TRPmodule to be on and remain on even if the input signal falls below a certainlower-low threshold which is configured as one of the threshold crossingalarm limits (see 3.6 Enabling/Disabling Laser Power-level ThresholdAlarms on page 50).

Warning: This procedure should only be necessary during installation andconfiguration of your Tellabs 7200 system. For safety reasons, we

strongly advise that you do not force laser transmitters to be on un-less you are very sure that nobody is likely to be exposed to the laserwhile it is on. Read 2.1 Safety Precautions on page 19before per-forming this procedure.

4 Click OK.

The Optical Portswindow is closed.

Step Action

Step Action



2 In the Ports:field, select the TRP module where the laser of interestis located.

The module is highlighted and its attributes appear in the fields inthe top of the window.


29/92MA326 Rev. A1 29



2.10 Forcing a Laser to be Switched Off and Remain Off

To force a laser

transmitter on a module

to switch off

This procedure describes how to force a specific laser to be switched off andremain off.


3 Read the lasers mode of operation in the Laser Control:field.

Normal: indicates that the automatic power shutdown feature ofthe laser is enabled.

Forced Off: indicates that the laser has been forced off (see2.10 Forcing a Laser to be Switched Off and Remain Off onpage 29).

Forced Active: indicates that the laser will remain active underall circumstances - in other words, that its automatic powershutdown feature is disabled.

Note: Please read the warning given in the introduction to thisprocedure.

4 If the lasers mode of operation is not Forced Active, open the Laser

Control:drop-down list, and select Forced Active.The mode of operation of the laser is shown as Forced Activein theLaser Control:field.

5 Click Apply.

The mode of operation of the laser is changed to Forced Activeinthe NE, and the Laser Statusattribute should change to read Active.

6 Click OK.

The Optical Portswindow closes.

Step Action

Step Action




30/9230 MA326 Rev. A1



2.11 Activating a Laser that has been Forced Off

Activating a laser that

has been forced off

It is possible to switch off a particular laser transmitter. In this state, the laserwill remain off until both of the following conditions are met:

Its automatic power shutdown feature is enabled (see 2.2 AutomaticPower Shutdown Safety Feature on page 22)

It is activated in one of the ways discussed in 2.3 Activating Tellabs 7200System Lasers after an Automatic Power Shutdown on page 23.

2.12 Adjusting the Attenuator

Adjusting attenuators It is possible to adjust attenuators on OFA (2P) and MA-OFA (4P) modules.When performing the procedure to adjust an attenuator it causes the attenua-

tor to adjust to the actual link loss.

2 In the Ports:field, select the module where the laser of interest is lo-cated.


3 Open the Laser Control:drop-down list, and select:

Forced Offif you have selected a TRP module in Step 2

Shutdownif you have selected an OFA module in Step 2.

The mode of operation of the laser is shown in the Laser Control:field.

4 Click Apply.

The mode of operation of the laser is changed in the NEs database.

If you have selected a TRP module the Laser Statusattribute shouldchange to read Off.

5 Click OK.

Note: The laser in question will remain off until it meets the condi-tions described in 2.11 Activating a Laser that has been Forced Offon page 30.

Step Action


31/92MA326 Rev. A1 31



To adjust the

attentuators

This procedure describes how to adjust the attenuators.

2.13 Setting the Decision Threshold

The decision threshold For TRP-tx (2P) and TRP-rx (2P) modules as well as for the WDM input inter-face on TRP-bd (4P) modules it is possible to set the amplitude threshold fordetection of the bit value 1.

Warning: This facility is not to be used under normal circumstances, but pri-

marily when adjusting the equipment during installation.

Step Action



2 In the Ports:field, select the OFA (2P) or MA-OFA (4P) module ofinterest.

The module is highlighted and its attributes appear in the fields inthe top of the window. The text becomes visible on the Att. Adjustbutton.

3 Click on the Att. Adjustbutton.

The attenuator of the selected module will be adjusted to the actuallink loss.

4 Click OK.

The Optical Portswindow is closed.


32/9232 MA326 Rev. A1



To set the decision

threshold

This procedure describes how to set the threshold for detecting the bit value 1.

2.14 Setting the Output Power Offset

Output power offset of

transponders

The output power offset of the modules TRP-tx (2P) and TRP-bd (4P) WDMside can be adjusted within specific limits.

Warning: This facility is not to be used under normal circumstances, but pri-marily when adjusting the equipment during installation.

Step Action



2 In the Ports:field, select the TRP module of interest.


3 Open the Decision Threshold (%):drop-down list, and select a val-ue, see 2.16 Attributes in the Optical Ports Window on page 34.

4 Click OK.

The selected value will be applied as amplitude threshold for decid-

ing when to interpret a received signal as the bit value 1.

Note: If for a particular module with a given configuration it is notpossible to set the decision threshold, an alarm will be generated.


33/92MA326 Rev. A1 33



To set the output power

offset

This procedure describes how to set the output power offset of the transpon-der modules.

2.15 Setting the Output Channel Power

Output channel power of

OFA modules

The output channel power of MA-OFA (4P) and OFA (2P) modules can be ad-justed within specific limits.

Warning: This facility is not to be used under normal circumstances, but pri-

marily when adjusting the equipment during installation.

Step Action



2 In the Ports:field, select the TRP module of interest (output poweroffset canonly be adjusted for TRP-tx (2P) and TRP-bd (4P) WDMside).


3 Select a value in the Output Power Offset (dBm):drop-down list. Thevalue can be specified in steps of 0.1.

4 Click OK.

The output power offset of the module will be adjusted to the spec-ified value.


34/9234 MA326 Rev. A1



To set the output channel

power

This procedure describes how to set the output channel power of MA-OFA(4P) and OFA (2P) modules.

2.16 Attributes in the Optical Ports Window

Optical Ports window

attributes

The attributes in the Optical Portswindow are listed and described here.

Channel Counter Source on page 34

Channels Present on page 35

Decision Threshold (%) on page 35

Laser Control on page 35

Laser Status on page 36

Output Channel Power (dBm) on page 37

Output Power Offset (dBm) on page 37

Port ID on page 37.

Channel Counter Source

Shows the channel counter source of OFA (2P) and MA-OFA (4P) modules.

See also Channels Present on page 35.

Step Action



2 In the Ports:field, select the OFA module of interest (output chan-nel power canonly be adjusted for MA-OFA (4P) and OFA (2P)modules).


3 Select a value in the Output Channel Power (dBm):drop-down list.The value can be specified in steps of 0.1.

4 Click OK.

The output channel power of the module will be adjusted to thespecified value.


35/92MA326 Rev. A1 35



This is a read-only attribute.

Channels Present

Shows the number of channels present on OFA (2P) and MA-OFA (4P) mod-ules. The output power of OFA (2P) and MA-OFA (4P) modules has to dependon the actual number of channels present in the signal. If one or more channelsvanish from the signal, the overall output power shall be reduced accordingly.Thus the number of channels is permanently monitored. Channel countingcan be performed by the module itself or by a dedicated Channel Count Mod-

ule (CCM), see also Channel Counter Source on page 34. A Loss of channelcountingalarm will be received, if the channel counting has stopped.


Decision Threshold (%)

Specifies the amplitude threshold for deciding whether to interpret the re-

ceived signal as the bit value 1.

For TRP-tx (2P) and TRP-rx (2P) modules the following values are used:

For TRP-bd (4P) modules the following values are used on the WDM input in-

terface:

Laser Control

Specifies whether the laser is to shut down automatically if a loss of signal is

detected at the input port of a module.

Value Description

No Counting The channel counting has stopped.

Internal An internal channel counter is used.

External An external channel counter is used.

Value Description

No Counting Implies that the channel counting has stopped.

0, 1, ..., 32 The number of channels.

Value Description

Auto A 50 % duty cycle is employed. This is the defaultvalue for TRP-tx (2P) modules.

0, 1, ..., 100 The specified integer value (in percent) is thethreshold for detecting the bit value 1. 47 % is thedefault value for TRP-rx (2P) modules.

Value Description

Auto 100 % is the threshold for detecting the bit value1.

0, 1, ..., 99 The specified integer value (in percent) is thethreshold for detecting the bit value 1.


36/9236 MA326 Rev. A1



For MA-OFA (4P) and OFA (2P) modules the following values are used:

For TRP-tx (2P), TRP-rx (2P) and TRP-bd (4P) modules the following valuesare used:

Laser Status

Shows the status of the laser on TRP-tx (2P), TRP-rx (2P) and TRP-bd (4P)modules.


Value Description

Automatic Indicates that the automatic power shutdownfeature of the laser is enabled.

Shutdown Indicates that the laser has been shut down.

Value Description

Normal Indicates that the automatic power shutdownfeature of the laser is enabled.

Forced Off Indicates that the laser has been forced off.

Forced Active Indicates that the laser will remain active underall circumstances - in other words, that its auto-matic power shut down feature is disabled.

Value Description

N/A Indicates that the laser status cannot be read be-cause its operational status is disabled (for exam-ple, because an expected module is not actuallyphysically present).

Off Either indicates that the laser has been forced off(the Laser Controlattribute will indicate this byshowing Forced Off), or that the module is not yetin operation (the Laser Controlattribute will indi-cate this by showing Normal).

Active Either indicates that the laser is operating correct-ly ( the Laser Controlattribute will indicate thisby showing Normal), or that the laser has beenforced to remain active (the Laser Controlat-tribute will indicate this by showing Forced Ac-tive).

In test Indicates that the laser is being tested (the LaserControlattribute will indicate this by showingNormalor Forced Off).


37/92MA326 Rev. A1 37



Output Channel Power (dBm)

Specifies the output channel power on OFA (2P) and MA-OFA (4P) modules.

Output Power Offset (dBm)

Specifies the output power offset of lasers on the WDM side of TRP-tx (2P) andTRP-bd (4P) modules.

Port ID

The rack ID, subrack ID, slot ID and module handling the laser.


2.17 Viewing and/or Changing the Laser Power-level Thresholds

To view and/or change

power-level thresholds of

OTS monitor points

There are four threshold crossing alarm power levels that can be assigned tosome optical transmission section (OTS) monitor points in a Tellabs 7200 sys-tem network element (these threshold power levels and their function are ex-

plained in 5.3 Monitoring Power Levels at Termination Points on page 68).This procedure describes how to view and/or change any of these thresholdlevels.

Value Description

-10, -9.9, ..., 5, ..., 30 Value of output channel power. Specified in stepsof 0.1 dBm.

Value Description

-10, -9.9, ..., 10 Value of output power offset. Specified in steps of0.1 dBm.

Step Action

1 Select PerformancePerformance Monitoring...in the pop-up menuof the NE matrix icon.

The Performance Monitoringwindow appears. The different parts ofthe Tellabs 7200 system that contain monitor points are shown inthe Monitor Points: field.


38/9238 MA326 Rev. A1



2 Click on the expand icon (+) alongside the OTS Monitor Pointsbox.

The rack, subrack and slot numbers (for example, 15/7/01) of themodules containing monitored termination points appear in thewindow.

3 Click on the expand icon (+) alongside the location of the modulecontaining the termination points of interest.

The ports at this location appear in the window.

4 Click on the expand icon (+) alongside the port of interest.

The measurements made at this port become visible, that is, Chan-nel Powerand Total Power.

5 Click on the expand icon (+) alongside the Channel Powertext if youwish to set the power-level thresholds for a single channel, oralongside the Total Powertext if you wish to set the power-levelthresholds for all channels.

The measurements made at this port become visible, that is, PowerLevel.

6 Select the Power Leveltext.

It is highlighted, and the text Thresholds...appears on the button inthe lower-right corner of the Monitor Points:field.

Step Action


39/92MA326 Rev. A1 39



7 Click on the Thresholds...button.

The Thresholds window appears.

The name of the NE, and the name and location of the monitorpoint in question, appears in the Monitor Point:field. The currentpower level at the monitor point in question can be seen in the Pow-er Level:field. The settings of the four power-level thresholds areshown in the fields Upper-high:, Upper-low:, Lower-high:and Lower-low:.

8 Enter the threshold level(s) you want in the relevant field(s).

9 Click OK.

The Thresholds window closes and the new threshold level is cop-ied to the NEs memory.

10 Click OK.

The Performance Monitoringwindow closes.

Step Action


40/9240 MA326 Rev. A1




41/92MA326 Rev. A1 41

Tellabs 6300Network Manager 3 Configuring Alarms


3 Configuring Alarms

Overview The following topics are available:

3.2 Configuring the Severity Level of and Destination for a Specific Alarmon page 41

3.3 Setting the Fault Persistency Attributes on page 43

3.4 Suppressing a Specific Alarm on page 44

3.5 Configuring Alarms Generated by Auxiliary Equipment on page 45

3.6 Enabling/Disabling Laser Power-level Threshold Alarms on page 50

3.7 Sending Alarms to a Specific Management Center on page 52.

3.1 Automatic Generation of Alarms by an NE

Self-monitoring in an NE An NE is capable of monitoring its own condition by automatically takingmeasurements at pre-defined monitoring points (managed objects) within it.It is programmed to generate an alarm if a measured value falls above/belowa pre-specified maximum/minimum value respectively, or it falls outside aspecified range of values. For example: the Degraded signal alarm is generatedif the bit-error threshold has been set to 1E-6 on a particular VC-4 terminationpoint, and a bit-error ratio >10-6is measured on the signal passing through it.

3.2 Configuring the Severity Level of and Destination for aSpecific Alarm

Default severity levels for

NE alarms

NE alarms have the following severity levels assigned by default:

None

Warning

Minor

Major

Critical

To see a specific alarms default severity, refer to 4 Tellabs 7200 SystemAlarms on page 55. You can change the alarms severity, see To configure a

specific alarm on page 42.

Alarms from auxiliary

equipment

The default severity of auxiliary alarms is None, and these alarms only exist ifthe user has configured them in connection with use of auxiliary equipmentattached to the NE.


42/9242 MA326 Rev. A1



Possible alarm

destinations for Major

and Critical alarms

Major and Critical alarms can be configured as rack alarms (RA) or centralalarms (CA) or as both.

A central alarm (CA) is sent to the outlet socket on the system connectionfield and AUX panel. A cable from this socket can then be used to send thealarms along to a central monitoring station.

A rack alarm (RA) is sent to the rack connection field LEDs (light emittingdiodes) of the NE.

To configure a specific

alarm

This procedure describes how you configure the severity level of and destina-tion for a specific alarm.

Step Action

1 Select EquipmentAlarm Configuration...in the pop-up menu ofthe NE matrix icon.

TheAlarm Configuration

window appears.

2 Select the relevant managed object class from the Managed ObjectClasses list.

The selected managed object class is highlighted, and the corre-sponding alarms and related information are shown in the lowerhalf of the window. For an overview of all managed object classesand corresponding alarms, refer to 4 Tellabs 7200 System Alarmson page 55.


43/92MA326 Rev. A1 43



3.3 Setting the Fault Persistency Attributes

What are the fault

persistency attributes?

The fault persistency attributes decide:

how long a fault needs to be detected before an alarm is generated and

shown in theCurrent Problem List

window. The attribute that governs thisperiod is called the Fault On Time.

how long a fault must be absent before the alarm is automatically clearedfrom the Current Problem Listwindow. The attribute that governs this pe-riod is called the Fault Off Time.

Default value of alarm

persistency attributes

The default value for both Fault On Timeand Fault Off Timeis 1 (one) second.

Which alarms can you

set the fault persistency

attributes for?

You can modify the fault persistency for transmission alarms. The value ofeach attribute is common for the whole alarm group.

3 Click on the alarm of interest.

It is highlighted, and details about the alarm appear in the Severity:,RA:, CA:, AUX Ports:and Text:boxes.

4 Configure the selected alarm:

a) Select the alarms severity from the Severity: drop-down list.

Note: If you do not want an alarm to be emitted, set the severityto None.

b) For Criticalor Majoralarms: set the alarm to be an RAand/or CAby clicking on the relevant check boxes.

c) Select which AUX ports the hardware will use to send the alarm

by clicking in the relevant AUX Ports:check boxes. Refer to3.5.1 Using Auxiliary Equipment on page 45.

5 Click OK.

The changes are saved in the NE, and the window closes.

Step Action


44/9244 MA326 Rev. A1



To set the fault

persistency attributes

This procedure describes how to set the fault persistency attributes.

3.4 Suppressing a Specific Alarm

To suppress a specific

alarm

This procedure describes how to suppress a specific alarm.

Step Action

1 Select EquipmentFault Persistency...in the pop-up menu of theNE matrix icon.

The Fault Persistencywindow appears.

The current Fault On Timeand Fault Off Timeare shown in the re-spective fields in the right side of the window.

2 Set the fault persistency attributes (see What are the fault persisten-cy attributes? on page 43):

a) Enter a period in seconds in the Fault On Time (seconds):field.

b) Enter a period in seconds in the Fault Off Time (seconds):field.

Legal values are periods in the range 0.1 and 25.5 seconds in incre-ments of 0.1 seconds. The default setting is 1.0 second for both at-tributes.

3 Click OK.

The changes are saved in the NEs memory, and the window closes.

Step Action

1 Select EquipmentAlarm Configuration...in the pop-up menu ofthe NE matrix icon.

The Alarm Configurationwindow appears.


45/92MA326 Rev. A1 45



3.5 Configuring Alarms Generated by Auxiliary Equipment

Purpose You can connect other equipment to the auxiliary ports of the NE. Any alarmsreceived from the equipment can be acted upon. The following is described:

3.5.1 Using Auxiliary Equipment on page 45

3.5.2 Configuring Alarms Generated by Auxiliary Equipment on page 49.

3.5.1 Using Auxiliary Equipment

Use of AUX ports Third-party (auxiliary) equipment can be connected to one of the auxiliary(AUX) ports of the network element. An auxiliary port can then be configuredin one of the following ways:

To create an environmental alarm.

To change the condition of the auxiliary equipment connected to it.

2 Select the relevant managed object class from the Managed ObjectClasses list.

The selected managed object class is highlighted, and the corre-sponding alarms and related information are shown in the lowerhalf of the window. For an overview of all managed object classesand corresponding alarms, refer to 4 Tellabs 7200 System Alarmson page 55.

3 Select the alarm you wish to suppress.

It is highlighted, and details about the alarm appear in the Severity:,RA:, CA:, AUX Ports: and Text:boxes.

4 Open the Severity:drop-down list and select None.

Note: Alarms that have a severity of Nonecannot produce alarms.

5 Click OK.

The changes are saved in the NEs memory, and the Alarm Configu-rationwindow closes.

Step Action


46/9246 MA326 Rev. A1



Two examples to

illustrate the use of AUX

ports

The figure in Connecting the auxiliary monitoring equipment to the Tellabs7200 systems AUX ports on page 47illustrates the following two examples:

Using the sensor on a cabinet door to create an environmental alarm:

An auxiliary port can be configured to measure its own polarity, and gen-erate a selected environmental alarm when its polarity is high or low.For example, suppose a sensor on a cabinet door is connected to AUX portno. 1. Suppose that AUX port no. 1s polarity is zero (low) when the dooron which the sensor is mounted is closed, but its polarity changes to a pos-itive value (that is, high) when the door is opened. You can configureAUX port no. 1 to generate the environmental alarm Enclosure door openwhen it measures a high polarity. The AUX port is configured accord-ingly (see 3.5.2 Configuring Alarms Generated by Auxiliary Equipmenton page 49).

Changing the condition of cooling fans connected to an auxiliary port:

The port can be configured to generate its own high or low polarity

when a specified alarm is generated by the NE. This polarity can cause thecondition of the attached auxiliary equipment to change. For example, sup-pose some cooling fans are installed in the same cabinet as the NE. Supposethey start automatically when the polarity of the AUX port connected tothem is low. You can configure the AUX port to produce its own lowpolarity when the already-configured Unit temperature too highalarm isgenerated by the NE. This will automatically start the cooling fan.


47/92MA326 Rev. A1 47



Connecting the auxiliary

monitoring equipment to

the Tellabs 7200

systems AUX ports

The figure illustrates two types of auxiliary equipment connected to the AUXports of the Tellabs 7200 system.

Demands on auxiliary

equipment

Auxiliary equipment must function according to the polarity of the port con-

nected to the NEs AUX port. This polarity is equipment specific. Refer to therelevant user manual of the equipment in question.

Setting the severity of an

AUX alarm

The severity of an environmental alarm generated at an AUX port must bechanged from None(default value) to another severity level (Criticalor Major)if you wish to send it to any destination (see Destination for an alarm on page48). The procedure for doing this is described in 3.2 Configuring the SeverityLevel of and Destination for a Specific Alarm on page 41.

Specifying destinations

for an alarm

The AUX port to which the auxiliary equipment is attached must be config-ured to send an alarm to a destination. The procedure for doing so is describedin 3.5.2 Configuring Alarms Generated by Auxiliary Equipment on page 49.


48/9248 MA326 Rev. A1



Destination for an alarm An alarm from auxiliary equipment can be sent to either or both of the follow-ing destinations:

to the central alarm outlet socket on the system connection field and AUXpanel. This is where Station Supervision Alarms are collected from allCMCC1 modules within a rack. A cable from this socket can then be usedto send these alarms along to a central monitoring station.

to the rack connection field LEDs of the NE .

Pin connections for

auxiliary alarms

The pin connections for auxiliary alarms are called EXT (external ports) in theTellabs 7200 system hardware manual, but they are called AUX ports in Tel-labs 6300 manager.

Relationship between

ports and pin

connections

The table shows the relationship between the pin connection numbers, the ex-ternal port (EXT) numbers and the AUX port numbers.

Pin No. Pin Name AUX Port No.

1 EXT 0 0

9 EXT 1 1

2 EXT 2 2

10 EXT 3 3

3 EXT 4 4

11 EXT 5 5

4 EXT 6 6

12 EXT 7 7

15 5 V -

8 GND(ground)

-


49/92MA326 Rev. A1 49



3.5.2 Configuring Alarms Generated by Auxiliary Equipment

To configure an alarm

generated by orchanging the condition of

auxiliary equipment

This procedure is explained with reference to the examples given in Two ex-

amples to illustrate the use of AUX ports on page 46.

Step Action

1 Select EquipmentAUX Ports...in the pop-up menu of the NE ma-trix icon.

The AUX Portswindow appears.

2 Click on the relevant port number in the list of ports shown in theupper part of the window.

The selected number appears in thePort:

field in the upper part ofthe window.

3 Open the Direction:drop-down list, and select either Inputor Out-put.

Inputindicates that it is the auxiliary equipment which is respon-sible for creating the required polarity at the selected port.

Outputindicates that it is a generated alarm that is responsiblefor creating the required polarity at the selected port.

4 In the list of ports shown in the lower part of the window, click onthe same port number you selected in Step 2.

The selected number appears in the Port:field in the lower part ofthe window.

5 Select a value for the relevant polarity in the lower part of the win-dow.

If you selected Inputas the value in the Direction:drop-down listin Step 3, then you must open the Input Polarity:drop-down listand select the relevant polarity.

If you selected Outputas the value in the Direction:drop-downlist in Step 3, then you must open the Output Polarity: drop-down list and select the relevant polarity.

The selected polarity value appears in the field.


50/9250 MA326 Rev. A1



3.6 Enabling/Disabling Laser Power-level Threshold Alarms

To enable/disable alarms

associated with power-

level thresholds

The Power too low and Power too high alarms that are discussed in5.3 Monitoring Power Levels at Termination Points on page 68can be en-abled or disabled. The procedure to do so follows.

6 If you selected Inputas the value in the Direction:drop-down list inStep 3, then you must select a text which describes the alarm condi-

tion. Otherwise (that is, if you selected Output), continue to the pro-cedure To configure a specific alarm on page 42.

To select an alarm condition text: Open the Input Alarm Text:drop-down list, and select the text that describes the condition which willcause the alarm to be generated.

7 Click OK.

The window closes and details about the new AUX ports configura-tion are saved in the NE.

Note: You have to configure the severity of the alarm to be eithermajor or critical if you want the alarm to be sent as a rack alarm or amanagement center alarm. See To configure a specific alarm on

page 42for a description of this procedure.

Step Action

Step Action

1 Select PerformancePerformance Monitoring...in the pop-up menu

of the NE matrix icon.The Performance Monitoringwindow appears showing differentparts of the Tellabs 7200 system NE that contain monitor points.

Note: The cross icon indicates that no measurement data is avail-able at this location.
http://-/?-http://-/?-


51/92MA326 Rev. A1 51



2 Click on the expand icon (+) alongside the OTS Monitor Pointsbox.

The rack, subrack and slot numbers (for example, 15/7/01) of themodules containing monitored termination points appear in thewindow.

3 Click on the expand icon (+) alongside the location of the modulecontaining the termination points of interest.

The ports at this location appear in the window.

4 Click on the expand icon (+) alongside the port of interest.

The measurements made at this port become visible, that is, Chan-nel Powerand Total Power.

5 Click on the expand icon (+) alongside the Channel Powertext if youwish to set the power-level thresholds for a single channel, oralongside the Total Powertext if you wish to set the power-levelthresholds for all channels.

The measurements made become visible, that is, Power Level.

6 Select the Power Leveltext.

It is highlighted, and the text Thresholds...appears on the button inthe lower-right corner of the Monitor Points:field.

Step Action


52/9252 MA326 Rev. A1



3.7 Sending Alarms to a Specific Management Center

Directing alarms to a

management center

You have to direct alarms generated by an NE to the management center ofyour choice dependent on which management center is responsible for whichpart of the network.

What is a management

center?

A management center is any computer, running Tellabs 6300 manager soft-ware, that is able to monitor/manage some of or all of the NEs in a telecom-

munications network.

7 Click on the Thresholds...button.

The Thresholds window appears.

8 Select the default value of the threshold power level in the Upper-high: field.

It is highlighted.

9 Enter the value you wish this threshold to have.

The new value replaces the highlighted value.

10 Repeat Steps 8and 9inclusive, for each of the threshold power lev-els.

Note: The size of the thresholds must be such that the following ap-plies: Lower-lowLower-highUpper-lowUpper-high.

11 Perform one of the following operations:

To enable the Power too highand Power too lowalarms in ques-tion, select the Enable Threshold Crossing Alarms:check box.

To disable the Power too highand Power too lowalarms in ques-tion, deselect the Enable Threshold Crossing Alarms:check box.

12 Click OK.

The changes made in the Thresholds window are saved in the NEsmemory, and the window closes.

13 Click Close.

The Performance Monitoring window closes.

Step Action


53/92MA326 Rev. A1 53



Number of management

centers in a network

Small networks can perhaps be monitored/managed by a single managementcenter. The computer must request all NEs in the network to send their alarms(events) to it. However, larger networks normally require more than one man-agement center, and each center is made responsible for monitoring only part

of the network (a limited number of NEs). In this case, each management com-puter must be configured to receive alarms only from those NEs it is respon-sible for monitoring/managing.


54/9254 MA326 Rev. A1




55/92MA326 Rev. A1 55

Tellabs 6300Network Manager 4 Tellabs 7200 System Alarms


4 Tellabs 7200 System Alarms

List of alarms from

managed object classes

This table lists all alarm-emitting managed object classes (MOCs) and their as-sociated alarms. It also lists the default values of severity level and alarm des-tination.

Managed

Object

Class

(MOC)

Alarm Text Severity

Alarm Destination

(default settings)

Rack

Alarm

(RA)

Enabled

Central

Alarm

(CA)

Enabled

AUX Air compressor failure None

Air conditioning failure NoneAir dryer failure None

Battery discharging None

Battery failure None

CCM loss of communica-tion

None

Commercial power failure None

Cooling fan failure None

DTMF EOW failure NoneEnclosure door open None

Engine failure None

Equipment cooling failure None

Equipment fan malfunction None

Explosive gas None

Fire None

Fire detector failure None

Flood None

Fuse failure None

Generator failure None

High humidity None

High temperature None

High wind None

Ice build up None


56/9256 MA326 Rev. A1



AUX Intrusion detection None

Loss of optical signal None

Low battery threshold None

Low cable pressure None

Low fuel None

Low humidity None

Low temperature None

Low water None

Power failure None

Pump failure None

Rectifier failure None

Rectifier high voltage None

Rectifier low voltage None

Smoke None

Toxic gas None

User defined 1 None

User defined 2 None

User defined 3 None

User defined 4 None

User defined 5 None

User defined 6 NoneUser defined 7 None

User defined 8 None

Ventilations system failure None

CMCC1 Unit sub type mismatch Major x x

EFD Storage capacity problem None

Laser Laser degraded Major x x

Loop back Loop back active Critical x x

Managed

Object

Class(MOC)

Alarm Text Severity

Alarm Destination

(default settings)

Rack

Alarm(RA)

Enabled

Central

Alarm(CA)

Enabled


57/92MA326 Rev. A1 57



MA-OFA Loss of channel counting Major x x

Output power out of range Warning

Power failure Major x x

Unit sub type mismatch Major x x

Module Unit main type mismatch None

OCH AIS None

Loss of retiming Critical x x

OCH (FEC) Degraded signal Major x x

Loss of frame Critical x x

OCH(WRP)

Degraded signal Major x x


Section trace mismatch Critical x x

OFA (2P) Loss of channel counting Major x x




OFA (4P) Power failure Major x x


OSC (2P) Power failure Major x x


OSC (4P) Power failure Major x xUnit sub type mismatch Major x x

OSC inputport

OSC link down Major x x

OSC Laser Laser degraded Major x x

OTS Loss of signal Critical x x

OTS Moni-tor Point

Power too high Major x x

Power too low Major x x

Managed

Object

Class(MOC)

Alarm Text Severity

Alarm Destination

(default settings)

Rack

Alarm(RA)

Enabled

Central

Alarm(CA)

Enabled


58/9258 MA326 Rev. A1



OutputPort

Output degraded Major x x

PSF Main power input supplyfailed

Major x x


Protection voltage failure Major x x

Unit sub type mismatch Major x xPump La-ser

Laser degraded Major x x

RS moni-tor point

Degraded signal Major x x


Section trace mismatch Critical x x

Slot Unit main type mismatch Critical x x

Unit missing Major x x

Subrack Unit sub type mismatch Major x x

TRP-BD(4P)



Unit temperature too high Critical x x

TRP-BD4P) inputport (Cli-ent)

Receiver overload Major x x

TRP-BD(4P) inputport(WDM)

Decision threshold not sup-ported

Warning


TRP-BD(4P) out-put port(Client)


TRP-BD(4P) out-put port(WDM)

Optical frequency offsetout of range

Warning



Managed

Object

Class(MOC)

Alarm Text Severity

Alarm Destination

(default settings)

Rack

Alarm(RA)

Enabled

Central

Alarm(CA)

Enabled


59/92MA326 Rev. A1 59



TRP-rx (2P) FEC FIFO error Major x x




TRP-rx (2P)input port


Warning


TRP-rx (2P)output port


TRP-tx (2P) Power failure Major x x



TRP-tx (2P)input port


Warning


TRP-tx (2P)output port

Optical frequency offsetout of range

Warning



Managed

Object

Class(MOC)

Alarm Text Severity

Alarm Destination

(default settings)

Rack

Alarm(RA)

Enabled

Central

Alarm(CA)

Enabled


60/9260 MA326 Rev. A1




61/92MA326 Rev. A1 61

Tellabs 6300Network Manager 5 Configuring and Viewing Performance Data


5 Configuring and Viewing Performance Data

What is performance

data?

The performance monitoring function lets you examine the performance ofthe traffic terminated in a specific NE. The data, in the form of counter values(see Overview of monitor points collecting historical data on page 65) orgauge values (for example, optical power level, laser bias), is collected in theNE and can be displayed either in list form or as a graph. Configuring andviewing performance data is described in:

5.1 Monitor Points, Data Registers and Event Counters on page 61

5.2 Viewing the Non-historical Performance Data on page 66

5.3 Monitoring Power Levels at Termination Points on page 68

5.4 Specifying Which Historical Performance Data to Display on page 72

5.5 Viewing the Historical Performance Data on page 74.

Performance data can be used to find out in which sections a fault exists, tolocate sources of intermittent errors and/or to determine the quality of ser-vice.

5.1 Monitor Points, Data Registers and Event Counters

Monitor points A monitor point is a termination point which is capable of providing perfor-mance information. Performance monitoring is always active for monitorpoints; you do not need to enable it specifically. In Tellabs 7200 system theperformance data collected are divided into two distinct groups since somedata supports historical information and some do not. The two kinds of data

can be viewed in two separate windows. The data registers and the countersmeasured are described in

5.1.1 Non-historical Performance Data on page 61

5.1.2 Historical Performance Data on page 64.

5.1.1 Non-historical Performance Data

Performance data in the

Performance Monitoring

window

Lasers in TRP and OSC modules, as well as pump lasers are automaticallymonitored for performance purposes in the Tellabs 7200 system. Power levelof lasers at source and sink termination points on each optical transmissionsection is also automatically monitored in Tellabs 7200 system NEs (see

5.3 Monitoring Power Levels at Termination Points on page 68). For modulessupporting forward error correction (FEC), the number of block errors and anestimated bit error rate are monitored. The performance tests are always per-formed, that is, you cannot disable them. You can view these measurementsin the Performance Monitoringwindow.


62/9262 MA326 Rev. A1



Overview of monitor

points collecting non-

historical data

The table lists available monitor points on different modules and the measure-ments made on these monitor points.

Monitor Point Module Type Port Name Measurement

OTS MonitorPoints

OFA (4P) WestOut,WestIn, EastOut,EastIn

Power Level

OFA (2P) In, Out

MA-OFA (4P) In, Out, MA-In,MA-Out

TRP-tx (2P),TRP-rx (2P)

In, Out

TRP-bd (4P) ClientIn,

ClientOut,WDMIn,WDMOut

OCH MonitorPoints

TRP-rx (2P) In Block Errors

Estimated Bit Er-ror Rate

Unreliable Per-formance Data

TRP-bd (4P) WDMIn Block Errors

Estimated Bit Er-

ror Rate

Unreliable Per-formance Data

Percentage ofBlock Errors

TRP - Transpon-der Lasers

TRP-tx (2P),TRP-rx (2P)

Out Laser Modula-tion Current (%)

Laser Bias Cur-rent (%)

Laser Tempera-ture Deviation(C)

TRP-bd (4P) ClientOut,WDMOut

Laser Modula-tion Current (%)




63/92MA326 Rev. A1 63



Power level

measurements on the

OTS monitor points

On the OTS monitor points the power levels are measured per channel and asa total power level.

Names of measurements

used in the Performance

Monitoring window

In the Performance Monitoringwindow the measurements mentioned in thetable above can be found under the following names:

OSC - OpticalSupervisory

Channel

OSC (4P),OSC (2P)

OSC Laser Power Level


Input PowerLevel (dBm)

Pump Lasers OFA (4P) WestOut,WestIn, EastOut,EastIn

Power Level



OFA (2P) In, Out Power Level



MA-OFA (4P) In, Out, MA-In,MA-Out

Power Level



Monitor Point Module Type Port Name Measurement

MeasurementIn the Performance Monitoring win-

dow called

Block Errors BE ()

Estimated Bit Error Rate EBER ()

Percentage of Block Errors PBEO (%)

Unreliable Performance Data UPD ()

Power Level Power (dBm)

Laser Bias Current (%) Bias (%)

Laser Modulation Current (%) Modulation (%)


64/9264 MA326 Rev. A1



Block errors are given as number of errors. Unreliable performance data areshown as Y (for Yes) and N (for No).

5.1.2 Historical Performance Data

Performance data in the

Performance Monitoring

- Bit Error Counters

window

Non-intrusive monitoring of client signals is supported by TRP modules. Theperformance measurements on non-intrusive monitoring points are countingvarious errors and accumulating them over fixed periods of time. You canview these measurements in the Performance Monitoring - Bit Error Counterswindow.

Data registers in an NE Each monitor point has the following data registers:

15-minute registers that accumulate performance events over fixed 15-minute periods

24-hour r

Tellabs OSN

Documents

Transcript of Tellabs OSN