Hi Guys,

I have a problem to establish an new ibgp - session. Router 1 (R1) has an external working ebgp-session, also on router 2 (R2). To get redundancy I will setup an internal bgp-session. The connection between R1 and R2 was a DAC-cable und ping works well. The network between R1 and R2 is /31, but testing with a /30 has the same issue.

bgp-config on R1:
name="ibgp_1"
remote.address=x.y.z.231/32 .as=214000
local.address=x.y.z.230 .role=ibgp
tcp-md5-key="1xxxxxxx9" connect=yes listen=yes routing-table=main as=214000 nexthop-choice=force-self address-families=ip
output.redistribute=connected .default-originate=if-installed

bgp-config on R2:
name="ibgp_1"
remote.address=x.y.z.230/32 .as=214000
local.address=x.y.z.231 .role=ibgp
tcp-md5-key="1xxxxxxx9" connect=yes listen=yes routing-table=main as=214000 nexthop-choice=force-self address-families=ip
output.redistribute=connected .default-originate=if-installed

In torch I see on both router packets to port 179.

Have anyone an idea to fix the problem?

Best regards
Rheinhesse

Try to set next-hop to default.

no change, same issue.

Try to check if you can ping x.y.z.231 from x.y.z.230 setting the source of ping x.y.z.230 on R1.
You can do tracroute to check if session tries to go via local DAC cable. Mayby it does not "like" this short path.