(ASCEND) Re: outbound radius requests

[James Courtier-Dutton <jcdutton@lucent.com>]

Hello
If you get your radius server to reject "service-type=outbound",  they
will slow down a bit.
In TAOS 8.X there is a setting at the bottom of the radius profile to
switch them off. This might be in earlier versions, I am not sure. It is
"Auth-User=No" or something similar.
Cheers
James


Alan Spicer wrote:
> 
> * Hello,
> One of our TNT's is sending the following to the Radius Server ... in bursts of
> like 10 per second ????
> 
> Fri Feb  4 12:44:24 2000: Received-Authentication: 106/26568
> 'permconn-lpz-dinamita-01-8657' from lapaz_nas6 port 0 Outbound Fri Feb  4
> 12:44:24 2000: Authentication: 106/26568 'permconn-lpz-dinamita-01-8657' from
> lapaz_nas6 port 0 Outbound - OK -- total 0, holding 0 Fri Feb  4 12:44:24 2000:
> Received-Authentication: 107/26569 'permconn-lpz-dinamita-01-8658' from
> lapaz_nas6 port 0 Outbound Fri Feb  4 12:44:24 2000: Authentication: 107/26569
> 'permconn-lpz-dinamita-01-8658' from lapaz_nas6 port 0 Outbound - OK -- total
> 0, holding 0 Fri Feb  4 12:44:25 2000: Received-Authentication: 108/26570
> 'permconn-lpz-dinamita-01-8659' from lapaz_nas6 port 0 Outbound Fri Feb  4
> 12:44:25 2000: Authentication: 108/26570 'permconn-lpz-dinamita-01-8659' from
> lapaz_nas6 port 0 Outbound - OK -- total 0, holding 0 Fri Feb  4 12:44:25 2000:
> Received-Authentication: 109/26571 'permconn-lpz-dinamita-01-8660' from
> lapaz_nas6 port 0 Outbound Fri Feb  4 12:44:25 2000: Authentication: 109/26571
> 'permconn-lpz-dinamita-01-8660' from lapaz_nas6 port 0 Outbound - OK -- total
> 0, holding 0
> 
> * This seems to be related to the following documentation of the TNT's:
> 
> Perm-Conn-Upd-Mode
> Description: Specifies under what circumstances the MAX TNT performs nonintrusive
> remote updates of the configurations of permanent connections.
> Usage: Specify one of the following values:
> ° All (the default) specifies that, if they are fetched from the RADIUS server, all existing
> permanent connections will be torn down and reestablished following the update. This
> setting causes service interruption every time any nailed profile is updated or added.
> ° Changed specifies that only changed permanent connections will be torn down and
> reestablished.
> Example: set perm-conn-upd-mode=changed
> Location: System
> See Also: Analog-Encoding, Call-Routing-Sort-Method, Idle-Logout,
> Master-Shelf-Controller, Name, New-NAS-Port-ID-Format, Parallel-Dialing, SessionID-Base,
> Shelf-Controller-Type, Single-File-Incoming, System-Rmt-Mgmt, Use-Trunk-Groups
> 
> * But no matter how I set that ... it still keeps sending like that. Is there
> another place that I need to disable that? We do not update any such thing
> about permanent connections from the Radius Server, so this is wasted
> processing and bandwidth (and log/disk space). Our other TNT's do not seem
> to be doing this. (It says nonintrusive, but 10 times per second bursts - almost
> constantly, is certainly INTRUSIVE, especially if it is basically a not needed.)
> 
> Thanks for any help or suggestions ...
> 
> --
> Alan Spicer (InterNIC:AGS14)
> Systems Administration
> aspicer@ifxcorp.com
> ++ Ascend Users Mailing List ++
> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> To get FAQ'd:   <http://www.nealis.net/ascend/faq>
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>