Medias Mediatrix 1204, Reference Manual

Page: 76 / 390

Chapter 3 - Web Interface – Management Configuration File Download
50 Mediatrix 1204
Error Handling
The following configuration file fetching service error sources are divided in three types depending on the
transfer protocol: common errors (Table 35), TFTP errors (Table 36) and HTTP errors (Table 37). The error
cause and the unit behaviour are also described.
Table 36: Configuration File Fetching Error Handling
Error Type Cause Behaviour
Common Error Handling
Invalid file format The file format is not valid. Send a syslog warning message including the
file location/name with the transfer server
address:
The fetched configuration file “XXX”,
from server “XXX”, has an invalid
format.
No recorded settings applied.
Empty file Committing an empty file. Send a syslog warning message including the
file location/name with the transfer server
address:
The fetched configuration file “XXX”,
from server “XXX”, is empty.
Invalid file content The file contains invalid
characters. Allowed characters
are ASCII codes 10 (LF),
13(CR), and 32 to 126. Send a syslog warning message including the
file location/name, the transfer server address
and the invalid character (ASCII code):
The fetched configuration file “XXX”,
from server “XXX”, has an invalid
character “ASCII code XXX”.
No recorded settings applied.
Invalid transfer server
address The server address is not valid. Send a syslog warning message including the
transfer server address:
No configuration file is fetched
because the server host “XXX” is
invalid.
Set sysAdminDownloadConfigFileStatus to fail .
File size too big Downloading a file with a size
exceeding 512000 bytes. Send a syslog warning message including the
file location/name, the transfer server address,
the file size and the maximum allowed size:
The fetched configuration file “XXX”,
from server “XXX”, has a size “XXX
bytes” that exceeds the maximum
allowed size “XXX bytes”.
Set sysAdminDownloadConfigFileStatus to fail .
Invalid encryption The configuration file cannot be
decrypted. A badly encrypted
file is detected if the header or
the padding is invalid. Send a syslog warning message including the
file location/name and the transfer server
address:
The fetched configuration file \”%s\”,
from server \”%s\”, can not be
decrypted.