1
General Discussion / BGP multiple ASN
« on: September 11, 2023, 10:30:04 pm »
Hello everyone.
I have one prefix, e. g. 170.234.78.0/24 which is announced by e. g. ASN 28929 on IPv4, everything works fine with that.
Now, my organisation need to announce prefix IPv6, e. g. 2805:1a5::/48 with another ASN 273141
How can I configure multiple BGP instances with different ASNs? In GUI I cannot look nothing to do that.
I did try in CLI on /usr/local/etc/frr/bgpd.conf like the follow, with no success using VRF option in config file:
! Zebra configuration saved from vty
!
log syslog notifications
frr defaults traditional
!
!
router bgp 28929
no bgp default ipv4-unicast
no bgp ebgp-requires-policy
bgp network import-check
neighbor 21.173.52.185 remote-as 24764
neighbor 21.173.52.185 update-source igb1
address-family ipv4 unicast
redistribute connected
network 170.234.78.0/24
neighbor 21.173.52.185 activate
neighbor 21.173.52.185 next-hop-self
neighbor 21.173.52.185 prefix-list USACTEC-IN in
neighbor 21.173.52.185 prefix-list USACTEC-OUT out
neighbor 21.173.52.185 route-map RMUSACTEC-IN1 in
neighbor 21.173.52.185 route-map RMUSACTEC-OUT1 out
exit-address-family
!
address-family ipv6 unicast
redistribute connected
exit-address-family
!
!
!
router bgp 273141 vrf jaimecov6
neighbor 2803:bf40::5 remote-as 24764
neighbor 2803:bf40::5 update-source igb1
!
address-family ipv6 unicast
redistribute connected
network 2805:1a5::/48
neighbor 2003:bf40::5 activate
neighbor 2003:bf40::5 next-hop-self
neighbor 2003:bf40::5 prefix-list USACTECv6-IN in
neighbor 2003:bf40::5 prefix-list USACTECv6-OUT out
neighbor 2003:bf40::5 route-map RMUSACTECv6-IN1 in
neighbor 2003:bf40::5 route-map RMUSACTECv6-OUT1 out
exit-address-family
!
ip prefix-list USACTEC-IN seq 3 permit any
ip prefix-list USACTEC-OUT seq 1 permit 170.234.78.0/24
!
ip prefix-list USACTECv6-IN seq 5 permit any
ip prefix-list USACTECv6-OUT seq 4 permit 2805:1a5::/48
!
!
!
route-map RMUSACTEC-IN1 permit 3
match ip address prefix-list USACTEC-IN
route-map RMUSACTEC-OUT1 permit 1
match ip address prefix-list USACTEC-OUT
!
route-map RMUSACTECv6-IN1 permit 5
match ip address prefix-list USACTECv6-IN
route-map RMUSACTECv6-OUT1 permit 4
match ip address prefix-list USACTECv6-OUT
!
!
line vty
!!!
# service frr restart
Stopping bgpd.
Waiting for PIDS: 58719.
Stopping zebra.
Waiting for PIDS: 57401.
Checking zebra.conf
2023/09/11 14:20:43 ZEBRA: [EC 4043309111] Disabling MPLS support (no kernel support)
OK
Starting zebra.
2023/09/11 14:20:43 ZEBRA: [EC 4043309111] Disabling MPLS support (no kernel support)
Checking bgpd.conf
2023/09/11 14:20:44 BGP: [EC 33554499] sendmsg_nexthop: zclient_send_message() failed
OK
Starting bgpd.
Thanks for any orientation.
--
jaimeco
I have one prefix, e. g. 170.234.78.0/24 which is announced by e. g. ASN 28929 on IPv4, everything works fine with that.
Now, my organisation need to announce prefix IPv6, e. g. 2805:1a5::/48 with another ASN 273141
How can I configure multiple BGP instances with different ASNs? In GUI I cannot look nothing to do that.
I did try in CLI on /usr/local/etc/frr/bgpd.conf like the follow, with no success using VRF option in config file:
! Zebra configuration saved from vty
!
log syslog notifications
frr defaults traditional
!
!
router bgp 28929
no bgp default ipv4-unicast
no bgp ebgp-requires-policy
bgp network import-check
neighbor 21.173.52.185 remote-as 24764
neighbor 21.173.52.185 update-source igb1
address-family ipv4 unicast
redistribute connected
network 170.234.78.0/24
neighbor 21.173.52.185 activate
neighbor 21.173.52.185 next-hop-self
neighbor 21.173.52.185 prefix-list USACTEC-IN in
neighbor 21.173.52.185 prefix-list USACTEC-OUT out
neighbor 21.173.52.185 route-map RMUSACTEC-IN1 in
neighbor 21.173.52.185 route-map RMUSACTEC-OUT1 out
exit-address-family
!
address-family ipv6 unicast
redistribute connected
exit-address-family
!
!
!
router bgp 273141 vrf jaimecov6
neighbor 2803:bf40::5 remote-as 24764
neighbor 2803:bf40::5 update-source igb1
!
address-family ipv6 unicast
redistribute connected
network 2805:1a5::/48
neighbor 2003:bf40::5 activate
neighbor 2003:bf40::5 next-hop-self
neighbor 2003:bf40::5 prefix-list USACTECv6-IN in
neighbor 2003:bf40::5 prefix-list USACTECv6-OUT out
neighbor 2003:bf40::5 route-map RMUSACTECv6-IN1 in
neighbor 2003:bf40::5 route-map RMUSACTECv6-OUT1 out
exit-address-family
!
ip prefix-list USACTEC-IN seq 3 permit any
ip prefix-list USACTEC-OUT seq 1 permit 170.234.78.0/24
!
ip prefix-list USACTECv6-IN seq 5 permit any
ip prefix-list USACTECv6-OUT seq 4 permit 2805:1a5::/48
!
!
!
route-map RMUSACTEC-IN1 permit 3
match ip address prefix-list USACTEC-IN
route-map RMUSACTEC-OUT1 permit 1
match ip address prefix-list USACTEC-OUT
!
route-map RMUSACTECv6-IN1 permit 5
match ip address prefix-list USACTECv6-IN
route-map RMUSACTECv6-OUT1 permit 4
match ip address prefix-list USACTECv6-OUT
!
!
line vty
!!!
# service frr restart
Stopping bgpd.
Waiting for PIDS: 58719.
Stopping zebra.
Waiting for PIDS: 57401.
Checking zebra.conf
2023/09/11 14:20:43 ZEBRA: [EC 4043309111] Disabling MPLS support (no kernel support)
OK
Starting zebra.
2023/09/11 14:20:43 ZEBRA: [EC 4043309111] Disabling MPLS support (no kernel support)
Checking bgpd.conf
2023/09/11 14:20:44 BGP: [EC 33554499] sendmsg_nexthop: zclient_send_message() failed
OK
Starting bgpd.
Thanks for any orientation.
--
jaimeco