In a back-to-back VPN connection (prefixes are transferred as ipv4 prefixes in an eBGP session) we observe that the ASBR imports prefixes into vpnv4 with next-hop-self. For ipv4 next-hop-self is not automatically set. Is there any explanation, documentation or even standard for this different treatment of the prefixes?
in address family vpnv4 the next-hop is changed automatically, because it needs to be an address in the global routing table and so the eBGP next-hop learned in the eBGP session in VRF cannot be reused.
This is needed in order to have a working forwarding plane
This does not happen in af ipv4 because the original eBGP next-hop can be retained being part of global routing table on ASBR/PE node, in this case setting next-hop self may solve problems of installation of BGP routes in downstream iBGP peers as they could not know how to reach theoriginal BGP next-hop.
1. Introduction Internet security is important with the increasing
attacks that are happening every day. Many internet and browsing
security solutions exist, but some are not very easy to use or maybe the
question is how can I enable them? In this referen...
Cisco Software Manager Server API Guide This document describes the
programmatic interfaces, RESTful APIs, which are supported by Cisco
Software Manager Server (CSM Server). Overview CSM Server supports a set
of finite RESTful APIs. The first step to use ...
If you are using Cisco's new linux-based Cisco Software Manager server,
then you probably want to make sure there is a startup service for
it.I'll assume that you've already installed the CSM server on a
systemd-based linux system. The commands given belo...