Conference netcad::hub_mgnt

  i think your are limited to 6 characters in the name of probe
  try using probe9 instead probe90

  jean-yves

    I just tried using a 6 character name for the probe and I still get the
    syntax errors.
    
    Does anyone know if there is some sort of debug flag (switch, variable)
    that I can set up to try to log more info about the error condition.
    Right now I can't tell what item in the dvlog.cfg file has the syntax
    error!!
    
    Richard

 it's works very well for me..

  try to put in DVLOG.cfg  all words in same place/space

#
#       probe1  IP      00:15   02:00   08:00
#       probe2  TCP     -       04:00   -
#       probe3  ALL     01:00   -       24:00
#
        probe9  ALL     00:15   00:30   02:00

       instead 

#       probe1  IP      00:15   02:00   08:00
#       probe2  TCP     -       04:00   -
#       probe3  ALL     01:00   -       24:00
#
probe90         ALL     00:15   00:30   02:00


 may be an key sensitive problem

  jean-yves

    Jean-Yves, thank you very much for your assistance.  I have been
    able to get the data logging to work - somewhere in the dvlog.cfg
    file was something that the dvlogd.exe did not like.  I wasn't able
    to find the exact cause, however.  I took your example in .3 (did
    and extract of the note and used VMS EDT to edit out all but the
    bare essentials, then kermited that file to my pc and logging worked.
    
    When you edit your .cfg files, what editor do you use?? I was using
    DOS edit.  Guess I should try Notepad, Write, or MSWORD (saving as
    a straight text file, of course).
    
    Also, have you noticed that the logging daemon is sometimes contrary
    about starting up?
    
    Richard

>>    When you edit your .cfg files, what editor do you use?? I was using
>>    DOS edit.  Guess I should try Notepad, Write, or MSWORD (saving as
>>    a straight text file, of course).

  Dos Editor

  >> Also, have you noticed that the logging daemon is sometimes contrary
  >>  about starting up?

   nothing in logfile ??
   have you enough of memory and disk's space in your PC ??

   jean-yves

    Jean-Yves,
    
    When the logging daemon fails to start there's no indication in
    the dvlog.log file.  I have a DEC 425sl laptop with 8 meg of memory
    and a 200 meg hard drive with 10-12 meg of free space.  Failure of
    dvlogd to start has always been cured by simply stopping the trap
    and config daemons after exiting PROBEwatch, then restarting PROBE-
    watch.  
    
    Just in case it's pertinent, I am using a Xircom PCMCIA Ethernet
    card (CB10 I think its called). 
    
    Richard

    What is your UDPMaxSock set to in PWTCP.INI? It should be set to 20. 
    If it is set too low, then the daemons will not be able to grab enough 
    buffers to run. At least that's my guess.

  Yes, i think all TCP/IP parameters must be boosted  if you want
  running all applications of probewatch Concurrently


   jean-yves

  

    I recently tried to do some report generation of the host
    converstations (other reports work) but no report gets
    generated.  The dvlog file shows that data got logged for host
    conversations and the data file is in the directory.  The report
    generation screen says it's generating a report, but the report
    directory has no report in it.  I have made sure I specify a time
    range within which there should be conversation data, but the result
    is the same - no conversation report.
    
    BTW - why would the report "profiles" be written to the root directory.
    (report profile being the rpt1, rpt2,.... file that contains the
    parameter for start/end time, etc for the report to be generated)?
    
    This should probably be a separate note, but why is it that the probe
    for the domain you want to generate reports for must be ip reachable 
    in order for a report to be generated?   
    

    Hi!!
    
    I'm about to deliver a series of LAN Performance Analysis Reports using
    Probewatch 3.1 but have not been able to get Report Generator to work.
    
    The symptoms are almost identical to Richard's original problems, so
    could you tell me if you ever decided what the solution was.
    
    At present I'm trying both the Report Generator and the dvlog.cfg file
    for some kind of result but neither are producing the goods.
    
    Maybe if you listed the steps you took to success I could do a sanity
    check.
    
    Thanks,
    
    Brendan.
    
    
    
     

    
    
    Brendan,
    
    	It has taken me two days to get this to work but I was just able
    to generate my first report from Probewatch for Windows.
    
    Here is what finally worked for me.
    
    Edit the c:\probew\usr\dvlog.cfg file (I used dos editor) and remove
    the last # symbol.  Replace the probe, domain and times with your
    values.  In my case I used:
    
    	kaopb2	ALL   00:15  00:15  00:15
    
    I then created the following directories
    
    C:\probew\db
    c:\probew\db\kaopb2
    c:\probew\db\kaopb2\all
    c:\probew\reports
    
    I then restarted probewatch for the bazillionth time and checked that
    the PROBEwatch Logging Daemon was running (look for Icon).  It doesn't
    always seem to start.
    
    After 15 mins I had three files created in the C:\probew\db\kaopb2\all
    directory of the format date.15c,15e,15h.
    
    According to the logreport.txt file on nac::nipg:[manage.rmon] it says
    you need two samples to generate a report.  I waited untill I had files
    with .30c.30e,30h as well.
    
    I selected the domain manager from the probewatch main window.  This
    open the domain manager and I selected my probe kaopb2 and then chose
    report generator from the tools pull down menu.
    
    I chose segment statistics and generate.  This created a report.txt
    in the c:\probew\reports directory.
    
    This is as far as I've gotten so far.  Hope this helps. Lord knows what
    customers are supposed to do.
    
    Scott
    

    
    
    Well I can make a segment traffic stats report but that is it.
    
    When I try to envoke the host report I get:
    
    	DVREPORT caused a general protection fault in module DVREPORT.EXE
    at 0001:B54B.
    
    Nothing happens when I try to run the conversations report.
    
    Also why do rpt?? files get create in C:\   ??? Is there a variable to
    redirect these files?  Also is there a log file I can check to try to
    figure out why the other reports don't run.
    
    Scott

    Scott,
    
    Thanks for the assistance!!!
    
    I reached the same stage that you decribe in .12 but I'm stil
    puzzled about dvlog.cfg. I've been trying to isolate the difference
    between editing a existing line in the dvlog.cfg header and appending
    your own line, but so far the only difference appears to be that one
    works and one doesn't.
    
    At this stage I have a maximum logging ability of 3
    probes/domains/lines...
    
    Another  alternative for me appears to be in increasing the number of
    buckets when installing the domain but I've had trouble here as well.
    There are Packetprobe memory restrictions to consider but if I can
    record 580 buckets of 5 minute intervals this gives me the 48 hour
    record I desire without the requirement of a dedicated PC during this
    session.
    
    Anyway, I've raised these issues in a new note (2070)
    
    Thanks again,
    
    Brendan.