Just before you emailed me, I noticed tone of the problems:
+.1.3.6.1.4.1.307.3.2.3.1.1.3 MdmStat
+.1.3.6.1.4.1.307.3.2.3.1.1.8 PortsSvc
Note the trailing 8, instead of 3. That contributed to the problem as
well. As soon as I start snmpwalking the right MIB, I compared the values
to my 'sho ses' and wallah, it made sense. Thanks for the listing, though,
that's going to be helpful for something else I'm working on.
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 / mattr@spacestar.net
-----Original Message-----
From: elanda@beavis.comstar.net [mailto:elanda@beavis.comstar.net]On
Behalf Of Ed Landa
Sent: Thursday, May 25, 2000 1:35 PM
To: Matt Raykowski
Cc: nocol-users@navya.com
Subject: Re: [nocol-users] snmpgeneric error message.
> ts5.eden 206.191.207.205 +.1.3.6.1.4.1.307.3.2.3.1.1.3 MdmStat community
> 32 31 31 (((1<*)&&(*<5))||(*==7))
This checks for modems in an abnormal status.
livingstonModemStatus OBJECT-TYPE
SYNTAX INTEGER {
none(1),
bound(2),
connecting(3),
active(4),
test(5),
down(6),
ready(7),
halt(8),
admin(9)
}
> 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.
3 is for modems that are in the carrier negotation phase. Try using 4
and see if that gives you the correct result.
Ed
|