Hello,

I've comments out all the syslog part in /opt/xcat/sbin/xcat_traphandler 
to avoid xCAT logs all snmp alerts in my /var/log/messages file, however, 
still no luck, SNAM traps still logged in the syslog file. 
Can you please advise? 

thx in advance! 

#log to syslog if needed. default is log all
$ENV{'XCATCFG'}="";
#if ($LOG || (keys(%hashL)==0)) {
#  my $head="SNMP $severity received from $host($ip).";
#  my $body;
#  if ($briefmsg) { $body=$briefmsg;}
#  else { $body=$message; }

#  openlog("xCATMon Event","","local4");
#  if ($severity_type eq "Informational") {
#    syslog("local4|info", "$head\n$body\n");
#  } else {
#    syslog("local4|err", "$head\n$body\n");
#  }
#  closelog();
#}
 

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.



From:   Ling Gao <[email protected]>
To:     xCAT Users Mailing list <[email protected]>
Cc:     xCAT Users Mailing list <[email protected]>
Date:   09/03/2012 22:54
Subject:        Re: [xcat-user] snmpmon question



Hi Gilad, 
    1. "snmpmon","log","None,",,  in monsetting table should work.  I do 
not have time to debug now, you can modify the file 
/opt/xcat/sbin/xcat_traphandler   to fit your need. Like comment out the 
syslog part. 

   2. you can specify a command to run for certain traps. For example 
"snmpmon","runcmd30","snmpTrapOID.0=~vol_ufm",, 
"snmpmon","cmds30","/tmp/echotrap",, 
This way /tmp/echotrap will be invoked when snmpTrapOID.0 contains 
vol_ufm.  The whole trap + the sender info is passed to this script. Then 
in this script, you can parse the trap to get the info you need and call 
other commands with specific info. So it's better to create a script just 
to see what is passed to it by xCAT first. 

Ling 

Ling Gao
Poughkeepsie Unix Development Lab
IBM Systems and Technology Group
Internal: T/L 293-5692 
External: [email protected], 845-433-5692

"I never worry about the future. It comes soon enough." --- Albert 
Einstein 



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

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to