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

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

OK,
Since I made the change, I checked the Q from all three MAXen.  Now its
making sense...I can see that two of the servers are sending the
'Acounting-On' message (I matched the session ID) and the third is sending a
couple messages:

 > radd q
AcctInfo (0) Pending Q (0):
AcctInfo (0) Backoff Q (2):
  name=<jgottloeb-isdn@sp>, logout=0, nasPort=11201, nasPortType=2
evTim=11343
    sessId=268129958, authTyp=1, durat=0,
len[class,calling#,called#]=[12,0,7]
    id=204, statTyp 1 relT 1623, backT 7200, retryLim 0 tot ret 0
  name=<(null pointer)>, logout=0, nasPort=128, nasPortType=-1 evTim=90
    sessId=919984437, authTyp=3, durat=0,
len[class,calling#,called#]=[0,0,0]
    id=210, statTyp 7 relT 3522, backT 7200, retryLim 0 tot ret 0
AcctInfo (1) Pending Q (0):
AcctInfo (1) Backoff Q (1):
  name=<(null pointer)>, logout=0, nasPort=128, nasPortType=-1 evTim=90
    sessId=919984437, authTyp=3, durat=0,
len[class,calling#,called#]=[0,0,0]
    id=207, statTyp 7 relT 2669, backT 7200, retryLim 0 tot ret 0
 >                                                                   > radd
q

So I guess I need to reset the servers to clear the old messages.  As soon
as I get a chance, I'll reset and write back with the results.

Thanks for everyone's help.                         


Kirk

		-----Original Message-----
		From:	Aydin Edguer [mailto:edguer@MorningStar.Com]
		Sent:	Tuesday, October 06, 1998 9:34 PM
		To:	ascend-users@max.bungi.com
		Subject:	RE: (ASCEND) "Accounting-On" Accounting
Packet?

		> Acct Timeout = 10
		> SessTimer = 0
		> Acct Reset Timeout = 600
		> Acct Checkpoint = 0
		> Allow Stop Only = No
		> Acct Max Retry = 4
		>
		> The way I understand it from top to bottom...

		More information about these parameters can be found in the
"MAX 4000 Series
		Reference Guide".

		> 1.      The system will try to send an accounting packet
to the primary
		>         RADIUS server for 10 seconds.  If it fails to
respond, it will try
		>         the secondary.

		The Acct Timeout means that the MAX will send an
Accounting-Request and wait
		10 seconds for an Accounting-Response.  If it has not
received a response
		then it will retry the message.  If there is more than one
server defined
		then the MAX will switch to a different server on the retry.

		> 2.      Not quit sure what to do with Sess Timer.

		The Sess Timer is used with RADIUS/LOGOUT.  To the best of
my knowledge,
		it is not applicable if you are using normal RADIUS
accounting.

		> 3.      If the secondary server gets the request, the
system will try to
		>         send an accounting packet back to the primary
server after 10 minutes
		>         (600 seconds)

		The Acct Reset Timeout will switch back to Acct Host #1,
after 600 seconds,
		if the accounting is ever switched to Host #2 or #3.

		> 4.      I don't believe I need Checkpoint

		No, probably not.  Checkpoint messages increase the number
of Accounting
		messages your server(s) need to keep up with.  They allow
you to keep
		better track of long connections.

		> 5.      The system is not restricting the accounting
packets due to
		>         something?

		RADIUS accounting messages can be used for troubleshooting
in addition to
		billing.  By default the MAX will send an Accounting Stop
message for any
		connection attempt, whether it was successful or not.  This
means that the
		MAX will send Accounting Stop messages without a
corresponding Accounting
		Start and in some cases without even a User-Name.

		The Allow Stop Only is used to stop the MAX from generating
these lone
		Accounting Stop messages.  It is useful if your RADIUS
server is confused
		by unpaired Accounting messages.  Since the Disconnect Cause
and Connect
		Progress are also recorded by syslog, the information can be
redundant,
		so it can also shrink the detail file without risking losing
too much
		troubleshooting information.

		> 6.      The system will try to send an accounting packet 4
times before
		>         giving up.  This is what im assuming will kill any
further accounting
		>         retries?

		Yes, the Acct Max Retry will allow the MAX to "give up" on
an accounting
		message.  It will stop any future accounting messages from
being retried,
		but I do not believe it will affect existing accounting
messages.

		++ 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>