Sun Management Center 3.5 Update 1 Release Notes

Sun Management Center Bugs

Individual Users Are Not Added to the ACL of the Server Support Module (4843429)

If you delete the esadm group from the ACLs of the agent and then add individual users to the ACL of the agent, the user is not automatically added to the ACL of the server support module. Because the server support module does not get updated with the user, the server support module does not allow enabling or disabling of the Performance Reporting Manager. This message is displayed:

Unable to enable/disable PRM data collection on an  agent with new user

Workaround: Add the esadm group to the ACL of the agent and then add the individual users to the esadm group.

Sun Management Center Incorrectly Reports That a Successful Agent Update Has Failed (4994784)

The Job Manager user interface shows Failed for a successful agent update operation. When the agent update operation is performed using the Manage Jobs GUI (graphical user interface), the status of the operation is shown as successful or failed at two different levels.

Summarized status: If the operation was attempted on multiple hosts and if it fails even on one of the hosts, the status of the entire Job is stated as Failed.
Individual status: By clicking the View logs button in the GUI, you can view the status of the operation on the individual host.

The individual status is based on the status information reported by the host to the server through agent-to-server SNMP communication. The status might not be accurate in the following conditions:

The upgrade was successful, but the SNMP port of the agent was changed as a result of agent upgrade that involves reinstall and reconfiguration.
The upgrade was successful but the SNMP request timed out due to various other factors and the status was not communicated back successfully.
The upgrade was successful, but the process took more than the 30–minute timeout set by the server for each individual host. As a result the server thread waiting for status update was terminated before the status report was initiated from the agent side.

Workaround: Use the View Logs tab of the server host details window to see the InstallServer.log on the server host. The details of the operation are available in /var/opt/SUNWsymon/install/agent-update.log of each target host on which the operation is performed.

Module Configuration Propagation (MCP) Does Not Work Through Firewall (4796734)

Module Configuration Propagation (MCP) reads and writes to the Sun Management Center web server through a single predefined port. The default port is 8080. If the web server sits behind a firewall, MCP has no problem reading from the web server, but will have a problem writing to the web server. Once the web server has established a connection with MCP, the server arbitrarily assigns a port to do its job. You cannot specify which port number the web server should assign.

Workaround: None.