<EventDest>
<Destination id="0" type="T" default="y" >
<Srv location="xx.xx.xx.xx" port="5529" />
</Destination>
</EventDest>
You will see the following in the *LG0 log file:
1090918140248857KRAX002I XML begin tag Srv unrecognized XML Parser
1090918140323448KRAX003I XML end tag Srv unrecognized XML Parser
If you have a problem with the value in the xml file, you need to check the agent
log file. For example, if you misspell the value in the pc_eventmap.map file as
follows:
<itmEventMapping:agent
xmlns:itmEventMapping="http://www.ibm.com/tivoli/itm/agentEventMapping"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.ibm.com/tivoli/itm/agentEventMapping
agentEventMap.xsd">
<idUD/id>
<version>6.2.0</version>
<event_mapping>
<situation name="UDB_Buff_Used_Pct_Warn_pr">
<class name="ITM_KUDINFO00"/>
<slot slotName1="msg">
<mappedAttribute name="Incorrect slotName"/>
</slot>
</event_mapping>
You will see the following errors in the agent log:
(4AB91AF5.0005-2:kraaeevx.cpp,686,"process_Slot_Tag") <slotName> attribute
not specified for element <slot>
(4AB91AF5.0006-2:kraaeevx.cpp,192,"IRA_EIF_endXMLElement") Null Emb
<110A05EB0> or Esb <NULL> processing slot end element.
(4AB91AF5.0007-2:kraaeevm.cpp,788,"processMapFile") Event map parsing error.
Map entries from file
</data/achan/private_situation/ud_eventmap.map> not added.
Subnode Limitations for autonomous function
The Service Interface has the following limitations when working with subnode
agents:
v The Queries Link has been removed and is not supported for subnode agents.
v The Situations Link only shows situations from the agent instance level. While
situations can be distributed to run on specific subnodes, the Situations page
does not filter by subnode, so all situations for all subnodes defined in the agent
instance are shown.
v The History views show metrics for all subnodes combined in a single table.
Currently, the service interface does not allow filtering by subnode.
SNMP alerts sent from the monitoring agent have some limitations when working
with subnodes. Currently, the monitoring agent does not support situation
attribute atomization. This means that for a situation that returns multiple rows
from a table, an SNMP alert is only sent for the first row returned. For example, a
situation called Low_Disk_Space will trigger if available_disk_space *LE 20% might
be true for more than 1 disk at a time. An enterprise situation would define the
disk name as the display item so a separate situation alert would be displayed for
each disk with less than 20% free space available.
178 IBM Tivoli Monitoring: Troubleshooting Guide
To Next Page
Loading...
Need help?
General
