Table of Contents
Advertisement
Route Map Operation
The entries in the route map are processed in the ascending order of the sequence
number. Within the entry, the match statements are processed first. When the match
operation is successful, the set and goto statements within the entry are processed, and
the action associated with the entry is either applied, or else the next entry is processed.
If the end of the route map is reached, it is implicitly denied.
When there are multiple match statements, the primitive match-one or match-all in the
entry determines how many matches are required for success. When an entry has no
match statements, the entry is considered a successful match.
Configuring the Accounting Bin Number for Route Map Entry
To configure an accounting bin number associated with a specified route map entry, use
the following command:
config route-map <route-map> <sequence_number> [add | delete] set
accounting-index 1 value <bin_number>
Where the following is true:
• The
route-map
• The
sequence_number
sequence number must be associated with a match statement.
• The
set accounting-index 1 value
parameter is an accounting bin number.
• The
bin_number
accounting bin number.
Route Map Configuration Examples
Destination-sensitive accounting uses the
to map traffic destinations to accounting bins. Access profiles are applied to route maps.
Route maps are applied to the routing table to count traffic. Traffic is counted in eight
different bins per VLAN. See the ExtremeWare Software User Guide for more information.
MPLS Module Installation and User Guide
parameter identifies a particular route map.
parameter identifies a specific entry in that route map. The
parameter is an integer between 0–7, and allows you to define the
keyword phrase indicates that the following
and
access-profile
Configuring Route Maps
commands
route-map
8-13
Advertisement
Table of Contents
