10-31-2021 11:59 AM
Hi All,
I'm trying to set up a lab in gns3, using route-server-client in a vrf. I'm trying to route the vrf into the global routing table in the route-server. When I apply the command "neighbor default-originate" (which works if there is no vrf) it logs the below error and tear down the bgp connection. I don't have the option of "dont-capability-negotiate" in this IOS version (if that is the issue). Any ideas of what is wrong?
In the route-server:
%BGP-3-NOTIFICATION: received from neighbor x.x.x.x/11 (invalid or corrupt AS path) 3 bytes 400200
In the route-server-client:
%BGP-3-NOTIFICATION: sent to neighbor x.x.x.x/11 (invalid or corrupt AS path) 3 bytes 400200
BGP: x.x.x.x Bad attributes
%BGP-4-MSGDUMP: unsupported or mal-formatted message received from x.x.x.x:
FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF 002D 0200 0000 1540 0101 0040 0200 4003
0478 0003 0180 0404 0000 0000 00
Solved! Go to Solution.
10-31-2021 05:26 PM
Hi @gusgestal ,
The error message means that the BGP message is wrong because the AS PATH is empty. This is actually normal behavior, as the route server functionality is to pass updates from one client to another without inserting its own ASN. The route server is a control plane function and the router server should not be involved in the forwarding path. What you are trying to do is unsupported.
There was some bugs in the older code related to route server functionality. The newer code will not even let you inject routes from the route server to the clients.
Regards,
10-31-2021 01:10 PM
Hello,
which images are you using in GNS3, Dynamips, or IOSv ?
10-31-2021 01:44 PM
Hi,
It's c7200-adventerprisek9-mz.152-4.M7.bin.
10-31-2021 02:35 PM
Hello,
can you send the configs, I'll try this on IOSv. Obviously you are aware that the versions you use are...very old.
10-31-2021 03:03 PM
Hi, thanks, yes, I'm aware of old version. Please see below conf:
route-server:
!
ip vrf internet
rd 160:50
!
interface GigabitEthernet0/0.50
encapsulation dot1Q 50
ip vrf forwarding internet
ip address 120.0.3.1 255.255.255.0
!
interface GigabitEthernet2/0
ip address 4.4.4.1 255.255.255.252
!
router bgp 160
!
address-family ipv4 vrf internet
redistribute static
neighbor 120.0.3.2 remote-as 150
neighbor 120.0.3.2 activate
neighbor 120.0.3.2 route-server-client
!
ip route 120.0.3.0 255.255.255.0 GigabitEthernet0/0
ip route vrf internet 0.0.0.0 0.0.0.0 GigabitEthernet2/0 4.4.4.2 global
route-server-client:
!
ip vrf internet
rd 150:50
!
interface GigabitEthernet1/0.50
encapsulation dot1Q 50
ip vrf forwarding internet
ip address 120.0.3.2 255.255.255.0
!
router bgp 150
!
address-family ipv4 vrf internet
redistribute static
neighbor 120.0.3.1 remote-as 160
neighbor 120.0.3.1 activate
!
ip route vrf internet 0.0.0.0 0.0.0.0 GigabitEthernet1/0.50 120.0.3.1
10-31-2021 02:47 PM
Hello
When using bgp and vrf then you need to specify address families and then within that AF advertise a default.
example:
ip vrf stan
rd 1:10
router bgp x
address-family ipv4 vrf stan
default-information originate
exit-address-family
10-31-2021 03:09 PM
Hello, yes, I'm specifying address family, and when I applied the command "default-information originate" is when I get the errors:
R(config-router-af)#default-information originate
%BGP-3-NOTIFICATION: received from neighbor 120.0.3.2 3/11 (invalid or corrupt AS path) 3 bytes 400200
10-31-2021 03:44 PM
Hello
Why are you adding a static default into the vrf rib when you want it to be advertised via bgp vrf? - in any case looks like the bgp capbailites of each neigbour are not supported, try
neighbor x.x.x.x dont-capability-negotiate
10-31-2021 03:49 PM
Hi, because I need to route that vrf to internet (there is another router with 4.4.4.2 acting as gateway.
I don't have the option "dont-capability-negotiate" in this IOS version.
Thanks,
10-31-2021 04:01 PM
Hello
What IOS are you using and on what rtr?
10-31-2021 04:03 PM
c7200-adventerprisek9-mz.152-4.M7.bin on both.
10-31-2021 05:26 PM
Hi @gusgestal ,
The error message means that the BGP message is wrong because the AS PATH is empty. This is actually normal behavior, as the route server functionality is to pass updates from one client to another without inserting its own ASN. The route server is a control plane function and the router server should not be involved in the forwarding path. What you are trying to do is unsupported.
There was some bugs in the older code related to route server functionality. The newer code will not even let you inject routes from the route server to the clients.
Regards,
10-31-2021 05:36 PM
Thanks Harold. I think I will have to start from scracht my design then.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide