next-hop-self for update received from iBGP neighbor

[Tatiana]

Hi,

will next-hop-self still work for bgp update received from iBGP neighbor in ExtremeXOS?

for example for cisco additional routemap is required:

route-map RM-NHSset ip next-hop peer-address neighbor X.X.X.X route-map out RM-NHS While for juniper it works by default for iBGP neighbors within different clusters

[Henrique]

Hi Tatiana,

To configure outgoing updates to the specified neighbors to specify the address of the BGP connection originating the update as the next hop address, use the following command:

configure bgp neighbor next-hop-self

IPv4 unicast address family will be used by default. For IPv6 you must specify the option in the command.

[Henrique]

Hi Tatiana, thanks for the feedback.

I have created an article with those steps:
https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-configure-a-BGP-router-reflector-wi...

[Tatiana]

Thanks Henrique, it helped,
We tested it on the equipment and route-map made his work.

[Henrique]

Hi, I have just tested with the policy below and worked:

Policy: regrabgp

entry R1 {
if match any {
nlri 123.123.123.0/24 exact;
} then {
next-hop ;
permit ;
}
}

To match any routes with /24 mask-length you can use:

Policy: regrabgp

entry R1 {
if match any {
nlri any/24 exact;
} then {
next-hop ;
permit ;
}
}

BGP configuration for router B for the neighbor Router A:

create bgp neighbor 192.168.1.8 remote-AS-number 100 multi-hop
configure bgp neighbor 192.168.1.8 route-reflector-client
configure bgp neighbor 192.168.1.8 source-interface ipaddress 192.168.1.6
configure bgp neighbor 192.168.1.8 route-policy out regrabgp
enable bgp neighbor 192.168.1.8


Thanks Stephane to mention the routing-policy concepts. 🙂

Tatiana, please let us know if that worked for you.