Sysload Version 5.80

Sylvain DelangueSylvain Delangue lulTeam Automic Posts: 69 Journeyman ✭✭✭
edited October 2015 in Sysload - English

FAQs


Monitored Object does not register

Check Collector log file and look for "AutoDeclare - WARNING: could not register Monitored Object"
Check Management Server parameters in Collector configuration file, section "MS_SERVERS_DEF"

A Monitored Object appears as "n/d" in a view

Immediately after becoming a member of a MO Group, the MO appears in the Views containing the MO Group.
Go to the MO list and press "F5" to refresh the list.

MO does not appear right away in the Monitored Object list

MO list refresh not dynamic when a MO is added in Management Server.
Press F5.
Note: The MO is added to the MO Groups right away; hence views may contain the new MOs with "n/a" until MO list is refreshed.

When editing an Enterprise Model, some Monitored Objects do not appears in the field "To update"

This can be expected.
MOs that are part of configuration automation do not appear in the "To update" field. The Agent will download the configuration.
Only the MOs that are not part of configuration automation are listed and need manual update (e.g. Agent versions < 5.80)

Error obtained when forcing EM preparation

Expected on Agents in versions < 5.60


Example:

http://vmstm2k8856:9900/services/sldmgts/sldapi/api_execute?method=cfgsvrforceemdistribution&username=admin&password=sysload&outputformat=html&showheader=1&waitforcompletion=1&returnforcemodeployreport=1

#    type    name        instance    moname        status    message
1    NT      vmstminf04              vmstminf04    0         Error while receiving reply header



API indicates MO configuration should be deployed although the MO config is up to date

The Management Server API queries "cfgsvrforceemdistribution" and "cfgsvremgetdeployreport" may indicate MO configuration is not up to date.
Check the Agent is in version 5.80 and that configuration automation is activated.
The API ignores the fact automation is activated or not, hence MOs show as not up to date.

The MO is listed in the field "To update", it means the Agent does not use configuration automation.

The configuration for the MO appears in the result of the query "cfgsvrforceemdistribution".


Resources

Sample Sysload Modules Entities

https://marketplace.automic.com/details/sample-entities-for-sysload-modules


Application KDB

https://marketplace.automic.com/details/application-knowledge-database


Dynamic command line setup for the Agent for Windows

https://marketplace.automic.com/details/dynamic-setup-for-windows-agent

Sign In or Register to comment.