bgp peering with mx stays in active

Bug #1788379 reported by vimal
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
Trunk
New
Critical
Nikhil Bansal

Bug Description

bgp peering with mx stays in active . From MX logs its shown as contrail advertise wrong AS (16515072 instead of 64512) . This is seen in latest master builds.

build
---------
ocata-master-248

topology
------------
nodec7 , nodec8

contrail logs
-------------
/cs-shared/bugs/1788379

mx logs
---------
Aug 22 16:18:16.420831 BGP RECV 192.168.192.5+179 -> 192.168.192.253+59617
Aug 22 16:18:16.420882 BGP RECV message type 1 (Open) length 65
Aug 22 16:18:16.420920 BGP RECV version 4 as 64512 holdtime 90 id 192.168.192.5 parmlen 36
Aug 22 16:18:16.420948 BGP RECV MP capability AFI=1, SAFI=128
Aug 22 16:18:16.420974 BGP RECV MP capability AFI=2, SAFI=128
Aug 22 16:18:16.420998 BGP RECV MP capability AFI=1, SAFI=132
Aug 22 16:18:16.421022 BGP RECV MP capability AFI=25, SAFI=70
Aug 22 16:18:16.421052 BGP RECV 4 Byte AS-Path capability (65), as_num 16515072
Aug 22 16:18:16.421081 BGP RECV Restart capability, code=64, time=0, flags=
Aug 22 16:18:16.421295 bgp_process_open:4064: NOTIFICATION sent to 192.168.192.5 (Internal AS 64512): code 2 (Open Message Error) subcode 2 (bad peer AS number), Reason: peer 192.168.192.5 (Internal AS 64512) claims 16515072, 64512 configured <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Aug 22 16:18:16.421338 BGP_64512.192.168.192.5: send proc: sending 21 bytes
Aug 22 16:18:16.421375

root@hooper> show configuration protocols bgp group testbed_c7_c8_g31_i1_i3 | display set
set protocols bgp group testbed_c7_c8_g31_i1_i3 type internal
set protocols bgp group testbed_c7_c8_g31_i1_i3 traceoptions file testbed_log
set protocols bgp group testbed_c7_c8_g31_i1_i3 traceoptions file size 65535
set protocols bgp group testbed_c7_c8_g31_i1_i3 traceoptions file world-readable
set protocols bgp group testbed_c7_c8_g31_i1_i3 traceoptions flag packets detail
set protocols bgp group testbed_c7_c8_g31_i1_i3 local-address 192.168.192.253
set protocols bgp group testbed_c7_c8_g31_i1_i3 keep all
set protocols bgp group testbed_c7_c8_g31_i1_i3 family inet-vpn unicast
set protocols bgp group testbed_c7_c8_g31_i1_i3 family route-target
set protocols bgp group testbed_c7_c8_g31_i1_i3 local-as 64512
set protocols bgp group testbed_c7_c8_g31_i1_i3 neighbor 192.168.192.6
set protocols bgp group testbed_c7_c8_g31_i1_i3 neighbor 192.168.192.5
set protocols bgp group testbed_c7_c8_g31_i1_i3 neighbor 192.168.192.7

vimal (vappachan)
description: updated
Revision history for this message
Nikhil Bansal (nikhilb-u) wrote :

Have you tried an image which has fix for 1787978?
I had verified the fix with Ganesha on MX setup so please let me know before I dig deeper into it.

Revision history for this message
vimal (vappachan) wrote :

hi Nikhil,

Checked in latest master , this issue is fixed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.