[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 7.286::fddi

Title:FDDI - The Next Generation
Moderator:NETCAD::STEFANI
Created:Thu Apr 27 1989
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2259
Total number of notes:8590

1543.0. "Mgmnt Module LED can't be turned OFF" by STKAI1::EROSEN () Thu Dec 29 1994 07:44

Hi!

We are in great need for explanation to the following. We don't 
have at the moment any expertise available in the CSC to handle 
the problem described below at our customer here in Sweden.

All the help is VERY appreciated.

/Ebbe Rosen

===================

Problem with FDDI concentrator. It can't be reached via DECmcc.
It reports an error when the test plug is installed. But it anyway
seems like 3 systems works through this concentrator.

Power OFF/ON did clear all problem, BUT it left the "management 
board broken LED" turned on. It is not possible to get that LED to 
turn OFF.
We have tried to swap "mgmnt board, port board and backplane" 
without any change. The mgmnt board broken LED is still lit and 
the concentrator works just fine.

We have not introduced any change tho the concentrator (all the 
boards in the concentrator are original), it was OK before power 
OFF/ON.

When you examine the status of the bridge it says OPTICAL BYPASS 
BROKEN. We do not use optical bypass.

It also says:   ROM: 1.0.0
                SW : 3.4
                FRU REV P� mgmnt board and mother board :  1
                FRU STATE = working
T.RTitleUserPersonal
Name
DateLines
1543.1Response from EngineeringSTKAI1::EROSENFri Dec 30 1994 04:3165
I received following the following mail and response from Mike Johnson.
We will work this issue through e-mail with Mike and his team members.

/Ebbe


From:	NPSS::JOHNSON "Mike - Network Products Support - 226-5174  29-Dec-1994 1357" 29-DEC-1994 20:47:25.55
To:	STKAI1::EROSEN
CC:	STANLEY,WADE,CIFELLI,TAYLOR,JOHNSON
Subj:	RE:  Inquiry from Sweden - LED on FDDI concentrator Mgmnt Module

Ebbe,

Per the attached, the simple answer is that if the fault LED on the management
module is on, something is broken, or more likely, improperly configured.
We are working on a couple different situations where the DEFCN stops 
responding to management commands but continues to pass data.  However, none
of these cases involved any LED fault indications.

Last year we found a problem with the power-on sequencing logic that caused
some DEFCN's to lock up when power is first applied.  This does not match your
problem description.  Units with that problem would work fine for many months,
until power was interrupted, but then would not initialize when power was 
restored.  Those units would not function AT ALL when the error ocurred, 
although they might start to work normally again if power was cycled off/on 
again.

However, the FIX for that problem introduced some new hardware revisions that,
if used in the wrong combinations, MIGHT cause some of the symptoms you are
reporting.  Therefore, PLEASE provide us with the following information: 

	Part number and revision of the DEFCN chassis.
		If the chassis revision is questionable, please visually
		examine the unit.  When looking at the backplane through
		the module slots -

			Are there ANY green ECO wires in the area to the
			right of the module connectors ???

			If there are wires, is there just one wire running
			up and down or are there SEVERAL wires running
			left and right ???

			Are there any "dead bug" IC's ???

	Part number and revision of the Management Module.  Please obtain
	that information from the yellow bar-coded label on the rear edge
	of the module near the backplane connector.

	Part numbers and quantity of line cards.

I will be on vacation from 31-Dec through 8-Jan.  I doubt that you will be 
able to get answers to these questions for me today, so PLEASE copy both
Wayne NPSS::TAYLOR and Tom NPSS::CIFELLI on your reply.  Both of them will be
at work next week and can analyze your response.

One last item.  Do NOT be concerned about the "Optical Bypass Broken" error.
The OBR test microcode only knows about SUCCESS or FAILURE.  Failure also
means that it tried to test something that isn't there !!!  That test is only 
valid when the DEFCN has a management module with an OBR port AND there is
either a test plug or an external bypass relay plugged into the port.

Regards,

Mike J.