STONEBEAT RELEASE NOTES WebCluster 2.5 Build 2549 Service Pack 8-4

Transcription

1 STONEBEAT RELEASE NOTES WebCluster 2.5 Build 2549 Service Pack 8-4 April 4, 2004 Stonesoft Corporation Itälahdenkatu 22 A FIN HELSINKI FINLAND

2 Copyright Stonesoft Corporation All Rights reserved. This product and related documentation are protected by copyright and distributed under licensing restricting their use, copying, distribution, and decompilation. No part of this product or related documentation may be reproduced in any form or by any means without written authorization of Stonesoft Corporation. All right, title, and interest in to the Product shall remain with Stonesoft and its licensors. The information in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Stonesoft Corporation does not warrant that this document is free of errors. TRADEMARKS StoneBeat is a registered trademark of Stonesoft Corporation. WebCluster is a trademark of Stonesoft Corporation. Sun, Solaris, Java, iplanet and JRE are trademarks or registered trademarks of Sun Microsystems, Inc. HP-UX is a registered trademark of Hewlett-Packard Company. Microsoft, Windows, Windows NT, Microsoft IIS, Microsoft Internet Information Server and Windows 95 are either trademarks or registered trademarks of Microsoft Corporation. AIX is a registered trademark of International Business Machines Corporation. Cisco and Catalyst are registered trademarks of Cisco Systems, Inc. Linux is a registered trademark of Linus Torvalds. Red Hat is a registered trademark of Red Hat, Inc. Any other trademarks referenced in this document are the property of their respective owners. Stonesoft Corporation Itälahdenkatu 22 A FIN HELSINKI FINLAND Tel: Fax:

3 Contents System Requirements...1 StoneBeat WebCluster for Linux...3 Compatibility...3 Network Interface Cards...3 Changes since WebCluster 2.5 Build 2544 Service Pack Changes since WebCluster 2.5 Build 2544 Service Pack Changes since WebCluster 2.5 Build 2541 Service Pack Changes since WebCluster 2.5 Build 2539 Service Pack Changes since WebCluster 2.5 Build 2537 Service Pack Changes since WebCluster 2.5 Build 2535 Service Pack Changes since WebCluster 2.5 Build Changes since WebCluster 2.0 Build 2060 Service Pack Changes since WebCluster 2.0 Build Changes since WebCluster 2.0 Build Known Issues...6 Installation...6 i

4

5 System Requirements Operating Systems Network Media Network Interfaces Web servers DNS servers Cache servers Switches StoneBeat WebCluster supports the following operating systems and versions: Solaris 8 SPARC in 32-bit mode and 64-bit mode. Solaris 9 SPARC in 64-bit mode. Red Hat Linux 8.0 and 9.0 Red Hat Enterprise Linux 3.0 Windows 2000 US English version with SP2 and SP3 StoneBeat WebCluster operates with Fast Ethernet and Gigabit Ethernet interfaces: Fast Ethernet, type 100BASE-TX Gigabit Ethernet, type 1000BASE-SX Each web server machine must have at least two physical network interfaces: Heartbeat protocol interface Operative interface(s) Optionally, an additional heartbeat interface and a separate control interface. A dedicated LAN is required for the heartbeat traffic. StoneBeat WebCluster has been tested with the following web servers: Apache on Solaris and Linux Sun One Web Server on Solaris StoneBeat WebCluster works with all application level HTTP servers StoneBeat WebCluster has been tested with the following DNS servers: Bind on Solaris and Linux StoneBeat WebCluster has been tested with the following cache servers: Squid on Solaris and Linux StoneBeat WebCluster can be connected to most switches that support static multicast groups or IGMP snooping. In other cases, the web server machines must be connected to a hub or a full duplex repeater. StoneBeat WebCluster has been tested with the following switches using unicast MAC addresses: Cisco Catalyst 2900 and 3500 Series XL StoneBeat WebCluster has been tested with the following switches using multicast MAC addresses: Cisco Catalyst 2900 and 3500 series XL Cisco Catalyst 5000 and 5500 series using static multicast groups Cisco Catalyst 6000 and 6500 series using static multicast groups Cisco Catalyst 8500 series using a bridge group 1

