Hi, We have over many systemedge agents on unix and use a shell script to configure them through our software distribution tool. My suggestion for you would be to make a script to edit the sysedge.cf file on each agent.
If you make settings remotely via snmp or whatever it updates another file called sysedge.mon instead and the two files mash together to make the running config which can be confusing and create unpredictable results as the .cf takes priority over the .mon entries. For example if you make a setting in .cf and edit in the system resources panel in one click your changes only persist till next agent restart. Here are some examples for unix. Note sysEdge can send two types of traps based on the line in .cf : version 4 format (no severity) and version 12.x / 5.x traps that do have a severity. These examples are 12.x version # open .new file and append entries below # then restart agent # /opt/CA/SystemEDGE/bin/sysedgectl stop # /opt/CA/SystemEDGE/bin/sysedgectl start # cpu 10000+ <2% idle for > 240 intervals of 60 sec # 0f0 = 240 # 5xx = send clear trap + x intervals # xxxxxx8 = no logging of trap in local log monitor oid cpuTotalIdlePercent.0 13 0x0f000508 60 absolute <= 2 'CPU Idle Time (percentage)' '' 'CPU' 'Total' 'PercentIdle' critical # 15 min load average > 30 (measure is * 10) 10100+ monitor oid 1.3.6.1.4.1.546.1.1.7.8.26.0 10100 0x00 60 absolute > 300 'Monitor 15 minute load average' '' 'kernelperf' 'null' 'LoadAverage15Min' critical # swap > 95% 10200+ monitor oid swapCapacity.0 10200 0x00 60 absolute > 95 'Swap utilization' '' 'SysHealth' 'TotalSwap' 'UtilPercent' critical # file systems 10300+ monitor filesystem / devCapacity 10301 0x0 120 absolute > 98 'Monitor / Filesystem' '' 'devTableEntry' '/' 'devCapacity' critical monitor filesystem / devCapacity 10302 0x0 120 absolute > 90 'Monitor / Filesystem' '' 'devTableEntry' '/' 'devCapacity' warning #processes 10500+ 0x8 = no log of trap # note = 4 is ignored because of ProcAlive watch process procAlive 'nfsd' 10500 0x8 60 absolute = 4 'Process Monitor: nfsd' '' 'processEntry' 'nfsd' 'procAlive' critical watch process procAlive 'syslogd' 10501 0x8 60 absolute = 4 'Process Monitor: syslogd' '' 'processEntry' 'syslogd' 'procAlive' critical # log file standard watchers 10600+ # watch logfile 20 0x00 /var/log/syslog ' /^WARNING:(.*\n)*Invalid login attempt/m' 'NOTICE – Invalid login attempt' '' 1 warning watch logfile 10600 0x8 /var/log/messages '#Device not ready' 'Logwatcher: Device not ready' '' 1 critical watch logfile 10601 0x8 /var/log/messages 'Bad' 'Logwatcher: Bad' '' 1 critical [cid:[email protected]] Rick Jury Senior Support Specialist Tools Phone: +64 4 8029643 Mobile: +64 27 278 5992 Level 12 Telecom Central - Boulcott 42-52 Willis Street, Wellington www.telecom.co.nz<http://www.telecom.co.nz> ________________________________ This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002. From: Nikhil Mehra [mailto:[email protected]] Sent: Friday, 9 August 2013 9:44 a.m. To: spectrum Cc: spectrum Subject: Re: [spectrum] Adding System Resources Yes Sent from my iPhone On Aug 8, 2013, at 5:23 AM, Ami R Patel <[email protected]<mailto:[email protected]>> wrote: Hi Community! This is my first time implementing Spectrum. I have SystemEdge agent installed on some systems as test.. they're discovered and modeled properly. When I attempt to add System Resources (processes, filesystems, logs, etc) to monitoring, I get message stating either system is not responding or SNMP community is read-only. Can someone please advise if SNMP read-write access is required to set this up correctly or is there a configuration setting that I may be missing? Thanks, Ami This is a PRIVATE message. If you are not the intended recipient, please delete without copying and kindly advise us by e-mail of the mistake in delivery. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose. * --To unsubscribe from spectrum, send email to [email protected]<mailto:[email protected]> with the body: unsubscribe spectrum [email protected]<mailto:[email protected]> * --To unsubscribe from spectrum, send email to [email protected]<mailto:[email protected]> with the body: unsubscribe spectrum [email protected] --- To unsubscribe from spectrum, send email to [email protected] with the body: unsubscribe spectrum [email protected]
<<inline: image001.jpg>>
