[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

2850.0. "HUB manager V4.1 ...forgot Decpacketprobe90 ??" by PRSSOS::PEYRACHE (Jean-Yves Peyrache Country Support Group France) Tue Oct 10 1995 08:11

 Hi,

 with 4.0.X of HUB manager and HUbwatch, i was able to see my Decpacketprobe90
in my HUB900 (just from panel view but with leds) and start Probewatch
 directly by double clicking on my Probe (of course if Probewatch was installed)

 Now With V4.1.X of HUB manager i can see my probe always (just the front panel
 i have lost leds..) but i can't start Probewatch.

 can anybody will explain this difference ? 

 thanks 

 JYP

T.R	Title	User	Personal Name	Date	Lines
2850.1	Remove & Insert the probe....	FOUNDR::SKABO	Expect Nothing U never disappointed	`Tue Oct 10 1995 08:58`	24
	Hello Jean-Yves, I had a similar problem with an upgarde, and what I did was to remove the Probe from the HUB and put it back it.... This has been QARed (QAR # 2200) Try this, it may help.... NOTE: This only happened to me on DOS (Windows) as OSF worked okay. Tom Skabo ---------------------------------------------------------------------------- Description of QAR #2200: Description: When you upgrade the MAM (In this case from V4.0.0 to V4.1.0, or V4.0.4 to V4.1.0) the probe icon is seen (Logical View) before the upgrade. After the upgrade, the probe icon is "blank". Doing a soft reset of the probe does not correct the problem, you must pull the probe out of the hub and put it back in. Then the probe icon is seen in the Logical View. Taking HUBwatch for DOS down and bring it back up, the probe icon is still missing. NOTE: This is only for HUBwatch for DOS, works correctly for DIGITAL UNIX
2850.2	Set environment variable also	NETCAD::FORINO		`Tue Oct 10 1995 09:28`	6
	About lauching Probewatch from HUBwatch. Speaking for the OSF version HUBwatch V4.0 tried to lauch Probewatch from the hardwired location /usr/kits/PROBEwatch/bin but in V4.1 it now uses the environment variable NSHOME (or $NSHOME - check the Probewatch documentation). Make sure that is set if running V4.1 John
2850.3		PRSSOS::PEYRACHE	Jean-Yves Peyrache Country Support Group France	`Tue Oct 10 1995 10:35`	15
	thanks all, re:1 in my case Hubwatch see the module in the slot but like other unmanageable module (no front panel view just a module with the type writed on it and under the Lan interconnect a beautiful ? in the slot) re:2 if in launch directly Probewatch without HUBwatch it's work.aka NSHOME is correctly set. before V4.1 i can double click on the module now i can't. may be a "b..g" or a little miss in the firmware JYP
2850.4	What platform	NETCAD::FORINO		`Tue Oct 10 1995 18:11`	3
	What platform are we really talking about here - Windows or OSF? John
2850.5	all of them	PRSSOS::PEYRACHE	Jean-Yves Peyrache Country Support Group France	`Wed Oct 11 1995 04:32`	3
	the pb is reproductible on osf and windows base JYP
2850.6	Follow-up on the Fix....	FOUNDR::SKABO	Expect Nothing U never disappointed	`Thu Oct 12 1995 12:10`	15
	Sorry.... This was taken off line via MAIL but to let all know, that Jean-Yves problem in 2850.0 was corrected by removing the Probe module from the HUB and re-inserting the module back into the HUB..... YEP - MAGIC again... ;*) This could be "close" to the same problem I identified in QAR #2200 (See reply 2850.1) - also maybe a MAM soft reset could also correct the this problem problem. But in any case the MAM people should maybe look into this. Thanks, Tom Skabo - former_HUB_Systems_Tester@lkg_now_in_TAX-FREE_NH!