On Oct 16, 2018, at 3:03 PM, Maile Halatuituia <maile.halatuituia@tcc.to> wrote:
thank for you kind reply and I do really appreciate. I have configure my ASR and I can receive these attribute on my Radius on the accounting packet from the ASR tomy radius server.
Acct-Input-Octets = 43507 Acct-Output-Octets = 69956 Cisco-AVPair = "acct-input-octets-ipv6=28898" Cisco-AVPair = "acct-output-octets-ipv6=38897"
I understand the top two are the standard ietf attribute and the last ones are cisco AVP attribute. My question is if the Cisco AVP attribute counter already include in the ietf attribute standard counter or all ipv6 traffic only goes to the Cisco AVPair counters.
Again... ask Cisco how their software works. We don't know everything about every possible device from every possible manufacturer.
If all traffic both v4 and v6 already include in the ietf standard attribute counter's (Acct-Input-Octets = 43507 Acct-Output-Octets = 69956) then I don’t have to edit my accounting processed script on my radius, otherwise if that’s not the case then I have to edit to add the ipv6 counter as well from the CiscoAVPair which I already tried but the freeradius debug says it is an unknown attributes.
Because you likely did something wrong. Read the *whole* debug output to see what is going on. Alan DeKok.