Table of Contents
Advertisement
create access-profile arm2 type ipaddress
config access-profile arm2 mode none
config access-profile arm2 add 10 permit ipaddress 192.168.101.0/24
create access-profile arm3 type ipaddress
config access-profile arm3 mode none
config access-profile arm3 add 10 permit ipaddress 192.168.102.0/24
2 Create a route map named ip_example.
create route-map ip_example
config route-map ip_example add 100 permit match-one
config route-map ip_example 100 add match nlri-list arm1
config route-map ip_example add 200 permit match-one
config route-map ip_example 200 add match nlri-list arm2
config route-map ip_example add 300 permit match-one
config route-map ip_example 300 add match nlri-list arm3
3 Assign bin numbers to each route map.
config route-map ip_example 100 add set accounting-index 1 value 3
config route-map ip_example 200 add set accounting-index 1 value 4
config route-map ip_example 300 add set accounting-index 1 value 5
4 Correlate the route map to direct routes.
config iproute route-map direct ip_example
The
show accounting
per VLAN. Bin 0 is always the default bin and is used to maintain traffic statistics for
packets that do not match any of the route map profiles. Bins that have the same packet
and octet count are grouped together. All maintained statistics are 64-bit values.
The
show ipr
particular route.
Configuring Destination-Sensitive Accounting Based on BGP Community
Strings
Figure 8-2 is an example of destination-sensitive accounting based on BGP community
strings.
MPLS Module Installation and User Guide
command lists the packet and octet counts for each bin number
command displays the bin number, if any, that is associated with a
Configuring Route Maps
8-15
Advertisement
Table of Contents
