We need to pass our ASN inside the community, having them separate doesn't work for us. For example, we need to see 123:666
That said, it was just as easy to add Large Community support so we didn't end up in a spot where the ASN and Community were variables, but could overflow the structure with valid variable choices. I need to talk to our network engineers to see if they can support the Large Community as this does:
Network Next Hop AS_PATH Age Attrs
*> 1.1.1.1/32 192.0.2.199 65400 00:08:31 [{Origin: ?} {LargeCommunity: [ 65400:666:0]}]
If we can't support that right now, it would be easy enough to add in standard community support in some sort of if/then. Maybe based on a binary being set in the web socket message of Largecommunities: True or Largecommunities: False and then we can pull from that like we do ASN and Community already.
We need to pass our ASN inside the community, having them separate doesn't work for us. For example, we need to see
123:666That said, it was just as easy to add Large Community support so we didn't end up in a spot where the ASN and Community were variables, but could overflow the structure with valid variable choices. I need to talk to our network engineers to see if they can support the Large Community as this does:
Network Next Hop AS_PATH Age Attrs *> 1.1.1.1/32 192.0.2.199 65400 00:08:31 [{Origin: ?} {LargeCommunity: [ 65400:666:0]}]
If we can't support that right now, it would be easy enough to add in standard community support in some sort of if/then. Maybe based on a binary being set in the web socket message of
Largecommunities: TrueorLargecommunities: Falseand then we can pull from that like we do ASN and Community already.