I guess it would populate the call info in the ServerPorts table if you
numbered your ports starting with 257 as the port number and then going
up by one digit for the first 24 ports. Then, you would have to make
the 25th port number 513 or something and then go up by one digit for
the next 24 modems, etc, etc. So your advice to count the reported port
numbers was also correct because it shows what your nas is sending to
the db as a port number and lends insight into the problem.
By using the commands that Tom showed us, we can make the 3Com NAS
report back port numbers that make sense, such as beginning with the
number 0 or 1.
Mark Colasante
-----Original Message-----
From: Dale E. Reed Jr. [mailto:daler@iea-software.com]
Sent: Wednesday, February 10, 1999 1:30 PM
To: radiusnt@iea-software.com
Subject: Re: [RadiusNT] Server Ports table not populating correctly
Tom Bilan wrote:
>
> It's a problem with the HiperARC. Their port numbering is retarded.
>
> I complained to USR a year ago about this and they added the commands:
> SET PBUS REPORTED_BASE
> SET PBUS REPORTED_PORT_DENSITY
>
> USR/3com defaults to 256 per port and if you are running hiper DSPs
you need
> to change that to 24. If you're running quad modem cards it's 4. If
you
> have both HiperDSPs and Quads in the same chassis they you need to set
it to
> 24 (the highest of the two).
I thought I had them somewhat figured out. Damn, I give up. Why can't
they just make things easy like the rest of them do? :(
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.comFor more information about this list, including removal, pleasesee this URL: http://www.iea-software.com/maillist.html
For more information about this list, including removal, pleasesee this URL: http://www.iea-software.com/maillist.html