Re: [RadiusNT] SNMP concurrency checking
Dale E. Reed Jr. ( (no email) )
Fri, 27 Aug 1999 09:26:51 -0700
Herman verschooten wrote:
>
> Say Dale,
> We've got a RA8000 from Bay-Nortel, i've seen that there's an entry for the
> 5399, but the proble we face is that bay has changed their entry to
>
> .1.3.6.1.4.1.15.2.16.1.2.1.3.1.x for asynchrone calls, where x is the
> port-number
> .1.3.6.1.4.1.15.2.16.1.2.1.3.9.x for synchronce calls
> .1.3.6.1.4.1.15.2.16.1.2.1.3.10.x for ta calls
>
> but what they sent in the access-request is either
>
> a. when radius-port-enconding is set to channel
>
> aabcc
>
> where aa is the connection type (10 for async, 20 for sync, etc)
> where b is the PRI
> where cc is the connection
>
> b. when set to device
>
> you just get the port-number, eg when you have an async call on port 10,
> this will be 10. When you get a sync (ISDN) call on port 10, this will alse
> be 10. You can never get two simultanous calls with the same port-number.
> But how can you do you set this up ?
You need to find what the SNMP OID for them is. For example, do
they allow a lookup based on the port number (no matter what the
scheme) on some SNMP tree, or are they always 0-x types SNMP
requests? It really doesn't matter, as long as you can setup
a mapping of them. For example, lets say in radius-port-encoding
mode, they still do the physical port 0-x type SNMP lookups.
You would just define all three sets of ports (async, sync, ta)
where the first entry of each would point to the first OID,
the second entries of each to the second OID, etc (remember I do
NOT know if that is how they do it or not).
If you want to give me SNMP access to one of them and access
to your DB, I'd be happy to check it out.
--
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