match/set IP packet or route advertisement ?

From: Jongsoo.Kim@Intelsat.com
Date: Fri Mar 18 2005 - 20:03:40 GMT-3


Guys

I am just summarizing match or set command per category and its usage for ip
packet or route-advertisement.

1) Any match and set under class/policy map is for ip packet.
2) When route-map is used for route filter/manipulation, it is obviously for
ip route advertisement

3) Confusing part is when route-map was used as policy routing for ip packet
routing..
At a glance, I think there is only one macth command that can be used. It is
"match ip address ACL"
And set command are
        set ip next-hop
        set interface
        set ip default next-hop
        set default interface
These set command has only one purpose, which is to tell the packet
forwarding output interface.
I think all other match ( specially such as match ip next-hop, etc ) or set
command under route-map are not for policy-routing( ip traffic) but for
route filter/manipulation( route-advertisement).

Please someone tell me if I am wrong. I will appreciate it.

Thanks

Jongsoo
 

 

############################################################

Building on 40 Years of Leadership - As a global communications leader with 40 years of experience, Intelsat helps service providers,
broadcasters, corporations and governments deliver information and entertainment anywhere in the world, instantly, securely and reliably.

############################################################
This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended
recipient, please contact the sender by reply email and
destroy all copies of the original message. Any views
expressed in this message are those of the individual
sender, except where the sender specifically states them
to be the views of Intelsat, Ltd. and its subsidiaries.
############################################################



This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:47 GMT-3