|[Date Prev] [Date Next]||[Thread Prev] [Thread Next]||[Date Index] [Thread Index]|
RE: [nocol-users] snmpgeneric error message.
That fixed that problem. The other thing is that I was trying to modify the portmaster mdmstat variable: ts5.eden 184.108.40.206 +.220.127.116.11.4.1.307.3.2.3.1.1.3 MdmStat community 32 31 31 (((1<*)&&(*<5))||(*==7)) That's what comes in the file by default, which is nearly identical to the PortsSvc (MdmStat == modems used, PortsSvc == ports serviceable): ts5.eden 18.104.22.168 +.22.214.171.124.4.1.307.3.2.1.1.1.8 PortsSvc community 23 22 22 *!=6 The only thing MdmStat doesn't get that PortsSvc does is when the state = 1. When a line is waiting for a call, the value is one, and when a call is connected, the value is 3. So I figured I could use: (*==3), but that reports I have 0 modems in use, even though the pool happens to have only three modems NOT in use. The output of nocol/run/snmpgeneric.error is as follows: bash-2.02$ more ../run/snmpgeneric.error 24135 I get no error messages about dotest, or anything, there must be something simple I'm missing. Matt Raykowski - Network/Systems Administration Spacestar Communications, Inc. Dial-up to DS-3 Serving - MN WI ND MI IL Voice (612) 996-0000 / Fax (612) 996-0123 www.spacestar.net / firstname.lastname@example.org -----Original Message----- From: email@example.com [mailto:firstname.lastname@example.org]On Behalf Of Ed Landa Sent: Wednesday, May 24, 2000 4:55 PM To: Matt Raykowski Cc: email@example.com Subject: Re: [nocol-users] snmpgeneric error message. > It seems like it's trying to "snmpget 126.96.36.199 community > system.sysUpTime.0.0" for some reason. I'm not sure where the extra .0 is > coming from. The other ones seem to work fine (I'm using it to monitor line > saturation, as well as some other stuff.) It just seems to be this one that > has a problem. Other 'sysUpTimes' variables or just other variables on that device? I use a fuller 'system.sysUpTime.0' in mine and have never seen this. Ed