[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

1253.0. "DECrepeater900 problem?" by TKTVFS::OHTSUKA_MU () Wed Jul 27 1994 11:44

  Hi!

  I had similar troubles of DECrepeater900.(4 times)

  It's inserted in DEChub900 , and assigned to "inbound ip address" slot module.
  This hub has other module (DECbridge900 and DECconcent900) and connected
  other DEChub900s by FDDI . These hub are formed DAS FDDI RING .

  The workstation which is connected in DECrepeater900 on remote hub , didn't
  get respose from problem hub by ping command to hub's inbound address.

  User operation looks good. ( End to End communication is good through 
  problem repeater <-> hub <-> FDDI <-> other hub <-> other repeater)


  I guess,  Bad DECrepeater900 don't give it's MAC address to DEChub900
  inbound address.

  I had those recover operations.
        a. Remove and insert DECrepeater900 ( 2 times) <== intermittent
        b. Replace DECrepeater900 ( 2 times )          <== fixed
	
	DEChub900 mam version : T3.0.19
  	DECrepeater900 version: HW=v2,RO=v1,SW=v1.0G

  Can I get any information ?

  thanks,

T.R	Title	User	Date	Lines
1253.1	Do not use T releases	LEVERS::SLAWRENCE	`Thu Jul 28 1994 17:45`	1
	You should not be running MAM T3.anything - please upgrade to V3.0.0
1253.2	I'll schedule MAM upgrade	TKTVFS::OHTSUKA_MU	`Thu Jul 28 1994 21:14`	2
	Thanks, !!