[FROG] FRR - Route-Server / IPv6 error
Duchet Rémy
remy at duchet.eu
Wed Jan 30 08:13:58 EST 2019
Hi Donald,
rs02# show bgp nexthop
% No such BGP instance exist
rs02# sh ipv6 nht
rs02#
And
sh ip bgp view rs summary
IPv4 Unicast Summary:
BGP router identifier 185.56.25.16, local AS number 65129 vrf-id -1
BGP table version 730864
RIB entries 1332016, using 203 MiB of memory
Peers 6, using 123 KiB of memory
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
192.168.0.2 4 60129 247305 235917 0 0 0 00:06:21 729682
192.168.0.17 4 60129 46 121481 0 0 0 00:37:01 2
192.168.0.18 4 60129 46 121482 0 0 0 00:37:05 2
2001:db8::2 4 60129 195 260 0 0 0 00:00:09 Idle
2001:db8::17 4 60129 47 42 0 0 0 00:13:17 NoNeg
2001:db8::18 4 60129 47 42 0 0 0 00:13:17 NoNeg
Total number of neighbors 6
sh zebra client
Client: bgp
------------------------
FD: 14
Route Table ID: 0
Connect Time: 00:39:14
Not registered for Nexthop Updates
Last Msg Rx Time: 00:39:14
Last Msg Tx Time: 00:39:14
Last Rcvd Cmd: ZEBRA_HELLO
Type Add Update Del
==================================================
IPv4 0 0 0
IPv6 0 0 0
Redist:v4 0 0 0
Redist:v6 0 0 0
Connected 0 0 0
BFD peer 0 0 0
Interface Up Notifications: 0
Interface Down Notifications: 0
VNI add notifications: 0
VNI delete notifications: 0
L3-VNI add notifications: 0
L3-VNI delete notifications: 0
MAC-IP add notifications: 0
MAC-IP delete notifications: 0
Client: vnc
------------------------
FD: 21
Route Table ID: 0
Connect Time: 00:39:14
Not registered for Nexthop Updates
Last Msg Rx Time: 00:39:14
Last Msg Tx Time: 00:39:14
Last Rcvd Cmd: ZEBRA_HELLO
Type Add Update Del
==================================================
IPv4 0 0 0
IPv6 0 0 0
Redist:v4 0 0 0
Redist:v6 0 0 0
Connected 0 0 0
BFD peer 0 0 0
Interface Up Notifications: 0
Interface Down Notifications: 0
VNI add notifications: 0
VNI delete notifications: 0
L3-VNI add notifications: 0
L3-VNI delete notifications: 0
MAC-IP add notifications: 0
MAC-IP delete notifications: 0
Client: static
------------------------
FD: 28
Route Table ID: 0
Connect Time: 00:39:14
Nexthop Registry Time: 00:39:14
Nexthop Last Update Time: 00:39:14
Last Msg Rx Time: 00:39:14
Last Msg Tx Time: 00:39:14
Last Rcvd Cmd: ZEBRA_ROUTE_ADD
Type Add Update Del
==================================================
IPv4 2 0 2
IPv6 0 0 0
Redist:v4 0 0 0
Redist:v6 0 0 0
Connected 9 0 0
BFD peer 0 0 0
Interface Up Notifications: 0
Interface Down Notifications: 0
VNI add notifications: 0
VNI delete notifications: 0
L3-VNI add notifications: 0
L3-VNI delete notifications: 0
MAC-IP add notifications: 0
MAC-IP delete notifications: 0
sh ip bgp view rs nexthop
Current BGP nexthop cache:
192.168.0.2 valid [IGP metric 0], #paths 729694
192.168.0.17 valid [IGP metric 0], #paths 2
192.168.0.18 valid [IGP metric 0], #paths 2
Does it means that Zebra need to run differently / with config ?
Rémy
-----Message d'origine-----
De : Donald Sharp <sharpd at cumulusnetworks.com>
Envoyé : mercredi, 30 janvier 2019 14:04
À : Duchet Rémy <remy at duchet.eu>
Cc : frog at lists.frrouting.org
Objet : Re: [FROG] FRR - Route-Server / IPv6 error
Duchet -
Can I see `show ipv6 nht` and a `show bgp nexthop`. This sure looks like you don't have zebra running
donald
On Wed, Jan 30, 2019 at 7:43 AM Duchet Rémy <remy at duchet.eu> wrote:
>
> Hello all,
>
>
>
> We have setup successfully FRR as route server (IPv4) with multiple PEER (Cisco ASR), and we are happy with the first part of the configuration.
>
> When we try to configure the same with IPv6, we have multiple problem, and the BGP session is always reset.
>
> Our setup :
>
> - CISCO ASR IOS-XE 16.1 and IOS-XE 15.4
>
> - Physical server with Bond interface (2 x 10Gbps SFP+) and 1 UTP (for management purpose).
>
> - Private AS for the route-server
>
> - Public AS for all other router
>
>
>
> Purpose of this setup :
>
> - All router will announce his own learned BGP route to the RS
>
> - The RS will redistribute one FULL table to all router.
>
>
>
> Configuration on FRR (IP add and router-ID was changed:
>
>
>
> router bgp 65129 view rs
>
> bgp router-id 192.168.1.16
>
> bgp log-neighbor-changes
>
> neighbor 2001:db8::2 remote-as 60129
>
> neighbor 2001:db8::2 interface br0
>
> neighbor 2001:db8::2 update-source br0
>
> !
>
> address-family ipv6 unicast
>
> neighbor 2001:db8::2 activate
>
> neighbor 2001:db8::2 as-override
>
> neighbor 2001:db8::2 soft-reconfiguration inbound
>
> neighbor 2001:db8::2 route-server-client
>
> exit-address-family
>
>
>
> Configuration on PEER (IP add and router-ID was changed:
>
>
>
> router bgp 60129
>
> bgp router-id 192.168.0.2
>
> no bgp enforce-first-as
>
> bgp log-neighbor-changes
>
> neighbor 2001:db8::16 remote-as 65129
>
> neighbor 2001:db8::16 update-source Port-channel5.210
>
> !
>
> address-family ipv6
>
> neighbor 2001:db8::16 activate
>
> neighbor 2001:db8::16 next-hop-self
>
> neighbor 2001:db8::16 allowas-in
>
> neighbor 2001:db8::16 soft-reconfiguration inbound
>
> exit-address-family
>
> !
>
>
>
> Debug Log of FRR (real IPv6 was changed ):
>
>
>
> 2019/01/30 08:31:50 BGP: u7:s5 add peer 2001:db8::2
>
> 2019/01/30 08:31:50 BGP: 2001:db8::2: Interface not set appropriately
> to handle this some attributes
>
> 2019/01/30 08:31:50 BGP: 2001:db8::2: Attribute MP_REACH_NLRI, parse
> error - treating as withdrawal
>
> 2019/01/30 08:31:50 BGP: 2001:db8::2 rcvd UPDATE with errors in attr(s)!! Withdrawing route.
>
> 2019/01/30 08:31:50 BGP: 2001:db8::2 [Error] Update packet error
> (wrong prefix length 64 for afi 1)
>
> 2019/01/30 08:31:50 BGP: 2001:db8::2 [Error] Error parsing NLRI
>
> 2019/01/30 08:31:50 BGP: %NOTIFICATION: sent to neighbor 2001:db8::2
> 3/10 (UPDATE Message Error/Invalid Network Field) 0 bytes
>
> 2019/01/30 08:31:50 BGP: bgp_process_packet: BGP UPDATE receipt failed
> for peer: 2001:db8::2
>
> 2019/01/30 08:31:50 BGP: %ADJCHANGE: neighbor 2001:db8::2(Unknown) in
> vrf Down BGP Notification send
>
> 2019/01/30 08:31:50 BGP: 2001:db8::2 remove from all update group
>
> 2019/01/30 08:32:02 BGP: bind to interface br0 failed, errno=1
>
> 2019/01/30 08:32:02 BGP: 2001:db8::2 unrecognized capability code: 70
> - ignored
>
> 2019/01/30 08:32:02 BGP: %ADJCHANGE: neighbor 2001:db8::2(Unknown) in
> vrf Up
>
> 2019/01/30 08:32:02 BGP: u7:s5 add peer 2001:db8::2
>
> 2019/01/30 08:32:02 BGP: 2001:db8::2: Interface not set appropriately
> to handle this some attributes
>
> 2019/01/30 08:32:02 BGP: 2001:db8::2: Attribute MP_REACH_NLRI, parse
> error - treating as withdrawal
>
> 2019/01/30 08:32:02 BGP: 2001:db8::2 rcvd UPDATE with errors in attr(s)!! Withdrawing route.
>
> 2019/01/30 08:32:02 BGP: 2001:db8::2 [Error] Update packet error
> (wrong prefix length 64 for afi 1)
>
> 2019/01/30 08:32:02 BGP: 2001:db8::2 [Error] Error parsing NLRI
>
> 2019/01/30 08:32:02 BGP: %NOTIFICATION: sent to neighbor 2001:db8::2
> 3/10 (UPDATE Message Error/Invalid Network Field) 0 bytes
>
> 2019/01/30 08:32:02 BGP: bgp_process_packet: BGP UPDATE receipt failed
> for peer: 2001:db8::2
>
> 2019/01/30 08:32:02 BGP: %ADJCHANGE: neighbor 2001:db8::2(Unknown) in
> vrf Down BGP Notification send
>
> 2019/01/30 08:32:02 BGP: 2001:db8::2 remove from all update group
>
> 2019/01/30 08:32:09 BGP: bind to interface br0 failed, errno=1
>
> 2019/01/30 08:32:09 BGP: 2001:db8::2 unrecognized capability code: 70
> - ignored
>
> 2019/01/30 08:32:09 BGP: %ADJCHANGE: neighbor 2001:db8::2(Unknown) in
> vrf Up
>
> 2019/01/30 08:32:09 BGP: u7:s5 add peer 2001:db8::2
>
> 2019/01/30 08:32:09 BGP: 2001:db8::2: Interface not set appropriately
> to handle this some attributes
>
> 2019/01/30 08:32:09 BGP: 2001:db8::2: Attribute MP_REACH_NLRI, parse
> error - treating as withdrawal
>
> 2019/01/30 08:32:09 BGP: 2001:db8::2 rcvd UPDATE with errors in attr(s)!! Withdrawing route.
>
> 2019/01/30 08:32:09 BGP: 2001:db8::2 [Error] Update packet error
> (wrong prefix length 64 for afi 1)
>
> 2019/01/30 08:32:09 BGP: 2001:db8::2 [Error] Error parsing NLRI
>
> 2019/01/30 08:32:09 BGP: %NOTIFICATION: sent to neighbor 2001:db8::2
> 3/10 (UPDATE Message Error/Invalid Network Field) 0 bytes
>
> 2019/01/30 08:32:09 BGP: bgp_process_packet: BGP UPDATE receipt failed
> for peer: 2001:db8::2
>
> 2019/01/30 08:32:09 BGP: %ADJCHANGE: neighbor 2001:db8::2(Unknown) in
> vrf Down BGP Notification send
>
> 2019/01/30 08:32:09 BGP: 2001:db8::2 remove from all update group
>
>
>
>
>
> Debug log from 1 PEER :
>
>
>
> Jan 30 08:34:08.582: BGP: nbr global 2001:db8::16 Open active delayed
> 9216ms (35000ms max, 60% jitter)
>
> Jan 30 08:34:08.583: BGP: nbr global 2001:db8::16 Active open failed -
> open timer running
>
> Jan 30 08:34:17.773: BGP: 2001:db8::16 active went from Idle to Active
>
> Jan 30 08:34:17.773: BGP: 2001:db8::16 open active, local address
> 2A02:4FE0::2
>
> Jan 30 08:34:17.774: BGP: ses global 2001:db8::16 (0x7F2DB7BC45C8:0)
> act Adding topology IPv6 Unicast:base
>
> Jan 30 08:34:17.774: BGP: ses global 2001:db8::16 (0x7F2DB7BC45C8:0)
> act Send OPEN
>
> Jan 30 08:34:17.774: BGP: ses global 2001:db8::16 (0x7F2DB7BC45C8:0)
> act Building Enhanced Refresh capability
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active went from Active to
> OpenSent
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active sending OPEN, version 4,
> my as: 60129, holdtime 180 seconds, ID B9381902
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active rcv message type 1,
> length (excl. header) 70
>
> Jan 30 08:34:17.774: BGP: ses global 2001:db8::16 (0x7F2DB7BC45C8:0)
> act Receive OPEN
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active rcv OPEN, version 4,
> holdtime 180 seconds
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active rcv OPEN w/ OPTION
> parameter len: 60
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active rcvd OPEN w/ optional
> parameter type 2 (Capability) len 6
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active OPEN has CAPABILITY
> code: 1, length 4
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active OPEN has MP_EXT CAP for
> afi/safi: 1/1
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active rcvd OPEN w/ optional
> parameter type 2 (Capability) len 6
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active OPEN has CAPABILITY
> code: 1, length 4
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active OPEN has MP_EXT CAP for
> afi/safi: 2/1
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active rcvd OPEN w/ optional
> parameter type 2 (Capability) len 2
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active OPEN has CAPABILITY
> code: 128, length 0
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active OPEN has ROUTE-REFRESH
> capability(old) for all address-families
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active rcvd OPEN w/ optional
> parameter type 2 (Capability) len 2
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active OPEN has CAPABILITY
> code: 2, length 0
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active OPEN has ROUTE-REFRESH
> capability(new) for all address-families
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active rcvd OPEN w/ optional
> parameter type 2 (Capability) len 6
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active OPEN has CAPABILITY
> code: 65, length 4
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active OPEN has 4-byte ASN CAP
> for: 65129
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active rcvd OPEN w/ optional
> parameter type 2 (Capability) len 10
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active OPEN has CAPABILITY
> code: 69, length 8
>
> Jan 30 08:34:17.774: BGP: ses global 2001:db8::16 (0x7F2DB7BC45C8:0) act Add Path not supported for EBGP nbr 2001:db8::16.
>
> Jan 30 08:34:17.774: BGP: ses global 2001:db8::16 (0x7F2DB7BC45C8:0) act Add Path not supported for EBGP nbr 2001:db8::16.
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active rcvd OPEN w/ optional
> parameter type 2 (Capability) len 8
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active OPEN has CAPABILITY
> code: 73, length 6
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active unrecognized capability
> code: 73 - ingored
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active rcvd OPEN w/ optional
> parameter type 2 (Capability) len 4
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active OPEN has CAPABILITY
> code: 64, length 2
>
> Jan 30 08:34:17.774: BGP: ses global 2001:db8::16 (0x7F2DB7BC45C8:0)
> act NSF OPEN has GR cap
>
> Jan 30 08:34:17.774: BGP: ses global 2001:db8::16 (0x7F2DB7BC45C8:0)
> act NSF Peer has not restarted. Restart Time: 120
>
> Jan 30 08:34:17.774: BGP: nbr global 2001:db8::16 neighbor does not
> have IPv4 MDT topology activated
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active rcvd OPEN w/ remote AS
> 65129, 4-byte remote AS 65129
>
> Jan 30 08:34:17.774: BGP: ses global 2001:db8::16 (0x7F2DB7BC45C8:0)
> act Peer sent not matching OPEN AFCAP 0
>
> Jan 30 08:34:17.774: BGP: 2001:db8::16 active went from OpenSent to
> OpenConfirm
>
> Jan 30 08:34:17.775: BGP: 2001:db8::16 active went from OpenConfirm to
> Established
>
> Jan 30 08:34:17.775: BGP: ses global 2001:db8::16 (0x7F2DB7BC45C8:1)
> act Assigned ID
>
> Jan 30 08:34:17.775: BGP: ses global 2001:db8::16 (0x7F2DB7BC45C8:1)
> Up
>
> Jan 30 08:34:17.775: %BGP-5-ADJCHANGE: neighbor 2001:db8::16 Up
>
> Jan 30 08:34:17.801: BGP: ses global 2001:db8::16 (0x7F2DB7BC45C8:1) Remote close.
>
> Jan 30 08:34:17.801: BGP: nbr_topo global 2001:db8::16 IPv6
> Unicast:base (0x7F2DB7BC45C8:1) Not scheduling for GR processing [Peer
> did not advertise GR cap]
>
> Jan 30 08:34:17.801: %BGP-5-NBR_RESET: Neighbor 2001:db8::16 reset
> (Peer closed the session)
>
> Jan 30 08:34:17.801: BGP: ses global 2001:db8::16 (0x7F2DB7BC45C8:1) Reset (Peer closed the session).
>
> Jan 30 08:34:17.801: BGP: nbr_topo global 2001:db8::16 IPv6
> Unicast:base (0x7F2DB7BC45C8:1) NSF delete stale NSF not active
>
> Jan 30 08:34:17.801: BGP: nbr_topo global 2001:db8::16 IPv6
> Unicast:base (0x7F2DB7BC45C8:1) NSF no stale paths state is NSF not
> active
>
> Jan 30 08:34:17.802: BGP: nbr_topo global 2001:db8::16 IPv6 Unicast:base (0x7F2DB7BC45C8:1) Resetting ALL counters.
>
> Jan 30 08:34:17.802: BGP: 2001:db8::16 rcv message type 3, length
> (excl. header) 2
>
> Jan 30 08:34:17.802: %BGP-3-NOTIFICATION: received from neighbor
> 2001:db8::16 3/10 (illegal network) 0 bytes
>
> Jan 30 08:34:17.802: BGP: ses global 2001:db8::16 (0x7F2DB7BC45C8:1)
> Receive NOTIFICATION 3/10 (illegal network) 0 bytes
>
> Jan 30 08:34:17.802: BGP: 2001:db8::16 went from Established to
> Closing
>
> Jan 30 08:34:17.802: %BGP_SESSION-5-ADJCHANGE: neighbor 2001:db8::16
> IPv6 Unicast topology base removed from session Peer closed the
> session
>
> Jan 30 08:34:17.802: BGP: ses global 2001:db8::16 (0x7F2DB7BC45C8:1)
> Removed topology IPv6 Unicast:base
>
> Jan 30 08:34:17.802: BGP: ses global 2001:db8::16 (0x7F2DB7BC45C8:1)
> Removed last topology
>
> Jan 30 08:34:17.802: BGP: 2001:db8::16 closing
>
> Jan 30 08:34:17.802: BGP: 2001:db8::16 went from Closing to Idle
>
> Jan 30 08:34:17.802: %BGP-5-ADJCHANGE: neighbor 2001:db8::16 Down Peer
> closed the session
>
>
>
>
>
> Any help or comment will be very appreciated.
>
> Thanks in advance,
>
>
>
>
>
> Rémy
>
>
>
> _______________________________________________
> frog mailing list
> frog at lists.frrouting.org
> https://lists.frrouting.org/listinfo/frog
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5504 bytes
Desc: not available
URL: <http://lists.frrouting.org/pipermail/frog/attachments/20190130/4f86a544/attachment-0001.bin>
More information about the frog
mailing list