[c-nsp] Small Issue With next-hop-self for VPNv4

Marko Milivojevic markom at PanGalactic.net
Tue Jul 26 05:25:59 EDT 2005


	I am having one small problem, that could be the result of my 
misunderstanding the concept, or something else. I have the following 
topology:

	The topology below is all in, say, AS1


[PE-7600-1: .1]--[P]--[PE-7600-2: .2]--[CE: .3]


	I am running iBGP RR on PE-7600-2 towards CE. 7600's (both running 
12.2(18)SXE2) have MBGP session and everything works fine. CE has iBGP 
session with PE-7600-2 from VRF to PE-7600-2's IPV4 VRF.

	PE-7600-2 is configured with "next-hop-self" toward all neighbors, but, 
neighbors are receiving original next-hop information.

	To clarify, CE will receive routes from PE-7600-1 with next-hop of .1 
and PE-7600-1 will receive routes from CE with next-hop .3. I want them 
both to have the next-hop .2.

	I have found the workaround to configure incoming route-map on sessions 
with PE-7600-2 and do "set ip next-hop peer-address", but I think this 
is very ugly.

	Am I not doing something wrong, or I have stumbled upon something that 
should work but just doesn't?

	CE is Catalyst 3560, running 12.2(25)SEC, but I think that is not 
relevant for this case.

Kind regards,
Marko.



More information about the cisco-nsp mailing list