Conference netcad::hub_mgnt

2763.0. "ProbeWatch questions" by DRAC::DSMAIL () Fri Sep 15 1995 09:00

    
    
    Hi,
    
    I'm analyzing a big network with several segments and more than
    250 hosts/PC/routers/etc. using ProbeWatch 3.2 under Windows
    environment.
    
    I've detects several things that someone could clarify me.
    
    First at all there is a tree.cfg file that includes in a specific
    domain certain subdomains.
    My question is, if I want to capture/collect information about IP
    protocol I setup the Domain Manager with the IP domain, should I
    modify the tree.cfg for the IP domain that includes all subdomains
    that the IP protocol has?
    Or do I assume that the IP domain include all subdomains ie:
    UDP,Telnet,etc
    The same for the Novell protocol, does it include all sort off NOVRIP
    NOVSAP,NOVSPX,NCP,etc?
    
    Second,in the segment zoom screen appears at the Drop counter on the
    right side values diferent than zero, as many as many traffic is
    detected.What is the meaning of this Drops.
    
    Last,Having capture Atalk protocol files, I can't get a report generated
    for conversational if the files has more than 20000 bytes (aprox), is
    it a bug or is a resource problem of the packetprobe (rev. 1.5)
    
    Thanks for you help
    
    Jordi Manchon

    The tree.cfg file is for producing multi-domain reports.  If you
    want to see what percentage of IP traffic breaks down into stuff
    like NFS, TFTP, etc, you have to install those domains in the probe,
    along with the IP "parent" domain. That will collect the raw
    statistics. 
    
    If you then want the report generator to break down the IP traffic
    into specific types, you have to modify the tree.cfg file to include
    those domains that you installed into the probe.
    
    Drop events are caused when the probe can't handle the volume of
    traffic for some reason.  Its the probe that is dropping the
    packets.  It could mean that there are too many resources used up in
    the probe, therefore it has to drop some packets and not analyze
    them.
    
    You may want to bring up the console messages window.  It will tell
    you error messages.  I am currently struggling to get a conversation
    report generated myself, and the console window told me that the
    report failed because I didn't have enough memory.
    
    good luck,
    -Craig