![]() LifeKeeper requires Inter-Process Communication (IPC) semaphores and IPC shared memory. ![]() SIOS has migrated to the use of the ip command and away from the ifconfig command (for more information, see the IPv6 Known Issue). If there is a concern that there may be a consistency problem, the system administrator should unmount the file system by taking it out of service and run xfs_check(8) and xfs_repair(8) to resolve any issues. The XFS file system does not use the fsck utility to check and fix a file system but instead relies on mount to replay the log. on SLES 11 on IBM x3550 x86_64 architecture and RHEL5.5 64-bit. This feature was tested by SIOS Technology Corp. on Red Hat EL 5.5 64-bit, Red Hat EL 5.6 32-bit and Red Hat EL 6 + softdog. The feature was tested by SIOS Technology Corp. LifeKeeper supports the watchdog feature. The MIB file describing the LifeKeeper traps can be found at /opt/LifeKeeper/include/LifeKeeper-MIB.txt. See the lk_configsnmp(8) man page for more information about configuring this capability. LifeKeeper can be configured to issue SNMP traps describing the events that are occurring within the LifeKeeper cluster. See also lklin00002100 under Restrictions or Known Issues for additional information. However, many of the messages displayed by the LifeKeeper GUI come from the LifeKeeper core, so localization of the GUI will provide only a partial solution for users until the core software is fully localized. The LifeKeeper GUI can be localized by creating locale-specific versions of the Java property files, although currently only the English version is fully localized. LifeKeeper for Linux v5.2 and later does support wide/multi-byte characters in resource and tag names but does not include native language message support. ![]() Refer to the vendor-specific hardware and software configuration information to determine the maximum supported cluster size. This includes items such as the storage interconnect and operating system or storage software limitations. There are many factors other than LifeKeeper, however, that can affect the number of servers supported in a cluster. LifeKeeper supports large cluster configurations, up to 32 servers. The Host IDs, along with the Activation ID(s) provided with your software, are used to obtain license keys from the SIOS Technology Corp. The installation support script installs a Licensing Utilities package that obtains and displays the Host ID of your server. A license key is required for the LifeKeeper core software, as well as for each separately packaged LifeKeeper recovery kit. This applies to both physical and virtual servers. LifeKeeper requires unique runtime license keys for each server.
0 Comments
Leave a Reply. |