BGP advertise-map in XOS



Show first post

29 replies

Userlevel 4
what if the primary link fails to the other ISP . how will the secondary ISP knows that so that their routers can remove these communities As i wrote before https://community.extremenetworks.com/extreme/topics/bgp-advertise-map-in-xos?topic-reply-list%5Bset...
if secondary ISP receives routes with localpref 50 and from other uplinks with 100, then routes will become unavailable through other uplinks and become active through direct connection
Guys, i have had a case open with Expedient and Cognet for almost a Year and ISPs are hard to deal with and it takes forever. i am trying to implement a Solution from my side . in my initial post i mentioned if someone know if there is a feature like bgp advertise-map as in cisco.
thank you ,
Userlevel 6
I hate to agree with the others here but your first step has to be working with the upstream provider you are paying good money to for the best way they would support your scenario. They each have their own rules on how they will send traffic back to you from other customers of theirs that are directly connected to them. They would prefer that traffic to remain on their direct connection to you and may be ignoring any community or pre-pend you are sending out. You must escalate and work through sales channel if you have to. Tell you get responses back from them you are just guessing and hoping for the best....
Userlevel 3
Elie,

This is only an idea and I don't have a time to put it all together, but...
lets assume you have scenario like this bellow:

Router Expedient - Low speed link
/
Your Standby Router (EXOS switch)
|
|
|
Your Main Router (EXOS switch)
\
Router Cogent - High speed link

You advertise your prefix for example 10.0.0.0/24 from Main router:
- dirtect to Cogent
- to Standby Router and then to Expedient

On Main Router you can have a UPM script and BGP export policy.

The UPM script will check if some route is in table and this route nexthop is via Cogent
or if the session is up and so on.
If the route does not exists, you apply iBGP_export_Stby.pol to iBGP peer out to Standby Router
and advertise prefix with community 65535:100
If all is ok, unconfigure policy iBGP_export_Stby.pol

================= iBGP_export_Stby.pol =====================

entry iBGP_peer_Main { if match all {
nlri 10.0.0.0/24;
} then {
permit;
community set 65535:100;
}}

========================================================

On Stanby Router you can have a policy that import prefix from Main router like this:
If I receive my prefix from IBGP peer Main Router with community 65535:100
then I will permit and then advertise to Expedient.
If not deny the prefix and don't advertise anything.

example
========== iBGP_import_Main.pol =============================
entry iBGP_peer_Main { if match all {
community 65535:100;
nlri 10.0.0.0/24;
} then {
permit;
}}

entry IP_BGP_deny { if {
} then {
deny;
}}
===========================================================

--
Jarek

Reply