Serviceguard Manager Version A.05.02 Release Notes, March 2009
To ConfigureTo AdministerTo MonitorTarget cluster's
Service- guard
version
Session Server's
Service- guard
version
not supportedUser must log in to Session
Server as root.
Target must have
<sess.serv> root in
cmclnodelist file.
User can be any entry in Session
Server's /etc/passwd file
Target must have
<sess.serv><root> in
cmclnodelist file.
A.11.13.xx,
A.11.14.xx, and
A.11.15.xx
A.11.16.xx,
A.11.17.xx
User can be any entry
in Session Server's
/etc/passwdfile
Target cluster
User must supply root
password for a cluster
node
User can be any entry in
Session Server's /etc/passwd
file
Target cluster must have an
Access control Policy
configured
• Host = Session
Server
• User = any entry in
Session Server's
/etc/passwd
• Role = Admin
User can be any entry in Session
Server's /etc/passwd file
Target cluster must have an Access
Control Policy configured
• Host = Session Server
• User = any entry in Session
Server's /etc/passwd
• Role = Monitor
A.11.16.xx,
A.11.17.xx
A.11.16.xx
A.11.17.xx
Port Requirements
Serviceguard Manager itself does not have any port requirements. If you want to receive SNMP traps in the
Event Browser, you need the SNMP ports 161 and 162.
Serviceguard does have port requirements, particularly when interacting with internal firewalls. If you are
using a firewall such as Bastille, and connecting to a Cluster Object Manager outside the cluster, these rules
apply:
Each Serviceguard Manager
node must allow these connections:
▲ from the cluster nodes:
udp on port 162•
▲ to the cluster nodes:
udp on port 161•
Each Serviceguard node
must allow these connections:
▲ from the Serviceguard Manager node:
udp on port 161•
▲ to the Serviceguard Manager node:
udp on port 162•
▲ to the COM node:
tcp on port 5303 - and allow only packets with SYN flag.•
Each cluster node
must allow these connections:
• from the COM node to the cluster nodes:
tcp on port 5302 and allow only packets with the SYN flag•
• udp on port 5302
• to the COM node from the cluster nodes
tcp and udp on port numbers 49152-65535 from the cluster nodes•
Compatibility Information and Installation Requirements 21