match origin
Use this command to match origin code. The origin attribute defines the origin of the path information. The egp parameter is indicated as an e in the routing table, and it indicates that the origin of the information is learned via EGP (Exterior Gateway Protocol). The igp parameter is indicated as an i in the routing table, and it indicates the origin of the path information is interior to the originating AS. The incomplete parameter is indicated as a ? in the routing table, and indicates that the origin of the path information is unknown or learned through other means. If a static route is redistributed into BGP, the origin of the route is incomplete.
This command specifies the origin to be matched. If there is a match for the specified origin, and permit is specified when you created the route-map, the route is redistributed or controlled as specified by the set action. If the match criteria are met, and deny is specified, the route is not redistributed or controlled. If the match criteria are not met, the route is neither accepted nor forwarded, irrespective of permit or deny specifications.
The route specified by the policies might not be the same as specified by the routing protocols. Setting policies enable packets to take different routes depending on their length or content. Packet forwarding based on configured policies overrides packet forwarding specified in routing tables.
Note: This command is valid only for BGP.
Use the no parameter with this command to disable this matching.
Command Syntax
match origin (egp|igp|incomplete)
no match origin (egp|igp|incomplete|)
Parameters
egp
Remote exterior gateway protocol.
igp
Local internal gateway protocol.
incomplete
Unknown heritage.
Default
No default value is specified
Command Mode
Route-map mode
Applicability
This command was introduced before OcNOS version 1.3.
Example
#configure terminal
(config)#route-map myroute deny 34
(config-route-map)#match origin egp
Last modified date: 07-13-2023