6 Routers License BayStack 350 using IGMP snooping 3Com SuperStack II Switch 3300 XM using IGMP snooping 3Com SuperStack 3 Switch 4400 using IGMP snooping 3Com CoreBuilder 3500 using IGMP snooping, routing requires a dedicated VLAN for servers to avoid flooding multicast frames HP ProCurve 2424M using static multicast groups and IGMP snooping Nortel Passport 1200 with image version 2.1. It is necessary to manually associate the multicast MAC address to the ports were the WebCluster nodes are attached. This configuration also ensures that no other ports in the same VLAN will be flooded by the multicast traffic IBM 8277 Nways Ethernet RouteSwitch using static port groups. Multicast flooding is quite CPU consuming task for the IBM 8277 switch. This may cause performance problems under heavy traffic load. Define the port groups to contain the needed ports only. Alcatel Omnistack 5024 with software release GA or later using VLANs for multicasting Alcatel Omnistack 4024 with software release GA or later using VLANs for multicasting Alcatel Omnistack OS-ESM100 with software release GA or later using VLANs for multicasting. Usage of multicast MAC addresses requires that the routers, servers and workstations connected to the same LAN as the web server machines allow address resolution to multicast MAC addresses. Multicast MAC addresses have been tested with network components running the following operating systems: Cisco IOS, requires static ARP entries Nokia IPSO 3.3, multicast ARP resolution enabled in Voyager Alcatel Omnicore 5022 with software release 3.3.1r20 or later, requires static ARP entries Alcatel Omnicore 5010 with software release 3.3.1r20 or later, requires static ARP entries Sun Solaris Windows 95, Windows NT and Windows 2000 HP-UX AIX Linux Be sure to use a StoneBeat WebCluster license string. StoneBeat WebCluster does not work with a license string for some other StoneBeat product. 2

7 StoneBeat WebCluster for Linux Compatibility StoneBeat WebCluster 2.5 Build 2549 Service Pack 8-4 has been tested with the following kernel versions: Red Hat Linux 8.0: and smp Red Hat Linux 9.0: and smp Red Hat Enterprise EL, ELsmp, EL, ELsmp, EL and ELsmp Network Interface Cards StoneBeat WebCluster 2.5 works with most of the Ethernet 10/100/1000Mb cards. Please see known issues section for information about non working NICs. Cards have been tested that use one of the following NIC drivers: tulip, eepro100, 3c59x, 3c90x, e100, e1000, eepro100, tg3 and bcm57xx. Changes since WebCluster 2.5 Build 2544 Service Pack 8-1 The following changes were made since WebCluster 2.5 Service Pack 8-1 Kernel update Support for new kernels added Changes since WebCluster 2.5 Build 2544 Service Pack 8 The following changes were made since WebCluster 2.5 Service Pack 8 Kernel update Support for new kernels added FullCluster module FullCluster Module (sbfcd) accepts commands also after system time is changed more than few seconds back or forward Streams Kernel Heartbeat channel failure messages are also printed Driver Test subsystem WebCluster tester (sbfc-tester) does not crash if logical operators are used Web Tool The Web Tool now uses OpenSSL 0.9.6m and apache with modssl Changes since WebCluster 2.5 Build 2541 Service Pack 6 The following changes were made since WebCluster 2.5 Service Pack 6 Operating WebCluster supports now Red Hat Enterprise Linux 3 System Kernel Update Support for new kernels added 3

8 Changes since WebCluster 2.5 Build 2539 Service Pack 5 The following changes were made since WebCluster 2.5 Service Pack 5 Operating WebCluster supports now Red Hat Linux 9.0. System Kernel Update Support for new kernels added Changes since WebCluster 2.5 Build 2537 Service Pack 3 The following changes were made since WebCluster 2.5 Service Pack 3 FullCluster The FullCluster Module now uses OpenSSL 0.9.6k. Module Web The Web Tool now uses apache and OpenSSL 0.9.6k Cluster Protocol The Cluster Protocol allows more than one node online after heartbeat has been re-established. Package File permissions should be 770 on Linux. Installation Changes since WebCluster 2.5 Build 2535 Service Pack 1 The following changes were made since WebCluster 2.5 Build 2535 Service Pack 1: Operating System Kernel Update Test Subsystem Module Web Tool Red Hat 8.0 support added. Support for new kernels added The networkinterface-linkstatus now uses eth-tool API if the NIC driver supports it. The WebCluster Module now uses OpenSSL 0.9.6j The Web Tool does copy evaluation certificates to correct location. Changes since WebCluster 2.5 Build 2532 The following changes were made since WebCluster 2.5 build 2532 Test subsystem Problem with very long service names in service running test solved. Kernel update Support for new kernels added Changes since WebCluster 2.0 Build 2060 Service Pack 1 The following changes were made since WebCluster 2.0 build 2060 service pack 1 Combining Products StoneBeat WebCluster includes now all the functionalities of StoneBeat DNSCluster and StoneBeat CacheCluster. 4

