System information

5-2 Endurance FTvirtual Server Administrator’s Guide
Monitoring and Managing Faults
Because the Endurance Configuration is fault tolerant, when a fault occurs (for example, a failed
network adapter), the Endurance FTvirtual Server continues operating. Even though the
Configuration is still operational, any failure to a faulted component’s redundant counterpart
affects the server’s availability.
To return the Endurance Configuration to a fully fault tolerant state, you need to complete some
repair procedures. Repairs involve several steps. The actions taken depend on the type of fault
that occurs. In general, the process includes:
• Diagnosing Faults
• Isolating Faults
• Correcting Faults
You can also set up various system management agents as an additional way of receiving fault
notifications. For example, the Endurance implementation of SNMP enables you to view
management data and receive notification of state changes from the SNMP trap mechanism.
You can use SNMP along with other, third-party products to obtain a complete view of the state
of your virtual server’s viability and performance.
Setting Up Management Agents
The Endurance FTvirtual Server is compatible with many third-party management agents and
tools, such as Fujitsu’s ServerView. To set up and use any third-party tools, refer to the third-
party tool’s documentation. As with applications, modification of the tools is not necessary to
run them on a Endurance Configuration.
Reconfiguring Port Numbers
The Endurance System Management Service uses port number 2809 for communication with
client programs. On either of the Endurance CoServers and/or the FTvirtual Server you can
reconfigure the port number if another application running on one of your Endurance
components uses port 2809. Also, because the CoServer and FTvirtual Server need not have the
same port number configured, you only need to reconfigure the component that has the port
number conflict.