Page History

...

This does not accept IPv6 Addresses, see INC0176849 and INC0176966. 

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.

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.

Testing

The connection to the database is  defined in: /afs/slac/package/pinger/oracleArchive/netratDb.pm

...

The password is kept in a protected file. The password on SLACDEV2 was changed to match the one on SLACPROD

Accessing SLACPROD and SLACDEV2 from the web as follows, they use the same windows userid/passwords

• To access the SLACPROD production copy of the NODEDETAILS database go to:
  • https://oraweb.slac.stanford.edu/apex/slacprod/f?p=123:2:15892093406016::NO:2::
• To access the SLACDEV2 test copy of the NODETATILS database go to: 
  • https://oraweb.slac.stanford.edu/apex/slacprod/f?p=123:2:15892093406016::NO:2::

XML file at Guanhzhou

See here. Currently, it contains random pingable IPv6 addresses as I have taken it from http://www.ipv6forum.com/ipv6%5fenabled/approval%5flist.php

...