...
Name | Null? | Data Type | Use |
---|---|---|---|
NODENAME | NOT NULL | VARCHAR2(100) | DNS host name |
IPADDRESS |
| VARCHAR2(15) | IPv4 address |
SITENAME |
| VARCHAR2(100) | Domain name of the node |
NICKNAME |
| VARCHAR2(35) | Abstraction of the hostname with the TLD first and the hostname last1 |
FULLNAME |
| VARCHAR2(100) | Human-friendly description of the node/site/Institute |
LOCATION |
| VARCHAR2(100) | City and/or State/Province/Region for node 2 |
COUNTRY |
| VARCHAR2(100) | Country for node |
CONTINENT |
| VARCHAR2(100) | Continent or region where node is thought to be located 3 |
LATANDLONG |
| VARCHAR2(25) | Latitude and longitude of node (as signed decimal values separated by a space) |
PROJECTTYPE |
| VARCHAR2(10) | Flags describing how nodes are used 4 |
PINGSERVER |
| VARCHAR2(100) | URL for requesting a ping from this node to another 5 |
TRACESERVER |
| VARCHAR2(100) | URL for requesting a traceroute from this node to another 5 |
DATASERVER |
| VARCHAR2(100) | URL for retrieving PingER data from this node 5 |
URL |
| VARCHAR2(100) | URL for the home page for the institution running the node |
GMT |
| VARCHAR2(10) | Node's time offset from GMT, not used |
COMMENTS |
| VARCHAR2(4000) | Comments and notes on when and how the node's record was last updated 6 |
APP_USER |
| VARCHAR2(20) | Windows user name of the last user to edit the node's record through the UI. THis is entered automatically. |
CONTACTS |
| VARCHAR2(100) | Name and email address(es) of the node's maintainer(s) |
PING_SIZE |
| NUMBER | Size of pings to be sent to the node - only controls SLAC's PingER install. Usually left blank. |
...
- EDU.SLAC.STANFORD.PINGER - node at SLAC,stanford.edu, fully qualified hostname pinger.slac.stanford.edu
- CH.CERN.N2 WANMONINST1 - second node at CERN, fully qualified hostname wanmoninst1.cern.ch
- AO.UCAN.EDU.N1 - first node at the Catholic University of Angola, hostname fully qualified hostname www.ucan.edu
- For IPv6 host we insert IPV6 in front of the hostname:
pship02.csc.fi =>NICKNAME=> FI.CSC.IPV6.PSHIP02
- If it is a NET or ORG etc. add the TLD country code at the start:
ps-esu-lt.perfsonar.kanren.net=>NICKNAME=>US.NET.KANREN.PERFSONAR.IPV6.PS-ESU-LT
Anchor | ||||
---|---|---|---|---|
|
...
Anchor | ||||
---|---|---|---|---|
|
...
Code Block | ||||
---|---|---|---|---|
| ||||
update country set country = 'Democratic Republic of Congo' where country_id = 461; |
Finally, fix any incorrect entries in the actual NODEDETAILS table by putting the correct country in the set clause and the incorrect value in the where clause.
...
The checking the validity of the data is not particularly robust, especially when creating a new entry. It can complain that there is an error in the data (invalid IPv4 address, extra spaces in the field, duplicate nodename (i.e. it already existsiexists)). The rror error messages are not very instructibeinstructive. In this case cas,e you may be able to correct the enyry or you may have to cancel the entry and re-create it.
...