cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1775
Views
0
Helpful
5
Replies

AAA Accounting Gigawords

jalock
Level 1
Level 1

We are trying to implement the use of Gigawords with a Cisco 7201 running the following: Cisco IOS Software, 7200 Software (C7200P-IPBASEK9-M), Version 15.0(1)M3, RELEASE SOFTWARE (fc2).  Based on the documentation gigawords is enabled by default, and we even issued the command aaa accounting gigawords and reloaded the router, however our radius server is still not getting the attributes.  Even in the debugs, the router appears to not be sending them either.  We have a support ticket open with Cisco, but i thought i would ask and see if anyone else has had a similar problem.

5 Replies 5

Are you not seeing the attribute at all, or is it not reflecting the correct data after it gets to 1GB? If the latter you may be running into CSCsr13399 (or at least the symptoms of it).

Thanks for the reply.  We are not seeing the attributes 52/53 come across at all, either in the debugs or to the radius server.  The 32 bit counter rolls once it reaches 4G (2^32) and resets to 0.  Not seeing the command (aaa accounting gigawords) in the startup config or via show run all as a default.

jalock
Level 1
Level 1

Update

After what has been a long time, Cisco has been able to confirm that gigawords is not working in the 15.x code, and looks like a continuation of a previous bug (CSCin67619).

We are now in the process of planning to revert back to 12.4, trying to confirm the exact version that will work and provide the gigawords.

Does anyone know if there are plans to fix this in the 15.X code or downgrading is the only option still?

There was no timeframe or indication that a fix would be forthcoming.

The last update I received indicated that our Service Request now "currently in a status of Bug/Defect Required".

Our service request was linked to this bug, CSCtn05407, however when i checked on that it indicates "CSCtn05407 has been superseded by CSCsj35342".  The description of that bug does not relate to the issue we initially reported.

Gigawords has been working well for us since reverting to  12.4(24)T4.