Configure Bgp Accept Own - Cisco NCS 5500 Series Configuration Manual

Bgp configuration ios xr
Hide thumbs Also See for NCS 5500 Series:
Table of Contents

Advertisement

Configure BGP Accept Own

Specifies either the IPv4 or IPv6 address family and enters address family configuration submode.
Step 7
redistribute ospf osp route-policy plcy_namemetric value
Example:
RP/0/RP0/CPU0:router(config-bgp-af)#redistribute ospf osp route-policy aigp_policy metric 1
Allows the redistribution of AiBGP metric into OSPF.
Step 8
commit
Originating Prefixes With AiGP: Example
The following is a sample configuration for originating prefixes with the AiGP metric attribute:
route-policy aigp-policy
set aigp-metric 4
set aigp-metric igp-cost
end-policy
!
router bgp 100
address-family ipv4 unicast
network 10.2.3.4/24 route-policy aigp-policy
redistribute ospf osp1 metric 4 route-policy aigp-policy
!
!
end
Configure BGP Accept Own
The BGP Accept Own feature allows you to handle self-originated VPN routes, which a BGP speaker receives
from a route-reflector (RR). A 'self-originated' route is one which was originally advertized by the speaker
itself. As per BGP protocol [RFC4271], a BGP speaker rejects advertisements that were originated by the
speaker itself. However, the BGP Accept Own mechanism enables a router to accept the prefixes it has
advertised, when reflected from a route-reflector that modifies certain attributes of the prefix. A special
community called ACCEPT-OWN is attached to the prefix by the route-reflector, which is a signal to the
receiving router to bypass the ORIGINATOR_ID and NEXTHOP/MP_REACH_NLRI check. Generally, the
BGP speaker detects prefixes that are self-originated through the self-origination check (ORIGINATOR_ID,
NEXTHOP/MP_REACH_NLRI) and drops the received updates. However, with the Accept Own community
present in the update, the BGP speaker handles the route.
One of the applications of BGP Accept Own is auto-configuration of extranets within MPLS VPN networks.
In an extranet configuration, routes present in one VRF is imported into another VRF on the same PE. Normally,
the extranet mechanism requires that either the import-rt or the import policy of the extranet VRFs be modified
to control import of the prefixes from another VRF. However, with Accept Own feature, the route-reflector
can assert that control without the need for any configuration change on the PE. This way, the Accept Own
feature provides a centralized mechanism for administering control of route imports between different VRFs.
Note
BGP Accept Own is supported only for VPNv4 and VPNv6 address families in neighbor configuration
mode.
Perform this task to configure BGP Accept Own:
BGP Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.2.x
70
Implementing BGP

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents