[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

4430.0. "Link Confidence Test on DualHomed VNswitch" by TKTVFS::WASAKA (OhmiyaII MCS / 71D) Thu May 22 1997 01:00

	-< Cross-Posted in GIGASWITCH,COMMON_BROUTER >-

Hello,

We have two customers where a mysterious symptom goes out.
The following Network Configuration,


	+===============+
	|		|
       F|	[DECconcentrator900MX][M]+------+
       D|		|			|
       D|		|                       |
       I|		|                      [B]
	|	[VNswitch900EF]            [VNswitch900EF]
       R|		|                      [A]
       I|		|                       |   
       N|		|			|   
       G|	[DECconcentrator900MX][M]+------+   
	|		|              
	+===============+           The State suddenly changes STANDBY to
				    "Link Confidence Test Remote".


There is VNswitch900EF connected with DECconcentrator900 by Dual Homing.

The state of each Port connected with Dual Homing after a while becomes
abnormal. Port "A" on the VNswitch900EF side is in the state of STANDBY, but
Port on the Concentrator900 side enters the state of "Link Confidence Test"
suddenly. At this time, PHY on the Concentrator900 side is changed from usual
amber blinking into lighting. 

However, there is no problem in a usual operation. Moreover, the Dual Homing 
function operates normally. 

This phenomenon happens even if Concentrator900 taking the place of 
GIGAswitch/FDDI.

Could anyone please explain to me what this happens?

Thanks for any information.
Hiroyuki Wasaka
MCS/Japan

T.RTitleUserPersonal
Name
DateLines
4430.1fix is in the pipeline...FORBIN::WILKINSONThu May 22 1997 10:345
    The dual homed configuration has a known bug.  The fix is making
    its way towards a maintenance release.  The bug has to do with
    a memory reference that was optimized away by the compiler.
    
    Hugh
4430.2TKTVFS::WASAKAMon May 26 1997 04:2716
	Thank you for answering my question.

	This phenomenon does not have the influence directly because 
	there is no problem in operation. However, the customer cannot 
	judge at first sight whether it is a trouble of FDDI Port or not.

	Please teach us a rough estimate date to which Maintenance Release is
	released.

	Should I escalate to IPMT formally?


	Thank you for your support.
	Hiroyuki Wasaka
	MCS/Japan
4430.3IPMT itFORBIN::WILKINSONMon May 26 1997 16:145
    IPMT would be appropriate.  The specific Maintenance Release
    has not been identified yet.
    
    Hugh
    
4430.4V1.5.5 of the dvnef to fix thisNETCAD::FLOWERSHigh Performance Networking; DanThu May 29 1997 12:247
>    IPMT would be appropriate.  The specific Maintenance Release
>    has not been identified yet.

There will be a V1.5-005 maint release of the dvnef coming up shortly (in a
few days) to fic this problem.

Dan