Serviceguard Manager Version A.04.00 Release Notes, June 2004

Serviceguard Manager Version A.04.00 Release Notes
Installing and Running Serviceguard Manager
Chapter 132
Notice that the configuration tab shows only the nodes in your
current map. If you have several subnets, connect to a Session Server
in each, and use the View All option.
2. Log in to each node and edit the /etc/snmpd.conf file to remove your
computer from the list.
3. Stop and re-start the SNMP Master Agent on the node.
a. Find the process ID number, using: ps -ef | grep snmp.
The master agent will show as snmpd, and the subagent will
show as cmsnmpd.
b. Stop that process, using: kill <pid>
c. Restart the agents.
Use: /sbin/init.d/SnmpMaster start for the master agent
Use: /sbin/lbin/cmsnmpd for the subagent.
Setting up Serviceguard Manager
Security, Logins, and Access Policies
In version A.11.16, Serviceguard changed its method of controlling and
assigning logins, and roles. Therefore, the way you open Serviceguard
sessions and discover Serviceguard objects is quite different in version
A.11.16 and later than it is in earlier versions.
Logins and roles, Version A.11.16 and later: Creating or modifying
configuration still requires Root access (UID=0) on a cluster’s nodes.
Starting in Serviceguard version A.11.16, however, a root user can
configure clusters and packages using Serviceguard Manager or on the
command line.
In addition, there are four possible non-root roles that can be defined in
the cluster’s configuration files. These can be specified as Access Control
Policies in the cluster and package configuration files. Each Access Policy
has three parts:
• User: A username from the host’s /etc/passwd file
• Host: Where the user will issue the command. For Serviceguard
Manager, this is the Session Server node