Page History

...

Modified to enable both the hostname and IPv6 address to be the same. It is integrated with the new xml files generated from NODEDETAILS.  It is backward compatible.

traceroute.pl

Modified to make work on Solaris and Linux:

...

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.pl 

Call with:

wrap-analyze-hourly.pl  --usemetric --dataset ipv6 --by by-node --size 100 --set_metric 3 --date 2017-12-19

This will use as input:

• /nfs/slac/g/net/pinger/pingerdata/<dataset>/data/<nodename>/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 

We decided to stick with a single data set (hep) and wrap-analyze-hourly now allows both IPv4 and IPv6 addresses by using the valid_ip function. 

The other analyze scripts (daily, monthly and yearly) did not need mondification.

APEX/Oracle user interface to PingER NODEDETAILS database

This did not accept IPv6 Addresses, see INC0176849 and INC0176966. It has been fixed., see INC0176849 and INC0176966. The NODEDETAILS Oracle Apex database now accepts IPv6 addresses as the name (in case there is no name for the host) and as the IP address. It is backward compatible and also (as before) accepts IPv4 addresses in both fields. 

%NODE_DETAILS=(
"2001:da8:270:2018:f816:3eff:fef3:bd3" => [  
"2001:da8:270:2018:f816:3eff:fef3:bd3",   
"gzhu.edu.cn",   
"CN.GZHU.EDU.IPV6",
"CERNET Cloud",  
"Tsinghua University, Beijing",  
"China",
"East Asia",
"23.037002 113.36777",
"M",
"http://[2001:da8:270:2018:f816:3eff:fef3:bd3]/cgi-bin/traceroute.pl?function=ping",
"http://[2001:da8:270:2018:f816:3eff:fef3:bd3]/cgi-bin/traceroute.pl?choice=yes",
"http://[2001:da8:270:2018:f816:3eff:fef3:bd3]/cgi-bin/ping_data.pl",
"http://www.gzhu.edu.cn/",
"",
"",
"",
"Saqib Ali <saqibutm\@outlook.com>, Prof. Guojun Wang, csgjwang\@gzhu.edu.cn; csgjwang\@gmail.com",
"Test record by Venkat based on add by Cottrell 12/19/2017.",
],

...

Nodename (the primary key)

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, which is backward compatible as far as the user is concerned.

ipaddress 

Ipaddress is limited to 15 characters and expecting a format of ^[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}\.[[:digit:]]{1,3}$

...

We modified NodeIPCheck-new.pl to add a subroutine to use dig to find the IPv6 address of a host and also to validate the hostname and Iv6 address. These were used in script write_offsitenodes.pl.

node.pl

There were no changes.

IPv6 Targets

See Validating ICMP ping measurements against TCP nping measurements

...