topic Re: CoA NAKs between PSNs in Network Access Control

CoA NAKs between PSNs

paul — Mon, 09 Oct 2017 13:45:49 GMT

In 2.3, in my live logs I see a pretty constant stream of dynamic author failures and if you dig into them they are CoA Requests between the PSNs with the receiving PSN NAKing it. I think it is MAR cache sync causing the CoAs as I see this in the details:

acs:mar-cache-operation=query-entry, cts-pac-opaque=****

We aren't using MAR cache, and I don't have MAR cache distribution enabled.

I am just treating this as noise in the live logs, but wanted to know if I should be digging into this.

Thanks.

Re: CoA NAKs between PSNs

hslai — Mon, 09 Oct 2017 13:56:04 GMT

This is a known issue -- CSCve84667 -- and planned for 2.3 Patch 1.

Re: CoA NAKs between PSNs

mmcfarlin456 — Tue, 10 Oct 2017 03:55:06 GMT

Can you give a rough idea on when to expect Patch 1?

Re: CoA NAKs between PSNs

hslai — Tue, 10 Oct 2017 05:12:41 GMT

Sorry but we cannot comment on a release date in a public forum. It's taking more time as we are adding a couple of critical fixes.

Re: CoA NAKs between PSNs

marco.merlo — Tue, 18 Jun 2019 07:11:04 GMT

Hi Paul,

Actually I have the reverse problem: mar cache distribution is enabled but apparentely not working. Since both TAC and my TAM are not able to provide me any useful troubleshooting tip might you please so kind to tell me how did you get the logs messages you indeed didn't expect?

Regards

Re: CoA NAKs between PSNs

Jason Kunst — Tue, 18 Jun 2019 11:26:07 GMT

If tac is it useful please escalate the case

Re: CoA NAKs between PSNs

marco.merlo — Tue, 18 Jun 2019 11:36:53 GMT

Thanks

At the end I figured how to get the log messages I need setting aaa-runtime log at trace level.

Details here

https://community.cisco.com/t5/cisco-bug-discussions/cscvo73749-mar-cache-distribution-is-not-enabled-even-when-it/m-p/3872315/highlight/false#M9474

Regards

Re: CoA NAKs between PSNs

travis.kamish — Wed, 08 Apr 2020 19:04:58 GMT

it seems I have the same problem and I am running version 2.4 patch 11 and that indicated this has been fixed in 2.4. Are we sure this bug did not come back?