[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

1542.0. "Protocol Monitor Error under Probewatch" by PADNOM::PEYRACHE (Jean-Yves Peyrache Country Support Group France) Mon Oct 10 1994 13:55

  hi,


 i have a big trouble with Protocol Monitor feature in new version of Probewatch
 if i tried to use this option , i receive the following error message

  "Error accessing agent XXX domain YYY
   nql error Domain not present in agent YYY"

 but i have right domain select in my probe and a capture using same protocol
 works great..

  any clues with this functionnality or this items is'nt really implemented
  with current version (field test )??


  thanks

  Jean-Yves

T.R Title User Personal
Name Date Lines

1542.1 Try enabling Host and/or Conv for that domain NAC::FORREST Fri Dec 02 1994 19:00 4

T.R	Title	User	Personal Name	Date	Lines
1542.1	Try enabling Host and/or Conv for that domain	NAC::FORREST		`Fri Dec 02 1994 19:00`	4
	I saw this once too - if I remember, I didn't have the HOST group enabled of the failing domain. I'm not sure why it would need the Host group to do a Protocol Monitor, but I think that was the difference.

    I saw this once too - if I remember, I didn't have the HOST group
    enabled of the failing domain. I'm not sure why it would need the 
    Host group to do a Protocol Monitor, but I think that was the
    difference.