Not sending Community to Peer

General questions
1

I don’t seem to be able to get the config working to send a Community to BGP peer. Here is my config … but it does not look to be working.

route-map gtt-export {
rule 10 {
action permit
match {
ip {
address {
prefix-list gtt-export
}
}
}
set {
community 3257:1000
ip-next-hop 185.180.186.62
}
}

  neighbor 185.180.186.61 {
        address-family {
            ipv4-unicast {
                remove-private-as
                route-map {
                    export gtt-export
                    import gtt-import
                }
                soft-reconfiguration {
                    inbound
                }
            }
        }
        description GTT
        password ****************
        remote-as 60670
    }

but this is what shows

For address family: IPv4 Unicast
Update group 3, subgroup 3
Packet Queue length 0
Inbound soft reconfiguration allowed
Private AS numbers removed in updates to this neighbor
Community attribute sent to this neighbor(all)
Inbound path policy configured
Outbound path policy configured
Route map for incoming advertisements is *gtt-import
Route map for outgoing advertisements is *gtt-export
887377 accepted prefixes

2

Try to reset soft out the neighbor

3

You don’t specify the prefix-list. Maybe nothing’s matching, so nothing’s getting set?

4

Also: no, doing a “show ip bgp neighbor 185.180.186.61” isn’t going to show you anything about the prefixes you’re sending.

Do “show ip bgp aa.bb.cc.dd” to see the actual prefix - it should show the community on THAT prefix.

5

it’s not showing a community being sent

show ip bgp 37.143.138.0
BGP routing table entry for 37.143.138.0/24
Paths: (1 available, best #1, table default)
Advertised to non peer-group peers:
185.180.186.61
Local
37.143.136.249 from 2a00:b340:0:4::6 (37.143.136.245)
Origin incomplete, metric 0, localpref 100, valid, internal, best (First path received)
Last update: Wed Sep 7 21:52:07 2022

but a show route-map produced

BGP:
route-map: gtt-export Invoked: 7417849 Optimization: enabled Processed Change: false
permit, sequence 10 Invoked 0
Match clauses:
ip address prefix-list gtt-export
Set clauses:
community 3257:1000
ip next-hop 185.180.186.62
Call clause:
Action:
Exit routemap

6

I notice that the next-hop didn’t get set either.

Is it possible that the prefix-list ‘gtt-export’ does not exist, or does not contain an entry that exactly matches 37.143.138.0/24?

Frankly, if it does, then you might be into “what version are you running” territory, preparatory to filling a bug report.

7

the prefix list is good and it matches … the upstream provider is currently looking at the issue as it may be an upstream issued.

8

the issue was an error with the upstream provider…

9

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.