This section explains registration of the error page response file necessary when using an HTTP error message response as an optional function of server failure monitoring of the server load balancer function.
The tenant user creates the error message file based on the business system to configure, and the infrastructure administrator registers this file in the NS Appliance.
Figure C.4 Registration Flow of Error Page Files
Registration of Error Page Files
Store the error page file on the NS appliance.
Store the error page file of the NS appliance by transferring it to the NS appliance
Store the error page file on the FTP server beforehand.
Execute the following command:
copy src_uri [ username name [ password password ] ] [ dst_filename ]
Specify the file on the FTP server as the copy source, in order to copy it to the NS appliance.
ftp://IPv4 address of the FTP server/directory/filename
Specify the login ID for the FTP server using a character string containing between 1 and 64 characters.
Specify the password for the login ID for the FTP server using a character string containing between 1 and 64 characters.
Specify the file name as "XXX-slb.html".
Specify an arbitrary name.
Information
Create an error page file based on the following points:
Specify a character string containing between 10 and 25 characters, including the extension.
The characters which can be used for the file name are A to Z, a to z, 0 to 9, and !#$%'`()_-~^\{}:+..
The character of the file name is case-sensitive.
Add "-slb.html" to the end of the file name.
Example: error-slb.html
Error page files must be HTML files.
A sample HTML of an error page file is shown below.
<HTML><HEAD><TITLE>Notice</TITLE></HEAD> <BODY> We apologize for any inconvenience. <BR> The server is currently congested, or undergoing periodic maintenance. <BR> For this reason, access is currently not possible. <BR> Sorry, but please wait a while and then try again. <BR> <BR> Periodic maintenance is performed every Monday, from 3:00 am to 5:00 am. <BR> </BODY> </HTML>