Routing

 View Only
last person joined: 19 hours ago 

Ask questions and share experiences about ACX Series, CTP Series, MX Series, PTX Series, SSR Series, JRR Series, and all things routing, including portfolios and protocols.
  • 1.  inverse-match community

    Posted 03-20-2021 14:07
    I have the following to apply to bgp group import policy. In my understanding and tests in the lab, any prefix with the community 456:* should be accepted, otherwise rejected.

    set policy-options community com456 invert-match
    set policy-options community com456 members 456:*
    set policy-options policy-statement FromISP1 term 2 from community com456
    set policy-options policy-statement FromISP1 term 2 then reject
    ​

    The reason I am asking is what I am reading in one demo showing the prefix with the community 456:1234 is rejected. I thought it has some mistakes. But like to confirm with experienced folks.

    thanks a lot !!



  • 2.  RE: inverse-match community
    Best Answer

    Posted 03-20-2021 18:53
    Invert-match means that anything that is not <community> will be either accepted or rejected. In this case you have:

    set policy-options community com456 invert-match
    set policy-options community com456 members 456:* << # Everything with 456:*
    set policy-options policy-statement FromISP1 term 2 from community com456 << # Matching commmunity.
    set policy-options policy-statement FromISP1 term 2 then reject << # Reject anything that is NOT 456:*
    ​

    Regards,

    Elvin




  • 3.  RE: inverse-match community

    Posted 03-20-2021 18:57
    thanks a lot !!


  • 4.  RE: inverse-match community

    Posted 03-21-2021 04:51
    Welcome!

    Elvin