Web Interface for the Guthrie Database can be accessed here:

https://oraweb.slac.stanford.edu/apex/slacprod/f?p=123:1

As an example we will add pinger.aup.edu.pk in the database.
The main page contains a Table of Nodes already present in the database. There is a search box, at the top of this table to search against all the columns.

We first search for any other entry containing the word 'aup' in it. 
We see there is just one other entry and it is disabled. We will now create a new entry.

On clicking the button 'Create' we see the following interface:

• We now enter the IP address of the Node.
• Entering the Nodename of the host, which is pinger.aup.edu.pk
• Next is site name. This should be aup.edu.pk
• Nickname is way to identify domains. It is very much similar to reverse DNS lookups. e.g. In case of our Example the Nickname is PK.AUP.EDU.N2. The entry would then be: 
• Full name follows then. Which in this case will be 'Agriculture University of Peshawar'.
• Location refers to the city( and state) or other such information that can identify the location of the host.

To enter value for Country Continent, click the small notepad icon next to field. A pop up appears with locations. Upon selecting a location, the field is set appropriately. 

After you select the Country link the Country Continent Field becomes:

• To add Lat Lon, One can visit a number of websites. The most commonly used one is http://www.satsig.net/maps/lat-long-finder.htm

Latitude and Longitude should be separated by a space. The final result is:

• Project Type can be one of M, B or R. Where M refers to Monitoring Node, B to Beacon sites and r to Remote node. We enter M for our new monitoring Node.
• PingServer is a link to the traceroute script running on the new node. In case of pinger.aup.edu.pk, it is http://pinger.aup.edu.pk/cgi-bin/traceroute.pl?function=ping
• http://pinger.aup.edu.pk/cgi-bin/traceroute.pl?function=pingTraceroute Server is a link to the traceroute script without function=ping. Which will be http://pinger.aup.edu.pk/cgi-bin/traceroute.pl?function=ping
• http://pinger.aup.edu.pk/cgi-bin/traceroute.pl?function=pingDataServer refers to url for ping_data.pl script which is used by getdata.pl script running at Archive site to collect data. In case of pinger.aup.edu.pk, this will be http://pinger.aup.edu.pk/cgi-bin/ping_data.pl?
• Due to implementation limitations, it is very important to place a question mark at the end of Data Server URL.
  
• If the remote Host requires a username and password to access then, place a space after the remote url and then place the username:password string. e.g. 
  http://[*username]:[password]@*vle.iiu.edu.pk/cgi-bin/pinger/ping_data.pl? 
• In URL we enter the web url for the site. This will be http://www.aup.edu.pk.
• We then enter Contact Details for the Person incharge of this node. These details are used whenever we run into problems.
• pingsize should be kept blank if the remote site accepts both 56 and 100 byte sized packets. In case the remote site is configured to accept anyone, then we suggest selecting that value.
• In comments section, enter the changes, name of the owner and data time of the change or new entry. Also it is very important to indicate the change. This will help us revert any changes in the future if need be.