Procedure 5-48: Clear "inc. data type mismatch" alarm

- Overview

This procedure is used to clear an inc. data type mismatch alarm.

- Before you begin

Prior to performing this procedure:

  1. Refer to Before you begin and Required equipment in this chapter.

  2. Refer to Electrostatic discharge in Chapter 1, Safety.

Steps

Complete the following steps to clear an inc. data type mismatch alarm.

 
1

From the WaveStar® CIT System View, click the Alarm List button and locate the inc. data type mismatch alarm in the resulting alarm list.


2

Determine the alarm level(s) for the active inc. data type mismatch alarm(s). Clear the alarms in order of severity.


3

Refer to the Probable Cause column in the alarm list, determine the affected VCG, and note the corresponding AID and the type of circuit pack.

Note:

An LNW73/73C VCG must be connected through the network to another Fiber Channel VCG.

An Ethernet LNW63, LNW66, LNW67, LNW68 VCG must be connected through the network to another Ethernet VCG.


4

Using circuit layouts and/or office records, identify the far-end network element for the specified VCG.


5

Use the WaveStar® CIT to log in to the required far-end Alcatel-Lucent 1665 DMX for the specified VCG.

Reference:

Procedure 6-2: Connect Personal Computer (PC) and establish WaveStar® CIT session


6

From the System View, select Reports → Equipment Lists → Pack. Select Shelf and click Select.

Result:

The Circuit Pack List appears.


7

Using the Circuit Pack List and office records, determine if the far-end pack is the same type (Ethernet, Fibre Channel) as the near end circuit pack.


8

If the far-end Alcatel-Lucent 1665 DMX...

Then...

Is the same type of circuit pack as the near end,

Proceed to Step 11.

Is a different type of circuit pack than the near end,

Decide which circuit pack should be replaced so the types match. Change one of the circuit packs to match the other end. Continue with the next step.


9

From the System View, click the Alarm List button and click Refresh.


10

Is the inc. data type mismatch alarm still present?

If...

Then...

Yes

Continue the next step.

No

STOP! End of Procedure.


11

At the near end, select View → Cross-Connections. Select the required circuit pack and click Select to obtain a list of cross-connections. Observe the provisioned cross-connections for the required circuit pack and verify that the port is connected through the network to a circuit pack of the same type.

Note:

The cross-connections at the local node may be correct; the incorrect cross-connection could be at any node in the transmission path.


12

Select Configuration → Cross-Connections to access the Cross-Connection Wizard and make the required cross-connections changes to/from the circuit pack.


13

From the System View, click the Alarm List button and click Refresh.


14

Is the inc. data type mismatch alarm still present?

If...

Then...

Yes

Continue the next step.

No

STOP! End of Procedure.


15

From the System View, select View → Equipment, expand the group (GRP), highlight the alarmed port, and then click Select.

Result:

The View Equipment window opens.


16

If the affected port is...

Then...

Connected to test equipment,

Proceed to Step 17.

In service,

Proceed to Step 18.


17

If the port is connected to test equipment, you have the following options to clear the alarm.

  1. Align the test set signal characteristics with those of the port.

  2. Disconnect the test set, or

  3. Ignore the alarm until the test set is disconnected, (recommended method), or


18

In the Transmission section of the Configure Equipment window, change the provisioned state of the VCG's GFP Frame Check Sequence (ENABLE or DISABLE) to match the far end port and click Apply.

Result:

A warning message appears asking you to confirm executing this command. Click Yes. Continue with Step 19.


19

Click Close on the Configure Equipment window.


20

From the System View, click the Alarm List button and click Refresh.


21

Is the inc. data type mismatch alarm still present?

If...

Then...

Yes

Contact your next level of support.

No

STOP! End of Procedure.


End of steps

November 2011Copyright © 2011 Alcatel-Lucent. All rights reserved.