[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

2161.0. "Decrepeater 900TM disconnecting from additional configured backplane" by KERNEL::CHOPRAA () Fri Mar 31 1995 15:14

Hi,

I have a customer with the following configuration;

Two Decrepeater 900TM's in a Dechub 900.  Each repeater is conected to it's own isolated
LAN; one on the default thinwire and the other on an additionally configured ethernet lan.

A problem occured where both repeaters became connected to the default thinwire lan - this
posed a serious security problem for the customer.

As far as I know, the only ways that this could have happened are 

	1. The decrepeater 900TM was power cycled 	or
	2. The Hub manager was reset to factory defaults.

I am fairly sure that neither of these events happened.  Unfortunatley, after the event the
repeater was power cycled so we lost the error log.

Both repeaters are running Version 1.1 and the HubMan is version 3.1.

In an attempt to isolate the problem, I have created two additional ethernet lans and
connected each repeater to a seperate lan.  Neither of the repeaters are connected to the
default Thinwire lan.

Hence if the problem re-occurs, I'll be able to see if the problem was with the HUBMAN (ie
both repeaters connecting to the default thinwire) or with one of the repeaters (ie one of
the repeaters becomming connected to the default thinwire lan).

Has anyone seen a similar problem or does anyone have any ideas as to what the problem could
be.

Thanks

Anil Chopra.
T.RTitleUserPersonal
Name
DateLines