200 All Good
Server Error Messages found on Status Log
401 Error – Unauthorized: Access is denied due to invalid credentials.
Check INI file – incorrect configuration of
auth_user
auth_password
401 Error – ‘EiRegisterParty’ failed Check INI file – incorrect configuration
Check in Status that the failing URL is the correct URL for the VTN.
It could also be the INI file was accidentally uploaded to the 1.0 directory: /nvram/sxcd/dras_client.ini instead of 2.0a/b directory: /nvram/gridlink/dras_client.ini
404 Not Found Error means that the webpage you were trying to reach could not be found on the server. It is a Client-side Error which means that either the page has been removed or moved and the URL was not changed accordingly, or that you typed in the URL incorrectly.
Check INI file – incorrect configuration of
service_hostname
service_port
service_prefix
406 Bad Schema Something in the payload received from the VTN is wrong
450 Bad Mod Number
452 Bad VTN ID The expected VTN ID doesn’t agree with that specified in the INI File
460 Bad market Context
480 Default Error with Status Description
Comm Status
The comm_status register reflects certain errors by numeric representation when connecting to a VTN. This is also reflected in the Alarm Panel on the Home page.
-1 is a failure to connect at all. This indicates an incorrect URL for the VTN in the dras_client.ini file. The failing URL should be shown in the logs on the status page.
-2 is an XML parse failure
-3 is non-200 response code from the server usually an authentication error meaning bad cert, user name or password when used
225 General failure for 1.0 & 2.0a Top Node. This could be caused from an incorrect URL, the VTN not responding to a request within certain time parameters, or an error in the parse of the payload.