[ANSS-netops] Q330 POC Software Question

[Jennifer Eakins]

The Antelope program q3302orb in conjunction with orb2logs logs writes out POC contact information.  

For example:

      2015223 00:00:02.443: targetname: POC-:poc: Processing POC from 1XX.1XX.8X.2XX:5330, sn=010000A1A1A1A1A1, lport=1, ip=1XX.XXX.XXX.XXX

Individual datalogger log files contain information as well:

      2015223 08:32:24.106: targetname: TA_XXXX: POC initiated acquisition start.

You also get a notification when the datalogger ip address has changed (in this case from the null “ - “ to a value):

      2015221 17:01:27.723: targetname: TA_XXX: POC change in datalogger ipaddress - resetting from - to 7X.XX.XXX.XXX

I also use some internal scripts that will review these logs and review to see if we are not getting POCs from a particular datalogger.  In addition, I have an Antelope script that allows for a batch report and/or resetting of the POC structure on remote dataloggers:  very useful when you have 400+ to review at one time.

—Jennifer

On Aug 11, 2015, at 10:10 AM, Patrick Bastien <bastienp at ldeo.columbia.edu> wrote:

> Has anyone written or know of software that logs Q330 POCs to a file? The seispoc.exe program only displays the POC on the screen or integrates with Pecos, but does not write to a log file.
> 
> Thanks,
> Patrick
> _______________________________________________
> ANSS-netops mailing list
> ANSS-netops at geohazards.usgs.gov
> https://geohazards.usgs.gov/mailman/listinfo/anss-netops

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://geohazards.usgs.gov/pipermail/anss-netops/attachments/20150811/4ce2b1a7/attachment.html>