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

Conference netcad::hub_mgnt

Title:	DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:	Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:	NETCAD::COLELLADT

Created:	Wed Nov 13 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4455
Total number of notes:	16761

1850.0. "reject reason on HUBwatch" by TKTVFS::OHTSUKA_MU () Fri Jan 06 1995 05:46

Hi!

I have a DEF6M-MA trouble of same customer on note#1693 this note.
 
>One DEF6M-MA(port#1-5) connected 5 work stations by mic-mic cable.
>DEF6M-MA is supplied power by HUBone.DEF6M-MA port#6 is connected other 
>DEF6M-MA port on DEChub900MS.
>
>   
>  DEChub900MS             DECHUB-one
>                                 port
>       D                        D  1 ----------- w/s
>       E port3                  E  2 ----------- w/s
>       F  -----|                F  3 -----------  "
>       6       |                6  4 -----------  "
>       M       |                M  5 -----------  "
>       |       |                |
>       M       |--------------	 M
>       A                 port6  A


Trouble : DEF6M-MA port#2 MIC-PMD led lit on orange. Workstations don't 
	  communicate other one. 

Action:   I checked DEF6M-MA port 2 status by HUbwatch. Port2 rejected .
	  Reject reason was 
		" Link confidence test - protocol"
	
	  Recovered by reconnect mic cable on this port.
          DEF6M-MA f/w version 2.0.

         
I want known more information of this reject reason. Because I can't deside
this trouble only port2<->w/s trouble ,DEF6M-MA trouble or FDDI ring trouble.

Can I get more information of reference database or reference mamuals ?


Thank you.

T.R	Title	User	Personal Name	Date	Lines
1850.1	Its the link, not the whole ring	NETCAD::B_CRONIN		`Wed Jan 11 1995 14:09`	13
	The message that you describe indicates that port 2 of the concentrator determined that there was an error as it tried to wakeup the connection. Because of this error, the station was not connected into the ring. The problem would be located in the link between the w/s and port 2 of the concentrator. This would indicate that either the transmitter of w/s, the cable between w/s and port 2, or the receiver in port 2 are at fault. It is not a problem with the entire ring, it is local to that one link. Try connecting another station into that link. If the problem goes away it may be the w/s. Also, try cleaning all of the connections. If they get dirty, they can cause this to happen.
1850.2	this might be of help	TKTVFS::NEMOTO	no facts, only interpretations	`Thu Jan 12 1995 02:53`	10
	> Can I get more information of reference database or reference mamuals ? See Raj Jain's FDDI handbook, specifically the section 11.3 (Link Confidence Test) on page 202-, and the section 11.13 (Automatic Fault Detection and Recovery) on page 210-. Oka-san has the FDDI handbook, I sent it to him last month. _Tak
1850.3		TKTVFS::NEMOTO	no facts, only interpretations	`Thu Jan 12 1995 03:23`	6
	Also, see UPSAR::FDDI note 1491.4. Although it explains about how the dual homing configuration is determined, you may find some additional info on when the LCT (link confidence test) sequence takes place. _Tak