HP Serviceguard for Linux Version A.11.18 Release Notes, 2nd Edition, March 2009

All nodes in the cluster must allow the following communications:
• from the remote nodes:
— TCP on ports 5302 - and allow only packets with the SYN flag
— UDP on port 5302
• to the remote nodes:
— TCP and UDP on port numbers 49152-65535
The remote nodes must allow the following communications:
• from the cluster nodes
— TCP and UDP on port numbers 49152-65535
• to the cluster nodes
— TCP on ports 5302 - and allow only packets with the SYN flag
— UDP on port 5302
Authentication communication must allow the following ports:
• from the cluster nodes:
— TCP and UDP on port 123
• to the cluster nodes:
— TCP and UDP on port 123
NOTE: If you suspect that the firewall is blocking communications, you can add-j
LOG before the last line in your iptablesfile (for example /etc/sysconfig/
iptables) to log any blocked ports. Consult your Linux distribution’s documentation
on firewalls for information on iptables.
Using udev for Persistent Device Names
In a Linux system, device names are not necessarily consistent from one boot to another.
Consider a system with LUNs /dev/sdg, /dev/sdh, and /dev/sdi. If /dev/sdh
is removed, then after the system is rebooted the old /dev/sdi may be renamed to
/dev/sdh. This can cause problems with scripts that refer to specific device names.
Some I/O components provide a persistent naming function, such as the multipath
function within the QLogic driver.
Serviceguard for Linux now supports the use of udev in cases where no other persistent
naming is available. Details are in the white paper Using udev to Simplify HP Serviceguard
for Linux Configuration at http://docs.hp.com -> High Availability ->
Serviceguard for Linux.
52 Serviceguard for Linux Version A.11.18 Release Notes