[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

2132.0. "DECbridge 90 crash" by SNOTTY::BARRY (Ploppy Sir, Son of Ploppy) Wed Mar 22 1995 09:17

Hi All,

We have an OSF/1 V3.2 Alpha DEC 3000, running, Netview V3.1B and
Hubwatch V3.1.

In the hub we have an agent, a bridge, a brouter, a couple
of repeaters and a terminal server. All of these are working
fine and can be managed from Hubwatch apart from the DECbridge 90.

When I double click on the bridge I get the following message
and Hubwatch crashes :-

X Error of failed request:  BadValue (integer parameter out of range for operat)
  Major opcode of failed request:  61 (X_ClearArea)
  Value in failed request:  0xffff8011
  Serial number of failed request:  6386
  Current serial number in output stream:  6461

Any suggestions anyone ??

Cheers

Barry Howard

T.R	Title	User	Personal Name	Date	Lines
2132.1	Any help please....	SNOTTY::BARRY	Ploppy Sir, Son of Ploppy	`Tue Mar 28 1995 04:39`	3
	Anyone got any advice for me please ?? Barry
2132.2	A little more data needed	ROGER::GAUDET	Because the Earth is 2/3 water	`Tue Mar 28 1995 08:44`	18
	Since you didn't say it in your base note, I'll assume this is a DEChub 90. Now for some standard questions: 1) What revision of DECagent 90 firmware? 2) What revision of the DECbridge 90 firmware? 3) If you can connect a console terminal to the DECagent 90, does the bridge appear to be reachable in the [13] Show Community display? Obviously, the DECagent knows about the bridge since it appears in the hub view presented by HUBwatch. HUBwatch certainly should not crash, but it would be nice to know if it's something that the agent is telling HUBwatch versus something that HUBwatch is not handling correctly. ...Roger...
2132.3	Ok....I'll find out	SNOTTY::BARRY	Ploppy Sir, Son of Ploppy	`Tue Mar 28 1995 08:54`	4
	Cheers Roger....I'll get that info and post it back asap. Barry
2132.4	At last....some free time !!	SNOTTY::BARRY	Ploppy Sir, Son of Ploppy	`Mon Apr 24 1995 10:00`	20
	Roger, Sorry about the delay in replying....... 1) The Agent is M=BL05.01 SW=V2.1.3 2) How can I find the Bridge's version.....there doesnt appear to be a console port ?? 3) In the "show community" option on the agents console port, there is an entry for the bridge, it shows its ethernet address and says a "yes" in the reachable column. Any further info required......or any ideas about the problem ?? Thanks in advance Barry Howard NSSG
2132.5	Customers looming !!	SNOTTY::BARRY	Ploppy Sir, Son of Ploppy	`Mon Apr 24 1995 10:10`	8
	P.s. I have to give a Netview/Hubwatch demo to a customer on Thursday and am hoping that I can get this working by then.....otherwise I'll just have to hope they dont ask to see the Bridge management screens !! Cheers Barry (waiting with baited breath)
2132.6	This looks like a HUBwatch for OSF/1 problem	ROGER::GAUDET	Because the Earth is 2/3 water	`Mon Apr 24 1995 12:44`	13
	Barry... If the DECagent can see the device and says it is reachable, it is reporting the information correctly to HUBwatch. Maybe one of the HUBwatch folks can request more details to isolate this problem. BTW, if you really want to know the bridge's firmware version, you can MOP connect to it from the DECagent's console. Select menu option 15 and either enter the community/slot combination for the bridge or its MAC address. The version next to the word "FPROM" is the version of interest. It should be at least V3.1. ..Roger... formerly of DECagent 90 firmware fame
2132.7	Looks like a low version.......	SNOTTY::BARRY	Ploppy Sir, Son of Ploppy	`Mon Apr 24 1995 13:27`	10
	Roger, I have successfully tried connecting to the bridge. The version is FPROM V3.0. As you have said that this should be at least V3.1, what are the implications and what can I do about it ?? Cheers Barry
2132.8		SLINK::HOOD	April showers bring vacation days	`Mon Apr 24 1995 15:24`	1
	What kind of hub? 90 or 900?
2132.9		SNOTTY::BARRY	Ploppy Sir, Son of Ploppy	`Tue Apr 25 1995 05:48`	1
	Dechub90
2132.10	Upgrade ASAP	ROGER::GAUDET	Because the Earth is 2/3 water	`Tue Apr 25 1995 09:23`	14
	I don't recall specifics, but V3.1 of the DECbridge 90 firmware was released along with the first version of the DECagent 90 firmware. They were essentially developed together and several things are in V3.1 to support DECagent 90 operations. You should upgrade as soon as possible. However, running V3.0 should not cause the problem you are seeing. Check out note 2.0 for the latest firmware kit which contains V3.1 of the bridge firmware. FYI, there is a V3.9 of the DECbridge 90 firmware that is available. There are other notes in this conference giving pointers to it. This version will be available with the next release of the firmware kit, due out shortly. ...Roger...
2132.11	Trying to upgrade....but.....!!	SNOTTY::BARRY	Ploppy Sir, Son of Ploppy	`Tue Apr 25 1995 13:14`	18
	I have installed NDU V1.0f and the version of the firmware images pointed to by note 2.0. I can see the Bridge with the "download show device ....." command but when I issue the following command : "download load/nomanagement/log 08-00-2b-39-a5-a9 mom$load:dewgb310.sys" I get the following error message : "%NDU-E-OTHER_USER, protocol being used by other user %SYSTEM-F-BADPARAM, bad parameter value" Anyone point me where I'm going wrong ?? Cheers Barry
2132.12	Bridge firmware upgrade done	SNOTTY::BARRY	Ploppy Sir, Son of Ploppy	`Wed Apr 26 1995 05:41`	30
	A chap called Paul Djerbaka has sent me the solution to my NDU loading problem : I think you may have Terminal Load Service Enabled. Try doing the following to your Active Circuit (assuming; una-0): * NCP> Set circuit (una-0) state off * NCP> Set circuit (una-0) service disable * NCP> Set circuit (una-0) state on I have now managed to load V3.1 of the firmware into the DECbridge 90. The initial problem....ie. the hubwatch crash is still present : X Error of failed request: BadValue (integer parameter out of range for operati on) Major opcode of failed request: 61 (X_ClearArea) Value in failed request: 0xffff8011 Serial number of failed request: 6575 Current serial number in output stream: 6650 Any advice anyone please.....(I am running out of time quickly!!) Cheers Barry Howard NSSG
2132.13	Now up to V3.9	SNOTTY::BARRY	Ploppy Sir, Son of Ploppy	`Wed Apr 26 1995 08:10`	7
	I have also now upgraded the Bridge to V3.9 of the firmware...... Any suggestions where to go from here ?? Cheers Barry
2132.14	Problem found.......	SNOTTY::BARRY	Ploppy Sir, Son of Ploppy	`Wed Apr 26 1995 12:32`	19
	Hi All, I have found the problem (perhaps I should have mentioned this before). As I mentioned, we have been running Netview and Hubwatch from an OSF/1 Alpha. But I have been firing the windows back over the network to my VAX station at my desk. Having spoken to someone who has had a lot of problems firing Netview windows back over the network, I have put a screen/keyboard etc etc on the OSF/1 box and guess what.....yep thats right.....no more Hubwatch crashes. It looks like it doesnt like this configuration....... Any ideas why anyone ?? Cheers Barry (perhaps the customer will be impressed after all!!)