I would double check the OID that Emerald has set up for you. I found that
it produces the incorrect OID for my Cisco 2511s by default. The are just
one off starting at 0 instead of 1. This makes port 1 have an SNMPUser OID
of .18.104.22.168.22.214.171.124.126.96.36.199.0 instead of the correct OID of
..188.8.131.52.184.108.40.206.220.127.116.11.1 which corresponds to the SNMP return from the
I used this SQL query to populate the correct static OIDs in the SNMPUser
Set SNMPUser=".18.104.22.168.22.214.171.124.126.96.36.199." + convert(varchar(5), Port)
and according to radius -x31 it works now on my 2511s.
Hope this helps,
----- Original Message -----
From: "Brian Johnson" <firstname.lastname@example.org>
Sent: Saturday, April 15, 2000 5:08 PM
Subject: RE: [Emerald] Work on SNMP Concurrency Checking
> Then what is the problem with SNMP concurrency checking and Cisco AS5396s?
> > -----Original Message-----
> > From: email@example.com
> > [mailto:firstname.lastname@example.org]On Behalf Of Dale E. Reed Jr.
> > Sent: Saturday, April 15, 2000 1:10 PM
> > To: email@example.com
> > Subject: Re: [Emerald] Work on SNMP Concurrency Checking
> > Brian Johnson wrote:
> > >
> > > If the radius is set to strip off domains and leading spaces,
> > will the SNMP
> > > show the original or stripped version and does the SNMP query remove
> > > domain and leading spaces from the results. This could be part of the
> > > problem.
> > Its based on your trimdomains setting. If trimdomains is on, then it
> > would be using the trimmed version.
> > --
> > Dale E. Reed Jr. Emerald and RadiusNT
> > __________________________________________
> > IEA Software, Inc. www.iea-software.com
> > For more information about this list (including removal) go to:
> > http://www.iea-software.com/support/maillists/liststart
> For more information about this list (including removal) go to:
For more information about this list (including removal) go to: