Conference netcad::hub_mgnt

751.0. "Probewatch questions" by SIOG::PARKS () Tue Feb 22 1994 12:13

I need answers to the following questions on probewatch quickly.

1) I copied the probewatch kit from cigam::/usr/kits/PWULT100.tar. Each time I
start probewatch, I get a copyright message for Frontier Technologies and the
version number is V2.23. Is this DEC's V1.0 product ie. am I using the right
version of probewatch ?

2) I normally use 100dpi fonts on my monitor, I have to use 75dpi fonts for
probewatch otherwise the windows don't form properly on the screen. Is this a
bug ?

3) When the discovery process runs and says it has discovered so many new
mappings where does it store this information. The only way I have found to get
new information in /usr/kits/probewatch/user.def is to do a data capture then
protocol decode and use the learn addresses option. This puts the information
into user.def. Is this the correct operation of probewatch ?

My customer wants to 'discover' new devices on the ethernet by running the
discovery process periodically and see if there are new devices.

Ideally I would like an snmp trap when a new node is discovered.

4) When I use the watchdog to setup a packet/sec trap on a rising threshold.
(Generate Trap When: Rising Threshold Reached). The trap only appears to fire
when the packet/sec rate rises past the threshold for the first time. The trap
only fires subsequently if the modify button is hit. I would like to be told
every time interval the value is exceeded. Is this correct behaviour for
probewatch ?

I could only setup up the packetprobe for a single trap. Is is possible to
setup the probe for more than 1 trap, if so how ?

3) When I register (partially) the packetprobe on DECmcc/Ultrix either DECmcc
gets all snmp traps (packetprobe and others) or probewatch gets all snmp traps.
The application that starts first binds to port 162 and gets all the traps. Is
this a bug ? The trap that DECmcc receives doesn't contain eventDescription MIB
value so it doesn't tell you what trap occurs, which is not very useful.

When DECmcc tries to register the packetprobe it pings it, the packetprobe
echos the ping, DECmcc then issues three 'get next requests' for object
{1,3,6,1,3,27,0} which is the EXP_RMON. The packetprobe doesn't respond to any
of the three requests and the registration fails.

Thanks.
Colman

    
    Hi,
       I have some more questions to add to this section. I to have the kit
    called PWULT100.TAR which is in fact v2.23 .
     
    Anyway, here goes :
    
    1.	Can Probewatch display a pie graph (or similar) of the protocol
    breakdown on a given LAN segment?? (I can see what the packets are by
    doing a trace, but havent found a graph option for it)
    
    2.  What is the pointer to the Probewatch for Ultrix manual?
    
    3.  Is a Windows version of Probewatch available yet?
    
    4.  Are there plans to allow for an out-of-band port on the packetprobe
    in the advent of total LAN failure or a TCP/IP addressing (or
    subnetting) problem which may prevent LAN comms between the station and
    probe??
     
    5.	Are there any competitive edges that this product offers over the
    HP Lanprobe product?? (At least the LANprobe has out-of-band
    capabilities)
     
    
    Any help would be greatly appreciated!
     
    Regards,
    	   Jason