[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

825.0. "Decpacketproble90 and Hubwatch" by PADNOM::PEYRACHE (Jean-Yves Peyrache Country Support Group France) Tue Mar 15 1994 11:16

  hi,


 using Hubwatch for Windows V2.0 (new one)or Hubwatch for OpenVMS v2.0 i have
some trouble to get information from packetprobe90.

  Packetprobe90 is currently seen by Decagent90 (v2.0-16), using add agent
option in Community table windows(like 90TL,90M or Decbrouter)
after entered all requested informations
 (ip address ,community,Mac address,agent type), i can't save all informations
using OK or Apply items:

  the error display message appears "no response from the agent"
  if i go back to main windows (lost all parameters for my probe in Community
table) and "double clicking" on the decprobe display module nothing appears...

  of course "pinging" the ip address of the probe works as well , and using
Decprobewatch for ultrix on another workstations works too on this probe.


 any clue for this problems ??

 thanks for any comments/reply/questions

  Jean-Yves

T.R	Title	User	Personal Name	Date	Lines
825.1	Ain't nothin' to see.	SLINK::HOOD	I'd rather be surfing	`Tue Mar 15 1994 11:40`	7
	You won't get anything from HUBwatch for the packetprobe. If you select it (single-click) on the front panel, then use the Manage Current option under "Communities", I think you might see the MIB-II stuff, but that's all the support it has. Tom Hood HUBwatch
825.2	Same player ,shoot again....	PADNOM::PEYRACHE	Jean-Yves Peyrache Country Support Group France	`Tue Mar 15 1994 12:17`	10
	Tom, single or double click seems to have same result on the probe : nothing appears, using your approach ,i display only information from my Decagent90. thanks for your help Jean-Yves
825.3	then it ain't there?	SLINK::HOOD	I'd rather be surfing	`Tue Mar 15 1994 14:27`	9
	The following modules do not have added windows in HUBwatch (as of V3.0): WANrouter 90 DECpacketprobe 90 MUXservers LATprint every token ring card Tom Hood HUBwatch
825.4	hope to provide more than we have today	NAC::FORREST		`Tue Mar 15 1994 15:25`	10
	Our future plans for the DECpacketprobe are to launch PROBEwatch when the user double clicks on the DECpacketprobe. PROBEwatch is a much better manager of DECpacketprobes than HUBwatch - it will not be cost effective to include PROBEwatch in HUBwatch. Obviously, if PROBEwatch isn't installed on the same system, then we should show a MIB II summary screen and include a message to the effect "this device must be managed using PROBEwatch". We'll have to see how much of this we can include in V4 of HUBwatch.
825.5	Merci.	PADNOM::PEYRACHE	Jean-Yves Peyrache Country Support Group France	`Thu Mar 17 1994 07:42`	8
	all, thanks for theses explanations rgds Jean-Yves
825.6	Can't see a DECpprobe from HUBwatch	CGOOA::PITULEY	Ain't technology wonderful?	`Tue Feb 21 1995 12:27`	15
	I have installed a DECpacketprobe in a customer's new network. It is mounted in a DEChub90. It seems that no matter where I put the DECagent and/or the DECpacketprobe on the network, I cannot get HUBwatch to show the packetprobe. The customer is running HUBwatch 3.1 and it works properly in every other way. The DECpacketprobe does not show up in the list of modules that can be added manually to a view of a DEChub90. I'm puzzled... Brian Pituley NPC, Calgary
825.7		SLINK::HOOD	This is my new personal name for Notes	`Tue Feb 21 1995 15:32`	3
	What rev DECagent 90? What rev packetprobe? And what platform HUBwatch?
825.8	Some answers for your questions......	CGOOA::PITULEY	Ain't technology wonderful?	`Mon Feb 27 1995 15:10`	10
	The packetprobe and the DECagent are both at the latest revision of firmware.....I downloaded them before I installed them on the customer site. The HUBwatch package being used is Windows based and it is a copy that came out of a shrink-wrapped box. Version is 3.1 Brian Pituley NPC, Calgary
825.9	probably a DECpacketprobe firmware rev problem	NAC::FORREST		`Mon Mar 13 1995 18:17`	8
	I think the problem may be the later rev of DECpacketprobe code. If you can see the DECpacketprobe from the DECagent 90 console using Show Community, but not from HUBwatch, then this is most likely the problem. HUBwatch uses the device sysOID to further identify the module; Frontier changed the sysOID beginning with V2.1 firmware in the DECpacketprobe. I understand that Engineering is working to make either sysOID known in HUBwatch V4.0.