[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

428.0. "Can't see DB 90 fields in HUBwatch for Windows" by HKGACT::RICHARDLAM () Thu Oct 14 1993 02:29

   
   Hi,
   
   The question relates to Hubwatch for Windows....
   
   I was trying to enter bridge information for a DECbridge 90 module. With 
   the bridge module zoomed in, I clicked Configuration Report Bridge Info. 
   The "Bridge Information" window came up.
   
   However all I can modify was the "Bridge Name" field, the other fields 
   were not bolded. I entered "demobridge90_1" in the "Bridge Name" field, 
   hit the TAB key; it immediately took me to the "Modify" section of the 
   window. If I hit the ENTER key instead of the TAB key, it'd ask me to 
   click OK, Apply, Cancel. I just could not get to the other fields such as 
   NVRAM Self Test, Oper Status, SANMP Agent ....
   
   In addition when I tried to open the Performance Statistics Window for the 
   same module, none of the fields in both "Backbone - Port 1" and "Workgroup 
   - Port 2" was bolded, and the contents in these fields were blank.
   
   Thanks in advance for any help.
   
   
   Richard

T.R	Title	User	Personal Name	Date	Lines
428.1	More info...	CGOS01::DMARLOWE	dsk dsk dsk (tsk tsk tsk)	`Thu Oct 14 1993 17:44`	4
	What version of HUBWATCH are you running? Also what are the version numbers for the DB90 that you are using? dave
428.2	REV of DB90 and DEVagent 90	HKGACT::RICHARDLAM		`Fri Oct 15 1993 04:34`	18
	I could not connect to the console via NCP connect. It gave me "Target does not response" message. I don't know why; I tried this before and did not have any trouble. Would this be the cause of the problem? Anyway on the back of the DB 90 it says: REV A01. For the DECagent 90: REV B02. Are these revisions supported? Or am I giving you the right information? If not, please tell me what the min. REV have to be, thanks! I am sure the bridge is working though. Because there are terminals connecting to a DECserver 90L+ which is in slot 2 of the DEChub 90, while the DB 90 is in slot 8, and its AUI port is connected to a DELNI to provide connection to the LAN. Richard
428.3	Hubwatch beta 1.1	HKGACT::RICHARDLAM		`Fri Oct 15 1993 04:42`	5
	By the way the HUBwatch icon says its version is Beta 1.1, while the Readme.TXT says V1.0. richard
428.4	DB 90 firwire version a factor	HKGACT::RICHARDLAM		`Mon Oct 18 1993 06:49`	8
	I swapped out the DB 90 and put a new one in. It started to work. Thanks to those who have given attention to this question. However it does appear that some DB 90 support MOP and some don't. Does it have anything to do with the firmwire revision? Anybody? Richard
428.5	All DECbridge 90s support MOP.	NAC::FORREST		`Wed Nov 10 1993 15:54`	5
	All DECbridge 90s since day 1 have supported MOP; however only those with rev 3.0 or higher firmware support RBMS. The DECagent 90 speaks to the DECbridge 90 using RBMS and translates that to SNMP. I'm not sure why you couldn't talk to that bridge using MOP.