On 10/06/2024 11:20, Saku Ytti wrote:
I don't think there is enough information here to understand the
problem.
Since you asked:
Router B is exaBGP sending announcements to router A (128.139.220.90).
192.0.2.1 is a GigE interface on router A. I want to null0 all traffic
which is easy to do b
Hi Hank
If I understand correctly you are trying to send bgp routes to a router
that have a next hop local to the router?
I think this would contrast with the route selection process and not be
accepted.. as the route would not be installable. i.e. The router would
route it to itself on the Ge i
On 10/06/2024 11:05, Hank Nussbacher wrote:
Ignore. There was an ACL on GigabitEthernet0/0/0/43.1 that blocked the
traffic.
Nothing like solving your own issues.
-Hank
I have a simple iBGP peer defined as follows:
neighbor 128.139.197.146
remote-as 378
update-source Loopback0
addre
Hi,
On Mon, Jun 10, 2024 at 11:05:18AM +0300, Hank Nussbacher via cisco-nsp wrote:
> If the feed sets the IP to 192.0.2.2 then the BGP routes appear in the
> routing table. If I then change the IP address on interface
> GigabitEthernet0/0/0/43.1 to 192.0.2.2 then the routes disappear as well
> af
I don't think there is enough information here to understand the problem.
So you have
RouterA - RouterB
RouterA is 192.0.2.1/24
RouterB is 128.139.197.146
RouterB advertises bunch of /32s to routerA, with next-hop 192.0.2.1?
This seems nonsensical to me, where is routerA supposed to send the
p
I have a simple iBGP peer defined as follows:
neighbor 128.139.197.146
remote-as 378
update-source Loopback0
address-family ipv4 unicast
I have a GigE interface defined as:
interface GigabitEthernet0/0/0/43.1
ipv4 address 192.0.2.1 255.255.255.0
encapsulation dot1q 1
This iBGP peer f
