Scribd
Upload
163 views

Routing Process Picture

Policy routing allows routing of packets based on criteria other than the destination address, such as source address, application type, or input interface. Packets can be routed to specific outputs or next hops using route maps with match and set commands to match packet characteristics and set routing values. Administrative distance and metrics are used to determine the preferred path when multiple routes to the same destination exist.

Uploaded by

lefreak1979
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
163 views

Routing Process Picture

Policy routing allows routing of packets based on criteria other than the destination address, such as source address, application type, or input interface. Packets can be routed to specific outputs or next hops using route maps with match and set commands to match packet characteristics and set routing values. Administrative distance and metrics are used to determine the preferred path when multiple routes to the same destination exist.

Uploaded by

lefreak1979
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

route-map map-tag [permit | deny] [sequence-number] FOR POLICY ROUTING

match ip address {access-list-number | name} [...access-list-number | name]


The CISCO Routing Process
match length min max including POLICY Routing

Policy Routing
set ip next-hop ip-address [...ip-address] DATA Packets
on incoming interface
set interface type number [...type number]
selected by: Output Access-list
Input Access-list
NAT / PAT Queueing
NAT ip policy route-map map-tag Accounting

DATA no match
or deny or Recursive Lookup
set default interface type number [... type number] OUTGOING to same protocol
set ip default next-hop ip-address [...ip-address]

distribute-list {access-list-number | name} out [interface-name]


passive-interface type number
offset-list {access-list-number | name} out
INCOMING from REMOTE Routing Table offset [type number]

S ... Static
C ... Connected
offset-list {access-list-number | name} in offset [type number] x .... dynamic routing
distance weight [address mask [access-list-number | name]]
Route-TAGs
Route-TAGs
distribute-list {access-list-number | name} in [type number] OUTGOING coming from other protocol
passive-interface type number (only for Link State and EIGRP)
ip access-group {access-list-number | name} in
( for selected protocol)
distribute-list {access-list-number | name} out
Metric [routing-process |autonomous-system-number]

Incoming Outgoing
ROUTE Information Routes
Route Processing Route Processing

Administrative Distance Metric


INCOMING from LOCAL OUTGOING to another protocol
0 Connected
1 Static Route redistribute protocol [process-id] {level-1 | level-1-2 | level-2} [metric
5 EIGRP Summary metric-value] [metric-type type-value] [match {internal | external 1 |
20 External BGP external 2}] [tag tag-value] [route-map map-tag] [weight weight] [subnets]
ip route prefix mask {address |
90 Internal EIGRP default-information redistribution:
interface} [distance] [tag tag]
100 IGRP default-information originate [always] [metric metric-value] [metric-type type-
[permanent]
110 OSPF value] {level-1 | level-1-2 | level-2} [route-map map-name](RIP/OSPF)
and from connected interfaces
115 IS-IS default-information {in | out} {access-list-number | name}(IGRP/EIGRP)
120 RIP
170 External EIGRP route-map map-tag [permit | deny] [sequence-number] FOR ROUTE REDISTRIBUTION
200 Internal BGP match interface type number [...type number]
255 <don´t use> match ip route-source {access-list-number | name}[...access-list-number | name] set automatic-tag
match metric metric-value set level {level-1 | level-2 | level-1-2 | stub-area | backbone}
match route-type {local | internal | external [type-1 | type-2] | level-1 | level-2} set local-preference
match tag tag-value [...tag-value] set metric metric-value
match ip address {access-list-number | name} [...access-list-number | name] set metric-type {internal | external | type-1 | type-2}
match ip next-hop {access-list-number | name}[...access-list-number | name] set origin {igp | egp autonomous-system | incomplete}
set tag tag-value
set next-hop next-hop

You might also like