======================================================================
Halcyon Monitoring Solutions
www.HalcyonInc.com
Neuron Management Suite
Version 1.16.0
README.config
======================================================================
Overview
======================================================================
This README.config file describes how to configure the adapters and
modules that make up this distribution as well as how to access the
Neuron Management Portal.
The following sections describe how to setup users and login to the
Halcyon Neuron Management Portal to perform additional configuration
tasks found in the sections that follow:
Halcyon Neuron Management Portal Users
Logging into the Halcyon Neuron Management Portal
After Halcyon Neuron Management Suite is installed, the following
adapters, integration solutions, and modules can be enabled, disabled
and configured via the Neuron Management Suite's Server Configuration
page (see "Accessing Server Configuration Page" below).
- Halcyon Generic Adapter
- Halcyon Email Adapter
- Halcyon Message Logger
- Halcyon Neuron Integration for Oracle Enterprise
Manager Ops Center
- Halcyon Neuron Integration for IBM Tivoli
- Halcyon Neuron Integration for IBM Tivoli Netcool
- Halcyon Neuron Integration for BMC Event Manager
- Halcyon Neuron Integration for HP OpenView
- Halcyon Neuron Integration for Sun Management Center
- Halcyon Neuron Integration for Oracle Grid Engine
- Halcyon Neuron Module for Generic Hardware
- Halcyon Neuron Module for Linux Base
- Halcyon Neuron Module for Solaris Base
- Halcyon Neuron Module for Solaris Virtualization
- Halcyon Neuron Module for Windows Base
- Halcyon Neuron Module for Cisco Base
- Halcyon Neuron Agent Module
Inbound rules for SNMP traps and Oracle Enterprise Manager Ops Center
notifications as well as response rules for processed events can be
configured via the Event Manager ("Manage Events" via Events tab
Actions panel; see NeuronEventManager_[VERSION]_UsersGuide.pdf for
more details).
The following sections contain additional instructions that are
needed to configure the above listed components:
1. Halcyon Generic Adapter Configuration Instructions
1.1 Configuration of Generic Adapter: Send Snmp Traps
1.2 Configuration of Generic Adapter: Call a Script
2. Halcyon Email Adapter Configuration Instructions
3. Halcyon Message Logger Configuration Instructions
4. Halcyon Neuron Integration for Oracle Enterprise
Manager Ops Center Configuration Instructions
4.1 Pre-Configuration: Create Ops Center Integration User
4.2 Integration Configuration: Connection Credentials
4.3 Integration Configuration: JMX Server
4.4 Integration Configuration: Inbound and Outbound
4.5 Integration Configuration: Notification Recipients
5. Halcyon Neuron Integration for IBM Tivoli Configuration
Instructions
5.1 Integration Configuration: Set up a Tivoli Action
5.2 Integration Configuration: Postemsg Binary
5.3 Integration Configuration: Tivoli Action Configuration
5.4 Integration Configuration: Baroc File
5.5 Integration Configuration: Rules File
6. Halcyon Neuron Integration for IBM Tivoli Netcool Configuration
Instructions
6.1 Integration Configuration: Action Configuration
6.2 Integration Configuration: Netcool Configuration
6.3 SNMP MIB Files
7. Halcyon Neuron Integration for BMC Event Manager Configuration
Instructions
7.1 Integration Configuration: Action Configuration
7.2 SNMP MIB Files
8. Halcyon Neuron Integration for HP OpenView Configuration
Instructions
8.1 Integration Configuration: Action Configuration
8.2 SNMP MIB Files
9. Halcyon Neuron Integration for Sun Management Center
Configuration Instructions
9.1 Configuration of Sun Management Center Server Adapter
9.2 Configuration of Sun Management Center Agent Adapter
9.3 Remote Acknowledgement of Sun MC alarms
10. Halcyon Neuron Integration for Oracle Grid Engine Configuration
Instructions
10.1 Include Oracle Grid Engine Libraries for Integration
10.2 Configuration of Oracle Grid Engine Master Hosts
11. Halcyon Neuron Module for Generic Hardware Configuration
Instructions
11.1 Configuration: IPMI Connection Default Credentials
11.2 Configuration: IPMI Enabled Hosts
11.3 Configuration: Syslog
12. Halcyon Neuron Module for Linux Base Configuration Instructions
12.1 Configuration: Syslog
13. Halcyon Neuron Module for Solaris Base Configuration Instructions
13.1 Configuration: Syslog
14. Halcyon Neuron Module for Solaris Virtualization Configuration
Instructions
15. Halcyon Neuron Module for Windows Base Configuration Instructions
16. Halcyon Neuron Module for Cisco Base Configuration Instructions
17. Halcyon Neuron Agent Module
18. Halcyon Event Manager Configuration Instructions
18.1 Configuration of Event Manager: User Interface
18.2 Configuration of Event Manager: Rule Matching (Inbound)
18.3 Configuration of Event Manager: Rule Matching (Response)
Halcyon Neuron Management Portal Users
======================================================================
The Management Portal requires authentication. Please note that during
installation the default user admin is set up with a secure password.
In order to change the default password of this user or to create
additional users use the User Manager utility. For information on
managing users see section 4 User Management of the Neuron Management
Server User's Guide.
Logging into the Halcyon Neuron Management Portal
======================================================================
To actually login to the Management Portal, use the URL provided at
the end of the installation:
https://<hostname>:<port>/portal
The hostname is the name of the host that the Neuron Management
Suite was installed.
The port number can be found in the managementPortal.config file
located in the [LOCALDIR]/conf directory for future reference.
Accessing Server Configuration Page
======================================================================
Please follow these steps to access the server configuration page for
the Neuron Management Server and all install modules and adapters:
1) Log into the Neuron Management Portal (see Logging into the
"Halcyon Neuron Management Portal" above).
2) Select "Neuron Topology" from the drop-down selector at the top of
the left hand panel (default selection will be "Systems Topology").
3) Expand any collapsed branches (click the + box) and click "Control
Agent" to select it.
4) Selecting "Control Agent" will make the "Server Configuration" and
"Licensing" tabs available (top center of the screen).
5) Click the "Server Configuration" tab to access the server
configuration page.
6) Make any necessary configuration changes here.
NOTE: The Server Configuration and Licensing tabs are only available
via the Control Agent. Deselecting the Control Agent or
selecting another node in the Neuron Topology will remove the
tabs and you will end up on the Events tab if you were on one
of them. The same will happen if you change to another Topology
(i.e. change back to the Systems Topology).
"Server Configuration" vs. "Configuration" Tabs
----------------------------------------------------------------------
The "Server Configuration" tab was introduced in 1.13.0 and contains
everything that was in the "Configuration" tab in prior versions.
The "Configuration" tab now in 1.13.0 and in all future versions
is the user interface for the Neuron Configuration Manager. It
displays configuration data for all discovered assets that are
managed and have credentials. Please refer to the following guide
for more information on the Configuration Manager:
- NeuronConfigurationManager_[VERSION]_UsersGuide.pdf
1. Halcyon Generic Adapter Configuration Instructions
======================================================================
NOTE: [LOCALDIR] is typically /var/opt/HMF
1.1 Configuration of Generic Adapter: Send Snmp Traps
----------------------------------------------------------------------
1) The MIBs for the Halcyon Generic Adapter are located at:
[LOCALDIR]/conf/module/GenericAdapter_v1.mib
[LOCALDIR]/conf/module/GenericAdapter_v2.mib
(for v1 and v2 traps respectively).
A description of these MIBs can be found at:
[LOCALDIR]/conf/module/GenericAdapter.txt
2) To enable the sending of Snmp Traps when fault events occur,
create a rule in the Event Manager
(NeuronEventManager_[VERSION]_UsersGuide.pdf) which includes
"Send an SNMP trap" action.
3) You can specify the type of SNMP trap to send (either V1 or V2),
the SNMP community, and one or more hosts where the SNMP traps
are sent to via the Neuron Management Suite's Server Configuration
page (see "Accessing Server Configuration Page" above), by editing
properties for GenericAdapter.
In order to specify the SNMP agent host the following values can
be set via the same Server Configuration page:
- source: take the IP address from the event that is processed
- server: use the Neuron server's IP address
- IP: specify a specific IP address
For SNMP v1 traps the agent host is set directly in the trap's
header. For SNMP v2 traps the snmpTrapAddress varbind with OID
1.3.6.1.6.3.18.1.3.0 is set instead.
NOTE: Any trap destinations defined here are only used if the
rules that specify the SNMP trap action do not also
specify the trap destination.
4) To disable the sending of SNMP traps when fault events occur,
remove the action from the rule via the Event Manager
(NeuronEventManager_[VERSION]_UsersGuide.pdf).
1.2 Configuration of Generic Adapter: Call a Script
----------------------------------------------------------------------
1) To enable the execution of one or more scripts when fault events
occur, create a rule in the Event Manager
(NeuronEventManager_[VERSION]_UsersGuide.pdf) which includes "Run
a script" action.
2) You can specify one or more scripts to be called via the Neuron
Management Suite's Server Configuration page (see "Accessing
Server Configuration Page" above), by editing properties for
GenericAdapter.
IMPORTANT: If the script is not being specified by an absolute
path, then the script must be located in the Neuron
Management Suite's bin directory ([LOCALDIR]/bin).
NOTE: Any scripts defined here are only used if the rules that
specify the script action do not also specify the scripts.
4) To disable the execution of scripts when fault events occur, remove
the action from the rule via the Event Manager
(NeuronEventManager_[VERSION]_UsersGuide.pdf).
2. Halcyon Email Adapter Configuration Instructions
======================================================================
To enable the Email Adapter, please update the "mailHost" configuration
properties of EmailService in the Neuron Management Suite's Server
Configuration page (see "Accessing Server Configuration Page" above)
with your own mail server.
3. Halcyon Message Logger Configuration Instructions
======================================================================
The Message Logger module is loaded by default. It logs all events
that have been received by the Halcyon Neuron Management Suite. Please
note that not only external but also internal events are logged.
The location of the default Message Logger log is:
[LOCALDIR]/logs/messageLogger.log
(where [LOCALDIR] is typically /var/opt/HMF)
This log file is limited in size. It is also rotated once the maximum
file size has been reached. See the Message Logger configuration in
the Neuron Management Suite's Server Configuration page (see
"Accessing Server Configuration Page" above).
It is also possible to configure additional log files. This is done
via the Neuron Management Suite's Server Configuration page (see
"Accessing Server Configuration Page" above), by editing properties
for the MessageLogger module. The following properties can be set:
- messageLogs: Specifies the number of temporary log files to be
created. Set this value to 0 if no log files are
required. No further configuration is then needed.
If this value is set to greater than 0 then for each
temporary log file the following parameters must be
defined.
- messageLogEnabled: Specifies whether the message log is enabled.
- messageLogFile: Specifies the name of the message log file.
- messageLogType: Specifies the type of message to log. Even
though this could be any Neuron Management Suite
message class only the following two are supported
at this time:
com.halcyoninc.primealert.hmf.message.event.RawEvent
These are external events received by the Halcyon
Neuron Management Suite.
com.halcyoninc.primealert.hmf.message.data.PerformanceData
These are performance data messages received by
the Halcyon Neuron Management Suite.
- messageLogSubType: Specifies the sub-type of message to log.
This value should not be changed without
contacting Halcyon support.
- messageLogLimit: Specifies the maximum number of bytes to write to
the log file. When this number is exceeded the log
file is removed.
4. Halcyon Neuron Integration for Oracle Enterprise Manager Ops Center
Configuration Instructions
======================================================================
This section describes how to configure the Neuron Integration for
Oracle Enterprise Manager Ops Center. It consists of the following
sub-sections:
4.1 Pre-Configuration: Create Ops Center Integration User
4.2 Integration Configuration: Connection Credentials
4.3 Integration Configuration: JMX Server
4.4 Integration Configuration: Inbound and Outbound
4.5 Integration Configuration: Notification Recipients
4.1 Pre-Configuration: Create Ops Center Integration User
----------------------------------------------------------------------
In order to receive notifications from Oracle Enterprise Manager Ops
Center, an existing Ops Center user must be specified in the
Integration for Oracle Enterprise Manager Ops Center configuration.
The Integration for Oracle Enterprise Manager Ops Center automatically
deletes notifications from the specified Ops Center user as they are
processed. Therefore it is strongly recommended that a dedicated user
be setup for exclusive use by this Neuron Integration for Oracle
Enterprise Manager Ops Center.
1) To create a new user for the Neuron Integration for Oracle
Enterprise Manager Ops Center, first you must create a new user
on the system where Ops Center is running. If you do not know how
to do this or are unable to do this, please contact your System
Administrator.
NOTE: While you can pick any username you want, it should be one
that associates the user with the Halcyon Integration.
Some recommendations include the following possible users:
- halcyon_opscenter
- halcyon_neuron
- halcyon_integration
2) Once the new user is created on the system, log into the Ops
Center console as an admin user and browse to the
Administration section.
3) In the Administration section, there should be a tab labeled
"Users". Click on this tab.
4) On the Users tab, click on the Add User icon, enter the new user
name in the dialog that appears and then click Add User.
5) The new user created on the system in step 1 is now an Ops
Center user, using the same password as setup in step 1.
6) The new user should be assigned "All Assets" admin privileges
in order to receive all notifications. Please perform the
following:
- Go to Administration.
- Click the "Roles" tab.
- Select the new user.
- Click "All Assets".
- Click the pencil "Edit" icon.
- Check the "Admin" box on "All Assets".
NOTE: To receive connectivity and security alerts, check
the "Admin" box on "Enterprise Controller".
7) Create a notification profile for the new user by performing
the following:
- Go to Administration.
- Click the Enterprise Controller.
- Click the User tab.
- Click the Configure Notification Profile icon.
- Click the "User Interface" drop-down list
- Select an appropriate notification severity.
To receive all notifications, select "Notification Priority >= LOW".
Receiving all notifications is recommended by Halcyon.
To not receive all notifications, please select an appropriate
choice under the "User Interface" drop-down list. For example,
by selecting "Problems Severity >= INFO" only problem type
notifications will be received.
In addition, clicking "Subscribe to Custom Filtered Notifications"
filters out notifications based on the user's selections.
8) Test that the user is properly configured by generating a
notification within Ops Center and verifying the new user
actually received the notification.
If the integration user did NOT receive the notification,
please consult your Ops Center admin to resolve any
problems.
IMPORTANT: The Neuron Integration for Oracle Enterprise
Manager Ops Center will not work if the configured
user does not receive Ops Center notifications.
4.2 Integration Configuration: Connection Credentials
----------------------------------------------------------------------
The Neuron Integration for Oracle Enterprise Manager Ops Center works
by connecting to the Ops Center JMX server. In order to do this, a
user name and password is required.
NOTE: If you need to setup multiple connections to integrate with
several Ops Center installations, please contact Halcyon
Support.
To configure the user name and/or password used to connect to Ops
Center, in the Neuron Management Suite's Server Configuration page
(see "Accessing Server Configuration Page" above), select
OpsCenterAdapter and then click "Edit". In the Connections tab, edit
the User and Password fields.
4.3 Integration Configuration: JMX Server
----------------------------------------------------------------------
The Neuron Integration for Oracle Enterprise Manager Ops Center works
by connecting to the Ops Center JMX server. In order to do this, the
host and JMX port of the Ops Center server is required.
To configure the Ops Center JMX Server to connect to, in the Neuron
Management Suite's Server Configuration page (see "Accessing Server
Configuration Page" above), select OpsCenterAdapter and then click
"Edit". In the Connections tab, edit the URL field, type your Ops
Center host and JMX port.
If you do not know what the host or port values should be, please
consult your Ops Center admin.
NOTE: The port should be in the cacao.properties file under
com.sun.cacao.jmxmp.connector.port.
For Ops Center 11g and later, the file should be located in
the following directory:
/etc/cacao/instances/oem-ec/private/
If there is no /etc/cacao/instances/oem-ec/ directory, then
check for the default file here:
/etc/cacao/instances/default/private
For Ops Center 2.5 and earlier, the default location of
this file is:
/etc/cacao/instances/default/private
4.4 Integration Configuration: Inbound and Outbound
----------------------------------------------------------------------
Each JMX connection to an Ops Center server can be configured to
receive notifications from Ops Center (inbound) and/or send
notifications to Ops Center (outbound) when events are received
by the Halcyon Neuron Management Suite.
NOTE: Inbound uses the Connection user configured in section 4.2 while
outbound uses the usersToNotify. In addition, the inbound and
outbound user(s) may have different notification privileges.
Both inbound and outbound communication are disabled by default. In
the Neuron Management Suite's Server Configuration page (see
"Accessing Server Configuration Page" above), select OpsCenterAdapter
and then click "Edit". In the Connections tab, you can enable inbound
or outbound by checking it or disable inbound or outbound by
un-checking it.
4.5 Integration Configuration: Notification Recipients
----------------------------------------------------------------------
In order to have events from the Halcyon Neuron Management suite sent
to Ops Center users as notifications, the adapter will need to be
configured with a list of users who should receive these notifications.
After the adapter is configured as indicated below, one or more Neuron
Rules will need to be setup with an Ops Center action indicating
that Neuron Events should be forwarded to Ops Center. Neuron
Rules can be created using the Halcyon Neuron Event Manager
(NeuronEventManager_[VERSION]_UsersGuide.pdf).
NOTE: In Ops Center, each user receives their own notifications.
If you wish to send notifications to all users, you will need
to list out all users in this configuration.
NOTE: By default, notifications will be sent to everyone who is an
Ops Center Domain Authorized User.
NOTE: If you need to setup/integrate with multiple Ops Center
installations, please contact Halcyon Support.
To configure Ops Center users who would receive the outbound
notifications, in the Neuron Management Suite's Server Configuration
page (see "Accessing Server Configuration Page" above), select
OpsCenterAdapter and then click "Edit". In the Connections tab, edit
the Users To Notify field.
IMPORTANT:
==========
- If you include the same user more than once, injection of events
into Ops Center will fail.
- If a user is specified here, but also occurs in one or both of
domainAuthorizedUsers and serverAuthorizedUsers, no problems occur.
- If a user specified is not a valid Ops Center user, injection
of events into Ops Center will fail.
5. Halcyon Neuron Integration for IBM Tivoli Configuration
Instructions
======================================================================
This section describes how to configure the Neuron Integration for IBM
Tivoli. It consists of the following sub-sections:
5.1 Integration Configuration: Set up a Tivoli Action
5.2 Integration Configuration: Postemsg Binary
5.3 Integration Configuration: Tivoli Action Configuration
5.4 Integration Configuration: Baroc File
5.1 Integration Configuration: Set up a Tivoli Action
----------------------------------------------------------------------
In order to use the Neuron Integration for IBM Tivoli, a Tivoli action
must be defined in a rule via the Neuron Event Manager
(NeuronEventManager_[VERSION]_UsersGuide.pdf), which will forward
Neuron Events to IBM Tivoli.
The Halcyon Neuron Event Manager should be used to setup a Tivoli
Adapter action within a rule. When the given rule matches an incoming
event, the Tivoli action will be triggered and the event will be
forwarded to the Tivoli server specified with the action.
5.2 Integration Configuration: Postemsg Binary
----------------------------------------------------------------------
For the Neuron Integration for IBM Tivoli to get messages into Tivoli,
the "postemsg" binary has to be in [LOCALDIR]/bin.
Alternatively, a symbolic link can be created in [LOCALDIR]/bin
and pointed to the actual "postemsg" binary.
5.3 Integration Configuration: Tivoli Action Configuration
----------------------------------------------------------------------
The Neuron Integration for IBM Tivoli can be configured to send
messages to IBM Tivoli using the "postemsg" binary mentioned above in
one of two ways:
1) You can create an IBM TEC configuration file and provide a path to
this file when you setup the IBM Tivoli action (as outlined above).
OR
2) When creating the IBM Tivoli action, you can specify the IBM
Tivoli host to send the event to.
NOTE: Depending on how you have IBM Tivoli configured, you may
need to use a TEC configuration file. For instance, you may
need to specify a custom Tivoli cache file accessible by
user "halcyon" by including a BufEvtPath in a TEC
configuration file. For example:
BufEvtPath=/var/opt/HMF/logs/HMFAdapterTivoli.cache
If you are attempting to forward Neuron Events to Tivoli you
will need to specify the configuration option above if you
see this error message:
error in opening cache file /etc/Tivoli/tec/cache
You may also need to specify the specific Tivoli Server Port
by including a ServerPort in a TEC configuration file.
For example:
ServerPort=5529
If you are attempting to forward Neuron Events to Tivoli
running on a Windows system you will need to specify the
ServerPort configuration option because Windows does not run
the portmapper that Unix does. If you do not provide the port
in a TEC configuration file, you will see this error message:
tec_put_event failed, errno = 38
5.4 Integration Configuration: Baroc File
----------------------------------------------------------------------
The Tivoli baroc file for the Neuron Integration for IBM Tivoli is
located at:
[LOCALDIR]/conf/module/TivoliAdapter.baroc
5.5 Integration Configuration: Rules File
----------------------------------------------------------------------
The Tivoli rules file for the Neuron Integration for IBM Tivoli is
located at:
[LOCALDIR]/conf/module/TivoliAdapter.rls
6. Halcyon Neuron Integration for IBM Tivoli Netcool Configuration
Instructions
======================================================================
This section describes how to configure the Neuron Integration for IBM
Tivoli Netcool. It consists of the following sub-sections:
6.1 Integration Configuration: Action Configuration
6.2 Integration Configuration: Netcool Configuration
6.3 SNMP MIB Files
6.1 Integration Configuration: Action Configuration
----------------------------------------------------------------------
In order to use the Neuron Integration for IBM Tivoli Netcool, a
Netcool action must be defined in a rule via the Neuron Event Manager
(NeuronEventManager_[VERSION]_UsersGuide.pdf), which forwards Neuron
Events to Netcool.
The Halcyon Neuron Event Manager should be used to setup an IBM Tivoli
Netcool action within a rule. When the given rule matches an incoming
event, the Netcool action will be triggered and the event will be
forwarded to the IBM Tivoli Netcool server specified with the action.
It is possible to specify default values for the type of SNMP trap to
send (either V1 or V2), SNMP community, SNMP targets, and SNMP agent
host via the Neuron Management Suite's Server Configuration page (see
"Accessing Server Configuration Page" above), by editing properties for
NetcoolAdapter. Also see "Halcyon Generic Adapter Configuration
Instructions" above for more details on these values.
6.2 Integration Configuration: Netcool Configuration
----------------------------------------------------------------------
The following instructions apply to IBM Tivoli Netcool/OMNIbus 7.2.
integration with other versions of Netcool OMNIbus may vary.
1. From the Halcyon Neuron Management Suite server host, copy the
following rule file:
[BASEDIR]/conf/module/NetcoolAdapter.rules
to a filesystem on the Netcool server or a shared filesystem
accessible to the Netcool server. This file contains a set of
rules which handle the enterprise specified snmp traps with
generic trap-type = 6.
[BASEDIR] can be determined by running the following command:
# pkgparam HALhmfcon BASEDIR
2. Append the contents of the file "NetcoolAdapter.rules" to the end
of the Netcool MTTrapd Probe configuration file:
${OMNIHOME}/probes/solaris2/mttrapd.rules
using the following command:
# cat NetcoolAdapter.rules >>
${OMNIHOME}/probes/solaris2/mttrapd.rules
where ${OMNIHOME} refers to the base installation directory of the
Netcool/OMNIbus software package.
It is strongly recommended that a new Alert Class be created in
all Netcool ObjectServers expected to receive events from Halcyon
Neuron Management Suite. This allows greater flexibility and ease
in identifying and managing Halcyon Neuron Management Suite events
in a Netcool environment. Remember that the class id of alerts
originating from Halcyon Neuron Management Suite must be updated
accordingly in the mttrapd.rules to match the id of the newly
created Omnibus class.
3. If you have not started the Netcool ObjectServer, run the
following command as root to launch it:
# ${OMNIHOME}/bin/nco_objserv -name <server_name>
where <server_name> is the name of the Netcool ObjectServer.
4. Check if the Netcool MTTrap Probe process is running with the
following command:
# ps -ef | grep nco_p_mttrapd
5. If the Netcool MTTrapd Probe process nco_p_mttrapd is already
running, send a HUP signal to force the MTTrapd Probe to read
the updated "mttrapd.rules" file using the following command:
# kill -HUP <nco_p_mttrapd pid>
Otherwise, you need to start the MTTrapd Probe by using the
following command as root:
# ${OMNIHOME}/probes/nco_p_mttrapd -server <ObjectServer host>
where <ObjectServer host> is the host name of the ObjectServer
that will receive Netcool alerts from this probe.
The MTTrapd Probe is ready to receive and interpret SNMP traps
sent from Halcyon Neuron Management Suite. The detailed event
information can be viewed on the Event List console.
6. Launch the Netcool Event List console with the following command:
# ${OMNIHOME}/bin/nco_event -server <ObjectServer>
Press the "View" button on the desired Event List filter to review
the detailed contents of the events.
6.3 SNMP MIB Files
----------------------------------------------------------------------
Halcyon provides MIB files describing the format of the SNMP traps
being sent to IBM Tivoli Netcool. IBM Tivoli Netcool can use these
files to map the OIDs which are inside the SNMP trap to object names
from the MIB file.
The Halcyon MIB files can be found at the following locations:
[LOCALDIR]/conf/module/GenericAdapter_v1.mib
[LOCALDIR]/conf/module/GenericAdapter_v2.mib
A description of these MIBs can be found at:
[LOCALDIR]/conf/module/GenericAdapter.txt
7. Halcyon Neuron Integration for BMC Event Manager Configuration
Instructions
======================================================================
This section describes how to configure the Neuron Integration for BMC
Event Manager. It consists of the following sub-sections:
7.1 Integration Configuration: Action Configuration
7.2 SNMP MIB Files
7.1 Integration Configuration: Action Configuration
----------------------------------------------------------------------
In order to use the Neuron Integration for BMC Event Manager, a BMC
action must be defined in a rule via the Neuron Event Manager
(NeuronEventManager_[VERSION]_UsersGuide.pdf), which will forward
Neuron Events to BMC.
The Halcyon Neuron Event Manager should be used to setup a BMC Event
Manager action within a rule. When the given rule matches an incoming
event, the BMC action will be triggered and the event will be
forwarded to the BMC Event Manager specified with the action.
It is possible to specify default values for the type of SNMP trap to
send (either V1 or V2), SNMP community, SNMP targets, and SNMP agent
host via the Neuron Management Suite's Server Configuration page (see
"Accessing Server Configuration Page" above), by editing properties for
BEMAdapter. Also see "Halcyon Generic Adapter Configuration
Instructions" above for more details on these values.
7.2 SNMP MIB Files
----------------------------------------------------------------------
Halcyon provides a MIB file describing the format of the SNMP traps
being sent to BMC Event Manager. BMC PATROL Enterprise Manager Connect
SNMP can use this file to map the OIDs which are inside the SNMP trap
to object names from the MIB file.
The Halcyon MIB file can be found at the following location:
[BASEDIR]/conf/module/BEMAdapter.mib
A description of this MIB can be found at:
[BASEDIR]/conf/module/BEMAdapter.txt
8. Halcyon Neuron Integration for HP OpenView Configuration
Instructions
======================================================================
This section describes how to configure the Neuron Integration for HP
OpenView. It consists of the following sub-sections:
8.1 Integration Configuration: Action Configuration
8.2 SNMP MIB Files
8.1 Integration Configuration: Action Configuration
----------------------------------------------------------------------
In order to use the Neuron Integration for HP OpenView, an HP OpenView
action must be defined in a rule via the Neuron Event Manager
(NeuronEventManager_[VERSION]_UsersGuide.pdf), which will forward
Neuron Events to OpenView.
The Halcyon Neuron Event Manager should be used to setup an HP OpenView
action within a rule. When the given rule matches an incoming event,
the OpenView action will be triggered and the event will be forwarded
to the HP OpenView server specified with the action.
It is possible to specify default values for the type of SNMP trap to
send (either V1 or V2), SNMP community, SNMP targets, and SNMP agent
host via the Neuron Management Suite's Server Configuration page (see
"Accessing Server Configuration Page" above), by editing properties for
OpenViewAdapter. Also see "Halcyon Generic Adapter Configuration
Instructions" above for more details on these values.
8.2 SNMP MIB Files
----------------------------------------------------------------------
Halcyon provides MIB files describing the format of the SNMP traps
being sent to HP OpenView. HP OpenView can use these files to map
the OIDs which are inside the SNMP trap to object names from the
MIB file.
The Halcyon MIB files can be found at the following locations:
[LOCALDIR]/conf/module/GenericAdapter_v1.mib
[LOCALDIR]/conf/module/GenericAdapter_v2.mib
A description of these MIBs can be found at:
[LOCALDIR]/conf/module/GenericAdapter.txt
9. Halcyon Neuron Integration for Sun Management Center Configuration
Instructions
======================================================================
This section describes how to configure the Neuron Integration for Sun
Management Center. It consists of the following sub-sections:
9.1 Configuration of Sun Management Center Server Adapter
9.1.1 Install PrimeAlert for Sun Management Center
9.1.2 Include Sun MC Libraries for Integration
9.1.3 Update Configuration
9.2 Configuration of Sun Management Center Agent Adapter
9.3 Remote Acknowledgement of Sun MC alarms
9.1 Configuration of Sun Management Center Server Adapter
----------------------------------------------------------------------
In order to use the Sun Management Center Server Adapter some
preliminary configuration on both the Sun MC server host and the
Neuron Management Suite server host is required.
9.1.1 Install PrimeAlert for Sun Management Center
--------------------------------------------------------------------
Included in this distribution is the following file:
HALSunMC_[version].tar.gz
Please extract the distribution and install it on the Sun MC server
as outlined in README.install found in that distribution's root
directory.
9.1.2 Include Sun MC Libraries for Integration
--------------------------------------------------------------------
The Halcyon Neuron Sun Management Center Server Adapter requires the
inclusion of Sun MC libraries in the Halcyon Neuron Management Suite
library path.
To include the libraries, copy the following JAR files from the Sun
MC server host ([SUNMC_INSTALL_DIR]/classes) to the library
directory ([LOCALDIR]/lib):
esclt.jar, escom.jar, esjrm.jar, esmsg.jar
Execute the following commands to copy the required files:
On the Sun MC server host:
% su -
# cd [SUNMC_INSTALL_DIR]/classes
# cp esclt.jar escom.jar esjrm.jar esmsg.jar [COMMON_LOCATION]
On the Neuron Management Suite host:
% su -
# cd [COMMON_LOCATION]
# cp esclt.jar escom.jar esjrm.jar esmsg.jar [LOCALDIR]/lib
NOTE: By default SUNMC_INSTALL_DIR is: /opt/SUNWsymon
NOTE: The Sun MC files will be copied over during installation
if Sun MC and Halcyon Neuron Management Suite are
installed on the same host.
9.1.3 Update Configuration
--------------------------------------------------------------------
After installing Neuron Management Suite, please update the
following configuration properties of the Sun MC Server Adapter
via the Neuron Management Suite's Server Configuration page (see
"Accessing Server Configuration Page" above), by selecting
"SunMCServerAdapter" and clicking on "Edit". In the Connections
tab, edit the following fields:
- Name: Unique name for the connection to a Sun Management
Center Server.
- User: The user name for a Sun Management Center Server
esops user.
- Password: The password for the user, which will be encoded
automatically
- URL Host: The Sun Management Center Server host name.
- URL Port: The Sun Management Center Server port number,
default is 2099)
You can also configure other properties on the General tab. After
updating the configuration for the Sun MC Server Adapter, please
enable it.
9.2 Configuration of Sun Management Center Agent Adapter
----------------------------------------------------------------------
In order for this integration approach to work, the Sun Management
Center agents being integrated must be configured to send traps to
the Halcyon Neuron Management Suite and then restarted for the
changes to take effect.
On each Sun Management Center agent host, run the following:
% su -
# [SUNMC_INSTALL_DIR]/sbin/es-trapdest -a host:port -f sunmcTraps
# [SUNMC_INSTALL_DIR]/sbin/es-stop -a
# [SUNMC_INSTALL_DIR]/sbin/es-start -a
SUNMC_INSTALL_DIR: directory where Sun MC was installed
(default is /opt/SUNWsymon)
host: where the Halcyon Neuron Management Suite is installed
port: port the Halcyon Neuron Management Suite is configured
to receive SNMP traps on (default is 2162)
After installing Neuron Management Suite, please update the following
configuration properties of the Sun MC Agent Adapter via the Neuron
Management Suite's Server Configuration page (see "Accessing Server
Configuration Page" above), by selecting "SunMCAgentAdapter" and
clicking on "Edit":
- communityString (the SNMP community string used by the Sun
Management Center agent)
After updating the configuration for "SunMCAgentAdapter", please
enable it.
9.3 Remote Acknowledgement of Sun MC alarms
----------------------------------------------------------------------
Neuron Integration for Sun Management Center provides a mechanism for
acknowledging Sun MC alarms through Halcyon Neuron Management Suite.
To enable remote acknowledgement of Sun MC alarms, set the value of
"remote_acknowledgements_enabled" configuration property to 'true'
via the Neuron Management Suite's Server Configuration page (see
"Accessing Server Configuration Page" above), by selecting
"SunMCServerAdapter" and clicking on "Edit".
Then disable and re-enable the adapter. This will reload and apply
the configuration.
To remotely acknowledge Sun MC alarms from your enterprise management
framework, such as Tivoli, HP OpenView, etc, configure and enable one
of the following integration solutions to forward Neuron Events to
the management framework:
- Neuron Integration for IBM Tivoli
- Neuron Integration for IBM Tivoli Netcool
- Neuron Integration for HP OpenView
Follow the instructions in README.reverseAck to set up your enterprise
management framework in order to reverse acknowledge Neuron Events.
Once this is set up, if you acknowledge a Neuron Event for a Sun MC
alarm in your management framework console, this Neuron Integration
for Sun Management Center will acknowledge the alarm in Sun MC.
To disable remote acknowledgement of Sun MC alarms, set the value of
"remote_acknowledgements_enabled" configuration property to 'false'
via the Neuron Management Suite's Server Configuration page (see
"Accessing Server Configuration Page" above). Disable and re-enable
the adapter in order to apply the changes.
10. Halcyon Neuron Integration for Oracle Grid Engine Configuration
Instructions
======================================================================
This section describes how to configure the Neuron Integration for
Oracle Grid Engine. It consists of the following sub-sections:
10.1 Include Oracle Grid Engine Libraries for Integration
10.2 Configuration of Oracle Grid Engine Master Hosts
10.1 Include Oracle Grid Engine Libraries for Integration
--------------------------------------------------------------------
In order to use the Halcyon Neuron Integration for Oracle Grid
Engine with JMX enabled Grid Engine Master Hosts the inclusion
of Grid Engine libraries in the Halcyon Neuron Management Suite
library path is necessary.
Note: Halcyon Neuron Integration for Oracle Grid Engine provides two
integration strategies: JMX and SSH. If SSH is used no Oracle
Grid Engine libraries are required and the following steps
can be skipped.
To include the libraries, copy the following JAR files from the Grid
Engine Master Host ([GRID_ENGINE_DIR]/lib) to the library directory
([LOCALDIR]/lib):
jgdi.jar
Execute the following commands to copy the required files:
On the Grid Engine Master Host:
% su -
# cd [GRID_ENGINE_DIR]/lib
# cp jgdi.jar [COMMON_LOCATION]
On the Neuron Management Suite host:
% su -
# cd [COMMON_LOCATION]
# cp jgdi.jar [LOCALDIR]/lib
NOTE: By default GRID_ENGINE_DIR is: /opt/sge[VERSION]
10.2 Configuration of Oracle Grid Engine Master Hosts
--------------------------------------------------------------------
After installing Neuron Management Suite, please update the
following configuration properties of the Oracle Grid Engine
Module via the Neuron Management Suite's Server Configuration page
(see "Accessing Server Configuration Page" above), by selecting
"GridEngineModule" and clicking on "Edit":
- Click on Add Master Host to add a new Master Host configuration
- Master Host Name (the Oracle Grid Engine Master Host name)
- SGE_ROOT (the Oracle Grid Engine installation directory)
- SGE_CELL (the Oracle Grid Engine cluster name, in a single
cluster installation the default is default)
- Port (the Oracle Grid Engine port, for JMX the default is
6446, for SSH the default is 22)
- Strategy (the method by which to connect to the Oracle Grid
Engine, default is JMX)
- Username (the user name for a Oracle Grid Engine user)
- Password (the password for the Oracle Grid Engine user)
After updating the configuration for the Oracle Grid Engine Module,
please enable it.
11. Halcyon Neuron Module for Generic Hardware Configuration
Instructions
======================================================================
This section describes how to configure the Neuron Module for Generic
Hardware. It consists of the following sub-sections:
11.1 Configuration: IPMI Connection Default Credentials
11.2 Configuration: IPMI Enabled Hosts
11.3 Configuration: Syslog
11.1 Configuration: IPMI Connection Default Credentials
----------------------------------------------------------------------
In order for Neuron Module for Generic Hardware to work, an IPMI user
name and password are required. You could specify an IPMI user and
password for each IPMI enabled server too (see section 11.2). If
there is no specific credential provided for an IPMI enabled server,
the default user and password will be used.
After installing Neuron Management Suite, please update the following
configuration properties of "HardwareModule" module via the Neuron
Management Suite's Server Configuration page (see "Accessing Server
Configuration Page" above), by selecting "HardwareModule" and clicking
on "Edit":
- default.user
- default.password
After updating the configuration for "HardwareModule", please enable
it.
11.2 Configuration: IPMI Enabled Hosts
----------------------------------------------------------------------
Neuron Module for Generic Hardware can monitor multiple IPMI enabled
hosts. There are two ways to monitor IPMI enabled hosts:
1. System Event Log Fault Monitoring
The System Event Log of the Baseboard Management Controller
on the IPMI enabled host is retrieved periodically. Any new
events are converted into Neuron Management Server events.
The configuration property "ipmi.hosts.monitor.sel" defines
which IPMI enabled hosts are to be monitored.
The value for "ipmi.hosts.monitor.sel" property has the
following format:
<IPMI HOST INFO 1>, <IPMI HOST INFO 2>, <IPMI HOST INFO 3>, ...
And each of the <IPMI HOST INFO> has one the following format:
hostA
hostB/userB
hostC/userC/encryptedPasswordC
hostD:portD
hostE:portE/userE
hostE:portE/userE/encryptedPasswordE
For each IPMI enabled host, either the host name or IP must be
provided. The IPMI port number is optional. The connection
credential for each IPMI enabled host is also optional. But if
an IPMI connection credential is provided, you could either
provide only user or provide user plus encrypted password.
Giving only encrypted password without a user will not work.
If no connection credential is given for a host, the default
user and password will be used (see section 11.1). If only the
IPMI user is provided, the default password will be used for
this user. To encrypt a password, run the password encoding
tool that comes with Halcyon Neuron Management Suite:
# [BASEDIR]/bin/PasswordEncoder.sh -u
where BASEDIR is /opt/HMF by default.
The frequency at which System Event Log Fault Monitoring is
performed is defined by the "sel.event.refresh.interval"
configuration property (in minutes).
2. IPMI Platform Event Traps Monitoring
Configure your IPMI enabled hosts to send IPMI Platform Event
Traps to the Neuron Management Server. The default port for
receiving events is 2162.
Any IPMI Platform Event Trap that is received is converted into
a Neuron Management Server event.
In order to disable monitoring for certain IPMI enabled hosts the
configuration property "ipmi.hosts.monitor.disable" can be used. This
property expects a comma-separated list of IPMI enabled hosts for
which no System Event Log Fault Monitoring or IPMI Platform Event
Traps Monitoring should be performed.
It is also possible to completely disable fault monitoring. In order
to do so set the configuration property "monitoring.fault" to "false".
In addition to fault monitoring Neuron Module for Generic Hardware
also monitors the status of the System Event Log. When the size of the
event log passes certain thresholds an event is generated. The
following configuration properties are used to specify these thresholds:
- sel.usage.threshold.critical
- sel.usage.threshold.warning
- sel.usage.threshold.info
The frequency at which this System Event Log Threshold Monitoring is
performed is defined by the "sel.status.refresh.interval" configuration
property (in minutes).
Note: Update configuration properties of the "HardwareModule" via the
Neuron Management Portal -> Configuration user interface, by selecting
"HardwareModule" and clicking on "Edit".
11.3 Configuration: Syslog
----------------------------------------------------------------------
The Neuron Module for Generic Hardware can monitor a system log file
on the host where Halcyon Neuron Management Suite is installed.
After installing Neuron Management Suite, please update the following
configuration properties of "HardwareModule" via the Neuron Management
Suite's Server Configuration page (see "Accessing Server Configuration
Page" above), by selecting "HardwareModule" and clicking on "Edit":
- logEnabled
- logFiles
- logCheckIntervals
When system log monitoring is enabled each line in this file is read
by the Neuron Module for Generic Hardware. It then uses the Generic
Hardware Module rule file to determine whether the line represents
an event of interest that should be handled by Halcyon Neuron
Management Suite.
The rule file is called HardwareModule.drl and can be found in
[LOCALDIR]/conf/module. It contains a default rule that acts on
each line. In order to filter events, add one or more of the
following conditions:
- that contains [CONSTRAINT]
- that not contains [CONSTRAINT]
- that is [CONSTRAINT]
- that is not [CONSTRAINT]
These conditions check whether the line contains, does not contain,
is equal to, or is not equal to the provided constraint.
The generic form of possible actions is:
Send raw event
This will generate an event. The event being sent can be modified
using one or more of the following statements:
- with [SEVERITY] severity
- where the state is [STATE]
- take the asset from position [POSITION]
The following values may be used:
- severity: INFO, WARNING, MINOR, MAJOR, CRITICAL
- state: OPEN, CLOSE, MANUAL_CLOSE, ACKNOWLEDGE, LOG,
DISABLE, OFF
The last statement - take the asset from position - can be used
to set the asset where the event originated from. The value for
POSITION is the number of the field in the line that contains
the asset. For the standard UNIX system log this is usually at
position 4. Fields are separated by space.
Examples of rules in HardwareModule.drl file:
rule "Syslog Example 1"
when
There is a logfile line
- that contains kern.error
then
Send raw event
- with Error severity
- where the state is Open
- take the asset from position 4
end
rule "Syslog Example 2"
when
There is a logfile line
- that contains kern.info or kern.warning
then
Send raw events
- with Info severity
- where the state is Log
- take the asset from position 4
end
In order for Halcyon Neuron Management Suite to use an updated rule
file, first disable and then re-enable the "HardwareModule" in the
Neuron Management Suite's Server Configuration page (see "Accessing
Server Configuration Page" above). This will reload the Neuron Module
for Generic Hardware and activate its rules from the updated rule file.
12. Halcyon Neuron Module for Linux Base Configuration Instructions
======================================================================
This section describes how to configure the Neuron Module for Linux
Base. It consists of the following sub-sections:
12.1 Configuration: Syslog
12.1 Configuration: Syslog
----------------------------------------------------------------------
The Neuron Module for Linux monitors the primary system log file
(/var/log/messages) on the Linux host where Halcyon Neuron Management
Suite is installed. Do not enable the Neuron Module for Linux if
Halcyon Neuron Management Suite is installed on a non-Linux host.
After installing Neuron Management Suite, please update the following
configuration properties of "LinuxBaseModule" via the Neuron Management
Suite's Server Configuration page (see "Accessing Server Configuration
Page" above), by selecting "LinuxBaseModule" and clicking on "Edit":
- logEnabled
- logFiles
- logCheckIntervals
IMPORTANT: By default, some Linux installations only allow the
syslog to be read be root. You will need to ensure that
the file is readable by user halcyon, otherwise
monitoring of it will not work.
After making changes to the configuration properties, you
will need to disable and then re-enable the "LinuxBaseModule"
in the Neuron Management Suite's Server Configuration page
(see "Accessing Server Configuration Page" above). This will
reload the Neuron Module for Linux and activate updated
configuration setting.
Each line in the specified system log file is read by the Neuron Module
for Linux. A Linux Module rule file determines whether the line represents
an event of interest that should be handled by Neuron Management Suite.
The rule file is called LinuxBaseModule.drl and can be found in
[LOCALDIR]/conf/module. Rules representing known message patterns
are predefined. Additional rules may be specified to act on
one or more of the following conditions:
- that contains [CONSTRAINT]
- that not contains [CONSTRAINT]
- that is [CONSTRAINT]
- that is not [CONSTRAINT]
These conditions check whether the line contains, does not contain,
is equal to, or is not equal to the provided constraint.
The Linux form of possible actions is:
Send raw event
This will generate an event. The event being sent can be modified
using one or more of the following statements:
- with [SEVERITY] severity
- where the state is [STATE]
- take the asset from position [POSITION]
The following values may be used:
- severity: INFO, WARNING, MINOR, MAJOR, CRITICAL
- state: OPEN, CLOSE, MANUAL_CLOSE, ACKNOWLEDGE, LOG,
DISABLE, OFF
The last statement - take the asset from position - can be used
to set the asset where the event originated from. The value for
POSITION is the number of the field in the line that contains
the asset. For the standard UNIX system log this is usually at
position 4. Fields are separated by space.
Examples of rules in LinuxBaseModule.drl file:
rule "Generic Warning"
activation-group "syslog"
when
There is a logfile line
- that contains "[Ww][Aa][Rr][Nn]"
then
Send raw event
- with Warning severity
- where the state is Log
- use Linux asset
end
rule "Generic Error"
activation-group "syslog"
when
There is a logfile line
- that contains "[Ee][Rr][Rr][Oo][Rr]"
then
Send raw event
- with Critical severity
- where the state is Log
- use Linux asset
end
In order for Halcyon Neuron Management Suite to use an updated rule
file, first disable and then re-enable the "LinuxBaseModule" in the
Neuron Management Suite's Server Configuration page (see "Accessing
Server Configuration Page" above). This will reload the Neuron Module
for Linux and activate its rules from the updated rule file.
13. Halcyon Neuron Module for Solaris Base Configuration Instructions
======================================================================
This section describes how to configure the Neuron Module for Solaris
Base. It consists of the following sub-sections:
13.1 Configuration: Syslog
13.1 Configuration: Syslog
----------------------------------------------------------------------
The Neuron Module for Solaris monitors the primary system log file on
the Solaris host where Halcyon Neuron Management Suite is installed.
Do not enable Neuron Module for Solaris if Halcyon Neuron Management
Suite is installed on a non-Solaris host.
After installing Neuron Management Suite, please update the following
configuration properties of "SolarisBaseModule" via in the Neuron
Management Suite's Server Configuration page (see "Accessing Server
Configuration Page" above), by selecting "SolarisBaseModule" and clicking
on "Edit":
- logEnabled
- logFiles
- logCheckIntervals
IMPORTANT: After making changes to the configuration properties, you
will need to disable and then re-enable the "SolarisBaseModule"
in the Neuron Management Suite's Server Configuration page
(see "Accessing Server Configuration Page" above). This will
reload the Neuron Module for Solaris and activate updated
configuration setting.
Each line in the specified sytem log file is read by the Neuron Module
for Solaris. A Solaris Module rule file determines whether the line
represents an event of interest that should be handled by Halcyon
Neuron Management Suite.
The rule file is called SolarisBaseModule.drl and can be found in
[LOCALDIR]/conf/module. Rules representing known hardware message
patterns are predefined. Additional rules may be specified to act on
one or more of the following conditions:
- that contains [CONSTRAINT]
- that not contains [CONSTRAINT]
- that is [CONSTRAINT]
- that is not [CONSTRAINT]
These conditions check whether the line contains, does not contain,
is equal to, or is not equal to the provided constraint.
The Solaris form of possible actions is:
Send raw event
This will generate an event. The event being sent can be modified
using one or more of the following statements:
- with [SEVERITY] severity
- where the state is [STATE]
- take the asset from position [POSITION]
The following values may be used:
- severity: INFO, WARNING, MINOR, MAJOR, CRITICAL
- state: OPEN, CLOSE, MANUAL_CLOSE, ACKNOWLEDGE, LOG,
DISABLE, OFF
The last statement - take the asset from position - can be used
to set the asset where the event originated from. The value for
POSITION is the number of the field in the line that contains
the asset. For the standard UNIX system log this is usually at
position 4. Fields are separated by space.
Examples of rules in SolarisBaseModule.drl file:
rule "CPU Panic"
when
There is a logfile line
- that contains "panic *\[cpu([0-9]+)\]/thread=0x[0-9a-f]+: ([^:]+)"
then
Send raw event
- with Error severity
- where the state is Log
end
rule "Corrupted Frame Buffer"
when
There is a logfile line
- that contains "InitOutput: Error loading module for /dev/fb"
then
Send raw event
- with Warning severity
- where the state is Log
end
In order for Halcyon Neuron Management Suite to use an updated rule
file, first disable and then re-enable the "SolarisBaseModule" in the
Neuron Management Suite's Server Configuration page (see "Accessing
Server Configuration Page" above). This will reload the Neuron Module
for Solaris and activate its rules from the updated rule file.
14. Halcyon Neuron Module for Solaris Virtualization Configuration
Instructions
======================================================================
The Neuron Module for Solaris Virtualization monitors Solaris
zones and Oracle VMs for SPARC (LDOMs). It does not yet provide
any configurable options.
15. Halcyon Neuron Module for Windows Base Configuration Instructions
======================================================================
The Neuron Module for Windows Base monitors Windows hosts. It does
not yet provide any configurable options.
16. Halcyon Neuron Module for Cisco Base Configuration Instructions
======================================================================
The Neuron Module for Cisco Base monitors Cisco network devices. It
does not yet provide any configurable options.
17. Halcyon Neuron Agent Module Configuration Instructions
======================================================================
The Neuron Agent Module monitors systems with a Neuron Agent installed.
It does not yet provide any configurable options.
18. Halcyon Event Manager Configuration Instructions
======================================================================
NOTE: [LOCALDIR] is typically /var/opt/HMF
18.1 Configuration of Event Manager: User Interface
----------------------------------------------------------------------
The Neuron Management Portal contains Neuron Event Manager which
allows the user to specify inbound and response rules.
The Event Manager is accessed by clicking "Manage Events" from the
Event's tab Actions panel (if there's a "View Events" button instead,
then you're already in the Event Manager).
To return to the Event Viewer, click "View Events" from the Event's
tab Actions panel (if there's a "Manage Events" button instead, then
you're already in the Event Viewer).
(See NeuronEventManager_[VERSION]_UsersGuide.pdf for more details)
Inbound rules define whether incoming information is processed and how
they are converted to Neuron Core events. There are two types of
inbound rules which define a stream:
- SNMP traps
- Ops Center notifications
SNMP traps are generated by devices or applications on the network.
Neuron Core listens to these traps on port 2162 by default (see section
9.2 for details). Inbound rules define whether these SNMP traps should
be processed and how they are transformed into Neuron Core events.
Select the rule type "Inbound" and the stream "SNMP" in the Event
Manager in order to create rules for the SNMP stream.
Ops Center notifications are generated by Oracle Enterprise Manager Ops
Center. If the Neuron Integration for Oracle Enterprise Manager Ops
Center has been configured and enabled Neuron Core will periodically
retrieve notifications from Ops Center. Inbound rules define whether
these notifications should be processed and converted into Neuron Core
events. Select the rule type "Inbound" and the stream "Ops Center" in
the Event Manager in order to create rules for the Ops Center stream.
The Event Manager also allows the specification of so-called "response"
rules. This type of rule defines which Neuron Core events should be
processed and what actions to perform. Select the rule type "Response"
in the Event Manager in order to create rules that act upon Neuron Core
events. The following actions are available for response rules:
- Send an email: send an email to one or more recipients
- Run a script: execute a script on the Neuron Core server host
- Send an SNMP trap: send an SNMP trap to one or more destinations
- Send to BMC Event Manager: send an SNMP trap to BMC Event Manager
- Send to IBM Tivoli Netcool: send an SNMP trap to IBM Tivoli Netcool
- Send to HP OpenView: send an SNMP trap to HP OpenView
- Send to IBM Tivoli: send an SNMP trap to IBM Tivoli
- Send to OEM Ops Center: inject the event into Oracle Enterprise
Manager Ops Center
Once rules have been created within the Event Manager they must be
enabled in order to become active.
18.2 Configuration of Event Manager: Rule Matching (Inbound)
----------------------------------------------------------------------
SNMP traps and Ops Center notifications are processed according to the
defined inbound rules (see section 18.1). If an SNMP trap matches one
of the inbound rules the SNMP trap is converted to an event according
to the specified transformation rules. Ops Center notifications are
also converted to events and processed by configured response rules
(see section 18.3).
18.3 Configuration of Event Manager: Rule Matching (Response)
----------------------------------------------------------------------
When Neuron Management Suite receives events they are first stored as
raw events. These are periodically converted to so-called Fault
Events and stored permanently in the Neuron Management Suite Message
Database (MSGDB). Events from this table are displayed by Neuron
Event Viewer.
The Neuron Management Suite Message Database Service periodically
reads new Fault Events from the MSGDB and evaluates them against the
rules defined in its rule file. The following Fault Event fields can
be used in response rules:
- host
- port
- module
- url
- severity (INFO, WARNING, MINOR, MAJOR, CRITICAL, UNKNOWN)
- type (OPEN, CLOSE, ACKNOWLEDGE, OFF, DISABLE, LOG, MANUAL_CLOSE)
- proxy type, e.g. Ops Center, Sun MC
- proxy host
- message
When defining rules for host or proxy host the host names must be in
lower-case characters. This allows for case-insensitive comparison
by the Event Manager rules.