I can't speak to #2, but as for syslog, I would replace syslog with either
rsyslog or syslog-ng. I believe Red Hat 6 comes with the former, SLES has
been defaulting to the latter since v10. Both will allow you to split
incoming logs into however many files you want. In the past, I used
syslog-ng to have individual log files for each node in a cluster as well
as a single log file for all nodes that was both kept on the xCAT MN as
well as forwarded on to a splunk log server. There are plenty of write-ups
on how to configure both packages.
Hope that helps.
From: Gilad Berman <[email protected]>
To: xCAT Users Mailing list <[email protected]>,
Date: 03/07/2012 10:46 AM
Subject: [xcat-user] snmpmon question
Hello,
I have few questions regarding monitoring with xCAT, especially snmp.
1. Is there a way to prevent xCAT to log all events coming from the nodes
/ devises to /var/log/messages? i tried the following line in monsetting
table - "snmpmon","log","None",, did not work.
2. Lets say i would like to run command when event received, use the
runcmd and cmds values. what is the best way to handle specific event? is
there a way to pass the event to the script? not sure its clear enough,
so, here's what we want to do - when an even received, we would like to
run a script that will take the device name (that generate the event), the
severity, take the message text (we do not want to take all the snmp trap,
for example) and send it to another monitoring system in a certain format.
3. This is a general question that i hope someone one the list can advise
- Assuming the xCAT server (or any other server for that matter) will act
as the syslog servers for the networking devices (MLX, BNT etc.), if there
a way to write those messages to different file and not have one long
unified /var/log/messages? preferably even to spit each IP / device to
its own file. Looking at the syslog.conf, i see no way of doing this and
no criteria that i can use. any ideas are more than welcome!
any other ideas / best practices / solution you've implemented are more
than welcome!
Regards,
Gilad Berman
HPC Architect
IBM System & Technology Group. Israel
E-mail: [email protected]
Tel: 972-3-9188262
Mobile: 972-52-2554262
The information contained in this email is being provided by IBM as a
matter of courtesy and provided "AS-IS" without any direct and implied
warranty; IBM assumes no liability. It is your responsibility to ensure
that any resulting customer proposal has been correctly designed to meet
your clients' requirements and to have an active review process which
ensures an appropriate level of solution assurance is performed for all
proposals. IBM does not take responsibility for the solution or solution
assurance.
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user
------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user