Workaround: Use the es-config command to change the SNMP port of the agent.
When you click the Help button in the Java console, it points to Sun Management Center 3.6 Document Collection instead of Sun Management Center 3.6.1 Document Collection.
Workaround: For Java Console help, edit the sunmc.docs.path entry in the /var/opt/SUNWsymon/cfg/javaconsole.properties file as follows:
sunmc.docs.path=docs.sun.com/app/docs/coll/810.8?
For Web Console help, edit the sunmc.docs.path entry in the /opt/SUNWsymon/web/console/smwebconf/smwebconf.properties file as follows:
sunmc.docs.path=docs.sun.com/app/docs/coll/810.8?
Workaround: Close the Host Details window and open it. The Hardware Summary table will be displayed.
In the Hardware tab of the Details window, the physical view of system is set to the front view irrespective of the current view. Also, the history shows only the front view.
Workaround: None.
When a Solaris x86 or Linux agent is upgraded either through the CLI/GUI installer or through Agent Update, the updated information is not automatically reflected in the topology.
Workaround: After the agent upgrade, modify the topology object manually.
On Solaris SPARC systems, Agent Update allows you to create an image that contains the X86/X64 Config Reader add-on. However, this add-on will not be installed on Solaris SPARC systems.
Workaround: While creating images for Solaris SPARC systems, select only the add-ons that are applicable.
When Sun Management Center services attempt to start after rebooting the system, they step onto cryptosvc service and kcfd daemon causing them to log errors in /var/adm/messages.
The following error messages might be displayed:
Oct 3 18:16:09 atqa32 lomv: 10/3/2005 23:16:9 GMT LOM time reference |
Oct 3 18:16:13 atqa32 kcfd[106]: kcfd: elfsign_hash_mem_resident failed to hash for /usr/lib/security/pkcs11_softtoken.so: sign or verify of ELF object failed |
Oct 3 18:16:13 atqa32 kcfd[106]: kcfd: elfsign_hash_mem_resident failed to hash for /usr/lib/security/pkcs11_softtoken.so: sign or verify of ELF object failed |
Oct 3 18:16:13 atqa32 esd[1949]: libpkcs11: /usr/lib/security/pkcs11_softtoken.so signature verification failed. See cryptoadm(1M). Skipping this plug-in. |
Oct 3 18:16:13 atqa32 esd[1949]: libpkcs11: /usr/lib/security/pkcs11_softtoken.so signature verification failed. See cryptoadm(1M). Skipping this plug-in. |
Oct 3 18:16:13 atqa32 cfgserver[1949]: syslog Oct 03 18:16:13 cfgserver Unable to get pkcs session. Can not initialize snmp engine |
Oct 3 18:16:13 atqa32 cfgserver[1949]: syslog Oct 03 18:16:13 cfgserver *** terminating execution *** |
Workaround: Before rebooting the system, stop all Sun Management Center services using es-stop -A. When the system reboots, all services will start without errors.
On Solaris 10 systems, Sun Management Center agent services are stopped during boot.
The following error messages might be displayed:
Oct 12 09:19:59 atqa33 metadata[6245]: [ID 985908 daemon.alert] syslog |
Oct 12 09:19:59 metadata {received software termination signal} |
Oct 12 09:19:59 atqa33 metadata[6245]: [ID 122441 daemon.alert] syslog |
Oct 12 09:19:59 metadata *** terminating execution *** |
Oct 12 09:19:59 atqa33 event[27957]: [ID 652029 daemon.alert] syslog |
Oct 12 09:19:59 event {received software termination signal} |
Oct 12 09:19:59 atqa33 event[27957]: [ID 721961 daemon.alert] syslog |
Oct 12 09:19:59 event *** terminating execution *** |
Oct 12 09:19:59 atqa33 agent[28990]: [ID 651061 daemon.alert] syslog |
Oct 12 09:19:59 agent {received software termination signal} |
Oct 12 09:19:59 atqa33 agent[28990]: [ID 891934 daemon.alert] syslog |
Oct 12 09:19:59 agent *** terminating execution *** |
Workaround: Before rebooting the system, stop the services using es-stop -A. In this case, error messages are not logged into the syslog file.
Sun Management Center database can contain duplicate entries of hosts when one of the following scenarios occurs:
The IP address is changed after installation.
The host name is changed after installation.
The host name has multiple host aliases.
Workaround:
Follow these recommendations to avoid duplicate entries:
Do not use composite objects.
Do not use the subnet or IP address range discovery.
Ensure that the host name is available in the /var/opt/SUNWsymon/cfg/domain-config.x file on the agent machine before adding it to the topology.
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 is not 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.
Workaround 1: Follow these steps:
Minimize the login screen and restore.
Type the input in the field that has the active cursor.
Position the cursor in the next field.
Minimize the login screen and restore.
Type the input in that field.
Workaround 2: Use JDK 1.4 or compatible versions.
When a zone agent is used as the base agent, Module Configuration Propagation (MCP) does not work with zone agents. Propagating the configuration data from MCP to a zone agent also fails.
The following error messages are logged in taskreq.log when MCP propagation with zone agent as base fails.
Http error : HTTP/1.1 404 File not found: /var/opt/SUNWsymon/mcp/procmon-zoneagentbase/index.xml |
The following error messages are logged in taskreq.log when MCP propagation to zone agent fails.
Operation mcp has failed on target:hostname:1161 Exception was thrown: /usr/bin/nawk: can't open file /var/opt/SUNWsymon/cfg/base-modules-d.dat.MCP |
Workaround: Edit the /var/opt/SUNWsymon/zone-scripts-d.dat file of zone agent to include es-mcp-get and es-mcp-put script names.
Workaround: None.
Workaround: None.
Run a Discovery request by specifying an IP range and selecting specific platform types. The request does not discover an object(s) if ALL the following conditions are true.
Default port option is selected in the Discover request.
Additional port to search on is also specified.
Both the default and additional ports are occupied on the host(s) being searched.
Workaround: Create separate Discover requests for Default port and additional port, if you want check both default port and an additional port on the objects being discovered.
Workaround: None.
Workaround: Task creation may fail when CST service is running. Use es-stop -x to stop CST service.
Workaround: Put sleep of two to three seconds in the called script.