Orphaned BGP Neighbour Config Left In The Address-family After Relocating A Site To A New Device

(Doc ID 2021013.1)

Last updated on JUNE 30, 2017

Applies to:

Oracle Communications IP Service Activator - Version 7.2.0 and later
Information in this document applies to any platform.

Symptoms

2 BGP sites were created in the same address family with random attributes:

address-family ipv4 vrf BGPN
redistribute connected route-map BGP-CONNECTED
redistribute static route-map BGP-STATIC
neighbor <IP Address> remote-as 1020
neighbor <IP Address> local-as 5678 no-prepend
neighbor <IP Address> ebgp-multihop 5
neighbor <IP Address> password 7 094B481D1C1603
neighbor <IP Address> update-source FastEthernet0/0.100
neighbor <IP Address> activate
neighbor <IP Address> send-community both
neighbor <IP Address> default-originate route-map DEFAULT-ORIG-MAP
neighbor <IP Address> as-override
neighbor <IP Address> weight 10
neighbor <IP Address> soft-reconfiguration inbound
neighbor <IP Address> route-map GENERATED-ROUTE-MAP in
neighbor <IP Address> filter-list 1 in
neighbor <IP Address> filter-list 2 out

neighbor <IP Address> remote-as 1020
neighbor <IP Address> local-as 2345
neighbor <IP Address> description BGP neighbor desc
neighbor <IP Address> update-source FastEthernet0/0.110
neighbor <IP Address> activate
neighbor <IP Address> next-hop-self
neighbor <IP Address> remove-private-as
neighbor <IP Address> advertisement-interval 10
neighbor <IP Address> route-map INBOUND-ROUTEMAP in
neighbor <IP Address> maximum-prefix 100 90




 The site was unlinked in IPSA. After config removal, the following was still in the address family for that neighbour:


 

neighbor <IP Address> remote-as 1020

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms