Header Only - DO NOT REMOVE - Extreme Networks

DFE with continual 'FTM2 received link interrupts' Error Messages


Userlevel 3
Article ID: 7298

Products
DFE

Symptoms
Error messages
"FTM2 received link interrupts"
"The board in slot of the chassis has been removed."
"The board in slot of the chassis is operational."

Cause
An example sequence of Fault Log "link interrupts" error messages, as extracted per the procedure in 5101, is shown here:

1050 2005-11-10,23:02:52.00 System Init 04.21.11
DFE-P software system has successfully completed initialization
and is entering its normal operational mode.

1051 2005-11-11,06:24:15.00 Syslog Message 04.21.11
<3>TimesSqr[1.tTsPoll](Remote slot 5, BP1) FTM2 BP2 received 0x00000003
link interrupts (value = 0x0000001f, prior = 0x0000001c)

1052 2005-11-11,07:33:07.00 Syslog Message 04.21.11
<3>TimesSqr[1.tTsPoll](Remote slot 3, BP2) FTM2 BP1 received 0x00000003
link interrupts (value = 0x00000074, prior = 0x00000071)

. . .

2043 2005-11-10,23:02:51.00 System Init 04.21.11
DFE-P software system has successfully completed initialization
and is entering its normal operational mode.

2044 2005-11-11,08:51:08.00 Syslog Message 04.21.11
<3>TimesSqr[2.tTsPoll](Remote slot 1, BP4) FTM2 BP2 received 0x00000003
link interrupts (value = 0x0000000c, prior = 0x00000009)

2045 2005-11-11,11:31:55.00 Syslog Message 04.21.11
<3>TimesSqr[2.tTsPoll](Remote slot 1, BP4) FTM2 BP2 received 0x00000003
link interrupts (value = 0x0000000f, prior = 0x0000000c)

. . .

3043 2005-11-10,23:02:53.00 System Init 04.21.11
DFE-P software system has successfully completed initialization
and is entering its normal operational mode.

3044 2005-11-11,03:44:53.00 Syslog Message 04.21.11
<3>TimesSqr[3.tTsPoll](Remote slot 1, BP1) FTM2 BP2 received 0x00000003
link interrupts (value = 0x0000004b, prior = 0x00000048)

3045 2005-11-11,05:25:59.00 Syslog Message 04.21.11
<3>TimesSqr[3.tTsPoll](Remote slot 1, BP1) FTM2 BP2 received 0x00000003
link interrupts (value = 0x00000062, prior = 0x0000005f)

3046 2005-11-11,07:33:07.00 Syslog Message 04.21.11
<3>TimesSqr[3.tTsPoll](Remote slot 1, BP1) FTM2 BP2 received 0x00000003
link interrupts (value = 0x00000079, prior = 0x00000076)

3047 2005-11-11,08:24:15.00 Syslog Message 04.21.11
<3>TimesSqr[3.tTsPoll](Remote slot 1, BP1) FTM2 BP2 received 0x00000003
link interrupts (value = 0x00000083, prior = 0x00000080)

. . .

4050 2005-11-10,23:02:51.00 System Init 04.21.11
DFE-P software system has successfully completed initialization
and is entering its normal operational mode.

4051 2005-11-11,04:02:21.00 Syslog Message 04.21.11
<3>TimesSqr[4.tTsPoll](Remote slot 1, BP3) FTM2 BP1 received 0x00000003
link interrupts (value = 0x0000000e, prior = 0x0000000b)

. . .

5055 2005-11-10,23:02:52.00 System Init 04.21.11
DFE-P software system has successfully completed initialization
and is entering its normal operational mode.

5056 2005-11-11,06:24:15.00 Syslog Message 04.21.11
<3>TimesSqr[5.tTsPoll](Remote slot 1, BP2) FTM2 BP1 received 0x00000003
link interrupts (value = 0x00000018, prior = 0x00000015)[/code]
This condition may be accompanied by a series of repetitive Syslog error messages, for example:

<165>Nov 11 14:45:29 10.20.29.172 System[5]The board in slot 1 of the chassis h
as been removed.
<165>Nov 11 14:46:15 10.10.29.172 System[5]The board in slot 1 of the chassis i
s operational. [/code]
Solution
Focus on the slot which is the common factor in the error messages. In this example; slot 1 issued Fault Log messages (sequence numbers 1xxx), was referenced as the "Remote slot" by Fault Log messages of the modules in the other slots, and was directly referenced as the unstable slot in the Syslog messages.

Using the procedures as explained in 5036, remove and firmly reseat the module in that slot. If that doesn't resolve the symptoms, contact Enterasys Networks Technical Services for further assistance.

0 replies

Be the first to reply!

Reply