|[Date Prev] [Date Next]||[Thread Prev] [Thread Next]||[Date Index] [Thread Index]|
RE: [snips-users] Thresholds in snmpgeneric
Hi Michael, I have also had this problem. I could not find a solution so I am still using NOCOLv4.2.2. If you do find a solution please let me know and I could try out SNIPS. Thanks, Steve Daltrey Network Engineer Operations Telecity London www.telecity.net -----Original Message----- From: Michael Dipper [mailto:md at lf net] Sent: Tuesday, January 08, 2002 4:32 PM To: snips-users at navya com Subject: [snips-users] Thresholds in snmpgeneric Hi, I have a problem with snmpgeneric in snips-1.1: While this config works fine: TEMP 192.168.1.2 .18.104.22.168.4.1.2606.1.1.1.0 TEMP public 26 28 30 This one doesn´t work: PRI 192.168.1.3 .22.214.171.124.126.96.36.199.1.8.2 STATUS public 2 2 2 It seems that snips can´t handle the case when the thresholds for warning, error and critical are equal although otherwise indicated in the sample-config. The output goes to "critical" for any snmpget-output, even if it is just "1". What I want to reach is to have an OK for output "1" and a CRITICAL for anything higher. -- Gruss / Best regards | LF.net GmbH | fon +49 711 90074-27 Michael Dipper | Ruppmannstr. 27 | fax +49 711 90074-33 md at LF net | D-70565 Stuttgart | http://www.lf.net DISCLAIMER This e-mail is intended only for the use of the addressees named above and may be confidential. If you are not an addressee you must not read it and must not use any information contained in nor copy it nor inform any person other than TeleCity Limited or the addressees of its existence or contents. If you have received this email and are not a named addressee, please delete it and notify the TeleCity IT department on 0161 226 7643 or by email at techsupport at telecity co.uk.