5.0.1 Release Notes (PDF 344 KB)

5.0.1 Release Notes (PDF 344 KB)
Resonate
Central Dispatch™
Version 5.0.3
Release Notes
Copyright © 2001-2006 Resonate, Inc. All rights reserved.
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
Resonate Incorporated and its licensors retain all ownership rights to the Central Dispatch computer
programs (hereinafter collectively called Resonate Software) and their documentation. Use of Resonate
Software is governed by the license agreement accompanying your original media.
Information in this book is subject to change without notice. Companies, names, and data used in examples
herein are fictitious unless otherwise noted.
Resonate is a registered trademark of Resonate, Inc. The Resonate logo, Resonate Central Dispatch, and
Resource-based Scheduling are trademarks of Resonate, Inc. Sun, Sun Microsystems, Solaris, and Java
are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC
International, Inc. in the United States and other countries. Products bearing SPARC trademarks are based
upon an architecture developed by Sun Microsystems, Inc. UNIX is a registered trademark of the Open
Group. RS/6000, Power2, and PowerPC are trademarks, and AIX and IBM are registered trademarks of
International Business Machines Corporation. HP-UX and Hewlett Packard are registered trademarks of
Hewlett Packard Company. Microsoft is a registered trademark, and Windows, Windows 95, Window 98,
Windows NT, and Windows 2000 are trademarks of Microsoft Corporation. Red Hat is a registered
trademark of Red Hat Software, Inc. Linux is a registered trademark of Linus Torvalds. Adobe and Acrobat
are registered trademarks of Adobe Systems Incorporated. Intel and Pentium are registered trademarks of
Intel Corporation in the U.S. and other countries. HP is a registered trademark of HP Computer Corporation.
3COM is a registered trademark of 3COM Corporation. Adaptec is a registered trademark of
Adaptec, Inc. HP is a registered trademark of Hewlett-Packard Company.
All other brand product names mentioned herein may be the trademarks or registered trademarks of their
respective companies.
Resource-based Scheduling™ technology is protected under U.S. Patent 5,774,660.
Version:
Date:
Part Number:
5.0.3
Oct 13, 2006
82-0002-B
2 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
Table of Contents
1 Features and Enhancements __________________________________________________________ 7
1.1 New Features in CD 5.0.3__________________________________________________________ 7
1.2 Supported Operating Systems & Adapters ___________________________________________ 7
1.2.1 Support for Red Hat Linux ES/AS 4.0 64 bit ________________________________________ 7
1.2.1.1 Kernel Version ___________________________________________________________ 7
1.2.1.2 Network Adapters _________________________________________________________ 7
1.2.2 Support for Solaris 10 x86 ______________________________________________________ 7
1.2.3 Support for ISA-2004 Firewall (Windows 2003 SP1) __________________________________ 7
1.2.3.1 ISA firewall configuration for Central Dispatch 4.2.4 and later _______________________ 7
1.2.3.2 Configuration of Firewall for VPN access _______________________________________ 8
1.2.4 Windows 2003 & SP1 (64 bit) Intel Xeon ___________________________________________ 8
1.2.4.1 Installation issues _________________________________________________________ 8
1.2.4.2 Platform & Editions ________________________________________________________ 8
1.2.4.3 Network Adapter Cards ____________________________________________________ 8
1.2.5 Windows 2003 & SP1 (64 bit) AMD Opteron ________________________________________ 9
1.2.5.1 Installation issues _________________________________________________________ 9
1.2.5.2 Platform & Editions ________________________________________________________ 9
1.2.6.3 Network Adapter Cards ____________________________________________________ 9
1.2.7 VMware Workstation 5 & GSX 3.0 Servers (32 bit) ___________________________________ 9
1.2.8 Red Hat Linux ES/AS 4.0 (32 bit) ________________________________________________ 10
1.2.8.1 Kernel Version __________________________________________________________ 10
1.2.8.2 Network Adapters ________________________________________________________ 10
1.2.9 Solaris 10 (32/64 bit) _________________________________________________________ 10
1.2.10 Red Hat Linux ES/AS 3.0 (64 bit)_______________________________________________ 10
1.2.10.1 Kernel Versions ________________________________________________________ 10
1.2.10.2 Network Adapters _______________________________________________________ 10
1.2.11 IBM AIX 5.1, 5.2 & 5.3 (64 bit) _________________________________________________ 11
1.2.11.1 Supported Maintenance Levels ____________________________________________ 11
1.2.11.2 Network Adapters _______________________________________________________ 11
1.2.12 HP-Compaq DL 360/380 G3/G4 Adapter Windows 2003 (32 bit) ______________________ 11
1.2.13 Red Hat Linux AS & ES 3.0 (32 bit) _____________________________________________ 11
1.2.13.1 Kernel Versions ________________________________________________________ 11
1.2.13.2 Network Adapters _______________________________________________________ 11
1.2.14 HP-UX 11.11 (64 bit) (CD 4.2.x only)The following Network Adapter Interface cards are
supported. ______________________________________________________________________ 11
1.2.15 HP-UX 11.11 (32 bit) (CD 4.2.x only) ____________________________________________ 11
1.2.16 Windows 2003 (32 bit) _______________________________________________________ 12
1.2.16.1 Editions _______________________________________________________________ 12
1.2.16.2 Network Adapters _______________________________________________________ 12
1.2.17 Red Hat Linux AS 2.1 (32 bit) (CD 4.2.x only) _____________________________________ 12
1.2.18 Red Hat Linux 9.0 (32 bit) (CD 4.2.x only) ________________________________________ 12
1.2.18.1 Kernel Versions ________________________________________________________ 12
1.2.18.2 Network Adapters _______________________________________________________ 12
1.2.19 Windows 2000 Server & AS (32 bit) (CD 4.2.x only) ________________________________ 13
1.2.19.1 Supported Service Packs _________________________________________________ 13
1.2.20 AIX 5.1 & 5.2 (32 bit) (CD 4.2.x only) ____________________________________________ 13
1.2.20.1 Supported Maintenance Levels ____________________________________________ 13
1.2.20.2 Network Adapter Cards __________________________________________________ 13
1.2.21 Solaris 8 & 9 (32/64 bit) (CD 4.2.x only) _________________________________________ 13
1.3 Supported Browsers ____________________________________________________________ 13
2 Cautions and Warnings ______________________________________________________________ 15
2.1 Browser and JVM Requirements for Real-time Monitoring _____________________________ 15
2.2 Changes to your operating system ________________________________________________ 15
2.3 Balancing Multiple FTP sessions __________________________________________________ 16
2.4 Correct Version of CDAction______________________________________________________ 16
3. Hardware and Software Support ______________________________________________________ 17
3 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
3.1 Central Dispatch Release Qualification _____________________________________________ 17
3.2 Disk space requirements_________________________________________________________ 17
3.3 RAM memory Requirements ______________________________________________________ 17
3.4 Patches & Maintenance Packs ____________________________________________________ 18
3.4.1 Patches for Solaris ___________________________________________________________ 18
3.5 Supported NICs ________________________________________________________________ 18
3.5.1 Certified NICs _______________________________________________________________ 18
3.5.2 Certified fail-over NICs Teamed _________________________________________________ 19
3.6 Hardware issues________________________________________________________________
3.6.1 Node occasionally stops responding with 3Com NIC_________________________________
3.6.2 3COM failover NIC option______________________________________________________
3.6.3 3COM NIC driver TCAITDI.SYS monitor __________________________________________
3.6.4 Alteon NICs and Gigabit Ethernet _______________________________________________
3.6.5 Network interface does not reconnect ____________________________________________
3.6.6 Solaris ERI/Gigabit Ethernet NICs _______________________________________________
3.6.7 Multiple NICs and a split site ___________________________________________________
19
19
19
19
19
19
19
20
4. Installation Options_________________________________________________________________ 21
4.1 Solaris Installation Options_______________________________________________________
4.1.1 Command Line ______________________________________________________________
4.1.2 Solaris 8, 9 and 10 kernels _____________________________________________________
4.1.3 Installing Central Dispatch on Solaris_____________________________________________
4.1.4 Reusing a node in a different site________________________________________________
4.1.5 Enable IP Forwarding on Solaris ________________________________________________
21
21
21
22
22
22
4.2 Linux Installation Options ________________________________________________________
4.2.1 Command Line ______________________________________________________________
4.2.2 Linux post-installation checks___________________________________________________
4.2.3 Checking network masks on Linux_______________________________________________
4.2.4 Silent install of components requires reboot _______________________________________
4.2.5 Mounting the CD-ROM file system on Linux _______________________________________
4.2.6 Unmounting the CD-ROM filesystem on Linux______________________________________
4.2.7 Installing Central Dispatch on Linux ______________________________________________
4.2.8 Reusing a node in a different site________________________________________________
4.2.9 Enable IP Forwarding _________________________________________________________
22
22
23
23
23
23
23
24
24
24
4.3 Windows installation Options _____________________________________________________
4.3.1 Performing installation ________________________________________________________
4.3.2 Silent installation on Windows __________________________________________________
4.3.3 Reinstall to reconfigure Windows network parameters _______________________________
4.3.4 Uninstaller under Windows 2003 ________________________________________________
24
24
24
25
25
5 Known Issues and Workarounds ______________________________________________________ 26
5.1 Site Setup and Operations Issues _________________________________________________
5.1.1 Central Dispatch Site is not available_____________________________________________
5.1.2 Flushing the RXP Cache of Schedulers ___________________________________________
5.1.3 Unexpected Scheduler fail back and Connection Resets _____________________________
5.1.4 Large Number of VIPs and Multiple Schedulers ____________________________________
5.1.5 Shadow Scheduling, Persistence, and Multiple failures_______________________________
5.1.6 Clients must run outside of site _________________________________________________
26
26
26
27
27
27
27
5.2 GUI Issues_____________________________________________________________________
5.2.1 No Warning for 10-day Expiration of CD License____________________________________
5.2.2 Privilege to Add/Delete Nodes Revoked __________________________________________
5.2.3 Unable to Zoom Real time Charts _______________________________________________
5.2.4 Historical Data Display ________________________________________________________
5.2.5 Validation of IP Persistency is missing____________________________________________
5.2.6 Fail-back to primary scheduler NOT functioning ____________________________________
5.2.7 Configuration Issues with Soft/Hard Disable _______________________________________
5.2.8 Intermittent Display of CD site components ________________________________________
5.2.9 Secure Access to CD 5.0 ______________________________________________________
5.2.10 Multiple Administrators _______________________________________________________
27
27
27
27
28
28
28
28
28
28
28
4 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
5.2.11 Re-enabling a Administratively Disabled Node ____________________________________ 28
5.2.12 Dithered Display with HTTPS with Firefox 1.5.0.4 __________________________________ 28
5.3 Scheduling Rules issues _________________________________________________________
5.3.1 Ping of VIPs Requires ICMP rule ________________________________________________
5.3.2 Firewalls and ICMP traffic______________________________________________________
5.3.3 FTP traffic and multiple session-based firewalls ____________________________________
5.3.4 Port mapping not supported with MAT routing ______________________________________
5.3.5 Bandwidth Allocation Denial protection ___________________________________________
5.3.6 Deleting all Scheduling Rules___________________________________________________
5.3.7 Generic IP Rules do not support FTP ____________________________________________
5.3.8 Non-persistent rule creates persistent connections __________________________________
5.3.9 Loss of Firewall Connectivity Not Detected ________________________________________
5.3.10 UDP Connection Timeout Value Not Absolute ____________________________________
5.3.11 FTP Rules Not Supported for Affiliated Servers____________________________________
5.3.12 Mistaken Assignment of MAT Affiliated servers ____________________________________
5.3.13 False Message, “Under SYN flood attack” ________________________________________
5.3.14 Large Configuration File Requires Environment Variable ____________________________
5.3.15 Web Server Keep-alive Feature and IP Persistence ________________________________
5.3.16 Port-independent persistent sessions refused _____________________________________
5.3.17 Scheduling Based on CGI parameters___________________________________________
5.3.18 No Warnings Possible for Invalid Scheduling Rules ________________________________
5.3.19 Custom Data Scheduling Rule Unchecked Protocol ________________________________
5.3.20 Central Dispatch Cannot Know that the UDP Server is Down _________________________
5.3.21 Source IP of ICMP Response Packet from Affiliated Server __________________________
5.3.22 Multiple FTP Connections May not Follow Rules___________________________________
5.3.23 Custom Data Rules Issues ____________________________________________________
5.3.23.1 Persistent sessions not based on ranges or masks _____________________________
5.3.23.2 Expression field ‘end of offset’ incorrect ______________________________________
5.3.23.3 Incomplete Requests Cause Connection Hang ________________________________
5.3.24 UDP Replies use Server IP address, not VIP address_______________________________
5.3.25 Round-robin for Site setup and Resource-based Scheduling Rule _____________________
5.3.26 Cannot Add a Scheduling Rule with Port _________________________________________
28
28
28
29
29
29
29
29
29
29
30
30
30
30
30
31
31
31
31
31
31
31
31
32
32
32
32
32
33
33
5.4 Outbound Rules issues __________________________________________________________
5.4.1 Evaluation of packets affects Redirect ____________________________________________
5.4.2 Redirect of UDP requests lost if timeout = 0 _______________________________________
5.4.3 Redirect fails for segmented requests ____________________________________________
5.4.4 Rule fails because of retransmitted packets________________________________________
5.4.5 Segmented pattern fails to create persistence Session _______________________________
5.4.6 Cookie persistence and Outbound Rules__________________________________________
5.4.7 Route tracing for persistent Sessions_____________________________________________
5.4.8 TCP & IP Persistency Outbound Direction_________________________________________
5.4.9 Incorrect Duplication of Outbound Rules __________________________________________
33
33
33
33
33
33
34
34
34
34
5.5 Command Line Interfaces issues __________________________________________________
5.5.1 No statistics for MAT mode Affiliated servers_______________________________________
5.5.2 No hits for persistence rules ____________________________________________________
5.5.3 Primary server weight field missing from rule_______________________________________
5.5.4 Failover Server Weight Blank in Web GUI _________________________________________
5.5.5 Starting/Stopping CD site with CDAction __________________________________________
34
34
34
34
34
34
5.6 Solaris Specific Issues __________________________________________________________
5.6.1 Site Restart Script Not Installed _________________________________________________
5.6.2 Solaris VIP limit _____________________________________________________________
5.6.3 Support for Solaris 10 Local Zones ______________________________________________
5.6.4 Conflict with Hardware Checksum _______________________________________________
35
35
35
35
35
5.7 Linux Specific Issues____________________________________________________________
5.7.1 Heavy load causes Apache to halt _______________________________________________
5.7.2 MAT Mode for Affiliated servers not supported _____________________________________
5.7.3 Stopping CD Agent sometimes results in an error message ___________________________
5.7.4 Non-TCP traffic with Affiliated Servers ____________________________________________
5.7.5 Red Hat Linux Package Required to Install Central Dispatch __________________________
5.7.6 Failure to Add Large Rules File _________________________________________________
5.7.7 “Hard/Soft” Disable for IP Custom Data Rule_______________________________________
35
35
35
35
36
36
36
36
5 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
5.7.8 Outbound Custom Data Rule for UDP protocol _____________________________________
5.7.9 “Eth0: memory shortage….”: Error for UDP with Timeout 0____________________________
5.7.10 No Response from UDP requests on Affiliated Servers______________________________
5.7.11 Re-authentication Required to Load RXP Driver for SSL ____________________________
5.7.12 Deletion or Conversion of Master Agent Node in a CD site ___________________________
5.7.13 Version of Agent when importing 3.3.x rule into CD 5.0 _____________________________
5.7.14 Maximum Number of Rules Loadable on RXP_____________________________________
5.7.15 Custom data rule for IP Address/Netmask combination______________________________
5.7.16 Incorrect Status Node after stopping CD Agent ____________________________________
36
36
36
37
37
37
37
37
37
5.8 Windows specific issues _________________________________________________________
5.8.1 SYN-bomb protection _________________________________________________________
5.8.2 Installer allows duplicate port numbers ___________________________________________
5.8.3 Site restart script not installed __________________________________________________
5.8.4 Installation and the Performance Monitor__________________________________________
5.8.4.1 Event log shows rxpperf.dll error messages____________________________________
5.8.4.2 Workaround ____________________________________________________________
5.8.5 Network Load Balancing not supported ___________________________________________
5.8.6 Large Persistence Tables______________________________________________________
5.8.7 Multicasting applications need physical IP addresses ________________________________
5.8.8 Multiple network cards require proper routing ______________________________________
5.8.9 Do not manually uninstall Resonate RXP Driver ____________________________________
5.8.10 Switch to Affiliated server _____________________________________________________
5.8.11 Memory error message: ‘Can’t get memory’ ______________________________________
5.8.12 Log files not readable with Notepad _____________________________________________
5.8.13 Deleted node returns ________________________________________________________
5.8.14 RXP binds to HP NC3134 Teamed Card after install________________________________
5.8.14.1 Installation_____________________________________________________________
5.8.14.2 Fail over ______________________________________________________________
5.8.14.3 Uninstall Issue _________________________________________________________
5.8.15 CD Adapter connectivity during fail over _________________________________________
5.8.16 Warning for Unsigned RXP Driver (Windows 2003 only) _____________________________
5.8.17 “Automatic Metric” Settings (Windows 2003 only) __________________________________
5.8.18 Warning for remote installation (Windows 2003) ___________________________________
37
37
38
38
38
38
38
39
39
39
39
39
40
40
40
40
40
40
41
41
41
41
41
42
5.9 Migration from 3.x and 4.0________________________________________________________
5.9.1 Concurrent Usage of Different GUI ______________________________________________
5.9.2 Support for multiple shadow schedulers __________________________________________
5.9.3 Removing rule after upgrade ___________________________________________________
5.9.4 CD 5.0 Rule with partially upgraded site __________________________________________
5.9.5 Shadow Scheduling to backup scheduler _________________________________________
5.9.6 Limitations with downgrading ___________________________________________________
5.9.10 Migration of 4.x outbound rules ________________________________________________
5.9.11 Incorrect HTTP Rule Statistics _________________________________________________
5.9.12 Support for Physical Service __________________________________________________
42
42
42
42
42
42
42
43
43
43
6 External Issues_____________________________________________________________________ 44
6.1 TCP/IP services can fail if Agent fails to start ________________________________________ 44
7 Online Help ________________________________________________________________________ 44
6 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
1 Features and Enhancements
1.1 New Features in CD 5.0.3
This latest version adds
• Load balancing using on Windows 2003 processor queue length
• Support for new Linux 2.6.9 kernel 37 & 40
1.2 Supported Operating Systems & Adapters
The features described here represent significant improvements to Central Dispatch with
the release of version 5.0.3
1.2.1 Support for Red Hat Linux ES/AS 4.0 64 bit
The following Kernel versions are supported.
1.2.1.1 Kernel Version
Kernel
Version
2.6.9-34
2.6.9-37
2.6.9-40
2.4.9*
Other
Support
Fully supported
Compatible (warning message during installation)
Not supported and not installable
1.2.1.2 Network Adapters
The following Network Adapter Interface cards are supported.
Type
100 M
100 M
1G
1G
1G
Ethernet Adapters
IntelPro 100 T IP Storage Adapter V 2.0
3-COM EtherLink 10/100 PCI 3C905c-TX/TX-M “Tornado
Intel Pro 1000 T IP Storage Adapter V 2.0
Broadcom NetXtreme 10/100/1000Base-T 570x Adapter PCI 2.2/X
Intel Pro 1000 XT for Dell PowerEdge 4x00
1.2.2 Support for Solaris 10 x86
Solaris 10 x86 is supported on AMD Opteron processor
Type
100 M
1G
1G
Ethernet Adapters
SUN FastEthernet 10/100BaseT PCI Adapter 2.0 w/MII
SUN Gigabit Ethernet PCI 2.0/3.0 (GBE/S) Driver: ge (GEM Ethernet Driver (B) v2.29
BGE – GLDV3 interface with Solaris 10 patch 118833-10 or higher
1.2.3 Support for ISA-2004 Firewall (Windows 2003 SP1)
1.2.3.1 ISA firewall configuration for Central Dispatch 4.2.4 and later
1.
2.
3.
4.
------Configuration of Firewall for Central Dispatch Protocol -------On ISA Server GUI, right side, Toolbox. tab
Select Protocols
Select User Defined
Select New
7 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
5.
6.
7.
8.
9.
10.
11.
12.
Name the protocol appropriately under General Tab
Select Parameters tab
Under Primary Connections, Add the following values
Protocol Num...173, Protocol type...IP-Level, Direction...Send Receive
Add Similar Values for 171, 175, 177, 178
Now Select Firewall Policy on left side
Create new access rule
Select all protocols created.
------- Disabling IP Spoofing Detection ---------------13. Select the windows registry HKLM of the machine running CD Scheduler and ISA
firewall
14. Under HKLM\System\Current Control Set\Services\FwEng\Parameters, Adds
the following DWORD DisableSpoofDetection and 1
Note: The IP Spoofing detection has to be disabled in the case the scheduler runs on the
same server as the ISA 2004 firewall. The step 13 & 14 describe the process for disabling
IP spoofing detection.
1.2.3.2 Configuration of Firewall for VPN access
The following mode are currently supported for VPN access
• VPN IPSec tunneling
• PPTP
The allow load balancing of traffic through VPN the VPN Client Access option has to be
disabled on the ISA firewall.
1.1.4 Windows 2003 & SP1 (64 bi
1.2.4 Windows 2003 & SP1 (64 bit) Intel Xeon
1.2.4.1 Installation issues
The installation of Central Dispatch requires disabling the verification for signed driver.
Please refer to the installation guide.
1.2.4.2 Platform & Editions
The following platforms are supported: Intel Xeon
Editions
Intel 32 bit
AMD 64/Opteron
Intel 64/Xeon
UP:
SMP:
Web
Server
Enterprise
Data Center
4.0.2.7
4.0.2.7
4.2.1
4.2.1
UP & SMP
UP & SMP
Support for UniProcessor servers
Support for Symmetrical MultiProcessor servers
Not Supported
Not Supported
Not Supported
Not Supported
1.2.4.3 Network Adapter Cards
The following Network Adapter Interface cards are supported.
Type
100 M
100 M
100 M
1G
1G
1G
1G
Ethernet Adapters
IBM 10/100Base-TX Server Adapter PCI v2.1
IBM 10/100Base-TX Dual Port Server Adapter PCI v2.1
IntelPro 100 T IP Storage Adapter V 2.0
Intel Pro 1000 T IP Storage Adapter V 2.0
Broadcom NetXtreme 10/100/1000 SX Fiber 5700
Broadcom NetXtreme 10/100/1000Base-T 570x family Adapter PCI 2.2, PCI-X
Intel Pro 1000 XT for Dell PowerEdge 4x00
Note: NVidia Network Adapter cards are not supported
8 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
1.2.5 Windows 2003 & SP1 (64 bit) AMD Opteron
1.2.5.1 Installation issues
The installation of Central Dispatch requires disabling the verification for signed driver.
Please refer to the installation guide.
1.2.5.2 Platform & Editions
The following platforms are supported: AMD Opteron
Web
Server
Enterprise
Editions
Intel 32 bit
Not Supported
4.0.2.7
4.0.2.7
AMD Opteron
UP & SMP
UP & SMP
UP:
Support for UniProcessor servers
SMP: Support for Symmetrical MultiProcessor servers
Data Center
Not Supported
Not Supported
1.2.6.3 Network Adapter Cards
The following Network Adapter Interface cards are supported.
Type
100 M
100 M
100 M
1G
1G
1G
1G
Ethernet Adapters
IBM 10/100Base-TX Server Adapter PCI v2.1
IBM 10/100Base-TX Dual Port Server Adapter PCI v2.1
IntelPro 100 T IP Storage Adapter V 2.0
Intel Pro 1000 T IP Storage Adapter V 2.0
Broadcom NetXtreme 10/100/1000 SX Fiber 5700
Broadcom NetXtreme 10/100/1000Base-T 570x family Adapter PCI 2.2, PCI-X
Intel Pro 1000 XT for Dell PowerEdge 4x00
Note: NVidia Network Adapter cards are not supported
1.2.7 VMware Workstation 5 & GSX 3.0 Servers (32 bit)
Central Dispatch supports version 5 of VMware workstation and version 3.0 of GSX
servers running Windows 2003 and Red Hat Linux ES/AS 3.0 & 4.0 in 32-bit mode.
The Network adapter cards supported on Windows 2003 & Red Hat Linux 3.0/4.0 are
also supported through the VMware virtual machine.
Type
Ethernet Adapters
100 M
100 M
1G
1G
1G
1G
IntelPro 100 T IP Storage Adapter V 2.0
3-COM EtherLink 10/100 PCI 3C905c-TX/TX-M “Tornado
Intel Pro 1000 T IP Storage Adapter V 2.0
Broadcom NetXtreme 10/100/1000Base-T 570x Adapter PCI 2.2/X
Intel Pro 1000 XT for Dell PowerEdge 4x00
HP-Compaq DL 360/380 G3/G4
100 M
100 M
100 M
100 M
1G
1G
100 M
1G
100 M
100 M
IBM 10/100Base-TX Server Adapter PCI v2.1
IBM 10/100Base-TX Dual Port Server Adapter PCI v2.1
HP 10/100Base Fast Ethernet Server Adapter NC3134 Dual Port PCI v2.2
HP 10/100Base-TX NC3131 Fast Ethernet NIC 64 PCI PCI V2.1
Broadcom NetXtreme 10/100/1000 SX Fiber 5700
Broadcom NetXtreme 10/100/1000Base-T 570x family Adapter PCI 2.2, PCI-X
HP ProLiant DL360 G3 Xeon based Embedded 7781 PCI-X 10/100/100 WOL
HP 10/100/1000Base NC7770 PCI-X Server Adapter Copper-wire
3COM 100Base-SX Fiber 3C996-SX PCI-X
3COM Etherlink XL 100 PCI Model 3c905B-TX
9 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
1.2.8 Red Hat Linux ES/AS 4.0 (32 bit)
The following Kernel versions are supported.
1.2.8.1 Kernel Version
Kernel
Version
2.6.9-5.EL
2.6.9-37.EL
2.6.9-40.EL
2.4.9*
Other
Support
Fully supported
Compatible (warning message)
Not supported and not installable
1.2.8.2 Network Adapters
The following Network Adapter Interface cards are supported.
Type
100 M
100 M
1G
1G
1G
1G
Ethernet Adapters
IntelPro 100 T IP Storage Adapter V 2.0
3-COM EtherLink 10/100 PCI 3C905c-TX/TX-M “Tornado
Intel Pro 1000 T IP Storage Adapter V 2.0
Broadcom NetXtreme 10/100/1000Base-T 570x Adapter PCI 2.2/X
Intel Pro 1000 XT for Dell PowerEdge 4x00
HP-Compaq DL 360/380 G3/G4
1.2.9 Solaris 10 (32/64 bit)
Central Dispatch can be deployed only in a Solaris 10 global zone. However Central
Dispatch agent is not compatible when deployed on a non-global zone.
The following Network Adapter Interface cards are supported.
Type
100 M
1G
Ethernet Adapters
SUN FastEthernet 10/100BaseT PCI Adapter 2.0 w/MII
SUN Gigabit Ethernet PCI 2.0/3.0 (GBE/S) Driver: ge (GEM Ethernet Driver (B) v2.29
1.2.10 Red Hat Linux ES/AS 3.0 (64 bit)
Dispatch Manager and CDAction are running on JRE 1.5, which is installed as part of
Central Dispatch.
1.2.10.1 Kernel Versions
The following kernel versions are supported.
Kernel Version
Support
2.4.21-4.EL*
Fully supported
2.4.21*
Compatible (warning message)
Other
Not supported and not installable
1.2.10.2 Network Adapters
The following Network Adapter Interface cards are supported.
Type
10 of 44 pages
Ethernet Adapters
October 2006
Resonate Inc
100 M
100 M
1G
1G
Resonate Central Dispatch 5.0.3 Release Notes
IntelPro 100 T IP Storage Adapter V 2.0
3-COM EtherLink 10/100 PCI 3C905c-TX/TX-M “Tornado
Intel Pro 1000 T IP Storage Adapter V 2.0 (E1000 V 5.7.2 Linux Base Driver 5.7.2)
Broadcom NetXtreme 10/100/1000Base-T 570x Adapter PCI 2.2/X
1.2.11 IBM AIX 5.1, 5.2 & 5.3 (64 bit)
1.2.11.1 Supported Maintenance Levels
•
•
Maintenance Level 6 is recommended for AIX 5.1
Maintenance Level 4 is recommended for AIX 5.2
1.2.11.2 Network Adapters
The following Network Adapter Interface cards are supported.
Type
1G
1G
1G
1G
100 M
100 M
Ethernet Adapters
IBM Ethernet 5700 SX PCI 1.0
IBM Ethernet 5701 TX PCI 1.0
IBM Ethernet 5706 SX PCI-X 2 port
IBM Ethernet 5707 TX - UTP
IBM PCI 2.0 (4962)
IBM PCI 2.0 Universal 4 port (4961)
1.2.12 HP-Compaq DL 360/380 G3/G4 Adapter Windows 2003 (32 bit)
The teamed gigabit adapter board DL 360/380 is supported under Windows 2003
1.2.13 Red Hat Linux AS & ES 3.0 (32 bit)
1.2.13.1 Kernel Versions
Kernel Version
2.4.21-4.EL*
2.4.21*
Other
Support
Fully supported
Compatible (warning message)
Not supported and not installable
1.2.13.2 Network Adapters
The following Network Adapter Interface cards are supported
Type
100 M
100 M
1G
1G
Ethernet Adapters
3-COM EtherLink 100 PCI 3C905-TX “Boomerang”
3-COM EtherLink 10/100 PCI 3C905c-TX/TX-M “Tornado
Broadcom NetXtreme 10/100/1000 SX Fiber 5700
Broadcom NetXtreme 10/100/1000Base-T 570x Adapter PCI 2.2/X
1.2.14 HP-UX 11.11 (64 bit) (CD 4.2.x only)The following Network Adapter
Interface cards are supported.
Type
100 M
1G
100 M
Ethernet Adapters
HP J3515A HSC 10/100Base-TX D-Class 1 Port
HP PCS 10/1000Base-TX
HP A5230A/B5509BA PCI 10/100Base-TX
1.2.15 HP-UX 11.11 (32 bit) (CD 4.2.x only)
The following Network Adapter Interface card is supported.
11 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
Type
Ethernet Adapters
100 M
HP J3515A HSC 10/100Base-TX D-Class 1 Port
1.2.16 Windows 2003 (32 bit)
1.2.16.1 Editions
Editions
32 bit
64 bit
Web
Server
Not Supported
UP & SMP
Enterprise
Data Center
UP & SMP
Not Supported
Not Supported
Not Supported
UP: Support for UniProcessor SMP: Support for Symmetrical MultiProcessor
1.2.16.2 Network Adapters
The following Network Adapter Interface cards are supported.
Type
100 M
100 M
100 M
100 M
1G
1G
100 M
1G
100 M
100 M
Ethernet Adapters
IBM 10/100Base-TX Server Adapter PCI v2.1
IBM 10/100Base-TX Dual Port Server Adapter PCI v2.1
HP 10/100Base Fast Ethernet Server Adapter NC3134 Dual Port PCI v2.2
HP 10/100Base-TX NC3131 Fast Ethernet NIC 64 PCI PCI V2.1
Broadcom NetXtreme 10/100/1000 SX Fiber 5700
Broadcom NetXtreme 10/100/1000Base-T 570x family Adapter PCI 2.2, PCI-X
HP ProLiant DL360 G3 Xeon based Embedded 7781 PCI-X 10/100/100 WOL
HP 10/100/1000Base NC7770 PCI-X Server Adapter Copper-wire
3COM 100Base-SX Fiber 3C996-SX PCI-X
3COM Etherlink XL 100 PCI Model 3c905B-TX
1.2.17 Red Hat Linux AS 2.1 (32 bit) (CD 4.2.x only)
The following Network Adapter Interface cards are supported.
Type
Ethernet Adapters
100 M 3-COM Fast EtherLink XL 100 PCI 3C905b-TX “Cyclone
100 M 3-COM EtherLink 10/100 PCI 3C905c-TX/TX-M “Tornado
1.2.18 Red Hat Linux 9.0 (32 bit) (CD 4.2.x only)
1.2.18.1 Kernel Versions
The following Kernel versions are supported.
Kernel Version
2.4.20-8
2.4.20*
Other
Support
Fully supported
Compatible (warning message)
Not supported or allowed
1.2.18.2 Network Adapters
The following Network Adapter Interface cards are supported.
Type
Ethernet Adapters
100 M 3-COM EtherLink 100 PCI 3C905-TX “Boomerang”
12 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
100 M 3-COM Fast EtherLink XL 100 PCI 3C905b-TX “Cyclone
100 M 3-COM EtherLink 10/100 PCI 3C905c-TX/TX-M “Tornado
1.2.19 Windows 2000 Server & AS (32 bit) (CD 4.2.x only)
1.2.19.1 Supported Service Packs
CD 5.x support Windows 2000 Server, Advanced Server Service Packs 1, 2, 3, 4.
1.2.19.2 Network Adapter Cards
The support for the following Network Adapter Cards are currently supported in W2K
Type
100 M
100 M
100 M
100 M
100 M/Teamed
1G
1G
100 M
1G
100 M
Ethernet Adapters
IBM 10/100Base-TX Server Adapter PCI v2.1
IBM 10/100Base-TX Dual Port Server Adapter PCI v2.1
HP 10/100Base Fast Ethernet Server Adapter NC3134 Dual Port PCI v2.2
HP 10/100Base-TX NC3131 Fast Ethernet NIC 64 PCI PCI V2.1
HP 10/100Base Fast Ethernet Server Adapter Teamed NC3134 PCI v2.2
Broadcom NetXtreme 10/100/1000 SX Fiber 5700
Broadcom NetXtreme 10/100/1000Base-T 570x family Adapter PCI 2.2, PCI-X
HP ProLiant DL360 G3 Xeon based Embedded 7781 PCI-X 10/100/100 WOL
HP 10/100/1000Base NC7770 PCI-X Server Adapter Copper-wire
3COM 100Base-SX Fiber 3C996-SX PCI-X
1.2.20 AIX 5.1 & 5.2 (32 bit) (CD 4.2.x only)
1.2.20.1 Supported Maintenance Levels
•
•
AIX 5.1 maintenance level 6
AIX 5.2 maintenance level 4
1.2.20.2 Network Adapter Cards
Central Dispatch 4.1 supports AIX 5.1 and 5.2 with the following Network Adapter
Cards in 32 bit mode
IBM Gigabit Ethernet 5700 SX PCI-X V1.0 (Fiber)
IBM Gigabit Ethernet 5701 1000Base-TX PCI-X v1.0 (UTP)
IBM Gigabit Ethernet 5706 SX PCI-X 2 port
IBM Gigabit Ethernet 5707 1000Base-TX (UTP)
IBM 10/100Base NIC PCI v2.0 (4962)
IBM 10/100Base NIC PCI v2.0 Universal 4 Port (4961)
1.2.21 Solaris 8 & 9 (32/64 bit) (CD 4.2.x only)
Type
100 M
1G
Ethernet Adapters
SUN FastEthernet 10/100BaseT PCI Adapter 2.0 w/MII
SUN Gigabit Ethernet PCI 2.0/3.0 (GBE/S) Driver: ge (GEM Ethernet Driver (B) v2.29
1.3 Supported Browsers
The following browsers are supported in this current version
• IE 5.5
• IE 6.0, 6.0 SP1 & SP2
• Firefox 1.5.0.4 & 1.5.0.6
13 of 44 pages
October 2006
Resonate Inc
14 of 44 pages
Resonate Central Dispatch 5.0.3 Release Notes
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
2 Cautions and Warnings
Pay close attention to the information in this chapter. It warns about potentially serious
problems that you want to avoid.
2.1 Browser and JVM Requirements for Real-time Monitoring
The following browsers are compatible with Central Dispatch 5.0.2
• Internet Explorer 5.5
• Internet Explorer 6.0
• Firefox 1.5 and higher
In order to run the real time monitoring console in Central Dispatch 5.0.2 GUI, IE requires
java runtime version 1.5.0 installed as a plug-in to the browser. The user can check the
option to integrate it to the required browsers.
To test if JRE plug-in is installed on browser
IE Explorer
$CurrentDirectory\jview
Firefox:
$CurrentDirectory\java –version
To install JVM plug-in for IExplorer browser
http://www
To Install JVM plug-in for Firefox browser
http://plugins.netscape.com/moreinfo.adp?PID=10047
2.2 Changes to your operating system
If you make any major changes to the operating systems of your hosts running the Central
15 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
Dispatch software then you must uninstall the software and reinstall it after the changes
have been made. The install program inspects your operating system and automatically
installs the Central Dispatch software that is compatible with your operating system. Major
changes can include (but are not restricted to) modifications to a UNIX kernel, adding a
new service pack to a Windows-based host or changing the mode of the operating system
such as switching between Solaris 32-bit and Solaris 64-bit mode.
2.3 Balancing Multiple FTP sessions
Central Dispatch supports a subset of configurations for balancing the load of Multiple FTP
sessions from the same client by setting the variable RES_FTP_FULL_LOAD_BALANCE
to 1. This variable has to be set and unset for the configuration of the agent running on both
the scheduler and the FTP server.
Note: Setting this variable to 1 (for load balancing of multiple FTP sessions from a
single client) or 0 (for disabling the feature) for the agent running either only on the
scheduler or the FTP servers, will not work.
2.4 Correct Version of CDAction
CDAction 3.x (resp. 4.x) should not be used after a 3.x (resp. 4.x) site is upgraded to 5.0.
CDAction 5.0 should be used instead.
16 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
3. Hardware and Software Support
3.1 Central Dispatch Release Qualification
An installation of the Central Dispatch node component automatically installs the
CDAgent and Reporter Agent. The following table shows supported operating systems by
installation component:
Component
Central Dispatch Node
CDAction
CDController
Reporter Data Collector
Solaris 7/8
(32 bit)
Solaris 9 , 10
(32/64)
Yes
Yes
Yes
Yes
W2K Server
& ES
(32)
Win
2003
(32/64)
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Yes
RH Linux 7.2/9.0
AS 2.1
AS/ES 3.0
AS/ES 4.0
Yes
Yes
3.2 Disk space requirements
Each computer used for your Central Dispatch site does not require the installation of all
components. For instance, only one CDController is required for a site. The components
and their requirements are:
Component
Java
Node
IBM
Red Hat
SUN
HP
Microsoft
AIX
5.1/5.2/5.3
(32/64 bit)
Linux
7.2/9.0
AS 2.1
AS/ES 3.0
(32/64bit)
AS/ES 4.0
Solaris 7, 8
(32 bit)
Solaris 9
(32/64 bit)
Solaris 10
HP-UX
11.11
(32/64bit)
W2K SP1,2,3 & 4
NT SP5, SP6a
Win 2003 SP1(32 and
64 bit)
2.66 MB
0.62 MB
CDAction
CDController
Reporter Data
Collector
Documentation
During
installation
1.68 MB
27.17 MB
2.59 MB
3.10 MB
0.60 MB
6.32 MB
0.60 MB
4 MB
4MB
4 MB
4 MB
19.5 MB
5.5 +2 MB on system
to avoid paging
0.5 MB
14.5 MB + 100
KB/instance
14.55MB
+100KB/instance
4 MB
20 MB in %TEMP%
3.3 RAM memory Requirements
Component
Node
Scheduler
17 of 44 pages
IBM
Red Hat
SUN
HP
Microsoft
AIX
5.1/5.2
(32/64 bit)
Linux
7.2/9.0
AS 2.1
ES/AS 3.0
(32/64 bit)
ES/AS 4.0
256 Mb
256 Mb
Solaris 7, 8
(32 bit)
Solaris 9
(32/64 bit)
Solaris 10
HP-UX
11.11
(32/64bit)
NT SP5, SP6a
W2k SP1,2,3 & 4
Win 2003 SP1
(32/64 bit)
256 Mb
256 Mb
256 Mb
384 Mb
256 Mb
256 Mb
256 Mb
256 Mb
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
3.4 Patches & Maintenance Packs
3.4.1 Patches for Solaris
Before installing Central Dispatch on a Solaris system, retrieve and install the Sun patches
listed for your operating system. For each base patch, such as 106040, install at least the
level listed, 106040-11, for instance, or any later level. Required for Solaris 7:
Solaris Version
Patches
7
8
9
10
106541-34
117350-4
117171-05
All
If you have a newer patch that includes and replaces one of the patches listed above, you
may need to revise the Solaris installation script. Call Resonate Technical Support for
details.
3.5 Supported NICs
3.5.1 Certified NICs
The supported NICs include:
• 3COM® 3C905 Etherlink 100 PCI TX “Boomerang”
• 3COM3C905B Fast Etherlink XL 100 PCI TX “Cyclone”
• 3COM3C905C 10/100 PCI TX/TX-M “Tornado”
• 3COM 3C900B-TPOXL PCI
• 3COM 3C985B-SX Gigabit EtherLink® Server NIC
• Adaptec® Quartet64 DuraLAN Fast Ethernet NIC ANA62044
• Alteon® ACEnic PCI Adapter, 10/100Base-T (512kB)
• Broadcom NetXtreme 1000Base-SX 5700
• Broadcom NetXtreme 1000Base-T 570x Adapters PCI-X & PCI 2.0
• HP® NC3131 Fast Ethernet NIC
• HP NC3163 Fast Ethernet NIC
• HP NC6133 Gigabit Module
• HP 10/100Base Fast Ethernet Server Adapter NC3134 dual port
• HP 101/00Base-TX NC3131 Fast Ethernet NIC-64 PCI
• HP J3515A HSC 10/100Base-TX D-Class 1 Port for HP-UX 11i
• HP PCI 100/1000Base-TX for HP-UX 11.x
• HP A5230A/B5509BA PCI 10/100Base-TX for HP-UX 11i
• HP ProLiant DL 360/380 G3 embedded 7781 PCI
• HP Proliant DL 360/380 G4 gigabits embedded 7781 PCI-X
• IBM 10/100 Mbps default NIC
• IBM Netfinity 4000 (Intel card)
• IBM 10/100Base NIC PCI ve 2.0 - 4962
• IBM 10/100Base NIC pCI v2.0 Universal 4 Port 4961
• IBM Gigabit Ethernet 5700 SX PCI-X v1.0 (Fiber)
• IBM Gigabit Ethernet 5701 1000Base-TX PCI-X v1.0 (UTP)
• IBM Gigabit Ethernet 5706 SX PCI-X 2 port
• IBM Gigabit Ethernet 5705 1000Base-TX (UTP)
• IBM 10/100Base-TX Server Adapter
• IBM 10/100Base-TX Dual Port Server Adapter
• Intel 21040 (DEC tulip)-based Adapter
• Intel EtherExpress 82557-based Adapter
• Intel PRO/100 S Intelligent Server (i960)
• Intel Pro/100 T Storage Adapter V 2.0
18 of 44 pages
October 2006
Resonate Inc
•
•
•
•
•
•
Resonate Central Dispatch 5.0.3 Release Notes
Intel PRO/1000 T IP Storage Adapter V 2.0
Intel PRO/1000 XT Dell PowerEdge
NetGear® FA310TX
NetGear GA620 PCI Gigabit
SUN FastEthernet 10/100BaseT PCI Adapter 2.0 w/MII
SUN gigabit Ethernet PCI 2.0/3.0 (GBE/S) with ge and bge drivers
3.5.2 Certified fail-over NICs Teamed
•
•
•
•
•
•
•
•
Adaptec Quartet64 DuraLAN Fast Ethernet NIC ANA62044
HP NC3131 Fast Ethernet NIC
HP NC3163 Fast Ethernet NIC
Intel PRO/100 S Server
Solaris Quad Fast Ethernet
HP NC3134 Fast Ethernet Server in Teamed Mode
HP DL 360 G3 & G4 in teamed mode
HP DL 380 G3 & G4 in teamed mode
3.6 Hardware issues
3.6.1 Node occasionally stops responding with 3Com NIC
This is a 3Com-specific problem. It has been observed that, on occasion, if a host using a
3Com 3C59x NIC experiences a heavy load, the installed Central Dispatch node
component will stop responding for a few seconds and messages will be logged in the
/var/log/messages file.
3.6.2 3COM failover NIC option
3Com failover NICs using the “Dedicated IP address for Receive L/B” option with a
dedicated IP that is not the VIP for the Central Dispatch site prevents Central Dispatch
from advertising its VIPs and from responding to requests to the VIPs. To check the use
of or to disable the option, click Start, Settings, Control Panel, and the 3COM Dynamic
Access SW Server icon. Select Load Balancing/RXL Groups and the Properties
button. In the Properties display, the Dedicated IP address for Receive L/B check box
determines if the option is on (checked) or off (cleared).
3.6.3 3COM NIC driver TCAITDI.SYS monitor
Some drivers for 3COM NIC cards silently install monitor software. A monitoring module
named TCAITDI.SYS may lead to a blue screen condition. If the module is present on a
system, Resonate recommends disabling the module. From the Start button, go to
Settings, Control Panel, Devices. Set TCAITDI.SYS to disabled and reboot the
machine.
3.6.4 Alteon NICs and Gigabit Ethernet
The jumbo frame feature of Alteon NICs and switches is not supported by the gigabit
Ethernet feature of this release of Central Dispatch.
3.6.5 Network interface does not reconnect
Network interface drivers may not reconnect to the network following a media disconnect
or failure. Correct this problem by updating NIC to the latest available driver version.
3.6.6 Solaris ERI/Gigabit Ethernet NICs
To use the Solaris ERI Network Cards or Gigabit Ethernet NICs you must add a line to
19 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
the /etc/system file and then reboot the system. The line to add is:
set ip:dohwcksum=0
3.6.7 Multiple NICs and a split site
A split site happens when communication between Central Dispatch Schedulers is
interrupted (because of network problems, for instance) and both sides continue to
function as an active Central Dispatch site. If the split happens because a Scheduler with
multiple NICs loses communication through the NIC used by Central Dispatch, the
Scheduler can still communicate through the other NIC, elect its Agent as master Agent,
and function as a Central Dispatch site. The single node site may end up receiving all
requests for the site’s VIPs.
To guard against such problems with multi-NIC machines, you can use either of the
following strategies:
• Set the environment variable RES_NOTMASTER for the agent on that machine.
See the “Setting Central Dispatch environment variables” section of the “Site
Setup and Maintenance” chapter of the Resonate Central Dispatch User
Guide for details on setting variables.
• During installation, bind to only one NIC. The installation routine by default binds
to all NICs on a machine, but gives you the opportunity to bind to one or selected
NICs. However, to avoid split site use above option only. Since, it is
recommended to bind RXP to all NICs present on the host. Otherwise, that could
require modifications to the routing table on the host. i.e. The packets arrived on
NIC with RXP binding should be forwarded to the NIC with RXP binding only.
20 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
4. Installation Options
4.1 Solaris Installation Options
4.1.1 Command Line
Below is the updated command line parameter list for the UNIX installer.
Usage:
install-CD [options]
Options:
-h, H
-S
-P <path>
-N
-D <1|0>
Displays the option list
Do a silent installation (if used, must be the first option)
Install base path (if -S and no -P <path> then default)
Install the Node option (rxp, cdagent, and Reporter agent)
Flag for starting the [installed] Resonate Daemons:
1 = start
0 = don't start
-a <port> CD Agent port value (if -N and no -a, then default)
-b <port> Reporter Agent port (if -N and no -b, then default)
-n <user1> Administrator mode account (no default)
-o <user2> Monitor mode account (no default )
-A
Install CDAction
-C <N>
Install <N> instances of Reporter Data Collector(no default, use with -d
and -r)
-d <name1>:<name2>:...
Reporter Data collector names (no default)
-r <port1>:<port2>:...
Reporter Data Collector ports (defaults to last adapter port + 1)
-R <N>
Install <N> instances of CDController (no default, use with -c and -p )
-c <name1>:<name2>:...
CDController names (no default)
-p <port1>:<port2>:...
CDController ports (defaults to 2900 - (2900+n))
Examples:
# install-CD
# install-CD -h
# install-CD -D 1
# install-CD -N
# install-CD -N -a 2242 -n "dispadm" -o "dispmon"
# install-CD -S -N -M -R 1 -c TestAdapter -p 2900 -D 1 -n dispadm –o dispmon
# install-CD -S -N -M -R 2 -c Adapter_1:Adapter_2 -p 2900:2901 -C 2 –d
Collector1:Collector2 -r 2910:2911 -D 1 -n dispadm -o dispmon
4.1.2 Solaris 8, 9 and 10 kernels
On Solaris 8, Solaris 9, and Solaris 10 systems, the installation procedure checks the
eeprom for the reboot mode (32-bit kernel or 64-bit kernel) and the current running
mode. If the two match, the procedure begins an installation. If the two do not match,
the installation program asks you to resolve the conflict and restart the installation. A
Central Dispatch installation on a machine running in 32-bit mode is not functional in
64-bit mode and vice-versa.
The following example shows the command that checks on which kernel is current
21 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
and output from the command:
# isainfo –kv
Use the following command to set a Solaris 7, Solaris 8, or Solaris 9 system to
always boot with the 32-bit kernel:
# eeprom boot-file=kernel/unix
Use the following command to set a Solaris 7, Solaris 8, or Solaris 9 system to
always boot with the 64-bit kernel:
# eeprom boot-file=kernel/sparcv9/unix
4.1.3 Installing Central Dispatch on Solaris
The installable image for Central Dispatch is located in one of the following
directories:
For a remotely mounted CD-ROM Drive, /cdrom/<platform>/cd
For a locally mounted CD-ROM Drive, /cdrom/cdrom0/<platform>/cd
where <platform> is either Linux.
4.1.4 Reusing a node in a different site
Using the Central Dispatch uninstall procedure does not delete the Central Dispatch
configuration file. If a machine serving as a node in one Central Dispatch site, is
removed from the site, has Central Dispatch uninstalled, and later has Central
Dispatch re-installed for another site, the machine as a Central Dispatch node will still
use the configuration file from the original site. To completely uninstall Central
Dispatch, remove all Resonate directories or folders after the un-installation program.
4.1.5 Enable IP Forwarding on Solaris
In order for Central Dispatch to schedule traffic, the IP forwarding feature must be
enabled on the Schedulers for your site. By default, when you install the node
component, the installation process automatically enables IP forwarding. If IP
forwarding has been disabled after installation on a Scheduler host, you need to
manually re-enable it.
To enable IP forwarding on a Solaris system:
1. Logon to the Scheduler host.
2. From a command line prompt enter: # ndd –set /dev/ip ip_forwarding 1
4.2 Linux Installation Options
4.2.1 Command Line
Usage:
install-CD [options]
Options:
-h, H
-S
-P <path>
-N
-D <1|0>
-a <port>
-b <port>
22 of 44 pages
Displays the option list
Do a silent installation (if used, must be the first option)
Install base path (if -S and no -P <path> then default)
Install the Node option (rxp, cdagent, and Reporter agent)
Flag for starting the [installed] Resonate Daemons:
1 = start
0 = don't start
CD Agent port value (if -N and no -a, then default)
Reporter Agent port (if -N and no -b, then default)
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
-n <user1>
-o <user2>
-A
-C <N>
Administrator mode account (no default)
Monitor mode account (no default )
Install CDAction
Install <N> instances of Reporter Data Collector(no default, use with -d
and -r)
-d <name1>:<name2>:...
Reporter Data collector names (no default)
-r <port1>:<port2>:...
Reporter Data Collector ports (defaults to last adapter port + 1)
-R <N>
Install <N> instances of CDController (no default, use with -c and -p )
-c <name1>:<name2>:...
CDController names (no default)
-p <port1>:<port2>:...
CDController ports (defaults to 2900 - (2900+n))
4.2.2 Linux post-installation checks
Use the following command on Linux to check that the RXP module is installed:
lsmod | grep rxp
4.2.3 Checking network masks on Linux
On Linux systems, make sure the network interface configuration files and scripts or
the NIS/NIS+ database contain every network number/network mask pair used on
your network.
You can find the network configuration files and scripts in /etc/sysconfig/networkscripts.
4.2.4 Silent install of components requires reboot
After doing a silent install of either the SNMP agent or the node component, you must
reboot the machine. Silent install of any of the other Central Dispatch components or
combinations of components does not require a reboot as long as the SNMP agent
or node component are not included.
4.2.5 Mounting the CD-ROM file system on Linux
When using a local drive:
1. Log in as root.
2. Insert the Central Dispatch CD-ROM in the drive.
3. Type: # mount /dev/cdrom
The CD-ROM filesystem is now mounted onto /mnt/cdrom on the local host.
4.2.6 Unmounting the CD-ROM filesystem on Linux
When you are finished installing Resonate software, unmount the CD-ROM as
follows:
1. Change to a directory that is not on the CD-ROM. For example, to change to the
root directory enter the command: # cd /
2. Unmount the CD-ROM drive by entering the following command:
# umount /dev/cdrom
3. Remove the CD-ROM from the drive.
23 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
4.2.7 Installing Central Dispatch on Linux
The installable image for Central Dispatch is located in one of the following
directories:
For a remotely mounted CD-ROM Drive, /cdrom/<platform>/cd
For a locally mounted CD-ROM Drive, /cdrom/cdrom0/<platform>/cd
where <platform> is either Linux.
4.2.8 Reusing a node in a different site
Using the Central Dispatch uninstall procedure does not delete the Central Dispatch
configuration file. If a machine serving as a node in one Central Dispatch site, is
removed from the site, has Central Dispatch uninstalled, and later has Central
Dispatch re-installed for another site, the machine as a Central Dispatch node will still
use the configuration file from the original site. To completely uninstall Central
Dispatch, remove all Resonate directories or folders after the un-installation program.
4.2.9 Enable IP Forwarding
In order for Central Dispatch to schedule traffic, the IP forwarding feature must be
enabled on the Schedulers for your site. By default, when you install the node
component, the installation process automatically enables IP forwarding. If IP
forwarding has been disabled after installation on a Scheduler host, you need to
manually re-enable it.
To enable IP forwarding on a Linux system:
1. Logon to the Scheduler host.
2. From a command line prompt enter:
# echo 1 > /proc/sys/net/ipv4/ip_forward
4.3 Windows installation Options
4.3.1 Performing installation
The Resonate installation procedure for Windows recommends installing from the
Add/Remove Programs utility opened from Start, Settings, Control Panel on the
desktop. If that is not optimal for your site, the installation can be done from the My
Computer window through the CD-ROM icon or from a DOS command prompt.
However, if the machine has Terminal Services installed and set to Application server
mode, DO NOT install Resonate products from the My Computer window or from a
DOS command prompt. To check the setting or to set Terminal Services to Remote
administration mode, select Start, Settings, Control Panel, Add/Remove
Programs, Add/Remove Windows Components, Terminal Services, Next. Select
Remote administration mode to change the setting if needed.
4.3.2 Silent installation on Windows
The silent installation procedure does not work when installing from the “\cd” directory
of the CD-ROM. To do a silent installation of Central Dispatch:
• From the CD-ROM, copy the Windows2k directory to the target machine.
• In the Windows2k directory on the target machine, find the file
\cd\resonate_sample.dat.
• Change the file name to resonate.dat.
• Edit the file for your site’s installation parameters.
• Run ‘Setup’ from the same directory.
24 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
4.3.3 Reinstall to reconfigure Windows network parameters
Before you change any of the parameters affecting the network configuration of your
computer (either manually or by installing software that modifies network parameters
as part of its installation), uninstall Central Dispatch following the instructions in the
Resonate installation guide for the machine. Always reboot the machine after
uninstalling a Central Dispatch node.
After reconfiguring the network parameters, reinstall Central Dispatch. This ensures
that the configuration information required by Central Dispatch is correct and in effect
4.3.4 Uninstaller under Windows 2003
After removing the program from Add/Remove Programs, you need to manually
remove the RXP driver. This is due to a problem in the CD InstallShield installer
program.
The steps are
1. Go to Start -> Settings -> Network and Dial-up Connections
2. Right-click the 'Local Area Connection' and select 'Properties'
3. Highlight Resonate RXP Driver and click Uninstall button
4. Click Yes to restart the machine
25 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
5 Known Issues and Workarounds
The known issues and workarounds described in this chapter were discovered prior to
this release of Central Dispatch.
The issues described in this chapter are:
• Site setup and operations issues
• CDController issues
• Scheduling Rules issues
• Outbound Rules issues
• Command Line Interfaces issues
• Windows specific issues
• Linux specific issues
5.1 Site Setup and Operations Issues
5.1.1 Central Dispatch Site is not available
A Central Dispatch site can become unreachable even though all of the machines in
the site are available on one subnet or another.
The situation can occur when:
• The primary or backup Scheduler or both have 2 or more interfaces to subnets.
• The nodes (including Schedulers) were added to the site on one subnet.
• The VIPs for the site are on another subnet.
• The primary or backup Scheduler loses contact with the subnet used to add the
Scheduler to the site.
The site can end up with two primary Schedulers. If the one recognized by the network
switch or router is the one that cannot contact the nodes in the site, the site is
unreachable. The workarounds for this situation are:
• Fix the disconnection between the Scheduler and the subnet.
OR
• Stop the Central Dispatch Agent on the Scheduler that is disconnected from the
subnet.
With this workaround, the Central Dispatch site will recover immediately, but will not be
recognized by the network switch or router until the ARP cache entry for the
disconnected Scheduler times out and is replaced with an entry from the other
Scheduler.
5.1.2 Flushing the RXP Cache of Schedulers
The MAC addresses for all the servers in a Central Dispatch site are cached in the
RXP module of the Schedulers. If you do anything to change the MAC address of any
of the servers in the site (such as changing a NIC card on a Central Dispatch
Scheduler or changing a NIC card or modifying a route on a router used by Central
Dispatch) the Schedulers will not be able to transfer client connections to that server.
When this happens, you will observe that the number of hits per second on that server
is zero.To correct this, you must force the Schedulers to flush the cache and obtain the
updated MAC addresses. You can do this in either of the following ways:
a) Delete the server with the new MAC address from the site, then add the server back
into the site.
b) Reboot the Schedulers (first the primaries, then the backups). Because of automatic
Scheduler fail over, rebooting the primary Schedulers causes the backup Schedulers to
take over. Then, when you reboot the backup Schedulers, the primary Schedulers take
over again.
26 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
5.1.3 Unexpected Scheduler fail back and Connection Resets
In a two-node site, an unexpected Scheduler fail back can occur after a network
connection failure and recovery removes the Scheduler from a site and then returns it.
If the Scheduler wins as the master Agent node after it rejoins the site, and if a backup
Scheduler is the active Scheduler, the node rejoining the site can set off a Scheduler
fallback even if automatic Scheduler fail back is disabled. Also, if the master Agent on
the site is running on a server node, and failure of that node causes the Central
Dispatch Agent on the Scheduler to become the new master Agent, connections to the
Scheduler may be reset when the failed server node comes back online.
5.1.4 Large Number of VIPs and Multiple Schedulers
Sites that use more than 8 Schedulers are recommended to use no more than 256
VIPs. Users can utilize up to the maximum number of Schedulers (16) by lowering the
number of VIPs.
5.1.5 Shadow Scheduling, Persistence, and Multiple failures
Shadow Scheduling can lose persistence information after the sequence of events:
• The primary Scheduler fails and the backup Scheduler successfully takes over as
active Scheduler.
• the primary Scheduler returns to service and fail back successfully returns
persistence information to the primary as it becomes the active Scheduler.
• the primary Scheduler fails again and the failure happens before the Shadow
Scheduling synchronization interval expires, meaning that the complete
persistence table does not get re-synchronized to the backup Scheduler.
After the second failure of the primary Scheduler, the only persistence entries that the
backup Scheduler has will be session creation entries passed along through the kernel
for sessions started after the primary had resumed as active Scheduler. The full
persistence table, synchronized by Agents, will not be available on the (now acting as
active Scheduler) backup Scheduler.
5.1.6 Clients must run outside of site
If you run a client (such as a browser) on one of the server nodes of your site and try to
access one of your site’s VIPs, you will get a response only from the server node on
which the client is running. You will not get the expected Scheduling Rule traffic
management to the other server nodes of your site. If you are testing Scheduling Rule
functionality always run clients on machines outside of your site.
5.2 GUI Issues
5.2.1 No Warning for 10-day Expiration of CD License
A warning dialog box regarding expiration of CD license should pop up each time the
user logs in or initiate any update CD site configuration, within 10 days of the expiration
of the license.
5.2.2 Privilege to Add/Delete Nodes Revoked
An administrator may not be add or delete nodes from a CD site which he/she created
then assign to a monitor.
5.2.3 Unable to Zoom Real time Charts
The Zooming of charts is not supported in the current version
27 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
5.2.4 Historical Data Display
The historical statistics are not available on this version. The configuration of the
Reporter Data Collector is not available from the GUI
5.2.5 Validation of IP Persistency is missing
The IP persistency rule is not validated in this version.
5.2.6 Fail-back to primary scheduler NOT functioning
Under some circumstances, the fail-back from the backup scheduler to the primary
scheduler does not work. The fail-over mechanism from primary to backup works
properly as intended.
5.2.7 Configuration Issues with Soft/Hard Disable
Deleting a node from a second CD site may cause loss of this site configuration if
Soft/hard disable is selected.
5.2.8 Intermittent Display of CD site components
Under rare conditions, Central Dispatch Site components such as nodes, scheduling
rules or NAT configuration may not visible after they have been either added or deleted
to the CD site
5.2.9 Secure Access to CD 5.0
In this release, CD can be managed and configure through HTTP, port 3000. Access
through HTTPS using SSL (port 5000) is not supported.
5.2.10 Multiple Administrators
This version does not allow multiple administrators to be logged in concurrently.
5.2.11 Re-enabling a Administratively Disabled Node
A user can re-enable an administratively disabled node by making it an affiliated node,
then making it a regular node, then enabling it.
5.2.12 Dithered Display with HTTPS with Firefox 1.5.0.4
The user may experience fuzzy and dithered look and feel on the left panel when using
SSL to connect to CD administration console using Firefox 1.5.0.4
5.3 Scheduling Rules issues
5.3.1 Ping of VIPs Requires ICMP rule
Central Dispatch can now schedule traffic for all protocols. In order to get a ping
response showing that a VIP is alive, you must create a Generic IP (non-persistent)
Scheduling Rule for ICMP. Without the rule the Scheduler discards all ICMP traffic.
5.3.2 Firewalls and ICMP traffic
When load balancing a firewall using CD, schedulers check the firewall for availability
using ICMP. If a firewall device has ICMP turned off, the Scheduler marks the node as
down. The workaround is to set a firewall security rule (or policy on some firewalls) to
accept and respond to ICMP traffic from both the inside and outside firewall
Schedulers. Firewall load balancing is not supported on the Linux platform.
28 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
5.3.3 FTP traffic and multiple session-based firewalls
FTP traffic using Central Dispatch through multiple session-based firewalls must be set
up with rules that send FTP connection requests through only one firewall node. To do
that, set up an FTP rule on the outside Central Dispatch site to send all FTP traffic to
only one firewall server node using VIP port 21.
You need to set up, next, an FTP rule on the inside Central Dispatch site to send
traffic back through the same firewall node but using VIP port 0 (zero). On the inside
site, add specific rules for other ports (not using FTP) to load balance to more than one
firewall server node.
5.3.4 Port mapping not supported with MAT routing
The MAT (MAC address translation) method for routing Affiliated servers cannot be
used with the Central Dispatch port-mapping feature. Port mapping allows a request to
the VIP on one port number to be mapped to a different port number on the server.
5.3.5 Bandwidth Allocation Denial protection
The Resonate Central Dispatch User Guide explains the use of the variables
BAD_PROTECT_FILE_SIZE and BAD_PROTECT_WIN_SIZE to protect against
Bandwidth Allocation Denial (BAD) attacks. To completely turn off the effects of the
variables, commenting out or removing the variables and then stopping and starting the
Central Dispatch Agent is not sufficient. To turn off one of the variables on a UNIX
system, comment out or delete the variable and then unload and load the RXP module.
Call Resonate Technical Support for loading and unloading details. To turn off one of
the variables on a Windows system, delete the variable or set the variable to 0 (zero)
and then reboot the system. See the “Set environment variables” section of the
“Advanced Site Setup” chapter of the Resonate Central Dispatch User Guide for
details on setting variables.
5.3.6 Deleting all Scheduling Rules
Deleting all Scheduling Rules from a site that also has Outbound Rules creates a site
configuration that is not supported and not valid. The site continues to run with the
deleted rules, and the rxpstat -x command displays the same number of rules as before
the deletion, but the configuration file is updated. Stopping and re-starting the site
brings up the site with no rules file.
5.3.7 Generic IP Rules do not support FTP
Generic IP service rules do not support the FTP protocol. Use FTP service rules to
schedule FTP requests to one or more servers.
5.3.8 Non-persistent rule creates persistent connections
A non-persistent rule may be handled as if it is persistent rule if the port-independent
persistent sessions (also known as ‘shopping cart’) variable is set. This can happen:
1. The port-independent persistent sessions variable is set.
2. A persistent session rule creates a association in the scheduling table between a
client to a given server.
3. A non-persistent rule evaluates to true by the same client to the same VIP.
4. The connection will be directed to the same server if that server is also
configured for the second rule.
The result is that load balancing does not happen as expected because the new
connection is treated as a persistent connection.
5.3.9 Loss of Firewall Connectivity Not Detected
If one of the Affiliated servers that make up your firewall experiences a loss of
29 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
connectivity (for example, because of a cable pull), this loss of connectivity might not
be detected by the Scheduler in the site on the other side of the firewall. The Scheduler
in the other site continues scheduling traffic to the firewall as usual. You can use the
Resonate Commander Solutions™ to monitor for connection losses and automatically
adjust the scheduling policy accordingly for the Schedulers.
5.3.10 UDP Connection Timeout Value Not Absolute
The timeout value you specify for UDP Scheduling Rules (Generic IP) is not absolute.
Because UDP connections are considered stateless persistent connections, additional
processing must occur to clear them from the scheduling table. If you specify a 10
second timeout, it could take a total 20 seconds or slightly more before the entry for the
UDP connection is cleared from scheduling table. After the entry has been cleared,
new UDP connections can be sent to a different server.
5.3.11 FTP Rules Not Supported for Affiliated Servers
Affiliated servers are not able to handle FTP Scheduling Rules.
5.3.12 Mistaken Assignment of MAT Affiliated servers
Affiliated servers using the MAT (MAC address translation) routing mechanism are not
able to handle FTP requests. When you specify an FTP Scheduling Rule using the
Web GUI, the individual MAT servers are absent from the Servers sub-tab of the
Scheduling Rule’s content pane, but you are still allowed select the asterisk (*) server
to indicate all servers in your site (including the MAT servers). Central Dispatch
mistakenly does not then exclude MAT affiliated servers from the list of all servers
assigned to the rule. In another scenario you could accidentally change a server in,
using the Web GUI or CDAction, from normal server mode to affiliated server mode
and not be aware that it is assigned to an FTP rule (which it is not able to handle).
However this happens, open connections will begin to build up on the affiliated servers
as the wrong requests are sent to them.
5.3.13 False Message, “Under SYN flood attack”
A Central Dispatch site receiving 1000 or more hits per second may falsely generate
the message, “Site may be under SYN flood attack!” To avoid this message, set the
connection hard limit for the service used to 65535. For instance, when using
persistence services, set the variable PERSIST_CONN_HARD_LIMIT=65535. See the
“Set environment variables” section of the “Advanced Site Setup” chapter of the
Resonate Central Dispatch User Guide for details.
5.3.14 Large Configuration File Requires Environment Variable
The default size for the agent-config file is 110 KB. This file holds your site
configuration including VIPs and rules (both Scheduling Rules and Outbound Rules).
You will exceed the default file size if you try to configure a site with a large number of
VIPs (maximum is 512) and a large number of rules (500 or more), or a site with fewer
VIPs but an even larger number of rules (900 or more). In the case, you need to
exceed the default size, you must set the RES_FILE_BUF_SIZE environment variable
on every non-Affiliated node of your site to a value greater than 110 KB. For a 200 KB
file this variable should be set to a value of 204800 (kilobytes times 1024). In one
example a file with 512 VIPs and 512 rules was 118 KB in size, but other factors such
as the number of nodes in your site could easily change this. For details on setting
Central Dispatch environment variables see the “Set environment variables” section of
the “Advanced Site Setup” chapter of the Resonate Central Dispatch User Guide.
A copy of this file is located on all non-Affiliated nodes at:
$RESONATE/cd/log/agent.dir-<node_name>/agent-config
where <node_name> is the name of a non-Affiliated node in your site. Check the
size of this file before adding large numbers of VIPs or rules.
30 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
5.3.15 Web Server Keep-alive Feature and IP Persistence
When using the IP Persistence Scheduling Rule, the timeout feature does not work if
the Web server has the keep-alive feature active. With the keep-alive feature active on
a Web server, once a client connection is set up, requests that come in after the
timeout always go to the same server until a new connection is made. Set the keepalive feature to “off” on all Web servers to make the IP Persistence timeout functional.
5.3.16 Port-independent persistent sessions refused
For port-independent sessions to remain persistent to the same server, each IP
persistence or Cookie Persistence rule for the VIP, with multiple ports, must include the
exact same list of servers. If one of the rules does not contain the same list, persistent
session requests can be refused.
5.3.17 Scheduling Based on CGI parameters
Scheduling Rules based on CGI parameters catch CGI requests only if the requests
are GET requests. POST requests do not trigger CGI parameter rules. To trigger a rule,
the CGI parameters must be in the body of an HTTP request as in a GET request.
5.3.18 No Warnings Possible for Invalid Scheduling Rules
It is possible to add Scheduling Rules that are inconsistent with your node
configurations and not have a warning issued. For example, you can add Scheduling
Rules that direct connections to a dedicated Scheduler (one that is not enabled as a
server) without getting a warning.
5.3.19 Custom Data Scheduling Rule Unchecked Protocol
Custom data scheduling rule does not check protocol when choose which rule to match
according to pattern of request
Create two Custom Data rules, one with pattern "aaa" with server A serving the rule the
other with pattern "bbb" with server B serving it. So, if we execute "$telnet VIP 80",
and send a request " GET /?aaa", we will get a page from server A. If we send "GET
/?bbb", we will get a page from server B.
Now change the Protocol of the first rule (with pattern"aaa") from TCP to "Other" and
randomly issue a number, say, 99, to the protocol. Then if we send "GET /?aaa" to
VIP:80, it should be rejected but instead, it is accepted and we get a page from Server
A. If we change TCP to UDP or ICMP, the same thing happens. If we change the
Protocol of BOTH rules to UDP or ICMP or Other, and then send a request, no request
will be accepted.
5.3.20 Central Dispatch Cannot Know that the UDP Server is Down
If a UDP server process goes down or is unreachable by the scheduler but the
operating system is up and running, Central Dispatch won’t know that the UDP server
is down.
5.3.21 Source IP of ICMP Response Packet from Affiliated Server
The source IP of ICMP response packet from affiliated server is physical IP of server
Ping the VIP of a site. If the site includes affiliated server and the echo request is
served, the response packet’s source IP isn’t the VIP -- it’s the IP address of the
affiliated server.
5.3.22 Multiple FTP Connections May not Follow Rules
If a single client makes simultaneous, multiple FTP connections to your site, the
connections will be made, but they may not follow the Scheduling Rules you have
31 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
defined. All simultaneous FTP connections from a single client are passed to the same
server, namely, the one that gets the first connection. This happens even in the case
where the client specifies a different IP address for each connection and you have
defined Scheduling Rules that direct FTP connections for those different IP address to
different servers in your site. By design, FTP rules are persistent on IP address.
5.3.23 Custom Data Rules Issues
5.3.23.1 Persistent sessions not based on ranges or masks
Custom Data rules that create persistent sessions using expressions containing port
ranges or IP address masks do not work as expected. Theoretically, all requests
coming in on any port in a range, or that match the IP address mask, should go to the
same server. This is not the case. Currently, persistence is based on individual
requests and not on the complete range or mask. For example, if a rule specifies
persistence to servers S1 and S2 based on a port range of 80 to 200, then when a
request comes in on port 80, one persistent session is created for S1 but a second
persistent session can be created for S2 if another request comes in on port 81. Both
requests do not persist on S1.
5.3.23.2 Expression field ‘end of offset’ incorrect
In Custom Data and Outbound Rule expressions that use Pattern Length and Data
Offset End, the pattern length is incorrectly added to the end of the data offset. For
example, if an expression has a data offset specified to end at byte 1000, and the
pattern length is set to 7 bytes, the search looks for the pattern through byte 1007 of
the data stream. The workaround is to subtract the pattern length from the intended
end of offset, then enter this number as the End of Offset. In the example above,
entering 993 for the End of Offset would give the desired results.
5.3.23.3 Incomplete Requests Cause Connection Hang
If a Custom Data rule is used to search a long segment of the data stream, say the
rule’s end of the offset is 5000 bytes, and the total length of an inbound data request is
shorter than this end value, say only 1500 bytes, then Central Dispatch issues a TCP
ACK for more data from the client application. If more data does not arrive then the
request is incomplete and causes the connection to hang. This situation can happen in
one of two ways, a) there is only one rule and the request is incomplete, or b) there are
multiple rules that all fail and one of them experiences an incomplete request. The
workaround is for you to either carefully choose the offsets for rules if the offset spans
multiple IP packets or to include the “Always-True” rule to insure that the connection is
handled (see the “Using Scheduling Rules” chapter of Resonate Central Dispatch
User Guide for more information).
5.3.24 UDP Replies use Server IP address, not VIP address
When UDP datagrams whose destination address is the VIP are sent to a UDP
application on a Central Dispatch server, the source address of replies from the UDP
application is the server's physical IP address and not the VIP address. RXP will detect
this and change the source address back to the VIP automatically. This feature can be
disabled on servers and scheduler-servers (but not dedicated schedulers) via the rxpctl
utility:
rxpctl -UDP 0/* disable UDP translation */
rxpctl -UDP 1/* enable UDP translation */
The status of udp translation can be checked with the command:
rxpstat -A rxp_stats.txt
This will print a value for the RXP_UDP_TRANS environment variable if UDP
translation is enabled. Otherwise, it will not be shown.
32 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
5.3.25 Round-robin for Site setup and Resource-based Scheduling Rule
The Round Robin Scheduling Policy is intended for site setup and testing purposes and
is not intended as a fully supported load balancing policy. The round-robin algorithm used
in Resource-based Scheduling can be used to direct traffic to content nodes.
5.3.26 Cannot Add a Scheduling Rule with Port
A scheduling rule cannot be created without specifying a server Port
5.4 Outbound Rules issues
5.4.1 Evaluation of packets affects Redirect
Retransmitted packets are not always properly evaluated by Outbound Rules. If a pattern
needs to be evaluated and the offsets are 0 to 2000, and the first packet of 1460 bytes
was retransmitted, then the outbound filter will incorrectly assume it has seen 2920 bytes
of data and switch off the filter.
Or, if the server has found the pattern but the client or Scheduler has not received the
pattern, the server stack will retransmit the packet. But as the rule has already been
evaluated the filter will skip reevaluating the retransmitted packet, which could lead to a
loss of persistent data on the scheduler.
5.4.2 Redirect of UDP requests lost if timeout = 0
Each Outbound Rule must have an associated service created for it with a Scheduling
Rule. In the case of a UDP service created using the Generic IP Scheduling Rule, UDP
requests are considered persistent sessions and a timeout field is provided. The default
value for the timeout is 0 (zero). If you create an Outbound Rule for UDP using the
Redirect command, and the timeout value in the original Scheduling Rule is 0, redirected
UDP requests will be lost because the entries for the requests are immediately removed
from the scheduling table. Therefore, you must provide a reasonable timeout for the UDP
Scheduling Rule in order for the Redirect of an Outbound UDP Rule to work. For
example, if it takes between 5 to 10 seconds for a server to response to UDP requests,
the timeout should be set to 11 to 13 seconds. A longer timeout should be used if the
Scheduler will be running under a heavy load.
5.4.3 Redirect fails for segmented requests
The redirect command feature of Outbound Rules fails if the client request is segmented
into more than one packet and the complete pattern is not in the first packet. A rule
searching for a pattern fails if the rule does not find the pattern in the first packet received
after establishing the connection.
5.4.4 Rule fails because of retransmitted packets
The offset values specified for Outbound Rules are not always handled correctly when
servers retransmit packets. Assume that an Outbound Data rule is created to search for a
expression and the rule has an offset of 0 to 1,500 bytes. If the server transmits the first
packet, which has a length of 1,000 bytes, and the expression to be searched for ends at
byte 1,250, and if the server then retransmits the first packet, the Scheduler wrongly
assumes that the retransmitted packet is the second packet in the sequence. The rule
then incorrectly fails because the offset appears to be exceeded and the expression was
not detected. This same problem could cause persistent data to not be detected.
5.4.5 Segmented pattern fails to create persistence Session
If the pattern for an Outbound Rule used to create a persistent session is divided
33 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
between TCP segments, the pattern is not recognized and a persistent session is not
created.
5.4.6 Cookie persistence and Outbound Rules
If you have one or more Cookie Persistence Scheduling Rules, Outbound Rules for
HTTP are overwritten by the Scheduling Rules. The IP Persistence Scheduling Rules
coexist with Outbound Rules with no conflict.
5.4.7 Route tracing for persistent Sessions
The trace route mechanism sends three packets with 3 different server ports. As
consequence, the shopping cart future should be turned off.
5.4.8 TCP & IP Persistency Outbound Direction
Outbound rules for TCP & IP persistency are not supported to specify the Redirect
request command, despite the fact the Graphical User Interface allows it.
5.4.9 Incorrect Duplication of Outbound Rules
Newly created outbound rule are duplicated for HTTP service rule.
5.5 Command Line Interfaces issues
5.5.1 No statistics for MAT mode Affiliated servers
Use of rxpstat -s shows no hits, open connections for MAT mode Affiliated servers
assigned to server persistent TCP con. created using the Generic IP scheduling Rule.
5.5.2 No hits for persistence rules
Using the RXPSTAT utility (rxpstat -x or rxpstat -X) to check for hits of Cookie
Persistence and persistent Outbound Data Rules shows no hits even though hits may
have occurred.
5.5.3 Primary server weight field missing from rule
When you add a Scheduling Rule using CDAction, and you accept the default server
weight for the primary server(s) by not specifying a value, the field for the server weight
(VS_SWGHT) does not get entered into the rule. You can verify this by viewing the rule
file or configuration file. If you use the Web GUI to enter the same rule, the server weight
field is entered into the rule.
5.5.4 Failover Server Weight Blank in Web GUI
When you add a Scheduling Rule with a failover server using CDAction, and then view
the rule in Web GUI, the field for the failover server weight is blank.
5.5.5 Starting/Stopping CD site with CDAction
If users use CDAction to start/stop the CD site then they need to restart CDController in
order to see the changes in CDController.
34 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
5.6 Solaris Specific Issues
5.6.1 Site Restart Script Not Installed
The auto site restart script, Sentinel, requires CDAction to be installed in order for it to run
at the appropriate time (see the “Site Management” chapter of the Resonate Central
Dispatch User Guide for more information). During the installation of Central Dispatch,
when you choose to install both the node component and CDAction, the Sentinel script is
automatically installed. But if you choose to install the node component first, and then
later decide to do a separate installation of CDAction, the Sentinel script does not get
installed. If you want the Sentinel script installed, the workaround is to uninstall both the
node and CDAction and then re-install them together at one time.
5.6.2 Solaris VIP limit
Solaris systems dynamically add VIPs when starting a Central Dispatch site. When a site
is stopped, the VIPs are only disabled. If you stop a site often to add new VIPs and delete
old VIPs, you may hit the Solaris interface limit. (The limit varies for different Solaris
releases). To free the interfaces that the system is no longer using, remove VIPs
manually. Use the ifconfig(1M) command with the down 0 option to remove VIPs.
Disabled VIPs are also removed during a reboot.
The number of VIPs configured on a Solaris platform (32-bit/64-bit) cannot exceed 255.
This is the default maximum value on a Solaris platform.
5.6.3 Support for Solaris 10 Local Zones
Central Dispatch can be deployed only in a Solaris 10 global zone. However Central
Dispatch agents are not compatible when deployed on a non-global zone.
5.6.4 Conflict with Hardware Checksum
The Hardware checksum for all the NIC installed on Scheduler node (not just the one
used by Central Dispatch) has to be disabled before the RXP module is loaded.
5.7 Linux Specific Issues
5.7.1 Heavy load causes Apache to halt
It has been observed that if you have Central Dispatch configured to schedule requests
using SSL to a host running the Apache Web Server, and there is a heavy HTTP load
on that server, the Apache Web Server will occasionally halt with an “Out of Memory”
error being generated. To prevent this situation configure your SSL Scheduling Rule to
limit the number of requests being sent to the Linux host running the Apache Server.
5.7.2 MAT Mode for Affiliated servers not supported
MAC address translation is not supported on Linux Affiliated servers.
5.7.3 Stopping CD Agent sometimes results in an error message
When you stop cdagent or reporter agent using the command /etc/init.d/cdagent or
/etc/init.d/agent-reporter, sometimes you will get an error message that says the
process doesn’t exist. This occurs because there are three processes and one of them
is the parent process. The first process killed by the command can be any of the three.
If the command kills the parent process first, the other two processes will also be killed.
35 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
5.7.4 Non-TCP traffic with Affiliated Servers
Traffic using transport protocol other than TCP (i.e UDP) sent to Affiliated Servers
cannot have 0 as timeout value
5.7.5 Red Hat Linux Package Required to Install Central Dispatch
RH Linux
Version
9.0
AS 2.1
AS 3.0
AS 4.0
Runtime Libraries
bc, binutils, coreutils, gawk, grep, modutils
bc, binutils, sh-utils, fileutils, textutils, gawk, grep, modutils
bc, binutils, sh-utils, fileutils, textutils, gawk, grep, modutils
bc, binutils, sh-utils, fileutils, textutils, gawk, grep, modutils
5.7.6 Failure to Add Large Rules File
In the case, the scheduler is running for a long period of time, adding a file describing a
number of rules greater than 500, may result in an error message. if the host running
Central Dispatch scheduler has limited RAM memory (< 384 Mbytes). Depending on the
context, and operation, the error can be displayed using the following messages:
• “Couldn’t set the rules”
• “New rule set ignored”
• “Kernel Rules have not been set”
There are 2 options available to get around this problem
1. Set RES_FILE_BUF_SIZE environment variable with a value greater than100K.
2. Increase the RAM memory on the machine the scheduler runs alleviates the
problem.
5.7.7 “Hard/Soft” Disable for IP Custom Data Rule
In the case of a Custom Outbound Rule is defined for IP Persistent connection, request
to disable the server node using either a ‘Hard Disable’ or ‘Soft Disable’ actions does not
time out as expected. The two environmental variable are defined as
• RES_SOFT_DISABLE_TIMER
• RES_HARD_DISABLE_TIMER
5.7.8 Outbound Custom Data Rule for UDP protocol
The client may not receive the response from an UDP-based Protocol request, for an
outbound custom data rule; in the case the target of the request is the scheduler/server
node. The problem does not exist for independent server nodes the scheduler does not
run.
5.7.9 “Eth0: memory shortage….”: Error for UDP with Timeout 0
Very heavy UDP-based traffic may cause memory shortage on the server running as
Central Dispatch Scheduler and Nodes; in the case the timeout is set to zero. The
following error message is displayed under this condition:
“Eth0: memory shortage. Can’t kill the process xxxx”
5.7.10 No Response from UDP requests on Affiliated Servers
In the case CD scheduler runs on Red Hat Linux 9.0 and Advanced Server 2.1, a UDP
request from a client to an affiliated node, may not generate a response. The problem
occurs for both generic IP and custom data rules for full and half NAT (Network Address
Translation) modes.
36 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
5.7.11 Re-authentication Required to Load RXP Driver for SSL
On Red Hat Linux AS 3.0, The RXP driver won’t load in the case Apache Server using
SSL protocol start. The user must either re-authenticate by entering a password to
enable Central Dispatch to process SSL request or load the driver prior to the launch of
the web server. In order to ensure that rxp starts before the apache Web Server, the
startup script needs to be executed before the one for apache.
It is highly recommended to use scripted from run level 3 (RC3) and having the RXP load
script be invoked prior to SSL service is started at script level S55 (apache).
5.7.12 Deletion or Conversion of Master Agent Node in a CD site
Removing a master agent node from a site or converting a node into an affiliate node
may cause RXP statistic, total hits, to be cleared up on other nodes of this site.
5.7.13 Version of Agent when importing 3.3.x rule into CD 5.0
Importing a 3.3.x rule file into CD 5.0 site, causes the version of the agent-config file to
change to 3.3. The output of the execution of rxpstat –X will display the version 3.3
5.7.14 Maximum Number of Rules Loadable on RXP
The maximum number of rules, defined in the agent-rule file, which can be loaded to the
RXP using the CDAction utility (CDAction –t 400 command) is 1200. The rules can be
printed out on the standard output (screen) using the command rxpstat –X.
5.7.15 Custom data rule for IP Address/Netmask combination
An inbound custom data rule which the pattern is defined as an IP address/netmask
combination, may fail for netmask of 255.255.255.0.
The rule is not fired in the case the netmask portion is not matched when the rule uses
netmask=255.255.255.0. The work around is to use netmask=255.255.255.255.
5.7.16 Incorrect Status Node after stopping CD Agent
Node will not change the status, after stopping or removing CDAgent from running site
5.8 Windows specific issues
5.8.1 SYN-bomb protection
Central Dispatch protection from SYN-bomb attacks on Windows depends on the amount
of available memory in machines used as Central Dispatch Schedulers. The amount of
memory needed depends on the number of IP services that are susceptible to SYN-bomb
attacks. Central Dispatch has default hard and soft limits for the number of connections
allowed for a service (as explained in the Resonate Central Dispatch User Guide). The
defaults assume 256 MB of memory on a Windows machine with one service and 128
MB of memory on a UNIX machine with one service.
Machines with less memory need lower hard and soft limits for the number of
connections allowed. Use the environment variables given in the Resonate Central
Dispatch User Guide to set the hard limit to 70000 and the soft limit to 15000. Examples
of such variables are HTTP_CONN_HARD_LIMIT and HTTP_CONN_SOFT_LIMIT.
A machine with more than one service to protect needs 32 to 64 MB of added memory for
each added service. This is true for machines starting out with the expected amount of
memory (256 MB for Windows, 128 MB for UNIX) and for machines with less memory
37 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
and lower hard and soft limits.
For example, a Windows machine with HTTP and Generic TCP (TELNET) services to
protect and 256 MB of memory needs:
• An additional 64 MB of memory.
• The hard and soft limits for both services set to 70000 and 15000:
HTTP_CONN_SOFT_LIMIT 15000
HTTP_CONN_HARD_LIMIT 70000
TELNET_CONN_SOFT_LIMIT 15000
TELNET_CONN_HARD_LIMIT 70000
A Windows machine with 256 MB of memory and two services needs only an extra 64
MB of memory.
5.8.2 Installer allows duplicate port numbers
During installation, if you change a default port number for one Central Dispatch
component, the installer program fails to check if the number you enter is a duplicate of
another port number used by a another Central Dispatch component.
5.8.3 Site restart script not installed
The auto site restart script, Sentinel, requires CDAction to be installed in order for it to run
at the appropriate time (see the “Site Management” chapter of the Resonate Central
Dispatch User Guide for more information). During the installation of Central Dispatch,
when you choose to install both the node component and CDAction, the Sentinel script is
automatically installed. But if you choose to install the node component first, and then
later decide to do a separate installation of CDAction, the Sentinel script does not get
installed.
If you installed CDAction separately, the workaround is to:
1. Open a command prompt.
2. cd C:\Program Files\Resonate\cd\bin
3. Run sentinel.exe -c install
4. Open regedit and set the following string value:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\sentinel]
"DependOnService"="RESONATE_AGENT"
5.8.4 Installation and the Performance Monitor
If any application is using the Windows Performance Monitor when you install Central
Dispatch, the installation gives the following error message: “Registry error: Unable to
load the RXPVNIC performance counter strings.” The installation continues to
completion, but RXP statistics will not be available to Performance Monitor.
5.8.4.1 Event log shows rxpperf.dll error messages
The error message is, “The collect procedure in Extensible Counter DLL “rxpperf.dll” for
the “RXPVNIC” service returned a buffer that was larger than the space allocated and
may have corrupted the application’s heap. This DLL should be disabled or removed
from the system until the problem has been corrected to prevent further corruption. The
application accessing this performance data should be restarted. The Performance
data returned by counter DLL will be not be returned in Perf Data Block. Overflow size
is data DWORD 0.”
5.8.4.2 Workaround
The workaround for this problem is:
1. Run unlodctr rxpvnic from the command line.
2. Delete the following registry key:
38 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
MyComputer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
RXPVNIC\Performance
To address the “Unable to load the RXPVNIC performance counter strings” problem
listed in the error message, be sure to close out all applications, which use
performance counters before running the Central Dispatch installation program.
5.8.5 Network Load Balancing not supported
The Network Load Balancing feature of Windows 2000 is not compatible with Central
Dispatch. Do not install Network Load Balancing on a machine that will use Central
Dispatch components.
5.8.6 Large Persistence Tables
On Windows 2000 machines using persistence services, after a fail over to a backup
Scheduler and then fallback to the primary, the persistence table may be left in memory
on the backup Scheduler. The memory may not be released. If the primary fails over
again, the backup machine may run out of kernel memory. Persistence data may be
lost or the machine may hang. The situation can happen when the persistence table
has 100K entries or more (generally a size of 8 MB or larger) and the machine has 256
MB of memory or with entries of 200K or more and 512 MB of memory. To avoid this,
add more memory to the backup Scheduler. Fallback to the primary does not create the
problem on the primary Scheduler.
5.8.7 Multicasting applications need physical IP addresses
The Central Dispatch installation includes a copy of the MS Loop back Adapter.
Multicasting applications using the machine will find that multicasting traffic is blocked if
that traffic uses the loop back adapter. To allow multicasting to work, the application
needs to have multicasting set up with one of the following solutions:
• For WinSock1 applications, the imr_interface field in the ip_mreq data structure
must use a physical IP address. If the application uses INADDR_ANY when it does
not get a physical IP address at run time, use gethostbyname() to get the IP
address of the first NIC card. Use that address for imr_interface.
• For WinSock2 applications, use a physical IP address in the bind() system call. If the
application uses INADDR_ANY when it does not get a physical IP address at run
time, use gethostbyname() to get the IP address of the first NIC card. Use that
address for bind().
5.8.8 Multiple network cards require proper routing
If any of the Central Dispatch nodes running Windows has more than one network
adapter card installed, all of the cards are selected by default during installation for
binding the RXPVNIC driver to those cards. If you choose not to bind RXPVNIC to one
or more of those cards, be sure to set up routing so that no Central Dispatch traffic
(incoming data from clients, traffic between Central Dispatch Schedulers and servers,
outgoing data back to clients) is routed through the cards to which RXPVNIC is not
bound.
5.8.9 Do not manually uninstall Resonate RXP Driver
Do not use the Network Control Panel to unbind the Resonate RXP Driver from any
NICs to which it is bound. The correct way to remove the Resonate RXP Driver is to
remove the Central Dispatch software from the machine. See the Resonate Central
Dispatch Installation Guide for the complete instructions for uninstalling Central
Dispatch.
39 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
5.8.10 Switch to Affiliated server
A Central Dispatch node can be configured as a normal server node and then later
switched to be an Affiliated server node (but not nodes configured as Schedulers). In
some cases, the switch can leave the server unable to respond to client requests for up
to 10 minutes, depending on the ARP timeout value.
The following scenario creates the problem:
• The Windows machine is set up as a standard Central Dispatch server, Serv1
as an example.
• The Central Dispatch Scheduler receives a client request for a VIP serviced by
Serv1 and routes the request to Serv1.
• Change Serv1 to affiliated server using half NAT routing.
• The Central Dispatch Scheduler fails over to the backup Scheduler.
The fixes for this situation are:
• Use the ‘ARP’ command to delete the VIP entry: arp -d <vip_ip_address>
• Reboot the machine to reset the ARP entries.
• Wait for the ARP timeout to delete the ARP entry.
5.8.11 Memory error message: ‘Can’t get memory’
A Central Dispatch node (a machine with RXP installed) that has CPU-intensive loads
may generate the message, “add_to_msg: Can’t get memory!” You can safely ignore
the message if it appears occasionally. If it appears repeatedly over a short time,
increase the amount of physical RAM or decrease the CPU load.
5.8.12 Log files not readable with Notepad
Some log files on Windows 2000 systems are written using the UNIX system new line
convention to indicate line breaks. To read such log files, use an editor or utility (such
as WordPad) that can properly interpret the UNIX system linefeed convention and
break the lines correctly when displaying them on the screen. Notepad cannot be used
because it does not properly interpret the UNIX system linefeeds.
5.8.13 Deleted node returns
Occasionally, after deleting from a site a node that is also the master Agent, the node
reappears in the site. Another node does take over the master Agent task, but the
deleted node returns to the site as a functional node. Delete the node a second time to
fully remove it from the site. This same thing can happen if the master Agent node is
changed to an affiliated server.
5.8.14 RXP binds to HP NC3134 Teamed Card after install
The problem occurs when the proper and strict installation steps are not followed.
5.8.14.1 Installation
If teaming NICs are required, NICs should be teamed before installing the RXP. If
NICs are teamed together after installing RXP, then behavior is undefined.
When CD is installed on host with Teamed NIC, there is a possibility that "RXP
Driver" is bound to Teamed Adapter. This can be verified through "Network and
Dialup Connections" menu. If RXP Driver is bound to teamed NIC, uncheck it and
reboot the host.
RXP Driver should be bound to all physical NICs in the team and shouldn't be bound
teamed NIC.
40 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
5.8.14.2 Fail over
Fail over due to heartbeat failure could be tricky. When different ports in the team lost
the connectivity with one another, but connectivity with rest of the network is OK,
Heartbeat fail over occurs.
All the members in the team keep sending heartbeats to one another at pre-specified
intervals of time. This interval can be configured through teaming configuration utility.
The default value is 3 seconds.
Central Dispatch has also heartbeat interval. Assume that the master agent of CD
Site is on different CDNode than host with teamed NIC. When CD Agent's heartbeat
interval is less than that of teaming NICs, CD Agent on master agent couldn't get
response to it's heartbeat until the teaming NIC performs the fail over. Teaming NIC
using its heartbeat interval performs this fail over. At this point the CD Agent detected
the fail over resulting from a failure on master agent. Subsequently, master agent
deletes the CDNode with teamed Incan adds it back when the failure is completed.
To avoid this, always keep CD Agents heartbeat interval more than that of teaming
NICs.
5.8.14.3 Uninstall Issue
RXP Driver isn't unbound even after CD un-install program. This can happen if the
teamed NIC configuration utility is opened while running either CD Uninstall program
or opening any of the NIC Adapter's property dialogue.
It's possible that this error message "Could not lock INETcfg, it is already locked by"
occurs during the uninstall operation. When you click ‘OK’ button, the installation will
continue to completion. However, it does not remove Resonate rxp driver from the
interfaces. You need to reboot the system, and then uninstall the Resonate rxp
driver from any interface, and then reboot the system. After machine comes up,
make sure to verify that Resonate rxp driver has been uninstalled completely.
The uninstall operation would restrict the uninstall program from unbinding RXP
Driver from the NICs. This is in the control of OS and Install/Uninstall merely send
messages to OS. When that message is sent to OS and any of the utilities previously
mentioned are kept open, OS returns error.
5.8.15 CD Adapter connectivity during fail over
If CDAdapter is installed on a machine with teaming NICs (i.e HP NC3134) and
failover occurs for the teamed adapter, CDMaster (GUI) could loose the connectivity
with CDAdapter. The work around is to connect to the CDAdapter again.
5.8.16 Warning for Unsigned RXP Driver (Windows 2003 only)
During the installation of the RXP driver component of Central Dispatch 4.1 on
Windows 2003, a warning dialog pop up with "Hardware Installation" with the
following messages:
"The software you are installing for this hardware: Resonate RXP Miniport has nor
passed Windows Logo testing to verify its compatibility with this version of
Windows. ..."
"Continuing your installation of the software may impair or destabilize the correct
operation of your system either immediately or in the future. ..."
The message can be safely ignored.
5.8.17 “Automatic Metric” Settings (Windows 2003 only)
The option “Automatic Metric” of advanced TCP/IP is enabled by default in Windows
2003 server. The option causes connectivity to network to be lost because of the
presence of some IP routes on those machines.
The work around this limitation is to disable the “Automatic Metric” advanced TCP/IP
option in the operating system before installing the CD.
41 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
The steps are
• Select->Control Panel->Network Connections->Local Area
• Connection<#X>->Properties
• Select General Tab
• Select Internet Protocol TCP/IP
• Select->Properties->Advanced
• Uncheck "Automatic Metric"
• Enter the metric value as "1".
5.8.18 Warning for remote installation (Windows 2003)
The following message is displayed, on a pop up dialog box, during the remote
installation of central dispatch using SETUP.EXE utility.
“Some files can harm your computer. If the file information below looks suspicious, or
you do not fully trust the source, do not open or save the file”
“This type of file could harm you computer if it contains malicious code.”
The message is generated by Windows 2003 operating system to warn the user for a
potentially insecure operation but has not impact on the installation or execution.
5.9 Migration from 3.x and 4.0
5.9.1 Concurrent Usage of Different GUI
The GUI of CD 3.x (Dispatch Manager), 4.x (CDMaster) and 5.0 (CDController) both
cannot be used concurrently: only one type of GUI is allowed to manage a CD 5.0 site.
5.9.2 Support for multiple shadow schedulers
In case of multiple shadow schedulers are used to manage a CD 3.x site, all the
primary and backup schedulers need to be upgraded to CD 5.0. A combination of CD
schedulers with version 3.x, 4.x and 5.0 schedulers will some prevent statistics to be
displayed in GUI.
5.9.3 Removing rule after upgrade
rxpstat may still reports the statistics on a rule that has been removed after the
upgrade from CD 3.x or CD 4.0 to CD 5.0 The user has to modify the version of the rule
file to correct the problem using the following procedure
1. Export the rule file
2. Change the version number to 5.0 in the rule file
3. Import the rule file
5.9.4 CD 5.0 Rule with partially upgraded site
User should not add any rule with CD 5.0 specific feature through the web-based GUI
of CD 5.0 until the CD site is entirely updated with CD 5.0 agents.
5.9.5 Shadow Scheduling to backup scheduler
In the case the option “Use shadow scheduling to backup scheduler" is enable,, no
persistence entry can be shadowed to the backup scheduler and no fail back if primary
and backup schedulers are with different versions (3.x or 4.0 and 5.0
5.9.6 Limitations with downgrading
Existing schedule rules cannot be modified or deleted after the user roll the upgrade from
5.0 back to 3.x or 4.x. New rules added after the downgrade back to 3.x and 4.x can be
modified and deleted.
42 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
5.9.10 Migration of 4.x outbound rules
Following migration from 4.x to 5.0 outbound rules that involve disabling server may not
work properly. The status of the node is displayed incorrectly on the GUI
5.9.11 Incorrect HTTP Rule Statistics
After migration the statistics of a HTTP rule are shown in the Generic TCP category
5.9.12 Support for Physical Service
This feature has been introduced in version 4.0 so physical services will not be displayed
in previous versions of agents (3.x)
43 of 44 pages
October 2006
Resonate Inc
Resonate Central Dispatch 5.0.3 Release Notes
6 External Issues
This chapter describes any issues caused by software or hardware outside the control of
Resonate Central Dispatch.
6.1 TCP/IP services can fail if Agent fails to start
When Central Dispatch starts running on a node, the Central Dispatch Agent on that node
updates the local routing table to allow TCP/IP packets to go through the appropriate
network adapter. This routing change applies only to the adapter to which the Resonate
Virtual Adapter (RXPVNIC) is bound.
If you reboot the machine and the Central Dispatch Agent fails to start, the routing table is
not updated and TCP/IP packets that should go out over that particular adapter are not sent
out over the network. This causes all applications and services that communicate over
TCP/IP through that adapter to fail.
To correct this problem on Windows, restart the Agent from the Services dialog box (open
the Services icon in Control Panel). Once the Agent has updated the routing table as part
of its startup processing, TCP/IP services that communicate through that adapter should
function normally.
7 Online Help
Online help is available in PDF format and requires installation of acrobat Reader
preferably version 7.0.
44 of 44 pages
October 2006
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement