06-02-2015 06:13 AM
Hi,
I work in a service provider environment and a customer requested for an Enterprise MPLS network for a customer.
The customer is going to 2 service providers terminating on their network.
the solution is something like this
Customer CPE -CE -P/PE - P/PE -CE -Customer CPE
the protocol between Cusomter CPE - CE is EIGRP, CE-PE is BGP and PE-PE is BGP for customer traffic and IS-IS for the core.
Once the EIGRP is redistributed into the BGP, The BGP begins to flap unless the redistributed prefixes are filtered to only large subnets e.g. /23, /22
Now the second provider has thesame setup with the difference of PE-CE protocol to be OSPF, PE-PE to be OSPF also.
The second providers routes were tagged and those routes were filtered out, however the flaps were still observed.
also noticed was that the routes redistributed from the eigrp into bgp on the CE were advertised via BGP to the PE and those routes were advertised back by the PE to the CE.
We tried changing the PE-CE protocol to OSPF and the link is currently stable
06-09-2015 09:38 AM
Hi,
Once the EIGRP is redistributed into the BGP, The BGP begins to flap unless the redistributed prefixes are filtered to only large subnets e.g. /23, /22
- What error are you seeing with BGP flap?.
The second providers routes were tagged and those routes were filtered out, however the flaps were still observed.
- The second provider appears to be running OSPF as PE-CE protocol. Do you mean, the OSPF is flapping?. Or did you meant, the OSPF prefix learnt from CPE where filtered and not redistributed into BGP?.
06-26-2015 04:49 AM
There are no errors from the BGP logs;
It only shows the neighbor down, this happens after every 180seconds
Yes, the OSPF prefixes learnt from the second provider were tagged and not redistributed into the BGP
06-26-2015 07:21 PM
Hi,
It only shows the neighbor down, this happens after every 180seconds
<Nagendra> Ok. Are you seeing the BGP flapping every 180 seconds due to Hold time expired?. It appears to be MTU/MSS issue.
To confirm that, can you try disabling PMTUD for this neighbor using "neighbor <> transport path-mtu-discovery disable"
-Nagendra
07-06-2015 02:09 AM
This has already being disabled.
07-06-2015 06:54 AM
How many routes are being received from the CE side. Also, can you perform the below ping test from PE to PE
PE to PE:
ping <remote_peering_ip> sou <local_peering_ip> size <mtu> df-bit rep 100
Also,
show ip bgp nei <nei_ip>
Please share the output in a file.
Thanks
Vinit
07-06-2015 01:55 PM
Do you have it disabled on both side?. Can you share teh configuration and logs from both the neighbors?.
-Nagendra
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide