If you change the med in a term, then filter in a following term, you don't «accept» in the first term. Because «accept» is a terminating action.
No terminating action (like «then metric») or no action calls an implicit «next term».
Therefore, djadhav's question is a good question :)
------------------------------
Olivier Benghozi
------------------------------
Original Message:
Sent: 09-02-2025 15:21
From: HoneyBear
Subject: Question on the 'next term' action
Hi,
Let's say that you have two actions that you want to perform on a list of routes. The first term can set the MED on those routes. Now, let's say that you want to do something additional to a subset of those routes, like set Next Hop Self. So, in the first term, you can both accept the route and set next-term. In the second term, you can filter down to the smaller list that you want to set the NHS on.
This is just one example.
Erik
Juniper Business Use Only
Original Message:
Sent: 8/30/2025 7:14:00 AM
From: djadhav
Subject: Question on the 'next term' action
Hi.
I know what the 'next term' action in a routing policy does, but why would anyone need to add it to a policy. After a route is processed by a term that doesn't have an 'accept' or 'reject' action, it will anyway be processed by the next term.
So.. what is the purpose of the 'next term' action?
Thanks,
Deepak
-------------------------------------------