Configuration
Error starting syslogTrap process:
You must have the Syslog Integration functionality enabled before starting the syslogTrap background process.
To enable the Syslog Integration functionality in NNM standalone configurations, see “Configuring Syslog Integration for NNM Standalone” on page 18.
To enable the Syslog Integration functionality in OVO with NNM configurations, see “Configuring Syslog Integration for OVO with NNM” on page 21.
To start the syslogTrap process, execute:
ovstart syslogTrap
Seeing Duplicate Syslog Messages in Message Browser: This could be caused by a number of reasons, including one of the following:
• In OVO with NNM configurations, you must enable the message stream interface for both the Syslog to NNM template and the OVO agent on the NNM management station in order for syslog messages to be processed as documented. However, in OVO, there are a multitude of combinations for diverting messages through the system. For example, you can enable the message stream interface for individual conditions of a template to copy messages as well as enabling the message stream interface for the template to copy messages. This will produce multiple messages in the message browser.
• Templates are not ordered, meaning that if messages match
conditions of multiple templates, multiple messages are displayed in the message browser. For example, if a wildcard template is assigned and installed on a system, then every message entering the agent is forwarded to the message browser. Furthermore, if additional templates are assigned and installed on a system, then those messages matching the conditions of the templates are also
forwarded to the message browser. Thus, duplicate messages appear in the message browser, formatted according to rules in the
Configuration
Not Seeing Syslog Messages in Message Browser
This could be caused by many reasons, including one of the following: • The Syslog to NNM template is not installed or enabled on the OVO
agent system (on the NNM management station). To verify that the
Syslog to NNM template is installed and enabled on the OVO agent, execute:
$OV_BIN/OpC/opctemplate
This command lists all templates with the type, name, and status (enabled or disabled). This command is helpful to check whether a template you have assigned to an agent node has successfully been installed on that agent system. Be aware that this command does not indicate which version of the template has been deployed. If you have made modifications to any assigned templates, you must reinstall the templates on the managed nodes.
• For OVO with NNM configurations, the message stream interface is not enabled for either the Syslog to NNM template or the OVO agent on the NNM management station.
To isolate the problem, you can turn on XPL tracing for the
syslogTrap process. If you see no activity in incoming messages, it usually means that the message stream interface has not been enabled in all places that must be enabled.
Troubleshooting Tips
A
Agent MSI
,
22Application
OVO template condition field
,
41C
Condition Text field
,
35configuration options
,
7custom message attributes (CMAs)
,
41,
43D DCE requirements
,
16 DCE RPC,
16 DCE-KT-Tools,
16 deployment options,
7 L logger,
19,
24 M Message GroupOVO template condition field
,
41Message on Matched Condition OVO template condition field
,
40message source templates overview
,
29Message Source Templates interface
,
11,
21,
30assigning templates
,
22installing templates
,
22modifying logfile location
,
23starting
,
31message stream interface (MSI)
,
21Message Text
OVO template condition field
,
39,
41Message Type
OVO template condition field
,
41message type NNMsyslog_
,
7,
41MSI
enabling OVO agent
,
22enabling template
,
21 N NIS syslog requirement,
17 NNM starting,
36 NNM standalone configuration configuring syslog monitoring,
11deploying
,
12 deploying templates,
46 described,
7 disabling,
25 setting up,
12,
18 testing,
19NNMsyslog_ message type
,
7,
41NNMsyslogTraps
,
21Node
OVO template condition field
,
39,
40O Object
OVO template condition field
,
41opc
starting OVO
,
11opc_op
add OVO user locally
,
17opccfgupld
,
21 opcpat,
46 opctemplate,
53 OV_Syslog_FrameDLCI_Active,
13 OV_Syslog_FrameDLCI_Inactive,
13 OV_Syslog_LineProtoDown,
13 OV_Syslog_LineProtoUp,
13 OV_Syslog_LinkDown,
13 OV_Syslog_LinkUp,
13 OV_Syslog_OSPF_Neighbor_Down,
13 OV_Syslog_OSPF_Neighbor_Up,
13 OVO agent in NNM standalone configuration,
7,
12,
29in OVO with NNM configuration
,
9OVO server
in OVO with NNM configuration
,
9OVO template condition field Message Group
,
41Message Text
,
41Message Type
,
41Node
,
40Service Name
,
41OVO with NNM configuration described
,
9disabling
,
25,
47setting up
,
12,
21testing
,
24ovsyslogcfg
,
11,
18,
19,
30ovtrap2opc
,
24in OVO with NNM configuration
,
10P pmd
in NNM standalone configuration
,
8in OVO with NNM configuration
,
10S
Service Name
OVO template condition field
,
41setupSyslog.ovpl
,
11 -deploy option,
12,
46 -disable option,
25,
46,
47 -help option,
11 -server option,
12,
21 -standalone option,
12,
18 SNMP Traps template,
24Suppress Matched Condition OVO template condition field
,
39Suppress Unmatched Condition OVO template condition field
,
40Syslog FRAME DLCI Active
,
34Syslog FRAME DLCI Inactive
,
34Syslog FRAME DLCI Invalid
,
34Syslog Integration configuring
,
18,
21described
,
6disabling
,
46,
47removing
,
25Syslog LINEPROTO down
,
34Syslog LINEPROTO up
,
34Syslog LINKDOWN
,
34Syslog LINKUP
,
34Syslog OSPF Adjacency down
,
34Syslog OSPF Adjacency up
,
34Syslog to NNM template
,
8,
10,
12,
29assigning to agent
,
22Condition Text field
,
35conditions
,
33deploying
,
46in NNM standalone configuration
,
35in OVO with NNM configuration
,
38syslog trap mappings
,
13uploading in OVO with NNM configuration
,
21Syslog Trap Mapping Configuration interface
,
30 starting,
11 syslog.log,
50 syslogTrap,
18,
21 error starting,
52 in NNM standalone configuration,
7,
12in OVO with NNM configuration
,
10starting in OVO with NNM configuration
,
23,
47stopping in NNM standalone configuration
,
46stopping in OVO with NNM configuration