IBM E027SLL-H - Tivoli Monitoring - PC, Troubleshooting Manual

Page: 198 / 310

Calendar entries overlap
After an upgrade, the calendar entries for PrimeShift and NonPrimeShift might
have overlaps for hours 8 and 17. The default PrimeShift and NonPrimeShift
calendar entries should look as follows:
Name: NonPrimeShift
Type: CRON
Data: * 0,1,2,3,4,5,6,7,17,18,19,20,21,22,23 * * 1-5
Name: PrimeShift
Type: CRON
Data: * 8-16 * * 1-5
To correct the problem, use the
tacmd editcalendarentry
command to correct the
calendar overlaps so that the calendar entries look as shown above.
Receive an error when deploying an System Service Monitor agent
When deploying a System Service Monitor agent using a hub monitoring server
outside a firewall through a remote monitoring server inside the firewall to a client
inside the firewall, this error occurs:
KDY3010E: The SNMP command installSSM
timed out with an SNMP return code of 0. The SNMP command timed out because
there was a network error, or the agent was stopped, or the specified SNMP
community/user does not have write and create privileges.
This happens because the SNMPPORT is not available to use. The default
SNMPPORT is 161. You should try to specify a different SNMPPORT to use when
deploying the agent. Here is an example command:
tacmd createNode -h
smb://target_endpoint_hostname -p snmpport=4567 server=RTEM_hostname -u
user_id -w password -t ssm
The Agent Service Interface is not globalized
This window is only displayed in English. There is not a workaround for this
issue.
Some attribute group names are unintelligible from the History
Collection Configuration window
If you have configured historical collection for the monitoring agents and
upgraded to IBM Tivoli Monitoring v6.2.2, you might notice that the names listed
for attribute groups are now unintelligible.
In some cases, these names are not friendly and hovering over the item on the
navigation tree shows the attribute group to which it belongs. You can alter the
name of these collections by editing the historical collection and modifying only
the name.
History collection fails to display the most recent 24 hours of data
When requesting a display of the historical availability for beyond 24 hours, the
most recent 24 hours of data was not displayed, only the 48 hours (previous to the
current 24) was displayed. This seems to be a case where data is retrieved correctly
from the long-term store in the warehouse but is not retrieving data from the local
short term history.
180
IBM Tivoli Monitoring: Troubleshooting Guide