In order to assure and control the quality of the services' rendered, is important the establishment of an alarm management system for clients, so that the service operates 24/7, being capable of taking a decision, based in the incidence and the customer's contract. The most elemental operation is to generate a message notice.
InterHost has established a security system that monitors final services seen from the external network. Those services have a clear correspondence with its protocol
IP Access
It is a matter of verifying that a machine is Internet accessible. Every 5 minutes, 10 ICMP (ping) packages are sent to 2 seconds intervals. The operation is interrupted at the moment when an answer is received. If to the end of the 10 intents no answer is obtained, an alarm is generated.
Web service
It is a matter of verifying that a Web server is attending petitions. Every 5 minutes a connection to the indicated Web server is tried. If the connection is not established, 5 consecutive intents will follow at intervals of 5 seconds. If the connection is established, the main page will be requested, and is verified that the status returned by the server is that of "correct operation", otherwise, an alarm is generated. If after the 5 intents the connection is not established, the alarm will go off.
Secure Web service
It is a matter of verifying that a secure WEB server returns pages correctly. Every 5 minutes a connection to the indicated Web server is tried. If the connection is not established, 5 consecutive intents will follow at intervals of 5 seconds. If the connection is established, an initial HELO will be sent as the beginning of a negotiation. If there is no answer, an alarm will be generated.
Relay mail service
It is a matter of verifying that a SMTP mail server responds to connections. Every 5 minutes a connection to the indicated SMTP server is tried. If the connection is not established, will try 5 consecutive times at 5 seconds' intervals. If the connection is established, the heading delivered by the connection service is analyzed and checks if the code delivered corresponds to "available service". Otherwise, an alarm goes off. If after 5 intents there is no connection, an alarm is generated.
Telnet service
It is a matter of verifying that a Telnet server is attending petitions. Every 5 minutes a connection to the indicated Telnet server is tried. If no connection is established, will try 5 consecutive times at intervals of 5 seconds. If the connection is established, available service is considered, otherwise an alarm is generated. If after the fifth intent no connection is available, the alarm goes off.
FTP service
It is a matter of verifying that an FTP server attends petitions. Every 5 minutes a connection to the indicated FTP server will be tried. If a connection is not established, will try 5 consecutive times at 5 seconds intervals. If the connection is established, the header delivered by the connection service is analyzed and is verified that the code delivered corresponds to "available service". Otherwise, an alarm is generated. If by the fifth intent no connection is obtained, an alarm will go off.
Special check up services at server
If the previous methods do not satisfy the needs of the client, they can be sophisticated, given that its establishment mechanism allows any degree of complexity. The habitual methodology is that the client, or InterHost at customer's request, develops a procedure that will carry out the verifications considered more opportune. Such procedure will be available in a determined port with the connection's permission (based on IP address) that will permit its integration in the general mechanism of monitoring, alarms and control of quality established by InterHost's Technical Directors.