Not that simple...
Configuring an Import Policy for the PE Router's VRF Table
An import policy must contain a second term that rejects all other routes.
Unless an import policy contains only a then reject statement, it must include a reference to a community. Otherwise, when you try to commit the configuration, the commit fails. You can configure multiple import policies.
Not sure all the route really can be default-matched in such VRF import policy, not sure they default-match if they don't explicitly match a target community, actually...
Lab test is required :)
------------------------------
Olivier BenghoziOlivier Benghozi
------------------------------
Original Message:
Sent: 10-08-2024 01:47
From: ABHISHEK KUMAR
Subject: VRF-IMPORT policy | Implicit statement
"You would need to add a reject all term at the end of the policy as you note. " I would like to do exactly opposite of it. if my other routes as you say (other than community B and C) will be accepted by policy then I don't need do anything.
------------------------------
ABHISHEK KUMAR
Original Message:
Sent: 10-07-2024 19:47
From: spuluka
Subject: VRF-IMPORT policy | Implicit statement
It will accept all other routes as the default behavior.
You would need to add a reject all term at the end of the policy as you note.
------------------------------
Steve Puluka BSEET - Juniper Ambassador
IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP - Retired)
http://puluka.com/home
Original Message:
Sent: 10-07-2024 08:17
From: ABHISHEK KUMAR
Subject: VRF-IMPORT policy | Implicit statement
Does VRF-IMPORT policy have any implicit statement? if we dont define any at the end of the policy terms?
Take a look at policy below
At present VRF A table has 100 routes. I configure the following (this A-IN policy is new) and will be applied on vrf level. At present there is no policy applied at VRF level and all the import and export are happening based on global RT.
Please note community B and C have RT defined
| set policy-options policy-statement A-IN term B from community B |
| set policy-options policy-statement A-IN term B then local-preference 150 |
| set policy-options policy-statement A-IN term B then accept |
| set policy-options policy-statement A-IN term C from community C |
| set policy-options policy-statement A-IN term C then local-preference 130 |
| set policy-options policy-statement A-IN term C then accept |
| set routing-instances D vrf-import A-IN |
will the above policy only accept community B and C routes or will it allow other routes as well since I dont have any REJECT term at the end of my policy?
------------------------------
ABHISHEK KUMAR
------------------------------