Rule Engine

The Troubleshooting tips for Rule Engine are as follows:

Traps Not Received

Reason: The following may be the cause:

ACTIONID is not correctly mapped with the TFTTABLEID under SNMP_TRAP_ACTION_TABLE.
ACTIONID is not mapped to the TYPEID that refers to the SNMP_TRAP_ACTION_TABLE, under ACTION_TABLE
ACTIONID is not correctly mapped to the ACTIONSETID under ACTIONSET_TABLE
TRAP_FORWARDING_TABLE must have correct details of the manager such as port, host, hosttype of the manager.

Solution: Provide the exact mapping between tables for sending traps.

Reason: Other reasons can be related to the expressions evaluated during the rule engine.

Expression returns "false"
The variable or constant is not correctly mapped to the DATAID which in turn is not mapped to the correct table for mentioning the expression details using TYPEID
The details about the variable such as GROUPNAME, SUBID, and INSTANCE are specified wrong or misspelt.
The operator used in the expression is mentioned wrong.
The value for the constants hold a wrong data type mentioned by a table using TYPEID

Solution: Provide the related details once identifying the problem.

Email Not Received

Reason: The following may be the cause:

ACTIONID is not mapped to the TYPEID that refers to the EMAIL_ACTION_TABLE, under ACTION_TABLE.
ACTIONID is not correctly mapped to the EMAILID under EMAIL_ACTION_RELATION_TABLE that sends the email to the specified mail addresses.
ACTIONID mapping to the SERVERID may be wrong under EMAIL_ACTION_TABLE.
EMAILID mentioned under EMAIL_ADDRESS_TABLE may not be a valid mail ID.

Solution: Provide the exact mapping between tables and correct email address for sending email.

Reason: Other reasons can be related to the expressions evaluated during the rule engine as mentioned above in the last reason of "Traps Not Received" section.

Cannot Perform SET Operations

Reason:

ACTIONID is not mapped to the TYPEID that refers to the SNMP_SET_ACTION_TABLE, under ACTION_TABLE
ACTIONID is wrongly mentioned in SNMP_SET_ACTION_TABLE.

Solution: Provide the exact mapping between tables to perform SET operation.

Reason: The details of the managed object specified in the SNMP_SET_ACTION_TABLE to which the action is to be performed is invalid.

Solution: Specify the valid details such as the OID and its instance, value to be set and its data type.

Reason: The data type of the value to be set for the managed object, mentioned using the TYPEID is wrong

Solution: Check the data type that must be given as mentioned in the SNMP API Javadocs.

Reason: Other reasons can be related to the expressions evaluated during the rule engine as mentioned above in in the last reason of "Traps Not Received" section..

Cannot Stop the Traps/Mails that Gets Generated Continuously

Reason: This may happen when the rule engine is started in scheduler mode. The scheduler starts sending traps/mails once the expression is true and performs the action repeatedly by refreshing the rule file for every refresh time.

Solution: The rule engine can be operated in the triggered mode by disabling the scheduler mode. The scheduler refresh time can also be increased to avoid frequent generation of the traps/email. For more information on scheduler mode of execution, refer the Rule Engine section.

Note: Even in Scheduler mode, the traps/mails generated periodically depending on the refresh time, stops its generation once the condition becomes false. This again starts performing action when the condition becomes true.

Email Sent with Macros Does Not Work

Reason: The same macro name mentioned for another MACROID.
Solution: The Macro name must be unique. Hence check whether the MACROID has a unique macro name.

Reason: The DATAID mentioned in the MACRO_TABLE may not contain a valid data in its table referred using TYPEID.
Solution: Provide the exact data and correct mapping of DATAID to the MACROID.

Reason: The Macro name is not given between the "$" sign.
Solution: While specifying the macros, ensure that the macro name is mentioned between $ symbol, otherwise it will not be considered as macros, for eg $test$, where test is the macro name. Also ensure that the macro name mentioned in the EMAIL_ACTION_TABLE is the same as that of the macro name specified in the MACRO_TABLE to send message with macros.

Traps are Sent to Multiple Managers Even When Only One TrapForwardingTable is Set in the Rule File

Reason: This might be due to specifying the TFTABLEID to be 0 which will send the traps to all the entries specified in the TrapForwardingTable of the agent.

Solution: If the trap must be send to only the TrapForwardingTable mentioned in the TRAP_FORWARDING_TABLE of the rule file, then define a TrapForwarding entry in the table and give the TFTABLEID corresponding to that entry.

Ruleset Not Executed Even After Mapping to the AGENTID

Reason: Though the Ruleset is correctly mapped to the AGENTID, it may not get executed if STATUS column in the RULESET_TABLE is 0.

Solution: Make the STATUS to be 1 to enable the ruleset.

Rule Not Executed Even When Mapped to the RULESETID

Reason: Though the Rule is correctly mapped to the RULESETID, it may not get executed if the STATUS column in the RULEID is 0.

Solution: Make the STATUS to be 1 to execute the rules under the ruleset

Cannot Perform More Than One Action

Reason: ACTIONID mapping to the ACTIONSETID for the respective tables performing different actions is not done.

Solution: Different actions have there unique ACTIONID. In case more than one action needs to be performed, map them correctly to the ACTIONSETID.

Action is Not Performed for a Tabular Variable

Reason: This might be due to mentioning an instance value of wrong type, value, length etc.

Solution: Rule Engine supports tabular group with both index and external index. While mentioning INSTANCE for such tabular variable, the instance must be specified along with the length of the instance, index and external index. For eg, <INSTANCE>.6.87.23.56.35.24.67</INSTANCE>

Cannot Send Mail to More Than One Email Address

Reason: EMAILID is not properly mapped to the ACTIONID.

Solution: The EMAILID defines different email address in EMAIL_ADDRESS_TABLE. Hence mail can be sent to more than one email address by mapping the ACTIONID used for sending mails to the EMAILID under EMAIL_ACTION_RELATION_TABLE.

Cannot Set Values with Data Types Such as Timeticks, IPaddress etc for SET Action

Reason: The rule engine will not perform set operation if the values of data type are mentioned wrong.

Solution: To mention the data types are required for setting values in SET operation, specify them as defined in the SNMP API Javadocs. By default, the data type mentioned in the rule file are String and Integer.