9 Operating system Nodes Test subsystem Web Red Hat 7.3 support added. Clustering supports up to 32 nodes. The Test Subsystem can now recover the node automatically to online state after a successful testing period. The Web GUI can manage multiple Cluster sites. Changes since WebCluster 2.0 Build 2060 The following changes were made since WebCluster 2.0 Build 2060: Operating systems Caldera Open Linux support added. Red Hat 7.2 support added. Changes since WebCluster 2.0 Build 2045 The following changes were made since WebCluster 2.0 Build 2045: Web sbfcconfig WebCluster Module Test Subsystem The Web GUI can be configured to use secure (https) connections The Web GUI checks license validity. The Web GUI can generate monitor-only certificates. The Web GUI uses alias IP address for the cluster IP address if available. The Web GUI can be used to configure secondary heartbeat interface. Nodes can be rebooted individually. The Web GUI can be used to remove StoneBeat virtual interfaces. It is now possible to configure clustering and starting mode with the sbfcconfig command line configuration tool. Using the rsa-key-period option in the node.conf file can change secret key exchange between WebCluster Module and StoneBeat GUI or sbfc. The automatic switching of a node from the standby to the online state can be delayed with the boot-delay option in the node.conf. Support for RSA certificates generated by an external CA. The WebCluster Module now reports different exit codes if it is configured incorrectly. Use the $SBFCHOME/bin/exit_codes utility program to get more information about the exit code. The WebCluster Module now reports improved error messages to the system log if it is configured incorrectly. The first test round can be delayed using the boot-delay tester parameter in the checklist configuration file. The next test round after reconfiguration can be delayed using the restartdelay parameter in the checklist configuration file. 5

10 The next test round after a state transition can be delayed using the statusdelay parameter in the checklist. Load Balancing Filter Fragmented IP packets are load balanced when protocol is not TCP or UDP, or port-mode is set to off in the filter.conf configuration file. Known Issues Please note the following known issues: Interface sbfcconfig Connections in fail-over Reinstalling The linuxconf utility does not include the device name in the alias interface configuration file and the alias interface is not initialized. Workaround: Add the device name to the interface configuration file, for example, add DEVICE="eth1:0" to the /etc/sysconfig/networkscripts/ifcfg-eth1:0 file. An interface can be inadvertently defined twice using the sbfcconfig configuration tool, for example, to be a protocol interface and a control interface. In this case the last definition takes effect and the first definition is ignored. An interface must be defined only once. If the same interface is used for both, protocol and control, it must be defined as a protocol interface. In case one web server node fails, the connections established to the failed web server need to be re-established by clicking the refresh button in the web browser If you uninstall StoneBeat WebCluster and reinstall it later on to the same directory, you will need to reconfigure all the interfaces using sbfcconfig. Even though sbfcconfig shows the interface information from the previous installation, you will have to reconfigure each interface before putting the node online. Installation Note! WebCluster 2.5 Build 2549 Service Pack 8-4 can be installed as fresh install or as an upgrade to StoneBeat WebCluster 2.0 Service Pack 1, WebCluster 2.5 Build 2532, Build 2535 Service Pack 1, Build 2537 Service Pack 3, Build 2539 Service Pack 5, Build 2541 Service Pack 6 or Build 2544 Service Pack 8 or Build 2545 Service Pack 8-1. On Red Hat 9.0 you need to have perl-x.y.z package installed before you install StoneBeat WebCluster. Extract the gzipped tar package to the /tmp directory Change to the /tmp/ sp08-04/ directory. To install the packages: - Run rpm i SBFC*.rpm - Start configuration as described in StoneBeat WebCluster Manual To upgrade: - Run rpm F --force SBFCbase*.rpm and rpm -F SBFCdrv*.rpm SBFCmod*.rpm SBFCconf*.rpm commands. Reboot the machine. 6