[c-nsp] Acct-Session-Id-Count problem

[Sebastian]

Thanks Dennis,

Point 2) is the answer of my problem.
The doc on CCO did not explains that option, and the option itself is
hidden.

Thanks for help

-- 
Regards
Sebastian

31 sierpnia 2005 (19:43:19)

> The unique-identifier which is persistent across reloads is only
> written to NVRAM if:

> 1) The configuration hasn't changed

> 2) An interval of time has passed since the command was first read
> (usually upon bootup). The default interval is 10 minutes (can be
> changed by specifying "radius-server unique-ident <id> interval <n>")

> (1) prevents temporary configuration changes from being unknowingly
> written to NVRAM (you'll see an error message if this pops up) and (2)
> is designed to prevent abusing the NVRAM in case the router is
> experiencing unusual instability.

> You need to be aware of these restrictions in a test environment,
> otherwise the results may not match your expectations. Hopefully in
> production, these restrictions won't limit the usefulness of the
> feature.

> If you still feel the feature isn't working as intended, let me
> know. Thanks.

> Dennis

> Sebastian [piestaga at aster.pl] wrote:
>> Hi,
>> 
>> 
>> I have got the problem with the accounting sessions of the dialup
>> (backup) connections that I have to present to the customers.
>> Everything works fine until the reset occures.
>> Then all accounting counters are cleared and my customers are
>> presented with incorrect data.
>> 
>> I was looking for any 'indicator' that would either be independend on
>> router reset or be as clever as could tell me that such rest took
>> place.
>> I have found the following doc:
>> 
>> http://www.cisco.com/en/US/customer/products/ps6350/products_configuration_guide_chapter09186a0080455a49.html
>> 
>> where Cisco claims that they had implemented an
>> Acct-Session-Id-Count that could solve my
>> problem.
>> Unfortunately, according to my tests, the counter is incremented only when
>> the 'reload' command is entered manualy and only if the
>> 'write memory' command was entered before the 'reload', I mean:
>> 
>> 1. When I simply reload the router, after reload the couter stays the
>> same (no incrementation)
>> 2. When the router is just powered-off, the couter stays the
>> same (no incrementation)
>> 3. When the configuration is saved and the router is manualy reload,
>> then the counter is incremented by 1.
>> 
>> In such case it does not make sense, because I can protect my service
>> in case the router was reset due to power or other problems.
>> 
>> Could you please tell me if you expirienced such a problem or have any
>> idea how to cope with that ?
>> 
>> ---------------------
>> Regards
>> Sebastian
>> 
>> _______________________________________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/