Error Message |
How to fix the error |
Overlaps found within whois cust-networks |
Overlaps were found within entries in the APNIC Whois Database inetnum objects that you registered. You need to fix either the whois entry or the cust-network line. |
Error parsing address and netmask |
The IP address or subnet mask you have provided is not in the correct format. You need to fix the incorrect IP address field or the incorrect subnet mask field. |
Overlaps found within cust-networks |
Overlaps were found within the two cust-networks mentioned in the error message. You need to fix the incorrect line. |
Overlaps found within infrastructure |
Overlaps found within the two infrastructure lines mentioned in the error message. You need to fix the incorrect line. |
Overlaps founds within cust-network and infrastructure |
Overlaps found between a cust-network line and an infrastructure line provided. You need to fix the incorrect line. |
Could not find inetnum object in whois database |
Cust-network line provided has not been updated into the APNIC Database. You need to update the database entry for that customer assignment. |
More than one inetnum object found in whois database |
Overlaps found within whois entries within the database. You need to fix the database entries. |
Problem retrieving inetnum object in whois database |
System error accessing the APNIC Whois Database. Please try again later or contact APNIC staff if you experience this error message. |
Netname mismatches against whois netname |
Cust-network netname provided is not the same as the netname registered in the APNIC Whois database. You need to fix the cust-network field or database entry. |
Number of initial hosts is greater than number of hosts available for address |
The initial host estimate provided is larger than the maximum number of available hosts in the subnet assigned. The host estimates should always be equal to or less than the maximum number of hosts in the subnet. |
Number of hosts after 6 months is greater than number of hosts available for address |
The 6 month estimate provided is larger than the maximum number of available hosts in the subnet assigned. The host estimates should always be equal to or less than the maximum number of hosts in the subnet. |
Number of hosts after 1 year is greater than number of hosts available for address |
The 1 year estimate provided is larger than the maximum number of available hosts in subnet assigned. The host estimates should always be equal to or less than the maximum number of hosts in the subnet. |
Date is not in expected YYYYMMDD format |
The date provided needs to be in the format YYYYMMDD, for example May 2, 2001 would be 20010502. |
Failed date verification for address |
The date provided is not valid. Check the date for factors such as leap years and typing errors. |
Date is in the future for address |
The date the assignment was made is in the future. Use the date the assignment was actually made. |
Please choose NO, PART or YES for connect |
The connect field in the infrastructure and network-plan field can only have the following reserved words NO, YES, PART. |
Max value should be X |
The correct maximum number of hosts available in the subnet mask provided. |
No hosts field found |
The host estimates field was not given. |
Connectivity must be one of PEERING-POINT, SERVICE-PROVIDER or OTHER |
The connectivity field can only accept the following reserved words in this format in separate lines.
Example:
Connectivity: PEERING-POINT
Connectivity: SERVICE-PROVIDER |
Incorrect cust-network line |
The cust-network line provided is not in the correct format. |
Incomplete cust-network line |
The cust-network line provided does not include all of the required fields. |
Invalid syntax |
The syntax for the attribute is invalid. |
Invalid syntax for mask |
The syntax for the subnet mask is invalid. |
Invalid syntax for host estimates |
The host estimates provided need to be an integer. |
Invalid syntax for subnet estimates |
The host estimates provided need to be an integer. |
The nic-hdl failed verification |
The nic handle provided is not in the APNIC database. |
Invalid Admin Contact Handles entered. Please use Person Template (NIC Handle) format |
Please use the Person Template format. Example:
KX9-AP |
Invalid syntax for Technical Contact attribute |
Please use the Person Template format. Example:
KX9-AP |
Maintainer object has not been entered |
A valid maintainer object needs to be entered in this field. |
X is not a valid APNIC account name |
A valid APNIC account name needs to be provided. |
Incomplete line (infrastructure) |
The infrastructure line provided does not include all of the required fields. |
Incomplete line (network-plan) |
The network-plan line provided does not include all of the required fields. |
Location has not been entered |
At least one location needs to be provided when you choose 'YES' for cable bootstrap criteria. |
Make has not been entered |
At least one make must be provided when you choose 'YES' for cable bootstrap criteria. |
Model has not been entered |
At least one model must be provided when you choose 'YES' for cable bootstrap criteria. |
Quantity has not been entered |
At least one quantity entry must be provided when you choose 'YES' for cable bootstrap criteria. |
Equipment list has not been entered. |
At least one equipment entry must be provided when you choose 'YES' for cable bootstrap criteria. |
Conn-provider must not be blank |
You must complete the connection provider filed. |