Hi all,
We have a MX-104, with the following OS:
Model: mx104
Junos: 13.3R7.4
JUNOS Base OS boot [13.3R7.4]
In BGP configuration, there was only one BGP group, and inside this group, 2 neighbors (i-BGP, towards route reflectors).
We added a second BGP group, and inside of it, an e-BGP neighbor. When we committed, ALL BGP neighbors went down, and then re-established adjacency.
The log shows:
Jun 1 14:45:54 DEVICE-re0 rpd[1541]: %DAEMON-4: bgp_adv_main_update:8762: NOTIFICATION sent to NEIGHBOR-1 (Internal AS MY AS): code 6 (Cease) subcode 6 (Other Configuration Change), Reason: Configuration change - VPN table advertise
Jun 1 14:45:54 DEVICE-re0 rpd[1541]: %DAEMON-4: bgp_adv_main_update:8762: NOTIFICATION sent to NEIGHBOR-2 (Internal AS MY AS): code 6 (Cease) subcode 6 (Other Configuration Change), Reason: Configuration change - VPN table advertise
Jun 1 14:45:54 DEVICE-re0 rpd[1541]: %DAEMON-4: bgp_set_peer_if: BGP peer NEIGHBOR-3 (External AS ISP AS) interface not found. Leaving peer idled
Jun 1 14:45:57 DEVICE-re0 mgd[88798]: %INTERACT-4-UI_COMMIT_COMPLETED: commit complete
Jun 1 14:45:58 DEVICE-re0 mib2d[1473]: %DAEMON-4-SNMP_TRAP_LINK_DOWN: ifIndex 551, ifAdminStatus down(2), ifOperStatus down(2), ifName xe-2/0/1.950
Jun 1 14:46:00 DEVICE-re0 /kernel: %KERN-4: ae_linkstate_ifd_change: MUP received for interface xe-2/0/1, member of ae1
Jun 1 14:46:28 DEVICE-re0 rpd[1541]: %DAEMON-3: bgp_process_caps: mismatch NLRI with NEIGHBOR-2 (Internal AS MY AS): peer: <inet-vpn-unicast l2vpn>(68) us: <inet-vpn-unicast>(4)
Jun 1 14:46:31 DEVICE-re0 rpd[1541]: %DAEMON-3: bgp_process_caps: mismatch NLRI with NEIGHBOR-1 (Internal AS MY AS): peer: <inet-vpn-unicast l2vpn>(68) us: <inet-vpn-unicast>(4)
So, why is this behaviour? I don't understand what's the reason all bgp neighbors go down/reset when adding another BGP group in BGP configuration. Is this MX-104 specific?
Thanks.