Thanks Heinrich, AddToRequestIfNotExist was the one that fixed it. I didn't see
it in the documentation myself because I was looking in the AuthBy
sections, not the Client section.
Just to make it clear, Hugh, there wasn't a problem with the 0 value being
added in place of the missing
Hi Michael, this was indeed a typo in my original post. I am using
AcctSQLStatement, and not AuthSelect. AddToRequestIfNotExist did fix the
problem; as you suggest, Radiator works fine without it, but my installation
does complain about it a lot. Thanks.
--
Michael Newton
Manager, Information
On 7 Dec 2011 at 9:15, Hugh Irvine wrote:
Hi, most of our NAS devices include Acct-Output-Gigawords in
their accounting requests, so we store it in our SQL database using
an AuthSelect parameter with the
%{IntegerValue:Acct-Output-Gigawords} syntax. But, we have a few
devices that do not
Isn't AuthSelect used for authentication queries in AuthBy SQL? not
accounting inserts? Aren't you suppose to be using a combination of
AccountingTable and AcctColumnDef or use AcctSQLStatement?
I use both ways, for different purposes. be aware i use some of my own custom
attributes, ie
Hi,
Maybe I was not clear enough. The line
AddToRequestIfNotExist Acct-Input-Gigawords=0
should be added to the Client section and is processed long before
any AuthBy. It just makes sure, that Acct-Input-Gigawords exists
in any request (either with it's original value or 0). This should
Maybe i wasn't clear ether. I was suggesting that there's something else
wrong. I use Gigawords and have a nas with old IOS and doesn't send the
attribute. But if the attribute isn't there, radiator is fine with it. It
doesn't show an error. You shouldn't have to use AddToRequestIfNotExist.
On 12/06/2011 07:34 AM, Michael Newton wrote:
Hi, most of our NAS devices include Acct-Output-Gigawords in their
accounting requests, so we store it in our SQL database using an
AuthSelect parameter with the %{IntegerValue:Acct-Output-Gigawords}
syntax. But, we have a few devices that do not
Hello Michael -
Use 0%{IntegerValue:Acct-Output-Gigawords} (leading zero).
regards
Hugh
On 6 Dec 2011, at 16:34, Michael Newton wrote:
Hi, most of our NAS devices include Acct-Output-Gigawords in their accounting
requests, so we store it in our SQL database using an AuthSelect parameter
Thanks, I had already tried that after seeing it in another list posting, with
no effect. I believe the error is resulting from the thing inside the {} not
being present in the request, isn't it?
Mike
On 2011-12-06, at 12:21 AM, Hugh Irvine h...@open.com.au wrote:
Hello Michael -
Use
Hello Michael -
If the attribute is not present, you will just get a 0 (zero) in the
expression which should always work.
To say any more we will need to see a copy of the configuration file (no
secrets) and a trace 4 debug showing what is happening.
regards
Hugh
On 7 Dec 2011, at 03:17,
Hi, most of our NAS devices include Acct-Output-Gigawords in their accounting
requests, so we store it in our SQL database using an AuthSelect parameter with
the %{IntegerValue:Acct-Output-Gigawords} syntax. But, we have a few devices
that do not include it. So every time the AuthSelect is run
Hello Brian -
On Thursday 16 August 2001 12:08, Brian Morris wrote:
Hi All,
I am receiving the following error in our log file :
ERR: Attribute number 87 (vendor ) is not defined in your dictionary
Can anyone tell me what this attribute is and (ideally) the line to put
into our
Hi All,
I am receiving the following error in our log file :
ERR: Attribute number 87 (vendor ) is not defined in your dictionary
Can anyone tell me what this attribute is and (ideally) the line to put into
our dictionary file to stop these errors.
We are using a Unisphere ERX for our ADSL
13 matches
Mail list logo
