Re: [nsp] BGP Policy Acct and MPLS

From: Neil J. McRae (neil@COLT.NET)
Date: Tue Jun 12 2001 - 06:15:29 EDT


I'd say this is a bug, there shouldn't be any reason on the
ingress why things are done differently.

Regards,
Neil.

> Has anyone on this list had any experiences with BGP Policy
> Accounting used in conjunction with label switching (or
> tag-switching for that matter).
>
> I'm attempting to use BGP PA to analyse the ingress traffic
> on an interface of an edge router. I've configured policy
> simply based on IP prefix at this stage.
>
> The CEF table is coloured with the appropriate traffic_index
> but I'm finding that accounting only seems to be collected for
> some classes. It seems that traffic to label switched destinations
> is not accounted for.
>
> Eg. here's the CEF statistics - notice that traffic classes
> 1 and 4 are zeroed out. These destinations are label switched.
> Traffic classes 2 and 3 are not.
>
> router#show cef interface policy-statistics
> POS4/0 is up (if_number 8)
> Corresponding hwidb fast_if_number 8
> Corresponding hwidb firstsw->if_number 8
> BGP based Policy accounting is enabled
> Index Packets Bytes
> 1 0 0
> 2 22793933 13346561348
> 3 83934938 45008514252
> 4 0 0
> 5 0 0
> 6 0 0
> 7 0 0
> 8 40947165 7009408861
>
> Here's the CEF detail outputs for prefixes in each traffic class.
> The only difference I see is the "fast tag rewrite" on 1 and 4,
> which is coincidental with the zero accounting data.
>
> router#show ip cef 212.23.58.0 detail
> 212.23.58.0/24, version 103443, cached adjacency 212.23.40.5
> 0 packets, 0 bytes
> tag information from 212.23.38.4/32, shared
> local tag: 19
> fast tag rewrite with Gi3/2, 212.23.40.5, tags imposed {17}
> Flow: AS 0, mask 24, traffic_index 1
> via 212.23.38.4, 0 dependencies, recursive
> next hop 212.23.40.5, GigabitEthernet3/2 via 212.23.38.4/32
> valid cached adjacency
> tag rewrite with Gi3/2, 212.23.40.5, tags imposed {17}
>
> router#show ip cef 212.23.60.0 detail
> 212.23.60.0/24, version 103444, cached adjacency 212.23.34.45
> 0 packets, 0 bytes
> tag information from 212.23.34.241/32, shared
> local tag: 23
> Flow: AS 0, mask 24, traffic_index 2
> via 212.23.34.241, 0 dependencies, recursive
> next hop 212.23.34.45, GigabitEthernet3/1 via 212.23.34.241/32
> valid cached adjacency
> tag rewrite with Gi3/1, 212.23.34.45, tags imposed {}
>
> router#show ip cef 212.23.40.128 detail
> 212.23.40.128/25, version 103442, cached adjacency 212.23.40.5
> 0 packets, 0 bytes
> tag information from 212.23.38.4/32, shared
> local tag: 19
> fast tag rewrite with Gi3/2, 212.23.40.5, tags imposed {17}
> Flow: AS 0, mask 25, traffic_index 4
> via 212.23.38.4, 0 dependencies, recursive
> next hop 212.23.40.5, GigabitEthernet3/2 via 212.23.38.4/32
> valid cached adjacency
> tag rewrite with Gi3/2, 212.23.40.5, tags imposed {17}
>
> Software is IOS 12.0(16)ST on GRP but I see similar symptoms
> with same version on RSP with/without dCEF. Any ideas?
>
> -- Adam.
>
>



This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:41 EDT