Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: (ASCEND) "Accounting-On" Accounting Packet?

Thanks for the response,
The system is not rebooting (its actually been stable since the upgrade to
6.1.3) , no-one is resetting the accounting, nor are there any RADIUS SNMP
packets being sent to the system.  So I guess it must be in the Backoff Q.
How long will it retransmit before it is dropped?  Look at the delay
time...over 162 hours!  What gives?  Can I clear the Q?

Tue Oct 06 01:17:23 1998
	NAS-IP-Address = 10.1.1.10
	Acct-Status-Type = Accounting-On
	Acct-Delay-Time = 585619
	Acct-Session-Id = "919984437"

Kirk
 

		-----Original Message-----
		From:	basher@alpha.ces.cwru.edu
[mailto:basher@alpha.ces.cwru.edu]
		Sent:	Tuesday, October 06, 1998 3:22 PM
		To:	ascend-users@max.bungi.com
		Subject:	RE: (ASCEND) "Accounting-On" Accounting
Packet?

		> However, I'm running MSSQL on NT and am receiving these
errors from the
		> accounting logs files.
		>
		> Mon Oct 05 00:04:48 1998: Received-Accounting: 2/530 from
129.4.247.253 Accounting-On
		> Mon Oct 05 00:04:48 1998: odbc_get_stop_whereclause()
Can't generate WHERE clause, record is missing User-Name
		> Mon Oct 05 00:04:48 1998: send_reply: Rejecting unknown
request type (4)
		> 
		> I'm receiving the same error from three different MAX
4004's and each Unit
		> is sending the message exactly 2 hours apart.  I already
check the
		> constraints in the Accounting table and found only one
with Acct_Session_Id
		> set to 'NOT NULL'.  So why is SQL rejecting this
accounting packet?
		 
		SQL is not rejecting the accounting message, the RADIUS
server is rejecting
		the attempt to add the accounting record to SQL.  The RADIUS
server is 
		objecting to the attempt because there is no User-Name
attribute in the
		packet.  There is no User-Name in the packet because the
Accounting-On 
		message is not associated with a user, it is associated with
the NAS.
		The RADIUS server requires the User-Name attribute because
that is
		one of the primary indexes into the SQL database.

		You are seeing the message every two hours because (a) the
packet is in
		the Accounting Backoff Q, which is where accounting packets
are placed
		after trying to send the packet three times to each RADIUS
accounting server
		that is defined or (b) because the MAX is rebooting every
two hours or
		(c) someone is disabling and re-enabling RADIUS accounting
every two
		hours [maybe you have an SNMP process that is running at
that time].
		++ 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>