BGP - Vyatta - Advice getting range advertised with communities

I'm trying to advertise a class C out of a data centre using bgp.

I am using vyatta.

I have the bgp session connected, but they operate a default deny advertisement scheme and you have to tag your prefix with their communities depending on where you want it advertised, else they will not advertise it.  This is where I'm having the issue.

The relevant config is below (ip / as changed). 199.138.102.0/24 = our range, 1 = our as

 prefix-list EXPORT-PREFIXES {
     rule 1 {
         action permit
         prefix 199.138.102.0/24
     }
 }
 route-map EDGE {
     rule 10 {
         action permit
         match {
             ip {
                 address {
                     prefix-list EXPORT-PREFIXES
                 }
             }
         }
         set {
             community "12100:805 additive"
         }
     }
 }

 bgp 1 {
     neighbor 44.232.39.33 {
         password xxx
         remote-as 12100
         route-map {
             export EDGE
         }
     }
     network 199.138.102.0/24 {
     }
 }

For community I have tried 12100:805 additive, additive 12100:805, and 12100:805.  They also have a 0 after it for no-prepend (not sure if that is required or not but I have tried that as well).  I have cleared the bgp session after making changes.  The route does not seem to propagate. The isp is telling me the prefix is being received but is not tagged with any communities.  I thought the above would take care of that?  Besides the specific location communities, I've also been given  'all peers' and 'all transit' communities.  Tried them as well!

Any advice to get this up and running?
pjsmith2Asked:
Who is Participating?
 
pjsmith2Author Commented:
Hi,

OK, got up this morning to find this all working!  The syntax in vyatta is the other way round as per the docs )and not the forum examples!).  It is 'additive 12100:805'.

I wrote to the ISP in desperation before I gave up for the night last night.  They had replied by this morning saying they has an as path filter in place preventing my as being advertised.  Being new to this, I assumed the error was my side as they'd already said their side was ready to go :(
0
 
rfc1180Commented:
it should be "12100:805 additive"; your syntax is correct. You are either running into a bug or the ISP has no idea how to look for a community. The fact they are getting the prefix and not seeing a community is a bit interesting. Have your provider send you the output of
'show ip bgp 199.138.102.0'

You should see something like:

edge01.lax02#show ip bgp 172.16.100.0
BGP routing table entry for 172.16.100.0/24, version 13
Paths: (1 available, best #1, table Default-IP-Routing-Table)
  Not advertised to any peer
  65000
    10.100.100.2 from 10.100.100.2 (10.100.100.2)
      Origin IGP, metric 0, localpref 100, valid, external, best
      Community: 12100:805

Additionally you can capture the packets to see if you are in fact sending the communities; in the BGP update packet, there should be a dedicated field for the communities.


Billy
0
 
rfc1180Commented:
Yeah, not too sure on the additive, i have mine at the end and was from previous versions. Cisco is at the end as well. But glad you have it working

Billy
0
 
QlemoBatchelor, Developer and EE Topic AdvisorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.