Serviceguard Manager Version A.05.02 Release Notes, 2nd Edition, May 2009

Table 1-2 Capabilities of Session Servers on Target Clusters (continued)
To ConfigureTo AdministerTo MonitorTarget cluster's
Service- guard
version
Session Server's
Service- guard
version
Configuration menu
available when an
A.11.16.xx or
A.11.17.xx object is
selected User must
supply root
password for a
cluster node
Not supportedUser 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.13.xx,
A.11.14.xx, and
A.11.15.xx
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:
Compatibility Information and Installation Requirements 21