...
Copied getdata.pl to getdata-ipv6.pl and modified to use the /afs/slac/package/pinger/nodes-ipv6.cf file and write to the /nfs/slac/g/net/pinger/pingerdata/ipv6/data/ directory (e.g. /nfs/slac/g/net/pinger/pingerdata/ipv6/data/2001:da8:270:2018:f816:3eff:fef3:bd3/ping-2017-12-19.txt.gz) when running getdata-ipv6.pl 2001:da8:270:2018:f816:3eff:fef3:bd3 2017-12-19 1. Also replaced IPv4 address checks with sub chck_ip{} to test for both IPv4 and IPv6 addresses.
wrap-analyze-hourly.plpl
Call with:
wrap-analyze-hourly.pl --usemetric --dataset ipv6 --by by-node --size 100 --set_metric 3 --date 2017-12-19
This will use use as input:
- /nfs/slac/g/net/pinger/pingerdata/<dataset>/data/<mas>/ping-<year>-<mm>-<dd>.txt.gz
- or more specifically /nfs/slac/g/net/pinger/pingerdata/ipv6/data
...
- /2001:da8:270:2018:f816:3eff:fef3:bd3//ping-2017-12-19.txt.gz
Output will go to:
- /nfs/slac/g/net/pinger/pingerreports/<dataset>/<metrics>/<metric>-<size>-<by-node>-<yyyy><mm><dd>.txt.gz
- or more specifically /nfs/slac/g/net/pinger/pingerreports/ipv6/minimum_rtt/minimum_rtt-100-by-node-2017-12-19.txt.gz
APEX/Oracle user interface to PingER NODEDETAILS database
...
APEX doesn't like colon(:) in primary key column values. Primary key value is passed in the URL as a parameter and APEX parameters are separated by colons (:), which is causing the issue. Venkat provided a workaround. We will test this on the Oracle SLACDEV2 (SLACPROD is the production version) test database.
ipaddress
Ipaddress is limited to 14 characters and expecting a format of ^[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}$
If you want to increase the length or change the format, we need to modify the interface code. Proposal is to extend the field to 100 characters (like the other fields) and not apply any filters.
...
I made a copy of the script and in /afs/slac/package/pinger/oracleArchive/netratDb-dev2.pm and substituted slacdev2/SLACDEV2 for slacprod/SLACPROD and also made a copy of /afs/slac/package/pinger/guthrie/node.pl to call the new script.
Also as a short cut we made a copy of the nodes.cf file to /afs/slac/package/pinger/nodes-ipv6.cf
The password is kept in a protected file. The password on SLACDEV2 was changed to match the one on SLACPROD
...
- To access the SLACPROD production copy of the NODEDETAILS database go to:
- To access the SLACDEV2 test copy of the NODETATILS database go to:
...