Route Policy - Match All matching any?

  • 0
  • 1
  • Question
  • Updated 5 years ago
Create Date: Oct 4 2013 2:18PM

Hi all,

I have the following issue, tested in both 15.2 and 15.3 EXOS, am I doing something wrong?

configure bgp neighbor 10.10.112.103 route-policy out out-filter-1

out-filter-1.pol:
entry OutFilter1 {
        if match all {
                nlri 10.10.112.0/22;
                nlri any/23;
        }
        then { permit; }
}
entry deny_all { if { }
        then { deny; }
}
(vr Internet) BD-1.7 # show bgp neighbor 10.10.112.103 transmitted-routes all

Advertised Routes:
     Destination                         Next-Hop        LPref Weight MED        AS-Path
----------------------------------------------------------------------------------------
 >i  10.10.112.0/22                     10.10.112.101  100          0          
 >i  10.10.112.0/24                     10.10.112.101  100          0          
 >i  10.10.112.0/25                     10.10.112.101  100          0          
 >i  10.10.112.128/25                   10.10.112.101  100          0          

I don't want to transmit the first route, am I doing anything wrong?


(from Luis_Coelho)
Photo of EtherNation User

EtherNation User, Employee

  • 20,340 Points 20k badge 2x thumb

Posted 5 years ago

  • 0
  • 1
Photo of EtherNation User

EtherNation User, Employee

  • 20,340 Points 20k badge 2x thumb
Create Date: Oct 24 2013 2:37PM

bump.

Does anyone use Extreme's BGP?

(from Luis_Coelho)
Photo of EtherNation User

EtherNation User, Employee

  • 20,340 Points 20k badge 2x thumb
Create Date: Oct 28 2013 12:42AM

Hi

delete "nlri 10.10.112.0/22;" from entry OutFilter1

--
Jarek

(from Jaroslaw_Kasjaniuk)
Photo of EtherNation User

EtherNation User, Employee

  • 20,340 Points 20k badge 2x thumb
Create Date: Nov 4 2013 6:19PM

If you show policy out-filter-1, does it match? In particular, does the match all directive still say match all, or did it turn into a match any?

I've seen some mysterious issues with match alls turning into match anys. They might be resolved in 15.3.2p1-2, but I'm not sure yet.

Also, you may need to remove and then reapply the policy, if you've changed it since applying it. Refresh policy doesn't seem to be sufficient. (initiating a bgp soft reconfiguration might be though).

I assume you are trying to match any /23 or smaller subnet that is also part of that /22 (but not the /22 itself)?

(from xxiii)

This conversation is no longer open for comments or replies.