> Yes. One other thing you might need to do is set a SNMP
> registry setting for RadiusNT to 1 (or -C on the command line).
> I'm guessing that RadiusNT itself doesn't have the SNMP thread
> running, do the DLL has nothing to talk to and thats why it is
> reporting -1 for everything.
What should the registry key and string value name be? Presently, I have
the following relating to SNMP in RadiusNT:
HKEY_LOCAL_MACHINE\SOFTWARE\IEA\RadiusNT\SNMP\
(Default) (value not set)
Pathname "c:\radius\radntmib.dll"
I didn't notice anything relating to SNMP (other than the key name above)
in the RadiusNT key.
Thanks,
Josh Hillman
hillman@talstar.com
> Josh Hillman wrote:
> >
> > I upgraded our RadiusNT from 2.5.110 to 2.5.124 a week or so ago, but
only
> > replaced radius.exe and radadmin.exe; and added both mib.txt and
> > radntmib.dll to c:\radius\.
> > In Accordance with the instructions on page 32 of RadiusNT25.doc, I
added
> > the appropriate registry keys, then restarted the SNMP service.
> > HKEY_LOCAL_MACHINE\Software\IEA\RadiusNT\SNMP\Pathname
> > c:\radius\radntmib.dll
> > HKEY_LOCAL_MACHINE\SYSTEM\...\SNMP\Parameters\ExtensionAgents\3
> > SOFTWARE\IEA\RadiusNT\SNMP
> >
> > While running snmpwalk on one of our unix systems, all information
received
> > shows "-1" (except for "Config Reset" = 4). The docs say that if
RadiusNT
> > isn't running, that "-1" will show for all entries, but RadiusNT IS
running
> > (without any known problems). SNMP is functioning correctly on the
server
> > in which RadiusNT is installed.
> >
> > There are no subdirectories in c:\radius and in RadiusNT Admin, the
Data
> > and Acct directory locations are left blank.
> >
> > Does RadiusNT 2.5.124 not support the SNMP feature yet?
>
>
> If you have your mib.txt on the UNIX box patched with the RadiusNT
> additions in the MIB.txt of RadiusNT (its CMU compatable) then
> you will get something like below (this is a 2.5.105 production
> server of a customer):
>
> >snmpwalk -v 1 radiusnt public .1.3.6.1.3.79
>
>
radius.radiusAuthentication.radiusAuthServMIB.radiusAuthServMIBObjects.radiu
sAuthServ.radiusAuthServIdent.0
> = "RadiusNT 2.5.105"
>
radius.radiusAuthentication.radiusAuthServMIB.radiusAuthServMIBObjects.radiu
sAuthServ.radiusAuthServUpTime.0
> = 872495
>
radius.radiusAuthentication.radiusAuthServMIB.radiusAuthServMIBObjects.radiu
sAuthServ.radiusAuthServResetTime.0
> = 872495
>
radius.radiusAuthentication.radiusAuthServMIB.radiusAuthServMIBObjects.radiu
sAuthServ.radiusAuthServConfigReset.0
> = running(4)
>
radius.radiusAuthentication.radiusAuthServMIB.radiusAuthServMIBObjects.radiu
sAuthServ.radiusAuthServStats.radiusAuthServAccessRequests
> = 19234
>
radius.radiusAuthentication.radiusAuthServMIB.radiusAuthServMIBObjects.radiu
sAuthServ.radiusAuthServStats.radiusAuthServInvalidRequests
> = 0
>
radius.radiusAuthentication.radiusAuthServMIB.radiusAuthServMIBObjects.radiu
sAuthServ.radiusAuthServStats.radiusAuthServDupAccessRequests
> = 0
>
radius.radiusAuthentication.radiusAuthServMIB.radiusAuthServMIBObjects.radiu
sAuthServ.radiusAuthServStats.radiusAuthServAccessAccepts
> = 19002
>
radius.radiusAuthentication.radiusAuthServMIB.radiusAuthServMIBObjects.radiu
sAuthServ.radiusAuthServStats.radiusAuthServAccessRejects
> = 172
>
radius.radiusAuthentication.radiusAuthServMIB.radiusAuthServMIBObjects.radiu
sAuthServ.radiusAuthServStats.radiusAuthServAccessChallenges
> = 0
>
radius.radiusAuthentication.radiusAuthServMIB.radiusAuthServMIBObjects.radiu
sAuthServ.radiusAuthServStats.radiusAuthServMalformedAccessRequests
> = 50
>
radius.radiusAuthentication.radiusAuthServMIB.radiusAuthServMIBObjects.radiu
sAuthServ.radiusAuthServStats.radiusAuthServAuthenticationBadAuthenticators
> = 0
>
radius.radiusAuthentication.radiusAuthServMIB.radiusAuthServMIBObjects.radiu
sAuthServ.radiusAuthServStats.radiusAuthServPacketsDropped
> = 52
>
radius.radiusAuthentication.radiusAuthServMIB.radiusAuthServMIBObjects.radiu
sAuthServ.radiusAuthServStats.radiusAuthServUnknownType
> = 0
>
radius.radiusAccounting.radiusAccServMIB.radiusAccServMIBObjects.radiusAccSe
rv.radiusAccServIdent.0
> = "RadiusNT 2.5.105"
>
radius.radiusAccounting.radiusAccServMIB.radiusAccServMIBObjects.radiusAccSe
rv.radiusAccServUpTime.0
> = 872496
>
radius.radiusAccounting.radiusAccServMIB.radiusAccServMIBObjects.radiusAccSe
rv.radiusAccServResetTime.0
> = 872496
>
radius.radiusAccounting.radiusAccServMIB.radiusAccServMIBObjects.radiusAccSe
rv.radiusAccServConfigReset.0
> = running(4)
>
radius.radiusAccounting.radiusAccServMIB.radiusAccServMIBObjects.radiusAccSe
rv.radiusAccServStats.radiusAccServAccountingRequests
> = 651504
>
radius.radiusAccounting.radiusAccServMIB.radiusAccServMIBObjects.radiusAccSe
rv.radiusAccServStats.radiusAccServInvalidRequests
> = 0
>
radius.radiusAccounting.radiusAccServMIB.radiusAccServMIBObjects.radiusAccSe
rv.radiusAccServStats.radiusAccServDupAcccountingRequests
> = 1896
>
radius.radiusAccounting.radiusAccServMIB.radiusAccServMIBObjects.radiusAccSe
rv.radiusAccServStats.radiusAccServAccountingResponses
> = 88356
>
radius.radiusAccounting.radiusAccServMIB.radiusAccServMIBObjects.radiusAccSe
rv.radiusAccServStats.radiusAccServMalformedAccountingRequests
> = 0
>
radius.radiusAccounting.radiusAccServMIB.radiusAccServMIBObjects.radiusAccSe
rv.radiusAccServStats.radiusAccServAccountingBadAuthenticators
> = 0
>
radius.radiusAccounting.radiusAccServMIB.radiusAccServMIBObjects.radiusAccSe
rv.radiusAccServStats.radiusAccServPacketsDropped
> = 561252
>
radius.radiusAccounting.radiusAccServMIB.radiusAccServMIBObjects.radiusAccSe
rv.radiusAccServStats.radiusAccServAccountingNoRecord
> = 0
>
radius.radiusAccounting.radiusAccServMIB.radiusAccServMIBObjects.radiusAccSe
rv.radiusAccServStats.radiusAccServUnknownType
> = 0
>
> --
> Dale E. Reed Jr. (daler@iea-software.com)
> _________________________________________________________________
> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> Internet Solutions for Today | http://www.iea-software.com